System for communication of image information between multiple-protocol imaging devices

• US 5,630,101 A
• Filed: 11/22/1994
• Issued: 05/13/1997
• Est. Priority Date: 11/22/1994
• Status: Expired due to Term

• Current Assignee: CareStream Health Incorporated
• Original Assignee: Minnesota Mining and Manufacturing Co (3M Company)
• Inventors: Sieffert, Kent J.
• Primary Examiner(s): Teska, Kevin J.
• Assistant Examiner(s): MOHAMED, AYNI Y
• Application Number:
  US08/343,184
• Time in Patent Office: 903 Days
• Field of Search: 395/118, 395/125, 395/500
• US Class Current: 710/11
• CPC Class Codes: H04N 1/32502 in systems having a plurality of input or output devices
• CPC Class Codes: H04N 1/32512 of different type, e.g. internal and external devices
• CPC Class Codes: H04N 1/32529 of different type, e.g. internal and external devices
• CPC Class Codes: H04N 1/32561 using a programmed control device, e.g. a microprocessor
• CPC Class Codes: H04N 1/32797 Systems adapted to communicate over more than one channel, e.g. via ISDN changing transmission mode according to type of channel H04N2201/33364; multichannel or multilink communication protocols H04L69/14

Abstract

A medical imaging system for communicating image information between a plurality of different input imaging devices having different input protocols and a plurality of different output imaging devices having different output protocols takes advantage of a reusable software architecture having a plurality of functionally independent components. The individual components can be configured in a communication pipeline to communicate image information between an input imaging device and an output imaging device according to desired protocols. Each component can be interchanged with a differently configured component to facilitate communication of image information according to a different protocol, thereby reconfiguring the pipeline to achieve significant flexibility. Moreover, the software architecture is scalable to produce a plurality of communication pipelines, each of which can be configured according to desired protocols. Thus, the system of the present invention can support a different protocol by either swapping components to reconfigure a single communication pipeline, or by simply selecting an alternative among a plurality of differently configured communication pipelines in the scalable architecture. Because each of the components is isolated and functionally independent, if redesign of a component is necessary, several programmers can be allocated to the effort with little added overhead, saving time and expense. The modularity of the architecture also enables necessary modifications or corrections to be made to a single component with little impact to the overall system.

Claims

1. A software system for communicating image information between at least one of a plurality of different input imaging devices and at least one of a plurality of different output imaging devices, said software system comprising:

one or more input driver components, each of said input driver components being configured to receive image information from one of said input imaging devices, said image information being received according to one of a plurality of different input driver protocols, wherein each of said input driver protocols is specifically associated with one of said input imaging devices;

one or more input interpreter components, each of said input interpreter components being configured to generate first imaging requests based on the image information received by one of said input driver components, said first imaging requests being generated according to one of a plurality of different input interpreter protocols, wherein each of said input interpreter protocols is specifically associated with one of said input imaging devices;

one or more output interpreter components, each of said output interpreter components being configured to generate second imaging requests based on the first imaging requests generated by one of said input interpreter components, said second imaging requests being generated according to one of a plurality of different output interpreter protocols, wherein each of said output interpreter protocols is specifically associated with one of said output imaging devices;

one or more output driver components, each of said output driver components being configured to communicate the second imaging requests generated by one of said output interpreter components to one of said output imaging devices, said second imaging requests being communicated according to one of a plurality of different output driver protocols, wherein each of said output driver protocols is specifically associated with one of said output imaging devices; and

an interface executive component for defining one or more communication pipelines, each of said pipelines communicatively interconnecting one of said input imaging devices, one of said input driver components, one of said input interpreter components, one of said output interpreter components, one of said output driver components, and one of said output imaging devices.

2. The software system of claim 1, wherein:

each of said input driver components includes a first interface for communicating the image information to one of said input interpreter components according to a first base-class protocol generic to each of said input driver components and understood by each of said input interpreter components;

each of said input interpreter components includes a second interface for communicating the first imaging requests to one of said output interpreter components according to a second base-class protocol generic to each of said input interpreter components and understood by each of said output interpreter components; and

each of said output interpreter components includes a third interface for communicating the second imaging requests to one of said output driver components according to a third base-class protocol generic to each of said output interpreter components and understood by each of said output driver components.

3. The software system of claim 2, wherein each of said first base-class protocol, said second base-class protocol, and said third base-class protocol is defined according to an object-oriented hierarchy.

4. The software system of claim 2, wherein:

each of said output driver components is further configured to receive first responses to the second imaging requests from one of said output imaging devices, said first responses being received according to one of said output driver protocols;

each of said output interpreter components is further configured to generate second responses based on said first responses received by one of said output driver components, said second responses being generated according to one of said output interpreter protocols;

each of said input interpreter components is further configured to generate third responses based on said second responses generated by one of said output interpreter components, said second responses being generated according to one of said input interpreter protocols;

each of said input driver components is further configured to communicate said third responses generated by one of said input interpreter components to one of said input imaging devices, said third responses being communicated according to one of said input driver protocols; and

each of said pipelines defined by said interface executive component is a bi-directional pipeline communicatively interconnecting one of said input imaging devices, one of said input driver components, one of said input interpreter components, one of said output interpreter components, one of said output driver components, and one of said output imaging devices for hi-directional communication between one of said input imaging devices and one of said output imaging devices.

5. The software system of claim 4, wherein:

each of said output driver components includes a fourth interface for communicating the first responses to one of said output interpreter components according to a fourth base-class protocol genetic to each of said output driver components and understood by each of said output interpreter components;

the third interface of each of said output interpreter components is configured to communicate the second response to one of said input interpreter components according to said third base-class protocol genetic to each of said output interpreter components and understood by each of said input interpreter components; and

the second interface of each of said input interpreter components is configured to communicate the third response to one of said input driver components according to said second base-class protocol generic to each of said input interpreter components and understood by each of said input driver components.

6. The software system of claim 5, wherein at least one of said input imaging devices includes a medical imaging device and at least one of said output devices includes a laser imager.

7. The software system of claim 5, wherein said interface executive component defines each of said pipelines according to a client-server relationship such that each of said input interpreter components is a client of one of said input driver components, each of said input interpreter components is a client of one of said output interpreter components, each of said output interpreter components is a client of one of said output driver components, and said interface executive component is a client of each of said input driver components, each of said input interpreter components, each of said output interpreter components, and each of said output driver components.

8. The software system of claim 7, wherein communication between said input interpreter components, said input driver components, and said output interpreter components is carried out by remote procedure calls generated by said input interpreter components and executed by said input driver components and said output interpreter components, wherein communication between said output interpreter components and said output driver components is carried out by remote procedure calls generated by said output interpreter components and executed by said output driver components, and wherein communication between said interface executive component, said input driver components, said input interpreter components, said output interpreter components, and said output driver components is carried out by remote procedure calls generated by said interface executive component and executed by said input driver components, said input interpreter components, said output interpreter components, and said output driver components.

9. An imaging system having a software system for communicating image information between at least one of a plurality of different input imaging devices and at least one of a plurality of different output imaging devices, said imaging system comprising:

one or more input driver components, each of said input driver components being configured to receive image information from one of said input imaging devices, said image information being received according to one of a plurality of different input driver protocols, wherein each of said input driver protocols is specifically associated with one of said input imaging devices;

one or more input interpreter components, each of said input interpreter components being configured to generate first imaging requests based on the image information received by one of said input driver components, said first imaging requests being generated according to one of a plurality of different input interpreter protocols, wherein each of said input interpreter protocols is specifically associated with one of said input imaging devices;

one or more output interpreter components, each of said output interpreter components being configured to generate second imaging requests based on the first imaging requests generated by one of said input interpreter components, said second imaging requests being generated according to one of a plurality of different output interpreter protocols, wherein each of said output interpreter protocols is specifically associated with one of said output imaging devices;

one or more output driver components, each of said output driver components being configured to communicate the second imaging requests generated by one of said output interpreter components to one of said output imaging devices, said second imaging requests being communicated according to one of a plurality of different output driver protocols, wherein each of said output driver protocols is specifically associated with one of said output imaging devices; and

an interface executive component for defining one or more communication pipelines, each of said pipelines communicatively interconnecting one of said input imaging devices, one of said input driver components, one of said input interpreter components, one of said output interpreter components, one of said output driver components, and one of said output imaging devices.

10. The imaging system of claim 9, wherein:

each of said input driver components includes a first interface for communicating the image information to one of said input interpreter components according to a first base-class protocol generic to each of said input driver components and understood by each of said input interpreter components;

each of said input interpreter components includes a second interface for communicating the first imaging requests to one of said output interpreter components according to a second base-class protocol generic to each of said input interpreter components and understood by each of said output interpreter components; and

