WO2025150807A1

WO2025150807A1 - Methods and apparatus for enhanced qos setup with nwdaf assistance in a wireless communication system

Info

Publication number: WO2025150807A1
Application number: PCT/KR2025/000215
Authority: WO
Inventors: Tingyu XIN; David Gutierrez Estevez; Chadi KHIRALLAH; Mahmoud Watfa
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2024-01-12
Filing date: 2025-01-06
Publication date: 2025-07-17
Anticipated expiration: 2026-07-12
Also published as: GB2640480A; GB202400505D0; GB202418099D0

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Specifically, the disclosure related to a method of Network Data Analytics Function (NWDAF) assisted Quality of Service (QoS) setup for a User Equipment (UE) in a telecommunications network, the method comprising: using, at and/or during establishment or modification of a Protocol Data Unit (PDU) session, a QoS value for a default QoS that is different from a subscribed default QoS value for the UE; and/or returning, by the Session Management Function (SMF) and/or the Policy Control Function (PCF), at least two QoS flows; and/or subscribing, by the SMF and/or the PCF, to and/or with the NWDAF for at least one defined analytics.

Description

METHODS AND APPARATUS FOR ENHANCED QOS SETUP WITH NWDAF ASSISTANCE IN A WIRELESS COMMUNICATION SYSTEM

The present disclosure relates generally to wireless communication systems and, more specifically, the present disclosure relates to QoS setup, for example in 5GC in a wireless communication system.

Considering the development of wireless communication from generation to generation, the technologies have been developed mainly for services targeting humans, such as voice calls, multimedia services, and data services. Following the commercialization of 5G (5th generation) communication systems, it is expected that the number of connected devices will exponentially grow. Increasingly, these will be connected to communication networks. Examples of connected things may include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machines, and factory equipment. Mobile devices are expected to evolve in various form-factors, such as augmented reality glasses, virtual reality headsets, and hologram devices. In order to provide various services by connecting hundreds of billions of devices and things in the 6G (6th generation) era, there have been ongoing efforts to develop improved 6G communication systems. For these reasons, 6G communication systems are referred to as beyond-5G systems.

6G communication systems, which are expected to be commercialized around 2030, will have a peak data rate of tera (1,000 giga)-level bit per second (bps) and a radio latency less than 100μsec, and thus will be 50 times as fast as 5G communication systems and have the 1/10 radio latency thereof.

In order to accomplish such a high data rate and an ultra-low latency, it has been considered to implement 6G communication systems in a terahertz (THz) band (for example, 95 gigahertz (GHz) to 3THz bands). It is expected that, due to severer path loss and atmospheric absorption in the terahertz bands than those in mmWave bands introduced in 5G, technologies capable of securing the signal transmission distance (that is, coverage) will become more crucial. It is necessary to develop, as major technologies for securing the coverage, Radio Frequency (RF) elements, antennas, novel waveforms having a better coverage than Orthogonal Frequency Division Multiplexing (OFDM), beamforming and massive Multiple-input Multiple-Output (MIMO), Full Dimensional MIMO (FD-MIMO), array antennas, and multiantenna transmission technologies such as large-scale antennas. In addition, there has been ongoing discussion on new technologies for improving the coverage of terahertz-band signals, such as metamaterial-based lenses and antennas, Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS).

Moreover, in order to improve the spectral efficiency and the overall network performances, the following technologies have been developed for 6G communication systems: a full-duplex technology for enabling an uplink transmission and a downlink transmission to simultaneously use the same frequency resource at the same time; a network technology for utilizing satellites, High-Altitude Platform Stations (HAPS), and the like in an integrated manner; an improved network structure for supporting mobile base stations and the like and enabling network operation optimization and automation and the like; a dynamic spectrum sharing technology via collision avoidance based on a prediction of spectrum usage; an use of Artificial Intelligence (AI) in wireless communication for improvement of overall network operation by utilizing AI from a designing phase for developing 6G and internalizing end-to-end AI support functions; and a next-generation distributed computing technology for overcoming the limit of UE computing ability through reachable super-high-performance communication and computing resources (such as Mobile Edge Computing (MEC), clouds, and the like) over the network. In addition, through designing new protocols to be used in 6G communication systems, developing mechanisms for implementing a hardware-based security environment and safe use of data, and developing technologies for maintaining privacy, attempts to strengthen the connectivity between devices, optimize the network, promote softwarization of network entities, and increase the openness of wireless communications are continuing.

It is expected that research and development of 6G communication systems in hyper-connectivity, including person to machine (P2M) as well as machine to machine (M2M), will allow the next hyper-connected experience. Particularly, it is expected that services such as truly immersive eXtended Reality (XR), high-fidelity mobile hologram, and digital replica could be provided through 6G communication systems. In addition, services such as remote surgery for security and reliability enhancement, industrial automation, and emergency response will be provided through the 6G communication system such that the technologies could be applied in various fields such as industry, medical care, automobiles, and home appliances.

The present disclosure relates to wireless communication systems and, more specifically, the present disclosure relates to method and apparatus for enhanced QoS Setup with NWDAF Assistance in a wireless communication system.

In one embodiment, the present disclosure relates to a method of Network Data Analytics Function (NWDAF) assisted Quality of Service (QoS) setup for a User Equipment (UE) in a wireless communication system. The method comprises using, at and/or during establishment or modification of a Protocol Data Unit (PDU) session, a QoS value for a default QoS that is different from a subscribed default QoS value for the UE; and/or returning, by the Session Management Function (SMF) and/or the Policy Control Function (PCF), at least two QoS flows; and/or subscribing, by the SMF and/or the PCF, to and/or with the NWDAF for at least one defined analytics.

In another embodiment, the method further comprises the step of defining, by the PCF and/or the SMF, the default QoS value for the UE, for example based on analytics information.

In another embodiment, the method further comprises the step of obtaining, by the SMF and/or the PCF, analytics for the UE, and/or other information related to network performance.

In another embodiment, the method further comprises the step of verifying, by the SMF and/or the PCF, the frequency of QoS changes that were made by the UE.

In another embodiment, the method further comprises the step of determining, by the SMF and/or the PCF, to use a default QoS value for the default QoS flow that is different from the subscribed QoS value.

In an embodiment, the method further comprises the step of informing, by the SMF, the PCF that at least one QoS value has been modified, based on analytics.

In another embodiment, the method further comprises the step of obtaining, by the SMF and/or the PCF analytics for the UE, where the analytics relates to QoS sustainability analytics.

In another embodiment, the method further comprises the step of performing, by the NWDAF, analytics for the UE in a certain area of interest.

In another embodiment, the method further comprises the step of determining, by the SMF and/or the PCF, that QoS change statistics indicate that the UE may request a change of QoS.

In another embodiment, the method further comprises the step of creating and/or establishing, by the SMF and/or the PCF, at least one additional QoS rule or QoS flow with a QoS value that is different from the QoS value associated with the default QoS flow.

In another embodiment, the method further comprises the step of choosing, by the SMF and/or the PCF, a QoS value for an additional QoS flow such that the chosen value is similar to, or better than in terms of QoS characteristics, what the UE would have normally requested for a QoS flow which is not a default QoS flow.

In another embodiment, the method further comprises the step of ensuring, by the SMF and/or the PCF, that an "Authorized QoS rules" Information Element (IE) of a PDU Session Establishment Accept message contains at least one additional QoS rule which is not a default QoS rule, and/or the QoS value that is indicated is associated with, or maps to, the chosen QoS value.

In another embodiment, the method further comprises the step of informing, by the SMF, the PCF that at least one QoS value has been modified based on analytics.

In another embodiment, the method further comprises the step of triggering, by the PCF and/or the PCF, storage/retrieval of analytics from the ADRF.

In another embodiment, the method further comprises the step of retrieving, by the PCF, the stored analytics for the UE, when the SMF contacts the PCF to obtain policy rules.

In another embodiment, the method further comprises the step of determining, by the PCF and/or the SMF, a modified QoS value based on the analytics obtained from the ADRF and/or the NWDAF and providing, by the PCF, a policy rule such that the determined QoS value is then provided.

In another embodiment, the method further comprises the step of determining, by the PCF and/or the SMF, to provide a second rule such that the second rule is associated with a non-default QoS rule and determining the QoS value for this rule based on the analytics that is received.

In another embodiment, the method further comprises the step of providing, by the PCF to the SMF: the determined QoS value for the default QoS rule or QoS flow; and/or at least two rules where the second rule is for a non-default QoS rule with a QoS value that has been determined.

In another embodiment, the method further comprises the step of determining, by the SMF and/or PCF, to establish at least two QoS rules during a PDU session establishment procedure, if SMF and/or PCF receives at least two policy rules where at least one of these are for a non-default QoS rule.

In another embodiment, the method further comprises the step of providing, by the PCF to the SMF, an indication that the QoS value has been determined based on analytics; and establishing, by the SMF, at least one non-default QoS rule based on the indication.

According to a second aspect of the invention, there is provided a telecommunications network configured to implement the method according to the first aspect.

For a better understanding of the invention, and to show how exemplary embodiments of the same may be brought into effect, reference will be made, by way of example only, to the accompanying diagrammatic Figures, in which:

Figure 1A illustrates overall signalling based on a prior art procedure for session modification from 3GPP TS 23.502;

Figure 1B illustrates overall signalling based on a prior art procedure for session modification from 3GPP TS 23.502;

Figure 2 illustrates an example procedure to establish a PDU session using a modified default 5QI value based on analytics;

Figure 3 illustrates an example procedure to establish non-default QoS rule based with 5QI based on analytics;

Figure 4 illustrates an example procedure for PCF determination of 5QI values based on analytics.

