Content for TS 23.502 Word version: 18.2.0

1… 4.2.2.2.2 4.2.2.2.3… 4.2.2.3… 4.2.3… 4.2.3.3 4.2.4… 4.2.6 4.2.7… 4.2.9… 4.2.11… 4.2.11.5… 4.3… 4.3.2.2.2 4.3.2.2.3… 4.3.3… 4.3.3.3 4.3.4… 4.3.4.3 4.3.5… 4.3.5.2… 4.3.5.4… 4.3.5.6… 4.3.6… 4.4… 4.5… 4.9… 4.9.1.3… 4.9.2… 4.11… 4.11.1… 4.11.1.2.2 4.11.1.2.3 4.11.1.3… 4.11.1.3.3… 4.11.1.4… 4.11.1.5… 4.11.2… 4.11.3… 4.12… 4.12.6… 4.12a… 4.12b… 4.13… 4.13.4… 4.13.6… 4.14… 4.15… 4.15.3.2.5… 4.15.4… 4.15.6… 4.15.6.7… 4.15.6.13… 4.15.6.14… 4.15.9… 4.15.9.4… 4.15.13… 4.15.13.4… 4.16… 4.16.4… 4.16.8… 4.16.11… 4.16.14… 4.16.15… 4.17… 4.17.9… 4.18… 4.19… 4.22… 4.23… 4.23.7… 4.23.7.3.3 4.23.7.3.4… 4.23.9… 4.23.9.4… 4.23.11… 4.24… 4.25… 4.25.6… 4.26… 5… 5.2.3… 5.2.5… 5.2.6… 5.2.7… 5.2.8… 5.2.9… 5.2.12… 5.2.18… A… E… F… G H…

4.15.13 Assistance for Member UE selection 4.15.13.0 General 4.15.13.1 Member UE selection general information flow 4.15.13.2 Member UE Filtering Criteria for 5GS assistance to Member UE selection 4.15.13.3 Specific procedure for QoS Member UE filtering criteria
...

4.15.13 Assistance for Member UE selection |R18| p. 475

4.15.13.0 General p. 475

AF provides a list of target UE(s) and at least one Member UE filtering criterion as part of the service operation parameters to assist the candidate UEs selection. Upon receiving the AF request, NEF triggers corresponding 5GC procedures to retrieve the information for the UE in the list of target UE(s) from 5GC NFs. Before sending the list(s) of candidate UEs to the AF, NEF consolidates all the information collected from other 5GC NFs and derives one or more list(s) of candidate UEs and possibly additional information according to the Member UE filtering criteria requested by the AF.

The Member UE selection assistance capability can be used to assist the AF to select the group of UEs to support application service (e.g. FL operation) and it is further defined in clause 5.46.2 of TS 23.501.

AF leverages the 5GC network exposure for Member UE selection without the NEF assistance as described in clause 5.46.2 of TS 23.501. An example of how AF to leverage the 5GC network exposure for Member UE selection can be referred to informative Annex I.

4.15.13.1 Member UE selection general information flow p. 475

This clause describes the procedures that are generally applicable independently of the Member UE filtering criteria sent by the AF.

Reproduction of 3GPP TS 23.502, Fig. 4.15.13.1-1: 5GC assistance to Member UE selection and update

Figure 4.15.13.1-1: 5GC assistance to Member UE selection and update

Step 1.

AF subscribes the Member UE selection assistance functionality by sending Nnef_MemberUESelectionAssistance_subscribe request including a list of target UE(s), one or more UE member filtering criteria listed in the Table 4.15.13.2-1 and optionally, time window(s). Subsequently, the AF may update the filtering criteria of the subscription by invoking Nnef_UEMemberSelectionAssistance_subscribe and providing a

Step 2a.

[OPTIONAL] NEF verifies the authorization of the AF Request and identifies which information needs to be collected for each UE in the list of target UE(s) and executes the corresponding service operation based on the Member UE filtering criteria provided by the AF, e.g. events, analytics and/or notifications.

Step 2b.

