RNC2600

[bbiswajit90ece]

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
1 (74)





Nokia WCDMA RNC Product
Description for RNC2600 RN4.0



DRAFT





Nokia WCDMA RNC Product Description for RNC2600

2 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is intended for the
use of Nokia's customers only for the purposes of the agreement under which the document is
submitted, and no part of it may be reproduced or transmitted in any form or means without
the prior written permission of Nokia. The document has been prepared to be used by
professional and properly trained personnel, and the customer assumes full responsibility
when using it. Nokia welcomes customer comments as part of the process of continuous
development and improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products cannot be considered binding
but shall be defined in the agreement made between Nokia and the customer. However,
Nokia has made all reasonable efforts to ensure that the instructions contained in the
document are adequate and free of material errors and omissions. Nokia will, if necessary,
explain issues which may not be covered by the document.
Nokia's liability for any errors in the document is limited to the documentary correction of
errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING
MONETARY LOSSES), that might arise from the use of this document or the information in it.
This document and the product it describes are considered protected by copyright according
to the applicable laws.
NOKIA logo is a registered trademark of Nokia Oyj.
Other product names mentioned in this document may be trademarks of their respective
companies, and they are mentioned for identification purposes only.
Copyright © Nokia Oyj 2007. All rights reserved.

Contents

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
3 (74)

Contents
1 Nokia Radio Network Controller RNC2600......................................... 5
1.1 RNC functionality ................................................................................... 7
2 RNC interfaces ................................................................................... 12
3 RNC2600 architecture........................................................................ 15
3.1 Computer units .................................................................................... 17
3.2 Control computers ............................................................................... 18
3.3 Signal processing units ........................................................................ 20
3.4 Element management units ................................................................. 21
3.5 Peripheral devices ............................................................................... 22
3.6 Switching and multiplexing units .......................................................... 22
3.7 Timing and hardware management bus unit ........................................ 23
3.8 Alarm units........................................................................................... 23
3.9 Network Interface Units (NIU) .............................................................. 24
4 RNC software ..................................................................................... 25
4.1 Platform architecture............................................................................ 25
5 RNC2600 capacity.............................................................................. 27
5.1 Capacity licensing................................................................................ 27
5.2 Configuration steps of the RNC2600.................................................... 28
5.3 RNC capacity extensions and upgrade ................................................ 29
5.4 Capacity and reference call mix model................................................. 33
5.5 Traffic mix rule ..................................................................................... 36
6 RNC hardware management and supervision ................................. 37
7 RNC2600 reliability ............................................................................ 39
7.1 Reliability from the maintenance point of view...................................... 40
7.2 RNC availability performance............................................................... 41
7.3 Redundancy principles......................................................................... 42
8 RNC2600 physical interfaces ............................................................ 45
8.1 Synchronisation interfaces................................................................... 46
8.2 LAN/Ethernet for O&M connections ..................................................... 48
8.3 Timing and synchronization ................................................................. 49
9 RNC2600 mechanical design ............................................................ 51
10 RNC2600 power requirements .......................................................... 56
11 RNC2600 operating environment...................................................... 61
11.1 Equipment room .................................................................................. 61
11.2 Cooling of the cabinets ........................................................................ 62
Nokia WCDMA RNC Product Description for RNC2600

4 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

11.3 Operating temperature and humidity tolerances................................... 63
12 RNC standards................................................................................... 65
12.1 EMC standards .................................................................................... 65
12.2 Power feed........................................................................................... 65
12.3 Grounding and bonding........................................................................ 66
12.4 Environmental durability....................................................................... 66
12.5 Earthquake .......................................................................................... 67
12.6 Interfaces............................................................................................. 67
12.7 Environmental conditions ..................................................................... 68
12.8 Legislation............................................................................................ 69
12.9 Electromagnetic environment............................................................... 70
12.10 European Union RoHS Directive.......................................................... 70
13 RNC eco-efficiency ............................................................................ 71
14 RNC site equipment........................................................................... 73


RNC interfaces

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
5 (74)

1 Nokia Radio Network Controller
RNC2600
The Nokia radio network controller (RNC) is based on a fault tolerant
packet switching platform. The main function of the RNC is to control
and manage the radio access network (RAN) and the radio channels.
The RNC is designed for efficient use of radio resources and easy
operation and maintenance. This document concentrates on the release
RU10 / RN4.0.
RNC2600 replaces RNC450 as new delivery in RU10/RN4.0 release
onwards.
Nokia WCDMA RNC Product Description for RNC2600

6 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en





Figure 1. Nokia radio network controller RNC2600
RNC interfaces

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
7 (74)

1.1 RNC functionality
The tasks and functions of the RNC are briefly explained below.
Because of the highly modular and generic RNC architecture, the
future requirements for the RNC can be implemented easily. The
modular structure also supports optimised dimensioning and the cost of
surplus capacity is thus removed. High reliability and fault tolerance
are supported by redundant units (2N, N+1 and SN+).
Radio resource management
The available radio spectrum is utilised efficiently to optimise the inter-
related cell coverage, cell capacity and service quality aspects
according to network planning targets. Advanced Nokia radio resource
management algorithms (admission control, handover control, load
control, packet scheduling and power control) provide these. The Nokia
radio resource management solution enables optimised bearers and
services.
RNC radio resource management (RRM) manages channel allocations,
that is, the number of traffic channels and signalling channels that can
be used in the RAN simultaneously. This is done in connection with the
radio network planning. RRM can be divided into network-based
functions and connection-based functions as shown in the figure below:



Figure 2. Radio resource management
Nokia WCDMA RNC Product Description for RNC2600

8 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Some network-based functions (admission control, packet scheduler)
work on event basis, that is, service requests are handled as they arrive.
Load control is a continuous process monitoring the cell load and
managing loads when necessary.
When it comes to connection-based functions, power control and
handover control are activated when a radio link is allocated to
connection. The user equipment (UE) runs handover control, outer loop
power control and fast closed loop power control in mobile state
Cell_DCH. In other states the UE uses open loop power control.
• Admission control (AC)
Admission control is used to maintain stability and to achieve high
traffic capacity of the RAN. The AC algorithm is executed when
the radio access bearer is set up or the bearer is modified. The AC
measures also take place with all kinds of handovers.
• Load control (LC)
Load control sees to that the system is not overloaded and that it
remains stable. If, however, the system is overloaded, the system is
returned back to the normal load state, defined by the radio
network planning, in a quick and controlled manner.
• Power control (PC)
Since the WCDMA system is interference limited, that is, the less
interference the more capacity, it is beneficial to use as low
transmission power at the transmitting entities as possible.
Therefore, the target of the power control (PC) is to achieve the
minimum signal-to-interference ratio (SIR) that is required for the
sufficient quality of the connection. PC works on a radio link basis.
• Handover (HO) control
The handover control (HC) of the RAN supports soft handovers
and hard handovers. Handovers are controlled by the RNC, but
both the UE and the RNC can initiate them.
• Packet Scheduler (PS)
Packet scheduler is a general feature, which takes care of
scheduling radio resources for non-real time radio bearers.
RNC interfaces

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
9 (74)

Operation and maintenance
Operation and maintenance is the means for the operator personnel
to maintain the radio network (RNW) and the RNC in optimal
condition. The RNC is provided with an easy-to-use graphical user
interface. This allows illustrative presentations for configuration,
fault, and performance management information. The same
Element Manager can be used via a local terminal or Network
Management System.
The RNC offers the possibility for maintenance procedures that are
part of the alarm system. This contains the following sub-areas:
• The supervision system performs continuous checking to detect
irregularities in the operation of the network element and
informs the alarm system about them.
• The alarm system identifies the faulty unit and informs you and
the recovery system about the fault. The alarm system also
stores the alarm events in the alarm history.
• The recovery system eliminates the escalation of the fault by
isolating the faulty unit from the rest of the system. A spare
unit, if one is available, is taken into use.
• The fault diagnosis system pinpoints the cause of the fault
more precisely and informs you and the recovery system about
the status of the unit. It also verifies that the hardware is
functioning properly.
• reconfiguration of the RNC
• reconfiguration support to the BTS
• remote software upgrade in the RNC and BTS
• During normal operation, the RNC offers various possibilities
for the operator:
• modification of the radio network parameters
• display of radio network alarms
• configuration of the RNC hardware and automatic notification
of HW changes to NetAct
• administration of the RNC equipment, fault localisation tool
• user authentication and action logging
• extended (key performance indicator KPI) calculating
possibilities in RNC
• threshold-based performance triggering
Nokia WCDMA RNC Product Description for RNC2600

