BTS Maintenance

Chapter 8

This chapter is designed to provide the student with the

knowledge of how to perform BTS maintenance.

2%-(&7,9(6
Upon completion of this chapter the student will be able to:

• Interpret the error log

• Locate faulty units within the BTS
• Describe how BTS software is downloaded
• Perform manually initiated tests of RILT devices
• Perform manually initiated tests of EMRS
• Perform the proper steps to troubleshoot faults in the EMG
and control signaling link
GSM BSC Operation

t io
e n na
lly
t
In

Bl n
a
k

EN/LZT 123 3801 R2A

 8 BTS Maintenance

8 BTS Maintenance
Table of Contents

Topic Page

BTS MAINTENANCE.........................................................................203
GENERAL .................................................................................................................. 203
ALARM HANDLING AND DESCRIPTIONS............................................................... 203
FAULT REPORT HANDLING .................................................................................... 209
BRINGING MOs INTO OPERATION......................................................................... 213
FUNCTION CHANGE AND PROGRAM LOAD OF MO ............................................ 214

TRI MAINTENANCE ..........................................................................217

GENERAL .................................................................................................................. 217
MAINTENANCE OF RADIO INTERFACE LINE TERMINAL..................................... 218
MAINTENANCE OF EXTENSION MODULE RADIO SELECTOR............................ 219
EMG FAULT............................................................................................................... 220
EMG CONTROL DOWN ............................................................................................ 221
TRI STATUS INDICATOR ......................................................................................... 223

EN/LZT 123 3801 R2A –i–

GSM BSC Operation

t io
e n na
lly
t
In

Bl n
a
k

– ii – EN/LZT 123 3801 R2A

 8 BTS Maintenance

BTS MAINTENANCE

GENERAL
If the BTS breaks down, behaves abnormally, or becomes
impossible to communicate with, the BSC/OSS operator will be
alerted by an alarm.

ALARM HANDLING AND DESCRIPTIONS

Any faults that may occur at the BTS and permanently effect the
normal operation of the equipment, will be detected by BTS
software and reported to the alarm handling block in the BSC.
The event will be stored in two different event registers, the
faulty unit list and the error log, and automatically printed out at
the alarm printer, once it is detected.

***ALARM 022 AS/SW-DEV

“ R420-120-16TRU&
” A950512 1020
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO EMG RSITE ALARM SITUATION
RXOTX-0-0 E2AA PERMANENT FAULT
END

Figure 8-1 Example of an alarm printout

The faulty unit list contains information about all the equipment
which has been taken out of service due to active alarms while
the error log contains historical information about active and
past alarm events. The stored information can be retrieved by the
commands 5;(/3 and 5;0)3.

EN/LZT 123 3801 R2A – 203 –

GSM BSC Operation

<RXELP:MO=RXOTX-0-0;
RADIO X-CEIVER ADMINISTRATION ERROR LOG DATA
FAULT INFORMATION LOG
MO BTSSWVER DATE TIME REPLMAP BTS
RXOTX-0-0 ERA-G01-R02-V00 95-05-12 09-25-31 000000030009 RES
1AMAP 1BMAP 2AMAP EXT1BMAP EXT2BMAP
000000000080 000000000000 0000000000000 0000 0000
MO BTSSWVER DATE TIME REPLMAP BTS
RXOTX-0-0 ERA-G02-R02-V00 95-05-12 09-20-12 000000030009 RES
1AMAP 1BMAP 2AMAP EXT1BMAP EXT2BMAP
000000000080 000000000000 0000000000000 0000 0000
END

Figure 8-2 Example of an error log printout

<RXMFP:MOTY=RXOTX;
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT INFORMATION
MO BTSSWVER BTSHWREV
RXOTG-0 ERA-G01-R02-V00
STATE BLSTATE INTERCNT CONCNT CONERRCNT
OPER 00002
END

Figure 8-3 Example of a faulty log printout

Whenever a BTS alarm is issued, the BSC operator determines

if the fault is permanent by performing a test on the faulty
equipment. The OPI 5DGLR;FHLYHU$GPLQLVWUDWLRQ0DQDJHG
2EMHFW)DXOW is to be used as the first step in locating the cause
of a fault.

– 204 – EN/LZT 123 3801 R2A

 8 BTS Maintenance

The following is an example of a class 1A fault.

1. Compare fault indication with the recorded information in

the error log. If a specific fault has occurred several times
before in the same BTS, it could possibly be a hardware
fault. If the fault occurs throughout the system and no
particular HW fault is found, then a trouble report should be
issued.
5;(/302 PR

2. Print MO fault information.

5;0)302 PR

3. Manually block the faulty equipment.

5;%/,02 PR

4. Test the faulty MO.

5;7(,02 PR

If the test indicates a fault in the MO, the MO must be repaired

according to the fault code list in the O&M manual for the BTS.
The test result must be used as an input to the fault analysis.

5. If the test does not indicate any faults, the MO can be

deblocked.
5;%/(02 PR

The example in Figure 8-2 prints the error log for all
transceivers of MO type RXOTX and for all MOs that belong to
those transceivers. If the alarm is serious, it is reported as a class
1 alarm and immediate action is taken to isolate the faulty unit.
The BSC initiates a test to verify the fault and locate the
5HJLRQDO8QLWV (RUs). If the alarm is not serious, it is reported
as a class 2 alarm. When the alarm is deactivated, it is noted on
an alarm stop printout. The different fault classes are:

&ODVV$)DXOW Faults reported in this class are faults that

affect MO functionality.

&ODVV%)DXOW Faults reported in this class are faults that affect

MO functionality.

&ODVV$)DXOW Faults reported in this class are faults that do

