IP Library › Granted Patent US 12,598,515
Granted Patent B2
US 12,598,515 · App. 17/738,263 · Granted Apr 7, 2026

Network entities for enhanced QoS monitoring

Inventors: Siva Vakeesar (Kista, SE); Ali Hamidian (Kista, SE)
Assignee: Huawei Technologies Co., Ltd.
H04W28/24H04W28/0268H04W48/18H04W84/042
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,598,515
App. No.
17/738,263
Granted
Apr 7, 2026
Kind
B2
Abstract

The disclosure relates to enhanced quality of service (QoS) monitoring. A first network entity receives a request for monitoring non-fulfilment of a QoS requirement of a packet data unit (PDU) session from a second network entity. Based on the received request, the first network entity obtains a QoS requirement of the PDU session from a third network entity and monitors for non-fulfilment of the obtained QoS requirement based on QoS estimates associated with the obtained QoS requirement. In response to detecting a non-fulfilment of the obtained QoS requirement, the first network entity transmits a second message to the second network entity, wherein the second message indicates the non-fulfilment of the obtained QoS requirement of the PDU session.

Claims (42)

1 . A first network entity, comprising:

at least one processor; and

one or more memories including computer-executable instructions that, when executed by the at least one processor, cause the first network entity to:

receive a first message from a second network entity, wherein the first message indicates a request for monitoring non-fulfilment of a quality of service (QoS) requirement of a packet data unit (PDU) session, and wherein the first network entity is a network data analytics function (NWDAF);

obtain the QoS requirement of the PDU session based on the first message, wherein the obtained QoS requirement is at least one of a network layer QoS parameter and a network layer QoS characteristics, wherein the obtained QoS requirement is associated with a QoS flow of the PDU session, and wherein the PDU session comprises a plurality of QoS flows, and each of the plurality of QoS flows is associated with a respective QoS requirement;

monitor for non-fulfilment of the obtained QoS requirement based on QoS estimates associated with the obtained QoS requirement; and

in response to detecting a non-fulfilment of the obtained QoS requirement, transmit a second message to the second network entity, wherein the second message indicates the non-fulfilment of the obtained QoS requirement of the PDU session.

2 . The first network entity according to claim 1 , wherein the first message indicates the PDU session by at least one of a PDU session identifier, a QoS flow identifier, an internet protocol (IP) address, a client device location, a public mobile network, PLMN, identifier associated with a client device, a data network name (DNN) and a single network slice selection assistance information (S-NSSAI).

3 . The first network entity according to claim 1 , wherein the obtaining the QoS requirement of the PDU session comprises:

transmit a third message to a third network entity, wherein the third message indicates a request for QoS requirement of the PDU session; and

receive a fourth message from the third network entity, wherein the fourth message indicates a QoS requirement of the PDU session.

4 . The first network entity according to claim 3 , wherein the third message indicates the PDU session by at least one of a PDU session identifier, a QoS flow identifier, an IP address, a client device location, a PLMN identifier associated with a client device, a DNN, and a S-NSSAI.

5 . The first network entity according to claim 1 , wherein the detecting a non-fulfilment of the obtained QoS requirement comprises:

detecting that a QoS estimate associated with the obtained QoS requirement is below or above a threshold value.

6 . The first network entity according to claim 5 , wherein the detecting a non-fulfilment of the obtained QoS requirement further comprises at least one of:

detecting that the QoS estimate associated with the obtained QoS requirement is below or above the threshold value in a location; and

detecting that the QoS estimate associated with the obtained QoS requirement is below or above the threshold value during a time period.

7 . The first network entity according to claim 6 , wherein the first message further indicates at least one of the threshold value, the location, and the time period.

8 . The first network entity according to claim 5 , wherein the second message further indicates at least one of the QoS estimate associated with the obtained QoS requirement, a location, a time period, and a confidence level associated with the QoS estimate.

9 . A second network entity comprising:

at least one processor; and

one or more memories including computer-executable instructions that, when executed by the at least one processor, cause the second network entity to:

transmit a first message to a first network entity, wherein the first message indicates a request for monitoring for non-fulfilment of a quality of service (QoS) requirement of a packet data unit (PDU) session, wherein the QoS requirement is at least one of a network layer QoS parameter configured for the PDU session and a network layer QoS characteristics configured for the PDU session, wherein the first network entity is a network data analytics function (NWDAF), wherein the QoS requirement of the PDU session is associated with a QoS flow of the PDU session, and wherein the PDU session comprises a plurality of QoS flows, and each of the plurality of QoS flows is associated with a respective QoS requirement; and

receive a second message from the first network entity, wherein the second message indicates a non-fulfilment of the QoS requirement of the PDU session.

10 . The second network entity according to claim 9 , wherein the first message indicates the PDU session by at least one of a PDU session identifier, a QoS flow identifier, an IP address, a client device location, a PLMN identifier associated with a client device, a data network name (DNN), and a single network slice selection assistance information (S-NSSAI).

11 . The second network entity according to claim 9 , wherein the first message further indicates at least one of a threshold value, a location, and a time period.

12 . The second network entity according to claim 9 , wherein the second message further indicates at least one of a QoS estimate associated with the QoS requirement of the PDU, a location, a time period, and a confidence level associated with the QoS estimate.

13 . A second network entity comprising:

at least one processor; and

one or more memories including computer-executable instructions that, when executed by the at least one processor, cause the second network entity to:

receive a third message from a first network entity, wherein the third message indicates a request for quality of service (QoS) requirement of a packet data unit (PDU) session, and wherein the first network entity is a network data analytics function (NWDAF);

obtain the QoS requirement of the PDU session based on the third message, wherein the obtained QoS requirement is associated with a QoS flow of the PDU session, and wherein the PDU session comprises a plurality of QoS flows, and each of the plurality of QoS flows is associated with a respective QoS requirement; and

transmit a fourth message to the first network entity, wherein the fourth message indicates the obtained QoS requirement of the PDU session.

14 . The second network entity according to claim 13 , wherein the third message indicates the PDU session by at least one of a PDU session identifier, a QoS flow identifier, an IP address, a client device location, a PLMN identifier associated with a client device, a data network name (DNN), and a single network slice selection assistance information (S-NSSAI).

15 . The second network entity according to claim 13 , wherein the QoS requirement of the PDU session is at least one of a network layer QoS parameter and a network layer QoS characteristics.

16 . The first network entity according to claim 1 , wherein monitor for non-fulfilment of the obtained QoS requirement based on the QoS estimates associated with the obtained QoS requirement comprises:

obtaining network performance data to derive network analytics associated with one or more key performance indicators; and

determining the QoS estimates associated with the obtained QoS requirement based on the network analytics.

17 . The first network entity according to claim 1 , wherein the first message comprises a request to subscribe to monitoring for non-fulfilment of the QoS requirement of the PDU session.

18 . The second network entity according to claim 9 , wherein the first message comprises a request to subscribe to monitoring for non-fulfilment of the QoS requirement of the PDU session.

19 . The first network entity according to claim 1 , wherein the second message comprises a flag or an information element that indicates the non-fulfilment of the obtained QoS requirement of the PDU session.

