Wireless communication with medical devices

Abstract

A medical device, the medical device comprising: a telemetry circuit configured to communicate according to a communication protocol comprising an announcement mode and a connected mode; and processing circuitry configured to cause the telemetry circuitry to: broadcast first data of the medical device specific to a first device in the announcement mode without pairing or binding with the first device according to the communication protocol; and transmitting second data of the medical device for a second device in the connected mode after pairing or binding with the second device according to the communication protocol, the first device and the second device being different devices.

Description

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

[0002] The present disclosure relates generally to medical device communication. BACKGROUND

[0003] Medical devices can be external or implanted and can be used to sense neural signals (e.g., central and peripheral neural signals) 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, 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 one or more of the peripheral senses by stimulation. Some medical devices include a rechargeable battery that is recharged from a charger. Additionally, some medical devices include telemetry circuitry for communicating with other devices, such as a charger or another device. SUMMARY

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

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

[0006] In one example, the disclosure describes a method for communication, the method comprising: broadcasting, with a medical device, first data of the medical device that is specific to a first device in an advertising mode of a communication protocol without pairing or binding with the first device according to the communication protocol; and transmitting, with the medical device, second data of the medical device for a second device in a connected mode of the communication protocol after pairing or binding with the second device according to the communication protocol, the first device and the second device being different devices.

[0007] In one example, the disclosure describes a computer-readable storage medium having instructions stored thereon that, when executed, cause one or more processors of a medical device to: broadcast, in an advertising mode of a communication protocol without pairing or binding with a first device according to the communication protocol, first data of the medical device that is specific to the first device; and transmit, in a connected mode of the communication protocol after pairing or binding with a second device according to the communication protocol, second data of the medical device for the second device, the first device and the second device being different devices.

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

[0009] Figure 1 is a conceptual diagram illustrating an example system including a medical device, a charger, and a programmer in accordance with one or more techniques of the disclosure.

[0010] Figure 2 is a conceptual diagram illustrating example wireless channels for advertising transmission and for paired or bound communication.

[0011] Figure 3 is a block diagram of example components of a medical device of Figure 1

[0012] Figure 4 is a block diagram of an example charger of Figure 1

[0013] Figure 5 is a block diagram of an example configuration of components of an external programmer of Figure 1

[0014] Figure 6 is a flow diagram illustrating an example method of operation.

[0015] Figure 7 is a flow diagram 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) to a first device in an advertising mode, and to transmit second data (e.g., a second set of packets) to a second device in a connected mode. An example of the first device is a charger or monitor (e.g., a bedside monitor) for the medical device, and an example of the second device is a programmer for the medical device. Other examples of the first and second devices are possible, and the charger, bedside monitor, and programmer are provided as examples only.

[0017] The medical device can be configured to communicate according to a communication protocol, such as a Bluetooth ™ protocol or a Bluetooth ™ Low Energy (BLE) protocol, including the BLE 5.4 specification. The communication protocol supports an advertising mode and a connected mode. In the advertising mode (also referred to as a broadcast or beacon mode), the medical device broadcasts advertising packets that include relevant information to allow other devices to know of the medical device’s presence and to allow connection to the medical device. The term “broadcast” means that the medical device transmits the packets (e.g., data) without addressing the packets to any particular device.

[0018] In the connected mode, the medical device and another device handshake as part of a pairing process or a bonding process to establish a connection. The pairing process can include temporary storage of security keys, and those keys cannot be reused once the connection is terminated. A new connection can then require a new security key exchange. The bonding process includes long-term storage of security keys. Those keys are maintained and reused for the next connection once the connection is terminated. Whether the connected mode includes pairing only or bonding only or some combination can be based on the desired connection mode. This disclosure refers to pairing or bonding to mean pairing only, bonding only, or both pairing and bonding (e.g., such as if some keys are maintained and some keys are no longer used).

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

[0020] Accordingly, in the advertising mode of the communication protocol, transmissions from the medical device are broadcast without pairing or bonding (e.g., without forming a secure link through handshaking). In the connected mode of the communication protocol, unlike the advertising mode, after pairing or bonding (e.g., forming a secure link through handshaking), transmissions from the medical device are addressed to a particular device.

[0021] The advertising mode and the connected mode can not be mutually exclusive. For example, the communication channel used for the advertising mode and the communication channel used for the connected mode can be different channels. In some examples, the medical device can be configured to broadcast the first data and transmit the second data simultaneously. In some examples, the medical device can be configured to stagger the broadcasting of the first data and the transmitting of the second data.

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

[0023] In this example, the medical device can broadcast first data specific to the charger in the advertising mode, which includes information related to recharging the medical device (e.g., current temperature of the medical device, charge level of the medical device, etc.). Then, after pairing or binding, the medical device can transmit second data with the programmer in the connected mode. The second data includes information related to programming the medical device (e.g., therapy parameters, status information, etc.). In one or more examples, after pairing or binding, the medical device can transmit the second data with the programmer in the connected mode while broadcasting the first data to the charger (e.g., simultaneously or through staggering).

[0024] The medical device can be able to communicate with the first device (e.g., the charger) in a communication mode, rather than utilizing the advertising mode. However, the medical device can not be able to communicate with the second device (e.g., the programmer) in the communication mode. For example, it can be beneficial to limit the number of devices that are allowed to communicate with the medical device at a time in the communication mode. For example, if the medical device is able to communicate with multiple devices, there is a possibility that two programmers pair or bind with the medical device. In this case, the medical device can require additional processing overhead to determine which of the two programmers is the actual programmer that is controlling the medical device.

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

[0026] As described above, in order to utilize the notification mode, the medical device can broadcast device-specific information, such as information other than, or in lieu of, the information used for pairing or binding with the medical device. For example, the first device could be a charger, and the medical device could broadcast first data including information related to recharging the medical device, such as the temperature of the medical device or its battery level. The charger can then use this information to control the delivery of recharge energy to the medical device.

[0027] In notification mode, the medical device can broadcast initial data periodically or intermittently. This also depends on the communication protocol (e.g., Bluetooth). ™ A device configured with either medical device or BLE (Browser-Loop Electron Device) may periodically or intermittently enter a scanning mode in which it listens for notifications. In one or more examples, because there may be no pairing or binding 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 notification time overlap. To increase the likelihood that the first device will receive the first data, the medical device may be configured to broadcast the first data more frequently than normal notifications, such that the chance of overlap between when the medical device is broadcasting the first data and when the first device is scanning increases. In some examples, the first device may be configured to be in a continuous scanning mode to ensure that the first data is received.