10 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

o pre-defined RNW Configuration Profiles for BTSs
o RNC tools for fault localisation: Diagnostics and state handing
GUIs
o RNC supports license handling mechanism for activating
optional features and controlling the capacity.
Site solution
The Nokia RNC can be located at the core network site or in a
remote location near the base stations. This makes it possible to
optimise RNC configurations for different areas. Integrated IP and
SDH/Sonet transmission interfaces are provided for ATM based
transport. The one-cabinet configuration of the RNC is small and
compact, measuring only 600 x 600 x 2100 mm. The two-cabinet
configurations provide extensive capacity.
Nokia provides complementary transport solutions with external
transport device for various transport needs. For example Hybric
BTS backhaul feature is supported providing IP transport in Iub.
Telecom
Telecom basic functionality and end-user related features
concentrate on the functional procedures and end-user services
provided by the RAN. These include:
• user plane processing towards CS and PS core network (for
example management of radio access bearers (RAB))
• radio network layer control plane processing
• security functions, integrity checking, ciphering
• location services
• service area broadcast
• HSPA functionalities
Transmission and transport
Transmission and transport features include:
• integrated transmission interfaces
• transport network layer control plane processing (for example
AAL2 signalling)
• ATM transport over SDH/Sonet or PDH
• ATM and AAL2/AAL5 transport on Iu-CS, Iu-PS, Iu-BC, Iur,
Iub
• IP over Ethernet transport.
• HSPA transport with best effort AAL2 QoS
• 3GPP Iub
• UBR+ and path selection in Iub providing savings in the ATM
transport costs

RNC interfaces

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
11 (74)

Element Manager and Nokia NetAct
The RNC Element Manager (EM) provides a user-friendly
graphical interface that assists the user with useful online helps.
The same screen formats are also available via the NetAct.
The RNC Element Manager is the program that runs in the local
management tool. The local management tool is connected to the
LAN interface of the RNC either for local or remote element
management purposes. One RNC can support dozens of
simultaneous sessions from NetAct or EM.
The RNC user interface is based on WWW technology, which
ensures familiar and efficient ways of operation. Where possible,
graphics are added to the user interface.
The user interface assists the user in the efficient administration of
the operation and maintenance functions, but because the functions
in the RNC are geared to be operated mainly from the NetAct
while the RNC site may remain unmanned, there is seldom need
for local operation. However, if this is necessary, the user interface
supports simultaneous administration of local operations at the
RNC site and remote operations from the NetAct. The user
interface meets the needs of the user by achieving superior
administration of the RNC O&M functions.
Measurements and observations
The RNC executes various measurements about radio network,
transmission network and RNC performance. It is possible to
measure cell loads, handover control and outer loop power control
in the radio network in real time (online monitoring). In RNC there
are also extended KPI (key performance indicator) calculating
possibilities.
The measurements are post-processed in the OMS of the RNC and
then forwarded to the NetAct.
Nokia WCDMA RNC Product Description for RNC2600

12 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

2 RNC interfaces
The radio network controller (RNC) provides logical interfaces for the
mobile services switching centre (MSC), the multimedia gateway
(MGW), other RNCs, Nokia NetAct, base transceiver stations (BTSs),
the serving GPRS support node (SGSN) and the cell broadcast centre
(CBC).

Figure 3. RAN interfaces
The radio access network (RAN) reference model defines a system
consisting of the functional network elements RNC and BTS. Each
BTS is connected to only one RNC via Iub interface, whereas an RNC
can be connected to a number of other RNCs via Iur interface. Each
RNC is also connected to MGW, MSC, 3G-CBC and 3G SGSN via Iu
interface.
The RNC supports a connection to multiple core networks.
RNC interfaces

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
13 (74)

The multi-operator RAN feature enables sharing of the RAN, including
the RNC, between several operators.
Iub interface (RNC-BTS)
The Iub interface telecommunication part takes place between the RNC
and the BTS. In order to be fully compatible with the 3GPP Iub
interface, the layer 3 control plane protocol (NBAP protocol) is
implemented according to the 3GPP NBAP specification TS25.433
instead of the Nokia NBAP specification. The main differences
between Nokia and 3GPP protocols are in the Logical O&M part of the
NBAP. Also, some other NBAP procedures of RAN release 1 require
changes to be fully compliant with the 3GPP NBAP specification.
Iur interface (RNC-RNC)
The Iur interface is used to support soft handovers within the RAN.
Connections that are managed by two RNCs are managed by soft
handovers. All necessary data from the serving RNC (SRNC) is
transferred to the drifting RNC (DRNC) across the Iur interface. The
Iur is an open and standardised interface.
Iu interface (RNC-MSC and RNC-SGSN)
The Iu interface between the core network and the RNC is divided into
two separate functional parts to support circuit-switched and packet-
switched services to the core network. The Iu interface is implemented
according to the 3GPP standards. The open Iu interface means that the
RNC can be connected to core networks of other suppliers.
Iu-BC interface (RNC-CBC)
The Iu-BC interface between the MSC and the CBC is implemented
according to the 3GPP standards. The open Iu-BC interface means that
the RNC can be connected to the cell broadcast centre (part of core
network) of other suppliers.
Iu-PC interface (RNC-SAS)
The Iu-PC interface is a logical interface for the interconnection of the
Stand-Alone SMLC (SAS) and the RNC via the PCAP protocol. The
SAS provides GPS assistance data to the RNC and may perform the
position calculation function for various positioning methods.
Nokia WCDMA RNC Product Description for RNC2600

14 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Network management interface (RNC-NetAct)
The data communications network (DCN) architecture provides
connections for the implementation of O&M functions from the radio
access network to the operation support system (Nokia NetAct). A
common transport protocol is provided for the DCN network and the IP
used as a flexible solution for network management.
Network management operations are initiated from NetAct, messages
related to these operations are routed by the RNC to the appropriate
network element. The DCN to realise this is based on TCP/IP
communication protocol. RNC and NetAct application level
communication is based on CORBA, while communication between
RNCs and BTSs takes place across the Iub interface. The O&M traffic
is secured by IPSec protocol between RNC and NetAct.
RNC provides LAN interface (ethernet) or IP over ATM (IPoA)
connection to the rest of the O&M network. IPoA and LAN
connections can be combined to achieve redundant O&M connections
to RNC from NetAct. The MML command line interface is available
via telnet.
RNC2600 architecture

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
15 (74)

3 RNC2600 architecture
The RNC has a modular software (SW) and hardware (HW) structure,
which allows scalability of processing power and switching capacity, as
well as flexibility in terms of the number and types of interfaces. Due to
exact specifications for the interfaces between different modules, new
functions can easily be added without changing the architecture of the
system. Therefore, the RNC has a long operational life span and can still
contain new up-to-date features. For more information on the existing RNC
features, see WCDMA RAN05.1 Existing Features and RAS06 Features
under development and on new features, see WCDMA RAN release RU10
Feature Candidates
The complexity of services envisioned for future networks calls for
computing power in the network elements. The RNC is well positioned to
provide required scalability and flexibility through the distributed, fault-
tolerant computing environment provided by the fault-tolerant computing
platform.
The packet switching platform provides generic ATM and IP functionality
common for several application areas, such as statistics, connection
control, traffic management, operations and maintenance, and resource
management.
A hardware platform based on standard mechanics provides cost-efficiency
through the use of modular, optimised and standardised solutions that are
largely based on commercially available chipsets.
A block diagram of the RNC shows the general functional architecture of
the RNC. At high level, the network element consists of the following
parts:
• network interface functions
• switching and multiplexing functions
• control plane functions
• user plane functions
• O&M functions
Nokia WCDMA RNC Product Description for RNC2600