[OPTIONAL] The NEF correlates the Nnef_MemberUESelectionAssistance_Subscribe request to an existing subscription according to the Subscription Correlation ID. The NEF uses the target UEs received in step 1 for the Member UE update using the updated filtering criteria.

Step 3.

NEF interacts with different 5GC network functions to collect the required information for each UE in the list of target UE(s). The set of interactions between NEF and among 5GC NFs are dependent on the Member UE filtering criteria provided by the AF. See Table 4.15.13.2-1 for details.

Step 4.

Based on the collected information from other 5GC NFs, NEF consolidates all the information collected from other 5GC NFs to derive the list(s) of candidate UE(s) which fulfil the Member UE filtering criteria in the AF request. The NEF may derive recommended time window(s) considering the validity period(s) of the analytics used for Member UE selection criteria, which are a subset of the time window(s) received from the AF.

Step 5.

NEF sends a Nnef_MemberUESelectionAssistance_Notify request to the AF including the list(s) of candidate UE(s) and possibly additional information. See clause 5.2.6.32.4 for details.

4.15.13.2 Member UE Filtering Criteria for 5GS assistance to Member UE selection p. 476

Table 4.15.13.2-1 provides a summary of the Member UE filtering criteria that the AF may request.

Table 4.15.13.2-1: Description of Member UE filtering criteria

Member UE filtering criteria	Description of filtering criterion	UE filtering information	Detailed description clause
QoS	The Quality of Service of the selected UEs match or exceed the QoS of the filtering criteria	Filter: target=SUPI, Event=QoS Monitoring, traffic descriptor (e.g. Application ID)	4.15.13.3
Access Type and/or RAT Type of the PDU Session	Indicate the Access Type and/or RAT Type of the selected UE for the PDU Session used by the application (e.g. 3GPP/NR, Non-3GPP/WLAN, additional Access Type and RAT Type for MA PDU session)	Service operation: Nsmf_EventExposure Filter: a list of GPSI(s) or SUPI(s), DNN/S-NSSAI Event ID: Change of Access Type and/or Change of RAT Type	This can be provided by existing service operations, events and procedures.
End-to-end data volume transfer time	Indicate the end-to-end data volume transfer time that refers to a time for completing the transmission of a specific data volume between UE to AF, e.g. the average and variance of End-to-end data volume transfer time	Service operation: Nnwdaf_AnalyticsSubscription/ Nnwdaf_AnalyticsInfo Filter: Analytics ID = End-to-end data volume transfer time, target = GPSI(s) or SUPI(s)	4.15.13.6
UE current location	Indicate the certain area that the selected UE currently located in.	Service operation: Namf_EventExposure Filter: a list of GPSI(s) or SUPI(s)	4.15.13.4
UE historical location	Indicate the certain area that the selected UE appeared in a historical period of time	Service operation: Nnwdaf_AnalyticsSubscription Filter: Analytics ID = UE mobility, Filters include "Visited AoI = Target AOI" and "target period = historical nomadic period"	4.15.13.4
UE direction	Indicate the selected UEs should include different moving direction	Service operation: Nnwdaf_AnalyticsSubscription Filter: Analytics ID= UE Mobility, Direction	4.15.13.4
UE separation distance (NOTE 1)	Indicate the selected UEs should comply with a minimum separation distance between each other	Service operation: Nnwdaf_AnalyticsSubscription/ Nnwdaf_AnalyticsInfo Filter: Analytics ID = Relative Proximity Filters include "Proximity Attributes"	4.15.13.4
Service Experience	Indicates selected UEs fulfilling ceratin Service Experience criteria e.g., MOS value	Service operation: Nnwdaf_AnalyticsInfo_Request/Subscribe Analytics ID=Service Experience Filter: S-NSSAI, DNN, Application ID, DNAI, AoI, Service Experience Contribution weight reporting threshold (NOTE 2), Service Experience Type (NOTE 3)	4.15.13.5
DNN	Indicate the DNN of the selected UE for the PDU Session used by the application	Service operation: Nsmf_EventExposure Filter: a list of GPSI(s) or SUPI(s) Event ID: QFI allocation	5.2.8.3
NOTE 1: This criterion should only be applied when the number of UEs is in the range of 10's or less. NOTE 2: The Service Experience Contribution Weights signal the relative importance of each UE's Service Experience value (i.e. MOS), as defined in TS 23.288. For example, it might be that the service experience of a UE in relation to other UEs may not be as important e.g. because the data provided by such UE is not as critical to the service. NOTE 3: Indicates the type of service experience analytics, e.g. AIML traffic where a customized MoS apply.

