RNC2600 Introduction

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

Nokia Siemens Networks RNC2600Radio Access


Agenda• Introduction Platform RNC2600 Software

• Architecture• Cabinet Hardware• Functionality- Role of RNC in RAN networks• Interfaces

Physical Interfaces • Hardware Capacity • Capacity Licensing • Redundancy


UMTS network architecture

Iu

OSS

CNRANO&M

Uu

UE

UE = User EquipmentRAN = Radio Access NetworkCN = Core NetworkOSS = Operations Support Systems


RNC-Introduction


Main RNC tasksThe main function of the RNC is to control and manage the Radio Access

Network (RAN) and the radio channels. The RNC is designed for efficient use 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


NSN RNCsNSN 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


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


RNC450 original standard configurations

3

21

HW step 1150 Mbps DL4000 Erl200 BTSs

600 Cells

HW step 2300 Mbps DL6250 Erl300 BTSs 900 Cells

HW step 3450 Mbps DL8000 Erl512 BTSs 1152 Cells


• 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

• Best traffic load sharing in the market• Optimized for mobile broadband and flat

fee tariffing• High number of HSPA users• Capacity licensing

NSN RNC2600


RNC2600 with RU20

• 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– 1540 Mbit/s DL+UL– 2520 Mbit/s DL+UL– 3500 Mbit/s DL+UL

• Transport interfaces per unit– 2x 1G Ethernet– 8x STM-1 VC-4

3

21


3

21

RNC Dimensioning – RNC VariantsRNC2600 - RU10

3500 Mbps DL+UL70000 Erl/50000 Erl2800 Cells/ 4800 cells

2840 Mbps DL+UL20000 Erl2800 Cells

RNC450 RNC2600 – RU20

450 Mbps DL8000 Erl1152 Cells


Nokia Siemens Networks RNC2600Platform


NSN RNC2600 Architecture - Platform

• The RNC2600 is based on the IPA2800 A8/A9 platform• The platform allows

• A fault tolerant computing platform• Constitutes a base for switching• Offers a wide range of cellular and fixed network

operations• The operating system is used as a platform for other system

level software and all the application software


Nokia Siemens Networks RNC2600RNC2600 Software


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 operating

environment for the application software• Facilitates easy development and maintenance of the

application software• Helps the user to understand the software operation


Nokia Siemens Networks RNC2600Architecture


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 system

architecture▪ A long operational life span while still being able to support new and

up to date features

• The RNC2600 is able to provide more than adequate computing power that will be necessary to support the complex services envisioned for the future.

• The computing environment is fault tolerant (redundancy)


NSN RNC2600 Architecture

MXU

MXU

SFU

ICSU

DMCU

RSMU

OMU

WDU

NIP (NIP!)NPS1(P)

DMCUDMCU

TBU EHUEHU

MXU

NIP (NIP!)NPGE(P)

Ethernet

HDD

OMS

ESA24Ethernet

Ethernet

ICSUICSU


NSN RNC2600 Architecture - Hardware Changes

• The RNC2600 no longer has:-• A2SU units – functionality is included in the STM-1

interface unit• GTPU units – functionality is included in the Ethernet or

STM-1 interface units NP8S1-B or NP2GE-B• RRMU units – functionality is included in ICSU and

RSMU/OMU units• NIP1 – E1/T1/JT1 interfaces are not supported by the

RNC2600


NSN RNC2600 Architecture - Computer Units

• Multiprocessor based system• Based on the most suitable commercially available

microprocessors• The data processing capacity is divided amongst several

computer unit• Appropriate redundancy is configured according to the

application needs▪ 2N - Hot standby▪ N+1 - 1 or more spare units designated to a group of

functional units▪ SN+ - No spare unit is allocated due to the units being part

of a resource pool. Extra capacity is already built in to the pool


General categories of functional units in RNC

Management and control computer units • - OMU, ICSU, RSMU, DMCU and OMS

Switching and multiplexing units• - SFU, MXU

Network element interface units• - NIU

Units in the timing, power supply, and hardware management subsystems• - TBU, Power supply


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– Example: SF20H


NSN RNC2600 Architecture - Control Computer Units - OMU • OMU - Operations and Maintenance Unit

• Serves as an interface between the RNC and Operations and Maintenance 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 recovering

and configuring the radio network• monitors the status of the network and blocks the faulty units

if necessary• 2N redundant plug in unit


NSN RNC2600 Architecture - Control Computer Units - ICSU • ICSU - Interface Control and Signalling Unit

