Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.502  Word version:  19.1.0

Top   Top   Up   Prev   Next
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.6.14 Procedures for AF requested QoS for a UE or group of UEs not identified by a UE address  4.15.7 Network status reporting  4.15.8 Event exposure controlled by a DCCF 
...

 

4.15.6.14  Procedures for AF requested QoS for a UE or group of UEs not identified by a UE address |R18|  p. 469

Reproduction of 3GPP TS 23.502, Fig. 4.15.6.14-1: Procedure for AF requested QoS for a UE or group of UEs not identified by a UE address
Figure 4.15.6.14-1: Procedure for AF requested QoS for a UE or group of UEs not identified by a UE address
Up
Step 0.
When a new PDU Session is established, based on local configuration associated with the DNN/S-NSSAI, the PCF determines if the PDU Session needs involvement of TSCTSF. If the TSCTSF is used the PCF invokes Npcf_PolicyAuthorization_Notify service operation to the TSCTSF discovered and selected as described in clause 6.3.24 of TS 23.501. The Npcf_PolicyAuthorization_Notify service operation includes the UE address of the PDU Session and DNN/S-NSSAI. If the TSCTSF is not used, the PCF subscribes to notifications for Application Data from UDR.
The PCF registers to BSF as described in TS 23.503. When the TSCTSF is used, the TSCTSF invokes a Npcf_PolicyAuthorization_Create request message to the PCF and stores the DNN, S-NSSAI and IP address as received from PCF and SUPI as received from BSF and associates them with the AF-session.
Step 1.
The AF sends a request to reserve resources using Nnef_AF_Request_QoS_Create request message (GPSI or External Group ID, AF Identifier, Flow description(s) or External Application Identifier, QoS reference or individual QoS parameters, Alternative Service Requirements (as described in clause 6.1.3.22 of TS 23.503), DNN, S-NSSAI) to the NEF. Optionally, a period of time or a traffic volume for the requested QoS can be included in the AF request. The AF may, instead of a QoS Reference, provide the individual QoS parameters. Regardless, whether the AF request is formulated using a QoS Reference or Individual QoS paramaters, the AF may also provide one or more of the parameters that describe the traffic characteristics as described in clause 6.1.3.28 of TS 23.503.
Step 2.
This step is the same as step 2 in clause 4.15.6.6.
Step 3.
This step is the same as steps 2-4 in clause 4.15.6.7a.
The NEF determines whether to invoke the TSCTSF or not, as described in step 2 in clause 4.15.6.6. If the NEF determines to invoke TSCTSF, steps 4-9 are executed and steps 10-12 are skipped. Otherwise steps 4-9 are skipped and steps 10-12 are executed. The procedure then continues in step 13.
Step 4.
This step is the same as step 3a in clause 4.15.6.6 with the difference that Internal Group ID or SUPI is provided instead of UE address.
Step 5.
If the group members are identified by GPSI or External/Internal Group ID, the TSCTSF uses the Nudm_SDM_Get request to retrieve the subscription information (SUPI(s)) from the UDM using each GPSI or the External/Internal Group Identifier received in step 4 The TSCTSF also determines which of these group members have active PDU Sessions matching the DNN/S-NSSAI and determines the relevant UE address. The TSCTSF manages the AF request QoS information targeting for a group as defined in TS 23.501.
Step 6.
For each PDU Session, the TSCTSF invokes Npcf_PolicyAuthorization service. This step is the same as step 3b in clause 4.15.6.6.
Step 7.
The PCF replies to the TSCTSF. This step is the same as step 4a in clause 4.15.6.6.
Step 8.
The TSCTSF replies to the NEF. This step is the same as step 4b in clause 4.15.6.6.
Step 9.
This step is the same as step 6a in clause 4.15.6.6 with the difference that it is executed for all PDU Sessions identified in step 6 above.
Step 10.
If the NEF determines to not invoke the TSCTSF, the NEF uses the Nudr_DM service to store the information related to the Internal Group ID or SUPI in UDR. The information is stored as Application Data in UDR. If the AF requested for notifications of Resource allocation status or other events, the NEF includes the information required for reporting the event, including the Notification Target Address pointing to the NEF or AF and the Notification Correlation ID containing the AF Transaction Internal ID. This step is the same as step 3 in clause 4.15.6.7.2 except the Data Subset of "Application Data" is set to "AF request for QoS information".
Step 12.
The PCF(s) identifies the active PDU Sessions associated with the data received from UDR. The PCF(s) manages the AF request QoS information targeting for a group as defined in TS 23.503.
Step 13.
The NEF replies to the AF. This step is the same as step 8 in clause 4.15.6.6.
Step 14.
When an event condition is met, e.g. that the establishment of the transmission resources corresponding to the QoS update succeeded or failed, the PCF sends a notification to TSCTSF or NEF as applicable. This step is the same as steps 7-8 in clause 4.15.6.6.
Up

4.15.7  Network status reporting |R16|  p. 470

This clause contains the detailed description and the procedures for the network status reporting capability.
An AF may request for being notified about the network status, in a specific geographical area or for a specific UE.
The following methods are supported:
  • The AF requests to be informed, one-time, about the network status. This procedure is referred to as one-time network status request;
  • The AF requests to be informed, continuously, about the network status. This procedure is referred to as continuous network status request;
The procedure as described in clause 6.1.1.2 or clause 6.1.2.2 of TS 23.288 is used by an AF to retrieve Network Status Result (NSR) from the network for a specific geographical area or for a specific UE.
After receiving the request for network status notification from the AF, the NEF retrieves user data congestion analytics information from NWDAF, as defined in TS 23.288.
Based on the user data congestion analytics information the NEF receives from the NWDAF, the NEF derives and reports the network status for the geographical area or for the UE as Network Status Result (NSR) to the AF. When reporting to the AF, the NSR shall not include any 3GPP location information.
When an AF requests one-time Network Status from the NEF, the NEF can optionally provide a time interval at which the AF is allowed to re-issue the same request for network status.
Up

4.15.8  Event exposure controlled by a DCCF |R17|  p. 471

A DCCF can coordinate the subscriptions and notifications to event exposure in Network Functions. This is further described in TS 23.288.

Up   Top   ToC