Method and apparatus for identifying network data traffic flows and for applying quality of service treatments to the flows

• US 6,434,624 B1
• Filed: 07/23/2001
• Issued: 08/13/2002
• Est. Priority Date: 12/04/1998
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: McCloghrie, Keith, Gai, Silvano, Mohaban, Shai
• Primary Examiner(s): VU, VIET DUY
• Application Number:
  US09/911,122
• Time in Patent Office: 386 Days
• Field of Search: 709/223, 709/225, 709/226, 709/228, 709/229, 709/230, 709/234, 709/236, 709/238, 709/232, 709/313, 370/235
• US Class Current: 709/232
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5045 Making service definitions prior to deployment
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 47/2433 Allocation of priorities to traffic types
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/2475 for supporting traffic characterised by the type of applications
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/724 at intermediate nodes, e.g. resource reservation protocol [RSVP]
• CPC Class Codes: H04L 47/803 Application aware
• CPC Class Codes: H04L 47/808 User-type aware

Abstract

A system within a computer network identifies specific traffic flows originating from a given network entity and requests and applies appropriate policy rules or service treatments to the traffic flows. A network entity includes a flow declaration component that communicates with one or more application programs executing on the entity. The flow declaration component includes a message generator and an associated memory for storing one or more traffic flow data structures. For a given traffic flow, the application program issues one or more calls to the flow declaration component providing it with information identifying the traffic flows. The flow declaration component then opens a flow management session with a local policy enforcer that obtains policy rules or service treatments for the identified flow from a policy server and applies those rules or treatments to the specific traffic flows from the network entity.

Claims

1. A method for applying a service treatment to a plurality of network messages issued by an application program running on a network entity connected to a computer network, the network messages corresponding to a specific traffic flow, the computer network including a policy server and the computer network configured to support transport and network communication layers, the method comprising the steps of:

receiving from the network entity a Resource reSerVation Protocol (RSVP) Path message identifying the traffic flow and including one or more application-level parameters;

generating a request policy message containing the identified traffic flow and at least some of the application-level parameters included in the RSVP Path message;

sending the request policy message to the policy server; and

receiving a policy decision message from the policy server specifying one or more service treatments to be applied to the traffic flow, the one or more service treatments based, at least in part, upon the application-level parameters.

2. The method of claim 1 further comprising the steps of

identifying network messages corresponding to the traffic flow; and

applying the one or more service treatments specified in the policy decision message to those network messages identified as corresponding to the traffic flow.

3. The method of claim 1 wherein the application-level parameters included in the RSVP Path message specify one or more of the following characteristics:

the size of a file being transmitted, a video segment name, a video segment viewer, a user name, a user department, an application identifier, a transaction type, a transaction name, an application state, a calling party, a called party, a compression method, a service level, a uniform resource locator (URL) and a mime type.

4. The method of claim 1 wherein the service treatment specified in the policy decision message includes marking network messages corresponding to the traffic flow with one or more of a selected Differentiated Services Codepoint (DSCP), a selected Type of Service (ToS), and a selected user_priority.

5. The method of claim 1 further comprising the steps of:

generating an RSVP Reservation (Resv) message; and

sending the RSVP Resv message to the network entity.

6. The method of claim 5 wherein the steps of generating the RSVP Resv message and sending the RSVP Resv message are performed by a first hop intermediate network device relative to the network entity.

7. The method of claim 5 wherein the RSVP Resv message includes one or more of the service treatments specified in the policy decision message.

8. The method of claim 7 wherein the steps of generating the RSVP Resv message and sending the RSVP Resv message are performed by a first hop intermediate network device relative to the network entity.

9. The method of claim 1 wherein the received RSVP Path message includes a plurality of network and transport layer parameters corresponding to the traffic flow.

10. The method of claim 9 wherein

the RSVP Path message includes a RSVP sender Template object and a RSVP session object, and

the network and transport layer parameters are contained in the RSVP sender Template and session objects.

11. The method of claim 9 wherein the RSVP Path message includes one or more policy_data objects.

12. The method of claim 11 wherein the policy_data objects are encoded versions of the application-level parameters.