Figure 5 illustrates a block diagram of a terminal (or a user equipment (UE), according to embodiments of the present disclosure;

Figure 6 illustrates a block diagram of a base station, according to embodiments of the present disclosure; and

Figure 7 illustrates a block diagram of a network entity, according to embodiments of the present disclosure.

3GPP SA2 Rel-19 Study in AIML

The 3GPP has agreed a study item for Rel-19 AIML topic in SP-231800 - "Study on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML), 3GPP TSG SA Meeting #102, 11-15 December 2023, Edinburgh, UK".

The study lists so called work tasks (WT) which define specific aspects that are to be investigated, where WT3 is described as follows:

- 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.

- WT3.2 - Study prediction, detection, prevention, and mitigation of network abnormal behaviours i.e. signalling storm with the assistance of NWDAF.

The Network Data Analytics Function framework is defined in 3GPP TS 23.288. The specification describes how the NWDAF can be used to obtain analytics (and/or predictions) for well-defined set of parameters. For example, section 6.9 defines the QoS Sustainability Analytics as follows:

The consumer of QoS Sustainability analytics may request the NWDAF analytics information regarding the QoS change statistics for an Analytics target period in the past in a certain area or the likelihood of a QoS change for an Analytics target period in the future in a certain area. The consumer can request either to subscribe to notifications (i.e. a Subscribe-Notify model) or to a single notification (i.e. a Request-Response model).

The inputs and outputs of the analytics are further defined in aforementioned 3GPP specification.

According to the present invention there is provided a method, as set forth in the appended claims. Also provided is a network. Other features of the invention will be apparent from the dependent claims, and the description that follows.

Lack of solutions for enhanced QoS setup with NWDAF assistance

There are no current solutions which have been proposed for the WT indicated above, in particular one that can be used as an enhancement for QoS flow setup.

The following is one example of a scenario that can be used to describe a use case which can benefit from further enhancements.

A UE may setup a PDU session after it registers with the 5GS. Each PDU session is necessarily associated with a so called default QoS rule which in turn provides a default QoS treatment for data flows. The characteristics of the default QoS is determined by the so called subscribed default values (for parameters such as 5QI, ARP) which the SMF may obtain from the UDM.

The characteristics of a default QoS rule, and hence default QoS flow, may not be able to support requirements for applications like video streaming or video conferencing, etc. The default values may be sufficient for basic browsing or instant messaging over IP whereas video streaming applications will then require better QoS treatment e.g. using QoS flows which are for Guaranteed Bit Rate (GBR) or which are characterized by certain 5QI values even for the case of non-GBR QoS flows. Further parameters and details related to QoS can be found in 3GPP TS 23.501.

When such flows are required due to the use of an application in the UE, the UE would normally send a NAS message to modify the PDU session and thereby request to establish a new QoS with the required characteristics. This results in a few NAS signalling messages between the UE and the SMF, and also requires signalling between the SMF, UPF, RAN, and eventually results in RRC messages between the RAN and the UE. As such a modification of a PDU session can indeed result in system-wide signalling. Figure 1, taken from 3GPP TS 23.502 shows the overall signalling that can be associated with a PDU session modification procedure.

Figure 1A and Figure 1B illustrates overall signalling based on a prior art procedure for session modification from 3GPP TS 23.502.

The procedure in figure 1A follows table 1 below. Table 1 describes the procedure for UE or network requested PDU session modification described in TS 23.502.

1. The procedure may be triggered by following events:
1a. (UE initiated modification) The UE initiates the PDU Session Modification procedure by the transmission of an NAS message (N1 SM container (PDU Session Modification Request (PDU session ID, Packet Filters, Operation, Requested QoS, Segregation, 5GSM Core Network Capability, Number Of Packet Filters, [URSP rule enforcement reports], [Always-on PDU Session Requested], [Requested Non-3GPP Delay Budget])), PDU Session ID, UE Integrity Protection Maximum Data Rate, [Port Management Information Container]) message. Depending on the Access Type, if the UE was in CM-IDLE state, this SM-NAS message is preceded by the Service Request procedure. The NAS message is forwarded by the (R)AN to the AMF with an indication of User location Information. The AMF invokes Nsmf_PDUSession_UpdateSMContext (SM Context ID, N1 SM container (PDU Session Modification Request)).
When the UE requests specific QoS handling for selected SDF(s), the PDU Session Modification Request includes Packet Filters describing the SDF(s), the requested Packet Filter Operation (add, modify, delete) on the indicated Packet Filters, the Requested QoS and optionally a Segregation indication. The Segregation indication is included when the UE recommends to the network to bind the applicable SDF(s) on a distinct and dedicated QoS Flow e.g. even if an existing QoS Flow can support the requested QoS. The network should abide by the UE request, but is allowed to proceed instead with binding the selected SDF(s) on an existing QoS Flow.
NOTE　1: Only one QoS Flow is used for traffic segregation. If UE makes subsequent requests for segregation of additional SDF(s), the additional SDF(s) are multiplexed on the existing QoS Flow that is used for segregation.
The UE shall not trigger a PDU Session Modification procedure for a PDU Session corresponding to a LADN when the UE is outside the area of availability of the LADN.
The PS Data Off status, if changed, shall be included in the PCO in the PDU Session Modification Request message.
For a PDU Session which was established in the EPS, when the UE moves from EPS to 5GS for the first time, the UE includes an Always-on PDU Session Requested indication in the PDU Session Modification Request message if it wants to change the PDU Session to an always-on PDU Session.
If UE supports to report URSP rule enforcement to network, when the UE associates a newly detected application to an existing PDU Session based on URSP evaluation result and the matched URSP rule included the Indication for reporting URSP rule enforcement, the UE may initiate PDU Session Modification procedure to provide URSP rule enforcement report as described in clause　6.6.2.4 of TS　23.503　[20].
When PCF is deployed, the SMF shall further report the PS Data Off status to PCF if the PS Data Off event trigger is provisioned, the additional behaviour of SMF and PCF for 3GPP PS Data Off is defined in TS　23.503　[20].
The 5GSM Core Network Capability is provided by the UE and handled by SMF as defined in clause　5.4.4b of TS　23.501　[2].
The UE Integrity Protection Maximum Data Rate indicates the maximum data rate up to which the UE can support UP integrity protection. It is set as defined in TS　23.501　[2].
The Number Of Packet Filters indicates the number of supported packet filters for signalled QoS rules as described in clause　5.17.2.2.2 of TS　23.501　[2].
When it moves from EPS to 5GS for the first time, a UE that supports EAS re-discovery as described in clause　6.2.3.3 of TS　23.548　[74], may indicate so in the PCO.
When it moves from EPS to 5GS for the first time, a UE that hosts the EDC functionality shall indicate in the PCO its capability to support the EDC functionality (see clause　5.2.1 of TS　23.548　[74]).
Port Management Information Container may be received from DS-TT and includes DS-TT port related management information as defined in clause　5.28.3 of TS　23.501　[2].
1b. (PCF initiated SM Policy Association Modification) The PCF performs a PCF initiated SM Policy Association Modification procedure as defined in clause　4.16.5.2 to notify SMF about the modification of policies. This may e.g. have been triggered by a policy decision or upon AF requests, e.g. Application Function influence on traffic routing as described in step　5 in clause　4.3.6.2 or AF to provide Port management information Container.
If QoS Monitoring is requested by the AF, the PCF generates the QoS Monitoring policy for the corresponding service data flow and provides the policy in the PCC rules to the SMF in this step.
If Periodicity is provided by the AF, the PCF provides the Periodicity information in the PCC rules. Based on operator's local policies, the PCF sends to the SMF an indication in the PCC Rule to perform N6 Traffic Parameter Measurements for N6 Jitter and, if not received from the AF, also UL and/ or DL Periodicity measurements.
The PCF may provision a PDU Set Control Information and Protocol Description as described in clause　6.1.3.27.4 of TS　23.503　[20] within PCC Rules based on the information provided by the AF and/or the local operator policies.
The PCF may provision a Data Burst Handing Information and DL Protocol Description as described in clause　6.3.1 of TS　23.503　[20] within PCC Rules based on the information provided by the AF and/or the local operator policies.
1c. (SMF requested modification) The UDM updates the subscription data of SMF by Nudm_SDM_Notification (SUPI, Session Management Subscription Data). The SMF updates the Session Management Subscription Data and acknowledges the UDM by returning an Ack with (SUPI).
1d. (SMF requested modification) The SMF may decide to modify PDU Session. This procedure also may be triggered based on locally configured policy or triggered from the (R)AN (see clause　4.2.6 and clause　4.9.1). It may also be triggered if the UP connection is activated (as described in Service Request procedure) and the SMF has marked that the status of one or more QoS Flows are deleted in the 5GC but not synchronized with the UE yet. It may also be triggered to update QoS profile in the NG RAN and PDU Set information marking in the PSA UPF upon completion of mobility procedure as defined in clause　5.37.5.3 of TS　23.501　[2].
If interworking with TSN deployed in the transport network is supported and either the UPF supports CN-TL or NG-RAN supports AN-TL (see clause　4.4.8 of TS　23.501　[2]), the procedure may be triggered due to reception of Status group from TN CNC.
The SMF may decide to modify PDU Session to send updated ECS Address Configuration Information to the UE as defined in clause　6.5.2 of TS　23.548　[74].
The SMF may decide to modify PDU Session to send updated DNS server address to the UE as defined in clause　6.2.3.2.3 of TS　23.548　[74].
The SMF may decide to modify PDU Session to send the EAS rediscovery indication to the UE as defined in clause　6.2.3.3 of TS　23.548　[74].
If the SMF receives one of the triggers in step 1b ~ 1d, the SMF starts SMF requested PDU Session Modification procedure.
1e. (AN initiated modification) (R)AN shall indicate to the SMF when the AN resources onto which a QoS Flow is mapped are released irrespective of whether notification control is configured. (R)AN sends the N2 message (PDU Session ID, N2 SM information) to the AMF. The N2 SM information includes the QFI, User location Information and an indication that the QoS Flow is released. The AMF invokes Nsmf_PDUSession_UpdateSMContext (SM Context ID, N2 SM information).
(AN initiated notification control) If notification control is configured for a GBR QoS Flow, (R)AN sends a N2 message (PDU Session ID, N2 SM information) to SMF when the (R)AN decides the QoS targets of the QoS Flow cannot be fulfilled or can be fulfilled again, respectively. The N2 SM information includes the QFI and an indication that the QoS targets for that QoS Flow cannot be fulfilled or can be fulfilled again, respectively. When QoS targets cannot be fulfilled, the N2 SM information indicates a reference to the Alternative QoS Profile matching the values of the QoS parameters that the NG-RAN is currently fulfilling as specified in clause　5.7.2.4 of TS　23.501　[2]. If the QoS Flow has a TSCAI including Capability for BAT adaptation and without Burst Arrival Time, the N2 SM information can also include a BAT offset as described in clause　5.27.2.5 of TS　23.501　[2]. The AMF invokes Nsmf_PDUSession_UpdateSMContext (SM Context ID, N2 SM information). If the PCF has subscribed to the event, SMF reports this event to the PCF for each PCC Rule for which notification control is set in step　2.
1f. (AMF initiated modification) If the UE supports CE mode B and use of CE mode changes from restricted to unrestricted or vice versa in the Enhanced Coverage Restriction information in the UE context in the AMF and the UE has already established PDU sessions, then the AMF shall trigger a PDU session modification to the SMFs serving the UE's PDU sessions when the AMF determines that NAS-SM timer shall be updated due to the change of Enhanced Coverage Restriction and include the extended NAS-SM indication only if use of CE mode B is now unrestricted in the Enhanced Coverage Restriction information in the UE context in the AMF.
If the AMF, based on configuration, is aware that the UE is accessing over a gNB using GEO satellite backhaul and GEO Satellite ID needs to be updated to the SMF, the AMF may, based on configuration, include the latest GEO Satellite ID as described in clause　5.43.2 of TS　23.501　[2].
1g. (AMF initiated modification) the AMF informs the SMF of updates of the NWDAF ID(s) used for UE related Analytics and corresponding Analytics ID(s). Also, If the PCF request notification of SM Policy Association and there is any PDU Session established to that DNN, S-NSSAI [PCF binding information, notification of SM Policy Association establishment Indication].
1h. (AMF initiated modification) When the AMF determines that the S-NSSAI is to be replaced with an Alternative S-NSSAI (as described in clause　5.15.19 of TS　23.501　[2]), the AMF invokes Nsmf_PDUSession_UpdateSMContext Request (SM Context ID, S-NSSAI, Alternative S-NSSAI) to the SMF of the PDU session associated with the S-NSSAI.
(AMF initiated modification) When the AMF determines that the S-NSSAI is subject to area restriction, e.g. when the S-NSSAI is configured with an NS-AoS, or when the S-NSSAI is present in the Partially Allowed NSSAI, the AMF invokes Nsmf_PDUSession_UpdateSMContext Request (SM Context ID, S-NSSAI, Slice Area Restriction indication) to the SMF indicating that the PDU Session is subject to area restriction for the S-NSSAI. If the S-NSSAI is replaced with the Alternative S-NSSAI, the AMF checks the area restriction only for the Replaced S-NSSAI for this PDU Session.
Based on the extended NAS-SM timer indication, the SMF shall use the extended NAS-SM timer setting for the UE as specified in TS　24.501　[25].
2. The SMF may need to report some subscribed event to the PCF by performing an SMF initiated SM Policy Association Modification procedure as defined in clause　4.16.5.1. This step may be skipped if PDU Session Modification procedure is triggered by step 1b or 1d. If dynamic PCC is not deployed, the SMF may apply local policy to decide whether to change the QoS profile.
The PCF may make policy control decisions based on the awareness of URSP rule enforcement, as described in clause　6.1.1.5 in TS　23.503　[20].
Steps 2a to 7 are not invoked when the PDU Session Modification requires only action at a UPF (e.g. gating).
2a. The SMF may update the UPF with N4 Rules related to new or modified QoS Flow(s).
NOTE　2: This allows the UL packets with the QFI of a new or modified QoS Flow to be transferred.
If the SMF initiated the PDU Session Modification procedure in step　1b due to PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with a TSC Assistance Container and if interworking with TSN deployed in the transport network is supported, the SMF may instruct the UPF to assign or remove a distinct N3 tunnel end point address for the QoS Flow(s) assigned with a TSC Assistance Container.
If the SMF initiated the PDU Session Modification procedure in step　1d due to reception of Status group from TN CNC, the SMF includes a TL-Container with a set-request to the N4 Session Modification request that is sent to the UPF, as described in clause　5.28a.2 of TS　23.501　[2].
If the SMF initiated the PDU Session Modification procedure in step　1b due to PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with UL and/or DL Periodicity, the SMF composes the TSCAI with the periodicity information.
If the SMF initiated the PDU Session Modification procedure in step　1b due to PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with an indication to perform N6 Traffic Parameter measurements (e.g. the N6 Jitter range associated with the DL Periodicity, and the UL/DL periodicity), the SMF instructs the UPF to perform N6 Traffic Parameter measurement associated with the DL Periodicity for the QoS Flow, as described in clause　5.37.8.2 of TS　23.501　[2].
If N6 Traffic Parameter measurements are requested and DL Periodicity is received in the PCC Rule, the SMF shall include the DL Periodicity as well as the indication of N6 Traffic Parameter measurement in the request to the UPF, see clause　5.8.5.11 of TS　23.501　[2].
If the PCC Rule includes a Protocol Description and PDU Set QoS parameters for DL and the SMF decides to enable PDU Set Identification and marking for PDU Set based Handling by PSA UPF, the SMF should provide the Protocol Description information and PDU Set Marking indication to the UPF and request the UPF to mark the PDU Set Information in each PDU belonging to the PDU Sets as described in clause　5.37.5.2 and 5.8.5.4 of TS　23.501　[2].
If the SMF decides to enable End of Data Burst marking by PSA UPF, the SMF should request the UPF to mark End of Data Burst as described in clause　5.37.8.3 of TS　23.501　[2] . If the PCC Rule includes a Protocol Description, the SMF should provide the Protocol Description information to the UPF.
If the PDU Set information marking has been activated in the UPF for a QoS flow, the SMF may request the UPF to stop the marking of the PDU Set information based on the indication from the RAN or PCF, e.g. if the Target RAN does not support the PDU Set based handling as described in clause　5.37.5.3 of TS　23.501　[2].
If the PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with PDU Set Control Information, the SMF performs PDU Set based QoS handling, see clause　5.37.5 of TS　23.501　[2].
If redundant transmission has not been activated to the PDU session and the SMF decides to perform redundant transmission for the QoS Flow, the SMF indicates to the UPF to perform packet duplication and elimination for the QoS Flow.
If redundant transmission has been activated on the PDU Session and the SMF decides to stop redundant transmission, the SMF indicates the UPF to release the CN Tunnel Info which is used as the redundancy tunnel of the PDU Session and also indicates the UPF to stop packet duplication and elimination for the corresponding QoS Flow(s).
NOTE　3: The method to perform elimination and reordering on RAN/UPF based on the packets received from the two GTP-U tunnels is up to RAN/UPF implementation. The two GTP-U tunnels are terminated at the same RAN node and UPF.
If redundant transmission has not been activated to the PDU Session and the SMF decides to perform redundant transmission for the QoS Flow with two I-UPFs between the PSA UPF and the NG-RAN, the SMF sends a N4 Session Establishment Request message to the I-UPFs including UL CN Tunnel Info of the PSA UPF and a request to allocate CN Tunnel Info.
SMF may make use of Redundant Transmission Experience analytics provided by NWDAF, when SMF takes a decision whether to perform redundant transmission, or stop redundant transmission if it had been activated, as described in clause　6.13 of TS　23.288　[50].
If the AMF initiated the PDU Session Modification procedure in step　1h due to network slice replacement with the Alternative S-NSSAI and if the SMF determines that the PDU Session is retained, the SMF sends N4 Session Modification request message to the UPF to replace the S-NSSAI with the Alternative S-NSSAI, as described in clause　5.15.19 of TS　23.501　[2].
2b. The UPF(s) respond to the SMF. If redundant transmission has not been activated to the PDU session and the SMF indicated the UPF to perform packet duplication and elimination for the QoS Flow in step　2a, the UPF allocates an additional CN Tunnel Info. The additional CN Tunnel Info is provided to the SMF.
If redundant transmission has not been activated to the PDU Session and the SMF decides to perform redundant transmission for the QoS Flow with two I-UPFs in step　2a, the UPFs allocate CN Tunnel Info. The CN Tunnel Info of each I-UPF is provided to the SMF.
If interworking with TSN deployed in the transport network is supported and the UPF supports CN-TL and received a TL-Container with a set-request from the SMF/CUC in step　2a (see clause　4.4.8 of TS　23.501　[2]), the UPF/CN-TL includes a TL-Container with a set-response to the N4 Session Modification response, as described in clause　5.28a.2 of TS　23.501　[2].
If requested by SMF in step　2a, the PSA UPF will initiate N4 Session Level reporting for N6 Traffic Parameter Measurement Report as described in clause　4.4.2.2. If N6 Traffic Parameter(s) are available then the response to the SMF in this step　may include the N6 Traffic Parameter(s) (e.g. the N6 Jitter range associated with the DL Periodicity, and the UL/DL periodicity) for the QoS Flow (see clause　5.37.8.2 of TS　23.501　[2]). The SMF composes the TSCAI with the received N6 Traffic Parameters.
3a. For UE or AN initiated modification or AMF initiated modification, the SMF responds to the AMF through Nsmf_PDUSession_UpdateSMContext Response ([N2 SM information (PDU Session ID, QFI(s), QoS Profile(s), [Alternative QoS Profile(s)], Session-AMBR], [CN Tunnel Info(s)]), N1 SM container (PDU Session Modification Command (PDU Session ID, QoS rule(s) and associated UL Protocol Description(s) (if available), QoS rule operation, QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), Session-AMBR, [Always-on PDU Session Granted], [Port Management Information Container], [Non-3GPP QoS Assistance Information Container]))). See clause　5.7 of TS　23.501　[2] for the QoS Profile, Alternative QoS Profile and QoS rule and QoS Flow level QoS parameters. Alternative QoS Profile is only valid for AN initiated modification.
If the PDU Session Modification was requested by the UE to modify a PDU Session to an always-on PDU Session, the SMF shall include an Always-on PDU Session Granted indication in the PDU Session Modification Command to indicate whether the PDU Session is to be changed to an always-on PDU Session or not via the Always-on PDU Session Granted indication in the PDU Session Modification Command.
The N2 SM information carries information that the AMF shall provide to the (R)AN. It may include the QoS profiles and the corresponding QFIs to notify the (R)AN that one or more QoS flows were added, or modified. It may include only QFI(s) to notify the (R)AN that one or more QoS flows were removed. The SMF may indicate for each QoS Flow whether redundant transmission shall be performed by a corresponding redundant transmission indicator. If the SMF decides to activate redundant transmission in step　2a, the SMF includes the allocated additional CN Tunnel Info in the N2 SM information. If the SMF decides to perform redundant transmission for new QoS Flow with two I-UPFs in step　2a, the SMF includes the allocated CN Tunnel Info of the two I-UPFs in the N2 SM information. If the PDU Session Modification was triggered by the (R)AN Release in step　1e the N2 SM information carries an acknowledgement of the (R)AN Release. If the PDU Session Modification was requested by the UE for a PDU Session that has no established User Plane resources, the N2 SM information provided to the (R)AN includes information for establishment of User Plane resources. For Network Slice Replacement if the SMF determines that the PDU Session is to be retained, the S-NSSAI in N2 SM information is set to Alternative S-NSSAI.
- If the SMF has received a Requested Non-3GPP Delay Budget for a QoS flow from the PEGC, the SMF may adjust the dynamic CN PDB signalled to the NG-RAN as defined in clause　5.44.3.4 of TS　23.501　[2].
If redundant transmission has been activated on the PDU Session and the SMF decides to stop redundant transmission in step　2a, the SMF indicates the (R)AN to release the AN Tunnel and stop packet duplication and elimination associated with the redundancy tunnel of the PDU Session.
The N1 SM container carries the PDU Session Modification Command that the AMF shall provide to the UE. It may include the QoS rules and associated UL Protocol Description(s) (if available), QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) and corresponding QoS rule operation and QoS Flow level QoS parameters operation to notify the UE that one or more QoS rules were added, removed or modified. If the PCF provides the PCC rules with Protocol Description for UL in step　2, based on operator policy, the SMF may additionally provide the Protocol Description for UL with the associated QoS rule as described in clause　5.37.5.1 of TS　23.501　[2].
For the AMF initiated the PDU Session Modification procedure in step　1h due to network slice replacement, and if the SMF determines that the PDU Session is to be retained, the SMF includes the Alternative S-NSSAI in the PDU Session Modification Command to the UE and a cause value indicating that the S-NSSAI of the PDU Session is replaced with the Alternative S-NSSAI.
If the AMF initiated the PDU Session Modification procedure in step　1h due to network slice replacement and if the PDU Session is SSC mode 3 and if the SMF determines that the PDU Session is to be re-established on the Alternative S-NSSAI, the SMF includes the Alternative S-NSSAI in the PDU Session Modification Command to the UE and a cause value indicating that a PDU Session re-establishment on the Alternative S-NSSAI is required. The UE re-establishes a new PDU Session on the Alternative S-NSSAI, as described in clause　5.15.19 in TS　23.501　[2]. If the PDU Session is SSC mode 1 or SSC mode 2, the SMF may initiate release of the PDU Session as described in clause　4.3.4.2.
If port number and a Port Management Information Container have been received from PCF in Step 2 and the port number matches the port number assigned for the DS-TT port for this PDU session, then SMF includes the Port Management Information Container in the N1 SM container.
The SMF may need to send transparently through NG-RAN the PDU Session Modification Command to inform the UE about changes in the QoS parameters (i.e. 5QI, GFBR, MFBR) that the NG-RAN is currently fulfilling after the SMF receives QoS Notification Control as defined in clause　5.7.2.4 of TS　23.501　[2]. When the SMF sends on the PDU Session Modification Command transparently through NG-RAN, the N2 SM information is not included as part of the Namf_Communication_N1N2MessageTransfer.
If the UE indicated in the PCO that it supports the EDC functionality, the SMF may indicate to the UE either that the use of the EDC functionality is allowed for the PDU Session or that the use of the EDC functionality is required for the PDU Session (see clause　5.2.1 of TS　23.548　[74]).
Based on the S-NSSAI and DNN for PIN, the SMF may provide the UE with per QoS-flow Non-3GPP QoS Assistance Information in the N1 SM container.
If SMF receives the indication indicating that the PDU Session is subject to area restriction for the S-NSSAI, and if SMF has not subscribed before, the SMF subscribes to "UE mobility event notification" event for reporting UE presence in Area of Interest by providing the S-NSSAI as an indicator for the Area Of Interest (see clauses 5.6.11 and 5.3.4.4 of TS　23.501　[2]).
If SMF does not receive the indication indicating that the PDU Session is subject to area restriction for the S-NSSAI, and if the SMF has subscribed the "UE mobility event notification" event in the AMF before, the SMF may unsubscribe "UE mobility event notification" event in the AMF.
3b. For SMF requested modification, the SMF invokes Namf_Communication_N1N2MessageTransfer ([N2 SM information] (PDU Session ID, QFI(s), QoS Profile(s), [Alternative QoS Profile(s)], Session-AMBR, [CN Tunnel Info(s)], QoS Monitoring indication, QoS Monitoring reporting frequency, QoS monitoring parameter), [TSCAI(s)], TL-Container(s), [ECN marking for L4S indicator(s)]), N1 SM container (PDU Session Modification Command (PDU Session ID, QoS rule(s) and associated UL Protocol Description(s) (if available), QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), QoS rule operation and QoS Flow level QoS parameters operation, Session-AMBR))).
- For each QoS Flow, the SMF may at most request one of the following to the NG-RAN:
- ECN marking for L4S indicator at NG-RAN in the case of ECN marking for L4S in RAN as described in clause　5.37.3 of TS　23.501　[2]; or
- Congestion information monitoring as described in clauses 5.45.3 and 5.37.4 of TS　23.501　[2]; or
- provide information for ECN marking for L4S at UPF in the case of ECN marking for L4S by PSA UPF as described in clause　5.37.3 of TS　23.501　[2].
If the SMF initiated the PDU Session Modification procedure in step　1b due to PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with a TSC Assistance Container and if interworking with TSN deployed in the transport network is supported, the SMF may instruct the NG-RAN to assign or remove a distinct N3 tunnel end point address for the QoS Flow(s) assigned with a TSC Assistance Container.
The SMF may indicate for each QoS Flow whether redundant transmission shall be performed by a corresponding redundant transmission indicator. If the SMF decides to activate redundant transmission in step　2a, the SMF includes the allocated additional CN Tunnel Info in the N2 SM information. If the SMF decides to perform redundant transmission for new QoS Flow with two I-UPFs in step　2a, the SMF includes the allocated CN Tunnel Info of the two I-UPFs in the N2 SM information.
If redundant transmission has been activated on the PDU Session and the SMF decides to stop redundant transmission in step　2a, the SMF indicates the (R)AN to release the AN Tunnel and stop packet duplication and elimination associated with the redundancy tunnel of the PDU Session.
The SMF indicates the request for QoS Monitoring for the QoS Flow according to the information received from the PCF in step　1b, or based on SMF local policy, e.g. when the RAN rejected the creation of a specific QoS Flow. In the case of receiving the QoS Monitoring indication, the RAN enables the RAN part of UL/DL packet delay measurement for the QoS Flow and the QoS Monitoring reporting frequency is used by RAN to determine the packet delay measurement frequency of the RAN part. In the case of receiving a congestion information request, RAN initiates reporting of UL and/or DL QoS Flow congestion information to PSA UPF as defined in clause　5.45.3 of TS　23.501　[2]. The TSCAI is defined in clause　5.27.2 of TS　23.501　[2].
If the SMF initiated the PDU Session Modification procedure in step　1d due to reception of Status group from TN CNC, the SMF includes a TL-Container with a set-request to the N2 SM information, as described in clause　5.28a.2 of TS　23.501　[2].
The SMF indicates EAS rediscovery indication to the UE, if that initiated the PDU Session Modification procedure in step　1d as defined in clause　6.2.3.3 of TS　23.548　[74].
If the UE is in CM-IDLE state and an ATC is activated, the AMF updates and stores the UE context based on the Namf_Communication_N1N2MessageTransfer and steps 4, 5, 6 and 7 are skipped. When the UE is reachable e.g. when the UE enters CM-CONNECTED state, the AMF forwards the N1 message to synchronize the UE context with the UE.
If the PCF provides the PCC rules with Protocol Description for UL in step　2, based on operator policy, the SMF may provide the Protocol Description(s) for UL with the associated QoS rule(s) as described in clause　5.37.5.1 of TS　23.501　[2].
3c. For SMF requested modification due to updated SMF-Associated parameters from the UDM, the SMF may provide the SMF derived CN assisted RAN parameters tuning to the AMF. The SMF invokes Nsmf_PDUSession_SMContextStatusNotify (SMF derived CN assisted RAN parameters tuning) towards the AMF. The AMF stores the SMF derived CN assisted RAN parameters tuning in the associated PDU Session context for this UE.
3d. For SMF requested modification due to updated NWDAF ID, the SMF informs the AMF of updates of the NWDAF ID(s) used for UE related Analytics and corresponding Analytics ID(s).
4. The AMF may send N2 ([N2 SM information received from SMF], NAS message (PDU Session ID, N1 SM container (PDU Session Modification Command))) Message to the (R)AN.
5. The (R)AN may issue AN specific signalling exchange with the UE that is related with the information received from SMF. For example, in the case of a NG-RAN, an RRC Connection Reconfiguration may take place with the UE modifying the necessary (R)AN resources related to the PDU Session or if only N1 SM container is received in step　4 from AMF, RAN transports only the N1 SM container to the UE.
The (R)AN may consider the updated CN assisted RAN parameters tuning to reconfigure the AS parameters.
As part of this, the N1 SM container is provided to the UE. If the N1 SM container includes a Port Management Information Container then the UE provides the container to DS-TT.
If new DNS server address is provided to the UE in the PCO, the UE can refresh all EAS(s) information (e.g. DNS cache) bound to the PDU Session, based on UE implementation as described in clause　6.2.3.2.3 of TS　23.548　[74].
If EAS rediscovery indication is provided to the UE, the UE can trigger EAS rediscovery procedure as defined in clause　6.2.3.3 of TS　23.548　[74].
6. The (R)AN may acknowledge N2 PDU Session Request by sending a N2 PDU Session Ack (N2 SM information (List of accepted/rejected QFI(s), AN Tunnel Info, PDU Session ID, Secondary RAT usage data, TL-Container(s), BAT offset, Periodicity, established QoS Flows status (active/not active) (for one of the following: congestion information monitoring, ECN marking for L4S at PSA UPF, ECN marking for L4S at NG-RAN), PDU Set Based Handling Support Indication), User location Information) Message to the AMF. In the case of Dual Connectivity, if one or more QFIs were added to the PDU Session, the Master RAN node may assign one or more of these QFIs to a NG-RAN node which was not involved in the PDU Session earlier. In this case the AN Tunnel Info includes a new N3 tunnel endpoint for QFIs assigned to the new NG-RAN node. Correspondingly, if one or more QFIs were removed from the PDU Session, a (R)AN node may no longer be involved in the PDU Session anymore and the corresponding tunnel endpoint is removed from the AN Tunnel Info. The NG-RAN may reject QFI(s) if it cannot fulfil the User Plane Security Enforcement information for a corresponding QoS Profile, e.g. due to the UE Integrity Protection Maximum Data Rate being exceeded. When receiving the request for QoS Monitoring, the (R)AN may indicate its rejection to perform QoS Monitoring, e.g. due to the (R)AN load condition. The (R)AN may reject the addition or modification of a QoS Flow, e.g. due to handling of the UE-Slice-MBR as described in clause　5.7.1.10 of TS　23.501　[2]. If the (R)AN rejects the addition or modification of a QoS Flow, the SMF is responsible of updating the QoS rules and QoS Flow level QoS parameters associated to that QoS Flow in the UE accordingly. NG-RAN includes the PDU Set Based Handling Support Indication in N2 SM information as defined in clause　5.37.5.3 of TS　23.501　[2]
If the PLMN has configured secondary RAT usage reporting, the NG-RAN node may provide RAN Usage Data Report. The User Location Information shall include the serving cell's ID and if Dual Connectivity is activated for the UE, the PSCell ID.
If the redundant transmission has not been activated to the PDU session and the SMF indicates to the RAN that one of the QoS Flow shall perform redundant transmission, the RAN includes an additional AN tunnel info in N2 SM information.
If interworking with TSN deployed in the transport network is supported and the NG-RAN supports AN-TL and received a TL-Container with a set-request from the SM/CUC in step　3b (see clause　4.4.8 of TS　23.501　[2]), the NG-RAN/AN-TL includes a TL-Container with a set-response to the N2 SM information, as described in clause　5.28a.2 of TS　23.501　[2].
If the NG-RAN has determined a BAT offset and optionally a periodicity as described in clause　5.27.2.5 of TS　23.501　[2], the NG-RAN provides the BAT offset and optionally the periodicity in the N2 SM information.

