System and apparatus for receiving data and method for controlling the same

By using technologies such as microprocessors and communication integrated circuits in in vivo analyte monitoring systems, the convenience and cost problems in the existing technology are solved, the glucose monitoring frequency and accuracy of diabetic patients are improved, and the power efficiency of the equipment is enhanced. User experience.

CN118973469APending Publication Date: 2024-11-15ABBOTT DIABETES CARE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380032578.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-06
Filing Date
2023-04-06
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

The existing in vivo analyte monitoring system has shortcomings in terms of convenience, testing judgment and cost, resulting in infrequent monitoring of glucose levels in patients with diabetes, affecting health management.

Method used

Designed an analyte monitoring device including a microprocessor, communication integrated circuit, analog front-end and IO extender, which can detect attachment devices through a USB module, provide tactile and auditory feedback, and includes a temperature sensor and a display, supporting low power Mode to improve battery life.

Benefits of technology

It improves the convenience and accuracy of analyte monitoring, enhances the power efficiency of the equipment and hardware and software flexibility, reduces the possibility of discomfortability and errors, and improves the patient's health management capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118973469A_ABST
    Figure CN118973469A_ABST
Patent Text Reader

Abstract

Embodiments described herein include an analyte monitoring device for receiving data in an analyte monitoring system. An analyte monitoring device includes a microprocessor, one or more communication integrated circuits electrically coupled to the microprocessor, where the one or more communication integrated circuits are further electrically coupled to at least one respective antenna, an input / output (IO) extender electrically coupled to the microprocessor, and one or more storage memories including instructions, when operable by the microprocessor, the instructions cause the microprocessor to receive analyte data from a sensor control of an analyte sensor in the analyte monitoring system. The IO expander increases the number of pins of the microprocessor.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] priority

[0002] This application claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Patent Application No. 63 / 328,037, filed on April 6, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The subject matter described herein relates to systems and devices for receiving data, and methods of controlling systems and devices for receiving data, for example, regarding the operation of a handheld device that forms part of an in vivo analyte monitoring system. Background Art

[0004] Frequent monitoring and management of analyte levels (such as glucose, ketones, lactate, oxygen, hemoglobin A1C, etc.) can improve the overall health of people and, in particular, people with diabetes. Diabetic patients may experience complications, including loss of consciousness, cardiovascular disease, retinopathy, neuropathy, and nephropathy. Diabetic patients are generally required to monitor their glucose levels to ensure that the glucose levels are maintained within a clinically safe range, and this information can also be used to determine whether and / or when insulin is needed to lower the glucose level in their body, or when additional glucose is needed to increase the glucose level in their body.

[0005] Clinical data demonstrate a strong correlation between frequency of glucose monitoring and glycemic control. Despite this correlation, however, many individuals diagnosed with a diabetic condition do not monitor their glucose levels as frequently as they should due to a combination of factors including convenience, testing discretion, pain associated with glucose testing, and cost.

[0006] In order to improve the patient's compliance with the plan of frequent glucose monitoring, an in vivo analyte monitoring system can be utilized, wherein the sensor control device can be worn on the body of the individual requiring analyte monitoring. In order to improve the comfort and convenience to the individual, the sensor control device can have a small form factor, and can be assembled and applied by the individual using a sensor applicator. The application process includes inserting a sensor using an applicator or an insertion mechanism, such as an in vivo sensor that senses the user's analyte level in the body fluid in the skin layer of the human body, so that the sensor is in contact with the body fluid. The sensor control device can also be configured to transmit data to one or more data receiving devices, and the individual, her health care provider ("HCP"), or other people can view data from the one or more data receiving devices and make treatment decisions. During the life cycle of the sensor, background information that helps to improve performance can be generated.

[0007] Based on the way that data is communicated between the reader device and the sensor control device, in vivo analyte monitoring systems can be widely classified. One type of in vivo system is a "continuous analyte monitoring" system (or "continuous glucose monitoring" system), in which data can be broadcasted from the sensor control device to the data receiving device continuously and without prompting, for example, in an automatic manner according to a broadcast schedule. Another type of in vivo system is a "flash analyte monitoring" system (or "flash glucose monitoring" system or simply "flash" system), in which data can be transferred from the sensor control device in response to a scan or request of data by the data receiving device, such as using near field communication (NFC) or radio frequency identification (RFID) protocols. The data receiving device may include various hardware components to enable processing of data received from the sensor control device, and must include telecommunication components to enable communication with the sensor control device. The data receiving device may further include additional testing or sending hardware to assist individuals in making treatment decisions.

[0008]

[0006] Therefore, a need exists for improved analyte monitoring devices and associated data receiving devices having greater power efficiency, more performance control, and greater hardware and software flexibility for use in new analyte monitoring applications. Summary of the invention

[0009] The purposes and advantages of the subject matter of the present disclosure will be set forth in and apparent from the following description, and will be learned by practicing the subject matter of the present disclosure. Other advantages of the subject matter of the present disclosure will be realized and obtained by the methods and systems particularly pointed out in the written description and claims thereof as well as the drawings.

[0010] To achieve these and other advantages and in accordance with the purpose of the subject matter of the present disclosure, as embodied and widely described, the subject matter of the present disclosure includes a system and device for receiving and processing data in an analyte monitoring system, and a control method of the system and device. An exemplary system and method may include an analyte monitoring device for receiving data in an analyte monitoring system, including a microprocessor, one or more communication integrated circuits electrically coupled to the microprocessor, an analog front end electrically coupled to the microprocessor and optionally coupled to a test strip port, an input output (IO) expander electrically coupled to the microprocessor, and one or more storage memories including instructions, when being operable by the microprocessor, the instructions enable the microprocessor to control the device analyte data from the sensor of the analyte sensor in the receiving analyte monitoring system. One or more communication integrated circuits are further electrically coupled to at least one corresponding antenna. In some instances, the analyte monitoring device may be optionally configured to perform an assay to determine the presence or level of an analyte in a sample presented to the test strip port. The IO expander is configured to increase the number of pins available to the microprocessor for input and output. In some embodiments, the analog front end includes four external operational amplifiers and uses an external VREF. In some embodiments, the IO expander is electrically coupled to a motor for providing tactile feedback, electrically coupled to a buzzer for providing audible feedback, or electrically coupled to a battery monitoring integrated circuit.

[0011] The microprocessor may include an integrated universal serial bus (USB) module. The instruction further causes the microprocessor to detect the attachment of a USB device through the USB port of the analyte monitoring device and determine the host type of the USB device, wherein the host type includes a powered or unpowered USB host. In some embodiments, the microprocessor determines the host type of the USB device through the attachment detection protocol module and the battery charging detector module of the analyte monitoring device. In some embodiments, the instruction causes the microprocessor to detect the attachment of the USB device, further causing the microprocessor to measure the ramp time from the sink voltage of the attachment detection protocol to the probe voltage of the attachment detection protocol, and compares the ramp time to at least a first threshold and a second threshold, wherein the second threshold is greater than the first threshold; and determining a ramp time below the first threshold or above the second threshold. In some embodiments, the analyte monitoring device may include a VBUS protection circuit electrically coupled to the microprocessor. In some embodiments, when the host type of the USB device is a powered host, the microprocessor prevents the use of the analog front end from performing the determination until the USB device is detached.

[0012] In some embodiments, the analyte sensor is configured to detect an analyte level in a bodily fluid of a user, wherein a portion of the analyte sensor is configured to be transcutaneously positioned in the user such that when operably positioned, a portion of the analyte sensor is configured to reside above the surface of the user's skin and an in vivo portion of the analyte sensor is configured to reside below the surface of the skin and in contact with the user's bodily fluid. In some embodiments, the analyte comprises glucose, ketones, lactate, oxygen, hemoglobin A1C, albumin, alcohol, alkaline phosphatase, alanine aminotransferase, aspartate aminotransferase, bilirubin, blood urea nitrogen, calcium, carbon dioxide, chloride, creatinine, hematocrit, lactate, magnesium, oxygen, pH, phosphorus, potassium, sodium, total protein, or uric acid.

[0013] In some embodiments, the analyte monitoring device further comprises a display for outputting at least processed analyte data from the sensor control device. The display comprises a touch screen circuit for detecting user input by direct interaction with the display using charge transfer detection between an input node of the touch screen circuit and a sampling capacitor of the touch screen circuit.

[0014] In some embodiments, the analyte monitoring device further comprises a temperature sensor. The temperature sensor may comprise a thermistor having a resistance that varies with temperature, and the temperature from the sensor may be determined by querying a lookup table that maps the resistance of the thermistor to the detected temperature.

[0015] In some embodiments, the microprocessor further includes a hardware-based random number generator. The instructions may further cause the microprocessor to seed the pseudo-random number generator using a random number from the hardware-based random number generator.

