Integrated Policy Control & Charging Architecture for Mobile ...
Integrated Policy Control & Charging Architecture for Mobile ...
Integrated Policy Control & Charging Architecture for Mobile ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Integrated</strong> <strong>Policy</strong><br />
<strong>Control</strong> & <strong>Charging</strong><br />
<strong>Architecture</strong> <strong>for</strong> <strong>Mobile</strong><br />
Broadband
<strong>Mobile</strong> Broadband<br />
Strong subscriber and traffic growth<br />
› Subscriber growth<br />
– more subscribers than <strong>for</strong><br />
fixed broadband by 2010<br />
› Traffic growth<br />
– applications same as <strong>for</strong><br />
fixed broadband<br />
– bulk of bandwidth used by<br />
minority of users<br />
– increasing due to streaming<br />
and peer-to-peer applications<br />
(Terabytes/year)<br />
3,000,000<br />
2,250,000<br />
1,500,000<br />
750,000<br />
Ericsson | 18-04-2012 | Page 2<br />
Traffic in mobile networks<br />
Voice<br />
Source: Internal Ericsson<br />
Data<br />
Other Data<br />
Downloads<br />
<strong>Mobile</strong> TV,<br />
Streaming<br />
Messaging<br />
<strong>Mobile</strong> PC<br />
Video<br />
Telephony
<strong>Mobile</strong> Broadband<br />
Meeting demand while protecting margins<br />
› Flat-rate pricing<br />
– attractive and easy to<br />
understand, drives growth<br />
› Over The Top (service<br />
content providers)<br />
– even more pressing<br />
› Revenues vs. cost<br />
– allow investments in<br />
additional capacity to serve<br />
new subscribers<br />
– protect per<strong>for</strong>mance of delaysensitive<br />
applications<br />
Ericsson | 18-04-2012 | Page 3<br />
Increased traffic<br />
per subscriber:<br />
- streaming<br />
- peer-to-peer
The Risk of the Dumb Pipe<br />
Internet players<br />
going mobile.<br />
Broadband traffic is<br />
growing exponentially,<br />
not revenue.<br />
Voice revenue is<br />
flattening and additional<br />
data revue can not fully<br />
compensate.<br />
Few subscribers consume<br />
a majority of the<br />
capacity.<br />
Difficult to differentiate<br />
other than on price.<br />
Ericsson | 18-04-2012 | Page 4<br />
Dumb Pipe<br />
BACK TO INDEX
Bit Pipe Smart pipe<br />
Internet players<br />
going mobile<br />
Broadband traffic is<br />
growing exponentially,<br />
the revenue is not<br />
Voice revenue is flattening<br />
out and additional data<br />
revenue can not yet fully<br />
compensate <strong>for</strong> that<br />
revenue loss<br />
Few subscribers<br />
consume a majority of<br />
the network capacity<br />
Difficult to differentiate<br />
other than on price<br />
Smartpipe enables MBB Differentiation and Monetization<br />
Bit<br />
Pipe<br />
Ericsson | 18-04-2012 | Page 5<br />
Bit Rate at Congestion<br />
Dynamic Differentiation<br />
Subscriber<br />
ToD<br />
Maximum Bit Rates<br />
WCDMA RAN Packet Core<br />
Prioritization<br />
Active Subscribers per Radio Cell<br />
…<br />
Service<br />
Internet<br />
“Gold” Subscriber<br />
No Prioritization<br />
“Bronze” Subscriber<br />
… and additionally Turbo Button, Voucher handling, Real-time notifications,<br />
Spending control etc.
Beyond flat rate<br />
powered by the network<br />
Price<br />
Best-ef<strong>for</strong>t broadband<br />
Single<br />
Flat rate<br />
Offer<br />
Lost revenue<br />
opportunity<br />
OTT are winners<br />
Penetration<br />
Ericsson | 18-04-2012 | Page 6<br />
Price<br />
Service-based broadband<br />
Multiple targeted<br />
packages with QoS<br />
and policy control<br />
<strong>for</strong> differentiation<br />
Penetration<br />
Operators are winners<br />
THE E2E IP NETWORK COST EFFECTIVELY<br />
ENABLES NEW BUSINESS MODELS
Quali sono le soluzioni e le<br />
piatta<strong>for</strong>me che gli Operatori<br />
Mobili stanno considerando<br />
per far fronte alla dinamicità e<br />
ai nuovi requisiti del mercato<br />
Broadband mobile?
QoS, <strong>Policy</strong> and <strong>Charging</strong> <strong>Control</strong><br />
PCC <strong>Architecture</strong><br />
› <strong>Policy</strong> and <strong>Charging</strong><br />
<strong>Control</strong><br />
– <strong>Policy</strong> and <strong>Charging</strong><br />
Rules Function<br />
– <strong>Policy</strong> <strong>Control</strong><br />
En<strong>for</strong>cement Function<br />
– Bearer Binding and<br />
Event Reporting<br />
Function<br />
› Off-line and On-line<br />
<strong>Charging</strong> Systems<br />
– Subscription Profile<br />
Registry<br />
– Application Function<br />
Ericsson | 18-04-2012 | Page 8
How to build the right POLICY<br />
control & charging architecture?<br />
Which is the recommended<br />
architecture <strong>for</strong> fair use<br />
cases and specific charging<br />
use cases?<br />
Where to define the<br />
product offers?<br />
What’s the most flexible<br />
and future poof solution?<br />
What are the benefits or<br />
inconvenience of<br />
different architectures?<br />
Where to report<br />
usage and<br />
accumulate quotas ?<br />
Ericsson | 18-04-2012 | Page 9<br />
How do I make money<br />
on my MBB offers?<br />
How to handle credit<br />
limits per subscriber?<br />
How to manage time<br />
quotas per service?<br />
How to ensure<br />
consistent provisioning<br />
of policy and rating?
PCC architecture<br />
(3GPP TS 23.203 V7.12.0)<br />
Online <strong>Charging</strong> System (OCS)<br />
CAMEL<br />
SCP<br />
Ericsson<br />
<strong>Charging</strong><br />
System<br />
Service Data Flow<br />
Based<br />
Credit <strong>Control</strong><br />
Subscription Profile<br />
Repository<br />
(SPR)<br />
Gy<br />
Sp<br />
Ericsson | 18-04-2012 | Page 10<br />
Gz<br />
Rx<br />
Gx<br />
AF<br />
Ericsson<br />
<strong>Policy</strong> and <strong>Charging</strong><br />
Service Aware<br />
Rules Function<br />
<strong>Policy</strong> (PCRF) <strong>Control</strong>ler<br />
(SAPC)<br />
Ericsson PCEF<br />
GGSN<br />
or SASN<br />
GW<br />
Ericsson<br />
File & Event<br />
Mediation<br />
Offline<br />
<strong>Charging</strong><br />
System<br />
(OFCS)
Reference architecture<br />
Ericsson Business Solution - SACC<br />
Ericsson node included in SACC Business Solution<br />
Ericsson node not included in SACC Business Solution<br />
Other vendor’s node/system<br />
RBS<br />
Iub<br />
Billing<br />
System<br />
HLR<br />
Vendor<br />
Specific<br />
Interfaces<br />
Ericsson<br />
Multi Mediation<br />
Online<br />
<strong>Charging</strong><br />
System<br />
File & Event Online<br />
Ericsson<br />
RNC<br />
Radio Access Network<br />
Gz<br />
IuPS<br />
Gy<br />
Ericsson<br />
SGSN<br />
Ericsson<br />
<strong>Charging</strong><br />
System<br />
Gn<br />
CAI<br />
IMS<br />
P-CSCF<br />
Packet Core Network<br />
Ericsson | 18-04-2012 | Page 11<br />
Customer<br />
Care<br />
System<br />
Radius<br />
Provisioning /<br />
EMA<br />
Rx LDAP<br />
Gy<br />
Ericsson<br />
GGSN<br />
Gi<br />
Gx<br />
Ericsson<br />
SAPC<br />
Self-care<br />
System<br />
Gx, Rx<br />
Ericsson<br />
SASN<br />
Vendor Specific<br />
Interfaces / CAI<br />
Gi<br />
Application<br />
Function<br />
Rx<br />
LDAP<br />
/ SQL<br />
/SOAP<br />
SPR<br />
Ericsson<br />
MSP<br />
ICAP<br />
SFTP<br />
Content<br />
Classification<br />
Engine<br />
Ericsson OSS<br />
ENIQ<br />
Business<br />
Objects<br />
Operator<br />
Service<br />
Network<br />
Internet<br />
Corporate<br />
Intranet
Role of Common <strong>Policy</strong> Manager<br />
INFO<br />
• Subscriber In<strong>for</strong>mations/Subscriber Group<br />
• Calendar (Day, Hour, …)<br />
• Dynamic Session in<strong>for</strong>mations from Application<br />
Function<br />
• Access In<strong>for</strong>mation (User Equipment, network type,<br />
location, …)<br />
• Dynamic In<strong>for</strong>mation about the context (es. APN,<br />
…)<br />
• Metric used<br />
• …..<br />
Media flow<br />
<strong>Policy</strong> Manager<br />
Ericsson | 18-04-2012 | Page 12<br />
AF SPR<br />
GW<br />
PCEF<br />
PCC RULE<br />
• Change<br />
bandwidth<br />
• Deny/Allow<br />
Services access<br />
• Redirection<br />
• Change <strong>Charging</strong><br />
method<br />
• Usage reporting<br />
• …
Features<br />
› Session Management<br />
› Service Awareness<br />
› Access <strong>Control</strong><br />
› <strong>Charging</strong><br />
› Quality of Service <strong>Control</strong><br />
› Fair Usage <strong>Policy</strong> <strong>Control</strong><br />
› User Interaction and Notification<br />
› Traffic Monitoring and Reporting<br />
Ericsson | 18-04-2012 | Page 13
Features<br />
› Session Management<br />
› Service Awareness<br />
› Access <strong>Control</strong><br />
› <strong>Charging</strong><br />
› Quality of Service <strong>Control</strong><br />
› Fair Usage <strong>Policy</strong> <strong>Control</strong><br />
› User Interaction and Notification<br />
› Traffic Monitoring and Reporting<br />
Ericsson | 18-04-2012 | Page 14
Session management<br />
IP-CAN Session and bearer<br />
› An IP-CAN Session is an association between a UE and an IP Network<br />
identified by one or more UE IP Addresses and a PDN ID (e.g. APN)<br />
› An IP-CAN Session incorporates one or more IP-CAN Bearers<br />
› An IP-CAN Session exists as long as the UE IP Addresses are assigned<br />
to the IP Network<br />
GGSN UE<br />
GGSN Radio<br />
Network<br />
IP-CAN SESSION<br />
Default Bearer Dedicated Bearer<br />
GGSN SGSN<br />
Ericsson | 18-04-2012 | Page 15<br />
GGSN<br />
Service 1<br />
(e.g. Internet)<br />
Service 2<br />
(e.g. File Sharing)<br />
Service 3<br />
(e.g. <strong>Mobile</strong>TV)
Session management<br />
Terminology<br />
› Default Bearer<br />
– Provides basic connectivity<br />
– Can be compared with primary PDP Context<br />
› Dedicated Bearer<br />
– Shares IP-Address with the default bearer<br />
– Provides different Quality of Service Settings<br />
– Can be compared with the Secondary PDP Context<br />
› Session Management<br />
– IP-CAN Session Establishment --- (PDP Context Activate, Create)<br />
– IP-CAN Session Modification------ (PDP Context Update, Modify)<br />
– IP-CAN Session Termination ----- (PDP Context Terminate,<br />
Delete)<br />
Ericsson | 18-04-2012 | Page 16
Features<br />
› Session Management<br />
› Service Awareness<br />
› Access <strong>Control</strong><br />
› <strong>Charging</strong><br />
› Quality of Service <strong>Control</strong><br />
› Fair Usage <strong>Policy</strong> <strong>Control</strong><br />
› User Interaction and Notification<br />
› Traffic Monitoring and Reporting<br />
Ericsson | 18-04-2012 | Page 17
Service awareness<br />
Packet Inspection Analysis, classification & <strong>Control</strong><br />
Heuristic<br />
Patterns<br />
...01101011...<br />
undifferentiated<br />
incoming packets<br />
Analysis<br />
Engine<br />
Protocol<br />
Analyzers<br />
GGSN-MPG or SASN<br />
Classification<br />
Engine<br />
analysis<br />
parameters<br />
obtained<br />
Classification<br />
Rules<br />
Ericsson | 18-04-2012 | Page 18<br />
Reporting<br />
Usage<br />
Reporting<br />
(Volume /<br />
Time / Event)<br />
service<br />
differentiated<br />
sessions<br />
Gy, Gx, Rx<br />
<strong>Policy</strong><br />
Provisioning<br />
<strong>Control</strong><br />
Profiles<br />
and<br />
Policies Output<br />
traffic<br />
<strong>Control</strong><br />
<strong>Control</strong><br />
Engines<br />
Engines<br />
<strong>Control</strong> engines:<br />
Authorization, <strong>Charging</strong>,<br />
Redirection, QoS,<br />
Application notification,<br />
etc
Packet inspection<br />
Analysis<br />
Heuristic Analysis<br />
Empirical patterns obtained in Layer 3 – Layer<br />
7 headers + payload + IP flow metrics<br />
Ericsson | 18-04-2012 | Page 19<br />
Layer 3<br />
Layer 4 Layer 7<br />
Shallow Packet Inspection<br />
Layer 7+<br />
IP 5-tuple: Layer 3 source / destination IP,<br />
protocol type and Layer 4<br />
source / destination port<br />
Deep Packet Inspection<br />
Headers in Layer 4, Layer 7 and Layer 7+
Packet inspection<br />
Heuristic Analysis<br />
Binary Patterns<br />
...01011001011...<br />
...00101000101...<br />
...00100100101...<br />
. . .<br />
Patterns in IP Flow<br />
Metrics<br />
. . .<br />
GGSN/SASN<br />
Ericsson | 18-04-2012 | Page 20<br />
IP Connectivity<br />
Patterns<br />
Most probable<br />
protocol<br />
. . .
Heuristic analysis<br />
accuracy<br />
› IP flow metrics take some time to be calculated (average<br />
needs some minimum sample traffic be<strong>for</strong>e convergence)<br />
Likelihood of<br />
being Skype<br />
100%<br />
90%<br />
› Bit and connectivity patterns may involve a defined<br />
sequence of packets<br />
Converging<br />
Same packets miss the<br />
classification criteria<br />
Ericsson | 18-04-2012 | Page 21<br />
Time
Features<br />
› Session Management<br />
› Service Awareness<br />
› Access <strong>Control</strong><br />
› <strong>Charging</strong><br />
› Quality of Service <strong>Control</strong><br />
› Fair Usage <strong>Policy</strong> <strong>Control</strong><br />
› User Interaction and Notification<br />
› Traffic Monitoring and Reporting<br />
Ericsson | 18-04-2012 | Page 22
Authorization<br />
› A service is authorized if<br />
– An authorization rule has been installed over the Gx interface that is<br />
associated with the service data flow in the PCEF<br />
– The service data flow is configured as always-authorized in the PCEF<br />
(GGSN/SASN)<br />
– The service data flow is authorized by local configuration (no Gx<br />
used)<br />
› A service is not authorized if<br />
– No authorization in<strong>for</strong>mation is available (provided over Gx or<br />
locally configured in the PCEF (GGSN/SASN)<br />
Ericsson | 18-04-2012 | Page 23
Access control<br />
service authorization<br />
Incoming traffic<br />
PISC<br />
Services are<br />
identified and<br />
classified<br />
with filter rules<br />
GGSN/SASN<br />
SDF-ID=1<br />
SDF-ID=2<br />
SDF-ID=3<br />
OCS<br />
Local<br />
<strong>Policy</strong><br />
Gy<br />
Ericsson | 18-04-2012 | Page 24<br />
Authorization<br />
SAPC<br />
Gx
Service Authorization<br />
› Access control provides the ability <strong>for</strong> detailed control of how users could have<br />
or not have access to a service.<br />
› The operator desired authorization conditions <strong>for</strong> the services can be<br />
configured:<br />
– Per each service and applicable to all subscribers<br />
– Per each service and applicable to a group of subscribers<br />
– Per service and per subscriber basis<br />
Core Network<br />
Ericsson GGSN<br />
or SASN<br />
Ericsson | 18-04-2012 | Page 25<br />
Service Network<br />
Discard<br />
Self-subscription<br />
portal<br />
Redirect<br />
Forward<br />
Internet<br />
Free and authorized<br />
services
Features<br />
› Session Management<br />
› Service Awareness<br />
› Access <strong>Control</strong><br />
› <strong>Charging</strong><br />
› Quality of Service <strong>Control</strong><br />
› Fair Usage <strong>Policy</strong> <strong>Control</strong><br />
› User Interaction and Notification<br />
› Traffic Monitoring and Reporting<br />
Ericsson | 18-04-2012 | Page 26
<strong>Charging</strong><br />
Online credit control and <strong>Charging</strong><br />
Vendor<br />
Specific<br />
Interfaces<br />
Radio<br />
Access<br />
Online<br />
<strong>Charging</strong><br />
System<br />
Ericsson Multi Mediation<br />
Online<br />
Mediation<br />
SGSN<br />
Gy<br />
Ericsson<br />
GGSN<br />
Ericsson<br />
<strong>Charging</strong><br />
System<br />
Ericsson | 18-04-2012 | Page 27<br />
Gi<br />
Radius<br />
› GGSN-MPG/SASN<br />
– Classify the traffic<br />
– Measure the traffic<br />
– Report the measured traffic<br />
› Online <strong>Charging</strong> System<br />
Gy<br />
Ericsson<br />
SASN<br />
– Handle the money and<br />
accounts<br />
– Make any rating<br />
– Specifies what shall be<br />
measured <strong>for</strong> a specific<br />
Rating Group<br />
Operator<br />
Service<br />
Network<br />
Internet<br />
Corporate<br />
Intranet
Dynamic service configuration in chsys<br />
Service detection<br />
1<br />
ChSys<br />
Quota reporting<br />
Ericsson | 18-04-2012 | Page 28<br />
3<br />
Granted Quota<br />
Granted quota<br />
GGSN-MPG<br />
/SASN<br />
2<br />
4
Off line <strong>Charging</strong><br />
Statistics and<br />
Data Warehouse<br />
Billing<br />
System<br />
Vendor<br />
Specific<br />
Interfaces<br />
Ericsson Multi Mediation<br />
File & Event<br />
Mediation<br />
Radio<br />
Access<br />
SGSN<br />
› GPRS CDRs<br />
Ericsson | 18-04-2012 | Page 29<br />
– G-CDR and eG-CDR <strong>for</strong>mat<br />
– Binary <strong>for</strong>mat: ASN.1 BER<br />
– Partial CDRs <strong>for</strong> time and volume thresholds<br />
› SASN also supports:<br />
– Event Detail Records (EDRs)<br />
Gz<br />
Ericsson<br />
GGSN<br />
› ASCII <strong>for</strong>mat XML or CSV<br />
› Generated based on configurable rules<br />
Gi<br />
Radius<br />
Gz<br />
Ericsson<br />
SASN<br />
Operator<br />
Service<br />
Network<br />
Internet<br />
Corporate<br />
Intranet
Features<br />
› Session Management<br />
› Service Awareness<br />
› Access <strong>Control</strong><br />
› <strong>Charging</strong><br />
› Quality of Service <strong>Control</strong><br />
› Fair Usage <strong>Policy</strong> <strong>Control</strong><br />
› User Interaction and Notification<br />
› Traffic Monitoring and Reporting<br />
Ericsson | 18-04-2012 | Page 30
QoS, <strong>Policy</strong> and charging control<br />
What is QOS?<br />
Subscriber<br />
Differentiation<br />
Business vs. Standard<br />
Post- vs. Pre-Paid<br />
Roamers<br />
Privileged (e.g. Police)<br />
Heavy users<br />
etc.<br />
Ericsson | 18-04-2012 | Page 31<br />
Total Edge-to-Edge<br />
(UEs GW) Capacity<br />
Load Management<br />
BH load control<br />
Priority en<strong>for</strong>cement<br />
Maximum Bit Rate<br />
...<br />
Service<br />
Differentiation<br />
Public Internet<br />
Corporate (VPN)<br />
Premium Content<br />
P2P File Sharing<br />
Video Streaming<br />
IMS Voice<br />
Non-IMS Voice<br />
<strong>Mobile</strong>-TV<br />
etc.
QoS, <strong>Policy</strong> and <strong>Charging</strong> <strong>Control</strong><br />
Default and Dedicated Bearers<br />
› One Default Bearer per IP<br />
Address to Provide Basic<br />
Connectivity<br />
› Default Bearer is Always a<br />
Non-GBR Bearer<br />
› Default Bearer QoS Assigned<br />
by MME Based on<br />
Subscription Data from HSS<br />
IP Address<br />
Dedicated Bearer (aka Secondary PDP Context)<br />
Terminal<br />
Default Bearer (aka Primary PDP Context)<br />
RAN<br />
Transport<br />
Ericsson | 18-04-2012 | Page 32<br />
› Providing Different QoS in RAN<br />
and/or Transport Network to two<br />
Service Data Flows <strong>for</strong> the Same<br />
Terminal Requires One or More<br />
Dedicated Bearers<br />
› Dedicated Bearer can be Non-GBR<br />
or GBR Bearer<br />
› Dedicated Bearer QoS and Packet<br />
Filters Assigned by <strong>Policy</strong><br />
<strong>Control</strong>ler (PCRF) Based on<br />
Operator <strong>Policy</strong><br />
Gateway<br />
(Bearer <strong>Policy</strong><br />
En<strong>for</strong>cer)<br />
Service 1<br />
(e.g. Internet)<br />
Service 2<br />
(e.g. P2P File Sharing)<br />
Service 3<br />
(e.g. IMS-Voice or MTV)<br />
Service Data Flow (SDF)
Quality of Service (QoS)<br />
Bearer QoS Management (e2E QoS)<br />
› It is possible to negotiate the Bearer QoS (upgrade / downgrade / reject)<br />
at PDP Context activation and modification<br />
› An un-solicited Bearer QoS change can be initiated by SAPC during the<br />
lifetime of the PDP Context, i.e. PCRF Initiated QoS Modification<br />
Radio<br />
Network<br />
PDP Context<br />
SGSN<br />
Ericsson | 18-04-2012 | Page 33<br />
GGSN<br />
QoS <strong>for</strong> a PDP Context<br />
• Traffic Class<br />
• Traffic Handling Priority (THP)<br />
• Maximum Bit Rate (MBR)<br />
• Guaranteed Bit Rate (GBR)<br />
• …
Quality of Service (QoS)<br />
IP Flow Bandwidth Management (Throttling)<br />
› IP Flow Bandwidth Management allows controlling single<br />
IP flows within a multi-service PDP Context<br />
– The bandwidth limits can be changed during a session<br />
– It is possible to change the bandwidth limit settings from SAPC<br />
PDP Context<br />
IP Flows<br />
Ericsson | 18-04-2012 | Page 34<br />
GGSN/P-GW
Default Bearer QoS <strong>Control</strong><br />
Downgrade QoS (THP) <strong>for</strong> a heavy user<br />
Aggregated bandwidth<br />
Cell Capacity<br />
Aggregated<br />
load in cell<br />
THP=2<br />
THP=2<br />
Total<br />
volume<br />
limit<br />
exceeded<br />
THP=2<br />
THP=3<br />
Heavy user dynamically downprioritized at network congestion<br />
Ericsson | 18-04-2012 | Page 35<br />
Time
Bearer QoS Mgmt vs.<br />
IP Flow Bandwidth Mgmt<br />
› Bearer QoS management<br />
– can be managed in the whole GPRS network<br />
(i.e. Packet Core + RAN)<br />
– can act as a flag and works in case of actual network congestion<br />
– has no effect on the service per<strong>for</strong>mance as long as there is no<br />
network congestion<br />
– preserves scarce resources when they get limited<br />
› IP flow bandwidth management<br />
– acts on the single IP flow (i.e. service) independently of the actual<br />
congestion in the network<br />
– has an immediate impact on the service per<strong>for</strong>mance<br />
– tries to avoid scarce resources becoming congested<br />
Ericsson | 18-04-2012 | Page 36
UE<br />
E2E QoS Architectural Overview – What<br />
does each node do?<br />
Uu<br />
Scheduling<br />
of resources<br />
(air interface)<br />
RBS<br />
HLR<br />
RNC SGSN GGSN<br />
RAN<br />
<strong>Mobile</strong><br />
Backhaul RAN MPBN<br />
Prioritization<br />
of IP packets<br />
Iub<br />
Prioritization<br />
of IP packets<br />
Radio<br />
resource<br />
management<br />
Static<br />
QoS profile<br />
IuPS<br />
Prioritization<br />
of IP packets<br />
Negotiation<br />
of QoS<br />
parameters<br />
Ericsson | 18-04-2012 | Page 37<br />
Gn<br />
Dynamic<br />
QoS control<br />
SAPC AF<br />
Gx Gx<br />
Rx<br />
Rx<br />
Negotiation<br />
of QoS<br />
parameters<br />
Event<br />
detection<br />
SASN<br />
Gi Gi<br />
Packet<br />
inspection<br />
engine
Features<br />
› Session Management<br />
› Service Awareness<br />
› Access <strong>Control</strong><br />
› <strong>Charging</strong><br />
› Quality of Service <strong>Control</strong><br />
e2e QoS in LTE<br />
› Fair Usage <strong>Policy</strong> <strong>Control</strong><br />
› User Interaction and Notification<br />
› Traffic Monitoring and Reporting<br />
Ericsson | 18-04-2012 | Page 38
QoS Parameters in EPS<br />
› UE-AMBR<br />
› APN-AMBR<br />
Aggregated Maximum Bit Rate per UE and APN<br />
› ARP Allocation/Retention Priority<br />
› QCI QoS Class Identifier<br />
› GBR Guaranteed Bit Rate<br />
› (Bearer-)MBR Maximum Bit Rate (only <strong>for</strong> GBR Data)<br />
Additionally<br />
› (SDF-)MBR MBR applicable per SDF<br />
Ericsson | 18-04-2012 | Page 39
Aggregated Maximum Bit Rate<br />
› UE-AMBR or APN-AMBR en<strong>for</strong>cement (UL and DL)<br />
– UE-AMBR<br />
› En<strong>for</strong>ced in LTE<br />
– APN-AMBR<br />
› En<strong>for</strong>ced in:<br />
- GGSN-MPG<br />
- CPG<br />
UE-AMBR<br />
eNodeB<br />
Ericsson | 18-04-2012 | Page 40<br />
APN 1-AMBR<br />
APN 2-AMBR<br />
APN 3-AMBR<br />
APN 1<br />
GW1<br />
APN 2<br />
APN 3<br />
GW2<br />
Maximum Bandwidth<br />
per user
Summary MBR en<strong>for</strong>cements<br />
In GGSN-MPG<br />
› APN-AMBR en<strong>for</strong>ced in DL and UL <strong>for</strong> all non-GBR bearers sharing<br />
the same PDN connection<br />
› Bearer-MBR, is en<strong>for</strong>ced in DL, valid only <strong>for</strong> GBR bearers in EPS and<br />
<strong>for</strong> all bearers in UMTS<br />
› SDF-MBR aka IP flow throttling, (applied through dynamic or static<br />
PCC rule) is en<strong>for</strong>ced DL and UL (regardless of the bearer).<br />
In the RAN<br />
› UE-AMBR is en<strong>for</strong>ced in UL and DL (from L12B)<br />
Ericsson | 18-04-2012 | Page 41
Bearer QoS Parameters:<br />
QoS Class Identifier (QCI)<br />
› 9 Standardized QoS Classes<br />
› In Specs Each of the 9 QCIs is Associated with Standardized Characteristics in<br />
Terms of Priority, Packet Delay Budget, and Packet Error Loss Rate<br />
› Operator <strong>Policy</strong> Decides Semi-Static Mapping Service+Subscriber-ID to QCI<br />
QCI Resource<br />
Type<br />
Priority Packet Delay<br />
Budget<br />
Ericsson | 18-04-2012 | Page 42<br />
Packet Error<br />
Loss Rate<br />
Example Services<br />
1 GBR 2 100 ms 10-2 Conversational Voice<br />
2 4 150 ms 10-3 Conversational Video (Live Streaming)<br />
3 3 50 ms 10-3 Real Time Gaming<br />
4 5 300 ms 10-6 Non-Conversational Video (Buffered<br />
Streaming)<br />
5 Non-GBR 1 100 ms 10-6 IMS signaling<br />
6 6 300 ms 10-6 Video (Buffered Streaming)<br />
TCP-based (<strong>for</strong> example, www, e-mail,<br />
chat, ftp, p2p file sharing, progressive<br />
video)<br />
7 7 100 ms 10-3 Voice, Video (Live Streaming),<br />
Interactive Gaming<br />
8 8 300 ms 10-6 Video (Buffered Streaming), TCP-based<br />
9 9<br />
(<strong>for</strong> example, www, e-mail, chat, ftp, p2p<br />
file sharing, progressive video)
Features<br />
› Session Management<br />
› Service Awareness<br />
› Access <strong>Control</strong><br />
› <strong>Charging</strong><br />
› Quality of Service <strong>Control</strong><br />
› Fair Usage <strong>Policy</strong> <strong>Control</strong><br />
› User Interaction and Notification<br />
› Traffic Monitoring and Reporting<br />
Ericsson | 18-04-2012 | Page 43
Fair usage policy en<strong>for</strong>cement<br />
QoS Based on Accumulated Usage<br />
(Bandwidth)<br />
1024 kbps<br />
64 kbps<br />
(Accumulated<br />
traffic volume)<br />
Fair usage<br />
limit<br />
Billing<br />
period 1<br />
Downgrade Upgrade<br />
Ericsson | 18-04-2012 | Page 44<br />
Billing<br />
period 2<br />
(Time)<br />
(Time)<br />
Operator’s<br />
own services<br />
Peer-to-peer<br />
applications
Time of Day Fair Usage <strong>Policy</strong><br />
Heavy<br />
Users<br />
Normal<br />
Users<br />
Shared Capacity<br />
(radio and<br />
transport link)<br />
Ericsson | 18-04-2012 | Page 45<br />
SAPC spr<br />
GGSN
8 Mbps<br />
bandwidth<br />
128 kbps<br />
Time of Day FUP (CAP Trasversale)<br />
SAPC<br />
GGSN<br />
Users whole<br />
available BW<br />
SAPC Granted<br />
Volume Quota<br />
Gx<br />
5 pm<br />
Gx<br />
Gx<br />
QoS bearer<br />
downgrade<br />
GGSN Usage<br />
Reporting<br />
<br />
Gx signaling storm is expected at 5 and 11 o’clock<br />
Ericsson | 18-04-2012 | Page 46<br />
Gx<br />
11 pm<br />
QoS bearer<br />
upgrade<br />
SPR<br />
time
Cell-Aware Throttling<br />
Congestion Location In<strong>for</strong>mation<br />
per Location (Cell-ID, LAC, RAI)<br />
configured in SAPC based on<br />
OSS-RC statistics<br />
Ericsson | 18-04-2012 | Page 47<br />
SAPC<br />
GGSN-MPG<br />
/SASN<br />
During Peak Hour there is network congestion and then the<br />
BW is reduced in controlled zones and <strong>for</strong> controlled users<br />
Non-peak hour<br />
· MBR = 5 Mbps<br />
Peak hour & Heavy &<br />
Congested Zone<br />
· MBR = 512 kbps<br />
Default <strong>Policy</strong>:<br />
MBR = 5 Mbps<br />
Congestion <strong>Policy</strong>:<br />
(Peak Hour – Congestion)<br />
From: 10:00<br />
to: 12:00<br />
MBR = 512 kbps
What is policy & <strong>Charging</strong> control?<br />
Operator<br />
Business<br />
Models<br />
<strong>Policy</strong> & <strong>Charging</strong><br />
<strong>Control</strong><br />
› Enables Operators to <strong>Control</strong> …<br />
– Access to content & services by blocking or redirecting<br />
– <strong>Charging</strong> per application and/or per subscriber<br />
– Quality of Service (QoS) per application and/or per subscriber<br />
Ericsson | 18-04-2012 | Page 48<br />
Impossibile visualizzare l'immagine. La memoria del computer<br />
potrebbe essere insufficiente per aprire l'immagine oppure<br />
l'immagine potrebbe essere danneggiata. Riavviare il computer e<br />
aprire di nuovo il file. Se viene visualizzata di nuovo la x rossa,<br />
potrebbe essere necessario eliminare l'immagine e inserirla di<br />
nuovo.<br />
Broadband<br />
Network Capacity<br />
Subscriber &<br />
Service<br />
Differentiation<br />
Maximize Return on Investment into Network Capacity<br />
Operator<br />
<strong>Control</strong>led<br />
Wholesale<br />
OverTheTop
<strong>Integrated</strong> <strong>Architecture</strong><br />
<strong>Policy</strong> and <strong>Charging</strong> <strong>for</strong> Data<br />
• <strong>Charging</strong> product<br />
offers<br />
• <strong>Charging</strong> events<br />
• Rating<br />
• Credit limits<br />
• Balance<br />
• Other services<br />
consumption<br />
• Refill<br />
CHSys-<br />
OCS<br />
mBC<br />
Business Support Systems<br />
Customer Care, Self-Provisioning etc.<br />
DB<br />
ESy<br />
GGSN-mpG<br />
SASN PCEFor<br />
3GPP GW<br />
Ericsson | 18-04-2012 | Page 49<br />
SAPC<br />
PCRF<br />
Ericsson PCC <strong>Architecture</strong><br />
SAPC uses SDP<br />
as SPR DB<br />
• QoS control<br />
• <strong>Charging</strong> control<br />
• Gating control<br />
• Application<br />
triggered QoS
Ericsson Proposal <strong>for</strong> new PCC<br />
architecture<br />
› 3GPP is currently discussing to define a way to exchange in<strong>for</strong>mation<br />
between OCS and PCRF. The target release is 3GPP Rel-11.<br />
› The proposal driven from Ericsson is to define a Diameter interface<br />
between OCS and PCRF<br />
Gxx<br />
Subscription Profile<br />
Repository<br />
(SPR)<br />
Sp<br />
<strong>Policy</strong> and <strong>Charging</strong> Rules Function<br />
(PCRF)<br />
BBERF<br />
Gx<br />
Rx<br />
PCEF<br />
Gateway<br />
AF<br />
Ericsson | 18-04-2012 | Page 50<br />
Sy<br />
Gy<br />
Gz<br />
Online <strong>Charging</strong> System (OCS)<br />
Service Data Flow<br />
Based<br />
Credit <strong>Control</strong><br />
Offline<br />
<strong>Charging</strong><br />
System<br />
(OFCS)
3GPP Standard <strong>for</strong> <strong>Charging</strong> and <strong>Policy</strong><br />
<strong>for</strong> Data<br />
Ericsson | 18-04-2012 | Page 51<br />
Gxx<br />
Subscription Profile<br />
Repository<br />
(SPR)<br />
Sp<br />
<strong>Policy</strong> and <strong>Charging</strong> Rules Function<br />
(PCRF)<br />
BBERF<br />
3GPP Rel11<br />
Diameter based protocol<br />
Gx<br />
Rx<br />
PCEF<br />
Gateway<br />
AF<br />
Sy<br />
Gy<br />
Gz<br />
Online <strong>Charging</strong> System (OCS)<br />
3GPP Sy enables that PCRF stand-alone nodes become<br />
aware of “users-charging-context-status” overcoming<br />
functional limitations <strong>for</strong> Advanced Data Monetization<br />
Service Data Flow<br />
Based<br />
Credit <strong>Control</strong><br />
Offline<br />
<strong>Charging</strong><br />
System<br />
(OFCS)
What is Ericsson Sy?<br />
› Pre-3GPP Sy implementation based on draft 3GPP Rel-11<br />
Sy specification<br />
› Ericsson Sy allows <strong>for</strong><br />
– Cost efficient solution with maximum integration between already<br />
deployed features in SAPC and ChSys-MBC<br />
– Common User Data Base: SAPC uses Ericsson ChSys User DB as<br />
SPR-Entity<br />
› Introduced in SAPC 2011B and ChSys-MBC 2.1<br />
Ericsson | 18-04-2012 | Page 52
Ericsson integrated <strong>Policy</strong> and charging<br />
<strong>Architecture</strong><br />
BTS<br />
NodeB<br />
eNodeB<br />
Usage storage<br />
and User accounts<br />
BSC<br />
RNC<br />
Product offers<br />
SGSN<br />
MME<br />
Business Support Systems<br />
Subscriber<br />
DB<br />
Ericsson<br />
CHSys-MBC<br />
GGSN-mpG<br />
SASN or<br />
3GPP GW<br />
Ericsson | 18-04-2012 | Page 53<br />
<strong>Integrated</strong> <strong>Policy</strong> and <strong>Charging</strong><br />
(IPC)<br />
Gy<br />
ESy<br />
Gx<br />
DPI<br />
Ericsson<br />
SAPC<br />
Gi<br />
Rx<br />
<strong>Policy</strong><br />
DB<br />
Profile data<br />
management<br />
Operator Service<br />
Network<br />
Internet<br />
Rx<br />
Application<br />
function<br />
Corporate Intranet<br />
IMS<br />
<strong>Policy</strong> management
Ericsson integrated <strong>Policy</strong> and charging<br />
Main benefits<br />
Single BSS<br />
integration<br />
Keep account and<br />
subscription DB in ChSys-<br />
MBC, One Common User<br />
Profile database<br />
BTS<br />
NodeB<br />
eNodeB<br />
BSC<br />
RNC<br />
Credit control <strong>for</strong> both<br />
CS and PS domain<br />
Unified SGSN Usage<br />
Reporting: MMEReuse<br />
of<br />
Real-Time <strong>Charging</strong> i/f<br />
Business Support Systems<br />
Subscriber<br />
DB<br />
Ericsson<br />
CHSys-MBC<br />
GGSN-mpG<br />
SASN or<br />
3GPP GW<br />
Ericsson | 18-04-2012 | Page 54<br />
<strong>Integrated</strong> <strong>Policy</strong> and <strong>Charging</strong><br />
(IPC)<br />
Gy<br />
Enabling fixedmobile<br />
convergence<br />
support<br />
ESy<br />
Cross-service promotions<br />
and bonuses<br />
Gx<br />
DPI<br />
Ericsson<br />
SAPC<br />
Gi<br />
Rx<br />
<strong>Policy</strong><br />
DB<br />
Ready <strong>for</strong> VoLTE,<br />
Video Streaming<br />
Services<br />
Operator Service<br />
Network<br />
Internet<br />
Rx<br />
Multiple Gx-<br />
PCEF integration<br />
Application<br />
function<br />
E2e QoS Corporate <strong>Control</strong> <strong>for</strong> Intranet<br />
GPRS, LTE/EPC, IMS,<br />
Fixed & <strong>Mobile</strong>, Multivendor<br />
PCEF<br />
IMS
Ericsson <strong>Integrated</strong> <strong>Policy</strong> and<br />
<strong>Charging</strong> solution <strong>Architecture</strong><br />
<strong>Policy</strong>-Group ::= < AVP Header: 1347 ><br />
{ <strong>Policy</strong>-Group-Name }<br />
[ <strong>Policy</strong>-Group-Priority ]<br />
[ <strong>Policy</strong>-Group-Activation-Time ]<br />
[ <strong>Policy</strong>-Group-Deactivation-Time ]<br />
*[ AVP ]<br />
Ericsson-<strong>Policy</strong>-Counter-Status-Report ::= < AVP<br />
Header: 1355><br />
[ <strong>Policy</strong>-Counter-<strong>Policy</strong>-Group-Name ]<br />
{ Ericsson-<strong>Policy</strong>-Counter-Identifier }<br />
{ Ericsson-<strong>Policy</strong>-Counter-Status }<br />
*[ AVP ]<br />
ChSys-MBC<br />
2.1<br />
ESy<br />
ESy<br />
<strong>Policy</strong> Group<br />
<strong>Policy</strong> Counter <strong>Policy</strong> Group Status<br />
<strong>Policy</strong> Group<br />
<strong>Policy</strong> Counter Status<br />
<strong>Policy</strong> Counter Status<br />
Ericsson | 18-04-2012 | Page 55<br />
SAPC<br />
2011B<br />
Which policy to use <strong>for</strong><br />
the session<br />
Status of event in<br />
related to accumulation<br />
and balance
Network <strong>Control</strong> & User Experience<br />
How to differentiate<br />
Maximum Maximum<br />
Bandwidth Bandwidth<br />
per user<br />
Per User<br />
admission<br />
priority<br />
Guaranteed<br />
Bit Rate<br />
per Application<br />
Content<br />
Optimization<br />
Maximum<br />
Bandwidth<br />
per Application<br />
Throughput<br />
Throughput<br />
per User<br />
Minimum<br />
Bit Rate<br />
per User<br />
Content<br />
Caching<br />
LIMIT<br />
PRIORITIZE<br />
GUARANTEE<br />
ACCELERATE<br />
Ericsson | 18-04-2012 | Page 56<br />
When to differentiate<br />
Fair Usage <strong>Policy</strong> Time of the Day<br />
Location Terminal type<br />
Prime Service<br />
Flexibility in NETWORK POLICY HANDLING<br />
Updated<br />
Subscriber<br />
profile (Turbo)<br />
OTT Service Video Service
Monetizing mobile broadband<br />
Differentiated Services “Pay-as-you-go” schemes<br />
Add-on packages<br />
Ericsson | 18-04-2012 | Page 57<br />
Cross-services and<br />
promotions
Offering Examples with <strong>Integrated</strong><br />
policy and <strong>Charging</strong><br />
Allowing more advanced product offerings<br />
Ericsson | 18-04-2012 | Page 58
Cap Unlimited options<br />
Telecom Italia data plan<br />
+<br />
5<br />
€<br />
+<br />
5<br />
€<br />
Ericsson | 18-04-2012 | Page 59<br />
If the 10 GB volume limit is<br />
surpassed the QoS is<br />
downgraded to 64 Kbps<br />
Around 1 million subscribers<br />
have bought the CAP Unlimited<br />
option in 6 months!
References<br />
Ericsson Publications White Papers Spotlight on industry and technology on LTE-SAE<br />
http://www.ericsson.com<br />
“SAE and the Evolved Packet Core” - ISBN: 978-0-12-374826-3 Academic Press publications<br />
"LTE-Advanced Modem Design: Challenges and Perspectives“, Dongwoon Bai, Cheolhee Park,<br />
Jungwon Lee, Hoang Nguyen, Jaspreet Singh, Ankit Gupta, Zhouyue Pi, Taeyoon Kim, Chaiman Lim,<br />
Min-Goo Kim, Inyup Kang, IEEE Communications Magazine, Vol. 50, no. 2, February 2012<br />
"LTE-Advanced: An Operator Perspective", Prakash Bhat, Satoshi Nagata, Luis Campoy, Ignacio<br />
Berberana, Thomas Derham, Guangyi Liu, Xiaodong Shen, Pingping Zong, Jin Yang, IEEE<br />
Communications Magazine, Vol. 50, no. 2, February 2012<br />
"Relaying Operation in 3GPP LTE: Challenges and Solutions", Christian Hoymann, Wanshi Chen,<br />
Juan Montojo, Alexander Golitschek, Chrysostomos Koutsimanis, Xiaodong Shen, IEEE<br />
Communications Magazine, Vol. 50, no. 2, February 2012<br />
3GPP Technical Specifications<br />
[22.278] 3GPP TS 22.278 Service requirements <strong>for</strong> the Evolved Packet System (EPS)<br />
[36.420] 3GPP TS 36.420 Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2<br />
general aspects and principles<br />
[23.060] 3GPP TS 23.060 General Packet Radio Service (GPRS); Service description; Stage 2<br />
[23.203] 3GPP TS 23.203 <strong>Policy</strong> and charging control architecture<br />
[25.913] 3GPP TS 25.913 Requirements <strong>for</strong> Evolved UTRA (E-UTRA) and Evolved UTRAN (E-<br />
UTRAN)<br />
[29.219] 3GPP TS 29.219 <strong>Policy</strong> and <strong>Charging</strong> <strong>Control</strong>: Spending Limit Reporting over Sy reference<br />
point (Release 11)<br />
Ericsson | 18-04-2012 | Page 60
Q&A<br />
Ericsson | 18-04-2012 | Page 61
Ericsson | 18-04-2012 | Page 62
Change language