NBSS_RNC Architecture and Functionalities_v0.1

1

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

For internal use


RNC Architecture & Functionalities

Synchronous Classroom v.01

RSO EFLM

5 Feb. 2014 RSO - NBSS

2

For internal use


Content

RNC Release versions & Mechanics

IPA2800 Platform description and comparison with DX200

Redundancy Types

RNC2600 Block diagram & ATM Switching Functionality

RNC2600 Computer units & Functionality

Radio Resource Management

WCDMA Protocol & Traffic Flow Scenarios

RNC2600 Hardware plug in units capability & interfaces

RNC Preventive Maintenance & Troubleshooting

RNC SW Build Safe-copying & Restoration

RSO - NBSS

3

For internal use


RNC Product Naming

Release version is associated with particular hardware release.

All type of RNCs can be upgradable to capability of higher releases with some H/W and S/W up-gradation.

RSO - NBSS

initial

4

For internal use


Controllers- RNCs

RNC 196: First WCDMA

RNC and have 8 step up-

gradation steps with latest

RU30 SW.

Three capacity steps

150 Mbit/s,

300 Mbit/s

450 Mbit/s

RNC is built on IPA 2800 platform. Scalability and flexibility for network evolution.

2000 Mbps in download,

600Mbps upload

RNC196 mcRNC RNC 2600 RNC 450

Highly scalable & compact.

Data capacity upto

50 Gbps.

(Iub interface throughput )

Up to ~30,000 cells.

Scalable : 2-8 modules

RSO - NBSS

5

For internal use


Mechanics

Dept. / Author / Date

M80 & M90

M2000

M98 (M98N, M98F, M98F2, M98A)

ATCA

MSC, HLR

RNC 196, RNC 450, RNC 2600

MSCi, HLRi, Transit MSCi, MSS, SGSN, BSC3i, TCSM3

ATCA MSS, ATCA SGSN, Flexi NS

Box HW mcBSC, mc RNC

M2000 ATCA

Box (Advanced Telecommunications Computing Architecture)

RSO - NBSS

6

For internal use


IPA2800

IPA2800 is a SW and HW Platform for Network Elements

IPA2800 is Modular, Scalable and Redundant

Modular

Refers to the design of any system composed of separate components that can be connected together.

The opposite of a modular architecture is an integrated architecture, in which no clear divisions exist between components

Independent smaller parts (modules) and use them in different systems to drive multiple functionalities.

Personal Computers ( PCs) are classic example of a modular system . Processors, main boards, graphics cards, hard drives, power supply units, optical drives, etc are independent units assembled to get a compelte system

RSO - NBSS

7

For internal use


IPA2800

IPA2800 is a SW and HW Platform for Network Elements

IPA2800 is Modular, Scalable and Redundant

Scalable

Refers to how well a hardware or software system can adapt to increased demands.

Redundant

N+1 Principle: Units which are used in call setup and not critical for calls in progress.

2N Principle: Units which are critical for calls in progress

SN+ Principle:

Units can have load sharing mode.

RSO - NBSS

8

For internal use


IPA2800 Basic Principle

Operation and maintenance

Control Part

Network Interface Switching

Subscriber lines

Trunk circuit lines

Load sharing based on functional distribution

Network of independent computers

High speed Ethernet connectivity for inter-computer communications

Fault tolerance achieved by hardware redundancy

RSO - NBSS

9

For internal use


IPA2800 M2000 & Box HW DX200 M92, M98 & Box HW Mechanics Type

IPA2800 - ATM DX200 MB & LAPD

System Internal Communication

IPA2800 - HMS DX200 Wired Alarms

Hardware Management

System

Platform : IPA2800 (RNC) vs. DX200 (BSC) Hardware Platform

Improved & new hardware for computing & processing to adapt with new interfaces. In an IPA2800 network element, each functional unit usually consists of one plug-in unit, which has a fixed capacity. Compatible with new system communication and advanced applications.

RSO - NBSS

10

For internal use


IPA2800 ATM DX200 TDM

Basic Switching Technology

IPA2800 Improved POSIX DX200 POSIX Computing

Platform : IPA2800 (RNC) vs. DX200 (BSC) Computing & Swithching Platform

Both Platform support some common features: Distributed Processing Architecture Modularity Common Hardware Modular Software Fault Tolerance

RSO - NBSS

11

For internal use


Computer System

RSO - NBSS

12

For internal use


Redundancy Types

N+1/R

N+1/L

Used in the RNC

Redundancy Types

2N

No Redundancy

N+1

RSO - NBSS

13

For internal use


Redundancy principles : 2N

Active

Hot Standby

Faulty

Active

Spared unit is ready to take over the action all the time. - SFU, RSMU, TBU, NPGEP etc.

RSO - NBSS

14

For internal use


Redundancy principles : N+1/Replaceable

Active

Active

Stand by

Active

Active

Active

Stand by

Active

Active

Faulty

Active

Active

In case of failure, information of WO unit must be loaded into the SP one before SP starting the operation- ICSU

RSO - NBSS

15

For internal use


Redundancy principles : SN+ or N+1/Load sharing

Active

Active

Active

Active

25%

25%

25%

25%

Active

Active

Active

Active

Active

Faulty

Active

Active

33%

33%

33%

0%

The same as n+1, but the redundant unit is used to shared the load of each WO unit.

i.e. DMCU in RNC

