Close proximity communication device and methods

Description

BACKGROUND

Analyte, e.g., glucose monitoring systems including continuous and discrete monitoring systems generally include a small, lightweight battery powered and microprocessor controlled system which is configured to detect signals proportional to the corresponding measured glucose levels using an electrometer. RF signals may be used to transmit the collected data. One aspect of certain analyte monitoring systems include a transcutaneous or subcutaneous analyte sensor configuration which is, for example, at least partially positioned through the skin layer of a subject whose analyte level is to be monitored. The sensor may use a two or three-electrode (work, reference and counter electrodes) configuration driven by a controlled potential (potentiostat) analog circuit connected through a contact system.

An analyte sensor may be configured so that a portion thereof is placed under the skin of the patient so as to contact analyte of the patient, and another portion or segment of the analyte sensor may be in communication with the transmitter unit. The transmitter unit may be configured to transmit the analyte levels detected by the sensor over a wireless communication link such as an RF (radio frequency) communication link to a receiver/monitor unit. The receiver/monitor unit may perform data analysis, among other functions, on the received analyte levels to generate information pertaining to the monitored analyte levels.

Transmission of control or command data over wireless communication link is often constrained to occur within a substantially short time duration. In turn, the time constraint in data communication imposes limits on the type and size of data that may be transmitted during the transmission time period.

In view of the foregoing, it would be desirable to have a method and apparatus for optimizing the RF communication link between two or more communication devices, for example, in a medical communication system.

SUMMARY

Devices and methods for analyte monitoring, e.g., glucose monitoring, and/or therapy management system including, for example, medication infusion device are provided. Embodiments include transmitting information from a first location to a second, e.g., using a telemetry system such as RF telemetry. Systems herein include continuous analyte monitoring systems, discrete analyte monitoring system, and therapy management systems.

These and other objects, features and advantages of the present disclosure will become more fully apparent from the following detailed description of the embodiments, the appended claims and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of a data monitoring and management system for practicing one or more embodiments of the present disclosure;

FIG. 2 is a block diagram of the transmitter unit of the data monitoring and management system shown in FIG. 1 in accordance with one embodiment of the present disclosure;

FIG. 3 is a block diagram of the receiver/monitor unit of the data monitoring and management system shown in FIG. 1 in accordance with one embodiment of the present disclosure;

FIG. 4 is a flowchart illustrating data packet procedure including rolling data for transmission in accordance with one embodiment of the present disclosure;

FIG. 5 is a flowchart illustrating data processing of the received data packet including the rolling data in accordance with one embodiment of the present disclosure;

FIG. 6 is a block diagram illustrating the sensor unit and the transmitter unit of the data monitoring and management system of FIG. 1 in accordance with one embodiment of the present disclosure;

FIG. 8 is a flowchart illustrating the pairing or synchronization routine in the data monitoring and management system of FIG. 1 in accordance with one embodiment of the present disclosure;

FIG. 9 is a flowchart illustrating the pairing or synchronization routine in the data monitoring and management system of FIG. 1 in accordance with another embodiment of the present disclosure;

FIG. 10 is a flowchart illustrating the power supply determination in the data monitoring and management system of FIG. 1 in accordance with one embodiment of the present disclosure;

FIG. 12 illustrates a data format of a close proximity data packet sent by a controller, for use in one or more embodiments of the present disclosure;

FIG. 13 is a block diagram representation of a close proximity detection logic of the transmitter unit 620 in one or more embodiments of the present disclosure; and

FIG. 14 is a flow chart illustrating close proximity detection logic in one or more embodiments of the present disclosure.

DETAILED DESCRIPTION

As summarized above and as described in further detail below, in accordance with the various embodiments of the present disclosure, there is provided a method and system for positioning a controller unit within a transmission range for close proximity communication, transmitting one or more predefined close proximity commands, and receiving a response packet in response to the transmitted one or more predefined close proximity commands.

FIG. 1 illustrates a data monitoring and management system such as, for example, analyte (e.g., glucose) monitoring system 100 in accordance with one embodiment of the present disclosure. The subject invention is further described primarily with respect to a glucose monitoring system for convenience and such description is in no way intended to limit the scope of the invention. It is to be understood that the analyte monitoring system may be configured to monitor a variety of analytes, e.g., lactate, and the like.

Analytes that may be monitored include, for example, acetyl choline, amylase, bilirubin, cholesterol, chorionic gonadotropin, creatine kinase (e.g., CK-MB), creatine, DNA, fructosamine, glucose, glutamine, growth hormones, hormones, ketones, lactate, 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. More than one analyte may be monitored by a single system, e.g. a single analyte sensor.

The analyte monitoring system 100 includes a sensor unit 101, a transmitter unit 102 coupleable to the sensor unit 101, and a primary receiver unit 104 which is configured to communicate with the transmitter unit 102 via a bidirectional communication link 103. The primary receiver unit 104 may be further configured to transmit data to a data processing terminal 105 for evaluating the data received by the primary receiver unit 104. Moreover, the data processing terminal 105 in one embodiment may be configured to receive data directly from the transmitter unit 102 via a communication link which may optionally be configured for bidirectional communication. Accordingly, transmitter unit 102 and/or receiver unit 104 may include a transceiver.

Also shown in FIG. 1 is an optional secondary receiver unit 106 which is operatively coupled to the communication link and configured to receive data transmitted from the transmitter unit 102. Moreover, as shown in the Figure, the secondary receiver unit 106 is configured to communicate with the primary receiver unit 104 as well as the data processing terminal 105. Indeed, the secondary receiver unit 106 may be configured for bidirectional wireless communication with each or one of the primary receiver unit 104 and the data processing terminal 105. As discussed in further detail below, in one embodiment of the present disclosure, the secondary receiver unit 106 may be configured to include a limited number of functions and features as compared with the primary receiver unit 104. As such, the secondary receiver unit 106 may be configured substantially in a smaller compact housing or embodied in a device such as a wrist watch, pager, mobile phone, PDA, for example. Alternatively, the secondary receiver unit 106 may be configured with the same or substantially similar functionality as the primary receiver unit 104. The receiver unit may be configured to be used in conjunction with a docking cradle unit, for example for one or more of the following or other functions: placement by bedside, for re-charging, for data management, for night time monitoring, and/or bi-directional communication device.

In one aspect sensor unit 101 may include two or more sensors, each configured to communicate with transmitter unit 102. Furthermore, while only one, transmitter unit 102, communication link 103, and data processing terminal 105 are shown in the embodiment of the analyte monitoring system 100 illustrated in FIG. 1. However, it will be appreciated by one of ordinary skill in the art that the analyte monitoring system 100 may include one or more sensors, multiple transmitter units 102, communication links 103, and data processing terminals 105. Moreover, within the scope of the present disclosure, the analyte monitoring system 100 may be a continuous monitoring system, or semi-continuous, or a discrete monitoring system. In a multi-component environment, each device is configured to be uniquely identified by each of the other devices in the system so that communication conflict is readily resolved between the various components within the analyte monitoring system 100.

In one embodiment of the present disclosure, the sensor unit 101 is physically positioned in or on the body of a user whose analyte level is being monitored. The sensor unit 101 may be configured to continuously sample the analyte level of the user and convert the sampled analyte level into a corresponding data signal for transmission by the transmitter unit 102. In certain embodiments, the transmitter unit 102 may be physically coupled to the sensor unit 101 so that both devices are integrated in a single housing and positioned on the user's body. The transmitter unit 102 may perform data processing such as filtering and encoding on data signals and/or other functions, each of which corresponds to a sampled analyte level of the user, and in any event transmitter unit 102 transmits analyte information to the primary receiver unit 104 via the communication link 103.

In one embodiment, the analyte monitoring system 100 is configured as a one-way RF communication path from the transmitter unit 102 to the primary receiver unit 104. In such embodiment, the transmitter unit 102 transmits the sampled data signals received from the sensor unit 101 without acknowledgement from the primary receiver unit 104 that the transmitted sampled data signals have been received. For example, the transmitter unit 102 may be configured to transmit the encoded sampled data signals at a fixed rate (e.g., at one minute intervals) after the completion of the initial power on procedure. Likewise, the primary receiver unit 104 may be configured to detect such transmitted encoded sampled data signals at predetermined time intervals. Alternatively, the analyte monitoring system 100 may be configured with a bidirectional RF (or otherwise) communication between the transmitter unit 102 and the primary receiver unit 104.

Additionally, in one aspect, the primary receiver unit 104 may include two sections. The first section is an analog interface section that is configured to communicate with the transmitter unit 102 via the communication link 103. In one embodiment, the analog interface section may include an RF receiver and an antenna for receiving and amplifying the data signals from the transmitter unit 102, which are thereafter, demodulated with a local oscillator and filtered through a band-pass filter. The second section of the primary receiver unit 104 is a data processing section which is configured to process the data signals received from the transmitter unit 102 such as by performing data decoding, error detection and correction, data clock generation, and data bit recovery.

In operation, upon completing the power-on procedure, the primary receiver unit 104 is configured to detect the presence of the transmitter unit 102 within its range based on, for example, the strength of the detected data signals received from the transmitter unit 102 and/or a predetermined transmitter identification information. Upon successful synchronization with the corresponding transmitter unit 102, the primary receiver unit 104 is configured to begin receiving from the transmitter unit 102 data signals corresponding to the user's detected analyte level. More specifically, the primary receiver unit 104 in one embodiment is configured to perform synchronized time hopping with the corresponding synchronized transmitter unit 102 via the communication link 103 to obtain the user's detected analyte level.

Referring again to FIG. 1, the data processing terminal 105 may include a personal computer, a portable computer such as a laptop or a handheld device (e.g., personal digital assistants (PDAs)), and the like, each of which may be configured for data communication with the receiver via a wired or a wireless connection. Additionally, the data processing terminal 105 may further be connected to a data network (not shown) for storing, retrieving and updating data corresponding to the detected analyte level of the user.

Within the scope of the present disclosure, the data processing terminal 105 may include an infusion device such as an insulin infusion pump (external or implantable) or the like, which may be configured to administer insulin to patients, and which may be configured to communicate with the receiver unit 104 for receiving, among others, the measured analyte level. Alternatively, the receiver unit 104 may be configured to integrate or otherwise couple to an infusion device therein so that the receiver unit 104 is configured to administer insulin therapy to patients, for example, for administering and modifying basal profiles, as well as for determining appropriate boluses for administration based on, among others, the detected analyte levels received from the transmitter unit 102.

Additionally, the transmitter unit 102, the primary receiver unit 104 and the data processing terminal 105 may each be configured for bi-directional wireless communication such that each of the transmitter unit 102, the primary receiver unit 104 and the data processing terminal 105 may be configured to communicate (that is, transmit data to and receive data from) with each other via the wireless communication link 103. More specifically, the data processing terminal 105 may in one embodiment be configured to receive data directly from the transmitter unit 102 via the communication link 106, where the communication link 106, as described above, may be configured for bi-directional communication.

In this embodiment, the data processing terminal 105 which may include an insulin pump, may be configured to receive the analyte signals from the transmitter unit 102, and thus, incorporate the functions of the receiver 103 including data processing for managing the patient's insulin therapy and analyte monitoring. In one embodiment, the communication link 103 may include one or more of an RF communication protocol, an infrared communication protocol, a Bluetooth enabled communication protocol, an 802.11x wireless communication protocol, or an equivalent wireless communication protocol which would allow secure, wireless communication of several units (for example, per HIPPA requirements) while avoiding potential data collision and interference.

FIG. 2 is a block diagram of the transmitter of the data monitoring and detection system shown in FIG. 1 in accordance with one embodiment of the present disclosure. Referring to the Figure, the transmitter unit 102 in one embodiment includes an analog interface 201 configured to communicate with the sensor unit 101 (FIG. 1), a user input 202, and a temperature detection section 203, each of which is operatively coupled to a transmitter processor 204 such as a central processing unit (CPU). As can be seen from FIG. 2, there are provided four contacts, three of which are electrodes—work electrode (W) 210, guard contact (G) 211, reference electrode (R) 212, and counter electrode (C) 213, each operatively coupled to the analog interface 201 of the transmitter unit 102 for connection to the sensor unit 101 (FIG. 1). In one embodiment, each of the work electrode (W) 210, guard contact (G) 211, reference electrode (R) 212, and counter electrode (C) 213 may be made using a conductive material that is either printed or etched or ablated, for example, such as carbon which may be printed, or a metal such as a metal foil (e.g., gold) or the like, which may be etched or ablated or otherwise processed to provide one or more electrodes. Fewer or greater electrodes and/or contact may be provided in certain embodiments.

