01 RNC Architecture PDF

7/22/2019 01 RNC Architecture PDF

http://slidepdf.com/reader/full/01-rnc-architecture-pdf 1/85

1 © Nokia Siemens Networks Presentation / Author / Date

For internal use

Nokia Siemens Networks RNC2600

RNC Architecture




For internal use

Agenda

• Introduction

Platform

RNC2600 Software• Architecture

• Cabinet Hardware

• Functionality- Role of RNC in RAN networks

• Interfaces

Physical InterfacesTiming and Synchronisation Interfaces

LAN/Ethernet Interface

Contd….




For internal use

Agenda

• Hardware Capacity

• Capacity Licensing

• Capacity and Reference Call Mix Model

• Redundancy

• RNC roadmap

• Multicontroller RNC

• NSN RNC and competition




For internal use

UMTS network architecture

Iu

OSS

CNRANO&M

Uu

UE

UE = User Equipment

RAN = Radio Access NetworkCN = Core Network

OSS = Operations Support Systems




For internal use

UMTS network architecture

UTRAN Core Network (CN)

Uu

BSS

UE

Gb

s

HLR/AC

Gc

GGSN

A

Gn

PDNGi

MSC/VLR GMSC

E

CD

Gr

Gs

SGSN

EIR

Gf

PSTN

ISDN

s

SCP/CSE

s s

F

RNC

RNC

Node B

Node B

Node B

MS

Um

Uu

Uu

Iub

Iub

Iub

Iur

Iu(PS)

Iu(CS)

Iu(CS)

Iu(PS)

s




For internal use

RNC-Introduction


http://slidepdf.com/reader/full/01-rnc-architecture-pdf 7/857 © Nokia Siemens Networks Presentation / Author / Date

For internal use

Main RNC tasks

The main function of the RNC is to control and manage the Radio AccessNetwork (RAN) and the radio channels. The RNC is designed for efficientuse of radio resources and easy operation and maintenance.

Radio Resource Management

• Admission Control…………. network based function

• Load Control…………………network based function

• Packet Scheduling…………. network based function

• Power Control………………. connection based function• Handover Control……………connection based function

Operation and maintenance

• supervision system

• alarm system• recovery system

• fault diagnosis system



For internal use

NSN RNCs

NSN has 3 RNC products in portfolio,

• all based on IPA platform,

• all using same plug in units

• RNC196

• Available in deliveries 2001 … 2007

• Uses 1.8m tall cabinet,

• 7 HW configurations, max capacity 450 Mbps DL

• Capacity expansions available still today

• RNC450

• Available in deliveries starting RAS05.1, P01/2007

• Uses 2.1m tall cabinet,• Upgrade path to RNC2600 in RU10 release

• RNC2600

• Available RU10 onwards

• Uses 2.1 m tall cabinet



For internal use

RNC196, Original Design

1 2

3

4

5

• RNC196 has been in deliveries since 2001

• Originally RNC196 consisted of 5 capacity steps

• Step1,

• first cabinet

• Steps 2 … 5• Additional subracks in the second cabinet

• Step1, 48 Mbps

• Step 2, 85 Mbps

• Step 3, 122 Mbps

• Step 4, 159 Mbps• Step 5, 196 Mbps



For internal use

RNC450 original standard configurations

3

21

HW step 1

150 Mbps DL

4000 Erl

200 BTSs

600 Cells

HW step 2

300 Mbps DL

6250 Erl

300 BTSs

900 Cells

HW step 3

450 Mbps DL

8000 Erl

512 BTSs

1152 Cells



For internal use

• Flexible transmission solution with IP

• Dynamic Voice & Data capacity• Pay as you grow with SW licensing

• Field proven high availability platform

• Based on IPA platform

• RNCs based on IPA platform havebeen in deliveries since 2001

• HSPA+ Ready

NSN Radio Network Controller



For internal use

• Scalable RNC for all use cases;

• high capacity,• high coverage,

• remote and indoor solutions

• Max Iub capacity of 2.8Gbit/s in RU10 and

3.5Gbit/s in RU20 with two cabinets• 25% more efficient than competition, best

capacity per footprint

• Best traffic load sharing in the market

• Optimized for mobile broadband and flatfee tariffing

• High number of HSPA users

• Capacity licensing

NSN RNC2600




For internal use

3

21

RNC Dimensioning – RNC Variants

RNC2600 - RU10

3500 Mbps DL+UL

70000 Erl/50000 Erl

2800 Cells/ 4800 cells

2840 Mbps

DL+UL

20000 Erl

2800 Cells

RNC45

0

RNC2600 – RU20

450 Mbps DL

