Segment Routing Label Switch Paths in NFV Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In communications networks, especially in NFV environments, existing technologies face challenges in efficiently supporting Segment Routed Label Switched Paths (SR LSPs) without the need for RSVP-TE or LDP signaling protocols, which limits scalability and agility in setting up large numbers of LSPs, and also struggle with handling RSVP messages due to the lack of control plane functions in forwarding engines.
Innovation Solution
The implementation of a system where control plane engines, such as XR controllers, proxy control plane functions for forwarding engines, enabling the establishment of SR LSPs with or without traffic engineering, and handle RSVP messages by identifying and forwarding them to the appropriate control plane engines, thereby simplifying network operations and enhancing scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If RSVP-TE or LDP signaling protocols are deployed to set up MPLS LSPs, then reliable path establishment and QoS guarantees are achieved, but network operation complexity increases and scalability deteriorates
Solution Approach 1:
The patent extracts the signaling protocol functionality from the forwarding engines and places it in control plane engines. This separation removes the complex RSVP-TE or LDP signaling processing from the data plane forwarding devices, achieving simpler network operation while maintaining reliable path establishment through the control plane's dedicated signaling handling.
Solution Approach 2:
The control plane engine acts as an intermediary between the forwarding engines and the signaling protocol. It receives signaling messages, processes them, and translates them into forwarding instructions for the forwarding engines, thereby simplifying the overall network operation while ensuring reliable path setup.
2Reliability
If RSVP-TE or LDP signaling protocols are deployed to set up MPLS LSPs, then QoS guarantees and path protection are achieved, but scalability and agility in setting up large numbers of LSPs deteriorate
Solution Approach 1:
By extracting signaling protocol processing from forwarding engines to control plane engines, the system enables centralized management of multiple LSPs. The control plane engine can efficiently handle QoS guarantees and path protection while scaling to support large numbers of LSPs through automated control plane operations.
Solution Approach 2:
The control plane engine can replicate and distribute forwarding instructions to multiple forwarding engines simultaneously, enabling rapid setup of large numbers of LSPs while maintaining consistent QoS policies across the network through centralized control.
3Ease of operation
If control plane functions are integrated into forwarding engines, then direct LSP setup capability is achieved, but handling RSVP messages becomes difficult due to lack of control plane functions
Solution Approach 1:
The patent segments control plane functions from forwarding engine functions. The forwarding engine handles data plane forwarding operations, while the control plane engine handles RSVP message processing and LSP setup control. This segmentation allows each component to specialize in its core function, improving both direct LSP setup capability and RSVP message handling.
Solution Approach 2:
The control plane engine serves as an intermediary that receives RSVP messages, processes them according to QoS and path protection requirements, and generates appropriate forwarding instructions for the forwarding engines. This intermediary approach enables proper RSVP message handling while maintaining simple forwarding engine operations.
Data Source
AI summary
A method is provided in one example embodiment and includes receiving a request to create a path through a network, wherein the path originates on a first network device and terminates on the second network device; identifying a first controller associated with the first network device, wherein the first controller proxies control plane functions for the first network device; identifying a second controller associated with the second network device, wherein the second controller proxies control plane functions for the second network device; and computing the path using the first controller as a source and the second controller as a destination. The first controller installs the computed path on the first network device and the second controller installs the computed path on the second network device.