MPLS Data Plane Header Extensions for Scalable OAM Encoding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current MPLS implementations face inefficiencies due to the need for separate extended special purpose labels, which increase label stack depth and are not scalable, and lack the ability to add ancillary data within or after the bottom-of-stack in MPLS packets.
Innovation Solution
Implementing new MPLS data plane extension headers that encode forwarding and OAM instructions as flags and opcodes, allowing for in-stack and bottom-of-stack extension headers to be added efficiently, without increasing label stack depth.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate extended special purpose labels are used to add ancillary data and instructions, then forwarding and OAM functionalities are enhanced, but label stack depth increases and scalability is reduced
Solution Approach 1:
The patent merges the functionality of separate extended special purpose labels with ancillary data into a unified extension header structure. The extension header contains both forwarding/OAM instructions and associated data in a single consolidated format, eliminating the need for multiple separate label stack entries and reducing overall stack depth while maintaining enhanced functionality
Solution Approach 2:
The extension header is designed as a universal structure that can carry multiple types of information (forwarding instructions, OAM data, ancillary information) within a single header format. This multi-functional approach allows the same header structure to serve multiple purposes without requiring separate specialized labels for each function
2Adaptability or versatility
If separate extended special purpose labels are used, then additional instructions can be added, but scalability is reduced
Solution Approach 1:
The extension header incorporates dynamic field structures with variable-length encodings and flexible instruction formats that can adapt to different network requirements. The header can be configured to carry different types and amounts of data depending on the specific forwarding or OAM needs, allowing the system to scale efficiently without being constrained by fixed rigid structures
3Quantity of substance
If label stack depth is increased to add ancillary data, then more data can be carried, but network burden increases
Solution Approach 1:
The patent implements a nested structure where ancillary data is embedded within the extension header that is itself attached to the MPLS packet. This nesting allows multiple levels of information organization (instructions nested within data nested within header nested within packet) maximizing the use of available space without requiring proportional increases in overall packet size or processing complexity
Data Source
AI summary
Systems and techniques are provided for implementing multiprotocol label switching (MPLS) header extensions. In some examples, a method can include, receiving, by a router of a MPLS network, a data packet. In some aspects, the method can include adding, by the router of the MPLS network, at least one entry to an MPLS stack of the data packet, wherein the at least one entry includes an MPLS extension indicator (MEI) that is associated with at least one of an in-stack extension header presence indicator (IPI) and a bottom-of-stack extension header presence indicator (BPI). In some examples, the method can include adding, based on the IPI and the BPI, at least one of an in-stack extension header and a bottom-of-stack extension header to the MPLS stack of the data packet.