System and Method for Managing Network Flows Based on Policy Criteria

• US 20090100506A1
• Filed: 10/11/2007
• Published: 04/16/2009
• Est. Priority Date: 10/11/2007
• Status: Abandoned Application

• Current Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Whang, Steve, Ghang, Phil, Haffar, Mounif
• Application Number:
  US11/870,694
• Publication Number:
  US 20090100506A1
• Time in Patent Office: Days
• US Class Current: 726/4
• 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 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/20 Traffic policing

Abstract

A policy-based network flow management system and method. In one embodiment, various policy conditions are configured based at least in part upon source network conditions and multi-layer information (e.g., Layer 2, Layer 3, and so on) associated with network traffic. Where network traffic from a content requester is determined to satisfy a policy condition, a corresponding policy action is effectuated, e.g., dropping the network traffic, forwarding the network traffic, redirecting the network traffic, or queuing the network traffic.

Claims

1. A policy-based network flow management method, comprising:

determining whether network traffic received from a requester satisfies a policy condition that is configured based at least in part upon one of a source network condition associated with said requester and multi-layer information associated with said network traffic; and

responsive to said determining, applying a policy action corresponding to said policy condition, said policy action including at least one of dropping said network traffic, forwarding said network traffic, redirecting said network traffic, and queuing said network traffic.

2. The policy-based network flow management method as recited in claim 1, further including determining whether said requester is an authorized subscriber.

3. The policy-based network flow management method as recited in claim 1, wherein said source network condition includes a source address associated with said requester.

4. The policy-based network flow management method as recited in claim 1, wherein said policy condition is further configured based on a destination network condition associated with a provider entity towards which said network traffic is directed.

5. The policy-based network flow management method as recited in claim 1, wherein said multi-layer information includes Open System Interconnect (OSI) Layer 1 information.

6. The policy-based network flow management method as recited in claim 1, wherein said multi-layer information includes Open System Interconnect (OSI) Layer 2 information.

7. The policy-based network flow management method as recited in claim 1, wherein said multi-layer information includes Open System Interconnect (OSI) Layer 3 information.

8. The policy-based network flow management method as recited in claim 1, wherein said multi-layer information includes Open System Interconnect (OSI) Layer 4 information.

9. A policy-based network flow management system, comprising:

means for determining whether network traffic received from a requester satisfies a policy condition that is configured based at least in part upon one of a source network condition associated with said requester and multi-layer information associated with said network traffic; and

means, operable to responsive to said determining, for applying a policy action corresponding to said policy condition, said policy action including at least one of dropping said network traffic, forwarding said network traffic, redirecting said network traffic, and queuing said network traffic.

10. The policy-based network flow management system as recited in claim 9, further including means for determining whether said requester is an authorized subscriber.

11. The policy-based network flow management system as recited in claim 9, wherein said source network condition includes a source address associated with said requester.

12. The policy-based network flow management system as recited in claim 9, wherein said policy condition is further configured based on a destination network condition associated with a provider entity towards which said network traffic is directed.

13. The policy-based network flow management system as recited in claim 9, wherein said multi-layer information includes Open System Interconnect (OSI) Layer 1 information.

14. The policy-based network flow management system as recited in claim 9, wherein said multi-layer information includes Open System Interconnect (OSI) Layer 2 information.

15. The policy-based network flow management system as recited in claim 9, wherein said multi-layer information includes Open System Interconnect (OSI) Layer 3 information.

16. The policy-based network flow management system as recited in claim 9, wherein said multi-layer information includes Open System Interconnect (OSI) Layer 4 information.

17. A network node, comprising:

means for maintaining at least one pointer table associated with a plurality of policy application servers, wherein said policy application servers are grouped into clusters based on an access control list, said policy application servers operating to apply one or more policy actions with respect to network traffic generated by content requesters;

means for polling said policy application servers to determine status of said policy application servers; and

means for updating said at least one pointer table based upon said polling.

18. The network node as recited in claim 17, wherein said access control list is operable to discriminate based on source address information associated with said content requesters.

19. The network node as recited in claim 17, wherein said content requesters include home subscribers.

20. The network node as recited in claim 17, wherein said content requesters include enterprise subscribers.

21. The network node as recited in claim 17, wherein said polling is performed periodically.

22. The network node as recited in claim 17, wherein each of said clusters is interfaced via a corresponding virtual local area network (VLAN) supported by said network node.