umts ran dimensioning guidelines

UMTS RAN Dimensioning GuidelinesNokia Equipment

Version 1.5

T-Mobile FSCRAN Engineering and Dimensioning Group

Document Name: UMTS Dimensioning Guidelines for Nokia Equipment

UMTS RAN Dimensioning GuidelinesNokia

Revision History:

Revision HistoryVersion Date Changes Change Description Done by:

1.0 05/26/04 First issued full version G. Jacinto1.1 06/16/06 Nokia Flexi

includedAdditional guidelines on Flexi dimensioning

G. Jacinto

1.2 06/27/06 Additional: Section 6

Adds summary of formulas, includes the Nokia counters

G. Jacinto

1.3 10/26/06 Edit Section 2 and 3

Remove details on Ultrasites, change Iub configuration figures

G. Jacinto

1.4 11/28/06 Updated version

Updated based on inputs from A.Lemow Y.Zhang, RAN Dim Group

G. Jacinto

1.5 12/22/06 Counters Revised the Counter lists 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.

Table of Contents

Version 1.3Jacinto

2


1. Introduction..................................................................................................................42. Nokia Product Description.............................................................................................5

2.1.1 Node B...............................................................................................................52.1.2 Description of Flexi WCDMA BTS Units...........................................................52.1.3 Flexi WCDMA BTS Capacity............................................................................6

2.1 RNC.......................................................................................................................82.2.1 Description of RNC units................................................................................82.2.2 RNC Capacity.......................................................................................................9

3 Channel Element Dimensioning..................................................................................103.1 Nokia Flexi WCDMA BTS System Module (FSM)...................................................10

4 Iub Dimensioning........................................................................................................124.1 User Plane Iub Bandwidth....................................................................................134.2 Control Plane Iub Bandwidth...............................................................................14

5 RNC Dimensioning......................................................................................................176 Iu Interface Dimensioning...........................................................................................20

6.1 Iu-CS Interface.....................................................................................................206.2 Iu-PS Interface.....................................................................................................21

7 Summary of Formulas and Counters...........................................................................227.1 Channel Element Dimensioning Formulas...........................................................227.2 Iub Dimensioning Formulas.................................................................................227.3 RNC Dimensioning Formulas...............................................................................227.4 Nokia Counters....................................................................................................237.5 Partial Results of Capacity Tests in Bellingham...................................................24

List of Tables

Table 1 – RF Module TypesTable 2 – Transmission Sub module TypesTable 3 – Flexi WCDMA BTS CapacityTable 4 – Flexi ConfigurationsTable 5 – Maximum RNC Capacity per ReleaseTable 6 – Number of CEs needed for different servicesTable 7 – Flexi BTS CE dimensioning exampleTable 8 – Nokia Iub VC RequirementsTable 9 – Iub User Plane Dimensioning AssumptionsTable 10 – Iub Dimensioning exampleTable 11 – Nokia RAS05 RNC CapacityTable 12 – Nokia RNC HSDPA CapacityTable 13 – RNC Dimensioning exampleTable 14 – Nokia RNC Counters on RAB SetupTable 15 – Nokia RNC Counters on Congestion

List of Figures

Figure 1 – Flexi WCDMA BTS unitsFigure 2 – Nokia Flexi WCDMA BTSFigure 3 – Nokia RNC unitsFigure 4 – Nokia Iub ConfigurationFigure 5 – Iub Configuration exampleFigure 6 – Iu-CS Configuration exampleFigure 7 – Iu-PS Configuration example

1. Introduction

Version 1.3Jacinto

3


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 Nokia’s recommendations and 3GPP specifications. The detailed computations of these overheads were not included in this document but can be issued separately.

2. Nokia Product Description

Version 1.3Jacinto

4

Baseband Unit

Transmission

Control

RF Module

Flexi System Module


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.

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 CabinetMax Unit

/cabinetRF Module Type

# of PA/Type

Max output Power/PA

(W)

FlexiFCOA or

FCIA (optional)

8 RF Module - FRIA 2 40

8 RF Module - FRIB 1 40

Table 1. RF Module types

Version 1.3Jacinto

RF Unit

5


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.

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 Sub-Modules

IMA groups supported Transmission links per IMA group

FTPB 4 8 T1 linksFTIA 2 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.3Jacinto

