System and method for communication of display devices and sensor electronic equipment units

Abstract

The method and apparatus are provided for communication between a display device and a sensor electronics unit within an analyte monitoring system. [Solution] The analyte monitoring system may include a sensor configured to perform measurements indicating the analyte level. The sensor may be communicatively coupled to a sensor electronic unit. The sensor electronic unit may be configured to transmit data indicating the analyte level to a display device using one or more communication protocols. Furthermore, the sensor electronic unit may operate in multiple modes and be configured to switch between modes in response to commands received from the display device. Related systems, methods, and products are also described.

Description

[Technical Field]

[0001] Incorporation by reference to related applications Any priority claims or amendments thereto identified in the application datasheet 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 forms part herein.

[0002] This application generally relates to a system and method for communication between a sensor electronics unit and a display device in an analyte monitoring system. [Background technology]

[0003] Analyte monitors can be placed on tissue and configured to detect analytes within a sensing area. For example, but are not limited to, analyte monitors may include sensors that measure the concentration of glucose, lactate, cholesterol, hemoglobin, and / or other blood or body fluid components.

[0004] In some cases, individuals with diabetes mellitus (also known as diabetes) may use an analytic monitor. Diabetes mellitus is a disorder in which a person's pancreas is unable to produce enough insulin, such as type 1 diabetes, and / or insulin is unable to be effective for the person, such as type 2 diabetes. In a diabetic state, affected individuals may experience hyperglycemia, which can lead to a range of physiological disorders, including renal failure, skin ulcers, or vitreous hemorrhage of the eye, which may be associated with deterioration of microvessels. Hypoglycemic reactions, such as hypoglycemia, can be induced by inadvertent overdose of insulin, or by extreme exercise or insufficient food intake after normal administration of insulin or glucose-lowering agents.

[0005] In some cases, diabetic patients may be required to wear analyte monitors, such as self-monitoring blood glucose ("SMBG") monitors, which typically involve an uncomfortable finger-prick method. Due to the lack of comfort and / or convenience, diabetic patients typically measure their glucose levels only two to four times a day. Unfortunately, these time intervals are so widely spaced that diabetic patients may not realize they are hyperglycemic or hypoglycemic until it is too late, sometimes leading to dangerous side effects. In fact, diabetic patients may not only fail to obtain timely SMBG readings, but they may also be unable to determine whether their blood glucose levels are elevated or decreased based on conventional methods.

[0006] Consequently, various analyte monitors have been developed to include non-invasive, transdermal (e.g., transcutaneous), and / or implantable electrochemical sensors for continuously detecting and / or quantifying blood glucose levels. These, as well as 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 the user hosting the sensor. [Overview of the project] [Means for solving the problem]

[0007] Any feature of an embodiment expressly described herein is applicable to all other embodiments and implementations identified herein. Furthermore, any feature of a given embodiment can be combined in part or in whole with other embodiments described herein independently, for example, one, two, or three or more embodiments may be combined in whole or in part. Furthermore, any feature of a given embodiment can be optional with respect to other embodiments. Any embodiment of a method can be performed by a system or apparatus of another embodiment, and any embodiment of a system can be configured to perform a method of another embodiment.

[0008] In some implementations, multiple communication protocols can be used for communication between a sensor electronics unit and one or more display devices. Communication between sensor electronics units can be based on wired and / or wireless communication protocols, which will be discussed later in this disclosure with reference to Figures 3-4 and elsewhere throughout this disclosure. For example, but not limited to, a first communication protocol may utilize wireless communication such as BLUETOOTH® or Bluetooth Low Energy (BLE) wireless communication protocol, which uses a wireless communication frequency range of 2.4 to 2.485 GHz. A second communication protocol may utilize a radio frequency ("RF") field such as Near Field Communication ("NFC") or Radio Frequency Identification ("RFID"). NFC may 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, a second communication protocol can be used by a display device to communicate with a sensor electronics unit. In some cases, these communications may include commands / requests, data transmission, and / or other communications.

[0010] In some implementations, a display device can use a second communication protocol to cause a sensor electronics unit to perform one or more actions. In some cases, these actions can be combined into an action queue. Thus, the actions described in the 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 and 6A-B, and elsewhere throughout this disclosure.

[0011] In some implementations, one action can be a wake action, in which the display device uses a second communication protocol to send commands / requests 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 being woken up, the sensor electronics unit can use the first communication protocol to pair with and communicate with the display device used to wake it up. Similarly, the operating mode of the sensor electronics unit can be changed using the second communication protocol, 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 analytic level monitoring system is provided which includes a sample sensor for measuring analytic levels and is communicatively coupled to a sensor electronics unit. The sensor electronics unit is configured to receive analytic measurement data from the sensor and may be further configured to process the data based on the measurement data to calculate an estimated analytic value. The sensor electronics unit is also configured to communicate with a display device using multiple communication protocols and to operate in multiple operating modes. For example, but not limited to, operating modes may 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 may include one or more commands that, upon receipt by the sensor electronics unit, cause the sensor electronics unit to switch from a low power mode, such as a memory mode, to a normal power mode, and / or wirelessly connect to the display device using a different communication protocol than the one used to communicate the commands. Alternatively, the sensor electronics unit can switch from normal power mode to low power mode and / or terminate the connection for communication with the display device using the first communication protocol in response to a command communicated using a second communication protocol. The sensor electronics unit can communicate data indicating analyte levels, such as analyte measurement data or estimated analyte values, to the display device using at least one of a plurality of communication protocols, for example, while operating in normal power mode. In some of these embodiments, the display device is configured to process the analyte measurement data and calculate estimated analyte values.

[0013] In other embodiments, the analyte monitoring system includes a sample sensor for measuring analyte levels and communicately coupled to a sensor electronics unit. The sensor electronics unit is configured to receive analyte measurement data from the sensor and may be further configured to process the data based on the measurement data to calculate an estimated analyte value. The sensor electronics unit is also configured to communicate with a display device using a plurality of communication protocols. The sensor electronics unit may communicate analyte measurement data or an 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 an 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, it may stop performing analyte measurements and further stop transmitting analyte measurement data or an estimated analyte value.

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

[0015] In other embodiments, the analyte monitoring system includes a sample sensor for measuring analyte levels and communicately coupled to a sensor electronics unit. The sensor electronics unit is configured to receive analyte measurement data from the sensor and may be further configured to process the data based on the measurement data to calculate an estimated analyte value. The sensor electronics unit is also configured to communicate with a display device using a plurality of communication protocols. The sensor electronics unit may communicate analyte measurement data or an 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 an estimated analyte value. The display device is also configured to communicate commands to the sensor electronics unit using a second communication protocol. For example, a command may include one or more instructions, which, upon receipt by the sensor electronics unit, cause the sensor electronics unit to transmit analyte measurement data or an 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 ​​can be communicated using a first communication protocol, and another portion of the analyte data or values ​​can be communicated using a different communication protocol.

[0016] In several implementations, one action may be a calibration action, in which the display device uses a second communication protocol to transmit commands / requests and / or data to the sensor electronics unit, thereby calibrating the sensor electronics unit. This calibration data may include data acquired by the user through finger puncture and input into the display device. The calibration data can be used by the sensor electronics unit to calibrate its calibration function, converting raw measurements of the analyte sensor (e.g., current, voltage, resistance, gate logic, etc.) into data representing analyte measurements, such as estimated glucose values ​​("EGV"), estimated blood glucose levels, blood glucose levels, and / or any other analyte measurements or estimates of analyte measurements.

[0017] In some implementations, one action can be a cloning action, and the display device can use a second communication protocol to send commands / requests and / or data to clone the sensor electronics unit. For example, but not limited to, two sensor electronics units can be used in the cloning action. The display device can use the second communication protocol to send commands / requests to the first sensor electronics unit and can 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 via the first or second communication protocol. The display device can then use the second communication protocol to then initiate the transfer of the data obtained from the first sensor electronics unit to the second sensor electronics unit.

[0018] In several implementations, one action may be a data retrieval action, and the display device may use a second communication protocol to send commands / requests and / or data to the sensor electronics unit causing it to send data to the display device using the first and / or second communication protocols. For example, but not limited to, an NFC-enabled or RFID-enabled display device may modify the establishment of normal communication, such as scheduled communication or communication that follows a specific timing, as described later in this disclosure with reference to Figures 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 before a scheduled transmission. This transmission may result from the user / host sensing signs of hypoglycemia, or the user may want to transmit a backlog of sensor data to the display device in bulk transfer.

[0019] In some embodiments, one action is a configured white / bonding list action, and the display device uses a second communication protocol to send commands / requests and / or data to configure, adjust, and / or operate the white list or bonding list of the first communication protocol within the sensor electronics unit. The white list and bonding list 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 the white list or bonding list, removing the display device from the white list or bonding list, and / or reorganizing the white list and / or bonding list. In some embodiments, adding the display device can send commands (s) through the second communication protocol to add the display device to the white list of the sensor electronics unit of the first communication protocol, the commands (s) can also specify the position of that display device and other display devices on the white list, and can also shift other display devices outside the white list.

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

[0021] In some embodiments, multiple communication protocols (e.g., a first and a second communication protocol) can be used to transmit data and / or commands. For example, without limitation, certain types of communication can be transmitted through the first communication protocol, and certain types of communication can be transmitted through the second communication protocol. By way of illustration, without limitation, all commands can be transmitted through the second communication protocol, and all data can be transmitted through the first communication protocol. In some embodiments, communication can be divided between the first communication protocol and the second communication protocol. For example, without limitation, encrypted data / information can be transmitted through one communication protocol, while decryption keys and / or other security information can be transmitted through another communication protocol, so that the display device can read the communication from the sensor electronics unit using both communication protocols. In some embodiments, communication can be divided among multiple communication protocols, so that a complete message includes data / information from multiple communication protocols.

[0022] In some embodiments, the sensor electronics unit can adjust the communication protocol based on the battery level. For example, without limitation, the second communication protocol can be used to recover data from a sensor electronics unit that is out of power and / or has low power. In some cases, the sensor electronics unit can stop data measurement and / or transmission when the battery level drops below a predetermined threshold. Then, one or more communication protocols (e.g., the second communication protocol) can be used to power the sensor electronics module, and further, the data stored in the sensor electronics module can be recovered. In some cases, the sensor electronics unit can load data onto a passive tag when its battery level drops below a predetermined threshold.

[0023] In some cases, the display device can use NFC to initiate power supply and / or communication from the sensor electronics unit to the display device via wireless transmission (e.g., using the BLUETOOTH® or BLE wireless protocol). This may be desirable when the sensor electronics unit's battery is low or dead. This can be used by healthcare workers to process patient data and / or by any user to retrieve data from a sensor electronics unit that is nearing or has lost power, or in the event of a sensor electronics unit failure. [Brief explanation of the drawing]

[0024] The embodiments disclosed herein are described in conjunction with the accompanying drawings, which are provided to illustrate and not limit the embodiments disclosed, and the same symbols represent the same elements. Details of one or more embodiments of the subject matter described herein are shown in the accompanying drawings and the description below. Other features, embodiments, and advantages will become apparent from the description, drawings, and claims. Note that the relevant dimensions in the following drawings may not be drawn to a constant ratio.

[0025] [Figure 1A] This figure illustrates an exemplary continuous analyte monitoring system having a sensor electronics unit, sensors, and multiple display devices that can be connected to the sensor electronics unit. [Figure 1B] This is an exemplary flowchart illustrating the start of a sensor electronics unit, from manufacturing to user use. [Figure 1C] This figure illustrates an exemplary display device and sensor electronics unit communicating via two different communication channels. [Figure 2A] This 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]This figure illustrates an exemplary system in which an exemplary sensor electronics unit is communicatively coupled to two exemplary display devices. [Figure 3] This is a functional block diagram of an exemplary sensor electronics unit. [Figure 4A] This is a functional block diagram of an exemplary display device. [Figure 4B] This is an exemplary advertising / connection sequence between an exemplary sensor electronics unit and an exemplary display device. [Figure 5A] This figure illustrates the exemplary range of exemplary communication protocols for exemplary sensor electronic equipment units, where each communication protocol has a different range. [Figure 5B] This figure illustrates the exemplary range of exemplary communication protocols for exemplary display devices, where each communication protocol has a different range. [Figure 5C] This diagram illustrates an exemplary functional block diagram illustrating an exemplary functional unit of an exemplary display device. [Figure 6A] This diagram illustrates an exemplary interface in which a user can select NFC functionality from an exemplary display device. [Figure 6B] This diagram illustrates an exemplary interface for performing actions in an exemplary action queue via NFC. [Figure 6C] This is an exemplary timing diagram showing how to wake an exemplary sensor electronics unit from low-power mode using an RF field communication protocol. [Figure 6D] This is an exemplary flowchart illustrating the process of waking an exemplary sensor electronics unit using an RF field communication protocol. [Figure 6E] This is an exemplary timing diagram of an exemplary sensor electronics unit entering low-power mode. [Figure 7A] This is an exemplary timing diagram of an exemplary first communication protocol for an exemplary sensor electronic equipment unit. [Figure 7B]Figure 7A is an exemplary timing diagram of an exemplary sensor electronics unit, illustrating the signal processing that may occur during communication of the first communication protocol. [Figure 7C] Figure 7B illustrates an exemplary transmission from an exemplary sensor electronics unit using a second communication protocol to initiate communication using a first communication protocol, as shown in the exemplary timing diagram of Figure 7B. [Figure 7D] This is an exemplary timing diagram showing transmission via a second communication protocol to terminate an exemplary sensor session. [Figure 7E] This is an illustrative timing diagram showing the timing of transmission via the second communication protocol to initiate a sensor session. [Figure 8] This is an illustrative flowchart illustrating how one communication protocol can be used to facilitate pairing for communication using the other communication protocol. [Figure 9A] This figure illustrates exemplary whitelists and exemplary bonding lists that can be used to pair exemplary sensor electronics units and exemplary display devices by using two or more communication protocols. [Figure 9B] This figure illustrates multiple exemplary display devices connected to an exemplary sensor electronics unit using a second communication protocol, as reflected in the exemplary whitelist and exemplary bonding list illustrated in Figure 9A. [Figure 9C] This figure illustrates an exemplary whitelist and exemplary bonding list of a communication protocol, which are updated when an exemplary sensor electronics unit and an exemplary display device are unpaired using a second communication protocol. [Figure 9D] This diagram illustrates an exemplary implementation in which an exemplary display device can be added to an exemplary whitelist of another communication protocol using a communication protocol, and a different exemplary display device can be removed from the same exemplary whitelist. [Figure 9E]This figure illustrates one embodiment of reordering the exemplary whitelist shown in Figure 9B using a second communication protocol. [Figure 9F] This figure illustrates an embodiment in which an exemplary display device on an exemplary bonding list of a first communication protocol is moved to an exemplary whitelist of the first communication protocol using a second communication protocol. [Figure 9G] This figure illustrates an exemplary sequential communication window graph for communication between an exemplary sensor electronics unit and an exemplary whitelisted exemplary display device shown in Figures 9A-F. [Modes for carrying out the invention]

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

[0027] While certain embodiments are described herein, numerous variations and substitutions of these embodiments are included within the scope of this disclosure. While some of the advantages and merits of preferred embodiments are mentioned, the scope of this disclosure is not intended to be limited to any particular advantage, use, and / or purpose. The detailed description and drawings are not limiting but merely illustrative of this disclosure, and the scope of this 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 (which will be discussed in more detail below), can improve conventional monitoring systems and methods by improving comfort and convenience, and by reducing the chances of overlooking a person's deteriorating or medically dangerous condition. Accordingly, the various realizations described herein concern systems and methods for continuously monitoring an analyte and for communication between a sensor electronics unit and a display device.

[0029] In some implementations, the system is provided for the continuous measurement of a host analyte, and the system may include a continuous analyte sensor (and / or any other sensor) configured to measure the concentration of a host analyte substantially continuously, and a sensor electronics unit operationally and / or communicatively coupled to the continuous analyte sensor to receive the analyte concentration measurements and communicate the analyte measurements to a display device. Specifically, the sensor electronics unit may include electronics configured to process process data and / or data streams at least partially associated with the analyte concentration measured by the continuous analyte sensor in order to generate sensor information including raw sensor data, converted 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 each display device so that different display devices can receive modified sensor information for presentation to a host, caregiver, or others.

[0030] Communication between a 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, and so on. The sensor electronics unit may 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 may affect communication, such as the timing and order of communication, but are not limited to these.

