Network Slice Containers Distributed Across Nodes for High Availability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
5G networks struggle to meet the diverse service level agreement (SLA) requirements of various vertical industries due to the failure of network slices when a node fails, leading to service disruptions.
Innovation Solution
Implementing network slicing with distributed network element containers across different network nodes, using labels to distinguish slices, isolating resources, and sharing resources among slices of the same type to ensure high availability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If network slices are deployed on single physical network nodes, then device complexity is reduced, but reliability deteriorates when node failures occur
Solution Approach 1:
The patent segments network slices across multiple physical network nodes rather than concentrating them on a single node. Each network slice is divided into multiple network element containers that are independently deployed on different nodes, ensuring that slice functions are distributed and can survive individual node failures.
Solution Approach 2:
The patent applies local quality by allowing different network nodes to have different characteristics and roles. Each node can be optimized for specific functions, and network element containers are placed on nodes based on local resource availability and performance requirements, enabling tailored deployment strategies for different parts of the network.
2Productivity
If resources are shared among all network slices, then resource utilization improves, but resource isolation and security deteriorate
Solution Approach 1:
The patent implements universality by creating network element containers that can serve multiple network slices simultaneously. These containers are designed with multi-functionality, allowing the same container instance to provide services to different slices while maintaining logical isolation through labeling and resource allocation policies.
Solution Approach 2:
The patent uses copying by creating virtual copies of network element containers for different network slices. While the underlying infrastructure can be shared, each slice receives a copied or cloned instance of the necessary network elements, ensuring that each slice has its own isolated logical representation while benefiting from shared physical resources.
3Reliability
If network element containers are distributed across different network nodes, then reliability improves through fault tolerance, but device complexity increases
Solution Approach 1:
The patent implements self-service by enabling network element containers to automatically discover and deploy themselves across appropriate network nodes. The system includes self-configuration capabilities that allow containers to adapt to their deployment environment without manual intervention, reducing the operational complexity of managing distributed deployments.
Solution Approach 2:
The patent applies preliminary action by pre-configuring network element containers with the necessary information to deploy themselves on suitable nodes. Deployment manifests and configuration templates are prepared in advance, specifying node selection criteria, resource requirements, and inter-container dependencies, which simplifies the actual deployment process when the system is activated.
Data Source
AI summary
A network slice high-availability method includes determining at least one network slice. Each network slice of the at least one network slice includes at least one network element container. Network element containers of the network slice are distributed at different network nodes. Labels of network slices are used to distinguish different network slices. Resources are isolated among a plurality of network slices. Resources are shared among network slices of a same type. Network containers of the network slices realize high availability for resources.