NWDAF-based QoS service experience and QoS flow level analytics

Abstract

There is provided a policy control function (PCF) entity configured to: request or subscribe to analytics relating to quality of service (QoS) from an network data analytics function (NWDAF) entity; a

Description

BACKGROUND Field Certain examples of the present disclosure provide one or more techniques for NWDAF-based QoS service experience and QoS flow level analytics, for example in a 3rd Generation Partnership Project (3GPP) 5th Generation (5G) New Radio (NR) network. Description of the Related Art Various acronyms, abbreviations and definitions used in the present disclosure are defined at the end of this description. Overview of QoS and PCC rules As defined in TS 23.501, the QoS parameters of 5GS include: 5QI: 5G QoS Identifier ARP: priority level, the pre-emption capability and the pre-emption vulnerability. RQA: The Reflective QoS Attribute (RQA) is an optional parameter which indicates that certain traffic (not necessarily all) carried on this QoS Flow is subject to Reflective QoS QoS Parameter Notification control: indicates whether notifications are requested from the NG-RAN when the "GFBR can no longer (or can again) be guaranteed" for a QoS Flow during the lifetime of the QoS Flow. Notification control may be used for a GBR QoS Flow if the application traffic is able to adapt to the change in the QoS (e.g. if the AF is capable to trigger rate adaptation). Flow Bit Rates o Guaranteed Flow Bit Rate (GFBR) - UL and DL; o Maximum Flow Bit Rate (MFBR) -- UL and DL. Aggregate Bit Rates: o per Session Aggregate Maximum Bit Rate (Session-AMBR): The Session-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS Flows for a specific PDU Session o per UE Aggregate Maximum Bit Rate (UE-AMBR): aggregate bit rate that can be expected to be provided across all Non-GBR QoS Flows of a UE o per UE per Slice-Maximum Bit Rate (UE-Slice-MBR): aggregate bit rate that can be expected to be provided across all GBR and Non-GBR QoS Flows corresponding to PDU Sessions of the UE for the same slice (S-NSSAI) which have an active user plane. Default values: For each PDU Session Setup, the SMF retrieves the subscribed Session-AMBR values as well as the subscribed default values for the 5QI and the ARP and optionally, the 5QI Priority Level, from the UDM. The subscribed default 5QI value shall be a Non-GBR 5QI from the standardized value range. Maximum Packet Loss Rate: maximum rate for lost packets of the QoS Flow that can be tolerated in the uplink and downlink direction. This is provided to the QoS Flow if it is compliant to the GFBR Within the 5GS, a QoS Flow associated with the default QoS rule is required to be established for a PDU Session and remains established throughout the lifetime of the PDU Session. This QoS Flow should be a Non-GBR QoS Flow. For QoS rules, as defined in TS 23.501: The UE performs the classification and marking of UL User plane traffic, i.e. the association of UL traffic to QoS Flows, based on QoS rules. These QoS rules may be explicitly provided to the UE (i.e. explicitly signalled QoS rules using the PDU Session Establishment / Modification procedure), pre-configured in the UE or implicitly derived by the UE by applying Reflective QoS (see clause 5.7.5). A QoS rule contains the QFI of the associated QoS Flow, a Packet Filter Set (see clause 5.7.6) and a precedence value (see clause 5.7.1.9). An explicitly signalled QoS rule contains a QoS rule identifier which is unique within the PDU Session and is generated by SMF. There can be more than one QoS rule associated with the same QoS Flow (i.e. with the same QFI). A default QoS rule is required to be sent to the UE for every PDU Session establishment and it is associated with a QoS Flow. For IP type PDU Session or Ethernet type PDU Session, the default QoS rule is the only QoS rule of a PDU Session which may contain a Packet Filter Set that allows all UL packets, and in this case, the highest precedence value shall be used for the QoS rule. For Unstructured type PDU Session, the default QoS rule does not contain a Packet Filter Set, and in this case the default QoS rule defines the treatment of all packets in the PDU Session. As long as the default QoS rule does not contain a Packet Filter Set or contains a Packet Filter Set that allows all UL packets, Reflective QoS should not be applied for the QoS Flow which the default QoS rule is associated with and the RQA should not be sent for this QoS Flow. The PCC rules / decision is defined in TS 23.503: The QoS rules is generated by PCF and then provisioned to the SMF. PCC decision: A PCF decision for policy and charging control provided to the SMF (consisting of PCC rules and PDU Session related attributes), a PCF decision for access and mobility related policy control provided to the AMF, a PCF decision for UE policy information provided to the UE or a PCF decision for service related policy (e.g. background data transfer policy) provided to the AF. QoS control refers to the authorization and enforcement of the maximum QoS that is authorized for a service data flow, for a QoS Flow or for the PDU Session. A service data flow may be either of IP type or of Ethernet type. PDU Sessions may be of IP type or Ethernet type or unstructured. The authorized QoS for a service data flow template shall include a 5QI and the ARP and may include a 5QI Priority Level For a 5QI of GBR or Delay-critical GBR resource type, the authorized QoS shall also include the MBR, GBR and may include the QoS Notification Control parameter (for notifications when authorized GFBR can no longer ( or can again) be fulfilled). For 5QI of Non-GBR resource type, the authorized QoS may include the MBR and the Reflective QoS Control parameter The 5QI value can be standardized (i.e. referring to QoS characteristics as defined in clause 5.7.3 of TS 23.501), pre-configured (i.e. referring to QoS characteristics configured in the RAN) or dynamically assigned QoS control also refers to the authorization and enforcement of the Session-AMBR, default 5QI / ARP combination and 5QI Priority Level, if applicable. The PCF may provide the Authorized Session-AMBR, the Authorized default 5QI and ARP combination and the 5QI Priority Level as part of the PDU Session information for the PDU Session to the SMF. The Authorized Session-AMBR, Authorized default 5QI / ARP and if available, 5QI Priority Level values take precedence over other values locally configured or received at the SMF. The PCC rules are determined by PCF. The PCF may take the information collected by multiple data sources to make the PCC decision, as specified in 6.2.1.2 of TS23.503: The PCF shall accept input for PCC decision-making from the SMF, the AMF, the CHF, the NWDAF if present, the UDR and if the AF is involved, from the AF, as well as the PCF may use its own predefined information The AMF may provide information related to the UE as defined in clauses 5.2.5.2 and 5.2.5.6 of TS 23.502, for example in the following services: • Npcf_AMPolicyControl service • Npcf_UEPolicyControl Service The SMF may provide information related to the PDU Session as defined in clause 5.2.5.4 of TS 23.502, for example: Default 5QI and default ARP etc. and the parameters in the following services: • Npcf_SMPolicyControl service of TS 23.502 • Npcf_SMPolicyControl_Create service operation: • Inputs, Optional: - subscribed default QoS information • Outputs, Optional: Policy information for the PDU Session as defined in TS 23.503

[20] and Policy Control Request Trigger(s) of SM Policy Association as defined in clause 6.1.3.5 of TS 23.503

