Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.502  Word version:  17.4.0

Top   Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.3…   4.3.2.2.2   4.3.2.2.3…   4.3.3…   4.3.4…   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.2.2…   4.11.1.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.7…   4.15.7…   4.16…   4.16.4…   4.16.8…   4.16.11…   4.17…   4.17.9…   4.18…   4.19…   4.23…   4.23.7…   4.23.9…   4.23.11…   4.24…   4.25…   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…

 

4.16.8  Procedures on interaction between PCF and CHFWord‑p. 412

4.16.8.1  GeneralWord‑p. 412

The PCF may interact with the CHF to make PCC decisions based on spending limits. In Home Routed roaming and Non-roaming case, the H-PCF will interact with the CHF in HPLMN.

4.16.8.2  Initial Spending Limit RetrievalWord‑p. 412

This clause describes the signalling flow for the PCF to retrieve the status of the policy counters available at the CHF, and to subscribe to spending limit reporting (i.e. to notifications of policy counter status changes) by the CHF. If the PCF provides the list of policy counter identifier(s), the CHF returns the policy counter status per policy counter identifier provided by the PCF. If the PCF does not provide the list of policy counter identifier(s), the CHF returns the policy counter status of all policy counter(s), which are available for this subscriber.
The Initial Spending Limit Report Retrieval includes all subscriber Identifiers associated with the UE available at the PCF.
Reproduction of 3GPP TS 23.502, Fig. 4.16.8.2-1: Initial Spending Limit Report Retrieval
Up
Step 1.
The PCF retrieves subscription information that indicates that policy decisions depend on the status of policy counter(s) held at the CHF and optionally the list of policy counter identifier(s).
Step 2.
The PCF sends Nchf_SpendingLimitControl_Subscribe if this is the first time policy counter status information is requested for the user identified by a SUPI. It includes: the subscriber ID (e.g. SUPI), the EventId "policy counter status change" and, optionally, the list of policy counter identifier(s) as Event Filter, the Notification Target Address, Event Reporting Information (continuous reporting).
The CHF responds to the Nchf_SpendingLimitControl_Subscribe service operation including the Subscription Correlation Id) and as Event Information provides a policy counter status, and optionally pending policy counter statuses and their activation times, per required policy counter identifier and stores the PCF's subscription to spending limit reports for these policy counters. If no policy counter identifier(s) was provided the CHF returns the list of the policy counter status, optionally including pending policy counter statuses and their activation times, for all policy counter(s), which are available for this subscriber and stores the PCF's subscription to spending limit reports of all policy counters provided to the PCF.
Up

4.16.8.3  Intermediate Spending Limit Report RetrievalWord‑p. 413

This clause describes the signalling flow for the PCF to retrieve the status of additional policy counters available at the CHF or to unsubscribe from spending limit reporting. If the PCF provides the list of policy counter identifier(s), the CHF returns the policy counter status per policy counter identifier provided by the PCF.
Reproduction of 3GPP TS 23.502, Fig. 4.16.8.3-1: Intermediate Spending Limit Report Retrieval
Up
Step 1.
The PCF determines that policy decisions depend on the status of additional policy counter(s) held at the CHF or that notifications of policy counter status changes for some policy counters are no longer required.
Step 2.
The PCF sends Nchf_SpendingLimitControl_Subscribe to the CHF, including the Subscription Correlation Id, the EventId "policy counter status change" and an updated list of policy counter identifier(s) as EventFilters, that overrides the previously stored list of policy counter identifier(s).
The CHF responds to the Nchf_SpendingLimitControl_Subscribe service operation and provides as Event Information the policy counter status, and optionally pending policy counter statuses and their activation times, per required policy counter identifier, and stores or removes the PCF's subscription to spending limit reporting by comparing the updated list with the existing PCF subscriptions. If no policy counter identifier(s) was provided, the CHF returns the policy counter status, optionally including pending policy counter statuses and their activation times, for all policy counter(s), which are available for this subscriber and stores the PCF's subscription to spending limit reports of all policy counters provided to the PCF.
Up

4.16.8.4  Final Spending Limit Report RetrievalWord‑p. 414