Further shown in FIG. 2 are a transmitter serial communication section 205 and an RF transmitter 206, each of which is also operatively coupled to the transmitter processor 204. Moreover, a power supply 207 such as a battery is also provided in the transmitter unit 102 to provide the necessary power for the transmitter unit 102. Additionally, as can be seen from the Figure, clock 208 is provided to, among others, supply real time information to the transmitter processor 204.

In one embodiment, a unidirectional input path is established from the sensor unit 101 (FIG. 1) and/or manufacturing and testing equipment to the analog interface 201 of the transmitter unit 102, while a unidirectional output is established from the output of the RF transmitter 206 of the transmitter unit 102 for transmission to the primary receiver unit 104. In this manner, a data path is shown in FIG. 2 between the aforementioned unidirectional input and output via a dedicated link 209 from the analog interface 201 to serial communication section 205, thereafter to the processor 204, and then to the RF transmitter 206. As such, in one embodiment, via the data path described above, the transmitter unit 102 is configured to transmit to the primary receiver unit 104 (FIG. 1), via the communication link 103 (FIG. 1), processed and encoded data signals received from the sensor unit 101 (FIG. 1). Additionally, the unidirectional communication data path between the analog interface 201 and the RF transmitter 206 discussed above allows for the configuration of the transmitter unit 102 for operation upon completion of the manufacturing process as well as for direct communication for diagnostic and testing purposes.

As discussed above, the transmitter processor 204 is configured to transmit control signals to the various sections of the transmitter unit 102 during the operation of the transmitter unit 102. In one embodiment, the transmitter processor 204 also includes a memory (not shown) for storing data such as the identification information for the transmitter unit 102, as well as the data signals received from the sensor unit 101. The stored information may be retrieved and processed for transmission to the primary receiver unit 104 under the control of the transmitter processor 204. Furthermore, the power supply 207 may include a commercially available battery, which may be a rechargeable battery.

In certain embodiments, the transmitter unit 102 is also configured such that the power supply section 207 is capable of providing power to the transmitter for a minimum of about three months of continuous operation, e.g., after having been stored for about eighteen months such as stored in a low-power (non-operating) mode. In one embodiment, this may be achieved by the transmitter processor 204 operating in low power modes in the non-operating state, for example, drawing no more than approximately 1 μA of current. Indeed, in one embodiment, a step during the manufacturing process of the transmitter unit 102 may place the transmitter unit 102 in the lower power, non-operating state (i.e., post-manufacture sleep mode). In this manner, the shelf life of the transmitter unit 102 may be significantly improved. Moreover, as shown in FIG. 2, while the power supply unit 207 is shown as coupled to the processor 204, and as such, the processor 204 is configured to provide control of the power supply unit 207, it should be noted that within the scope of the present disclosure, the power supply unit 207 is configured to provide the necessary power to each of the components of the transmitter unit 102 shown in FIG. 2.

Referring back to FIG. 2, the power supply section 207 of the transmitter unit 102 in one embodiment may include a rechargeable battery unit that may be recharged by a separate power supply recharging unit (for example, provided in the receiver unit 104) so that the transmitter unit 102 may be powered for a longer period of usage time. Moreover, in one embodiment, the transmitter unit 102 may be configured without a battery in the power supply section 207, in which case the transmitter unit 102 may be configured to receive power from an external power supply source (for example, a battery) as discussed in further detail below.

Referring yet again to FIG. 2, the temperature detection section 203 of the transmitter unit 102 is configured to monitor the temperature of the skin near the sensor insertion site. The temperature reading is used to adjust the analyte readings obtained from the analog interface 201. In certain embodiments, the RF transmitter 206 of the transmitter unit 102 may be configured for operation in the frequency band of approximately 315 MHz to approximately 322 MHz, for example, in the United States. In certain embodiments, the RF transmitter 206 of the transmitter unit 102 may be configured for operation in the frequency band of approximately 400 MHz to approximately 470 MHz. Further, in one embodiment, the RF transmitter 206 is configured to modulate the carrier frequency by performing Frequency Shift Keying and Manchester encoding. In one embodiment, the data transmission rate is about 19,200 symbols per second, with a minimum transmission range for communication with the primary receiver unit 104.

Referring yet again to FIG. 2, also shown is a leak detection circuit 214 coupled to the guard electrode (G) 211 and the processor 204 in the transmitter unit 102 of the data monitoring and management system 100. The leak detection circuit 214 in accordance with one embodiment of the present disclosure may be configured to detect leakage current in the sensor unit 101 to determine whether the measured sensor data are corrupt or whether the measured data from the sensor 101 is accurate. Exemplary analyte systems that may be employed are described in, for example, U.S. Pat. Nos. 6,134,461, 6,175,752, 6,121,611, 6,560,471, 6,746,582, and elsewhere, the disclosure of each of which are incorporated by reference for all purposes.

FIG. 3 is a block diagram of the receiver/monitor unit of the data monitoring and management system shown in FIG. 1 in accordance with one embodiment of the present disclosure. Referring to FIG. 3, the primary receiver unit 104 includes an analyte test strip, e.g., blood glucose test strip, interface 301, an RF receiver 302, an input 303, a temperature detection section 304, and a clock 305, each of which is operatively coupled to a receiver processor 307. As can be further seen from the Figure, the primary receiver unit 104 also includes a power supply 306 operatively coupled to a power conversion and monitoring section 308. Further, the power conversion and monitoring section 308 is also coupled to the receiver processor 307. Moreover, also shown are a receiver serial communication section 309, and an output 310, each operatively coupled to the receiver processor 307.

In one embodiment, the test strip interface 301 includes a glucose level testing portion to receive a manual insertion of a glucose test strip, and thereby determine and display the glucose level of the test strip on the output 310 of the primary receiver unit 104. This manual testing of glucose may be used to calibrate the sensor unit 101 or otherwise. The RF receiver 302 is configured to communicate, via the communication link 103 (FIG. 1) with the RF transmitter 206 of the transmitter unit 102, to receive encoded data signals from the transmitter unit 102 for, among others, signal mixing, demodulation, and other data processing. The input 303 of the primary receiver unit 104 is configured to allow the user to enter information into the primary receiver unit 104 as needed. In one aspect, the input 303 may include one or more keys of a keypad, a touch-sensitive screen, or a voice-activated input command unit. The temperature detection section 304 is configured to provide temperature information of the primary receiver unit 104 to the receiver processor 307, while the clock 305 provides, among others, real time information to the receiver processor 307.

Each of the various components of the primary receiver unit 104 shown in FIG. 3 is powered by the power supply 306 which, in one embodiment, includes a battery. Furthermore, the power conversion and monitoring section 308 is configured to monitor the power usage by the various components in the primary receiver unit 104 for effective power management and to alert the user, for example, in the event of power usage which renders the primary receiver unit 104 in sub-optimal operating conditions. An example of such sub-optimal operating condition may include, for example, operating the vibration output mode (as discussed below) for a period of time thus substantially draining the power supply 306 while the processor 307 (thus, the primary receiver unit 104) is turned on. Moreover, the power conversion and monitoring section 308 may additionally be configured to include a reverse polarity protection circuit such as a field effect transistor (FET) configured as a battery activated switch.

The serial communication section 309 in the primary receiver unit 104 is configured to provide a bi-directional communication path from the testing and/or manufacturing equipment for, among others, initialization, testing, and configuration of the primary receiver unit 104. Serial communication section 104 can also be used to upload data to a computer, such as time-stamped blood glucose data. The communication link with an external device (not shown) can be made, for example, by cable, infrared (IR) or RF link. The output 310 of the primary receiver unit 104 is configured to provide, among others, a graphical user interface (GUI) such as a liquid crystal display (LCD) for displaying information. Additionally, the output 310 may also include an integrated speaker for outputting audible signals as well as to provide vibration output as commonly found in handheld electronic devices, such as mobile telephones presently available. In a further embodiment, the primary receiver unit 104 also includes an electro-luminescent lamp configured to provide backlighting to the output 310 for output visual display in dark ambient surroundings.

Referring back to FIG. 3, the primary receiver unit 104 in one embodiment may also include a storage section such as a programmable, non-volatile memory device as part of the processor 307, or provided separately in the primary receiver unit 104, operatively coupled to the processor 307. The processor 307 may be configured to synchronize with a transmitter, e.g., using Manchester decoding or the like, as well as error detection and correction upon the encoded data signals received from the transmitter unit 102 via the communication link 103.

Additional description of the RF communication between the transmitter 102 and the primary receiver 104 (or with the secondary receiver 106) that may be employed in embodiments of the subject invention is disclosed in pending application Ser. No. 11/060,365 filed Feb. 16, 2005 entitled “Method and System for Providing Data Communication in Continuous Glucose Monitoring and Management System” the disclosure of which is incorporated herein by reference for all purposes.

Referring to the Figures, in one embodiment, the transmitter 102 (FIG. 1) may be configured to generate data packets for periodic transmission to one or more of the receiver units 104, 106, where each data packet includes in one embodiment two categories of data—urgent data and non-urgent data. For example, urgent data such as for example glucose data from the sensor and/or temperature data associated with the sensor may be packed in each data packet in addition to non-urgent data, where the non-urgent data is rolled or varied with each data packet transmission.

That is, the non-urgent data is transmitted at a timed interval so as to maintain the integrity of the analyte monitoring system without being transmitted over the RF communication link with each data transmission packet from the transmitter 102. In this manner, the non-urgent data, for example that are not time sensitive, may be periodically transmitted (and not with each data packet transmission) or broken up into predetermined number of segments and sent or transmitted over multiple packets, while the urgent data is transmitted substantially in its entirety with each data transmission.

Referring again to the Figures, upon receiving the data packets from the transmitter 102, the one or more receiver units 104, 106 may be configured to parse the received data packet to separate the urgent data from the non-urgent data, and also, may be configured to store the urgent data and the non-urgent data, e.g., in a hierarchical manner. In accordance with the particular configuration of the data packet or the data transmission protocol, more or less data may be transmitted as part of the urgent data, or the non-urgent rolling data. That is, within the scope of the present disclosure, the specific data packet implementation such as the number of bits per packet, and the like, may vary based on, among others, the communication protocol, data transmission time window, and so on.

In an exemplary embodiment, different types of data packets may be identified accordingly. For example, identification in certain exemplary embodiments may include—(1) single sensor, one minute of data, (2) two or multiple sensors, (3) dual sensor, alternate one minute data, and (4) response packet. For single sensor one minute data packet, in one embodiment, the transmitter 102 may be configured to generate the data packet in the manner, or similar to the manner, shown in Table 1 below.

TABLE 1

Single sensor, one minute of data

Number of Bits
Data Field

8
Transmit Time

14
Sensor1 Current Data

14
Sensor1 Historic Data

8
Transmit Status

12
AUX Counter

12
AUX Thermistor 1

12
AUX Thermistor 2

8
Rolling-Data-1

As shown in Table 1 above, the transmitter data packet in one embodiment may include 8 bits of transmit time data, 14 bits of current sensor data, 14 bits of preceding sensor data, 8 bits of transmitter status data, 12 bits of auxiliary counter data, 12 bits of auxiliary thermistor 1 data, 12 bits of auxiliary thermistor 1 data and 8 bits of rolling data. In one embodiment of the present disclosure, the data packet generated by the transmitter for transmission over the RF communication link may include all or some of the data shown above in Table 1.

Referring back, the 14 bits of the current sensor data provides the real time or current sensor data associated with the detected analyte level, while the 14 bits of the sensor historic or preceding sensor data includes the sensor data associated with the detected analyte level one minute ago. In this manner, in the case where the receiver unit 104, 106 drops or fails to successfully receive the data packet from the transmitter 102 in the minute by minute transmission, the receiver unit 104, 106 may be able to capture the sensor data of a prior minute transmission from a subsequent minute transmission.

