End-to-End IMS Network Slicing for Resource-Efficient QoS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IMS networks lack an end-to-end mechanism for network slicing, making it difficult to customize and efficiently manage resources, provide differentiated services, and introduce new features, leading to operational and capital expenses.
Innovation Solution
Implementing IMS network slicing by configuring logical end-to-end slices within the IMS network, allowing each slice to have its own customized set of network elements and performance parameters, with mechanisms for dynamic reconfiguration and resource allocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If IMS network slicing is implemented, then resource utilization efficiency and service differentiation are improved, but network complexity increases
Solution Approach 1:
The IMS network is segmented into multiple independent network slices, each capable of supporting different service requirements. Each slice is defined by a set of network elements and can be independently configured, deployed, and managed, enabling efficient resource utilization while maintaining manageable complexity through modular architecture.
Solution Approach 2:
Network slicing introduces a new dimension of virtualization to the IMS network architecture. By adding the slice identification and selection dimension to existing network elements, the system achieves multi-tenancy and resource sharing without requiring separate physical networks for each service type.
2Adaptability or versatility
If network slicing is implemented, then service customization and QoS differentiation are improved, but operational complexity increases
Solution Approach 1:
The network slicing architecture enables dynamic configuration and reconfiguration of network elements based on service requirements. Network slices can be created, modified, and terminated dynamically without affecting other slices, allowing operators to adapt the network to changing service demands while simplifying operations through automated provisioning.
Solution Approach 2:
Existing IMS network elements are designed to operate universally across multiple network slices through slice selection and identification mechanisms. This multi-functionality allows a single network element to serve multiple slices with different QoS requirements, reducing operational complexity by eliminating the need for separate dedicated elements for each service type.
3Ease of repair
If network slicing is implemented, then localized changes and maintenance are improved, but system complexity increases
Solution Approach 1:
The network is divided into isolated slices with clear boundaries defined by network elements. This segmentation allows localized changes, repairs, or upgrades to be performed within a single slice without propagating to other slices, significantly simplifying maintenance operations while the modular structure keeps system complexity manageable.
Solution Approach 2:
Specific network elements or functions can be extracted to form separate slices that can be independently maintained. This extraction enables targeted repairs and updates without affecting the entire network system, improving maintenance simplicity while the extracted elements remain integrated through standardized interfaces.
Data Source
AI summary
An Internet Protocol (IP) Multimedia Subsystem (IMS) network slice manager and orchestrator receives first performance requirements associated with a first network slice of a mobile network. The IMS network slice manager and orchestrator determines, based on the first performance requirements, first configuration data associated with a first IMS network slice of an IMS network, where the first IMS network slice is linked to the first network slice of the mobile network. The IMS network slice manager and orchestrator configures and provisions, based on the first configuration data, the first IMS network slice in the IMS network.