OpenFlow OAM Packet Handling via Packet Inject Logic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

OpenFlow does not provide mechanisms for identifying, injecting, or de-multiplexing Operations, Administration, and Management (OAM) packets, which are essential for monitoring and managing data flows, leading to difficulties in implementing OAM solutions within the OpenFlow domain.

Innovation Solution

A method and system are introduced to enable the identification, injection, and de-multiplexing of OpenFlow OAM packets by utilizing a new logical module called Packet Inject Logic (PIL) within the OpenFlow switch module, ensuring fate sharing with data packets. This involves using a matching field not considered during data packet handling to identify OAM packets and adding a new module to the packet processing pipeline for injection and de-multiplexing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If OpenFlow 1.1 specification is used without extensions, then the protocol maintains simplicity and standard compliance, but OAM packet identification, injection, and de-multiplexing functionalities are not provided

Engineering Contradiction:
ImproveOAM functionalityVSAvoidprotocol complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the packet handling process by introducing a dedicated Packet Inject Logic (PIL) module that operates independently from the main OpenFlow processing pipeline. This module specifically handles OAM packet identification, injection, and de-multiplexing, while the rest of the system continues to operate according to standard OpenFlow 1.1 specifications. This segmentation allows OAM functionality to be added without complicating the core protocol.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary Packet Inject Logic (PIL) module that acts as a mediator between incoming packets and the OpenFlow processing pipeline. This intermediary module intercepts packets, identifies OAM packets using matching fields, and directs them to appropriate handling routines without requiring changes to the underlying OpenFlow specification. The PIL module serves as a bridge that enables OAM functionality while maintaining protocol simplicity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a new module Packet Inject Logic is added to handle OAM packets, then OAM packet identification and injection capabilities are provided, but the complexity of the OpenFlow switch module increases

Engineering Contradiction:
Improvepacket handling capabilityVSAvoidswitch module complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The Packet Inject Logic (PIL) module is designed with multi-functionality to handle multiple OAM operations including packet identification, injection, and de-multiplexing within a single unified module. By consolidating these functions rather than creating separate modules for each operation, the patent achieves enhanced packet handling capability while minimizing the increase in overall system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The PIL module implements self-service mechanisms by autonomously identifying OAM packets through matching field analysis and automatically directing them to appropriate handling routines without requiring external control or configuration. This self-service capability reduces the operational complexity of managing the extended functionality, as the module manages its own operations independently.

Inventive Principle:
Principle #25Self-service

3Difficulty of detecting and measuring

If matching fields not considered during data packet handling are used to identify OAM packets, then OAM packets can be distinguished from data packets, but the matching structure complexity increases

Engineering Contradiction:
Improvepacket identification accuracyVSAvoidmatching structure complexity
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The patent employs a metaphorical 'color change' approach by utilizing matching fields that are not typically considered during standard data packet handling to create distinctive identifiers for OAM packets. Similar to how color changes can signal different meanings, these unused matching fields serve as unique markers that allow the PIL module to easily distinguish OAM packets from regular data packets without adding complex identification logic.

Inventive Principle:
Principle #32Color changes

Solution Approach 2:

The patent changes the parameter space used for packet identification by leveraging matching fields that are normally ignored in data packet processing. By repurposing these existing parameters for OAM packet identification, the system achieves accurate packet differentiation without introducing additional complex matching structures or new identification mechanisms.

Inventive Principle:
Principle #35Parameter changes

4Measurement precision

If fate sharing is ensured for OAM packets with data packets, then monitoring accuracy is improved, but the packet processing complexity increases

Engineering Contradiction:
Improvemonitoring accuracyVSAvoidprocessing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by having the Packet Inject Logic (PIL) module pre-identify and pre-direct OAM packets to the same forwarding paths as their corresponding data packets before the actual forwarding occurs. This preliminary routing decision ensures fate sharing - that OAM packets follow the same path as data packets - without requiring complex real-time processing or coordination during packet forwarding, thus maintaining processing efficiency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system employs feedback mechanisms where the PIL module monitors the forwarding decisions made for data packets and uses this information to ensure OAM packets receive identical treatment. By implementing feedback loops that verify fate sharing compliance, the system achieves high monitoring accuracy while keeping processing complexity manageable through automated verification rather than manual configuration.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8964569B2Generic monitoring packet handling mechanism for OpenFlow 1.1
Publication Date: 2015.02.24 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US8964569B2 patent drawing
  • US8964569B2 patent drawing
  • US8964569B2 patent drawing

AI summary

A method implemented by a network element monitor OpenFlow data flows and enable operations, administration and management (OAM) functionality in OpenFlow. The method inserts OpenFlow OAM packets into an OpenFlow data flow to monitor the OpenFlow data flow, wherein inserted OpenFlow OAM packets have fate sharing with data packets in the OpenFlow data flow. The method comprises the steps of receiving by the network element the OpenFlow OAM packets from a source through a port of the network element, matching by an OpenFlow switch module using a matching structure of OpenFlow data packets received by the network element to identify the OpenFlow OAM packets, and forwarding the identified OpenFlow OAM packets to a flow table or group table of the OpenFlow switch module to aggregate the OpenFlow OAM packets with a corresponding OpenFlow data flow.