[20] , • At PDU Session establishment the NF Service Consumer, e.g. SMF, requests the creation of a corresponding SM Policy Association with the PCF (Npcf_SMPolicyControl_Create) and provides relevant parameters about the PDU Session to the PCF.When the PCF has created the SM Policy Association, the PCF may provide policy information for the PDU Session in the response. The UDR may provide the information for a subscriber connecting to a specific DNN and S-NSSAI, as described in the clause 6.2.1.3. The AF, if involved, may provide application session related information as defined in clause 5.2.5.3 of TS 23.502 directly or via NEF, e.g. based on SIP and SDP, for example: Npcf_PolicyAuthorization Service. This service is to authorise an AF request and to create policies as requested by the authorized AF for the PDU Session to which the AF session is bound. The NWDAF, if involved, may provide analytics information as described in clause 6.1.1.3. Examples of operator policies including network analytics information as inputs for policy decisions included: o Based on the "Service Experience" statistics or predictions, the PCF may check the 5QI values assigned to the Application, and may use this as input to calculate and update the authorized QoS for a service data flow template. o Based on the "User Data Congestion" statistics or predictions including the list of applications contributing the most to the traffic the PCF may perform SM Policy Association modifications to update policies in the SMF for the PDU sessions handling traffic from those applications. o Examples of operator policies including combination of multiple network analytics as inputs for policy decisions are included: Based on the notification of application(s) in use, provided by "UE Communication" analytics, the PCF may request the "Service Experience" analytics (optionally per RAT Type and / or per Frequency) for each application in use as defined in the list of examples of operator policies that may include network analytics as input for a policy decision. QoS flow descriptions in Clause 6.25 of TS 24.501: 2.5.1.1.4 QoS flow descriptions The network can also provide the UE with one or more QoS flow descriptions associated with a PDU session at the PDU session establishment or at the PDU session modification. Each QoS flow description contains: a) a QoS flow identifier (QFI); b) if the flow is a GBR QoS flow: 1) Guaranteed flow bit rate (GFBR) for UL; 2) Guaranteed flow bit rate (GFBR) for DL; 3) Maximum flow bit rate (MFBR) for UL; 4) Maximum flow bit rate (MFBR) for DL; and 5) optionally averaging window, applicable for both UL and DL; c) 5QI, if the QFI is not the same as the 5QI of the QoS flow identified by the QFI; and d) optionally, an EPS bearer identity (EBI) if the QoS flow can be mapped to an EPS bearer as specified in subclause 4.11.1 of 3GPP TS 23.502 [9], If the averaging window is not included in a QoS flow description for a GBR QoS flow with a 5QI indicated in 3GPP TS 23.501 [8] table 5.7.4-1, the averaging window associated with the 5QI in 3GPP TS 23.501 [8] table 5.7.4-1 applies for the averaging window. if the averaging window is not included in a QoS flow description for a GBR QoS flow with a 5QI not indicated in 3GPP TS 23.501 [8] table 5.7.4-1, the standardized value of two seconds is used as the averaging window. Overview of NWDAF analytics to support policy decision As mentioned above, when making PCC rules or other policy decisions, the PCF may consider the NWDAF analytics as input for decision making. The NWDAF analytics are defined in TS 23.288. As described above, UE Communication and Service Experience are two analytics 5 used by the PCF to determine the QoS currently. UE Communication Analytics is defined in clause 6.7.3 of TS 23.288, and was introduced to support some optimized operations, e.g. customized mobility management, traffic routing handling, RFSP Index Management, QoS improvement or Inactivity Timer optimization, in 5GS, an NWDAF may perform data analytics on UE communication pattern and user plane 10 traffic and provide the analytics results (i.e. UE communication statistics or prediction) to NFs in the 5GC or an AF. An NWDAF supporting UE Communication Analytics collects per-application communication description from AFs. If consumer NF provides an Application ID, the NWDAF only considers the data from AF, SMF and UPF that corresponds to this application ID. NWDAF may also collect data from AMF. 15 The output analytics (use predictions as examples) of the UE Communication Analytics are in Table 1 (Table 6.7.3.3-2: UE Communication Predictions of TS 23.822) The outputs include the per UE or per UE group parameters, and per application ID level parameters. Table 1: Table 6.7.3.3-2: UE Communication Predictions of TS 23.822 Information Description UE group ID or UE ID Identifies a UE or a group of UEs, e.g. internal group ID defined in clause 5.9.7 of TS 23.501 [2] or SUPI (see NOTE). UE communications (1..max) (NOTE 1) List of communication time slots. > Periodic communication indicator (NOTE 1) Identifies whether the UE communicates periodically or not. > Periodic time (NOTE 1) Interval Time of periodic communication (average and variance) if periodic. Example: every hour. > Start time (NOTE 1) Start time predicted (average and variance). > Duration time (NOTE 1) Duration interval time of communication. > Traffic characterization S-NSSAI, DNN, ports, other useful information. > Traffic volume (NOTE 1) Volume UL / DL (average and variance). > Confidence Confidence of the prediction. > Ratio Percentage of UEs in the group (in the case of a UE group). Applications (0..max) (NOTE 1) List of application in use. > Application Id Identification of the application. > Start time Start time of the application. > Duration time Duration interval time of the application. > Occurrence probability Probability the application will be used by the UE. > Spatial validity Area where the service behaviour applies. If Area of Interest information was provided in the request or subscription, spatial validity may be a subset of the requested Area of Interest. If a Spatial granularity size was provided in the request or subscription, the number of elements of TAs or cells in the area is smaller than or equal to the Spatial granularity size. N4 Session ID (1..max) (NOTE 1) (NOTE 2) Identification of N4 Session. > Inactivity detection time Value of session inactivity timer (average and variance). > Confidence Confidence of the prediction. NOTE 1: Analytics subset that can be used in "list of analytics subsets that are requested" and "Preferred level of accuracy per analytics subset". NOTE 2: This analytics subset shall only be included if the consumer is SMF. The Observed Service Experience related network data analytics is specified in clause 6.4 of TS 23.288. the Observed Service Experience can provide the analytics of user experience, 5 i.e. average of observed Service MoS and / or variance of observed Service MoS indicating service MOS distribution for services such as audio-visual streaming as well as services that are not audio-visual streaming such as V2Xand Web Browsing services, analytics, in the form of statistics or predictions, to a service consumer. This analytics may collected huge amount of data from different sources and at different levels. And the output analytics can be for an 10 application, an network slice and an UE. The outputs of this analytics are in (use statistics as examples). Table 2: Table 6.4.3-1: Service Experience statistics of TS 23.288 Information Description Slice instance service experiences (0..max) List of observed service experience information for each Network Slice instance. > S-NSSAI Identifies the Network Slice > NSI ID (NOTE 2) Identifies the Network Slice instance within the Network Slice. > Network Slice instance service experience Service experience across Applications on a Network Slice instance over the Analytics target period (average, variance). > SUPI list (O..SUPImax) (NOTE 3) List of SUPI(s) for which the slice instance service experience applies. > Ratio (NOTE 3) Estimated percentage of UEs with similar service experience (in the group, or among all UEs). > Spatial validity (NOTE 6) Area where the Network Slice service experience analytics applies. > Validity period Validity period for the Network Slice service experience analytics as defined in clause 6.1.3. Application service experiences (0..max) List of observed service experience information for each Application. > S-NSSAI Identifies the Network Slice used to access the Application. > Application ID Identification of the Application. > Service Experience Type Type of Service Experience analytics, e.g. on voice, video, other. > UE location (NOTE 1, NOTE 5) Indicating the UE location information (e.g. TAI list, gNB ID, or location coordinates, etc) when the UE service is delivered. > UPF Info (NOTE 4) Indicating UPF serving the UE. > DNAI Indicating which DNAI the UE service uses / camps on. > DNN DNN for the PDU Session which contains the QoS flow. > Application Server Instance Address Identifies the Application Server Instance (IP address of the Application Server) or FQDN of Application Server. > Service Experience Service Experience over the Analytics target period (average, variance). > SUPI list (O..SUPImax) (NOTE 3) List of SUPI(s) with the same application service experience. > Ratio (NOTE 3) Estimated percentage of UEs with similar service experience (in the group, or among all UEs). > Spatial validity (NOTE 6) Area where the Application service experience analytics applies. > Validity period Validity period for the Application service experience analytics as defined in clause 6.1.3. > RAT Type (NOTE 7) Indicating the list of RAT type(s) for which the application service experience analytics applies. > Frequency (NOTE 7) Indicating the list of carrier frequency value(s) of UE's serving cell(s) where the application service experience analytics applies. > SSC Mode SSC Mode selected for the PDU Session used to associate with the application. > PDU Session Type Type of PDU Session used to associate with the application. > Access Type List of Access Type(s) used for the PDU Session for the application. NOTE 1: This information element is an Analytics subset that can be used in "list of analytics subsets that are requested" and "Preferred level of accuracy per analytics subset". NOTE 2: The NSI ID is an optional parameter. If not provided the Slice instance service experience indicates the service experience for the S-NSSAI. NOTE 3: The SUPI list and Ratio in the service experience information for an application can be omitted, if the corresponding parameter(s) is / are provided and are assigned with the same value(s) in the service experience information for the slice instance which the application belongs to. Otherwise, the SUPI list and Ratio are mandatory to be provided for an application service experience. NOTE 4: If the consumer NF is an AF, the "UPF info" shall not be included. NOTE 5: When possible and applicable to the access type, UE location is provided according to the preferred granularity of location information. UE location shall only be included if the Consumer analytics request is for single UE or a list of UEs. Inclusion of UE location requires user consent. NOTE 6: The Spatial validity is present in the output parameters if the consumer provided the Area of Interest as defined in Table 6.4.1-1. NOTE 7: When "any" value has been provided in the request (e.g. "any" RAT type, "any" frequency, or "any" for all the RAT type and frequency indication), the NWDAF provides an instance of the Application service experience per combination of RAT Type(s) and / or Frequency value(s) having the same Service Experience. Overview of Standard SA2 Rel-19 New SID on Core Network Enhanced Support for Artificial Intelligence (Al) / Machine Learning (ML) was approved in SP-231800 during SA 102 meeting (Dec, 2023). As it has been documented in the WT#3.1 in SP-231800: WT3: Study enhancements to support NWDAF-assisted policy control and address network abnormal behaviour WT3.1 - Study whether and what additionally needs to be supported in order to enhance 5GC NF operations (i.e. policy control and QoS) assisted by NWDAF. The work will firstly identify the specific use cases to be considered, in order to identify the appropriate scope. The work will analyse the result impacts on NWDAF (e.g. the need to understand specific NF functionality), and the compatibility of new solutions wrt existing analytics, in order to determine the need and benefits of new solutions. The Key issue description of WT3.1 was agreed and documented during SA2 160 ahe meeting. As documented in clause 5.2.3 of TR 23.700-84, Key Issue #3: NWDAF-assisted policy control and QoS enhancement: The NWDAF can gather quite a lot of data from 5GC NFs, AF and OAM and thus may further assist the PCF in making PCC decisions (which traditionally determine QoS parameters based on its own data and knowledge as well optional statistics and predictions collected from the NWDAF). This Key issue aims to study whether and what additionally needs to be supported in order to enhance 5GC NF operations related to policy control and QoS with the assistance of the NWDAF. In this key issue, the following aspects will be studied: Identification of use cases where policy control and QoS can be further enhanced with assistance from NWDAF. - Whether and how to introduce new 5GC functionality e.g. of the NWDAF and / or PCF to enhance the policy control and QoS, considering operator's policies. - Whether and what additional input information is needed by the NWDAF for providing an assistance to policy control and QoS, and how to gather it. - Whether and what output information, on top of already provided, the NWDAF can provide to assist with policy control and QoS enhancements. - Whether and howto evaluate the quality of the enhanced NWDAF assistance to policy control and QoS. NOTE 1: The study will focus primarily on existing enforcement mechanisms when available and identify new ones only when no existing ones can be used. A use case associated to the above Kl#3 was agreed in SA2 160 ahe meeting, and documented in 5.1.1, 5.1.2 of TR 23.700-84. Use Case #1: NWDAF-assisted QoS enhancement Currently, the QoS parameters are determined by the PCF based on its knowledge, e.g. AF requirements, analytics provided by the NWDAF, etc. After applying the determined QoS parameters to the service, the PCF may determine whether or not the current QoS can fully satisfy the service requirements based on the Service Experience analytics provided by the NWDAF. If the current QoS cannot satisfy the service requirements, the PCF may update the QoS parameters and informs the new parameters to SMF. Then the PCF may require new Service Experience analytics to check whether the updated QoS parameters can satisfy the service requirements. Based on this current framework, it may require several iterations to work out the ideal QoS parameters. Using its knowledge based on data collection, NWDAF can assist the PCF in determining QoS parameters that can achieve the expected service experience requirements. Use Case #2: Enhancements to QoS Determination with NWDAF Assistance A use case is provided for how the network can benefit from the NWDAF-assistance for QoS determination and setup for the purpose of optimising the overall network performance and signalling based on operator's policy. After UE registers with the 5GS, a PDU session set up might be required. Each PDU session is associated with a default QoS rule which provides a default QoS treatment for data flows. Currently the characteristics of the default QoS is determined by the subscribed default values (for parameters such as 5QI, ARP) which the SMF may obtain from the UDM. The default QoS rule might be sufficient for basic browsing or instant messaging over IP, whereas it may not able to satisfy the relatively high service requirements, i.e. of video streaming applications which require better QoS treatment. For example, for V2X and XRM services, the applications may require transmitting traffic with Guaranteed Bit Rate (GBR) or to use certain standardised 5QI values even for non-GBR QoS flows. Therefore, the default QoS requirements may not be able to support such applications. When the QoS flows with different requirements from the default flow are required, modification to the PDU session and thereby to establish a new QoS flow with the required characteristics might be needed. Such modification will result in significant system-wide signalling, including NAS signalling messages between the UE and the 5GC, signalling within 5GC (i.e. signalling between SMF, UPF, PCF), signalling between 5GC and RAN, and also the RRC messages between the RAN and the UE, etc. In order to optimise the network performance by determining QoS in a more intelligent manner, it would be beneficial for the 5GC to leverage NWDAF assistance. For example, when the UE or network trigger PDU session establishment or modification for a new QoS flow with QoS requirements driven by a user or service, it would be beneficial if the QoS characteristics are determined by the network by considering the predictions and measurements of some UE and network related information and also service related information (e.g. service requirements provided by the AF). The information considered by the 5GC could be some patterns in terms of frequency of use of one or more services and the potential QoS requirements to be emerged from the UE subsequently, the QoS sustainability of the UE or of an area the UE belongs to, the corresponding UE locations, the service requirements provided by the AF, etc. Therefore, the PDU session and QoS flow can be established or modified in a more 'future proof and multiple-service-compatible manner and reduce the potential modifications of the existing QoS flow and the corresponding policy control, e.g. PCC rules. Based on this use case, potential enhancements to 5GC functionality e.g. of the NWDAF, PCF, to enhance the policy control and QoS by considering operator's policies, will improve the network performance and UE experience significantly. Multiple solutions on Key Issue #3: NWDAF-assisted policy control and QoS enhancement was documented in TR 23.700-84. In SA2#163 meeting (May 2024), conclusions for Key Issue #3: NWDAF-assisted policy control and QoS enhancement were agreed and documented in clause 8.3 of TR 23.700-84, including Based on PCF request, NWDAF may provide assistance information analytics to PCF to assist the QoS determination and / or modification of QoS parameters. The PCF may take the assistance information into account to determine QoS parameters for a QoS flow, based on the operator's policy. After the PCF determines the QoS parameters, if updated assistance information is received from NWDAF (the updated assistance information may include candidate QoS parameters, the analytics of the duration and usage of established QoS Flows), the PCF may determine to modify the QoS parameters for a QoS flow and provide the modified QoS towards the SMF, based on the operator's policy. In particular: The PCF may send a analytics request or subscription to NWDAF for QoS and policy assistance information analytics. The PCF may include an analytics ID, Filter Information, one or multiple sets of QoS parameters, the candidate value list(s) for each QoS parameter, requesting expected service experience (e.g. QoE), etc. NOTE 1: Details of the input parameters in the PCF request will be determined in normative stage. NOTE 2: Whether to introduce a new analytics ID or reuse existing one will be determined in normative stage. - Based on the PCF request, the QoS and policy assistance information analytics provided by NWDAF may include: expected QoE can be achieved by the candidate QoS parameters (the values of the QoS parameters are within the candidate value list provided by the PCF). NOTE 3: Whether the time window(s) associated with QoS parameters can be provided by PCF and can be then used to determine the candidate QoS will be discussed in the normative work. NOTE 4: Whether to introduce new or reuse existing service / service operation for providing candidate QoS will be determined in normative phase. - The PCF may request one or more analytics from the NWDAF that are used within the same analytics target period, i.e. Observed service experience, QoS sustainability, Network Performance analytics, analytics of the duration and usage of the established QoS Flows. NOTE 5: Possible enhancements to the existing analytics and / or introducing new analytics will be determined in the normative phase. NOTE 6 Details of the input data and corresponding data sources for analytics will be determined in normative stage. NOTE 7: To provide the assistance for policy control and QoS, NWDAF shall not be aware of PCF internal logic. NOTE 8: NWDAF can monitor the accuracy performance of the assistance information analytics based on a request from PCF. Whether to reuse the existing procedures for Analytics Accuracy Monitoring (defined in clause 6.2D ofTS 23.288 [5]) or not can be decidedin the normative phase. Overview of QoS flow analytics in TR 23.288-84 In clause 6.28 Solution #28: QoS Flow Analytics, it is documented to leverage the NWDAF by introducing more inputs and outputs to support the PCF policy determination. The inputs of the NWDAF for QoS Flow Analytics include: 5 Table 6.28.2-1 of TR 23.700-84: Input data from 5GC related to QoS Flow Information Source Description Time SMF Time stamp of the generated data record UE ID SMF, AF SUPI in the case of SMF, external UE ID (i.e. GPSI) in the case of AF Group ID SMF, AF To identify UE group if available Internal Group ID in the case of SMF, External Group ID in the case of AF S-NSSAI SMF Information to identify a Network Slice DNN SMF Data Network Name where PDU connectivity service is provided Application ID SMF, AF Identifying the application providing this information PDU session ID (1..max) SMF Identification of PDU Session. >QoS Flow ID (1..max) Identification of QoS Flow. »QoS profile AN QoS profile of the QoS Flow »QoS rules (1..max) UE side QoS rules of the QoS Flow »>5QI 5QI associated to the QoS Rule »>QoS Parameters QoS parameters of the QoS Rule UE locations (1..max) AMF UE positions >UE location TA or cells that the UE enters >Timestamp A time stamp when the AMF detects the UE enters this location "Service data flow detection" and "Policy control" part of PCC rules PCF The information of the traffic and corresponding policy rules provided by the PCF. The outputs of the NWDAF for QoS Flow Analytics include: NWDAF provides the statistic and prediction of QoS Flow as depicted in Table 6.28.2-2 and 6.28.3-3 respectively. 10 Table 6.28.2-2 of TR 23.700-84: Output statistics of QoS Flow Analytics Information Description UE ID SUPI in the case of SMF, external UE ID (i.e. GPSI) in the case ofAF S-NSSAI Information to identify a Network Slice DNN Data Network Name where PDU connectivity service is provided Application ID Identifying the application QoS Flow (1 ..max) List of QoS Flows >Duration Duration of QoS Flow >Number of usages The number of times that this QoS Flow characteristics are used >QoS profile AN QoS profile of the QoS Flow >QoS rules (1..max) UE side QoS rules of the QoS Flow »5QI 5QI associated to the QoS Rule »QoS Parameters QoS parameters of the QoS Rule >"Service data flow detection" and "Policy control" part of PCC rules Traffic description and applied PCC rules Table 6.28.2-2 TR 23.700-84: Output predictions of QoS Flow Analytics Information Description UE ID SUPI in the case ofSMF, external UE ID (i.e. GPSI) in the case ofAF S-NSSAI Information to identify a Network Slice DNN Data Network Name where PDU connectivity service is provided Application ID Identifying the application QoS Flow (1 ..max) List of QoS Flows >Duration Duration of QoS Flow >Number of used The number of times that this QoS Flow characteristics are used >QoS profile AN QoS profile of the QoS Flow >QoS rules (1..max) UE side QoS rules of the QoS Flow »5QI 5QI associated to the QoS Rule »QoS Parameters QoS parameters of the QoS Rule >"Service data flow detection" and "Policy control" part of PCC rules >"Service data flow detection" and "Policy control"part of PCC rules The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. SUMMARY It is an aim of certain examples of the present disclosure to address, solve and / or mitigate, at least partly, at least one of the problems and / or disadvantages associated with the related art, for example at least one of the problems and / or disadvantages described herein. It is an aim of certain examples of the present disclosure to provide at least one advantage over the related art, for example at least one of the advantages described herein. The present invention is defined in the independent claims. Advantageous features are defined in the dependent claims. Embodiments or examples disclosed in the description and / or figures falling outside the scope of the claims are to be understood as examples useful for understanding the present invention. According to a first aspect of the present disclosure, there is provided a policy control function (PCF) entity configured to: request or subscribe to analytics relating to quality of service (QoS) from an network data analytics function (NWDAF) entity; and receive, from the NWDAF entity, analytics results relating to QoS and comprising service experience information associated with one or more candidate QoS parameter set; wherein the request or subscription indicates one or more QoS parameter set; wherein each QoS parameter set includes at least one parameter and, for each of the at least one parameter, a value for said parameter; and wherein the at least one parameter includes at least one of: 5G QoS Identified (5QI), one or more QoS characteristics, guaranteed flow bit rate (GFBR) or maximum flow bit rate (MFBR). According to various examples, the PCF entity is configured to: based on the analytics results, determine a new policy or QoS for a user equipment (UE), or based on the analytics results, modify an existing policy or QoS for the UE. According to various examples, the request or subscription further indicates a quality of experience (QoE); and wherein the one or more candidate QoS parameter set satisfy the indicated QoE. According to various examples, the analytics results include one or more QoE associated with the one or more candidate QoS parameter set. According to various examples, the request or subscription further indicates one or more of: a preferred order of results for the one or more candidate QoS parameter; or an ordering criterion for one or more QoE associated to the one or more candidate QoS parameter set. According to various examples, the requestor subscription is transmitted to the NWDAF entity via another entity. According to various examples, the analytics results comprise a duration of a time slot; and / or wherein the service experience information comprises an indication of the one or more candidate QoS parameter set. According to various examples, the service experience information includes, for each of the one or more candidate QoS parameter set, one or more of: DNN for a protocol data unit (PDU) session which contains a corresponding QoS flow for said candidate QoS parameter set; a list of RAT type(s) for which the information applies; a QoE associated with said candidate QoS parameter set; value(s) of individual parameter(s) in said candidate QoS parameter set; a validity period within the time slot for the analytics results; an area where the analytics results apply; and a valid duration of a corresponding QoS and / or a valid duration of the service experience information. According to various examples, the value(s) of individual parameter(s) for each of the one or more candidate QoS parameter set correspond to one or more of: a priority level; PDB; PER; an averaging window; or a maximum delay burst volume. According to various examples, the PCF entity is configured to: configured to: if the PCF entity subscribes to the analytics relating to QoS, receive new analytics results relating to QoS from the NWDAF entity. According to various examples, the one or more QoS parameter set and the one or more candidate QoS parameter set include the same parameter(s). According to another aspect of the present disclosure, there is provided a network data analytics function (NWDAF) entity configured to: receive, from a policy control function (PCF) entity, a request or subscription to analytics relating to quality of service (QoS); and provide, to the PCF entity, analytics results relating to QoS and comprising service experience information associated with one or more candidate QoS parameter set; wherein the request or subscription indicates one or more QoS parameter set; wherein each QoS parameter set includes at least one parameter and, for each of the at least one parameter, a value for said parameter; and wherein the at least one parameter includes at least one of: 5QI, one or more QoS characteristics, guaranteed flow bit rate (GFBR) or maximum flow bit rate (MFBR). According to various examples, the NWDAF entity is configured to: obtain data from one or more entity in a network; and derive the analytics results based on the obtained data. According to various examples, the obtained data comprises at least one of: packet filter set, obtained from a session management function (SMF) entity; user equipment (UE) location, obtained from an access and mobility management function (AMF) entity or a gateway mobile location centre (GMLC) entity; a time stamp associated with the obtained data, obtained from an SMF entity; service data, obtained from an operations, administration and maintenance (QAM) entity; a radio access technology (RAT) type camped on by a UE or accessed by the UE, obtained from an SMF entity; delay between a user plane function (UPF) entity and radio access network (RAN) entity, obtained from an QAM entity; and uplink(UL) / downlink(DL) delay between a UE and RAN, obtained from an QAM entity. According to various examples, the analytics results comprise a duration of a time slot; and / or wherein the service experience information comprises an indication of the one or more candidate QoS parameter set. According to various examples, the service experience information includes, for each of the one or more candidate QoS parameter set, one or more of: data network name (DNN) for a protocol data unit (PDU) session which contains a corresponding QoS flow for said candidate QoS parameter set; a list of RAT type(s) for which the information applies; a quality of experience (QoE) associated with said candidate QoS parameter set; value(s) of individual parameter(s) in said candidate QoS parameter set; a time window or time slot associated to the information; a validity period within the time slot for the analytics results; an area where the analytics results apply; and a valid duration of a corresponding QoS and / or a valid duration of the service experience information. According to various examples, the value(s) of individual parameter(s) for each of the one or more candidate QoS parameter set correspond to one or more of: a priority level; packet delay budget (PDB); packet error rate (PER); an averaging window; or a maximum delay burst volume. According to various examples, the request or subscription further indicates a QoE; and wherein a predicted QoE of the one or more candidate QoS parameter set satisfy the indicated QoE. According to various examples, the request or subscription further indicates one or more of: a preferred order of results for the one or more candidate QoS parameter; or an ordering criterion for one or more QoE associated to the one or more candidate QoS parameter set. According to various examples, the request or subscription is received via another entity. According to various examples, the NWDAF entity is configured to: if the PCF entity has subscribed to the analytics relating to QoS, generate new analytics results relating to QoS and providing the new analytics results to the PCF entity. According to various examples, the one or more QoS parameter set and the one or more candidate QoS parameter set include the same parameter(s). According to another aspect of the present disclosure, there is provided a method of (or for) a policy control function (PCF) entity, the method comprising: requesting or subscribing to analytics relating to quality of service (QoS) from an network data analytics function (NWDAF) entity; and receiving, from the NWDAF entity, analytics results relating to QoS and comprising service experience information comprising one or more candidate QoS parameter set; wherein the request or subscription indicates one or more QoS parameter set; wherein each QoS parameter set includes at least one parameter and, for each of the at least one parameter, a value for said parameter; and wherein the at least one parameter includes at least one of: 5G QoS Identified (5QI), one or more QoS characteristics, guaranteed flow bit rate (GFBR) or maximum flow bit rate (MFBR). According to various examples, the method of / for the PCF entity includes operation(s) and / or feature(s) in accordance with any of the examples relating to the PCF entity given above. According to another aspect of the present disclosure, there is provided a method of (or for) a network data analytics function (NWDAF) entity, the method comprising: receiving, from a policy control function (PCF) entity, a request or subscription to analytics relating to quality of service (QoS); and providing, to the PCF entity, analytics results relating to QoS and comprising service experience information comprising one or more candidate QoS parameter set; wherein the request or subscription indicates one or more QoS parameter set; wherein each QoS parameter set includes at least one parameter and, for each of the at least one parameter, a value for said parameter; and wherein the at least one parameter includes at least one of: 5QI, one or more QoS characteristics, guaranteed flow bit rate (GFBR) or maximum flow bit rate (MFBR). According to various examples, the method of / for the NWDAF entity includes operation(s) and / or feature(s) in accordance with any of the examples relating to the NWDAF entity given above. According to another aspect of the present disclosure, there is provided a computer-readable storage medium comprising instructions which, when executed by at least one processor of an electronic device (e.g. computer), cause the electronic device to perform a method according to any one of the aspects or examples described above. Other aspects, advantages and salient features of the invention will become apparent to those skilled in the art from the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 illustrates an exemplary association of QoS rules / policy and applied time window; Figure 2 illustrates an exemplary procedure for candidate QoS analytics; and Figure 3 is a block diagram of an exemplary network entity that may be used in certain examples of the present disclosure. Figure 4 is a flow diagram illustrating a method of a PCF entity according to various examples of the present disclosure. Figure 5 is a flow diagram illustrating a method of an NWDAF entity according to various examples of the present disclosure. DETAILED DESCRIPTION The following description of examples of the present disclosure, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of the present invention, as defined by the claims. The description includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the scope of the invention. The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings. Detailed descriptions of techniques, structures, functions, operations or processes known in the art may be omitted for clarity and conciseness, and to avoid obscuring the subject matter of the present invention. The terms and words used herein are not limited to the bibliographical or standard meanings, but, are merely used to enable a clear and consistent understanding of the invention. Throughout the description and claims of this specification, the words “comprise”, “include” and “contain” and variations of the words, for example “comprising” and “comprises”, means “including but not limited to”, and is not intended to (and does not) exclude other features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof. Throughout the description and claims of this specification, the singular form, for example “a”, “an” and “the”, encompasses the plural unless the context otherwise requires. For example, reference to “an object” includes reference to one or more of such objects. Throughout the description and claims of this specification, language in the general form of “X for Y” (where Y is some action, process, operation, function, activity or step and X is some means for carrying out that action, process, operation, function, activity or step) encompasses means X adapted, configured or arranged specifically, but not necessarily exclusively, to do Y. Features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof described or disclosed in conjunction with a particular aspect, embodiment, example or claim are to be understood to be applicable to any other aspect, embodiment, example or claim described herein unless incompatible therewith. The skilled person will appreciate that the techniques described herein may be used in any suitable combination. Certain examples of the present disclosure provide one or more techniques for NWDAF-based QoS service experience and QoS flow level analytics, for example in a 3GPP 5G NR network. However, the skilled person will appreciate that the present invention is not limited to these examples, and may be applied in any suitable system or standard, for example one or more existing and / or future generation wireless communication systems or standards, including any existing or future releases of the same standards specification, for example 3GPP 5G, 5G-advanced or 6th Generation (6G). The functionality of the various network entities and other features disclosed herein may be applied to corresponding or equivalent entities or features in the same or any other suitable communication systems or standards. Corresponding or equivalent entities or features may be regarded as entities or features that perform the same or similar role, function or purpose within the network. For example, the functionality of a base station or the like (e.g. eNB, gNB, NB, RAN node, access point, wireless point, transmission / reception point, central unit, distributed unit, radio 5 unit, remote radio head, etc.) in the examples below may be applied to any other suitable type of entity performing RAN functions, and the functionality of a UE or the like (e.g. electronic device, user device, mobile station, subscriber station, customer premises equipment, terminal, remote terminal, wireless terminal, vehicle terminal, etc.) in the examples below may be applied to any other suitable type of device. 10 A particular network entity may be implemented as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure. The skilled person will appreciate that the present invention is not limited to the specific examples disclosed herein. For example: 15 • The techniques disclosed herein are not limited to 3GPP 5G. • One or more entities in the examples disclosed herein may be replaced with one or more alternative entities performing equivalent or corresponding functions, processes or operations. • One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals or other type of information carriers that communicate equivalent or corresponding information. • One or more further elements or entities may be added to the examples disclosed herein. • One or more non-essential elements or entities may be omitted in certain examples. • The functions, processes or operations of a particular entity in one example may be divided between two or more separate entities in an alternative example. • The functions, processes or operations of two or more separate entities in one example may be performed by a single entity in an alternative example. • Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example. • Information carried by two or more separate messages in one example may be carried by a single message in an alternative example. • The order in which operations are performed and / or the order in which messages are transmitted may be modified, if possible, in alternative examples. Certain examples of the present disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions and / or a method therefor. Certain examples of the present disclosure may be provided in the form of a system (e.g. network or wireless communication system) comprising one or more such apparatuses / devices / network entities, and / or a method therefor. As documented in the conclusions for Kl#3 in clause 8.3 of TR 23.700-84, the following conclusions for the QoS analytics were made: - The PCF may send a analytics request or subscription to NWDAF for QoS and policy assistance information analytics. The PCF may include an analytics ID, Filter Information, one or multiple sets of QoS parameters, the candidate value list(s) for each QoS parameter, requesting expected service experience (e.g. QoE), etc. - Based on the PCF request, the QoS and policy assistance information analytics provided by NWDAF may include: expected QoE can be achieved by the candidate QoS parameters (the values of the QoS parameters are within the candidate value list provided by the PCF). - The PCF may request one or more analytics from the NWDAF that are used within the same analytics target period, i.e. Observed service experience, QoS sustainability, Network Performance analytics, analytics of the duration and usage of the established QoS Flows. Currently, in TS 23.288 Architecture enhancements for 5G System (5GS) to support network data analytics services, there is no analytics related to QoS flow level analytics or the QoE of different QoS. However, to support intelligent and future-proof decision making of policy at PCF, in particular for PCC rules which is QoS flow level decision, statistics and prediction of QoS flow level parameters and the potential service experience of different QoS of will be useful. In Solution#28 of TR 23.700-84, some information (e.g. NWDAF inputs and outputs) related to QoS flow analytics were provided, but there significant information was missing to fully specify a functional QoS flow analytics, e.g. the proposed PDU session level inputs are not sufficient for NWDAF to generate QoS flow related analytics, the proposed NWDAF outputs are limited and not effective to assist the PCF decision making. Based on the above, to support NWDAF-assisted policy control and QoS enhancement, analytics outputs at QoS flow level and service experience of different QoS are expected to be provided by the NWDAF. In certain examples, the NWDAF analytics (IDs) which can provide the statistics and predictions of QoS flow related parameters and the service experience of different QoS is fully specified to support NWDAF-assisted policy control and QoS enhancement for PCF. In certain examples, the NWDAF based analytics is leveraged to provide output analytics (e.g. statistics and predictions) of QoS flow level parameters and the service experience of one or a list of QoS parameter set(s). For example, the QoS flow level output analytics may include the QoS performance parameters (e.g. data rate, latency, data volume,), the usage duration and number of the usage of different QoS flows that is associated to different QoS parameter sets / profiles and the PCC rules. In addition, the service experience (e.g. MOS, QoE) of different QoS parameter sets / profiles and the PCC rules can be also provided by the NWDAF to the service consumer as required. The consumer may request the NWDAF or subscribe to NWDAF for the QoS flow level parameters and the service experience of one or a list of QoS parameter set(s). In the request, the consumer may include some information that can help the NWDAF to derive the output and control the result reporting or update, e.g. the QoS parameter set and the potential available values of different QoS parameter set. The consumer of the QoS flow related and QoS service experience analytics could be AF, QAM, or any 5GC NF (e.g. PCF, AMF, SMF, UPF, etc.). Based on the request of the consumer and information indicated by the consumer, the NWDAF will collect service data from multiple data sources (e.g. AF, QAM, or any 5GC NF) to perform Al ML model inference and optionally model training for the required QoS flow related and QoS service experience related analytics ID. The data collected by NWDAF might be related to the performance of QoS flow and QoS parameters. The derived output analytics can be in the form of statistics and / or predictions and will be notified to the service consumer by NWDAF. Then the consumer will take the information into account to determine or modify the policy, including the session related policy and non-session related policy. When using PCF as an example of the service consumer, based on the PCF request, the NWDAF provides the statistics and predictions of QoS flow level parameters and the service experience of different QoS. The output analytics may include the usage frequency and usage duration of different QoS flow and the associated policy. The PCF may also require the service experience (e.g. MOS, QOE) of the different QoS and optionally at different times or during different time windows. Based on the analytics outputs and other assistance information, the PCF may determine new policy (e.g. PCC rules) / QoS or modify the existing policy (e.g. PCC rules) / QoS. E.g. the PCF may choose the QoS that provides the satisfying QoE to apply within communication system and also negotiate with AF, or the PCF chooses the QoS that can achieve the highest service experience to apply within communication system. The PCF may interact with AF to notify the determined or updated QoS for QoS negotiation and authorisation, e.g. during setting up an AF session with required QoS procedure. By leveraging NWDAF to provide QoS flow and QoS service experience related analytics, the PCF can have better understanding of the performance and usage of different QoS flows associated to different applications and UEs. And the PCF can be aware of the service experience or the performance of different QoS parameter sets before applying the corresponding configuration into 5GS. Based on the knowledge, the PCF can choose and determine the QoS and policy, which can result in the service experience that satisfy the service requirement. Therefore, the PCF is able to make more intelligent, sustainable and future-proof decisions on QoS determination and modification to improve the service experience of users and overall performance of the network. Certain examples are described in terms of a 5G core network, but may also be applicable to a 4G (EPC) or 6G Core network or other future generations of communication systems. In certain examples, the term ‘QoS’ can be replaced by policy, PCC / QoS rules, (QoS) policy, QoS profile, QoS parameters, QoS reference, etc. Various examples of the present disclosure will now be described in more detail. General As described in Use Case #1 and #2 of TR 23.700-84, each PDU session is associated with a default QoS rule which is normally sufficient for basic browsing or instant messaging over IP in general. For some services that require higher or specific QoS treatments (e.g. V2X, XRM, etc.), modification to the established PDU session might be required, e.g. by establishing new QoS flow or modifying the default QoS rule, which will increase the complex the system and involve significant system-wide signalling. Furthermore, the modification to the PDU session still cannot guarantee that the assigned QoS can satisfy the service requirements. In order to optimise the network performance, it would be beneficial for the 5GC to leverage NWDAF assistance to determine the QoS and policy control in a more 'future proof and multiple-service-compatible manner. If the PCF observes that the customer service experience is low or cannot meet the requirement, the PCF may determine to update the policy (e.g. PCC rules) and inform the update policy to SMF. Then the SMF needs to derive new QoS parameters / profile and inform the information to UPF and AN. The above policy update will result in a configuration update in the entire communication system, e.g. within the core network (e.g. 5GC for 5G system and any possible terminologies for 6G and future communication systems), between core network and AN, between AN and UEs, etc. In order to assist the PCF to determine policy, e.g. PCC rules, one or more analytics IDs, QoS monitoring and other measurements will be helpful, e.g. PCC rules. For example as concluded clause 8.3ofTR 23.700-84: The PCF may request one or more analytics from the NWDAF that are used within the same analytics target period, i.e. Observed service experience, QoS sustainability, Network Performance analytics, analytics of the duration and usage of the established QoS Flows. Based on above, the QoS level analytics will be useful to support PCF to determine policy or support NWDAF to determine candidate QoS which will be sent to PCF for policy decision making. However, currently there is no QoS level analytics specified in TS 23.288 and the solution provided in Solution#28 in TR 23.700-84 is not sufficient, e.g. the proposed NWDAF inputs in PDU session level are not sufficient to derive the analytics output at QoS flow level, and the proposed analytics outputs are not sufficient to support the PCF to determine policy. The QoS level analytics might be new analytics to be specified in TS 23.288, or enhancement to any existing analytics in TS 23.288, e.g. Observed Service Experience related network data analytics, UE communication analytics, PDU session traffic analytics, etc. In certain examples, in order to support NWDAF-assisted policy control and QoS enhancement, the interaction between consumer (e.g. AF, PCF) and NWDAF and the details of NWDAF analytics at QoS flow level are fully specified. The consumer requests the NWDAF to provide QoS Flow related analytics by indicating: • application ID(s). • The QoS flow / service flow associated to the interested application ID(s). • The UE(s) that are interested in the service flow from the corresponding application ID(s). • The traffic / service requirements / characteristics of the service, e.g. associated to the interested application ID(s). o QoS requirements, QoS reference, or QoS parameters, e.g. 5QI, ARP, RQA, QoS Parameter Notification control, Flow Bit Rates, Aggregate Bit Rates, Maximum Packet Loss Rate, etc. o Expecting / required service experience, e.g. QOE, MOS. • Potential policy (e.g. PCC rules), could be authorised or not yet authorised rules. • Indication of the request QoS flow related parameters (the QoS parameters are as defined in TS 23.501) as output, e.g. 5QI, ARP, RQA, QoS Parameter Notification control, Flow Bit Rates, Aggregate Bit Rates, Maximum Packet Loss Rate, etc. Based on the request of the consumer and information indicated by the consumer, the NWDAF will collect service data from multiple data sources (e.g. AF, QAM, or any 5GC NF) to performance Al ML model inference and optionally model training for the required QoS flow related analytics ID. Examples of the input data are described below (“Support for QoS flow analytics”). Once the NWDAF derives the output, for example as described below (“Support for QoS service experience related analytics”), the output analytics in the form of statistics and / or predictions will be notified to the service consumer by NWDAF. Then the consumer will take the information into account to determine or modify policies, including the session related policy and non-session related policy. E.g. the PCC rules, UE policies, the AM policy, SM policy, etc. From the perspective of the NWDAF service consumer: • If the PCF is the consumer of the QoS Flow related analytics, the PCF may determine the PCC policy based on the assistance information / analytics provided by NWDAF. E.g. the PCF may determine the modify / determine the default QoS rule of a PDU session to the one that was / to be used more frequently, can satisfy the most of / all the services experience requirements (e.g. QoE) transmitted via this PDU session or QoS flow. Based on the QoS flow analytics, the PCF determines to generate new / duplicate the policy that was / to be used more frequently and can satisfy the most of / all the services experience requirements to establish new QoS flow or modified the existing QoS flow. • The AF could be also the consumer of the QoS Flow related analytics, as the AF should be aware of the QoS performance of interested UEs in interested areas to determine the expecting service quality and service requirement. • More details are described below (”6.x.4 Procedures”). Explanation of time window In the existing 5G NR system / 5GC, multiple PDU sessions can be established for a UE. And within one PDU session, the NW may determine to establish one or more QoS flow, based on NW implementation. For each QoS flow, based on the description in clause 5.7.1.1 QoS Flow of TS 23.501: Any QoS Flow is characterised by: - A QoS profile provided by the SMF to the AN via the AMF over the N2 reference point or preconfigured in the AN; - One or more QoS rule(s) and optionally QoS Flow level QoS parameters (as specified in TS 24.501

