MPLS Extension Headers for In-Network Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
MPLS networks are not designed to support multiple in-network services such as Network Service Header (NSH), In-situ Operations, Administration, and Maintenance (IOAM), Segment Routing (SR), and network programming, limiting their functionality and requiring full label stack scanning that can degrade performance.
Innovation Solution
The implementation of MPLS Extension Headers that allow for the addition of multiple in-network services by modifying packets with additional headers and indications within the MPLS label stack, enabling support for services like NSH, IOAM, and SR without extensive overhead, and allowing for backwards compatibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MPLS networks use full label stack scanning to support in-network services, then service functionality is improved, but forwarding performance degrades
Solution Approach 1:
The patent segments the label stack into two functional parts: a conventional MPLS label stack for forwarding decisions and a separate extension header area for in-network services. This segmentation allows routers to scan only the extension header area (containing 1-2 headers) rather than the entire label stack, significantly reducing scanning time while maintaining service functionality. The extension header area is positioned after the conventional label stack and contains service-specific information such as NSH, IOAM, or SR headers.
Solution Approach 2:
The patent introduces an intermediary structure (extension header area with indication bits in the label stack) that mediates between the conventional MPLS forwarding mechanism and in-network services. The indication bits in the label stack serve as a mediator signal to routers, telling them to expect extension headers after the conventional label stack. This intermediary structure enables service functionality without requiring routers to scan the entire label stack, thus preserving forwarding performance.
2Adaptability or versatility
If MPLS networks add extension headers for in-network services, then service functionality is improved, but packet overhead increases
Solution Approach 1:
The patent applies local quality by adding extension headers only when needed for specific in-network services, rather than universally adding the same headers to all packets. The extension header area is positioned at the end of the packet structure, and routers can selectively process these headers based on service requirements. This allows different packet types to have different effective overheads, optimizing the balance between service functionality and packet size.
Solution Approach 2:
The patent implements partial action by adding only the necessary extension headers for specific services rather than comprehensive headers for all possible services. The extension header area contains 1-2 service-specific headers (such as NSH or IOAM) rather than multiple comprehensive headers. This partial approach provides sufficient functionality for current needs while minimizing unnecessary overhead, and the structure can be extended if needed.
3Adaptability or versatility
If MPLS networks modify packet structure to add services, then adaptability is improved, but backward compatibility deteriorates
Solution Approach 1:
The patent uses the nested doll principle by placing extension headers inside the existing MPLS packet structure without replacing the conventional label stack. The extension header area is nested after the conventional label stack, maintaining the original MPLS packet format as the outer structure. Routers can selectively process the extension headers if they support the new services, while ignoring them if they don't, thus maintaining backward compatibility. Existing MPLS routers continue to function normally, while upgraded routers can utilize the extension headers for advanced services.
Data Source
AI summary
Described herein are methods and devices (e.g., routers) that add network services to a multiprotocol label switching (MPLS) network. A method can include a network device of the MPLS network receiving a packet, the network device of the MPLS network modifying the packet by adding multiple MPLS extension headers, wherein each of the multiple MPLS extension headers added to the packet is used to support a different one of multiple network services for the MPLS network, and the network device of the MPLS network forwarding the packet as modified to another network device of the MPLS network.