3GTPL IP Transport QOS

3GTPL IP Transport QOS
1 © Nokia Siemens Networks RN30036EN40GLA0

Objectives
After this module, the student will be able to:

• Identify supported QOS features in the actual release
• Explain Scheduling Mechanisms supported in RAN NEs
• Explain how to plan and configure QOS
• Discuss the possible configurations through an example/exercise

Content
• QOS Introduction
• Scheduling in cRNC and WBTS
• Scheduling in mcRNC
• QoS with IPsec
• QOS Parameters Configuration
• QOS Planning Example/Exercise

IP Transport QOS
• QoS with IPsec

Introduction to QoS
The planned QoS scenario should reflect the marketing and sales strategy of the
network operator. Thus there is large number of different possible QoS scenarios.
QOS QOS QOS Network

Features and
Strategy Attributes Enforcing Configuration
The QoS scenario is formed with combination of different QoS attributes and QoS enforcing
mechanisms.
The main QoS attributes used in mobile networks are:
• Maximum bit rate for the connection
• Minimum bit rate for the connection
• Priority of the connection relative to other connections
• Maximum delay (for RT streaming)
• Monthly quota
• Some operators can also differentiate subscriptions by different device offering (high-low category UE
types etc.)
These QoS attributes are enforced in the radio network with combinations of multiple features
and mechanisms.

QoS Enforcement functional split in RAN and CN
•Flexi NG enforces policies defined in PCRF (Policy and Charging Rules
Function)
•QoS priority of the user/service is delivered from CN to RAN via RAB QoS
parameters
•RAN enforces further the defined policy via RNC and node B congestion
handling and resource management and allocations (CAC)
•Priority can be updated on the fly via RAB reconfiguration
CN PCS 5000
Congestion handling and RA
resource management
N HLR
RNC
Subscriber and service Content &
management Connectivi
Iub Iu y
Flexi Internet+
Intranet
BTS
SGS
N the
QoS parameters deliver
user/service priority to RAN Flexi NG
DPI
QoS Enforcement in RAN
• Throughput cannot exceed MBR values
• GBR and NBR values are fulfilled in SPI order
• The excess capacity after fulfilling GBR and NBR is shared
according to SPI specific scheduling weights (higher priority gets more)
• QoS aware HSPA • HSPA QoS

scheduling based parameter mapping in
on SPI RAB setup and
modification
• GBR for real time
applications • AC for Real time
traffic
• NBR for non real
time applications • Maximum bit rate
control
• Resource sharing
NodeB between R99 and
RNC HSPA
Bronze Silver Gold
•Transport fully aligned with radio

interface

QOS Differentiation Options
Subscribers Services
Differentiation Differentiation
QoS 5 Operator VoIP
QoS 5
QoS 4 Audio/video
QoS 4 Gold stream
QoS 3
QoS 3
QoS 2 Silver QoS 2
QoS 1 Bronze QoS 1
QoS 0 QoS 0 P2P
• Subscribers based QoS differentiation can be done with three

subscriber QoS levels and one addition QoS class for users that have
exceeded the quota.
• The service level QoS differentiation would include a core network
initiated QoS modification which would be triggered based on service
detection in core network.
• Also combined scenario can be implemented.
Subscribers-based Differentiation
Cell congestion
Subscribers
Mbit/s
in the same cell Premium service
for Gold subscribers
QoS 5 21
QoS 4 Gold
QoS 3
QoS 2 Silver
Mbit/s
QoS 1 Bronze Service degrade
for Silver and Bronze
QoS 0 21
Increase service QoS differentiation is dynamic, cell specific

experience of – traffic policing only during congestion
priority users • Improved service experience for Gold subscribers
• No changes necessarily needed in existing contracts

Application-based Differentiation
Example: “Silver” subscriber with max 2 Mbps nominal speed:
QoS 5 Operator VoIP Mbit/s
QoS 4 Audio/video 21
stream
Streaming – guaranteed bit
QoS 3 rate 2 Mbps
QoS 2
Mbit/s
QoS 1
QoS 0 21
P2P P2P traffic – lowest priority
Increase service Examples: • Prioritize operator preferred services

experience as per • Prioritize mobile TV quality assurance
• Adjust speed while maintaining user experience
selected service

Mapping of NRT services and/or subscribers
QoS parameters from CN: (TC+THP+ARP)
Scheduling weights in NodeB
SPI mapping table in Transport and RNC
RAN
NodeB RNC
SPI SchWeight IUB SPI SPI
Priority
Interactive THP1 ARP1 11