[0028] Further, in one or more examples, the first device can provide information back to the medical device. For example, assume the first device is a charger. After the charger completes charging, the charger can be configured to provide information to the medical device about the charging (e.g., length of time, start and end power levels, etc.). However, because the first device and the medical device are not in communication after pairing or binding, the first device can similarly use the advertising mode of the first device to broadcast information about the charging back to the medical device. During a scan time of the medical device, the medical device can receive the information from the first device. The BLE 5.4 specification also supports bidirectional communication without establishing a secure link through pairing or binding, and the medical device and the first device can be configured to use bidirectional communication without establishing a secure link through pairing or binding, as provided by the BLE 5.4 specification.

[0029] The first data broadcast by the medical device can be able to be processed by any other device that is also configured according to the communication protocol. In some examples, the medical device and the first device can be configured with a key that the medical device and the first device use to encrypt the first data. As one example, a second device (e.g., a programmer) can provide the key to both the medical device and the first device. As another example, the medical device and the first device can be preconfigured with the key. As another example, the medical device and the first device can be configured to communicate using an additional communication protocol (e.g., a protocol other than Bluetooth ™ or BLE). In such examples, the first device can transmit the key using the additional communication protocol, and the medical device can receive the key using the additional communication protocol. Other ways of encrypting 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 can also broadcast an advertising packet for pairing or binding with the medical device (e.g., for a unique identifier of the medical device). In some examples, the medical device can include the advertising packet with the first data, such that the first device can receive the first data and a second device can receive the advertising packet for pairing or binding. As another example, the medical device can interleave the first data and the advertising packet. For example, in a first advertising session, the medical device can broadcast the first data, in a second advertising session, the medical device can broadcast the advertising packet, and so on.

[0031] Figure 1 is a conceptual diagram illustrating an example system including a medical device, a charger, and a programmer, in accordance with one or more techniques of the present disclosure. Figure 1Examples include an implantable medical device (IMD) 100, a charger 102, and a programmer 104. For ease of description, examples are described with respect to an IMD 100, but the technology should not be considered limited to implantable medical devices, and can generally be applicable to medical devices.

[0032] The charger 102 includes one or more antennas for recharging an electrical energy storage device of the IMD 100, such as a battery. The programmer 104 can be configured to program operation of the IMD 100. For example, the programmer 104 can communicate with the IMD 100 to adjust therapy and / or sensing parameters, download recorded data, and the like.

[0033] Figure 1 An example is a side view of a patient's leg 106 showing the IMD 100 proximate to the ankle and adjacent to the tibial nerve 108. The IMD 100 is Figure 1 The IMD 100 can be implanted through the patient's skin and skin fat layer via a small incision (e.g., about one to three centimeters (cm)) over the tibial nerve 108 on the medial aspect of the patient's ankle. While the incision can be generally horizontal to the length of the tibial nerve 108, other incisions or implantation techniques can be used according to physician preference. Figure 1 Examples of the IMD 100 describe a nerve stimulation implantable medical device for tibial nerve stimulation. In other examples, the technology of the present disclosure can be applied to other medical devices, such as wearable or implantable nerve stimulation systems for use in spinal cord stimulation therapy (e.g., pain therapy), deep brain stimulation, pelvic floor muscle stimulation (e.g., sacral nerve stimulation), and to other types of implantable or external medical devices without limitation.

[0034] In examples of the IMD 100, Figure 1 The IMD 100 can be positioned adjacent to a region defined by the flexor digitorum longus and the soleus muscle, in which the tibial nerve 108 is contained and implanted adjacent to and proximate to the fascia layer. One or more electrodes of the IMD 100 can face the tibial nerve 108. Although not shown in Figure 1 The IMD 100 can also be connected to one or more leads including one or more electrodes (not shown in Figure 1

[0035] ​The IMD 100 can be constructed from any polymer, metal, or composite material sufficient to house the components of the IMD 100. In this example, the IMD 100 can be constructed with a biocompatible housing, such as titanium or stainless steel, or a polymeric material, such as silicone or polyurethane, and in some examples implanted at a site near the tibial nerve 108 of a patient through a surgical procedure, while in other examples implanted near the pelvis, abdomen, or hip. The housing of the IMD 100 can be configured to provide a hermetic seal to components, such as a rechargeable power source. Further, the housing of the IMD 100 can be selected from materials that facilitate receiving energy to charge the rechargeable power source.

[0036] In providing therapy, the electrical stimulation signals can be transmitted through the fascia layer between one or more electrodes. The electrical signals can be used to stimulate the tibial nerve 108, which can be used to treat overactive bladder (OAB) symptoms of urinary urgency, urinary frequency, and / or urge urinary incontinence, fecal incontinence, pain, or other symptoms. Figure 1 Examples of the present disclosure can help alleviate some symptoms for some patients.

[0037] One type of therapy for treating bladder dysfunction includes delivering electrical stimulation to a target tissue site in the patient to elicit a therapeutic effect during delivery of the electrical stimulation. For example, delivering electrical stimulation from the IMD 100 to a target therapy site (e.g., a tissue site that delivers stimulation to modulate activity of the tibial nerve, a spinal nerve (e.g., a sacral nerve), a pudendal nerve, a dorsal genital nerve, a hypogastric nerve, a pelvic nerve, or a branch of any of the foregoing nerves) can provide a therapeutic effect for bladder dysfunction, such as a desired reduction in bladder contraction frequency. In some cases, electrical stimulation of the tibial nerve can modulate afferent neural activity to restore voiding function.

[0038] In some examples, the techniques described in the present disclosure involve a non-continuous manner of neurostimulation therapy delivery that can include an on cycle and an off cycle. For example, the IMD 100 can 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., inhibits delivery of neurostimulation). The period during which stimulation is delivered (the on cycle) can include an on period and an off period (e.g., a duty cycle or burst of pulses) with a short inter-pulse duration when no pulses are delivered.

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

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

[0041] IMD 100 can receive energy from charger 102. Charging circuitry within IMD 100 can condition and / or transform the energy (e.g., rectify the energy). The charging circuitry can then deliver electrical energy for charging the rechargeable power source of IMD 100 when the power source is fully depleted or only partially depleted.

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

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

[0044] In one or more examples, IMD 100 and charger 102 can be configured to communicate with each other, and IMD 100 and programmer 104 can be configured to communicate with each other. For example, charger 102 can control the amount of energy delivered based on information received from IMD 100, such as the temperature of IMD 100 and / or the charge level of IMD 100. That is, while charger 102 is charging IMD 100, a wireless connection is established to exchange periodic recharging information, such as the battery status and temperature of IMD 100. In a method referred to as "closed loop recharging," this information is used to adjust and control the recharging energy. As another example, after a charging session, charger 102 can output information related to the charge to IMD 100, indicating the length of the charge time, the starting charge level, the completed charge level, etc. As described above, IMD 100 and programmer 104 can communicate with each other for programming purposes (e.g., from programmer 104 to IMD 100) or to transmit information determined by IMD 100 (e.g., from IMD 100 to programmer 104).

