System and method for RF wake-up of implantable medical device

Information

  • Patent Grant
  • 8639339
  • Patent Number
    8,639,339
  • Date Filed
    Tuesday, November 20, 2012
    11 years ago
  • Date Issued
    Tuesday, January 28, 2014
    10 years ago
Abstract
A telemetry system is presented for enabling wireless communications between an implantable medical device and an external device in a manner which reduces the power requirements of the implantable device by duty cycling its wireless communication circuitry. A wakeup scheme for the implantable device is provided in which the external device transmits a data segment containing a repeating sequence of special wakeup characters in order to establish a communications session with the implantable device. The wakeup scheme may be designed to operate in the context of a handshaking protocol for collision avoidance.
Description
FIELD OF THE INVENTION

This invention pertains to implantable medical devices such as cardiac pacemakers and implantable cardioverter/defibrillators. In particular, the invention relates to a system and method for implementing telemetry in such devices.


BACKGROUND

Implantable medical devices, including cardiac rhythm management devices such as pacemakers and implantable cardioverter/defibrillators, typically have the capability to communicate data with a device called an external programmer via a radio-frequency telemetry link. One use of such an external programmer is to program the operating parameters of an implanted medical device. For example, the pacing mode and other operating characteristics of a pacemaker are typically modified after implantation in this manner. Modern implantable devices also include the capability for bidirectional communication so that information can be transmitted to the programmer from the implanted device. Among the data that may typically be telemetered from an implantable device are various operating parameters and physiological data, the latter either collected in real-time or stored from previous monitoring operations.


Telemetry systems for implantable medical devices utilize radio-frequency (RF) energy to enable bidirectional communication between the implantable device and an external programmer. An exemplary telemetry system for an external programmer and a cardiac pacemaker is described in U.S. Pat. No. 4,562,841, issued to Brockway et al. and assigned to Cardiac Pacemakers, Inc., the disclosure of which is incorporated herein by reference. A radio-frequency carrier is modulated with digital information, typically by amplitude shift keying where the presence or absence of pulses in the signal constitute binary symbols or bits. The external programmer transmits and receives the radio signal with an antenna incorporated into a wand that can be positioned in proximity to the implanted device. The implantable device also generates and receives radio signals by means of an antenna, typically formed by a wire coil wrapped around the periphery of the inside of the device casing. Most conventional radio-frequency telemetry systems used for implantable medical devices such as cardiac pacemakers utilize inductive coupling between the antennas of the implantable device and an external programmer in order to transmit and receive RF signals. Because the induction field produced by a transmitting antenna falls off rapidly with distance, such systems require close proximity between the implantable device and a wand antenna of the external programmer in order to work properly, usually on the order of a few inches. This requirement is an inconvenience for a clinician and limits the situations in which telemetry can take place.


Wireless radio-frequency communication over greater distances requires the use of far-field telemetry. Communication using far-field radiation can take place over much greater distances, which makes it more convenient to use an external programmer. Also, the increased communication range makes possible other applications of the telemetry system such as remote monitoring of patients and communication with other types of external devices such as network access points. In order for a substantial portion of the energy delivered to an antenna to be emitted as far-field radiation, the wavelength of the driving signal should not be very much larger than the length of the antenna. Far-field radio-frequency communications with an antenna of a size suitable for use in an implantable device therefore requires a carrier in the frequency range of between a few hundred MHz to a few GHz. Active transmitters and receivers for this frequency range require special RF components (typically including SiGe or GaAs semiconductor devices) that consume a significant amount of power (typically tens of milliwatts). Implantable medical devices, however, are powered by a battery contained within the housing of the device that can only supply a limited amount of continuous power before it fails. When the battery fails in an implantable device, it must be replaced which necessitates a re-implantation procedure. Power conservation is thus an important design objective in wireless telemetry systems for implantable medical devices.


SUMMARY

The present invention relates to a telemetry system for enabling radio-frequency (RF) communications between an implantable medical device and an external device in a manner which reduces the power requirements of the implantable device. In accordance with the invention, the external device is programmed to transmit a data segment containing a repeating sequence of special wakeup characters in order to establish a communications session with the implantable device. The implantable device is programmed to power up its transmitter and receiver for a specified time window at periodic intervals defined by the wakeup timer and wait for receipt of one of the special wakeup characters transmitted by the external device. The implantable device maintains its transmitter and receiver in a powered-up state upon receipt of a special character and for as long as consecutive special wakeup characters continue to be received, to transmit an acknowledge signal to the external device upon receipt of at least one character other than a special wakeup character, and then to wait a specified period of time for a response from the external device. The external device and the implantable device then attempt to establish a communications session when a response to the acknowledge signal is received by the implantable device.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of a telemetry system for an implantable device and an external device.



FIG. 2 illustrates a handshaking protocol for collision avoidance.



FIG. 3 illustrates a wakeup scheme in accordance with the invention.





DETAILED DESCRIPTION

The present invention is a system and method for providing far-field RF telemetry between an implantable medical device and an external device in which power consumption by the implantable device is lessened by managing the duty cycle of the RF transmitting and receiving components. Long-range RF telemetry circuitry (i.e., the transmitter and receiver) typically requires power on the order of tens of milliwatts in order to operate. Implantable cardiac devices in use today, on the other hand, are usually designed to operate with average power in the microwatt range. This means that the RF telemetry circuitry must be duty cycled down in order to meet the power budget of such devices. Previous examples of duty cycling for implantable devices are described in U.S. Pat. No. 5,342,408 and U.S. patent application Ser. No. 10/025,223, entitled “A TELEMETRY DUTY CYCLE MANAGEMENT SYSTEM FOR AN IMPLANTABLE MEDICAL DEVICE”, presently assigned to Cardiac Pacemakers, Inc., and hereby incorporated by reference.


The RF telemetry circuitry of an implantable device can either be powered up or down, referred to as awake and sleep states, respectively. Duty cycling of the implantable device's RF telemetry circuitry can be implemented by a wakeup timer which defines periodic wakeup intervals at which the implantable device powers up its RF circuitry and listens for a transmission from an external device for a specified period of time, referred to as a wakeup window. Upon acknowledging the transmission from the external device, a communications session can be established by a handshaking protocol, and data can then be transferred between the devices. In order to minimize power consumption, it is desirable for the RF circuitry of the implantable device to be powered up for as short a time as possible at each wakeup interval while still being able to reliably recognize session requests from the external device. If the implantable device recognizes a session request from the external device during its wakeup window, it remains awake long enough to establish a communications session with the external device; otherwise, the implantable device returns to a sleep state until the next wakeup interval occurs.


In accordance with the present invention, the external device is programmed to transmit a data frame containing a repeating sequence of special wakeup characters when it is desired to establish a communications session with the implantable device. The implantable device is programmed to power up its transmitter and receiver for a specified wakeup window at periodic intervals defined by its wakeup timer and wait for receipt of one of the special wakeup characters transmitted by the external device. The implantable device maintains its transmitter and receiver in a powered-up state upon receipt of a special character and for as long as consecutive special wakeup characters continue to be received, and transmits an acknowledge signal to the external device upon receipt of at least one character other than a special wakeup character. After transmitting the acknowledge signal, the implantable device then waits a specified period of time for a response from the external device. When a response to the acknowledge signal is received by the implantable device, the external device and the implantable device are programmed to establish a communications session by a handshaking protocol. During a communications session, the RF transmitter and receiver of the implantable device may then either be maintained in the powered-up state for the duration of the communications session or powered down at prescribed intervals according to a defined protocol.


As described in detail below, the wakeup scheme may be designed to work in the context of a medium access control (MAC) protocol by which network participants contend for access to the wireless medium. Also, in one embodiment, the implantable device and the external device communicate by a transmission code which provides a DC balanced data stream such as 8b/10b. Such bit balanced data streams are advantageous in RF communications. In order for the special wakeup character to be invariant, the special wakeup character may be selected as a bit balanced sequence which is not changed by the transmission code.


In another particular embodiment, the external device is a remote monitor (RM) which operates to periodically collect data from the implantable device. The remote monitor may thus include a wakeup timer and be programmed to transmit a plurality of special wakeup characters to the implantable device in an attempt to establish a communications session at periodic intervals as defined by its wakeup timer. After the implantable device is awoken by the special wakeup characters, a communications session is established in which the implantable device transmits whatever data it has to the RM. If the implantable device has no data to transmit, however, the communications session is terminated almost immediately after being established. Such empty communications sessions still impose an energy cost upon the implantable device, however, due to the time it takes for the implantable device to wake up, establish a communications session with the RM, indicate that there is nothing to download, and then terminate the session. The total duty cycle of the RF circuitry in the implantable device is thus a function of both its own wakeup interval and the intervals at which the RM attempts to wake up the implantable device. In order to lessen power consumption by the implantable device, therefore, it is desirable for the intervals at which the RM attempts to wake up the implantable device to be such that the number of empty communications sessions is minimized. The remote monitor may thus be further programmed to adjust the periodic intervals at which it transmits a plurality of special wakeup characters to the implantable device in accordance with when previous successful communications sessions have been established such that data was collected. In one particular embodiment, the remote monitor is programmed to establish a communications session and collect data from the implantable device on a daily basis and further programmed to adjust the periodic intervals at which it attempts to wake up the implantable device in accordance with the time of day at which past successful communications sessions were established. In order to be able to respond to an episode, the remote monitor may also be programmed to transmit a plurality of special wakeup characters to the implantable device for establishing a communications session when a user command is received via a user interface.


1. Exemplary Hardware Components



FIG. 1 shows the primary telemetry components of an external device 200 and an implantable medical device 100. In this functional block diagram, the components are shown as being identical in each device. In this exemplary embodiment, the external device and the implantable device are microprocessor-based devices each having a controller 102a or 102b that includes a microprocessor and memory for data and program storage that supervises overall device operation as well as telemetry. Code executed by the controller also implements the duty cycle management schemes to be described below. The implantable device 100 may be a cardiac rhythm management device such as a pacemaker or implantable cardioverter/defibrillator, while the external device 200 may be an external programmer or a data-gathering device such as remote monitor. A user interface 300 (e.g., a keyboard and monitor) enables a user such as a clinician to direct the operation of the external device.


A long-range RF receiver 120a or 120b and a long-range RF transmitter 110a or 110b are interfaced to the microprocessor 102a or 102b in the implantable device and the external device, respectively. Also in each device, the transmitter and receiver are coupled to an antenna 101a or 101b through a transmit/receive switch 130a or 130b. The transmit/receive switches 130a and 130b are controlled by the microprocessor and either passes radio-frequency signals from the transmitter to the antenna or from the antenna to the receiver. To effect communications between the devices, a radio-frequency carrier signal modulated with digital data is transmitted wirelessly from one antenna to the other. A demodulator for extracting digital data from the carrier signal is incorporated into each receiver, and a modulator for modulating the carrier signal with digital data is incorporated into each transmitter. The interface to the controller for the RF transmitter and receiver in each device enables data transfer. The implantable device also incorporates a means by which the controller can power up or power down the RF receiver and/or transmitter in order to manage duty cycles in the manner described below. A wakeup timer 180 for defining the RF duty cycle is also shown for the implantable device, and this timer can either be implemented in code executed by the controller or can be discrete components. FIG. 1 also shows an inductively coupled transmitter/receiver 140a or 140b and antenna 150a or 150b for the implantable and external devices by which communication may take place without concern for power consumption when the two devices are in close physical proximity to one another.


