Packet flow bifurcation and analysis

• US 20070058632A1
• Filed: 09/12/2005
• Published: 03/15/2007
• Est. Priority Date: 09/12/2005
• Status: Active Grant

• Current Assignee: Tellabs Communications Canada Ltd. (Infinera Corp.)
• Original Assignee: Zeugma Systems Canada, Inc.
• Inventors: Luft, Siegfried, Back, Jonathan
• Granted Patent: US 7,508,764 B2
• Time in Patent Office: Days
• US Class Current: 370/392
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/22 Traffic shaping
• 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 49/355 Application aware switches, e.g. for HTTP
• CPC Class Codes: H04L 49/40 Constructional details, e.g. power supply, mechanical construction or backplane

Abstract

Methods and apparatus for optimum matching of a traffic profile with an individual traffic flow using flow bifurcation and analysis. Bifurcation and duplication of packets that make up a flow received at an ingress element are forwarded to each of egress traffic and computation processor resources, such that egress traffic operations and traffic analysis operations may be performed concurrently without introducing jitter or delay in either bifurcated processing path. The traffic analysis includes maintaining flow statistics, flow stateful information and classifying the flow as a particular application traffic type. The optimum traffic profile for this application traffic type is then selected and applied to the individual flow. The traffic analysis data is forwarded to ingress and egress processing elements in real time, and ingress and egress traffic processing operations are dynamically adjusted in view of the traffic analysis data.

Claims

1. A method, comprising:

receiving packets comprising an ingress traffic flow at a network element;

bifurcating processing of the packets to an egress traffic processor and a computation processor;

performing egress traffic flow operations at the egress traffic processor, the egress traffic flow operations assigning the packets to an egress traffic flow; and

performing traffic analysis operations at the computation processor concurrently with the egress traffic flow operations, the traffic analysis operations generating traffic analysis data corresponding to the ingress traffic flow.

2. The method of claim 1, wherein the operation of bifurcating processing of the packets introduces no additional latency into the processing of the ingress or egress traffic flows.

3. The method of claim 1, further comprising:

receiving packets corresponding to multiple ingress traffic flows at the network element; and

assigning packets associated with multiple ingress traffic flows to egress traffic flows in view of traffic profiles generated from the traffic analysis data for the multiple ingress traffic flows.

4. The method of claim 1, further comprising:

maintaining flow state information for the ingress traffic flow; and

altering traffic analysis operations in view of the flow state information.

5. The method of claim 1, further comprising:

dynamically adjusting an egress traffic profile applied to the egress traffic flow in view of the ingress traffic flow traffic analysis data that is generated.

6. The method of claim 1, wherein the network element comprises a modular chassis including a plurality of traffic blades and compute blades, the method further comprising:

receiving the packets at an ingress traffic blade;

performing primary classification of the packets to identify a subscriber flow associated with the packets; and

based on the subscriber flow,

identifying an egress traffic blade to be employed for the egress traffic flow operations and sending a first copy of the packets to that egress traffic blade; and

identifying a computation blade to be employed for the traffic analysis operations and sending a second copy of the packets to that compute blade.

7. The method of claim 6, further comprising:

detecting initiation of a subscriber session;

storing data associating traffic blade and computation resources with a subscriber flow corresponding to the subscriber session.

8. The method of claim 7, wherein a compute blade includes multiple compute nodes, and associating computation resources with the subscriber flow identifies a compute node on a compute blade to be employed for performing traffic analysis operations.

9. The method of claim 6, wherein the copying the first and second packets to the egress traffic blade and compute blade comprises:

buffering packets received at the ingress traffic blade in a backplane fabric switch of the ingress traffic blade;

transmitting the first copy of the packets across a mesh interconnect to a backplane fabric switch of the egress traffic blade; and

transmitting the second copy of the packets across the mesh interconnect to a backplane fabric switch of the compute blade.

10. The method of claim 9, wherein the backplane fabric switches employ an insertion ring transfer scheme to transfer a copy of a packet buffered in the backplane fabric switch of the ingress traffic blades to target egress traffic and compute blades.

11. The method of claim 6, wherein the primary classification operation comprises performing a 5-Tuple classification.

12. The method of claim 1, further comprising:

providing the generated traffic flow analysis data to the ingress processor;

and adjusting policing performed on the ingress traffic flow in view of the traffic flow analysis data.

13. The method of claim 1, further comprising:

performing classification of the packets to classify the ingress traffic flow as a particular application traffic type.

14. The method of claim 13, further comprising:

employing deep packet inspection to classify the ingress traffic flow.

15. An apparatus, comprising:

a plurality of ingress traffic processors;

a plurality of egress traffic processors, communicatively coupled to the ingress traffic processors;

a plurality of computation processors, communicatively coupled to the ingress and egress traffic processors; and

software components distributed across the plurality of ingress traffic processors, egress traffic processors and computation processors, the software to execute on the plurality of ingress traffic processors, egress traffic processors and computation processors to perform operations including,

