Programmer patch for transmitting sideband signals

Abstract

A system includes a programmer configured to communicate with a medical device using a first communication protocol; and a communication device that is physically coupled externally to the programmer and configured to: receive a first wireless signal from the programmer; and output, in response to receiving the first wireless signal, a second wireless signal to the medical device using a second communication protocol that is different than the first communication protocol.

Description

Docket No.: A0012687W001 PROGRAMMER PATCH FOR TRANSMITTING SIDEBAND SIGNALSCROSS RELATED APPLICATION

[0001] This application is a PCT application that claims priority to, and the benefit of, U.S. Provisional Patent Application No. 63 / 749,388, filed January 24, 2025, the entire contents of which is incorporated herein by reference.TECHNICAL FIELD

[0002] This disclosure generally relates to medical device communicationBACKGROUND

[0003] Medical devices may be external or implanted, and may be used to sense neural signals (e.g., central and peripheral nerves) and / or deliver electrical stimulation therapy to various tissue sites of a patient to treat a variety of symptoms or conditions such as, for example, one or more of chronic pain, tremor, Parkinson’s disease, other movement disorders, epilepsy, urinary or fecal incontinence, sexual dysfunction, obesity, gastroparesis, sleep apnea, neural control of prosthetic devices, or stimulation to provide peripheral sensation. Medical devices include telemetry circuitry to communicate with other devices, such as a programmer.SUMMARY

[0004] This disclosure describes example techniques for using a communication device that physically couples externally to a programmer to allow the programmer to communicate with a medical device using a communication protocol not supported by the programmer. The communication device may receive a wireless signal (e.g., a near-field communication signal) from the programmer. In response to receiving the wireless signal, the communication device may output a wireless signal in accordance with the communication protocol not supported by the programmer. The communication device may be formed on a circuit board that affixes to the programmer (e.g., to a backside that is a side opposite of a display of the programmer or to cover of the programmer), without needing additional wiring (e.g., such as wiring to connect to an input / output (IO) port of the programmer). In this manner, when there is benefit in wireless transmission to the medical device using the communication protocol that the programmer does not support, the communication device functions as intermediate device to support such wireless transmission.

[0005] Furthermore, because the communication device is affixed to the programmer, there is less burden on the user to track two different devices (e.g., separately holding the programmerDocket No.: A0012687W001 and the communication device). In one or more examples, the communication device may be fully powered by signals from the programmer allowing the communication device to operate without separate power sources that require replacement. However, it may be possible for the communication device to operate with a separate power source in some examples.

[0006] In one example, the disclosure describes a system comprising: a programmer configured to communicate with a medical device using a first communication protocol; and a communication device that is physically coupled externally to the programmer and configured to: receive a first wireless signal from the programmer; and output, in response to receiving the first wireless signal, a second wireless signal to the medical device using a second communication protocol that is different than the first communication protocol.

[0007] In one example, the disclosure describes a method for communicating between devices, the method comprising: receiving, with a communication device, a first wireless signal from a programmer that is configured to communicate with a medical device using a first communication protocol, wherein the communication device is physically coupled externally to the programmer; and outputting, in response to receiving the first wireless signal, a second wireless signal to the medical device using a second communication protocol that is different than the first communication protocol.

[0008] The details of one or more examples of the techniques of this disclosure are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the techniques will be apparent from the description and drawings, and from the claims.BRIEF DESCRIPTION OF DRAWINGS

[0009] FIG. l is a conceptual diagram illustrating an example system including a medical device, a communication device, and a programmer according to one or more techniques of this disclosure.

[0010] FIG. 2 is a conceptual diagram illustrating an example of a communication device affixed to a programmer.

[0011] FIG. 3 is a block diagram illustrating example components of a communication device.

[0012] FIG. 4 is a block diagram illustrating an example configuration of components of external programmer of FIG. 1.

[0013] FIG. 5 is a block diagram illustrating example components of the medical device of FIG. 1.

[0014] FIG. 6 is a flowchart illustrating an example method of operation.Docket No.: A0012687W001DETAILED DESCRIPTION

[0015] Medical devices such as implantable medical devices (HMDs) or external medical devices are configured to communicate with other devices in addition to delivering therapy. The medical devices may be configured to communicate using mainstream wireless communication protocols such as the BlueTooth™ protocol or the BlueTooth™ Low Energy (BLE) protocol, including the BLE 5.4 specification. The BlueTooth or BLE protocol may be considered as examples of a communication protocol used for advertisement-based communication. For instance, in the BlueTooth and BLE protocol, the medical device may perform operations in accordance with an advertisement mode and a connection mode. In the advertisement mode (also called broadcast or beacon mode), the medical device broadcasts advertising packets that include relevant information to allow other devices to know the presence of the medical device, as well as to allow connection with the medical device. The term “broadcast” means that the medical device transmits the packets (e.g., data) without the medical device addressing the packets to any specific device. In the connection mode, the medical device and another device engage in a handshake to establish a connection as part of a pairing process or bonding process.

[0016] The term “advertisement-based communication” is used to generically refer to communication protocols in which the medical device may output information indicating the presence of the medical device to establish a communication link with another device. The BlueTooth and BLE protocols are examples of such communication protocols that use advertisement-based communication. However, the example techniques should not be considered limited to BlueTooth and BLE protocols.

[0017] In one or more examples, the medical devices may be configured to communicate in accordance with a communication protocol used for immediate-link, short-range communication. The term “immediate-link” may refer to the capability of the medical device to always be listening (e.g., be in a ready-state to process data or commands) for communications received in the communication protocol used for immediate-link communication. “Short-range” may refer to a signal that can be received within a relatively short-range (e.g., within 10 centimeters (cm)). If the device receiving the short-range communication is more than 10 cm, the signal may be sufficiently attenuated that the device receiving the short-range communication cannot differentiate the signal from noise. One example of the communication protocol used for immediate-link, short-range communication is inductive telemetry, but the examples are not limited to inductive telemetry.

[0018] The reception of a signal in accordance with the communication protocol used for immediate-link communication triggers a response or process by the medical device withoutDocket No.: A0012687W001 requiring the same level of overhead or initial steps needed to establish a communication link in communication protocols used for advertisement-based communication. There may be various benefits of using the immediate-link, short-range communication, such as controlling the advertisement frequency of the medical device, resetting communication if the BlueTooth communication is faulty (e.g., non-responsive), waking up the medical device if the medical device is in sleep mode, etc.

[0019] While a programmer for the medical device may communicate using a first communication protocol (e.g., BlueTooth and BLE protocols), the programmer may not support the second communication protocol (e.g., immediate-link, short-range communication protocol). For example, rather than providing a user (e.g., clinician or patient) with a separate device for programming the medical device, there may be ease-of-use benefits of reusing a smart phone or tablet, that the user already owns, as a programmer for the medical device. For instance, the smart phone or tablet may store a programming application that is used to program the medical device and receive data from the medical device. However, commercial smart phones or tablets tend not to support the second communication protocol.

[0020] In accordance with one or more examples described in this disclosure, a communication device may be configured to be externally couple to the programmer and be configured to support communication using the second communication protocol. For example, in addition to communicating using the BlueTooth communication protocol, the programmer (e.g., commercial smart phone or tablet) may be configured to support other communication techniques, such as near-filed communication (NFC). In one or more examples, the receiving of the NFC signal may trigger the communication device to output a wireless signal to the medical device in accordance with the second communication protocol.

[0021] In this disclosure, the first communication protocol (e.g., a protocol with relatively high overhead such as BlueTooth), the second communication protocol (e.g., immediate-link, short-range communication such as inductive telemetry with relatively low overhead), and NFC should not be confused. Commercial smart phones and tablets may already support the first communication protocol and NFC, but may not support the second communication protocol. The second communication protocol may be a specific communication protocol used for sideband communication with the medical device (e.g., to control advertisement frequency, wake-up, reset, etc.).

[0022] As an example, patient may desire to establish a BlueTooth communication link between the programmer and the medical device. However, for power saving purposes, the medical device may transmit the advertisement packets infrequently which delays the establishing the communication link. In one or more examples, the patient may utilize theDocket No.: A0012687W001 programmer application on the programmer to cause the programmer to output an NFC signal. Upon receiving the NFC signal, the communication device may transmit an immediate-link, short-range communication signal to the medical device which causes the medical device to advertise more frequently. That is, the medical device may be configured to respond to the immediate-link, short-range communication signal by advertising more frequently to reduce the delay in establishing a BlueTooth communication link.

