EP4690722A1

EP4690722A1 - Quality of service monitoring and reporting in 5g systems

Info

Publication number: EP4690722A1
Application number: EP24718134.0A
Authority: EP
Inventors: Maria Luisa Mas Rosique; Fuencisla Garcia Azorero; Susana Fernandez Alonso; Ignacio RIVAS MOLINA; Paul Schliwa-Bertling
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-04-05
Filing date: 2024-04-05
Publication date: 2026-02-11
Also published as: WO2024209041A1

Abstract

This disclosure provides a method for Quality of Service monitoring control in a communications network. The method comprises a second network node receiving QoS measurement requests from a first node, establishing an authorized QoS Monitoring Policy, and calculating QoS parameters based on QoS Monitoring reports of individual QoS Flows. These measurements are then communicated back to the first node. Further, the method includes receiving QoS Monitoring reports, sending measurements requested by the Application Function (AF), and evaluating the feasibility of a direct notification path based on the QoS Monitoring Policy's alignment with AF requests, including considerations for the Policy and Charging Function (PCF) understanding of results and measurement matching. Also, it encompasses transmitting a round-trip delay event for multiple flows, indicating separated uplink and downlink traffic delays or delays measured between User Equipment (UE) and a User Plane Function (UPF), thereby enhancing QoS monitoring and control in communication networks.

Description

QUALITY OF SERVICE MONITORING AND REPORTING IN 5G SYSTEMS

TECHNICAL FIELD

The present invention generally relates to telecommunication networks, and more specifically, the invention relates to Quality of Service (QoS) monitoring and reporting in 5G systems.

BACKGROUND

Quality of Service (QoS) monitoring plays a crucial role in ensuring the performance and reliability of telecommunication networks, particularly in the context of 5G (Fifth Generation) networks or systems. QoS monitoring involves measuring various parameters, such as packet delays, for certain traffic flows. These measurements are typically enabled based on requests from Application Functions (AF) or operator policies configured in the Policy Control Function (PCF). The PCF generates an authorized QoS Monitoring policy and sends it to the Session Management Function (SMF) for configuration and reporting.

Extended Reality (XR) and interactive media services further demands effective QoS monitoring. These services include Augmented Reality (AR) and Virtual Reality (VR) applications, cloud gaming, and tactile or multi-modal communication services. These applications and services require high data rates and low latency communication to function properly.

Measurements of QoS parameters have been defined in 3GPP (Third Generation Partnership Project) specification for 5G (Fifth Generation) systems These measurements include measurements of QoS parameters in QoS Monitoring, and measurements of QoS Parameters determined and reported by the PCF based on measurements taken over several QoS Flows or statistically calculated from measurements over time. To obtain these basic measurements for calculations, the PCF uses QoS Monitoring of individual QoS flows.

A problematic aspect of the existing Quality of Service (QoS) monitoring is limited efficiency functioning of advanced services, such as extended Reality (XR) and interactive media services. Particularly, the limitation of having one QoS Monitoring control information per PCC (Policy Charging and Control) rule. This leads to exceeding the limits of QoS flows in the network in certain scenarios. For example, the PCF may need to derive specific PCC rules with QoS monitoring requirements for the same services, potentially surpassing the limits of QoS flows in the network. This may lead to network congestion and degraded service quality.

A further problematic aspect of the existing solutions is the increased signaling and processing load. Deriving multiple PCC rules with QoS monitoring requirements for the same services adds extra signaling and logic for the processing of monitoring information. This can result in higher processing overhead and reduced network efficiency.

A further problematic aspect of the existing solutions is misbehavior and presence of contradictory information. The presence of multiple QoS monitoring policies for the same services may lead to misbehavior, contradictory information, and race conditions, adversely affecting network performance and reliability.

SUMMARY

The invention is set out in the appended set of claims.

The object of the invention is to improve the Quality of Service (QoS) monitoring process in 5G systems, enabling more efficient and accurate management of QoS parameters for advanced services such as Extended Reality (XR) and interactive media services. The invention aims to achieve this objective by enhancing the role of the Policy Control Function (PCF) in QoS monitoring, making informed decisions about QoS monitoring policies and reporting paths.

An aspect of the invention relates to a method performed by a first network node for Quality of Service monitoring control in a communications network. The method comprises transmitting from a first network node to a second network node one or more requests for measurements of QoS parameters associated with a PCC Rule; and receiving at the first network node from the second network node one or more measurements of QoS parameters determined at the PCF. In some embodiments, the method further comprises receiving at the first network node from the second network node the measurements of QoS parameters requested by AF based on the QoS Monitoring reports. In some embodiments, the method further comprises receiving at the first network node from the second network node a response indicating whether direct notification is possible or not possible. In some embodiments, the method further comprises receiving at the first network node from the second network node a round-trip delay for multiple flows event, particularly wherein the event indicates a report of round-trip delay measurements when uplink (LIL) and downlink (DL) traffic are separated into two flows and/or wherein the event is derived from measurements of packet delay between a User Equipment (UE) and a User Plane Function (UPF). In some embodiments, the PCF determines the QoS Monitoring Policy considering which QoS Monitoring measurements of QoS parameters are required to provide all QoS monitoring requests and/or measurements requested by the AF. In some embodiments, the PCF determines whether direct reporting is possible or not possible, particularly wherein it is determined by evaluating if QoS Monitoring reports generated according to the determined QoS Monitoring Policy may or may not be suitable for sending to the AF directly by a User Plane Function (UPF). In some embodiments, the method further comprises notifying from the PCF to the AF that direct reporting is possible or not possible. In some embodiments, the method further comprises notifying from the PCF to the AF that direct reporting is not possible if a direct notification indication is included in the request from the AF. In some embodiments, the method further comprises subscribing from the AF to the PCF for measurements of QoS parameters that the PCF derives from QoS Monitoring reports, particularly wherein the QoS Monitoring reports are received at the PCF from a Session Management Function (SMF). In some embodiments, the method further comprising subscribing from the AF to the PCF for measurements of QoS parameters which are derived by the PCF from QoS Monitoring measurements of one or more individual QoS Flows, particularly wherein the QoS Monitoring measurements comprise a round-trip delay for multiple flows. In some embodiments, the method further comprises the PCF deriving the round-trip delay measurement and transmitting the derived round-trip delay measurement to the AF. In some embodiments, the determining of the authorized QoS Monitoring policy at the PCF comprises at least one of: considering all measurements of the QoS parameters included in the request from the AF; and considering QoS Monitoring measurements of QoS parameters and measurements of QoS parameters derived by the PCF from QoS Monitoring measurements on one or more individual flows. In some embodiments, the derived measurements by the PCF include round-trip delay measurements for multiple flows and/or Packet Delay Variation monitoring and reporting and/or difference in delay of more than one flow. In some embodiments, the method further comprises receiving at the PCF from the AF an indication of direct event notification in the request; and determining at the PCF whether to set the indication for direct event notification in the QoS Monitoring Policy based on the suitability of QoS Monitoring reports to be sent to the AF directly by a User Plane Function (UPF). In some embodiments, the PCF transmits to the AF an indication that direct event notification is not possible if the PCF decides not to set the indication for direct event notification. In some embodiments, the authorized QoS Monitoring policy comprises at least one of: one or more QoS parameters to be measured, a reporting frequency, a reporting threshold for each QoS parameter, a minimum waiting time between subsequent reports, a reporting period, a target of reporting, and an indication of direct event notification. In some embodiments, the first network node is an Application Function (AF) or a Network Exposure Function (NEF), and the second network node is a Policy Control Function (PCF) or a Network Exposure Function (NEF).

