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:
Nov. 04, 2008
Filed:
Feb. 11, 2002
Ratinder Paul Singh Ahuja, Saratoga, CA (US);
Susan Carrie, Mountain View, CA (US);
Chien C. Chou, San Jose, CA (US);
Erik DE LA Iglesia, Mountain View, CA (US);
Miguel Gomez, Fremont, CA (US);
Liang Liu, San Jose, CA (US);
Ricky K. Lowe, Atherton, CA (US);
Rahoul Puri, Los Altos, CA (US);
Kiet Tran, Saratoga, CA (US);
Mark Aaron Wallace, San Jose, CA (US);
Wei Wang, San Jose, CA (US);
Todd E. Wayne, Santa Cruz, CA (US);
Hui Zhang, Cupertino, CA (US);
Ratinder Paul Singh Ahuja, Saratoga, CA (US);
Susan Carrie, Mountain View, CA (US);
Chien C. Chou, San Jose, CA (US);
Erik De La Iglesia, Mountain View, CA (US);
Miguel Gomez, Fremont, CA (US);
Liang Liu, San Jose, CA (US);
Ricky K. Lowe, Atherton, CA (US);
Rahoul Puri, Los Altos, CA (US);
Kiet Tran, Saratoga, CA (US);
Mark Aaron Wallace, San Jose, CA (US);
Wei Wang, San Jose, CA (US);
Todd E. Wayne, Santa Cruz, CA (US);
Hui Zhang, Cupertino, CA (US);
Extreme Networks, Santa Clara, CA (US);
Abstract
Systems and related methods are described for handling one or more resource requests. A protocol engine receives a resource request in accordance with a prescribed protocol, and a classification engine determines a desired class of service for the request. An analysis engine optionally analyzes the request, and, responsive thereto, determines a desired sub-class of service for the request. A policy engine then allocates a resource to the request responsive to one or both of the desired class of service, and the desired sub-class of service.