[0031] As used herein, the term “analyte” is a broad term whose ordinary and conventional meaning is evident to those skilled in the art (and is not limited to any special or customized meaning), and further refers to, but is not limited to, substances or chemical components in biological fluids that can be analyzed (e.g., blood, interstitial fluid, cerebrospinal fluid, lymph, or urine). Analytes may include naturally occurring substances, artificial substances, metabolites, and / or reaction products. In some embodiments, the analyte for measurement by a sensor head, device, and method is the analyte. However, other analytes were similarly targeted, including acarboxyprothrombin, acylcarnitine, adenine phosphoribosyltransferase, adenosine deaminase, albumin, alpha-fetoprotein, amino acid profile (arginine (Krebs cycle), histidine / urocanic acid, homocysteine, phenylalanine / tyrosine, tryptophan), andrenostenedione, antipyrine, arabinitol enantiomer, arginase, benzoylecgonine (cocaine), biotinidase, biopterin, C-reactive protein, carnitine, carnosinase, CD4, ceruloplasmin, chenodeoxycholic acid, chloroquine, cholesterol, cholinesterase, conjugated 1-β-hydroxycholic acid, cortisol, creatine kinase, and creatine kinase MM isoform. Immune, Cyclosporine A, d-Penicillamine, De-ethylchloroquine, Dehydroepiandrosterone sulfate, DNA (acetylated polymorphism, alcohol dehydrogenase, α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, β-thalassemia, Hepatitis B virus, HCMV, HIV-1, HTLV-1, Leber's hereditary optic neuropathy, MCAD, RNA, PKU, Plasmodium vivax, Sex differentiation, 21-deoxycortisol), Desbutylhalofantrin, Dihydropteridine reductase, Diphtheria / tetanus antitoxin, Erythrocyte arginase, Erythrocyte protoporphyrin, Esterase D, Fatty acids / Acylglycine,Free β-human chorionic gonadotropin, free erythrocyte porphyrin, free thyroxine (FT4), free triiodothyronine (FT3), fumaryl acetase, galactose / gal-1-phosphate, galactose-1-phosphate uridyltransferase, gentamicin, analyte-6-phosphate dehydrogenase, glutathione, glutathione peroxidase, glycocholic acid, glycosylated hemoglobin, halofantrin, hemoglobin variant, hexosaminidase A, human erythrocyte carbonic anhydrase I, 17-α-hydroxyprogesterone, hypoxanthine phosphoribosyltransferase Immunoreactive trypsin, lactate, lead, lipoprotein ((a), B / A-1, β), lysozyme, mefloquine, netylmycin, phenobarbiton, phenytoin, phytanic acid / pristanic acid, progesterone, prolactin, prolidase, purine nucleoside phosphorylase, kinin, inverted triiodothyronine (rT3), selenium, serum pancreatic lipase, shisomycin, somatomedin C, specific antibodies (adenovirus, antinuclear antibody, anti-zeta antibody, arbovirus, Aujeszky's disease virus, dengue fever virus, guinea pig, tapeworm, amoeba histolytica, enterovirus, Giardia lamblia) Helicobacter pylori, Hepatitis B virus, Herpesvirus, HIV-1, IgE (atopic disease), Influenza virus, Donovan's leishmania, Leptospira, Measles / Mumps / Rubella, Mycoplasma leprae, Mycoplasma pneumoniae, Myoglobin, Irocystitis rotundifolia, Parainfluenza virus, Plasmodium falciparum, Poliovirus, Pseudomonas aeruginosa, Respiratory rash virus, Rickettsia (scrub typhus), Schistosomiasis mansoni, Toxoplasma gondii, Treponema pallidum, Trypanosoma cruz / Langer's, Vesicular stomatis virus (virus), Bancroftian filarial parasite, 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 include, but are not limited to, vitamin A, leukocytes, and zinc protoporphyrin. Salts, sugars, proteins, lipids, vitamins, and hormones naturally occurring in blood or interstitial fluid may also constitute analytes in specific realizations. Analytes may be naturally occurring in biological fluids, e.g., metabolites, hormones, antigens, antibodies, etc. Alternatively, analytes may be introduced into the body, e.g., 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 (amphetamine, methamphetamine, Ritalin, Cylert, Preludin, Didrex, PreState, Voranil, Sandrex, Plegine), and inhibitors (barbiturates, metakalon, Valiu Examples of analytes include, but are not limited to, tranquilizers (such as m, Librium, Miltown, Serax, Equanil, and Tranxene), hallucinogens (phencyclidine, lysergic acid, mescaline, peyote, and psilocybin), narcotics (heroin, codeine, morphine, opium, meperidin, Percocet, Percodan, Tussionex, Fentanyl, Darvon, Talwin, and Lomotil), designer drugs (fentanyl, meperidin, amphetamine, methamphetamine, and analogs of phencyclidine, e.g., Ecstasy), anabolic steroids, and nicotine. Metabolites of drugs and pharmaceutical compositions are also intended analytes. For example, analytes of neurochemicals and other chemicals produced in the body, such as ascorbic acid, uric acid, dopamine, norepinephrine, 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 may include electronics configured to communicate and store data from a user's sensor (e.g., an analyte sensor). The sensor electronics unit may be connected to a display device (e.g., a mobile device, a specialized medical receiver) or any of the other display devices described herein. In any case, the display device may be a device that the user can use to monitor sensor measurements.

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

[0034] In this embodiment, a display device on the whitelist can respond to an advertising signal transmitted by a sensor electronics unit. Upon receiving this response, the sensor electronics unit can update the whitelist with an identifier indicating the display device. In some implementations, a display device can be removed from the whitelist after a period of inactivity, for example, after no communication has occurred between the sensor electronics unit and the display device. A separate list (e.g., a bonding list) can be used to maintain a list of bonding or pairing information for display devices that can be paired with the sensor electronics unit. Exemplary, but not limited to, display device identifiers may also be stored in the bonding list in accordance with pairing or bonding / inclusion in the whitelist. Thus, the sensor electronics unit can retrieve pairing information from the bonding list, and therefore avoid re-pairing the display device with the sensor electronics unit when using the bonding list. For example, but not limited to, even if a display device is removed from the whitelist (e.g., due to a period of inactivity, explicit removal, and / or pairing with a new device), its identifier may still be stored in the bonding list. 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 has been previously bonded to the sensor electronics unit. If it has been bonded, a data connection can be established without engaging in authentication.

[0035] In some implementations, wireless communication searches and / or attempts may occur in a predetermined and / or programmable order (e.g., gradually and / or incrementally). For example, but not limited to, failure in an attempt to communicate with a first display device and / or to issue an alarm to that device may trigger an attempt to communicate with a second display device and / or to issue an alarm to that device. It should be noted that a sensor electronics unit may not be confined to a single display device. Rather, a 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 queries, based on alerts or alarms, and / or similar.

[0036] Sensor information (e.g., data, measurements, etc.) may include processed and / or converted sensor information that does not require processing by the display device before being displayed. However, some display devices may include software that includes display commands configured to enable the display of sensor information thereon (e.g., software programming with commands configured to display sensor information and, optionally, to query the sensor electronics unit to obtain sensor information). In some implementations, the display device may be programmed with display commands by the manufacturer and may also include security and / or authentication to prevent theft of the display device. In some implementations, the display device is configured to display sensor information via a downloadable program (e.g., downloadable Java Script® via the Internet, and / or mobile applications downloaded from entities that create and / or own and / or license apps, and / or from app stores such as APPLE, INC. or GOOGLE INC., or from other companies), and so any display device that supports program downloads (e.g., any display device that supports Java® applets or mobile applications, but is not limited to these) can be configured to display displayable sensor information (e.g., mobile devices, smartphones, tablets, personal digital assistants, personal computers, and the like).

[0037] In some implementations, a specific display device can communicate directly with a sensor electronics unit wirelessly, but intermediate network hardware, firmware, and / or software may be included directly within the wireless communication. In some implementations, a repeater (e.g., a BLUETOOTH® or BLE repeater) can be used to retransmit the transmitted sensor information to a location further away 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) can 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 sensor information transmitted from the sensor electronics unit is received by the display devices without any intermediate processing of the sensor information.