16 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

The functions are distributed to a set of functional units capable of
accomplishing a special purpose. These are entities of hardware and
software. The main functional units of the RNC are listed below.
• The control computers (ICSU) consist of common hardware and
system software supplemented with function-specific software.
• The data and macro diversity unit (DMCU) performs RNC-related user
and control plane L1 and 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 has hard disk units for program code and data.
• 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, synchronisation and system maintenance functions.
• The Network interface and processing unit 8xSTM-1/OC-3
(NPS1/NPS1P) provides STM-1 external 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 provides
Ethernet external 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 is to drive the lamp panel
(EXAU), the cabinet-integrated lamp and possible other external
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 for the system's internal
communication.
RNC2600 architecture

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
17 (74)



Figure 4. Block diagram of the RNC2600
3.1 Computer units
The distributed processing architecture of the RNC is implemented by a
multiprocessor system based on the most suitable commercially available
microprocessors. In a multiprocessor system, the data processing capacity
is divided among several computer units.
Computer units form the basis for the computing platform. According to
application needs, several general-purpose computer units with the
appropriate redundancy principle (no redundancy, 2N, N+1 or SN+) can be
assigned to different tasks. Specialised units (generic or application-
specific) typically
Nokia WCDMA RNC Product Description for RNC2600

18 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

include application-specific hardware and software. In general, processing
capacity can be increased by distributing the functions of the network
element to multiple computer units and by upgrading computer units with
more powerful variants.
In the RNC, call-handling capacity depends on the number of equipped
units. Adding more control computer units and signal processing units
respectively can easily increase the capacity of the RNC.
In order to guarantee high capacity and throughput, internal
communication between the computer units and other units of the system is
based on the use of ATM virtual connection.
3.2 Control computers
OMU
The RNC always includes a duplicated (2N) OMU to provide high
availability and minimised interruptions in usage (see Redundancy
principles in RNC2600 reliability). Duplicated system disk units are
connected to and controlled by the OMU. The system disk units contain the
operative software and the fallback software of the RNC.
The cellular management functions of the OMU are responsible for
maintaining the radio network configuration and recovery. The OMU
monitors the status of the network and blocks the faulty units if necessary.
The OMU contains the radio network database, ATM/IP configuration
database, RNC equipment database and alarm history database.
The OMU unit further contains basic system maintenance functions and
serves as an interface between the RNC and the O&M Server unit (OMS).
In the event of a fault, the unit automatically activates appropriate recovery
and diagnostics procedures within the RNC. 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 can be used, for example, as a management interface
of the network element
• a service terminal interface which provides support for debugger
terminals
RNC2600 architecture

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
19 (74)

• a multiplexer interface that allows termination of ATM virtual
connections to the computer unit, thus supporting both inter-processor
communication and termination of external connections in the network
element (used, for example, for signalling or network management
purposes).
• a duplicated hardware management system interface (see RNC
hardware management and supervision)
• a USB 1.1 port and drivers for loading software or making backups
locally to the RNC

ICSU
The interface control and signalling unit (ICSU) performs those RNC
functions that are highly dependent on the signalling to other network
elements. The unit also handles distributed radio resource management
related tasks of the RNC.
The unit is responsible for the following tasks:
• layer 3 signalling protocols RANAP, NPAB, RNSAP, RRC and SABP
• transport network level signalling 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 (see Redundancy principles in
RNC2600 reliability), there is one extra ICSU in addition to the number set
by the dimensioning rules. The additional unit is used only if one of the
active units fails.
Nokia WCDMA RNC Product Description for RNC2600

20 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

RSMU
The resource and switch management unit (RSMU) performs the RNC's
central resource management tasks such as connection control, ATM
resource scheduling and DSP related resource management tasks. It also
performs the call connection related functions according to requests
received from signalling computer units (ICSU). The unit is 2N redundant
to provide high availability. The unit is responsible for the following tasks:
• DSP resource management
• supervision and management of the DMCU units
• software loading of the DMCU units
• allocation of DSP and related computer resources for different tasks,
such as macrodiversity combining and data traffic functions
• management of the ATM connections within the DMCU
• ATM connection control and ATM resource management functions


3.3 Signal processing units
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 digital signal processors (DSPs) and general purpose RISC
processors. The signal processing tasks can be configured and altered
dynamically for each DSP. The unit is SN+ redundant. The unit is
responsible for the following tasks:
• UE and L2 related protocols
- frame protocol (FP)
- radio link control (RLC)
RNC2600 architecture

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
21 (74)

- medium access control (MAC)
- application level IP header compression
• The following functions within protocols:
- FP: macro diversity combining
- FP: outer loop PC
- RLC/MAC: ciphering
- PDCP: header compression
- HSPA processing (MAC-SH, EDCH)

3.4 Element management units
OMS
The O&M Server unit (OMS) is responsible for RNC element management
tasks. It provides interface to the higher-level network management
functions 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 performance management data, implementation of the RNC user
interface and support for configuration management of the RNC. This way
the OMS provides easy and flexible interfacing to the RNC.
The OMS is implemented with an Intel-based industry standard PC core. It
contains own disk devices, interfaces for keyboard and display for
debugging purposes, a serial interface, a USB interface, and a LAN (100
Mbit/s Ethernet) interface. Communication between the OMS and the rest
of the RNC takes place on the Ethernet.
The OMS is implemeded on top of linux based Nokia Flexi platform
providing high availability and security. The OMS does not have
redundancy because it does not affect traffic switching capabilities. The
unit is responsible for the following tasks:
• user interface, both GUI functionalities and MMI for MML sessions
• NetAct interface
• O&M functions in the RNC

Nokia WCDMA RNC Product Description for RNC2600

22 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

• post-processing support for measurement and statistics tasks
• Duplicated SCSI interface for connecting mass memory devices

ESA24, Ethernet Switch for ATM with 24 Ports
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 2 Ethernet ports in the front panel.
3.5 Peripheral devices
The peripheral devices of the RNC2600 are:
• a Winchester disk unit for OMU
• OMS hard disk units


WDU
The RNC has a Winchester disk unit (WDU) that serves as a non-volatile
memory for program code and data. Duplicated system disk units are
connected to and controlled by the OMU. The OMS has a separate
duplicated Winchester disk (2N). Disk units are included in HDS-B type of
disk adapter.

3.6 Switching and multiplexing units
Switching and multiplexing in the RNC are based on ATM technology.
The ATM technology provides required capacity and flexibility to support
various traffic types in the network and also within the network element
itself.
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 as differentiated handling of
various ATM service categories.
RNC2600 architecture

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
23 (74)

High capacity network interface units and multiplexer units are connected
to the 2N redundant SFU.
MXU
The multiplexer unit (MXU) multiplexes traffic from tributary units to the
ATM switching fabric. Therefore, it allows the efficient use of switching
resources for low bit rate network interface units and computer units with
small to moderate bandwidth requirements. 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 units are connected to the switching fabric via the MXU, which is
a 2N redundant unit. The RNC has several pairs of MXUs, depending on
the configured capacity (see RNC2600 capacity).
3.7 Timing and hardware management bus unit
The timing and hardware management bus unit (TBU) is responsible for
the network element synchronisation, timing signal distribution and
message transfer functions in the hardware management system.
This duplicated functional unit consists of two plug-in units in each
subrack. It also has a serial bus, spanning all plug-in units of the network
element.
3.8 Alarm units
EHU
The purpose of the external hardware alarm unit is to receive external
alarms and send indications of these as messages to the OMU-located
external alarm handler via the HMS. Its second function is to drive the
external lamp panel (EXAU), the cabinet integrated lamp and any other
external equipment. The interface includes 32 voltage-controlled inputs, 8
current-controlled inputs, 16 general purpose 20 mA current outputs.
Connections to external devices are performed via a cabling panel located
on the rear side of the RNC cabinet.
Nokia WCDMA RNC Product Description for RNC2600