8000 Erl

1152 Cells




For internal use

Nokia Siemens Networks RNC2600Platform




For internal use

NSN RNC2600 Architecture - Platform

• The RNC2600 is based on the IPA2800 platform

• The platform allows

• A fault tolerant computing platform

• Constitutes a base for switching

• Offers a wide range of cellular and fixed networkoperations

• The operating system is used as a platform for other systemlevel software and all the application software




For internal use

Nokia Siemens Networks RNC2600RNC2600 Software




For internal use

NSN RNC2600 Software

• The software level for use with the RNC2600 is RN4.0 for

release RU10 and RN5.0 for release RU20.

• Common system software used for all the control computers

• This provides a standard easy to use operatingenvironment for the application software

• Facilitates easy development and maintenance of theapplication software

• Helps the user to understand the software operation




For internal use

Nokia Siemens Networks RNC2600Architecture




For internal use

NSN RNC2600 Architecture

• The NSN RNC2600 has a modular software and Hardware

architecture

• This allows:-▪ Scalability of processing and switching capacity

▪ Flexibility of the number and types of interfaces

▪ New functionality to be added without changing the systemarchitecture

▪ A long operational life span while still being able to support new andup to date features

• The RNC2600 is able to provide more than adequate

computing power that will be necessary to support thecomplex services envisioned for the future.

• The computing environment is fault tolerant (redundancy)




For internal use

NSN RNC2600 Architecture

MXU

MXU

SFU

ICSU

DMCU

RSMU

OMU

WDU

NIP (NIP!)NPS1(P)

DMCUDMCU

TBUEHUEHU

MXU

NIP (NIP!)NPGE(P)

Ethernet

HDD

OMS

ESA24Ethernet

Ethernet

ICSUICSU




For internal use

NSN RNC2600 Architecture - Hardware Changes

• The RNC2600 no longer has:-

• A2SU units – functionality is included in the STM-1interface unit

• GTPU units – functionality is included in the Ethernet orSTM-1 interface units NP8S1-B or NP2GE-B

• RRMU units – functionality is included in ICSU andRSMU/OMU units

• NIP1 – E1/T1/JT1 interfaces are not supported by theRNC2600




For internal use

NSN RNC2600 Architecture - Computer Units

• Multiprocessor based system

• Based on the most suitable commercially availablemicroprocessors

• The data processing capacity is divided amongst severalcomputer unit

• Appropriate redundancy is configured according to theapplication needs

▪ 2N - Hot standby

▪ N+1 - 1 or more spare units designated to a group offunctional units

▪ SN+ - No spare unit is allocated due to the units being partof a resource pool. Extra capacity is already built in to thepool




For internal use

General categories of functional units in RNC

Management and control computer units

• - OMU, ICSU, RSMU, DMCU and NEMU

Switching and multiplexing units

• - SFU, MXU

Network element interface units• - NIU

Units in the timing, power supply, and hardwaremanagement subsystems

• - TBU, Power supply




For internal use

RNC units

•Functional units:

– Logical units created on top of certain HW – Each functional unit has its own functional tasks

– Certain SW modules are loaded to each functional unit type

– Each functional unit has its own redundancy scheme

– Functional unit has certain operations state (WO, SP, TE)

– Example: SFU

• Plug-in-unit

– Physical HW unit

– One plug-in-unit type can be used for one or more functional unit types

– In most of the operations the plug-in-unit type is not relevant for the operator

(e.g. state handling of the units is done for functional units)

– Most of SW does not see the different plug-in-unit types – only functional units




For internal use

NSN RNC2600 Architecture - Control ComputerUnits - OMU

• OMU - Operations and Maintenance Unit

• Serves as an interface between the RNC and Operations andMaintenance Server (OMS)

• Responsible for basic system maintenance functions

• Connects to and controls duplicated system hard disks

containing the operating software and fallback software• Stores the Radio Network database, ATM/IP configuration

database, Equipment database, Alarm History database

• Responsible for Cellular Maintenance functions for recoveringand configuring the radio network

• monitors the status of the network and blocks the faulty unitsif necessary

• 2N redundant plug in unit




For internal use

NSN RNC2600 Architecture - Control ComputerUnits - ICSU

• ICSU - Interface Control and Signalling Unit

• Performs RNC functions that are highly dependant uponsignalling to other network elements

• Handles distributed RRM functions related to the RNC

• The ICSU is responsible for the following tasks

▪ Layer 3 signalling protocols - RANAP, NBAP, RNSAP, RRC.▪ transport network level signalling protocol ALCAP

▪ Handover control

▪ Power control

▪ Load control