[0016] According to other aspects of the subject matter of the present disclosure, systems and methods may include a method performed by a microprocessor of an analyte monitoring device in an analyte monitoring system. The method includes, before switching to a low power mode, enabling write protection of at least one memory location in a flash memory electrically coupled to the microprocessor. At least one memory location is associated with a state of one or more status registers in the flash memory. The method includes switching, by the microprocessor, to operate in a low power mode. The method includes, after waking up from a low power mode, disabling write protection of at least one memory location, wherein the write protection of at least one memory location is enabled before switching to the low power mode to prevent the value stored in the at least one memory location from being unintentionally modified by a process operated when the microprocessor is operating in the low power mode. In some embodiments, the state corresponds to a clock safety state. In some embodiments, the state corresponds to the detection of a sequence execution error.

[0017] Other systems, methods, features, and advantages of the subject matter described herein will be or will become apparent to one skilled in the art upon examination of the following drawings and detailed description. All such additional systems, methods, features, and advantages are intended to be included within this specification, to be within the scope of the subject matter described herein, and to be protected by the appended claims. In any event, features of the exemplary embodiments should not be construed as limiting the appended claims, to the extent those features are not explicitly recited in the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The details of the structure and operation of the subject matter set forth herein may be apparent by studying the accompanying drawings, in which like reference numerals represent like components. The components in the drawings are not necessarily drawn to scale, with emphasis placed on illustrating the principles of the subject matter. In addition, all illustrations are intended to convey concepts, in which relative sizes, shapes, and other detailed attributes may be shown schematically rather than literally or precisely.

[0019] Figure 1 is a high-level diagram describing an example embodiment of an analyte monitoring system for real-time analyte (eg, glucose) measurement, data acquisition, and / or processing.

[0020] Figure 2 is a block diagram depicting an example sensor control device.

[0021] Figure 3 is a block diagram illustrating an exemplary embodiment of a data receiving device.

[0022] Figure 4 is a schematic diagram of an input / output (IO) expander used in accordance with an embodiment of the present disclosure.

[0023] Figure 5 is a schematic diagram of a touch screen circuit used according to an embodiment of the present disclosure.

[0024] Figure 6 is a diagram illustrating allocation and numbering of touch areas according to an embodiment of the present disclosure.

[0025] Figure 7 is a schematic diagram showing the connection of a touch screen to a microprocessor according to an embodiment of the present disclosure.

[0026] Figure 8 is a schematic diagram of a VBUS protection circuit according to an embodiment of the present disclosure.

[0027] FIG. 9A to FIG. 9B is a schematic diagram of an analog front-end circuit according to an embodiment of the present disclosure.

[0028] Fig.10 is a schematic diagram of a temperature sensor according to an embodiment of the present disclosure.

[0029] Fig.11 A method 1100 for preventing errors caused by waking up a microprocessor is shown. DETAILED DESCRIPTION

[0030] Reference will now be made in detail to various example embodiments of the presently disclosed subject matter, example embodiments of which are illustrated in the accompanying drawings.

[0031] Before describing the present subject matter in detail, it should be understood that the present disclosure is not limited to the particular embodiments described, as these may of course vary. It should also be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting, as the scope of the present disclosure will be limited only by the appended claims.

[0032] As used herein and in the appended claims, the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise.

[0033] In general, embodiments of the present disclosure include systems, devices and methods for using an analyte sensor insertion applicator used with an in vivo analyte monitoring system. The applicator can be provided to the user in a sterile package, in which the electronic housing of the sensor control device is contained. According to some embodiments, a structure separated from the applicator, such as a container, can also be provided to the user as a sterile package containing a sensor module and a tip module. The user can couple the sensor module to the electronic housing, and the tip can be coupled to the applicator by an assembly process (involving inserting the applicator into the container in a particular manner). In other embodiments, the applicator, the sensor control device, the sensor module, and the tip module can be provided in a single package. The applicator can be used to position the sensor control device on the human body, wherein the sensor contacts the body fluids of the wearer. The embodiments provided herein are improvements that reduce the possibility of improper insertion or damage of the sensor or causing adverse physiological reactions. Other improvements and advantages are also provided. The various configurations of these devices are described in detail by way of embodiments that are only examples.

[0034] In addition, many embodiments include an in vivo analyte sensor that is structurally configured such that at least a portion of the sensor is or can be located in the body of a user to obtain information about at least one analyte of the body. However, it should be noted that embodiments of the present disclosure can be used with in vivo analyte monitoring systems that incorporate in vivo capabilities as well as purely in vivo or purely in vitro analyte monitoring systems (including completely non-invasive systems).

[0035] In addition, for each and every embodiment of the disclosed method, systems and devices capable of executing each of those embodiments are included within the scope of the present disclosure. For example, embodiments of sensor control devices are disclosed, and these devices may have one or more sensors, analyte monitoring circuits (e.g., analog circuits), memories (e.g., for storing instructions), power supplies, communication circuits, transmitters, receivers, processors, and / or controllers (e.g., for executing instructions), which may perform any and all method steps or facilitate the execution of any and all method steps. These sensor control device embodiments can be used and can be used to implement those steps performed by the sensor control device in any and all methods described herein.

[0036] In addition, the systems and methods presented herein can be used for the operation of sensors used in analyte monitoring systems, such as, but not limited to, health, fitness, diet, research, information, or any purpose involving analyte sensing over time. As used herein, "sensor" can refer to any device capable of receiving sensor information from a user, including, for example and not limitation, a temperature sensor, a blood pressure sensor, a pulse or heart rate sensor, a glucose level sensor, an analyte sensor, a physical activity sensor, a body movement sensor, or any other sensor for collecting physical or biological information. The analyte measured by the analyte sensor can include, by way of example and not limitation, glucose, ketones, lactate, oxygen, hemoglobin A1C, albumin, alcohol, alkaline phosphatase, alanine aminotransferase, aspartate aminotransferase, bilirubin, blood urea nitrogen, calcium, carbon dioxide, chloride, creatinine, hematocrit, lactate, magnesium, oxygen, pH, phosphorus, potassium, sodium, total protein, uric acid, etc.

[0037] However, before describing these aspects of the embodiments in detail, it is first desirable to describe examples of devices that may be present, for example, within an in vivo analyte monitoring system, and examples of their operation, all of which may be used with the embodiments described herein.

[0038] There are different types of in vivo analyte monitoring systems. For example, a "continuous analyte monitoring" system (or "continuous glucose monitoring" system) can continuously and unpromptedly transmit data from a sensor control device to a reader device, for example, in an automatic manner according to a broadcast schedule. As another example, a "flash analyte monitoring" system (or "flash glucose monitoring" system or simply a "flash" system) can transfer data from a sensor control device in response to a scan or request for data by a reader device, such as using near field communication (NFC) or radio frequency identification (RFID) protocols. In vivo analyte monitoring systems can also operate without the need for finger prick calibration.

[0039] In vivo analyte monitoring systems can be distinguished from "ex vivo" systems that contact a biological sample outside the body (or "in vitro") and can include a metering device having a port for receiving an analyte test strip carrying a user's bodily fluid, which can be analyzed to determine the user's blood glucose level.

[0040] The in-vivo monitoring system may include a sensor that, when positioned in-vivo, contacts a user's bodily fluids and senses the level of an analyte contained therein. The sensor may be part of a sensor control device that resides on the user's body and contains electronics and a power source that enable and control analyte sensing. The sensor control device and variations thereof may also be referred to as a "sensor control unit," "on-body electronics" device or unit, "on-body" device or unit, or "sensor data communication" device or unit, to name a few.

[0041] The in vivo monitoring system may also include a device that receives the sensed analyte data from the sensor control device and processes and / or displays the sensed analyte data to the user in any number of forms. This device and variations thereof may be referred to as a "data receiving device," "handheld reader device," "reader device" (or simply "reader" or "handheld"), a "portable data processing" device or unit, a "data receiver," a "receiver" device or unit, and other names. Other devices such as personal computers have also been used or incorporated with in vivo and ex vivo monitoring systems.

[0042] Figure 1 An exemplary embodiment of the operating environment of the analyte monitoring system 100 capable of implementing the technology described herein is shown. As shown, the analyte monitoring system 100 may include a component system, which is designed to provide monitoring of parameters (such as analyte levels) of a human or animal body, or other operations may be provided based on the configuration of various components. As embodied herein, the system may include a low-power sensor control device 102, which is worn by a user or attached to the body from which information is collected. As embodied herein, the sensor control device 102 may be a sealed disposable device with a predetermined effective service life (e.g., 1 day, 14 days, 30 days, etc.). The sensor control device 102 may be applied to the skin of the user's body and remain adhered within the time period of the sensor life, or may be designed to be selectively removed and remain functional when reapplied. The low power analyte monitoring system 100 may further include a data reader 120 or a multi-purpose data receiving device 130 configured as described herein to facilitate retrieval and delivery of data (including analyte data) from the sensor control device 102 .

