UMTS RAN Dimensioning Guidelines PDF

UMTS RAN Dimensioning Guidelines
Nokia Equipment
Version 1.5
T-Mobile FSC
RAN Engineering and Dimensioning Group

Nokia
Document Name: UMTS Dimensioning Guidelines for Nokia Equipment

Revision History:
Version
1.0
1.1
Date
05/26/04
06/16/06
1.2
06/27/06
1.3
10/26/06
1.4
11/28/06
1.5
12/22/06
Revision History
Change Description
First issued full version
Nokia Flexi
Additional guidelines on Flexi
included
dimensioning
Additional:
Adds summary of formulas, includes
Section 6
the Nokia counters
Edit Section 2
Remove details on Ultrasites,
and 3
change Iub configuration figures
Updated
Updated based on inputs from
version
A.Lemow Y.Zhang, RAN Dim Group
Counters
Revised the Counter lists
Changes
Done by:
G. Jacinto
G. Jacinto
G. Jacinto
G. Jacinto
G. Jacinto
J.Javier
Scope:
This document presents the dimensioning process for Nokia UMTS Radio Access Network specifically
the Node B Channel Elements, Iub interface and RNC. The dimensioning rules in this document are
intended for establishing a new or overlay UMTS network, considerations on network quality and
performance can be inputted on future versions when considerable amount of traffic and statistics are
already available.
For this version, Nokia RAS05.1 capacity limitations were used for the dimensioning exercises but
roadmaps for future RAN releases were also mentioned.
Purpose:
The purpose of this document is to provide the fundamental knowledge in dimensioning a Nokia UMTS
Radio Access Network. This intends to support the engineers involved in planning and dimensioning of
UMTS RAN by providing detailed guidelines and computations of network requirements.
Version 1.3
Jacinto

Nokia
Table of Contents
1.
2.
3
4
5
6
7
Introduction.............................................................................................................................4
Nokia Product Description .........................................................................................................5
2.1.1
Node B ........................................................................................................................5
2.1.2
Description of Flexi WCDMA BTS Units ......................................................................5
2.1.3
Flexi WCDMA BTS Capacity .......................................................................................6
2.1
RNC ................................................................................................................................8
2.2.1
Description of RNC units ...........................................................................................8
2.2.2 RNC Capacity ..................................................................................................................9
Channel Element Dimensioning ............................................................................................... 10
3.1
Nokia Flexi WCDMA BTS System Module (FSM) ................................................................ 10
Iub Dimensioning ................................................................................................................... 12
4.1
User Plane Iub Bandwidth .............................................................................................. 13
4.2
Control Plane Iub Bandwidth .......................................................................................... 14
RNC Dimensioning ................................................................................................................. 17
Iu Interface Dimensioning ...................................................................................................... 20
6.1
Iu-CS Interface .............................................................................................................. 20
6.2
Iu-PS Interface .............................................................................................................. 21
Summary of Formulas and Counters ........................................................................................ 22
7.1
Channel Element Dimensioning Formulas ........................................................................ 22
7.2
Iub Dimensioning Formulas ............................................................................................ 22
7.3
RNC Dimensioning Formulas ........................................................................................... 22
7.4
Nokia Counters .............................................................................................................. 23
7.5
Partial Results of Capacity Tests in Bellingham ................................................................. 30
List of Tables
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
1 RF Module Types
2 Transmission Sub module Types
3 Flexi WCDMA BTS Capacity
4 Flexi Configurations
5 Maximum RNC Capacity per Release
6 Number of CEs needed for different services
7 Flexi BTS CE dimensioning example
8 Nokia Iub VC Requirements
9 Iub User Plane Dimensioning Assumptions
10 Iub Dimensioning example
11 Nokia RAS05 RNC Capacity
12 Nokia RNC HSDPA Capacity
13 RNC Dimensioning example
14 Nokia RNC Counters on RAB Setup
15 Nokia RNC Counters on Congestion
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
1
2
3
4
5
6
7
Version 1.3
Jacinto
Flexi WCDMA BTS units

Nokia Flexi WCDMA BTS
Nokia RNC units
Nokia Iub Configuration
Iub Configuration example
Iu-CS Configuration example
Iu-PS Configuration example
3

Nokia
1. Introduction
This document presents the dimensioning guidelines for the Node B channel elements, Iub interface
and the Radio Network Controller for Nokia equipments. The dimensioning process is the initial phase
of planning where the estimate requirements for network elements count and configuration are
calculated based on the inputted values. The accuracy of the dimensioning output would primarily
depends on the inputs and assumptions used in the process, thus network element counts and
configurations based on the traffic and subscriber forecast might differ with the actual need when the
network is in on operating phase. Nonetheless this document will provide the necessary knowledge to
dimension the Nokia UMTS RAN.
Node B dimensioning should involve not only the channel element capacity, but also the BTS power and
carrier because most of the times the channel element capacity of node B cannot be maximized due to
power and carrier limitations brought by high UL interference. But this document focuses only with the
channel element capacity, the BTS power and carrier capacity which affects the RF design will be
handled by the RF Planning group.
Section 2 provides the description of the Node B and RNC units and the equipment capacity. It is
important to understand the hardware units and its functions and how they can affect the dimensioning
process. The capacity tables included in this section are taken from Nokia documents and roadmaps,
and are used on the dimensioning guidelines for Channel Element and RNC in Section 3 and 5
respectively.
Section 3 deals with the dimensioning guidelines for Channel elements. This includes the required
inputs and assumptions, dimensioning process and a sample calculation. Some of the assumptions and
considerations can vary depending on the network performance and future service requirements.
Section 4 is concerned with the Iub interface dimensioning; this illustrates a detailed calculation of the
user plane and control plane bandwidths and the allocation of VCs needed in Nokia Iub.
Finally, Section 5 deals with the RNC dimensioning process which includes three main considerations,
the throughput, BTS and cell count and AAL2 connectivity. Other factors that might limit the RNC
capacity such as the interfaces and VP in traffic shaping feature were also included in the dimensioning
exercise.
The protocol and ATM overheads used in these dimensioning guidelines were based on Nokias
recommendations and 3GPP specifications. The detailed computations of these overheads were not
included in this document but can be issued separately.
Version 1.3
Jacinto

Nokia
2. Nokia Product Description

This section provides the description of hardware units of Node B and RNC, and also the equipment
capacity.
2.1.1
Node B
The Node B implements the WCDMA radio path and performs layer 1 functions such as channel coding,
interleaving, rate adaptation and spreading. There is a wide selection of Nokia Node B in terms of
application, processing capacity and power output.
One distinct characteristic of Nokia Node B is its pooled processing capacity, the channel elements are
being pooled to all the sectors and contains both the uplink and downlink resources and control
channels.
T-Mobile will deploy a modular Node B type called Flexi WCDMA BTS. The Flexi BTS can easily be
installed in various locations due to its small structure and modular design, it also does not require
specific BTS cabinet.
2.1.2
Description of Flexi WCDMA BTS Units
The figure 1 below shows the Nokia Flexi WCDMA BTS units, divided into the following main parts: the
RF module, Baseband unit, Transmission and Control units.
RF Unit
RF Module
Control
Baseband Unit
Transmission
Flexi
System Module
Figure 1. Flexi WCDMA BTS units

RF Module
The RF module is a stand-alone fully operational transceiver module with integrated antenna filters.
The RF Module is able to support one or two sectors in a WCDMA base station. It hosts the RF
functionality and provides control and power supply to the Flexi Antenna line.
The following are the different types of RF module:
BTS Type
Cabinet
Max Unit
/cabinet
RF Module Type
# of
PA/Type
Max output
Power/PA (W)
Flexi
FCOA or FCIA
(optional)
8
8
RF Module - FRIA
RF Module - FRIB
2
1
40
40
Table 1. RF Module types

Although the RF module is capable of 40W output power, it will be initially deployed with 20 W license
only but can eventually be upgraded to 40W by software license.
Version 1.3
Jacinto

Nokia
Flexi System Module

The Flexi System Module hosts the telecom control, system operation and maintenance, baseband
application, transmission, and power distribution functionality. The System Module can also act as a
second system module operating in a baseband extension mode. The System Module provides the BTS
external interfaces towards the RNC and other external devices.
The System Module is the overall BTS control, system clock generator unit, network termination
point of the BTS, and WCDMA baseband processing unit.
Transmission Sub Module
The transmission sub module, contained within the Flexi System Module, provides the physical Iub
interface to the RNC. It is also one possible source of synchronization for the Node B.
The following are the available transmission sub modules type:
Transmission SubModules
FTPB
FTIA
IMA groups supported

4
2
Transmission links per