not affect MO functionality.

EN/LZT 123 3801 R2A – 205 –

GSM BSC Operation

%76([WHUQDO&ODVV%)DXOW Faults reported in this class are

faults that do affect MO functionality. The conditions are
external to the TG .

%76([WHUQDO&ODVV%)DXOW Faults reported in this class are

faults that do not affect MO functionality. The conditions are
external to the TG.

Fault Description
The functionality dedicated to detect faults in a MO is called
VXSHUYLVLRQ. Each MO is responsible for its own supervision.
Fault reports may be preceded by a fault filtering function of the
detected disturbance. The filtering can, for example, be an
averaging function or a disturbance counter. The output from the
fault filter has a normal range where a specific fault type is not
activated. When this limit is passed, the fault becomes active.
This means a fault report is sent to the BSC. There is a fault map
for each class of BTS internal faults, each map containing 48
bits. This gives the ability to detect up to 48 different faults of
each class within any object. If the disturbances that caused the
fault report disappear or become less frequent, the output from
the fault filter may pass into the normal range again. For some
faults, where a fault cease condition is defined, information
about the fault cease is sent to the BSC.

For some fault types, the cause of the disturbance disappears

when the MO is disabled. These fault types are therefore
latched, which means there are no possible fault stop conditions
until the procedure is executed and terminated. The only way to
stop a latched fault is to block and deblock the concerned
equipment through the use of the commands 5;%/, and
5;%/(.

– 206 – EN/LZT 123 3801 R2A

 8 BTS Maintenance

Disturbance Description
The disturbance sources in the BTS are a number of internally
supervised test points. The test points can be component,
equipment part, or a physical parameter. When the supervision
detects that a predefined limit for normal operation has been
exceeded during a predefined time interval, a disturbance has
occurred. Disturbances are fed through a fault filtering
mechanism to the fault detectors. Each fault detector controls an
individual fault state bit within the fault map. The fault filtering
mechanism is a classification algorithm for disturbances. A
single disturbance may cause a fault due to its seriousness or a
number of disturbances over a certain time interval are needed
before a fault is issued. All faults do not have a specific
disturbance identity.

Fault and Replacement Unit Maps

When a fault is reported in the BSC, that report also includes
information about the most probable RU where the fault may be
located. In some cases several possible RUs may be identified.

'HFRGLQJRI)DXOW0DSV All fault and RU codes consist of a

number of hexadecimal digits, in most cases twelve. These
twelve digits represent a map that consists of 48 bits. Each bit
represents a decimal number and can be translated into a
description by using thefault class and RU maps. An exception
is the code for an external fault. These codes contain only four
hexadecimal digits (16 bits). The decoding principle is the same
as for the twelve digit code.

EN/LZT 123 3801 R2A – 207 –

GSM BSC Operation

Fault Code 0 0 0 0 0 0 0 2 8 0 0 0

47 - 44 43 - 40 39 - 36 35 - 32 31 - 28 27 - 24 23 - 20 19 - 16 15 - 12 11 - 8 7-4 3-0
0 0 0 0 0 0 0 2 8 0 0 0

Hexadecimal to Binary Conversion

47 - 44 43 - 40 39 - 36 35 - 32 31 - 28 27 - 24 23 - 20 19 - 16 15 - 12 11 - 8 7-4 3-0
0 0 0 0 0 0 0 2 8 0 0 0
0000 0000 0000 0000 0000 0000 0000 0010 1000 0000 0000 0000

19 18 17 16
0 0 1 0
Bit 17 Active 15 14 13 12
1 0 0 0
Bit 15 Active

Figure 8-4 Conversion Process

Error Log
The error log is a memory area in the BSC used for storing fault
information received from a BTS. The error log contains
information received in the BTS Fault Reports and information
about when the different reports were received. Information
provided per entry in the error log printout includes: MO, MO
class, the date the entry was made, and the time the entry was
made.

– 208 – EN/LZT 123 3801 R2A

 8 BTS Maintenance

BTS State
The BTS state shows the last known state of the MO in the BTS.
Possible BTS states are:

RES RESet
STA STArted
DIS DISabled
ENA ENAbled

FAULT REPORT HANDLING

Faults fall into one of the following fault categories:

%765HSRUWHG)DXOWV These are faults or events reported by

the BTS.

)DXOWVUHSRUWHGIURPWKHUHPRWH7UDQVFRGHU These are faults

in speech and data transmission equipment reported by the
remote Transcoder.

%76/LQN)DXOWV These are faults in the signaling links to the

