SDN Controller API Signature Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of discovering Software-Defined Networking (SDN) components in networks, due to their varied and vendor-specific APIs, makes traditional discovery methods inefficient compared to standard network components that use Simple Network Management Protocol (SNMP).
Innovation Solution
An SDN controller identifies SDN components by iteratively selecting API signatures from a set, using priority lists to optimize the process, and dynamically updates priorities based on previous component identifications, allowing it to determine if the API exhibits specific characteristics through messages and responses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional SNMP-based discovery methods are used for SDN components, then standard network components can be easily discovered, but SDN components with varied vendor-specific APIs cannot be effectively discovered
Solution Approach 1:
The patent creates a universal discovery mechanism that handles both SNMP-based standard components and API-based SDN components through a single standardized interface. The SDN controller implements a unified discovery process that can adapt to different component types, making the system multi-functional without requiring separate discovery procedures for each component type.
Solution Approach 2:
The patent introduces an intermediary layer (the standardized API interface) between the SDN controller and diverse SDN components. This intermediary allows the controller to discover and manage vendor-specific components through a common interface, translating varied vendor APIs into a standardized form that the controller can handle uniformly.
2Adaptability or versatility
If vendor-specific APIs are supported for each SDN component, then component functionality is preserved, but discovery complexity increases significantly
Solution Approach 1:
The patent changes the parameter of API interaction from vendor-specific implementations to a standardized interface with consistent parameters and methods. By defining a uniform set of API parameters and communication protocols, the system can discover and interact with diverse vendor components without being hindered by their individual API variations.
3Measurement precision
If comprehensive API signature testing is performed to identify SDN components, then accurate component identification is achieved, but time and computational resources are consumed
Solution Approach 1:
The patent performs preliminary actions by establishing a standardized API interface and signature framework before actual component discovery begins. By pre-defining expected API patterns, parameters, and response formats, the system can quickly match discovered components against these predefined signatures, reducing the time needed for comprehensive testing while maintaining identification accuracy.
Data Source
AI summary
Based on a request to identify a networking component, a first application programming interface (API) signature is selected from a plurality of API signatures within a priority list that associates the first API signature with a corresponding first API type, wherein the first API signature includes a first characteristic. A first API implemented by the networking component is tested to determining whether the first API implemented by the networking component exhibits the first characteristic. A determination is made of whether the networking component implements the first API type based on determining that the first API implemented by the networking component exhibits the first characteristic.