RADIO NETWORK

CONTROLLER
DIMENSIONING
The need for high speed, high bandwidth data drives the
evolution of wireless networks from 2G to 3G. The radio network
controller is one of the key network elements in the 3G wireless
network as it handles both circuit switched and packet switched
data and also the associated signaling in both domains. Therefore
the dimensioning of this network element, in terms of control
processors, network processors and addressing the terminating
link capacities is crucial from the operator’s point of view.
This white paper describes an approach for the dimensioning of
the radio network controller in the 3G wireless network. It also
explains the RNC architecture and configurations through
examples.
WHITE PAPER

SRIVATSA K N
Radio Network Controller Dimensioning

Table of Contents

INTRODUCTION ............................................................................................................................................................ 3
ARCHITECTURE ............................................................................................................................................................. 3
THE DIMENSIONING APPROACH .............................................................................................................................. 4
INPUTS FROM TRAFFIC MODEL .................................................................................................................. 5
CALL ATTEMPTS ................................................................................................................................. 5
DATA RATES ....................................................................................................................................... 5
SIGNALLING ASPECTS ...................................................................................................................... 6
BHCA COMPUTATIONS ................................................................................................................................. 6
CONTROL PLANE ............................................................................................................................... 6
USER PLANE ...................................................................................................................................... 7
USER PLANE REQUIREMENTS ...................................................................................................................... 7
CONTROL PLANE REQUIREMENTS .............................................................................................................. 8
MESSAGE COMPLEXITY ANALYSIS METHOD – A SUMMARY ................................................. 8
CONTROL PLANE REQUIREMENTS – A SAMPLE OUTPUT ......................................................... 9
LINK CAPACITIES COMPUTATION ................................................................................................................ 9
SAMPLE RNC CONFIGURATION ............................................................................................................................. 10
INPUTS .......................................................................................................................................................... 10
TRAFFIC MODEL ............................................................................................................................. 10
USER TRAFFIC CHARACTERISTICS ............................................................................................... 11
OUTPUTS ........................................................................................................................................................ 11
CONTROL PLANE CONFIGURATION ............................................................................................ 11
DATA PLANE CONFIGURATION ................................................................................................... 12
OUTPUT – RNC SPECIFICATIONS ............................................................................................... 12
CONCLUSION .......................................................................................................................................................... 14
ACRONYMS ................................................................................................................................................ 14
REFERENCES ................................................................................................................................................ 15
ABOUT THE AUTHOR ................................................................................................................................................. 15
ABOUT WIPRO TECHNOLOGIES ............................................................................................................................... 16
WIPRO IN TELECOM ................................................................................................................................................. 16

Page: Table of Contents

Radio Network Controller Dimensioning

INTRODUCTION
There are various models which have the ability to predict the traffic requirements in a 3G network. But given a traffic model,
the next step is to dimension the network according to the parameters of the traffic model. In this paper, an approach is
presented for the dimensioning of the RNC.
The dimensioning of RNC can be viewed from 3 different aspects:
• User plane requirements – what is the required bandwidth for supporting both CS and PS traffic
• Control plane capacities – what are the required control processor capacities for handling both CS and PS signaling
across all interfaces
• Link capacities – what are the link capacity requirements across all interfaces
Given these aspects, this paper discusses approaches dealing with:
• Computation of user plane capacities required across all the interfaces in terms of network processor requirements
• Computation of control plane capacities across all the interfaces in terms of control processor requirements
• Computation of link capacities required across all the interfaces
This information will be useful for designing the RNC in terms of determining the number of control/network processors
required and the corresponding link capacities required at each interface based on the estimated subscriber traffic in that area.
Another usage could be that of validating an existing design of the RNC with the dimensions given by the approach. This
information can also be used for existing RNCs to check if the current dimensions of the RNC are inline with the traffic offered
on a per RNC basis. While scaling up to meet increased bandwidth requirements, the new required RNC configuration can be
determined.