RSO - NBSS

16

For internal use



Sub rack, Rack, Cabinet, Functional unit, PIUs, Cards..... ??

RSO - NBSS

17

For internal use


Mechanics POWER SUPPLYCONNECTOR GROUP

FILTER

FUSE UNIT(PDFU)

DOOR RIGHT

RAIL FORSHELVES

CARTRIDGESHELF

COVER FOR WHEEL BOXADJUSTABLE FEET WHEEL

HORIZONTALGROUNDINGBAR

DOOR LEFT

CARTRIDGE

SIDE COVERPLATE - SCPOR EMC GASKETFRAME

VERTICALGROUNDING

BAR

COVER FORPOWER SUPPLY

CABLESUPPORT

Racks can be equipped with four or five shelves on which the cartridges are laid

Cartridge sizes 1/1, 2/3, 1/2, 1/3, 1/4 or 1/6 of the shelf width

Cartridge has typically its own power supply

P L U G - I N U N I T

C A R T R I D G E

1 / 2

1 / 3 1 / 4 1 / 6

1 / 1

D X 2 0 0

R A C K

RSO - NBSS

18

For internal use


Mechanics (M2000) Cabinet mechanics for indoor use Cabinet contains 4 subracks, 4 fan trays, and power distribution equipment

EMC shielding at subrack level rather than at cabinet level

Front and back cabling Based on metric dimensioning (IEC/ETSI) Old hardware mechanics (prior to A5):

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

SRA1 Subrack, ATM, type 1


FTRA Fan Tray

New hardware mechanics (A5HW): EC216 Equipment Cabinet, 2100*600*600 mm


FTRA-B Fan Tray 1200W

RSO - NBSS

19

For internal use


Generic Block Diagram of IPA2800

MXU

MXU

TBU OMU

WDU

E1/T1/JT1 ATM

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

ATM

Ethernet 100Base-TX

CU*

NIS1 NIP1

NIWU

MXU

OMS

A2SU

CU*

SPU*

FDU

E1/T1/JT1 TDM

IPFE

Ethernet 1G IPGO/GE

IWS1E/T STM-1 TDM

Ethernet 100M


ATM

NPS1

NPGE Ethernet 1G

SFU

SWU

Ethernet 100Base-TX

CU*

CU*

Switching Platform

Computing Platform

RSO - NBSS

20

For internal use


OMU

lower traffic capacity

higher traffic capacity

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

NIWU

FDU WDU

Generic Functional Architecture of IPA2800 ATM E1/T1/JT1

1.5-2 Mbit/s

NIP1

DMCU /TCU

MXU

MXU

TBU Ethernet

10/100 Mbit/s

ATM STM-1 155 Mbit/s

NIS1 NPS1

OMS

Interface Functions

Switching Functions

Control Functions

Signal Processing

System Functions

TDM STM-1 155 Mbit/s

IWS1E IWS1T

IPGO/GE NPGE

IPFE

Ethernet 1G (optical/

electric)

Ethernet 100M

ISU /ICSU

Signaling

RSMU /CACU

Resource mangement

A2SU

SFU

SWU

RSO - NBSS

21

For internal use



Actually it is NOT

& COMPLICATED ?

Looks COMPLEX


22

For internal use

2013 Nokia Solutions and Networks. All rights reserved. 5 Feb. 2014 RSO - NBSS

ATM VCI & VPI

23

For internal use

2013 Nokia Solutions and Networks. All rights reserved. 5 Feb. 2014 RSO - NBSS

ATM VCI & VPI

24

For internal use


VCI/VPIs

VCI/VPIs

Switching

1. Well, that requires a input and output device, 2. The transportation of information from an incoming logical channel to an outgoing logical channel VCI : Virtual channel identifier VPI : Virtual path identifier

Inputs Outputs

Physical Ports


25

For internal use



VCI/VPIs

VCI/VPIs

1. Well, that requires a input and output device Ethernet / STM-1 / E1 connectivity VCI : Virtual channel identifier VPI : Virtual path identifier

Inputs Outputs

Physical Ports

Switching


26

For internal use



VCI/VPIs VCI/VPIs

1. Well, that requires a input and output device - Ethernet / STM-1 / E1 connectivity

Inputs Outputs

2. Input and output alone will not work right ? We need a switch to connect these two.

And here we call it as SFU Switch fabric unit

SFU

Switching


27

For internal use



VCI/VPIs VCI/VPIs

1. Well, that requires a input and output device - Ethernet / STM-1 / E1 connectivity

Inputs Outputs

2. We need a switch to connect these two, and here we call it as Switch Fabric Unit SFU.

SFU

Switching


28

For internal use



VCI/VPIs VCI/VPIs Inputs

Outputs

We need a switch to connect these two, and here we call it as Switch Fabric Unit SFU.

SFU

We all know that a switch wont work independently

We need somebody to

Operate\Control it

Switching


29

For internal use



VCI/VPIs VCI/VPIs Inputs

Outputs

We need a switch to connect these two, and here we call it as Switch Fabric Unit SFU.

SFU

RSMU

RSMU

Switching


30

For internal use


Lets review the BASIC functionalities of a BSC

1. Switching

Input device SFU

RSMU

Output device

switch

Controlling\ computing unit

Switching platform

Computing platform


31

For internal use


Guaranteed Capacity

Constant Transmission Delay Circuit Switching