[0043] As embodied herein, the analyte monitoring system 100 may include a software or firmware library or application program, which is provided to a third party, for example, via a remote application server 155 and is combined with a multi-purpose hardware device 130 (such as a mobile phone, a tablet computer, a personal computing device, or other similar computing devices capable of communicating with the sensor control device 102 via a communication link). The multi-purpose hardware may further include an embedded device, including but not limited to an insulin pump or an insulin pen, having an embedded library configured to communicate with the sensor control device 102. Although the illustrated embodiment of the analyte monitoring system 100 includes only one of each illustrated device, the present disclosure contemplates that the analyte monitoring system 100 is combined with each component that interacts with multiple systems. For example, but not limited to, as embodied herein, the data receiving device 120 and / or the multi-purpose data receiving device 130 may include each component that interacts with multiple systems. As embodied herein, multiple data receiving devices 130 may communicate directly with the sensor control device 102 as described herein. Additionally or alternatively, the data receiving device 130 may communicate with an auxiliary data receiving device 130 to provide analyte data, or a visualization or analysis of the data, for auxiliary display to a user or other authorized party.

[0044] For purposes of illustration and not limitation, Figure 2 An example embodiment of a sensor control device 102 that is compatible with the security architecture and communication schemes described herein is depicted.

[0045] As embodied herein, the sensor control device 102 may include an application specific integrated circuit ("ASIC") 200 communicatively coupled to the communication module 240. The ASIC 200 may include a microcontroller core 210, an onboard memory 220, and a storage memory 230. The storage memory 230 may store data used in an authentication and encryption security architecture. The storage memory 230 may store program instructions for the sensor control device 102. As embodied herein, certain communication chipsets may be embedded in the ASIC 200 (e.g., the NFC transceiver 225). The ASIC 200 may receive power from a power module 250 (such as an onboard battery) or from an NFC pulse. The storage memory 230 of the ASIC 200 may be programmed to include information such as an identifier of the sensor control device 102 for identification and tracking purposes. The storage memory 230 may also be programmed with configuration or calibration parameters for use by the sensor control device 102 and its various components. The storage memory 230 may include a rewritable or one-time programmable (OTP) memory. The storage memory 230 may be updated using the techniques described herein to expand the usefulness of the sensor control device 102 .

[0046] As embodied herein, the communication module 240 of the sensor control device 102 can be or include one or more modules to support communication with other devices of the analyte monitoring system 100. By way of example only and not limitation, the exemplary communication module 240 may include a Bluetooth low energy ("BLE") module 241. As used throughout this disclosure, "BLE" refers to a short-range communication protocol optimized to make pairing of Bluetooth devices simple for end users. The communication module 240 can transmit and receive data and commands via interaction with a communication module of similar capabilities of the data receiving device 120 or the user device 145. The communication module 240 may include additional or alternative chipsets for use with similar short-range communication schemes, such as personal area networks according to the IEEE 802.15 protocol, the IEEE 802.11 protocol, infrared communications according to the Infrared Data Association standard (IrDA), etc.

[0047] To perform its functions, the sensor control device 102 may further include appropriate sensing hardware 260 suitable for its functions. As embodied herein, the sensing hardware 260 may include an analyte sensor positioned transcutaneously or subcutaneously in contact with a bodily fluid of a subject. The analyte sensor may generate sensor data including values ​​corresponding to the level of one or more analytes within the bodily fluid.

[0048] For purposes of illustration and not limitation, reference is made to Figure 3 1 and 12. An exemplary embodiment of a data receiving device 120 for use with the disclosed subject matter is shown. The data receiving device 120 and the related multi-purpose data receiving device 130 include components closely related to the discussion of the sensor control device 102 and its operation, and may include additional components. In certain embodiments, the data receiving device 120 and the multi-purpose data receiving device 130 may be or include components provided by a third party, and are not necessarily limited to including devices manufactured by the same manufacturer as the sensor control device 102.

[0049] like Figure 3As shown, the data receiving device 120 includes a microprocessor 310, an integrated SRAM 311 and a flash memory 312, several oscillators (including a 32.768kHz low-speed external crystal oscillator (LSE) 313 and a 48MHz multi-speed internal RC oscillator (MSI) 314), and several controllers and buses for receiving and providing inputs and outputs. The SRAM 311 can include any appropriate size of SRAM for the operation of the microprocessor, and as an example only, the SRAM 311 can include 320K bytes of accessible memory. Similarly, the internal flash memory 312 can include any appropriate size of memory to enable the operation of the microprocessor, such as the storage of executable code and variables, and as an example only, it can include 1M bytes of accessible memory. In some embodiments, the microprocessor 310 can be programmed through a serial wired connection consisting of clock, data, reset, and ground. The connection also allows an interface to a real-time debugger or flash programmer for software development. The microprocessor 310 includes various reference oscillators that can work with an external crystal to generate a source, as an example, a source for a reference block used as a real-time counter. The real-time counter can be output to different components of the data receiving device 120 and for debugging purposes, using hardware and pin configuration. The microprocessor includes a USB controller 315 and an analog-to-digital converter (ADC) 316. An SPI module 317, a parallel bus 318, an I2C interface 319, and a universal asynchronous receiver-transmitter (UART) module 320. As described herein, the integrated touch controller 321 and DAC output 322 further relate to aspects of interaction with the touch screen display 330.

[0050] The data receiving device 120 includes an integrated haptic motor 333 and a buzzer 335 for providing notifications to the user. The haptic motor 333 provides tactile feedback from the data receiving device 120 to the user. The tactile feedback can be applied together with a counterweight vibration motor mounted to the PCB of the data receiving device 120. The haptic motor 333 is excited by applying a voltage across the motor terminals from the battery 341. The buzzer 335 provides audible feedback to the user. The buzzer includes an annunciator in combination with a piezoelectric disk. As an example, the annunciator can have a dual volume and can generate a tone at a frequency between 50Hz and 200Hz. The maximum volume can be generated by causing the annunciator to generate a tone of the resonant frequency of the buzzer 335 and the cavity in which it is located. At other frequencies, the lower volume can be smaller. In a specific embodiment, the microprocessor 310 can use one of its available timers to generate a 50% duty cycle pulse width modulation (PWM) at a desired frequency.

[0051] The data receiving device 120 includes a power button 353, which enables the user to manually activate or deactivate the data receiving device 120. The microprocessor 310 may include several power modes, including running, sleeping, and stopping. When the user interacts with the data receiving device 120, the microprocessor 310 alternates between a running mode (to complete a specific task) and a sleep mode (once a specific task is completed). When the data receiving device 120 reader is turned off by the user or turned off due to user inactivity, the microprocessor 310 enters a low power state (stop) that can be exited via an interrupt. From the user's perspective, the data receiving device 120 is in this mode when it is turned off, and the real-time clock is maintained only while waiting for an interrupt to wake up. The interrupt that causes the data receiving device 120 to wake up can be issued due to the following events: test strip insertion (when the test strip port is available in an optional embodiment), power button 353 pressing, USB insertion, or battery low alarm. The external wake-up input pin can detect a rising edge or a falling edge. Any pin can be configured to wake up the microprocessor 310 from all low power modes.

[0052] In certain embodiments, certain conditions may cause status bits associated with the operation of certain hardware components to be inaccurately reported. As an example, a status bit associated with a low-speed oscillator (e.g., LSE 313) and stored in a reset and clock control register may be incorrectly altered or reported. Specifically, it has been determined that the status bit may be improperly set, and the low-speed oscillator is then never ready, preventing operation. The condition causing the error may include waking up the microprocessor 310 from certain low-power modes or accessing registers to stop associated timers. In some cases, hardware associated with a timer register may change an otherwise unrelated internal flash status register when accessing a register (e.g., stopping a timer). For example, a bit associated with detecting or reporting a flash programming sequence error may be incorrectly set, causing subsequent operations to fail. In some cases, the status bit may be, for example, a clock security status bit, meaning that a damaged or incorrect value may cause a large number of errors involving security issues, even if the clock security module was previously disabled.

[0053] To prevent this error from occurring or affecting further operation of the microprocessor, the memory location associated with the bit that was unintentionally changed (e.g., the battery backup RTC field) can be temporarily set to a read-only state before entering a low power state. This can prevent the bit and the rest of the field from being corrupted when entering or exiting a low power mode. Additionally or alternatively, changes to state bits of an expected nature (e.g., setting a flash programming sequence error bit when stopping a particular timer) can be left out and handled as known errors due to the repeatability of the error.