[0038] In some implementations, one or more display devices are configured to query the sensor electronics unit for sensor information, and the display devices request sensor information from the sensor electronics unit on demand, for example, by responding to the queries. In some implementations, the sensor electronics unit can be configured to transmit sensor information to one or more display devices periodically, systematically, regularly, irregularly, or non-periodically (e.g., every minute, every two minutes, five minutes, or ten 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 performed by any combination of paired sensor electronics unit and display devices. For example, one or more display devices can be configured to query the sensor electronics unit's database and to receive alarm information triggered by fulfilling one or more alarm conditions. In addition, the sensor electronics unit can be configured to transmit sensor information to one or more display devices (for example, the same or different display devices as described in the previous example), and the display devices may function differently in terms of how they obtain the sensor information.

[0039] In some implementations, as will be 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 specific types of data content, including direct queries to the memory database of the sensor electronics unit and / or requests for configured or configurable packages of data content therefrom; that is, 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 its knowledge that the display device is receiving a particular transmission. In addition, some display devices can acquire calibration information and transmit it wirelessly to the sensor electronics unit through manual input of calibration information, automatic distribution of calibration information, and / or an integrated reference analyzer monitor built into the display device. U.S. Patent Applications Publications 2006 / 0222566, 2007 / 0203966, 2007 / 0108245, and 2005 / 0154271 (all of which are incorporated herein by reference in their entirety) 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 embodiments disclosed herein.

[0040] In general, multiple display devices (e.g., custom analyte monitoring devices, mobile phones, tablets, smartwatches, reference analyte monitors, drug delivery devices, medical devices, and personal computers) can be configured to communicate wirelessly with a sensor electronics unit. One or more display devices can be configured to show at least some of the sensor information communicated wirelessly by the sensor electronics unit. Sensor information may include, but is not limited to, raw data and / or converted sensor data such as 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 offer several advantages compared to currently available systems and methods. These advantages are generally described below. For example, in the art, there is a need for improved systems and methods of communication using communication protocols between sensor electronics units and display devices. In some cases, the use of communication protocols can consume excessive power, processor capacity, and / or other resources of the CGM system. This issue can be exacerbated by repetitive pairing, synchronization, and / or handshake procedures that may be used in some communication protocols such as BLUETOOTH® or BLE. Therefore, there is a need for improved communication that effectively utilizes the power, processor capacity, and / or other resources of the CGM system.

[0042] In some cases, the repetitive pairing, synchronization, and / or handshake procedures of a CGM system can also generate excessive communication traffic. This traffic can burden the network and / or deplete network resources (e.g., communication channels, data lines, power, processing power, etc.) by tying up communication channels and / or data lines, resulting in interference, power consumption, processor time utilization, and other issues. In some cases, excessive communication traffic can lead to network slowdowns, network failures, and / or increased costs of operating the network, such as higher energy costs, or the use of additional hardware (e.g., processors, communication lines, cooling, etc.). Therefore, there is a need for improved communication in CGM systems.

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

[0044] In some cases, the interaction between sensor electronics units and display devices using communication protocols can be unintuitive and / or cumbersome for the user. For example, but not limited to, a user may have to navigate through numerous menus and configure numerous devices to pair and / or unpair sensor electronics units, display devices, and / or other devices that utilize the communication protocol. As another non-limiting example, the initialization protocols for calibrating and / or configuring sensor electronics units and / or display devices may require navigating numerous menus that can be cumbersome for the user. Having too many steps can impair the user experience and / or prevent the user from effectively using the CGM system and / or faithfully following their medical regimen. Therefore, there is a need for improved communication in CGM systems to enable enhanced usability.

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

[0046] In some cases, communication through communication protocols can be disruptive and / or otherwise lead to security problems. For example, but not limited to, a device may steal the authentication of a display device and / or communicate with a sensor electronics unit as a display device. Such security challenges can allow unauthorized persons to receive personal information and / or control a user's CGM system, potentially causing disruption. Therefore, there is a need for ways to improve advanced communication systems and / or security.

[0047] In some cases, certain communication protocols, such as BLUETOOTH® or BLE, use energy from sensor electronics units to transmit messages. As a result, if the sensor electronics unit runs out of power (e.g., its battery dies) or if a failure / malfunction occurs in the sensor electronics unit that prevents data transfer via wireless communication such as BLUETOOTH® or BLE (e.g., an error in the wireless protocol), it may become difficult to obtain data from the sensor electronics unit. Retrieving such data may be desirable when a user has not previously accessed data from the sensor electronics unit (e.g., data was not transmitted to the user's display device) and / or when they desire an additional copy. Healthcare workers may also desire to download this data in order to provide appropriate treatment to patients. Therefore, there is a need for systems and methods for extracting data from sensor electronics units when the sensor electronics unit no longer has the energy to power certain communication protocols or when it fails.

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

[0049] Figure 1A shows an exemplary continuous analyte monitoring system 1, comprising a sensor electronics unit 6, a continuous analyte sensor 8, and a plurality of display devices 20A-E that can be connected to the sensor electronics unit 6. The continuous analyte monitoring system 1 may include an analyte sensor system 4 and display devices 20A-E. The analyte sensor system 4 may be operationally connected to a host 2 and the plurality of display devices 20A-E according to a particular aspect of this disclosure. In some cases, the display devices 20A-E may run software applications, such as mobile applications (e.g., mobile applications downloaded from an entity that creates and / or owns and / or licenses an app, and / or from an app store such as APPLE, INC. or GOOGLE INC., or otherwise), which perform and / or have the functions described throughout this disclosure.

[0050] The display device 20E can be, alternatively, or in addition to being a display device, a drug delivery device capable of working in conjunction with the analyte sensor system 4 to deliver a drug to the host 2. Exemplary, but not limited to, 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 may 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 communicate directly with one or more of the display devices 20A-E via wireless or wired communication signals. As will be discussed in more detail below, the display devices 20A-E can also communicate with each other and / or through each other to the analyte sensor system 4. Wireless communication signals from the analyte sensor system 4 to the display devices 20A-E may include an uplink signal 12. Wireless communication signals from the display devices 20A-E to the analyte sensor system 4 may include a downlink signal 14. Wireless communication signals can also be between two or more of the display devices 20A-E. For example, the crosslink signal 16 can be a signal communication between display device 20A and display device 20C.

[0051] The sensor electronics unit 6 may include sensor electronics configured to process sensor information and / or transmit and / or receive sensor data to one or more display devices 20A-E. Figure 1A illustrates display devices 20A-E, but the continuous analyte monitoring system 1 may have any number of display devices 20A-N, as discussed in this disclosure with reference to Figure 2A. Display device 20 represents any one of display devices 20A-N when used throughout this disclosure. In a particular embodiment, the sensor electronics unit 6 may include electronics associated with measuring and processing data from the continuous analyte sensor 8, including predictive algorithms associated with processing and / or calibrating the data from the continuous analyte sensor. The sensor electronics unit 6 may be integrated with (e.g., detachably mounted) or detachable from the continuous analyte sensor 8 to achieve a physical connection between them. The sensor electronics unit 6 may include hardware, firmware, and / or software that enables analyte level measurement. For example, but not limited to, 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 fixed to a printed circuit board ("PCB") or similar and may take various 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 herein, and in more detail in U.S. Patent Nos. 7,310,544 and 6,931,327, and U.S. Patent Publications 2005 / 0043598, 2007 / 0032706, 2007 / 0016381, 2008 / 0033254, 2005 / 0203360, 2005 / 0154271, 2005 / 0192557, 2006 / 0222566, 2007 / 0203966, and 2007 / 0108245, all of which are incorporated herein by reference in their entirety for all purposes.

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

[0053] In some embodiments, the display device 20A may be a special medical receiver specifically designed to display a particular type of displayable sensor information associated with analyte values ​​(e.g., numerical values ​​and directions such as increasing or decreasing trends) received from the sensor electronic equipment unit 6. In some embodiments, the display device 20C may be a handheld device such as a mobile phone, palmtop computer, and the like based on the Android® or iOS operating system, and the display device 20C may have a relatively large display and may be configured to display a graphical representation of continuous sensor data (e.g., current and / or historical data). Other display devices include other handheld devices such as tablets (e.g., display device 20D), smartwatches (e.g., display 20B), drug delivery devices (e.g., display device 20E), blood glucose meters, and / or desktop or laptop computers.

[0054] As implicitly mentioned above, different display devices 20A to N can provide different user interfaces, so the content of the data package (e.g., the amount, format, and / or type of data to be displayed, alarms, and the like) can be customized for each specific display device and / or type of display device (e.g., programmed differently by the manufacturer and / or by the user). Therefore, in some implementations, one or more of the display devices 20A to N can communicate wirelessly, directly or indirectly, with the sensor electronics unit 6 to enable multiple different types and / or levels of display and / or functions associated with the sensor information, which will be described in more detail elsewhere in this specification.

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

[0056] The continuous analyte sensor 8 can provide a data stream indicating the concentration of the analyte measured in host 2 using any known method, including invasive, minimally invasive, and non-invasive detection 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 host 2 or a caregiver (e.g., parent, relative, guardian, teacher, doctor, nurse, and / or any other individual concerned with the health of 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 representing the concentration of the analyte.

[0057] In several embodiments, the continuous analyte sensor 8 can measure the glucose concentration of the host 2, one of which is described below as utilizing an implantable continuous glucose sensor. For example, but not limited to, the continuous analyte sensor 8 may be an implantable glucose sensor as described with reference to U.S. Patent No. 6,001,067 and U.S. Patent Application Publication No. 2005 / 0027463-A1. In another embodiment, the continuous analyte sensor 8 may be a transcutaneous glucose sensor as described with reference to U.S. Patent Application Publication No. 2006 / 0020187-A1. In further embodiments, the continuous analyte sensor 8 may be configured to be implanted intravascularly or extravascularly in a host, as described in U.S. Patent Application Publication 2007 / 0027385-A1, concurrently pending U.S. Patent Application Publication 2008 / 0119703-A1 filed on 4 October 2006, concurrently pending U.S. Patent Application Publication 2008 / 0108942-A1 filed on 26 March 2007, and concurrently pending U.S. Patent Application Publication 2007 / 0197890-A1 filed on 14 February 2007. In one alternative embodiment, the continuous analyte sensor 8 may comprise a transcutaneous sensor, as described, for example, in U.S. Patent No. 6,565,509 to Say et al. In another alternative implementation, the continuous analyte sensor 8 may include a subcutaneous sensor, as described, for example, with reference to U.S. Patent No. 6,579,690 to Bonnecaze et al. or U.S. Patent No. 6,484,046 to Say et al. In another alternative implementation, the continuous analyte sensor 8 may include a refillable subcutaneous sensor, as described, for example, with reference to U.S. Patent No. 6,512,939 to Colvin et al. In another alternative implementation, the continuous analyte sensor 8 may include an intravascular sensor, as described, for example, with reference to U.S. Patent No. 6,477,395 to Schulman et al. In another alternative implementation, the continuous analyte sensor 8 may include an intravascular sensor, as described, for example, with reference to U.S. Patent No. 6,424,847 to Mastrototaro et al.Each of the aforementioned patents and patent applications is incorporated herein by reference.

[0058] Figure 1B illustrates an exemplary flowchart showing an exemplary start of a sensor electronics unit 6 from manufacturing to user use. The sensor electronics unit 6 may have a predetermined lifecycle, including exemplary method 50. In block 52, the sensor electronics unit 6 may be manufactured in factory configuration. In some cases, manufacturing may include circuit fabrication, assembly, testing, calibration, and others. In block 54, once the sensor electronics unit 6 is manufactured, it can then be put into shelf mode and / or any low-power mode, which will be further described with reference to Figure 6E and elsewhere throughout this disclosure. This shelf mode and / or any low-power mode may allow the sensor electronics unit 6 to consume less power before use. In block 56, the sensor electronics unit 6 may be transported to a user while in shelf mode. In a non-limiting exemplary example, the sensor electronics unit 6 may be put into shelf mode when it is shipped, placed in a warehouse, and / or before it is activated by a user. Other instances in which the sensor electronics unit 6 may be in shelf mode and / or any low-power mode are described throughout this disclosure.

[0059] In block 58, the sensor electronics unit 6 can be woken from shelf mode and / or any low-power mode when it is desirable to start and use the sensor electronics unit 6. For example, in some cases, but not limited to, the sensor electronics unit 6 can periodically check whether it is connected to the continuous analyte sensor 8. This periodic check may include detecting the current and / or voltage across the electrodes. In some cases, and as exemplary examples, but not limited to, the periodic check may occur at predetermined time intervals, such as every 5 minutes, every 10 minutes, every 15 minutes, or every desired number of minutes, and / or after a predetermined number of counts. The sensor electronics unit 6 can be woken up if there is a change in the current and / or voltage that at least partially indicates a connection to the continuous analyte sensor 8 (e.g., an increase in current and / or voltage, and / or a change over a particular period and / or count). In certain cases, predetermined thresholds can be used for current, voltage, count, time, etc., so that the sensor electronics unit 6 is woken up when the current, voltage, count, time, etc. exceeds (or, where appropriate, falls below) the predetermined threshold. In some implementations, if the sensor electronics unit 6 has an accelerometer, wake-up can be made extremely quick. 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. When the accelerometer detects motion, the sensor electronics unit 6 can be woken up to reduce the interval for checking the current. If the current remains below the wake-up threshold and no motion is detected for a certain period, the sensor electronics unit 6 can be returned to shelf mode. Conveniently, the accelerometer can facilitate an extremely short warm-up time without affecting shelf life. Motion can indicate a user preparing to use the sensor electronics unit 6.

[0060] In block 60, after waking up the sensor electronic equipment unit 6, the continuous analyte sensor 8 of the sensor electronic equipment unit 6 can be initialized. Initialization can be part of a warm-up period during which the sensor electronic equipment unit 6 and / or the continuous analyte sensor 8 run software, perform calibration, perform diagnostics, and do other things.

[0061] In block 62, the sensor electronics unit 6 can be paired with one or more display devices 20A to N. To pair with a display device, the sensor electronics unit 6 can first advertise (e.g., broadcast to the display device about the connection) and then pair with the display device. Advertising by the sensor electronics unit 6 may include, but is not limited to, using communication protocols such as BLUETOOTH® (e.g., BLUETOOTH® Low Energy ("BLE"), Classic BLUETOOTH®, Dual Mode BLUETOOTH®, etc.), IBEACONS®, ZIGBEE®, Wi-Fi, Inductive Radio Data Transmission, Radio Transmission, Radio Frequency Identification ("RFID"), Near Field Communication ("NFC"), and / or any other communication protocols desired and / or referred to in this disclosure. In this specification, any reference to BLUETOOTH® may include BLE, Classic BLUETOOTH®, Dual-Mode BLUETOOTH®, and / or any other BLUETOOTH® protocol. Any display device 20A-N receiving an advertisement can send a connection request to the sensor electronic device 6. The sensor electronic unit 6 and the display devices 20A-N can then pair using the communication protocol being used (e.g., authentication, connection, encryption / decryption, data exchange, etc.) by following the appropriate steps.

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

[0063] In block 66, the sensor electronics unit 6 can be connected to one or more display devices 20A-N during a transmission cycle to transmit / receive communications, and the sensor electronics unit 6 transmits relevant data (e.g., analyte data) to one or more display devices 20A-N. For illustrative purposes only, but not limited to, the sensor electronics unit 6 and display devices 20A-N can be connected during a transmission cycle using the following procedure. The sensor electronics unit 6 can advertise periodically at predetermined time intervals, such as every 5 minutes, every 10 minutes, every 15 minutes, or any desired number of minutes, as desired. The advertisement window can be 7 to 22 seconds in any location. In some cases, the duration of the advertisement window can be extended to allow multiple display devices 20A-N (e.g., receivers and / or mobile devices) to be connected and / or to exchange data and / or commands / requests. The duration of any given interval can depend on the respective types of display devices 20A-N present.

[0064] This transmission cycle may be affected by the battery limitations of the sensor electronics unit 6. Modifying advertising parameters such as the advertising interval or duration can directly affect the total battery level of the sensor electronics unit 6. Through testing, these parameters (e.g., advertising interval and duration) can be adjusted to optimize the time required to connect different display devices 20A~N. In some cases, these parameters can be intelligently adjusted to optimize operation by, for example, monitoring past connection performance to set the advertising interval and duration. By doing so, the overall average advertising time can be reduced when the display devices 20A~N are nearby by connecting them as quickly as possible.

[0065] As described above, in some cases, the continuous analyte monitoring system 1 may include a sensor electronics unit 6 that is operationally and / or communicatively coupled to the continuous analyte sensor 8. The sensor electronics unit 6 can receive (raw and / or processed) data from the continuous analyte sensor 8. Also, as described above, the sensor electronics unit 6 can communicate with one or more display devices 20A-N using communication protocols such as wireless communication, including but not limited to BLUETOOTH®. Through this communication protocol, the sensor electronics unit 6 can transmit data to one or more display devices 20A-N that includes data at least partially based on the received sensor information. 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 electronic equipment unit 6 and one or more display devices 20A-N are connected using wireless communication such as BLUETOOTH®, the sensor electronic equipment 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 the user. In this configuration, the display devices 20A-N can act as a central device. In this setup, the central device can be responsible for scanning for connections of the peripheral devices. For illustrative purposes and to ensure clarity (as sometimes used in the art), a peripheral device (e.g., the sensor electronic equipment unit 6) can advertise that it is available for connection and accept connection requests made by a central device (e.g., display devices 20A-N). In some implementations, a peripheral device cannot provide more than a predetermined number of connections (e.g., one, two, three, four, five, six, or more connections) within a single transmission window. To enable peripheral devices to periodically request data, such as every 5 minutes, 10 minutes, 15 minutes, or any desired interval, the central device can scan, connect, exchange data, and ultimately disconnect in a timely manner. Peripheral devices can enforce timeouts within the connection to prevent the central device from remaining connected for longer than expected. Peripheral devices can use whitelists, as described above, to enable certain central devices or types of devices to connect. This can mean that a central device may be denied a connection due to whitelist features that are enabled for different central devices, even if it is advertising itself as connectable.

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

[0068] The sensor electronics unit 6 and the display device 20 can communicate through communication channels 106 and 108 via multiple communication protocols. As used herein, communication protocols include, but are not limited to, any communication systems configured to transmit information between two or more electronic devices, such as BLUETOOTH®, IBEACONS®, ZIGBEE®, Wi-Fi, inductive radio 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 reference to Figures 5A and 5B. In some cases, communication protocols can utilize electromagnetic radio waves (e.g., electronic induction between antenna loops) and / or radio frequency ("RF") fields, as used by NFC or RFID. Wireless communication and RF fields are further described throughout this disclosure, including reference to Figures 5A and 5B. Where a particular communication protocol is discussed with reference to an embodiment, it should be understood that other communication protocols can be used in the same way.

[0069] As an exemplary example, communication channel 106 may utilize an RF field, such as NFC or RFID. Communication channel 108 may utilize wireless communication such as BLUETOOTH®. In cases 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 minimal interference in crowded environments, ease of use, automatic pairing when in proximity, lower power consumption, and others. Similarly, BLUETOOTH® may have advantages over NFC or RFID, such as high-speed data transmission, wide range, autonomous communication with many different devices, automatic transmission scheduling, and others.

[0070] In several implementations, as described herein, data, commands, status, and / or other communications between the sensor electronic equipment unit 6 and the display device 20 can be transmitted through 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, communication through multiple communication protocols can be used simultaneously and / or sequentially to provide additional security, utility, and / or other desirable advantages. Each of the multiple communication protocols used can be individually utilized and may have different characteristics for different advantages in different applications.

[0071] Figure 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 and 108A-N. In this specification, "N" in the display devices 20A-N and communication channels 106A-N and 108A-N can at least partially indicate the number of display devices that can be connected to the sensor electronics unit 6 at one time. For example, if N is B, then B can at least partially indicate that two display devices (e.g., display devices 20A and B) can be connected to the sensor electronics unit 6 and can communicate with it through communication channels 106A-B and 108A-B. If N is C, then C can at least partially indicate that at least three display devices (e.g., display devices 20A, B, and C) can communicate through communication channels 106A-C and 108A-C. Similarly, N can at least partially indicate any number of display devices. In some cases, the number of display devices that can be connected to the sensor electronic equipment unit 6 can be predetermined when the sensor electronic equipment unit 6 is manufactured and / or configured. For example, two or three display devices can be connected to the sensor electronic equipment unit 6 in many exemplary configurations, but this number is not limited, and more can be connected. In some cases, the number of display devices that can be connected to the sensor electronic equipment unit 6 may be limited by the communication protocol and / or the energy consumption of the communication protocol. For example, but not limited to, some versions of BLUETOOTH® may be limited to a maximum of seven display devices.

[0072] In some cases, one or more of the communication channels 106A to N can use the same communication protocol. In some cases, one or more of the communication channels 106A to N can use different communication protocols. Similarly, in some cases, one or more of the communication channels 108A to N can use the same communication protocol, or one or more of the communication channels 108A to N can use different communication protocols. Also, in some cases, any of the communication channels 106A to N can use the same communication protocol as any of the communication channels 108A to N. Similarly, in some cases, any of the communication channels 106A to N can use a different communication protocol than any of the communication channels 108A to N. In other words, it is recognized that any permutation of different communication protocols can be used as the communication channels 106A to N and 108A to N between the sensor electronic equipment unit 6 and the display devices 20A to N. As a non-limiting example, each of the communication channels 106A to N may use a first communication protocol such as wireless communication like BLUETOOTH®, and each of the communication channels 108A to N may use a second different communication protocol such as an RF field like NFC or RFID. Communication between each of the display devices 20A to 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] Figure 2B illustrates an exemplary system in which an exemplary sensor electronics unit 6 is communicatively coupled to two exemplary display devices 20A and 20C, and display devices 20A and 20C are configured to communicate with each other. Display devices 20A and 20C are particularly exemplary because in many implementations, particularly in the case of a CGM system, a user may have display device 20A as a special display device and another display device 20C which can be a mobile device. However, display devices 20A and 20C are merely exemplary embodiments, and any other display devices, including any of display devices 20A to N, can be used instead. Display devices 20A and 20C can communicate with each other through a communication channel 259. Through the communication channel 259, display devices 20A and 20C can utilize any communication protocol described herein. As exemplary examples, but not limited to them, display devices 20A and 20C can communicate with each other using an RF field such as NFC or RFID. For example, using NFC or RFID, display devices 20A and C can transmit data (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 timestamps, etc.), raw sensor data, system status information, detected faults, alerts, clocking information, device manufacturing ID, and / or any other data and / or information described herein) to each other, commands / requests (e.g., data requests, synchronization requests, pairing requests), and other information. In some cases, information about the sensor electronics unit 6 can be transmitted to facilitate pairing of one of the display devices 20A or C with the sensor electronics unit 6 of the other display device 20A or C. This information can be used to enable the other display device 20A or C to pair with the sensor electronics unit 6 using another communication protocol, such as communication utilizing wireless communication including BLUETOOTH®.For example, but not limited to, pairing information can be transmitted directly between display devices 20A and 20C, or via a server (e.g., network, cloud, etc.). For example, but not limited to, a user can pair display device 20A with sensor electronics unit 6. Subsequently, pairing information from sensor electronics unit 6 (e.g., timing information, encryption key, authentication information, advertising parameters, address, manufacturer / model, name, GAP, IRK, and / or any other relevant information for pairing) can be transmitted directly from display device 20A to display device 20C, or display device 20A can transmit its pairing information to a server, which is then accessible to display device 20C. Thus, display device 20C can download the pairing information uploaded by display device 20A. The pairing information then allows for easier pairing of display device 20C with sensor electronics unit 6. In some cases, the display device 20C can download pairing information by signing a mobile application (for example, 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 a mobile application downloaded from another company). After signing in, this mobile application can communicate with the server and obtain the pairing information, thereby enabling the display device 20C to connect with the sensor electronics unit 6. Conveniently, enabling the display devices 20A and C to communicate in this way allows for the rapid and efficient sharing of pairing information and reduces communication traffic between the display devices 20A and / or 20C and the sensor electronics unit 6. Furthermore, it is possible to enable the display devices 20A and C to update and / or receive information (for example, via the server) when they are not within each other's and / or the sensor electronics unit 6's range.The ability to update and / or receive this information may be advantageous in keeping the display devices 20A,C updated even when they are not connected to the sensor electronics unit 6. Transferring pairing information between such display devices 20A,C may be advantageous in enabling healthcare professionals to set up the system for a user. For example, but not limited to, a healthcare professional may have a display device 20C that can transmit pairing information for the patient's display device 20A while the display device 20A is being set up. This can facilitate the patient's use of the display device 20A, particularly when the patient is an infant, elderly, disabled, or otherwise unable to set up the display device 20A. In another non-limiting example, a user may wish to use a display device 20C and also transmit pairing information using the display device 20A.

[0074] The estimated blood glucose level can be transmitted between display devices 20A and 20C to facilitate the visualization of information about the user of the sensor electronic device unit 6. For example, but not limited to, display device 20A may be the user's display device. Display device 20C may be a display device owned by a healthcare professional. Using an RF field such as NFC or RFID, data transmission from display device 20A to display device 20C may include historical data, enabling the healthcare professional to analyze the patient's response to blood glucose levels and provide treatment. Conveniently, NFC or RFID can enable a secure method 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 their display devices (e.g., by not advertising and / or not needing to re-authenticate) and can also prevent the professional from accidentally connecting to another device in the vicinity. In other applications, data transmitted via NFC or RFID can be used for backfill purposes to enable one of the display devices 20A-B to transmit past 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 be aware that other communication protocols, such as Wi-Fi or any other communication protocols described herein, can also be used to transfer data.

[0075] In some implementations, alerts to display devices 20A, C can be synchronized using communication protocols (e.g., NFC, RFID, Wi-Fi, Bluetooth®, and / or any other communication protocols described herein or known in the art). For example, but not limited to, Wi-Fi can be used so that when a user acknowledges an alert or communication to one of the display devices 20A, C, such acknowledgment can be made visible on the other of the display devices 20A, C. Conveniently, this allows multiple users and devices to coordinate with respect to the treatment of the user of the sensor electronics unit 6, and / or prevents excessive alerts and communications to a single user using a large number of users and / or a large number of devices.

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

[0077] The controller 301 can be operationally and / or communicatively coupled to memory 302, which may include, but is not limited to, 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 memory 302 may also include non-volatile random access memory ("NVRAM"). The controller 301 can perform logical and / or arithmetic operations based on program instructions stored in memory 302. The controller 301 may include one or more processors (e.g., microprocessors) and other peripherals. Instructions in memory 302 can be executed to perform the methods described herein. For example, memory 302 may be a non-temporary computer-readable storage medium having a plurality of instructions stored therein, which can be executed by a processing unit (e.g., controller 301) to operate the sensor electronics unit 6. The operating unit 304 can be coupled to the controller 301 to perform various operations described herein. In some implementations, the operating unit 304 may include one or more of the units within it, or it may not include any of them. 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. 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 can coordinate and / or manage the operating unit 304, and / or set timings (e.g., synchronously or asynchronously), turn it on / off, control the power budget, receive and / or send network commands and / or updates, update firmware, send query signals, receive and / or send status, and / or perform any operations to operate the features of the sensor electronics unit 6.

[0078] The operating unit 304 may include various units that perform the functions of the sensor electronic equipment unit 6. For example, but are not limited to, units of such an operating 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 component therein (e.g., the operating unit 304) to one or more display devices (e.g., display devices 20A-N described herein and / or any other display devices). The communicator 305 can be configured to transmit / receive communications through wired and / or wireless connections, such as any wired and / or wireless connections described herein. For example, but not limited to, the communicator 305 can utilize a communication protocol configured to transmit and / or receive data through a communication channel. For example, but not limited to, such communication protocols include BLUETOOTH®, IBEACON®, ZIGBEE®, Wi-Fi, inductive radio data transmission, radio frequency, wireless 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, but not limited to, the communicator 305 may include an antenna, inductor, signal lines, ground lines, and / or any other electronic equipment used to transmit / receive data. In the case of NFC, RFID, and / or substantially similar technologies, the communicator 305 may include a reader, writer, and / or tag.

[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 device 306, data manager 307, signal processor 308, operating system 310, operating 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 may include a storage device that can store data using different media, including, but not limited to, electrical (e.g., semiconductors, floating-gate transistors, hard disks, flash memory, RAM, ROM, enterprise storage devices, clouds, distributed storage devices, etc.), optical storage (e.g., photographs, microforms, holographics, optical discs, magneto-optical drives, 3D optical data storage devices, holographic data storage devices), chemical (e.g., organic matter, proteins, synapses, receptors, chemical concentration, etc.), thermodynamic (e.g., phase change materials, heat storage devices, etc.), photochemical (e.g., films, etc.), mechanical (e.g., switches), magnetic storage (e.g., magnetic tapes, wires, etc.), and others. The data storage device 306 may also store any data and / or information that is at least partially based on data from any component of the sensor electronics unit 6, including the controller 301, the power supply 303, the memory 302, and / or the units in the operating unit 304.

[0082] The data manager 307 can be configured to analyze and / or manage data in the data storage device 309, memory 302, and / or any components of the sensor electronic equipment unit 6 (e.g., the controller 301, power supply 303, and / or units within the operating unit 304). Operations that the data manager 307 can perform on such data include, but are not limited to, compression, decompression, sorting, classification, instruction, optimization, defragmentation, deletion, secure erasure, security, manipulation, identification, copy, paste, write protection (e.g., temporary write protection or permanent write protection), backup, authentication, and others. 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] The signal processor 308 can be configured to process any data of the sensor electronics unit 6, including, in non-limiting examples, data stored in the data storage device 306 and / or managed by the data manager 307. The signal processor 308 can perform any analysis of the data presented in this disclosure, as well as other analyses and / or processes.

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

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

[0086] Any of the above-described components of the sensor electronic equipment unit 6 can be instantiated in software and / or hardware. For example, the unit can be a part(s) of hardware and / or a unit / module of code running on a computer. The hardware may include a processor, circuit logic, and others.

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

[0088] The controller 401 can be operationally and / or communicatively coupled to memory 402, which may be volatile, non-volatile, ROM, and / or RAM, and may provide instructions and data to the controller 401. A portion of memory 402 may also include NVRAM. The controller 401 can perform logical and arithmetic operations based on program instructions stored in memory 402. The controller 401 may include one or more processors (e.g., microprocessors) and other peripherals. Instructions in memory 402 can be executed to perform the methods described herein. For example, memory 402 may be a non-temporary computer-readable storage medium having a plurality of instructions stored therein, which can be executed by a processing unit (e.g., controller 401) to operate the display device 20. The operating unit 404 can be coupled to the controller 401 to perform various operations described herein. In some implementations, the operating unit 404 may include one or more of the units within it, or none at all. Throughout this disclosure, references are made to various controllers and / or processors. In some implementations, a single controller (e.g., controller 401) can perform the roles of various controllers and / or processors described. In other implementations, different controllers or processors may 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 can coordinate and / or manage the operating unit 404, and / or set timing (e.g., synchronously or asynchronously), turn it on / off, control the power budget, receive and / or send network commands and / or updates, update firmware, send query signals, receive and / or send status, and / or perform any operations to operate the features of the display device 20.

[0089] The operating 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 operating 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 component therein (e.g., the operating unit 404) to one or more sensor electronic units (e.g., sensor electronic unit 6). The communicator 405 can be configured to transmit / receive communications through wired and / or wireless connections, such as any wired and / or wireless connections described herein. For example, but not limited to, the communicator 405 can utilize communication protocols configured to transmit and / or receive data through a communication channel. For example, but not limited to, such communication protocols include BLUETOOTH®, IBEACON®, ZIGBEE®, Wi-Fi, inductive radio data transmission, wireless 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, but not limited to, the communicator 405 may include an antenna, inductor, signal line, ground line, and / or any other electronic equipment used to transmit / receive data. In the case of NFC, RFID, and similar technologies, the communicator 405 may include a reader, writer, and / or tag.

[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 device 406, data manager 407, signal processor 408, operating system 410, operation unit 404, controller 401, memory 402, power supply 403 of the sensor electronics unit 20, and / or any other components and / or subcomponents.

[0092] The data storage device 406 can be configured to store (e.g., record) data temporarily and / or permanently. The data storage device 406 may include a storage device that can store data using different media, including, but not limited to, electrical (e.g., semiconductors, floating-gate transistors, hard disks, flash memory, RAM, ROM, enterprise storage devices, clouds, distributed storage devices, etc.), optical storage (e.g., photographs, microforms, holographics, optical discs, magneto-optical drives, 3D optical data storage devices, holographic data storage devices), chemical (e.g., organic matter, proteins, synapses, receptors, chemical concentration, etc.), thermodynamic (e.g., phase change materials, heat storage devices, etc.), photochemical (e.g., films, etc.), mechanical (e.g., switches), magnetic storage (e.g., magnetic tapes, wires, etc.), and others. The data storage device 406 may also store any data and / or information based at least in part on data from any component of the display device 20, including the controller 401, the power supply 403, the memory 402, and / or units in the operating unit 404.

[0093] The data manager 407 can be configured to analyze and / or manage data in the data storage device 406, memory 402, and / or any components of the display device 20 (e.g., controller 401, power supply 403, and / or units within the operating unit 404). Operations that the data manager 407 can perform on such data include, but are not limited to, compression, decompression, sorting, classification, instruction, optimization, defragmentation, deletion, secure erasure, security, manipulation, identification, copy, paste, write protection (e.g., temporary write protection or permanent write protection), backup, authentication, and others. The data manager 407 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.

[0094] The signal processor 408 can be configured to process any data of the display device 20, including, in non-limiting examples, data stored in the data storage device 406 and / or managed by the data manager 407. The signal processor 408 can perform any analysis 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 the user to communicate with the display device 20. For example, but not limited to, the user interface 409 may include a touch panel, buttons, a keypad / keyboard, ports (e.g., USB, DVI, DisplayPort, E-SATA, FireWire, PS / 2, Serial, VGA, SCSI, audio ports, HDMI®, PCMCIA ports, memory card ports (e.g., SD and miniSD), and / or ports for computer-readable media), a mouse, a rollerball, a console, a vibrator, an audio transducer, and / or any interface (including, but not limited to, any wireless or wired connections as described herein) for the user to input and / or receive data and / or commands, whether connected wirelessly or via wire. The user interface 409 may include, but is not limited to, displays such as LCDs, LED displays, LED LCD displays, IPS, cathode ray tubes, plasma displays, HD panels, 4K displays, Retina displays, OLED displays, touchscreens, surfaces, canvases, and / or any displays, televisions, monitors, panels, and / or devices known in the prior art for their visual representation.

[0096] Power supply 403 may include one or more batteries, but are not limited to lithium, lithium-ion, nickel-cadmium, nickel metallic hydrogen, nickel-hydrogen, carbon-zinc, silver-oxide, zinc-carbon, zinc-air, mercury oxide, alkali, or any other type of battery known in the art. Certain batteries may be recharged wirelessly (e.g., by a resonant circuit and / or resonant tank circuit) and / or by plugging into an external power supply. Power supply 403 may also be any energy source, including solar, wind, water, nuclear, hydrogen, gasoline, natural gas, fossil fuels, mechanical energy, steam, and / or outlets and electronic devices that convert any power source into electricity. Power supply 403 may have a sensor (not shown) to monitor the amount of available power. For example, but are not limited to, when the battery is in use, 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 realizations, 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 lifespan 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 battery life. In some cases, the sensor can track battery usage (e.g., count, power budget, voltage consumption, current consumption, estimated leakage, etc.) and sum up battery usage over time. The sum of usage can be kept and compared to the total battery budget (e.g., count, power budget, voltage budget, current budget, etc.) to estimate the remaining battery life and / or service life.

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

[0098] Any of the above-described components of the display device 20 can be instantiated in software and / or hardware. For example, a unit can be a part(s) of hardware and / or a unit / module of code running on a computer. Hardware can include a processor, circuit logic, and others.

[0099] Figure 4B shows an exemplary advertising / connection sequence between an exemplary sensor electronics unit 6 and a display device 20. The various tasks performed in connection with the advertising / connection illustrated in Figure 4B can be carried out by a processor / controller executing instructions embodied in a non-temporary computer-readable medium. For example, tasks performed in connection with the procedure can be carried out by hardware, software, firmware, or any combination thereof, incorporated into one or more computing devices such as the sensor electronics unit 6 and / or the display device 20. It should be noted that the procedure may include any number of additional or alternative tasks. The tasks shown in Figure 4B may not be performed in the illustrated order, and the procedure may be incorporated into a more comprehensive procedure or process with additional functions not described in detail herein.

[0100] In the embodiments 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. Wireless data communication between the sensor electronics unit 6 and the display device 20 may correspond to the duration between two consecutive wireless communication sessions between the communicator 305 of the sensor electronics unit 6 (e.g., communicator 305) and the communicator 405 of the display device 20 (e.g., communicator 405), "T 間隔 This can occur periodically at intervals defined by the update interval indicated by . Alternatively, the update interval can be the period during which the most recently measured glucose value is obtained and transmitted. The transmission of the advertisement signal, the establishment of a data connection (e.g., a communication channel), authentication, and the request and transmission of data are each within the T update interval. 間隔 Inside "T 起動 This can occur during a wireless communication session, lasting for the duration of the activation time or period (also known as timing) indicated by "T". For example, between two consecutive wireless communication sessions, the communication unit may be affected by "T 停止 The device can enter a pause or sleep mode for a pause period indicated by "[ ]" to conserve battery power and / or reduce peak voltage requirements.

[0101] Figure 4B illustrates one embodiment of two such wireless communication sessions, namely 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 a data connection with the display device 20, the communicator unit 305 of the sensor electronics unit 6 may transmit a series of advertisement signals 412 during the first wireless communication session 420. Each advertisement signal can be considered 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. In some implementations, as will be discussed in more detail below, the advertisement signals 412 can be embodied as advertising beacons. It should be noted that in some implementations, the advertising signal 412 itself may have advertising parameters so that directed or targeted advertising can be directed to a specific display device 20 or type of device.

[0102] In some cases, since 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 can engage in initial system setup. Typically, the user of the display device 20 can identify a new and / or never-before-used sensor electronics unit 6, and the unit can be paired with the display device 20 by entering identification information (e.g., 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., downloadable Java Script® via the Internet, and / or from entities that create and / or own and / or license apps, and / or from app stores such as APPLE, INC. or GOOGLE INC., or mobile applications downloaded from other companies). During the first wireless communication session 410, an authentication procedure, which may be a first data connection process, can be performed as part of the data connection process 414. In some embodiments, information can be obtained from a passive tag or communicator 305 incorporated in the sensor electronics unit 6, for example, by using the NFC reader of the display device 20 to read the passive NFC tag. For example, but not limited to, the passive NFC tag may 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 (for example, via the communicator 405) after the 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 may be located at the base of the sensor electronics module 6.In such an embodiment, the information stored in the passive tag (e.g., information related to a sensor or sensor electronics module) can be initially read by the display device 20. Subsequently, the display device can transmit the acquired information to the sensor electronics module 6 or other display devices via a wireless protocol (e.g., NFC or BLE).

[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. When the communicator 305 of the sensor electronics unit 6 begins transmitting an advertisement signal 412, the display device 20 can take in one, two, or more advertisement signals, receive at least one of the advertisement signals, and respond to at least one of the advertisement signals. In some cases, the extension of advertising may consume energy and / or the battery capacity of the sensor electronics unit 6. In some implementations, once the display device 20 receives an advertisement signal and responds to it, for example, via an acknowledgment, the communicator 305 of the sensor electronics unit 6 may stop transmitting additional advertisement signals. In other implementations, the communicator 305 of the sensor electronic equipment unit 6 may continue to transmit additional advertisement signals even after receiving a response from the display device 20, so that another display device (e.g., one or more of the display devices 20A to N) may receive and / or respond to at least one of the additional advertisement signals. After successfully receiving an advertisement signal from the display device 20, the display device 20 and the sensor electronic equipment unit 6 may engage in the data connection process 414.

[0104] During the data connection process 414, the display device 20 may request a challenge value from the sensor electronics unit 6, and the sensor electronics unit 6 may respond by sending the challenge value to the display device 20. Upon receiving the challenge value, the display device 20 may 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 send the hash value to the communicator 305 of the sensor electronics unit 6. The communicator 305 of the sensor electronics unit 6 receives the hash value from the display device 20, decodes the identification information from the hash value, and can verify that the received identification information matches previously stored identification information associated with the sensor electronics unit 6 and / or the communicator 305 of the sensor electronics unit 6, such as during the manufacturing of the sensor electronics unit 6, in the memory of the sensor electronics unit 6 (e.g., memory 302). Depending on the verification, the communicator 305 of the sensor electronics unit 6 may send a signal to the display device 20 confirming the success of the authentication. Once authenticated, the sensor electronics unit 6 and the display device 20 can exchange information and determine how to exchange data (e.g., specific frequency, time slot allocation, encryption, etc.).

[0105] After completion of the data connection process 414, the sensor electronics unit 6 and the currently connected display device 20 can engage in a first data communication 416, during which the display device 20 can 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 complete, the data connection can be terminated (e.g., by closing an established communication channel), and the communicator 305 and / or the controller 301 of the sensor electronics unit 6 can be put to sleep or stopped (e.g., in a low power mode or shelf mode) by putting the communicator 305 and / or the controller 301 of the sensor electronics unit 6 to sleep. In some embodiments, the communicator 305 of the sensor electronics unit 6 can be completely or substantially completely powered off during sleep mode (e.g., low power or shelf mode). In some embodiments, the communicator 305 of the sensor electronics unit 6 can be put in a low power mode that uses only a very small amount (e.g., 1 - 50%) of normal current / power. As discussed further below with reference to FIGS. 6C - D and elsewhere throughout the present 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 NFC or RFID, which makes an on - demand request to the display device 20.

[0106] Startup period T corresponding to the duration of each wireless communication session 起動 is a very short update interval T corresponding to the period between two consecutive wireless communication sessions 間隔 can be set. For example, T 間隔 can be set to about 200 - 20 seconds, and T 起動 can be set to 20 - 40 seconds. Thus, the communicator 305 of the sensor electronics unit 6 is T / 5 間隔It is possible to fully supply power for only 10 percent of that time (e.g., 30 seconds). This can significantly reduce power consumption and peak voltage demand. In some cases, the communicator 305 can enter a low-power mode when not transmitting, rather than completely cutting off power. Downtime or period T 停止 Subsequently, when the communicator 305 of the sensor electronic equipment unit 6 is powered on again, a second wireless communication session 420 can be initiated, and as shown in Figure 4B, the transmission of a second series of advertisement signals 422 begins, engaging 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, since the pairing or bonding of the sensor electronic equipment unit 6 and the display device 20 was successful during the first wireless communication session 410 as described above, the second data connection process 424 does not need to include an authentication procedure. This process can continue while completing new data connections and communications at predetermined intervals. Each downtime T while the communicator 305 of the sensor electronic equipment unit 6 is in sleep mode... 停止 During all or part of this process, the controller 401 of the sensor electronics unit 6 may take one or more measured values ​​of an analyte using the analyte sensor and sensor measurement circuit. For example, but not limited to, the controller 401 or the sensor electronics unit 6 may take multiple measured values ​​of an analyte and average these values ​​to generate a single averaged analyte value to be transmitted in the next wireless communication session.

[0107] Continuously re-establish a new communication channel, with each update interval T 間隔Within this, enabling the communicator 305 of the sensor electronics unit 6 to be partially or completely power-shut off can provide significant power savings. For example, a cycle of re-establishing a new communication channel and power-shutting off the communicator 305 can allow the sensor electronics unit 6 to operate for one month, three months, six months, one year, or other periods without battery replacement. It should be noted that in some implementations, battery replacement can be a function of actual battery depletion or a predetermined level of battery remaining capacity. Furthermore, the update interval T 間隔In some implementations, instead of transmitting glucose data points globally, establishing specific data connections (e.g., communication channels) only with desired display devices, for example, display device 20 and / or any display devices 20A-N, can prevent unauthorized use and interference of glucose measurements. In some implementations, only a subset of a large number of display devices (e.g., display devices 20A-N) can be configured to receive different data, such as glucose measurements and / or alarm states. For example, a whitelist can be populated with data type identifiers that indicate the types of data transmitted to specific display devices(s) populating the whitelist, in addition to display device identifiers(s). For example, specific display devices(s) may have data type identifiers that indicate which display devices receive glucose measurement data and / or alarm states, such as low blood glucose levels. In other implementations, the sensor electronics unit 6 can be pre-programmed with preference or profile information, which can be accessed to determine what types of data are transmitted to which display devices(s). Therefore, before exchanging sensor information, the sensor electronics unit 6 can access a whitelist (or, in some implementations, a bonding list) and / or preference / profile information to determine what type(s) of data should be sent to the display device. In further implementations, in the initial communication between the sensor electronics unit 6 and the display device 20, the display device 20 can 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 display devices 20A-N communicating with the sensor electronics unit 6 from issuing alarms, thereby preventing confusion and / or disappointment to the user.In addition, by establishing a secure bidirectional communication channel, requests for communication of specific glucose measurements or calibration or configuration information can be transmitted between the sensor electronic equipment unit 6 and the display device 20 as needed / on request.

[0108] Furthermore, in some implementations, the communicator 305 of the sensor electronic equipment unit 6 has an update interval T 間隔 It can be prevented from being activated for each data communication. Instead, the communicator 305 of the sensor electronic equipment unit 6 will update the communication between the sensor electronic equipment unit 6 and the display device 20 at intervals T 間隔 For example, a second, third, or fourth update interval T, so that it occurs less frequently than every one. 間隔 It can be activated each time. Doing so can further reduce power consumption. Activation can also depend on sensor information. For example, the communicator 305 of the sensor electronics unit 6 only needs to be activated when the data meets certain thresholds, such as the rate of change of current, high current values, low current values, absolute difference from previously exchanged values, percentage difference from previously exchanged values, and similar. In some implementations, instead of skipping a specific fixed update interval, the length of each interval can be varied based on sensor information or other criteria. For example, but not limited to, if the sensor information indicates a low glucose value and / or a hypoglycemic response is detected, the update interval value can be shortened from the usual longer update interval value to take and / or transmit the indicated value more frequently.

[0109] In some implementations, the update interval T 間隔 , startup period T 起動 , and the frequency F of activating the transceiver (for example, every second, third, or fourth update interval). 起動One or more of these can be made variable. In a particular implementation, the parameters identified above can be configured by the user (for example, by entering variable values ​​using the user interface of the display device 20) and / or automatically varied by the sensor electronics unit 6 or the display device 20, based on one or more criteria. These criteria include: (i) the battery power of the monitored sensor electronics unit 6 (e.g., using power supply 303); (ii) whether the currently measured, previously measured, and / or predicted glucose concentrations meet or exceed 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 in 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 close to hypoglycemia based on the currently measured, previously measured, and / or predicted glucose concentrations; (vii) the host's activity entered by the user (e.g., exercise or sleep); (viii) the time since the start of the 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 can be connected to or populated in a whitelist or bonding list).

[0110] T as described herein 間隔 , T 起動 F 起動 , and / or other configuration items can form part of a communication protocol profile that can be stored in any profile, and the device implements 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 protocol may have different ranges and / or different authentication protocols. Figure 5A illustrates exemplary ranges of exemplary communication protocols in an exemplary sensor electronic device unit 6 having two communication protocols, each having a different range. As described above, the communication protocol may be any communication protocol known in the art, including those described herein. For example, range 506 may, but is not limited, at least partially represent the range of an RF field such as NFC or RFID. For example, if NFC has range 506, range 506 may be in centimeters, such as 10 centimeters or less. Due to the narrow range, in many cases NFC may have simple and / or automatic connections between devices using the NFC communication protocol. NFC-enabled devices may include NFC card emulation, NFC readers / writers, and / or devices operating by NFC peer-to-peer. NFC can transfer data at speeds ranging from 10⁶ to 424 kilobits per second, or at any other speed as the communication protocol standard is updated at any given time. In some cases, NFC communicates at 13.56 MHz. In some cases, the initiating device of a transmission using NFC can generate an RF field that can power the receiving device. In many cases, NFC is preferred for security and simplicity. However, the NFC communication protocol may have limited 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. Generally, RFID technologies can have a variable range, including those with a range of up to 2000 feet. An RFID system can be an active-reader-passive-tag ("ARPT") having an active reader device that transmits interrogator signals and also receives authentication responses from passive tags.In some cases, an RFID system may be an active reader-active tag ("ARAT") in which the active tag is awakened from the active reader by a query signal. RFID can operate in frequency band ranges such as, but is 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. As used herein, communication protocols using an RF field 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, and 3.1–10 GHz. NFC or RFID are merely illustrative examples.

[0112] Range 508 can at least partially indicate a second communication protocol. For example, the second communication protocol may utilize wireless communication such as BLUETOOTH®. Exemplary example, if the second communication protocol is BLUETOOTH®, range 508 may be approximately 30 feet. In some cases, BLUETOOTH® may have a user-setup device-to-device connection, such as a procedure in which one device detects the other and the devices are paired and / or authenticated. BLUETOOTH® can transmit in the 2.4–2.485 GHz ISM band or at any frequency as the BLUETOOTH® standard is updated at any given time. The BLUETOOTH® version may have relatively fast data transfer rates, such as up to 800 kilobits per second. In many cases, BLUETOOTH® is preferable in terms of its speed and range. However, connectivity, energy consumption, excessive handshakes, packet drops, security, and other challenges may exist. As used herein, wireless communication may include other wireless communication protocols other than BLUETOOTH®, including other wireless communication operating in the 2.4–2.485 GHz frequency range. BLUETOOTH® is used merely as an illustrative example.

[0113] Similarly, Figure 5B illustrates exemplary ranges of exemplary communication protocols for exemplary display device 20, where each communication protocol has a different range. Ranges 556 and 558 may be substantially similar to ranges 506 and 508, respectively. As mentioned above, various communication protocols can be used, such as those using RF fields (e.g., NFC or RFID) or wireless communication (e.g., BLUETOOTH®).

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

[0115] The wake unit 654 can perform waking actions, and the user can use the display device 20 to wake up the sensor electronics unit 6 from low-power mode and / or shelf mode, for example, but not limited to (see, for example, Figures 4B, 6C-D, and described elsewhere throughout this disclosure). In some cases, waking up the sensor electronics unit 6 may include sending a wake-up command to the sensor electronics unit 6.

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

[0117] The sensor electronics unit 6 can be calibrated using the calibration unit 656. For example, but not limited to, a user can measure their blood glucose level through a finger prick. This user can input this data into the display device 20 (e.g., into a field (not shown) through the user interface 409) and transmit information at least partially based on that data to the sensor electronics unit 6 via an RF field communication protocol such as NFC or RFID. Conveniently, the calibration can be time-dependent if the user wishes to quickly adjust and / or add new calibration parameters so that they have the correct readings. Conveniently, calibration using an RF field such as NFC or RFID can be achieved on demand and without requiring the following pairing procedure.

[0118] The data retrieval unit 657 can be used to request data retrieval from the sensor electronic equipment unit 6. In some cases, data retrieval may include a command to send data through a different communication protocol than the one used to request the data. The data request may include what data to send (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 electronic equipment unit log), the data timeframe (e.g., including a timestamp), and other details. As an exemplary example, the second communication protocol used by the display device 20 to request data transmission from the sensor electronic equipment unit 6 may utilize an RF field such as NFC or RFID. The second communication protocol used to transfer the data may be wireless communication such as BLUETOOTH®. Conveniently, transmitting data via wireless communication instead of an RF field can enable faster transfer speeds and longer transfer distances. For example, if it is desirable to retrieve data from the display device 20, the user can use the display device 20 to initiate data transfer from the sensor electronic equipment unit 6 using an RF field such as NFC or RFID to the display device 20, and then move further away while transferring the data via wireless transmission such as BLUETOOTH®. If the data is transferred via NFC, it may take longer and / or the user may have to keep close to the sensor electronic equipment unit 6. Having the flexibility to move around, including moving further away during data transfer, can be advantageous when healthcare professionals are treating the user and other patients.

[0119] In some cases, the command to send data can be a command requesting that data be sent via NFC. Such a command may be desirable when security is important (e.g., the user only wants to send data to nearby devices), when the sensor electronic device has little or no battery power, and / or in any situation desired by the user. In some implementations, the decision of when to use NFC for data transfer can be determined by the display device 20 or the sensor electronic device unit 6, such as using NFC when only a small amount of data is being 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, the sensor electronics unit 6 may have one or more whitelists and / or bonding lists that can be used to manage connected devices. The role of the whitelist may include a list of devices that can be paired with the sensor electronics unit 6 and / or pairing information for such devices (e.g., timing information, encryption keys, authentication information, advertising parameters, addresses, manufacturers / models, names, general access profiles ("GAP"), identification information resolution keys ("IRK"), etc.). In some cases, the whitelist can be stored and updated in the memory of the sensor electronics unit 6. In some implementations, the whitelist may have a predetermined number of slots, such as one, two, three, four, five, or more. Display devices listed in the whitelist can be connected for communication with the sensor electronics unit 6. For example, but not limited to, a display device 20 can be added to the whitelist, and then pairing information from the display device 20 can be retrieved from the bonding list by the sensor electronics unit 6. When display device 20 is connected, the whitelist is updated to allow that specific display device 20, as well as other display devices on that whitelist, to connect.

[0121] The bonding list may contain 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, may be held by an application on the sensor electronics unit 6 or on a display device (e.g., display device 20). The bonding list may contain authentication and / or pairing information (e.g., timing information, encryption keys, authentication information, advertising parameters, addresses, manufacturer / model, name, GAP, IRK, etc.) for a predetermined number of display devices. Display devices 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. Since the user is currently using the display device 20, it may be desirable and convenient for the user to place the display device 20 on the whitelist. For example, but not limited to, if a user is using a receiver and then wants to use a smartphone and leave the receiver elsewhere, the user may want to quickly add the smartphone to the whitelist. In some cases, as will be discussed later with reference to Figure 9A in this disclosure, 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 for the display device 20. This information can be added to any available slot in the whitelist. In some implementations, as will be discussed later with reference to Figure 9C in this disclosure, 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 to notify all of these display devices of the same alert.

[0123] In some cases, as will be discussed later with reference to Figure 9D in this disclosure, the sensor electronics unit 6 may communicate with each display device 20 on its whitelist in a specific order, such as a sequential order (for example, starting from the first slot and progressing 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 the device to connect only at a lower frequency than other slots, such as every 20 instead of every 5 minutes. Also, different slots in the whitelist may have different parameters associated with that slot, which may affect the reliability of the connection, for example, but not limited to. Therefore, along with a command to add the display device 20 to the sensor electronics unit's whitelist and any other associated data as desired (e.g., pairing information), the white / bonding list setting unit 658 may include a request to add the display device 20 to a specific slot in the whitelist. For example, but not limited to, the display device 20 may be requested to be added to the first slot. Conveniently, this allows the display device 20 to have preferred reliability and connectivity, as well as / or faster data reception in some situations.

[0124] In some cases, adding display device 20 to the whitelist may affect other display devices in the whitelist. If the requested slot in the whitelist is available, the information for display device 20 (e.g., pairing information) can simply be added to that available slot. However, other situations may exist. For example, if display device 20 requests to be added to a slot that is already occupied, the white / bonding list setting unit 658 may include instructions to be performed by the display device already occupying it. In some cases, as will be discussed later with reference to Figure 9D in this disclosure, the white / bonding list setting unit 658 may include a request to remove a display device occupying the desired slot for the new display device 20. In this way, an already occupied display device can be removed from the whitelist (and in some cases, from the bonding list as well). In other cases, as will be discussed later with reference to Figure 9E in this disclosure, the white / bonding list setting unit 658 may include a request to shift a display device to a subsequent specified slot and remove the display device in the last slot. For example, in a case where there are three slots numbered 1 to 3, each already occupied, within the whitelist, the white / bonding list unit 658 may include a request to add a pairing indicator device to slot 1. A temporary whitelist can be created in memory to hold the contents of the previous whitelist. In that case, information from the previous slot 1 can be placed into slot 2, and information from the previous slot 2 can be placed into slot 3. Therefore, information from the previous slot 3 cannot be added to the whitelist.

[0125] In some cases, the white / bonding list setting unit 658 can also indicate which display devices should be removed from the whitelist. In the above embodiment, the white / bonding list setting unit 658 may include a request to add the current display device to slot 1, remove the previous display device in slot 2, and shift the devices accordingly. In that scenario, 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 unchanged.

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

[0127] The bonding list can be configured as a separate action or included in the white / bonding list unit 658. Configuring the bonding list can include commands to add or remove items from the bonding list. Typically, the order of the bonding list does not affect the user, but the user can change the order of the bonding list and / or reorder the bonding list in a manner similar to that described above for the whitelist, including commands to add and / or remove specific display devices for specific slots in the bonding list (identified, for example, by display device and / or slot number). The bonding list can contain more slots than the whitelist (e.g., store more devices).

[0128] The operation mode unit 659 may include setting the operation mode. The operation mode unit 659 may include requests to advance the sensor electronic equipment unit 6 to shelf mode, low power mode, normal operation, startup, sleep, transmission, idle, battery management (for example, to improve energy efficiency by using a communication protocol that uses an RF field such as NFC or RFID instead of wireless transmission 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 constitute a second sensor electronics unit. In exemplary cases, in some instances, a user may want to completely clone the sensor electronics unit 6 by transferring its data and / or configuration (e.g., pairing information, calibration data, timing, whitelist, bonding list, etc.) to another second sensor electronics unit. In another exemplary case, only a subset of the data and / or configuration of the sensor electronics unit 6 may be transferred. Such a transfer may be desirable when the user only wants to clone a specific aspect of the sensor electronics unit 6. In some instances, pairing information may not be transferred between the sensor electronics unit 6 and the second sensor electronics unit because that information is device-specific and may vary between units. In any of these instances, the clone unit 649 may use a communication protocol to transfer one or more parameters of the sensor electronics unit 6 to the second sensor electronics unit.

[0130] As an exemplary example, in some cases, the sensor electronic unit 6 and the display device 20 can typically transfer data using a first communication protocol such as wireless transmission (e.g., BLUETOOTH®). If a second communication protocol utilizing an RF field, such as NFC or RFID, is used with the sensor electronic unit 6, the clone unit 649 can use the second communication protocol to transfer data and / or configuration from the sensor electronic unit 6 to the display device 20. The display device 20 can store the data and / or configuration in its memory. In some cases, this transfer may occur while the sensor electronic unit 6 still has a low battery level, and / or after the battery of the sensor electronic unit 6 has run out and power has been supplied to the transfer using a second communication protocol such as NFC. In some cases, before the battery of the sensor electronic unit 6 runs out, the sensor electronic unit 6 can upload its data and / or configuration to an NFC tag that facilitates passive transfer. In some implementations, cloning can be initiated using a second communication protocol, but the data can actually be transferred from one display device to the other using the first communication protocol. For example, the first communication protocol may be wireless transmission such as BLUETOOTH®. The display device 20 can initiate cloning of the sensor electronics unit 6 via a second communication protocol that can utilize an RF field, such as NFC or RFID. The sensor electronics unit 6 can then transfer its data and / or configuration to either the second sensor electronics unit or the display device 20 via the first communication protocol. Once the data and / or configuration is transferred to the display device 20, the display device 20 can subsequently 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 herein.Subsequently, the display device 20 can transmit data and / or configuration to a second sensor electronics unit. In some cases, this second sensor electronics unit can use the data and / or configuration to set itself up in substantially similar manner to the sensor electronics unit 6 (e.g., by substantially similar pairing, configuration, calibration, etc.).

[0131] Figure 6A illustrates an exemplary interface 620 that allows a user to select functions corresponding to the functional units illustrated in Figure 5C from the display device 20. Interface 620 may be part of a mobile application (for example, 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) that performs and / or has the structure described throughout this disclosure, including a reference to Figure 5C. Interface 620 may include visual, auditory, and / or haptic elements to interact with the user using the display device 20. Interface 620 may be instantiated on user interface 409 (illustrated in Figure 4A). The user can use interface 620 to access various functions of the display device 20.

[0132] In some cases, interface 620 may have multiple panels for displaying information and / or enabling user interaction. For example, but not limited to, panel 610 may include fields that display information about a sensor electronics unit (e.g., sensor electronics unit 6). In some cases, by selecting a field, the user can select a sensor electronics unit and use its sensor function. A sensor electronics unit can be identified by a serial number, alias, name, code, and / or any desired identifier. In some implementations, the identifier can be entered manually and / or selected from a list of available (e.g., previously entered, detected, and / or paired) sensor electronics units. Panel 611 may describe the status of the sensor electronics unit identified in panel 610. In some non-limiting examples, the status may include one or more of the following: shelf mode, low power mode, normal operation, startup, sleep, transmission, idle, low battery, and / or any status description. These statuses can be retrieved and displayed by interface 620 through a server (e.g., network, cloud, etc.) to which the sensor electronics unit transmits such statuses, through other communication protocols (e.g., wireless transmission, or any of the communication protocols described herein), and / or through previous transmissions containing status information from the sensor electronics unit (e.g., via wireless transmission, RF field, and / or any other communication protocols described herein). Panel 612 can describe the pairing status of the display device 20 with respect to the sensor electronics unit displayed on panel 610. In a non-limiting example, a dispaired status may indicate that the sensor electronics unit is not paired with the display device 20 via a communication protocol (e.g., wireless transmission such as BLUETOOTH® and / or any other communication protocols described herein).Other examples include paired (for example, the sensor electronics unit is paired with the display device 20 through the communication protocol described herein), advertising, whitelisted, bonded, and / or any other pairing status.

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

[0134] Figure 6B illustrates an exemplary interface 640 for performing actions in action queue 630 via NFC. Action queue 630 may consist of actions selected from action 613 (e.g., one or more of actions 614, 615, 616, 617, 618, 619, 609) and / or other actions. In this exemplary embodiment, commands are transmitted from the display device 20 to the sensor electronics unit 6 via NFC, but other communication protocols may be used, including wireless transmission, RF field, and / or any other communication protocols described herein. Graphic 632 may show commands to the user and instruct the user to hold the display device 20 close to the sensor electronics unit 6. In some cases, such commands may instruct the user to tap the display device 20 against the sensor electronics unit 6 and / or to hold the display device 20 close to the sensor electronics unit 6. Once the display device 20 is within range of the sensor electronics unit 6, the sensor electronics unit 6 can then perform the actions in action queue 630. In some cases, the display device 20 may also display a prompt to indicate, for example, 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 deployed in a low-power mode, such as shelf mode, after manufacturing to maintain battery charge. This deployment can be done at the factory for shipment (as illustrated with reference to Figure 1B, for example) and / or by the user if they wish to maintain the battery of the sensor electronics unit 6. When the user decides to begin using the sensor electronics unit 6, it can be deployed in its normal operating mode. In some cases, 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) from which a wake-up command can be initiated, making it difficult to wake up the sensor electronics unit 6.

[0136] As discussed above, in some cases, the sensor electronics unit 6 can be woken up from low-power mode by using the activation of a continuous analyte sensor 8 which is communicatively and / or operationally coupled to the sensor electronics unit 6. The sensor electronics unit 6 can be attached to the continuous analyte sensor 8 by electrodes, which allow 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) indicating attachment to the continuous analyte sensor 8, it can be woken up from low-power mode. However, this method of waking up the sensor electronics unit 6 may have drawbacks in some situations. For example, but not limited to, a user may unintentionally wake up the sensor electronics unit 6 by touching the electrodes with their fingers and / or otherwise causing a change in current across the electrodes of the sensor electronics unit 6. In some cases, the sensor electronics unit 6 may also not constantly detect current across the electrodes. Rather, sensing may only occur periodically, such as every 5 minutes, 10 minutes, 15 minutes, or even longer intervals. In such cases, the user may have to wait a considerable amount of time before the sensor electronic unit 6 detects the current across its electrodes and wakes up from low-power mode. This can result in an unsatisfactory user experience.

[0137] In some cases, the low-power sensor electronics unit 6 can draw its operating power from an RF field associated with the display device 20 using electromagnetic radio waves for communication. For example, but not limited to, a communication protocol such as NFC or RFID can be used by the display device 20 to create an RF field, which can enable the display device 20 to communicate with the low-power sensor electronics unit 6. Conveniently, 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 utilizing a wake unit 654. In some implementations, action 614 can be part of an action queue 630 that can perform multiple actions (e.g., actions within action 613).

[0138] Figure 6C illustrates an exemplary timing diagram for waking the sensor electronics unit 6 from a low-power mode using an RF field. The exemplary timing diagram is a timing diagram for 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, in which power consumption is lower than that of at least one other power mode (e.g., normal operation mode). As discussed throughout this disclosure (see, for example, Figures 1B, 5C), the low-power mode can be used during the shipment and / or dormancy period of the sensor electronics unit 6. Transmission 604 can be performed using an RF field-utilizing communication protocol such as NFC or RFID when the sensor electronics unit 6 is in a low-power mode. Transmission 604 can be transmitted to the sensor electronics unit 6 using a display device 20. In some implementations, transmission 604 may include a wake action such as action 614, and / or action 614 may also include transmission 604. Transmission 604 may include commands, data, status, and / or any other desired transmissions. The wake action may also include and / or be performed in combination with other actions, such as any of the actions in action 613. For example, but not limited to, a command may include instructions that require 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 enables the reception of measurement values ​​indicating the user's glucose measurement and / or the 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 in normal operating mode. This advertising may begin immediately or substantially immediately after the sensor electronics unit 6 wakes from low-power mode.

[0139] In some implementations, other commands may 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, and so on. Commands may also include commands for changing the operating mode, calibrating the measurement circuit, turning the sensor circuit on / off, adjusting defined parameters or presets, and so on. These commands may also include any commands described with respect to action 613. In some cases, transmission 604 may include energy (e.g., energy transmitted to power supply via NFC) which can be used to power the display device 20 delivered to the sensor electronics unit 6 to power the reception of commands and / or any steps desired to perform the commands. For example, but not limited to, transmission 604 may include energy from the sensor display device 20, transmitted 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 it to move from a low-power mode to a normal-power mode. Once the sensor electronics unit is in normal-power mode, it can then be powered for its own operation. In some cases, the energy received by the sensor electronics unit 6 can power all transitions from low-power mode to higher-power modes (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 normal-power modes, but it can power the sensor electronics unit 6 sufficiently to receive commands to change from low-power mode to higher-power mode.

[0140] The data from the display device 20 transmitted to the sensor electronic equipment unit 6 in transmission 604 may include data about the display device 20 (e.g., serial number, authentication, security information, manufacturer / model, etc.). In some cases, this data (alone or in combination with transmitted commands, status, etc.) may facilitate pairing between the sensor electronic equipment unit 6 and the display device 20 using other communication protocols. The status may include any information about the status of the display device and / or the functionality of the display device (e.g., ready, standby, error in operation, etc.). During or after transmission 604, or both during and after, the sensor electronic equipment unit 6 may be allowed to proceed to normal operation in period 606. 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] When NFC or RFID is used, transmission 604 can be transmitted using a “tap to start” initiation. Specifically, when NFC is used, the NFC may have a range of several centimeters (e.g., 10 centimeters or less) and the user can transmit transmission 604 by bringing the display device 20 close to and / or touching the sensor electronics unit 6. Such physical interaction may be advantageous by providing the user with a physical initiation that can be intuitive. As described throughout this disclosure, a “tap to start” initiation may be desirable in a variety of cases. Exemplarily, but not limited to, 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., shelf, mode, normal operation, high-power mode, etc.) when desired. In some cases, NFC can be used to transmit commands, data, calibration information, etc. between the display device 20 and the sensor electronics unit 6. Preferably, using NFC in general, or at the start of a "tap to start" operation, may be advantageous in allowing the user to change the settings of the sensor electronic device unit 6 without going through a number of steps for pairing and / or authentication (such as Bluetooth®). Such use of NFC can also enable reliable data and command transmission, and can be done on demand without requiring waiting for the transmission timing of other communication protocols such as Bluetooth®.

[0142] In some implementations, normal operation during period 606 may include using the communication protocol of transmission 604. In some implementations, normal operation during period 606 may include using a second communication protocol, such as a communication protocol that utilizes wireless transmission. In some implementations, this second communication protocol may not be the same as the first communication protocol. As an exemplary example, BLUETOOTH® can be given as this second communication protocol. In some embodiments, after transmitting data via the second communication protocol, the sensor electronic equipment unit 6 can be returned to low-power mode.

[0143] Figure 6D illustrates an exemplary flowchart illustrating the process described in Figure 6C. In some cases, a user of display device 20 may wish to use Method 620 when they wish to pair their display device 20 with 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 predetermined intervals, such as every 20 minutes. Instead of waiting for that timing, the user may wish to connect the display device 20 to the sensor electronics unit 6 substantially immediately. For example, the user may want to immediately add the display device 20 to a whitelist during an emergency when no other display devices are available for use. The sensor electronics unit 6 can detect analyte measurements of the user or someone else (e.g., someone under the user's protection). Therefore, the user can use Method 620 to pair the display device 20 with the sensor electronics unit 6 on demand to facilitate assistance during an emergency. As another exemplary example, a healthcare worker may want to immediately pair the display device 20 with a patient's sensor electronic unit 6 when making rounds. Since the healthcare worker may not have waiting time over a predetermined time interval on the whitelist, the healthcare worker may use method 620 appropriately to immediately connect with the user's sensor electronic unit 6. As another exemplary example, a user may simply find it inconvenient to wait a predetermined time interval to connect the sensor electronic unit 6 to the display device 20. Therefore, such a user may want to use method 620 to connect the display device 20 to the sensor electronic unit 6 substantially on demand.

[0144] In block 622, the sensor electronics unit 6 can operate in low-power mode. In block 624, the sensor electronics unit 6 can receive signals using a first communication protocol. As an exemplary example, a second communication protocol can be used by the sensor electronics unit 6 and / or the display device 20 to utilize an RF field such as NFC or RFID. This transmission may include, but is not limited to, commands for pairing the first communication protocol, changing the operating mode, calibrating the measurement circuit, turning the sensor circuit on / off, adjusting defined parameters or presets, and other commands. The transmission may also include, but is not limited to, any actions such as action 613. Exemplarily, but is not limited to, this transmission may include multiple actions that can be queued by the user using the display device 20. In some cases, such actions may include one or more of the following: operating mode actions (e.g., action 619), pairing actions (e.g., action 615), and / or white / bonding list setting actions (e.g., action 618). Conveniently, the operating mode action allows the sensor electronic equipment unit 6 to be switched from a low-power mode to a different operating mode, such as a normal operating mode. The pairing action can allow the display device 20 to communicate with the sensor electronic equipment unit 6 using a second communication protocol and pair with the sensor electronic equipment unit 6 using a first communication protocol. For example, the sensor electronic equipment unit 6 can be paired with the display device 20 by exchanging pairing information for the first communication protocol for communication using the first communication protocol, such as using a second communication protocol that uses an RF field, such as NFC or RFID, or 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 electronic equipment unit 6 for the first communication protocol as desired.In some cases, this action may include instructions on how to reorder the whitelist, pointers for modifying the whitelist, copies of the new whitelist, and / or any other methods of setting up the whitelist as described in this disclosure (for example, as described above with reference to Figures 5C and 6A). Other actions described in this disclosure may also be used. Conveniently, this allows for user flexibility and convenience when setting up the connection. In some implementations, the display device 20 may autonomously decide which actions to queue based at least in part on the user's usage patterns (e.g., the use of one or more of the actions 614, 615, 616, 617, 618, 619, 609 at a particular time and / or situation of the day, which allows the display device 20 to learn to initiate the same action from among the actions 614, 615, 616, 617, 618, 619, 609 at the same time and / or situation of the day) and / or the needs of the display device 20 (e.g., retrieving missing data).

[0145] Next, in block 626, the sensor electronic equipment unit 6 can be changed from a low-power mode to a desired operating mode. Various operating modes can be used, but are not limited to illustrative examples, such as a normal operating mode, a calibration mode, a blind mode (for example, a mode in which all or some of the data is not displayed on the display device 20), and / or any desired mode. In some cases, the desired operating mode in block 626 can be the normal operating mode.

[0146] In block 628, the sensor electronic equipment unit 6 can then communicate using a first communication protocol, which includes wireless transmission such as BLUETOOTH® and / or any other communication protocols described herein. Since the sensor electronic equipment unit 6 has already received information such as pairing information via a second communication protocol, it can communicate using this first communication protocol 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, the user may want to put the sensor electronics unit 6 into a low-power mode from another operating mode. For example, but not limited to, the user may want to monitor glucose only once a week or once a month. Since some sensor electronics units 6 may have a predetermined (or limited) battery capacity, putting the sensor electronics unit 6 into a low-power mode may allow the sensor electronics unit 6 to be used for several more days.

[0148] Figure 6E illustrates an exemplary timing diagram of the sensor electronics unit 6 entering low-power mode. During period 652, the sensor electronics unit 6 may have normal operation or any operation that uses more power / energy than low-power mode. In normal operation, the sensor electronics unit 6 may communicate using one or more communication protocols, including wireless transmission such as BLUETOOTH®, or any communication protocols described in this disclosure. In some implementations, transmission 654 may put the sensor electronics unit 6 into low-power mode during period 656 by using commands such as a command instructing the sensor electronics unit 6 to enter low-power mode and / or a low-power start command. Period 656 may occur after a time delay 658 from transmission 654. The time delay 658 may be a predetermined delay (e.g., 5 seconds, 4 seconds, 3 seconds, 2 seconds, 1 second, or less). Transmission 654 may be made using any communication protocol described in this disclosure. As an exemplary example, transmission 654 can be performed using an RF field for communication such as NFC or RFID, or using wireless transmission such as BLUETOOTH®. When NFC is used, since NFC can have a range of several centimeters (e.g., 10 centimeters or less), the user can transmit transmission 654 by bringing the display device 20 close to and / or touching the sensor electronic equipment unit 6. Such physical interaction may be advantageous in that it provides the user with a physical initiation that can be intuitive. The display device 20 may be far from the sensor electronic equipment unit 6 and / or may already be communicating with the sensor electronic equipment unit 6 via wireless transmission such as BLUETOOTH®, so using wireless transmission such as BLUETOOTH® may be advantageous.

[0149] In some implementations, the low-power mode may be a shelf mode or other power mode that uses less power. For example, as described with reference to Figures 1B and 6A, the low-power mode may be a mode that turns off one or more of the following: a transmission circuit (e.g., BLUETOOTH® wireless), a measurement circuit, a sensor circuit, a processor, or others. It may also reduce the frequency of refresh, advertisement, measurement analysis, and / or any other periodic operation of the sensor electronics unit 6. The sensor electronics unit 6 may later be woken up in a process substantially similar to the process described with reference to Figures 6C-D.

[0150] As described in this disclosure with reference to Figures 6A-B, wake actions (e.g., action 614 and / or other waking actions described herein) can be performed in combination with other actions, such as one or more of action 613. These actions can be performed in a queue, such as action queue 630. For example, but not limited to, waking up the sensor electronics unit 6 can be done in combination with any one or more of actions 614, 615, 616, 617, 618, 619, and 609. B. Asynchronous Communication

[0151] In some cases, communications transmitted by the sensor electronics unit 6 may follow a specific communication pattern, such as the communication patterns described with reference to Figures 6C and 6E, but not limited to those described. However, in some cases, a user may desire to transmit / receive communications that do not follow the timing of that communication pattern. For example, a data retrieval action, such as action 617, can be used by the display device 20 to retrieve data from the sensor electronics unit 6 outside of the communication pattern. As described herein, a data retrieval action (e.g., action 617 and / or other waking actions described herein) 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 action queue 630.

[0152] Figure 7A illustrates an exemplary timing diagram of an exemplary first communication protocol for the sensor electronics unit 6. The measurement line 704 illustrates that the sensor electronics unit 6 can substantially always receive measurement values. The measurement line 704 can represent analog and / or digital measurement values. In the case of digital measurement values, the solid line of the measurement line 704 can represent the repeated reception of discrete digital data measurement values.

[0153] Communication line 702 illustrates the timing of a first communication protocol in which the sensor electronic equipment unit 6 transmits communications indicating the taken measurements to one or more display devices 20A-N. During these times, the sensor electronic equipment unit 6 can also receive communications. For example, but not limited to, wireless transmission such as BLUETOOTH® can be used as the first communication protocol for communication line 702 to transmit data indicating blood glucose measurements from the sensor electronic equipment unit 6 to the display device 20. Communications can be made to occur periodically, such as at times 708, 710, 712, and 714.

[0154] In some implementations, the time between each sequential time 708, 710, 712, and 714 can be 5 minutes, 10 minutes, 15 minutes, 20 minutes or more, as desired. At each of the times 708, 710, 712, and 714, the sensor electronics unit 6 can transmit communications along the communication line 702. In a non-limiting example, at time 708, the communication window between the sensor electronics unit 6 and the display device 20 can be started by a rising edge 716. The sensor electronics unit 6 can then actively transmit / receive communications over a predetermined amount of time on the edge 718 where the communication window is opened. For example, but not limited to, 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 cases, the amount of time may be at least partially related to the amount of data being transmitted and / or the transmission time of that data.

[0155] As an illustrative example, but not limited to, the relationships between times 708, 710, 712, 714 and the time can indicate the frequency with which communication occurs, and this frequency can be varied based on a predetermined transmission frequency based on user-defined settings and / or activities. For example, but not limited to, when a user desires to have very regular and / or frequent data points regarding their blood glucose levels, a period of 5 minutes or less can 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). Such regular and / or frequent data points may be desirable when the user experiences normal activities such as walking, working, daily exercise, driving, etc., so that the user can analyze trends in their activities. As another non-limiting example, when the user does not desire many data points, 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). For example, but not limited to, the user's blood glucose level may be relatively normal or stable. By not transmitting measurement data frequently, the user can extend the lifespan 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 conditions. For example, a shorter period may be used if clinically high-risk situations are detected, such as conditions that at least partially indicate a hyperglycemic or hypoglycemic event. In such a situation, the sensor electronic equipment unit 6 and / or the display device 20 can detect when the user's blood glucose level falls below a threshold for hypoglycemic glucose levels or exceeds a threshold for hyperglycemic glucose levels.In such cases, the sensor electronics unit 6 can increase its connection establishment frequency so as to reduce the time between two consecutive measurement transmissions. As another example, since diabetic patients may be at risk of experiencing hypoglycemia during sleep, the sensor electronics unit 6 and / or display device 20 can detect when the user is sleeping and transmit measurement data more frequently. The time between consecutive measurement transmissions can also be variable with respect to a predetermined schedule, such as transmitting more frequently during meal times. In some cases, the time between consecutive measurement transmissions can be set by sending commands and durations between such consecutive measurement transmissions via NFC or RFID so that the user can tap (or bring close enough) the display device 20 to the sensor electronics unit 6. Conveniently, this allows the user to set the frequency of measurement transmissions on demand.

[0156] Figure 7B illustrates an exemplary timing diagram of the sensor electronics unit 6 showing signal processing that may occur during communication of the first communication protocol in Figure 7A. For example, but not limited to, the sensor electronics unit 6 may periodically perform signal processing on measurement data during communication, such as communication on communication line 702. Signal processing line 722 illustrates the timing of signal processing. As an exemplary example, but not limited to, communication windows may open at times 708, 710 as described with respect to Figure 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 herein. In some cases, signal processing may include data aggregation calculations to compile and process measurements taken since the last communication to determine, for example, trends in analyte measurements, blood glucose measurements, and / or other indications of the user's blood glucose level and / or health status in the sensor electronics unit 6. In some cases, the conversion function can be used to convert the measured raw data into processed data such as estimated glucose values. Signal processing can also determine the user's state (e.g., normal, hypoglycemia, hyperglycemia) and trigger alarms and / or notifications if there are any health concerns.

[0157] Figure 7C illustrates an exemplary transmission from the sensor electronics unit 6 using a second communication protocol to initiate communication using a first communication protocol, as shown in the exemplary timing diagram of Figure 7B. For example, transmission 732 may utilize a second communication protocol, such as an RF field-based communication protocol, including, but not limited to, NFC or RFID, for communication line 706. Transmission 732 may further include a command to initiate communication in accordance with the first communication protocol (e.g., utilizing wireless transmission such as BLUETOOTH®), whose timing is represented by communication line 702. Other transmissions in transmission 732 may include transmissions associated with data retrieval actions, such as action 617. The communication may 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, waveform 734 may represent an additional communication window opening. In some implementations, this additional communication window opening allows aggregated measurements to be transmitted when processed by the sensor electronics unit 6 before transmission 732. For example, but not limited to, data aggregated by processing initiated at time 724 may be transmitted in transmission 734 in response to transmission 732. Transmission 734 may occur after a time delay 736 from transmission 732. Conveniently, in some implementations, transmission 734 may occur without changing and / or shifting the scheduled communication window opening on communication line 706. This ability not to change and / or shift the communication schedule allows the user to receive / transmit data without having to wait for the entire communication timing for the next communication (e.g., the period between time 710 and time 708), as would be the case if the communication schedule were changed.

[0158] In other implementations, instead of transmission 734, data transmission can utilize communication using a second communication protocol. For example, but not limited to, the display device 20 may transmit recent data by sending transmission 732 to the sensor electronics unit 6. The sensor electronics unit 6 can then return the data to the display device 20 using the second communication protocol. C. Starting or stopping a sensor session

[0159] In some cases, the 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, the continuous analyte sensor 8 may have a certain lifespan in terms of usage by the user. As an exemplary example, but not limited to, the user may use the 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 for any amount of time that the continuous analyte sensor 8 was built and functioning before changing the continuous analyte sensor 8. For example, but not limited to, the amount of time that the continuous analyte sensor 8 can function may be referred to as a sensor session. Starting or stopping a sensor session can be done in combination with other actions, such as one or more of the actions 613. These actions can be done in a queue, such as the action queue 630.

[0160] As an illustrative example, components of the sensor electronics unit 6 may be replaced periodically. For example, 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 to 30 days). The sensor electronics unit 6 may be configured to be powered and / or started up for a much longer period than the continuous analyte sensor 8, and the sensor electronics unit 6 may have power for 1 month, 2 months, 3 months, 4 months, 5 months, 6 months or more until its power supply (e.g., battery and / or power supply 303) runs out. Replacing these components may be difficult and costly, including the time and financial costs of assistance from trained personnel. Reducing the replacement of such components, including batteries, when replaceable, would greatly improve the convenience of the sensor electronics unit 6 for the user.

