01_RN33151EN30GLA0_RNC Architecture and Interfaces

1 © Nokia Siemens Networks RN33151EN30GLA0

For public use – IPR applies

RNC Architecture and Interfaces



Nokia Siemens Networks Academy

Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks.



Objectives

After this training module, the student should be able to:

• Explain RNC architectures: cabinet, Plug In Unit (PIU) connection, cabling, Functional Units (FUs), redundancy types and Hardware Management System (HMS) of RNC196, RNC450 and RNC2600

• Explain RU20 RNC configuration and capacity steps for RNC196, RNC450 and RNC2600

• Understand new changes in RU20 (RN5.0) for RNC196, RNC450 and RNC2600

• Understand signalling and data flow in RU20 for RNC196, RN450 and RNC2600

• Explain changes in RU20 for hardware, software, alarms, MML, measurement



CN

BSS

UE

UTRAN

PS-Domain

CS-Domain

RNS

EI

R HS

S

VL

R

PDN/

Internet

VLR

PSTN

Um

Uu

Abis

A

A

IuCS

Gb Gs

F D C

PSTN

Gf Gc

Gn

Gp

Nc

Mc Mc

Nb

PSTN Nc E G

IuPS

Iur

USIM

IuCS

Gr

Gi

PSTN

PSTN

SIM

Cu

GERAN

BSC BTS

Node B

RNC SGSN

GGS

N

MG

W

MSS

MS

S

MGW

GMSS

Iub

IMS

Go

Other

PLMN

BG

UMTS Basic Network Architecture (Rel 7)



UTRAN

Iu-CS

Uu

User Equipment (UE)

Iur Iub

DRNC

WBTS

WBTS

WBTS

WBTS

SRNC

Core Network (CN)

3G-SGSN

3G- MSC

Iu-PS

CBC Iu-BC

SAS or

A-GPS Server

Iu-pc or

ADIF

UTRAN Interfaces



OMU

lower traffic capacity

higher traffic capacity

TDM E1/T1/JT1 1.5-2 Mbit/s

NIWU

FDU WDU

Generic Functional Architecture of IPA2800 ATM E1/T1/JT1

1.5-2 Mbit/s

NIP1

DMCU /TCU

MXU

MXU

TBU Ethernet

10/100 Mbit/s

ATM STM-1 155 Mbit/s

NIS1 NPS1

OMS

Interface Functions

Switching Functions

Control Functions

Signal Processing

System Functions

TDM STM-1 155 Mbit/s

IWS1E IWS1T

IPGO/GE NPGE

IPFE

Ethernet 1G (optical/

electric)

Ethernet 100M

ISU /ICSU

Signaling

RSMU /CACU

…

Resource mangement

A2SU

SFU

SWU



Generic Block Diagram of IPA2800

MXU

MXU

TBU OMU

WDU

E1/T1/JT1 ATM

STM-1/VC-4 STM-1/VC-3

ATM

Ethernet 100Base-TX

CU*

NIS1

NIP1

NIWU

MXU

OMS

A2SU

CU*

SPU*

FDU

E1/T1/JT1

TDM

IPFE

Ethernet 1G IPGO/GE

IWS1E/T STM-1 TDM

Ethernet 100M

STM-1/VC-4 STM-1/VC-3

ATM

NPS1

NPGE Ethernet 1G

SFU

SWU

Ethernet 100Base-TX

CU*

CU*



IPA2800 Conceptual Model

Application Software (RNC, MGW) Applications

Signal

Processing

Platform

SW Adjunct

Platform

(NEMU)

Switching

Platform

SW

Fault Tolerant

Computing Platform

Software

Modular and Scalable Hardware (Processing, switching and interface capacity required)

IPA2800

Platform

API API API API



Mechanics (M2000)

Cabinet mechanics for indoor use

Cabinet contains 4 subracks, 4 fan trays, and power distribution equipment

EMC shielding at subrack level rather than at cabinet level

Front and back cabling

Based on metric dimensioning (IEC/ETSI)

Old hardware mechanics (prior to A5):

IC186-B Indoor Cabinet, 1800*600*600 mm

SRA1 Subrack, ATM, type 1


FTRA Fan Tray

New hardware mechanics (A5HW):

EC216 Equipment Cabinet, 2100*600*600 mm


FTRA-B Fan Tray 1200W



Similarities and Differences of DX200 and IPA2800 (Optional)



Comparison of IPA2800 & DX200 Platforms

Similarities and Differences: Hardware Platform

All plug-in units are different in IPA2800 platform and DX 200 platform. However, plug-in units may contain common hardware blocks in some cases.

System internal communication: ATM vs. Message Bus and LAPD channels

Hardware Management System (HMS) replaces Wired Alarms, and provides new functionality.

Similarities and Differences: Computing Platform

Major improvements visible to application level will be: POSIX, I/O architecture, System Maintenance, Chorus Computing Platform

Similarities and Differences: Switching Platform

Switching based on ATM: a lot of ATM-specific additional functionality



DX 200 / IPA 2800 Platform

Both Platform support the common features:

• Distributed Processing Architecture

• Modularity

• Common Hardware

• Modular Software

• Fault Tolerance



IPA2800 Redundancy Principles



2N Redundancy

2N Redundancy (duplication)

• one spare unit designated for one active unit

• Software in the unit pair is kept synchronized

(hot-standby) -> fast switchover

Active

Hot stand-by

2N redundancy principle



Replaceable N+1 Redundancy

• Replacement (N+1) or (N+m)

• 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

Active

Active

Stand-by

N+1 redundancy principle



SN+ Redundancy (Load Sharing)

SN+ (Load Sharing)

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

