01 Mn1783eu11mn 0001 Introduction

7/28/2019 01 Mn1783eu11mn 0001 Introduction

1/70

Introduction Siemens

MN1783EU11MN_0001 2002 Siemens AG

1

Contents

1 Structure of a GSM PLMN 3

1.1 Components of a GSM PLMN 4

1.2 Structure of the NSS 6

1.3 Structure of the BSS 10

1.4 Structure of the OSS 12

1.5 Transmission on the terrestrial interfaces 14

1.6 Flexible Abis Allocation Strategy (FAAS) 16

1.7 Transmission on the air interface 22

1.8 Signaling in the BSS 24

2 Radio Commander (RC) 27

2.1 General RC Setup 28

2.2 RC Hardware 30

2.3 RC tasks 50

3 Exercise 63

4 Solution 67

Introduction


2/70

Siemens Introduction

MN1783EU11MN_0001

2002 Siemens AG

2


3/70



3

1 Structure of a GSM PLMN

RC

SC

MSC

HLR

VLR

EIRAC

BSC

BTS

T

R

A

U

other

networks

PSTN

ISDN

Data

Networks

MS =

ME + SIM

IN

Fig. 1


4/70


MN1783EU11MN_0001

2002 Siemens AG

4

1.1 Components of a GSM PLMN

A GSM PLMN can be divided into three main parts: the Network Switching Sub-System (NSS)

the Radio Sub-System (RSS), itself consisting of the

Mobile Station (MS), and the

Base Station System (BSS),

and the Operation Sub-System (OSS)


5/70



5

PLMNPublic Land Mobile Network

MSMobile

Station

BSSBase Station

Subsystem

NSSNetwork Switching

Subsystem

OSSOperation SubSystem

RSSRadio

SubSystem

Fig. 2


6/70


MN1783EU11MN_0001

2002 Siemens AG

6

1.2 Structure of the NSS

The NSS is separated in a circuit switched and packet switched part.

1.2.1 Circuit-Switched Core Network

The circuit switched part consists itself of five parts:

the Mobile services Switching Center (MSC)

the Home Location Register (HLR)

the Visitor Location Register (VLR)

the Authentication Center (AC)

the Equipment Identity Register (EIR)

The Mobile services Switching Centeris responsible for establishing traffic channelconnections

to the BSS,

to other MSC, and

to other networks (e.g., public switched telephone network (PSTN)).

The database of a MSC contains information for the routing of traffic channelconnections and handling of the basic and supplementary services. The MSC alsoperforms administration of cells and location areas.

Since in a PLMN the mobile subscriber is not permanently connected to a MSC, thesubscriber administration is performed by a network component called HomeLocation Register.

The Visitor Location Registercontains the relevant data of all mobile subscriberscurrently located in the service area of a MSC.

The purpose of the Authentication Centeris to protect the network againstunauthorized users. The authentication feature ensures that the user (mobile

subscriber) is who he claims to be. Subscriber authentication is performed at eachregistration and at each call set-up attempt (mobile originating or terminating).

The Equipment Identification Registeris a database that stores the InternationalMobile Equipment Identity (IMEI) numbers for all registered Mobile Equipment (ME).The IMEI uniquely identifies all registered ME. There are three classes of ME that arestored in the database, and each group has different characteristics:

the black list for mobile stations that e.g. have been reported stolen).

the gray list for mobile stations to be observed

the white list for approved mobile stations


7/70



7

Network Switching System (NSS)

MSC

VLR

HLR

MSC

VLR

AC EIR

Fig. 3


8/70


MN1783EU11MN_0001

2002 Siemens AG

8

1.2.2 Packet-Switched Core Network

The packet switched part of the NSS consists of two parts:

the Serving GPRS Support Node (SGSN)

the Gateway GPRS Support Node (GGSN)

The Serving GPRS Support Node is responsible for establishing data connections

to the BSS,

to other GPRS Support Nodes, and

to the Gateway GPRS Support Node.

The SGSN:

z is the node serving GPRS mobile stations in a region;

z traces the location of the respective GPRS MS ("routing area");

z is responsible for the paging of MS;

z performs security functions and access control (authentication/cipher settingprocedures,...).

z performs routing/traffic management;

z collects charging data;

provides interfaces to GGSN (Gn), Packet Control Unit PCU (Gb), other PLMN,HLR, VLR, SMS-GMSC, and EIR.

The Gateway GPRS Support Node is responsible for establishing data connections

to the SGSN,

to other GPRS Support Nodes, and

to data networks (e.g., the Internet).

GGSN

z is the node allowing contact/interworking between a GSM PLMN and a packetdata network PDN (Gi interface);

z contains the routing information for GPRS subscribers available in the PLMN;

z has a screening function;

z can inquire about location information from the HLR (optional)

transfers data/signaling to SGSN.


9/70



9

Network Switching System (NSS)

GGSNSGSN

Fig. 4


10/70


MN1783EU11MN_0001

2002 Siemens AG

10

1.3 Structure of the BSS

The BSS includes the following: Base Station Controller (BSC)

Base Transceiver Station Equipment (BTSE)

