Network Slice Management via Subnet Capability Templates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing service deployment process for network slices is manual and time-consuming, leading to long negotiation periods and resource wastage, as each new service requires manual design and negotiation with multiple vendors, making it difficult to quickly respond to diverse service requirements and reduce time-to-market for new services.
Innovation Solution
A network slice management method involving a first manager and a second manager that generates information about network slices based on subnet capability information, allowing for the reuse of generated slices and improving resource utilization by shielding the physical implementation externally.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual negotiation and design are used for service deployment, then resource allocation can be customized, but the deployment time and complexity increase significantly
Solution Approach 1:
The patent applies preliminary action by pre-defining network slice templates with standardized configurations before actual service deployment. These templates include pre-configured network functions, resources, and parameters that can be directly instantiated without manual negotiation, significantly reducing deployment time while maintaining resource allocation customization through template selection and parameter adjustment.
Solution Approach 2:
The patent utilizes parameter changes by allowing dynamic adjustment of template parameters during deployment. The system enables modification of resource quantities, configuration parameters, and network function selections based on specific service requirements, maintaining adaptability while reducing overall deployment complexity and time.
2Adaptability or versatility
If manual design of network slices is performed, then specific service requirements can be met, but resource wastage occurs due to inability to reuse designs
Solution Approach 1:
The patent applies universality by creating network slice templates that can serve multiple service types and requirements. A single template design can be reused for different services by adjusting parameters, eliminating the need to create new network slices from scratch for each service, thereby reducing resource wastage while maintaining the ability to meet specific service requirements.
Solution Approach 2:
The patent implements copying by enabling replication of proven network slice templates for new service deployments. Instead of manually redesigning network slices, the system copies existing validated templates and instantiates them with modified parameters, ensuring resource efficiency while meeting diverse service requirements through parameter customization.
3Adaptability or versatility
If manual negotiation with multiple vendors is required, then vendor-specific requirements can be addressed, but the process becomes complex and time-consuming
Solution Approach 1:
The patent applies preliminary action by pre-resolving vendor-specific requirements and configurations during template creation. Vendor requirements are incorporated into the template design phase, so that during actual deployment, the system only needs to instantiate the pre-configured template rather than engaging in complex negotiations with multiple vendors, significantly reducing process complexity.
Solution Approach 2:
The patent utilizes an intermediary approach where the network slice template acts as a mediator between service requirements and vendor implementations. The template encapsulates vendor-specific configurations and interfaces, allowing the system to address vendor requirements indirectly through standardized template parameters, thereby reducing direct negotiation complexity while maintaining compliance.
4Reliability
If network slices are designed for each new service, then service-specific optimization is achieved, but time to market increases
Solution Approach 1:
The patent applies preliminary action by optimizing network slice designs during the template creation phase rather than during service deployment. Service-specific optimizations are incorporated into templates in advance through parameter configuration and network function selection, allowing rapid instantiation of optimized slices for new services without time-consuming design processes, thus reducing time to market while maintaining service-specific optimization.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
This application provides a network slice management method and apparatus. A first manager obtains capability information of a subnet, where the capability information of the subnet includes at least one of the following information: capability information of a subnet template and capability information of a subnet instance, the capability information of the subnet template is used to represent a feature of the subnet template, and the capability information of the subnet instance is used to represent a feature of the subnet instance; and then generates information about a network slice based on the capability information of the subnet, where the information about the network slice includes information about a network slice template or information about a network slice instance, and the network slice includes at least one subnet. According to the method, the first manager can generate information about a plurality of network slices based on capability information of a plurality of subnets, to meet a plurality of service requirements. The generated network slices can be reused, and physical implementation of the network slices is shielded externally.