Active

Active

Active

SN+ redundancy principle

Active

Active

Fail

Load

33%

33%

33%

Load

50%

50%

0%



Functional Unit Redundancy Principles

No redundancy

• no special requirements for reliability

No Redundancy is needed in cases where the redundancy of a unit would not

noticeably increase the overall availability performance of the unit type.

For example:

RNC: OMS

BSC: ET

The 2–Mbit/s exchange terminal (ET), where the probability of failure of the 2–

Mbit/s line is expected to be much greater than that of the exchange terminal

hardware.



Multiplex Section Protection (MSP 1+1)

Physical Layer Protection (MSP 1+1)



Exercise

1. List 2 Network Elements use IPA2800 Platform ____________________________________

2. Fill in redundancy type to match description

Redundancy Type Description

If a few units are disabled, the whole group can still perform its functions

Spare unit can replace any active unit in the group slower switchover

Software in the unit pair is kept synchronized Fast switchover



RNC Mechanical Design

RNC450 and RNC2600

CPD120A Cabinet (H=2100mm) RNC196

CPD80B Cabinet (H=1800mm)



Connector panels



Fan Tray (FTRA-B)

Forced cooling for subracks (max power dissipation per subrack 1,2kW)

FTRA-B is used with 2000mm cabinet

Fans are controlled and supervised by HMS via fan control and supervision HWB located in PD30

M0 M1

Control and alarm Interface (rear cable)

M2 M3

M4 M5

M6 M7

PD30 Plug-in unit

2 x –48vdc

2 x CAN



RNC196 and RNC450 Architecture

The network element consists of the following parts:

•Network interface functions

•Switching and multiplexing functions

•Control plane functions

•User plane functions O&M functions



RNC2600 Architecture

Some units from earlier releases areno longer exist, because

– The functionalities are embedded to other units, or

– The unit is no longer supported

The units are:

– GTPU, functionalities are embedded to NPS1(P) and/or NPGE(P)

– A2SU, functionalities are embedded to NPS1(P)

– RRMU, functionalities are distributed to ICSU and OMU/RSMU

– NIS1(P), replaced with NPS1(P)

– NIP1, no more PDH interface are supported



RNC Functional Units in RU20

SFU

MXU

HDD WDU

EHU

TBU

ICSU

DMCU

OMU

OMS

SWU

DMCU

ICSU

NIU - NIS1(P)*

A2SU*

GTPU* MXU

NIU - NIP1*

PDU

NIU - NPGE(P)

NIU - NPS1(P)

* Only unit in RNC196 / RNC450

RSMU

RRMU



New Plug-in Units in RNC2600

SF20H

MX1G6-A

CDSP-DH

NP8S1-B

NP2GE-B



Block Diagram and Plug-in Unit Variants for RNC2600

FU/Product PIU Variant

ICSU CCP18-A

RSMU CCP18-A

OMU CCP18-A

DMCU CDSP-DH

SFU SF20H

MXU MX1G6-A

SWU ESA24

WDU HDS-B 73G

OMS (integrated)

MCP18-B

TBUF TBUF

TSS3 TSS3

PDU PD30

NPS1 NP8S1-B

NPGE NP2GE-A

Standalone

or Integrated



Blank Slide for Note page



RNC2600 Functional Unit Removed from Non-exist units Non-exist units

• Some units from earlier releases are no longer exist, because

– The functionalities are embedded to other units, or

– The unit is no longer supported

• The units are:

– GTPU, functionalities are embedded to NPS1(P) and/or NPGE(P)

– A2SU, functionalities are embedded to NPS1(P)

– RRMU, functionalities are distributed to ICSU and OMU/RSMU

– NIS1(P), replaced with NPS1(P)

– NIP1, no more PDH interface are supported



Change in RU20 (RN5.0) for RNC196/RNC450 and RNC2600

• Change of RNC196 in RU20 (RN5.0)





Change of RNC196 in RU20 (RN5.0)




• Common Iub interface has been removed from RNC functionality

• Broadband interfaces has been updated

- Functional unit NPGE or NPGEP offers IP over Ethernet interfaces.

- NPGE or NPGEP is introduced with RAN1225: IP Interface Upgrade for RNC196 and RNC450

• Connectivity rule has been updated

- CBR AAL2 Path VCC: PCR

- UBR+ AAL2 Path VCC: max( 0.1 * PCR, MDCR )




• HSUPA and HSDPA peak rate information has been updated in CDSP-DH upgrade for HSDPA peak rate per user

The RNC196 HSPA capacity




• Table Capacity and reference call mix model has been updated

• NPS1/NPS1P interfaces has been added toRNC196 architecture

• RNC196 capacity step 8 information has been added toRNC 196 capacity

• New figure RNC configuration and plug-in locations in capacity step 8 has been added.



RNC196 Capacity Steps

RNC196, 8 steps

Capacity steps:

1.RNC196/48

2.RNC196/85

3.RNC196/122

4.RNC196/159

5.RNC196/196

6.RNC196/300 (RAS05.1)

7.RNC196/450 (RAS05.1)

8.RNC196/1000 (RU20)

• Step 6 is achieved by:

– Removing NIP1 and FDU.

– Replace HDS-A with HDS-B.

– Add more ICSU, GTPU, MXU and A2SU.

– Add more NIS1(P).

• Step 7 is achieved by upgrade computer units at step 6 to latest version.



RNC 196/1000M in RU20 (RN5.0)

The capacity of RNC196/450M is increased to 1000 Mbit/s (Iub) by removing some units and replacing them with other functional unit:

• SF10 is removed and replaced with SF10E.

• NIS1, A2SU are removed and replaced with NPS1.

