Method for supporting different service levels in a network using web page content information

• US 6,073,175 A
• Filed: 04/27/1998
• Issued: 06/06/2000
• Est. Priority Date: 04/27/1998
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Tavs, John Edward, Verma, Dinesh Chandra
• Primary Examiner(s): Maung, Zarni
• Application Number:
  US09/067,509
• Time in Patent Office: 771 Days
• Field of Search: 709/226, 709/240, 709/229, 709/203, 709/219
• US Class Current: 709/226
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method for classifying different pages accessed by a web-browser into different service-levels on a granularity finer than that of the connection. The method augments each edge device with two applications, a Client-Proxy and a Server-Proxy. The Client-Proxy obtains identifying information from the client'"'"'s request, and the obtain PICS labelling information from a label referee. This information is used to obtain a service level from an LDAP based SLA directory, and this service level information is then imbedded along with a unique identifier for the network operator organization in the HTTP header request which is transferred to the Server-Proxy. The Server-Proxy then strips the header containing the PICS information from the request and forwards the request to the server. When the Server-Proxy gets a response, it uses the PICS information to mark the packets.

Claims

1. In a network connected to clients by intermediate nodes, a method of differentiating priority of access to an internet web server based on content of web pages being accessed, comprising the steps of:

storing ratings independent of client input of web pages at a node on the network;

on receipt of a client request for a web page, determining at an intermediate node a rating for said web page, said determination being made by lookup at said rating storage node;

converting, at said intermediate node, said rating to a service class by looking up said rating at an Lightweight Delivery Access Protocol (LDAP) directory node;

selecting, for use of said intermediate node, a mechanism for providing differentiated services according to said service class.

2. The method of claim 1, wherein said rating storage node is a label bureau node.

3. The method of claim 1, wherein said rating storage node is said server.

4. The method of claim 1, wherein said selected mechanism is one or more of:

establishing a queuing priority for said service class;

setting Type of Service (TOS) flags in package headers;

using channels in the network which have been designated for said service class;

passing parameters to the server;

limiting bandwidth used by said service class.

5. The method of claim 1, wherein a client-side intermediate node determines said rating and sends it to a server-side intermediate node, which converts the rating to a service class and then uses said service class to select a mechanism for differentiating services on the network.

6. The method of claim 5, wherein said client-side and said server-side intermediate nodes monitor the network traffic between them, and said client-side intermediate node decides when to activate said selected mechanism.

7. The method of claim 1, wherein a client-side intermediate node determines said rating and converts said rating to a service class and then uses said service class to select a mechanism for differentiating services on the network.

8. The method of claim 7, wherein a server-side intermediate node receives said service class from a client-side intermediate node and overrides said service class determination by converting said rating to another service class and then uses said service class to select another mechanism for differentiating services on the network.

9. In a network connected to clients by intermediate nodes, a system for differentiating priority of access to an internet web server based on content of web pages being accessed, comprising:

means for storing ratings independent of client input of web pages at a node on the network;

on receipt of a client request for a web page, means for determining at an intermediate node a rating for said web page, said determination being made by lookup at said rating storage node;

means for converting, at said intermediate node, said rating to a service class by looking up said rating at a Lightweight Delivery Access Protocol (LDAP) directory node;

means for selecting, for use of said intermediate node, a mechanism for providing differentiated services according to said service.

10. The system of claim 9, wherein said rating storage node is a label bureau node.

11. The system of claim 9, wherein said rating storage node is said server.

12. The system of claim 9, wherein said selected mechanism is one or more of:

means for establishing a queuing priority for said service class;

means for setting Type of Service (TOS) flags in package headers;

means for using channels in the network which have been designated for said service class;

means for passing parameters to the server;

means for limiting bandwidth used by said service class.

13. The system of claim 9, wherein a client-side intermediate node determines said rating and sends it to a server-side intermediate node, which converts the rating to a service class and then uses said service class to select a mechanism for differentiating services on the network.

14. The system of claim 13, wherein said client-side and said server-side intermediate nodes monitor the network traffic between them, and said client-side intermediate node decides when to activate said selected mechanism.

15. The system of claim 9, wherein a client-side intermediate node determines said rating and converts said rating to a service class and then uses said service class to select a mechanism for differentiating services on the network.

16. The system of claim 15, wherein a server-side intermediate node receives said service class from a client-side intermediate node and overrides said service class determination by converting said rating to another service class and then uses said service class to select another mechanism for differentiating services on the network.