Transcoder and Rate Adapter Unit (TRAU)

Local Maintenance Terminals (LMT)

One Base Station Controller can control several BTSE and several TRAU. Theinterface between the BSC and the BTSE is called the Abis interface, the interfacebetween BSC and TRAU is the Asub interface. The interface between the Base

Station System and the Switching Subsystem (or the TRAU and the MSCrespectively) is called the A interface.

The Base Station Controlleris responsible for the intelligent functions in the BaseStation System (BSS). The BSC assigns traffic channel connections from the SSS tothe BTSE. Furthermore, it controls the whole Base Station System.

The Base Transceiver Station Equipment comprises the radio transmission andreception equipment, including the antennas, and also the signaling processingspecific to the radio interface. The BTSE contains one or more transceivers (TRX)and serves up to 24 cells.

The Transcoding and Rate Adaptation Unit is the equipment in which speech

coding and decoding is carried out as well as rate adaptation. The two mainfunctional units of the TRAU are:

Transcoder (TC) for speech coding/compression

Rate Adapter (RA) for data rate adaptation

Local Maintenance Terminals are the (notebooks) computers, which the servicetechnicians use for work on site with the BSC, BTSE and TRAU. They are necessaryfor local fault clearance and for the commissioning of the system.


11/70



11

Transcoder

and

Rate Adapter

Unit

TRAU

Base Station

Controller

BSC

Abis Asub

Base Station System BSS

A

S

G

S

N

M

S

C

Gb

PCU

Base

Transceiver

Station

Equipment

BTSE

Fig. 5


12/70


MN1783EU11MN_0001

2002 Siemens AG

12

1.4 Structure of the OSS

The OSS, often called Operation and Maintenance System (OMS) or Operation andMaintenance Center (OMC), can be divided into two parts, the

Siemens Switch Commander (SC), and the

Siemens Radio Commander (RC).

In the OSS, monitoring of the network components of the SSS and the BSS can beperformed. The RC and SC are independent, but may be combined in the samelocation.

For the RC there are three different possibilities to connect it to the BSC:

Either via dedicated line

via A-interface connection (nailed-up connection)

via an IP based connection.


13/70



13

RC SC

OMS

Fig. 6

BTSE

RC SC

TRAU

AC

MSCVLR HLR

BSC

EIR

A-interface connectiondedica-

ted line

OMS

BSS SSS

IP based

connection

Fig. 7


14/70


MN1783EU11MN_0001

2002 Siemens AG

14

1.5 Transmission on the terrestrial interfaces

For the transmission on the terrestrial interfaces the standard PCM30 (or in someregions PCM24, e.g. in the U.S.) is used. The PCM30 standard (ITU-T G.703)describes the transmission using 32 timeslots with 64 kbit/s transmission rate each,i.e. a link with a total capacity of 2048 kbit/s. Many subscribers can therefore use thislink simultaneously. This principle is called Time Division Multiple Access (TDMA).

In PCM30, timeslot 0 is used for the Service Word (SW) and the Frame AlignmentWord (FAW), which is necessary to transmit check bits and PCM internal alarminformation. Therefore it can never be used for carrying traffic or BSS signaling.

The timeslots 1 up to 31 are available for calls (traffic) and for signaling between thecomponents of the PLMN.

Traffic channels are transmitted using 64 kbit/s (one full timeslot) on the A interfaceand with 16 kbit/s (one subslot) on the Asub and Abis interface.

The transmission rate used forsignaling channels depend on the type of thesignaling:

LPDLM and LPDLR: 16 or 64 kbit/s

LPDLS: 64 kbit/s

CCSS7: 64 kbit/s

OMAL (X25 or IP): 64 kbit/s

The PCM30 standard is a general standard for the transmission, i.e. not only cablescan be used, but also optical fibers or microwave links.


15/70



15

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

TDM frame

125 s

Service Word /

Frame Alignment Word

0 1 2 3 4 5 6 7

Traffic or signaling

Timeslots

0 1 2 3 4 5 6 7

3.90625 s

a b c d

Timeslots

Subslots

Bits

Fig. 8


16/70


MN1783EU11MN_0001

2002 Siemens AG

16

1.6 Flexible Abis Allocation Strategy (FAAS)

Flexible Abis Allocation Strategy (FAAS) is a general strategy for handling Abisresources in a flexible way. Flexible Abis allocation is necessary to support GPRSCS3-CS4, EDGE and TD-SCDMA, requiring more than 16 kbit/s Abis throughput forspecific radio channels. For packet services, concatenated PCU frames are alsonecessary.

User Data Rate (kbps)Number of 16 kbps TSCoding Scheme

59,25MCS9

54,45MCS8

44,84MCS7

27,2/29,63MCS6

22,42MCS5

17,62MCS4

13,6/14,82MCS3

11,22MCS2

8,81MCS1

21,42CS4

15,62CS3

13,42CS2

9,051CS1

Fig. 9


17/70



17

Flexible Abis Allocation Strategy

Um Abis

5 1 5 1 5 1 5 1

4 0 4 4 0 4

7 3 7 3 7 3 7 3

6 2 6 2 6 2 6 2