13. The method of claim 11 wherein one or more of the policy_data objects have a policy identifier (PID) element and an encoded policy instance element.

14. The method of claim 13 wherein the PID elements comply in at least substantial part with the Common Open Policy Service (COPS) Usage for Differentiated Services specification standard.

15. The method of claim 1 whereby the steps of the method are performed by an intermediate network device and the received policy decision includes instruction steps directing the intermediate network device to:

generate an RSVP Reservation (Resv) message; and

send the RSVP Resv message to the network entity.

16. The method of claim 15 wherein

the service treatment specified in the policy decision message includes marking network messages corresponding to the traffic flow with one or more of a selected Differentiated Services Codepoint (DSCP), a selected Type of Service (ToS), and a selected user_priority,

the RSVP Resv message specifies the selected DSCP, ToS and/or user_priority, and

the network entity marks network messages corresponding to the traffic flow with the selected DSCP, ToS and/or user_priority.

23. The method of claim 3 wherein the service treatment specified in the policy decision message includes marking network messages corresponding to the traffic flow with one or more of a selected Differentiated Services Codepoint (DSCP), a selected Type of Service (ToS), and a selected user_priority.

24. The method of claim 3 further comprising the steps of:

generating an RSVP Reservation (Resv) message; and

sending the RSVP Resv message to the network entity.

25. The method of claim 24 wherein the steps of generating the RSVP Resv message and sending the RSVP Resv message are performed by a first hop intermediate network device relative to the network entity.

26. The method of claim 24 wherein the RSVP Resv message includes one or more of the service treatments specified in the policy decision message.

27. The method of claim 26 wherein the steps of generating the RSVP Resv message and sending the RSVP Resv message are performed by a first hop intermediate network device relative to the network entity.

28. The method of claim 3 wherein the received RSVP Path message includes a plurality of network and transport layer parameters corresponding to the traffic flow.

29. The method of claim 28 wherein the RSVP Path message includes one or more policy_data objects.

30. The method of claim 29 wherein the policy_data objects are encoded versions of the application-level parameters.

31. The method of claim 29 wherein one or more of the policy_data objects have a policy identifier (PID) element and an encoded policy instance element.

32. The method of claim 31 wherein the PID elements comply in at least substantial part with the Common Open Policy Service (COPS) Usage for Differentiated Services specification standard.

33. The method of claim 3 whereby the steps of the method are performed by an intermediate network device and the received policy decision includes instruction steps directing the intermediate network device to:

generate an RSVP Reservation (Resv) message; and

send the RSVP Resv message to the network entity.

34. The method of claim 33 wherein

the service treatment specified in the policy decision message includes marking network messages corresponding to the traffic flow with one or more of a selected Differentiated Services Codepoint (DSCP), a selected Type of Service (ToS), and a selected user_priority,

the RSVP Resv message specifies the selected DSCP, ToS and/or user_priority, and

the network entity marks network messages corresponding to the traffic flow with the selected DSCP, ToS and/or user_priority.

17. A Resource reSerVation Protocol (RSVP) Path message for transmission by the network entity and/or receipt by an intermediate network device, the RSVP Path message specifying a traffic flow which one or more service treatments are to be applied, the RSVP Path message comprising:

a sender Template object specifying one or more source network and transport parameters;

a session object specifying one or more destination network and transport parameters; and

one or more policy_data objects specifying one or more application-level parameters.

18. The RSVP Path message of claim 17 wherein the application-level parameters included in the one or more policy_data objects specify one or more of the following characteristics:

the size of a file being transmitted, a video segment name, a video segment viewer, a user name, a user department, an application identifier, a transaction type, a transaction name, an application state, a calling party, a called party, a compression method, a service level, a uniform resource locator (URL) and a mime type.

19. The RSVP Path message of claim 17 wherein the policy_data objects are encoded versions of the application-level parameters.

20. The RSVP Path message of claim 19 wherein one or more of the policy_data objects have a policy identifier (PID) element and an encoded policy instance element.

21. The RSVP Path message of claim 20 wherein the PID elements comply in at least substantial part with the Common Open Policy Service (COPS) Usage for Differentiated Services specification standard.

22. The RSVP Path message of claim 17 wherein the message is free of a sender Tspec object.