For the purposes of the present document, the terms and definitions given in TR 21.905
, TS 23.501
, TS 23.502
and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905
Application detection filter:
A logic used to detect packets generated by an application based on extended inspection of these packets, e.g. header and/or payload information, as well as dynamics of packet flows. The logic is entirely internal to a UPF, and is out of scope of this specification.
An identifier referring to a specific application detection filter.
Application service provider:
A business entity responsible for the application that is being / will be used by a UE, which may be either an AF operator or has an association with the AF operator.
The maximum QoS that is authorised for a service data flow. In the case of an aggregation of multiple service data flows within one QoS Flow, the combination of the "Authorised QoS" information of the individual service data flows is the "Authorised QoS" for the QoS Flow. It contains the 5QI and the data rate.
The association between a service data flow and the QoS Flow transporting that service data flow.
The method for creating, modifying and deleting bindings.
The process of associating packets, belonging to a service data flow, to a charging key and applying online charging and/or offline charging, as appropriate.
Information used by the CHF for rating purposes.
Detected application traffic:
An aggregate set of packet flows that are generated by a given application and detected by an application detection filter.
Dynamic PCC Rule:
a PCC rule, for which the definition is provided to the SMF by the PCF.
The process of blocking or allowing packets, belonging to a service data flow / detected application's traffic, to pass through to the UPF.
information used by the SMF and PCF for usage monitoring control purposes as a reference to a given set of service data flows or application (s), that all share a common allowed usage on a per UE and DNN basis.
A multi-modal service is a communication service that consists of several data flows that relate to each other and are subject to application coordination. The data flows can transfer different types of data (for example audio, video, positioning, haptic data) and may come from different sources (e.g. a single UE, a single device or multiple devices connected to the single UE, or multiple UEs).
Non-3GPP access network selection information:
It consists of ePDG identifier configuration, N3IWF identification and non-3GPP access node selection information, as defined in clause 220.127.116.11 in TS 23.501
A capability of the UE to access the data networks via non-3GPP access (e.g. WLAN radio access) outside of a PDU Session.
A service for which complete PCC rule information, including service data flow filter information, is available in the PCF through configuration and/or dynamic interaction with an AF.
Operating System (OS):
Collection of UE software that provides common services for applications.
Operating System Identifier (OSId):
An identifier identifying the operating system.
OS specific Application Identifier (OSAppId):
An identifier associated with a given application and uniquely identifying the application within the UE for a given operating system.
A specific user data flow from and/or to the UE.
Packet Flow Description (PFD):
A set of information enabling the detection of application traffic provided by a 3rd party service provider.
A PCF decision for policy and charging control provided to the SMF (consisting of PCC rules and PDU Session related attributes), a PCF decision for access and mobility related policy control provided to the AMF, a PCF decision for UE policy information provided to the UE or a PCF decision for service related policy (e.g. background data transfer policy) provided to the AF.
A set of information enabling the detection of a service data flow and providing parameters for policy control and/or charging control and/or other control or support information. The possible information is described in clause 6.3.1
The process whereby the PCF indicates to the SMF how to control the QoS Flow. Policy control includes QoS control and/or gating control.
Policy Control Request trigger report:
a notification, possibly containing additional information, of an event which occurs that corresponds with a Policy Control Request trigger.
Policy Control Request trigger:
defines a condition when the SMF shall interact again with the PCF.
A mechanism within the CHF to track spending applicable to a subscriber.
Policy counter identifier:
A reference to a policy counter in the CHF for a subscriber.
Policy counter status:
A label whose values are not standardized and that is associated with a policy counter's value relative to the spending limit(s) (the number of possible policy counter status values for a policy counter is one greater than the number of thresholds associated with that policy counter, i.e. policy counter status values describe the status around the thresholds). This is used to convey information relating to subscriber spending from CHF to PCF. Specific labels are configured jointly in CHF and PCF.
A Policy Section is identified by a Policy Section Identifier and consists of one or multiple URSP rule(s) or one or multiple WLANSP rule(s) or non-3GPP access network selection information or a combination of WLANSP rule(s) and non-3GPP access network selection information.
Predefined PCC Rule:
a PCC rule that has been provisioned directly into the SMF by the operator.
Redirect the detected service traffic to an application server (e.g. redirect to a top-up / service provisioning page).
Service data flow:
An aggregate set of packet flows carried through the UPF that matches a service data flow template.
Service data flow filter:
Service data flow filter identifier:
A set of packet flow header parameter values/ranges used to identify one or more of the packet flows in the UPF. The possible service data flow filters are defined in clause 18.104.22.168
A scalar that is unique for a specific service data flow (SDF) filter within a PDU Session.
Service data flow template:
The set of service data flow filters in a PCC Rule or an application identifier in a PCC rule referring to an application detection filter in the SMF or in the UPF, required for defining a service data flow.
Session based service:
An identifier for a service. The service identifier provides the most detailed identification, specified for flow based charging, of a service data flow. A concrete instance of a service may be identified if additional AF information is available (further details to be found in clause 6.3.1
An end user service requiring application level signalling, which is separated from service rendering.
A spending limit is the usage limit of a policy counter (e.g. monetary, volume, duration) that a subscriber is allowed to consume.
Spending limit report:
a notification, containing the current policy counter status generated from the CHF to the PCF.
Subscribed guaranteed bandwidth QoS:
The per subscriber, authorized cumulative guaranteed bandwidth QoS which is provided by the UDR to the PCF.
is a means to group the subscribers into different classes, e.g. gold user, silver user and bronze user.
UE Local Configuration:
Information about the association of an application to either a PDU Session or to non-seamless Offload is configured in the Mobile Termination (MT) and in the Terminal Equipment (TE). For example, UE Local Configuration can include operator specific configuration (e.g. operator provided S-NSSAI(s)), or application specific parameters to set up a PDU Session or end user configuration for specific applications.
UE policy information:
Policy information preconfigured in the UE and/or provisioned to the UE for access selection (i.e. ANDSP), PDU Session selection (i.e. URSP), V2X communications (i.e. V2XP), ProSe operations (i.e. ProSeP) and/or A2X communications (i.e. A2XP).
Uplink binding verification:
The network enforcement of terminal compliance with the negotiated uplink traffic mapping to QoS Flows.
User Preferences On Non-3GPP Access Selection:
The list of configuration parameters provided by a layer (e.g. application) above NAS and used by the UE for access network discovery and selection.
VPLMN specific URSP Rules:
A VPLMN specific URSP Rule is applicable when the UE is registered in that VPLMN or its equivalent PLMNs. A VPLMN specific URSP Rule may be used to route traffic to the VPLMN, if the V-PCF provides a local DNN to the AMF, using the PCRT on SMF selection management. A VPLMN specific URSP Rule may be used to route traffic to the Home PLMN if the HPLMN operator wants to provide a different list of RSDs for the same Traffic Descriptor for a VPLMN and for the HPLMN. When provided, the Time and Location criteria in the RSD(s) contain values that are based on agreements with the VPLMN or service parameters that were received from the VPLMN.
For the purposes of the present document, the abbreviations given in TR 21.905
, TS 23.501
, TS 23.502
, TS 23.316
and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905
5G Direct Discovery Name Management Function
Aggregated Maximum Bitrate
Access Network Discovery & Selection Policy
Allocation and Retention Priority
Application Service Provider
Background Data Transfer
Binding Support Function
Data Collection Coordination Function
A PCF in the HPLMN
A UDR in the HPLMN
Multimedia Priority Service
Network-based IP flow mobility
Non-Seamless WLAN Offload
Network Data Analytics Function
Operation Administration and Maintenance
Online Charging System
Policy and Charging Control
Planned Data Transfer with QoS
ProSe Discovery UE ID
Packet Delay Variation
Packet Flow Description
Packet Flow Description Function
Presence Reporting Area
Proximity based Services
Radio Access Network
Stand-alone Non-Public Network
UE Route Selection Policy
A PCF in the VPLMN
A UDR in the VPLMN
video Single Radio Voice Call Continuity
WLAN Selection Policy