Virtual Server Update Management for Seamless Service Switching

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional application updates for communication services are inefficient due to strong hardware and software connections, requiring time-consuming re-installation and recovery processes, especially for communication services where temporary service stoppages are difficult, such as mobile communication infrastructure.

Innovation Solution

An update management system that includes a virtualization resource management node, service monitor, and virtual communication function management node to generate a new version virtual server, perform network switching, and synchronize settings, allowing for seamless updates and recoveries without service disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional application updates are performed for communication services, then application updates can be implemented, but service stoppages are required and efficiency is reduced

Engineering Contradiction:

Improveupdate efficiencyVSAvoidservice continuity

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system segments the application update process into multiple independent stages: creating a new version virtual server, synchronizing settings, and performing network switching. This segmentation allows the new version to be prepared and tested independently while the old version continues to serve users, enabling updates without service stoppages.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by creating a new version virtual server and synchronizing its settings with the old version before actually switching the network traffic. This preliminary preparation ensures that the new version is ready and configured correctly before taking over service, avoiding service disruptions.

Inventive Principle:

Principle #10Preliminary action

2Productivity

If re-installation work is performed for applications without update functions, then new versions can be deployed, but time consumption increases

Engineering Contradiction:

Improvedeployment speedVSAvoidupdate time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system creates a copy of the old version virtual server as a new version virtual server, then synchronizes the settings from the old version to the new version. This copying approach is much faster than complete re-installation while still achieving new version deployment, significantly reducing update time.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system discards the old version virtual server after successfully switching network traffic to the new version. This allows the old version to be removed from the system once its function has been transferred, streamlining the deployment process and reducing overall update time.

Inventive Principle:

Principle #34Discarding and recovering

3Reliability

If recovery processes are performed when faults occur, then service reliability can be maintained, but process complexity increases

Engineering Contradiction:

Improveservice recovery capabilityVSAvoidrecovery process complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by maintaining the old version virtual server as a backup ready for immediate recovery. When faults occur in the new version, the old version can be quickly restored through network switching without requiring complex recovery procedures, as everything is already prepared in advance.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the service monitor continuously monitors the communication service and can detect faults. When faults are detected, the feedback triggers the recovery process by switching back to the old version, creating a closed-loop system that automatically responds to failures.

Inventive Principle:

Principle #23Feedback

4Productivity

If unified update procedures are implemented for all application types, then process efficiency is improved, but system complexity increases

Engineering Contradiction:

Improveupdate process efficiencyVSAvoidmanagement system complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system implements universality by creating a unified update management framework that can handle different types of applications (communication services, data processing services, etc.) through the same standardized process of virtual server creation, setting synchronization, and network switching. This multi-functional approach improves efficiency while managing complexity through standardization.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentEP3125117B1Update management system and update management method

Publication Date: 2020.09.23 NTT DOCOMO INC

Figure 1
Figure 2
Figure 3

AI summary

In an update management system including a plurality of servers executing a communication service, a server (VNF2) not connected to a network in which a new version of an application is operated is generated in parallel with a server (VNFM1) in which an old version of the application is operated, and old and new correspondence data between an old version server and a new version server is generated and used to execute switching from the old version server (VNF1) to the new version server (VNF2) in a flow on the network and to execute switching-back to the old version server (VNF1) by referring to the old and new correspondence data at the time of occurrence of fault in a new version.