Diagnostics and Fault Handling

FUNCTION SPECIFICATION 1(33)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
ERALIOM EPLAND 40/155 17−HRB 105 01 Uen

Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference
ERA/LRT/C 1999−11−25 E
DIAGNOSTICS AND FAULT HANDLING
Table of Contents
1 Introduction 3
1.1 Purpose and Readers 3

1.2 Scope 3
1.3 Abbreviations 4
1.4 References 4
1.5 Terminology 5
1.6 Revision History 6
2 General 7
2.1 Overview 7
2.2 Fault classes 8
2.3 Filter types 8
2.4 Latching of fault 10
3 Function: Fault installation 11
4 Function: Fault detection 12
4.1 Subfunction: Fault filtering 14

4.2 Subfunction: Fault evaluating 15
4.3 Subfunction: Fault classification 15
5 Function: Fault localization 17
6 Function: Local action 18
7 Function: Fault reporting 19
8 Function: Monitoring of MO fault status 20
9 Function: Fault logging 21
10 Function: Disturbance logging 22
11 Function: Status request 23
12 Function: Test of MO 24
LZF 032 41/1M RJ
13 Function: RBS diagnostics 25
14 Function: RBS diagnostics future 27
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec
FUNCTION SPECIFICATION 2

ERA/LRT/C 1999−11−25 E
15 Function: Read of RBS diagnostics information 29
16 Function: RU diagnostics logging 30
17 Function: Read of RU diagnostics log 32
18 Function: Request of relations between SO and RUs 33

LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
1 INTRODUCTION
1.1 PURPOSE AND READERS
Purpose
The functions in the TRS system, viewed as a black box,
derived from GSM specifications or Ericsson internal
requirements, are defined.
Readers
− system developers, who will partition the system
into subsystems, allocate requirements to them and
verify the requirements with product management etc
− system verifiers, who will assure testability of the
requirements and write test specifications according to
the requirements
− product management, who want to know the system
functionality and present it to potential customers
1.2 SCOPE
Diagnostics and Fault handling regards the functionality

of detecting and reporting of malfunctions within the
RBS and diagnostics of the RBS.
The fault detection function shall detect at least 99%

of all faults and the diagnostics shall pinpoint at least
98% of all faults to one RU. The probability that a
fault is localized to a wrong RU shall be minimized.
The rate of false alarms shall be less than 100 false

alarms/Mhrs, and less than 10 false alarms/Mhrs for
alarms that result in service actions.
Diagnostics and Fault handling does not interfere with

the RBS traffic operation.
This document will describe the following functions:
− Fault installation
− Fault detection
− Fault localization
− Local action
− Fault reporting
− Monitoring of MO fault status
− Fault logging
− Disturbance logging
− Status request
− Test of MO
− RBS diagnostics
LZF 032 41/1M RJ
− Read of RBS diagnostics information
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
− RU diagnostics logging
− Read of RU diagnostics log
− Request of relations between SO and RUs
1.3 ABBREVIATIONS
AO Application Object
HWU Hardware Unit
ME Managed Entity
MO Managed Object
OMT Operation and Maintenance Terminal
RU Replacement Unit
SE Supervised Entity
SO Service Object
TG Transceiver Group
1.4 REFERENCES
/FS−term/ 0033−1/FCP 103 313 Uen

Common FS terminology
/Abis−1/ 1/155 19−CRT 241 07 Uen

Abis O&M interface, part I, functions and
structured procedures
/Abis−2/ 2/155 19−CRT 241 07 Uen

Abis O&M interface, part II, procedures
/Sys−spec/ 1029−FCP 103 313 Uen

System specification for RBS 2000
/ARS1−A/ 1/122 61−FCP 103 313 Uen

Application requirement specification 1
(ARS1) for CME R5A/BTS
/ARS1−B/ 2/122 61−FCP 103 313 Uen

Application requirement specification 1
(ARS1) for CME R5B/BTS
/Proc−spec/ LT/SU−93:5023 Uen

CME 201/BSS. Operation and Maintenance
process
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
/Req−spec/ LT/SD−1056−093 Uen

BTS diagnostic information handling,
CME201 R5/BSS
/FS_OMSUP/ 24/155 17−HRB 105 01 Uen

FS O&M Support functions
1.5 TERMINOLOGY
Supervised Entity (SE):

See /FS−term/.
Hardware unit (HWU):

