name: PCC
full_form: Policy and Charging Control
context: The Evolved Packet System applies the PCC framework as defined in TS 23.203[ Policy and charging control architecture ]  [6] for QoS policy and charging control. PCC functionality is present in the AF, PCEF and PCRF. An EPS needs to both PCEF and PCRF functionality to enable dynamic policy and charging control by means of installation of PCC rules based on user and service dimensions. However, an EPS may only PCEF functionality in which case it shall static policy and charging control. NOTE: The local configuration of PCEF static policy and charging control functionality is not subject to standardization. The PCEF static policy and control functionality is not based on subscription information. The following applies to the use of dynamic policy and charging control in EPS: - The service level (per SDF) QoS parameters are conveyed in PCC rules (one PCC rule per SDF) over the Gx reference point. The service level QoS parameters consist of a QoS Class Identifier (QCI) Allocation and Retention Priority (ARP) and authorised Guaranteed and Maximum Bit Rate values for uplink and downlink. The QCI is a scalar that represents the QoS characteristics that the EPS is expected to provide for the SDF. ARP is an indicator of the priority for the SDF that is used to decide about the assignment of resources due to resource limitations. The service level ARP assigned by PCRF in a PCC rule may be different from the bearer level ARP stored in subscription data; - The set of standardized QCIs and their characteristics that the PCRF in an EPS can select from is provided in TS 23.203[ Policy and charging control architecture ]  [6]. It is expected that the PCRF selects a QCI in such a way that the IP-CAN receiving it can support it; - It is not required that an IP-CAN supports all standardized QCIs; - In the case of IP address configuration subsequent to initial attachment, i.e. through DHCP mechanism to complete the IP address configuration, the PDN GW/PCEF shall notify the PCRF of the UE's IP address by means of an IP-CAN Session Modification procedure or IP-CAN Session Establishment procedure as defined in TS 23.203[ Policy and charging control architecture ]  [6] when it is assigned. If the PCRF response leads to an EPS bearer modification the PDN GW should initiate a bearer update procedure; - For local breakout, the visited network has the capability to reject the QoS authorized by the home network based on operator policies. The following applies regardless of whether dynamic or static policy and charging control is used in EPS: - For E-UTRAN the value of the ARP of an EPS bearer is identical to the value of the ARP of the SDF(s) mapped to that EPS bearer; - For the same UE/PDN connection: SDFs associated with different QCIs or with the same service-level QCI but different ARP shall not be mapped to the same EPS bearer; - The bearer level QCI of an EPS bearer is identical to the value of the QCI of the SDF(s) mapped to that EPS bearer.
description: The Policy and Charging Control (PCC) framework, as defined in TS 23.203, is a crucial component within the Evolved Packet System (EPS). It enables dynamic policy and charging control by installing PCC rules based on user and service dimensions. The PCC functionality is present in the Application Function (AF), Policy and Charging Enforcement Function (PCEF), and Policy and Charging Rules Function (PCRF). This framework allows for efficient management of Quality of Service (QoS) policies and charging mechanisms, ensuring that the network provides the expected QoS characteristics for different services. The PCC rules convey service-level QoS parameters, including QoS Class Identifier (QCI), Allocation and Retention Priority (ARP), and authorized Guaranteed and Maximum Bit Rate values for uplink and downlink.
explanation: PCC is classified as a Network Function because it plays a vital role in controlling policy and charging within the EPS. It interacts with other network functions, such as AF, PCEF, and PCRF, to manage QoS policies and charging mechanisms, aligning with the 3GPP's specifications for efficient network operations.
section_title: 4.7.5 Application of PCC in the Evolved Packet System
biotag_Context: O,B-Network,I-Network,I-Network,O,O,B-Miscellaneous,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,B-Network,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,B-Miscellaneous,O,O,B-Miscellaneous,O,O,O,O,O,B-Interface,O,O,O,O,O,B-Measurement,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Measurement,O,O,O,B-Network,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Network Function,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Parameter,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,B-Network,O,O,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O,O,B-Network,O,O,O,O,B-Network,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Parameter,O,O,B-Network,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Parameter,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,B-Parameter,O,O,B-Network,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Network,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,B-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,B-Network Function,I-Network Function,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,B-Measurement,I-Measurement,I-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,B-Miscellaneous,O,O,O,B-Measurement,O,O,B-Parameter,I-Parameter,I-Parameter,O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O