An aspect of the invention relates to a method performed by a second network node for Quality of Service monitoring control in a communications network. The method comprises receiving at a second network node from a first network node one or more requests for measurements of QoS parameters associated with a PCC Rule; determining at the second network node a single authorized QoS Monitoring Policy for the 5G Core Network (5GC) to produce measurements of QoS parameters; determining at the second network node one or more measurements of QoS parameters from one or more QoS Monitoring reports, particularly wherein the QoS Monitoring reports are of one or more individual QoS Flows; and transmitting from the second network node to the first network node the one or more measurements of QoS parameters. In some embodiments, the method further comprises receiving at the second network node one or more QoS Monitoring reports. In some embodiments, the method further comprises transmitting from the second network node to the first network node the measurements of QoS parameters requested by AF based on the QoS Monitoring reports. In some embodiments, the method further comprises determining at the second network node whether direct notification path is possible or not possible based on the determined QoS Monitoring Policy and its relation to the original AF request, particularly wherein the relation pertains to the PCF understanding of the QoS Monitoring results, and/or the measurement of QoS parameters at the PCF match the measurement of QoS parameters requested by the AF; and transmitting from the second network node to the first network node a response indicating whether direct notification is possible or not possible. In some embodiments, the method further comprises transmitting from the second network node to the first network node a round-trip delay for multiple flows event, particularly wherein the event indicates a report of round-trip delay measurements when uplink (LIL) and downlink (DL) traffic are separated into two flows and/or wherein the event is derived from measurements of packet delay between a User Equipment (UE) and a User Plane Function (UPF). In some embodiments, the PCF determines the QoS Monitoring Policy considering which QoS Monitoring measurements of QoS parameters are required to provide all QoS monitoring requests and/or measurements requested by the AF. In some embodiments, the PCF determines whether direct reporting is possible or not possible, particularly wherein it is determined by evaluating if QoS Monitoring reports generated according to the determined QoS Monitoring Policy may or may not be suitable for sending to the AF directly by a User Plane Function (UPF). In some embodiments, the method further comprises notifying from the PCF to the AF that direct reporting is possible or not possible. In some embodiments, the method further comprises notifying from the PCF to the AF that direct reporting is not possible if a direct notification indication is included in the request from the AF. In some embodiments, the method further comprises subscribing from the AF to the PCF for measurements of QoS parameters that the PCF derives from QoS Monitoring reports, particularly wherein the QoS Monitoring reports are received at the PCF from a Session Management Function (SMF). In some embodiments, the method further comprising subscribing from the AF to the PCF for measurements of QoS parameters which are derived by the PCF from QoS Monitoring measurements of one or more individual QoS Flows, particularly wherein the QoS Monitoring measurements comprise a round-trip delay for multiple flows. In some embodiments, the method further comprises the PCF deriving the round-trip delay measurement and transmitting the derived round-trip delay measurement to the AF. In some embodiments, the determining of the authorized QoS Monitoring policy at the PCF comprises at least one of: considering all measurements of the QoS parameters included in the request from the AF; and considering QoS Monitoring measurements of QoS parameters and measurements of QoS parameters derived by the PCF from QoS Monitoring measurements on one or more individual flows. In some embodiments, the derived measurements by the PCF include round-trip delay measurements for multiple flows and/or Packet Delay Variation monitoring and reporting and/or difference in delay of more than one flow. In some embodiments, the method further comprises receiving at the PCF from the AF an indication of direct event notification in the request; and determining at the PCF whether to set the indication for direct event notification in the QoS Monitoring Policy based on the suitability of QoS Monitoring reports to be sent to the AF directly by a User Plane Function (LIPF). In some embodiments, the PCF transmits to the AF an indication that direct event notification is not possible if the PCF decides not to set the indication for direct event notification. In some embodiments, the authorized QoS Monitoring policy comprises at least one of: one or more QoS parameters to be measured, a reporting frequency, a reporting threshold for each QoS parameter, a minimum waiting time between subsequent reports, a reporting period, a target of reporting, and an indication of direct event notification. In some embodiments, the first network node is an Application Function (AF) or a Network Exposure Function (NEF), and the second network node is a Policy Control Function (PCF) or a Network Exposure Function (NEF).

Other aspects of the invention relate to mobile network nodes, particularly a second network node (111 , 700), a first network node (113, 600) configured to perform the respective methods as described herein. Other aspects of the invention relate to computer program and computer program products.

Additional objectives, features and advantages of the concepts disclosed herein will be apparent from the following description, claims and drawings, or may be learned by practice of the described technologies and concepts as set forth herein.

Advantageously, the proposed solution enhances the role of the Policy Control Function (PCF) in QoS monitoring, with the PCF gaining the intelligence to make informed decisions regarding QoS monitoring policies and reporting paths.

Further advantageously, the proposed solution enables the provision of a variety of QoS parameter measurements, including those that are part of QoS monitoring or determined by the PCF based on QoS monitoring reports. This enhanced capability allows for a more accurate QoS parameters, leading to better network performance.

Further advantageously, the proposed solution allows, for one single Authorized QoS Monitoring Policy per PCC Rule, minimizing the measurements that are enabled in the 5GS on a QoS flow. This contributes to improved network efficiency and reduces the potential for conflicts or redundancies in QoS monitoring.

Further advantageously, the proposed solution allows the selection of the notification path according to the AF request and the Monitoring Policy. This improves flexibility and ensures that the appropriate network functions (PCF, SMF, or UPF) send the QoS Monitoring reports to the AF. Further advantageously, the proposed solution allows the PCF to process QoS Monitoring reports received from SMF and adapt them to report QoS Monitoring according to the AF request, the proposed solution simplifies the reporting procedure. This results in reduced signaling and more efficient QoS monitoring process.

Further advantageously, the proposed solution allows better support of advanced services like extended Reality (XR) and interactive media services by telecommunication network operators.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to best describe the manner in which the disclosed concepts may be implemented, as well as define other objects, advantages and features of the disclosure, a more particular description is provided below and is illustrated in the appended drawings. Understanding that these drawings depict only exemplary embodiments of the invention and are not therefore to be considered to be limiting in scope, the examples will be described and explained with additional specificity and detail through the use of the accompanying drawings.

Figure 1 illustrates an example networked system in accordance with particular embodiments of the solution described herein.

Figure 2 illustrates an example signaling diagram showing a procedure according to particular embodiments of the solution described herein.

Figure 3 illustrates an example signaling diagram showing a procedure according to particular embodiments of the solution described herein.

Figure 4 illustrates an example flowchart showing a method performed by a mobile network node according to particular embodiments of the solution described herein.

Figure 5 illustrates an example flowchart showing a method performed by a mobile network node according to particular embodiments of the solution described herein.

Figure 6 illustrates an example block diagram of a mobile network node configured in accordance with particular embodiments of the solution described herein. Figure 7 illustrates an example block diagram of a mobile network node configured in accordance with particular embodiments of the solution described herein.

Figure 8 illustrates an example block diagram of a virtualized environment.

DETAILED DESCRIPTION

The invention will now be described in detail hereinafter with reference to the accompanying drawings, in which examples of embodiments or implementations of the invention are shown. The invention may, however, be embodied or implemented in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present invention to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment. These embodiments of the disclosed subject matter are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.

The example embodiments described herein arise in the context of a telecommunications network, including but not limited to a telecommunications network that conforms to and/or otherwise incorporates aspects of a fifth generation (5G) architecture. Figure 1 is an example networked system 100 in accordance with example embodiments of the present disclosure. Figure 1 specifically illustrates User Equipment (UE) 101 , which may be in communication with a (Radio) Access Network (RAN) 102 and Access and Mobility Management Function (AMF) 106 and User Plane Function (UPF) 103. The AMF 106 may, in turn, be in communication with core network services including Session Management Function (SMF) 107 and Policy Control Function (PCF) 111. The core network services may also be in communication with an Application Server/ Application Function (AS/AF) 113. Other networked services also include TSCTSF (Traffic Steering Control and Traffic Switching Function) 108, Authentication Server Function (AUSF) 105, User Data Management (LIDM) 112, Network Exposure Function (NEF) 109, Network Repository Function (NRF) 110 and Data Network (DN) 104. In some example implementations of embodiments of the present disclosure, each one of the entities in the networked system 100 are considered to be a Network Function (NF). One or more additional instances of the NFs may be incorporated into the networked system.

The solution described herein aims to improve the Quality of Service (QoS) monitoring process in 5G systems, enabling more efficient and accurate management of QoS parameters for advanced services such as Extended Reality (XR) and interactive media services. The invention aims to achieve this objective by enhancing the role of the Policy Control Function (PCF) in QoS monitoring, making informed decisions about QoS monitoring policies and reporting paths.

