Network Slicing QoS Migration for Media Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 5G network slicing technologies face challenges in providing reliable and optimal quality of service (QoS) for media services, as network slices are not permanently reliable resources and end-user applications struggle to discover and utilize suitable slices, leading to performance issues during faulty network conditions.
Innovation Solution
The method involves providing media services with network slicing and user/device profiles, where a processor identifies if the required QoS is not met and migrates application flows from one device profile to another based on the capability of the target profile to provide the necessary QoS, ensuring continuous media streaming sessions by utilizing multiple app instances across different user/device profiles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network slicing is implemented to provide differentiated QoS, then service quality and isolation are improved, but device complexity and implementation difficulty increase
Solution Approach 1:
The patent segments the network into multiple virtual slices, each optimized for specific QoS requirements. Device profiles are divided into multiple instances (primary and secondary), with each profile associated with specific network slices. This segmentation allows differentiated QoS treatment while managing complexity through structured organization of slices and profiles.
Solution Approach 2:
The patent creates multi-functional device profiles that can operate across different network slices. A single device profile can be associated with multiple network slices, enabling the same application to leverage different slices based on QoS needs. This universality reduces the need for completely separate configurations for each slice.
2Adaptability or versatility
If network slicing is implemented without standardized support, then service differentiation is improved, but compatibility and wide support deteriorate
Solution Approach 1:
The patent uses parameter-based configuration to enable service differentiation while maintaining compatibility. Device profiles contain configurable parameters that define QoS requirements, network slice associations, and switching conditions. By changing these parameters rather than the fundamental architecture, the system adapts to different service requirements while maintaining standardized interfaces.
3Reliability
If application flows are migrated between device profiles to maintain QoS, then service continuity is improved, but processing complexity and switching overhead increase
Solution Approach 1:
The patent establishes primary and secondary device profiles in advance, with pre-configured network slice associations and QoS parameters. When QoS degradation is detected, the system switches to the pre-prepared secondary profile rather than creating new configurations on-the-fly. This preliminary action reduces processing complexity during actual switching events.
Solution Approach 2:
The patent implements QoS monitoring that provides feedback on network slice performance. When QoS thresholds are not met, the feedback triggers automatic switching between device profiles. This closed-loop feedback mechanism enables automated QoS maintenance without complex manual intervention, reducing processing complexity through rule-based decision making.
Data Source
AI summary
A method includes providing first application flows related to a first application instance via a first device profile, wherein the first device profile corresponds to a first network slice. The method also includes identifying that a quality of service (QOS) required for the first application flows is not met by the first device profile. The method further includes, in response to identifying that the QoS required for the first application flows is not met, selecting a second device profile corresponding to a second network slice based on (i) a capability of the second device profile to provide the QoS required for the first application flows and (ii) a presence of a second application instance corresponding to the first application instance. In addition, the method includes migrating at least one of the first application flows from the first device profile to the second device profile.