The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
May. 31, 2011
Filed:
Sep. 10, 2004
Frederick Baker, Santa Barbara, CA (US);
Bruce S. Davie, Cambridge, MA (US);
David R. Oran, Acton, MA (US);
Carol Iturralde, Framingham, MA (US);
Roger Levesque, Tewksbury, MA (US);
Michael V. Dibiasio, Westford, MA (US);
Frederick Baker, Santa Barbara, CA (US);
Bruce S. Davie, Cambridge, MA (US);
David R. Oran, Acton, MA (US);
Carol Iturralde, Framingham, MA (US);
Roger Levesque, Tewksbury, MA (US);
Michael V. DiBiasio, Westford, MA (US);
Cisco Technology, Inc., San Jose, CA (US);
Abstract
A technique is provided for one or more network nodes to deterministically select data flows to preempt. In particular, each node employs a set of predefined rules which instructs the node as to which existing data flow should be preempted in order to admit a new high-priority data flow. The rules are precisely defined and are common to all nodes configured in accordance with the present invention. Illustratively, a network node not only selects a data flow to preempt, but additionally may identify other 'fate sharing' data flows that may be preempted. As used herein, a group of data flows has a fate-sharing relationship if the application instance(s) containing the data flows functions adequately only when all the fate-shared flows are operational. In a first illustrative embodiment, after a data flow in a fate-sharing group is preempted, network nodes may safely tear down the group's remaining data flows. In a second illustrative embodiment, when a data flow is preempted, all its fate-shared data flows are marked as being 'at risk.' Because the at-risk flows are not immediately torn down, it is less likely that resources allocated for the at-risk flows may be freed then subsequently used to establish relatively lower-priority data flows instead of relatively higher-priority data flows.