[0161] In some implementations, the sensor electronics unit 6 can connect to the continuous analyte sensor 8 when it is used for the first time (or, in some cases, restarted after a battery replacement). The display device 20 and the sensor electronics unit 6 can establish communication for the first time, when the sensor electronics unit 6 is used for the first time or restarted (e.g., after a battery replacement). Once the display device 20 and the sensor electronics unit 6 have established communication, they can communicate periodically and / or continuously over the lifespan of several sensors (e.g., the continuous analyte sensor 8) until, for example, the battery or the entire sensor electronics unit 6 is replaced. Each time a sensor is replaced, a notification of the new sensor 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 herein).

[0162] In several implementations, the sensor electronics unit 6 can collect and / or process sensor measurements from the continuous analyte sensor 8 and periodically transmit sensor information representing the sensor measurements to the display device 20. The measurements can be collected and transmitted throughout the lifespan of the continuous analyte sensor 8 (e.g., in the range of 1 to 30 days or more). In some cases, the measurements are often transmitted sufficiently to adequately monitor analyte levels, such as blood glucose levels. Rather than having the radio frequency ("RF") circuits of the sensor electronics unit 6 and the display device 20 communicate continuously, the sensor electronics unit 6 and the display device 20 can establish a communication channel between them regularly and / or periodically. Thus, the sensor electronics unit 6 can communicate wirelessly with the display device 20 at predetermined time intervals. The duration of these predetermined time intervals can be selected to be long enough to prevent the sensor electronics unit 6 from consuming an undesirable amount of energy / power by transmitting data too frequently, while still being frequent enough to provide sensor information (e.g., measured analyte values) to one or more display devices for output to the user in substantially real-time. As described herein, the transmission of this data may, if desired, occur at predetermined time intervals and / or irregularly / non-regularly.