▪ Packet scheduler control▪ Location calculations for location based services

• N+1 Redundancy - 1 extra unit




For internal use

NSN RNC2600 Architecture - Control ComputerUnits - RSMU

• RSMU - Resource and Switch Management Unit

• Performs the central resource management tasks

• The RSMU is responsible for the following tasks

▪ Allocation of DSP and resource management for differenttasks - macro diversity combining, data traffic

▪ Supervision and management of DMCUs▪ Software loading of DMCUs

▪ Management of ATM connections in the DMCU

• ATM connection control

• ATM resource management

• 2N redundant




For internal use

NSN RNC2600 Architecture - Signal ProcessingUnits - DMCU

• DMCU - Data and Macro Diversity Combining Unit

• Performs the User Plane and Control Plane related RNCfunctions

• Processors used are▪ General purpose RISC (Reduced Instruction Set Computer)

processor

▪ State of the art Digital Signal Processors

• Signalling processing is configured and altereddynamically for each DSP

• The DMCU is responsible for the following tasks▪ UE and L2 protocols

• Frame protocol (FP)

• Radio Link control (RLC)

• Medium Access control (MAC)

• Application level IP header compression

• SN+ redundant




For internal use

NSN RNC2600 Architecture - Element ManagementUnit - OMS

• OMS - Operations and Maintenance Server

• Provides an interface to

▪ Higher level network management functions (NMS/NetAct)

▪ Local user interface functions (via Application Launcher)

• The OMS is implemented using an Intel based standard

PC core and supports▪ A USB keyboard and mouse

▪ A standard VGA display

▪ USB peripheral devices (flash drives)

▪ A Serial port▪ A 100Mbps Ethernet interface




For internal use

NSN RNC2600 Architecture - Element ManagementUnit - OMS

• Primarily responsible for the RNC Element Management

functions and performs the following tasks▪ Support of Graphical User Interfaces - GUIs

▪ Support for MML/MMI sessions

▪ Provides the NetAct interface to the RNC and NetworkElements

▪ Supports O&M functions in the RNC▪ Post processing support for Measurements and Statistics

▪ Support for the duplicated SCSI interfaces for its massmemory devices (hard disks)

• Operating system is Linux supporting the Linux based

NSN Flexi platform.• The Flexi platform provides high availability and security

• The OMS has no redundancy - does not affect trafficswitching capabilities of the RNC




For internal use

NSN RNC2600 Architecture - Switching andMultiplexing Units

• The RNC2600 Switching and Multiplexing units are

• Based on ATM technology

• The ATM technology provides required capacity andflexibility to support the various traffic types within thenetwork.

• Support capacity and traffic switching within the RNC




For internal use

NSN RNC2600 Architecture - Switching andMultiplexing Units - SFU

• SFU - Switching fabric Unit

• Provides part of the ATM cell switching functionality

• Supports Point to Point and Point to Multi Pointconnection topologies

• Differentiated handling of the various ATM service

categories

• Connects to the Network Interface Units (NIUs) andMultiplexer units (MXUs)

• 2N redundant




For internal use

NSN RNC2600 Architecture - Switching andMultiplexing Units - MXU

• MXU - Multiplexer Unit

• The RNC has several pairs of MXUs depending on theRNC configuration

• The MXU – Multiplexes traffic from the various tributary units to the ATM

SFU

– Allows for the efficient usage of switching resources for the lowbit rate NIUs

– Allows for the efficient usage of computer units with small tomoderate bandwidth requirements (RSMU/ICSU/DMCU)

– Responsible for part of the ATM layer processing functions

▪ Policing▪ Statistics

▪ Operations, Administrations and Maintenance, OAM

▪ Buffer management and scheduling

• 2N redundant

S C S




For internal use

NSN RNC2600 Architecture - Switching andMultiplexing Units - MXU

• The ICSU, DMCU, RSMU all connect to the SFU via the

MXU

NSN RNC2600 A hi Ti i d H d




For internal use

NSN RNC2600 Architecture - Timing and HardwareManagement Bus Unit - TBU

• TBU - Timing Bus Unit

• Duplicated unit

• Two plug in units in each sub rack

• Serial bus that spans all the plug in units in the RNC

•Responsible for

– RNC synchronisation

– Timing signal distribution within the RNC

– Hardware Management System (HMS) message transfer

NSN RNC2600 A hit t N t k I t f




For internal use

NSN RNC2600 Architecture - Network InterfaceUnit - NIU

• NPS1/NPS1P

• Provides 8 x STM-1/OC-3 optical interfaces or 2 x STM-4optical interfaces on the unit’s front panel

