Method and systems for allowing data service system to provide class-based services to its users

• US 6,304,906 B1
• Filed: 08/06/1998
• Issued: 10/16/2001
• Est. Priority Date: 08/06/1998
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Zara, Anna M., Friedrich, Richard J., Bhatti, Nina T., Jin, Tai
• Primary Examiner(s): Lim, Krisna
• Assistant Examiner(s): Le, Hieu
• Application Number:
  US09/130,636
• Time in Patent Office: 1,167 Days
• Field of Search: 709/201-203, 709/226-227, 709/207, 709/228-229, 370/395, 370/431
• US Class Current: 709/227
• CPC Class Codes: H04L 12/2856 Access arrangements, e.g. Internet access asynchronous transfer mode networks H04L12/5601; broadband local area networks H04L12/2801; optical access or distribution networks H04Q11/0067; access to open networks H04L12/5691; digital subscriber line end-user equipment and bit-level processing of data on a PSTN-based network H04M11/00; home network gateways H04L12/2834; wireless access networks H04W
• CPC Class Codes: H04L 12/2874 Processing of data for distribution to the subscribers
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 47/19 at layers above the network layer network arrangements for networked applications for scheduling or organising the servicing of application requests H04L67/60
• CPC Class Codes: H04L 47/24 Traffic characterised by specific attributes, e.g. priority or QoS
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/808 User-type aware
• CPC Class Codes: H04L 47/821 Prioritising resource allocation or reservation requests
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A data service system is accessible through a plurality of access requests. The data service system includes a user access request classification system for classifying the access requests. The user access request classification system includes a request classifier that classifies each of the access requests into one of a plurality of classes based on a predetermined classification policy. The user access request classification system also includes a plurality of buffers coupled to the request classifier. Each buffer corresponds to one of the classes to receive the access requests classified by the request classifier as belonging to that class such that the data service system processes the access requests in accordance with their classes. A method of classifying user access requests for the data service system is also described.

Claims

1. In a data service system that includes a content site accessible through a plurality of access requests, a user access request classification system for classifying the access requests, comprising:

a request classifier that classifies each of the access requests into one of a plurality of classes based on a predetermined classification policy;

a plurality of buffers outside the request classifier but coupled to the request classifier, each for one of the classes in order to receive the access requests classified by the request classifier as belonging to that class such that the data service system processes the access requests in accordance with their classes;

a rejecter outside the request classifier but coupled between the request classifier and the buffers to reject the classified access requests based on a predetermined rejection policy, wherein the request classifier, the buffers, and the rejecter are part of and reside within the data service system.

2. The user access request classification system of claim 1, wherein the predetermined classification policy allows classification of the access requests based on the sender addresses of the access requests.

3. The user access request classification system of claim 1, wherein the predetermined classification policy allows classification of the access requests based on a tag contained in each of the access requests, a cookie, or a browser plug-in value.

4. The user access request classification system of claim 1, wherein the predetermined classification policy allows classification of the access requests based on a pathname or a URL locator.

5. The user access request classification system of claim 1, further comprising a connection manager that determines which one of the access requests from which one of the buffers is to be processed in accordance with a predetermined scheduling policy.

6. The user access request classification system of claim 5, wherein the predetermined scheduling policy is selected from a group comprising a priority scheduling, a Round robin fair scheduling, a bandwidth metric scheduling, a throughput metric scheduling, a response time metric scheduling, and an error rate metric scheduling.