RNC 450 / 2600

Oct, 2oo7

For internal use

1 © Nokia Siemens Networks Presentation / Author / Date
Functionality of RNC
Main function of the WCDMA Radio Network Controller (RNC) is to
control and manage the Radio Access Network (RAN) and radio
channels
Key functions:
Management of terrestrial channels
 Allocation of traffic channels in Iu and Iub interfaces

MGW
Management of radio channel configurations in RAN Rel4 MSS
Radio resource management
Admission Control
Resource Manager
Iu-CS
Packet Scheduler A'
Load Control
Power Control
Hand-over control BS
Iub Iu-CS
RNC MGW
Rel99
MGRe
99
Iur Iu-PS ATM
BS Iub

RNC
3G-SGSN
For internal use
2 © Nokia Siemens Networks Presentation / Author / Date
 NSN Radio Network Controller

Scalability to cater for all RNC use

cases from small/remote RNC to high
capacity and indoor solutions
Max capacities of 585 and 2600
Mbit/s
in just two cabinets
Fully HSPA compatible – SW upgrade
only
Flexible Voice & Data capacity
Easy upgradeability and scalability
Fault tolerant, distributed platform
Flexible transmission solution with
evolution to IP

For internal use

3 © Nokia Siemens Networks Presentation / Author / Date
NSN RNC Product Evolution
Secure for investment

RNC product evolution has two paths

• Installed Base product evolution since 1999
• New Delivery product evolution
Platform scalability is turned to customer benefit by creating evolution
and upgrade paths for RNC product
RNC evolution is based on the evolution of functional units under IPA
platform
The three main evolution areas
• Capacity and connectivity based
• Performance based
• Feature or functionality based

For internal use

4 © Nokia Siemens Networks Presentation / Author / Date
 Flexible Voice and Data Capacity

SW configurable capacity
• Data optimized solutions
• Coverage optimized solutions for voice
Easy upgradeability and scalability
• Pay as You grow with flexible capacity
licensing
• Future evolution with upgradeability
• Cost savings by extended lifecycle

For internal use

5 © Nokia Siemens Networks Presentation / Author / Date
 Wide Portfolio of Handovers with
Advanced Functionalities
• Benefit from installed 2G network capacity upon 3G
service launch with maximum interworking
Load and
• Guaranteed service quality even when 3G coverage is service
not ubiquitous handover
• Load balancing between 2G and 3G layers reducing
overall CAPEX needs
• Optimised use of all available 2G and 3G spectrum GSM
GSM
• Ensured service continuity and mobility with e.g. GSM
WCDMA
• Inter-system handovers
WCDMA
• Load and service based handovers
WCDMA
• Coverage based handovers
• IMSI based handover Coverag
W e
• Directed RRC connection setup IDLE
Directed RRC
handover
W connection
• Idle mode control mode
setup for load
control
IMSI reason
based
handover
For internal use
6 © Nokia Siemens Networks Presentation / Author / Date
RNC product

For internal use

7 © Nokia Siemens Networks Presentation / Author / Date
RNC Solution Roadmap
2005 2006 2007 2008 2009 2010 2011

RNC196 based site solutions

RNC196/step6, step7 Upgrade Path to 450M
Upgrade Pack (P1/07) Fixed capacity steps
Capacity/BTS for data or
voice evolution
RNC196 + RNC450 based site solutionsRNC450 (P1/07)

RNC450 to RNC2600
AND Upgrade Pack (2008)

Upgrade Path to RNC2600

RNC450 based site solutions Capacity and coverage options
RNC450 (P1/07) Flexibility for network
RNC450 to RNC2600 evolution
OR Upgrade Pack (2008)

RNC2600 (2008)
RNC2600 based site solutions
High voice, data and cell capacity
Capacity licensing
OR
Scalability and flexibility for
network evolution

For internal use

8 © Nokia Siemens Networks Presentation / Author / Date
RNC450 WCDMA Radio Controller 585 Mbps DL+UL
Enhanced capacity
10000 Erl
600 BTSs
• Meets the increasing user data traffic due to HSDPA usage
1800 Cells
– Capability to launch new services and differentiate
• More RNC capacity; more voice & data capacity
• More AAL2 and STM-1 connectivity for BTS
High number of RRC connected state subscribers
• Enhanced support for always on –services e.g. push email
• Shortens the call setup times i.e. email, video call, gaming
Evolution
• Easy IP transport upgradeability
– Optimized solutions for IP transport
• RNC450 upgrade path to RNC2600
– Secured investment with upgradeability