6


Figure 2. Nokia Flexi WCDMA BTS

Configurations

No. of Channel Elements (RAS05.1)

No. of Channel Elements (RAS06)

No. of Carriers No. of Sectors

FSMB 192 240 6 3FSMB + FSMB 384 480 12 6

Table 3. Flexi BTS Capacity

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 ConfigPower Output

(W)RF Module

Type RAN Release2+2 20 FRIA RAS05.1 CD

1+1+1 Feederless 20 or 40 3 FRIB RAS05.12+2+2 20 FRIA + FRIB RAS05.1 CD

2+2+2 Feederless 20 3 FRIB RAS05.1 CD2+2+2 40 3 FRIA RAS06

1+1+1+1 40 2 FRIA RAS063+3+3 40 3 FRIA RAS064+4+4 20 3 FRIA RAS06

Uneven config 3 FRIA RAS061+1+1+1+1+1 20 or 40 3 FRIA RAS062+2+2+2+2+2 20 3 FRIA RAS06

Table 4 Flexi Configurations

2.1 RNC

Version 1.3Jacinto

7

RNC 450

RNC 150

RNC 300


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.

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.RSMU - Resource and Switch Management Unit performs the RNC's central resource management tasks, such as connection control, ATM resource scheduling and digital signal

Version 1.3Jacinto

8


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 RNC Throughput (Mbps)

Number of BTS

Number of cells

No of HSDPA

activated BTSs

No of HSDPA

activated cells

AAL2 Connectivit

y (Mbps)

HSDPA traffic (Mbps)

RAS 05.1 450 512 1152 512 1152 3594 450RAS 06 1000 768 1728 768 1728 3594 1000

Table 5. Maximum RNC Capacity per Release

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.

3 Channel Element Dimensioning

Version 1.3Jacinto

9


3.1 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 CEs Required PS: 8 kbps, 16 kbpsCS: 12.2 kbps AMR

1

PS: 32 kbps 2PS: 64kbps, 128 kbps (including ADCH)CS: 64 kbps

4

PS: 256 kbps 8PS: 384 kbps (including ADCH) 16HSDPA scheduler reserved blocks for 5 codes (UL and DL)

32

HSDPA UL SRB: 3.4 kbps 1Control Channels 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

Version 1.3Jacinto

10


- Traffic usage per subscriber per application: AMR, CS64, PS64, PS128, PS384, PS512 UL/DL

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 Services UL CE Requirement

DL CE Requirement

12 12.2 kbps AMR 12*1 = 12 12*1 = 123 CS 64 kbps 3*4 = 12 3*4 = 125 PS 64/128 kbps 5*4 = 20 5*4 = 202 PS 64/384 kbps 2*4 = 8 2*16 = 322 384 A-DCH HSDPA 2*16 = 32 2*1 = 2

R99 and ADCH Reqt

84 78

SHO Requirements 84*0.3= 26 78*0.3 = 24HSDPA scheduler 32 32Control Channels 16 16Total CEs Required

158 150

FSMB Required =158/192 = 0.82 = 1 FSMB moduleTable 7. Flexi BTS CE dimensioning example

Version 1.3Jacinto

11

AXC(AXCC, AXCD, AXUA)

RNCFlexi BTS

VC1 – USER PLANE

VC2 – AAL2 SIGNALING

VC3 – DNBAP

VC4 – CNBAP

VC4 – O&M

Iub


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.

4 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.

Figure 4. Nokia Iub Configuration

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.

Version 1.3Jacinto

12

Virtual Channel (VC) Number of VCs Required

QoS

User Plane 1 VC = 248 AAL2 connections

CBR

AAL2 Signalling 1 per Node B CBRDNBAP 1 per Node B CBRCNBAP 1 per Node B CBRO&M 1 per Node B UBR


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.

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 SHO Percentage

Protocol/ATM Overhead

Throughput Factor

12.2 kbps AMR 67% 30% 55%CS 64 kbps 100% 30% 25%PS 64 kbps 100% 30% 28% 26.5%PS 128 kbps 100% 30% 25% 26.5%PS 384 kbps 100% 30% 23% 26.5%

HSDPA 100% 21 – 43% 26.5%Table 9. Iub User Plane Dimensioning Assumptions

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

Dimensioning Process: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:

Version 1.3Jacinto

13


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.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 secondRL_setup_msg_size is the size of the RL setup response message, typically 2 atm cellsRRI_msg_size is the radio resource indication message size, estimated to be 4 atm cells for 1-3 WCDMA cellsRR_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 onlyBH 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

Version 1.3Jacinto

14


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

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: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

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

Version 1.3Jacinto

15

AXC(AXCC, AXCD, AXUA)

RNCFlexi BTS

USER PLANE VCs 10153 cps

AAL2 SIGNALING VC 254 cps

DNBAP VC 508 cps

CNBAP VC 254 cps

O&M VC 150 cps

Iub


- 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 cpsDNBAP = 508 cpsCNBAP = 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 Services Iub Requirement UL

Iub Requirement DL

12 12.2 kbps AMR 197.65 kbps 197.65 kbps3 CS 64 kbps 312 kbps 312 kbps5 PS 64/128 kbps 673.59 kbps 1315.6 kbps2 PS 64/384 kbps 269.43 kbps 1553.46 kbps2 384 A-DCH HSDPA 1553.46 kbps 926.18 kbps

User Plane Reqt (kbps)

3006.13 kbps 4304.89 kbps

User Plane Reqt (cps)

7090 cps 10153 cps

AAL2 signalling 178 cps 254 cpsDNBAP 354 cps 508 cpsCNBAP 178 cps 254 cps

Contro Plane Reqt 710 cps 1016 cpsO&M 150 cps 150 cps

Iub Reqt (cps) 7950 cps 11319 cpsIub BW Requirement 11319 cps or 4.8 Mbps or 4 T1s

Table 10. Iub Dimensioning example

Version 1.3Jacinto

16


Figure 5. Iub Configuration example

5 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

Iub Throughput

(Mbps)

Number of Node B

Number of cells

AAL2 Connectivity

(Mbps)

Interface Cards STM1 / T1

150 150 200 600 1,950 4/16300 300 300 900 2,800 8/16450 450 512 1,152 3,594 12/16

Table 11. Nokia RAS05.1 RNC Capacity

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 Max No of HSDPA activated

BTS

HSDPA Net Throughput

(Mbps)

Max HSDPA users per cell

Max no of HSDPA users

150 200 135 16 290300 300 270 16 580450 512 405 16 1500

Table 12. Nokia RNC HSDPA Capacity

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

Version 1.3Jacinto

17


- Traffic usage per application

Assumptions:- SHO = 30%- Fill rate = 60-70% for new network, 80-90% for operating network

Dimensioning Process: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)

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 + IuCSIur 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:

Node B with 3 sectors, FSMB modules onlyTraffic 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 bandwidthRNC with full config will be used

Version 1.3Jacinto

18


Channelized STM-1 connection from Node B to RNC (1 STM-1 = 63 E1s or 84 T1s)Traffic shaping is enabled90% 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.

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 MbpsIur = 5%*Iub = 0.05*480 Mbps = 24 Mbps IuCS = (AMR users*12.2 kbps + CS64 users*64 kbps)*Protocol overhead*Signaling

overhead = 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

Version 1.3Jacinto

19


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 Requirement RNC Capacity Required No of RNC

Iub throughput 480 Mbps 450 Mbps 2BTS count 100 512 1Cell count 300 1152 1

AAl2 connectivity 546.72 Mbps 3594 Mbps 1Required RNC = 2

Table 13. RNC Dimensioning example

6 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:100 Node Bs, each has the following specs:Node B with 3 sectors, FSMB modules onlyTraffic 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

Iu-CS User Plane = 100*(12*12.2+3*64)*(1.25) = 42. 3 MbpsIu-CS Control Plane = 1%*42.3 Mbps = 423 kbps Iu-CS Bandwidth = 42.3 Mbps + 423 kbps = 42.72 Mbps

Version 1.3Jacinto

20

MSC/MGW

RNCUSER PLANE VCs 42.3 Mbps

CONTROL PLANE VC 423 kbps

Iu-CS

3G SGSN

RNCUSER PLANE VCs 242.2 Mbps

CONTROL PLANE VC 2.4 Mbps


Figure 6. Iu-CS Configuration example

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:100 Node Bs, each has the following specs:Node B with 3 sectors, FSMB modules onlyTraffic 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