This disclosure provides a method for Quality of Service monitoring control in a communications network. The method comprises receiving at a second network node from a first network node one or more requests for measurements of QoS parameters associated with a PCC Rule; determining at the second network node a single authorized QoS Monitoring Policy for the 5G Core Network (5GC) to produce measurements of QoS parameters; determining at the second network node one or more measurements of QoS parameters from one or more QoS Monitoring reports, particularly wherein the QoS Monitoring reports are of one or more individual QoS Flows; and transmitting from the second network node to the first network node the one or more measurements of QoS parameters. In some embodiments, the method further comprises receiving at the second network node one or more QoS Monitoring reports. In some embodiments, the method further comprises transmitting from the second network node to the first network node the measurements of QoS parameters requested by AF based on the QoS Monitoring reports. In some embodiments, the method further comprises determining at the second network node whether direct notification path is possible or not possible based on the determined QoS Monitoring Policy and its relation to the original AF request, particularly wherein the relation pertains to the PCF understanding of the QoS Monitoring results, and/or the measurement of QoS parameters at the PCF match the measurement of QoS parameters requested by the AF; and transmitting from the second network node to the first network node a response indicating whether direct notification is possible or not possible. In some embodiments, the method further comprises transmitting from the second network node to the first network node a round-trip delay for multiple flows event, particularly wherein the event indicates a report of round-trip delay measurements when uplink (LIL) and downlink (DL) traffic are separated into two flows and/or wherein the event is derived from measurements of packet delay between a User Equipment (UE) and a User Plane Function (UPF). In some embodiments, the PCF determines the QoS Monitoring Policy considering which QoS Monitoring measurements of QoS parameters are required to provide all QoS monitoring requests and/or measurements requested by the AF. In some embodiments, the PCF determines whether direct reporting is possible or not possible, particularly wherein it is determined by evaluating if QoS Monitoring reports generated according to the determined QoS Monitoring Policy may or may not be suitable for sending to the AF directly by a User Plane Function (UPF). In some embodiments, the method further comprises notifying from the PCF to the AF that direct reporting is possible or not possible. In some embodiments, the method further comprises notifying from the PCF to the AF that direct reporting is not possible if a direct notification indication is included in the request from the AF. In some embodiments, the method further comprises subscribing from the AF to the PCF for measurements of QoS parameters that the PCF derives from QoS Monitoring reports, particularly wherein the QoS Monitoring reports are received at the PCF from a Session Management Function (SMF). In some embodiments, the method further comprising subscribing from the AF to the PCF for measurements of QoS parameters which are derived by the PCF from QoS Monitoring measurements of one or more individual QoS Flows, particularly wherein the QoS Monitoring measurements comprise a round-trip delay for multiple flows. In some embodiments, the method further comprises the PCF deriving the round-trip delay measurement and transmitting the derived round-trip delay measurement to the AF. In some embodiments, the determining of the authorized QoS Monitoring policy at the PCF comprises at least one of: considering all measurements of the QoS parameters included in the request from the AF; and considering QoS Monitoring measurements of QoS parameters and measurements of QoS parameters derived by the PCF from QoS Monitoring measurements on one or more individual flows. In some embodiments, the derived measurements by the PCF include round-trip delay measurements for multiple flows and/or Packet Delay Variation monitoring and reporting and/or difference in delay of more than one flow. In some embodiments, the method further comprises receiving at the PCF from the AF an indication of direct event notification in the request; and determining at the PCF whether to set the indication for direct event notification in the QoS Monitoring Policy based on the suitability of QoS Monitoring reports to be sent to the AF directly by a User Plane Function (UPF). In some embodiments, the PCF transmits to the AF an indication that direct event notification is not possible if the PCF decides not to set the indication for direct event notification. In some embodiments, the authorized QoS Monitoring policy comprises at least one of: one or more QoS parameters to be measured, a reporting frequency, a reporting threshold for each QoS parameter, a minimum waiting time between subsequent reports, a reporting period, a target of reporting, and an indication of direct event notification. In some embodiments, the first network node is an Application Function (AF) or a Network Exposure Function (NEF), and the second network node is a Policy Control Function (PCF) or a Network Exposure Function (NEF).

An aspect of the invention relates to a method performed by a second network node for Quality of Service monitoring control in a communications network. The method comprises receiving at a second network node from a first network node one or more requests for measurements of QoS parameters associated with a PCC Rule; determining at the second network node a single authorized QoS Monitoring Policy for the 5G Core Network (5GC) to produce measurements of QoS parameters; determining at the second network node one or more measurements of QoS parameters from one or more QoS Monitoring reports, particularly wherein the QoS Monitoring reports are of one or more individual QoS Flows; and transmitting from the second network node to the first network node the one or more measurements of QoS parameters. In some embodiments, the method further comprises receiving at the second network node one or more QoS Monitoring reports. In some embodiments, the method further comprises transmitting from the second network node to the first network node the measurements of QoS parameters requested by AF based on the QoS Monitoring reports. In some embodiments, the method further comprises determining at the second network node whether direct notification path is possible or not possible based on the determined QoS Monitoring Policy and its relation to the original AF request, particularly wherein the relation pertains to the PCF understanding of the QoS Monitoring results, and/or the measurement of QoS parameters at the PCF match the measurement of QoS parameters requested by the AF; and transmitting from the second network node to the first network node a response indicating whether direct notification is possible or not possible. In some embodiments, the method further comprises transmitting from the second network node to the first network node a round-trip delay for multiple flows event, particularly wherein the event indicates a report of round-trip delay measurements when uplink (LIL) and downlink (DL) traffic are separated into two flows and/or wherein the event is derived from measurements of packet delay between a User Equipment (UE) and a User Plane Function (UPF). In some embodiments, the PCF determines the QoS Monitoring Policy considering which QoS Monitoring measurements of QoS parameters are required to provide all QoS monitoring requests and/or measurements requested by the AF. In some embodiments, the PCF determines whether direct reporting is possible or not possible, particularly wherein it is determined by evaluating if QoS Monitoring reports generated according to the determined QoS Monitoring Policy may or may not be suitable for sending to the AF directly by a User Plane Function (UPF). In some embodiments, the method further comprises notifying from the PCF to the AF that direct reporting is possible or not possible. In some embodiments, the method further comprises notifying from the PCF to the AF that direct reporting is not possible if a direct notification indication is included in the request from the AF. In some embodiments, the method further comprises subscribing from the AF to the PCF for measurements of QoS parameters that the PCF derives from QoS Monitoring reports, particularly wherein the QoS Monitoring reports are received at the PCF from a Session Management Function (SMF). In some embodiments, the method further comprising subscribing from the AF to the PCF for measurements of QoS parameters which are derived by the PCF from QoS Monitoring measurements of one or more individual QoS Flows, particularly wherein the QoS Monitoring measurements comprise a round-trip delay for multiple flows. In some embodiments, the method further comprises the PCF deriving the round-trip delay measurement and transmitting the derived round-trip delay measurement to the AF. In some embodiments, the determining of the authorized QoS Monitoring policy at the PCF comprises at least one of: considering all measurements of the QoS parameters included in the request from the AF; and considering QoS Monitoring measurements of QoS parameters and measurements of QoS parameters derived by the PCF from QoS Monitoring measurements on one or more individual flows. In some embodiments, the derived measurements by the PCF include round-trip delay measurements for multiple flows and/or Packet Delay Variation monitoring and reporting and/or difference in delay of more than one flow. In some embodiments, the method further comprises receiving at the PCF from the AF an indication of direct event notification in the request; and determining at the PCF whether to set the indication for direct event notification in the QoS Monitoring Policy based on the suitability of QoS Monitoring reports to be sent to the AF directly by a User Plane Function (UPF). In some embodiments, the PCF transmits to the AF an indication that direct event notification is not possible if the PCF decides not to set the indication for direct event notification. In some embodiments, the authorized QoS Monitoring policy comprises at least one of: one or more QoS parameters to be measured, a reporting frequency, a reporting threshold for each QoS parameter, a minimum waiting time between subsequent reports, a reporting period, a target of reporting, and an indication of direct event notification. In some embodiments, the first network node is an Application Function (AF) or a Network Exposure Function (NEF), and the second network node is a Policy Control Function (PCF) or a Network Exposure Function (NEF).

This disclosure also provides mobile network nodes, particularly a second network node (11 1 , 700) and a first network node (1 13, 600) configured to perform the respective methods as described herein. In some embodiments, the second network node is a Policy Control Function (PCF) 1 11. In some embodiments, the first network node is an Application Function (AF) 1 13. In some embodiments, the first or second network node is a Network Exposure Function (NEF) 109.

This disclosure also provides the corresponding computer program and computer program products comprising code, for example in the form of a computer program, that when run on processing circuitry of the mobile network nodes causes the mobile network nodes to perform the disclosed methods.

The solution and the features comprised therein are further described in what follows.

