Beruflich Dokumente
Kultur Dokumente
Product Description
Product version: 3.6
Document version: 2.9
Status: development
Yota 2013
Revision History
Date
09.03.2011
Version
1.0
Author
Evgenia Martynyuk
01.06.2011
1.1
Evgenia Martynyuk
06.06.2011
28.07.2011
17.08.2011
29.08.2011
17.10.2011
1.1
1.2
1.2
1.3
2.1
Evgenia
Evgenia
Evgenia
Evgenia
Evgenia
19.01.2012
2.2
Evgenia Martynyuk
04.03.2012
2.3
Evgenia Martynyuk
13.07.2012
2.4
Evgenia Martynyuk
21.08.2012
2.5
Evgenia Martynyuk
29.10.2012
2.6
Evgenia Martynyuk
31.01.2013
2.7
Evgenia Martynyuk
02.04.2013
2.8
Evgenia Martynyuk
10.09.2013
2.9
Evgenia Martynyuk
Yota 2013
Martynyuk
Martynyuk
Martynyuk
Martynyuk
Martynyuk
Revision
Document created
Integration with 3G CDMA2000 was added.
Figures review and update
Geographical distribution was added
Yota PCRF architecture update
Integration with LTE network figure was changed
Functional and Redundancy figures were changed
Supported product version changed to 2.5
Supported product version changed to 3.0,
"Yota PCRF Architecture" and "Feature
Description" chapters update
Supported product version changed to 3.1,
"Yota PCRF Architecture" and "Network
Integration" chapters updated
Supported product version changed to 3.2,
"Yota PCRF Architecture" chapter updated
Supported product version changed to 3.3
Supported product version changed to 3.4. "Yota
PCRF Architecture" chapter updated
Supported product version changed to 3.5.1.
"Yota PCRF Architecture" and "Integration"
chapters updated
Supported product version changed to 3.5.2.
Supported product version changed to 3.6. "Yota
PCRF Architecture" chapter updated
Table of Contents
About the document .................................................................................................. 5
Formatting conventions .......................................................................................... 5
Abbreviations ........................................................................................................ 5
Introduction .............................................................................................................. 8
Yota PCRF Architecture .............................................................................................. 9
Yota PCRF System Functional Components ..................................................................10
Geographical Distribution ..........................................................................................10
DDF as Temporary Subscriber Profile Storage ..........................................................11
DDF as Permanent Subscriber Profile Storage ..........................................................11
PCRF Node Components ............................................................................................11
PCRF Core ...........................................................................................................12
PCRF Database .....................................................................................................12
Diameter Interfaces ..............................................................................................12
HTTP Interfaces ....................................................................................................13
Administration Tools .............................................................................................15
EDR Writer ..........................................................................................................16
BackUp ...............................................................................................................16
Service Components .............................................................................................17
Monitoring ...........................................................................................................17
DDF Node Components .............................................................................................18
Data Distribution Function (DDF) ............................................................................19
Propagator ...........................................................................................................19
PCRF Database .....................................................................................................19
Diameter Interfaces ..............................................................................................19
HTTP Interfaces ....................................................................................................20
MiniCRM ..............................................................................................................21
Administration Tools .............................................................................................21
Service Components .............................................................................................21
BackUp ...............................................................................................................22
Monitoring and Statics ...........................................................................................22
PCRF Cluster Architecture ..........................................................................................23
Integration ............................................................................................................... 24
Network Integration ..................................................................................................25
LTE .....................................................................................................................25
WiMAX ................................................................................................................25
3G UTMS .............................................................................................................26
Yota 2013
Yota 2013
Formatting conventions
The following conventions are used in the document:
Item
Convention
Document titles
Command on menus
and buttons
System components
General emphasis
Italic
Chapter titles
Example
See "Yota PCRF 3.4 Periodic Tasks
Description"
See Chapter 2, "PCRF System Processes"
Click Add button
PCRF Core
Reference to another chapter of the same
document is made as a cross reference in
the following format
Abbreviations
Abbreviation
Meaning
3GPP
AAA
AF
Application Function
ASN-GW
BS
Base Station
BSC
CLI
CRM
CSP
DDF
DPI
eGGSN
enhanced GGSN
eNB
E-UTRAN NodeB
Yota 2013
GGSN
GPRS
HLR
HSS
IMS
IP Multimedia Subsystem
IMSI
LTE
MME
MS
Mobile Station
O&M
OSS/BSS
(B/OSS)
P2P
Peer to Peer
PC
Personal Computer
PCC
PCEF
PCRF
P-CSCF
PDN-GW (PGW)
PDSN/HA
PLM
QoS
Quality of Service
SCTP
SGSN
Yota 2013
Serving Gateway
SMS
SOAP
SPR
TCP
USSD
UMTS
Yota 2013
Introduction
In the era of packet communication technologies and rapidly growing demand for bandwidth
and data transfer volumes intelligent control over quality of services (QoS) provided to
subscribers plays a major role.
In telecommunication networks dynamic control over QoS policies is performed by PCRF (Policy
and Charging Rules Function), which is supplied with SPR (Subscriber Profile Repository).
Yota PCRF is a standard compliant policy management solution that enables operator to
dynamically control network elements with real-time policies based on service, subscriber or
usage context.
Yota PCRF allows making policy decisions based on:
Cell congestion
Yota PCRF gives operators the flexibility to quickly respond to competitor tactics, new devices,
applications and changing consumer data habits.
Yota PCRF gives service providers valuable abilities like:
At the same time Yota PCRF provides subscribers with the following benefits:
True personalization
Yota 2013
1
Yota PCRF Architecture
Yota PCRF System Functional Components
Geographical Distribution
PCRF Node Components
DDF Node Components
Cluster Architecture
Yota 2013
PCRF. This element carries all policy selection logic and also incorporates SPR functionality.
The system can have one DDF cluster and several PCRF clusters (standalone nodes). Every
cluster consists of two physical identical servers.
Geographical Distribution
Yota PCRF supports installation in multiple regions. The component that provides geographical
distribution is DDF (Data Distribution Function).
DDF carries out a single entry point for BSS. BSS sends commands only to DDF. DDF then
forwards these commands to Yota PCRF clusters.
The scheme of geographically-distributed configuration is shown in the figure below:
Figure 1. Geographical distribution
BSS
HTTP
DDF
HTTP,
Diameter (I0,I1)
PCRF
DB
HTTP,
Diameter (I0,I1)
HTTP,
Diameter (I0,I1)
PCRF
PCRF
SPR
PCRF
DB
PCEF
PCEF
City A
PCRF
SPR
PCRF
DB
PCEF
PCEF
City B
SPR
PCRF
DB
PCEF
PCEF
City C
Yota 2013
10
CRM
DDF
I0, I1 (Diameter)
DDF O&M
Console
Administrator
PCRF O&M
Console
CLI
Monitoring
Center
HTTP
MiniCRM
Subscriber
Session Info
Interface
GRAPI
Administration Tools
SPR
Configuration
Interface
Subscriber
Management
Interface
SNMP,
HTTP
Monitoring
HTTP Interfaces
In-memory DB
System
Logging
BackUp
PCRF
DB
PCRF Core
Service
Components
EDR
Writer
Policy Engine
PCRF
Node
Gx
Gxx
Cluster
watchdog
Diameter Interfaces
Rx
S9
I0, I1
Secondary
PCRF Node
PCEF
Yota 2013
BBERF
AF
Visited
PCRF
11
PCRF Core
Diameter Interfaces (for interaction with network core equipment and DDF)
Administration Tools
PCRF Core
PCRF Core contains Policy Engine, which implements the logic of policy decision for subscriber
access, based on different criteria. The input is SPR information (subscription information,
subscriber location), session information, accumulated usage, used quota or roaming
conditions. The output is the chosen policy, which defines access of a subscriber to network
resources and levels of QoS.
Policy Engine has embedded script processor which is based on Lua scripting language. Script
processor can operate with PCRF functions and attributes, and build any combination of
attributes and conditions for policy decision. This enables virtually unlimited flexibility in
configuration of rules in PCRF.
PCRF Database
In-memory PCRF database contains:
SPR information
Session information
SPR Information
This is information about:
Subscribers (such as subscriber identity, his profile). These subscribers are attached to the
Network in the region that is served by a local PCRF cluster
Session Information
This service information contains network session context and information of all Diameter
interfaces: Gx, Rx, S9, etc
Diameter Interfaces
Diameter interfaces allows PCRF node to communicate with PCEF, AF, secondary cluster node
and DDF. Yota PCRF supports Diameter message transfer over TCP or SCTP transport protocol.
Several DPIs and/or PCEFs (e.g., PDN-GW, GGSN) can be connected to PCRF in cluster or
standalone mode.
The following Diameter Gx dialects are supported:
Vendor-specific dialects
Yota 2013
12
Huawei
Cisco
Procera
Samsung
Sandvine
PCRF clusters communicate with DDF cluster via I0 and I1 interfaces which are based on
Diameter. I0 is used for subscriber profiles migration between clusters and I1 is used for
subscriber session start reporting to DDF or PCEF.
Information
For more information about Diameter interfaces, please refer to the "Yota PCRF 3.6
Diameter Interfaces".
HTTP Interfaces
The following HTTP interfaces are available for external systems:
Yota 2013
13
Information
For more information about the interface, please refer to the "Yota PCRF 3.6 Subscriber
Management Interface".
Service dictionary. Contains information about all services that can be assigned to a
subscriber.
Threshold Scheme dictionary. Contains information about all threshold schemes that are
used in Yota PCRF.
Accumulator dictionary. Contains information about all accumulators that are used in
Yota PCRF.
Attribute dictionary. Contains information about all supplementary attributes that can be
added to a specified service or subscriber.
Information
For more information about the interface, please refer to "Yota PCRF 3.6 SPR Configuration
Interface".
Yota 2013
14
Information
For more information about the interface, please refer to "Yota PCRF 3.6 Subscriber Session
Information Interface".
services
session information
GRAPI involves launching a custom Lua script, which contains processing logic, to a PCRF node
by HTTP request.
Information
For more information about the interface, please refer to "Yota PCRF 3.6 Generic Request
API".
Administration Tools
PCRF O&M Console
PCRF O&M Console is one of the main administration tools. It allows configuring, maintaining,
monitoring of the Yota PCRF system.
This Web Interface:
allows process and session browsing, which occur in the system, connections generating,
dynamic routes creating, and other operations.
CLI
This component is optional and is used for performing simple administration tasks like adding,
updating, or deleting subscriber profile or service information.
Yota 2013
15
Information
For more information about the utility, please refer to "Yota PCRF 3.6 Mass Operation Utility
Description".
EDR Writer
EDR Writer (Event Data Records Writer) generates files with information about all events that
lead to a QoS policy or rules set change. EDR files contain all policy change history for each
subscriber that makes subscriber support easier. This information can be loaded into external
BI systems for further analysis.
EDR file includes:
Subscriber information
Session information
Information
For more information about EDR files, please refer to "Yota PCRF 3.6 EDR Generation".
BackUp
This component is optional and performs full backup of the information (such as subscriber
profiles, session information, configuration files, server settings, etc.), which is stored in PCRF
database. Full backup of the database is performed every 3 hours.
Information
For more information about backup and restore procedures, please refer to "Yota PCRF 3.6
Backup and Recovery".
Yota 2013
16
Service Components
Service components provide stable system operating and high performance, manage active
processes in the system (if a process is down or doesnt respond it will be restarted), root out
session doubles and terminate them, collect required information required for RRD charts, etc
Monitoring
This component is optional and serves for monitoring of system status, including subcomponents, load level and performance.
Yota 2013
17
BSS
CRM
Administrator
Monitoring
Center
HTTP
HTTP
MiniCRM
Subscriber
Session Info
Interface
GRAPI
HTTP
Subscriber
Management
Interface
SPR
Configuration
Interface
DDF Info
Interface
Interfaces
DDF O&M
Console
CLI
Statistics
Monitoring
Administration Tools
Proxy
In-memory DB
BackUp
PCRF
DB
System
Logging
Service
Components
Propagator
DDF
HTTP
HTTP
I0, I1
PCRF
Clusters
Cluster
watchdog
Diameter Interfaces
DDF
Node
Secondary DDF
Node
Propagator
PCRF Database
Diameter Interfaces
HTTP Interfaces
MiniCRM
Administration Tools
Yota 2013
18
Propagator
This component propagates SPR configuration commands to regional PCRF clusters.
PCRF Database
DDF database has the same structure as PCRF database on a PCRF node and contains:
SPR information
Session information
Temporary Storage
In case of temporary storage subscriber profiles are stored on DDF only when:
DDF performs a subscriber profile migration from one regional PCRF to another.
The complete transaction is divided into two parts. At first, DDF requests profile from an
old PCRF cluster database and stores it in own database. Then DDF sends profile to a new
PCRF cluster database and removes it from PCRF database on DDF.
BSS sends a command to create new subscriber, to whom DDF doesnt have routing
information yet.
In this case DDF creates a profile in its own PCRF database. The subscriber profile
information will be migrated to a home PCRF cluster right after the first attach to the
network of this subscriber.
Permanent Storage
In case of permanent storage all subscriber profiles are stored on DDF. Local PCRF gets
subscriber profile and stores it while this subscriber session exists on PCRF.
Diameter Interfaces
DDF communicate with PCRF clusters via I0 and I1 interfaces which are based on Diameter.
I0 is used for subscriber profiles migration between clusters and I1 is used for subscriber
session start reporting.
Yota 2013
19
HTTP Interfaces
The following interfaces are available for external systems on DDF node:
Important
If DDF is configured as single profile storage, Subscriber Management Interface commands
are not propagated to PCRF clusters. All changes a will be applied to subscriber profiles that
are stored on DDF cluster only.
Yota 2013
20
MiniCRM
MiniCRM is a centralized interface, which is used to obtain subscriber profiles and session
information by subscriber ID or session IP.
The following information is available via miniCRM:
Subscriber location
Session information (session ID, base station ID, QoS policy, region, etc.)
Administration Tools
To provide full Operations & Maintenance function Yota PCRF system has the following main
administration tools:
CLI
CLI on DDF node is optional and has the same functions as PCRF node CLI.
Service Components
Service components provide stable system operating and high performance, manage active
processes in the system (if a process is down or doesnt respond it will be restarted), collect
required information required for RRD charts, etc
Yota 2013
21
BackUp
This component is optional and performs backup of DDF databases information (subscriber
profiles, session information, server settings, etc.). Full backup is performed every 3 hours.
Information
For more information about backup and restore procedures, please refer to "Yota PCRF 3.6
Backup and Recovery".
Yota 2013
22
Master link
DDF
DDF
Slave link
HTTP
HTTP
PCRF Cluster
HTTP
Interfaces
HTTP
Interfaces
Secondary
Node
Primary
Node
DB replication
PCRF
DB
PCRF
DB
Policy Engine
Policy Engine
Cluster
watchdog
Diameter
Interfaces
Gx
Gx
Diameter
Interfaces
Gx
PCEF
Gx
PCEF
PCEF Cluster
23
2
Integration
Network Integration
Integration with IT Infrastructure
Yota 2013
24
Network Integration
This chapter describes Yota PCRF integration with different networks and integration with IT
infrastructure.
Network Integration
LTE
A high-level view of Yota PCRF integration with LTE network is shown in the figure below:
Figure 5. Integration with LTE network
Internet
Services
eNB
Content
Video
P-GW
MME
S-GW
PCEF
DPI
Gx
Gxx
PCRF
Yota PCRF can be integrated with S-GW or P-GW. In GTP-based network Yota PCRF is
integrated with P-GW via Gx interface. In PMIP-based network Yota PCRF is also integrated
with S-GW via Gxx interface.
Integration with Gx-enabled external DPI is available as well.
WiMAX
A high-level view of Yota PCRF integration with WiMAX network is shown in the figure below:
Figure 6. Integration with WiMAX network
Internet
ASN-GW
DPI
PCEF
Services
Content
BS
Video
Gx
MS
AAA
PCRF
For QoS management in WiMAX networks, Yota PCRF is integrated with DPI via Gx interface.
In some cases it is needed to get traffic between AAA and ASN-GW to detect a device identifier.
Yota 2013
25
3G UTMS
If the 3G network has an enhanced GGSN (eGGSN) component, which includes PCEF function,
Yota PCRF integrates with the eGGSN via Gx interface. See Figure 7.1.
Figure 7.1. Integration with 3G UTMS network (eGGSN)
BSC
Internet
eGGSN
SGSN
Services
PCEF
Content
Video
Gx
PCRF
If the 3G network has GGSN without Gx support and external DPI with built-in PCEF, Yota
PCRF can be integrated with DPI via Gx interface. To identify subscribers Yota PCRF integrates
with the GGSN. See figure 7.2.
Figure 7.2. Integration with 3G UTMS network (GGSN)
BSC
Internet
SGSN
GGSN
DPI
PCEF
Services
Content
Video
Gx
PCRF
Yota 2013
26
Network Integration
3G CDMA2000
If the 3G CDMA 2000 network doesnt have an independent DPI component and PCEF function
is included in the PDSN\HA, Yota PCRF integrates with the PDSN\HA via Gx interface. See
Figure 8.1.
Figure 8.1. Integration with 3G CDMA2000 network (without independent DPI)
Internet
Services
PDSN/HA
Content
BSC
Video
Gx
PCRF
If the 3G CDMA 2000 network has an independent DPI component, which includes PCEF
function, Yota PCRF integrates with the DPI via Gx interface. To identify subscribers Yota PCRF
integrates with the PDSN\HA. See Figure 8.2.
Figure 8.2. Integration with 3G CDMA2000 network (independent DPI)
Internet
PDSN/HA
DPI
PCEF
Services
Content
BSC
Video
Gx
PCRF
Yota 2013
27
IMS
A high-level view of Yota PCRF integration with IMS is shown in the figure below:
Figure 9. Integration with IMS
IMS
P-CSCF
Rx
PCRF
AF
Gx
LTE
Rx
Rx
AF
Yota PCRF is integrated with the IMS P-CSCF (Proxy Call Session Control Function) via Rx
interface and with LTE network via Gx interface.
IMS P-CSCF component manages QoS and authorizes the usage of specific bearer services
(services that allow transmission of information signals between network interfaces) in relation
to IMS-based services.
Yota 2013
28
Network Integration
Convergence
Yota PCRF is a network-agnostic solution. It supports LTE, WiMAX, 3G and is capable of
controlling policies of different networks and enables operators to build a centralized policy
control solution across all operators networks. This network convergence concept is illustrated
in figure below:
Figure 10. Convergence
IMS
AF
AF
Qo
S
re q
ue
Qo
st
eq
Sr
ue
st
l i cy
Po
LTE
n
Co
l
tro
Policy Control
PCRF
Po
lic
yC
on
tro
l
3G
WiMAX
Yota PCRF receives QoS requests from different services via different interaction interfaces and
applies policies based on subscribers/network/session information.
Yota PCRF can implement policy control functions over transport networks as well as receive
notifications and QoS requests from IMS and AF via Rx and in compliance with this information
dynamically manage policies over transport networks.
Yota 2013
29
Connection
Manager
- Notifications
- Subscriber status
- Quota / Usage
Provisioning
Billing
Self-care
- Subscriber status
- Quota / Usage
PCRF
OSS
Cell load
information
QoS Tariffs
PLM
Billing
Yota PCRF integration with Billing allows subscribers to centralize policies and billing functions
in a multi-service/multi-network environment and have access to consolidated subscriber
information.
Self-care
Yota PCRF integration with self-care allows subscribers to see online status of their services.
Online status includes information about a subscribers remaining quota, either in terms of
time or volume.
OSS
Yota PCRF integration with OSS enables service providers to detect network congestion periods
and during these periods provide services with QoS based on subscriber data plans.
PLM/Product Catalog
Today, policy is a parameter of the same level of service as a price. Operator offers should
have both price and QoS configured in the same place.
Yota PCRF integration with PLM/Product Catalog rapidly decreases time required for configuring
new tariffs by service provider staff, thus reducing Time-to-Market for new marketing offers.
Yota 2013
30
Connection Manager
The best way to interact with mobile broadband subscribers is via the Connection Manager
instead of SMS, USSD, and other communication channels commonly used by service providers.
Yota PCRF integration with Connection Manager enables service providers to notify, make
promotions, and interact with subscribers via the Connection Manager which is always at hand.
Yota 2013
31
3
Feature Description
Policy Control in General
Usage-based Policy Control
Personalized Services
Time-based Policy Control
Location-based policy control
Policy Control Based on Device Type
Parental Control
Shared Quota
Congestion Management
Notifications and Promotion
Yota 2013
32
Personalized Services
One size never fits all. Some subscribers only use instant messaging programs (e.g., ICQ) or
do internet browsing to access social networks. They dont need high speed, but want to
always be on-line. Others download lots of movies and music from the Internet using P2P
services and high speed is important to them. And there also are subscribers who use their
USB dongles for business purposes. They need to be online even on the go. It is critical for
them to have guaranteed quality.
Yota 2013
33
Service validity period - PCRF controls the validity period which was set for each particular
service. If the service validity time comes to an end, PCRF takes an action like bandwidth
reducing or blocking broadband access. It can be used for parental controls when parents set
limited Internet access time for their children.
Time of a day/ days of a week - Operator can offer broadband access only during weekends
and holidays or during non-congestion periods for lower prices.
Control quality of service based on subscribers location and their favorite zones
Have connectivity all over the world and prevent roaming surprises
Yota 2013
34
Define a list of blocked devices or a list of blocked applications for specific devices
Manage devices and their usage to make sure that the subscriber uses his device in
accordance with a service plan
Parental Control
With internet access now becoming standard on mobile devices, parents want the peace of
their mind knowing that their children are safe when using their phone or PC and that
excessive usage can be prevented. For example, parents dont want their children to visit
specific sites and use the Internet more than 3 hours a day. Via the self-care portal, parents
can configure the list of sites which can be visited by their children, the time period when the
Internet can be used, and the parent can specify the maximum duration of daily Internet
usage.
Yota PCRF allows the abilities to:
Redirect a child to a special page each time he tries to access a site that was not approved
by his parents
Enforce full blocking of the Internet for children when their usage reaches daily limit
With the Parental Control feature, subscribers can make flexible configurations of the list of
web sites which can be visited with their subscription in self-care. These business rules then
are automatically applied and controlled in the network.
Shared Quota
Beyond increasing volumes, the growth of mobile data has also increased the number of
subscriptions per customer. Many companies provide their employees with mobile broadband
devices and many families may have several of them. Sometimes buying broadband access for
every device can be rather troublesome because a subscriber will have to monitor each of his
accounts and top-up pre-paid balance in time.
Yota PCRF provides advanced subscriber profile structure, where different subscriptions of an
individual or different individuals in an organization or a family, can be connected to each other.
Yota 2013
35
Congestion Management
With the Congestion Management feature Yota PCRF can control cell load and apply specific
policies to particular subscriber categories when congestion threshold is reached.
Cell load awareness begins with mapping active subscribers to the cell in which they have
active data sessions. Mapping is followed by measuring the cell in terms of the number of
active subscribers in the cell and in terms of the total bandwidth being used by those
subscribers. Once a pre-configured congestion threshold has been crossed, a specific policy
may be applied selectively per subscriber or for everyone in the cell until new measurements
indicate that the triggering condition has subsided.
Figure 12. Congestion Management Scheme
4. A
p
for a plies s
p
ffec
ted ecific r
su b
u
scri les
6. R
bers
e
for a moves
s
ffec
ted pecific
su b
r
scri ules
bers
5. Congestion
relief
Network
1. Congestion
notification
2. Requests profiles of
affected subscribers
PCRF
3. Sends profiles of
affected subscribers
SPR
Yota 2013
36
Yota 2013
37