• Executes the physical layer and ATM layer functions – Maps ATM cells to and from the SDH/Sonet frame structure

– Header translation

– AAL2 mini packet switching

– Usage Parameter Control (UPC) - UNI / Network ParameterControl (NPC) - NNI

– OAM functions

– Traffic management

– Performance monitoring

– Performance data collection

– Optional reference clock for timing and synchronisation

• The NPS1P supports transport protection (MSP 1+1 /

APS 1+1)

NSN RNC2600 A hit t N t k I t f




For internal use

NSN RNC2600 Architecture - Network InterfaceUnit - NIU

• NPGE/NPGEP

• Executes physical layer and IP layer functionality

– Maps IP packets to and from the Ethernet transmission framestructure

– Header translation

– Traffic management – Performance monitoring

– Performance data collection

• Supports transmission protection for the GigabitEthernet interfaces

NSN RNC2600 A hit t E t l H d



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

NSN RNC2600 Architecture - External HardwareAlarm Unit

• EHU - External Hardware Unit

• Receives alarms from external sources and forwardsthem via the HMS to the OMU located external alarmhandler

• Drives an external lamp panel (EXAU), the cabinet

integrated lamp and any other external notificationequipment

– The EXAU unit is an option

• External device connections handled via a cabling panelat the rear of the RNC cabinet

NSN RNC2600 A hit t 24 P t Eth t




NSN RNC2600 Architecture - 24 Port EthernetSwitch - ESA24

• ESA24 - 24 port Ethernet Switch

• 2 Ethernet ports in the Front panel

• Provides the Ethernet switch functionality required forthe OMS

• 2N redundant

NSN RNC2600 A hit t P i h l D i




NSN RNC2600 Architecture - Peripheral Devices

• The RNC2600 peripheral devices are

• Winchester disk unit for the OMU

• 2N redundant

▪ Duplicated

▪ Separated SCSI interfaces

▪ Serve as non volatile memory for the OMU

▪ Store program code and data for the RNC

▪ Plug in unit type HDS-B

• Hard disk devices for the OMS

▪ Collocated with OMU disks on HDS-B PIUs▪ Configured Raid1

▪ Separated SCSI interfaces




Nokia Siemens Networks RNC2600Cabinet Hardware



NSN RNC2600 Cabinet Hardware




NSN RNC2600 - Cabinet Hardware

Unit type Plug in Unit type

SFU SF20H BISFD/BISFA at back of the cabinet

MXU MX1G6-A BISFB at back of the cabinetOMU CCP18-A 2Gb memory

OMS MCP18-B 4Gb memory

SWU ESA24

ICSU CCP18-C

RSMU CCP18-C

DMCU CDSP-DH

WDU (OMU) WDW73

HDD (OMS) WDW73

NPGEP/NPGE 0 NP2GE-B BISFC at back of the cabinet.NPS1P/NPS1 0 NPS1P/NPS1 0 BISFC at back of the cabinet.

TBU/TBUF TSS3

SUBRACK PWR PD30




Nokia Siemens Networks RNC2600Functionality- Role of RNC in RAN networks

Main RNC tasks sw features




Main RNC tasks, sw features

Radio Resource Management

• Radio Resource Control (RRC)• Admission Control

• Code Allocation

• Power Control

•Handovers

Telecommunication Management

• PS and CS RABs

Operability and Counters, Transport

NSN RNC2600 Functionality Radio Resource




NSN RNC2600 Functionality - Radio ResourceManagement (RRM)

• Radio Resource Management (RRM)

• Manages channel allocations - traffic and signalling thatcan simultaneously be used in the RAN

• Divided into Network based functions and connectionbased functions

NSN RNC2600 Functionality - Radio Resource




NSN RNC2600 Functionality - Radio ResourceManagement (RRM)

• Network based functions can be divided into twocategories

▪ Event Based - as and when required

• Admission Control - used to maintain stability and achieve therequired traffic capacity of the RAN. Executed when the RAB is set upor modified. Also interacts with Handover Control

• Packet Scheduling - takes care of scheduling the radio resources forNRT radio bearers

▪ Continuous

• Load Control - ensures that the system does not become overloaded.If an overload situation does occur it needs to make sure that thesystem is returned to the normal load state as defined by radio networkplanning in a quick and controlled manner

• Connection Based functions are activated when a radiolink is allocated to a connection

▪ Power Control - takes care of the power requirements for the transmittingentities and tries to ensure that all the SIR targets are kept ensuringminimum interference and sufficient quality of the connection

▪ Handover Control - provides support for soft/softer handovers. PrimarilyRNC controlled but can be UE initiated as well