[47] ) associated with these QoS rule(s) which can be provided by the SMF to the UE via the AMF over the N1 reference point and / or derived by the UE by applying Reflective QoS control; and - One or more UL and DL PDR(s) provided by the SMF to the UPF. For a QoS flow, different PCC rules or QoS rules / parameter sets / profiles might be applied at different times (windows) to achieve the required / targeting / expected service experience and quality (e.g. QoE). The PCF / SMF may consider the traffic pattern of the UE / PDU session / QoS flow for the determination of the PCC rules / QoS rules. For example, the PCF may configure PCC rules or QoS rules / parameter sets / profiles for a QoS flow. After a while, the PCF modify the PCC rules to update the QoS rules for the UE at different time points. The PCF may further update the PCC rules or QoS rules / parameter sets / profiles in the future. The determined QoS / policy will be informed to SMF, UPF, RAN, UE. Alternatively, the PCF may configure multiple PCC rules / QoS rules are configured for different time duration / windows of a flow. Based on the configuration, different QoS rules will be used by SMF / UPF for the flow at different time window / duration to. As shown in Figure 1, for a QoS flow X (QFI=X), different QoS rules / parameters / policy might be applied at different windows based on (pre-)configuration (e.g. PDU establishment) and modification procedure (e.g. PDU modification). For example, QoS rule ID 1 which is window 1; QoS rule ID 2 which is window 2; QoS rule ID n which is window 3; associated to PCC rule 1, is associated to PCC rule 2, is associated to PCC rule n, is applied during duration / time applied during duration / time applied during duration / time • It might be possible that the QoS rule ID 1 which is associated to PCC rule 1, is applied again for this QoS flow during duration / time window 4. This might be based on the configuration of the QoS rules application time, or based on the configuration modification of the QoS rules of this QoS flow (e.g. the PCF may determine that the service experience / quality of QoS / PCC rule 2 and n is not better than QoS / PCC rule 1; or due to the traffic pattern, the PCF may determine QoS / PCC rule 1 can provide better service for the in-coming traffic, etc.). • QoS rule ID n which is associated to PCC rule n, is applied again for QoS flowX during duration / time window 5; • QoS rule ID 1 which is associated to PCC rule 1, is applied the 3rd time for this QoS flow during duration / time window 6; In certain examples, the duration / time window of QoS rules / PCC rules / QoS parameters indicates the duration 1,2,...6,...n in Figure 1 association of QoS rules / policy and applied time window. This applies to both the inputs and outputs parameters of NWDAF. The overall time window could be used to count to the number of usage of the QoS flow / QoS rule / QoS parameters / PCC policy. This overall time window could be configure by the service consumer in the analytics request, or preconfigured subject to operator’s policy or application arrangement. The time slot entries in the output parameters maybe equivalent to the different the overall time window. Interaction between NWDAF and service consumer (e.g. PCF.SMF, UPF, AMF, AF) As it has been concluded in clause 8.3 of TR 23.700-84 below, the PCF may require one or more analytics IDs to assist the policy determination, e.g. for PCC rules. The PCF may request one or more analytics from the NWDAF that are used within the same analytics target period, i.e. Observed service experience, QoS sustainability, Network Performance analytics, analytics of the duration and usage of the established QoS Flows. In order to require the above listed analytics IDs, the consumer (e.g. PCF, AF) may invoke the Nnwdaf_AnalyticsSubscription Service or Nnwdaf_Analyticslnfo service operation to subscribe to NWDAF to require analytics output information from NWDAF. In addition, new pcf / nwdaf service operation might be also specified to support the policy decision making at PCF, e.g. Nnwdaf_QoS / policy_AnalyticsSubscription Service or Nnwdaf_ QoS / policy_Analyticslnfo, etc. More than one QoS flow usage duration and frequency / number classes might be assigned by operator / consumer / application service provider to categorise the performance and usage of QoS flows. For example, the classes are assigned to a list of UEs / QoS flow / QoS rules / QoS policy / QoS profile / application IDs / PDU sessions. The classes / groups might be classified into high-, medium- and low- usage duration and frequency / number with respect to the threshold(s) of the corresponding class. The threshold(s) of corresponding class might be provided by the operator / consumer / application service. In the consumer (e.g. PCF, UPF, SMF, UDR / UDM, etc.) request or subscription to NWDAF, the following information might be included: The bold text corresponds to certain examples of the present disclosure. The text in italic has been documented in clause 6.28.2 of TR 23.700-84. - Analytics ID, e.g. = "QoS Flow" or any other existing analytics ID(s) in TS 23.288, e.g. Observed Service Experience related network data analytics, UE communication analytics, PDU session traffic analytics, etc. - Target of Analytics Reporting: a single UE (SUPI) or a group of UEs (an Internal Group ID), any UE, a single application ID or a group of application ID(s), a or a group of PDU session application ID(s), a or a group of QoS flow ID(s) (e.g. QFI), a or a group of QoS flow ID(s) (e.g. QFI)), a or list of QoS rule identifier (QRI), etc. - Analytics Filter Information optionally including: - S-NSSAI; - DNN; - Application ID; - Area of Interest; - an optional list of analytics subsets that are requested. - RAT type - type of QoS flow, e.g. GBR, non-GBR, delay-critical QoS flow. - UE location - one or more of the following for of a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, or unstructured PDU session type - PDU session ID - QoS flow ID (QFI), 5QI - QoS parameters, QoS requirements, QoS profile, QoS rules, (PCC) policy (ID), a QoS rule identifier (QRI) - as specified in TS 24.501; - Packet Filter Set of the QoS rule, e.g. associated to the QRI - a precedence value of the QoS rule, e.g. associated to the QRI - The default QoS rule indication (DQR) as specified in TS 24.501 - Service experience / QoE (Quality of experience), e.g. of the qos flow / the user(s) / the application ID / the service flow, etc. - QoS Flow level QoS parameters (as specified in TS 24.501), e.g. for a GBR QoS flow Guaranteed flow bit rate (GFBR) for UL and DL, Maximum flow bit rate (MFBR) for UL and DL, and - flow bit rate (UL and DL) - delay (DL, UL and roundtrip), e.g. e2e delay between UE and UPF, delay between UE and RAN, delay between RAN and UPF, etc. - Analytics / Performance feedback information, e.g. may contain the information on the (UE) location, time (window), service quality / experience of the QoS rule, the duration and frequency / number of usage of the corresponding QoS rule(s) statistics and predictions, and the Reporting Threshold(s) that were crossed. - UE location, interested area / location - Targeting / required / expecting service experience (e.g. QoE) of a qos flow / qos rule / UE / application - A request of service experience (e.g. QoE) of a qos flow / qos rule / UE / application that was / to be achieved. - Reporting Thresholds: which apply only for subscriptions and indicate conditions on the levels to be reached for the respective analytics subsets of the analytics outputs. E.g. the thresholds of the QoS parameters, the number / usage frequency of one or more QoS flow, the duration / usage time of one or more QoS flow, QoE of one or more QoS flow / parameters / profile, etc. - type of QoS flow in the consumer’s interests, e.g. GBR, non-GBR, delay-critical QoS flow. - location of UE(s) - one or more of the following for of a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, or unstructured PDU session type - PDU session ID - QoS flow ID (QFI), 5QI - QoS parameters, QoS requirements, QoS profile, QoS rules, (PCC) policy (ID), a QoS rule identifier (QRI) - as specified in TS 24.501; - Packet Filter Set of the QoS rule, e.g. associated to the QRI - a precedence value of the QoS rule, e.g. associated to the QRI - The default QoS rule indication (DQR) as specified in TS 24.501 - Service experience / QoE (Quality of experience), e.g. of the QoS flow / the user(s) / the application ID / the service flow, etc. - QoS Flow level QoS parameters (as specified in TS 24.501), e.g. for a GBR QoS flow Guaranteed flow bit rate (GFBR) for UL and DL, Maximum flow bit rate (MFBR) for UL and DL, and - time window(s), one or more time window used to derive the statistics and prediction of the QoS flow related analytics - An Analytics target period indicates the time period over which the statistics or predictions are requested. - Preferred level of accuracy of the analytics. - Optional Preferred level of accuracy per analytics subset; - Optional preferred order of results for the list of QoS Flows: - ordering criterion: "duration" or "number of usages", service experience (e.g. QoE) - order: ascending or descending.e.g. the consumer PCF / AF / SMF may require the NWDAF to provide the usage of QoS flow in descending order which means the most frequent usage QoS and / or the QoS used for the longest duration will be ranked on 1st place. - Optionally, maximum number of objects, e.g. the max. / min. Number of QoS flows, PDU session, max. / min number of number / usage frequency of one or more QoS flow, max. / min number of duration / usage time of one or more QoS flow, max. / min QoE of one or more QoS flow / parameters / profile. - In a subscription, the Notification Correlation Id and the Notification Target Address are included. - different groups / classes of the Number of QoS flows, PDU session, of number / usage frequency of one or more QoS flow, of duration / usage time of one or more QoS flow, of one or more QoS flow / parameters / profile, etc. E.g. high- / medium- / low- Number of QoS flows, PDU session, of number / usage frequency of one or more QoS flow, of duration / usage time of one or more QoS flow, of one or more QoS flow / parameters / profile. The classes / groups could be configured by the operators, applications, PCF, etc. - threshold to groups the different groups / classes of Number of QoS flows, PDU session, of number / usage frequency of one or more QoS flow, of duration / usage time of one or more QoS flow, of one or more QoS flow / parameters / profile, etc. Support for QoS flow analytics Inputs of NWDAF The NWDAF supporting analytics on QoS flow analytics shall be able to collect information from AF, QAM and 5GC NFs (e.g. PCF, SMF, UPF, etc.). 5 In Table 3 (inputs of NWDAF to derive the statistics and predictions of QoS flow related analytics), the bold input parameters are new parameters in certain examples. The other parameters in italic have been documented in clause 6.28.2 of TR 23.700-84. The different levels of the parameter are not limited to the examples in the table. Any parameter can be in any level, may not be necessarily in the subset of other parameters. This 10 also applies to all the input and output parameters in the present disclosure. Table 3: inputs of NWDAF to derive the statistics and predictions of QoS flow related analytics Information Source Description Time SMF Time stamp of the generated data record UE ID SMF, AF SUPI in the case of SMF, external UE ID (i.e. GPSI) in the case of AF Group ID SMF, AF To identify UE group if available. Internal Group ID in the case of SMF, External Group ID in the case of AF S-NSSAI SMF Information to identify a Network Slice DNN SMF Data Network Name where PDU connectivity service is provided Application ID SMF, AF Identifying the application providing this information Overall time window SMF, UPF, PCF. OAM The overall time window for collecting the following data. RAT Type SMF.AMF The RAT type the UE camps on if in idle mode or access to if in connected mode. If the UE is connecting to more than one RAT type, the RAT type might be associated to different PDU sessions or QoS (flow) in this table. PDU session ID (1..max) SMF, UPF Identification of PDU Session. >PDU Session status SMF, OAM Status of the PDU Session (activated, deactivated). >PDU inactivity timer / Inactivity detection time SMF, UPF, OAM Value of session inactivity timer. > time stamp / point of PDU SMF, UPF, The time point / stamp when the PDU session inactivity 1 activity OAM switches to inactivity and / or activity > duration / time window SMF, UPF, OAM Start and end time / time window / duration of PDU session activation / deactivation. >QoS Flow ID (1..max) SMF, UPF, OAM Identification of QoS Flow. Max. is the max. number of the QoS flow within the corresponding PDU session. »application________ID(s) / application qroup ID SMF, UPF, OAM Identification of the application(s). The application(s) of which the traffic flow(s) are associated to the corresponding QoS flow (ID). » QFI / 5QI SMF, UPF, PCF, OAM Identification of QoS Flow. » QoS flow status SMF, UPF, AMF, OAM e.g. The QoS flow is active / not active. Might be collected from SMF or UPF using new events, or collects from AMF. » QoS flow active / SMF, UPF, OAM Value of QoS flow inactivity timer. Or QoS flow activity in TS 28.552, e.g. 5.1.1.13.2.1 In-session activity time for QoS flow provides the deactivate time aggregated active session time for QoS flow in a cell. The measurement is split into subcounters per QoS level » duration / time window of QoS flow status SMF, UPF, PCF, OAM Start and end time / time window / duration of QoS Flow activation / deactivation. Or the duration / time window associated to different QoS rules / profiles / parameters / policy. » flow bit rate / traffic rate / throughput SMF, UPF, OAM flow bit rate / traffic rate of the associated gos flow. Might be averaged within the time window of QoS activation and deactivation. »traffic volume SMF, UPF, OAM The traffic volume of the associated gos flow. Might be accumulated within the time window of QoS activation and deactivation. »QoS rules (1..max) UE side QoS rules of the QoS Flow »>5QI 5QI associated to the QoS Rule »> QoS Parameters / QoS profile SMF, UPF, PCF QoS parameters of the QoS Rule »> QoS rule ID PCF, SMF, UPF QoS rule identifier (QRI). As defined in TS 23.501, QoS rule identifier which is unique within the PDU Session and is generated by SMF. »> PCC rule (identifies) PCF, AF The PCC rule and / or the identifies of the PCC rules »> associated policy PCF, SMF The associated policv (e.g. PCC rule. QoS related policv) corresponds to the QoS flow and the duration / time window that the policv rules applied. »> number of SMF, UPF, PCF The number of usage of the QoS flow / QoS rule / QoS parameters / PCC policy. The number of usage could be counted within a time window, e.g. the overall time window in Figure 1 usage association of QoS rules / policv and applied time window. »> duration / time window of QoS SMF, UPF, PCF The duration / time window of QoS rules / PCC rules / QoS parameters, eguivalent to the duration rules / PCC rules / QoS parameters 1,2,...6,...n in Figure 1 association of QoS rules / policv and applied time window. »> flow bit rate / SMF, UPF, OAM flow bit rate / traffic rate of the associated QoS flow per duration of QoS rules / PCC rules / QoS parameters (as defined above). Might be averaged within the time window of QoS activation and traffic__________rate / throughput deactivation. »> traffic volume / throughput SMF, UPF, OAM, AF The traffic volume of the associated QoS flow per duration of QoS rules / PCC rules / QoS parameters (as defined above).. Might be accumulated within thetime window of QoS activation and deactivation. Average / Minimum / Maximum traffic volume / Throughput. »> delay UPF, SMF, AF e.g. QoS flow Packet Delay collected from UPF for the observed Packet delay for UL / DL direction. The UE with an Application Server that includes: UL / DL Average / Maximum Packet Delay, »> packet loss UPF, SMF, AF, QAM UL / DL Averaqe / Maximum Loss Rate UE locations (1..max) and / or UE trajectory (1..max) AMP, AF, LCS UE positions >UE location TA or cells that the UE enters Location of the UE(s) needs to be collected from AMF if the application needs to be started at the same time. If the Aoi indicated by the AF is a finer qranularity area than the Cell level, the current location of the UE(s) needs to be collected from GMLC instead >Timestamp A time stamp when the AMF, AF, LCS / GMLC detects the UE enters this location "Service data flow detection" and "Policy control" part of PCC rules PCF The information of the traffic and corresponding policy rules provided by the PCF. Table 4 (inputs of NWDAF collected from AF to derive the statistics and predictions of QoS flow related analytics) are new in certain examples. The parameters listed in Table 4 (inputs of NWDAF collected from AF to derive the statistics 5 and predictions of QoS flow related analytics) might be also collected from QAM, 5GC NF (e.g. PCF, SMF, UPF, UDR / UDM, etc.). Table 4: inputs of NWDAF collected from AF to derive the statistics and predictions of QoS flow related analytics Information Source Description Time stamp AF Time stamp of the data recorded Application ID AF AF identifier of the application QoS AF QoS for a UE or list of UEs of the traffic from the corresponding application ID UE addresses / IDs AF The IDs of the UE or list of UEs, e.g. of the traffic from the corresponding application ID e.g. GPSI, IP address or MAC address etc. Flow description information AF as described in clause 6.1.3.6 of TS 23.503 e.g. source and destination IP address and port numbers and the protocol information to enable the binding functionality and the generation or selection of the service data flow filter(s) in the PCC rules QoS Reference or individual QoS parameters AF QoS Reference or individual QoS parameters associated to the Flow description information of the corresponding application ID Alternative Service Requirements AF Containing one or more QoS Reference parameters or Requested Alternative QoS Parameter Sets in a prioritized order Time period AF The time period associate to the parameters in this table. Targeting service quality and experience AF Targeting service quality and experience of the UE(s) of the traffic associated to the corresponding application ID QoS duration (interval) AF The duration of QoS QoS inactivity interval AF The internal of QoS inactivity or activity Outputs of NWDAF The NWDAF supporting QoS flow related analytics provides the analytics results to consumer NFs, e.g. AF, PCF, SMF, UPF, or NEF. The analytics results provided by the NWDAF could be QoS flow statistics and / or predictions. 5 In Table 5 (QoS flow related statistics and predictions), the bold output parameters are new parameters in examples of the present disclosure. The other Italic parameters have been documented in clause 6.28.2 of TR 23.700-84. Table 5: QoS flow related statistics and predictions Information Description UE ID SU PI in the case of SMF, external UE ID (i.e. GPSI) in the case of AF Could be one or list of UEs. S-NSSAI Information to identify a Network Slice DNN Data Network Name where PDU connectivity service is provided Application ID Identifying the application RAT type(s) Indicate the list of RAT types, e.g. for which the UE(s) / PDU session / QoS flow, e.g. LTE, NR, 6G RAN, etc. The RAT type the UE camps on if in idle mode or access to if in connected mode. If the UE is connecting to more than one RAT type, the RAT type might be associated to different PDU sessions or QoS (flow) in this table. Time slot entry (1„max) Time slot entry (1..max) > PDU session (1...max) The PDU session of the UE(s) » PDU session ID The ID of the corresponding PDU session » QoS FlowlD (1..max) List of QoS Flows within a PDU session The max. is the maximum number of the QoS. e.g. within the corresponding PDU session »> QoS flow ID / QFI Identification of QoS Flow >»Durationl Time window The statistics and predictions of Duration_ / time window of QoS Flow / start and end time associated to the QoS flow activation / deactivation. »>Number of usages The number of times that this QoS Flow characteristics are used »> Application ID(s) / application group ID The application ID(s) associated to the corresponding QoS flow / policy / QoS profile / QoS parameters. »>QoS profile AN QoS profile of the QoS Flow >>>QoS rules (1..max) UE side QoS rules of the QoS Flow »»5QI 5QI associated to the QoS Rule >>»QoS Parameters QoS parameters of the QoS Rule »» QoS rule identifier (QRI); QoS rule identifier (QRI), as specified in TS24.501. »» PCC rule identifies The identifier of the PCC rule »» QoE, service quality / experience QoE, service Quality / experience Associated to the corresponding QoS flow and the duration »» applied level of QoS flow / QoS_____profile / _____QoS parameter / policy How often the QoS is used. The applied freguency / level of the corresponding QoS flow / QoS profile / QoS parameter / policy, e.g. High-, medium-, low-freguency / level of the corresponding QoS flow / QoS profile / QoS parameter / policy applied / used for data / service transmission. »» QoS duration The duration of the QoS applied. E.g. start and end time associated to the QoS rule / parameters / policy »» service experience The service experience of QoS, e.g. QoE. »> flow bit rate Bit rate of the QoS Flow, for GBR flow. Could be Guaranteed Flow Bit Rate (GFBR) - UL and PL, and / or Maximum Flow Bit Rate (MFBR) — UL and DL. »> QoS flow type The type of QoS flow, e.g. GBR, non-GBR, delay-critical QoS flow. > Validity period The validity period for the QoS flow related statistics and prediction as defined in clause 6.1.3 of TS 23.288. > spatial Validity The Area where the QoS flow related statistics and prediction applied. classified usage level of QoS flow Classified usage level of QoS flow statistics and predictions for multiple UEs / QoS flows / PDU session with respect to one or more reporting thresholds (e.g. NWDAF may provide the ratio of QoS floes that have reached certain Reporting Threshold(s)). The list of UEs / QoS flows or the associated application ID is indicated in the reouest of service consumer. > usage level of QoS flow classes (1.,. max) List with group of Ues / QoS flows / policies / QoS classified by ranges of usage level of QoS flow, e.g. the number of usage, the usage freguency, duration, etc. The QoS flow might be replaced by the PCC rule / policy (ID), QoS parameters, QoS profile (ID), etc. The QoS flow classes could be high-, medium, low-freguency usage / number of usage; or long-, medium-, short-duration of usage. » UE ID(s) / QoS flow IDs / PCC rule / policy (ID), QoS parameters, QoS profile (ID) / PDU session Identifies the UE(s) / QoS flow / PCC rule / policy / PDU session, or QoS parameters, QoS profile in the class with respect to the threshold of the corresponding usage freguency or duration. » Ratio usage level of QoS flow classes Ratio of UEs of QoS parameters / QoS profile (ID / policy / QoS flow per class. > Validity period The validity period for the QoS flow related statistics and prediction as defined in clause 6.1.3 of TS 23.288. > spatial Validity The Area where the QoS flow related statistics and prediction applied. >"Service data flow detection" and "Policy control" part of PCC rules Traffic description and applied PCC rules Support for QoS service experience related analytics 6.x. 1 General Clause 6.x describes how NWDAF can provide the QoE of candidate QoS based on the consumer request. QoS and policy assistance analytics can be used to assist PCF with deciding policy, i.e. PCC rules and QoS parameters. The consumer may provide the list of targeting QoS and PCC rules of a service flow to the NWDAF. Based on the targeting QoS parameter set(s) provided by the consumer, the NWDAF generates the QoE(s) of the corresponding QoS parameter set(s) in the list. In addition, the service consumer may also provide the allowed values of individual QoS parameters of the different QoS parameter set(s) in the list, and the targeting service experience (i.e. QoE) of the service flow. Using the list of targeting QoS and the allowed values of individual QoS parameters, the NWDAF generates the candidate QoS parameter set(s) that can fulfil the QoE indicated by the service consumer and informs the consumer of the candidate QoS parameter set(s), the PCC rules and the associated QoE(s). In order to derive the QoS analytics, the NWDAF collects data from AF, QAM, 5GC NFs (e.g. SMF, PCF, etc.). The consumer can either subscribe to analytics notifications (i.e. a Subscribe-Notify model) or request a single notification (i.e. a Request-Response model). The consumer may provide a list of target QoS parameter set(s) and optionally list(s) of candidate values of individual QoS parameters of different QoS parameter set(s), e.g. list of candidate values of UL / DL flow bit rate of QoS parameter set 1; a list of candidate values Maximum Packet Loss Rate of QoS parameter set 2, etc. The consumer may also provide the expecting QoE(s) associated to the list of QoS parameter set(s) and optionally the acceptable range / variation of the expecting QoE(s) (e.g. X <QoE <Y), the minimum / maximum / average acceptable QoE. Based on the request of the consumer, the NWDAF generates the QoE of the target QoS parameter set(s) provided by the consumer. If the consumer also provide the candidate values of individual QoS parameters in different QoS parameter set(s), the NWDAF may optimise the QoS parameter set(s) by computing the QoE of different QoS parameter combinations. The NWDAF may also notify the QoS parameter set(s) that can satisfy the QoE requirements to the consumer, and optionally in the order as required by the consumer (e.g. ascending or descending order to the QoE). If there is no QoS parameter set / combination that can satisfy the required QoE, the NWDAF may notify the one or more QoS parameter set / combinations with the best QoE, e.g. the QoS parameter set / combinations associated to top N QoE / service experience quality. The service consumer may be an NF (e.g. PCF or AF). The consumer of these analytics indicates in the request or subscription: - Analytics ID = "QoS and policy assistance analytics ". - Target of Analytics Reporting as defined in clause 6.1.3. - Analytics Filter Information optionally includes: - DNN; - Application ID; - Area of Interest (AOI(s)): restricts the scope of the QoS service experience analytics to the provided area; - A list of analytics subsets that are requested (see clause 6.x.3), e.g. QoS requirements (e.g. 5QI, QoE of different QoS). - A list of target QoS parameter set(s) and the associated PCC rule identifier, and optional the candidate values of one or more individual QoS parameters in the QoS parameter set(s). - The expecting QoE / MOS associated to each targeting QoS parameter set(s), including the lowest / minimum / maximum / variance / average service experience level / quality / QoE / MOS, the range of the acceptable QoE / MOS (e.g. N <MOS< M). The NWDAF may only notify the consumer of the QoS parameter set that can satisfy the service quality requirement. The expecting QoE / MOS associated to each targeting QoS parameter set(s) could be also the reporting threshold of this analytics ID. - An Analytics target period indicates the time period over which the statistics or predictions are requested. - In a subscription, the Notification Correlation Id and the Notification Target Address are included. - Optionally, preferred level of accuracy of the analytics. - Optionally, preferred level of accuracy per analytics subset (see clause 6.x.3). - Optionally, preferred order of results for the list of QoE associated to QoS: - ordering criterion: "QoE associated to QoS", - order: ascending or descending. - Optionally, Reporting Thresholds, which apply only for subscriptions and indicate conditions on the levels to be reached for the respective analytics subsets (see 5 clause 6.X.3). 6.X.2 Input Data The NWDAF supporting analytics on candidate QoS shall be able to collect information from AF, QAM and 5GC NFs. The input data collect from AF defined for Observed Service Experience related network data 10 analytics in Table 6.4.2-1 is reused. In addition to the data in Table 6.4.2-1 and Table 6.4.2-1a, other information collected by the NWDAF from the AF is defined in the Table 6.X.2-1. The information collected by the NWDAF from relevant 5GC NFs (i.e. UPF, SMF, AMF, PCF) is defined in Table 6.X.2-2. The input data collected from OAM for E2E data volume transfer time analytics in Table 6.18.2-15 1 can be reused. Table 6.X.2-1: Input data from AF related to QoS and policy assistance analytics Information Source Description Application ID AF Identifier of the application at the AF. UE ID AF The list of UE IDs that are associated to the service flows / candidate QoS with the Service Experience value(s). When the AF is untrusted, GPSIs will be provided. When the AF is trusted SUPIs will be provided. QoS reference AF The (pre-defined) QoS information of the service flow associated to the application ID to present the service requirement of the AF. QoS parameters AF Individual QoS parameters of the flow associated to the application ID to present the service requirement of the AF, i.e. Requested Priority, Maximum Burst Size, Requested 5GS Delay, Requested Maximum Bitrate, Requested Guaranteed Bitrate and Requested Packet Error Rate. Time window AF The time window to apply the QoS parameters. Alternative service requirements AF Indicate a list of preference of the QoS parameters sets in prioritized order with which the service can operate. Each Requested Alternative QoS Parameter Set is comprised of the following individual parameters: Requested 5GS Delay, Requested Guaranteed Flow Bitrate and Requested Packet Error Rate. Each requested Alternative QoS Parameter Set may also include a Maximum Burst Size parameter, as described in clause 6.1.3.22 of TS 23.503 [4]). Expecting service experience AF The expecting or required service experience (e.g. MOS, QoE) of the service flow associated to the application ID. Averaging Window AF The value of the averaging window for deriving individual QoS parameters for GBR QoS Flows. Table 6.X.2-2: Input data from 5GC NF related to QoS and policy assistance analytics Information Source Description PCC rule / QoS policy PCF The content of PCC rule / QoS policy, as defined in Table 6.3.1 ofTS 23.503 [4], PCC rule identifier PCF The identifier of the PCC rule. QoS parameter set(s) PCF, SMF, PCF The QoS parameter set(s) deployed into 5GS. The QoS parameter set(s) including individual QoS parameters and QoS characteristics as defined in TS 23.501. e.g. 5QI, ARP / Priority Level, RQA, Alternative QoS Profiles / parameters, Flow Bit Rates, GFBR.MFBR, Aggregate Bit Rates, Session-AMBR, UE-AMBR, UE-Slice-MBR, Default values, Packet Loss Rate, Resource type / QoS flow type, Packet Delay Budget, Packet Error Rate Averaging Window, Maximum Data Burst Volume Packet Filter Set, PDU Set QoS Parameters, etc. QoS profile ID SMF, UPF The identifier of the QoS profile associated to the QoS flow / PCC rule. QoS profile SMF, UPF The QoS profile associated to the QoS flow / PCC rule. 5QI PCF, SMF, UPF The 5QI / reference of the QoS parameters and QoS characteristics. Could be standardised and nonstandardised 5Qls. Active duration of QoS PCF, SMF, UPF The active / applicable duration of the QoS / policy. PDU session ID SMF, UPF PDU session ID PDU Session Type SMF, UPF The type of the PDU session, i.e. Ethernet PDU Session Type and IP PDU Session Type. Default values PCF, SMF, UDM The default values of QoS parameters of the PDU session. QFI SMF, UPF The QFI associated to the PCC rule / QoS parameter set / profile. Time stamp PCF, SMF, UPF The time stamp associated to the collected data. Averaging time window PCF, SMF, UPF The averaging window used to measure the parameters, e.g. data rate, data volume. The averaging window might be a standardized value. Start time and end time UPF Start time and end time of the measurement. UE location AMF, GMLC, LCS The location of the corresponding UE, e.g. TA or cells that the UE enters, the location in a finer granularity than cell level. Service data of QoS related parameters and characteristics SMF, UPF, PCF, QAM Service data of QoS related parameters and characteristics, e.g. Real time measurement (based on QoS monitoring), > Congestion information The UL and / or DL QoS Flow congestion information. > jitter information The N6 jitter information for UL / DL collected from UPF. > Data rate / flow bit rate UL and / or DL data rate per QoS flow / UE at the PSA UPF and it can be applied to a Non-GBR or GBR QoS flow. Could be data rate between UE and RAN, UE and UPF, UPF and RAN. > Traffic delay E.g. QoS flow Packet Delay for UL / DL / Round trip collected from UPF, delay between UE and RAN, UE and UPF, UPF and RAN collected from QAM. > data volume / throughput Measured UL / DL / overall data traffic volume / throughput for the flow of the UE. > packet loss rate The Maximum / average Packet Loss Rate of UL and / or DL. Table 6.X.2-3: Input data from OAM related to QoS and policy assistance analytics, same as Table 6.18.2-1: Input data from OAM related to E2E data volume transfer time in TS 23.288 Information Source Description RAN part delay for DL and UL OAM (See NOTE 2) Average packet transmission delay through the RAN part to the UE per 5QI and per S-NSSAI as specified in clauses 6.3.1.2.1 and 6.3.1.7.1 of TS 28.554