ARCHITECTURE
In UMTS, RNC is part of the UTRAN (Universal Terrestrial Radio Access Network). A UTRAN consists of a set of radio network
subsystems, which in turn consist of one RNC and multiple Node-Bs. The Node-B connects to the RNC though the Iub interface.
One RNC connects to another RNC through the Iur interface, and the RNC is connected to the MSC through the Iu-CS interface
and to the SGSN through the Iu-PS interface.

Iu-CS Iu-PS

RNS
Iur

RNC RNC

Iub

Node B Node B
cell

Uu

Figure 1: High level network architecture of UMTS networks

© Wipro Technologies Page: 03 of 16

Radio Network Controller Dimensioning

All elements in a 3G network connect through ATM or IP networks, where the throughput, QoS, and link configurations can be
managed at a granular level. At the physical layer, the elements can be connected through E1/T1 links or SONET/STM links or
Ethernet links. The Iub, Iu-CS, and Iu-PS interfaces can be either ATM based, IPoATM based or fully IP based.

THE DIMENSIONING APPROACH

This dimensioning approach will be discussed at the following levels:
• Inputs from the traffic model
• The BHCA computations that are done at the user and signalling planes based on the inputs from the traffic model
• Computation of the actual user plane requirements
• Computation of the actual control plane requirements
• Computation of link capacities
A visual representation of this approach is given in Figure 2.

User Plane User Plane RNC Dimensioning

BHCA Requirements Aspects
computations

Basic Traffic Link Capacity

Model Requirements

Control Control Plane

Plane Requirements
BHCA

Figure 2: RNC dimensioning approach

© Wipro Technologies Page: 04 of 16

Radio Network Controller Dimensioning

Inputs from Traffic Model

This forms the basis of all computations.
The parameters that constitute the traffic model can be broadly classified under call attempts, duration of calls and the data
rates associated with the calls. Under these categories, the parameters need to be input are given in the following tables (these
parameters are for a single user).

Call attempts
Parameter Explanation

Mobile originated/terminated ratio The ratio of mobile originated versus the mobile terminated calls.

Successful MO/MT call ratios The ratio of successful versus unsuccessful call attempts originated/terminated
by the mobile.

Successful mobile call attempts per user This includes both MO and MT calls which were successfully attempted.
per busy hour

Table 1: Call attempts

Data rates
Parameter Explanation

Uplink user peak bit rate Depending on the traffic class, this represents the highest bit rate the user
might be transmitting on the uplink

Downlink user peak bit rate Depending on the traffic class, this represents the highest bit rate the user
might be transmitting on the downlink.

Uplink activity factor Percentage of the total call duration the user is engaged in transmitting data
on the uplink

Downlink activity factor Percentage of the total call duration the user is engaged in transmitting data on
the downlink
Session duration (in secs) This is applicable for both CS and PS calls. This gives the total time the user
is engaged in holding the call.

Table 2: Data rates

© Wipro Technologies Page: 05 of 16

Radio Network Controller Dimensioning

Signalling aspects
Parameter Explanation

No. of paging per MTCA Ideally, there should only be 1 paging per user per call. But in case the user
is not reachable this could be more.

No. of LA/RA updates per call attempt This is directly proportional to the number of call attempts the user makes.

No. of cell/URA updates per user/second This is directly proportional to the user session duration and number of call
attempts.

Number of soft HOs per user/second This is directly proportional to the user session duration and number of call
attempts.

Number of intra-RNC hard handovers This is directly proportional to the user session duration and number of call
per user/second attempts.

Number of inter-RNC hard handovers/ This is directly proportional to the user session duration and number of call
second attempts.

Number of inter-RAT handovers/second This is directly proportional to the user session duration and number of call
attempts.

Table 3: Signalling related parameters

BHCA Computations
Based on the above input parameters the following parameters can be computed:

Control plane