NSN RNC2600 Functionality Telecom




NSN RNC2600 Functionality - Telecom

• Telecom

– Provides basic functionality and End User related features

▪ User Plane (UP) processing towards the Circuit Switched (CS) andPacket Switched (PS) core networks - management of RABs

▪ Radio Network Layer Control Plane processing

▪ Security - Integrity Checking and Ciphering

▪ Location Services

▪ Service Area Broadcast

▪ HSPA functionality

NSN RNC2600 Functionality Operations and




NSN RNC2600 Functionality - Operations andMaintenance (O&M)

• Operations and Maintenance (O&M)

– Provides the means for operations personnel to maintain theRNC and Radio Network in optimal condition

▪ Easy to use Graphical User Interfaces (GIUs) for

• Configuration

• Fault Management

• Performance Management▪ Accessible via Local Management System (LMS) or Network

Management System (NMS)

– Configuration

• Reconfiguration of the RNC

• Reconfiguration of the WBTS

• Reconfiguration of the Radio Network Parameters

• Support for remote software upgrades to the RNC and WBTS

NSN RNC2600 Functionality Operations and




NSN RNC2600 Functionality - Operations andMaintenance (O&M)

• Fault Management

▪ Continuous checking of the network to detect any irregularities inthe operation of the Network Elements

▪ Identification of faulty units in the RNC and notifying the NMS andrecovery system of the problem

▪ Isolates the faulty unit/s from the system and places spare units intooperation if they exist

▪ Fault diagnosis system pinpoints the exact nature of the problemand verifies the status of the faulty unit and the system as a whole

▪ Maintains an alarm and events history

• Performance Management

▪ Continually monitors and collects performance statistics from thenetwork and network elements

▪ Provides the ability to set triggers in order to identify possibleproblem areas in the network before they become a real problem




BREAK……




RNC2600Interfaces

NSN RNC2600 - Interfaces





• RNC2600 Interfaces

• The RNC2600 provides various interfaces between theNetwork Elements situated in the Core Network and theRAN

• Iub Interface

– Connects the WBTS and the RNC▪ 3GPP compliant

▪ NBAP also 3GPP compliant (3GPP TS25.433)

• Iur Interface

– Connects between two RNCs

▪ Manages soft handovers by transferring all the necessary informationand data between the Serving RNC (SRNC) and Drift RNC (DRNC)

▪ The Iur is a standardised open interface






• Iu Interfaces (Iu-CS / Iu-PS)

▪ 3GPP compliant

– The interfaces between the RNC and Core Network are split intotwo separate functional paths

▪ Iu-CS supports Circuit Switched traffic

• Iu-CS normally terminates in the MSC via the MGW

▪ Iu-PS supports Packet Switched traffic• Iu-PS normally terminates in the SGSN

• Iu-BC Interface

– The interface between the RNC and the Cell Broadcast Centre(CBC)

▪ 3GPP compliant

▪ Can be used with any other vendors CBC solution






• Iu-PC Interface

– The interface between the Stand Alone Serving Mobile LocationCentre (S-SMLC)

▪ Uses PCAP protocol

▪ Provides GPS assistance data to the RNC for UE positioning

▪ May also perform the position calculations for different postioningmethods

• Network Management Interface – The interface used to connect the RNC to the Operations Support

System (OSS/NetAct)

▪ Provides the O&M connections between the Radio Network and theOSS

▪ Uses TCP/IP▪ RNC/NetAct application level communication uses CORBA

▪ O&M traffic secured by IPSec protocol between the RNC and NetAct

▪ Supports MML via telnet




Nokia Siemens Networks RNC2600 Physical Interfaces

Timing and Synchronisation Interfaces

LAN/Ethernet Interface

NSN RNC2600 - Physical Interfaces




NSN RNC2600 Physical Interfaces

• STM-1 / OC-3

• The NPS1 or NPS1P functional unit offers ATM overSDH/Sonet interfaces

– The NPS1P offers MSP 1+1 and APS 1+1 protection

• Plug in unit type is NP8S1-B for both NPS1 and NPS1P

• Each plug in unit contains 8 x SDH STM-1/Sonet OC-3optical interfaces

• Gigabit Ethernet

• The NPGE or NPGEP functional unit offers IP overEthernet interfaces

– The NPGEP supports 2N redundancy

• Plug in unit type is NP2GE for both NPGE and NPGEP




Nokia Siemens Networks RNC2600Hardware Capacity

NSN RNC2600 (RU10) - Hardware Capacity




NSN RNC2600 (RU10) Hardware Capacity

RNC2600/1278

Capacity Step 1RNAC sub racks 1 - 4