[0163] The 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. When 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 that it can be initialized and calibrated. Similarly, the user may wish to stop the sensor when the user wishes to replace the sensor. Also, in some cases, the user may not start / end the sensor session during connection / disconnection to the sensor. Instead, as a non-limiting example, the user may wish to start / stop the user session after a poor connection between the sensor electronics unit 6, the sensor (e.g., continuous analyte sensor 8), and / or the display device 20, to synchronize data acquisition until a certain time, stop data acquisition, and / or reconnect. Having such capability can allow the user to acquire data more quickly and / or have a better user experience. In some cases, it may be desirable to stop the sensor session when the sensor is no longer collecting data and / or the sensor is collecting bad data. Stopping the sensor session at this point prevents malformed data from continuing to be processed by the sensor electronics unit 6, and / or prevents the display device 20 from warning the user that no data has been collected and / or that malformed data has been collected.

[0164] However, in some implementations, starting / stopping a sensor session can be unintuitive and / or cumbersome for the user. For example, but not limited to, returning to Figure 7A, communication line 702 illustrates the timing of a first communication protocol, and the sensor electronics unit 6 can open a communication window and transmit / receive communications indicating the measurements taken by the display device 20. For example, but not limited to, the first communication protocol can utilize wireless transmission such as BLUETOOTH®, which can be used to transmit data indicating blood glucose measurements. Communication windows 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 the sensor session, the user can use a second communication protocol different from the first communication protocol. The second communication protocol may include a communication protocol that creates an RF field, such as NFC or RFID.

