5-0+RNC+2600

1 © Nokia Siemens Networks Presentation / Author / DateFor internal use

RNC 450 / 2600Oct, 2oo7


Functionality of RNC

Key functions:

Management of terrestrial channels Allocation of traffic channels in Iu and Iub interfaces

Management of radio channel configurations in RANRadio resource management

Admission Control Resource Manager Packet Scheduler Load Control Power Control Hand-over control

Main function of the WCDMA Radio Network Controller (RNC) is to control and manage the Radio Access Network (RAN) and

radio channels

Iu-CS

Iub Iur Iu-PS

Iub BS

BS

RNC MGW Rel99MGRe99 ATM

MSS

3G-SGSN

RNC

A' Iu-CS

MGW Rel4


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

NSN Radio Network Controller


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


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


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 control

WCDMAGSM

GSMGSM

WW

WCDMA

WCDMA

IDLE mode

control IMSI based

handover

Directed RRC

connection setup for

load reason

Coverage

handover

Load and service

handover


RNC product


AND

RNC Solution Roadmap

RNC196 based site solutions

RNC196 + RNC450 based site solutions

RNC450 based site solutions

20062006 20072007 20082008 20092009 20102010 2011201120052005

RNC196/step6, step7

Upgrade Pack (P1/07)

RNC450 (P1/07)

RNC450 to RNC2600

Upgrade Pack (2008)

ORRNC450 to RNC2600

Upgrade Pack (2008)

RNC2600 based site solutionsRNC2600 (2008)

RNC450 (P1/07)

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

Upgrade Path to RNC2600Capacity and coverage optionsFlexibility for network evolution

High voice, data and cell capacityCapacity licensingScalability and flexibility for network evolution

OR


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

RNC450 WCDMA Radio Controller 585 Mbps DL+UL

10000 Erl600 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)

3

21


Scalability

• to cater forall 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

RNC2600 WCDMA Radio Controller

evolution, flexibility, scalability

2600 Mbps DL+UL

20000 Erl

2800 BTSs

2800 Cells

CapacityCapacity ConnectivityConnectivity ScalabilityScalability


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

3

21


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

• NP8S1, 8x STM-1 VC-4 SF20HMX1G6

CDSP-DHNP2GE

NP8S1

RNC450

RNC2600

3

21

3

21

Target Upgrade Path from RNC450 to RNC2600


Target Performance for RNC2600 in RU10

Capacity and performance stated against NSN (Nokia) traffic mix

solutions for flexible network building

3

21Total throughput (DL+UL) 2600 Mbps

RNC2600 / 3 steps

IP transport Solution

Scalability for all use cases

Capacity Licensing

Config.

Iub Mbit/s AMR Erlangs

Number of BTSs supported

Carriers

Max number of the cards

Nbr of int unprot. / (Protected)

Max number of the cards

Nbr of int unprot. / (Protected)

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)

Gigabit EthernetSTM-1 /OC-3InterfacesIub traffic capacity

RNC2000/


RNC2600 with SW Configurable Capacity LicensingHigh capacity RNC2600 enables capacity licensing in four dimensions

Capacity can be freely SW configured for

• Data

• Voice

• Number of BTS

• Number of Carriers

Capacity upgrades are possible only with an upgrade of a SW license

No HW changes is required

capacity step 10….900 Mbps

DL

0….8000 Erl

0….1440 BTSs

0….1440 Cells


DL

0….14000 Erl

0….2100 BTSs

0….2100 Cells


DL

0….20000 Erl

0….2800 BTSs

0….2800 Cells


Generic RNC dimensioningas part of RAN dimensioning


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

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.

D-RNC

60%40%

8% lurlub

BTS

BTS

lub S-RNClu-CS orlu-PS

32%


RNC / RAN dimensioning - Principles

RNC is seen as a black box.

Checking against Product Description-level limits for RNC.

• Connectivity:

–AAL2 User Plane Connectivity.

–Number of BTS.

–Number of cells.

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.

• Traffic:

– AMR Erlang.

– Iub throughput.

CS

PS

CSmax

PSmax


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

1(Mbps)t throughpuIubax m

(Mbps) data CS

(Mbps)t throughpuIubmax

(Mbps) data PS

)Erl( AMR max

)Erl( AMR

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

Relative rule for PS traffic:

1)(max

)(

)( S384 max

(Mbps) 384

256max

)(256

)( S128 max

(Mbps) 128

)( S64 max

(Mbps) 64

MbpsHSDPADMCU

MbpsHSDPA

MbpsPDMCU

PS

PSDMCU

MbpsPS

MbpsPDMCU

PS

MbpsPDMCU

PS

)(_max_)()(384)(256)(128)(64 MbpsthroughputIubMbpsHSDPAMbpsPSMbpsPSMbpsPSMbpsPS Max PS data:


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

Input values

ICSU model

MXU model

DMCU model

A2SU model

GTPU model

+ 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

– SMS, MMS

• Value-added service procedures

– Location services

• PS Core Network procedures

– Cell Update

– Routing Area Update

– GPRS Attach/Detach

– PDP Context Activation/Modification/Deactivation

– PS SMS


What is RDT (RNC Dimensioning Tool)

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

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


RNC Dimensioning Tool (RDT) – Preview

Level Category Group Name Description Value Units Value CustomSoftware level per RN2.2 setLogical configuration RNC196Capacity step 450M

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

Hide Description

Show details

RNC load Configuration: RNC196/450M

Unit ResourceTarget fill factor

Estimated fill factor

Relative 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


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


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


Main Sales Items for RNC450 1st capacity step• Cabinet A with HW for 4 subracks2nd capacity step• Cabinet A+B with HW for 6 subracks3rd capacity step• Cabinet A+B with HW for 8 subracksTransport interface cardsRNC sales items (HW + OSW) in RNC product catalog


Herzlichen Dank!

Merci Bien!

Thank you!

Muchas Gracias!

Paljon Kiitoksia!

ευχαριστώ !

شكرا

5-0+RNC+2600

Documents

rnc capacity

rnc2600 capacity

rnc product rnc evolution

high capacity

g network capacity

network evolution rnc2600

rnc use cases

controlfor internal