See /FS−term/.
Replaceable unit (RU):

See /FS−term/.
Managed Object (MO):

See /FS−term/.
Service Object (SO):

See /FS−term/.
Application Object (AO):

See /FS−term/.
RBS Operational States:

See /FS−term/.
RU modes:
See /FS−term/.
Operation and Maintenance Terminal (OMT):

See /FS−term/.
Managed Entity (ME):

A HWU, RU, SO or a AO.
Fault maps:
Information about a ME fault status are stored in
fault maps capable of indicating the presence or
absence of all possible faults for a ME.
RU map:
Information about suspected faulty RUs are stored in a
RU map capable of indicating all suspected faulty units
corresponding to the current contents of the fault
maps.
Fault status:
LZF 032 41/1M RJ
Fault maps, RU map and state for a ME (RU map only for
SO and AO).
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
SW log:
The SW log is a circular RAM log where debug and
verification information is stored. The log are only
for Ericsson internal use.
The log is placed in volatile memory and its contents

are therefor always lost at power failure.
1.6 REVISION HISTORY
Rev Date Purpose

PB1 940809 Added cr1..cr15.
B 940815 Approved after final review.
PC1 950508 Added cr16A, cr17A and cr19A
C 950511 Approved.
PD1 951013 Added CR #20 and 21
D 951016 Approved after FR
E 980917 Added CR #24
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
2 GENERAL
2.1 OVERVIEW
Figure 1 shows the different object types with

attributes and functions who is relevant for the
diagnostics and fault handling functionality.
――――――――――――――――――――――――――――――――――――――――――――――――――――
| Object | Attribute | Function |
――――――――――――――――――――――――――――――――――――――――――――――――――――
| RBS | Diagnostics | RBS Diagnostics |
| | information | Read of RBS diagnostics |
| | | information |
――――――――――――――――――――――――――――――――――――――――――――――――――――
| SO | Faultmaps | Fault evaluating |
| | RU map | Fault classification |
| | MO State | Fault localization |
| | | Fault reporting |
| | | Monitoring of MO fault |
| | | status |
| | | Status request |
| | | Test of MO |
| | | Request of relations |
| | | between SO and RUs |
――――――――――――――――――――――――――――――――――――――――――――――――――――
| AO | Faultmaps | Fault evaluating |
| | RU map(always | Fault classification |
| | empty) | Fault reporting |
| | MO state | Status request |
| | | Test of MO |
――――――――――――――――――――――――――――――――――――――――――――――――――――
| RU | Faultmaps | Fault evaluating |
| | Diagnostics log | Fault classification |
| | | RU diagnostics logging |
| | | Read of RU diagnostics log|
――――――――――――――――――――――――――――――――――――――――――――――――――――
| HWU | Faultmaps | Fault filtering |
| | | Fault classification |
| | | Fault logging |
| | | Disturbance logging |
――――――――――――――――――――――――――――――――――――――――――――――――――――
| SE | Disturbance | Fault installation |
| | | Fault filtering |
| | | Fault classification |
| | | Local action |
―――――――― ――――――――――――――――― ―――――――――――――――――――――――――――
Figure 1 : Object types
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
2.2 FAULT CLASSES
Faults are divided into five classes:
Internal class 1A
Faults that do or may affect the ME functionality and
the fault origin is in the ME.
Internal class 1B
Faults that do or may affect the ME functionality and
the fault origin is outside of the ME but within the TG.
Internal class 2A
Faults that do not affect the ME functionality and the
fault origin is in the ME.
External condition class 1

Conditions that do or may affect the ME functionality
and the fault origin is outside of the TG.
External condition class 2

Conditions that do not affect the ME functionality and
the fault origin is outside of the TG.
2.3 FILTER TYPES
The list below shows the fault filter types that can be
used when installing an SE.
− Received disturbance frequence

This filtertype is based on received disturbance
frequency.
Example.
Freq class1 12
Freq cease class1 8
Freq class2 5
Freq cease class2 0
Freq time interval 10 s
Supervised time interval 0.5 s
Class 2 fault is set when 5 disturbances are received

in 10 seconds. Class 1 fault is set and class 2 fault
is ceased when 12 disturbances are received in 10
seconds. When the disturbancefrequency has decreased
to 8 disturbance in 10 seconds, class 1 fault is ceased
and class 2 fault is set. Class 2 fault is then ceased
when there are 0 disturbances in 10 seconds.
Every 0.5 seconds a new measurement is performed to

