Virtual Service OAM for Virtualized Network Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is no defined mechanism to verify readiness of network, hardware, and software layers in virtualized systems, and no existing mechanism to monitor Virtual Network Services and Hosted Network Services end-to-end, either periodically or on demand.
Innovation Solution
A virtual service operations, administration, and management (vSOAM) system is implemented, which includes virtual maintenance points (vMPs) such as virtual Maintenance Endpoints (vMEPs) and virtual Maintenance Intermediate Points (vMIPs that initiate and terminate Continuity Fault Management sessions, conduct messaging sessions to test and monitor connection integrity, and collect packet loss and throughput statistics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If virtualized systems implement high availability through multiple independent layers with separate failure recovery mechanisms, then service availability is improved, but system complexity increases significantly
Solution Approach 1:
The patent merges failure recovery mechanisms across multiple virtualized layers by implementing a unified Service Function Chain (SFC) architecture. The SFC orchestrator coordinates failure recovery across different service functions (firewall, load balancer, proxy) that would otherwise operate independently, combining their recovery actions into a coordinated response that maintains service availability while reducing overall system complexity.
Solution Approach 2:
The SFC orchestrator serves multiple functions simultaneously: it manages service function chaining, coordinates failure recovery across layers, and provides centralized control for virtualized network services. This multi-functional approach eliminates the need for separate dedicated failure recovery mechanisms at each layer, reducing complexity while maintaining high availability.
2Reliability
If no defined mechanism exists to verify readiness of network, hardware, and software layers, then system simplicity is maintained, but service reliability cannot be ensured
Solution Approach 1:
The SFC orchestrator performs preliminary verification of service function readiness before service activation. It checks the operational status of network layers, hardware components, and software services in advance, ensuring all components are ready to handle service traffic. This preliminary action prevents service deployment issues and ensures reliability without requiring complex continuous verification mechanisms during normal operation.
Solution Approach 2:
The system implements feedback mechanisms where the SFC orchestrator receives status information from various service functions and network layers, verifying their readiness state. This feedback loop enables the orchestrator to confirm that all necessary components are operational before activating services, ensuring reliability through a relatively simple verification approach rather than complex continuous monitoring.
3Reliability
If no existing mechanism monitors Virtual Network Services end-to-end, then implementation simplicity is maintained, but connection integrity cannot be verified
Solution Approach 1:
The SFC orchestrator acts as an intermediary that monitors connection integrity across the entire service function chain. Instead of requiring complex distributed monitoring at each service function, the orchestrator receives status reports from service functions and network elements, synthesizing this information to provide end-to-end connectivity verification. This intermediary approach ensures connection integrity monitoring while keeping individual service function complexity low.
Data Source
AI summary
A device may create a virtualization layer on top of a physical layer of the device; create a virtual machine layer on top of the virtualization layer; create a virtual network function (VNF) layer based on the virtual machine layer and the virtualization layer; create a connection layer on top of the VNF layer; and create a first virtual maintenance endpoint (MEP) that includes a first virtual media access control (MAC) address. The first virtual MEP may be configured to: send a first continuity fault management (CFM) message to a physical MEP having a physical MAC address or a second virtual MEP having a second virtual MAC address; and receive a second CFM message from the physical MEP or the second virtual MEP.