Classifications

• • A—HUMAN NECESSITIES
  • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
  • A61F—FILTERS IMPLANTABLE INTO BLOOD VESSELS; PROSTHESES; DEVICES PROVIDING PATENCY TO, OR PREVENTING COLLAPSING OF, TUBULAR STRUCTURES OF THE BODY, e.g. STENTS; ORTHOPAEDIC, NURSING OR CONTRACEPTIVE DEVICES; FOMENTATION; TREATMENT OR PROTECTION OF EYES OR EARS; BANDAGES, DRESSINGS OR ABSORBENT PADS; FIRST-AID KITS
  • A61F2/00—Filters implantable into blood vessels; Prostheses, i.e. artificial substitutes or replacements for parts of the body; Appliances for connecting them with the body; Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
  • A61F2/82—Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
• • A—HUMAN NECESSITIES
  • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
  • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
  • A61B5/00—Measuring for diagnostic purposes; Identification of persons
  • A61B5/0002—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network
  • A61B5/0031—Implanted circuitry
• • A—HUMAN NECESSITIES
  • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
  • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
  • A61B5/00—Measuring for diagnostic purposes; Identification of persons
  • A61B5/02—Detecting, measuring or recording pulse, heart rate, blood pressure or blood flow; Combined pulse/heart-rate/blood pressure determination; Evaluating a cardiovascular condition not otherwise provided for, e.g. using combinations of techniques provided for in this group with electrocardiography or electroauscultation; Heart catheters for measuring blood pressure
  • A61B5/021—Measuring pressure in heart or blood vessels
  • A61B5/0215—Measuring pressure in heart or blood vessels by means inserted into the body
• • A—HUMAN NECESSITIES
  • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
  • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
  • A61B5/00—Measuring for diagnostic purposes; Identification of persons
  • A61B5/07—Endoradiosondes
  • A61B5/076—Permanent implantations
• • A—HUMAN NECESSITIES
  • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
  • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
  • A61B2560/00—Constructional details of operational features of apparatus; Accessories for medical measuring apparatus
  • A61B2560/02—Operational features
  • A61B2560/0204—Operational features of power management
  • A61B2560/0209—Operational features of power management adapted for power saving
• • A—HUMAN NECESSITIES
  • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
  • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
  • A61B2562/00—Details of sensors; Constructional details of sensor housings or probes; Accessories for sensors
  • A61B2562/08—Sensors provided with means for identification, e.g. barcodes or memory chips
• • A—HUMAN NECESSITIES
  • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
  • A61N—ELECTROTHERAPY; MAGNETOTHERAPY; RADIATION THERAPY; ULTRASOUND THERAPY
  • A61N1/00—Electrotherapy; Circuits therefor
  • A61N1/18—Applying electric currents by contact electrodes
  • A61N1/32—Applying electric currents by contact electrodes alternating or intermittent currents
  • A61N1/36—Applying electric currents by contact electrodes alternating or intermittent currents for stimulation
  • A61N1/372—Arrangements in connection with the implantation of stimulators
  • A61N1/37211—Means for communicating with stimulators
  • A61N1/37252—Details of algorithms or data aspects of communication system, e.g. handshaking, transmitting specific data or segmenting data
  • A61N1/37288—Communication to several implantable medical devices within one patient

Definitions