Referring again to Table 1, the Auxiliary data in one embodiment may include one or more of the patient's skin temperature data, a temperature gradient data, reference data, and counter electrode voltage. The transmitter status field may include status data that is configured to indicate corrupt data for the current transmission (for example, if shown as BAD status (as opposed to GOOD status which indicates that the data in the current transmission is not corrupt)). Furthermore, the rolling data field is configured to include the non-urgent data, and in one embodiment, may be associated with the time-hop sequence number. In addition, the Transmitter Time field in one embodiment includes a protocol value that is configured to start at zero and is incremented by one with each data packet. In one aspect, the transmitter time data may be used to synchronize the data transmission window with the receiver unit 104, 106, and also, provide an index for the Rolling data field.

In a further embodiment, the transmitter data packet may be configured to provide or transmit analyte sensor data from two or more independent analyte sensors. The sensors may relate to the same or different analyte or property. In such a case, the data packet from the transmitter 102 may be configured to include 14 bits of the current sensor data from both sensors in the embodiment in which 2 sensors are employed. In this case, the data packet does not include the immediately preceding sensor data in the current data packet transmission. Instead, a second analyte sensor data is transmitted with a first analyte sensor data.

TABLE 2

Dual sensor data

Number of

Bits
Data Field

8
Transmit Time

14
Sensor1 Current Data

14
Sensor2 Current Data

8
Transmit Status

12
AUX Counter

12
AUX Thermistor 1

12
AUX Thermistor 2

8
Rolling-Data-1

In a further embodiment, the transmitter data packet may be alternated with each transmission between two analyte sensors, for example, alternating between the data packet shown in Table 3 and Table 4 below.

TABLE 3

Sensor Data Packet Alternate 1

Number of Bits
Data Field

8
Transmitter Time

14
Sensor1 Current Data

14
Sensor1 Historic Data

8
Transmit Status

12
AUX Counter

12
AUX Thermistor 1

12
AUX Thermistor 2

8
Rolling-Data-1

TABLE 4

Sensor Data Packet Alternate 2

Number of Bits
Data Field

8
Transmitter Time

14
Sensor1 Current Data

14
Sensor2 Current Data

8
Transmit Status

12
AUX Counter

12
AUX Thermistor 1

12
AUX Thermistor 2

8
Rolling-Data-1

As shown above in reference to Tables 3 and 4, the minute by minute data packet transmission from the transmitter 102 (FIG. 1) in one embodiment may alternate between the data packet shown in Table 3 and the data packet shown in Table 4. More specifically, the transmitter 102 may be configured in one embodiment to transmit the current sensor data of the first sensor and the preceding sensor data of the first sensor (Table 3), as well as the rolling data, and further, at the subsequent transmission, the transmitter 102 may be configured to transmit the current sensor data of the first and the second sensor in addition to the rolling data.

In one embodiment, the rolling data transmitted with each data packet may include a sequence of various predetermined types of data that are considered not-urgent or not time sensitive. That is, in one embodiment, the following list of data shown in Table 5 may be sequentially included in the 8 bits of transmitter data packet, and not transmitted with each data packet transmission of the transmitter (for example, with each 60 second data transmission from the transmitter 102).

TABLE 5

Rolling Data

Time Slot
Bits
Rolling-Data

0
8
Mode

1
8
Glucose1 Slope

2
8
Glucose2 Slope

3
8
Ref-R

4
8
Hobbs Counter, Ref-R

5
8
Hobbs Counter

6
8
Hobbs Counter

7
8
Sensor Count

