IP Library › Granted Patent US 12,238,585
Granted Patent B2
US 12,238,585 · App. 17/534,163 · Granted Feb 25, 2025

Client device and network node for indication of quality-of-service (QOS) non-fulfillment

Inventors: Gustaf Claeson (Lund, SE); Vishnu Preman (Lund, SE); Rama Kumar Mopidevi (Lund, SE); Bengt Lindoff (Kista, SE); Taimoor Abbas (Kista, SE)
Assignee: Huawei Technologies Co., Ltd
H04W28/24H04W24/08H04W28/0273H04W28/12
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,238,585
App. No.
17/534,163
Granted
Feb 25, 2025
Kind
B2
Abstract

The disclosure relates to early detection and indication of a Quality-of-Service (QoS) non-fulfillment in one or more radio links serving an application. A client device monitors for a QoS non-fulfillment in the one or more radio links based on a QoS monitoring configuration associated with the application. The QoS monitoring configuration may be received from a network node and/or derived based on a predefined rule. Upon detection of a QoS non-fulfillment of one or more QoS requirements obtained from the QoS monitoring configuration, the client device provides a QoS non-fulfillment indication to the application. The QoS non-fulfillment indication gives the application an early warning about QoS non-fulfillment on the one or more radio links. Thereby, allowing the application to take precautionary actions to counteract possible negative consequences of the QoS non-fulfillment. Furthermore, the disclosure also relates to corresponding methods and a computer program.

Claims (59)

1. A client device for a wireless communication system, the client device comprising at least one processor, the client device being configured to:

obtain a quality-of-service (QOS) monitoring configuration associated with an application;

monitor for a QoS non-fulfillment in one or more radio links serving the application based on the QoS monitoring configuration; and

upon detection of a QoS non-fulfillment of one or more QoS requirements obtained from the QoS monitoring configuration, provide a QoS non-fulfillment indication to the application via at least one of: a service data adaptation protocol layer, a radio link control layer, or an intermediate layer, wherein the intermediate layer is arranged above the service data adaptation protocol layer and below an application layer.

2. The client device according to claim 1 , configured to:

monitor for a QoS fulfillment in the one or more radio links based on the QoS monitoring configuration; and

provide a QoS fulfillment indication to the application upon detection of a QoS fulfillment of the one or more QoS requirements.

3. The client device according to claim 1 , wherein the QoS monitoring configuration indicates at least one of: a QoS monitoring rule, information of downlink radio links serving the application, a downlink timer associated with the downlink radio links, information of uplink radio links serving the application, an uplink timer associated with the uplink radio links, or a QoS threshold value.

4. The client device according to claim 3 , wherein the detection of the QoS non-fulfillment comprises at least one of:

detect the QoS non-fulfillment in the downlink based on at least one downlink radio link serving the application being indicated as not fulfilling a QoS requirement; or

detect the QoS non-fulfillment in the uplink based on at least one uplink radio link serving the application being indicated as not fulfilling the QoS requirement.

5. The client device according to claim 4 , wherein the detection of the QoS non-fulfillment further comprises:

detect the QoS non-fulfillment in the downlink based on at least one downlink radio link serving the application being indicated as not fulfilling a QoS requirement during a time period defined by the downlink timer; and

detect the QoS non-fulfillment in the uplink based on at least one uplink radio link serving the application being indicated as not fulfilling a QoS requirement during a time period defined by the uplink timer.

6. The client device according to claim 4 , wherein the QoS requirement is at least one of: error rate or latency.

7. The client device according to claim 3 , wherein the radio links serving the application are independent radio links configured for packet duplication in the downlink and the uplink, respectively, and wherein the detection of the QoS non-fulfillment comprises at least one of:

detect the QoS non-fulfillment in the downlink based on all independent downlink radio links serving the application being indicated as not fulfilling a QoS requirement; or

detect the QoS non-fulfillment in the uplink based on all independent uplink radio links serving the application being indicated as not fulfilling a QoS requirement.

8. The client device according to claim 7 , wherein the detection of the QoS non-fulfillment comprises at least one of:

