US5237662A
Expired / Lapsed
US
⏱️ 0.0 years remaining
System and method with a procedure oriented input/output mechanism
Assignee: Hewlett Packard Development Co LP
•
Filing: 1991-06-27
•
Granted: 1993-08-17
•
Expires: 2011-06-27
Abstract
Abstract In a data processing system a structure (50) called an I/O association is constructed. An I/O association (50) is a symmetric structure which allows not only consumer (52) of a service to locate the provider (54) of the service, but it also permits the converse. In some respects, an I/O channel (32) is only half of an association (50). The association (50) describes a targeted object (56) and provides the means (57) of locating the necessary procedures to operate on the target (56). The association (50) also describes a source object (58) that is held responsible for the requested operation, as well as the means (60) of locating and invoking procedures to report results to the source object (58).
Inventors
- 👤 Kelly C. Green
- 👤 Steven M. Jenness
- 👤 Terry L. Carruthers
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-03 14:39
CPC Classifications
G; G06; G06F; G06F13/00; G06F13/38; G06F13/382; G06F13/385; G06F13/10; G06F13/102
Claims Analysis
Total Claims: 14
Claim 1
Independent Claim
210 words
An input/output system for a data processing system, said input/output system comprising a plurality of subsystems, said plurality of subsystems including: a consumer subsystem including consumer subsystem routines for controlling input/output operations between said consumer subsystem and any other of said plurality of subsystems, and a source object, accessible by other ones of said plurality of subsystems, that defines said consumer subsystem; a provider subsystem including provider subsystem routines for controlling input/output operations between said provider subsystem and any other of said plurality of subsystems, and a target object, accessible by other ones of said plurality of subsystems, that defines said provider subsystem; and an input/output association binding said consumer subsystem to said provider subsystem, said input/output association including: a source handle in said provider subsystem enabling said provider subsystem to access said source object; a target handle in said consumer subsystem enabling said provider subsystem to access said source object; consumer bindings in said provider subsystem for enabling said provider subsystem to access said consumer subsystem routines when performing input/output operations between said provider subsystem and said consumer subsystem; and provider bindings in said consumer subsystem for enabling said consumer subsystem to access said provider subsystem routines when performing input/output operations between said consumer subsystem and said provider subsystem.
Claim 2
Dependent Claim
210 words
An input/output system for a data processing system, said input/output system comprising a plurality of subsystems, said plurality of subsystems including: a consumer subsystem including consumer subsystem routines for controlling input/output operations between said consumer subsystem and any other of said plurality of subsystems, and a source object, accessible by other ones of said plurality of subsystems, that defines said consumer subsystem; a provider subsystem including provider subsystem routines for controlling input/output operations between said provider subsystem and any other of said plurality of subsystems, and a target object, accessible by other ones of said plurality of subsystems, that defines said provider subsystem; and an input/output association binding said consumer subsystem to said provider subsystem, said input/output association including: a source handle in said provider subsystem enabling said provider subsystem to access said source object; a target handle in said consumer subsystem enabling said provider subsystem to access said source object; consumer bindings in said provider subsystem for enabling said provider subsystem to access said consumer subsystem routines when performing input/output operations between said provider subsystem and said consumer subsystem; and provider bindings in said consumer subsystem for enabling said consumer subsystem to access said provider subsystem routines when performing input/output operations between said consumer subsystem and said provider subsystem.
Claim 3
Dependent Claim
61 words
The input/output system of claim 1 in which said consumer subsystem includes means for invoking a provider service by calling one of said provider subsystem routines, said provider subsystem includes a means for validating and enqueuing requests for provider service, said means for invoking a provider service and said means for validating and enqueuing requests being connected through said input/output association.
Claim 4
Dependent Claim
59 words
The input/output system of claim 2, said provider subsystem routines in said provider subsystem including a means for performing a provider service, said consumer subsystem routines in said consumer subsystem including a means for providing a completion procedure, said means for performing a provider service and said means for providing a completion procedure being connected through said input/output association.
Claim 5
Dependent Claim
33 words
The input/output system of claim 3 in which said means for validating and enqueuing requests is connected to said means for performing a provider service through a means for instantiating a next request.
Claim 6
Dependent Claim
29 words
The input/output system of claim 3 in which said means for providing a completion procedure is connected to a means for synchronizing said consumer subsystem with a controlling system.
Claim 7
Dependent Claim
137 words
An input/output system which comprises a data processing system including a consumer subsystem including consumer subsystem routines for controlling input/output operations between said consumer subsystem and any other subsystem in said data processing system, a provider subsystem including provider subsystem routines for controlling input/output operations between said provider subsystem and any other subsystem in said data processing system, and a non-hierarchical input/output association binding together said consumer subsystem and said provider subsystem as peers, said input/output association including: consumer bindings in said provider subsystem for enabling said provider subsystem to access said consumer subsystem routines when performing input/output operations between said provider subsystem and said consumer subsystem; and provider bindings in said consumer subsystem for enabling said consumer subsystem to access said provider subsystem routines when performing input/output operations between said consumer subsystem and said provider subsystem.
Claim 8
Dependent Claim
137 words
An input/output system which comprises a data processing system including a consumer subsystem including consumer subsystem routines for controlling input/output operations between said consumer subsystem and any other subsystem in said data processing system, a provider subsystem including provider subsystem routines for controlling input/output operations between said provider subsystem and any other subsystem in said data processing system, and a non-hierarchical input/output association binding together said consumer subsystem and said provider subsystem as peers, said input/output association including: consumer bindings in said provider subsystem for enabling said provider subsystem to access said consumer subsystem routines when performing input/output operations between said provider subsystem and said consumer subsystem; and provider bindings in said consumer subsystem for enabling said consumer subsystem to access said provider subsystem routines when performing input/output operations between said consumer subsystem and said provider subsystem.
Claim 9
Dependent Claim
63 words
The input/output system of claim 6 in which said consumer subsystem includes a means for involving a provider service by calling one of said provider subsystem routines, said provider subsystem includes a means for validating and enqueuing requests for provider service, said means for invoking a provider service and said means for validating and enqueuing requests being bound together by said input/output association.
Claim 10
Dependent Claim
58 words
The input/output system of claim 6, said provider subsystem routines in said provider subsystem including a means for performing a provider service, said consumer subsystem routines in said consumer subsystem including means for providing a completion procedure, said means for performing a provider service and said means for providing a completion procedure being connected through said input/output association.
Claim 11
Dependent Claim
118 words
In a data processing system, a method for controlling input/output operations in the system, comprising: providing a consumer subsystem including consumer subsystem routines for controlling input/output operations between said consumer subsystem and any other subsystem in said data processing system, providing a provider subsystem including provider subsystem routines for controlling input/output operations between said provider subsystem and any other subsystem in said data processing system, forming an input/output association between the consumer subsystem and the provider subsystem, said input/output association enabling said consumer subsystem to access the provider subsystem routines in said provider subsystem and enabling said provider subsystem to access the consumer subsystem routines in said consumer subsystem, and performing input/output operations therebetween through the input/output association.
Claim 12
Dependent Claim
118 words
In a data processing system, a method for controlling input/output operations in the system, comprising: providing a consumer subsystem including consumer subsystem routines for controlling input/output operations between said consumer subsystem and any other subsystem in said data processing system, providing a provider subsystem including provider subsystem routines for controlling input/output operations between said provider subsystem and any other subsystem in said data processing system, forming an input/output association between the consumer subsystem and the provider subsystem, said input/output association enabling said consumer subsystem to access the provider subsystem routines in said provider subsystem and enabling said provider subsystem to access the consumer subsystem routines in said consumer subsystem, and performing input/output operations therebetween through the input/output association.
Claim 13
Dependent Claim
44 words
The method for input or output of claim 9 in which said consumer subsystem initiates an input/output operation by making a request for a provider service through the input/output association, and validating and enqueuing the request for the provider service in the provider subsystem.
Claim 14
Dependent Claim
63 words
The method for input or output of claim 9 in which an input/output operation is performed by performing a provider service by calling one of said provider subsystem routines in the provider subsystem, signaling completion of the service to the consumer subsystem through the input/output association, and performing a completion procedure by calling one of said consumer subsystems routines in the consumer subsystem.
References Cited (Backward Citations)
US4246637A
Cited
US4418382A
Cited
US4451884A
Cited
US4517641A
Cited
US4791560A
Cited
US4947028A
Cited
US4947028B1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 1996-08-16 | 1997-02-15 | 1997-08-17 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2000-08-16 | 2001-02-15 | 2001-08-17 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2004-08-16 | 2005-02-15 | 2005-08-17 | $7700.00 | Window Closed / Lapsed |