UL User Plane = 100*(5*64+2*64+2*384) = 121.6 MbpsDL User Plane = 100*(5*128+2*384+2*512) = 192 MbpsIu-PS User Plane = 192*1.25 = 240 MbpsIu-PS Control Plane = 1%*240 Mbps = 2.4 Mbps Iu-PS Bandwidth = 240 + 2.4 Mbps = 242.4 Mbps

Version 1.3Jacinto

21


Figure 7. Iu-PS Configuration example

7 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 voice = no. of channels * bit rate * (1+SHO) * activity factor * protocol overheadIub CS = no. of channels * bit rate * (1+SHO)* activity factor * protocol overheadIub PS = no.of channels * bit rate * (1+SHO) * activity factor * protocol overhead*throughput factorIub 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 ADCHDL 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

Version 1.3Jacinto

22


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 BsNumber 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)

AAL2 connectivity (Mbps) = Iub + Iur + IuCSIur = 5% * Iub RequirementsIuCS = (AMR users*12.2 kbps + CS64 users*64 kbps)*Protocol overhead*Signaling overheadAAL2 Connectivity = Iub + Iur + IuCSNumber of RNC (AAL2 connectivity) = AAL2 Connectivity/(AAL2 capacity*fill rate)

Number of STM-1 connections = sum of STM-1 for Iub, Iur, IuCS and IuPSIuPS = 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 Abbreviation

NodeB_Cell Resource

M5001C0 MAXIMUM NUMBER OF AVAILABLE CHANNEL ELEMENTS MAX_AVAIL_CE

M5001C1 MINIMUM NUMBER OF AVAILABLE CHANNEL ELEMENTS MIN_AVAIL_CE

M5001C2 AVERAGE NUMBER OF AVAILABLE CHANNEL ELEMENTS AVE_AVAIL_CE

M5001C3 MAXIMUM NUMBER OF USED CE FOR DL MAX_USED_CE_DL

M5001C4 MAXIMUM NUMBER OF USED CE FOR UL MAX_USED_CE_UL

M5001C5 MINIMUM NUMBER OF USED CE FOR DL MIN_USED_CE_DL

M5001C6 MINIMUM NUMBER OF USED CE FOR UL MIN_USED_CE_UL

M5001C7 AVERAGE NUMBER OF USED CE FOR DL AVG_USED_CE_DL

M5001C8 AVERAGE NUMBER OF USED CE FOR UL AVG_USED_CE_UL

RNC Cell resource

M1000C181 NUMBER OF SAMPLES FOR CE CALCULATIONCE_SAMPLE_AMOUNT

M1000C182 AVERAGE USED CE FOR AMR ALLOCATIONS AVE_CE_USED_AMR

M1000C183 AVERAGE USED CE FOR CS CONVERSATIONAL 64 KBPSAVE_CE_USED_CS_CONV_64

M1000C184 AVERAGE USED CE FOR CS STREAMING 14.4 KBPSAVE_CE_USED_CS_STR_14_4

Version 1.3Jacinto

23


M1000C185 AVERAGE USED CE FOR CS STREAMING 57.6 KBPSAVE_CE_USED_CS_STR_57_6

M1000C186 AVERAGE USED CE FOR PS STREAMING 8 KBPS ULAVE_CE_USED_PS_STR_8_UL





M1000C191 AVERAGE USED CE FOR PS STREAMING 8 KBPS DLAVE_CE_USED_PS_STR_8_DL







M1000C198 AVERAGE USED CE FOR PS INTERACTIVE 8 KBPS ULAVE_CE_USED_PS_INT_8_UL







M1000C212 AVERAGE USED CE FOR PS BACKGROUND 8 KBPS ULAVE_CE_USED_PS_BGR_8_UL







M1000C219 AVERAGE USED CE FOR PS BACKGROUND 8 KBPS DLAVE_CE_USED_PS_BGR_8_DL



M1000C222 AVERAGE USED CE FOR PS BACKGROUND 64 KBPS DL AVE_CE_USED_PS_B

Version 1.3Jacinto

24


GR_64_DL




RAB downgrade/release due to BTS Congestion

M1000C146 RB DOWNGRADE BY PBS DUE TO BTS CONGESTION

M1000C151 RB DOWNGRADE BY PRE-EMPTION DUE TO BTS CONGESTION

