Upload
gaurav-varshney
View
229
Download
3
Embed Size (px)
Citation preview
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
1/127
RN33111EN20GLA0
RNC Architecture and Functionalities
1
1 Nokia Siemens Networks RN33111EN20GLA1
RU20 RNC Architectureand Interfaces
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
2/127
RN33111EN20GLA0
RNC Architecture and Functionalities
2
2 Nokia Siemens Networks RN33111EN20GLA1
Nokia Siemens NetworksAcademy
Legal notice
Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Siemens Networks trainingdocumentation, product documentation and slide presentation material, all of which are forthwithknown as Nokia Siemens Networks training material, are the exclusive property of NokiaSiemens Networks. Nokia Siemens Networks owns the rights to copying, modification,translation, adaptation or derivatives including any improvements or developments. NokiaSiemens Networks has the sole right to copy, distribute, amend, modify, develop, license,sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individualscan use the Nokia Siemens Networks training material for their own personal self-developmentonly, those same individuals cannot subsequently pass on that same Intellectual Property toothers without the prior written agreement of Nokia Siemens Networks. The Nokia SiemensNetworks training material cannot be used outside of an agreed Nokia Siemens Networkstraining session for development of groups without the prior written agreement of NokiaSiemens Networks.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
3/127
RN33111EN20GLA0
RNC Architecture and Functionalities
4
4 Nokia Siemens Networks RN33111EN20GLA1
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 andRNC2600
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
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
4/127
RN33111EN20GLA0
RNC Architecture and Functionalities
5
5 Nokia Siemens Networks RN33111EN20GLA1
CN
BSS
UE
UTRAN
PS-Domain
CS-Domain
RNS
EI
RHS
S
VL
R
PDN/
Internet
PDN/
Internet
VLR
PSTNPSTN
Um
Uu
Abis
A
A
IuCS
Gb Gs
F D C
PSTN
Gf Gc
Gn
Gp
Nc
Mc Mc
Nb
PSTNNc E G
IuPS
Iur
USIM
IuCS
Gr
Gi
PSTN
PSTN
SIM
Cu
GERAN
BSCBTS
Node B
RNC SGSN
GGSN
MG
W
MSS
MS
S
MGW
GMSS
Iub
IMSIMS
Go
Other
PLMN
Other
PLMN
BG
UMTS Basic Network Architecture (Rel 7)
The picture shows an overview of mobile network supporting both 2G and 3G. Thecore network (CN) is divided into Circuit Switched and Packet Switched domains.The 3G radio access network, or UTRAN (UMTS Terrestrial Radio Access Network),
consists of Node B's and RNC's. One RNC together with all Node B controlled formsan RNS (Radio Network Subsystem).
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
5/127
RN33111EN20GLA0
RNC Architecture and Functionalities
6
6 Nokia Siemens Networks RN33111EN20GLA1
UTRAN
Iu-CS
Uu
User Equipment(UE)
IurIub
DRNC
WBTS
WBTS
WBTS
WBTS
SRNC
Core Network(CN)
3G-SGSN
3G-MSC
Iu-PS
CBCIu-BC
SASor
A-GPSServer
Iu-pcor
ADIF
UTRAN Interfaces
Picture shows UTRAN interfaces. In addition to the MSC and SGSN, interfaces to optional corenetwork nodes are shown:
CBC (Cell Broadcast Centre) supports cell broadcast traffic to all mobiles within a service
area. SAS (Standalone SMLC, Standalone Serving Mobile Location Centre) or Assisted GPS (A-
GPS) server supports location services (LCS).
For location services the following methods are supported by RNC:
Cell Coverage Based with Geographical Coordinates
In the Cell Coverage Based positioning method, the location of the UE is estimated on the basisof its serving cell. Information about the serving cell is obtained, for example, by paging, locationarea update, cell update, URA update or routing area update.
Assisted GPS
Since RAS05.1 / RAS05.1 ED, in addition to Cell Coverage Based positioning, A-GPS (AssistedGPS) is supported. The objective of this method is to forward to the UE the GPS NavigationMessage in a specified Assistance Measurement Control message. Hence, the satelliteacquisition time can be significantly reduced and the availability of the positioning service can beenhanced to urban canyons and light indoor environments. Moreover, the A-GPS positioningaccuracy can be improved if rough location of the UE can be included in the AssistanceMeasurement Control message. Rough position of the UE can be estimated based on, e.g.,introduced Cell Coverage Based location technique.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
6/127
RN33111EN20GLA0
RNC Architecture and Functionalities
7
7 Nokia Siemens Networks RN33111EN20GLA1
OMU
lower trafficcapacity
higher trafficcapacity
TDM E1/T1/JT11.5-2 Mbit/s
NIWU
FDU WDU
Generic Functional Architecture of IPA2800ATM E1/T1/JT1
1.5-2 Mbit/s
NIP1
DMCU/TCU
MXU
MXU
TBUEthernet
10/100 Mbit/s
ATM STM-1155 Mbit/s
NIS1NPS1
OMS
Interface Functions
Switching Functions
Control Functions
Signal Processing
System Functions
TDM STM-1155 Mbit/s
IWS1EIWS1T
IPGO/GENPGE
IPFE
Ethernet1G (optical/
electric)
Ethernet100M
ISU/ICSU
Signaling
RSMU/CACU
Resourcemangement
A2SU
SFU
SWU
The general functional architecture of the IPA2800 Packet Platform based networkelements is shown above. At the high level network element consists of switching functions,interface functions, control functions, signal processing functions, and system functions(such as timing and power feed).
Functionality is distributed to a set of functional units capable of accomplishing a special
purpose. These are entities of hardware and software or only hardware.
Operation and Maintenance Unit (OMU) for performing centralized parts of systemmaintenance functions; peripherals such as Winchester Disk Drive (WDU) and Floppy DiskDrive (FDU) (i.e. magneto-optical disk in the ATM Platform) connected via SCSI interface;
Distributed Control Computers (signaling and resource management computers) whichconsist of common hardware and system software supplemented with function specificsoftware for control, protocol processing, management, and maintenance tasks;
Network Interface Units (NIU) for connecting the network element to various types oftransmission systems (e.g. E1 or STM-1); (Please note that actual names of functionalunits are different, e.g. NIS1 and NIP1 instead of NIU)
Network Interworking Units (NIWU, IWS1) for connecting the network element to non-ATMtransmission systems (e.g. TDM E1);
ATM Multiplexer (MXU) and ATM Switching Fabric Unit (SFU) for switching both circuit andpacket switched data channels, for connecting signalling channels, as well as for systeminternal communications;
AAL2 switching unit (A2SU) performs switching of AAL type 2 packets;
Timing and Hardware Management Bus Unit (TBU) for timing, synchronization and systemmaintenance purposes; and
Distributed Signal Processing units (DMCU/TCU) which provide support for e.g.transcoding, macro diversity combining, data compression, and ciphering.
Units are connected to the SFU either directly (in the case of units with high traffic capacity)or via the MXU (in the case of units with lower traffic capacity). The order of magnitude of
the interconnection capacity for both cases is shown in the figure.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
7/127
RN33111EN20GLA0
RNC Architecture and Functionalities
8
8 Nokia Siemens Networks RN33111EN20GLA1
Generic Block Diagram of IPA2800
MXU
MXU
TBUOMU
WDU
E1/T1/JT1ATM
STM-1/VC-4STM-1/VC-3
ATM
Ethernet100Base-TX
CU*
NIS1
NIP1
NIWU
MXU
OMS
A2SU
CU*
SPU*
FDU
E1/T1/JT1
TDM
IPFE
Ethernet1GIPGO/GE
IWS1E/TSTM-1TDM
Ethernet100M
STM-1/VC-4STM-1/VC-3
ATM
NPS1
NPGE Ethernet1G
SFU
SWU
Ethernet100Base-TX
CU*
CU*
More formal way to view the generic functional architecture is by the generic blockdiagram. Note that the naming of functional units is different in actual network elementsbased on the platform. Here more generic terms are used to describe the concepts (forexample, NIU, SPU and CU). Such generic terms are marked with an asterisk (*).
To achieve higher reliability, many functional units are redundant: there is a spare unitdesignated for one or more active units. There are several ways to manage these spareunits. All the centralized functions of the system are protected in order to guarantee highavailability of the system.
To guarantee high availability, the ATM Switching Fabric and ATM Multiplexer as corefunctions of the system are redundant. Power feed, hardware management bus, andtiming supply are also duplicated functions. Hot standby protected units and units thathave management or mass memory interfaces are always duplicated. Hard discs andbuses connecting them to control units are always duplicated.
Computing platform provides support for the redundancy. Hardware and software of thesystem are constantly supervised. When a defect is detected in an active functional unit,a spare unit is set active by an automatic recovery function. The number of spare unitsand the method of synchronization vary, but redundancy always operates on softwarelevel.
If the spare unit is designated for only one active unit the software in the unit pair is keptsynchronized so that taking the spare in use in fault situations (switchover) is very fast.This is called 2N redundancy principle or duplication.
For less strict reliability requirements, the spare unit may also be designated to a groupof functional units. The spare unit can replace any unit in the group. In this case theswitchover is a bit slower to execute, because the spare unit synchronization (warming)is performed as a part of the switchover procedure. This redundancy principle is calledreplaceable N+1.
A unit group may be allocated no spare unit at all, if the group acts as a resource pool.
The number of unit in the pool is selected so that there is some extra capacity available.If a few units of the pool are disabled because of faults, the rest of the group can stillperform its designated functions. This redundancy principle is called complementaryN+1 or load sharing.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
8/127
RN33111EN20GLA0
RNC Architecture and Functionalities
9
9 Nokia Siemens Networks RN33111EN20GLA1
IPA2800 Conceptual Model
Application Software (RNC, MGW)Application Software (RNC, MGW)Applications
Signal
Processing
Platform
SWAdjunct
Platform
(NEMU)
Adjunct
Platform
(NEMU)
Switching
Platform
SW
Fault Tolerant
Computing Platform
Software
Modular and Scalable Hardware(Processing, switching andinterface capacity required)
Modular and Scalable Hardware(Processing, switching andinterface capacity required)
IPA2800
Platform
APIAPI APIAPI
The IPA2800 Packet Platform consists of the Switching Platform Software, the FaultTolerant Computing Platform Software, Signal Processing Platform Software, and theHardware Platform. In addition, adjunct platforms can be used if needed in an application.
The Switching Platform Software provides common telecom functions (for example,statistics, routing, and address analysis) as well as generic packet switching/routingfunctionality common for several application areas (for example, connection control, trafficmanagement, ATM network operations and maintenance, and resource management).
The Fault Tolerant Computing Platform Software provides a distributed and fault tolerantcomputing environment for the upper platform levels and the applications. It is ideal for usein implementing flexible, efficient and fault tolerant computing systems. The ComputingPlatform Software includes basic computer services as well as system maintenanceservices, and provides DX Light and POSIX application interfaces.
The Computing Platform Software is based upon general purpose computer units with inter-processor communications implemented using ATM virtual connections. The number ofcomputer units can be scaled according to application and network element specific
processing capacity requirements.
The Hardware Platform based on standard mechanics provides cost-efficiency through theuse of modular, optimized and standardized solutions that are largely based oncommercially available chipsets.
The Signal Processing Platform Software provides generic services for all signal processingapplications. Digital signal processing (DSP) is needed in providing computation intensiveend-user services, such as speech transcoding, echo cancellation, or macrodiversitycombining.
The Adjunct Platform (NEMU) provides a generic platform for O&M application services anddifferent NE management applications and tools.
Concept platform and it's layer structure should in this context be seen as a modular set ofclosely related building blocks which provide well defined services. Structure must not beseen as static and monolithic, as the subset of services needed for an application (specificnetwork element) can be selected.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
9/127
RN33111EN20GLA0
RNC Architecture and Functionalities
10
10 Nokia Siemens Networks RN33111EN20GLA1
Mechanics (M2000)
Cabinet mechanics for indoor use
Cabinet contains 4 subracks, 4 fan trays,and power distribution equipment
EMC shielding at subrack level ratherthan 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*600mm
SRA1 Subrack, ATM, type 1
SRA2 Subrack, ATM, type 2
FTRA Fan Tray
New hardware mechanics (A5HW):EC216 Equipment Cabinet, 2100*600*600 mm
SRA3 Subrack, ATM, type 3
FTRA-B Fan Tray 1200W
The IPA2800 platform introduces a new mechanics concept, with new cabinet, newsubrack (EMC shielded), and new plug-in unit dimensions. Fan units are neededinside the cabinet for forced cooling.
The M2000 mechanics comprises the basic mechanics concept based on ETSI 300119-4 standard and IEC 917 series standards for metric dimensioning of electronicequipment.
The concept supports the platform architecture which allows modular scalability ofconfigurations varying from modest to very large capacity. It also allows theperformance to be configured using only few hardware component types.
The mechanics consists of following equipment:
cabinet mechanics
19-slot subrack, it's backplane and front plate mechanics
connector and cabling system
cooling equipment.
Dimensions of the cabinet are: width 600 mm, depth 600 mm, and height 1800/2100mm (based on standard ETS 300 119-2 and IEC 917-2).
Subrack has a height of 300 mm, a depth of 300 mm, and a width of 500 mm. Thenominal plug-in unit slot in the subrack is 25 mm which results in 19 slots per onesubrack. The basic construction allows dividing a part of a subrack vertically into twoslots with optional guiding mechanics for the use of half-height plug-in units.
The backplane and cabling system provides reliable interconnections between plug-in units. In addition to this, the backplane provides EMC shield to the rear side of thesubrack. Common signals are delivered via the backplane and all otherinterconnection signals are connected via cabling. This allows backplane modularityand flexibility in different configurations. Because of flexible cabling and redundancyit is possible to scale the system to a larger capacity in an active system withoutshutting down the whole system.
Cabinet power distribution equipment and four subracks with cooling equipment canbe installed in one cabinet. Openings in the sides of the cabinet behind the subrackbackplanes allow direct horizontal cabling between cabinets.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
10/127
RN33111EN20GLA0
RNC Architecture and Functionalities
11
11 Nokia Siemens Networks RN33111EN20GLA1
Similarities and Differencesof DX200 and IPA2800(Optional)
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
11/127
RN33111EN20GLA0
RNC Architecture and Functionalities
12
12 Nokia Siemens Networks RN33111EN20GLA1
Comparison of IPA2800 & DX200Platforms
Similarities and Differences: Hardware PlatformAll plug-in units are different in IPA2800 platform and DX 200 platform.However, plug-in units may contain common hardware blocks in somecases.
System internal communication:ATM vs. Message Bus and LAPDchannels
Hardware Management System (HMS) replaces Wired Alarms, andprovides new functionality.
Similarities and Differences: Computing Platform
Major improvements visible to application level will be: POSIX, I/Oarchitecture, System Maintenance, Chorus Computing Platform
Similarities and Differences: Switching Platform
Switching based on ATM: a lot of ATM-specific additional functionality
Similarities and Differences: Hardware
Basic switching technology different: TDM versus ATM
A variety of new interface types, also network interworking is supported.
New mechanics concept and new dimensioning, but common technical solutions inM98 and M2000 mechanics when possible.
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 replaces wired alarms, and provides newfunctionality
Increased functional integration
Compact network elements
Forced cooling with fans
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
12/127
RN33111EN20GLA0
RNC Architecture and Functionalities
13
13 Nokia Siemens Networks RN33111EN20GLA1
DX 200 / IPA 2800 Platform
Both Platform support the common features:
Distributed Processing Architecture
Modularity
Common Hardware
Modular Software
Fault Tolerance
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
13/127
RN33111EN20GLA0
RNC Architecture and Functionalities
14
14 Nokia Siemens Networks RN33111EN20GLA1
IPA2800 Redundancy Principles
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
14/127
RN33111EN20GLA0
RNC Architecture and Functionalities
15
15 Nokia Siemens Networks RN33111EN20GLA1
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
2N Redundancy (duplication) is used when two units are dedicated to a task forwhich one is enough at any given time. One of the units is always active, that is inthe working state. The other unit is kept in the hot standby state, the spare state.
For example:
2N in RNC: OMU, SFU, MXU, RSMU
2N in BSC: OMU, GSW, MCMU
When a unit is detected faulty, it is taken into the testing state, and the fault locationand testing programs are activated. On the basis of the diagnosis, the unit is taken tothe separated state, if a fault is detected, or into use automatically, if no fault isdetected.
If the spare unit is designated for only one active unit, the software in the spare unit iskept synchronised so that taking it in use in fault situations (switchover) is very fast.The spare unit can be said to be in hot standby. This redundancy principle is calledduplication, abbreviated "2N".
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
15/127
RN33111EN20GLA0
RNC Architecture and Functionalities
16
16 Nokia Siemens Networks RN33111EN20GLA1
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, notallocating resources 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 leastone spare unit
Active
Active
Stand-by
N+1 redundancy principle
Replaceable N+1 / N+m Redundancy are used when there is just one or a few spareunits for a set of N units of a given type. The spare unit is not used by theapplications and is not permanently bound to one of the N active units, but can take
over the load of any one of them. When a commandinitiated changeover for areplaceable N+1 unit is performed, a pair is made up, the spare unit is warmed up tothe hot standby state, and changeover takes place without major interruptions.When a unit is detected faulty, it is automatically replaced without interruptions toother parts of the system.
For example:
N+1 in RNC: ICSU
N+1 in BSC: BCSU
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
16/127
RN33111EN20GLA0
RNC Architecture and Functionalities
17
17 Nokia Siemens Networks RN33111EN20GLA1
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 performits functions
Active
Active
Active
SN+ redundancy principle
Active
Active
Fail
Load
33%
33%
33%
Load
50%
50%
0%
Load sharing (SN+) or Complementary N+1 Redundancy
A unit group can be allocated no spare unit at all if the group acts as a resource pool.The number of units in the pool is selected so that there is a certain amount of extracapacity. If a few units of the pool are disabled because of faults, the whole groupcan still perform its designated functions. This redundancy principle is called loadsharing and abbreviated as 'SN+
For example:
SN+ in RNC: GTPU, A2SU, DMCU
SN+ in BSC: -
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
17/127
RN33111EN20GLA0
RNC Architecture and Functionalities
18
18 Nokia Siemens Networks RN33111EN20GLA1
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 2Mbit/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.
For example:
RNC: OMS
BSC: ET
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
18/127
RN33111EN20GLA0
RNC Architecture and Functionalities
19
19 Nokia Siemens Networks RN33111EN20GLA1
Multiplex Section Protection (MSP 1+1)
Physical Layer Protection (MSP 1+1)
MSP is the SDH name for the Multiplex Section Protection scheme , as defined inITU-T
recommendation G.783. In SONET, the equivalent term APS (Automatic Protection
Switching) is used instead. Throughout the rest of the document the term MSP is
used
for both SDH and SONET. In the basic MSP functionality, the service line is protected
using another line which is called the protection line : if an error occurs, for instance a
loss of signal (LOS), the protection mechanism switches over to the protection line.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
19/127
RN33111EN20GLA0
RNC Architecture and Functionalities
20
20 Nokia Siemens Networks RN33111EN20GLA1
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 stillperform its functions
Spare unit can replace any active unit in the group
slower switchoverSoftware in the unit pair is kept synchronizedFast switchover
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
20/127
RN33111EN20GLA0
RNC Architecture and Functionalities
21
21 Nokia Siemens Networks RN33111EN20GLA1
RNC Mechanical Design
RNC450 and RNC2600CPD120A Cabinet (H=2100mm)
RNC196CPD80B Cabinet (H=1800mm)
Subracks
The subrack mechanics consist of a subrack frame, backplane, and front plateforming electromagnetic shielding for electronics to fulfil EMC requirements.The basic construction allows dividing a part of a subrack vertically into two slots withoptional guiding mechanics for the use of half-height plug-in units.
Plug-in unit
The RNC is constructed by using a total of approximately 11 plug-in unit types. Thebasic mechanical elements of the plug-in units are PCB, connectors and front platemechanics. Front plate mechanics include insertion/extraction levers, fixing screwsand EMC gasket.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
21/127
RN33111EN20GLA0
RNC Architecture and Functionalities
22
22 Nokia Siemens Networks RN33111EN20GLA1
Connector panels
External PDH lines are connected to the RNC cabinet using a back interface plug-inunit which allows modular backplane connections. One back interface plug-in unitsupports one E1 plug-in unit. The back interface plug-in unit is installed in the same
row as the plug-in unit, but at the rear of the cabinet. There are two kinds ofconnector panels available:
connector panel with RJ45 connectors for balanced E1/T1 line connection to/from thecabinet
connector panel with SMB connectors for coaxial E1 line connection to/from thecabinet
External timing requires a specific connector panel. PANEL 1 in the RNAC cabinetprovides the physical interface connectors
Picture on top:
Cabling cabinet IC183 installed next to IC186. Notice the balanced cabling between
rear transition cards and cabling cabinet patch panels.Topmost patch panel in IC186 is CPSAL.
Picture on buttom:
BIE1C (SMB connectors) and BIE1T (RJ45 connectors) rear transition cardsinstalled to SRBI in rearside of cabinet.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
22/127
RN33111EN20GLA0
RNC Architecture and Functionalities
23
23 Nokia Siemens Networks RN33111EN20GLA1
Fan Tray (FTRA-B)
Forced cooling for subracks (max powerdissipation per subrack 1,2kW)
FTRA-B is used with 2000mm cabinet
Fans are controlled and supervised byHMS via fan control and supervision HWBlocated in PD30
M0 M1
Control and alarm
Interface (rear cable)
M2 M3
M4 M5
M6 M7
PD30Plug-in unit
2 x 48vdc
2 x CAN
Acoustic noise emitted by one IPA2800 fully equipped cabinet is 67 dBA (Powerlevel) 61 dBA (pressure level) in normal conditions (4 FTR1 fantarys containing 32fans). Acoustic noise increases by 3 dB per new cabinet. FTR1 meet the ETS 300-753 requirements.
Expected lifetime L10(time when 10% of fans failed) ~8years (@+40 degreeCelsius).
Fantray replacement is possible in live system. Without the fantray live system willoverheat approx. in 5 minutes.
Faulty FTRA fantary replacement procedure:
-Remove front cable conduit if present (move cables carefully away)
-Unscrew the fantay from mounting flanges
-Unplug the control cable first from subrack side and secondly from fantray side.
-Extract the faulty fantary from cabinet and insert the spare fantray unit
-Plug the control cable first in fanray and secondly to the subrack side-Screw the fantray to the cabinet flanges
-Install cable conduit and cables (if present)
-Faulty FTRA-A and FTRA-B replacement procedure:
-Remove fantray front grill and extract air filter
-Unplug the control cable from fantray side (rear side of cabinet)
-Open two thumb-screws behind the grill
-Lower and extract the fan assembly by openening the locking latches (drawerassembly and cable conduit is still mounted to cabinet)
-Insert spare fan assembly and secure latches and thumb-screws
-Plug the control cable
-Insert new air filter and close the fantray front grill.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
23/127
RN33111EN20GLA0
RNC Architecture and Functionalities
24
24 Nokia Siemens Networks RN33111EN20GLA1
RNC196 and RNC450 Architecture
The network element consists ofthe following parts:
Network interface functions
Switching and multiplexing functions
Control plane functions
User plane functions O&M functions
The functions are distributed to a set of functional units capable of accomplishing a specialpurpose. These are entities of hardware and software. The main functional units of the RNCare listed below:
The control computers (ICSU and RSMU) consist of common hardware and system softwaresupplemented with function-specific software.
The AAL2 switching units (A2SU) perform AAL2 switching.
The Data and Macro Diversity Unit (DMCU) performs RNC-related user and control plane L1and L2 functions.
The Operation and Maintenance Unit (OMU) performs basic system maintenance functions.
The O&M Server (OMS) is responsible for RNC element management tasks. The OMS hashard disk units for program code and data.
The Magneto-Optical Disk Drive (FDU) is used for loading software locally to the RNC.
The Winchester Disk Unit (WDU) serves as a non-volatile memory for program code and datafor the OMU.
The Timing and Hardware Management Bus Unit (TBU) takes care of timing, synchronisationand system maintenance functions.
The Network Interface Unit (NIU) STM-1/OC-3 (NIS1/NIS1P) provides STM-1 externalinterfaces and the means to execute physical layer and ATM layer functionality.
Network interface and processing unit 2x1000Base-T/LX provides Ethernet external interfacesand the means to execute physical layer and IP layer functionality.
The NIU PDH (NIP1) provides 2 Mbit/s / 1,5 Mbit/s (E1/T1) PDH external interfaces and themeans to execute physical layer and ATM layer functionality.
The GPRS Tunnelling Protocol Unit (GTPU) performs RNC-related Iu user plane functionstowards the SGSN.
The External Hardware Alarm Unit (EHU) receives external alarms and sends indications ofthem as messages to the OMU-located external alarm handler through HMS. Its secondfunction is to drive the Lamp Panel (EXAU), the cabinet-integrated lamp and other possibleexternal equipment.
The Multiplexer Unit (MXU) and the Switching Fabric Unit (SFU) are required for switching
both circuit- and packet-switched data channels, for connecting signalling channels and forthe system's internal communication.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
24/127
RN33111EN20GLA0
RNC Architecture and Functionalities
25
25 Nokia Siemens Networks RN33111EN20GLA1
RNC2600 Architecture
Some units from earlier releasesareno longer exist, because
The functionalities areembedded to other units, or
The unit is no longer supported
The units are:
GTPU, functionalities areembedded to NPS1(P) and/orNPGE(P)
A2SU, functionalities areembedded to NPS1(P)
RRMU, functionalities aredistributed to ICSU and
OMU/RSMU NIS1(P), replaced with NPS1(P)
NIP1, no more PDH interfaceare supported
The functions are distributed to a set of functional units capable of accomplishing a specialpurpose.
These are entities of hardware and software. The main functional units of the RNC are listedbelow.
The control computers (ICSU and RSMU) consist of common hardware and system softwaresupplemented with function-specific software.
The Data and Macro Diversity Unit (DMCU) performs RNC-related user and control plane L1and L2 functions.
The Operation and Maintenance Unit (OMU) performs basic system maintenance functions.
The Operation and Maintenance Server (OMS) is responsible for RNC element managementtasks.
The OMS has hard disk units for program code and data.
From RU20/RN5.0, standalone OMS is recommended for new RNC2600 deliveries.
Both standalone and integrated OMS are supported in RU20/RN5.0 release.
The Winchester Disk Unit (WDU) serves as a non-volatile memory for program code and data.The Timing and hardware management Bus Unit (TBU) takes care of timing, synchronisationand system maintenance functions.
The Network interface and processing unit 8xSTM-1/OC-3 (NPS1/NPS1P) provides STM-1external interfaces and the means to execute physical layer and ATM/AAL2 layer functionality.It also terminates the GTP protocol layer in Iu-ps interface.
Network interface and processing unit 2x1000Base-T/LX (NPGE/NPGEP) provides Ethernetexternal interfaces and the means to execute physical layer and IP layer functionality.
The External Hardware alarm Unit (EHU) receives external alarms and sends indications ofthem as messages to the OMU located external alarm handler via HMS. Its second function isto drive the lamp panel (EXAU), the cabinet-integrated lamp and possible other externalequipment.
The MultipleXer Unit (MXU) and the Switching Fabric Unit (SFU) are required for switching
both circuit and packet-switched data channels, for connecting signalling channels and for thesystem's internal communication.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
25/127
RN33111EN20GLA0
RNC Architecture and Functionalities
26
26 Nokia Siemens Networks RN33111EN20GLA1
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 inRNC196 / RNC450
RSMU
RRMU
Availability performance calculations describe the system from the availability pointof view presenting availability
Availability performance values are calculated for the complete system, that is,redundancy principles are taken into account
In reference to ITU-T Recommendation Q.541, intrinsic unavailability is theunavailability of an exchange (or part of it) due to exchange (or unit) failure itself,excluding the logistic delay time (for example, travel times, unavailability of spareunits, and so on) and planned outages
The results of the availability performance calculations for the complete systemare presented in the Predicted availability performance values.
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
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
26/127
RN33111EN20GLA0
RNC Architecture and Functionalities
27
27 Nokia Siemens Networks RN33111EN20GLA1
New Plug-in Units in RNC2600
SF20H
MX1G6-A
CDSP-DH
NP8S1-B
NP2GE-B
The main function of the SF20H plug-in unit is to switch cells from input to outputports. It has protocol-independent switching core of 80 Gbit/s, half of which isreserved for routing and framing overhead (link speed-up). There are 32 ports of 3.9Mcells/s ATM cell rate (corresponds to a user data rate of 1.65 Gbit/s).
The MX1G6-A is 1.6 Gbit/s ATM multiplexer plug-in unit. It multiplexes anddemultiplexes ATM cells and perform ATM layer and traffic management functions.This enables connecting low speed units to the switching fabric and improve the useof switching fabric port capacity by multiplexing traffic from up to twenty tributaryunits to a single fabric port.
The NP8S1-B provides multiprotocol packet processing at wire speed and networkconnectivity with eight optical synchronous digital hierarchy (SDH) STM-1 orsynchronous optical network (SONET) OC-3 interfaces. The high processing powerof the network processor and the unit computer enable the NP8S1-B plug-in unit toprocess protocol and data at the line interface unit (LIU) instead of the dedicatedprocessing units.
Similarly, the NP2GE-B provides multiprotocol packet processing at wire speed andalso offer the possibility of using both electrical (copper) and optical (fibre) basedEthernet. It has two 1000Base-LX/T (optical or electrical) Gigabit interfaces.interfaces in compliant with the IEEE802.3 specifications.
The configurable dynamic signal processing platform CDSP-DH plug-in unit functionas CDSP pool. Each CDSP-DH has 8 DSPs. The DSP cores are used in applicationsthat need digital signal processing including the outer loop power control and thePDCP, RLC, MAC, MDC, FP and RTP/RTCP (on IP-based Iu-CS) protocols.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
27/127
RN33111EN20GLA0
RNC Architecture and Functionalities
28
28 Nokia Siemens Networks RN33111EN20GLA1
Block Diagram and Plug-in Unit Variants forRNC2600
FU/Product PIU VariantICSU 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
Functional units (FU) and their functionalities:
ICSU (Interface Control and Signalling Unit)Ssignalling to other network elements and distributed radio resourcemanagement related tasks of the RNC.
RSMU (Resource and Switch Management Unit)
RNC's central resource management tasks such as connection control,internal ATM/IP resource scheduling, DSP related resource managementtasks, call connection related functions.
OMU (Operation and Maintenance Unit)
Maintaining the radio network configuration and recovery, basic system
maintenance functions, interface to the OMS unit.
DMCU (Data and Macro Diversity Combining Unit)
RNC-related user and control plane functions in Frame Protocol (FP), RadioLink Control (RLC), Medium Access Control (MAC)
SFU (Switching Fabric Unit)
ATM cell switching function supporting point-to-point and point-to-multipointconnection topologies, as well as differentiated handling of various ATMservice categories.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
28/127
RN33111EN20GLA0
RNC Architecture and Functionalities
29
MXU (Multiplexer Unit)
Multiplex traffic from tributary units to the ATM switching fabric, ATM layerprocessing functions such as policing, statistics, OAM, buffer management
and scheduling
SWU (Switching Unit) Ethernet switch
WDU (Winchester Disk Unit) system disk units for OMU
OMS (Operation and Maintenance Server) RNC element
TBU (Timing and Hardware Management Bus Unit)
synchronisation, timing signal distribution and message transfer in the
Hardware Management System of a network element. The TBU functionalunit consists of 2 different plug-in units:
TBUF (Timing Buffer)
Receive the system clock from the TSS3's, buffer and transmit to thebackplane, basic hardware management functions such as alarmsupervision and the configuration of the plug-in unit.
TSS3 (Timing and Synchronization, SDH, Stratum 3)
Snchronize and deliver the timing signals to TBUF units, basichardware management functions such as alarm supervision and the
configuration of the plug-in unit.
PDU (Power Distribution Unit)
Power distribution and control the cooling equipment of its own subrack
NIU (Network Interface Unit) can be either NPS1 or NPGE:
NPS1 (Network Processor Interface Unit STM-1)
8x STM-1/OC-3 external interfacesATM layer functions such asheader translation, AAL2 mini-packet switching, UPC/NPC
parameter control, OAM functions, traffic management, performancemonitoring, and performance data collection, and part of the GTPprotocol termination for IuPS
NPGE (Network Processor Interface Unit Gigabit Ethernet)2x1000Base-T/LX Gigabit Ethernet external interfaces, IP layerfunctions such as header translation, traffic management,performance monitoring, and performance data collection, and partof the GTP protocol termination for IuPS
EHU (External Hardware alarm Unit)
Rreceive external alarms, drive the external lamp panel (EXAU), the cabinet
integrated lamp, and any other external equipment
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
29/127
RN33111EN20GLA0
RNC Architecture and Functionalities
30
30 Nokia Siemens Networks RN33111EN20GLA1
RNC2600 Functional Unit Removed fromNon-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
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
30/127
RN33111EN20GLA0
RNC Architecture and Functionalities
31
31 Nokia Siemens Networks RN33111EN20GLA1
Change in RU20 (RN5.0)for RNC196/RNC450 and RNC2600
Change of RNC196 in RU20 (RN5.0)
Change of RNC450 in RU20 (RN5.0)
Change of RNC2600 in RU20 (RN5.0)
The RNC2600 has many improvements in RU20 which keep in line with currentnetwork challenges but also maintain CAPEX and OPEX at minimum and increasethe RNC data throughput.
Flexi Multiradio RF module introduces industry leading RF integration level and thesmallest power consumption combined with flexible GSM-WCDMA-LTE siteevolution.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
31/127
RN33111EN20GLA0
RNC Architecture and Functionalities
32
32 Nokia Siemens Networks RN33111EN20GLA1
Change of RNC196in RU20 (RN5.0)
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
32/127
RN33111EN20GLA0
RNC Architecture and Functionalities
33
33 Nokia Siemens Networks RN33111EN20GLA1
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 withRAN1225: 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 )
Broadband interfaces
STM-1
Functional units, NIS1 or NIS1P offer ATM over SDH network interface. NIS1 hasMSP 1+1 protection possibility within one plug-in unit and NIS1P between plug-in
units.Single plug-in unit type NI4S1-B is used by NIS1 and NIS1P. A plug-in unit containsfour SDH STM-1 (optical) interfaces.
OC-3
Functional units, NIS1 or NIS1P offer ATM network interface OC-3. APS 1+1protection can be used with OC-3 interfaces. Single plug-in unit type NI4S1-B is usedby NIS1 and NIS1P. A plug-in unit contains four OC-3 IR-1 (optical) interfaces.
Gigabit Ethernet (GE)
Functional unit NPGE or NPGEP offers IP over Ethernet interfaces. NPGE or
NPGEP is introduced with RAN1225: IP Interface Upgrade for RNC196 and RNC450.
For detailed information, see the feature description. NPGEP supports 2Nredundancy.
Single plug-in unit type NP2GE-B is utilised by NPGE and NPGEP functional units. Aplug-in unit contains two GE (optical or electrical) interfaces.
Connectivity
The AAL2UP connectivity corresponds to the sum of AAL2 path sizes in Iub, Iur, andIu-CS connections. The limiting factor for the AAL2UP connectivity in steps 1...5 isthe A2SU capacity. For steps 6 and 7, the limiting factor is the physical interfacecapacity, and the AAL2UP connectivity value is derived from the sum of STM-1
interface capacities. The AAL2UP connectivity is consumed as follows:CBR AAL2 Path VCC: PCR
UBR+ AAL2 Path VCC: max( 0.1 * PCR, MDCR )
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
33/127
RN33111EN20GLA0
RNC Architecture and Functionalities
34
34 Nokia Siemens Networks RN33111EN20GLA1
Change of RNC196 in RU20 (RN5.0)
HSUPA and HSDPA peak rate information has been updated in CDSP-DHupgrade for HSDPA peak rate per user
The RNC196 HSPA capacity
HSDPA traffic does not include soft handovers. HSUPA includes 40% soft handoveroverhead in Iub.
*) On top of GTP-U layer.
HSPA traffic uses shared channel where the peak rate throughput is shared by allusers in the same cell. When the number of user's transmitting data simultaneouslyincreases, the average throughput per user decreases.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
34/127
RN33111EN20GLA0
RNC Architecture and Functionalities
35
35 Nokia Siemens Networks RN33111EN20GLA1
Change of RNC196 in RU20 (RN5.0)
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 hasbeen added.
The actual number of subscribers in one RNC varies depending on how many of thesubscribers are in Soft Handover (SHO) state. The operator can affect this with radionetwork planning, as well as handover and power control parameters. The actualnumber of base stations controlled by one RNC varies depending on how the Iub isconfigured.
The RNC capacity and the number of BTSs has to be calculated together with RadioNetwork Planning. Transmission planning needs to be made according to match theanticipated traffic mixes used in RNW planning.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
35/127
RN33111EN20GLA0
RNC Architecture and Functionalities
36
36 Nokia Siemens Networks RN33111EN20GLA1
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 andA2SU.
Add more NIS1(P).
Step 7 is achieved by upgradecomputer units at step 6 to latestversion.
RNC196/48M
The smallest capacity step, RNC196/48M includes the first cabinet and the plug-in-units
NIS1 and NIS1P share same unit locations and are mutually exclusive. If redundancyis to be used, RNC196 can be configured to use NIS1 or NIS1P in case of STM1ATM transport, and to NPGE or NPGEP in case of IP transport.
RNC196/85M to 196M
In capacity steps 2 to 5, the capacity is expanded by taking additional subracks 1 to 4into use from the second cabinet.
RNC196/300M
The capacity of RNC196/196M is increased to 300Mbit/s (Iub) by removing some
units and replacing them with other functional units. NIP1 and FDU are removed. Optionally, one NIP1 can be left to the configuration.
The FDU or the magneto-optical disk drive functionality is replaced by an externalUSB memory stick supported with OMU. The external USB memory stick can beused for transferring data to or from the RNC. The OMU unit must be upgraded withanother hardware variant (CCP18-A) that supports the USB interface.
There are additional units for A2SU, ICSU, MXU, and GTPU.
The number of NIS1/NIS1P units can be increased.
The HDS-A plug-in-unit is replaced by another variant (HDS-B) that supports twohard disk units in one card.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
36/127
RN33111EN20GLA0
RNC Architecture and Functionalities
37
37 Nokia Siemens Networks RN33111EN20GLA1
RNC 196/1000M in RU20 (RN5.0)
The capacity of RNC196/450M is increased to 1000 Mbit/s (Iub) by removingsome 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.
The table below defines the minimum hardware requirements that must be fulfilled inthe RNC196/196M before upgrading to RNC196/300M. Separate unit upgradepackages are available if the requirements are not met.
RNC196/450M
The RNC196/450M includes the same number of units as the RNC196/300, but theminimum hardware requirements for the units are different. The following tabledefines the minimum hardware requirements for RNC196/450M. Separate unitupgrade packages are available if the requirements are not met.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
37/127
RN33111EN20GLA0
RNC Architecture and Functionalities
38
38 Nokia Siemens Networks RN33111EN20GLA1
RNC2600 Traffic FlowGTP termination in NIU
NIU, NPGE(P) or NPS1(P), covers GTPU functionalities inRNC2600, that is termination of UDP/IP protocol in Iu-PSinterface.
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
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
38/127
RN33111EN20GLA0
RNC Architecture and Functionalities
39
39 Nokia Siemens Networks RN33111EN20GLA1
RNC196 Capacity Figure
RNC196
196/48 196/85 196/122 196/159 196/196 196/300196/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 connectivityMbit/s (AL2S-D)
950 1450 1950 2400 2800 3594 3594 -
AAL2UP connectivityMbit/s (NP8S1B)
- - - - - - - 5100
RRC connected modeusers
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 270Number of HSDPAcarriers
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
In case RAN1754: HSPA optimized configuration is used, the maximum possibleR99 data capacity is 67% from the maximum throughput of the configuration definedin Table Capacity and reference call mix model.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
39/127
RN33111EN20GLA0
RNC Architecture and Functionalities
40
40 Nokia Siemens Networks RN33111EN20GLA1
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
Mixing STM-1/OC-3, E1/T1, and Gigabit Ethernet interfaces is possible, but thenumber of cards and interfaces are reduced due to limited number of available slotsin the subracks.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
40/127
RN33111EN20GLA0
RNC Architecture and Functionalities
41
41 Nokia Siemens Networks RN33111EN20GLA1
Change of RNC450in RU20 (RN5.0)
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
41/127
RN33111EN20GLA0
RNC Architecture and Functionalities
42
42 Nokia Siemens Networks RN33111EN20GLA1
Change of RNC450 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 withRAN1225: 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 )
Broadband interfaces
STM-1
Functional units, NIS1 or NIS1P offer ATM over SDH network interface. NIS1 hasMSP 1+1 protection possibility within one plug-in unit and NIS1P between plug-inunits.
Single plug-in unit type NI4S1-B is used by NIS1 and NIS1P. A plug-in unit containsfour SDH STM-1 (optical) interfaces.
OC-3
Functional units, NIS1 or NIS1P offer ATM network interface OC-3. APS 1+1protection can be used with OC-3 interfaces. Single plug-in unit type NI4S1-B is usedby NIS1 and NIS1P. A plug-in unit contains four OC-3 IR-1 (optical) interfaces.
Gigabit Ethernet (GE)
Functional unit NPGE or NPGEP offers IP over Ethernet interfaces. NPGE orNPGEP is introduced with RAN1225: IP Interface Upgrade for RNC196 andRNC450.
For detailed information, see the feature description. NPGEP supports 2Nredundancy.
Single plug-in unit type NP2GE-B is utilised by NPGE and NPGEP functional units. Aplug-in unit contains two GE (optical or electrical) interfaces.
Connectivity
The AAL2UP connectivity corresponds to the sum of AAL2 path sizes in Iub, Iur, andIu-CS connections. The limiting factor for the AAL2UP connectivity in steps 1...5 isthe A2SU capacity. For steps 6 and 7, the limiting factor is the physical interfacecapacity, and the AAL2UP connectivity value is derived from the sum of STM-1interface capacities. The AAL2UP connectivity is consumed as follows:
CBR AAL2 Path VCC: PCR
UBR+ AAL2 Path VCC: max( 0.1 * PCR, MDCR )
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
42/127
RN33111EN20GLA0
RNC Architecture and Functionalities
43
43 Nokia Siemens Networks RN33111EN20GLA1
Change of RNC450 in RU20 (RN5.0)
HSUPA and HSDPA peak rate information has been updated in CDSP-DHupgrade for HSDPA peak rate per user
The RNC450 HSPA capacity
*) 10M is for CDSP-C, 21 for CDSP-DH, CDSP-DH upgrade is an optional upgrade
HSDPA traffic does not include soft handovers. HSUPA includes 40% soft handoveroverhead in Iub.
1) On top of GTP-U layer.
HSPA traffic uses shared channel where the peak rate throughput is shared by allusers in the same cell. When the number of user's transmitting data simultaneouslyincreases, the average throughput per user decreases.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
43/127
RN33111EN20GLA0
RNC Architecture and Functionalities
44
44 Nokia Siemens Networks RN33111EN20GLA1
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/150
The smallest capacity step, RNC150 includes the first cabinet and the plug-in-units
RNC450/300
Expanded capacity to 300 Mbits/s, the RNC can be obtained by adding anothercabinet and the necessary plug-in units and connecting internal cabling between thecabinets.
RNC450/450
Expanded capacity to 450 Mbits/s, the RNC can be obtained by adding thenecessary plug-in units into two subracks.
Note: NIS1 and NIS1P share same unit locations and are mutually exclusive.
If redundancy is to be used, RNC196 can be configured to use NIS1 or NIS1P incase of STM1 ATM transport, and to NPGE or NPGEP in case of IP transport.
Reference: DN0628405 : RNC capacity extensions and upgrade
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
44/127
RN33111EN20GLA0
RNC Architecture and Functionalities
45
45 Nokia Siemens Networks RN33111EN20GLA1
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
The capacities of carrier-optimized configurations is given in RNC450 carrier-optimized configurations.
The actual number of the subscribers in one RNC varies depending on how many ofthe subscribers are in Soft Handover (SHO) state. You can affect this with radionetwork planning, as well as handover and power control parameters. The actualnumber of base stations controlled by one RNC varies depending on how the Iub isconfigured.
The RNC capacity and the number of BTSs should be calculated together with radionetwork planning. Transmission planning needs to be made accordingly to match theanticipated traffic mixes used in RNW planning.
HSPA capacity figures
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
45/127
RN33111EN20GLA0
RNC Architecture and Functionalities
46
46 Nokia Siemens Networks RN33111EN20GLA1
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 connectivityMbit/s
1950 1950 1950 1950 2800 3594
RRC connected modeusers
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 HSDPAcarries
660 720 780 840 1200 1800
Number of HSDPA BTSs 220 240 260 280 400 600
Note: Capacities with NSN traffic mix model
RNC450 carrier-optimized configurations
RNC450 supports the carrier connectivity optimization functionality that can be usedto increase the number of carriers by decreasing the Iub throughput at the sametime. Also the AMR capacity is increased in some of the carrier-optimizedconfigurations.
The carrier-optimized configuration is activated by altering the HSDPA configurationvalues. For detailed information, see Activating Basic HSDPA with QPSK and 5codes.
RAN1754: HSPA optimized configuration is not supported in carrier optimizedconfigurations.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
46/127
RN33111EN20GLA0
RNC Architecture and Functionalities
47
47 Nokia Siemens Networks RN33111EN20GLA1
RNC450 Interface Capacity
RNC450
STM-1 / OC-3 E1 / T1 Gigabit Ethernet
Unprotected Protected Unprotected Unprotected Protected
150 168 + 8
or 12 + 12(if no E1/T1)
16 8 4 + 4
300 2416 + 16
or 20 + 20(if no E1/T1)
16 12 6 + 6
450 24 24 + 24 16 16 8 + 8
Mixing STM-1/OC-3 and Gigabit Ethernet interfaces is possible, but the number ofcards and interfaces are reduced due to limited number of available slots in thesubracks.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
47/127
RN33111EN20GLA0
RNC Architecture and Functionalities
48
48 Nokia Siemens Networks RN33111EN20GLA1
Change of RNC2600in RU20 (RN5.0)
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
48/127
RN33111EN20GLA0
RNC Architecture and Functionalities
49
49 Nokia Siemens Networks RN33111EN20GLA1
Change of RNC2600 in RU20 (RN5.0)
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
Recommended up to 1600 BTSs
The actual number of subscribers in one RNC varies depending on how many of thesubscribers are in Soft Handover (SHO) state. The operator can affect this with radionetwork planning as well as handover and power control parameters. The actualnumber of base stations controlled by one RNC varies depending on how the Iub isconfigured.
The RNC capacity and the number of BTSs should be calculated together with RadioNetwork Planning. Transmission planning needs to be made accordingly to matchthe anticipated traffic mixes used in Radio Network (RNW) planning.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
49/127
RN33111EN20GLA0
RNC Architecture and Functionalities
50
50 Nokia Siemens Networks RN33111EN20GLA1
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
configuration step.
RNC2600/step 1The smallest configuration step RNC2600/step 1 includes the first cabinet and theplug- in-units.
Note that NPS1 and NPS1P / NPGE and NPGEP are mutually exclusive.
RNC2600/step 2
Configuration extension to RNC2600/step 2 can be obtained by adding the newcabinet, necessary plug-in units.
There are more reserved slots for NPGE(P) and NPS1 units than can be installed atthe same time - the combined maximum is 14.
RNC2600/step 3
Configuration extension to RNC2600/step 3 can be obtained by adding thenecessary plug-in units into two sub-racks
There is a restriction on a number of NPS1 and NPGE.
There is a total of 28 slots and 16 SFU ports available:
1 NPS1 occupies 2 slots and 1 SFU port
1 NPGE occupies 1 slot and 1 SFU port
As a result, you cannot exceed either of the available slots or SFU ports.
For PIU detail please check DN70474741 : RNC Capacity extension and upgrade
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
50/127
RN33111EN20GLA0
RNC Architecture and Functionalities
51
51 Nokia Siemens Networks RN33111EN20GLA1
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 675HSDPA carriers 1 440 2 100 2 800
HSDPA BTSs 1 440 2 100 2 800
Note: Capacities and reference call mix model
Recommended up to 1600 BTSs
Iub throughput is the traffic in downlink direction defined in FP level. Additionally,30% PS traffic in the uplink direction is supported. For Rel99, throughput iscalculated in the Iub interface and the Soft Handover (SHO) (40%) are included. ForHigh-Speed Uplink Packet Access (HSUPA), throughput is calculated in the Iu-PSinterface from the effective High-Speed Downlink Packet Access (HSDPA)throughput where the SHO is excluded. This means that in the case of HSUPA, if theSHO is added on top of the 30%, and the actual HSUPA throughput in the Iubincluding the SHO is more than 30% (= 30% * (1+ 40%)).
Maximum number of simultaneous HSDPA users in Cell_DCH state
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
51/127
RN33111EN20GLA0
RNC Architecture and Functionalities
52
52 Nokia Siemens Networks RN33111EN20GLA1
RNC2600 Traffic FlowDSP 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
CCHnon-
CCH
non-
CCH
non-
CCH
CCHnon-
CCH
non-
CCH
non-
CCH
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
52/127
RN33111EN20GLA0
RNC Architecture and Functionalities
53
53 Nokia Siemens Networks RN33111EN20GLA1
RNC2600 Traffic Flow AAL2 switching in NPS1(P)
NIS1(P)or
NIP1A2SU DMPG A2SU
NPS1(P) DMPG1CID
AAL2 VCCAAL2 VCC
AAL2 VCCNCID 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
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
53/127
RN33111EN20GLA0
RNC Architecture and Functionalities
54
54 Nokia Siemens Networks RN33111EN20GLA1
RNC2600 Interface Capacity
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
This table shows the maximum number of STM-1/OC-3 and Gigabit Ethernetinterfaces possible in the RNC. Both protected and non-protected numbers areshown. Note that mixing STM-1/OC-3 and Gigabit Ethernet interfaces is possible, but
the number of cards, and hence the number of interfaces are reduced due to limitednumber of available slots in the subracks.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
54/127
RN33111EN20GLA0
RNC Architecture and Functionalities
55
55 Nokia Siemens Networks RN33111EN20GLA1
General Protocol Model
Application
Protocol
Data
Stream(s)
ALCAP(s)
Physical Layer
SignallingBearer(s)
Control Plane User PlaneRadio
Network
Layer
SignallingBearer(s)
DataBearer(s)
Transport
Network
Layer
Transport Network
User Plane
Transport Network
User Plane
Transport Network
Control Plane
The picture shows general model for protocols in the UTRAN interfaces Iub, Iur, Iu-CS and Iu-PS. In each interface there are two options of transport technology: ATM,and IP over Ethernet. Additionally, an option to use IP over ATM is supported for
signalling in Iu-CS and Iu-PS.
Protocols can be divided into two layers:
Radio Network Layerprotocols handling UTRAN functionalities. Theprotocols used in an interface are the same regardless of the choice oftransport technology used: ATM or IP.
Transport Network Layer protocols handling the actual transmission ofdata or signalling over the interface. The detail of protocols is specific to aparticular transport technology used.
Protocols can be divided into three planes according to the type of information:
Control Plane for signalling purpose between network elements.
User Plane for user data.
Transport Network Control Plane this plane only exists when the ATMoption is used and user data is carried in AAL2. It is used to dynamicallyconfigure AAL2 channels for user plane traffic.
The control plane and the user plane, in turn, rely the transport network user planeinside the transport network layer as their bearers.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
55/127
RN33111EN20GLA0
RNC Architecture and Functionalities
56
56 Nokia Siemens Networks RN33111EN20GLA1
WCDMA
L1
RLC
MAC
FP
RNCWBTSUE MG W
Iub IuUu
RLC
MAC
PHY
ATM
AAL2
FP
WCDMA
L1
CSapplication
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-basedoption
The figure illustrates protocols used in carrying user plane circuit switched traffic. Both ATM andIP options are shown for Iub and Iu interfaces.
3GPP Release 5 introduces IP transport option as an alternative to ATM transport. Due to the
layered structure of the UMTS protocol architecture, the impact on the Radio Network Layer isminimal. However, there is a deep change in the architecture of the transport, in terms ofprotocols, functionality and network configuration.
Since RN4.0, IP based Iu-CS is an option to ATM based transport, and both can be supportedsimultaneously in RNC. For Iub, there are two features supported: IP based Iub and Dual Iub.Dual Iub feature is different from IP Based Iub in a sense that there are transport bearers overthe ATM and IP towards one BTS.
IP based Iu-CS is implemented by Real-time Transport Protocol (RTP) and RTP ControlProtocol (RTCP), which are carried on top of UDP (User Datagram Protocol) and IP. RTP/RTCPprotocol provides end-to-end delivery services for data with real-time characteristics, e.g.interactive audio. RTP/RTCP was developed by IETF to overcome the shortcomings of IPnetwork, such as packet loss, reordering and delay. RTP itself does not provide anymechanisms to ensure timely delivery or other Quality-of-Service (QoS) guarantees, but relies
on lower layer services to do that.
In Iub, the frame protocol (FP) user data is carried over UDP over IP on top of Ethernet.
Abbreviations
WCDMA Wideband Code Division Multiple Access
AAL2 ATM (Asynchronous Transport Mode) Adaptation Layer 2
RLC Radio Link Control MAC Medium Access Control
PHY Physical layer FP Frame Protocol
RTP Real-Time transport Protocol UDP User Datagram Protocol
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
56/127
RN33111EN20GLA0
RNC Architecture and Functionalities
57
57 Nokia Siemens Networks RN33111EN20GLA1
WCDMAL1
RLC
MAC
FP
RNCWBTSUE 3G-SGSN
Iub
Iu
Uu
RLC
MAC
PHY
ATM
AAL2
FP
WCDMA L1
PSapplication
PHY
ATM
AAL5
PDCP PDCP
IP
GTP-U
UDP
IP
GTP-U
UDP
PHY
LinkLayer
IP
GTP-U
UDP
Gn
IP
GGSN
PHY
IP
GTP-U
UDP
PHY
LinkLayer
IP
Ethernet-Phy
Ethernet-MAC
IPv4
UDP
PHY
ATM
AAL2
Ethernet-Phy
Ethernet-MAC
IPv4
UDP
Ethernet-MAC
PHY
ATM
AAL5Ethernet
-MAC
Ethernet-Phy
Ethernet-Phy
Protocols in the PS User Plane
CN
IP-basedoption
ATM-basedoption
The figure illustrates protocols used in carrying user plane packet switched traffic. Both ATM andIP options are shown for Iub and Iu interfaces.
The feature IP Based Iu-PS enables the use of cost-efficient IP-over-Ethernet transport at theIu-PS interface in accordance with the 3GPP release 5 and later specifications.
The RNC supports both Ethernet and ATM-based protocol stacks at the Iu-PS interface. In otherwords, the connection to a certain serving GPRS support node (SGSN) can be based on eitherEthernet or ATM transport.
For Iub, it is the same as CS user plane figure.
In the picture, Release 99 PS data is shown. For HSDPA and HSUPA, additional MAC layers inRNC, WBTS and UE exist.
Abbreviations
PDCP Packet Data Convergence Protocol
GTP-U GPRS (General Packet Radio System) Tunnelling Protocol for the user plane
UDP User Datagram Protocol
IP Internet Protocol
AAL5 ATM Adaptation Layer 5
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
57/127
RN33111EN20GLA0
RNC Architecture and Functionalities
58
58 Nokia Siemens Networks RN33111EN20GLA1
Protocols in the UE Control Plane
RNCWBTSUE CN
WCDMA L1
Iub IuUu
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-basedoption
ATM-basedoption
M3UA
SCTP
IP
PHY
ATM
AAL5
Ethernet-MAC
Ethernet-Phy
The figure illustrates protocols used in carrying signalling between UE and the network mobile.Signalling between UE and RNC is handled by RRC protocol while signalling between UE andCN is handled by various NAS protocols such as Connection Management (CM), SupplementaryService (SS), etc. Signalling between RNC and CN is handled by RANAP protocol.
IP-based control plane at the Iu-PS, Iu-CS, and Iur (to be shown in the next figure) supports theevolution of the mobile core network towards an all-IP network. This feature is introduced as anoption to the current ATM-based control plane transport architecture.
The message-oriented and reliable SCTP (Stream Control Transmission Protocol) is a newalternative to the unreliable UDP and the reliable but slow TCP protocol. SCTP is described inIETF RFC 3286.
M3UA (MTP3 User Adaptation) protocol supports transport of SCCP messages over IP usingthe services of SCTP. M3UA is described in IETF RFC 3286.
Abbreviations
NAS Non Access Stratum
RANAP Radio Access Network Application Protocol
RRC Radio Resource Control
SCCP Signalling Control Connection Part
MTP3b Message Transfer Part Layer 3 broadband
SSCF-NNI Service Specific Coordination Function Network-to-Network Interface
SSCOP Service Specific Connection Oriented Protocol
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
58/127
RN33111EN20GLA0
RNC Architecture and Functionalities
59
59 Nokia Siemens Networks RN33111EN20GLA1
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-basedoption
ATM-basedoption
The figure illustrates protocols used in the control plane of Iub and Iur protocol.
Abbreviations
RNSAP Radio Network Subsystem Application Part
NBAP NodeB Application Part
SCCF-UNI Service Specific Coordination Function User-to-Network Interface
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
59/127
RN33111EN20GLA0
RNC Architecture and Functionalities
60
60 Nokia Siemens Networks RN33111EN20GLA1
User Data and SignallingFlow in RNC
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
60/127
RN33111EN20GLA0
RNC Architecture and Functionalities
61
61 Nokia Siemens Networks RN33111EN20GLA1
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
ATMIub/Iu/Iur
IP
Iub/Iu/Iur
Standalone or Integrated
The picture shows traffic flow for permanent signalling links on different type of Iubinterface, ATM based and IP based.
Permanent signalling links external VCCs to/from ATM based Iub areoriginated/terminated in NPS1(P).
Permanent signalling links IP connections to/from IP based Iub areoriginated/terminated in NPGE(P).
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
61/127
RN33111EN20GLA0
RNC Architecture and Functionalities
62
62 Nokia Siemens Networks RN33111EN20GLA1
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
The picture shows traffic flow for common control channel on different type of Iubinterface, ATM based and IP based. RACH (Random Access Channel) and FACH(Forward Access Channel) are the transport channels used to carry common control
channel in uplink and downlink direction, respectively.
Common control channel external VCCs to/from ATM based Iub areoriginated/terminated in NPS1(P). AAL2 switching this type of traffic is also done inNPS1(P).
Common control channel IP connections to/from IP based Iub areoriginated/terminated in NPGE(P).
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
62/127
RN33111EN20GLA0
RNC Architecture and Functionalities
63
63 Nokia Siemens Networks RN33111EN20GLA1
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
The picture shows traffic flow for dedicated control channel on different type of Iubinterface, ATM based and IP based. It is carried by the transport channel DCH(Dedicated Channel).
Dedicated control channel external VCCs to/from ATM based Iub areoriginated/terminated in NPS1(P). AAL2 switching this type of traffic is also done inNPS1(P).
Dedicated control channel IP connections to/from IP based Iub areoriginated/terminated in NPGE(P).
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
63/127
RN33111EN20GLA0
RNC Architecture and Functionalities
64
64 Nokia Siemens Networks RN33111EN20GLA1
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
The picture shows CS user data flow involving ATM based Iub and IP based Iu-CS.DCH is used and AAL2 switching of traffic is done in NPS1(P).
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
64/127
RN33111EN20GLA0
RNC Architecture and Functionalities
65
65 Nokia Siemens Networks RN33111EN20GLA1
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
The picture shows PS user data flow involving ATM based Iub and IP based Iu-PS.DCH is used to carry user data. The GTP termination for Iu-PS connection isperformed in NPGE(P).
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
65/127
RN33111EN20GLA0
RNC Architecture and Functionalities
66
66 Nokia Siemens Networks RN33111EN20GLA1
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
The picture shows PS user data flow involving ATM based Iub and IP based Iu-PS.FACH and RACH are used to carry user data for uplink and downlink, respectively.The GTP termination for Iu-PS connection is performed in NPGE(P).
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
66/127
RN33111EN20GLA0
RNC Architecture and Functionalities
67
67 Nokia Siemens Networks RN33111EN20GLA1
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
The picture shows PS user data flow involving ATM based Iub and IP based Iu-PS.
HS-DSCH (high-speed downlink shared channel) and E-DCH (enhanced dedicatedchannel) are the transport channels used to carry traffic in downlink and uplink,respectively. The GTP termination for Iu-PS connection is performed in NPGE(P).
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
67/127
RN33111EN20GLA0
RNC Architecture and Functionalities
68
68 Nokia Siemens Networks RN33111EN20GLA1
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
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
68/127
RN33111EN20GLA0
RNC Architecture and Functionalities
69
69 Nokia Siemens Networks RN33111EN20GLA1
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 thenumber of cabinets and subracks equipped withplug-in units.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
69/127
RN33111EN20GLA0
RNC Architecture and Functionalities
70
70 Nokia Siemens Networks RN33111EN20GLA1
WCDMAL1
RNCWBTSUE MGWIub IuUu
MAC
PHY
ATM
FP
WCDMA L1
CSapplicatio
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-basedoption
ATM-basedoption
Review Questions
4. Fill in the missing protocol names in CS domain.
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
70/127
RN33111EN20GLA0
RNC Architecture and Functionalities
71
71 Nokia Siemens Networks RN33111EN20GLA1
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)
8/21/2019 01_RN33111EN20GLA1_RNC Architecture and Functionalities
71/127
RN33111EN20GLA0
RNC Architecture and Functionalities
72
72 Nokia Siemens Networks RN33111EN20GLA1
RNC Functional Units
This is optional module
In case participant has not attend RNC Architecture e-learning or IPA2800 plat