Software Defined Protocol Stack Dynamic Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network data plane protocols are inflexible and unable to efficiently adapt to changes, limiting their ability to provide per-application quality of experience (QoE) and failing to accommodate custom requirements for new services like machine-to-machine (M2M) communications, as they are based on a fixed, preconfigured 7-layer protocol stack.
Innovation Solution
A software-defined protocol (SDP) framework that allows for dynamic configuration of network components using a SDP controller interacting with a Software Defined Networking (SDN) controller to determine the best protocol stack and data plane functionality based on application needs, enabling flexible protocol implementation and adaptation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a fixed, preconfigured 7-layer protocol stack is used, then network stability and standardization are maintained, but adaptability to network changes and application-specific requirements deteriorates
Solution Approach 1:
The patent implements dynamic protocol stack configuration where the protocol stack is no longer fixed but can be dynamically selected and configured based on application requirements and network conditions. The system allows runtime modification of protocol parameters and selection of appropriate protocol combinations, transforming the static protocol architecture into a dynamic adaptive system.
Solution Approach 2:
The invention enables parameter changes in the protocol stack by allowing different protocol parameters to be configured and adjusted based on specific application needs. The system can modify protocol parameters such as QoS settings, data plane processing capabilities, and protocol layer configurations to optimize performance for different applications while maintaining network stability.
2Adaptability or versatility
If a fixed protocol stack is used, then implementation simplicity is maintained, but per-application quality of experience (QoE) provisioning deteriorates
Solution Approach 1:
The patent introduces an intermediary controller or management system that mediates between application requirements and protocol stack configuration. This intermediary automatically translates application QoE requirements into appropriate protocol stack configurations, eliminating the need for manual protocol configuration while enabling fine-grained per-application QoE provisioning through automated policy-based management.
3Adaptability or versatility
If all end-to-end hosts are treated the same, then network simplicity is maintained, but support for custom protocol stacks in new services deteriorates
Solution Approach 1:
The patent implements local quality by allowing different protocol stack configurations for different hosts or network segments based on their specific requirements. Instead of a uniform protocol stack across the entire network, the system enables customized protocol configurations at local levels (per-host or per-service basis) while maintaining overall network coherence through centralized management and coordination.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Embodiments are provided for a framework for networks with software defined protocols (SDP) network nodes. The embodiments include a SDM controller component for managing and controlling a data plane protocol for SDP network nodes. The SDP controller also interacts with a software defined networking (SDN) controller for determining one or more paths in a network including the SDP network nodes. The SDP controller is configured to determining a break-down of data plane process functionality into a plurality of basic process function blocks for a service, traffic flow, or virtual network in accordance with network component capabilities or quality of service/experience requirement. A workflow and status information are also determined for one or more network components along a path allocated, by the SDN controller. The workflow and status information are indicated to the one or more components, which are configured to implement the workflow using the basic process function blocks.