[10] and per UE level per supported S-NSSAI and per QoS level in clauses 6.3.1.1.1 and 6.3.1.1.6 of TS 28.558

[50] , Timestamp OAM A time stamp associated with the collected information. RAN Throughput for DL and UL OAM (see NOTE 1) The per UE measurement of the throughput for DL and UL as specified in clauses 5.2.1.1 and 5.4.1.1 of TS 37.320

[20] , RAN Packet delay for DL and UL OAM (see NOTE 1) The per UE measurement of the packet delay for DL and UL, including per DRB per UE packet delay as specified in clause 5.4.1.1 ofTS 37.320(20], RAN Packet loss rate for DL and UL OAM (see NOTE1, NOTE 2) The per UE measurement of the packet loss rate for DL and UL, including per DRB per UE packet loss rate as specified in clause 5.4.1.1 of TS 37.320

[20] and packet loss rate per UE per QoS level and per supported S-NSSAI in clauses 6.3.1.2.1 and 6.3.1.3.1 of TS 28.558

[50] , Average UL / DL packet delay between PSA UPF and UE OAM (See NOTE 2) The average of UL / DL packet delay between PSA UPF and UE per S-NSSAI as specified in clauses 5.4.9.1.1 and 5.4.9.2.1 of TS 28.552 [8] and per UE level per supported S-NSSAI and per QoS level in clauses 6.2.2.1.1 and 6.2.2.1.3 of TS 28.558