Parameter Domain (CS/PS

No. of successful CS MTCA per user/hr CS

No. of successful CS MOCA per user/hr CS
No. of successful PS MOCA per user/hr PS
Total number of CS MTCA CS
Total number of CS MOCA CS
Total number of PS MOCA PS
Total number of calls CS+PS
Total no. of Paging CS+PS
Total no. of LA/RA updates CS+PS
Total no. of cell/URA updates for PS CS+PS

© Wipro Technologies Page: 06 of 16

Radio Network Controller Dimensioning

Parameter Domain (CS/PS

Total no. of CS SHOs CS

Total no. of PS SHOs PS
Total SHOs CS+PS
Nbr of intra-RNC hard HOs for CS CS
Nbr of intra-RNC hard HOs for PS PS
Total intra-RNC hard Hos CS+PS
Nbr of inter-RNC hard HOs for CS CS
Nbr of inter-RNC hard HOs for PS PS
Total inter-RNC hard Hos CS+PS
Nbr of inter-RAT HOs for CS CS

*Values in italics are the ones directly used in the user/control plane computations

Table 4: BHCA computations for control plane

User plane
For the user plane, only the peak user traffic that will need to be processed is required. The main BHCA parameters that need to
be computed based on the traffic model are given below:
• Total user traffic per session on the uplink/downlink
• Total user traffic per person per busy hour
• Total traffic (UL/DL) for the entire RNC per BH

User Plane Requirements

The calculation of the user plane bandwidth requirements directly comes from the input Traffic Model. In general, the user
traffic associated with umts can be classified into conversational, streaming, interactive and background.
For each of these traffic classes, there can be a separate traffic model. Ultimately when the user plane capacity needs to be
computed an aggregate of all these separate traffic models needs to be considered.
The steps involved in calculating the user plane requirements are briefly summarized hereafter:
Step 1: The basic traffic model inputs are entered. For example, parameters are number of subscribers, % of subscribers
engaged in CS, no. of CS/PS mobile originated, call attempts per user/hour etc.
Step 2: Based on the input Traffic model parameters in step 1, some parameters related to the user plane requirements are
computed. For example computed parameters are no. of successful CS/PS mobile originated call attempts per user/hr, no. of
successful CS MTCA per user/hr etc.
Step 3: Finally, the required bandwidth on the UL and DL for user plane traffic is computed. This is done for each assumed traffic
class (e.g., CS, PS-64K, PS-128K and PS-256K).

© Wipro Technologies Page: 07 of 16

Radio Network Controller Dimensioning

Control Plane Requirements

The approach to computing the control plane requirements is as follows:
• Using the traffic model, determine the number of primary events (see below) occurring during a BH (busy hour)
• For each such event, determine the number of messages to be handled at each of the RNC interfaces (Iub, Iur, Uu, Iu)
• Estimate the complexity of handling each message using a method which determines the number of fields that need to
be processed in each message and the complexity of these fields. This is done using the Message Analysis Method
• The complexity derived from each message is converted to LOC based on a multiplication factor (which is computed
based on some existing implementation of telecom scenarios related to 2G networks)
• The total number of LOC executed per scenario is determined by multiplying the LOC obtained in the previous step with
the estimated number of occurrences of that scenario (this is derived from the traffic model)
• Finally, the estimated LOC/sec is aggregated on a protocol/interface basis to give the estimated processing requirements
for each control processor. In this case, aggregation is made on NBAP(Iub), RRC(Uu), RNSAP(Iur) and RANAP(Iu)
protocol basis.

Message complexity analysis method – a summary

This method primarily involves analysing the complexity of incoming/outgoing messages at each interface based on the fields
present in the message and the nature of these fields (basic, compound etc.).
A sample output of this method is given below, where the complexity of the messages URA Update and URA Update Confirm
are determined at the Uu interface. Also the number of LOC executed per second as a result of processing these messages is also
given.
RRC Messages UCE Number of Interface ACE LOC Number Total LOC
Messages UCE of Occurrences executed
(per sec) (per sec)

URA Update 8 1

URA Update 20 1 28 30.24 3156 1.764 5334.336

Confirm

• Unadjusted complexity estimate (UCE) – This is obtained from the message complexity analysis
• Interface UCE – This is just a summation of the complexity estimates of the messages passing through that interface
• Adjusted complexity estimate (ACE) – This is the result of adjusting the user interface UCE with the adjustments factor
derived from the general system characteristics determined for RNC
• LOC – This is the result of converting the ACE to LOC using the multiplicative factor
• Number of occurrences – This is obtained from the Traffic Model
• Total LOC executed – LOC multiplied by Number of occurrences per second gives the Total LOC executed for that
scenario per second.

© Wipro Technologies Page: 08 of 16

Radio Network Controller Dimensioning

Control plane requirements – a sample output

Based on the above approaches, the following was computed for the signalling plane requirements:
Processor Requirements (MHz)

2500

2000
NBAP
1500
RRC
1000 RANAP
RNSAP
500

0
100000 150000 200000 250000 300000

Number of Subscribers

Figure 3: Control plane requirements – sample output

Link Capacities Computation

As a final step, the link capacities at each interface and the corresponding network processor requirements will be computed.
This is based on the following inputs:
• Total user traffic as determined in Error! Reference source not found.
• Total signaling traffic will be taken as a percentage of this entire user traffic (for the purposes of this paper, it is taken as
percentage of the traffic, depending on the interface).
• The total of the user and signaling traffic would yield the actual traffic estimated at the RNC level
• For each interface, the traffic can be split as follows:
- IuB – The entire traffic generated from CS and PS calls and the associated signaling would be taken into account
here.
- IuCS - The traffic is further split into CS and PS traffic (based on the traffic model). The traffic associated with CS will
be used for determining the capacity at this interface.
- IuPS – Similar to IuCS, the traffic associated with PS will be used.
- Iur – Here the entire data traffic (CS+PS) is taken into account and a percentage of this is estimated to flow through
this interface.
• Based on the above bandwidth requirements, the link capacities (in terms of number of E1 or OC-3 links) can be derived

© Wipro Technologies Page: 09 of 16

Radio Network Controller Dimensioning

For a subscriber base of 300,000 and a given traffic model, the sample output obtained using this method is shown below.

Interface IuB IuCS IuPS Iur

Capacity requirements (In Mbps) 4960.368 131.516 4415.488 1736.129
Nbr of E1 links 2480.184 65.758 2207.744 868.0644
Nbr of OC-3 links 32.00237 0.84849 28.48702 11.20083

Table 5: Link capacity requirements – sample output

SAMPLE RNC CONFIGURATION

In this section, a sample RNC configuration is presented, given a traffic model and the subscriber base to be supported.

Inputs
Traffic Model
Basic Inputs Value
Number of Subscribers 300000
% of subscribers engaged in CS 80%
% of subscribers engaged in PS 20%
% of traffic using 64K class 60%
% of traffic using 126K class 30%
% of traffic using 256K class 10%
No. of CS Mobile Terminated Call Attempts per user/hour 2
No. of CS MO Call attempts per user/hr 2
No. of PS Mobile Terminated Call Attempts per user/hour 0
No. of PS MO Call attempts per user/hr 1
Blocking Probability 2%
No. of paging per MTCA 1.5
No. of LA/RA updates per call attempt 1
No. of cell/URA updates per user/second 0.01
Number of soft HOs per user/second 0.001
Number of intra-RNC hard handovers per user/second 0.0001
Number of inter-RNC hard handovers/second 0.0001
Number of inter-RAT handovers/second 0.0001
CS session duration (in secs) 60
PS session duration (in secs) 600

© Wipro Technologies Page: 10 of 16

Radio Network Controller Dimensioning

User traffic characteristics

Characteristic CS (kbps) PS-64K (kbps) PS-128K (kbps) PS-256K (kbps)

UL peak rate 12.2 64 128 256

DL peak rate 12.2 64 128 256
UL activity factor 50% 20% 20% 20%
DL activity factor 50% 80% 80% 80%

Outputs
Control plane configuration

Control plane processors Data plane processors

Sample CPU specifications Sample CPU specifications

Intel Pentium III Xeon Intel IXP
Clock speed: 1000 Mhz Clock speed: 166 Mhz
Peak bandwidth: 4 Gbps

100%
RRC CPU
RRC CPU 100%
RRC CPU
RRC
Total MHz : 2087 configuration
8% Iub NP 100%
Iub NP
Iub configuration
NBAP CPU 50% Total Bandwidth:
NBAP CPU NBAP 5 Gbps 25%
configuration
Total MHz: 1123 50%

IuCS/PS NP 100%

RANAP CPU RANAP IuCS/PS NP Iub configuration

50% Total Bandwidth:
Total MHz: 500 configuration
4.4 Gbps
10%

RNSAP CPU Iur NP

RNSAP
70%
Total MHz: 700 configuration Total Bandwidth: 50% Iub configuration
1.8 GBps

Figure 4: Sample configuration for a subscriber base of 300,000

© Wipro Technologies Page: 11 of 16

Radio Network Controller Dimensioning

Here, the assumption is that the load is evenly spread across all the processors – with an assumed upper threshold of 75%
occupancy. Beyond this threshold there may be performance issues in dealing with real time traffic. Therefore, the above
configuration diagram is only intended to provide the number of CPUs required and not give the occupancy of each CPU.
Since the processors used for RRC and RNSAP are relatively underutilized, they can also be used for supporting OAM related
modules. Typically these functionalities would include:
• Support of interface towards the OMC-R
• Support of interface towards local terminals
• Supervision and maintenance of all modules within the RNC
• Performance measurement functions
• Maintenance of central disk-backed database (or any other equivalent data storage base)

Data plane configuration

The link capacity requirements at each interface in order to support a user base of 300,000 subscribers are given here.

RNC
Iub Interface Iu Interface
Nbr of OC-3 links - 32 Nbr of OC-3 links - 29
Data Plane bandwidth - 4.2 Gbps Data Plane bandwidth - 4.2 Gbps
Control Plane bandwidth - 0.8 Gbps Control Plane bandwidth - 0.4 Gbps

Iur Interface
Nbr of OC-3 links - 11
Data Plane bandwidth - 1.5 Gbps
Control Plane bandwidth - 0.2 Gbps

Figure 5: Sample links configuration for a subscriber base of 300,000

Output – RNC specifications

Using the dimensioning technique outlined in this approach note, we have arrived at a typical RNC specification (please refer
Table 6).

© Wipro Technologies Page: 12 of 16

Radio Network Controller Dimensioning

Number of subscribers 300000

Iub Number of OC-3 links 32
Number of n/w processor cards* 2
Iur Number of OC-3 links 11
Number of n/w processor cards* 1
Iu Number of OC-3 links 29
Number of n/w processor cards* 2
NBAP Number of control processor cards* 2
RRC Number of control processor cards* 3
RNSAP Number of control processor cards* 1
RANAP Number of control processor cards* 1
* Network Processor – Intel IXP, Control Processor – Intel Pentium III Xeon

Table 6: Sample RNC specifications

CONCLUSION
In this white paper, an approach to dimensioning the RNC was discussed. The main aspects dealt with were the computation of
user plane requirements, control plane requirements and the link capacity requirements. This approach would prove to be
useful from the RNC designer’s perspective when the expected traffic model is known. Also from the operator’s perspective this
information can be used while considering the impacts related to scaling up the network to meet increased user demands.
It has to be kept in mind that this is an iterative approach. Initially, based on the number of subscribers that needs to be
supported, the model generates a sample RNC configuration. These outputs have to be validated against hardware constraints,
budget constraints and the estimated cost-benefit ratio.
Based on the results of this validation, the desired RNC specifications can be used as inputs to the model to derive the subscriber
base that can be supported. These steps can be performed iteratively to generate the most optimum specifications in terms of
cost, benefits and hardware constraints.

© Wipro Technologies Page: 13 of 16

Radio Network Controller Dimensioning

CONCLUSION
In this white paper, an approach to dimensioning the RNC was discussed. The main aspects dealt with were the computation of
user plane requirements, control plane requirements and the link capacity requirements. This approach would prove to be
useful from the RNC designer’s perspective when the expected traffic model is known. Also from the operator’s perspective this
information can be used while considering the impacts related to scaling up the network to meet increased user demands.
It has to be kept in mind that this is an iterative approach. Initially, based on the number of subscribers that needs to be
supported, the model generates a sample RNC configuration. These outputs have to be validated against hardware constraints,
budget constraints and the estimated cost-benefit ratio.
Based on the results of this validation, the desired RNC specifications can be used as inputs to the model to derive the subscriber
base that can be supported. These steps can be performed iteratively to generate the most optimum specifications in terms of
cost, benefits and hardware constraints.

ACRONYMS
BHCA Busy Hour Call Attempts
Iub Interface between Node-B and RNC
Iur Interface between RNC and RNC
Iu-CS Interface between RNC and Circuit Switched Network
LA Location Area
LOC Lines Of Code
MOCA Mobile Originated Call Attempt
MOTA Mobile Terminated Call Attempt
Iu-PS Interface between RNC and SGSN
NBAP Node B Application Part
RA Routing Area
RANAP RAN Application Part
RNC Radio Network Controller
RNSAP Radio Network Subsystem Application Part
SGSN Serving GPRS Support Node

© Wipro Technologies Page: 14 of 16

Radio Network Controller Dimensioning

REFERENCE
1. 3GPP Standards and Protocol Documents

ABOUT THE AUTHOR

Srivatsa is a Project Leader in Wipro Technologies with about 6 years experience in the telecom domain and 4 years in the
wireless domain. He has been involved in the specification, design, implementation and testing of various features related to
GSM/GPRS base station controller. He holds a bachelor’s degree in Computer Science. His areas of interest include aspects
involving migration of existing wireless 2G systems to 3G systems and integration of wireless systems (GPRS/WLAN).

© Wipro Technologies Page: 15 of 16

Radio Network Controller Dimensioning

ABOUT WIPRO TECHNOLOGIES

Wipro is a PCMM Level 5 and SEI CMMi Level 5 certified global IT Services company providing comprehensive IT solutions and
services (including systems integration, IS outsourcing, package implementation, software application development and
maintenance) and Research and Development services (hardware and software design, development and implementation) to
corporations all over the world. Wipro’s unique value proposition is further delivered through their pioneering offshore
outsourcing Model and stringent Quality Processes of SEI and Six Sigma.

WIPRO IN TELECOM
Wipro Telecom Solutions Division offers comprehensive solutions for telecommunication to confront challenges, and convert
every challenge into an opportunity. With over two decades of telecom experience, Wipro Telecom solutions offers a wide
range of solutions in wireless networking, broadband (data, optical and access networking), voice switching, network
management and hardware design.
Wipro also provides several IPs, components and reference solutions in these domains which help our clients in saving costs
and providing the time-to-market advantage. We offer complete consulting, architecting, design, implementation and
maintenance services to the telecom equipment manufacturers.

For further information visit us at: http://www.wipro.com/telecomandinternetworking

For more whitepapers logon to: http://www.wipro.com/insights

© Copyright 2004. Wipro Technologies. All rights reserved. No part of this document may be reproduced, stored in a retrieval system, transmitted in any form or by any means, electronic, mechanical,
photocopying, recording, or otherwise, without express written permission from Wipro Technologies. Specifications subject to change without notice. All other trademarks mentioned herein are the
property of their respective owners. Specifications subject to change without notice.

Worldwide HQ
Wipro Technologies,
Sarjapur Road,
Bangalore-560 035,
India.

U.S.A. U.K. France

Wipro Technologies Wipro Technologies Wipro Technologies
1300 Crittenden Lane, 137 Euston Road, 91 Rue Du Faubourg,
Mountain View, CA 94043. London, NW1 2 AA. Saint Honoré, 75008 Paris.

Germany Japan U.A.E.

Wipro Technologies Wipro Technologies Wipro Limited
Horn Campus, # 911A, Landmark Tower, Office No. 124,
Kaistrasses 101, 2-1-1 Minatomirai 2-chome, Building 1, First Floor,
Kiel 24114. Nishi-ku, Yokohama 220 8109. Dubai Internet City,
P.O. Box 500119, Dubai.

www.wipro.com
eMail: info@wipro.com

© Wipro Technologies Page: 16 of 16