IMA group
8 T1 links
4 T1 links
Table 2. Transmission Sub Module types

2.1.3
Flexi WCDMA BTS Capacity
Nokia Flexi WCDMA BTS has basically the same architecture as the other Node B types, but its
hardware is more compact and modular. The Flexi BTS contains its baseband and transmission
functionality in one module known as Flexi System Module. This makes it advantageous it terms of site
acquisition, installation and operational costs.
The Flexi BTS capacity is dictated by four factors: the number of carriers, baseband processing
capacity, the output power and number of interface transmission units. If any of these four
factors meet its maximum capacity limits, a new Node B or traffic off-loading to adjacent Node Bs is
required to support the UMTS traffic.
A Flexi BTS has a micro BTS dimensions with typical macro Node B functionality. It has WCDMA and
HSDPA functionality and can support up to 12 carriers, 6 sectors and have 20 or 40 watts
output power.
Nokia Flexi BTS is designed based on modular Open Base Station Architecture supporting multiple radio
technologies. The introduction of new radio part can be done by adding a new module.
Version 1.3
Jacinto

Nokia
Figure 2. Nokia Flexi WCDMA BTS
Configurations
FSMB
FSMB + FSMB
No. of Channel
Elements
(RAS05.1)
192
384
No. of Channel
No. of Carriers
Elements
(RAS06)
240
6
480
12
Table 3. Flexi BTS Capacity
No. of Sectors
3
6
Each FSM module have three sub-modules, each call must be handled only by one sub-module. If the
capacity of the used sub-module is not enough, the call can be transfer to the other entity with enough
capacity.
The following are the available configurations for Flexi BTS and the corresponding RAN SW Release
needed to support the configuration.
Node B Config
Power Output (W)
RF Module Type
2+2
20
FRIA
1+1+1 Feederless
20 or 40
3 FRIB
2+2+2
20
FRIA + FRIB
2+2+2 Feederless
20
3 FRIB
2+2+2
40
3 FRIA
1+1+1+1
40
2 FRIA
3+3+3
40
3 FRIA
4+4+4
20
3 FRIA
Uneven config
3 FRIA
1+1+1+1+1+1
20 or 40
3 FRIA
2+2+2+2+2+2
20
3 FRIA
Table 4 Flexi Configurations
Version 1.3
Jacinto
RAN Release
RAS05.1 CD
RAS05.1
RAS05.1 CD
RAS05.1 CD
RAS06
RAS06
RAS06
RAS06
RAS06
RAS06
RAS06

Nokia
2.1
RNC
The Radio Network Controller controls and manages the radio access network and radio channels.
Nokia RNC has a modular software and hardware structure that provides flexibility in adding up the
processing capacity, power and interfaces.
2.2.1
Description of RNC units
The different units of Nokia RNC are shown in Figure 3. The main cabinet have all the necessary
functional plug-ins to provide the necessary RNC functions, the extension cabinet with four subracks
indicates additional four capacity steps to support expansion.
RNC 300
RNC 150
RNC 450
Figure 3. RNC units

SFU - Switching Fabric Unit provides a part of the ATM cell switching function. It provides redundancy,
full accessibility and is non-blocking at the ATM connection level.
NIU - Network Interface Unit connects network elements to transmission systems. It can be NIS or NIP.
A2SU - AAL Type 2 Switching Unit performs minipacket switching of AAL Type 2 common part sublayer
packets between external interfaces and Signal Processing Units.
RRMU - Radio Resource Management Unit performs the central radio resource management and call
management related tasks of the RNC.
Version 1.3
Jacinto

Nokia
RSMU - Resource and Switch Management Unit performs the RNC's central resource management
tasks, such as connection control, ATM resource scheduling and digital signal processing related
resource management tasks. It also performs cell connection related functions according to request
received from signaling computer units.
MXU - Multiplexer Unit multiplexes traffic from tributary units to the ATM switching fabric. The MXU
also includes a part of ATM layer processing functions, such as policing, statistics, O&M, buffer
management, and scheduling.
NEMU - Network Element Management Unit is responsible for RNC element management tasks. It
provides an interface to the higher level network management functions and to local user interface
functions.
OMU - Operation and Maintenance Unit maintains the radio network configuration and recovery. It also
contains basic system maintenance functions and serves as an interface between the RNC and the
Network Element Management Unit.
TBU - Timing and Hardware Management Bus Unit is responsible for the network element
synchronization, timing signal distribution, and message transfer functions in the hardware
management system.
ICSU - Interface Control and Signaling unit performs RNC functions, that are highly dependent on the
signaling to other network elements, and handles the distributed radio resource management related
tasks of the RNC.
GTPU GPRS Tunneling Protocol Unit performs RNC related functions towards the serving GPRS
support node.
DMCU - Data and Macro Diversity Combining Unit performs RNC related user and control plane
functions.
2.2.2 RNC Capacity
As illustrated in Figure 3, Nokia RNC450 has 3 capacity steps. Each configuration has a corresponding
capacity limit in terms of throughput, Node B and cell counts, and AAL2 connections. With the smallest
configuration, only the first RNC cabinet is needed. The maximum configuration requires two cabinets
with full configured plug-in unit amount.
The table below shows the maximum capacity of Nokia RNC for RAS05.1 and RAS06 software release.
Release
RAS 05.1
RAS 06
RNC
Throughput
(Mbps)
450
1000
Number
of BTS
Number
of cells
No of HSDPA No of HSDPA
activated
activated
BTSs
cells
512
1152
512
1152
768
1728
768
1728
Table 5. Maximum RNC Capacity per Release
AAL2
Connectivity
(Mbps)
3594
3594
HSDPA
traffic
(Mbps)
450
1000
In RAS 05.1, the throughput increases to 450 Mbps as compared to previous SW releases due to new
RNC hardware. The maximum number of BTSs that can be connected also increases but the number of
cells supported remains with 1152.
The RAS 06, also known as RNC1000, can provide up to 1 Gbps throughput and 768 BTS connections.
Version 1.3
Jacinto

Nokia
3
3.1
Channel Element Dimensioning

Nokia Flexi WCDMA BTS System Module (FSM)
This section provides the guidelines for dimensioning the Flexi BTS Channel Elements and System
Module.
The Flexi BTS System Module comes up with two types, the FSMA and FSMB. FSMB will be used for the
deployment. One FSMB has three sub modules, each with 80 CEs, which provides an FSMB entity with
240 CEs. Up to 2 FSMB can be cascaded which can provide a capacity of 480 Channel Elements. But for
RAS05.1, the Flexi SW architecture which is based on Ultrasites limit the SW capacity to 64 CEs per sub
module thus the CE capacity is 192 for one module (64 CEs for each sub module) and 384 CEs for 2
FSMB. The software optimization required to increase the capacity of FSMB to its maximum hardware
capacity will be available in RAS06.
Note that the channel elements are pooled among the modules, but each call must be handled only by
one sub-module. If the resources are not enough, a call can be moved to other available sub-modules
with enough capacity.
The number of channel elements and modules per Node B would depend on the traffic mix, the
number of control channels and the HSDPA requirements. Refer to Table 4 for the number of channel
elements needed for each service. Note that the Number of CEs needed for Control Channels will
increase from 16 to 26 CEs in RAS06.
Services
PS: 8 kbps, 16 kbps
CS: 12.2 kbps AMR
PS: 32 kbps
PS: 64kbps, 128 kbps (including ADCH)
CS: 64 kbps
PS: 256 kbps
PS: 384 kbps (including ADCH)
HSDPA scheduler reserved blocks for 5 codes (UL and DL)
HSDPA UL SRB: 3.4 kbps
Control Channels
CEs Required
1
2
4
8
16
32
1
16
Table 6. Number of CEs needed for different services

In Nokia Node B, the channel elements are asymmetrically allocated, which means that the CEs are
allocated separately in uplink and downlink. Thus the CE requirements for the Node B must be
computed separately for UL and DL using the individual service bit rates, and consider which among
the UL and DL CE requirements is higher.
For HSDPA, aside from the 32 CEs reserved for HS-DSCH downlink traffic, the corresponding A-DCH
(Associated DCH) on uplink and SRB (Signaling Radio Bearer) on downlink must be considered. For UL
A-DCH the channel elements needed is based on the bearer rate, while for DL SRB only one CE is used
in each connection. In RAS05.1 the number of HSDPA users can be increased up to 16 users per cell
but this would also require additional CEs to support it. For 16 HSDPA users per Node B, 32 CEs are
required and for 16 HSDPA users per cell, 32*3=96 CEs are needed.
Inputs Required:
- number of subscribers per Node B and
- Traffic usage per subscriber per application: AMR, CS64, PS64, PS128, PS384, PS512 UL/DL
Version 1.3
Jacinto
10

