Content for  TS 23.503  Word version:  19.1.0

The Policy and charging control rule (PCC rule) comprises the information that is required to enable the user plane detection of, the policy control and proper charging for a service data flow. The packets detected by applying the service data flow template of a PCC rule form a service data flow. Two different types of PCC rules exist: Dynamic rules and predefined rules. The dynamic PCC rules are provisioned by the PCF to the SMF, while the predefined PCC rules are configured into the SMF, as described in TS 23.501, and only referenced by the PCF. The operator defines the PCC rules. Table 6.3.1 lists the information contained in a PCC rule, including the information name, the description and whether the PCF may modify this information in a dynamic PCC rule which is active in the SMF. The Category field indicates if a certain piece of information is mandatory or not for the construction of a PCC rule, i.e. if it is possible to construct a PCC rule without it. The differences with Table 6.3 in TS 23.203 are shown, either "none" means that the IE applies in 5GS or "removed" meaning that the IE does not apply in 5GS, this is due to the lack of support in the 5GS for this feature or "modified" meaning that the IE applies with some modifications defined in the IE.

The Rule identifier shall be unique for a PCC rule within a PDU Session. A dynamically provided PCC rule that has the same Rule identifier value as a predefined PCC rule shall replace the predefined rule within the same PDU Session. The Precedence defines in what order the activated PCC rules within the same PDU Session shall be applied at the UPF for service data flow detection. When a dynamic PCC rule and a predefined PCC rule have the same precedence, the dynamic PCC rule takes precedence. For downlink packets all the service data flow templates, activated for the PDU Session shall be applied for service data flow detection and for the mapping to the correct QoS Flow. For uplink packets the service data flow templates activated on their QoS Flow shall be applied for service data flow detection (further details are provided in clause 6.2.2.2). The Service data flow template may comprise any number of Service data flow filters or an application identifier as is defined in Table 6.3.1. A Service data flow filter contains information for matching user plane packets for IP PDU traffic or Ethernet PDU traffic. All Service data flow filters of a Service data flow template shall be of the same type, i.e. either Packet Filters for IP or Ethernet PDU traffic (defined in clause 5.7.6 of TS 23.501). The Service data flow template information within an activated PCC rule is applied by the SMF to instruct the UPF to identify the packets belonging to a particular service data flow. For the IP PDU Session type only, the Service data flow template may consist of an application identifier that references an application detection filter that is used for matching user plane packets. The application identifier is also identifying the application, for which the rule applies. The same application identifier value can occur in a dynamic PCC rule and one or multiple predefined PCC rules. If so, the PCF shall ensure that there is at most one PCC rule active per application identifier value at any time. The Mute for notification defines whether notification to the PCF of application's starts or stops shall be muted. Absence of this parameter means that start/stop notifications shall be sent. The Charging key is the reference to the tariff for the service data flow. Any number of PCC Rules may share the same charging key value. The Charging key values for each service shall be operator configurable. The Service identifier identifies the service. PCC Rules may share the same service identifier value. The service identifier provides the most detailed identification, specified for flow-based charging, of a service data flow. The Sponsor Identifier indicates the (3rd) party organization willing to pay for the operator's charge for connectivity required to deliver a service to the end user. The Application Service Provider Identifier indicates the (3rd) party organization delivering a service to the end user. The Charging method indicates whether online charging or offline charging is required, or the service data flow is not subject to any end user charging. If the charging method identifies that the service data flow is not subject to any end user charging, a Charging key shall not be included in the PCC rule for that service data flow, along with other charging related parameters. If the charging method is omitted the SMF shall apply the default charging method provided within the PDU Session related policy information (see clause 6.4). The Charging method is mandatory if there is no default charging method for the PDU Session. The Service Data Flow handling while requesting credit indicates either "blocking" if a credit for the Charging Key needs to be granted as a condition for the PCC Rule to be active or "non-blocking" if a credit for the Charging Key has been requested as a condition for the PCC Rule to be active. The Measurement method indicates what measurements apply to charging for a PCC rule. The Service Identifier Level Reporting indicates whether the SMF shall generate reports per Service Identifier. The SMF shall accumulate the measurements from all PCC rules with the same combination of Charging key/Service Identifier values in a single report. The Application Function Record Information identifies an instance of service usage. A subsequently generated usage report (i.e. CDR), generated as a result of the PCC rule by the SMF, may include the Application Function Record Information, if available. The Application Function Record Information may contain the AF Charging Identifier and/or the Flow identifiers. If exclusive charging information related to the Application function record information is required, the PCF shall provide a service identifier, not used by any other PCC rule of the PDU Session at this point in time, for the AF session. The Gate indicates whether the SMF shall instruct the UPF to let a packet identified by the PCC rule pass through (gate is open) to discard the packet (gate is closed). The 5G QoS Identifier, 5QI, represents the QoS parameters for the service data flow. The 5G QoS identifier is scalar and accommodates the need for differentiating QoS in both 3GPP and non-3GPP access type. The bitrates indicate the authorized bitrates at the IP packet level of the SDF, i.e. the bitrates of the IP packets before any access specific compression or encapsulation. The UL maximum-bitrate indicates the authorized maximum bitrate for the uplink component of the service data flow. The DL maximum-bitrate indicates the authorized maximum bitrate for the downlink component of the service data flow. The UL guaranteed-bitrate indicates the authorized guaranteed bitrate for the uplink component of the service data flow. The DL guaranteed-bitrate indicates the authorized guaranteed bitrate for the downlink component of the service data flow. The 'Maximum bitrate' is used for enforcement of the maximum bit rate that the SDF may consume, while the 'Guaranteed bitrate' is used by the SMF to determine resource allocation demands. The UL sharing indication indicates that resource sharing in uplink direction for service data flows with the same value in their PCC rule shall be applied by the SMF as described in clause 6.2.2.4. The DL sharing indication indicates that resource sharing in downlink direction for service data flows with the same value in their PCC rule shall be applied by the SMF as described in clause 6.2.2.4. The Allocation and Retention Priority indicates the allocation, retention and priority of the service data flow. The ARP contains information about the priority level, the pre-emption capability and the pre-emption vulnerability. The Allocation and Retention Priority resolves conflicts of demands for network resources. The Priority Level is signalled together with the 5QI to the (R)AN and UPF, only when a value different from the standardized value in the QoS characteristics Table 5.7.4-1 in TS 23.501 is required. The Averaging Window is signalled together with the 5QI to the (R)AN and UPF, only when a value different from the standardized value in the QoS characteristics Table 5.7.4-1 in TS 23.501 is required. The Maximum Data Burst Volume, MDBV, is signalled together with the 5QI to the (R)AN, only when a value different from the standardized value in the QoS characteristics Table 5.7.4-1 in TS 23.501 is required. The Bind to QoS Flow associated with the default QoS rule indicates that the SDF shall be bound to the QoS Flow associated with the default QoS rule. The presence of this parameter attribute causes the 5QI/ARP of the rule to be ignored by the SMF during the QoS Flow binding. The Bind to QoS Flow associated with the default QoS rule and apply PCC rule parameters indicates that the SDF shall be bound to the QoS Flow associated with the default QoS rule and that the QoS related attributes of the PCC rule shall be applied by the SMF to derive the QoS parameters of the QoS Flow associated with the default QoS rule instead of the PDU Session related information Authorized default 5QI/ARP. The QoS Notification Control, QNC, indicates whether notifications are requested from the access network (i.e. 3GPP RAN) when the GFBR can no longer (or can again) be guaranteed for a QoS Flow during the lifetime of the QoS Flow. If it is set and the GFBR can no longer (or can again) be guaranteed, the access network (i.e. 3GPP RAN) sends a notification towards the SMF, which then notifies the PCF. The Disable UE notifications at changes related to Alternative QoS Profiles parameter indicates to disable QoS Flow parameters signalling to the UE when the SMF is notified by the NG-RAN of changes in the fulfilled QoS situation. The fulfilled situation is either the QoS profile or an Alternative QoS Profile. The Precedence for TFT packet filter allocation parameter determines the order in which TFT packet filters are allocated for PCC rules. The PCF may include this parameter if there is a possibility to run into a restriction regarding the number of TFT packet filters that can be allocated for the PDU Session and interworking with EPS with N26 deployment is supported (see also clause 4.11.1 of TS 23.502). The Reflective QoS Control indicates to apply reflective QoS for the service data flow. The indication is used to control the RQI marking in the DL packets of the service data flow and may trigger the sending of the RQA parameter for the QoS Flow the service data flow is bound to. Reflective QoS is defined in clause 5.7.5 of TS 23.501. The Reflective QoS Control parameter shall not be used for the PCC rule with match-all SDF template. If PCC rule with match-all SDF template is present, the Reflective QoS Control parameter shall not be used for PCC rules which contain the Bind to QoS Flow of the default QoS rule parameter, either. The N6-LAN Traffic Steering Enforcement Control contains Traffic steering policy identifier(s) for steering traffic onto N6-LAN to the appropriate N6 service functions deployed by the operator or a third party, and optional Metadata if received from AF due to Application Function influence on Service Function Chaining as described in clause 5.6.16 of TS 23.501. The ECN marking for L4S indicates that the service data flow supports ECN marking for L4S to be performed. The access network information reporting parameters (User Location Report, UE Timezone Report) instruct the SMF about what information to forward to the PCF when the PCC rule is activated, modified or removed. The Monitoring Key is the reference to a resource threshold. Any number of PCC Rules may share the same monitoring key value. The monitoring key values for each service shall be operator configurable. The Indication of exclusion from session level monitoring indicates that the service data flow shall be excluded from the PDU Session usage monitoring. The Application Function influence on traffic routing Enforcement Control may contain:

• a set of DNAI(s) (i.e. a reference to the DNAI(s) the SMF needs to consider for UPF selection/reselection), an optional Indication of traffic correlation and, per DNAI, a corresponding Traffic steering policy identifier (i.e. a reference to a pre-configured traffic steering policy at the SMF), and/or a corresponding N6 traffic routing information (when the N6 traffic routing information is provided explicitly as part of the AF request, as described in clause 5.6.7 of TS 23.501), or;
• an AF subscription to UP change events parameter which contains subscription information defined in clause 5.2.8.3 of TS 23.502 for the change of UP path Event Id i.e. an Indication of early and/or late notification and information on where to provide the corresponding notifications (Notification Target Address + Notification Correlation ID as specified in clause 4.15.1 of TS 23.502) and optionally an indication of "AF acknowledgment to be expected" to the corresponding notifications as described in clause 5.6.7 of TS 23.501.
• a user plane latency requirements parameter which contains AF requested information on the requirements for user plane latency defined in TS 23.548.
• an indication for Simultaneous Connectivity at Edge Relocation, which includes Keep existing PSA indication to provide guidance to the network on whether to provide simultaneous connectivity over source and target PSA at edge relocation; also, optionally a related Keep existing PSA timer that indicates the minimum time interval to be considered for inactivity for the traffic described before the connectivity over the source PSA may be removed, as defined in TS 23.548.
• an EAS Correlation indication, which indicates selecting a common EAS for a set of UEs identified by Traffic Correlation ID and accessing the application identified by Service data flow template or FQDN(s).
• a Traffic Correlation ID, identifying a set of UEs accessing the application identified by the Service data flow template or FQDN(s). See more in clause 5.6.7 of TS 23.501.
• a Common EAS IP address, IP address of the common EAS accessed by the UEs with the same Traffic Correlation ID, for the application identified by the Service data flow template.
• FQDN(s), FQDN(s) for the application traffic identified by the Service data flow template, and used for influencing EASDF-based DNS query procedure as defined in TS 23.548.
• NEF Information, Notification Endpoint of the NEF responsible of the set of UEs associated with the Traffic correlation ID.