[0023] In some examples, the communication device may be configured to power the components of the communication device using the NFC signal. The signal content of the NFC signal may be immaterial, and any NFC signal of sufficient duration and sufficient power may be adequate for powering components of the communication device. The communication device converts the NFC signal to a power signal to power components of the communication device as well as store energy in one or more capacitors of the communication device used for delivering the wireless signal to the medical device. In examples where the communication device converts energy from the NFC signal, the communication device may not utilize a non-rechargeable battery or any other battery.

[0024] However, in some examples, it may be possible for the communication device to utilize a battery. For instance, the reception of the NFC signal may cause the communication device to output the wireless signal to the medical device, but the power for the components may come from the battery. As another example, the battery may slowly recharge the one or more capacitors on the communication device, and the one or more capacitors may output an electrical signal used for transmitting the wireless signal to the medical device.

[0025] In one or more of the above examples, the content of the NFC signal may be immaterial, as the NFC signal is merely being utilized for power and to trigger the communication device to output a wireless signal. However, in some examples, the NFC signal may include confirmation information confirming that the communication device is to output the wireless signal. If the confirmation information is not included, the communication device may not output the wireless signal. In this manner, if other applications executing on the programmer output an NFC signal, such output of an NFC signal should not cause the communication device to output a wireless signal.

[0026] Furthermore, in some examples, the communication device may be configured for two-way communication. For instance, the communication device may periodically determine whether there is sufficient energy stored on the one or more capacitors for outputting a wireless signal, and if there is not sufficient energy, the communication device may output a request using an NFC signal (e.g., upstream transmission of an NFC signal) to the programmer requesting an NFC signal (e.g., requesting a downstream transmission of an NFC signal) for purposes ofDocket No.: A0012687W001 recharging the one or more capacitors. As another example, the programmer may periodically poll the communication device (e.g., using a downstream transmission of an NFC signal) requesting information of energy stored in the one or more capacitors. The communication device may output using an NFC signal (e.g., upstream transmission of an NFC signal) the information of energy stored in the one or more capacitors. In some examples, the programmer may be configured to, periodically or whenever the user uses the application for communicating with the medical device, output the NFC signal to recharge the one or more capacitors. That is, the programmer may be configured to periodically, on request, or responsive to user action, transmit wireless signals to the communication device to recharge components of the communication device used for outputting the wireless signal from the communication device.

[0027] As described, having the communication device may allow the user to repurpose a smart phone or tablet that is already available to the user. However, the user may misplace or lose the communication device. In one or more examples, the communication device may be physically coupled externally to the programmer. Physically coupled externally to the programmer may mean that the communication device moves with the programmer while the communication device is physically coupled to the programmer. As one example, the communication device may be affixed to a backside of the programmer or affixed to a cover of the programmer. For instance, the communication device is formed on a first side of a circuit board, and a second side of the circuit board includes adhesive material to affix the communication device to the backside of the programmer or to the cover of the programmer. In such examples, the communication device may be a “sticker / backpack.” The backside may be the side opposite the side of the programmer that includes a display.

[0028] The communication device need not couple to the programmer through a port of the programmer. Rather, the communication device may be physically coupled externally to the programmer, but receive and transmit wirelessly to the programmer, such as via NFC.

[0029] In general, the communication device may be considered as a programmer patch for transmitting sideband signals. For instance, the BlueTooth communication link may be considered as the main communication link. However, there may be benefits of transmitting sideband signals that do not utilize the BlueTooth communication link, such as using immediate-link, short-range communication link. As described above, the sideband signals can be used to increase advertisement frequency, reset communication if the BlueTooth communication is faulty (e.g., non-responsive), wake up the medical device if the medical device is in sleep mode, general reset of the medical device, etc.

[0030] Accordingly, in one or more examples, a programmer (e.g., commercial smart phone or tablet) may be configured to communicate with a medical device using a first communicationDocket No.: A0012687W001 protocol (e.g., BlueTooth). A communication device may be physically coupled externally to the programmer and configured to receive a first wireless signal (e.g., NFC signal) from the programmer, and output, in response to receiving the first wireless signal, a second wireless signal to the medical device using a second communication protocol (e.g., immediate-link, short-range communication protocol) that is different than the first communication protocol.

[0031] In the above, BlueTooth, immediate-link, short-range, and NFC communication protocols are described for purposes of illustration only, and other communication protocols may be used. In some examples, signals, other than NFC signals, whose energy can be harvested (e.g., converted to a power signal) may be utilized instead of or in addition to NFC signals.

[0032] FIG. l is a conceptual diagram illustrating an example system including a medical device, a communication device, and a programmer according to one or more techniques of this disclosure. The example of FIG. 1 includes an implantable medical device (IMD) 100, communication device 102, and a programmer 104. For ease of description, the examples are described with respect to IMD 100, but the techniques should not be considered limited to implantable medical devices, and may be applicable to medical devices generally.

[0033] Programmer 104 may be configured to program the operation of IMD 100. For example, programmer 104 may communicate with IMD 100 to adjust therapy and / or sensing parameters, download recorded data, and so on. Programmer 104 may be patient programmer or a clinician programmer. In the example of FIG. 1, programmer 104 may be a commercial smart phone or tablet. Programmer 104 may be a portable device with a primary function that is not necessarily being a programmer for IMD 100. To program IMD 100, a user may specifically access an application on programmer 104 that is designed to allow programmer 104 to program IMD 100.

[0034] The example of FIG. 1 is a side view of a patient’s leg 106 showing IMD 100 near the ankle and adjacent to the tibial nerve 108. IMD 100 is a leadless neurostimulation device in the example of FIG. 1. IMD 100 can be implanted through the patient’s skin and cutaneous fat layer via a small incision (e.g., about one to three centimeters (cm)) above the tibial nerve 108 on a medial aspect of the patient’s ankle. While the incision may be approximately horizontal to the length of the tibial nerve 108, other incisions or implantation techniques could be used according to physician preference. The example of FIG. 1 describes a neurostimulation implantable medical device for tibial nerve stimulation. In other examples, the techniques of this disclosure may apply to other medical devices, such as wearable or implantable neurostimulation system for use in spinal cord stimulation therapy (e.g., pain therapy), deep brain stimulation, pelvic floor stimulation (e.g., sacral nerve stimulation) as well as to other types of implantable or external medical devices without limitation.Docket No.: A0012687W001

[0035] In the example of FIG. 1, IMD 100 may be positioned adjacent to the region defined by flexor digitorum longus and soleus in which tibial nerve 108 is contained and implanted adjacent and proximal to a fascia layer. One or more electrodes of IMD 100 may face toward tibial nerve 108. Though not shown in FIG. 1, IMD 100 may also connect to one or more leads comprising one or more electrodes (not shown in FIG. 1).

[0036] IMD 100 may be constructed of any polymer, metal, or composite material sufficient to house the components of IMD 100. In this example, IMD 100 may be constructed with a biocompatible housing, such as titanium or stainless steel, or a polymeric material such as silicone or polyurethane, and surgically implanted at a site in patient near the tibial nerve 108, in some examples, while in other examples, implanted near the pelvis, abdomen, or buttocks. The housing of IMD 100 may be configured to provide a hermetic seal for components, such as a rechargeable power source. In addition, the housing of IMD 100 may be selected of a material that facilitates receiving energy to charge the rechargeable power source.

[0037] While providing therapy, an electrical stimulation signal may be transmitted between one or more electrodes through the fascia layer. The electrical signal may be used to stimulate tibial nerve 108 which may be useful in the treatment of overactive bladder (OAB) symptoms of urinary urgency, urinary frequency and / or urge incontinence, fecal incontinence, pain, or other symptoms. The example of FIG. 1 may help relieve some symptoms of some disorders.

