Systems and methods to support quality of service in communications networks

• US 20050102414A1
• Filed: 09/16/2004
• Published: 05/12/2005
• Est. Priority Date: 09/16/2003
• Status: Abandoned Application

• Current Assignee: Nexthop Technologies
• Original Assignee: Shailesh Mehra
• Inventors: Tavs, John, Hares, Susan
• Application Number:
  US10/944,398
• Publication Number:
  US 20050102414A1
• Time in Patent Office: Days
• US Class Current: 709/232
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/30 Routing of multiclass traffic
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• 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/2491 Mapping quality of service [QoS] requirements between different networks
• CPC Class Codes: H04L 47/283 in response to processing delays, e.g. caused by jitter or round trip time [RTT]

Abstract

Systems and methods are described for supporting Quality of Service assurances for communication by and between software applications over a best-efforts networks. Characteristic signatures are generated and referenced to segregate traffic on the network into discrete flows. Traffic engineering protocols, such as MPLS, are used to generate discrete paths in the best-efforts network, and flows are routed on such paths based on pre-set policies. The state of individual paths and the network at large are continuously monitored in order to re-map flows on paths and maintain the QoS assurances.

Claims

1. A method of communication for a plurality of software applications over a wide-area packet-switched network, wherein the packet-switched network communicates via a best-efforts protocol operating on a first layer of the packet-switched network, and a label switching protocol operating on a second layer of the packet-switched network, the method comprising:

at one or more nodes in the wide-area packet-switched network, classifying packets traversing through the one or more nodes into a plurality of microflows, the classifying packets further including

detecting identifying signatures for the packets,

mapping the signatures to the plurality of microflows;

mapping in real-time the plurality of microflows to a plurality of label-switched paths, the label-switch paths generated by the label switching protocol, mapping the plurality of microflows further including

determining a current status of each of the plurality of label-switched paths,

for each micro-flow from the plurality of micro-flows, determining a rule applicable to the micro-flow, wherein the rule specifies one or more network characteristics for the microflow, and

comparing the rule applicable to the micro-flow to the current status of each of the plurality of label-switched paths to select a label-switched path from the plurality of label-switched paths on which to forward the microflow.

2. The method of claim 1, wherein each of the plurality of microflows includes a distinct unit of network traffic related to one or more of the plurality of software applications.

3. The method of claim 2, wherein, for each of the plurality of micro-flows, the one or more of the plurality of software applications have a service level requirement, the service level requirement defined by one or more of the following:

a relative priority of the microflow amongst the plurality of micro-flows, a bandwidth requirement for the microflow, a latency tolerance range for the microflow, a jitter tolerance range for the microflow, and a packet-drop tolerance for the micro-flow.

4. The method of claim 3, wherein for each of the plurality of microflows, the rule applicable to the microflow guarantees the service level requirement for the one or more software applications.

5. The method of claim 1, wherein for each of the plurality of label-switched paths, the current status includes one or more of the following:

a percentage of bandwidth currently consumed in the label-switched path, an indication of whether the label-switched path is currently live or non-responsive.

6. The method of claim 1, wherein the one or more network characteristics specified by the includes one or more of the following:

a relative priority of the microflow amongst the plurality of micro-flows, a bandwidth requirement for the microflow, a latency tolerance range for the microflow, a jitter tolerance range for the microflow, and a packet-drop tolerance for the micro-flow, a port number for the microflow, a protocol-type for the microflow.

7. The method of claim 1, wherein the plurality of software applications includes database applications, virtual private network applications, multimedia streaming applications, e-mail applications, web applications, internet telephony applications, storage area networking applications, file transfer applications, peer-to-peer networking applications.

8. The method of claim 1, wherein the identifying signatures identify headers in the packets.

9. The method of claim 1, wherein the identifying signatures identify payloads in the packets.

10. The method of claim 1, wherein the label switching protocol includes Multiple Protocol Label Switching.