Flexibility

Efficiency for Intermittent traffic Packet Switching

ATM Switching

Switching


32

For internal use


Guaranteed Capacity

Constant Transmission Delay Circuit Switching

Flexibility

Efficiency for Intermittent traffic Packet Switching

ATM Switching

Switching Queuing

ATM Switching Functionality


33

For internal use


ATM Switching

Switching Queuing

ATM Switching Functionality Time space switch

ATM Switching

Any Inputs can be connected to any output. Both time slot & lines can be switched.

1

2

3

n

x

1

2

3

n

y

Time Slot change

Line change

Time Stage Space Stage

MXU

SFU

MXU MXU


34

For internal use


Time space switch

Any Inputs can be connected to any output.

Both virtual connections & ports can be switched.

In ATM technology, it is easier to design switching devices with high capacity and low delay.

1

2

3

n

Cell x

1

2

3

n

Cell y

VC / VP change

Line change

Time Stage Space Stage

ATM Switching : Time slot is replaced with Virtual Connections / Ports

RSO - NBSS

35

For internal use


ATM Switching

Switching Queuing



36

For internal use


Queuing


The number of input staying in the system including the ones being under service. The service discipline determines the rule according to the next input is selected. The most commonly used laws are :

FIFO

First in First out

Who comes earlier leaves earlier

LIFO

Last in First out

Who comes later leaves earlier

RS

Random service

Input is selected randomly

PRIORITY

Customized Preferences

Input is selected as per the priority settings


37

For internal use


ATM Switching

SFU

Computer / Processing Units

Ports

Computer / Processing Units

External

Interface

Units

Via MXU

Via MXU

ATM Switching

MXU

SFU

MXU NPS1

/ NPGE

RSO - NBSS

38

For internal use


Generic Block Diagram of IPA2800

MXU

MXU

TBU OMU

WDU

E1/T1/JT1 ATM


ATM

Ethernet 100Base-TX

CU*

NIS1 NIP1

NIWU

MXU

OMS

A2SU

CU*

SPU*

FDU

E1/T1/JT1 TDM

IPFE

Ethernet 1G IPGO/GE

IWS1E/T STM-1 TDM

Ethernet 100M


ATM

NPS1

NPGE Ethernet 1G

SFU

SWU

Ethernet 100Base-TX

CU*

CU*

Switching Platform

Computing Platform

RSO - NBSS

39

For internal use


SF20H

Switching Fabric Unit (SFU) are required for switching both circuit and packet-switched data channels. Also used for connecting signalling channels and for the

system's internal communication. Provides redundant, fully accessible and non-blocking

connection at ATM level.

SFU Switching Fabric Unit

SFU

Computer

/ Processin

g Units

Ports With a total of 32 ports, the SF20H provides a 1.655 Gbit/s serial switching fabric interface with single port.

Ports can be combined for higher capacity ports.

The port redundancy of the ports is implemented by mirroring two fabric ports together

Computer

/ Processin

g Units

External

Interface

Units

Via MXU

Via MXU Test Purposes


40

For internal use


Multiplexes/de-multiplexes traffic from tributary units to the ATM switching fabric vice versa. Enable connection of the low-to-medium bit-rate signal

processing units and computer units, as well as low-bit-rate network interface units, to the ATM switch fabric.

MXU Multiplexer Unit

SFU

.

Ports

The port redundancy of the ports is implemented by mirroring two fabric ports together

External

Interface

Units

MX1G6-/A

Test Purposes

Netw

ork

Proc

essor

Trib

utar

y

Units

Trib

utar

y

Units

1

20

41

For internal use


RNC 2600

RNC 2600 STEP-1

RNC 2600 STEP-2

RNC 2600 STEP-3

RSO - NBSS

42

For internal use


RNC 2600 Capacity

RSO - NBSS

43

For internal use


RNC 2600 Units Redundancy Type

RSO - NBSS

44

For internal use


RSMU

Switch

Management

RSMU Resource and Switch Management unit

Resource

Management

Functions of the ATM Switch Management controls and supervises the SFU, MXUs. Transmission resource management finds free circuits (hunting), connects and

releases all Connections

Functions of DSP Resource Management Supervision & management of DMCU. Management of ATM connections within

DMCU. Allocation of DSPs & associated

computer resources to different tasks. Software dowloading of DMCU.

Call Connection: It also performs the call

connection related functions according to requests received from signalling computer units (ICSU).

Having ATM interface with

MXU

Call Connection


45

For internal use


DMCU

L1

Functionalities

DMCU Data and Macro Diversity Combining unit

L2

Functionalities

Handling of the L1 Functionalities like WCDMA L1 functionalities Macro diversity combining Outer loop Power Control

Handling of WCDMA L2 Functionalities WCDMA L2 protocol processing RLC-U & RLC-C, MAC-C & MAC-D protocol

processing. Packet data convergence protocol

processing : Header compression HSPA signal Processing : MAC-SH & EDCH

It uses configurable dynamic signal processing platform in which signal processing tasks can be configured and altered dynamically for each DSP.

DSPs and RISC processors of the unit are automatically allocated within the RNC according to the capacity need.

Encryption, ciphering related tasks are performed by DMCU.

It also handles GPRS Tunneling protocol termination

CDSP & Macro

Diversity


46

For internal use


Micro Diversity Combining

Received signals (+noise) Time and phase adjustment