[0165] Figure 7D illustrates an exemplary timing diagram showing a transmission via a second communication protocol that stops a sensor session, such as the sensor session referenced in Figure 7A. In this exemplary embodiment, transmission 742 can utilize a second communication protocol, such as a communication protocol that creates an RF field including NFC or RFID, along the communication line 706. Transmission 742 may include a command or instruction to stop measurement and / or to stop wireless transmission (e.g., transmission of data via BLUETOOTH®). Reception of transmission 742 may stop measurement and communication on communication line 702 in accordance with a first communication protocol (e.g., closing communication via communication line 702). In some implementations, there may be a delay after transmission 742 before stopping measurement and communication in accordance with the first communication protocol. 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 the user or automatically by the sensor electronics unit 6 and / or display device 20. After the time delay 746, measurement on measurement line 704 may be turned off.

[0166] Figure 7E illustrates an exemplary timing diagram showing the timing of a transmission via a second communication protocol to initiate a sensor session. In this exemplary embodiment, transmission 752 can utilize a second communication protocol, such as a communication protocol that creates an RF field including NFC or RFID, along the communication line 706. Reception of transmission 752 can initiate measurement and communication along the first communication protocol along the communication line 702. In some implementations, there may be a delay after transmission 752 before the initiation of measurement and communication along the first communication protocol. This delay can be a time delay 756 and 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 separate actions. As described herein, pairing actions (e.g., action 615 and / or other pairing actions described herein) 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 capability can be advantageous in improving the user experience. For example, some communication protocols, though not limited to these, have a vast number of pairing and / or authentication procedures. As a non-limiting example, wireless transmission such as BLUETOOTH® can utilize a handshake procedure in which a device (e.g., display device 20) transmits authentication information and is selected from a list of available devices. If the procedure has too many steps, it can impair the user experience and, furthermore, excessive communication can drain battery life and bandwidth.

[0168] As background, and as a non-limiting example, the display device 20 may have a unique address, such as a unique 48-bit address that can be represented as a 12-digit hexadecimal value. The address or a portion of the address may be used as an identifier for other devices via the same wireless transmission, such as BLUETOOTH®, and such other devices may also have an address for communication connections. The BLUETOOTH® device may also have a user-friendly name provided to the device, as seen within the display.

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

[0170] In some cases, during the initial connection, two devices can be paired using an authentication process, and the user validates the connection between the first and second devices. The authentication flow may vary depending on the user interface of the devices. At times, pairing may involve clicking a button, entering a numeric code, entering a common PIN, entering an alphanumeric string, or other methods.

[0171] The BLUETOOTH® pairing process involves many steps and may prompt the user to enter information or take other actions, thus compromising the user experience. The procedure for pairing this CGM device needs to be simplified so that users can more easily monitor their glucose levels on their own devices. Furthermore, the sensor electronics unit 6 may lack a user interface, making it more difficult for the user to initiate pairing via several 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. RF fields such as NFC or RFID allow the user to simply place the display device substantially next to the sensor electronics unit 6. This NFC or RFID capability can be advantageous when the sensor electronics unit 6 lacks a user interface.

[0172] Figure 8 is an illustrative flowchart illustrating how pairing for communication using one communication protocol can be facilitated using the other communication protocol. Process 800 can be performed by the sensor electronics unit 6 and / or display device 20 used with the CGM system.

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

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

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

[0176] Similarly, in block 804, a second device can receive addresses, pairings, commands, and / or other information from the first device using a second protocol. Pairing information may include timing information, encryption keys, authentication information, advertising parameters, addresses, manufacturer / model, name, GAP, IRK, and similar information.

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

[0178] As an exemplary embodiment, process 800 can be part of a “Tap to Start” NFC protocol, and a user having a display device 20 can connect the display device 20 to the sensor electronic unit 6 of the CGM system by tapping (or bringing close enough) the display device 20 to the sensor electronic unit 6. This tap can use an RF field protocol such as NFC or RFID as a second communication protocol. Thus, this second communication protocol can facilitate pairing the display device 20 and the sensor electronic unit 6 and communicating using a first communication protocol such as BLUETOOTH®.

[0179] In some cases, using process 800 (which may be called out-of-band pairing) can save power beyond that of conventional first communication protocol pairing. For example, but not limited to, advertising and connecting a display device 20 to a sensor electronics unit 6 using wireless transmission such as BLUETOOTH® can drain the battery of the sensor electronics unit 6. In some cases, the sensor electronics unit 6 may advertise using wireless transmission such as BLUETOOTH® for different durations depending on the display device 20 attempting to connect. As a non-limiting example, advertising and connection times using BLUETOOTH® for a special 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, shorter connection times can lead to energy savings when NFC or RFID is used for pairing.

[0180] As an illustrative example, instead of advertising, connection time, and power consumption associated with wireless transmission (e.g., Bluetooth®), pairing for wireless transmission can be initiated using NFC or similar technologies. When used in a "tap to start" manner, connecting the display device 20 can establish a connection on demand without incurring (or using less of) the power consumption associated with standard wireless transmission advertising and connection. E. Setting up the whitelist and / or bonding list

[0181] In some implementations, actions can be taken via a 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 may include action 618 and / or similar actions, and some actions may utilize the white / bonding list setting unit 658. The following exemplary examples described with reference to the whitelist and bonding list may be part of action 618 and / or separate actions and / or utilize the white / bonding list setting unit 658. As described herein, white / bonding list setting actions (e.g., actions 618 and / or other actions described herein that set, add, delete, and / or manipulate the whitelist and / or bonding list) may be performed in combination with other actions, such as one or more of action 613. These actions may be performed in a queue, such as action queue 630.

[0182] Figures 9A-F illustrate exemplary operations of whitelisting and / or bonding lists using multiple communication protocols. Figure 9A illustrates exemplary whitelisting 906 and bonding lists 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 process 800. As described in process 800, a second communication protocol can be used to enable the sensor electronics unit 6 and the display device 20A to send / receive addresses, pairing, and / or other information from 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 a first communication protocol using wireless transmission such as BLUETOOTH®, but is not limited to this.

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

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

[0185] Figure 9C illustrates exemplary whitelists and bonding lists that are updated when the sensor electronics unit 6 and the display device 20A are unpaired using a second communication protocol. Conveniently, using a second communication protocol such as an RF field (e.g., NFC or RFID) allows the user to dynamically and on-demand remove the display device 20A (or any other display device such as display device 20C) from the whitelist (e.g., whitelist 906). This can result in power savings in some situations. As an exemplary example, the sensor electronics unit 6 may advertise to a display device on the whitelist 906. However, if that display device is no longer within range and / or no longer desired for use, the sensor electronics unit 6 may unintentionally waste energy when attempting to make that connection. Also conveniently, removing the first display device from the whitelist 906 can prevent the first display device from inadvertently connecting when such a connection is undesirable. For example, but not limited to, a user may want to connect a second display device to the sensor electronic equipment unit 6, and by connecting the first display device to the sensor electronic equipment unit 6, it is possible to prevent the second display device from being connected by placing it in that position in the whitelist 906.

[0186] As an illustrative example, but not limited to, the sensor electronics unit 6 may 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 may send a command to the sensor electronics unit 6 instructing it to remove the display device 20A from slot 908A. In some cases, this may leave an empty spot in the whitelist 906.

[0187] The bonding list 914 can operate independently of the whitelist 906. The removal of the display device 20A from the whitelist 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 available slots, it can delete the pairing information in one or more slots of the bonding list 914. The bonding list 914 can store the pairing information of one or more applications of the sensor electronics unit 6 and the display devices 20A, C (e.g., mobile applications downloaded from entities that create and / or own and / or license the apps, and / or from app stores such as APPLE, INC. or GOOGLE INC., or from others). In some cases, this deletion can be achieved by the display device 20A sending at least a command / request via a second communication protocol to remove its pairing information from the bonding list 914. This deletion may be desired if the user does not want the sensor electronics unit 6 to communicate further with the display device 20A and does not want to take the risk of connecting the display device 20A. Removing the display device 20A from the bonding list 914 conveniently reduces the risk of unwanted communication / connection by removing the pairing information from memory.