each of said output interpreter components includes a third interface for communicating the second imaging requests to one of said output driver components according to a third base-class protocol generic to each of said output interpreter components and understood by each of said output driver components.

11. The imaging system of claim 10, wherein each of said first base-class protocol, said second base-class protocol, and said third base-class protocol is defined according to an object-oriented hierarchy.

12. The imaging system of claim 10, wherein:

each of said output driver components is further configured to receive first responses to the second imaging requests from one of said output imaging devices, said first responses being received according to one of said output driver protocols;

each of said output interpreter components is further configured to generate second responses based on said first responses received by one of said output driver components, said second responses being generated according to one of said output interpreter protocols;

each of said input interpreter components is further configured to generate third responses based on said second responses generated by one of said output interpreter components, said second responses being generated according to one of said input interpreter protocols;

each of said input driver components is further configured to communicate said third responses generated by one of said input interpreter components to one of said input imaging devices, said third responses being communicated according to one of said input driver protocols; and

each of said pipelines defined by said interface executive component is a bi-directional pipeline communicatively interconnecting one of said input imaging devices, one of said input driver components, one of said input interpreter components, one of said output interpreter components, one of said output driver components, and one of said output imaging devices for bi-directional communication between one of said input imaging devices and one of said output imaging devices.

13. The imaging system of claim 12, wherein:

each of said output driver components includes a fourth interface for communicating the first responses to one of said output interpreter components according to a fourth base-class protocol generic to each of said output driver components and understood by each of said output interpreter components;

the third interface of each of said output interpreter components is configured to communicate the second response to one of said input interpreter components according to said third base-class protocol generic to each of said output interpreter components and understood by each of said input interpreter components; and

the second interface of each of said input interpreter components is configured to communicate the third response to one of said input driver components according to said second base-class protocol generic to each of said input interpreter components and understood by each of said input driver components.

14. The imaging system of claim 13, wherein at least one of said input imaging devices includes a medical imaging device and at least one of said output devices includes a laser imager.

15. The imaging system of claim 13, wherein said interface executive component defines each of said pipelines according to a client-server relationship such that each of said input interpreter components is a client of one of said input driver components, each of said input interpreter components is a client of one of said output interpreter components, each of said output interpreter components is a client of one of said output driver components, and said interface executive component is a client of each of said input driver components, each of said input interpreter components, each of said output interpreter components, and each of said output driver components.

16. The imaging system of claim 15, wherein communication between said input interpreter components, said input driver components, and said output interpreter components is carried out by remote procedure calls generated by said input interpreter components and executed by said input driver components and said output interpreter components, wherein communication between said output interpreter components and said output driver components is carried out by remote procedure calls generated by said output interpreter components and executed by said output driver components, and wherein communication between said interface executive component, said input driver components, said input interpreter components, said output interpreter components, and said output driver components is carried out by remote procedure calls generated by said interface executive component and executed by said input driver components, said input interpreter components, said output interpreter components, and said output driver components.

17. A software system for communicating image information between at least one of a plurality of different input imaging devices and at least one of a plurality of different output imaging devices, said software system comprising:

one or more input interface components, each of said input interface components being configured to receive image information from one of said input imaging devices, said image information being received according to one of a plurality of different input interface protocols, wherein each of said input interface protocols is specifically associated with one of said input imaging devices, and to generate first imaging requests based on the received image information, said first imaging requests being generated according to said one of said input interface protocols;

one or more output interface components, each of said output interface components being configured to generate second imaging requests based on the first imaging requests generated by one of said input interface components, said second imaging requests being generated according to one of a plurality of different output interface protocols, wherein each of said output interface protocols is specifically associated with one of said output imaging devices, and to communicate the second imaging requests generated by one of said output interface components to one of said output imaging devices, said second imaging requests being communicated according to said one of said output interface protocols; and

an interface executive component for defining one or more communication pipelines, each of said pipelines communicatively interconnecting one of said input imaging devices, one of said input interface components, one of said output interface components, and one of said output imaging devices.

18. The software system of claim 17, wherein each of said input interface components includes a first interface for communicating the first imaging requests to one of said output interface components according to a base-class protocol generic to each of said input interface components and understood by each of said output interface components.

19. The software system of claim 18, wherein base-class protocol is defined according to an object-oriented hierarchy.

20. The software system of claim 18, wherein:

each of said output interface components is further configured to receive first responses to the second imaging requests from one of said output imaging devices, said first responses being received according to one of said output interface protocols, and to generate second responses based on said first responses, said second responses being generated according to one of said output interface protocols; and