• Performs RNC functions that are highly dependant upon signalling 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, SABP

▪ 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


NSN RNC2600 Architecture - Control Computer Units - 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 different tasks - 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


NSN RNC2600 Architecture - Signal Processing Units - DMCU • DMCU - Data and Macro Diversity Combining Unit

• Performs the User Plane and Control Plane related RNC functions

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

processor▪ State of the art Digital Signal Processors

• Signalling processing is configured and altered dynamically 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


NSN RNC2600 Architecture - Element Management Unit - 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

▪ SCSI Interfaces to its own mass memory devices (2 - Raid1)▪ A USB keyboard and mouse▪ A standard VGA display▪ USB peripheral devices (flash drives)▪ A Serial port▪ A 100Mbps Ethernet interface


NSN RNC2600 Architecture - Element Management Unit - 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 Network

Elements▪ Supports O&M functions in the RNC▪ Post processing support for Measurements and Statistics▪ Support for the duplicated SCSI interfaces for its mass

memory 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 traffic

switching capabilities of the RNC


NSN RNC2600 Architecture - Switching and Multiplexing Units• The RNC2600 Switching and Multiplexing units are

• Based on ATM technology• The ATM technology provides required capacity and

flexibility to support the various traffic types within the network.

• Support capacity and traffic switching within the RNC


NSN RNC2600 Architecture - Switching and Multiplexing Units - SFU• SFU - Switching fabric Unit

• Provides part of the ATM cell switching functionality• Supports Point to Point and Point to Multi Point

connection topologies• Differentiated handling of the various ATM service

categories• Connects to the Network Interface Units (NIUs) and

Multiplexer units (MXUs)• 2N redundant


NSN RNC2600 Architecture - Switching and Multiplexing Units - MXU• MXU - Multiplexer Unit

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

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

SFU– Allows for the efficient usage of switching resources for the low

bit rate NIUs– Allows for the efficient usage of computer units with small to

moderate 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


NSN RNC2600 Architecture - Switching and Multiplexing Units - MXU

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


NSN RNC2600 Architecture - Timing and Hardware Management 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 Architecture - Network Interface Unit - NIU• NPS1/NPS1P

• Provides 8 x STM-1/OC-3 optical interfaces or 2 x STM-4 optical 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 Parameter