As can be seen from Table 5 above, in one embodiment, a sequence of rolling data are appended or added to the transmitter data packet with each data transmission time slot. In one embodiment, there may be 256 time slots for data transmission by the transmitter 102 (FIG. 1), and where, each time slot is separately by approximately 60 second interval. For example, referring to the Table 5 above, the data packet in transmission time slot 0 (zero) may include operational mode data (Mode) as the rolling data that is appended to the transmitted data packet. At the subsequent data transmission time slot (for example, approximately 60 seconds after the initial time slot (0), the transmitted data packet may include the analyte sensor 1 calibration factor information (Glucose1 slope) as the rolling data. In this manner, with each data transmission, the rolling data may be updated over the 256 time slot cycle.

Referring again to Table 5, each rolling data field is described in further detail for various embodiments. For example, the Mode data may include information related to the different operating modes such as, but not limited to, the data packet type, the type of battery used, diagnostic routines, single sensor or multiple sensor input, or type of data transmission (RF communication link or other data link such as serial connection). Further, the Glucose1-slope data may include an 8-bit scaling factor or calibration data for first sensor (scaling factor for sensor 1 data), while Glucose2-slope data may include an 8-bit scaling factor or calibration data for the second analyte sensor (in the embodiment including more than one analyte sensors).

In addition, the Ref-R data may include 12 bits of on-board reference resistor used to calibrate our temperature measurement in the thermister circuit (where 8 bits are transmitted in time slot 3, and the remaining 4 bits are transmitted in time slot 4), and the 20-bit Hobbs counter data may be separately transmitted in three time slots (for example, in time slot 4, time slot 5 and time slot 6) to add up to 20 bits. In one embodiment, the Hobbs counter may be configured to count each occurrence of the data transmission (for example, a packet transmission at approximately 60 second intervals) and may be incremented by a count of one (1).

In one aspect, the Hobbs counter is stored in a nonvolatile memory of the transmitter unit 102 (FIG. 1) and may be used to ascertain the power supply status information such as, for example, the estimated battery life remaining in the transmitter unit 102. That is, with each sensor replacement, the Hobbs counter is not reset, but rather, continues the count with each replacement of the sensor unit 101 to establish contact with the transmitter unit 102 such that, over an extended usage time period of the transmitter unit 102, it may be possible to determine, based on the Hobbs count information, the amount of consumed battery life in the transmitter unit 102, and also, an estimated remaining life of the battery in the transmitter unit 102.

That is, in one embodiment, the 20 bit Hobbs counter is incremented by one each time the transmitter unit 102 transmits a data packet (for example, approximately each 60 seconds), and based on the count information in the Hobbs counter, in one aspect, the battery life of the transmitter unit 102 may be estimated. In this manner, in configurations of the transmitter unit 620 (see FIG. 6) where the power supply is not a replaceable component but rather, embedded within the housing the transmitter unit 620, it is possible to estimate the remaining life of the embedded battery within the transmitter unit 620. Moreover, the Hobbs counter is configured to remain persistent in the memory device of the transmitter unit 620 such that, even when the transmitter unit power is turned off or powered down (for example, during the periodic sensor unit replacement, RF transmission turned off period and the like), the Hobbs counter information is retained.

Referring to Table 5 above, the transmitted rolling data may also include 8 bits of sensor count information (for example, transmitted in time slot 7). The 8 bit sensor counter is incremented by one each time a new sensor unit is connected to the transmitter unit. The ASIC configuration of the transmitter unit (or a microprocessor based transmitter configuration or with discrete components) may be configured to store in a nonvolatile memory unit the sensor count information and transmit it to the primary receiver unit 104 (for example). In turn, the primary receiver unit 104 (and/or the secondary receiver unit 106) may be configured to determine whether it is receiving data from the transmitter unit that is associated with the same sensor unit (based on the sensor count information), or from a new or replaced sensor unit (which will have a sensor count incremented by one from the prior sensor count). In this manner, in one aspect, the receiver unit (primary or secondary) may be configured to prevent reuse of the same sensor unit by the user based on verifying the sensor count information associated with the data transmission received from the transmitter unit 102. In addition, in a further aspect, user notification may be associated with one or more of these parameters. Further, the receiver unit (primary or secondary) may be configured to detect when a new sensor has been inserted, and thus prevent erroneous application of one or more calibration parameters determined in conjunction with a prior sensor, that may potentially result in false or inaccurate analyte level determination based on the sensor data.

FIG. 4 is a flowchart illustrating a data packet procedure including rolling data for transmission in accordance with one embodiment of the present disclosure. Referring to FIG. 4, in one embodiment, a counter is initialized (for example, to T=0) (410). Thereafter the associated rolling data is retrieved from memory device, for example (420), and also, the time sensitive or urgent data is retrieved (430). In one embodiment, the retrieval of the rolling data (420) and the retrieval of the time sensitive data (430) may be retrieved at substantially the same time.

Referring back to FIG. 4, with the rolling data and the time sensitive data, for example, the data packet for transmission is generated (440), and upon transmission, the counter is incremented by one (450) and the routine returns to retrieval of the rolling data (420). In this manner, in one embodiment, the urgent time sensitive data as well as the non-urgent data may be incorporated in the same data packet and transmitted by the transmitter 102 (FIG. 1) to a remote device such as one or more of the receivers 104, 106. Furthermore, as discussed above, the rolling data may be updated at a predetermined time interval which is longer than the time interval for each data packet transmission from the transmitter 102 (FIG. 1).

FIG. 5 is a flowchart illustrating data processing of the received data packet including the rolling data in accordance with one embodiment of the present disclosure. Referring to FIG. 5, when the data packet is received (510) (for example, by one or more of the receivers 104, 106, in one embodiment) the received data packet is parsed so that the urgent data may be separated from the not-urgent data (stored in, for example, the rolling data field in the data packet) (520). Thereafter the parsed data is suitably stored in an appropriate memory or storage device (530).

In the manner described above, in accordance with one embodiment of the present disclosure, there is provided method and apparatus for separating non-urgent type data (for example, data associated with calibration) from urgent type data (for example, monitored analyte related data) to be transmitted over the communication link to minimize the potential burden or constraint on the available transmission time. More specifically, in one embodiment, non-urgent data may be separated from data that is required by the communication system to be transmitted immediately, and transmitted over the communication link together while maintaining a minimum transmission time window. In one embodiment, the non-urgent data may be parsed or broken up in to a number of data segments, and transmitted over multiple data packets. The time sensitive immediate data (for example, the analyte sensor data, temperature data, etc.), may be transmitted over the communication link substantially in its entirety with each data packet or transmission.

FIG. 6 is a block diagram illustrating the sensor unit and the transmitter unit of the data monitoring and management system of FIG. 1 in accordance with one embodiment of the present disclosure. Referring to FIG. 6, in one aspect, a transmitter unit 620 is provided in a substantially water tight and sealed housing. The transmitter unit 620 includes respective contacts (wrk, ref, cntr, and grd) for respectively establishing electrical contact with one or more of the working electrode, the reference electrode, the counter electrode and the ground terminal (or guard trace) of the sensor unit 610. Also shown in FIG. 6 is a conductivity bar/trace 611 provided on the sensor unit 610. For example, in one embodiment, the conductivity bar/trace 611 may comprise a carbon trace on a substrate layer of the sensor unit 610. In this manner, in one embodiment, when the sensor unit 610 is coupled to the transmitter unit 610, electrical contact is established, for example, via the conductivity bar/trace 611 between the contact pads or points of the transmitter unit 620 (for example, at the counter electrode contact (cntr) and the ground terminal contact (grd) such that the transmitter unit 620 may be powered for data communication.

That is, during manufacturing of the transmitter unit 620, in one aspect, the transmitter unit 620 is configured to include a power supply such as battery 621. Further, during the initial non-use period (e.g., post manufacturing sleep mode), the transmitter unit 620 is configured such that it is not used and thus drained by the components of the transmitter unit 620. During the sleep mode, and prior to establishing electrical contact with the sensor unit 610 via the conductivity bar/trace 611, the transmitter unit 620 is provided with a low power signal from, for example, a low power voltage comparator 622, via an electronic switch 623 to maintain the low power state of, for example, the transmitter unit 620 components. Thereafter, upon connection with the sensor unit 610, and establishing electrical contact via the conductivity bar/trace 611, the embedded power supply 621 of the transmitter unit 620 is activated or powered up so that some of all of the components of the transmitter unit 620 are configured to receive the necessary power signals for operations related to, for example, data communication, processing and/or storage.

In one aspect, since the transmitter unit 620 is configured to a sealed housing without a separate replaceable battery compartment, in this manner, the power supply of the battery 621 is preserved during the post manufacturing sleep mode prior to use.

In a further aspect, the transmitter unit 620 may be disposed or positioned on a separate on-body mounting unit that may include, for example, an adhesive layer (on its bottom surface) to firmly retain the mounting unit on the skin of the user, and which is configured to receive or firmly position the transmitter unit 620 on the mounting unit during use. In one aspect, the mounting unit may be configured to at least partially retain the position of the sensor unit 610 in a transcutaneous manner so that at least a portion of the sensor unit is in fluid contact with the analyte of the user. Example embodiments of the mounting or base unit and its cooperation or coupling with the transmitter unit are provided, for example, in U.S. Pat. No. 6,175,752, incorporated herein by reference for all purposes.

In such a configuration, the power supply for the transmitter unit 620 may be provided within the housing of the mounting unit such that, the transmitter unit 620 may be configured to be powered on or activated upon placement of the transmitter unit 620 on the mounting unit and in electrical contact with the sensor unit 610. For example, the sensor unit 610 may be provided pre-configured or integrated with the mounting unit and the insertion device such that, the user may position the sensor unit 610 on the skin layer of the user using the insertion device coupled to the mounting unit. Thereafter, upon transcutaneous positioning of the sensor unit 610, the insertion device may be discarded or removed from the mounting unit, leaving behind the transcutaneously positioned sensor unit 610 and the mounting unit on the skin surface of the user.

Thereafter, when the transmitter unit 620 is positioned on, over or within the mounting unit, the battery or power supply provided within the mounting unit is configured to electrically couple to the transmitter unit 620 and/or the sensor unit 610. Given that the sensor unit 610 and the mounting unit are provided as replaceable components for replacement every 3, 5, 7 days or other predetermined time periods, the user is conveniently not burdened with verifying the status of the power supply providing power to the transmitter unit 620 during use. That is, with the power supply or battery replaced with each replacement of the sensor unit 610, a new power supply or battery will be provided with the new mounting unit for use with the transmitter unit 620.

Referring to FIG. 6 again, in one aspect, when the sensor unit 610 is removed from the transmitter unit 620 (or vice versa), the electrical contact is broken and the conductivity bar/trace 611 returns to an open circuit. In this case, the transmitter unit 620 may be configured, to detect such condition and generate a last gasp transmission sent to the primary receiver unit 104 (and/or the secondary receiver unit 106) indicating that the sensor unit 610 is disconnected from the transmitter unit 620, and that the transmitter unit 620 is entering a powered down (or low power off) state. And the transmitter unit 620 is powered down into the sleep mode since the connection to the power supply (that is embedded within the transmitter unit 620 housing) is broken.

In this manner, in one aspect, the processor 624 of the transmitter unit 620 may be configured to generate the appropriate one or more data or signals associated with the detection of sensor unit 610 disconnection for transmission to the receiver unit 104 (FIG. 1), and also, to initiate the power down procedure of the transmitter unit 620. In one aspect, the components of the transmitter unit 620 may be configured to include application specific integrated circuit (ASIC) design with one or more state machines and one or more nonvolatile and/or volatile memory units such as, for example, EEPROMs and the like.

Referring again to FIGS. 1 and 6, in one embodiment, the communication between the transmitter unit 620 (or 102 of FIG. 1) and the primary receiver unit 104 (and/or the secondary receiver unit 106) may be based on close proximity communication where bi-directional (or uni-directional) wireless communication is established when the devices are physically located in close proximity to each other. That is, in one embodiment, the transmitter unit 620 may be configured to receive very short range commands from the primary receiver unit 104 (FIG. 1) and perform one or more specific operations based on the received commands from the receiver unit 104).

In one embodiment, to maintain secure communication between the transmitter unit and the data receiver unit, the transmitter unit ASIC may be configured to generate a unique close proximity key at power on or initialization. In one aspect, the 4 or 8 bit key may be generated based on, for example, the transmitter unit identification information, and which may be used to prevent undesirable or unintended communication. In a further aspect, the close proximity key may be generated by the receiver unit based on, for example, the transmitter identification information received by the transmitter unit during the initial synchronization or pairing procedure of the transmitter and the receiver units.

Referring again to FIGS. 1 and 6, in one embodiment, the transmitter unit ASIC configuration may include a 32KHz oscillator and a counter which may be configured to drive the state machine in the transmitter unit ASIC. The transmitter ASIC configuration may include a plurality of close proximity communication commands including, for example, new sensor initiation, pairing with the receiver unit, and RF communication control, among others. For example, when a new sensor unit is positioned and coupled to the transmitter unit so that the transmitter unit is powered on, the transmitter unit is configured to detect or receive a command from the receiver unit positioned in close proximity to the transmitter unit. For example, the receiver unit may be positioned within a couple of inches from the on-body position of the transmitter unit, and when the user activates or initiates a command associated with the new sensor initiation from the receiver unit, the transmitter unit is configured to receive the command from the receiver and, in its response data packet, transmit, among others, its identification information back to the receiver unit.

In one embodiment, the initial sensor unit initiation command does not require the use of the close proximity key. However, other predefined or preconfigured close-proximity commands may be configured to require the use of the 8 bit key (or a key of a different number of bits). For example, in one embodiment, the receiver unit may be configured to transmit a RF on/off command to turn on/off the RF communication module or unit in the transmitter unit 102. Such RF on/off command in one embodiment includes the close proximity key as part of the transmitted command for reception by the transmitter unit.

During the period that the RF communication module or unit is turned off based on the received close proximity command, the transmitter unit does not transmit any data, including any glucose related data. In one embodiment, the glucose related data from the sensor unit which are not transmitted by the transmitter unit during the time period when the RF communication module or unit of the transmitter unit is turned off may be stored in a memory or storage unit of the transmitter unit for subsequent transmission to the receiver unit when the transmitter unit RF communication module or unit is turned back on based on the RF-on command from the receiver unit. In this manner, in one embodiment, the transmitter unit may be powered down (temporarily, for example, during air travel) without removing the transmitter unit from the on-body position.

FIG. 7 is a flowchart illustrating data communication using close proximity commands in the data monitoring and management system of FIG. 1 in accordance with one embodiment of the present disclosure. Referring to FIG. 7, the primary receiver unit 104 (FIG. 1) in one aspect may be configured to retrieve or generate a close proximity command (710) for transmission to the transmitter unit 102. To establish the transmission range (720), the primary receiver unit 104 may be positioned physically close to (that is, within a predetermined distance from) the transmitter unit 102. For example, the transmission range for the close proximity communication may be established at approximately one foot distance or less between the transmitter unit 102 and the primary receiver unit 104. When the transmitter unit 102 and the primary receiver unit 104 are within the transmission range, the close proximity command, upon initiation from the receiver unit 104 may be transmitted to the transmitter unit 102 (730).

Referring back to FIG. 7, in response to the transmitted close proximity command, a response data packet or other responsive communication may be received (740). In one aspect, the response data packet or other responsive communication may include identification information of the transmitter unit 102 transmitting the response data packer or other response communication to the receiver unit 104. In one aspect, the receiver unit 104 may be configured to generate a key (for example, an 8 bit key or a key of a predetermined length) based on the transmitter identification information (750), and which may be used in subsequent close proximity communication between the transmitter unit 102 and the receiver unit 104.

In one aspect, the data communication including the generated key may allow the recipient of the data communication to recognize the sender of the data communication and confirm that the sender of the data communication is the intended data sending device, and thus, including data which is desired or anticipated by the recipient of the data communication. In this manner, in one embodiment, one or more close proximity commands may be configured to include the generated key as part of the transmitted data packet. Moreover, the generated key may be based on the transmitter ID or other suitable unique information so that the receiver unit 104 may use such information for purposes of generating the unique key for the bidirectional communication between the devices.

While the description above includes generating the key based on the transmitter unit 102 identification information, within the scope of the present disclosure, the key may be generated based on one or more other information associated with the transmitter unit 102, and/or the receiver unit combination. In a further embodiment, the key may be encrypted and stored in a memory unit or storage device in the transmitter unit 102 for transmission to the receiver unit 104.

FIG. 8 is a flowchart illustrating the pairing or synchronization routine in the data monitoring and management system of FIG. 1 in accordance with one embodiment of the present disclosure. Referring to FIG. 8, in one embodiment, the transmitter unit 102 may be configured to receive a sensor initiate close proximity command (810) from the receiver unit 104 positioned within the close transmission range. Based on the received sensor initiate command, the transmitter unit identification information may be retrieved (for example, from a nonvolatile memory) and transmitted (820) to the receiver unit 104 or the sender of the sensor initiate command.

Referring back to FIG. 8, a communication key (830) optionally encrypted is received in one embodiment, and thereafter, sensor related data is transmitted with the communication key on a periodic basis such as, every 60 seconds, five minutes, or any suitable predetermined time intervals (840).

Referring now to FIG. 9, a flowchart illustrating the pairing or synchronization routine in the data monitoring and management system of FIG. 1 in accordance with another embodiment of the present disclosure is shown. That is, in one aspect, FIG. 9 illustrates the pairing or synchronization routine from the receiver unit 104. Referring back to FIG. 9, the sensor initiate command is transmitted to the transmitter unit 102 (910) when the receiver unit 104 is positioned within a close transmission range. Thereafter, in one aspect, the transmitter identification information is received (920) for example, from the transmitter unit that received the sensor initiate command. Thereafter, a communication key (optionally encrypted) may be generated and transmitted (930) to the transmitter unit.

In the manner described above, in one embodiment, a simplified pairing or synchronization between the transmitter unit 102 and the receiver unit 104 may be established using, for example, close proximity commands between the devices. As described above, in one aspect, upon pairing or synchronization, the transmitter unit 102 may be configured to periodically transmit analyte level information to the receiver unit for further processing.

FIG. 10 is a flowchart illustrating the power supply determination in the data monitoring and management system of FIG. 1 in accordance with one embodiment of the present disclosure. That is, in one embodiment, using a counter, the receiver unit 104 may be configured to determine the power supply level of the transmitter unit 102 battery so as to determine a suitable time for replacement of the power supply or the transmitter unit 102 itself. Referring to FIG. 10, periodic data transmission is detected (1010), and a corresponding count in the counter is incremented for example, by one with each detected data transmission (1020). In particular, a Hobbs counter may be used in the rolling data configuration described above to provide a count that is associated with the transmitter unit data transmission occurrence.

Referring to FIG. 10, the updated or incremented count stored in the Hobbs counter is periodically transmitted in the data packet from the transmitter unit 102 to the receiver unit 104 (1030). Moreover, the incremented or updated count may be stored (1040) in a persistent nonvolatile memory unit of the transmitter unit 102. Accordingly, based on the number of data transmission occurrences, the battery power supply level may be estimated, and in turn, which may provide an indication as to when the battery (and thus the transmitter unit in the embodiment where the power supply is manufactured to be embedded within the transmitter unit housing) needs to be replaced.

Moreover, in one aspect, the incremented count in the Hobbs counter is stored in a persistent nonvolatile memory such that, the counter is not reset or otherwise restarted with each sensor unit replacement.

FIG. 11 is a flowchart illustrating close proximity command for RF communication control in the data monitoring and management system of FIG. 1 in accordance with one embodiment of the present disclosure. Referring to FIG. 11, a close proximity command associated with communication status, for example is received (1110). In one aspect, the command associated with the communication status may include, for example, a communication module turn on or turn off command for, for example, turning on or turning off the associated RF communication device of the transmitter unit 102. Referring to FIG. 11, the communication status is determined (1120), and thereafter, modified based on the received command (1130).

That is, in one aspect, using one or more close proximity commands, the receiver unit 104 may be configured to control the RF communication of the transmitter unit 102 to, for example, disable or turn off the RF communication functionality for a predetermined time period. This may be particularly useful when used in air travel or other locations such as hospital settings, where RF communication devices need to be disabled. In one aspect, the close proximity command may be used to either turn on or turn off the RF communication module of the transmitter unit 102, such that, when the receiver unit 104 is positioned in close proximity to the transmitter unit 102, and the RF command is transmitted, the transmitter unit 102 is configured, in one embodiment, to either turn off or turn on the RF communication capability of the transmitter unit 102.

FIG. 12 illustrates a data format of a close proximity data packet sent by a controller such as the receiver unit 104/106 to the transmitter unit 620 (FIG. 6) in the analyte monitoring system 100 (FIG. 1). Referring to FIG. 12, in one embodiment, a close proximity data packet sent by the controller may include 24 bits of data. In one aspect, the 24 bit data packet may include a dotting pattern 1210, a data frame 1220, one or more close proximity commands 1230, and a close proximity key 1240. As discussed in further detail below, in one embodiment, a sequence detector 1330 (FIG. 13) in the transmitter unit 620 ASIC logic uses the dotting pattern 1210 and the data frame 1220 to determine whether the incoming data is a proper close proximity data packet. In one aspect, the close proximity data packet as shown in FIG. 12 may include dotting pattern 1210 which may be used by the close proximity detector logic to detect and synchronize the received data, the data frame 1220 that includes bit pattern prior to the actual received data, the close proximity commands 1230, and close proximity key 1240 to validate the close proximity communication.

In one aspect, there may be five valid close proximity commands 1230 and the close proximity key 1240 may be used as a validation for the communication received from the controller (receiver unit 104/106) for example. While a 24 bit data packet for the close proximity command and five valid close proximity commands 1230 are described above, within the scope of the present disclosure, the data packet for the close proximity commands may include greater or less number of bits within the data packet, and further, the number of valid close proximity commands may be greater or fewer than five valid close proximity commands as described above.

FIG. 13 is a block diagram representation of a close proximity detection logic of the transmitter unit 620 in one or more embodiments of the present disclosure. Referring to FIG. 13, in one embodiment, incoming Manchester encoded data packet, for example, from the controller (receiver unit 104/106) is received at a rate of approximately 4.8 Kbits/second by the close proximity detector logic and decoded by a Manchester bit decoder logic 1310. The Manchester bit decoder logic 1310 detects the two data symbols and may be configured to convert the detected data to one data bit at 2.4 Kbits/sec.

In one aspect, the decoded data bit is sent to a bit timing counter logic 1320, a sequence detector logic 1330, and the shift register logic 1340. In one embodiment, the sequence detector logic 1330 looks for a predetermined data pattern showing the authenticity of the received data packet. In on aspect, the predetermined data pattern, for example ‘0100’, includes an occurrence of a dotting pattern ‘01’ and a data frame ‘00’. If only a partial sequence is detected followed by an incorrect data bit, the sequence detector logic 1330 may be configured to reset and wait for the next data packet. On the other hand, if the correct data packet is received with the expected or anticipated predetermined data pattern, for example, a ‘0100’, then the sequence detector logic 1330 deems the data packet to be valid.

When the data packet is determined to have the correct dotting pattern and data frame, and is deemed to be valid, a reset signal is disabled and a shift register signal is enabled. With a shift register signal enabled, each incoming bit of validated data is latched into an 11 bit envelope detector shift register logic 1340. Once the 11^thbit is latched into the register 1340, an on/off keying (OOK) signal indicates that close proximity communication has been completed. Once a close proximity command is sent and decoded, an envelope detect finite state machine (FSM) logic 1360 is configured to process the command. During the processing period, no further commands are accepted, and the close proximity state machine logic 1360 is locked in a final state. Once the command has been processed, the close proximity logic is reset by a logic reset signal. The close proximity logic then returns to its initial state and awaits further instructions.

Referring again to FIG. 13, a close proximity key 1350 may be used in conjunction with the close proximity command data packet to determine or confirm the identity of the close proximity command issuing device, such as, for example, the controller (receiver unit 104/106). For example, in one aspect, each transmitter unit 102, 620 (FIGS. 1, 6) may have a unique key based on, for example, the device serial or identification number. This value may be latched or stored, and provided to the close proximity logic, and when a close proximity communication is completed, the received key value as part of the close proximity command data packet is compared to the latched unique key. If the two values match, a signal corresponding to a key match is set high, indicating that the close proximity command received is intended for the transmitter unit that received the command.

Referring again to FIG. 13, a time out signal in conjunction with a bit timing counter 1320 may be used to determine whether transmission errors may have occurred. For example, each time a valid data bit is received by the close proximity logic of the transmitter unit 104/620, a time out signal is generated by the bit timing counter logic 1320. In one aspect, the time period between each time out signal is compared by the bit timing counter logic 1320, and if it is determined that the time period is greater than a predetermined time period based on the data bit time (for example, approximately 1.75 times the data bit time), then it is determined that the data transmission is in error. If it is determined that the transmission is in error, the state machine logic 1360 may be configured to reset the shift register logic 1340, sequence detector logic 1330, and the bit timer logic 1320. On the other hand, when it is determined that the data transmission is not in error, that is, when the time period between each time out signal compared by the bit timing counter logic 1320 is below the predetermined time period, then the data bit associated with the current data communication is considered valid.

Referring still to FIG. 13, a clock signal is provided to the Manchester bit decoder logic 1310, the bit timing counter logic 1320 and the shift register logic 1340 to, among others, synchronize the operation of the various routines executed by the components of the close proximity detector logic in the transmitter unit of the analyte monitoring system. Additionally, in the manner described, the close proximity detector logic may be configured to use small logic blocks running at a relatively slower clock rate, resulting in, for example, reduction in the required ASIC resources and/or power consumption. Furthermore, the embodiments of the close proximity detector logic described above provides a standalone continuous OOK detection without the use of a microcontroller that requires relatively more power and ASIC resources (for example, ASIC area).

Indeed, in accordance with embodiments of the present disclosure, the transmitted OOK data packets from the receiver unit (104/106) may be decoded in conjunction with the received close proximity commands using, for example, one or more of a Manchester decode block logic, error detection logics and a command decoder logic. Furthermore, while Manchester decoder logic is described above, within the scope of the present disclosure, other data encoding/decoding techniques may be used, for example, other binary phase-shift keying (BPSK).

FIG. 14 is a flow chart illustrating close proximity detection logic in one or more embodiments of the present disclosure. Referring to FIGS. 13 and 14, when a close proximity communication mode is activated in a data communication system for example, in the analyte monitoring system 100 (FIG. 1), the close proximity detector logic may be configured to continuously monitor to detect an incoming command or data signal. When the close proximity logic activated, an initial initialization occurs (1410) to clear data bits to ensure no incorrect signals are sent to the close proximity logic. The close proximity detector logic waits to receive one or more data packet (1420). As discussed above, the Manchester encoded data packets may be received at a rate of 4.8 Kbits/sec. When data is not received, the logic may time out and return to the initialization state (1410).

On the other hand, when the data packet is received, error correction is performed to determine the validity of the received data packet (1430). For example, as discussed above, the sequence detection logic may be configured to analyze the dotting pattern and the data frame of the received data packet to determine whether the data packet is valid. If it is determined that the analyzed dotting pattern and the data frame results in the detection of a particular sequence in the data pattern, then in one aspect, the routine may return to the reset/initialization state (1410). However, when it is determined that the received data packet is valid, the data packet is latched (1440), for example, in the shift register as discussed above. Indeed, when the 11^thbit in the data packet is received, in one aspect, it is determined that the close proximity communication is completed (1460).

Referring to FIGS. 13 and 14, the close proximity key is compared to confirm that the command received is intended for the transmitter device receiving the command (1450). For example, as discussed above in conjunction with FIG. 13, the data packet received may include a unique transmitter identification information (such as a serial number or other unique information). This information may be compared with a stored value to determine whether the information received matches the value stored. If it is determined that the close proximity key des not match, in one aspect, the routine returns to the initialization/reset state (1410), as the received data packet is not intended for the device that received the packet. On the other hand, if the closed proximity key matches the stored information or unique value, in one aspect, the state machine logic may be configured to generate the OOK signal confirming the receipt of the valid close proximity communication, and the state machine logic may be configured to perform the requested function or execute the one or more routines associated with the received close proximity command.

In this manner, embodiments of the present disclosure provide method and apparatus for optimizing power consumption and ASIC resources in communication devices such as transmitter unit 620 of the analyte monitoring system described above, or on-body patch pump for infusing medication such as insulin, or other therapeutic agents.

It is to be noted that while exemplary embodiments described above include configurations that have specific data packet size, transmission rate, size of the shift register, error correction techniques, and the like, within the scope of the present disclosure, other suitable variations are fully contemplated.

A method in one aspect includes receiving an encoded data packet including one or more error detection bits, one or more close proximity commands, and a communication identifier, decoding the received data packet, performing error detection based on the one or more error detection bits, validating the decoded received data packet, and executing one or more routines associated with the respective one or more close proximity commands when the decoded received data packet is validated, where the executed one or more routines includes transmitting analyte related data.

The received data packet may be Manchester encoded.

The one or more error detection bits may include a predetermined bit pattern such as a dotting pattern, for example.

In a further aspect, decoding the received data packet may include performing Manchester decoding.

Also, validating the decoded received data packet may include comparing the received communication identifier in the data packet with a stored value.

The communication identifier may include a device identification information.

The one or more routines may be associated with the operation of an analyte monitoring device.

The executed one or more routines may include a power on routine, a power off routine, data transfer initiation routine, or data transfer disable routine.

The analyte related data may include a monitored analyte level, such as glucose level.

In a further aspect, the method may include storing the received data packet.

A method in accordance with another embodiment includes receiving an encoded data packet including a close proximity command and a communication identifier, decoding the received data packet, validating the decoded received data packet, and executing one or more routines associated with the respective one or more close proximity commands when the decoded received data packet is validated.

In one aspect, validating the decoded received data packet may include comparing the received communication identifier in the data packet with a stored value.

Further, validating the decoded received data packet may include performing error detection on the data packet, including, for example, comparing one or more data pattern in the received data packet.

The communication identifier may include a device identification information.

The one or more routines may be associated with the operation of an analyte monitoring device.

The executed one or more routines may include a power on routine, a power off routine, data transfer initiation routine, or data transfer disable routine.

In still another aspect, the method may include receiving a signal associated with an analyte level, where the analyte includes glucose.

Also, the decoded received data packet may be stored in, for example, a memory, storage device, or the like.

An apparatus in accordance with still another embodiment includes a communication interface, one or more processors coupled to the communication interface, and a memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to receive an encoded data packet including one or more error detection bits, one or more close proximity commands, and a communication identifier over the communication interface, decode the received data packet, perform error detection based on the one or more error detection bits, validate the decoded received data packet, and execute one or more routines associated with the respective one or more close proximity commands when the decoded received data packet is validated, wherein the executed one or more routines includes transmitting analyte related data.

The memory for storing instructions which, when executed by the one or more processors, may cause the one or more processors to Manchester decode the received data packet.

The one or more error detection bits may include a predetermined bit pattern including, for example, a dotting pattern.

The memory for storing instructions which, when executed by the one or more processors, may cause the one or more processors to Manchester decode the received data packet.

The memory for storing instructions which, when executed by the one or more processors, may cause the one or more processors to compare the received communication identifier in the data packet with a stored value to validate the received data packet.

The memory for storing instructions which, when executed by the one or more processors, may cause the one or more processors to store the received data packet in the memory.

The one or more processors may include an application specific integrated circuit (ASIC).

In the manner described, in accordance with embodiments of the present disclosure, the close proximity detector logic may be configured to use small logic blocks running at a relatively slower clock rate, resulting in, for example, reduction in the required ASIC area and power consumption. Furthermore, the embodiments of the close proximity detector logic described above provides a standalone continuous OOK detection without the use of a microcontroller that requires relatively more power and ASIC resources.

Various other modifications and alterations in the structure and method of operation of this invention will be apparent to those skilled in the art without departing from the scope and spirit of the invention. Although the invention has been described in connection with specific preferred embodiments, it should be understood that the invention as claimed should not be unduly limited to such specific embodiments. It is intended that the following claims define the scope of the present disclosure and that structures and methods within the scope of these claims and their equivalents be covered thereby.

Claims

1. A method, comprising: establishing a communication range between a data processing unit and a control unit by placing the control unit within a predetermined distance from the data processing unit;receiving an encoded data packet at the data processing unit when the control unit is within the predetermined distance, wherein the received encoded data packet includes one or more error detection bits, one or more close proximity commands, and a communication identifier;decoding the received data packet;performing error detection based on the one or more error detection bits;validating the decoded received data packet; andexecuting one or more routines associated with the respective one or more close proximity commands when the decoded received data packet is validated; wherein the executed one or more routines includes transmitting analyte related data.
2. The method of claim 1 wherein the received data packet is Manchester encoded.
3. The method of claim 1 wherein the one or more error detection bits include a predetermined bit pattern.
4. The method of claim 3 wherein the predetermined bit pattern includes a dotting pattern.
5. The method of claim 1 wherein decoding the received data packet includes performing Manchester decoding.
6. The method of claim 1 wherein validating the decoded received data packet includes comparing the received communication identifier in the data packet with a stored value.
7. The method of claim 1 wherein the communication identifier includes a device identification information.
8. The method of claim 1 wherein the one or more routines are associated with the operation of an analyte monitoring device.
9. The method of claim 1 wherein the executed one or more routines includes a power on routine, a power off routine, a data transfer initiation routine, or a data transfer disable routine.
10. The method of claim 1 wherein the analyte related data includes a monitored analyte level.
11. The method of claim 10 wherein the analyte is glucose.
12. The method of claim 1 including storing the received data packet.
13. A method, comprising: establishing a communication range between a data processing unit and a control unit by placing the control unit within a predetermined distance from the data processing unit;receiving an encoded data packet at the data processing unit when the control unit is within the predetermined distance, wherein the received encoded data packet includes a close proximity command and a communication identifier;decoding the received data packet;validating the decoded received data packet; andexecuting one or more routines associated with the respective one or more close proximity commands when the decoded received data packet is validated, wherein the one or more close proximity commands are configured to control the transmission of analyte related data.
14. The method of claim 13 wherein the encoded data packet is Manchester encoded.
15. The method of claim 13 wherein decoding the received data packet includes performing Manchester decoding.
16. The method of claim 13 wherein validating the decoded received data packet includes comparing the received communication identifier in the data packet with a stored value.
17. The method of claim 13 wherein validating the decoded received data packet includes performing error detection on the data packet.
18. The method of claim 17 wherein performing error detection includes comparing one or more data pattern in the received data packet.
19. The method of claim 13 wherein the communication identifier includes a device identification information.
20. The method of claim 13 wherein the one or more routines are associated with the operation of an analyte monitoring device.
21. The method of claim 13 wherein the executed one or more routines includes a power on routine, a power off routine, a data transfer initiation routine, or a data transfer disable routine.
22. The method of claim 13 including receiving a signal associated with an analyte level.
23. The method of claim 22 wherein the analyte is glucose.
24. The method of claim 13 including storing the decoded received data packet.
25. An apparatus, comprising: a communication interface;one or more processors coupled to the communication interface; anda memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to establish a communication range with a control unit when the control unit is placed within a predetermined distance, receive an encoded data packet when the control unit is within the predetermined distance, wherein the received encoded data packet includes one or more error detection bits, one or more close proximity commands, and a communication identifier over the communication interface, decode the received data packet, perform error detection based on the one or more error detection bits, validate the decoded received data packet, and execute one or more routines associated with the respective one or more close proximity commands when the decoded received data packet is validated, wherein the executed one or more routines includes transmitting analyte related data.
26. The apparatus of claim 25 wherein the memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to Manchester decode the received data packet.
27. The apparatus of claim 25 wherein the one or more error detection bits include a predetermined bit pattern.
28. The apparatus of claim 27 wherein the predetermined bit pattern includes a dotting pattern.
29. The apparatus of claim 25 wherein the memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to Manchester decode the received data packet.
30. The apparatus of claim 25 wherein the memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to compare the received communication identifier in the data packet with a stored value to validate the received data packet.
31. The apparatus of claim 25 wherein the communication identifier includes a device identification information.
32. The apparatus of claim 25 wherein the executed one or more routines includes a power on routine, a power off routine, a data transfer initiation routine, or a data transfer disable routine.
33. The apparatus of claim 25 wherein the analyte related data includes a monitored analyte level.
34. The apparatus of claim 33 wherein the analyte is glucose.
35. The apparatus of claim 25 wherein the memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to store the received data packet in the memory.
36. The apparatus of claim 25 wherein the one or more processors include an application specific integrated circuit (ASIC).
37. The method of claim 1 wherein the predetermined distance is approximately one foot or less.
38. The method of claim 13 wherein the predetermined distance is approximately one foot or less.
39. The apparatus of claim 25 wherein the predetermined distance is approximately one foot or less.

US Referenced Citations (571)

Number	Name	Date	Kind
3581062	Aston	May 1971	A
3926760	Allen et al.	Dec 1975	A
3949388	Fuller	Apr 1976	A
4036749	Anderson	Jul 1977	A
4055175	Clemens et al.	Oct 1977	A
4129128	McFarlane	Dec 1978	A
4245634	Albisser et al.	Jan 1981	A
4327725	Cortese et al.	May 1982	A
4344438	Schultz	Aug 1982	A
4349728	Phillips et al.	Sep 1982	A
4373527	Fischell	Feb 1983	A
4392849	Petre et al.	Jul 1983	A
4425920	Bourland et al.	Jan 1984	A
4478976	Goertz et al.	Oct 1984	A
4494950	Fischell	Jan 1985	A
4509531	Ward	Apr 1985	A
4527240	Kvitash	Jul 1985	A
4538616	Rogoff	Sep 1985	A
4619793	Lee	Oct 1986	A
4671288	Gough	Jun 1987	A
4703756	Gough et al.	Nov 1987	A
4731726	Allen, III	Mar 1988	A
4749985	Corsberg	Jun 1988	A
4757022	Shults et al.	Jul 1988	A
4777953	Ash et al.	Oct 1988	A
4779618	Mund et al.	Oct 1988	A
4854322	Ash et al.	Aug 1989	A
4871351	Feingold	Oct 1989	A
4890620	Gough	Jan 1990	A
4925268	Iyer et al.	May 1990	A
4953552	DeMarzo	Sep 1990	A
4986271	Wilkins	Jan 1991	A
4995402	Smith et al.	Feb 1991	A
5000180	Kuypers et al.	Mar 1991	A
5002054	Ash et al.	Mar 1991	A
5019974	Beckers	May 1991	A
5050612	Matsumura	Sep 1991	A
5055171	Peck	Oct 1991	A
5068536	Rosenthal	Nov 1991	A
5082550	Rishpon et al.	Jan 1992	A
5106365	Hernandez	Apr 1992	A
5122925	Inpyn	Jun 1992	A
5165407	Wilson et al.	Nov 1992	A
5246867	Lakowicz et al.	Sep 1993	A
5262035	Gregg et al.	Nov 1993	A
5262305	Heller et al.	Nov 1993	A
5264104	Gregg et al.	Nov 1993	A
5264105	Gregg et al.	Nov 1993	A
5279294	Anderson et al.	Jan 1994	A
5285792	Sjoquist et al.	Feb 1994	A
5293877	O'Hara et al.	Mar 1994	A
5299571	Mastrototaro	Apr 1994	A
5320725	Gregg et al.	Jun 1994	A
5322063	Allen et al.	Jun 1994	A
5340722	Wolfbeis et al.	Aug 1994	A
5342789	Chick et al.	Aug 1994	A
5356786	Heller et al.	Oct 1994	A
5360404	Novacek et al.	Nov 1994	A
5372427	Padovani et al.	Dec 1994	A
5379238	Stark	Jan 1995	A
5390671	Lord et al.	Feb 1995	A
5391250	Cheney, II et al.	Feb 1995	A
5408999	Singh et al.	Apr 1995	A
5411647	Johnson et al.	May 1995	A
5425868	Pedersen	Jun 1995	A
5431160	Wilkins	Jul 1995	A
5431921	Thombre	Jul 1995	A
5462645	Albery et al.	Oct 1995	A
5497772	Schulman et al.	Mar 1996	A
5507288	Bocker et al.	Apr 1996	A
5509410	Hill et al.	Apr 1996	A
5514718	Lewis et al.	May 1996	A
5531878	Vadgama et al.	Jul 1996	A
5568806	Cheney, II et al.	Oct 1996	A
5569186	Lord et al.	Oct 1996	A
5582184	Erickson et al.	Dec 1996	A
5586553	Halili et al.	Dec 1996	A
5593852	Heller et al.	Jan 1997	A
5609575	Larson et al.	Mar 1997	A
5628310	Rao et al.	May 1997	A
5653239	Pompei et al.	Aug 1997	A
5665222	Heller et al.	Sep 1997	A
5711001	Bussan et al.	Jan 1998	A
5711861	Ward et al.	Jan 1998	A
5733259	Valcke et al.	Mar 1998	A
5772586	Heinonen et al.	Jun 1998	A
5791344	Schulman et al.	Aug 1998	A
5899855	Brown	May 1999	A
5925021	Castellano et al.	Jul 1999	A
5935224	Svancarek et al.	Aug 1999	A
5942979	Luppino	Aug 1999	A
5957854	Besson et al.	Sep 1999	A
5964993	Blubaugh, Jr. et al.	Oct 1999	A
5965380	Heller et al.	Oct 1999	A
5971922	Arita et al.	Oct 1999	A
5995860	Sun et al.	Nov 1999	A
6001067	Shults et al.	Dec 1999	A
6024699	Surwit et al.	Feb 2000	A
6049727	Crothall	Apr 2000	A
6083710	Heller et al.	Jul 2000	A
6088608	Schulman et al.	Jul 2000	A
6091976	Pfeiffer et al.	Jul 2000	A
6093172	Funderburk et al.	Jul 2000	A
6103033	Say et al.	Aug 2000	A
6117290	Say et al.	Sep 2000	A
6119028	Schulman et al.	Sep 2000	A
6120676	Heller et al.	Sep 2000	A
6121009	Heller et al.	Sep 2000	A
6121611	Lindsay et al.	Sep 2000	A
6122351	Schlueter, Jr. et al.	Sep 2000	A
6134461	Say et al.	Oct 2000	A
6162611	Heller et al.	Dec 2000	A
6175752	Say et al.	Jan 2001	B1
6200265	Walsh et al.	Mar 2001	B1
6212416	Ward et al.	Apr 2001	B1
6219574	Cormier et al.	Apr 2001	B1
6233471	Berner et al.	May 2001	B1
6248067	Causey, III et al.	Jun 2001	B1
6275717	Gross et al.	Aug 2001	B1
6284478	Heller et al.	Sep 2001	B1
6293925	Safabash et al.	Sep 2001	B1
6295506	Heinonen et al.	Sep 2001	B1
6306104	Cunningham et al.	Oct 2001	B1
6309884	Cooper et al.	Oct 2001	B1
6329161	Heller et al.	Dec 2001	B1
6360888	McIvor et al.	Mar 2002	B1
6366794	Moussy et al.	Apr 2002	B1
6377828	Chaiken et al.	Apr 2002	B1
6379301	Worthington et al.	Apr 2002	B1
6424847	Mastrototaro et al.	Jul 2002	B1
6427088	Bowman, IV et al.	Jul 2002	B1
6440068	Brown et al.	Aug 2002	B1
6478736	Mault	Nov 2002	B1
6484046	Say et al.	Nov 2002	B1
6514718	Heller et al.	Feb 2003	B2
6544212	Galley et al.	Apr 2003	B2
6551494	Heller et al.	Apr 2003	B1
6558321	Burd et al.	May 2003	B1
6558351	Steil et al.	May 2003	B1
6560471	Heller et al.	May 2003	B1
6561978	Conn et al.	May 2003	B1
6562001	Lebel et al.	May 2003	B2
6564105	Starkweather et al.	May 2003	B2
6565509	Say et al.	May 2003	B1
6571128	Lebel et al.	May 2003	B2
6576101	Heller et al.	Jun 2003	B1
6577899	Lebel et al.	Jun 2003	B2
6579690	Bonnecaze et al.	Jun 2003	B1
6585644	Lebel et al.	Jul 2003	B2
6591125	Buse et al.	Jul 2003	B1
6595919	Berner et al.	Jul 2003	B2
6605200	Mao et al.	Aug 2003	B1
6605201	Mao et al.	Aug 2003	B1
6607509	Bobroff et al.	Aug 2003	B2
6610012	Mault	Aug 2003	B2
6633772	Ford et al.	Oct 2003	B2
6635014	Starkweather et al.	Oct 2003	B2
6648821	Lebel et al.	Nov 2003	B2
6654625	Say et al.	Nov 2003	B1
6659948	Lebel et al.	Dec 2003	B2
6668196	Villegas et al.	Dec 2003	B1
6687546	Lebel et al.	Feb 2004	B2
6689056	Kilcoyne et al.	Feb 2004	B1
6694191	Starkweather et al.	Feb 2004	B2
6695860	Ward et al.	Feb 2004	B1
6698269	Baber et al.	Mar 2004	B2
6702857	Brauker et al.	Mar 2004	B2
6733446	Lebel et al.	May 2004	B2
6740075	Lebel et al.	May 2004	B2
6741877	Shults et al.	May 2004	B1
6746582	Heller et al.	Jun 2004	B2
6758810	Lebel et al.	Jul 2004	B2
6770030	Schaupp et al.	Aug 2004	B1
6790178	Mault et al.	Sep 2004	B1
6809653	Mann et al.	Oct 2004	B1
6810290	Lebel et al.	Oct 2004	B2
6811533	Lebel et al.	Nov 2004	B2
6811534	Bowman, IV et al.	Nov 2004	B2
6813519	Lebel et al.	Nov 2004	B2
6862465	Shults et al.	Mar 2005	B2
6873268	Lebel et al.	Mar 2005	B2
6881551	Heller et al.	Apr 2005	B2
6892085	McIvor et al.	May 2005	B2
6895263	Shin et al.	May 2005	B2
6895265	Silver	May 2005	B2
6931327	Goode, Jr. et al.	Aug 2005	B2
6932894	Mao et al.	Aug 2005	B2
6936006	Sabra	Aug 2005	B2
6950708	Bowman, IV et al.	Sep 2005	B2
6958705	Lebel et al.	Oct 2005	B2
6968294	Gutta et al.	Nov 2005	B2
6971274	Olin	Dec 2005	B2
6974437	Lebel et al.	Dec 2005	B2
6990366	Say et al.	Jan 2006	B2
6997907	Safabash et al.	Feb 2006	B2
6998247	Monfre et al.	Feb 2006	B2
7003336	Holker et al.	Feb 2006	B2
7003340	Say et al.	Feb 2006	B2
7003341	Say et al.	Feb 2006	B2
7022072	Fox et al.	Apr 2006	B2
7024245	Lebel et al.	Apr 2006	B2
7029444	Shin et al.	Apr 2006	B2
7041068	Freeman et al.	May 2006	B2
7052483	Wojcik	May 2006	B2
7056302	Douglas	Jun 2006	B2
7074307	Simpson et al.	Jul 2006	B2
7081195	Simpson et al.	Jul 2006	B2
7098803	Mann et al.	Aug 2006	B2
7108778	Simpson et al.	Sep 2006	B2
7110803	Shults et al.	Sep 2006	B2
7113821	Sun et al.	Sep 2006	B1
7118667	Lee	Oct 2006	B2
7134999	Brauker et al.	Nov 2006	B2
7136689	Shults et al.	Nov 2006	B2
7171274	Starkweather et al.	Jan 2007	B2
7190988	Say et al.	Mar 2007	B2
7192450	Brauker et al.	Mar 2007	B2
7198606	Boecker et al.	Apr 2007	B2
7225535	Feldman et al.	Jun 2007	B2
7226978	Tapsak et al.	Jun 2007	B2
7267665	Steil et al.	Sep 2007	B2
7276029	Goode, Jr. et al.	Oct 2007	B2
7299082	Feldman et al.	Nov 2007	B2
7310544	Brister et al.	Dec 2007	B2
7335294	Heller et al.	Feb 2008	B2
7354420	Steil et al.	Apr 2008	B2
7364592	Carr-Brendel et al.	Apr 2008	B2
7366556	Brister et al.	Apr 2008	B2
7379765	Petisce et al.	May 2008	B2
7402153	Steil et al.	Jul 2008	B2
7424318	Brister et al.	Sep 2008	B2
7460898	Brister et al.	Dec 2008	B2
7467003	Brister et al.	Dec 2008	B2
7471972	Rhodes et al.	Dec 2008	B2
7494465	Brister et al.	Feb 2009	B2
7497827	Brister et al.	Mar 2009	B2
7519408	Rasdal et al.	Apr 2009	B2
7547281	Hayes et al.	Jun 2009	B2
7569030	Lebel et al.	Aug 2009	B2
7583990	Goode, Jr. et al.	Sep 2009	B2
7591801	Brauker et al.	Sep 2009	B2
7599726	Goode, Jr. et al.	Oct 2009	B2
7613491	Boock et al.	Nov 2009	B2
7615007	Shults et al.	Nov 2009	B2
7618369	Hayter et al.	Nov 2009	B2
7632228	Brauker et al.	Dec 2009	B2
7637868	Saint et al.	Dec 2009	B2
7640048	Dobbles et al.	Dec 2009	B2
7651596	Petisce et al.	Jan 2010	B2
7654956	Brister et al.	Feb 2010	B2
7657297	Simpson et al.	Feb 2010	B2
7711402	Shults et al.	May 2010	B2
7713574	Brister et al.	May 2010	B2
7715893	Kamath et al.	May 2010	B2
20020019022	Dunn et al.	Feb 2002	A1
20020042090	Heller et al.	Apr 2002	A1
20020103499	Perez et al.	Aug 2002	A1
20020106709	Potts et al.	Aug 2002	A1
20020128594	Das et al.	Sep 2002	A1
20020161288	Shin et al.	Oct 2002	A1
20020169635	Shillingburg	Nov 2002	A1
20030004403	Drinan et al.	Jan 2003	A1
20030023317	Brauker et al.	Jan 2003	A1
20030032874	Rhodes et al.	Feb 2003	A1
20030042137	Mao et al.	Mar 2003	A1
20030065308	Lebel et al.	Apr 2003	A1
20030100821	Heller et al.	May 2003	A1
20030125612	Fox et al.	Jul 2003	A1
20030130616	Steil et al.	Jul 2003	A1
20030134347	Heller et al.	Jul 2003	A1
20030168338	Gao et al.	Sep 2003	A1
20030176933	Lebel et al.	Sep 2003	A1
20030187338	Say et al.	Oct 2003	A1
20030199790	Boecker et al.	Oct 2003	A1
20030208113	Mault et al.	Nov 2003	A1
20030212317	Kovatchev et al.	Nov 2003	A1
20030212379	Bylund et al.	Nov 2003	A1
20030216630	Jersey-Willuhn et al.	Nov 2003	A1
20030217966	Tapsak et al.	Nov 2003	A1
20040010207	Flaherty et al.	Jan 2004	A1
20040011671	Shults et al.	Jan 2004	A1
20040039298	Abreu	Feb 2004	A1
20040040840	Mao et al.	Mar 2004	A1
20040045879	Shults et al.	Mar 2004	A1
20040064068	DeNuzzio et al.	Apr 2004	A1
20040106858	Say et al.	Jun 2004	A1
20040122353	Shahmirian et al.	Jun 2004	A1
20040133164	Funderburk et al.	Jul 2004	A1
20040138588	Saikley et al.	Jul 2004	A1
20040146909	Duong et al.	Jul 2004	A1
20040152622	Keith et al.	Aug 2004	A1
20040167801	Say et al.	Aug 2004	A1
20040171921	Say et al.	Sep 2004	A1
20040176672	Silver et al.	Sep 2004	A1
20040186362	Brauker et al.	Sep 2004	A1
20040186365	Jin et al.	Sep 2004	A1
20040193025	Steil et al.	Sep 2004	A1
20040193090	Lebel et al.	Sep 2004	A1
20040197846	Hockersmith et al.	Oct 2004	A1
20040199059	Brauker et al.	Oct 2004	A1
20040204687	Mogensen et al.	Oct 2004	A1
20040225338	Lebel et al.	Nov 2004	A1
20040236200	Say et al.	Nov 2004	A1
20040254433	Bandis et al.	Dec 2004	A1
20040267300	Mace	Dec 2004	A1
20050004439	Shin et al.	Jan 2005	A1
20050004494	Perez et al.	Jan 2005	A1
20050010269	Lebel et al.	Jan 2005	A1
20050024227	Dunstan	Feb 2005	A1
20050027177	Shin et al.	Feb 2005	A1
20050031689	Shults et al.	Feb 2005	A1
20050038332	Saidara et al.	Feb 2005	A1
20050043598	Goode, Jr. et al.	Feb 2005	A1
20050090607	Tapsak et al.	Apr 2005	A1
20050096511	Fox et al.	May 2005	A1
20050096512	Fox et al.	May 2005	A1
20050112169	Brauker et al.	May 2005	A1
20050113653	Fox et al.	May 2005	A1
20050114068	Chey et al.	May 2005	A1
20050121322	Say et al.	Jun 2005	A1
20050131346	Douglas	Jun 2005	A1
20050143635	Kamath et al.	Jun 2005	A1
20050176136	Burd et al.	Aug 2005	A1
20050177398	Watanabe et al.	Aug 2005	A1
20050182306	Sloan	Aug 2005	A1
20050187720	Goode, Jr. et al.	Aug 2005	A1
20050192494	Ginsberg	Sep 2005	A1
20050192557	Brauker et al.	Sep 2005	A1
20050195930	Spital et al.	Sep 2005	A1
20050199494	Say et al.	Sep 2005	A1
20050203360	Brauker et al.	Sep 2005	A1
20050239154	Feldman et al.	Oct 2005	A1
20050241957	Mao et al.	Nov 2005	A1
20050245795	Goode, Jr. et al.	Nov 2005	A1
20050245799	Brauker et al.	Nov 2005	A1
20050245839	Stivoric et al.	Nov 2005	A1
20050245904	Estes et al.	Nov 2005	A1
20050287620	Heller et al.	Dec 2005	A1
20060001538	Kraft et al.	Jan 2006	A1
20060004270	Bedard et al.	Jan 2006	A1
20060015020	Neale et al.	Jan 2006	A1
20060015024	Brister et al.	Jan 2006	A1
20060016700	Brister et al.	Jan 2006	A1
20060019327	Brister et al.	Jan 2006	A1
20060020186	Brister et al.	Jan 2006	A1
20060020187	Brister et al.	Jan 2006	A1
20060020188	Kamath et al.	Jan 2006	A1
20060020189	Brister et al.	Jan 2006	A1
20060020190	Kamath et al.	Jan 2006	A1
20060020191	Brister et al.	Jan 2006	A1
20060020192	Brister et al.	Jan 2006	A1
20060029177	Cranford, Jr. et al.	Feb 2006	A1
20060031094	Cohen et al.	Feb 2006	A1
20060036139	Brister et al.	Feb 2006	A1
20060036140	Brister et al.	Feb 2006	A1
20060036141	Kamath et al.	Feb 2006	A1
20060036142	Brister et al.	Feb 2006	A1
20060036143	Brister et al.	Feb 2006	A1
20060036144	Brister et al.	Feb 2006	A1
20060036145	Brister et al.	Feb 2006	A1
20060155180	Brister et al.	Jul 2006	A1
20060166629	Reggiardo	Jul 2006	A1
20060173260	Gaoni et al.	Aug 2006	A1
20060173406	Hayes et al.	Aug 2006	A1
20060173444	Choy et al.	Aug 2006	A1
20060183985	Brister et al.	Aug 2006	A1
20060189863	Peyser et al.	Aug 2006	A1
20060222566	Brauker et al.	Oct 2006	A1
20060224109	Steil et al.	Oct 2006	A1
20060229512	Petisce et al.	Oct 2006	A1
20060247508	Fennell	Nov 2006	A1
20060272652	Stocker et al.	Dec 2006	A1
20070016381	Kamath et al.	Jan 2007	A1
20070027381	Stafford	Feb 2007	A1
20070033074	Nitzan et al.	Feb 2007	A1
20070060814	Stafford	Mar 2007	A1
20070066873	Kamath et al.	Mar 2007	A1
20070071681	Gadkar et al.	Mar 2007	A1
20070073129	Shah et al.	Mar 2007	A1
20070078320	Stafford	Apr 2007	A1
20070078321	Mazza et al.	Apr 2007	A1
20070078322	Stafford	Apr 2007	A1
20070078323	Reggiardo et al.	Apr 2007	A1
20070106135	Sloan et al.	May 2007	A1
20070124002	Estes et al.	May 2007	A1
20070149875	Ouyang et al.	Jun 2007	A1
20070163880	Woo et al.	Jul 2007	A1
20070168224	Letzt et al.	Jul 2007	A1
20070173706	Neinast et al.	Jul 2007	A1
20070173761	Kanderian et al.	Jul 2007	A1
20070179349	Hoyme et al.	Aug 2007	A1
20070179352	Randlov et al.	Aug 2007	A1
20070191701	Feldman et al.	Aug 2007	A1
20070203407	Hoss et al.	Aug 2007	A1
20070203966	Brauker et al.	Aug 2007	A1
20070232880	Siddiqui et al.	Oct 2007	A1
20070235331	Simpson et al.	Oct 2007	A1
20070249922	Peyser et al.	Oct 2007	A1
20080009692	Stafford	Jan 2008	A1
20080017522	Heller et al.	Jan 2008	A1
20080021666	Goode, Jr. et al.	Jan 2008	A1
20080029391	Mao et al.	Feb 2008	A1
20080033254	Kamath et al.	Feb 2008	A1
20080039702	Hayter et al.	Feb 2008	A1
20080045824	Tapsak et al.	Feb 2008	A1
20080058625	McGarraugh et al.	Mar 2008	A1
20080064937	McGarraugh et al.	Mar 2008	A1
20080071156	Brister et al.	Mar 2008	A1
20080071157	McGarraugh et al.	Mar 2008	A1
20080071158	McGarraugh et al.	Mar 2008	A1
20080081977	Hayter et al.	Apr 2008	A1
20080083617	Simpson et al.	Apr 2008	A1
20080086042	Brister et al.	Apr 2008	A1
20080086044	Brister et al.	Apr 2008	A1
20080086273	Shults et al.	Apr 2008	A1
20080097289	Steil et al.	Apr 2008	A1
20080108942	Brister et al.	May 2008	A1
20080154513	Kovatchev et al.	Jun 2008	A1
20080167543	Say et al.	Jul 2008	A1
20080172205	Breton et al.	Jul 2008	A1
20080183060	Steil et al.	Jul 2008	A1
20080183061	Goode et al.	Jul 2008	A1
20080183399	Goode et al.	Jul 2008	A1
20080188731	Brister et al.	Aug 2008	A1
20080188796	Steil et al.	Aug 2008	A1
20080189051	Goode et al.	Aug 2008	A1
20080194935	Brister et al.	Aug 2008	A1
20080194936	Goode et al.	Aug 2008	A1
20080194937	Goode et al.	Aug 2008	A1
20080194938	Brister et al.	Aug 2008	A1
20080195232	Carr-Brendel et al.	Aug 2008	A1
20080195967	Goode et al.	Aug 2008	A1
20080197024	Simpson et al.	Aug 2008	A1
20080200788	Brister et al.	Aug 2008	A1
20080200789	Brister et al.	Aug 2008	A1
20080200791	Simpson et al.	Aug 2008	A1
20080208025	Shults et al.	Aug 2008	A1
20080208113	Damiano et al.	Aug 2008	A1
20080214915	Brister et al.	Sep 2008	A1
20080214918	Brister et al.	Sep 2008	A1
20080228051	Shults et al.	Sep 2008	A1
20080228054	Shults et al.	Sep 2008	A1
20080242961	Brister et al.	Oct 2008	A1
20080255434	Hayter et al.	Oct 2008	A1
20080255437	Hayter	Oct 2008	A1
20080255808	Hayter	Oct 2008	A1
20080256048	Hayter	Oct 2008	A1
20080262469	Brister et al.	Oct 2008	A1
20080275313	Brister et al.	Nov 2008	A1
20080287761	Hayter	Nov 2008	A1
20080287762	Hayter	Nov 2008	A1
20080287763	Hayter	Nov 2008	A1
20080287764	Rasdal et al.	Nov 2008	A1
20080287765	Rasdal et al.	Nov 2008	A1
20080287766	Rasdal et al.	Nov 2008	A1
20080288180	Hayter	Nov 2008	A1
20080288204	Hayter et al.	Nov 2008	A1
20080296155	Shults et al.	Dec 2008	A1
20080306368	Goode et al.	Dec 2008	A1
20080306434	Dobbles et al.	Dec 2008	A1
20080306435	Kamath et al.	Dec 2008	A1
20080306444	Brister et al.	Dec 2008	A1
20080312841	Hayter	Dec 2008	A1
20080312842	Hayter	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
20090012379	Goode et al.	Jan 2009	A1
20090018424	Kamath et al.	Jan 2009	A1
20090018425	Ouyang et al.	Jan 2009	A1
20090030294	Petisce et al.	Jan 2009	A1
20090033482	Hayter et al.	Feb 2009	A1
20090036747	Hayter et al.	Feb 2009	A1
20090036758	Brauker et al.	Feb 2009	A1
20090036760	Hayter	Feb 2009	A1
20090036763	Brauker et al.	Feb 2009	A1
20090043181	Brauker et al.	Feb 2009	A1
20090043182	Brauker et al.	Feb 2009	A1
20090043525	Brauker et al.	Feb 2009	A1
20090043541	Brauker et al.	Feb 2009	A1
20090043542	Brauker et al.	Feb 2009	A1
20090045055	Rhodes et al.	Feb 2009	A1
20090055149	Hayter et al.	Feb 2009	A1
20090062633	Brauker et al.	Mar 2009	A1
20090062635	Brauker et al.	Mar 2009	A1
20090062767	VanAntwerp et al.	Mar 2009	A1
20090063402	Hayter	Mar 2009	A1
20090076356	Simpson et al.	Mar 2009	A1
20090076360	Brister et al.	Mar 2009	A1
20090076361	Kamath et al.	Mar 2009	A1
20090099436	Brister et al.	Apr 2009	A1
20090105636	Hayter et al.	Apr 2009	A1
20090124877	Goode et al.	May 2009	A1
20090124878	Goode et al.	May 2009	A1
20090124879	Brister et al.	May 2009	A1
20090124964	Leach et al.	May 2009	A1
20090131768	Simpson et al.	May 2009	A1
20090131769	Leach et al.	May 2009	A1
20090131776	Simpson et al.	May 2009	A1
20090131777	Simpson et al.	May 2009	A1
20090137886	Shariati et al.	May 2009	A1
20090137887	Shariati et al.	May 2009	A1
20090143659	Li et al.	Jun 2009	A1
20090143660	Brister et al.	Jun 2009	A1
20090156919	Brister et al.	Jun 2009	A1
20090156924	Shariati et al.	Jun 2009	A1
20090163790	Brister et al.	Jun 2009	A1
20090163791	Brister et al.	Jun 2009	A1
20090164190	Hayter	Jun 2009	A1
20090164239	Hayter et al.	Jun 2009	A1
20090164251	Hayter	Jun 2009	A1
20090178459	Li et al.	Jul 2009	A1
20090182217	Li et al.	Jul 2009	A1
20090192366	Mensinger et al.	Jul 2009	A1
20090192380	Shariati et al.	Jul 2009	A1
20090192722	Shariati et al.	Jul 2009	A1
20090192724	Brauker et al.	Jul 2009	A1
20090192745	Kamath et al.	Jul 2009	A1
20090192751	Kamath et al.	Jul 2009	A1
20090198118	Hayter et al.	Aug 2009	A1
20090203981	Brauker et al.	Aug 2009	A1
20090204341	Brauker et al.	Aug 2009	A1
20090216103	Brister et al.	Aug 2009	A1
20090240120	Mensinger et al.	Sep 2009	A1
20090240128	Mensinger et al.	Sep 2009	A1
20090240193	Mensinger et al.	Sep 2009	A1
20090242399	Kamath et al.	Oct 2009	A1
20090242425	Kamath et al.	Oct 2009	A1
20090247855	Boock et al.	Oct 2009	A1
20090247856	Boock et al.	Oct 2009	A1
20090287073	Boock et al.	Nov 2009	A1
20090287074	Shults et al.	Nov 2009	A1
20090299155	Yang et al.	Dec 2009	A1
20090299156	Simpson et al.	Dec 2009	A1
20090299162	Brauker et al.	Dec 2009	A1
20090299276	Brauker et al.	Dec 2009	A1
20100010324	Brauker et al.	Jan 2010	A1
20100010331	Brauker et al.	Jan 2010	A1
20100010332	Brauker et al.	Jan 2010	A1
20100016687	Brauker et al.	Jan 2010	A1
20100016698	Rasdal et al.	Jan 2010	A1
20100022855	Brauker et al.	Jan 2010	A1
20100030038	Brauker et al.	Feb 2010	A1
20100030053	Goode, Jr. et al.	Feb 2010	A1
20100030484	Brauker et al.	Feb 2010	A1
20100030485	Brauker et al.	Feb 2010	A1
20100036215	Goode, Jr. et al.	Feb 2010	A1
20100036216	Goode, Jr. et al.	Feb 2010	A1
20100036222	Goode, Jr. et al.	Feb 2010	A1
20100036223	Goode, Jr. et al.	Feb 2010	A1
20100036225	Goode, Jr. et al.	Feb 2010	A1
20100041971	Goode, Jr. et al.	Feb 2010	A1
20100045465	Brauker et al.	Feb 2010	A1
20100049024	Saint et al.	Feb 2010	A1
20100057040	Hayter	Mar 2010	A1
20100057041	Hayter	Mar 2010	A1
20100057042	Hayter	Mar 2010	A1
20100057044	Hayter	Mar 2010	A1
20100057057	Hayter et al.	Mar 2010	A1
20100063373	Kamath et al.	Mar 2010	A1
20100076283	Simpson et al.	Mar 2010	A1
20100081906	Hayter et al.	Apr 2010	A1
20100081908	Dobbles et al.	Apr 2010	A1
20100081910	Brister et al.	Apr 2010	A1
20100087724	Brauker et al.	Apr 2010	A1
20100096259	Zhang et al.	Apr 2010	A1
20100099970	Shults et al.	Apr 2010	A1
20100099971	Shults et al.	Apr 2010	A1
20100119693	Tapsak et al.	May 2010	A1
20100121169	Petisce et al.	May 2010	A1

Foreign Referenced Citations (28)

Number	Date	Country
4401400	Jul 1995	DE
0098592	Jan 1984	EP
0127958	Dec 1984	EP
0320109	Jun 1989	EP
0353328	Feb 1990	EP
0390390	Oct 1990	EP
0396788	Nov 1990	EP
0286118	Jan 1995	EP
1048264	Nov 2000	EP
WO-9625089	Aug 1996	WO
WO-9635370	Nov 1996	WO
WO-9835053	Aug 1998	WO
WO-9956613	Nov 1999	WO
WO-0049940	Aug 2000	WO
WO-0059370	Oct 2000	WO
WO-0078992	Dec 2000	WO
WO-0152935	Jul 2001	WO
WO-0154753	Aug 2001	WO
WO-0216905	Feb 2002	WO
WO-02058537	Aug 2002	WO
WO-03076893	Sep 2003	WO
WO-03082091	Oct 2003	WO
WO-03085372	Oct 2003	WO
WO 2004061420	Jul 2004	WO
WO 2005041766	May 2005	WO
WO 2005089103	Sep 2005	WO
WO 2006024671	Mar 2006	WO
WO 2008138006	Nov 2008	WO

Related Publications (1)

	Number	Date	Country
	20090296742 A1	Dec 2009	US

Close proximity communication device and methods

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

US Classifications

Field of Search

US

International Classifications

Term Extension

Abstract

Description

Claims

US Referenced Citations (571)

Foreign Referenced Citations (28)

Related Publications (1)