Sei sulla pagina 1di 4

NETMANIAS TECH-BLOG Please visit www.netmanias.

com to view more posts

LTE QoS (Part 3) - P2P Traffic Bandwidth


Control using the LTE QoS
October 25, 2013 | By Chris (tech@netmanias.com) | Netmanias Tech-Blog | www.netmanias.com

In the last two posts (Part 1, Part 2), we learned about LTE QoS. Now, we will show you an example of
controlling P2P traffic using the LTE QoS in the LTE network.

Let's say there is a network operator named "NMC Telecom", and it offers a service plan with the following
features:
 No bandwidth limitation for Internet usage
 Data rate limitation (512 Kbps for download, and 128 Kbps for upload) for P2P traffic such as
BitTorrent

To provide such features, NMC Telecom has an LTE QoS architecture built as follows. Below, you can see a UE,
an eNB, and an SAE-GW, a combination of S-GW and P-GW.

PDN
UE eNB SAE-GW (Internet)

2 DPI Rule SDF Bearer ID


P2P Traffic SDF 1 Bearer 5

3 SDF1 MBR (DL)


Policer=512Kb
Non- Non- SDF1
GBR GBR P2P traffic (SDF=1)
Bearer Bearer
Less than 512Kb
SDF2 DPI
Not
SDF=2 PF1 matched 1
Unlimited 5
7 UE-AMBR (DL) APN-AMBR (DL) SDF2 MBR (DL) 4
Scheduler=Unlimited Policer=Unlimited Policer=Unlimited
6
Filter Rule SDF Bearer ID
Default
Application

PF1 (*, UE IP, *, *, *) SDF 2 Bearer 5


Bearer Default Bearer
(Bearer (Bearer ID=5)
ID=5)
DPI Rule SDF Bearer ID
P2P Traffic SDF 1 Bearer 5 SDF1 MBR (UL)
Policer=128Kb
6
SDF1
P2P traffic (SDF=1)
Non- Non- Non-
GBR GBR GBR Less than 128Kb
Bearer Bearer Bearer DPI SDF2
PF1
Not
5 matched PF1 SDF=2
Unlimited 7 SDF2 MBR (UL) Unlimited
APN-AMBR (UL) 2 3 UE-AMBR (UL) 4 APN-AMBR (UL) Policer=Unlimited
1 Policer=Unlimited Scheduler=Unlimited Policer=Unlimited
Filter Rule SDF Bearer ID
Filter Rule Bearer ID PF1 (UE IP, *, *, *, *) SDF 2 Bearer 5
PF1 (UE IP, *, *, *, *) Bearer 5

Before we begin...

Deep Packet Inspection (DPI) function is required in order to detect P2P traffic from an LTE system (SAE-GW).
This DPI function allows the SAE-GW to look down as deep as the payload (L7), where applications (e.g. web,
voice, video, P2P, etc.) are located, in a packet. Just so you know, standalone equipment featuring only the DPI
function is already available in the market from Cisco SCE, Sandvine PTS, etc.
1
Netmanias Tech-Blog: LTE QoS (Part 3) - P2P Traffic Bandwidth Control using the LTE QoS

Downlink (DL) Traffic


1. When traffic from the Internet (PDN) arrives at an SAE-GW, DPI in the SAE-GW checks whether the
traffic is P2P traffic or not.
2. P2P traffic is mapped to Service Data Flow (SDF) = 1 and EPS Bearer ID = 5 (The SAE-GW receives
information about where (to which SDF and EPS bearer) to map the P2P traffic from PCRF when a
user attaches to the LTE network).
3. Since MBR (Maximum Bit Rate) for SDF = 1 is defined as 512 Kbps, the SAE-GW performs rate policing
for all the P2P traffic by applying MBR of 512 Kbps (any P2P traffic exceeding 512 Kbps is discarded).
4. Traffic found by the DPI to be not P2P is classified by a SDF filter (5-tuple based packet classifier).
Here, the filter is set as (Source IP, Destination IP, Protocol ID, Source Port, Destination Port) = (*, UE
IP, *, *, *), where * means any value (i.e. wildcard). So, all the traffic heading to its own destination,
a particular IP address of the UE, is matched by this rule, consequently mapping all the non-P2P
traffic to SDF = 2, EPS Bearer ID = 5 (The SAE-GW also receives information about this SDF filter from
the PCRF when a user attaches to the LTE network.).
5. Since MBR (Maximum Bit Rate) for SDF = 2 is defined as "Unlimited", no bandwidth control limitation
is applied to all the non-P2P Internet traffic.
6. Because of "APN-AMBR = Unlimited" (APN-AMBR: a QoS parameter that controls the bandwidth of
the traffic sent from the same APN (i.e. Internet in this example) and received at non-GBR EPS
bearers), there is no bandwidth limitation for SDF = 1 and SDF = 2. These SDFs are mapped to EPS
Bearer ID = 5, and delivered to the eNB through the GTP tunnels. Through the steps 1 to 6 explained
so far, the bandwidth for P2P traffic is limited to 512 Kbps, whereas the bandwidth of other Internet
traffic is not limited before the traffic was delivered to the eNB.
7. For the traffic delivered through EPS Bearer ID = 5 to the eNB, based on the eNB's parameter set as
"UE-AMBR = Unlimited" (UE-AMBR: a QoS parameter that controls the bandwidth of all the traffic
heading to the UE and received at non-GBR EPS bearers), the bandwidth of the traffic is not limited.
The eNB tries to deliver the traffic to the UE to the fullest extent allowed by the available resources
over the radio link.