20 . The second network entity according to claim 9 , wherein the second message comprises a flag or an information element that indicates the non-fulfilment of the QoS requirement of the PDU session.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 24, 2022
From: VAKEESAR, SIVA; HAMIDIAN, ALI
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 060888/0955 →
Continuity (2)
Continuation PCTEP2019080491 · Nov 7, 2019
Related Publication 20220264375A1 · Aug 18, 2022
References Cited (41)
US 10492096B2 · Lee · 2019 [cited by examiner]
US 11350475B2 · Youn · 2022 [cited by examiner]
US 11412403B2 · Godin · 2022 [cited by examiner]
US 11825332B2 · Schliwa-Bertling · 2023 [cited by examiner]
US 11956513B2 · Nadeau · 2024 [cited by examiner]
US 12052657B2 · Garcia Martin · 2024 [cited by examiner]
US 12082050B2 · Wang · 2024 [cited by examiner]
US 12133108B2 · Wang · 2024 [cited by examiner]
US 12143863B2 · Van Phan · 2024 [cited by examiner]
US 12185156B2 · Wei · 2024 [cited by examiner]
US 12185166B2 · Kousaridas · 2024 [cited by examiner]
US 12231967B2 · Wei · 2025 [cited by examiner]
US 12238586B2 · Ahmad · 2025 [cited by examiner]
US 20180324633A1 · Lee · 2018 [cited by examiner]
US 20190222489A1 · Shan · 2019 [cited by examiner]
US 20190253917A1 · Dao · 2019 [cited by applicant]
US 20200314686A1 · Godin · 2020 [cited by examiner]
US 20210385693A1 · Wang · 2021 [cited by examiner]
US 20220022090A1 · Schliwa-Bertling · 2022 [cited by examiner]
US 20220312275A1 · Van Phan · 2022 [cited by examiner]
US 20220386164A1 · Lee · 2022 [cited by examiner]
US 20240334520A1 · Pancorbo Marcos · 2024 [cited by examiner]
US 20250159558A1 · Wei · 2025 [cited by examiner]
EP 3238389B1 · 2019 [cited by applicant]
Huawei, “NG-U Delay Measurement for QoS Monitoring,” 3GPP TSG-RAN3 Meeting #105bis, R3-195253, Chongqing, China, Oct. 14-18, 2019, 2 pages. [cited by applicant]
[No Author Listed] [online], “How to Implement Time-to-Trigger (TTT) Used in 5G and LTE Handover Modeling?”, Aug. 18, 2021, retrieved on Nov. 11, 2022, retrieved from URL <https://tetcos.freshdesk.com/support/solutions/… [cited by applicant]
Ericsson et al., “Update of QoS Related Analytics Terminology,” 3GPP TSG-SA WG2 Meeting #134, S2-1908222, Sapporo, Japan, Jun. 24-28, 2019, 2 pages. [cited by applicant]
3GPP TS 23.032 V15.1.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Universal Geographical Area Description (GAD) (Release 15),” Sep. 2018, 32 pages. [cited by applicant]
3GPP TS 23.271 V15.1.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional Stage 2 Description of Location Services (LCS) (Release 15),” Sep. 2018, 184 pages. [cited by applicant]
3GPP TS 23.273 V16.0.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G System (5GS) Location Services (LCS); Stage 2 (Release 16),” Jun. 2019, 86 pages. [cited by applicant]
3GPP TS 23.287 V16.1.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture Enhancements for 5G System (5GS) to Support Vehicle-to-Everything (V2X) Services (Rele… [cited by applicant]
3GPP TS 23.288 V16.1.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture Enhancements for 5G System (5GS) to Support Network Data Analytics services (Release 1… [cited by applicant]
3GPP TS 23.501 V16.0.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16),” Mar. 2019, 318 pages. [cited by applicant]
3GPP TS 28.533 V16.1.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and Orchestration; Architecture Framework (Release 16),” Sep. 2019, 27 pages. [cited by applicant]
3GPP TS 28.552 V16.2.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and Orchestration; 5G Performance Measurements (Release 16),” Jun. 2019, 98 pages. [cited by applicant]
3GPP TS 28.554 V16.1.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and Orchestration; 5G End to End Key Performance Indicators (KPI) (Release 16),” Jun. 20… [cited by applicant]
3GPP TS 36.314 V15.2.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2—Measurements (Release 15),” Dec. 2018, 28 pag… [cited by applicant]
3GPP TR 37.816 V16.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on RAN-Centric Data Collection and Utilization for LTE and NR (Release 16),” Jul. 2019, 35 pages. [cited by applicant]
International Search Report and Written Opinion in International AppIn. No. PCT/EP2019/080491, mailed on Aug. 27, 2020, 24 pages. [cited by applicant]
3GPP TS 23.288 V0.4.0, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for 5G System (5GS) to support network data analytics services (Release 16)… [cited by applicant]
EP Communication Pursuant to Article 94(3) EPC in European Appln. No. 19804656.7, mailed on Jan. 14, 2026, 15 pages. [cited by applicant]