[0054] Fig.11A process for preventing or circumventing errors caused by certain known hardware errors is shown in FIG. Fig.11 A method 1100 for preventing errors caused by waking up a microprocessor is shown. At step 1110, write protection of at least one memory location in a flash memory 312 electrically coupled to the microprocessor 310 is enabled before the microprocessor 310 is transitioned to a low power mode. The microprocessor 310 itself may enable write protection, or may include other memory controllers. As an example, at least one memory location may be associated with a state of one or more status registers in the flash memory 312. The state may relate to the safety of one or more clocks within or used by the microprocessor 310. The state may relate to the detection of execution errors in or associated with the flash memory 312, including but not limited to sequence execution errors.

[0055] At step 1120, the microprocessor 310 is converted to operate in a low power mode. At step 1130, the microprocessor 310 is awakened from the low power mode. As described herein, the microprocessor 310 can be awakened by an interrupt issued by or associated with one or more hardware components of the data receiving device 120. Example hardware capable of issuing an interrupt includes a power button 353 or a touch screen overlay 351 when receiving direct user input, a BLE co-processor 365 or RFID IC 360 when detecting a communication attempt from another device, an ADC 316 when receiving a signal such as from an optional AFE 347, an integrated USB module 315, or any other suitable component.

[0056] At step 1140, after waking up from the low power mode, write protection of at least one memory location is disabled. As described herein, enabling write protection of at least one memory location prior to transitioning to the low power mode prevents a value stored at the at least one memory location from being inadvertently modified by a process operating while the microprocessor is operating in the low power mode. Disabling write protection when the microprocessor 310 wakes up from the low power mode allows standard operation to continue.

[0057] To increase the number of input / output pins available to the microprocessor 310, the data receiving device 120 includes an input / output (IO) expander 337 as described herein. The IO expander 337 is communicatively coupled to the microprocessor 310 via the I2C interface 319.

[0058] The inclusion of IO expander 337 can increase the reliance on the stable operation of I2C interface 319, especially when adding additional peripheral components. In some cases, it has been determined that if there is contention during the use of the I2C bus (for example, when several peripheral devices attempt to read or write on the I2C bus), the transmission function on the I2C bus can be suspended. This causes the microprocessor 310 to be unable to communicate with the peripheral device. In order to alleviate this behavior, the microprocessor 310 can be configured to take preventive or corrective actions. As an example, the microprocessor 310 can be configured to detect the failure of communication via the I2C interface 319. Check the associated serial data line, and if it is low, the microprocessor 310 can be configured to change the configuration of the I2C serial clock output to switch the serial clock for a predetermined number of times. Because the "low" state of the serial data line is an incorrect state of the idle I2C bus, the serial clock is switched, and the serial data line is cleared and reset. The microprocessor 310 can then check the state of the serial data line for the "high" state, indicating that the I2C bus is now idle.

[0059] The I2C interface 319 also couples the microprocessor 310 to a charger / power manager 339 which, together with the regulator 340, manages the power supplied to and drawn from the battery 341. The battery 341 is charged when the data receiving device 120 is plugged into a suitable power source via the integrated USB controller 315. The data receiving device 120 may include a USB On-the-Go (OTG) 2.0 full speed interface and an appropriate connector (e.g., a Micro B type connector). The port is used to charge the battery 341 when connected to a USB charger 343 without establishing a simultaneous data connection, or to interact with the user device 140 to, for example, establish a data connection and download analyte value readings for data analysis and monitoring.

[0060] The data receiving device 120 includes an integrated USB that complies with the USB Battery Charger Specification, which defines limiting, detection, control, and reporting mechanisms that allow the device to draw current exceeding the USB 2.0 specification for charging or powering from dedicated chargers, hosts, and hubs, and for charging downstream ports. These mechanisms are backward compatible with USB 2.0 compatible hosts and peripheral devices. This has led to the creation of USB chargers that expose a USB Standard A receptacle that allows a portable device (e.g., the data receiving device 120) to be charged from a user device 140 or from a USB charger 343 using the same USB cable.

[0061] When connecting to a host that requires a data connection, USB communications are protected by requiring authorization and encryption of payload data. The Instrument Abstraction Service (MAS) is designed to be used during USB communications. The MAS is responsible for establishing communications with the data receiving device 120. The MAS runs in the background of the host device to allow for faster response and loading times. The MAS can further initiate communications with the data receiving device 120 and collect data in parallel with a suitable application automatically launched to be able to interpret the collected data. The MAS handles authentication with the data receiving device 120 and decrypts data received over the USB connection. The MAS manages plug-ins, operates IPC for client communications, routes events, manages database write access, and provides notification events to client applications, such as device connection, detection, and detachment alarms.

[0062] The microprocessor 310 includes a battery charge detector (BCD) and an attachment detection protocol (ADP) module that can identify whether the data receiving device 120 is connected to a USB charger 343 (VBUS is on) or an unpowered host (VBUS is off). Additional hardware provides data communication. In a particular embodiment, the actual connection to the USB host can only be made when the two modules are disconnected after use. In some examples, when the data receiving device 120 optionally incorporates an AFE 347 including a test strip port, the data receiving device 120 can be prohibited from performing a test strip determination, such as through the AFE 347, at any time when the data receiving device 120 has a galvanic connection to a host computer or USB charger (i.e., via a USB link). If a powered host is connected, the user interface on the display 330 can provide a warning or alarm that the test strip determination is not allowed.

[0063] The BCD module of the integrated USB module 315 can detect a standard host port with a maximum draw of up to 500mA or a dedicated charging port with a maximum draw of up to 1500mA. The microprocessor 310 requires VBUS to be connected to a specific processor pin. The processor pin can be configured as a GPIO input, with or without a pull-down to support ADP. The microprocessor 310 can be protected by ensuring that +5VDC is not present on PA9 when the microprocessor 310 is not powered. Figure 8 The circuit shown in (which is a schematic diagram of a VBUS protection circuit according to an embodiment of the present disclosure) can be used to provide such protection. Although VBUS can be used to detect the presence of a USB connection, its absence does not guarantee that it is not connected. Therefore, when a change in the 5V state is detected, a process is initialized to determine whether a powered host or an unpowered host is connected.

[0064] If VBUS is off, the ADP module can be used to detect an unpowered host according to the following process. The process can be programmed by software or firmware or other executable code executed by the microprocessor 310. The ADP module measures the VBUS ramp time (RTIM) from the ADP sink voltage to the ADP probe voltage. The ADP driver determines whether there is an attachment to the USB port of the data receiving device 120 by comparing the RTIM with a threshold. For example, ADP detection can use two thresholds, which can be set by calibration and set during manufacturing. The lower first threshold can be associated with the detection of the attached host, but is associated with the voltage present on VBUS. The measured RTIM below the first threshold can indicate an unpowered host. The higher second threshold can be associated with the detection of the attached host and high external capacitance. The measured RTIM above the second threshold can also indicate an unpowered host. The measured RTIM between the first and second thresholds indicates that no device is connected to the USB port.

[0065] From a hardware perspective, the process starts by turning on the ADPMEN bit in the OTG_GPWRDN register. The ADP core is then reset by setting the ADPRST bit in the OTG_GADPCTL register. The ENAPRB bit in the OTG_GADPCTL register is then set to enable the probe while waiting for the ADPPRBIF bit to be set in the OTG_GADPCTL register to indicate that the operation is complete. Next, the RTIM 11-bit field in the OTG_GADPCTL register is read while monitoring a timeout check or while waiting for the ADPTOIF bit to be set. The ADP result is the RTIM in units of 32kHz, where RTIM is the RC time constant for charging VBUS to 20%. Therefore, using the ADP detection hardware, the microprocessor 310 can detect the type of device connected to the integrated USB module 315.

[0066] When 5V VBUS is available, the BCD function can be used to detect the battery charger type. The BCD function of the integrated USB subsystem 315 can be operated according to the following process. The process can be programmed by software, firmware, or other executable code executed by the microprocessor 310. First, the BCDEN and DCDEN bits in the OTG_GCCFG register are set, and the process waits for the DCDDET bit to start working. A timeout can be used to detect a bad or non-existent connection. Then, the DCDEN bit is reset while waiting for a period of time. The PDEN bit is set and the process waits for another period of time. If the PDET bit is set after waiting, the USB subsystem 315 is connected to a standard downstream port. If the PDET is reset after waiting, the USB subsystem 315 is connected to a dedicated charging port.

[0067] Once the connection type is determined, the USB stack of the microprocessor 310 and the integrated USB module 315 provide support for sending and receiving device reports and queuing reports into commands. The commands may contain internal commands, text-based commands, or binary commands. The USB stack may further support internal commands that may include firmware updates or writes.