Combined signal (+ residual noise)

Transmitted signal

WBTS UE

RSO - NBSS

47

For internal use


Macro Diversity Combining

WBTS2

WBTS3

WBTS1

SRNC

DRNC

Macro Diversity Combining Point

Active Set

Core Network

UE

UL Direction

The aim is to combat fading and to increase the received signal strength and signal quality.

RSO - NBSS

48

For internal use


OMU

OMS

Collects hardwired alarms within the RNC

OMU Interface for

USB I/O Controller

Houses to mirrored Hard

disks

Service Terminal

Localizes faults & Initiates recovery

HMS

RSO - NBSS

49

For internal use


OMU: Operational and Management Unit Functions:

- Cellular management Handles all RNC's crucial upper-level system maintenance functions Serves as an interface between OMS and the other units of the network element Maintains radio network configuration and recovery Houses radio network database and ATM/IP configuration database Has dedicated storage devices

- Basic maintenance

Hardware configuration management HMS supervision Centralised recovery functions

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

Interfaces of OMU : Ethernet interface to OMS. SCSI interface for mass memory devices (when not using HDS-C). Service Terminal Interface. Hardware management System (HMS) Interface.


50

For internal use


ICSU

Signalling

ICSU Interface Control and Signalling unit

Radio Resource

Management

Handling of the Signalling part Signalling protocols to Iu, Iub, and Iur

interfaces. Handling all layer 3 protocols in RNC like

RANAP, NBAP etc. Monitoring and recovery of the signalling

links.

Functions of Radio Resource Management Admission control, Handover control. Load Control, Power Control Packet Scheduler control Allocation of DSPs & associated

computer resources to different tasks.

Location calculations for location based services.

Transport network level singalling protocol - ALCAP.

Location based

services


51

For internal use


Radio Resource Management

Target for RRM is to ensure the RAN offers:

The planned coverage for each targeted service High capacity i.e. low blocking (new calls, handovers) The required Quality of Service (QoS) Optimize the use of available capacity (priorities)

By continuously monitoring/adjusting how the available resources are used in accordance with user requests

Radio Resource Management (RRM) is responsible for optimal utilization of the air interface resources.

RSO - NBSS

52

For internal use


RRM is made up of a number of closely interdependent functions (i.e. algorithms) These functions can be divided into;

Cell Based

- Load Control (LC)

- Admission Control (AC)

- Packet Scheduling (PS)

- Resource Manager (RM)

Connection Based

- Handover Control (HC)

- Power Control (PC)

RRM Functional Split

PC

HC

Connection based functions

LC

AC

Cell based functions

PS RM

53

For internal use


RRM Functionalities Network Element Level

MS

Power Control

NodeB

Power Control

Load Control

RNC

Power Control

Load Control

Admission Control

Packet Scheduler

Handover Control

54

For internal use


CCP18-C CCP18-A

CCP18

Main Control Processor unit in IPA2800 Platform. ATM connections to other plug-in units. This is done by an interface to the ATM multiplexer (MXU). Common H/W platform for RSMU, ICSU & OMU (with SCSI).

CCP18-A

Computer

/ Processing Units

HMS Master/Slave

Node

Ultra 2/3

SCSI Interface

Up to 16 units

USB 1.1

Interface

PCI Bus Interfaces

I/O Controller Interfaces

CCP18-C : No SCSI Interface No HMS Master Node No USB Interfaces


55

For internal use


CCP1D-A CCP1D-A

Main Control Processor unit in IPA2800 Platform R6. ATM connections to other plug-in units. This is done by an interface to the ATM multiplexer (MXU). Common H/W platform for RSMU, ICSU & OMU.

CCP1D-A

Computer

/ Processing

/ HDS-

C Units

HMS Master/Slave

Node

Serial

Interface

USB 2.0

Interface

PCI Bus Interfaces

I/O Controller Interfaces


56

For internal use


HDS-B : OMU's Storage Device

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

Hard Disk Drive (HDD): One for OMU and

another for OMS

- 73 GB formatted storage capacity/disk

- Redundancy type : 2N

- External devices: USB memory stick, one

for each OMU (for CCP18-A only)

HDS-BHDD 0(OMS)

WDU 0(OMU)

OMU 0OMS

HDS-B

HDD 1(OMS)

WDU 1(OMU)

OMU 1

SCSI 0

SCSI 1

SCSI 0

SCSI 1 HD: AHD: B

HD: AHD: B

HDS-B Connectivity

Principle


57

For internal use


Operations and Maintenance (O&M)

- Operations and Maintenance (O&M)

Provides the means for operations personnel to maintain the RNC and Radio Network in optimal condition

- Easy to use Graphical User Interfaces (GIUs) for

Configuration Fault Management Performance Management

- Accessible via Local Management System (LMS) or Network Management

System (NMS)

Configuration Reconfiguration of the RNC Reconfiguration of the WBTS Reconfiguration of the Radio Network Parameters Support for remote software upgrades to the RNC and WBTS

58

For internal use


Operations and Maintenance (O&M)

- Fault Management

- Continuous checking of the network to detect any irregularities in the operation of

the Network Elements

- Identification of faulty units in the RNC and notifying the NMS and recovery

system of the problem

- Isolates the faulty unit/s from the system and places spare units into operation if

they exist

- Fault diagnosis system pinpoints the exact nature of the problem and verifies the

