Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.503  Word version:  17.5.0

Top   Top   Up   Prev   Next
0…   4…   5…   6…   6.1.3…   6.1.3.6…   6.2…   6.2.2…   6.3…   6.4…   6.6…   A…

 

6.1.3  Session management related policy controlWord‑p. 46

6.1.3.1  GeneralWord‑p. 46

The session management related policy control functionality of the Policy and Charging control framework for the 5G system provides the functions for policy and charging control as well as event reporting for service data flows.
The PCF evaluates operator policies that are triggered by events received from the AF, from the SMF, from the AMF and from the CHF as well as changes in User subscription Profile.
The following clauses describe the most relevant session management related functionality in detail.
Up

6.1.3.2  Binding mechanismWord‑p. 46

6.1.3.2.1  GeneralWord‑p. 46
The binding mechanism is the procedure that associates a service data flow (defined in a PCC rule by means of the SDF template), to the QoS Flow deemed to transport the service data flow. For service data flows belonging to AF sessions, the binding mechanism shall also associate the AF session information with the QoS Flow that is selected to carry the service data flow.
The binding mechanism includes three steps:
  1. Session binding;
  2. PCC rule authorization; and
  3. QoS Flow binding.
Up
6.1.3.2.2  Session bindingWord‑p. 46
Session binding is the association of the AF session information to one and only one PDU Session. The PCF shall perform the session binding, which may take the following PDU Session parameters into account:
  1. For an IP type PDU Session, the UE IPv4 address and/or IPv6 network prefix, in addition when using W-5GAN the description in TS 23.316 applies, or when using 5G ProSe Layer-3 UE-to-Network Relay the description in TS 23.304 applies;
    For an Ethernet type PDU Session, the UE MAC address(es);
  2. The UE identity (e.g. SUPI), if present;
  3. The information about the Data Network (DN) the user is accessing, i.e. DNN, if present.
Once it has determined the impacted PDU Session, the PCF shall identify the PCC rules affected by the AF session information, including new PCC rules to be installed and existing PCC rules to be modified or removed.
Session Binding applies for PDU Sessions of IP type. It may also apply to Ethernet PDU Session type but only when especially allowed by PCC related Policy Control Request triggers.
Up
6.1.3.2.3  PCC rule authorizationWord‑p. 47
PCC Rule authorization is the selection of the 5G QoS parameters, described in clause 5.7.2 of TS 23.501, for the PCC rules.
The PCF shall perform the PCC rule authorization for dynamic PCC rules belonging to AF sessions that have been selected in step 1, as described in clause 6.1.3.2.2, as well as for PCC rules without corresponding AF sessions.
For the authorization of a PCC rule the PCF shall consider any 5GC specific restrictions, subscription information and other information available to the PCF. Each PCC rule receives a set of QoS parameters that are supported by the specific Access Network.
The authorization of a PCC rule associated with an emergency service shall be supported without subscription information. The PCF shall apply local policies configured for the emergency service.
The authorization of a PCC rule used for provisioning the UE SNPN credentials via User Plane Remote Provisioning shall be supported without subscription information in the case of Onboarding SNPN (or shall be supported with subscription information in the cases other than Onboarding SNPN). The PCF shall apply policies for support of User Plane Remote Provisioning of UE SNPN Credentials as described in clause 6.1.3.25.
Up
6.1.3.2.4  QoS Flow bindingWord‑p. 47
QoS Flow binding is the association of a PCC rule to a QoS Flow within a PDU Session. The binding is performed using the following binding parameters:
  • 5QI;
  • ARP;
  • QNC (if available in the PCC rule);
  • Priority Level (if available in the PCC rule);
  • Averaging Window (if available in the PCC rule);
  • Maximum Data Burst Volume (if available in the PCC rule).