Nokia
Or
Traffic usage per application
Assumptions:
- Soft Handover Overhead (SHO) = 30%
Dimensioning Process:
1. Compute separately for UL and DL CE Requirements
- Determine the total traffic per application per Node B.
- Based on Table 4, compute the number of CEs required per application (R99 CE).
- Compute CEs needed by A-DCH based on HSDPA bearer rate for UL and 1 CE on each
connection for DL.
- Add the CEs required for R99 and HSDPA A-DCH
2.
Compute for the Soft Handover CE Requirement by multiplying the above result by SHO.
3.
Add the CEs for HSDPA scheduler reserved block
4.
Add the CEs needed for control channels.
5. Sum up the CEs required for R99 and A-DCH, SHO, HSDPA scheduler and control channels to get the
total required CEs for UL and DL.
6. Compare the DL and UL CE requirements; use the higher value to compute the number of FSMB
modules required: 1 FSMB = 192 CEs (RAS05.1)
Example:
Node B with 3 sectors, FSMB modules
BH Traffic mix: 12 x AMR, 3 x CS64, 5 x 64/128 PS, 2 x 64/384 PS, 2 x 384/HSPDA
SHO = 30%
Max 16 HSDPA users per BTS
-
Compute for the DL and UL CE Requirements
Number of users
12
3
5
2
2
R99 and ADCH Reqt
SHO Requirements
HSDPA scheduler
Control Channels
Total CEs Required
FSMB Required
Services
12.2 kbps AMR
CS 64 kbps
PS 64/128 kbps
PS 64/384 kbps
384 A-DCH HSDPA
UL CE Requirement
DL CE Requirement
12*1 = 12
12*1 = 12
3*4 = 12
3*4 = 12
5*4 = 20
5*4 = 20
2*4 = 8
2*16 = 32
2*16 = 32
2*1 = 2
84
78
84*0.3= 26
78*0.3 = 24
32
32
16
16
158
150
=158/192 = 0.82 = 1 FSMB module
Table 7. Flexi BTS CE dimensioning example
For Multi RAB configurations where an MS can have 2 or more simultaneous services, the CEs needed
to support such is still the sum of the CEs for each service. For example, an MS having AMR + 3 PS64
would require 1+3*4=15 CEs.
Version 1.3
Jacinto
11

Nokia
Iub Dimensioning
The Iub interface is the ATM connection between the Node B and RNC. Each ATM connection, which is
also called as CoCo (Connection Configuration) in Nokia, is defined as ATM VP (Virtual Path) that is
consists of several VCs (Virtual Channels). These VCs define the Iub bandwidth requirements and are
composed of the control plane and user plane links. The figure below shows the VC configuration in
Nokia Iub.
VC1 USER PLANE
Flexi
BTS
VC2 AAL2 SIGNALING
RNC
VC3 DNBAP
VC4 CNBAP
VC4 O&M
AXC
(AXCC,
AXCD,
AXUA)
Iub
Figure 4. Nokia Iub Configuration

Virtual Channel (VC)
User Plane
AAL2 Signalling
DNBAP
CNBAP
O&M
Number of VCs Required

1 VC = 248 AAL2 connections
1 per Node B
1 per Node B
1 per Node B
1 per Node B
QoS
CBR
CBR
CBR
CBR
UBR
Table 8. Nokia Iub Virtual Channel Requirement

The required Iub bandwidth then is the sum of the user planes, control planes: AAL2 Signaling, DNBAP,
CNBAP and O&M.
The user plane VCs are used for the transport of the following channels: CCCH (Common Control
Channel), DCCH (Dedicated Control Channel) and DTCH (Dedicated Traffic Channel).
The AAL2 Signaling is used for setup and release of AAL2 connections inside the user plane VCs.
The DNBAP (Dedicated Node B Application Part) handles all the signaling after the radio link setup
procedure which includes the Radio Link measurement reports, deletion commands, reconfiguration
messages and soft handover related commands.
The CNBAP (Common Node B Application Part) defines the signaling procedure across the common
signaling link such as establishing radio links and various broadcast information and indication
messages.
O&M (Operation and Maintenance) defines all the logical BTS O&M such as fault and configuration
management.
Version 1.3
Jacinto
12

Nokia
4.1
User Plane Iub Bandwidth
The Iub traffic requirement must be computed for each service and consider the applicable protocol
overheads and dimensioning factors.
Services
Activity Factor
12.2 kbps AMR

CS 64 kbps
PS 64 kbps
PS 128 kbps
PS 384 kbps
HSDPA
67%
100%
100%
100%
100%
100%
Table 9.
SHO Percentage
Protocol/ATM
Overhead
30%
55%
30%
25%
30%
28%
30%
25%
30%
23%
21 43%
Iub User Plane Dimensioning Assumptions
Throughput
Factor
26.5%
26.5%
26.5%
26.5%
The activity factor indicates the percent of time the bandwidth allocated in each service is being used.
In voice for example, the AMR user usually talks and sends information 50 67% of the entire holding
time.
The SHO factor is the additional resources consumed by soft handover. No soft handover for HSDPA as
of RAS05.
The protocol overhead includes the following: RLC overhead for PS, FP, AAL2 overhead and ATM cell
overhead. The RLC (Radio Link Control) protocol is for segmentation, reassemble and retransmission of
data, RLC overhead is usually 5%. FP (Frame Protocol) overhead depends on the bit rate, and varies
from 3-19%. AAL2 overhead is 3 bytes per packet + 1 byte per ATM cell. ATM cell overhead is 10.4%,
5 bytes for each 53 bytes ATM cell.
The throughput factor, also known as L1 adaptation factor, indicates the overhead needed to achieve
the full rate in the air interface and Iub not limiting the rates achievable.
Inputs Required:
- number of subscribers per Node B and
- Traffic usage per subscriber per application: AMR, CS64, PS64, PS128, PS384, PS512
Or
- Traffic usage per application
1. Compute for the bandwidth requirement for each service based on the following procedures:
For voice, 12.2 kbps AMR:
1. Get the total voice traffic in Erlangs.
2. Using Erlang B @ 2% GoS, compute the number of traffic channels.
3. Multiply the number of traffic channels by the bit rate (12.2 kbps), SHO factor
(1+SHO) and activity factor.
4. Multiply by the protocol overhead for voice to get the total Iub traffic for voice.
Iub dimensioning for CS64:
1. Get the total CS64 traffic in Erlangs.
2. Using Erlang B @ 2% GoS, compute the number of traffic channels.
3. Multiply the number of traffic channels by the bit rate (64 kbps), SHO factor (1+SHO)
and activity factor.
4. Multiply by the protocol overhead for CS64 to get the total Iub traffic for CS64.
Iub dimensioning for Packet Switched data:
1. Get the total packet switched traffic per bearer.
Version 1.3
Jacinto
13

Nokia
2. Multiply by the activity factor, SHO factor (1+SHO), protocol overhead and L1
adaptation rate factor.
The Packet switched data traffic must be calculated separately for each radio bearer (PS64,
PS128, PS256, PS384).
2. The total user plane Iub traffic then is equal to the sum of the voice, CS64, PS64, PS128, PS256,
PS384 Iub bandwidth requirements.
4.2
Control Plane Iub Bandwidth
The estimated signaling bandwidth requirement for Iub is typically 6-7% of Iub capacity or 8-10% of
the user plane bandwidth. This signaling bandwidth is divided between the AAL2 Signalling, DNBAP and
CNBAP with the ratio of 1:2:1. In initial network set-up, the signaling bandwidth of Iub can be allocated
this way but on operating the network the CNBAP and DNBAP can be calculated. For CNBAP, the load
can be estimated using the following formula:
CNBAP = 3+RL_setups/sec*RL_setup_msg_size+RRI_msg_size/RR_ind_period
Where:
RL_setups/sec is the Radio Link setups per second
RL_setup_msg_size is the size of the RL setup response message, typically 2 atm cells
RRI_msg_size is the radio resource indication message size, estimated to be 4 atm cells for 1-3
WCDMA cells
RR_ind_period is the reporting period of the Radio Resource Indication messages, equal to 200 ms.
The DNBAP bandwidth on the other hand depends on the simultaneous PS calls, approximately 13 cps
is needed for each PS call.
The AAL2 signaling bandwidth can be estimated using the ratio 1:2:1 of AAL2 signaling, DNBAP and
CNBAP.
The minimum link size for the AAL2 signaling, DNBAP and CNBAP is 39 cps and the maximum is 2100
cps per VC.
For the O&M (Operation and Maintenance) link, Nokia recommends 150 cps or 64 kbps per BTS.
Example:
Node B with 3 sectors, FSMB modules only
BH Traffic mix: 12 x AMR, 3 x CS64, 5 x 64/128 PS, 2 x 64/384 PS, 2 x 384/HSPDA
SHO = 30%
-
Compute for the user plane traffic in UL and DL
For UL:
Iub voice = no. of channels * bit rate * (1+SHO) * activity factor * protocol overhead
= 12*12.2*1.30*0.67*1.55
= 197.65 kbps
Iub CS64 = no. of channels * bit rate * (1+SHO)* activity factor * protocol overhead
= 3*64*1.30*1.0*1.25
= 312 kbps
Version 1.3
Jacinto
14

