US 5,513,328 AGranted

Apparatus for inter-process/device communication for multiple systems of asynchronous devices

OwnerJames F. Christoffersoninventor

Life of this patent

Estimating the term…

Loading patent…

Abstract

An apparatus for inter-process/inter-device communication in a system of multiple asynchronous devices which uses processing resources efficiently by adhering to an event driven software architecture. An event driven architecture requires that every process have a single blocked input and no blocked outputs, and that all communication between processes take place through a common routing mechanism. The apparatus uses a streams facility, which is commonly used to handle devices, to make processes see the common routing mechanism as a device driver within the streams facility. This common process driver is linked to each real device driver via either a device process set, a polling support service or a half duplex flip-flop, depending upon the nature of the device driver, so as to minimize use of processing resources for communications with real devices.

Claims20

Dependent claims

In a system of multiple asynchronous devices, each said asynchronous device being connected to said system by a respective device driver, said system being defined by operational protocols which determine a logical sequence and timing of messages between said asynchronous devices, said system including processing resources for operating said system, said processing resources having means for allocating said processing resources to multiple tasks and means for managing contention for said processing resources between and among said multiple tasks, said allocating means and contention managing means being implemented by said system during a process interval, an apparatus for inter-process/inter-device communication in furtherance of said operational protocols, said apparatus for communication comprising:

a plurality of data/protocol processes implementing said operational protocols, said plurality of data/protocol processes being organized in conformity with an event-driven architecture, wherein each said data/protocol process has one and only one input, each said input depending for return upon completion of an output event, each said input being fully blocked while awaiting completion of said output event, each said fully blocked input being promptly awakened upon completion of said output event, said allocating and contention managing means making said data/protocol process ready for execution/return within a small number of process intervals in accordance with said operational protocols, and wherein any output of any said data/protocol process is unblocked;
a common routing device for queuing and routing all communication between said data/protocol processes, said common routing device accepting and queuing all said output of any said data/protocol process and invoking said allocating means and said contention managing means in order to awaken said fully blocked inputs and accomplish said routing;
respective device linking mechanisms for effecting communication between each said device driver and said data/protocol processes in conformity with said event-driven architecture;
and
one or more physical links through which said asynchronous devices are connected.

2 more elements

In a system of multiple asynchronous devices, each said asynchronous device being connected to said system by a respective device driver, said system being defined by operational protocols which determine a logical sequence and timing of messages between said asynchronous devices, said system including processing resources for operating said system, said processing resources having means for allocating said processing resources to multiple tasks and means for managing contention for said processing resources between and among said multiple tasks, said allocating means and contention managing means being implemented by said system during a process interval, a method for inter-process/inter-device communication in furtherance of said operational protocols, said method for communication comprising the steps of:

implementing said operational protocols by creating a plurality of data/protocol processes, said plurality of data/protocol processes being organized in conformity with an event-driven architecture, wherein each said data/protocol process has one and only one input, each said input depending for return upon completion of an output event, each said input being fully blocked while awaiting completion of said output event, each said fully blocked input being promptly awakened upon completion of said output event, said allocating and contention managing means making said data/protocol process ready for execution/return within a small number of process intervals in accordance with said operational protocols, and wherein any output of any said data/protocol process is unblocked;
channeling all messages between and among said data/protocol processes and said asynchronous devices into a common routing device for queuing and routing said messages, said common routing device accepting and queuing all said output of any said data/protocol process and invoking said allocating means and said contention managing means in order to awaken said fully blocked inputs and accomplish said routing;
linking each said device driver with said common routing device in conformity with said event-driven architecture;
and
providing one or more physical links through which said asynchronous devices are connected.

2 more elements

Dependencies are inferred from the claim text.