LZF 032 41/1M RJ
see if a disturbance has occured. In this example there

will be maximum 20 disturbances in 10 seconds, each
every 0.5 seconds.
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
− Leaking disturbance counter

This filtertype is based on the number of received
disturbances.
Every time a disturbance is received a counter is

incremented, if the counter is less than ’Leak max
level’. After each ’Leak time’ the counter is decremented
’Leak step’ times, if the value of the counter is greater
than ’Leak step’.
Example
Leak class1 12
Leak cease class1 8
Leak class2 5
Leak cease class2 3
Leak step 2
Leak time 10 s
Leak max level 100
Class 2 fault is set when the counter is equal to 5.

Class 2 fault is ceased and class 1 fault is set when
the counter is equal to 12. Class 1 fault is ceased and
class 2 fault is set when the counter is equal to 8.
Class 2 fault is ceased when the counter is equal to 3.
Each ’Supervised time interval’ a measurement is

performed to see if a disturbance has occured. In this
example a measurement is performed every 0.5 seconds.
This means, the counter can increase with 18 (20−2)
every 10 seconds.
It takes about 60 seconds before the counter is equal

to ’Leak max level’. If disturbances are ceased it will
take 500 seconds until the counter is equal to 0.
− Absolute
When the fault filter is of absolute type the fault
filterering is done in the SE. The SE report if the
fault is present or not.
− Measurement report
This filtertype is based on received
measurement reports. Measured values are transferred into
disturbances. Measured value which fulfils the criteria
for a class 2 fault will generate a class 2 disturbance.
Measured value which fulfils the criteria
for both class 1 and class 2 fault will generate both a
class 1 disturbance and a class 2 disturbance. The
final filtering is based on the frequency of generated
disturbances.
LZF 032 41/1M RJ
Measured value will generate a class 2 disturbance

if one of the following criterias are fulfilled:
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
measured value >= ’Meas upper threshold class 2’

measured value <= ’Meas lower threshold class 2’
Measured value will generate a class 1 disturbance

if one of the following criterias are fulfilled:
measured value >= ’Meas upper threshold class 1’

measured value <= ’Meas lower threshold class 1’
Example.
Meas class1 12
Meas cease class1 8
Meas class2 5
Meas cease class2 2
Meas upper threshold class1 7
Meas lower threshold class1 3
Meas upper threshold class2 6
Meas lower threshold class2 4
Meas time interval 10 s
Class 2 fault is set when 5 measurement reports has

generated 5 class 2 disturbances in 10 seconds.
Class 2 fault is ceased and class 1 fault is set when
12 measurement reports has generated 12 class 1
disturbances in 10 seconds. Class 1 fault is ceased
and class 2 fault is set when the number of class 1
disturbances decreased to 8 in 10 seconds. Class 2
fault is ceased when the number of class 2 disturbances
decreased to 2 in 10 seconds.
Every ’Supervised time interval’ a measurement is

performed. In this example a measurement is performed
every 0.5 seconds. This means the maximum number of
disturbances are 20 in 10 seconds.
2.4 LATCHING OF FAULT
Class 1B faults in the RBS with low probability to be

ceased without external actions and detected by
supervision functionality that is dependent on MO
State, are latched in the RBS as long as supervision
function is inactive or until reset of supervision
function at software restart.
The reason is to avoid a situation with cyclic

repetition of rasing or ceasing of a fault following
a MO state change.
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
3 FUNCTION: FAULT INSTALLATION
Operational Conditions
RBS operational state = Any state
RU mode = Local/Remote
Initiation
Applications software start.
Description
When the applications software is started all SEs will
report its identity and fault parameters. Fault
parameters includes fault filter type, fault criteria
for class 1 and class 2 and fault cease criteria.
There must be some hysteresis between the
fault criteria and fault cease criteria. If fault is
internal or external to MO or BTS will not be
installed.
When the fault filtering parameters has been reported,

the fault is said to be installed.
The fault criteria and fault cease criteria can be

changed due to reconfiguration of the RBS (over Abis or
from OMT).
Termination
The fault is installed.
Fault Handling
Not applicable
Capacity
Not applicable
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
4 FUNCTION: FAULT DETECTION
Initiation
Not applicable
Description
This function detects malfunctions in the RBS system.
Hardware and functionality faults within the RBS are
handled by this function. The RBS shall be capable of
supervision itself even without traffic being present.
The fault detection function is splitted in three

