4.2.4 Npcf_PolicyAuthorization_Delete service operation

29.5143GPP5G SystemPolicy Authorization ServiceRelease 18Stage 3TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

4.2.4.1 General

The Npcf_PolicyAuthorization_Delete service operation provides means for the NF service consumer to delete the context of application session information.

The following procedures using the Npcf_PolicyAuthorization_Delete service operation are supported:

– AF application session context termination.

– Reporting usage for sponsored data connectivity.

– Termination of Multimedia Priority Services.

– Request and report of access network information.

– Termination of MCPTT.

– Termination of MCVideo.

– Priority sharing indication.

– Report of RAN-NAS release cause.

– Termination of Mission Critical Services.

– Report of Service Data Flow QoS Monitoring.

4.2.4.2 AF application session context termination

This procedure is used to terminate an AF application session context for the service as defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4].

Figure 4.2.4.2-1 illustrates the application session context termination.

Figure 4.2.4.2-1: Application session context termination

When an AF session is terminated, and if the AF application session context was created as described in clause 4.2.2 or in clause 4.2.6.3, the NF service consumer shall invoke the Npcf_PolicyAuthorization_Delete service operation to the PCF using an HTTP POST request, as shown in figure 4.2.4.2-1, step 1.

The NF service consumer shall set the request URI to "{apiRoot}/npcf-policyauthorization/v1/app-sessions/{appSessionId}/delete".

The NF service consumer may include in the body of the HTTP POST the "EventsSubscReqData" data type with the "evSubsc" attribute indicating the corresponding list of events to subscribe to.

When the PCF receives the HTTP POST request from the NF service consumer, indicating the termination of the AF application session context information, the PCF shall acknowledge that request by sending an HTTP response message with the corresponding status code.

If the HTTP POST request from the NF service consumer is accepted, the PCF shall send to the NF service consumer:

a) if event information is reported, a "200 OK" response to HTTP POST request, as shown in figure 4.2.4.2-1, step 2a, including in the "AppSessionContext" data type the "evsNotif" attribute, which encodes within "evNotifs" attribute the event to report to the NF service consumer, if available, as described in clause 4.2.5.2. If the event information is not available at the PCF the PCF shall defer sending the response to the NF service consumer and shall immediately configure the SMF to provide such information, as specified in 3GPP TS 29.512 [8];

b) otherwise, the PCF shall send to the NF service consumer a "204 No Content".

Afterwards, the PCF shall free the network resources allocated for the Service Data Flow(s) corresponding to the deleted AF application session context information. In order to do that, the PCF shall initiate the request for the removal of any related PCC rules from the SMF, if not previously done, following the corresponding procedures specified in 3GPP TS 29.512 [8].

If the HTTP POST request from the NF service consumer is rejected, the PCF shall indicate in the response to HTTP POST request the cause for the rejection as specified in clause 5.7.

4.2.4.3 Reporting usage for sponsored data connectivity

When "SponsoredConnectivity" is supported, and the NF service consumer indicated to enable sponsored data connectivity and the NF service consumer provided usage thresholds for such sponsor to the PCF, the PCF shall report accumulated usage to the NF service consumer using the response of the Npcf_PolicyAuthorization_Delete service operation.

This procedure is initiated when:

– the "Individual Application Session Context" is deleted by the NF service consumer; or

– the PCF requests the deletion of the "Individual Application Session Context" to the NF service consumer, as described in clause 4.2.5.3, due to PDU session termination, the termination of all the service data flows of the AF session or the home operator policy disallowing the UE accessing the sponsored data connectivity in the roaming case.

To report the accumulated usage, the PCF shall immediately configure the SMF to retrieve the accumulated usage as specified in 3GPP TS 29.512 [8]. When the PCF receives the usage information from the SMF, the PCF shall notify the NF service consumer by including the "EventsNotification" data type in the response of the HTTP POST request as described in clause 4.2.4.2.

The PCF shall include:

– an event of the "AfEventNotification" data type in the "evNotifs" attribute with the matched event "USAGE_REPORT" in the "event" attribute; and

– the usage encoded in the "usgRep" attribute.

4.2.4.4 Void

4.2.4.5 Termination of Multimedia Priority Services

If the AF session being terminated corresponds to an MPS session, the PCF shall delete the PCC rules corresponding to the MPS session and the PCF shall revoke the actions related to the prioritization of the MPS session in the corresponding PDU Session as defined in 3GPP TS 29.512 [8].

If the AF session being terminated corresponds to an MPS for DTS session, the PCF shall revoke MPS for DTS session in the corresponding PDU Session as defined in 3GPP TS 29.512 [8].

4.2.4.6 Request and report of access network information

This procedure is used by a NF service consumer to request the PCF to report the access network information (i.e. user location and/or user timezone information) at the deletion of the "Individual Application Session Context" resource when the "NetLoc" feature is supported.