[0045] One way in which IMD 100 and charger 102 or IMD 100 and programmer 104 communicate with each other is according to a communication protocol, such as Bluetooth® or BLE. For example, IMD 100, charger 102, and programmer 104 can each have telemetry circuitry configured to communicate according to the communication protocol. The communication protocol includes an advertising mode and a connected mode. ™

[0046] In the advertising mode, IMD 100 broadcasts the presence of IMD 100 by periodically transmitting small data packets, referred to as advertising packets. The advertising packets include information, such as the address of IMD 100, supported services, device name, and other relevant data. Charger 102 and programmer 104, which are enabled to communicate according to the communication protocol, can be in a scan mode to listen for advertising packets and learn of the presence of IMD 100.

[0047] In the connected mode, IMD 100 and charger 102 or IMD 100 and programmer 104 establish a connection (e.g., a secure connection) for data exchange. For example, IMD 100 and charger 102 or IMD 100 and programmer 104 can go through a handshake process, referred to as a pairing or binding process, to establish the connection. Once the pairing or binding process is complete, 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 can include temporary storage of security keys that cannot be reused once the connection is terminated. New connections can require new security key exchanges. The binding 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 pairing only or binding only or some combination can be based on the desired system. The present disclosure refers to pairing or binding to mean pairing only, binding only, or both pairing and binding (e.g., such as if some keys are maintained and some keys are no longer used).

[0049] However, if the IMD 100 establishes a secure link with the charger 102 through the connection mode, certain problems can exist. For example, in some examples, if the IMD 100 establishes a secure link with the charger 102 in the connection mode, the IMD 100 can not be able to establish a secure link with the programmer 104 because the number of connections the IMD 100 can make at a time in the connection mode can be limited. Additionally, the charger 102 can be limited in the number of connections the charger 102 can make and, thus, can not be well suited to act as a pass-through device that allows the programmer 104 and the IMD 100 to communicate.

[0050] Thus, during a closed-loop recharging session, the user can not be able to communicate with the IMD 100 using the programmer 104 because the wireless communication of the IMD 100 is occupied by the charger 102. Thus, the user is prevented from checking the status of the IMD 100 or making any therapy adjustments during the recharging session.

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

[0052] The present disclosure describes example techniques for broadcasting data specific to a charger 102 using the use of an advertising mode of an IMD 100 without establishing a secure link with the charger 102 according to a communication protocol (e.g., without pairing or binding). The data includes information related to recharging of the IMD 100. Broadcasting the information using the advertising mode can be referred to as a connectionless connection. Although examples are described with a charger 102, examples are not so limited. For example, the IMD 100 can broadcast data specific to a first device without establishing a secure link with the first device according to a communication protocol (e.g., without pairing or binding). One example of a first device is a charger 102, but other examples such as a monitor device are possible. In general, a device configured to perform operations according to a communication protocol can be considered a first device.

[0053] In some examples, the IMD 100 can be configured to broadcast data specific to a first device (e.g., charger 102) in response to a condition being met. For example, the IMD 100 can be configured to detect whether recharging energy is being delivered from the charger 102. In response to detecting that recharging energy is being delivered from the charger 102, the IMD 100 can broadcast data specific to the charger 102 without establishing a secure link with the charger 102 according to a communication protocol (e.g., without pairing or binding). The receipt of recharging energy is one example of a condition that can cause the IMD 100 to broadcast data specific to a first device. However, techniques are not so limited, and the IMD 100 can broadcast data specific to a first device in response to a different condition being met, or without requiring a condition to be met.

[0054] It can not be guaranteed that data transmitted in the advertising mode is actually received by the intended device. For example, if the charger 102 is not in a scan mode, the charger 102 cannot receive the information from the advertising mode. Accordingly, in one or more examples, the IMD 100 can accelerate the advertising to ensure low latency of the communication. That is, the IMD 100 can increase the frequency at which the IMD 100 broadcasts data specific to the charger 102 (e.g., advertise more frequently), which increases the likelihood that a scan mode of the charger 102 overlaps when the IMD 100 is advertising. In some examples, the charger 102 can be configured to be in a continuous scan mode to ensure that the charger 102 senses the advertising. That is, the charger 102 can detect the advertisements and acquire the data needed for the charger 102 to adjust the recharging energy.

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

[0056] In some examples, the charger 102 can provide information back to the IMD 100. After a charging session, the charger 102 can be configured to provide information to the IMD 100 about the charge (e.g., length of time, start and end power levels, etc.). However, because the charger 102 and the IMD 100 are not communicating after pairing or binding, the charger 102 can similarly use an advertising mode to broadcast information about the charge back to the IMD 100. During a scan time of the IMD 100 (e.g., the IMD 100 is using the same channel as used for scanning in advertising mode), the IMD 100 can receive the information from the charger 102. The BLE 5.4 specification also supports 2-way communication without establishing a secure link through pairing or binding, and the IMD 100 and the charger 102 can be configured to use 2-way communication without establishing a secure link through pairing or binding, as provided by the BLE 5.4 specification. For example, the 2-way communication without establishing a secure link can be considered a periodic advertisement with a response.

[0057] For example, the IMD 100 can be configured to scan for data broadcast from a first device (e.g., the charger 102) in an advertising mode of the first device on an advertising channel assigned to the advertising mode. The IMD 100 can receive data broadcast from the first device (e.g., the charger 102). In some examples, the data received by the IMD 100 can be part of a 2-way communication (e.g., a periodic advertisement with a response). In some examples, the data received by the IMD 100 can be based on the IMD 100 being periodically configured in the advertising mode, where the first device periodically broadcasts data specific to the IMD 100.

[0058] In cases where IMD 100 and charger 102 communicate using the advertising mode, a connection mode for establishing a secure connection after pairing or binding according to the communication protocol is available. Accordingly, IMD 100 and programmer 104 can establish a secure link after pairing or binding to communicate over the secure link. Although examples are described with programmer 104 communicating over the secure link, examples are not so limited. For example, IMD 100 can communicate data with a second device after pairing or binding with the second device according to the communication protocol. One example of a second device is programmer 104, although other examples are possible. Generally, a device configured to perform operations according to a communication protocol can be considered a second device similar to a first device.

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