BTS.

6\VWHP,QWHUQDO)DXOWV These faults occur when a MO has

behaved in an abnormal way.

BTS Reported Faults

Faults in a BTS are reported to the BSC on a MO basis. The
Fault Report indicates one or more of the following:

• LMT Intervention Arising

• LMT Intervention Ceasing
• Spontaneous MO Reset
• Fault Affecting Functionality Arising
• Fault Affecting Functionality Ceasing
• Fault Not Affecting Functionality Arising
• Fault Not Affecting Functionality Ceasing

When an MO is manually blocked, no action is taken on the

BTS Reported Fault Reports except that they are acknowledged.
Each type of fault requires different handling. These are
described below.

EN/LZT 123 3801 R2A – 209 –

GSM BSC Operation

/07,QWHUYHQWLRQ$ULVLQJ When/RFDO0DLQWHQDQFH
7HUPLQDO/07 intervention is reported, it means a BTS
operator is currently performing local maintenance actions.
During LMT intervention, there can be no communication from
the BSC to the MO. The MO is taken out of operation and any
associated logical channels are taken out of the traffic process.

/07,QWHUYHQWLRQ&HDVLQJ When LMT intervention finishes,

the state of the MO is unknown. The MO is reset, conditionally
loaded and tested, and BTS parameters updated while being
brought back into operation. If the test result indicates a fault,
the MO will remain out of operation.

6SRQWDQHRXV025HVHW This is reported when the MO in the

BTS has been reset, but not under BSC control. When this
occurs, the MO is taken out of operation and any associated
logical channels are taken out of the traffic process. The MO is
reset again, conditionally loaded, tested and BTS parameters
updated while being brought back into operation. If the test
result shows that there is a fault, the MO remains out of
operation. If the test proves the unit to be fault free, the fault is
classified as an intermittent fault and the MO brought back into
operation. The Intermittent Fault Counter for that MO is then
incremented.

)DXOW$IIHFWLQJ)XQFWLRQDOLW\$ULVLQJ This situation arises

when the BSC receives a Fault Report indicating a fault in the
MO’s operational functionality (a class 1A fault, class 1B fault
or BTS external class 1B fault). When this occurs, the MO is
taken out of operation and any associated logical channels are
taken out of the traffic process. However, if the fault is a BTS
external class 1B fault indicating lost synchronization on the
speech and data path, then it will be treated the same way as
TRA synchronization faults. For a class 1A fault, a test is
performed to verify the fault. If the test proves the unit to be
fault free, then the fault is classified as an intermittent fault and
the MO brought back into operation. The Intermittent Fault
Counter for that MO is then incremented. If the test result
indicates a fault, then the MO remains out of operation.