The procedure in figure 1B follows table 2 below. Table 2 describes the procedure for UE or network requested PDU session modification described in TS 23.502 following Figure 1A.

7. The AMF forwards the N2 SM information and the User location Information received from the AN to the SMF via Nsmf_PDUSession_UpdateSMContext service operation. The SMF replies with a Nsmf_PDUSession_UpdateSMContext Response.
If the N2 SM information indicates failure of whole N2 SM request (i.e. no part of the N2 SM request is successful in (R)AN), the SMF assumes that the NAS PDU, if provided in step　3, was not forwarded by NG-RAN to UE, as described in TS　38.413　[10]. In this case, if the PDU Session modification is UE triggered the SMF shall reject the PDU session modification by including a N1 SM container with a PDU Session Modification Reject message (see clause　8.3.3 of TS　24.501　[25]) in the Nsmf_PDUSession_UpdateSMContext Response in step　7b. Step　8 is skipped in this case.
Otherwise, the SMF assumes that the NAS PDU was sent to UE successfully. If the (R)AN rejects QFI(s), the SMF is responsible of updating the QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) in the UE accordingly, i.e. the SMF shall trigger a separate NAS PDU Session Modification procedure after step　11 to align the SM context of this PDU Session in UE.
8. The SMF may update N4 session of the UPF(s) that are involved by the PDU Session Modification by sending N4 Session Modification Request message to the UPF (see NOTE　3).
The SMF may update the UPF with N4 Rules related to new, modified or removed QoS Flow(s), unless it was done already in step　2a.
NOTE　4: This allows the DL packets of the new or modified QoS Flow to be transferred.
If an additional AN Tunnel Info is returned by RAN in step　6, the SMF informs the UPF about this AN Tunnel Info for redundant transmission. In the case of redundant transmission with two I-UPFs, the SMF provides AN Tunnel Info to two I-UPFs. If CN Tunnel Info of two I-UPFs is allocated by the UPFs in step　2b, the SMF also provides the DL CN Tunnel Info of two I-UPFs to the UPF (PSA).
If the QoS Monitoring is enabled for the QoS Flow, the SMF provides the N4 rules containing the QoS Monitoring policy generated according to the information received in step　1b to the UPF via the N4 Session Modification Request message as defined in clause　5.45 of TS　23.501　[2].
If port number and a Port Management Information Container have been received from PCF in Step 2 and the port number matches the port number of the NW-TT port for this PDU session, then SMF includes the Port Management Information Container in the N4 Session Modification Request. If the N4 Session Modification Request includes a Port Management Information Container, then UPF also includes a Port Management Information Container in the N4 Session Modification Response.
If SMF decides to enable ECN marking for L4S by PSA UPF, a QoS Flow level ECN marking for L4S indicator shall be sent by SMF to PSA UPF over N4 as described in clause　5.37.3.3 of TS　23.501　[2].
If the N2 SM information includes the PDU Set Based Handling Support Indication and there are PCC Rules with PDU Set QoS parameters for DL, SMF configures PSA UPF to activate PDU set identification and marking for the QoS flow as described in clause　5.37.5.3 of TS　23.501　[2].
9. The UE acknowledges the PDU Session Modification Command by sending a NAS message (PDU Session ID, N1 SM container (PDU Session Modification Command Ack, [Port Management Information Container])) message.
10. The (R)AN forwards the NAS message to the AMF.
11. The AMF forwards the N1 SM container (PDU Session Modification Command Ack) and User Location Information received from the AN to the SMF via Nsmf_PDUSession_UpdateSMContext service operation. The SMF replies with a Nsmf_PDUSession_UpdateSMContext Response.
If the SMF initiated modification is to delete QoS Flows (e.g. triggered by PCF) which do not include QoS Flow associated with the default QoS rule and the SMF does not receive response from the UE, the SMF marks that the status of those QoS Flows is to be synchronized with the UE.
If interworking with TSN deployed in the transport network is supported, for any QoS Flow including a TSC Assistance Container, the SMF/CUC derives the merged stream requirements as described in Annex　M of TS　23.501　[2]. If AN-TL and CN-TL are supported, the SMF/CUC uses the information provided in the get-responses stored during the PDU Session Establishment procedure to derive the merged stream requirements. The SMF/CUC interacts with the CNC deployed in the transport network and provides the merged stream requirements in the Talker and Listener groups to the TN CNC. The TN CNC uses the merged stream requirements as input to select respective path(s) and calculate schedules in TN.
Based on the processing results, the TN CNC provides a Status group that contains the merged end station communication-configuration back to the SMF/CUC.
12. The SMF may update N4 session of the UPF(s) that are involved by the PDU Session Modification by sending N4 Session Modification Request (N4 Session ID) message to the UPF. For a PDU Session of Ethernet PDU Session Type, the SMF may notify the UPF to add or remove Ethernet Packet Filter Set(s) and forwarding rule(s).
NOTE　5: The UPFs that are impacted in the PDU Session Modification procedure depends on the modified QoS parameters and on the deployment. For example in the case of the session AMBR of a PDU Session with an UL CL changes, only the UL CL is involved. This note also applies to the step　8.
13. If the SMF interacted with the PCF in step 1b or 2, the SMF notifies the PCF whether the PCC decision could be enforced or not by performing an SMF initiated SM Policy Association Modification procedure as defined in clause　4.16.5.1. If the trigger for 5GS Bridge/Router information available is armed and the SMF received a Port Management Information Container from either UE or UPF, then SMF provides the Port Management Information Container and the port number of the related port to the PCF in this step, as described in clause　5.28.3.2 of TS　23.501　[2]. If the trigger for 5GS Bridge/Router information available is armed and the SMF received the User Plane node Management Information Container from UPF, then the SMF provides the User Plane node Management Information Container to the PCF as described in clause　5.28.3.2 of TS　23.501　[2]. If trigger for Notification on BAT offset is armed and the SMF received BAT offset and/or Periodicity from the RAN, then the SMF provides the BAT offset and/or Periodicity to the PCF as described in clause　5.27.2.5 of TS　23.501　[2].
SMF notifies any entity that has subscribed to User Location Information related with PDU Session change.
If step　1b is triggered to perform Application Function influence on traffic routing by step　5 in clause　4.3.6.2, the SMF may reconfigure the User Plane of the PDU Session as described in step　6 in clause　4.3.6.2.
If interworking with TSN deployed in the transport network is supported and if the Status group from TN CNC to SMF/CUC in step　11 includes InterfaceConfiguration and if the AN-TL/CN-TL are supported, the SMF/CUC initiates a PDU Session Modification procedure as in step　1d.

