Deeksha Tech Group: Policy and Charging Control
Deeksha Tech Group: Policy and Charging Control
Module 13
2.GW(PCEF) receives request for IP-CAN Bearer establishment and assigns IP address for UE
3.PCEF determines that the PCC authorization is required, requests the authorization of allowed service(s) and PCC Rules
information. The PCEF may also include e charging ID information.
4.If the PCRF does not have the subscriber's subscription related information, it sends a request to The SPR in order to receive the
information related to the IP-CAN session.
5.PCRF stores the subscription related information containing the information about the allowed service(s) and PCC Rules
information.
7.PCRF sends the decision(s), including the chosen IP-CAN bearer establishment mode, to the PCEF which enforces the decision.
8.If online charging is applicable, and at least one PCC rule was activated, the PCEF activates the Online charging session,
providing relevant input information for the OCS decision.
9.The OCS provides the possible credit information to the PCEF and may provide re-authorisation Triggers for each of the credits.
10.If at least one PCC rule was successfully activated and credit was not denied by the OCS, The GW(PCEF) acknowledges the IP-
CAN Bearer Establishment Request.
12.If the PCRF in step7 requested an acknowledgement based on PCC rule operations ,the GW(PCEF) sends the IP-CAN Session
Establishment Acknowledgement to the PCRF in order to Inform the PCRF of the activated PCC rules result.
PCC Procedures over Gx Interface
• Push-Pull Request between PCRF & PCEF on Gx Interface
PCC Procedures over Gx Interface
There are 2 procedures through which the PCRF can communicate PCC rules to PCEF over Gx interface. They
are -
• Pull Procedure: In this procedure the PCEF request for PCC rules from PCRF in following instances.
– At IP-CAN Session Establishment - The PCEF sends a Credit Check Request (CCR) message with CCR-
Type value set to "Initial_Request" . It also includes user subscription and IP-CAN session related
information to allow the PCRF to identify the rules to be applied. The PCRF validates the request
message and responds with a Credit Check Answer (CCA) message. If the PCRF rejects the request, it
includes the Error cause in the CCA message.
– At IP-CAN Session Modification - This can occur when an IP-CAN bearer is being
established/modified/terminated, or UE requests network resources to be modified, or an event
triggers. The PCEF sends a Credit Check Request (CCR) message with CCR-Type value set to
"Update_Request". The PCEF also includes the Event Trigger (could be UE requested) that caused the
IP-CAN bearer modification, any previously provisioned PCC rules that needs to be modified and
charging information. The PCRF validates the request message and responds with a Credit Check
Answer (CCA) message.
• Push Procedure: In this procedure, the PCRF may decide to provision PCC rules without obtaining any
request from the PCEF. This could be in response to information provided by AF over Rx interface, or
internal trigger within the PCRF. The PCRF sends these PCC rules in Re-Auth Request (RAR) message. The
RAR message also includes the Event Trigger and Event Report indications for the session. The PCEF
sends Re-Auth Answer (RAA) message in response to the RAR message.
PCC Rules
PCC Rules and its Purposes
• to detect a packet belonging to an SDF to map that packet to proper IP-CAN bearer in
downlink and uplink direction
• to identify the service
• to provide appropriate applicable charging
• to provide policy control
S-GW External
GW
P-GW Internet
(PCEF)
eNodeB
LTE CPE
HGW Wi-fi
HOME
LOCAL ROUTED
“Thank you”