[0068] The power subsystem of the data receiving device 120 includes several semi-autonomous functions that work in unison. The subsystem includes an independent battery 341 and a battery monitoring circuit, wherein the independent battery 341 has a protection circuit module that provides protection against overcharging, overdischarging, and overcurrent, and the battery monitoring circuit provides voltage to the ADC converter input of the microprocessor 310 to measure the battery voltage.

[0069] The data receiving device 120 can incorporate a power path management IC to manage battery charging and system power distribution within the reader. When connected to a USB port, the data receiving device can be configured to comply with the USB standard for current draw during enumeration by appearing as a 100mA device. As described above, once the upstream device is properly identified, the data receiving device 120 is configured in 400mA mode, which allows for simultaneous battery charging and device operation to be completed by USB power. The upstream device powers the data receiving device 120 while simultaneously and independently charging the battery 341. This reduces the number of charge and discharge cycles on the battery and allows for proper charge termination.

[0070] Through the ADC 316, the microprocessor 310 may be communicatively coupled to one or more analog circuits, such as a temperature sensor 345 and an analog front end (AFE) 347. Through the AFE 347, the microprocessor 310 of the data receiving device 120 may optionally receive, for example, a digital value corresponding to a detection level of a test strip, as described herein.

[0071] As described herein, the digital receiving device 120 includes an integrated display 330. Output data is presented to the display via a parallel bus 318, where control of the backlight of the display is provided by a backlight driver 350. In certain embodiments, the backlight driver 350 output 322 operates as a buffer from the DAC output 322 to reduce the high output impedance. In some cases, operating with a buffer has the effect of reducing the backlight LED current.

[0072] In some embodiments, the display 330 includes an interactive touch screen. The interactive features are provided by a touch screen overlay 351, which enables addressing of portions of the display 330 that can be mapped to user interface elements.

[0073] Although shown as a single module 317, for operability, the SPI module 317 can include multiple different modules. The SPI module 317 can interface the microprocessor 310 with an onboard flash memory 355 external to the microprocessor 310. The external flash memory 355 can be used to store data, such as fonts, bitmaps, application code, and other various contents. The flash memory 355 or flash memory 312 can further store analyte data received from the sensor control device 102, as described herein, and the data receiving device communicates with the sensor control device 102.

[0074] SPI module 317 additionally interfaces microprocessor 310 with RFID integrated circuit 360. RFID IC 360 may include an oscillator, such as a 13.56 MHz oscillator 361 to enable RFID antenna 363 compliant operation. RFID IC 360 may be capable of clocking at up to 10 MHz, but may be limited, for example, to 2 MHz to minimize noise coupling. RFID IC 360 clock may be configured to 1.5 MHz. Since RFID IC 360 is capable of communicating using, for example, a near field communication protocol, the RFID IC may be configured to generate a signal to the microprocessor 310 associated with an NFC interrupt when incoming communications are detected and / or when maintenance of the RFID IC 360 is required.

[0075] The UART module 320 enables the microprocessor 310 to interface with the BLE coprocessor 365. The BLE coprocessor 365 controls the operation of the BLE antenna 367 to enable communication input to the data receiving device 120 and communication output from the data receiving device 120. Similar to the RFID IC 360, the BLE coprocessor 365 can include an integrated external oscillator to provide timing operations. Both the microprocessor 310 and the BLE coprocessor 365 support low-power sleep mode. The software used by the microprocessor 310 and the BLE coprocessor 365 uses a hardware pin to wake up another peer processor to prepare for incoming commands. The wake-up process involves a handshake, in which the transmitter sets a ready signal and waits for the ready signal of the peer processor before sending data. Through the control operation of the microprocessor 310, the data receiving device 120 can communicate with other devices such as the sensor control device 102 using the RFID antenna 363 and the BLE antenna 367.

[0076] The data receiving device 120 can be configured to wirelessly couple with the sensor control device 102 and transmit commands to and receive data from the sensor control device 102. As embodied herein, the data receiving device 120 can be configured to operate as an NFC scanner and a BLE endpoint with respect to the sensor control device 102 as described herein. For example, the data receiving device 120 can issue a command (e.g., an activation command for a data broadcast mode of the sensor; a pairing command to identify the data receiving device 120) to the sensor control device 102 using a first module (e.g., an RFID IC 360) and receive data from and transmit data to the sensor control device 102 using a second module (e.g., a BLE co-processor 365 and associated hardware).

[0077] As another example, the data receiving device 120 may include, for example, a cellular radio module. The cellular radio module may include one or more radio transceivers for communicating using a broadband cellular network, including but not limited to third generation (3G), fourth generation (4G) and fifth generation (5G) networks. In addition, according to one or more of the IEEE 802.11 standards (e.g., 802.11a, 802.11b, 802.11g, 802.11n (also known as Wi-Fi 4), 802.11ac (also known as Wi-Fi 5), 802.11ax (also known as Wi-Fi 6)), the data receiving device 120 may include a Wi-Fi radio module for communicating using a wireless local area network. Using the cellular radio module or the Wi-Fi radio module, the data receiving device 120 can communicate with the remote application server 155 to receive analyte data or provide updates or inputs received from a user (e.g., through one or more user interfaces).

[0078] As embodied herein, the sensor control device 102 may provide data to the data receiving device 120 or the multi-purpose data receiving device 130. The data receiving device 120 may transmit the data to the user computing device 145. The user computing device 145 (or the multi-purpose data receiving device 130) may in turn transmit the data to the remote application server 155 for processing and analysis.

[0079] As embodied herein, the data receiving device 120 can be configured to coordinate with the sensor control device 102 and operate based on the analyte data received from the sensor control device 102. For example, in the case where the sensor control device 102 is a glucose sensor, the data receiving device 120 can be or include an insulin pump or an insulin injection pen. In coordination, the compatible device 130 can adjust the user's insulin dosage based on the glucose value received from the analyte sensor.

[0080] Figure 4 is a schematic diagram of an input / output (IO) expander 337 used in accordance with an embodiment of the present disclosure. The IO expander 337 is used to provide additional pins for accessing the inputs and outputs of the microprocessor 310. As an example, the IO expander 337 can be used to connect the microprocessor 310 to a battery management IC including a charger / power manager 339 and a regulator 340, a switch VDD for the display 330, a volume control for a buzzer 335 or a haptic motor 333 control, or an output radio interface. The microprocessor 310 communicates with the IO expander 337 using an I2C interface 319. The outputs (e.g., OUT0 to OUT11) can be programmable. The inputs (e.g., IN0 to IN3) can have internal resistive pull-downs within the IO expander, e.g., 100k ohm pull-downs.

[0081] Figure 5 3 is a schematic diagram of a touch screen circuit used according to an embodiment of the present disclosure. The touch screen interface 351 of the display 330 is implemented using an integrated touch sensing controller 321. The touch screen controller module 321 is a hardware touch implementation. The touch screen controller 321 drives the touch electrodes and logic of the microprocessor 310 to scan, measure, output results, and interrupt based on the received input.

[0082] The touch sensing feature is based on charge transfer, such as Figure 5 As shown. CX includes the internal parasitic capacitance of the general purpose input / output (GPIO) pins of the microprocessor 310 and the PCB trace capacitance. Both the parasitic capacitance of the GPIO pins and the PCB trace capacitance can be referenced to the application ground. Ct is the parallel plate capacitance formed between the electrode 510 and the earth ground when the user, for example, touches the electrode with a finger. CF is the feedback capacitor between the ground and the application ground. Cs is the sampling capacitor used by the touch sensing controller 321. The total capacitance at the sensor input node of each touch sensing controller 321 is CX+CT / / CF.

[0083] The touch sensing controller 321 charges the capacitance at the input node to a stable reference voltage (VDD) and then transfers the accumulated charge to the sampling capacitor (Cs). This process is repeated until the voltage across the sampling capacitor reaches V_IH. The number of transfers required to reach this threshold depends on the capacitance at the input node. When the user touches the sensor, the capacitance to ground increases by increasing CT, and the amount of time required for the sampling capacitor to reach V_IH decreases.

[0084] When the sampling capacitor reaches V_IH, the touch sense controller 321 stops the charging process and discharges the sampling capacitor back to 0 V. When the number of counts charged to Cs is less than a specified threshold, the touch sense controller 321 reports a detection.

[0085] Figure 6 is a diagram showing the allocation and numbering of touch zones according to an embodiment of the present disclosure. One sampling capacitor can be used for up to 3 capacitive sensing channels to reduce system components. In a specific embodiment, 3 capacitive sensing channels are connected to sensing zones of approximately the same size and capacitance. A combination of up to 3 sensing channels and one sampling capacitor can be referred to as a touch sensing group.