This clause describes the signalling flow for the PCF to cancel the subscriptions to status changes for the policy counters available at the CHF.
Reproduction of 3GPP TS 23.502, Fig. 4.16.8.4-1: Final Spending Limit Report Retrieval
Up
Step 1.
The PCF decides that notifications of policy counter status changes are no longer needed.
Step 2.
The PCF sends Nchf_SpendingLimitControl_Unsubscribe including the SubscriptionCorrelationId to the CHF to cancel the subscription to notifications of policy counter status changes from the CHF.
Step 3.
The CHF removes the PCF's subscription to spending limit reporting and responds to the Nchf_SpendingLimitControl_Unsubscribe service operation to the PCF.
Up

4.16.8.5  Spending Limit ReportWord‑p. 415

This clause describes the signalling flow for the CHF to notify the change of the status of the subscribed policy counters available at the CHF for that subscriber. Alternatively, the signalling flow can be used by the CHF to provide one or more pending statuses for a subscribed policy counter together with the time they have to be applied.
Reproduction of 3GPP TS 23.502, Fig. 4.16.8.5-1: Spending Limit Report
Up
Step 1.
The CHF detects that the status of a policy counter(s) has changed and the PCF subscribed to notifications of changes in the status of this policy counter. Alternatively, the CHF may detect that a policy counter status will change at a future point in time, and decides to instruct the PCF to apply one or more pending statuses for a requested policy counter.
Step 2.
The CHF sends Nchf_SpendingLimitControl_Notify with the SUPI, Notification Target Address, and in the Event Information the policy counter status, and optionally pending policy counter statuses and their activation times, for each policy counter that has changed and for which the PCF subscribed to spending limit reporting. Alternatively, the CHF sends one or more pending statuses for any of the subscribed policy counters together with the time they have to be applied.
Step 3.
The PCF acknowledges sending Nchf_SpendingLimitControl_Notify response and takes that information into account as input for a policy decision.
Up

4.16.8.6  CHF report the removal of the subscriberWord‑p. 415

This clause describes the signalling flow for the CHF to report the removal of the subscriber.
Reproduction of 3GPP TS 23.502, Fig. 4.16.8.6-1: CHF report the removal of the subscriber
Up
Step 1.
The CHF decides that a subscriber is removed.
Step 2.
The CHF sends the Nchf_SpendingLimitControl_Notify Request to H-PCF to notify the removal of the subscriber. The H-PCF removes the subscription to notification of policy counter status from CHF.
Step 3.
The H-PCF responds to CHF using Nchf_SpendingLimitControl_Notify to acknowledge the receiving of the notification.
Up

4.16.9  Update of the subscription information in the PCFWord‑p. 416

Reproduction of 3GPP TS 23.502, Fig. 4.16.9-1: Procedure for update of the subscription information in the PCF
Up
Step 0.
The PCF performs the subscription to notification to the profile modified in the UDR by invoking Nudr_DM_Subscribe (Policy Data, SUPI, Notification Target Address (+ Notification Correlation Id), Event Reporting Information (continuous reporting), one or several of the following: "PDU Session Policy Control data", "Remaining allowed Usage data" or "UE context Policy Control data") service.
Step 1.
The UDR detects that the related subscription profile has been changed.
Step 2.
If subscribed by the PCF, the UDR notifies the PCF on the changed profile by invoking Nudr_DM_Notify (Notification Correlation Id, Policy Data, SUPI, updated data and one or several of the following data subtypes "PDU Session Policy Control Data" or "Remaining allowed Usage data" or "UE Context Policy Control data") service.
Step 3.
The PCF stores the updated profile.
Step 4.
If the updated subscriber profile requires the status of new policy counters available at the CHF then an Initial/Intermediate Spending Limit Report Retrieval is initiated by the PCF as defined in clauses 4.16.8,2 and 4.16.8.3. If the updated subscriber profile implies that no policy counter status is needed an Intermediate Spending Limit Report Request Retrieval is initiated by the PCF to unsubscribe or, if this is the last policy counter status, a Final Spending Limit Report Retrieval is initiated by the PCF as specified in clause 4.16.8.4.
Step 5.
PCF makes an authorization and policy decision.
Step 6.
The PCF provides new session management related policy decisions to the SMF, using the Policy related interaction in PDU Session Modification procedure in clause 4.16.6, new access and mobility related policy information to the AMF using the AM Policy Association Modification procedure in clause 4.16.2 or new UE policy information to the AMF using the UE Policy Association Modification procedure in clause 4.16.12.
Up

4.16.10Void


Up   Top   ToC