EMS Split-Brain Resolution for Virtual Network Function Components
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current NFV architecture lacks detailed specifications for fault detection in Virtual Network Function Components (VNFCs), particularly in systems employing Active/Standby fault tolerance, which is crucial for ensuring reliability and service continuity in telecommunication networks.
Innovation Solution
The implementation of a system that includes receiving VNFCI status notifications, retrieving timestamps of state changes, sending requests to determine network isolation, and managing state changes between active and standby states within the VNFM framework to handle faults and prevent split-brain conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If Active/Standby fault tolerance is implemented in VNFCs, then reliability is improved, but device complexity increases due to the need for state management and fault detection mechanisms
Solution Approach 1:
The patent introduces an Element Management System (EMS) as an intermediary component that centralizes the management of VNFC operational states. The EMS receives status notifications from VNFCs, determines network isolation conditions, and sends state change requests to transition VNFCs between active and standby states. This intermediary approach simplifies the overall system architecture by consolidating complex state management logic in a dedicated management entity rather than distributing it across multiple VNFCs.
Solution Approach 2:
The patent implements a feedback mechanism where VNFCs send status notifications to the EMS, which then determines appropriate state transitions based on network isolation detection. The EMS monitors the operational states of VNFCs and peer VNFCs, compares timestamps to detect split-brain conditions, and sends control messages to adjust states accordingly. This closed-loop feedback system ensures reliable fault tolerance while managing complexity through centralized control logic.
2Reliability
If fault detection mechanisms are added to VNFCs, then reliability is improved, but ease of operation deteriorates due to increased monitoring and state management overhead
Solution Approach 1:
The patent enables VNFCs to autonomously send status notifications to the EMS, which automatically processes these notifications and determines appropriate state transitions. The system performs self-diagnosis by comparing timestamps of state changes and detecting network isolation conditions without requiring manual intervention. The EMS automatically sends state change requests to transition VNFCs between active and standby states, eliminating the need for operators to manually monitor and manage fault tolerance states.
3Reliability
If network isolation detection is implemented, then reliability is improved by preventing split-brain conditions, but measurement precision requirements increase for timestamp comparison and state tracking
Solution Approach 1:
The patent records timestamps of VNFCI state changes to an active state in advance, storing them in an element VNFCI state database. When status notifications are received, the system retrieves these pre-recorded timestamps and compares them to detect split-brain conditions. By performing the timestamp recording action in advance rather than calculating it in real-time during fault detection, the system reduces measurement precision requirements and simplifies the comparison process.
Data Source
AI summary
An example operation may include a system, comprising one or more of receiving a virtual network function component instance (VNFCI) status notification resumption message with an active state when a peer VNFCI operational state is active, retrieving a timestamp of a VNFCI state change to an active state from an element VNFCI state database, retrieving a timestamp of a peer VNFCI state change to active from an element VNFCI state database, sending one or more of: a request to a virtual network function manager (VNFM) to determine if the VNFCI network is isolating while an operating state was active, and a request to the VNFM to determine if the peer VNFCI network is isolating while an operating state was active, sending a state change request with standby state to the peer VNFCI when the VNFCI is not network isolated and the peer VNFCI is network isolated, and a VNFM response is received regarding the VNFCI, a timeout response from the VNFM, and a VNFM response is received regarding the peer VNFCI, and sending a state change request with standby to the VNFCI with one or more of: the VNFCI network isolate and peer VNFCI is not network isolated, and the VNFCI is network isolated or the peer VNFCI is not network isolated, and the VNFCI is not network isolated and the peer VNFCI is network isolated and the VNFCI is in preferred standby.