Segment Routing Packet Processing With Dual-Path OAM Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing packet switching technologies face challenges in efficiently processing Operations, Administration, and Maintenance (OAM) packets in segment routing networks, leading to suboptimal performance and resource utilization.
Innovation Solution
Implementing a dual-path packet processing system where fast path processing units handle hardware-based operations and slow path processing units handle OAM operations, using OAM segment identifiers to determine when packets need to be 'punted' to the slow path for further processing, including timestamping and OAM functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If all packets are processed by the same processing unit, then device complexity is reduced, but processing efficiency and resource utilization deteriorate
Solution Approach 1:
The patent segments packet processing into two distinct paths: a fast path for routine packet forwarding handled by hardware-based processing units, and a slow path for OAM packet processing handled by software-based processing units. This segmentation allows each path to be optimized independently, with the fast path achieving high throughput for regular packets while the slow path providing thorough OAM processing capability.
Solution Approach 2:
The patent extracts OAM packet processing from the general packet processing flow by introducing a separate slow path. OAM packets are identified through OAM bits in the packet header and routed to the slow path processing units, which are specifically designed for OAM functionality. This extraction allows the fast path to focus solely on efficient packet forwarding without the overhead of OAM processing.
2Speed
If hardware-based processing is used for all packets, then processing speed is improved, but OAM processing capability deteriorates
Solution Approach 1:
The patent segments processing capabilities between hardware and software paths. The fast path uses hardware-based processing units optimized for high-speed packet forwarding, while the slow path uses software-based processing units that provide comprehensive OAM processing capability. This segmentation allows the system to achieve both high speed for regular packets and full OAM functionality for management packets.
Solution Approach 2:
The patent introduces an intermediary mechanism (the OAM bit in the packet header and the slow path routing logic) that mediates between the fast path and slow path processing. When OAM packets are detected through this intermediary mechanism, they are redirected to the slow path where they receive specialized OAM processing, while regular packets continue through the fast path.
3Reliability
If software-based processing is used for all packets, then OAM processing thoroughness is improved, but processing throughput deteriorates
Solution Approach 1:
The patent segments the processing workload by implementing a slow path specifically for OAM packets that require thorough processing. This slow path uses software-based processing units that can perform comprehensive OAM functions. Meanwhile, the fast path handles regular packets with simpler hardware-based processing, maintaining high throughput for the majority of traffic.
Solution Approach 2:
The patent extracts OAM processing requirements from the general packet processing stream and handles them separately through the slow path. This extraction ensures that OAM packets receive the thorough processing they need without dragging down the processing speed of regular packets, as OAM processing is isolated to a dedicated path.
4Productivity
If dual-path processing is implemented, then processing efficiency and resource utilization are improved, but device complexity increases
Solution Approach 1:
The patent implements a dual-path architecture that segments packet processing into fast and slow paths. This segmentation enables efficient resource utilization by directing different types of packets to appropriate processing units. While the architecture complexity increases, the benefits of optimized resource allocation and processing efficiency outweigh the additional complexity.
Data Source
AI summary
In one embodiment, a service chain data packet is instrumented as it is communicated among network nodes in a network providing service-level and/or networking operations visibility. The service chain data packet includes a particular header identifying a service group defining one or more service functions, and is a data packet and not a probe packet. A network node adds networking and/or service-layer operations data to the particular service chain data packet, such as, but not limited to, in the particular header. Such networking operations data includes a performance metric or attribute related to the transport of the particular service chain packet in the network. Such service-layer operations data includes a performance metric or attribute related to the service-level processing of the particular service chain data packet in the network.