[50] , Average UL / DL Packet delay between PSA UPF and RAN OAM (See NOTE 2) The per UE level per supported S-NSSAI and per QoS level of the average UL / DL packet delay between PSA UPF and RAN as specified in clauses 6.2.2.1.4 and 6.2.2.1.5 ofTS 28.558

[50] , Average DL / UL UE throughput in gNB OAM (See NOTE 2) Average DL / UL UE throughput in the gNB per QoS level (mapped 5QI) and per S-NSSAI as specified in clauses 5.1.1.3.1 and 5.1.1.3.3 ofTS 28.552 [8] and per UE per supported S-NSSAI and per QoS level clauses 6.3.1.4.1 and 6.3.1.4.2 ofTS 28.558

[50] NOTE 1: Per UE measurement for a specific UE from OAM (via MDT), is as specified in clause 6.2.3.1 in TS 37.230

[20] , NOTE 2: In addition to the average KPIs, per UE level measurements if available, can be taken into account by the NWDAF. 6.X.3 Output Analytics 5 The NWDAF supporting analytics on candidate QoS provides the analytics results to consumer NFs, e.g. PCF or AF. The analytics results provided by the NWDAF could be candidate QoS statistics as defined in Table 6.X.3-1 or predictions as defined in table 6.X.3-2. Table 6.X.3-1: Service experience associated of candidate QoS Information Description UE ID or list of UE IDs (1..SUPImax) Identifies the UE(s)for which the statistic applies by a list of SUPIs. Time slot entry (1..max) List of time slots during the Analytics target period. > Time slot start Time slot start within the Analytics target period. > Duration Duration of the time slot. > Service experience information of candidate QoS (1...max) (NOTE 1) Service experience information of a list of candidate QoS, e.g. The service experience of user(s) / UEs. The list of candidate QoS is indicated in the consumer request. Max. is the number of the QoS parameter set(s), if applicable. » DNN DNN for the PDU Session which contains the QoS flow. » S-NSSAI Identifies the Network Slice used to access the application. » RAT Type Indicate the list of RAT types for which the Service experience information of candidate QoS applies. » Access Type Access Type when the UE establishes a PDU Session for the AF. » UE location Indicate the UE location information when the service is delivered. » PDU session ID The PDU session of the QoS flow associated to the PCC rule / QoS parameters belongs to. » PDU Session Type The type of the PDU session, i.e. Ethernet PDU Session Type and IP PDU Session Type. » QFI QoS Flow Identifier. The QoS flow that associated to the PCC rule / QoS parameters. » Application ID(s) Identifies the application(s) that associated to the PCC rule or QoS. » Access Type Access Type when the UE establishes a PDU Session for the AF(s). » PCC rule identifier The identifier of the PCC rule associated to the QoS parameters. » QoS service experience The service experience (e.g. QoE, MOS) of the corresponding QoS parameter set (e.g. average, peak, maximum, minimum, variance). » QoS service experience variation The variation / variance of the QoS service experience (e.g. QoE, MOS) within the time window or time slot. If the variation / variance of the » valid duration of QoS service experience The time window or time slot / duration that is associated to the QoS service experience. » data volume The UL / DL / overall data volume of the QoS flow within the valid duration. » candidate QoS parameters and characteristics The values of one or more individual QoS parameters within the QoS parameter set. »> 5QI The reference to 5G QoS characteristics / parameter sets. »> ARP / Priority Level The QoS parameter ARP contains information about the priority level, the preemption capability and the pre-emption vulnerability, as defined in TS 23.501 (21. »> RQA (NOTE 4) Reflective QoS Attribute (RQA) only applies to Reflective QoS. The Reflective QoS Attribute (RQA) is an optional parameter which indicates that certain traffic (not necessarily all) carried on this QoS Flow is subject to Reflective QoS, as defined in TS 23.501 [2], »> Notification control »> Alternative QoS Profiles / parameters The alternative QoS Profiles / parameters of the QoS flow. »> Flow Bit Rates (NOTE 2) The flow bit rates only applies to GBR QoS Flow. »» GFBR Guaranteed Flow Bit Rate (GFBR) for UL and / or DL. »» MFBR Maximum Flow Bit Rate (MFBR) for UL and / or DL. »> Aggregate Bit Rates (NOTE 2) The aggregate bit rate of PDU session, UE, or slice, s »» Session-AMBR The aggregate bit rate limit of the corresponding PDU Session of the UE. »» UE-AMBR The aggregate bit rate limit of the corresponding UE. »» UE-Slice-MBR The aggregate bit rate limit of each group of PDU Sessions of the UE for the same slice (S-NSSAI). »> Default values Optimised default QoS parameters for PDU session establishment or modification. »> Packet Loss Rate (NOTE 2) The Maximum Packet Loss Rate (UL, DL) indicates the maximum rate for lost packets of the QoS Flow that can be tolerated in the uplink and downlink direction. This is provided to the QoS Flow if it is compliant to the GFBR »> Resource type / QoS flow type The resource type of the corresponding QoS flow, e.g. GBR QoS flow, non-GBR QoS flow, delay-critical QoS flow. »> Packet Delay Budget Packet Delay Budget (PDB) indicates the upper bound for the time that a packet may be delayed between the UE and the N6 termination point at the UPF, as defined in TS 23.501 [2], »> Packet Error Rate Packet Error Rate (PER) defines an upper bound for a rate of non-congestion related packet losses, as defined in TS 23.501 [2], »> Averaging Window (NOTE 2) The Averaging window is applied when the resource type is GBR QoS. The Averaging window represents the duration over which the GFBR and MFBR shall be calculated (e.g. in the (R)AN, UPF, UE), as defined in TS 23.501 [2], »> Maximum Data Burst Volume (NOTE 3) The Maximum Data Burst Volume (MDBV)applies to GBR QoS Flow with Delay-critical resource type. The MDBV denotes the largest amount of data that the 5G-AN is required to serve within a period of 5G-AN PDB, as defined in TS 23.501 [2], »> Packet Filter Set The Packet Filter Set is used in the QoS rule and the PDR to identify one or more packet (IP or Ethernet) flow(s), including IP Packet Filter Set (as defined in clause 5.7.6.2 of TS 23.501 [2]) and Ethernet Packet Filter Set (as defined in clause 5.7.6.3 of TS 23.501 [2]). »» PDU Set QoS Parameters As defined in clause 5.7.7 of TS 23.501 [2], the PDU Set QoS Parameters are used to support PDU Set based QoS handling in the NG-RAN, including PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), PDU Set Integrated Handling Information (PSIHI). » Validity period The validity period within the time slot for the xxxxx statistics as defined in clause 6.1.3. » Spatial validity Area where the xxxx statistics applies. NOTE 1: Analytics subset that can be used in "list of analytics subsets that are requested", "Preferred level of accuracy per analytics subset" and "Reporting Thresholds". NOTE 2: The output analytics only applies to GBR QoS Flow. NOTE 3: The output analytics only applies to GBR QoS Flow with Delay-critical resource type. NOTE 4: The output analytics only applies to Reflective QoS. 6.x.4 Procedures The NWDAF may provide the analytics of QoS and policy assistance analytics to a consumer 5GC NF (e.g. PCF). Referring to Figure 2: 5 1. The Consumer NF, e.g. PCF or AF, requests or subscribes to analytics for QoS and policy assistance analytics analytics from NWDAF (possibly via NEF in case the consumer NF is an untrusted AF) and provides the input information as specified in clause 6.x. 1 to 5GC. 2a. The NWDAF may subscribe to the service data from AMF as defined in Table 6.X.2-2 10 using Namf_EventExposure_Subscribe service operation for collecting UE location(s) for a UE or a group of UEs. NOTE: If NWDAF requires UE location information with finer granularity than TA / cell level, then NWDAF collects the location data from GMLC instead of AMF. 2b. The NWDAF may subscribe to service data from PCF as defined in Table 6.X.2-2 by 15 invoking Npcf_EventExposure_Subscribe service operation (Event ID, PCC rule ID, SUPI(s) or Application ID). 2c-1. The NWDAF may subscribe to service data from SMF as defined in Table 6.x.2-2 by invoking Nsmf_EventExposure_Subscribe service operation (Event ID, QoS profile ID, PCC rule ID, SLIPI(s) or Application ID). 2d. In order to provide the QoS flow Packet delay to NWDAF the SMF subscribe to QoS Monitoring information from UPF, as defined in Table 6.X.2-2, using the N4 Session level Reporting procedure defined in TS 23.502 [3], 2e. The subscribed event is triggered in the UPF. 2c-2. The SMF notifies the NWDAF of the subscribed service data. 2f. Alternatively, the UPF may notify the subscribed event report directly to the NWDAF. 2g. The NWDAF may subscribe to the service data from as defined AF in the Table 6.x-2-1 by invoking Nnef_EventExposure_Subscribe or Naf_EventExposure_Subscribe (Event ID = QoS and policy assistance analytics, Application ID, Event Filter information, Target of Event Reporting = UE ID(s)) service as defined in TS 23.502 [3], 2h. The NWDAF may subscribe to the input data from the QAM as defined in the Table 6.18.2-1 according to the data collection principles described in clause 6.2.3. 3. The NWDAF derives the requested analytics on QoS and policy assistance analytics. 4. The NWDAF provides the requested QoS and policy assistance analytics to the consumer NF, using either Nnwdaf_Analyticslnfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1. 5-7. If the consumer NF subscribed to QoS and policy assistance analytics in step 1, once the NWDAF generates new analytics for QoS and policy assistance analytics, it provides a notification using Nnwdaf_AnalyticsSubscription_Notify to the Consumer NF. Consumer behaviours of using the QoS flow and QoS service experience related analytics If PCF is the consumer of NWDAF analytics When the PCF is used as an example of the consumer: based on the QoS flow related analytics, the PCF is aware of the usage information of different policies / QoS / QoS flows, and optionally the service experience of the users or applications. Then the PCF may take different actions to enhance the user experience by modifying the QoS / policy configuration: • The PCF may determine to release / optimise the QoS policy (and any related parameters and configurations) that are used less frequently and result in low service experience / quality, to save resources and optimise the NW performance. • The PCF may determine to steer traffic of some services from the less frequently used and low service experience QoS to the better QoS flows and modify the policy / PCC rules of the corresponding services / flows. • The PCF may modify the QoS / PCC rules of the less frequently used and low service experience QoS flows to improve service experience; • The PCF may establish new / modify QoS flows by deploying the QoS / PCC rules that are in higher ranking, e.g. used more frequently and with higher service experience. • The PCF may determine the modify / determine the default QoS rule of a PDU session to the one that was / to be used more frequently, can satisfy the most of / all the services experience requirements (e.g. QoE) transmitted via this PDU session or QoS flow. • The PCF determines to generate new / duplicate the policy that was / to be used more frequently and can satisfy the most of / all the services experience requirements to establish new QoS flow or modified the existing QoS flow. The classified usage classes of QoS can help the PCF to understand the applied frequency / level of the corresponding QoS, e.g. High-, medium-, low- usage frequency or duration of the corresponding QoS flow / QoS profile / QoS parameters / policy (e.g. PCC rule) for the service flows (e.g. for data / service transmission for UE or application). Alternatively, the ranking of the QoS (e.g. QoS flow / QoS profile / QoS parameter / policy etc.) can be provided to the PCF implicitly or explicitly. • The NWDAF may include the ranking in the output analytics, e.g. the ranking is from 1 to the max. Number of QoS flows / policies / QoS profiles / parameters. Rank 1 means this QoS flow / QoS profile / QoS parameter / policy is the most frequent used and / or longest duration of the QoS, rank max. means the least frequent used one and / or the shortest duration; or another way around. • Or the consumer may indicate the preferred order of results for the list of QoS (Flows). Then the NWDAF will provide the outputs in the order as required by the consumer. See above under the heading “Interaction between NWDAF and service consumer”. Validity period and spatial validity of the QoS flow related Statistics and prediction should be provided by NWDAF. The PCF may requires multiple analytics IDs to assist the policy determination or modification. Those analytics should be valid for the same Validity period and Spatial validity or the Validity period and Spatial validity should overlap. The policy determined by the PCF by taking the analytics IDs into account will be valid during the (overlapped) Validity period and in the area of (overlapped) spatial validity of multiple analytics IDs. The analytics IDs may include: • QoS flow related analytics • UE communication analytics • QoS Sustainability analytics • Observed Service experience analytics The PCF may interact with SMF and then UPF to notify the determined or updated QoS to apply the QoS within the communication system. The corresponding QoS and policy enforcement will be also performed based on the determined or updated QoS. The determined or updated QoS will be also delivered to based station and UE for traffic transmission. If the AF is the consumer of the QoS flow analytics: based on the output analytics, the AF is aware of the statistics and the prediction of performance of different QoS flow. Therefore, the AF will take the QoS flow performance information into account to generate more reasonable service requirements on the communication system. As the result, the AF service requirements (e.g. expecting QoE, qos parameters) will be more likely to be authorised by the PCF. And the AF services could be transmitted via the communication system in a more service quality guaranteed manner. The accompanying annex to this description (“Change Request”) discloses example modifications to the existing 3GPP standard to incorporate one or more of the techniques described herein. Figure 3 is a block diagram of an exemplary network entity that may be used in examples of the present disclosure. For example, a UE / network entity (e.g. AMF, SMF, NWDAF) I base station (e.g. eNB, gNB) in the examples of Figures 1 and 2 may comprise an entity of Figure 3. The skilled person will appreciate that a network entity may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure. The entity 300 comprises a processor (or controller) 301, a transmitter 303 and a receiver 305. The receiver 305 is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter 303 is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor 301 is configured for performing one or more operations, for example according to the operations as described above. Figure 4 illustrates a method of a PCF entity (e.g. PCF) according to an example of the present disclosure. The method may be performed by an entity as described in FIG. 3. In operation S410, the PCF entity requests or subscribes to analytics relating to QoS from an NWDAF entity (e.g. NWDAF). The request or subscription indicates one or more QoS parameter set. Each QoS parameter set includes at least one parameter and, for each of the at least one parameter, a value for said parameter. The at least one parameter includes at least one of: 5QI, one or more QoS characteristics, guaranteed flow bit rate (GFBR) or maximum flow bit rate (MFBR). In operation S420, the PCF entity receives, from the NWDAF entity, analytics results relating to QoS and comprising service experience information comprising one or more candidate QoS parameter set. Figure 5 illustrates a method of an NWDAF entity (e.g. NWDAF) according to an example of the present disclosure. The method may be performed by an entity as described in FIG. 3. In operation S510, the NWDAF entity receives, from a PCF entity (e.g. PCF), a request or subscription to analytics relating to QoS from an NWDAF entity (e.g. NWDAF). The request or subscription indicates one or more QoS parameter set. Each QoS parameter set includes at least one parameter and, for each of the at least one parameter, a value for said parameter. The at least one parameter includes at least one of: 5QI, one or more QoS characteristics, guaranteed flow bit rate (GFBR) or maximum flow bit rate (MFBR). In operation S520, the NWDAF entity provides, to the PCF entity, analytics results relating to QoS and comprising service experience information comprising one or more candidate QoS parameter set. The techniques described herein may be implemented using any suitably configured apparatus and / or system. Such an apparatus and / or system may be configured to perform a method according to any aspect, embodiment, example or claim disclosed herein. Such an apparatus may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). The one or more elements may be implemented in the form of hardware, software, or any combination of hardware and software. It will be appreciated that examples of the present disclosure may be implemented in the form of hardware, software or any combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example a storage device like a ROM, whether erasable or rewritable or not, or in the form of memory such as, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a CD, DVD, magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising 5 instructions that, when executed, implement certain examples of the present disclosure. Accordingly, certain examples provide a program comprising code for implementing a method, apparatus or system according to any example, embodiment, aspect and / or claim disclosed herein, and / or a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium, for example a communication 10 signal carried over a wired or wireless connection. While the invention has been shown and described with reference to certain examples, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention, as defined by the appended claims. Definitions / Acronyms In the present disclosure, the following acronyms / definitions may be used. Other acronyms may be defined in accordance with the 3GPP 5G and other relevant standards at the filing date of the present application. 3GPP 3rd Generation Partnership Project 3G 3rd Generation 4G 4th Generation 5G 5th Generation 6G 6th Generation 5GS 5G System 5QI 5G QoS Identifier AI / ML Artificial Intelligence / Machine Learning AMF Access and Mobility Management Function ARP Allocation and Retention Priority CN Core Network DRB Data Radio Bearer eNB Base Station FTP File Transfer Protocol GBR Guaranteed Bit Rate GFBR Guaranteed Flow Bit Rate gNB 5G Base Station IE Information Element MC-PTT Mission Critical Push To Talk MFBR Maximum Flow Bit Rate ms milliseconds N3IWF non-3GPP Interworking Function NAS Non Access Stratum NG Next Generation NG Interface between RAN and CN NR New Radio NWDAF Network Data Analytics Function P2P Peer-to-Peer PCF Policy Control Function PDU Protocol Data Unit QFI QoS Flow Identifier QoE Quality of Experience QoS Quality of Service RAN Radio Access Network RRC Radio Resource Control RSU Roadside Unit S1 Interface between RAN and CN SIB System Information Block SMF Session Management Function TCP Transmission Control Protocol TR Technical Report TS Technical Specification UDM Unified Data Management UE User Equipment UPF User Plane Function URLLC Ultra-Reliable Low Latency Communications V2X Vehicle to Everything 3GPP TSG-SA2 Meeting #164 S2-240xxx 19 - 23 August, 2024, Maastricht, Netherlands rewssow CHANGE REQUEST CR-Form-v12.1 23.288 CR H rev - Current version: 18.6.0 For HELP on using this form: comprehensive instructions can be found at http: / / www. 3qpp. ora'Chanoe-Regi^sts. Proposed change affects: UICC apps| | ME| | Radio Access Network! I Core Networkrx] Title: Support of QoS and policy assistance analytics Source to WG; Source to TSG: Work item code: Samsung SA2 AIML_CN Date: 2024-08-09 Category: B Release: Re I-19 Use one of the following categories: Use one of the following releases: F (correction) Rei-8 (Released) A (mirror corresponding to a change in an earlier Rel-9 (Release 9) release) Rei-10 (Release 10) B (addition of feature), Rel-11 (Release 11) C (functional modification of feature) D (editorial modification) Rei-15 (Release 15) Detailed explanations of the above categories can Rel-16 (Release 16) be found in 3GPP TR 21.900. Rel-17 (Release 17) Rel-18 (Release 18) Reason for change: Summary of change: Consequences if not approved: Clauses affected: 6.x (new), 6.x.1 (new), 6.x.2 (new), 6.X.3 (new), 6.X.4 (new), 7.1 Other specs affected: (show related CRs) Y N Other core specifications TS / TR ... CR ... Test specifications TS / TR ... CR ... O&M Specifications TS / TR ... CR ... X X X Other comments: This CR's revision history: Input Data .Xt*£h&uL4fdfQQ2Ux£jLfr£i»A£jv£-&Qx^ and Table 6.4,2-la is reused, In addition io rhe data in Table 6.4.2-1 and 'Table 6.4.2-la, other inibnuation collected by the NWDAF from rhe AF is defined in die Table 6.L The bdlnmauon collected by the NWDAF from mlevam. 5GC MFs. (i.e. UPF, SAIF, AMF, PCI7) is defined hr Table 2hAi:mA.dAmW.b4mWGoQ.QAV fm.hFh.dW^ Table J - x. :, j PTdj t data fro m. AF related. to .an 11 £Q j ; c v_ aaslsta In fora m don Information Source Dsseaipbori Application iD AF identifier of the twiication et the AF. AF ThsJaioWiLlQlLFMStS^si^ciaF^ When the AF: is urAusteci, GFFis w.|; be provided When the AF is rrustod SUPis wii: be orovicAd. QoS reference AA Trie ;ore-defined) QoS infonTiation of tne service iiow aescoiated to Fie appiicat^ri iD to present the sendee repiA ement of the AF. QoS parameters AA individual QoS parameter s of trie flow associated to the aobiioation :Q to present the service resuiremenr of the AF. CQbQiQ^ AA Trie active duration of the QoS. Alter 1 jatjye Qo S AA indicate a list of preference of trie QoS parameters sets in oriodtized. other with ydii^ Fxos&U^^ AF Tfie expectiitp.orFeouiited ser;tice.ezoeriej3pefecT.. MQG. QoFl of tiie service fiow associated to tine application iO Aye; as i r 1¾ Wi r rd o w — TheAislLbiFddT^Liai^diSSi^^ QoS parameters for GBP QoS Fiows. Tabta 6.X.2-2: inptif data from 5GC related to QoS anrf poiicy assistance information 6.X.3 Output Analytics The NWDAF on service experience associated to QoS results to consumer NFs. ¢.¾. PCF o.t AF. as delmed in Table 6.a.3-1. Tabie S.x.S-1: QoS and Policy Assistance analytics ^formation Description UE :D or Hsr or UE IDs (•'..SUPImax! identifies the UPQ) Or * n:ch the statistic applies by a list of SUPIs Time sic- eritry 0 rcaxt > Time slot start > Duration > Service experience -1-1,-.1::1-.1-. -.i !;<-•> ,•-.-! , -n-.-li.'-ijitL. <>1’< 1-.ir-.irngt,-Jr ^STS) information! associated to > and ai-owed values of oamTd^ (NOTE Q PPlicable. » DNN >> S-NSSAi > r* <X A : : V PS \ information of >> Access Tvoe rvop wn?n fhr.' : A :--1-2(-1-0-20^ PI; । s^-c^ii'in for too Ah >> Access Type » UE iocation -ed. dQQEXPmAsim^ RuRpara^ SgssjonType » QFl QoS Flow identifier, The QoS flow that associated to the ROC ruie / QoS parameters. » Application !Dfs) identities the aooi-cation S; that associated to the ROC rule or QoS. » POO rule idenhfier The identifier of the POU ruie associated to ths QoS parameters. JJUQQQRss^ The secm^ey^ te n. average maximum ^QlJ^oih^OSNjijQadAtE^ minimum, variance) JGuUjaEi^^ experience Th r^d u t tat se r y i eg -Oxperisrice.of.ttis QoSJsAcilid.. >> Data. volume The U: / DL / oveml- data v olume of the QoS flow withirr ths vaiid dur ation. kUJOTObadmOoS parameter set ar-d characteristics Ths^YaDeo^fj^n^^ ejndiUdijcddQCiLSEIEnit^^ >» 5QI Ret!s^AAOuo§L^SJt^iJt^ ndiygtes that u - u G Receptive parameters ATT- Blow Bit Rates (NOTE: 2- »» GEER »» MFER >» Ac^recjate Bit Rates (NOTE 2: 1 M^f-s R’-j*^ as Pats (I -!i DI "j indicates ths maximum rate for lost packets INOTE2- a<X4U !! ! 1! !C iK <r<! «U ’,4’..''.-V> ■!!< 1*. '>j!! «. >» Resource tvpe >» Packet Delay Eudqei >» Packet :"rror Rate- de of non-conaestion related k^QQAG^T^SiilGGXQQiQ (NOTEz; QS.GJ3R QcS: ilihe^HcRandJ^^ >>> Maxviium Data Durst \ GrAbl-tgJgsnifOdjto serve .. .-.■..-. . . .-. .-. .-.V. .. .. .'. .-. .'. — .. .V. .-.-..4 .-. .-. — .LV.V. 6.x. 4 Procedures Service Consumer: 1 / Nnwdaf_Ar alyticsSubscriptlan_Subscri x! Nnwd at_Anal- trcslnto_ Request (AnalytlcslDyServiceExperlence Assoc atedto: i Commented [DGE1]: A number of steps need to be marked as optional (i e dotted line), e g >tep 2b. step 2c-2. step 2f : Commented [DGE2]: Siep 2e should be ini Pl1' Filters- QoS; QoE;Aol, Etc j: 2a / Na:rrrf_EventExposure_Si. bscrib e / : :Namf EventExposure Notify: : / / / / / / / _li IIpi t_E r-ritE |m hih_ ii) rppp Up, t_E r-ntE pH ni-Jliitrt : .'I I 1-1-11111 I.VI.'IIII -1111-.1111- •jbscribe: : ^c-2 Nsmt- EventExoosure F otify: / 2fNupf_EventExposu re_Not|f / : 2d: Subscribe event via N4 Session Reporting: Rule :2g :Naf_EventExposure_<Subf cribe: / :Nat_EventExposure_'lotiiV ,'i- : -iiirj iini'ii ivi'in r. imnn111 and QAM: : 2b; Data coiieaionfromQAM : response:::: Is NWDAF derives I. II I. IIVIII 4 Nnwd<-_Analvticslnto_Re quest Re sponse / :Nnwdaf_4nalyticsSubscription Not(fy' ::::: / / Ba / Namf JEvehtExpOSure_M^ 5 Narrf / Npcf / Nsrrf / Nupf / Naf_EventExposure received or QAM data collected 16 NWDAF derives :|new analytics 1: Nnwdaf_AnalyticsSubscript on_Notify: i Commented [DGE3]: l |Khnc he NWDAF derives rhe requested analytics o;. Service ExpeHe^ce Associated to QoS. used in step 1. * * *Next Change * * * 7.1 General Table 7.1-1 illustrates the NWDAF Services. Table 7.1-1: NF services provided by NWDAF Service Name Service Operations Operation Semantics Example Consumers) Nnwdaf_AnalyticsSubscri ption Subscribe Subscribe / Notify PCF, NSSF, AMF, SMF, NEF, AF, OAM, CEF, NWDAF, DCCF, LMF Unsubscribe PCF, NSSF, AMF, SMF, NEF, AF, OAM, CEF, NWDAF, DCCF, LMF Notify PCF, NSSF, AMF, SMF, NEF, AF, OAM, CEF, NWDAF, DCCF, MFAF, LMF Transfer Request / Response NWDAF Nnwdaf_Analyticslnfo Request Request / Response PCF, NSSF, AMF, SMF, NEF, AF, OAM, CEF, NWDAF, DCCF, LMF ContextTransfer Request / Response NWDAF Nnwdaf_DataManagement Subscribe Subscribe / Notify NWDAF, DCCF Notify NWDAF, DCCF, MFAF, ADRF Fetch Request / Response NWDAF, DCCF, MFAF, ADRF Nnwdaf_MLModelProvision Subscribe Subscribe / Notify NWDAF Unsubscribe NWDAF Notify NWDAF Nnwdaf MLModellnfo Request Request / Response NWDAF Nnwdaf_MLModelMonitor Subscribe Subscribe / Notify NWDAF Unsubscribe NWDAF Notify NWDAF Register Request / Response NWDAF Request NWDAF Nnwdaf_MLModelTraining Subscribe Subscribe / Notify NWDAF Unsubscribe NWDAF Notify NWDAF Nnwdaf MLModelTraininglnfo Request Request / Response NWDAF Nnwdaf_RoamingAnalytics Subscribe Subscribe / Notify H-RE-NWDAF, V-RE-NWDAF Unsubscribe H-RE-NWDAF, V-RE-NWDAF Notify H-RE-NWDAF, V-RE-NWDAF Request Request / Response H-RE-NWDAF, V-RE-NWDAF N nwdaf_Roa mi ng Data Subscribe Subscribe / Notify H-RE-NWDAF, V-RE- NWDAF Unsubscribe H-RE-NWDAF, V-RE-NWDAF Notify H-RE-NWDAF, V-RE-NWDAF NOTE 1: How OAM consumes Nnwdaf services and which Analytics information is relevant is defined in TS 28.550 [7] Annex H and out of the scope of this TS. NOTE 2: How CEF consumes Nnwdaf services and which Analytics information is relevant is defined in TS 28.201