status of the faulty unit and the system as a whole

- Maintains an alarm and events history

- Performance Management

- Continually monitors and collects performance statistics from the network and

network elements

- Provides the ability to set triggers in order to identify possible problem areas in

the network before they become a real problem

59

For internal use


OMS : O&M Server

Performs RNC element management tasks. Provide platform for different O&M applications. OMS offers adaptation, post processing & value adding functions between NMS & RNC. It provides high availability, security, flexibility & uses the LINUX operating system. Sharing Hard disk drive with OMU through SCSI Interface. Communication between OMS & other RNC units is through Ethernet switch card (ESA24). Duplicated SCSI & Ethernet interfaces.

60

For internal use


Network Interface Unit NPS1(P)

- Functions: Provides 8 SDH STM-1/STM-4 interfaces and an RJ45

connector, and handles multiprotocol packet processing at wire speed and network connectivity

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

Performs AAL2 minipacket switching. Translates ATM header. Performs UPC/NPC, traffic management, performance

management and performance data collection. Provides optional reference clock for timing and

synchronisation.

- Redundancy type: NONE or 2N - Plugin unit type

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


61

For internal use


Network Interface Unit NPGE(P)

- Functions:

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

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

interfaces

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

Translates IP header. Performs traffic management, performance management and

performance data collection.

Terminates GTP protocol when used at Iu-PS.

- Redundancy type: NONE or 2N

- Plugin unit type

NP2GE, NP2GE-A, NP2GE-B


62

For internal use


RNC2600 - Physical Interfaces

The physical network interfaces provide the means to connect to external elements and execute

Physical layer functions ATM layer functions

- Policing - Statistics - O&M - Buffer management - Scheduling

If IP transport QoS is used the O&M statistics are handled at IP level and the IP packets then mapped to the Ethernet frames

One network interface unit may include more than one physical interface depending on the type

Any interface unit can be configured as an Iu, Iub or Iur interface In addition to the network interfaces, synchronisation and Local Area Network

(LAN) interfaces are also provided

63

For internal use


RNC2600 - Physical Interfaces

STM-1 / OC-3 - The NPS1 or NPS1P functional unit offers ATM over SDH/Sonet interfaces

The NPS1P offers MSP 1+1 and APS 1+1 protection - Plug in unit type is NP8S1-B for both NPS1 and NPS1P

- Each plug in unit contains 8 x SDH STM-1/Sonet OC-3 optical interfaces

Gigabit Ethernet - The NPGE or NPGEP functional unit offers IP over Ethernet interfaces

The NPGEP supports 2N redundancy - Plug in unit type is NP2GE for both NPGE and NPGEP

64

For internal use


RNC2600 - Capacity licensing

The RNC2600 capacity licensing allows for capacity configurations based upon the actual RNC2600 traffic

This allows for cost efficient usage of the RNC2600 resources in different networks

Capacity is licensed using three capacity parameters Iub PS data throughput in Mbps AMR capacity in Erlang Number of required carriers

The license keys are required to be installed in the RNC2600 The initial RNC2600 capacity is defined when ordering the RNC2600

The corresponding license file will be delivered with the RNC2600 RNC2600 capacity upgrades can be performed by ordering new capacity license

files and activating them via NetAct Local Element Manager

65

For internal use


RNC2600 - Capacity licensing

Capacity can only be upgraded to a level supported by the hardware that is already available in the RNC2600

The hardware requirements of certain features may affect the overall capacity capability of the RNC2600

The capacity figures are calculated without considering any of the optional features

66

For internal use


RNC2600 - Power Redundancy

Power to the RNC2600 is protected by a duplicated power supply feed from the rectifier/s and Battery/ies

At cabinet level the duplicated power is distributed via MCBs to each sub rack in the same cabinet

At sub rack level each duplicated power feed is received by the PD30 unit that distributes 4 duplicated 5A power feed lines to the plug in units via the backplanes

67

For internal use


RNC2600 - Forced Cooling System Redundancy

Each sub rack and fan tray is connected to separate thermal circuits A failure in one cooling system does not affect the cooling system for other

sub racks

The Fan trays are supervised by the PD30 supervisory block in each sub rack

In case of a single fan unit failure the remaining fans are switched to full rotational speed in order to maintain sufficient cooling under the specified

environmental conditions

68

For internal use


Timing and Synchronisation - Line Timing

The Synchronisation unit has 5 interface inputs available

The synchronisation unit inputs are connected via cable to 3 selected network interface units (NPS1 or NPS1P)

Two External interfaces can also be provided.

The synchronised timing signal is then delivered to the other timing units and then distributed to all the other RNC2600 plug in units

Line timing is also supported on E1/T1 interfaces

Bus 0

term.

Bus 1

term.

Bus 0

term.

Bus 1

term.

TBUF

TBUF

TBUF

TBUF

TBUF

TBUF

TBUF

TBUF

RNAC RNBC

0

1

TBUF

TBUF

TSS3 1

TBUF

TBUF

TBUF

TBUF

TSS3 0NPS1P 0/NPS1 0

00

11

1

Subrack 1

Subrack 2

Subrack 3

Subrack 4

NPS1P 1/NPS1 1

NPS1P 2/NPS1 2

Timing signal distribution can also be provided in star topology.

69

For internal use


Traffic Flow Permanent signalling links

