MITIGATING DEVICE POWER DRAIN ASSOCIATED WITH STALLED TELEMETRY SESSIONS

• US 20190070423A1
• Filed: 11/07/2018
• Published: 03/07/2019
• Est. Priority Date: 02/28/2017
• Status: Active Grant

• Current Assignee: Medtronic Incorporated (Medtronic Plc)
• Original Assignee: Medtronic Incorporated (Medtronic Plc)
• Inventors: KIVI, Gary P., WINE, Nicholas C., YODER, Matthew R., ZHANG, Bo
• Granted Patent: US 10,639,487 B2
• Time in Patent Office: Days
• CPC Class Codes: A61B 5/0002 Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network A61B5/07 takes precedence; transmission systems for measured values G08C; transmission H04B; transmission of digital information H04L; wireless communication networks H04W
• CPC Class Codes: A61B 5/0022 Monitoring a patient using a global network, e.g. telephone networks, internet
• CPC Class Codes: A61B 5/0031 Implanted circuitry
• CPC Class Codes: A61B 5/021 Measuring pressure in heart or blood vessels A61B5/0205 takes precedence
• CPC Class Codes: A61B 5/0215 by means inserted into the body catheters A61M25/00
• CPC Class Codes: A61B 5/6801 specially adapted to be attached to or worn on the body surface
• CPC Class Codes: A61N 1/056 Transvascular endocardial electrode systems
• CPC Class Codes: A61N 1/36 for stimulation
• CPC Class Codes: A61N 1/36007 of urogenital or gastrointestinal organs, e.g. for incontinence control
• CPC Class Codes: A61N 1/36014 External stimulators, e.g. with patch electrodes external pacemakers A61N1/3625
• CPC Class Codes: A61N 1/36062 Spinal stimulation
• CPC Class Codes: A61N 1/365 controlled by a physiological parameter, e.g. heart potential evoked response A61N1/371
• CPC Class Codes: A61N 1/37276 characterised by means for reducing power consumption during telemetry
• CPC Class Codes: A61N 1/3956 Implantable devices for applying electric shocks to the heart, e.g. for cardioversion
• CPC Class Codes: A61N 1/3962 in combination with another heart therapy
• CPC Class Codes: H04L 43/0888 Throughput
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04Q 2209/43 using wireless personal area networks [WPAN], e.g. 802.15, 802.15.1, 802.15.4, Bluetooth or ZigBee
• CPC Class Codes: H04Q 2209/47 using RFID associated with sensors
• CPC Class Codes: H04Q 9/00 Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom
• CPC Class Codes: H04Q 9/02 : Automatically-operated arrangements
• CPC Class Codes: H04W 76/30 : Connection release
• CPC Class Codes: H04W 76/38 : triggered by timers

Abstract

Systems, apparatus, methods and computer-readable storage media that mitigate device power drain associated with stalled telemetry sessions are provided. In one embodiment, a first device includes a memory and a processor that executes executable components stored in the memory. The executable components include a communication component configured to receive a communication request from a second device via a telemetry communication link established between the first and second devices. The communication request can comprise a request for data. The executable components can also comprise a throughput monitoring component configured to monitor uplink throughput measuring successful transmission of the data by the first device to the second device via the telemetry communication link based on reception of the communication request. The communication component is configured to terminate the telemetry communication link based on the uplink throughput being below a threshold value.

Claims

1. A device comprising:

a memory that stores executable components; and

a processor that executes the executable components stored in the memory, wherein the executable components comprise;

a communication component configured to receive a communication request from a second device via a telemetry communication link established between the device and the second device, wherein the communication request comprises a request for data from the device; and

a throughput monitoring component configured to monitor uplink throughput measuring successful transmission of the data by the device to the second device via the telemetry communication link, wherein the communication component is further configured to terminate the telemetry communication link based on the uplink throughput being below a threshold value.

2. The device of claim 1, wherein the throughput monitoring component is configured to determine the uplink throughput based on a number of application data packets comprising the data that are transmitted by the device to the second device via the telemetry communication link per connection interval.

3. The device of claim 1, wherein the throughput monitoring component is configured to determine the uplink throughput based on time delays between successful transmissions of data packets comprising the data by the device to the second device via the telemetry communication link.

4. The device of claim 1, wherein the threshold value varies based on a type of the data.

5. The device of claim 1, wherein the threshold value varies based on a type of telemetry session associated with the communication request.

6. The device of claim 1, wherein the data comprises a first type of data and wherein the uplink throughput comprises first uplink throughput, and wherein the throughput monitoring component is configured to monitor the first uplink throughput independently from second uplink throughput measuring successful transmission of a second type of data by the device to the second device via the telemetry communication link.

7. The device of claim 1, wherein the communication component is further configured to terminate the telemetry communication link based on the uplink throughput being below the threshold value for a defined period of time following reception of the communication request.

8. The device of claim 7, wherein the defined period of time varies based on a type of telemetry session associated with the communication request.

9. The device of claim 1, wherein the transmission of the data comprises transmission of one or more data packets comprising the data, and wherein the throughput monitoring component is configured to determine the uplink throughput based on whether the communication component receives one or more acknowledgment messages from the second device that indicate the second device received the one or more data packets.

10. The device of claim 1, wherein the transmission of the data comprises transmission of one or more data packets comprising the data, and wherein the throughput monitoring component is configured to determine the uplink throughput based on timing of reception, by the communication component, of one or more acknowledgment messages from the second device that indicate the second device received the one or more data packets.

11. A device comprising:

a memory that stores executable components; and

a processor that executes the executable components stored in the memory, wherein the executable components comprise;

a communication component configured to transmit data to a second device via a telemetry communication link established between the device and the second device; and

a throughput monitoring component configured to monitor uplink throughput measuring successful transmission of the data by the device to the second device, wherein the communication component is further configured to terminate the telemetry communication link based on the uplink throughput being below a threshold value.

12. The device of claim 11, wherein the throughput monitoring component is configured to determine the uplink throughput based on at least one of a number of application data packets comprising the data that are successfully transmitted by the device per connection interval or time delays between successful transmissions of data packets comprising the data by the device.

13. The device of claim 11, wherein the threshold value varies based on a type of the data.

14. The device of claim 11, wherein the communication component is further configured to terminate the telemetry communication link based on the uplink throughput being below the threshold value for a defined period of time following establishment of the telemetry communication link.

15. The device of claim 15, wherein the defined period of time varies based on a type of telemetry session associated with establishment of the telemetry communication link.

16. A method comprising:

receiving, by a first device, a data request from a second device via a telemetry communication link established between the first device and the second device, wherein the data request comprises a request for data from the first device;

monitoring, by the first device, uplink throughput measuring successful transmission of the data by the first device to the second device via the telemetry communication link; and

terminating, by the first device, the telemetry communication link based on the uplink throughput being below a threshold value.

17. The method of claim 16, wherein the monitoring the uplink throughput comprises determining the uplink throughput based on number of application data packets comprising the data that are successfully transmitted by the first device per connection interval.

18. The method of claim 16, wherein the monitoring the uplink throughput comprises determining the uplink throughput based on time delays between successful transmissions of data packets comprising the data by the first device.

19. The method of claim 16, wherein the threshold value varies based on a type of the data.

20. The method of claim 16, wherein the monitoring comprises monitoring the uplink throughput measuring successful transmission of the data based on a type of the data.

21. The method of claim 16, wherein the terminating comprises terminating the telemetry communication link based on the uplink throughput being below the threshold value for a defined period of time following reception of the data request.

22. The method of claim 21, wherein the defined period of time varies based on a type of telemetry session associated with the data request.