subfunctions, fault filtering, fault evaluating and
fault classification.
The following figures describe the relations between

the different subfunctions. The flow of fault
information will also be described.
The XXX_fault_map a to b in the figures below describes

that there is one fault map for each fault class
described in chapter 2.2.
The SEs 0 to n reports disturbances to the fault

filtering function, f(SE(0..n)). The fault filtering
function and the fault classification function, g1(),
will update the HWU_Fault_map a to b. The fault
filtering function can be done in the SE or in the
HWU depending on the fault filter type.
― HWU x ―――――――――――――――――――――――――――――――――――――――――――――――
| ―――― ――――――――――――――――― |
| |SE 0― ―→| HWU_Fault_map a | |
| ―――― | | ――――――――――――――――― |
| . | | . |
| . ――― g1(f(SE(0..n)))―――― . |
| . | | . |
| ―――― | | ――――――――――――――――― |
| |SE n― ―→| HWU_Fault_map b | |
| ―――― ――――――――――――――――― |
―――――――――――――――――――――――――――――――――――――――――――――――――――――――
Figure 2 : Relation between SEs and HWU
The HWUs fault maps are evaluated by the fault

evaluating function, h1(HWU(0..m)). The fault
evaluating function and the fault classification
function, g2(), will update the RU_Fault_map a to b.
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
The HWUs fault maps are also evaluated by the fault

evaluating function, h2(HWU(0..m)). The fault evaluating
will update the AO_fault_map a to b.
One HWU can affect more then one AO but only one RU.
― RU y ―――――――――――――――――――――――――――――――――――――――――――――――――
| ――――― ―――――――――――――――― |
| |HWU 0― ―→| RU_Fault_map a | |
| ――――― | | ―――――――――――――――― |
| . ――― g2(h1(HWU(0..m)))――― . |
| . | | . |
| . ― | . |
| ――――― | | | ―――――――――――――――― |
| |HWU m― | ―→| RU_Fault_map b | |
| ――――― | ―――――――――――――――― |
―――――――――――――――――――――――――――――――――――――――――――――――――――――――
|
―――― AO 0 − m ――――――――――――――――――――――――――――――――
| | ―――――――――――――――― |
| | ―→| AO_Fault_map a | |
| | | ―――――――――――――――― |
| ― g3(h2(HWU(0..m)))――― . |
| | . |
| | ―――――――――――――――― |
| ―→| AO_Fault_map b | |
| ―――――――――――――――― |
―――――――――――――――――――――――――――――――――――――――――――――――
Figure 3 : Relation between HWUs and RU/AO
The RUs fault maps are evaluated by the fault

evaluating function, h3(RU(0..j)). The fault evaluating
will update the SO_fault_map a to b.
― SO ―――――――――――――――――――――――――――――――――――――――――――――――――――
| ―――― ―――――――――――――――― |
| |RU 0― ―→| SO_Fault_map a | |
| ―――― | | ―――――――――――――――― |
| . | | . |
| . ―――― g4(h3(RU(0..j)))―――― . |
| . | | . |
| ―――― | | ―――――――――――――――― |
| |RU j― ―→| SO_Fault_map b | |
| ―――― ―――――――――――――――― |
――――――――――――――――――――――――――――――――――――――――――――――――――――――――
Figure 4 : Relation between RUs and SO
Termination
LZF 032 41/1M RJ
Not applicable
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
Fault Handling
Not applicable
Capacity
Not applicable
4.1 SUBFUNCTION: FAULT FILTERING
Initiation
The Selftest and Supervision function has detected a
disturbance.
Description
All disturbances are filtered before a fault is said to
be present or absent. Each fault has a fault filter with
its own fault filter parameters which is adapted for best
performance.
Fault filtering can be performed in the SE or in the

HWU.
− Fault filtering in the SE

If the fault filter is of absolute type the fault
filterering is done in the SE. The SE then report if
the fault is present or not.
− Fault filtering in the HWU

If the fault filter is not of absolute type the SE only
report the disturbance or the measurement to the HWU
where the fault filterering is done.
Fault filter
――――――――――――――
Disturbance/ | |
Measurement | Fault filter | Fault present/
――――――――――――→| parameters ―――→ Fault absent
| |
| |
――――――――――――――
The fault filtering function together with the fault

