Patent Grant
11207006
The subject matter described herein relates generally to changing the state of power consumption of an electrical device in an efficient manner, for example, within an analyte monitoring environment.
The detection and/or monitoring of analyte levels, such as glucose, ketones, lactate, oxygen, hemoglobin A1C, or the like, can be vitally important to the health of an individual having diabetes. Diabetics generally monitor their glucose levels to ensure that they are being maintained within a clinically safe range, and may also use this information to determine if and/or when insulin is needed to reduce glucose levels in their bodies or when additional glucose is needed to raise the level of glucose in their bodies.
Growing clinical data demonstrates a strong correlation between the frequency of glucose monitoring and glycemic control. Despite such correlation, 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. For these and other reasons, needs exist for improved analyte monitoring systems, devices, and methods.
A number of systems have been developed for the automatic monitoring of the analyte(s), like glucose, in a bodily fluid of a user, such as in the blood, interstitial fluid (“ISF”), dermal fluid, or in other biological fluid. Some of these systems include a sensor that can be at least partially positioned “in vivo” within the user, e.g., transcutaneously, subcutaneously, or dermally, to make contact with the user's bodily fluid and sense the analyte levels contained therein. These systems are thus referred to as in vivo analyte monitoring systems.
The sensor is generally part of a sensor control device that resides on (or in) the body of the user and contains the electronics and power source that enable and control the analyte sensing. The sensor control device, and variations thereof, can be referred to as a “sensor control unit,” an “on-body electronics” device or unit, an “on-body” device or unit, or a “sensor data communication” device or unit, to name a few.
The analyte data sensed with the sensor control device can be communicated to a separate device that can process and/or display that sensed analyte data to the user in any number of forms. This device, and variations thereof, can be referred to as a “reader device” (or simply a “reader”), “handheld electronics” (or a handheld), a “portable data processing” device or unit, a “data receiver,” a “receiver” device or unit (or simply a receiver), or a “remote” device or unit, to name a few. The reader device can be a dedicated use device, a smart phone, a tablet, a wearable electronic device such as a smart glass device, or others.
In vivo analyte monitoring systems can be broadly classified based on the manner in which data is communicated between the reader device and the sensor control device. One type of in vivo system is a “Continuous Analyte Monitoring” system (or “Continuous Glucose Monitoring” system), where data can be broadcast from the sensor control device to the reader device continuously without prompting, e.g., in an automatic fashion 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), where data can be transferred from the sensor control device in response to a scan or request for data by the reader device, such as with a Near Field Communication (NFC) or Radio Frequency Identification (RFID) protocol.
Provided herein are a number of example embodiments of systems, devices, and methods that allow the state (or mode) of power consumption for a device, such as a sensor control device, to be changed in an energy efficient manner. Changing of the state of power consumption can include, for example, changing from a low power state (e.g., powered off) to a higher power state (e.g., powered on). In some cases, this change of state is referred to as “activation” and is employed, for example, when a sensor control device is first put in use by a wearer. For ease of illustration, many of the embodiments described herein will refer to changing the power state of a sensor control device, although these embodiments are not limited to such.
In certain embodiments an activation sensor is provided with the sensor control device and operation of the activation sensor causes activation of the internal electronics. The activation sensor can be an optical activation sensor that produces a response when exposed to ambient optical light or another light source. The exposure to light (or some other trigger such as a magnetic field) and subsequent activation can be accomplished before applying the device to the body of a user, for example, during the unpacking of the applicator assembly. The optical activation sensor can be part of an activation circuit for the sensor control device. Upon exposure to light, the optical activation sensor, which may be in the form of an optically activatable switch, can cause the activation circuit to initiate an on-board processor. The processor, in turn, can maintain the internal electronics in the active state during the duration of use of the sensor control device, or during the lifetime of the device's power supply. Verification of the initiation of the electronics can be performed by the user or automatically by the system, such as by generation of a message or other indication to the user at the reader device. Also provided are methods of manufacturing the sensor control device with a sensor control activation sensor such as an optical sensor.
In other embodiments, the sensor control device is capable of utilizing transmissions over a wireless communication protocol to change a power state, or to recognize when such a change should be effected.
For example, the sensor control device can be capable of sending and receiving communications according to a Bluetooth Low Energy (BTLE) protocol. In certain embodiments, the sensor control device, while operating in a first power state (e.g., a low power state such as a powered-off or inactivated state, a storage state, or a sleep state), can receive such a wireless communication from the reader device and recognize that it is or is part of a BTLE advertising sequence (or is a single advertising message). The recognition can be made either through hardware or software. Upon making that recognition, the sensor control device can change to a second, higher power state (e.g., a state of greater power consumption than the first power state, such as a powered-on or activated state, or an awake state). In certain embodiments, the sensor control device can recognize the advertising sequence without first demodulating the communication.
In some embodiments the sensor control device receives a second or subsequent advertising sequence from the reader device when in the second power state. The sensor control device can demodulate the second advertising sequence and determine if it contains an activation request message and, if so, then transmit a confirmation response to the reader device. If the demodulated communication does not contain the activation request message, then the state of the sensor control device can be changed back to the first power state. In some embodiments, the first power mode is a sleep (or storage) mode and the second power mode is a normal operation mode.
A number of variations to the aforementioned embodiments are also provided. For example, the advertising sequence can include a series of advertising packets transmitted at a predetermined time interval. The advertising sequence can include a connectable directed advertising packet type, a connectable undirected advertising packet type, a non-connectable undirected advertising packet type, or a scannable undirected advertising packet type, each of which can be the activation request message.
In still other embodiments, successive radio frequency (RF) communications can be used to supply power to, for example, the sensor control device. The sensor control device can be in a low-power state (e.g., a power-off or inactivated mode, a storage mode, or a sleep mode) where full operating power is not being supplied. The sensor control device can utilize the power of the received wireless communications to cause a local power source to begin supplying the operating power, thereby transitioning the sensor control device to a higher-power state (e.g., a normal, awake, or activated operating state). In many of these embodiments, the wireless communications are sent and received in accordance with a Near Field Communication (NFC) protocol, although other protocols can be used as well.
Adaptive embodiments are also described where the power mode of the sensor control device is directly or indirectly monitored by the reader device and one or more of the number, type, interval, or power of the successive wireless communications is adjusted by the reader device until sufficient power is supplied to enable the sensor control device to transition to a higher-power mode. The embodiments described herein are particularly suitable when the reader device is in the form of a smartphone.
Other systems, devices, methods, features and advantages of the subject matter described herein will be or will become apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that all such additional systems, devices, methods, features and advantages be included within this description, be within the scope of the subject matter described herein, and be protected by the accompanying claims. In no way should the features of the example embodiments be construed as limiting the appended claims, absent express recitation of those features in the claims.
The details of the subject matter set forth herein, both as to its structure and operation, may be apparent by study of the accompanying figures, in which like reference numerals refer to like parts. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the subject matter. Moreover, all illustrations are intended to convey concepts, where relative sizes, shapes and other detailed attributes may be illustrated schematically rather than literally or precisely.
The present subject matter is not limited to the particular embodiments described, as those are only examples and may, of course, vary. Likewise, the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting, since the scope of the present disclosure will be limited only by the appended claims.
In conventional analyte monitoring systems, the sensor control device has a small physical form enabling it to be worn inconspicuously by the user. This constrains the size of the device's internal electronics and power source. If the sensor control device has a limited lifespan dictated by the long-term reliability of the sensor (e.g., fourteen days), then it will be disposable and replaceable with another device. The desirability to minimize the cost of each device adds further pressure to minimize the size of the power source and the rate at which it is used. The power requirements of the sensor control device electronics and the rate at which the software operates those electronics are therefore minimized in the design process.
To this end, the sensor control device is often shipped and stored in a low-power mode where the power source does not supply operating power to all or most of the sensor electronics. In some embodiments, only wireless communication circuitry is active, operating in a mode that draws minimal quiescent current to listen for an activation RF signal.
In this low-power mode the power source can be disconnected mechanically from the internal electronics (such as by placement of a removable insulator between the device's contacts and the power source), electronically (such as with a controllable isolation circuit) in a manner that minimizes leakage current from the source, or otherwise. The power source can be connected once the wearer is ready to begin use of the sensor.
Many of the embodiments described herein provide techniques for changing the power state of a sensor control device with improved efficiency, cost, and reduced hardware and software (among others) as compared to conventional techniques.
An example embodiment of an in vivo analyte monitoring system 100 with which the embodiments described herein can be used is depicted in the illustrative view of
Any version of Bluetooth can be used for communication links 140, 141, and 142. One such version is Bluetooth Low Energy (BTLE, BLE), which is also referred to as Bluetooth SMART or Bluetooth SMART Ready. A version of BTLE is described in the Bluetooth Specification, version 4.0, published Jun. 30, 2010, which is explicitly incorporated by reference herein for all purposes. It should be noted that one of ordinary skill in the art will readily recognize that the embodiments described herein can be used with subsequent iterations of the Bluetooth protocols, or with new protocols that operate in a similar fashion to the Bluetooth protocols described herein, regardless of whether those protocols are in existence as of the time of this filing.
The use of BTLE communication (or other low-energy wireless standards), allows for reduced energy usage, which can be particularly important in performing data transmissions between sensor control device 102 and reader device 120 over link 140. This, in turn, allows for either reduction of the battery size in sensor control device 102 or extension of the battery life (or combinations thereof).
Use of a low-energy wireless communication protocol can allow the respective communication interfaces to have, for example, a lower duty cycle (i.e., less frequent active operation, which drains less battery power), shorter periods of usage, or any combination thereof. In addition to BTLE, other wireless protocols such as Wi-Fi, cellular, Zigbee, and custom protocols can be used instead of, or in addition to, BTLE for links 140, 141, and 142. These other protocols, however, typically require either more energy than BTLE, are not widely integrated into smartphones or tablets, or are not approved for worldwide use. Today and for the foreseeable future, smartphones, tablets, and other portable computing devices will be provided to customers with Bluetooth capability, as that family of protocols is widely regarded as the most convenient to accomplish close proximity communication between, e.g., a tablet, and the tablet's peripherals (e.g., wireless headset, mouse, keyboard, etc.).
Other embodiments of sensor control device 102 and reader device 120, as well as other components of an in vivo-based analyte monitoring system that are suitable for use with the system, device, and method embodiments set forth herein, are described in US Patent Application Publ. No. 2011/0213225 (the '225 Publication), which is incorporated by reference herein in its entirety for all purposes.
Sensor control device 102 can include a housing 103 containing in vivo analyte monitoring circuitry and a power source (shown in
After activation, sensor control device 102 can wirelessly communicate the collected analyte data (such as, for example, data corresponding to monitored analyte level and/or monitored temperature data, and/or stored historical analyte related data) to reader device 120 where, in certain embodiments, it can be algorithmically processed into data representative of the analyte level of the user and then displayed to the user and/or otherwise incorporated into a diabetes monitoring regime.
As shown in
Computer system 170 can be used by the user or a medical professional to display and/or analyze the collected analyte data with an informatics software program. Computer system 170 may be a personal computer, a server terminal, a laptop computer, a tablet, or other suitable data processing device, and can be (or include) software for data management and analysis and communication with the components in analyte monitoring system 100.
The processing of data and the execution of software within system 100 can be performed by one or more processors of reader device 120, computer system 170, and/or sensor control device 102. For example, raw data measured by sensor 104 can be algorithmically processed into a value that represents the analyte level and that is readily suitable for display to the user, and this can occur in sensor control device 102, or it can occur in reader device 120 or computer system 170 after receipt of the raw data from sensor control device 102. This and any other information derived from the raw data can be displayed in any of the manners described above (with respect to display 122) on any display residing on any of sensor control device 102, reader device 120, or computer system 170. The information may be utilized by the user to determine any necessary corrective actions to ensure the analyte level remains within an acceptable and/or clinically safe range.
As discussed above, reader device 120 can be a mobile communication device such as, for example, a Wi-Fi or internet enabled smartphone, tablet, or personal digital assistant (PDA). Examples of smartphones can include, but are not limited to, those phones based on a WINDOWS operating system, ANDROID operating system, IPHONE operating system, PALM WEBOS, BLACKBERRY operating system, or SYMBIAN operating system, with data network connectivity functionality for data communication over an internet connection and/or a local area network (LAN).
Reader device 120 can also be configured as a mobile smart wearable electronics assembly, such as an optical assembly that is worn over or adjacent to the user's eye (e.g., a smart glass or smart glasses, such as GOOGLE GLASSES). This optical assembly can have a transparent display that displays information about the user's analyte level (as described herein) to the user while at the same time allowing the user to see through the display such that the user's overall vision is minimally obstructed. The optical assembly may be capable of wireless communications similar to a smartphone. Other examples of wearable electronics include devices that are worn around or in the proximity of the user's wrist (e.g., a watch, etc.), neck (e.g., a necklace, etc.), head (e.g., a headband, hat, etc.), chest, or the like.
Communications processor 202 can interface with RF transceiver 208 and perform analog-to-digital conversions, encoding and decoding, digital signal processing and other functions that facilitate the conversion of voice, video, and data signals into a format (e.g., in-phase and quadrature) suitable for provision to RF transceiver 208, which can then transmit the signals wirelessly. Communications processor 202 can also interface with RF transceiver 208 to perform the reverse functions necessary to receive a wireless transmission and convert it into digital data, voice, and video.
Applications processor 204 can be adapted to execute the operating system and any software applications that reside on reader device 120, process video and graphics, and perform those other functions not related to the processing of communications transmitted and received over RF antenna 209, such as the handling and formatting of NFC or Bluetooth communications. Any number of applications can be running on reader device 120 at any one time, and will typically include one or more applications that are related to a diabetes monitoring regime, in addition to the other commonly used applications, e.g., email, calendar, etc.
Memory 210 can be shared by one or more of the various functional units present within reader device 120, or can be distributed amongst two or more of them (e.g., as separate memories present within different chips). Memory 210 can also be a separate chip of its own. Memory 210 is non-transitory, and can be volatile (e.g., RAM, etc.) and/or non-volatile memory (e.g., ROM, flash memory, F-RAM, etc.).
NFC communication circuitry 207 can be implemented as one or more chips and/or components that perform controller functions (e.g., level and data mode detection, framing, etc.), analog-digital conversions (ADC and DAC), and analog interfacing with antenna 217 (e.g., the modulation and demodulation of NFC communications). Circuitry 207 can include a voltage-controlled oscillator (VCO), phase-locked loop (PLL) circuitry, a power amplifier for sending communications, and associated filters for waveform shaping. Antenna 217 can be implemented as a loop-inductor as is typical for NFC platforms.
Similarly, Bluetooth communication circuitry 219 can be implemented as one or more chips and/or components that perform controller functions (e.g., level and data mode detection, framing, etc.), analog-digital conversions (ADC and DAC), and analog interfacing with antenna 220 (e.g., modulation and demodulation). Bluetooth communication circuitry 219 can be configured to operate according to any of the Bluetooth standards described herein. Circuitry 219 can include a voltage-controlled oscillator (VCO), phase-locked loop (PLL) circuitry, a power amplifier for sending communications, and associated filters for waveform shaping.
Multi-functional circuitry 212 can also be implemented as one or more chips and/or components, including communication circuitry, that perform functions such as handling other local wireless communications (e.g., Wi-Fi) and determining the geographic position of reader device 120 (e.g., global positioning system (GPS) hardware). One or more other antennas 214 are associated with multi-functional circuitry 212 as needed. Reader device 120 can include all of NFC communication circuitry 207, Bluetooth communication circuitry 219, and multifunctional circuitry 212, or omit any one or more of those blocks (and associated antennas) as desired for the individual application, so long as a manner for communicating with sensor control device 102 is maintained.
Power source 216 can include one or more batteries, which can be rechargeable or single-use disposable batteries. Power management circuitry 218 can regulate battery charging and perform power source monitoring, boost power, perform DC conversions, and the like.
Structural and functional components similar to that described with respect to
A non-transitory memory 253 is also included within ASIC 251 and can be shared by the various functional units present within ASIC 251, or can be distributed amongst two or more of them. Memory 253 can be volatile and/or non-volatile memory. In this embodiment, ASIC 251 is coupled with power source 260, e.g., a coin cell battery. AFE 252 interfaces with in vivo analyte sensor 104 and receives measurement data therefrom, conditions the data signal, and outputs the data signal to processor 256 in analog form, which in turn uses an analog-to-digital converter (ADC) to convert the data to digital form (not shown) and then processes the data to arrive at the end-result analyte discrete and trend values, etc.
This data can then be provided to communication circuitry 258 for sending, by way of antenna 261, to reader device 120 (not shown) where further processing can be performed. Communication circuitry 258 can operate according to any of the NFC, Bluetooth, and Wi-Fi communication protocols described herein, or any other desired communication protocol, depending on the selected manner of communication with reader device 120. For example, communication circuitry 258 can include functional and discrete components similar to those of NFC communication circuitry 207 or Bluetooth communication circuitry 219 described with respect to
Incorporation of the majority, or all, of the data processing into sensor control device 102 allows reader device 120 to act mostly or entirely as a display and interface device for the user. This can provide an advantage in managing regulatory approval of system 100, as sensitive glucose calculations and related processing can be performed on the sensor control device 102 and not on an uncontrolled data processing device such as a commercially available smartphone. Conversion of a smartphone, or other similar commercially available device, into reader device 120 suitable for interfacing with sensor control device 102 can be accomplished by installing a software application (or “app”) onto the smartphone in a conventional manner without any hardware additions or modifications. The software application need only interface with the appropriate communication circuitry (e.g., 207, 219, 212) on this smartphone to accept and display the end-result data from sensor control device 102 (glucose data, trend data, etc.).
The incorporation of algorithmic data processing within sensor control device 102, along with the use of a continuous wireless transmission protocol can also provide the advantage of allowing sensor control device 102 to readily interface with products provided by third parties or other manufacturers, such as other types of healthcare systems that do not have the on-board glucose data processing capabilities and/or algorithms. Examples of third party systems include continuous glucose monitoring systems, home health monitoring systems, hospital vital sign monitors, and closed loop systems (such as an artificial pancreas), or insulin pumps, and the like.
However, the data processing functions described herein can take place within the sensor control device 102 (as just described), reader device 120, computer system 170, or any combination thereof. This can include determinations of the user's analyte or glucose value, determinations of the variation or fluctuation of the monitored analyte level as a function of time, determinations of glucose trend over time, determinations of glucose rate of change, the occurrence of an alarm condition such as hypoglycemia or hyperglycemia or impending hypoglycemia or hyperglycemia, and any other data processing functions described herein (or with respect to data processing module 160 in the '225 Publication).
Example Embodiments for Changing the Power State Using External Stimuli Such as Optical or Magnetic Energy
As described earlier, after the completion of the manufacturing process there may be an extended period of time during which system 100 is not used, for instance, while awaiting shipment, while being present “on the shelf,” or while otherwise awaiting initial use by the customer or subject. During this time, sensor control device 102 may use minimal power in order to conserve the life of on-board power source 260. Sensor control device 102 may be in a low power state, or altogether deactivated if power source 260 is electrically isolated from the remainder of sensor electronics 250. Embodiments where the post-manufacturing initialization, or activation, is performed using wireless signals are described in the incorporated Provisional Application No. 61/817,839. The following embodiments can be freely substituted for those wireless-based embodiments.
In this embodiment, activation circuit 301 includes a P-type MOSFET (PMOS) 302, an N-type MOSFET (NMOS) 304, a resistor 306, and an optical activation sensor 308 (also referred to herein as “optical sensor 308”), which, in this example, is an optically activatable switch 308. The positive terminal of power source 260 is coupled with a first terminal of resistor 306 and a source node of PMOS 302. The gate node of PMOS 302 is coupled with the opposite terminal of resistor 306, a drain node of NMOS 304, and a first terminal of optically activatable switch 308. The drain node of PMOS 302 is coupled with power management circuitry 254, and the gate node of NMOS 304 is coupled with processor 256. The negative terminal of power source 260, the opposite terminal of optically activatable switch 308, and the source node of NMOS 304 are each coupled with ground, or reference node, 312.
Optically activatable switch 308 is just one type of optical sensor. Optically activatable switch 308 can be any device that transitions from an open circuit (or current blocking state) to closed circuit (or current passing state) upon the incidence of radiation in the optical band (optical light). The larger field of optical sensors can include any device that produces a physical, thermal, or electrical response to the presence of optical light. Those of skill in the art will readily recognize that the response should be of sufficient magnitude to distinguish it from noise or other negligible responses. Other bands of radio frequency can be used to activate the switch, including ultraviolet, infrared, and so forth. Optically activatable switch 308 can be, for instance, a photodiode or phototransistor. Here, optically activatable switch 308 is shown as a photodiode that transitions from an open state (e.g., a low energy storage state in which current cannot flow) to a closed state (i.e., an active state in which current can flow) upon the receipt of sufficient optical radiation 310. In many embodiments, the amount of optical radiation 310 necessary to activate switch 308 is relatively low to ensure easy activation by the user at the appropriate time.
Upon receipt of a sufficient amount of radiation 310, photodiode 308 permits current to flow through resistor 306, which in turn causes the gate bias on PMOS pass transistor 302 to drop, thereby allowing current to flow from power source 260 to power management circuitry 254. Power management circuitry 254 is in communication with processor 256 and provides one or more commands or signals to processor 256 to initiate, or boot up, at which point processor 256 can perform an activation routine for sensor control device 102 that brings the remaining sensor electronics 250 into a higher power state.
This technique, as implemented in the optical, magnetic, and other embodiments herein, provides a significant advantage over conventional activation approaches. One such approach is that described in US Patent Publ. 2012/0078071 (Bohm et al.) where a processor must remain active, either by staying awake in a low-power mode or by being awoken in repeated fashion (e.g., each minute), in order to monitor for an interrupt signal (or other indicator) that the sensor device is ready to be taken out of a storage or other inactive mode. During these instances where the processor is in an active mode, even if the mode is a low power one, or only occurs for short intervals, the processor is functioning and drawing current from the power source at a greater rate, thereby depleting the stored charge of the power source and lessening the shelf life of the sensor device. This and other disadvantages are overcome with the embodiments described herein.
In certain embodiments, microprocessor 256 is capable of applying (and holding) a gate bias voltage to the gate of NMOS pass transistor 304 in order to allow current to flow across transistor 304 and thereby latch PMOS 302 in the “ON” state. Stated differently, processor 256 is capable of bypassing the optical sensor after changing the power state of device 102. Thus, should the light incident on the optical sensor (e.g., photodiode 308) become interrupted, sensor electronics 250 will remain active.
In many embodiments, optically activatable switch 308 operates with a relatively low dark current, for example, on the order of 10 nanoamps (nA) or less, so that switch 308 will not significantly impact the life of power source 260 during storage.
Although this embodiment has been described with respect to MOSFET devices, those of ordinary skill in the art will readily recognize that any number of other transistor types can be substituted for those described here, while achieving the same practical result. Also, in view of the disclosure contained herein and the schematic depicted in
Still further, the components of activation circuit 301 can be implemented “on-chip” or “off-chip” or any combination thereof. (On-chip refers to the integration of the respective component with all other components on one semiconductor die.) Here, each of the components of activation circuit 301 is located on-chip with the exception of optically activatable switch 308, which is located off-chip. The placement of optically activatable switch 308 off-chip allows flexibility in the overall package design for sensor electronics 250, for example, by allowing optically activatable switch 308 to be placed in a location amenable to the receipt of sufficient light at the desired activation time.
Optical sensor 308 can be located within a housing of sensor control device 102, on the outer surface of sensor control device 102, or in a position coupled with the applicator (where it would later become detached upon deployment of sensor control device 102), so long as optical sensor 308 remains communicatively coupled with sensor electronics 250 so as to permit activation of those electronics.
At 404 (
In some embodiments, container 506 and applicator 512 can initially be packaged connected together to simplify packaging and shipping. Thus, in those embodiments, before removing cover 508 from the casing 510 and separating removable end cap 514 from applicator assembly 516, in an initial unpacking step, container 506 and applicator 512 are separated from each other.
At 405 (
At 406 (
Next, in an assembly operation 407 (
Next, once the user has chosen an application site, a sensor control device application operation 408 (
In some embodiments, user 500 performs application operation 408 by applying an uncontrolled force to applicator assembly 516 where the uncontrolled force is applied in a single, continuous pushing motion along the longitudinal axis of applicator assembly 516 that once started, causes applicator assembly 516 to perform the application operation 408 such that applicator assembly 516 does not stop operation until completion. Applicator assembly 516 can be configured to relay action/audible cues to user so 500 that all three of the above listed actions happen automatically in response to applying the force to the applicator causing it to trigger.
Advantageously, an adhesive of sensor control device 102 does not contact the user until the downward travel of applicator assembly 516 has completed. So, even after applicator assembly 516 has been placed on the skin, it can be moved to a different location as many times as desired until application operation 408 is actually carried out, and this is without damage to the apparatus or other system components. In a post-application stage 410, use of sensor control device 102 for monitoring the user's analyte level occurs during wear followed by appropriate disposal. An example of such a stage is depicted in
Steps 405 (light exposure) and 406 (initialization) were described above as being performed prior to step 407, however, in some embodiments steps 405 and 406 are performed after step 407, and in other embodiments steps 405 and 406 are performed after step 408. Also, step 406 can be performed immediately after step 405 or with one or more intervening steps.
Additional details regarding the method steps described with respect to
Applicator 512, container 506, and the associated components shown in
Turning to
In some embodiments, the end (not visible) of removable end cap 514 can include one or more openings, which can be sealed by a sterile barrier material such as DuPont™ Tyvek®, or other suitable material, to form seal 608. Such provision allows for ethylene oxide (ETO) sterilization of the applicator 512 through seal 608 when closed. In some embodiments, the openings in removable cap 514 may not be present and removable cap 514 may be made from a sterile process-permeable material so that the interior of applicator assembly 516 can be sterilized when cap 514 is mated to it, but that maintains sterility of the interior of the cap after exposure to the sterility process. In some embodiments, ETO sterilization is compatible with the electronics within sensor electronics 250 and with the associated adhesive patch 105, both of which can be releasably retained within applicator assembly 516 until applied to the user. As shown, applicator assembly 516 includes a housing 614 including integrally formed grip features 616 and a translating sheath or guide sleeve 618.
In reference to
In addition to optical manners of activation, other types of activation can be used with sensor control device 102. One such example is magnetic activation.
The operation of the embodiment in
Magnetic sensor 702 can be located within a housing of sensor control device 102, on the outer surface of sensor control device 102, or in a position coupled with applicator 512, so long as magnetic sensor 702 remains communicatively coupled with sensor electronics 250 so as to permit activation of those electronics 250.
At 805, the user exposes sensor control device 102 to a magnetic field, for example, by bringing sensor control device 102 and/or a magnet into close proximity with each other, in order to initiate magnetic sensor 702 contained within sensor control device 102. At this point, sensor electronics 110 become activated and sensor control device 102 can begin communication with reader device 120. It should be noted that step 805 can be a positive step, such as the user physically bringing the magnetically-sensitive region of applicator 512 towards the source of the magnetic field (or vice versa), or step 805 can be a direct result of removal of applicator cover 514, such as by removal of a magnetic field supplied by a magnet in or on cover 514, which in turn causes activation of electronics 250.
At 806, the initialization, or activation, of sensor electronics 250 is verified. This can be performed automatically by communication between sensor control device 102 and reader device 120. For instance, in one embodiment a successful initialization of sensor electronics 250 will enable a communication to be transmitted from sensor control device 102 to reader device 120, at which point reader device 120 can generate an indication or message to the user that sensor electronics 250 were successfully activated. In another embodiment a visual, auditory, vibrational, or tactile output is generated by sensor control device 102 that indicates successful activation to the user.
The method of use can proceed with steps 807, 808, and 810 in the same manner as described with respect to
Other examples of manners of initialization include the use of near field communication (NFC), cellular energy, Bluetooth energy, Wi-Fi energy, and the like. These types of RF energy can be applied by dedicated devices sold with system 100, or by commercially available devices that can be integrated by the user into system 100, for example, a smartphone or tablet.
In one embodiment, placement of sensor control device 102 into proximity with the user's skin or body will be sensed by a temperature sensitive device that can be used to activate sensor electronics 250. The temperature sensitive device can be a differential device that can distinguish the body temperature of the user from what could be a relatively high ambient temperature. Upon detection of a sufficient gradient between the ambient temperature and the temperature of the user's body (expected to be a typical human body temperature), the temperature sensitive device will become enabled and activate operation of electronics 250, such as by closing a circuit to the power source.
Alternatively, a mechanical switch can be present on device 102, the actuation of which initiates electronics 250 therein. In yet another alternative embodiment, a shorting bar or shorting path can be used. For example, sensor assembly 610 (
The construction of an example embodiment of sensor control device 102 described with respect to the following
Circuit board 900 is ready for an over-mold process or other sealing method. As illustrated in
Alternatively, the enclosure of the electronics assembly of sensor control device 102 may include elements snap-fit (or welded/adhered) together as illustrated in the assembly view of
When snap-fit, various interference or snap fit elements (e.g., annular rims 1106) may be provided around the entirety of the periphery of the enclosure or as discrete snap-fit connectors (not shown). Notably, such an approach may benefit from additional O-ring sealing elements to avoid fluid intrusion. Alternatively or additionally, adhesive set at the snap junction(s) may be used to ensure good sealing, especially in connection with continuous annular snap-fit features 1106. As seen in
However constructed, final assembly of the electronics assembly of sensor control device 102 involves adhesive patch installation. An exemplary approach is illustrated in
The surface of sensor control device 102 on which window 1218 is located (as shown in
Example Embodiments for Changing the Power State Using Wireless Transmissions
Additional embodiments that can be used to activate sensor control device 102, establish communication with sensor control device 102, and/or reestablish communication with sensor control device 102 (e.g., after a prior communication session has ended) are set forth here. These embodiments involve the sending of one or more RF transmissions from reader device 120 to sensor control device 102. In some embodiments, the RF transmissions are sent according to a Bluetooth protocol in the RF band from about 2400 to 2480 Megahertz (Mhz) (or 2.4 to 2.48 Gigahertz (Ghz)), while in other embodiments communications made according to NFC protocols and other protocols and frequency bands can also be utilized.
As already mentioned, sensor control device 102 is provided to the user in a powered-off (or power-off, or deactivated) state where the circuitry of sensor control device 102 consumes little, if any, current from power source 210. Sensor control device 102 can be activated such that it changes state from this powered-off (or storage) state to a second state that consumes relatively higher power.
If in the storage state, the second state may be a normal operation state. If in a fully deactivated powered-off state, the second state may be characterized as a low-power state that is used to conduct low-power monitoring for wireless signals or transmissions coming from reader device 120. These transmissions can advertise the availability of reader device 120 to establish a communication session with sensor control device 102. The transmission(s) can be used to activate sensor control device 102. This low-power state can allow sensor control device 102 to operate for a relatively long period of time while device 102 awaits the receipt of a wireless transmission from reader device 120.
Once sensor control device 102 receives one or more wireless transmissions from reader device 120 that indicate that the user is ready to begin normal usage of sensor control device 102 (e.g., the collection and transmission of sensed analyte data), then sensor control device 102 can optionally transition to a third state that consumes even higher power than the first (e.g., fully deactivated) and second states. In this third state, sensor control device 102 can fully establish the communication link with reader device 120, sense analyte levels in the user's bodily fluid, perform some degree of processing on the sensed data, and/or transmit that sensed data to the reader device 120. Continuous operation in this third state will, in most embodiments, last for a predetermined time period, e.g., 14 days.
Of course, in any of the embodiments described herein, it is possible for sensor control device 102 to temporarily enter lower power states to conserve energy even after commencement of normal operation.
Sensor control device 102 can be activated using wireless RF transmissions, e.g., can transition from a powered-off state, or a storage state, to a higher power state, at any time prior to communicating with reader device 120. For example, sensor control device 102 can be wirelessly activated before removal from its packaging, upon removal from its packaging, after removal from its packaging but prior to application to the user's body, upon application to the user's body, or after application to the user's body.
At 1302, sensor control device 102 is applied to the body of a user such that the adhesive patch is satisfactorily adhered to the user's skin with sensor 104 extending into tissue and in contact with bodily fluid (e.g., ISF, dermal fluid, and the like). At this point, it is desirable for sensor control device 102 to monitor for one or more wireless transmissions from reader device 120. Sensor control device 102 can be in either a power-off state or a low-power state, such as a sleep state, that consumes less power than the normal operation state.
If sensor control device 102 is in a powered-off state, then that state should be capable of supplying at least a minimal amount of current to communication circuitry 258 (operating according to the appropriate Bluetooth protocol) to allow monitoring for a wireless transmission from reader device 120. Accordingly, communication circuitry 258 can have a low-power function or state that consumes less power than the normal state of operation, and this low-power state can be used for monitoring for a first wireless transmission from reader device 120.
If the powered-off state is not capable of supplying sufficient current for monitoring for a wireless transmission because, for example, the power source is electrically disconnected, then sensor control device 102 is transitioned from the powered-off state to a low-power state where monitoring is possible. In some embodiments, the powered-off or the low-power state of sensor control device 102 does not permit the transmission of messages in order to save power.
At 1304, reader device 120 is activated (if not already) and the user initiates connection with sensor control device 102 by, for example, selecting an option to do so on the user interface of reader device 120. At 1306, the user brings reader device 120 into close proximity (e.g., less than 6 feet, less than 3 feet, less than 2 feet, less than 1 foot, or less than 6 inches, etc.) with sensor control device 102, if reader device 120 is not already in such a position.
In these embodiments, the initiation of a connection at step 1304 causes reader device 120 to begin sending wireless transmissions according to a Bluetooth protocol. In some of these embodiments, the wireless transmissions are sent in accordance with an advertising regimen of the BTLE protocol, and transmitted at the highest power level allowable by reader device 120. The advertising regimen is a link layer mode of BTLE, and is typically carried out while reader device 120 is in an advertising state by the performance of an advertising event, which can include the sending of one or more advertising request packets on one or more advertising channels (e.g., one, two, or three) of the link layer of the BTLE packet structure (e.g., protocol data unit (PDU) header, PDU payload, CRC). Each packet can be sent on each advertising channel at a specified time interval.
Each advertising packet can contain an advertising request, which is a predetermined string of bits, or bit code, that can be interpreted by sensor control device 102 as a request to initiate the communication session. An example of an advertising request is a packet data unit (PDU) type corresponding to a connectable directed advertising event (ADV_DIRECT_IND). ADV_DIRECT_IND is described in the incorporated Bluetooth specification, version 4.0, as a 0001 code appearing in the 4 most least significant bits (the PDU type) of the PDU header. In certain embodiments, for the connectable directed advertising packet, the time interval between the sending of consecutive requests on the same channel is 3.75 milliseconds (ms) or less, and these repeated transmissions can persist for a predetermined length of time, e.g., as long as about 1.28 seconds (s). If sent on two advertising channels provided by BTLE, the interval between consecutive requests on any channel will be about 1.375 ms or less and, if sent on three channels, the interval will be about 1.25 ms or less.
Other PDUs can be used as well, such as: ADV_IND, which can be a 0000 code corresponding to a connectable undirected event; ADV_NONCONN_IND, which can be a 0010 code corresponding to a non-connectable undirected event; and ADV_SCAN_IND, which can be a 0110 code corresponding to a scannable undirected event.
At 1307, sensor control device 102 detects the advertising message or sequence and, at 1308, demodulates the transmission to determine if an activation request is present. The determination of whether an activation request is present can be performed by processor 256 or communication circuitry 258 (e.g., a BTLE transceiver). If the activation request is present, sensor control device 102 can transmit an activation confirmation message at 1310. The activation confirmation message can be a predetermined bit code that is recognized by reader device 120 as confirmation that sensor control device 102 is ready to establish a connection. For example, the activation confirmation message can be a CONNECT_REQ (0101) or a SCAN_REQ (0011) PDU. In some embodiments, prior to transmitting the activation confirmation message, sensor control device 102 changes into a higher power mode of operation, such as a normal operation state, that enables the use of power to transmit messages. Upon receiving the activation confirmation message, reader device 120 can transition from the advertising state to the connection state according to the BTLE protocol.
If the activation request is not present, then, at 1311, sensor control device 102 can continue to monitor for another transmission sent according to an advertising feature of the BTLE protocol. In some embodiments, sensor control device 102 can wait a predetermined period of time, e.g., 2 to 3 seconds, before monitoring for another transmission.
The user continues to hold reader device 120 in close proximity with sensor control device 102 until reader device 120 indicates, at 1312, that a connection is being established or has been established. This indication can be a visual indication on a display of reader device 120, an audible indication (e.g., a beep, tone, jingle, etc.), a tactile indication (e.g., a vibration or series of vibrations), or any combination thereof. Reader device 120 can provide such an indication upon receiving the activation confirmation message from sensor control device 102. Reader device 120 and sensor control device 102 can then proceed with formally establishing a communication link or pairing and can begin the exchange of analyte data sensed from the body of the user.
At 1402, sensor control device 102 is placed in, or transitions to, a low-power receiving mode or state. As already stated herein, sensor control device 102 can be shipped in this state, or can be shipped in a fully powered-off state and transitioned into this state by the user, e.g., manually with a switch or other actuator, or automatically with a photo-sensor or magnetic sensor, etc.
At 1403, sensor control device 102 monitors for a Bluetooth transmission and, if one is received, determines if that transmission qualifies as an advertising message or sequence at 1404. This determination can be accomplished without demodulating the wireless transmission, and can be performed by processor 256 or communication circuitry 258. For example, if a sequence of two or more transmissions are received at the appropriate time interval (e.g., less than or equal to 3.75 ms) and at the appropriate frequency (e.g., approximately 2.4 Ghz), then processor 256 can assume that the transmissions are part of a direct advertising regimen according to the BTLE protocol. If the one or more transmissions do not qualify, then sensor control device 102 returns to monitoring for another wireless transmission, optionally by first waiting the predetermined period of time at 1405.
If the transmission or transmissions do qualify, then at 1406, processor 256 (through its programming) transitions sensor control device 102 to a higher power state that allows for the demodulation of one or more wireless transmissions and the sending of a response. This can be, for example, a normal operation state of sensor control device 102. At 1408, the next, or a subsequent, wireless transmission is demodulated by sensor control device 102 (e.g., by BTLE transceiver 258). At 1410, sensor control device 102 determines if the demodulated transmission includes an activation request. If it does not, then sensor control device 102 can return to the low-power state at 1402 (either before or after waiting an optional predetermined time at 1405), where it can then proceed to monitor for new wireless transmissions.
If the demodulated transmission does include the activation request, then sensor control device 102 transmits the activation confirmation message at 1412. Sensor control device 102 and reader device 120 can then proceed to finalize the pairing and/or otherwise continue with normal operation at 1414.
In another example embodiment, reader device 120 transmits advertising requests as part of a connectable directed advertising event with a maximum power level allowable by the reader device 120, which can be a smart phone. Sensor control device 102 receives one or more of these requests and changes state from a low power (e.g., storage) state to a higher power state (e.g., normal operation). Sensor control device 102 then begins advertising for a connection with reader device 120 according to any advertising regimen in the BTLE protocol (e.g., an advertising regimen that is not a connectable directed advertising event), and reader device 120 can receive the advertising requests and respond accordingly. Thus, in this embodiment, both sensor control device 102 and reader device 120 act as advertisers at some point. Reader device 120 acts as an advertiser to wake up device 102, and device 102 then acts as an advertiser to establish a connection with reader device 120.
Turning now to other embodiments, in some cases, to accomplish a connection of a power source in an electrical manner, another source of power may be required to operate the responsible circuitry. Embodiments of the systems, devices, and methods described herein provide for, among other things, the utilization of the power (or current) harnessed from multiple wireless RF communications, e.g., NFC communications, sent from reader device 120 to sensor control device 102 to drive the responsible connection circuitry. These multiple RF communications provide the power necessary to connect the power source or otherwise cause the source to supply the operating power to sensor electronics 250. In certain embodiments, this can entail harnessing sufficient power to enable processor 256 of sensor control device 102 to demodulate and interpret a wirelessly received transition command that instructs sensor control device 102 to transition from a low-power mode to a higher-power mode, e.g., from an inactive mode to an activate mode. Typically, the greater the efficiency of the sensor control device's power management circuitry 254, the lesser the number of RF communications that are required to successfully transition.
The use of multiple wireless RF communications provides greater power than just a single RF communication of the same type, which may be insufficient. The amount of power that is available in this RF “scavenging” process is dependent on a number of factors such as the antenna efficiency (e.g., tuning), the alignment of the RF fields (distance, position, and plane angle), and the power of the sending communication circuitry (e.g., the transmitter or transceiver) within the reader device.
As mentioned earlier, reader device 120 can be a dedicated-use type device that is designed for the primary (or sole) purpose of interfacing with sensor control device 102. Dedicated-use type reader devices 120 are typically, but not always, manufactured by the same entity that manufactures sensor control device 102. Because the manufacturers have control over the design of dedicated-use reader devices 120, they can be configured to transmit RF communications at a sufficiently high power level that enables sensor control device 102 to transition to a higher-power mode after receiving a minimal number of communications.
In other embodiments, however, reader devices 120 (including some dedicated-use devices) have more limited capabilities and transmit at lower power levels. One example is a multi-function smartphone, where the function of interfacing with sensor control device 102 is an ancillary one only fully implemented by those users that require it. Smartphones are designed to maximize battery life and limit the consumption of power by the secondary circuits such as the NFC communication circuitry that may be used to communicate with sensor control device 102. Due to size constraints, the smartphone may also have a smaller NFC antenna than that of a dedicated-use device. As a result, the amount of power that can be scavenged from each RF communication is limited, often severely. The systems, devices, and methods described herein, while not limited to such, are particularly suited for smartphones and other reader devices that send RF communications at a relatively low power.
Power management circuitry 254 can perform voltage level monitoring of power source 260, can monitor the level of charge stored within capacitive reservoirs 249 and 255, and can also include control circuitry for controlling whether power source 260 is supplying the operating power to the remainder of sensor electronics 250.
Control circuit 1600 can be responsive to a first control signal at an input 1602 (e.g., a connection command) that causes control circuit 1600 to connect power source 260 to the remaining sensor electronics 250. Control circuit 1600 can also be responsive to a second control signal at an input 1604 (e.g., a disconnection command) that causes control circuit 1600 to disconnect power source 260 from the remaining sensor electronics 250. These control signals can be generated by power management circuitry 254 or processor 256 using the power stored in capacitive reservoirs 249 and/or 255.
Turning now to detailed description of the RF power transfer techniques,
NFC is a technique for establishing radio communication between devices by touching them or bringing them into close proximity to each other (by way of a non-limiting example, any spaced relation up to about 1.5 meters (m)). NFC devices typically send communications by generating a magnetic field with an inductive antenna at a frequency around 13.56 MHz. This magnetic field induces current in a similar inductive antenna in the receiving NFC device, which can then be decoded to interpret the contents of the communication. NFC devices can be “active” or “passive” devices. Active devices typically include their own power source for generating voltage or current used to send NFC requests and responses. Passive devices typically do not include their own power source and respond to a received communication by using power scavenged from that communication.
The term “NFC” applies to a number of protocols (or standards) that set forth operating parameters, modulation schemes, coding, transfer speeds, frame format, and command definitions for NFC devices. The following is a non-exhaustive list of examples of these protocols, each of which (along with all of its sub-parts) is incorporated by reference herein in its entirety for all purposes: ECMA-340, ECMA-352, ISO/IEC 14443, ISO/IEC 15693, ISO/IEC 18000-3, ISO/IEC 18092, and ISO/IEC 21481.
The embodiments described herein can utilize any of the aforementioned NFC features and can utilize any NFC protocol for supplying power across link 140 regardless of whether that protocol is contained in the aforementioned list or otherwise in existence at the time of this filing. Communication protocols other than NFC can also be used for supplying power across link 140. For example, with supplemental power harnessing circuitry, Wi-Fi transmissions could be used to transfer power of link 140 to sensor control device 102.
Now referring back to
In another example, sensor control device 102 may have already been activated and applied to the user's body, and has instead entered a power conservation or sleep mode that disconnects power source 260 from a portion of sensor electronics 250 not directly responsible for analyte monitoring. In such an example the user may select an option to perform a scan of sensor control device 102 and retrieve the user's most current analyte data, which in turn initiates the sending of the NFC communications to “wake-up” sensor control device 102.
In
Sensor control device 102 receives the supply communication at 1730 (
Reader device 120 receives the NFC response at 1708 (
If a valid NFC response is received within the predetermined time limit, then reader device 120 sends a transition command at 1712. The transition command instructs sensor control device 102 to cause power source 260 to supply the operating power to sensor electronics 250. This can entail instructing sensor control device 102 to transition from the low-power mode to a higher power mode. The transition command can be an “activation command” that instructs sensor control device 102 to activate and began an initialization process to ready itself for use in collecting analyte data.
Referring back to
In another example, after recognizing that a transition command has been received, sensor control device 102 can forego determining whether sufficient charge is present (step 1735) and attempt to execute the command directly. Sensor control device 102 will either succeed or not depending on whether sufficient charge has been collected. Sensor control device 102 can then optionally perform the appropriate action described with respect to steps 1736 and 1738.
Reader device 120 monitors for receipt of confirmation that the transition command was executed at 1714 (
As mentioned, the communication containing the supply command is selected to result in a net power gain for sensor control device 102, i.e., the power required to read and react to the communication is less than the power conveyed to sensor control device 102 by its receipt. The action that the command instructs sensor control device 102 to take may not be a needed one at the point in time that it is sent by reader device 120. In other words, the command's execution may be considered to be a negligible artifact of this power supply technique. One example of a supply command is the inventory command set forth in ISO 15693-3, which instructs sensor control device 102 to perform the anti-collision sequence of that protocol. In ISO 15693, each NFC request contains flags, a command code, mandatory and optional parameter fields depending on the command, application data fields, and a cyclic redundancy check (CRC), while an NFC response contains similar fields but omits the command code. Sensor control device 102 can be designed to achieve net power gains from the other commands described in ISO 15693-3, which are reiterated in Table 1 below.
In the embodiment of method 1700 described with respect to
Furthermore, reader device 120 need not monitor for an NFC response to each supply command and can instead be programmed to send a specific number of supply commands in rapid succession. Reader device 120 can follow with a transition command and monitor for a successful response. The sending of the supply commands in rapid succession increases the likelihood of supplying sufficient power to sensor control device 102 while minimizing the length of the process, as it is desirable to avoid significant delays that are perceptible to the user. In one non-limiting example that was experimentally performed, four supply commands are sent at intervening intervals of 130 milliseconds (ms) with a transition command sent every 600 ms until confirmation of success is received. In another non-limiting example that was also experimentally performed, ten supply commands were sent in succession followed by a transition command. It was experimentally determined that ten supply commands provide sufficient margin to supply power across a wide range of commercially available smartphones under the most common conditions of alignment and separation forming the NFC link. Other examples include the sending of X supply commands prior to the sending of a transition command, where X is 2, 3, 5, 6, 7, 8, 9, 11, 12, and so forth, wherein each cycle of sending supply commands followed by a transition command can be repeated X times or as many times as desired until the desired transition is carried out.
Upon initiation of the RF carry power at T0, reader device 120 begins sending commands and VCC begins to rise from a zero (or near-zero) value to a regulated maximum voltage. A communication containing supply command 1806-1 is received by sensor control device 102 at T1. Sensor control device 102 demodulates the communication, interprets command 1806-1, and attempts to generate and send a response within predetermined time limit 1811-1. But as indicated by the precipitous drop in VCC that occurs after receipt of supply command 1806-1, sensor control device 102 has insufficient power to send any response, as indicated by the response failure 1807 at TR1.
At T2, reader device 120 sends a second supply command 1806-2. Here, sensor control device 102 again experiences a drop in VCC, although this drop is of less magnitude and duration because of the partial charging of reservoirs 249 and 255, and sensor control device 102 is able to send a delayed response 1808-2 at TR2. Because this delayed response 1808-2 is not received by reader device 120 within the predetermined time limit 1811-2, reader device 120 proceeds to send additional supply commands.
At TN, an Nth supply command 1806-N is received by sensor control device 102. The VCC drop here is of even less magnitude and less duration than the ones occurring at T1 and T2, and at TRN sensor control device 102 sends a valid response 1808-N within the predetermined time limit 1811-N.
Upon confirming this valid response 1808-N, reader device 120 sends a transition command 1810 that is received by sensor control device 102 at TN+1. Sufficient charge is present to permit sensor control device 102 to perform a successful mode transition and sensor control device 102 sends a response 1812 with confirmation of the transition at TRN+1. Because of the higher power requirement to respond to transition command 1810, the VCC drop is greater and longer than that experienced responding to the preceding supply command 1806-N.
Also provided herein are adaptive techniques that can adjust the amount of power supply to sensor control device 102 based upon one or more failures to transition device 102 out of a low-power mode.
At 1902, reader device 120 sends a first multitude of successive NFC communications containing supply commands to sensor control device 102. This first multitude of communications is selected so that it is capable of conveying a first net power to sensor control device 102. Every one of the first multitude of communications can contain a supply command, or one of the communications, such as the last communication, can contain a transition command. In this and any embodiment described herein, if the sensor control device 102 can interpret and react to a transition command while maintaining a net power gain, then all supply commands can be transition commands. At 1904, reader device 120 monitors to determine whether a valid response was received from sensor control device 102 to any of the first multitude of communications, or alternatively to any transition command that was sent.
If a valid response was received to one of the supply commands, and no transition command was sent, then reader device 120 sends a transition command at 1906 and determines whether a valid response was received to the transition command at 1908. If a valid response was received then reader device 120 can exit the software routine and optionally notify the user that sensor control device 102 successfully transitioned to a higher power mode (e.g., was activated) at 1910. If no valid response was received to one of the supply commands (see 1904) or if no valid response was received to the transition command (see 1908), then reader device 120 proceeds to 1912, where another multitude of successive NFC communications is sent that is capable of conveying a net power that is the same as or greater than the net power of the multitude of communications that was sent immediately prior, which in this example was the first multitude.
The net power conveyed to sensor control device 102 can be increased in a number of ways. For example, a greater number of communications can be sent over the same time period, or substantially the same time period, as was used with the preceding multitude of communications. Alternatively, the same number of communications can be sent over a shorter time period than was used with the preceding multitude of communications. This approach could be used if sensor control device 102 was susceptible to leakage of the received power. Also, the same number of communications can be sent over the same time period as was used with the first multitude, except each communication can be sent at a higher power. In yet another example, a type of supply command can be used that is different from the supply command in the preceding multitude an effort to adaptively locate the type of supply command that most efficiently transfers power to sensor control device 102. A combination of any two or more of the aforementioned approaches can also be used.
At 1914, reader device 120 determines whether a valid response was received to any of the most recently transmitted multitude of communications, similar to step 1904. If so, then reader device 120 proceeds to 1906 and executes it in a similar fashion to that already described. If no valid response was received at 1914, then reader device 120 proceeds to 1916 and determines if the iterative process can proceed. Factors that can be used in this assessment can include whether reader device 120 is already sending communications at a maximum transmit power, whether a maximum number of attempts has been reached, or whether a maximum duration of time for the entire process has been reached. If the process can proceed then reader device 120 continues to 1912 and sends yet another (in this example a third) multitude of communications capable of conveying an even higher net power. If a maximum has been reached as determined at 1916, then reader device 120 can exit the routine and optionally notify the user at 1918.
Reader device 120, when in the form of a smartphone, can perform the methods described herein under the control of a downloadable software application executed by applications processor 204. The smartphone application can be generic to different smartphone models and can execute an adaptive process like that of method 1900 to determine the optimum combination of supply command timing, supply command type, or number of supply command communications, to supply power to each different smartphone model.
Such an adaptive process could be executed upon installation of the software application, periodically in association with a scan of sensor control device 102, or during a scan as part of a retry process. If sensor control device 102 is already activated, then reader device 120 can send a notification to sensor control device 102 that it is performing the optimization process, at which point sensor control device 102 can scavenge power from the subsequent supply commands and transmit a notification back to reader device 120 as to the amount of power successfully scavenged. Reader device 120 can then attempt different combinations of the aforementioned variables, each time receiving an indication from sensor control device 102 as to the amount of power scavenged. The optimal combination can then be used for accomplishing future mode transitions with that sensor control device 102 or a subsequent one, and can be communicated by reader device 120 back to the manufacturer for future reference, such as over an internet data connection.
Although many of the embodiments described herein are done so in the context of transitioning from a lower power mode to a higher power mode with the aid of a transition command, the power scavenging technique can be used in other contexts as well. For example, these embodiments can be used to prolong the battery life by sending supply commands even after sensor control device 102 has transitioned to the higher power mode (activated). Supply commands can be sent automatically during every communication session between reader device 120 and sensor control device 102, or whenever reader device 120 sends a command known to require greater power consumption than usual. Reader device 120 may be programmed to send supply commands whenever a predetermined subset of NFC commands are transmitted (e.g., an NFC command to perform a scan of the user's analyte level, process the results, and transmit back to reader device 120 is one such command that consumes a large amount of power). Reader device 120 can also send supply commands whenever they are requested by sensor control device 102 during a communication session.
Unless otherwise noted herein, each of the methods steps described in the aforementioned embodiments can be performed by processor 256 or communication circuitry 258 (e.g., a transceiver, or a separate receiver or transmitter). Steps performed by these components can be done at the direction of software programming executed by processor 256.
While many of the embodiments described herein relate to activation of a device, these embodiments are not mutually exclusive. Stated differently, a subject device can include any combination of one or more of the embodiments described herein, including multiple different mechanisms for activating that device.
Generally, embodiments of the present disclosure are used with in vivo systems, devices, and methods for detecting at least one analyte, such as glucose, in body fluid (e.g., transcutaneously, subcutaneously within the ISF or blood, or within the dermal fluid of the dermal layer). In vivo analyte monitoring systems can be differentiated from “in vitro” systems that contact a biological sample outside of the body (or rather “ex vivo”) and that typically include a meter device that has a port for receiving an analyte test strip carrying the biological sample of the user, which can be analyzed to determine the user's blood sugar level. Many in vitro systems require a “finger stick” to obtain the biological sample. In vivo analyte monitoring systems, however, can operate without the need for finger stick calibration.
Many embodiments include in vivo analyte sensors arranged so that at least a portion of the sensor is positioned in the body of a user to obtain information about at least one analyte of the body. However, the embodiments described herein can be used with in vivo analyte monitoring systems that incorporate in vitro capability, as well has purely in vitro or ex vivo analyte monitoring systems. Furthermore, the embodiments described herein can be used in systems, devices, and methods outside of the analyte monitoring field, either in other medical device fields, or any other field that requires the supply of power to one device from another.
Sensor Configurations
Analytes that may be monitored with system 100 include, but are not limited to, acetyl choline, amylase, bilirubin, cholesterol, chorionic gonadotropin, glycosylated hemoglobin (HbAlc), creatine kinase (e.g., CK-MB), creatine, creatinine, DNA, fructosamine, glucose, glucose derivatives, glutamine, growth hormones, hormones, ketones, ketone bodies, lactate, oxygen, peroxide, prostate-specific antigen, prothrombin, RNA, thyroid stimulating hormone, and troponin. The concentration of drugs, such as, for example, antibiotics (e.g., gentamicin, vancomycin, and the like), digitoxin, digoxin, drugs of abuse, theophylline, and warfarin, may also be monitored. In embodiments that monitor more than one analyte, the analytes may be monitored at the same or different times with a single sensor or with a plurality of sensors which may use the same electronics (e.g., simultaneously) or with different electronics of sensor control device 102.
Analyte sensor 104 may include an analyte-responsive enzyme to provide a sensing element. Some analytes, such as oxygen, can be directly electrooxidized or electroreduced on sensor 104, and more specifically at least on a working electrode (not shown) of a sensor 104. Other analytes, such as glucose and lactate, require the presence of at least one electron transfer agent and/or at least one catalyst to facilitate the electrooxidation or electroreduction of the analyte. Catalysts may also be used for those analytes, such as oxygen, that can be directly electrooxidized or electroreduced on the working electrode. For these analytes, each working electrode includes a sensing element proximate to or on a surface of a working electrode. In many embodiments, a sensing element is formed near or on only a small portion of at least a working electrode.
Each sensing element includes one or more components constructed to facilitate the electrochemical oxidation or reduction of the analyte. The sensing element may include, for example, a catalyst to catalyze a reaction of the analyte and produce a response at the working electrode, an electron transfer agent to transfer electrons between the analyte and the working electrode (or other component), or both.
Electron transfer agents that may be employed are electroreducible and electrooxidizable ions or molecules having redox potentials that are a few hundred millivolts above or below the redox potential of the standard calomel electrode (SCE). The electron transfer agent may be organic, organometallic, or inorganic. Examples of organic redox species are quinones and species that in their oxidized state have quinoid structures, such as Nile blue and indophenol. Examples of organometallic redox species are metallocenes including ferrocene. Examples of inorganic redox species are hexacyanoferrate (III), ruthenium hexamine, etc. Additional examples include those described in U.S. Pat. Nos. 6,736,957, 7,501,053 and 7,754,093, the disclosures of each of which are incorporated herein by reference in their entirety.
In certain embodiments, electron transfer agents have structures or charges which prevent or substantially reduce the diffusional loss of the electron transfer agent during the period of time that the sample is being analyzed. For example, electron transfer agents include but are not limited to a redox species, e.g., bound to a polymer which can in turn be disposed on or near the working electrode. The bond between the redox species and the polymer may be covalent, coordinative, or ionic. Although any organic, organometallic or inorganic redox species may be bound to a polymer and used as an electron transfer agent, in certain embodiments the redox species is a transition metal compound or complex, e.g., osmium, ruthenium, iron, and cobalt compounds or complexes. It will be recognized that many redox species described for use with a polymeric component may also be used, without a polymeric component.
Embodiments of polymeric electron transfer agents may contain a redox species covalently bound in a polymeric composition. An example of this type of mediator is poly(vinylferrocene). Another type of electron transfer agent contains an ionically-bound redox species. This type of mediator may include a charged polymer coupled to an oppositely charged redox species. Examples of this type of mediator include a negatively charged polymer coupled to a positively charged redox species such as an osmium or ruthenium polypyridyl cation.
Another example of an ionically-bound mediator is a positively charged polymer including quaternized poly (4-vinyl pyridine) or poly(1-vinyl imidazole) coupled to a negatively charged redox species such as ferricyanide or ferrocyanide. In other embodiments, electron transfer agents include a redox species coordinatively bound to a polymer. For example, the mediator may be formed by coordination of an osmium or cobalt 2,2′-bipyridyl complex to poly(1-vinyl imidazole) or poly(4-vinyl pyridine).
Suitable electron transfer agents are osmium transition metal complexes with one or more ligands, each ligand having a nitrogen-containing heterocycle such as 2,2′-bipyridine, 1,10-phenanthroline, 1-methyl, 2-pyridyl biimidazole, or derivatives thereof. The electron transfer agents may also have one or more ligands covalently bound in a polymer, each ligand having at least one nitrogen-containing heterocycle, such as pyridine, imidazole, or derivatives thereof. One example of an electron transfer agent includes (a) a polymer or copolymer having pyridine or imidazole functional groups and (b) osmium cations complexed with two ligands, each ligand containing 2,2′-bipyridine, 1,10-phenanthroline, or derivatives thereof, the two ligands not necessarily being the same. Some derivatives of 2,2′-bipyridine for complexation with the osmium cation include but are not limited to 4,4′-dimethyl-2,2′-bipyridine and mono-, di-, and polyalkoxy-2,2′-bipyridines, including 4,4′-dimethoxy-2,2′-bipyridine. Derivatives of 1,10-phenanthroline for complexation with the osmium cation include but are not limited to 4,7-dimethyl-1,10-phenanthroline and mono, di-, and polyalkoxy-1,10-phenanthrolines, such as 4,7-dimethoxy-1,10-phenanthroline. Polymers for complexation with the osmium cation include but are not limited to polymers and copolymers of poly(1-vinyl imidazole) (referred to as “PVI”) and poly(4-vinyl pyridine) (referred to as “PVP”). Suitable copolymer substituents of poly(1-vinyl imidazole) include acrylonitrile, acrylamide, and substituted or quaternized N-vinyl imidazole, e.g., electron transfer agents with osmium complexed to a polymer or copolymer of poly(l-vinyl imidazole).
Embodiments may employ electron transfer agents having a redox potential ranging from about −200 mV to about +200 mV versus the standard calomel electrode (SCE). The sensing elements may also include a catalyst which is capable of catalyzing a reaction of the analyte. The catalyst may also, in some embodiments, act as an electron transfer agent. One example of a suitable catalyst is an enzyme which catalyzes a reaction of the analyte. For example, a catalyst, including a glucose oxidase, glucose dehydrogenase (e.g., pyrroloquinoline quinone (PQQ), dependent glucose dehydrogenase, flavine adenine dinucleotide (FAD) dependent glucose dehydrogenase, or nicotinamide adenine dinucleotide (NAD) dependent glucose dehydrogenase), may be used when the analyte of interest is glucose. A lactate oxidase or lactate dehydrogenase may be used when the analyte of interest is lactate. Laccase may be used when the analyte of interest is oxygen or when oxygen is generated or consumed in response to a reaction of the analyte.
In certain embodiments, a catalyst may be attached to a polymer, cross linking the catalyst with another electron transfer agent, which, as described above, may be polymeric. A second catalyst may also be used in certain embodiments. This second catalyst may be used to catalyze a reaction of a product compound resulting from the catalyzed reaction of the analyte. The second catalyst may operate with an electron transfer agent to electrolyze the product compound to generate a signal at the working electrode. Alternatively, a second catalyst may be provided in an interferent-eliminating layer to catalyze reactions that remove interferents.
In certain embodiments, the sensor works at a low oxidizing potential, e.g., a potential of about +40 mV vs. Ag/AgCl. These sensing elements use, for example, an osmium (Os)-based mediator constructed for low potential operation. Accordingly, in certain embodiments the sensing elements are redox active components that include: (1) osmium-based mediator molecules that include (bidente) ligands, and (2) glucose oxidase enzyme molecules. These two constituents are combined together in the sensing elements of the sensor.
A number of embodiments of sensor configurations that may be used in system 100 are described in Int'l Publication No. WO 2012/174538, titled “Connectors for Making Connections between Analyte Sensors and Other Devices,” and also in U.S. Pat. No. 8,435,682, titled “Biological Fuel Cell and Methods,” both of which are incorporated by reference herein in their entirety for all purposes. Particular attention is drawn to paragraphs 121-145 of the '528 Publication, several of which are reproduced herein.
All features, elements, components, functions, and steps described with respect to any embodiment provided herein are intended to be freely combinable and substitutable with those from any other embodiment. If a certain feature, element, component, function, or step is described with respect to only one embodiment, then it should be understood that that feature, element, component, function, or step can be used with every other embodiment described herein unless explicitly stated otherwise. This paragraph therefore serves as antecedent basis and written support for the introduction of claims, at any time, that combine features, elements, components, functions, and steps from different embodiments, or that substitute features, elements, components, functions, and steps from one embodiment with those of another, even if the following description does not explicitly state, in a particular instance, that such combinations or substitutions are possible. Express recitation of every possible combination and substitution is overly burdensome, especially given that the permissibility of each and every such combination and substitution will be readily recognized by those of ordinary skill in the art upon reading this description.
In many instances, entities are described herein as being coupled to other entities. It should be understood that the terms “coupled” and “connected” (or any of their forms) are used interchangeably herein and, in both cases, are generic to the direct coupling of two entities (without any non-negligible (e.g., parasitic) intervening entities) and the indirect coupling of two entities (with one or more non-negligible intervening entities). Where entities are shown as being directly coupled together, or described as coupled together without description of any intervening entity, it should be understood that those entities can be indirectly coupled together as well unless the context clearly dictates otherwise.
As used herein and in the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.
While the embodiments are susceptible to various modifications and alternative forms, specific examples thereof have been shown in the drawings and are herein described in detail. It should be understood, however, that these embodiments are not to be limited to the particular form disclosed, but to the contrary, these embodiments are to cover all modifications, equivalents, and alternatives falling within the spirit of the disclosure. Furthermore, any features, functions, steps, or elements of the embodiments may be recited in or added to the claims, as well as negative limitations that define the inventive scope of the claims by features, functions, steps, or elements that are not within that scope.
The present application is a continuation of U.S. patent application Ser. No. 14/265,026, filed Apr. 29, 2014, which claims the benefit of and priority to U.S. Provisional Patent Application No. 61/973,775, filed Apr. 1, 2014, U.S. Provisional Patent Application No. 61/896,578, filed Oct. 28, 2013, and U.S. Provisional Patent Application No. 61/817,839, filed Apr. 30, 2013, all of which are incorporated by reference herein in their entireties for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4545382 | Higgins et al. | Oct 1985 | A |
| 4711245 | Higgins et al. | Dec 1987 | A |
| 5262035 | Gregg et al. | Nov 1993 | A |
| 5262305 | Heller et al. | Nov 1993 | A |
| 5264104 | Gregg et al. | Nov 1993 | A |
| 5267152 | Yang et al. | Nov 1993 | A |
| 5320715 | Berg | Jun 1994 | A |
| 5356786 | Heller et al. | Oct 1994 | A |
| 5509410 | Hill et al. | Apr 1996 | A |
| 5543326 | Heller et al. | Aug 1996 | A |
| 5593852 | Heller et al. | Jan 1997 | A |
| 5601435 | Quy | Feb 1997 | A |
| 5628890 | Carter et al. | May 1997 | A |
| 5820551 | Hill et al. | Oct 1998 | A |
| 5822715 | Worthington et al. | Oct 1998 | A |
| 5899855 | Brown | May 1999 | A |
| 5918603 | Brown | Jul 1999 | A |
| 6071391 | Gotoh et al. | Jun 2000 | A |
| 6103033 | Say et al. | Aug 2000 | A |
| 6120676 | Heller et al. | Sep 2000 | A |
| 6121009 | Heller et al. | Sep 2000 | A |
| 6134461 | Say et al. | Oct 2000 | A |
| 6143164 | Hsieh et al. | Nov 2000 | A |
| 6144837 | Quy | Nov 2000 | A |
| 6161095 | Brown | Dec 2000 | A |
| 6175752 | Say et al. | Jan 2001 | B1 |
| 6270455 | Brown | Aug 2001 | B1 |
| 6284478 | Heller et al. | Sep 2001 | B1 |
| 6299757 | Feldman et al. | Oct 2001 | B1 |
| 6338790 | Feldman et al. | Jan 2002 | B1 |
| 6377894 | Deweese et al. | Apr 2002 | B1 |
| 6461496 | Feldman et al. | Oct 2002 | B1 |
| 6503381 | Gotoh et al. | Jan 2003 | B1 |
| 6514460 | Fendrock | Feb 2003 | B1 |
| 6514718 | Heller et al. | Feb 2003 | B2 |
| 6540891 | Stewart et al. | Apr 2003 | B1 |
| 6560471 | Heller et al. | May 2003 | B1 |
| 6579690 | Bonnecaze et al. | Jun 2003 | B1 |
| 6591125 | Buse et al. | Jul 2003 | B1 |
| 6592745 | Feldman et al. | Jul 2003 | B1 |
| 6600997 | Deweese et al. | Jul 2003 | B2 |
| 6605200 | Mao et al. | Aug 2003 | B1 |
| 6605201 | Mao et al. | Aug 2003 | B1 |
| 6616819 | Liamos et al. | Sep 2003 | B1 |
| 6618934 | Feldman et al. | Sep 2003 | B1 |
| 6650471 | Doi | Nov 2003 | B2 |
| 6654625 | Say et al. | Nov 2003 | B1 |
| 6676816 | Mao et al. | Jan 2004 | B2 |
| 6730200 | Stewart et al. | May 2004 | B1 |
| 6736957 | Forrow et al. | May 2004 | B1 |
| 6746582 | Heller et al. | Jun 2004 | B2 |
| 6749740 | Liamos et al. | Jun 2004 | B2 |
| 6764581 | Forrow et al. | Jul 2004 | B1 |
| 6773671 | Lewis et al. | Aug 2004 | B1 |
| 6881551 | Heller et al. | Apr 2005 | B2 |
| 6893545 | Gotoh et al. | May 2005 | B2 |
| 6932892 | Chen et al. | Aug 2005 | B2 |
| 6932894 | Mao et al. | Aug 2005 | B2 |
| 6942518 | Liamos et al. | Sep 2005 | B2 |
| 7041468 | Drucker et al. | May 2006 | B2 |
| 7167818 | Brown | Jan 2007 | B2 |
| 7291497 | Holmes et al. | Nov 2007 | B2 |
| 7299082 | Feldman et al. | Nov 2007 | B2 |
| 7418285 | Ghesquiere et al. | Aug 2008 | B2 |
| 7501053 | Karinka et al. | Mar 2009 | B2 |
| 7545272 | Goodnow et al. | Jun 2009 | B2 |
| 7722536 | Goodnow | May 2010 | B2 |
| 7749740 | Eiteman et al. | Jul 2010 | B2 |
| 7754093 | Forrow et al. | Jul 2010 | B2 |
| 7768408 | Reggiardo et al. | Aug 2010 | B2 |
| 7782192 | Jeckelmann et al. | Aug 2010 | B2 |
| 7801582 | Peyser | Sep 2010 | B2 |
| 7811231 | Jin et al. | Oct 2010 | B2 |
| 7866026 | Wang et al. | Jan 2011 | B1 |
| 8066639 | Nelson et al. | Nov 2011 | B2 |
| 8219173 | Budiman et al. | Jul 2012 | B2 |
| 8346335 | Harper et al. | Jan 2013 | B2 |
| 8372351 | Ow-Wing | Feb 2013 | B2 |
| 8435682 | Heller | May 2013 | B2 |
| 8497777 | Harper | Jul 2013 | B2 |
| 8514086 | Harper et al. | Aug 2013 | B2 |
| 8515518 | Ouyang et al. | Aug 2013 | B2 |
| 8595607 | Nekoomaram et al. | Nov 2013 | B2 |
| 8601465 | Bernstein et al. | Dec 2013 | B2 |
| 8764657 | Curry et al. | Jul 2014 | B2 |
| 8771183 | Sloan | Jul 2014 | B2 |
| 8815154 | List et al. | Aug 2014 | B2 |
| 8816862 | Harper et al. | Aug 2014 | B2 |
| 8828330 | Galasso | Sep 2014 | B2 |
| 9295784 | Eggert et al. | Mar 2016 | B2 |
| 20040118704 | Wang et al. | Jun 2004 | A1 |
| 20040186365 | Jin et al. | Sep 2004 | A1 |
| 20050182306 | Sloan | Aug 2005 | A1 |
| 20050261556 | Such | Nov 2005 | A1 |
| 20060025662 | Buse et al. | Feb 2006 | A1 |
| 20060091006 | Wang et al. | May 2006 | A1 |
| 20060166629 | Reggiardo | Jul 2006 | A1 |
| 20060193375 | Lee | Aug 2006 | A1 |
| 20070056858 | Chen et al. | Mar 2007 | A1 |
| 20070068807 | Feldman et al. | Mar 2007 | A1 |
| 20070095661 | Wang et al. | May 2007 | A1 |
| 20070102649 | Colvin et al. | May 2007 | A1 |
| 20070108048 | Wang et al. | May 2007 | A1 |
| 20070199818 | Petyt et al. | Aug 2007 | A1 |
| 20070227911 | Wang et al. | Oct 2007 | A1 |
| 20070232877 | He | Oct 2007 | A1 |
| 20070233013 | Schoenberg | Oct 2007 | A1 |
| 20080064937 | McGarraugh et al. | Mar 2008 | A1 |
| 20080066305 | Wang et al. | Mar 2008 | A1 |
| 20080081977 | Hayter et al. | Apr 2008 | A1 |
| 20080102441 | Chen et al. | May 2008 | A1 |
| 20080119705 | Patel et al. | May 2008 | A1 |
| 20080129486 | Jeckelmann et al. | Jun 2008 | A1 |
| 20080148873 | Wang | Jun 2008 | A1 |
| 20080154101 | Jain et al. | Jun 2008 | A1 |
| 20080161666 | Feldman et al. | Jul 2008 | A1 |
| 20080255434 | Hayter et al. | Oct 2008 | A1 |
| 20080255437 | Hayter | Oct 2008 | A1 |
| 20080255808 | Hayter | Oct 2008 | A1 |
| 20080256048 | Hayter | Oct 2008 | A1 |
| 20080267823 | Wang et al. | Oct 2008 | A1 |
| 20080281179 | Fennell et al. | Nov 2008 | A1 |
| 20080287763 | Hayter | Nov 2008 | A1 |
| 20080288180 | Hayter et al. | Nov 2008 | A1 |
| 20080288204 | Hayter et al. | Nov 2008 | A1 |
| 20080312842 | Hayter et al. | Dec 2008 | A1 |
| 20080312844 | Hayter et al. | Dec 2008 | A1 |
| 20080312845 | Hayter et al. | Dec 2008 | A1 |
| 20090005665 | Hayter et al. | Jan 2009 | A1 |
| 20090006034 | Hayter et al. | Jan 2009 | A1 |
| 20090033482 | Hayter et al. | Feb 2009 | A1 |
| 20090036760 | Hayter | Feb 2009 | A1 |
| 20090054748 | Feldman | Feb 2009 | A1 |
| 20090108992 | Shafer | Apr 2009 | A1 |
| 20090294277 | Thomas et al. | Dec 2009 | A1 |
| 20100094110 | Heller et al. | Apr 2010 | A1 |
| 20100094111 | Heller et al. | Apr 2010 | A1 |
| 20100094112 | Heller et al. | Apr 2010 | A1 |
| 20100198034 | Thomas et al. | Aug 2010 | A1 |
| 20100198142 | Sloan et al. | Aug 2010 | A1 |
| 20100204557 | Kiaie et al. | Aug 2010 | A1 |
| 20100213057 | Feldman et al. | Aug 2010 | A1 |
| 20100230285 | Hoss et al. | Sep 2010 | A1 |
| 20100270150 | Wang et al. | Oct 2010 | A1 |
| 20100324392 | Yee et al. | Dec 2010 | A1 |
| 20100326842 | Mazza et al. | Dec 2010 | A1 |
| 20110021889 | Hoss et al. | Jan 2011 | A1 |
| 20110082484 | Saravia et al. | Apr 2011 | A1 |
| 20110106126 | Love et al. | May 2011 | A1 |
| 20110190603 | Stafford | Aug 2011 | A1 |
| 20110191044 | Stafford | Aug 2011 | A1 |
| 20110213225 | Bernstein | Sep 2011 | A1 |
| 20110256024 | Cole et al. | Oct 2011 | A1 |
| 20110257495 | Hoss et al. | Oct 2011 | A1 |
| 20110282175 | Geissler et al. | Nov 2011 | A1 |
| 20110288574 | Curry et al. | Nov 2011 | A1 |
| 20110319729 | Donnay et al. | Dec 2011 | A1 |
| 20120010642 | Lee et al. | Jan 2012 | A1 |
| 20120078071 | Bohm et al. | Mar 2012 | A1 |
| 20120190941 | Donnay et al. | Jul 2012 | A1 |
| 20120190942 | Donnay et al. | Jul 2012 | A1 |
| 20120190943 | Donnay et al. | Jul 2012 | A1 |
| 20120197098 | Donnay et al. | Aug 2012 | A1 |
| 20120197222 | Donnay et al. | Aug 2012 | A1 |
| 20130040573 | Hillyard et al. | Feb 2013 | A1 |
| 20130059541 | Sloan et al. | Mar 2013 | A1 |
| 20130150691 | Pace et al. | Jun 2013 | A1 |
| 20130150697 | Imai et al. | Jun 2013 | A1 |
| 20140031655 | Stafford | Jan 2014 | A1 |
| 20140275898 | Taub et al. | Sep 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 2005074161 | Aug 2005 | WO |
| WO 2008129532 | Oct 2008 | WO |
| WO 2012160163 | Nov 2012 | WO |
| WO 2005112744 | Dec 2012 | WO |
| WO 2012174538 | Dec 2012 | WO |
| WO 2014179343 | Nov 2014 | WO |
| Entry |
|---|
| JP, 2019-142804 Office Action, dated Sep. 2, 2020. |
| Bluetooth Low Energy Technology Training, All Hands Meeting, Apr. 19-22, 2010. |
| Specification of the Bluetooth System, vol. 0—Master Table of Contents & Compliance Requirements, Covered Core Package version: 4.0, Jun. 30, 2010. |
| Specification of the Bluetooth System, vol. 1—Architecture & Terminology Overview, Covered Core Package version: 4.0, Jun. 30, 2010. |
| Specification of the Bluetooth System, vol. 2—Core System Package [BR/EDR Controller volume], Covered Core Package version: 4.0, Jun. 30, 2010. |
| Specification of the Bluetooth System, vol. 3—Core System Package [Host volume], Covered Core Package version: 4.0, Jun. 30, 2010. |
| Specification of the Bluetooth System, vol. 4—Host Controller Interface [Transport Layer], Covered Core Package version: 4.0, Jun. 30, 2010. |
| Specification of the Bluetooth System, vol. 5—Core System Package [AMP Controller volume], Covered Core Package version: 4.0, Jun. 30, 2010. |
| Specification of the Bluetooth System, vol. 6—Core System Package [Low Energy Controller volume], Covered Core Package version: 4.0, Jun. 30, 2010. |
| AU, 2014260023 First Examination Report, dated Jan. 31, 2018. |
| CN, 201480024659.9 Office Action, dated Jun. 1, 2017. |
| CN, 201480024659.9 Second Office Action, dated Jan. 4, 2018. |
| EP, 14792119.1 Supplementary Search Report, dated Dec. 6, 2016. |
| WO, PCT/US2014/035926 ISR and Written Opinion, dated Sep. 25, 2014. |
| Number | Date | Country | |
|---|---|---|---|
| 20190142315 A1 | May 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61973775 | Apr 2014 | US | |
| 61896578 | Oct 2013 | US | |
| 61817839 | Apr 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14265026 | Apr 2014 | US |
| Child | 16201688 | US |
