OAM State Machine Mapper for MPLS Network Interworking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current MPLS-TP networks face complexity in interconnecting nodes with different OAM implementations, such as BFD and BHH, which leads to network manageability issues and increased operational expenses due to the need for terminating and interworking OAM paths at each side of the connecting points, limiting end-to-end LSP and PW design.
Innovation Solution
A node with OAM state machine mapping capabilities that translates and exchanges OAM information between different OAM state machines, allowing for seamless communication across boundaries, enabling nodes with different OAM standards to operate without path termination, thus supporting data traffic paths and reducing vendor lock-in.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If nodes with different OAM implementations (e.g., BFD and BHH) are interconnected, then network versatility and vendor flexibility are improved, but path termination and OAM information demultiplexing are required at boundaries, increasing network complexity and operational expenses
Solution Approach 1:
The patent introduces an OAM state machine mapper as an intermediary component that translates between different OAM state machines (e.g., BFD and BHH). This mapper acts as a mediator at network boundaries, enabling nodes with different OAM implementations to interoperate without requiring path termination or complex manual demultiplexing, thus reducing network complexity while maintaining versatility
Solution Approach 2:
The OAM state machine mapper is designed to handle multiple OAM state machines universally. A single mapper can translate between BFD, BHH, and other OAM implementations, making the system multi-functional and adaptable to different vendor technologies without requiring separate handling mechanisms for each OAM type
2Adaptability or versatility
If OAM paths are terminated at network boundaries to support incompatible nodes, then interoperability between different vendors is improved, but end-to-end LSP and PW design is limited and operational expenses increase
Solution Approach 1:
The OAM state machine mapper serves as a transparent intermediary that enables end-to-end OAM information exchange across vendor boundaries without requiring path termination. The mapper translates OAM state machines at the boundary while allowing the path to continue seamlessly, thus maintaining end-to-end design capability while supporting multi-vendor interoperability
Solution Approach 2:
The patent enables continuous OAM information exchange across network boundaries by translating state machines at the boundary rather than terminating the path. This maintains the continuity of OAM supervision and management functions throughout the entire path, allowing end-to-end LSP and PW design to remain effective across heterogeneous networks
Data Source
AI summary
A node (110) for an MPLS telecommunications network has interfaces (100) for OAM information exchange relating to a path for data traffic, between first and second other nodes each operating according to different OAM state machines for OAM information exchange. An OAM state machine mapper (120) maps the states of either of the different OAM state machines of the first and second other nodes into states recognized by the other of the different OAM state machines. OAM information exchange is according to either the first or the second OAM state machine and according to states mapped from the other of the OAM state machines, to support the path for data traffic through the node. By such mapping of the different states OAM information can be exchanged across corresponding boundaries and so paths no longer need to be terminated at the boundary to enable end to end operations.