PCRF Basic Overview

Rishi Shekhar
Vaibhav Chirde
Date:- 27/07/2020
Contents
• Introduction to PCRF
• WHY PCRF
• PCC Rules
• PCRF Architecture
• PCRF Interfaces
• PCRF Components
• Diameter
• Radius
• PCRF Call flows
• Case Scenarios
Introduction
• Policy and Charging Rule Functions- was introduced in September
2007 when standards for the 3GPP Policy Charging Control (PCC)
architecture were published.
• A node which functions in real-time to determine policy rules in a
multimedia network.
• Operates at the network core and accesses subscriber databases and
other specialized functions, such as a charging system, in a centralized
manner.
• Provides ability to efficiently and dynamically route and prioritize
network traffic.
 WHY PCRF..?
Policy Solution

Policy control/management solution enables Network

operators/service providers to scale, control, monetize, and personalize
any data services on any type of networks (it could be on fixed, mobile,
managed Wi-Fi, converged networks etc) in a simple and cost effective
manner
Business/Policy Use cases:-

Monthly upload/download Parental control/filter for

limits specific data contents

Limited data access Application detection

to specific devices based policies

Specific Time of day

Fair usage policies data usage monitoring
and charging

Promotional data Policy

services Solution
Bill Shock prevention
packages/plans

RAT based policies

Throttling data rates/speeds
at various thresholds
Policy to prioritize/authorize
higher QoS for real time Quota Top-up and
application traffic Loyalty programs
PCC Rule:-
The purpose of the PCC rule is to:
• Detect a packet belonging to a service data flow.
• Identify the service the service data flow contributes to.
• Provide applicable charging parameters for a service data flow.
• Provide policy control for a service data flow.
• The service data flow filters within the PCC rule are used for the
selection of downlink IP CAN bearers.
• The service data flow filters within the PCC rule are used for the
enforcement that uplink IP flows are transported in the correct IP CAN
bearer.
PCC Rule structure:-
• Rulename
• Service Identifier
• QoS Parameters
• Service Data Flow Filters
• Precedence
• Charging Key
• Monitoring Key
• Gate Status
• Indication for PS to CS session continuity
• Other charging parameters
• Indication of access network information reporting etc
Types of PCC Rule:-
I. Dynamic PCC Rules:- Dynamically provisioned by the PCRF to the
PCEF via the Gx interface. These may be either predefined or
dynamically generated in the PCRF. Dynamic PCC rules can be
installed, modified and removed at any time.

II. Predefined PCC Rules:- Preconfigured in the PCEF. Predefined PCC

rules can be activated or deactivated by the PCRF at any time.

NOTE: The operator may define a predefined PCC rule, to be activated

by the PCEF. Such a predefined rule is not explicitly known in the PCRF.
Converged Core Architecture
Du Backoffice
OSS/BSS Subscriber
Portal

Billing/
HSS/UDR Provisioning OA&M
Mediation

OTT/CDN
Swx/Ud SOAP SNMP Sftp/CDRs
SOAP/REST

SOAP

SPR/SDM
Rx IMS

Policy/
Policy &
AAA Sy
PCRF
Charging

External
OCS
Gx/Sd OCS
RADIUS/CoA
Gx

Home GW
With AP ONU OLT RADIUS Acct BNG
Fibre Network
DPI
RADIUS/CoA Internet
Mobile
4G
eNodeB PDN-GW