detect the QoS non-fulfillment in the downlink based on all independent downlink radio links serving the application being indicated as not fulfilling a QoS requirement during a time period defined by the downlink timer; or

detect the QoS non-fulfillment in the uplink based on all independent uplink radio links serving the application being indicated as not fulfilling a QoS requirement during a time period defined by the uplink timer.

9. The client device according to claim 1 , configured to:

obtain the QoS monitoring configuration in a first layer;

monitor for the QoS non-fulfillment in the one or more radio links in a third layer and provide QoS indications from the third layer to a second layer; and

detect the QoS non-fulfillment of the one or more QoS requirements in the second layer based on the QoS indications provided by the third layer.

10. The client device according to claim 9 , wherein

the first layer is radio resource control or non access stratum,

the second layer is packet data convergence protocol or medium access control, and

the third layer is medium access control or physical layer.

11. The client device according to claim 1 , wherein the obtaining the QoS monitoring configuration comprises:

receiving at least one part of the QoS monitoring configuration from a network node.

12. The client device according to claim 11 , configured to:

receive the QoS monitoring configuration from the network node in response to a transmission of a QoS monitoring activation request to the network node.

13. The client device according to claim 12 , wherein the QoS monitoring activation request is transmitted in at least one of: a registration request message, a pdu session establishment request message, or a pdu session modification request message.

14. The client device according to claim 1 , wherein the obtaining the QoS monitoring configuration comprises:

deriving at least one part of the QoS monitoring configuration from a predefined rule.

15. The client device according to claim 14 , wherein the obtaining the QoS monitoring configuration comprises:

deriving at least one part of the QoS monitoring configuration from a predefined rule and in dependence on one or more characteristics of QoS flows or IP packet flows associated with the application, wherein the one or more characteristics are at least one of: 5G QoS identifier, QoS flow identifier, resource type, packet error rate, packet delay budget, or survival time and jitter.

16. The client device according to claim 1 , configured to:

perform reverse access stratum mapping in the service data adaptation protocol layer so as to identify one or more QoS flows associated with the application upon detection of the QoS non-fulfillment of the one or more QoS requirements.

17. The client device according to claim 1 , configured to:

apply a packet filter in reverse in the intermediate layer so as to identify the application upon detection of the QoS non-fulfillment of the one or more QoS requirements.

18. The client device according to claim 1 , configured to:

provide a report to a network node, wherein the report indicates information about the QoS non-fulfillment.

19. The client device according to claim 18 , configured to:

provide the report to a network node in a service data adaptation protocol report or in an application layer report.

20. A network node for a wireless communication system, comprising at least one processor, the network node being configured to:

obtain a quality-of-service (QOS) monitoring activation request associated with an application from a client device according to claim 1 ;

determine at least one part of the QoS monitoring configuration based on the QoS monitoring activation request; and

transmit the QoS monitoring configuration to the client device.

21. The network node according to claim 20 , wherein the determining the QoS monitoring configuration comprises:

determining the QoS monitoring configuration based on the QoS monitoring activation request and in dependence on one or more characteristics of QoS flows or IP packet flows associated with the application, wherein the one or more characteristics are at least one of: 5G QoS identifier, QoS flow identifier, resource type, packet error rate, packet delay budget, or survival time and jitter.

22. The network node according to claim 20 , wherein the QoS monitoring configuration indicates at least one of: a QoS monitoring rule, information of downlink radio links serving the application, a downlink timer associated with the downlink radio links, information of uplink radio links serving the application, an uplink timer associated with the uplink radio links, or a QoS threshold value.

23. A method for a client device, the method comprising:

obtaining a quality-of-service (QOS) monitoring configuration associated with an application;

monitoring for a QoS non-fulfillment in one or more radio links serving the application based on the QoS monitoring configuration; and

upon detection of a QoS non-fulfillment of one or more QoS requirements obtained from the QoS monitoring configuration, providing a QoS non-fulfillment indication to the application via at least one of:

a service data adaptation protocol layer, a radio link control layer, or an intermediate layer, wherein the intermediate layer is arranged above the service data adaptation protocol layer and below an application layer.

24. A non-transitory computer-readable medium, having computer-executable instructions stored thereon, the computer-executable instructions, when executed by one or more processors, cause a processor to perform a method according to claim 23 .

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 10, 2022
From: CLAESON, GUSTAF; PREMAN, VISHNU; MOPIDEVI, RAMA KUMAR; LINDOFF, BENGT; ABBAS, TAIMOOR
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 058606/0531 →
Continuity (2)
Continuation PCTEP2019063388 · May 23, 2019
Related Publication 20220086699A1 · Mar 17, 2022
References Cited (30)
US 11153833B2 · Balachandran et al. · 2021 [cited by applicant]
US 20050094560A1 · Montes Linares · 2005 [cited by applicant]
US 20170013514A1 · Tseng · 2017 [cited by examiner]
US 20170230956A1 · Kim et al. · 2017 [cited by applicant]
US 20170325120A1 · Szilagyi et al. · 2017 [cited by applicant]
US 20180176830A1 · Yang et al. · 2018 [cited by applicant]
US 20190052377A1 · Hwang et al. · 2019 [cited by applicant]
US 20190053293A1 · Akoum et al. · 2019 [cited by applicant]
US 20220022192A1 · Sakhnini et al. · 2022 [cited by applicant]
US 20220132603A1 · Adjakple et al. · 2022 [cited by applicant]
US 20220150782A1 · Liu · 2022 [cited by examiner]
CN 102396259A · 2012 [cited by applicant]
JP 6808035B2 · 2021 [cited by applicant]
WO 2017135998A1 · 2017 [cited by applicant]
WO WO2019032503A1 · 2019 [cited by examiner]
WO 2019065617A1 · 2019 [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Scenarios and Requirements for Next Generation Access Technologies (Release 15),” 3GPP TR 38.913 V15.0.0, total 39 pages,… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Requirements for support of radio resource management (Release 15),” 3GPP TS 38.133 V15.5.0, total 893 pages, 3rd Generation P… [cited by applicant]
3GPP TS 24.501 V16.0.2, “Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3,” Release 16, total 480 pages, 3rd Generation Partnership Project, Valbonne, France, 3rd Generation Partnership Project, Valbonne, … [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification (Release 15),” 3GPP TS 38.323 V15.5.0, total 26 pages (Mar. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Link Control (RLC) protocol specification (Release 15),” 3GPP TS 38.322 V16.0.0, total 33 pages, 3rd Generation Partners… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System (Release 16),” 3GPP TS 23.501 V16.0.2, total 317 pages, 3rd Generation Partnership Pr… [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16), 3GPP TS 23.502 V16.0.2, total 419 pages, 3rd Generation Partnership Proj… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15),” 3GPP TS 38.331 V15.5.1, total 491 pages, 3rd Generation Par… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification (Release 15),” 3GPP TS 37.324 V15.1.0, total 13 pages, 3rd Ge… [cited by applicant]
Huawei et al., “Add indication of Notification Control to QoS rules sent to UE,” 3GPP TSG-SA WG2 Meeting #127bis, S2-186157, Newport Beach, USA, XP051459137, Total 2 pshrd, 3rd Generation Partnership Project, Valbonne, … [cited by applicant]
Huawei et al., “KI#3: Evaluation of Solution 16,” SA WG2 Meeting #129bis, S2-1812381(was of S2-1810636), West Palm Beach, FL, USA, XP051563894, Total 6 pages, 3rd Generation Partnership Project, Valbonne, France (Nov. 2… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation (Release 15),” 3GPP TS 38.211 V15.5.0, Total 96 pages, 3rd Generation Partnership Project, Va… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15),” 3GPP TS 38.213 V15.5.0, Total 104 pages, 3rd Generation Partnership Proje… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 15),” 3GPP TS 38.214 V15.5.0, Total 103 pages, 3rd Generation Partnership Project,… [cited by applicant]