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:  18.5.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.16.14 Management of access and mobility related policy information depending on the application in use  4.16.14.1 General  4.16.14.2 Procedures for management of access and mobility related policy information  4.16.14.2.1 Management of access and mobility related policy information at start and stop of application traffic  4.16.14.2.2 Management of access and mobility related policy information at SM Policy Association establishment and termination with the notification sent by the BSF 
...

 

4.16.14  Management of access and mobility related policy information depending on the application in use |R17|  p. 535

4.16.14.1  General  p. 535

The procedure for management of access and mobility related policy information depending on the application in use enables modification of the access and mobility related policy information on detection of the start and stop of an application.
The content of this clause applies to non-roaming and LBO roaming scenario (for any inbound roaming UEs), i.e. to cases where the involved entities (e.g. PCF, SMF and UPF) belong to the serving PLMN. The PCF shall not apply a change of access and mobility related policy information for application traffic detected in PDU Sessions established in Home Routed mode.
If PCF for the UE and PCF for the PDU Session are the same PCF, then steps 3, 5, 6, 9 and 12 in Figure 4.16.14.2.1-1 are not performed.
If the PCF for the UE and the PCF for the PDU Session are different PCFs, then the PCF for the UE is informed when a SM Policy Association is established or released by either:
  • Subscription to the BSF:
    • see steps 2, 3, 4, 5a, 11 and 12a in Figure 4.16.14.2.1-1. The BSF notifies when a PCF is registered or deregistered for the PDU Session to a DNN, S-NSSAI.
    • see steps 2, 3, 5 and 8 in Figure 4.16.14.2.2-1. The BSF reports the registration of a PCF for the PDU Session when the first SM Policy Association is established and the deregistration of the PCF for the PDU Session when the last SM Policy Association is terminated for a (DNN, S-NSSAI).
  • Request to the PCF for the PDU Session to a DNN, S-NSSAI via AMF and SMF. See steps 1, 4, 5b, 11 and 12b in Figure 4.16.14.2.1-1. The PCF for the PDU Session reports that the SM Policy Association is established as described in clause 4.16.4 and provides the UE address(es). The SM Policy Association Termination notifies the PCF for the UE as described in clause 4.16.6.
Up

4.16.14.2  Procedures for management of access and mobility related policy information  p. 535