[0086] Figure 7 is a schematic diagram showing the connection of a touch screen display 330 to a microprocessor 310 according to an embodiment of the present disclosure. In a particular embodiment, the display 330 is a small, relatively low resolution color TFT display. Other embodiments may include larger or smaller displays, higher or lower resolution, color or non-color displays, and displays using different display technologies. The display controller may interface via a number of hardware selectable interfaces. In Figure 7 In the embodiment shown in FIG. 1 , the display uses an 8080 type 1 16-bit MCU interface. Using a 16-bit interface, the data receiving device 120 can support 64K colors (RGB 5-6-5) with a single bus to write / read per pixel to the controller.

[0087] The microprocessor 310 may include a flexible memory controller (FMC) module 700, which may be configured to interface seamlessly with a display driver. In an embodiment using a display based on TFT technology, the backlight of the display 330 may be an integral part of the display module. Unlike an LCD interface, which only requires a backlight to be viewed under low light conditions, TFT technology requires a constant light source to make the display content visible. The boost converter may be configured to act as a voltage-controlled current source, driving a controlled current through a series LED chain within the TFT display module. The boost may draw power directly from the battery 341. The DAC control is set to provide dimmable control of the display, and if the display is proven to be variable in brightness from one module to another, from one manufacturer to another, etc., the ability to fine-tune the brightness is provided.

[0088] FIG. 9A to FIG. 9B1 is a schematic diagram of an analog front-end circuit according to an embodiment of the present disclosure. As described, the data receiving device 120 may optionally include hardware and executable code to perform a test strip determination. When the test strip is inserted into the data receiving device 120 in the included case, the data receiving device 120 wakes up. The strip insertion and identification process continues. First, the strip insertion causes an interrupt because the signal is mechanically grounded by the strip port 370. This ground pulls up the resistor to VBAT. Next, the firmware tests the type of the test strip. As an example, a ketone test strip can be identified by detecting a conductive bar printed to a specific port pin of a short strip together. The test strip AFE 347 detects the short strip and sets the appropriate pin to issue an interrupt to the ADC 316. If the test strip is detected, but cannot be identified as a ketone test strip, the firmware can assume that the test strip is a glucose test strip and continue accordingly. In other embodiments, a glucose test strip can be positively determined, and a ketone test strip can be assumed by default. Although ketone and glucose test strips are discussed, this is only by way of illustrative examples, and other types of test strips may be encountered.

[0089] refer to FIG. 9A to FIG. 9B , external op amp U1A and external op amp U1B are transimpedance amplifiers for trigger (TRIGGER) and work (WORK), external op amp U12B is a fixed unity gain buffer for the RC filter work 1X channel (WORK_FILT), and external op amp U12A is a fixed 4x gain amplifier for the work 4X channel. DAC0 is a 12-bit DAC for work and trigger transimpedance amplifier bias. These circuits support a variety of AFE channels and current ranges. For each channel, a measurement stage is identified, which can include but is not limited to work peak, work 1X, work 4X, and trigger. In a specific embodiment, as FIG. 9A to FIG. 9B A similar circuit as shown may be implemented using two available operational amplifiers within microprocessor 310 for an operating 1X buffer and an operating 4X gain stage.

[0090] In a particular embodiment, a 3V ADC reference is used to reduce the use of a differential amplifier. This configuration can allow a 4x gain with a maximum input offset, which leaves enough headroom for a working 4X signal. The differential amplifier is not used to subtract the strip bias voltage before applying the 4x gain to obtain a working 4X signal. This avoids the need for a bipolar ADC mode to handle negative readings when the signal is close to zero. This configuration also reduces the need to add an offset to the differential signal to keep it positive at the A / D input. However, this configuration requires the use of a 1.2V bandgap reference (VREFINT) internal to the microprocessor 310 to correct the ADC data and DAC settings due to changes in VREF+, which may drift due to slowly decreasing or discharging battery voltage input to the LDO.

[0091] In order to use 16-bit resolution, hardware oversampling and software averaging are used. In general, greater ADC resolution is useful because a large component of the conversion error is often in the internal ADC noise in the counts. Therefore, the better the resolution, the lower the chance that noise can be a problem in the current it represents. The ADC used by the microprocessor 310 can be scaled up to a higher resolution through hardware oversampling and software averaging. A hardware oversampling setting of 16x or greater gives a 16-bit result via the summation of consecutive ADC samples and reduction to 16 bits.

[0092] There are four AFE signals. The four AFE signals are Figure 8 The outputs of four different op amps in the circuit shown in . The op amp outputs then go to four different ADC inputs. Current range, resolution, bandwidth, and time constants are related, and information directly applicable to software control and range switching of the AFE is extracted. Tolerances can be built into the nominal design resolution and range specifications because the op amp resistor and ADC reference voltage tolerances result in small deviations from the maximum overall gain and range tolerances from nominal. Because the operating 4X gain stage follows a 300Hz LPF, a lag-lead filter topology is used to place the filter far beyond the target frequency. A lag-lead filter means that the frequency response is typically a 4x gain low pass filter with a cutoff at the pole frequency, and then approaches unity gain at frequencies beyond the zero frequency.

[0093] In a particular embodiment, the maximum hardware oversampling (of 256x) can be used for default and assay ADC samples to reduce the increased overhead of software averaging for the default samples. This approach simplifies implementation details and standardizes implementation requirements across sample types. However, in some cases, unintentional errors prevent this approach. As an example, in some cases, a hardware failure may destroy the first ADC sample processed in this manner. The turnaround may be to discard the first sample. However, because the assay timing is given at 1 millisecond resolution, 256x oversampling produces samples that are too long to be discarded. Therefore, 8x resolution hardware oversampling can be used, which reduces the time error of the first discarded sample to less than 1 millisecond. Software averaging can be used to obtain the 256x average of the default hardware samples.

[0094] In certain embodiments, rather than correcting each ADC sample or sample average during a strip assay, the strip signal channel slopes (e.g., for Operating Peak, Operating 1X, Operating 4X, and Trigger) can be corrected and stored at the beginning of a simple assay. These corrected slopes can be applied to the raw ADC strip signal readings to obtain the assay currents used to determine the analyte value of the assay. A similar scheme can be used for DAC setting corrections.

[0095] Fig.10 3 is a schematic diagram of a temperature sensor 345 according to an embodiment of the present disclosure. The data receiving device 120 can measure the temperature within a certain tolerance accuracy (eg, ±1° C.) over an operating temperature range. Fig.10 As shown, the temperature sensor includes an external 100KΩ (at 25°C) thermistor RT1, whose resistance changes with temperature. The thermistor is used for temperature sensing. A mapping of temperature to RT1 measurement can be provided by the manufacturer. The 100KΩ resistor is further placed in series with RT1 to produce a voltage TEMP_MON, the digital conversion of which is used in a software lookup table (LUT) to determine the temperature. Note that the thermistor is driven by 3VVDD, which produces a small self-heating effect at the thermistor. However, this effect is on the order of about 0.02°C, which is negligible compared to the ±1°C temperature measurement accuracy requirement. The detected temperature from the temperature sensor can be used to calibrate or otherwise modify the analyte value interpreted by the microprocessor 310.

[0096] The external working and trigger op amps are enabled via GPIO controls of OP_ENABLE and OP1_ENABLE from the microprocessor 310. OP_ENABLE enables or disables the three working channel external op amps together - WORK_OUT, WORK1X, and WORK4X. OP_ENABLE1 enables or disables the trigger (Trigger) external op amp. The open drain 3V+ tolerant microprocessor 310 output pins are used to interface the 3V op amp inputs to the 1.8V microprocessor 310 I / O. External pull-ups of 249K are used for each op amp enable. The selection of this pull-up resistor value results in an open drain microprocessor 310 high and low output with values ​​close to the op amp supply rails, providing good logic threshold margins.

[0097] The bar REF pin is assigned to two microprocessor 310 output pins connected together to reduce low voltage output saturation. The output pins can change state together at the same time under software control. When the bar REF is in high impedance, the bar REF is used to pause chemical reactions during an assay. When the bar REF is in low impedance, the bar REF is used to initiate chemical reactions during an assay. At the highest specific operating current level of 120uA, the low voltage on this pin saturates at 1.0mV nominal.

[0098] ADC self-calibration is used to adjust the ADC offset. ADC offset calibration is performed each time the data receiving device 120 wakes up, allowing ADC self-calibration to be performed before run-time measurement offset measurement. In certain embodiments, ADC self-calibration can also be performed before AFE channel slope calibration or before AFE ADC serial commands.