• the present invention relates generally to communication between implantable medical devices. More specifically, the present invention relates to a system and method for addressing implantable medical devices.
• Medical devices can be implanted in the bodies of patients for various purposes. Some medical devices detect physiologic events and may apply therapy in response to certain events of interest. For example, a cardiac pacemaker can detect a lull in the beating of the patient's heart and apply an electrical pulse to stimulate the heart into beating again. Other devices may be implanted, such as defibrillators, neuro-stimulators, ICDs, CRTS, drug pumps, and various types of sensors. It is becoming more common to implant multiple devices in a single patient. In such situations, a controller device can communicate with the implanted medical devices. The medical devices can communicate data to the controller in response to commands from the controller. When multiple medical devices are implanted, the controller must be able to direct commands to a selected device with a relatively high degree of reliability.
• globally unique identifiers such as device manufacturing serial numbers
• Typical systems involve a single external master controlling communication with a single slave device within the body.
• Multiple devices within a body in communication with each other or with an external device require using globally unique identifiers as well, but this can unnecessarily burden the local communication traffic.
• the representation, in bits, of a globally unique identifier must be sufficiently large to identify a global population of devices. For example, 20- to 64-bit globally unique identifiers are common for electronic devices. In a local patient environment that can consist of approximately 6 implanted devices in communication with each other or with a local device external to the body, transferring large, unique identifiers during communication sessions represents communication overhead that consumes power and delays transfer of desired data within the local environment.
• Embodiments described herein include systems and methods for communicating with an implanted medical device without use of the device's globally unique identifier. For each medical device, a shorter local device identifier is selected and used for addressing the device, in order to reduce overhead in communications.
• the local identifier is unique within a single patient's body, but not necessarily globally unique among identifiers of devices outside the patient's body. The number of devices in any single body will be considerably smaller than a global population of devices, so the local identifier can be represented with fewer bits than a globally unique identifier, which speeds communication and saves electrical power consumed for communication purposes.
• the local device identifier may be stored in volatile or nonvolatile memory of the medical device. If stored in nonvolatile memory, the local identifier will be available again for use after reset or power-up of the medical device.
• a controller device is operable to identify each medical device upon power- up, assign a local identifier to each slave device, and communicate each local identifier to the associated slave device. The controller device may also command the local identifier to be written to nonvolatile memory prior to reset or power-up of the medical device.
• An embodiment of a system includes multiple slave devices implanted in a human body, wherein each slave device includes a communication module operable to receive transmitted communications, and wherein each slave device is associated with a globally unique, or simply global, device identifier.
• the system further includes a master device including a communications module operable to address a first communication to a selected slave device using the global device identifier associated with the selected slave device, wherein the first communication includes a local identifier for assignment to the selected slave device, wherein the assigned local identifier does not match any other local identifier assigned to any other slave device implanted in that particular human body, and wherein subsequent communications are addressed to the selected slave device using the assigned local identifier.
• An embodiment of a method includes assigning a local identifier to each of one or more of multiple slave medical devices, wherein each assigned local identifier is selectable during each communication session, transmitting a message to each of the one or more slave medical devices, wherein the message comprises the associated permanent device identifier and the assigned local identifier, and using the local identifier assigned to a selected one of the one or more slave medical devices to address subsequent communications to the selected slave device.
• Fig. 1 illustrates a human patient with one or more slave implantable medical devices (IMD) in communication with a master device, wherein the slave devices are addressable using a local identifier.
• IMD implantable medical devices
• Fig. 2 is a schematic diagram illustrating a generalized system including a master device and one or more slave devices.
• Fig. 3 is a functional block diagram illustrating functional components of a slave device in accordance with one embodiment.
• Fig. 4 is a functional block diagram illustrating functional components of a master device in accordance with one embodiment.
• Fig. 5 is a state diagram illustrating a state machine that can be implemented by a slave device implanted in a patient, and in communication with a master device.
• Fig. 6 is a flow chart illustrating an algorithm that can be carried out by a slave device that is in communication with a master device.
• Fig. 7 is a flow chart illustrating an algorithm that can be carried out by a master device that is in communication with one or more devices.
• An implantable medical device generally refers to any medical device that can be implanted in a human body to perform one or more of a sensing function or a therapeutic function.
• an IMD may be operable to sense a physiologic parameter, such as blood pressure, temperature, posture, blood sugar level, or others.
• An IMD may be operable to provide therapy, such as, but not limited to, pulses for rhythm management in a patient's heart.
• an IMD may provide other functions, such as communications functions.
• Embodiments described herein generally provide for communication between a master device and one or more implanted medical devices, which are configured as slave devices.
• the master device itself may also be implanted in the patient. More specifically, multiple implanted slave devices can be addressed by the master device.
• a local identifier is a locally unique address that is assigned to a slave device by the master device. For example, in a system of multiple slave devices implanted in a patient's body, each slave device can be assigned a local identifier that is locally unique to the slave device. The local identifiers can then be used by the master device to direct communications (e.g., commands or data) to the slave devices.
• each local identifier is composed of substantially fewer bits than a conventional globally unique IMD identifier, such as a device serial number.
• the local identifier can be selected from one communication session to the next.
• the local identifier can be variable or static from one communication session to the next.
• globally unique device identifiers such as manufacturer's serial numbers
• Permanent device identifiers such as serial numbers
• a local identifier bit representation can be shorter, spanning only the number of unique devices likely to be implanted in any single human body.
• a device serial number is composed of twenty or more bits.
• Device serial numbers can be considered to be globally unique, because the likelihood of duplication of any one serial number is very small due to the length of the serial number.
• a local identifier requires fewer bits and can be variable.
• local identifiers are composed of a number of bits sufficient to uniquely identify each of multiple slave IMDs implanted in a patient. As such, for example, but without limitation, a local identifier may require only between two and five bits to address each slave IMD within a patient.
• each slave IMD executes a state machine that facilitates coordinated communication with the master device.
• a state machine a slave device transitions from a reset state through an awake state to an eventual session state or suspend state, before returning to the reset state following communication session activity.
• slave devices can also enter a charge state, in which a device battery is charged.
• the master device can cause a slave device to enter the awake state by sending a wakeup command to the slave device.
• a communication session between a master and a slave generally refers to a period of interaction that spans from the time the slave device wakes up until the slave device returns to the reset state.
• a master device can maintain simultaneous communication sessions with multiple slave devices.
• data security is insured by including the local identifier in each command (master to slave) and each response (slave to master).
• the slave devices are configured to timeout after a specified time of no communication with the master device.
• the master device can be configured to periodically establish (or reestablish) communications with the slave devices, in order to avoid timeout of the slave devices.
• one or more slave devices can be allowed to timeout, or the slave devices may be sent a command to cause the slave devices to enter a low power consumption state and/or a noncommunicative state.
• the term "address” refers to the act of directing a communication to a medical device. Addressing a communication to a medical device may involve, for example, transmitting a message that includes a logical address or identifier associated with the medical device, such that the medical device recognizes the message as being directed at the medical device. [0025] When the term “address” is used as a noun, “address” refers to a logical identifying location among one or more medical devices. An address is typically used to direct communications to a selected medical device. For example, a local address distinguishes a medical device in a system of medical devices, such that commands can be sent to a particular medical device. An identifier may be viewed as a type of address because an identifier can be used to direct a communication to an associated device.
• the term "communication" refers to a set of data that can be transmitted or received.
• the set of data can be of any type.
• a communication can refer to a message (e.g., a status message) or a command.
• Fig. 1 illustrates a human body 100 with an IMD, such as a physiologic sensor device 102, implanted in a vessel of the circulatory system of the body 100, and another sensor device 104 located in an abdominal area of the human body 100.
• the sensor devices 102, 104 are operable to measure parameters, such as blood pressure, and blood glucose.
• a master device 106 is also implanted in the human body 100.
• the master device 106 is in communication with the sensor devices 102, 104. More specifically, the master device 106 is configured to send commands to, and receive data from, the sensor devices 102, 104.
• the sensor device 102 and sensor device 104 are examples of slave devices, because they respond to commands from the master device 106.
• the master device 106 may be a therapeutic or nontherapeutic device.
• the master device 106 may or may not include a sensor for performing sensory functions, and may or may not be operable to administer therapy to the patient 100.
• Fig. 1 illustrates only one possible arrangement of the master device and slave devices.
• multiple slave devices can be attached to an anchoring mechanism at a single location in the body.
• two sensor devices can be attached to a compressible retention device, and thereby anchored at a selected location. Particular embodiments of this type are shown and described in commonly owned and concurrently filed U.S. Patent Application Serial No.
• Fig. 2 is a schematic diagram 200 that more generally illustrates a system of medical devices including a master device 202 and one or more slave devices 206(n), wherein n ranges from one to M. Local identifiers are assigned and communicated to one or more of the slave devices 206(n). In the case of M less than or equal to eight, each local identifier can be composed of three bits.
• the master device 202 assigns local identifiers to slave devices 206(1), 206(3), 206(4), and 206(6).
• slave devices 206(1), 206(3), 206(4), and 206(6) assigns local identifiers to slave devices 206(1), 206(3), 206(4), and 206(6).
• Fig. 3 is a functional block diagram illustrating functional components of a slave device 300 in accordance with one embodiment.
• the components of the slave device 300 are housed in a casing composed of a biocompatible material.
• the slave device 300 includes a processor 302, a communication module 304, a sensor 306 and/or a therapy module 318, a battery 308, and memory 310, which are in operable communication with each other (e.g., via a bus or circuit board traces).
• Processor 302 may be any of a variety of processor as may be known in the art.
• processor 302 may be a microprocessor, microcontroller, a digital signal processor, or application specific integrated circuit (ASIC).
• processor 302 has relatively low power requirements, and can implement basic processes, such as a simple state machine (e.g., state machine 500, Fig. 5).
• Communication module 304 includes a receiver and transmitter (not shown) for communicating with another device, such as a master device.
• the receiver and/or the transmitter can be disabled and enabled, depending on the state of the slave device 300.
• the communication module 304 can communicate using any of a variety of wired and/or wireless communication technologies, including, but not limited to, acoustic or radio frequency (RF).
• communication module 304 is connected to leads 312, through which communication module 304 can communicate with another device, such as a master device.
• RF radio frequency
• Sensor 306 is operable to sense a specified physiologic parameter, such as, but not limited to, blood pressure.
• Memory 310 includes volatile memory 314 and nonvolatile memory 316.
• Volatile memory 314 is typically random access memory (RAM).
• nonvolatile memory 316 includes electrically erasable programmable read only memory (EEPROM).
• Memory 308 can include processor 302 executable instructions to cause processor 302 to carry out a process. Battery 308 provides power to the components of the slave device 300. In some embodiments, battery 308 is rechargeable.
• Fig. 4 is a functional block diagram illustrating functional components of a master device 400 in accordance with one embodiment.
• the components of the master device 400 are housed in a casing composed of a biocompatible material.
• the master device 400 includes a processor 402, a communication module 404, a battery 408, and memory 410, which are in operable communication with each other.
• Processor 402 may be any of a variety of processor as may be known in the art.
• processor 402 may be a microprocessor, microcontroller, a digital signal processor, or application specific integrated circuit (ASIC).
• ASIC application specific integrated circuit
• Communication module 404 includes a receiver and transmitter (not shown) for communicating with one or more slave devices.
• the communication module 404 can communicate using any of a variety of wired and/or wireless communication technologies, including, but not limited to acoustic or radio frequency (RF).
• communication module 404 is connected to leads 412, through which communication module 404 can communicate via wire with one or more slave devices.
• RF radio frequency
• a preferred embodiment of the communication module 404 communicates via wireless communication, which obviates the need for the optional leads 412.
• memory 410 in the master device 400 can include volatile memory 414 and nonvolatile memory 416.
• Volatile memory 414 is typically random access memory (RAM).
• nonvolatile memory 416 includes electrically erasable programmable read only memory (EEPROM).
• Memory 410 can include processor 402 executable instructions to cause processor 402 to carry out a process.
• Various data may be stored in nonvolatile memory 416. For example, prior to deployment, globally unique serial numbers of slave devices that the master device 400 will command, are stored in nonvolatile memory. Using the serial numbers, the master device 400 can initially address the slave devices.
• Battery 408 provides power to the components of the master device 400. In some embodiments, battery 408 is rechargeable.
• Fig. 5 is a state diagram illustrating a state machine 500 that can be implemented in a slave device implanted in a patient, and in communication with a master device.
• the state machine 500 includes a finite number of logical states, or modes, in which each of the slave machines can operate. At any particular time, the slave machines may be in the same or different states, depending on what commands or signals, if any, each of the slave machines has received from the master device.
• exemplary commands are discussed, which can be issued by the master device, and can cause the slave devices to transition among the states.
• the master device is configured to generate commands for transmission to slave devices. All slaves recognize and react to a wake-up command 513 that a master employs to simultaneously transition all local devices into the Awake state 504. Two commands that transition individual slave devices to the Session state 506 or the Suspend state 508 are referred to here as, "Single Device Session” (SDS) 512, and “Multiple Device Session” (MDS) 511.
• SDS Single Device Session
• MDS Multiple Device Session
• commands for master-to-slave interaction include data read and write commands, commands to prompt actions to be performed within individual slaves, and commands to transition slave devices to the Reset state 502.
• each slave device is configured to "timeout” and enter a nonresponsive or noncommunicative, low power mode (referred to as a Suspend state 508, discussed below) if the slave device has not received a command within a predetermined length of time.
• a Suspend state 508 a nonresponsive or noncommunicative, low power mode
• the identify (ID) command is used to identify a selected slave device among a plurality of slave devices, and cause the selected slave device to associate itself with an assigned local address or local identifier.
• the ID command format includes a long identifier (e.g., 20 - 64 bits), such as a device serial number, which is permanent and globally unique, and a local address.
• the local address is a locally unique identifier that is represented with fewer bits than the long identifier.
• the term "locally unique" means unique among a set of slave devices implanted in, or otherwise carried by, a single patient.
• the local address can be dynamically assigned during a communication session, and therefore can be variable across communication sessions, or the local address can be static across communication sessions.
• some local addresses may be kept static (e.g., by writing them to nonvolatile memory), while others may be allowed to change across communication sessions.
• the local address can be any number of bits in length, and in some embodiments ranges from two to five bits, depending on the number of slave devices in a medical device system implanted in a patient. For example, in some embodiments, each local address is composed of three bits, which allows for unique identification of up to seven slave devices.
• the master device can use the local addresses to address commands to the slave devices, without using the globally unique long device identifier.
• commands discussed herein can be addressed to a selected slave device with the local address assigned to the selected slave device.
• the assigned local addresses may be used within a single communication session, and/or during subsequent communications sessions.
• the local address is stored in nonvolatile memory of a slave device so that the local address can be used when the slave device powers up later.
• the master device controls whether and when local identifiers are stored to nonvolatile memory in the slave devices.
• the local address After a local address is stored to nonvolatile memory, the local address will be available immediately upon exiting the Reset state 502, and the ID command with the globally unique identifier does not need to be used.
• the slave device will also transmit the local identifier in all responses to the master device to insure integrity on all commands and responses.
• the slave device starts in a Reset state 502.
• the Reset state 502 is the default state because the slave device reverts to the Reset state 502 from other states under certain conditions. For example, when in either the Awake state 504 or the Session state 506, the slave device will transition to the Reset state 502 if a specified command is received. As another example, when in any of the Awake state 504, Suspend state 508, or Session state 506, the device transitions to the Reset state 502 after a finite time has passed and no command has been received from the master and the slave device has not transmitted any data.
• the Reset state 502 is a low power state, in which only certain components are enabled in order to reduce power consumption.
• the slave device may have a receiver and minimal circuitry or processing components enabled to receive a signal from the master device.
• the slave device exits the Reset state 502 when it receives a "wake-up" signal or pulse from the master device.
• the wake-up pulse is a signal that is broadcast by the master device and is recognized by each of the slave devices. Upon receiving a wake-up pulse from the master device, each slave device transitions into an Awake state 504.
• each slave device waits to be addressed by the master device.
• the master device follows the wake-up pulse with a command intended for a single slave device.
• the single slave device can be addressed at least in one of the following three ways:
• ⁇ a universal identifier, represented using the same number of bits as the local identifier.
• a globally unique slave device address (e.g., a serial number) can be contained in an identification (ID) command that also includes an assigned local identifier that can be used later.
• ID identification
• a universal identifier is an address that is associated by default with all manufactured slave devices. All devices implanted within a patient are a subset of this population. As such, a slave device that receives a command addressed with the universal identifier will act on the command, unless the slave device has been assigned a different local identifier. As a result, when a command is sent with the universal identifier, more than one slave device could potentially act on the command.
• a universal identifier can be used in cases when a slave device has not been assigned a particular local identifier.
• the universal identifier is used when one and only one slave device is in a data transfer state (e.g., Awake state 504, or Session state 506) and all other devices are either not present within the body, or have been assigned a local identifier.
• a slave that transitions to the Session state 506 with the universal identifier may have restricted operations in the Session state 506. For example, writes to nonvolatile memory may be blocked.
• a slave device when a slave device is in the Awake state 504, and a local identifier has been assigned to it, commands from the master device are addressed to the slave device using the slave device's associated local identifier.
• each slave device determines validity of the command and whether the command is intended for that particular slave device. Validity can be based on a number of factors, such as, but not limited to, a cyclic redundancy check (CRC).
• CRC cyclic redundancy check
• the slave device checks the local identifier in the command to determine if the command is intended for it.
• a slave device After a wake-up event from the Reset state 502, a slave device will stay in the Awake state 504 until a reset/sleep command is received, a timeout occurs, or a command is received that has a matching identifier (globally unique, local, or universal).
• a timeout is an interval of time (T s i ee p) during which no master device commands have been received and the slave has not transmitted data.
• the slave device If a command is received for which the address does not match and the command is not a Multiple Device Session command 511 , the slave device enters a Suspend state 508. If a Multiple Device Session command is received that does not have a matching address, the slave device remains in the Awake state 504. If a command is received that has a matching address, the slave device enters the Session state 506. [0052] In accordance with one embodiment, among others, the operation of a slave device is the same in the Session state 506 as it is in the Awake state 504, except that the slave device will not enter the Suspend state 508 directly from the Session state 506 when not addressed.
• the Session state 506 can be used by the master device to communicate with more than one slave device during a communication session.
• MDS Multiple Device Session
• the selected slave device enters the Session state 506; but, the non-selected slave devices remain in the Awake state 504.
• the master device can transmit multiple MDS commands to cause more than one slave device to enter the Session state 506.
• the master In order to communicate with a single selected slave device during a communication session, the master initially sends any command other than the Multiple Device Session command with the local identifier of the selected slave, immediately following the wake-up command, when the slave devices are in the Awake state 504. In response, the other slave devices enter the Suspend state 508, while the selected slave device enters the Session state 506. [0054] When a slave device is in Suspend state 508, the slave device will enter a very low current mode that blocks or blanks the input receiver. As a result, a slave device in Suspend state 508 cannot be addressed by the master device. After a programmable time interval, the slave device will re-enable the input receiver and enter the Reset state 502. In some embodiments, the programmable time interval ranges from 15 to 20 seconds; however, other time intervals may be used, depending on the particular implementation.
• Various embodiments include a Charge state 510.
• the Charge state 510 is a passive state in which the slave device charges a battery.
• the Charge state 510 may be entered when the slave device detects a continuous wave (CW) signal that is recognized as a charge signal.
• the CW charge signal may be generated by the master device, or another device, such as a charger that is external to the patient's body.
• the slave device can minimize power usage, for example, by disabling all the components except the components that are necessary for charging the battery.
• the CW charge signal is no longer present, the slave device enters the Reset state 502.
• Fig. 6 is a flow chart illustrating an algorithm 600 that can be carried out by a slave device that is in communication with a master device.
• the slave device whenever the slave device receives a command, the slave device performs certain validation operations to validate the command.
• validation may include performing a cyclic redundancy check (CRC) using a CRC value included in the command, and/or checking that a command type specified in the command corresponds to the format of the command.
• CRC cyclic redundancy check
• the slave device In a power-on operation 602, the slave device enables one or more components or portions of components in the slave device, increasing slave device power consumption, depending on the embodiment.
• the receiver of a communication module is enabled to receive communications from the master device. After powering on, the slave device waits for a wake-up signal from the master device. In a receiving operation 604, the receiver receives the wake-up signal from the master device.
• a waiting operation 606 the slave device waits to be addressed by the master device.
• the slave device can be addressed in several ways: with a long device ID, a local identifier, or a universal identifier.
• the slave device is addressed with a command, such as one of the commands described above.
• the slave device also starts a timer counting for a specified time (e.g., Ttimeout), which will be used to determine whether a timeout interval has passed.
• Ttimeout a specified time (e.g., Ttimeout)
• a query operation 608 determines whether the specified timeout time has passed. If the timeout time has not elapsed, the algorithm 600 branches "No" and returns to the waiting operation 606. If the timeout time has elapsed, the algorithm 600 branches "Yes" to the power on operation 602.
• the slave device receives a command sent by the master device.
• the slave device checks the command type. If the command type is an identification command, the algorithm 600 branches "ID Command" to query operation 612.
• the slave device determines whether the long device ID included in the ID command matches the slave device's permanent, globally unique identifier. If the global device IDs do match, the algorithm branches "Yes" to an accepting operation 614.
• the local identifier included in the command is saved in volatile memory and an acknowledgment response is transmitted to the master device.
• the algorithm returns to the waiting operation 606, resets the timeout timer, and awaits another command. If, however, the query operation 612 determines that the ID in the ID command does not match the slave device's global identifier, the algorithm 600 branches "No" to the query operation 608, and continues to count down from the timeout time. [0061] If in the receiving operation 610 it is determined that the command is any type of command other than an ID command, the algorithm 600 takes branch "Other Command" to another query operation 616.
• the slave device determines whether the local identifier of the command matches the local identifier of the slave device that received the command. If it is determined that the local identifier in the received command does not match the local identifier of the slave device, the algorithm 600 branches "No" to another query operation 618. In query operation 618, the slave device determines whether the command is a Multiple Device Session command.
• the algorithm branches "Yes" to acknowledging operation 620.
• Acknowledging operation 620 transmits an acknowledgment response and resets the timer. From the acknowledging operation 620, the algorithm 600 returns to the waiting operation 606 to await another command.
• the algorithm branches "No" to a disabling operation 622.
• Disabling operation 622 disables the receiver of the slave device, so that the slave device will not receive communications from the master device.
• the slave device then enters the Suspend state, in which power consumption is minimized. While in the Suspend state, the slave device performs a counting operation 626, in which the slave device counts for a specified length of time. After the counting operation 626, the algorithm returns to the reset state in the resetting operation 602.
• the algorithm branches "Yes" to another query operation 628.
• the query operation 628 determines the command type.
• the command type can be determined by checking a command type field in the received command.
• the algorithm branches along the "MDS or SDS" path to an acknowledge (Ack) operation 630.
• Ack operation 630 an acknowledgment response is issued and the timer is reset.
• the algorithm returns to the waiting operation 606 to await another command.
• the command is determined to be another command type
• the algorithm branches "Data Transfer" to a performing operation 632.
• performing operation 632 the slave device performs the specified command. For example, if the command is a read command, the slave device reads data from the requested memory location and transmits the contents of that memory location to the master device.
• the slave device If the command is a write command, the slave device writes the specified data to the specified location in memory and sends an acknowledgment response. If in the query operation 628, it is determined that the command is a Reset/Sleep command, the algorithm branches "Reset" and returns to the resetting operation 602.
• Fig. 7 is a flow chart illustrating an algorithm 700 that can be carried out by a master device that is in communication with one or more slave devices in an implanted medical device system.
• the master device reads one or more globally unique IDs associated with slave devices in the system.
• the master device determines whether local identifiers have been assigned to one or more selected slave devices.
• the master device assigns local identifiers to one or more selected slave devices.
• the master device issues a wake-up signal to the slave devices, causing the slave devices to exit a low power reset state.
• the master device In a generating operation 710, the master device generates one or more ID commands for one or more selected slave devices that do not have assigned local identifiers.
• the master device communicates the one or more ID commands to identify the slave devices and to transmit the assigned local identifiers. After the communicating operation 712, the master device may address future commands to selected slave devices using the local identifiers, without using the globally unique, long device ID. In some embodiments, the master device issues a subsequent command to instruct the slave devices to store the local identifier to a specified location in nonvolatile memory, so that the local identifier can be used in subsequent communication sessions. [0068] Various modifications and additions can be made to the exemplary embodiments discussed without departing from the scope of the present invention.

Applications Claiming Priority (3)

Publications (1)

Family

ID=38963150

Family Applications (2)

Family Applications After (1)

Country Status (5)

Families Citing this family (15)

Family Cites Families (15)

• 2007
  • 2007-07-20 CN CN200780025727.3A patent/CN101484070B/zh not_active Expired - Fee Related
  • 2007-07-20 JP JP2009521025A patent/JP5026519B2/ja not_active Expired - Fee Related
  • 2007-07-20 WO PCT/US2007/074020 patent/WO2008011592A2/en active Application Filing
  • 2007-07-20 JP JP2009521026A patent/JP5131272B2/ja not_active Expired - Fee Related
  • 2007-07-20 EP EP07813183A patent/EP2043512A2/de not_active Withdrawn
  • 2007-07-20 EP EP07813182.8A patent/EP2043513B1/de not_active Not-in-force
  • 2007-07-20 AU AU2007275030A patent/AU2007275030B2/en not_active Ceased
  • 2007-07-20 WO PCT/US2007/074021 patent/WO2008011593A2/en active Application Filing
• 2010
  • 2010-09-16 AU AU2010221815A patent/AU2010221815B2/en not_active Ceased

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events