Uplink (UL) Traffic


1. When there is traffic from an application in a UE, the UE maps the traffic to EPS Bearer ID = 5 using a
TFT filter (The UE cannot distinguish SDFs and only knows to which EPS bearer to send which
application. SDFs can be distinguished by SAE-GW (P-GW) only). The UE receives information about
the TFT filter from the LTE network when it attaches to the network.
2. For all the traffic heading to an APN (Internet) in all non-GBR EPS bearers (i.e. the one default non-
GBR EPS bearer herein), the bandwidth is controlled by APN-AMBR in the UE. However, since the
parameter is set as "APN-AMBR = Unlimited", the UE sends all the traffic, P2P or not, using the
maximum available bandwidth.
3. The UE traffic is delivered to the eNB, which control the uplink bandwidth of the traffic in all the non-
GBR EPS bearers sent by the UE based on UE-AMBR. To be accurate, it is wrong to say the UE sends
the traffic using the maximum bandwidth and the eNB controls UE-AMBR. Since the eNB gives the UE
transmission opportunities based on UE-AMBR (by allocating Resource Block (RB) over the radio link),
you should say "The bandwidth of the traffic to be sent over the radio link by the UE is controlled

2
Netmanias Tech-Blog: LTE QoS (Part 3) - P2P Traffic Bandwidth Control using the LTE QoS

based on UE-AMBR by the eNB". Since the parameter is set as "UE-AMBR = Unlimited", the UE will
try to deliver the traffic to the eNB to the fullest extent allowed without any bandwidth limitation.
4. When the SAE-GW receives traffic from the eNB through EPS Bearer ID = 5, it controls the bandwidth
of all the traffic in non-GBR EPS bearers that is heading to the same APN (Internet in this example) by
using APN-AMBR. Since the parameter is set as "APN-AMBR = Unlimited", there is no limitation on
bandwidth here.
5. Then, the DPI in the SAE-GW distinguishes P2P traffic and non-P2P traffic (So, it's always the SAE-GW
that distinguishes P2P traffic, whether in uplink or downlink.).
6. P2P traffic is defined as SDF = 1, and thus its bandwidth is limited to 128 Kbps as set by MBR = 128
Kbps.
7. All other Internet traffic are defined as SDF = 2, and they are delivered to the Internet without
bandwidth limitation as set by "MBR = Unlimited".

This way, we can divide the traffic that travels through one EPS bearer into P2P and other Internet traffic, and
then control the uplink/downlink bandwidth of P2P traffic only.

3
Netmanias Research and Consulting Scope

99 00 01 02 03 04 05 06 07 08 09 10 11 12 13

eMBMS/Mobile IPTV
CDN/Mobile CDN
Transparent Caching
BSS/OSS
Services Cable TPS
Voice/Video Quality
IMS
Policy Control/PCRF
IPTV/TPS
LTE

Mobile Mobile WiMAX


Network Carrier WiFi
LTE Backaul
Data Center Migration
Carrier Ethernet
FTTH
Wireline
Data Center
Network
Metro Ethernet
MPLS
IP Routing

Visit http://www.netmanias.com to view and download more technical documents.

We design the future


Consulting
Carrier Ethernet

Transparent

We design the future protocols


IP/MPLS

Caching

Analysis
Wi-Fi
CDN

Concept Design
We design the future LTE IMS DRM
Infrastructure Services
POC

Networks
eMBMS

Training

Analyze trends, technologies and market


Report
Technical documents
Blog
One-Shot gallery
Future

About NMC Consulting Group (www.netmanias.com)


NMC Consulting Group is an advanced and professional network consulting company, specializing in IP network areas (e.g., FTTH, Metro Ethernet and IP/MPLS), service
areas (e.g., IPTV, IMS and CDN), and wireless network areas (e.g., Mobile WiMAX, LTE and Wi-Fi) since 2002.
Copyright © 2002-2013 NMC Consulting Group. All rights reserved.

Potrebbero piacerti anche