This procedure is initiated when:

– the "Individual Application Session Context" is deleted by the NF service consumer; or

– the PCF requests the deletion of the "Individual Application Session Context" from the NF service consumer, as described in clause 4.2.5.3, due to PDU session termination or the termination of all the service data flows of the AF session.

The NF service consumer shall include in the HTTP POST request message described in clause 4.2.4.2:

– an entry of the "AfEventSubscription" data type in the "events" attribute with:

a) the "event" attribute set to the value "ANI_REPORT"; and

b) the "notifMethod" attribute set to the value "ONE_TIME"; and

– the "reqAnis" attribute, with the required access network information, i.e. user location and/or user time zone information).

When the PCF determines that the access network does not support the access network information reporting because the SMF does not support the NetLoc feature, the PCF shall respond to the NF service consumer including in the "EventsNotification" data type the "noNetLocSupp" attribute set to "ANR_NOT_SUPPORTED" value. Otherwise, the PCF shall immediately configure the SMF to provide such access information, as specified in 3GPP TS 29.512 [8].

When the PCF receives the access network information from the SMF, the PCF shall provide the corresponding access network information to the NF service consumer by including the "EventsNotification" data type in the "200 OK" response to the HTTP POST request. The PCF shall include:

– in case of 3GPP access, the user location information in the "eutraLocation" or in the "nrLocation" attribute in the "ueLoc" attribute, if available and required;

– in case of untrusted non-3GPP access, the user location information in the "n3gaLocation" attribute in the "ueLoc" attribute, if required, as follows:

a) the user local IP address in the "ueIpv4Addr" or "ueIpv6Addr" attribute, if available;

b) the UDP source port or the TCP source port in the "portNumber" and "protocol" attributes, if available; and

c) if the "WLAN_Location" feature is supported, the WLAN location information encoded in the "twapId" attribute, if available, that shall consist of:

i. the SSID in the "ssId" attribute;

ii. the BSSID the "bssId" attribute if available; and

iii. the civic address in the "civicAddress" attribute if available;

NOTE 1: When the UE reaches the ePDG via a NAT, the combination of UE local IP address and the UE source port is needed for lawful interception purposes. The UE source port may be either a UDP or a TCP port, and it is indicated in the "protocol" attribute.

– in case of trusted non-3GPP access, the user location information in the "n3gaLocation" attribute in the "ueLoc" attribute, if required, as follows:

a) the user local IP address in the "ueIpv4Addr" or "ueIpv6Addr" attribute, if available; and

b) the UDP source port in the "portNumber" attribute if available; and

NOTE 2: The UDP protocol can be used between the UE and the TNGF to enable NAT traversal.

c) either the TNAP identifier encoded in the "tnapId" attribute or the TWAP identifier encoded in the "twapId" attribute. The TNAP identifier and the TWAP identifier shall consist of:

i. the SSID in the "ssId" attribute;

ii. the BSSID the "bssId" attribute if available; and

iii. the civic address in the "civicAddress" attribute if available;

– if user location was required, the time when it was last known in the "ueLocTime" attribute if available;

NOTE 3: The PCF derives the value of the "ueLocTime" attribute from the "userLocationInfoTime" attribute received from the SMF as specified in 3GPP TS 29.512 [8].

– the serving network identity i.e. the PLMN Identifier (the PLMN network code and the country code) or the SNPN Identifier (the PLMN Identifier and the NID) in the "plmnId" attribute, if user location information is required but not available in any access; and/or

– the UE timezone in the "ueTimeZone" attribute if required and available.

NOTE 4: The PCF forwards both 3GPP and non-3GPP access UE locations in the "ueLoc" attribute when both UE locations are provided by the SMF as defined in 3GPP TS 29.512 [8].

When the PCF receives from the SMF that the access network does not support access network information report, the PCF shall include the "noNetLocSupp" attribute set to "ANR_NOT_SUPPORTED", "TZR_NOT_SUPPORTED" or "LOC_NOT_SUPPORTED" value received from the SMF in the "EventsNotification" data type in the "200 OK" response to the HTTP POST request.

The PCF shall also include an event of the "AfEventNotification" data type in the "evNotifs" attribute with the "event" attribute set to the value "ANI_REPORT".

4.2.4.7 Termination of MCPTT

If the "Individual Application Session Context" resource being removed corresponds to an MCPTT session, the PCF shall delete the PCC rules corresponding to the MCPTT session and the PCF shall revoke the actions related to the prioritization of the MCPTT session in the corresponding PDU Session as defined in 3GPP TS 29.512 [8].

4.2.4.8 Termination of MCVideo

If the "Individual Application Session Context" resource being removed corresponds to an MCVideo session, the PCF shall delete the PCC rules corresponding to the MCVideo session and the PCF shall revoke the actions related to the prioritization of the MCVideo session in the corresponding PDU Session as defined in 3GPP TS 29.512 [8].

