This document relates generally to communication systems and particularly, but not by way of limitation, to a system and method for telemetry of analog and digital data, such as between implantable and remote devices.
Electronic devices are often implanted within a human or animal for acquiring biological data or for providing therapy. It is often desirable for such an implanted device to wirelessly communicate with a remote external device. For example, the implanted device may communicate the acquired biological data to the remote device for processing and/or display or other user output. In another example, the implanted device may communicate to the remote device information about how the implanted device is configured. In a further example, the external device may communicate to the implanted device instructions for performing subsequent operations. Because the implanted device is often battery-powered, there is a need for the communication protocol to operate without consuming excessive energy, which would deplete the battery and, therefore, shorten the usable life of the implanted device. However, such low-power communication techniques may be particularly sensitive to environmental noise. Such noise can disrupt the data communication and can even corrupt the data being transmitted. Therefore, there is also a need for a low-power communication protocol that allows any such detected noise to be evaluated to determine whether the data being transmitted risks being corrupted.
This document discusses a system and method that involves transceiving successive first and second synchronization signals defining endpoints of a frame. A digital signal is transceived by a modulating time interval between portions of the first and second synchronization signals. A first data pulse is transceived during the frame. A relative position in the frame of the first data pulse represents a first analog signal. The system and method discussed herein is particularly suited for the low-power transceiving of analog biological data from an implantable device to an external or other remote device. A further example permits noise and/or signal strength manifested during such communication to be quantified and evaluated, such as to qualify the data being transceived. Other aspects of the invention will be apparent on reading the following detailed description of the invention and viewing the drawings that form a part thereof.
In the drawings, which are offered by way of example, and not by way of limitation, and which are not necessarily drawn to scale, like numerals describe substantially similar components throughout the several views. Like numerals having different letter suffixes represent different instances of substantially similar components.
In the following detailed description, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that the embodiments may be combined, or that other embodiments may be utilized and that structural, logical and electrical changes may be made without departing from the spirit and scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
In this document, the terms “transceive,” “transceiving,” and “transceiver” refer to transmitting and/or receiving data. That is, these terms include all of: (1) transmitting, but not receiving; (2) receiving, but not transmitting; and, (3) both transmitting and receiving.
Remote device 104 (which may also be implanted in the human or animal subject or which is instead located external to the subject) includes a transceiver circuit 116 that is communicatively couplable to transceiver 110 of implantable device 102. Remote device 104 also includes a controller circuit 118, which is coupled to transceiver 116 via node/bus 120, and which is coupled to a user input/output (I/O) device 122 via node/bus 124. Controller 118 is capable of sequencing through various control states such as, for example, by using a digital microprocessor having executable instructions stored in an associated instruction memory circuit, a microsequencer, or a state machine. In operation, by execution of these instructions, controller 118 provides control signals to transceiver 116 and/or I/O device 122 for controlling and timing their operation.
In one example, implantable device 102 is configured to transmit both analog and digital information to be received by remote device 104. Controller 112 times the transmission of data pulses by transceiver 110, and controller 118 interprets the reception of these data pulses by transceiver 116 according to a predefined communication protocol.
Similarly, the relative position at which data pulse 206 is received within data window 208 decodes the analog signal. In one example, the analog signal encoded, communicated, and decoded is a signal representative of the detected biological signal, as discussed above. Moreover, as illustrated in
In one suitable example, but not by way of limitation, each frame includes two data windows 208. In this example, controller 112 includes a 32.768 kHz crystal oscillator clock circuit in addition to its digital sequencer. Modulation of the length of frame 200 to communicate the digital signal includes either shortening or lengthening the length of frame 200 by one clock cycle (e.g., about 30.52 microseconds). Thus, in this example, the nominal frame length 201A is about 1587 microseconds, the longer frame length 201B is about 1617 microseconds, the shorter frame length 201C is about 1556 microseconds, the synchronization interval is about 183 microseconds, the guardbands are about 213 microseconds, and the data windows are about 366 microseconds.
In one example, the variability characteristic is compared to a predetermined threshold value. If the variability in the duration of the synchronization intervals exceeds the threshold value, a noise indicator value of “1” is output at node 412, otherwise a value of “0” is output. Thus, in this example, the binary noise indicator represents the validity of the analog data being communicated between transceivers 110 and 116. In another example, the variability characteristic itself, which takes on more than two states, is used as a figure of merit of the quality of the analog data being communicated between transceivers 110 and 116. In this manner, the variability characteristic itself may be used in subsequent processing of the transmitted analog data. For example, a larger jitter between synchronization pulses leads to a larger variability characteristic, which may trigger a longer averaging of the analog signal being transmitted to compensate for the increased noise. In this manner, controller 118 may include noise detection components for determining the integrity of the analog data being communicated between transceivers 110 and 116. Among other things, this information may be used to reject transmitted analog data, to qualify transmitted analog data, to ascertain or mark a range of error associated with transmitted analog data, or to compensate for error associated with transmitted analog data.
In one example, as illustrated in
Although the above examples have highlighted, for brevity, data transmission by device 102 for reception by remote device 104, it is understood that the above-described communication protocol is also applicable for data transmission by remote device 104 to device 102.
In a further example, this communication protocol also includes a higher level protocol for further defining transception of the digital data, over a plurality of frames 200, by modulating the length of the frame 200.
Table 1 illustrates one example of how command header 504 is defined for transmitting commands including system control information from device 104 to device 102, such as for configuring an operational mode, requesting return data from device 102, or reading or writing identification information to or from the particular device 102.
Thus, Table 1 illustrates one example of how command header 504 is used to configure controller 112 and/or another component of device 102 into one of several possible modes of operation, to interface with an EEPROM or other memory included within or coupled to controller 112, and/or to interface with one or more scannable registers in memory associated with controller 112.
Table 2 illustrates one example of how command header 604 is defined for transmitting commands from device 102 to device 104, such as for identifying the nature of one or more following data fields.
Thus, Table 2 illustrates one example of how command header 604 is used to identify subsequently transmitted data field(s) 606, data from the EEPROM or other memory 126 in device 102, or data from scan-chain configured memory registers in device 102.
It is to be understood that the above description is intended to be illustrative, and not restrictive. For example, the above-discussed embodiments may be used in combination with each other. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. For example, although the data transmission protocol discussed herein has been illustrated in terms of wireless communication techniques, the protocol could also be implemented with a wired electrical or optical connection between transceivers. The scope of the invention should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.”
Number | Name | Date | Kind |
---|---|---|---|
4281664 | Duggan | Aug 1981 | A |
4374382 | Markowitz | Feb 1983 | A |
4513403 | Troy | Apr 1985 | A |
4531523 | Anderson | Jul 1985 | A |
4556063 | Thompson et al. | Dec 1985 | A |
RE32361 | Duggan | Feb 1987 | E |
5107833 | Barsness | Apr 1992 | A |
5127404 | Wyborny et al. | Jul 1992 | A |
5137022 | Henry | Aug 1992 | A |
5168871 | Grevious | Dec 1992 | A |
5241961 | Henry | Sep 1993 | A |
5292343 | Blanchette et al. | Mar 1994 | A |
5314450 | Thompson | May 1994 | A |
5324315 | Grevious | Jun 1994 | A |
5330513 | Nichols et al. | Jul 1994 | A |
5350411 | Ryan et al. | Sep 1994 | A |
5354319 | Wyborny et al. | Oct 1994 | A |
5383909 | Keimel | Jan 1995 | A |
5402794 | Wahlstrand et al. | Apr 1995 | A |
5411536 | Armstrong | May 1995 | A |
5522866 | Fernald | Jun 1996 | A |
5611346 | Heikkila et al. | Mar 1997 | A |
5620472 | Rahbari | Apr 1997 | A |
5684871 | Devon et al. | Nov 1997 | A |
5752976 | Duffin et al. | May 1998 | A |
5752977 | Grevious et al. | May 1998 | A |
5766232 | Grevious et al. | Jun 1998 | A |
5782890 | Wahlstrand et al. | Jul 1998 | A |
5861019 | Sun et al. | Jan 1999 | A |
5899931 | Deschamp et al. | May 1999 | A |
5919214 | Ciciarelli et al. | Jul 1999 | A |
5999857 | Weijand et al. | Dec 1999 | A |
6009350 | Renken | Dec 1999 | A |
6083248 | Thompson | Jul 2000 | A |
6115636 | Ryan | Sep 2000 | A |
6167310 | Grevious | Dec 2000 | A |
6167312 | Goedeke | Dec 2000 | A |
6169925 | Villaseca et al. | Jan 2001 | B1 |
6201993 | Kruse et al. | Mar 2001 | B1 |
Number | Date | Country |
---|---|---|
3816018 | Nov 1988 | DE |
268 972 | Jun 1988 | EP |
WO 9428968 | Dec 1994 | WO |
Number | Date | Country | |
---|---|---|---|
20050261749 A1 | Nov 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09968644 | Oct 2001 | US |
Child | 11193818 | US |