Network Slice Upgrade Orchestration Across Multiple NFs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing 5G network slice upgrade technologies fail to perform collaborative upgrades across multiple network functions (NFs) and lack effective end-to-end verification during upgrades, leading to potential service disruptions and failures.

Innovation Solution

A network slice upgrade master control unit coordinates the upgrade of multiple NFs by managing upgrade plans, dial tests, and rollback procedures, ensuring only a portion of service instances are upgraded at a time, with real-time monitoring and verification to ensure minimal disruption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a single NF is upgraded at a time, then the upgrade process is simple to manage, but collaborative upgrade across multiple NFs in network slice cannot be achieved

Engineering Contradiction:
Improveupgrade management simplicityVSAvoidcollaborative upgrade capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The network slice upgrade system is segmented into multiple independent NFs, each with its own service instances. The upgrade process divides the network slice into manageable NF units that can be upgraded individually while maintaining overall coordination through the master control unit, enabling both simple management and collaborative upgrade capability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The master control unit serves multiple functions: it manages upgrade plans, coordinates dial tests, controls rollback procedures, and monitors multiple NFs simultaneously. This multi-functional design enables the system to achieve collaborative upgrade across multiple NFs while maintaining operational simplicity through a single control point

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If all service instances are upgraded at once, then the upgrade is completed quickly, but service processing may be affected and risks increase

Engineering Contradiction:
Improveupgrade speedVSAvoidservice processing stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system upgrades service instances in controlled batches rather than all at once or one at a time. The master control unit manages the upgrade of multiple service instances across different NFs in a coordinated manner, achieving faster upgrade speed while maintaining service stability through partial upgrading with proper coordination

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs dial tests before completing the full upgrade to verify service functionality. This preliminary verification acts as a cushion, ensuring that upgrades do not adversely affect service processing. The rollback mechanism also provides a safety cushion in case verification fails

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Productivity

If upgrade verification is performed after complete upgrade, then the upgrade process is efficient, but risk verification cannot be performed and service disruptions may occur

Engineering Contradiction:
Improveupgrade efficiencyVSAvoidupgrade risk control
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs dial tests after upgrading a portion of service instances but before completing the full upgrade. This preliminary verification allows risk assessment early in the process, enabling the system to confirm upgrade effectiveness and detect issues before full deployment, thus maintaining both efficiency and reliability

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If multiple NFs are upgraded cooperatively, then end-to-end network upgrade is achieved, but service processing may be affected during upgrade

Engineering Contradiction:
Improveend-to-end upgrade capabilityVSAvoidservice processing continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The master control unit receives feedback from each NF regarding upgrade status and service functionality. Based on this feedback, the control unit makes real-time decisions about continuing or stopping the upgrade process. This feedback mechanism ensures that cooperative NF upgrades are performed in a way that maintains service processing continuity

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12526189B2Network slice upgrading method and device
Publication Date: 2026.01.13 ZTE CORP
  • US12526189B2 patent drawing
  • US12526189B2 patent drawing
  • US12526189B2 patent drawing

AI summary

A network slice upgrading method and device are disclosed. The method may include, acquiring version information of each service instance, and receiving an upgrade instruction; downloading an upgrade package after receiving the upgrade instruction, and simultaneously performing an upgrade to a service instance in each NF according to the upgrade package until each upgrade is completed; wherein, the upgrade instruction comprises a preset upgrade proportion and an upgrade order.