11. The method of claim 10, wherein the label switching protocol includes RSVP.

12. The method of claim 10, wherein the label switching protocol includes LDP.

13. The method of claim 1, wherein the best-efforts protocol includes IP.

14. The method of claim 1, wherein the best-efforts protocol includes TCP.

15. The method of claim 1, wherein the best-efforts protocol includes UDP.

16. The method of claim 1, wherein the classifying packets further includes:

updating one or more state tables for the plurality of microflows.

17. The method of claim 16, wherein the one or more state tables includes a plurality of tuples associated with the plurality of microflows.

18. The method of claim 17, wherein each of the plurality of tuples includes a source address, a destination address, a source port, a destination port, an application from the plurality of software applications.

19. The method of claim 17, wherein the state table further includes a protocol.

20. The method of claim 1, further comprising:

combining two or more microflows from the plurality of micro-flows, wherein the two or more micro-flows are related to a single application from the plurality of software applications.

21. The method of claim 1, further comprising:

combining two or more microflows from the plurality of micro-flows, wherein the two or more micro-flows evidence similar traffic performance, the traffic performance characterized by one or more of a delay, a jitter, and a loss of the two or more microflows.

22. The method of claim 1, further comprising:

periodically measuring a status of the packet-switched network in real-time.

23. The method of claim 22, wherein the status of the packet-switch network includes measurements of a current delay, a current jitter, and a current loss on the packet-switched network.

24. The method of claim 22, further including:

re-mapping the plurality of micro-flows to the plurality of label-switched paths in response to one or more events on the packet switched network.

25. The method of claim 24, wherein the one more events on the packet-switched network comprises a surge in network traffic.

26. The method of claim 24, wherein the one or more events includes a security violation on the packet-switched network.

27. The method of claim 26, wherein security violation includes a Denial of Service Attack on the packet-switched network.

28. The method of claim 26, wherein the one or more events includes a SYN Flood on the packet-switched network.

29. The method of claim 24, wherein the one or more events increases jitter on the packet-switched network.

30. The method of claim 24, wherein the one or more events increases delay on the packet-switched network.

31. The method of claim 24, wherein the one or more events increases packet drops on the packet-switched network.

32. A node on a packet-switched network, the packet-switched network in communication via a label-switching protocol, the node comprising:

one or more interfaces coupled to the packet-switched network;

a plurality of label-switched paths coupling the node to one or more destination nodes, wherein node is in communication with the one or more destination nodes via the label-switching protocol over the packet-switched network, wherein the node is operative to monitor a current status network performance of the plurality of label-switched paths in real-time;

one or more tables identifying a plurality of micro-flows traversing the packet-switched network via the node, the one or more micro-flows including network traffic to the one or more destination nodes for a distinct software application from a plurality of software applications, each of the plurality of software applications having a distinct service-level requirement, the distinct service-level requirement including one or more of;

a bandwidth requirement and a priority amongst the plurality of software applications;

wherein the node is further operative to re-map the plurality of micro-flows to the plurality of label-switched paths periodically based on the distinct service-level requirement of each of the plurality of software applications and the current network performance of the plurality of label-switched paths.

33. The node of claim 32, wherein the plurality of software applications database applications includes one or more of:

virtual private network applications, multimedia streaming applications, e-mail applications, web applications, internet telephony applications, storage area networking applications, file transfer applications, peer-to-peer networking applications.

34. The node of claim 32, wherein the node further comprises:

a database of signatures for network traffic traversing the node, the signatures identifying one or more software applications related to the network traffic.

35. The node of claim 34, wherein the node further comprises:

a database of policies to ensure the distinct service-level requirement of each of the plurality of software applications.

36. The node of claim 34, wherein the node further comprises one or more processes for reading signatures for network traffic traversing the node.

37. The node of claim 36, wherein the node is operative to periodically re-map the network traffic traversing node to the plurality of micro-flows in response to reading signature for the network traffic traversing the node.