2. Description of Specific Embodiments


A wireless telemetry system for implantable medical devices is generally a multiple access network in which a number of network participants share the available bandwidth of the wireless medium. A medium access control (MAC) protocol may be defined which allows each network participant to acquire exclusive access to the medium before transmitting data to an intended recipient. A collision is said to occur when two or more participants attempt to transmit at the same time. In certain networks, collisions may be detected by the sender listening to the medium when a transmission is initiated to determine if other network activity is present. If a collision is detected, the sender ceases transmitting and waits for a random or defined period before trying again. Most wireless transceivers operate in a half-duplex mode, however, and cannot simultaneously transmit and listen for ongoing network activity. MAC protocols for wireless networks therefore typically use out-of-band signaling or a handshaking protocol to minimize the probability of a collision occurring. In an example of the latter type of protocol, a four-way RTS-CTS-DS-ACK exchange as illustrated by FIG. 2 is used to avoid collisions. A network participant who desires to send a message to a particular recipient first transmits a request-to-send (RTS) frame and waits a defined period of time for a clear-to-send (CTS) frame from the intended recipient. All network participants who hear either of the RTS or CTS frames defer their transmissions. Upon receiving the CTS response, the sender can assume that the medium has been exclusively acquired and can then begin transmission of a data segment (DS) to the recipient. If the data is received without errors, the recipient responds with an acknowledge (ACK) frame which frees the medium for access by another participant. The present invention, in various embodiments, may work in the context of any of the medium access control protocols discussed above.


a. Exemplary Wakeup Scheme


A particular embodiment of the invention will now be described with reference to an external programmer or remote monitor (PRM/RM) and an implantable device (referred to as a pulse generator or PG). In this embodiment, the wakeup process works within the framework of a handshaking collision avoidance scheme as described above. In such a scheme, a network participant may transmit a so-called universal broadcast to all other participants in the network by transmitting an RTS-CTS-DS-ACK sequence. The PRM/RM transmits the RTS and CTS frames to cause other participants to defer their transmissions, transmits a data segment DS, and then transmits an ACK frame to release the medium. The wakeup process is illustrated by FIG. 3 and is similar to a universal broadcast with the exception that the PG provides the ACK frame instead of the PRM/RM. The PRM/RM sends out the messages RTS, CTS, and DS using the universal access code. The length of the DS message is set to a large number (e.g., 256 bytes), and the entire data portion of the message area is set to a repeating sequence of a special 10-bit character reserved solely for use as a wakeup indicator. (As described below, the wakeup indicator may be a special 8b/10b character.) The PG wakes up periodically (e.g., every 20-30 seconds) and listens for a very short interval to receive the wakeup special character. This short wakeup interval needs to be on the order of slightly longer than twenty bits after the PG's RF receiver has stabilized so that at least one entire 10-bit special character can be received. It is important to note that any normal preamble that is designed to get the PG receiver to its steady state of operation will not be present during the wakeup. An additional time is therefore required, on the order of an additional 10 bits above the standard 20 bits for a total of 30 bits. This means that the minimum wakeup time in this embodiment is 50 bits (10+20+20), which is 440 microseconds at a modulation rate of 113.7 Kbps. The projections below are based on a margin above this of 500 μs allowing for a 6-bit margin. If one wakeup special character is received, then the PG will stay awake long enough to receive several more wakeup special characters. If several wakeup special characters are received, the PG stays awake until it no longer receives special characters. After two consecutive non-special characters (e.g., these could be the CRC values of the DS frame), the PG responds with an ACK frame and will now stay awake for an extended period of time. The PRM having successfully received this ACK message will then proceed to perform a discovery process which will contend for message traffic within the protocol framework in order to establish a communications session with the PG.


In the wakeup scheme just described, a problem may arise if two PG's are in range of the PRM/RM when the wakeup sequence is transmitted. If both PG's wake up and respond to the wakeup sequence with an ACK frame, a collision will occur. In a further modification of the scheme, the PRM/RM may therefore be programmed to monitor the RF signal strength after transmission of the wakeup sequence during the expected ACK response time and proceed with the discovery process if there is found to be some RF activity.


An advantage of the wakeup scheme described above is that the PRM/RM is able to quickly establish a communications session with the PG on demand. The PG will be woken up within 20 seconds if the PG wakes up every 20 seconds and wakes up when a special character is being transmitted. (The probability that the PG will be awoken within that time increases with the length of the sequence of repeating special characters transmitted by the PRM/RM.) At the same time, the PG is subjected to a very low duty cycle which lessens the power requirements of operating a far-field RF telemetry system to acceptable levels. For example, an exemplary implantable cardiac rhythm management device may operate at an average current draw on the order of 22 microamps and is designed to last 6 years before a battery replacement is needed. This means that each 305 nanoamps of current draw costs the device one month in longevity. When the RF circuitry is powered up, its current draw is on the order of 4 milliamps. If the device wakes up every 20 seconds and remains powered up for 500 microseconds, the duty cycle is 1/40,000. The average current due to wake ups (but not, of course, including the current necessary for actually performing telemetry) is then (4 mA) ( 1/40,000)=100 nanoamps, resulting in a longevity cost to the device of just over a week.


b. Choice of Special Wakeup Character


In an embodiment where a DC balanced coding scheme such as 8b/10b is employed, it is desired to know a priori that the wakeup special character is always going to have one value independent of the running disparity (RD) of the 8b/10b encoding. The first step in achieving this goal is to choose a wakeup preamble from the set of valid special characters that is bit balanced. There are 7 such codes that have exactly 5 ones and 5 zeros. Codes that are bit balanced do not change the running disparity after transmission so that successive transmission would be identical values avoiding the inversion that occurs on non-bit balanced codes. The second step is to determine what the initial running disparity is when the data portion of the DS message is sent. Since this message is predetermined, it is a simple matter to determine the running disparity. The RD has an initial negative value (RD−) and starts with the first byte of the access code. The RD is then computed after each of the 8b/10b conversions. The RD at the start of the data portion is then the RD after the two universal access code bytes, the command byte, and the length byte. The proposal for wakeup special character and universal access codes is to choose two of the 7 bit-balanced valid special characters. The values are chosen as:
















Special




Code
code name
RD−
RD+







Universal Access Code 1:
K28.0
0011110100
1100001011


Universal Access Code 2:
K28.4
0011110010
1100001101


Wakeup Special Code:
K29.7
1011101000
1011100111










The choice of the RD− K28.0 and K28.4 codes are used as the universal access code. After transmission, the RD remains negative. The command byte and length byte are next to be transmitted. The command and length bytes depend on the value of the DS command code (3) and the length. Using a length of 256 bytes (0x100) gives a command byte of 0x31 and a length byte of 0x00 (The least significant two bits of the command are the most significant bits of the length). The 0x31 command byte then becomes the 8b/10b code of D17.1 that is also bit balanced so the RD remains negative. The 0x00 length byte is the 8b/10b code of D0.0 which converts to 1001110100, again this code is bit balanced so the RD remains negative. Now the wakeup special code K29.7 can be transmitted containing the RD− code of 101110 1000 repeatedly since the RD does not change. The CRC can take on its normal value and does not need to be considered here since it does not affect the RD of the data portion. Note that the alignment pattern is the 8b/10b code K28.5 (001111 1010) since it is the comma character.


Although the invention has been described in conjunction with the foregoing specific embodiments, many alternatives, variations, and modifications will be apparent to those of ordinary skill in the art. Such alternatives, variations, and modifications are intended to fall within the scope of the following appended claims.

Claims
  • 1. A telemetry system for enabling wireless communications between an implantable medical device and an external remote monitor (RM), comprising: a wireless transmitter, a wireless receiver, and a controller incorporated into each of the implantable medical device and the RM;a wakeup timer incorporated into the implantable device;wherein the transmitter and receiver of the implantable device are interfaced to the controller to enable the transmitter and receiver to be independently powered up or down;wherein the RM is programmed to transmit a data segment containing a repeating sequence of special wakeup characters in order to establish a wireless communications session with the implantable device;wherein the implantable device is configured to: power up its receiver for a specified time window at periodic intervals to wait for receipt of a special wakeup character transmitted by the RM;maintain its receiver and place its transmitter in a powered-up state upon receipt of the special character and for as long as consecutive special wakeup characters continue to be received; andtransmit an acknowledge signal upon receipt of at least one character other than a special wakeup character; andwherein the RM is configured to: establish a communications session with the implantable device when a response to the acknowledge signal is received by the implantable device; andadjust a periodic interval at which the RM transmits the special wakeup characters to the implantable device according to when previous successful communications sessions have been established.
  • 2. The system of claim 1, wherein implantable medical device transmitter includes a modulator configured to modulate a carrier signal with data, and wherein the modulator is placed in a powered up state upon receipt of the special wakeup character received from the RM.
  • 3. The system of claim 1, wherein the at least one character other than the special wakeup character includes a collision avoidance message.
  • 4. The system of claim 3, wherein the collision avoidance message includes a request-to-send message and a clear-to-send message.
  • 5. The system of claim 1, wherein the RM defers transmission of the special wakeup character when the RM detects wireless communication activity.
  • 6. The system of claim 1, wherein the RM is configured to perform a discovery process to contend for message traffic upon receiving the acknowledge signal from the implantable device.
  • 7. The system of claim 6, wherein the RM is configured to monitor wireless communication signal strength during an expected acknowledge response time and perform the discovery process when communication activity is detected during the expected acknowledge response time.
  • 8. The system of claim 1, wherein the implantable medical device receiver includes a demodulator configured to extract the special wakeup character from a carrier signal, and wherein the implantable medical device is configured to power up the demodulator for the specified time window.
  • 9. The system of claim 8, wherein a duration of the specified time window provides for both stabilization of the implantable device receiver and demodulation of two special wakeup characters.
  • 10. The system of claim 1, wherein the implantable medical device includes an inductive transmitter and an inductive receiver separate from the wireless transmitter and wireless receiver.
  • 11. A method comprising: wirelessly transmitting a data segment containing a repeating sequence of special wakeup characters by an external remote monitoring device (RM) in order to establish a wireless communications session with an implantable medical device;powering up a receiver of the implantable medical device for a specified time window at periodic intervals to wait for receipt of a special wakeup character transmitted by the RM, wherein the implantable medical device maintains the receiver and places a transmitter in a powered-up state upon receipt of a special character and for as long as consecutive special wakeup characters continue to be received;transmitting, by the implantable medical device, an acknowledge signal upon receipt of at least one character other than a special wakeup character;establishing a communications session with the implantable medical device when a response to the acknowledge signal is received by the implantable device; andadjusting, by the RM, a periodic interval at which the RM transmits the special wakeup characters to the implantable medical device according to when previous successful communications sessions have been established.
  • 12. The method of claim 11, wherein transmitting by the implantable medical device includes modulating a carrier signal with data, and wherein the method includes the implantable device placing the modulator in a powered up state upon receipt of the special wakeup character.
  • 13. The method of claim 11, wherein transmitting an acknowledge signal includes transmitting, by the implantable medical device, the acknowledge signal upon receipt of a collision avoidance message.
  • 14. The method of claim 13, wherein transmitting the acknowledge signal includes transmitting, by the implantable medical device, the acknowledge signal upon receipt of a request-to-send message and a clear-to-send message.
  • 15. The method of claim 11, including deferring, by the RM, transmission of the special wakeup character when the RM detects wireless communication activity.
  • 16. The method of claim 11, including performing, by the RM, a discovery process to contend for message traffic upon receiving the acknowledge signal from the implantable medical device.
  • 17. The method of claim 16, including: monitoring, by the RM, wireless communication signal strength during an expected acknowledge response time, andwherein performing the discovery process includes performing the discovery process when communication activity is detected during the expected acknowledge response time.
  • 18. The method of claim 11, including: demodulating, by the implantable medical device, the special wakeup character from a carrier signal, andwherein powering up the receiver included powering up the demodulator for the specified time window.
  • 19. The method of claim 18, wherein powering up the receiver includes powering up, by the implantable medical device, the receiver and demodulator for a specified time window having a duration that allows for both stabilization of the implantable device receiver and demodulation of two special wakeup characters by the demodulator.
  • 20. The method of claim 11, wherein the special wakeup character of the plurality of special wakeup characters includes a sequence of direct current (DC) balanced bits.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 13/218,672, filed Aug. 26, 2011, is now issued U.S. Pat. No. 8,326,424, which is a continuation of U.S. application Ser. No. 12/102,480, filed Apr. 14, 2008, now issued as U.S. Pat. No. 8,024,043, which is a continuation of U.S. application Ser. No. 11/101,142, filed Apr. 7, 2005, now issued as U.S. Pat. No. 7,359,753, which claims the benefit of U.S. Provisional Application No. 60/560,171, filed on Apr. 7, 2004, under 35 U.S.C. §119(e), which are hereby incorporated by reference.