[0188] Figure 9D illustrates an embodiment in which a display device 20D can be added to the whitelist 906 of the first communication protocol and a display device 20C can be removed from the same whitelist 906 using a second communication protocol. First, the pairing information of the display device 20A can be stored in slot 908A, the pairing information of the display device 20C can be stored in slot 908B, and then the display device 20C and the sensor electronics unit 6 can be paired for communication using the second communication protocol. The display device 20D can be paired with the sensor electronics unit 6 and communicate through 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, by pairing the display device 20D with the sensor electronics unit 6, the display device 20D can be replaced with another display device paired with the sensor electronics unit 6. This may be desirable when all slots in the whitelist 906 are filled and / or when the user wishes to pair the display device 20D with the sensor electronics unit 6. In some implementations, the display device 20D may also send a command to the sensor electronics unit 6 via a second communication protocol instructing the sensor electronics unit 6 to exchange the pairing information of the display device 20C on the whitelist 906 for the pairing information of the display device 20D. In some implementations, the command may include an instruction to 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 display device 20D (e.g., receiver, mobile device, etc.), the sensor electronics unit 6 may exchange the display devices 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 send information to the display device 20D indicating at least the contents of the whitelist 906, including slot 908B. The sensor electronics unit 6 can then send information indicating the contents of such whitelist 906 to the display device 20D. The display device 20D can then choose to remove the pairing information of display device 20C from slot 908B and add the pairing information of display device 20D, either through user input or automatically (based on learned patterns, such as the type of device or the user disconnecting the device at a specific time of day). As illustrated in Figure 9D, the pairing information of display device 20D can be exchanged with the pairing information of display device 20C in slot 908B.

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

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

[0191] Since the sensor electronic equipment unit 6 can communicate sequentially with the display devices in slots 908A to N (for example, the sensor electronic equipment unit 6 first communicates 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 to N receive messages. Furthermore, there may be differences in reliability (and / or robustness) in the communication between the sensor electronic equipment unit 6 and each of the display devices in slots 908A to N. In some cases, the display device in slot 908A that receives information first can be designated as the primary display device, the display device in slot 908B as the secondary display device, the display device in slot 908C as the tertiary display device, and so on. In some cases, it may be desirable to switch the order in which each display device is located in slots 908A to N. As an exemplary embodiment, but not limited to, 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 to N can communicate with the sensor electronics unit 6 to change the designation of one or more of the display devices 20A to N. Returning to Figure 9E, as a non-limiting example, but not limited to, the pairing information of display device 20C can be initially stored in slot 908B, and the pairing information of display device 20A can be initially stored in slot 908A. For example, display device 20C can communicate with the sensor electronics unit 6 using a second communication protocol, such as an RF field communication protocol like NFC or RFID. Through the second communication protocol, display device 20C can send a command to the sensor electronics unit 6 to move the sensor electronics unit to slot 908A, and then move the pairing information of slot 908A (e.g., the pairing information of display device 20A) to another slot (e.g., slot 908B). In some implementations, the command may include a request to designate display device 20C to a specific status (e.g., primary, secondary, tertiary, etc.). Therefore, the sensor electronics unit 6 can then switch the display device 20C from slot 908B to slot 908A, and then switch the display device 20A from slot 908A to slot 908B, at least in part on the sensor electronics unit 6's determination that slot 908A corresponds to a specific requested status. When making that switch, the sensor electronics unit 6 can also switch the display device 20A to slot 908B, at least in part on the determination that the display device 20A must be switched to slot 908B in order to provide appropriate priority, since the display device 20C has been switched to slot 908A. In some implementations, the command may include an instruction that causes the sensor electronics unit 6 to send information to the display device 20C indicating at least the contents of a whitelist 906 that includes slot 908B. The sensor electronics unit 6 can then send information indicating the contents of such a whitelist 906 to the display device 20C.Next, the display device 20C may choose to switch the pairing information of slot 908B and slot 908A through user input or automatically (for example, based on learned patterns such as the type of device or the user's use of the display device as the primary display device at a specific time of day).

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

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

[0195] By using a second communication protocol, such as an RF field communication protocol like 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 of the sensor electronics unit 6's first communication protocol (e.g., to slot 908B). In some cases, the first communication protocol may be BLUETOOTH®. 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 may fail, may have data corruption, and may have errors when attempting to identify and pair the display device 20C. In such situations, the identification and pairing information of the display device 20C can be moved from the bonding list 914 to the whitelist 906, allowing a user to connect to the display device 20C.

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

[0197] In some implementations, the sensor electronics unit 6 can communicate with the display device 20 using one communication protocol. However, a different communication protocol can be used in specific situations. For example, in some implementations, the user may want to connect the display device 20 to the sensor electronics unit 6 to collect historical data or data generated to analyze past events in which the sensor electronics unit 6 collected data. Such connections for collecting historical data can be made once or periodically, as desired. For example, but not limited to, the display device 20 may be in a mode where the user cannot view glucose values ​​in real time, but can receive glucose alerts and alarms during a sensor session. The data can later be downloaded by a medical professional or any user who wishes to view the data using another display device (e.g., one of display devices 20A-N). In another non-limiting embodiment, the user may want to switch from a previously used display device (e.g., another one of display devices 20A-N) to a display device (e.g., one of display devices 20A-N). A newly connected display device allows the user to download historical data from the sensor electronics unit 6. In this example, the display device downloading the historical data can provide the sensor electronics unit 6 with timing information for at least part of the period during which the sensor electronics unit 6 should transmit the lost data. In another non-limiting embodiment, the sensor electronics unit 6 can 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. In another non-limiting embodiment, the user and / or medical provider may wish to download data periodically and, consequently, wish to connect the display device 20 to the sensor electronics unit 6 to collect historical data.

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

[0199] In some implementations, commands and / or requests can be transmitted from the display device 20 to the sensor electronics unit 6 using NFC or RFID. Such commands or requests may include any desired commands, including initiating transmission for a communication protocol (e.g., wireless transmission such as BLUETOOTH® or any other communication protocol described herein), pairing with a display device (e.g., wireless transmission such as BLUETOOTH® or any other communication protocol described herein), stopping transmission for a communication protocol (e.g., wireless transmission such as BLUETOOTH® or any other communication protocol described herein), sleep, low power, wake up, calibration of the sensor electronics unit 6 and / or continuous analyte sensor 8, starting or stopping a sensor session, transmitting past data, and / or commands associated with one or more of the actions 613. In this way, in some cases, data transfer can be initiated via wireless transmission such as BLUETOOTH® using an RF field-based communication protocol such as NFC or RFID. This data may include data showing estimated blood glucose levels, historical data showing blood glucose levels, pairing information, status, model number, error logs, communication conditions (e.g., previous communications or history such as the number of previously lost communications, previous advertising interval / duration budget, and / or history of time to connection associated with a particular display device), and more.

[0200] In some implementations, when the first communication protocol is not functioning and / or when some form of failure occurs, a second communication protocol can be used to transmit information about error conditions or any type of data that may be useful in assisting technical support. For example, in some implementations, but not limited to, 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 may fail or be interrupted, so the sensor electronics unit 6, the display device 20, or neither has full communication capability via wireless transmission. To diagnose a problem, it may be desirable to obtain diagnostic and / or error condition information (e.g., an error log). Diagnostic and / or error condition information can be obtained using a second communication protocol that uses an RF field, such as NFC or RFID. Using a second communication protocol may be advantageous in that it allows for the retrieval of diagnostic and / or error condition information 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 exemplary example, the display device 20 may transmit commands to the sensor electronics unit 6 via a communication protocol that uses an RF field, such as NFC or RFID. The sensor electronics unit 6 may then transmit diagnostic and / or error status information using the same communication protocol. In some cases, the display device 20 may then transfer this information to a server (e.g., a network, cloud, etc.) via a communication protocol such as a cellular connection, Wi-Fi, or any communication protocol described herein.

[0201] In some cases, it may be desirable to receive data from the sensor electronic equipment unit 6 when its battery level is low or dead. In some implementations, a communication protocol can be used to retrieve this data, including, but not limited to, data indicating estimated blood glucose levels, historical data indicating blood glucose levels, pairing information, status, model number, error logs, and so on. For example, but not limited to, a communication protocol using an RF field such as NFC or RFID can use the energy of the display device 20 to power the transmission of the sensor electronic equipment unit 6 through that same communication protocol. As an exemplary example, if NFC is the communication protocol, the display device 20 can use induction to create an RF field. The sensor electronic equipment unit 6 may be equipped with an NFC tag to store data. Therefore, the display device 20 may have an NFC reader that can read the NFC tag even when the sensor electronic equipment unit 6 has little or no power. In some implementations, the use of the communication protocol by the display device 20 can actually power the unit of the sensor electronic equipment unit 6 and transmit data. As an illustrative example, but not limited to, the magnetic inductance of the RF field created by the display device 20 using the NFC communication protocol can enable inductive charging or wireless energy transfer 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 the circuitry of the sensor electronics unit 6 (e.g., application-specific integrated circuits ("ASICs") and / or other hardware) to recover data, and / or this 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] Conveniently, there may be situations where a user wishes to retrieve such data from their sensor electronic device unit 6 after the sensor electronic device unit 6's battery level is low or it has run out. For example, but not limited to, a user may send their sensor electronic device unit 6 to a health provider or a third party at the end of a sensor session. At that stage, the sensor electronic device unit 6's battery may become low or run out. The health provider or third party can then download the data from the sensor electronic device 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 electronic device unit 6, and the sensor electronic device unit 6 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 (for example, using action 609 and / or clone unit 649). Conveniently, if the user transfers data after the sensor electronics unit 6 has run out of power or has very little power (e.g., the battery is almost or completely depleted), the user can transfer as much information as possible before switching to a new sensor electronics unit. Thus, while using NFC and clone actions such as action 609, the user can then power the data transfer / information transfer from the sensor electronics unit 6 to the display device 20, even if the sensor electronics unit 6 has almost or completely depleted battery power.

[0204] As another non-limiting example, a user may neglect to monitor their blood glucose levels and maintain their device. If a user wishes to obtain information from the sensor electronics unit 6 when the battery level of the sensor electronics unit 6 is low or nonexistent, the user may use NFC to power the transfer.

[0205] In some implementations, multiple communication protocols can be used, with some types of communication being transmitted through one type of communication protocol and other types of communication being transmitted through another type of communication protocol.

[0206] As an illustrative example, but not limited to, NFC can be used to transmit all commands and / or requests from the display device 20 to the sensor electronics unit 6. Such commands or requests may include, but are not limited to, initiating transmission for a communication protocol (e.g., wireless transmission such as BLUETOOTH® or any other communication protocol described herein), pairing with the display device 20 (e.g., wireless transmission such as BLUETOOTH® or any other communication protocol described herein), stopping transmission for a communication protocol (e.g., wireless transmission such as BLUETOOTH® or any other communication protocol described herein), calibrating the sensor electronics unit 6 having the continuous analyte sensor 8, transmitting historical data, and / or any desired commands 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, beacon transmission, stealth mode, etc.), timing, etc. Conveniently, NFC can provide the user with a secure and intuitive way to transmit such commands and / or requests. NFC range limitations can reduce the risk of unauthorized display devices transmitting commands and / or requests to the sensor electronics unit 6. Furthermore, the physical action of bringing the display device 20 closer to the sensor electronics unit 6 can be intuitive for the user.

[0207] In some implementations, since wireless transmission can have a longer range and higher transmission speed, all data can be transmitted from the sensor electronic equipment unit 6 to the display device 20 using wireless transmission such as BLUETOOTH®. Furthermore, conveniently, wireless transmission communication can be generated autonomously by the display device 20, and can be used without the user actively positioning the display device 20 next to the sensor electronic equipment unit 6. In some cases, data can be transmitted in response to commands and / or requests sent via communication protocols using an RF field, such as NFC or RFID. In some implementations, certain types of data may be transmitted via an RF field rather than wireless transmission. For example, but not limited to, some data may require higher security considerations and may affect the functionality of the sensor electronic equipment unit 6 / continuous analyte sensor 8. It may be desirable to use a different protocol than wireless transmission to transmit such information. For example, but not limited to, the user can transmit calibration data from the display device 20 to the sensor electronic equipment unit 6. This calibration data may include data showing analyte measurements, such as blood glucose levels, taken from another source, such as a finger puncture. This data can be used to calibrate the indicated blood glucose level from the sensor electronics unit 6 / continuous analyte sensor 8. Such data can be transmitted via NFC to provide further security and / or to make the transfer more user-friendly. Transmission via NFC may also be particularly advantageous, as it can allow the user to adjust or update the calibration of the sensor electronics unit 6 on demand when it is convenient and / or desirable.

[0208] In some implementations, transmission can be divided into multiple communication protocols to further encrypt the message. For example, but not limited to, the display device 20 may transmit part of a command via a first communication protocol (e.g., wireless transmission such as BLUETOOTH®) and part of the command via a second communication protocol (e.g., RF field such as NFC or RFID). In an exemplary example, in a case where an RF field communication protocol and wireless transmission are used, the sensor electronic equipment unit 6 can receive part of a command via wireless transmission and perform the commanded action when it receives part of the command via the RF field communication protocol. Similarly, data transmitted from the sensor electronic equipment unit 6 can be divided into an RF field communication protocol and wireless transmission such that part of the data is transmitted via the RF field communication protocol and part of the data is transmitted via wireless transmission. In this way, the display device 20 receives all the data using both the RF field communication protocol and wireless transmission. In an indefinite example, encrypted information can be transmitted via an RF field communication protocol such as NFC or RFID, and then the encrypted data can be used to decrypt data transmitted via a wireless transmission protocol such as BLUETOOTH®.

[0209] In some implementations, the type of transmission transmitted and through which communication protocol may depend at least in part on the battery level and / or available power of the sensor electronic equipment unit 6. In some implementations, one use of the communication protocol can be used when the battery level of the sensor electronic equipment unit 6 is above a first predetermined threshold, while a second use of the communication protocol can be used when the battery level falls below a second predetermined threshold (which may be equal to or substantially equal to the first predetermined threshold, or may be different). As an illustrative example, but not limited to, the first predetermined threshold may be defined as a range in which the battery of the sensor electronic equipment unit 6 has a considerable remaining charge (e.g., the battery level may, as desired, exceed 30, 40, 50, 60, or more percent, or any predetermined percentage). When the battery level exceeds a first predetermined threshold, communication between the sensor electronic equipment unit 6 and the display device 20 can utilize wireless transmission such as BLUETOOTH®, and / or a combination of wireless transmission such as BLUETOOTH® and an RF field communication protocol such as NFC or RFID. However, when the battery level of the sensor electronic equipment 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 electronic equipment unit 6 and the display device 20 can use a communication protocol that utilizes less energy and / or conserves energy (e.g., an RF field communication protocol such as NFC or RFID). Conveniently, this can allow the battery power to be supplied in such a way that the user can perform only a certain number of actions per day through the communication protocol. For example, if the number of actions performed by the first communication protocol per day exceeds a certain number (e.g., one, five, ten, or any number of actions budgeted by the user, at least partially determined by energy consumption), the communication between the sensor electronics unit 6 and the display device 20 can 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 limited to five per day. Therefore, if a user exceeds five communications per day via wireless transmission, the user will then use an RF field communication protocol for subsequent communications.

[0210] In some implementations, transmission can be done through one communication protocol, but the transmission can be viewed using data / information through a second communication protocol. For example, but not limited to, data can be transmitted from the sensor electronic equipment unit 6 to the display device 20 using a wireless transmission protocol such as BLUETOOTH®. However, the data can be made invisible to the display device 20 until the sensor electronic equipment unit 6 transmits a decryption key to the display device 20 via an RF field communication protocol such as NFC or RFID.

[0211] As an illustrative example, but not limited to, the sensor electronics unit 6 may broadcast data, transmit beacons, and / or otherwise transmit data using one protocol. For example, it may transmit data to any device within its range via wireless transmission such as BLUETOOTH®. The user can then view the information using a second communication protocol, such as a communication protocol that uses an RF field, such as NFC or RFID. As an illustrative example, but not limited to, the sensor electronics unit 6 may broadcast user data via BLUETOOTH® to a BLUETOOTH®-enabled device within the BLUETOOTH® range of the sensor electronics unit 6. Such a BLUETOOTH®-enabled device can receive and store the data (for example, using a computer application). However, the data may be encrypted and / or made inaccessible on the BLUETOOTH®-enabled device until it receives an encryption key, command, and / or data that enables the BLUETOOTH®-enabled device to view the received data by communicating with the sensor electronics unit 6 and receiving an encryption key using NFC or RFID.

[0212] As another exemplary example, in some implementations, the sensor electronic equipment unit 6 can be in broadcast mode using a first communication protocol that uses wireless transmission such as BLUETOOTH®, where the wireless communication of the sensor electronic equipment unit 6 can only transmit data but cannot receive that data from the display device 20 (e.g., one-way data transmission). In this example, a second communication protocol that uses an RF field such as NFC or RFID can be used to send commands, such as a command to open bidirectional communication through the first communication protocol. Once bidirectional communication is opened through the first communication protocol, the display device 20 can send commands and / or information to the sensor electronic equipment unit 6. For example, but not limited to, the display device 20 can send calibration data and calibration commands to the sensor electronic equipment unit 6 through the first communication protocol. Once bidirectional communication is complete, the sensor electronic equipment unit 6 returns to broadcast mode. Conveniently, allowing the second communication protocol to open bidirectional communication while the sensor electronic equipment unit 6 is in broadcast mode allows the sensor electronic equipment unit 6 to maintain the efficiency of broadcasting via broadcast mode while still being able to receive information and / or commands from the display device 20 in a timely manner.

[0213] As another exemplary example, the sensor electronics unit 6 may use a wireless transmission broadcast, such as a BLUETOOTH® broadcast (e.g., beacon transmission and / or one-way communication), transmitted to the display device 20. This beacon can be transmitted exclusively to a specific device (e.g., in exclusive mode) and / or only at a specific time. This exclusivity can be achieved by encrypting the beacon and / or by broadcasting the beacon to a specific identified display device (e.g., identified through the manufacturer, model, IP address, etc., within the beacon). For example, but not limited to, a user may use different display devices at night than they do during the day. During the day, a user may start work at an office and have mobile devices that they use there. These mobile devices may differ from the display devices the user uses when at home. In some implementations, the beacon may broadcast to a first set of display devices during the day when the user is working, and to a second set of display devices at night when the user is away from work. In some cases, these wireless transmission broadcasts can be encrypted to secure any data, commands, information, status, etc., transmitted between sensor electronic devices and display devices, and vice versa. In some implementations, another communication protocol, such as NFC or RFID, can be used to transmit a decryption key to decrypt the encrypted data, commands, information, status, etc. If NFC is used, the display device that the user wishes to send / receive data, commands, information, status, etc., can be placed close to the sensor electronic device unit 6. The sensor electronic device unit 6 may already be transmitting beacons to the display device, or it may not have started transmitting beacons yet.The display device and the sensor electronic equipment unit 6 can exchange decryption keys (e.g., static keys and / or dynamic keys), and then use these decryption keys to decrypt transmissions (e.g., data, commands, information, status, communications, etc.) transmitted between the display device and the sensor electronic equipment unit 6.

[0214] In some cases, the sensor electronics unit 6 can transmit a beacon, which can transmit data and / or invite a device to its communication range and connect. In some implementations, the sensor electronics unit 6 can transmit a beacon using a first communication protocol, and the display device 20 can then connect to the sensor electronics unit 6 using a second communication protocol for communication using the first communication protocol. As an illustrative example, but not limited to, the sensor electronics unit 6 can transmit a beacon using wireless transmission such as BLUETOOTH®. The display device 20 can receive the beacon-transmitted message and prompt the display device 20 to pair with it. The display device 20 can then pair with the sensor electronic equipment unit 6 for communication via Bluetooth® using an RF field communication protocol such as NFC or RFID. Conveniently, such a pairing mechanism can simplify the pairing procedure, allowing the user to avoid multiple steps involved in Bluetooth® pairing. Furthermore, by utilizing the limited scope of NFC for pairing, additional security can be provided, preventing unauthorized connections.

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