ATM Iub/Iu/Iur

IP Iub/Iu/Iur

SFU

RSMU

DMCU

ICSU

NIU - NPGE(P)

NIU - NPS1(P)

SWU

OMS

HDD WDU

EHU

TBU

ICSU

DMCU OMU

PDU

Standalone or Integrated

70

For internal use


SFU

RSMU

DMCU

ICSU

NIU - NPGE(P)

NIU - NPS1(P)

SWU

OMS

HDD WDU

EHU

TBU

ICSU

DMCU OMU

PDU

Traffic Flow Common control channel

ATM Iub

IP Iub


71

For internal use


SFU

RSMU

DMCU

ICSU

NIU - NPGE(P)

NIU - NPS1(P)

SWU

OMS

HDD WDU

EHU

TBU

ICSU

DMCU OMU

PDU

Example of Traffic Flow Dedicated control channel

ATM Iub

IP Iub


72

For internal use


SFU

RSMU

DMCU

ICSU

NIU - NPGE(P)

NIU - NPS1(P)

SWU

OMS

HDD WDU

EHU

TBU

ICSU

DMCU OMU

PDU

Traffic Flow CS user data

ATM Iub

IP Iu-CS


73

For internal use


SFU

RSMU

DMCU

ICSU

NIU - NPGE(P)

NIU - NPS1(P)

SWU

OMS

HDD WDU

EHU

TBU

ICSU

DMCU OMU

PDU

Traffic Flow PS user data over DCH

ATM Iub

IP Iu-PS


74

For internal use


SFU

RSMU

DMCU

ICSU

NIU - NPGE(P)

NIU - NPS1(P)

SWU

OMS

HDD WDU

EHU

TBU

ICSU

DMCU OMU

PDU

Traffic Flow PS user data over FACH/RACH

ATM Iub

IP Iu-PS


75

For internal use


SFU

RSMU

DMCU

ICSU

NIU - NPGE(P)

NIU - NPS1(P)

SWU

OMS

HDD WDU

EHU

TBU

ICSU

DMCU OMU

PDU

Traffic Flow HSPA user data

ATM Iub

IP Iu-PS


76

For internal use


For internal use


RNC Preventive Maintenance & Trobleshooting Prm, Alarm handling, Health Check & ST


77

For internal use


System Maintenance

Mechanisms to guarantee high availability and required performance in fault situations

Maintenance tasks preventive maintenance fault control fault correction

78

For internal use


System Maintenance Principles

Failure

Fault Detection

Supervision system

Alarm printouts

Updating of failure

information

Alarm message

Alarm system

Fault elimination

Activation of recovery

Recovery system

Fault elimination

Activation of fault location

Fault location system

HW supervision SW supervision Real time supervision

Alarms collection Alarm storage Output alarms Control alarm output Startup recovery Informing about an alarm

Uses redundancy/restarts Controls restarts Starts Automatic fault

location

Locates fault Uses HW config data Provides alarm printout

and LED alarms

RSO - NBSS

79

For internal use


Alarms Classification

- The alarms arriving in the Network can be divided into various classes

depending upon the criterion chosen.

Alarms division in Mobile Communication System is based on:

a. Network Element Environment

b. Network Architecture

c. Severity of Alarm

d. Network Service Alarms

80

For internal use


Types of alarms:

Network Element Environment

Network Element Environment

i. External Alarm ii. Internal Alarms

These alarms are not caused by Network Element itself. They can effect the operation of Network Element in many ways. External alarms can be configured on a Network Element in

accordance with the Network Provider preferences and requirements. Example:

These alarms are generated by the Network Element itself. These alarms represent some malfunction in the operation of Network Element. Both HW and SW alarms come under this category. Example:

7415 *** On_air_N

PROP_82110B ;; ; ;

PLMN-PLMN/RNC-1017/WBTS-33917

EXTERNAL AL 15

Started 2007-03-06 10:36:17

Notif ID 20465

Suppl Info Mains Break

Object 82110B EQUIPMENT

Ctrl NE RNOREBR2 Orebro On_air_N

7653 *** On_air_S

25154A RNJONKP1 IF15/P2

PLMN-PLMN/RNC-1011/WBTS-16027/WCEL-2016029

CELL FAULTY

Started 2007-03-06 08:27:59

Notif ID 9373

Suppl Info Cell power monitoring

User info

Diag Info 02 03 03 0125WPAJ 03 00

Object 25154A3 EQUIPMENT

Ctrl NE RNJONKP1 Jonkoping On_air_S

81

For internal use


Types of alarms: Severity of the Alarm

Severity of Alarm

Notice Alarms

Disturbance Alarms

Minor Alarms

Major Alarms

Critical Alarms

These alarms only inform about an event giving information about the situation in the Network Element. For example the user is informed of a unit state change by a notice.

Disturbance alarms are used for informing about temporary disturbance situations that means informing about a short failure event that does not have any permanent effect on service.

Minor alarms ( one star alarms) give information to help the operator to decide that measures should be taken to remove the alarm.

Major alarms ( two stars alarms) dont threaten the operation of the system; the fault requires operator action during normal working hours.

Critical alarms ( three stars alarms) require immediate FM group action at all times.

82

For internal use


Alarms Classes and Numbers

MML: command class "A Alarm Classes

Notice

Disturbance

Alarm *

Alarm **

Alarm ***

Alarm Number