As to the PCF role in relation to QoS Monitoring, the PCF has QoS Monitoring intelligence and moves away from the simple relay of requests and responses. It can determine the best QoS Monitoring Policy to deliver all types of measurements of QoS requirements in the AF Request, and most suitable reporting path to AF.

The solution comprises, upon AF request for measurements of QoS parameters (QoS Monitoring and/or other measurements):

The PCF has the intelligence to determine the one single authorized QoS Monitoring Policy that can enable QoS Monitoring as needed to satisfy the complete AF request.

The PCF has the intelligence to determine which NFs (PCF, SMF or LIPF) shall send the QoS Monitoring reports to AF

The PCF can indicate AF when requested direct notification (by UPF) cannot be satisfied and still process the request via indirect notification.

The PCF can process the QoS Monitoring reports received from SMF and adapt them to report QoS Monitoring according to the AF request.

Hereinafter, drawings showing examples of embodiments of the solution are described in detail.

The QoS Monitoring control refers to the enabling of real-time measurements of QoS parameters for a service data flow (e.g., for packet delay measurement between the UE and the UPF for a QoS Flow for example for a URLLC service).

QoS Monitoring Control is performed when AF request measurements of QoS parameters as part of “Setting up an AF session with required QoS procedure" (Figure 2) or “AF session with required QoS update procedure” (Figure 3). In stepl of those procedures, AF request may include a subscription to QoS Monitoring or request measurements of QoS parameters determined by PCF. This request is conveyed to PCF in an Npcf PolicyAuthorization Create/Update request.

Figure 2 is a signaling diagram illustrating a procedure for setting up an AF session with required QoS procedure. The procedure is performed by a second network node (111 , 700) and a first network node (113, 600). In some embodiments, the first network node is an Application Function (AF) or a Network Exposure Function (NEF), and the second network node is a Policy Control Function (PCF) or a Network Exposure Function (NEF). More specifically, the procedure involves the following nodes: AF (Application Function) 113, which initiates the process by sending a QoS session creation request to the NEF; NEF (Network Exposure Function) 109, which handles the authorization of the initial request and facilitates the communication between the AF and the other network functions; PCF (Policy Control Function) 111 , which receives policy authorization requests and responds to them, participates in the subscription and notification of QoS information; and TSCTSF (Traffic Steering Control and Traffic Switching Function) 108, which interacts with the PCF for QoS and Traffic Steering Control (TSC) assistance and contributes to requested Packet Delay Budget (PDB) calculations.

In step 1 , the AF sends a request to reserve resources for an AF session using Nnef_AFsessionWithQoS_Create request message (UE address, AF Identifier, Flow description information or External Application Identifier, QoS Reference or individual QoS parameters, Alternative Service Requirements, DNN, S-NSSAI) to the NEF.

In step 2, the NEF assigns a Transaction Reference ID to the Nnef_AFsessionWithQoS_Create request. The NEF authorizes the AF request and may apply policies to control the overall amount of QoS authorized for the AF. If the authorisation is not granted, all steps (except step 5) are skipped and the NEF replies to the AF with a Result value indicating that the authorisation failed.

The NEF determines whether to invoke the TSCTSF or to directly contact the PCF based on operator configuration. This determination may use the presence of a QoS Reference or individual QoS parameters in the AF request. The determination may also use the AF identifier or the presence of AF provided parameters that describe the traffic characteristics.

If the NEF determines not to invoke the TSCTSF, then steps 3, 4, 5, 6, 7, 8 are executed, otherwise, steps 3a, 3b, 4a, 4b, 5, 6a, 7a, 7b, 8 are executed.

In step 3, if the NEF determines to contact the PCF directly without invoking the TSCTSF, the NEF uses the UE address to discover the PCF from the BSF. The NEF forwards received parameters to the PCF in the Npcf_PolicyAuthorization_Create request. Any optionally received period of time or traffic volume mapped and forwarded as sponsored data connectivity information.

If the AF is considered to be trusted by the operator, the AF uses the Npcf_PolicyAuthorization_Create request message to interact directly with PCF to request reserving resources for an AF session.

The PCF receives the AF request (via the NEF). The AF request may include QoS Monitoring measurements requests of QoS parameters and/or measurements requests of QoS parameters that PCF calculates itself from QoS monitoring measurements on individual flows. The following measurements are derived by PCF:

Round-trip delay measurements for multiple flows Packet Delay Variation monitoring and reporting

QoS Monitoring is enabled by PCF by generating the authorized QoS Monitoring policy for the service data flow.

The QoS Monitoring policy includes the following:

- QoS parameters to be measured (e.g. DL packet delay, UL packet delay or round trip packet delay);

- Reporting frequency (event triggered, periodic, or when the PDU Session is released):

- if the reporting frequency is event triggered:

Reporting threshold to each QoS parameter;

Minimum waiting time between reports;

- the reporting period;

- optionally, Target of reporting (i.e. the NEF, the AF or the Local NEF, indicated as Notification Target Address + Notification Correlation ID);

- optionally, an indication of direct event notification (to request the UPF to directly send QoS Monitoring reports to the Local NEF or the AF.

The PCF generates one single Authorized QoS Monitoring Policy for the PCC Rule. To do that, the PCF may take into account all measurements of QoS parameters in the AF request i.e., any QoS Monitoring but also AF requests for other parameters as listed above. As one example, the PCF may decide that even if QoS Monitoring subscription requests reporting frequency on threshold events, the policy will request periodic reporting to be able to calculate other required measurements.

As another example, the PCF may decide subscribe to receive QoS Monitoring reports from SMF by setting the QoS Monitoring Policy Control Request Trigger even if QoS Monitoring subscription request include indication of direct event notification, because reporting frequency has been set in a way consumer will not understand the reports (e.g. change to periodic instead of per threshold events).

In step 3a, if the NEF determines to invoke the TSCTSF, the NEF forwards received parameters in the Ntsctsf_QoSandTSCAssistance_Create request message to the TSCTSF. Any optionally received period of time or traffic volume is mapped and forwarded as sponsored data connectivity information.

If the AF is considered to be trusted by the operator, the AF uses the Ntsctsf_QoSandTSCAssistance_Create request message to interact directly with TSCTSF to request reserving resources for an AF session.

A TSCTSF address may be locally configured (a single TSCTSF per DNN/S-NSSAI) in the NEF, PCF and trusted AF. Alternatively, the NEF uses the AF Identifier to determine the DNN/S-NSSAI and uses the DNN/S-NSSAI to discover the TSCTSF from the NRF.

In step 3b, the TSCTSF determines whether it has an AF session with a PCF for the given UE address. In this case the TSCTSF sends a Npcf_PolicyAuthorization_Update request message to the PCF and forwards the received parameters after executing the adjustment and mapping actions described below.

If the TSCTSF does not have an AF-session for a given UE address, the TSCTSF discovers the PCF and a Npcf_PolicyAuthorization_Create request message to the PCF.

If the TSCTSF receives a Requested 5GS Delay, the TSCTSF calculates a Requested PDB by subtracting the UE-DS-TT Residence Time (either provided by the PCF or pre-configured at TSCTSF) from the Requested 5GS Delay and sends the Requested PDB to the PCF instead of the Requested 5GS Delay. If the TSCTSF receives any of the following parameters: flow direction, Burst Arrival Time, Periodicity, Time domain, Survival Time from the NEF, the TSCTSF determines the TSC Assistance Container and sends it to the PCF instead of these parameters. In step 4, for requests received from the NEF in step 3, the PCF determines whether the request is authorized and notifies the NEF if the request is not authorized.

If the request is authorized, the PCF derives the required QoS parameters of the PCC rule based on the information provided by the NEF and determines whether this QoS is allowed (according to the PCF configuration) and notifies the result to the NEF. If the AF is considered to be trusted by the operator, the PCF sends the Npcf_PolicyAuthorization_Create response message directly to AF.

If the PCF receives the individual QoS parameters instead of QoS Reference, the PCF determines a 5QI that matches the individual QoS parameters. It also sets the GBR and MBR for the PCC rule according to the requested values. The PCF may use the Requested Priority from the AF to determine Priority Level. Requested individual QoS parameter values supersede default values for the 5QI.

In addition, if the Alternative Service Requirements are provided, the PCF derives the Alternative QoS parameter set(s) in the same way from the one or more QoS Reference parameters or the Requested Alternative QoS Parameter Set(s) contained in the Alternative Service Requirements keeping the same prioritized order.

The PCF derived Alternative QoS parameter set(s) for the PCC rule are subsequently used to establish Alternative QoS Profile(s).

If the PCF determines that the SMF needs updated policy information, the PCF issues a Npcf_SMPolicyControl_UpdateNotify request with updated policy information about the PDll Session as described in the PCF initiated SM Policy Association Modification procedure.

In the response to the AF request (Npcf PolicyAuthorization Create/Update response), the PCF may indicate that direct event notification is not possible when that has been requested by AF based on PCF selected notification path).

