Virtual Network Function Graceful Shutdown

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing methods for updating and maintaining virtual network functions in cloud environments are resource-intensive and time-consuming, leading to increased downtime and labor costs due to the complexity of inter-dependencies and frequent updates required for real-time and mission-critical services, which can result in infrastructure faults and maintenance challenges.

Innovation Solution

A system and method for dynamic message flow management that includes a control module to manage network function instances, allowing for graceful shutdowns, updates, and reactivation of virtual network functions, using a snapshot of configuration data to restore message flows and minimize downtime, by identifying peers, stopping message flows temporarily, and resuming them after updates are completed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If virtual network function instances are shut down for updates and maintenance, then the virtualized resources can be updated and changed, but downtime increases and network services are disrupted

Engineering Contradiction:

Improveability to update and change virtualized servicesVSAvoiddowntime during updates

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by capturing configuration snapshots and identifying peer dependencies before shutting down virtual network function instances. This preparation enables rapid restoration of message flows after updates, minimizing downtime while maintaining the ability to update services.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If comprehensive MOP procedures are defined to manage interdependencies during updates, then network service continuity is maintained, but labor costs and complexity increase

Engineering Contradiction:

Improvenetwork service continuityVSAvoidcomplexity of MOP procedures

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service by automatically capturing configuration snapshots, identifying peer virtual network functions, and managing message flow routing during updates. This automation eliminates the need for complex manual MOP procedures while maintaining network service continuity, reducing both labor costs and procedural complexity.

Inventive Principle:

Principle #25Self-service

3Productivity

If frequent updates are performed to maintain cloud services, then service functionality is improved, but labor costs and downtime accumulate

Engineering Contradiction:

Improveservice functionality updatesVSAvoidcumulative downtime from frequent updates

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system enables continuity of useful action by implementing graceful shutdown procedures that maintain message flow routing to peer instances during updates. Configuration snapshots are captured and restored efficiently, allowing frequent updates to be performed with minimal cumulative downtime, thus maintaining high productivity while reducing time loss.

Inventive Principle:

Principle #20Continuity of useful action

4Reliability

If virtual network function instances are shut down for maintenance, then infrastructure faults are prevented, but the impact on peer instances and network services increases

Engineering Contradiction:

Improveinfrastructure fault preventionVSAvoidimpact on peer instances

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system uses configuration snapshots and peer identification as intermediaries to manage the impact of shutdowns. By capturing the state before maintenance and systematically restoring it afterward, the system prevents infrastructure faults while minimizing the harmful impact on peer instances and network services through controlled, predictable update procedures.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10212035B2Message flow management for virtual networks

Publication Date: 2019.02.19 AT&T INTELLECTUAL PROPERTY I L P

AI summary

Concepts and technologies are disclosed herein for message flow management for virtual networks. A processor can identify a target virtual network function instance that is to be taken offline. The processor can change a status associated with the target virtual network function instance to indicate it being taken offline. The processor can start a graceful shutdown timer to trigger shutdown of the target virtual network function instance. The processor can identify external interfaces and a peer network function that identifies the target virtual network function instance as a next hop. The processor can obtain, for the target virtual network function instance and the peer network function instance, a snapshot that identifies configuration data for the target virtual network function instance and the peer network function instance and can generate a command to trigger a shutdown of the target virtual network function instance.