M1000C158 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

M1000-C20 Average PTx Feasible Load Area 3 Ave PtxTot Class 3

M1000-C21 Total Ptx Tot Feasible Load Area 3 PtxTot Denom 3

M1000-C22 Average PTx Feasible Load Area 4 Ave PtxTot Class 4

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

M1000-C99Estimated average transmitted power for DL RT users on the cell for Class 3 Ave Ptx RT Class 3

M1000-C100 Ptx total value is inside Class 3 range Ptx RT Denom 3

M1000-C101Estimated average transmitted power for DL RT users on the cell for Class 4 Ave Ptx RT Class 4

M1000-C102 Ptx total value is inside Class 4 range Ptx RT Denom 4

M1000-C50Estimated average transmitted power for DL NRT users on the cell for Class 3 Ave Ptx NRT Class 3

M1000-C51 Ptx total value is inside Class 3 range Ptx NRT Denom 3

M1000-C52Estimated average transmitted power for DL NRT users on the cell for Class 4 Ave Ptx NRT Class 4

M1000-C53 Ptx total value is inside Class 4 range Ptx NRT Denom 4

SCCPCH Load Monitoring based on available counters

M1000-C64 Average load of SCCPCH chanel including PCHAve SCCPCH inc PCH Load

M1000-C65Denominator for Average load of SCCPCH channel (including PCH)

SCCPCH Load Denom 0

M1000-C70 PCH throughput Ave PCH Throughput

M1000-C71 Denominator for Average PCH throughputPCH Throughput Denom 0

M1000-C103 Average load of SCCPCH channel -PCH not presentAve SCCPCH exc PCH Load

M1000-C104Denominator for Average load of SCCPCH channel (excluding PCH)

SCCPCH Load Denom 1

M1000-C105Average FACH throughput of both user data and signalling in b/sec without PCH

Ave FACH User Tot Throughput for SCCPCH Exc PCH

M1000-C106 FACH User Tot Throughput Denom 1 FACH User Tot Throughput Denom 1

M1000-C107Average FACH throughput of user data only in bit/s for SCCPCH - excluding PCH

Ave FACH Data Throughput for SCCHPCH exc PCH

M1000-C108 FACH User Data Throughput Denom 1 FACH User Data Throughput Denom 1

Spreading Factor Monitoring based on available counters

M1000-C72 Average code usage in percentageAverage usage of Code capacity

M1000-C73 Denominator for average usage of code capacity Denominator for average usage of code

Version 1.3Jacinto

25


capacity

M1000-C74 Minimum code usage in percentageMinimum code occupancy percentage

M1000-C75 maximum code usage in percentageMax Code Occupancy percentage

M1000-C76 Number of tmes when no SF4 codes were available No Codes available SF4

M1000-C77 Number of tmes when no SF8 codes were availableNo Codes available SF8






M1000-C83 The number of successful code tree allocations.Nbr of Succ Code Tree Allo

Radio Link Reports

M1000-C89 Average Transmission power per radio link in a cell Ave Trx for RL in Cell

M1000-C90 Number of reported radio link during measurement period Nbr of RLS

M1000-C91Sum of squared measured values for transmission powers for the RL in the cell

Sum SQR TRX for RL in Cell

M1000-C92Number of Radio link measurement reports during the measurement period Nbr of RL Meas Reps

Traffic Measurement Area-RNC level

M1002-C0 Total number of DCH request for a signalling link in the SRNCDCH Req for Sig Link in SRNC

M1002-C1Total 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

M1002-C2Total number of DCH request for a signalling link rejected in the SRNC for reasons caused by DL radio resources.

DCH Req for SigLink Reject in DL in SRNC

M1002-C3Total number of DCH request for a RRC connection establishment in the SRNC

DCH Req for RRC Conn in SRNC

M1002-C4Total number of DCH request for a signalling link because of the diversity handover in the SRNC

DCH Dho Reqq for Sig link in SRNC

M1002-C5

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

DCH DHO Req for Sig Link Reject in SRNC

M1002-C12Total number of RT DCH requests for a CS voice call in the SRNC

RT DCH Req for CS Voice Call in SRNC

M1002-C13Total number of RT DCH requests for CS voice call rejected in the SRNC for reasons caused by UL radio resources