classification function updates the HWU_fault_map a to
b.
Dependent on supervision function and fault

characteristics, fault latching is performed in fault
LZF 032 41/1M RJ
filtering as long as supervision function is inactive

or until reset of supervision function.
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
Termination
If the fault criteria or the fault cease criteria is
passed the fault is raised or ceased and the fault
logging function is initiated.
Fault Handling
Not applicable
Capacity
Not applicable
4.2 SUBFUNCTION: FAULT EVALUATING
Initiation
A change in fault status for a HWU or a RU.
Description
This function evaluates the input fault maps and tries
to find out the actual fault cause.
The fault evaluating function together with the fault

classification function updates the RU_fault_map a to b
and/or the MO_fault_map a to b.
Termination
If the evaluation affects MO(s) the fault status are
reported to the fault report function.
Fault Handling
Not applicable
Capacity
Not applicable
4.3 SUBFUNCTION: FAULT CLASSIFICATION
Initiation
The fault filtering function or the fault evaluating
function has detected or ceased a fault.
Description
The fault classification function decides the severity
LZF 032 41/1M RJ
of the fault, affecting functionality or not affecting
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
functionality, and also if the fault is internal or

external of the TG/ME. For description of the fault
classes see chapter 2.2.
Termination
The fault has been classified.
Fault Handling
Not applicable
Capacity
Not applicable
Accuracy
Depending on the fault class, the BSC can take
different actions. Therefore it is very important that
the fault is correctly classified.
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
5 FUNCTION: FAULT LOCALIZATION
Initiation
The fault detection function has found a change in
fault status for a RU.
Description
This function is used to localize a detected fault to
possible faulty RU.
― SO ――――――――――――――――――――――――――――――――――――――――
| ―――― |
| |RU 0― |
| ―――― | |
| . | ―――――――――――――――― |
| . ――f(RU(0..i))―――→| SO_RU_map | |
| . | ―――――――――――――――― |
| ―――― | |
| |RU i― |
| ―――― |
―――――――――――――――――――――――――――――――――――――――――――――
Figure 5 : Relation between RUs and SO_RU_map
If the fault status has changed for a RU, its related

SO compile a new SO_RU_map.
Termination
The new SO RU map for the affected SO is reported to the
fault report function.
Fault Handling
Not applicable
Capacity
Not applicable
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
6 FUNCTION: LOCAL ACTION
Initiation
The fault detecting function has detected a fault
for a SE.
Description
When a fault is detected for a SE it can be possible
to minimize the affect of the fault. It is called a
local action.
Allowed local actions:
− Reinitiation
For example, if a bus is faulty the bus circuit is
reinitiated.
− Fault isolation
If the fault can cause equipment damage, the equipment
is isolated (switched off). For example, too high
temperature in a transmitter.
− Fault compensation
For example if a fan unit is faulty then rpm of the
other fan units are increased.
Note. The supervision must continue after a local