each of said input interface components is further configured to generate third responses based on said second responses generated by one of said output interface components, said third responses being generated according to one of said input interface protocols, and to communicate said third responses to one of said input imaging devices, said third responses being communicated according to one of said input interface protocols; and

each of said pipelines defined by said interface executive component is a bi-directional pipeline communicatively interconnecting one of said input imaging devices, one of said input interface components, one of said output interface components, and one of said output imaging devices for bi-directional communication between one of said input imaging devices and one of said output imaging devices.

21. The software system of claim 20, wherein each of said output interface components includes a second interface for communicating the second responses to one of said input interface components according to a second base-class protocol generic to each of said output interface components and understood by each of said input interface components.

22. The software system of claim 21, wherein at least one of said input imaging devices includes a medical imaging device and at least one of said output devices includes a laser imager.

23. The software system of claim 21, wherein said interface executive component defines each of said pipelines according to a client-server relationship such that each of said input interface components is a client of one of said output interface components, and said interface executive component is a client of each of said input interface components and each of said output interface components.

24. The software system of claim 23, wherein communication between said input interface and said output interface components is carried out by remote procedure calls generated by said input interface components and executed by said output interface components, and wherein communication between said interface executive component, said input interface components, and said output interface components is carried out by remote procedure calls generated by said interface executive component and executed by said input interface components and said output interface components.

25. An imaging system having a software system for communicating image information between at least one of a plurality of different input imaging devices and at least one of a plurality of different output imaging devices, said software system comprising:

one or more input interface components, each of said input interface components being configured to receive image information from one of said input imaging devices, said image information being received according to one of a plurality of different input interface protocols, wherein each of said input interface protocols is specifically associated with one of said input imaging devices, and to generate first imaging requests based on the received image information, said first imaging requests being generated according to said one of said different input interface protocols;

one or more output interface components, each of said output interface components being configured to generate second imaging requests based on the first imaging requests generated by one of said input interface components, said second imaging requests being generated according to one of a plurality of different output interface protocols, wherein each of said output interface protocols is specifically associated with one of said output imaging devices, and to communicate the second imaging requests generated by one of said output interface components to one of said output imaging devices, said second imaging requests being communicated according to said one of said output interface protocols; and

an interface executive component for defining one or more communication pipelines, each of said pipelines communicatively interconnecting one of said input imaging devices, one of said input interface components, one of said output interface components, and one of said output imaging devices.

26. The imaging system of claim 25, wherein each of said input interface components includes a first interface for communicating the first imaging requests to one of said output interface components according to a base-class protocol generic to each of said input interface components and understood by each of said output interface components.

27. The imaging system of claim 26, wherein said base-class is defined according to an object-oriented hierarchy.

28. The imaging system of claim 26, wherein:

each of said output interface components is further configured to receive first responses to the second imaging requests from one of said output imaging devices, said first responses being received according to one of said output interface protocols, and to generate second responses based on said first responses, said second responses being generated according to one of said output interface protocols; and

each of said input interface components is further configured to generate third responses based on said second responses generated by one of said output interface components, said third responses being generated according to one of said input interface protocols, and to communicate said third responses to one of said input imaging devices, said third responses being communicated according to one of said input interface protocols; and

each of said pipelines defined by said interface executive component is a bi-directional pipeline communicatively interconnecting one of said input imaging devices, one of said input interface components, one of said output interface components, and one of said output imaging devices for bi-directional communication between one of said input imaging devices and one of said output imaging devices.

29. The imaging system of claim 28, wherein each of said output interface components includes a second interface for communicating the second responses to one of said input interface components according to a second base-class protocol generic to each of said output interface components and understood by each of said input interface components.

30. The imaging system of claim 29, wherein at least one of said input imaging devices includes a medical imaging device and at least one of said output devices includes a laser imager.

31. The imaging system of claim 29, wherein said interface executive component defines each of said pipelines according to a client-server relationship such that each of said input interface components is a client of one of said output interface components, and said interface executive component is a client of each of said input interface components and each of said output interface components.

32. The imaging system of claim 31, wherein communication between said input interface and said output interface components is carried out by remote procedure calls generated by said input interface components and executed by said output interface components, and wherein communication between said interface executive component, said input interface components, and said output interface components is carried out by remote procedure calls generated by said interface executive component and executed by said input interface components and said output interface components.