RT DCH Req for CS Voice Call Reject in UL in SRNC

M1002-C14Total number of RT DCH requests for CS voice call rejected in the SRNC for reasons caused by DL radio resources

RT DCH Req for CS Voice Call Reject in DL in SRNC

M1002- C16Total number of DCH requests for a CS voice call due to diversity handover in the SRNC

RT DCH DHO Req for CS Voice call in SRNC

M1002-C17

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

RT DCH DHO Req for CS Voice call reject in SRNC

M1002C18-M1002C33

Number of real time DCH allocation for AMR x.xx in yL in the SRNC. (AMR codec 12.2 - UL/DL)

RT DCH Allo for AMR 12.2 kbps in UL/DL in the SRNC

M1002-C34-M10020C49

Summary of RT DCH allocated durarions for AMR 12.2 in UL/DL in SRNC

RT DCH Allo Dura for AMR 12.2 kbps in

Version 1.3Jacinto

26


UL/DL in the SRNC

M1002-C50Total number of RT DCH request for a transparent CS Data call with conversational class in the SRNC

RT DCH Req for CS Data call Conv Class in SRNC

M1002-C51Total number of RT DCH request for a nontransparent CS data call with streaming class in the SRNC

RT DCH Req for CS Data call Stream Class in SRNC

M1002-C52

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

RT DCH Req for CS Data call Conv Class Reject in UL in SRNC

M1002-C53

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

RT DCH Req for CS Data call Conv Class Reject in DL in SRNC

M1002-C54

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

RT DCH Req for CS Data call Stream Class Reject in UL in SRNC

M1002-C55

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

RT DCH Req for CS Data call Stream Class Reject in DL in SRNC

M1002-C58Total number of DCH request for a transparent CS data call with conversation class due to diversity handoever in the SRNC

RT DCH DHO Req for CS Data Call Conv Class in SRNC

M1002-C59

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

RT DCH DHO Req for CS Data Call Conv Class Reject in SRNC

M1002-C60Total number of DCH request for a nontransparent CS data call with streaming class due to diversity handoever in the SRNC

RT DCH DHO Req for CS Data Call Stream Class in SRNC

M1002-C61

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 DHO Req for CS Data Call Stream Class Reject in SRNC

ATMThe number of egress cells transmitted to a virtual path connection. EG_TOT_CELLS_VP

The number of ingress cells received from a virtual path connection IN_TOT_CELLS_VP

The number of egress cells transmitted to a virtual channel connection. EG_TOT_CELLS_VC

The number of ingress cells received from a virtual channel connection. 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-C88RT DCH REQ FOR PS CALL CONV CLASS REJECT IN UL IN SRNC

Version 1.3Jacinto

27


M1002-C89RT DCH REQ FOR PS CALL CONV CLASS REJECT IN DL IN SRNC

M1002-C90RT DCH REQ FOR PS CALL STREAM CLASS REJECT IN UL IN SRNC

M1002-C91RT DCH REQ FOR PS CALL STREAM CLASS REJECT IN DL IN SRNC

M1002-C92RT DCH REQ FOR PS CALL INTERA CLASS REJECT IN UL IN SRNC

M1002-C93RT DCH REQ FOR PS CALL INTERA CLASS REJECT IN DL IN SRNC

M1002-C94RT DCH REQ FOR PS CALL BACKG CLASS REJECT IN UL IN SRNC

M1002-C95RT 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-C98NRT DCH INI REQ FOR PS CALL INTERA CLASS IN UL IN SRNC

M1002-C99NRT DCH INI REQ FOR PS CALL INTERA CLASS IN DL IN SRNC

M1002-C100NRT DCH INI REQ FOR PS CALL BACKG CLASS IN UL IN SRNC

M1002-C101NRT 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-C348RT DCH HHO REQ FOR PS CALL CONV CLASS REJECT IN SRNC

M1002-C349 RT DCH HHO REQ FOR PS CALL STREAM CLASS IN SRNC

M1002-C350RT 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-C352RT DCH HHO REQ FOR PS CALL INTERA CLASS REJECT IN SRNC

M1002-C353 NRT DCH HHO REQ FOR PS CALL BACKG CLASS IN SRNC

M1002-C354NRT DCH HHO REQ FOR PS CALL BACKG CLASS REJECT IN SRNC

