Patent Application
20060206606
1. Field of the Invention
The present invention generally relates to traffic management within an internet protocol (IP) based communications network and, more particularly, to the creation and management of route groups within an IP-based communications network.
2. Description of the Background Art
Presently, IP-based networks are designed to provide communications connectivity for IP packets of information from one point within a network to another point within a network. A customer generally establishes a policy with regard to the routing of their data through an IP based network. The policies established for the sites within the network having the same routing policies define the route groups. A communications network service provider defines the routing of the communications traffic between the two points using the policies established by the customers. As such, traffic routing is controlled by the service provider; however, the route group policies are defined by the customers. In some situations, the network service customers desire to have particular traffic regions defined for their communications traffic (i.e., have certain traffic confined to a particular geographic region). Presently, such specific routing protocols for network traffic require special, individualized programming of the edge routers within the network. Once grouped, the programmed edge routers and the traffic patterns they control are generally static. Such static traffic patterns do not provide the flexibility or the granularity that customers' desire in controlling their network traffic. Also, programming each edge router consistently per customer is operationally very complex.
Therefore, there is a need in the art for a dynamic and granular traffic management technique that will improve the efficiency in defining and operating route groups within an IP communications network.
The present invention is a method and apparatus for providing traffic management through dynamic and granular definitions of route groups. Within a communications network, a traffic routing control unit (e.g., an intelligent route service control point (IRSCP)) establishes the route group assignments to fulfill a customer's routing policy, determines protocol control values to be set within each edge router of the network to fulfill the group assignments, and uses border gateway protocol (BGP) to set the protocol control values in the edge routers to facilitate fulfilling the route group assignments. Using the traffic routing control unit and programming the protocol control values of the edge routers, enables the network to be flexibly defined and the traffic routing within the network to have very granular control.
So that the manner in which the above recited features of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.
The IRSCP 106 dynamically adjusts traffic flow through the network 104 as described in commonly assigned U.S. patent application Ser. No. 11/019,845, filed Dec. 22, 2004, Attorney Docket No. 2004-0085, which is incorporated by reference herein in its entirety. The IRSCP 106 uses a border gateway protocol (BGP) and an interior border gateway protocol (IBGP) to control the routing protocols of the edge routers 108, 112, 116, 122, 126 and 130 within the network 104. The route groups can be defined (but not limited) by establishing at least one of route preferences, route denial parameters, and route filtering.
Once the policy is created, at step 206, the customer communicates the policy to the service provider. The policy is generally submitted to the IRSCP using customer peering protocol control values (e.g., BGP Community values)or an e-portal.
At step 206, the method 200 determines route group assignments for each route between points (nodes) of the network as dictated by the policy. The method identifies each possible route from customer site to customer site to fulfill the routing requirements of the customer. To facilitate this traffic routing protocol, there may be a number of routers that can be used to handle the traffic from, for example, customer site 110 to customer site 120. As such, a route group is defined, by the routing preferences of the policy. At step 208, the IRSCP 106 is used to define all the routes that can handle the traffic to fulfill the requirements of the customer. The route definition step is performed for each and every one of the customer site to customer site traffic pattern requirements.
At step 210, the IRSCP 106 determines the protocol control values to be set within each router to fulfill the group assignments. In one embodiment of the invention, there are seven BGP protocol control values that can be set in any router. The protocol control values are referred to in BGP as the community values (i.e., local preferences). These community values include five route preferences, one route denial and another value that is used for denying the route for all route groups except for a specific route group. A customer can use these seven defined community values to communicate their policies to the provider. In one embodiment, any given edge router may be included in up to thirty two different route groups within various network configurations. As such an edge router may be contained within a number of different route groups defining different regions of the network. Once the community values are determined for each edge router to fulfill the policy requirements, the method 200 proceeds to step 212. At step 212, the IRSCP creates BGP messages to communicate the customer policy into the edge routers by using “control knobs” such as local preferences. IRSCP can use other protocols besides BGP or use other “knobs” besides local preference to communicate the routing policy to the edge routers.
At step 214, the IRSCP pushes the BGP messages through the edge routers to institute the policy. At step 216, the edge routers set their local preferences in accordance with the BGP messages. As such, the customer's routing policy is specifically implemented with granularity at the individual edge router. The method ends at step 218.
If a customer requires a change in their policy, the customer communicates the change to the IRSCP and method 200 is performed to update the local preferences to fulfill the new requirements. As such, the invention can be used to dynamically adjust the network routing to fulfill the changing needs of a customer.
In this manner the centralized IRSCP 106 can define the traffic routing protocols for all of the edge routers 108, 112, 116, 122, 126, and 130 within a network 104. The protocols can be used to define a plurality of regions for traffic propagation. The plurality of regions may be defined to enable a single customer to have multiple areas with traffic that does not cross between the two regions or it may enable multiple customers of the same network provider to require their traffic to be separately routed through the network. In other instances, the regions may be different regions of the world that cannot have their traffic pass from one region to another. As such, the invention enable those regions to be segregated. Such segregation may be desired to fulfill government regulations as well as customer requirements.
Traffic may also be passed between regions in a specific manner where not all the traffic from one region is passed through to another region, but the traffic may be filtered to allow certain traffic to pass. Such a filtering function may be accomplished by the IRSCP 106 programming an edge router to forward certain traffic to an edge router within a different region. For example, edge router 116 may be programmed to send certain traffic to edge router 122, where routers 116 and 122 are in different regions. Such filtering may be required to meet certain customer requirements.
Consequently, the IRSCP 106 can be used to provide route grouping and traffic filtering on a dynamic and granular basis. Network customers receive flexibility in defining the route groups and adjusting the route groups to fulfill their specific traffic routing requirements.
While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.