[21] and out of the scope of this TS. NOTE 3: The Nnwdaf_MLModelProvision service and the Nnwdaf_MLModellnfo service are provided by an NWDAF containing MTLF and consumed by an NWDAF containing AnLF or provided by an NWDAF containing MTLF supporting FL as a server and consumed by an NWDAF containing MTLF. Table 7.1-2 shows the analytics information provided by NWDAF service. Table 7.1-2: Analytics information provided by NWDAF Analytics Information Request Description Response Description Slice Load level information Analytics ID: load level information Load level provided as number of UE registrations and number of PDU sessions for a Network Slice and Network Slice instances as well as resource utilization for Network Slice instances. Observed Service experience information Analytics ID: Service Experience Observed Service experience statistics or predictions may be provided for a Network Slice or an Application. They may be derived from an individual UE, a group of UEs or any UE. For slice service experience, they may be derived from an Application, a set of Applications or all Applications on the Network Slice. NF Load information Analytics ID: NF load information Load statistics or predictions information for specific NF(s). Network Performance information Analytics ID: Network Performance Statistics or predictions on the load in an Area of Interest; in addition, statistics or predictions on the number of UEs that are located in that Area of Interest. UE mobility information Analytics ID: UE Mobility Statistics or predictions on UE mobility. When visited AOI(s) is included in the Analytics Filter information, only statistics on UE mobility can be provided. UE Communication information Analytics ID: UE Communication Statistics or predictions on UE communication. Expected UE behavioural parameters Analytics ID: UE Mobility and / or UE Communication Analytics on UE Mobility and / or UE Communication. UE Abnormal behaviour information Analytics ID: Abnormal behaviour List of observed or expected exceptions, with Exception ID, Exception Level and other information, depending on the observed or expected exceptions. End-to-end data volume transfer time Analytics ID: E2E data volume transfer time Analytics on E2E data volume transfer time. User Data Congestion information Analytics ID: User Data Congestion Statistics or predictions on the user data congestion for transfer over the user plane, for transfer over the control plane, or for both. QoS Sustainability Analytics ID: QoS Sustainability For statistics, the information on the location and the time for the QoS change and the threshold(s) that were crossed; or, for predictions, the information on the location and the time when a potential QoS change may occur and what threshold(s) may be crossed. Session Management Congestion Control Experience Analytics ID: Session Management Congestion Control Experience Statistics on session management congestion control experience for specific DNN and / or S-NSSAI. Redundant Transmission Experience Analytics ID: Redundant Transmission Experience Statistics or predictions aimed at supporting redundant transmission decisions for URLLC services. WLAN performance Analytics ID: WLAN performance Statistics or predictions on WLAN performance of UE. Dispersion Analytics ID: UE Dispersion Statistics or predictions that identify the location (i.e. areas of interest) or network slice(s) where a UE, or a group of UEs disperse their data volume, or disperse mobility or session management transactions or both. DN Performance Analytics ID: DN Performance Statistics or predictions on user plane performance for a specific Edge Computing application. PFD Determination Analytics ID: PFD Determination Statistics on PFD information for a known application identifier(s). Movement Behaviour Analytics ID: Movement Behaviour Statistics or predictions on movement behaviour for an applicable area. Location Accuracy Analytics ID: Location Accuracy Predictions on Location Accuracy. Relative Proximity Analytics ID: Relative Proximity Statistics or predictions on Relative Proximity among UEs. PDU Session traffic Analytics ID: PDU Session traffic Statistics on whether traffic of UEs via one or multiple PDU sessions is according to the information provided bvthe service consumer. QoS and Policy Analytics ID: QoS and Policy Assistance aS parameter setfs) and * * *Next Change * * * 7.2.2 Nnwdaf_AnalyticsSubscription_Subscribe service operation Service operation name: NnwdafAnalyticsSubscriptionSubscribe Description: Subscribes to NWDAF analytics and optionally Analytics Accuracy Information with specific parameters. Inputs, Required: - (Set of) Analytics ID(s) as defined in Table 7.1-2; - Target of Analytics Reporting; - Notification Target Address (+ Notification Correlation ID); - Analytics Reporting Parameters (including Analytics target period, etc.). NOTE 1: Target of Analytics Reporting can be provided per individual Analytics ID. Inputs, Optional: - Analytics Filter Information; - Time window for historical analytics; Subscription Correlation ID (in the case of modification of the analytics subscription); - Preferred level of accuracy of the analytics; - Preferred level of accuracy per analytics subset; - Reporting Thresholds; - Maximum number of objects requested (max); - Preferred order of results; - Maximum number of SUPIs requested (SUPImax); - Time when analytics information is needed; - Analytics Metadata Request; - (Set of) NWDAF identifiers used by the NWDAF service consumer when aggregating multiple analytic subscriptions; - Dataset Statistical Properties; - Output strategy; - Data time window; - Consumer NF's serving area or NF ID; - Information of previous analytics subscription, i.e. NWDAF identifier (i.e. Instance ID or Set ID), Analytics ID(s) (including SUPIs and Analytics Filter Information for UE-related Analytics) and Subscription Correlation ID; - Use case context. - Analytics Accuracy Request information. - Analytics Feedback Information. NOTE 2: Analytics Filter Information, Reporting Thresholds, maximum number of objects requested (max), maximum number of SUPIs requested (SUPImax), Analytics Metadata Request, Dataset Statistical Properties, Output strategy, Data time window and time when analytics information is needed can be provided per individual Analytics ID. NOTE 3: Analytics Feedback Information only can be included in modification request for the existing analytics subscription. NOTE 4: Other input parameters specific for different analytics ID can be also needed, as specified in the corresponding clause for each analytics ID. param ete Outputs Required: When the subscription is accepted: Subscription Correlation ID (required for management of this subscription). When the subscription is not accepted, an error response. Outputs, Optional: First corresponding Analytics report is included, if available and if analytics consumer requested immediate reporting (see clause 4.15.1 of TS 23.502 [3]). NOTE 5: When the Target of Analytics Reporting is a SUPI or a GPSI then the subscription may not be accepted, e.g. user consent is not granted and an error is sent to the consumer. When the Target of Analytics Reporting is an Internal Group Id, or a list of SUPIs / GPSIs or any UE, no error is sent, but a SUPI or GPSI is skipped if user consent is not granted. * * *Next Change * * * 7.3.2 Nnwdaf_Analyticslnfo_Request service operation Service operation name: Nnwdaf AnalyticsInfo Request Description: The consumer requests NWDAF operator specific analytics and optionally Analytics Accuracy Information. Inputs, Required: (Set of) Analytics ID(s) as defined in Table 7.1-2, Target of Analytics Reporting, Analytics Reporting Parameters (including Analytics target period, etc.). NOTE 1: Target of Analytics Reporting can be provided per individual Analytics ID. Inputs, Optional: Analytics Filter Information, preferred level of accuracy of the analytics, preferred level of accuracy per analytics subset, time when analytics information is needed, maximum number of objects requested (max), preferred order of results, maximum number of SUPIs requested (SUPImax), Analytics Metadata Request, Dataset Statistical Properties, Output strategy, Data time window, Use case context, Time window for historical analytics and Analytics Accuracy Request infonnation,Jarget\QojS parameter setfsk^^^^ NOTE 2: Analytics Filter Information, Maximum number of objects requested (max), Maximum number of SUPIs requested (SUPImax), Analytics Metadata Request, Dataset Statistical Properties, Output strategy, Data time window and time when analytics information is needed can be provided per individual Analytics ID. Outputs, Required: If the request is accepted, then set of the tuple (Analytics ID, Analytics specific parameters). When the request is not accepted, an error response. Outputs, Optional: Timestamp of analytics generation (required when ADRF is deployed), validity period, confidence, revised waiting time, Analytics Metadata Information, Analytics Accuracy Information. See clause 6.1.3. NOTE 3: Validity period can also be provided as part of Analytics specific parameters for some NWDAF output analytics. NOTE 4: When the Target of Analytics Reporting is a SUPI or a GPSI then the request may not be accepted, e.g. user consent is not granted and an error is sent to the consumer. When the Target of Analytics Reporting is an Internal Group Id, or a list of SUPIs / GPSIs or any UE, no error is sent, but a SUPI or GPSI is skipped if user consent is not granted. NOTE 5: Other input or output parameters specific for different analytics ID can be also needed, as specified in the corresponding clause of each analytics * * *End of Changes * * *