Wi-FI BNG
Hotspot
Wi-Fi
AP Wi-FI
Controller
PCRF Interfaces in LTE
Interfaces
• Gx:- PCRF and PCEF
• Sy:- PCRF and OCS
• Rx:- PCRF and AF
• Sd:- PCRF and TDF
• Sp:- PCRF and SPR
• Radius CoA Interface:- PCRF and Non-3gpp enforcement point
• Radius Interface:- PCRF and external AAA server in Non-3gpp access
Gx:-
• PCRF Server supports the Gx interface as defined in 3GPP Release 7, 8, 9 and 10.
• It is used for provisioning service data flow based on charging rules.
Rx:-
• PCRF Server supports the Rx interface as defined in 3GPP Release 10.
• Used to exchange application level session information & media related information
between the PCRF & Application function/Application Server.
Sy:-
• PCRF Server supports the Sy interface as defined in 3GPP Release 11.
• It is used between PCRF and OCS for sending limits reports.
Sp:-
• Allows the PCRF to request subscription information related to transport level policies
from the SPR as specified in 3GPP TS 23.203 v9.x.
PCRF Components
• Policy Server:- main server engine that processes the policy requests from the
core network elements systems at real-time.

• SPR:- Subscriber Profile Repository is the repository to store all business

assets, technical assets and configuration items used by the PCRF Server,
Central Management Server.

• Policy Management Platform/ Central Management Systems:- A centralized

server node to monitor and manage the PCRF Server and Repository Server.
It’s the core component for PCRF Server to provide the OA&M functions.
PCRF Components
Diameter Protocol
Diameter Nodes:-
Diameter Message Format
Diameter Base Messages:-
• Diameter Connection Management
• Generic Session Operations
• Offline Charging
Diameter Vs Radius
Radius
• AAA Protocol
• Client / Server Model
• Flexible Authentication Mechanism
Gx Connection messages:-
As per RFC 6733/3588 and 3gpp
specs 23.203
• Capabilities Exchange Request
• Capabilities Exchange Answer
Gx Session messages:-
As per RFC 6733/3588 and 3gpp specs 23.203
• Credit-Control Requests/Answers – Initial
• Credit-Control Requests/Answers – Update
• Credit-Control Requests/Answers – Terminate
• Reauthorization Requests/ Answers
Gx session call flow:-
Rx Session call flow:-
• Authorize-Authenticate Requests/Answers
• Abort Session Requests/Answers
• Session Termination Requests/Answers
Sy message flow:-
• Spending Limit Requests/Answers – Initial/Intermediate/Final
• Spending-Status Notification Requests/Answers
• Session Termination Requests/Answers

Gy message flow will be similar to Gx as mentioned above.

PCC – Call Authorization and Setup
(2/2)
1. UE requests connectivity to the PDN (Internet/Intranet) via access gateways
(SGSN/MME).
2. The PCEF (GGSN/PGW) processes the request allocates the necessary network
resources and forwards the request towards the PCRF for specific information on the
rules to be applied for this subscriber session.
3. The PCRF replies with a set of rules such as QoS and DPI rule names to be applied
specific to this subscriber session also called “policy”. It also requests the PCRF to
initiate an update when certain events occur, all called “Event Triggers”
4. The PCEF then enforces the policy that it received from the PCRF along the value
chain.
5. Any subscriber data passing through the mobile network will now undergo a packet
or flow inspection followed by the application of policy specific to application or
filters as instructed by the PCRF.
References
• 3GPP TS 23.203 – Policy and Charging Architecture:
http://www.etsi.org/deliver/etsi_ts/123200_123299/123203/10.10.00_60/
• 3GPP TS 29.212 – Policy and Charging Control (PCC); Reference Points:
http://www.etsi.org/deliver/etsi_ts/129200_129299/129212/10.16.00_60/
• 3GPP TS 29.213 – Policy and Charging control signaling flows and Quality of Service
(QoS) parameter mapping:
http://www.etsi.org/deliver/etsi_ts/129200_129299/129213/10.12.01_60/
• 3GPP TS 29.214 – Policy and Charging Control over Rx reference point:
http://www.etsi.org/deliver/etsi_ts/129200_129299/129214/11.06.00_60/
• Diameter RFC- 6733/3588
• https://diameter-protocol.blogspot.com/2011/05/diameter-message-structure-and-mes
sage.html
• https://en.wikipedia.org/wiki/Diameter_Credit-Control_Application