5 1 5 1 5 1 5 1

4 4 0 4 0 4

7 3 7 3 7 3 7 3

6 2 6 2 6 2 6 2

L

A

P

D

L

A

P

D

S

W

/F

A

W

7 6 5 4 3 2 1TRX-3-0

7 6 5 4 3 2 1 0TRX-3-1

7 6 5 4 3 2 1TRX-0-0

7 6 5 4 3 2 1 0TRX-0-1

7 6 5 4 3 2 1 0TRX-0-2

7 6 5 4 3 2 1TRX-1-0

L

A

P

D

TR

X-

3

-

1

TR

X-

3

-

0

TR

X-

2

-

1

TR

X-

2

-

0

TR

X-

1

-

0

TR

X-

0

-

2

TR

X-

0

-

1

TR

X-

0

-

0

Fixed

Allocation

7 6 5 4 3 2 1TRX-2-0

7 6 5 4 3 2 1 0TRX-2-1

Fig. 10


5 1 5 1 5 1 5 1

4 0 4 4 0 4

7 3 7 3 7 3 7 3

6 2 6 2 6 2 6 2

5 1 5 1 5 1 5 1

4 4 0 4 0 4

7 3 7 3 7 3 7 3

6 2 6 2 6 2 6 2

L

AP

D

L

AP

D

S

W

/

F

A

W

TS pool for

BTSM 0

000

TS pool

for BTSM

2

7 6 5 4 3 2 1

TRX-1-0

7 6 5 4 3 2 1

TRX-3-0

MCS7

CS4

Flexible

Allocation

L

AP

D

Fig. 11


18/70


MN1783EU11MN_0001

2002 Siemens AG

18

FAAS consists of two functional building blocks. The first block allows flexibledefinition and reconfiguration of Abis pools per BTS site. Each Abis pool deals witharbitrarily defined sets of Abis subslots on individual PCMBs. The second block relies

on the flexible allocation and release of resources taken from the Abis pool. Duringruntime, the new Abis allocation algorithm assigns sufficient Abis bandwidth to an airinterface timeslot. It also releases bandwidth in case of congestion, according toservice priorities and QoS constraints.

Dynamic Abis resource allocation is applied to both, PS and CS services. Theappropriate number of Abis resources is dynamically allocated, according to theservice applied. Since the capacity of each air interface timeslot can vary duringruntime, dynamic Abis allocation adjusts the Abis capacity to the required airinterface capacity.

WARNINGThe Abis configuration of BR5.5 (with 2 PCMB lines and only one LPDLM) will nolonger be supported. Therefore, before executing a change version procedure BR5.5(or an earlier release), switch to a configuration with at least 1 LPDLM for eachPCMB trunk.

FAAS has to be coupled with the management of up to 8 Abis PCM lines per BTSE.


19/70



19


BSC

Pool Site_1 Pool Site_2

1 x 64kbps

PCM slot

Site_1

CELL_1

CELL_2

CELL_3

C

O

R

E

C

O

R

E

Integrated CrossIntegrated Cross--ConnectConnect

or Multidropor Multidrop

Abis Pooling

on Site Basis

Site_2

CELL_4

CELL_5

CELL_6

C

O

R

E

C

O

R

E

Pool Site_2

Fig. 12

TS 20

LAPD:0

TS 21

One LAPD controls one subpool

Assosiated LAPD is LAPD:0

Abis subpool: one LAPD and

11 Abis subslots

Fig. 13


20/70


MN1783EU11MN_0001

2002 Siemens AG

20

The following HW configuration/platforms support flexible Abis allocation:

Both BSC configurations: the old BSC HW, and the enhanced BSC HWconfiguration,

BTSplus mainline with GSM-CU and E-CU, picoBTS, enhanced micro BTS, BTS1.


21/70



21

BSC with SNAP/PPXU

BTS 1 HW with old BBSIGOnly standard PCU framesOnly CS1, CS2

No EDGE support

Dynamic Abis

BTS 1 HW with BBSIG44Standard/concatenated PCU frames

CS1, ..., CS4

MCS1, ..., MCS9 on EDGE TRX

Dynamic Abis

BTS+, pico BTS, e--BTS HWStandard/concatenated PCU frames

CS1, ..., CS4

MCS1, ..., MCS9 on EDGE TRX

Dynamic Abis

Dynamic

Abis

Concatenated

or Standard PCU frames

Standard PCU frames

Bothstandard and concatenated

PCU frames are supported.

Concatenated or Standard

PCU frames

Old BBSIG NOT

supported with BR7.0

BSC with SN16/PPCU

Only Standard PCU framesare supported.

Fig. 14


22/70


MN1783EU11MN_0001

2002 Siemens AG

22

1.7 Transmission on the air interface

On the air interface Um a different transmission scheme is used. It is again based onTDMA, i.e. several subscribers can simultaneously use the resource that is called atransceiver (TRX). Every subscriber performing a call in a cell (BTS) will use onetimeslot of the TRX, which is called channel (CHAN). In a cell many TRX can exist atthe same time, using different frequencies (Radio Frequency Carrier RFC). This isalso called Frequency Division Multiple Access (FDMA).