11 35 Transport Interactive THP1 ARP2 10
CN
connections
10 30 queues Interactive THP1 ARP3 9 HLR
9 25 rt-DCH
8
Paramete
Interactive THP2 ARP1 rs
nrt-DCH
8 20 ATM
or Interactive THP2 ARP2 7 TC
7 15 IP
transport Rt-HSDPA (streaming) Interactive THP2 ARP3 6 THP
6 10 connection Nrt- HSDPA (GOLD) SPI ARP
Nrt- HSDPA (SILVER) Interactive THP3 ARP1 5 GBR
5 9 Nrt- HSDPA (BRONZE)
4 8
3 6
2 5 HSPA Congestion Control BckgroundARP1 2
1 2 Background ARP2 1
0 1 Background ARP3 0
6 © Nokia Siemens Networks / © Nokia Siemens Networks /
Bronze Silver Gold

QOS Tag at IP Layer
IP – Packet (IP v4)

DSCP +
Header Total Identi- Fragment Fragment Time to Header
Version CU Protocol
Length Length fication Flag Offset live Checksum
(4 Bit) (6 + (1 Byte)
(4 Bit) (2 Byte) (2 Byte) (3 Bit) (13 Bit) (1 Byte) (2 Byte)
2 Bit)
Payload
Source Destination
Options (maximum theoretical 65535 Bytes,
Address Address
(0-40 Byte) Practical at least 576 Byte, typical 1500 (Ethernet standard)
(4 Byte) (4 Byte)
dependent on max. MTU size of Data link layer)
Packet size at least 20 Byte
DiffServ Code Point value as defined in RFC2474.

Old name of this field was TOS (Type Of Service).

QOS Tag at Ethernet Layer
Ethernet Frame (with VLAN tag)

46 to
7 Bytes 1 B. 6 Byte. 6 Byte 2 B. 2 B. 2 B. 4 bytes 12 bytes
1500 Bytes
Dest. Source Frame Interframe
Preamble SD TPID TCI Type Data Check
Address Address Sequence Gap
TPID (Ether type) TCI

Total Ethernet Tag protocol identifier Tag Control Information
Frame Size
68...1522 Byte
Defines type of 802.1q tag 3 1 12
(without Preamble,
SD and Interframe Gap) VLAN ID
User priority CFI (Cannonical
format identifier) (n <= 4094)
Additional bytes:
In a VLAN-tagged frame 4 bytes are added between the Type-Field and the Data-
Field.

IP QoS Mechanisms
 Classification: Each class-oriented QoS mechanism has to support some type of

classification (access lists, route maps, class maps, etc.)
 Marking: Used to mark (color) packets based on classification and/or metering.
 Metering: Some mechanisms measure the rate of traffic to enforce a certain policy
(e.g. rate limiting, shaping, scheduling, etc.).
 Policing: it is the QoS component that limits incoming traffic flow to a configured bit
rate (excess traffic is dropped).
 Shaping: it is the QoS feature component that regulates outgoing traffic flow to a
configured bit rate (excess traffic is delayed).
 Congestion Management: Each interface must have a queuing mechanism to

prioritize transmission of packets (e.g SPQ, WRR and WFQ).
 Dropping: Congestion Avoidance mechanisms are used to drop packets (e.g.

random early detection, RED)

QoS and Overbooking of data traffic
Different applications/subscribers are treated differently and monitored
separately
QoS profile 5
QoS profile 4
QoS profile 3
Best Effort traffic
QoS profile 2
QoS profile 1
QoS profile 0
Best effort QoS differentiation
In case of congestion packets are In case of congestion packets are

randomly discarded. This is discarded on priority base.
limiting the overbooking factor
that can be applied. Higher overbooking factors can
be applied.
Congestion has equally impacts
on all users and all data services.

Guaranteed traffic – not affected by overbooking
Congestion control
and QoS
enforcement
Packet
Network
RNC Traffic where

overbooking
applies
CAC Guaranteed Bw
BTS#1
Non-Guaranteed Bw
CAC Guaranteed Bw CAC Guaranteed Bw

BTS#2
Non-Guaranteed Bw
Non-Guaranteed Bw
CAC Guaranteed Bw
BTS#3
Non-Guaranteed Bw
Ethernet interface rate