When PCF generates the QoS Monitoring Policy it determines the reporting path:

If the AF did not provide an indication of direct event notification in the request, PCF may forward the Target of reporting parameter in the QoS Monitoring policy and instruct SMF to send directly the QoS Monitoring reports to target entity. The PCF takes into account whether the QoS Monitoring reports shall be used by PCF itself to produce new measurements and/or whether they need to be processed to be understood by AF. If so, PCF instructs SMF to report to PCF

If the AF provided an indication of direct event notification in the request, the PCF may instruct the SMF so that notifications are not sent directly by UPF when the QoS Monitoring Reports need to be processed to be understood by AF (i.e. else, AF will not understand them)

If the AF provided an indication of direct event notification in the request, PCF can instruct SMF so that notifications are sent directly by UPF to AF, but PCF takes also into account whether the QoS Monitoring reports shall be used to produce new measurements according to AF request, and if so, PCF instructs SMF request duplicated reporting.

In general, Reporting by PCF of QoS Monitoring reports or other measurements determined by PCF is performed in PCF according to AF subscription and previous decisions on selected reporting path. When the PCF receives QoS Monitoring reports from the SMF (Npcf_SMPolicyControl_Update request), PCF calculates any measurements that need be calculated by PCF and reports as requested by AF by means of (Npcf PolicyAuthorization Notify request) according to AF subscription. If AF request included a subscription on QoS Monitoring, PCF processes the received QoS Monitoring report, if needed, before it is reported (in Npcf PolicyAuthorization Notify request) according to the AF subscription. This step is not needed if direct reporting by UPF applies as decided by the PCF.

In step 4a, for requests received from the TSCTSF in step 3b, the PCF determines whether the request is authorized and notifies the TSCTSF if the request is not authorized.

If the request is authorized, the PCF derives the required QoS parameters of the PCC rule in the same way it is described in step 4 based on the information provided by the TSCTSF and determines whether this QoS is allowed (according to the PCF configuration) and notifies the result to the TSCTSF.

If the PCF determines that the SMF needs updated policy information, the PCF issues a Npcf_SMPolicyControl_UpdateNotify request with updated policy information about the PDU Session as described in the PCF initiated SM Policy Association Modification procedure.

If the PCF receives a subscription for the 5GS Bridge information from the TSCTSF, if the PCF does not have the 5GS Bridge information for the PDU Session, the PCF uses the PCF initiated SM Policy Association Modification procedure to subscribe for 5GS Bridge information event from the SMF. Once the PCF has the 5GS Bridge information, the PCF notifies the TSCTSF for the 5GS Bridge information (including the UE-DS-TT Residence Time).

The functionality described in step 4 may also apply to step 4a.

In step 4b, the TSCTSF sends a Ntsctsf_QoSandTSCAssistance_Create response message (Transaction Reference ID, Result) to the NEF. Result indicates whether the request is granted or not.

If the AF is considered to be trusted by the operator, the TSCTSF sends the Ntsctsf_QoSandTSCAssistance_Create response message directly to AF.

In step 5, the NEF sends a Nnef_AFsessionWithQoS_Create response message (Transaction Reference ID, Result) to the AF. Result indicates whether the request is granted or not.

In step 6, the NEF shall send a Npcf_PolicyAuthorization_Subscribe message to the PCF to subscribe to notifications of Resource allocation status and may subscribe to other events.

The functionality described in step 3 may also apply to step 6.

In step 6a, the TSCTSF shall send a Npcf_PolicyAuthorization_Subscribe message to the PCF to subscribe to notifications of Resource allocation status and may subscribe to other events.

The functionality described in step 3 may also apply to step 6a.

In step 7, when the event condition is met, e.g. that the establishment of the transmission resources corresponding to the QoS update succeeded or failed, the PCF sends Npcf_PolicyAuthorization_Notify message to the NEF notifying about the event.

If the AF is considered to be trusted by the operator, the PCF sends the Npcf_PolicyAuthorization_Notify message directly to AF.

In step 7a, when the event condition is met, e.g. that the establishment of the transmission resources corresponding to the QoS update succeeded or failed, the PCF sends Npcf_PolicyAuthorization_Notify message to the TSCTSF notifying about the event. In step 7b, the TSCTSF sends Ntsctsf_QoSandTSCAssistance_Notify message with the event reported by the PCF to the NEF.

If the AF is considered to be trusted by the operator, the TSCTSF sends the Ntsctsf_QoSandTSCAssistance_Notify message directly to AF.

In step 8, the NEF sends Nnef_AFsessionWithQoS_Notify message with the event reported by the PCF to the AF.

Figure 3 is a signaling diagram illustrating an alternative procedure for setting up an AF session with required QoS update procedure. The procedure is performed by a second network node (111 , 700), and a first network node (113, 600). In some embodiments, the first network node is an Application Function (AF) or a Network Exposure Function (NEF), and the second network node is a Policy Control Function (PCF) or a Network Exposure Function (NEF). More specifically, the procedure involves the following nodes: AF (Application Function) 113, NEF (Network Exposure Function) 109, PCF (Policy Control Function) 111 , and TSCTSF (T raffic Steering Control and T raffic Switching Function) 108.

The description of the steps in Figure 2 applies mutatis mutandis to the steps in Figure 3. See the detailed description in Figure 2 for the information carried by the messages of Figure 3.

The steps of Figure 3 are outlined in the following:

In step 1 , the AF transmits to the NEF an Nnef_AfsessionWithQoS_Update request.

In step 2, the NEF performs Authorization.

In step 3, the NEF transmits to the PCF an Npcf_PolicyAuthorization_Update request.

In step 3a, the NEF transmits to the TSCTSF an Ntsctsf_QoSandTSC_Assistance_Update request. Then, the TSCTSF performs a Requested PDB calculation.

In step 3b, the TSCTSF transmits to the PCF an Npcf_PolicyAuthorization_Update request.

In step 4, the PCF transmits to the NEF an Npcf_PolicyAuthorization_Update response. In step 4a, the PCF transmits to the TSCTSF an Npcf_PolicyAuthorization_Update response. In step 4b, the TSCTSF transmits to the NEF an Ntsctsf_QoSandTSC_Assistance_Update response.

In step 5, the NEF transmits to the AF an Nnef_AfsessionWithQoS_Update response. In step 6, the PCF transmits to the NEF an Npcf_PolicyAuthorization_Notify message. In step 6a, the PCF transmits to the TSCTSF an Npcf_PolicyAuthorization_Notify message. In step 6b, the TSCTSF transmits to the NEF an Ntsctsf_QoSandTSC_Assistance_notify.

In step 7, the NEF transmits to the AF an Nnef_AfsessionWithQoS_Notify message.

The QoS Monitoring control refers to the enabling of real-time measurements of QoS parameters for a service data flow (e.g., for packet delay measurement between the UE and the UPF for a QoS Flow corresponding to an URLLC service).

The AF request may include QoS Monitoring meaurements of QoS parameters and/or measurements of QoS parameters that PCF calculates itself from QoS monitoring measurements on individual flows. Following measurements are derived by PCF:

Round-trip delay measurements for multiple flows.

Packet Delay Variation monitoring and reporting.

The PCF generates the authorized QoS Monitoring policy for the service data flow taking into account all measurements of QoS parameters included in the AF request, i.e., based on the QoS Monitoring request if received from the AF and AF subscription requests for other measurements as listed above.

The QoS Monitoring policy includes the following:

QoS parameters to be measured (e.g. DL packet delay, UL packet delay or round trip packet delay);

Reporting frequency (event triggered, periodic, or when the PDU Session is released): if the reporting frequency is event triggered: the corresponding reporting threshold to each QoS parameter; minimum waiting time between subsequent reports; the reporting period; optionally, Target of reporting (i.e. the NEF, the AF or the Local NEF, indicated as Notification Target Address + Notification Correlation ID); optionally, an indication of direct event notification (to request the UPF to directly send QoS Monitoring reports to the Local NEF or the AF).

