Modular Network Slice Design Components
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network orchestration systems lack a comprehensive design system for service-driven slice infrastructure designs, failing to implement per slice instance configuration, which limits the definition and deployment of all network slice components.
Innovation Solution
The system introduces modular components such as Network Service Configuration, Network Function Configuration, Slice Configuration, Infrastructure Deployment Unit, and Assurance Deployment Unit, allowing network designers to create reusable and extensible designs for network slices, enabling on-demand service offerings and automated network adaptation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If current network orchestration systems are used, then network slicing can be implemented, but comprehensive design system for service-driven slice infrastructure is lacking
Solution Approach 1:
The system segments network slice design into modular components including Network Service Configuration component, Network Function Configuration component, Slice Configuration component, Infrastructure Deployment Unit, and Assurance Deployment Unit. Each component handles specific aspects of slice configuration independently, enabling comprehensive service-driven design while maintaining manageable system complexity through division of functionality.
2Ease of operation
If modular components are introduced for comprehensive design, then full control for operations teams is achieved, but system complexity increases
Solution Approach 1:
The modular components are designed with universal interfaces and standardized configuration mechanisms that enable operations teams to control diverse network slice aspects through consistent operational procedures. The Network Service Configuration component, Network Function Configuration component, and Slice Configuration component all follow similar interaction patterns, reducing operational complexity despite the multi-component architecture.
Solution Approach 2:
The system introduces an intermediary orchestration layer that coordinates between the multiple modular components and operations teams. This intermediary manages the interactions between Network Service Configuration, Network Function Configuration, and Slice Configuration components, providing a unified control interface that simplifies operations while maintaining comprehensive component-level control.
3Adaptability or versatility
If per slice instance configuration is implemented, then customization capability improves, but deployment complexity increases
Solution Approach 1:
The system performs preliminary configuration actions by pre-defining network service templates, network function profiles, and slice configuration parameters before actual slice deployment. The Network Service Configuration component establishes service-level agreements and requirements in advance, while the Network Function Configuration component prepares function-specific configurations, enabling customized per-slice deployment without increasing real-time deployment complexity.
Data Source
AI summary
A system may include one or more devices that with processors. The processors are configured to: receive instructions to assemble a slice service design for a network using slice design components; store the slice service design; and receive a request to deploy a slice service specified by the slice service design. The processors may be configured to: deploy the slice service in subnets of the network; or deploy services defined by portions of the slice service design in some of the subnets of the network.