action has been performed.
When the fault is ceased the local action is stopped.
Termination
If it is possible to perform a local action on the SE,
the local action was performed.
Fault Handling
Not applicable
Capacity
Not applicable
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
7 FUNCTION: FAULT REPORTING
RBS operational state = IO/RFU/IU
RU mode = Remote
Initiation
The fault detection function or the fault localization
function reports new fault status for a MO. Both
functions must have been completed before start of this
function.
Description
This function reports MO fault status to the BSC. The
old fault status is compared with the new fault status.
If the fault status has changed for a MO a FAULT REPORT
procedure is initiated on Abis.
Termination
The FAULT REPORT procedure is terminated.
Fault Handling
Not applicable
Capacity
Not applicable
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
8 FUNCTION: MONITORING OF MO FAULT STATUS
RU mode = Remote/Local
Initiation
A command from OMT.
Description
This function monitors fault status for all MOs.
When the fault status has changed for a MO, the OMT
is updated with the new fault status. The function
updates initially the OMT with all MO fault maps that
have faults set in them.
Termination
A command from OMT.
Fault Handling
Not applicable
Capacity
Not applicable
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
9 FUNCTION: FAULT LOGGING
Fault logging = ON
Initiation
A fault has been raised or ceased by the fault filtering
function and fault classification function.
Description
All fault changes are logged in the SW log with
timestamp. Fault logging is ON by default.
Termination
The fault change has been stored in the SW log.
Fault Handling
Not applicable
Capacity
Not applicable
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
10 FUNCTION: DISTURBANCE LOGGING
Disturbance logging = ON
Initiation
The Selftest and Supervision function has detect a
disturbance.
Description
All detected disturbance are logged in the SW log.
Disturbance logging is OFF by default.
Termination
The detected disturbance has been stored in the SW log.
Fault Handling
Not applicable
Capacity
Not applicable
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
11 FUNCTION: STATUS REQUEST
RU mode = Remote
Initiation
STATUS REQUEST received on Abis.
Description
This function provides a reading of current fault
status for the requested MO.
Termination
STATUS RESPONSE is sent.
Fault Handling
See /Abis/.
Capacity
Not applicable
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
12 FUNCTION: TEST OF MO
RU mode = Remote
Initiation
TEST REQUEST procedure is initiated on Abis.
Description
No actual test is performed when TEST REQUEST is
received. Only current fault status for the requested
MO will be returned.
Termination
TEST RESULT procedure is initiated on Abis.
Fault Handling
See /Abis/.
Capacity
Not applicable
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
13 FUNCTION: RBS DIAGNOSTICS
Initiation
The fault detecting function has reported a change in
fault status for a HWU.
Description
The purpose of this function is to make conclusions about
where the original fault source is located. The
diagnostics function has access to fault maps for
the whole RBS, not only for a MO. The RU fault map has
information about which SE(s) that has reported fault.
The handling of LED−indicators is dependent on type of

cabinet:
− Macro building system
If there is any fault at the RBS, this function shall

switch on BS fault indicator. If this function can
pinpoint the fault to a RU with 100% probability,
it shall switch on the fault indicator on that RU.
If the fault affects functionality and the RU is not

in remote mode, then the operational indicator on the RU
shall be switched off.
− Micro building system
If there is any fault at the RBS and it can be

pinpointed to the master cabinet with 100% probability,
the fault indicator shall be switched on. If there is a
fault external to the master cabinet the fault
indicator in the master cabinet shall start flashing.
If the fault affects CMRU−functionality or all

TDMRU−functionality in the master cabinet and the RBS
is not in remote mode, then the operational indicator
in the master cabinet shall be switched off.
If the RU is in local mode the reduced capacity

indicator shall be handled as specified in /FS_OMSUP/.
No additional tests will be performed to collect more

fault information.
Termination
LZF 032 41/1M RJ
Not applicable
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
Fault Handling
Not applicable
Capacity
The diagnostics function shall pinpoint at least 98% of
all faults to one RU.
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
14 FUNCTION: RBS DIAGNOSTICS FUTURE
Initiation
The fault detecting function has reported a change in
fault status for a HWU.
Description
The purpose of this function is to make conclusions about
where the original fault source is located. The
diagnostics function has access to fault information for
the whole RBS, not only for a MO. So it can do a much
better fault localization than the fault localization
function.
When the function is started a co−ordinate timer is set

to be able to collect more fault information. A fault
collecting timer is also set to be able to supervise
the maximum time limit for collecting of fault. If more
fault information is received before the co−ordinate
timer expire, the co−ordinate timer is restarted. If
the fault collecting timer or the co−ordinate timer has
expired, the function will start to analyse the fault
information for the whole RBS. If more fault
information is needed the diagnostics function can
request tests which is performed by the Selftest and
supervision functionality.
The result of the diagnostics function shall contain at

least the following:
− Calender time
A time stamp indicating when the diagnostics was
completed.
− Fault severity
Indicate if the fault affect functionality or not.
− Fault indication
The fault indication identifies the nature of the fault
(e.g. local bus, watchdog reset, TX temperature
fault).
− Replacement unit identity

A specific RU shall be identified with RU logical
identity, article number, revision, serial number,
and physical position.
− Replacement unit probability

LZF 032 41/1M RJ
The probability that the RU is faulty (in percentage).
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
The result shall be stored so it can be read by the read

of diagnostics information function.
Termination
The diagnostics logging function shall be initiated and
if a fault is pinpointed to a single RU, an indicator
light on the RU shall indicate the fault.
Fault Handling
Not applicable
Capacity
The diagnostics function shall pinpoint at least 98% of
all faults to one RU.
Timers and times:
Maximum diagnostics time = see reference /Abis−1/.
Co−ordinate timer = 10 seconds
Fault collecting timer = Maximum diagnostics time −