• GTPU is removed and re-configured as ICSU.

• Eight more CDSP-DH units are configured.



RNC2600 Traffic Flow GTP termination in NIU

• NIU, NPGE(P) or NPS1(P), covers GTPU functionalities in RNC2600, that is termination of UDP/IP protocol in Iu-PS interface.

ATM

IP

GTP’ GTP

UDP

ATM

GTP’

ATM ATM

IP

GTP

UDP

3G-SGSNNPS1DMPG

SNAP

LLC

AAL5AAL5

SNAP

LLC

GTP appl.

AAL5AAL5

GE

IP

GTP’ GTP

UDP

ATM

GTP’

ATM GE

IP

GTP

UDP

3G-SGSNNPGEDMPG

GTP appl.

AAL5AAL5



RNC196 Capacity Figure

RNC196

196/48 196/85 196/122 196/159 196/196 196/300 196/ 450

196 /1000

Number of subscribers 59000 122000 181000 240000 300000 300000 360000 1000000

BHCA 52000 108000 160000 216000 272000 272000 320000 1000000

Erlangs 1300 2700 4000 5400 6800 6800 8000 20000

Iub throughput Mbit/s 48 85 122 159 196 300 450 1000

Number of carriers 384 576 768 960 1152 1152 1152 1800

Number of BTSs 170 256 340 420 512 512 512 600

AAL2UP connectivity Mbit/s (AL2S-D)

950 1450 1950 2400 2800 3594 3594 -

AAL2UP connectivity Mbit/s (NP8S1B)

- - - - - - - 5100

RRC connected mode users

20000 30000 40000 50000 60000 70000 100000 100000

HSDPA on IuPS Mbit/s 43 94 109 140 176 270 405 900

HSUPA on IuPS Mbit/s 13 23 32 42 53 81 122 270

Number of HSDPA carriers

384 576 768 960 1152 1152 1152 1800

Number of HSDPA BTSs 170 256 340 420 512 512 512 900

Note: Capacity and reference call mix model



RNC196 Interface Capacity

RNC196/

STM-1 / OC-3 E1 / T1 Gigabit Ethernet

Unprotected Protected Unprotected Unprotected Protected

48 24 16 + 16 64 8 4 + 4

85 24 16 + 16 96 10 5 + 5

122 24 16 + 16 128 12 6 + 6

156 24 16 + 16 160 14 7 + 7

196 24 16 + 16 192 16 8 + 8

300 24 24 + 24 16 16 8 + 8

450 24 24 + 24 16 16 8 + 8

1000 24 24 + 24 16 16 8 + 8







•Common Iub interface has been removed from RNC functionality

• Broadband interfaces has been updated

- Functional unit NPGE or NPGEP offers IP over Ethernet interfaces.

- NPGE or NPGEP is introduced with RAN1225: IP Interface Upgrade for RNC196 and RNC450

• Connectivity rule has been updated

- CBR AAL2 Path VCC: PCR

- UBR+ AAL2 Path VCC: max( 0.1 * PCR, MDCR )




• HSUPA and HSDPA peak rate information has been updated in CDSP-DH upgrade for HSDPA peak rate per user

The RNC450 HSPA capacity



RNC450 Configuration Steps

Configuration steps:

1.RNC450/150

2.RNC450/300

3.RNC450/450

• 3 basic capacity option

and 6 carrier-optimised option.

1

2

3



RNC450 Capacity Basic Option

RNC450/150 RNC450/300 RNC450/450

Number of subscriber 181000 284000 360000

BHCA 240000 375000 576000

Erlangs 4000 6250 8000

Iub throughput Mbps 150 300 450

Number of carriers 600 900 1152

Number of BTS 200 300 512

AAL2UP connectivity Mbit/s 1950 2800 3594

RRC connected mode users 35000 70000 100000

HSDPA on IuPS Mbps 135 270 405

HSUPA on IuPS Mbps 41 81 122

Number of HSDPA carries 600 900 1152

Number of HSDPA BTS 200 300 512

Note: Capacities with NSN traffic mix model



RNC450 Capacity Figure Carrier Optimised

RNC450/150

Carrier opt1

RNC450/150

Carrier opt2

RNC450/150

Carrier opt3

RNC450/150

Carrier opt4

RNC450/300

Carrier opt

RNC450/450

Carrier opt

Number of subscriber 181000 181000 181000 181000 309000 454000

Busy Hour Call Attempt 240000 240000 240000 240000 408000 720000

Erlangs 4000 4000 4000 4000 6800 10000

Iub throughput Mbps 135 105 80 50 180 250

Number of carriers 660 720 780 840 1200 1800

Number of BTS 220 240 260 280 400 600

AAL2UP connectivity Mbit/s

1950 1950 1950 1950 2800 3594

RRC connected mode users

35000 35000 35000 35000 75000 100000

HSDPA on IuPS Mbps 122 95 72 45 163 227

HSUPA on IuPS Mbps 36 28 21 13 49 67

Number of HSDPA carries

660 720 780 840 1200 1800

Number of HSDPA BTSs 220 240 260 280 400 600

Note: Capacities with NSN traffic mix model




RNC450

STM-1 / OC-3 E1 / T1 Gigabit Ethernet

Unprotected Protected Unprotected Unprotected Protected

150 16 8 + 8

or 12 + 12 (if no E1/T1)

16 8 4 + 4

300 24 16 + 16

or 20 + 20 (if no E1/T1)

16 12 6 + 6

450 24 24 + 24 16 16 8 + 8







• New standalone OMS in RNC2600 architecture

• Number of recommended BTSs has been updated to 1600 BTSs