When the PCF provisions a PCC Rule, the SMF shall evaluate whether a QoS Flow with QoS parameters identical to the binding parameters exists unless the PCF requests to bind the PCC rule to the QoS Flow associated with the default QoS rule. If no such QoS Flow exists, the SMF derives the QoS parameters, using the parameters in the PCC Rule, for a new QoS Flow, binds the PCC Rule to the QoS Flow and then proceeds as described in clause 5.7.1.5 of TS 23.501 to establish the new QoS Flow. If a QoS Flow with QoS parameters identical to the binding parameters exists, the SMF binds the PCC Rule to this QoS Flow and proceeds as described in clause 5.7.1.5 of TS 23.501 to modify the QoS Flow unless local policies or the below mentioned conditions (which QoS Flow binding shall ensure), require the establishment of a new QoS Flow following the actions described above.
The SMF shall identify the QoS Flow associated with the default QoS rule based on the fact that the PCC rule(s) bound to this QoS Flow contain:
  • 5QI and ARP values that are identical to the PDU Session related information Authorized default 5QI/ARP; or
  • a Bind to QoS Flow associated with the default QoS rule and apply PCC rule parameters Indication.
When a QoS Flow associated with the default QoS rule exists, the PCF can request that a PCC rule is bound to this QoS Flow by including the Bind to QoS Flow associated with the default QoS rule Indication in a dynamic PCC rule. In this case, the SMF shall bind the dynamic PCC rule to the QoS Flow associated with the default QoS rule (i.e. ignoring the binding parameters) and keep the binding as long as this indication remains set. When the PCF removes the association of a PCC rule to the QoS Flow associated with the default QoS rule, a new binding may need to be created between this PCC rule and a QoS Flow based on the binding mechanism described above.
The binding created between a PCC Rule and a QoS Flow causes the downlink part of the service data flow to be directed to the associated QoS Flow at the UPF (as described in clause 5.7.1 of TS 23.501). In the UE, the QoS rule associated with the QoS Flow (which is generated by the SMF and explicitly signalled to the UE as described in clause 5.7.1 of TS 23.501) instructs the UE to direct the uplink part of the service data flow to the QoS Flow in the binding.
Whenever the binding parameters of a PCC rule changes, the binding of this PCC rule shall be re-evaluated, i.e. the binding mechanism described above is performed again. The re-evaluation may, for a PCC rule, result in a new binding with another QoS Flow. If the PCF requests the same change of the binding parameter value(s) for all PCC rules that are bound to the same QoS Flow, the SMF should not re-evaluate the binding of these PCC rules and instead, modify the QoS parameter value(s) of the QoS Flow accordingly.
When the PCF removes a PCC Rule, the SMF shall remove the association of the PCC Rule to the QoS Flow. If the last PCC rule that is bound to a QoS Flow is removed, the SMF shall delete the QoS Flow.
When a QoS Flow is removed, the SMF shall remove the PCC rules bound to this QoS Flow and report to the PCF that the PCC Rules bound to a QoS Flow are removed.
The QoS Flow binding shall also ensure that:
  • when the PCF provisions a PCC rule, and if the PCC rule contains a TSC Assistance Container, the PCC rule is bound to a new QoS Flow and no other PCC rule is bound to this QoS Flow. Whenever the TSC Assistance Container of an existing PCC rule is changed, the binding of this PCC rule shall not be re-evaluated.
  • if a dynamic value for the Core Network Packet Delay Budget (defined in clause 5.7.3.4 of TS 23.501) is used, PCC rules with the same above binding parameters but different PDU Session anchors (i.e. the corresponding service data flows which have different CN PDBs) are not bound to the same QoS Flow.
  • For MA PDU Session, PCC rules for GBR or delay critical GBR service data flows allowed on different access are not bound to the same QoS Flow even if the PCC rules contain the same binding parameters.
  • When the PCF provisions a PCC rule with QoS Monitoring Policy, the PCC rule is bound to a new QoS Flow and no other PCC rules is bound to this QoS Flow.
Up

6.1.3.3  ReportingWord‑p. 48