[0038] One type of therapy for treating bladder dysfunction includes delivery of electrical stimulation to a target tissue site within a patient to cause a therapeutic effect during delivery of the electrical stimulation. For example, delivery of electrical stimulation from IMD 100 to a target therapy site, e.g., a tissue site that delivers stimulation to modulate activity of a tibial nerve, spinal nerve (e.g., a sacral nerve), a pudendal nerve, dorsal genital nerve, an inferior rectal nerve, a perineal nerve, or branches of any of the aforementioned nerves, may provide a therapeutic effect for bladder dysfunction, such as a desired reduction in frequency of bladder contractions. In some cases, electrical stimulation of the tibial nerve may modulate afferent nerve activities to restore urinary function.

[0039] In some examples, IMD 100 may deliver neurostimulation therapy in a non-continuous manner which may include on-cycles and off-cycles. For example, an IMD 100 may deliver neurostimulation therapy for a specified period of time followed by a specified period of time when the IMD 100 does not deliver neurostimulation (e.g., withholds delivery of neurostimulation). A period during which stimulation is delivered (an on-cycle) may include on and off periods (e.g., a duty cycle or bursts of pulses) with short inter-pulse durations of time when pulses are not delivered.Docket No.: A0012687W001

[0040] The power source of IMD 100 may include one or more capacitors, batteries, or other components (e.g., chemical, or electrical energy storage devices). Example batteries may include lithium-based batteries, nickel metal-hydride batteries, or other materials. In some examples, the power source may be a primary cell battery that is replaced when depleted. In other examples, the power source may be rechargeable. The rechargeable power source may be replenished, refilled, or otherwise capable of increasing the amount of energy stored after energy has been depleted.

[0041] Programmer 104 may be configured to provide therapy parameters to IMD 100, such as amplitude, frequency, and pulse width of the electrical stimulation signal that IMD 100 delivers. Programmer 104 may also receive information from IMD 100, such as sensed signals, temperature, errors, etc. In general, programmer 104 may provide the interface with which a medical professional or user interacts to program IMD 100, as well as view information received from IMD 100. Programmer 104 may include a housing to enclose operational components such as a processor, memory, user interface, telemetry circuitry, and power source. Examples of programmer 104 include a tablet computer, laptop, a smartphone, a dedicated handheld device, or other similar computing devices.

[0042] In one or more examples, IMD 100 may be configured to communicate using two or more communication protocols. A first communication protocol may be used for advertisementbased communication (e.g., BlueTooth), and maybe considered as the main communication link. A second communication protocol may be used for immediate-link, short-range communication, and may be considered as an out-of-band communication link (i.e., sideband).

[0043] As described above, an immediate-link may refer to the capability of IMD 100 to always be listening (e.g., be in a ready-state to process data or commands) for communications received in the first communication protocol used for immediate-link communication. The reception of a signal in accordance with the second communication protocol used for immediate-link communication triggers a response or process by the medical device without requiring the same level of overhead or initial steps needed to establish a communication link in communication protocols used for advertisement-based communication. That is, IMD 100 may be configured to receive signals in accordance with the second communication protocol without advertisement.

[0044] Communications in accordance with the second communication protocol may be considered as low complexity, and requiring minimal communication circuitry overhead. For example, the second communication protocol may be a frequency-shift-keying (FSK) based communication that utilizes a reception coil, as an antenna, to receive communication. In theDocket No.: A0012687W001 immediate-link communication, there may be minimal to no back-and-forth of transmitting and receiving encryption and decryption keys, device authentication, etc.

[0045] In some examples, communications in accordance with the second communication protocol may be one-way communication. That is, IMD 100 may be configured to receive signals, but may not necessarily transmit signals. IMD 100 may be considered as being in an “always listening” or “always ready” mode for communication (e.g., signals) received in accordance with the second communication protocol. Always listening or always ready may mean that IMD 100 may be able to immediately process information in a signal received in accordance with the second communication protocol. Accordingly, the second communication protocol may be considered as being used for immediate-link communication.

[0046] In some examples, the second communication protocol may be standard nonconforming. For example, the second communication protocol may be a proprietary communication protocol that is specifically designed and used for short-range communication. As one example, the short-range communication may be a very low power H-field communication techniques that run constantly with very low power consumption and limited range in a variety of implantable medical devices.

[0047] Unlike the second communication protocol, the first communication protocol may be used for advertisement-based communication. The advertisement-based communication may be far more complex and standards conforming as compared to the immediate-link, short-range communication. Examples of the advertisement-based communication (e.g., first communication protocol) are the BlueTooth and BLE protocols. Additional examples include Medical Implant Communication System (MICS) band telemetry which may be higher power, greater distance telemetry schemes, but may be proprietary and / or at different points in the frequency spectrum, as compared to BlueTooth or BLE protocols.

[0048] For example, in advertisement-based communication, IMD 100 may broadcast advertisement packets at an advertisement frequency, and programmer 104 that is going to establish a communication link with IMD 100 may use the advertisement packets for establishing the communication link. The advertisement packets may indicate to other devices that IMD 100 is available for establishing a communication link.

[0049] IMD 100 may be configured to communicate using the first communication protocol (e.g., main communication link) or the second communication protocol (e.g., sideband communication link) for various purposes. As one example, if side information or immediate commands are needed to be transmitted to IMD 100, including wake-up commands, etc., communications in accordance with the second communication protocol may be preferred. If therapy -based communication, such as transmission of therapy parameters to IMD 100 orDocket No.: A0012687W001 reception of patient information from IMD 100, is needed, then the first communication protocol may be preferred.

[0050] In some examples, communication device 102 may be configured to transmit wireless signals that causes IMD 100 to perform certain tasks. As one example, communication device 102 may transmit a wireless signal to IMD 100 that causes IMD 100 to broadcast advertisement packets at a higher advertisement frequency than the advertisement frequency at which IMD 100 would otherwise transmit the advertisement packets. For instance, the patient may desire to program or interrogate IMD 100. However, IMD 100 may attempt to maximize the time between advertisement packets inorder to minimize the impact of the power usage by the transceiver circuitry of IMD 100. One impact of extending the time between advertisement packets may increase discovery / connection times, resulting in a poor user experience.

[0051] Communication device 102 may transmit the wireless signal to help reduce connection delays using inductive telemetry (e.g., immediate-link, short-range communication) to “sting” IMD 100 to wake up and advertise faster. As noted above, an issue with using the sting with immediate-link, short-range communication is that communication circuitry for outputting in accordance with immediate-link, short-range communication is not available in commercial smart phones or tablets. Therefore, while leveraging commercial smart phones or tablets as programmer 104 may be beneficial, without the example techniques described in the disclosure, there may be unwanted delay in programmer 104 and IMD 100 establishing a communication link.

[0052] In accordance with one or more examples, communication device 102 may be programmer patch (e.g., sticker / backpack) that can attach to programmer 104. Communication device 102 may be relative thin and configured to be affixed to programmer 104 (e.g., via adhesive or some other way). In this disclosure, communication device 102 is described as being physically coupled externally to programmer 104 (e.g., such as by being affixed to the programmer 104 or a cover of programmer 104). Being physically coupled externally to programmer 104 may mean that communication device 102 travels with programmer 104 as long as communication device 102 is physically coupled externally to programmer 104.

[0053] The application on programmer 104 that the user uses for programming or interrogating IMD 100 may be configured to output an NFC signal (e.g., provide NFC energy) to communication device 102. In response, communication device 102 may output the wake-up sting. Communication device 102 may be relatively thin and may require no batteries due to the energy-harvesting capability of communication device 102 harvesting energy from the NFCDocket No.: A0012687W001 signal. However, as described in more detail, in some examples, communication device 102 may include batteries.

[0054] That is, programmer 104 may already be configured to communicate using NFC, but may not support the immediate-link, short-range communication protocol. Therefore, for programmer 104 to “sting” IMD 100 (e.g., wake-up, advertise more frequently, reset, etc.), programmer 104 may output the NFC signal (e.g., a first wireless signal) to communication device 102. The receiving of the NFC signal (e.g., the first wireless signal) may trigger communication device 102 to output the sting (e.g., a second wireless signal) to IMD 100 using the immediate-link, short-range communication protocol. For example, communication device 102 may include a first antenna to receive a first wireless signal (e.g., NFC signal) from programmer 104, and may include a second antenna for outputting a second wireless signal (e.g., sting) to IMD 100.

