IP Library Granted Patent US 9,154,219
Granted Patent B2
US 9,154,219 · App. 14/715,915 · Granted Oct 6, 2015

Communication for implantable medical devices

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,154,219
App. No.
14/715,915
Granted
Oct 6, 2015
Kind
B2
Abstract

Systems and methods for communication between an implantable medical device and an external device. Data blocks are generated and transmitted between the implantable device and the external device. The data blocks include a first flag indicating whether the data block is a first data block in a message and when the data block is a subsequent data block in a multiple data block message. When the first flag indicates that the data block is a first data block in a message, the data block also contains a device ID, a command token, and message content. When the first flag indicates that the data block is a subsequent data block in a multiple data block message, the data block contains additional message content that is appended to message content from a previously received data block.

Claims (72)

1. A method of communicating between an implanted device implanted in a patient and an external device external to the patient, the method comprising:

receiving, by the implanted device, a first data block of a defined size;

monitoring the first data block for a first flag indicating whether the first data block is an initial data block in a message or a subsequent data block in a multiple data block message; and

when the first flag indicates that the first data block is the initial data block in the message, monitoring the first data block for a fixed device ID including:

comparing the fixed device ID from the first data block to one or more stored fixed device IDs, the one or more stored fixed device IDs each uniquely identifying a specific external device; and

identifying a device sending the first data block as a first authorized device when the fixed device ID from the first data block matches a stored fixed device ID of the one or more stored fixed device IDs, the stored fixed device ID corresponding to the first authorized device.

2. The method of claim 1 , comprising storing message content from the first data block to a memory of the implanted device when the first flag indicates that the first data block is the initial data block in the message.

3. The method of claim 2 , comprising appending message content from the first data block to message content stored in the memory from a previously received data block when the first flag indicates that the first data block is a subsequent data block in a multiple data block message.

4. The method of claim 1 , comprising monitoring the first data block for a command token indicating the type of message that is being received when the first flag indicates that the first data block is the initial data block in the message.

5. The method of claim 4 , wherein:

the implanted device monitors the first data block for the first flag by monitoring a first byte in the first data block;

when the first flag indicates that the first data block is the first data block in the message, the implanted device monitors the first data block for the fixed device ID by monitoring a second byte, a third byte, and a fourth byte in the first data block; and

when the first flag indicates that the first data block is the initial data block in the message, the implanted device monitors the first data block for the command token by monitoring a fifth byte and a sixth byte in the first data block.

6. The method of claim 1 , comprising:

receiving, by the implanted device, a second data block of the defined size;

monitoring the second data block for a first flag indicating whether the second data block is an initial data block in a second message or a subsequent data block in the same message as the first data block; and

when the first flag of the second data block indicates that the second data block is the initial data block in a second message, monitoring the second data block for a fixed device ID, including:

comparing the fixed device ID from the second data block to the one or more stored fixed device IDs;

identifying the device sending the second data block as the first authorized device when the fixed device ID from the second data block matches the stored fixed device ID corresponding to the first authorized device; and

identifying the device sending the second data block as a second authorized device when the fixed device ID from the second data block matches a stored fixed device ID of the one or more stored fixed device IDs, the stored fixed device ID corresponding to the second authorized device.

7. The method of claim 1 , comprising:

monitoring the first data block for a checksum value; and

when the first flag indicates that the first data block is the initial data block in the message, comparing the checksum value from the first data block to a checksum value calculated by the implanted device indicative of the data in the first data block.

8. The method of claim 1 , comprising disregarding the first data block when the first flag indicates that the first data block is a subsequent data block in a multiple data block message and when the implanted device has not received a previous data block in the multiple data block message.

9. The method of claim 1 , wherein receiving, by the implanted device, a first data block of a defined size includes:

receiving a radio-frequency signal by a communication module included in the implanted device; and

extracting the first data block from the radio-frequency signal.

10. An implantable device comprising:

a housing;

a wireless communication module within the housing;

a processor disposed within the housing; and

a memory configured to store executable instructions that, when executed by the processor, cause the implantable device to:

receive a first data block of a defined size;

monitor the first data block for a first flag indicating whether the first data block is an initial data block in a message or a subsequent data block in a multiple data block message;

when the first flag indicates that the first data block is the initial data block in the message, monitor the first data block for a fixed device ID, including:

comparing the fixed device ID from the first data block to one or more stored fixed device IDs, the one or more stored fixed device IDs each uniquely identifying a specific external device; and

identifying a device sending the first data block as a first authorized device when the fixed device ID from the first data block matches a stored fixed device ID of the one or more stored fixed device IDs, the stored fixed device ID corresponding to the first authorized device.

11. The implantable device of claim 10 , wherein the executable instructions, when executed by the processor, cause the implantable device to monitor the first data block for a command token indicating the type of message that is being received when the first flag indicates that the first data block is the initial data block in the message.

12. The implantable device of claim 10 , wherein the executable instructions, when executed by the processor, cause the implantable device to store message content from the first data block to the memory when the first flag indicates that the first data block is the initial data block in the message.

13. The implantable device of claim 10 , wherein the executable instructions, when executed by the processor, cause the implantable device to append message content from the first data block to message content stored in the memory from a previously received data block when the first flag indicates that the first data block is a subsequent data block in a multiple data block message.

14. The implantable device of claim 10 , wherein the executable instructions, when executed by the processor, cause the implantable device to:

receive a second data block of the defined size;

monitor the second data block for a first flag indicating whether the second data block is an initial data block in a second message or a subsequent data block in the same message as the first data block; and