Reporting refers to the differentiated PDU Session resource usage information (measured at the UPF) being reported by the SMF to the CHF.
The SMF shall report usage information for online and offline charging.
The SMF shall report usage information for each charging key value.
For service data flow charging, for the case of sponsored data connectivity, the reports for offline charging shall report usage for each charging key, Sponsor Identity and Application Service Provider Identity combination if Sponsor Identity and Application Service Provider Identifier have been provided in the PCC rules.
The SMF shall report usage information for each charging key/service identifier combination if service identifier level reporting is requested in the PCC rule.
Charging information shall be reported based on the result from the service data flow detection and measurement on a per PDU Session basis.
A report may contain multiple containers, each container associated with a charging key, charging key and Sponsor Identity (in the case of sponsored connectivity) or charging key/service identifier.
Up

6.1.3.4  Credit managementWord‑p. 49

The credit management applies only for service data flow with online charging method and shall operate on a per charging key basis. The SMF should initiate one charging session with the CHF for each PDU Session subject to charging, in order to perform credit management within the charging session.
The SMF shall request a credit for each charging key occurring in a PCC rule. It shall be up to operator configuration whether the SMF shall request credit in conjunction with the PCC rule being activated or when the first packet corresponding to the service is detected. The CHF may either grant or deny the request for credit. The CHF shall strictly control the rating decisions.
During PDU Session establishment and modification, the SMF shall request credit using the information after applying policy enforcement action (e.g. upgraded or downgraded QoS information), if applicable, even though the SMF has not signalled this information to the AMF or RAN.
The events trigger information which may be received from the CHF, causing the SMF to perform a usage reporting and credit request to CHF when the event occurs are specified in TS 32.255.
The CHF may subscribe to Change of UE presence in Presence Reporting Area at any time during the life time of the charging session as described in TS 32.255.
If the PCF set the Out of credit event trigger (see clause 6.1.3.5), the SMF shall inform the PCF about the PCC rules for which credit is no longer available together with the applied termination action.
Up

6.1.3.5  Policy Control Request Triggers relevant for SMFWord‑p. 49