In every cell at least one channel of one transceiver is reserved for signaling in thiscell (Broadcast Control Channel BCCH, located on CHAN-0 of TRX-0). Especially inbigger cells with many TRX, further signaling channels can be defined (e.g. SDCCH).All the remaining channels are used for speech or data transmission (TrafficChannels TCH).


23/70



23

0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7

4.616 ms

Burst

577 s

MAINBCCH

SDCCH

TCH

Fig. 15


24/70


MN1783EU11MN_0001

2002 Siemens AG

24

1.8 Signaling in the BSS

For the internal communication in the BSS and between BSS and SSS different typesof signaling are used.

LAPD (Link Access Protocol for the D-channel, derived from ISDN technology)signaling is used within the BSS. Three links have to be distinguished: LPDLM,LPDLR and LPDLS. Furthermore CCSS7 (Common Channel Signaling System No.7)and OMAL (Operation and Maintenance Access Link) are used.

An additional signaling link may exist, the CBCL (Cell Broadcast Center Link), whichis used only if Short Message Service Cell Broadcast is used. The CBCL usesresources of the OMAL link, i.e. it is carried within the same timeslot.

Signaling link Used between Function

LPDLM BSC BTSE management of the BTSE sites,

up to 11 links per BTSM

LPDLR BSC BTSE call related signaling,

one link per TRX

LPDLS BSC TRAU management of the TRAU,

one link per TRAU

CCSS7 BSC MSC call related signaling,

up to 16 links per BSS (with BSC120)

OMAL BSC RC supervision and control of BSS,

up to 2 links per BSS

CBCL BSC CBC information for SMS Cell Broadcast

LPDLM for a BTSE and LPDLR for all the TRX housed in this BTSE are transmittedin the same timeslot.


25/70



25

BSCBTSE

BTS:

TRX:0

TRX:1

TRX:2

TRAU MSC

OMC

CBC

LPDLM

LPDLR

LPDLS

CCSS7

OMAL CBCL

Fig. 16


26/70


MN1783EU11MN_0001

2002 Siemens AG

26


27/70



27

2 Radio Commander (RC)

Fig. 17


28/70


MN1783EU11MN_0001

2002 Siemens AG

28

2.1 General RC Setup

The RC functionality is split into the functions of the Operation and Maintenance Processor (OMP), and

the functions of the Operation and Maintenance Terminals (OMT), and

optionally servers for the O&M Toolset.

The OMP is the main hardware, where all the tasks for the supervision and control ofa BSS are processed. The OMP works as a server and is connected to the OMT viaa Local Area Network (LAN), implemented as an Ethernet. On the other hand, theOMP is responsible for the connections to the BSC of the BSS to be controlled.

The OMT are the Workstations with both, a Graphical User Interface and aCommand Line Interface, which are used by the OMC staff to enter their commandsand to get a graphical representation of the condition of the BSS. The OMTs work asclients. Although a bigger number of OMT can be physically installed in an RC,maximum 20 user sessions can be handled by the OMP with reasonable responsetime.

For the OMT different hardware types can be distinguished:

the Workstation (WS),

the X-Terminal (XT), and

a dedicated X-Terminal-Server (OMX).

Depending on the hardware used, the Workstations can handle one or twosessions: one local session and one additional session of an X-Terminal.

The X-Terminals do not require such a powerful hardware as the Workstations.However, they cannot run a session alone, but they need a Workstation or adedicated X-Terminal-Server to process the user tasks. So the functions of the X-Terminal are restricted to handle the user input (keyboard and mouse) and to displaythe output (monitor).

Unlike the Workstations, which can handle just one additional session, the X-Terminal-Servercan handle many sessions for X-Terminals. One of these sessionscan also run locally, i.e. one session runs at the OMX and all the other sessions runat the XT.


29/70



29

OMC OMP

LAN

OMX Server

X-T m+1 X-T k

......

..........

WS 0

X-T 0

WS n

X-T m

OMC OMT

OMC Toolset Server

Fig. 18


30/70


MN1783EU11MN_0001

2002 Siemens AG

30

2.2 RC Hardware

An Operation and Maintenance System (RC) comprises the following components: Nearly unlimited number of Operation and Maintenance Terminals (OMT0-OMTn)

including both workstations (WS) and X-Terminals (X-T), along with the relevantmass storage and input/output devices, CD Reader Unit and Tape Reader Unit

Color Printer or Black/White printer

Local Area Network (Fast Ethernet)

Operation and Maintenance Processor with the relevant mass memory and TapeUnit

External Disk Storage Array (Hard Disk Multipack)

External Tape Autoloader for ORACLE backup and restore operations

Operation and Maintenance Console

optionally a Terminal Server

Operation and Maintenance Printer

Communication Controller:

PT E1 or PT T1 board for A interface connections, or

HSI/PCI board for dedicated line configurations


31/70



31

External Hard Disk

Tape device for Backup & RestoreOMP

Spoolprinter

Colourprinter

WS 2

X-T 0

WS 0

LAN

BSCBSC

via A interfacededicated

line

Console

OMT Server

X-T 1

WS 1

BSC

IP based

