Network Slice Deployment via Dynamic Instantiation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In existing 5G network slice deployment methods, there is a temporal and geographic gap between slice deployment and usage, leading to wastage of network resources and increased costs.

Innovation Solution

A method where a subscriber requests a network slice only when needed, and the management function entity generates and deploys the slice dynamically based on the service request, reducing unnecessary resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the slice is deployed in advance to ensure service availability, then service accessibility is improved, but network resources are wasted and costs increase

Engineering Contradiction:
Improveservice accessibilityVSAvoidnetwork resource waste
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The network device performs preliminary actions by pre-obtaining slice template information and configuration parameters before actual service requests occur. When a service request arrives, the slice can be quickly instantiated using the pre-prepared templates, avoiding both advance deployment waste and deployment delays. This preliminary preparation of templates resolves the contradiction by enabling fast deployment without continuous resource reservation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts slice deployment based on actual service requests rather than maintaining static pre-deployed slices. The network device determines whether to deploy a slice based on real-time service requirements, and the slice lifecycle (deployment, activation, release) is dynamically managed according to service duration and type. This dynamic approach eliminates the need for continuous resource reservation while ensuring service availability when needed.

Inventive Principle:
Principle #15Dynamics

2Area of stationary object

If the slice is deployed in a large geographic area to ensure coverage, then service coverage is improved, but network resources are wasted in areas where service is not actually used

Engineering Contradiction:
Improveservice coverageVSAvoidnetwork resource waste
Core Design Contradiction:
Area of stationary objectVSLoss of energy

Solution Approach 1:

The system applies local quality by deploying slices only in specific geographic areas where service requests are actually generated, rather than uniformly across the entire network coverage area. The network device determines deployment location based on service request patterns and geographic distribution of users, allocating resources locally where needed rather than reserving resources across the entire service area. This resolves the contradiction by matching resource allocation to actual service demand in specific locations.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP3678411B1Network slice deployment method and related device
Publication Date: 2025.04.23 HUAWEI TECH CO LTD
  • EP3678411B1 patent drawingFigure 1
  • EP3678411B1 patent drawingFigure 2
  • EP3678411B1 patent drawingFigure 3

AI summary

Embodiments of this application disclose a network slice deployment method and a related device, to reduce a gap between deployment and use of a slice, thereby saving network resources and reducing costs. The method in the embodiments of this application includes: receiving, by a network device, a first request message sent by a terminal device, where the first request message is used to instruct to deploy a target network slice for providing a target service to the terminal device, and a corresponding management function entity has allocated target network slice information for the target network slice corresponding to the target service; sending, by the network device, a second request message to the management function entity, where the second request message carries the target network slice information; and receiving, by the network device, a second response message sent by the management function entity, where the second response message is used to indicate that the target network slice has been completely deployed.