4.15.13.3 Specific procedure for QoS Member UE filtering criteria p. 479

4.15.13.3.1 General p. 479

An AF may invoke Nnef_MemberUESelectionAssistance_Subscribe service operation with a QoS filtering criteria for receiving a list of UEs that match or exceed such criteria.

In addition to the mandatory parameters, the AF also includes in the request:

QoS filtering criteria.
Optionally, an Area of Interest: location area of the candidate UEs.

The QoS filtering criteria includes:

a traffic descriptor (e.g. Application ID).

And one or more of the QoS parameters subject to QoS monitoring (see list in clause 5.45 of TS 23.501).

The current list of UEs that match or exceed the QoS filtering criteria and are optionally located in the AoI in real time, for the duration of the subscription, is further described in clause 4.15.13.3.3.

4.15.13.3.2 Void

4.15.13.3.3 Member UE Assistance with QoS filtering criteria for real-time QoS Monitoring p. 479

At the reception of Nnef_MemberUESelectionAsistance_Subscribe request of step 1, NEF determines to do real-time QoS monitoring for determining the list of UEs that match or exceeds the QoS filtering criteria in real time. Unless the QoS flow to be monitored is associated with a default QoS flow, QoS Monitoring must have been activated in SMF for that QoS Flow before (e.g. by AF Session with required QoS) (see clause 4.15.4.5.1 for details).

Reproduction of 3GPP TS 23.502, Fig. 4.15.13.3.3-1: 5GC assistance to Member UE selection for real-time QoS monitoring

Figure 4.15.13.3.3-1: 5GC assistance to Member UE selection for real-time QoS monitoring

Step 1.

AF subscribes the Member UE selection assistance functionality by sending Nnef_MemberUESelectionAssistance_subscribe request including its AF ID, the Application ID, optionally S NSSAI/DNN and the QoS filtering criteria.

Step 2.

NEF uses the AF ID to verify the authorization of the AF request and identifies which information needs to be collected and executed based on the QoS filtering criteria provided by the AF.

Step 3.

If an S-NSSAI/DNN are not included in the request from the AF, the NEF derives the S-NSSAI and DNN to which this Application ID have access. NEF discovers querying UDM and NRF the SMFs that are deployed in the Area of Interest. The NEF may also restrict the discovery to those SMFs that serve some S-NSSAI and DNN combination.

Step 4.

For each target SMF, NEF sends an Nsmf_EventExposure_Subscribe request (Event: 'QoS monitoring', target UEs, optional a traffic descriptor (e.g. Application ID), optional indication for default QoS flows monitoring, , S-NSSAI, DNN, Notification Target Address set to NEF, etc.). Alternatively, NEF may send an Nudm_EventExposure_Subscribe request to the UDM (not shown in Figure 4.15.13.3.3-1).

Step 5.

The SMF may need to send an N4 Session Modification request to UPF for requesting the QoS monitoring for certain flows.

Step 6.

UPF sends an Nupf_EventExposure_Notify request to NEF including an Event Exposure notification, according to the subscription received from SMF.

Step 7.

Based on the Event Exposure reports received from the UPFs, NEF consolidates the received results and derives the list(s) of candidate UE(s) and additional information which fulfil the QoS filtering criteria requested by the AF request.

Step 8.

NEF sends a Nnef_MemberUESelectionAssistance_Notify request to the AF including the list(s) of candidate UE(s) and additional information.