Notice 0-999

Disturbance 1000-1999

Alarm 2000-3999

Diagnostic 3700-3999

External 4000-5999

BTS 7000-7999

OMS 70001-71999

83

For internal use


Alarm system in NSN RAN Equipment

1. Alarm blocking:

2. Alarm canceling:

3. Alarm history:

4. Operation instructions:

5. External alarm:

block incoming alarm & alarm printing to avoid excessive repetitive alarms, use "AF"

can by done by system or user (except external alarm that user must do it), use "AA"

- in WDU / Hard disk of OMU - use "AH"

- extra info in alarm printout, e.g.. Who takes care of this alarm - use "AO"

- use "AQ : External alarm connections handling - e.g.. Room temperature

84

For internal use


Alarm system in NSN RAN Equipment

Alarm Handling

Alarm Printing Handling

85

For internal use


Alarm System

Structure of the alarm

1. Type of alarm printout

3. Exchange 4. Remote Object

5. Location of Alarm Object

6. Event type

COMM communication failure QUAL quality of service PROCES processing failure EQUIPM equipment failure ENVIR environmental failure

8. Date

9. Time

10. Urgency level

*** requires immediate actions ** requires actions during working hours * no actions required

11. Printout type

16. Program Block : Related to alarm

13. RNW Object Name

2. Consecutive alarm number

14. Alarm number

Alarm Text

Supplementary text

Supplementary information fields

Supplementary text

a. Rack b. Shelf c. Plug-in unit location d. Plug-in unit type e. Unit f. Subunit

Example:

HST (19437) NBSS01 EQUIPM 2014-01-25 21:14:15.00 .. CANCEL WBTS-1402 WCEL-14028 U_KAN_Nirmalagi 7654 CELL OPERATION DEGRADED OBH_QX OMU-0 64 0B 64 2010FRGP 01 00 Failure in optical RP3 interface

ALARM fault situation CANCEL fault terminated DISTUR disturbance NOTICE notice

7. Recovery Info *RCY* - send to system, if requires recovery action to perform

17. Computer Sending the Alarm

18 to 23 : Provide diff. Info like flow control etc.

Supplementary information fields

12. Alarm Object expressed either as a single object or in the form of an object hierarchy. WBTS WCEL etc.

86

For internal use


NSN Definition of Maintenance procedures

Maintenance

Preventive Maintenance

Provide regular maintenance to the RNC in order to reduce the possibility of failures or decreasing of performance

Corrective Maintenance

The activity in order to rectify or solve faults happened in the network. This usually carried out after a trouble shooting procedure.

Detecting, tracing and analysing the mistakes of fault in the system networks

Troubleshooting

RSO - NBSS

87

For internal use


Preventive Maintenance

Daily HC Monthly PrM Pre festival Half Yearly

Comp unit status Status of all links Signaling load Unit status SYNC Status Disc unit status Active alarms Blocked alarms

Unit diagnostician Unit Switchover

Physical visit External Power supply Environmental conditions TXN redundancy

Unit working status Processor load Status of links Load distribution Service affecting alarms Call handling parameters &

timers.

Pre festival and Half yearly activities are Major activities severity level thus CH permission to be obtained before carrying out the activities.

RSO - NBSS

88

For internal use


RNC health Check report

Comp unit State

Unavailable Signaling Links

Hard Disk State

Alarm Status Measurement status Blocked Command calendar

RNC Synch and Control word value

Software consistency

SW and CD level

RSO - NBSS

89

For internal use


Functional unit states

RSO - NBSS

90

For internal use


RNC Synchronization Handling : DYI

CURRENT OPERATION MODE OF ACTIVE SYSTEM CLOCK IS: SYNCHRONIZED CURRENT VALUE OF CONTROL WORD OF SYSTEM CLOCK OSCILLATORS ARE: ACTIVE: 2066 SPARE: 1886 SITUATION OF EXTERNAL OUTPUT SQUELCHING: DISABLED SITUATION OF REVERTIVE SWITCHING: ENABLED SITUATION OF SPECIAL CONFIGURATION: DISABLED SSM VALUES USED DURING REFERENCE SELECTION: YES

RSO - NBSS

91

For internal use


State changes in computer

No redundancy

SE-NH SE-OU TE-EX WO-RE WO-EX

Ex: OMS in RNC

RSO - NBSS

92

For internal use



2N redundancy

WO-EX

SP-EX

WO-RE

SP-RE

TE-EX

SP-UP

SE-OU

SE-NH

Ex: RSMU in RNC

RSO - NBSS

93

For internal use



N+1/R redundancy

WO-EX

SP-EX

WO-RE

SP-RE

SE-OU

SE-NH

Ex: ICSU in RNC

TE-EX

SP-UP

RSO - NBSS

94

For internal use


Unit State Handling in MML

WORKING STATE AND RESTART HANDLING COMMAND < ZUSI;

LOADING PROGRAM VERSION 6.12-0

WORKING STATES OF UNITS 2010-02-24 12:45:26

UNIT PHYS LOG STATE INFO OMU-0 0000H 4002H WO-EX - OMU-1 0001H 4002H SE-NH - MXU-0 0017H 4242H WO-EX - MXU-1 001CH 4242H SP-EX - ... DMCU-0 > WO-EX - DMCU-1 > WO-EX - ...

COMMAND EXECUTED

95

For internal use