performing ingress processing operations on packets comprising an ingress traffic flow received at the apparatus;

bifurcating processing of the packets to an egress traffic processor and a computation processor;

performing egress traffic flow operations at the egress traffic processor, the egress traffic flow operations assigning the packets to an egress traffic flow; and

performing traffic analysis operations at the computation processor concurrently with the egress traffic flow operations, the traffic analysis operations generating traffic profile data corresponding to the ingress traffic flow.

16. The apparatus of claim 15, wherein execution of the software performs further operations comprising:

performing ingress processing operations on packets corresponding to multiple ingress traffic flows received at the apparatus;

maintaining flow state information for each of the multiple ingress traffic flows; and

altering traffic analysis operations in view of the flow state information.

17. The apparatus of claim 15, wherein execution of the software performs further operations comprising:

dynamically adjusting an egress traffic profile applied to the egress traffic flow in view of the ingress traffic flow traffic profile data that is generated.

18. The apparatus of claim 15, wherein execution of the software performs further operations comprising:

providing the generated traffic flow profile data to the ingress processor;

and adjusting policing performed on the ingress traffic flow in view of the traffic flow profile data.

19. The apparatus of claim 15, wherein execution of the software performs further operations comprising:

performing classification of the packets to classify the ingress traffic flow as a particular application traffic type.

20. The apparatus of claim 15, wherein execution of the software performs further operations comprising:

associating the ingress traffic flow with a subscriber flow;

identifying processing resources allocated to the subscriber flow, the processing resources including a target egress traffic processor and a target computation processor; and

bifurcating processing of the packets by transmitting a copy of each packet to each of the target egress traffic processor and the target computation processor.

21. An apparatus, comprising:

a chassis having a plurality of slots and including a backplane providing a mesh interconnect between the slots;

a plurality of traffic blades, each installed in the chassis in a respective slot and including a backplane interface coupled to the backplane, the plurality of traffic blades including ingress traffic blades and egress traffic blades;

a plurality of compute blades, each installed in the chassis in a respective slot and including a backplane interface coupled to the backplane; and

software components distributed across the plurality of traffic blades and compute blades, the software components to execute on processing elements hosted by the traffic blades and compute blades to perform operations including,

performing ingress processing for packets received at an ingress traffic blade, the ingress processing including performing primary classification of the packets to identify a subscriber flow associated with the packets;

based on the subscriber flow,

identifying an egress traffic blade to be employed for the egress traffic flow operations and sending a first copy of the packets to that egress traffic blade; and

identifying a computation blade to be employed for the traffic analysis operations and sending a second copy of the packets to that compute blade,

performing egress traffic operations for the subscriber flow on the egress traffic blade using the first copy of packets; and

concurrently performing traffic analysis operations on the computation blade using the second copy of packets.

22. The apparatus of claim 21, wherein a compute blade includes a plurality of computing elements organized as compute nodes, and execution of the software components perform further operations comprising:

identifying a compute node to be employed for traffic analysis operations;

sending a copy of the packets to that compute node; and

performing the traffic analysis operations, at least in part, on that compute node.

23. The apparatus of claim 21, wherein copying the first and second packets to the egress traffic blade and compute blade comprises:

buffering packets received at the ingress traffic blade in a backplane fabric switch of the ingress traffic blade;

transmitting the first copy of the packets across the mesh interconnect to a backplane fabric switch of the egress traffic blade; and

transmitting the second copy of the packets across the mesh interconnect to a backplane fabric switch of the compute blade.

24. The apparatus of claim 23, wherein the backplane fabric switches employ an insertion ring transfer scheme to transfer a copy of a packet buffered in the backplane fabric switch of the ingress traffic blades to target egress traffic and compute blades.

25. The apparatus of claim 21, wherein execution of the software performs further operations comprising:

generating traffic flow profile data via the traffic analysis operations;

providing the traffic flow profile data to the ingress traffic blade; and

adjusting policing performed on the subscriber flow in view of the traffic flow profile data.

26. The apparatus of claim 21, wherein execution of the software performs further operations comprising:

effecting a distributed traffic analysis database in which traffic analysis data is stored, the distributed traffic analysis database including local instances of the database hosted on respective traffic and compute blades;

updating a local instance of the traffic analysis database with traffic analysis data generated by its host blade; and

propagating the update to other local instances of the traffic analysis database hosted by other blades.

27. The apparatus of claim 21, wherein execution of the software performs further operations comprising:

performing classification of the packets to classify the subscriber flow as a particular application traffic type; and

managing egress flow operations corresponding to the subscriber flow based on its application traffic type.

28. The apparatus of claim 27, wherein an ingress traffic blade includes a network processor unit (NPU) and a host processor, and wherein classification of packets into particular application traffic types is performed by:

employing the NPU to perform a first level classification using the NPU; and

employing the host processor to perform at least one additional level of classification including deep packet inspection.

29. The apparatus of claim 21, wherein the chassis comprises an Advanced Telecommunication and Computing Architecture (ATCA) chassis.