[0055] FIG. 2 is a conceptual diagram illustrating an example of a communication device affixed to a programmer. For example, FIG. 2 illustrates programmer 200, which is an example of programmer 104 of FIG. 1. Communication device 202, which is an example of communication device 102 of FIG. 1, is physically coupled externally to programmer 200. For example, communication device 202 is affixed to a backside of programmer 200 (e.g., side of programmer 200 that does not include a display) or affixed a cover of programmer 200. In the example of FIG. 2, communication device 202 is formed on a first side of a circuit board, and a second side of the circuit board includes adhesive material to affix communication device 202 to the backside of programmer 200 or to the cover of programmer 200.

[0056] Communication device 202 may be formed on a printed circuit board (PCB) having a thickness of approximately 0.4 mm. The length 206 of communication device 202 may be approximately 70 mm. The width 204 of communication device 202 may be approximately 35 mm. However, other sizes are possible, and generally any size that fits on programmer 200 without being too obstructive is possible. The term “approximately” is used to address manufacturing intolerances. In general, communication device 202 may be sized such as to fit behind programmer 200, and small enough to not impact usage of programmer 200.

[0057] FIG. 3 is a block diagram illustrating example components of a communication device. FIG. 3 illustrates communication device 300, which is an example of communication device 102 of FIG. 1 or communication device 202 of FIG. 2. FIG. 3 also illustrates programmer 318, which is an example of programmer 104 of FIG. 1 and programmer 200 of FIG. 2, and medical device 320, which is an example of IMD 100 of FIG. 1.

[0058] In some examples, communication device 300 may be formed on a 4-layer PCB. The top side may include the circuit components. NFC coil 302 may be on two layers of the PCB, andDocket No.: A0012687W001 communication coil 312 may be on two different layers of the PCB. The above is one example, and other configurations are possible as well. In this disclosure, a first side may refer to a side facing away from programmer 318 when communication device is coupled to programmer 318, and a second side may refer to the side that is attached programmer 318.

[0059] In the example of FIG. 3, programmer 318 and medical device 320 may be configured to communicate using a first communication protocol, such BlueTooth™ or BlueTooth™ Low Energy (BLE) communication protocol. For instance, programmer 318 and medical device 320 may establish communication link 326 which is a communication link in accordance with the first communication protocol. However, to establish communication link 326, programmer 318 may cause medical device 320 to advertise more frequently. In some examples, after establishing communication link 326, programmer 318 may attempt to break communication link 326 (e.g., due to a fault). In such cases, programmer 318 may cause communication device 300 to output a sting signal to medical device 320, in accordance with one or more examples. In some examples, programmer 318 may cause communication device 300 to output a sting signal to medical device 320 to wake-up medical device 320.

[0060] Communication device 300 includes a first coil configured to receive a first wireless signal. For example, communication device 300 includes NFC coil 302 configured to receive NFC signal 322. NFC coil 302 may output a voltage and current based on NFC signal 322. In some examples, the amplitude of the voltage and current that NFC coil 302 outputs may be proportional to the amplitude of NFC signal 322.

[0061] Communication device 300 also includes transceiver circuitry 304. Transceiver circuitry 304 may be configured to receive the output from NFC coil 302. In examples where NFC signal 322 also includes information, such as confirmation information, described in more detail, transceiver circuitry 304 may be configured to extract the information from the output of NFC coil 302 for sending to processing circuitry 308. In examples, described in more detail, where communication device 300 is also configured to transmit information to programmer 318 (e.g., using NFC signal 324), transceiver circuitry 304 may be configured to form the information in accordance with NFC signal requirements for NFC coil 302 to output the information to programmer 318 via NFC signal 324.

[0062] Accordingly, in one or more examples, programmer 318 and communication device 300 may be configured to utilize NFC technology. NFC technology enables communication between two devices that are within a few centimeters of each other. NFC operates at a frequency of 13.56 MHz and is based on radio-frequency identification (RFID) technology. Unlike Bluetooth or Wi-Fi, NFC may not require device pairing or complex setup, allowing for quick and seamless connections.Docket No.: A0012687W001

[0063] With NFC, programmer 318 and communication device 300 may exchange small amounts of data simply by being sufficiently proximate to one another. The power of the NFC signal may be approximately 15 to 20 milli-Watts (mW). In one or more examples, although NFC supports communication of data, the example techniques may not utilize the communication capabilities of the NFC signal. Rather, communication device 300 may utilize the power from the NFC signal, and the actual information included in the NFC signal may be immaterial. However, as also described, utilizing NFC techniques for communication device 300 and programmer 318 to communicate with one another may be possible in some examples.

[0064] Energy harvest circuitry 306 may be configured to convert the NFC signal 322 into a first electrical signal. For example, energy harvest circuitry 306 may be configured to convert NFC signal 322 (e.g., a first wireless signal) to a power signal to power components of communication device 300. As an example, energy harvest circuitry 306 may include a rectifier to convert the AC voltage and current output from NFC coil 302 and a linear regulator to generate a constant voltage. In addition, in some examples, energy harvest circuitry 306 may output energy to capacitor bank 314 that includes one or more capacitors. Capacitor bank 314 may store energy for driving communication coil 312, as described in more detail. Capacitor bank 314 is one example, and other components may be used in addition to or instead of capacitor bank 314 such as surface mount, chip lithium-ion batteries.

[0065] Processing circuitry 308 may include one or more processors, such as one or more microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or any other equivalent integrated or discrete logic circuitry, as well as any combinations of such components. Processing circuitry 308 may be configured to control delivery of wireless signal 328 based on the first electrical signal (e.g., the power signal from energy harvest circuitry 306).

[0066] The output from energy harvest circuitry 306 (e.g., the first electrical signal or the power signal) may wake-up processing circuitry 308. In response to waking up, processing circuitry 308 may command transmitter circuitry 310 to generate a second electrical signal. For instance, transmitter circuitry 310 may access capacitor bank 314 and discharge energy stored in capacitor bank 314 in such a way to generate a second electrical signal that conforms to the immediate-link, short-range communication protocol. Communication coil 312 (e.g., a second coil) may then wirelessly transmit wireless signal 328 based on the second electrical signal to medical device 320. Instead of or in addition to capacitor bank 314, transmitter circuitry 310 may access surface mount, chip lithium-ion batteries to discharge in such a way to generate a second electrical signal.Docket No.: A0012687W001

[0067] Accordingly, in one or more examples, the one or more capacitors of capacitor bank 314 or surface mount, chip lithium-ion batteries may be configured to generate an output electrical signal that is converted to the second wireless signal 328. Energy harvest circuitry 306 may charge the one or more capacitors of capacitor bank 314 using the power signal (e.g., the first electrical signal that energy harvest circuitry 306 generated).

[0068] In one or more examples, processing circuitry 308 may be configured to determine whether there is sufficient energy stored in capacitor bank 314 in response to the first electrical signal (e.g., the power signal from energy harvest circuitry 306 that woke up processing circuitry 308). Processing circuitry 308 may control delivery of the second wireless signal based on the determination of whether there is sufficient power. For instance, if there is not sufficient energy (e.g., power) stored in capacitor bank 314, processing circuitry 308 may not command transmitter circuitry 310 to transmit wireless signal 328. If there is sufficient energy (e.g., power) stored in capacitor bank 314, processing circuitry 308 may command transmitter circuitry 310 to transmit wireless signal 328.

[0069] Transmitter circuitry 310 may be preconfigured to output a specialized sting signal (e.g., as wireless signal 328). That is, the form and content of wireless signal 328 may be preprogrammed within transmitter circuitry 310. In some examples, transmitter circuitry 310 may select from a plurality of different sting signal options, and wireless signal 328 may conform the selected sting signal. For example, there may be a first sting signal used to cause medical device 320 to advertise more frequently, a second sting signal used to cause medical device 320 to reset itself or a communication link, a third sting signal used to turn therapy on or off, etc.

[0070] Medical device 320 may be preconfigured to perform the task instructed by wireless signal 328. As one example, if medical device 320 receives any signal in accordance with the immediate-link, short-range communication protocol, regardless of the actual content of wireless signal 328, medical device 320 may be configured to advertise more frequently, reset, or wakeup. In other examples, based on the content of wireless signal 328, medical device 320 may perform different operations.

