SDN Controller OAM Module Distribution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Software defined networking (SDN) datapath nodes lack the intelligence to implement Operations, Administration, and Management (OAM) functions independently, requiring special programming for each node, which goes against the SDN architecture's intent of centralized control and increased efficiency.

Innovation Solution

A controller node determines the OAM actions capable by each datapath node, communicates OAM tool modules to implement OAM functions, allowing multiple types of datapath nodes to execute OAM actions without individual programming, facilitating centralized management and reduced node-specific configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If datapath nodes are specially programmed to implement OAM functions, then OAM functionality can be achieved, but device complexity and programming effort increase for each node

Engineering Contradiction:

ImproveOAM function implementation capabilityVSAvoidnode programming complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the OAM intelligence from individual datapath nodes and concentrates it in the controller node. The controller determines which OAM actions each datapath node is capable of implementing and communicates appropriate OAM tool modules to them, thereby achieving OAM functionality without programming each datapath node individually.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The controller acts as an intermediary between the OAM management system and the datapath nodes. It translates high-level OAM requirements into specific tool module configurations and communicates them to the appropriate datapath nodes, eliminating the need for direct programming of each node.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If multiple conventional network nodes combine control plane and forwarding plane, then OAM functions can be implemented, but network cost increases

Engineering Contradiction:

ImproveOAM function implementationVSAvoidnetwork node quantity

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the network functions by separating the control plane (OAM intelligence) from the forwarding plane (datapath nodes). This allows multiple inexpensive datapath nodes to be deployed without requiring each to have full OAM capabilities, as the controller provides centralized OAM management.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The controller node provides universal OAM management capabilities that serve multiple different types of datapath nodes. A single controller can manage diverse datapath nodes with varying capabilities, eliminating the need for each node to be a full-featured conventional network node.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Quantity of substance

If a single controller node manages multiple datapath nodes, then overall network cost decreases, but OAM management complexity increases

Engineering Contradiction:

Improvenetwork node quantityVSAvoidcontroller management complexity

Core Design Contradiction:

Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent changes the parameter of OAM management from distributed (at each datapath node) to centralized (at the controller). The controller determines OAM actions based on each datapath node's capabilities and communicates appropriate tool modules, transforming a complex distributed programming problem into a centralized configuration task.

Inventive Principle:

Principle #35Parameter changes

4Adaptability or versatility

If datapath nodes lack OAM intelligence, then SDN architecture is maintained, but OAM function implementation requires centralized control

Engineering Contradiction:

ImproveSDN architecture complianceVSAvoidcentralized control complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent enables datapath nodes to self-configure with appropriate OAM tool modules based on their inherent capabilities. The controller communicates which OAM actions each node can implement, and the nodes execute the received tool modules autonomously, maintaining SDN principles while enabling OAM functionality.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS9680698B2Operations, administration, and management (OAM) functions in a software defined network

Publication Date: 2017.06.13 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

Communication of a module to a datapath node is disclosed. A controller node receives connection information identifying a first datapath node in communication with a network. The controller node obtains Operations, Administration, and Management (OAM) information including an OAM action set that identifies one or more OAM actions the first datapath node is capable of implementing at the first datapath node. A first OAM tool module is determined that is operative to perform at least one of the one or more OAM actions identified in the OAM action set to implement a first OAM tool function. The first OAM tool module is communicated to the first datapath node.