It is possible that the UE's requests for establishing a PDU session and subsequent modification of the session in order to request a new QoS flow with particular treatment are driven by a user (of the device or UE) who demonstrates some pattern in terms of frequency of use of a service, place of use of a service, and the QoS requirements that emerge from the UE as a result. For example, a UE may request a PDU session and later modify that such that a new GBR QoS flow is established for a particular time window. This may be a recurring pattern for the UE.

As such, it can be expected that a PDU session will be modified eventually (at some time) and, hence, system-wide signalling is expected to be generated as explained above.

If the NAS procedures can be predictable, then the system may benefit from analytics and predictions that would help the SMF establish the necessary QoS flows as part of one procedure instead of having multiple procedures and hence more signalling. Embodiments of the present invention seek to provide NWDAF assistance for enhancing QoS setup and reduction of signalling.

Solutions

The first aspect provides a method of Network Data Analytics Function (NWDAF) assisted Quality of Service (QoS) setup for a User Equipment (UE) in a telecommunications network, for example a 5G network, the method comprising:

using, for example at and/or during establishment of a Protocol Data Unit (PDU) session, a 5QI for a default QoS that is different from a subscribed default 5QI for the UE; and/or

returning, by the Session Management Function (SMF), for example at and/or during establishment of the PDU session, at least two QoS flows; and/or