[0071] In the above description, NFC signal 322 (e.g., first wireless signal) is described as being used only for harvesting energy to power the components of communication device 300. However, the example techniques are not so limited. In some examples, NFC signal 322 may include confirmation information confirming that communication device 300 is to output wireless signal 328 (e.g., second wireless signal). For instance, NFC signal 322 may include a particular header or some other information that processing circuitry 308 can utilize to confirm that the source of NFC signal 322 is programmer 318. In this manner, if programmer 318 is used to generate an NFC signal that is not meant for communication device 300, processing circuitryDocket No.: A0012687W001 308 may not instruct transmitter circuitry 310 to generate the electrical signal that communication coil 312 uses to output wireless signal 328.

[0072] NFC signal 322 may be considered as downstream NFC signal 322. In some examples, there may be benefit of communication device 300 to transmit upstream NFC signal 324 from communication device 300 to programmer 318. For example, in some examples, the energy stored in capacitor bank 314 may be used to periodically power on processing circuitry 308. After powering on, processing circuitry 308 may determine the energy level stored in capacitor bank 314. If the energy level is below a threshold, processing circuitry 308 may output, via transceiver circuitry 304 and NFC coil 302, upstream NFC signal 324 to programmer 318 requesting that programmer 318 output downstream NFC signal 322 for recharging capacitor bank 314. Upstream NFC signal 324 may be considered as a third wireless signal using a third communication protocol (e.g., NFC communication techniques). The third wireless signal (e.g., upstream NFC signal 324) may include status information of communication device 300. One example of the status information of communication device 300 is the energy level of capacitor bank 314, but other examples of status information exist, and the techniques should not be considered limited to energy level of capacitor bank 314 being the only status information.

[0073] In some examples, communication device 300 may include battery 316 (e.g., rechargeable or non-rechargeable battery). In examples where communication device 300 includes battery 316, energy harvest circuitry 306 may not be necessary. In such examples, the receiving of NFC signal 322 (e.g., first wireless signal) may cause communication device 300 to output wireless signal 328 (e.g., second wireless signal). Battery 316 may be configured to provide power to components of communication device 300.

[0074] In examples where communication device 300 includes battery 316, capacitor bank 314 may not be necessary, and transmitter circuitry 310 and communication coil 312 may utilize energy from battery 316 to transmit wireless signal 328. However, in some examples, battery 316 may not be able to source current at a sufficiently high rate to generate wireless signal 328. In such examples, communication device 300 may still include capacitor bank 314 for delivering the energy to generate wireless signal 328. Battery 316 may periodically output power to capacitor bank 314 so that the one or more capacitors of capacitor bank 314 have enough energy to transmit wireless signal 328 (e.g., the sting signal) when needed.

[0075] The example communication device 300 of FIG. 3 is provided as one example and should not be considered limiting. Communication device 300 may include more or fewer components. For instance, if communication capabilities between communication device 300 and programmer 318 are not needed, then transceiver circuitry 304 may not be needed. IfDocket No.: A0012687W001 communication device 300 is fully powered using NFC signal 322, then battery 316 may not be needed.

[0076] Moreover, various circuitry illustrated in FIG. 3 may be combined together to form a single integrated circuit. For example, one or more of transceiver circuitry 304, energy harvest circuitry 306, and processing circuitry 308 may be combined together to form a single integrated circuit to which transmitter circuitry 310 is coupled. In some examples, transmitter circuitry 310 may also be combined with one or more of transceiver circuitry 304, energy harvest circuitry 306, and processing circuitry 308.

[0077] FIG. 4 is a block diagram illustrating an example configuration of components of external programmer of FIG. 1. FIG. 4 illustrates programmer 400, which is an example of programmer 104 of FIG. 1, programmer 200 of FIG. 2, or programmer 318 of FIG. 3.Programmer 400 may be a commercial smart phone or tablet. As illustrated in FIG. 4, programmer 400 may include processing circuitry 402, storage device 404, user interface 406, telemetry circuitry 408, and power source 410. Storage device 404 may store instructions that, when executed by processing circuitry 402, cause processing circuitry 402 and programmer 400 to provide the functionality ascribed to programmer 400 throughout this disclosure. Each of these components, circuitry, or modules, may include electrical circuitry that is configured to perform some, or all of the functionality described herein.

[0078] In general, programmer 400 includes any suitable arrangement of hardware, alone or in combination with software and / or firmware, to perform the techniques attributed to external programmer 400, and processing circuitry 402, user interface 406, and telemetry circuitry 408 of programmer 400. In various examples, programmer 400 may include one or more processors, such as one or more microprocessors, DSPs, ASICs, FPGAs, or any other equivalent integrated or discrete logic circuitry, as well as any combinations of such components. Programmer 400 also, in various examples, may include a storage device 404, such as random access memory (RAM), read only memory (ROM), programmable read only memory (PROM), erasable programmable read only memory (EPROM), electronically erasable programmable read only memory (EEPROM), flash memory, a hard disk, a CD-ROM, including executable instructions for causing the one or more processors to perform the actions attributed to them.

[0079] Moreover, although processing circuitry 402 and telemetry circuitry 408 are described as separate modules, in some examples, processing circuitry 402 and telemetry circuitry 408 are functionally integrated. In some examples, processing circuitry 402 and telemetry circuitry 408 correspond to individual hardware units, such as ASICs, DSPs, FPGAs, or other hardware units.Docket No.: A0012687W001

[0080] Storage device 404 (e.g., a storage device) may store instructions that, when executed by processing circuitry 402, cause processing circuitry 402 and programmer 400 to provide the functionality ascribed to programmer 400 throughout this disclosure. Storage device 404 may include a plurality of programs, where each program includes a parameter set that defines stimulation pulses, such as control pulses and / or informed pulses. Storage device 404 may also store data received from a medical device.

[0081] User interface 406 may include a button or keypad, lights, a speaker for voice commands, a display, such as a liquid crystal (LCD), light-emitting diode (LED), or organic light-emitting diode (OLED). In some examples the display includes a touch screen. User interface 406 may be configured to display any information related to the delivery of electrical stimulation, identified patient behaviors, sensed patient parameter values, patient behavior criteria, or any other such information. User interface 406 may also receive user input via user interface 406. The input may be, for example, in the form of pressing a button on a keypad or selecting an icon from a touch screen. The input may request starting or stopping electrical stimulation, or request some other change to the delivery of electrical stimulation.

[0082] Telemetry circuitry 408 may support wireless communication between the medical device (e.g., IMD 100 or medical device 320) and programmer 400 under the control of processing circuitry 402. For example, telemetry circuitry 408 may be configured to communicate with a medical device using a first communication protocol (e.g., BlueTooth™ or BlueTooth™ Low Energy (BLE) communication protocol). Telemetry circuitry 408 may also be configured to communicate using NFC communication techniques.

[0083] Telemetry circuitry 408 may also be configured to communicate with another computing device via wireless communication techniques, or direct communication through a wired connection. In some examples, telemetry circuitry 408 provides wireless communication via an RF or proximal inductive medium. In some examples, telemetry circuitry 408 includes an antenna, which may take on a variety of forms, such as an internal or external antenna. Examples of local wireless communication techniques that may be employed to facilitate communication between programmer 400 and the medical device include RF communication according to the 802.11 or BlueTooth™ specification sets or other standard or proprietary telemetry protocols.

[0084] In one or more examples, processing circuitry 402 may execute a programmer application, stored on storage device 404, to allow a user to modify therapy parameters.Processing circuitry 402 may also cause telemetry circuitry to establish a communication link using the first communication protocol. In some examples, to facilitate establishing the communication link, processing circuitry 402 may cause telemetry circuitry 408 to output a first wireless signal (e.g., NFC signal 322), which may cause communication device 300 to output, inDocket No.: A0012687W001 response to receiving the first wireless signal, a second wireless signal (e.g., wireless signal 328) to the medical device using a second communication protocol (e.g., immediate-link, short-range communication protocol) that is different than the first communication protocol.