For internal use

9 © Nokia Siemens Networks Presentation / Author / Date
RNC450 with RAS05.1

In RAS05.1 NSN introduce a new RNC network element RNC450;

• Based on 2100mm high cabinet,

– Enhanced power distribution and cooling 1 2

• Same max 2 cabinet solution

– Same max 4 subracks per cabinet

• Three capacity steps

– 150 Mbit/s, 3
– 300 Mbit/s
– 450 Mbit/s

RNC450 will be based on latest plug-in-units

Number of STM-1 interfaces increased to 24 (protected)

For internal use

10 © Nokia Siemens Networks Presentation / Author / Date
RNC2600 WCDMA Radio Controller 2600 Mbps DL+UL
20000 Erl
evolution, flexibility, scalability 2800 BTSs
2800 Cells
Scalability
• to cater for
all RNC use cases from small/remote RNC to
high capacity and indoor solutions
Flexible capacity solution
• Software scalable capacity steps in four
dimensions
Evolution to IP transport network
• Optimized solutions for IP transport
RNC450 upgrade path to RNC2600
• Secured investment with upgradeability

Capacity Connectivity Scalability

For internal use

11 © Nokia Siemens Networks Presentation / Author / Date
New RNC2600 with RU10

In 2008 NSN will introduce RNC2600;

• Based on 2100mm high cabinet,
– Same cabinet solution as with RNC450
1 2
• Same max 2 cabinet solution
– Same max 4 subracks per cabinet
• Three target capacity steps
– 900 Mbit/s,
– 1450 Mbit/s
– 2000 Mbit/s 3
Transport interfaces
• 2x 1G Ethernet
• 8x STM-1 VC-4

For internal use

12 © Nokia Siemens Networks Presentation / Author / Date
Target Upgrade Path from RNC450 to RNC2600
Planned upgrade requirement:
• a set of new cards, cabling and PIU position changes
• RN SW release upgrade and operating SW upgrade for capacity
• Following plug-in-Unit version levels: (SFU)SF20H, MXU(MX1G6) and
DMCU(CDSP-DH)
SFU(SF20) is compatible only with NP2GE and NP8S1 interface cards
Required Transport interface cards
RNC2600
• NP2GE, 2x 1G Ethernet
• NP8S1, 8x STM-1 VC-4 SF20H

RNC450
MX1G6 1 2
CDSP-DH
NP2GE

1 2 NP8S1

For internal use

13 © Nokia Siemens Networks Presentation / Author / Date
Target Performance for RNC2600 in RU10
solutions for flexible network building
RNC2600 / 3 steps

Total throughput (DL+UL) 2600 Mbps

1 2
IP transport Solution
Capacity Licensing

Scalability for all use cases

Config. Iub traffic capacity Interfaces

RNC2000/
Iub Mbit/s AMR
Erlangs
Number of
BTSs
Carriers
STM-1 /OC-3 Gigabit Ethernet
3
supported
Max Nbr of int unprot. / Max Nbr of int
number (Protected) number of unprot. /
of the the cards (Protected)
cards
step 1 900 8000 1440 1440 6 48 / (24+24) 6 12 / (6+6)
step 2 1450 14000 2100 2100 8 64 / (32+32) 8 16 / (8+8)
step 3 2000 20000 2800 2800 12 96 / (48+48) 12 24 / (12+12)

Capacity and performance stated against NSN (Nokia) traffic mix

For internal use

14 © Nokia Siemens Networks Presentation / Author / Date
RNC2600 with SW Configurable Capacity
Licensing capacity step 3
High capacity RNC2600 enables 0….2000 Mbps DL
capacity licensing in four 0….20000 Erl
dimensions 0….2800 BTSs
Capacity can be freely SW 0….2800 Cells
configured for
• Data capacity step 2
0….1450 Mbps DL
• Voice
0….14000 Erl
• Number of BTS 0….2100 BTSs
• Number of Carriers 0….2100 Cells
Capacity upgrades are possible
only with an upgrade of a SW capacity step 1
license 0….900 Mbps DL
No HW changes is required 0….8000 Erl
0….1440 BTSs
0….1440 Cells

For internal use

15 © Nokia Siemens Networks Presentation / Author / Date
Generic RNC dimensioning
as part of RAN dimensioning

For internal use

16 © Nokia Siemens Networks Presentation / Author / Date
 RNC Dimensioning

Controllers are computing systems