4.16.14.2.1  Management of access and mobility related policy information at start and stop of application traffic  p. 535
This procedure applies when the AF provides a service coverage area or the indication of high throughput associated with the Application Identifer(s).
Reproduction of 3GPP TS 23.502, Fig. 4.16.14.2.1-1: Management of access and mobility related policy information at start and stop of application traffic
Figure 4.16.14.2.1-1: Management of access and mobility related policy information at start and stop of application traffic
Up
Step 1.
The AMF establishes an AM Policy Association for retrieving access and mobility related policy information, e.g. RFSP index value, as described in clause 4.16.1.2.
Step 2.
If the access and mobility related policy information depends on the application in use, then depending on operator policies in the PCF, the PCF may subscribe to the BSF, then step 3 follows, or provides its PCF binding information to the AMF in step 1 with the indication to be notified about the PCF for the PDU Session for a DNN, S-NSSAI, then step 4 follows.
Step 3.
The PCF for the UE determines that access and mobility related policy information (e.g. RFSP index value) depends on the detection of one or more application(s) in use, the DNN, S-NSSAI used to access each Application Id is configured in the PCF or retrieved from the UDR as part of the Application Data Set, then subscribes to the BSF to be notified when a PCF for the PDU Session for this SUPI is registered in the BSF, by invoking Nbsf_Management_Subscribe (SUPI, list of (DNN, S-NSSAI)(s)). Steps 4 and 5 are repeated for each PCF registered for a PDU Session to a (DNN, S-NSSAI) included in the Nbsf_Management.
Step 4.
The SMF establishes a SM Policy Association as described in clause 4.16.4. The allocated UE address/prefix, SUPI, DNN, S-NSSAI and the PCF address is registered in the BSF, as described in clause 6.1.1.2.2 of TS 23.503.
Step 5a.
If the PCF for the UE subscribed to the BSF, then the BSF notifies that a PCF for the PDU Session is registered in the BSF, by invoking Nbsf_Management_Notify (DNN, S-NSSAI, UE address(es), PCF address, PCF instance id, PCF Set ID, level of binding). When there are multiple PDU Sessions to the same (DNN, S-NSSAI) the BSF provides multiple notification to the PCF.
Step 5b.
If the PCF for the UE sent the request to notify that a PCF for the PDU Session is available to the AMF in step 1, then the PCF for the PDU Sessions sends Npcf_PolicyAuthorization_Notify (EventID set to SM Policy Association established, UE address, PCF address, PCF instance is, PCF Set ID) to the PCF indicated in the PCF binding information provided by the SMF.
Step 6.
The PCF for the UE subscribes to notifications of event "start/stop of application traffic" as defined in clause 6.1.3.18 of TS 23.503, using Npcf_PolicyAuthorization_Subscribe (UE address, EventId, EventFilter set to "list of Application Identifiers") to the PCF for the PDU Session to the DNN, S-NSSAI. The PCF for the PDU Session then generates PCC Rules including the Application Identifier in the SDF template, if there are multiple Application Identifiers included in the Npcf_PolicyAuthorization, the PCF generates PCC Rules for each Application Identifier. The response includes the NotificationCorrelationId.
Step 7.
The PCF installs PCC Rules and the Policy Control Request Trigger to detect "start/stop of application traffic" in the SMF.
Step 8.
The SMF detects that the Policy Control Request Trigger is met, then reports the start/stop of application traffic to the PCF serving the PDU Session.
Step 9.
The PCF for the UE is notified on the start/stop of application traffic by Npcf_PolicyAuthorization_Notify (NotificationCorrelationId, EventId set to "start/stop of application traffic", EventInformation including the ApplicationId). When the reporting of start and stop of a list of Application(s) was requested, the PCF for the PDU Session provides multiple notification to the PCF for the UE.
Step 10.
The PCF checks operator policies and then may change access and mobility related policy information (e.g. RFSP index value) based on the reporting of start/stop of application traffic.
Step 11.
The SM Policy Association is terminated as described in clause 4.16.6. The allocated UE address/prefix, SUPI, DNN, S-NSSAI and the PCF address are deregistered in the BSF.
Step 12a.
If the PCF for the UE subscribed to the BSF, then the BSF notifies that the PCF serving a PDU Session is deregistered in the BSF, by invoking Nbsf_Management_Notify (Binding Identifier for the PDU Session).
Step 12b.
If the PCF for the UE sent the request to notify that a PCF for the PDU Session is available to the AMF in step 1, then the PCF for the PDU Session sends Npcf_PolicyAuthoritation_Notify ((EventID set to SM Policy Association termination, Notification Correlation Id).
Up
4.16.14.2.2  Management of access and mobility related policy information at SM Policy Association establishment and termination with the notification sent by the BSF  p. 538
Reproduction of 3GPP TS 23.502, Fig. 4.16.14.2.2-1: Management of access and mobility related policy information at SM Policy Association establishment and termination with the notification by the BSF
Figure 4.16.14.2.2-1: Management of access and mobility related policy information at SM Policy Association establishment and termination with the notification by the BSF
Up
Step 1.
The AMF establishes an AM Policy Association for retrieving access and mobility related policy information, e.g. RFSP index value, as described in clause 4.16.1.2.
Step 2.
If the access and mobility related policy information depend on the SM Policy Association establishment and termination for a DNN, S-NSSAI combination, then depending on operator policies in the PCF, the PCF may subscribe to BSF and then step 3 follows, or the PCF may provide its PCF binding information to the AMF with the indication to be notified about the PCF for the PDU Session for a DNN, S-NSSAI and then step 4 follows.
Step 3.
The PCF for the UE determines that access and mobility related policy information (e.g. RFSP index value) depend on the detection of SM Policy Association establishment associated with the (DNN, S-NSSAI) combinations configured in the PCF or retrieved from the UDR as part of the Application Data Set. The PCF for the UE then subscribes to the BSF to be notified when a PCF for the PDU Session is registered for the first SM Policy Association establishment and the PCF for the PDU Session is deregistered for the last SM Policy Association termination to the same (DNN, S-NSSAI) combination in the BSF, by invoking Nbsf_Management_Subscribe (SUPI, list of (DNN, S-NSSAI)(s), indication of registration/deregistration per (DNN, S-NSSAI)).
Step 4.
The SMF establishes a SM Policy Association as described in clause 4.16.4. The allocated UE address/prefix, SUPI, DNN, S-NSSAI and the PCF address are registered in the BSF, as described in clause 6.1.1.2.2 of TS 23.503.
Step 5.
If the PCF for the UE subscribed to BSF, then the BSF notifies a PCF registration when the first SM Policy Association corresponding to the (DNN, S-NSSAI) combination is established, by invoking Nbsf_Management_Notify (DNN, S-NSSAI, notification of registration).
Step 6.
The PCF checks operator policies and then may change access and mobility related policy information (e.g. RFSP index value) based on the reporting of SM Policy Association establishment.
Step 7.
The SM Policy Association is terminated as described in clause 4.16.6 and the allocated UE address/prefix, SUPI, DNN, S-NSSAI and the PCF address are deregistered in the BSF.
Step 8.
If the PCF for the UE subscribed to BSF, then BSF notifies of a PCF deregistration when the last SM Policy Association corresponding to the (DNN, S-NSSAI) combination is terminated, by invoking Nbsf_Management_Notify (DNN, S-NSSAI, notification of deregistration).
Up

Up   Top   ToC