

The PCEF provides a control over the user plane traffic handling at the Access Gateway and its QoS, and provides service data flow detection and counting as well as online and offline charging interactions. For a service data which is controlled by the PCC rules the PCEF allows the data flow to pass through the Access Gateway only if the corresponding gate is open. GGSN in the GPRS case, PGW in the ePC case). This functional entity is located at the Access Gateway (e.g. The PCRF also provides a feedback about user plane events to the P-CSCF (AF) – for example in case of a bearer loss. maximum bandwidth or QoS class) and charging rules that sends to the PCEF functionality via the Gx reference point. Based on the data received over the Rx interface from P-CSCF and operator defined policy rules, the PCRF forms authorized QoS data (e.g. The PCRF povides Policy Control decisions which are enforced by PCEF, and flow based charging control functionalities. This ensures that the PCRF gets the proper information in order to perform reliable PCC. session termination, modification) can trigger a new request sent towards the PCRF. The information is taken from SIP/SDP session setup and it is forwarded to the PCRF via the Rx reference point. Each new SIP message that includes an SDP payload or session events (e.g. The P-CSCF provides the information related to the control plane signaling. In VoLTE is the AF incorporated within the Proxy-CSCF. Policy and Charging Control (PCC) Architecture Application Function

Policy Charging and Rules Function (PCRF).The ETSI TS 29.212, 29.213, 29.214 and 29.203 define Policy and Charging Control Architecture. PCC functionality comprises of Policy Control (e.g. In order to achieve these requirements we use two techniques in the VoLTE architecture:

And, of course, we want to accordingly charge the users. We want to control when the media starts and stops, we want to be sure about media routing, we want to ensure Quality of Service (QoS).
#Diff serv sip definition full
However a full independence of control and user plane is not desirable. In the IMS we have separated signalling and media data. But no worries, there will be abbreviations starting on other letters as well 🙂 Today we should be very careful as many of them start on ‘P’ – PCC, PCRF, PCEF, P-CSCF, PGW, PDN, PDG, PDB, PHB. My wife always loughs and tries to mimic me when she listens to my calls. In IT and particularly in Telco we are obsessed with abbreviations.