Iub throughput:

1278Mbps (DL+UL)

RNC2600/2840

Capacity Step 3

RNAC sub racks 1 - 4

RNBC sub racks 1 - 4

Iub throughput:2840Mbps (DL+UL)

RNC2600/2130



Iub throughput:

2130Mbps (DL+UL)






RNC2600/1540


Iub throughput:

1540Mbps (DL+UL) RNC2600/3500

Capacity Step 3


RNBC sub racks 1 - 4Iub throughput:

3500Mbps (DL+UL)

RNC2600/2520Capacity Step 2



Iub throughput:

2520Mbps (DL+UL)






• The RNC2600 can be equipped for three different hardware

configuration steps• RNC2600/1540 (Step 1)

– This consists of 1 cabinet with all the sub racks fully equipped

• RNC2600/2520 (Step 2) – This consists of 2 cabinets - cabinet 1 with all sub racks fully

equipped and cabinet 2 with the first two sub racks fully equipped

• RNC2600/3500 (Step 3) – This consists of 2 cabinets - cabinet 1 with all sub racks fully

equipped and cabinet 2 with all the sub racks fully equipped

• The RNC2600 supports capacity licensing which defines theactual allowed capacity of the RNC2600

• The software only defines the maximum RNC2600 capacityfrom the hardware perspective

NSN RNC2600 (RU10) – Physical Interface




NSN RNC2600 (RU10) Physical InterfaceCapacity

Config.

steps

Iub DL traffic

capacity

(estimate)

Number of interfaces Number of

interface units

Number of functional

units

Iub Mbit/s STM-1 GE

Ethernet

NPS1,

NPS1P

NPGE,

NPGEP

ICSU DMCU MXU

Step 1 900 48 or 24 + 24 16 or 8+8 6 8 14 18 8Step 2 1450 80 or 40 + 40 24 or 12+12 10 12 26 28 12

Step 3 2000 112 or 56 + 56 28 or 14+14 14 14 38 38 16

Capacity steps for RNC2600 at RN4.0 level

NSN RNC2600 (RU20) – Physical Interface




S C 600 ( U 0) ys ca te aceCapacity

Config.

steps

Iub DL traffic

capacity

(estimate)

Number of interfaces Number of

interface units

Number of functional

units

Iub Mbit/s STM-1 GE

Ethernet

NPS1,

NPS1P

NPGE,

NPGEP

ICSU DMCU MXU

Step 1 1540 48 or 24 + 24 16 or 8+8 6 8 14 18 8Step 2 2520 80 or 40 + 40 24 or 12+12 10 12 26 28 12

Step 3 3500 112 or 56 + 56 32 or 16+16 14 16 38 38 16

Capacity steps for RNC2600 at RN5.0 level




Nokia Siemens Networks RNC2600Capacity Licensing

NSN RNC2600 - Capacity licensing




p y g

• The RNC2600 capacity licensing allows for capacityconfigurations based upon the actual RNC2600 traffic

–This allows for cost efficient usage of the RNC2600 resources indifferent networks

• Capacity is licensed using three capacity parameters – Iub PS data throughput in Mbps

– AMR capacity in Erlang

– Number of required carriers• The license keys are required to be installed in the RNC2600

• The initial RNC2600 capacity is defined when ordering theRNC2600

– The corresponding license file will be delivered with the RNC2600

• RNC2600 capacity upgrades can be performed by orderingnew capacity license files and activating them via

– NetAct

– Local Element Manager

RNC2600 with SW Configurable Capacity




g p yLicensing – RU20

• RNC2600 enables capacity licensing

• RNC Capacity can be freelyconfigured with SW license key for:

– Data

– Voice

– Number of Carriers• SW License key enables

incremental usage of HW potential

capacity step 1

0….1540 Mbps DL+UL

0….23800 Erl

0….1440 Cells

capacity step 2

0….2520 Mbps DL+UL

0….47600 Erl

0….2100 Cells

capacity step 3

0….3500 Mbps

DL+UL0….70000 Erl

0….2800 Cells




RNC2600Capacity and Reference Call Mix Model

NSN RNC2600 - Capacity and Reference Call Mix




p yModel – RU20

3

21

1 8xSTM-1 interfaces per unit2 2xGE interfaces per unit

Step 1 Step 2 Step 3

Number of subscribers 680 000 1 360 000 2 000 000CS Busy hour

call attempts 680 000 1 360 000 2 000 000

CS Erlangs

including soft

handover )

23 800 47 600 70 000

PS Busy hour

call attempts 800 000 1 400 000 2 000 000

DL+UL Iub

throughput Mbit/s900 1 450 2 000