The Traffic Steering Enforcement Control may contain Indication of UE IP address preservation. The SMF takes this indication into account when determining whether to reselect PSA UPF, as specified in clause 5.6.7 of TS 23.501. The Redirect indicates whether the uplink part of the service data flow should be redirected to a controlled address. The Redirect Destination indicates the target redirect address when Redirect is enabled. The UL Maximum Packet Loss Rate indicates the maximum rate for lost packets that can be tolerated in the uplink direction. The DL Maximum Packet Loss Rate indicates the maximum rate for lost packets that can be tolerated in the downlink direction. The Application descriptors provides one or several instances of the OSId and OSAppId combination. It is used by the UE to identify the application traffic for which steering is required based on the Steering Functionality, the Steering Mode, the Steering Mode Indicator and the Threshold Values. The Steering Functionality indicates the method for how traffic matching the SDF template in the UPF or a Traffic descriptor in the UE is sent over the MA PDU Session. The method ATSSS_LL indicates that the traffic matching the SDF template is sent over the MA PDU Session without additional tunnelling, e.g. with IP flow switching. The method MPTCP indicates that the traffic matching the SDF template is sent over the MA PDU Session using MPTCP. The method MPQUIC indicates that traffic matching the SDF template is sent over the MA PDU Session using MPQUIC. The Steering Mode indicates the rule for distributing downlink SDFs in the UPF or uplink traffic in the UE between accesses, together with the associated steering parameters. The PCF may indicate separate values for uplink and downlink directions. The available Steering Modes are defined in TS 23.501. The Steering Mode Indicator indicates that the UE or the UPF or both may change the steering parameters provided in the Steering Mode and may adjust the traffic steering based on their own decisions, as further defined in TS 23.501. When the PCF selects the Load-Balancing Steering Mode for both the uplink and the downlink, and the PCF provides a Steering Mode Indicator for the uplink equal to UE-assistance operation, then the PCF shall provide the same Steering Mode Indicator for the downlink. The Threshold Values indicate the authorized RTT or Packet Loss Rate for a SDF. Depending on the Steering Mode value, the PCF may include, per SDF, one threshold value for RTT or one threshold value for Packet Loss Rate, or both. The PCF may indicate separate values for uplink and downlink directions. The Steering Modes that may use the threshold values and how the UE and UPF enforces them are defined in TS 23.501. The Transport Mode indicates one of the Transport Modes as defined in TS 23.501 that should be applied for transmitting a UDP flow between UE and UPF. The Transport Mode may be included when the MPQUIC functionality is selected as the Steering Functionality. The Charging key for Non-3GPP access indicates the Charging key that shall be used for charging the detected service data flow traffic carried via Non-3GPP access. The other charging related parameters apply for both accesses. The Monitoring key for Non-3GPP access indicates the Monitoring key that shall be used for monitoring the usage of the detected service data flow traffic carried via Non-3GPP access. The QoS Monitoring parameter(s) indicates the QoS Monitoring parameter(s) for which QoS QoS Monitoring can be enabled for a service data flow as defined in clause 5.45 of TS 23.501, e.g. the UL packet delay, DL packet delay or round trip packet delay between the UE and the UPF. The Reporting frequency indicates the frequency for the reporting, such as event triggered, periodic. The following applies:

• If the Reporting frequency indicates "periodic", the reporting period shall also be included in the PCC rule.
• The reporting period shall also be used for reporting measurement failure in any of the Reporting frequency modes "periodic" or "event triggered".
• If the Reporting frequency indicates "event triggered", the reporting period, Reporting threshold(s) and the minimum waiting time shall also be included in the PCC rule. The Reporting threshold(s) indicates the measurement threshold for each of the included QoS Monitoring parameter(s). The minimum waiting time indicates the minimum time interval between subsequent reports.

The Target of reporting indicates the target for the QoS Monitoring reports sent as notifications. It can be either the NEF, the AF or the Local NEF, indicated as Notification Target Address + Notification Correlation ID. The Indication of direct event notification indicates that the QoS Monitoring reports shall be sent by the UPF directly to the NF indicated by the Target of reporting (i.e. to the Local NEF or the AF as described in clause 5.8.2.18 of TS 23.501). The DataCollection_ApplicationIdentifier is provided to assist the SMF when it needs to decide whether this PCC Rule corresponds to an event exposure subscription (see clause 4.15.4.5.1 of TS 23.502). The Alternative QoS Parameter Set(s) define alternative set(s) of QoS parameters for the service data flow. Every set consists of a PER, a PDB, as well as an UL and a DL guaranteed bitrate QoS parameter. For delay-critical service data flow, every Alternative QoS Parameter Set may also include a Maximum Data Burst Volume (MDBV). The content of the TSC Assistance Container is defined in clause 5.27.2 of TS 23.501. The Traffic Parameter Information applies to the UE power saving as specified in clause 5.37.8 of TS 23.501. The following parameters are included:

• Periodicity:
  • indicates the time period between start of two data bursts in UL and/or DL direction.
  • this parameter is only included when PCF receives the periodicity information from AF.

The Traffic Parameter Measurement applies to the UE power saving as specified in clause 5.37.8 of TS 23.501. The following parameters are included:

• Traffic Parameter to be measured:
  • UL and/or DL periodicity. This parameter is only included when PCF does not receive the periodicity information from AF.
  • N6 jitter range associated with DL Periodicity.
• reporting condition can be optionally included to define the condition for the reporting, such as event triggered or periodic, frequency.

