Method and apparatus for QoS amd policy enhancements

Abstract

A policy control function (PCF) transmits to a network data analytics function (NWDAF) a request for information relating to quality of service (QoS) and / or policy control for a UE. The NWDAF obtains

Description

[0001] Certain examples of the present disclosure relate to methods, apparatus and / or systems for providing QoS and policy enhancements assisted by NWDAF. In various examples, a PCF is configured to consider a combination of enhanced NWDAF-based analytics in determining a policy such as a PCC rule and / or a QoS rule. In other examples, the PCF is configured to store or update the determined policy at a UDR, where the PCF may later retrieve the policy from the UDR for example during PDU session establishment for a UE. In other examples, a NWDAF is configured to collect new inputs to generate new outputs, such as predictions and / or statistics, to assist the PCF in determining QoS and / or policy control. Description of Related Art LO

[0002] The content of the following documents is referred to below and / or their content provides C\J background information that the following disclosure should be considered in the context of: [1] 3GPP TS 23.501 - System architecture for the 5G System (5GS), Release 18 (e.g. V18.4.0). [2] 3GPP TS 23.503 - Policy and charging control framework for the 5G System (5GS); Stage 2, Release 18 (e.g. V18.4.0). [3] 3GPP TS 23.288 - Architecture enhancements for 5G System (5GS) to support network data analytics services, Release 18 (e.g. V18.4.0). [4] 3GPP TSG SA Meeting #102, SP-231800. [5] TR 23.700-84 - Study on Core Network Enhanced Support for Artificial Intelligence (Al) I Machine Learning (ML), Release 19 (e.g. V0.1.0) Note: indicated version numbers are provided for illustrative purposes, other (including future) versions of these documents are considered also.

[0003] Wireless or mobile (cellular) communications networks in which a mobile terminal (e.g., user equipment (UE), such as a mobile handset) communicates via a radio link with a network of base stations, or other wireless access points or nodes, have undergone rapid development through a number of generations. The 3rd Generation Partnership Project (3GPP) design, specify and standardise technologies for mobile wireless communication networks. Fourth Generation (4G) and Fifth Generation (5G) systems (5GS) are now widely deployed, while beyond 5G (B5G) and 6G systems are being considered.

[0004] 3GPP standards for 4G systems include an Evolved Packet Core (EPC) and an Enhanced-UTRAN (E-UTRAN: an Enhanced Universal Terrestrial Radio Access Network). The E-UTRAN uses Long Term Evolution (LTE) radio technology. LTE is commonly used to refer to the whole system including both the EPC and the E-UTRAN, and LTE is used in this sense in the remainder of this document. LTE should also be taken to include LTE enhancements such as LTE Advanced and LTE Pro, which offer enhanced data rates compared to LTE.

[0005] In 5G systems a new air interface has been developed, which may be referred to as 5G New Radio (5G NR) or simply NR. NR is designed to support the wide variety of services and use case scenarios envisaged for 5G networks, though builds upon established LTE technologies B5G systems, such as 6G, are currently being considered and developed, and are expected to at least partly build on 5G systems.

[0006] New frameworks and architectures are being developed as part of 5G network (and £\J beyond, such as 6G networks) in order to increase the range of functionality and use cases available through 5G networks. T"—

[0007] Background of QoS (Quality of Service) and PCC (Policy and Charging Control) rules CO

[0008] As defined in TS 23.501 [1], the QoS parameters of 5GS include: — 5QI (5G QoS Identifier). — ARP (Allocation and Retention Priority): priority level, the pre-emption capability and the pre-emption vulnerability. — RQA (Reflective QoS Attribute): The 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 (Guaranteed Bit Rate) 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 (Protocol Data Unit) 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 "1“

[0009] 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 CM Session. This QoS Flow should be a Non-GBR QoS Flow.

[0010] The PCC rules / decision is defined in TS 23.503 [2]: 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.

[0011] 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.

[0012] 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 (Maximum Bit Rate), 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.

[0013] 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.

[0014] 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 clause 6.2.1.2 of TS 23.503 [2]: — 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: o Npcf_AMPolicyControl service. o 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: o Npcf_SMPolicyControl service of TS 23.502. o 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] , o 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.

[0015] Background of NWDAF analytics to support policy decision

[0016] 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 [3]. In the above (e.g. the above clause), UE Communication and Service Experience are two analytics used by the PCF to determine the QoS currently.

[0017] UE Communication Analytics is defined in clause 6.7.3 of TS 23.288 [3], 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 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.

[0018] The output analytics (using some predictions as examples) of the UE Communication Analytics are in Table 1 below (corresponding to Table 6.7.3.3-2: UE Communication Predictions of TS 23.822 [3]). The outputs include the per UE or per UE group parameters, and per application ID level parameters.

[0019] Table 1 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) (NOTE1) 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.

[0020] The Observed Service Experience related network data analytics is specified in clause 6.4 of TS 23.288 [3], The Observed Service Experience can provide the analytics of user experience, 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 V2X and Web Browsing services, analytics, in the form of statistics or predictions, to a service consumer. These analytics may collect or be based on a huge amount of data from different sources and at different levels. The output analytics may be for an application, an network slice and an UE. The outputs of this analytics may be statistics, where an example of statistics are shown in Table 2 below (corresponding to Table 6.4.3-1: Service Experience statistics of TS 23.288 [3]).