Claims

1. A policy control function (PCF) entity configured to:request or subscribe to analytics relating to quality of service (QoS) from an network data analytics function (NWDAF) entity; andreceive, from the NWDAF entity, analytics results relating to QoS and comprising service experience information associated with one or more candidate QoS parameter set;wherein the request or subscription indicates one or more QoS parameter set;wherein each QoS parameter set includes at least one parameter and, for each of the at least one parameter, a value for said parameter; andwherein the at least one parameter includes at least one of: 5G QoS Identified (5QI), one or more QoS characteristics, guaranteed flow bit rate (GFBR) or maximum flow bit rate (MFBR).

2. The PCF entity of claim 1, configured to:based on the analytics results, determine a new policy or QoS for a user equipment (UE), orbased on the analytics results, modify an existing policy or QoS for the UE.

3. The PCF entity of claim 1 or claim 2, wherein the request or subscription further indicates a quality of experience (QoE); andwherein the one or more candidate QoS parameter set satisfy the indicated QoE.

4. The PCF entity of any one of the previous claims, wherein the analytics results include one or more QoE associated with the one or more candidate QoS parameter set.

5. The PCF entity of any one of the previous claims, wherein the request or subscription further indicates one or more of:a preferred order of results for the one or more candidate QoS parameter; oran ordering criterion for one or more QoE associated to the one or more candidate QoS parameter set.

