System, apparatus and method for supporting constraint based routing for multi-protocol label switching traffic engineering in policy-based management

• US 7,539,741 B2
• Filed: 08/05/2003
• Issued: 05/26/2009
• Est. Priority Date: 04/30/2003
• Status: Expired due to Term

• Current Assignee: RPX Corporation
• Original Assignee: Nokia Solutions and Networks US LLC (Nokia Corporation)
• Inventors: Li, Man, Barnes, Roberto, Liong, Yin-Ling
• Primary Examiner(s): Hu, Jinsong
• Application Number:
  US10/635,205
• Publication Number:
  US 20040218535A1
• Time in Patent Office: 2,121 Days
• Field of Search: 709/220, 709/223, 709/228, 370/254, 370/255
• US Class Current: 709/223
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• 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 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/50 using label swapping, e.g. multi-protocol label switch [MPLS]

Abstract

A policy server is arranged to construct device-neutral policies for configuring CBR for MPLS traffic engineering across a network. The policy server translates the device-neutral policies into device-specific commands (e.g. link attribute definitions and affinity profiles). The policy server defines the link attributes, assigns the link attributes to network interfaces, establishes affinity profiles and attaches the affinity profiles to MPLS tunnels. The link attribute definitions and affinity profiles are shared across the network to construct the policies such that IP operators can configure CBR easily across a network.

Claims

1. A system for configuring constraint based routing in multi protocol label switching traffic engineering with a policy based management approach across a network, comprising:

network interfaces configured to have link attribute definitions set;

a memory configured to store affinity profiles configured to identify at least one link attribute as preferred or not preferred;

a policy server configured to attach the affinity profiles to a multi-protocol label switching tunnel such that the affinity profiles and the link attribute definitions are shared across a network to construct service and network policies; and

a link attribute definition object that is configured to define the semantics of the link attributes and the affinity profiles,

wherein the link attribute definition object is further configured to describe a policy target by defining a representation for each attribute bit and for each affinity bit in the affinity profile.

2. The system of claim 1, wherein the affinity profiles are device-neutral and wherein the policy server is further configured to translate the affinity profiles into device-specific commands.

3. The system of claim 1, wherein the policy server is further configured to assign the link attributes to the network interfaces by determining the current configuration of a muter, configuring the router, and issuing new commands based on the set of link attributes to be assigned.

4. The system of claim 1, wherein the policy server comprises a user interface that is configured to allow an operator to configure the service and network policies.

5. The system of claim 1, wherein the policy server is further configured to configure the multi-protocol label switching tunnels such that an operator can create an multi-protocol label switching tunnel by specifying end-point routers and inter-connecting topology.

6. The system of claim 1, further comprising a database configured for storing the affinity profiles, the link attribute definitions and the link attributes of each of the network interfaces.

7. The system of claim 1, wherein the representation comprises at least one of a bit position, an attribute name and category.

8. The system of claim 1, wherein the affinity profiles identify at least one link attribute as preferred and at least one link attribute as not preferred.

9. The system of claim 1, wherein the affinity profiles identify each link attribute as preferred, not preferred, or neutral.

10. A method for supporting constrain based routine for multi-protocol label switching traffic engineering across a network, comprising:

performing, by a computer processor defining link attributes;

assigning the link attributes to network interfaces;

establishing affinity profiles that identify at least one traffic engineering attribute as preferred or not preferred;

attaching the affinity profiles to multi-protocol label switching tunnels such that service and network policies are constructed across a network;

defining the semantics of the link attributes and the affinity profiles, and

defining a representation for each attribute bit and for each affinity bit in the affinity profile.

11. The method of claim 10, further comprising storing the affinity profiles, the link attribute definitions and the link attributes of each of said network interfaces in a database.

12. The method of claim 10, further comprising translating the amity profiles into device-specific commands.

13. The method of claim 10, further comprising storing device-neutral information associated with the affinity profiles in a database.

14. The method of claim 10, wherein assigning the link attributes to the network interfaces further comprises:

determining the command configuration of a router;

configuring the router; and

issuing new commands to the router based on the link attributes to be assigned.

15. An apparatus for configuring constraint based routing in multi protocol label switching traffic engineering with a policy based management approach across a network, comprising:

a computer processor configured to

define link attributes;

a an ass˜

ming means for assigning the link attributes to network interfaces;

establish affinity profiles that identify at least one traffic engineering attribute as preferred or not preferred; and

define the semantics of the link attributes and the affinity profiles; and

describe a policy target by defining a representation for each attribute bit and for each affinity bit in the affinity profile.

16. The apparatus of claim 15, wherein the processor is further configured to the affinity profiles into device-specific command.

17. A computer-readable storage medium encoded with a computer program configured to control a processor to perform:

defining link attributes;

assigning the link attributes to network interfaces;

establishing affinity profiles that identify at least one traffic engineering attribute as preferred or not preferred; and

attaching the affinity profiles to multi-protocol label switching tunnels such that service and network policies are constructed across a network;

defining the semantics of the link attributes and the affinity profiles, and

defining a representation for each attribute bit and for each affinity bit in the affinity profile.