Summary
– QOS Attributes are negotiated between RAN and CN

– QOS differentiation can be done per users and/or service
– Overbooking is an important aspect in QOS planning

IP Transport QOS
• QoS with Ipsec

Scheduling in cRNC
• The logical scheduling architecture is composed of two levels:

– One level controlling the egress traffic for each IP based route
separately
– One level handling IP traffic for the whole IP interface
Available only for Iub

IP Interface Scheduler
• cRNC supports a combination of Strict Priority scheduler (SP) and Weighted Fair
Queuing scheduler (WFQ)
– EF queue shall be handled with a strict priority scheme and no weight
is associated
– AF1, AF2, AF3, AF4, and BE queues are processed with WFQ

Iub Transport QoS
Queue weights in the Default PHB Profile in the RNC
PHB name Queue Queue Queue Queue Min Thd (%) Max Max Exp. VLAN
schedule length weight priority Thd (%) Drop Weight priority
(%)
BE WFQ 500 1 NRT 75 100 10 0 0
AF1 WFQ 300 4 NRT 75 100 10 0 1
AF2 WFQ 300 10 NRT 75 100 10 0 3
AF3 WFQ 300 25 NRT 75 100 10 0 4
AF4 WFQ 100 60 RT 100 100 0 0 5
EF SP 100 N/A RT 100 100 0 0 6
Default Profile ID = 0 Need to be adjusted

per network
The p-bit 6 is
sometimes used for
control
IP Based Route Scheduler
• The rate limiting is done using Internal Flow Control (IFC)

– Only available for Iub
– IFC can be applied to AF1, AF2, AF3, AF4, and BE traffic
– cRNC supports a combination of Strict Priority scheduler (SP) and
Weighted Fair Queuing scheduler (WFQ)
By default the queues

Q1, Q2 and Q6 are used
without Iub transport
QoS feature.
Q7 is used for Iur traffic.

IP Based Route Scheduler
The IP based route scheduling in the cRNC is always virtual.
Queue weight defines the share of the capacity that the queue
gets from the capacity left over from the queue Q1.
If any of the queues is empty, the spare capacity is shared

among the remaining queues according to their weights. So
the average capacity for a queue can be calculated as:
WFQ rule:
QueueAverageRate  AvailableCapacity  QueueWeigh t /  QueueWeigh t
ActiveQueues

WBTS Scheduling
Scheduling in WBTS is implemented as for cRNC Interface

Scheduler.
Queues weights and

traffic mapping are
defined in WBTS
Manager

Summary
– In cRNC we have Interface Scheduler and IP Based Route Scheduler

– IPBR Scheduling in cRNC is always Virtual
– WBTS Scheduling is very similar to RNC

IP Transport QOS
• QoS with Ipsec

Interface Scheduler
• There is no flow control at interface level, no rate limiting
• Exponential Random Early Detection (E-RED) queue management is supported in

the cRNC and in the mcRNC in the interface level to avoid TCP global
synchronization

Egress classification in mcRNC NEVER change PIP6+7 mappings
or put additional traffic to those
– impact on RNC internal messaging!
DSCP = 63
PIP = 7 Egress Queue EF

PIP = 6
DSCP PIP = 5 Egress Queue AF4
DSCP to PIP = 4 Egress Queue AF3
PIP PIP = 3
Egress Queue AF2
Mapping PIP = 2
PIP = 1 Egress Queue AF1
PIP = 0
Egress Queue BE
DSCP = 0
Configured Static
via ACL rules mapping
• Traffic classification is purely based on DSCP

• Egress classification maps traffic to Internal Packet Priority (PIP)
• PIP is a numerical representation of PHB concept
• PIPs 0..7 are statically allocated to physical egress queues
– PIPs 5..7 map to same (highest priority) queue
• Default mappings
DSCP 48,46 34,36,38 26,28,30 18,20,22 10,12,14 Any
PIP 5 4 3 2 1 0

Egress Interface scheduling
Physical Network Interface Scheduler
Egress Queue EF (PIP=5,6,7) Strict Priority

Egress Queue AF4 (PIP = 4) w1
w2
Egress Queue AF3 (PIP = 3)
w3
WRR
Egress Queue BE (PIP = 0)
• Static scheduler configuration