– 210 – EN/LZT 123 3801 R2A

 8 BTS Maintenance

)DXOW$IIHFWLQJ)XQFWLRQDOLW\&HDVLQJ This occurs when the

BSC receives a Fault Report indicating no more faults for that
MO. If the MO has had a fault affecting functionality then the
MO is conditionally loaded, tested, and its BTS parameters
updated while being brought back into operation.

)DXOW1RW$IIHFWLQJ)XQFWLRQDOLW\$ULVLQJ On receipt of a
fault report indicating a fault not affecting functionality, a class
2 fault has occurred. The Alarm Coordination function is
informed.

)DXOW1RW$IIHFWLQJ)XQFWLRQDOLW\&HDVLQJ On receipt of a
fault report indicating all faults not affecting functionality, a
class 2 fault has stopped. The Alarm Coordination function is
informed.

BTS Link Faults

Disturbances affecting 2SHUDWLRQDQG0DLQWHQDQFH/LQN
20/ or 5DGLR6LJQDOLQJ/LQN 56/ links are reported to
the Handling of BTS Related Faults function. There are three
types of links affected by disturbances:

OML-TC The link to the TRU. One link per TRU.

OML-TGC The link to the active TGC application. One

link per TG.

RSL The link to the TCHs. One link per TRU.

For each link type, there are four types of reports:

Disturbed Indicates something is going wrong with the

link and another report will soon follow.

OK Link previously reported disturbed or faulty,

has now recovered. Communication is
restored.

Change Link previously reported disturbed, could not

be recovered. However, a spare signaling
device was used as a replacement.
Communication is restored.

Fault Link is not usable.

The following table summarizes actions taken depending on link

type and report type.

EN/LZT 123 3801 R2A – 211 –

GSM BSC Operation

OML-TC OML-TGC RSL-TRXC

Report Type
Disturb ignore ignore 5
OK1 ignore ignore 7
OK2 1 3 4
Change 1 ignore ignore 7
Change 2 1 3 4
Fault 2 3 6
Table 8-1

Key to Table
2. This is when Link OK occurs after Link Disturbed.
2. This is when Link OK occurs after Link Fault.
&KDQJH This is when Link Change occurs after Link
Disturbed.
&KDQJH This is when Link Change occurs after Link Fault.
 Bring affected MOs back into operation
automatically.
 Take affected MOs out of operation.
 Inform TGC Handling.
 Any associated BPCs can be made available for
traffic.
 Block BPCs without forced release.
 Block BPCs with forced release.
 Deblock BPCs.

System Internal Faults

A system internal fault occurs when the BSC identifies an MO
operating in an abnormal way, e.g., a message to the BTS times
out without receiving a reply. When such a fault occurs, this
function waits a certain length of time and then attempts to
discover the fault reason. During this period, the MO is taken
out of operation. If no fault reason is discovered, the MO resets,
is conditionally loaded and tested, and its BTS parameters are
updated while being brought back into operation.

– 212 – EN/LZT 123 3801 R2A

 8 BTS Maintenance

BRINGING MOs INTO OPERATION

The actions described in the following sections are involved in
bringing an MO back into operation.

Checking for too Many Faults Occurring

These faults can be faults affecting functionality reported by the
BTS; LMT Intervention, Spontaneous MO Reset or System
Internal Faults. MOs that report more than a specified number of
such faults during a given time are called unstable objects.
Unstable MOs will be permanently taken out of operation,
preventing possible disturbance of traffic. Manual blocking and
deblocking are then required to put the MO back into operation
again.

A Leaky Bucket algorithm is used to calculate when an MO is

permanently faulty. Each MO Class has a threshold, a timer, an
increment value and a decrement value. Each 0DQDJHG2EMHFW
,QVWDQFH 02, also has a counter. If the counter exceeds the
threshold for that MO Class then the MOI is unstable. The MOI
counter is incremented by the increment value when a fault
affecting functionality is received in a BTS reported Fault
Report. A timer is then started for the MOI. When the timer
expires, the MOI counter is reduced by the decrement value for
the MOIs MO Class. When the MOI is being brought back into
operation the MOI counter is checked. If the MOI counter
exceeds the threshold for that MO Class, then the MOI is
unstable and classified as permanently faulty.

Verifying BTS Data

