Network Slice Creation via Hierarchical Template Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing network slice deployment process is inefficient due to the need for extensive manual input of deployment information, leading to low efficiency and a high error rate.

Innovation Solution

The method divides the network slice into four levels (data center-level, slice-level, NS-level, and VNF-level) and pre-stores VNFD information in a database, allowing automatic creation of network slices by entering basic name information, reducing manual work and increasing efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual deployment information input is used for network slice creation, then deployment flexibility and customization are improved, but deployment efficiency and time consumption deteriorate

Engineering Contradiction:
Improvedeployment flexibilityVSAvoiddeployment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent pre-configures deployment templates with common network slice parameters, NS information, VNF information, and VNFD information before deployment is needed. When a network slice needs to be deployed, the system automatically selects and fills these pre-configured templates based on the slice type, eliminating the need for manual input of routine deployment information while maintaining the ability to customize specific parameters.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates and stores deployment templates that capture standardized deployment configurations for different network slice types. These templates serve as reusable copies of deployment information that can be automatically instantiated multiple times, reducing repetitive manual work while preserving deployment flexibility through template selection and parameter customization.

Inventive Principle:
Principle #26Copying

2Manufacturing precision

If manual network slice deployment is performed, then deployment accuracy and error control are improved, but time consumption and operational complexity increase

Engineering Contradiction:
Improvedeployment accuracyVSAvoidtime consumption
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent implements automatic validation mechanisms that check deployment parameters against predefined rules and constraints. The system provides feedback on parameter validity, configuration consistency, and resource availability, automatically correcting errors or alerting operators before deployment execution. This automated feedback loop maintains deployment accuracy while significantly reducing the time required for manual verification.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system automatically performs deployment information validation, template selection, and parameter configuration based on the specified network slice type. The automated system serves itself by retrieving pre-configured deployment information, validating parameters, and executing deployment without requiring manual intervention for routine checks, thereby reducing both time consumption and operational complexity while maintaining accuracy through automated validation rules.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If extensive manual input is required for network slice deployment, then deployment control and customization are improved, but operational complexity and error rate increase

Engineering Contradiction:
Improvedeployment controlVSAvoidoperational complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the network slice deployment process into distinct hierarchical levels: slice-level parameters, NS-level parameters, VNF-level parameters, and VNFD-level parameters. Each level has its own deployment template and validation rules. This segmentation allows operators to control deployment at the appropriate level of abstraction without being overwhelmed by the entire configuration, reducing operational complexity while maintaining precise control over each deployment aspect.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates universal deployment templates that can be applied across multiple network slice types with different levels of customization. The same template framework serves multiple functions: storing pre-configured parameters, validating input data, guiding the deployment process, and generating deployment configurations. This multi-functional template system reduces operational complexity by providing a unified interface while maintaining the ability to control deployment specifics for different slice types.

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

Data Source

PatentEP3806390B1Network slice creation method and management and orchestration system
Publication Date: 2023.01.04 DATANG MOBILE COMM EQUIP CO LTD
  • EP3806390B1 patent drawingFigure 1~2
  • EP3806390B1 patent drawingFigure 3~4
  • EP3806390B1 patent drawingFigure 5~6

AI summary

Disclosed are a network slice creation method and a management and orchestration system. The method comprises: a management and orchestration system (MANO) acquiring name information of a first slice network that needs to be created; the MANO acquiring first virtualized network function descriptor (VNFD) information corresponding to a first network service (NS) and second VNFD information corresponding to a first VNF; the MANO creating, according to the first VNFD information and the second VNFD information, the first slice network corresponding to the name of the first slice network, the first NS corresponding to the name of the first NS, a subnet of the first NS, the first VNF corresponding to the name of the first VNF, and a subnet of the first VNF; and the MANO creating, in the subnet of the first NS and in any one or more of networks of the subnet of the first VNF, at least one port and at least one virtualized network function component (VNFC), and connecting the at least one port to the at least one VNFC one by one.