Evolium A9140 RNC Evolution Description 211310000e05

8/12/2019 Evolium A9140 RNC Evolution Description 211310000e05

1/100

Alcatel UMTS

Evolium A9140 RNC Evolution

Description

RNC Document

Sub-System Description

Release R5 from MR3

3BK 21131 AAAA TQZZA Ed.05


2/100

Status RELEASED

Short title N/A

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel.

BLANK PAGE BREAK

2 / 100 3BK 21131 AAAA TQZZA Ed.05


3/100


4/100

Contents

4.2.3 M-OMP Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.2.4 Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.3 M-CM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.3.1 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.3.2 M-CM Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.3.3 M-CM Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.3.4 Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.4 M-XWY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4.4.1 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.4.2 M-XWY Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.4.3 M-XWY Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.4.4 Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4.5 M-SIFMB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.5.1 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.5.2 M-SIFMB Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.5.3 M-SIFMB Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.5.4 Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.6 M-XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.6.1 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.6.2 M-XP Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.6.3 M-XP Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.6.4 Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

4.7 M-FANU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.7.1 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.7.2 M-FANU Top View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.7.3 M-FANU Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.7.4 Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.1 Control Part Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.1.1 Control Part Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.1.2 Platform Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.1.3 Application Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.2 Application Part Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

5.2.1 Operation and Maintenance Functional Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.2.2 Telecom Functional Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