when the first flag of the second data block indicates that the second data block is the initial data block in a second message, monitor the second data block for a fixed device ID, including:

comparing the fixed device ID from the second data block to the one or more stored fixed device IDs;

identifying the device sending the second data block as the first authorized device when the fixed device ID from the second data block matches the first stored fixed device ID; and

identifying the device sending the second data block as a second authorized device when the fixed device ID from the second data block matches a second stored fixed device ID from the stored list of fixed device IDs, wherein the second stored fixed device ID is different from the first stored fixed device ID, and wherein the second stored fixed device ID corresponds to the second authorized device.

15. The implantable device of claim 10 , wherein the executable instructions, when executed by the processor, cause the implantable device to:

monitor the first data block for a checksum value;

when the first flag indicates that the first data block is the initial data block in the message, compare the checksum value from the first data block to a checksum value calculated by the implantable device indicative of the data in the first data block; and

when the first flag indicates that the first data block is a subsequent data block in a multiple data block message, compare the checksum value from the first data block to a checksum value calculated by the implantable device indicative of the data in the first data block and data in at least one previously received data block of the message.

16. A method of communicating between an implanted device implanted in a patient and an external device external to the patient, the method comprising:

generating, by the external device, a first data block of a defined size, wherein generating the first data block includes:

setting a first flag in the first data block indicating whether the first data block is an initial data block in a message or a subsequent data block in a multiple data block message;

when the first data block is an initial data block in the message, including a fixed device ID in the first data block, wherein:

the fixed device ID is a pre-assigned ID that uniquely identifies the external device; and

the implanted device stores a list of approved device IDs, each uniquely identifying a different authorized device, and only responds to messages sent from authorized devices; and

transmitting, by the external device, the first data block.

17. The method of claim 16 , comprising:

including a command token in the first data block indicating the type of message when the first data block is the initial data block in the message;

including message content in the first data block when the first data block is the initial data block in the message; and

including additional message content in the first data block when the first data block is a subsequent data block in a multiple data block message.

18. The method of claim 17 , wherein generating a first data block of a defined size includes:

including the first flag in a first byte of the first data block;

when the first data block is the initial data block in the message, including the fixed device ID in a second byte, a third byte, and a fourth byte of the first data block; and

when the first data block is the initial data block in the message, including the command token in a fifth byte and a sixth byte of the first data block.

19. The method of claim 16 , comprising:

generating, by the external device, a second data block of the defined size, wherein, when the second data block is an initial data block in a second message, generating the second data block includes including the fixed device ID in the second data block, wherein the fixed device ID in the second data block is the same as the fixed device ID in the first data block; and

transmitting, by the external device, the second data block.

20. The method of claim 16 , wherein generating a first data block of a defined size includes:

calculating a checksum value; and

including the checksum value in the first data block, wherein, when the first data block is an initial data block in the message, the calculated checksum value is indicative of the data in the first data block.

Assignments (9)
PATENT SECURITY AGREEMENT Recorded Jan 30, 2023
From: CIRTEC MEDICAL CORP.
To: BMO HARRIS BANK N.A., AS COLLATERAL AGENT
Reel/Frame 062559/0098 →
RELEASE OF SECURITY INTEREST Recorded Oct 12, 2022
From: MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT)
To: GREATBATCH, INC.; GREATBATCH LTD.; ELECTROCHEM SOLUTIONS, INC.; NEURONEXUS TECHNOLOGIES, INC.; GREATBATCH-GLOBE TOOL, INC.; PRECIMED INC.; MICRO POWER ELECTRONICS, INC.
Reel/Frame 061659/0858 →
RELEASE OF SECURITY INTEREST Recorded Jan 6, 2022
From: MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT)
To: GREATBATCH, INC.; GREATBATCH LTD.; ELECTROCHEM SOLUTIONS, INC.; NEURONEXUS TECHNOLOGIES, INC.; GREATBATCH-GLOBE TOOL, INC.; PRECIMED INC.; MICRO POWER ELECTRONICS, INC.
Reel/Frame 060938/0069 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 18, 2020
From: NUVECTRA CORPORATION
To: CIRTEC MEDICAL CORP.
Reel/Frame 052185/0680 →
RELEASE OF SECURITY INTEREST Recorded Jun 23, 2016
From: MANUFACTURERS AND TRADERS TRUST COMPANY
To: GREATBATCH LTD.; GREATBATCH INC.; QIG GROUP LLC; NEURONEXUS TECHNOLOGIES, INC.; MICRO POWER ELECTRONICS, INC.; ELECTROCHEM SOLUTIONS, INC.
Reel/Frame 039132/0773 →
CHANGE OF NAME Recorded Apr 18, 2016
From: QIG GROUP, LLC
To: NUVECTRA CORPORATION
Reel/Frame 038455/0153 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 12, 2016
From: GREATBATCH LTD.
To: QIG GROUP, LLC
Reel/Frame 037810/0051 →
SECURITY INTEREST Recorded Oct 27, 2015
From: GREATBATCH, INC.; GREATBATCH LTD.; ELECTROCHEM SOLUTIONS, INC.; NEURONEXUS TECHNOLOGIES, INC.; GREATBATCH-GLOBE TOOL, INC.; PRECIMED INC.; MICRO POWER ELECTRONICS, INC.
To: MANUFACTURERS AND TRADERS TRUST COMPANY
Reel/Frame 036980/0482 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2015
From: POLEFKO, RICHARD J.; HOWARD, DAVID J.; LEYH, SCOTT G.; WILDER, STEVEN E.
To: GREATBATCH LTD.
Reel/Frame 035668/0755 →