Systems and methods for display device and sensor electronics unit communication

Abstract

To provide methods and apparatus for communication among display devices and a sensor electronics unit in an analyte monitoring system.SOLUTION: The analyte monitoring system may include a sensor that is configured to perform measurement indicative of analyte levels. The sensor may be communicatively coupled to the sensor electronics unit. The sensor electronics unit may be configured to transmit data indicative of analyte levels to the display devices using one or more communication protocols. Furthermore, the sensor electronics unit may be configured to operate in multiple modes, and switch between the modes in response to commands received from the display devices. Related systems, methods and articles of manufacture are also described.SELECTED DRAWING: Figure 1A

Description

[Technical field]

[0001] INCORPORATION BY REFERENCE OF RELATED APPLICATIONS Any and all priority claims or any amendments thereto identified in the Application Data Sheet are incorporated herein by reference under 37 CFR 1.57. This application claims the benefit of U.S. Provisional Application No. 62 / 315,976, filed March 31, 2016. The aforementioned application is incorporated herein by reference in its entirety and expressly made a part hereof.

[0002] FIELD OF THE DISCLOSURE This application relates generally to systems and methods for communication between a sensor electronics unit and a display device of an analyte monitoring system. [Background technology]

[0003] The analyte monitor can be configured to be placed on the tissue and detect an analyte within a sensing region. For example, without limitation, the analyte monitor can include sensors that measure concentrations of glucose, lactate, cholesterol, hemoglobin, and / or other blood or bodily fluid constituents.

[0004] In some cases, a person with diabetes mellitus (also known as diabetes) may use an analyte monitor. Diabetes mellitus is a disorder in which a person's pancreas cannot make enough insulin, such as type I diabetes, and / or in which insulin cannot be effective for the person, such as type II diabetes. In the diabetic state, the affected person may suffer from hyperglycemia, which can result in a series of physiological disorders, such as kidney failure, skin ulcers, or bleeding into the vitreous of the eye, which may be associated with deterioration of the microvessels. A hypoglycemic response, such as low blood sugar, may be triggered by inadvertent overdosing of insulin, or extreme exercise or inadequate food intake after regular dosing of insulin or glucose-lowering agents.

[0005] In some cases, a diabetic patient may carry an analyte monitor, such as a self-monitoring blood glucose ("SMBG") monitor, which may typically utilize an uncomfortable finger prick method. Due to lack of comfort and / or convenience, a diabetic patient typically measures their glucose levels only two to four times per day. Unfortunately, these time intervals are spread so far apart that a diabetic patient may not know until it is too late that they are in a hyperglycemic or hypoglycemic state, sometimes resulting in dangerous side effects. In fact, not only may a diabetic patient not be able to take their SMBG readings in a timely manner, but a diabetic patient may also not know whether their blood glucose levels are rising or falling based on traditional methods.

[0006] As a result, a variety of analyte monitors have been developed that include noninvasive, transcutaneous (e.g., transdermal), and / or implantable electrochemical sensors for continuously detecting and / or quantifying blood glucose levels. These, and other types of devices, generally allow for the transmission of raw or processed data to a remote device, which may include a display, to present information to a user hosting the sensor. Summary of the Invention [Means for solving the problem]

[0007] Any of the features of an embodiment explicitly described herein is applicable to all other embodiments and implementations identified herein. Furthermore, any of the features of an embodiment may be combined, in part or in whole, independently with other embodiments described herein, e.g., one, two, or more embodiments may be combined in whole or in part. Furthermore, any of the features of an embodiment may be optional with respect to other embodiments. Any embodiment of a method may be performed by a system or device of another embodiment, and any embodiment of a system may be configured to perform a method of another embodiment.

[0008] In some implementations, multiple communication protocols can be used for communication between the sensor electronics unit and one or more display devices. Communication between the sensor electronics units can be based on wired and / or wireless communication protocols, which are discussed later in this disclosure with reference to Figures 3-4, as well as elsewhere throughout this disclosure. For example, without limitation, a first communication protocol can utilize wireless communication, such as BLUETOOTH or Bluetooth Low Energy (BLE) wireless communication protocols, which use a wireless communication frequency range of 2.4-2.485 GHz. A second communication protocol can utilize a radio frequency ("RF") field, such as near field communication ("NFC") or radio frequency identification ("RFID"). NFC can be an RF field having a frequency of 13.56 MHz. RFID can operate in a range of frequency bands, including but not limited to 120-150 kHz, 13.56 MHz, 433 MHz, 865-868 MHz, 902-928 MHz, 2450-5800 MHz, and 3.1-10 GHz.

[0009] In some implementations, the second communication protocol can be used by the display device to communicate with the sensor electronics unit. In some cases, these communications can include commands / requests, transmission of data, and / or other communications.

[0010] In some implementations, the display device can utilize the second communication protocol to cause the sensor electronics unit to perform one or more actions. In some cases, these actions can be combined into action cues. Thus, the actions described in various implementations of this disclosure can be combined into a series of actions. These various actions and their functional units are discussed later in this disclosure with reference to Figures 5C, 6A-B, and elsewhere throughout this disclosure.

[0011] In some implementations, one action can be a wake action, where the display device uses the second communication protocol to send a command / request and / or data to wake up the sensor electronics unit from shelf mode, idle mode, and / or any low power mode. In some cases, after waking up, the sensor electronics unit can use the first communication protocol to pair and communicate with the display device used to wake up the sensor electronics unit. Similarly, the second communication protocol can be used to change the operating mode of the sensor electronics unit, such as changing to shelf mode, idle mode, low power mode, normal mode, high speed mode, and / or any mode that may be desirable for the sensor electronics unit.

[0012] In some embodiments, an analyte level monitoring system is provided that includes an analyte sensor for measuring an analyte level and is communicatively coupled to a sensor electronics unit. The sensor electronics unit is configured to receive analyte measurement data from the sensor and can be further configured to process the data to calculate an estimated analyte value based on the measurement data. The sensor electronics unit is also configured to communicate with the display device using multiple communication protocols and to operate in multiple operational modes. For example, but not limited to, the operational modes can include a normal power mode and a low power mode. The display device is configured to communicate commands to the sensor electronics unit using at least one of the multiple communication protocols. For example, the commands can include one or more commands that, when received by the sensor electronics unit, cause the sensor electronics unit to switch from a low power mode, such as a storage mode, to a normal power mode and / or wirelessly connect to the display device using a communication protocol different from the communication protocol used to communicate the command. Alternatively, the sensor electronics unit can switch from a normal power mode to a low power mode and / or terminate a connection for communication with the display device using the first communication protocol in response to a command communicated using the second communication protocol. The sensor electronics unit can communicate data indicative of an analyte level, such as analyte measurement data or an estimated analyte value, to the display device using at least one of the multiple communication protocols, for example while operating in the normal power mode. In some of these embodiments, the display device is configured to process the analyte measurement data to calculate an estimated analyte value.

[0013] In other embodiments, the analyte monitoring system includes an analyte sensor for measuring an analyte level and communicatively coupled to a sensor electronics unit. The sensor electronics unit is configured to receive analyte measurement data from the sensor and can be further configured to process the data to calculate an estimated analyte value based on the measurement data. The sensor electronics unit is also configured to communicate with the display device using multiple communication protocols. The sensor electronics unit can communicate the analyte measurement data or the estimated analyte value to the display device using a first communication protocol. In some of these embodiments, the display device is configured to process the analyte measurement data to calculate the estimated analyte value. The display device is also configured to communicate commands to the sensor electronics unit using a second communication protocol. For example, when the sensor electronics unit receives a command, the sensor electronics unit can stop making analyte measurements and can also stop transmitting the analyte measurement data or the estimated analyte value.

[0014] In some embodiments, an analyte level monitoring system is provided that includes an analyte sensor for measuring an analyte level and is communicatively coupled to a sensor electronics unit. The sensor electronics unit is configured to receive analyte measurement data from the sensor and can be further configured to process the data to calculate an estimated analyte value based on the measurement data. The sensor electronics unit is also configured to communicate with the display device using a plurality of communication protocols. The sensor electronics unit can communicate the analyte measurement data or the estimated analyte value to the display device at a predefined time using a first communication protocol. The sensor electronics unit can be further configured to communicate the analyte measurement data or the estimated analyte value to the display device from just prior to the predefined time using a second communication protocol. In some of these embodiments, the display device is configured to process the analyte measurement data to calculate an estimated analyte value.

[0015] In other embodiments, the analyte monitoring system includes an analyte sensor for measuring an analyte level and communicatively coupled to a sensor electronics unit. The sensor electronics unit is configured to receive analyte measurement data from the sensor and can be further configured to process the data to calculate an estimated analyte value based on the measurement data. The sensor electronics unit is also configured to communicate with the display device using multiple communication protocols. The sensor electronics unit can communicate the analyte measurement data or the estimated analyte value to the display device using a first communication protocol. In some of these embodiments, the display device is configured to process the analyte measurement data to calculate the estimated analyte value. The display device is also configured to communicate commands to the sensor electronics unit using a second communication protocol. For example, the commands can include one or more instructions that, when received by the sensor electronics unit, cause the sensor electronics unit to transmit the analyte measurement data or the estimated analyte value using the first communication protocol in response to a data request command sent using the second communication protocol. Alternatively, a portion of the analyte data or values ​​may be communicated using a first communication protocol and another portion of the analyte data or values ​​may be communicated using a different communication protocol.

[0016] In some implementations, one action can be a calibration action, where the display device sends commands / requests and / or data using the second communication protocol to transmit calibration data to the sensor electronics unit to calibrate the sensor electronics unit. This calibration data can include data obtained by a user through a finger prick and entered into the display device. The calibration data can be used by the sensor electronics unit to calibrate its calibration function that converts raw analyte sensor measurements (e.g., current, voltage, resistance, gate logic, etc.) into data indicative of an analyte measurement, such as an estimated glucose value ("EGV"), an estimated blood glucose level, a blood glucose level, and / or any other analyte measurement or estimate of an analyte measurement.

[0017] In some implementations, one action can be a clone action, and the display device can send a command / request and / or data to clone the sensor electronics unit using a second communication protocol. For example, but not limited to, two sensor electronics units can be used in a clone action. The display device can send a command / request to a first sensor electronics unit using the second communication protocol and send some or all of the stored data of the first sensor electronics unit (e.g., whitelist, bonding list, calibration data, analyte measurements, raw sensor measurements, etc.) to the display device over the first or second communication protocol. The display device can then initiate a transfer of data acquired from the first sensor electronics unit to the second sensor electronics unit using the second communication protocol.

[0018] In some implementations, one action can be a data retrieval action, and the display device can transmit a command / request and / or data using the second communication protocol that causes the sensor electronics unit to transmit data to the display device using the first communication protocol and / or the second communication protocol. For example, but not limited to, an NFC-enabled or RFID-enabled display device can modify the establishment of a normal communication, such as a scheduled communication or a communication according to a specific timing, as described later in this disclosure with reference to FIGS. 7A-E and elsewhere throughout this disclosure. For example, but not limited to, a user may want the sensor electronics unit to transmit sensor information prior to a scheduled transmission. This transmission may be due to the user / host sensing symptoms of a hypoglycemic condition, or the user may want a backlog of sensor data to be transmitted to the display device in a bulk transfer.

[0019] In some implementations, one action is a set white / bonding list action, where the display device transmits commands / requests and / or data using the second communication protocol to set, adjust, and / or manipulate a whitelist or bonding list of the first communication protocol in the sensor electronics unit. Whitelists and bonding lists are discussed later in this disclosure with reference to FIGS. 5C, 6A-B, 9A-F, and elsewhere throughout this disclosure. This action can include adding the display device to a whitelist or bonding list, removing the display device from a whitelist or bonding list, and / or reorganizing the whitelist and / or bonding list. In some implementations, adding a display device can transmit command(s) over the second communication protocol to add the display device to the whitelist of the sensor electronics unit of the first communication protocol, where the command(s) can also specify the position of the display device and other display devices on the whitelist, and can shift other display devices out of the whitelist.

[0020] In some implementations, one action can be starting or stopping a sensor session, and the display device uses the second communications protocol to send commands / requests and / or data to the sensor electronics unit to start or stop sensor measurements and / or transmissions.

[0021] In some implementations, data and / or commands can be transmitted using multiple communication protocols (e.g., first and second communication protocols). For example, but not limited to, certain types of communications can be transmitted over a first communication protocol and certain types of communications can be transmitted over a second communication protocol. By way of example, but not limited to, all commands can be transmitted over a second communication protocol and all data can be transmitted over the first communication protocol. In some implementations, communications can be split between a first communication protocol and a second communication protocol. For example, but not limited to, encrypted data / information can be transmitted over one communication protocol while decryption keys and / or other security information can be transmitted over another communication protocol such that the display device can read communications from the sensor electronics unit using both communication protocols. In some implementations, communications can be split between multiple communication protocols such that a complete message includes data / information from multiple communication protocols.

[0022] In some implementations, the sensor electronics unit can adjust the communication protocol based on the remaining battery power. For example, but not limited to, a second communication protocol can be used to recover data from a powered-down and / or low-powered sensor electronics unit. In some cases, the sensor electronics unit can cease data measurement and / or transmission when the battery power drops below a predetermined threshold. One or more communication protocols (e.g., the second communication protocol) can then be used to power the sensor electronics module and recover data stored on the sensor electronics module. In some cases, the sensor electronics unit can load data onto a passive tag when its battery power drops below a predetermined threshold.

[0023] In some cases, the display device can use NFC to power and / or initiate communication from the sensor electronics unit to the display device via wireless transmission (e.g., using BLUETOOTH or BLE wireless protocols). Such may be desirable when the sensor electronics unit is low on battery or has run out of battery. This can be used by health care workers to process patient data and / or by any user to pull data from a near-running or out-of-power sensor electronics unit or in the event of a sensor electronics unit failure. [Brief description of the drawings]

[0024] The disclosed aspects are described below in conjunction with the accompanying drawings, which are provided to illustrate and not limit the disclosed aspects, and the same symbols represent the same elements. Details of one or more implementations of the subject matter described herein are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. Please note that the relevant dimensions in the following drawings may not be drawn to scale.

[0025] [Figure 1A] FIG. 1 depicts an exemplary continuous analyte monitoring system having a sensor electronics unit, a sensor, and multiple display devices that may be connected to the sensor electronics unit. [Figure 1B] 1 is an exemplary flow chart illustrating an exemplary initiation of a sensor electronics unit from manufacture to use by a user. [Figure 1C] FIG. 2 illustrates an example display device and sensor electronics unit communicating over two different communication channels. [Figure 2A] FIG. 1 is a block diagram of an exemplary system in which a sensor electronics unit is communicatively coupled to multiple display devices using multiple communication channels. [Figure 2B]FIG. 1 illustrates an example system in which an example sensor electronics unit is communicatively coupled to two example display devices. [Diagram 3] FIG. 2 is a functional block diagram of an exemplary sensor electronics unit. [Figure 4A] FIG. 2 is a functional block diagram of an exemplary display device. [Figure 4B] 1 illustrates an example advertising / connection sequence between an example sensor electronics unit and an example display device. [Figure 5A] FIG. 1 illustrates example ranges of example communication protocols for an example sensor electronics unit, with each communication protocol having a different range. [Figure 5B] FIG. 1 illustrates example ranges of example communication protocols for an example display device, with each communication protocol having a different range. [Figure 5C] FIG. 2 illustrates an example functional block diagram illustrating example functional units of an example display device. [Figure 6A] FIG. 1 illustrates an example interface that allows a user to select NFC capabilities from an example display device. [Figure 6B] FIG. 13 illustrates an example interface for performing an example action cue action through NFC. [Figure 6C] FIG. 13 is an example timing diagram for waking an example sensor electronics unit from a low power mode using an RF field communication protocol. [Figure 6D] 1 is an exemplary flow chart illustrating a process for waking an exemplary sensor electronics unit using an RF field communication protocol. [Figure 6E] FIG. 13 is an example timing diagram of an example sensor electronics unit entering a low power mode. [Figure 7A] FIG. 10 is an example timing diagram of an example first communication protocol for an example sensor electronics unit. [Figure 7B]7B is an example timing diagram of an example sensor electronics unit illustrating signal processing that may occur during communication of the first communication protocol of FIG. 7A. [Figure 7C] FIG. 7C illustrates an example transmission from an example sensor electronics unit using a second communication protocol to initiate communication using the first communication protocol from the example timing diagram of FIG. 7B. [Figure 7D] 11 is an example timing diagram illustrating a transmission over a second communication protocol to stop an example sensor session. [Figure 7E] FIG. 11 is an example timing diagram illustrating the timing of transmissions over a second communication protocol to initiate a sensor session. [Figure 8] 1 is an exemplary flowchart illustrating how one communication protocol can be used to facilitate pairing for communication using another communication protocol. [Figure 9A] FIG. 1 illustrates an example whitelist and an example bonding list that can be used to pair an example sensor electronics unit and an example display device by using two or more communication protocols. [Figure 9B] FIG. 9B illustrates a number of exemplary display devices connecting to an exemplary sensor electronics unit using a second communication protocol, as reflected in the exemplary whitelist and exemplary bonding list illustrated in FIG. 9A. [Figure 9C] FIG. 13 illustrates an example communication protocol whitelist and an example bonding list that are updated when an example sensor electronics unit and an example display device are unpaired using a second communication protocol. [Figure 9D] FIG. 1 illustrates an example implementation in which a communication protocol can be used to add an example display device to an example whitelist of another communication protocol and remove a different example display device from that same example whitelist. [Figure 9E]FIG. 9C illustrates an example of reordering the example whitelist illustrated in FIG. 9B using a second communication protocol. [Figure 9F] FIG. 1 illustrates an example of using a second communication protocol to move an example display device on an example bonding list of a first communication protocol to an example white list of the first communication protocol. [Figure 9G] FIG. 10 illustrates a graph of an example sequential communication window for communication between an example sensor electronics unit and an example display device of the example whitelist of FIGS. 9A-F. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0026] Various aspects of the novel systems, devices, and methods disclosed herein are described more fully below with reference to the accompanying drawings. However, the disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout the disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will recognize that the scope of the disclosure is intended to cover all aspects of the novel systems, devices, and methods disclosed herein, whether implemented independently or in combination with any other aspects. For example, a device can be implemented or a method can be implemented using any number of aspects described herein. In addition, the scope of the disclosure is intended to cover such devices or methods practiced using other structures, functions, or structures and functions in addition to or other than the various aspects of the disclosure described herein. It should be understood that any aspect disclosed herein can be implemented by one or more elements of a claim.

[0027] Although specific embodiments are described herein, numerous variations and permutations of these embodiments are within the scope of the present disclosure. Although some benefits and advantages of the preferred embodiments are mentioned, the scope of the present disclosure is not intended to be limited to specific benefits, applications, and / or purposes. The detailed description and drawings are merely illustrative of the present disclosure, rather than limiting, and the scope of the present disclosure is defined by the appended claims and their equivalents.

[0028] As mentioned above, continuous monitoring of blood glucose levels, one example of an analyte (described in more detail below), can improve upon conventional monitoring systems and methods by improving comfort and convenience, as well as reducing the chance that a person's deteriorating or medically dangerous condition will go unnoticed. Accordingly, various implementations described herein are directed to systems and methods for continuous monitoring of an analyte and communication between a sensor electronics unit and a display device.

[0029] In some implementations, a system is provided for continuously measuring an analyte in a host, the system may include a continuous analyte sensor (and / or any other sensor) configured to measure a concentration of an analyte in a host substantially continuously, and a sensor electronics unit operatively and / or communicatively coupled to the continuous analyte sensor to receive the analyte concentration measurements and communicate the analyte measurements to a display device. In particular, the sensor electronics unit may include electronics configured to process process data and / or data streams associated at least in part with the analyte concentration measured by the continuous analyte sensor to generate sensor information including raw sensor data, transformed sensor data, and / or any other sensor data or data derived from the sensor electronics unit, such as predictive or trend data. The sensor electronics unit may be further configured to generate sensor information customized for a respective display device such that different display devices may receive sensor information modified for the different display devices for presentation to a host, a caregiver, or the like.

[0030] The communication between the sensor electronics unit and one or more display devices can be controlled via an advertising and communication protocol, including, for example, how often and / or how long the sensor electronics unit advertises to the display devices, the order in which the sensor electronics unit advertises to the display devices, etc. The sensor electronics unit can include a communication unit, such as a wireless transceiver, that operates according to the advertising and communication protocol to achieve such communication between the sensor electronics unit and one or more display devices. The control achieved by the advertising and connection protocol can be achieved by varying or adjusting variables or parameters that can affect the communication, such as, but not limited to, the timing and order of the communications.