Number of

carriers 1 440 2 100 2 800

Number of

BTSs 1 440 2 100 2 800

STM-1 interfaces

(unprotected /

protected) 48 / 24+24 80 / 40+40 112 / 56+56

Gigabit Ethernet

interfaces

(unprotected /

protected) 16 / 8+8 24/12+12 32/16+16

RNC2600High capacity

RNC2600





p yModel

• R99 Iub throughput is calculated as

▪ Downlink (DL) traffic defined at FP level (includes 40% soft handoverSHO)

▪ Uplink (UL) PS traffic 30%

• HSUPA throughput is calculated at the Iu-PS from theeffective HSPA throughput

▪ Does not include SHO

▪ This means that SHO needs to be added on top of the existing 30%

▪ The actual HSUPA throughput in the Iub including SHO is > 30%

• Iur capacity is assumed at 8% of the Iu capacity

• RRC connected mode users include subscribers inCell_DCH, Cell_FACH and Cell_PCH state





p yModel

• Subscriber BHCA and Erlang figures are related to the Voice

Service Call mix below

• The BHCA figure is calculated according to the followingequation:

BHCA = AMR Erl / MHT x 3600

Mean Holding Time (MHT) 90s

Proportion of Handovers 40%

Hard Handovers 0.1 per call

Soft Handovers 2.55 per call

Max AMR Codec 12.65

Traffic per User 25mErl

NAS BHCA per User 3.8

RNC2600 WCDMA Radio Controller

RU10/RU20



73 © Nokia Siemens Networks Presentation / Author / DateFor internal use Feature ID(s): RAN1197, RAN1793

Solution to enable HSPA, voice and services

• Best in class performance and traffic handlingcapability

• One solution, multiple services, all use cases

• Excellent broadband experience with always-on users

Flexible capacity solution

• SW configurable capacity

• Coverage solution

• Full scalability with SW licensing

Future evolution

• HSPA+, IP, VoIP ready

Enabler for HSPA - scalable for all traffic scenarios

2839 Mbps DL+UL

28000 Erl

2800 BTSs

2800 Cells

RU10

3500 Mbps DL+UL

70000 Erl2800 BTSs

4800 Cells

RU20

+20% of HSPA

RNC2600 Coverage Optimised Solution

RU20




42% less RNCs for coverage building

• High capacity RNC2600 enables alsocoverage optimized solutions

• No HW changes required

• Performance change is done with SWconfiguration

• When connected with capacity licensenetwork level capacity needs can befulfilled

in optimized way• Solution control is based on a SW

license

2 cabinets

3500 Mbps DL + UL

70000 Erl

2800 BTSs

2800 Cells

RU20

Feature ID(s): RAN1795

3000 Mbps DL + UL

56000 Erl

2800 BTSs

4800 Cells

Market Leading Latency with NSN RNCRU20/RU30




Further RNC latency

optimization would not have

noticeable impact on

service quality

2 ms

UE

Uu

BTS

RNCCore

HSPA RTT – 32 byte ping

RNC latency target 2 ms – total latency 25 ms

Second to none performance withrecord breaking results:

• RU10 41 ms with optimized 7msRNC latency

• RU20 28 ms with <5 ms RNC latency• mcRNC with 2 ms latency target

Feature ID(s): -

RNC450 Upgrade to RNC2600 RU10



76 © Nokia Siemens NetworksConfidential

Solution for enabling HSPA, voice and services• Best in class traffic handling capability

• One solution, multiple services

• All traffic scenarios, from peak to average

• Flexibility with coverage and capacity solutions

Future evolution

• From HSPA to HSPA+

• Efficient transport solutions

– Native IP

– Hybrid, dual Iub – Direct tunnel support

Capacity upgrade paths

• Gigabit or RNC2600 upgrade options

pg


Enabler for HSPA - one solution, multiple services

3500 Mbps DL+UL

70000 Erl

2800 BTSs

4800 Cells

639 Mbps DL+UL

14000 Erl

600 BTSs

1800 Cells

5.5x capacityincrease

Gigabit+ RNC196 - Upgrade Option

RU20




g pg p

6RNC196/300

196 Mbps DL9520 Erlang512 BTS1152 cells



7

RNC196/450 8

RNC196/step8

1.4 Gbps DL+UL

22400 Erlang

600 BTS

1800 cells

RAS05.1

Flat rate enabler – voice, coverage and HSPA evolution


5RNC196/196

Gigabit+ levelperformance

• Gigabit+ level performance upgrade• Market leading installed base evolution

• Full support for all operator business models




RNC2600Redundancy

Reliability and scalability concepts