If the AF did not provide an indication of direct event notification in the request, PCF may decide that it does not want to receive the QoS Monitoring reports. If so, the PCF forwards the Target of reporting parameter in the QoS Monitoring policy and the SMF shall then send the QoS Monitoring reports directly to the NF indicated by the Target of reporting parameter. If the PCF decides that it wants to receive the QoS Monitoring reports, e.g. when the AF request includes measurements that are derived by PCF, the PCF shall not forward the Target of reporting parameter in the QoS Monitoring policy and instead subscribe to receive QoS Monitoring reports from SMF by setting the QoS Monitoring Policy Control Request Trigger.

If the AF provided an indication of direct event notification in the request and PCF determines that the QoS Monitoring reports can be notified directly, the PCF forwards the Target of reporting parameter in the QoS Monitoring policy and sets the indication of direct event notification to indicate that QoS Monitoring reports have to be sent by the UPF directly to the NF indicated by the Target of reporting. The PCF may also subscribe to receive QoS Monitoring reports e.g. the AF request includes measurements that are derived by PCF) by setting the QoS Monitoring Policy Control Request Trigger. In that case, the UPF is asked to duplicate the reports and the QoS Monitoring reports will be sent by the UPF to both, the NF indicated by the Target of reporting and to the SMF (which then forwards the report to the PCF).

If the AF provided an indication of direct event notification but PCF generates a QoS Monitoring Policy and decides not to set indication for direct event notification, the PCF generates a successful response to AF and indicates that direct event notification is not possible.

If there are multiple QoS rules containing a QoS monitoring policy, the PCF will receive the QoS Monitoring reports for all of them when the QoS Monitoring Policy Control Request Trigger is set.

The PCF includes the authorized QoS Monitoring policy in the PCC rule and provides it to the SMF. The SMF determines based on the QoS Monitoring policy in the PCC rule what it needs to indicate the RAN and the UPF to perform the measurement of the QoS parameters. Hereinafter, flowcharts showing examples of embodiments of the solution are described in detail.

The embodiments correspond to methods performed by and involving a second network node (111 , 700), and a first network node (113, 600). In some embodiments, the second network node is a Policy Control Function (PCF) 111. In some embodiments, the first network node is an Application Function (AF) 113. In some embodiments, the first or second network node is a Network Exposure Function (NEF) 109.

Figure 4 is a flowchart illustrating a method performed by the first network node for Quality of Service monitoring control in a communications network.

In step S-401 , the first network node transmits to a second network node one or more requests for measurements of QoS parameters associated with a PCC Rule.

In step S-402, the first network node receives from the second network node the measurements of QoS parameters requested by AF based on the QoS Monitoring reports.

In step S-403, the first network node receives from the second network node a response indicating whether direct notification is possible or not possible.

In step S-404, the first network node receives from the second network node a round-trip delay for multiple flows event, particularly wherein the event indicates a report of round-trip delay measurements when uplink (LIL) and downlink (DL) traffic are separated into two flows and/or wherein the event is derived from measurements of packet delay between a User Equipment (UE) and a User Plane Function (UPF) .

In step S-405, the first network node receives from the second network node one or more measurements of QoS parameters determined at the PCF.

In some embodiments, the PCF determines the QoS Monitoring Policy considering which QoS Monitoring measurements of QoS parameters are required to provide all QoS monitoring requests and/or measurements requested by the AF.

In some embodiments, the PCF determines whether direct reporting is possible or not possible, particularly wherein it is determined by evaluating if QoS Monitoring reports generated according to the determined QoS Monitoring Policy may or may not be suitable for sending to the AF directly by a User Plane Function (UPF). In some embodiments, the method further comprises notifying from the PCF to the AF that direct reporting is possible or not possible.

In some embodiments, the method further comprises notifying from the PCF to the AF that direct reporting is not possible if a direct notification indication is included in the request from the AF.

In some embodiments, the method further comprises subscribing from the AF to the PCF for measurements of QoS parameters that the PCF derives from QoS Monitoring reports, particularly wherein the QoS Monitoring reports are received at the PCF from a Session Management Function (SMF).

In some embodiments, the method further comprising subscribing from the AF to the PCF for measurements of QoS parameters which are derived by the PCF from QoS Monitoring measurements of one or more individual QoS Flows, particularly wherein the QoS Monitoring measurements comprise a round-trip delay for multiple flows.

In some embodiments, the method further comprises the PCF deriving the round-trip delay measurement and transmitting the derived round-trip delay measurement to the AF.

In some embodiments, the determining of the authorized QoS Monitoring policy at the PCF comprises at least one of: considering all measurements of the QoS parameters included in the request from the AF; and considering QoS Monitoring measurements of QoS parameters and measurements of QoS parameters derived by the PCF from QoS Monitoring measurements on one or more individual flows.

In some embodiments, the derived measurements by the PCF include round-trip delay measurements for multiple flows and/or Packet Delay Variation monitoring and reporting and/or difference in delay of more than one flow.

In some embodiments, the method further comprises receiving at the PCF from the AF an indication of direct event notification in the request; and determining at the PCF whether to set the indication for direct event notification in the QoS Monitoring Policy based on the suitability of QoS Monitoring reports to be sent to the AF directly by a User Plane Function (UPF).

In some embodiments, the PCF transmits to the AF an indication that direct event notification is not possible if the PCF decides not to set the indication for direct event notification. - T1 -

In some embodiments, the authorized QoS Monitoring policy comprises at least one of: one or more QoS parameters to be measured, a reporting frequency, a reporting threshold for each QoS parameter, a minimum waiting time between subsequent reports, a reporting period, a target of reporting, and an indication of direct event notification.

In some embodiments, the first network node is an Application Function (AF) or a Network Exposure Function (NEF), and the second network node is a Policy Control Function (PCF) or a Network Exposure Function (NEF).

Figure 5 is a flowchart illustrating a method performed by the second network node for Quality of Service monitoring control in a communications network.

In step S-501 , the second network node receives from a first network node one or more requests for measurements of QoS parameters associated with a PCC Rule.

In step S-502, the second network node determines a single authorized QoS Monitoring Policy for the 5G Core Network (5GC) to produce measurements of QoS parameters.

In step S-503, the second network node determines one or more measurements of QoS parameters from one or more QoS Monitoring reports, particularly wherein the QoS Monitoring reports are of one or more individual QoS Flows.

In step S-504, the second network node receives one or more QoS Monitoring reports.

In step S-505, the second network node transmits to the first network node the measurements of QoS parameters requested by AF based on the QoS Monitoring reports.

In step S-506, the second network node determines whether direct notification path is possible or not possible based on the determined QoS Monitoring Policy and its relation to the original AF request, particularly wherein the relation pertains to the PCF understanding of the QoS Monitoring results, and/or the measurement of QoS parameters at the PCF match the measurement of QoS parameters requested by the AF.

In step S-507, the second network node transmits to the first network node a response indicating whether direct notification is possible or not possible.

In step S-508, the second network node transmits to the first network node a round-trip delay for multiple flows event, particularly wherein the event indicates a report of round-trip delay measurements when uplink (LIL) and downlink (DL) traffic are separated into two flows and/or wherein the event is derived from measurements of packet delay between a User Equipment (UE) and a User Plane Function (UPF) .

In step S-509, the second network node transmits to the first network node the one or more measurements of QoS parameters.

In some embodiments, the PCF determines whether direct reporting is possible or not possible, particularly wherein it is determined by evaluating if QoS Monitoring reports generated according to the determined QoS Monitoring Policy may or may not be suitable for sending to the AF directly by a User Plane Function (UPF).

In some embodiments, the method further comprises notifying from the PCF to the AF that direct reporting is possible or not possible.

In some embodiments, the PCF transmits to the AF an indication that direct event notification is not possible if the PCF decides not to set the indication for direct event notification.

Figure 6 is a block diagram illustrating elements of a mobile network node 600 of a mobile communications network. In some embodiments, the mobile network node 600 is an AF 1 13. As shown, the mobile network node may include network interface circuitry 601 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the network. The mobile network node may also include a processing circuitry 602 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 603 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 603 may include computer readable program code that when executed by the processing circuitry 602 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 602 may be defined to include memory so that a separate memory circuitry is not required. As discussed herein, operations of the mobile network node may be performed by processing circuitry 602 and/or network interface circuitry 601 . For example, processing circuitry 602 may control network interface circuitry 601 to transmit communications through network interface circuitry 601 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 603, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 602, processing circuitry 602 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).

