NSN RU10 Interface Dimensioning (IP Part)

RU10 Dimensioning TTT Workshop
Interface Dimensioning (IP Part)

Wojciech Bigos
Network Engineering COO RA MRD SA NE Wroclaw, 27-29.02.2008
Company Confidental 1 Nokia Siemens Networks
Content
The following session covers dimensioning and configuration aspects of the RNC related interfaces: IP Iub BTS NNI IP Iu-CS UNI MSS/MSC MGW Iu-CS Iub RNC IP Iu-PS BTS IP Iur
NNI
NNI
Iur
BTS UNI BTS
Iub
BTS
SGSN
Iu-PS
RNC
BTS BTS UNI BTS
3G-SGSN
UNI stands for User-Network-Interface, like Iub NNI stands for Network-Network-Interface, like Iu-CS, Iu-PS and Iur
Company Confidental 2 Nokia Siemens Networks Interface Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos
Session Outline
1. IP-based Iub
Functional Overview
IP Connection Admission Control QoS support with IP DiffServ
Iub Dimensioning
Capacity-related parameters Dimensioning steps Impact of IP CAC and DiffServ to dimensioning
Iub Configuration
IP Addressing VLAN Assignment
2. Dimensioning Iur, Iu-CS and Iu-PS

IP-based Iub
Functional Description (1)
BTS BTS
E1 E1
ATM
ATM based Iub (SDH /PDH ATM based Iub (SDH /PDH )
RNC
STM1 Eth
BTS
Eth
IP
IP based Iub (Ethernet
IP based Iub (Ethernet )
BTS
Eth
IP Based Iub allows usage of 3GPP Rel-5 compliant IP transport between the
RNC and the WCDMA BTS.
Opex and capex savings for the operator due to the lower cost of the UTRAN
Access IP / Ethernet transport.
Interface Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos
IP based Iub
Functional Description (2)
Main building blocks for IP-based Iub are

3GPP Rel-5 / Rel-6 compliant protocol stack IP Diff Serv for QoS support IPv4 support IP fragmentation/reassembly Connection Admission Control VLANs
IP CAC: Functional Description (1)
IP Connection Admission Control (CAC) allocates the guaranteed bit rate on Iub for each RAB connection subject to CAC -> CAC_Guaranteed_Bitrate RAB. The CAC is performed against the specified guaranteed capacity (IPRoute_Commited_BW, usually the Iub bottleneck) An incoming RAB connection on Iub is admitted by IP CAC provided that the residual Iub bandwidth is more than or equal to CAC_Guaranteed_Bitrate RAB. It is performed by the RNC in DL and by the BTS in UL. CAC applies to:

Rel99 RT DCH Rel99 nRT DCH DCCHs Common Transport Channels HSPA streaming (with RAN1004 Streaming QoS for HSPA) HSPA interactive (with RAN1004) HSPA background (with RAN1004)
Incoming RAB Connection with CAC_Guaranteed_Bitrate demand
Yes
Residual Bandwidth IP_Comm_B W Sufficient ?
No
IP CAC
Connection accepted Connection rejected
IP CAC: Functional Description (2)
Set of 4 traffic descriptors for each bearer, one for UL and one for DL:

Maximum bit rate in IP layer Average bit rate in IP layer Maximum size of one IP packet Average size of one IP packet.
Incoming RAB Connection with CAC_Guaranteed_Bitrate demand
Parameters include IP overhead, but do not include Ethernet overhead.

Traffic descriptors are defined in the RNC, and forwarded to the BTS by using a private NBAP message. Residual Bandwidth IP_Comm_B W Sufficient ?
Yes
No
CAC-guaranteed BW per RAB connection:
CAC_Guaranteed_Bitrate RAB = MAX_BitrateRAB 0.2 + AVE_BitrateRAB 0.8
IP CAC
Traffic Descriptors are stored in PI:

https://pi.inside.nokiasiemensnetworks.com/urn.htm?id= 09006c378148d76b&DMW_DOCBASE=espoo11&auth= T&version=current&document_id=13-608250
Connection accepted
Connection rejected
QoS support with IP DiffServ
With DiffServ packets are classified into PHBs according to DiffServ Code Point (DSCP) field in the IP header and based on this information the RNC and the routers will handle the packets.
Up to 6 PHBs are supported (Expedited Forwarding, Assured Forwarding 1-4, Best Effort),
To get the full functionality (6 PHBs) RAN1253 IP Transport QoS must be activated. Without RAN 1253 only 3 PHBs are supported, for RT DCHs, nRT DCHs and HSPA. DSCPs are operator configurable. UMTS traffic classes can be mapped to one of these DSCPs as appropriate.
If VLANs are enabled, a PHB to VLAN priority bits mapping is defined
Not required in RU10

Transport QoS mapping schemes on IP-based Iub

UMTS Transport bearers Radio Network Layer Transport Network Layer
HS-DSCH
Conversational Streaming InteractiveTHP1 InteractiveTHP2
ARP1-3 ARP1-3 ARP1-3 ARP1-3 ARP1-3 ARP1-3 QoSPri15 QoSPri14 QoSPri13
E-DCH
InteractiveTHP3 Background
IP transport
DSCP DSCP DSCP DSCP DSCP DSCP EF AF4 AF3 AF2 AF1 BE DSCP 6 4 3 2 1 0
Conversational Streaming
ARP1-3 ARP1-3 ARP1-3 ARP1-3 ARP1-3 ARP1-3
QoSPri12 QoSPri11 QoSPri10 QoSPri9 QoSPri8 QoSPri7 QoSPri6 QoSPri5 QoSPri4
R99 DCH
InteractiveTHP1 InteractiveTHP2 InteractiveTHP3 Background
PCH, FACH, RACH
ARP1-3 ARP1-3 ARP1-3
QoSPri3 QoSPri2 QoSPri1 QoSPri0
6 Default PHBs corresponding to the IP egress scheduling queues
Ethenet VLAN priority bits
Signalling C-Plane
ARP1-3 ARP1-3
O&M
ARP1-3
Operator configurable mapping
RNC DiffServ Scheduler (1)

EF Q1 Rate limiting W1 W2 W3 AF2 Q4 W4 AF1 Q5 W5 WFQ SP IP Route Shaping
Per IP Based Route
AF4 AF3
Q2
Q3
BE
Q6
Each PHB is mapped to a queue EF is served as Strict Priority Other PHBs are served as Weighted Fair Queue (WFQ) Highest priority queue is rate limited Lowest priority queues are controlled by a WFQ scheduler (weights: w1-w5) Aggregate (interface) traffic is shaped to the specified transport service capacity. Note: Having a separate queue per PHB implies that traffic should be dimensioned separately per PHB class and then summed up. Company Confidental
10 Nokia Siemens Networks Interface Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos
RNC DiffServ Scheduler (2)

IP Based Route
SP+WFQ
EF Q1 Q2 Q3 Q4 W4 AF1 BE Q5 Q6 W5 Rate limiting W1 W2 W3 AF2 WFQ SP IP Based route shaping
Interface I/F shaping
SP+WFQ
IP based route #1
AF4 AF3
IP based route #2 IP based route #N
SP+WFQ
There is a logical SP+WFQ scheduler per IP Based route (BTS)

SP+WFQ
The interface scheduler is also SP+WFQ, which aggregates traffic from each traffic class in each IP Based Route Aggregate (interface) traffic is shaped to the specified transport service capacity.
IP-based Iub Dimensioning Components

BTS 1
IPRoute1_Bw
CAC guaranteed traffic
RNC
IP_Route Commited_BW Shared_BE IP_Allocation CAC guaranteed traffic Non CACguaranteed traffic
IP_Route 1
IPRoute2_Bw
CAC guaranteed traffic Non-guaranteed traffic
IP_Route 2
Rnc_Ethernet_Cap
Non-guaranteed traffic
IP_Route Commited_BW Shared_BE IP_Allocation
CAC guaranteed traffic Non CACguaranteed traffic
BTS 2

IP_Route_Comm_Bitrate: CAC-guaranteed IP bandwidth per logical Iub for high priority traffic. Shared_BE_IP_Allocation: non CAC-guaranteed IP bandwidth per logical Iub for low-priority BE traffic. IPRoute_BW: Total IP bandwidth per Iub Iub_Ethernet_Cap: Total bandwidth per Iub on Transport level (incl. Ethernet OH) RNC_Ethernet_Cap: Total bandwidth per RNC Ethernet port grouping multiple logical Iubs
User Traffic Estimation
Mapping of UMTS Service Classes to DiffServ PHBs
Calculating CACguaranteed BW
Calculating Non CACguaranteed BW
Calculating Total IP Bandwidth
Setting WFQ Scheduler Weights
Calculating Effective Transport Capacity
VLAN Assignment
Mapping of User Applications to UMTS Services

Conversational/Streaming Applications

Speech Release 99 CS C AMR 12.2 Video calls Release 99 CS S UDI 64 Audio Streaming Rel99 PS S RAB or Rel. 5, 6 Streaming HSPA
Video Streaming Rel. 5,6 Streaming HSPA
PS Interactive/Background Applications
File Download Web browsing Email
mapped either to:
PS Interactive/Background Release 99 RAB or
PS Interactive/Background Release 5 HSDPA DCH/HS-DSCH or

PS Interactive/Background Release 6 HSPA E-DCH/HS-DSCH
Representing User Traffic Demand

How the user traffic is represented:
Mean traffic in Busy Hour per subscriber +service mix (e.g. 40% C/S
services, 60% I/B services) Mean traffic in BH per subscriber per service
Offered traffic Service = # Subscr Service Mean traffic per subscriber Service
The value of Mean_traffic RAB is defined by the operator. Alternatively it can be

taken from the Reference Traffic Model:
User Application
Voice Media Streaming HTTP FTP E-mail
UMTS Service Type

Conversational Streaming Interactive Background Background
UMTS Service
CS C Streaming HSPA PS I/B 128 I/B HSPA PS I/B 64
Per each UMTS Service
BHCA per user, Call Duration, Activity Factor, Peak rate
Mean traffic => per subscriber per application
VLAN Assignment
Exemplary Mapping of UMTS Service Classes to PHBs

UMTS transport bearer Timing over Packet CS C, PS C incl. DCCHs FACH, RACH, PCH C-NBAP, DNBAP, O&M PS S, CS S incl. DCCHs, HSPA S PS I/B Prio_1 PS I/B Prio_2 PS I/B Prio_3 HSPA I/B
UMTS Service class -
DSCP Value (default) 0b101110 (46)
PHB to be used EF
VLAN p-priority (default) 6 "Voice"
CAC
Conversational
0b101110 (46)
EF
6 "Voice"
Yes
0b001010 (10)
AF1
4 "Controlled load"
Yes
0b001010 (10)
AF1
4 "Controlled load"
Yes
Streaming
0b010010 (18)
AF2
Yes
Interactive THP 1 Interactive THP 2 Interactive THP 3 Background
0b010010 (18) 0b011010 (26) 0b100010 (34) 0b000000 (0)
AF2 AF3 AF4 BE
3 2 1 0 "Best Effort"
Yes Yes Yes No
VLAN Assignment
Calculating CAC-guaranteed Traffic (1)

BTS 1
IPRoute1_Bw
RNC
IP_Route 1
IPRoute2_Bw
IP_Route 2
Rnc_Ethernet_Cap
BTS 2

IP_Route_Comm_BW: CAC-guaranteed bandwidth per logical Iub for high priority traffic; CAC ensures that conforming connections keep within IP_Route_Comm_BW IP_Route_Comm_BW is shared by:
U-Plane traffic: R99 DTCHs (C/S/I/B CS and PS RABs), DCCHs, CCHs and HSPA (if subject to CAC) C-Plane traffic: C-NBAP, D-NBAP O&M traffic
19 IP_Route_Comm_BW Nokia Siemens Networks Interface Dimensioning (IP Part) / COO RA at MRD SA NE / and Wojciech Bigos is a user-configurable parameter RNC BTS
Company Confidental

IP_Route_Committed_BW is calculated as:
IP_Route_comm_BW = IP_Route_U-Plane_comm_BW + IP_Route_C-Plane_comm_BW+ IP_Route_O&M_comm_BW (1)
For calculating C-Plane traffic (IP_Route_C-Plane_comm_BW ) refer to [RU10

Signaling Dimensioning Guide]
For the O&M traffic (IP_Route_O&M_comm_BW ) a 64 kbps IP transport channel

is assumed.
Calculation of the U-plane traffic (IP_Route_U-plane_comm_BW ):

IP_Route_U-Plane_comm_BW = RT_U-Plane_comm_BW + NRT_U-Plane_comm_BW + CCH_U-Plane_comm_BW will be explained next.
(2)

Real Time U-Plane traffic (RT_U-Plane_comm_BW)
It is recommended to dimension the RT traffic (i.e. Conversational and Streaming
Rel99 DCHs and Streaming HSPA) with MD-Erlang formula, separately for each PHB class:
RT_IP_Route_comm_BW PHB = MD-Erlang [Gross_peak_rate RAB 1, Off_traffic RAB 1, Bl_Pr RAB 1 ; ;
Gross_peak_rate RAB n, Off_traffic RAB n, Bl_Pr RAB n]
(3)
where:
n is the number of RT services (RABs) within a given PHB class, Gross peak rate RAB, is a sum of CAC-guaranteed bit rates for RT DTCH and DCCH RABs:
Gross peak rate RAB = CAC_Guaranteed_BW RAB_DTCH + CAC_Guaranteed_BW RAB_DCCH
(4)
Offered_traffic RAB is the mean traffic per service (RAB) in [erlang] extended with SHO_factor:
Offered_traffic RAB = Mean_traffic RAB [erlang] (1+ SHO_Factor)
(5)
Bl_Pr RAB is the service blocking probability. Usually assumed values are 0.1% 1%.
The total RT bandwidth is a sum of RT bandwidth portions in individual PHB classes Company Confidental
Example:
Calculating Real Time U-Plane traffic with MD-Erlang
Service rate [kbps]
12.2 MBR: 30 GBR: 15
RT Application
AMR Voice VoIP
UMTS Service
CS 12.2 Streaming HSPA
Mean traffic per BTS [erl]

3 2
CAC-guaranteed BW [kbps]
23.7 39.4
PHB Mapping Option 1

EF EF AF1
Option 2
Blocking Pr = 0.1%, SHO_Factor = 30%; MBR: Max Bit rate, GBR: Guaranteed Bit Rate; DCCH 3.4 kbps
Offered traffic Service [erl]
RT U-Plane BW MD-Erlang RT U-Plane BW
CAC-guaranteed BW Service
Bl. Probability Service
Option 1 Option 2
EF: 288 kbps AF1: 390 kbps Total: 678 kbps (+30%)
Total (EF): 510 kbps

Non Real Time U-Plane traffic Option 1
To dimension NRT traffic (i.e. Interactive/Background Rel99 DCHs and I/B HSPA, if subject
to CAC) two options are proposed:
Option 1: Estimate the number of parallel NRT connections in Busy Hour and apply to them
the set of traffic descriptors. The number of parallel connections of a given NRT RAB type is calculated as: Parallel connections RAB = round-up [Offered_traffic RAB / (Service_bitrate RAB Activity_factor RAB)] (6) where:
Offered_traffic RAB is the mean traffic per service (RAB) in [kbps] extended with SHO_factor Service_bitrate RAB is the nominal RAB bit rate in [kbps] above the Frame Protocol level
The CAC-guaranteed bandwidth for NRT traffic within a single PHB is calculated as:
NRT_U-Plane_comm_BW PHB =
RAB
Parallel connections RAB, PHB (CAC_Guar_BW RAB_DTCH + CAC_Guar_BW RAB_DCCH )
The total NRT bandwidth is a sum of NRT bandwidth portions in individual PHB classes

Non Real Time U-Plane traffic Option 2
Option 1 does not explicitly take into account any QoS parameters e.g. in terms of blocking
or transfer delay assurances in dimensioning of NRT traffic. Therefore, Option 2 is proposed:
Option 2: Calculate the NRT U-plane traffic with M/G/R-PS formula:

NRT_U-Plane_comm_BW PHB = M/G/R-PS [Total_off_traffic; Gross_peak_rate RAB 1, Transfer_delay RAB 1 ; ; Gross_peak_rate RAB n, Delay_factor RAB n ] where: Total_offered_traffic RAB is the total mean traffic summed over all services (RABs): Total_offered_traffic = (8)
Mean_trafficRAB (1+ SHO_Factor)

RAB
(9)
Delay_factor RAB reduces the effective bit rate perceived by the end-user of an NRT application as
compared with the nominal CAC_Guar_Bitrate. Suggested values of Delay_factor RAB on Iub are 5-10%.
With this set of inputs, M/G/R-PS is repeated n times, separately for each NRT RAB service,
and the Max value over all calculations is picked-up.
Use of M/G/R-PS is recommended when the QoS measures in terms of transfer delay on Iub
Company Confidental 24 Nokia Siemens Networks Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos must be explicitly taken into Interface account.
Example:
Calculating Non Real Time U-Plane traffic (DL) with M/G/R-PS (Option 2)
nRT Application
HTTP FTP
UMTS Service
PS I/B 128 PS I/B 384
Service rate [kbps]

128 384
Mean traffic per BTS [kbps]

500 600
CAC-guaranteed BW [kbps]
167.4 364.4
PHB Mapping Option 1

AF1 AF1 AF2
Option 2
Delay Factor = 10%, SHO_Factor = 30%; DCCH 3.4 kbps
Total off. traffic [kbps] CAC-guaranteed BW Service M/G/R-PS Delay Factor Service Option 2 nRT U-Plane BW Option 1
nRT U-Plane BW
AF1: 699 kbps AF2: 759 kbps Total: 1458 kbps (+ 6%)
Total (AF1): 1399 kbps

CCH U-Plane traffic
The CCH bandwidth is calculated out of the CCH traffic descriptors assuming the
number of CCHs as resulting from the number of cells per BTS (with 4 CCHs per cell: FACH-C, FACH-U, RACH and PCH).
CCH FACH-C FACH-U RACH PCH
Max Bitrate [kbps] 66.2 68.7 14.3 55.2
Ave Bitrate [kbps] 6.1 6.3 1.1 5.0
MAX size [byte] 76 79 29 62
Ave size [byte] 34 34 0 34
VLAN Assignment
Calculating Non CAC-guaranteed Traffic (1)

BTS 1
IPRoute1_Bw
RNC
IP_Route 1
IPRoute2_Bw
IP_Route 2
Rnc_Ethernet_Cap
BTS 2
Shared_BE_IP_Allocation: non-CAC guaranteed BW per logical Iub for low-priority BE

traffic; provides an extra add-on on Iub to accommodate this type of traffic.
Currently only I/B HSPA can fall under the non CAC-guaranteed traffic.
Calculating Non CAC-Guaranteed Traffic (2)

The Non CAC-guaranteed traffic can be calculated based on the mean traffic of I/B HSPA
users : Shared_BestEffort_IP_Allocation = #_of_Subs I/B HSPA Mean_traffic_per_subs I/B HSPA where:
the value of mean I/B HSPA traffic per subscriber is defined by the operator. Alternatively it can be taken
from the traffic model.
(10)
Alternatively, this can be extended with an additional QoS overhead, to account for
instantaneous I/B HSPA bursts above the average value:
Shared_BestEffort_IP_Allocation = #_of_Subs I/B HSPA Mean_traffic_per_subs I/B HSPA (1 +

QoS_Factor) (11)
Typical QoS_Factor values are around 20%
VLAN Assignment
Calculating Total IP Bandwidth (1)

BTS 1
IPRoute1_Bw
RNC
IP_Route 1
IPRoute2_Bw
IP_Route 2
Rnc_Ethernet_Cap
BTS 2
IPRoute_BW determines the total bandwidth per logical Iub on IP level

With respect to this parameter a rate limiting is performed in RNC and BTS the nonconforming traffic is dropped.
IPRoute_BW is a user-configurable parameter at RNC and BTS

Calculating Total IP Bandwidth (2)

Total IP Bandwidth is a sum of the CAC-guaranteed and the non CAC-guaranteed traffic:
IP_based_Route_BW = IP_based_Route_commited_BW + Shared_BestEffort_IP_Allocation
(12)
where:
IP_Route_comm_BW = IP_Route_U-Plane_comm_BW + IP_Route_C-Plane_comm_BW+

IP_Route_O&M_comm_BW (1)
VLAN Assignment
Calculating Effective Transport Capacity (1)

BTS 1
IPRoute1_Bw
RNC
IP_Route 1
IPRoute2_Bw
IP_Route 2
Rnc_Ethernet_Cap
BTS 2
Iub_Ethernet_Capacity is the Iub bandwidth on Transport level (incl. Ethernet OH). It determines the effective Iub capacity to be installed on Ethernet transport links at BTS side. RNC_Ethernet_Cap is the bandwidth per single RNC Ethernet port grouping multiple logical Iubs. It determines the effective Iub capacity to be installed on Ethernet transport links at RNC side. With respect to this parameter a rate limiting is performed in RNC. Company RNC_Ethernet_Cap is a user-configurable parameter at RNC. Confidental

Transport Capacity per Iub (Iub_Ethernet_Capacity)
The effective Iub capacity on the transport level should be increased by applying additional
Ethernet overhead: Iub_Ethernet_Capacity = IP_based_Route_BW (1 + Weighted_Ethernet_OH) where:
Weighted_Ethernet_OH is the mean Ethernet transport overhead weighted over the services supported
on Iub:
(13)
Weighted_Ethernet_OH =
RAB
Mean _ traffic RAB Eth _ OH RAB Mean _ traffic RAB

RAB
(14)
Ethernet overhead for single RAB is calculated out of the traffic descriptors:
Eth_OH RAB [%] =
Eth _ frame _ header _ length[byte] 100 % Average _ IP _ packet _ size RAB [byte]
(15)
Length of Ethernet frame header is assumed 38 bytes w/o VLAN and 42 bytes with VLAN.

Transport Capacity per RNC port (RNC_Ethernet_Capacity)
In addition, the total capacity per physical RNC interface IP_Port is defined as a
sum of the capacities of all Iubs terminated at this physical port:
RNC_Ethernet_Capacity (IP_Port) =
log ical _ IubIP _ Port
Iub _ Ethernet _ Capacitylog ical _ Iub
(16)
where logical_Iub IP_Port denotes logical Iubs terminated at the physical interface IP_Port.
Estimating Timing over Packet (ToP) Bandwidth

PRC
M Timing server S
RNC
PSN
BTS
S M S Master Clock Slave Clock
ToP solution comprises a timing master and timing slaves. The master sends synchronization messages to the slaves. By using a specific algorithm the slaves can recover the timing reference from the synchronization messages send by the master. Sync messages are based on Precise Time Protocol (PTP) defined in IEEE 1588 v2 standard. The bandwidth requirement of the ToP stream depends on the frequency of the Sync Msg exchange and the Sync Msg length:
ToP_BW [kbps] = (Eth/IP/UDP_Hdr_length + PTP_Sync_Msg_size [bits] / 1000) PTP_Sync_Msg_rate [1/s] (17)
PTP_Sync_Msg_rate is configurable in range of 0.5/s to 128/s. Default value is 16/s. The PTP_Sync_Msg_size is 44 bytes. Company The ToP bandwith for the default value of the Sync Msg rate and assuming 42 byte Eth frame hdr (incl. VLAN Confidental
37 Nokia Siemens Networks Tag) is ~ 24 kbps. Interface Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos
VLAN Assignment
VLAN Assignment Options
A single VLAN can be allocated per logical Iub (i.e. IP Route), per single RNC
port or per multiple RNC ports. No VLAN can also be used. VLAN assignment per traffic class is not required. Commited Information Rate (CIR) and Excessive Information Rate (EIR) setting:
Option 1: Single VLAN per logical Iub
CIR Iub = IP_based_Route_commited_Bitrate Weighted_Ethernet_OH EIR Iub = Iub_Ethernet_Capacity

Option 2: Single VLAN per RNC port
(18) (19)
CIR IP_port =
log ical _ IubIP _ Port
IP _ based _ Route _ commited _ Bitratelog ical _ Iub Weighted _ Eth _ OH log ical _ Iub
(20)
(21)
EIR IP_port = RNC_Ethernet_Capacity

VLAN Assignment

EF Q1 Rate limiting W1 W2 W3 AF2 Q4 W4 AF1 Q5 W5 WFQ SP IP Route Shaping
AF4 AF3
Q2
Q3
BE
Q6
For WFQ, queues AF4 - BE shall be assigned a weight (W1 W5) that determines the
share of the available capacity that they will have, according to the following formula:
Average _ Queue _ RatePHB IP _ based _ Route _ BW
Weight PHB Weight PHB
(22)
PHB
To assure a fair access to link recourses, WFQ Weights should be set proportional to the
dimensioned IP bandwidth per PHB.
By replacing Average_Queue_RatePHB by IPRoute_BW PHB in (22) one gets:

Company Confidental AF1 AF2 AF3 41 Nokia Siemens Networks
:W
:W
: WAF4 : WBE = IP_BWAF1 : IP_BWAF2 : IP_BWAF3 : IP_BWAF4 : IP_BWBE

(23)
IP-based Iub Transport flow configuration in DL

NRT HSDPA RT HSDPA NRT CS NRT PS RT CS RT PS SRB
UTRAN Service
At Layer 4 UMTS transport

bearers are identified by UDP/SCTP ports
HS-DSCH #1
HS-DSCH #2
C-NBAP
D-NBAP
O&M #1
O&M #2
DCH #1
DCH #2
DCH #3
DCH #4
DCCH
RACH
FACH
PCH
UTRAN Transport Bearer
At Layer 3 transport flows are

Layer 4
IP Layer
Dest IP Address
0b101110 (46)
0b010010 (18)
0b010010 (18)
0b011010 (26)
0b101110 (46)
0b010010 (18)
0b001010 (10)
0b001010 (10)
0b001010 (10)
0b001010 (10)
0b001010 (10)
0b001010 (10)
0b001010 (10)
0b000000 (0)
DSCP marking
allocated IP addresses. In BTS one IP address is allocated commonly for the U-Plane and C-Plane traffic. In RNC there are two separate addresses for the U-Plane and C-Plane traffic.
SCTP Port #1
SCTP Port #2
UDP Port #10
UDP Port #11
IP Address #1
IP Address #2
IP Address #3
IP Address #3
IP Address #3
IP Address #3
IP Address #3
IP Address #3
IP Address #3
IP Address #3
IP Address #3
IP Address #3
IP Address #3
IP Address #3
UDP Port #12
UDP Port #1
UDP Port #2
UDP Port #3
UDP Port #4
UDP Port #5
UDP Port #6
UDP Port #7
UDP Port #8
UDP Port #9
On DiffServ level traffic is

classified as belonging to a number of different PHBs corresponding to different DSCP values.
AF1
EF
AF2
AF3
EF
AF2
BE
PHB allocation
Ethernet Transport Network

p-bit marking
PHBs are mapped to the

Ethernet Class of Service (CoS) using Ethernet priority code point (PCP) corresponding to the IP DSCP value.
VLAN tagging
VLAN ID #1
CIR = IP_based_Route_commited_Bitrate EIR = IP_based_Route_BW
Dimensioning Iur, Iu-CS and Iu-PS interfaces

BTS NNI UNI
MGW
Iu-CS
RNC
Iub
BTS NNI
MSS/MSC NNI
Iur
BTS UNI BTS
Iub SGSN Iu-PS RNC
BTS
BTS BTS UNI BTS
3G-SGSN
Functional components incl. dimensioning and configuration approaches

remain the same as for IP-based Iub Material will be presented as a delta to the Iub dimensiong
Dimensioning Iur Interface

Iur carries the traffic of the users being simultanously served by 2 RNCs Iur is dimensioned based on the offered traffic of users in the inter-RNC
handover state. MSS/MSC The inter-RNC handover traffic can be estimated using one of the 2 options: ex-North :
Iur traffic is 4-9 % of the Iu traffic per RNC ex-South: Number of subscribers in the inter-RNC handover is determined with Drift_Handover_Factor (set to 10 %):
# subscribersdrift _ area # subscriberstotal DHO _ factor
Once having determined the Iur traffic, the same capacity components needs to be calculated as on Iub (RT, nRT CAC-guaranteed BW, non CAC-guaranteed BW, etc.) CAC Traffic descriptors and Ethernet overheads are the same as on Iub.
Dimensioning Iu-CS Interface

Iu-CS groups the CS traffic from RNC towards MGW. The calculation method is the same as in Iub RT U-Plane traffic, which is MDErlang:
Iu-CS_BW PHB = MD-Erlang [Gross_peak_rate RAB 1, Off_traffic RAB 1, Bl_Pr RAB 1 ; ; Gross_peak_rate
RAB n,
MSS/MSC
Off_traffic RAB n, Bl_Pr RAB n]
(24)
where: Gross peak rate RAB, is a sum of CAC-guaranteed bit rates for RT RABs:
Gross peak rate RAB = CAC_Guaranteed_BW RAB (25)
Offered_traffic RAB is the mean traffic per RAB per RNC in [erlang] (w/o SHO_factor) Bl_Pr RAB is the service blocking probability. Usually assumed values are 0.1% 1%.
Note 1: Due to a different data structure on Iu-CS, CAC traffic descriptors and
Ethernet OHs on Iu-CS are different that the ones on Iub.
Note 2: Dimensioning should be done separately per PHB class.

Dimensioning Iu-PS Interface

Iu-PS groups Rel99 PS and HSPA traffic from RNC towards 3G-SGSN. The calculation method depends on the supported traffic types and mixes:
Streaming HSPA should be dimensioned as RT CS (i.e. with MD-Erlang), Rel99 PS + I/B HSPA should be dimensioned using one of the options for dimensioning
nRT U-plane traffic on Iub:
via Parallel Connections with IP CAC traffic descriptors, or
MSS/MSC
with M/G/R-PS
If there is a large share of PS Streaming, it should be dimensioned as RT CS (i.e. with

MD-Erlang).
Note: Dimensioning should be done per PHB class.
Iu-PS transmission overhead depends on the packet size that has to be transmitted
from RNC to 3G-SGSN. Subscriber data packet can vary from 64 Bytes to 64K Bytes.
Therefore IP traffic descriptors and Eth overhead will vary depending on the data
packet size.
It seems reasonable to assume an average packet size of 512 bytes.

Iu-PS OH vs Packet Size

IuPS overhead table
protocol overhead
MSS/MSC
1.2 1 0.8 0.6 0.4 0.2 0
10 0 16 0 22 0 28 0 34 0 40 0 46 0 52 0 58 0 64 0 70 0 76 0 82 0 88 0 94 0 10 00 10 60 11 20 11 80 12 40 13 00 13 60 14 20 14 80
packet size
relative overhead
Overhead is LARGE for small packet sizes!
30%

NSN RU10 Interface Dimensioning (IP Part)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NSN RU10 Interface Dimensioning (IP Part)

Uploaded by

Copyright:

Available Formats

RU10 Dimensioning TTT Workshop

Interface Dimensioning (IP Part)

Company Confidental 1 Nokia Siemens Networks

2. Dimensioning Iur, Iu-CS and Iu-PS

IP based Iub (Ethernet )

Interface Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos

Main building blocks for IP-based Iub are

Company Confidental 5 Nokia Siemens Networks

Interface Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos

IP CAC: Functional Description (1)

Incoming RAB Connection with CAC_Guaranteed_Bitrate demand

Residual Bandwidth IP_Comm_B W Sufficient ?

Interface Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos

IP CAC: Functional Description (2)

Incoming RAB Connection with CAC_Guaranteed_Bitrate demand

Parameters include IP overhead, but do not include Ethernet overhead.

CAC-guaranteed BW per RAB connection:

CAC_Guaranteed_Bitrate RAB = MAX_BitrateRAB 0.2 + AVE_BitrateRAB 0.8

Traffic Descriptors are stored in PI:

Interface Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos

QoS support with IP DiffServ

If VLANs are enabled, a PHB to VLAN priority bits mapping is defined

Not required in RU10

Transport QoS mapping schemes on IP-based Iub

Conversational Streaming InteractiveTHP1 InteractiveTHP2

ARP1-3 ARP1-3 ARP1-3 ARP1-3 ARP1-3 ARP1-3 QoSPri15 QoSPri14 QoSPri13

ARP1-3 ARP1-3 ARP1-3 ARP1-3 ARP1-3 ARP1-3

QoSPri12 QoSPri11 QoSPri10 QoSPri9 QoSPri8 QoSPri7 QoSPri6 QoSPri5 QoSPri4

InteractiveTHP1 InteractiveTHP2 InteractiveTHP3 Background

PCH, FACH, RACH

ARP1-3 ARP1-3 ARP1-3

QoSPri3 QoSPri2 QoSPri1 QoSPri0

6 Default PHBs corresponding to the IP egress scheduling queues

Ethenet VLAN priority bits

Operator configurable mapping

Company Confidental 9 Nokia Siemens Networks

Interface Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos

RNC DiffServ Scheduler (1)

Per IP Based Route

RNC DiffServ Scheduler (2)

Interface I/F shaping

IP based route #2 IP based route #N

There is a logical SP+WFQ scheduler per IP Based route (BTS)

Company Confidental 11 Nokia Siemens Networks

Interface Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos

IP-based Iub Dimensioning Components

CAC guaranteed traffic Non-guaranteed traffic

IP_Route Commited_BW Shared_BE IP_Allocation

CAC guaranteed traffic Non CACguaranteed traffic

Company Confidental 12 Nokia Siemens Networks

User Traffic Estimation

Mapping of UMTS Service Classes to DiffServ PHBs

Calculating Non CACguaranteed BW

Calculating Total IP Bandwidth

Setting WFQ Scheduler Weights

Calculating Effective Transport Capacity

Mapping of User Applications to UMTS Services

Video Streaming Rel. 5,6 Streaming HSPA

PS Interactive/Background Release 5 HSDPA DCH/HS-DSCH or

Company Confidental 14 Nokia Siemens Networks

Interface Dimensioning (IP Part) / COO RA MRD SA NE / Wojciech Bigos

Representing User Traffic Demand

The value of Mean_traffic RAB is defined by the operator. Alternatively it can be

UMTS Service Type