01 01 CT53331EN53GLA0 RNC Architecture and Functionalities

8/20/2019 01 01 CT53331EN53GLA0 RNC Architecture and Functionalities

1/71

RNC Architecture and Functionalities

1CT53331EN53GLA0


2/71


4CT53331EN53GLA0


3/71


5CT53331EN53GLA0


4/71


6CT53331EN53GLA0

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

IPA2800 Platform is used in RNC and MGW


5/71


7CT53331EN53GLA0

The general functional architecture of the IPA2800 Packet Platform based network elements isshown 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 powerfeed).

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 system maintenancefunctions; peripherals such as Winchester Disk Drive (WDU) and Floppy Disk Drive (FDU) (i.e.magneto-optical disk in the ATM Platform) connected via SCSI interface;

Distributed Control Computers (signaling and resource management computers) which consist ofcommon hardware and system software supplemented with function specific software for control,protocol processing, management, and maintenance tasks;

Network Interface Units (NIU) for connecting the network element to various types of transmissionsystems (e.g. E1 or STM-1); (Please note that actual names of functional units are different, e.g.NIS1 and NIP1 instead of NIU)

Network Interworking Units (NIWU, IWS1) for connecting the network element to non-ATM

transmission systems (e.g. TDM E1);

ATM Multiplexer (MXU) and ATM Switching Fabric Unit (SFU) for switching both circuit and packetswitched data channels, for connecting signaling channels, as well as for system internalcommunications;

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, macrodiversity combining, data compression, and ciphering.

Units are connected to the SFU either directly (in the case of units with high traffic capacity) or viathe MXU (in the case of units with lower traffic capacity). The order of magnitude of theinterconnection capacity for both cases is shown in the figure.


6/71


8CT53331EN53GLA0