4.2.4.9 Priority sharing indication

If the "Individual Application Session Context" resource being removed included the "prioSharingInd" attribute set to "ENABLED" within a media component of the "medComponents" attribute, if the related media flow(s) was in priority sharing with other media flows the PCF should readjust the Allocation and Retention Priority for the remaining services sharing Allocation and Retention Priority as described in 3GPP TS 29.512 [8], clause 4.2.6.2.9 and handle the media flow removed according to normal PCC/QoS rule provisioning procedures described in 3GPP TS 29.512 [8], clause 4.2.6.2.

4.2.4.10 Report of RAN-NAS release cause

This procedure is used by a PCF to report about the RAN-NAS release cause together with access network information (i.e. user location and/or user timezone information) at the deletion of the "Individual Application Session Context" resource when the "RAN-NAS-Cause" feature is supported.

This procedure is initiated when:

– the "Individual Application Session Context" is deleted by the NF service consumer; or

The PCF shall immediately configure the SMF to provide such RAN-NAS release cause together with access information, as specified in 3GPP TS 29.512 [8].

When the PCF receives the RAN-NAS release cause and access network information from the SMF, the PCF shall provide the corresponding access network information and RAN-NAS release cause to the NF service consumer by including the "EventsNotification" data type in the "200 OK" response to the HTTP POST request. The PCF shall include:

– in case of 3GPP access, the user location information in the "eutraLocation" or in the "nrLocation" attribute in the "ueLoc" attribute, if available;

– in case of untrusted non-3GPP access, the user location information in the "n3gaLocation" attribute in the "ueLoc" attribute, if available, as follows:

a) the user local IP address in the "ueIpv4Addr" or "ueIpv6Addr" attribute;

b) the UDP source port or the TCP source port in the "portNumber" and "protocol" attributes if available; and

c) if the "WLAN_Location" feature is supported, the WLAN location information encoded in the "twapId" attribute, if available, that shall consist of:

i. the SSID in the "ssId" attribute;

ii. the BSSID the "bssId" attribute if available; and

iii. the civic address in the "civicAddress" attribute if available;

– in case of trusted non-3GPP access, the user location information in the "n3gaLocation" attribute in the "ueLoc" attribute, if available, as follows:

a) the user local IP address in the "ueIpv4Addr" or "ueIpv6Addr" attribute, if available; and

b) the UDP source port in the "portNumber" attribute if available; and

NOTE 2: The UDP protocol can be used between the UE and the TNGF to enable NAT traversal.

c) either the TNAP identifier encoded in the "tnapId" attribute or the TWAP identifier encoded in the "twapId" attribute. The TNAP identifier and the TWAP identifier shall consist of:

i. the SSID in the "ssId" attribute;

ii. the BSSID the "bssId" attribute if available; and

iii. the civic address in the "civicAddress" attribute if available;

– the UE timezone in the "ueTimeZone" attribute if available; and

– the RAN and/or NAS release cause in the "ranNasRelCauses" attribute, if available.

The PCF shall also include an event of the "AfEventNotification" data type in the "evNotifs" attribute with the "event" attribute set to the value "RAN_NAS_CAUSE".

4.2.4.11 Termination of Mission Critical Services

If the AF session being terminated corresponds to an MCS session, the PCF shall delete the PCC rules corresponding to the MCS session and the PCF shall revoke the actions related to the prioritisation of the MCS session in the corresponding PDU Session as defined in 3GPP TS 29.512 [8].

4.2.4.12 Report of Service Data Flow QoS Monitoring

If the NF service consumer indicated to be notified of Service Data Flow QoS Monitoring at PDU Session termination, and the PCF reports the QoS monitoring events to the AF, the PCF shall report the Service Data Flow QoS Monitoring to the NF service consumer using the response of the Npcf_PolicyAuthorization_Delete service operation.

This procedure is initiated when the PCF requests the deletion of the "Individual Application Session Context" to the NF service consumer due to PDU session termination as described in clause 4.2.5.3 and the PCF receives the information about Service Data Flow QoS Monitoring from the SMF as specified in clause 4.2.5.5 of 3GPP TS 29.512 [8].

The PCF shall notify the NF service consumer by including the "EventsNotification" data type in the response of the HTTP POST request as described in clause 4.2.4.2. The PCF shall include:

– within the "evNotifs" attribute an event entry of the "AfEventNotification" data type with the matched event "QOS_MONITORING" in the "event" attribute; and

– the "qosMonReports" array with:

a) the identification of the affected service flows (if not all the flows are affected) encoded in the "flows" attribute if applicable; and

b) one or two uplink packet delays within the "ulDelays" attribute;

c) one or two downlink packet delays within the "dlDelays" attribute; and/or

d) one or two round trip packet delays within the "rtDelays" attribute.