EP4728763A1

EP4728763A1 - Wireless communication with medical devices

Info

Publication number: EP4728763A1
Application number: EP24740698.6A
Authority: EP
Inventors: Bernard P. Bechara; Brett A. Otteson; Nathan A. Torgerson; Jacob D. Chatterton; Venkat R. GADDAM; Thomas W. WOLF; Vincent A. ROCZNIAK; Katherine J. Bach; Touby A. Drew; Christopher M. Arnett
Original assignee: Medtronic Inc
Current assignee: Medtronic Inc
Priority date: 2023-06-16
Filing date: 2024-06-14
Publication date: 2026-04-22
Also published as: WO2024259194A1; CN121359480A

Abstract

A medical device includes telemetry circuitry configured to communicate in accordance with a communication protocol that includes an advertisement mode and a connection mode, and processing circuitry configured to cause the telemetry circuitry to: broadcast first data of the medical device, in the advertisement mode, that is specific for a first device without pairing or bonding, in accordance with the communication protocol, with the first device; and communicate second data of the medical device, in the connection mode, for a second device after pairing or bonding, in accordance with the communication protocol, with the second device, the first device and the second device being different devices.

Description

WIRELESS COMMUNICATION WITH MEDICAL DEVICES

[0001] This application is a PCT application that claims priority to, and the benefit of, U.S. Provisional Patent Application No. 63/508,775, filed June 16, 2023, the entire contents of which is incorporated herein by reference.

TECHNICAL FIELD

[0002] This disclosure generally relates to medical device communication.

BACKGROUND