The Policy Control Request Triggers relevant for SMF define the conditions when the SMF shall interact again with PCF after a PDU Session establishment as defined in the Session Management Policy Establishment and Session Management Policy Modification procedure as defined in TS 23.502.
The PCR triggers are not applicable any longer at termination of the SM Policy Association.
The access independent Policy Control Request Triggers relevant for SMF are listed in Table 6.1.3.5-1.
The differences with Table 6.2 and Table A.4.3-2 in TS 23.203 are shown, either "none" means that the parameter applies in 5GS or "removed" meaning that the parameter does not apply in 5GS, this is due to the lack of support in the 5GS for this feature or "modified" meaning that the parameter applies with some modifications defined in the parameter.
Policy Control Request Trigger Description Difference compared with Table 6.2 and Table A.4.3-2 in TS 23.203 Conditions for reporting Motivation
PLMN changeThe UE has moved to another operators' domain.NonePCF
QoS changeThe QoS parameters of the QoS Flow has changed.RemovedOnly applicable when binding of bearers was done in PCRF.
QoS change exceeding authorizationThe QoS parameters of the QoS Flow has changed and exceeds the authorized QoS.RemovedOnly applicable when binding of bearers was done in PCRF.
Traffic mapping information changeThe traffic mapping information of the QoS profile has changed.RemovedOnly applicable when binding of bearers was done in PCRF.
Resource modification requestA request for resource modification has been received by the SMF.NoneSMF always reports to PCF
Routing information changeThe IP flow mobility routing information has changed (when IP flow mobility as specified in TS 23.261 applies) or the PCEF has received Routing Rules from the UE (when NBIFOM as specified in TS 23.161 applies).RemovedNot in 5GS yet.
Change in Access Type (NOTE 8)The Access Type and, if applicable, the RAT Type of the PDU Session has changed.NonePCF
EPS FallbackEPS fallback is initiatedAddedPCF
Loss/recovery of transmission resourcesThe Access type transmission resources are no longer usable/again usable.RemovedNot in 5GS yet.
Location change (serving cell) (NOTE 6) The serving cell of the UE has changed.NonePCF
Location change (serving area) (NOTE 2)The serving area of the UE has changed.NonePCF
Location change (serving CN node) (NOTE 3)The serving core network node of the UE has changed.NonePCF
Change of UE presence in Presence Reporting Area (see NOTE 1)The UE is entering/leaving a Presence Reporting Area.NonePCFOnly applicable to PCF
Out of creditCredit is no longer available.NonePCF
Reallocation of creditCredit has been reallocated after the former Out of credit indication.AddedPCF
Enforced PCC rule requestSMF is performing a PCC rules request as instructed by the PCF.NonePCF
Enforced ADC rule requestTDF is performing an ADC rules request as instructed by the PCRF.RemovedADC Rules are not applicable.
UE IP address change A UE IP address has been allocated/released.NoneSMF always reports allocated or released UE IP addresses
UE MAC address changeA new UE MAC address is detected or a used UE MAC address is inactive for a specific period.NewPCF
Access Network Charging Correlation InformationAccess Network Charging Correlation Information has been assigned.NonePCF
Usage report (NOTE 4)The PDU Session or the Monitoring key specific resources consumed by a UE either reached the threshold or needs to be reported for other reasons.NonePCF
Start of application traffic detection and Stop of application traffic detection (NOTE 5)The start or the stop of application traffic has been detected.NonePCF
SRVCC CS to PS handoverA CS to PS handover has been detected.RemovedNo support in 5GS yet
Access Network Information reportAccess information as specified in the Access Network Information Reporting part of a PCC rule.NonePCF
Credit management session failureTransient/Permanent failure as specified by the CHF.NonePCF
Addition / removal of an access to an IP-CAN session The PCEF reports when an access is added or removed.RemovedNo support in 5GS yet
Change of usability of an access The PCEF reports that an access becomes unusable or usable again.RemovedNo support in 5GS yet
3GPP PS Data Off status changeThe SMF reports when the 3GPP PS Data Off status changes.NoneSMF always reports to PCF
Session AMBR changeThe Session-AMBR has changed.AddedSMF always reports to PCF
Default QoS changeThe subscribed QoS has changed.AddedSMF always reports to PCF
Removal of PCC ruleThe SMF reports when the PCC rule is removed.AddedSMF always reports to PCF
Successful resource allocationThe SMF reports to the PCF that the resources for a PCC rule have been successfully allocated.AddedPCF
GFBR of the QoS Flow can no longer (or can again) be guaranteed The SMF notifies the PCF when receiving notifications from RAN that GFBR of the QoS Flow can no longer (or can again) be guaranteed.Added
UE resumed from suspend stateThe SMF reports to the PCF when it detects that the UE is resumed from suspend state.NonePCFOnly applicable to EPC IWK
Change of DN Authorization Profile IndexThe DN Authorization Profile Index received from DN-AAA has changed.AddedSMF always reports to PCF
5GS Bridge information available SMF has detected new 5GS Bridge information, which may contain, user-plane Node ID, UE-DS-TT residence time and Ethernet port (port number and MAC address) or IP address for the PDU Session and/or PMIC and/or UMIC.AddedPCF
QoS Monitoring for URLLCThe SMF notifies the PCF of the QoS Monitoring information (e.g. UL packet delay, DL packet delay or round trip packet delay).AddedPCF
DDN Failure event Subscription with Traffic DescriptorThe SMF requests PCF to provide or remove policies if it received an event subscription or cancellation for DDN Failure event including traffic descriptors. The SMF provides the traffic descriptors to the PCF for policy evaluation.AddedPCF
DDD Status event Subscription with Traffic DescriptorThe SMF requests PCF to provide or remove policies if it received an event subscription or cancellation for DDD Status event including traffic descriptors. The SMF provides the traffic descriptors and the requested type(s) of notifications (notifications about downlink packets being buffered, and/or discarded) to the PCF for policy evaluation.AddedPCF
QoS constraints changeThe QoS constraints in the VPLMN have been provided or changed.AddedSMF always reports to PCF
Satellite backhaul category changeThe backhaul is changed between different satellite backhaul categories, or between satellite backhaul and non-satellite backhaul.AddedPCF
NWDAF info changeThe NWDAF instance IDs used for the PDU session or associated Analytics IDs used for the PDU session and available in the SMF have changed.AddedPCF
Request for notification on SM Policy Association establishment or termination (NOTE 9)The SMF reports to the PCF the request to notify on the established or terminated SM Policy Association.AddedPCF
NOTE 1:
The maximum number of PRA(s) per UE per PDU Session is configured in the PCF. The PCF may have independent configuration of the maximum number for Core Network pre-configured PRAs and UE-dedicated PRAs. The exact number(s) should be determined by operator in deployment.
NOTE 2:
This trigger reports change of Tracking Area in both 5GS and EPC interworking, or reports change of Routing Area for GERAN/UTRAN access (see Annex G of TS 23.502).
NOTE 3:
This trigger reports change of AMF in 5GC, change between ePDG and Serving GW in EPC, change between Serving GWs in EPC, change between EPC and 5GC, change between Serving Gateway and SGSN in GERAN/UTRAN from/to E-UTRAN mobility, or change between SGSNs in the case of GERAN/UTRAN access. In HR roaming case, if the AMF change is unknown by the H-SMF, then the AMF change is not reported.
NOTE 4:
Usage is defined as either volume or time of user plane traffic.
NOTE 5:
The start and stop of application traffic detection are separate event triggers, but received under the same subscription from the PCF.
NOTE 6:
Location change of serving cell can increase signalling load on multiple interfaces. Hence it is recommended that any such serving cell changes only applied for a limited number of subscribers avoiding extra signalling load. It also is applicable for GERAN/UTRAN access.
NOTE 7:
Void.
NOTE 8:
For 3GPP access the RAT type may refer to NR, E-UTRAN, and, when the SMF+PGW-C enhancements to support GERAN/UTRAN access via Gn/Gp interface as specified in Annex L of TS 23.501 apply, to UTRAN or GERAN. For MA PDU Session this trigger reports the current used Access Type(s) and RAT type(s) upon any change of Access Type and RAT type.
NOTE 9:
The PCF for the PDU Session knows the change of the PCF for the UE by this Policy Control Request Trigger based on the associated binding information of and notifies the PCF for the UE as described in clause 6.1.3.18.
When the EPS Fallback trigger is armed by the PCF, the SMF shall report the event to the PCF when a QoS Flow with 5QI=1 is rejected due to EPS Fallback.
When the Location change trigger is armed, the SMF shall subscribe to the AMF for reports on changes in location to the level indicated by the trigger. If credit-authorization triggers and Policy Control Request Triggers require different levels of reporting of location change for a single UE, the location to be reported should be changed to the highest level of detail required. However, there should be no request being triggered for PCC rules update to the PCF if the report received is more detailed than requested by the PCF.
The Resource modification request trigger shall trigger the PCF interaction for all resource modification requests not tied to a specific QoS Flow received by SMF. The resource modification request received by SMF may include request for guaranteed bit rate changes for a traffic aggregate and/or the association/disassociation of the traffic aggregate with a 5QI and/or a modification of the traffic aggregate.
The enforced PCC rule request trigger shall trigger a SMF interaction to request PCC rules from the PCF for an established PDU Session. This SMF interaction shall take place within the Revalidation time limit set by the PCF in the PDU Session related policy information. The SMF reports that the enforced PCC rule request trigger was met and the enforced PCC Rules.
The UE IP address change trigger shall trigger a SMF interaction with the PCF if a UE IP address is allocated or released during the lifetime of the PDU Session. The SMF reports that the UE IP address change trigger was met and the new or released UE IP address.
The UE MAC address change trigger shall trigger a SMF interaction with the PCF if a new UE MAC address is detected or a used UE MAC address is inactive for a specific period during the lifetime of the Ethernet type PDU Session. The SMF reports that the UE MAC address change trigger was met and the new or released UE MAC address.
The Access Network Charging Correlation Information trigger shall trigger the SMF to report the assigned access network charging identifier for the PCC rules that are accompanied with a request for this trigger at activation. The SMF reports that the Access Network Charging Correlation Information trigger was met and the Access Network Charging Correlation Information.
If the Usage report trigger is set and the volume or the time thresholds, earlier provided by the PCF, are reached, the SMF shall report this situation to the PCF. If both volume and time thresholds were provided and the thresholds, for one of the measurements, are reached, the SMF shall report this situation to the PCF and the accumulated usage since last report shall be reported for both measurements.
The management of the Presence Reporting Area (PRA) functionality enables the PCF to subscribe to reporting change of UE presence in a particular Presence Reporting Area.
Upon every interaction with the SMF, the PCF may activate / deactivate reporting changes of UE presence in Presence Reporting Area by setting / unsetting the corresponding trigger by providing the PRA Identifier(s) and additionally the list(s) of elements comprising the Presence Reporting Area for UE-dedicated Presence Reporting Area(s).
The SMF shall subscribe to the UE Location Change notification from the AMF by providing an area of interest containing the PRA Identifier(s) and additionally the list(s) of elements provided by the PCF as specified in clause 5.6.11 of TS 23.501 and in clause 5.2.2.3.1 of TS 23.502.
When the Change of UE presence in Presence Reporting Area trigger is armed, i.e. when the PCF subscribes to reporting change of UE presence in a particular Presence Reporting Area and the reporting change of UE presence in this Presence Reporting Area was not activated before, the SMF subscribes to the UE mobility event notification service provided by the AMF for reporting of UE presence in Area of Interest which reports when the UE enters or leaves a Presence Reporting Area (an initial report is received when the PDU Session specific procedure is activated). The SMF reports the PRA Identifier(s) and indication(s) whether the UE is inside or outside the Presence Reporting Area(s), and indication(s) if the corresponding Presence Reporting Area(s) is set to inactive by the AMF to the PCF.
When PCF modifies the list of PRA id(s) to change of UE presence in Presence Reporting Area for a particular Presence Reporting Area(s), the SMF removes or adds the PRA id(s) provided in the UE mobility event notification service provided by AMF for reporting of UE presence in Area Of Interest. When the PCF unsubscribes to reporting change of UE presence in Presence reporting Area, the SMF unsubscribes to the UE mobility event notification service provided by AMF for reporting of UE presence in Area Of Interest, unless subscriptions to AMF remains due to other triggers.
The SMF stores PCF subscription to reporting for changes of UE presence in Presence Reporting Area and notifies the PCF with the PRA Identifier(s) and indication(s) whether the UE is inside or outside the Presence Reporting Area(s) based on UE location change notification in area of interest received from the serving node according to the corresponding subscription.
If PCF is configured with a PRA identifier referring to the list of PRA Identifier(s) within a Set of Core Network predefined Presence Reporting Areas as defined in TS 23.501, it activates the reporting of UE entering/leaving each individual PRA in the Set of Core Network predefined Presence Reporting Areas, without providing the complete set of individual PRAs.
When a PRA set identified by a PRA Identifier was subscribed to report changes of UE presence in Presence Reporting Area by the PCF, the SMF additionally receives the PRA Identifier of the PRA set from the AMF, along with the individual PRA Identifier(s) belonging to the PRA set and indication(s) of whether the UE is inside or outside the individual Presence Reporting Area(s), as described in TS 23.501.
When the Out of credit detection trigger is set, the SMF shall inform the PCF about the PCC rules for which credit is no longer available together with the applied termination action.
When the Reallocation of credit detection trigger is set, the SMF shall inform the PCF about the PCC rules for which credit has been reallocated after credit was no longer available and the termination action was applied.
The Start of application traffic detection and Stop of application traffic detection triggers shall trigger an interaction with PCF once the requested application traffic is detected (i.e. Start of application traffic detection) or the end of the requested application traffic is detected (i.e. Stop of application traffic detection) unless it is requested within a specific PCC Rule to mute such interaction for solicited application reporting or unconditionally in the case of unsolicited application reporting. The application identifier and service data flow descriptions, if deducible, shall also be included in the report. An application instance identifier shall be included in the report both for Start and for Stop of application traffic detection when service data flow descriptions are deducible. This is done to unambiguously match the Start and the Stop events.
At PCC rule activation, modification and deactivation the SMF shall send, as specified in the PCC rule, the User Location Report and/or UE Timezone Report to the PCF.
If the trigger for Access Network Information reporting is set, the SMF shall check the need for access network information reporting after successful installation/modification or removal of a PCC rule or upon termination of the PDU Session. The SMF shall check the Access Network Information report parameters (User Location Report, UE Timezone Report) of the PCC rules and report the access network information to the PCF. The SMF shall not report any subsequent access network information updates received from the PDU Session without any previous updates of related PCC rule unless the associated QoS Flow or PDU Session has been released.
If the SMF receives a request to install/modify or remove a PCC rule with Access Network Information report parameters (User Location Report, UE Timezone Report) set the SMF shall initiate a PDU Session modification to retrieve the current access network information of the UE and forward it to the PCF afterwards.
If the Access Network Information report parameter for the User Location Report is set and the user location (e.g. cell) is not available to the SMF, the SMF shall provide the serving PLMN identifier to the PCF.
The Credit management session failure trigger shall trigger a SMF interaction with the PCF to inform about a credit management session failure and to indicate the failure reason, and the affected PCC rules.
The default QoS change triggers shall trigger the PCF interaction for all changes in the default QoS data received in SMF from the UDM.
The Session AMBR change trigger shall trigger the SMF to provide the Session-AMBR to the PCF containing the DN authorised Session AMBR if received from the DN-AAA, or the Subscribed Session-AMBR received from the UDM as described in clause 5.6.6 of TS 23.501.
The default QoS change trigger reports a change in the default 5QI/ARP retrieved by SMF from UDM, as explained in clause 5.7.2.7 of TS 23.501.
If the PCC Rules bound to a QoS Flow are removed when the corresponding QoS Flow is removed or the PCC rules are failed to be enforced, the SMF shall report this situation to the PCF. The PCF may then provide the same or updated PCC rules for the established PDU Session.
If the trigger for successful resource allocation is set and the PCF has also provided an indication that a specific PCC rule is subject to this trigger, the SMF shall report to the PCF when the resources associated to this PCC rule have been successfully allocated. The SMF shall report resource allocation failure always to the PCF, independently of this trigger.
If the GFBR of the QoS Flow can no longer (or can again) be guaranteed trigger is armed, the SMF shall check the need for reporting to the PCF when the SMF receives an explicit notification from (R)AN indicating that GFBR of the QoS Flow can no longer (or can again) be guaranteed or when the condition described in clause 5.7.2.4 of TS 23.501 is met during the handover. The SMF shall report that GFBR of the QoS Flow can no longer (or can again) be guaranteed accordingly to the PCF for those PCC rules which are bound to the affected QoS Flow and have the QoS Notification Control (QNC) parameter set. If additional information is received with the notification from NG-RAN (see clause 5.7.2.4 of TS 23.501), the SMF shall also provide to the PCF the reference to the Alternative QoS parameter set corresponding to the Alternative QoS Profile referenced by NG-RAN. If NG-RAN has indicated that the lowest priority Alternative QoS Profile cannot be fulfilled, the SMF shall indicate to the PCF that the lowest priority Alternative QoS parameter set cannot be fulfilled.
In an interworking scenario between 5GS and EPC/E-UTRAN, as explained in clause 4.3 of TS 23.501, the PCF may subscribe via the SMF also to the Policy Control Request Triggers described in clause 6.1.2.5 when the UE is served by the EPC/E-UTRAN.
The change of DN Authorization Profile Index shall trigger a SMF interaction to send DN Authorization Profile Index to retrieve a list of PCC Rules (as defined in clause 6.3) and/or PDU Session related policy (as defined in clause 6.4) for an established PDU Session.
If the trigger for 5GS Bridge information available is armed, the SMF shall report the 5GS Bridge information when the SMF has determined or updated the 5GS Bridge information, e.g. when SMF has detected an Ethernet port which supports exchange of Ethernet Port Management Information Containers or received User plane node Management Information Container or Port Management Information Container. If a new manageable Ethernet DS-TT port is detected, the SMF provides User plane node ID, the port number and optionally MAC address of the related port of the related PDU Session to the PCF. If the SMF has received UE-DS-TT Residence Time then the SMF also provides UE-DS-TT Residence Time to the PCF. If the SMF has received the User plane node Management Information Container from NW-TT or Port Management Information Container from NW-TT or DS-TT, the SMF also provides User plane node Management Information Container or Port Management Information Container and related port number to the PCF.
When the QoS Monitoring for URLLC trigger is set, the SMF shall indicate the RAN and the UPF to perform the measurement of the QoS parameters based on the PCC rule information for QoS Monitoring as defined in clause 4.3.3.2 of TS 23.502. Upon receiving the QoS Monitoring report from the UPF, the SMF sends the measurement report to the PCF.
If the Policy Control Request Trigger "DDN Failure event subscription with Traffic Descriptor" or "DDD Status event subscription with Traffic Descriptor" is set, the SMF shall request policies if it received a subscription or cancellation of notifications for availability after DDN Failure event with traffic descriptor or DDD Status event with traffic descriptor, respectively. The SMF indicates whether it is a subscription or cancellation event and provides the received Traffic Descriptor as well as the requested type(s) of notifications (notifications about downlink packets being buffered, and/or discarded) to the PCF. When the SMF indicates a subscription event, the PCF checks whether an installed PCC rule exists for the received Traffic Descriptor and if so, the PCF sets the Downlink Data Notification Control information of that PCC rule according to the requested type(s) of notifications. Otherwise, the PCF provides a new PCC Rule with the received Traffic Descriptor in the SDF Template, the Downlink Data Notification Control information set according to the requested type(s) of notifications and other PCC Rule information set to the same values as in the existing PCC rule that previously matched the traffic. When the new PCC has to be bound to the QoS Flow associated with the default QoS rules, the PCF sets the "Bind to QoS Flow associated with the default QoS rule" parameter. From now on, the PCF needs to keep the PCC rule for the DDD event detection fully synchronized with the existing PCC rule that previously matched the traffic for all other policy and charging control settings to ensure the same user experience and traffic treatment according to the operator policy. When the SMF indicates a cancellation event, the PCF removes the Downlink Data Notification Control information in the installed PCC Rule or removes the PCC Rule if a new PCC rule has been provided during the subscription event and this PCC rule is no longer necessary for any other policy enforcement.
The QoS constraints change trigger shall trigger a SMF interaction with the PCF if QoS constraints are received by the SMF during the lifetime of the PDU Session. The SMF reports that the QoS constraints change trigger was met and the new QoS constraints.
When the Satellite backhaul category change trigger is armed, the SMF reports to the PCF that the Satellite backhaul category change was met and the new satellite backhaul category (or that satellite backhaul is no longer used) when it becomes aware that there is a change of the backhaul which is used for the PDU Session between satellite backhaul categories, or between satellite backhaul and a non-satellite backhaul. The SMF determines whether or not a satellite backhaul is used and whether there is a change of backhaul based on signalling from the AMF as specified in TS 23.501.
The NWDAF info change trigger shall trigger the SMF to interact with the PCF when the list of NWDAF Instance IDs used for the PDU Session or associated Analytics IDs used for the PDU Session are changed in the SMF.
The Request for notification on SM Policy Association establishment or termination indicates to the SMF that the request from the AMF to notify on the established or terminated SM Policy Association should be sent to the PCF together with the received PCF binding information.
Up

Up   Top   ToC