• 1 Strict Priority (SP) queue
• 5 Weighted Round Robin (WRR) queues
• Dynamic scheduler configuration via Queue Sets, comprising
• ID (range: 0..5, used to map PIP to transmission queue)
• Weight (range: 1..8, not supported for Queue 0)
• Queue length (range: 1..1024 kbytes)
• It is recommended to apply the default Queue Set „rncdefault“ to all interfaces
Name EF AF4 AF3 AF2 AF1 BE
ID 5 4 3 2 1 0
Weight - 8 4 1 1 1
Length 20k 50k 50k 50k 50k 100k
IP Based Route Scheduler in mcRNC
• The IP based route scheduling in the cRNC is always virtual

• In the mcRNC there are two alternatives for scheduling in the mcRNC at IP
based route level:
1. Virtual Scheduling means the system is not providing dedicated

buffers for each of the queues of each IP based route
▪ Instead packets are stored in the physical (interface) queues directly and
individual queues are represented by byte/packet counters
▪ IFC event triggering queue management shall only be provided in case of
virtual scheduling
2. Real Scheduling means the system is providing dedicated buffers for
each of the queues of each IP based route
▪ This allows more accurate scheduling/shaping than the virtual scheduling
approach at the cost of memory and processing power
▪ E-RED queue management that drops packets from the queue in case of
congestion is used

Virtual Queueing – based on E-RED
IP based route using E-RED Physical Network Interface Scheduler
Packet Packet
Packet User Plane
Counters EF Queue Strict Priority

Strict Priority
EF
Decrease
counters at AF4 Packet AF4 Queue
97% route AF3 Packet
bitrate
WFQ AF2
AF3 Queue WRR
AF1
BE
AF2 Queue
AF1 Queue
E-RED
Algorithm BE Queue
• Virtual Queueing counts bytes in virtual queues per IP based route

• No dedicated (physical) scheduling per IP based route
• Counters are decreased according to 1SP + 5WFQ scheme,
but only according to 97% of the configured route bandwidth
– Leading to low queueing delay at the bottleneck (assuming a static bandwidth limit)
• E-RED packet dropping mode
• When counter indicates (virtual) queue low threshold is exceeded, packets are dropped according to
E-RED algorithm per IP based route
• WFQ weights and E-RED parameters can be configured via PHB profile (IPHB)
• Supported for all logical interfaces (user plane)

Virtual Queueing – based on IFC
IP based route using IFC Physical Network Interface Scheduler
Packet Packet
Packet RLC/MAC
Counters Packet EF Queue Strict Priority

Strict Priority
EF
Decrease AF4 Queue
counters at
97% route
AF4 Packet
AF3
bitrate
WFQ AF2 Packet AF3 Queue WRR
AF1
BE
AF2 Queue
AF1 Queue
E-RED
Algorithm BE Queue
• Internal Flow Control (IFC) mode

• IFC mode supported for IP based routes on Iub interface only (due to relation to RLC/MAC)
• When counter indicates (virtual) queue low threshold is exceeded, IFC message is sent based on an
E-RED algorithm to RLC/MAC scheduler
• Instead of dropping packets, RLC/MAC scheduler reduces transmission rate
• Reduces Iub packet delay, as packet drop (and thus retransmissions of end user packets) is avoided
• E-RED algorithm
• WFQ weights and E-RED parameters can be configured via PHB profile (IPHB)
• Although no real discard is performed, E-RED alike algorithm is used to determine the level of user
plane transmission rate reduction needed

Real Queueing Physical Network Interface Scheduler
IP based route
EF Queue Strict Priority

EF Queue Strict Priority
Packet AF4 Queue
AF3 Queue AF4 Queue
Packet AF2 Queue WFQ Packet
AF1 Queue AF3 Queue
BE Queue WRR
AF2 Queue
E-RED
Dropper Packet AF1 Queue
BE Queue
2nd Level 1st Level

Queues Queues
• Real Queueing provides dedicated physical queues (buffers) per IP based route
• Adds second level of scheduling
• Scheduler type: 1SP + 5WFQ
• Supported for all logical interfaces (user plane)
• No significant performance penalty compared to Virtual Queueing, yet higher precision achieved
• Queue management
• Excess packets are discarded by E-RED algorithm
• Queues can be configured via PHB profile (IPHB), e.g. queue length, weight, and thresholds