For internal use

Duplication (2N)

• one spare unit designated for one active unit

• software in the unit pair is kept synchronized (hot-standby) ->fast switchover

Replacement (N+1)

• one or more units designated to be spare units for a group

• allocating resources to a unit defines it as active, not allocatingresources defines to be spare

• spare unit can replace any active unit in the group -> slowerswitchover, requires warming (cold-standby)

• users responsibility to change the working state of the unit toreflect the resource allocation situation and to leave at least onespare unit

Load sharing (SN+)

• no spare units, group acts as a resource pool

• number of units selected so that there is overcapacity

• if a few units are disabled, the whole group can still perform itsfunctions

No redundancy

• no special requirements for reliability

NSN RNC2600 - Unit Redundancy




For internal use

Functional

Unit

Redundancy Principle

DMCU SN+

EHU None

ICSU N+1

MXU 2N

OMS None

OMU 2N

RSMU 2N

SFU 2N

TBU 2N

WDU 2N

OMS HDD 2N

NPS1 None

NPGE None

NPS1P 2N (MSP 1+1 / APS 1 + 1)

NPGEP 2N (MSP 1+1 / APS 1 + 1)

• 2N - Hot standby

• N+1 - 1 or more spare units

designated to a group offunctional units

• SN+ - No spare unit isallocated due to the unitsbeing part of a resourcepool. Extra capacity isalready built in to the pool

RNC architecture and load sharing




For internal use

• In RNC2600 all the plug in units of the network element are inthe same resource pool regardless of the cabinet or thesubrack they are physically located.

• All User plane and all Control Plane resources are sharedbetween all BTSs connected to RNC2600.

• In NSN RNC there are no dedicated resources for certainBTSs or Iub, Iu CS or Iu PS.

• This allows the most optimal RNC capacity utilization. Theload can be shared over all the units. This is efficient as thetraffic is not evenly shared between BTSs and traffic changesover the time.

• Any RAN interface (Iub, Iu-cs, Iu-ps, ..) can be configured toany physical interface unit or to any physical interface ofRNC2600.

• The same ATM/IP interface unit and even the physicalinterface can have several logical interfaces. This allowsefficient utilization of the physical interfaces in RNC.

NSN RNC

One resource

pool

Competitor A

Several small

resource pools

Load sharing only

possible among

units in the samesubrack




For internal use

RNC roadmap

WCDMA RNC450/2600 Roadmap




For internal use

Capacity (Rel99+HSPA)

• 2.839 Gbps DL+UL

• Max 28 000 Erl AMR

• Max in 2 cabinets

• 2800 BTSs

• 2800 cells

HSPA

• HSDPA 14Mbps/user

Interfaces & Features

• 112/56 unprot/prot STM-1 interfaces

• Iu-PS, Iu-CS, Iur, Iub over IP, Giga-Ethernet

• Common Iub

• Capacity Management Reports*

Capacity

• SW Enhanced RNC2600

- 3.5 Gbps UL + DL

- 70 000 Erl AMR

- 2800 BTSs

- 4800 Cells

HSPA

• HSUPA 5.8 Mbps

• DL 42 Mbps Dual-Cell with 64QAM*

• DL 21 Mbps 64QAM

• DL 28 Mbps MIMO

• CS Voice over HSPA*

Features

• Reduced Downtime for SW Upgrades

Latency

• RNC HSPA latency <5 ms

HSPA

• DL 84 Mbps Dual-Cell with MIMO

• DL 42 Mbps 64QAM & MIMO

• UL 23 Mbps Dual-Cell

• UL 11 Mbps 16QAM

HSPA

• DL 168 Mbps Multi-Cell with MIMO

• Multi-User MIMO

Features• Cositing with mcRNC

RU20RU10 RU30 RU40Available Ready for Contract Under Planning Study Items

(* on top feature

WCDMA mcRNC Roadmap




For internal use

Capacity

• mcRNC 25Gbps

• mcRNC 35Gbps*

HSPA• DL 84 Mbps Dual-Cell with MIMO

• DL 42 Mbps 64QAM & MIMO

• UL 23 Mbps Dual-Cell

• UL 11 Mbps 16QAM

Latency

• mcRNC HSPA latency 2 ms

Capacity

• mcRNC 50Gbps

HSPA

• DL 168 Mbps Multi-Cell with MIMO• Multi-User MIMO

Features

• Local Breakout

• mcRNC Automatic ResourceOptimization

• Warm SW Upgrade

RU30 RU40Under Planning Study Items

(* on top feature



Questions???

01 RNC Architecture PDF

Documents

Transcript of 01 RNC Architecture PDF