[0021] Table 2 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 (0..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 (0..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. LD

[0022] Standards Background CM v M

[0023] SA2 Rel-19 New SID on Core Network Enhanced Support for Artificial Intelligence (Al) / Machine Learning (ML) was approved in SP-231800 [4] during SA 102 meeting (Dec, 1 2023). As it has been documented in the WT#3.1 in SP-231800 [4]: CO — 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 adhoc e-meeting. As documented in clause 5.2.3 of TR 23.700-84 [5], Key Issue #3: NWDAF-assisted policy control and QoS enhancement: The NWDAF can gather quite a lot of data from 5GC NFs, AF and 0AM 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 ass / sf with policy control and QoS enhancements. — Whether and how to 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.

[0024] A use case associated to the above Kl#3 was agreed in SA2 160 ad-hoc e- meeting, and documented in 5.1.2 of TR 23.700-84 [5], 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. l / l / / 7en 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.

[0025] The description of Kl#3 in TR 23.700-84 [5] indicates that the following issues should be addressed during R19 AIML_CN study phase: — 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 how to evaluate the quality of the enhanced NWDAF assistance to policy control and QoS.

[0026] However, at present there is a lack of solutions for these issues, in particular based on the agreed use case in clause 5.1.2 of TR 23.700-84 [5], SUMMARY

[0027] 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.

[0028] According to an aspect of the present disclosure, there is provided a policy control function (PCF) entity configured to: transmit, to a network data analytics function (NWDAF) entity, a first request for information relating to quality of service (QoS) and / or policy control for a user equipment (UE); receive, from the NWDAF entity, a first response including the information; determine the QoS and / or policy control for the UE based on the information; I Ci Uj and notify the determined QoS and / or policy control for the UE to one or more consumer; wherein the information includes: analytics relating to one or more of network congestion level, resource usage condition, traffic patterns of UE services, service experience associated to different QoS parameters, or QoS sustainability associated to different 5Qls; CO and / or one or more set of candidate QoS and / or candidate policy. CM

[0029] According to various examples, the PCF entity is further configured to: determine the QoS and / or policy control from the one or more set of candidate QoS and / or candidate policy included in the information; or determine the QoS and / or policy control based on PCF internal logic and operator policy.

[0030] According to various examples, the first request comprises an indication of one or more analytics ID indicating analytics for providing assistance information on determining QoS and / or policy control.

[0031] According to various examples, the analytics comprises statistics, predications or output including one or more of: application ID; per application ID level traffic related parameters; QoS sustainability analytics; congestion level in an area within which the UE is or unexpected expected to appear; or resource usage for non- guaranteed bit rate (non-GBR) traffic.

[0032] According to various examples, the per application ID traffic related parameters comprise one or more of: uplink (UL) data rate per application ID; downlink (DL) data rate per application ID; data / traffic volume per application ID; delay per application ID; or traffic requirements per application ID (for example, QoS parameter(s), service mean opinion score (MOS), 5QI, Allocation and Retention Priority (ARP), Reflective QoS Attribute (RQA), Flow Bit Rates I traffic rate, GBR or non-GBR and / or Maximum Packet Loss Rate of said application).

[0033] According to various examples, the statistics, predications or output comprises one or more of: 5G QoS identifier (5QI); QoS key performance indicator (KPI); QoS flow identifier (QFI); UE ID for the UE; applicable area; or applicable time period; and / or wherein the QoS sustainability analytics are provided per-UE per QoS flow level.

[0034] According to various examples, the QoS KPI: is QoS flow Retainability KPI, and / or provides user or service experience satisfaction / level associated to each of the candidate QoS .

[0035] According to various examples, the candidate QoS parameters are associated with a QoS flow.

[0036] According to various examples, the PCF entity is further configured to: identify a trigger for transmitting the first request; and / or wherein the one or more consumer includes session management function (SMF), application function (AF) and / or Unified Data Repository (UDR).

[0037] 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 first request for information relating to quality of service (QoS) and / or policy control for a user equipment (UE); obtain input data based on the first request; and provide, to the PCF entity, a first response including the information; wherein the information includes: analytics relating to one or more of network congestion level, resource usage condition, traffic patterns of UE services, service experience associated to different QoS parameters, or QoS sustainability associated to different 5Qls; and / or one or more set of candidate QoS parameters and / or candidate policy. The information may be obtained by the NWDAF entity based on the input data or at least part thereof.

[0038] According to various examples, the first request comprises an indication of one or more analytics ID indicating analytics for providing assistance information on determining QoS and / or policy control.

[0039] According to various examples, the analytics comprises statistics, predications or output including one or more of: application ID; per application ID level traffic related parameters; QoS sustainability analytics; congestion level in an area within which the UE is or unexpected expected to appear; or resource usage for non- guaranteed bit rate (non-GBR) traffic.

[0040] According to various examples, the per application ID traffic related parameters comprise one or more of: uplink (UL) data rate per application ID; downlink (DL) data rate per application ID; data / traffic volume per application ID; delay per application ID; or traffic requirements per application ID (for example, QoS parameter(s), service mean opinion score (MOS), 5QI, Allocation and Retention Priority (ARP), Reflective QoS Attribute (RQA), Flow Bit Rates / traffic rate, GBR or non-GBR and / or Maximum Packet Loss Rate of said application).

[0041] According to various examples, the statistics, predications or output comprises one or more of: 5G QoS identifier (5QI); QoS key performance indicator (KPI); QoS flow identifier (QFI); UE ID for the UE; applicable area; or applicable time period; and / or wherein the QoS sustainability analytics are provided per-UE per QoS flow level.

[0042] According to various examples, the QoS KPI: is QoS flow Retainability KPI, and / or provides user or service experience satisfaction / level associated to each of the candidate QoS.

[0043] According to various examples, the input data is obtained from one or more of application function (AF), 5G network function (NF) or session management function (SMF); and / or wherein the input data relates to traffic / service requirements associated to an application.

[0044] According to various examples, the input data comprises one or more of: a set of QoS parameters; 5QI; ARP; RQA; flow bit rates / traffic rate; GBR or non-GBR; or maximum packet loss rate of the traffic of the application.

[0045] According to various examples, the NWDAF entity is further configured to derive the information based on the input data and reused input data of analytics existing prior to receiving the first request.

[0046] According to various examples, the reused input data is of any one or more of user data congestion analytics, network performance analytics, UE mobility analytics and abnormal behaviour analytics, UE communication analytics, observed service experience analytics, or QoS sustainability analytics.

[0047] According to another aspect of the present disclosure there is provided a method of a policy control function (PCF) entity, the method comprising: transmitting, to a network data analytics function (NWDAF) entity, a first request for information relating to quality of service (QoS) and / or policy control for a user equipment (UE); receiving, from the NWDAF entity, a first response including the information; determining the QoS and / or policy control for the UE based on the information; and notifying the determined QoS and / or policy control for the UE to one or more consumer; wherein the information includes: analytics relating to one or more of network congestion level, resource usage condition, traffic patterns of UE services, service experience associated to different QoS parameters, or QoS sustainability associated to different 5Qls; and / or one or more set of candidate QoS and / or candidate policy.

[0048] According to various examples, the method is modified to be in accordance with any one or more of the examples relating to the PCF entity given above.

[0049] According to another aspect of the present disclosure there is provided a method of a network data analytics function (NWDAF) entity, the method comprising: receiving, from a policy control function (PCF) entity, a first request for information relating to quality of service (QoS) and / or policy control for a user equipment (UE); obtaining input data based on the first request; and providing, to the PCF entity, a first response including the information; wherein the information includes: analytics relating to one or more of network congestion level, resource usage condition, traffic patterns of UE services, service experience associated to different QoS parameters, or QoS sustainability associated to different 5Qls; and / or one or more set of candidate QoS parameters and / or candidate policy. The information may be obtained by the NWDAF entity based on the input data or at least part thereof. LO

[0050] According to various examples, the method is modified to be in accordance with any one or C\l more of the examples relating to the NWDAF entity given above.

[0051] According to another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium comprising instructions which, when executed by at CO least one processor of an apparatus, cause the apparatus to perform a method according to any aspect or examples described / indicated above.

[0052] Other aspects, advantages, and salient features of the disclosure 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

[0053] Embodiments / examples of the present disclosure are further described hereinafter with reference to the accompanying drawings, in which: Figure 1 is a call flow diagram illustrating a method of NWDAF-assisted policy control and QoS enhancement according to various examples of the present disclosure. Figure 2 is a call flow diagram illustrating a method of NWDAF-assisted policy control and QoS enhancement according to various examples of the present disclosure. Figure 3 is a call flow diagram illustrating a method of deploying NWDAF-assisted QoS and policy determination during PDU session establishment according to various examples of the present disclosure. Figure 4 is a block diagram illustrating an example structure of a network entity in accordance with various examples of the present disclosure. Figure 5 is a flow diagram illustrating a method in accordance with various examples of the present disclosure. Figure 6 is a flow diagram illustrating a method in accordance with various examples of the present disclosure. DETAILED DESCRIPTION

[0054] The following description of examples of the present disclosure, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of certain examples of the present disclosure. The description includes various specific details to LO assist in that understanding but these are to be regarded as merely exemplary. C\l 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 T"— scope of the invention or disclosure. CO

[0055] The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings.

[0056] Detailed descriptions of techniques, structures, constructions, functions or processes known in the art may be omitted for clarity and conciseness, and to avoid obscuring the subject matter of the present disclosure.

[0057] 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 disclosure.

[0058] Throughout the description 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.

[0059] Throughout the description 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.

[0060] Throughout the description, the expression “at least one of A, B and / or C” (or the like), the expression “and / or”, and the expression “one or more of A, B and / or C” (or the like) should be seen to separately include all possible combinations, for example: A, B, C, A and B, A and C, A and B and C.

[0061] Throughout the description 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.

[0062] Features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof described or disclosed in conjunction with a particular aspect, embodiment or example are to be understood to be applicable to any other aspect, embodiment or example described herein unless incompatible therewith.

[0063] Certain examples of the present disclosure relate to methods, apparatus and / or systems for QoS and policy enhancements assisted by NWDAF. In various examples, a PCF is LO configured to consider a combination of enhanced NWDAF-based analytics in determining C\l a policy, such as a PCC rule and / or a QoS rule. In other examples, the PCF is configured to store or update the determined policy at a UDR, where the PCT may later retrieve the stored or updated policy from the UDR such as triggered by PDU session establishment for (hQ a UE. In other examples, a NWDAF is configured to collect new inputs to generate new CM outputs, such as predictions and / or statistics, to assist the PCF in determining QoS and / or policy control.

[0064] The following examples are applicable to, and use terminology associated with, 3GPP 5G. However, the skilled person will appreciate that the techniques disclosed herein are not limited to these examples or to 3GPP 5G, 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. The skilled person will appreciate that the techniques disclosed herein may be applied in any existing or future releases of 3GPP 5G NR or any other relevant standard. For example, the functionality of the various network entities and other features disclosed herein may be applied to corresponding or equivalent entities or features in other 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, operation or purpose within the network. In particular, the following disclosure should be considered at least in relation to 6G also, which is expected to use at least part of the 5G architecture, or equivalent, and to which the present disclosure also relates.

[0065] 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.

[0066] The skilled person will appreciate that the present disclosure is not limited to the specific examples disclosed herein. For example: • The techniques disclosed herein are not limited to 3GPP 5G, B5G or 6G. • 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, entities and / or messages may be added to the examples disclosed herein. • One or more non-essential elements, entities and / or messages 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 may be modified, if possible, in alternative examples. • The transmission of information between network entities is not limited to the specific form, type and / or order of messages described in relation to the examples disclosed herein.

[0067] 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. Such an apparatus / device / network entity 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). Certain examples of the present disclosure may be provided in the form of a system (e.g., a network) comprising one or more such apparatuses / devices / network entities, and / or a method therefor.

[0068] It will be appreciated that examples of the present disclosure may be realized in the form of hardware, software or a combination of hardware and software. Certain examples of the present disclosure may provide a computer program comprising instructions or code which, when executed, implement a method, system and / or apparatus in accordance with any aspect, example and / or embodiment disclosed herein. Certain embodiments of the present disclosure provide a machine-readable storage storing such a program.

[0069] A network according to one or more of the examples disclosed herein may include one or more of a Network Data Analytics Function (NWDAF) entity, an Access and Mobility Management Function (AMF) entity, a Session Management Function (SMF) entity, a Network Slice Selection Function (NSSF) entity, a Network Repository Function (NRF) entity, Application Function (AF) entity, and an Operation and Maintenance (OAM) entity. The network may include one or more Service Consumers (including one or more of the entities mentioned above and / or one or more other entities) that reoeive analytics from £\J NWDAF. The skilled person will appreciate that a network may omit one or more of the entities mentioned above and / or may comprise one or more additional entities T"—

[0070] As described above, there is a lack of solutions for the issues documented in the (hQ description of Kl#3 in TR 23.700-84 [5], in particular based on the agreed use case in CM clause 5.1.2 of TR 23.700-84 [5], According to various examples of the present disclosure, to solve, address or at least mitigate one or more of these issues, NWDAF analytics are leveraged to support enhanced 5GC NF operations, such as policy control and QoS.

[0071] In particular, various examples disclosed herein introduce enhancements or modifications to an / the NWDAF to assist with the QoS and policy control decision making. For example, the NWDAF disclosed herein provides or obtains enhanced analytics. The PCF considers a combination of the enhanced NWDAF-based analytics and other existing analytics to determine the policies, e.g. PCC rules, QoS. In some examples, a focus is on the use of the enhanced analytics by the PCF, so reference to existing analytics may be omitted. In various examples, the NWDAF may provide the (candidate) QoS parameters / 5QI, the QoS KPI / satisfaction associated with other assistance information to the PCF. Accordingly, the PCF will considering the analytic related to QoS and policy provided by the NWDAF, and optionally other additional information (e.g. information from AMF, SMF, NEF, AF, OAM. RAN node, UE etc.) to determine the QoS and policy to be deployed into 5GS. Based on the above, the PCF is able to (or aims to) generate future-proof and multi-service-compatible QoS for a UE; and therefore, to optimise the UE experience, reduce system wide signalling and / or improve the overall network performance. Accordingly, reference to a ‘future-proof rule (or similar) herein may be seen to refer to a rule which is obtained or generated using a method according to the present disclosure.

[0072] As described in Use Case #2 of TR 23.700-84 [5], 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. LD

[0073] In the existing framework, the PCF may determine the PCC rules based on information collected from multiple data sources, e.g. SMF, UPF, AF, etc. The NWDAF analytics can be considered by the PCF to check and improve the UE and network performance, e.g., as captured in clause 6.1.1.3 of TS 23.503 [2], after the 5QI is deployed by 5GS, based on "Service Experience" analytics, the PCF may check whether the 5QI values assigned to the application can satisfy the performance requirements and calculate and update the authorised QoS; the PCF may perform the SM Policy Association modifications to update policies for the PDU sessions handling traffic based on User Data Congestion analytics; and the PCF may also deploy a combination of multiple network analytics as inputs for policy decisions, e.g. the PCF may request the "Service Experience" analytics based on the UE Communication" analytics received previously for a policy decision.

[0074] Currently, the determination of default QoS rule and the SM policy generated during the PDU session establishment barely deploy the assistance of NWDAF analytics. Furthermore, the PCF is not capable to determine whether the assigned 5QI or the QoS rules can satisfy the requirements before they are actually deployed by the system.

[0075] According to various examples of the present disclosure, in order to determine the QoS and policy in a more intelligent and sustainable way, when authorising the QoS and / or generating or updating the PCC rules, the PCF may consider a combination of several aspects that may impact the QoS and policy of the current service(s) and, optionally, also the potential future service(s). The PCF may consider the statistics and / or predictions of the network congestion level and resource usage condition (e.g. the resource usage of GBR and non-GBR traffic given by Network performance analytics and congestion level given by congestion related analytics) in the area within which the UE may be expected or unexpected to appear (e.g. based on the UE location provided by UE mobility analytics or Unexpected UE location provided by Abnormal behaviour analytics), and / or the statistics and / or predictions of the traffic patterns of UE services (e.g. introducing new application level ID level inputs and outputs to UE communication analytics), the service experience of a UE associated to different QoS parameters (e.g. given by service experience), and the finer granularity of QoS sustainability associated to different 5Qls, etc. Therefore, the PCF will take a combination of analytics into consideration when generating, updating or authorising PCC rules and QoS.

[0076] Note that while examples disclosed herein may refer to QoS and policy (e.g. PCC) together, it should be appreciated that in other examples just the QoS or just the policy may be referred to instead; that is, the examples disclosed herein should be seen to include examples relating to QoS, examples relating to policy, and examples relating to QoS and policy together.

[0077] To assist with QoS and policy control, it is possible to enhance the existing analytics ID and / or introduce new analytics ID according to examples disclosed herein. LO

[0078] According to various examples of the present disclosure, the QoS and the policy can be C\l determined by taking the output(s) of one or more analytics ID into account, at the same time. In an example, one or more set of QoS parameters and policies are generated, e.g. T"— based on the internal logic of PCF or NWDAF. In a case where the one or more set of QoS ¢9 parameters and policies are generated by NWDAF or other NFs, the NWDAF or other NFs CM sends the one or more set of QoS parameters and policies to PCF. The final decision of the QoS and the policy (update / modification) of a service / PDU session / QoS flow / UE may be made by PCF. It will be understood that, in other examples, the PCF (as referred to in the previous example) can be replaced by any other 5GC network function (NF) that hosts the functionality of QoS and policy determination / modification / recommendation by considering a one or more output analytics (can be multiple analytics ID or multiple output analytics parameters), e.g. NWDAF, a new NF, NEF, etc.

[0079] In various examples, the 5GC NF (e.g. NWDAF, PCF, NEF, etc.) gathers information to determine one or more set of (candidate) QoS parameters and (candidate) policies to provide to the PCF to choose. The PCF may determine the QoS and policy to be applied to the 5GS from the one or more set of QoS parameters and policies, or the PCF may determine another QoS and / or policy, for example based on PCF internal logic and subject to operator policy.

[0080] Determining one or more set of QoS parameters and policies may be performed (e.g. determined) by the 5GC NF (e.g. NWDAF or PCF) based on information, data and / or outputs of one or more analytics ID(s) collected from different data sources, e.g. other NFs (SMF, UPF, NRF, AMF, GLMC, AF) or OAM, etc.

[0081] For example, if the NWDAF derives the one or more set of (candidate) QoS parameters and (candidate) policies, the NWDAF takes the existing (or stored) but still valid analytics output(s) of one or analytics ID into account. The NWDAF may retrieve the existing (or stored) but still valid analytics output(s) from ADRF which will be used as input data of the NWDAF to derive the prediction and statistics of (candidate) QoS parameters and (candidate) policies and / or the relevant assistance information. The existing (or stored) but still valid analytics outputs may include the output analytics of any one or more of: DN Performance Analytics. User Data Congestion analytics. Observed Service Experience Analytics. Abnormal Behaviour Analytics. UE communication analytics . QoS sustainability Analytics. UE mobility Analytics. Slice Load level Analytics . Network Performance Analytics. Observed Service Experience Analytics . NF Load Analytics.

[0082] Alternatively, in other examples the NWDAF may derive the prediction and statistics of (candidate) QoS parameters and (candidate) policies and / or the relevant assistance information by reusing the input information of the above analytics (with enhancements / introducing new input data), and other additional data

[0083] In order to allow the PCF and / or NWDAF to understand the service characteristics and the requirements of the past, on-going and potential future service(s) of a UE, application, service, DN (data network), PDU session and / or QoS flow; and, therefore, support the PCF and / or NWDAF to generate, determine or authorise the future-proof and multi-service-compatible (candidate) QoS and policy, enhancements to the input data and output of the above of the analytics are needed or new analytics ID is needed. — E.g. by enhancement of the UE communication analytics or introducing new analytics ID, the service requirements (e.g. 5QI, ARP, RQA, Flow Bit Rates / traffic rate, GBR or non-GBR, and / or Maximum Packet Loss Rate of the application) can be considered as new input information of NWDAF to generate the output analytics that can assist PCF. An example of this is shown in Table 3, given below (this may also be referred to as Table 6.X.1-1). It will be appreciated that other examples may comprise part of (e.g. one or more of) the entries shown in Table 3. The statistics and predictions (or output) of QoS and policy assistance information may include the per service level or per application ID level traffic related parameters, e.g. by enhancing the existing UE communication analytics, as shown in Table 4 (this may also be referred to as Table 6.x. 1-2): o UL7DL data rate per application ID; o data / traffic volume per application ID; o delay per application ID; o traffic requirements per application ID (e.g. 5QI, ARP, RQA, Flow Bit Rates / traffic rate, GBR or non-GBR, Maximum Packet Loss Rate of the application), etc.

[0084] Table 3 shows examples of input data for output analytics related to QoS and policy assistance information. LD CM

[0085] Table 3 Information Source Description Traffic / service requirements SMF, UPF, AF Traffic / service requirements associated to an application, e.g. 5QI, a set of QoS parameters, ARP, RQA, Flow Bit Rates / traffic rate, GBR or non-GBR, Maximum Packet Loss Rate of the traffic of the application. Resource allocated to a gNB for non-GBR traffic OAM The overall resource allocated to a gNB for non-GBR traffic RAN UE Throughput per UE OAM TS 28.558 The average UE throughput in downlink or uplink, per QoS level and per supported S-NSSAI, as defined in clause 6.3.1.4 of TS 28.558. Delay in RAN per UE OAM TS 28.558 The average time it takes for packet transmission over the airinterface in the downlink and uplink direction, per QoS level, per S-NSSAI, as defined in clause 6.3.1.1 of TS 28.558.

[0086] Table 4 shows examples of new statistics and prediction for assisting QoS and policy control decision. It will be appreciated that other examples may comprise part of (e.g. one or more of) the entries shown in Table 4.

[0087] Table 4 Information Description Applications (0..max) (NOTE 1) / DN performance List of application in use. > application ID Identifying the application providing this information / service > DNAI Identifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501 [2], > data rate (average, variance, maximum, peak) UL and / or DL data rate (e.g. flow bit rate) or throughput over the analytics period of an application or at application (ID) level. > data / traffic volume (average, variance, maximum, peak) data / traffic volume of the application over the analytics period or at application (ID) level > data packet delay / latency (average, variance, maximum, peak) data packet delay / latency of the application over the analytics period or at application (ID) level > traffic requirements of the application e.g. the QoS parameters, service MOS (Mean Opinion Score (MOS), one or more of the following parameters, e.g. 5QI, ARP, RQA, Flow Bit Rates, GBR or non-GBR, Maximum Packet Loss Rate, QoS parameters List of QoS sustainability Analytics at finer granularity (1..max) List of QoS sustainability Analytics at finer granularity, e.g. per QoS flow, per PDU session or per UE within the interested area. (1 ...max) can be the number / index of the UE, QoS flow, PDU session, etc. >UE ID Identifies a UE. >UE location Indicate the UE location information. >PDU session ID PDU session identifier. >QFI QoS Flow Identifier. >5QI or a set of QoS parameters / QoS profile (candidate) 5G QoS Identifier or a set of QoS parameters / QoS profile of a QoS flow. Application ID Identifier of an application. >Applicable Area (NOTE 1) A list of TAIs or Cell IDs or a geographical area in a fine granularity (e.g. smaller than a cell) within the Location information that the analytics applies to. If a Spatial granularity size was provided in the request or subscription, the number of elements of the list is smaller than or equal to the Spatial granularity size. >Applicable Time Period The time period within the Analytics target period that the analytics applies to. If a Temporal granularity size was provided in the request or subscription, the duration of the Applicable Time Period is greater than or equal to the Temporal granularity size. >QoS KPI The values of QoS KPI could be the MOS, the user or service experience satisfaction / level, or as defined in clause 6.9.1 of TS 23.288. e.g. fora 5QI of GBR resource type, (the Reporting Threshold(s)) refer to the QoS flow Retainability KPI; for a 5QI of non-GBR resource type, (the Reporting Threshold(s)) refer to the RAN UE Throughput KPI and / or delay in RAN KPI as defined in TS 28.554. QoS and / policy The Candidate or recommended QoS and / or policy derived by the NWDAF. Could be list of / one or more QoS parameter, QoS profiles, AM polices, SM policies, charging rules, UE policies, etc. gNB resource usage for non-GBR traffic Usage of assigned resources for non-GBR traffic (average, peak).

[0088] In order to better maintain the service quality for a UE, the QoS sustainability is an important factor. As defined in TS 23.288 [3], for a 5QI of GBR resource type, the QoS KPI LD could be the QoS flow Retainability KPI, which reflects how often an end-user abnormally C\J loses a QoS flow during the time the QoS flow is used. If the QoS flow Retainability of a QoS flow associated to a 5QI is not ideal, losing the QoS flow may interrupt the services of 1 a UE. For a 5QI of non-GBR, the QoS KPI refers to the RAN UE Throughput and / or delay CO in RAN which can reflect the service quality that can be provided by the network in the AOI (area of interest). Therefore, enhancing the outputs of QoS Sustainability analytics to per UE per QoS flow level will help the PCF to understand the whether the 5QI or QoS parameters can be supported for the UE in the AOI stably; and therefore, help the PCF to optimise the 5QI which can provide more sustainable service. The potential enhanced output analytics of the QoS Sustainability analytics may include the statistics and prediction of the per UE per QoS flow level QoS KPI for reporting, as shown in Table 4.

[0089] In various examples, in order to provide assistance information and / or candidate QoS to PCF, the NWDAF reuses the input data of the existing (enhanced) analytics and may request additional input data. The NWDAF may reuse the input data of any one or more of the following analytics IDs: — User Data Congestion Analytics. — Network Performance Analytics. — UE Mobility analytics and Abnormal Behaviour Analytics. — UE Communication Analytics. — Observed Service Experience Analytics . — QoS sustainability Analytics.

[0090] The additional input data may service requirements, e.g. one or more of 5QI or QoS profile, ARP, RQA, Flow Bit Rates / traffic rate, GBR or non-GBR, or Maximum Packet Loss Rate of the application, as shown in Table 3.

[0091] The NWDAF may also take the output of some analytics into account (e.g. as input data) to generate the output analytics of (candidate) QoS and policies and / or the assistance information, e.g. the output analytics of one or more of: — User Data Congestion Analytics — Network Performance Analytics — UE Mobility analytics and Abnormal Behaviour Analytics — UE Communication Analytics — Observed Service Experience Analytics — QoS sustainability Analytics

[0092] In various examples, the NWDAF may trigger to generate the output analytics of the above analytics ID, or fetch the existing but still valid analytics outputs that might be stored, e.g. in ADRF.

[0093] The output of the NWDAF aims help the PCF to understand the service characteristics and the requirements.

[0094] In order to better maintain the service quality for a UE, the QoS sustainability is an important factor. As defined in TS 23.288, for a 5QI of GBR resource type, the QoS KPI could be the QoS flow Retainability KPI which reflects how often an end-user abnormally loses a QoS flow during the time the QoS flow is used. If the QoS flow Retainability of a QoS flow associated to a 5QI is not ideal, losing the QoS flow may interrupt the services of a UE. For a 5QI of non-GBR, the QoS KPI refers to the RAN UE Throughput and / or delay in RAN which can reflect the service quality that can be provided by the network in the AOI. Therefore, the outputs analytics could be enhanced to per UE per QoS flow level which will help the PCF to understand the whether the 5QI or QoS parameters can be supported for the UE in the AOI stably. The candidate QoS candidates could be also provide by the NWDAF to the consumer NF (e.g. PCF). The QoS KPI may also provide the MOS, the user or service experience satisfaction / level associated to the candidate QoS. The potential enhanced output analytics are shown in Table 4.

[0095] Accordingly, Tables 3 and 4 provide examples of the enhanced analytics provided by an NWDAF according to the present disclosure, which are then provided to a PCF for use in determining, or generating, QoS and policy with enhancement.

[0096] Figure 1 illustrates (via a call flow diagram) a method of NWDAF-assisted policy control and QoS enhancement.

[0097] The entities in the example of Figure 1 are as follows: • 100 - UE (User Equipment). • 200 - SMF (Session Management Function). • 300 - PCF (Policy Control Function). • 400 - NWDAF (Network Data Analytics Function). • 500 -AMF (Access and Mobility Management Function), UPF (User Plane Function), AF (Application Function) and / or other 5GC. • 600 - UDR (Unified Data Repository). CO CM • 700 - ADRF (Analytics Data Repository Function).

[0098] It will be appreciated that, in more general examples, reference could instead be made to a first entity 100, a second entity 200, a third entity 300, a fourth entity 400, a fifth entity 500, a sixth entity 600 and a seventh entity 700; where each entity is arranged to perform the associated operation(s) indicated below. Furthermore, any one or more of entities in Figure 1 may be combined or co-located. For example, the PCF and the NWDAF can be co located, in which case an operation which indicates interaction between these two entities is performed internally (for example, not necessitating use of a transmitter / receiver for exchange of data between separate points in the network).

[0099] It will also be understood that various examples relate to individual entities shown in Figure 1. For instance; various examples are directed to the PCF, in which case such examples can focus on operations in which the PCF is involved and omit any other operations; while some other examples are directed to the NWDAF, in which case such examples can focus on operations in which the PCF is involved and omit any other operations. Additionally, yet further examples relate to any combination of the individual entities, and so may include the operations performed by these entities while omitting operations performed by other entities not included in the combination.

[00100] In operation S110, to collect the relevant information to assist with QoS and policy control decision, PCF 300 subscribes to or sends a request to different data sources, e.g. one or more of NWDAF 400, AMF 500, SMF 200, AF 500, etc. In the description of Figure 1, it will be appreciated that references to QoS and policy control together should be understood to not be limiting, where other examples in accordance with Figure 1 relate to either QoS or policy control.

[00101] This procedure / operation may be triggered, e.g. based on a condition being satisfied or detecting a trigger. Some example reasons by which the operation is triggered are as follows: to set up or update the default QoS rule before PDU session was established; triggered by the AF 500 to authorise the QoS and control policy of a service before the service starts; triggered by the PCF itself to check and update the performance of existing or active QoS and control policy that have been determined; etc. It will be appreciated that, more generally, the PCF may subscribe to or send the request based on a predetermined condition being met. As seen from the examples, one trigger is in response to a command or instruction (e.g. authorization) received from another entity in the network. LD

[00102] The PCF 300 may require the NWDAF 400 to provide the statistics and / or predictions of one or more (enhanced) analytics to assist with QoS and / or policy control decision for a UE, e.g. analytics ID indicates (or is) UE Communication, UE Mobility, Service Experience, QoS Sustainability, Network performance, or indicates (or is) new analytics that can provide assistance information of QoS and policy control decision, etc.

[00103] In operation S120, NWDAF 400 collects input data and generates (or provides, configures etc.) analytics based on PCF request. CO

[00104] To assist with QoS and policy control, based on the PCF 300 request, the NWDAF 400 may collect the information related to service requirements of multiple applications associated to a UE as input data to generate the UE communication analytics at per application ID level. The statistics and / or predictions of the per application ID level traffic characteristics - e.g. data rate, traffic volume, delay etc. - may help or assist the PCF 300 to determine the traffic patterns of multiple services of a UE when deciding the QoS and policy control. For examples, the collected information (e.g. information related to service requirements) relates to one or more of the information included in Table 3, while the output (e.g. statistics and / or predictions) may relate to one or more of the information included in Table 4.

[00105] In order to generate more sustainability QoS and policy control, the PCF 300 may require the NWDAF 400 to provide the statistics and / or predictions of QoS Sustainability analytics at finer granularity - e.g. per UE per QoS flow level of a 5QI. Based on the QoS KPI provided by the PCF 300 may choose the 5QI or the combination of QoS parameters that can provide the required QoS Sustainability for a UE or a QoS flow.

[00106] In operation S130, the different data sources from S110 send the required data or analytics (for NWDAF 400) to the PCF 300. For example, the different data sources first send the required data or analytics to the NWDAF 400, which processes the received data or analytics (e.g. combine them, or use them to generate output) and forwards / sends the result to the PCF 300. In another example, the PCF 300 receives the required data or analytics from the different data sources, where this may be based on an instruction from the NWDAF 400. More generally, operation S130 may be seen as the PCF 300 receiving the enhanced analytics or data related to such.

[00107] In operation S140, the PCF 300 consolidates all the input data and determines the QoS and / or policy control. The PCF 300 may determine QoS and policy control in a future-proof and multi-service-compatible manner. For example, in determining QoS and policy control in a future-proof and multi-service-compatible manner, the PCF 300 operates according to one of the examples disclosed above; e.g. PCF 300 considers the statistics and / or predictions of the network congestion level and resource usage condition (e.g. the resource usage of GBR and non-GBR traffic given by Network performance analytics and congestion level given by congestion related analytics) in the area within which the UE may be expected or unexpected to appear (e.g. based on the UE location provided by UE mobility analytics or Unexpected UE location provided by Abnormal behaviour analytics), and / or the statistics and / or predictions of the traffic patterns of UE services (e.g. introducing new application level ID level inputs and outputs to UE communication analytics), the service experience of a UE associated to different QoS parameters (e.g. given by service experience), and / or the finer granularity of QoS sustainability associated to different 5Qls, etc

[00108] The PCF 300 may notify (e.g. transmit or communicate) the determined QoS and policy control to the consumer(s) - e.g. other 5GC NFs or AF - based on the trigger of the QoS and policy control procedures. PCF 300 may notify the outcome of the QoS and policy control to SMF 200 to establish SM policy, to the AF 500 for the QoS configuration before the service starts, and / or to UDR 600 to provide or update the default QoS rule (e.g. before PDU session establishment), etc.

[00109] The method of Figure 1 includes an operation of policy and analytics context management, which comprises either or both of operations S150a and S150b. These operations are omitted in some examples of the present disclosure, such as examples in which storing output of the PCF 300 and / or NWDAF 400 at the UDR 600 and ADRF 700, respectively, is not required.

[00110] In operation S150a, the PCF 300 determines to store the determined QoS and policy control, and / or update existing QoS and policy control in UDR 600 for future use. In other words, the PCF 300 may store the results of operation S140, such as in the UDR 600, or may use the results of operation S140 to update existing, corresponding information (e.g., an existing QoS, if a QoS is determined in operation S140, and / or existing policy control, if policy control is determined in operation S140) stored at the UDR 600.

[00111] In operation S150b, the NWDAF 400 determines (based on PCF requirement) to store and / or update the analytics context of the above analytics in ADRF 700 for future use (e.g. update existing analytics context). In other words, the NWDAF 400 may store the analytics derived in operation S120 or data related to these analytics, such as at ADRF 700, or may use the derived analytics or related data to update existing, corresponding information at the ADRF 700 (e.g., update corresponding analytics or analytics context stored at the ADRF 700).

[00112] The method may further include an operation of PDU session establishment, which comprises one or more of operations S160a, 160b, S170a, S170b, S180, S190a and S190b). That is, from operations S160a to S190b, the PDU session establishment procedures are used as an example to illustrate the procedures of QoS and / or policy enhancements assisted by NWDAF as disclosed herein. It will therefore be appreciated that operations S160a to S190b can be omitted for various examples of the present disclosure, as these operations relate to an example which illustrates use of the NWDAF-assisted £\J enhanced QoS and policy control. It will also be appreciated that operations other than PDU session establishment may make use of QoS and / or policy control determined according to earlier operations S110 to S140 (and optionally S150a and / or S150b).

[00113] In operations S160a and S160b, a UE 100 triggers PDU session establishment to the CM 5GC. Upon receiving the PDU session establishment request, the SMF 200 triggers SM policy establishment procedures to the PCF 300 to require or request PCC rules.

[00114] In operation S170a, based on the SMF request, the PCF 300 determines to fetch the determined QoS and policy for the UE 100.

[00115] In operation S170b, the PCF 300 determines to update the fetched determined QoS and policy for the UE 100, or the PCF 300 determines to generate new QoS and policies by repeating operations S110 to S140.

[00116] It will be appreciated that it may be the decision of PCF 300 to determine whether to fetch or update the determined QoS and policy, or to generate new QoS and policy, e.g. subject to operator policy.

[00117] In operations S180, S190a and S190b, the PCF 300 notifies the SMF 200 of the determined QoS and policy for the UE 100. The SMF 200 establish the SM policy and PDU session based on the information derived from PCF notification. The SMF 200 establishes two QoS flows during the PDU session establishment, e.g. one QoS flow is with default QoS rule, another QoS flow associated to the future-proof QoS rule(s) to provide multi service-compatible QoS configuration. The SMF 200 notifies the UE 100 about the PDU session successfully establishment.

[00118] In an example, the operations of Figure 1 can be labelled as follows: • S110 — 1. PCF subscribes to different data sources to collect data to assist with QoS and policy decision. • S120 - 2. NWDAF collects input data and generates (enhanced) analytics based on PCF request. • S130 - 3. Different data sources send required data or analytics to PCF to assist with QoS and policy decision. • S140 - 4. PCF determines PCC rules, including QoS related information. • S150a - 5a. PCF stores or updates the generated QoS and policy in UDR (e.g. as part of policy and analytics context management procedure). • S150b - 5b. NWDAF stores or updates the analytics context in ADRF (e.g. as part of policy and analytics context management procedure). • S160a - 6a. PDU establishment (e.g. as part of PDU session establishment procedures). • S160b - 6b. Request for PCC rules (e.g. as part of PDU session establishment procedures). • S170a - 7a. PCF fetch the determined PCC rules from UDR (e.g. as part of PDU session establishment procedures). • S170b - 7b. The PCT may determine to update the determined or generate new QoS and policy by repeating steps 1-4 (e.g. as part of PDU session establishment procedures). • S180 - 8. PCC rules provided with determines 5QI(s) or QoS parameters (e.g. as part of PDU session establishment procedures). • S190a - 9a. SMF establishes QoS rule (e.g. as part of PDU session establishment procedures). • S190b - 9b. PDU session Establishment Accept (e.g. as part of PDU session establishment procedures).

[00119] For various examples in accordance with the present disclosure, a PCF is configured to consider a combination of NWDAF analytics, including new or enhanced analytics from NWDAF, to generate future-proof and multi-service-compatible QoS and policy. Also, the PCF is configured to store, update and / or fetch the determined (or generated) QoS and policy from UDR, including default QoS rules.

[00120] For various examples in accordance with the present disclosure, a NWDAF is configured to collect new inputs to generate assistance information of QoS and policy control. Also, the NWDAF is configured to generate new outputs to assist with PCF for QoS and policy control determination, including predictions and / or statistics. Further, the NWDAF is configured to expose, or provide, the new output analytics to consumers.

[00121] For various examples in accordance with the present disclosure, a UDR is configured to store, update, and / or notify QoS and policy decision based on a request from a PCF.

[00122] Figure 2 illustrates (via a call flow diagram) another example of a method of NWDAF-assisted policy control and QoS enhancement.

[00123] The entities in the example of Figure 2 are as follows: • 100 - UE (User Equipment). • 200 - SMF (Session Management Function). • 300 - PCF (Policy Control Function). • 400 - NWDAF (Network Data Analytics Function). • 500 -AMF (Access and Mobility Management Function), UPF (User Plane Function), AF (Application Function) and / or other 5GC. • 600 - UDR (Unified Data Repository). • 700 - ADRF (Analytics Data Repository Function). • 800-AF (Application Function).

[00124] It will be appreciated that, in more general examples, reference could instead be made to a first entity 100, a second entity 200, a third entity 300, a fourth entity 400, a fifth entity 500, a sixth entity 600, a seventh entity 700 and an eighth entity 800; where each entity is arranged to perform the associated operation(s) indicated below. Furthermore, any one or more of entities in Figure 2 may be combined or co-located. For example, the PCF and the NWDAF can be co-located, in which case an operation which indicates interaction between these two entities is performed internally (for example, not necessitating use of a transmitter / receiver for exchange of data between separate points in the network).

[00125] It will also be understood that various examples relate to individual entities shown in Figure 2. For instance; various examples are directed to the PCF, in which case such examples can focus on operations in which the PCF is involved and omit any other operations; while some other examples are directed to the NWDAF, in which case such examples can focus on operations in which the PCF is involved and omit any other operations. Additionally, yet further examples relate to any combination of the individual entities, and so may include the operations performed by these entities while omitting operations performed by other entities not included in the combination.

[00126] In operation S210, to collect the relevant information to assist with QoS and policy control decision, PCF 300 subscribes to or sends a request to different data sources, e.g. one or more of NWDAF 400, AMF 500, SMF 200, AF 500, 800, etc. In the description of Figure 2, it will be appreciated that references to QoS and policy control together should be understood to not be limiting, where other examples in accordance with Figure 2 relate to either QoS or policy control. LD

[00127] This procedure / operation may be triggered, e.g. based on a condition being satisfied or detecting a trigger. Some example reasons by which the operation is triggered are as follows: to set up or update the default QoS rule before PDU session was established; triggered by the AF 500, 800 to authorise the QoS and control policy of a service before the service starts; triggered by the PCF 300 itself to check and update the performance of existing or active QoS and control policy that have been determined; etc. It will be appreciated that, more generally, the PCF 300 may subscribe to or send the request based on a predetermined condition being met. As seen from the examples, one trigger is in response to a command or instruction (e.g. authorization) received from another entity in the network.

[00128] The PCF 300 may require the NWDAF 400 to provide the statistics and / or predictions of one or more (enhanced) analytics to assist with QoS and / or policy control decision for a UE, e.g. analytics ID indicates (or is) UE Communication, UE Mobility, Service Experience, QoS Sustainability, Network performance, or indicates (or is) new analytics that can provide assistance information of QoS and policy control decision, etc.

[00129] It is possible to enhance the existing analytics ID and / or introduce new analytics ID to assist with QoS and policy control.

[00130] In operation S220, NWDAF 400 collects input data and generates (or provides, configures etc.) analytics based on PCF request, to derive the output analytics that can assist with QoS and policy control.

[00131] To derive the output analytics that can assist with QoS and policy control, based on the PCF 300 request, the NWDAF 400 may collect the input data of one or more (e.g. all) of User Data Congestion Analytics, Network Performance Analytics, UE Mobility analytics and Abnormal Behaviour Analytics, UE Communication Analytics, Observed Service Experience Analytics, QoS sustainability Analytics, etc., and (optionally) additional input data, e.g. one or more (e.g. all) of service requirements related data that includes 5QI or QoS profile, ARP, RQA, Flow Bit Rates / traffic rate, GBR or non-GBR, or Maximum Packet Loss Rate of the application.

[00132] For example, the information related to service requirements of multiple applications associated to a UE is used as input data to generate the UE communication analytics at per application ID level. The statistics and prediction of the per application ID level traffic characteristics, e.g. data rate, traffic volume, delay etc., help the PCF 300 to determine the traffic patterns of multiple services of a UE when deciding the QoS and policy control. Furthermore, in order to generate more sustainability QoS and policy control, the PCF 300 may require the NWDAF 400 to provide the statistics and prediction of QoS Sustainability analytics at finer granularity, e.g. per UE per QoS flow level of a 5QI. Based on the QoS KPI provided by the NWDAF 400, the PCF 300 may choose the 5QI or the combination of QoS parameters that can provide the required QoS Sustainability for a UE or a QoS flow.

[00133] In operation S230, the different data sources from operation S210 send the required data or analytics (for NWDAF 400) to the PCF 300.

[00134] In operation S240, the PCF 300 consolidates all the collected data (e.g. the input data) LO and determine the QoS and / or policy control. The PCF 300 may determined the QoS C\l and / or policy control in a future-proof and multi-service-compatible manor, for example based on its internal logic and subject to operator policy.

[00135] For example, based on the trigger of the QoS and policy control procedures in operation CO S210, the PCF 300 notifies the determined QoS and policy control to its consumers to store or update the QoS and policy. For example, the PCF 300 notifies the QoS and policy control to SMF 200 to establish or modify SM policy, to the AF 500, 800 for the QoS configuration before the service starts, or to UDR 600 to provide or update the default QoS rule before PDU session establishment, etc.

[00136] Operation S250 relates to policy and analytics context management, and comprises either or both of operations S150a and S150b. These operations are omitted in some examples of the present disclosure, such as examples in which storing output of the PCF 300 and / or NWDAF 400 at the UDR 600 and ADRF 700, respectively, is not required.

[00137] In operation S250a, the PCF 300 determines to store the determined QoS and policy control or update the existing ones in UDR 600 for future use. In various examples, this operation is similar to operation S150a of FIG. 1.

[00138] In operation S250b, the NWDAF 400 determines (based on PCF requirement) to store or update the analytics context of the analytics derived in operation S220 in ADRF 700 for future use. In various examples, this operation is similar to operation S150b of FIG. 1.

[00139] In operation S260, the PCF 300 notifies the QoS and policy to other 5GC NF (e.g. SMF 200, AMF 100) or the AF 500, 800.

[00140] In an example, the operations of Figure 2 can be labelled as follows: • S210 - 1. PCF subscribes to different data sources to collect data to assist with QoS and policy decision. • S220 - 2. NWDAF collects input data and generates (enhanced) analytics based on PCF request. • S230 - 3. Different data sources send required data or analytics to PCF to assist with QoS and policy decision. • S240 - 4. PCF determines PCC rules, including QoS related information. • S250 - 5. Policy and analytics context management. • 250a - 5a. PCF store or update the generated QoS and policy in UDR. • S250b - 5b. NWDAF stores or updates the analytics context in ADRF. i / • S260 - 6. PCF sends the QoS and policy for policy establishment or modification. CM

[00141] Figure 3 illustrates (via a call flow diagram) an example of a method of deploying NWDAF-assisted QoS and policy determination during PDU session establishment.

[00142] The entities in the example of Figure 3 are as follows: • 100 - UE (User Equipment). • 200 - SMF (Session Management Function). • 300 - PCF (Policy Control Function). • 400 - NWDAF (Network Data Analytics Function). • 500 - AMF (Access and Mobility Management Function), UPF (User Plane Function), AF (Application Function) and / or other 5GC. • 600 - UDR (Unified Data Repository). • 700 - ADRF (Analytics Data Repository Function).

[00143] It will be appreciated that, in more general examples, reference could instead be made to a first entity 100, a second entity 200, a third entity 300, a fourth entity 400, a fifth entity 500, a sixth entity 600 and a seventh entity 700; where each entity is arranged to perform the associated operation(s) indicated below. Furthermore, any one or more of entities in Figure 3 may be combined or co-located. For example, the PCF and the NWDAF can be co-located, in which case an operation which indicates interaction between these two entities is performed internally (for example, not necessitating use of a transmitter / receiver for exchange of data between separate points in the network).

[00144] It will also be understood that various examples relate to individual entities shown in Figure 3. For instance; various examples are directed to the PCF, in which case such examples can focus on operations in which the PCF is involved and omit any other operations; while some other examples are directed to the NWDAF, in which case such examples can focus on operations in which the PCF is involved and omit any other operations. Additionally, yet further examples relate to any combination of the individual entities, and so may include the operations performed by these entities while omitting operations performed by other entities not included in the combination.

[00145] In the example of Figure 3, PDU session establishment procedures are used as an example to illustrate the procedures of how the 5GC may deploy the NWDAF assistance with QoS and policy determination as disclosed herein.

[00146] In operation S310a, UE 100 triggers PDU session establishment to the 5GC. Upon receiving the PDU session establishment request, in operation S310b the SMF 200 triggers LO SM policy establishment procedures to the PCF 300 to require PCC rules. CM

[00147] Relating to operations S320a, S320b, the PCF 300 determines the QoS and policy for the SM policy establishment request by deploying NWDAF assistance. For example, based on the SMF request: in operation S320a the PCF 300 determines to fetch the determined QoS CO and policy (if available) for the UE, if operation S250 or operation S250a in FIG. 2 is already performed; and / or, in operation S320b, the PCF 300 determines to update the fetched stored QoS and policy or generate new QoS and policy for PDU session of the UE, by repeating operations S210 to S240 in FIG. 2.

[00148] It will be understood that, in various examples, it is the decision of PCF 300 to determine whether to fetch or update the determined QoS and policy, or to generate new QoS and policy, e.g. subject to operator policy.

[00149] In operation S330, the PCF 300 notifies or informs the SMF 200 of the determined QoS and policy for PDU session of the UE 100.

[00150] In operation S340a, the SMF 200 establishes the SM policy and PDU session based on the information indicated by PCF notification, and in operation S340b the SMF 200 sends PUD Session Establishment Accept message to the UE 100. The SMF 200 may establish two QoS flows during the PDU session establishment, e.g. one QoS flow is with default QoS rule and another QoS flow associated to the future-proof QoS rules to provide multi-service-compatible QoS configuration. The SMF 200 may notify the UE 100 about the PDU session being successfully established.

[00151] In an example, the operations of Figure 3 can be labelled as follows: • S310a - 1a. PDU establishment. • S310b - 1b. Request for PCC rules. • S320a - 2a. PCF fetch the determined PCC rules from UDR. • S320b - 2b. the PCF may determine to update the determined or generate new QoS and policy by repeating step 1-4 (of Figure 2). • S330 - 3. PCC rules provided with determined 5QI(s) or QoS parameters. • S340a - 4a. SMF establishes QoS rule. • S340b - 4b. PDU session Establishment Accept.

[00152] Figure 4 is a block diagram of an exemplary apparatus, or network entity, that may be used in examples of the present disclosure. The skilled person will appreciate said 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.

[00153] The entity 1000 comprises a processor (or controller) 1001, a transmitter 1003 and a receiver 1005. The receiver 1005 is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter 1003 is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor 1001 is configured for performing one or more operations, for example according to the operations as described above.

[00154] Figure 5 illustrates a method according to an example of the present disclosure. The method is performed by a network entity such as a PCF entity.

[00155] In operation 510, the PCF entity transmits, to a NWDAF entity, a first request relating to QoS and / or policy control for a UE. The first request may be for information relating to QoS and / or policy control for the UE.

[00156] In operation 520, the PCF entity receives, from the NWDAF entity, a first response including information (this may be the requested information), wherein the information includes: analytics relating to one or more of network congestion level, resource usage condition, traffic patterns of UE services, service experience associated to different QoS parameters, or QoS sustainability associated to different 5Qls; and / or one or more set of candidate QoS and / or candidate policy.

[00157] In operation 530, the PCF entity determines the QoS and / or policy control for the UE based on the information.

[00158] In optional operation 540, the PCF entity notifies the determined QoS and / or policy control for the UE to one or more consumer.

[00159] Figure 6 illustrates a method according to an example of the present disclosure. The method is performed by a network entity such as a NWDAF entity.

[00160] In operation 610, the NWDAF entity receives, from a PCF entity, a first request relating to QoS and / or policy control for a UE. The first request may be for information relating to QoS and / or policy control for the UE.

[00161] In operation 620, the NWDAF entity obtains input data based on the first request.

[00162] In operation 630, the NWDAF entity provides to the PCF entity, a first response including information (this may be the requested information), wherein the information includes: analytics relating to one or more of network congestion level, resource usage condition, traffic patterns of UE services, service experience associated to different QoS parameters, or QoS sustainability associated to different 5Qls; and / or one or more set of candidate QoS parameters and / or candidate policy. The information may be obtained, by the NWDAF entity, based on the obtained input data or at least a part thereof. LO

[00163] It will be appreciated that, in each example / embodiment / aspect etc. described above, one or more features or operations may be omitted, modified or moved (e.g., to change the order of the features or the operations), if desired and appropriate. Additionally, one or more features or operations from any example / embodiment may be combined with features or operations from any other example / embodiment. In particular, regardless of whether or not a pointer towards a combination of features / examples is found herein, the present disclosure should be considered to include all combinations of two or more of the embodiments, examples etc. disclosed herein, and all combinations of two or more of the features disclosed herein.

[00164] 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 or example 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.

[00165] 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.

[00166] 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 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 and / or aspect 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 signal carried over a wired or wireless connection.

[00167] While the present disclosure has been shown, illustrated 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 disclosure.

[00168] The reader's attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference. 23 10 25 Acronyms and Definitions (as may be used herein) 3GPP 3rd Generation Partnership Project NSSF Network Slice Selection Function 5G 5th Generation NW Network 5GC 5G Core NWDAF Network Data Analytics Function 5QI 5G QoS Identifier QAM Operations and Management 5GS 5G System OS Operating System 5GSM 5G System Session Management PCF Policy Control Function 5GMM 5G System Mobility Management PCC Policy and Charging Control AF Application Function PCO Protocol Configuration Options Al Artificial Intelligence PDR Packet Detection Rule AIML Artificial Intelligence / Machine PDU Protocol Data Unit Learning PMF Performance Measurement Function AM Acknowledged Mode PRU Positioning Reference Unit AMF Access and Mobility Management PSA PDU session anchor Function QFI QoS Flow Identifier (ID) ARP Allocation and Retention Priority QoE Quality of Experience AS Application Server QoS Quality of Service ASP Application Service Provider RACH Random Access Channel ATSSS Access Traffic Steering Switching RAN Radio Access Network & Splitting RAT Radio Access Technology AUSF Authentication Server Function RLC-AM Radio Link Control Acknowledge CDRX Connected Mode Discontinuous Mode Reception RLC-UM Radio Link Control Unacknowledge CSI Channel Status Information Mode DCAF Data Collection Application RSD Route Selection Descriptor Function SA Standalone DNAI Data Network Access Identifier SBA Service-Based Architecture DNN Data Network Name SBI Service-Based Interface DNS Domain Name Server SCEF Service Capability Exposure Function DRB Data Radio Bearer SCP Service-Based Communication Proxy eNB Evolved Node B SCTP Stream Control Transmission EPS Evolved Packet System Protocol FQDN Fully Qualified Domain Name SDAP Service Data Adaptation Protocol GBR Guaranteed Bit Rate SDU Service Data Unit GFBR Guaranteed Flow Bit Rate SIM Subscriber Identity Module GMLC Gateway Mobile Location Centre SLA Service Level Agreement gNB Next generation Node B SM Session Management GPSI Generic Public Subscription SMF Session Management Function Identifier SN Secondary Node IAB Integrated Access and Backhaul S-NSSAI Single Network Slice Selection HoT Industrial Internet of Things Assistance Information IMEI International Mobile Equipment SSC Session and Service Continuity Identities SUPI Subscription Permanent Identifier IP Internet Protocol TAI Tracking Area Identity l-SMF Intermediate SMF TE Terminal Equipment LMF Location Management Function TM Transparent Mode MA-PDU Multiple Access PDU TS Technical Specification ML Machine Learning UDM Unified Data Manager MME Mobility Management Entity UDR Unified Data Repository MN Master Node UE User Equipment MNO Mobile Network Operator UL Uplink MPTCP MultiPath TCP UM Unacknowledged Mode MT Mobile Termination UP User Plane NAS Non-Access Stratum UPF User Plane Function NEF Network Exposure Function URLLC Ultra-Reliable and Low-Latency NRF Network Repository Function Communication NG-RAN Next Generation Radio Access URSP UE Route Selection Policy Network V2X Vehicle-to-everything NG-eNB Next Generation eNB XRM Extended Reality and Media NSA Non-Standalone

Claims

1. A policy control function (PCF) entity configured to:transmit, to a network data analytics function (NWDAF) entity, a first request for information relating to quality of service (QoS) and / or policy control for a user equipment (UE);receive, from the NWDAF entity, a first response including the information;determine the QoS and / or policy control for the UE based on the information; and notify the determined QoS and / or policy control for the UE to one or more consumer; wherein the information includes:analytics relating to one or more of network congestion level, resource usage condition, traffic patterns of UE services, service experience associated to different QoS parameters, or QoS sustainability associated to different 5Qls; and / orone or more set of candidate QoS and / or candidate policy.

2. The PCF entity of claim 1, configured to:determine the QoS and / or policy control from the one or more set of candidate QoS and / or candidate policy included in the information; ordetermine the QoS and / or policy control based on PCF internal logic and operator policy.

3. The PCF entity of any previous claim, wherein the first request comprises an indication of one or more analytics ID indicating analytics for providing assistance information on determining QoS and / or policy control.

4. The PCF entity of any previous claim, wherein the analytics comprises statistics, predications or output including one or more of:application ID;per application ID level traffic related parameters;QoS sustainability analytics;congestion level in an area within which the UE is or unexpected expected to appear; orresource usage for non- guaranteed bit rate (non-GBR) traffic.

5. The PCF entity of claim 4, wherein the per application ID traffic related parameters comprise one or more of:uplink (UL) data rate per application ID;downlink (DL) data rate per application ID;data / traffic volume per application ID;delay per application ID; ortraffic requirements per application ID (for example, QoS parameter(s), service mean opinion score (MOS), 5QI, Allocation and Retention Priority (ARP), Reflective QoS Attribute (RQA), Flow Bit Rates I traffic rate, GBR or non-GBR and / or Maximum Packet Loss Rate of said application).

6. The PCF entity of claim 4 or claim 5, wherein the statistics, predications or output comprises one or more of:5G QoS identifier (5QI);QoS key performance indicator (KPI);QoS flow identifier (QFI);UE ID for the UE;applicable area; orapplicable time period;and / or wherein the QoS sustainability analytics are provided per-UE per QoS flow level.

7. The PCF entity of claim 6, wherein the QoS KPI:is QoS flow Retainability KPI, and / orprovides user or service experience satisfaction / level associated to each of the candidate QoS.

8. The PCF entity of any previous claim, wherein the candidate QoS parameters are associated with a QoS flow.

9. The PCF entity of any previous claim, wherein the PCF entity is further configured to identify a trigger for transmitting the first request; and / or wherein the one or more consumer includes session management function (SMF), application function (AF) and / or Unified Data Repository (UDR).

10. A network data analytics function (NWDAF) entity configured to:receive, from a policy control function (PCF) entity, a first request for information relating to quality of service (QoS) and / or policy control for a user equipment (UE);obtain input data based on the first request; andprovide, to the PCF entity, a first response including the information;wherein the information includes:analytics relating to one or more of network congestion level, resource usage condition, traffic patterns of UE services, service experience associated to different QoS parameters, or QoS sustainability associated to different 5Qls; and / orone or more set of candidate QoS parameters and / or candidate policy.

11. The NWDAF entity of claim 10, wherein the first request comprises an indication of one or more analytics ID indicating analytics for providing assistance information on determining QoS and / or policy control.

12. The NWDAF entity of claim 10 or claim 11, wherein the analytics comprises statistics, predications or output including one or more of:application ID;per application ID level traffic related parameters;QoS sustainability analytics;congestion level in an area within which the UE is or unexpected expected to appear; orresource usage for non- guaranteed bit rate (non-GBR) traffic.

13. The NWDAF entity of claim 12, wherein the per application ID traffic related parameters comprise one or more of:uplink (UL) data rate per application ID;downlink (DL) data rate per application ID;data / traffic volume per application ID;delay per application ID; ortraffic requirements per application ID (for example, QoS parameter(s), service mean opinion score (MOS), 5QI, Allocation and Retention Priority (ARP), Reflective QoS Attribute (RQA), Flow Bit Rates I traffic rate, GBR or non-GBR and / or Maximum Packet Loss Rate of said application).

14. The NWDAF entity of claim 12 or claim 13, wherein the statistics, predications or output comprises one or more of:5G QoS identifier (5QI);QoS key performance indicator (KPI);QoS flow identifier (QFI);UE ID for the UE;applicable area; orapplicable time period;and / or wherein the QoS sustainability analytics are provided per-UE per QoS flow level.

15. The NWDAF entity of claim 14, wherein the QoS KPI:is QoS flow Retainability KPI, and / orprovides user or service experience satisfaction / level associated to each of the candidate QoS.

16. The NWDAF entity of any one of claims 10 to 15, wherein the input data is obtained from one or more of application function (AF), 5G network function (NF) or session management function (SMF); and / orwherein the input data relates to traffic / service requirements associated to an application.

17. The NWDAF entity of claim 16, wherein the input data comprises one or more of:a set of QoS parameters;5QI;ARP;RQA;flow bit rates / traffic rate;GBR or non-GBR; ormaximum packet loss rate of the traffic of the application.

18. The NWDAF entity of any one of claims 10 to 16, further configured to:derive the information based on the input data and reused input data of analytics existing prior to receiving the first request.

19. The NWDAF entity of claim 18, wherein the reused input data is of any one or more of user data congestion analytics, network performance analytics, UE mobility analytics and abnormal behaviour analytics, UE communication analytics, observed service experience analytics, or QoS sustainability analytics.

20. A method of a policy control function (PCF) entity, the method comprising:transmitting, to a network data analytics function (NWDAF) entity, a first request for information relating to quality of service (QoS) and / or policy control for a user equipment (UE);receiving, from the NWDAF entity, a first response including the information;determining the QoS and / or policy control for the UE based on the information; and notifying the determined QoS and / or policy control for the UE to one or more consumer;wherein the information includes:analytics relating to one or more of network congestion level, resource usage condition, traffic patterns of UE services, service experience associated to different QoS parameters, or QoS sustainability associated to different 5Qls; and / orone or more set of candidate QoS and / or candidate policy.

21. A method of a network data analytics function (NWDAF) entity, the method comprising:receiving, from a policy control function (PCF) entity, a first request for information relating to quality of service (QoS) and / or policy control for a user equipment (UE);obtaining input data based on the first request; andproviding, to the PCF entity, a first response including the information;wherein the information includes:analytics relating to one or more of network congestion level, resource usage condition, traffic patterns of UE services, service experience associated to different QoS parameters, or QoS sustainability associated to different 5Qls; and / orone or more set of candidate QoS parameters and / or candidate policy.

22. A non-transitory computer-readable storage medium comprising instructions which, when executed by at least one processor of an apparatus, cause the apparatus to perform a method according to claim 20 or claim 21.

Images