[0085] In some examples, processing circuitry 402 may be configured to periodically, on request, or responsive to user action, transmit wireless signals (e.g., NFC signal 322) to communication device 300 to recharge components of communication device 300 used for outputting the second wireless signal (e.g., wireless signal 328). For instance, processing circuitry 402 may receive a request for power from medical device 320, via upstream NFC signal 324, and in response may cause telemetry circuitry 408 to output NFC signal 322. As another example, every time the user executes the programmer application, processing circuitry 402 may cause telemetry circuitry 408 to output NFC signal 322. As another example, the programmer application may execute in the background of programmer 400, and may be configured to periodically transmit a signal like NFC signal 322 so that communication device 300 can recharge components on communication device 300 (e.g., recharge capacitor bank 314).

[0086] Power source 410 is configured to deliver operating power to the components of external programmer 400. Power source 410 may include a battery and a power generation circuit to produce the operating power. In some examples, the battery is rechargeable to allow extended operation. Recharging may be accomplished by electrically coupling power source 410 to a cradle or plug that is connected to an alternating current (AC) outlet. In addition, recharging may be accomplished through proximal inductive interaction between an external charger and an inductive charging coil within programmer 400. In other examples, traditional batteries (e.g., nickel cadmium or lithium ion batteries) may be used. In addition, programmer 500 may be directly coupled to an alternating current outlet to operate.

[0087] Furthermore, in some examples, a communication device like communication device 300 may couple to programmer 400 (e.g., clinician tablet) similar to how communication device 300 couples to programmer 104 or 200, such as in examples where programmer 400 does not support immediate-link, short-range communication. Similar to communication device 300, the communication device coupled to programmer 400 may include a thin PCB (e.g., 0.4 mm) with an integrated inductive communication coil, similar to communication coil 312, and associated electronics such as an H-bridge for driving the the communication coil. A rechargeable lithium-ion coin battery would provide power and allow for recharging over USB. The communication device coupled to programmer 300 may include a low-power BLE-enabled microcontroller, which could connect via BLE to programmer 400 (e.g., the clinician tablet), and await a command to start a “sting”. In some examples, the communication device coupled toDocket No.: A0012687W001 programmer 400 may include a physical button, and the “sting” could be enabled by the button press.

[0088] As the low-power BLE microcontroller could also be placed in a BLE Central mode, it could detect a successful "wake-up" of the implanted medical device (e.g., medical device 100 or 320) by monitoring the advertising rate. The communication device coupled to programmer 400 could continue to sting the medical device until the medical device started advertising faster, or notify the clinician if the communication device did not detect an increase in advertising rate during a specific time period.

[0089] Similar to communication device 300, as illustrated by communication device 202 of FIG. 2, the total thickness of the communication device coupled to programmer 400 could be on the order of a few millimeters. This way, the communication device may attach via adhesive to the back of programmer 400. There may be other ways in which to attach the communication device to programmer 400.

[0090] FIG. 5 is a block diagram illustrating example components of the medical device of FIG. 1. Medical device 500 is an example of IMD 100 described above in relation to FIG. 1 or medical device 320 described above in relation to FIG. 3. In the example illustrated in FIG. 5, medical device 500 includes coil 501, power source 502, processing circuitry 504, telemetry circuitry 506, temperature sensor 508, one or more sensor(s) 510 (e.g., accelerometer), memory 512, and therapy and sensing circuitry 514 coupled to one or more electrodes 516A-516D. In other examples, medical device 500 may include a greater or a fewer number of components, e.g., in some examples, medical device 500 may not include sensors 510. In general, medical device 500 may comprise any suitable arrangement of hardware, alone or in combination with software and / or firmware, to perform the various techniques described herein attributed to medical device 500 and processing circuitry 504, and any equivalents thereof.

[0091] Processing circuitry 504 may include one or more processors, such as one or more microprocessors, DSPs, ASICs, FPGAs, or any other equivalent integrated or discrete logic circuitry, as well as any combinations of such components. Medical device 500 may include computer readable storage media, such as memory 512, which may be implemented as RAM, ROM, PROM, EPROM, EEPROM, flash memory, comprising executable instructions for causing the processing circuitry 504 to perform the actions attributed to this circuitry. Moreover, although processing circuitry 504, therapy and sensing circuitry 514, recharge circuitry 503, telemetry circuitry 506, and temperature sensor 508 are described as separate circuits, in some examples, some combination of processing circuitry 504, therapy and sensing circuitry 514, recharge circuitry 503, telemetry circuitry 506, and temperature sensor 508 are functionally integrated. In some examples, processing circuitry 504, therapy and sensing circuitry 514,Docket No.: A0012687W001 recharge circuitry 503, telemetry circuitry 506, and temperature sensor 508 correspond to individual hardware units, such as ASICs, DSPs, FPGAs, or other hardware units. In this disclosure, therapy and sensing circuitry 514 may be referred to as therapy circuitry 514, for simplicity, such as in examples where there is no sensing.

[0092] Memory 512 may store therapy programs or other instructions that specify therapy parameter values for the therapy provided by therapy circuitry 514 and medical device 500. In some examples, memory 512 may also store temperature data from temperature sensor 508, instructions for recharging rechargeable power source 502, or any other instructions required to perform tasks attributed to medical device 500. In various examples, memory 512 stores information related to determining the temperature of the housing of medical device 500 and / or exterior surface(s) of the housing of medical device 500 based on temperatures sensed by one or more temperature sensors, such as temperature sensor 508.

[0093] In some examples, memory 512 may store programming settings such as electrical stimulation therapy output magnitude, pulse width, and so on. Memory 512 may store programming instructions that when executed by processing circuitry 504 cause processing circuitry 504 to perform example techniques described in this disclosure.

[0094] Therapy and sensing circuitry 514 may generate and deliver electrical stimulation under the control of processing circuitry 504. In some examples, processing circuitry 504 controls therapy circuitry 514 by accessing memory 512 to selectively access and load at least one of the stimulation programs to therapy circuitry 514. For example, in operation, processing circuitry 504 may access memory 512 to load one of the stimulation programs to therapy circuitry 514. In such examples, relevant stimulation parameters may include a voltage amplitude, a current amplitude, a pulse rate, a pulse width, a duty cycle, or the combination of electrodes 516A, 516B, 516C, and 516D (collectively “electrodes 516”) that therapy circuitry 514 may use to deliver the electrical stimulation signal as well as sense biological signals. In other examples, medical device 500 may have more or fewer electrodes than the four shown in the example of FIG. 5. In some examples electrodes 516 may be part of or attached to a housing of medical device 500, e.g., a leadless electrode. In other examples, one or more of electrodes 516 may be part of a lead implanted in or attached to a patient to sense biological signals and / or deliver electrical stimulation.

[0095] In the example of FIG. 5, medical device 500 also includes components to receive power to recharge rechargeable power source 502 when rechargeable power source 502 has been at least partially depleted. As shown in FIG. 5, medical device 500 includes coil 501 and recharge circuitry 503 coupled to rechargeable power source 502. Recharge circuitry 503 may be configured to charge rechargeable power source 502 with the selected power level determined byDocket No.: A0012687W001 either processing circuitry 504 or an external charging device. Recharge circuitry 503 may include any of a variety of charging and / or control circuitry configured to process or convert current induced in coil 501 into charging current to charge power source 502.

[0096] Coil 501 may include a coil of wire or other device capable of inductive coupling with a primary coil disposed external to medical device 500. Although coil 501 is illustrated as a simple loop of in FIG. 5, coil 501 may include multiple turns of conductive wire. Coil 501 may include a winding of wire configured such that an electrical current can be induced within coil 501 from a magnetic field. The induced electrical current may then be used to recharge rechargeable power source 502.

[0097] Recharge circuitry 503 may include one or more circuits that process, filter, convert and / or transform the electrical signal induced in coil 501 to an electrical signal capable of recharging rechargeable power source 502. For example, in alternating current induction, recharge circuitry 503 may include a half-wave rectifier circuit and / or a full-wave rectifier circuit configured to convert alternating current from the induction to a direct current for rechargeable power source 502. The full-wave rectifier circuit may be more efficient at converting the induced energy for rechargeable power source 502. However, a half-wave rectifier circuit may be used to store energy in rechargeable power source 502 at a slower rate. In some examples, recharge circuitry 503 may include both a full-wave rectifier circuit and a half-wave rectifier circuit such that recharge circuitry 503 may switch between each circuit to control the charging rate of rechargeable power source 502 and temperature of medical device 500.

