The present specification adds detailed flows of Policy and Charging Control (PCC) over the Diameter-based Rx, Gx, Gxx, Sd, Sy, S9, Nt, Diameter-based St and Np reference points and their relationship with the bearer level signalling flows over the Gn/Gp, S4, S5/S8, S2a and S2c interfaces.
The calls flows depicted in this Technical Specification represent usual cases, i.e. not all situations are covered. Detailed information provided in TS 29.212, TS 29.214, TS 29.215, TS 29.217 , TS 29.154 and TS 29.219 shall be taken into consideration.
The present specification also describes the PCC reference architectures for non-roaming and roaming scenarios.
The present specification also describes the binding and the mapping of QoS parameters among SDP, UMTS QoS parameters, and QoS authorization parameters.
The present specification also describes the PCRF addressing using DRA.
The present specification also describes Diameter race condition handling for Gx based applications, i.e Gx, Gxx, Sd and S9.
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
References are either specific (identified by date of publication and/or edition number or version number) or non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply:
The PCRF routing information stored per UE or per PDN in the DRA, which include the user identity (UE NAI), the UE Ipv4 address and/or Ipv6 prefix, the APN (if available) and the selected PCRF identity for a certain IP-CAN Session.
Gateway Control Session:
An association between a BBERF and a PCRF (when GTP is not used in the EPC), used for transferring access specific parameters, BBERF events and QoS rules between the PCRF and BBERF. In the context of this specification this is implemented by use of the Gxx procedures.
association between a UE and an IP network. The association is identified by one or more UE Ipv4 addresses/ and/or Ipv6 prefix together with a UE identity information, if available, and a PDN represented by a PDN ID (e.g. an APN). An IP-CAN session incorporates one or more IP-CAN bearers. Support for multiple IP-CAN bearers per IP-CAN session is IP-CAN specific. An IP-CAN session exists as long as the related UE Ipv4 address and/or Ipv6 prefix are assigned and announced to the IP network.
A mechanism within the OCS to track spending applicable 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 OCS to PCRF. Specific labels are configured jointly in OCS and PCRF.
RAN user plane congestion:
RAN user plane congestion occurs when the demand for RAN resources exceeds the available RAN capacity to deliver the user data for a prolonged period of time.
Restricted local operator services:
communication services provided by an operator that involve either automated or human assistance (e.g. credit card billing, directory assistance, customer care) for which successful authentication is not necessary.
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 OCS to the PCRF via the Sy reference point.
An association between an IP-CAN session and the assigned TDF for the purpose of application detection and control by the PCRF . The association is identified by one UE Ipv4 address and/or Ipv6 prefix together with optionally a PDN represented by a PDN ID and a set of ADC rules to be applied by the TDF.