[0031] As used herein, the term "analyte" is a broad term given its ordinary and customary meaning to those of skill in the art (and is not limited to any special or customized meaning), and further refers to, but is not limited to, a substance or chemical component in a biological fluid (e.g., blood, interstitial fluid, cerebrospinal fluid, lymphatic fluid, or urine) that can be analyzed. Analytes can include naturally occurring substances, man-made substances, metabolic substances, and / or reaction products. In some implementations, the analyte for measurement by the sensor head, devices, and methods is an analyte. However, other analytes are contemplated as well, including acarboxyprothrombin, acylcarnitines, adenine phosphoribosyltransferase, adenosine deaminase, albumin, alpha-fetoprotein, amino acid profile (arginine (Krebs cycle), histidine / urocanic acid, homocysteine, phenylalanine / tyrosine, tryptophan), andrenostenedione, antipyrine, arabinitol enantiomers, arginase, benzoylecgonine (cocaine), biotinidase, biopterin, C-reactive protein, carnitine, carnosinase, CD4, ceruloplasmin, chenodeoxycholic acid, chloroquine, cholesterol, cholinesterase, conjugated 1-beta hydroxycholic acid, cortisol, creatine kinase, creatine kinase MM isoforms. im, cyclosporine A, d-penicillamine, de-ethylchloroquine, dehydroepiandrosterone sulfate, DNA (acetylation 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's hereditary optic neuropathy, MCAD, RNA, PKU, Plasmodium vivax, sex differentiation, 21-deoxycortisol), desbutylhalofantrine, dihydropteridine reductase, diphtheria / tetanus antitoxin, erythrocyte arginase, erythrocyte protoporphyrin, esterase D, fatty acids / acylglycines,Free β-human chorionic gonadotropin, free erythrocyte porphyrin, free thyroxine (FT4), free tri-iodothyronine (FT3), fumarylacetoacetase, galactose / gal-1-phosphate, galactose-1-phosphate uridyltransferase, gentamicin, analyte-6-phosphate dehydrogenase, glutathione, glutathione peroxidase, glycocholate, glycosylated hemoglobin, halofantrine, hemoglobin mutants, hexosaminidase A, human erythrocyte carbonic anhydrase I, 17-α-hydroxyprogesterone, hypoxanthine phosphoribosyltransferase , immunoreactivity, trypsin, lactate, lead, lipoproteins ((a), B / A-1, β), lysozyme, mefloquine, netilmicin, phenobarbitone, phenytoin, phytanic acid / pristanic acid, progesterone, prolactin, prolidase, purine nucleoside phosphorylase, kinin, inverted tri-iodothyronine (rT3), selenium, serum pancreatic lipase, sisomicin, somatomedin C, specific antibodies (adenovirus, antinuclear antibody, anti-zeta antibody, arbovirus, Aujeszky's disease virus, dengue virus, Dracaena fasciata, Echinococcus granulosus, Entamoeba histolytica, enterovirus, Giardia lamblia (giardia duodenalisa, Helicobacter pylori, Hepatitis B virus, Herpes virus, HIV-1, IgE (atopic disease), Influenza virus, Leishmania donovani, Leptospira, Measles / Mumps / Rubella, Mycobacterium leprae, Mycoplasma pneumoniae, Myoglobin, Onchocerca volvulus, Parainfluenza virus, Plasmodium falciparum, Poliovirus, Pseudomonas aeruginosa, Respiratory syncytial virus, Rickettsia (scrub typhus), Schistosoma mansoni, Toxoplasma gondii, Trepenoma pallidium, Trypanosoma cruzi / Langer, Vesicular stomatitis virus virus), Wuchereria bancrofti, Yellow fever virus), Specific antigens (Hepatitis B virus, HIV-1), Succinylacetone sulfadoxine, Theophylline, Thyrotropin (TSH), Thyroxine (T4), Thyroxine-binding globulin, Trace elements, Transferrin, UDP-galactose-4-epimerase, Urea, Uroporphyrinogen I synthase,Examples of analytes that may be present in the body include, but are not limited to, vitamin A, white blood cells, and zinc protoporphyrin. Salts, sugars, proteins, lipids, vitamins, and hormones that are naturally present in blood or interstitial fluids may also constitute analytes in certain implementations. Analytes may be naturally present in biological fluids, such as metabolites, hormones, antigens, antibodies, and the like. Alternatively, analytes may be introduced into the body, such as contrast agents for imaging, radioisotopes, chemical agents, fluorocarbon-based synthetic blood, or drugs or pharmaceutical compositions, such as insulin, ethanol, cannabis (marijuana, tetrahydrocannabinol, hashish), inhalants (nitrous oxide, amyl nitrite, butyl nitrite, chlorinated hydrocarbons, hydrocarbons), cocaine (crack cocaine), stimulants (amphetamines, methamphetamines, Ritalin, Cylert, Preludin, Didrex, PreState, Voranil, Sandrex, Plegine), depressants (barbiturates, methaqualone, Valiu Drugs and pharmaceutical compositions that may be used to assess the efficacy of analytes include, but are not limited to, tranquilizers such as benzodiazepines, benzodiazepines, benzocaine, benzodiazepines, benzoyl peroxide ... Analytes such as neurochemicals and other chemicals produced in the body, such as ascorbic acid, uric acid, dopamine, noradrenaline, 3-methoxytyramine (3MT), 3,4-dihydroxyphenylacetic acid (DOPAC), homovanillic acid (HVA), 5-hydroxytryptamine (5HT), and 5-hydroxyindoleacetic acid (FHIAA), can also be analyzed.

[0032] The sensor electronics unit can include electronics configured to communicate and store data from a user's sensors (e.g., analyte sensors). The sensor electronics unit can be connected to a display device (e.g., a mobile device, a specialized medical receiver) or any of the other display devices described in this disclosure. In either case, the display device can be a device that the user can use to monitor the sensor measurements.

[0033] In some implementations, the sensor electronics unit can be configured to retrieve, advertise to, and / or attempt to wirelessly communicate with a list of display devices (e.g., a whitelist). This list can be stored in memory and can include display device information that reflects, at least in part, the types of devices that are permitted to pair and / or associate with the display devices or sensor electronics unit. For example, but not limited to, in some cases, only display devices or device types (e.g., models, makes, or classifications of devices (e.g., specialized receivers, mobile devices, etc.)) on the whitelist can be connected to the sensor electronics unit. Connection requests from display devices that are not on the whitelist or whose types are not on the whitelist can be ignored or rejected, and the display devices can not be allowed to connect to the sensor electronics unit.

[0034] In this example, the display devices on the whitelist can respond to an advertising signal transmitted by the sensor electronics unit. When the sensor electronics unit receives this response, it can update the whitelist with an identifier indicative of the display device. In some implementations, the display device can be removed from the whitelist after some predetermined amount of inactivity, e.g., after there is no communication between the sensor electronics unit and the display device. Another list (e.g., a bonding list) can be utilized to maintain a list of bonding or pairing information of display devices that can be paired with the sensor electronics unit. By way of example and not limitation, depending on the pairing or bonding / inclusion in the whitelist, the display device identifier can also be stored in the bonding list. Thus, the sensor electronics unit can pull the pairing information from the bonding list and therefore avoid re-pairing the display device to the sensor electronics unit when utilizing the bonding list. For example and not limitation, the identifier of a display device can be stored in the bonding list even if the display device is removed from the whitelist (e.g., due to being inactive for some predetermined amount of time, an explicit removal, and / or pairing of a new device). In this way, when the sensor electronics unit receives a response to an advertising signal from the display device, it can access the bonding list to check whether the display device was previously bonded to the sensor electronics unit, and if so, a data connection can be established without engaging in authentication.

[0035] In some implementations, the searches and / or attempts for wireless communication may occur in a predetermined and / or programmable order (e.g., gradually and / or incrementally). For example, but not limited to, if an attempt to communicate with and / or alarm a first display device fails, this failure triggers an attempt to communicate with and / or alarm a second display device. Note that the sensor electronics unit may not be tied to a single display device. Rather, the sensor electronics unit may be configured to communicate with multiple different display devices directly, systematically, simultaneously (e.g., via broadcasting), regularly, periodically, randomly, on-demand, in response to a query, based on an alert or alarm, and / or the like.

[0036] The sensor information (e.g., data, measurements, etc.) can include processed and / or transformed sensor information that does not require processing by the display device prior to displaying the sensor information. However, some display devices can include software including display instructions configured to enable the sensor information to be displayed thereon (e.g., software programming including instructions configured to display the sensor information and, optionally, to query the sensor electronics unit to obtain the sensor information). In some implementations, the display device is programmed with the display instructions at the manufacturer and can also include security and / or authentication to avoid theft of the display device. In some implementations, the display device is configured to show the sensor information via a downloadable program (e.g., a downloadable Java Script™ over the Internet and / or a mobile application downloaded from an entity that creates and / or owns and / or licenses the app and / or from an app store such as APPLE, INC. or GOOGLE INC., or from other companies), such that any display device that supports downloading of programs (e.g., without limitation, any display device that supports Java™ applets or mobile applications) can be configured to display the displayable sensor information (e.g., mobile devices, smartphones, tablets, personal digital assistants, personal computers, and the like).

[0037] In some implementations, a particular display device may wirelessly communicate directly with the sensor electronics unit, but may include intermediate network hardware, firmware, and / or software in the direct wireless communication. In some implementations, a repeater (e.g., a BLUETOOTH or BLE repeater) may be used to retransmit the transmitted sensor information to a location farther than the immediate range of the telemetry module of the sensor electronics unit. In some implementations, a display device (e.g., a BLUETOOTH or BLE display device) may be used to retransmit the transmitted sensor information to the display device, possibly in a different format, such as a text message. In certain implementations, the sensor electronics unit transmits sensor information to one or more display devices, and the transmitted sensor information from the sensor electronics unit is received by the display device without intermediate processing of the sensor information.

[0038] In some implementations, the one or more display devices are configured to query the sensor electronics unit for sensor information, and the display device requests the sensor information from the sensor electronics unit in an on-demand manner, such as, but not limited to, in response to the query. In some implementations, the sensor electronics unit can be configured to transmit sensor information to the one or more display devices periodically, systematically, regularly, irregularly, or non-periodically (e.g., every 1, 2, 5, or 10 minutes or more). In some implementations, the sensor electronics unit can be configured to transmit data packages associated with triggered alerts (e.g., triggered by one or more alert conditions). However, any combination of the data transmission statuses described above can be implemented by any combination of paired sensor electronics units and display device(s). For example, but not limited to, the one or more display devices can be configured to query a database of the sensor electronics unit and receive alarm information triggered by meeting one or more alarm conditions. Additionally, the sensor electronics unit can be configured to transmit the sensor information to one or more display devices (e.g., the same or different display devices, as described in the previous examples), where the display devices function differently with respect to how they obtain the sensor information.

[0039] In some implementations, as described in more detail below, the display device can be configured to query / request data stored in the memory of the sensor electronics unit for certain types of data content, including directly querying a database in the memory of the sensor electronics unit and / or requesting a configured or configurable package of data content therefrom; i.e., data stored in the sensor electronics unit can be configured, queried, and / or pre-packaged based on the display device with which the sensor electronics unit is communicating. In some additional or alternative implementations, the sensor electronics unit can generate sensor information based on the sensor electronics unit's knowledge that the display device is the one receiving a particular transmission. Additionally, some display devices can obtain calibration information and wirelessly transmit the calibration information to the sensor electronics unit, such as through manual entry of calibration information, automatic delivery of calibration information, and / or an integrated reference analyte monitor built into the display device. U.S. Patent Application Publication Nos. 2006 / 0222566, 2007 / 0203966, 2007 / 0108245, and 2005 / 0154271 (all of which are incorporated by reference in their entirety into this specification) describe systems and methods for providing an integrated reference analyte monitor incorporated into a display device and / or other calibration methods that can be implemented by the implementations disclosed herein.

[0040] In general, a number of display devices (e.g., custom analyte monitoring devices, cell phones, tablets, smart watches, reference analyte monitors, drug delivery devices, medical devices, and personal computers) can be configured to wirelessly communicate with the sensor electronics unit. The one or more display devices can be configured to show at least some of the sensor information wirelessly communicated by the sensor electronics unit. The sensor information can include, for example, sensor data such as raw and / or converted sensor data, such as, but not limited to, analyte concentration values, rate of change information, trend information, alert information, sensor diagnostic information, calibration information, temperature readings, or non-visual information such as sound, etc.

[0041] The features described throughout this disclosure have several advantages over currently available systems and methods. These advantages are generally described below. For example, there is a need in the art for improved systems and methods of communication using a communication protocol between a sensor electronics unit and a display device. In some instances, the use of a communication protocol may consume excessive power, processor capabilities, and / or other resources of the CGM system. This challenge may be exacerbated by repetitive pairing, synchronization, and / or handshaking procedures that may be used in some communication protocols, such as BLUETOOTH or BLE. Thus, there is a need for improved communication that efficiently utilizes the power, processor capabilities, and / or other resources of the CGM system.

[0042] In some cases, the repetitive pairing, synchronization, and / or handshaking procedures of the CGM system may also result in excessive communication traffic. This communication traffic may burden the network and / or drain network resources (e.g., communication channels, data lines, power, processing power, etc.), such as by tying up communication channels and / or data lines, causing interference, power consumption, processor time utilization, etc. In some cases, the excessive communication traffic may lead to network slowdowns, network failures, and / or increased costs of operating the network, such as more energy costs, or additional hardware utilization (e.g., processors, communication lines, cooling, etc.). Thus, a need exists for improved communication of CGM systems.

[0043] Specifically, because certain CGM systems perform repetitive handshaking / authentication to exchange data (e.g., EGV data) with several protocols (e.g., wireless communication such as BLUETOOTH), these CGM systems may strain the battery life of the sensor electronics unit. In addition, because multiple display devices may compete to connect with the sensor electronics unit (e.g., during the same advertisement window), the repetitive handshaking / authentication may lead to undesirable interference. This interference may lead to connection failures and ultimately to undesirable data drops. Thus, utilizing a second communication protocol (e.g., RF fields such as NFC or RFID) allows the CGM system to more efficiently pair the sensor electronics unit to the display device on demand.

[0044] In some cases, interaction using a communication protocol between the sensor electronics unit and the display device may be unintuitive and / or cumbersome for a user. For example, but not limited to, a user may navigate through multiple menus and configure multiple devices to pair and / or unpair the sensor electronics unit, the display device, and / or other devices utilizing the communication protocol. As another non-limiting example, an initialization protocol in which the sensor electronics unit and / or the display device are calibrated and / or configured may require navigation of multiple menus that may be cumbersome for a user. Having too many steps may impair the user experience and / or may prevent a user from effectively using the CGM system and / or adhering to their medical regimen. Thus, there is a need for improved communication of the CGM system to enable enhanced usability.

[0045] In some cases, user authentication of a display device for a transceiver can be time consuming and / or cumbersome for a user. However, such authentication can provide security to a user by preventing unauthorized devices from receiving and / or sending data and / or commands to the sensor electronics unit. Having too many authentication scheme steps can impair the user experience and / or further prevent a user from effectively using the system and / or adhering to their medical regimen. Thus, there is a need for improved user authentication between a display device and a sensor electronics unit.

[0046] In some cases, communication over a communication protocol may cause problems and / or otherwise lead to security issues. For example, but not limited to, a device may steal the authentication of a display device and / or communicate to the sensor electronics unit as a display device. Such security issues may allow unauthorized persons to receive private information and / or control a user's CGM system, potentially causing problems. Thus, there is a need for advanced communication systems and / or methods to improve security.

[0047] In some instances, some communication protocols, such as BLUETOOTH or BLE, use energy from the sensor electronics unit to transmit messages. As a result, it may be difficult to obtain data from the sensor electronics unit when the sensor electronics unit runs out of power (e.g., the sensor electronics unit's battery runs out) or when a sensor electronics unit failure / failure (e.g., wireless protocol error) occurs that may prevent data transfer over wireless communication, such as BLUETOOTH or BLE. Retrieving such data may be desirable when a user has not previously accessed data from the sensor electronics (e.g., data was not transmitted to the user's display device) and / or when an additional copy is desired. Healthcare workers may also likewise want to download this data to provide appropriate treatment to the patient. Thus, a need exists for systems and methods for extracting data from the sensor electronics unit when the sensor electronics unit no longer has the energy to power some communication protocols or when it fails.

[0048] In some cases, the communication may be at predefined time intervals. For example, the sensor electronics unit may only communicate to the display device every 5, 10, 15, 20 minutes, or any other predefined period. As another example, the sensor electronics unit may only clear a device from the whitelist every 5, 10, 15, 20 minutes, or any other predefined period to allow a new device to connect. A user may wish to pair a display device with a sensor electronics unit or send / receive communications between a display device and a sensor electronics unit outside of the predefined period. Thus, there is a need for systems and methods that allow communication users to pair and / or communicate on demand. These and further advantages will be readily apparent from the implementations disclosed herein.

[0049] FIG. 1A is a diagram depicting an exemplary continuous analyte monitoring system 1 having a sensor electronics unit 6, a continuous analyte sensor 8, and a number of display devices 20A-E that can be connected to the sensor electronics unit 6. The continuous analyte monitoring system 1 can include an analyte sensor system 4 and display devices 20A-E. The analyte sensor system 4 can be operatively connected to a host 2 and a number of display devices 20A-E in accordance with certain aspects of the present disclosure. In some cases, the display devices 20A-E can run software applications, such as mobile applications (e.g., mobile applications downloaded from an entity that creates and / or owns and / or licenses the app, and / or from an app store such as by APPLE, INC. or GOOGLE INC., or otherwise), also referred to as apps, that perform functions and / or have structures described throughout this disclosure.

[0050] Alternatively, or in addition to being a display device, the display device 20E can be a drug delivery device that can act in concert with the analyte sensor system 4 to deliver a drug to the host 2. By way of example and not limitation, the display device 20E can be an insulin delivery pump, an insulin delivery pen, or other device for drug delivery. The analyte sensor system 4 can include a sensor electronics unit 6 and a continuous analyte sensor 8 that can be associated with the sensor electronics unit 6. The sensor electronics unit 6 can directly wirelessly communicate with one or more of the multiple display devices 20A-E via wireless communication signals or wired communication signals. As discussed in more detail below, the display devices 20A-E can also communicate between each other and / or through each other to the analyte sensor system 4. The wireless communication signals from the analyte sensor system 4 to the display devices 20A-E can include uplink signals 12. The wireless communication signals from the display devices 20A-E to the analyte sensor system 4 can include downlink signals 14. The wireless communication signals can also be between two or more of the display devices 20A-E. By way of example, cross link signal 16 may be a signal communication between display device 20A and display device 20C.

[0051] The sensor electronics unit 6 can include sensor electronics configured to process sensor information and / or transmit and / or receive sensor data to one or more display devices 20A-E. Although FIG. 1A illustrates display devices 20A-E, as discussed in this disclosure with reference to FIG. 2A, the continuous analyte monitoring system 1 can have any number of display devices 20A-N. Display device 20, as used throughout this disclosure, represents any one of display devices 20A-N. In certain implementations, the sensor electronics unit 6 can include electronic circuitry associated with measuring and processing data from the continuous analyte sensor 8, including predictive algorithms associated with processing and / or calibrating the data of the continuous analyte sensor. The sensor electronics unit 6 can be integral (e.g., removably attached) to the continuous analyte sensor 8 or can be removable, achieving a physical connection therebetween. The sensor electronics unit 6 can include hardware, firmware, and / or software that enables analyte level measurement. For example, without limitation, the sensor electronics unit 6 may include a potentiostat, a power supply for providing power to the continuous analyte sensor 8, other components useful for signal processing and data storage, and a telemetry module for transmitting data from itself to one or more display devices 20A-N. The electronics may be affixed 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.Examples of systems and methods for processing sensor analyte data are described in more detail herein, as well as in U.S. Pat. Nos. 7,310,544 and 6,931,327, and U.S. Patent Application Publication Nos. 2005 / 0043598, 2007 / 0032706, 2007 / 0016381, 2008 / 0033254, 2005 / 0203360, 2005 / 0154271, 2005 / 0192557, 2006 / 0222566, 2007 / 0203966, and 2007 / 0108245, all of which are incorporated by reference in their entireties for all purposes.

[0052] The display devices 20A-N can be configured to display, alarm, and / or base drug delivery on sensor information transmitted by the sensor electronics unit 6 (e.g., in a data package transmitted to one or more of the display devices 20A-N based on their respective preferences). Each of the display devices 20A-N can include a display, such as a touchscreen display, for displaying the sensor information to a user (e.g., the host 2 or a caregiver / healthcare professional) and / or receiving input from a user. In some implementations, the display devices 20A-N can include other types of user interfaces, such as a voice user interface, instead of or in addition to a touchscreen display, for communicating the sensor information to a user of the display device 20A-N and / or receiving user input. In some implementations, one, some, or all of the display devices 20A-N may be configured to display or otherwise communicate sensor information as it is communicated from the sensor electronics unit 6 (e.g., in a data package transmitted to the respective display device 20A-N) without any additional predictive processing required for calibration and real-time display of the sensor information.

[0053] In some implementations, the display device 20A can be a specialized medical receiver specially designed to display a particular type of displayable sensor information associated with the analyte value (e.g., numerical value and direction, such as an increasing or decreasing trend) received from the sensor electronics unit 6. In some implementations, the display device 20C can be a handheld device, such as a mobile phone based on the Android or iOS operating system, a palmtop computer, and the like, which can have a relatively large display and can be configured to display a graphical representation of continuous sensor data (e.g., including current and / or historical data). Other display devices can include other handheld devices, such as tablets (e.g., display device 20D), smart watches (e.g., display 20B), drug delivery devices (e.g., display device 20E), blood glucose meters, and / or desktop or laptop computers.

[0054] As alluded to above, different display devices 20A-N can provide different user interfaces, such that the content of the data packages (e.g., the amount, format, and / or type of data displayed, alarms, and the like) can be customized (e.g., programmed differently by the manufacturer and / or by the user) for each particular display device and / or type of display device. Thus, in some implementations, one or more of the display devices 20A-N can wirelessly communicate directly or indirectly with the sensor electronics unit 6 to enable multiple different types and / or levels of display and / or functionality associated with the sensor information, as described in more detail elsewhere herein.

[0055] The continuous analyte sensor 8 can be, for example, without limitation, a subcutaneous, transcutaneous (e.g., transdermal), or intravascular device. In some implementations, the continuous analyte sensor 8 can analyze multiple intermittent blood samples, but the continuous analyte sensor 8 can be configured to use any analyte measurement method, including enzymatic, chemical, physical, electrochemical, spectrophotometric, polarimetric, calorimetric, iontophoretic, radiometric, immunochemical, and the like.

[0056] The continuous analyte sensor 8 can provide a data stream indicative of the concentration of the analyte measured in the host 2 using any known method, including invasive, minimally invasive, and non-invasive sensing techniques (e.g., fluorescence monitoring). In some implementations, this data stream can typically be a raw data signal, which can be converted into a calibrated and / or filtered data stream used to provide a useful value of the measured analyte to a user, such as the host 2 or a caregiver (e.g., a parent, relative, guardian, teacher, doctor, nurse, and / or any other individual interested in the health of the host 2). It should be understood that the devices and methods described herein can be applied to any device capable of detecting the concentration of an analyte and providing an output signal representative of the concentration of the analyte.

[0057] In some implementations, the continuous analyte sensor 8 can measure the glucose concentration of the host 2, one of which is described below utilizing an implantable continuous glucose sensor. For example, without limitation, the continuous analyte sensor 8 can be an implantable glucose sensor, such as those described with reference to U.S. Pat. No. 6,001,067 and U.S. Patent Application Publication No. 2005 / 0027463-A1. In another implementation, the continuous analyte sensor 8 can be a transcutaneous glucose sensor, such as those described with reference to U.S. Patent Application Publication No. 2006 / 0020187-A1. In yet other implementations, the continuous analyte sensor 8 can be configured to be implanted within a host's blood vessel or extravascularly as described in U.S. Patent Application Publication No. 2007 / 0027385-A1, co-pending U.S. Patent Application Publication No. 2008 / 0119703-A1, filed October 4, 2006, co-pending U.S. Patent Application Publication No. 2008 / 0108942-A1, filed March 26, 2007, and co-pending U.S. Patent Application No. 2007 / 0197890-A1, filed February 14, 2007. In an alternative implementation, the continuous analyte sensor 8 can comprise a transcutaneous sensor, for example, as described in U.S. Patent No. 6,565,509 to Say et al. In another alternative implementation, the continuous analyte sensor 8 can comprise a subcutaneous sensor, such as described with reference to U.S. Pat. No. 6,579,690 to Bonnecaze et al. or U.S. Pat. No. 6,484,046 to Say et al. In another alternative implementation, the continuous analyte sensor 8 can comprise a refillable subcutaneous sensor, such as described with reference to U.S. Pat. No. 6,512,939 to Colvin et al. In another alternative implementation, the continuous analyte sensor 8 can comprise an intravascular sensor, such as described with reference to U.S. Pat. No. 6,477,395 to Schulman et al. In another alternative implementation, the continuous analyte sensor 8 can comprise an intravascular sensor, such as described with reference to U.S. Pat. No. 6,424,847 to Mastrototaro et al.Each of the above mentioned patents and patent applications is incorporated herein by reference.

[0058] FIG. 1B illustrates an exemplary flow chart showing an exemplary initiation of the sensor electronics unit 6 from manufacture to use by a user. The sensor electronics unit 6 can have a predetermined life cycle that includes an exemplary method 50. At block 52, the sensor electronics unit 6 can be manufactured in a factory setting. In some cases, manufacturing can include circuit fabrication, assembly, testing, calibration, etc. At block 54, once the sensor electronics unit 6 is manufactured, it can then be placed into a shelf mode and / or any low power mode, which will be further described with reference to FIG. 6E and elsewhere throughout this disclosure. This shelf mode and / or any low power mode can allow the sensor electronics unit 6 to consume less power before being used. At block 56, the sensor electronics unit 6 can be shipped to a user while in shelf mode. As a non-limiting illustrative example, the sensor electronics unit 6 can be in shelf mode when shipped, when located in a warehouse, and / or before being activated by a user. There are other instances when the sensor electronics unit 6 may be placed into shelf mode and / or any low power mode, which are described throughout this disclosure.

[0059] At block 58, the sensor electronics unit 6 may be powered up and woken from shelf mode and / or any low power mode when desired for use. For example, but not limited to, in some cases, the sensor electronics unit 6 may periodically check whether it is connected to the continuous analyte sensor 8. This periodic check may include sensing the current and / or voltage across the electrodes. In some cases, by way of illustrative example and not limited to, the periodic check may occur at a predetermined time interval, such as every 5 minutes, every 10 minutes, every 15 minutes, or any desired number of minutes, and / or after a predetermined number of counts. The sensor electronics unit 6 may be woken up if there is a change in the current and / or voltage (e.g., an increase in the current and / or voltage and / or a change over a certain period and / or count) that is at least partially indicative of a connection to the continuous analyte sensor 8. In certain cases, predetermined thresholds for the current, voltage, counts, time, etc. may be used to wake up the sensor electronics unit 6 when the current, voltage, counts, time, etc. exceed (or, when appropriate, fall below) the predetermined threshold. In some implementations, if the sensor electronics unit 6 has an accelerometer, wake-up can occur very quickly. For example, but not limited to, while in shelf mode, the sensor electronics unit 6 can check the current every 5 minutes or at longer intervals. If the accelerometer detects motion, the sensor electronics unit 6 can be woken up and the interval for checking the current can be reduced. If the current remains below the wake-up threshold and no motion has been detected for a certain period of time, the sensor electronics unit 6 can be returned to shelf mode. Advantageously, the accelerometer can facilitate a very short warm-up time without impacting shelf life. Motion can indicate a user preparing to use the sensor electronics unit 6.

[0060] At block 60, after waking up the sensor electronics unit 6, the continuous analyte sensor 8 of the sensor electronics unit 6 may be initialized. The initialization may be part of a warm-up period during which the sensor electronics unit 6 and / or the continuous analyte sensor 8 execute software, calibrate, run diagnostics, etc.

[0061] At block 62, the sensor electronics unit 6 may be paired with one or more display devices 20A-N. To pair with a display device, the sensor electronics unit 6 may first advertise (e.g., broadcast a connection to the display device) to pair with the display device. Advertising by the sensor electronics unit 6 may include using a communication protocol such as, but not limited to, BLUETOOTH (e.g., BLUETOOTH Low Energy ("BLE"), Classic BLUETOOTH, Dual-mode BLUETOOTH, etc.), IBEACONS, ZIGBEE, Wi-Fi, inductive wireless data transmission, radio transmission, radio frequency identification ("RFID"), near field communication ("NFC"), and / or any other communication protocol as desired and / or mentioned in this disclosure. As used herein, any reference to BLUETOOTH® may include BLE, Classic BLUETOOTH®, Dual-mode BLUETOOTH®, and / or any other BLUETOOTH® protocol. Any display device 20A-N that receives the advertisement may send a connection request to the sensor electronics device 6. The sensor electronics unit 6 and the display device 20A-N may then continue with the appropriate steps to pair using the communications protocol used (e.g., authentication, connection, encryption / decryption, data exchange, etc.).

[0062] Once the one or more display devices 20A-N and the sensor electronics unit 6 are paired at block 64, a user may calibrate the continuous analyte sensor 8 and / or the sensor electronics unit 6. In some cases, a user may use a finger prick to take a measurement indicative of their blood glucose level. The user may input such a measurement into one or more display devices 20A-N, which may transmit the data to the sensor electronics unit 6 using a communication protocol, and the measurement may be used to calibrate the continuous analyte sensor 8. For example, without limitation, the measurement may be incorporated into a calibration function that may be used by the continuous analyte sensor 8 and / or the sensor electronics unit 6 to convert a measurement or (e.g., current and / or voltage measurement) taken by the continuous analyte sensor 8 into a measurement indicative of the blood glucose level, such as, without limitation, a measurement having units of mmol / L or mg / dL. In some cases, a calibration function may be available on one or more display devices 20A-N, but not on the continuous analyte sensor 8 and / or the sensor electronics unit 6. In one such instance, the raw data (e.g., voltage, current, counts) can be transmitted to a display device 20A-N and converted to a measurement indicative of blood glucose level. After calibration, the sensor electronics unit 6 can proceed through a transmission cycle and communicate with the connected display devices 20A-N and / or any other desired devices.

[0063] At block 66, the sensor electronics unit 6 may connect to one or more display devices 20A-N during a transmission cycle to transmit / receive communications, with the sensor electronics unit 6 transmitting relevant data (e.g., analyte data) to the one or more display devices 20A-N. By way of example illustration and not limitation, the sensor electronics unit 6 and display devices 20A-N may connect during a transmission cycle using the following procedure: The sensor electronics unit 6 may advertise periodically at a predefined time interval, such as every 5 minutes, every 10 minutes, every 15 minutes, or any desired number of minutes, as desired. The advertisement window may be anywhere from 7 seconds to 22 seconds. In some cases, the duration of the advertisement window may be open longer to allow multiple display devices 20A-N (e.g., receivers and / or mobile devices) to connect and / or exchange data and / or commands / requests. The duration of any given interval may depend on the type of each of the display devices 20A-N present.

[0064] This transmission cycle may be affected by the battery constraints of the sensor electronics unit 6. Modifying advertising parameters such as advertising interval or duration may directly impact the total battery remaining in the sensor electronics unit 6. Through testing, these parameters (e.g., advertising interval and duration) may be adjusted to optimize the time it takes to connect different display devices 20A-N. In some cases, these parameters may be smartly adjusted to optimally change the behavior, for example, by monitoring past connection performance to set advertising interval and duration. Doing so may reduce the overall average advertising time when display devices 20A-N are nearby by connecting display devices 20A-N as quickly as possible.

[0065] As noted above, in some cases, the continuous analyte monitoring system 1 can include a sensor electronics unit 6 operatively and / or communicatively coupled to the continuous analyte sensor 8. The sensor electronics unit 6 can receive data (raw and / or processed) from the continuous analyte sensor 8. Also, as noted above, the sensor electronics unit 6 can communicate to one or more display devices 20A-N using a communication protocol, such as wireless communication, including but not limited to BLUETOOTH. Through this communication protocol, the sensor electronics unit 6 can transmit data, including but not limited to data based at least in part on the received sensor information, to the one or more display devices 20A-N. The one or more display devices 20A-N can also transmit data, commands, and / or other communications to the sensor electronics unit 6.

[0066] In some cases, when the sensor electronics unit 6 and one or more display devices 20A-N connect using wireless communication such as BLUETOOTH, the sensor electronics unit 6 can act as a peripheral device, which is an auxiliary device configured to connect to and in some cases support a central device used by a user. In this state, the display devices 20A-N can act as the central device. In this configuration, the central device can be responsible for scanning for peripheral device connections. By way of example, and using this terminology (as sometimes used in the art) for full clarity, a peripheral device (e.g., the sensor electronics unit 6) can advertise its availability for connections and accept connection requests made by a central device (e.g., the display devices 20A-N). In some implementations, a peripheral device cannot provide more than a certain number of connections (e.g., one, two, three, four, five, six, or more connections) within one transmission window. The central device can scan, connect, exchange data, and eventually disconnect in a timely manner to allow the peripheral device to request data periodically, such as every 5 minutes, 10 minutes, 15 minutes, or any desired number of minutes. The peripheral device can implement timeouts in the connection to prevent the central device from remaining connected longer than expected. To connect, the peripheral device uses a whitelist as described above to allow certain central devices or types of devices to connect. This can mean that a central device may be denied a connection even if it advertises as being connectable, due to the whitelist feature that is enabled for a different central device.

[0067] In some implementations, the sensor electronics unit 6 can communicate with one or more display devices 20A-N using multiple communication channels. Figure 1C illustrates the sensor electronics unit 6 in communication with a display device 20 through two or more different communication channels 106, 108. As noted above, display device 20, as used throughout this disclosure, refers to any one of the display devices 20A-N.

[0068] The sensor electronics unit 6 and the display device 20 can communicate through a number of communication protocols over the communication channels 106, 108. As used herein, a communication protocol can include any communication system configured to transmit information between two or more electronic devices, including, but not limited to, wired and wireless technologies such as BLUETOOTH, IBEACONS, ZIGBEE, Wi-Fi, inductive wireless data transmission, radio frequency, RFID, NFC, GSM, infrared, Ethernet cable, coaxial cable, Universal Serial Bus ("USB"), Firewire, data line, wire, and / or any wired and / or wireless connection known in the art. In some cases, the communication protocol can utilize wireless communication such as that used by BLUETOOTH. Wireless communication is further described throughout this disclosure, including with reference to Figures 5A and B. In some cases, the communication protocol may utilize electromagnetic radio waves (e.g., electronic induction between antenna loops) and / or radio frequency ("RF") fields, such as those used by NFC or RFID. Wireless communication and RF fields are further described throughout this disclosure, including with reference to Figures 5A and B. And, where a particular communication protocol is discussed with reference to an embodiment, it should be understood that other communication protocols may be used as well.

[0069] As illustrative examples, communication channel 106 may utilize an RF field, such as, but not limited to, NFC or RFID. Communication channel 108 may utilize wireless communication, such as BLUETOOTH. In instances where communication channel 106 is NFC and / or communication channel 108 is BLUETOOTH, NFC or RFID may offer several advantages over BLUETOOTH, including, but not limited to, little interference in crowded areas, ease of use, automatic pairing upon proximity, low power usage, etc. Similarly, BLUETOOTH may have advantages over NFC or RFID, such as faster data transmission, greater range, autonomous communication with many different devices, transmissions are automatically scheduled, etc.

[0070] In some implementations, as described in this disclosure, data, commands, status, and / or other communications between the sensor electronics unit 6 and the display device 20 can be transmitted over different communication protocols, such as communication channels 106, 108, depending on circumstances such as the range of communication protocols or the speed of data transfer. In some cases, communications over multiple communication protocols can be used simultaneously and / or sequentially to provide additional security, usability, and / or other desirable benefits. Each of the multiple communication protocols used can have different characteristics that can be utilized individually and for different advantages in different applications.

[0071] FIG. 2A illustrates a block diagram of an exemplary system in which a sensor electronics unit 6 is communicatively coupled to multiple display devices 20A-N using multiple communication channels 106A-N, 108A-N. As used herein, the "N" in display devices 20A-N and communication channels 106A-N, 108A-N may at least partially indicate the number of display devices that may be connected to the sensor electronics unit 6 at one time. For example, if N is B, B may at least partially indicate that two display devices (e.g., display devices 20A, B) may be connected to the sensor electronics unit 6 and may communicate with the sensor electronics unit 6 through communication channels 106A-B, 108A-B. If N is C, C may at least partially indicate that at least three display devices (e.g., display devices 20A, B, C) may communicate through communication channels 106A-C, 108A-C. Similarly, N may at least partially indicate any number of display devices. In some cases, the number of display devices that can be connected to the sensor electronics unit 6 can be predetermined when manufacturing and / or configuring the sensor electronics unit 6. For example, two or three display devices can be connected to the sensor electronics unit 6 in many exemplary configurations, but are not limited to this number and more can be connected. In some cases, the number of display devices that can be connected to the sensor electronics unit 6 can be limited by a communication protocol and / or the energy consumption of the communication protocol. For example, but not limited to, some versions of BLUETOOTH® can be limited to a maximum of seven display devices.

[0072] In some cases, one or more of the communication channels 106A-N may utilize the same communication protocol as one another. In some cases, one or more of the communication channels 106A-N may utilize different communication protocols from one another. Similarly, in some cases, one or more of the communication channels 108A-N may utilize the same communication protocol as one another, or one or more of the communication channels 108A-N may utilize different communication protocols from one another. Also, in some cases, any of the communication channels 106A-N may utilize the same communication protocol as any of the communication channels 108A-N. Similarly, in some cases, any of the communication channels 106A-N may utilize a different communication protocol than any of the communication channels 108A-N. That is, it is recognized that any kind of permutation of different communication protocols can be used as the communication channels 106A-N, 108A-N between the sensor electronics unit 6 and the display devices 20A-N. As a non-limiting example, each of communication channels 106A-N may use a first communication protocol, such as wireless communication like BLUETOOTH, and communication channels 108A-N may use a second, different communication protocol, such as an RF field like NFC or RFID. Communication between each of display devices 20A-N may also use any of the communication protocols described in this disclosure, including wireless communication (e.g., BLUETOOTH) or an RF field (e.g., NFC or RFID).

[0073] FIG. 2B illustrates an exemplary system in which an exemplary sensor electronics unit 6 is communicatively coupled to two exemplary display devices 20A,C, and the display devices 20A and 20C are configured to communicate with each other. The display devices 20A,C are particularly exemplary because in many implementations, particularly in the case of a CGM system, a user may have the display device 20A as a specialized display device and another display device 20C, which may be a mobile device. However, the display devices 20A,C are illustrated merely as examples, and any other display device, including any of the display devices 20A-N, may be used instead. The display devices 20A,C may communicate with each other through a communication channel 259. Through the communication channel 259, the display devices 20A,C may utilize any communication protocol described in this disclosure. As an illustrative example, but not limited to, the display devices 20A,C may communicate with each other using an RF field, such as NFC or RFID. For example, using NFC or RFID, the display devices 20A,C can transmit data to each other (e.g., estimated blood glucose levels, pairing information, information about the sensor electronics unit 6, calibration information, timing information (e.g., time synchronization, EGV data with time stamps, etc.), raw sensor data, system status information, detected faults, alerts, clocking information, device manufacturing ID, and / or any other data and / or information described in this disclosure), commands / requests (e.g., data requests, synchronization requests, pairing requests), etc. In some cases, information about the sensor electronics unit 6 can be transmitted to enable one of the display devices 20A,C to facilitate pairing the other of the display devices 20A,C to the sensor electronics unit 6. This information can be used to enable the other of the display devices 20A,C to pair with the sensor electronics unit 6 using another communication protocol, such as communication utilizing wireless communications including BLUETOOTH.For example, but not limited to, the pairing information can be transmitted between the display devices 20A,C directly or via a server (e.g., a network, a cloud, etc.). By way of example, but not limited to, a user can pair the display device 20A with the sensor electronics unit 6. Thereafter, the pairing information (e.g., timing information, encryption key, authentication information, advertising parameters, address, make / model, name, GAP, IRK, and / or any other relevant information for pairing) of the sensor electronics unit 6 can be transmitted directly from the display device 20A to the display device 20C, or the display device 20A can transmit its pairing information to a server, which can then be accessed by the display device 20C. Thus, the display device 20C can download the pairing information uploaded by the display device 20A. The pairing information can then more easily pair the display device 20C with the sensor electronics unit 6. In some cases, the display device 20C can download pairing information by signing in with a mobile application (e.g., a mobile application downloaded from an entity that creates and / or owns and / or licenses the app and / or from an app store such as APPLE, INC. or GOOGLE INC. or from another company). After signing in, the mobile application can communicate with a server and obtain the pairing information, thereby connecting the display device 20C with the sensor electronics unit 6. Advantageously, allowing the display devices 20A,C to communicate in this manner can enable the pairing information to be shared quickly and efficiently, reducing communication traffic between the display devices 20A and / or 20C and the sensor electronics unit 6. Furthermore, it can enable the display devices 20A,C to update and / or receive information (e.g., via a server) when they are not within range of each other and / or the sensor electronics unit 6.Having the ability to update and / or receive this information can be advantageous in keeping the display devices 20A,C updated even when they are not connected to the sensor electronics unit 6. Such transfer of pairing information between the display devices 20A,C can be advantageous in allowing a medical professional to set up the system for a user. For example, but not limited to, a medical professional can have a display device 20C to which the medical professional can send the pairing information of the patient's display device 20A during the setup of the display device 20A. This can allow the medical professional to facilitate the patient's use of the display device 20A, especially when the patient is an infant, elderly, disabled, or otherwise unable to set up the display device 20A. As another non-limiting example, a user may wish to use the display device 20C and also use the display device 20A to send the pairing information.

[0074] The estimated blood glucose levels can be transmitted between the display devices 20A,C to facilitate viewing of information about the user of the sensor electronics unit 6. For example, without limitation, the display device 20A can be the user's display device. The display device 20C can be a display device owned by a medical practitioner. Using an RF field such as NFC or RFID, data transmission from the display device 20A to the display device 20C can include historical data that allows the health practitioner to analyze the patient's blood glucose level response and provide treatment. Advantageously, the NFC or RFID can enable a secure manner of transferring such data without requiring pairing. Also, since a physician may ultimately retrieve data from multiple display devices or have multiple display devices that the physician can connect to using wireless communication such as BLUETOOTH, the ability to use NFC or RFID can enable the physician to conserve the battery of the physician's display device (e.g., by not advertising and / or not having to re-authenticate) and can also enable the practitioner not to accidentally connect to another device in the vicinity. In other applications, data transmitted via NFC or RFID can be used for backfill purposes to allow one of the display devices 20A-B to transmit historical data to the other. In some cases, current data can also be transmitted between the display devices 20A-B via NFC or RFID. Those skilled in the art should recognize that other communication protocols, such as Wi-Fi or any other communication protocol described in this disclosure, can be used to transfer data as well.

[0075] In some implementations, a communication protocol (e.g., NFC, RFID, Wi-Fi, BLUETOOTH, and / or any other communication protocol described in this disclosure or known in the art) may be used to synchronize alerts to the display devices 20A,C. For example, without limitation, Wi-Fi may be used such that when a user acknowledges an alert or communication to one of the display devices 20A,C, such acknowledgment is visible on the other of the display devices 20A,C. Advantageously, this may allow multiple users and devices to coordinate treatment of a user of the sensor electronics unit 6 and / or prevent excessive alerts and communications to multiple users and / or a single user using multiple devices.

[0076] 3 illustrates a functional block diagram of an exemplary sensor electronics unit 6. The sensor electronics unit 6 can include a controller 301, a memory 302, a power source 303, and / or an operations unit 304, each of which can be operatively and / or communicatively coupled to each other and to each other's components and / or subcomponents. The controller 301 can control various operations performed by the sensor electronics unit 6. In some implementations, the sensor electronics unit 6 can be configured to perform example processes, methods, and / or systems, and / or substantially similar processes, methods, and / or systems described with reference to the sensor electronics unit 6 throughout this disclosure.

[0077] The controller 301 may be operatively and / or communicatively coupled to a memory 302, which may include, but is not limited to, a volatile, non-volatile, read-only memory ("ROM"), and / or random access memory ("RAM"), and may provide instructions and data to the controller 301. A portion of the memory 302 may also include a non-volatile random access memory ("NVRAM"). The controller 301 may perform logical and / or arithmetic operations based on program instructions stored in the memory 302. The controller 301 may include one or more processors (e.g., microprocessors) and other peripherals. The instructions in the memory 302 may be executed to implement the methods described herein. For example, the memory 302 may be a non-transitory computer-readable storage medium having a number of instructions stored therein, which may be executed by a processing device (e.g., the controller 301) to operate the sensor electronics unit 6. The operational unit 304 may be coupled to the controller 301 to perform various operations described in this disclosure. Some implementations may include none, one or more of the units in the operational unit 304. Throughout this disclosure, references are made to various controllers and / or processors. In some implementations, a single controller (e.g., controller 301) may serve as the various controllers and / or processors described. In other implementations, different controllers or processors may be used. The controller 301 may transmit and / or receive signals, such as power signals, control signals, sensor signals, interrogation signals, status signals, data signals, electrical signals, and / or any other desired signals, including discrete or analog signals.The controller 301 may coordinate and / or manage the operational units 304 and / or set timing (e.g., synchronously or asynchronously), turn on / off, control power budget, receive and / or send network commands and / or updates, update firmware, send interrogation signals, receive and / or send status, and / or perform any operation to operate the features of the sensor electronics unit 6.

[0078] The operational unit 304 may include various units that perform the functions of the sensor electronics unit 6. For example, without being limited thereto, such units of the operational unit 304 may include a communicator 305, a data storage device 306, a data manager 307, a signal processor 308, and / or an operating system 310.

[0079] In some implementations, the communicator 305 can communicatively couple the sensor electronics unit 6 and / or any components therein (e.g., the operational unit 304) to one or more display devices (e.g., the display devices 20A-N and / or any other display devices described in this disclosure). The communicator 305 can be configured to send / receive communications through a wired and / or wireless connection, such as any wired and / or wireless connection described in this disclosure. For example, but not limited to, the communicator 305 can utilize a communication protocol configured to send and / or receive data through a communication channel. For example, but not limited to, such communication protocols include BLUETOOTH, IBEACON, ZIGBEE, Wi-Fi, inductive wireless data transmission, radio frequency, radio transmission, RF field, RFID, NFC, GSM, infrared, Ethernet cable, coaxial cable, USB, Firewire, data line, wire, and / or any wired and / or wireless connection known in the art. For example, without limitation, the communicator 305 may include antennas, inductors, signal lines, ground lines, and / or any other electronics used to transmit / receive data. In the case of NFC, RFID, and / or substantially similar technologies, the communicator 305 may include readers, writers, and / or tags.

[0080] The communicator 305 can be configured to transmit and / or receive status, commands, and / or other data / information. For example, but not limited to, the communicator 305 can transmit status, commands, and / or data / information from the data storage 306, data manager 307, signal processor 308, operating system 310, operational unit 304, controller 301, memory 302, power supply 303, and / or any other components and / or subcomponents of the sensor electronics unit 6.

[0081] The data storage device 306 can be configured to store (e.g., record) data temporarily and / or permanently. The data storage device 306 can include storage devices that can store data using different media, such as, but not limited to, electrical (e.g., semiconductor, floating gate transistor, hard disk, flash memory, RAM, ROM, enterprise storage, cloud, distributed storage devices, etc.), optical storage (e.g., photographic, microform, holographic, optical disk, magneto-optical drive, 3D optical data storage, holographic data storage), chemical (e.g., organic, protein, synapse, receptor, chemical concentration, etc.), thermodynamic (e.g., phase change material, heat storage device, etc.), photochemical (e.g., film, etc.), mechanical (e.g., switch), magnetic storage (e.g., magnetic tape, wire, etc.), etc. The data storage device 306 may also store any data and / or information based at least in part on data from any components of the sensor electronics unit 6, including the controller 301, the power supply 303, the memory 302, and / or units within the operational unit 304.

[0082] The data manager 307 can be configured to analyze and / or manage data in the data storage 309, memory 302, and / or any components (e.g., controller 301, power supply 303, and / or units within operational unit 304) of the sensor electronics unit 6. Operations that the data manager 307 can use on such data include, but are not limited to, compressing, decompressing, sorting, categorizing, ordering, optimizing, defragmenting, deleting, securely erasing, securing, manipulating, identifying, copying, pasting, write protecting (e.g., temporary or permanent write protecting), backing up, authenticating, and the like. The data manager 307 can also perform error monitoring, error correction, and / or data validation, including identifying and / or repairing transmission-related errors, data formatting, device-related error codes, invalid data, duplicate data points, and / or other processes on the data.

[0083] Signal processor 308 can be configured to process any of the data from sensor electronics unit 6, including, by way of non-limiting example, data stored in data storage 306 and / or managed by data manager 307. Signal processor 308 can perform any of the analyses of the data presented in this disclosure, as well as other analyses and / or processes.

[0084] The power source 303 can include one or more batteries, including but not limited to lithium, lithium ion, nickel-cadmium, nickel metal hydride, nickel-hydrogen, carbon-zinc, silver-oxide, zinc-carbon, zinc-air, mercury oxide, alkaline, or any other type of battery known in the art. Certain batteries can be recharged wirelessly (e.g., by a resonant circuit and / or a resonant tank circuit) and / or by plugging into an external power source, etc. The power source 303 can also be any energy source, including solar, wind, water, nuclear, hydrogen, gasoline, natural gas, fossil fuels, mechanical energy, steam, and / or a wall socket and electronics device that converts any power source into electricity. The power source 303 can have a sensor (not shown) that monitors the amount of power available. For example, but not limited to, if a battery is used, the sensor can measure the battery charge remaining. The sensor can detect and / or estimate the battery charge remaining in the sensor electronics unit 6. In some implementations, the battery charge sensor can actively measure the charge, capacitance, chemical composition, or potential of the battery unit. In some cases, the sensor can be a timer that estimates the life of the sensor electronics unit 6, such as one month, two months, three months, four months, five months, six months, or more. The estimated time or percentage of battery usage or remaining capacity can be displayed on one or more display devices and / or the sensor electronics unit 6. In some cases, the sensor can track battery usage (e.g., count, power budget, voltage draw, current draw, estimated leakage, etc.) and total the battery usage over time. The total operation can be kept and compared to a total battery budget (e.g., count, power budget, voltage budget, current budget, etc.) to estimate the remaining battery capacity and / or usage life.

[0085] The operating system 310 can be configured to manage the memory 302, the controller 301, the power supply 303, the units within the operational unit 304, and / or any software, hardware, and / or features of the sensor electronics unit 6. For example, without limitation, the operating system 310 can include device drivers to manage hardware resources of the sensor electronics unit 6.

[0086] Any of the above-mentioned components of the sensor electronics unit 6 may be instantiated in software and / or hardware. For example, a unit may be a portion(s) of hardware and / or a unit / module of code running on a computer. Hardware may include a processor, circuit logic, etc.

[0087] 4A illustrates a functional block diagram of an example display device 20. As noted above, display device 20, as used throughout this disclosure, represents any one of display devices 20A-N. In some implementations, display device 20 can be configured to perform example processes, methods, and / or systems, and / or substantially similar processes, methods, and / or systems described with reference to display devices throughout this disclosure.

[0088] The controller 401 may be operatively and / or communicatively coupled to a memory 402, including but not limited to volatile, non-volatile, ROM, and / or RAM, that may provide instructions and data to the controller 401. A portion of the memory 402 may also include an NVRAM. The controller 401 may perform logical and arithmetic operations based on program instructions stored in the memory 402. The controller 401 may include one or more processors (e.g., microprocessors) and other peripherals. The instructions in the memory 402 may be executed to implement the methods described herein. For example, the memory 402 may be a non-transitory computer-readable storage medium having a number of instructions stored therein, which may be executed by a processing device (e.g., the controller 401) to operate the display device 20. The operation unit 404 may be coupled to the controller 401 to perform various operations described in this disclosure. Some implementations may include one or more or none of the units in the operation unit 404. Throughout this disclosure, reference is made to various controllers and / or processors. In some implementations, a single controller (e.g., controller 401) can serve as the various controllers and / or processors described. In other implementations, different controllers or processors can be used. Controller 401 can transmit and / or receive signals, such as power signals, control signals, sensor signals, interrogation signals, status signals, data signals, electrical signals, and / or any other desired signals, including discrete or analog signals.The controller 401 may coordinate and / or manage the operational units 404 and / or set timing (e.g., synchronously or asynchronously), turn on / off, control power budget, receive and / or send network commands and / or updates, update firmware, send interrogation signals, receive and / or send status, and / or perform any operation to operate the features of the display device 20.

[0089] The operational unit 404 may include various units that perform the functions of the display device 20. For example, but not limited to, such units of the operational unit 404 may include a communicator 405, a data storage device 406, a data manager 407, a signal processor 408, a user interface 409, and / or an operating system 410.

[0090] In some implementations, the communicator 405 can communicatively couple the display device 20 and / or any components therein (e.g., the operational unit 404) to one or more sensor electronics units (e.g., the sensor electronics unit 6). The communicator 405 can be configured to send / receive communications through a wired and / or wireless connection, such as any wired and / or wireless connection described in this disclosure. For example, but not limited to, the communicator 405 can utilize a communication protocol configured to send and / or receive data through a communication channel. For example, but not limited to, such communication protocols include BLUETOOTH, IBEACON, ZIGBEE, Wi-Fi, inductive wireless data transmission, radio transmission, RF field, radio frequency, RFID, NFC, GSM, infrared, Ethernet cable, coaxial cable, USB, Firewire, data line, wire, and / or any wired and / or wireless connection known in the art. For example, without limitation, communicator 405 may include antennas, inductors, signal lines, ground lines, and / or any other electronics used to transmit / receive data. In the case of NFC, RFID, and similar technologies, communicator 405 may include readers, writers, and / or tags.

[0091] The communicator 405 can be configured to transmit and / or receive status, commands, and / or other data / information. For example, but not limited to, the communicator 405 can transmit status, commands, and / or data / information from the data storage 406, data manager 407, signal processor 408, operating system 410, operational unit 404, controller 401, memory 402, power supply 403, and / or any other components and / or subcomponents of the sensor electronics unit 20.

[0092] The data storage device 406 can be configured to store (e.g., record) data temporarily and / or permanently. The data storage device 406 can include storage devices that can store data using different media, such as, but not limited to, electrical (e.g., semiconductor, floating gate transistor, hard disk, flash memory, RAM, ROM, enterprise storage, cloud, distributed storage devices, etc.), optical storage (e.g., photographic, microform, holographic, optical disk, magneto-optical drive, 3D optical data storage, holographic data storage), chemical (e.g., organic, protein, synapse, receptor, chemical concentration, etc.), thermodynamic (e.g., phase change material, heat storage device, etc.), photochemical (e.g., film, etc.), mechanical (e.g., switch), magnetic storage (e.g., magnetic tape, wire, etc.), etc. The data storage device 406 may also store any data and / or information based at least in part on data from any components of the display device 20, including the controller 401, the power supply 403, the memory 402, and / or units within the operating unit 404.

[0093] The data manager 407 may be configured to analyze and / or manage data in the data storage 406, memory 402, and / or any components (e.g., controller 401, power supply 403, and / or units within operating unit 404) of the display device 20. Operations that the data manager 407 may use on such data include, but are not limited to, compressing, decompressing, sorting, categorizing, directing, optimizing, defragmenting, deleting, securely erasing, securing, manipulating, identifying, copying, pasting, write-protecting (e.g., temporary or permanent write-protecting), backing up, authenticating, and the like. The data manager 407 may also perform error monitoring, error correction, and / or data validation, including identifying and / or repairing transmission-related errors, data formatting, device-related error codes, invalid data, duplicate data points, and / or other processes on the data.

[0094] Signal processor 408 can be configured to process any data of display device 20, including, by way of non-limiting example, data stored in data storage 406 and / or managed by data manager 407. Signal processor 408 can perform any of the analyses of the data presented in this disclosure, as well as other analyses and / or processes.

[0095] The user interface 409 can be configured to allow a user to communicate with the display device 20. For example, but not limited to, the user interface 409 can include a touch panel, buttons, a keypad / keyboard, a port (e.g., USB, DVI, display port, E-Sata, Firewire, PS / 2, serial, VGA, SCSI, audio port, HDMI, PCMCIA port, memory card port (e.g., SD and miniSD), and / or a port for computer readable media), a mouse, a roller ball, a console, a vibrator, an audio transducer, and / or any interface for a user to input and / or receive data and / or commands, whether coupled wirelessly or through a wire (including, but not limited to, any of the wireless or wired connections described in this disclosure). The user interface 409 may include displays such as, but not limited to, LCD, LED displays, LED LCD displays, IPS, cathode ray tubes, plasma displays, HD panels, 4K displays, retina displays, organic LED displays, touch screens, surfaces, canvases, and / or any display, television, monitor, panel, and / or device known in the art for visual representation.

[0096] The power source 403 may include one or more batteries, including, but not limited to, lithium, lithium ion, nickel-cadmium, nickel metal hydride, nickel-hydrogen, carbon-zinc, silver-oxide, zinc-carbon, zinc-air, mercury oxide, alkaline, or any other type of battery known in the art. Certain batteries may be recharged wirelessly (e.g., by a resonant circuit and / or a resonant tank circuit) and / or by plugging into an external power source, etc. The power source 403 may also be any energy source, including solar, wind, water, nuclear, hydrogen, gasoline, natural gas, fossil fuels, mechanical energy, steam, and / or electrical outlets and electronic devices that convert any power source into electricity. The power source 403 may have a sensor (not shown) that monitors the amount of power available. For example, but not limited to, if a battery is used, the sensor may measure the remaining battery charge. The sensor may detect and / or estimate the remaining battery charge of the display device 20. In some implementations, the battery charge sensor may actively measure the charge, capacitance, chemical composition, or potential of the battery unit. In some cases, the sensor can be a timer that estimates the life of the display device 20, such as one month, two months, three months, four months, five months, six months, or more. The sensor can then display an estimated time or percentage of battery usage or remaining capacity. In some cases, the sensor can track battery usage (e.g., count, power budget, voltage consumption, current consumption, estimated leakage, etc.) and total the battery usage over time. The total operation can be kept and compared to a total battery budget (e.g., count, power budget, voltage budget, current budget, etc.) to estimate the remaining battery capacity and / or usage life.

[0097] Operating system 410 may be configured to manage memory 402, controller 401, power supply 403, units within operating unit 404, and / or any software, hardware, and / or features of display device 20. For example, but not limited to, operating system 410 may include device drivers to manage hardware resources of display device 20.

[0098] Any of the above-mentioned components of the display device 20 may be instantiated in software and / or hardware. For example, a unit may be a portion(s) of hardware and / or a unit / module of code running on a computer. The hardware may include a processor, circuit logic, etc.

[0099] FIG. 4B is an example advertising / connection sequence between an example sensor electronics unit 6 and a display device 20. The various tasks performed in association with the advertising / connection illustrated in FIG. 4B may be performed by a processor / controller executing instructions embodied in a non-transitory computer-readable medium. For example, the tasks performed in association with the procedure may be performed by hardware, software, firmware, or any combination thereof embedded in one or more computing devices, such as the sensor electronics unit 6 and / or the display device 20. It should be appreciated that the procedure may include any number of additional or alternative tasks. The tasks shown in FIG. 4B may 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.

[0100] In the examples described below, the analyte value may be a glucose value based on one or more measurements from the continuous analyte sensor 8. However, it should be understood that the analyte value may be any other analyte value described herein. The wireless data communication between the sensor electronics unit 6 and the display device 20 may correspond to the duration between two successive wireless communication sessions between the communicator 305 (e.g., communicator 305) of the sensor electronics unit 6 and the communicator 405 (e.g., communicator 405) of the display device 20, referred to as "T 間隔 The update interval may occur periodically, at a time delimited by an update interval, denoted T . Alternatively, the update interval may be a period of time during which the most recently measured glucose value is obtained and transmitted. The transmission of advertisement signals, the establishment of a data connection (e.g., a communication channel), authentication, and the request and transmission of data each occur within the update interval T . 間隔 Inside "T 起動 For example, between two consecutive wireless communication sessions, the communication unit may be in a state where the communication unit is ... 停止 " to conserve battery power and / or reduce peak voltage requirements.

[0101] 4B illustrates an example of two such wireless communication sessions, a first wireless communication session 410 and a second wireless communication session 420. Each wireless communication session 410, 420 begins with the sensor electronics unit 6 establishing a data connection with the display device 20. To establish the data connection with the display device 20, the communicator unit 305 of the sensor electronics unit 6 can transmit a series of advertisement signals 412 during the first wireless communication session 420. Each advertisement signal can be considered as an invitation for the communicator 405 of the display device 20 to establish a data connection with the communicator 305 of the sensor electronics unit 6. As discussed in more detail below, in some implementations, the advertisement signals 412 can be embodied as advertising beacons. It should be noted that in some implementations, the advertisement signal 412 itself can have advertising parameters so that directed or targeted advertising can be performed to a particular display device 20 or type of device.

[0102] In some cases, because the sensor electronics unit 6 may only be turned on for the first time and / or may not currently be paired with the display device 20, when the sensor electronics unit 44 is turned on, the sensor electronics unit 6 may engage in an initial system setup. Typically, a user of the display device 20 may identify a new and / or never-used sensor electronics unit 6 and pair it with the display device 20 by inputting identification information (e.g., a serial number) associated with the new / unpaired sensor electronics unit 6 via an application running on the display device 20 using the user interface 409 (e.g., a downloadable internet-based Java Script and / or mobile application downloaded from an entity that creates and / or owns and / or licenses the app and / or from an app store such as APPLE, INC. or GOOGLE INC. or from other companies). During the first wireless communication session 410, an authentication procedure may occur as part of a data connection process 414, which may be a first data connection process. In some embodiments, information can be obtained from a passive tag or communicator 305 integrated into the sensor electronics unit 6, for example, using an NFC reader of the display device 20 to read the passive NFC tag. For example, but not limited to, the passive NFC tag can store data such as calibration or manufacturing information, including identification information associated with the continuous analyte sensor 8 or the sensor electronics unit 6. In some cases, the display device 20 is configured to read information from the passive tag (e.g., via the communicator 405) after completion of an authentication procedure. In some cases, at least a portion of the information stored in the passive tag is encrypted. In some embodiments, the tag can be located at the base of the sensor electronics module 6.In such embodiments, information stored on the passive tag (e.g., information related to a sensor or sensor electronics module) may first be read by a display device 20. The display device may then transmit the captured information via a wireless protocol (e.g., NFC or BLE) to the sensor electronics module 6 or another display device.

[0103] To establish a data connection with the sensor electronics unit 6, the display device 20 can listen continuously or periodically until it receives an advertisement signal transmitted by the communicator 305 of the sensor electronics unit 6. Once the communicator 305 of the sensor electronics unit 6 starts transmitting advertisement signals 412, it can capture one, two, or more advertisement signals for the display device 20, receive at least one of the advertisement signals, and respond to at least one of the advertisement signals. In some cases, the extended advertising can consume energy and / or battery power of the sensor electronics unit 6. In some implementations, once the display device 20 receives an advertisement signal and responds to it, e.g., via an acknowledgment, the communicator 305 of the sensor electronics unit 6 can stop sending additional advertisement signals. In other implementations, the communicator 305 of the sensor electronics unit 6 can continue to transmit additional advertisement signals even after receiving a response from the display device 20, such that another display device (e.g., one or more of the display devices 20A-N) can receive and / or respond to at least one of the additional advertisement signals. After successful reception of the advertisement signal by the display device 20, the display device 20 and the sensor electronics unit 6 can engage in a data connection process 414.

[0104] During the data connection process 414, the display device 20 can request a challenge value from the sensor electronics unit 6, which in response can transmit the challenge value to the display device 20. Upon receiving the challenge value, the display device 20 can calculate a hash value based on the challenge value and identification information associated with the sensor electronics unit 6 and / or the communicator 305 of the sensor electronics unit 6, and transmit the hash value to the communicator 305 of the sensor electronics unit 6. The communicator 305 of the sensor electronics unit 6 can receive the hash value from the display device 20, decode the identification information from the hash value, and verify that the received identification information matches identification information associated with the sensor electronics unit 6 and / or the communicator 305 of the sensor electronics unit 6 that was previously stored in a memory (e.g., memory 302) of the sensor electronics unit 6, such as during manufacturing of the sensor electronics unit 6. In response to the verification, the communicator 305 of the sensor electronics unit 6 can transmit a signal confirming successful authentication to the display device 20. Once authenticated, the sensor electronics unit 6 and display device 20 can exchange information to determine how to exchange data (e.g., specific frequencies, time slot allocations, encryption, etc.).

[0105] After completion of the data connection process 414, the sensor electronics unit 6 and the currently connected display device 20 may engage in a first data communication 416 during which the display device 20 may request and / or receive desired information (e.g., analyte measurement data, control information, identification information, and / or instructions) from the sensor electronics unit 6. When the first data communication 416 is completed, the data connection may be terminated (e.g., by closing the established communication channel) and the communicator 305 and / or controller 301 of the sensor electronics unit 6 may be shut down by causing the communicator 305 and / or controller 301 to go into a sleep or stopped mode (e.g., low power mode or shelf mode). In some implementations, the communicator 305 of the sensor electronics unit 6 may be completely or substantially completely powered down during the sleep mode (e.g., low power or shelf mode). In some implementations, the communicator 305 of the sensor electronics unit 6 can be in a low power mode that uses only a small fraction (e.g., 1-50%) of its normal current / power. As discussed further below with reference to Figures 6C-D, as well as elsewhere throughout this disclosure, the communicator 305 of the sensor electronics unit 6 can be woken up by a communication protocol that uses an RF field, such as, for example, NFC or RFID, which issues an on-demand request to the display device 20.

[0106] The wake-up period T corresponds to the duration of each wireless communication session. 起動 is a negligible update interval T 間隔 For example, T 間隔 can be about 200 to 20 seconds, T 起動 The T can be 20 to 40 seconds. Therefore, the communicator 305 of the sensor electronics unit 6 is configured to have a T of 5 minutes. 間隔The communicator 305 may be fully powered for only 10 percent (e.g., 30 seconds) of the downtime or period T. This can significantly reduce power consumption and peak voltage demands. In some cases, the communicator 305 may go into a low power mode when not transmitting, rather than cutting off power completely. 停止 When the communicator 305 of the sensor electronics unit 6 is subsequently powered on again, it may initiate a second wireless communication session 420, as shown in FIG. 4B, and begin transmitting a second series of advertisement signals 422 and engage in a second data connection process 424 and a second data communication process 426 with the communicator 405 of the display device 20. However, unlike the first data connection process 414, the second data connection process 424 does not need to include an authentication procedure, since the sensor electronics unit 6 and the display device 20 have been successfully paired or bonded during the first wireless communication session 410, as explained above. This process may continue, with new data connections and communications being completed at predetermined intervals. Each inactivity period T during which the communicator 305 of the sensor electronics unit 6 is in sleep mode may be followed by a second data connection process 424. 停止 During all or part of, the controller 401 of the sensor electronics unit 6 can take one or more analyte value measurement(s) using the analyte sensor and sensor measurement circuitry. For example, without limitation, the controller 401 or the sensor electronics unit 6 can take multiple analyte value measurements and average the measurements to generate a single averaged analyte value that is transmitted in the next wireless communication session.

[0107] A new communication channel is continuously re-established at each update interval T 間隔Allowing the communicator 305 of the sensor electronics unit 6 to be partially or fully powered down during a period of time can provide significant power savings. For example, a cycle of re-establishing a new communication channel and powering down the communicator 305 can allow the sensor electronics unit 6 to operate for a month, three months, six months, a year, etc., without a battery change. Note that in some implementations, a battery change can be a function of an actual battery running out of power, or some predetermined level of battery charge. Additionally, the update interval T 間隔Establishing a specific data connection (e.g., communication channel) with only desired display devices, e.g., display device 20 and / or any display devices 20A-N, rather than transmitting glucose data points globally during a signaling session can prevent unauthorized use and interception of glucose measurements. In some implementations, only a subset of the multiple display devices (e.g., display devices 20A-N) can be configured to receive different data, such as glucose measurements and / or alarm conditions. For example, but not limited to, in addition to the display device identifier(s), the whitelist can be populated with a data type identifier that indicates the type of data that is to be sent to the particular display device(s) that populate the whitelist. For example, but not limited to, a particular display device(s) can have a data type identifier that indicates the display device that receives glucose measurement data and / or alarm conditions, such as low blood glucose level. In other implementations, the sensor electronics unit 6 can be pre-programmed with preference or profile information that can be accessed to determine what type(s) of data is to be sent to what display device(s). Thus, prior to exchanging sensor information, the sensor electronics unit 6 may access a whitelist (or in some implementations, a bonding list) and / or preference / profile information to determine what type(s) of data to send to the display device. In yet other implementations, in an initial communication between the sensor electronics unit 6 and the display device 20, the display device 20 may transmit type information (e.g., the type of information the display device should receive) to the sensor electronics unit 6. This has the advantage of preventing all of the display devices 20A-N in communication with the sensor electronics unit 6 from issuing alarms, thereby confusing and / or frustrating the user.Additionally, by establishing a secure two-way communication channel, requests for specific glucose measurements or communication of calibration or configuration information can be transmitted between the sensor electronics unit 6 and the display device 20 as needed / on demand.

[0108] Also, in some implementations, the communicator 305 of the sensor electronics unit 6 may update the update interval T 間隔 Instead, the communicator 305 of the sensor electronics unit 6 may not wake up over every data communication update interval T 間隔 To occur less frequently than every second, third, or fourth update interval T 間隔 The communicator 305 of the sensor electronics unit 6 may be woken up every 10 seconds, thereby further reducing power consumption. Wake-up may also depend on the sensor information. For example, the communicator 305 of the sensor electronics unit 6 may only wake up if the data meets certain thresholds, such as a rate of change of current, a high value of current, a low value of current, an absolute difference from a previously exchanged value, a percentage difference from a previously exchanged value, and the like. In some implementations, instead of skipping a certain fixed update interval, the length of each interval may be varied based on the sensor information or other criteria. For example, but not limited to, if the sensor information indicates a low glucose value and / or if a hypoglycemic reaction is detected, the update interval value may be shortened from the normal longer update interval value so that readings are taken and / or transmitted more frequently.

[0109] In some implementations, the update interval T 間隔 , startup period T 起動 , and the frequency at which the transceiver is woken up (e.g., every second, third, or fourth update interval) F 起動, may be variable. In certain implementations, the above-identified parameters may be user-configurable (e.g., by entering values ​​for the variables using a user interface of display device 20) and / or may be varied automatically by sensor electronics unit 6 or display device 20 based on one or more criteria. The criteria may include: (i) the battery power (e.g., using power source 303) of the monitored sensor electronics unit 6; (ii) the currently measured, previously measured, and / or predicted glucose concentrations meeting or exceeding a predetermined threshold; (iii) the trend of the host's glucose concentration based on the currently measured, previously measured, and / or predicted glucose concentrations; (iv) the rate of change of the host's glucose concentration based on the currently measured, previously measured, and / or predicted glucose concentrations meeting or exceeding a predetermined threshold; (vi) whether the host is determined to be hyperglycemic or near hypoglycemic based on the currently measured, previously measured, and / or predicted glucose concentrations; (vii) the host's activity (e.g., exercise or sleep) entered by the user; (viii) the time since the start of a sensor session (e.g., when a new sensor is used); (ix) one or more errors detected by the sensor electronics unit 6 and / or the display device 20; and / or (x) the type of display device 20 (e.g., the display device 20 may be connected to or populated with a whitelist or bonding list).

[0110] T as described herein 間隔 , T 起動 , F 起動 , and / or other configuration items may form part of a communication protocol profile that may be stored in any profile, the device implementing a basic communication protocol to enable customized use of the protocol for communicating analyte measurements in one or more of the sensor electronics unit 6 and the display device 20.

[0111] In some implementations, the communication protocols can have different ranges and / or different authentication protocols. FIG. 5A illustrates an example range of an example communication protocol of an example sensor electronics unit 6 having two communication protocols, each communication protocol having a different range. As described above, the communication protocols can include any communication protocol known in the art, including those described in this disclosure. For example, but not limited to, the range 506 can at least partially indicate the range of an RF field, such as, but not limited to, NFC or RFID. By way of example, if NFC has a range 506, the range 506 can be in centimeters, such as 10 centimeters or less. Due to the small range, in many cases, NFC can have simple and / or automatic connection between devices using the NFC communication protocol. NFC-enabled devices can include devices that operate with NFC card emulation, NFC reader / writer, and / or NFC peer-to-peer. NFC can transfer data at speeds ranging from 106 to 424 kilobits per second, or at any other speed as communication protocol standards are updated from time to time. In some cases, NFC communicates at 13.56 MHz. In some cases, an initiating device of a transmission using NFC can generate an RF field that can power a receiving device. In many cases, NFC is desirable for security and simplicity. However, the NFC communication protocol can be limited in range. NFC is sometimes considered by those skilled in the art to be included as a subset and / or derivative of the RFID family of technologies. In general, RFID technologies can have variable ranges, including those with ranges of up to 2000 feet. RFID systems can be active reader passive tags ("ARPT"), with an active reader device that transmits an interrogator signal and also receives an authentication response from the passive tag.In some cases, the RFID system may be an Active Reader Active Tag ("ARAT") where an active tag is awakened from an active reader by an interrogator signal. RFID may operate in a range of frequency bands, including, but not limited to, 120-150 kHz, 13.56 MHz, 433 MHz, 865-868 MHz, 902-928 MHz, 2450-5800 MHz, 3.1-10 GHz, etc. As used herein, communication protocols using RF fields may include other RF fields other than NFC or RFID, including other RF fields operating in the frequency ranges of 13.56 MHz, 120-150 kHz, 13.56 MHz, 433 MHz, 865-868 MHz, 902-928 MHz, 2450-5800 MHz, 3.1-10 GHz. NFC or RFID are merely illustrative examples.

[0112] The range 508 may at least partially indicate a second communication protocol. For example, but not limited to, the second communication protocol may utilize wireless communication, such as BLUETOOTH. As an illustrative example, but not limited to, when the second communication protocol is BLUETOOTH, the range 508 may be approximately 30 feet. In some cases, BLUETOOTH may include a connection between devices that is manually set up by a user, such as a procedure in which one device detects the other device and the devices are paired and / or authenticated. BLUETOOTH may transmit in the 2.4-2.485 GHz ISM band, or any frequency as the BLUETOOTH standard is updated from time to time. BLUETOOTH versions may have relatively fast data rates, such as up to 800 kilobits per second. In many cases, BLUETOOTH is desirable for its speed and range. However, there may be challenges with connectivity, energy consumption, excessive handshaking, packet drops, security, and other issues. As used herein, wireless communication can include other wireless communication protocols other than BLUETOOTH, including other wireless communications operating in the 2.4-2.485 GHz frequency range. BLUETOOTH is used merely as an illustrative example.

[0113] 5B illustrates example ranges of example communication protocols of example display device 20, with each communication protocol having a different range. Ranges 556, 558 may be substantially similar to ranges 506, 508, respectively. As noted above, a variety of communication protocols may be used, such as those that use RF fields (e.g., NFC or RFID) or wireless communications (e.g., BLUETOOTH).

[0114] 5C illustrates an exemplary functional block diagram illustrating certain functional units of display device 20. These functional units may be instantiated in software and / or hardware. For example, the units may be a portion(s) of hardware and / or a unit / module of code running on a computer. Hardware may include a processor, circuit logic, etc.

[0115] Wake unit 654 can perform waking actions, such as, but not limited to, allowing a user to wake up sensor electronics unit 6 from a low power mode and / or a shelf mode (e.g., as described with reference to FIGS. 4B, 6C-D, and elsewhere throughout this disclosure) using display device 20. In some cases, waking up sensor electronics unit 6 can include sending a wake-up command to sensor electronics unit 6.

[0116] The pairing unit 655 can be used to pair the display device 20 and the sensor electronics unit 6, and can be configured to communicate via wireless communication (e.g., BLUETOOTH) and / or any other communication protocol described in this disclosure. In some cases, if the display device 20 and the sensor electronics unit 6 have not been previously paired via that communication protocol, the pairing unit 655 can include one or more of commands for pairing, initial setup information, timing information, advertising parameters, device information, frequency, sequence, encryption / decryption information, and / or other parameters. This functionality and others are discussed elsewhere throughout this disclosure, with reference to FIG. 8 below. If the display device 20 is paired with the sensor electronics unit 6, the pairing unit 655 can include adding the display device 20 to a white / bonding list (if not already added), advertising the display device 20, connecting, authenticating, exchanging data, and the like.

[0117] The calibration unit 656 can be used to calibrate the sensor electronics unit 6. For example, but not limited to, a user can measure his or her blood glucose level through a finger prick. The user can enter that data into the display device 20 (e.g., into a field (not shown) through the user interface 409) and transmit information based at least in part on that data to the sensor electronics unit 6 through an RF field communication protocol such as NFC or RFID. Conveniently, the calibration can be time-dependent, where the user may want to adjust and / or add new calibration parameters quickly so that the user has a correct reading. Conveniently, calibration using an RF field such as NFC or RFID can be achieved on demand and without the need to follow a pairing procedure.

[0118] The data retrieval unit 657 can be used to request the sensor electronics unit 6 to retrieve data. In some cases, the data retrieval can include a command to transmit the data over another communication protocol other than the communication protocol used to request the data. The request can include what data to transmit (e.g., the last 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 or more data points), the type of data (e.g., sensor data or electronics unit log), the time frame of the data (e.g., including a timestamp), and so on. As an illustrative example, the second communication protocol used by the display device 20 to request the sensor electronics unit 6 to transmit the data can utilize an RF field such as NFC or RFID. The second communication protocol used to transfer the data can be a wireless communication such as BLUETOOTH. Advantageously, transmitting the data over a wireless communication instead of an RF field can allow for faster transfer speeds and transfer over longer distances. For example, if it is desired to retrieve data on the display device 20, the user can use the display device 20 to initiate a data transfer from the sensor electronics unit 6 to the display device 20 using an RF field such as NFC or RFID, and then move away while transferring the data through wireless transmission such as BLUETOOTH. If the data is transferred through NFC, it may take longer and / or the user may have to remain close to the sensor electronics unit 6. Having the flexibility to move around, including moving away, during data transfer can be advantageous when medical personnel are treating the user and other patients.

[0119] In some cases, the command to transmit data can be a command requesting that data be transmitted over NFC, which may be desirable when security is important (e.g., the user only wants to transmit data to nearby devices), when the sensor electronics has little or no battery power remaining, and / or in any situation desired by the user. In some implementations, determining when to use NFC for data transfer can be determined by the display device 20 or the sensor electronics unit 6, such as using NFC when only a small amount of data is to be transferred.

[0120] A white / bonding list can be configured using the white / bonding list configuration unit 658. In some communication protocols, such as wireless transmission communication protocols, there can be one or more white lists and / or bonding lists that can be used by the sensor electronics unit 6 to manage connected devices. The role of the white list can include a list of devices with which the sensor electronics unit 6 can be paired and / or pairing information of the devices (e.g., timing information, encryption keys, authentication information, advertising parameters, addresses, make / model, name, General Access Profile ("GAP"), Identity Resolution Key ("IRK"), etc.). In some cases, the white list can be stored and updated in the memory of the sensor electronics unit 6. In some implementations, there can be a predetermined number of slots in the white list, such as one, two, three, four, five, or more slots. Display devices listed in the white list can be connected for communication with the sensor electronics unit 6. For example, but not limited to, the display device 20 can be added to the white list, and then pairing information from the display device 20 can be retrieved from the bonding list by the sensor electronics unit 6. When a display device 20 is connected, the whitelist is updated to allow that particular display device 20, and any other display devices on the whitelist, to connect.

[0121] The bonding list may include a predetermined number of slots, such as one, two, three, four, five, or more slots. The bonding list may be stored in memory and, in some cases, maintained by an application on the sensor electronics unit 6 or on the display device (e.g., display device 20). The bonding list may include authentication and / or pairing information (e.g., timing information, encryption keys, authentication information, advertising parameters, addresses, make / model, name, GAP, IRK, etc.) for a predetermined number of display devices. A display device whose information is on the bonding list may or may not be on the whitelist.

[0122] In some cases, the display device 20 may not be on the whitelist. It may be desirable and convenient for the user to place the display device 20 since the user is currently using the display device 20. For example, but not limited to, if the user uses a receiver, but then uses a smartphone and wants to leave the receiver elsewhere, the user may want to quickly add the smartphone to the whitelist. As described later in this disclosure with reference to FIG. 9A, in some cases, the white / bonding list setting unit 658 may include sending a command to add the display device 20 to the whitelist of the sensor electronics unit 6 along with the pairing information of the display device 20. This information may be added to any free slot in the whitelist. In some implementations, as discussed later in this disclosure with reference to FIG. 9C, the white / bonding list setting unit 658 may include removing the display device 20 from the whitelist, so that the sensor electronics unit 6 does not communicate with the display device and the sensor electronics unit 6 and the display device 20 do not inadvertently connect. For example, a user may have multiple display devices (including display device 20) and may not want the same alerts to be notified on all of the display devices.

[0123] In some cases, as discussed later in this disclosure with reference to FIG. 9D, the sensor electronics unit 6 may communicate with each display device 20 on its whitelist in a particular order, such as consecutive order (e.g., starting with the first slot and proceeding to the nth slot). In one such case, some slots allow the display device 20 to connect and receive information relatively faster than other slots in the same whitelist. For example, but not limited to, some slots on the whitelist allow devices to connect only less frequently than other slots, such as every 20 minutes instead of every 5 minutes. Also, different slots in the whitelist may have different parameters associated with them that may affect, for example, but not limited to, the reliability of the connection. Thus, along with a command to add the display device 20 to the whitelist of the sensor electronics device and any other associated data desired (e.g., pairing information), the white / bonding list configuration unit 658 may include a request to add the display device 20 to a particular slot in the whitelist. For example, but not limited to, the display device 20 may request to be added to the first slot. Advantageously, this allows display device 20 to have a more reliable connection and / or faster receipt of data in some circumstances.

[0124] In some cases, adding a display device 20 to the whitelist may affect other display devices in the whitelist. If the requested slot in the whitelist is free, the information (e.g., pairing information) of the display device 20 may simply be added to the free slot. However, other situations may exist. For example, but not limited to, if a display device 20 requests to be added to a slot that is already filled, the white / bonding setting list unit 658 may include instructions to be performed by the display device already occupying it. In some cases, as discussed later in this disclosure with reference to FIG. 9D, the white / bonding list setting unit 658 may include a request to remove a display device occupying a desired slot of the new display device 20. In this manner, the already occupying display device may be removed from the whitelist (and in some cases, from the bonding list as well). In other cases, as discussed later in this disclosure with reference to FIG. 9E, the white / bonding list setting unit 658 may include a request to shift a display device to a subsequent designated slot and remove the display device in the last slot. For example, and without limitation, in the case where there are three slots in the whitelist numbered 1 through 3, each filled, the whitelist / bonding list unit 658 may include a request to add a pairing indication device to slot 1. A temporary whitelist may be created in memory that holds the contents of the previous whitelist. Then, information from the previous slot 1 may be placed in slot 2, and information from the previous slot 2 may be placed in slot 3. Thus, information from the previous slot 3 may not be added to the whitelist.

[0125] In some cases, the white / bonding list setting unit 658 may also indicate which display devices should be removed from the white list. In the previous example, the white / bonding list setting unit 658 may include a request to add the current display device to slot 1 and remove the previous display device in slot 2, and shift the devices accordingly. In that situation, the new display device is added to slot 1, the previous display device in slot 1 is added to slot 2, and the display device in slot 3 remains as is.

[0126] The white / bonding list configuration unit 658 may also include any number of reorderings of the whitelist. In some cases, the whitelist may be reordered without adding any new devices. Advantageously, this allows a user to dynamically adjust their preferences. In such a situation, the white / bonding list configuration unit 658 may include one or more requests instructing the sensor electronics unit 6 how to reorder the whitelist and / or where to advance each device. In some cases, if the display device 20 has prior information about the whitelist of the sensor electronics unit 6 (e.g., a previous exchange of the whitelist and / or the structure of the whitelist from the sensor electronics 6 to the display device 20), this may include a whitelist map (e.g., a bitmap and / or pointers indicating how to reorder the whitelist) transmitted to the sensor electronics unit 6 that informs the sensor electronics unit 6 of which other slots to send the contents of each slot to. The whitelist map may include a pointer or address that indicates, at least in part, which slot of the display device currently listed on the whitelist should be advanced. For example, each entry (e.g., a vector or matrix) in the whitelist map may correspond to a slot in the whitelist. Each entry in the whitelist map may include at least the address of the slot to which a current entry in the whitelist should be moved in the updated whitelist. In other implementations, the white / bonding list configuration unit 658 may include an entirely new whitelist that is used by the sensor electronics unit 6 to replace its previous whitelist.

[0127] The bonding list may be configured as a separate action or for inclusion in the white / bonding list unit 658. Configuring the bonding list may include commands to add or remove items from the bonding list. Typically, the order of the bonding list has no effect on the user, but the user may change the order of the bonding list and / or reorder the bonding list in a manner similar to that described above with respect to the white list, including commands to add and / or remove specific display devices from specific slots (e.g., identified by display device and / or slot number) of the bonding list. The bonding list may include more slots (e.g., store more devices) than the white list.

[0128] The operational modes unit 659 can include setting operational modes, including requests to put the sensor electronics unit 6 into shelf mode, low power mode, normal operation, power up, sleep, transmission, idle, battery management (e.g., energy efficient to reduce energy consumption, such as by using communication protocols that use RF fields, such as NFC or RFID, instead of wireless transmissions, such as BLUETOOTH), and / or any desired mode and / or status.

[0129] The clone unit 649 may include cloning the sensor electronics unit 6. Cloning may include receiving and / or transmitting one or more parameters of the sensor electronics unit 6 to configure a second sensor electronics unit. As an illustrative example, in some cases, a user may wish to completely clone the sensor electronics unit 6 by transferring the data and / or configuration (e.g., pairing information, calibration data, timing, whitelist, bonding list, etc.) of the sensor electronics unit 6 to another, second sensor electronics unit. As another illustrative example, only a subset of the data and / or configuration of the sensor electronics unit 6 may be transferred. Such may be desirable when a user only wishes to clone a particular aspect of the sensor electronics unit 6. In some cases, pairing information may not be transferred between the sensor electronics unit 6 and the second sensor electronics unit, as that information is device specific and may vary between units. In any of these cases, the clone unit 649 may transfer one or more parameters of the sensor electronics unit 6 to the second sensor electronics unit using a communication protocol.

[0130] As an illustrative example, in some cases, the sensor electronics unit 6 and the display device 20 can transfer data using a first communication protocol, typically wireless transmission (e.g., BLUETOOTH). If a second communication protocol utilizing an RF field, such as NFC or RFID, is used in the sensor electronics unit 6, the clone unit 649 can transfer data and / or configuration from the sensor electronics unit 6 onto the display device 20 using the second communication protocol. The display device 20 can store the data and / or configuration in memory. In some cases, this transfer can occur while the sensor electronics unit 6 is still in low battery and / or after the sensor electronics unit 6 battery has run out and powered the transfer also using a second communication protocol, such as NFC. In some cases, before the sensor electronics unit 6 battery runs out, the sensor electronics unit 6 can upload the sensor electronics unit 6 data and / or configuration to an NFC tag, which can facilitate passive transfer. In some implementations, the first communication protocol may be used to actually transfer data from one display device to the other, although the second communication protocol may be used to initiate cloning. As an illustrative example, the first communication protocol may be a wireless transmission, such as BLUETOOTH. The display device 20 may initiate cloning of the sensor electronics unit 6 via a second communication protocol, which may utilize an RF field, such as NFC or RFID. The sensor electronics unit 6 may then transfer its data and / or configuration to either the second sensor electronics unit or the display device 20 via the first communication protocol. If the data and / or configuration is transferred to the display device 20, the display device 20 may then transfer the data and / or configuration to the second sensor electronics unit via a communication protocol, such as the first or second communication protocol, or any other communication protocol described in this disclosure.Display device 20 can then transmit the data and / or configuration to a second sensor electronics unit, which in some cases can use the data and / or configuration to set itself up substantially similar to sensor electronics unit 6 (e.g., with substantially similar pairing, configuration, calibration, etc.).

[0131] FIG. 6A illustrates an exemplary interface 620 through which a user can select functions corresponding to the functional units illustrated in FIG. 5C from the display device 20. The interface 620 can be part of a mobile application (e.g., a mobile application downloaded from an entity that creates and / or owns and / or licenses the app, and / or from an app store such as by APPLE, INC. or GOOGLE INC., or from another company) that performs functions and / or has a structure described throughout this disclosure, including with reference to FIG. 5C. The interface 620 can include visual, audio, and / or tactile elements to interact with a user using the display device 20. The interface 620 can be instantiated on the user interface 409 (illustrated in FIG. 4A). A user can use the interface 620 to access various functions of the display device 20.

[0132] In some cases, the interface 620 may have multiple panels that display information and / or allow user interaction. For example, without limitation, the panel 610 may include a field that indicates information of the sensor electronics unit (e.g., sensor electronics unit 6). In some cases, by selecting a field, a user may select the sensor electronics unit to use the sensor functions. The sensor electronics unit may be identified by a serial number, an alias, a name, a code, and / or any desired identifier. In some implementations, the identifier may be entered manually and / or selected from a list of available (e.g., previously entered, detected, and / or paired) sensor electronics units. The panel 611 may describe the status of the sensor electronics unit identified in the panel 610. As some non-limiting examples, the status may include one or more of shelf mode, low power mode, normal operation, booting, sleep, transmitting, idle, low battery, and / or any status description. These statuses can be retrieved and displayed by interface 620 through a server (e.g., a network, cloud, etc.) to which the sensor electronics unit sends such status, through other communication protocols (e.g., wireless transmission or any of the communication protocols described in this disclosure), and / or through a previous transmission containing status information from the sensor electronics unit (e.g., via wireless transmission, RF field, and / or any other communication protocol described in this disclosure). Panel 612 can describe the pairing status of the display device 20 with respect to the sensor electronics unit displayed on panel 610. As a non-limiting example, a status of unpaired can indicate that the sensor electronics unit is not paired with the display device 20 through a communication protocol (e.g., wireless transmission such as BLUETOOTH and / or any other communication protocol described in this disclosure).Other examples may include paired (e.g., the sensor electronics unit is paired with the display device 20 through the communication protocols described in this disclosure), advertising, on a whitelist, on a bonding list, and / or any other pairing status.

[0133] The panel 613 may include user selectable fields on the interface 620 that, when selected, may cause the display device 20 to initiate a corresponding action. The panel 613 may include actions that a user may take with respect to the sensor electronics units displayed on the panel 610. Such actions may include an action 614, which may be a wake action that performs a function at least partially corresponding to a wake unit 654, an action 615, which may be a pairing action that performs a function at least partially corresponding to a pairing unit 655, an action 616, which may be a calibration action that performs a function at least partially corresponding to a calibration unit 656, an action 617, which may be a data retrieval action that performs a function at least partially corresponding to a data retrieval unit 657, an action 618, which may be a white / bonding list setting action that performs a function at least partially corresponding to a white / bonding list setting unit 658, an action 619, which may be an operational mode action that performs a function at least partially corresponding to an operational mode unit 659, and an action 609, which may be a clone action that performs a function at least partially corresponding to a clone unit 649. The user can add such actions 614, 615, 616, 617, 618, 619, 609 to a queue 630 (illustrated in FIG. 6B), which can constitute a list of actions stored in memory. The actions on the queue can then be used to transmit appropriate commands, data / information, etc., to perform such actions. These actions can be added to the queue 630 by selecting the action through an interface 620 (e.g., by touching, clicking, pressing, etc., an option on a touch screen, or by inputting using a keyboard, mouse, and / or any other device). Those skilled in the art will recognize that other actions than those previously listed can also be included in the actions 613. When the user wishes to transmit one or more actions selected from the panel 613, the user can select a button 634, which can then open an interface 640 for transmission. FIG. 6B illustrates one such interface.

[0134] 6B illustrates an example interface 640 for performing actions in the action queue 630 through NFC. The action queue 630 can be comprised of actions selected from the action 613 (e.g., one or more of actions 614, 615, 616, 617, 618, 619, 609) and / or other actions. In this example embodiment, the instructions are transmitted from the display device 20 to the sensor electronics unit 6 via NFC, although other communication protocols can be used, including wireless transmission, RF fields, and / or any other communication protocols described in this disclosure. The graphic 632 can show instructions to the user, instructing the user to hold the display device 20 close to the sensor electronics unit 6. In some cases, such instructions can instruct the user to tap the display device 20 against the sensor electronics unit 6 and / or hold the display device 20 close to the sensor electronics unit 6. Once the display device 20 is placed within range of the sensor electronics device 6, the sensor electronics unit 6 can then perform an item in the action queue 630. In some cases, the display device 20 may also display a prompt, for example to indicate that the display device 20 is currently connected via NFC. A. Wake-up and transition to low power mode

[0135] In some implementations, the sensor electronics unit 6 can be placed in a low power mode, such as a shelf mode, after manufacture to conserve battery power. This placement can be done at the factory for shipping (e.g., as described with reference to FIG. 1B ) and / or by a user if the user wants to conserve the battery in the sensor electronics unit 6. Once the user decides to start using the sensor electronics unit 6, the sensor electronics unit 6 can be placed in its normal operating mode. In some cases, waking up the sensor electronics unit 6 can be difficult because the sensor electronics unit 6 may not have a user interface and / or may not be actively transmitting to connect to a display device (e.g., display device 20) that can initiate a command to wake it up.

[0136] As discussed above, in some cases, the sensor electronics unit 6 can wake up the sensor electronics unit 6 from a low power mode using activation of a continuous analyte sensor 8 that is communicatively and / or operatively coupled to the sensor electronics unit 6. The sensor electronics unit 6 can be attached to the continuous analyte sensor 8 by electrodes that allow a current (or voltage) to flow between the sensor electronics unit 6 and the electrodes. When the sensor electronics unit 6 detects a current (or voltage) indicative of attachment to the continuous analyte sensor 8, the sensor electronics unit 6 can wake up from a low power mode. However, this manner of waking up the sensor electronics unit 6 can have drawbacks in some situations. For example, but not limited to, a user can unintentionally wake up the sensor electronics unit 6 by touching their finger across the electrodes and / or otherwise causing a change in the current across the electrodes of the sensor electronics unit 6. In some cases, the sensor electronics unit 6 may also not sense a current across the electrodes all the time. Rather, sensing may only occur periodically, such as every 5, 10, 15, or more minutes. In such cases, the user may have to wait a significant amount of time before the sensor electronics unit 6 detects a current across its electrodes and wakes up from a low power mode. This may result in a poor user experience.

[0137] In some cases, the sensor electronics unit 6 in the low power mode can derive its operating power from an RF field associated with the display device 20 using electromagnetic radio waves for communication. For example, a communication protocol such as, but not limited to, NFC or RFID can be used by the display device 20 to create an RF field that allows the display device 20 to communicate with the sensor electronics unit 6 in the low power mode. Advantageously, this communication protocol (e.g., NFC or RFID) can be used by the display device 20 to wake up the sensor electronics unit 6 from its low power mode. The following description of waking up the sensor electronics unit 6 can be part of an action 614 that utilizes the wake unit 654. In some implementations, the action 614 can be part of an action queue 630, and multiple actions (e.g., actions in action 613) can be performed.

[0138] FIG. 6C illustrates an example timing diagram for waking the sensor electronics unit 6 from a low power mode using an RF field. The example timing diagram is a timing diagram of the sensor electronics unit 6. The sensor electronics unit 6 can initially be in a low power mode (e.g., shelf mode and / or any other low power mode) for a period 602, consuming less power compared to at least one other power mode (e.g., normal operation mode). As discussed throughout this disclosure (e.g., with reference to FIGS. 1B, 5C), the low power mode can be used during shipping and / or hibernation periods of the sensor electronics unit 6. The transmission 604 can be performed using a communication protocol that utilizes an RF field, such as NFC or RFID, when the sensor electronics unit 6 is in the low power mode. The transmission 604 can be sent to the sensor electronics unit 6 using the display device 20. In some implementations, the transmission 604 can include a wake action, such as action 614, and / or the action 614 can also include the transmission 604. The transmission 604 may include command(s), data, status(es), and / or any other desired transmission. The wake action may also include and / or be combined with other actions, such as any of the actions of action 613. For example, without limitation, the command may include instructions requesting the sensor electronics unit 6 to wake up (e.g., action 614) and / or proceed to a normal operating mode (e.g., action 659), such as an operating mode that allows for receipt of measurements indicative of a user's glucose measurements and / or transmission of data between the sensor electronics unit 6 and the display device 20. In some cases, the sensor electronics unit 6 may advertise to the display device 20 of its normal operating mode. This advertising may begin immediately or substantially immediately after the sensor electronics unit 6 wakes up from the low power mode.

[0139] In some implementations, other commands can instruct the sensor electronics unit 6 to perform tasks such as reading data and / or current / voltage from the continuous analyte sensor 8 and / or sending data, status, commands to the display device 20, etc. The commands can also include commands for changing operational modes, calibrating the measurement circuitry, turning on / off the sensor circuitry, adjusting defined parameters or pre-settings, etc. These commands can also include any of the commands described with respect to actions 613. In some cases, the transmission 604 can include energy (e.g., energy transmitted for powering via NFC) that can be used to power the reception of the command and / or any steps desired to perform the command from the display device 20 delivered to the sensor electronics unit 6. For example, without limitation, the transmission 604 can include energy from the sensor display device 20 sent to the electronics unit 6 (e.g., via NFC) so that the sensor electronics unit 6 can receive a wake-up command and increase its power usage. In some cases, the power received by the sensor electronics unit 6 can enable the sensor electronics unit 6 to go from a low power mode to a normal power mode. Once the sensor electronics unit is in the normal power mode, it can then power its own operation. In some cases, the energy received by the sensor electronics unit 6 can power all transitions from the low power mode to a higher power mode (e.g., all actions / steps taken by the sensor electronics unit 6). In some cases, the energy received by the sensor electronics unit 6 does not power all transitions to the normal power mode, but can sufficiently power the sensor electronics unit 6 to receive a command to change from the low power mode to the higher power mode.

[0140] The data from the display device 20 transmitted to the sensor electronics unit 6 in transmission 604 may include data regarding the display device 20 (e.g., serial number, authentication, security information, make / model, etc.). In some cases, this data (alone or in combination with transmitted commands, status, etc.) may facilitate pairing between the sensor electronics unit 6 and the display device 20 using other communication protocols. The status may include the status of the display device and / or any information regarding the functionality of the display device (e.g., ready, standby, error in operation, etc.). During, after, or both during and after transmission 604, in a period 606, the sensor electronics unit 6 may proceed to normal operation. The period 606 may occur after a time delay 608 from transmission 604. The time delay 608 may be a predetermined delay (e.g., 5 seconds, 4 seconds, 3 seconds, 2 seconds, 1 second, or less).

[0141] If NFC or RFID is used, the transmission 604 can be sent using a "tap to start" initiation. Specifically, if NFC is used, NFC can have a range that is on the order of centimeters (e.g., 10 centimeters or less), and the user can bring the display device 20 close to and / or touch the sensor electronics unit 6 to send the transmission 604. Such physical interaction can be advantageous by providing the user with a physical initiation that can be intuitive. As described throughout this disclosure, a "tap to start" initiation can be desirable in a variety of cases. By way of example and not by way of limitation, a "tap to start" initiation can be used to wake up the sensor electronics unit 6 from a low power mode. This can also generally be used to change the power mode of the sensor electronics unit 6 (e.g., to shelf, mode, normal operation, high power mode, etc.) when desired. In some instances, NFC can be used to transmit commands, data, calibration information, etc. between the display device 20 and the sensor electronics unit 6. Desirably, using NFC generally or in a "tap to start" initiation can be advantageous to allow a user to change settings on the sensor electronics unit 6 without going through multiple steps for pairing and / or authentication (e.g., as with BLUETOOTH). Such use of NFC can also enable reliable data and command transmission, and can be done on demand, without having to wait for transmission timing of other communication protocols such as BLUETOOTH.

[0142] In some implementations, normal operation during time period 606 may include utilizing communication of the protocol of transmission 604. In some implementations, normal operation during time period 606 may include using a second communication protocol, such as a communication protocol utilizing wireless transmission. In some implementations, this second communication protocol may not be the same communication protocol as the first communication protocol. As an illustrative example, this second communication protocol may include BLUETOOTH. In some implementations, after transmitting data via the second communication protocol, the sensor electronics unit 6 may return to a low power mode.

[0143] FIG. 6D illustrates an example flow chart illustrating the process described in FIG. 6C. In some cases, a user of the display device 20 may want to use the method 620 when they want to pair their display device 20 to the sensor electronics unit 6 substantially on-demand. For example, but not limited to, some whitelists may only allow the display device 20 to connect at a predetermined interval, such as every 20 minutes. Instead of waiting for that timing, the user may want to connect the display device 20 to the sensor electronics unit 6 substantially immediately. By way of example, the user may want to immediately add the display device 20 to the whitelist during an emergency situation where there are no other display devices available for use. The sensor electronics unit 6 may sense analyte measurements of the user or of someone else (e.g., someone under the user's care). Thus, the user may use the method 620 to pair the display device 20 to the sensor electronics unit 6 on-demand to facilitate assistance during an emergency situation. As another illustrative example, a health care worker may want to immediately pair the display device 20 to a patient's sensor electronics unit 6 as the health care worker makes rounds. Because the health care worker may not have the time to wait for the whitelist's predetermined time interval, the health care worker may suitably use method 620 to immediately connect with the user's sensor electronics unit 6. As another illustrative example, a user may simply find it inconvenient to wait the predetermined time interval to connect the sensor electronics unit 6 to the display device 20. Thus, such a user may want to use method 620 to connect the display device 20 to the sensor electronics unit 6 substantially on-demand.

[0144] At block 622, the sensor electronics unit 6 can operate in a low power mode. At block 624, the sensor electronics unit 6 can receive a signal using a first communication protocol. As an illustrative example, a second communication protocol can utilize an RF field, such as NFC or RFID, by the sensor electronics unit 6 and / or the display device 20. The transmission can include commands, such as, but not limited to, commands for pairing the first communication protocol, changing the operating mode, calibrating the measurement circuitry, turning on / off the sensor circuitry, adjusting defined parameters or pre-settings, and the like. The transmission can also include any action, such as, but not limited to, action 613. By way of example, but not limited to, the transmission can include multiple actions queued by a user using the display device 20. In some cases, such actions can include one or more of an operating mode action (e.g., action 619), a pairing action (e.g., action 615), and / or a white / bonding list setting action (e.g., action 618). Advantageously, the operation mode action allows the sensor electronics unit 6 to switch from a low power mode to a different operation mode, such as a normal operation mode. The pairing action can allow the display device 20 to communicate with the sensor electronics unit 6 using a second communication protocol to pair with the sensor electronics unit 6 using a first communication protocol. For example, a second communication protocol using an RF field, such as, but not limited to, NFC or RFID, can be used to pair the sensor electronics unit 6 with the display device 20 by exchanging pairing information of the first communication protocol for communication using the first communication protocol, such as using wireless transmission (e.g., BLUETOOTH). As described herein, the whitelist setting action can be used to change the order of the whitelist of the sensor electronics unit 6 for the first communication protocol, as desired.In some cases, the action may include instructions on how to reorder the whitelist, a pointer to change the whitelist, a copy of the new whitelist, and / or any other manner of setting the whitelist described in this disclosure (e.g., as described above with reference to FIGS. 5C, 6A). Other actions described in this disclosure may also be used. Advantageously, this allows for user flexibility and convenience in setting up a connection. In some implementations, the display device 20 may autonomously determine which actions to queue based at least in part on the user's usage patterns (e.g., based on the use of one or more of the actions 614, 615, 616, 617, 618, 619, 609 at a particular time of day and / or in a particular situation, such that the display device 20 learns to initiate the same one of the actions 614, 615, 616, 617, 618, 619, 609 at the same time of day and / or in the same situation) and / or the needs of the display device 20 (e.g., to retrieve missing data), etc.

[0145] Next, in block 626, the sensor electronics unit 6 may change from the low power mode to a desired operating mode. As illustrative examples, various operating modes may be used, such as, but not limited to, a normal operating mode, a calibration mode, a blind mode (e.g., a mode in which all or some data is not displayed on the display device 20), and / or any desired mode. In some cases, in block 626, the desired operating mode may be a normal operating mode.

[0146] At block 628, the sensor electronics unit 6 can then communicate using a first communication protocol, including wireless transmission, such as, but not limited to, BLUETOOTH and / or any other communication protocol described in this disclosure. Because the sensor electronics unit 6 has already received information, such as pairing information, over the second communication protocol, when communicating using this first communication protocol, it can communicate without further user interaction.

[0147] In some implementations, instead of waking up the sensor electronics unit 6 from a low power mode, such as shelf mode, a user may want to place the sensor electronics unit 6 in a low power mode for another mode of operation. For example, without limitation, a user may only want to monitor glucose once a week or once a month. Some sensor electronics units 6 may have a predetermined (or limited) battery life remaining, so placing the sensor electronics unit 6 in a low power mode can enable the sensor electronics unit 6 to be used for a few more days.

[0148] FIG. 6E illustrates an example timing diagram of the sensor electronics unit 6 entering a low power mode. In period 652, the sensor electronics unit 6 can have normal operation or any operation that uses more power / energy than the low power mode. In normal operation, the sensor electronics unit 6 can communicate using one or more communication protocols, such as any communication protocol described in this disclosure, including wireless transmissions such as BLUETOOTH. In some implementations, a transmission 654 can place the sensor electronics unit 6 in a low power mode during period 656 using a command to instruct the sensor electronics unit 6 to enter a low power mode and / or a command such as a start low power command. The period 656 can occur after a time delay 658 from the transmission 654. The time delay 658 can be a predetermined delay (e.g., 5 seconds, 4 seconds, 3 seconds, 2 seconds, 1 second, or less). The transmission 654 can be made using any communication protocol described in this disclosure. As illustrative examples, the transmission 654 may be performed using an RF field for communication, such as NFC or RFID, or using wireless transmission, such as BLUETOOTH. If NFC is used, the user may bring the display device 20 close to and / or touch the sensor electronics unit 6 to send the transmission 654, since NFC may have a range that is on the order of centimeters (e.g., 10 centimeters or less). Such physical interaction may be advantageous by providing a physical initiation that may be intuitive to the user. Since the display device 20 may be far away from the sensor electronics unit 6 and / or may already be in communication with the sensor electronics unit 6 through wireless transmission, such as BLUETOOTH, it may be advantageous to use wireless transmission, such as BLUETOOTH.

[0149] In some implementations, the low power mode can be a shelf mode or other power mode that uses less power. For example, but not limited to, as described with reference to FIGS. 1B, 6A, the low power mode can be a mode that turns off one or more of the transmission circuitry (e.g., BLUETOOTH radio), the measurement circuitry, the sensor circuitry, the processor, etc. Also, the frequency of refreshes, advertisements, analysis of measurements, and / or any other periodic operations of the sensor electronics unit 6 can be reduced. The sensor electronics unit 6 can be later woken up in a process substantially similar to that described with respect to FIGS. 6C-D.

[0150] 6A-B in this disclosure, a wake action (e.g., action 614 and / or other waking actions described in this disclosure) may be performed in combination with other actions, such as one or more of actions 613. These actions may be performed in a queue, such as action queue 630. For example, without limitation, waking up the sensor electronics unit 6 may be combined with any one or more of actions 614, 615, 616, 617, 618, 619, 609. B. Asynchronous communication

[0151] In some cases, communications sent by the sensor electronics unit 6 may follow a particular communication pattern, such as, but not limited to, the communication patterns described with reference to FIGS. 6C, 6E. However, in some cases, a user may desire to send / receive communications that do not follow the timing of that communication pattern. By way of example, but not limited to, a data retrieval action, such as action 617, may be used by the display device 20 to retrieve data from the sensor electronics unit 6 outside of the communication pattern. As discussed in this disclosure, a data retrieval action (e.g., action 617 and / or other waking actions described in this disclosure) may be performed in combination with other actions, such as one or more of actions 613. These actions may be performed in a queue, such as action queue 630.

[0152] 7A illustrates an example timing diagram of an example first communication protocol of the sensor electronics unit 6. Measurement line 704 illustrates that the sensor electronics unit 6 can receive measurements substantially constantly. Measurement line 704 can represent analog and / or digital measurements. In the case of digital measurements, the solid lines of measurement line 704 can represent the repeated receipt of discrete digital data measurements.

[0153] Communication line 702 illustrates the timing of a first communication protocol in which the sensor electronics unit 6 sends communications to one or more display devices 20A-N indicative of measurements taken. At these times, the sensor electronics unit 6 may also receive communications. For example, but not limited to, wireless transmissions such as BLUETOOTH® may be used as the first communication protocol on communication line 702 to transmit data indicative of blood glucose measurements from the sensor electronics unit 6 to the display device 20. Communications may occur periodically, such as occurring at times 708, 710, 712, 714.

[0154] In some implementations, the time between each successive time 708, 710, 712, 714 can be 5 minutes, 10 minutes, 15 minutes, 20 minutes, or more, as desired. At each of the times 708, 710, 712, 714, the sensor electronics unit 6 can transmit a communication along the communication line 702. As a non-limiting example, at the time 708, a communication window between the sensor electronics unit 6 and the display device 20 can be initiated by a rising edge 716. The sensor electronics unit 6 can then actively transmit / receive communications for a predetermined amount of time on edge 718, during which the communication window opens. For example, without limitation, the predetermined amount of time can be 10 seconds, 15 seconds, 20 seconds, 25 seconds, 30 seconds, 35 seconds, 40 seconds, or any desired number of seconds. The communication window can then be closed by a falling edge 720. In some instances, the amount of time can be related, at least in part, to the amount of data being transmitted and / or the time of transmission of that data.

[0155] As an illustrative example, but not by way of limitation, times 708, 710, 712, 714 and the relationship of said times may indicate how often communication occurs, which may be variable based on a predefined transmission frequency based on user-defined settings and / or activity. For example, but not by way of limitation, a period of 5 minutes or less between two consecutive measurement transmissions (e.g., between time 708 and time 710, between time 710 and time 712, and / or between time 712 and time 714) may be used when a user desires to have very regular and / or frequent data points regarding their blood glucose level. Such regular and / or frequent data points may be desirable when a user goes through normal activities, such as walking, working, daily exercise, driving, etc., so that the user may analyze trends in their activity. As another non-limiting example, a period of 20 minutes or more may be used between two consecutive measurement transmissions (e.g., between time 708 and time 710, between time 710 and time 712, and / or between time 712 and time 714) when a user does not desire many data points. For example, but not limited to, a user's blood glucose level may be relatively normal or stable. By transmitting measurement data less frequently, a user may extend the life of the sensor electronics unit 6 and / or the continuous analyte sensor 8. As another non-limiting example, the period between two consecutive measurement transmissions (e.g., between time 708 and time 710, between time 710 and time 712, and / or between time 712 and time 714) may be dynamic and / or variable based on activity and / or condition. For example, a shorter period may be used when a clinically risky situation is detected, such as a condition at least partially indicative of a hyperglycemic or hypoglycemic event. In such a situation, the sensor electronics unit 6 and / or display device 20 can detect when the user's blood glucose level falls below a threshold hypoglycemic glucose level or above a threshold hyperglycemic glucose level.In such cases, the sensor electronics unit 6 can increase its connection establishment frequency so that the period between two successive measurement transmissions is reduced. As another example, since there may be a risk of a diabetic patient having a hypoglycemic condition while sleeping, the sensor electronics unit 6 and / or the display device 20 can detect when the user is sleeping and transmit measurement data more frequently. The period between successive measurement transmissions can also be variable with respect to a predefined schedule, such as transmitting more frequently during meal times. In some cases, the period between successive measurement transmissions can be set by sending a command and a period between such successive measurement transmissions through NFC or RFID so that the user can tap (or bring the display device 20 close enough to) the sensor electronics unit 6. Advantageously, this allows the user to set the frequency of measurement transmissions on demand.

[0156] FIG. 7B illustrates an example timing diagram of the sensor electronics unit 6 showing signal processing that may occur during communication of the first communication protocol of FIG. 7A. For example, but not limited to, the sensor electronics unit 6 may periodically perform signal processing on the measurement data during communication, such as communication on communication line 702. Signal processing line 722 illustrates the timing of the signal processing. As an illustrative example, but not limited to, a communication window may open at times 708, 710 as described with respect to FIG. 7A. Between times 708 and 710, a signal processor (e.g., a processor substantially similar to signal processor 308) may perform signal processing at times 724, 726, and / or other predefined times. Such signal processing may include any signal processing described in this disclosure. In some cases, the signal processing may include data aggregation operations, compiling and processing measurements taken since the last communication to determine, for example, trends in analyte measurements, blood glucose measurements, and / or other indications of the blood glucose level and / or health status of a user of the sensor electronics unit 6. In some cases, a conversion function may be used to convert the measured raw data into processed data, such as an estimated glucose value. Signal processing may also determine the user's condition (e.g., normal, hypoglycemic, hyperglycemic) and initiate alarms and / or notifications if there are any health concerns.

[0157] 7C illustrates an example transmission from the sensor electronics unit 6 using a second communication protocol to initiate communication using the first communication protocol from the example timing diagram of FIG. 7B. For example, but not limited to, the transmission 732 can utilize a second communication protocol, such as a communication protocol utilizing an RF field, including but not limited to NFC or RFID, on the communication line 706. The transmission 732 can further include a command to initiate communication along the first communication protocol (e.g., utilizing a wireless transmission such as BLUETOOTH), the timing of which is represented by the communication line 702. Other transmissions in the transmission 732 can include transmissions associated with data retrieval actions, such as action 617. The communication can occur after a time delay 736, which can be a predetermined delay (e.g., 5 seconds, 4 seconds, 3 seconds, 2 seconds, 1 second, or less). For example, but not limited to, the waveform 734 can represent an additional communication window opening. In some implementations, this additional communication window opening can transmit aggregate measurements as they are processed by the sensor electronics unit 6 prior to transmission 732. By way of example, and not by way of limitation, aggregate processed data from processing initiated at time 724 can be transmitted during transmission 734 in response to transmission 732. Transmission 734 can occur after a time delay 736 from transmission 732. Advantageously, in some implementations, transmission 734 can occur without changing and / or shifting the scheduled communication window opening on communication line 706. This ability to not change and / or shift the schedule of communication can allow a user to receive / transmit data without having to wait the entire communication timing (e.g., the period between time 710 and time 708) for the next communication, as would be the case if the communication schedule were changed.

[0158] In other implementations, instead of transmission 734, the transmission of data can utilize communication using a second communication protocol. For example, without limitation, the display device 20 can send a transmission 732 to the sensor electronics unit 6 to transmit recent data. The sensor electronics unit 6 can then return data to the display device 20 using the second communication protocol. C. Starting or Stopping a Sensor Session

[0159] In some cases, a user may wish to start a new sensor session and / or end a previous sensor session. For example, but not limited to, in some cases, a continuous analyte sensor 8 may have a particular life span for usage at the user. As an illustrative example, but not limited to, a user may use a continuous analyte sensor 8 for 1 day, 2 days, 3 days, 4 days, 5 days, 6 days, 7 days, 8 days, 9 days, 10 days, 14 days or more, or any amount of time the continuous analyte sensor 8 was constructed and functioning before changing the continuous analyte sensor 8. For example, but not limited to, the amount of time the continuous analyte sensor 8 may function may be referred to as a sensor session. Starting or stopping a sensor session may be performed in combination with other actions, such as one or more of actions 613. These actions may be performed in a queue, such as action queue 630.

[0160] By way of illustrative background, components of the sensor electronics unit 6 may be replaced periodically. For example, without limitation, a continuous analyte sensor 8 may be attached to the sensor electronics unit 6, and it may be desirable to replace the continuous analyte sensor 8 periodically (e.g., every 7-30 days). The sensor electronics unit 6 may be configured to be powered and / or activated for much longer than the continuous analyte sensor 8, and the sensor electronics unit 6 may have power for one, two, three, four, five, six, or more months before its power source (e.g., battery and / or power source 303) runs out. Replacing these components may be difficult and costly, including time and monetary costs for assistance by trained personnel. Reducing the replacement of such components, including batteries, if replaceable, greatly improves the convenience of the sensor electronics unit 6 to users.

[0161] In some implementations, the sensor electronics unit 6 can connect to the continuous analyte sensor 8 when it is first used (or in some cases, when it is rebooted after a battery change). The display device 20 and the sensor electronics unit 6 can initially establish communication when the sensor electronics unit 6 is first used or rebooted (e.g., when the battery is changed). Once the display device 20 and the sensor electronics unit 6 have established communication, they can communicate periodically and / or continuously over the life of some sensors (e.g., continuous analyte sensors 8), until, for example, the battery or the entire sensor electronics unit 6 is replaced. Each time a sensor is replaced, notifications of new sensors can be sent / exchanged between the sensor electronics unit 6 and the display device 20 via a communication protocol (e.g., any communication protocol described in this disclosure).

[0162] According to some implementations, the sensor electronics unit 6 can collect and / or process sensor measurements from the continuous analyte sensor 8 and periodically transmit sensor information representative of the sensor measurements to the display device 20. The measurements can be collected and transmitted throughout the life of the continuous analyte sensor 8 (e.g., ranging from 1 to 30 days or more). In some cases, the measurements can be transmitted frequently enough to adequately monitor analyte levels, such as blood glucose levels. Rather than having the radio frequency ("RF") circuitry of the sensor electronics unit 6 and the display device 20 in continuous communication, the sensor electronics unit 6 and the display device 20 can regularly and / or periodically establish a communication channel between them. Thus, the sensor electronics unit 6 can wirelessly communicate with the display device 20 at predetermined time intervals. The duration of the predetermined time intervals can be selected to be long enough so that the sensor electronics unit 6 does not consume an undesirable amount of energy / power by transmitting data too frequently, yet frequent enough to provide substantially real-time sensor information (e.g., measured analyte values) to one or more of the display devices for output to a user. As described herein, transmission of this data may occur at predetermined time intervals and / or on an irregular / non-periodic basis, as desired.

[0163] A user may wish to start a sensor session after connecting a new sensor (e.g., continuous analyte sensor 8) to the sensor electronics unit 6. In starting a new sensor session, the sensor electronics unit 6 (and in some cases the display device 20) recognizes that a new sensor is being used and can initialize and calibrate the sensor. Similarly, a user may wish to stop a sensor when the user wishes to replace a sensor. Also, in some cases, a user may not start / end a sensor session during connection / disconnection to a sensor. Instead, as a non-limiting example, a user may wish to start / stop a user session to synchronize data collection until a certain time, stop collecting data, and / or reconnect after a poor connection between the sensor electronics unit 6, the sensor (e.g., continuous analyte sensor 8), and / or the display device 20. Having such a capability may enable a user to obtain data more quickly and / or have a better user experience. In some cases, it may be desirable to stop a sensor session when a sensor is no longer collecting data and / or the sensor is collecting bad data. Stopping the sensor session at this point can prevent bad data from continuing to be processed by the sensor electronics unit 6 and / or prevent the display device 20 from warning the user that no data is being collected and / or that bad data is being collected.

[0164] However, in some implementations, starting / stopping a sensor session may be unintuitive and / or cumbersome for a user. For example, but not limited to, returning to FIG. 7A, communication line 702 illustrates the timing of a first communication protocol, where the sensor electronics unit 6 opens a communication window and can also send / receive a communication indicative of a measurement taken by the display device 20. For example, but not limited to, the first communication protocol can utilize a wireless transmission, such as BLUETOOTH, which can be used to transmit data indicative of the blood glucose measurement. The communication window can be opened periodically, such as occurring at times 708, 710, 712, 714, etc. In this example, if the user wishes to start or stop a sensor session, the user can use a second communication protocol that is different from the first communication protocol. The second communication protocol can include a communication protocol that creates an RF field, such as NFC or RFID.

[0165] 7D illustrates an example timing diagram showing a transmission over a second communication protocol that stops a sensor session, such as the sensor session referenced in FIG 7A. In this example embodiment, the transmission 742 can utilize a second communication protocol, such as a communication protocol that creates an RF field along communication line 706, including NFC or RFID. The transmission 742 may include a command or instruction to stop the measurement and / or stop sending data over a wireless transmission (e.g., BLUETOOTH). Receipt of the transmission 742 may stop the measurement and communication along the first communication protocol on the communication line 702 (e.g., close communication over the communication line 702). In some implementations, after the transmission 742, there may be a delay before the measurement and communication along the first communication protocol is stopped. This delay may be a time delay 746 and may be a predetermined delay (e.g., 5 seconds, 4 seconds, 3 seconds, 2 seconds, 1 second, or less than 1 second) set by a user or automatically by the sensor electronics unit 6 and / or display device 20. After the time delay 746, the measurement on the measurement line 704 may be turned off.

[0166] FIG. 7E illustrates an example timing diagram showing the timing of a transmission over a second communication protocol that initiates a sensor session. In this example embodiment, the transmission 752 can utilize a second communication protocol, such as a communication protocol that creates an RF field along communication line 706, including NFC or RFID. Receipt of the transmission 752 can initiate measurement and communication along the first communication protocol along communication line 702. In some implementations, there can be a delay after the transmission 752 before the start of measurement and communication along the first communication protocol. This delay can be a time delay 756, which can be a predetermined delay (e.g., 5 seconds, 4 seconds, 3 seconds, 2 seconds, 1 second, or less than 1 second) set by the user or automatically by the sensor electronics unit 6 and / or display device 20. After the time delay 756, measurement on the measurement line 704 can be turned on. D. Pairing using multiple communication protocols

[0167] In some implementations, one communication protocol can be used to initiate pairing using another communication protocol. Such pairing can be performed as part of action 615 and / or as a separate action. As described in this disclosure, pairing actions (e.g., action 615 and / or other pairing actions described in this disclosure) can be performed by pairing unit 655 and in combination with other actions (e.g., one or more actions 613). These actions can be performed in a queue, such as action queue 630. Such pairing capabilities can be advantageous in improving the user experience. For example, but not limited to, some communication protocols have extensive pairing and / or authentication procedures. As a non-limiting example, wireless transmissions such as BLUETOOTH can utilize a handshaking procedure, where a device (e.g., display device 20) transmits authentication information and is selected from a list of available devices. Having too many steps in the procedure can impair the user experience and can also drain battery power and bandwidth due to excessive communication.

[0168] By way of background and as a non-limiting example, display device 20 may have a unique address, such as a unique 48-bit address that may be expressed as a 12-digit hexadecimal value. The address or a portion of the address may be used as an identifier for other devices over the same wireless transmission, such as BLUETOOTH, which may also have addresses for communication connections. BLUETOOTH devices may also have a user-friendly name that is provided to the device as seen in the display.

[0169] In this exemplary context, for BLUETOOTH and substantially similar wireless transmission protocols, a connection process using BLUETOOTH may have a number of steps. The first step may be an inquiry, where two BLUETOOTH devices (e.g., illustratively a first device and a second device) connecting for the first time make an inquiry to discover the other. The first device may send a request, where the second device responds with its address and possibly other information (e.g., its user-friendly name or any desired information). The inquiry request may include the address of the first device, or the address information may be sent in a separate transmission. The next step is a paging process, where the devices use the addresses obtained in the inquiry step to form a connection. The next step is a connection step, where the devices actually connect.

[0170] In some cases, during the initial connection, an authentication process can be used to pair the two devices, where the user validates the connection between the first and second device. The authentication flow can vary depending on the device's user interface. Sometimes pairing can be the click of a button, entering a numeric code, entering a common pin, entering an alphanumeric string, etc.

[0171] The BLUETOOTH® pairing process may involve too many steps and may prompt the user to enter information or take other actions, which may impair the user experience. There is a need to simplify the procedure for pairing this CGM device so that the user can more easily monitor their glucose levels on their device. Also, the sensor electronics unit 6 may not have a user interface, making it more difficult for the user to initiate pairing through some communication protocols such as wireless transmission (e.g., BLUETOOTH®). In many cases, communication protocols such as BLUETOOTH® allow the user to initiate and / or confirm pairing using the user interface of the display device 20. With an RF field such as NFC or RFID, the user can simply place the display device substantially next to the sensor electronics unit 6. This NFC or RFID capability may be advantageous when the sensor electronics unit 6 does not have a user interface.

[0172] 8 is an example flow chart showing how one communication protocol can be used to facilitate pairing for communication using another communication protocol. Process 800 can be performed by the sensor electronics unit 6 and / or display device 20 used with a CGM system.

[0173] In block 802, a first device (e.g., the sensor electronics unit 6 or the display device 20) can transmit address, pairing information (e.g., timing information, encryption key, authentication information, advertising parameters, address, make / model, name, GAP, IRK, etc.), commands, and / or other information to a second device (e.g., the sensor electronics unit 6 or the display device 20) using a second communication protocol. In some cases, the second communication protocol can utilize an RF field such as NFC or RFID. In particular, NFC or RFID can be advantageous because they can transmit data and / or information automatically, sometimes in a matter of seconds or even a split second. When in range, address, pairing, and / or other information can be transmitted from a device to another device. Advantageously, limited range NFC communication can enable additional security, in particular because only within the range can devices communicate via NFC. In some cases, NFC communications may be encrypted using algorithms such as 128-bit or 256-bit keys and / or other encryption algorithms that comply with standards such as the Advanced Encryption Standard ("AES"), RSA, Data Encryption Standard ("DES"), Triple DES, and the like.

[0174] In some implementations, block 802 may include transmitting encryption information. For example, but not limited to, the encryption may be encryption associated with the first communication protocol (e.g., BLUETOOTH encryption) or other encryption schemes, such as, but not limited to, using 128-bit or 256-bit keys and / or other encryption algorithms conforming to standards such as AES, RSA, DES, Triple DES, and the like.

[0175] In some implementations, block 802 can include transmitting parameters, which can include the frequency of advertising, the sequence of advertising (e.g., which devices are advertised, in what order, and with what signal), the type of display device 20 to be paired with, and / or other pairing information. Advantageously, this can facilitate pairing of the display device 20 and the sensor electronics unit 6, and can also enable battery management that can reduce excessive advertising.

[0176] Similarly, the second device may receive address, pairing, commands, and / or other information from the first device using the second protocol, at block 804. Pairing information may include timing information, encryption keys, authentication information, advertising parameters, address, make / model, name, GAP, IRK, and the like.

[0177] In block 806, the first device may then pair with the second device for communication over a first communication protocol, which in some implementations may be wireless transmission such as BLUETOOTH®.

[0178] As an illustrative example, process 800 may be part of a "tap to start" NFC protocol, where a user with a display device 20 may connect the display device 20 to the sensor electronics unit 6 of a CGM system by tapping (or bringing the display device 20 sufficiently close) to the sensor electronics unit 6. The tap may use an RF field protocol, such as NFC or RFID, as a second communication protocol. This second communication protocol may thus facilitate pairing the display device 20 and the sensor electronics unit 6 to communicate using a first communication protocol, such as BLUETOOTH.

[0179] In some cases, the process 800 (which may be referred to as out-of-band pairing) may be used to conserve power over traditional first communication protocol pairing. For example, but not limited to, advertising and connecting the display device 20 to the sensor electronics unit 6 using wireless transmissions such as BLUETOOTH may drain the battery power of the sensor electronics unit 6. In some cases, the sensor electronics unit 6 may advertise using wireless transmissions such as BLUETOOTH for different lengths of time depending on the display device 20 attempting to connect. As a non-limiting example, advertising and connection times using BLUETOOTH for a specialized receiver may be shorter (e.g., about 7 seconds) compared to advertising and connection times for a mobile device (e.g., 20 seconds). As a result, energy savings may occur when NFC or RFID are used for pairing because of the shorter connection times.

[0180] As an illustrative example, NFC or other wireless communication devices can be used to initiate pairing for wireless communication, instead of advertising and connection times and power consumption associated with wireless communication devices (e.g., BLUETOOTH). When used in a "tap-to-start" fashion, connecting display devices 20 can establish a connection on demand without incurring (or using less) the power consumption associated with standard wireless communication advertising and connection. E. Configuring the Whitelist and / or Bonding List

[0181] In some implementations, actions can be taken through the communication protocol to set and / or manipulate the whitelist and / or bonding list of the sensor electronics unit 6. When NFC is used, such actions can include actions 618 and / or similar actions, some of which can utilize the white / bonding list setting unit 658. The illustrative examples described below with reference to the whitelist and bonding list can be part of the actions 618 and / or separate actions and / or can utilize the white / bonding list setting unit 658. As discussed in this disclosure, white / bonding list setting actions (e.g., actions 618 and / or other actions described in this disclosure that set, add, delete, and / or manipulate the whitelist and / or bonding list) can be performed in combination with other actions, such as one or more of the actions 613. These actions can be performed in a queue, such as the action queue 630.

[0182] 9A-F illustrate an example operation of a whitelist and / or a bonding list using multiple communication protocols. FIG. 9A illustrates an example whitelist 906 and a bonding list 914 that can be used to pair the sensor electronics unit 6 and the display device 20A by using two or more communication protocols. The sensor electronics unit 6 can communicate with the display device 20A as described in the process 800. As described in the process 800, a second communication protocol can be used to enable the sensor electronics unit 6 and the display device 20A to send / receive address, pairing, and / or other information to each other. As a result of the exchange, the sensor electronics unit 6 and the display device 20A can communicate using a first communication protocol, such as, but not limited to, a first communication protocol using wireless transmission such as BLUETOOTH.

[0183] In the case of a wireless transmission (e.g., BLUETOOTH®) connection, the display device 20A may be listed in a whitelist 906 of the sensor electronics unit 6 when paired with the sensor electronics unit 6. The whitelist 906 may have a predetermined number of slots, such as slot 908A, in which the pairing information from the display device 20A may be stored. Information from the whitelist 906 may also be stored in a bonding list 914. For example, but not limited to, the information of the display device 20A stored in slot 908A of the whitelist 906 may also be stored in slot 910A of the bonding list 914.

[0184] 9B illustrates multiple exemplary display devices 20A,C connecting using a second communication protocol, as reflected in the whitelist 906 and bonding list 914 illustrated in FIG. 9A. In the case of a wireless transmission (e.g., BLUETOOTH®) connection, the display device 20C may also be listed in the whitelist 906 of the sensor electronics unit 6. The pairing information (e.g., address, make / model, name, GAP, IRK, etc.) of the display device 20C may be stored in a slot, such as slot 908B, that is different from the pairing information of the display device 20A stored in slot 908A. The pairing information of the display device 20C may also be stored in a slot in the bonding list 914, such as slot 910B.

[0185] FIG. 9C illustrates an exemplary whitelist and bonding list that are updated when the sensor electronics unit 6 and the display device 20A are unpaired using a second communication protocol. Advantageously, using a second communication protocol such as an RF field (e.g., NFC or RFID) allows a user to dynamically and on-demand remove the display device 20A (or any other display device such as the display device 20C) from the whitelist (e.g., whitelist 906). This may result in power savings in some situations. As an illustrative example, the sensor electronics unit 6 may advertise a display device on the whitelist 906. However, if that display device is no longer in range and / or is no longer desired for use, the sensor electronics unit 6 will potentially undesirably waste energy in attempting to make that connection. Also, advantageously, removing a first display device from the whitelist 906 may prevent that first display device from inadvertently connecting when such a connection is undesirable. For example, and not by way of limitation, a user may wish to connect a second display device to the sensor electronics unit 6 and by connecting a first display device to the sensor electronics unit 6, the second display device may be prevented from connecting by entering its position in the whitelist 906.

[0186] As an illustrative example, without limitation, the sensor electronics unit 6 can use a second communication protocol, as also described with reference to Figures 9A-B, to remove the display device 20A from the whitelist 906 and consequently from active communication with the sensor electronics unit 6. In some implementations, the display device 20A can send a command to the sensor electronics unit 6 instructing the sensor electronics unit 6 to remove the display device 20A from slot 908A. In some instances, this can leave an empty spot in the whitelist 906.

[0187] The bonding list 914 can operate independently from the white list 906. Just because the display device 20A is removed from the white list 906 does not mean that it is removed from the bonding list 914. The bonding list 914 can store the pairing information of the display device 20A for later use. In some cases, if the bonding list 914 has utilized all of its free slots, the pairing information in one or more slots of the bonding list 914 can be deleted. The bonding list 914 can be stored in the sensor electronics unit 6 and one or more applications of the display devices 20A, C (e.g., a mobile application downloaded from an entity that creates and / or owns and / or licenses the app, and / or from an app store such as APPLE, INC. or GOOGLE INC., or otherwise). In some cases, this deletion can be accomplished by the display device 20A sending at least a command / request through the second communication protocol to delete the pairing information of the display device 20A from the bonding list 914. This removal may be desirable if the user does not want the sensor electronics unit 6 to further communicate with the display device 20A and does not want to risk connecting the display device 20A. Removing the display device 20A from the bonding list 914 advantageously reduces the risk of undesired communication / connection by deleting the pairing information from memory.

[0188] FIG. 9D illustrates an example in which a display device 20D can be added to a whitelist 906 of a first communication protocol and a display device 20C can be removed from the same whitelist 906 using a second communication protocol. First, pairing information for display device 20A can be stored in slot 908A, pairing information for display device 20C can be stored in slot 908B, and then display device 20C and the sensor electronics unit 6 can be paired for communication using the second communication protocol. Display device 20D can be paired with the sensor electronics unit 6 to communicate over the first communication protocol by using a second communication protocol, such as a communication protocol using an RF field (e.g., NFC or RFID) as described in process 800. In some cases, pairing display device 20D to the sensor electronics unit 6 can allow display device 20D to be replaced with another display device that is paired to the sensor electronics unit 6. This may be desirable when all slots in the whitelist 906 are filled and / or when a user desires to pair the display device 20D to the sensor electronics unit 6. In some implementations, the display device 20D may also send a command to the sensor electronics unit 6 via the second communication protocol instructing the sensor electronics unit 6 to replace the pairing information of the display device 20C on the whitelist 906 with the pairing information of the display device 20D. In some implementations, the command may include instructions to cause the sensor electronics unit 6 to add the display device 20D to the whitelist 906. In some cases, based at least in part on the type of the display device 20D (e.g., a receiver, a mobile device, etc.), the sensor electronics unit 6 may replace the display device on the whitelist 906 for devices of the same type.In some implementations, the command may include instructions that cause the sensor electronics unit 6 to transmit information indicative of at least the contents of the whitelist 906, including the slot 908B, to the display device 20D. The sensor electronics unit 6 may then transmit information indicative of the contents of such whitelist 906 to the display device 20D. The display device 20D may then select, through user input or automatically (e.g., based on device type or learned patterns, such as a user disconnecting a device at a certain time of day), to remove the pairing information of the display device 20C from the slot 908B and add the pairing information of the display device 20D. As illustrated in FIG. 9D, the pairing information of the display device 20D may be replaced with the pairing information of the display device 20C in the slot 908B.

[0189] 9E illustrates an example of reordering the whitelist 906 illustrated in FIG. 9B using a second communication protocol. In some implementations, the sensor electronics unit 6 can communicate to paired display devices (e.g., any paired display devices 20A-N) serially. In other words, it can communicate to one display device first, then to the next display device sequentially.

[0190] As an illustrative example, FIG. 9G illustrates sequential communication windows for communicating between the sensor electronics unit 6 and the display devices in the slots 908A-N. Communication between the sensor electronics unit 6 and the display devices in the slots 908A-N may occur within communication windows 972A-N. Each of the communication windows 972A-N may be a period during which the sensor electronics unit 6 may connect to and communicate with a respective display device in the slots 908A-N. Each of the communication windows 972A-N may be set independently (e.g., by a user or automatically by the sensor electronics unit 6) or together. For example, the period of each of the communication windows 972A-N may be set independently in some cases. In other cases, multiple communication windows 972A-N may be set to the same period. In other cases, all of the communication windows 972A-N may be set to the same period. In any of these cases, the period may be 5 seconds, 10 seconds, 15 seconds, 20 seconds, 25 seconds, 30 seconds, or more. The period may also be set at least in part based on the time it takes to connect to the display device, the importance of the connection, and / or other factors. For example, it may vary depending on the time it takes to connect to the display device, the type of device, and the communication protocol used. By way of example, a specialized receiver may be specifically configured to connect to the sensor electronics unit 6 and may transmit / receive pairing information faster than a general-purpose device, such as a mobile device. Thus, the specialized receiver may have one of the communication windows 972A-N set with a shorter period. In some cases, the period of one of the communication windows 972A-N corresponding to a preferred device may be longer, since a longer period may allow for more communication attempts in the event of any interrupted and / or lost communication.

[0191] Because the sensor electronics unit 6 may communicate with the display devices in slots 908A-N sequentially (the sensor electronics unit 6 may first communicate with the display device in slot 908A, then with the display device in slot 908B, etc.), there may be a time difference between when the display devices in slots 908A-N receive messages. There may also be a difference in reliability (and / or robustness) between the communication between the sensor electronics unit 6 and each of the display devices in slots 908A-N. In some cases, the display device in slot 908A that receives information first may be designated as the primary display device, the display device in slot 908B may be the secondary display device, the display device in slot 908C may be the tertiary display device, and so on. In some cases, it may be desirable to switch the order of which display devices are in which of slots 908A-N. As an illustrative example, and not by way of limitation, it may be desirable to switch the secondary display device to the primary display device, and consequently switch slot 908B to slot 908A.

[0192] In some cases, one or more of the display devices 20A-N can communicate with the sensor electronics unit 6 to change the designation of one or more of the display devices 20A-N. Returning to FIG. 9E, by way of a non-limiting example, but not limited to, the pairing information of the display device 20C can be stored first in the slot 908B, and the pairing information of the display device 20A can be stored first in the slot 908A. For example, the display device 20C can communicate with the sensor electronics unit 6 using a second communication protocol, such as a communication protocol using an RF field, such as NFC or RFID. Through the second communication protocol, the display device 20C can send a command to the sensor electronics unit 6 to move it to the slot 908A and move the pairing information of the slot 908A (e.g., the pairing information of the display device 20A) to another slot (e.g., the slot 908B). In some implementations, the command can include a request to designate the display device 20C to a particular status (e.g., primary, secondary, tertiary, etc.). Thus, the sensor electronics unit 6 can then switch display device 20C from slot 908B to slot 908A, and switch display device 20A from slot 908A to slot 908B, based at least in part on the sensor electronics unit 6's determination that slot 908A corresponds to the particular status requested. In making that switch, the sensor electronics unit 6 can also switch display device 20A to slot 908B, based at least in part on a determination that because display device 20C is switching to slot 908A, display device 20A should be switched to slot 908B to provide appropriate priority. In some implementations, the command can include instructions that cause the sensor electronics unit 6 to transmit information indicative of at least the contents of a whitelist 906 that includes slot 908B to the display device 20C. The sensor electronics unit 6 can then transmit information indicative of the contents of such whitelist 906 to the display device 20C.Display device 20C can then choose to switch the pairing information for slot 908B and slot 908A through user input or automatically (e.g., based on learned patterns such as device type or the user's use of the display device as the primary display device at certain times of day).

[0193] In some implementations, a command to reorder the whitelist 906 can be paired with another command, request, and / or action of this disclosure. For example, without limitation, a display device can be added to the whitelist 906 and also reorder the whitelist 906. There can be any number of combinations of actions that can be taken in a queue, such as the action queue 630.

[0194] 9F illustrates using a second communication protocol to move display device 20C on the bonding list 914 of a first communication protocol to the whitelist 906 of that first communication protocol. For example, but not limited to, the pairing information of display device 20C may be stored in slot 910B of the bonding list 914. The pairing information of display device 20C may not be listed on the whitelist 906.

[0195] Using a second communication protocol, such as a communication protocol using an RF field, such as NFC or RFID, the display device 20C can send a command to the sensor electronics unit 6 to move the display device from the bonding list 914 to the whitelist 906 (e.g., to slot 908B) of the first communication protocol of the sensor electronics unit 6. The first communication protocol can be BLUETOOTH in some cases. Moving the display device 20C from the bonding list 914 to the whitelist 906 can be used in some cases when the whitelist 906 fails and when the whitelist 906 can be populated using information from the bonding list 914. For example, but not limited to, the whitelist 906 can fail, have corrupted data, or have errors in attempting to identify and pair the display device 20C. The identification and pairing information of the display device 20C can be moved from the bonding list 914 to the whitelist 906 in such a situation to allow a user to connect to the display device 20C.

[0196] Although the depictions of display devices (e.g., display devices 20A, C, D) and sensor electronics units 6 in Figures 9A-F have form factors for illustrative purposes, those skilled in the art will recognize that any such display device and sensor electronics unit 6 represents any sensor electronics unit and / or display device described in this disclosure. F. Data Transfer

[0197] In some implementations, the sensor electronics unit 6 may communicate with the display device 20 using one communication protocol. However, another communication protocol may be used in certain circumstances. For example, in some implementations, a user may wish to connect the display device 20 to the sensor electronics unit 6 to collect historical data or data generated by the sensor electronics unit 6 to analyze past events for which the sensor electronics unit 6 collected data. Such connection to collect historical data may be made one time or periodically as desired. For example, without limitation, the display device 20 may be in a mode in which the user may not be able to view glucose values ​​in real time, but may receive glucose alerts and alarms during a sensor session. The data may later be downloaded by a medical professional using another display device (e.g., one of the display devices 20A-N) or by any user who wishes to view the data. As another non-limiting example, a user may wish to switch to a display device (e.g., one of the display devices 20A-N) from another display device (e.g., another one of the display devices 20A-N) that was previously used. The newly connected display device may allow the user to download historical data from the sensor electronics unit 6. In this case, the display device downloading the historical data may provide timing information to the sensor electronics unit 6 during at least a portion of the time period during which the sensor electronics unit 6 should transmit the lost data. As another non-limiting example, the sensor electronics unit 6 may reduce and / or completely stop transmissions to connect to the display device 20 after a determined amount of time / cycles. This allows the sensor electronics unit 6 to conserve power, processor usage, and / or other resources. As another non-limiting example, a user and / or medical provider may wish to periodically download data and, as a result, connect the display device 20 to the sensor electronics unit 6 to collect historical data.

[0198] In these examples, the display device 20 (or any other one of the display devices 20A-N) can typically send / receive data and / or otherwise transmit communications to the sensor electronics unit 6 using one communication protocol, such as a communication protocol using wireless transmissions like BLUETOOTH. The display device 20 can then receive past data through another communication protocol, such as an RF field like NFC and RFID. The display device 20 can first send a command to the sensor electronics unit 6 through either the first communication protocol or the second communication protocol. The sensor electronics unit 6 can then transmit data through the second communication protocol. For example, but not limited to, the data can be transmitted through a communication protocol using an RF field like NFC and RFID. The second communication protocol can also resume communication through the first communication protocol in a manner substantially similar to the process described in this disclosure, such as described with reference to FIG. 8, FIG. 9A-F.

[0199] In some implementations, NFC or RFID can be used to transmit commands and / or requests from the display device 20 to the sensor electronics unit 6. Such commands or requests can include start transmission for a communication protocol (e.g., wireless transmission such as BLUETOOTH or any other communication protocol described in this disclosure), pair with the display device (e.g., wireless transmission such as BLUETOOTH or any other communication protocol described in this disclosure), stop transmission for a communication protocol (e.g., wireless transmission such as BLUETOOTH or any other communication protocol described in this disclosure), sleep, low power, wake up, calibrate the sensor electronics unit 6 and / or continuous analyte sensor 8, start or stop a sensor session, send historical data, and / or any other command desired, including commands associated with one or more of the actions 613. Thus, in some instances, a communication protocol utilizing an RF field such as NFC or RFID can be used to initiate a transfer of data over wireless transmission such as BLUETOOTH. This data may include data indicative of estimated blood glucose levels, historical data indicative of blood glucose levels, pairing information, status, model number, error logs, communication conditions (e.g., previous communications or history, such as the number of previous lost communications, previous advertising interval / duration budgets, and / or time to connection history associated with a particular display device), and so forth.

[0200] In some implementations, when the first communication protocol is not functioning and / or some form of failure occurs, a second communication protocol can be used to transfer information about an error condition or any type of data that would be useful in assisting technical support. For example, but not limited to, in some implementations, wireless transmission, such as BLUETOOTH, can be the first communication protocol. In some cases, the wireless transmission capabilities of the sensor electronics unit 6, the display device 20, or both, can be impaired or blocked, such that the sensor electronics unit 6, the display device 20, or neither has full communication capabilities through wireless transmission. It may be desirable to obtain diagnostic and / or error condition information (e.g., an error log) to diagnose a problem. A second communication protocol using an RF field, such as NFC or RFID, can be used to obtain diagnostic and / or error condition information. Using a second communication protocol can be advantageous in that it allows for the diagnostic and / or error condition information to be retrieved on demand, instead of waiting for the communication timing of the first communication protocol, even if the first communication protocol is capable of transmitting that information. As an illustrative example, display device 20 can send commands to sensor electronics unit 6 through a communication protocol that uses an RF field, such as NFC or RFID. Sensor electronics unit 6 can then use that same communication protocol to send diagnostic and / or error condition information. In some cases, display device 20 can then forward this information to a server (e.g., network, cloud, etc.) via a communication protocol, such as a cellular connection, Wi-Fi, or any communication protocol described in this disclosure.

[0201] In some cases, it may be desirable to receive data from the sensor electronics unit 6 when the sensor electronics unit 6 has low or dead battery. In some implementations, a communication protocol may be used to retrieve that data, such as, but not limited to, data indicative of an estimated blood glucose level, historical data indicative of blood glucose level, pairing information, status, model number, error logs, and the like. For example, a communication protocol using an RF field, such as, but not limited to, NFC or RFID, may use the energy of the display device 20 to power the transmission of the sensor electronics unit 6 through that same communication protocol. As an illustrative example, if NFC is the communication protocol, the display device 20 may create an RF field using induction. The sensor electronics unit 6 may include an NFC tag that stores data. Thus, the display device 20 may have an NFC reader that can read the NFC tag even when the sensor electronics unit 6 has little or no power. In some implementations, the use of a communication protocol by the display device 20 may actually power the unit of the sensor electronics unit 6 to transmit data. As an illustrative example, but not limited to, the magnetic inductance of an RF field created by the display device 20 using an NFC communication protocol can enable inductive charging or wireless transfer of energy from the display device 20 to the sensor electronics unit 6. This energy can be used by the sensor electronics unit 6 to power data transfer using an RF field such as NFC or another communication protocol. In some implementations, this energy can be used by the sensor electronics unit 6 to power circuitry (e.g., application specific integrated circuits ("ASICs") and / or other hardware) of the sensor electronics unit 6 to recover data and / or the energy can be used to power a wireless transmission protocol such as BLUETOOTH. The wireless transmission protocol can then transmit data from the sensor electronics unit 6 to the display device 20.

[0202] Advantageously, there may be situations where a user would like to retrieve such data from their sensor electronics unit 6 after the sensor electronics unit 6 battery is low or dead. For example, but not limited to, a user may send their sensor electronics unit 6 to a health provider or a third party at the end of a sensor session. At that stage, the sensor electronics unit 6 battery may be low or dead. The health provider or third party may then download the data from the sensor electronics unit 6 using a communication protocol that uses an RF field, such as NFC or RFID. In some cases, the health provider may be instructed by the sensor electronics unit 6, which may instruct the health provider's display device to transfer the data via NFC.

[0203] As another non-limiting example, a user may wish to clone their sensor electronics unit 6 (e.g., using action 609 and / or clone unit 649). Advantageously, if a user transfers data after the sensor electronics unit 6 has run out of power or is low on power (e.g., has little or no battery power remaining), the user can transfer as much information as possible before switching to a new sensor electronics unit. Thus, while using NFC and a clone action such as action 609, the user can then power the data / information transfer from the sensor electronics unit 6 to the display device 20 even if the sensor electronics unit 6 has little or no battery power remaining.

[0204] As another non-limiting example, a user may neglect monitoring their blood glucose levels and maintaining their device. If a user wants to get their information from the sensor electronics unit 6 when the sensor electronics unit has little or no battery power remaining, the user can use NFC to power the transfer.

[0205] In some implementations, multiple communication protocols may be used, with some types of communications being sent over one type of communication protocol and other types of communications being sent over another type of communication protocol.

[0206] As an illustrative example, and without limitation, NFC can be used to send all commands and / or requests from the display device 20 to the sensor electronics unit 6. Such commands or requests can include starting transmission for a communication protocol (e.g., wireless transmission such as BLUETOOTH or any other communication protocol described in this disclosure), pairing with the display device 20 (e.g., wireless transmission such as BLUETOOTH or any other communication protocol described in this disclosure), stopping transmission for a communication protocol (e.g., wireless transmission such as BLUETOOTH or any other communication protocol described in this disclosure), calibrating the sensor electronics unit 6 with the continuous analyte sensor 8, sending historical data, and / or any other command desired, including commands associated with one or more of the actions 613. NFC can also be used to configure settings of the sensor electronics unit 6, such as its transmission parameters, advertising (e.g., broadcasting, beaconing, stealth mode, etc.), timing, etc. Advantageously, NFC can provide a user with a secure and intuitive manner to send such commands and / or requests. The range limiting of NFC can reduce the risk of an unauthorized display device sending commands and / or requests to the sensor electronics unit 6. Additionally, the physical action of bringing the display device 20 close to the sensor electronics unit 6 can be intuitive to a user.

[0207] In some implementations, all data may be transmitted from the sensor electronics unit 6 to the display device 20 using wireless transmission such as BLUETOOTH, as wireless transmission may have a longer range and higher transmission speed. Also, conveniently, wireless transmission communication may occur autonomously by the display device 20 and may be utilized without the user having to actively place the display device 20 next to the sensor electronics unit 6. In some cases, data may be transmitted in response to commands and / or requests transmitted through a communication protocol that uses an RF field, such as NFC or RFID. In some implementations, certain types of data may be transmitted through an RF field rather than wireless transmission. By way of illustrative example and without limitation, some data may be considered more secure and may affect the functionality of the sensor electronics unit 6 / continuous analyte sensor 8. It may be desirable to use a different protocol than wireless transmission to transmit such information. For example and without limitation, a user may transmit calibration data from the display device 20 to the sensor electronics unit 6. This calibration data may include data indicative of an analyte measurement, such as blood glucose level, taken from another source, such as a finger prick. This data can be used to calibrate blood glucose level readings from the sensor electronics unit 6 / continuous analyte sensor 8. Such data can be transmitted over NFC to provide additional security and / or to make the transfer more user friendly. Calibration data can also be particularly advantageous to transmit over NFC as it can enable a user to adjust or update the calibration of the sensor electronics unit 6 on-demand when convenient and / or desirable.

[0208] In some implementations, the transmission can be split into multiple communication protocols to further encrypt the message. For example, but not limited to, the display device 20 can send a portion of the command through a first communication protocol (e.g., wireless transmission such as BLUETOOTH) and a portion of the command through a second communication protocol (e.g., RF field such as NFC or RFID). As an illustrative example, in a case where an RF field communication protocol and wireless transmission are used, the sensor electronics unit 6 can receive a portion of the command through wireless transmission and perform a commanded action if it receives a portion of the command through the RF field communication protocol. Similarly, data transmitted from the sensor electronics unit 6 can be split into an RF field communication protocol and a wireless transmission such that a portion of the data is sent through the RF field communication protocol and a portion of the data is sent through wireless transmission. In this way, the display device 20 receives all the data using both the RF field communication protocol and the wireless transmission. As a non-limiting example, encrypted information can be sent through an RF field communication protocol such as NFC or RFID, and then the encrypted data can be used to decrypt the data sent via a wireless transmission protocol such as BLUETOOTH.

[0209] In some implementations, what type of transmission is sent over which communication protocol may depend at least in part on the remaining battery charge and / or available power of the sensor electronics unit 6. In some implementations, one usage of the communication protocol may be used when the battery charge of the sensor electronics unit 6 is above a first predetermined threshold, while a second usage of the communication protocol may be used when the battery charge falls below a second predetermined threshold (which may have a value equal or substantially equal to the first predetermined threshold, or may have a different value). As an illustrative example, without limitation, the first predetermined threshold is defined as a range in which the battery of the sensor electronics unit 6 has a significant amount of charge remaining (e.g., greater than 30, 40, 50, 60, or more percentages of battery charge remaining, or any predetermined percentage, as desired). When the battery level is above its first predetermined threshold, communication between the sensor electronics unit 6 and the display device 20 may utilize wireless transmissions such as BLUETOOTH and / or a combination of wireless transmissions such as BLUETOOTH and an RF field communication protocol such as NFC or RFID. However, when the battery level of the sensor electronics unit 6 is relatively low and falls below a second predetermined threshold (e.g., less than 30% of the battery level), communication between the sensor electronics unit 6 and the display device 20 may use a less energy utilizing and / or energy saving communication protocol (e.g., an RF field communication protocol such as NFC or RFID). Advantageously, this may enable a user to provide battery power such that only a certain number of actions per day can be performed through the communication protocol. For example, if the number of actions taken via the first communication protocol per day (e.g., one, five, ten, or any number of actions budgeted by the user, determined at least in part by energy consumption) is exceeded, communication between the sensor electronics unit 6 and the display device 20 may be switched to the second communication protocol.As a non-limiting example, the first communication protocol can be wireless transmission, such as BLUETOOTH, and the second communication protocol can utilize an RF field, such as NFC or RFID. The number of actions can be five per day. Thus, if the user exceeds five communications in a day via wireless transmission, the user then utilizes the RF field communication protocol for subsequent communications.

[0210] In some implementations, a transmission may be sent through one communication protocol, but the transmission may be viewed using data / information through a second communication protocol. For example, but not limited to, data may be transmitted from the sensor electronics unit 6 to the display device 20 using a wireless transmission protocol such as BLUETOOTH. However, the data may not be viewable by the display device 20 until the sensor electronics unit 6 transmits a decryption key to the display device 20 through an RF field communication protocol such as NFC or RFID.

[0211] By way of illustrative example, and not by way of limitation, the sensor electronics unit 6 can broadcast, beacon, and / or otherwise transmit data using one protocol. For example, the data can be transmitted to any device within its range via wireless transmission, such as BLUETOOTH. The information can be viewed by a user using a second communication protocol, such as a communication protocol using an RF field, such as NFC or RFID. By way of illustrative example, and not by way of limitation, the sensor electronics unit 6 can broadcast data about the user via BLUETOOTH to BLUETOOTH-enabled devices within BLUETOOTH range of the sensor electronics unit 6. Such BLUETOOTH-enabled devices can receive the data (e.g., using a computer application) and store the data. However, the data may be encrypted and / or made invisible on the BLUETOOTH® enabled device until the BLUETOOTH® enabled device communicates with the sensor electronics unit 6 using NFC or RFID to receive the encryption key, commands, and / or data that allow the BLUETOOTH® enabled device to view the received data.

[0212] As another illustrative example, in some implementations, the sensor electronics unit 6 can be in a broadcast mode using a first communication protocol using wireless transmission such as BLUETOOTH, where the radio of the sensor electronics unit 6 can only transmit data but cannot receive it from the display device 20 (e.g., one-way data transmission). In this case, a second communication protocol using an RF field such as NFC or RFID can be used to transmit commands, such as a command to open two-way communication over the first communication protocol. Once two-way communication is opened over the first communication protocol, the display device 20 can transmit commands and / or information to the sensor electronics unit 6. For example, but not limited to, the display device 20 can transmit calibration data and calibration commands to the sensor electronics unit 6 over the first communication protocol. Once the two-way communication is completed, the sensor electronics unit 6 returns to the broadcast mode. Advantageously, allowing the second communication protocol to open two-way communication while the sensor electronics unit 6 is in the broadcast mode allows the sensor electronics unit 6 to maintain the efficiency of broadcasting over the broadcast mode and still receive information and / or commands from the display device 20 in a timely manner.

[0213] As another illustrative example, the sensor electronics unit 6 can use a wireless transmission broadcast, such as a BLUETOOTH broadcast (e.g., beacon transmission and / or one-way communication) sent to the display device 20. The beacon can be sent exclusively to a particular device (e.g., in an exclusive mode) and / or can be sent only at a particular time. This exclusivity can be achieved by encrypting the beacon and / or by broadcasting the beacon to a particular identified display device (e.g., identified through make, model, IP address, etc. in the beacon). For example, without limitation, a user may use a different display device at night than during the day. During the day, the user may start work at an office and have mobile devices that he or she uses there. These mobile devices may be different from the display devices that the user uses when at home. In some implementations, the beacon can be broadcast to a first set of display devices during the day when the user is at work and a second set of display devices at night when the user is away from work. In some cases, these wireless transmission broadcasts may be encrypted to secure any data, commands, information, status, etc., transmitted between the sensor electronics device and the display device and vice versa. In some implementations, another communication protocol such as NFC or RFID may be used to transmit a decryption key to decrypt the encrypted data, commands, information, status, etc. If NFC is used, the display device from which the user wishes to send / receive data, commands, information, status, etc. may be brought into proximity with the sensor electronics unit 6. The sensor electronics unit 6 may already beaconing to the display device or may not have yet begun beaconing.The display device and the sensor electronics unit 6 can exchange decryption keys (e.g., static and / or dynamic keys) that can then be used to decrypt transmissions (e.g., data, commands, information, status, communications, etc.) sent between the display device and the sensor electronics unit 6.

[0214] In some cases, the sensor electronics unit 6 can beacon, which can transmit data and / or invite devices into its communication range to connect. In some implementations, the sensor electronics unit 6 can beacon using a first communication protocol, and the display device 20 can then use a second communication protocol to connect the display device 20 to the sensor electronics unit 6 for communication using the first communication protocol. As an illustrative example, but not limited to, the sensor electronics unit 6 can beacon using a wireless transmission such as BLUETOOTH. The display device 20 can receive the beaconed message and prompt to pair with the display device 20. The display device 20 can then use an RF field communication protocol such as NFC or RFID to pair the sensor electronics unit 6 and the display device 20 for communication over BLUETOOTH®. Advantageously, such a pairing mechanism can simplify the pairing procedure, allowing a user to avoid the multiple steps involved in BLUETOOTH® pairing. Utilizing the limited range of NFC for pairing can also provide additional security, preventing unauthorized connections.

[0215] In some cases, poor connectivity through a first communication protocol, such as BLUETOOTH, can result in excessive connection attempt data and packet drops. Intelligently switching to another second communication protocol that does not have the same connectivity challenges can be used to resynchronize the timing of the first communication protocol and / or to transmit data packets.

[0216] As an illustrative example, a first communication protocol for communication between the sensor electronics unit 6 and the display device 20 can be a wireless transmission, such as BLUETOOTH. When desired by a user (e.g., when a user of the sensor electronics unit 6 and / or the display device 20 notes a connectivity issue), the connection (e.g., pairing) of the sensor electronics unit 6 and the display device 20 can be re-established by using a second communication protocol, such as an RF field communication protocol (e.g., NFC or RFID).

[0217] Due to its simple initiation and transmission in short range, NFC may be particularly useful when a wireless transmission such as BLUETOOTH is the first communication protocol and NFC is the second communication protocol. As an example, the display device 20 may send a command to the sensor electronics unit 6 to disconnect. RF field communication protocols such as NFC or RFID may also be used by the sensor electronics unit 6 and / or device 20 to exchange public and / or private keys for authentication and connection.

[0218] In some cases, to transmit the missing data, an RF field communication protocol such as NFC or RFID may be used to transmit data from the sensor electronics unit 6 to the device 20 or vice versa. For example, but not limited to, data packets received by either the sensor electronics unit 6 or the display device 20 through an RF field communication protocol may be compared to data packets transmitted by the other of the sensor electronics unit 6 and the display device 20. In some cases, the sensor electronics unit 6 and / or the display device 20 may have a list of data packets that were transmitted, received, and / or transmitted but not received. A processor in either the sensor electronics unit 6 and / or the display device 20 may compare the transmitted list and the received list or process the transmitted but not received list to determine which data packets were transmitted but not received. Thus, such transmitted but unreceived data packets may be transferred (e.g., from the sensor electronics unit 6 to the display device 20 and / or from the display device 20 to the sensor electronics unit 6) via an RF field communication protocol or any other communication protocol described in this disclosure (e.g., wireless transmission such as BLUETOOTH (registered trademark)). Exemplary Analyte Monitoring Systems

[0219] The following exemplary analyte monitoring system is provided.

[0220] Analyte monitoring system 1: An analyte monitoring system comprising: a sensor configured to take measurements indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, the sensor electronics unit configured to receive measurements indicative of the analyte level from the sensor, calculate an estimated analyte value, and operate in a normal power mode and a low power mode, and to transmit data indicative of the analyte level using a first communications protocol when in the normal power mode and to receive commands using a second communications protocol when in the low power mode; and a display device configured to transmit commands to the sensor electronics unit using the second communications protocol and receive data indicative of the analyte level from the sensor electronics unit using the first communications protocol, wherein the sensor electronics unit is configured to switch from the low power mode to the normal power mode in response to the command and to wirelessly connect to the display device for communication using the first communications protocol.

[0221] Analyte monitoring system 2: One embodiment of the analyte monitoring system 1, in which the low power mode is a shelf mode.

[0222] Analyte monitoring system 3: An embodiment of analyte monitoring system 1 or 2, wherein the command is a wake-up command.

[0223] Analyte monitoring system 4: An analyte monitoring system comprising: a sensor configured to take measurements indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, the sensor electronics unit configured to receive measurements indicative of the analyte level from the sensor, calculate an estimated analyte value, and operate in a normal power mode and a low power mode, and to transmit data indicative of the analyte level using a first communications protocol when in the normal power mode and to receive commands using a second communications protocol when in the normal power mode; and a display device configured to receive data indicative of the analyte level from the sensor electronics unit using the first communications protocol and to transmit commands to the sensor electronics unit using the second communications protocol, wherein the system is configured to cause the sensor electronics unit to switch from the normal power mode to the low power mode in response to the commands and to wirelessly disconnect the display device from the sensor electronics unit for communication over the first communications protocol.

[0224] Analyte monitoring system 5: One embodiment of the analyte monitoring system 4, wherein the low power mode is a shelf mode.

[0225] Analyte monitoring system 6: An embodiment of the analyte monitoring system 4 or 5, wherein the command is a sleep command.

[0226] Analyte monitoring system 7: An analyte monitoring system comprising: a sensor configured to take measurements indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, the sensor electronics unit configured to receive measurements indicative of the analyte level, process the received measurements, and transmit data indicative of the analyte level at a predefined time using a first communications protocol; and a display device configured to receive data indicative of the analyte level transmitted by the sensor electronics unit using the first communications protocol and to retrieve data indicative of the analyte level from the sensor electronics unit using a second communications protocol at least before the predefined time.

[0227] Analyte monitoring system 8: An embodiment of the analyte monitoring system 7 in which the processing of the received measurements by the sensor electronics unit includes calculating an estimated analyte level based at least in part on the measurements.

[0228] Analyte monitoring system 9: An analyte monitoring system comprising: a sensor configured to take measurements indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, the sensor electronics unit configured to receive measurements indicative of the analyte level, process the received measurements, and transmit data indicative of the analyte level at a predefined time using a first communications protocol; and a display device configured to receive data indicative of the analyte level transmitted by the sensor electronics unit using the first communications protocol, transmit a command message via the second communications protocol causing the sensor to stop taking measurements, and further transmit a request message via the second communications protocol requesting the sensor electronics unit to stop transmitting data indicative of the analyte level using the first communications protocol.

[0229] Analyte monitoring system 10: One embodiment of the analyte monitoring system 9 in which the processing of the received measurements by the sensor electronics unit includes calculating an estimated analyte value based at least in part on the measurements.

[0230] Analyte monitoring system 11: An embodiment of analyte monitoring system 9 or 10 in which a command message provides an instruction to the sensor electronics unit to cause the sensor to stop taking measurements.

[0231] Analyte monitoring system 12: An embodiment of analyte monitoring system 9, 10, or 11, wherein the display device is further configured to initiate taking measurements by the sensor using the second communication protocol and initiate transmission of data indicative of the analyte level using the first communication protocol.

[0232] Analyte monitoring system 13: An analyte monitoring system comprising: a sensor configured to take measurements indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, the sensor electronics unit configured to receive measurements indicative of the analyte level from the sensor, calculate an estimated analyte value, transmit data indicative of the analyte level using a first communications protocol, and receive commands using a second communications protocol; and a display device configured to receive data indicative of the analyte level using the first communications protocol and transmit data request commands to the sensor electronics unit using the second communications protocol, wherein the sensor electronics unit transmits data indicative of the analyte level using the first communications protocol in response to the data request commands.

[0233] Analyte monitoring system 14: An embodiment of the analyte monitoring system 13, wherein the sensor electronics unit is further configured to measure remaining battery power of the sensor electronics unit.

[0234] Analyte monitoring system 15: An embodiment of the analyte monitoring system 14, wherein the display device is further configured to transmit a data request command to the sensor electronics unit using a second communications protocol when the battery level falls below a predetermined threshold.

[0235] Analyte monitoring system 16: An embodiment of the analyte monitoring system 13 in which the sensor electronics unit is configured to selectively receive one or more commands via a second communication protocol and selectively transmit data via a first communication protocol.

[0236] Analyte monitoring system 17: An embodiment of the analyte monitoring system 13, wherein the sensor electronics unit is further configured to transmit data indicative of the analyte level at predetermined time intervals.

[0237] Analyte monitoring system 18: An embodiment of the analyte monitoring system 17, wherein transmitting data indicative of an analyte level using a first communications protocol in response to a data request command does not prevent the sensor electronics unit from transmitting data indicative of the analyte level at predetermined time intervals.

[0238] Analyte monitoring system 19: An embodiment of analyte monitoring system 13, 14, or 15, wherein when the battery level falls below a predetermined threshold, the display device transmits power to the sensor electronics unit using a radio frequency field, thereby providing power to the sensor electronics unit to transmit data indicative of the analyte level over a second communication protocol.

[0239] Analyte monitoring system 20: An embodiment of the analyte monitoring system 14, wherein the sensor electronics unit is further configured to store data indicative of the analyte level in a passive tag when the battery level falls below a predetermined threshold, and the display device is further configured to read the passive tag using a second communications protocol.

[0240] Analyte monitoring system 21: An embodiment of the analyte monitoring system 13, in which the sensor electronics unit further transmits a decryption key using a second communication protocol in response to a data request command, and the decryption key is used to decrypt data indicative of the analyte level transmitted using the first communication protocol in response to the data request command.

[0241] Analyte monitoring system 22: An analyte monitoring system comprising: a sensor configured to take measurements indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, the sensor electronics unit configured to receive measurements indicative of the analyte level from the sensor, calculate an estimated analyte value, and transmit estimated data indicative of the analyte level using a first communications protocol and to receive commands using a second communications protocol; and a display device configured to receive data indicative of the analyte level using the first communications protocol and to transmit data request commands to the sensor electronics unit using the second communications protocol, wherein in response to the data request command, the sensor electronics unit transmits a portion of the data indicative of the analyte level using the first communications protocol and transmits another portion of the data indicative of the analyte level using the second communications protocol.

[0242] Analyte monitoring system 23: An embodiment of the analyte monitoring system 22, wherein the sensor electronics unit is further configured to measure remaining battery power of the sensor electronics unit.

[0243] Analyte monitoring system 24: An embodiment of analyte monitoring system 22 or 23, wherein the sensor electronics unit is further configured to cease transmitting data indicative of the analyte level when the measured remaining battery charge falls below a predetermined threshold.

[0244] Analyte monitoring system 25: An embodiment of the analyte monitoring system 23, wherein the sensor electronics unit is further configured to utilize a low power mode when a measured remaining battery charge falls below a predetermined low power mode threshold.

[0245] Analyte monitoring system 26: An embodiment of the analyte monitoring system 23, 24, or 25, wherein the sensor electronics unit is further configured to utilize the normal power mode when the measured remaining battery power exceeds a predetermined normal power mode threshold.

[0246] Analyte monitoring system 27: An embodiment of the analyte monitoring system 22, in which the second communication protocol utilizes at least one of near field communication and radio frequency identification.

[0247] Analyte monitoring system 28: An embodiment of the analyte monitoring system 22, in which the sensor electronics unit is further configured to calculate an estimated analyte level based at least in part on the measurement.

[0248] Analyte monitoring system 29: An embodiment of the analyte monitoring system 22, wherein the display device is further configured to calculate an estimated analyte value based at least in part on the measurement.

[0249] Analyte monitoring system 30: An embodiment of the analyte monitoring system 22, in which the display device is further configured to read calibration or manufacturing information from a passive tag integrated into the sensor electronics unit after the device authentication procedure is completed.

[0250] Analyte monitoring system 31: One embodiment of the analyte monitoring system 30 in which at least a portion of the information read from the passive tag is encrypted.

[0251] In some implementations, the monitoring system, or particular components and / or subcomponents of the monitoring system, may be executed using a computing system having components including a central processing unit ("CPU"), input / output ("I / O") components, storage, and memory. The executable code modules of the monitoring system may be stored in the memory of the computer system and / or in other types of non-transitory computer-readable storage media. In some implementations, the monitoring system may be configured differently than described above.

[0252] Each of the routines, processes, methods, and algorithms described in the previous sections can be embodied in and fully or partially automated by code modules executed by one or more computers, computer processors, or machines configured to execute computer instructions. The code modules can be stored in any type of non-transitory computer-readable medium or tangible computer storage device, such as a hard drive, solid-state memory, optical disk, and / or the like. The systems and modules can also be transmitted (e.g., as part of a carrier wave or other analog or digital propagated signal) as a generated data signal on various computer-readable transmission media, including wireless-based media and wire / cable-based media, and can take various forms (e.g., as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The processes and algorithms can be partially or fully implemented in application-specific circuits. The results of the disclosed processes and process steps can be stored permanently or otherwise non-transitory in any type.

[0253] As used herein, the term module or unit may describe a given functional unit that may perform according to one or more implementations of the present application. As used herein, a module or unit may be implemented utilizing any form of hardware, software, or 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 form a module or unit. Modules, units, circuits, processors, etc. may be fixed to a printed circuit board (PCB) or the like, and may take various forms. In an implementation, various modules described herein may be implemented as discrete modules, or the functions and features described may be shared, in part or in whole, among one or more modules. In other words, various features and functions described herein may be implemented in any given application and may be implemented in one or more separate or shared modules in various combinations and permutations, as would be apparent to one of ordinary skill in the art after reading this description. Even though various features or functional elements may be described or claimed separately as separate modules, those skilled in the art will understand that these features and functionality may be shared among one or more common software and hardware elements, and that such description does not require or imply the use of separate hardware or software components to implement such features or functionality.

[0254] The various features and processes described above can be used independently of each other or can be combined in various ways. All possible combinations and subcombinations are intended to be within the scope of the present disclosure. In addition, certain method or process blocks can be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states associated therewith can be performed in other sequences where appropriate. For example, the tasks or events described can be performed in orders other than those specifically disclosed, or multiple ones can be combined into a single block or state. The example blocks or events can be performed serially, in parallel, or in some other manner. Tasks or events can be added to or removed from the example implementations disclosed. The example systems and components described herein can be configured differently than described. For example, elements can be added to, removed from, or rearranged compared to the example implementations disclosed.

[0255] Conditional language used herein, such as, inter alia, "can," "could," "might," "may," and the like, is not generally intended to suggest that features, elements, and / or steps are in any way required for one or more implementations, or that one or more implementations necessarily include logic for determining whether those features, elements, and / or steps are included in or performed in any particular implementation, with or without author input or direction. Terms such as "comprising," "including," "having," and the like, are synonymous and used inclusively in an open-ended manner and do not exclude additional elements, features, acts, operations, etc. Additionally, the term "or" is used in its inclusive sense (and not in its exclusive sense), e.g., when used to connect a list of elements, the term "or" means one, some, or all of the elements in the list. Conjunctive language, such as the phrase "at least one of X, Y, and Z," is understood according to the context as generally used to convey that an item, term, etc., can be either X, Y, or Z, unless specifically provided otherwise. Thus, such conjunctive language is not generally intended to suggest that a particular implementation requires that there is at least one of X, at least one of Y, and at least one of Z. "About" or "approximate" and similar terms are used synonymously and to indicate that the value modified by the term has an understood range associated with the term, which can be within ±20%, ±15%, ±10%, ±5%, or ±1% of the range. The term "substantially" is used to indicate that a result (e.g., a measurement) is close to a target value, where "close" can mean, for example, that the result is within 80% of the value, within 90% of the value, within 95% of the value, or within 99% of the value.Additionally, as used herein, "defined" can include "predefined" and / or otherwise predetermined values, conditions, thresholds, measurements, and the like.

[0256] Although certain exemplary implementations have been described, these implementations are presented as examples only and are not intended to limit the scope of the invention disclosed herein. Thus, nothing in any of the above description is intended to imply that any particular feature, characteristic, step, module, or block is necessary or essential. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms, and various omissions, substitutions, and changes may be made in the form of the methods and systems described herein without departing from the spirit of the invention disclosed herein. [Explanation of symbols]

[0257] 1 Sensor Electronics Unit 2 Host 4 Analyte Monitoring Systems 6 Sensor Electronics Unit 8. Continuous Analyte Sensors 12 Uplink Signal 20a Display device 20b Display device 20c Display device 20d display device 20e Display device

Claims

1. 1. An analyte monitoring system comprising: a sensor configured to take a measurement indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, receiving a measurement indicative of the analyte level from the sensor and calculating an estimated analyte value; Operates in normal power mode and low power mode, transmitting data indicative of an analyte level using a first communication protocol while in the normal power mode; and a sensor electronics unit configured to receive commands using a second communications protocol in the low power mode; and A display device, comprising: transmitting the command to the sensor electronics unit using the second communications protocol; a display device configured to receive data indicative of an analyte level from the sensor electronics unit using the first communication protocol; the sensor electronics unit is configured to switch from the low power mode to the normal power mode in response to the command and to wirelessly connect to the display device for communication using the first communication protocol.

2. The analyte monitoring system of claim 1 , wherein the low power mode is a shelf mode.

3. The analyte monitoring system of claim 1 or 2, wherein the command is a wake-up command.

4. 1. An analyte monitoring system comprising: a sensor configured to take a measurement indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, receiving a measurement indicative of the analyte level from the sensor and calculating an estimated analyte value; Operates in normal power mode and low power mode, transmitting data indicative of an analyte level using a first communication protocol while in the normal power mode; and a sensor electronics unit configured to receive commands using a second communications protocol in the normal power mode; and A display device, comprising: receiving data indicative of an analyte level from the sensor electronics unit using the first communications protocol; and a display device configured to transmit commands to the sensor electronics unit using the second communications protocol; an analyte monitoring system, wherein the system is configured to, in response to the command, cause the sensor electronics unit to switch from the normal power mode to the low power mode and to wirelessly disconnect the display device from the sensor electronics unit for communication over the first communication protocol.

5. The analyte monitoring system of claim 4 , wherein the low power mode is a shelf mode.

6. The analyte monitoring system of claim 4 or 5, wherein the command is a sleep command.

7. 1. An analyte monitoring system comprising: a sensor configured to take a measurement indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, receiving a measurement indicative of the analyte level; Processing the received measurements; and a sensor electronics unit configured to transmit data indicative of the analyte level using a first communication protocol at a predefined time; A display device, comprising: receiving data indicative of an analyte level transmitted by the sensor electronics unit using the first communications protocol; and a display device configured to retrieve data indicative of the analyte level from the sensor electronics unit using a second communications protocol at least prior to the predefined time.

8. The analyte monitoring system of claim 7 , wherein the processing of the received measurements by the sensor electronics unit includes calculating an estimated analyte level based at least in part on the measurements.

9. 1. An analyte monitoring system comprising: a sensor configured to take a measurement indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, receiving a measurement indicative of the analyte level; Processing the received measurements; and a sensor electronics unit configured to transmit data indicative of the analyte level using a first communication protocol at a predefined time; A display device, comprising: receiving data indicative of an analyte level transmitted by the sensor electronics unit using the first communications protocol; transmitting a command message via a second communication protocol to cause the sensor to stop taking measurements; and a display device configured to further transmit a request message via the second communication protocol requesting the sensor electronics unit to stop transmitting data indicative of the analyte level using the first communication protocol.

10. 10. The analyte monitoring system of claim 9, wherein the processing of the received measurements by the sensor electronics unit includes calculating an estimated analyte value based at least in part on the measurements.

11. The analyte monitoring system of claim 9 or 10, wherein the command message provides an instruction to the sensor electronics unit to cause the sensor to stop taking measurements.

12. 12. The analyte monitoring system of claim 9, wherein the display device is further configured to initiate the taking of the measurements by the sensor using the second communication protocol and to initiate the transmission of data indicative of an analyte level using the first communication protocol.

13. 1. An analyte monitoring system comprising: a sensor configured to take a measurement indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, receiving a measurement indicative of the analyte level from the sensor and calculating an estimated analyte value; transmitting data indicative of the analyte level using a first communication protocol; and a sensor electronics unit configured to receive commands using a second communications protocol; and A display device, comprising: receiving data indicative of an analyte level using the first communication protocol; and a display device configured to transmit a data request command to the sensor electronics unit using the second communication protocol, wherein the sensor electronics unit transmits data indicative of an analyte level using the first communication protocol in response to the data request command.

14. The analyte monitoring system of claim 13 , wherein the sensor electronics unit is further configured to measure a remaining battery charge of the sensor electronics unit.

15. 15. The analyte monitoring system of claim 14, wherein the display device is further configured to transmit the data request command to the sensor electronics unit using the second communications protocol when the battery level falls below a predetermined threshold.

16. 14. The analyte monitoring system of claim 13, wherein the sensor electronics unit is configured to selectively receive one or more commands over the second communication protocol and selectively transmit data over the first communication protocol.

17. The analyte monitoring system of claim 13 , wherein the sensor electronics unit is further configured to transmit data indicative of the analyte level at predetermined time intervals.

18. 20. The analyte monitoring system of claim 17, wherein the transmitting of data indicative of an analyte level using the first communications protocol in response to the data request command does not prevent the sensor electronics unit from transmitting data indicative of an analyte level at the predetermined time interval.

19. 16. The analyte monitoring system of claim 13, wherein when the battery level falls below the predetermined threshold, the display device transmits power to the sensor electronics unit using a radio frequency field, thereby providing power to the sensor electronics unit to transmit data indicative of the analyte level over the second communication protocol.

20. 15. The analyte monitoring system of claim 14, wherein the sensor electronics unit is further configured to store data indicative of the analyte level in a passive tag when the battery level falls below a predetermined threshold, and the display device is further configured to read the passive tag using the second communication protocol.

21. 14. The analyte monitoring system of claim 13, wherein the sensor electronics unit further transmits a decryption key using the second communication protocol in response to the data request command, the decryption key being used to decrypt data indicative of the analyte level transmitted using the first communication protocol in response to the data request command.

22. 1. An analyte monitoring system comprising: a sensor configured to take a measurement indicative of an analyte level; a sensor electronics unit communicatively coupled to the sensor, receiving a measurement indicative of the analyte level from the sensor and calculating an estimated analyte value; transmitting estimated data indicative of the analyte level using a first communication protocol; and a sensor electronics unit configured to receive commands using a second communications protocol; and A display device, comprising: receiving data indicative of an analyte level using the first communication protocol; and a display device configured to transmit a data request command to the sensor electronics unit using the second communications protocol, wherein the sensor electronics unit transmits a portion of the data indicative of the analyte level using the first communications protocol and transmits another portion of the data indicative of the analyte level using the second communications protocol in response to the data request command.

23. 23. The analyte monitoring system of claim 22, wherein the sensor electronics unit is further configured to measure a remaining battery charge of the sensor electronics unit.

24. 24. The analyte monitoring system of claim 22 or 23, wherein the sensor electronics unit is further configured to cease transmitting data indicative of analyte levels when the measured remaining battery power falls below a predetermined threshold.

25. 24. The analyte monitoring system of claim 23, wherein the sensor electronics unit is further configured to utilize the low power mode when the measured remaining battery power falls below a predetermined low power mode threshold.

26. The analyte monitoring system of any of claims 23-25, wherein the sensor electronics unit is further configured to utilize the normal power mode when the measured remaining battery power exceeds a predetermined normal power mode threshold.

27. 23. The analyte monitoring system of claim 22, wherein the second communication protocol utilizes at least one of near field communication and radio frequency identification.

28. 23. The analyte monitoring system of claim 22, wherein the sensor electronics unit is further configured to calculate an estimated analyte level based at least in part on the measurement.

29. 23. The analyte monitoring system of claim 22, wherein the display device is further configured to calculate an estimated analyte value based at least in part on the measurement.

30. 23. The analyte monitoring system of claim 22, wherein the display device is further configured to read calibration or manufacturing information from a passive tag integrated into the sensor electronics unit after a device authentication procedure is completed.

31. 31. The analyte monitoring system of claim 30, wherein at least a portion of the information read from the passive tag is encrypted.

Images