Figure 7 is a block diagram illustrating elements of a mobile network node 700 of a mobile communications network. In some embodiments, the mobile network node 700 is a PCF 111 . As shown, the mobile network node may include network interface circuitry 701 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the network. The mobile network node may also include a processing circuitry 702 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 703 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 703 may include computer readable program code that when executed by the processing circuitry 702 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 702 may be defined to include memory so that a separate memory circuitry is not required. As discussed herein, operations of the mobile network node may be performed by processing circuitry 702 and/or network interface circuitry 701 . For example, processing circuitry 702 may control network interface circuitry 701 to transmit communications through network interface circuitry 701 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 703, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 702, processing circuitry 702 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).

Figure 8 is a block diagram illustrating a virtualization environment 800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 800 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

Applications 802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware 804 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 808a and 808b (one or more of which may be generally referred to as VMs 808), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to the VMs 808.

The VMs 808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 806. Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of VMs 808, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, a VM 808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 808, and that part of hardware 804 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 808 on top of the hardware 804 and corresponds to the application 802.

Hardware 804 may be implemented in a standalone network node with generic or specific components. Hardware 804 may implement some functions via virtualization. Alternatively, hardware 804 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 810, which, among others, oversees lifecycle management of applications 802. In some embodiments, hardware 804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 812 which may alternatively be used for communication between hardware nodes and radio units.

Embodiments within the scope of the present invention may also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such tangible computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or combination thereof) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such connection is properly termed a computer- readable medium. Combinations of the above should also be included within the scope of the tangible computer-readable media. Computer-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Computer-executable instructions also include program modules that are executed by computers in standalone or network environments. Generally, program modules include routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Computer executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.

Those of skill in the art will appreciate that other embodiments of the invention may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Embodiments may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination thereof) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

Communication at various stages of the described system can be performed through a local area network, a token ring network, the Internet, a corporate intranet, 802.11 series wireless signals, fiber-optic network, radio or microwave transmission, etc. Although the underlying communication technology may change, the fundamental principles described herein are still applicable.

The various embodiments described above are provided by way of illustration only and should not be construed to limit the invention. For example, the principles herein may be applied to any remotely controlled device. Further, those of skill in the art will recognize that communication between the remote the remotely controlled device need not be limited to communication over a local area network but can include communication over infrared channels, Bluetooth or any other suitable communication interface. Those skilled in the art will readily recognize various modifications and changes that may be made to the present invention without following the example embodiments and applications illustrated and described herein, and without departing from the scope of the present disclosure.

The terminology used herein is for the purpose of describing various embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "includes," "including," "comprises," and "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, or components, and combinations thereof, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, or components, and combinations thereof. Further, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to ""a/an/the element, apparatus, component, means, module, step, etc."" are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, module, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.

Claims

1 . A method for Quality of Service monitoring control in a communications network, the method comprising: receiving (S-501) at a second network node (700) from a first network node (600) a request for measurements of QoS parameters; determining (S-502) at the second network node an authorized QoS monitoring policy for measurement of QoS parameters, particularly wherein the authorized QoS monitoring policy is a single authorized QoS monitoring policy; and transmitting (S-509) from the second network node to the first network node one or more measurements of QoS parameters based on one or more QoS Monitoring reports, particularly wherein the QoS Monitoring reports are of one or more individual QoS Flows.

2. The method of claim 1 , further comprising: receiving at the second network node one or more QoS Monitoring reports.

3. The method of any one of claims from claim 1 to claim 2, further comprising: transmitting from the second network node to the first network node the measurements of QoS parameters requested by the first network node based on the QoS Monitoring reports.

4. The method of any one of claims from claim 1 to claim 3, further comprising: determining at the second network node whether direct notification is possible or not possible based on the QoS Monitoring Policy and/or the first network node request, particularly based on whether the measurement of QoS parameters at the second network node match the measurement of QoS parameters requested by the first network node.

5. The method of any one of claims from claim 1 to claim 4, further comprising: transmitting from the second network node to the first network node a round-trip delay for multiple flows event, particularly wherein the event indicates a report of round-trip delay measurements when uplink, LIL, and downlink, DL, traffic are separated into two flows and/or wherein the event is derived from measurements of packet delay between a User Equipment, UE, and a User Plane Function, UPF.

6. The method of any one of claims from claim 1 to claim 5, wherein the second network node determines the QoS Monitoring Policy considering which QoS Monitoring measurements of QoS parameters are required to provide all QoS monitoring requests and/or measurements requested by the first network node.

7. The method of any one of claims from claim 1 to claim 6, wherein the second network node determines whether direct reporting is possible or not possible, particularly wherein it is determined by evaluating if QoS Monitoring reports generated according to the QoS Monitoring Policy may or may not be suitable for sending to the first network node directly by a User Plane Function, UPF.

8. The method of any one of claims from claim 1 to claim 7, wherein the method further comprises transmitting from the second network node to the first network node an indication that direct reporting is possible or not possible.

9. The method of any one of claims from claim 1 to claim 8, wherein the method further comprises transmitting from the second network node to the first network node an indication that direct reporting is not possible if a direct notification indication is included in the request from the first network node.

10. The method of any one of claims from claim 1 to claim 9, wherein the method further comprises subscribing from the first network node to the second network node for measurements of QoS parameters that the second network node derives from QoS Monitoring reports, particularly wherein the QoS Monitoring reports are received at the second network node from a Session Management Function, SMF.

11 . The method of any one of claims from claim 1 to claim 10, wherein the method further comprising subscribing from the first network node to the second network node for measurements of QoS parameters which are derived by the second network node from QoS Monitoring measurements of one or more individual QoS Flows, particularly wherein the QoS Monitoring measurements comprise a round-trip delay for multiple flows.

12. The method of any one of claims from claim 1 to claim 11 , wherein the method further comprises deriving at the second network node the round-trip delay measurement and transmitting the derived round-trip delay measurement to the first network node.

13. The method of any one of claims from claim 1 to claim 12, wherein the determining of the authorized QoS Monitoring policy at the second network node comprises at least one of: considering all measurements of the QoS parameters included in the request from the first network node; and considering QoS Monitoring measurements of QoS parameters and measurements of QoS parameters derived by the second network node from QoS Monitoring measurements on one or more individual flows.

14. The method of any one of claims from claim 1 to claim 13, wherein the derived measurements by the second network node include round-trip delay measurements for multiple flows and/or Packet Delay Variation monitoring and reporting and/or difference in delay of more than one flow.

15. The method of any one of claims from claim 1 to claim 14, wherein the method further comprises receiving at the second network node from the first network node an indication of direct event notification; and determining at the second network node whether to set the indication for direct event notification in the QoS Monitoring Policy based on the suitability of QoS Monitoring reports to be sent to the first network node directly by a User Plane Function, UPF.

16. The method of any one of claims from claim 1 to claim 15, wherein the second network node transmits to the first network node an indication that direct event notification is not possible if the second network node decides not to set the indication for direct event notification.

17. The method of any one of claims from claim 1 to claim 16, wherein the authorized QoS Monitoring policy comprises at least one of: one or more QoS parameters to be measured, a reporting frequency, a reporting threshold for each QoS parameter, a minimum waiting time between subsequent reports, a reporting period, a target of reporting, and an indication of direct event notification.

18. The method of any one of claims from claim 1 to claim 17, wherein the first network node is an Application Function, AF, and the second network node is a Policy Control Function, PCF.

19. A method performed by a first network node (600) for Quality of Service monitoring control in a communications network, the method comprising: transmitting (S-401 ) from the first network node to a second network node (700) a request for measurements of QoS parameters; and receiving (S-405) at the first network node from the second network node one or more measurements of QoS parameters determined at the second network node.

20. The method of claim 19, further comprising: receiving at the first network node from the second network node the measurements of QoS parameters requested by the first network node based on QoS Monitoring reports.

21 . The method of any one of claims from claim 19 to claim 20, further comprising: receiving at the first network node from the second network node an indication of whether direct notification is possible or not possible.

22. The method of any one of claims from claim 19 to claim 21 , further comprising: receiving at the first network node from the second network node a round-trip delay for multiple flows event, particularly wherein the event indicates a report of round-trip delay measurements when uplink, LIL, and downlink, DL, traffic are separated into two flows and/or wherein the event is derived from measurements of packet delay between a User Equipment, UE, and a User Plane Function, UPF.

