Parameterized Device Models for OpenFlow Controllers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques for setting forwarding table entries in communication networks lose information about the application developer's intent, limiting the ability to leverage all features of forwarding devices for scalable and efficient end-to-end implementations.
Innovation Solution
A routing controller generates a device model using a universal language of network primitives, allowing parameterization to capture modifications and translate desired forwarding behavior into implementations based on target device capabilities, enabling reuse of the device model across different devices and configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If conventional techniques for setting forwarding table entries are used, then the forwarding device can operate, but information about the application developer's intent is lost
Solution Approach 1:
The patent introduces an intermediary system that translates high-level forwarding intent descriptions into low-level forwarding table entries. This intermediary layer preserves the application developer's intent by maintaining it as a separate representation while automatically generating the necessary device configuration, thus preventing information loss without increasing device complexity.
Solution Approach 2:
The patent creates a copy of the forwarding intent in a structured format that can be processed and transformed. By maintaining a representation of the intent separate from the implementation details, the system preserves the original developer intent while enabling automatic translation to device-specific configurations.
2Extent of automation
If device models are created for each specific device and configuration, then the forwarding behavior can be precisely controlled, but the work to configure forwarding devices cannot be automated
Solution Approach 1:
The patent creates a universal intent representation format that can describe forwarding behavior in a device-agnostic way. This single universal format can be translated to multiple different device-specific configurations, eliminating the need to create separate device models for each device while maintaining precise control over forwarding behavior.
Solution Approach 2:
The patent uses parameterized templates for forwarding intents that can be instantiated with different values for different devices. By changing parameters rather than creating entirely new models, the system achieves automation while managing device-specific variations efficiently.
3Productivity
If a device model is modified to accommodate a change in forwarding behavior, then the forwarding behavior can be updated, but the device model must be re-generated
Solution Approach 1:
The patent performs preliminary translation of the universal intent format into device-specific configurations during an initialization phase. When forwarding behavior needs to be updated, only the intent description needs to be modified, and the previously established translation rules can be reapplied, avoiding complete model regeneration and reducing update time.
Solution Approach 2:
The patent creates a dynamic system where the forwarding intent can be modified independently from the device configuration. The system maintains the ability to re-translate updated intents into new configurations without regenerating the entire device model, enabling flexible updates while maintaining efficiency.
4Extent of automation
If the same device model is applied to different devices, then the work to configure forwarding devices can be automated, but information about device-specific capabilities is lost
Solution Approach 1:
The patent applies local quality by allowing the universal intent format to be translated into device-specific configurations that leverage each device's unique capabilities. The translation process considers local device characteristics and optimizes the forwarding implementation for each specific device while maintaining consistency with the overall forwarding intent.
Data Source
AI summary
A controller in a communication network may be responsible for generating a device model that defines intended forwarding behavior of a network. The device model may be generated using a target-independent universal language of network primitives. The controller may assign a first set of parameters to the device model to generate a first parameterized device model. The controller may assign a second set of parameters to the device model to generate a second parameterized device model. The controller may send the first parameterized device model or the second parameterized device model to a target device. The target device may statically or dynamically translate the received parameterized device model(s) to implementation. The controller is not required to generate a new device model for each modification made to the network: the controller may parameterized a generic device model to reflect the modifications.