Interrogation of Child Unit States

WORKING STATE AND RESTART HANDLING COMMAND < USI:DMCU,0::FULL;

LOADING PROGRAM VERSION 6.12-0

WORKING STATES OF UNITS 2010-02-25 10:49:13

UNIT PHYS LOG STATE INFO DMCU-0 WO-EX - DMPG-0 000CH 4470H WO-EX - DSP-0 WO-EX - DSP-1 WO-EX - DMPG-1 0010H 4471H WO-EX - DSP-2 WO-EX - DSP-3 WO-EX - ...

96

For internal use


Disk Handling

Two main choices to interrogate disks and copy info: - MML

Interrogation Command IW Copying Command IBC

- Service terminal

Interrogation/Copying with MASHAN

97

For internal use


MASHAN

MAS> M:W0-ABCDEF.ABC:2,F0-FEDCBA.CBA;

ABCDEF.ABC: 0010H BLOCKS COPIED

Interrogation

Copying

0000-MAS> X:W0-/;

VOLUME DIRECTORY .DIR

CREATED 89-01-01 LAST WRITE 89-01-01

DIRECTORY OF /

CREATED 89-01-01 LAST WRITE 89-01-01

NUM NAME EXT VER DATA SIZE CREATED LAST MOD ATTR

YY-MM-DD YY-MM-DD

0001 DISK .DATA:01 FFFFFE00 97-12-11 97-12-11 DW

0002 DISK .TEST:01 FFFFFE00 97-12-11 97-12-11 DW

0003 SECTORS .MAP :01 FFFFFE00 97-12-11 97-12-11 DW

0004 SECTORS .BAK :01 FFFFFE00 97-12-11 97-12-11 DW

0007 080110 .dir :01 00000000 10-01-18 10-01-18 D

0008 121009 .dir :01 00000000 09-10-12 09-10-12 D

TOTAL FFFFF800

LISTED LABELS 00000045

DISK SIZE 08376D74H BLOCKS

98

For internal use


Show Software Package Information

< ZWQO:CR; PACKAGES CREATED IN OMU: SW-PACKAGE STATUS DIRECTORY ENVIRONMENT DEF ACT PACKAGE-ID (REP-ID) DELIVERY CD-ID RNCHOT FB RNCHOT Q1 1.24-0 Y Y C2 7.15-1 CID000QX 1.1-0 Q1012400 BU Q1012400 Q1 1.24-0 - Y C2 7.15-1 CID000QX 1.1-0 FB010726 UT FB010726 Q1 1.24-0 - Y C2 7.15-1 CID000QX 1.1-0 TRAINING UT TRAINING Q1 1.24-0 - Y C2 7.15-1 CID000QX 1.1-0 TEST UT TEST Q1 1.24-0 - Y C2 7.15-1 CID000QX 1.1-0

MMI command Printout Description

Build_Name Build_Dir

99

For internal use


Statuses of Created SW Build

UT

UT

FB BU

NW UT

Fallback copy ZWKS...

Rollback statuses ZWSR

Rollback statuses

ZWSR

Change of status ZWSC...

Change of status ZWSC...

Switch active package ZWSS...

Rollback statuses ZWSR

Switch active package ZWSS...

Fallback copy with parameter "FULL" ZWKS...

...

100

For internal use


Safecopying Recommendations

- Take fallbacks during low traffic, e.g. at night

- Avoid database updates or other changes during the fallback copying

- Check recent FB build prior major changes in soft- or hardware

- Take safecopies and backups systematically, the system generates an alarms (2518) if fallback

is too old

- Note that automatic fallback via command calendar assumes that the network element is stable

- Have initialized hard disks available

- Train at least two persons to take safecopies, backups and to restore SW build from fallback or

backup

- Note command calendar files are not copied to Fallback build

101

For internal use


Verify Fallback Build

ZWKP... DISPLAY FALLBACK LOGFILE -> displays phases, files and errors of the fallback process

ZWQB ... VERIFY SOFTWARE PACKAGE -> verifies that SW build corresponds to the MAFILE

Related Alarms concerning Fallback build:

- Notice 0027 displays the state of the fallback copying during the process

- Alarm 2393 "Fallback copying terminated in error"

- Alarm 2394 "Error in finishing fallback copying"

- Alarm 2518 "No valid fallback copy for default package"

102

For internal use


Backup Copying FB Build to Optical Disk or USB Stick

IWY:D:UNIT=OMU,PATH=/FB080801,DRIVE=FDU-N0,;

-> define Destination directory

FB_build

FDU-N0

WDU-S

/

FB_build

/

IWY:S:UNIT=OMU,PATH=/FB080801,DRIVE=WDU-S,;

-> define Source directory

IWL::F0,NODEF::FB080801:;

-> create destination directory on FDU

IBC:,,%,%,,,,,,DIR::;

-> copy all files and directories

COPYING IPA2800 OMU WDU-S: --> IPA2800 OMU FDU-0:

NODEF:FB080801/ --> NODEF:FB080801/ . . . SUCCEEDED : 1287

FAILED : 0

TOTAL : 131212976 BYTES

Whole FB_build Backup takes about 15 minutes !

Example for a successful printout !

MMI

commands

103

For internal use


Thank You

NBSS_RNC Architecture and Functionalities_v0.1

Documents

Transcript of NBSS_RNC Architecture and Functionalities_v0.1