subscribing, by the Policy Control Function (PCF), to and/or with the NWDAF for the QoS sustainability analytics.

The second aspect provides a telecommunications network configured to implement the method according to the first aspect.

Note that, herein, the term "analytics" may refer to any combination of: analytics, statistics, prediction, recommendation, information, and in any order.

For all the nodes that are proposed to use analytics, the nodes may aggregate analytics from one or more source analytics entities.

Although the solutions herein are set out using an example analytics (i.e. QoS sustainability analytics), the details can be applied with/to any other existing analytics, or new analytics, which may be used to provide similar information, statistics, predictions, etc. As such the embodiments herein are not necessarily limited to one type of analytics only. Moreover, embodiments may find utility with any existing analytics that may be enhanced in the future.

For all the embodiments herein, steps described can be applied in any order or combination.

The SMF subscribes to the QoS sustainability analytics with the NWDAF. Alternatively, or additionally, the PCF subscribes to the QoS sustainability analytics with the NWDAF

The following assumptions, which are to be considered as solutions, are set out:

* For at least one UE in question, the SMF and/ or the PCF should subscribe to or request the NWDAF for obtaining analytics (predictions) related to QoS sustainability analytics

- Note that the solutions described may also apply to all UEs or group of UEs or a list of UEs, as appropriate.