IP based route scheduling of Iur traffic
D-RNC combines Iur
(from S-RNC) and own Iub
traffic towards the Node B
Iub Iur
RNC 1 RNC 2
Iub (D-RNC role) Iur (S-RNC role)
• IPA RNC IP based route scheduler requires a dedicated queue for Iur
• Queue weight parameter „ratio“ defines Iub / Iur share
• mcRNC supports queueing Iur traffic in the usual queues
• Simpler and more consistent resource sharing via common DSCP based scheduling
Iub Iub
Iur
Iur
IPA-RNC IP based route mcRNC IP based route

Summary
– In mcRNC we have Interface Scheduling

– IFC can be provided by Virtual or Real Scheduling
– Virtual Queuing can be based on E-RED or IFC
– Compared to cRNC we don't have a separate queue for Iur traffic

IP Transport QOS
• QoS with Ipsec

DSCP
• Differentiated Services Code Point (DSCP) is a mechanism for classifying and

managing network traffic and providing quality of service (QoS).
• In tunnel mode, when encryption is enabled, the DSCP field carried in the inner IP
header cannot be inspected by the external devices. In order to avoid this
problem, the DCSP is copied from the inner IP header to the outer IP header.
Thus QoS can be applied by the network based on this outer header.
DSCP DSCP
IP Header ESP Header IV Original IP Header UDP UDP Payload Padding ESP ESP
Header Trailer Authentication

Anti-replay window
Anti-replay window protects the system against the replay by an attacker of a session packets,
potentially causing a malfunction.
The anti-replay window mechanism is based on the checking the sequence number of the
received packets:
•If the packet has been already received or if it occurs in the past (outside the rear end of the
window) the packet is discarded
•If the packet falls within the window and it has not been received already, the packet is
accepted
•If the packet is received ahead of the window, the packet is accepted and the window will slide
forward.
A limitation of the anti-replay window is that it requires the packets to arrive roughly in order. If the
packets suffer sufficiently high reordering when traversing the network, the lower priority packets
(which arrive later) will be dropped by the receiver since they miss the window rear limit.
The tolerable level of reordering depends on the size of the anti-replay window. This situation
might happen when the packets traverse schedulers with multiple queues for different QoS classes
and there is some congestion. It should be noted that within a given QoS class, packet reordering
should be a rare case.
Window shift
Anti –replay sliding window
Anti –replay window size
69 68 3 4 64 65 66 67 is configurable by the
parameter
Window size 64
Anti-replay drop 
antiReplayWindowSiz
e

Connection Admission Control (CAC)
CAC is a QoS mechanism preventing services

establishment in case of no transport resources
are available
IP CAC is applied for all user plane, control plane and management plane connections
As soon as IPsec is enabled, the overhead introduced by IPsec encapsulation is taken into account
in the evaluation of the IP CAC algorithms
The overhead is introduced by means of overhead factors which scale the bit rate
The IP CAC is implemented so that CAC sums up all transport bearers bit rates of individual IP
connections and compares that sum to the total available bit rate for particular link
IP bit rate of connection = MAX_Bitrate* 0.2 + AVE_Bitrate* 0.8

While:
VPN bit rate of connection = IP bit rate of connection * bearer specific overhead factor
Where:
bearer specific overhead factor= (IPsec overhead + average bearer IP packet size) / average
bearer IP packet size
IP Interface Committed Bit Rate >= Σ VPN bit rate of connection + IP Interface Signalling
Committed Bit Rate + IP Interface DCN Committed Bit Rate

IP Transport QOS
• QoS with Ipsec

QOS Features
Most important features to be configured for QOS:

• Iub Transport QOS – for packets marking and prioritisation in
RNC and WBTS schedulers and backhaul packet network
• HSDPA Congestion Control – for users prioritisation
according di SPI Weights, in case of transport congestion
HSDPA CC parameters are set at WBTS object level.

QOS Objects in WBTS and RNC
QSet
Note that most of the mcRNC objects TQM
are the same than in cRNC. IPQM for Iu
Iur
Routers QOS settings are usually IDSP
provided by operators. IPHB
Vlan PCP – DSCP mappping
WBTS
IPNB for NBAP
IPBR
QOS
L2SWI
Router
Packet
Network mcRNC
Flexi Rel.2

QoS Settings Overview
Each network element in the network has its own QOS marking capabilities.
RNC Router Switch