Nokia
Iub PS64/128 = no. of channels * bit rate * (1+SHO) * activity factor * protocol overhead *
throughput factor
= 5*64*1.30*1.0*1.28*1.265
= 673.59 kbps
Iub PS64/384 = no. of channels * bit rate * (1+SHO) *activity factor * protocol overhead *
throughput factor
= 2*64*1.30*1.0*1.28*1.265
= 269.43 kbps
Iub 384ADCH = no. of channels * bit rate * (1+SHO) * activity factor * protocol overhead *
throughput factor
= 2*384*1.30*1.0*1.23*1.265
= 1553.46 kbps
UL user plane requirement = Iub voice+Iub CS64 + Iub PS64/128 + Iub PS64/384 + Iub 384ADCH
= 197.65 + 312 + 673.59 + 269.43 + 1553.46 kbps
= 3006.13 kbps or 7090 cps
For DL:
= 12*12.2*1.30*0.67*1.55
= 197.65 kbps
Iub CS64 = no. of channels * bit rate * (1+SHO)* activity factor * protocol overhead
= 3*64*1.30*1.0*1.25
= 312 kbps
Iub PS64/128 = no. of channels * bit rate * (1+SHO) * activity factor * protocol OH* throughput
factor
= 5*128*1.30*1.0*1.25*1.265
= 1315.6 kbps
Iub PS64/384 = no. of channels * bit rate * (1+SHO) * activity factor * protocol OH* throughput
factor
= 2*384*1.30*1.0*1.23*1.265
= 1553.46 kbps
Iub HSDPA = no. of channels * bit rate * activity factor * protocol overhead * throughput factor
= 32*16*1.0*1.43*1.265
= 926.18 kbps
DL user plane requirement = Iub voice + Iub CS64 + Iub PS64/128 + Iub PS64/384 + Iub HSDPA
= 197.65 + 312 + 1315.6 + 1553.46 + 926.18 kbps
= 4304.89 kbps or 10153 cps
-
Compare the uplink and downlink requirements, the higher value will be used as the user plane
Iub bandwidth requirement.
User Plane Bandwidth = 4304.89 kbps or 10153 cps

-
Compute for the control plane bandwidth. Initially it can be assumed that the signaling
bandwidth requirement is 10% of the user plane traffic. But when the network is already
operating and actual statistics are present, the computations for CNBAP and DNBAP stated
above should be used.
Control Plane Bandwidth = 10%*total user plane bandwidth

= 0.10*10153 cps = 1016 cps
Using the ratio 1:2:1 of AAL2 signaling, DNBAP and CNBAP:
AAL2 Signaling = 254 cps
Version 1.3
Jacinto
15

Nokia
DNBAP = 508 cps

CNBAP = 254 cps
O&M = 150 cps (recommended per Node B)
-
Compute for the total Iub requirement by adding the user plane, control plane and O&M
requirements.
Iub Requirement = User Plane + Control Plane + O&M
= 10153 + 1016 + 150 cps
= 11319 cps or 4800 kbps
Number of users
12
3
5
2
2
User Plane Reqt (kbps)
User Plane Reqt (cps)
Services
12.2 kbps AMR
CS 64 kbps
PS 64/128 kbps
PS 64/384 kbps
384 A-DCH HSDPA
Iub Requirement UL
197.65 kbps
312 kbps
673.59 kbps
269.43 kbps
1553.46 kbps
3006.13 kbps
7090 cps
Iub Requirement DL
197.65 kbps
312 kbps
1315.6 kbps
1553.46 kbps
926.18 kbps
4304.89 kbps
10153 cps
AAL2 signalling
DNBAP
CNBAP
Contro Plane Reqt
O&M
178 cps
354 cps
178 cps
710 cps
150 cps
254 cps
508 cps
254 cps
1016 cps
150 cps
Iub Reqt (cps)

Iub BW Requirement
7950 cps
11319 cps
11319 cps or 4.8 Mbps or 4 T1s
Table 10. Iub Dimensioning example
USER PLANE VCs
Flexi
BTS
10153 cps
AAL2 SIGNALING VC
254 cps
DNBAP VC
508 cps
CNBAP VC
254 cps
O&M VC
150 cps
AXC
(AXCC,
AXCD,
AXUA)
RNC
Iub
Figure 5. Iub Configuration example
Version 1.3
Jacinto
16

Nokia
RNC Dimensioning
The number of Nokia RNCs to be deployed in the network can be dimensioned based on the RNC
throughput requirement, Node B and cell counts, AAL2 connectivity for Iub, Iur and IuCS interfaces and
other limiting factor such as the number of available interfaces and VP shapers. The table below shows
the RNC capacity limitations for Nokia RAS05.1.
RNC Config
150
300
450
Iub Throughput
(Mbps)
150
300
450
Number of
Number of
AAL2 Connectivity
Node B
cells
(Mbps)
200
600
1,950
300
900
2,800
512
1,152
3,594
Table 11. Nokia RAS05.1 RNC Capacity
Interface Cards
STM1 / T1
4/16
8/16
12/16
The RNC throughput is the sum of the bandwidth of the different services including the soft handover
overhead or simply the sum of the Iub throughput of all the Node Bs connected to the RNC. The AAL2
Connectivity is the sum of the Iub, Iur and IuCS bandwidths.
For dimensioning a new network, the fill rate is typically 60-70% to allow network expansions. On
operating network, 80-90% can be considered.
Aside from the above considerations in dimensioning the RNC, HSDPA requirement must also be
considered when we need to ensure that the maximum achievable bit rates will be available to the
users or when we have to dedicate resources for possible HSDPA users. The table below shows the
maximum number of HSDPA activated BTS, throughput and users.
RNC Config
150
300
450
Max No of HSDPA
HSDPA Net
Max HSDPA
activated BTS
Throughput (Mbps)
users per cell
200
135
16
300
270
16
512
405
16
Table 12. Nokia RNC HSDPA Capacity
Max no of HSDPA
users
290
580
1500
Inputs
-
Required:
Iub Throughput Requirement
Number of Node Bs and cells to be connected
Number of subscribers per Node B and
Traffic usage per subscriber per application: AMR, CS64, PS64, PS128, PS384, PS512
Or
- Traffic usage per application
Assumptions:
- SHO = 30%
- Fill rate = 60-70% for new network, 80-90% for operating network
1. Compute for the RNC throughput requirements, by computing the throughput required by each
Node B considering all the different services, soft handover overhead, and protocol overheads.
Or by considering the Iub throughput for each Node Bs (refer to section 3).
2. Calculate the number of required RNCs based on the Iub throughput.
Number of RNC (throughput) = Iub throughput reqt/(RNC throughput*fill rate)
Version 1.3
Jacinto
17

Nokia
3. Calculate the number of required RNCs based on BTS and cell capacity.
Number of RNC (BTS) = number of connected BTS / (BTS capacity*fill rate)
Number of RNC (cell) = number of cells connected / (cell capacity*fill rate)
4. Compute the total AAL2 connectivity by adding up the bandwidth requirements for Iub, Iur and
IuCS.
AAL2 connectivity (Mbps) = Iub + Iur + IuCS
Iur traffic depends on the RNC coverage areas, number of border cells in inter-RNC SHO areas,
and number of neighbor RNCs. For dimensioning purposes, Nokia recommends an assumption that
the Iur traffic is 4-9% of total Iub traffic.
IuCS, on the other hand, can be computed based on the circuit switched traffic (AMR and
CS64) and corresponding signaling and ATM overheads. For IuCS, 25% ATM OH and 1% signaling
OH are used for the bandwidth calculation.
IuCS = (AMR users*12.2 kbps + CS64 users*64 kbps)*Protocol overhead*Signaling overhead
5. Calculate the number of required RNCs based on AAL2 connectivity.
Number of RNC (AAL2 connectivity) = Required AAL2 connectivity / (AAL2 capacity*fill rate)
6. Compare the computed number of RNCs based on throughput, BTS/cell count and AAL2
connectivity. The highest RNC requirement must be considered.
7. The number of available interfaces and VP shapers must be enough to support the connected
Node Bs.
Refer to Table 9 for the number of available interfaces in each RNC.
If traffic shaping is enabled there is a limit of 108 VPs on each NIS or NIP card, without traffic
shaping 600 VPs can be defined in each NIS/NIP card.
Example:
100 Node Bs, each has the following specs:
Traffic mix: 12 x AMR, 3 x CS64, 5 x 64/128 PS, 2 x 64/384 PS, 2 x 384/HSPDA
Iub throughput as computed on Table 8 is 5.08 Mbps
Assumptions:
Iur = 5% of Iub bandwidth
RNC with full config will be used
Channelized STM-1 connection from Node B to RNC (1 STM-1 = 63 E1s or 84 T1s)
Traffic shaping is enabled
90% RNC fill rate
-
Compute for the RNC throughput requirements and the corresponding number of RNCs needed
to support it:
As computed earlier, each node B has an Iub throughput requirement of 4.8 Mbps, thus:
RNC throughput requirement = sum of all Node B Iub Requirements
= 100 * 4.8 Mbps
= 480 Mbps
Number of RNC (throughput) = 480/(450*0.9) = 2 RNCs
-
Calculate the number of RNCs required based on number of BTSs and cells.
Version 1.3
Jacinto
18

