Patent EP0491367A2 successfully refreshed from Google Patents.
EP0491367A2
Expired / Lapsed
EP
⏱️ 0.0 years remaining
A queue managing method for an electronic mail system
Assignee: Bull HN Information Systems Inc
•
Filing: 1991-12-17
•
Granted: —
•
Expires: 2011-12-17
Abstract
Abstract A queue manager for controlling the execution of requests for the transport of messages from users to destinations. Each request includes a message and an identification of a destination. The queue manager includes a queue for storing pending requests and a dispatcher task for creating a worker task to execute each request and provides a method for adapting the execution of requests to constraints and characteristics of destinations and communications links.
Inventors
- 👤 Richard E. Batchelor
Bibliographic Details
Application Number
—
Jurisdiction
EP
Data Source
google_patents
Last Synchronized
2026-11-09 19:16
CPC Classifications
H; H04; H04L; H04L51/00; H04L51/21; H04L51/226; H04L51/23
Claims Analysis
Total Claims: 10
Claim 1
Independent Claim
261 words
For use in an electronic mail system, a queue manager for controlling the execution of requests for the transport of messages from users to destinations, each request including a message and an identification of a destination, the queue manager including a queue for storing pending requests, a dispatcher task responsive to each request for creating a corresponding worker task to execute the request and associating the worker task with a corresponding bound unit for transporting the messages to the destination through communications links, a method for adapting operation of the queue manager to characteristics of the destinations and the communications links, comprising the steps of: providing in each request a parameter indicating a priority level of the request, providing and storing a table containing an entry for each destination, each entry including an identification of a bound unit serving that destination, and a set of descriptors describing time windows during which the destination may receive messages, wherein each window corresponds to a priority level, and each window descriptor contains parameters identifying the priority level of the window, a time during which the window is open, and an economic quantity number, and by operation of the dispatcher task, scanning the destination table to determine which windows are currently open, scanning the queue to identify pending requests for the currently open windows, and whether the number of requests for an open window equals or exceeds the economic quantity for the window, and executing the requests corresponding to each currently open window wherein the number of requests satisfies the economic quantity for the window.
Claim 2
Dependent Claim
30 words
The queue manager of claim 1, wherein: the group of requests corresponding to a currently open window and satisfying the economic quantity for the window are executed as a batch.
Claim 3
Dependent Claim
33 words
The queue manager of claim 2, wherein: when a window closes during the execution of a batch of requests for the window, the execution of all requests in the batch will be completed.
Claim 4
Dependent Claim
31 words
The queue manager of claim 2, wherein: all higher level priority requests pending for a window are executed during the execution of a batch of lower priority requests for the window.
Claim 5
Dependent Claim
34 words
The queue manager of claim 1, wherein: queued requests of a higher priority level for a destination will be counted towards satisfying the economic quantity of a lower level priority window of that destination.
Claim 6
Dependent Claim
95 words
The queue manager of claim 1, wherein: each request further includes parameters specifying attempts to retry execution of the request when an attempt to execute the request fails, and the bound units are responsive to the results of each attempt to transport the message of a request for providing result messages to the dispatcher task indicating the results of each attempt to execute a corresponding request, and the dispatcher task is responsive to the result messages to reschedule execution of a request according to the retry parameters when an attempt to execute the request fails.
Claim 7
Dependent Claim
28 words
The queue manager of claim 6, wherein: the retry parameters include at least one parameter specifying a time interval to elapse before the request is to be retried.
Claim 8
Dependent Claim
34 words
The queue manager of claim 6, wherein: the retry parameters include a parameter specifying whether the request is to be retried a limited number of times, or is to be retried until successfully executed.
Claim 9
Dependent Claim
36 words
The queue manager of claim 6 wherein: the dispatcher task is responsive to a failed attempt to execute a request to a destination to suspend execution of all requests to the destination for a specified time.
Claim 10
Dependent Claim
78 words
The queue manager of claim 9 wherein: the dispatcher task will attempt to execute a request to a suspended destination after the elapse of the specified suspension interval, and will resume execution of all other requests to the destination when the attempt to execute a request to the destination succeeds, and will continue suspension of execution of requests to the destination for a further specified suspension interval when the attempt to execute a request to the destination fails.
References Cited (Backward Citations)
No citation records indexed.
USPTO Annuity & Maintenance Windows
Maintenance schedule is calculated for granted US utility patents.