5.3 Software Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745.3.1 Downloaded Software (D-SW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745.3.2 Office Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5.4 PLD and FPGA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

6 Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786.1.1 OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

6.1.2 NEM-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796.2 Equipment Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806.2.1 Fault Detection and Reporting Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806.2.2 Board State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816.2.3 Board Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816.2.4 Fault Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826.2.5 Board Lock Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

6.3 Diagnosis and Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.3.1 Power-up Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.3.2 Automatic Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.3.3 Manual Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846.3.4 Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6.4 Hard Disk Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

6.5 System Defence Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

4 / 100 3BK 21131 AAAA TQZZA Ed.05


5/100


6/100

Figures

Figures

Figure 1: RNC Ev Rack Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Figure 2: RNC Ev Rack Side View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Figure 3: RNC Ev Rack Top View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

6 / 100 3BK 21131 AAAA TQZZA Ed.05


7/100


8/100

Preface

In Edition 01

First official release of document.

Audience The guide is intended for:

Commissioning personnel

Support and service engineers

OMC-R operators

Training personnel.

Assumed Knowledge The reader must have a general knowledge of UMTS.

8 / 100 3BK 21131 AAAA TQZZA Ed.05


9/100

1 Functional Description


This section describes the general architecture and each function of theEvolium A9140 RNC Evolution.

3BK 21131 AAAA TQZZA Ed.05 9 / 100


10/100


11/100


The connection diagram of the RNC Ev is illustrated below.

MCONT shelf

ML1L2 shelf

revd056

Node B

Core

Network

MSIFMB

MXP

[ESU]

MXP

[MSU]

MXP

[SPU]

MXP

[DHT]

MXP

[MMUX]

MXWY

OMCR

MOMP

MCP

MXWY

MCM

RNC Ev

1.2 Interface Architecture

1.2.1 External Interfaces

The external RNC Ev interfaces are illustrated below:

Node B

OMCR

Core

Network

LMT

(NEMR)

Iub

RNC Ev

O&M interface

(STM1/Ethernet)

(E1) (STM1)

Node B

RNC Ev

(E1) (STM1)

Iub

Iu (STM1)

Iur (STM1)

Iur (STM1)

Iu (STM1)

O&M interface

(Ethernet)

Transmission

system

revd046

Node B(STM1)

Node B

(STM1)

IMA

(E1)

Iub

Iub

Local Iur (STM1)

3BK 21131 AAAA TQZZA Ed.05 11 / 100


12/100


The following table describes each external interface:

ExternalInterface

Description

RNC Ev-Node B

interfaceThe interface between the RNC Ev and the Node B (the Iub interface) uses ATM.

The RNC Ev supports an STM-1 optical interface. The Node B supports an E1 link

with/without IMA and an STM-1 optical interface. A transport system is required

for interworking in case of an E1 link.

Control signal and user information (voice and data) is sent and received in an

ATM cell.

RNC Ev-CoreNetwork interface

The interface between the RNC Ev and the Core Network (the Iu interface) uses

ATM. The RNC Ev supports an STM-1 optical interface.


ATM cell.

RNC Ev-RNC Evinterface

The interface between two RNC Evs (the Iur interface) uses ATM. The RNC Ev

supports an STM-1 optical interface.


ATM cell.

There are two Iur connection types:

Through the Core Network via STM-1

Direct connection between RNC Evs via STM-1 (local Iur).

RNC Ev-LMTinterface

The interface between the RNC Ev and the LMT uses an Ethernet link. The RNC

Ev can be connected to the LMT either locally or remotely.

RNC Ev commissioning and local maintenance are performed using the LMT.

RNC Ev-OMC-Rinterface

The OMC-R and the RNC Ev are connected via the:

M-SIFMB STM-1 interface

M-XWY 10 / 100BaseT interface.

12 / 100 3BK 21131 AAAA TQZZA Ed.05


13/100


1.2.2 Internal Interfaces

1.2.2.1 I/O Bus Interface

The I/O bus between boards communicates in the TCP/IP layer of the Ethernet.

The TCP link setting and the IP address setting of each board are processed

on system restart. The I/O bus of the Ethernet network operates using I/Omessages.

Ethernet technology is used for the RNC Ev internal data highway. The M-XWYboard performs a layer 2 role, switching communications between RNC Evboards.

The I/O bus is used to:

Exchange the control/response packets between M-CPs/M-OMPs and

other RNC Ev boards

Send the reporting packets to the M-CPs/M-OMPs.

MCONT Shelf

I/O bus(Ethernet 10Gbps)

MOMP

#P

MXWY

#R

MXWY

#P

MCM

#P

MCM

#R

MOMP

#R

revd041

I/O bus(Serdes 1.08Gbps)

MCP

#0#9

MCP

#16#25

ML1L2 Shelf

MSIFMB

#10

MXWY

#R

MXWY

#P

MSIFMB

#15

I/O bus(Serdes 1.08Gbps)

MXP

#0#7

MXP

#18#25

I/O bus(Ethernet 10Gbps)

1.2.2.2 ATM Cell Interface

ATM cells are also used to send and receive user data. However, to transferthis information through the Ethernet together with the I/O bus data, one ATMcell is encapsulated in one Ethernet frame. U plane traffic routing does notuse the TCP/IP layer. To perform the I/O bus communication, private MACaddresses are used within the RNC Ev.

3BK 21131 AAAA TQZZA Ed.05 13 / 100


14/100


1.2.2.3 SV Bus Interface

The SV bus collects the status of boards and controls boards using resets andACT instructions. Board status provides information on:

Condition

Inventory

Faults.

The SV bus is located in the M-CONT shelf and in the M-L1L2 shelf. Each shelfhas two M-XWY boards and two SV bus lines as illustrated in the followingfigure. One SV bus line of the ACT M-XWY board works as a master and theother SV bus line is in SBY mode and works as a slave.

The status information collected in the M-L1L2 shelf is carried to the ACTM-XWY board in the M-CONT shelf through the I/O bus line between theM-L1L2 and the M-CONT shelves. The information collected from the boards iscarried to the ACT M-OMP board in the M-CONT shelf, via an I/O message

through the I/O bus line between the ACT M-XWY and M-OMP boards.

MCONT shelf

MOMP

(ACT)

MOMP

(SBY)

MCP

#0#9

#16#25

MCM

#P, #R

revd042

MXWY

(ACT)

MXWY

(SBY)I/O message

SV bus

SV bus

ML1L2 shelf

MXP

#0#7

#18#25

MSIFMB

#10, #15MXWY

(ACT)

MXWY

(SBY)

SV bus

SV bus

14 / 100 3BK 21131 AAAA TQZZA Ed.05


15/100


16/100


1.2.3 Reference Clock

The M-XWY performs RNC Ev reference clock management:

ACT M-OMP has all the selection information of the external reference clock

on the M-SIFMB / M-XWY boards. This information is transmitted from the

ACT M-OMP board to each M-XWY / M-SIFMB board as an I/O message.

The M-SIFMB software selects one line used for the reference clock from

among four STM-1 lines according to the I/O message from ACT M-OMP,

and transmits it to M-XWY.

The M-XWY software selects an M-SIFMB board used for the external

STM-1 reference clock according to the I/O message from ACT M-OMP,

and the M-XWY board transmits the timing to M-XWY in the M-CONT

shelf. M-XWY in the M-L1L2 shelf distributes the timing to each M-XP

/ M-SIFMB board.If the external STM-1 reference clock fails, an available, registered STM-1

reference line is selected. The local clock is used only if every registeredSTM-1 reference line fails.

Core

Network

MSIFMB

MXWY #RMXWY #P

MXWY #RMXWY #P

ML1L2 shelf

MCONT shelf

MOMP

(ACT)

OMCR

RNC

Node B

Re erence clock

revd043

: Reference clock collection

: Reference clock distribution

: I/O message

16 / 100 3BK 21131 AAAA TQZZA Ed.05


17/100


1.3 RNC Ev Function Blocks

The RNC Ev is managed on a function block basis. The following figureillustrates the relationship between the function blocks and the hardware:

The RNC Ev reports the status of the function blocks to the OMC/NEM-R.

RNC Ev

Interface FB

OMCR

Clock Distribution Interface

RNSO&M Routing

ROUTING[MXP]

Ethernet Switching

ETHSW[MXWY]

Processing FB

Telecom FB

CallPRC[MCP]

OAMPRC[MOMP]

GM

[MCM]

ESU[MXP]

MSU[MXP]

MMUX

[MXP]

DHT[MXP]

SPU[MXP]

Node B

CN

DCI[MXWY]

CNIF[MSIFMB]

revd036

RNCIF[MSIFMB]

Node BIF[MSIFMB]

OMCIF[MSIFMB][MXWY]

RNC Ev

1.3.1 Processing Function Blocks

FunctionBlock Name Supported by Description

Call-PRC M-CP in M-CONT shelf Processing capability for RNC Ev call control functions.

OAM-PRC M-OMP in M-CONT shelf Processing capability for RNC Ev operation and

maintenance control functions

Configuration function support via Office Data

management

Storage capability for performance measurement, trace,

and diagnostics files.

GM M-CM in M-CONT shelf Global memory for the:

Call processing

Operation and maintenance processing.

3BK 21131 AAAA TQZZA Ed.05 17 / 100


18/100


1.3.2 Interface Function Blocks


CN-IF M-SIFMB in M-L1L2 shelf ATM access over STM-1 to the Core Network.

Node B-IF M-SIFMB in M-L1L2 shelf ATM access over STM-1 to all Node Bs.

RNC-IF M-SIFMB in M-L1L2 shelf ATM access over STM-1 to all RNC Evs.

M-SIFMB in M-L1L2 shelf ATM access over STM-1 to a router for RNS (RNC Ev andall Node Bs) operation and maintenance traffic.

OMC-IF

M-XWY #P in M-CONT IP interface for RNS operation and maintenance traffic.

1.3.3 Telecom Function Blocks


ESU M-XP (ESU role) in M-L1L2 shelf MTP3b and SAAL NNI for an interface to the

circuit-switched Core Network.

MTP3b and SAAL NNI for an interface to other

RNC Evs.

Layer 2 links (SAAL-UNI): One for ALCAP and

one for NBAP for all Node Bs connected to the

RNC Ev.

MSU M-XP (MSU role) in M-L1L2 shelf RLC/MACd for UE-dedicated signaling functions.

MMUX M-XP (MMUX role) in M-L1L2 shelf MACc/sh protocol handling for all cells controlled

by the RNC Ev and the RLC for common channel

handling.

Frame clock management

Handling of the paging function transport

channels (PCH).

DHT M-XP (DHT role) in M-L1L2 shelf The MACd diversity handover function for DTCHand DCCH channels

SPU M-XP (SPU role) in M-L1L2 shelf DTCH (PS) and GTP for a packet interface to SGSN.

18 / 100 3BK 21131 AAAA TQZZA Ed.05


19/100


1.3.4 Miscellaneous Function Blocks

Function BlockName Supported by Description

ETH-SW M-XWY in:

M-L1L2 shelf

M-CONT shelf.

Ethernet switching function.

DCI M-XWY in M-L1L2 shelf Clock distribution interface.

RNS-O&M-RoutingM-XP (ESU role) in M-L1L2shelf

Routing function for RNS (RNC Ev and all Node Bs)operation and maintenance traffic.

3BK 21131 AAAA TQZZA Ed.05 19 / 100


20/100


21/100

2 Rack Description

2 Rack Description

This section describes the RNC Ev rack including its configuration, layoutand power supply.

3BK 21131 AAAA TQZZA Ed.05 21 / 100


22/100


23/100

2 Rack Description

2.1.1 RNC Ev MINI Configuration

revd004

MXP

#0

MXP

#1

MXP

#2

MXP

#3

MXP

#4

MBLPL

MSIFMB

#10

MXWY

#P

MXWY

#R

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MCP

#0

MCP

#1

MBLPL

MOMP

#P

MXWY

#P

MXWY

#R

MBLPL

MBLPL

MBLPL

MBLPL

MOMP

#R

MBLPL

MBLPL

MBLPL

MBLPL

MCM

#P

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MFFTU #0 MFFTU #1

00 010203 04 05 0607 0809 10 111213 14 15 1617 1819 20 212223 24 25

MFANU MFANU MFANU MFANU

00 010203 04 05 0607 0809 10 111213 14 15 1617 1819 20 212223 24 25


MBLSH

Note: Empty board slots (M-BLPL) and empty shelf positions (M-BLSH) appear ingray.

3BK 21131 AAAA TQZZA Ed.05 23 / 100


24/100

2 Rack Description

2.1.2 RNC Ev 1000HD Configuration

revd005

MXP

#0

MXP

#1

MXP

#2

MXP

#3

MXP

#4

MXP

#5

MSIFMB

#10

MXWY

#P

MXWY

#R

MXP

#6

MXP

#7

MBLPL

MBLPL

MSIFMB

#15

MBLPL

MBLPL

MXP

#18

MXP

#19

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MCP

#0

MCP

#1

MCP

#5

MOMP

#P

MXWY

#P

MXWY

#R

MBLPL

MBLPL

MBLPL

MBLPL

MOMP

#R

MBLPL

MBLPL

MBLPL

MBLPL

MCM

#P

MCM

#R

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MCP

#2

MCP

#3

MCP

#4

MFFTU #0 MFFTU #1

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25


MBLSH



24 / 100 3BK 21131 AAAA TQZZA Ed.05


25/100

2 Rack Description

2.1.3 RNC Ev 3000HD Configuration

revd006

MBLSH

MXP

#0

MXP

#1

MXP

#2

MXP

#3

MXP

#4

MXP

#5

MSIFMB

#10

MXWY

#P

MXWY

#R

MXP

#6

MXP

#7

MBLPL

MBLPL

MSIFMB

#15

MBLPL

MXP

#17

MXP

#18

MXP

#19

MBLPL

MBLPL

MXP

#20

MXP

#21

MXP

#22

MXP

#23

MXP

#24

MBLPL

MCP

#0

MCP

#1

MCP

#5

MOMP

#P

MXWY

#P

MXWY

#R

MCP

#6

MCP

#7

MCP

#8

MCP

#9

MOMP

#R

MCP

#16

MCP

#17

MCP

#18

MCP

#19

MCM

#P

MCM

#R

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MCP

#2

MCP

#3

MCP

#4

MFFTU #0 MFFTU #1

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25




3BK 21131 AAAA TQZZA Ed.05 25 / 100


26/100

2 Rack Description

2.1.4 RNC Ev 1000HSD Configuration

revd052

MXP

#0

MXP

#1

MXP

#2

MXP

#3

MXP

#4

MXP

#5

MSIFMB

#10

MXWY

#P

MXWY

#R

MXP

#6

MXP

#7

MBLPL

MBLPL

MSIFMB

#15

MSIFMB

#16*

MXP

#17

MXP

#18

MXP

#19

MBLPL

MBLPL

MXP

#20

MXP

#21

MXP

#22

MXP

#23

MXP

#24

MXP

#25

MCP

#0

MCP

#1

MCP

#5

MOMP

#P

MXWY

#P

MXWY

#R

MCP

#6

MCP

#7

MBLPL

MBLPL

MOMP

#R

MBLPL

MBLPL

MBLPL

MBLPL

MCM

#P

MCM

#R

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MBLPL

MCP

#2

MCP

#3

MCP

#4

MFFTU #0 MFFTU #1

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25


00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25


MBLSH

* : Optional


26 / 100 3BK 21131 AAAA TQZZA Ed.05


27/100

2 Rack Description

2.1.5 RNC Ev 3000HSD Configuration

revd053

MXP

#0

MXP

#1

MXP

#2

MXP

#3

MXP

#4

MXP

#5

MSIFMB

#10

MXWY

#P

MXWY

#R

MXP

#6

MXP

#7

MXP

#8

MXP

#9

MSIFMB

#15

MSIFMB

#16*

MXP

#17

MXP

#18

MXP

#19

MBLPL

MBLPL

MXP

#20

MXP

#21

MXP

#22

MXP

#23

MXP

#24

MXP

#25

MCP

#0

MCP

#1

MCP

#5

MOMP

#P

MXWY

#P

MXWY

#R

MCP

#6

MCP

#7

MCP

#8

MCP

#9

MOMP

#R

MCP

#16

MCP

#17

MCP

#18

MCP

#19

MCM

#P

MCM

#R

MCP

#20

MCP

#21

MBLPL

MBLPL

MBLPL

MBLPL

MCP

#2

MCP

#3

MCP

#4

MFFTU MFFTU

00010203 04 0506 07 080910111213 14 1516 17 181920212223 24 25


00010203 04 0506 07 080910111213 14 1516 17 181920212223 24 25


MBLSH

* : Optional

Note: Slots of empty boards (M-BLPL) appear in gray.

3BK 21131 AAAA TQZZA Ed.05 27 / 100


28/100

2 Rack Description

2.2 Rack Layout

2.2.1 Front View

C

LASS1

LA

SERP

RO

D

UC

T

UP

P

ER:

TX0

LO

W

ER:

RX0

UP

PER:

TX1

LO

WER:

RX1

UP

P

ER:

TX2

L

OW

ER:

RX2

UP

P

ER:

TX3

LOW

ER:

RX3

Air intake

MFFTU#0

Fan unit

MFFTU#1

Power terminal

Circuit breaker

Eyebolt

Door Air filter

Shelf

Wrist strap

terminal

SG

revd002

Protect ve eart

Figure 1: RNC Ev Rack Front View

28 / 100 3BK 21131 AAAA TQZZA Ed.05


29/100

2 Rack Description

2.2.2 Side View

1 2 3 4 5 6 7 8 9 0 1 2 3

1 2 3 4 5 6 7 8 9 0 1 2 3

1 2 3 4 5 6 7 8 9 0 1 2 3

1 2 3 4 5 6 7 8 9 0 1 2 3

1 2 3 4 5 6 7 8 9 0 1 2 3

Evolium

revd048

Door

Eyebolt

Cable duct

Air exhaust

Figure 2: RNC Ev Rack Side View

2.2.3 Top View

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7

Cable

duct

Air

exhaust

Eyebolt

Door

revd003

Figure 3: RNC Ev Rack Top View

3BK 21131 AAAA TQZZA Ed.05 29 / 100


30/100


31/100

2 Rack Description

2.4 M-FFTU

The M-FFTU unit is mounted with the circuit breaker for a DC -48 V powersupply. It also mounts a noise filter per line. The power supply terminalis assigned to each shelf.

2.4.1 Front Panel View

The following figure illustrates the front panel view of M-FFTU:

To MCONT To ML L # To ML L #

0 1 2

revd008

Basic Rack

MFFTU #0, MFFTU #1

48V 0V10 248V 48V0V 0V

#0 #1

ML1L2shelf

ML1L2shelf

MCONT

shelf

2.4.2 Dimensions and Weight

Item Specification

Dimensions 120 mm (H) x 315 mm (W) x 211.5 mm (D)

Weight Less than 4.2 kg

3BK 21131 AAAA TQZZA Ed.05 31 / 100


32/100

2 Rack Description

2.4.3 Power Supply Distribution

Two M-FFTUs are mounted on the upper side of the rack. One M-FFTUinterface has three power lines, and provides the power supply to each shelf.Each line has its own circuit breaker and noise filter in the M-FFTU. Thecurrent rating for each breaker is 60 A.

The following figure illustrates the power distribution route from the M-FFTU:

MFFTU

48V

FIL

20

FIL

10

FIL

20

FIL

10

FIL

30

FIL

30

0V 48V 0V 48V 0V

(00) (10) (20)

CN10 CN20 CN30

48V

FIL

21

FIL

11

FIL

21

FIL

11

FIL

31

BK

FIL

31

0V 48V 0V 48V 0V

(01) (11) (21)

CN11 CN21 CN31

CONT Shelf L1L2#0 Shelf L1L2#1 Shelf

V1ALMV1ALM V1ALMV1ALM

FAN FAN FAN FANV1ALMV1ALMV1ALMV1ALM

FAN FAN FANFANV1ALMV1ALMV1ALMV1ALM

FAN FAN FAN FAN

SGFG

V1ALMV1ALMV1ALMV1ALM V1ALMV1ALMV1ALMV1ALM V1ALMV1ALMV1ALMV1ALM

V1V1 V2 V2 FG SG V1V1 V2 V2 FG SG V1 V1V2 V2 FG SG

revd007

BKBKBKBKBK

2.5 M-FILT

The M-FILT unit is an air filter that removes dust in the forced-air coolingsystem. M-FILT is mounted in the air filter slot located above the air intake ofthe RNC Ev rack. Refer to Front View (Section 2.2.1) for the mount position.

2.5.1 M-FILT View

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

1 2 3 4 5 6 7 8 9 0 1 2 3 4

revd047

32 / 100 3BK 21131 AAAA TQZZA Ed.05


33/100

2 Rack Description


Item Specification

Dimensions 33 mm (H) x 751 mm (W) x 309.5 mm (D)


3BK 21131 AAAA TQZZA Ed.05 33 / 100


34/100

2 Rack Description

34 / 100 3BK 21131 AAAA TQZZA Ed.05


35/100

3 Shelf Description

3 Shelf Description

This section describes the RNC Ev shelf configurations and provides functionalinformation on the shelves.

3BK 21131 AAAA TQZZA Ed.05 35 / 100


36/100


37/100

3 Shelf Description

3.2 M-L1L2 Shelf

3.2.1 M-L1L2 Shelf Configurations

The M-L1L2 shelf provides the following roles in the RNC Ev system:

Signaling protocol processing

Termination of various protocols related to layer 1 and layer 2

Accommodation of external interfaces to the Core Network, RNC Ev, Node

B and OMC-R.

The M-L1L2 shelf is equipped with:

2 M-XWY boards (used for both ATM and Ethernet switching)

1 to 6 M-SIFMB boards depending on the transmission requirements

1 to 22 M-XP boards depending on the transmission requirements. It is

possible to use unused M-SIFMB slots to mount additional M-XP boards in

the shelf.

revd012

MXP

#0

MXP

#1

MXP

#2

MXP

#3

MXP

#4

MXP

#5

M

XP

#10

/

M

SIFMB

#10

MXWY

#P

MXWY

#R

MXP

#6

MXP

#7

M

XP

#8

/

M

SIFMB

#8

M

XP

#9

/

M

SIFMB

#9

M

XP

#15

/

M

SIFMB

#15

M

XP

#16

/

M

SIFMB

#16

M

XP

#17

/

M

SIFMB

#17

MXP

#18

MXP

#19

MBLPL

MBLPL

MXP

#20

MXP

#21

MXP

#22

MXP

#23

MXP

#24

MXP

#25

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25



The following table lists the dimensions and weight for the M-L1L2 shelf:

Item Specification

Dimensions 430.7 mm (H) x 751 mm (W) x 356.55 mm (D)

Weight Less than 45.64 kg (including boards)

3BK 21131 AAAA TQZZA Ed.05 37 / 100


38/100

3 Shelf Description

3.3 Shelf IDs

3.3.1 Shelf ID Jumper Position

Both the M-CONT and M-L1L2 backplanes contain jumpers that give the frame

ID and shelf ID of the boards mounted on the shelf.The following figure illustrates the position of the frame ID and shelf ID:

revd038

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 2000 21 22 23 24 25

FRAME ID 0

FRAME ID 1

SHELF ID 0

SHELF ID 1

Backplane


3.3.2 Jumper Settings

The following table lists the shelf ID and frame ID settings:

Shelf FRAME ID0 FRAME ID1 SHELF ID 0 SHELF ID 1 Remarks

M-CONT Close Close Close Close The shelf ID is set at thefactory.

M-L1L2 #0 Close Close Open Close The shelf ID is set at thefactory.

M-L1L2 #1 Close Close Close Open The shelf ID is set at thefactory.

M-L1L2 #2 Open Close Close Close The shelf ID is set at thefactory.

M-L1L2 #3 Open Close Open Close The shelf ID is set at thefactory.

M-L1L2 #4 Open Close Close Open The shelf ID is set at thefactory.

Note: Whenever you add a shelf to a rack, you must set the shelf ID for the shelf.

38 / 100 3BK 21131 AAAA TQZZA Ed.05


39/100

4 Hardware Modules

4 Hardware Modules

This section describes the functions of the hardware modules in the RNC Ev.

3BK 21131 AAAA TQZZA Ed.05 39 / 100


40/100

4 Hardware Modules

4.1 M-CP

4.1.1 Functional Description

The main function of the M-CP board is to perform call processing. A maximum

of twenty M-CP boards can be mounted in the M-CONT shelf. The callprocessing capacity increases in proportion to the number of boards mounted.

The M-CP boards form a load sharing configuration. All M-CP boards operatein ACT state and there is no SBY M-CP.

The following figure illustrates the M-CP board:

G bus 1

revd013

Processor

module

G bus interface module

Power

supply module

I O us SV bus

Processor

module

I O us SV bus

G bus 2

Function Description

Processormodule

The processor module is a sub-board with a:

CPU

Chip set that includes:

Field Programmable Gate Array (FPGA) and Programmable Logic Device (PLD)

chips

RAM chips

Flash memory chips.

Programmable CPU firmware runs on the sub-board.

Programmed logic in the firmware determines how the sub-board controls its processesand resources.

G bus interfacemodule

The G-bus interface module is:

The interface at which the M-CPs connect to the redundantly paired M-CMs over

point-to-point buses.

Used for access to common resources on the M-CM.

The transmission rate is 1.08 Gbps.

40 / 100 3BK 21131 AAAA TQZZA Ed.05


41/100

4 Hardware Modules

4.1.2 M-CP Front View

CP

Reset switch

Lamps

MP1

MP0

revd014

Ejector

Ejector

LOCK

ALM

ACT

SBY

3BK 21131 AAAA TQZZA Ed.05 41 / 100


42/100

4 Hardware Modules

4.1.3 M-CP Operation and Maintenance

4.1.3.1 Lamps

Lamp Color Description

Amber Board in blocked state. It is ready to be removed from the shelf.LOCK

Amber

(blinking)

Board undergoing diagnosis.

ALM Red Board malfunctioning due to an internal fault.

Green Board is in service and is running normally.ACT

Green

(blinking)

Board is in normal operating state, but does not accept the allocation of newservices. When the current services on the board are terminated, the boardswitches to LOCK state (the LOCK lamp lights up).

SBY Amber The SBY lamp is not used.

4.1.3.2 Connector

ConnectorIndication Interface

ConnectorType Used to ...

MP0 10 / 100BaseT RJ-45 Connect the PC to the M-CP board for collectingthe data of CPU #0.

MP1 10 / 100BaseT RJ-45 Connect the PC to the M-CP board for collectingthe data of CPU #1.

4.1.3.3 Switch

Switch Function Description

Reset switch Pressing this switch, turns off all lamps and resets all hardware/software in the board.

Board reset should be performed when the:

ALM or LOCK lamp lights

Board is unstable.

42 / 100 3BK 21131 AAAA TQZZA Ed.05


43/100


44/100

4 Hardware Modules

The following figure illustrates the block diagram of the M-OMP board:

G busrevd015

Processor

module

G bus interface

module

Power

supply module

I O us SV bus

Hard Disk


Processor module The processor module is a sub-board with a:

CPU


FPGA and PLD chips

RAM chips

Flash memory chips.


Programmed logic in the firmware determines how the sub-board controlsits processes and resources.

G Bus interface module The G-bus interface module is:

The interface at which the M-OMPs connect to the redundantly

paired M-CMs over point-to-point buses.

Used for access to common resources on the M-CM.

The transmission rate is 1.08 Gbps.

Hard disk The following are stored on this hard disk:

RNC Ev software

Logging data

Traffic data.

44 / 100 3BK 21131 AAAA TQZZA Ed.05


45/100

4 Hardware Modules

4.2.2 M-OMP Front View

OMP

Reset switch

LampsEjector

Ejector

LOCK

ALM

ACT

SBY

MP

PLEASE

PULL

OUT

TH

IS

UNIT

AFTER

LOOK

LAMP

ON.

THIS

UNIT

IS

EQUIP

PED

WHIH

A

HDD

ATTENTION

!

revd016

3BK 21131 AAAA TQZZA Ed.05 45 / 100


46/100

4 Hardware Modules

4.2.3 M-OMP Operation and Maintenance

4.2.3.1 Lamps



Amber

(blinking)




Green

(blinking)

The M-OMP starts flashing its ACT lamp when it detects that it doesnot have the necessary software on its hard disk. The ACT lamp keepsblinking up to the moment just before the D-SW is downloaded to the hard

disk in the early commissioning stage.

SBY Amber Board is in service and in standby state. It is ready for switch-over tooperating state.

4.2.3.2 Connector



MP 10 / 100BaseT RJ-45 Connect the PC to the M-OMP board for collecting thedata.

4.2.3.3 Switch





Board is unstable.

46 / 100 3BK 21131 AAAA TQZZA Ed.05


47/100

4 Hardware Modules


The following table lists the dimensions and weight for M-OMP:

Item Specification

Dimensions 294 mm (H) x 330.85 mm (W) x 26 mm (D)


4.3 M-CM


The M-CM board fulfills a shared memory function (global memory part) for the

M-CP/M-OMP boards in the M-CONT shelf, which connect to the M-CM boardvia the G bus. Its role includes a:

Semaphore function

Timer function

Calendar function.

The M-CM board also connects to the M-XWY board via the I/O bus to transferI/O packets and via the SV bus to control and monitor board status.

The following figure illustrates the block diagram of the M-CM board:

G bus 1

revd017

Processor

module

Common

memory module

Power

supply module

I/O bus SV bus

G bus 2

G bus 22

Synchronization interface

3BK 21131 AAAA TQZZA Ed.05 47 / 100


48/100

4 Hardware Modules


Processormodule

The processor module is a sub-board with a:

CPU


FPGA and PLD chips

RAM chips

Flash memory chips.


Programmed logic in the firmware determines how the sub-board controls its processesand resources.

G bus1 to 22

Connects the M-CM board to the M-CP and M-OMP boards.

Controls access to global memory from 20 M-CP boards and 2 M-OMP boards

Transient state control function

The G-bus interface chip sends or receives data over an 8-bit point-to-point data

channel at a bit rate of 480 Mbps (60 MHz x 8 bits).

Maintains consistency between the global memory on system #P and on system #R

via the synchronization interface.

Common memory

The common memory mounts 1 GB of DDR-SDRAM to support an Error Correcting

Code (ECC) function.

In normal mode, M-CP updates this common memory on the ACT and SBY M-CM

boards.

Stores temporary data shared between the M-CP and the M-OMP.

Common

memorymodule

Synchronization interface

The hardware continuously performs data synchronization from ACT M-CM to SBY M-CMvia the dedicated line.

48 / 100 3BK 21131 AAAA TQZZA Ed.05


49/100

4 Hardware Modules

4.3.2 M-CM Front View

CM

Reset switch

LampsEjector

Ejector

LOCK

ALM

ACT

SBY

MP

revd018

3BK 21131 AAAA TQZZA Ed.05 49 / 100


50/100

4 Hardware Modules

4.3.3 M-CM Operation and Maintenance

4.3.3.1 Lamps



Amber

(blinking)


The Lock lamp also blinks (ten minutes) during the GM copy phase of theCM board.


ACT Green Board is in service and running normally.

SBY Amber Board is in service and in standby state. It is ready for switch-over tooperating state.

4.3.3.2 Connector



MP 10 / 100BaseT RJ-45 Connect the PC to the M-CM board for collecting the data.

4.3.3.3 Switch





Board is unstable.

4.3.4 Dimensions and WeightThe following table lists the dimensions and weight for M-CM:

Item Specification



50 / 100 3BK 21131 AAAA TQZZA Ed.05


51/100


52/100

4 Hardware Modules


Ethernet switch I/O bus signal and U plane information are switched on the Ethernet frame.

Conversion between Ethernet and ATM.

SV bus master Monitors the bus for faults while managing slave boards.

Clock distribution Distributes EMA reset, M-XWY ACT, and clock for system synchronization.

52 / 100 3BK 21131 AAAA TQZZA Ed.05


53/100

4 Hardware Modules

4.4.2 M-XWY Front View

XWY

Reset switch

LampsEjector

Ejector

LOCK

ALM

ACT

SBY

revd020

CU

ET1

ET2

CL

GbEU

GbEL

MP

MON

3BK 21131 AAAA TQZZA Ed.05 53 / 100


54/100

4 Hardware Modules

4.4.3 M-XWY Operation and Maintenance

4.4.3.1 Lamps



Amber (blinking) Board undergoing diagnosis.


ACT Green Board is in service and is running normally.

SBY Amber Board is in service and is in the standby state. It is ready for switch-over tothe operating state.

4.4.3.2 Connector



CU 3V CMOS differential RJ-45 (*) For clock and EMARST distribution.

Connects to CL of the shelf with shelf IDN+1.

CL 3V CMOS differential RJ-45 (*) For clock and EMARST distribution.Connects to CU of the shelf with shelf ID

N-1 if it is not the one at the bottom of therack.

ET1, ET2 10 / 100BaseT RJ-45 For OMC-R/CBC/GPS

GbEU 10G Ethernet XAUI For inter-shelf I/O bus connection.

Connects to GbEL with shelf ID N+1.

GbEL 10G Ethernet XAUI For inter-shelf I/O bus connection.

Connects to GbEU of the shelf with shelfID N-1 if it is not the one at the bottom ofthe rack.

MP 10 / 100BaseT RJ-45 Connect the PC to the M-XWY board forcollecting the data.

MON 10 / 100BaseT RJ-45 For I/O bus tracing

(*) : Even though the connector type is RJ-45,DO NOT connect an Ethernet cable here. If you connect an Ethernetcable by mistake, the board is not damaged but does not work properly.

54 / 100 3BK 21131 AAAA TQZZA Ed.05


55/100

4 Hardware Modules

4.4.3.3 Switch





Board is unstable.


The following table lists the dimensions and weight for M-XWY:

Item Specification



4.5 M-SIFMB


The M-SIFMB board is responsible for the following functions:

Termination of 4 STM-1 optical interfaces

Support of VC4

Clock selection and generation

AAL2 and AAL5 processing

Band control.

3BK 21131 AAAA TQZZA Ed.05 55 / 100


56/100

4 Hardware Modules

The following figure illustrates the M-SIFMB board:

4 STM1 Optical Signals

STM1

Interface

revd021

VC4

BWC Control Module

Processor

Module

Clock

STM1

Interface

STM1

Interface

STM1

Interface

Power

Supply

Module

Clock

Interface

I/O bus SV bus



CPU


FPGA and PLD chips

RAM chips

Flash memory chips.


Programmed logic in the firmware determines how the sub-board controls itsprocesses and resources.

BWC control module Implements the following functions:

Bandwidth control

Shaping and QoS controlVP/VC-based OAM control.

VC4 Supports STM-1 in the non-channeled format.

VC4 cross connect for STM-1.

STM-1 interface STM-1 line control and alarm detection.

Clock STM-1 clock transfer to the 'CLOCK distribution block' in the M-XWY board.

56 / 100 3BK 21131 AAAA TQZZA Ed.05


57/100

4 Hardware Modules

4.5.2 M-SIFMB Front View

SIF

Reset switch

LampsEjector

Ejector

LOCK

ALM

ACT

SBY

revd022

CLASS 1

LASERPRODUCT

UPPER:TX0

LOWER:RX0

UPPER:TX1

LOWER:RX1

UPPER:TX2

LOWER:RX2

UPPER:TX3

LOWER:RX3

MP

3BK 21131 AAAA TQZZA Ed.05 57 / 100


58/100

4 Hardware Modules

4.5.3 M-SIFMB Operation and Maintenance

4.5.3.1 Lamps


Amber The board is in blocked state. It is ready to be removed from the shelf.LOCK

Amber (blinking) The board is undergoing diagnosis.

ALM Red The board malfunctions due to an internal fault.

Green The board is in service and running normally.ACT

Green (blinking) The board is in normal operating state, but does not accept the allocationof new services.

When the current services on the board are terminated, the boardswitches to LOCK state (LOCK lamp lights up).

SBY Amber Not used.

4.5.3.2 Connector

ConnectorIndication Interface Connector Type Used to ...

TX0, RX0,TX1, RX1,

TX2, RX2,TX3, RX3

STM-1 optical interface LC duplex receptacle For Iu, Iub and Iur optical connection

MP 10 / 100BaseT RJ-45 Connect the PC to the M-SIFMB boardfor collecting the data.

4.5.3.3 Switch





Board is unstable.

58 / 100 3BK 21131 AAAA TQZZA Ed.05


59/100

4 Hardware Modules


The following table lists the dimensions and weight for M-SIFMB:

Item Specification



4.6 M-XP


The M-XP board is responsible for signaling protocol processing. It has a

CPU and DSPs. Depending on the firmware installed, this board performsdifferent roles as follows:

ESU role:Implements SAAL functions to send/receive the following to/from theM-CONT:

Core Network control signals

Node B control signals

RNC Ev communication signals.

It also has a relay function to communicate with the M-CONT shelf.

MSU role:Terminates the DCCH in UE, AAL2, and RLC. It has a ciphering/decipheringfunction as well as integrity functions.

DHT role:On Diversity Handover, DHT chooses and composes the identical data(frame data with the same CFN) from UE sent through different branches. Itcopies and distributes data to send the same data to UE through differentbranches.

MMUX role:

Multiplex and demultiplex Unit for transport channel termination

Multiplexes or demultiplexes MAC layer information in RACH or FACH

at the radio interface. This information is used to exchange signaling

data and user data.

SPU role:Terminates the protocol of packet data communicated between the NodeB and the Core Network.

3BK 21131 AAAA TQZZA Ed.05 59 / 100


60/100

4 Hardware Modules

The following figure illustrates the M-XP board:

revd023

AAL

SAR

DSP1

RAM

DSP2

RAM

DSP8

RAM

Processor

module

Gbit Ethernet

interface

Power

supply moduleI/O bus

PCI interface

UTOPIA interface

SV bus

I/O bus I/O bus



CPU


FPGA and PLD chips

RAM chips

Flash memory chips.

Programmable CPU firmware runs on the sub-board.Programmed logic in the firmware determines how the sub-board controls itsprocesses and resources.

AAL5-SAR AAL5-SAR perform the following functions:

Ends the AAL5 cell sent from XWY-Inf FPGA through the UTOPIA layer 1

interface, and assembles it into a packet to send to the CPU.

Disassembles the packet sent from the CPU into an AAL5 cell, and sends it

to XWY-Inf FPGA through the UTOPIA layer 1 interface.

60 / 100 3BK 21131 AAAA TQZZA Ed.05


61/100

4 Hardware Modules


DSP The DSP block has 8 DSPs. As a hardware interface, each DPS has a

UTOPIA Layer 2 interface and a PCI bus interface. The UTOPIA layer 2

works between XWY Inf FPGAs and the PCI bus interface works between

PCI bridges.

DSP firmware processes each protocol, audio and packet data between radio

terminals capsulated in an AAL2 cell.

The M-XP board can change its function via a change to the DSP firmware.

With no change to the hardware of board, you can configure the firmware

to have the board perform the following functions:

DHT

MMUX

SPU

MSU

ESU.

PCI interface The PCI bus transmits/receives:

Signal processing data (C plane/U plane)

AAL2 type packet data

XWY-Inf FPGA

The AAL5 SAR block.

UTOPIA interface AAL5-type information is transmitted to the AAL5 SAR block (AAL5 SAR LSI)

through the UTOPIA layer 1 interface.

AAL2-type information is transmitted to the DSP block through the UTOPIA

layer 2 interface.

Gbit Ethernet interface The Gigabit Ethernet interface that connects the M-XP to the I/O bus to send orreceive ATM cells to or from the M-XWYs.

3BK 21131 AAAA TQZZA Ed.05 61 / 100


62/100

4 Hardware Modules

4.6.2 M-XP Front View

MP

XP

Reset switch

LampsEjector

Ejector

LOCK

ALM

ACT

SBY

revd024

62 / 100 3BK 21131 AAAA TQZZA Ed.05


63/100

4 Hardware Modules

4.6.3 M-XP Operation and Maintenance

4.6.3.1 Lamps



Amber

(blinking)




Green

(blinking)

Board is in normal operating state, but does not accept the allocation of newservices. When the current services on the board are terminated, the boardswitches to LOCK state (the LOCK lamp lights up).

SBY Amber Board is in service and in standby state. It is ready for switch-over to operating state.

4.6.3.2 Connector

ConnectorInterface Interface


MP 10 / 100BaseT (RJ-45) Connect the PC to the M-XP board for collecting the data.

4.6.3.3 Switch





Board is unstable.


The following table lists the dimensions and weight for M-XP:

Item Specification



3BK 21131 AAAA TQZZA Ed.05 63 / 100


64/100

4 Hardware Modules

4.7 M-FANU


M-FANU contains two fans and provides a forced air cooling system. Four fan

units are mounted in the bottom of each shelf. Each fan has its own ALM lampand a fuse for maintenance purposes.

4.7.2 M-FANU Top View

revd025

64 / 100 3BK 21131 AAAA TQZZA Ed.05


65/100

4 Hardware Modules

4.7.3 M-FANU Front View

F0

F1

1.0A

1

0

revd026

FAN ALM


The following table lists the dimensions and weight for the M-FANU:

Item Specification

Dimensions 87.5 mm (H) x 178.0 mm (W) x 331.2 mm (D)


3BK 21131 AAAA TQZZA Ed.05 65 / 100


66/100

4 Hardware Modules

66 / 100 3BK 21131 AAAA TQZZA Ed.05


67/100

5 Software

5 Software

This section describes the platform software structure, application functionalblock and firmware.

3BK 21131 AAAA TQZZA Ed.05 67 / 100


68/100

5 Software

5.1 Control Part Software Architecture

The following figure describes the main parts of the control softwarearchitecture.

FIRMEOS

Layer

Inside of CP

Application

VxWorks

(BOS)

Boot

ROM

EOS

Layer

Hardware

Platform

revd054

I/O bus

The control parts of software consists of :

The application part

The platform part

A Boot ROM

VxWorks (Operating System)

EOS Layer

Firmware

Hardware.

Each part communicates to control the RNC Ev.

The application part is separated from the platform part, which means that anupdate to the platform part does not impact the application part.

5.1.1 Control Part Roles

There are some roles of the control part.

Four roles in the platform level

Four roles in the application level.

The roles are assigned to specific board of the M-CP and the M-OMP board.

68 / 100 3BK 21131 AAAA TQZZA Ed.05


69/100

5 Software

5.1.2 Platform Level

CP Role Description

MCP (Master CP) All the M-CP and the M-OMP boards boot up simultaneously at the RNC Ev restarting,

One of the M-OMP board is always first started central processing unit and becomesthe MCP.

The MCP is responsible for the initialization of common resources:

GM memory area initialization

OD distribution from the SDM memory onto the GM memory.

After that, other central processing unit in the M-CPs and the M-OMP board canperform the platform initialization process.

OMP (Operationand Maintenance

CP)

An M-OMP board is in charge of operation and maintenance functions.

The two M-OMP boards are given the OMP role, one being the "Active OMP" andthe other one being the "Standby OMP".

These two M-OMP boards are always the CP #0 and CP #1. Usually at systemrestart, CP #1 becomes the Active OMP whereas CP #0 is the Standby OMP (onthe standby OMP, only booting and platform tasks initialization are performed, theapplication software is not started.)

CLP (CallProcessing CP)

The call processing function is ensured by the M-CP boards having the "CLP role".

And each M-CP board has 2 central processing units.

The central processor units have number from #2 to #41.

HCP (HookMethod CP)

The HCP role is allocated to only one M-CP board, which is the CLP having thesmallest CP number.

The HCP is in charge of distributing the call processing to the appropriated CLPbased on load sharing mechanisms.

In case the CP having the HCP role is in failure or in case it has been locked formaintenance purpose, the standby HCP takes immediately the HCP role withoutany service outage.

3BK 21131 AAAA TQZZA Ed.05 69 / 100


70/100


71/100

5 Software

5.2 Application Part Function

Application

O&M functional blocks

RANAP

(RANAP protocol control)

RRC

(RRC protocol control)

NBAP

(NBAP protocol control)

QAAL2

(QAAL2 protocol control)

RAC

(Radio Access Control)

ACC(Access Control)

ESV(Equipment SuperVisor)

TFO(TraFfic Observation)

RPC

(Restart Procedure Control)

OPI

(OPS Interface)

RMT

(Remote data Transfer)

RNSAP

(RNSAP protocol control)

RACLOAM

(RAC Logical OAM)ADT (AuDiT)

TST (Test)

revd055

Telecom functional blocks

3BK 21131 AAAA TQZZA Ed.05 71 / 100


72/100

5 Software

5.2.1 Operation and Maintenance Functional Blocks

Functional Block Description

ESV (Equipment Supervisor) This function block provides:

RNC equipment supervision

RNC control management

Node B emergency control

Diagnosis.

OPI (OPS Interface) This function block provides:

OMC-R Corba interface: Manager's requests &

responses/notifications to the Manager

OPI/FB's interface: Reception of requests

FB's/OPI interface: Reception of responses

Invalid data files management.

ACC (Access Control) This function block provides:

RAC interface: system information update requests/responses

System Information update procedure OPI interface:

requests/responses/notifications

Access restriction management SIB1(3) update on Iu link failure

SIB1/SIB3/SIB5/SIB11/SIB18 update for Outage Reduction

SIB3 update on CPU overload.

TFO (Traffic Observation) This function block provides the traffic measurement:

Data collection

Data aggregation

Reporting to the Manager.

RMT (Remote Data Transfer) This function block provides:

File operation

Directory operation

Pack operation.

72 / 100 3BK 21131 AAAA TQZZA Ed.05


73/100

5 Software


RPC (Restart Procedure Control) This function block provides:

AP initialization

Control of RNC restart

Control of Node B restart

Phase difference measurement

AP SW errors handling

Global mechanism for online OD update.

ADT (Audit) This function block provides:

Audit of the resources associated to calls

Audit control and supervision.

TST This function block provides the loopback tests on Iu, Iur and Iubfor NEM-R.

RACLOAM (RAC Logical OAM) This function block provides:

Cell Management Iu link supervision

BTS control channel monitoring

Paging list management.

5.2.2 Telecom Functional Blocks


RAC (Radio Access Control) This function block provides:

Ability of each protocol management processing

Call handling

Take a traffic

Connect a radio link.

RRC (RRC Protocol Control) Provides encoding/decoding of Uu protocol messages.

NBAP (NBAP Protocol Control) Provides encoding/decoding of NBAP protocol messages.

RANAP (RANAP Protocol Control) Provides encoding/decoding of RANAP protocol messages.

RNSAP (RNSAP Protocol Control) Provides encoding/decoding of RNSAP protocol messages.

QAAL2 (QAAL Protocol Control) Provides encoding/decoding of ALCAP protocol messages.

3BK 21131 AAAA TQZZA Ed.05 73 / 100


74/100

5 Software

5.3 Software Files

5.3.1 Downloaded Software (D-SW)

There are two types of software. One is O-SW (Origin software). Other is

D-SW (Downloaded software.)The O-SW has been installed in each board at factory and is not updatedusually. The role of the O-SW is initial set up of the each board such as boot.

There are two types of the D-SW.

Load Module

Firmware.

The D-SW is necessary to operate the RNC Ev.

5.3.1.1 Load Module

The Load Module contains the executable software of the processor board.The Load Module is installed on the following boards:

M-CP

M-OMP.

5.3.1.2 Firmware

Firmware is software installed in boards to perform basic hardware control. It ispossible to replace firmware as necessary to add or upgrade functions.

Firmware is installed on the following boards:

M-CM

M-XWY

M-SIFMB

M-XP.

5.3.2 Office Data

The Office Data file contains information on:

Network Element configuration

Transport configuration

Radio configuration.

74 / 100 3BK 21131 AAAA TQZZA Ed.05


75/100

5 Software

5.4 PLD and FPGA Configuration

All boards integrate a 'Configuration NGISL interface Reset control-Programmable Logical Device' (CNR-PLD). The PLD is a programmablelogic-gate chip, which can be considered a small-scale Field ProgrammableGate Array (FPGA). The PLD can provide various capabilities via programming.

Unlike FPGA, the PLD needs a special programming tool.

FPGA is provided with rewritable programs and can control them. CPUsoftware boots up first on the CPU daughter board, and then the softwareconfigures FPGAs on the motherboard by sending the data to each FPGAthrough CNR-PLD.

The following table summarizes the main hardware requirements for PLDand FPGA:

Name Type Functions Used on ...

CNR PLD FPGA configuration interface

Nectar Gate Array Internal Serial Link Version3 (NGISL3)

ASIC interface (bus protocol conversion)

Reset control

EMA function (S-WDT).

M-CP

M-OMP

M-CM

M-XWY

M-XP

M-SIFMB.

CPGIF FPGA G bus interface on M-CP side

Bus protocol conversion (device bus G bus)

G bus access arbitration between two CPUs.

M-CP

M-OMP.

CMGIF FPGA G bus interface on M-CM side

Global memory access arbitration

Flags.

M-CM

RAMCNT FPGA Global memory (DDR333 SDRAM) interface (SSTL-2) M-CM

BWC-MUX FPGA Line interface egress processing

PF cell -> composite cell conversion

QoS classification and shaping

Cell header conversion

Packet discard control (EPD / PPD)

Statistics.

M-SIFMB

3BK 21131 AAAA TQZZA Ed.05 75 / 100


76/100

5 Software

Name Type Functions Used on ...

BWC-DMUX FPGA Line interface ingress processing

Composite cell -> PF cell conversion

OAM F4/F5 control

Cell header conversion

Statistics.

M-SIFMB

XWYINF FPGA I/O bus interface

ATM cell encapsulation / decapsulation with Ethernet frames

Data multiplexing / demultiplexing for I/O plane and U plane

Switch plane selection

UTOPIA interface for DSPs

Health cell generation/termination

Lamp control

System timing, and frame number reception.

M-CP

M-OMP

M-XP

M-SIFMB.

MISC FPGA Clock generation / selection

Board status collection

SV bus gating control.

M-XWY

76 / 100 3BK 21131 AAAA TQZZA Ed.05


77/100

6 Operation and Maintenance


This section describes how to handle the problems that can occur in RNC Evequipment during operation and maintenance of the system.

3BK 21131 AAAA TQZZA Ed.05 77 / 100


78/100


6.1 Overview

6.1.1 OMC-R

The OMC-R is the central supervision and configuration tool for a UTRAN

network or subnetwork. Its management functions cover the following areas:

Cell and network topology management

Radio network evolution and optimization

Transport configuration management

Network level software management

Supervision at network level (state supervision, lock/unlock the network

elements, etc.)

Network alarm management

Network performance and radio trace management

Network time management

RNC Ev OD file replacement.

RNC Ev

OMCR

Itfr Itfb

LMT

(NEMB)

Switch

Other O&M

systemsRNP

Other

OMCRs

LMT

(NEMR)

Node B

revd027

SNMP,

Telnet

78 / 100 3BK 21131 AAAA TQZZA Ed.05


79/100


6.1.2 NEM-R

The NEM-R provides equipment management services for the RNC Ev.

It can perform its monitoring and control functions remotely from the OMC-R orlocally from the LMT. The services offered by the NEM-R depend on whetherthe RNC Ev is in offline or online mode.

OMCR

NM Server

RNC Ev

OMCR Router

OMCR Client

NEMR

LMT

NEMR

revd028

DCN

6.1.2.1 Local Mode

The NEM-R can access the RNC Ev locally via the maintenance port of theACT M-OMP board on the front of the RNC Ev.

Connection with the M-OMP board is used for supervision/control, softwareand configuration replacement, and system reset.

6.1.2.2 Remote Mode

The NEM-R on a remote site can access the RNC Ev in one of the followingways:

Via the ATM interface of the Port #0 on M-SIFMB #10 in M-L1L2 #0

Via the Ethernet interface of M-XWY #P in M-CONT.

Connection with each board is used for supervision and control services andsystem reset. Configuration replacement does not support remote mode.

3BK 21131 AAAA TQZZA Ed.05 79 / 100


80/100


6.2 Equipment Management

6.2.1 Fault Detection and Reporting Route

The RNC Ev supervises the RNC Ev itself always. The RNC Ev detects a

fault automatically.Faults detected in each board are collected by M-XWY through the SVbus and then reported to M-OMP through the I/O bus. The following figureillustrates the fault reporting route:

MXP

revd029

ML1L2 shelf

MCONT shelf

MSIFMB MSIFMB MXP

MXWY

MCP MOMP

MXWY

MCP MCPOMCR

NEMR

SV bus

I/O bus

ALM

SV bus

I/O bus

The M-OMP identifies the fault and reports it to OMC-R.

The M-XWY boards collect the FAN and power supply alarms, and send

them to M-OMP.

When M-OMP identifies a board alarm, it resets the faulty board and

performs a diagnosis on that board.

If the board diagnosis confirms a fault on the board, M-OMP lights up the

ALM lamp for the board.

If M-OMP does not receive a health check response from a duplicated I/O

bus, it considers that the board has a fault and lights up the ALM lamp

for that board through the SV bus.

80 / 100 3BK 21131 AAAA TQZZA Ed.05


81/100


6.2.2 Board State

The following lamps indicate the board state:

ACT (active):When lit, the ACT lamp on the front of the board indicates the board is

in service and operating.

SBY (standby):When lit up, the SBY lamp on the front of the board indicates:

The board is in service, operating and in standby.

The SBY board is ready to switch over to ACT state.

LOCK:When lit up, the LOCK lamp on the front of the board indicates the board islocked. It is possible to remove the board without additional operations.Fault processing for this board does not operate in ALM state.

DIAG (diagnosis):The LOCK lamp on the front panel of the board blinks while the board is

undergoing diagnosis.

Diagnosis is underway for the board to check its availability.

ALM (alarm):When lit, the ALM lamp indicates a board fault. The board is out-of-service.

6.2.3 Board Configuration

Shelf Board RNC Ev MINI Other RNC Types

M-CP Load sharing Load sharing

M-OMP P/R P/R

M-CONT

M-CM Non redundant P/R

M-SIFMB Non redundant Non redundant

M-XP (DHT role) Non redundant N+1

M-XP (MMUX role) Non redundant N+1

M-XP (SPU role) Non redundant Load sharing

M-XP (MSU role) Non redundant Load sharing

M-L1L2

M-XP (ESU role) Non redundant Load sharing

Common M-XWY P/R P/R

Other RNCTypes

: RNC Ev 1000HD / 3000HD / 1000HSD / 3000HSD.

3BK 21131 AAAA TQZZA Ed.05 81 / 100


82/100


6.2.4 Fault Processing

6.2.4.1 Redundancy Configuration

In a redundancy configuration, a board fault is processed as described below:

P R Con gurat on N+ Con iguration

ACT

revd033

RPNormal

RFault

SBY

ACTALM

RPFault

recovery

ACTSBY

SBY

+1

Normal

Fault

ACT

Fault

recovery

#N#1#0

ACT ACT

ACT

+1

ALM

#N#1

ACT ACT

ACT

+1

SBY

#N#1#0

ACT ACT

(*): Load sharing with protection (+1)

P #0

6.2.4.2 Non-Redundancy Configuration

In a non-redundancy configuration, a board fault is processed as describedbelow:

oa aring on e un an

ACT

#N#1#0

Normal

#N#1

Fault

ACT ACT

ACT ACTALM

#N#1#0

Fault

recovery

ACT ACTACT

ACT

Normal

Fault

ALM

Fault

recovery

ACT

#0

revd032

82 / 100 3BK 21131 AAAA TQZZA Ed.05


83/100


6.2.5 Board Lock Processing

6.2.5.1 Redundancy Configuration

The following figure illustrates the board lock operation with a redundancyconfiguration:

P R Con gurat on N+ Con iguration

ACT

revd033

RPNormal

RShutting

down

SBY

ACTACT

RPLocked

ACTLOCK

P

SBY

+1

Normal

Shutting

down

ACT

Locked

#N#1#0

ACT ACT

ACT

+1

ACT

#N#1

ACT ACT

ACT

+1

LOCK

#N#1#0

ACT ACT

#0

(*): Load sharing with protection (+1)

6.2.5.2 Non-Redundancy Configuration

The following figure illustrates the board lock operation with a non-redundancyconfiguration:

oa aring on e un an

ACT

revd034

#N#1#0

Normal

#N#1

Shutting

down

ACT ACT

ACT ACTACT

#N#1#0

Locked

ACT ACTLOCK

ACT

Normal

Shutting

down

ACT

Locked

LOCK

#0

6.3 Diagnosis and Health Check

6.3.1 Power-up Diagnosis

Power-up diagnosis is executed on power up of each board. If the result isOK, then the board switches to ACT or SBY state. If it is not OK, the boardswitches to ALM state.

6.3.2 Automatic Diagnosis

If a fault is detected in a board, M-OMP declares an ALM state for that boardand executes a detailed diagnosis. M-OMP turns on the ALM lamp of the boardwhen the diagnosis determines a fault on the board.

If the diagnosis result is not OK, the test information is stored in the hard disk ofthe RNC Ev. The stored result information can be obtained using the NEM-R.

3BK 21131 AAAA TQZZA Ed.05 83 / 100


84/100


6.3.3 Manual Diagnosis

The operator can perform a diagnosis on an individual hardware board usingthe NEM-R. When the diagnosis is started from the NEM-R, the correspondingboard is in LOCK state. The diagnosis result is logged in the file specifiedby the operator.

6.3.4 Health Check

The health check monitors the I/O bus condition between target boards.

To ensure that you can use the SBY side of the highway in case of switch-over,the health check mechanism is implemented as illustrated in the following figure:

MXWY

(ACT)

MXPMXP

revd035

ML1L2 #0 shelf

MCONT shelf

MXP MSIFMB

MXWY

(SBY)

MXWY

(ACT)

MXWY

(SBY)

MOMP

(ACT)MOMP

(SBY) MCP

CPU

#0

CPU

#1

MCM

Healthcheck

Healthcheck

Healthcheck

Result

Result

Result

Healthcheck

I/O messages are exchanged between M-XWY and subordinate boards.

The health check operation is performed between the M-XWY board and theassociated boards on the shelf. All health check results gathered by theM-XWY board are sent to ACT M-OMP.

84 / 100 3BK 21131 AAAA TQZZA Ed.05


85/100


6.4 Hard Disk Operation

The M-OMP board hard disk integrates a mirroring redundancy system.

The files in the hard disk of the ACT and SBY M-OMP boards are synchronizedvia a software operation. The hard disk of the SBY M-OMP board is overwritten

with the contents of the ACT M-OMP board via mirroring operation. However, apart of the directory is not subject to mirroring. If one M-OMP board becomesLOCKED, hard disk mirroring is stopped, which means that hard disk mirroringis not always performed continuously.

Mirroring is classified into two types:

Per-file synchronization (COPY and DELETE) in ACT M-OMP

Batch file monitoring in a non-active M-OMP undergoing restoration:

Standby

HD

Active

OMCR(SFTP)

(SFTP)

HD

MOMP #RMOMP #P

MCMMCP

Board

revd039

MOMP#P

\hd0(5GB)

a

b

c

f

g

FTP

FILE

COMMISS

ACCEPT

TRAFFIC\hd1(5GB)

\hd2(10GB)

d

e

VENDOR

TRACE

HISTORY

RESTART

DIAGNOSIS

MOMP#R

\hd0(5GB)

a

b

c

f

g

FTP

FILE

COMMISS

ACCEPT

TRAFFIC\hd1(5GB)

\hd2(10GB)

d

e

VENDOR

TRACE

HISTORY

RESTART

DIAGNOSIS

: Nonmirroring : Mirroring

Legend

LMT

The following table lists the file types stored on the hard disk:

Name of Directory File Type Allocation Size

/hd0/a/FTP D-SW and OD file for upload and download

/hd0/b/FILE D-SW and OD file update and rack inventory file

/hd0/f/COMMISS Commissioning file and rack inventory file

/hd0/g/ACCEPT Accepted OD file

5 GB

(directory space is shared)

3BK 21131 AAAA TQZZA Ed.05 85 / 100


86/100


Name of Directory File Type Allocation Size

/hd1/c/TRAFFIC Traffic data

/hd1/c/HISTORY History of equipment supervision

/hd1/c/RESTART Restart data

/hd1/c/DIAGNOSIS Diagnosis

5 GB


/hd2/d/VENDOR Trouble analysis information

/hd2/e/TRACE Trace data

10 GB


6.5 System Defence Mechanism

The total usage rate of the call processing units in the RNC Ev is measuredperiodically.

The RNC Ev detects overload state on the M-CP board when the usage rateexceeds the predetermined thresholds.

The RNC Ev performs an access classes restriction according to the overloadratio to solve the overload status. The access class restriction means to restrictoriginating/terminating call from UE.

In addition to the defence mechanism for the M-CP board, the RNC Ev hasoverload detection and handling mechanism for the M-XP(DHT, MMUX andSPU function) board and SIF board.

For the DHT function on the M-XP board, overload is prevented with anadmission control based on the number of simultaneous channels. Theadmission control is performed each time when resources for the DHT on theM-XP board are required.

For the SPU function on the M-XP board, overload is prevented an admissioncontrol based on:

the number of simultaneous connections

the requested bandwidth.

For the MMUX function on the M-XP board, FACH and PCH overload aredetected.

The MMUX overload actions are

the new paging requests is ignored while a PCH overload is detected.

excess FACH data frames are discarded while a FACH overload is detected.

For SIF board, overload is prevented by a connection admission control on Iub,Iur, Iu-CS and Iu-PS, called at each new ALCAP request.

86 / 100 3BK 21131 AAAA TQZZA Ed.05


87/100


6.6 Performance Measurement

One performance measurement (PM) task per the RNC Ev is activated atthe RNC initialization.

The PM counters are recorded every hour except the RNC restart period.

The PM counters are saved in files on the M-OMP board. The saved filesare kept during 24 hours.

The OMC-R collects the PM data from the RNC Ev per every hours.

For more information of the PM counters, refer to the PM Counters Dictionary.

6.7 RNC Ev Start-Up

In the initial stage of the commissioning procedure, Downloaded Software(D-SW) is not stored on the local SDM board, so this procedure does not work.

Origin Software (O-SW, similar to a boot file), however, is stored on a protected

area of each board. When O-SW is operating, the LMT can use FTP protocol.In short, it is possible to download D-SW and OD to the hard disk manually.

The system restarts after completing the D-SW and OD download, and theRNC Ev system starts up.

6.8 Security between RNC Ev and OMC-R

The RNC Ev and the OMC-R is usually connected via the DCN.

The RNC Ev supports the following security solutions b

Evolium A9140 RNC Evolution Description 211310000e05

Documents

Transcript of Evolium A9140 RNC Evolution Description 211310000e05