Nokia
Number of RNC (BTS/cell) = BTS or cells to be connected / (BTS or cell capacity * fill rate)
= 100/(512*0.9) = 1 RNC
= 300/(1152*0.9) = 1 RNC
-
Compute for the AAL2 connectivity by adding the Iub, Iur and IuCS bandwidths, then compute
the required number of RNCs based on AAL2 connectivity.
Iub bandwidth = 100*4.8 Mbps = 480 Mbps

Iur = 5%*Iub = 0.05*480 Mbps = 24 Mbps
= 100*(12*12.2 kbps + 3*64 kbps)*1.25*1.01
= 42.72 Mbps
AAL2 Connectivity = Iub + Iur + IuCS
= 480 + 24 + 42.72 Mbps
= 546.72 Mbps
Number of RNC (AAL2 connectivity) = 546.72/(3594*0.09) = 1 RNC
-
Based on the above computations, 2 RNCs are needed to satisfy all the dimensioning
requirements.
Number of required RNC = 2

-
Verify if the number of STM-1 interfaces would be enough to provide connections to Node B,
other RNCs, MSC and SGSN.
Based on Iub computations, 4 T1s per Node B, with 100 Node Bs 400 T1s are needed.
Number of STM-1 connections = sum of STM-1 for Iub, Iur, IuCS and IuPS
For Iub, 400/84 = 5 STM1, 3 STM1 for each RNC
For Iur = 24 Mbps for 2 RNC, 1 STM1
For IuCS = 42.72 Mbps for 2 RNC, 1 STM1
For IuPS = 242.4 Mbps for 2 RNC, 1 STM1
IuPS = (PS users*bit rate)*Protocol overhead*Signaling overhead
= 100*(5*128+2*384+32*16)*1.25*1.01
= 242.4 Mbps
Number of STM-1 connections = 5 STM-1 connections per RNC (1 RNC can support all the interface
connections needed)
-
Verify the VP limit per NIS card.

There are 4 NIS per RNC and each RNC can have 108 VPs, thus total of 432 VPs, more than
enough to accommodate the 100 Node Bs and Iu connections.
Dimensioning factors
Iub throughput
BTS count
Cell count
AAl2 connectivity
Version 1.3
Jacinto
Requirement
RNC Capacity
480 Mbps
450 Mbps
100
512
300
1152
546.72 Mbps
3594 Mbps
Required RNC = 2
Table 13. RNC Dimensioning example
Required No of RNC
2
1
1
1
19

Nokia
Iu Interface Dimensioning
The Iu interface is the connection from the radio access network to the core network. It has separate
user and control planes, the user plane uses AAL2 for IuCS and AAL5 for IuPS while the control plane is
AAL5.
6.1
Iu-CS Interface
The Iu-CS interface connects the radio access network to the circuit switched core network, between
an RNC and an MSC.
User Plane transfers user data related to radio access bearers over the Iu interface. It can be defined
as transparent mode where all traffic has predefined SDU sizes or support mode where SDU sizes
change during the connection such as in AMR call.
Control Plane RANAP (Radio Access Network Application Part) handles the signaling between the RNC
and MSC or SGSN.
The control plane in the Iu-CS can be terminated in the MSC server and the user plane can be
terminated in the MGW
Dimensioning Process
User Plane:
- Calculate the bandwidth requirements for Circuit Switched service.
- Multiply by the Protocol overhead (25%)
Control Plane:
- 1% of Iu-CS User Plane
Iu-CS Bandwidth = User Plane + Control Plane
Example:
Iu-CS User Plane = 100*(12*12.2+3*64)*(1.25) = 42. 3 Mbps
Iu-CS Control Plane = 1%*42.3 Mbps = 423 kbps
Iu-CS Bandwidth = 42.3 Mbps + 423 kbps = 42.72 Mbps
USER PLANE VCs
42.3 Mbps
MSC/
MGW
RNC
CONTROL PLANE VC
423 kbps
Iu-CS
Figure 6. Iu-CS Configuration example

Version 1.3
Jacinto
20

Nokia
6.2
Iu-PS Interface
The Iu-PS interface connects the radio access network to the packet switched core network, between
the RNC and SGSN
User Plane transfers user data related to radio access bearers over the Iu interface, the transparent
mode is used.
Control Plane RANAP (Radio Access Network Application Part) handles the signaling between the RNC
and MSC or SGSN.
Dimensioning Process
User Plane:
- Calculate the bandwidth requirements for Packet Switched services for both uplink and downlink
- Get the maximum between the uplink and downlink requirements and multiply by the Protocol
overhead (25%)
Control Plane:
- 1% of Iu-PS User Plane
Iu-PS Bandwidth = User Plane + Control Plane
Example:
UL User Plane = 100*(5*64+2*64+2*384) = 121.6 Mbps
DL User Plane = 100*(5*128+2*384+2*512) = 192 Mbps
Iu-PS User Plane = 192*1.25 = 240 Mbps
Iu-PS Control Plane = 1%*240 Mbps = 2.4 Mbps
Iu-PS Bandwidth = 240 + 2.4 Mbps = 242.4 Mbps
USER PLANE VCs
242.2 Mbps
RNC
CONTROL PLANE VC
3G
SGSN
2.4 Mbps
Iu-PS
Figure 7. Iu-PS Configuration example
Version 1.3
Jacinto
21

Nokia
Summary of Formulas and Counters
Listed below are the formulas used in this document, and Nokia RNC counters that can be used as
dimensioning inputs when there is already a considerable amount of network traffic.
7.1
Channel Element Dimensioning Formulas
UL CE Requirement = [sum of CEs per application + CE (hsdpa adch)]*(1+SHO) + CEs for HSDPA
scheduler + CEs for Control Channels
DL CE Requirement = [sum of CEs per application + CE (hsdpa adch)]*(1+SHO) + CEs for HSDPA
scheduler + CEs for Control Channels
Total CEs Required = max (UL CE Requirement, DL CE Requirement)
Number of FSM cards = roundup (Total CEs Required / CE capacity per card)
7.2
Iub Dimensioning Formulas
Iub CS = no. of channels * bit rate * (1+SHO)* activity factor * protocol overhead
Iub PS = no.of channels * bit rate * (1+SHO) * activity factor * protocol overhead*throughput factor
Iub ADCH / HSDPA = no.of channels * bit rate * (1+SHO) * activity factor * protocol overhead *
throughput factor
UL User Plane Bandwidth = Iub voice + Iub CS + Iub PS + Iub ADCH
DL User Plane Bandwidth = Iub voice + Iub CS + Iub PS + Iub HSDPA
User Plane Bandwidth = max (UL User Plane Bandwidth, DL User Plane Bandwidth)
Control Plane Bandwidth = 10% * User Plane Bandwidth
AAL2: DNBAP: CNBAP = 1:2:1 of Control Plane Bandwidth
O&M = 150 cps
Iub Requirement = User Plane Bandwidth + Control Plane Bandwidth + O&M
7.3
RNC Dimensioning Formulas
RNC Throughput Requirement = sum of Iub Requirements of connected Node Bs

Number of RNC (throughput) = Iub throughput reqt/(RNC throughput*fill rate)
Number of RNC (BTS) = number of connected BTS / (BTS capacity*fill rate)
Number of RNC (cell) = number of cells connected / (cell capacity*fill rate)
Version 1.3
Jacinto
22

Nokia
AAL2 connectivity (Mbps) = Iub + Iur + IuCS