24 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Optional EXAU
The external alarm unit provides indications about RNC-network elements'
faults in the telecommunication equipment room.
3.9 Network Interface Units (NIU)
NPS1/NPS1P
The network interface and processing unit 8xSTM-1/OC-3 (NPS1/NPS1P)
provides STM-1/OC-3 external interfaces and the means to execute
physical layer and ATM layer functionality. The unit maps ATM cells to
and from the transmission frame structure of SDH/ Sonet. Additionally, the
unit performs ATM layer functions such as header translation, AAL2
minipacket switching, UPC/NPC parameter control, OAM functions,
traffic management, performance monitoring and performance data
collection. NPS1P supports transmission protection (MSP 1+1 / APS 1+1)
for SDH/Sonet interfaces. The unit also provides an optional reference
clock for timing and synchronisation.
In case of Iu-ps interface the GTP protocol termination is done in
NPS1/NPS1P unit.

NPGE/NPGEP
The network interface and processing unit 2x1000Base-T/LX
(NPGE/NPGEP) provides Gigabit Ethernet external interfaces and the
means to execute physical layer and IP layer functionality. The unit maps
IP packets to and from the transmission frame structure of Ethernet.
Additionally, the unit performs IP layer functions such as header
translation, OAM functions, traffic management, performance monitoring
and performance data collection. The unit supports transmission protection
for Gigabit Ethernet interfaces within the plug-in unit.
In case of Iu-ps interface the GTP protocol termination is done in
NPGE/NPGEP unit.


RNC hardware management and supervision

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
25 (74)

4 RNC software
In the RNC, each control computer has common system software. This
uniform system software provides a standard, easy-to-use operating
environment for the application software. The uniform operating
environment facilitates the development and maintenance of the
application software and helps the user understand the operation of the
software.
4.1 Platform architecture
The RNC is based on a fault-tolerant computing platform, which
constitutes a base for switching and offers a wide range of cellular and
fixed network applications. The operating system is a platform for
other system level software and all the application software. The most
significant functions of the operating system are:
• scheduling the processor time
• synchronisation of processes
• exchange of messages between processes located in one
computer or in separate computers
• time supervision
• creation and deletion of processes
• memory allocation and protection
• observation of message traffic and processor load
• initialisation of the operating system
Nokia WCDMA RNC Product Description for RNC2600

26 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en


RNC hardware management and supervision

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
27 (74)

5 RNC2600 capacity
In the radio access network (RAN), the RNC is a stand-alone network
element that is connected to the surrounding network elements by
means of standard transmission interfaces.
The RNC2600 can be equipped for three different HW configuration
steps. The smallest configuration consists of one cabinet containing the
main parts of the entire node as well as the first capacity step plug-in
units. The second configuration requires an additional second cabinet
and plug-in units for two subrack added. The maximum (the third)
configuration requires two cabinets with full configured plug-in unit
amount.
RNC2600 supports capacity licensing and the actual capacity of
RNC2600 is defined by the capacity license files. The SW
configuration only defines the maximum capacity from the HW point
of view.
5.1 Capacity licensing
Capacity licensing allows to license capacity based on the actual traffic
needs. This allows cost efficient use of RNC in all different kinds of
networks. Capacity extensions are easy to be executed even without
any site visits.
Capacity is licensed by three capacity parameters:
• Iub PS data throughput (Mbit/s)
• AMR capacity (Erl)
• Number of carriers
License key for each of the capacity parameters needs to be installed in
RNC. The capacity is defined when the RNC ordered and
corresponding capacity license files are delivered with the RNC.
Capacity upgrades can be made by ordering new capacity license files
and activating those from NetAct or with the local element manager, as
long as the capacity is below the limits of the HW of the configuration
step.
Capacity figures are calculated without any optional features. These
may affect the overall capacity.
Nokia WCDMA RNC Product Description for RNC2600

28 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

5.2 Configuration steps of the RNC2600
RNC configurations are dynamically optimised for high speech or data
capacity. Same RNC HW configuration can be optimized in different
type of networks with more PS or AMR traffic and it scales well for
networks of different size.
The maximum nominal traffic throughput in maximum configuration is
2000 Mbit/s, which can be divided between speech and data users.
The Nokia RNC is designed especially for simultaneous dynamic
allocation and handling of speech, circuit-switched data and packet-
switched data. Advanced radio resource management algorithms can
achieve this.
The figures below show the division to different configuration steps
and the location of the units in the sub racks.







RNC hardware management and supervision

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
29 (74)


Figure 7. RNC2600 configurations

RNC2600/step1
RNC2600/step2
RNC2600/step3
RNC2600/step1
RNC2600/step2
RNC2600/step3

Figure 8. RNC2600 configuration and plug-in unit locations. (PIU
locations will change)

5.3 RNC capacity extensions and upgrade
The cabinets are delivered with all subracks, connector panels and
intra-cabinet cables installed at the factory. All cables that are needed
are included (such as intra-cabinet cabling for subracks). Empty plug-in
unit positions in subracks are covered with cover plates.
RNC capacity depends on the number of capacity extensions installed.
RNC2600/step 1
The smallest configuration step RNC2600/step 1 includes the first
cabinet and the plug- in-units for the following functional units:


Nokia WCDMA RNC Product Description for RNC2600

30 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Table 1. Units in RNC2600/step 1
Functional
Unit
Number of
units
ICSU 14
DMCU 18
MXU 8
RSMU 2
SFU 2
OMU 2
WDU 2
OMS HD 2
OMS 1
EHU 1
TBUF 6
TSS3 2
Power 4
NPS1 6 optional
NPS1P 6 optional
NPGE 6 optional
NPGEP 6 optional
ESA24
1 + 1
optional
_________________________________________________________
Note
NPS1 and NPS1P / NPGE and NPGEP are mutually exclusive.
_________________________________________________________

RNC2600/step 2
Configuration extension to RNC2600/step 2 can be obtained by adding
the new cabinet and necessary plug-in units and connecting internal
cabling between cabinets.
Table 2. Units in RNC2600/step 2
Functional
Unit
Number of
additional
units
Total number of
units in
RNC2600/step 2
ICSU 12 26
DMCU 10 28
MXU 4 12
RSMU - 2
SFU - 2
OMU - 2
WDU - 2
OMS - 1
OMS HD - 2
EHU - 1
TBUF 4 10
RNC hardware management and supervision

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
31 (74)

TSS3 - 2
Power 2 6
NPS1 4 10 optional
NPS1P 4 10 optional
NPGE 4 10 optional
NPGEP 4 10 optional
ESA24 - 1 + 1 optional

________________________________________________________
Note
NPS1 and NPS1P / NPGE and NPGEP are mutually exclusive.
_________________________________________________________

RNC2600/step 3
Configuration extension to RNC2600/step 3 can be obtained by adding
the necessary plug-in units into two subracks.
RNC2600/step 3 includes the following units:


Nokia WCDMA RNC Product Description for RNC2600

32 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Table 3. Units in RNC2600/step 3
Functional
Unit
Number of
additional
units
Total number of
units in
RNC2600/step 3
ICSU 12 38
DMCU 10 38
MXU 4 16
RSMU - 2
SFU - 2
OMU - 2
WDU - 2
OMS - 1
OMS HD - 2
EHU - 1
TBUF 4 14
TSS3 - 2
Power 2 8
NPS1 4 14 optional
NPS1P 4 14 optional
NPGE 4 14 optional
NPGEP 4 14 optional
ESA24 - 1 + 1 optional