This verifies that the data the MO has stored in the BTS
corresponds to that stored in the BSC. Verification is not carried
out if the MO is to be tested. The data read from the BTS and
compared with the BSC consists of software version, fault data,
state and configuration data. If the software version or checksum
is wrong, the MO is loaded, tested, and the BTS parameters are
updated. If the fault data does not correspond and the BTS
indicates a fault affecting functionality, then the MO is taken out
of operation. If a fault not affecting functionality is indicated,
then BTS Alarm Handling is informed. The BSC fault data is
updated with the BTS fault data. If configuration data does not
correspond, then the MO is reconfigured.

EN/LZT 123 3801 R2A – 213 –

GSM BSC Operation

Updating BTS Data

This function refreshes any BTS Internal Parameters that may
have been lost when the affected MO was taken out of
operation. It updates any data that was found to be inconsistent
by utilizing the Verifying BTS Data function. Once a MO is
back in operation it can be configured. This can result in logical
channels being made available for the traffic process.

Configuration of the BTS

The purpose of this function is to take a configuration
specification and match it to available BTS equipment. The
function then configures the BTS equipment accordingly. Once
the equipment has been set up to match the configuration
specification, this function attempts to maintain the
configuration. If insufficient BTS equipment is available to
match the configuration specification, the best possible result is
provided. In addition to the non-hopping configuration of
channels, the capability to maintain frequency hopping channels
is also provided. The configuration specification is provided by
the cell configuration function. This includes the nominal power
levels required for the cells connected to the TG being
configured. It also includes groups of channel combinations
along with their desired ARFCN and, for a hopping system,
0RELOH$OORFDWLRQ,QGH[2IIVHW0$,2. This function gives
all channels that could be supported by BTS equipment to the
cell configuration function as BPCs.

Testing the Affected MO

If the test indicates a fault, then the MO is kept out of operation.

FUNCTION CHANGE AND PROGRAM LOAD OF MO

Function Change
The MO function change is the loading of predetermined
software packages in all loadable MOs which are manually
deblocked. These MOs belong to a specific BTS manufacturer
and are administered by the BSC. The function change is
performed successively for each TG, and allows the traffic on
the rest of the system to remain unaffected. During the TG
function change, the parallel loading of TRUs and MOs is
performed.

– 214 – EN/LZT 123 3801 R2A

 8 BTS Maintenance

The software version defined per TRU or its TG includes a

header file and loadable software file for each MO. The function
change ensures that the replacement version in the BSC is
loaded in each manually deblocked TRU and its subordinate
deblocked MOs. During the function change, the identity of the
actual software version is changed to the replacement software
version.

After the function change, the MOs are restored to operation.

The function change of MOs can be conditionally or
unconditionally ordered. For unconditional MO function
changes, no checks are performed to verify if these files already
exist in the TRU and associated MOs. The replacement software
is reloaded to each TRU and subordinate MO. For conditional
function changes, the software reload for MOs takes place only
if the replacement software in the BSC does not correspond to
the operational software in the BTS. During this initial check,
the traffic is not interrupted. If the software checks fail, then
traffic is halted until the loading is complete and the MOs are
operational.

Following the function change, the updated software versions

are used for any subsequent automatic MO software loading.
This ensures that the BTS operates employing the changed
functionality. For MOs which are manually blocked during the
function change, only the identity of the actual software version
is changed. This software version is reloaded when it is
manually deblocked. If the command is given to abort the
function change process, it stops after completing the software
loading for the TG in progress. No attempts are made to switch
back to the previous TG functionality if new versions of
software have already been loaded in MOs.

Program Load
The MO program load is the loading of predetermined software
packages in specific MOs which are in service. These MOs
belong to a specific BTS manufacturer and are administered by
the BSC. The program load function allows the operator to load
software in MOs in service. Command initiated program load is
performed on an MO basis.

5;3/,02 5;27* 8&,2 $7

The MO program load follows the same procedure as a function

change. During the MO program load, software upload, file
transfer and loading of logical units takes place. Command

EN/LZT 123 3801 R2A – 215 –

GSM BSC Operation

initiated program loading of MOs can be ordered conditionally

or unconditionally. When a MO is specified for program
loading, all subordinate MOs are loaded at the same time.

After the MO program load, the changed software version is

employed for any subsequent automatic software loading of
MOs. If the command is given to abort the program load
process, it stops after completing the software loading of the
MO which is in progress. No attempts are made to switch back
to previous MO functionality if new versions of software are
already loaded in the MOs.

5;3/(02 5;27*

– 216 – EN/LZT 123 3801 R2A

 8 BTS Maintenance

TRI MAINTENANCE

GENERAL
The PCM links connected to the TRI and the equipment in the
TRI are continuously supervised. If a fault occurs, equipment
will be automatically blocked and an alarm issued. The operator
may then test the equipment by command, repair it and put it
back into service.

The function of the executive and standby synchronization

references are continuously supervised as well. Short
interruptions and disturbances will not cause any action. If an
interruption or disturbance of long duration is detected on the
executive reference, the executive and standby references are
automatically swapped. This is done without any additional
disturbance. On detection of a faulty synchronization reference,
an alarm is issued. If neither reference is accepted the TRI will
generate its own clock and semipermanent connections are then
released. Synchronization inlets may also be manually swapped
by command.

5,&6&(0* HPJ(056 HPUV

Parent Exchange TRI-EM

RS
PCM
ETC ETB RTT BTS
GS TSW
STC STR ETB PCM

CP RPB EMRP I/O V.24

EMRPB
ALARM

DEVCB

Figure 8-5 TRI-EM connected to parent exchange

EN/LZT 123 3801 R2A – 217 –

GSM BSC Operation

MAINTENANCE OF RADIO INTERFACE LINE TERMINAL

Supervision of hardware
An alarm is issued when continuous supervision detects a fault
in a RILT or when a RILT is manually blocked. Supervision is
turned off for a blocked device.

A2/APT "CME2O-BSC /CNA4" 165 960512 1140

RADIO INTERFACE LINE TERMINAL FAULT

EMG DEVICE EQMTYPE FCODE

GSMl RILT-9 RTT 2

Figure 8-6 Alarm indicating faulty RILT

Restoration of an automatically blocked RILT

In order to put equipment back into service, automatic tests are
made at regular intervals and, if equipment is considered fault
free, it is deblocked. The device must be fault free for 60
seconds before an alarm cease is received. In the case of three
alarms within 24 hours, the device is considered permanently
faulty and thereby the alarm will not cease.

Blocking and deblocking of devices

RILT devices can be blocked and deblocked manually by
command or automatically when faults have been detected by its
own supervision. To manually block and deblock a RILT device,
the commands 5,%/( and 5,%/, are used. This allows the
operator to put equipment into service or take an operating or
faulty RILT out of service. Before a RILT can be blocked, the
associated semipermanent connection must be terminated.

Manually test of devices

It is possible to test a manually blocked device of type ETB. The
command allows the operator to localize faulty equipment.
RILTs of type RTT can not be tested. The resultant printout
RADIO INTERFACE LINE TERMINAL TEST RESULT
indicates a fault by means of Result codes.

– 218 – EN/LZT 123 3801 R2A

 8 BTS Maintenance

The commnads to be used are:

5,63(76/27 5,/7 

5,%/,'(9 5,/7 

5,%/,'(9 5,/7

5,77,'(9 5,/7

MAINTENANCE OF EXTENSION MODULE RADIO SELECTOR

Supervision of hardware
Hardware is continuously supervised. An alarm is issued when
continuous supervision detects a fault in an EMRS or when an
EMRS is manually blocked. Supervision is turned off for a
blocked EMRS.

Al/APZ”CME2O-BSC/CNA4”121 960322 1221

RADIO SELECTOR SUPERVISION

EMG EMRS STATE FCODE FTYPE

GSM1 0 BLOC 45 STABLE

Figure 8-7 Alarm indicating Radio Selector fault

Restoration of an automatically blocked EMRS

To put equipment back into service, automatic tests are made at
regular intervals, and if equipment is considered fault free, it is
deblocked.

Routine tests of a EMRS

Routine tests are performed on a working or idle EMRS at
regular intervals.

Blocking and deblocking of a EMRS

An EMRS can be blocked and deblocked manually by command
or automatically, when faults have been detected by its own
supervision. To manually block and deblock an EMRS, the

EN/LZT 123 3801 R2A – 219 –

GSM BSC Operation

commands 5,%/( and 5,%/, are used. This allows the

operator to put equipment into service or take an operating or
faulty EMRS out of service. Associated RILTs must be blocked
before an EMRS is blocked.

Manual test of a EMRS

An EMRS can be manually tested. The EM must be working
and the EMRS must be manually blocked before the test. The
resulting printout RADIO SELECTOR TEST RESULT
indicates a fault by means of result codes.

The commands to be used are:

5,63(76/27 5,/7 

5,%/,'(9 5,/7 

5,%/,'(9 5,/7

5,%/,(0* *60(056 

5,57,(0* *60(056 

EMG FAULT
When the alarm EMG FAULT is issued, the faulty unit can
either be an EMRP (EMPC-card) or a STR. The unit can still be
in operation if the fault is of a temporary nature. If the fault is
permanent, the unit will be automatically blocked. To put the
unit back into service, automatic tests are made at regular
intervals, and if the unit is considered fault free, it is deblocked.

A1/APZ”CME20-BSC/CNA4”112 960202 1154

EMG FAULT

EMG UNIT STATE

GSM1 EMRP-0-A ABLOCK

Figure 8-8 Alarm indicating EMG FAULT

After reception of an alarm, the repair sequence is as follows:

– 220 – EN/LZT 123 3801 R2A

 8 BTS Maintenance

Diagnosis
By using the command 5(3(,, a diagnostic test is ordered. This
command also activates a function for recording board
replacements. A recording will be carried out if this command is
followed by the commands 5(0(, and 5(&(,.

Result printout EMG DIAGNOSIS contains a list of cards

suspected to be faulty. According to weights, the most suspected
card is selected.

Replacement of suspected card

The command 5(0(, is given before a board is replaced in the
EMG. The resultant printout EMG MANUAL
INTERVENTION shows the necessary actions in connection
with the board replacement.

Repair check
The command 5(&(, is used to order the testing of a repaired
unit in the EMG. If no fault is detected when the test is run, the
repaired unit is put into service and the alarm is ceased. If a fault
is detected during the testing of a unit, the fault is recorded and
the unit is blocked. The resulting printout EMG REPAIR
indicates if the unit has passed or failed the test.

EMG CONTROL DOWN

The alarm EMG CONTROL DOWN indicates that no active
control path exists to the indicated EMG. The printout specifies
failing system parts that have contributed to exclusion of the
control path, for which measurements should be taken to repair
the fault.

For example, if an STC is indicated, the OPI 53)$8/7 should

be followed. If an STR is indicated, the OPI (0*)$8/7
should be followed. If a system line fault is indicated, one of the
existing SNT or DIP alarms should be acted upon.

EN/LZT 123 3801 R2A – 221 –

GSM BSC Operation

A1/APZ”CME20-BSC/CNA4”254 960115
1048

EMG CONTROL DOWN

EMG

GSM1

SIDE PART
A RBLT-16
A STR-A

A2/APZ”CME20-BSC/CNA4”253 960115
1048

EMG FAULT

EMG UNIT STATE

GSM1 STR-A CBLOCK

Figure 8-9 EMG CONTROL DOWN alarm, with affiliated alarm

(;(*3(0* *60

EMG DATA

EMG TYPE SIDE RP LINK ST STRTYPE MAST EMGNUM

GSMl REMOTE A 110 CLC-0 BL STR2C IDLE 0

(;(33(0* *60(0 $//

EMGEM PROCESSOR CONTROL STATE

EMO EM PROCESSOR TYPE PATH STATE MAINTSTATE

GSM1 0 A EMRP3 A CBLOCK IDLE

Figure 8-10 Resulting CLC and EM state

– 222 – EN/LZT 123 3801 R2A

 8 BTS Maintenance

TRI STATUS INDICATOR

The installed red LED plug on the EMPC board indicates the
following EMRP status:

FAST FLASH EMRP is blocked or not initiated

from BSC.

VERY SLOW FLASH EMRP is loaded with software and

activated.

RESET BUTTON Resets EMRP when pushed.

127( 7KHEXWWRQVKRXOGEHOHIWLQLWVRXWPRVWSRVLWLRQ

EN/LZT 123 3801 R2A – 223 –

GSM BSC Operation

t io
e n na
lly
t
In

Bl n
a
k

– 224 – EN/LZT 123 3801 R2A