Iur = 5% * Iub Requirements
AAL2 Connectivity = Iub + Iur + IuCS
Number of RNC (AAL2 connectivity) = AAL2 Connectivity/(AAL2 capacity*fill rate)
Number of STM-1 connections = sum of STM-1 for Iub, Iur, IuCS and IuPS
IuPS = PS users * bit rate * Protocol Overhead * Signaling Overhead
RNC Requirement = max [Number of RNC (throughput), Number of RNC (BTS), Number of RNC (cell),
Number of RNC (AAL2 connectivity)]
7.4
Nokia Counters
When there is already a sufficient amount of traffic in the UMTS network, the following counters can be
used for getting the actual number of connections for each service that can be used as input to the
dimensioning process.
PI ID
Name
NodeB_Cell Resource
M5001C0
MAXIMUM NUMBER OF AVAILABLE CHANNEL ELEMENTS
M5001C1
MINIMUM NUMBER OF AVAILABLE CHANNEL ELEMENTS
M5001C2
AVERAGE NUMBER OF AVAILABLE CHANNEL ELEMENTS
M5001C3
MAXIMUM NUMBER OF USED CE FOR DL
M5001C4
MAXIMUM NUMBER OF USED CE FOR UL
M5001C5
MINIMUM NUMBER OF USED CE FOR DL
M5001C6
MINIMUM NUMBER OF USED CE FOR UL
M5001C7
AVERAGE NUMBER OF USED CE FOR DL
M5001C8
AVERAGE NUMBER OF USED CE FOR UL
RNC Cell resource
M1000C181
M1000C182
NUMBER OF SAMPLES FOR CE CALCULATION

AVERAGE USED CE FOR AMR ALLOCATIONS
M1000C183
AVERAGE USED CE FOR CS CONVERSATIONAL 64 KBPS
M1000C184
AVERAGE USED CE FOR CS STREAMING 14.4 KBPS
M1000C185
AVERAGE USED CE FOR CS STREAMING 57.6 KBPS
M1000C186
AVERAGE USED CE FOR PS STREAMING 8 KBPS UL
M1000C187
M1000C188
M1000C189
M1000C190
M1000C191
M1000C192
AVERAGE USED CE FOR PS STREAMING 8 KBPS DL

Version 1.3
Jacinto
Abbreviation
MAX_AVAIL_CE
MIN_AVAIL_CE
AVE_AVAIL_CE
MAX_USED_CE_DL
MAX_USED_CE_UL
MIN_USED_CE_DL
MIN_USED_CE_UL
AVG_USED_CE_DL
AVG_USED_CE_UL
CE_SAMPLE_AMOUN
T
AVE_CE_USED_AMR
AVE_CE_USED_CS_C
ONV_64
AVE_CE_USED_CS_S
TR_14_4
AVE_CE_USED_CS_S
TR_57_6
AVE_CE_USED_PS_S
TR_8_UL
AVE_CE_USED_PS_S
TR_16_UL
AVE_CE_USED_PS_S
TR_32_UL
AVE_CE_USED_PS_S
TR_64_UL
AVE_CE_USED_PS_S
TR_128_UL
AVE_CE_USED_PS_S
TR_8_DL
AVE_CE_USED_PS_S
23

Nokia
M1000C193
M1000C194
M1000C195
M1000C196
M1000C197
M1000C198
AVERAGE USED CE FOR PS INTERACTIVE 8 KBPS UL
M1000C199
M1000C200
M1000C201
M1000C202
M1000C203
M1000C204
M1000C212
AVERAGE USED CE FOR PS BACKGROUND 8 KBPS UL
M1000C213
M1000C214
M1000C215
M1000C216
M1000C217
M1000C218
M1000C219
AVERAGE USED CE FOR PS BACKGROUND 8 KBPS DL
M1000C220
M1000C221
M1000C222
M1000C223
M1000C224
M1000C225
RAB downgrade/release due to BTS Congestion
M1000C146
M1000C151
M1000C158
TR_16_DL
AVE_CE_USED_PS_S
TR_32_DL
AVE_CE_USED_PS_S
TR_64_DL
AVE_CE_USED_PS_S
TR_128_DL
AVE_CE_USED_PS_S
TR_256_DL
AVE_CE_USED_PS_S
TR_384_DL
AVE_CE_USED_PS_IN
T_8_UL
AVE_CE_USED_PS_IN
T_16_UL
AVE_CE_USED_PS_IN
T_32_UL
AVE_CE_USED_PS_IN
T_64_UL
AVE_CE_USED_PS_IN
T_128_UL
AVE_CE_USED_PS_IN
T_256_UL
AVE_CE_USED_PS_IN
T_384_UL
AVE_CE_USED_PS_B
GR_8_UL
AVE_CE_USED_PS_B
GR_16_UL
AVE_CE_USED_PS_B
GR_32_UL
AVE_CE_USED_PS_B
GR_64_UL
AVE_CE_USED_PS_B
GR_128_UL
AVE_CE_USED_PS_B
GR_256_UL
AVE_CE_USED_PS_B
GR_384_UL
AVE_CE_USED_PS_B
GR_8_DL
AVE_CE_USED_PS_B
GR_16_DL
AVE_CE_USED_PS_B
GR_32_DL
AVE_CE_USED_PS_B
GR_64_DL
AVE_CE_USED_PS_B
GR_128_DL
AVE_CE_USED_PS_B
GR_256_DL
AVE_CE_USED_PS_B
GR_384_DL
RB DOWNGRADE BY PBS DUE TO BTS CONGESTION

RB DOWNGRADE BY PRE-EMPTION DUE TO BTS CONGESTION
RB RELEASE BY PBS DUE TO BTS CONGESTION
M1000C163
RB RELEASE BY PRE-EMPTION DUE TO BTS CONGESTION
Transmit Output Power Monitoring based on available counters
Version 1.3
Jacinto
24

Nokia
M1000-C20
M1000-C21
M1000-C22
Average PTx Feasible Load Area 3

Total Ptx Tot Feasible Load Area 3
Average PTx Feasible Load Area 4
Ave PtxTot Class 3

PtxTot Denom 3
Ave PtxTot Class 4
M1000-C23
Total Ptx Tot Feasible Load Area 4

Estimated average transmitted power for DL RT users on the
cell for Class 3
Ptx total value is inside Class 3 range
Estimated average transmitted power for DL RT users on the
cell for Class 4
PtxTot Denom 4
Ptx RT Denom 4
M1000-C52

Estimated average transmitted power for DL NRT users on the
cell for Class 3
Estimated average transmitted power for DL NRT users on the
cell for Class 4
M1000-C53
Ptx NRT Denom 4
M1000-C99
M1000-C100
M1000-C101
M1000-C102
M1000-C50
M1000-C51
Ave Ptx RT Class 3

Ptx RT Denom 3
Ave Ptx RT Class 4
Ave Ptx NRT Class 3

Ptx NRT Denom 3
Ave Ptx NRT Class 4
SCCPCH Load Monitoring based on available counters

M1000-C64
M1000-C65
M1000-C70
Average load of SCCPCH chanel including PCH

Denominator for Average load of SCCPCH channel (including
PCH)
PCH throughput
M1000-C71
Denominator for Average PCH throughput
M1000-C103
M1000-C104
Average load of SCCPCH channel -PCH not present

Denominator for Average load of SCCPCH channel (excluding
PCH)
M1000-C105
Average FACH throughput of both user data and signalling in

b/sec without PCH
M1000-C106
FACH User Tot Throughput Denom 1
M1000-C107
Average FACH throughput of user data only in bit/s for

SCCPCH - excluding PCH
M1000-C108
FACH User Data Throughput Denom 1
Ave SCCPCH inc PCH

Load
SCCPCH Load Denom
0
Ave PCH Throughput
PCH Throughput
Denom 0
Ave SCCPCH exc PCH
Load
SCCPCH Load Denom
1
Ave FACH User Tot
Throughput for
SCCPCH Exc PCH
FACH User Tot
Throughput Denom 1
Ave FACH Data
Throughput for
SCCHPCH exc PCH
FACH User Data
Throughput Denom 1
Spreading Factor Monitoring based on available counters

M1000-C72
Average code usage in percentage
M1000-C73
Denominator for average usage of code capacity
M1000-C74
Minimum code usage in percentage
M1000-C75
M1000-C76
maximum code usage in percentage

Number of tmes when no SF4 codes were available
M1000-C77
M1000-C78
M1000-C79
M1000-C80

Version 1.3
Jacinto
Average usage of Code

capacity
Denominator for
average usage of code
capacity
Minimum code
occupancy percentage
Max Code Occupancy
percentage
No Codes available SF4
No Codes available
SF8
No Codes available
SF16
No Codes available
SF32
No Codes available
25