[0099] The storage memory 230 of the sensor control device 102 may include a software block related to the communication protocol of the communication module. For example, the storage memory 230 may include a BLE service software block, which has the function of providing an interface to make the BLE module 241 available to the computing hardware of the sensor control device 102. These software functions may include a BLE logical interface and an interface parser. The BLE service provided by the communication module 240 may include a general access file service, a general attribute service, a general access service, a device information service, a data transmission service, and a security service. The data transmission service may be a main service for transmitting data such as sensor control data, sensor state data, analyte measurement data (historical and current) and event log data. The sensor state data may include error data, current time activity and software status. The analyte measurement data may include information such as current and historical raw measurement values, current and historical values ​​after processing using appropriate algorithms or models, predictions and trends of measurement levels, comparisons of other values ​​with patient-specific average values, and calls of actions determined by algorithms or models and other similar types of data.

[0100] According to aspects of the disclosed subject matter, and as embodied herein, the sensor control device 102 can be configured to communicate with multiple devices simultaneously by adapting features of the communication protocol or medium supported by the hardware and radio of the sensor control device 102. As an example, the BLE module 241 of the communication module 240 can be provided with software or firmware to enable multiple simultaneous connections between the sensor control device 102 as a central device and other devices as peripheral devices, or other devices as peripheral devices of which another device is a central device.

[0101] A connection between two devices using a communication protocol such as BLE (and ensuring a communication session) can be characterized by a similar physical channel operating between the two devices (e.g., the sensor control device 102 and the data receiving device 120). The physical channel can include a single channel or a series of channels, including, for example but not limited to, a series of channels using a convention determined by a common clock and a channel hopping sequence or a frequency hopping sequence. Communication sessions can use a similar amount of available communication spectrum, and multiple such communication sessions can exist in the vicinity. In some embodiments, each set of devices in a communication session uses a different physical channel or series of channels to manage interference between devices in the same vicinity.

[0102] For purposes of illustration and not limitation, reference is made to an exemplary embodiment of a process of sensor-receiver connection for use with the disclosed subject matter. First, the sensor control device 102 repeatedly announces its connection information to its environment while searching for a data receiving device 120. The sensor control device 102 may periodically repeat the announcement until a connection is established. The data receiving device 120 detects the announcement packet for the sensor control device 102 and scans and filters for connection through the data provided in the announcement packet. Next, the data receiving device 120 sends a scan request command, and the sensor control device 102 responds with a scan response packet providing additional details. The data receiving device 120 then sends a connection request using the Bluetooth device address associated with the data receiving device 120. The data receiving device 120 may also continuously request to establish a connection to a sensor control device 102 with a specific Bluetooth device address. The devices then establish an initial connection that allows them to begin exchanging data. The devices begin the process of initializing the data exchange service and performing a mutual authentication process.

[0103] During the first connection between the sensor control device 102 and the data receiving device 120, the data receiving device 120 may initialize a service, feature, and attribute discovery process. The data receiving device 120 may evaluate these features of the sensor control device 102 and store them for use during subsequent connections. Next, the device enables notification of a customized security service for mutual authentication of the sensor control device 102 and the data receiving device 120. The mutual authentication process may be automatic and does not require user interaction. After successfully completing the mutual authentication process, the sensor control device 102 sends a connection parameter update to request the data receiving device 120 to use the connection parameter settings that are preferred by the sensor control device 102 and configured for maximum lifetime.

[0104] The data receiving device 120 can then perform a sensor control process to backfill historical data, current data, event logs, and plant data. As an example, for each type of data, the data receiving device 120 can send a request to initiate a backfill process. The request can specify a record range defined as appropriate based on, for example, a measurement value, a timestamp, etc. The sensor control device 102 responds with the requested data until all previously unsent data in the memory of the sensor control device 102 is delivered to the data receiving device 120. The sensor control device 102 can respond to a backfill request for all data sent from the data receiving device 120. Once the backfill is completed, the data receiving device 120 can notify the sensor control device 102 that the data receiving device 120 is ready to receive regular measurement readings. The sensor control device 102 can repeatedly send readings across multiple notification results. As embodied herein, multiple notifications can be redundant notifications to ensure that the data is transmitted correctly. Alternatively, multiple notifications can constitute a single payload.

[0105] For purposes of illustration and not limitation, reference is made to an exemplary embodiment of a process of sending a shutdown command to the sensor control device 102. If the sensor control device 102 is in, for example, an error state, an insertion failure state, or a sensor expiration state, a shutdown operation is performed. If the sensor control device 102 is not in these states, when the sensor control device 102 transitions to the error state or the sensor expiration state, the sensor control device 102 can record the command and perform the shutdown. The data receiving device 120 sends a properly formatted shutdown command to the sensor control device 102. If the sensor control device 102 is actively processing another command, the sensor control device 102 responds with a standard error response indicating that the sensor control device 102 is busy. Otherwise, the sensor control device 102 sends a response when the command is received. In addition, the sensor control device 102 sends a success notification through the sensor control feature to inform the sensor control device 102 that the command has been received. The sensor control device 102 records the shutdown command. At the next appropriate opportunity (e.g., as described herein, depending on the current sensor state), the sensor control device 102 shuts down.