* QoS sustainability analytics might be provided by the NWDAF at UE level, i.e. average value of multiple UEs in an area, or for specific UEs.

* QoS sustainability analytics might be the analytics for the Applicable Area that the UE belongs to.

* SMF and/or PCF subscribes to or requests the QoS related parameters, e.g. QoS sustainability analytics, with the NWDAF.

* The SMF and/or PCF should trigger the storage of analytics in the Analytics Data Repository Function (ADRF) as described in 3GPP TS 23.228. The SMF and/or PCF should maintain in context the ADRF address which was used to store analytics for a (group of) UE in question. Upon a NAS 5GSM procedure, e.g. during a PDU session establishment procedure or PDU session modification procedure, the SMF and/or PCF may verify if there is an ADRF address stored for the (group of) UE in question. If yes, the SMF and/or PCF may retrieve the analytics from the ADRF optionally before the completion of the procedure (e.g. before the SMF and/or PCF responds with a NAS message to the UE, etc). How the SMF and/or PCF uses this information will be described subsequently.

- The SMF and/or PCF may be configured to operate as explained above e.g. based on local policies or OAM. Alternatively, new subscription information may be defined such that the SMF and/or PCF can behave as described above for a UE in question. For example, the subscription information may indicate that the SMF and/or PCF can behave as described above for a UE. This new subscription information may be obtained from the UDM.

For all the embodiments described herein, the details can apply to a single UE or a group or list of UEs.

At establishment of a PDU session, use a 5QI for the default QoS such that it is different from the subscribed default 5QI

The SMF and/or PCF may be configured to operate as explained below for any combination of steps or SMF and/or PCF actions. Alternatively, new subscription information may be defined such that the SMF and/or PCF can behave as described below for a UE in question. For example, this new subscription information may indicate that the SMF and/or PCF can use the method below to proactively modify the default 5QI for a UE in question, where for example the updated value is different from the subscribed default value (and optionally based on NWDAF assistance as will be described). This new subscription information may be obtained from the UDM.

The default 5QI for a UE might be also defined by the PCF and/or the SMF based on analytics information, i.e. the PCF or SMF determine the default 5QI value by considering the QoS sustainability analytics from NWDAF, optionally with the potential and existing services the UE may have, any other information related to network condition and/or performance. Therefore, to reduce the potential modification of the established QoS flow, if there are new service flow or traffic for the UE. The signalling and modification procedures within the 5GS can be reduced or optimized correspondingly.

In one example, during the establishment of a PDU session (or modification of a PDU session), the SMF and/or PCF should obtain analytics for the UE in question, where the analytics is for QoS sustainability analytics, any other potential information related to the UE (e.g. UE performance, UE traffic, mobility, UE service experience), other potential information related to network performance.

In one example, the SMF and/or PCF may verify the frequency of QoS changes that were made by the UE. For example, the SMF and/or PCF may verify Crossed Reporting Threshold parameter as described in 'Table 6.9.3-1: "QoS Sustainability" statistics' in 3GPP TS23.228.

If the SMF and/or PCF determines that the QoS change statistics (optionally for an Analytics target period in the past in a certain area or the likelihood of a QoS change for an Analytics target period in the future in a certain area) indicates that the UE may request a change of QoS, then the SMF and/or PCF may determine to use a default 5QI value for the default QoS flow that is different from the subscribed 5QI value.

With the above, the SMF and/or PCF is using modified default 5QI value such that this value is applicable to different services that the UE may request and hence the UE will not need to request this 5QI value subsequently as part of PDU session modification for creating a new QoS flow with this 5QI. Therefore, advantageously, overall signaling can be reduced in the system.

In one example, the SMF and/or PCF should verify the frequency of QoS changes that were made by the UE. For example, the SMF and/or PCF may verify Crossed Reporting Threshold parameter as described in 'Table 6.9.3-1: "QoS Sustainability" statistics' in 3GPP TS 23.228.

Figure 2 illustrates an example procedure to establish a PDU session using a modified default 5QI value based on analytics.

Note that all the details set out above apply to other QoS parameters such as ARP, etc. In other words, the SMF and/or PCF may modify the ARP value, for example, when the SMF and/or PCF determines to modify the 5QI value for the default QoS flow. The determined / modified ARP value may be based on local policies.

Note that the SMF may have different suggestion for using a modified default 5QI value e.g. based on OAM, or indication from the subscription that this value can be changed, or based on a policy rule from the PCF (Policy Control Function), or based on NWDAF assistance as explained herein. The SMF and/or PCF may be configured with a method to prioritize one of these values or sources e.g. the SMF and/or PCF may prioritize the information which is based on NWDAF over other methods for determining a modified value for the default 5QI.

Note that although the details herein are set out based on the QoS sustainability analytics, embodiments can also relate to other analytics that can provide similar information to the consumer of the analytics. Therefore, the proposals are not to be considered limited to just the QoS sustainability analytics. Moreover, specific examples are given based around the SMF, but embodiments of the invention may apply or relate to other network functions such as, particularly, the PCF. As such, references to the use of the SMF should be considered as examples only, and not a limitation. As such, all the embodiments herein can be applied for other NFs such as the PCF. In this case, the PCF may in turn provide any determined values (as will be described below) to another NF such as the SMF.