Control (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 Architecture - Network Interface Unit - NIU• NPGE/NPGEP

• Executes physical layer and IP layer functionality– Maps IP packets to and from the Ethernet transmission frame

structure– Header translation– Traffic management– Performance monitoring– Performance data collection

• Supports transmission protection for the Gigabit Ethernet interfaces


NSN RNC2600 Architecture - External Hardware Alarm Unit• EHU - External Hardware Unit

• Receives alarms from external sources and forwards them via the HMS to the OMU located external alarm handler

• Drives an external lamp panel (EXAU), the cabinet integrated lamp and any other external notification equipment

– The EXAU unit is an option

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


NSN RNC2600 Architecture - 24 Port Ethernet Switch - ESA24• ESA24 - 24 port Ethernet Switch

• 2 Ethernet ports in the Front panel• Provides the Ethernet switch functionality required for

the OMS• 2N redundant


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 HardwareRNAC

19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

1

19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

1

19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

1

19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

1

30

29 28

27 26

25 24

23 22

21 20

19 18

17 16

15 14

13 12

11 10

09 08

31

30

29 28

27 26

25 24

23 22

21 20

19 18

17 16

15 14

13 12

11 10

09 08

31

07

06

05

04

03

02

01

00

07

06

05

04

03

02

01

00

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

CPSY-B EXT2 CPSY-A EXT1, ETH24

Optional CPAL-A CPAL-A

Front view Rear view

RNAC

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

4

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

3

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1

TSS3

MX

U 0

MX

U 1

SFU

0

NP

S1(

P)/

NP

GE

(P) 0

RS

MU

0

DM

CU

0

DM

CU

1

ICS

U 0

DM

CU

2

DM

CU

3

SW

U 0

OM

S

PD

30

A: W

DU

0 (O

MU

)

B: H

DD

0 (O

MS

)

OM

U 0

MXU

2

MXU

3

SFU

1

NP

S1(

P)/

NP

GE

(P) 1

A: W

DU

1 (O

MU

)

B: H

DD

1 (O

MS

)

RS

MU

1

ICSU

2

ICSU

1

DM

CU

6

DM

CU

7

DM

CU

4

DM

CU

5

SW

U 1

PD

30

OM

U 1

MX

U 4

MX

U 5

NP

S1(

P)/

NP

GE

(P) 4

NP

S1(

P)/

NP

GE

(P) 2

EHU

ICS

U 3

DM

CU

11

ICS

U 4

ICS

U 7

ICS

U 5

ICS

U 6

DM

CU

8

DM

CU

9

DM

CU

10

DM

CU

12

PD30

NP

S1(

P) /

NPG

E(P

) 5

MXU

6

MXU

7

NP

S1(

P)/

NP

GE

(P) 3

ICSU

13

ICSU

8

DM

CU

16

ICSU

9

ICSU

10

ICSU

11

ICSU

12

DM

CU

17

DM

CU

13

DM

CU

14

DM

CU

15

PD

30

TBU

FTS

S3

TSS

3TB

UF

TBU

FTB

UF

TBU

FTB

UF

RNBC

19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

1

19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

1

19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

1

19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

1

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

Front view Rear view

RNBC

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

4

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

3

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1

NP

S1(

P)/

NP

GE

(P)

13

MX

U 1

4

MX

U 1

5

NP

S1(

P)/

NP

GE

(P) 1

1

ICS

U 3

3IC

SU

32

ICS

U 3

7

DM

CU

36

ICS

U 3

5IC

SU

34

ICS

U 3

6D

MC

U 3

3D

MC

U 3

4D

MC

U 3

5

DM

CU

37

PD

30M

XU

12

MX

U 1

3

NP

S1(

P)/

NP

GE

(P)

12

NP

S1(

P)/

NP

GE

(P) 1

0

ICS

U 2

7IC

SU

26

ICS

U 3

1

DM

CU

31

ICS

U 2

9IC

SU

28

ICS

U 3

0D

MC

U 2

8D

MC

U 2

9D

MC

U 3

0

DM

CU

32

PD

30

NP

S1(

P)/

NP

GE(

P)

9

MX

U 1

0

MX

U 1

1

NP

S1(

P)/

NP

GE

(P) 7

ICS

U 2

1IC

SU

20

ICS

U 2

5

DM

CU

23

DM

CU

26

ICS

U 2

3IC

SU

22

ICS

U 2

4

DM

CU

24

DM

CU

25

DM

CU

27

PD

30M

XU

8

MX

U 9

NP

S1(

P)/

NP

GE

(P)

8

NP

S1(

P)/

NP

GE

(P) 6

ICS

U 1

5IC

SU

14

ICS

U 1

9

DM

CU

21

ICS

U 1

7IC

SU

16

ICS

U 1

8D

MC

U 1

8D

MC

U 1

9D

MC

U 2

0

PD

30

DM

CU

22

TBU

FTB

UF

TBU

FTB

UF

TBU

FTB

UF

TBU

FTB

UF


NSN RNC2600 - Cabinet Hardware

TSS3TBU/TBUFPD30SUBRACK PWR

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

WDW73HDD (OMS)WDW73WDU (OMU)CDSP-DHDMCUCCP18-CRSMUCCP18-CICSUESA24SWU

4Gb memoryMCP18-BOMS2Gb memoryCCP18-AOMUBISFB at back of the cabinetMX1G6-AMXUBISFD/BISFA at back of the cabinetSF20HSFU

Plug in Unit typeUnit type


Nokia Siemens Networks RNC2600Functionality- Role of RNC in RAN networks


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 Management (RRM)• Radio Resource Management (RRM)

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

• Divided into Network based functions and connection based functions


NSN RNC2600 Functionality - Radio Resource Management (RRM)

• Network based functions can be divided into two categories

▪ Event Based - as and when required• Admission Control - used to maintain stability and achieve the

required traffic capacity of the RAN. Executed when the RAB is set up or modified. Also interacts with Handover Control

• Packet Scheduling - takes care of scheduling the radio resources for NRT 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 the system is returned to the normal load state as defined by radio network planning in a quick and controlled manner

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

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

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


NSN RNC2600 Functionality - Telecom

• Telecom– Provides basic functionality and End User related features

▪ User Plane (UP) processing towards the Circuit Switched (CS) and Packet 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 Maintenance (O&M)

• Operations and Maintenance (O&M)– Provides the means for operations personnel to maintain the

RNC 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 Maintenance (O&M)

• Fault Management▪ Continuous checking of the network to detect any irregularities in

the operation of the Network Elements▪ Identification of faulty units in the RNC and notifying the NMS and

recovery system of the problem▪ Isolates the faulty unit/s from the system and places spare units into

operation if they exist▪ Fault diagnosis system pinpoints the exact nature of the problem

and 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 the

network and network elements▪ Provides the ability to set triggers in order to identify possible

problem areas in the network before they become a real problem


RNC2600Interfaces


NSN RNC2600 - Interfaces



• RNC2600 Interfaces• The RNC2600 provides various interfaces between the

Network Elements situated in the Core Network and the RAN

• 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 information and 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 into two 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 Location

Centre (S-SMLC)▪ Uses PCAP protocol▪ Provides GPS assistance data to the RNC for UE positioning▪ May also perform the position calculations for different postioning

methods

• 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 the

OSS▪ 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 RNC2600Physical Interfaces


NSN RNC2600 - Physical Interfaces

• STM-1 / OC-3• The NPS1 or NPS1P functional unit offers ATM over

SDH/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-3

optical interfaces• Gigabit Ethernet

• The NPGE or NPGEP functional unit offers IP over Ethernet 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

RNC2600/1278Capacity Step 1

RNAC sub racks 1 - 4Iub throughput:

1278Mbps (DL+UL)RNC2600/2840Capacity Step 3

RNAC sub racks 1 - 4RNBC sub racks 1 - 4

Iub throughput: 2840Mbps (DL+UL)







RNAC sub racks 1 - 4Iub throughput:

1540Mbps (DL+UL) RNC2600/3500Capacity Step 3








• 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 the

actual allowed capacity of the RNC2600• The software only defines the maximum RNC2600 capacity

from the hardware perspective


NSN RNC2600 (RU10) – Physical Interface Capacity

14

10

6

NPS1, NPS1P

1638381428 or 14+14112 or 56 + 562000Step 31228261224 or 12+1280 or 40 + 401450Step 2

81814816 or 8+848 or 24 + 24900Step 1

MXUDMCUICSUNPGE, NPGEP

GE Ethernet

STM-1Iub Mbit/s

Number of functional units

Number of interface units

Number of interfacesIub DL traffic capacity (estimate)

Config. steps

Capacity steps for RNC2600 at RN4.0 level


NSN RNC2600 (RU20) – Physical Interface Capacity

14

10

6

NPS1, NPS1P

1638381632 or 16+16112 or 56 + 563500Step 31228261224 or 12+1280 or 40 + 402520Step 2

81814816 or 8+848 or 24 + 241540Step 1

MXUDMCUICSUNPGE, NPGEP

GE Ethernet

STM-1Iub Mbit/s

Number of functional units

Number of interface units

Number of interfacesIub DL traffic capacity (estimate)

Config. steps

Capacity steps for RNC2600 at RN5.0 level


Nokia Siemens Networks RNC2600Capacity Licensing


NSN RNC2600 - Capacity licensing• The RNC2600 capacity licensing allows for capacity

configurations based upon the actual RNC2600 traffic– This allows for cost efficient usage of the RNC2600 resources in

different 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 the

RNC2600– The corresponding license file will be delivered with the RNC2600

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

– NetAct– Local Element Manager


RNC2600 with SW Configurable Capacity Licensing – RU20• RNC2600 enables capacity licensing • RNC Capacity can be freely

configured 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+UL0….23800 Erl0….1440 Cells

capacity step 20….2520 Mbps DL+UL0….47600 Erl0….2100 Cells

capacity step 3

0….3500 Mbps DL+UL0….70000 Erl0….2800 Cells

Pay

as y

ou g

row


RNC2600Redundancy


Reliability and scalability conceptsDuplication (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 allocating

resources defines to be spare• spare unit can replace any active unit in the group -> slower

switchover, requires warming (cold-standby) • users responsibility to change the working state of the unit to

reflect the resource allocation situation and to leave at least one spare 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 its

functionsNo redundancy

• no special requirements for reliability


NSN RNC2600 - Unit Redundancy

2N (MSP 1+1 / APS 1 + 1)NPGEP2N (MSP 1+1 / APS 1 + 1)NPS1PNoneNPGENoneNPS12NOMS HDD2NWDU2NTBU2NSFU2NRSMU2NOMUNoneOMS2NMXUN+1ICSUNoneEHUSN+DMCU

Redundancy PrincipleFunctional Unit

• 2N - Hot standby• N+1 - 1 or more spare units

designated to a group of functional units

• SN+ - No spare unit is allocated due to the units being part of a resource pool. Extra capacity is already built in to the pool


RNC architecture and load sharing

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

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

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

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

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

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

NSN RNCOne resource pool

Competitor ASeveral small resource poolsLoad sharing only possible among units in the same subrack


Questions???

Documents

RNC2600 Introduction