• Values in BHCA calculation have been updated

BHCA = AMR (Erl) / MHT * 3600

MHT used in the formula is 90s according to NSN traffic profile

• Capacity related updates throughout RNC2600 capacity



RNC2600 Configuration Steps

Configuration steps:

1. RNC2600/step1

2. RNC2600/step2

3. RNC2600/step3

Capacity is licensed

• Iub PS data throughput (Mbit/s)

• AMR capacity (Erl)

• Number of carriers

1

2

3



RNC2600 Capacity

RNC2600 step 1 RNC2600 step 2 RNC2600 step 3

Number of subscribers 680 000 1 360 000 2 000 000

BHCA (CS) 680 000 1 360 000 2 000 000

CS Erlangs 17 000 34 000 50 000

CS Erlangs (including softhandover) 23 800 47 600 70 000

BHCA (PS) 800 000 1 400 000 2 000 000

DL Iub throughput Mbit/s 1 100 1 800 2 500

DL + UL Iub throughput Mbit/s 1540 2520 3500

Number of carriers 1 440 2 100 2 800

Number of BTSs 1 440 2 100 2 800

RRC connected mode subscribers 100 000 152 000 200 000

Iu-PS HSDPA net bit rate [Mbit/s] 990 1 980 2 250

Iu-PS HSUPA net bit rate [Mbit/s] 297 594 675

HSDPA carriers 1 440 2 100 2 800

HSDPA BTSs 1 440 2 100 2 800

Note: Capacities and reference call mix model



RNC2600 Traffic Flow DSP pool configuration

• RNC2600 use CDSP-DH only

– Two powerful DSPs on each DMPG

• CCH DSPs process CCH for cells

• non-CCH DSPs process R99 DCH and HSPA

DMCU

DMPG

PPC

DMPG

PPC

DMPG

PPC

DMPG

PPC

CCH non-

CCH

non-

CCH

non-

CCH

CCH non-

CCH

non-

CCH

non-

CCH



RNC2600 Traffic Flow AAL2 switching in NPS1(P)

NIS1(P) or

NIP1 A2SU DMPG A2SU

NPS1(P) DMPG 1CID

AAL2 VCC AAL2 VCC

AAL2 VCC NCID 1CID 1CID NCID

AAL2 VCC

NPS1(P) 1CID

NIS1(P)

Iub -

ATM

Iub -

ATM

Iu-CS/Iur

-ATM

Iu-CS/Iur

-ATM

Old NE

RNC2600




RNC2600

STM-1 / OC-3 Gigabit Ethernet

Unprotected Protected Unprotected Protected

Step 1 48 24 + 24 16 8 + 8

Step 2 80 40 + 40 24 12 + 12

Step 3 112 56 + 56 32 16 + 16



General Protocol Model

Application

Protocol

Data

Stream(s)

ALCAP(s)

Physical Layer

Signalling Bearer(s)

Control Plane User Plane Radio

Network

Layer

Signalling Bearer(s)

Data Bearer(s)

Transport

Network

Layer

Transport Network

User Plane

Transport Network

User Plane

Transport Network

Control Plane



WCDMA L1

RLC

MAC

FP

RNC WBTS UE MGW

Iub Iu Uu

RLC

MAC

PHY

ATM

AAL2

FP

WCDMA L1

CS application

PHY

ATM

AAL2

Iu-UP protocol

PHY

ATM

AAL2

CS application

Ethernet-Phy

Ethernet-MAC

IPv4

UDP

Ethernet-Phy

Ethernet-MAC

IPv4

UDP

RTP

Iu-UP protocol

PHY

ATM

AAL2

Ethernet-Phy

Ethernet-MAC

IPv4

UDP

Ethernet-Phy

Ethernet-MAC

IPv4

UDP

RTP

Protocols in the CS User Plane ATM-based option



WCDMA L1

RLC

MAC

FP

RNC WBTS UE 3G-SGSN

Iub Iu Uu

RLC

MAC

PHY

ATM

AAL2

FP

WCDMA L1

PS application

PHY

ATM

AAL5

PDCP PDCP

IP

GTP-U

UDP

IP

GTP-U

UDP

PHY

Link Layer

IP

GTP-U

UDP

Gn

IP

GGSN

PHY

IP

GTP-U

UDP

PHY

Link Layer

IP

Ethernet-Phy

Ethernet-MAC

IPv4

UDP

PHY

ATM

AAL2

Ethernet-Phy

Ethernet-MAC

IPv4

UDP

Ethernet -MAC

PHY

ATM

AAL5 Ethernet -MAC

Ethernet -Phy

Ethernet -Phy

Protocols in the PS User Plane

CN

IP-based option

ATM-based option



Protocols in the UE Control Plane

RNC WBTS UE CN

WCDMA L1

Iub Iu Uu

RLC

MAC

PHY

ATM

AAL2

FP

WCDMA L1

RLC

MAC

PHY

ATM

AAL5

SSCOP

RANAP

MTP3b

SCCP

PHY

ATM

AAL5

SSCF-NNI

RANAP

MTP3b

SCCP

SSCOP

NAS

NAS

M3UA

SSCF-NNI SCTP

IP

RRC RRC

Ethernet-Phy

Ethernet-MAC

IPv4

UDP

PHY

ATM

AAL2

FP

Ethernet-Phy

Ethernet-MAC

IPv4

UDP

PHY

ATM

AAL5

Ethernet -MAC

Ethernet -Phy

IP-based option

ATM-based option

M3UA

SCTP

IP

PHY

ATM

AAL5

Ethernet -MAC

Ethernet -Phy



PHY

ATM

AAL5

SSCOP

SSCF-UNI