[0098] Power source 502 may include one or more capacitors, batteries, and / or other energy storage devices. Power source 502 may deliver operating power to the components of medical device 500. In some examples, rechargeable power source 502 may include a power generation circuit to produce the operating power. Power source 502 may be configured to operate through many discharge and recharge cycles. Power source 502 may also be configured to provide operational power to medical device 500 during the recharge process. In some examples, rechargeable power source 502 may be constructed with materials to reduce the amount of heat generated during charging. In other examples, medical device 500 may be constructed of materials and / or using structures that may help dissipate generated heat at rechargeable power source 502, recharge circuitry 503, and / or secondary coil 501 over a larger surface area of the housing of medical device 500.

[0099] Although power source 502, recharge circuitry 503, and coil 501 are shown as contained within the housing of medical device 500, in alternative implementations, at least one of these components may be disposed outside of the housing. For example, in someDocket No.: A0012687W001 implementations, coil 501 may be disposed outside of the housing of medical device 500 to facilitate better coupling between coil 501 and the coil of a charger.

[0100] Processing circuitry 504 may also control the exchange of information with programmer 104 using telemetry circuitry 506. Telemetry circuitry 506 may be configured for wireless communication using radio frequency protocols, such as BlueTooth™, BLE, or similar RF protocols, as well as using inductive communication protocols. That is, telemetry circuitry 506 may be configured to communicate in accordance with the first communication protocol used for advertisement-based communication, which may be BlueTooth or BLE. Telemetry circuitry 506 may be configured to receive signals in accordance with the second communication protocol used for immediate-link, short-range communication, which may be an inductive communication protocol.

[0101] Telemetry circuitry 506 may include one or more antennas configured to communicate with communication device 102 or communication device 300 or programmer 104, programmer 200, or programmer 318, for example. Processing circuitry 404 may transmit operational information and receive therapy programs or therapy parameter adjustments via telemetry circuitry 406. Telemetry circuitry 406 may be configured to control the exchange of information related to sensed and / or determined temperature data, for example temperatures sensed by and / or determined from temperatures sensed using temperature sensor 408.

[0102] In one or more examples, telemetry circuitry 506 may be configured to receive the wireless signal 328 that communication device 300 outputs. In response, medical device 500 may advertise more frequently, reset, wake-up, etc. Telemetry circuitry 506 may then also establish communication link 326 with programmer 318.

[0103] FIG. 6 is a flowchart illustrating an example method of operation. For ease of illustration, reference is made to FIG. 3. Communication device 300 may receive a first wireless signal from programmer 318 that is configured to communicate with medical device 320 using a first communication protocol (600). As one example, the first wireless signal is near field communication (NFC) signal 322. The first communication protocol may be a BlueTooth™ or BlueTooth™ Low Energy (BLE) communication protocol. For example, communication link 326 may be based on the first communication protocol.

[0104] Communication device 300 may be physically coupled externally to the programmer 318. As one example, communication device 300 may be affixed to a backside of programmer 318 (e.g., the side opposite to a side that includes a display) or affixed a cover of programmer 318. Communication device 300 may be formed on a first side of a circuit board, and a second side of the circuit board may include adhesive material to affix communication device 300 to the backside of programmer 318 or to the cover of programmer 318.Docket No.: A0012687W001

[0105] In one or more examples, communication device 300 is configured to convert the first wireless signal to a power signal to power components of the communication device. As one example, communication device 300 includes one or more capacitors of capacitor bank 314 and capacitor bank 314 is configured to generate an output electrical signal that is converted to a second wireless signal (e.g., wireless signal 328) that communication device 300 outputs.Communication device 300 may be configured to charge the one or more capacitors using the power signal.

[0106] For example, communication device 300 includes a first coil (e.g., NFC coil 302) configured to receive the first wireless signal (e.g., NFC signal 322). Energy harvest circuitry 306 may be configured to convert the first wireless signal into a first electrical signal. The first signal may be the power signal in some examples, and may power processing circuitry 308. Processing circuitry 308 may be configured to control delivery of the second wireless signal (e.g., wireless signal 328) based on the first electrical signal. As one example, processing circuitry 308 may determine whether there is sufficient energy stored in the one or more capacitors of capacitor bank 314 in response to the first electrical signal (e.g., the output from energy harvest circuitry 306). Processing circuitry 308 may control delivery of the second wireless signal (e.g., wireless signal 328) based on the determination of whether there is sufficient energy.

[0107] Transmitter circuitry 310 may be configured to generate a second electrical signal based on command from processing circuitry 308. A second coil (e.g., communication coil 312) may be configured to wirelessly transmit the second wireless signal (e.g., wireless signal 328) based on the second electrical signal. For instance, transmitter circuitry 310 may access capacitor bank 314 and discharge energy stored in capacitor bank 314 in such a way to generate a second electrical signal that conforms to the immediate-link, short-range communication protocol. Communication coil 312 (e.g., a second coil) may then wirelessly transmit wireless signal 328 based on the second electrical signal to medical device 320.

[0108] Communication device 300 may output, in response to receiving the first wireless signal, a second wireless signal (e.g., wireless signal 328) to medical device 320 using a second communication protocol that is different than the first communication protocol (602). The second communication protocol may be an immediate-link, short-range communication protocol. The second wireless signal (e.g., wireless signal 328) to medical device 320 may instruct medical device 320 to transmit advertisement packets more frequently than a frequency at which medical device 320 is transmitting the advertisement packets.In some examples, communication device 300 may support one-way or two-way communication. For instance, the first wireless signal (e.g., NFC signal 324) may include confirmationDocket No.: A0012687W001 information confirming that communication device 300 is to output the second wireless signal. As another example, communication device 300 may be configured to output a third wireless signal (e.g., NFC signal 324) using a third communication protocol (e.g., NFC communication techniques). The third wireless signal may include status information of communication device 300, such as amount of energy stored in capacitor bank 314. Moreover, programmer 318 may be configured to periodically, on request, or responsive to user action, transmit wireless signals to communication device 300 to recharge components of communication device 300 (e.g., capacitor bank 314) used for outputting the second wireless signal (e.g., wireless signal 328).

[0109] The following clauses are a non-limiting list of examples in accordance with one or more techniques of this disclosure.

[0110] Example 1 : A system comprising: a programmer configured to communicate with a medical device using a first communication protocol; and a communication device that is physically coupled externally to the programmer and configured to: receive a first wireless signal from the programmer; and output, in response to receiving the first wireless signal, a second wireless signal to the medical device using a second communication protocol that is different than the first communication protocol.

[0111] Example 2. The system of example 1, wherein the communication device is affixed to a backside that is a side opposite to a side of the programmer that includes a display or affixed to a cover of the programmer.

[0112] Example 3. The system of example 2, wherein the communication device is formed on a first side of a circuit board, and wherein a second side of the circuit board comprises adhesive material configured to affix the communication device to the backside of the programmer or to the cover of the programmer.

[0113] Example 4. The system of any of examples 1-3, wherein the first wireless signal is a near field communication (NFC) signal.

[0114] Example 5. The system of any of examples 1-4, wherein the communication device is configured to convert the first wireless signal to a power signal to power components of the communication device.

[0115] Example 6. The system of example 5, wherein the communication device further comprises one or more of capacitors or surface mount, chip lithium-ion batteries configured to generate an output electrical signal that is converted to the second wireless signal, and wherein the communication device is configured to charge the one or more capacitors using the power signal.Docket No.: A0012687W001

[0116] Example 7. The system of any of examples 1-6, wherein the first wireless signal comprises confirmation information confirming that the communication device is to output the second wireless signal.

[0117] Example 8. The system of any of examples 1-7, wherein the communication device is configured to output a third wireless signal using a third communication protocol, the third wireless signal comprising status information of the communication device.

[0118] Example 9. The system of any of examples 1-8, wherein the communication device comprises: a first coil configured to receive the first wireless signal; energy harvest circuitry configured to convert the first wireless signal into a first electrical signal; processing circuitry configured to control delivery of the second wireless signal based on the first electrical signal; transmitter circuitry configured to generate a second electrical signal based on command from the processing circuitry; and a second coil configured to wirelessly transmit the second wireless signal based on the second electrical signal.

[0119] Example 10. The system of example 9, wherein the processing circuitry is configured to be powered from energy from the first electrical signal.

