Virtualized Network Management Protocol Offloading via Service Function Chaining
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network management systems face challenges in upgrading and managing network elements due to computational overhead and compatibility issues with legacy protocols, particularly with SNMP, which lacks modern features and interoperability, leading to inefficiencies and increased resource consumption.
Innovation Solution
Implementing a virtualization engine that offloads network management protocol processes using Service Function Chaining (SFC) via Network Service Headers (NSH), allowing network elements to communicate with a virtualization engine rather than maintaining local NMP code blocks, thereby reducing computational load and enabling seamless protocol upgrades without altering network elements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network elements maintain local NMP code blocks for protocol communication, then protocol compatibility and direct communication capability are improved, but computational overhead and resource consumption increase
Solution Approach 1:
The patent extracts NMP code blocks from individual network elements and consolidates them into a centralized virtualization engine. Network elements no longer maintain local NMP implementations; instead, they communicate with the virtualization engine which houses the actual protocol handling code. This extraction eliminates redundant computational resources at each network element while preserving protocol compatibility through the centralized engine.
Solution Approach 2:
The patent merges multiple NMP code blocks from different network elements into a single virtualization engine. By combining scattered protocol implementations into one centralized location, the system reduces overall computational overhead while maintaining full protocol support. The virtualization engine serves as a shared resource that all network elements can access for protocol communication.
2Adaptability or versatility
If network elements implement legacy protocols like SNMP locally, then backward compatibility is improved, but adaptability to modern protocols and features deteriorates
Solution Approach 1:
The virtualization engine acts as an intermediary between network elements and the NMS. It handles all protocol translation and adaptation, allowing network elements to communicate with modern NMS using contemporary protocols without requiring the elements themselves to implement multiple protocol versions. This mediator approach eliminates the need for complex middleware at network elements while maintaining backward compatibility.
3Adaptability or versatility
If network elements maintain multiple protocol versions for interoperability, then compatibility with legacy systems is improved, but device complexity and maintenance difficulty increase
Solution Approach 1:
The virtualization engine is designed as a universal platform that supports multiple NMP versions and protocol types in a single system. Instead of each network element maintaining separate code blocks for different protocols, the centralized engine provides multi-functional protocol support. This allows the system to maintain interoperability across legacy and modern protocols while significantly reducing the complexity at individual network elements.
Data Source
AI summary
Approaches are disclosed for virtualizing a network management protocol (NMP). A network element offloads processes for communicating in the NMP to a virtualization engine (e.g., a backend virtualization proxy for the network element). The network element transmits a message containing a NMP request to the virtualization engine using service function chaining (SFC) by inserting service plane protocol data (e.g., a network service header (NSH)) into the message (e.g., an impregnated request). The virtualization engine expropriates, from the network element, processes for communicating in the NMP and can, thereby, reduce the computational resources used by the network element for communicating in the NMP. The virtualization engine generates a NMP response to the NMP request. The virtualization engine transmits a different message containing the NMP response to the network element using SFC by inserting service plane protocol data into the message (e.g., an impregnated response).