[0060] The present disclosure describes examples of IMD 100 broadcasting first data to charger 102 while communicating with programmer 104 using the connection mode. Such disclosures include examples where IMD 100 broadcasts and communicates over the secure link simultaneously, or examples where IMD 100 broadcasts and communicates over the secure link in an interleaved manner. Generally, IMD 100 broadcasting first data to charger 102 while communicating with programmer 104 means that IMD 100 broadcasts first data to charger 102 during a recharging session without pairing or binding, and communicates second data over the secure link after pairing or binding with programmer 104.

[0061] The first data broadcast by IMD 100 can be processable by any other device also configured according to the communication protocol. In some examples, IMD 100 and charger 102 can be configured with a key that IMD 100 and charger 102 use to encrypt the first data. As one example, programmer 104 can provide the key to both IMD 100 and charger 102. As another example, IMD 100 and charger 102 can be preconfigured with the key. As yet another example, IMD 100 and charger 102 can be configured to use a different communication protocol (e.g., other than Bluetooth Low Energy) to encrypt the first data. ™In such examples, the charger 102 can use an additional communication protocol to transmit the key, and the IMD 100 can use an additional communication protocol to receive the key. Other ways of encrypting the first data are possible, and the above examples should not be considered limiting.

[0062] As described above, by broadcasting the first data specific to the charger 102 in the advertising mode, the IMD 100 can be used to establish a connection with the programmer 104. However, to establish a connection with the programmer 104 (e.g., establish a secure link), the IMD 100 and the programmer 104 can need to perform pairing or binding through a handshake. To perform the handshake, the IMD 100 can need to advertise information for pairing or binding, such that the IMD 100 and the programmer 104 can establish a secure link. However, as described above, the IMD 100 is utilizing the advertising mode to broadcast the first data specific to the charger 102.

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

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

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

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

[0067] In some examples, the processing circuitry can cause the telemetry circuitry to broadcast the first data and transmit the second data simultaneously. In some examples, the processing circuitry can cause the telemetry circuitry to stagger the broadcasting of the first data and the transmitting of the second data. That is, the processing circuitry can cause the telemetry circuitry to broadcast the first data while transmitting the second data, and to transmit the second data while broadcasting the first data. The processing circuitry can be configured to limit the number of devices with which the IMD 100 is allowed to pair or bind at one time according to the communication protocol to one, although example techniques are not limited thereto.

[0068] As described, the IMD 100 can be configured to broadcast first data specific to a first device (e.g., charger 102) in the advertising mode, but can also broadcast information that a second device (e.g., programmer 104) can use to pair or bind. As one example, the first data is broadcast as part of a first packet, and the processing circuitry is configured to broadcast a second packet indicating that the IMD 100 is available for pairing or binding in the advertising mode prior to pairing or binding with the second device. For example, the processing circuitry can be configured to cause the telemetry circuitry to stagger the broadcasting of the first packet and the second packet in the advertising mode. In some examples, the processing circuitry is configured to receive a request to pair or bind with the second device in response to the broadcasting of the second packet, and to establish the pairing or binding with the second device in response to the request. The request to pair or bind or establish the pairing or binding can be considered 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, the IMD 100 can be configured to broadcast first data specific to a first device, and to transmit second data with a second device simultaneously or in a staggered manner. For example, the communication protocol defines a plurality of communication channels. The processing circuitry can be configured to cause the telemetry circuitry to broadcast first data for the IMD 100 via a first subset of the plurality of channels reserved for advertising, and to transmit second data for the IMD 100 via a second subset of the plurality of channels reserved for pairing or binding communications (e.g., secure communications).

[0070] The IMD 100 can broadcast the first data, and there is a possibility that another device receives the first data. In some examples, the communication protocol can be a first communication protocol. For encryption, the telemetry circuit of the IMD 100 can receive data from the first device (e.g., the charger 102) according to a different second communication protocol. The data can include key information. The processing circuit is configured to cause the telemetry circuit to broadcast the first data based on the key information. One example of the different second communication protocol is data transmitted using inductive telemetry.

[0071] Additionally, in some examples, the first device can need to output information for the IMD 100. However, because the first device and the IMD 100 are communicating via a connectionless connection, there can not be a secure connection after pairing or binding between the charger 102 and the IMD 100. Thus, in some examples, the processing circuit can be configured to cause the telemetry circuit to scan for data broadcast from the first device (e.g., the charger 102) in an advertising mode of the first device on an advertising channel assigned to the advertising mode. The telemetry circuit can receive the data broadcast from the first device. In some examples, the first device can be able to transmit data of the IMD 100 (e.g., after a charging session) using the different second communication protocol described above. Additionally, in some examples, the IMD 100 and the first device can communicate in the advertising mode using bidirectional communication according to the BLE 5.4 specification. That is, the first device can utilize bidirectional communication in the advertising mode when broadcasting data.

[0072] Figure 2 is a conceptual diagram illustrating example wireless channels for transmitting advertisements and for paired or bound communication. In Figure 2 In examples of the 2.4 GHz ISM (industrial, scientific, and medical) band, there are multiple channels (e.g., 40 channels) ranging from 2400 MHz to 2480 MHz for a communication protocol (e.g., BLE), labeled as channels 0 through 40. Channels 37, 38, and 39 can be a first subset of the multiple channels reserved for advertising, and channels 0 through 36 can be a second subset of the multiple channels reserved for paired or bound communication. That is, the communication protocol operates on different advertising channels in the 2.4 GHz ISM band. These channels are independent radio frequencies for transmitting data, where advertising typically occurs on three channels (37, 38, and 39) to maximize the chance of successful transmission.

[0073] IMD 100 can be considered a notification device for information in broadcast notification packets, which include data fields such as unique identifiers (e.g., its MAC address), service UUIDs (Universally Unique Identifiers), manufacturer-specific data, or other custom data. IMD 100 can determine the interval at which it sends notification packets, which limits the frequency at which it broadcasts these packets. Shorter intervals ensure a higher probability that another device will detect the packets.

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

[0075] In one or more examples, IMD 100 may detect that charger 102 is delivering charging energy. For example, charging energy may cause a switch in IMD 100 to close, allowing the charging energy to be routed to the power source of IMD 100, and 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 telemetry circuitry to broadcast first data in response to the detection that charger 102 is delivering charging energy. The processing circuitry may receive a request to pair or bind with a second device (e.g., programmer 104) in response to the broadcast of a second packet, and establish pairing or binding with the second device in response to the request (e.g., receiving a request to establish a secure link and establishing a secure link). For example, programmer 104 may periodically scan the notification channel for incoming packets. When a notification packet (e.g., the second packet in the example above) is received, programmer 104 may read the data fields contained within the packet. If programmer 104 finds an announcement packet with relevant information (e.g., a specific service UUID), programmer 104 can use a separate process called connection initiation (e.g., handshake) to initiate a connection with IMD 100.