[0120] Example 11. The system of any of examples 9 and 10, wherein the communication device further comprises one or more capacitors configured to store power used for wirelessly transmitting the second wireless signal, and wherein, to control delivery of the second wireless signal based on the first electrical signal, the processing circuitry is configured to: determine whether there is sufficient energy stored in the one or more capacitors in response to the first electrical signal; and control delivery of the second wireless signal based on the determination of whether there is sufficient energy.

[0121] Example 12. The system of any of examples 1-11, wherein the first communication protocol comprises a BlueTooth™ or BlueTooth™ Low Energy (BLE) communication protocol.

[0122] Example 13. The system of any of examples 1-12, wherein the second communication protocol comprises an immediate-link, short-range communication protocol.

[0123] Example 14. The system of any of examples 1-13, wherein the second wireless signal to the medical device instructs the medical device to transmit advertisement packets more frequently than a frequency at which the medical device is transmitting the advertisement packets.

[0124] Example 15. The system of any of examples 1-14, wherein the programmer is configured to periodically, on request, or responsive to user action, transmit wireless signals to the communication device to recharge components of the communication device used for outputting the second wireless signal.Docket No.: A0012687W001

[0125] Example 16. The system of any of examples 1-15, wherein the programmer is a patient programmer or a clinician programmer.

[0126] Example 17. A method for communicating between devices, the method comprising: receiving, with a communication device, a first wireless signal from a programmer that is configured to communicate with a medical device using a first communication protocol, wherein the communication device is physically coupled externally to the programmer; and outputting, in response to receiving the first wireless signal, a second wireless signal to the medical device using a second communication protocol that is different than the first communication protocol.

[0127] Example 18. The method of example 17, wherein the communication device is affixed to a backside that is a side opposite to a side of the programmer that includes a display of the programmer or affixed a cover of the programmer.

[0128] Example 19. The method of example 18, wherein the communication device is formed on a first side of a circuit board, and wherein a second side of the circuit board comprises adhesive material configured to affix the communication device to the backside of the programmer or to the cover of the programmer.

[0129] Example 20. The method of any of examples 17-19, wherein the first wireless signal is a near field communication (NFC) signal.

[0130] Example 21. The method of any of examples 17-20, further comprising converting, with the communication device, the first wireless signal to a power signal to power components of the communication device.

[0131] Example 22. The method of example 21, wherein the communication device further comprises one or more of capacitors or surface mount, chip lithium-ion batteries configured to generate an output electrical signal that is converted to the second wireless signal, the method further comprising charging the one or more capacitors using the power signal.

[0132] Example 23. The method of any of examples 17-22, wherein the first wireless signal comprises confirmation information confirming that the communication device is to output the second wireless signal.

[0133] Example 24. The method of any of examples 17-23, further comprising outputting, with the communication device, a third wireless signal using a third communication protocol, the third wireless signal comprising status information of the communication device.

[0134] Example 25. The method of any of examples 17-24, wherein the first communication protocol comprises a BlueTooth™ or BlueTooth™ Low Energy (BLE) communication protocol.Docket No.: A0012687W001

[0135] Example 26. The method of any of examples 17-25, wherein the second communication protocol comprises an immediate-link, short-range communication protocol.

[0136] Example 27. The method of any of examples 17-26, wherein the second wireless signal to the medical device instructs the medical device to transmit advertisement packets at a higher frequency.

[0137] Example 28. The method of any of examples 17-27, wherein the programmer is a patient programmer or a clinician programmer.

[0138] The techniques described in this disclosure may be implemented, at least in part, in hardware, software, firmware, or any combination thereof. For example, various aspects of the described techniques may be implemented within one or more processors, including one or more microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or any other equivalent integrated or discrete logic circuitry, as well as any combinations of such components. The term “processor” or “processing circuitry” may generally refer to any of the foregoing logic circuitry, alone or in combination with other logic circuitry, or any other equivalent circuitry. A control unit comprising hardware may also perform one or more of the techniques of this disclosure.

[0139] Such hardware, software, and firmware may be implemented within the same device or within separate devices to support the various operations and functions described in this disclosure. In addition, any of the described units, modules or components may be implemented together or separately as discrete but interoperable logic devices. Depiction of different features as modules or units is intended to highlight different functional aspects and does not necessarily imply that such modules or units must be realized by separate hardware or software components. Rather, functionality associated with one or more modules or units may be performed by separate hardware or software components, or integrated within common or separate hardware or software components.

[0140] The techniques described in this disclosure may also be embodied or encoded in a computer-readable medium, such as a computer-readable storage medium, containing instructions. Instructions embedded or encoded in a computer-readable storage medium may cause a programmable processor, or other processor, to perform the method, e.g., when the instructions are executed. Computer readable storage media may include random access memory (RAM), read only memory (ROM), programmable read only memory (PROM), erasable programmable read only memory (EPROM), electronically erasable programmable read only memory (EEPROM), flash memory, a hard disk, a CD-ROM, a floppy disk, a cassette, magnetic media, optical media, or other computer readable media.Docket No.: A0012687W001

[0141] Various examples have been described. These and other examples are within thescope of the following claims.

Claims

Docket No.: A0012687W001 WHAT IS CLAIMED IS:

1. A system comprising:a programmer configured to communicate with a medical device using a first communication protocol; anda communication device that is physically coupled externally to the programmer and configured to:receive a first wireless signal from the programmer; andoutput, in response to receiving the first wireless signal, a second wireless signal to the medical device using a second communication protocol that is different than the first communication protocol.

2. The system of claim 1, wherein the communication device is affixed to a backside that is a side opposite to a side of the programmer that includes a display or affixed to a cover of the programmer.

3. The system of claim 2, wherein the communication device is formed on a first side of a circuit board, and wherein a second side of the circuit board comprises adhesive material configured to affix the communication device to the backside of the programmer or to the cover of the programmer.

4. The system of any of claims 1-3, wherein the first wireless signal is a near field communication (NFC) signal.

5. The system of any of claims 1-4, wherein the communication device is configured to convert the first wireless signal to a power signal to power components of the communication device.

6. The system of claim 5, wherein the communication device further comprises one or more of capacitors or surface mount, chip lithium-ion batteries configured to generate an output electrical signal that is converted to the second wireless signal, and wherein the communication device is configured to charge the one or more capacitors using the power signal.

7. The system of any of claims 1-6, wherein the first wireless signal comprises confirmation information confirming that the communication device is to output the second wireless signal.Docket No.: A0012687W0018. The system of any of claims 1-7, wherein the communication device is configured to output a third wireless signal using a third communication protocol, the third wireless signal comprising status information of the communication device.

9. The system of any of claims 1-8, wherein the communication device comprises:a first coil configured to receive the first wireless signal;energy harvest circuitry configured to convert the first wireless signal into a first electrical signal;processing circuitry configured to control delivery of the second wireless signal based on the first electrical signal;transmitter circuitry configured to generate a second electrical signal based on command from the processing circuitry; anda second coil configured to wirelessly transmit the second wireless signal based on the second electrical signal.

10. The system of claim 9, wherein the processing circuitry is configured to be powered from energy from the first electrical signal.

11. The system of any of claims 9 and 10, wherein the communication device further comprises one or more capacitors configured to store power used for wirelessly transmitting the second wireless signal, and wherein, to control delivery of the second wireless signal based on the first electrical signal, the processing circuitry is configured to:determine whether there is sufficient energy stored in the one or more capacitors in response to the first electrical signal; andcontrol delivery of the second wireless signal based on the determination of whether there is sufficient energy.

12. The system of any of claims 1-11, wherein the first communication protocol comprises a BlueTooth™ or BlueTooth™ Low Energy (BLE) communication protocol, and the second communication protocol comprises an immediate-link, short-range communication protocol.

13. The system of any of claims 1-12, wherein the second wireless signal to the medical device instructs the medical device to transmit advertisement packets more frequently than a frequency at which the medical device is transmitting the advertisement packets.Docket No.: A0012687W00114. The system of any of claims 1-13, wherein the programmer is configured to periodically, on request, or responsive to user action, transmit wireless signals to the communication device to recharge components of the communication device used for outputting the second wireless signal.

15. The system of any of claims 1-14, wherein the programmer is a patient programmer or a clinician programmer.

Images