Fig. 19


32/70


MN1783EU11MN_0001

2002 Siemens AG

32

2.2.1 OMP Hardware

The minimum configuration for the Radio Commander is just one OMP, equipped

with 2 CPU/2 GB RAM (plus storage devices for installation and backup purposes),as the OMP can also double as an OMT.

With a growing number of Network Elements being connected to the system, theprocessing power can be easily extended by hardware upgrading of the OMP itself(RAM, hard disk capacity, CPUs)

To fulfill different customer requirements, five different OMP hardware configurations.Each configuration can be based on more than one HW platform. The main reason isSUN end-of-life policy (enterprise servers are already END OF LIFE, Fire serverbelong to the new generation).

Basic OMP Configuration

Extended Simple OMP Configuration

Extended Redundant OMP Configuration

Full Redundant OMP Configuration

Simultaneous Support OMP Configuration

OMP Configuration SUN Server forexisting sites

SUN Server fornew sites

Basic OMP / Basic Extended OMP Sun E420R Sun FireV440/V480/

F4800/E4900

Extended simple OMP Sun E4x00

Extended redundant OMP Sun E4x00

Full redundant OMP -

Simultaneous support OMP -

Sun FireF4800/E4900(flexible scalability)


33/70



33

Enterprise E4500 Server

Enterprise 420R

Sun Fire F4800

Sun Fire V480

Sun Fire E4900

Fig. 20 Servers used as OMP


34/70


MN1783EU11MN_0001

2002 Siemens AG

34


35/70



35

2.2.1.1 Basic configuration rules for selecting an OMP configuration

The choice among the different OMP configurations can be carried-out bearing in

mind the following aspects:

Size of the network that must be managed; the size of the network that the RCmust manage has a fundamental impact on the following hardware resources:

a) total number of CPU needed to satisfy the performance requirements, suchas, for example, alignment time

b) total amount of RAM memory needed by the application processes toproperly run

c) the architecture and the external disk size;

As the unit of measure for the size of the network, the total number of HMO/FMOobjects has been chosen as the most appropriate; for GERAN NEs, the number ofTRX objects has been chosen has a parameter to evaluate the network mean size,for UTRAN networks the number of managed cells and NodeBs will be used.

Type of physical connections to the GERAN NEs; related to the type ofphysical connection used, i.e., direct serial connection, WAN serial connection,PCM connection via MSC or TCP/IP connection, different cards must be used,requiring different types of free slots in the server.

Availability of additional devices needed for other features; the availability ofdevices such as printers, external alarm devices, selector unit, data-backup tapethat can be connected to the OMP also require different types of free slots in theserver.

Redundancy; the redundancy features, i.e., the WAN connection redundancy andthe link redundancy, expected to double the number of used physical connectionsand the number of needed boards in the server (E4x00 family servers).

Simultaneous support of GERAN/UTRAN; the simultaneous support feature alsorequires different HW configurations: CPU, RAM, connection equipment to 2G and3G network elements.


36/70


MN1783EU11MN_0001

2002 Siemens AG

36

Basic OMP

The "Basic OMP" can be made up by the E420R/ Sun Fire V440/V480 Server or by

the Sun Fire F4800/E4900. The E420R Server is less scalable than the other Serversused. The Sun Fire F4800/E4900 as Basic OMP uses a smaller configuration thanbeing used as Extended simple OMP.

The Basic OMP can be based on the following servers (number CPU and size ofRAM depends on NE to be managed):

Sun Enterprise 420R (two or four processors),

Sun Fire F4800 (up to eight processors),

Sun Fire E4900 (up to twelve processors),

Sun Fire V480 (two processors),

Sun Fire V440 (two processors).

Extended simple OMP

The configuration "Extended simple OMP" used to manage more NE can be basedon the Sun Enterprise Server family E4x00 (E4500 or E4000) orSun FireF4800/E4900.

Extended redundant OMP

The main characteristic of the Extended redundant OMP is, that it enhances thereliability and availability of the RC system, adding the following:

redundancy of the Sbus/PCI I/O boards

redundancy of the RC LAN connection

redundancy of internal and external disks (mirroring is mandatory).

The Extended Redundant OMP can be based either on the Sun Enterprise 4x00server or the Sun Fire F4800/E4900 server.

Full Redundant OMPThis configuration is based on Sun Fire F4800/E4900 server and is an improvementof Extended Redundant configuration, which provides internal redundancy feature. Itprovides the same features as Extended Redundant OMP with, in addition, the faulttolerance over the CPU/Memory boards.

Although providing more CPUs and more RAM than other configurations it isdesigned to support a failure of a CPU/Memory board without decrease of managednetwork capacity, therefore the supported network capacity remains the same asExtended Configurations based on the same platform.

TIP

Disk mirroring is optional for Basic and Extended simple OMP and mandatoryfor the redundant OMP configurations.


37/70



37

Sun Server Enterprise 4x00

Redundancy of CPU and

