5G QoS Violation Reporting for Delay-Critical GBR Flows
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 5G QoS models lack effective mechanisms to report events where QoS parameters of delay critical GBR QoS flows are violated, which can lead to serious issues in applications like industrial automation and automated driving vehicles.
Innovation Solution
Implement methods and network nodes to detect QoS violations in PDU sessions and send corresponding reports to the session management function (SMF), including configurations based on policy and charging control rules, and timestamping packet delays to track violations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the current 5G QoS model uses Notification Control parameter for GFBR support notifications, then the network can notify when Guaranteed Flow Bit Rate cannot be supported, but it cannot report events where QoS parameters of delay critical GBR QoS flows are violated
Solution Approach 1:
The existing Notification Control mechanism is extended to serve multiple functions: it continues to notify when GFBR cannot be supported while simultaneously reporting QoS parameter violations for delay critical GBR QoS flows. This multi-functional approach allows the system to address multiple reporting needs without adding separate dedicated mechanisms, thereby improving reliability while controlling complexity.
Solution Approach 2:
The Notification Control parameter is enhanced by introducing new notification types and conditions specifically for QoS parameter violations. The parameter configuration is modified to include violation detection thresholds, notification triggers, and reporting formats tailored for delay critical GBR flows, enabling the system to detect and report QoS violations without fundamentally changing the overall QoS model structure.
2Ease of operation
If QoS violations are not reported, then the QoS model remains simple, but applications like industrial automation and automated driving vehicles cannot identify and address QoS issues timely
Solution Approach 1:
A feedback mechanism is implemented where QoS parameter violations are detected, reported to the network, and triggered to send notifications to affected applications. This closed-loop feedback enables applications like industrial automation and automated driving to receive timely information about QoS violations, allowing them to identify and address issues promptly while maintaining appropriate information flow control.
3Reliability
If comprehensive QoS monitoring is implemented for all parameters, then all QoS violations can be detected, but the signaling overhead and network load increase significantly
Solution Approach 1:
QoS monitoring and reporting is applied selectively based on local requirements: only delay critical GBR QoS flows with specific violation conditions trigger notifications. The monitoring intensity and reporting frequency are adjusted locally according to flow characteristics and network conditions, enabling accurate detection of critical violations while avoiding unnecessary signaling for non-critical flows, thus reducing overall network overhead.
Solution Approach 2:
Instead of implementing continuous comprehensive monitoring for all QoS parameters, the system applies partial monitoring focused on critical thresholds and violation conditions. Notifications are generated only when specific violation criteria are met, providing sufficient detection accuracy for reliability-critical applications while minimizing signaling overhead by avoiding excessive reporting of normal operational variations.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
A method in a network node comprises: detecting a Quality of Service (QoS) Violated Event in respect of a particular QoS flow of a Protocol Data Unit (PDU) session; and sending a corresponding QoS violated event report to any one or more of: a Session Management Function (SMF) of the network; a Policy Control Function (PCF) of the network; an Application Function (AF) of the network; and a third party service provider.