US5428794A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Interrupting node for providing interrupt requests to a pended bus
Assignee: Hewlett Packard Development Co LP
•
Filing: 1994-03-03
•
Granted: 1995-06-27
•
Expires: 2014-03-03
Abstract
Abstract An interrupting node for providing interrupt requests to a pended bus. The interrupting node provides to the pended bus an interrupt request message including ID data for identifying the interrupting node as the source of an interrupt request. An interrupt servicing node provides interrupt acknowledge messages including destination data specifying a particular interrupting node at times when the interrupt servicing node is ready to service an interrupt request message. The interrupting node detects whether an interrupt acknowledge message on the bus includes destination data specifying that interrupting node, and provides an interrupt vector message to the bus in response.
Inventors
- 👤 Douglas D. Williams
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-04 10:06
CPC Classifications
G; G06; G06F; G06F15/00; G06F15/16; G06F15/163; G06F15/17; G06F13/00; G06F13/14; G06F13/20; G06F13/24
Claims Analysis
Total Claims: 28
Claim 1
Independent Claim
127 words
An interrupting node having a unique ID for providing interrupt requests to an interrupt servicing node, and coupled to a pended bus for transferring messages between the interrupting node and the interrupt servicing node, the interrupting node comprising: means for providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request; and means for monitoring interrupt acknowledge messages on the bus, and for detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node.
Claim 2
Dependent Claim
127 words
An interrupting node having a unique ID for providing interrupt requests to an interrupt servicing node, and coupled to a pended bus for transferring messages between the interrupting node and the interrupt servicing node, the interrupting node comprising: means for providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request; and means for monitoring interrupt acknowledge messages on the bus, and for detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node.
Claim 3
Dependent Claim
17 words
An interrupting node in accordance with claim 1, in which the interrupting node is an input/output device.
Claim 4
Dependent Claim
33 words
An interrupting node in accordance with claim 1 in which the interrupt request message providing means includes means for providing, the interrupt request message with destination data for specifying the interrupt servicing node.
Claim 5
Dependent Claim
30 words
An interrupting node in accordance with claim 3 in which the interrupt request message providing means includes means for providing destination data for specifying a plurality of interrupt servicing nodes.
Claim 6
Dependent Claim
37 words
An interrupting node in accordance with claim 1 in which the interrupt request message providing means includes means for providing the interrupt request message with priority level data specifying a priority level of the interrupt request message.
Claim 7
Dependent Claim
38 words
An interrupting node in accordance with claim 5 in which the interrupt acknowledge message detecting means includes means for extracting from the interrupt acknowledge message priority level data specifying a priority level of the interrupt request being serviced.
Claim 8
Dependent Claim
32 words
An interrupting node in accordance with claim 6 in which the interrupt request providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.
Claim 9
Dependent Claim
158 words
An interrupting node having a unique ID for providing interrupt requests to an interrupt servicing node, and coupled to a pended bus for transferring messages between the interrupting node and the interrupt servicing node, the interrupting node comprising: means for providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request; means for monitoring interrupt acknowledge messages on the bus, and for detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node; and means for providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message.
Claim 10
Dependent Claim
158 words
An interrupting node having a unique ID for providing interrupt requests to an interrupt servicing node, and coupled to a pended bus for transferring messages between the interrupting node and the interrupt servicing node, the interrupting node comprising: means for providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request; means for monitoring interrupt acknowledge messages on the bus, and for detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node; and means for providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message.
Claim 11
Dependent Claim
50 words
An interrupting node in accordance with claim 8 in which the interrupt vector providing means includes means for providing, in response to the detection of an interrupt acknowledge message including source data identifying the interrupt servicing node, the interrupt vector message with the source data identifying the interrupt servicing node.
Claim 12
Dependent Claim
17 words
An interrupting node in accordance with claim 8 in which the interrupting node is an input/output device.
Claim 13
Dependent Claim
33 words
An interrupting node in accordance with claim 8 in which the interrupt request message providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.
Claim 14
Dependent Claim
30 words
An interrupting node in accordance with claim 11 in which the interrupt request message providing means includes means for providing destination data for specifying a plurality of interrupt servicing nodes.
Claim 15
Dependent Claim
37 words
An interrupting node in accordance with claim 8 in which the interrupt request message providing means includes means for providing the interrupt request message with priority level data specifying a priority level of the interrupt request message.
Claim 16
Dependent Claim
37 words
An interrupting node in accordance with claim 9 in which the interrupt request message providing means includes means for providing the interrupt request message with priority level data specifying a priority level of the interrupt request message.
Claim 17
Dependent Claim
38 words
An interrupting node in accordance with claim 13 in which the interrupt acknowledge message detecting means includes means for extracting from the interrupt acknowledge message priority level data specifying a priority level of the interrupt request being serviced.
Claim 18
Dependent Claim
41 words
An interrupting node in accordance with claim 15 in which the interrupt vector message providing means includes means for selecting one of a plurality of interrupt vector messages in accordance with the priority level data extracted from the interrupt acknowledge message.
Claim 19
Dependent Claim
32 words
An interrupting node in accordance with claim 9 in which the interrupt request providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.
Claim 20
Dependent Claim
32 words
An interrupting node in accordance with claim 13 in which the interrupt request providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.
Claim 21
Dependent Claim
32 words
An interrupting node in accordance with claim 14 in which the interrupt request providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.
Claim 22
Independent Claim
149 words
A method for an interrupting node having a unique ID to provide interrupt requests to a pended bus for transferring messages between the interrupting node and an interrupt servicing node, the method comprising the steps of: providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request; monitoring interrupt acknowledge messages on the bus, and detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node; and providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message.
Claim 23
Independent Claim
149 words
A method for an interrupting node having a unique ID to provide interrupt requests to a pended bus for transferring messages between the interrupting node and an interrupt servicing node, the method comprising the steps of: providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request; monitoring interrupt acknowledge messages on the bus, and detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node; and providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message.
Claim 24
Dependent Claim
196 words
An interrupting node having a unique ID for providing interrupt requests to an interrupt servicing node, and coupled to a pended bus for transferring messages between the interrupting node and the interrupt servicing node, the interrupting node comprising: means for providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request, destination data for specifying the interrupt servicing node, and priority level data specifying a priority level of the interrupt request message; means for monitoring interrupt acknowledge messages on the bus, and for detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node, by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node, and source data identifying the interrupt servicing node; and means for providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message including the source data identifying the interrupt servicing node.
Claim 25
Dependent Claim
196 words
An interrupting node having a unique ID for providing interrupt requests to an interrupt servicing node, and coupled to a pended bus for transferring messages between the interrupting node and the interrupt servicing node, the interrupting node comprising: means for providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request, destination data for specifying the interrupt servicing node, and priority level data specifying a priority level of the interrupt request message; means for monitoring interrupt acknowledge messages on the bus, and for detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node, by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node, and source data identifying the interrupt servicing node; and means for providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message including the source data identifying the interrupt servicing node.
Claim 26
Independent Claim
186 words
A method for an interrupting node having a unique ID to provide interrupt requests to a pended bus for transferring messages between the interrupting node and an interrupt servicing node, the method comprising the steps of: providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request, destination data for specifying the interrupt servicing node, and priority level data specifying a priority level of the interrupt request message; monitoring interrupt acknowledge messages on the bus; detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node, by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node, and source data identifying the interrupt servicing node; and providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message including the source data identifying the interrupt servicing node.
Claim 27
Independent Claim
186 words
A method for an interrupting node having a unique ID to provide interrupt requests to a pended bus for transferring messages between the interrupting node and an interrupt servicing node, the method comprising the steps of: providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request, destination data for specifying the interrupt servicing node, and priority level data specifying a priority level of the interrupt request message; monitoring interrupt acknowledge messages on the bus; detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node, by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node, and source data identifying the interrupt servicing node; and providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message including the source data identifying the interrupt servicing node.
Claim 28
Dependent Claim
32 words
An interrupting node in accordance with claim 5 in which the interrupt request providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.
References Cited (Backward Citations)
US3800287A
Cited
US3881174A
Cited
JPS50156336A
Cited
US4000485A
Cited
US4020471A
Cited
US4106104A
Cited
US4028667A
Cited
US4056847A
Cited
JPS5341144A
Cited
US4058672A
Cited
US4172284A
Cited
US4271464A
Cited
US4296466A
Cited
US4268904A
Cited
US4275440A
Cited
US4250489A
Cited
US4240140A
Cited
US4291371A
Cited
US4482954A
Cited
US4271468A
Cited
US4349873A
Cited
US4373183A
Cited
US4337465A
Cited
US4510492A
Cited
US4366480A
Cited
US4615019A
Cited
US4443850A
Cited
US4510493A
Cited
US4534652A
Cited
US4560985A
Cited
US4560985B1
Cited
US4583088A
Cited
US4542501A
Cited
US4654654A
Cited
US4769768A
Cited
US4669057A
Cited
US4654820A
Cited
US4642758A
Cited
US4736319A
Cited
US4716523A
Cited
US4994960A
Cited
US4930070A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 1998-06-26 | 1998-12-26 | 1999-06-27 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2002-06-26 | 2002-12-26 | 2003-06-27 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2006-06-26 | 2006-12-26 | 2007-06-27 | $7700.00 | Window Closed / Lapsed |