In-situ OAM Trace Extension with Cascade Bitmap
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Ethernet networks lack support for certain Operation, Administration, and Maintenance (OAM) operations, limiting the ability to manage and diagnose issues, as they do not allow for fault detection, isolation, and other network management functions.
Innovation Solution
A method is introduced to modify data packets by encapsulating an OAM header with a segment size field and a remaining hop count field, partitioning the data path into fixed segments, and collecting data at each node, which is then reported to a collection entity when the hop count reaches zero, allowing for efficient network management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If Ethernet networks use standard OAM operations, then network management capability is improved, but Ethernet protocol compatibility is worsened
Solution Approach 1:
The data path is divided into multiple segments with configurable segment sizes. OAM operations are performed independently within each segment rather than across the entire path, allowing Ethernet networks to support advanced OAM capabilities while maintaining protocol compatibility at each hop. The segmentation enables fault isolation to specific segments without affecting the entire network path.
Solution Approach 2:
The patent implements nested OAM headers where segment OAM headers are embedded within the overall OAM structure. Each segment contains its own OAM header that is nested within the parent OAM framework, allowing multiple levels of OAM operations to coexist. This nested structure enables rich OAM functionality while maintaining compatibility with standard Ethernet protocols at each layer.
2Measurement precision
If OAM data is collected at every node along the data path, then fault detection precision is improved, but network overhead is worsened
Solution Approach 1:
Instead of collecting OAM data at every node across the entire path, the patent segments the path and collects data only within each segment. This reduces the total quantity of OAM data transmitted while maintaining sufficient fault detection precision within each manageable segment. The segment size can be configured to balance between detection precision and overhead.
Solution Approach 2:
The patent extracts and removes OAM data from the data path at segment boundaries rather than carrying it throughout the entire path. By taking out OAM data at intermediate points and transmitting only essential information forward, the network overhead is reduced while fault detection capability is maintained through periodic data collection at strategic nodes.
3Measurement precision
If the data path is divided into smaller segments, then fault isolation capability is improved, but OAM header complexity is worsened
Solution Approach 1:
The data path is divided into segments with a configurable segment size field in the OAM header. This segmentation improves fault isolation capability by limiting the scope of OAM operations to manageable segments. The segment size parameter allows networks to balance between isolation precision and header complexity based on specific requirements.
Solution Approach 2:
The patent introduces a segment size parameter that can be dynamically adjusted to change the granularity of segmentation. By allowing parameter changes rather than fixed segmentation, the system can adapt the level of fault isolation needed without permanently increasing header complexity. The remaining hop count field also provides dynamic control over segment traversal.
Data Source
AI summary
The disclosure relates to technology for sending network management information in a network. A source edge node modifies data packets by encapsulating an operations, administration and maintenance (OAM) header in the data packets traversing a data path, and the OAM header includes a first indicator field. The source edge node also inserts a segment size field into the OAM header of the data packets based on an indication by the first indicator field, the segment size field indicating the data path is partitioned into segments based on a value of the segment size field.