QoS Translation for Latency-Sensitive Application Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In modern telecommunications networks, data types other than voice and video, such as game application data, often experience higher latencies due to lower prioritization compared to VoLTE and ViLTE data streams, leading to inconsistent service quality.
Innovation Solution
Configuring the network to utilize VoLTE or ViLTE specifications for latency-sensitive data while allowing other data to be transmitted using native or alternative QoS specifications, with translation and identification mechanisms to ensure seamless delivery across different networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If data is transmitted using native QoS specifications, then data transmission flexibility is maintained, but latency-sensitive application data experiences higher latency and inconsistent service quality
Solution Approach 1:
The patent changes the QoS parameter assignment dynamically based on application requirements. Latency-sensitive application data is assigned the QoS parameters of VoLTE/ViLTE data streams (higher priority, shorter scheduling intervals), while other data maintains native QoS specifications. This parameter transformation resolves the contradiction by allowing selective optimization of latency-critical traffic without compromising overall system flexibility.
Solution Approach 2:
The patent segments application data into different categories based on latency sensitivity. Latency-sensitive data (e.g., game control data) is separated and transmitted using VoLTE/ViLTE QoS specifications, while non-latency-sensitive data uses native QoS specifications. This segmentation allows differential treatment of data streams, improving latency for critical applications while maintaining transmission flexibility for other data types.
2Reliability
If VoLTE/ViLTE specifications are used for all data, then latency and service quality are improved, but network complexity and resource allocation complexity increase
Solution Approach 1:
The patent applies local quality by assigning different QoS specifications to different data streams based on their specific requirements. Only latency-sensitive application data receives the enhanced VoLTE/ViLTE treatment, while other data continues to use standard QoS specifications. This localized application of high-priority QoS parameters improves service quality consistency for critical applications without unnecessarily complicating the overall network configuration.
3Speed
If latency-sensitive data is prioritized using VoLTE/ViLTE specifications, then transmission speed and consistency are improved, but network resource allocation complexity increases
Solution Approach 1:
The patent applies partial action by selectively applying VoLTE/ViLTE QoS specifications only to latency-sensitive application data rather than all data traffic. This selective prioritization achieves improved transmission speed and consistency for critical applications while avoiding the excessive complexity that would result from applying uniform high-priority treatment to all network traffic.
Data Source
AI summary
A telecommunication network associated with a wireless telecommunication provider can be configured to transmit application data using different quality of service (QoS) specifications. In some configurations, data, other than voice and video data, can be transmitted using VoLTE or ViLTE data streams. According to some examples, network hardware and/or software (e.g., in the core network of a telecommunications network), and/or an application on the UE (smartphone, tablet, etc.) may translate data to be compatible with the VoLTE or ViLTE specifications. The translated data is transmitted from the device to the telecommunications network as a VoLTE or ViLTE packet stream. The converted packets may be identified (e.g., a unique digital signature) so that the corresponding hardware and software in the MSO can identify that a stream of VoLTE or ViLTE packets is to be converted back into the native format of the application before being routed to a destination.