RNC hardware management and supervision

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
33 (74)

_________________________________________________________
Note
NPS1 and NPS1P / NPGE and NPGEP are mutually exclusive.
_________________________________________________________

5.4 Capacity and reference call mix model
The maximum capacity of the different capacity steps is shown in the
table below:
Table 4. Capacity and reference call mix model
High
capacity
RNC2600 Step 1 Step 2 Step 3
Number of
subscribers 363 000 636 000 909 000
Busy hour
call
attempts 443 000 775 000 1 107 000
Erlangs 8 000 14 000 20 000
DL Iub
throughput
Mbit/s 900 1 450 2 000
Number of
carriers 1 440 2 100 2 800
Number of
BTSs 1 440 2 100 2 800
RRC
connected
mode
subscribers 88 000 152 000 200 000

The actual number of subscribers in one RNC varies depending on how
many of the subscribers are in soft handover (SHO) state. The operator
can affect this with radio network planning as well as handover and
power control parameters. The actual number of base stations
controlled by one RNC varies depending on how the Iub is configured.
RNC capacity and the number of BTSs should be calculated together
with Radio Network Planning. Transmission planning needs to be
made accordingly to match the anticipated traffic mixes used in RNW
planning.
Nokia WCDMA RNC Product Description for RNC2600

34 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Iub throughput is the traffic in downlink direction defined in FP level
and it includes 40 % handovers. Additionally 30 % DCH traffic or
HSUPA in uplink direction is supported.
The size of the Iur assumed in the dimensioning is 8% from the Iu
capacity.
RRC connected mode users include the subscribers in Cell_DCH,
Cell_FACH and Cell_PCH states.
Subscribers, BHCA and Erlangs figures are related to Voice Service
Call mix (below).

Table 5. Voice Service Call mix
Mean holding time (MHT) 1) 90s
Proportion of handovers 40%
• hard handovers 0.1 per call
• soft handovers 4.1 per call
Bearer 16 kbit/s
Traffic per user 22 mErl
NAS BHCA per user 3.7

1) MHT used generally in RNC dimensioning. The maximum BHCA values in table
Capacity and reference call mix model are calculated with the minimum MHT
supported in each configuration.The mimimum MHT is 65s.

The BHCA figure is calculated according to the following equation:
BHCA= AMR (Erl) / MHT *3600


The RNC2600 HSPA capacity figures are presented in the following
table.
Table 6. HSPA capacity figures

RNC2600
Step 1 Step 2 Step 3
Max HSDPA peak rate per UE [Mbit/s] 14
Max HSDPA peak rate per cell [Mbit/s] 14
Max HSUPA peak rate per UE / cell [Mbit/s] 5.7
HSDPA active users per cell 20
HSUPA active users per cell 20
RNC hardware management and supervision

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
35 (74)

RNC2600
Step 1 Step 2 Step 3
HSUPA active users per BTS 24
HSDPA active users per RNC 3600 6800 10 000
HSUPA active users per RNC 3600 6800 10 000
Iu-ps HSDPA net bit rate [Mbit/s] *) 810 1305 1800
Iu-ps HSUPA net bit rate [Mbit/s] *) 243 390 540
HSDPA BTS 1440 2100 2800
HSDPA carriers 1440 2100 2800
HSDPA traffic does not include softhandovers. HSUPA includes 40 %
softhandover overhead in Iub.
*) On top of GTP-U layer.
HSPA traffic is using shared channel where the peak rate throughput is
shared by all users in the same cell. In case the number of user s
transmitting data simultaneously increases, the average throughput per
user decreases.

The table below displays the type and the number of interfaces
supported by different configurations of the RNC2600. The interfaces
can be configured flexibly according to operators' requests and capacity
needs.

Table 7. Interfaces
RNC2600
STM-1
non-protected
STM-1
protected
Gigabit
Ethernet
non-
protected
Gigabit
Ethernet
protected
step 1 48 24+24 12 6+6
step 2 80 40+40 20 10+10
step 3 112 56+56 28 14+14

STM-1 and Gigabit interfaces are mutually exclusive. There can be
also both STM-1 and Gigabit Ethernet interfaces in the same RNC.


Nokia WCDMA RNC Product Description for RNC2600

36 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

5.5 Traffic mix rule
In the mixed traffic the sum of relative loads of the three traffic types
(AMR, CS and PS) over the Iu-interface has to be less than or equal to
1. Relative load means dividing the offered traffic by the maximum
allowed traffic value:

CS data is calculated according to the following rule:
CS data (Mbps) ≤ 25% of max Iub throughput
PS data in the equation includes R99 PS data and HSPA.


RNC hardware management and supervision

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
37 (74)

6 RNC hardware management and
supervision
The hardware management system (HMS) provides a duplicated serial
bus between the 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 HMS master node.
The HMS is used in supporting auto-configuration, collecting fault data
from plug-in units and auxiliary equipment, collecting condition data
external to network elements and setting hardware control signals, like
restart and state control in plug-in units.
The hardware management system is robust. For example, it is
independent of system timing and it can read hardware alarms from a
plug-in unit without power.
It allows power alarms and remote power on/off switching function.
The hardware management system forms a hierarchical network, see
the figure below. The duplicated master network connects the master
node with the bridge node of each subrack. The subrack level networks
connect the bridge node with each plug-in unit in the subrack.
Nokia WCDMA RNC Product Description for RNC2600

38 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en



Figure 9. The logical structure of the hardware management system
RNC2600 reliability

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
39 (74)

7 RNC2600 reliability
The RNC is designed to be fault tolerant, and great attention is paid to
the reliability of operation. All centralised functions of the system are
protected in order to guarantee high availability of the system.
Hardware and software of the system are constantly supervised. When
a defect is detected in an active functional unit, a spare unit is activated
by an automatic recovery function.
The RNC is designed to meet the availability requirements of the ITU-
T. Simplicity and speed of maintenance procedures are the
prerequisites for the availability of the RNC. The maintenance is
improved by modularity of the equipment, automatic fault detection
procedures and elimination of downtime by using a hot standby unit in
the event of a failure. The following general design objectives have
been established for the maintenance of the RNC:
• mean active repair time less than half an hour
• fault localisation with the accuracy of one plug-in unit for 70 %
of the faults
• fault localisation with the accuracy of four plug-in units for 95
% of the faults
Nokia WCDMA RNC Product Description for RNC2600

40 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

7.1 Reliability from the maintenance point of
view
Mean down time (MDT)
The expectation of the time interval during which an item is in a down
state and cannot perform its function. MDT concerns only failures due
to exchange (or unit) itself.
Mean active repair time (MRT)
MRT is the expectation of that part of the active corrective
maintenance time during which repair actions are performed on an
item, for example, to replace a faulty unit in the network element.
Availability
Availability means the probability that an item is in a state to perform a
required function under stated conditions at a given instant of time,
assuming that the required external resources are provided.
The maintenance aspect of reliability comprises all failures demanding
repair whether they affect the functionality of the system or not. The
calculations only concern hardware failures. The following MTBF
values are calculated for the example system configurations. The
values below are presented strictly from the maintenance point of view
describing how often plug-in units fail and have to be replaced. The
tables below include all optional features.
Failure rates are calculated using the 'parts count' method. This means
that the failure rate of the network element is calculated by summing
up the failure rate values of the plug-in units.
The tables presented below are predictions based on preliminary
calculations. These predicted values cannot be used as guaranteed
values in contractual commitments (the availability calculations
exclude the OMS unit).
Table 9. Predicted MTBF for HW repair from the maintenance point of
view
RNC system configuration MTBF
RNC one cabinet 5000
RNC two cabinets 10 000