• Several type of units with an ATM-based interconnection User/Control plane
network R99 voice/data
• The load “traffic mix” can take very different forms (all
HSDPA/HSUPA
CS/all PS traffic, SMS, SHO)
• Product configuration have to be suitable for a wide range MHT
of traffic mixes BHCA
• RNC load is a function of customer specific traffic
DL/UL
scenarios and network planning
Target is to maximize the use of the available processing SHO
resources Number of Carriers
• RNC fill rate can be averaged thru simple linear rules Number of BTS
– Simple linear model is based on the Nokia traffic mix
NAS signaling
• Accurate models are needed to address the load of
specific customer traffic mix Active set update
– RDT tool models RNC load thru traffic parameters and Fill factor
results a load of functional units

For internal use

17 © Nokia Siemens Networks Presentation / Author / Date
Traffic Dimensioning Principles for RNC

(Green) The basic assumption is that 60% of

all traffic is not in handover lu-CS or
lub S-RNC lu-PS
(RED/BLACK) Soft handovers SHO cause
40% of the Iub traffic 60%
BTS 40%
• (RED) 32% of the Iub traffic consists of
terminals in inter-BTS handover (S-RNC)
• (BLACK) 8% of the Iub traffic is caused by 32%
terminal in inter-RNC handover. Also visible
in Iur interface (S-RNC - D-RNC) lub 8% lur
Intra-cell or intra-BTS handover traffic is not BTS
D-RNC
visible at the Iub or Iur interfaces.
(BLUE) Total Iu traffic consists of Iub traffic
(with or without intra-RNC handover) and Iur
traffic.

For internal use

18 © Nokia Siemens Networks Presentation / Author / Date
 RNC / RAN dimensioning - Principles
RNC is seen as a black box.
Checking against Product Description-level limits for RNC.
• Connectivity: CS
CS
– AAL2 User Plane Connectivity. max

– Number of BTS. • Traffic:

– AMR Erlang.
– Number of cells. PS
– Iub throughput. PS
Simplified traffic mix rules.
max

• Based on the maximum capacity figures for a single traffic type.

• Attempt to define the capacity with a mix of different traffic
types.
• Based on the NSN (ex. Nokia) reference traffic mix model.

For internal use

19 © Nokia Siemens Networks Presentation / Author / Date
 Baseline for RNC Capacity and Dimensioning
RNC Iub throughput Mbps is the traffic in downlink DL direction defined in FP level and it includes 40 % of SHO.
100 % activity factor is assumed
Additionally 30 % traffic is supported in uplink UL direction (Iub_UL=0.3*Iu_DL*fp_overheads*SHO)
• 0% SHO with HSDPA
Subscribers, BHCA and Erlangs figures are related to Nokia Voice Service Call mix. The packet data throughput
(Mbit/s) is considered for Backround traffic
In the mixed traffic the sum of relative loads of the three traffic types (AMR, CS and PS) over the Iub-interface
has to be less than or equal to 1. Relative load means dividing the offered traffic by the max allowed traffic value:

AMR (Erl) PS data (Mbps) CS data (Mbps)

  1
max AMR ( Erl) max Iub throughput (Mbps) max Iub throughput (Mbps)

Max CS data: CS data (Mbps)  25% max Iub throughput

Max PS data: PS 64(Mbps)  PS128( Mbps)  PS 256(Mbps)  PS 384(Mbps)  HSDPA( Mbps)  max_ Iub _ throughput(Mbps)

Relative rule for PS traffic:

PS 64 (Mbps) PS128 (Mbps) PS 256( Mbps) PS 384 (Mbps) HSDPA ( Mbps)
    1
DMCU max PS64 ( Mbps) DMCU max PS128 ( Mbps) DMCU max PS 256 DMCU max PS384 ( Mbps) DMCU max HSDPA ( Mbps)

For internal use

20 © Nokia Siemens Networks Presentation / Author / Date
 RNC internal dimensioning - Principles
The RAN configuration and RNC-level traffic are assumed to be known.
The most relevant internal resources are modelled
Focus on following functional units: MXU, ICSU, A2SU, DMCU, GTPU.
Unit-specific engineering margins are used to take into account load
unbalance and redundancy
Unit-level load is mostly calculated thru multiple traffic parameters

ICSU model + margin

MXU model + margin

Input values A2SU model + margin RNC internal load

DMCU model + margin

GTPU model + margin

For internal use
21 © Nokia Siemens Networks Presentation / Author / Date
 What is “NAS” signalling?
“NAS signalling” event frequency is an input parameter for the tool.
• NAS = Non Access Stratum.

“NAS signalling” does not include call-related procedures (e.g. paging)

