Controller Service Maps for SDN Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In software-defined networking (SDN), network devices from different vendors and generations exhibit generational and configuration differences, leading to feature gaps and performance variations, which hinder 'plug and play' interoperability and the ability to support new service offerings effectively.

Innovation Solution

Network devices in the forwarding plane communicate their features and performance metadata to the control plane through a southbound interface, using binary, conditional, or value response formats, enabling precise tracking and mapping of network topologies and capabilities to ensure optimal service support.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network devices from different vendors and generations are integrated into the network, then device diversity and potential service capabilities increase, but feature gaps and performance variations arise that hinder interoperability

Engineering Contradiction:
Improvedevice diversityVSAvoidinteroperability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary capability assessment by querying each forwarding box for its service capabilities, buffer depths, and performance metadata before service deployment. This advance knowledge allows the controller to make informed decisions about service placement and configuration, ensuring interoperability before issues arise.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts service parameters such as buffer depth allocations, queue configurations, and resource assignments based on the specific capabilities of each forwarding box. By adapting these parameters to match actual device characteristics, the system maintains reliable interoperability across diverse hardware platforms.

Inventive Principle:
Principle #35Parameter changes

2Measurement precision

If precise tracking of individual network elements is implemented to ensure optimal service support, then service quality improves, but system complexity increases

Engineering Contradiction:
Improveservice support accuracyVSAvoidtracking system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

Each forwarding box autonomously provides its own capability metadata and service support information in response to controller queries. This self-service approach eliminates the need for complex external tracking systems, as devices automatically publish their own operational characteristics and service capabilities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The controller implements a universal service map data structure that can represent multiple service types and device capabilities through a single standardized framework. This multi-functional approach allows precise tracking of diverse network elements without requiring separate complex tracking mechanisms for each service type.

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

3Manufacturing precision

If service-specific network maps are generated to track capabilities, then service deployment accuracy improves, but information processing overhead increases

Engineering Contradiction:
Improveservice deployment accuracyVSAvoidinformation processing overhead
Core Design Contradiction:
Manufacturing precisionVSLoss of information

Solution Approach 1:

The system pre-computes and stores service capability metadata, buffer depth requirements, and performance characteristics in the service map before actual service deployment. This preliminary preparation allows rapid, accurate service instantiation without requiring intensive real-time information processing when services are deployed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates abstract service map representations that capture essential capability information without duplicating complete device state information. These simplified copies contain only the metadata necessary for service deployment decisions, reducing information processing overhead while maintaining deployment accuracy.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9853870B2Controller supported service maps within a federation of forwarding boxes
Publication Date: 2017.12.26 VERIZON PATENT & LICENSING INC
  • US9853870B2 patent drawing
  • US9853870B2 patent drawing
  • US9853870B2 patent drawing

AI summary

A controller network device, in a network control layer of a service provider network, receives one or more parameters for providing particular services over a service provider network and provides, to a forwarding network device in a network resources layer of the service provider network, a capabilities query. The capabilities query includes a feature type identifier for a feature required to support the parameters. The controller network device receives, from the forwarding network device, a response to the capabilities query, wherein a format for the response is one of a binary response format, a conditional response format, or a value response format. The controller network device compiles the response with responses from other forwarding network devices to define a network map for supporting the particular services.