RNC2600 reliability

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
41 (74)

Note that the useful life of a fan tray (FTRA) is shorter than the useful
life of plug-in units in general. Therefore, fan trays should always be
changed for new ones before the end of their life expectancy.
7.2 RNC availability performance
Availability performance calculations describe the system from the
availability point of view presenting availability, mean operating time
between system failures and mean down time values. The availability
performance calculations are based on mathematical modelling and
they are calculated using reliability block diagrams of the system, plug-
in unit failure intensities, maintainability data and the rules of
probability theory. Mathematical models are implemented using a
reliability analysis tool.
Availability performance values are calculated for the complete system,
that is, redundancy principles are taken into account. The system is
considered to be operating successfully if at least half of its traffic
handling capacity is in use. It is also assumed that component failure
rates are constant. If temporary unavailability of a functional block
does not affect the call processing capability of the exchange, such
functional blocks are not taken into account in the availability analysis.
In reference to ITU-T Recommendation Q.541, intrinsic unavailability
is the unavailability 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 spare units, and so on) and planned outages.
Thereby, when intrinsic availability performance values are calculated,
only the active repair time (assumed to be 1.0 h) is taken into account.
In practice, the real active repair time is often well below the above-
mentioned one hour.
The results of the availability performance calculations for the
complete system are presented in the table below. The figures are
predictions based on preliminary calculations (the availability
calculations exclude the OMS unit).

Table 10. Predicted availability performance values

Nokia WCDMA RNC Product Description for RNC2600

42 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

7.3 Redundancy principles
The RNC provides a set of services to support redundancy. The
following function protection schemes are applied for various units:
Duplication (2N)
If the spare unit is designated for only one active unit, the software in
the spare unit is kept 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 called duplication,
abbreviated "2N".
Replacement (N+1)
For less strict reliability requirements, one or more spare units may also
be designated to a group of functional units. One spare unit can replace
any unit in the group. In this case the execution of the switchover is a
bit slower, because the spare unit synchronisation (warming) is
performed as a part of the switchover procedure. The spare unit is in
cold standby. This redundancy principle is called replacement,
abbreviated "N+1"
Load sharing (SN+)
A unit group may 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 extra capacity. If a few units of the pool are
disabled because of faults, the whole group can still perform its
designated functions. This redundancy principle is called load sharing,
abbreviated "SN+"
None
Some functional units have no redundancy at all. This is because a
failure in them does not prevent the function or cause any drop in the
capacity.
To guarantee high availability, the core functional units of the system,
that is, the SFU and MXUs, are redundant. Hard disks and buses
connecting them to the control units are always duplicated.
The distribution of the basic timing signal for active and backup units
comes from different or redundant DC/DC converters and their basic
timing signals are taken from different distribution lines.
RNC2600 reliability

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
43 (74)

Table 11. Functional unit redundancies

Functional Unit Redundancy principle
DMCU SN+
EHU None
ICSU N+1
MXU 2N
OMS None
OMU 2N
RSMU 2N
SFU 2N
TBU 2N
WDU 2N
OMS HDD 2N
NPS1 None
NPGE None
NPS1P 2N (MSP 1+1 / APS 1+1)
NPGEP 2N (MSP 1+1 / APS 1+1)


Redundancy of the power distribution system
The power feed is protected by duplicated power supply from rectifiers
or batteries. At cabinet level, duplicated battery voltage is distributed
via magnetic circuit breakers (MCB) to every subrack in the same
cabinet. At subrack level, duplicated power supply line is received by
PD30 (see section Power supply in RNC2600 power requirements)
which distributes four duplicated 5A power feed lines to the plug-in
units via the backplane.
Nokia WCDMA RNC Product Description for RNC2600

44 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Redundancy of the forced cooling system
Each subrack and fan tray (FTRA-B) connected perform separate
thermal circuits, which means that a failure in one subrack cooling
system does not affect other subracks cooling systems. The FTRA-B is
supervised and controlled via a PD30 plug-in unit. In case of a failure
in an FTRA-B control and supervisory block in PD30, individual
subrack forced cooling is not functioning or it is partly functional. Each
FTRA-B is protected by N+1 redundancy. In case of single fan failure,
operational fans are controlled to full rotation speed maintaining
sufficient cooling capacity in specified environmental conditions.

Timing and synchronisation

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
45 (74)

8 RNC2600 physical interfaces
Network interfaces provide external interfaces and the means to
execute physical layer and ATM layer functions, such as policing,
statistics, OAM, buffer management and scheduling. Network
interfaces map ATM cells to transmission frame structure of
synchronous digital hierarchy (SDH).
In case of IP transport QoS functionality, O&M, statistics are handled
in IP level and IP packets are mapped in to the Ethernet frames.
One network interface unit may include one or more physical interfaces
depending on the type of interface. Any interface can be configured to
be used as an Iu, Iub, or Iur interface.
In addition to the network interfaces, synchronisation interfaces and
local area network (LAN) interfaces are provided.
STM-1/OC-3
Functional unit NPS1 or NPS1P offers ATM over SDH/SONET
network interface. NPS1P uses MSP 1+1 and APS 1+1 protection.
Single plug-in unit type NP8S1-B is utilised by NPS1 and NPS1P-A
plug-in unit contains eight SDH STM-1 (optical) interfaces.

Table 12. STM-1/OC-3 interface specifications
Interface type
STM-1 optical S-1.1 ITU-T G.957, table
1
OC-3 IR-1 ANSI T1.105.06
Nominal Wavelenght 1310 nm
Distance < 15 km
Medium ITU-T G-652 optical fibre (SM)
Connectors LC
Bit rate 155 520 kbit/s
Transmission path
VC-4
STS-3c
Specification
ITU-T I.432.2 / G.707
ANSI T1.646-1995
Nokia WCDMA RNC Product Description for RNC2600

46 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Jitter and wander
ITU-T G.825, G.958
T1.105.03
Number of interfaces per unit 8

_________________________________________________________
Note
OC-3c, an abbreviation used in some texts for OC-3 with STS-3c
transmission path, is supported.

Gigabit Ethernet
Functional unit NPGE or NPGEP offers IP over Ethernet interfaces.
NP2GE supports 2N redundancy
Single plug-in unit type NP2GE is utilised by NPS1 and NPS1P. A
plug-in unit contains two GE (optical or elecrical) interfaces.


Table 13. Gigabit Ethernet interface specifications
Interface type
Optical 1000Base-LX
Electrical 1000BASE-T
Nominal Wavelenght 1100 … 1600 nm (optical)
Medium
Optimized for 10µm single-mode cable,
but also multi-mode cables can be used
for short operating distances.
Connectors
LC
RJ-45
Bit rate 1000 Mbit/s
Specification
Optical: IEEE802.3z
Electrical: ISO/IEC 11801:1995 and
ANSI/TIA/EIA-568-A:1995
Number of interfaces per unit 2


8.1 Synchronisation interfaces
A synchronisation interface for external timing reference signals is
provided. An external timing output (2.048 Mbit/s only), which can be
used to transmit either system clock or one of the timing reference
signals extracted from network interface units, is also provided.
Table 20. Synchronisation interface
Timing and synchronisation

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
47 (74)



Nokia WCDMA RNC Product Description for RNC2600

48 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

8.2 LAN/Ethernet for O&M connections
The local area network interface functions at the rate of 10/100 Mbit/s
using an RJ45 connector located in the front panel. The maximum data
transfer rate of each Ethernet interface is 100 Mbit/s full duplex.
Table 21. LAN interface specifications


RS232 service terminal
The RS232 interface using RJ45 connector is located in the front panel
of the plug-in unit. The interface is used for debugging and as a service
terminal.

Timing and synchronisation

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
49 (74)