The SMF may inform the PCF that at least one 5QI value (for the default QoS rule or a non-default QoS rule) has been modified based on analytics (although not shown in Figure 2).

At established of a PDU session, the SMF returns at least two QoS flows

In one example, during the establishment of a PDU session (or modification of a PDU session), the SMF and/or PCF should obtain analytics for the UE in question, where the analytics is for QoS sustainability analytics. Alternatively, the NWDAF may perform analytics for a particular UE in question, optionally in a certain area of interest. Note that this may apply to all solutions herein.

In one example, the SMF and/or PCF should verify the frequency of QoS changes that were made by the UE. For example, the SMF may verify Crossed Reporting Threshold parameter as described in 'Table 6.9.3-1: "QoS Sustainability" statistics' in 3GPP TS23.228.

If the SMF and/or PCF determines that the QoS change statistics (optionally for an Analytics target period in the past in a certain area or the likelihood of a QoS change for an Analytics target period in the future in a certain area) indicates that the UE may request a change of QoS, then the SMF may determine to behave as follows:

* In addition to the default QoS that is established with the PDU session, the SMF and/or PCF should create or establish at least one additional QoS rule (or QoS flow) with a 5QI value that is different (and expected to be better in terms of QoS treatment) from the value of the 5QI associated with the default QoS flow.

* The SMF and/or PCF should choose a 5QI value for the additional (at least one) QoS flow such that the chosen value is similar to (or better than in terms of QoS characteristics) what the UE would have normally requested for a QoS flow which is not a default QoS flow. This information (i.e. what the UE would have normally requested) may be based on the assistance information from the NWDAF (or ARDF) that the SMF and/or PCF should verify and use to make this determination.

* In one example for the details provided above, the SMF and/or PCF should ensure that the Authorized QoS rules IE (of the PDU Session Establishment Accept message) contains at least one additional QoS rule which is not a default QoS rule, and the QFI that is indicated is associated with (or maps to) the chosen 5QI as described above. Therefore the outcome of the NAS procedure (i.e. the PDU session establishment procedure) is that the UE will receive the IE (and NAS message) such that this leads to the creation of at least two QoS rules where one is a default QoS rule (associated with a subscribed QFI/5QI value) and at least one non-default QoS rule which is associated with a QFI/5QI that the SMF and/or PCF has determined as explained above.

Note that all the details above apply to other QoS parameters such as ARP, etc. In other words, the SMF and/or PCF may modify the ARP value, for example, when the SMF and/or PCF determines to modify the 5QI value for the default QoS flow. The determined / modified ARP value may be based on local policies.

Note that the SMF and/or PCF may have different suggestion for using a modified default 5QI value e.g. based on OAM, or indication from the subscription that this value can be changed, or based on a policy rule from the PCF (Policy Control Function), or based on NWDAF assistance as explained herein. The SMF and/or PCF may be configured with a method to prioritize one of these values or sources e.g. the SMF and/or PCF may prioritize the information which is based on NWDAF over other methods for determining a modified value for the default 5QI.

Note that although the solutions herein are described based on the QoS sustainability analytics, the solutions can also apply to/with other analytics that can provide similar information to the consumer of the analytics. Therefore, the details are not to be considered limited to just the QoS sustainability analytics. Moreover, the techniques may apply to other network functions such as the PCF and so the use of the SMF should be considered as an example proposal and not a limitation. As such, all the techniques herein can be applied to other NFs such as the PCF. In this case, the PCF may in turn provide any determined values (as will be described below) to another NF such as the SMF.

At establishment of a PDU session, the SMF and/or PCF returns at least two QoS flows

The SMF and/or PCF may be configured to operate as explained below for any combination of steps or SMF and/or PCF actions. Alternatively, new subscription information may be defined such that the SMF and/or PCF can behave as described below for a UE in question. For example, this new subscription information may indicate that the SMF and/or PCF can use the proposed method below to proactively modify the default 5QI for a UE in question, where for example the updated value is different from the subscribed default value (and optionally based on NWDAF assistance as will be described). This new subscription information may be obtained from the UDM.

In one example, the SMF and/or PCF should verify the frequency of QoS changes that were made by the UE. For example, the SMF may verify Crossed Reporting Threshold parameter as described in 'Table 6.9.3-1: "QoS Sustainability" statistics' in 3GPP TS 23.228.

If the SMF and/or PCF determines that the QoS change statistics (optionally for an Analytics target period in the past in a certain area or the likelihood of a QoS change for an Analytics target period in the future in a certain area) indicates that the UE may request a change of QoS, then the SMF and/or PCF may determine to behave as follows:

ㆍ In addition to the default QoS that is established with the PDU session, the SMF and/or PCF should create or establish at least one additional QoS rule (or QoS flow) with a 5QI value that is different (and expected to be better in terms of QoS treatment) from the value of the 5QI associated with the default QoS flow.

ㆍ The SMF and/or PCF should choose a 5QI value for the additional (at least one) QoS flow such that the chosen value is similar to (or better than in terms of QoS characteristics) what the UE would have normally requested for a QoS flow which is not a default QoS flow. This information (i.e. what the UE would have normally requested) may be based on the assistance information from the NWDAF (or ARDF) that the SMF and/or PCF should verify and use to make this determination.

ㆍ In one example for the above, the SMF and/or PCF should ensure that the Authorized QoS rules IE (of the PDU Session Establishment Accept message) contains at least one additional QoS rule which is not a default QoS rule, and the QFI that is indicated is associated with (or maps to) the chosen 5QI as described above. Therefore the outcome of the NAS procedure (i.e. the PDU session establishment procedure) is that the UE will receive the IE (and NAS message) such that this leads to the creation of at least two QoS rules where one is a default QoS rule (associated with a subscribed QFI/5QI value) and at least one non-default QoS rule which is associated with a QFI/5QI that the SMF has determined as explained above.

Figure 3 illustrates an example procedure to establish non-default QoS rule based with 5QI based on analytics.

Note that although the details herein are provided based on the QoS sustainability analytics, embodiments can also apply to other analytics that can provide similar information to the consumer of the analytics. Therefore, the examples are not to be considered limited to just the QoS sustainability analytics. Moreover, the details may apply to other network functions such as the PCF, in particular, and so the use of the SMF should be considered as an example and not a limitation. As such, all the details herein can be applied for other NFs such as the PCF. In this case, the PCF may in turn provide any determined values (as will be described below) to another NF such as the SMF.

The SMF may inform the PCF that at least one 5QI value (for the default QoS rule or a non-default QoS rule) has been modified based on analytics (although not shown in Figure 3).

PCF subscribes to QoS sustainability analytics

In this solution option, the PCF (Policy Control Function) subscribes to the (or with the) NWDAF for the QoS sustainability analytics. Moreover, the PCF can also trigger the storage/retrieval of analytics from the ADRF as set out above for the SMF. As such all the details above in terms of subscribing to the NWDAF, and triggering storage/retrieval of analytics into/from the ADRF would apply for the PCF.

Furthermore, this solution option sets out that when the SMF contacts the PCF to obtain policy rules (e.g. when the SMF requests to establish an SM Policy Association with the PCF by invoking Npcf_SMPolicyControl_Create operation), the PCF may retrieve the stored analytics for a UE in question. The PCF may then behave in any of the following manners:

* The PCF determines a modified 5QI value based on the analytics obtained from the ADRF (or NWDAF) and the PCF provides a policy rule such that the determined 5QI value is then provided (where this value is based on the analytics received)

* The PCF may determine to provide a second rule such that the second rule is associated with a non-default QoS rule and also determines the 5QI for this rule based on the analytics that is received.

The PCF may provide to the SMF either:

* The determined 5QI for the default QoS rule (or QoS flow) as described above,

* At least two rules where the second rule is for a non-default QoS rule with a 5QI that has been determined as described above.

If the SMF receives at least two policy rules where at least one of these are for a non-default QoS rule, then the SMF may determine to establish at least two QoS rules during the PDU session establishment procedure as has been described in previous solution options. In this case, the SMF uses the 5QI which has been received from the PCF per policy rule.

Note that although the details provided herein are based on the QoS sustainability analytics, embodiments can also apply to other analytics that can provide similar information to the consumer of the analytics. Therefore, the embodiments are not to be considered limited to just the QoS sustainability analytics. Moreover, the techniques may apply to other network functions such as the PCF and, so, the use of the SMF should be considered as an example proposal and not a limitation. As such, all the details herein can be applied to other NFs such as, in particular, the PCF. In this case, the PCF may in turn provide any determined values (as will be described below) to another NF such as the SMF.

PCF subscribes to QoS sustainability analytics

In this solution option, the PCF (Policy Control Function) subscribes to the (or with the) NWDAF for the QoS sustainability analytics. Moreover, the PCF can also trigger the storage/retrieval of analytics from the ADRF as set out above for the SMF. As such all the details above in terms of subscribing to the NWDAF, and triggering storage/retrieval of analytics into/from the ADRF apply for the PCF.

Furthermore, this solution option sets out that when the SMF contacts the PCF to obtain policy rules (e.g. when the SMF requests to establish an SM Policy Association with the PCF by invoking Npcf_SMPolicyControl_Create operation), the PCF may retrieve the stored analytics for a UE in question. The PCF may then behave in any of the following manner:

ㆍ The PCF determines a modified 5QI value based on the analytics obtained from the ADRF (or NWDAF) and the PCF provides a policy rule such that the determined 5QI value is then provided (where this value is based on the analytics received)