-Traffic type to DSCP marking -DSCP marking kept -VLAN p-bit marking kept NG-SDH
-DSCP to PHB mapping
-PHB to p-bit mapping
-VLAN p-bit marking kept
-per site VLAN termination
-no shaping or policing
-Queuing and schedulig
/ Dark
(C-VLAN) Fiber
-no shaping or policing Assumption:
-- Queuing and scheduling Transparent to
QoS
FPR FTM
-2xSP+2xWFQ scheduling -Traffic type to DSCP marking
-p-bit to queue mapping -DSCP to PHB mapping
-Tail drop regardless of the -PHB to p-bit mapping
PCP when buffer gets full -SP+5xWFQ Scheduling
-WFQ weights are configurable

mcRNC - QSet
• QSET object in mcRNC contains weights settings for

scheduling at interface level.
• It is recommended to not modify them.
Queue Id in RNC datafill refers to Internal Packet Priority (PIP).

mcRNC - TQM
• TQM is the most important

object in RNC for Iub Transport
QOS setting.
• Mapping between SPI settings
in WBTS and TQM allows to
get the desired DSCP marking
for a specific traffic class.
......

mcRNC - IPQM
• IPQM object in mcRNC allows QOS marking settings for Iu

interface.

mcRNC - Iur
• Iur object contains parameters for user plane marking.
DSCP High Priority -> Conversational, R99 Streaming

DSCP Medium Priority -> NRT-DCH R99
DSCP Low Priority -> NRT-HSPA
mapping between PHB and DSCP (IDSP)
• IDSP defines the mapping between PHB and DSCP values.

IPHB
• IPHB contains PHB parameters. It's suggested to keep
default values.

VLAN P-Bit – DSCP mapping
• Mapping between VLAN Priorities and DSCP in mcRNC is

done for L2 packets marking management.

mcRNC – WBTS and IPNB
• WBTS Object in RNC is used to enable/disable HSDPA

Congestion Control feature and to set basic Iub QOS
marking settings with following parameters:
 DSCPHigh - CCCH, HS FACH/RACH (signalling), DCCH on R99 DCH
(SRB), CS R99 DCH, PS Streaming R99 DCH
 DSCPLow – PS I/B HSPA traffic (HS-DSCH and E-DCH), HS
FACH/RACH (user data)
 DSCPMedDCH – PS I/B on R99 DCH
 DSCPMedHSPA – PS Streaming on HS-DSCH and E-DCH (HSPA)
 HSDPACCEnabled
 HSDPAULCToDSCP
 HSUPADLCToDSCP
• IPNB Object in RNC contains NBAP DSCP parameter.

mcRNC – IPBR
• In IP Based Route parameters, it's possible to set

DSCP marking related to the feature RAN1886
Efficient Transport for Small IP Packets.
• Packets are multiplexed with same DSCP value.
• udpMuxDSCP defines the DSCP value for IP

multiplexing.

FTM/AXC - QOS
QOS Object in FTM contains all the QOS related parameters for
marking and scheduling:
•PHB Weights -
assuredForwardingClas
s1 ....
•Traffic Types Marking

– with association
between Traffic Type,
DSCP, VLAN Priority,
PHB.
.....
FTM/AXC – L2SWI
L2SWI object is used to configure QOS Aware Ethernet

Switching feature in the transport module:
•Priority Queues to
PCP mapping
•Priority Queues
Weights
•Priority Queues to
DSCP mapping

Flexi Packet Radio
In case of Flexi Packet Radio used between WBTSes and RNC,
additional mapping is required for traffic scheduling management.
WBTS
Packet
Router
Network mcRNC
WBTS

Flexi Packet Radio
• With regards to the Classes of Service FPR supports four queues
(CoSs) with priority from 3 (highest) to 0 (lowest). The supported
configurable scheduling algorithms are:
• 4-SP
• 4-WFQ with configurable weights
• 2-SP + 2-WFQ with configurable weights (default)
• 1-SP + 3-WFQ with configurable weights
• Configuration which better matches WBTS Scheduling is 1-SP + 3-

WFQ, then traffic should be mapped accordingly.
• In case of Flexi Packet Hub connected to FPR, then 2-SP + 2-WFQ

configuration matches.

IP Transport QOS
• QoS with Ipsec

Customer Input
The most important information we need for QOS planning

come from preliminary discussions with the customer.
Network topology and how packets are marked and treated by

backhaul network elements, determine settings for
scheduling and packets marking.
Commercial strategy for users and services differentiation,

determine how to set HSDPA Congestion Control feature for
Iub in terms of CC Policy and thresholds settings based on
transport network capacity.