8.3 Timing and synchronization
The RNC can be connected to existing synchronisation networks. The
network element synchronisation and timing is designed to work in a
master/slave network synchronisation scheme and hierarchical
synchronisation network topology. The network element has an internal
clock that can operate even when external timing references are lost.
The network element synchronisation includes functions such as
selection, extraction, synchronisation and timing signal distribution to
the network element components. Almost all of these functions are
redundant to make the system reliable and fault tolerant. RNC supports:
External timing
External timing reference signal can be selected from a number of
possible inputs (E1, 2048 kbit/s, 1544 kbit/s or 64+8 kbit/s). The
synchronisation unit also provides an external timing output (2048
kbit/s only), which can be used to transmit either system clock or one
of the timing reference signals extracted from the network interface
units.
Line timing
The synchronisation unit has three timing inputs that are connected by
cabling to three selected network interface plug-in units. The system
clock can be synchronised to the SDH/Sonet network by detecting the
signal from incoming STM-1/OC-3 line. In the network interface plug-
in unit one of the STM-1/OC-3 ports is selected to give timing.With
this configuration at least three timing inputs from upper network level
can be made available. Line timing is also supported on E1/T1
interfaces.
The network element has one duplicated synchronisation unit. This unit
takes as input a timing signal from the upper network level. It adjusts
its local oscillator to the long time mean value by filtering jitter and
wander from the timing signal. It then delivers this synchronised timing
signal as system timing to other timing units and further to all plug-in
units of the system.
Nokia WCDMA RNC Product Description for RNC2600

50 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

The synchronisation unit delivers synchronised system timing signal
(system clock) with separate cables to every cabinet. In each subrack
TSS3/TBUF plug-in units receive the signal, reshape it and send it via
the backplane bus to all other plug-in units in the subrack. If there is no
external signal, the TSS3 plug-in unit can independently generate the
clock signals necessary for synchronising the functions of the network
element (as illustrated in the figure below). Timing distribution from
the synchronisation unit to other plug-in units is duplicated and the
timing signal selection is made in the plug-in units.


Figure 10. RNC synchronisation and distribution of timing signal
Monitoring the quality of the received timing from SDH/Sonet
transmission system and stating the control of synchronisation is
performed in the network element management. Functionality and
performance of the synchronisation and the timing are compliant with
ETS 300 462 series standards and ITU-T recommendations G.783
and G.825.
The network element fulfils Stratum 3 level accuracy requirement as
defined by Bellcore TA-NWT-1244.

RNC2600 power requirements

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
51 (74)

9 RNC2600 mechanical design
The RNC mechanics fulfil the ETSI 300 119-4 standard and IEC 917
series standards for metric dimensioning of electronic equipment.
The RNC mechanics comprise the basic mechanics concept based on
the NEBS-2000 standard.
The concept supports the RNC architecture, which allows modular
scalability of configurations varying from modest to very large
capacity. It also allows the performance to be configured using only
few hardware component types.
The mechanical structure is hierarchical, based on plug-in units,
subracks and cabinets. The RNC is easy to install, operate and
maintain. Special attention has been paid to thermal resistance and
immunity to various types of interference.
The mechanics consist of the following equipment:
• cabinet mechanics
• 19-slot subrack, its backplane and front plate mechanics
• connector and cabling system
• cooling equipment
The mechanics concept includes description of cabinets, subracks,
plug-in unit mechanics, connector system, interconnection cabling
system, requirements for environmental conditions (climate,
earthquake and transportation stress), EMC performance and safety
considerations.
Nokia WCDMA RNC Product Description for RNC2600

52 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en



Cabinets
The dimensions of the cabinet are given in the table below. They are
based on standard ETS 300 119-2 and IEC 917-2.
RNC2600 power requirements

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
53 (74)

Table 19. Cabinet dimensions
RNC2600 RNC2600 RNC2600 RNC2600 RNC2600 RNC2600 RNC2600 RNC2600


Cabinet power distribution equipment and four subracks with cooling
equipment can be installed in one cabinet. Openings in the sides of the
cabinet behind the subrack backplanes allow direct horizontal cabling
between cabinets. Openings on the top and bottom of the cabinet are
needed for conducting cables.
Subracks
The subrack mechanics consist of a subrack frame, backplane and front
plate forming electromagnetic shielding for electronics to fulfil EMC
requirements. The basic construction allows dividing a part of a
subrack vertically into two slots with optional guiding mechanics for
the use of half-height plug-in units.

Table 20. Subrack dimensions
Nokia WCDMA RNC Product Description for RNC2600

54 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Plug-in unit
The RNC is constructed by using a total of approximately 14 plug-in
unit types. The basic mechanical elements of the plug-in units are PCB,
connectors and front plate mechanics. Front plate mechanics include
insertion/extraction levers, fixing screws and EMC gasket.
Table 21. Plug-in unit dimensions




RNC2600 power requirements

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
55 (74)

Backplanes and cabling
The backplane and cabling system provides reliable interconnections
between plug-in units. In addition, the backplane provides EMC shield
to the rear side of the subrack. The cabling shielding system enables
EMI free interconnection path to signals. The AMP Z-pack HM
connector concept provides a reliable plug-in unit interconnection,
fastening to the backplane and cabling system in a demanding
environment.
Common signals are delivered through the backplane, and all other
interconnection signals are connected via cabling. This provides
backplane modularity and flexibility in different configurations.
Because of flexible cabling and redundancy, it is possible to scale the
system to a larger capacity in an active system without shutting down
the whole system.
Standard length cables are used for the internal cabling of the RNC.
These cables have been manufactured at the factory and are equipped
with connectors.
The network interface cables and other station cables of the RNC enter
the exchange room via a cable conduit. They enter the cabinet via
grounding elements placed on top and bottom of the cabinets. These
cables are attached to the connectors on the front panels of the plug-in
units. The power supply cables are terminated to the power
supplyconnector on top and bottom of the cabinet.
Nokia WCDMA RNC Product Description for RNC2600

56 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

10 RNC2600 power requirements
Power supply
Reliability, easy installation and easy maintenance have been the main
objectives in the design of the power feed system of the RNC.
The power feed forms a hierarchical system with function and overload
protection on every level. Protection is implemented by duplicating
power feed equipment from the battery feed to the plug-in units.
Nominal battery voltage is - 48 V.
Battery voltage is fed to the cabinet via the terminal block and circuit
breaker unit. Grounding 0V of the battery voltage in this unit is
possible but floating battery voltage with separate grounding cable can
also be used. Separate duplicated 30A power feeds to every subrack are
protected by circuit breakers. Eight fuses (two per subrack for
duplicated power feed) are installed in the front plate of the cabinet
power distribution unit.
A differential filter for duplicated battery voltage feed resides in the
power distribution plug-in unit in the subrack. The power feed in the
subrack is divided into four 10A groups, each having its own fuses in
the power distribution plug-in unit. The power feed of the fan tray
(FTRA-B) and the fan speed control circuit also reside in the power
distribution plug-in unit.
Each plug-in unit has a DC/DC converter unit that generates desired
voltages to electronics. Duplicated battery voltage is connected via
diodes to a low-pass filter and fuse to a DC/DC unit, which consists of
one or more converters depending on the need for different voltages.
Switches setting converters on and off can be separate or integrated
into converters. The power-up circuit and the hardware management
system (HMS) node control the switches. The HMS node supervises
battery voltages, the fuse and all the generated voltages.
RNC2600 power requirements

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
57 (74)



Figure 13. The protection schema and the protection areas of various protective
devices

Table 22. Power supply


Power supply cables
Power supply cables can be fed from top or bottom of the cabinet regardless ofthe
location of the CPD120.
Nokia WCDMA RNC Product Description for RNC2600

58 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Table 23. Power supply cables


