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 Management of radio channel configurations in RAN

MGW Rel4

MSS

Radio resource management Admission Control Resource Manager Packet Scheduler Load Control Power Control Hand-over control
For internal use 2 Nokia Siemens Networks

Iu-CS A'
BS

Iub
RNC

Iu-CS
MGW Rel99 MGRe

BS

Iub

Iur
RNC

Iu-PS

3G-SGSN
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 Guaranteed service quality even when 3G coverage is not ubiquitous Load balancing between 2G and 3G layers reducing overall CAPEX needs Optimised use of all available 2G and 3G spectrum Ensured service continuity and mobility with e.g. Inter-system handovers Load and service based handovers Coverage based handovers IMSI based handover Directed RRC connection setup IDLE mode Idle mode control
control IMSI based handover Load and service handover

Directed RRC connection setup for load reason

Coverag e handov er

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 Pack (P1/07)

Upgrade Path to 450M Fixed capacity steps Capacity/BTS for data or voice evolution

RNC196 + RNC450 based site solutions RNC450 (P1/07) AND RNC450 based site solutions
RNC450 (P1/07) RNC450 to RNC2600 Upgrade Pack (2008)

OR RNC2600 based site solutions

RNC450 to RNC2600 Upgrade Pack (2008)

Upgrade Path to RNC2600 Capacity and coverage options Flexibility for network evolution

RNC2600 (2008)

OR

High voice, data and cell capacity Capacity licensing Scalability and flexibility for network evolution

For internal use 8 Nokia Siemens Networks

Presentation / Author / Date

RNC450 WCDMA Radio Controller

Enhanced capacity Meets the increasing user data traffic due to HSDPA usage 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

585 Mbps DL+UL 10000 Erl 600 BTSs 1800 Cells

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 Same max 2 cabinet solution Same max 4 subracks per cabinet Three capacity steps 150 Mbit/s, 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

evolution, flexibility, scalability
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

2600 Mbps DL+UL 20000 Erl 2800 BTSs 2800 Cells

Capacity
For internal use 11 Nokia Siemens Networks

Connectivity
Presentation / Author / Date

Scalability

New RNC2600 with RU10

In 2008 NSN will introduce RNC2600; Based on 2100mm high cabinet, Same cabinet solution as with RNC450 Same max 2 cabinet solution Same max 4 subracks per cabinet Three target capacity steps 900 Mbit/s, 1450 Mbit/s 2000 Mbit/s 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 NP2GE, 2x 1G Ethernet SF20H NP8S1, 8x STM-1 VC-4 MX1G6

RNC2600

RNC450

CDSP-DH

NP2GE NP8S1

3 3
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 IP transport Solution Capacity Licensing Scalability for all use cases
Config. RNC2000/ Iub traffic capacity Iub Mbit/s AMR Erlangs Number of BTSs supported Carriers Interfaces STM-1 /OC-3 Gigabit Ethernet

step 1 step 2 step 3

900 1450 2000

8000 14000 20000

1440 2100 2800

1440 2100 2800

Max number of the cards 6 8 12

Nbr of int unprot. / (Protected)

Max number of the cards 6 8 12

Nbr of int unprot. / (Protected) 12 / (6+6) 16 / (8+8) 24 / (12+12)

48 / (24+24) 64 / (32+32) 96 / (48+48)

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 0.2000 Mbps DL High capacity RNC2600 enables 0.20000 Erl capacity licensing in four dimensions 0.2800 BTSs 0.2800 Cells Capacity can be freely SW configured for capacity step Data 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 capacity step only with an upgrade of a SW 1 license 0.900 Mbps DL 0.8000 Erl No HW changes is required
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 network The load traffic mix can take very different forms (all CS/all PS traffic, SMS, SHO) Product configuration have to be suitable for a wide range of traffic mixes RNC load is a function of customer specific traffic scenarios and network planning Target is to maximize the use of the available processing resources RNC fill rate can be averaged thru simple linear rules Simple linear model is based on the Nokia traffic mix Accurate models are needed to address the load of specific customer traffic mix RDT tool models RNC load thru traffic parameters and results a load of functional units
For internal use 17 Nokia Siemens Networks Presentation / Author / Date

User/Control plane R99 voice/data HSDPA/HSUPA MHT BHCA DL/UL SHO Number of Carriers Number of BTS NAS signaling Active set update Fill factor

Traffic Dimensioning Principles for RNC

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

lub BTS

S-RNC 60% 40%

lu-CS or lu-PS

32% lub BTS 8% lur D-RNC

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. CS Connectivity: CS AAL2 User Plane Connectivity. Number of BTS. Traffic: AMR Erlang. Number of cells. PS Iub throughput. PS Simplified traffic mix rules. 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.
max max 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)   e1 max AMR (Erl) max Iub throughput (Mbps) max Iub throughput (Mbps)

Max CS data: Max PS data:

CS data (Mbps) e 25% max Iub throughput

PS 64( Mbps )  PS128( Mbps )  PS 256( Mbps )  PS 384( Mbps )  HSDPA( Mbps ) e max_ Iub _ throughput ( Mbps)

Relative rule for PS traffic:

PS 64 (Mbps) PS128 (Mbps) PS 256( Mbps ) PS 384 (Mbps) HSDPA( Mbps )     e1 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 MXU model Input values A2SU model DMCU model GTPU model
For internal use 21 Nokia Siemens Networks Presentation / Author / Date

+ margin + margin + margin + margin + margin RNC internal load

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 Value-added service procedures Routing Area Update Location services GPRS Attach/Detach

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
Hide Description

Description Software level Logical configuration Capacity step The number of subscribers The number of base stations The number of cells The number of routing areas under RNC The number of location areas under RNC The average AAL2 UP connectivity at ATM level, per NodeB The average number of AAL2 UP VCCs, per NodeB

Value per

Units

Value RN2.2 Show RNC196 details 450M 363 636 300 800 5 2 10.9 3.0

Custom set

1 1 1 1 1 1 1

RNC RNC RNC RNC RNC RNC RNC

A B

no_of_subscribers no_of_nodeBs no_of_cells no_of_RACs no_of_LACs nodeb_aal2_up_connectivity nodeb_AAL2_up_vccs

RNC RNC RNC RNC RNC nodeB nodeB

# # # # # Mbit/s #

300 800 5 2

RNC load Unit ICSU GTPU GTPU DMCU MXU

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

RNC fill factors Most used resource

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