maximum test time − maximum analyse time
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
15 FUNCTION: READ OF RBS DIAGNOSTICS INFORMATION
Initiation
DIAGNOSTIC INFO REQUEST procedure is initiated on Abis
or a command is reveived from the OMT.
Description
This function provides a reading of current diagnostics
result. The diagnostics result shall be encoded using
a restricted CCITT alphabet No 5 according to
ref /ABIS−2/.
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
| 94−01−19 23:46 |
| |
| Faults that do or may affect functionality: |
| |
| TRA |
| 10% TRU−3, ROF 366 143/2, R2A/A, SN 1223A63, Cab1, |
| Shelf1, Slot3 |
| 90% External RBS |
| |
| Watchdog reset |
| 100% TRU−7, ROF 366 143/2, R2A/A, SN 1223A01, Cab2, |
| Shelf1, Slot1 |
| |
| Faults that do not affect functionality: |
| |
| Checksum fault in RXU EEPROM |
| 100% TRU−2, ROF 366 143/2, R2A/A, SN 1223B67, Cab1, |
| Shelf1, Slot2 |
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
Figure 6 : Exampel of a diagnostics result printout
Termination
DIAGNOSTIC INFO RESULT procedure is initiated on Abis
or a reply is sent to the OMT.
Fault Handling
See /Abis/.
Capacity
The length of each line is restricted to 63 characters
and a maximum of 64 lines is permitted. The result
shall be reported within the time specified for the
Diagnostics information procedure, see reference
/Abis−1/.
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
16 FUNCTION: RU DIAGNOSTICS LOGGING
Initiation
The diagnostics function has pinpointed a faulty RU
with 100% probability.
Description
All RUs having a processor on−board has a persistent
storage where information about fault changes within the
RU is stored. This storage is named RU diagnostics log.
Only the diagnostics logging function has permission to
store information in the RU diagnostics log.
When the diagnostics function has done a new diagnos,

the diagnostic logging function check if the fault
information for any RU has changed. If it has, the new
fault information is stored in the RU diagnostics log
for that RU. The RU diagnostics log is used as a
plane log. This means that when the log is full no more
fault information is stored in the log.
The fault information include:
− Calender time
A time stamp indicating when the diagnostics was
performed.
− Fault state
Indicate if the fault was raised or ceased.
− Fault severity
Indicate if the fault affect functionality or not.
− Fault indication
The fault indication identifies the nature of the fault
(e.g. local bus, watchdog reset, TX temperature
fault).
The fault information shall be encoded using CCITT

alphabet No 5.
Figure 7 shows an example of fault information

logged in the RU diagnostic log (one record).
―――――――――――――――――――――――――――――――――――――――――――――――――――――――
| 94−01−19 23:46, Fault set, class 2, Checksum fault in |
| RXU EEPROM, |
―――――――――――――――――――――――――――――――――――――――――――――――――――――――
LZF 032 41/1M RJ
Figure 7 : Example of a RU log record.
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
Termination
If the fault information for any RU has changed the new
fault information is stored in the RU diagnostics log.
Fault Handling
Not applicable
Capacity
A RU shall be able to store 100 records.
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
17 FUNCTION: READ OF RU DIAGNOSTICS LOG
Initiation
A command from OMT.
Description
All information in the RU diagnostics log are read from a
specified RU.
Termination
A reply to the OMT.
Fault Handling
Not applicable
Capacity
Not applicable
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

ERA/LRT/C 1999−11−25 E
18 FUNCTION: REQUEST OF RELATIONS BETWEEN SO AND RUS
Not applicable
Initiation
Request from OMT.
Description
This is a general function which implicitly is used by
functions who has to know the relations between a SO
and its related RUs. A list of RUs related to the
specified SO is returned as result. The function must
not be explicity referred to.
Termination
A respons to the OMT.
Fault Handling
Not applicable
Capacity
Not applicable
LZF 032 41/1M RJ
(hrb10501;t4_75)d40_15517.tec;0o1 d40_15517.tec

Diagnostics and Fault Handling

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Diagnostics and Fault Handling

Uploaded by

Copyright:

Available Formats

FUNCTION SPECIFICATION 1(33)

ERALIOM EPLAND 40/155 17−HRB 105 01 Uen