ㆍ The PCF may determine to provide a second rule such that the second rule is associated with a non-default QoS rule and also determines the 5QI for this rule based on the analytics that is received.

The PCF may provide to the SMF either:

ㆍ The determined 5QI for the default QoS rule (or QoS flow) as described above,

ㆍ At least two rules where the second rule is for a non-default QoS rule with a 5QI that has been determined as described above.

Figure 4 illustrates an example of how the solutions above can be used, more specifically, Figure 4 illustrates an example procedure for PCF determination of 5QI values based on analytics.

Note that although not shown in the Figure 4, the PCF may, based on the determined 5QI using analytics, provide an explicit indication to the SMF that the 5QI value(s) have been determined based on analytics. The SMF may use this indication to in turn establish at least one non-default QoS rule using the 5QI obtained from the PCF.

Although a preferred embodiment has been shown and described, it will be appreciated by those skilled in the art that various changes and modifications might be made without departing from the scope of the invention, as defined in the appended claims and as described above.

Figure 5 illustrates a block diagram of a terminal (or a user equipment (UE)), according to embodiments of the present disclosure. Figure 5 corresponds to the example of the UE of FIGs. 1A and 1B.

As shown in Figure 5, the UE according to an embodiment may include a transceiver 510, a memory 520, and a processor 530. The transceiver 510, the memory 520, and the processor 530 of the UE may operate according to a communication method of the UE described above. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. In addition, the processor 530, the transceiver 510, and the memory 520 may be implemented as a single chip. Also, the processor 530 may include at least one processor.

The transceiver 510 collectively refers to a UE receiver and a UE transmitter, and may transmit/receive a signal to/from a base station or a network entity. The signal transmitted or received to or from the base station or a network entity may include control information and data. The transceiver 510 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 510 and components of the transceiver 510 are not limited to the RF transmitter and the RF receiver.

Also, the transceiver 510 may receive and output, to the processor 530, a signal through a wireless channel, and transmit a signal output from the processor 530 through the wireless channel.

The memory 520 may store a program and data required for operations of the UE. Also, the memory 520 may store control information or data included in a signal obtained by the UE. The memory 520 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The processor 530 may control a series of processes such that the UE operates as described above. For example, the transceiver 510 may receive a data signal including a control signal transmitted by the base station or the network entity, and the processor 530 may determine a result of receiving the control signal and the data signal transmitted by the base station or the network entity.

Figure 6 illustrates a block diagram of a base station, according to embodiments of the present disclosure. Figure 6 corresponds to the example of the RAN node of Figure 1A to 1B.

As shown in Figure 6, the base station according to an embodiment may include a transceiver 610, a memory 620, and a processor 630. The transceiver 610, the memory 620, and the processor 630 of the base station may operate according to a communication method of the base station described above. However, the components of the base station are not limited thereto. For example, the base station may include more or fewer components than those described above. In addition, the processor 630, the transceiver 610, and the memory 620 may be implemented as a single chip. Also, the processor 630 may include at least one processor.

The transceiver 610 collectively refers to a base station receiver and a base station transmitter, and may transmit/receive a signal to/from a terminal or a network entity. The signal transmitted or received to or from the terminal or a network entity may include control information and data. The transceiver 610 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 610 and components of the transceiver 610 are not limited to the RF transmitter and the RF receiver.

Also, the transceiver 610 may receive and output, to the processor 630, a signal through a wireless channel, and transmit a signal output from the processor 630 through the wireless channel.

The memory 620 may store a program and data required for operations of the base station. Also, the memory 620 may store control information or data included in a signal obtained by the base station. The memory 620 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The processor 630 may control a series of processes such that the base station operates as described above. For example, the transceiver 610 may receive a data signal including a control signal transmitted by the terminal, and the processor 630 may determine a result of receiving the control signal and the data signal transmitted by the terminal.

Figure 7 illustrates a block diagram of a network entity, according to embodiments of the present disclosure. Figure 7 corresponds to the example of the core network entity of Figure. 1A to 1B.

As shown in Figure 7, the network entity according to an embodiment may include a transceiver 710, a memory 720, and a processor 730. The transceiver 710, the memory 720, and the processor 730 of the network entity may operate according to a communication method of the network entity described above. However, the components of the network entity are not limited thereto. For example, the network entity may include more or fewer components than those described above. In addition, the processor 730, the transceiver 710, and the memory 720 may be implemented as a single chip. Also, the processor 730 may include at least one processor.

The transceiver 710 collectively refers to a network entity receiver and a network entity transmitter, and may transmit/receive a signal to/from a terminal or other network entity. The signal transmitted or received to or from the terminal or other network entity may include control information and data. The transceiver 710 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 710 and components of the transceiver 710 are not limited to the RF transmitter and the RF receiver.

Also, the transceiver 710 may receive and output, to the processor 730, a signal through a wireless channel, and transmit a signal output from the processor 730 through the wireless channel.

The memory 720 may store a program and data required for operations of the network entity. Also, the memory 720 may store control information or data included in a signal obtained by the network entity. The memory 720 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The processor 730 may control a series of processes such that the network entity operates as described above. For example, the transceiver 710 may receive a data signal including a control signal transmitted by the terminal, and the processor 730 may determine a result of receiving the control signal and the data signal transmitted by the terminal.

The term "consisting of" or "consists of" means including the components specified but excluding other components.

Whenever appropriate, depending upon the context, the use of the term "comprises" or "comprising" may also be taken to include the meaning "consists essentially of" or "consisting essentially of", and also may also be taken to include the meaning "consists of" or "consisting of".

The optional features set out herein may be used either individually or in combination with each other where appropriate and particularly in the combinations as set out in the accompanying claims. The optional features for each aspect or exemplary embodiment of the invention, as set out herein are also applicable to all other aspects or exemplary embodiments of the invention, where appropriate. In other words, the skilled person reading this specification should consider the optional features for each aspect or exemplary embodiment of the invention as interchangeable and combinable between different aspects and exemplary embodiments.

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.

All of the features disclosed in this specification (including any accompanying claims and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at most some of such features and/or steps are mutually exclusive.

Each feature disclosed in this specification (including any accompanying claims, and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.

The invention is not restricted to the details of the foregoing embodiment(s). The invention extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed.

In the afore-described embodiments of the present disclosure, elements included in the present disclosure are expressed in a singular or plural form according to the embodiments. However, the singular or plural form is appropriately selected for convenience of explanation and the present disclosure is not limited thereto. As such, an element expressed in a plural form may also be configured as a single element, and an element expressed in a singular form may also be configured as plural elements.

Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the description in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claims scope. The scope of patented subject matter is defined by the claims.

Claims

A method performed by a network data analytics function (NWDAF) entity in a wireless communication system, the method comprising:

receiving, from a consumer network function (NF) entity, a first message requesting assistance information analytics;

obtaining data on a quality of service (QoS) and a policy;

generating the assistance information analytics based on the obtained data; and

transmitting, to the consumer NF entity, a second message including the assistance information analytics, wherein the assistance information analytics comprises a prediction of the QoS and the policy.
The method of claim 1,

wherein the assistance information analytics includes at least one of QoS sustainability analytics, or analytics on a QoS flow.
The method of claim 2,

wherein the analytics on the QoS flow includes information on duration of the QoS flow,

wherein the assistance information analytics is associated with one or more user equipments (UEs).
The method of claim 1,

wherein the consumer NF includes a policy control function (PCF) entity.
A method performed by a policy control function (PCF) entity in a wireless communication system, the method comprising:

transmitting, to a network data analytics function (NWDAF) entity, a first message requesting assistance information analytics;

receiving, from the NWDAF entity, a second message including the assistance information analytics, wherein the assistance information analytics comprises a prediction of a quality of service (QoS) and a policy; and

identifying the QoS or the policy based on the assistance information analytics.
The method of claim 5,

wherein the assistance information analytics includes at least one of QoS sustainability analytics, analytics on a QoS flow.
The method of claim 6,

wherein the analytics on the QoS flow includes information on duration of the QoS flow,

wherein the assistance information analytics is associated with one or more user equipments (UEs).
A network data analytics function (NWDAF) entity in a wireless communication system, the NWDAF entity comprising:

a transceiver, and

a controller coupled with the transceiver and configured to:

receive, from a consumer network function (NF) entity, a first message requesting assistance information analytics,

obtain data on a quality of service (QoS) and a policy,

generate the assistance information analytics based on the obtained data, and

transmit, to the consumer NF entity, a second message including the assistance information analytics, wherein the assistance information analytics comprises a prediction of the QoS and the policy.
The NWDAF entity of claim 8,

wherein the assistance information analytics includes at least one of QoS sustainability analytics, analytics on a QoS flow.
The NWDAF entity of claim 9,

wherein the analytics on the QoS flow includes information on duration of the QoS flow,

wherein the assistance information analytics is associated with one or more user equipments (UEs).
The NWDAF entity of claim 8,

wherein the consumer NF includes a policy control function (PCF) entity.
A policy control function (PCF) entity in a wireless communication system, the PCF entity comprising:

a transceiver, and

a controller coupled with the transceiver and configured to:

transmit, to a network data analytics function (NWDAF) entity, a first message requesting assistance information analytics,

receive, from the NWDAF entity, a second message including the assistance information analytics, wherein the assistance information analytics comprises a prediction of a quality of service (QoS) and a policy, and

identify the QoS or the policy based on the assistance information analytics.
The PCF entity of claim 12,

wherein the assistance information analytics includes at least one of QoS sustainability analytics, analytics on a QoS flow.
The PCF entity of claim 12,

wherein the analytics on the QoS flow includes information on duration of the QoS flow,

wherein the assistance information analytics is associated with one or more user equipments (UEs).