[0216] As an exemplary example, the first communication protocol for communication between the sensor electronic equipment unit 6 and the display device 20 may be wireless transmission such as BLUETOOTH®. When desired by the user (for example, when the user of the sensor electronic equipment unit 6 and / or the display device 20 is concerned with connectivity issues), the connection (e.g., pairing) of the sensor electronic equipment 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 over a narrow range, NFC can be particularly useful when wireless transmission such as BLUETOOTH® is the first communication protocol and NFC is the second communication protocol. For example, the display device 20 can send a command to the sensor electronics unit 6 to disconnect. RF field communication protocols such as NFC or RFID can 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 lost data, an RF field communication protocol such as NFC or RFID can be used to transmit data from the sensor electronics unit 6 to the device 20, or vice versa. For example, but not limited to, a data packet received by either the sensor electronics unit 6 or the display device 20 via an RF field communication protocol can be compared with a data packet 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 lists of transmitted, received, and / or transmitted but not received data packets. A processor in either the sensor electronics unit 6 and / or the display device 20 may compare the transmitted list with the received list, or process the transmitted but not received list, to determine which data packets were transmitted but not received. Therefore, such transmitted but unreceived data packets can be transferred (for example, 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®). Exemplary Analytical Monitoring System

[0219] The following example of an analyte monitoring system is provided.

[0220] Analyte monitoring system 1: An analyte monitoring system comprising: a sensor configured to take measured values ​​indicating an analyte level; a sensor electronic equipment unit communicatively coupled to the sensor, which receives measured values ​​indicating an analyte level from the sensor, calculates an estimated analyte value, operates in normal power mode and low power mode, transmits data indicating an analyte level using a first communication protocol in normal power mode, and receives commands using a second communication protocol in low power mode; and a display device configured to transmit commands to the sensor electronic equipment unit using a second communication protocol and receive data indicating an analyte level from the sensor electronic equipment unit using a first communication protocol, wherein the sensor electronic equipment unit is configured to switch from low power mode to normal power mode in response to a command, and to wirelessly connect to the display device for communication using the first communication protocol.

[0221] Analyte monitoring system 2: An embodiment of the analyte monitoring system 1, wherein the low-power mode is shelf mode.

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

[0223] Analyte monitoring system 4: Analyte monitoring system comprising: a sensor configured to take measured values ​​indicating an analyte level; a sensor electronic equipment unit communicatively coupled to the sensor, which receives measured values ​​indicating an analyte level from the sensor, calculates an estimated analyte value, operates in normal power mode and low power mode, transmits data indicating an analyte level using a first communication protocol when in normal power mode, and receives commands using a second communication protocol when in normal power mode; and a display device configured to receive data indicating an analyte level from the sensor electronic equipment unit using the first communication protocol and transmit commands to the sensor electronic equipment unit using the second communication protocol, wherein the system is configured to cause the sensor electronic equipment unit to switch from normal power mode to low power mode in response to a command, and to wirelessly disconnect the display device from the sensor electronic equipment unit for communication via the first communication protocol.

[0224] Analyte monitoring system 5: An embodiment of the analyte monitoring system 4, wherein the low-power mode is 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: Analyte monitoring system comprising: a sensor configured to take a measurement value indicating an analyte level; a sensor electronic equipment unit communicatively coupled to the sensor, configured to receive a measurement value indicating an analyte level, process the received measurement value, and transmit data indicating an analyte level using a first communication protocol at a predetermined time; and a display device configured to receive data indicating an analyte level transmitted by the sensor electronic equipment unit using the first communication protocol, and to retrieve data indicating an analyte level from the sensor electronic equipment unit using a second communication protocol at least a predetermined time in advance.

[0227] Analyte monitoring system 8: One embodiment of the analyte monitoring system 7, wherein the processing of measurements received by the sensor electronic equipment unit includes calculating an estimated analyte level based at least in part on the measurements.

[0228] Analyte monitoring system 9: Analyte monitoring system comprising: a sensor configured to take measurements indicating an analyte level; a sensor electronic equipment unit communicatively coupled to the sensor, configured to receive measurements indicating an analyte level, process the received measurements, and transmit data indicating an analyte level using a first communication protocol at a predetermined time; and a display device configured to receive data indicating an analyte level transmitted by the sensor electronic equipment unit using the first communication protocol, transmit a command message via a second communication protocol to stop the sensor from taking measurements, and further transmit a request message via the second communication protocol to request the sensor electronic equipment unit to stop transmitting data indicating an analyte level using the first communication protocol.

[0229] Analyte monitoring system 10: One embodiment of the analyte monitoring system 9, wherein the processing of measurements received by a sensor electronic equipment unit includes calculating estimated analyte values ​​based at least in part on the measurements.

[0230] Analytical substance monitoring system 11: One embodiment of the analytical substance monitoring system 9 or 10, wherein a command message provides a sensor electronics unit with an instruction to stop the sensor from taking measurements.

[0231] Analyte monitoring system 12: An embodiment of the analyte monitoring system 9, 10, or 11, further configured to initiate measurement by a sensor using a second communication protocol and to initiate transmission of data indicating the analyte level using a first communication protocol.

[0232] Analyte monitoring system 13: Analyte monitoring system comprising: a sensor configured to take measured values ​​indicating an analyte level; a sensor electronic equipment unit communicatively coupled to the sensor, configured to receive measured values ​​indicating an analyte level from the sensor, calculate an estimated analyte value, transmit data indicating the analyte level using a first communication protocol, and receive commands using a second communication protocol; and a display device configured to receive data indicating the analyte level using a first communication protocol and transmit data request commands to the sensor electronic equipment unit using a second communication protocol, wherein the sensor electronic equipment unit transmits data indicating the analyte level using a first communication protocol in response to a data request command.

[0233] Analytical substance monitoring system 14: An embodiment of the analytical substance monitoring system 13, wherein the sensor electronic equipment unit is further configured to measure the remaining battery level of the sensor electronic equipment unit.

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

[0235] Analytical substance monitoring system 16: An embodiment of the analytical substance monitoring system 13, wherein the sensor electronic equipment unit is configured to selectively receive one or more commands through a second communication protocol and selectively transmit data through a first communication protocol.

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

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

[0238] Analyte monitoring system 19: An embodiment of the 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 electronic equipment unit using a radio frequency field, thereby providing power to the sensor electronic equipment unit and transmitting data indicating the analyte level via a second communication protocol.

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

[0240] An embodiment of the analyte monitoring system 13, wherein the analyte monitoring system 21: Sensor electronic equipment 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 indicating the analyte level transmitted using a first communication protocol in response to a data request command.

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

[0242] Analytical substance monitoring system 23: An embodiment of the analytical substance monitoring system 22, wherein the sensor electronic equipment unit is further configured to measure the remaining battery level of the sensor electronic equipment unit.

[0243] Analyte monitoring system 24: One embodiment of the analyte monitoring system 22 or 23, wherein the sensor electronics unit is further configured to cease transmitting data indicating the analyte level when the measured battery level 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 low power mode when the measured battery level falls below a predetermined low power mode threshold.

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

[0246] Analytical substance monitoring system 27: An embodiment of the analytical substance monitoring system 22, wherein the second communication protocol utilizes at least one of short-range wireless communication and radio frequency identification.

[0247] Analyte monitoring system 28: One embodiment of the analyte monitoring system 22, wherein the sensor electronic equipment unit is further configured to calculate an estimated analyte level based at least in part on the measured values.

[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 measured value.

[0249] Analytical substance monitoring system 30: An embodiment of the analytical substance monitoring system 22, wherein, after the device authentication procedure is completed, the display device is further configured to read calibration or manufacturing information from a passive tag incorporated into the sensor electronics unit.

[0250] Analytical substance monitoring system 31: An embodiment of the analytical substance monitoring system 30, wherein at least a portion of the information read from the passive tag is encrypted.

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

[0252] Each of the routines, processes, methods, and algorithms described in the previous section can be embodied in code modules executed by one or more computers, computer processors, or machines configured to execute computer instructions, and can be fully or partially automated by them. The code modules can be stored in any kind of non-temporary computer-readable medium or tangible computer storage device, such as hard drives, solid memory, optical discs, and / or similar. The systems and modules can also be transmitted as generated data signals on various computer-readable transmission media, including wireless and wired / cable media (e.g., as part of a carrier wave or other analog or digital propagation signal), 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 entirely implemented in application-specific circuits. The results and process steps of the disclosed processes can be stored permanently or otherwise non-temporarily in any kind.

[0253] As used herein, the term module or unit may describe a given functional unit that can be implemented according to one or more implementations of this application. As used herein, a module or unit may be implemented using any form of hardware, software, or a combination thereof. For example, one or more processors, controllers, ASICs, PLAs, PALs, CPLDs, FPGAs, logic components, software routines, or other mechanisms may be implemented to form a module or unit. Modules, units, circuits, processors, and others may be fixed to a printed circuit board (PCB) or similar and may take various forms. In implementations, the various modules described herein may be implemented as discrete modules, or the functions and features described may be shared partially or entirely among one or more modules. In other words, as will be apparent to those skilled in the art after reading this description, the various features and functions described herein can be implemented in any given application and may be implemented in one or more separate or shared modules in various combinations and permutations. Even if various feature or functional elements can be described or claimed individually as separate modules, a person skilled in the art will understand that these features and functionalities can be shared among one or more common software and hardware elements, and that such descriptions do not require or imply the use of separate hardware or software components to implement such features or functionalities.

[0254] The various features and processes described above can be used independently of each other or combined in various ways. All possible combinations and partial combinations are intended to be within the scope of this 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 appropriate sequences. For example, the tasks or events described may be performed in an order other than that specifically disclosed, or multiple tasks or events may be combined into a single block or state. Illustrative blocks or events may be performed serially, in parallel, or in any other manner. Tasks or events may be added to or removed from the illustrated embodiment disclosed. Illustrative systems and components described herein may be configured differently from those described. For example, elements may be added to, removed from, or rearranged compared to the illustrated embodiment disclosed.

[0255] In particular, the conditional language used herein, such as "can," "could," "might," "may," and similar expressions, is not intended to suggest that features, elements, and / or steps are required in any way to one or more realizations, or that one or more realizations necessarily contain a logic for determination, whether or not these features, elements, and / or steps are included in any particular realization or performed therewith, with or without input or instruction from the author. Terms such as "comprising," "including," and "having" are synonyms and are used in an open, inclusive manner, without excluding additional elements, features, actions, or operations. The term "or" is used in its inclusive sense (and not in its exclusive sense), for example, when used to connect a list of elements, so that "or" means one, some, or all of the elements in that list. Conjunctional language such as “at least one of X, Y, and Z” is generally used to indicate that an item, term, etc., can be any of X, Y, or Z, unless otherwise specifically indicated, and is understood in context. Therefore, such conjunctional language is generally not intended to suggest that a particular manifestation requires the presence of at least one of X, at least one of Y, or at least one of Z. “About” or “approximate” and similar terms are synonyms and are used to indicate that the value modified by the term has an understood range associated with the term, which can be ±20%, ±15%, ±10%, ±5%, or ±1%. The term “substantially” is used to indicate that a result (e.g., a measurement) is close to a target value, and “close” can mean, for example, that the result is within 80%, 90%, 95%, or 99% of the value.Furthermore, as used herein, “defined” may include “predefined” and / or otherwise predetermined values, conditions, thresholds, measurements, and the like.

[0256] While specific exemplary embodiments have been described, these embodiments are presented merely as examples and are not intended to limit the scope of the invention disclosed herein. Therefore, nothing in the above description is intended to suggest that any particular feature, characteristic, step, module, or block is necessary or essential. Indeed, the novel methods and systems described herein can be embodied in various other forms, and various omissions, substitutions, and modifications can be made in the forms 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 hosts 4. Analytical Substance Monitoring System 6. Sensor Electronics Unit 8 Continuous Analytical Sensor 12 Uplink signal 20a Display device 20b Display device 20c display device 20d display device 20e Display Device

Claims

1. Analytical substance monitoring system, A sensor configured to take a measurement indicating the level of the analyte, A sensor electronic device unit that is communicatively coupled to the aforementioned sensor, The sensor receives a measurement value indicating the level of the analyte, and calculates the estimated analyte value. It operates in normal power mode and low power mode. In the aforementioned normal power mode, data indicating the analyte level is transmitted using the first communication protocol, and, In the low-power mode, a sensor electronic device unit is configured to receive commands using a second communication protocol, A display device, The command is transmitted to the sensor electronic equipment unit using the second communication protocol described above. The system comprises a display device configured to receive data indicating the analyte level from the sensor electronic equipment unit using the first communication protocol, Analyte monitoring system, wherein the sensor electronic equipment 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 according to claim 1, wherein the low-power mode is a shelf mode.

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

4. Analytical substance monitoring system, A sensor configured to take a measurement indicating the level of the analyte, A sensor electronic device unit that is communicatively coupled to the aforementioned sensor, The sensor receives a measurement value indicating the level of the analyte, and calculates the estimated analyte value. It operates in normal power mode and low power mode. In the aforementioned normal power mode, data indicating the analyte level is transmitted using the first communication protocol, and, In the aforementioned normal power mode, a sensor electronic device unit is configured to receive commands using a second communication protocol, A display device, Using the first communication protocol described above, data indicating the analyte level is received from the sensor electronic equipment unit, and, The system comprises a display device configured to transmit commands to the sensor electronic equipment unit using the second communication protocol described above, Analytical substance monitoring system, wherein the system is configured to, in response to the command, cause the sensor electronic equipment unit to switch from the normal power mode to the low power mode, and to wirelessly disconnect the display device from the sensor electronic equipment unit for communication via the first communication protocol.

5. The analyte monitoring system according to claim 4, wherein the low-power mode is shelf mode.

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

7. Analytical substance monitoring system, A sensor configured to take a measurement indicating the level of the analyte, A sensor electronic device unit that is communicatively coupled to the aforementioned sensor, Upon receiving a measurement value indicating the analyte level, The received measurement values ​​are processed, and also A sensor electronics unit configured to transmit data indicating the analyte level using a first communication protocol at a predetermined time, A display device, Using the first communication protocol, the system receives data indicating the analyte level transmitted by the sensor electronic equipment unit, and also, Analyte monitoring system comprising: a display device configured to retrieve data indicating the analyte level from the sensor electronic equipment unit using a second communication protocol at least before the predetermined time.

8. The analyte monitoring system according to claim 7, wherein the processing of the received measurement values ​​by the sensor electronic equipment unit includes calculating an estimated analyte level based at least in part on the measurement values.

9. Analytical substance monitoring system, A sensor configured to take a measurement indicating the level of the analyte, A sensor electronic device unit that is communicatively coupled to the aforementioned sensor, Upon receiving a measurement value indicating the analyte level, The received measurement values ​​are processed, and also A sensor electronics unit configured to transmit data indicating the analyte level using a first communication protocol at a predetermined time, A display device, Using the first communication protocol, receive data indicating the analyte level transmitted by the sensor electronic equipment unit. A command message is transmitted via a second communication protocol to stop the sensor from taking measurements, and also, Analyte monitoring system comprising: a display device configured to further transmit a request message via the second communication protocol to the sensor electronic equipment unit requesting it to stop transmitting the data indicating the analyte level using the first communication protocol.

10. The analyte monitoring system according to claim 9, wherein the processing of the received measurement values ​​by the sensor electronic equipment unit includes calculating estimated analyte values ​​based at least in part on the measurement values.

11. The analyzer monitoring system according to claim 9 or 10, wherein the command message provides the sensor electronic device unit with a command to stop the sensor from taking measurement values.

12. The analyte monitoring system according to any one of claims 9 to 11, wherein the display device is further configured to initiate the acquisition of the measurement value by the sensor using the second communication protocol and to initiate the transmission of data indicating the analyte level using the first communication protocol.

13. Analytical substance monitoring system, A sensor configured to take a measurement indicating the level of the analyte, A sensor electronic device unit that is communicatively coupled to the aforementioned sensor, The sensor receives a measurement value indicating the level of the analyte, and calculates the estimated analyte value. The first communication protocol is used to transmit data indicating the analyte level, and also, A sensor electronics unit configured to receive commands using a second communication protocol, A display device, Using the first communication protocol described above, data indicating the analyte level is received, and, Analyte monitoring system comprising: a display device configured to transmit data request commands to the sensor electronic equipment unit using the second communication protocol, wherein the sensor electronic equipment unit transmits data indicating the analyte level using the first communication protocol in response to the data request commands.

14. The analyte monitoring system according to claim 13, wherein the sensor electronic equipment unit is further configured to measure the remaining battery level of the sensor electronic equipment unit.

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

16. The analyte monitoring system according to claim 13, wherein the sensor electronic equipment unit is configured to selectively receive one or more commands through the second communication protocol and selectively transmit data through the first communication protocol.

17. The analyte monitoring system according to claim 13, wherein the sensor electronic equipment unit is further configured to transmit data indicating the analyte level at predetermined time intervals.

18. The analyte monitoring system according to claim 17, wherein transmitting data indicating the analyte level using the first communication protocol in response to the data request command does not prevent the sensor electronic equipment unit from transmitting data indicating the analyte level at predetermined time intervals.

19. The analyte monitoring system according to any one of claims 13 to 15, wherein when the battery level falls below a predetermined threshold, the display device transmits power to the sensor electronic equipment unit using a radio frequency field, thereby providing power to the sensor electronic equipment unit and transmitting data indicating the analyte level through the second communication protocol.

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

21. The analyte monitoring system according to claim 13, wherein the sensor electronic equipment unit further transmits a decryption key using the second communication protocol in response to the data request command, and the decryption key is used to decrypt the data indicating the analyte level transmitted using the first communication protocol in response to the data request command.

22. Analytical substance monitoring system, A sensor configured to take a measurement indicating the level of the analyte, A sensor electronic device unit that is communicatively coupled to the aforementioned sensor, The sensor receives a measurement value indicating the level of the analyte, and calculates the estimated analyte value. The estimated data indicating the analyte level is transmitted using the first communication protocol, and, A sensor electronics unit configured to receive commands using a second communication protocol, A display device, Using the first communication protocol described above, data indicating the analyte level is received, and, Analyte monitoring system comprising: a display device configured to transmit data request commands to the sensor electronic equipment unit using the second communication protocol, wherein the sensor electronic equipment unit transmits a portion of data indicating the analyte level using the first communication protocol, and transmits another portion of data indicating the analyte level using the second communication protocol in response to the data request command.

23. The analyte monitoring system according to claim 22, wherein the sensor electronic equipment unit is further configured to measure the remaining battery level of the sensor electronic equipment unit.

24. The analyte monitoring system according to claim 22 or 23, wherein the sensor electronic equipment unit is further configured to cease transmitting data indicating the analyte level when the measured battery level falls below a predetermined threshold.

25. The analyte monitoring system according to claim 23, wherein the sensor electronic equipment unit is further configured to utilize the low power mode when the measured battery level falls below a predetermined low power mode threshold.

26. The analyte monitoring system according to any one of claims 23 to 25, wherein the sensor electronic equipment unit is further configured to utilize the normal power mode when the measured battery level exceeds a predetermined normal power mode threshold.

27. The analytical material monitoring system according to claim 22, wherein the second communication protocol utilizes at least one of short-range wireless communication and radio frequency identification.

28. The analyte monitoring system according to claim 22, wherein the sensor electronic equipment unit is further configured to calculate an estimated analyte level based at least in part on the measured values.

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

30. The analyte monitoring system according to claim 22, wherein, after the device authentication procedure is completed, the display device is further configured to read calibration or manufacturing information from a passive tag incorporated in the sensor electronic equipment unit.

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

Images