M1002-C475DCH SELECTED FOR INTERACTIVE DUE TO MAX HSDPA USERS

M1002-C476DCH SELECTED FOR BACKGROUND DUE TO MAX HSDPA USERS

M1002C110 - M1002C125

RT DCH ALLO FOR PS CALL CONV CLASS x.xx KBPS IN yL IN SRNC

M1002C126 - M1002C141

RT DCH ALLO FOR PS CALL STREAM CLASS x.xx KBPS IN yL IN SRNC

M1002C142 - M1002C157

NRT DCH ALLO FOR PS CALL INTERA CLASS x.xx KBPS IN yL IN SRNC

M1002C158 - M1002C173

NRT DCH ALLO FOR PS CALL BACKG CLASS x.xx KBPS IN yL IN SRNC

Version 1.3Jacinto

28


M1002C174 - M1002C189

RT DCH ALLO DUR FOR PS CALL CONV CLASS x.xx KBPS IN yL IN SRNC

M1002C190 - M1002C205

RT DCH ALLO DUR FOR PS CALL STREAM CLASS x.xx KBPS IN yL IN SRNC

M1002C206 - M1002C221

NRT DCH ALLO DUR FOR PS CALL INTERA CLASS x.xx KBPS IN yL IN SRNC

M1002C222 - M1002C237

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

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 - C376DCH HHO OVER IUR REQ FOR DATA CALL REJECT IN DRNC

M1002C291 - M1002C314 DCH ALLO FOR DATA CALL x.xx KBPS IN yL IN DRNCM1002C315 - M1002C338

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

M1002 - C401 REJECTED HS-DSCH RETURN CH FOR INTERACTIVE

M1002 - C402 REJECTED HS-DSCH RETURN CH FOR BACKGROUND

M1002 - C413HS-DSCH SETUP FAILURE DUE TO RNC INTERNAL FOR INTERACTIVE

M1002 - C414HS-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 HS-DSCH SETUP FAILURE DUE TO BTS FOR INTERACTIVE

M1002 - C417HS-DSCH TOTAL IUB TRANSPORT SETUP FAIL FOR INTERACTIVE

M1002 - C418HS-DSCH 64 KBPS RETURN CH IUB TRANSPORT SETUP FAILURE FOR INTERACTIVE



M1002 - C421HS-DSCH SETUP FAILURE DUE TO RNC INTERNAL FOR BACKGROUND

M1002 - C422HS-DSCH MAC-D FLOW SETUP FAILURE DUE TO IUB TRANSPORT FOR BACKGROUND

M1002 - C423 HS-DSCH SETUP FAILURE DUE TO UE FOR BACKGROUND

M1002 - C424HS-DSCH SETUP FAILURE DUE TO BTS FOR BACKGROUND

Version 1.3Jacinto

29


M1002 - C425HS-DSCH TOTAL IUB TRANSPORT SETUP FAIL FOR BACKGROUND

M1002 - C426HS-DSCH 64 KBPS RETURN CH IUB TRANSPORT SETUP FAILURE FOR BACKGROUND



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 CapacityDL capacity = (Pmax – Pcommon – Preserved)/ (Plink x # of RL)

Where: Pmax = max power of the Node B power amplifier. Pcomm = power reserved for Common channelsPreserved = power reserved as headroom for in-progress callsPlink = average power per radio link for each radio bearer type

Test Case

WCELService Type

Activity Factor

Number of T1s

Number of cells

Number of call attempts

Number of call activated

110210, 12020, 10230

AMR 12.2

100% 1 3 180 71

2 10210 PS 64 20% 1 1 15 13

3 10210 PS 128 100% 1 1 15 10

4 10210 PS 384 100% 1 1 3 2

Version 1.3Jacinto

30


5 10210 CS 64 100% 1 1 15 13

- 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

7.5.3 Reserved Iub Bandwidth for each service

- 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 RAB Downgrade due to CE resources

7.5.5 Throughput Measurement

Application Average throughput (1 user): HSDPA = 900 kbpsApplication Average throughput (1 user): R99 = 350 kbps

Version 1.3Jacinto

31

umts ran dimensioning guidelines

Documents

aal2 capacityfill

bts capacityfill

cell capacityfill

rnc throughputfill

radio access

dsch return

egress cells

drnc dch hho