Network Topology
Chained WBTSes with VLAN Traffic Separation
QOS Aware Ethernet Switching
VLAN-100, 101, ...
depending on mcRNC
VLAN-10 U/C
Step.
VLAN-20 U/C
Same VLAN for all
VLAN-3 OAM WBTSes
MultiLayer
Routers
VLAN-4 SYNC
Switch
WBTS-20 Packet mcRNC

Fiber Network
Aggregation
UNI link
Fiber
VLAN-10 U/C
VLAN-3 OAM
WBTS-10
VLAN-4 SYNC

Commercial Strategy
We assume following QOS profile to be implemented with Gold-
Silver users differentiation:
QOS Table-1
User Traffic Type SPI WEIGHT GBR/NBR
Gold Interactive THP-2 ARP-1/2/3 8 4 0
Silver Background ARP3 0 1 0
Question1 – how do we configure HSDPA CC parameters

Weight and ccPolicy for SPI-8 and SPI-0 ?
ID Weight ccPolicy
15 0 0 (Control all data)
 Control All Data 13
12
0
1
0 (Control all data)
0 (Control all data)
 Control Data over GBR 11 8 0 (Control all data)
 OFF 9 1 0 (Control all data)
8
0
HSDPA CC
HSDPA CC considerations:
Question-2
DELAY – which WBTS requires more attention for minDelay
and maxDelay thresholds?
• CC Thresholds tuning, if really necessary, requires some

testing and monitoring sessions to see delay and loss
messages amount.
Question-3
In which object do we set HSDPA CC Thresholds?
Question-4
Which counters family indicates delay and loss msgs?
Transport QOS Strategy
This Operator wants to use separate DSCP values for CS

traffic, Gold User traffic, Silver User traffic, Signalling and
Control traffic:
Traffic types DSCP
applicable Value
Signalling and
Control 46
Voice Traffic
According to attached
46
Technical Note, if we want to
Gold NRT DCH with
SPI=8 34
get users differentiation for
Silver NRT DCH with HSDPA by usage of HSDPA
SPI=0 0 CC feature, these should use
Gold NRT HSPA
with SPI=8 0
same DSCP value.
Silver NRT HSPA
with SPI=8 0
All others
0
HSPA (flow) control
messages 34

TQM in RNC
Question-5 How do we set TQM object in RNC according to the

table of traffic mapping choosen by the Operator?
Object
Traffic types DSCP
Class Abbreviated Name applicable Value
TQM PchFachRachToDSCP CCCH

Traffic types DSCP
applicable Value DCCH
TQM SRBToDSCP
Signalling and RT DCH (e.g. AMR)
Control 46
TQM CSTrafficToDSCP
Voice Traffic
46 DCHQoSPri8 NRT DCH with
TQM ToDSCP SPI=8
Gold NRT DCH with
SPI=8 34 DCHQoSPri0 NRT DCH with
TQM ToDSCP SPI=0
Silver NRT DCH with
SPI=0 0 HSPAQoSPri HS-DSCH traffic with
8 SPI=8
Gold NRT HSPA TQM ToDSCP
with SPI=8 0
HSPAQoSPri HS-DSCH traffic with
Silver NRT HSPA 0 SPI=0
with SPI=8 0 TQM ToDSCP
All others HSPA (flow) control

0 WBTS HSDPAULCToDSCP messages
HSPA (flow) control HSPA (flow) control
messages 34 HSUPADLCToDSCP messages
Iub NBAP Signalling
IPNB NBAPDSCP

Scheduling in RNC
We leave Scheduling parameters in RNC with default values.
IP Based Route parameter IFC will be set OFF in case of cRNC

or E-RED in case of mcRNC (only for HSPA).
DSCP PHB P-bit Scheduling Weight
46 EF 6 SP N/A
34 AF4 5 WFQ 60
26 ,28 ,30 AF3 4 WFQ 25
18, 20, 22 AF2 3 WFQ 10
10, 12, 14 AF1 1 WFQ 4
All Other
DSCP
values BE 0 WFQ 1
In this case only EF, AF4 and BE receive traffic.

Scheduling in WBTS
WBTS Scheduling in case of VLAN Differentiation can be done

at VLAN level.
In this case we consider to have trafficPathShaping=PATH

setting to shape bandwidth of each VLAN-id to its SIR.