[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. Some medical devices include rechargeable batteries that are recharged from a charger. Also, some medical devices include telemetry circuitry to communicate with other devices, such as the charger or another device.

SUMMARY

[0004] This disclosure describes example techniques for using an advertisement mode of a communication protocol to transfer information from a medical device (e.g., an implantable medical device) to a first device associated with the medical device while allowing the medical device to communicate with a second device in a connection mode of the communication protocol. In this way, the medical device is configured to transmit information that is specific for the first device, but keeping open a communication link for paired or bonded communication with the second device.

[0005] In one example, the disclosure describes a medical device comprising: telemetry circuitry configured to communicate in accordance with a communication protocol that includes an advertisement mode and a connection mode; and processing circuitry configured to cause the telemetry circuitry to: broadcast first data of the medical device, in the advertisement mode, that is specific for a first device without pairing or bonding, in accordance with the communication protocol, with the first device; and communicate second data of the medical device, in the connection mode, for a second device after pairing or bonding, in accordance with the communication protocol, with the second device, the first device and the second device being different devices.

[0006] In one example, this disclosure describes a method for communication comprising: broadcasting, with a medical device, first data of the medical device, in an advertisement mode of a communication protocol, that is specific for a first device without pairing or bonding, in accordance with the communication protocol, with the first device; and communicating, with the medical device, second data of the medical device, in a connection mode of the communication protocol, for a second device after pairing or bonding, in accordance with the communication protocol, with the second device, the first device and the second device being different devices.

[0007] In one example, this disclosure describes a computer-readable storage medium storing instructions thereon that when executed cause one or more processors of a medical device to: broadcast first data of the medical device, in an advertisement mode of a communication protocol, that is specific for a first device without pairing or bonding, in accordance with the communication protocol, with the first device; and communicate second data of the medical device, in a connection mode of the communication protocol, for a second device after pairing or bonding, in accordance with the communication protocol, with the second device, the first device and the second device being different devices.

[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. 1 is a conceptual diagram illustrating an example system including a medical device, a charger, and a programmer according to one or more techniques of this disclosure. [0010] FIG. 2 is a conceptual diagram illustrating example wireless channels for transmitting advertisements and for paired or bonded communication.

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

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

[0014] FIG. 6 is a flowchart illustrating an example method of operation.

[0015] FIG. 7 is a flowchart illustrating another example method of operation.

DETAILED DESCRIPTION

[0016] This disclosure describes example techniques for a medical device configured to transmit first data (e.g., a first set of packets) in an advertising mode to a first device, and communicate second data (e.g., a second set of packets) to a second device in a connection mode. An example of the first device is a charger for the medical device or a monitor (e.g. , bed side monitor), and an example of the second device is a programmer for the medical device. Other examples of the first device and the second device are possible, and the charger, bed side monitor, and programmer are provided merely as examples.

[0017] A medical device may be configured to communicate in accordance with a communication protocol such as the BlueTooth™ protocol or the BlueTooth™ Low Energy (BLE) protocol, including the BLE 5.4 specification. The communication protocol supports an advertising mode and a connection mode. In the advertising 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.

[0018] 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. The pairing process may include the temporary storage of security keys, and once the connection is terminated those keys may not be used again. A new connection may then require a new exchange of security keys. A bonding process includes the long-term storage of security keys. Once the connection is terminated, these keys are maintained and reused for the next connection. Whether the connection mode includes only pairing or only bonding, or some combination, may be based on desired connection mode. This disclosure refers to pairing or bonding to refer to only pairing, only bonding, or pairing and bonding (e.g., such as if some keys are maintained and some keys are not used again).

[0019] After pairing or bonding, the medical device and the other device establish a secure link, and communicate over the secure link. During the communication, after pairing or bonding (e.g., over the secure link), the medical device may transmit data and receive data that is specifically addressed to or addressed from the other device.

[0020] Accordingly, in advertising mode of the communication protocol, the transmission from the medical device is broadcasted without pairing or bonding (e.g., without forming a secure link through handshake). In connection mode of the communication protocol, the transmission from the medical device, after pairing or bonding (e.g., forming a secure link through handshake), is addressed to a specific device, unlike advertising mode.

[0021] The advertising mode and the connection mode may not be mutually exclusive. For instance, the communication channels used for advertising mode and the communication channels used for connection mode may be different channels. In some examples, the medical device may be configured to broadcast the first data and communicate the second data simultaneously. In some examples, the medical device may be configured to interleave broadcasting the first data and communicating the second data.

[0022] This disclosure describes example techniques to leverage the advertising mode to broadcast first data without establishing a secure link (e.g., without pairing or bonding) with a first device, while including in the first data information that is specific to the first device, to allow the medical device to connect in connection mode with a second device. As one example, the first device is a charger for the medical device or a monitor, and the second device is a programmer for the medical device.

[0023] In this example, the medical device may broadcast first data, in the advertising mode, specific for the charger that includes information related to recharging the medical device (e.g., current temperature of the medical device, the charge level of the medical device, etc.). Then, the medical device can communicate second data with the programmer, after pairing or bonding, in the connection mode. The second data includes information related to programming the medical device (e.g., therapy parameters, status information, etc.). In one or more examples, the medical device can communicate second data with the programmer, after pairing or bonding, in the connection mode while broadcasting the first data to the charger (e.g., simultaneously or by interleaving).

[0024] It may be possible for the medical device to communicate with the first device (e.g., charger) in the communication mode, instead of leveraging the advertising mode. However, the medical device may then not be able to communicate with the second device (e.g., programmer) in the communication mode. For instance, there may be benefit in limiting the number of devices with which the medical device is allowed to communicate at a time in the communication mode. As an example, if the medical device were able to communicate with multiple devices, there is a possibility that two programmers pair or bond with the medical device. In this case, additional processing overhead may be needed for the medical device to determine which of the two programmers is the actual programmer that is controlling the medical device.

[0025] Therefore, even if possible for the charger and the programmer to communicate using the communication mode with the medical device, to avoid a situation where multiple programmers can establish secure links with the medical device, in some examples, the medical device may be limited to establishing only one secure link, at a time, through pairing or bonding (e.g., allowed to only pair or bond to one device at a time). It should be noted that the above example of the medical device being limited to only establishing one secure link is provided as an example, and should not be considered limiting. The medical device may be able to establish multiple secure links in the connection mode, and perform the example techniques described in this disclosure.

[0026] As described above, to leverage the advertising mode, the medical device may broadcast information that is specific to the first device, such as information in addition to or instead of information used for pairing or bonding with the medical device. As an example, the first device may be the charger, and the medical device may broadcast the first data, including information related to recharging the medical device such as temperature of the medical device or charge level of the medical device. The charger may then use such information to control delivery of recharge energy to the medical device.

[0027] In advertising mode, the medical device may periodically or intermittently broadcast the first data. Devices, also configured in accordance with the communication protocol (e.g., BlueTooth™ or BLE), may periodically or intermittently enter scanning mode in which devices listen for advertisements. In one or more examples, because there may not be pairing or bonding between the medical device and the first device, the first device may be able to process the first data only when the scanning time and the advertising time overlap. To increase the likelihood that the first device receives the first data, the medical device may be configured to, as compared to normal advertising, increase the frequency at which the medical device broadcasts the first data so that the chances of overlap between when the medical device is broadcasting the first data and when the first device is scanning is increased. In some examples, the first device may be configured in continuous scanning mode to ensure that the first data is received.

[0028] Moreover, in one or more examples, the first device may provide information back to the medical device. For instance, assume that the first device is a charger. After the charger completes charging, the charger may be configured to provide information to the medical device about charging (e.g., length of time, starting and finishing charge level, etc.). However, because the first device and medical device are not communicating after pairing or bonding, the first device may similarly use the advertising mode of the first device to broadcast back to the medical device the information about charging. During the scanning time of the medical device, the medical device may receive the information from the first device. The BLE 5.4 specification also supports two-way communication without establishing a secure link through pairing or bonding, and the medical device and the first device may be configured to use the two-way communication without establishing a secure link through pairing or bonding, as provided by the BLE 5.4 specification.

[0029] The first data that the medical device broadcasts may be processable by any other device that is also configured in accordance with the communication protocol. In some examples, the medical device and the first device may be configured with keys that the medical device and the first device use to encrypt the first data. As one example, the second device (e.g., programmer) may provide the keys to both the medical device and the first device. As another example, the medical device and the first device may be pre-configured with keys. As another example, the medical device and the first device may be configured to communicate using additional communication protocols (e.g., other than BlueTooth™ or BLE). In such examples, the first device may transmit the key using the additional communication protocol, and the medical device may receive the key using the additional communication protocol. Other ways in which to encrypt the first data are possible, and the above examples should not be considered limiting.

[0030] While the medical device is broadcasting the first data to the first device, the medical device may also broadcast advertising packets (e.g., unique identifier for the medical device) used for pairing or bonding with the medical device. In some examples, the medical device may include the advertising packets along with the first data so that the first device can receive the first data, and the second device can receive the advertising packets for pairing or bonding. As another example, the medical device may interleave the first data and the advertising packet. For instance, in a first advertising session, the medical device may broadcast the first data, in a second advertising session, the medical device may broadcast the advertising packets, and so forth.

[0031] FIG. 1 is a conceptual diagram illustrating an example system including a medical device, a charger, and a programmer according to one or more techniques of this disclosure. The example of FIG. 1 includes an implantable medical device (IMD) 100, charger 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.

[0032] Charger 102 includes one or more antennas to recharge an electrical energy storage device of IMD 100, such as a battery. 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. [0033] 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.

[0034] 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).

[0035] 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. [0036] 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.

[0037] 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.

[0038] In some examples, the techniques described in this disclosure are directed to delivery of 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.

[0039] 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.

[0040] Charger 102 may be used to recharge the rechargeable power source within IMD 100 implanted in the patient. Charger 102 may be a hand-held device, a portable device, or a stationary charging system Charger 102 may include components necessary to charge IMD 10 through tissue of the patient. External computing device 110 may include a power transmitting antenna such as an internal energy transfer coil and external energy transfer coil. In other examples, charger 102 may only include an internal primary coil and omit the use of external primary coil, or only include external primary coil and omit the use of internal primary coil.

[0041] IMD 100 may receive energy from charger 102. A charging circuit within IMD 100 may condition and/or transform the energy (e.g., rectify the energy). The charging circuit may then convey electrical energy to charge the rechargeable power source of IMD 100 when the power source is fully depleted or only partially depleted.

[0042] Charger 102 may include a housing to enclose operational components such as a processor, memory, user interface (optional), telemetry circuitry, power source, and charging circuit configured to transmit energy to IMD 100. Although a user may control the recharging process with a user interface of charger 102, charger 102 may alternatively be controlled by another device, e.g., an external programmer, a tablet computer, laptop or other similar computing device.

[0043] 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 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.

[0044] In one or more examples, IMD 100 and charger 102 may be configured to communicate with one another, and IMD 100 and programmer 104 may be configured to communicate with one another. For example, charger 102 may control the amount of energy delivered based on information received from IMD 100 such as temperature of IMD 100 and/or charge level of IMD 100. That is, when charger 102 is charging IMD 100, a wireless connection is established to exchange periodic recharge information such as battery status and temperature of IMD 100. This information is used to adjust and control the recharge energy, in a method known as Closed Loop Recharge. As another example, after a charging session, charger 102 may output information to IMD 100 related to charging that indicates length of time of charging, starting charge level, finished charge level, etc. As descried above, IMD 100 and programmer 104 may communicate with one another for programming purposes (e.g., from programmer 104 to IMD 100) or for transmitting information determined by IMD 100 (e.g., from IMD 100 to programmer 104).

[0045] One way for IMD 100 and charger 102 or IMD 100 and programmer 104 to communicate with one another is in accordance with a communication protocol, such as BlueTooth™ or BLE. For instance, IMD 100, charger 102, and programmer 104 may each have telemetry circuitry configured to communicate in accordance with the communication protocol. The communication protocol includes an advertisement mode and a connection mode.

[0046] In an advertisement mode, IMD 100 broadcasts the presence of IMD 100 by periodically transmitting small packets of data, referred to as advertising packets. The advertising packets includes information as the address of IMD 100, supported services, device name, and other relevant data. Charger 102 and programmer 104, which is enabled to communicate in accordance with the communication protocol, may be in a scanning mode to listen to advertising packets and learn about the presence of IMD 100.

[0047] In a communication mode, IMD 100 and charger 102 or IMD 100 and programmer 104 establish a connection (e.g., secure connection) for data exchange. For instance, IMD 100 and charger 102 or IMD 100 and programmer 104 may engage in a handshake process to establish the connection, known as the pairing or bonding process.

Once the pairing or bonding process is completed, IMD 100 and charger 102 or IMD 100 and programmer 104 create a secure link and can communicate with each other.

[0048] As described above, the pairing process may include the temporary storage of security keys, once the connection is terminated those keys may not be used again. A new connection may then require a new exchange of security keys. Bonding process is long term storage of security keys. Once the connection is terminated, these keys are maintained and reused for the next connection. Whether the connection mode includes only pairing or only bonding, or some combination may be based on desired system This disclosure refers to pairing or bonding to refer to only pairing, only bonding, or pairing and bonding (e.g., such as if some keys are maintained and some keys are not used again).

[0049] However, there may be certain issues if IMD 100 establishes a secure link through the connection mode with charger 102. For instance, in some examples, if IMD 100 establishes a secure link in connection mode with charger 102, then IMD 100 may not be able to establish a secure link with programmer 104 because the number of connections that IMD 100 can make in connection mode, at a time, may be limited. Also, charger 102 may be limited in the number of connections charger 102 can make, and therefore, may not function well as a passthrough device to allow programmer 104 and IMD 100 to communicate.

[0050] Therefore, during the Closed Loop Recharge session, a user may not be able to use programmer 104 to communicate with IMD 100 because the wireless communication of IMD 100 is occupied by charger 102. Accordingly, the user is prevented checking the status of IMD 100 or making any therapy adjustment during the recharge session.

[0051] Similarly, if IMD 100 establishes a secure link with programmer 104, then IMD 100 may not be able to establish a secure link in accordance with the communication protocol with charger 102. In this case, some of the benefits associated with usage of the communication protocol may not be available to IMD 100 and charger 102.

[0052] This disclosure describes example techniques to leverage the usage of the advertisement mode for IMD 100 to broadcast data that is specific to charger 102 without establishing a secure link (e.g., without pairing or bonding), in accordance with the communication protocol, with the charger. The data includes information related to recharging of IMD 100. Leveraging the advertisement mode for broadcasting information may be referred to as connectionless-connection. Although the example is described with charger 102, the examples are not so limited. For instance, IMD 100 may broadcast data that is specific to a first device, without establishing a secure link (e.g., without pairing or bonding), in accordance with the communication protocol, with the first device. One example of the first device is charger 102, but other examples such as monitor devices are possible. In general, a device that is configured to perform operations in accordance with the communication protocol may be considered as a first device.

[0053] In some examples, IMD 100 may be configured to broadcast data that is specific to the first device (e.g., charger 102) in response to satisfying a condition. As an example, IMD 100 may be configured to detect with recharge energy is being delivered from charger 102. In response to the detecting that recharge energy is being delivered from charger 102, IMD 100 may broadcast data that is specific to charger 102 without establishing a secure link (e.g., without pairing or bonding), in accordance with the communication protocol, with charger 102. The reception of recharge energy is one example that may cause IMD 100 to broadcast data specific to a first device. However, the techniques are not so limited, and IMD 100 may broadcast data specific to the first device in response to a different condition being satisfied or broadcast data specific to the first device without a requirement that a condition be satisfied. [0054] There may not be a guarantee that data transmitted in the advertising mode is actually received by the intended device. For example, if charger 102 is not in scanning mode, then charger 102 may not receive the information from the advertisement mode. Accordingly, in one or more examples, IMD 100 may speed up the advertisement to ensure low latency of the communication. That is, IMD 100 may increase the frequency at which IMD 100 broadcasts the data that is specific to charger 102 (e.g., advertise more often), which increases the likelihood that the scanning mode of charger 102 overlaps with when IMD 100 is advertising. In some examples, charger 102 may be configured to be in a continuous scanning mode to ensure that charger 102 senses the advertisement. That is, charger 102 may detect these advertisements and acquire the data that charger 102 needs to adjust the recharge energy.

[0055] In addition, with the newly released BLE 5.4 specification, charger 102 can respond to these advertisements and request more data if needed. This is a new BLE feature that allows a 2-way communication without establishing a BLE connection (e.g., without establishing a secure connection).

[0056] In some examples, charger 102 may provide information back to IMD 100. After a charging session, charger 102 may be configured to provide information to IMD 100 about charging (e.g., length of time, starting and finishing charge level, etc.). However, because charger 102 and IMD 100 are not communicating after pairing or bonding, charger 102 may similarly use the advertising mode to broadcast back to IMD 100 the information about charging. During the scanning time of IMD 100 (e.g., IMD 100 is using the same channels as used in advertisement mode for scanning), IMD 100 may receive the information from charger 102. The BLE 5.4 specification also supports two-way communication without establishing a secure link through pairing or bonding, and IMD 100 and charger 102 may be configured to use the two-way communication without establishing a secure link through pairing or bonding, as provided by the BLE 5.4 specification. For example, the two-way communication without establishing the secure link may be considered as Periodic Advertising with Response.

[0057] As an example, IMD 100 may be configured to scan for data on advertisement channels assigned to the advertisement mode that is broadcasted from the first device (e.g., charger 102) in the advertisement mode of the first device. IMD 100 may receive data that is broadcasted from the first device (e.g., charger 102). In some examples, the data that IMD 100 receives may be part of the two-way communication (e.g., Periodic Advertising with Response). In some examples, the data that IMD 100 receives may be based on periodically configuring IMD 100 in an advertisement mode, where the first device periodically broadcasts the data that is specific to IMD 100.

[0058] With IMD 100 and charger 102 communicating using advertising mode, the connection mode to establish a secure connection after pairing or bonding, in accordance with the communication protocol, is available. Accordingly, IMD 100 and programmer 104 may establish a secure link after pairing or bonding for communication. Although the example is described with programmer 104 communicating over a secure link, the examples are not so limited. For instance, IMD 100 may communicate data with a second device, after pairing or bonding, in accordance with the communication protocol, with the second device. One example of the second device is the programmer 104, but other examples are possible. In general, similar to the first device, a device that is configured to perform operations in accordance with the communication protocol may be considered as a second device.

[0059] As described above, the advertising mode and the connection mode may not be mutually exclusive. For instance, the communication channels used for advertising mode, and the communication channels used for connection mode may be different channels. In some examples, IMD 100 may be configured to broadcast the first data that is specific for a first device (e.g., charger 102) and communicate the second data with a second device (e.g., programmer 104) simultaneously. In some examples, IMD 100 may be configured to interleave broadcasting the first data and communicating the second data.

[0060] This disclosure describes examples of IMD 100 broadcasting first data to charger 102 while communicating with programmer 104 using the connection mode. Such disclosure includes examples where IMD 100 broadcasts and communicates over the secure link at the same time, or examples where IMD 100 broadcasts and communicates over the secure link in an interleaving manner. In general, IMD 100 broadcasting first data to charger 102 while communicating with programmer 104 means that during a recharge session, IMD 100 broadcasted first data to charger 102 without pairing or bonding and communicated second data over a secure link after pairing or bonding with programmer 104.

[0061] The first data that IMD 100 broadcasts may be processable by any other device that is also configured in accordance with the communication protocol. In some examples, IMD 100 and charger 102 may be configured with keys that IMD 100 and charger 102 use to encrypt the first data. As one example, programmer 104 may provide the keys to both IMD 100 and charger 102. As another example, IMD 100 and charger 102 may be pre-configured with keys. As another example, IMD 100 and charger 102 may be configured to communicate using additional communication protocols (e.g., other than BlueTooth™ or BLE). In such examples, charger 102 may transmit the key using the additional communication protocol, and IMD 100 may receive the key using the additional communication protocol. Other ways in which to encrypt the first data are possible, and the above examples should not be considered limiting.

[0062] As described above, by broadcasting first data that is specific to charger 102 in advertising mode, IMD 100 is available to establish a connection with programmer 104. However, to establish the connection with programmer 104 (e.g., establish the secure link), IMD 100 and programmer 104 may need to perform pairing or bonding through handshaking. To perform the handshaking, IMD 100 may need to advertise information used for pairing or bonding so that IMD 100 and programmer 104 can establish the secure link. However, as described above, advertising mode is being utilized by IMD 100 for broadcasting the first data that is specific to charger 102.

[0063] That is, while IMD 100 is broadcasting the first data to a first device (e.g., charger 102), IMD 100 may also broadcast advertising packets (e.g., unique identifier for IMD 100) used by a second device (e.g., programmer 104) for pairing or bonding with IMD 100. In some examples, IMD 100 may include the advertising packets along with the first data so that the first device (e.g., charger 102) can receive the first data, and the second device (e.g., programmer 104) can receive the advertising packets for pairing or bonding. As another example, IMD 100 may interleave the first data and the advertising packet. For instance, in a first advertising session, IMD 100 may broadcast the first data, in a second advertising session, IMD 100 may broadcast the advertising packets, and so forth.

[0064] In this way, IMD 100 includes telemetry circuitry configured to communicate in accordance with a communication protocol that includes an advertisement mode and a connection mode. The communication protocol is the BlueTooth™ Low Energy (BLE) protocol.

[0065] IMD 100 also includes processing circuitry configured to cause the telemetry circuitry to broadcast first data of IMD 100, in the advertisement mode, that is specific for a first device (e.g., charger 102 or other device) without pairing or bonding, in accordance with the communication protocol, with the first device. As one example, the first data includes information related to recharging of IMD 100. For example, the first data includes one or more of temperature of IMD 100 and charge level of IMD 100.

[0066] The processing circuitry may also cause the telemetry circuitry to communicate second data of IMD 100, in the connection mode, for a second device (e.g., programmer 104 or other device) after pairing or bonding, in accordance with the communication protocol, with the second device. The first device and the second device are different devices. As one example, the second data includes information related to programming of IMD 100. For instance, the second data include therapy parameters.

[0067] In some examples, the processing circuitry may cause the telemetry circuitry to broadcast the first data and communicate the second data simultaneously. In some examples, the processing circuity may cause the telemetry circuitry to interleave broadcasting the first data and communicating the second data. That is, the processing circuitry may cause the telemetry circuitry to broadcast the first data while communicating the second data, and communicate the second data while broadcasting the first data. The processing circuity may be configured to limit a number of devices with which IMD 100 is allowed to pair or bond at a time in accordance with the communication protocol to one, but the example techniques are not so limited.

[0068] As described, IMD 100 may be configured to broadcast in advertising mode first data specific for the first device (e.g., charger 102), but may also broadcast information that the second device (e.g., programmer 104) may use for pairing or bonding. As one example, the first data is broadcast as part of a first packet, and, before pairing or bonding with the second device, the processing circuitry is configured to broadcast a second packet in the advertisement mode indicating that IMD 100 is available for pairing or bonding. For example, the processing circuitry may be configured to cause the telemetry circuitry to interleave the broadcast of the first packet and the second packet in the advertisement mode. In some examples, the processing circuitry is configured to receive a request to pair or bonding with the second device in response to the broadcast of the second packet, and establish the pairing or bonding with the second device in response to the request. A request to pair or bond, or to establish the pairing or bonding may be considered as receiving a request to establish a secure connection (e.g., link), and establishing the secure connection (e.g., link).

[0069] In one or more examples, IMD 100 may be configured to broadcast the first data specific for the first device and communicate second data with the second device simultaneously or in an interleaving manner. For example, the communication protocol defines a plurality of communication channels. The processing circuitry may be configured to cause the telemetry circuitry to broadcast the first data of IMD 100 via a first subset of the plurality of channels reserved for advertising, and communicate the second data of IMD 100 via a second subset of the plurality of channels reserved for paired or bonded communication (e.g., secure communication). [0070] IMD 100 may broadcast the first data, and there is a possibility that another device receives the first data. In some examples, the communication protocol may be a first communication protocol. For encryption, the telemetry circuitry of IMD 100 may receive data from the first device (e.g., charger 102) in accordance with a second, different communication protocol. The data may include key information. The processing circuitry is configured to cause the telemetry circuitry to broadcast the first data based on the key information. One example of the second, different communication protocol is data that is communicated using inductive telemetry.

[0071] Also, in some examples, the first device may need to output information for IMD 100. However, because the first device and IMD 100 are communicating via a connectionless-connection, there may not be a secure connection after pairing or bonding between charger 102 and IMD 100. Accordingly, in some examples, the processing circuitry may be configured to cause the telemetry circuitry to scan for data on advertisement channels assigned to the advertisement mode that is broadcasted from the first device (e.g., charger 102) in the advertisement mode of the first device. The telemetry circuitry may receive the data that is broadcasted from the first device. In some examples, it may be possible for the first device to transmit the data for IMD 100 (e.g., after a charging session) using the second, different communication protocol described above. Also, in some examples, IMD 100 and the first device may communicate using the two-way communication in advertisement mode according to BLE 5.4 specification. That is, the first device, in broadcasting the data, may utilize the two-way communication in advertisement mode.

[0072] FIG. 2 is a conceptual diagram illustrating example wireless channels for transmitting advertisements and for paired or bonded communication. In the example of FIG. 2, there are a plurality of channels (e.g., 40 channels) for the communication protocol (e.g., BLE) that range from 2400 MHz to 2480 MHz, labeled as channels 0-40. Channels 37, 38, and 39 may be a first subset of the plurality of channels reserved for advertising, and channels 0-36 may be a second subset of the plurality of channels reserved for paired or bonded communication. That is, the communication protocol operates on different advertising channels in the 2.4 GHz ISM (Industrial, Scientific, and Medical) band. These channels are separate radio frequencies used for transmitting data, where advertisement typically occurs on three channels (37, 38, and 39) to maximize the chances of successful transmission.

[0073] IMD 100 may be considered as an advertising device that broadcasts information in an advertising packet that includes data fields like unique identifier (such as its MAC address), service UUIDs (Universally Unique Identifiers), manufacturer-specific data, or other custom data. IMD 100 may determine an interval at which IMD 100 sends out advertising packets, which defines how frequently IMD 100 broadcasts the advertising packets. A shorter interval may ensure a higher likelihood that another device senses the packets.

[0074] For instance, as described above, IMD 100 may use advertising packets to broadcast first data that is specific for a first device (e.g., charger 102). In some examples, IMD 100 may include the first data with the advertising packet. As another example, there may be different examples of advertising packets. For example, the first data is broadcast as part of a first packet, and, before pairing or bonding with a second device (e.g., programmer 104), the processing circuitry of IMD 100 may be configured to broadcast a second packet in the advertisement mode indicating that IMD 100 is available for pairing or bonding (e.g., the second packet includes the unique identifier). The processing circuitry of IMD 100 may be configured to cause the telemetry circuitry to interleave the broadcast of the first packet and the second packet in the advertisement mode.

[0075] In one or more examples, IMD 100 may detect that charger 102 is delivering charging energy. For instance, charging energy may cause a switch in IMD 100 to close to allow routing of the charging energy to the power source of IMD 100, and the processing circuitry may determine that the switch is closed to detect that charger 102 is delivering charging energy. The processing circuitry may be configured to cause the telemetry circuitry to broadcast the first data in response to detecting that charger 102 is delivering charging energy. The processing circuitry may receive a request to pair or bond with the second device (e.g., programmer 104) in response to the broadcast of the second packet, and establish the pairing or bonding with the second device in response to the request (e.g., receive a request to establish a secure link and establish the secure link). For example, programmer 104 may periodically scan the advertising channels for incoming packets. When an advertising packet (e.g., second packet in above example) is received, programmer 104 can read the data fields contained within the packet. If programmer 104 finds an advertising packet with relevant information (e.g., specific service UUID), programmer 104 can initiate a connection with IMD 100 using a separate process called connection initiation (e.g., handshake).

[0076] FIG. 3 is a block diagram illustrating example components of the medical device of FIG. 1. Medical device 300 is an example of IMD 100 described above in relation to FIG. 1. In the example illustrated in FIG. 3, medical device 300 includes coil 301, power source 302, processing circuitry 304, telemetry circuitry 306, temperature sensor 308, one or more sensor(s) 310 (e.g., accelerometer), memory 312, and therapy and sensing circuitry 314 coupled to one or more electrodes 316A-316D. In other examples, medical device 300 may include a greater or a fewer number of components, e.g., in some examples, medical device 300 may not include sensors 310. In general, medical device 300 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 300 and processing circuitry 304, and any equivalents thereof.

[0077] Processing circuitry 304 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. Medical device 300 may include computer readable storage media, such as memory 312, which may be implemented 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, comprising executable instructions for causing the processing circuitry 304 to perform the actions attributed to this circuitry. Moreover, although processing circuitry 304, therapy and sensing circuitry 314, recharge circuitry 303, telemetry circuitry 306, and temperature sensor 308 are described as separate circuits, in some examples, some combination of processing circuitry 304, therapy and sensing circuitry 314, recharge circuitry 303, telemetry circuitry 306, and temperature sensor 308 are functionally integrated. In some examples, processing circuitry 304, therapy and sensing circuitry 314, recharge circuitry 303, telemetry circuitry 306, and temperature sensor 308 correspond to individual hardware units, such as ASICs, DSPs, FPGAs, or other hardware units. In this disclosure, therapy and sensing circuitry 314 may be referred to as therapy circuitry 314, for simplicity, such as in examples where there is no sensing.

[0078] Memory 312 may store therapy programs or other instructions that specify therapy parameter values for the therapy provided by therapy circuitry 314 and medical device 300. In some examples, memory 312 may also store temperature data from temperature sensor 308, instructions for recharging rechargeable power source 302, thresholds, instructions for communication between medical device 300 and programmer 104 or charger 102, or any other instructions required to perform tasks attributed to medical device 300. In various examples, memory 312 stores information related to determining the temperature of the housing of medical device 300 and/or exterior surface(s) of the housing of medical device 300 based on temperatures sensed by one or more temperature sensors, such as temperature sensor 308.

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

[0080] Therapy and sensing circuitry 314 may generate and deliver electrical stimulation under the control of processing circuitry 304. In some examples, processing circuitry 304 controls therapy circuitry 314 by accessing memory 312 to selectively access and load at least one of the stimulation programs to therapy circuitry 314. For example, in operation, processing circuitry 304 may access memory 312 to load one of the stimulation programs to therapy circuitry 314. 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 316A, 316B, 316C, and 316D (collectively “electrodes 316”) that therapy circuitry 314 may use to deliver the electrical stimulation signal as well as sense biological signals. In other examples, medical device 300 may have more or fewer electrodes than the four shown in the example of FIG. 3. In some examples electrodes 316 may be part of or attached to a housing of medical device 300, e.g., a leadless electrode. In other examples, one or more of electrodes 316 may be part of a lead implanted in or attached to a patient to sense biological signals and/or deliver electrical stimulation.

[0081] In the example of FIG. 3, medical device 300 also includes components to receive power to recharge rechargeable power source 302 when rechargeable power source 302 has been at least partially depleted. As shown in FIG. 3, medical device 300 includes coil 301 and recharge circuitry 303 coupled to rechargeable power source 302. Recharge circuitry 303 may be configured to charge rechargeable power source 302 with the selected power level determined by either processing circuitry 304 or an external charging device, such as charger 102 described above in relation to FIG 1. Recharge circuitry 303 may include any of a variety of charging and/or control circuitry configured to process or convert current induced in coil 301 into charging current to charge power source 302.

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

[0083] Recharge circuitry 303 may include one or more circuits that process, filter, convert and/or transform the electrical signal induced in coil 301 to an electrical signal capable of recharging rechargeable power source 302. For example, in alternating current induction, recharge circuitry 303 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 302. The full-wave rectifier circuit may be more efficient at converting the induced energy for rechargeable power source 302. However, a half-wave rectifier circuit may be used to store energy in rechargeable power source 302 at a slower rate. In some examples, recharge circuitry 303 may include both a full-wave rectifier circuit and a half-wave rectifier circuit such that recharge circuitry 303 may switch between each circuit to control the charging rate of rechargeable power source 302 and temperature of medical device 300.

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

[0085] Although power source 302, recharge circuitry 303, and coil 301 are shown as contained within the housing of medical device 300, in alternative implementations, at least one of these components may be disposed outside of the housing. For example, in some implementations, coil 301 may be disposed outside of the housing of medical device 300 to facilitate better coupling between coil 301 and the coil of charger 102.

[0086] Processing circuitry 304 may also control the exchange of information with charger 102 and programmer 104 using telemetry circuitry 306. Telemetry circuitry 306 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. Telemetry circuitry 306 may include one or more antennas configured to communicate with charger 102 or programmer 104, for example. Processing circuitry 304 may transmit operational information and receive therapy programs or therapy parameter adjustments via telemetry circuitry 306. Telemetry circuitry 306 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 308.

[0087] In some examples, processing circuitry 30 may transmit additional information to charger 102 related to the operation of rechargeable power source 302. For example, processing circuitry 304 may use telemetry circuitry 306 to transmit indications that rechargeable power source 302 is completely charged, rechargeable power source 302 is fully discharged, the amount of charging current output by recharge circuitry 303 e.g., to power source 302, or any other charge status of rechargeable power source 302. In some examples, processing circuitry 304 may use telemetry circuitry 306 to transmit instructions to charger 102, including instructions regarding further control of the charging session, for example instructions to lower the power level or to terminate the charging session, based on the determined temperature of the housing/extemal surface of medical device 300. Processing circuitry 304 may also cause telemetry circuitry 306 to transmit information to charger 102 that indicates any problems or errors with rechargeable power source 302 that may prevent rechargeable power source 302 from providing operational power to the components of medical device 300.

[0088] In accordance with one or mor examples described in this disclosure, telemetry circuitry 306 may be configured to communicate in accordance with a communication protocol that includes an advertisement mode and a connection mode. Processing circuitry 304 may be configured to cause telemetry circuitry 306 to broadcast first data of medical device 300, in the advertisement mode, that is specific for a first device (e.g., charger 102 or other device) without pairing or bonding, in accordance with the communication protocol, with the first device. In examples where the first device is charger 102, the first data includes information related to recharging of medical device 300, as described above. Processing circuitry 304 may also cause telemetry circuitry 306 to communicate second data of medical device 300, in the connection mode, for a second device (e.g., programmer 104) after pairing or bonding, in accordance with the communication protocol, with the second device. In examples where the second device is programmer 104, the second data includes information related to programming of the medical device, as described above. [0089] For example, assume that the first device is charger 102 and the second device is programmer 104, telemetry circuitry 306 broadcasts the first data as part of a first packet, and, before pairing or bonding with programmer 104, processing circuitry 304 is configured to broadcast a second packet in the advertisement mode indicating that medical device 300 is available for pairing or bonding (e.g., such as the unique identifier of medical device 300). Processing circuitry 306 may be configured to cause telemetry circuitry 306 to interleave the broadcast of the first packet and the second packet in the advertisement mode. Processing circuitry 304 may receive a request to pair or bond with programmer 104 in response to the broadcast of the second packet, and establish the pairing or bonding with programmer 104 in response to the request. In some examples, processing circuitry 304 may limit a number of devices with which medical device 300 is allowed to pair or bond at a time in accordance with the communication protocol to one (e.g., so that only programmer 104 is allowed to program medical device 300).

[0090] FIG. 4 is a block diagram of an example charger of FIG. 1. FIG. 4 illustrates charger 400, which is an example of charger 102. In some examples, charger 400 may be described as a hand-held device, and in other examples, charger 400 may be a larger or a nonportable device. As shown in the example of FIG. 4, charger 400 includes two separate components. Housing 402 encloses components such as a processing circuitry 408, memory 410, user interface 412, telemetry circuitry 414, and power source 418. Charging head 404, also called charging wand 404, may include charging circuitry 420, temperature sensor 422, and coil 406. In some examples, a separate charging head 404 may facilitate positioning of coil 406 over coil 301 of medical device 300.

[0091] The example of a separate housing 402 and charging head 404 is merely one example and should not be considered limiting. In some examples, charger 400 may include housing 402, and charging circuitry 420, temperature sensor 422, and coil 406 may be within housing 402 (e.g., separate charging head 404 is not needed).

[0092] Charger 400 may also include one or more temperature sensors, illustrated as temperature sensor 422, similar to temperature sensor 308 of FIG. 3. As shown in FIG. 4, temperature sensor 422 may be disposed within charging head 404. In other examples, one or more temperature sensors of temperature sensor 422 may be disposed within housing 402. For example, charging head 404 may include one or more temperature sensors positioned and configured to sense the temperature of coil 406 and/or a surface of the housing of charging head 404. In some examples, charger 400 may not include temperature sensor 422. [0093] In general, charger 400 comprises any suitable arrangement of hardware, alone or in combination with software and/or firmware, to perform the techniques ascribed to charger 400, and processing circuitry 408, user interface 412, telemetry circuitry 414, and charging circuitry 420 of charger 400, and/or any equivalents thereof. In various examples, charger 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. Charger 400 also, in various examples, may include a memory 410, such as RAM, ROM, PROM, EPROM, EEPROM, flash memory, a hard disk, a CD-ROM, comprising executable instructions for causing the one or more processors to perform the actions attributed to them. Moreover, although processing circuitry 408, telemetry circuitry 414, charging circuitry 420, and temperature sensor 422 are described as separate modules, in some examples, processing circuitry 408, telemetry circuitry 414, charging circuitry 420, and/or temperature sensor 422 are functionally integrated. In some examples, processing circuitry 408, telemetry circuitry 414, charging circuitry 420, and/or temperature sensor 422 correspond to individual hardware units, such as ASICs, DSPs, FPGAs, or other hardware units.

[0094] Memory 410 may store instructions that, when executed by processing circuitry 408, cause processing circuitry 408 and charger 400 to provide the functionality ascribed to charger 400 throughout this disclosure, and/or any equivalents thereof. For example, memory 410 may include instructions that cause processing circuitry 408 to control the power level used to charge medical device 300 in response to the determined temperatures for the housing/extemal surface(s) of medical device 300, as communicated from medical device 300, or instructions for any other functionality. Memory 410 may include a record of selected power levels, sensed temperatures, determined temperatures, or any other data related to charging rechargeable power source 302, described above in relation to FIG. 3. [0095] User interface 412 may include buttons, a keypad, lights, such as indicator lights, a speaker for voice commands, a display, such as a liquid crystal (LCD), or light-emitting diode (LED). User interface 412, and the capabilities or complexity of user interface 412 may be different in different examples of charger 400, and in some examples, may not be present.

[0096] Charging circuitry 420 may include one or more circuits that generate an electrical signal, and an electrical current, within coil 406. Charging circuitry 420 may generate an alternating current of specified amplitude and frequency in some examples. In other examples, charging circuitry 420 may generate a direct current. In any case, charging circuitry 420 may be capable of generating electrical signals, and subsequent magnetic fields, to transmit various levels of power to medical device 300. In this manner, charging circuitry 420 may be configured to charge rechargeable power source 302 of medical device 300 with the selected power level.

[0097] Power source 418 may deliver operating power to the components of charger 400. Power source 418 may also deliver the operating power to drive coil 406 during the charging process. Power source 418 may include a battery and a power generation circuit to produce the operating power. In some examples, a battery of power source 418 may be rechargeable to allow extended portable operation. In other examples, power source 418 may draw power from a wired voltage source such as a consumer or commercial power outlet.

[0098] Telemetry circuitry 414 supports wireless communication between medical device 300 and charger 400 under the control of processing circuitry 408 or processing circuitry 304. Telemetry circuitry 414 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 414 may be substantially similar to telemetry circuitry 306 of medical device 300 described herein, providing wireless communication via an RF or proximal inductive medium. In some examples, telemetry circuitry 414 may include an antenna, which may take on a variety of forms, such as an internal or external antenna. Although telemetry circuitry 414 and 306 may each include dedicated antennas for communications between these devices, telemetry circuitry 414 and 306 may instead, or additionally, be configured to utilize inductive coupling from coils 301 and 406 to transfer data.

[0099] In one or more examples described in this disclosure, charger 400 may receive data that is specific to charger 400 through a broadcast in advertisement mode. Processing circuitry 408 may be configured to process data received in the broadcast to control operation of charging circuitry 420. That is, processing circuitry 408 may be configured to listen for first packets from medical device 300 that include data that processing circuitry 408 uses to control the rate at which electrical energy is delivered, whether delivery of electrical energy is stopped, etc.

[0100] In one or more examples, to the extent that medical device 300 transmits second packets in the advertisement mode for establishing secure connection (e.g., paired or bonded connection) in connection mode, processing circuitry 408 may be configured to ignore such communications. That is, processing circuitry 408 may avoid establishing a secure (e.g., paired or bonded) link with medical device 300. However, in some examples, processing circuitry 408 may initially setup a secure link based on advertisement mode data with medical device 300. Then, processing circuitry 408 may receive a request to disable the secure link (e.g., such as where medical device 300 is going to establish secure link with programmer 104). In this case, processing circuitry 408 may then listen for data from medical device 300 in advertising mode. In some examples, processing circuitry 408 may cause telemetry circuitry 414 to be in continuous scanning mode to ensure that the advertisement from medical device 300 is received by charger 400.

[0101] In some examples, the communication protocol (e.g., BLE) is a first communication protocol. Telemetry circuitry 414 may be configured to transmit data from charger 400 in accordance with a second, different communication protocol (e.g., inductive telemetry using coil 406 that is received by coil 301). The third data includes key information. The data that is then broadcasted by medical device 300 that is specific for charger 400 may be based on the key information.

[0102] For charger 400 to transmit data back to medical device 300, in some examples, processing circuitry 408 may cause telemetry circuitry 414, in broadcast mode, to transmit information that is specific for medical device 300. In some examples, processing circuitry 408 may cause telemetry circuitry 414 to broadcast information in accordance with two-way communication in advertising mode of BLE 5.4 specification.

[0103] FIG. 5 is a block diagram illustrating an example configuration of components of external programmer of FIG. 1. FIG. 5 illustrates programmer 500, which is an example of programmer 104 of FIG. 1. Although programmer 500 may generally be described as a hand-held device, programmer 500 may be a larger portable device or a more stationary device. As illustrated in FIG. 5, programmer 500 may include processing circuitry 502, storage device 504, user interface 506, telemetry circuitry 508, and power source 510.

Storage device 504 may store instructions that, when executed by processing circuitry 502, cause processing circuitry 502 and programmer 500 to provide the functionality ascribed to programmer 500 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.

[0104] In general, programmer 500 includes any suitable arrangement of hardware, alone or in combination with software and/or firmware, to perform the techniques attributed to external programmer 500, and processing circuitry 502, user interface 506, and telemetry circuitry 508 of programmer 500. In various examples, programmer 500 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 500 also, in various examples, may include a storage device 504, such as RAM, ROM, PROM, EPROM, 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. Moreover, although processing circuitry 502 and telemetry circuitry 508 are described as separate modules, in some examples, processing circuitry 502 and telemetry circuitry 508 are functionally integrated. In some examples, processing circuitry 502 and telemetry circuitry 508 correspond to individual hardware units, such as ASICs, DSPs, FPGAs, or other hardware units.

[0105] Storage device 504 (e.g., a storage device) may store instructions that, when executed by processing circuitry 502, cause processing circuitry 502 and programmer 500 to provide the functionality ascribed to programmer 500 throughout this disclosure. Storage device 504 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 504 may also store data received from a medical device (e.g., medical device 300).

[0106] User interface 506 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 506 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 506 may also receive user input via user interface 506. 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.

[0107] Telemetry circuitry 508 may support wireless communication between the medical device 300 and programmer 500 under the control of processing circuitry 502. Telemetry circuitry 508 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 508 provides wireless communication via an RF or proximal inductive medium In some examples, telemetry circuitry 508 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 500 and medical device 300 include RF communication according to the 802.11 or BlueTooth™ specification sets or other standard or proprietary telemetry protocols.

[0108] In some examples, selection of stimulation parameters for stimulation programs are transmitted to the medical device 300 for delivery to a patient. In other examples, the therapy may include medication, activities, or other instructions that a patient should perform themselves or a caregiver perform for the patient. In some examples, programmer 500 provides visual, audible, and/or tactile notifications that indicate there are new instructions. Programmer 500 requires receiving user input acknowledging that the instructions have been completed in some examples.

[0109] Power source 510 is configured to deliver operating power to the components of external programmer 500. Power source 510 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 510 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 500. 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.

[0110] FIG. 6 is a flowchart illustrating an example method of operation. For ease of illustration, FIG. 6 is described with respect to medical device 300. Processing circuitry 304 may cause telemetry circuitry 306 to broadcast first data of medical device 300, in the advertisement mode, that is specific for a first device without pairing or bonding (e.g., without establishing a secure link), in accordance with the communication protocol, with the first device (600). As one example, the first device is charger 400 of medical device 300. The first data includes information related to recharging of the medical device 300. For example, the first data includes one or more of temperature of medical device 300 and charge level of medical device 300. In one or more examples, processing circuitry 304 may cause telemetry circuitry 306 to broadcast the first data of medical device 300 via a first subset of the plurality of channels reserved for advertising. As another example, the first device is a bed side monitor, or some other device.

[0111] In some examples, the first data is broadcast as part of a first packet, and before pairing or bonding with programmer 500 (e.g., before establishing a secure link), processing circuitry 304 may be configured to broadcast a second packet in the advertisement mode indicating that medical device 300 is available for pairing or bonding (e.g., is available to establish a secure link). For example, processing circuitry 304 is configured to cause the telemetry circuitry 306 to interleave the broadcast of the first packet and the second packet in the advertisement mode. Processing circuitry 304 may be configured to receive a request to pair or bond with a second device in response to the broadcast of the second packet, and establish the pairing or bonding with the second device in response to the request.

[0112] For instance, processing circuitry 304 may be configured to cause telemetry circuitry 306 to communicate second data of medical device 300, in the connection mode, for a second device after pairing or bonding (e.g., after establishing the secure link), in accordance with the communication protocol, with the second device (602). The second device may be programmer 500 of the medical device 300. The second data may include information related to programming of medical device 300. For example, the second data includes therapy parameters. In some examples, processing circuitry 304 may be configured to cause telemetry circuitry 306 to communicate the second data of medical device 300 via a second subset of the plurality of channels reserved for paired or bonded communication (e.g., reserved for a secure link). In some examples, processing circuitry 304 may be configured to cause telemetry circuitry 306 to broadcast the first data and communicate the second data simultaneously, or cause telemetry circuitry 306 to interleave broadcasting the first data and communicating the second data. That is, processing circuitry 304 may be configured to cause telemetry circuitry 306 to communicate the second data while broadcasting the first data or broadcast the first data while communicating the second data.

[0113] FIG. 7 is a flowchart illustrating another example method of operation. For ease of illustration, FIG. 7 is described with respect to medical device 300, charger 400, and programmer 500.

[0114] For instance, medical device 300 may be in advertising mode advertising for a connection with a device (700). This may be an initial mode for medical device 300. Medical device 300 may sense charging energy from charger 400 (702). For instance, recharge circuitry 303 may indicate to processing circuitry 304 that there is energy on coil 301, as one example way in which medical device 300 may sense charging energy from charger 400.

[0115] In this case, medical device 300 may continue advertising for connection and broadcast charger specific advertising (704). That is, medical device 300 may detect that the charger 400 is delivering charging energy, and cause the telemetry circuitry 306 to broadcast the first data that is specific to charger 400 in response to detecting that the charger 400 is delivering charging energy. For example, the first data is broadcast as part of a first packet, and, before pairing or bonding (e.g., before establishing a secure link) with the programmer 500, the processing circuitry 304 may be configured to broadcast a second packet in the advertisement mode indicating that medical device 300 is available for pairing or bonding (e.g., is available for establishing a secure link).

[0116] Medical device 300 may pair or bond with programmer 500 (706). For instance, medical device 300 may receive a request to pair or bond with the programmer 500 in response to the broadcast of the second packet, and establish the pairing or bonding with the programmer 500 in response to the request. As one example, medical device 300 and programmer 500 may perform a handshake procedure that establishes a secure link between medical device 300 and programmer 500.

[0117] Medical device 300 may communicate with programmer 500 and broadcast charger specific advertising (708). For instance, processing circuitry 304 may be configured to cause the telemetry circuitry 306 to broadcast the first data (e.g., that is specific to charger 400) and communicate the second data (e.g., that is for programmer 500) simultaneously, or cause the telemetry circuitry 306 to interleave broadcasting the first data and communicating the second data. That is, medical device 300 may broadcast the first data while communicating the second data, and vice-versa.

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

[0119] Clause 1: A medical device comprising: telemetry circuitry configured to communicate in accordance with a communication protocol that includes an advertisement mode and a connection mode; and processing circuitry configured to cause the telemetry circuitry to: broadcast first data of the medical device, in the advertisement mode, that is specific for a first device without pairing or bonding, in accordance with the communication protocol, with the first device; and communicate second data of the medical device, in the connection mode, for a second device after pairing or bonding, in accordance with the communication protocol, with the second device, the first device and the second device being different devices.

[0120] Clause 2. The medical device of clause 1, wherein the first device is a charger of the medical device, wherein the first data includes information related to recharging of the medical device, wherein the second device is a programmer of the medical device, and wherein the second data includes information related to programming of the medical device. [0121] Clause 3. The medical device of any of clauses 1 and 2, wherein the processing circuitry is configured to: cause the telemetry circuitry to broadcast the first data and communicate the second data simultaneously, or cause the telemetry circuitry to interleave broadcasting the first data and communicating the second data.

[0122] Clause 4. The medical device of any of clauses 1-3, wherein the first device is a charger of the medical device, wherein the processing circuitry is configured to: detect that the charger is delivering charging energy, wherein to cause the telemetry circuitry broadcast the first data, the processing circuitry is configured to cause the telemetry circuitry to broadcast the first data in response to detecting that the charger is delivering charging energy. [0123] Clause 5. The medical device of any of clauses 1-4, wherein the first data is broadcast as part of a first packet, and wherein, before pairing or bonding with the second device, the processing circuitry is configured to broadcast a second packet in the advertisement mode indicating that the medical device is available for pairing or bonding. [0124] Clause 6. The medical device of clause 5, wherein the processing circuitry is configured to cause the telemetry circuitry to interleave the broadcast of the first packet and the second packet in the advertisement mode.

[0125] Clause 7. The medical device of any of clauses 5 and 6, wherein the processing circuitry is configured to: receive a request to pair or bond with the second device in response to the broadcast of the second packet; and establish the pairing or bonding with the second device in response to the request.

[0126] Clause 8. The medical device of any of clauses 1-7, wherein the processing circuity is configured to limit a number of devices with which the medical device is allowed to pair or bond at a time in accordance with the communication protocol to one.

[0127] Clause 9. The medical device of any of clauses 1-8, wherein the communication protocol defines a plurality of communication channels, wherein the processing circuitry is configured to cause the telemetry circuitry to: broadcast the first data of the medical device via a first subset of the plurality of channels reserved for advertising; and communicate the second data of the medical device via a second subset of the plurality of channels reserved for paired or bonded communication.

[0128] Clause 10. The medical device of any of clauses 1-9, wherein the communication protocol is a first communication protocol, wherein the telemetry circuitry is configured to receive third data from the first device in accordance with a second, different communication protocol, the third data including key information, and wherein the processing circuitry is configured to cause the telemetry circuitry to broadcast the first data based on the key information. [0129] Clause 11. The medical device of any of clauses 1-10, wherein the processing circuitry is configured to: cause the telemetry circuitry to scan for third data on advertisement channels assigned to the advertisement mode that is broadcasted from the first device in the advertisement mode of the first device; and receive the third data that is broadcasted from the first device.

[0130] Clause 12. The medical device of any of clauses 1-11, wherein the first data includes one or more of temperature of the medical device and charge level of the medical device.

[0131] Clause 13. The medical device of any of clauses 1-12, wherein the second data includes therapy parameters.

[0132] Clause 14. The medical device of any of clauses 1-13, wherein the communication protocol is the BlueTooth™ Low Energy (BLE) protocol.

[0133] Clause 15. A method for communication comprising: broadcasting, with a medical device, first data of the medical device, in an advertisement mode of a communication protocol, that is specific for a first device without pairing or bonding, in accordance with the communication protocol, with the first device; and communicating, with the medical device, second data of the medical device, in a connection mode of the communication protocol, for a second device after pairing or bonding, in accordance with the communication protocol, with the second device, the first device and the second device being different devices.

[0134] Clause 16. The method of clause 15, wherein the first device is a charger of the medical device, wherein the first data includes information related to recharging of the medical device, wherein the second device is a programmer of the medical device, and wherein the second data includes information related to programming of the medical device. [0135] Clause 17. The method of any of clauses 15 and 16, wherein broadcasting and communicating comprises: broadcasting the first data and communicating the second data simultaneously, or interleaving the broadcasting of the first data and the communicating of the second data.

[0136] Clause 18. The method any of clauses 15-17, wherein the first device is a charger of the medical device, the method further comprising: detecting that the charger is delivering charging energy, wherein broadcasting the first data comprises broadcasting the first data in response to detecting that the charger is delivering charging energy.

[0137] Clause 19. The method of any of clauses 15-18, wherein the first data is broadcast as part of a first packet, the method further comprising before pairing or bonding with the second device, broadcasting a second packet in the advertisement mode indicating that the medical device is available for pairing or bonding.

[0138] Clause 20. The method of clause 19, further comprising interleaving the broadcast of the first packet and the second packet in the advertisement mode.

[0139] Clause 21. The method of any of clauses 19 and 20, further comprising: receiving a request to pair or bond with the second device in response to the broadcast of the second packet; and establishing the pairing or bonding with the second device in response to the request.

[0140] Clause 22. The method of any of clauses 15-21, wherein a number of devices with which the medical device is allowed to pair or bond at a time in accordance with the communication protocol is limited to one.

[0141] Clause 23. The method of any of clauses 15-22, wherein the communication protocol defines a plurality of communication channels, wherein: broadcasting comprises broadcasting the first data of the medical device via a first subset of the plurality of channels reserved for advertising; and communicating comprises communicating the second data of the medical device via a second subset of the plurality of channels reserved for paired or bonded communication.

[0142] Clause 24. The method of any of clauses 15-23, wherein the communication protocol is a first communication protocol, the method further comprising receiving third data from the first device in accordance with a second, different communication protocol, the third data including key information, wherein broadcasting comprises broadcasting the first data based on the key information.

[0143] Clause 25. The method of any of clauses 15-24, the method further comprising: scanning for third data on advertisement channels assigned to the advertisement mode that is broadcasted from the first device in the advertisement mode of the first device; and receiving the third data that is broadcasted from the first device.

[0144] Clause 26. The method of any of clauses 15-25, wherein the first data includes one or more of temperature of the medical device and charge level of the medical device.

[0145] Clause 27. The method of any of clauses 15-26, wherein the second data includes therapy parameters.

[0146] Clause 28. The method any of clauses 15-27, wherein the communication protocol is the BlueTooth™ Low Energy (BLE) protocol.

[0147] Clause 29. A computer-readable storage medium storing instructions thereon that when executed cause one or more processors of a medical device to: broadcast first data of the medical device, in an advertisement mode of a communication protocol, that is specific for a first device without pairing or bonding, in accordance with the communication protocol, with the first device; and communicate second data of the medical device, in a connection mode of the communication protocol, for a second device after pairing or bonding, in accordance with the communication protocol, with the second device, the first device and the second device being different devices.

[0148] Clause 30. The computer-readable storage medium of clause 29, further comprising instructions that cause the one or more processors to perform the method of any of clauses 15-28.

[0149] Clause 31. A medical device comprising means for performing the method of any of clauses 15-28.

[0150] 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.

[0151] 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.

[0152] 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.

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

Claims

WHAT IS CLAIMED IS:

1. A medical device comprising: telemetry circuitry configured to communicate in accordance with a communication protocol that includes an advertisement mode and a connection mode; and processing circuitry configured to cause the telemetry circuitry to: broadcast first data of the medical device, in the advertisement mode, that is specific for a first device without pairing or bonding, in accordance with the communication protocol, with the first device; and communicate second data of the medical device, in the connection mode, for a second device after pairing or bonding, in accordance with the communication protocol, with the second device, the first device and the second device being different devices.

2. The medical device of claim 1, wherein the first device is a charger of the medical device, wherein the first data includes information related to recharging of the medical device, wherein the second device is a programmer of the medical device, and wherein the second data includes information related to programming of the medical device.

3. The medical device of any of claims 1 and 2, wherein the processing circuitry is configured to: cause the telemetry circuitry to broadcast the first data and communicate the second data simultaneously, or cause the telemetry circuitry to interleave broadcasting the first data and communicating the second data.

4. The medical device of any of claims 1-3, wherein the first device is a charger of the medical device, wherein the processing circuitry is configured to: detect that the charger is delivering charging energy, wherein to cause the telemetry circuitry to broadcast the first data, the processing circuitry is configured to cause the telemetry circuitry to broadcast the first data in response to detecting that the charger is delivering charging energy.

5. The medical device of any of claims 1-4, wherein the first data is broadcast as part of a first packet, and wherein, before pairing or bonding with the second device, the processing circuitry is configured to broadcast a second packet in the advertisement mode indicating that the medical device is available for pairing or bonding.

6. The medical device of claim 5, wherein the processing circuitry is configured to cause the telemetry circuitry to interleave broadcasting of the first packet and the second packet in the advertisement mode.

7. The medical device of any of claims 5 and 6, wherein the processing circuitry is configured to: receive a request to pair or bond with the second device in response to the broadcast of the second packet; and establish the pairing or bonding with the second device in response to the request.

8. The medical device of any of claims 1-7, wherein the processing circuity is configured to limit a number of devices with which the medical device is allowed to pair or bond at a time in accordance with the communication protocol to one.

9. The medical device of any of claims 1-8, wherein the communication protocol defines a plurality of communication channels, wherein the processing circuitry is configured to cause the telemetry circuitry to: broadcast the first data of the medical device via a first subset of the plurality of channels reserved for advertising; and communicate the second data of the medical device via a second subset of the plurality of channels reserved for paired or bonded communication.

10. The medical device of any of claims 1-9, wherein the communication protocol is a first communication protocol, wherein the telemetry circuitry is configured to receive third data from the first device in accordance with a second, different communication protocol, the third data including key information, and wherein the processing circuitry is configured to cause the telemetry circuitry to broadcast the first data based on the key information.

11. The medical device of any of claims 1-10, wherein the processing circuitry is configured to: cause the telemetry circuitry to scan for third data on advertisement channels assigned to the advertisement mode that is broadcasted from the first device in the advertisement mode of the first device; and receive the third data that is broadcasted from the first device.

12. The medical device of any of claims 1-11, wherein the first data includes one or more of temperature of the medical device and charge level of the medical device.

13. The medical device of any of claims 1-12, wherein the second data includes therapy parameters.

14. The medical device of any of claims 1-13, wherein the communication protocol is the BlueTooth™ Low Energy (BLE) protocol.

15. A computer-readable storage medium storing instructions thereon that when executed cause one or more processors of a medical device to perform the operations of any of claims 1-14.