Power consumption
If the maximum number of plug-in units is installed, the power consumption in each
subrack is the following:
The PD30 plug-in unit is a common unit with two supply branches in the subrack. If
one branch supplies all the current (that is, the other branch is not in use), the
maximum current in this branch is 30 A. The largest power which it can deliver
when voltage is at the lowest level (40,5 V) is about 1200W. When both branches
are in use, the current levels are below 20 A in each branch.
The power consumption of the cabinet types at the maximum traffic load is:

Table 24. Power consumption estimate
Property Value
First cabinet 3 kW
Second cabinet 3 kW

The power consumption for site planning of RNC2600 is:

Table 25. Power consumption
RNC2600 power requirements

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
59 (74)

These latter figures assume maximum power consumption in all HW components
simultaneously, which does not occur in normal operation under any load.
Grounding
The cabinet supports two grounding site (connection of protective earthing (PE) to
the common bonding network) principles.
Grounding using a dedicated PE conductor from the cabinet to the common bonding
point of the site, according to ITU-T K27 and Mesh-IBN.
Grounding using the DC-return conductor according to ETS 300 253. The cabinet
PE terminal can be connected to the purpose reserved Neutral (N) terminal at the
CPD80 unit.

___________________________________________________________________
Note
Cables used in grounding should be at least 50 mm2 . These cables are not included
in R&D equipping sets, and they are considered site installation equipment.
NEBS-compatible systems need to use common bonding network (CBN) grounding.
___________________________________________________________________
Nokia WCDMA RNC Product Description for RNC2600

60 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en



Figure 14. Grounding principle
RNC2600 operating environment

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
61 (74)

11 RNC2600 operating environment
11.1 Equipment room
The RNC can be flexibly co-sited in the core network. It can be
installed as a stand-alone network element at a remote site, for
example, at the same site as one of the base stations (BTS) it controls.
The following table gives the requirements for the equipment room.

Table 26. Equipment room


_________________________________________________________
Note
The mechanical structure of the RNC does not set any special
requirements on the ceiling, walls or floor. No raised floor is needed.
_________________________________________________________
Nokia WCDMA RNC Product Description for RNC2600

62 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en


When planning the location of the RNC, notice also the following:
• future expansion of the RNC
• standard lengths of the cables between the cabinets
• location of other equipment at the same site
• air-conditioning of the equipment room
• sufficient working space around the cabinets


Figure 15. Floor layout of a one-cabinet RNC2600
11.2 Cooling of the cabinets
The cabinets contain air deflectors to help cooling. The fan tray
(FTRA) units give additional cooling effect to the equipment installed
in the cabinet. The fan trays are supervised and controlled by the
Hardware Management System.
RNC2600 operating environment

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
63 (74)


The temperature of the air in the equipment room must be within the
limits of the recommendations (refer to Environmental conditions). For
safety reasons, the exchange room layout and the ventilation system
used should be designed so that the temperature in the premises stays
between +10 and +35 °C, unless peripheral and measuring devices are
used which require adherence to even stricter limits.
The figure below illustrates the cooling air flow.

Figure 16. Cooling air flow

11.3 Operating temperature and humidity
tolerances
Changes in temperature and relative humidity affect the reliability of the
equipment. The relationship between the availability, performance and the
Nokia WCDMA RNC Product Description for RNC2600

64 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

environment is defined in the climatogram in the figure below.

Figure 17. Climatogram of the RNC


Table 27. Environmental requirements


RNC standards

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
65 (74)

12 RNC standards
The tables list the standards with which the Nokia RNC complies.
In addition, the RNC meets the requirements described in CAU
100471, Type Approval and System Test Requirements, Environmental
Specifications, DX200 and IPA2800 Hardware.
12.1 EMC standards

12.2 Power feed



Nokia WCDMA RNC Product Description for RNC2600

66 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en




12.3 Grounding and bonding

12.4 Environmental durability

RNC standards

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
67 (74)


12.5 Earthquake

12.6 Interfaces

155 Mbit/s SDH STM-1, SONET OC-3
Standard Description
ITU-T, G.707, 12/03 Network node interface for the
synchronous digital hierarchy (SDH)
ANSI T1.646-1995 B-ISDN User-Network Interfaces Rates
and Formats Specifications

Gigabit Ethernet
Standard Description
ISO/IEC 11801:1995 Information technology — Generic cabling
for customer premises
ANSI/TIA/EIA-568-A:1995 Commercial Building Telecommunications
Cabling Standard
IEEE802.3z 1000 Mbps Ethernet


Nokia WCDMA RNC Product Description for RNC2600

68 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Service Terminal interface RS232

12.7 Environmental conditions
The requirements are based on market area assumption: EEA countries,
Japan and the USA.


RNC standards

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
69 (74)



12.8 Legislation
The requirements are based on market area assumption: EEA countries,
Japan and the USA.



Nokia WCDMA RNC Product Description for RNC2600

70 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en



12.9 Electromagnetic environment
The RNC is compliant with the European EMC directive 89/336/EEC.
12.10 European Union RoHS Directive
Nokia Radio Network Controller complies with the European Union
RoHS Directive 2002/95/EC on the restriction of the use of hazardous
substances in electrical and electronic equipment. The directive applies
to the use of lead, mercury, cadmium, hexavalent chromium,
polybrominated biphenyls (PBB), and polybrominated diphenyl ethers
(PBDE) in equipment put on the market after 1 July 2006.



RNC eco-efficiency

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
71 (74)

13 RNC eco-efficiency
In the RNC design project, a design for environment (DFE) is included
in the product creation process. The basis for the DFE is to implement
life cycle-based thinking. The concrete measures, which have both
ecological and economical value and are called eco-efficiency, include
the following:
• minimising energy intensity
• minimising material intensity
• minimising toxic dispersion
• enhancement of recyclability
• extension of product durability
Concrete examples of eco-efficiency include:
• Nokia designed plastic parts weight > 20 g are marked
according ISO standard
• hexavalent (=6) chromium is forbidden as surface treatment
Modularity, reliability and upgradability as well as remote management
all support eco-efficiency principles.

Nokia WCDMA RNC Product Description for RNC2600

72 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

Related topics

dn0628405
Issue 8 en
# Nokia Corporation
Nokia Proprietary and Confidential
73 (74)

14 RNC site equipment
The site equipment is not included in the normal RNC delivery. For
more information, please contact a local Nokia area organisation.
Battery back up
Definitions of battery back up and order instructions can be found at
Nokia site solution services.
Optional RNC site O&M peripheral devices
In normal operation, Nokia OSS will provide remote operation and
maintenance (O&M) for the RNC. If local O&M is needed, it is
recommended to install one peripheral device per site. The equipment
is standard and can be ordered by the customer either from a local store
or via a local Nokia area organisation.
External hardware alarm lamp panel (EXAU) (Optional)
RNC network faults can be indicated on a lamp panel in the
telecommunication site room. The connector panel of external alarms is
located at the rear site of the RNC A cabinet.
The RNC must have an external HW alarm unit (EHU) installed for the
lamp panel to work.
Printer
A printer can be connected to the OMS. An optional printer (not
included in the RNC delivery) can be connected to the RNC via a LAN
interface.
Nokia WCDMA RNC Product Description for RNC2600

74 (74)

© Nokia Corporation
Nokia Proprietary and Confidential
dn0628405
Issue 1 en

OMS service kit
• Keyboard, mouse, monitor and single USB cable
Standard USB mouse, monitor and keyboard are optional for
local O&M operation (also local commissioning) if a PC is
not available on site. This arrangement can also be used for
installing software to the OMS. The keyboard, mouse,
monitor and USB interfaces are implemented with the same
standard used in PCs. A single USB cable is needed for one
keyboard/mouse connector.
• External USB DVD-ROM drive and cable
A USB DVD-ROM drive is used when installing software on
the OMS if a remote connection to OSS is not available.


Standard PC
For local maintenance purposes, a local laptop or PC is required with
Red Hat Linux operating SW. A LAN card has to be connected to the
PC.

[plaosan]

what's the mean bro?where is the attachment?