More formal way to view the generic functional architecture is by the generic block diagram. Notethat the naming of functional units is different in actual network elements based on the platform.Here more generic terms are used to describe the concepts (for example, 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 unit designatedfor one or more active units. There are several ways to manage these spare units. All thecentralized functions of the system are protected in order to guarantee high availability of thesystem.

To guarantee high availability, the ATM Switching Fabric and ATM Multiplexer as core functionsof the system are redundant. Power feed, hardware management bus, and timing supply are alsoduplicated functions. Hot standby protected units and units that have management or massmemory interfaces are always duplicated. Hard discs and buses connecting them to control unitsare always duplicated.

Computing platform provides support for the redundancy. Hardware and software of the system

are constantly supervised. When a defect is detected in an active functional unit, a spare unit isset active by an automatic recovery function. The number of spare units and the method ofsynchronization vary, but redundancy always operates on software level.

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 iscalled 2N redundancy principle or duplication.

For less strict reliability requirements, the spare unit may also be designated to a group offunctional units. The spare unit can replace any unit in the group. In this case the switchover is abit slower to execute, because the spare unit synchronization (warming) is performed as a part ofthe switchover procedure. This redundancy principle is called replaceable N+1.

A unit group may be allocated no spare unit at all, if the group acts as a resource pool. Thenumber 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 still perform its designatedfunctions. This redundancy principle is called complementary N+1 or load sharing.


7/71


9CT53331EN53GLA0

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 specificprocessing 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/71


10CT53331EN53GLA0

The IPA2800 platform introduces a new mechanics concept, with new cabinet, newsub rack (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 sub rack is 25 mm which results in 19 slots per onesub rack. The basic construction allows dividing a part of a sub rack vertically intotwo slots 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 thesub rack. 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 sub racks with cooling equipment canbe installed in one cabinet. Openings in the sides of the cabinet behind the subrackbackplanes allow direct horizontal cabling between cabinets.


9/71


11CT53331EN53GLA0


10/71


12CT53331EN53GLA0

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 in

the working state. The other unit is kept in the hot stand –by 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 unitis kept synchronized so that taking it in use in fault situations (switchover) is veryfast. The spare unit can be said to be in hot standby. This redundancy principle iscalled duplication, abbreviated "2N".


11/71


13CT53331EN53GLA0

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 the

applications and is not permanently bound to one of the N active units, but can takeover the load of any one of them. When a command –initiated changeover for areplaceable N+1 unit is performed, a pair is made up, the spare unit is warmed up tothe hot stand –by 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


12/71


14CT53331EN53GLA0

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


13/71


15CT53331EN53GLA0

For example:

RNC: OMS

BSC: ET


14/71


16CT53331EN53GLA0

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 isused

for both SDH and SONET. In the basic MSP functionality, the service line isprotected

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.


15/71


17CT53331EN53GLA0


16/71


18CT53331EN53GLA0


17/71


19CT53331EN53GLA0

Sub racks

The sub rack mechanics consist of a sub rack frame, backplane, and front plate

forming electromagnetic shielding for electronics to fulfill 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.


18/71


20CT53331EN53GLA0

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 unit

supports one E1 plug-

in unit. The back interface plug-

in unit is installed in the samerow as the plug-in unit, but at the rear of the cabinet. There are two kinds of connectorpanels 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 betweenrear transition cards and cabling cabinet patch panels.

Topmost patch panel in IC186 is CPSAL.

Picture on bottom:

BIE1C (SMB connectors) and BIE1T (RJ45 connectors) rear transition cardsinstalled to SRBI in rear side of cabinet.


19/71


21CT53331EN53GLA0

Acoustic noise emitted by one IPA2800 fully equipped cabinet is 67 dBA (Power level) 61 dBA(pressure level) in normal conditions (4 FTR1 fan trays containing 32 fans). Acoustic noiseincreases by 3 dB per new cabinet. FTR1 meet the ETS 300-753 requirements.

Expected lifetime L10(time when 10% of fans failed) ~8years (@+40 degree Celsius).

Fan tray replacement is possible in live system. Without the fan tray live system will overheatapprox. in 5 minutes.

Faulty FTRA fan tray replacement procedure:

-Remove front cable conduit if present (move cables carefully away)

-Unscrew the fan tray from mounting flanges

-Unplug the control cable first from sub rack side and secondly from fan tray side.

-Extract the faulty fan tray from cabinet and insert the spare fan tray unit

-Plug the control cable first in fan tray and secondly to the sub rack side

-Screw the fan tray to the cabinet flanges

-Install cable conduit and cables (if present)

-Faulty FTRA-A and FTRA-B replacement procedure:

-Remove fan tray front grill and extract air filter

-Unplug the control cable from fan tray side (rear side of cabinet)

-Open two thumb-screws behind the grill

-Lower and extract the fan assembly by opening the locking latches (drawer assembly andcable 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 fan tray front grill.


20/71


22CT53331EN53GLA0

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, synchronizationand 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 Tunneling Protocol Unit (GTPU) performs RNC-related Iu user plane functionstowards the SGSN.

The External Hardware Alarm Unit (EHU) receives external alarms and sends indications of

them 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 switchingboth circuit- and packet-switched data channels, for connecting signaling channels and for thesystem's internal communication.


21/71


23CT53331EN53GLA0

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 listed

below.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, synchronizationand 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 of

them 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 switchingboth circuit and packet-switched data channels, for connecting signaling channels and for thesystem's internal communication.


22/71


24CT53331EN53GLA0


23/71


25CT53331EN53GLA0

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 STM1

ATM 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 sub racks 1 to4 into use from the second cabinet.

RNC196/300MThe capacity of RNC196/196M is increased to 300Mbit/s (Iub) by removing someunits 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.


24/71


26CT53331EN53GLA0

In case RAN1754: HSPA optimized configuration is used, the maximum possible R99data capacity is 67% from the maximum throughput of the configuration defined in

Table Capacity and reference call mix model.


25/71


27CT53331EN53GLA0

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 sub racks.

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


26/71


28CT53331EN53GLA0

RNC450 carrier-optimized configurations

RNC450 supports the carrier connectivity optimization functionality that can be used

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


27/71


29CT53331EN53GLA0

configuration step.

RNC2600 /step 1

The 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 at

the 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


28/71


30CT53331EN53GLA0

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 is calculatedin the Iub interface and the Soft Handover (SHO) (40%) are included. For High-SpeedUplink Packet Access (HSUPA), throughput is calculated in the Iu-PS interface fromthe effective High-Speed Downlink Packet Access (HSDPA) throughput where theSHO is excluded. This means that in the case of HSUPA, if the SHO is added on topof the 30%, and the actual HSUPA throughput in the Iub including the SHO is morethan 30% (= 30% * (1+ 40%)).

Maximum number of simultaneous HSDPA users in Cell_DCH state


29/71


31CT53331EN53GLA0

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


30/71


32CT53331EN53GLA0


31/71


33CT53331EN53GLA0

Duplication (2N)

If the spare unit is designated for only one active unit, the software in the spare unit

is kept synchronized so that taking it in use in fault situations (switchover ) is very fast.The spare unit can be said to be in hot stand -by. This redundancy principle is calledduplication, abbreviated "2N".

Replacement (N+1)

For less strict reliability requirements, one or more spare units may also bedesignated to a group of functional units. One spare unit can replace any unit in thegroup. In this case, the execution of the switchover is a bit slower, because of thespare unit synchronization (warming) is performed as a part of the switchoverprocedure. The spare unit is in cold stand-by. This redundancy principle is calledreplacement, abbreviated "N+1".

Load sharing (SN+)

A unit group may be allocated no spare unit at all, if the group acts as a resourcepool. The number of units in the pool is selected so that there is a certain amount ofextra capacity. If a few units of the pool are disabled because of faults, the wholegroup can still perform its designated functions. This redundancy principle is calledload sharing, abbreviated "SN+".

None

Some functional units have no redundancy at all. This is because a failure in themdoes not prevent the function or cause any drop in the capacity.


32/71


34CT53331EN53GLA0

Switching Fabric Unit (SFU)

The Switching Fabric Unit (SFU) provides a part of the ATM cell switching function.It provides redundancy, full accessibility and is non-blocking at ATM connection level(that is, if input and output capacity is available, the connection can be established).SFU supports point-to-point and point-to-multipoint connection topologies, as well asdifferentiated handling of various ATM service categories.

High capacity network interface units and multiplexer units are connected to the 2Nredundant SFU.


33/71


35CT53331EN53GLA0

SF10

The main function of the SF10 plug-in unit is to switch ATM cells from 16 input ports

to 16 output ports. The cell switching uses self-routing where the cell is forwarded byhardware to the target output port based on the given output port address. Thecorrect cell sequence at the output port is guaranteed. The switching fabric supportsspatial multicasting.

The total switching capacity of SF10 is 10 Gbit/s with 16x16 switching fabric portinterfaces capacity of each is 622 Mbit/s. Port interfaces are duplicated for redundantmultiplexer units and redundant network interface units. The active input is selectedinside the SF10

SF10E

The main function of the SF10E (C110899) plug-in unit is to switch cells from input tooutput ports. Within the SF10E switching is protocol independent, meaning thatbefore the cells are sent to the fabric they are encapsulated inside a special fabricframe. In the case of APC based legacy port cards, the cells are always ATM cells,but network processor based units (such as MX1G6) are able to process anyprotocol.

SF20H

The main function of the SF20H plug-in unit is to switch cells from input to outputports. Within the SF20H, switching is protocol independent. This means that beforethe cells are sent to the fabric, they are encapsulated inside a special fabric frame.

With a total of 32 ports, the SF20H provides a 2.5 Gbit/s serial switching fabricinterface (SFPIF2G5). Several SFPIF2G5 ports can be combined for higher capacityports


34/71


36CT53331EN53GLA0

Multiplexer Unit (MXU)

The Multiplexer Unit (MXU) multiplexes traffic from tributary units to the ATMswitching fabric. Therefore, it allows the efficient use of switching resources for lowbit rate network interface units and computer units with small to moderate bandwidthrequirements. The MXU also includes part of the ATM layer processing functions,such as policing, statistics, OAM, buffer management and scheduling.

Control computers, signal processing units, and low bit rate network interface unitsare connected to the switching fabric via the MXU, which is a 2N redundant unit. TheRNC has several pairs of MXUs, depending on the configured capacity. For moreinformation, see RNC2600 capacity.


35/71


37CT53331EN53GLA0

MX622

The ATM Multiplexer Plug-in Unit 622 Mbit/s MX622 multiplexes and demultiplexes

ATM cells and performs ATM Layer functions and Traffic Management functions.

MX1G6 and MX1G6-A

The MX1G6 and MX1G6-A are 1.6 Gbit/s ATM multiplexer plug-in units. Theymultiplex and demultiplex ATM cells and perform ATM layer and traffic managementfunctions. The MX1G6 and MX1G6-A enable connecting low speed units to theswitching fabric and improve the use of switching fabric port capacity by multiplexingtraffic from up to twenty tributary units to a single fabric port.


36/71


38CT53331EN53GLA0

A2SU

AAL2 Switching Unit (A2SU) performs switching of AAL Type 2 CPS packets

between external interfaces and signal processing units. A2SU operates in the load-sharing redundancy configuration (SN+).

The AAL Type 2 guarantees bandwidth-efficient transport of information with limitedtransfer delay in the RAN transmission network.

If Iub, Iu-CS, and Iur have been IP upgraded, A2SU units are not used.


37/71


39CT53331EN53GLA0

AL2S, AL2S-A, AL2S-B

The AAL2 Switching unit (AL2S, AL2S-A or AL2S-B plug-in unit) serves to

demultiplex AAL2 channel from AAL2-VC, maps the AAL2 payload to AAL5 or AAL0,terminates VC containing AAL2, AAL5 or AAL0 and performs traffic and performancemanagement and statistics collection for AAL2.

AL2S-D

The AAL2 Switching unit (AL2S-D plug-in unit) serves to demultiplex AAL2 channelfrom AAL2-VC, maps the AAL2 payload to AAL5 or AAL0, terminates VC containing

AAL2, AAL5 or AAL0 and performs traffic and performance management andstatistics collection for AAL2


38/71


40CT53331EN53GLA0

Operation and Maintenance Unit (OMU)

The RNC always includes a duplicated (2N) OMU to provide high availability and

minimized interruptions in usage (see ̈ Redundancy principles). Duplicated systemdisk units are connected to and controlled by the OMU. The system disk unitscontain the operative software and the fallback software of the RNC.

The cellular management functions of the OMU are responsible for maintaining theradio network configuration and recovery. The OMU monitors the status of thenetwork and blocks the faulty units if necessary. The OMU contains the radionetwork database, ATM/IP configuration database, RNC equipment database andalarm history database.

The OMU unit further contains basic system maintenance functions and serves as aninterface between the RNC and the OMS unit. In the event of a fault, the unitautomatically activates appropriate recovery and diagnostics procedures within theRNC. The unit has the following interfaces:

a duplicated SCSI interface that connects mass memory devices

an Ethernet interface; an auto-sensing 10 base-T/100 base-TX interface, which canbe used, for example, as a management interface of the network element

a service terminal interface which provides support for debugger terminals

a multiplexer interface that allows termination of ATM virtual connections to thecomputer unit, thus supporting both inter-processor communication and terminationof external connections in the network element (used, for example, for signaling ornetwork management purposes).

a duplicated hardware management system interface (see RNC hardwaremanagement and supervision)

a USB 1.1 port and drivers for loading software or making backups locally to theRNC


39/71


41CT53331EN53GLA0

CCP10

The Control Computer with 800 MHz Pentium III-M processor (CCP10) acts as the

central processing resource in the IPA2800 system computer units.

The CCP10 incorporates an Intel Mobile Pentium III-M Microprocessor with 133MHzSDRAM memory on DIMM modules.

CCP10 has ATM connections to other plug-in units. This is done by an interface to ATM multiplexer (MX622-B /-C).

CCP10 has an interface to the Hardware Management System (HMS) which isimplemented in CCP10 as two Hardware Management Nodes (HMN): the HMSMaster Node (HMSM) and HMS Slave Node (HMSS).

CCP10 has a 16 bit wide Ultra3 SCSI bus. It is possible to connect up to 16 devicesinto the SCSI bus (including CCP10). CCP10 has two SCSI interfaces because the

mass memory system is 2N redundant. Current Ultra2 SCSI is also supported.

The timing and synchronization of CCP10 is provided by Timing and Synchronizationplug-in unit (TSS3). TSS3 provides 19.44 MHz clock signal for real time clock andUX ASIC.

There are two V.24/V.28 based serial interfaces for service terminals to provide aninterface for controlling and monitoring CCP10.

CCP10 has two 10 Base-T /100 Base-TX /1000 Base-T Ethernet interfaces toconnect to LAN.

In addition to the interfaces described above CCP10 gets the - 48 V DC supply and

HMN’s power feed through back plane connectors. CCP10 is assembled into sub rack SRA1 and SRA2. There can be more than twoCCP10 units in the sub rack


40/71


42CT53331EN53GLA0

OMU has two dedicated hard disk units, which serve as a redundant storage for theentire system software, the event buffer for intermediate storing of alarms, and the

radio network configuration files.

Backup copies are made onto a USB memory stick that is connected to the CCP18- A front plate. Only memory sticks can be used.

FDU is the functional unit when using the USB memory stick. No separateconfiguration in the HW database is needed, because the USB memory stick is anexternal device. When removing the USB memory stick, set the state to blocked,because the system does not do it automatically.

In previous deliveries, the MDS-(A/B) magneto optical drive with a SCSI interface isused. FDU is the functional unit. No separate configuration is needed.


41/71


43CT53331EN53GLA0

The USB stick is an optional external device that is not automatically delivered. Theoperator can choose to use the USB memory stick for backup purposes in RN2.2

new deliveries. When USB memory stick is used (the functional unit is FDU), it isplugged in one CPU card. There is no direct connection to the other CPUs. Only theUSB memory stick that is connected to the active OMU can be used. For OMUswitchover, two USB memory sticks are needed: one for each OMU.

In previous deliveries, the MDS-A plug-in unit is used (the functional unit is FDU).When MDS-A is used, FDU connects to the SCSI 0 bus. It has been left withoutbackup since it is primarily used for facilitating temporary service operations.


42/71


44CT53331EN53GLA0

Interface Control and Signalling Unit (ICSU)

The Interface Control and Signalling Unit (ICSU) performs those RNC functions that

are highly dependent on the signaling to other network elements. The unit alsohandles distributed radio resource management related tasks of the RNC.

The unit is responsible for the following tasks:

• Layer 3 signaling protocols RANAP, NBAP, RNSAP, RRC, and SABP

• Transport network level signaling protocol ALCAP

• Handover control

• Admission control

• Load control

• Power control

• Packet scheduler control

• Location calculations for location based services

According to the N+1 redundancy principle (for more information, see Redundancyprinciples).there is one extra ICSU in addition to the number set by the dimensioningrules. The additional unit is used only if one of the active units fails.


43/71


45CT53331EN53GLA0

CCP18-A, CCP18-C

The Control Computer with Pentium M 745 processor (CCP18-A and CCP18-C) acts

as the central processing resource in the IPA2800 system computer units.

The CCP18-A/-C incorporate an Intel Pentium M 745 Microprocessor with DDR200SDRAM memory on board

The CCP18-A and CCP18-C have ATM connections to other plug-in units. This isdone by an interface to the ATM multiplexer (MXU).

The CCP18-A and CCP18-C have an interface to the Hardware ManagementSystem (HMS). CCP18-A has two Hardware Management Nodes (HMN): the HMSMaster Node (HMSM) and HMS Slave Node (HMSS-B). CCP18-C has only the HMSSlave Node (HMSS-B).

The CCP18-A has a 16 bit wide Ultra3 SCSI bus. It is possible to connect up to 16devices into the SCSI bus (including CCP18-A). The CCP18-A has two SCSIinterfaces because the mass memory system is 2N redundant. Current Ultra2 SCSIis also supported. CCP18-C does not have a SCSI bus.

The timing and synchronization of the CCP18-A and CCP18-C is provided by theTiming and Synchronization plug-in unit (TSS3). TSS3 provides 19.44 MHz clocksignal for real time clock and UX2 FPGA.

There are two V.24/V.28 based serial interfaces for service terminals to provide aninterface for controlling and monitoring the CCP18-A and the CCP18-C.

The CCP18-A and CCP18-C have two 10 Base-T /100 Base-TX /1000 Base-TEthernet interfaces to connect to LAN.

In addition to the interfaces described above, CCP18-A and CCP18-C get the - 48 VDC supply and HMN’s power feed through back plane connectors


44/71


46CT53331EN53GLA0

GTPU

The GTPU performs the RNC-related IU user plane functions towards the SGSN.

The unit is SN+ redundant.

The unit is responsible for the following tasks:

Iu-PS transport level IP protocol processing and termination

Gateway Tunnelling Protocol User Plane (GTP-U) protocol processing


45/71


47CT53331EN53GLA0

CCP18-A, CCP18-C

The Control Computer with Pentium M 745 processor (CCP18-A and CCP18-C) acts

as the central processing resource in the IPA2800 system computer units.

The CCP18-A/-C incorporate an Intel Pentium M 745 Microprocessor with DDR200SDRAM memory on board

The CCP18-A and CCP18-C have ATM connections to other plug-in units. This isdone by an interface to the ATM multiplexer (MXU).

The CCP18-A and CCP18-C have an interface to the Hardware ManagementSystem (HMS). CCP18-A has two Hardware Management Nodes (HMN): the HMSMaster Node (HMSM) and HMS Slave Node (HMSS-B). CCP18-C has only the HMSSlave Node (HMSS-B).

The CCP18-A has a 16 bit wide Ultra3 SCSI bus. It is possible to connect up to 16devices into the SCSI bus (including CCP18-A). The CCP18-A has two SCSIinterfaces because the mass memory system is 2N redundant. Current Ultra2 SCSIis also supported. CCP18-C does not have a SCSI bus.

The timing and synchronization of the CCP18-A and CCP18-C is provided by theTiming and Synchronization plug-in unit (TSS3). TSS3 provides 19.44 MHz clocksignal for real time clock and UX2 FPGA.

There are two V.24/V.28 based serial interfaces for service terminals to provide aninterface for controlling and monitoring the CCP18-A and the CCP18-C.

The CCP18-A and CCP18-C have two 10 Base-T /100 Base-TX /1000 Base-TEthernet interfaces to connect to LAN.

In addition to the interfaces described above, CCP18-A and CCP18-C


46/71


48CT53331EN53GLA0

Data and Macro Diversity Combining Unit (DMCU)

The Data and Macro Diversity Combining Unit (DMCU) performs RNC-related user

and control plane functions. Each of these units has several state-of-the-art digitalsignal processors (DSPs) and general purpose RISC processors. The signalprocessing tasks can be configured and altered dynamically for each DSP. The unitis SN+ redundant. The unit is responsible for the following tasks:

UE and L2 related protocols

Frame Protocol (FP)

Radio Link Control (RLC)

Medium Access Control (MAC)

The following functions are within protocols:

macro diversity combining and outer loop PC: FPciphering: FP and RLC/MAC

Packet Data Convergence Protocol (PDCP): header compression

High-Speed Packet Access (HSPA) processing: MAC-shared (MAC-SH) andEnhanced Dedicated Transport Channel (EDCH)


47/71


49CT53331EN53GLA0

CDSP, CDSP-B or CDSP-C

The Configurable Dynamic Signal Processing Platform (CDSP, CDSP-B or CDSP-C

plug-in unit) functions as a CDSP pool. Each CDSP (-B/-C) has 32 Digital SignalProcessors (DSPs) on four daughter boards, either type D5510 (CDSP), CIP (CDSP-B), or CIP-A (CDSP-B version 4 and CDSP-C). The daughter boards are used fortranscoding, echo cancelling and other applications which need digital signalprocessing. Four MPC 8260 processors control the DSPs.

CDSP-DT, CDSP-DH and CDSP-D

The configurable dynamic signal processing platform (CDSP-DT, CDSP-DH andCDSP-D plug-in units) function as CDSP pool. Each CDSP-D (C109045) plug-in unithas 16 multicore digital signal processors (DSP) and a total of 96 DSP cores. EachCDSP-DH (C110830) and CDSP-DT (C111195) has 8 DSPs. The DSP cores areused in transcoding and echo cancelling as well as other applications that needdigital signal processing. The DSPs are controlled by four MPC 8280 processors.

CDSP-D and CDSP-DT plug-in units are used in MGW and CDSP-DH in RNC.


48/71


50CT53331EN53GLA0

OMS

The Operation and Maintenance Server (OMS) is a computer unit which provides an

open and standard computing platform for applications which do not have strict real-time requirements. The OMS provides functions related to external O&M interfaces.For example:

Post-processing of fault management data

Post-processing of performance data

Software upgrade support

These functions include both generic interfacing to the data communication network(DCN) and application specific functions such as processing of fault andperformance management data, implementation of the network element userinterface and support for configuration management of the network element. This

way the OMS provides easy and flexible interfacing to the network element.The OMS is implemented with the Red Hat Enterprise Linux 4. It contains its owndisks devices, interfaces for keyboard, mouse and display for debugging purposes,and a LAN (10/100/1000Mbit Ethernet) interface. Communication between the OMS andthe rest of the network element uses Ethernet.

The basic services of the OMS are:

MMI interface implemented as a telnet protocol through which the user can executethe existing MML commands.

Alarm transfer from network element to network management system (NMS)

Provides the statistical interface for NMS


49/71


51CT53331EN53GLA0

MCP18-B

The MCP18-B plug-in unit is used as the management computer unit in network

elements. For OMS, MCP18-B B01 or later must be used.

The MCP18-B is a Pentium®M based, PC compatible, single slot computer designedto interface to the internal standard PCI bus. The Pentium®M 745 central processingunit (CPU) comes in an Intel 479 ball micro-FCBGA form factor. The IntelPentium®M chipset (E7501 MCH & P64H2) provides the PCI and PCI-X interfaces.Integrated PCI peripherals provide dual Ethernet, dual SCSI, SVGA and USBinterfaces.

Scalability

RNC OMS is capable of handling capacity of RNC2600, 2 800 WCDMA BTSs and 4800 cells.

RNC OMS is capable of handling different types of mass management operationsunder the control of Net Act, so that there are management operations going on inparallel towards several elements. Mass operations are used when certainmanagement operations need to be done to certain group of network elements. Anexample of this are configuration data and software downloads to new base stations.


50/71


52CT53331EN53GLA0

HDS-B capacity and performance

Hard disks

73 GB formatted storage capacity/disk

Average seek time: read 4.5 ms/ write 5.0 ms

Data transfer rate of disk drive: 132.4 MB/s

SCSI buses

Data transfer rate 160 MB/s (80 MHz) in synchronous mode

SCSI bus is 16 bits wide

Maximum 16 devices on bus

SCSI bus can work in both LVD or SE mode

HDS-B

The HDS-B plug-in unit is used with the OMU and NEMU units. The computer unitsserve two 16-bit wide Ultra SCSI buses which connect to the HDS-B through externalshielded back-cables. The HDS-B has two independent SCSI buses for twocomputer units. In the case of OMU the SCSI buses pass through the HDS-B andcontinue to the other unit of the duplicated pair (OMU only). In the case of NEMU theSCSI buses pass into the HDS-B and end there. It is possible to connect other SCSIdevices on the same bus. The maximum number of installed SCSI devices, notcounting computer units, is 14.

The HDS-B plug-in unit is connected to the hardware management bus the via thebus interface of the HMSS. HDS-B has an interface to two HMS transmission linesvia back connectors.


51/71


53CT53331EN53GLA0

HDS-B

The HDS-B serves as a non-volatile memory for program code and data in the MGW

and RNC. It connects via the SCSI bus to the OMU and NEMU units.

Operating environment of HDS-B

The HDS-B plug-in unit is used with the OMU and NEMU units. The computer unitsserve two 16-bit wide Ultra SCSI buses which connect to the HDS-B through externalshielded back-cables. The HDS-B has two independent SCSI buses for twocomputer units. In the case of OMU the SCSI buses pass through the HDS-B andcontinue to the other unit of the duplicated pair (OMU only). In the case of NEMU theSCSI buses pass into the HDS-B and end there. It is possible to connect other SCSIdevices on the same bus. The maximum number of installed SCSI devices, notcounting computer units, is 14.

The HDS-B plug-in unit is connected to the hardware management bus the via thebus interface of the HMSS. HDS-B has an interface to two HMS transmission linesvia back connectors.

The HDS-B has automatically functioning SCSI bus terminators.

The HMSS has a separate 2N redundant power feed.

The HDS-B gets also 48V DC supply and power feed from the HMSS through backconnectors


52/71


54CT53331EN53GLA0

Ethernet Switch for ATM with 24 Ports (ESA24)

The ESA24 plug-in unit provides the Ethernet switch functionality for OMS.

2N redundant ESA24 provides duplicated IP connections towards the A-GPS server.

There are two Ethernet ports in the front panel.

ESA24

The 10/100 Mbps LAN switch plug-in unit ESA24 functions as the LAN switch unit ofthe IPA2800 ATM platform.

The ESA24 features:

Complies with IEEE802.1d Spanning Tree protocol.

Store and Forward operation

Half and full duplex on all ports

IEE802.3X Full Duplex flow control on all ports

Back pressure in Half Duplex mode on all ports

Priority queuing based on Port or 802.1p

None blocking operation and VLAN per 802.1q

Address table contains 8000 entries and Port Trunking

Differences between ESA12 and ESA24

Increase in FLASH memory from 2 to 8 MB

RAM memory 64 MBNew operating system (BiNOS)

Complies with IEEE802.1w Rapid Spanning Tree protocol

Complies with IEEE802.1s Multiple Spanning Tree protocol


53/71


55CT53331EN53GLA0

Operation and Maintenance Server (OMS)

The Operation and Maintenance Server (OMS) unit is responsible for RNC element

management tasks. It provides interface to the higher-level network managementfunctions and to local user interface functions.

These functions include both generic interfacing to the data communication network(DCN) and application-specific functions like processing of fault and performancemanagement data, implementation of the RNC user interface and support forconfiguration management of the RNC. This way the OMS provides easy and flexibleinterfacing to the RNC.

In previous releases, OMS is integrated in RNC2600. It is implemented with Intel-based industry standard PC core. It contains own disk devices, interfaces forkeyboard and a display for debugging purposes, a serial interface, an USB interface,and a LAN (100 Mbit/s Ethernet) interface.

In RN5.0, standalone OMS is introduced. It uses commercial HW: HP DL360Proliant. This offers better scalability to OMS performance and always offers thelatest and best HW technology available. This is the first evolution step towards newtechnologies - common OMS platform within different technologies. Same OMSapplications and functions are available on both platforms. This does not bring anychanges to existing OMS interfaces.

HP ProLiant DL360 Generation 6:

Quad core Nehalem Intel processors

12 GB memory (scalable up to 128 GB)

4 x Mirrored hard discs (4 x 146GB)

Dual port network card

SCSI card for external devices like data tapes and magneto-optical

USB 2.0 ports

Height 1U


54/71


56CT53331EN53GLA0

Benefits of standalone RNC OMS

The main benefits of Nokia Siemens Networks RNC OMS are outlined below.

State-of-the-art feature set

Nokia Siemens Networks’ long experience of radio access and mobile data networksmanagement and input based on operator requirements ensure that RNC OMSfunctionality and feature set are well considered and provide maximum benefit tooperators.

High quality, proven software platform

RNC OMS software is running on top of a carrier grade Flexi Platform (SW platform).

The Flexi Platform design ensures high availability, reliability, scalability and highperformance incorporating innovations from open standards such as Linux andJ2EE. RNC OMS is based on the field-proven NEMU unit used in Nokia SiemensNetworks 3G networks. Thus a high quality platform and increased benefits ofeconomies of scale are ensured.

Scalable, efficient architecture

RNC OMS provides scalability of operability architecture via aggregating, parsingand intermediating the operation and management traffic flow between Net Act andaccess network elements. RNC OMS performs individual management operations tonetwork elements under control of Net Act. RNC OMS is able to perform efficient

parallel mass operations towards several network elements and handle differentoperation and management operations simultaneously to the same network element.These capabilities reduce both the processing and database access load in Net Actmanagement system and overall management data transmission needs.


55/71


57CT53331EN53GLA0

Benefits of standalone RNC OMS (Cont)

Accurate status of the network

RNC OMS provides synchronized measurement data from the WCDMA AccessNetwork elements and real-time WCDMA BTS and RNC state supervision andmanagement, giving thus an accurate picture of network status. Reliable, correctinformation helps operators to make right daily operation and managementdecisions. It also gives good input to longer-term network planning, enablingoperators to plan network investments in a cost efficient manner.

Local operation interface

RNC OMS offers a local operation interface towards RNC. The interface makes it

possible to monitor access networks locally via RNC OMS during network roll-out,upgrade and expansion phases and during regular daily operation, when reasonable.

Secure software platform

RNC OMS runs on top of Flexi Platform/Red Hat, gaining thus from the securitybenefits of Red Hat Linux Security Framework. Industry experts consider the securityrisk of Linux to be low, thus giving relief to platform software security concerns.

Easy to place and install

RNC OMS has a compact size and it fits to a standard 19-inch rack.


56/71


58CT53331EN53GLA0

NIP1 contains PDH E1/T1/JT1 interfaces with Inverse Multiplexing for ATM (IMA)function, which allows for flexible grouping of physical links to logical IMA groups.

Normally, the PDH lines are used for connections between RNC and the BTSs.

NI16P1A

The NI16P1A plug-in unit implements sixteen PDH E1/T1/JT1 based ATM interfaces.The NI16P1A supports IMA, that is, several E1/T1/JT1 interfaces can be groupedinto one group that seems like one interface to the upper protocol layers. TheNI16P1A makes ATM layer processing related to the traffic management and Utopiaaddress embedding. The NI16P1A also provides a reference clock (that is recoveredfrom the incoming E1/T1/JT1 lines) for the TSS3 plug-in unit.


57/71


59CT53331EN53GLA0

NI4S1-B

The main functions of the NI4S1-B plug-in unit are the following:

implementing adaptation between SDH transport technology and ATMperforming ATM layer functions

implementing interface to ATM Switch Fabric.

The NI4S1-B can also be used to implement four SONET OC-3 interfaces.

Operating environment of NI4S1-B

NI4S1-B has the following interfaces with its environment:

four interfaces with physical medium

interface with ATM Switch Fabric (SF10)

interface with the Hardware Management System (HMS)

interface with TSS3 or TBUF plug-in unit.


58/71


60CT53331EN53GLA0

NP8S1-B, NP8S1-A and NP8S1

The NP8S1-B, NP8S1-A and NP8S1 plug-in units are interface units for IPA2800

network elements that are specifically designed for the optimized use of the InternetProtocol (IP) and the packet environment. NP8S1-B, NP8S1-A and NP8S1 aretargeted for the multiprotocol transport interfaces Iu-PS and Iu-CS. The primarytransport methods used are Packet over SONET (POS) and IP over ATM (IPoA).

NP8S1-B, NP8S1-A and NP8S1 provide multiprotocol packet processing at wirespeed and network connectivity with eight optical synchronous digital hierarchy(SDH) STM-1 or synchronous optical network (SONET) OC-3 interfaces. The highprocessing power of the network processor and the unit computer enable theNP8S1-B, NP8S1-A and NP8S1 plug-in units to process protocol and data at the lineinterface unit (LIU) instead of the dedicated processing units.

The unit NP8S1 also has capacity for two SDH STM-4 or SONET OC-12 interfaces,

but they are not supported and cannot be used.

NP8S1 and NP8S1-A are only used in MGW, NP8S1-B is only used in RNC.


59/71


61CT53331EN53GLA0

NP2GE-B, NP2GE-A and NP2GE

The NP2GE-B, NP2GE-A and NP2GE plug-in units are interface units that are

specifically designed for the optimized use of the Internet Protocol (IP) and thepacket environment. NP2GE-B, NP2GE-A and NP2GE are targeted for themultiprotocol transport interfaces Iu-PS and Iu-CS. The primary transport methodtype used is IP over Ethernet.

NP2GE-B, NP2GE-A and NP2GE provide multiprotocol packet processing at wirespeed and also offer the possibility of using both electrical (copper) and optical (fibre)based Ethernet. The high processing power of the network processor and the unitcomputer enable the NP2GE-B, NP2GE-A and NP2GE plug-in units to processprotocol and data at the line interface unit (LIU) instead of the dedicated processingunits.

NP2GE and NP2GE-A are only used in MGW, NP2GE-B is only used in RNC.


60/71


62CT53331EN53GLA0

The filter is closed in an EMC tight enclosure. Both supply lines go through the filter.The supply lines share a common choke but have X- and Y-capacitors of their own.

In both supply branches, large electrolytic capacitors are located on two dedicatedcapacitor boards. After the electrolytic capacitors, supply branches are branchedfurther to five sub branches which are protected by fast glass tube fuses and thensupplied to the backplane. One of the sub branches in the supply branches is for fantray.


61/71


63CT53331EN53GLA0

PD20

The Power Distribution Unit 20 A (PD20 plug-in unit) is a sub rack level power

distribution unit in the IPA2800 network element power feed system. The PD20provides filtering, power distribution and fan control functions.

PD30

The Power Distribution Unit 30 (PD30 plug-in unit) is a sub rack level powerdistribution unit in the Nokia IPA2800 Network Elements power feed system. ThePD30 provides filtering, power distribution, and fan control functions. In addition, thePD30 also provides over-current and overvoltage protection, and power dropoutstretching.

The PD30 incorporates reverse battery voltage protection for accidental installation

errors. It continues to operate after correct battery voltage polarity and voltage levelhave been applied to it.

The use of the older fan tray models FTR1 and FTRA damages the equipment. Onlyuse the fan trays FTRA-A and FTRA-B with PD30


62/71


64CT53331EN53GLA0

The CPD120-A allows for either grounding the 0V lead from the battery or for a useof a separate grounding cable to achieve floating battery voltage. From the CPD120-

A unit, the voltage is fed through the sub rack-specific PD30 power distribution plug-in units, which have individual 10-A fuses for each outgoing distribution line, to theother plug-in units in a likewise manner as to the cabinets, that is, through twomutually redundant supply lines. The two distribution lines are finally combined in thepower converter blocks of individual plug-in units, which adapt the voltage so that it isappropriate for the plug-in unit components.


63/71


65CT53331EN53GLA0


64/71


66CT53331EN53GLA0

New clock plug-in unit variant TSS3-A is implemented in RN5.0 based RNC2600deliveries. However, TSS3-A can be used with RN4.0 software if Bridge HMX1BNGX

version inside the plug-in unit is newer than in RN4.0 release packageDue to 2N redundancy a mixed configuration of TSS3 and TSS3-A is not allowed.The same variant must be used for both clock units in each RNC.

TSS3/-As generate the clock signals necessary for synchronizing the functions ofRNC. Normally, TSS3/-A operates in a synchronous mode, that is, it receives aninput timing reference signal from an upper level of the network and adjusts its localoscillator to the long time mean value by filtering jitter and wander from the timingsignal. It transmits the reference to the plug-in units in the same sub rack (all plug-inunits are equipped with onboard PLL blocks), as well as to the TBUF units, whichdistribute the signals to units not directly fed by TSS3/-As.

TSS3/-A has inputs for both synchronization references from other network elements(via the network interfaces) and for those from external sources (options are 2048kbit/s, 2048 kHz, 64+8 kHz, 1544 kHz, or 1544 kbit/s (TSS3-A)). TSS3-A input is 5 Vtolerant.

If all synchronization references are lost, TSS3/-A can operate in plesiochronousmode, that is, by generating independently the synchronization reference for theunits in the network element.

TSS3/-As are also involved in the functioning of the HMS bus. They convey HMS

messages through the HMS bridge node to the HMS master node. Each OMU hasone master node.

TSS3-A is designed to conform ITU-T G813, G.703 and Bell core GR-1244recommendation.


65/71


67CT53331EN53GLA0

TSS3 and TSS3-A

The Timing and Synchronization, SDH, Stratum 3 (TSS3 plug-in unit) or the Timing

and Synchronization, SDH, Stratum 3, Variant A (TSS3-A plug-in unit) and TBUFplug-in units provide the functionality of the Timing and Hardware Management BusUnit (TBU) functional unit. This functional unit is responsible for synchronization,timing signal distribution and message transfer in the Hardware ManagementSystem of a network element.

The RNC and the MGW configurations have always one duplicated synchronizationunit implemented as two TSS3 or TSS3-A plug-in units. The TSS3s or TSS3-As arelocated in either of the two half-size slots in sub racks 1 and 2 of rack 1. Theremaining half-size two slots in these sub racks are equipped with TBUs, and so areall other such slots in other sub racks of the network element. Both TSS3s or TSS3-

As form a subsystem which is 2N redundant, so there are always two TSS3 orTSS3-A plug-in units working in active/cold standby fashion.

TBUF

The Timing Buffer (TBUF plug-in unit) and the TSS3 plug-in units provide thefunctionality of the Timing and Hardware Management Bus Unit (TBU) functionalunit. This functional unit is responsible for synchronization, timing signal distributionand message transfer in the Hardware Management System of a network element.

The RNC and the MGW configurations have always one duplicated synchronizationunit implemented as two TSS3 plug-in units. The TSS3s are located in either of thetwo half-size slots in subracks 1 and 2 of rack 1. The remaining half-size two slots inthese subracks are equipped with TBUFs, and so are all other such slots in other

subracks of the network element. The redundancy method is 2N.


66/71


68CT53331EN53GLA0

Synchronization

Usually the distribution of synchronization references for RAN NEs (BTS, RNC) is

based on a master-slave architecture, where the transport network is used forcarrying the synchronization references. In particular, this is the case for basestations.

In a master-slave synchronization architecture, a synchronization reference traceableto the Primary Reference Clock (PRC) is carried via the transport network to RANNEs. Traceability to the PRC means that the synchronization reference originatesfrom a timing source of PRC quality. The characteristics of primary reference clocksare specified in ITU-T Recommendation G.811 [8].

The hierarchical master-slave principle is generally used in traditional TDM basedsynchronization, where a PRC traceable reference is carried through asynchronization distribution chain via intermediate nodes to RAN NEs. In RAN NEs

(BTSs shown in the following figure) the timing reference is recovered from theincoming transport interface (e.g. E1, T1, STM-1). The recovered reference isfrequency locked to the original PRC signal, but due to impairments in the transportnetwork there is some jitter and wander in the recovered synchronization reference.


67/71


69CT53331EN53GLA0

RNC has two separate timing and synchronization distribution buses to ensure 2Nredundancy for the internal timing signal distribution. Each bus has its own system

clock (a TSS3/-A plug-in unit), distribution cabling, and timing buffers (TBUF plug-inunits).

The two TSS3/-A units backing up each other are placed in different subracks(subracks 1 and 2), each of which is powered by a power supply plug-in unit of itsown to ensure redundancy for the power supply. Each of these subracks is alsoequipped with a TBUF plug-in unit, which connects the equipment in the sub rack tothe other clock distribution bus. The RNAC subracks 3 and 4 and all RNBC subrackshave two separate TBUF units, which connect to different clock distribution buses bymeans of cables of their own.

In order to function correctly, the differential buses need terminations in the ends ofthe bus by means of a termination cable. Due to the expansion of the networkelement through the capacity steps, the end of the bus and similarly the terminationpoint changes. When a new subrack is taken into use in a capacity step, the cablingmust always be moved to the new subrack.

Duplicated buses need two terminations, which means that four terminatorsaltogether in each cabinet are required for the HMS and the timing andsynchronization distribution bus


68/71


70CT53331EN53GLA0

The optional peripheral EXAU-A / EXAU provides a visual alarm of the faultindications of RNC. The EXAU-A / EXAU unit is located in the equipment room.

The CAIND/-A is located on top of the RNAC cabinet and provides a visual alarmindicating the network element with a fault.


69/71


71CT53331EN53GLA0

The Hardware Management System (HMS) provides a duplicated serial bus betweenthe master node (located in the OMU) and every plug-in unit in the system. The bus

provides fault tolerant message transfer facility between plug-in units and the HMSmaster node.

The HMS is used in supporting auto-configuration, collecting fault data from plug-inunits and auxiliary equipment, collecting condition data external to network elementsand setting hardware control signals, such as restart and state control in plug-inunits.

The hardware management system is robust. For example, it is independent ofsystem timing and it can read hardware alarms from a plug-in unit without power.

The HMS allows power alarms and remote power on/off switching function.

The hardware management system forms a hierarchical network. The duplicatedmaster network connects the master node with the bridge node of each sub-rack.The sub-rack level networks connect the bridge node with each plug-in unit in thesub-rack.


70/71


72CT53331EN53GLA0

HMS Master Node (HMMN)

Head of Hardware Management System, which has responsible for example

selecting the transfer line and supervision of HMS bridge nodes.

Reside on OMU

HMS Bridge (HMSB)

Divides Hardware Management System into sub network, which physicallyeach sub rack.

Reside on TSS3 and TBUF

HMS Slave (HMSS)

Interfaces with for example PIU’s power and hardware alarms.

Reside on all PIUs except ESA12/24


71/71


01 01 CT53331EN53GLA0 RNC Architecture and Functionalities

Documents

Transcript of 01 01 CT53331EN53GLA0 RNC Architecture and Functionalities