OAM Processing Engine Flow Classification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network devices face challenges in efficiently processing Operations, Administration, and Maintenance (OAM) data units across multiple communication flows, requiring effective identification and processing of OAM packets to monitor connectivity and detect link failures, while existing solutions often struggle with scalability and real-time processing requirements.
Innovation Solution
A multi-stage OAM processing engine is implemented in network devices, utilizing a content-addressable memory (CAM) for fast flow classification and a random access memory (RAM) for flexible processing actions, allowing for efficient identification and processing of OAM data units by retrieving specific entries from a memory that indicate how to handle OAM packets based on their flow.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network devices process OAM data units for multiple communication flows, then connectivity monitoring and link failure detection capabilities are improved, but processing complexity and device resource requirements increase
Solution Approach 1:
The patent segments OAM data unit processing into distinct stages: a first stage for identifying communication flows using flow identifiers, and a second stage for processing OAM actions. This segmentation allows the device to handle multiple flows systematically without overwhelming complexity, as each stage focuses on a specific aspect of processing.
Solution Approach 2:
The patent introduces an intermediary data structure (the second data structure with flow identifiers and associated OAM actions) that mediates between the incoming OAM data units and the processing logic. This intermediary structure organizes the complexity by pre-establishing mapping relationships between flows and their corresponding OAM actions, simplifying the processing task.
2Measurement precision
If network devices implement comprehensive OAM processing for all communication flows, then fault detection accuracy is improved, but processing speed and real-time performance deteriorate
Solution Approach 1:
The patent performs preliminary actions by pre-configuring the second data structure with flow identifiers and their associated OAM actions before actual processing occurs. This allows the device to quickly match incoming OAM data units against pre-established flow mappings without performing complex analysis in real-time, thus maintaining both accuracy and speed.
Solution Approach 2:
The patent uses flow identifiers as copies or references to represent entire communication flows. Instead of processing every detail of each flow from scratch, the system uses these identifier copies to quickly retrieve and apply the appropriate OAM actions, significantly improving processing speed while maintaining detection accuracy.
3Measurement precision
If network devices use extensive content-addressable memory entries for flow classification, then processing accuracy is improved, but device complexity and memory requirements increase
Solution Approach 1:
The patent extracts only the essential flow identification information into the first data structure, separating it from the detailed OAM processing information stored in the second data structure. This extraction allows the system to use minimal CAM entries for flow classification while maintaining accuracy, as the detailed processing logic is stored in a more flexible RAM-based structure.
Solution Approach 2:
The patent transitions from a single-dimensional approach (using only CAM for all processing) to a multi-dimensional approach where flow identification occurs in one dimension (first data structure) and OAM action retrieval occurs in another dimension (second data structure). This dimensional separation allows each component to be optimized independently, reducing overall memory requirements while maintaining accuracy.
Data Source
AI summary
Network traffic that includes an Operations, Administration, and Maintenance (OAM) unit is received. A first data flow to which the OAM data unit belongs is identified from among a plurality of data flows of network traffic. Based on identifying the first flow of communication traffic to which the OAM data unit belongs, a first entry corresponding to the first flow is retrieved from a memory that stores OAM action data including a plurality of entries indicating how OAM data units in different flows of communication traffic are to be processed. The first entry is from among the plurality of entries and indicates how OAM data units in the first flow are to be processed, including whether the network device should modify the data unit as part of an OAM action. The OAM data unit is processed in accordance with the first entry.