US Referenced Citations (328)
Number Name Date Kind
3914586 McIntosh Oct 1975 A
4341982 Lahti et al. Jul 1982 A
4404972 Gordon et al. Sep 1983 A
4441498 Nordling Apr 1984 A
4486739 Franaszek et al. Dec 1984 A
4519401 Ko et al. May 1985 A
4539992 Calfee et al. Sep 1985 A
4542532 McQuilkin Sep 1985 A
4542535 Bates et al. Sep 1985 A
4543954 Cook et al. Oct 1985 A
4561443 Hogrefe et al. Dec 1985 A
4562841 Brockway et al. Jan 1986 A
4592360 Lesnick Jun 1986 A
4613937 Batty, Jr. Sep 1986 A
4634294 Christol et al. Jan 1987 A
4731814 Becker et al. Mar 1988 A
4799059 Grindahl et al. Jan 1989 A
4803987 Calfee et al. Feb 1989 A
4944299 Silvian Jul 1990 A
4945909 Fearnot et al. Aug 1990 A
4987897 Funke Jan 1991 A
5025808 Hafner Jun 1991 A
5074308 Sholder et al. Dec 1991 A
5080096 Hooper et al. Jan 1992 A
5089019 Grandjean Feb 1992 A
5109853 Taicher et al. May 1992 A
5113869 Nappholz et al. May 1992 A
5171977 Morrison Dec 1992 A
5230003 Dent et al. Jul 1993 A
5287384 Avery et al. Feb 1994 A
5292343 Blanchette et al. Mar 1994 A
5300093 Koestner et al. Apr 1994 A
5314453 Jeutter May 1994 A
5342408 deCoriolis et al. Aug 1994 A
5350411 Ryan et al. Sep 1994 A
5350412 Hoegnelid et al. Sep 1994 A
5370666 Lindberg et al. Dec 1994 A
5394433 Bantz et al. Feb 1995 A
5404877 Nolan et al. Apr 1995 A
5456692 Smith, Jr. et al. Oct 1995 A
5466246 Silvian Nov 1995 A
5476488 Morgan et al. Dec 1995 A
5486200 Lindemans Jan 1996 A
5516285 Yacker et al. May 1996 A
5532708 Krenz et al. Jul 1996 A
5535752 Halperin et al. Jul 1996 A
5562713 Silvian Oct 1996 A
5568510 Tam Oct 1996 A
5577087 Furuya Nov 1996 A
5579876 Adrian et al. Dec 1996 A
5593430 Renger Jan 1997 A
5598847 Renger Feb 1997 A
5603331 Heemels et al. Feb 1997 A
5617871 Burrows Apr 1997 A
5630835 Brownlee May 1997 A
5650759 Hittman et al. Jul 1997 A
5683432 Goedeke et al. Nov 1997 A
5694952 Lidman et al. Dec 1997 A
5697958 Paul et al. Dec 1997 A
5725559 Alt et al. Mar 1998 A
5729680 Belanger et al. Mar 1998 A
5733313 Barreras, Sr. et al. Mar 1998 A
5737419 Ganesan Apr 1998 A
5752976 Duffin et al. May 1998 A
5752977 Grevious et al. May 1998 A
5759199 Snell et al. Jun 1998 A
5764699 Needham et al. Jun 1998 A
5766232 Grevious et al. Jun 1998 A
5807397 Barreras Sep 1998 A
5833603 Kovacs et al. Nov 1998 A
5843139 Goedeke et al. Dec 1998 A
5861019 Sun et al. Jan 1999 A
5870391 Nago Feb 1999 A
5881101 Furman et al. Mar 1999 A
5887022 Lee Mar 1999 A
5895485 Loechel et al. Apr 1999 A
5898397 Murray Apr 1999 A
5904708 Goedeke May 1999 A
5919210 Lurie et al. Jul 1999 A
5940384 Carney et al. Aug 1999 A
6009350 Renken Dec 1999 A
6028527 Soenen et al. Feb 2000 A
6031863 Jusa et al. Feb 2000 A
6044485 Dent et al. Mar 2000 A
6083248 Thompson Jul 2000 A
6088381 Myers, Jr. Jul 2000 A
6093146 Filangeri Jul 2000 A
6115583 Brummer et al. Sep 2000 A
6115634 Donders et al. Sep 2000 A
6115636 Ryan Sep 2000 A
6128528 Erickson et al. Oct 2000 A
6130905 Wakayama Oct 2000 A
6155208 Schell et al. Dec 2000 A
6167310 Grevious Dec 2000 A
6167312 Goedeke Dec 2000 A
6169925 Villaseca et al. Jan 2001 B1
6200265 Walsh et al. Mar 2001 B1
6219580 Faltys et al. Apr 2001 B1
6223083 Rosar Apr 2001 B1
6240317 Villaseca et al. May 2001 B1
6249700 Alt Jun 2001 B1
6263246 Goedeke et al. Jul 2001 B1
6275737 Mann Aug 2001 B1
6309350 VanTassel et al. Oct 2001 B1
6329920 Morrison et al. Dec 2001 B1
6336900 Alleckson et al. Jan 2002 B1
6336903 Bardy Jan 2002 B1
6381492 Rockwell et al. Apr 2002 B1
6385318 Oishi May 2002 B1
6388628 Dettloff et al. May 2002 B1
6416471 Kumar et al. Jul 2002 B1
6424867 Snell et al. Jul 2002 B1
6427088 Bowman, IV et al. Jul 2002 B1
6434429 Kraus et al. Aug 2002 B1
6443891 Grevious Sep 2002 B1
6456256 Amundson et al. Sep 2002 B1
6456875 Wilkinson et al. Sep 2002 B1
6463329 Goedeke Oct 2002 B1
6470215 Kraus et al. Oct 2002 B1
6471645 Warkentin Oct 2002 B1
6472991 Schulman et al. Oct 2002 B1
6482154 Haubrich et al. Nov 2002 B1
6490487 Kraus et al. Dec 2002 B1
6505072 Linder et al. Jan 2003 B1
6527729 Turcott Mar 2003 B1
6531982 White et al. Mar 2003 B1
6535763 Hiebert et al. Mar 2003 B1
6535766 Thompson et al. Mar 2003 B1
6562000 Thompson et al. May 2003 B2
6562001 Lebel et al. May 2003 B2
6564104 Nelson et al. May 2003 B2
6564105 Starkweather et al. May 2003 B2
6567793 Hicks et al. May 2003 B1
6574503 Ferek-Petric Jun 2003 B2
6574509 Kraus et al. Jun 2003 B1
6574510 Von Arx et al. Jun 2003 B2
6577900 Silvian Jun 2003 B1
6577901 Thompson et al. Jun 2003 B2
6582365 Hines et al. Jun 2003 B1
6585644 Lebel et al. Jul 2003 B2
6600949 Turcott Jul 2003 B1
6600952 Snell et al. Jul 2003 B1
6602191 Quy Aug 2003 B2
6609029 Mann et al. Aug 2003 B1
6614406 Amundson et al. Sep 2003 B2
6622043 Kraus et al. Sep 2003 B1
6622050 Thompson Sep 2003 B2
6624786 Boyle Sep 2003 B2
6631296 Parramon et al. Oct 2003 B1
6648821 Lebel et al. Nov 2003 B2
6659948 Lebel et al. Dec 2003 B2
6662048 Balczewski et al. Dec 2003 B2
6671328 Poon et al. Dec 2003 B1
6675045 Mass et al. Jan 2004 B2
6687546 Lebel et al. Feb 2004 B2
6708065 Von Arx et al. Mar 2004 B2
6716165 Flanders et al. Apr 2004 B1
6741886 Yonce May 2004 B2
6752765 Jensen et al. Jun 2004 B1
6763269 Cox Jul 2004 B2
6768730 Whitehill Jul 2004 B1
6801807 Abrahamson Oct 2004 B2
6804559 Kraus et al. Oct 2004 B1
6809701 Amundson et al. Oct 2004 B2
6844854 Johnson et al. Jan 2005 B2
6868288 Thompson Mar 2005 B2
6873870 Ferek-Petric Mar 2005 B2
6889081 Hsu May 2005 B2
6897788 Khair et al. May 2005 B2
6907291 Snell et al. Jun 2005 B1
6951596 Green et al. Oct 2005 B2
6970735 Uber, III et al. Nov 2005 B2
6978181 Snell Dec 2005 B1
6985088 Goetz et al. Jan 2006 B2
6985773 Von Arx et al. Jan 2006 B2
6993393 Von Arx et al. Jan 2006 B2
7013178 Reinke et al. Mar 2006 B2
7027872 Thompson Apr 2006 B2
7047076 Li et al. May 2006 B1
7069086 Von Arx Jun 2006 B2
7107085 Doi Sep 2006 B2
7110823 Whitehurst et al. Sep 2006 B2
7155290 Von et al. Dec 2006 B2
7177700 Cox Feb 2007 B1
7218969 Vallapureddy et al. May 2007 B2
7228182 Healy et al. Jun 2007 B2
7274642 Sako et al. Sep 2007 B2
7280872 Mosesov et al. Oct 2007 B1
7289853 Campbell et al. Oct 2007 B1
7319903 Bange et al. Jan 2008 B2
7324012 Mann et al. Jan 2008 B2
7359753 Bange et al. Apr 2008 B2
7406349 Seeberger et al. Jul 2008 B2
7457669 Katoozi et al. Nov 2008 B2
7475245 Healy et al. Jan 2009 B1
7519430 Arx et al. Apr 2009 B2
7539489 Alexander May 2009 B1
7539541 Quiles et al. May 2009 B2
7573422 Harvey et al. Aug 2009 B2
7610065 Vallapureddy et al. Oct 2009 B2
7623922 Bange et al. Nov 2009 B2
7664553 Roberts Feb 2010 B2
7668596 Von Arx et al. Feb 2010 B2
7729776 Von Arx et al. Jun 2010 B2
7738964 Von Arx et al. Jun 2010 B2
7787953 Vallapureddy et al. Aug 2010 B2
7818067 Healy et al. Oct 2010 B2
7860574 Von Arx et al. Dec 2010 B2
7881802 Quiles et al. Feb 2011 B2
7890180 Quiles Feb 2011 B2
7903043 Rawat et al. Mar 2011 B2
8019434 Quiles et al. Sep 2011 B2
8024043 Bange et al. Sep 2011 B2
8041432 Von Arx et al. Oct 2011 B2
8046080 Von Arx et al. Oct 2011 B2
8055350 Roberts Nov 2011 B2
8290589 Bange et al. Oct 2012 B2
8326424 Bange et al. Dec 2012 B2
20010001014 Akins et al. May 2001 A1
20010012955 Goedeke et al. Aug 2001 A1
20010019614 Madoukh Sep 2001 A1
20010027331 Thompson Oct 2001 A1
20010047125 Quy Nov 2001 A1
20020013614 Thompson Jan 2002 A1
20020019606 Lebel et al. Feb 2002 A1
20020032661 Schuba et al. Mar 2002 A1
20020046276 Coffey et al. Apr 2002 A1
20020049480 Lebel et al. Apr 2002 A1
20020062139 Ding May 2002 A1
20020065509 Lebel et al. May 2002 A1
20020065539 Von Arx et al. May 2002 A1
20020065540 Lebel et al. May 2002 A1
20020109621 Khair et al. Aug 2002 A1
20020115912 Muraki et al. Aug 2002 A1
20020120838 Abdulkader Aug 2002 A1
20020123672 Christophersom et al. Sep 2002 A1
20020143372 Snell et al. Oct 2002 A1
20020147388 Mass et al. Oct 2002 A1
20020159545 Ramesh et al. Oct 2002 A1
20020173830 Starkweather et al. Nov 2002 A1
20020183806 Abrahamson et al. Dec 2002 A1
20030009204 Amundson et al. Jan 2003 A1
20030018369 Thompson et al. Jan 2003 A1
20030028902 Cubley et al. Feb 2003 A1
20030041866 Linberg et al. Mar 2003 A1
20030050535 Bowman, IV et al. Mar 2003 A1
20030065919 Albert et al. Apr 2003 A1
20030074036 Prutchi et al. Apr 2003 A1
20030083719 Shankar et al. May 2003 A1
20030097157 Wohlgemuth et al. May 2003 A1
20030107487 Korman et al. Jun 2003 A1
20030114891 Hiebert et al. Jun 2003 A1
20030114897 Von Arx et al. Jun 2003 A1
20030114898 Von Arx et al. Jun 2003 A1
20030135246 Mass et al. Jul 2003 A1
20030146835 Carter Aug 2003 A1
20030149459 Von Arx et al. Aug 2003 A1
20030159048 Matsumoto et al. Aug 2003 A1
20030174069 Goetz et al. Sep 2003 A1
20030187484 Davis et al. Oct 2003 A1
20030216793 Karlsson et al. Nov 2003 A1
20030220673 Snell Nov 2003 A1
20040009815 Zotto et al. Jan 2004 A1
20040030260 Von Arx Feb 2004 A1
20040047434 Waltho Mar 2004 A1
20040102815 Balczewski et al. May 2004 A1
20040106967 Von Arx et al. Jun 2004 A1
20040122489 Mazar et al. Jun 2004 A1
20040127959 Amundson et al. Jul 2004 A1
20040167587 Thompson Aug 2004 A1
20040168071 Silverbrook Aug 2004 A1
20040176811 Von Arx et al. Sep 2004 A1
20040176822 Thompson et al. Sep 2004 A1
20040215280 Dublin et al. Oct 2004 A1
20040236382 Dinsmoor et al. Nov 2004 A1
20040247047 Dennis et al. Dec 2004 A1
20040260363 Arx et al. Dec 2004 A1
20040263273 Ahmed Dec 2004 A1
20050134520 Rawat et al. Jun 2005 A1
20050203582 Healy et al. Sep 2005 A1
20050204134 Von Arx et al. Sep 2005 A1
20050222933 Wesby Oct 2005 A1
20050240245 Bange et al. Oct 2005 A1
20050245992 Persen et al. Nov 2005 A1
20050261934 Thompson Nov 2005 A1
20050283208 Von Arx et al. Dec 2005 A1
20050283209 Katoozi et al. Dec 2005 A1
20050288738 Bange et al. Dec 2005 A1
20060025834 Von Arx et al. Feb 2006 A1
20060029100 Dove Feb 2006 A1
20060030901 Quiles et al. Feb 2006 A1
20060030902 Quiles et al. Feb 2006 A1
20060030903 Seeberger et al. Feb 2006 A1
20060030904 Quiles Feb 2006 A1
20060071756 Steeves Apr 2006 A1
20060116744 Von Arx et al. Jun 2006 A1
20060161222 Haubrich et al. Jul 2006 A1
20060161223 Vallapureddy et al. Jul 2006 A1
20060194615 Vallapureddy et al. Aug 2006 A1
20060195161 Li Aug 2006 A1
20060195162 Arx et al. Aug 2006 A1
20060247736 Roberts Nov 2006 A1
20070049983 Freeberg Mar 2007 A1
20070100396 Freeberg May 2007 A1
20070118188 Von Arx et al. May 2007 A1
20070135216 Martinek et al. Jun 2007 A1
20070169181 Roskind Jul 2007 A1
20070185550 Vallapureddy et al. Aug 2007 A1
20070260293 Carpenter et al. Nov 2007 A1
20070282398 Healy et al. Dec 2007 A1
20080015655 Bange et al. Jan 2008 A1
20080015656 Bange et al. Jan 2008 A1
20080046745 Buch et al. Feb 2008 A1
20080055070 Bange et al. Mar 2008 A1
20080114412 Bange et al. May 2008 A1
20080215121 Bange et al. Sep 2008 A1
20080262573 Seeberger et al. Oct 2008 A1
20080288024 Abrahamson Nov 2008 A1
20090216298 Quiles et al. Aug 2009 A1
20100045480 Vallapureddy et al. Feb 2010 A1
20100106224 Von Arx et al. Apr 2010 A1
20100114233 Von Arx et al. May 2010 A1
20100121414 Roberts May 2010 A1
20100152816 Von Arx et al. Jun 2010 A1
20110066211 Von Arx et al. Mar 2011 A1
20110098788 Quiles Apr 2011 A1
20110134013 Rawat et al. Jun 2011 A1
20110313491 Bange et al. Dec 2011 A1
Foreign Referenced Citations (27)
Number Date Country
10119393 Jan 2002 DE
0168640 Jan 1986 EP
0607638 Jul 1994 EP
1050265 Nov 2000 EP
1062985 Dec 2000 EP
1308184 May 2003 EP
1495783 Jan 2005 EP
1732645 Jun 2012 EP
08511702 Dec 1996 JP
2001274901 Oct 2001 JP
2002132962 May 2002 JP
2003022008 Jan 2003 JP
2004094544 Mar 2004 JP
WO-9500202 Jan 1995 WO
WO-9819400 May 1998 WO
WO-9912302 Mar 1999 WO
WO-03053515 Jul 2003 WO
WO-03092240 Nov 2003 WO
WO-2005000397 Jan 2005 WO
WO-2005091546 Sep 2005 WO
WO-2005091546 Sep 2005 WO
WO-2005099816 Oct 2005 WO
WO-2005099817 Oct 2005 WO
WO-2006020546 Feb 2006 WO
WO-2006020549 Feb 2006 WO
WO-2006116004 Nov 2006 WO
WO-2008027655 Mar 2008 WO
Non-Patent Literature Citations (359)
Entry
US 7,680,541, 3/2010, Von et al. (withdrawn).
“U.S. Appl. No. 09/921,653, Notice of Allowance mailed May 7, 2002”, 6 pgs.
“U.S. Appl. No. 10/025,183, Appeal Brief filed Dec. 29, 2005”, 27 pgs.
“U.S. Appl. No. 10/025,183, Final Office Action mailed Jan. 13, 2005”, 7 pgs.
“U.S. Appl. No. 10/025,183, Final Office Action mailed May 25, 2005”, 9 pgs.
“U.S. Appl. No. 10/025,183, Final Office Action mailed Jul. 31, 2006”, 7 pgs.
“U.S. Appl. No. 10/025,183, Final Office Action mailed Aug. 3, 2004”, 7 pgs.
“U.S. Appl. No. 10/025,183, Non-Final Office Action mailed Feb. 15, 2006”, 5 pgs.
“U.S. Appl. No. 10/025,183, Non-Final Office Action mailed Feb. 19, 2009”, 5 pgs.
“U.S. Appl. No. 10/025,183, Non-Final Office Action mailed Mar. 4, 2004”, 5 pgs.
“U.S. Appl. No. 10/025,183, Non-Final Office Action mailed Mar. 26, 2007”, 4 pgs.
“U.S. Appl. No. 10/025,183, Non-Final Office Action mailed Dec. 10, 2007”, 4 pgs.
“U.S. Appl. No. 10/025,183, Notice of Allowance mailed Sep. 14, 2007”, 4 pgs.
“U.S. Appl. No. 10/025,183, Notice of Allowance mailed Sep. 18, 2008”, 7 pgs.
“U.S. Appl. No. 10/025,183, Notice of Allowance mailed Sep. 28, 2009”, 5 pgs.
“U.S. Appl. No. 10/025,183, Response filed Jan. 31, 2007 to Final Office Action mailed Jul. 31, 2006”, 11 pgs.
“U.S. Appl. No. 10/025,183, Response filed Apr. 13, 2005 to Final Office Action mailed Jan. 13, 2005”, 11 pgs.
“U.S. Appl. No. 10/025,183, Response filed May 12, 2008 to Non-Final Office Action mailed Dec. 10, 2007”, 10 pgs.
“U.S. Appl. No. 10/025,183, Response filed May 15, 2006 to Non-Final Office Action mailed Feb. 15, 2006”, 11 pgs.
“U.S. Appl. No. 10/025,183, Response filed Jun. 24, 2004 to Non-Final Office Action mailed Mar. 4, 2004”, 11 pgs.
“U.S. Appl. No. 10/025,183, Response filed Jun. 12, 2009 to Non Final Office Action mailed Feb. 19, 2009”, 10 pgs.
“U.S. Appl. No. 10/025,183, Response filed Jun. 26, 2007 to Non-Final Office Action mailed Mar. 26, 2007”, 14 pgs.
“U.S. Appl. No. 10/025,183, Response filed Dec. 3, 2004 to Final Office Action mailed Aug. 3, 2004”, 11 pgs.
“U.S. Appl. No. 10/025,223, Communication filed Nov. 16, 2004 to Final Office Action mailed Aug. 16, 2004”, 1 pg.
“U.S. Appl. No. 10/025,223, Final Office Action mailed Aug. 16, 2004”, 9 pgs.
“U.S. Appl. No. 10/025,223, Final Office Action mailed Aug. 16, 2004”, 7 pgs.
“U.S. Appl. No. 10/025,223, Final Office Action mailed Sep. 10, 2004”, 7 pgs.
“U.S. Appl. No. 10/025,223, Non Final Office Action mailed Mar. 1, 2005”, 6 pgs.
“U.S. Appl. No. 10/025,223, Non Final Office Action mailed Mar. 19, 2004”, 4 pgs.
“U.S. Appl. No. 10/025,223, Non-Final Office Action mailed Mar. 19, 2004”, 4 pgs.
“U.S. Appl. No. 10/025,223, Non-Final Office Action mailed Mar. 1, 2005”, 6 pgs.
“U.S. Appl. No. 10/025,223, Notice of Allowance mailed Aug. 10, 2005”, 4 pgs.
“U.S. Appl. No. 10/025,223, Response filed Jan. 10, 2005 to Final Office Action mailed Sep. 10, 2004”, 10 pgs.
“U.S. Appl. No. 10/025,223, Response filed Jun. 21, 2004 to Non Final Office Action mailed Mar. 19, 2004”, 9 pgs.
“U.S. Appl. No. 10/025,223, Response filed Jun. 30, 2005 to Non Final Office Action mailed Mar. 1, 2005”, 10 pgs.
“U.S. Appl. No. 10/071,255, Non Final Office Action mailed Jan. 7, 2005”, 6 pgs.
“U.S. Appl. No. 10/071,255, Notice of allowance mailed Jun. 15, 2005”, 4 pgs.
“U.S. Appl. No. 10/071,255, Preliminary Amendment filed Oct. 5, 2005”, 12 pgs.
“U.S. Appl. No. 10/071,255, Response Oct. 20, 2004 to Restriction Requirement mailed Sep. 28, 2004”, 10 pgs.
“U.S. Appl. No. 10/071,255, Response filed Apr. 7, 2005 non-final office action mailed Jan. 7, 2005”, 12 pgs.
“U.S. Appl. No. 10/071,255, Restriction Requirement mailed Sep. 28, 2004”, 5 pgs.
“U.S. Appl. No. 10/252,494, Non Final Office Action mailed Jan. 30, 2003”, 4 pgs.
“U.S. Appl. No. 10/252,494, Notice of Allowance mailed Mar. 25, 2003”, 5 pgs.
“U.S. Appl. No. 10/252,494, Response filed Mar. 5, 2003 to Non Final Office Action mailed Jan. 30, 2003”, 6 pgs.
“U.S. Appl. No. 10/269,905, Non Final Office Action mailed Jul. 27, 2005”, 15 pgs.
“U.S. Appl. No. 10/269,905, Notice of Allowance mailed Jan. 20, 2006”, 11 pgs.
“U.S. Appl. No. 10/269,905, Response filed Nov. 28, 2005 to Non Final Office Action mailed Jul. 27, 2005”, 13 pgs.
“U.S. Appl. No. 10/634,233, Notice of Allowance mailed Jun. 16, 2004”, 6 pgs.
“U.S. Appl. No. 10/744,943, Final Office Action mailed Feb. 21, 2008.”, 15 pgs.
“U.S. Appl. No. 10/744,943, Response filed Oct. 22, 2007 to Non-Final Office Action mailed Apr. 20, 2007”, 9 pgs.
“U.S. Appl. No. 10/870,324, Advisory Action mailed Mar. 21, 2008”, 3 pgs.
“U.S. Appl. No. 10/870,324, Examiner Interview Summary mailed Feb. 13, 2008”, 4 pgs.
“U.S. Appl. No. 10/870,324, Examiner Interview Summary mailed Sep. 28, 2007”, 3 pgs.
“U.S. Appl. No. 10/870,324, Examiner Interview Summary mailed Oct. 25, 2007”, 3 pgs.
“U.S. Appl. No. 10/870,324, Final Office Action mailed Jan. 8, 2008”, 8 pgs.
“U.S. Appl. No. 10/870,324, Non Final Office Action mailed Jun. 27, 2007”, 6 pgs.
“U.S. Appl. No. 10/870,324, Non-Final Office Action mailed May 14, 2008”, 8 pgs.
“U.S. Appl. No. 10/870,324, Notice of Allowance mailed Dec. 1, 2008”, 7 pgs.
“U.S. Appl. No. 10/870,324, Response filed Feb. 8, 2008 to Final Office Action mailed Jan. 8, 2008”, 20 pgs.
“U.S. Appl. No. 10/870,324, Response filed Aug. 14, 2008 to Non-Final Office Action mailed May 14, 2008”, 22 pgs.
“U.S. Appl. No. 10/870,324, Response filed Oct. 29, 2007 to Non Final Office Action mailed Jun. 27, 2007”, 21 pgs.
“U.S. Appl. No. 10/870,328, Non Final Office Action mailed Aug. 16, 2007”, 12 pgs.
“U.S. Appl. No. 10/870,328, Notice of Allowance mailed Jul. 24, 2008”, 10 pgs.
“U.S. Appl. No. 10/870,328, Response filed Nov. 16, 2007 to Non-Final Office Action mailed Aug. 16, 2007”, 17 pgs.
“U.S. Appl. No. 10/914,496, Final Office Action mailed May 23, 2007”, 11 pgs.
“U.S. Appl. No. 10/914,496, Final Office Action mailed Sep. 22, 2008”, 12 pgs.
“U.S. Appl. No. 10/914,496, Non Final Office Action mailed Dec. 5, 2006”, 9 pgs.
“U.S. Appl. No. 10/914,496, Non-Final Office Action mailed Mar. 18, 2008”, 9 pgs.
“U.S. Appl. No. 10/914,496, Notice of Allowance mailed Jan. 16, 2009”, 4 pgs.
“U.S. Appl. No. 10/914,496, Response filed Mar. 5, 2007 to Non Final office Action mailed Dec. 5, 2006”, 13 pgs.
“U.S. Appl. No. 10/914,496, Response filed Jun. 18, 2008 to Non-Final Office Action mailed Mar. 18, 2008”, 10 pgs.
“U.S. Appl. No. 10/914,496, Response filed Aug. 22, 2007 to Final Office Action mailed May 23, 2007”, 12 pgs.
“U.S. Appl. No. 10/914,496, Response filed Nov. 24, 2008 to Final Office Action mailed Sep. 22, 2008”, 9 pgs.
“U.S. Appl. No. 10/914,496, Response filed Dec. 12, 2007 to Restriction Requirement mailed Nov. 13, 2007”, 7 pgs.
“U.S. Appl. No. 10/914,496, Restriction Requirement mailed Nov. 13, 2007”, 5 pgs.
“U.S. Appl. No. 10/914,499, Advisory Action mailed Aug. 4, 2009”, 5 pgs.
“U.S. Appl. No. 10/914,499, Final Office Action mailed Jan. 24, 2008”, 10 pgs.
“U.S. Appl. No. 10/914,499, Final Office Action mailed May 12, 2009”, 10 pgs.
“U.S. Appl. No. 10/914,499, Non Final Office Action mailed May 29, 2007”, 11 pgs.
“U.S. Appl. No. 10/914,499, Non-Final Office Action mailed Feb. 3, 2010”, 11 pgs.
“U.S. Appl. No. 10/914,499, Non-Final Office Action mailed Apr. 24, 2008”, 5 pgs.
“U.S. Appl. No. 10/914,499, Non-Final Office Action mailed Nov. 5, 2008”, 12 pgs.
“U.S. Appl. No. 10/914,499, Notice of Allowance mailed Sep. 29, 2010”, 4 pgs.
“U.S. Appl. No. 10/914,499, Response filed Feb. 5, 2009 to Non-Final Office Action mailed Nov. 5, 2008”, 12 pgs.
“U.S. Appl. No. 10/914,499, Response filed Apr. 14, 2008 to Final Office Action mailed Jan. 24, 2008”, 11 pgs.
“U.S. Appl. No. 10/914,499, Response filed May 3, 2010 to Non-Final Office Action mailed Feb. 3, 2010”, 12 pgs.
“U.S. Appl. No. 10/914,499, Response filed Jun. 30, 2008 to Non-Final Office Action mailed Apr. 24, 2008”, 10 pgs.
“U.S. Appl. No. 10/914,499, Response filed Jul. 13, 2009 to Final Office Action mailed May 12, 2009”, 10 pgs.
“U.S. Appl. No. 10/914,499, Response filed Aug. 31, 2010 to Final Office Action mailed Jul. 20, 2010”, 10 pgs.
“U.S. Appl. No. 10/914,499, Response filed Oct. 23, 2007 to Non-Final Office Action mailed May 29, 2007”, 11 pgs.
“U.S. Appl. No. 10/914,499, Response filed Nov. 10, 2009 to Advisory Action mailed Aug. 4, 2009”, 12 pgs.
“U.S. Appl. No. 10/914,638, Final Office Action mailed Apr. 17, 2007”, 10 pgs.
“U.S. Appl. No. 10/914,638, Non Final Office Action mailed Oct. 18, 2006”, 9 pgs.
“U.S. Appl. No. 10/914,638, Notice of Allowance mailed Mar. 21, 2008”, 4 pgs.
“U.S. Appl. No. 10/914,638, Notice of Allowance mailed Oct. 22, 2007”, 4 pgs.
“U.S. Appl. No. 10/914,638, Response filed Jan. 18, 2007 to Non Final Office Action mailed Oct. 18, 2006”, 16 pgs.
“U.S. Appl. No. 10/914,638, Response filed Aug. 17, 2007 to Final Office Action mailed Apr. 17, 2007”, 8 pgs.
“U.S. Appl. No. 11/039,200, Non Final Office Action mailed Aug. 3, 2006”, 10 pgs.
“U.S. Appl. No. 11/039,200, Notice of Allowance mailed Dec. 15, 2006”, 4 pgs.
“U.S. Appl. No. 11/039,200, Response filed Nov. 2, 2006 to Non Final Office Action mailed Aug. 3, 2006”, 9 pgs.
“U.S. Appl. No. 11/068,478, Final Office Action mailed Jun. 2, 2008”, 17 pgs.
“U.S. Appl. No. 11/068,478, Non Final Office Action mailed Jan. 2, 2009”, 11 pgs.
“U.S. Appl. No. 11/068,478, Non-Final Office Action mailed Dec. 17, 2007”, 14 pgs.
“U.S. Appl. No. 11/068,478, Notice of Allowance mailed Jun. 9, 2009”, 7 pgs.
“U.S. Appl. No. 11/068,478, Response filed Mar. 17, 2008 to Non Final Office Action mailed Dec. 17, 2007”, 19 pgs.
“U.S. Appl. No. 11/068,478, Response filed Mar. 30, 2009 to Non Final Office Action mailed Jan. 2, 2009”, 20 pgs.
“U.S. Appl. No. 11/068,478, Response filed Aug. 4, 2008 to Final Office Action mailed Jun. 2, 2008”, 19 pgs.
“U.S. Appl. No. 11/101,142, Non-Final Office Action mailed Jun. 20, 2007”, 8 pgs.
“U.S. Appl. No. 11/101,142, Notice of Allowance mailed Nov. 27, 2007”, 6 pgs.
“U.S. Appl. No. 11/101,142, Response filed Jun. 4, 2007 to Restriction Requirement Response mailed May 3, 2007”, 7 pgs.
“U.S. Appl. No. 11/101,142, Response filed Sep. 20, 2007 to Non-Final Office Action mailed Jun. 20, 2007”, 7 pgs.
“U.S. Appl. No. 11/101,142, Restriction Requirement mailed May 3, 2007”, 5 pgs.
“U.S. Appl. No. 11/101,196, Non Final Office Action mailed Mar. 29, 2007”, 8 pgs.
“U.S. Appl. No. 11/101,196, Notice of Allowance mailed Aug. 27, 2007”, 5 pgs.
“U.S. Appl. No. 11/101,196, Response filed Jun. 29, 2007 to Non Final Office Action mailed Mar. 29, 2007”, 8 pgs.
“U.S. Appl. No. 11/116,108, Advisory Action mailed Jan. 29, 2009”, 3 pgs.
“U.S. Appl. No. 11/116,108, Final Office Action mailed Oct. 10, 2008”, 7 pgs.
“U.S. Appl. No. 11/116,108, Non-Final Office Action mailed Mar. 20, 2008”, 11 pgs.
“U.S. Appl. No. 11/116,108, Non-Final Office Action mailed Apr. 23, 2009”, 7 pgs.
“U.S. Appl. No. 11/116,108, Notice of Allowance mailed Sep. 29, 2009”, 8 pgs.
“U.S. Appl. No. 11/116,108, Response filed Jun. 20, 2008 to Non-Final Office Action mailed Mar. 20, 2008”, 9 pgs.
“U.S. Appl. No. 11/116,108, Response filed Jul. 23, 2009 to Non Final Office Action mailed Apr. 23, 2009”, 7 pgs.
“U.S. Appl. No. 11/116,108, Response filed Dec. 10, 2008 to Final Office Action mailed Oct. 10, 2008”, 6 pgs.
“U.S. Appl. No. 11/244,273, Non-Final Office Action mailed Nov. 28, 2008”, 7 pgs.
“U.S. Appl. No. 11/244,273, Notice of Allowance mailed Oct. 5, 2009”, 7 pgs.
“U.S. Appl. No. 11/244,273, Response filed Mar. 2, 2009 to Non-Final Office Action mailed Nov. 28, 2008”, 13 pgs.
“U.S. Appl. No. 11/244,273, Response filed Aug. 12, 2009 to Ex Parte Quayle mailed Jun. 12, 2009”, 4 pgs.
“U.S. Appl. No. 11/244,273, Response filed Oct. 22, 2008 to Restriction Requirement mailed Jul. 22, 2008”, 13 pgs.
“U.S. Appl. No. 11/244,273, Restriction Requirement mailed Jul. 22, 2008”, 10 pgs.
“U.S. Appl. No. 11/325,564, Examiner Interview Summary mailed Jun. 24, 2009”, 2 pgs.
“U.S. Appl. No. 11/325,584, Final Office Action mailed Oct. 24, 2008”, 5 pgs.
“U.S. Appl. No. 11/325,584, Non-Final Office Action mailed Mar. 24, 2009”, 5 pgs.
“U.S. Appl. No. 11/325,584, Non-Final Office Action mailed Apr. 10, 2008”, 6 pgs.
“U.S. Appl. No. 11/325,584, Notice of Allowance mailed Mar. 23, 2010”, 4 pgs.
“U.S. Appl. No. 11/325,584, Notice of Allowance mailed Oct. 21, 2009”, 5 pgs.
“U.S. Appl. No. 11/325,584, Response filed Jan. 22, 2009 to Final Office Action mailed Oct. 24, 2008”, 6 pgs.
“U.S. Appl. No. 11/325,584, Response filed Jun. 24, 2009 to Non-Final Office Action mailed Mar. 24, 2009”, 9 pgs.
“U.S. Appl. No. 11/325,584, Response filed Jul. 10, 2008 to Non Final Office Action mailed Apr. 10, 2008”, 9 pgs.
“U.S. Appl. No. 11/381,493, Appeal Brief filed Nov. 16, 2009”, 19 pgs.
“U.S. Appl. No. 11/381,493, Examiners Answer mailed Mar. 25, 2010”, 20 pgs.
“U.S. Appl. No. 11/381,493, Final Office Action mailed Jan. 8, 2009”, 12 pgs.
“U.S. Appl. No. 11/381,493, Final Office Action mailed Apr. 16, 2009”, 14 pgs.
“U.S. Appl. No. 11/381,493, Non-Final Office Action mailed Jun. 23, 2008”, 13 pgs.
“U.S. Appl. No. 11/381,493, Reply Brief filed Apr. 29, 2010”, 6 pgs.
“U.S. Appl. No. 11/381,493, Response filed Mar. 9, 2009 to Final Office Action mailed Jan. 8, 2009”, 13 pgs.
“U.S. Appl. No. 11/381,493, Response filed Apr. 28, 2008 to Restriction Requirement mailed Mar. 26, 2008”, 9 pgs.
“U.S. Appl. No. 11/381,493, Response filed Jun. 9, 2009 to Final Office Action mailed Apr. 16, 2009”, 13 pgs.
“U.S. Appl. No. 11/381,493, Response filed Sep. 22, 2008 to Non-Final Office Action mailed Jun. 23, 2008”, 15 pgs.
“U.S. Appl. No. 11/381,493, Restriction Requirement mailed Mar. 26, 2008”, 7 pgs.
“U.S. Appl. No. 11/640,552, Response filed Auag. 11, 2009 to Non Final Office Action mailed May 11, 2009”, 10 pgs.
“U.S. Appl. No. 11/733,339, Examiner Interview Summary mailed Aug. 13, 2009”, 2 pgs.
“U.S. Appl. No. 11/733,339, Non-Final Office Action mailed Apr. 30, 2009”, 10 pgs.
“U.S. Appl. No. 11/733,339, Non-Final Office Action mailed Sep. 9, 2009”, 9 pgs.
“U.S. Appl. No. 11/733,339, Notice of Allowance mailed Feb. 25, 2010”, 6 pgs.
“U.S. Appl. No. 11/733,339, Notice of Allowance mailed Apr. 21, 2010”, 6 pgs.
“U.S. Appl. No. 11/733,339, Response filed Dec. 4, 2009 to Non Final Office Action mailed Sep. 9, 2009”, 11 pgs.
“U.S. Appl. No. 12/004,892, Final Office Action mailed Sep. 14, 2011”, 8 pgs.
“U.S. Appl. No. 12/004,892, Response filed Jan. 4, 2012 to Final Office Action mailed Sep. 14, 2011”, 11 pgs.
“U.S. Appl. No. 12/102,480, Final Office Action mailed Jan. 18, 2011”, 6 pgs.
“U.S. Appl. No. 12/102,480, Non-Final Office Action mailed Aug. 18, 2010”, 9 pgs.
“U.S. Appl. No. 12/102,480, Notice of Allowance mailed May 19, 2011”, 8 pgs.
“U.S. Appl. No. 12/102,480, Response filed Apr. 18, 2011 to Final Office Action mailed Jan. 18, 2011”, 9 pgs.
“U.S. Appl. No. 12/102,480, Response filed Nov. 18, 2010 to Non Final Office Action mailed Aug. 18, 2010”, 13 pgs.
“U.S. Appl. No. 12/435,928, Non-Final Office Action mailed Oct. 22, 2010”, 14 pgs.
“U.S. Appl. No. 12/435,928, Notice of Allowance mailed May 4, 2011”, 9 pgs.
“U.S. Appl. No. 12/435,928, Response filed Jan. 21, 2011 to Non Final Office Action mailed Oct. 22, 2010”, 13 pgs.
“U.S. Appl. No. 12/648,687, Notice of Allowance mailed Aug. 17, 2010”, 7 pgs.
“U.S. Appl. No. 12/684,303, Non Final Office Action mailed Apr. 5, 2011”, 5 pgs.
“U.S. Appl. No. 12/691,364, Advisory Action mailed Mar. 30, 2011”, 3 pgs.
“U.S. Appl. No. 12/691,364, Final Office Action mailed Dec. 28, 2010”, 8 pgs.
“U.S. Appl. No. 12/691,364, Non-Final Office Action mailed Jul. 20, 2010”, 7 pgs.
“U.S. Appl. No. 12/691,364, Notice of Allowance mailed Sep. 13, 2011”, 7 pgs.
“U.S. Appl. No. 12/691,364, Response filed Feb. 17, 2011 to Final Office Action mailed Dec. 28, 2010”, 9 pgs.
“U.S. Appl. No. 12/691,364, Response filed Oct. 18, 2010 to Non-Final Office Action mailed Jul. 20, 2010”, 11 pgs.
“U.S. Appl. No. 12/713,669, Non-Final Office Action mailed Mar. 2, 2011”, 5 pgs.
“U.S. Appl. No. 12/713,669, Notice of Allowance mailed Jun. 24, 2011”, 5 pgs.
“U.S. Appl. No. 12/713,669, Response filed May 16, 2011 to Non-Final Office Action mailed Mar. 2, 2011”, 8 pgs.
“U.S. Appl. No. 13/218,672, Non Final Office Action mailed Mar. 15, 2012”, 6 pgs.
“U.S. Appl. No. 13/218,672, Notice of Allowance mailed Aug. 6, 2012”, 7 pgs.
“U.S. Appl. No. 13/218,672, Response filed Jun. 14, 2012 to Non Final Office Action mailed Mar. 15, 2012”, 9 pgs.
“European Application Serial No. 02799254.4, Office Action mailed Sep. 23, 2009”, 4 pgs.
“European Application Serial No. 05732873.4, Communication dated Feb. 13, 2007”, 3 pgs.
“European Application Serial No. 05732873.4, Communication dated Nov. 15, 2006”, 2 pgs.
“European Application Serial No. 05732873.4, Office Action mailed Mar. 23, 2010”, 2 pgs.
“European Application Serial No. 05732873.4, Response filed Aug. 10, 2007 to Communication dated Feb. 13, 2007”, 13 pgs.
“European Application Serial No. 05732873.4, Response filed Oct. 1, 2010 to Office Action mailed Mar. 23, 2010”, 11 pgs.
“European Application Serial No. 05737578.4, Communication dated Feb. 13, 2007”, 3 pgs.
“European Application Serial No. 05737578.4, European Office Action mailed Jul. 13, 2010”, 4 pgs.
“European Application Serial No. 05737578.4, Office Action Response Filed Nov. 22, 2010”, 12 pgs.
“European Application Serial No. 05737578.4, Response filed Aug. 10, 2007 to Communication dated Feb. 13, 2007”, 15 pgs.
“European Application Serial No. 05783799.9, Communication pursuant to Article 94(3) EPC mailed Jun. 16, 2009”, 3 pgs.
“European Application Serial No. 05783799.9, Office Action mailed Oct. 25, 2010”, 3 pgs.
“European Application Serial No. 05783799.9, Response filed Mar. 3, 2011 to Office Action mailed Oct. 25, 2010”, 12 pgs.
“European Application Serial No. 05783799.9, Response filed Oct. 23, 2009 to Communication mailed Jun. 16, 2009”, 9 pgs.
“European Application Serial No. 05783882.3, Communication pursuant to Article 94(3) EPC mailed Jun. 16, 2009”, 3 pgs.
“European Application Serial No. 06750873.9, Office Action mailed Apr. 14, 10”, 5 pgs.
“European Application Serial No. 06750873.9, Office Action mailed May 7, 2009”, 2 pgs.
“European Application Serial No. 06750873.9, Office Action Response Filed Oct. 22, 2010”, 13 pgs.
“European Application Serial No. 06750873.9, Response filed Sep. 16, 2009 to Communication mailed May 7, 2009”, 7 pgs.
“International Application No. PCT/US2002/040488, International Search Report mailed May 9, 2003”, 7 pgs.
“International Application No. PCT/US2003/003748, International Search Report mailed Oct. 20, 2003”, 5 pgs.
“International Application No. PCT/US2005/011606, International Search Report and Written Opinion mailed Jul. 26, 2005”, 12 pgs.
“International Application No. PCT/US2005/011639, International Search Report and Written Opinion mailed Aug. 26, 2005”, 12 pgs.
“International Application No. PCT/US2005/028052, International Preliminary Report on Patentability mailed Feb. 22, 2007”, 8 pgs.
“International Application No. PCT/US2005/028052, International Search Report and Written Opinion mailed Nov. 29, 2005”, 12 pgs.
“International Application No. PCT/US2005/028059, International Preliminary Report on Patentability mailed Feb. 13, 2007”, 9 pgs.
“International Application No. PCT/US2005/028059, International Search Report and Written Opinion mailed Jan. 12, 2005”, 13 pgs.
“International Application No. PCT/US2005/028059, International Search Report and Written Opinion mailed Dec. 1, 2005”, 13 pgs.
“International Application No. PCT/US2006/014957, International Search Report and Written Opinion mailed Sep. 29, 2006”, 16 pgs.
“International Application No. PCT/US2007/069424, International Search Report mailed Dec. 27, 2007”, 4 pgs.
“International Application No. PCT/US2007/069424, Written Opinion mailed Dec. 27, 2007”, 9 pgs.
“International Application No. PCT/US2007/069426, International Search Report mailed Dec. 27, 2007”, 4 pgs.
“International Application No. PCT/US2007/069426, Written Opinion mailed Dec. 27, 2007”, 8 pgs.
“International Application No. PCT/US2007/072827, International Search Report mailed Dec. 10, 2007”, 4 pgs.
“International Application No. PCT/US2007/072827, Written Opinion mailed Dec. 10, 2007”, 6 pgs.
“Japanese Application Serial No. 2007-507458, Office Action mailed Aug. 31, 2010”, (w/ English Translation), 4 pgs.
“Japanese Application Serial No. 2007-507458, Office Action Response Filed: Nov. 26, 2010”, (w/ English Translation of amended claims), 6 pgs.
“Japanese Application Serial No. 2007-507465, Notice of Allowance mailed Feb. 14, 2011”, 3 pgs.
“Japanese Application Serial No. 2007-507465, Office Action mailed Sep. 1, 2010”, 4 pgs.
“Japanese Application Serial No. 2007-507465, Office Action Response Filed Nov. 24, 2010”, 10 pgs.
“Japanese Application Serial No. 2007-525697, Office Action mailed Apr. 19, 2011”, (w/ English Translation), 7 pgs.
“Part III—Department of Health and Human Services, Office of the Secretary—45 CFR Part 142—Security and Electronic Signature Standards; Proposed Rule”, Federal Register, 63(155), (Aug. 12, 1998), 43241-43280.
“Public Law 104-191 [H.R. 3103]—Health Insurance Portability and Accountability Act of 1996”, United States Public Laws—104th Congress—2nd Session, (Aug. 21, 1996), 78 pgs.
Adams, J. T, “An introduction to IEEE STD 802.15.4”, Aerospace conference, 2006 IEEE big sky, (Mar. 4-11, 2006), 1-8.
Bange, Joseph E, et al., “U.S. Appl. No. 11/101,196, filed Apr. 7, 2005”, 19 pgs.
Bange, Joseph E, et al., “Implantable Medical Device Telemetry With Adaptive Frequency Hopping”, U.S. Appl. No. 11/456,937, filed Jul. 12, 2006, 35 pgs.
Bange, Joseph E, et al., “Implantable Medical Device Telemetry With Periodic Frequency Hopping”, U.S. Appl. No. 11/456,942, filed Jul. 12, 2006, 43 pgs.
Bange, Joseph E, et al., “System and Method for RF Wake-Up of Implantable Medical Device”, U.S. Appl. No. 11/101,142, filed Apr. 7, 2005, 19 pgs.
Crow, B P, et al., “Investigation of the IEEE 802.11 medium access control (MAC) sublayer functions”, Proceedings IEEE INFOCOM '97. Sixteenth Annual Joint Conference of the IEEE Computer and Communications Societies, vol. 1, (1997), 126-133.
Diffie, W., “The First Ten Years of Public-Key Cryptography”, Proceedings of the IEEE, 76(5), (May 1988), 560-577.
Duflot, M., et al., “A formal analysis of bluetooth device discovery”, International journal on software tools for technology transfer, 8 (6), (Jul. 5, 2006), 621-632.
Golmie, N., et al., “The Evolution of Wireless LANs and PANs -Bluetooth and WLAN coexistence: challenges and solutions”, IEEE Personal Communications, 10(6), (Dec. 2003), 22-29.
Guidant, “Feature Sheet and Specifications: Zoom Latitude”, Doc. No. C3-194-1005, (2005), 2 pgs.
Guidant, “Go Beyond the Wand”, Doc. No. C3-107-0505, (2005), 2 pgs.
Guidant, “Think Beyond the Wand”, Doc. No. C3-101-0505, (2005), 3 pgs.
Guidant, “What if you could ZIP through implants and follow ups?”, Doc. No. C3-117-0505, (2005), 2 pgs.
Guidant, “What if your patient develops diaphragmatic stimulation?”, Doc. No. 03-116-0505, (2005), 2 pgs.
Harney, Austin, et al., “Wireless Short-Range Devices: Designing a Global License-Free System for Frequencies <1 GHz”, Analog Dialogue 40-03, (Mar. 2006), 1 pg.
Healy, S. J., et al., “System and Method for Providing Secure Exchange of Sensitive Information With an Implantable Medical Device”, U.S. Appl. No. 10/801,150, filed Mar. 15, 2004, 30 pgs.
Katoozi, M., et al., “On-Demand Retransmission of Data With an Implantable Medical Device”, U.S. Appl. No. 10/870,328, filed Jun. 17, 2004, 30 pgs.
Quiles, S., “U.S. Appl. No. 10/914,499, filed Aug. 9, 2004”, 30 pgs.
Quiles, Sylvia, “U.S. Appl. No. 10/914,496, filed Aug. 9, 2004”, 23 pgs.
Rawat, Prashant, et al., “U.S. Appl. No. 10/744,943, filed Dec. 22, 2003”, 34 pgs.
Seeberger, M., “Dynamic Telemetry Link Selection for an Implantable Device”, U.S. Appl. No. 10/914,638, filed Aug. 9, 2004.
Von Arx, J. A., et al., “A Telemetry Duty Cycle Management System for an Implantable Medical Device”, U.S. Appl. No. 11/325,584, filed Jan. 4, 2006, 37 pgs.
Von Arx, Jeffrey, “U.S. Appl. No. 10/870,324, filed Jun. 14, 2004”, 38 pgs.
Zhu, H., et al., “A survey of quality of service in IEEE 802.11 Networks”, IEEE Wireless Communications, IEEE Service Center, Piscataway, NJ, US, 11(4), (Aug. 2004), 6-14 pgs.
Wikipedia, “SHA hash functions” <http://en.wikipedia.org/wiki/SHA> (1993), 8 pgs.
“U.S. Appl. No. 10/601,763, Non Final Office Action mailed Feb. 23, 2006”, 9 pgs.
“U.S. Appl. No. 10/601,763, Notice of Allowance mailed Aug. 4, 2006”, 8 pgs.
“U.S. Appl. No. 10/601,763, Response filed May 23, 2006 to Non Final Office Action mailed Feb. 23, 2006”, 13 pgs.
“U.S. Appl. No. 10/601,763, Supplemental Notice of Allowability mailed Oct. 23, 2006”, 4 pgs.
“U.S. Appl. No. 10/744,943, Non-Final Office Action mailed Mar. 19, 2010”, 10 pgs.
“U.S. Appl. No. 10/744,943, Non-Final Office Action mailed Apr. 20, 2007”, 8 pgs.
“U.S. Appl. No. 10/744,943, Non-Final Office Action mailed Aug. 1, 2006”, 7 pgs.
“U.S. Appl. No. 10/744,943, Non-Final Office Action Mailed Aug. 7, 2009”, 11 pgs.
“U.S. Appl. No. 10/744,943, Non-Final Office Action Mailed Oct. 28, 2008”, 16 pgs.
“U.S. Appl. No. 10/744,943, Non-Final Office Action mailed Dec. 15, 2005”, 7 pgs.
“U.S. Appl. No. 10/744,943, Notice of Allowance mailed Nov. 1, 2010”, 7 pgs.
“U.S. Appl. No. 10/744,943, Response filed Feb. 1, 2007 to Non-Final Office Action mailed Aug. 1, 2006”, 11 pgs.
“U.S. Appl. No. 10/744,943, Response filed Mar. 30, 2009 to Non Final Office Action mailed Oct. 28, 2008”, 8 pgs.
“U.S. Appl. No. 10/744,943, Response filed May 15, 2006 to Non-Final Office Action mailed Dec. 5, 2005”, 9 pgs.
“U.S. Appl. No. 10/744,943, Response filed Aug. 18, 2010 to Non Final Office Action mailed Mar. 19, 2010”, 14 pgs.
“U.S. Appl. No. 10/744,943, Response filed Aug. 19, 2008 to Final Office Action mailed Feb. 21, 2008”, 9 pgs.
“U.S. Appl. No. 10/744,943, Response filed Sep. 6, 2005 to Restriction Requirement mailed Aug. 3, 2005”, 8 pgs.
“U.S. Appl. No. 10/744,943, Response filed Nov. 9, 2009 to Non Final Office Action mailed Aug. 7, 2009”, 12 pgs.
“U.S. Appl. No. 10/744,943, Restriction Requirement mailed Aug. 3, 2005”, 5 pgs.
“U.S. Appl. No. 10/801,070, 312 Amendment filed Apr. 11, 2007”, 4 pgs.
“U.S. Appl. No. 10/801,070, Non Final Office Action mailed Feb. 6, 2006”, 17 pgs.
“U.S. Appl. No. 10/801,070, Non Final Office Action mailed Jun. 16, 2006”, 6 pgs.
“U.S. Appl. No. 10/801,070, Non-Final Office Action mailed Jun. 16, 2006”, 6 pgs.
“U.S. Appl. No. 10/801,070, Non-Final Office Action mailed Feb. 6, 2006”, 20 pgs.
“U.S. Appl. No. 10/801,070, Notice of Allowance mailed Jan. 12, 2007”, 7 pgs.
“U.S. Appl. No. 10/801,070, Response filed Mar. 7, 2006 to Non Final Office Action mailed Feb. 6, 2006”, 10 pgs.
“U.S. Appl. No. 10/801,070, Response filed Sep. 18, 2006 to Non Final Office Action mailed Jun. 16, 2006”, 11 pgs.
“U.S. Appl. No. 10/801,070, Response filed Mar. 7, 2006 to Non-Final Office Action”, 14 pgs.
“U.S. Appl. No. 10/801,070, Response filed Sep. 18, 2006 to Non Final Office Action mailed Jun. 16, 2006”, 15 pgs.
“U.S. Appl. No. 10/914,499, Final Office Action mailed Jul. 20, 2010”, 5 pgs.
“U.S. Appl. No. 10/914,641, Final Office Action dated Apr. 17, 2007”, 10 pgs.
“U.S. Appl. No. 10/914,641, Final Office Action mailed Feb. 20, 2008”, 9 pgs.
“U.S. Appl. No. 10/914,641, Final Office Action mailed Mar. 10, 2009”, 10 pgs.
“U.S. Appl. No. 10/914,641, Final Office Action mailed Mar. 11, 2010”, 11 pgs.
“U.S. Appl. No. 10/914,641, Final office action mailed Mar. 15, 2007”, 10 pgs.
“U.S. Appl. No. 10/914,641, Non Final Office Action mailed Aug. 2, 2006”, 9 pgs.
“U.S. Appl. No. 10/914,641, Non Final Office Action mailed Aug. 18, 2009”, 11 pgs.
“U.S. Appl. No. 10/914,641, Non Final Office Action mailed Aug. 22, 2008”, 9 pgs.
“U.S. Appl. No. 10/914,641, Non Final Office Action Mailed Aug. 31, 2007”, 9 pgs.
“U.S. Appl. No. 10/914,641, Notice of Allowance dated Aug. 4, 2006”, 8 pgs.
“U.S. Appl. No. 10/914,641, Notice of Allowance mailed Oct. 6, 2010”, 5 pgs.
“U.S. Appl. No. 10/914,641, Response filed Jan. 2, 2007 to Non Final Office Action mailed Aug. 2, 2006”, 9 pgs.
“U.S. Appl. No. 10/914,641, Response filed Jan. 18, 2007 to Non-Final Office Action”, 21 pgs.
“U.S. Appl. No. 10/914,641, Response filed May 11, 2009 to Final Office Action mailed Mar. 10, 2009”, 12 pgs.
“U.S. Appl. No. 10/914,641, Response filed May 18, 2010 to Final Office Action mailed Mar. 11, 2010”, 11 pgs.
“U.S. Appl. No. 10/914,641, Response filed Jun. 10, 2009 to Advisory Action mailed Mar. 10, 2009”, 11 pgs.
“U.S. Appl. No. 10/914,641, Response filed Jun. 16, 2006 to Restriction Requirement mailed May 16, 2006”, 5 pgs.
“U.S. Appl. No. 10/914,641, Response filed Jul. 16, 2007 to Final Office Action mailed Mar. 15, 2007”, 9 pgs.
“U.S. Appl. No. 10/914,641, Response filed Nov. 18, 2009 to Non Final Office Action mailed Aug. 18, 2009”, 11 pgs.
“U.S. Appl. No. 10/914,641, Response filed Nov. 24, 2008 to Non Final Office Action mailed Aug. 22, 2008”, 11 pgs.
“U.S. Appl. No. 10/914,641, Response filed Nov. 30, 2007 to Non Final Office Action mailed Aug. 31, 2007”, 14 pgs.
“U.S. Appl. No. 10/914,641, Restriction Requirement mailed May 16, 2006”, 5 pgs.
“U.S. Appl. No. 11/068,478, Advisory Action mailed Sep. 16, 2008”, 3 pgs.
“U.S. Appl. No. 11/068,478, Corrected Notice of Allowance mailed Jun. 19, 2009”, 4 pgs.
“U.S. Appl. No. 11/068,478, Response filed Nov. 3, 2008 to Advisory Action mailed Sep. 16, 2008”, 17 pgs.
“U.S. Appl. No. 11/456,942, Advisory Action mailed May 7, 2009”, 6 pgs.
“U.S. Appl. No. 11/456,942, Final Office Action mailed Mar. 10, 2009”, 15 pgs.
“U.S. Appl. No. 11/456,942, Non-Final Office Action mailed Aug. 18, 2008”, 15 pgs.
“U.S. Appl. No. 11/456,942, Notice of Allowance mailed Jul. 17, 2009”, 13 pgs.
“U.S. Appl. No. 11/456,942, Response filed May 4, 2009 to Final Office Action mailed Mar. 10, 2009”, 9 pgs.
“U.S. Appl. No. 11/456,942, Response filed Jun. 4, 2009 to Advisory Action mailed May 7, 2009”, 10 pgs.
“U.S. Appl. No. 11/456,942, Response filed Nov. 18, 2008 to Non-Final Office Action mailed Aug. 18, 2008”, 10 pgs.
“U.S. Appl. No. 11/640,552, Examiner Interview Summary mailed May 27, 2010”, 4 pgs.
“U.S. Appl. No. 11/640,552, Examiner Interview Summary mailed Aug. 10, 2009”, 3 pgs.
“U.S. Appl. No. 11/640,552, Final Office Action mailed Mar. 24, 2010”, 8 pgs.
“U.S. Appl. No. 11/640,552, Non Final Office Action mailed May 11, 2009”, 8 pgs.
“U.S. Appl. No. 11/640,552, Response filed Jun. 24, 2010 to Final Office Action mailed Mar. 24, 2010”, 9 pgs.
“U.S. Appl. No. 11/738,942, Non Final Office Action mailed Jan. 20, 2010”, 8 pgs.
“U.S. Appl. No. 11/738,942, Non Final Office Action mailed Jun. 9, 2009”, 14 pgs.
“U.S. Appl. No. 11/738,942, Notice of Allowance mailed Jun. 17, 2010”, 8 pgs.
“U.S. Appl. No. 11/738,942, Preliminary Amendment filed Apr. 23, 2007”, 6 pgs.
“U.S. Appl. No. 11/738,942, Response filed Apr. 20, 2010 to Non Final Office Action mailed Jan. 20, 2010”, 10 pgs.
“U.S. Appl. No. 11/738,942, Response filed Sep. 16, 2009 to Non Final Office Action mailed Jun. 9, 2009”, 9 pgs.
“U.S. Appl. No. 12/004,892, Notice of Allowance mailed Jun. 21, 2012”, 5 pgs.
“U.S. Appl. No. 12/145,343, Final Office Action mailed Mar. 8, 2011”, 9 pgs.
“U.S. Appl. No. 12/145,343, Non-Final Office Action mailed Oct. 26, 2010”, 10 pgs.
“U.S. Appl. No. 12/145,343, Response filed Jan. 25, 2011 to Non Final Office Action mailed Oct. 26, 2010”, 9 pgs.
“U.S. Appl. No. 12/145,343, Response filed May 9, 2011 to Final Office Action mailed Mar. 8, 2011”, 9 pgs.
“U.S. Appl. No. 12/145,343, Response filed Sep. 14, 2010 to Restriction Requirement mailed Aug. 26, 2010”, 8 Pgs.
“U.S. Appl. No. 12/145,343, Restriction Requirement mailed Aug. 26, 2010”, 7 pgs.
“U.S. Appl. No. 12/684,303, Response filed Jun. 13, 2011 to Non-Final Office Action mailed Apr. 5, 2011”, 10 pgs.
“U.S. Appl. No. 12/950,359, Notice of Allowance mailed Jun. 23, 2011”, 7 pgs.
“European Application Serial No. 02799254.4, Communication mailed Oct. 2, 2006”, 4 pgs.
“European Application Serial No. 02799254.4, Response filed Feb. 15, 2010 to Office Action mailed Sep. 23, 2009”, 12 pgs.
“European Application Serial No. 02799254.4, Response filed Apr. 2, 2007 to Communication mailed Oct. 2, 2006”, 18 pgs.
“European Application Serial No. 03709003.2, Office Action mailed Jul. 27, 2010”, 6 pgs.
“European Application Serial No. 03709003.2, Response filed Jan. 27, 2011 to office action mailed Jul. 27, 2010”, 10.
“European Application Serial No. 05732873.4, Office Action mailed Nov. 17, 2011”, 4 pgs.
“European Application Serial No. 05732873.4, Response filed Jan. 26, 2012 to Office Action mailed Nov. 17, 2011”, 11 pgs.
“European Application Serial No. 05783882.3, Response filed Oct. 22, 2009 to Communication mailed Jun. 16, 2009”, 7 pgs.
“International Application No. PCT/US2004/019902, International Search Report dated Dec. 6, 2004”, 4 pgs.
“International Application No. PCT/US2004/019902, Written Opinion dated Dec. 6, 2004”, 6 pgs.
“International Application No. PCT/US2005/008521, International Preliminary Report on Patentability mailed Sep. 28, 2006”, 13 pgs.
“International Application No. PCT/US2005/008521, International Search Report and Written Opinion mailed Oct. 11, 2005”, 19 pgs.
“International Application No. PCT/US2005/008521, International Search Report mailed Oct. 11, 2005”, 19 pgs.
“International Application No. PCT/US2005/008521, Invitation to Pay Additional Fees and Partial International Search Report mailed Jul. 29, 2005”, 7 pgs.
“Japanese Application No. 2004-527861, Notice of Allowance mailed Jun. 16, 2010”, 3 pgs.
“Japanese Application Serial No. 2006-517513, Notice of Allowance mailed Jan. 21, 2011”, 3 pgs.
“Japanese Application Serial No. 2006-517513, Office Action mailed Jan. 18, 2010”, (w/ English Translation), 5 pgs.
“Japanese Application Serial No. 2006-517513, Office Action mailed Oct. 12, 2010”, 1 pg.
“Japanese Application Serial No. 2006-517513, Response filed Apr. 19, 2010 to Office Action mailed Jan. 18, 2010”, (w/ English Translation of Amended Claims), 41 pgs.
“Japanese Application Serial No. 2006-517513, Response filed Dec. 13, 2010 to Office Action Sep. 14, 2010”, (w/ English Translation of Amended Claims), 16 pgs.
“Japanese Application Serial No. 2007-507458, Notice of Allowance mailed Feb. 14, 2011”, 3 pgs.
“Japanese Application Serial No. 2007-525695, Office Action mailed Feb. 3, 2011”, (w/ English Translation), 5 pgs.
“Japanese Application Serial No. 2007-525695, Response filed Apr. 20, 2011 to Non Final Office Action mailed Feb. 3, 2011”, (w/ English Translation of Amended Claims), 10 pgs.
“Japanese Application Serial No. 2007-525697, Response filed Jun. 8, 2011 to Office Action mailed Apr. 19, 2011”, (w/ English Translation of Amended Claims), 13 pgs.
Hammond, E., “Perspectives on Implementation of Administrative Simplification Provisions of P.L. 104-191”, National Committee on Vital and Health Statistics, Subcommittee on Health Data Needs, Standards and Security, (Feb. 11, 1997), 4 pgs.
Healy, S. J., et al., “Cryptographic Authentication for Telemetry With an Implantable Medical Device”, U.S. Appl. No. 10/801,070, filed Mar. 15, 2004, 38 pgs.
Quiles, S., “Secure Remote Access for an Implantable Medical Device”, U.S. Appl. No. 10/914,641, filed Aug. 9, 2004, 41 pgs.
Von Arx, J., et al., “System and Method for Securely Authenticating a Data Exchange Session With an Implantable Medical Device”, U.S. Appl. No. 10/800,806, filed Mar. 15, 2004, 47 pgs.
Zarlink Semiconductor, “Medical Implantable RF Transceiver”, (2005), 40 pgs.
Related Publications (1)
Number Date Country
20130090705 A1 Apr 2013 US
Provisional Applications (1)
Number Date Country
60560171 Apr 2004 US
Continuations (3)
Number Date Country
Parent 13218672 Aug 2011 US
Child 13682263 US
Parent 12102480 Apr 2008 US
Child 13218672 US
Parent 11101142 Apr 2005 US
Child 12102480 US