[0076] Figure 3 It is shown Figure 1 A block diagram of exemplary components of a medical device. Medical device 300 is as described above regarding... Figure 1 An example of the IMD 100. In Figure 3In the illustrated example, medical device 300 includes coil 301, power source 302, processing circuitry 304, telemetry circuitry 306, temperature sensor 308, one or more sensors 310 (e.g., an accelerometer), memory 312, and therapy and sensing circuitry 314 coupled to one or more electrodes 316A-D. In other examples, medical device 300 can include a greater or lesser number of components, e.g., in some examples, medical device 300 can not include sensors 310. In general, medical device 300 can include any suitable hardware arrangement, alone or in combination with software and / or firmware, for performing the various techniques described herein attributed to medical device 300 and processing circuitry 304 and any equivalents thereof.

[0077] Processing circuitry 304 can 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 can include computer readable storage media, such as memory 312, which can be implemented using random access memory (RAM), read only memory (ROM), programmable read only memory (PROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, including executable instructions for causing processing circuitry 304 to perform the actions attributed to it. Moreover, although processing circuitry 304, therapy and sensing circuitry 314, recharging circuitry 303, telemetry circuitry 306, and temperature sensor 308 are described as independent circuits, in some examples, some combination of processing circuitry 304, therapy and sensing circuitry 314, recharging circuitry 303, telemetry circuitry 306, and temperature sensor 308 are functionally integrated. In some examples, processing circuitry 304, therapy and sensing circuitry 314, recharging circuitry 303, telemetry circuitry 306, and temperature sensor 308 correspond to separate hardware units, such as ASICs, DSPs, FPGAs, or other hardware units. In the present disclosure, for simplicity, therapy and sensing circuitry 314 can be referred to as therapy circuitry 314, such as in examples where sensing is not present.

[0078] Memory 312 may store therapy programs or other instructions specifying therapy parameter values ​​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 supply 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 relating to determining the temperature of the housing of medical device 300 and / or the temperature of the outer surface of the housing of medical device 300 based on the temperature sensed by one or more temperature sensors, such as temperature sensor 308.

[0079] In some examples, memory 312 may store programming settings, such as the output amplitude of the electrical stimulation therapy, pulse width, etc. Memory 312 may store programming instructions that, when executed by processing circuitry 304, cause processing circuitry 304 to perform the exemplary techniques described in this disclosure.

[0080] The therapy and sensing circuit 314 can generate and deliver electrical stimulation under the control of the processing circuit 304. In some examples, the processing circuit 304 controls the therapy circuit 314 by accessing the memory 312 to selectively access at least one stimulation program in the stimulation program and loading the at least one stimulation program into the therapy circuit 314. For example, in operation, the processing circuit 304 may access the memory 312 to load one stimulation program into the therapy circuit 314. In such examples, the relevant stimulation parameters may include voltage amplitude, current amplitude, pulse rate, pulse width, duty cycle, or combinations of electrodes 316A, 316B, 316C, and 316D (collectively, "electrodes 316") that the therapy circuit 314 may use to deliver electrical stimulation signals and sense biological signals. In other examples, with Figure 3 Compared to the four electrodes shown in the example, medical device 300 may have more or fewer electrodes. In some examples, electrodes 316 may be part of or attached to the housing of medical device 300 (e.g., leadless electrodes). In other examples, one or more of electrodes 316 may be part of a lead implanted in or attached to a patient to sense biosignals and / or deliver electrical stimulation.

[0081] exist Figure 3 In the example, the medical device 300 also includes components for receiving power to recharge the rechargeable power supply 302 when it has been at least partially depleted. Figure 3As shown, the medical device 300 includes a coil 301 and a recharging circuit 303 coupled to a rechargeable power source 302. The recharging circuit 303 can be configured to charge the rechargeable power source 302 at a selected power level determined by the processing circuit 304 or an external charging device, such as the charger 102 described above with respect to Figure 1 The recharging circuit 303 can include any of a variety of charging and / or control circuits configured to process or convert current induced in the coil 301 into a charging current to charge the power source 302.

[0082] The coil 301 can include a wire coil or other device capable of inductive coupling with a primary coil disposed outside of the medical device 300. Although the coil 301 is shown as a simple loop in Figure 3 The coil 301 can include a multi-turn electrically conductive wire. The coil 301 can include a wire winding configured such that current can be induced within the coil 301 from a magnetic field. The induced current can then be used to recharge the rechargeable power source 302.

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

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

[0085] Although power source 302, recharging 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 can be disposed outside of the housing. For example, in some implementations coil 301 can 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 can also control exchange of information with charger 102 and programmer 104 using telemetry circuitry 306. Telemetry circuitry 306 can be configured to wirelessly communicate with charger 102 or programmer 104 using radio frequency (RF) protocols such as Bluetooth ™ , BLE, or similar RF protocols, as well as using inductive communication protocols. Telemetry circuitry 306 can include, for example, one or more antennas configured to communicate with charger 102 or programmer 104. Processing circuitry 304 can transmit operational information via telemetry circuitry 306 as well as receive therapy programs or therapy parameter adjustments. Telemetry circuitry 306 can be configured to control exchange of information related to sensed and / or determined temperature data, such as temperature sensed by using temperature sensor 308 and / or temperature determined from temperature sensed using the temperature sensor.

[0087] In some examples, processing circuitry 30 can transmit additional information related to the operation of rechargeable power source 302 to charger 102. For example, processing circuitry 304 can use telemetry circuitry 306 to transmit an indication that rechargeable power source 302 is fully charged, that rechargeable power source 302 is fully discharged, the amount of charging current output by recharging circuitry 303, for example, to power source 302, or any other charging status of rechargeable power source 302. In some examples, processing circuitry 304 can use telemetry circuitry 306 to transmit instructions to charger 102, including instructions regarding further control of the charging session, such as instructions to reduce the power level or terminate the charging session based on a determined temperature of the housing / outer surface of medical device 300. Processing circuitry 304 can also cause telemetry circuitry 306 to transmit information to charger 102 indicating any problems or errors with rechargeable power source 302 that can prevent rechargeable power source 302 from providing operational power to components of medical device 300.

[0088] According to one or more examples described in this disclosure, telemetry circuitry 306 can be configured to communicate according to a communication protocol that includes an advertising mode and a connected mode. Processing circuitry 304 can be configured to cause telemetry circuitry 306 to broadcast first data of medical device 300 that is specific to a first device (e.g., charger 102 or other device) in the advertising mode without requiring pairing or binding with the first device according to the communication protocol. 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 can also cause telemetry circuitry 306 to transmit second data of medical device 300 to a second device (e.g., programmer 104) in the connected mode after pairing or binding with the second device according to the communication protocol. 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, assuming the first device is charger 102 and the second device is programmer 104, telemetry circuit 306 broadcasts first data as part of a first packet, and before pairing or binding with programmer 104, processing circuit 304 is configured to broadcast a second packet (e.g., a unique identifier of medical device 300) in notification mode indicating that medical device 300 is available for pairing or binding. Processing circuit 306 may be configured to interleave the broadcasts of the first and second packets in notification mode. Processing circuit 304 may receive a request to pair or bind with programmer 104 in response to the broadcast of the second packet, and establish pairing or binding with programmer 104 in response to the request. In some examples, processing circuit 304 may limit the number of devices that medical device 300 can pair or bind with at one time according to the communication protocol to one (e.g., such that only programmer 104 is allowed to program medical device 300).

[0090] Figure 4 yes Figure 1 A block diagram of an exemplary charger. Figure 4 Charger 400 is shown as an example of charger 102. In some examples, charger 400 may be described as a handheld device, and in other examples, charger 400 may be a larger or non-portable device. Figure 4 As shown in the example, charger 400 includes two separate components. Housing 402 encloses components such as processing circuitry 408, memory 410, user interface 412, telemetry circuitry 414, and power supply 418. Charging head 404 (also referred to as charging stick 404) may include charging circuitry 420, temperature sensor 422, and coil 406. In some examples, the separate charging head 404 may facilitate positioning of coil 406 on coil 301 of medical device 300.

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

[0092] Charger 400 may also include Figure 3 Temperature sensor 308 is similar to one or more temperature sensors (shown as temperature sensor 422). Figure 4As shown, the temperature sensor 422 can be disposed within the charging head 404. In other examples, one or more of the temperature sensors of the temperature sensor 422 can be disposed within the housing 402. For example, the charging head 404 can include one or more temperature sensors positioned and configured to sense a temperature of the coil 406 and / or a temperature of a surface of a housing of the charging head 404. In some examples, the charger 400 can not include the temperature sensor 422.

[0093] In general, the charger 400 includes any suitable hardware arrangement of individual or in combination with software and / or firmware for performing the techniques attributed to the charger 400, as well as the processing circuitry 408, user interface 412, telemetry circuitry 414, and charging circuitry 420 of the charger 400, and / or any equivalents thereof. In various examples, the charger 400 can 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. In various examples, the charger 400 can also include memory 410 (such as RAM, ROM, PROM, EPROM, EEPROM, flash memory, hard disks, CD-ROMs), which includes executable instructions for the one or more processors to perform the actions attributed to them. Moreover, although the processing circuitry 408, telemetry circuitry 414, charging circuitry 420, and temperature sensor 422 are described as independent modules, in some examples, the processing circuitry 408, telemetry circuitry 414, charging circuitry 420, and / or temperature sensor 422 are functionally integrated. In some examples, the processing circuitry 408, telemetry circuitry 414, charging circuitry 420, and / or temperature sensor 422 correspond to separate hardware units, such as ASICs, DSPs, FPGAs, or other hardware units.

[0094] Throughout the present disclosure, the memory 410 can store instructions that, when executed by the processing circuitry 408, cause the processing circuitry 408 and the charger 400 to provide the functionality attributed to the charger 400, and / or any equivalents thereof. For example, the memory 410 can include instructions that cause the processing circuitry 408 to control a power level for charging the medical device 300 in response to a determined temperature of a housing / outer surface of the medical device 300 as communicated from the medical device 300, or instructions for any other functionality. The memory 410 can include a record of selected power levels, sensed temperatures, determined temperatures, or any other data related to charging the rechargeable power source 302, as described above with respect to the medical device 300. Figure 3

[0095] ​User interface 412 can 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, can vary among different examples of charger 400, and can be absent in some examples.

[0096] Charging circuit 420 can include one or more circuits that generate an electrical signal and current within coil 406. In some examples, charging circuit 420 can generate alternating current at a specified amplitude and frequency. In other examples, charging circuit 420 can generate direct current. In any case, charging circuit 420 can be capable of generating an electrical signal, and a subsequent magnetic field, to transfer various levels of power to medical device 300. As such, charging circuit 420 can be configured to charge rechargeable power source 302 of medical device 300 at a selected power level.

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

[0098] Telemetry circuit 414, under the control of processing circuit 408 or processing circuit 304, supports wireless communication between medical device 300 and charger 400. Telemetry circuit 414 can also be configured to communicate with another computing device via wireless communication techniques, or directly through a wired connection. In some examples, telemetry circuit 414 can be substantially similar to telemetry circuit 306 of medical device 300 described herein, providing wireless communication via RF or near-field inductive medium. In some examples, telemetry circuit 414 can include an antenna, which can take on many forms such as an internal or external antenna. While telemetry circuits 414 and 306 can each include a dedicated antenna for communication between these devices, telemetry circuits 414 and 306 can 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 the present disclosure, charger 400 can receive data specific to charger 400 through a broadcast in an advertising mode. Processing circuit 408 can be configured to process the data received in the broadcast to control operation of charging circuit 420. That is, processing circuit 408 can be configured to listen for a first packet from medical device 300 that includes data for processing circuit 408 to control the rate at which electrical energy is delivered, whether delivery of electrical energy is stopped, etc.

[0100] In one or more examples, with respect to the medical device 300 transmitting a second packet in an advertising mode to establish a secure connection (e.g., a paired or bonded connection) in a connected mode, the processing circuit 408 can be configured to ignore such communications. That is, the processing circuit 408 can refrain from establishing a secure (e.g., paired or bonded) link with the medical device 300. However, in some examples, the processing circuit 408 can initially set up a secure link with the medical device 300 based on the advertising mode data. Then, the processing circuit 408 can receive a request to disable the secure link (e.g., such as in the case where the medical device 300 is to establish a secure link with the programmer 104). In this case, then, the processing circuit 408 can listen for data from the medical device 300 in the advertising mode. In some examples, the processing circuit 408 can put the telemetry circuit 414 in a continuous scan mode to ensure that the charger 400 receives an advertisement from the medical device 300.

[0101] In some examples, the communication protocol (e.g., BLE) is a first communication protocol. The telemetry circuit 414 can be configured to transmit data from the charger 400 according to a different second communication protocol (e.g., inductive telemetry received by the coil 301 using the coil 406). The third data includes key information. The data broadcast by the medical device 300 that is specific to the charger 400 can be based on the key information.

[0102] To enable the charger 400 to transmit data back to the medical device 300, in some examples, the processing circuit 408 can cause the telemetry circuit 414 to transmit information specific to the medical device 300 in a broadcast mode. In some examples, the processing circuit 408 can cause the telemetry circuit 414 to broadcast the information according to bidirectional communication in the advertising mode of the BLE 5.4 specification.

[0103] Figure 5 is a block diagram illustrating an example configuration of components of an external programmer. Figure 1 is a block diagram illustrating an example configuration of components of an external programmer. Figure 5 A programmer 500 is shown that is an example of the programmer 104 of Figure 1 FIG. 1. Although the programmer 500 can generally be described as a handheld device, the programmer 500 can be a larger portable device or a more fixed device. As shown in Figure 5 FIG. 5, the programmer 500 can include a processing circuit 502, a storage device 504, a user interface 506, a telemetry circuit 508, and a power source 510. Throughout the present disclosure, the storage device 504 can store instructions that, when executed by the processing circuit 502, cause the processing circuit 502 and the programmer 500 to provide the functionality ascribed to the programmer 500. Each of these components, circuits, or modules can include circuitry configured to perform some or all of the functionality described herein.

[0104] Generally, programmer 500 includes any suitable hardware arrangement of individual or combined software and / or firmware for performing the techniques attributed to external programmer 500, as well as processing circuitry 502, user interface 506, and telemetry circuitry 508 of programmer 500. In various examples, programmer 500 can 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. In various examples, programmer 500 can also include memory 504, such as RAM, ROM, PROM, EPROM, EEPROM, flash memory, hard disks, CD-ROMs, which can include executable instructions for causing the one or more processors to perform the actions attributed to them. In addition, 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 separate hardware units, such as ASICs, DSPs, FPGAs, or other hardware units.

[0105] Throughout the present disclosure, memory 504 (e.g., storage) can store instructions that, when executed by processing circuitry 502, cause processing circuitry 502 and programmer 500 to provide functionality attributed to programmer 500. Memory 504 can include a plurality of programs, where each program includes a set of parameters defining stimulation pulses, such as control pulses and / or notification pulses. Memory 504 can also store data received from a medical device (e.g., medical device 300).

[0106] User interface 506 can include buttons or a 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 touchscreen. User interface 506 can be configured to display any information related to the delivery of electrical stimulation, identified patient behavior, sensed patient parameter values, patient behavior criteria, or any other such information. User interface 506 can also receive user input via user interface 506. The input can be in the form of, for example, pressing a button on a keypad or selecting an icon from a touchscreen. The input can request to start or stop electrical stimulation, or request some other change to the delivery of electrical stimulation.

[0107] The telemetry circuit 508, under the control of the processing circuit 502, can support wireless communication between the medical device 300 and the programmer 500. The telemetry circuit 508 can also be configured to communicate with another computing device via wireless communication techniques, or directly through a wired connection. In some examples, the telemetry circuit 508 provides wireless communication via RF or near-field induction ™ RF communication according to the Bluetooth® specification set or other standard or proprietary telemetry protocols.

[0108] In some examples, the transmission to the medical device 300 is of a selection of stimulation parameters of a stimulation program to deliver to the patient. In other examples, the therapy can include a medication, activity, or other instruction that the patient should perform themselves or that a caregiver performs for the patient. In some examples, the programmer 500 provides a visual, audible, and / or tactile notification indicating that there is a new instruction. In some examples, the programmer 500 requires receipt of user input confirming that the instruction has been completed.

[0109] The power source 510 is configured to deliver operating power to the components of the external programmer 500. The power source 510 can include a battery and power generation circuitry to produce the operating power. In some examples, the battery is rechargeable to allow extended operation. Recharging can be accomplished through electrical coupling of the power source 510 to a cradle or plug that is connected to an alternating current (AC) outlet. Additionally, recharging can be accomplished through proximal inductive interaction between an external charger and an inductive charging coil within the programmer 500. In other examples, a traditional battery (e.g., nickel cadmium or lithium ion) can be used. Furthermore, the programmer 500 can be directly coupled to an alternating current outlet to operate.

[0110] Figure 6 is a flow chart showing an example method of operation. For ease of illustration, the method is described with respect to the medical device 300 Figure 6The processing circuit 304 can cause the telemetry circuit 306 to broadcast first data of the medical device 300 specific to the first device in an advertising mode without pairing or binding with the first device according to the communication protocol (e.g., without establishing a secure link) (600). As one example, the first device is a charger 400 of the 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 a temperature of the medical device 300 and a charge level of the medical device 300. In one or more examples, the processing circuit 304 can cause the telemetry circuit 306 to broadcast the first data of the medical device 300 via a first subset of the plurality of channels reserved for advertising. As another example, the first device is a bedside monitor or some other device.

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

[0112] For example, the processing circuit 304 can be configured to cause the telemetry circuit 306 to transmit second data of the medical device 300 for the second device in a connected mode after pairing or binding with the second device according to the communication protocol (e.g., after establishing a secure link) (602). The second device can be a programmer 500 of the medical device 300. The second data can include information related to programming of the medical device 300. For example, the second data includes therapy parameters. In some examples, the processing circuit 304 can be configured to cause the telemetry circuit 306 to transmit the second data of the medical device 300 via a second subset of the plurality of channels reserved for paired or bound communications (e.g., reserved for a secure link). In some examples, the processing circuit 304 can be configured to cause the telemetry circuit 306 to broadcast the first data and transmit the second data simultaneously, or to cause the telemetry circuit 306 to interleave the broadcast of the first data and the transmission of the second data. That is, the processing circuit 304 can be configured to cause the telemetry circuit 306 to transmit the second data while broadcasting the first data, or to broadcast the first data while transmitting the second data.

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

[0114] For example, the medical device 300 can be in an advertising mode (700) that advertises a connection with the device. This can be an initial mode of the medical device 300. The medical device 300 can sense charging energy from the charger 400 (702). For example, as one example way in which the medical device 300 can sense charging energy from the charger 400, the recharging circuit 303 can indicate to the processing circuit 304 that energy is present on the coil 301.

[0115] In this case, the medical device 300 can continue to advertise the connection and broadcast charger-specific advertisements (704). That is, the medical device 300 can detect that the charger 400 is delivering charging energy, and cause the telemetry circuit 306 to broadcast first data specific to the 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 the processing circuit 304 can be configured to broadcast a second packet indicating that the medical device 300 is available for pairing or binding (e.g., available for establishing a secure link) in the advertising mode before pairing or binding with the programmer 500 (e.g., before establishing a secure link).

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

[0117] The medical device 300 can communicate with the programmer 500 and broadcast charger-specific advertisements (708). For example, the processing circuit 304 can be configured to cause the telemetry circuit 306 to broadcast the first data (e.g., specific to the charger 400) and transmit the second data (e.g., for the programmer 500) simultaneously, or to cause the telemetry circuit 306 to interleave the broadcast of the first data and the transmission of the second data. That is, the medical device 300 can broadcast the first data while transmitting the second data, and vice versa.

[0118] The following clauses are a non-limiting list of embodiments according to one or more techniques of the present disclosure.

[0119] Clause 1 : A medical device comprising: a telemetry circuit configured to communicate according to a communication protocol comprising an advertising mode and a connected mode; and a processing circuit configured to cause the telemetry circuit to: broadcast, in the advertising mode, first data of the medical device that is specific to a first device without pairing or binding to the first device according to the communication protocol; and transmit, in the connected mode, second data of the medical device for a second device after pairing or binding to the second device according to the communication protocol, the first and second devices being different devices.

[0120] Clause 2. The medical device of clause 1, wherein the first device is a charger for the medical device, wherein the first data comprises information related to recharging of the medical device, wherein the second device is a programmer for the medical device, and wherein the second data comprises information related to programming of the medical device.

[0121] Clause 3. The medical device of any of clauses 1 and 2, wherein the processing circuit is configured to cause the telemetry circuit to simultaneously broadcast the first data and transmit the second data, or to cause the telemetry circuit to stagger the broadcasting of the first data and the transmitting of the second data.

[0122] Clause 4. The medical device of any of clauses 1 to 3, wherein the first device is a charger for the medical device, wherein the processing circuit is configured to detect that the charger is delivering charging energy, wherein to cause the telemetry circuit to broadcast the first data, the processing circuit is configured to cause the telemetry circuit 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 to 4, wherein the first data is broadcast as part of a first packet, and wherein, prior to pairing or binding with the second device, the processing circuit is configured to broadcast, in the advertising mode, a second packet indicating that the medical device is available for pairing or binding.

[0124] Clause 6. The medical device of clause 5, wherein the processing circuit is configured to cause the telemetry circuit to stagger the broadcasting of the first packet and the second packet in the advertising mode.

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

[0126] Clause 8. The medical device of any of clauses 1-7, wherein the processing circuit is configured to limit a number of devices to which the medical device is permitted to pair or bind with at one time according to 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 circuit is configured to cause the telemetry circuit to: broadcast the first data of the medical device via a first subset of the plurality of channels reserved for advertising; and transmit the second data of the medical device via a second subset of the plurality of channels reserved for pairing or binding communications.

[0128] Clause 10. The medical device of any of clauses 1-9, wherein the communication protocol is a first communication protocol, wherein the telemetry circuit is configured to receive third data from the first device according to a different second communication protocol, the third data including key information, and wherein the processing circuit is configured to cause the telemetry circuit 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 circuit is configured to: cause the telemetry circuit to scan for third data on an advertising channel assigned to the advertising mode, the third data broadcast from the first device in the advertising mode of the first device; and receive the third data broadcast 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 a temperature of the medical device and a power level of the medical device.

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

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

[0133] Clause 15. A method for communication, the method comprising: broadcasting, with a medical device, first data of the medical device that is specific to a first device in an advertising mode of a communication protocol without pairing or binding with the first device according to the communication protocol; and transmitting, with the medical device, second data of the medical device for a second device in a connected mode of the communication protocol after pairing or binding with the second device according to the communication protocol, 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 for the medical device, wherein the first data includes information related to recharging of the medical device, wherein the second device is a programmer for 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 includes broadcasting the first data and communicating the second data simultaneously, or staggering the broadcasting of the first data and the communicating of the second data.

[0136] Clause 18. The method of any of clauses 15-17, wherein the first device is a charger for the medical device, the method further comprising detecting that the charger is delivering charging energy, wherein broadcasting the first data includes 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 broadcasted as part of a first packet, the method further comprising broadcasting, in the advertising mode, a second packet prior to pairing or binding with the second device, the second packet indicating that the medical device is available for pairing or binding.

[0138] Clause 20. The method of clause 19, the method further comprising staggering the broadcasting of the first packet and the second packet in the advertising mode.

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

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

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

[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 according to a different, second 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 an advertising channel assigned to the advertising mode, the third data broadcast from the first device in the advertising mode of the first device; and receiving the third data broadcast from the first device.

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

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

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

[0147] Clause 29. A computer-readable storage medium having stored thereon instructions that, when executed, cause one or more processors of a medical device to: broadcast, in an advertising mode of a communication protocol, first data of the medical device that is specific to a first device without pairing or binding with the first device according to the communication protocol; and transmit, in a connected mode of the communication protocol, second data of the medical device for a second device after pairing or binding with the second device according to the communication protocol, 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 can be implemented, at least in part, in hardware, software, firmware or any combination thereof. For example, various aspects of the described techniques can 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" can generally refer to any of the foregoing logic circuitry, alone or in combination with other logic circuitry. A control unit comprising hardware can also perform one or more of the techniques of this disclosure.

[0151] Such hardware, software, and firmware can 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 can be implemented together or independently 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 can 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 can also be embedded in or encoded in a computer-readable medium, such as a computer-readable storage medium, including instructions for causing a programmable processor or other processor to perform the methods. Computer-readable storage media can include random access memory (RAM), read only memory (ROM), programmable read only memory (PROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, a hard disk, a compact disc (CD), a digital video disc (DVD), a floppy disk, a cassette, magnetic tape, magnetic medium, optical medium, or other computer-readable medium.

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

Claims

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

2. The medical device of claim 1, wherein the first device is a charger for the medical device, wherein the first data comprises information related to recharging of the medical device, wherein the second device is a programmer for the medical device, and wherein the second data comprises 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 broadcast the first data and communicate the second data interleaved.

4. The medical device of any of claims 1-3, wherein the first device is a charger for 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 prior to pairing or binding with the second device, the processing circuitry is configured to broadcast, in the advertising mode, a second packet indicating that the medical device is available for pairing or binding.

6. The medical device of claim 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 advertising 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 bind with the second device in response to the broadcast of the second packet; and establish the pairing or binding with the second device in response to the request.

8. The medical device of any of claims 1-7, wherein the processing circuitry is configured to limit the number of devices with which the medical device is allowed to pair or bind at a time according to 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 connected mode communication. transmit the second data of the medical device via a second subset of the plurality of channels reserved for pairing or binding communications.

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

11. The medical device of any one of claims 1-10, wherein the processing circuit is configured to: cause the telemetry circuit to scan for third data on an advertising channel assigned to the advertising mode, the third data broadcast from the first device in the advertising mode of the first device; and receive the third data broadcast from the first device.

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

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

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

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

Images