Nokia
M1000-C81
M1000-C82
M1000-C83
The number of successful code tree allocations.
Radio Link Reports
M1000-C89
Average Transmission power per radio link in a cell
M1000-C90
Number of reported radio link during measurement period
Sum of squared measured values for transmission powers for
M1000-C91
the RL in the cell
Number of Radio link measurement reports during the
M1000-C92
measurement period
Traffic Measurement Area-RNC level
SF64
No Codes available
SF128
No Codes available
SF256
Nbr of Succ Code Tree
Allo
Ave Trx for RL in Cell
Nbr of RLS
Sum SQR TRX for RL
in Cell
Nbr of RL Meas Reps
M1002-C0
Total number of DCH request for a signalling link in the SRNC
DCH Req for Sig Link in

SRNC
M1002-C1
Total number of DCH request for a signalling link rejected in the

SRNC for reasons caused by UL radio resources.
DCH Req for SigLink

Reject in UL in SRNC
DCH Req for SigLink
Reject in DL in SRNC
DCH Req for RRC
Conn in SRNC
DCH Dho Reqq for Sig
link in SRNC
M1002-C12
Total number of DCH request for a signalling link rejected in the

SRNC for reasons caused by DL radio resources.
Total number of DCH request for a RRC connection
establishment in the SRNC
Total number of DCH request for a signalling link because of the
diversity handover in the SRNC
Total number of DCH request for a signalling rejected by the
SRNC for reasons caused by radio resources in the target cell of
the diversity handover
Total number of RT DCH requests for a CS voice call in the
SRNC
M1002-C13
Total number of RT DCH requests for CS voice call rejected in

the SRNC for reasons caused by UL radio resources
M1002-C2
M1002-C3
M1002-C4
M1002-C5
M1002-C17
Total number of RT DCH requests for CS voice call rejected in

the SRNC for reasons caused by DL radio resources
Total number of DCH requests for a CS voice call due to
diversity handover in the SRNC
Total number of DCH requests for a CS voice call rejected by the
SRNC for reasons caused by radio resources in the target cell of
diversity handover
M1002C18M1002C33
Number of real time DCH allocation for AMR x.xx in yL in the

SRNC. (AMR codec 12.2 - UL/DL)
M1002-C34M10020C49
Summary of RT DCH allocated durarions for AMR 12.2 in UL/DL

in SRNC
M1002-C50
Total number of RT DCH request for a transparent CS Data call

with conversational class in the SRNC
M1002-C14
M1002- C16
M1002-C51
M1002-C52
M1002-C53
Version 1.3
Jacinto
Total number of RT DCH request for a nontransparent CS data

call with streaming class in the SRNC
Total number of rejected RT DCH request for a transparent CS
Data call with conversational class in the SRNC fro reason
caused by UL radio resources
Total number of rejected RT DCH request for a transparent CS
Data call with conversational class in the SRNC fro reason
caused by DL radio resources
DCH DHO Req for Sig

Link Reject in SRNC
RT DCH Req for CS
Voice Call in SRNC
RT DCH Req for CS
Voice Call Reject in UL
in SRNC
RT DCH Req for CS
Voice Call Reject in DL
in SRNC
RT DCH DHO Req for
CS Voice call in SRNC
RT DCH DHO Req for
CS Voice call reject in
SRNC
RT DCH Allo for AMR
12.2 kbps in UL/DL in
the SRNC
RT DCH Allo Dura for
AMR 12.2 kbps in
UL/DL in the SRNC
RT DCH Req for CS
Data call Conv Class in
SRNC
RT DCH Req for CS
Data call Stream Class
in SRNC
RT DCH Req for CS
Data call Conv Class
RT DCH Req for CS
Data call Conv Class
26

Nokia
M1002-C54
M1002-C55
M1002-C58
M1002-C59
M1002-C60
M1002-C61
Total number of rejected RT DCH request for non transparent

CS Data call with streaming class in the SRNC fro reason
caused by UL radio resources
Total number of rejected RT DCH request for non transparent
CS Data call with streaming class in the SRNC fro reason
caused by DL radio resources
Total number of DCH request for a transparent CS data call with
conversation class due to diversity handoever in the SRNC
Total number of DCH requests for transparent CS data call
(onSRNC side) rejected for reasons caused by radio resources
in the target cell of diversity handover
Total number of DCH request for a nontransparent CS data call
with streaming class due to diversity handoever in the SRNC
Total number of DCH requests for nontransparent CS data call
with streaming class (onSRNC side) rejected for reasons caused
by radio resources in the target cell of diversity handover
RT DCH Req for CS

RT DCH Req for CS
RT DCH DHO Req for
CS Data Call Conv
Class in SRNC
RT DCH DHO Req for
CS Data Call Conv
Class Reject in SRNC
RT DCH DHO Req for
CS Data Call Stream
Class in SRNC
RT DCH DHO Req for
CS Data Call Stream
Class Reject in SRNC
ATM
The number
connection.
The number
connection
The number
connection.
The number
connection.
of egress cells transmitted to a virtual path

EG_TOT_CELLS_VP
of ingress cells received from a virtual path

IN_TOT_CELLS_VP
of egress cells transmitted to a virtual channel

EG_TOT_CELLS_VC
of ingress cells received from a virtual channel

N_TOT_CELLS_VC
Packet-Service
M1002-C82
RT DCH REQ FOR PS CALL CONV CLASS IN SRNC
M1002-C83
RT DCH REQ FOR PS CALL STREAM CLASS IN SRNC
M1002-C84
RT DCH REQ FOR PS CALL INTERA CLASS IN UL IN SRNC
M1002-C85
RT DCH REQ FOR PS CALL INTERA CLASS IN DL IN SRNC
M1002-C86
NRT DCH REQ FOR PS CALL BACKG CLASS IN UL IN SRNC
M1002-C87
NRT DCH REQ FOR PS CALL BACKG CLASS IN DL IN SRNC
M1002-C88
RT DCH REQ FOR PS CALL CONV CLASS REJECT IN UL IN SRNC
M1002-C89
RT DCH
RT DCH
SRNC
RT DCH
SRNC
RT DCH
SRNC
RT DCH
SRNC
RT DCH
SRNC
M1002-C90
M1002-C91
M1002-C92
M1002-C93
M1002-C94
Version 1.3
Jacinto
REQ FOR PS CALL CONV CLASS REJECT IN DL IN SRNC

REQ FOR PS CALL STREAM CLASS REJECT IN UL IN
REQ FOR PS CALL STREAM CLASS REJECT IN DL IN
REQ FOR PS CALL INTERA CLASS REJECT IN UL IN
REQ FOR PS CALL INTERA CLASS REJECT IN DL IN
REQ FOR PS CALL BACKG CLASS REJECT IN UL IN
27

Nokia
M1002-C95
RT DCH REQ FOR PS CALL BACKG CLASS REJECT IN DL IN

SRNC
M1002-C96
RT DCH INI REQ FOR PS CALL CONV CLASS IN SRNC
M1002-C97
RT DCH INI REQ FOR PS CALL STREAM CLASS IN SRNC
M1002-C98
NRT DCH INI REQ FOR PS CALL INTERA CLASS IN UL IN SRNC
M1002-C99
NRT DCH INI REQ FOR PS CALL INTERA CLASS IN DL IN SRNC
M1002-C100
NRT DCH INI REQ FOR PS CALL BACKG CLASS IN UL IN SRNC
M1002-C101
NRT DCH INI REQ FOR PS CALL BACKG CLASS IN DL IN SRNC
M1002-C347
RT DCH HHO REQ FOR PS CALL CONV CLASS IN SRNC
M1002-C348
RT DCH HHO REQ FOR PS CALL CONV CLASS REJECT IN SRNC
M1002-C349
M1002-C350
RT DCH HHO REQ FOR PS CALL STREAM CLASS IN SRNC

RT DCH HHO REQ FOR PS CALL STREAM CLASS REJECT IN
SRNC
M1002-C351
RT DCH HHO REQ FOR PS CALL INTERA CLASS IN SRNC
M1002-C352
RT DCH HHO REQ FOR PS CALL INTERA CLASS REJECT IN SRNC
M1002-C353
M1002-C354
NRT DCH HHO REQ FOR PS CALL BACKG CLASS IN SRNC

NRT DCH HHO REQ FOR PS CALL BACKG CLASS REJECT IN
SRNC
M1002-C475
DCH SELECTED FOR INTERACTIVE DUE TO MAX HSDPA USERS
M1002-C476
M1002C110 M1002C125
M1002C126 M1002C141
M1002C142 M1002C157
M1002C158 M1002C173
M1002C174 M1002C189
M1002C190 M1002C205
M1002C206 M1002C221
M1002C222 M1002C237
DCH SELECTED FOR BACKGROUND DUE TO MAX HSDPA USERS