The Downlink Data Notification Control applies to the control of subscription to Downlink Data Delivery status event notifications and DDN Failure event notifications as specified in clause 4.15.3 of TS 23.502. The following parameters are included:

• The Notification control for DDD status applies as described in clause 4.15.3.2.8 of TS 23.502 and contains the following parameters:
  • indication that notifications of Downlink Data Delivery status are required; and
  • the requested type of such notifications (notifications about downlink packets being buffered, and/or discarded).
• The Notification Control for DDN Failure applies as described in clause 4.15.3.2.9 of TS 23.502 and contains the following parameters:
  • indication that notifications of DDN Failure are required.

The PDU Set Control Information is needed to support the delivery of PDU Sets for a service data flow. The parameter values for UL and DL may be different (see clause 5.7.7 of TS 23.501). The Protocol Description Information needed to support identifying PDU Set Information for DL/UL packets and/or last packet of a DL Data Burst. The Protocol Descriptions for UL and DL may be different (see clause 5.37.5 of TS 23.501). The Data Burst Handling Information is needed to support detecting last PDU of the Data Burst and marking End of Data Burst Indication on the last packet of the Data Burst (see clause 5.37.8 of TS 23.501).

Policy and Charging Rule operations consist of activation, modification and de-activation of PCC rules. The PCF may activate, modify and deactivate a PCC rule at any time. However, the modification is applicable to dynamic PCC rules only. Activation of a dynamic PCC rule provides the PCC rule information to the SMF. Activation of a predefined PCC rule provides an identifier of the relevant PCC rule to the SMF. Each PCC rule shall be installed for a single QoS Flow only (for further details about predefined PCC rules see below). An active PCC rule means that:

• the service data flow template shall be used for service data flow detection;
• the service data flow template shall be used for mapping of downlink packets to the QoS Flow determined by the QoS Flow binding;
• the service data flow template shall be used for service data flow detection of uplink packets on the PDU Session determined by the QoS Flow binding;
• usage data for the service data flow shall be recorded;
• policies associated with the PCC rule, if any, shall be invoked;
• for service data flow detection with an application detection filter, the start or the stop of the application traffic is reported to the PCF, if applicable and requested by the PCF. In that case, the notification for start may include service data flow filters, (if possible to provide) and the application instance identifier associated with the service data flow filters.
• Either one of the conditions below:
  • a credit has been granted for the service data flow. Applicable when the Charging method is set to "online" and the Service Data Flow handling while requesting credit is set to "blocking"; or
  • a credit has been requested for the service data flow. Applicable when the Charging method is set to "online" and the Service Data Flow handling while requesting credit is set to "non-blocking".

A predefined PCC rule is known at least, within the scope of one PDU Session. A predefined PCC rule is bound to one and only one QoS Flow per PDU Session. For a predefined PCC rule whose service data flow cannot be fully reflected for the uplink direction in terms of traffic mapping information sent to the UE, the SMF may request the UPF to apply the uplink service data flow detection at additional QoS Flows with non-GBR 5QI of the same PDU Session. The deactivation of such a predefined PCC rule ceases its service data flow detection for the whole PDU Session. The PCF may, at any time, deactivate an active PCC rule in the SMF. At QoS Flow termination all active PCC rules on that QoS Flow are deactivated without explicit instructions from the PCF to do so. Policy and charging control rule operations can be also performed in a deferred mode. A PCC rule may have either a single deferred activation time, or a single deferred deactivation time or both. A PCC rule with only a deferred activation time shall be inactive until that time. A PCC rule with only a deferred deactivation time shall be active until that time. When the rule activation time occurs prior to the rule deactivation time, the rule is inactive until the activation and remains active until the deactivation time occurs. When the rule deactivation time occurs prior to the rule activation time, the rule is initially active until the deactivation time, then remains inactive until the activation time, and then becomes active again. An inactive PCC rule, that has not been activated yet, is still considered to be installed, and may be removed by the PCF. When modifying a dynamic PCC rule by setting, modifying or clearing its deferred activation and/or deactivation time or by changing any other attribute of a PCC rule having a deferred activation and/or deactivation time, the PCF shall provide all attributes of that PCC rule, including attributes that have not changed. Deferred activation and deactivation of PCC rules can only be used for PCC rules that belong to the QoS Flow associated with the default QoS rule that allows all UL packets. Deferred modification of PCC rules shall not be applied for changes of the QoS or service data flow filter information of PCC rules.