[0106] The microprocessor 310 may further provide a hardware-based random number generator. The random number generator may be used to facilitate certain authentication or encryption operations by providing a nonce value, a check value, or other initialization values ​​used when two devices are confirming a shared secret or a peer device accessing a private key. Authentication and encryption may be operable to support, for example, NFC, BLE, or USB security. The hardware-based random number generator provided by the microprocessor 310 may improve the configuration that only software-based random number generators can use. Because software-based methods may be deterministic, they depend on the seed value used and are therefore considered to be pseudo-random number generators. In addition, in some configurations, a hardware-based random number generator may be provided by a peer processor (such as a BLE coprocessor 365) of the data receiving device 120. In such a configuration, when a random number generator is needed, the microprocessor 310 requests a random number from the peer processor. The microprocessor 310 may use a random number received from a peer processor or may use the random number as a seed for a software-based method. However, these methods may have undesirable side effects. As an example, requesting hardware-based random numbers from a peer processor (e.g., BLE co-processor 365) in the form of calls to input and output (from the processor's perspective) slows down the process that relies on random numbers. In addition, from the perspective of the microprocessor 310, new hardware components are involved to remove control of random number generation, which can expose unintentional errors or security risks. Moreover, the need for additional hardware components to generate random numbers consumes additional battery power when compared to using a hardware-based approach such as provided by the microprocessor 310. Therefore, a hardware-based random number generator incorporated into the microprocessor 120 itself can increase the availability of random numbers (encourage their use), reduce the time, energy, and input-output related costs of using hardware-based random numbers generated by the co-processor, and minimize exposure to intentional abuse or unintentional errors.

[0107] The multi-purpose data receiving device 130 may be a mobile communication device, such as a Wi-Fi or Internet enabled smart phone, tablet computer, or personal digital assistant (PDA). Examples of smart phones may include, but are not limited to, those based on WINDOWS operating system, ANDROID operating system, IPHONE operating system, PALM, WEBOS, BLACKBERRY operating system, or SYMBIAN operating system, having a data network connection function for data communication via an Internet connection and / or a local area network (LAN).

[0108] The multi-purpose data receiving device 130 can also be configured as a mobile smart wearable electronic component, such as an optical component worn on or near the user's eyes (e.g., smart glass or smart glasses, such as Google Glasses). The optical component can have a transparent display that displays information about the user's analyte level (as described herein) to the user while allowing the user to view through the display so that the user's overall vision is minimally blocked. The optical component can be capable of wireless communication similar to a smart phone. Other examples of wearable electronic devices include devices worn around or near the user's wrist (e.g., smart watch, etc.), neck (e.g., necklace, etc.), head (e.g., headband, hat, etc.), chest, etc.

[0109] The multipurpose data receiving device 130 may be configured with a software application package (e.g., an "app") downloaded from a remote application server 155 or an application store. The app may enable communication with the sensor control device 102 using one or more protocols compatible with the sensor control device's communication hardware (e.g., the BLE module 241 or the NFC module 225). The app may further enable the multipurpose data receiving device 130 to process data received from the sensor control device 102. For example, the app may enable the multipurpose data receiving device 130 to decrypt and interpret analyte data for display to a user.

Claims

1. An analyte monitoring device for receiving data in an analyte monitoring system, include: microprocessor; one or more communication integrated circuits electrically coupled to the microprocessor, wherein the one or more communication integrated circuits are also electrically coupled to at least one corresponding antenna; An analog front end is electrically coupled to the microprocessor and to a test strip port, wherein the analyte monitoring device is configured to perform an assay to determine the presence or level of an analyte in a sample presented to the test strip port. an input-output (IO) expander electrically coupled to the microprocessor, wherein the IO expander is configured to increase the number of input and output pins available to the microprocessor; and One or more storage memories include instructions that, when operable by the microprocessor, cause the microprocessor to receive analyte data from a sensor control device of an analyte sensor in the analyte monitoring system.

2. The analyte monitoring device according to claim 1, in, The microprocessor includes an integrated universal serial bus (USB) module, and wherein the instructions further cause the microprocessor to perform the following steps: detecting attachment of a USB device through a USB port of the analyte monitoring device; and A host type of the USB device is determined, wherein the host type includes a powered USB host or an unpowered USB host.

3. The analyte monitoring device according to claim 2, in, The microprocessor determines the host type of the USB device through an attachment detection protocol module and a battery charge detector module of the analyte monitoring device.

4. The analyte monitoring device according to claim 3, in, The instructions cause the microprocessor to detect the attachment of the USB device and also cause the microprocessor to perform the following steps: measuring a ramp time from a sink voltage of the attachment detection protocol to a probe voltage of the attachment detection protocol; comparing the ramp time and at least a first threshold and a second threshold, wherein the second threshold is greater than the first threshold; and A ramp time below the first threshold or above the second threshold is determined.

5. The analyte monitoring device of any one of claims 2 to 4, further comprising a VBUS protection circuit electrically coupled to the microprocessor.

6. The analyte monitoring device according to any one of claims 2 to 5, in, When the host type of the USB device is a powered host, the microprocessor prevents measurements from being performed using the analog front end until the USB device is detached.

7. The analyte monitoring device according to any one of claims 1 to 6, in, The analyte sensor is configured to detect an analyte level in a bodily fluid of a user, wherein a portion of the analyte sensor is configured to be transcutaneously positioned in the user such that, when operably positioned, a portion of the analyte sensor is configured to reside above a skin surface of the user and an in vivo portion of the analyte sensor is configured to reside below the skin surface and in contact with the bodily fluid of the user.

8. The analyte monitoring device according to any one of claims 1 to 7, further comprising a display for outputting at least processed analyte data from the sensor control device, in, The display includes a touch screen circuit for detecting user input through direct interaction with the display using charge transfer detection between an input node of the touch screen circuit and a sampling capacitor of the touch screen circuit.

9. The analyte monitoring device of any one of claims 1 to 8, further comprising a temperature sensor comprising a thermistor having a resistance that varies with temperature, in, The temperature from the sensor is determined by consulting a lookup table that maps the resistance of the thermistor to the sensed temperature.

10. The analyte monitoring device according to any one of claims 1 to 9, in, The microprocessor also includes a hardware-based random number generator.

11. The analyte monitoring device according to claim 10, in, The instructions also cause the microprocessor to seed a pseudo-random number generator using a random number from the hardware-based random number generator.

12. The analyte monitoring device according to any one of claims 1 to 11, in, The analytes include glucose, ketones, lactate, oxygen, hemoglobin A1C, albumin, alcohol, alkaline phosphatase, alanine aminotransferase, aspartate aminotransferase, bilirubin, blood urea nitrogen, calcium, carbon dioxide, chloride, creatinine, hematocrit, lactate, magnesium, oxygen, pH, phosphorus, potassium, sodium, total protein, or uric acid.

13. The analyte monitoring device according to any one of claims 1 to 12, in, The analog front end includes four external operational amplifiers and uses an external VREF.

14. The analyte monitoring device of any one of claims 1 to 13, the microprocessor being electrically coupled to a motor for providing tactile feedback.

15. The analyte monitoring device according to any one of claims 1 to 14, in, The IO expander is electrically coupled to a buzzer for providing audible feedback.

16. The analyte monitoring device according to any one of claims 1 to 15, in, The IO expander is electrically coupled to a battery monitoring integrated circuit of an analyte monitoring device.

17. A method, include: The following steps are performed by a microprocessor of an analyte monitoring device in an analyte monitoring system: prior to transitioning to a low power mode, enabling write protection of at least one memory location in a flash memory electrically coupled to the microprocessor, wherein the at least one memory location is associated with a state of one or more status registers in the flash memory; converting by the microprocessor to operate in the low power mode; and Disabling write protection of the at least one memory location after waking up from the low power mode, wherein write protection of the at least one memory location was enabled prior to transitioning to the low power mode, preventing a value stored in the at least one memory location from being unintentionally modified by a process operating while the microprocessor is operating in the low power mode.

18. The method according to claim 17, in, The state corresponds to a clock safety state.

19. An analyte monitoring device for receiving data in an analyte monitoring system, include: microprocessor; one or more communication integrated circuits electrically coupled to the microprocessor, wherein the one or more communication integrated circuits are also electrically coupled to at least one corresponding antenna; an input-output (IO) expander electrically coupled to the microprocessor, wherein the IO expander is configured to increase the number of input and output pins available to the microprocessor; and One or more storage memories include instructions that, when operable by the microprocessor, cause the microprocessor to receive analyte data from a sensor control device of an analyte sensor in the analyte monitoring system.

20. The analyte monitoring device of claim 19, in, The microprocessor includes an integrated universal serial bus (USB) module, and wherein the instructions further cause the microprocessor to perform the following steps: detecting attachment of a USB device through a USB port of the analyte monitoring device; and A host type of the USB device is determined, wherein the host type includes a powered USB host or an unpowered USB host.

21. The analyte monitoring device of claim 20, in, The microprocessor determines the host type of the USB device through an attachment detection protocol module and a battery charge detector module of the analyte monitoring device.

22. The analyte monitoring device of claim 21, in, The instructions cause the microprocessor to detect the attachment of the USB device and also cause the microprocessor to perform the following steps: measuring a ramp time from a sink voltage of an attach detection protocol to a probe voltage of an attach detection protocol; comparing the ramp time and at least a first threshold and a second threshold, wherein the second threshold is greater than the first threshold; and A ramp time below the first threshold or above the second threshold is determined.

23. The analyte monitoring device according to any one of claims 20 to 22, in, When the host type of the USB device is a powered host, the microprocessor prevents measurements from being performed using an analog front end until the USB device is detached.

24. The analyte monitoring device of any one of claims 19 to 23, further comprising a VBUS protection circuit electrically coupled to the microprocessor.

25. The analyte monitoring device according to any one of claims 19 to 24, in, The analyte sensor is configured to detect an analyte level in a bodily fluid of a user, wherein a portion of the analyte sensor is configured to be transcutaneously positioned in the user such that, when operably positioned, a portion of the analyte sensor is configured to reside above a skin surface of the user and an intracorporeal portion of the analyte sensor is configured to reside below the skin surface and in contact with the bodily fluid of the user.

26. The analyte monitoring device of any one of claims 19 to 25, further comprising a display for outputting at least processed analyte data from the sensor control device.

27. The analyte monitoring device of claim 26, in, The display includes a touch screen circuit for detecting user input through direct interaction with the display using charge transfer detection between an input node of the touch screen circuit and a sampling capacitor of the touch screen circuit.

28. The analyte monitoring device of any one of claims 19 to 27, further comprising a temperature sensor comprising a thermistor having a resistance that varies with temperature, in, The temperature from the sensor is determined by consulting a lookup table that maps the resistance of the thermistor to the detected temperature.

29. The analyte monitoring device according to any one of claims 19 to 28, in, The microprocessor also includes a hardware-based random number generator.

30. The analyte monitoring device of claim 298, in, The instructions also cause the microprocessor to seed the pseudo-random number generator using a random number from the hardware-based random number generator.

31. The analyte monitoring device according to any one of claims 19 to 30, in, The analytes include glucose, ketones, lactate, oxygen, hemoglobin A1C, albumin, alcohol, alkaline phosphatase, alanine aminotransferase, aspartate aminotransferase, bilirubin, blood urea nitrogen, calcium, carbon dioxide, chloride, creatinine, hematocrit, lactate, magnesium, oxygen, pH, phosphorus, potassium, sodium, total protein, or uric acid.

32. The analyte monitoring device according to any one of claims 19 to 31, in, The microprocessor is electrically coupled to a motor for providing tactile feedback.

33. The analyte monitoring device according to any one of claims 19 to 32, in, The IO expander is electrically coupled to a buzzer for providing audible feedback.

34. The analyte monitoring device according to any one of claims 19 to 33, in, The IO expander is electrically coupled to a battery monitoring integrated circuit of an analyte monitoring device.

35. The analyte monitoring device of any one of claims 19 to 34, further comprising an analog front end electrically coupled to the microprocessor and to a test strip port, in, The analyte monitoring device is configured to perform an assay to determine the presence or level of an analyte in a sample presented to the test strip port.

36. The analyte monitoring device of claim 35, in, The analog front end includes four external operational amplifiers and uses an external VREF.