6. The PCF entity of any one of the previous claims, wherein the request or subscription is transmitted to the NWDAF entity via another entity.

7. The PCF entity of any one of the previous claims,wherein the analytics results comprise a duration of a time slot; and / orwherein the service experience information comprises an indication of the one or more candidate QoS parameter set.

8. The PCF entity of any one of the previous claims, wherein the service experience information includes, for each of the one or more candidate QoS parameter set, one or more of:DNN for a protocol data unit (PDU) session which contains a corresponding QoS flow for said candidate QoS parameter set;a list of RAT type(s) for which the information applies;a QoE associated with said candidate QoS parameter set;value(s) of individual parameter(s) in said candidate QoS parameter set;a validity period within the time slot for the analytics results;an area where the analytics results apply; anda valid duration of a corresponding QoS and / or a valid duration of the service experience information.

9. The PCF entity of claim 8, wherein the value(s) of individual parameter(s) for each of the one or more candidate QoS parameter set correspond to one or more of:a priority level;PDB;PER;an averaging window; ora maximum delay burst volume.

10. The PCF entity of any one of the previous claims, configured to:if the PCF entity subscribes to the analytics relating to QoS, receive new analytics results relating to QoS from the NWDAF entity.

11. The PCF entity of any one of the previous claims, wherein the one or more QoS parameter set and the one or more candidate QoS parameter set include the same parameter(s).

12. A network data analytics function (NWDAF) entity configured to:receive, from a policy control function (PCF) entity, a request or subscription to analytics relating to quality of service (QoS); andprovide, to the PCF entity, analytics results relating to QoS and comprising service experience information associated with one or more candidate QoS parameter set;wherein the request or subscription indicates one or more QoS parameter set;wherein each QoS parameter set includes at least one parameter and, for each of the at least one parameter, a value for said parameter; andwherein the at least one parameter includes at least one of: 5QI, one or more QoS characteristics, guaranteed flow bit rate (GFBR) or maximum flow bit rate (MFBR).

13. The NWDAF entity of claim 12, configured to:obtain data from one or more entity in a network; and derive the analytics results based on the obtained data.

14. The NWDAF entity of claim 13, wherein the obtained data comprises at least one of: packet filter set, obtained from a session management function (SMF) entity;user equipment (UE) location, obtained from an access and mobility management function (AMF) entity or a gateway mobile location centre (GMLC) entity;a time stamp associated with the obtained data, obtained from an SMF entity;service data, obtained from an operations, administration and maintenance (QAM) entity;a radio access technology (RAT) type camped on by a UE or accessed by the UE, obtained from an SMF entity;delay between a user plane function (UPF) entity and radio access network (RAN) entity, obtained from an QAM entity; anduplink(UL) / downlink(DL) delay between a UE and RAN, obtained from an QAM entity.

15. The NWDAF entity of any one of claims 12 to 14,wherein the analytics results comprise a duration of a time slot; and / orwherein the service experience information comprises an indication of the one or more candidate QoS parameter set.

16. The NWDAF entity of any one of claims 12 to 15, wherein the service experience information includes, for each of the one or more candidate QoS parameter set, one or more of:data network name (DNN) for a protocol data unit (PDU) session which contains a corresponding QoS flow for said candidate QoS parameter set;a list of RAT type(s) for which the information applies;a quality of experience (QoE) associated with said candidate QoS parameter set;value(s) of individual parameter(s) in said candidate QoS parameter set;a time window or time slot associated to the information;a validity period within the time slot for the analytics results;an area where the analytics results apply; anda valid duration of a corresponding QoS and / or a valid duration of the service experience information.

17. The NWDAF entity of claim 16, wherein the value(s) of individual parameter(s) for each of the one or more candidate QoS parameter set correspond to one or more of:a priority level;packet delay budget (PDB);packet error rate (PER);an averaging window; ora maximum delay burst volume.

18. The NWDAF entity of any one of claims 12 to 17, wherein the request or subscription further indicates a QoE; andwherein a predicted QoE of the one or more candidate QoS parameter set satisfy the indicated QoE.

19. The NWDAF entity of any one of claims 12 to 18, wherein the request or subscription further indicates one or more of:a preferred order of results for the one or more candidate QoS parameter; or an ordering criterion for one or more QoE associated to the one or more candidate QoS parameter set.

20. The NWDAF entity of any one of claims 12 to 19, wherein the request or subscription is received via another entity.

21. The NWDAF entity of any one of claims 12 to 20, configured to:if the PCF entity has subscribed to the analytics relating to QoS, generate new analytics results relating to QoS and providing the new analytics results to the PCF entity.

22. The NWDAF entity of any one of claims 12 to 21, wherein the one or more QoS parameter set and the one or more candidate QoS parameter set include the same parameter(s).

23. A method of a policy control function (PCF) entity, the method comprising:requesting or subscribing to analytics relating to quality of service (QoS) from an network data analytics function (NWDAF) entity; andreceiving, from the NWDAF entity, analytics results relating to QoS and comprising service experience information comprising one or more candidate QoS parameter set;wherein the request or subscription indicates one or more QoS parameter set;wherein each QoS parameter set includes at least one parameter and, for each of the at least one parameter, a value for said parameter; andwherein the at least one parameter includes at least one of: 5G QoS Identified (5QI), one or more QoS characteristics, guaranteed flow bit rate (GFBR) or maximum flow bit rate (MFBR).

24. A method of a network data analytics function (NWDAF) entity, the method comprising: receiving, from a policy control function (PCF) entity, a request or subscription to analytics relating to quality of service (QoS); andproviding, to the PCF entity, analytics results relating to QoS and comprising service experience information comprising one or more candidate QoS parameter set;wherein the request or subscription indicates one or more QoS parameter set;wherein each QoS parameter set includes at least one parameter and, for each of the at least one parameter, a value for said parameter; andwherein the at least one parameter includes at least one of: 5QI, one or more QoS characteristics, guaranteed flow bit rate (GFBR) or maximum flow bit rate (MFBR).

25. A computer-readable storage medium comprising instructions which, when executed by at least one processor of an electronic device, cause the electronic device to perform a method according to claim 23 or claim 24.T +44(0)30 0300 2000A

Images