Granted Patent B2

US 12,395,429 · App. 18/743,658 · Granted Aug 19, 2025

Inventors: Prakash Kumar Arvind Jha (San Diego, CA); James Cudney (Santee, CA); Benjamin Herr (Kelso, WA); Mark I. Lee (Poway, CA); Matteo D. Picinich (Temecula, CA)

Assignee: ICU Medical, Inc.

H04L45/74G16H20/17G16H40/63G16H40/67H04L45/302H04L69/16H04L69/162H04L69/165H04L69/32

Abstract

Claims (28)

1. A medical device communication system for connecting a first medical device system with a second medical device system, the medical device communication system comprising a controller configured to:

receive a first message comprising a request for an address from a first medical device system;

determine in a stored table that there is no entry corresponding to the first medical device system;

generate a connection identifier for the first medical device system based on the determination; and

transmit the connection identifier to the first medical device system, wherein the first medical device system is further configured to update its identity with the connection identifier.

2. The communication system of claim 1 , wherein the controller is further configured to facilitate transmission of a second message from the first medical device system to an additional hardware, wherein the first medical device system and the additional hardware are not directly connected.

3. The communication system of claim 2 , wherein the second message is transferred between a plurality of message layers by copying a pointer and without copying said second message itself.

4. The communication system of claim 2 , wherein a session layer communication is made independent of bus topology.

5. The communication system of claim 1 , wherein the controller is further configured to transmit the connection identifier to a second medical device system that replaces the first medical device system.

6. The communication system of claim 1 , wherein a fragmented message is reassembled into a complete message in an application buffer.

7. The communication system of claim 1 , wherein the controller is further configured to:

determine that a size of data to transfer is larger than a predetermined fragmentation value; and

pack said data in a plurality of messages independent of an underlying data bus width.

8. The communication system of claim 1 , wherein the controller is further configured to request memory from a buffer comprising non-uniform sizes.

9. The communication system of claim 1 , wherein the first medical device system is connected with the controller without altering an application of the first medical device system.

10. The communication system of claim 1 , wherein the controller manages connection requests from a plurality of medical device systems.

11. A method for connecting hardware components of an medical device system, the method comprising:

transmitting a first connection identifier to a controller of a first medical device system responsive to a first message corresponding to a first request for an address from the first medical device system;

receiving a second message corresponding to a second request for an address from a second medical device system;

determining that the second medical device system has replaced the first medical device system;

changing an association of the first connection identifier from the first medical device system to the second medical device system;

transmitting the first connection identifier to the second medical device system, wherein the second medical device system is further configured to update its identity with the first connection identifier.

12. The method of claim 11 , further comprising facilitating transmission of a second message from the first medical device system to an additional hardware, wherein the first medical device system and the additional hardware are not directly connected.

13. The method of claim 11 , further comprising transmitting messages between hardware components by copying a pointer and without copying the messages.

14. The method of claim 11 , wherein a session layer communication is made independent of bus topology.

15. The method of claim 11 , wherein a fragmented message is reassembled into a complete message in an application buffer.

16. The method of claim 11 , further comprising determining that a size of data to transfer is larger than a predetermined fragmentation value and packing said data in a plurality of messages independent of an underlying data bus width.

17. The method of claim 11 , further comprising requesting memory from a buffer comprising non-uniform sizes.

Assignments (1)

Continuity (7)

References Cited (400)