23. The method of any one of claims from claim 19 to claim 22, wherein the one or more measurements of QoS parameters are based on a QoS Monitoring Policy considering which QoS Monitoring measurements of QoS parameters are required to provide all QoS monitoring requests and/or measurements requested by the first network node.

24. The method of any one of claims from claim 19 to claim 23, further comprising determining whether direct reporting is possible or not possible, particularly wherein it is determined by evaluating if QoS Monitoring reports generated according to the determined QoS Monitoring Policy may or may not be suitable for sending to the first network node directly by a User Plane Function, UPF.

25. The method of any one of claims from claim 19 to claim 24, wherein the method further comprises receiving from the second network node at the first network node an indication that direct reporting is possible or not possible.

26. The method of any one of claims from claim 19 to claim 25, wherein the method further comprises receiving from the second network node at the first network node an indication that direct reporting is not possible if a direct notification indication is included in the request from the first network node.

21. The method of any one of claims from claim 19 to claim 26, wherein the method further comprises subscribing from the first network node to the second network node for measurements of QoS parameters that the second network node derives from QoS Monitoring reports, particularly wherein the QoS Monitoring reports are received at the second network node from a Session Management Function, SMF.

28. The method of any one of claims from claim 19 to claim 27, wherein the method further comprising subscribing from the first network node to the second network node for measurements of QoS parameters which are derived by the second network node from QoS Monitoring measurements of one or more individual QoS Flows, particularly wherein the QoS Monitoring measurements comprise a round-trip delay for multiple flows.

29. The method of any one of claims from claim 19 to claim 28, wherein the method further comprises receiving a round-trip delay measurement determined at the second network node.

30. The method of any one of claims from claim 19 to claim 29, wherein the QoS Monitoring policy is based on at least one of: considering all measurements of the QoS parameters included in the request from the first network node; and considering QoS Monitoring measurements of QoS parameters and measurements of QoS parameters derived by the second network node from QoS Monitoring measurements on one or more individual flows.

31 . The method of any one of claims from claim 19 to claim 30, wherein the measurements received from the second network node include round-trip delay measurements for multiple flows and/or Packet Delay Variation monitoring and reporting and/or difference in delay of more than one flow.

32. The method of any one of claims from claim 19 to claim 31 , wherein the method further comprises transmitting to the second network node from the first network node an indication of direct event notification.

33. The method of any one of claims from claim 19 to claim 32, further comprising receiving from the second network node to the first network node an indication that direct event notification is not possible if the second network node decides not to set the indication for direct event notification.

34. The method of any one of claims from claim 19 to claim 33, wherein the QoS Monitoring policy comprises at least one of: one or more QoS parameters to be measured, a reporting frequency, a reporting threshold for each QoS parameter, a minimum waiting time between subsequent reports, a reporting period, a target of reporting, and an indication of direct event notification.

35. The method of any one of claims from claim 19 to claim 34, wherein the first network node is an Application Function, AF, and the second network node is a Policy Control Function, PCF.

36. A method performed by a second network node (700) for Quality of Service monitoring control in a communications network, the method comprising: receiving (S-501) at the second network node from a first network node (600) a request for measurements of QoS parameters; determining (S-502) at the second network node an authorized QoS Monitoring Policy for measurement of QoS parameters, particularly wherein the authorized QoS monitoring policy is a single authorized QoS monitoring policy; transmitting (S-509) from the second network node to the first network node one or more measurements of QoS parameters based on one or more QoS Monitoring reports, particularly wherein the QoS Monitoring reports are of one or more individual QoS Flows.

37. The method of claim 36, further comprising: receiving at the second network node one or more QoS Monitoring reports.

38. The method of any one of claims from claim 36 to claim 37, further comprising: transmitting from the second network node to the first network node the measurements of QoS parameters requested by the first network node based on the QoS Monitoring reports.

39. The method of any one of claims from claim 36 to claim 38, further comprising: determining at the second network node whether direct notification is possible or not possible based on the QoS Monitoring Policy and/or the first network node request, particularly based on whether the measurement of QoS parameters at the second network node match the measurement of QoS parameters requested by the first network node.

40. The method of any one of claims from claim 36 to claim 39, further comprising: transmitting from the second network node to the first network node a round-trip delay for multiple flows event, particularly wherein the event indicates a report of round-trip delay measurements when uplink, LIL, and downlink, DL, traffic are separated into two flows and/or wherein the event is derived from measurements of packet delay between a User Equipment, UE, and a User Plane Function, UPF.

41 . The method of any one of claims from claim 36 to claim 40, wherein the second network node determines the QoS Monitoring Policy considering which QoS Monitoring measurements of QoS parameters are required to provide all QoS monitoring requests and/or measurements requested by the first network node.

42. The method of any one of claims from claim 36 to claim 41 , wherein the second network node determines whether direct reporting is possible or not possible, particularly wherein it is determined by evaluating if QoS Monitoring reports generated according to the determined QoS Monitoring Policy may or may not be suitable for sending to the first network node directly by a User Plane Function, UPF.

43. The method of any one of claims from claim 36 to claim 42, wherein the method further comprises transmitting from the second network node to the first network node an indication that direct reporting is possible or not possible.

44. The method of any one of claims from claim 36 to claim 43, wherein the method further comprises transmitting from the second network node to the first network node an indication that direct reporting is not possible if a direct notification indication is included in the request from the first network node.

45. The method of any one of claims from claim 36 to claim 44, wherein the method further comprises subscribing from the first network node at the second network node for measurements of QoS parameters that the second network node derives from QoS Monitoring reports, particularly wherein the QoS Monitoring reports are received at the second network node from a Session Management Function, SMF.

46. The method of any one of claims from claim 36 to claim 45, wherein the method further comprising subscribing from the first network node at the second network node for measurements of QoS parameters which are derived by the second network node from QoS Monitoring measurements of one or more individual QoS Flows, particularly wherein the QoS Monitoring measurements comprise a round-trip delay for multiple flows.

47. The method of any one of claims from claim 36 to claim 46, wherein the method further comprises deriving at the second network node the round-trip delay measurement and transmitting the derived round-trip delay measurement to the first network node.

48. The method of any one of claims from claim 36 to claim 47, wherein the determining of the authorized QoS Monitoring policy at the second network node comprises at least one of: considering all measurements of the QoS parameters included in the request from the first network node; and considering QoS Monitoring measurements of QoS parameters and measurements of QoS parameters derived by the second network node from QoS Monitoring measurements on one or more individual flows.

49. The method of any one of claims from claim 36 to claim 48, wherein the derived measurements by the second network node include round-trip delay measurements for multiple flows and/or Packet Delay Variation monitoring and reporting and/or difference in delay of more than one flow.

50. The method of any one of claims from claim 36 to claim 49, wherein the method further comprises receiving at the second network node from the first network node an indication of direct event notification in the request; and determining at the second network node whether to set the indication for direct event notification in the QoS Monitoring Policy based on the suitability of QoS Monitoring reports to be sent to the first network node directly by a User Plane Function, UPF.

51 . The method of any one of claims from claim 36 to claim 50, wherein the second network node transmits to the first network node an indication that direct event notification is not possible if the second network node decides not to set the indication for direct event notification.

52. The method of any one of claims from claim 36 to claim 51 , wherein the authorized QoS Monitoring policy comprises at least one of: one or more QoS parameters to be measured, a reporting frequency, a reporting threshold for each QoS parameter, a minimum waiting time between subsequent reports, a reporting period, a target of reporting, and an indication of direct event notification.

53. The method of any one of claims from claim 36 to claim 52, wherein the first network node is an Application Function, AF, and the second network node is a Policy Control Function, PCF.

54. Apparatus for Quality of Service monitoring control in a communications network, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to perform the method of any one of claims from claim 19 to claim 35.

55. Apparatus for Quality of Service monitoring control in a communications network, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to perform the method of any one of claims from claim 36 to claim 53.

56. A system comprising an apparatus as claimed in claim 54, and an apparatus as claimed in claim 55.

57. A computer-implemented system comprising one or more processors and one or more computer storage media storing computer-usable instructions that, when used by the one or more processors, cause the one or more processors to perform a method according to any one of claims from claim 19 to claim 53.

58. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to perform a method according to any of claims from claim 19 to claim 53.

59. A computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by a processor, causing the processor to perform the method according to any of claims from claim 19 to claim 53.