Class-Based Traffic Engineering in IP Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current traffic engineering mechanisms in IP networks require new hardware or data plane support, are limited to specific IP versions, and do not provide bandwidth guarantees, making them inefficient and inflexible.
Innovation Solution
Implementing class-based traffic engineering using Interior Gateway Protocols (IGP) such as IS-IS or OSPF, which allows routers to compute and advertise constrained paths without relying on signaling protocols like RSVP-TE or SR-TE, enabling IP forwarding for both IPv4 and IPv6 and avoiding encapsulation limitations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MPLS protocols (RSVP-TE or SR-TE) are used for traffic engineering, then traffic patterns can be engineered according to routing information, but new hardware requirements and hardware limitations are introduced
Solution Approach 1:
The patent replaces the MPLS signaling mechanism (which requires specialized hardware for label processing and tunnel establishment) with a pure IP-based routing approach using extended BGP attributes. This substitution eliminates the need for MPLS-specific hardware while achieving the same traffic engineering objectives through software-based route selection and policy routing.
2Adaptability or versatility
If IP tunneling (IP-in-IP or GRE) is used between routers, then traffic can be encapsulated, but bandwidth guarantees are not provided and encapsulation limitations exist
Solution Approach 1:
The patent changes the approach from modifying packet structure (encapsulation) to modifying routing parameters. By extending BGP attributes to include traffic engineering information such as bandwidth requirements, latency constraints, and path preferences, the system can guarantee bandwidth and QoS through intelligent route selection rather than through encapsulation mechanisms that lack enforcement capability.
3Speed
If MPLS labels are prepended to traffic for Label Switched Path forwarding, then packets can be forwarded along a particular path, but the mechanism is limited to specific IP versions and requires additional processing
Solution Approach 1:
The patent creates a universal traffic engineering solution that works across IPv4, IPv6, and future IP versions by using extended BGP attributes rather than version-specific mechanisms. The extended path attributes and community values provide multi-functional capability, enabling traffic engineering for any IP version without requiring separate implementations, thus achieving both speed and versatility.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques are described for class-based traffic engineering in an IP network. For example, routers of an IP network may establish one or more constrained traffic engineered paths using a link-state protocol (e.g., IGP) without using signaling protocols, such as RSVP or SPRING, or encapsulating packets over MPLS. For example, an egress router of the IP network may receive a capability message specifying the capability of routers to compute a constrained path to the egress router, wherein the capability message comprises path computation information including an identifier of a path computation algorithm to be used by the one or more of the plurality of network devices to reach the egress network device. The egress router may advertise a reachability message including a destination IP prefix and the identifier of the path computation algorithm to cause routers in the IP network to compute the constrained path to reach the egress router.