Ibtissam CHABIBA

Page 1

23/12/2003

Page 1 sur 8

Ibtissam CHABIBA

Page 2

23/12/2003

Table Of Contents
1 INTRODUCTION................................................................................................................................................3
2 SYSTEM RELATED INFORMATION ...........................................................................................................3
2.1 MO DESCRIPTION.................................................................................................................................................3
2.2 DESCRIPTION OF THE MO STATES........................................................................................................................3
3 SYSTEM RELATED INFORMATION ...........................................................................................................4
3.1 MANAGED OBJECT HIERARCHY.............................................................................................................................4
3.2 BLOCKING OF MO'S ...........................................................................................................................................4
3.3 DEBLOCKING OF MO'S ........................................................................................................................................5
4 BTS MAINTENANCE.........................................................................................................................................6
4.1 INTERNAL ALARM................................................................................................................................................6
4.2 EXTERNAL ALARM...............................................................................................................................................6
4.3 STATUS OF MOS.................................................................................................................................................6
4.4 BTS ALARM HANDLING........................................................................................................................................6
5 HISTORICAL STORAGE OF QUALITY DATA OF A DIGITAL PATH .................................................7
6 ANNEXE...............................................................................................................................................................8
Figures
FIGURE 1: MO-STATE OVERVIEW................................................................................................................3
FIGURE 2: MANAGED OBJECT (MO) HIERARCHY FOR RBS 2000 SERIES.........................................4

Page 2 sur 8

Ibtissam CHABIBA

Page 3

23/12/2003

Introduction

The aim of this manual is to give the NMC department an overview of the most used
commands , related to the BSS subsystem , while dealing with the maintenance procedures .

System Related Information

2.1 Mo description
MO
TG
CF
CON
IS
TF
DP
TRXC
RX
TX
TS

MO class
Transceiver Group
Central Function
LAPD Concentrator
Interworking Switch
Timing Function
Digital Path
Transceiver Controller
Receiver
Transmitter
Time Slot

MO type
RXOTG
RXOCF
RXOCON
RXOIS
RXOTF
RXODP
RXOTRX
RXORX
RXOTX
RXOTS

2.2 Description of the MO States

The figure below shows an overview of the different states the BSC/TAS1-MOs can have in
the procedure of blocking/deblocking and bring them into and out of service.

Figure 1: MO-State Overview

TAS Transceiver Administration Subsystem

Page 3 sur 8

Ibtissam CHABIBA

Page 4

23/12/2003

Automatically (auto in Figure 1) means that the operation is automatically performed by the
BSC.

System Related Information

3.1 Managed Object Hierarchy

The Managed Objects CF, TF, DP, CON and IS corresponds to the hardware unit DXU in the
BTS.
The Managed Objects TRX, TX, RX and TS corresponds to the hardware unit TRU in the
BTS.
The Managed Object TG has no corresponding hardware in the BTS.

Figure 2: Managed Object (MO) hierarchy for RBS 2000 series

3.2 Blocking of MO's

Defined MOs are brought out of service with command RXESE.
Blocking of a TG shall be performed in the order stated below.
Please note that XX is the TG number and the example is for a cell which has two TRxs ( 0 & 1 ).
RXBLI:MO=RXOTG-XX;
RXESE:MO=RXOTG-XX;
RXBLI:MO=RXOCF-XX;
RXESE:MO=RXOCF-XX;
RXBLI:MO=RXOCON-XX;
RXESE:MO=RXOCON-XX;

Page 4 sur 8

Ibtissam CHABIBA

Page 5

23/12/2003

RXBLI:MO=RXOIS-XX;
RXESE:MO=RXOIS-XX;
RXBLI:MO=RXOTF-XX;
RXESE:MO=RXOTF-XX;

RXBLI:MO=RXODP-XX-0; ! The same command for RXODP-XX-1 if exist !

RXESE:MO=RXODP-XX-0; ! The same command for RXODP-XX-1 if exist !
RXBLI:MO=RXOTRX-XX-0&1;
RXESE:MO=RXOTRX-XX-0&1;
RXBLI:MO=RXOTX-XX-0&1;
RXESE:MO=RXOTX-XX-0&1;
RXBLI:MO=RXORX-XX-0&1;
RXESE:MO=RXORX-XX-0&1;
RXBLI:MO=RXOTS-XX-0-0&-7;
RXESE:MO=RXOTS-XX-0-0&-7;
RXBLI:MO=RXOTS-XX-1-0&-7;
RXESE:MO=RXOTS-XX-1-0&-7;