Memory (like extended simple

OMP

Redundancy of the LAN connection

Redundancy of

Sbus and I/O boards

Redundancy of PCI boards

Redundancy of internal HD

2 x external Hard Disks

(mirroring)

2 x connection Equipment like

HSI or SpriteE1

Fig. 21 Extended Redundant OMP


38/70


MN1783EU11MN_0001

2002 Siemens AG

38

Simultaneous Support OMP

This configuration is based on Sun Fire F4800/E4900 servers and is designed to

manage both UMTS and GSM network from the same HW installation.Two different configurations are possible.

split the machine into 2 independent domains (each domain managing onenetwork technology)

It uses SUN domaining concept to split the machine in two independent parts(domains) having their own operating system image and SW load installation, andmanaging their own I/O Tray for connecting to network and external devices.

This type of Simultaneous Support OMP Configuration does not supportinternal redundancy feature.

Minimum requirements per domain are:

1 x CPU Board

1 x PCI I/O Tray (SF 4800)

2 x PCI I/O Tray (E4900)

1 x D240 Media Tray

1 x External Disk Array + Host Bus Adapter

common platform for GSM and UTRAN in one domain (NEW WITHBR8.0/UMR4.0)

In BR8.0/UMR4.0 the simultaneous support of GSM and UMTS systems are alsosupported in a common platform (Sun Fire F4800/E4900 configurations equal or

greater than Extended Simple OMP) but configured in one domain only. In thatcase the max capacity of the common platform is shared between the two systems(see table below).

Network type Number ofBSCs

Number ofTRXs

Number ofRNCs

Number ofNBs

100% GSM 0% UMTS 84 21000 0 0

50% GSM 50% UMTS 36 5000 15 1500 (4500cells)

0% GSM 100% UMTS 0 0 20 5000 (15000cells)


39/70



39

2.2.1.2 External disks

For storage of fault and alarm data, performance measurement results etc. external

hard disks are used. The external disk units can be installed single or mirrored. If diskmirroring is used (to avoid system outage in case of disk errors and maintenance),both disk copies must have the same capacity. The online system recoveryfunctionality ensures that both hard drives have the same status of data at all times.

The external disk devices are connected to the OMP via internal SCSI cards on theservers I/O boards. The disks are SCSI devices.

Type of disk array Disk Configuration Total Size Notes

MultiPack 6 x 9.1 GB 54 GB Reusing OMC 1 disks

MultiPack 6 x 18.2 GB 109.2 GB Reusing OMC 1 disksD 1000 4 x 36.4 GB 145.6 GB From RC 6.0 systems

D 1000 6 x 36.4 GB 218.4 GB From RC 6.0 systems

D 1000 12 x 36,4 GB 436.8 GB From RC 6.0 systems

StorEgde 3310 6 x 73.4 GB 440.4 GB New projects

StorEgde 3310 12 x 73.4 GB 880.8 GB New projects


40/70


MN1783EU11MN_0001

2002 Siemens AG

40

2.2.2 Interface types for OMP-BSS connection

For the connection of the RC to the BSC of all the BSS to be supervised, the so

called OMAL, the network operator has to choose which type of connection he willuse:

A interface connection,

Dedicated line connection, or

IP based connection.

In case ofA interface connection all BSC will use one timeslot on the A interface andAsub interface for this bi-directional communication. The signaling link is based on aX.25 connection called X25A (X.25 connection via A interface). Since one PCM30 is

connected between the MSC and the RC, maximum 31 BSS can be connected (24 incase of PCM24), each with a speed of 64 kbit/s.

The hardware required in the OMP is the PT E1 (PCM30) or the PT T1 (PCM24).

In the second case, the Dedicated line connection, the BSC are connected eithervia a packet data network or directly. Therefore a different interface card has to beinstalled in the OMP, the HSI/PCI interface card.

The HSI/PCI houses 4 connection ports with connectors for up to 30 BSC on eachport, allowing a total of 48 BSC to be connected in total.

A mixed configuration of A interface and dedicated line configuration can be usedwith a total of 4 boards in the OMP server.

Link redundancy

For the OMAL link a redundant configuration can be used, i.e. two links can beconfigured that can use either the same interface type or a mixed configuration. Toachieve the highest reliability, also internal OMP redundancy should be used.


41/70



41

BSC TRAU

MSC

OMC

PT card

NUC

Nailed Up

Connection

PCM30 Link 64k TSPCM30 Link 64k TS

TRAUBSC

Fig. 22

BSC

IX

L

T

OMC

HSI/PCI

PSDN

X.25 network

Modem Modem

dedicated point to point connection

connection via a packet switched data network

X.21/ V.11 Interface

Fig. 23


42/70


43/70



43

Reasons for introduction:

Current X.25 links allow max. 64 kbit/s IP network is faster

RC for UTRAN supports IP over Ethernet connection to RNC

IP network widespread available

Aspects of introduction:

No TCP/IP over PCM timeslot, i.e. dedicated line

Different LAN cards in RC for RC LAN and BSC LAN required Hardware requirement in BSC: MPCCv8

IP link is also used for CBC, no mixed configuration

Link supervision by ping command

Fig. 24

IXLT-0

IXLT-1

Hub orSwitch orRouter

RC

CBC

LMTLAN

X

IP-0X.25 Dedicated

X.25 Dedicated

X.25 PCM Timeslot

X.25 PCM Timeslot

BSC

LMT V.11 64Kbit/sec

StandbyMPCC-1

ActiveMPCC-0

Test only

IXLT cards are still required for LMT, power on/off, ...

Fig. 25


44/70


MN1783EU11MN_0001

2002 Siemens AG

44

2.2.3 OMT hardware configurations

The OMT graphical station, required to display the Graphical User Interface (GUI) of

the RC, has the following configurations:

OMT minimum

OMT normal

OMT X-Server

OMT X-Terminal

Each configuration can be based on platforms: the Sun Ultra family and the SunBlade family, which represent the new generation.

TIPThe OMT Server for new projects (BR8.0/UMR4.0) is based on V480/V440 Server.

Basic Configuration Rules for choosing the OMT and OMT Server HWConfiguration

The choice among the different OMT configurations can be carried-out bearing inmind the following aspects:

availability of serial and parallel connectors for I/O devices such as printers andExternal Alarm device,

availability of I/O slots for the additional graphic card,

number of RC GUI sessions that can run on a single OMT.


45/70



45

Ultra 5Ultra 10 / Sun Blade 150

Ultra 60

Sun Blade 1000/2000

Sun Fire V440/V480

9 OMT (2 sessions) 9 Minimum OMT (1 session)

9 OMT Server 9 X Terminal

Sun Blade 100

Ultra 1 140E/170E/200E

Ultra 5 Sun Blade 100/150NEW !

Sun Fire V440

Fig. 26


46/70


MN1783EU11MN_0001

2002 Siemens AG

46

Simultaneous sessions at OMT / X-Terminal

There is no limit to the number of terminals that can be configured to the OMP. As for

multi-session capability, several active graphic user interface (GUI) sessions plus anumber of alphanumeric sessions can run simultaneously. The sessions can be localor remote. RC Scalability leads to different types of OMT and X-Terminals withdifferent capacity: Like in OBR 5.5 one normal OMT can provide 2 Sessions, thenumber of sessions supported by the OMT-Server depends on the used HW platformand on used HW resources

TIPWith introduction of new OMT-Server Sun Fire V440/V480 up to 10 sessions can besupported.

The OMT systems, according to their hardware characteristics, mainly in terms ofnumber and speed of CPUs, and total amount of RAM memory, can be used forrunning a different number of GUI sessions.

The typical GUI session scenario to which these data apply, in terms of open panelsis:

1 Active alarm Monitor with view on one BSS,

1 Command History,

1 OMC-Region Panel, 1 BSS Summary Panel,

1 BSCE Panel,

1 TRAUE Panel,

1 BTSE Site Panel,

1 BTS Panel.

Additionally, in two of the active GUI sessions one global Alarm Monitor list (showing

all BSS and RNS) is opened with 5000 active alarms.


47/70



47

OMT configuration # of GUI sessions

OMT minimum 512 MB 1OMT Normal 1GB 2

OMT server 4GB (for Blade 1000/2000server based configuration)

4

OMT server 4GB (for V480/V440 serverbased configuration)

10

RCConfiguration GSM only Number of parallel GUIsessions at RC Number of parallelalphanumericsessions at RC(CLI)

Basic 10 BSCs and2500 TRXs

10 12

Basic Extended 36 BSCs and5000 TRXs

15 16

Extended 48 BSCs and12000 TRX

20 24

Extended (add.resources)

84 BSCs and21000 TRXs

30 32

TIPThe number of GUI and CLI sessions shall be valid in parallel.


48/70


MN1783EU11MN_0001

2002 Siemens AG

48

2.2.4 External Tape Drives

In addition to the internal tape device an external tape device is required to support

the data backup feature. In order for this feature to work, a "backup server" systemmust be designated, which can be a RC component, an OMP, or also an externalone.

The following tape devices can be connected to the "backup server" system:

StorEdge FlexiPack AutoLoader DDS-3 (jukebox), 72 GB, transfer rate1MByte/sec; the device must be connected to a free Fast/Wide SCSI-2 port

Deskside L280 Autoloader, 280 GB, transfer rate 5 MByte/sec; the device mustbe connected to the RC by means of

an SBus Fast/Wide differential intelligent SCSI-2 host adapter, on an E4X00

system, ora PCI differential Ultra SCSI host adapter, on a E420R system

StorEdge L9 Autoloader, 360GB, transfer rate 6MB/sec; the device must beconnected to the RC by means of:

an SBus Fast/Wide differential intelligent SCSI-2 host adapter, on an E4X00system, or

a PCI Ultra differential Ultra SCSI host adapter, on a E420R system.


49/70



49

StorEdge L9 AutoloaderStorEdge FlexiPack

AutoLoader DDS-3

Fig. 27


50/70


MN1783EU11MN_0001

2002 Siemens AG

50

2.3 RC tasks

The tasks of the RC can be classified into the following categories: Security Management

Configuration Management

Performance Measurement Management

Software Management

Fault and Test Management

2.3.1 Security Management

The Security Management is related to all the functions to prohibit an unauthorizedaccess to the network. Examples for the Security Management are

creation of log files containing the commands entered from all the terminals by allthe operators

protection of the RC access by access profiles and passwords

distinction between RC application access and UNIX access

supervision of local access on sites (LMT access supervision)


51/70



51

!

Fig. 28


52/70


MN1783EU11MN_0001

2002 Siemens AG

52

2.3.2 Configuration Management

The configuration management is related to all changes in the structure of the PLMN

and to changes of all parameters relevant for the communication in the radio cells.Some examples for configuration tasks are

adding new sites to the PLMN (new BTSE)

adding or removing TRX to/from a site

changing frequencies in the radio cells

Several ways of working in the configuration management are implemented:

online

using script files, and using the DBAEM tool.


53/70



53

Fig. 29


54/70


MN1783EU11MN_0001

2002 Siemens AG

54

2.3.3 Performance Measurement Management

Performance measurements are essential for the surveillance of a mobile network.

The corresponding information enables the operator to identify failures or quality ofservice problem areas within the network, which are not detected by the faultmanagement, and help to optimize and extend the existing network.

The operator establishes measurements with individual parameters. He canschedule, delete, modify, deactivate and display parameters of existingmeasurements and administer them interactively.

All the measurements coming from a NE and requested by the operator are stored onthe omp and can be exported to post-processing tools.


55/70



55

Fig. 30


56/70


MN1783EU11MN_0001

2002 Siemens AG

56

2.3.4 Software Management

From the RC the complete software of the BSS is administered. Therefore the RC

operator is able to:

import BSS Software images and data coming from software factory

download the BSS software images and data files

download and activate patches

activate BSS software

upload data files from the BSS

migrate BSS data base

export data (e.g. for backup procedure)


57/70



57

Fig. 31


58/70


MN1783EU11MN_0001

2002 Siemens AG

58

2.3.5 Fault and Test Management

Fault Management includes all the measures required to detect and repair faults in

the mobile communications network. Hardware faults are usually isolated to aparticular module. Operation is normally switched to another module that takes overthe function of the defective unit. The defective unit can be replaced later.

The operator receives information about the probable cause. In addition, he hasaccess to the on-line maintenance documentation, which provides further informationon how to deal with the fault.

Fault handling can be divided into the following main functions:

Fault detection

Fault recovery

Alarm logging

Alarm reporting

If a fault is detected, the state and status of the objects concerned changes. Thesechanges are displayed on the graphical workstation by graphical symbols, colors andanimation.

Each single failure (failure source) generates a single alarm report. Therefore, allalarms are transferred from the BTSE and TRAU via the BSC to the OMC and theLMT.

Alarm reports always result in one of five error types specified by GSM: Equipment alarm

Communication alarm

Quality of service alarm

Environment alarm

Processing alarm

Moreover, each alarm is qualified by a probable cause giving more detailed

information about the nature of the fault and an alarm severity.


59/70



59

Fig. 32


60/70


MN1783EU11MN_0001

2002 Siemens AG

60

Test Management is closely related to the fault management. The operator is able toactivate remote diagnostic procedures, so-called tests in order to get furtherinformation for maintenance.

Test results coming from BSS are logged in a test result database table, which canbe retrieved by operators request for further analysis.

Handling of RC faults

The RC supervises the following connections in order to detect possible link failures:

RC to SBS via layer 2 supervision (LAPB), and

OMP to OMT via keep-alive messages (TCP/IP).

BTSE, BSC and TRAU autonomously perform fault recovery. The recovery processcan be seen as a sequence of defense actions, performed to minimize the loss ofservice caused by a fault. Also in the RC the service is supervised in order to detectinternal faults.


61/70



61

?

TestMPCC

Fig. 33


62/70


MN1783EU11MN_0001

2002 Siemens AG

62


63/70



63

3 Exercise


64/70


MN1783EU11MN_0001

2002 Siemens AG

64


65/70



65

Exercise

Title: RC function and setup

Query

Which signaling links do exist in the BSS? What's their purpose?

Name the functions of the OMP and of the OMT.

Which types of OMT do exist and how do they differ?

Can the OMT be connected to the BSC directly?

List the OMAL connection types and the hardware required.

Can A interface connection and Dedicated Line connection be used simultaneously

with one OMP?

Name the tasks, which can be performed by the RC.


66/70


MN1783EU11MN_0001

2002 Siemens AG

66


67/70



67

4 Solution


68/70


MN1783EU11MN_0001

2002 Siemens AG

68


69/70



69

Solution

Title: RC function and setup

Query

Which signaling links do exist in the BSS? What's their purpose?

See table on page 24.

Name the functions of the OMP and of the OMT.

See page 28.

Which types of OMT do exist and how do they differ?

See page 28.

Can the BSC be connected to the OMT directly?

No. Always the interface cards of the OMP are required.

List the OMAL connection types and the hardware required.See page 40.

Can A interface connection and Dedicated Line connection be used simultaneously?

Yes, a PT card and an HSI/PCI card have to be mounted at the same time. However,not more than 48 BSS can be controlled.

Name the tasks, which can be performed by the RC.

See page 50


70/70


01 Mn1783eu11mn 0001 Introduction

Documents