NBAP

WBTS D-RNC

PHY

ATM

AAL5

SSCOP

SSCF-NNI

RNSAP

MTP3b

SCCP

S-RNC

Iub Iur

Ethernet-Phy

Ethernet

-MAC

IPv4

SCTP

PHY

ATM

AAL5

SSCOP

SSCF-UNI

NBAP

Ethernet

-Phy

Ethernet

-MAC

IPv4

SCTP M3UA

SCTP

IPv4

Ethernet

-Phy

Ethernet

-MAC

PHY

ATM

AAL5

SSCOP

SSCF-NNI

RNSAP

MTP3b

SCCP

M3UA

SCTP

IPv4

Ethernet

-Phy

Ethernet

-MAC

Protocols in the Iub and Iur Control Plane

IP-based option

ATM-based option



User Data and Signalling Flow in RNC



SFU

MXU

RSMU

HDD WDU

ICSU

DMCU

OMU

OMS

SWU

DMCU

ICSU

MXU

NIU - NPGE(P)

MXU

NIU - NPS1(P)

Permanent Signalling Links Traffic Flow

ATM

Iub/Iu/Iur

IP

Iub/Iu/Iur

Standalone or Integrated



SFU

MXU

RSMU

HDD WDU

ICSU

DMCU

OMU

OMS

SWU

DMCU

ICSU

MXU

NIU - NPGE(P)

MXU

NIU - NPS1(P)

Common Control Channel Traffic Flow

ATM Iub

IP Iub



SFU

MXU

RSMU

HDD WDU

ICSU

DMCU

OMU

OMS

SWU

DMCU

ICSU

MXU

NIU - NPGE(P)

MXU

NIU - NPS1(P)

Dedicated Control Channel Traffic Flow

ATM Iub

IP Iub



SFU

MXU

RSMU

HDD WDU

ICSU

DMCU

OMU

OMS

SWU

DMCU

ICSU

MXU

NIU - NPGE(P)

MXU

NIU - NPS1(P)

CS User Data Traffic Flow

ATM Iub

IP Iu-CS



SFU

MXU

RSMU

HDD WDU

ICSU

DMCU

OMU

OMS

SWU

DMCU

ICSU

MXU

NIU - NPGE(P)

MXU

NIU - NPS1(P)

PS User Data over DCH

ATM Iub

IP Iu-CS



SFU

MXU

RSMU

HDD WDU

ICSU

DMCU

OMU

OMS

SWU

DMCU

ICSU

MXU

NIU - NPGE(P)

MXU

NIU - NPS1(P)

PS User Data over FACH/RACH

ATM Iub

IP Iu-CS



SFU

MXU

RSMU

HDD WDU

ICSU

DMCU

OMU

OMS

SWU

DMCU

ICSU

MXU

NIU - NPGE(P)

MXU

NIU - NPS1(P)

HSPA User Data

ATM Iub

IP Iu-CS



Review of RNC Architecture and Interfaces

• UMTS Networks and NSN RNC Overview

• RNC2600

• RNC196 and RNC450

• RNC Protocol and Transport Options

• Traffic Flow Examples

• Review Questions



Review Questions

1. Describe the role of functional units: ▪ RSMU

▪ ICSU

▪ DMCU

▪ OMU

▪ MXU

▪ SFU

2. Explain the difference between NIS1 and NPS1.

3. List all the configuration steps of RNC2600 and the number of cabinets and subracks equipped with plug-in units.



WCDMA L1

RNC WBTS UE MGW Iub Iu Uu

MAC

PHY

ATM

FP

WCDMA L1

CS applicatio

n

PHY

ATM

PHY

ATM

AAL2

CS application

Ethernet-Phy

Ethernet-MAC

IPv4

Ethernet-Phy

Ethernet-MAC

IPv4

UDP

Iu-UP protocol

PHY

ATM

Ethernet-Phy

Ethernet-MAC

IPv4

UDP

Ethernet-Phy

Ethernet-MAC

IPv4

UDP

IP-based option

ATM-based option

Review Questions

4. Fill in the missing protocol names in CS domain.



Review Questions

5. Draw the flow of PS data over HSPA through the RNC. Assume that both IP-based Iub and Iu-PS are used.

SFU

MXU

RSMU

HDD WDU

ICSU

DMCU

OMU

OMS

SWU

DMCU

ICSU

MXU

NIU - NPGE(P)

MXU

NIU - NPS1(P)



RNC Functional Units

This is optional module

In case participant has not attend RNC Architecture e-learning or IPA2800 platform

following slides should be cover training



RNC Functional Units in RU20

SFU

MXU

HDD WDU

EHU

TBU

ICSU

DMCU

OMU

OMS

SWU

DMCU

ICSU

NIU - NIS1(P)*

A2SU*

GTPU* MXU

NIU - NIP1*

PDU

NIU - NPGE(P)

NIU - NPS1(P)

* Only unit in RNC196 / RNC450

RSMU

RRMU



RNC Units Redundancy Type 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



SFU: Switching Fabric Unit (1/2)

Functions:

• Serves as the main switch fabric of the exchange.

• Provides redundant, fully accessible and non-blocking connection at ATM level.

• Supports both point-to-point and point-to-multipoint connection topologies.

• Handles various ATM service categories.

Type: Switching Fabric

Redundancy: 2N

Plug-in unit: SF10, SF10E and SF20H

Interfaces: Network Interfaces

Low bit-rate network interface and control computer

(via MXU)

OMU from the unit computer of SFU via MXU



SFU: Switching Fabric Unit (2/2)

SF10 SF10E SF20H



MXU: Multiplexer Unit (1/2)

Functions:

• Enable connection of the low-to-medium bit-rate signal processing units and computer units, as well as low-bit-rate network interface units, to the ATM switch fabric

• Multiplexes/de-multiplexes traffic from tributary units to the ATM switching fabric vice versa.

• ATM layer functions such as header translation, UPC/NPC parameter control, OAM functions, traffic management.

Type : Multiplexer Unit

Redundancy : 2N

Plug-in unit : MX622-B, MX622-C, MX622-D, MX1G6, MX1G6-A



MXU: Multiplexer Unit (2/2)

MX622-B/C/D MX1G6-/A



A2SU: AAL Type 2 Switching Unit (1/2)

Functions:

• Performs minipacket switching of AAL2 CPS.

• Collects AAL2 layer statistics

This unit is no longer needed when network interface unit NIP1 and/or NIS1(P) are not used in RNC.

Type : Signal Processing Unit

Redundancy : SN+

Plug-in unit : AL2S-B/D



A2SU: AAL Type 2 Switching Unit (2/2)

AL2S-D AL2S-B



OMU: Operational and Management Unit (1/2)

Functions:

• Cellular management

– Handles all RNC's crucial upper-level system maintenance functions

– Serves as an interface between OMS and the other units of the network element

– Maintains radio network configuration and recovery

– Houses radio network database and ATM/IP configuration database

– Has dedicated storage devices

• Basic maintenance

– Hardware configuration management

– HMS supervision

– Centralised recovery functions

Type: Computer unit with a dedicated storage device unit as a sub-unit

Redundancy: 2N

Plug-in unit: CCP10, CCP18-A



OMU: Operational and Management Unit (2/2)

CCP18-A CCP 10



OMU's Storage Device

• New plug-in unit HDS-B, consist of two Hard Disk Drive (HDD): One for OMU and another for OMS

• 73 GB formatted storage capacity/disk

• Redundancy type : 2N

• External devices: USB memory stick, one for each OMU (for CCP18-A only)



Configuration and redundancy principle of OMU's storage devices

• The two mutually redundant WDUs are connected simultaneously to both OMUs by means of separate SCSI buses.

• SCSI connection is shown on the figure beside. (CCP18-A and HDS-B)



ICSU: Interface Control and Signalling Unit (1/2)

Functions:

• Handles signalling transaction and RRM functions:

– Signalling protocols to Iu, Iub, Iur and Iu-BC interfaces for

▪ NBAP, RNSAP, RANAP, SABP signalling

▪ ALCAP (Q.2630.1) signalling ,RRC signalling

– Termination of the UNI-SAAL, NNI-SAAL/MTP-3 and SCTP/M3UA signalling associations

– Monitoring and recovery of the signalling links

– Distributed RRM functions

▪ Admission control (AC), Handover control (HC)

▪ Load control (LC) , Packet scheduling (PS)

– Location calculations for location-based services

Type : Computer Unit with no sub units

Redundancy : N+1

Plug-in unit : CCP10, CCP18-A, CCP18-C



ICSU: Interface Control and Signalling Unit (2/2)

CCP18-A CCP18-C CCP10



Resource and Switch Management Unit (1/2)

Functions:

• Controls the switch fabrics in RNC

• Establishes connections for calls according to requests from the signalling computer units (ICSUs).

• Handles DSP resource management. – Allocation of the DSPs and associated computer resources to different tasks, such as

macrodiversity combining and data traffic functions.

– supervision and management of the DMCU units, including the necessary software upload procedures

– management of the ATM connections within DMCU

• ATM switching management functions: – Establishment of both internal and external connections via the SFU

– Management and control of the SFU, A2SU and MXU.

– Transmission resource management.

Type : Computer Unit

Redundancy : 2N




Resource and Switch Management Unit (2/2)




GTPU: GPRS Tunnelling Protocol Unit (1/2)

Function:

• Facilitates RNC connections towards the SGSN by performing those RNC-specific Iu user plane functions which are related to GTP protocols

– Routing based on GTP tunnel ID

– UDP/IP (User Datagram Protocol / Internet Protocol) protocols termination

– IP and GTP protocol processing

This unit is no longer needed if Iu-PS interface is implemented using new network interface unit, NPS1(P) or NPGE(P)

Type : Computer Unit with no sub unit

Redundancy : SN+




GTPU: GPRS Tunnelling Protocol Unit (2/2)




DMCU: Data and Macro-Diversity Combining Unit

Purpose:

• WCDMA L1 functions, including macro-diversity combining (MDC) and outer loop power control.

• RLC-U and RLC-C protocol processing

• MAC-C and MAC-D protocol processing

• PDCP (Packet Data Convergence Protocol) protocol processing

• GTP termination

• Encryption

• HSDPA with CDSP-C

Type : Signal processing unit with no sub unit

Redundancy : SN+

Plug-in unit : CDSP-C, CDSP-DH



DMCU: Data and Macro-Diversity Combining Unit

CDSP-C CDSP-DH



OMS: Operation & Maintenance Server Unit(1/2)

Purpose:

• RNC element management tasks and local user interface

• Provides interface toward higher-level network management function, such as OSS

• Provide graphic-based local interface

• Processing fault and performance management data

• Support for configuration management in RNC

• O&M functions which are not handled by other computer units of the RNC

• post-processing support for measurement and statistics

• peripheral device control

Type : Computer unit, with dedicated storage devices and the Ethernet Switch unit as sub-units

Redundancy : None

Plug-in unit : MCP18-B



OMS: Operation & Maintenance Server Unit (2/2)

MCP18-B



OMS’s Storage Device

• New plug-in unit HDS-B, consist of two Hard

Disk Drive (HDD): One for OMU and another for