• This type of NAS signalling is taken into account separately.

“NAS signalling” includes the following activities or services:

• CS Core Network procedures
– Location updates (inter/intra MSC, periodic)
– Imsi attach and detach • PS Core Network procedures
– SMS, MMS – Cell Update
– Routing Area Update
• Value-added service procedures
– GPRS Attach/Detach
– Location services
– PDP Context
Activation/Modification/Deactivation
– PS SMS

For internal use

22 © Nokia Siemens Networks Presentation / Author / Date
 What is RDT (RNC Dimensioning Tool)

Purpose:
provide help in answering customer requests about the dimensioning of standard
RNC IPA configurations, especially concerning control plane load.
Principle:
for a selected RNC configuration, and a specified applied traffic, the Excel-based
tool estimates the RNC load.
Customisation:
the tool initially uses default input values corresponding to a standard applied
traffic for the selected RNC configuration, default values can be overridden, the
other default input values are then automatically adjusted.
Limitation:
the tool focuses on internal RNC resources, the load of other resources is not
checked (e.g. network interface units).

Link to RDT:
http://wikis.inside.nokiasiemensnetworks.com/bin/view/PerformanceOfRNC/RDT

For internal use

23 © Nokia Siemens Networks Presentation / Author / Date
 RNC Dimensioning Tool (RDT) – Preview

Level Category Group Name Description Value Units Value Custom

Software level per RN2.2 set
Hide Show
Logical configuration RNC196
Des cription details
Capacity step 450M

1 RNC no_of_subscribers The number of subscribers RNC # 363 636

1 RNC no_of_nodeBs The number of base stations RNC # 300 300
1 RNC no_of_cells The number of cells RNC # 800 800
1 RNC no_of_RACs The number of routing areas under RNC RNC # 5 5
1 RNC no_of_LACs The number of location areas under RNC RNC # 2 2
1 RNC A nodeb_aal2_up_connectivity The average AAL2 UP connectivity at ATM level, per NodeB nodeB Mbit/s 10.9
1 RNC B nodeb_AAL2_up_vccs The average number of AAL2 UP VCCs, per NodeB nodeB # 3.0

RNC load Configuration: RNC196/450M

Target Estimated Relative
Unit Resource fill factor fill factor fill factor Main sources of load
ICSU CPU 70% 32% 46% Call attempts, SHO, NAS signalling, measurements, ...
GTPU CPU 80% 5% 6% Iu-PS traffic: number of IP packets per second.
GTPU bit rate 100% 9% 9% Iu-PS traffic: total bit rate. Note: the average packet size has an impact.
DMCU 80% 0% 0% User traffic, common channel traffic, …
MXU CPU 80% 46% 58% AAL2 leg setups per second (call attempts, SHO, NAS signalling, ...)

RNC fill factors 100% 58% 58%

Most used resource MXU CPU

For internal use

24 © Nokia Siemens Networks Presentation / Author / Date
Suggested guidelines for RNC dimensioning

Do the dimensioning as specified by the operator (input data, constraints, …).

If parameters are missing, preferably use the Nokia Siemens Networks
reference call model, and do this explicitly, i.e. document the assumptions
made on top of the given input.
Delay introducing additional factors of load until the final steps of
dimensioning, or before it is explicitly requested.
Most sensitive parameters in the reference call model:
• Call MHT
• Interval between SHO for a call (Active set update)
• Proportion of mobile terminated calls
• AMR traffic per user
• Share of NAS signaling
• Mix of data usage, R99 & HSPA

For internal use

25 © Nokia Siemens Networks Presentation / Author / Date
Sales items and ordering, Nokia Configurator

RAS05.1/RN2.2 HW items are available in

Nokia Configurator tool in tendering side.
RNC450 and RNC196 new capacity
extensions available
NC instructs for the needed upgrade
packages in the capacity extension

For internal use

26 © Nokia Siemens Networks Presentation / Author / Date
Main Sales Items for RNC450
1st capacity step
• Cabinet A with HW for 4 subracks
2nd capacity step
• Cabinet A+B with HW for 6 subracks
3rd capacity step
• Cabinet A+B with HW for 8 subracks
Transport interface cards
RNC sales items (HW + OSW) in RNC product catalog

For internal use

27 © Nokia Siemens Networks Presentation / Author / Date
 ‫شكرا‬
Thank you!
Herzlichen Dank!
Paljon Kiitoksia!
Merci Bien!
ευχαριστώ ! Muchas Gracias!
For internal use
28 © Nokia Siemens Networks Presentation / Author / Date