Network Slice Orchestration via Sub-Slice Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The 5G standard protocol lacks specific definitions for orchestrating and deploying network slices, as well as discovering and selecting instantiated 5G network slices, which hinders efficient management and utilization of network resources.

Innovation Solution

A network slice management method that involves receiving communication service subscription information, converting it into requirement description information, selecting and determining sub-slice parameters, and initiating deployment requests to orchestrate and manage network slices through a series of logical and physical resource management steps, including resource reservation and configuration, using entities like NSMF, NSSMF, NFVO, VNFM, and NFVI.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the 5G standard protocol is used for network slice management, then network slice isolation and resource allocation are achieved, but specific orchestration and deployment methods are not defined

Engineering Contradiction:
Improvenetwork slice isolation and resource allocationVSAvoidorchestration and deployment definition
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the network slice management process into distinct phases: subscription information reception, requirement description information generation, sub-slice selection, and deployment request initiation. This segmentation provides specific orchestration methods while maintaining the flexibility and isolation benefits of network slicing.

Inventive Principle:
Principle #1Segmentation

2Productivity

If network slice orchestration is implemented without standardized methods, then deployment flexibility is maintained, but efficient resource allocation is hindered

Engineering Contradiction:
Improveresource allocation efficiencyVSAvoidorchestration method definition
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by generating requirement description information from subscription information before actual deployment. This includes determining service level requirements, selecting appropriate sub-slices, and preparing deployment requests in advance, which enables efficient resource allocation while maintaining standardized orchestration methods.

Inventive Principle:
Principle #10Preliminary action

3Manufacturing precision

If detailed orchestration protocols are defined, then deployment precision is improved, but system complexity increases

Engineering Contradiction:
Improvedeployment precisionVSAvoidprotocol definition
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent introduces requirement description information as an intermediary between user subscription requests and actual network slice deployment. This intermediary layer translates high-level subscription requirements into specific deployment parameters, achieving precise deployment without requiring complex end-to-end protocols between all system components.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3648401B1Method, device, and computer readable storage medium for managing network slice
Publication Date: 2024.05.01 ZTE CORP
  • EP3648401B1 patent drawingFigure 1
  • EP3648401B1 patent drawingFigure 2
  • EP3648401B1 patent drawingFigure 3

AI summary

The present disclosure provides a network slice management method, device, and a computer-readable storage medium. The network slice management method includes the following steps: receiving communication service subscription information initiated by a user; converting the communication service subscription information into requirement description information of a corresponding network slice; selecting a sub-slice and determining requirement description information of the sub-slice, according to the requirement description information of the network slice; determining a deployment indicator of a corresponding network service according to the requirement description information of the sub-slice, and initiating a deployment request for the sub-slice based on the deployment indicator of the network service; and managing the sub-slice based on the network service and the deployment request for the sub-slice.