3.3 Deblocking of MO's

Defined MOs are brought into service with command RXESI.
Deblocking of a TG shall be performed in the order stated below.
Please note that XX is the TG number and the example is for a cell which has two TRxs ( 0 & 1 ).
RXESI:MO=RXOTG-XX;
RXBLE:MO=RXOTG-XX;
RXESI:MO=RXOCF-XX;
RXBLE:MO=RXOCF-XX;
RXESI:MO=RXOCON-XX;
RXBLE:MO=RXOCON-XX;
RXESI:MO=RXOIS-XX;
RXBLE:MO=RXOIS-XX;
RXESI:MO=RXOTF-XX;
RXBLE:MO=RXOTF-XX;

RXESI:MO=RXODP-XX-0; ! The same command for RXODP-XX-1 if exist !

RXBLE:MO=RXODP-XX-0; ! The same command for RXODP-XX-1 if exist !
RXESI:MO=RXOTRX-XX-0&1;
RXBLE:MO=RXOTRX-XX-0&1;
RXESI:MO=RXOTX-XX-0&1;
RXBLE:MO=RXOTX-XX-0&1;
RXESI:MO=RXORX-XX-0&1;
RXBLE:MO=RXORX-XX-0&1;

Page 5 sur 8

Ibtissam CHABIBA

Page 6

23/12/2003

RXESI:MO=RXOTS-XX-0-0&-7;
RXBLE:MO=RXOTS-XX-0-0&-7;
RXESI:MO=RXOTS-XX-1-0&-7;
RXBLE:MO=RXOTS-XX-1-0&-7;

BTS Maintenance

Faults occurring in the BTS which permanently affect the normal operation of the equipment,
will be detected by the software and are reported to the alarm handling block in the BSC.
We can distinguish between internal and external alarms.

4.1 Internal Alarm

To print Internal Alarm, execute the command :
RXASP : MO=RXOTG-XX;

The code of the fault of each MO (those which have faults ) are reported in the printout above.
More details about the alarms code can be founded in the Annex.

4.2 External Alarm

To print External Alarm, execute the command :
ALLIP;

To specify only alarms related to BTS execute the command :

ALLIP : PRCA=53;

4.3 Status of MOs

To check status of MOs execute the command :
RXMSP: MO= mo;
To print MO fault status of MOs execute the command :
RXMFP: MO= mo;

4.4 BTS alarm handling

Page 6 sur 8

Ibtissam CHABIBA

Page 7

23/12/2003

Whenever a BTS alarm is issued, we should check if the fault is permanent or not by
performing a test on the faulty equipment. The OPI Radio X-ceiver Administation Manged
Object Fault is to be used as the first step in locating the cause of a fault.
1. Print MOs fault information :
RXMFP: MO= mo;
2. Manually block the faulty equipment :
RXBLI: MO= mo; ! You can use parameter force to force the blockage !
3. Test the faulty MO.

Historical Storage of Quality Data of A Digital Path

If there is are any alarms issued regarding signalling and transmission Network to BTS, or
there is a doubt of the good performance of the concerned digital, an Historical Storage of
Quality Data can be initiated per DIP (Let's take RBLT-YY).
Please follow the procedure below to activate the storage of quality data per DIP.
1. To see the DIP status :
DTSTP:DIP=RBLT-XX;
The status should be WORKING, if there is a problem in the link, then the status will be
different, for example Automatically Blocked (ABL).
2. To see the quality of the DIP :
DTQDP: DIP=RBLT-XX;
3. To initiate a storage of the historical quality data for the dip XX , execute the command in
periods of 15 minutes!
DTQHI: DIP=RBLT-XX;
To initiate a storage of the historical quality data for the dip XX , in periods of 15 minutes!
DTQDP: DIP=RBLT-XX;
! Print the historical data that had been stored!
Please notice that the values T1 and T2 (inteval time can change ), but if the indicators (ES ,
ESS , SES, UAS, UASB, UASR,SFV, SFTI) are different than the value zero that mean the
the link is bad in term of quality.

Page 7 sur 8

Ibtissam CHABIBA

Page 8

23/12/2003

Annexe

Fault Code List.

Lists the Mo Fault Map on the Abis interface.

Page 8 sur 8