RT DCH ALLO FOR PS CALL CONV CLASS x.xx KBPS IN yL IN
SRNC
RT DCH ALLO FOR PS CALL STREAM CLASS x.xx KBPS IN yL IN
SRNC
NRT DCH ALLO FOR PS CALL INTERA CLASS x.xx KBPS IN yL IN
SRNC
NRT DCH ALLO FOR PS CALL BACKG CLASS x.xx KBPS IN yL IN
SRNC
RT DCH ALLO DUR FOR PS CALL CONV CLASS x.xx KBPS IN yL
IN SRNC
RT DCH ALLO DUR FOR PS CALL STREAM CLASS x.xx KBPS IN
yL IN SRNC
NRT DCH ALLO DUR FOR PS CALL INTERA CLASS x.xx KBPS IN
yL IN SRNC
NRT DCH ALLO DUR FOR PS CALL BACKG CLASS x.xx KBPS IN
yL IN SRNC
M1002 - C286
DCH REQ FOR DATA CALL IN DRNC
M1002 - C287
DCH REQ FOR DATA CALL REJECT IN UL IN DRNC
Version 1.3
Jacinto
28

Nokia
M1002 - C288
DCH REQ FOR DATA CALL REJECT IN DL IN DRNC
M1002 - C289
DCH DHO REQ FOR DATA CALL IN DRNC
M1002 - C290
DCH DHO REQ FOR DATA CALL REJECT IN DRNC
M1002 - C375
DCH HHO OVER IUR REQ FOR DATA CALL IN DRNC
M1002 - C376
M1002C291 M1002C314
M1002C315 M1002C338
DCH HHO OVER IUR REQ FOR DATA CALL REJECT IN DRNC
M1002 - C401
REJECTED HS-DSCH RETURN CH FOR INTERACTIVE
M1002 - C402
M1002 - C414
REJECTED HS-DSCH RETURN CH FOR BACKGROUND

HS-DSCH SETUP FAILURE DUE TO RNC INTERNAL FOR
INTERACTIVE
HS-DSCH MAC-D FLOW SETUP FAILURE DUE TO IUB
TRANSPORT FOR INTERACTIVE
M1002 - C415
HS-DSCH SETUP FAILURE DUE TO UE FOR INTERACTIVE
M1002 - C416
M1002 - C422
HS-DSCH SETUP FAILURE DUE TO BTS FOR INTERACTIVE

HS-DSCH TOTAL IUB TRANSPORT SETUP FAIL FOR
INTERACTIVE
HS-DSCH 64 KBPS RETURN CH IUB TRANSPORT SETUP
FAILURE FOR INTERACTIVE
HS-DSCH SETUP FAILURE DUE TO RNC INTERNAL FOR
BACKGROUND
HS-DSCH MAC-D FLOW SETUP FAILURE DUE TO IUB
TRANSPORT FOR BACKGROUND
M1002 - C423
HS-DSCH SETUP FAILURE DUE TO UE FOR BACKGROUND
M1002 - C424
HS-DSCH SETUP FAILURE DUE TO BTS FOR BACKGROUND

HS-DSCH TOTAL IUB TRANSPORT SETUP FAIL FOR
BACKGROUND
FAILURE FOR BACKGROUND
M1002 - C413
M1002 - C417
M1002 - C418
M1002 - C419
M1002 - C420
M1002 - C421
M1002 - C425
M1002 - C426
M1002 - C427
M1002 - C428
Version 1.3
Jacinto
DCH ALLO FOR DATA CALL x.xx KBPS IN yL IN DRNC

DCH ALLO DURA FOR DATA CALL x.xx KBPS IN yL IN DRNC
29

Nokia
7.5
Partial Results of Capacity Tests in Bellingham
Capacity tests are conducted in Bellingham trial network to simulate and validate Nokia capacity.
7.5.1
DL Power Capacity
DL capacity = (Pmax Pcommon Preserved)/ (Plink x # of RL)

Where:
Pmax = max power of the Node B power amplifier.
Pcomm = power reserved for Common channels
Preserved = power reserved as headroom for in-progress calls
Plink = average power per radio link for each radio bearer type
Test
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Service Type
AMR 12.2
AMR 12.2
AMR 12.2
AMR 12.2
AMR 12.2
AMR 12.2
PS 64
PS 64
PS 64
PS 64
PS 64
PS 64
PS 384
PS 384
CS 64
CS 64
CS 64
CS 64
Activity Factor
70%
70%
70%
70%
70%
70%
20%
20%
20%
20%
20%
20%
20%
20%
20%
20%
20%
20%
Ec/No
-5.00
-5.00
-5.00
-5.00
-5.00
-5.00
5.00
-5.00
-5.00
-5.00
-5.00
-5.00
-5.00
-5.00
-5.00
-5.00
-5.00
-5.00
PtxTarget
()
45
43
42
41
40
39
45
43
42
41
40
39
40
39
45
40
39.5
39
Number of
Total
Total
services
Power per
Total
CCH_Power_ Power_w Power_d
PtxOffset Activated service_watts Power_service watts
atts
bM
1dBm
71
25.23
1791.41
7.94 1799.354
62.6
1dBm
71
22.28
1582.07
7.94 1590.008
62.0
1dBm
71
20.47
1453.14
7.94 1461.086
61.6
1dBm
53
19.43
1029.68
7.94 1037.628
60.2
1dBm
33
17.95
592.24
7.94 600.1813
57.8
1dBm
0
7.94 7.943282
39.0
1dBm
13
32.60
423.86
7.94 431.7991
56.4
1dBm
13
29.66
385.52
7.94 393.4681
55.9
1dBm
13
27.84
361.92
7.94 369.8625
55.7
1dBm
13
25.53
331.91
7.94 339.8506
55.3
1dBm
13
21.99
285.90
7.94 293.8434
54.7
1dBm
0
7.94 7.943282
39.0
1dBm
2
30.12
60.24
7.94 68.18618
48.3
1dBm
0
7.94 7.943282
39.0
1dBm
13
32.60
423.86
7.94 431.7991
56.4
1dBm
13
21.99
285.90
7.94 293.8434
54.7
1dBm
13
18.72
243.42
7.94 251.366
54.0
1dBm
0
0.00
7.94 7.943282
39.0
The number of users for each service is reduced as the Ptx target is adjusted
Power Allocated for common channels need to be adjusted when Ptx target is adjusted
No service is allowed at Ptx target <= 39 dBm
7.5.2
Maximum Services per Cell 1 T1 per site
Test
Case
WCEL
Service
Type
Activity
Factor
Number of
T1s
Number of
cells
Number of call
attempts
Number of call
activated
10210,
12020,
10230
AMR 12.2
100%
180
71
10210
PS 64
20%
15
13
10210
PS 128
100%
15
10
10210
PS 384
100%
10210
CS 64
100%
15
13
7.5.3
Version 1.3
Jacinto
Reserved Iub Bandwidth for each service

30

Nokia
Sum Reserved CellRate

Net Cell Rate Reserved
# of Samples cps/sample kbps
450500
450500
901
500
212
504900
54400
900 60.444444 25.62844
696886
246386
900 27.376222 11.60752
540600
90100
901
100
42.4
545502
95002
901 105.44062 44.70682
681203
230703
899
256.6218 108.8076
1276880
826380
900
918.2 389.3168
No Load
1 AMR 12.2
10 AMR 12.2
1 CS64K
1 PS64K
1 PS128K
1 PS384K
There is reserved bandwidth for Signaling and Common Channels even if there is no load
As the number of services or data amount increase, the more efficient is the ATM packing
7.5.4
# of users
Activated
71 AMR 12.2
16 AMR calls/1
PS384
16 AMR calls/1
PS64
7.5.5
RAB Downgrade due to CE resources

Users _activated
16 AMR 12.2
12 AMR 12.2/1 PS
384
13 AMR 12.2/1 PS 64
# of T1
# of
# of
HSDPA_CE
# of CE
# of CE
CE/m odule CCH_CE
required
available
used_calculated
1
64
16
32
16
16
64
16
32
16
28
64
16
32
16
16
Throughput Measurement
Application Average throughput (1 user): HSDPA = 900 kbps

Application Average throughput (1 user): R99 = 350 kbps
Version 1.3
Jacinto
31

UMTS RAN Dimensioning Guidelines PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

UMTS RAN Dimensioning Guidelines PDF

Încărcat de

Drepturi de autor:

Formate disponibile

UMTS RAN Dimensioning Guidelines