OMS

• 73 GB formatted storage capacity/disk

• Redundancy type : 2N



Configuration and redundancy principles of OMS storage devices

• OMS has two redundant disk with RAID0 configuration

• SCSI connection is shown on the figure beside. (MCP18-B and HDS-B)



ESA: Ethernet Switch for ATM 24 Ports

• Provides physical LAN/Ethernet interfaces for connections between OMS and the other units of the network element.

• The ESA24 upgrade increases LAN switching capacity.

• Redundant ESA24 is needed for AGPS feature

Type: Sub unit to OMS

Redundancy: None/2N

Capacity/ Performance: 24 physical 10/100 Base-T Ethernet interfaces



Standalone OMS

• 1RU high server that is mountable to a standard 19 inch rack

• Concentrates operation and management traffic and performs operation and management activities towards the RNC and WCDMA Base Stations under control of NetAct

• Local management interface towards RNC network elements with basic centralised alarm and performance management capabilities

• Capable of handling capacity of RNC2600, 1 600 WCDMA BTSs and 4 800 cells

• Capable of handling different types of mass management operations under the control of NetAct



Standalone OMS

Benefit:

• State-of-the-art feature set

• High quality, proven software platform

• Scalable, efficient architecture

• Accurate status of the network

• Local operation interface

• Secure software platform

• Easy to place and install

OMS HW: HP ProLiant DL360 G6 1U rack-mount server

Redundancy: None



Standalone OMS Interfaces

• RNC OMS connects to RNC through Nokia Siemens Networks’ management interface EMT

• All fault management, performance management, configuration and software management transactions to/from RNC OMS are transferred over the EMT interface

• The NWI3 and EMT management interfaces used in Nokia Siemens Networks WCDMA systems provide sophisticated functional capabilities, reliability and efficiency



Network Interface Unit PDH (NIP1)

• Provides 16 physical electrical PDH (E1/T1/JT1) interface

• Execute physical and ATM layer functionalities

• Provides ATM header translation, OAM function and Traffic policing.

• Provides an optional reference clock for timing and synchronisation

• Support Inverse Multiplexing for ATM (IMA)

• Redundancy: None

• Plugin unit : NI16P1A



Concept of IMA

Tx direction: cells distributed across links in round robin sequence

Rx direction: cells recombined into single ATM stream

Physical Link #0

Single ATM Cell Stream from ATM Layer

IMA Virtual Link

IMA Group

PHY

PHY

PHY Physical Link #1

Physical Link #2

IMA Group

PHY

PHY

PHY

Original ATM Cell Stream to ATM Layer

• Low bit rate transmission lines can be combined into a group that seen as a single virtual link by ATM

• IMA sublayer is part of the physical layer.

• It is located between the traditional Transmission Convergence sublayer and the ATM layer.



Network Interface Unit SDH (NIS1/NIS1P)

• Provides STM-1/OC-3 external interface

• Execute physical and ATM layer functionalities

• Provides ATM header translation, OAM function and Traffic policing.

• Provides an optional reference clock for timing and synchronisation, handles bit timing, line coding, and timing recovery

• Support MSP1+1

• Redundancy: None/2N

• Plugin unit : NI4S1-B



Network Interface Unit NPS1(P) • Functions:

– Provides 8 SDH STM-1/STM-4 interfaces and an RJ45 connector, and handles multiprotocol packet processing at wire speed and network connectivity

– Maps ATM cells to/from transmission frame structure of SDH/Sonet.

– Performs AAL2 minipacket switching.

– Translates ATM header.

– Performs UPC/NPC, traffic management, performance management and performance data collection.

– Provides optional reference clock for timing and synchronisation.

• It supports MSP1+1 / APS1+1 for SDH/Sonet

• Redundancy type: NONE or 2N

• Plugin unit type

– NP8S1, NP8S1-A, NP8S1-B (two slots wide)



Network Interface Unit NPGE(P)

• Functions:

– Provides Ethernet interfaces and handles multiprotocol packet processing at wire speed.

– Two 1000Base-LX/T (optical or electrical) Gigabit Ethernet interfaces and two 10/100 Base-T (electrical) Fast Ethernet interfaces

– Maps IP packet to/from transmission frame structure of Ethernet.

– Translates IP header.

– Performs traffic management, performance management and performance data collection.

– Terminates GTP protocol when used at Iu-PS.

• Redundancy type: NONE or 2N

• Plugin unit type

– NP2GE, NP2GE-A, NP2GE-B



Power Distribution System (1/2)

Functions:

• Distributes the -48 V/-60 V power from the rectifiers or batteries to the equipment inside the RNC cabinets

• Consists of:

– Cabinet Power Distributor

– Subrack Power Distributor

• Subrack power distributor controls the cooling equipment of its own subrack on the basis of messages sent by the OMU

Redundancy : 2N

Units : CPD80/120-A

PD20/30



Power Distribution System (2/2)

PD20/30



Power distribution principle and redundancy

To ensure 2N redundancy for the power distribution lines, the RNC cabinets are provided with two independent feeding input branches

Each CPD120-A unit contains:

• Connectors for one of the two mutually redundant supply lines from the batteries/rectifiers. In this way the two independent input branches are kept separate until the subrack level.

• Connectors for four supply lines to the subracks. Each subrack is supplied by a line from both CPD120-As, giving 2N redundancy.

• Circuit breakers for the outgoing supply lines, each with 30-A rating



Fuse Connection

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

38

FB1

FB2

FB3

FB4

FA1

FA2

FA3

FA4

FA5 and FB5 to fan tray FTRx



Timing and Buffering Unit (1/2)

Functions:

• Responsible for the network element synchronization, timing signal distribution and message transfer functions in the hardware management system

• Receives an input timing signal from upper network level, adjusts its local oscillator to long time mean value and delivers this synchronised timing signal as system timing to all plug-in units.

• Operates in plesiochronous mode, if all synchronisation are lost

• Collect alarms from the PIUs in the same subrack and transfer them to HMS master (OMU)

• 3 synchronisation inputs from line interface card

• 8 synchronisation outputs support maximum 8-cabinet configuration

Redundancy: 2N

Plug-in unit: TSS3/A and TBUF



Timing and Buffering Unit (2/2)

TSS TBUF



Network Timing and Synchronisation

PRC MSC

RNC MGW

BS

MSC PRC

BS BS

PRC PRC

PRC

PRC

PRC = Primary Reference Clock



RNC Timing and Synchronisation

TSS3

NPS1(P) 2

NPS1(P) 3

NPS1(P) 4

CPSY-A

CPSY-B

TSS3 Timing

signal to PIU

Timing signal to

PIU

TBUF

TBUF

TBUF

TBUF

Timing Bus 1 Timing Bus 0

Timing Ref. 1

Timing Ref. 2

Timing Ref. 3

ext. Sync



Connection principle and redundancy for the timing and synchronisation distribution bus



External Hardware Unit

Functions:

• Receive external alarms and send as alarm message to OMU via HMS bus

• Drive the optional External Hardware Alarm panel (EXAU-A / EXAU), the cabinet integrated lamp, and possible other external equipment.

Redundancy: No

Plugin unit: EHAT

EXAU EHAT



RNC Units Summary

Functional Unit (redundancy)

Supported HW

OMU (2N) CCP18-A

WDU (2N) HDS-A or HDS-B, with WDW18, WDW36 or WDW73.

FDU (2N) MDS-A

OMS (No) MCP18-B (4GB memory)

HDD (2N) HDS-A or HDS-B, with WDW73 or WDW147

RSMU (2N) CCP10, CCP18-A, CCP18-C

ICSU (N+1) CCP10, CCP18-A, CCP18-C

DMCU (SN+) CDSP-C (int. D), CDSP-DH

GTPU (SN+) CCP10, CCP18-A, CCP18-C

A2SU (SN+) AL2S-D

NIU (No or 2N) NI16P1-A, NI4S1-B, NP8S1, NP8S1-A, NP8S1-B, NP2GE, NP2GE-A, NP2GE-B

SFU (2N) SF10, SF10E, SF20H

MXU (2N) MX622-B, MX622-C, MX622-D, MX1G6, MX1G6-A

SWU (No) ESA24

TBU (2N) TSS3, TBUF

EHU (No) EHAT

PDU (2N) CPD80, CPD120, PD20, PD30



Hardware Management System

• Lowest intelligent system

• Running on HMS bus, comprises 3 node types:

– Master Node, head of HMS

– Bridge Node, divide HMS network into subsystem, which physically each subrack.

– Slave Node, interface toward PIUs

• Function of HMS

– Collect equipment data from the equipped PIUs

– Transfer of system initialisation data

– Collect HW fault notification

– Control and supervise external or auxiliary equipments



Hardware Management System

HMMN = Hardware Management Master Node

HMSB = HMS Bridge

HMSS = HMS Slave



Change in RU20

Reference reading material:

Nokia Siemens NetworksWCDMA RAN, rel. RU20,operating documentation

DN70515054: Changes in RU20 DN70357656: Changes in configuration parameters for radio network, ATM transport plan, and IP transport plan



RU20: New MML Programs

Q9 DHCP Server Data Handling

Use this command group to maintain the data on DHCP server.These commands cover a wide range of maneuvers related to DHCP server: configure and interrogate DHCP server options, configure, modify and interrogate pool basic information, bind and unbind pool with unit and network interface,delete IP pool and interrogate pool binding relationship, add and delete IP address ranges, manage and interrogate DHCP client IP address status, manage DHCP server status,manage and interrogate DHCP server log.

UW Preload Handling

Use the command to start system preloading,cancel system preloading and interrogating system preloading information



RU20 : Modified MML Programs

LJ Bundle and Endpoint Handling

NE Signaling Network State Interrogation

Q8 IP Qos Configuration Handling

QM IP Interface Configuration Handling

QR TCP/IP Stack Data Handling

US Working State an Restart Handling

W7 Licence and Feature Handling

WP Signal Processing Service Handling

WS Software Package and Status Handling

YA EXCHANGE TERMINAL CONFIGURATION HANDLING

YB IMA Group Handling

YG BFD Supervision Handling

YW SDH TRANSMISSION PROTECTION HANDLING



Differences in the hardware implementation between RU10 (RN4.0) and RU20 (RN5.0)

New plug-in units

TSS3-A, Timing and Synchronization, SDH, Stratum 3,Variant A

New mechanics

Cable-supporting shelves have been changed from CS186-B to CS216-A in RNAC cabinet

RNC OMS hardware changes

Operation and Management Server (OMS) has been introduced as a standalone network element. HP Proliant DL360 Generation 6 hardware platform is used to support the standalone RNC OMS.



RU20 : RNC New Alarms



RU20 : RNC Changed Alarms



RU20 : RNC Changed Alarms



RU20 : RNC Alarm system configuration changes

RU20 : RNC Removed Alarms

• There are no removed alarms in RN5.0



RU20 : RNC OMS Changed Alarms



RU20 : RNC OMS New Alarms

RU20 : RNC OMS Removed Alarms

• There are no removed alarms

Documents

01_RN33151EN30GLA0_RNC Architecture and Interfaces