QOS Setting in FTM
FTM QOS DSCP and P-Bit mapping is left as default.

Switching in WBTS
Traffic from WBTS-10 is switched in WBTS-20 keeping in

account VLAN Differentiation settings.
M-Plane and S-Plane have their own VLAN-id shared between
the two WBTSes.
U/C Planes have dedicated VLAN-id for each WBTS.
Question-6 How do we make U/C packets from WBTS-10 are

forwarded through ethernet port 1 of WBTS-20 ?
VLAN-20
BTS-20
VLAN-10
BTS-10

QOS Ethernet Switching in WBTS
Ethernet Scheduling in
WBTS is performed in
egress ethernet port by
mapping of DSCP or P-Bit
values to the 4 or 6
available queues.
In this case we are

considering to have FTIB
in WBTS, then 4 queues
available.

QOS Ethernet Switching in WBTS
Question-7 How do we map DSCP values to switch queues in

L2SWI object? Is the Default mapping below

3GTPL IP Transport QOS

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

3GTPL IP Transport QOS

Enviado por

Direitos autorais:

Formatos disponíveis

3GTPL IP Transport QOS

1 © Nokia Siemens Networks RN30036EN40GLA0

After this module, the student will be able to:

2 © Nokia Siemens Networks RN30036EN40GLA0

3 © Nokia Siemens Networks RN30036EN40GLA0

4 © Nokia Siemens Networks RN30036EN40GLA0

QOS QOS QOS Network

5 © Nokia Siemens Networks RN30036EN40GLA0

• QoS aware HSPA • HSPA QoS

Bronze Silver Gold

•Transport fully aligned with radio

7 © Nokia Siemens Networks RN30036EN40GLA0

QoS 2 Silver QoS 2

QoS 1 Bronze QoS 1

QoS 0 QoS 0 P2P

• Subscribers based QoS differentiation can be done with three

Increase service QoS differentiation is dynamic, cell specific

9 © Nokia Siemens Networks RN30036EN40GLA0

QoS 5 Operator VoIP Mbit/s

Increase service Examples: • Prioritize operator preferred services

10 © Nokia Siemens Networks RN30036EN40GLA0

Interactive THP1 ARP1 11

Bronze Silver Gold

IP – Packet (IP v4)

Packet size at least 20 Byte

DiffServ Code Point value as defined in RFC2474.

12 © Nokia Siemens Networks RN30036EN40GLA0

Ethernet Frame (with VLAN tag)

TPID (Ether type) TCI

13 © Nokia Siemens Networks RN30036EN40GLA0

 Classification: Each class-oriented QoS mechanism has to support some type of

 Marking: Used to mark (color) packets based on classification and/or metering.

 Congestion Management: Each interface must have a queuing mechanism to

 Dropping: Congestion Avoidance mechanisms are used to drop packets (e.g.

14 © Nokia Siemens Networks RN30036EN40GLA0

In case of congestion packets are In case of congestion packets are

15 © Nokia Siemens Networks RN30036EN40GLA0

RNC Traffic where

CAC Guaranteed Bw CAC Guaranteed Bw

16 © Nokia Siemens Networks RN30036EN40GLA0

– QOS Attributes are negotiated between RAN and CN

17 © Nokia Siemens Networks RN30036EN40GLA0

18 © Nokia Siemens Networks RN30036EN40GLA0

• The logical scheduling architecture is composed of two levels:

Available only for Iub

19 © Nokia Siemens Networks RN30036EN40GLA0

20 © Nokia Siemens Networks RN30036EN40GLA0

BE WFQ 500 1 NRT 75 100 10 0 0

AF1 WFQ 300 4 NRT 75 100 10 0 1

AF2 WFQ 300 10 NRT 75 100 10 0 3

AF3 WFQ 300 25 NRT 75 100 10 0 4

AF4 WFQ 100 60 RT 100 100 0 0 5

EF SP 100 N/A RT 100 100 0 0 6

Default Profile ID = 0 Need to be adjusted

• The rate limiting is done using Internal Flow Control (IFC)

By default the queues

22 © Nokia Siemens Networks RN30036EN40GLA0

The IP based route scheduling in the cRNC is always virtual.

If any of the queues is empty, the spare capacity is shared

23 © Nokia Siemens Networks RN30036EN40GLA0

Scheduling in WBTS is implemented as for cRNC Interface

Queues weights and

24 © Nokia Siemens Networks RN30036EN40GLA0