Slice-Aware Network Recovery and Convergence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G networks, failures in transport networks can adversely affect traffic routing and latency metrics associated with network slices, as existing technologies lack effective mechanisms for prioritizing network recovery and convergence based on slice-specific requirements.
Innovation Solution
Implementing a slice-aware network architecture where routers and network devices are notified of slice priorities, enabling the identification and establishment of alternate paths that align with Service Level Agreements (SLAs), and communicating this information across the network to ensure convergence and recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traffic is re-routed after a failure in a transport network, then network connectivity is restored, but latency and other slice-specific metrics are adversely affected
Solution Approach 1:
The system pre-establishes multiple candidate paths for each network slice before failures occur. When a failure is detected, the system can immediately switch to a pre-calculated alternate path that maintains slice-specific performance requirements, rather than performing reactive path computation that would increase latency.
Solution Approach 2:
The system dynamically changes routing parameters based on failure conditions and slice requirements. Different path selection criteria are applied depending on the slice type and failure scenario, allowing optimization of latency, bandwidth, or other metrics specific to each slice's service level agreement.
2Reliability
If conventional routing protocols are used for network recovery, then general network connectivity is restored, but slice-specific performance requirements are not met
Solution Approach 1:
The network is segmented into multiple logical slices, each with its own performance requirements and path preferences. The routing system maintains separate path computations and recovery mechanisms for each slice, allowing slice-specific optimization while maintaining overall network connectivity.
Solution Approach 2:
Different quality attributes are assigned to different paths based on slice requirements. Each network slice receives routing treatment tailored to its specific performance needs (e.g., low latency for real-time traffic, high bandwidth for data-intensive applications), rather than uniform routing for all traffic.
3Speed
If fast convergence is prioritized during network failure recovery, then routing speed is improved, but slice performance metrics such as latency are degraded
Solution Approach 1:
Multiple candidate paths are pre-computed and staged before failures occur, with path selection criteria already determined based on slice requirements. This eliminates the need for slow reactive path computation during failures, achieving both fast convergence and maintained performance metrics.
Data Source
AI summary
A method may include identifying network slices associated with transmitting data in a network and determining, by a routing device, that a failure associated with a path used to transmit data has occurred. The method may also include determining, by the routing device, whether the failure is associated with one of the plurality of network slices. The method may further include prioritizing, by the routing device, a route selection process in response to determining that the failure is associated with one of the plurality of network slices.