A Quick Ref For Commandhandling

A Quick Ref for commandhandling of the APT 210 09 R7 (CMER6.
1/BSC_POLO) Page 1 of 132
report
Prepared Date Rev Document no.
eeiltn 1996-09-02 PA3 EEI/RGV-96:0054Uen
Approved Checked File/reference
eei/rgc Leo Theunissen
A QUICK REF FOR COMMANDHANDLING

OF THE APT 210 09 R7
(CMER6.1/BSC_POLO)
Contents:
1 Introduction
2 Managed object handling
2.1 G12
2.2 Managed Object Specific Properties
2.3 Operation and Maintenance Communication
3 Subrate Swith
4 Radio Transmission Subsystem, RTS
4.1 Command descriptions
4.1.1 Device SW Unit handling (RRDSL/RRDSP/RRDSE)
4.1.2 TRA Pool handling (RRTPC/RRTPE/RRTPI/RRTPP)
4.1.3 TRA Pool Mean Hold Supervision handling (RRMSE/RRMSI/RRMSP)
4.1.4 TRA Pool Mean Hold Supervision Alarm Handling (RRMAP/RRMAR)
4.1.5 TRA Pool Idle Supervision Handling (RRISE/RRISI/RRISP)
4.1.6 Manual blocking/deblocking TRA devices (RRTBI/RRTBE)
4.1.7 Line level handling (RRLLC/RRLLP)
4.1.8 TRH LOAD (RA-HII/HDC/HDP/HHP/HTP/HPP/HLC/HAR/HEP)
4.2 RTS command parameter information
4.2.1 Comand parameter, alphabetical order
4.3 RTS Command Fault code information
4.4 RTS Printout Parameter Descriptions
5 Tranceiver Administration Subsystem, TAS
5.1 Command Descriptions
5.1.1 Definition of MO, commands RXMOI/E/P/C
5.1.2 Abis path handling , commands RXAPI/RXAPE/RXAPP
5.1.3 TG To Channel Group ,commands RXTCI/RXTCE/RXTCP
5.1.4 MO in service, commands RXESI/RXESE,
5.1.5 commands RXMSC, MO in service data
5.1.6 Status of MO, commands RXMSP
5.1.7 Capabilities of MO, RXCAP
5.1.8 commands RXBLI/RXBLE, Blocking of MO
5.1.9 commands RXPLI/RXPLE, FC & PL of MO
5.1.10 Test of MO, commands RXTEI/RXTEE,
5.1.11 BSC-BTS Loop Test, commands RXLTI
5.1.12 MO congiguration data print, commands RXCDP,
5.1.13 MO Error Log Print , commands RXELP/RXELR
5.1.14 MO Hopping Data Print, commands RXHDP
5.1.15 MO Hopping Frequency set extension measuring program, commands RXHMI/RXHMP/R
5.1.16 MO Device Information Print, commands RXMDP,
5.1.17 MO Fault Information Print, commands RXMFP,
5.1.18 Alarm Coordination Data , RXALC/RXALP/RXASP
5.2 TAS command parameter information
http://users.eei.ericsson.se/eeir/RGV/html/R61/commandhandling.html 01/04/2004
A Quick Ref for commandhandling of the APT 210 09 R7 (CMER6.1/BSC_POLO) Page 2 of 132

5.3 TAS Printout Parameter Descriptions
5.3.1 Printout parameter, alphabetical order
5.4 TAS Command Fault code information
6 Link Handling Subsystem, LHS
6.1.1 Commands RIETI, RIETE, Radio Interface Equipm. Type, Init/End
6.1.2 Commands RISPI, RISPE RISPP Radio Interface Semiperm. Path, Init/End/Print
6.1.3 Commands RICSC, RICSP, Clock Sync. status, Print/Change
6.1.4 Commands RILSP, RILTP , Line Terminal (Status), PRINT
6.1.5 Commands RIRTI, RITTI, Radio Selector Test & Line Terminal Test
6.1.6 commands RIBLI, RIBLE, Radio Interface, Blocking/Deblocking
6.1.7 Commands RISTP, RIDCP, Radio Selector (Disturbance counters) PRINT
6.1.8 RADIO INTERFACE LAPD CONCENTRATOR , RICCI/RICCE/RICCP/RICBI/RICBE/RICBP
6.2 LHS Faultcode Information
7 Radio O&M Subsystem, ROS
7.1 Command description
7.1.1 Call path tracing in the BSC, RAPTI
7.1.2 Commands RADPI/RADPE/RADPP, BSC (CCITT) Destination Point Code Initiate
7.1.3 Commands RADCI/RACPE/RADCP, BSC (ANSI) Destination Point Code Initiate
7.1.4 Commands RARMC, RARMP Transmission Type
7.1.5 Commands RASIC, RASIP, Signalling Type
7.1.6 commands RASSI/RASSE/RASAR/RASSC/RASAP, Seizure Supervision of Devices,
7.2 Commands RATRI/RATRE/RATRP, Cell Traffis Recording commands
8 ROS, Command Faultcode information
9 Radio Control Subsystem, RCS
9.1.1 Radio Control Cell System Type, RLTYI/RLTYP/RYLTE/RYLTC
9.1.2 Commands RLDEI, RLDEP, RLDEE, RLDEC, Definition Of Cell
9.1.3 Commands RLDSI, RLDSE, Definition of subcell,
9.1.4 Commands RLDTC, RLDTP, Data administration TSC,
9.1.5 Commands RLCFI, RLCFP, RLCFE, RLCHC, Config. Frequency Data,
9.1.6 Commands RLDGI, RLDGE, RLDGC, Definition Of Channel Group,
9.2 Commands RLDCI, RLDCP, RLDCE, Diff. Channel Alloc. Data
9.2.1 Commands RLMFC, RLMFP, RLMFE, Measurement Frequencies
9.2.2 Commands RLCPC, RLCPP, Config. Power Data
9.3 Command RLCCC, Config Control Channel Data
9.3.1 Commands RLBDC, RLDBP, Configuration BPC DATA
9.3.2 Commands RLCAC, RLCAP, BSC Ciphering Algorithm
9.3.3 Commands RLSTC, RLSTP, Cell STATE,
9.3.4 Commands RLCXC, RLCXP, Configuration, DTX Downlink,
9.3.5 Commands RLCRP, Cell Resources
9.4 Commands RLNRI, RLNRE, RLNRC, RLNRP, Neighbouring Relation
9.4.1 Cell locating Area, RLLAP
9.5 Commands RLLDP, RLLDC, Cell Locating Disconnect Data
9.6 Commands RLLOC, RLLOP, Cell Locating Data
9.7 Commands RLLUC, Locating Urgeny Data,
9.8 Commands RLLBC, Locating BSC Data,
9.9 Commands RLLFP, Locating FILTER Data
9.10 Commands RLLHC,RLLHP , Locating Hierarchical Data
9.11 Commands RLOLC, RLOLP,Locating Overlaid Subcell Data
9.12 Commands RLLPC, Locating Penalty Data
9.13 Commands RLIHP, RLIHC, Locating Intracell Handover Data
9.13.1 Commands RLURI, RLURP
9.14 Commands RLPCI, RLPCP, RLPCC , Dynamic MS PWR Cell Control Data
9.15 Commands RLBCI, RLBCP, RLBCC , Dynamic BTS PWR Cell Control Data
9.15.1 Commands RLMBI, RLMBC, RLMBP, RLMBP, Cell Broadc. Message
9.15.2 Commands RLMTI, RLMTP, Cell Broadcast Distr. Time
9.16 System Information
9.16.1 Commands RLSSC, RLSSP, System Info SACCH & BCCH Data
9.16.2 Commands RLSBC, RLSBP, System info BCCH Data
9.16.3 Commands RLSMC, RLSMP , System Information BCCH Message Distribution
9.16.4 Commands RLVLI, RLVLC, RLVLP, RLVLE, Sup. of Logical Channels,
9.16.5 Commands RLVAP, RLVAR, Supervision of ALARM,
9.16.6 Commands RLSLI, RLSLC, RLSLP, RLSLE, Supervision of Logical Channels Availab
9.16.7 CELL CONNECTION OF CELL TO CHANNEL ALLOCATION , RLHPC/RLHPP
9.16.8 CELL IDLE CHANNEL MEASUREMENT CHANGE, RLIMC/RLIMI/RLIMP
9.16.9 CELL LOAD SHARING DATA , RLLCC/RLLCE/RLLCP
9.16.10 BSC LOAD SHARING DATA , RLLSI/RLLSE/RLLSP
9.16.11 CELL BSC BAND OPERATING MODE CHANGE, RLOMC/RLOMP
9.16.12 CELL BSC DIFF. CHANN. ALLOC. PRIO. PROFILE, RLLPPC/RLLPI/RLLPE
9.16.13 CELL BSC DIFF. CHANN. ALLOC. PRIO. TO RESOURCE TYPE , RLPRC/RLPRI/RLPRP
9.16.14 CELL BSC DIFF. CHANN. ALLOC. STATISTICS, RLSCE/RLSCE/RLSCP/RLDSP
9.17 RCS fault codes
9.17.1 Fault Codes in Numerical Order
10 Translation between the ABIS O&M IWD and BSC command parameters
10.1 BTS logical model G01
10.2 BTS Logical Model G12
1 Introduction
This document is ment as a quick reference when using the CMER6.1/BSC = APT210 09 R7 =
BSCR7
This document is NOT an official document and so will not be inspected and so some
mismatches, spelling mistakes etc.. could be expected
Command and printout information for the following Subsystems are covered by this
Document.:
LHS ANT 239 03 =R1
RCS ANT 240 06 =R1
TAS ANT 241 06 =R1
ROS ANT 248 04 =R1
RTS ANT 242 01 =R1
This document is stored in DELTA:

CME20_BSC:CME_R6.1/BSC:VERIFICATION/R6.1:V-ADM/r6.1
This PA3 revision has the RTS commands,TAS co commands are not on R6.1 level yet.
Currently the RCS/ROS/LHS commads are on R6 level. This beaciuse the R5 lazy ref has to be
updated to R6 first in order to go to R6.1.
By end of august 1996 this document is expected to be completly updated for R6.1
2 Managed object handling
2.1 G12
A managed object cannot perform any traffic function if it is not operational. Some objects
depend on other objects to be able to be operational, that is be automatically deblocked from
superior object. In the G12 TG the following relationships are valid:
TG (Superior)
| |
V |
CF |
| |
V |
+----+----+----+----+ |
V V V V V |
TRXC IS DP CON TF |
| |
V |
+---+---+ |
V V V |
RX TX TSs (Subordinate)
If a managed object is out of operation then its subordinate managed objects will also be taken
out of operation.
An application object must be configured to be used for its traffic function. Whether an
application object is configured or not is reflected by a configuration state.
A managed object can be defined, taken into service and manually deblocked.
The order for bringing managed object instances into service is TG first followed by CF before
its corresponding TRXCs, IS, DPs, TF and CON; and TRXC before its corresponding TX, RX
and TS. The manual deblocking will start the process of bringing a managed object into
operation. The managed object will then automatically be available to carry traffic.
Similarly, a managed object can be manually blocked to bring it out of operation, taken out of
service and removed. The order for taking managed object instances out of service is TX, TS
and RX before the corresponding TRXC;
TRXC, IS, CON, DP and TF before the corresponding CF; and CF before the corresponding
TG.
2.2 Managed Object Specific Properties

This chapter describes specific managed object properties from an operational and maintenance
point of view. However, it will not mention functional differences, which are described in other
functional specifications.
TG
The managed object TG cannot be communicated with over the Abis interface for operation
and maintenance. Thus, it cannot be tested, configured etc. However, if the managed object TG
is allowed in a command, it may refer to all managed objects within that TG. For example,
program load of a TG means program load of all managed objects belonging to that TG.
CF
The CF stores the software for itself the IS, DP and TF within the same TG.
TRXC
The TRXC stores the software files for itself and its dedicated RX, TX and TS.
TX, RX and TS
The TXs, RXs and TSs in a TG can be configured when they are operational. This
configuration makes the managed object possible to use for traffic purposes. In this case the
traffic purpose is to support the created basic physical channels.
If any TX, RX or TS cannot fulfill its assigned traffic function, the influenced logical channels
will be taken out of traffic. A managed object cannot fulfill its traffic function when it is out of
operation. However, a TS will not be able to fulfill its traffic functions, if the TF is not
synchronised or the radio signalling link is not working. A TS can support traffic channels and
signalling channels if the speech and data path is working. If the speech and data path is not
working then the TS can still support signalling channels. However, neither of these
circumstances will take the managed object TS itself out of operation.
IS
The IS is configured when operational in a similar way to the TXs, RX and TS however the IS
is not used directly for traffic functions. The IS is configured with data that sets up connections
between two DCPs. A connection is only considered made when the IS is enabled. Once
enabled connections will survive some fault situations and even a reset.
CON The CON is configured when operational in a simular way to the TX, RX and TS.
However, the CON is not used directly fro traffic functions . The CON is configured with data
thats sets up the internal connetctions between a concentrated path and it's associated un-
concentrated path, or paths.
A connection is only considered to have been made when the CON BTS state is ebnabled.
When a connection has been made, the CON BTS stae is set to disconnected in advance of any
future configurations.
CON connecions will survive some fault situations
DP
The DP is configured when operational in a similar way to the IS. The DP is configured with
data that specifies DIP Fault and Quality supervision of the associated PCM system. Data is
only allowed to be changed in BTS state disabled. Once enabled the supervision functions are
activated.
TF
The TF can be started with new software without losing synchronisation.
2.3 Operation and Maintenance Communication
All communication to and from the managed objects go through either a TRXC or the CF.
Each RX, TX and TS has a dedicated TRXC, through which its communication passes. The IS,
DP and TF are reached through the CF.
Communication is made with the CF and TRXC once these managed objects are brought into
service.
For the TRXC, the route through the IS will be made between the specified digital connection
point (DCP) described at definition of the TRXC and the specified DCP of any available abis
path.
For the CF, communication will be established automatically on any of the available abis paths.
+--------------------------+
| CF |
| |
+-+--------+-----+-----+----+
| | | |
| +-+-+ +-+-+ +-+-+
| |CON| |TF | |DP | -+
| +---+ +---+ +---+ | (2 DPs)
| +---+
|OML-C
+--|--+
OML-C | . | +-----+ +--+
--------.... | |TRXC +---+RX|
OML-TC | | OML-TC | | +--+
--------.......---------+ | +--+
| | | +---+TS++
| | | | ++-+| (8 TSs)
| | | | +--+
| IS | | | +--+
| | | +---+TX|
| | | | +--+
| | +-----+
| |
| | +-----+ +--+
| | |TRXC +---+RX|
OML-TC | | OML-TC | | +--+
--------.......---------+ | +--+
| | | +---+TS++
| | | | ++-+| (8 TSs)
| | | | +--+
| | | | +--+
| | | +---+TX|
| | | | +--+
| | +-----+
+-----+ .
.
(16 TRXCs)
TC = Transceiver Control
C = Common control
3 Subrate Swith
} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ~
! 0 }"""""""~ !
}"""""""~ }"""""""""""""\ }"""""#"~ }""""""""""""""""""""~
! SNT ! [""#"""""""""""""]"\ T S M ! ! }"""""""""""""""""#"""~ !
|"""""""{ . ! ! ["""""""""""\ ! S P M !
. ! . 15 ! ! ["""""""""""]""\ ! !
}"""""""~ }"""""""""""""\ ! ! ! ! !
! SNT ! [""#"""""""""""""]"\ ! ! ! ! !
|"""""""{ |"\ ! ! ! !
! |"""""""{ ! ! ! !
. ! ! !
! }"""""""~ ! ! ! !
}"""""""~ }"""""""""""""\ }"""""#"~ ! ! !
! SNT ! [""#"""""""""""""]"\ T S M ["""""""""""\ ! ! !
|"""""""{ ! ! ["""""""""""]""\ !
} - - - - - - { ! ! ! ! ! ! !
}"""""""~ ! ! ! ! ! !
! !}""""""#~ |"\ ! ! ! ! !
!!}""""""#~ |"""$"""{ ! ! !
! !!! C L M [""""""""""""""""""""""""""{ ! ! ! !
|\! [""""""""""""""""""""""""""""""""""""""""""\ ! !
! |\ [""""""""""""""""""""""""""~ ! ! ! !
|"""""""{ }"""""#""""~ ! ! !
! ! }""""""""#"~ ! ! ! !
}""""""""""""""""~ ! ! TSM ! ! ! !
! !}"""""""""""""""#~ 0 ! ! WITH [""""""""\ ! ! !
!! S R S M ["""""""""\ ! PARALLEL [""""""""]""\ !
! !! ["""$"""""]"\ INTER- ! ! ! ! !
!! ! ! |"\ FACE ! ! ! !
! !! ! ! |""""""""""{ ! ! ! !
!! !Each . ! ! !
! !! !Interface . ! ! ! !
!! !has 512 }""""""""""~ ! ! !
! !! !TimeSlots! }""""""""#"~ ! ! ! !
!! ! ! ! ! TSM ! ! ! !
! !! ! ! 7 ! ! WITH [""""""""\ ! ! !
!! ["""#"""""\ ! PARALLEL [""""""""]""\ !
! !! ["""""""""]"\ INTER- ! ! ! ! !
|\ ! |"\ FACE ! ! ! !
! |""""$"$"""$"$"""{ |$"$"$"$"""{ |""\ ! !
|"\ |"\ |"\ |"\ |"""""""""""""""""""""{
| - - - - - \ - - \ - - - - - - - - \ - \ - - - - - - - - - - - - - - - - - - - - -{
}"#"""""]""~ }"""#"""]""~ G S S
! }"""""#""#"~ ! }"""""#""#"~
! ! R P ! ! ! R P !
|"\ ! |"\ !
|""""""""""{ |""""""""""{
4 Radio Transmission Subsystem, RTS

4.1.1 Device SW Unit handling (RRDSL/RRDSP/RRDSE)
RADIO TRANSMISSION DEVICE SOFTWARE UNIT, LOAD
+ +
| SUID=suid | + +
RRDSL:SNT=snt..., + + |,UC| ;
| SUNAME=suname | + +
+ +
RADIO TRANSMISSION DEVICE SOFTWARE UNIT,
PRINT
RRDSP:SNT=snt...;
END
+ +
| snt... |
RRDSE:SNT=+ + ;
| ALL |
+ +
4.1.2 TRA Pool handling (RRTPC/RRTPE/RRTPI/RRTPP)
RADIO TRANSMISSION TRANSCODER POOL
CHANGE
+ +
RRTPC:TRAPOOL=trapool,RNOTRA=rnotra ... |,FORCE | ;
+ +
END
RRTPE:TRAPOOL=trapool;
INITIATE
RRTPI:TRAPOOL=trapool, CHRATE=chrate,SPV=spv;
PRINT
+ +
| ALL... | + +
RRTPP:TRAPOOL=+ + |,FORCE | ;
| trapool... | + +
+ +
4.1.3 TRA Pool Mean Hold Supervision handling (RRMSE/RRMSI/RRMSP)
RADIO TRANSMISSION TRANSCODER POOL MEAN HOLD SUPERVISION
END
+ +
| ALL... |
RRMSE:TRAPOOL=+ + ;
| trapool... |
+ +
INITIATE
+ + + +
| ALL... | | A1 | + +
RRMSI:TRAPOOL=+ + , ACL= + A2 + |,MHTLIM=mhtlim | ;
| trapool... | | A3 | + +
+ + + +
PRINT
+ +
| ALL... |
RRMSP:TRAPOOL=+ + ;
| trapool... |
+ +
4.1.4 TRA Pool Mean Hold Supervision Alarm Handling (RRMAP/RRMAR)
PRINT
+ +
| ALL... |
RRMAP:TRAPOOL=+ + ;
| trapool... |
+ +
REMOVE
+ +
| ALL... |
RRMAR:TRAPOOL=+ + ;
| trapool... |
+ +
4.1.5 TRA Pool Idle Supervision Handling (RRISE/RRISI/RRISP)
END
+ +
| ALL... |
RRISE:TRAPOOL=+ + ;
| trapool... |
+ +
INITIATE
+ + + +
| ALL... | | A1 | + + + +
RRISI:TRAPOOL=+ + , ACL= + + |,LIM1= lim1 | |,LIM2= lim2 | ;
| trapool... | | A3 | + + + +
+ + + +
PRINT
+ +
| ALL... |
RRISP:TRAPOOL=+ + ;
| trapool... |
+ +
4.1.6 Manual blocking/deblocking TRA devices (RRTBI/RRTBE)
BLOCKING
+ +
RRTBI:DEV=dev... |,FORCE |;
+ +
DEBLOCKING
RXTBE:DEV=dev...;
4.1.7 Line level handling (RRLLC/RRLLP)
Line level, Change
+ +
|+ ++ +|
||+ +|| + +||
|||ULP=ulp||| |DLP=dlp|||
RRLLC:+|+ +||,+ +|+;
|||ULN=uln||| |DLN=dln|||
||+ +|| + +||
|+ ++ +|
+ +
Line level Print
RRLLP;
4.1.8 TRH LOAD (RA-HII/HDC/HDP/HHP/HTP/HPP/HLC/HAR/HEP)
TRH LOAD DISTRIBUTION IMMEDIATE , PRINT
RAHII;
TRH LOAD DISTRIBUTION DISTRIBUTION PERIODIC, INITIATE

+ +
RAHPI + :MP =mp + ;
+ +
TRH LOAD MONITORING AND DISTRIBUTION DATA , CHANGE
+
| + + + +
RAHDC: + |,CAPHYST=caphyst| |,CAPLIM= caplim |
| + +
+
+
+ + + + |
|,INTERVAL= interval | |,STIME= stime | +
+ + + + |
+
TRH LOAD MONITORING AND DISTRIBUTION DATA , PRINT
RAHDP;
TRH LOAD LOAD TABLE, PRINT
+ +
| snt... |
RAHHP:SNT=+ + ;
| ALL | ,HIGH| |
+ +
TRH DEVICE LOAD TABLE, PRINT
+ +
| snt... |
RAHTP:SNT=+ + ;
| ALL |
+ +
TRH LOAD PERIODIC DISTRIBUTION STATE, PRINT
RAHHP;
TRH LOAD TRESHOLD DATA , PRINT
RAHLP;
TRH LOAD TRESHOLD DATA , CHANGE

+
| + + + +
RAHLC: + |,AVELIM=avelim| |,NOTRHLIM= notrhlim |
| + + +
+
+
+ + |
|, TRHLIM= trhlim | + ;
+ + |
+
TRH LOAD TRESHHOLD EXCEEDED, RESET
RAHAR;
TRH EVENT LOG PRINT
+ +
RAHEP + :NOINT =noint +;
+ +
4.2 RTS command parameter information

4.2.1.1 ACL - Alarm Class
ACL=acl Specifies the type of alarm to be isued

A1, A2 or A3
4.2.1.2 DEV
DEV=dev Transcoder multiplexed (MUX) device to be blocked.
Format is of the type "devicetype-individual";

RTTRDis the devicetype for full-rate (FR) transcoder
supported by R2 and R3 hardware.
RTTF1Dis the devicetype for FR transcoder supported
by R4 hardware.
RTTF2Dis the devicetype for enhanced full-rate (EFR) or
FR transcoder supported by R4 hardware.
RTTH2D is the devicetype for half-rate (HR) transcoder
supported by R4 hardware.
FR/EFR transcoder MUX individuals are valid if they belong
to the following series ...2,7,12,17,22,27,34,39 ... 10939
HR transcoder MUX individuals are valid if they belong to
the following series ...2,12,22,34,44,54,66 ... 10934.
4.2.1.3 DLN Dwnlink negative Line Level
DLN=dln Downlink negative Line Level

Adjustments
Paramter given is dB
Numeral 0 - 12
Default value: refer to application
information for RTTRC
4.2.1.4 DLP Dwnlink positive Line Level
DLP=dlp Downlink positive Line level

Adjustments
Numeral 0 - 12
4.2.1.5 FORCE
FORCE Force Adjustment

Pemits unconditional removal of transcoder resources
from the transcoder pool.
The parameter has no effect when increasing the
number of transcoder resources in a transcoder pool
4.2.1.6 LIM1 - Limit 1
LIM1=lim1 Limit 1
Percent: 1 -99
Alarm limit for idle transcoder resources in the
transcoder pool, in percent of actual number of transcoder
resourses for the transcoder pool. The lower and less
severe limit.
4.2.1.7 LIM2 - Limit 2
LIM2=lim2 Limit 2
Percent: 1 -99
Alarm limit for idle transcoder resources in the
transcoder pool, in percent of actual number of transcoder
resourses for the transcoder pool. The lower and more
severe limit.
4.2.1.8 MHTLIM - Mean Hold Time Limit
MHTLIM Mean Hold Time

seconds: 1 - 3600
The mean hold time in seconds, which implies
that a transcoder recourse is operating properly.
4.2.1.9 PRINTDEV - Print Devices
PRINTDEV printdevices
Specifies that the devices belonging to the
transcoder pools are printed
4.2.1.10 RNOTRA - Required number of transcoder resources
RNOTRA=rnotra Integer
The required number of transcoder
resources in the transcoder pool
4.2.1.11 TRAPOOL, Transcoder Pool
TRAPOOL=trapool Identifier 1 - 7 characters.

Specifies the name of the transcoder pool(s)
4.2.1.12 SNT - Switching Network Terminal
SNT=snt Switching network terminal associated with the

Transcoder Rate Adaptor-Extention Module (TRA-EM)
to be loaded.
Format is of the type "SNT type-individual" where
SNT type = RTTF1S, RTTF2S, RTTH2S or RTTRS
4.2.1.13 SUID- Software Unit Identity
SUID=suid Software Unit Identity

Text string 1-32 characters
4.2.1.14 SUNAME-Software Unit Name
Software Unit Identity

Identifier 1-8 characters
4.2.1.15 UC - Unconditional
UC The Device Software Unit (DSU) will be loaded even

if it has the same SUID/SUNAME as the already loaded DSU.
i.e. Unconditional.
4.2.1.16 ULN - Uplink negative Line Level
ULN=uln Uplink negative Line Level adjustments
Numeral 0 - 12
4.2.1.17 ULP - Uplink positive Line Level
ULP=ulp Uplink positive Line Level adjustments
Numeral 0 - 12
4.3 RTS Command Fault code information
FAULT CODE 1
TRANSCODER POOL ALREADY EXISTS
Pool name to be defined

already exists.
FAULT CODE 2
TRANSCODER POOL WITH SPECIFIED CHANNEL SERVICE ALREADY EXISTS
Transcoder pool with specified channel

service already exists.
FAULT CODE 3
TOO MANY ARGUMENTS
Too many transcoder MUX devices have

been specified in the same command.
FAULT CODE 4
TRANSCODER POOL WITH SPECIFIED CHANNEL SERVICE IS NOT SUPPORTED
The requested channel service is not

supported. Hardware does not exist to
support the requested combination of
channel rate and speech version.
FAULT CODE 5
TRANSCODER POOL DOES NOT EXIST
FAULT CODE 6
TRANSCODER POOL IDLE LEVEL SUPERVISION IS CONNECTED
FAULT CODE 7
TRANSCODER POOL MEAN HOLD TIME SUPERVISION IS CONNECTED
FAULT CODE 8
TRANSCODER RESOURCES ARE ASSIGNED TO POOL
All transcoder resources have not been

removed from the pool.
FAULT CODE 9
TRANSCODER POOL ALREADY CONNECTED TO IDLE LEVEL SUPERVISION
It is not possible to connect a transcoder

pool to idle level supervision, which is
already connected to idle level supervision.
FAULT CODE 10
TRANSCODER POOL IDLE LEVEL SUPERVISION IS NOT CONNECTED
It is not possible to disconnect transcoder

pool idle level supervision from a transcoder
pool when transcoder pool idle level
supervision is not connected.
FAULT CODE 11
INCORRECT LIMITS SPECIFIED
Limit2(LIM2) always has to be less than

limit1(LIM1).
FAULT CODE 12
TRANSCODER POOL ALREADY CONNECTED TO MEAN HOLD TIME SUPERVISION
It is not possible to connect a transcoder

pool to mean hold time supervision, which
is already connected to mean hold time
supervision.
FAULT CODE 13
TRANSCODER POOL MEAN HOLD TIME SUPERVISION IS NOT CONNECTED
FAULT CODE 14
PROGRAM LOAD IN PROGRESS
Program load is in progress.
FAULT CODE 15
UNSUPPORTED SNT TYPE
The SNT type is not supported.
FAULT CODE 16
MAXIMUM NUMBER OF TRANSCODER RESOURCE INDIVIDUALS IS USED
The transcoder resource individual file

is full. Use size alteration event number
500 to increase the size of the file.
FAULT CODE 17
DSU NOT TIED
The given device software unit is

not tied to the application.
FAULT CODE 18
DSU NAME NOT UNIQUE
The given device software unit name is ambigous.
FAULT CODE 19
NOT EXISTENT DSU
Non existent device software unit.
FAULT CODE 20
FILE SIZE ALTERATION IN PROGRESS
The number of transcoder resources cannot

be changed when file size alteration is
in progress.
FAULT CODE 21
SNT IS NOT BLOCKED
The SNT is not blocked.
FAULT CODE 22
TOO MANY SNTS SPECIFIED
Too many transcoder device processors

specified in the command. The maximum
number is 32.
FAULT CODE 23
SNT NOT FULLY CONNECTED
The SNT is not fully connected.
FAULT CODE 24
SNT SPECIFIED TWICE IN COMMAND
The same SNT has been specified twice

in the command.
FAULT CODE 25
CP-PS NOT AVAILABLE
The CP Program Store is temporarily

not available.
FAULT CODE 26
LOADING NOT ORDERED
Loading is not ordered.
FAULT CODE 27
INCORRECT DSU TYPE FOR THIS SNT OWNER
The DSU must be of the same type

as the SNT owner.
FAULT CODE 28
TRANSCODER POOL CHANGE IN PROGRESS
Modification of transcoder pool

data by a command is in progress.
FAULT CODE 29
LOADING NOT ORDERED FOR SPECIFIED SNT
Loading is not ordered for the

specified SNT.
FAULT CODE 30
TRANSCODER POOL NAME SPECIFIED MORE THAN ONCE
It is not possible to specify a

transcoder pool name more than
once.
FAULT CODE 50
CANNOT MIX DIFFERENT TRANSCODER DEVICE TYPES
Different transcoder device types

have been specified in the same
command.
4.4 RTS Printout Parameter Descriptions
acl Alarm class.

A1 or A2. The alarm class is associated with
limit 2's threshold. The alarm class associated
with limit 1 is the less severe alarm, for
example if lim2 is set to A2 then lim1 must be
set to A3
acquired The number of channels the

pool supports.
anotra Actual number of transcoder

resources.
board Board in stated SNT.

Expressed as TRAB-n, where
n Individual number of a TRAB
TRAB Transcoder Rate
Adaptation Board.
card Fault suspected card in SNT.

Format is of the type "boardname-boardind"
where;
boardname is "TRAB" (TRA board).
The boardname is only printed if 1 TRAB
is connected to the SNT.
boardind is a numeral 0 - 5.
chrate Channel rate, specifies the transmission

rate used by the transcoders in the pool
dev Transcoder multiplexed (MUX) device.

Format is of the type
"devicetype-individual";
RTTRD is the devicetype for full-rate (FR)
transcoder supported by R2 and R3 hardware.
RTTF1D is the devicetype for FR transcoder
RTTF2D is the devicetype for enhanced full-
rate (EFR) or FR transcoder supported by R4

hardware.
RTTH2D is the devicetype for half-rate (HR)
transcoder supported by R4 hardware.
FR/EFR transcoder MUX individuals are valid

if they belong to the following series ...
2,7,12,17,22,27,34,39 ... 10939
HR transcoder MUX individuals are valid if

they belong to the following series ...
2,12,22,34,44,54,66 ... 10934
DLN=dln Downlink negative Line Level

Adjustments
Numeral 0 - 12
DLP=dlp Downlink positive Line level

Adjustments
Numeral 0 - 12
idev
Transcoder demultiplexed (DEMUX) device.
Format is of the type
"devicetype-individual";
RTTRD is the devicetype for FR transcoder
supported by R2 and R3 hardware.
RTTF1D is the devicetype for FR transcoder
RTTF2D is the devicetype for EFR/FR transcoder
RTTH2D is the devicetype for HR transcoder
Transcoder DEMUX individuals are valid if

3,4,5,6,8,9,10,11,13,14 ... 10943
lim1 Limit 1.
Alarm limit for idle transcoder resources
in the transcoder pool, in percent of actual
number of transcoder resources for the
transcoder pool. The less severe limit.
lim2 Limit 2.
Alarm limit for idle transcoder resources
in the transcoder pool, in percent of actual
number of transcoder resources for the
transcoder pool. The more severe limit.
notra Number of transcoder resources which

are in an alarm state.
reason An indication of the type of fault for the

indicated device/board.
Fault slogans for transcoder and rate adaptor
are as follows:
ROUTINE TEST OF TRA FAULT
Routine test of TRAB
connection resulted in
fault.
ERROR ON COMPLETE TRAB
Error on complete TRAB
reported.
TRAB NOT RESPONDING
TRAB not alive, TRAB not
responding.
GS CLOCK SUPERVISION ERROR
GS clock supervision error
reported.
TRA CHANNEL FAULT
TRA channel fault reported.
result CHECKSUM ERROR

Loading not successful.
Program store checksum
error found during load
status check.
CONTROLLING EM FAILURE
Failure in controlling
EM.
DEVICE SEMIPERMANENTLY BUSY

The specified device is
semipermanent busy.
Specify again using the
FORCE parameter.
DEVICE BUSY
The specified device belongs
to a transcoder pool.
Specify again using the
FORCE parameter.
DEVICE NOT CONNECTED

The device is not connected.
DEMUX DEVICE NOT ALLOWED

The command cannot operate
on the specified device.
Give the command again with
the associated MUX device.
DP NOT LOADABLE
The device processor is
not of a loadable type.
DSU BEING REMOVED

Removal of device
software unit in
progress.
EXECUTED
The blocking order
was successful for
this device.
LOADING ABORTED
Loading has been
cancelled by
the operator.
LOADING SUCCESSFUL
The device processor
associated with the SNT
has been loaded
successfully.
NO DP CONTACT
Controlling EM has no
contact with device
processor.
NO PROGRAM LOADED
The information has
not been fetched
successfully. The device
processor associated
with the SNT has not
been program loaded.
PROGRAM ALREADY LOADED

The version of the
device software unit is
already loaded.
SUCCESSFUL
The information has
been fetched
successfully.
TIMEOUT
Time limit for
signalling with
controlling EM
exceeded.
rnotra Required number of transcoder

resources.
snt Switching Network Terminal (SNT) unit.

Format is of the type "bname-sntind"
where bname is the block name or SNT type.
sntind is the SNT individual number.
spv Speech version, a coding standard

specified by the GSM standard.
suid Software Unit Identity of the software product

loaded in the TRABs
Text string 1-32 charcters
suname Software Unit Name

Identifier 3-12 characters
supstatus Supervision status.

There are two possible states:
ON Transcoder pool idle level supervision
is connected.
OFF Transcoder pool idle level supervision
is disconnected.
traidle The number of idle transcoder resources.
trapool The name of the transcoder pool.
tratraf The number of transcoder resources

currently used in traffic
ULN=uln Uplink negative Line Level adjustments
Numeral 0 - 12
ULP=ulp Uplink positive Line Level adjustments
Numeral 0 - 12
required The number of channels the

pool is intended to support.
5 Tranceiver Administration Subsystem, TAS

5.1 Command Descriptions
5.1.1 Definition of MO, commands RXMOI/E/P/C
INITIATE
Managed object TG(Both Logical models)

+ +
|HYB| + +
RXMOI:MO=mo...,COMB=+ +,RSITE=rsite,SWVER=swver |,TRACO=traco | ;
|FLT| + +
+ +
E.g. RXMOI:MO=RXOTG-100,COMB=HYB,RSITE=RSITE2,SWVER=BSG12R2,TRACO=POOL;
Managed object TRXC(Logical model G01, RBS20x)

+ +
|,DEV2=dev2...|
RXMOI:MO=mo,TEI=tei,CTEI=ctei,DEV1=dev1+ +;
|,NOTRAFF |
+ +
Managed object TRXC(Logical model G12, RBS200x)

+ +
|,DCP2=dcp2...| + +
RXMOI:MO=mo,TEI=tei,DCP1=dcp1+ + |, SIG=sig |;
|,NOTRAFF | + +
+ +
E.g. RXMOI:MO=RXOTRX-101-0,TEI=4,DCP1=128,DCP2=129&130;
Managed object CF(Logical model G12, RBS200x)

+ +
RXMOI:MO=mo...,TEI=tei |, SIG=sig | ;
+ +
E.g. RXMOI:MO=RXOCF-100,TEI=62,SIG=MPLEX32;
Managed object IS(Logical model G12, RBS200x)
RXMOI:MO=mo...,TEI=tei;
E.g.RXMOI:MO=RXOIS-100;
Managed object TF(Both Logical models)
RXMOI:MO=mo...,TFMODE=tfmode;
RXMOI:MO=RXOTF-100,TFMODE=SA;
Managed object TX(Both Logical models)
+ +
|DCS| + +
RXMOI:MO=mo...,BAND=+ +,MPWR=mpwr|,ANT=ant|;
|GSM| + +
+ +
Managed object RX(Both Logical models)
+ +
|AB| + +
| | |DCS |+ ++ +
RXMOI:MO=mo...,RXD=+A +,BAND=+ +|,ANTA=anta||,ANTB=antb|;
| | |GSM |+ ++ +
|B | + +
+ +
Managed object TS(Both Logical models)
RXMOI:MO=mo...;
Managed object DP(Logical model G12, RBS200x)
RXMOI:MO=mo..,DEV=dev;
E.g RXMOI:MO=RXODP-1-0,DEV=RXODPI-2;
Managed object CON(Logical model G12, RBS200x)
RXMOI:MO=mo..,DCP=dcp;
E.g RXMOI:MO=RXOCON-1,DCP=64&&87;
CHANGE
Managed Object TG(Logical model G01)
+
|+ + + +
|| + +| | + +|
|| |BB||+ +| |HYB||
RXMOC:MO=mo...+|,FHOP=+ +||,SWVER=swver||,COMB=+ +|
|| |SY||+ +| |FLT||
|| + +| | + +|
|+ + + +
+
+
|
+ ++ +|
|,RSITE=rsite||,EMG=emg|+;
+ ++ +|
|
+
Managed Object TG(Logical model G12)

+
|+ + + +
|| + +| | + +|
|| |BB||+ +| |HYB||
RXMOC:MO=mo...+|,FHOP=+ +||,SWVER=swver||,COMB=+ +|
|| |SY||+ +| |FLT||
|| + +| | + +|
|+ + + +
+
+ + + + + +
|,RSITE=rsite| |,TRACO=traco| |,CONFACT=confact| ;
+ + + + + +
+
|
+ + |
|,HFSEXT=hfsext| ; + ;
+ + |
|
+
Managed Object TRXC(Logical model G01)
+
|+ ++ +
|| + +|| + +|
|| |cell||| |DEFAULT||+ +
RXMOC:MO=mo+|,CELL=+ +||,SWVER=+ +||,TEI=tei|
|| |ALL ||| |swver ||+ +
|| + +|| + +|
|+ ++ +
+
+
+ +|
|+ +||
+ ++ +||,DEV2=dev2...|||
|,CTEI=ctei||,DEV1=dev1||+ +|+;
+ ++ +||,NOTRAFF |||
|+ +||
+ +|
+
Managed Object TRXC(Logical model G12)
+
|+ ++ +
|| + +|| + +|
|| |cell||| |DEFAULT||+ +
RXMOC:MO=mo+|,CELL=+ +||,SWVER=+ +||,TEI=tei|
|| |ALL ||| |swver ||+ +
|| + +|| + +|
|+ ++ +
+
+
+ +|
|+ +||
+ +||,DCP2=dcp2...|||
|,DCP1=dcp1||+ +|+;
+ +||,NOTRAFF |||
|+ +||
+ +|
+
Managed Object CF(Logical model G12)
+ +
| + + |
| | | |
| | | |
| | |DEFAULT|| + + + + |
RXMOC:MO=mo...+ |,SWVER=+ +| |,SIG=sig| |,SIG=sig| + ;
| | |swver || + + + + |
| | + +| |
| | | |
| + + |
+ +
Managed Object TF(Both logical models)
RXMOC:MO=mo...,TFMODE=tfmode;
Managed Object TX(Both logical models)
+
|+ + + +
|| + +| | + +|
|| |cell||+ +| |DCS||
RXMOC:MO=mo...+|,CELL=+ +||,ANT=ant||,BAND=+ +|
|| |ALL ||+ +| |GSM||
|| + +| | + +|
|+ + + +
+
+
|
+ +|
|,MPWR=mpwr|+;
+ +|
|
+
Managed Object RX(Both logical models)
+
|+ +
|| + +|
|| |AB||
|| | ||+ ++ +
RXMOC:MO=mo...+|,RXD=+A +||,ANTA=anta||,ANTB=antb|
|| | ||+ ++ +
|| |B ||
|| + +|
|+ +
+
+
+ +|
| + +||
| |DCS|||
|,BAND=+ +|+;
| |GSM|||
| + +||
+ +|
+
RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT, PRINT
+ +
|MO=mo... |
RXMOP:+ +;
|MOTY=moty|
+ +
RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT, END
RXMOE:MO=mo...;
5.1.2 Abis path handling , commands RXAPI/RXAPE/RXAPP
RADIO X-CEIVER ADMINISTRATION MANAGED ABIS PATH, INITIATE
RXAPI:MO=mo,DEV=dev...,DCP=dcp...;
RADIO X-CEIVER ADMINISTRATION MANAGED ABIS PATH, END
+ +
| dcp...|
RXAPE:MO=mo,DCP= + + ;
| ALL |
+ +
RADIO X-CEIVER ADMINISTRATION MANAGED ABIS PATH, PRINT
+ +
|MOTY=moty|
RXAPP:+ +;
|MO=mo... |
+ +
5.1.3 TG To Channel Group ,commands RXTCI/RXTCE/RXTCP
RADIO X-CEIVER ADMINISTRATION TG TO CHANNEL GROUP, INITIATE
RXTCI:MO=mo,CELL=cell,CHGR=chgr...;
RADIO X-CEIVER ADMINISTRATION TG TO CHANNEL GROUP, END
RXTCE:MO=mo,CELL=cell,CHGR=chgr...;
RADIO X-CEIVER ADMINISTRATION TG TO CHANNEL GROUP, END
+ +
| + +|
|MOTY=moty|,CELL=cell||
| + +|
RXTCP:+ +;
| |
|MO=mo... |
| |
+ +
5.1.4 MO in service, commands RXESI/RXESE,
RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT IN SERVICE, INITIATE
RXESI:MO=mo...;
RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT IN SERVICE, END
RXESE:MO=mo...;
5.1.5 commands RXMSC, MO in service data

RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT IN SERVICE DATA CHANGE
Managed Object TG
+ +
| + + + + + + |
RXMSC:MO=mo...| |,SWVER=swver | |,CONFACT=confact | |, HFSEXT=hfsext | |;
| + + + + + + |
+ +
Managed Object TRXC

+ +
|DEFAULT|
RXMSC:MO=mo...,SWVER=+ +;
|swver |
+ +
Managed Objects CF
+ +
|DEFAULT|
RXMSC:MO=mo...,SWVER=+ +;
|swver |
+ +
Managed Object TF
RXMSC:MO=mo...,TFMODE=tfmode;
Managed Object TX
RXMSC:MO=mo...,ANT=ant;
Managed Object RX
+ ++ +
RXMSC:MO=mo...|,ANTA=anta||,ANTB=antb|;
+ ++ +
5.1.6 Status of MO, commands RXMSP
RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT STATUS, PRINT

+ +
|MOTY=moty|
RXMSP:+ +;
|MO=mo... |
+ +
5.1.7 Capabilities of MO, RXCAP
RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT CAPABILITIES, PRINT

+ +
|MOTY=moty|
RXCAP:+ +;
|MO=mo... |
+ +
E.g.RXCAP:MO= RXETRX-1-2;
5.1.8 commands RXBLI/RXBLE, Blocking of MO
RADIO X-CEIVER ADMINISTRATION MANUAL BLOCKING OF MANAGED OBJECT, INITIATE

+ +
RXBLI:MO=mo...|,FORCE|;
+ +
RADIO X-CEIVER ADMINISTRATION MANUAL BLOCKING OF MANAGED OBJECT, END
RXBLE:MO=mo...;
5.1.9 commands RXPLI/RXPLE, FC & PL of MO

RADIO X-CEIVER ADMINISTRATION FC. and PL. OF MANAGED OBJECT, INITIATE
+ +
|MOTY=moty|+ ++ +
RXPLI: + +|,UC||,IO=io|;
|MO=mo... |+ ++ +
+ +
RADIO X-CEIVER ADMINISTRATION FC. and PL. OF MANAGED OBJECT, END
+ +
|MOTY=moty|
RXPLE: + +;
|MO=mo... |
+ +
5.1.10 Test of MO, commands RXTEI/RXTEE,

RADIO X-CEIVER ADMINISTRATION TEST OF MANAGED OBJECT, INITIATE
RXTEI:MO=mo...;
RADIO X-CEIVER ADMINISTRATION TEST OF MANAGED OBJECT, END
RXTEE:MO=mo...;
5.1.11 BSC-BTS Loop Test, commands RXLTI

RADIO X-CEIVER ADMINISTRATION BSC-BTS LOOP TEST, INITIATE
RXLTI:MO=mo...;
5.1.12 MO congiguration data print, commands RXCDP,

RADIO X-CEIVER ADMINISTRATION MO CONFIGURATION DATA, PRINT
RXCDP:MO=mo...;
5.1.13 MO Error Log Print , commands RXELP/RXELR

RADIO X-CEIVER ADMINISTRATION ERROR LOG, PRINT
+ ++ +
|MOTY=moty|| |
RXELP:+ +|,IO2=io2|;
|MO=mo... || |
+ ++ +
RADIO X-CEIVER ADMINISTRATION ERROR LOG, PRINT

+ +
|MOTY=moty|
RXELR:+ +;
|MO=mo... |
+ +
5.1.14 MO Hopping Data Print, commands RXHDP

RADIO X-CEIVER ADMINISTRATION MO HOPPING DATA, PRINT
RXHDP:MO=mo...;
5.1.15 MO Hopping Frequency set extension measuring program, commands

RXHMI/RXHMP/RXHEI
RADIO X-CEIVER ADMINISTRATION MO HOPPING FREQUENCY SET
EXTENSION MEASURING PROGRAM , INIT
+ +
RAHPI: MP=mp +, IO=io+ ;
+ +

EXTENSION MEASURING PROGRAM , PRINT
RXHMP;

EXTENSION, INITIATE
RXHEI;
5.1.16 MO Device Information Print, commands RXMDP,

RADIO X-CEIVER ADMINISTRATION MO DEVICE INFORMATION, PRINT
+ +
|MOTY=moty|
RXMDP:+ +;
|MO=mo... |
+ +
5.1.17 MO Fault Information Print, commands RXMFP,

RADIO X-CEIVER ADMINISTRATION MO FAULT INFORMATION, PRINT
+ +
| + + |
|MOTY=moty|,FAULTY| |
| + + |
RXMFP:+ +;
| + ++ +|
|MO=mo...|,FAULTY||,SUBORD||
| + ++ +|
+ +
5.1.18 Alarm Coordination Data , RXALC/RXALP/RXASP

RADIO X-CEIVER ADMINISTRATION ALARM COORDINATION DATA, CHANGE
+
| + +
| | + +|
+ + | | |almask...||
| MOTY=moty | |+ +| | ||
RXALC:+ + +|,TGCOORD=tgcoord||,ALMASK=+CLEAR +|
| MO=mo... | |+ +| | ||
+ + | | |ALL ||
| | + +|
| + +
+
+
|
|
|
+ +|
|,ALCOTIM=alcotim|+;
+ +|
|
|
|
+
RADIO X-CEIVER ADMINISTRATION ALARM COORDINATION DATA, PRINT
+ +
|MOTY=moty|
RXALP:+ +;
|MO=mo... |
+ +
RADIO X-CEIVER ADMINISTRATION ALARM SITUATIONS, PRINT
+ +
|MOTY=moty|
RXASP:+ +;
|MO=mo... |
+ +
5.2 TAS command parameter information

5.2.1.1 ALCOTIM Alarm Coordination Timer
ALCOTIM=alcotim Alarm Coordination Timer

The filter time allowed for the fault
situation to settle before alarm
coordination analysis begins.
Range is 90 - 300 seconds.
5.2.1.2 ALMASK Alarm Situation
ALMASK=almask Alarm situation.

Indication of the type of alarm situation
to be masked. Following alarm situations are
allowed:
TGC TGC FAULT
PERM PERMANENT FAULT
LOM LOCAL MODE
LMT LMT INTERVENTION
LOOP LOOP TEST FAIL
CLS1 CLASS 1 FAULT
OML OML FAULT
ABIS ABIS PATH FAULT
SYNC TS SYNCHRONISATION FAULT
CLS2 CLASS 2 FAULT
CLEAR All alarm situations are valid.
ALL All alarm situations are masked.
5.2.1.3 ANT Antenna Designation.
:xmp ANT=ant Antenna Designation. Name of antenna connected to transmitter. This

parameter is represented by a string of 1-7 characters.
5.2.1.4 ANTA Antenna A Designation.
ANTA=anta Antenna A Designation.

Name of antenna A connected to receiver.
This parameter is represented by a string
of 1-7 characters.
5.2.1.5 ANTB Antenna B Designation.
ANTB=antb Antenna B Designation.

Name of antenna B connected to receiver.
of 1-7 characters.
5.2.1.6 BAND Frequency Band.
BAND=band Frequency Band.

Frequency band supported by transmitter/
receiver. GSM, DCS or PCS.
GSM GSM frequency band supported.

DCS DCS frequency band supported.
PCS PCS frequency band supported.
5.2.1.7 CELL Cell Designation.
CELL=cell Cell Designation or ALL.

The cell to which the TRXC or TX managed
object is dedicated to. This parameter is
represented by a string of 1 - 7 characters.
ALL The TRXC or the TX is not

dedicated to a particular cell.
5.2.1.8 CHGR Channel Group.
CHGR Channel Group.

A channel group is a subset of the frequencies
used in a cell
Numeral 0-15.
5.2.1.9 COMB Combiner.
COMB=comb Combiner.
Combiner type used in the TG.
FLT or HYB.
FLT Filter combiner.

HYB Hybrid combiner.
5.2.1.10 CONFACT Concentration Factor.
CONFACT=confact Maximum allowed LAPD concentration factor in

the TG.
Specifies the maximum number of TRXCs that
can be LAPD concentrated on the same trans-
mission device.
Numeral 1 - 16.
5.2.1.11 CTEI TGC Application Terminal Endpoint Identifier.
CTEI=ctei TGC Application Terminal Endpoint

Identifier.
LAPD element used for L2 addressing to
TGC application in a TRXC.
Numeral 58 - 63.
5.2.1.12 DCP Digital Connection Point
DCP=dcp Digital connection point number used as

termination point in the BTS for the
Abis path.
Numeral 0 - 255.
5.2.1.13 DCP1 Digital Connection Point One.
DCP1=dcp1 Digital connection point number used for the

signalling path to the TRXC.
Numeral 0 - 255.
5.2.1.14 DCP2 Digital Connection Point Two.
DCP2=dcp2 Digital connection point number used for the

speech and data connections to the TRXC.
Two dcp2s should be given. The first dcp2
will be associated with TSs 0 to 3 and the
second dcp2 will be associated with TSs 4
to 7.
Numeral 0 - 255.
5.2.1.15 DEV Device.
DEV=dev [Mandatory description of device.]

Transmission device used for the Abis
path.
See application information for block
TRAN for the format and value range of this
parameter.
Logical device used to connect the managed

object DP to Digital Path supervision
functions.
See application information for block TRAN
for the format and value range of this
parameter.
Device used for the specified managed object

type. See application information for block
TRAN for the format and value range of this
parameter.
Transcoder MUX device to be blocked/deblocked.
Format is of the type "devicetype-individual",

where devicetype = RXCTRD and
Transcoder MUX individuals are valid if they belong
to the following series ...
2,7,12,17,22,27,34,39 ... 5467
5.2.1.16 DEV1 Device One.
DEV1=dev1 [Mandatory description of device.]
Transmission device used for the signalling

path to the TRXC.
See application information for block TRAN
for the format and value range of this
parameter.
5.2.1.17 DEV2 Device Two.
DEV2=dev2 [Mandatory description of device.]

Transmission devices used for speech and
data connections to the TRXC.
Two devices should be given. The first
device will be associated with TSs 0 to 3
and the second device will be associated with
TSs 4 to 7. See application information for
block TRAN for the format and value range of
this parameter.
5.2.1.18 DLN Downlink Negative Line Level Adjustments.
DLN=dln Downlink Negative Line Level Adjustments.

Parameter is given in dB.
Numeral 0 - 12.
Default value: refer to the application
information for RXCTRD.
5.2.1.19 DLP Downlink Positive Line Level Adjustments.
DLP=dlp Downlink Positive Line Level Adjustments.

Parameter is given in dB.
Numeral 0 - 12.
Default value: refer to the application
information for RXCTRD.
5.2.1.20 EMG Extension Module Group.
EMG=emg Extension Module Group.

Identifies the Transmission Remote
Interface used for the TG. This parameter
is represented by a string of 1-15
characters.
5.2.1.21 FAULTY Faulty.
FAULTY Faulty.
This parameter specifies that only
information on faulty managed object
instances is to be printed.
5.2.1.22 FHOP Frequency Hopping.
FHOP=fhop Frequency Hopping.

The frequency hopping to be performed in
the TG. BB or SY.
BB Baseband hopping.
SY Synthesiser hopping.
5.2.1.23 FORCE Forced Blocking Indication.
FORCE Forced Blocking Indication.
5.2.1.24 HFSEXT Hopping Frequency Set Extension
HFSEXT=hfsext Hopping Frequency Set Extension.

Indicates whether periodic HFS extension
is allowed for the TG. ON or OFF.
ON Periodic HFS extension allowed.

OFF Periodic HFS extension prohibited.
5.2.1.25 IO IO Device.
IO=io IO device identifying the alphanumeric

device to which the result printout is
directed. This is required only if the
result printout is to be diverted to a
different IO from the command IO.
5.2.1.26 IO2 IO Device.
IO2=io2 IO Device.
Identifier of the alphanumeric device to
which the printout is directed. This is
only required if the printout is to be
directed to a different IO from
the one on which the printout is ordered.
Expressed as dt-n where
dt IO Device Type.
Identifier 1-7 characters.
n IO Device Number.
Numeral 0-255.
5.2.1.27 MP Measuring Program
MP=mp Identity of measuring program (MP).

Numeral 0 - 255.
5.2.1.28 MO Managed Object Instance.
MO=mo Managed Object Instance.

See the application information for block
RXCTA for the format and value range of
this parameter.
[If parameter is not allowed for all managed
object classes, mandatory clarification of
which managed object classes are allowed.]
5.2.1.29 MOTY Managed Object Type.
MOTY=moty Managed Object Type.

RXCTA for the format of this parameter.
[If parameter is not allowed for all managed
object types, mandatory clarification of which

managed object classes are allowed.]
5.2.1.30 MPWR Maximum Transmitter Power.
MPWR=mpwr Maximum Transmitter Power.

The parameter is expressed in dBm.
Numeral 0 - 63.
5.2.1.31 NOTRAFF No Traffic.
NOTRAFF No Traffic.
Indicates that the TRXC is not used for
speech and data.
5.2.1.32 RSITE Radio Site.
RSITE=rsite Radio Site.

Identity of the radio site where the TG is
located. This parameter is represented by
a string of 3-15 characters.
5.2.1.33 RXD Receiver Diversity.
RXD=rxd Receiver diversity.

Combination of receiver antennae to be used.
A, B or AB.
A Antenna A used only.
B Antenna B used only.
AB Receiver diversity employed using
antennae A and B.
5.2.1.34 SIG Signalling type
UNCONC, CONC, MPLEX16 or MPLEX32
UNCONC Unconcentrated
CONC LAPD concentrated
MPLEX16 16K Multiplex
MPLEX32 32K Multiplex
5.2.1.35 SUBORD Subordinate.
SUBORD Subordinate.
This parameter specifies that fault
information is also to be given on managed
object instances which are subordinate to
to the specified managed object instance(s).
5.2.1.36 SWVER Software Version.
SWVER=swver Software Version.

Name of the disk file holding the BTS soft-
ware version. This is the default software
version to be loaded into the TRXCs and CF
belonging to a TG.
of 1 - 12 characters.
SWVER=swver Software Version or DEFAULT.

Name of the disk file holding the BTS soft-
ware version. If this parameter is given for
a managed object of managed object class TG,
this is the default software version to be
loaded in the TRXCs and CF belonging to a
TG. If this parameter is given for a managed
object of managed object class TRXC, this is
a specific software version to be loaded in
the specific TRXC. If this parameter is
given for a managed object of managed object
class CF, this is a specific software
version to be loaded in the specific CF.
This parameter is represented by a string of
1 - 12 characters.
DEFAULT Given for the parameter SWVER for

a managed object of managed object
class TRXC or CF, when it is
intended to change the software
version for the TRXC and CF to
the default software version
designated for the superior TG
managed object.
5.2.1.37 TEI Terminal Endpoint Identifier.
TEI=tei Terminal Endpoint Identifier.

LAPD element used for L2 addressing to a
TRXC and CF.
Numeral 0 - 57 for G01.
Numeral 0 - 63 for G12.
5.2.1.38 TFMODE Timing Function Synchronization Mode.
TFMODE=tfmode Timing Function Synchronization Mode.

Mode of the timing function in the TG.
M, S or SA.
M Master, synchronized towards PCM
network and distributing
synchronization to other TFs.
S Slave, synchronized towards other TFs.
SA Standalone, synchronized towards PCM
network.
5.2.1.39 TGCOORD Coordination on TG level
TGCOORD=tgcoord Coordination on TG level.

Indication of whether alarm coordination
is on TG level or MO level.
ON Alarm coordination on TG level

OFF Alarm coordination on MO level
5.2.1.40 TRACO Transcoder connection type
SEMI Semi permanent connected transcoders.
POOL Transoder in POOL

The TRANSCODER will be allocated at
call set-up
5.2.1.41 UC Unconditional
UC Perform unconditional software loading of

managed objects.
5.3 TAS Printout Parameter Descriptions

5.3.1 Printout parameter, alphabetical order
5.3.1.1 ALCOTIM Alarm Coordination Timer
alcotim Alarm Coordination Timer

The filter time allowed for the
fault situation to settle before
alarm coordination analysis begins.
Range is 90 - 300 secs.
5.3.1.2 ALMASK Alarm Mask
almask Alarm situation being masked.

Indication of the type of fault situation
to be masked. Following fault types are
allowed:
TGC TGC FAULT
PERM PERMANENT FAULT
LOM LOCAL MODE
LMT LMT INTERVENTION
LOOP LOOP TEST FAIL
CLS1 CLASS 1 FAULT
OML OML FAULT
ABIS ABIS PATH FAULT
SYNC TS SYNCHRONISATION FAULT
CLS2 CLASS 2 FAULT
ALL All alarm situations are masked.
5.3.1.3 alarm_situation Alarm Situation.
alarm_situation Alarm Situation.

The alarm situation is an indication of the
type of fault in the indicated managed
object. The following alarm situations
are possible:
TGC FAULT
No active TGC application exists
in the transceiver group.
PERMANENT FAULT
A managed object is classified as
being permanently faulty when

fault situations have occurred,
and have been cleared, a certain
number of times within a certain
period of time.
Manual intervention is required to
bring such equipment back into
operation.
LMT INTERVENTION
Local maintenance activities being
performed in the BTS.
CLASS 1 FAULT
A fault exists in a piece of BTS
equipment that leads to that
equipment not being able to carry
out its operational function.
OML FAULT
A fault exists in the
communications link between the
BSC and the BTS.
ABIS PATH UNAVAILABLE

No transmission device exists
between the BSC and the BTS.
TS SYNC FAULT
Synchronization lost on uplink or
downlink TRAU channels.
CLASS 2 FAULT
A fault in BTS equipment that does
not directly interfere with its
operational function.
LOCAL MODE/OML FAULT

The BTS equipment is in Local Mode
or the BTS equipment has changed
from Local to Remote Mode and a
fault exists in the communication
link between the BSC and the BTS.
Communication between the BSC and
the BTS is not possible.
:xmp LOOP TEST FAILED Test of the traffic carrying capabilities of the TS has failed.
5.3.1.4 ant Antenna Designation.
:xmp ant Antenna Designation. Name of antenna connected to transmitter. This parameter is
represented by a string of 1-7 characters.
5.3.1.5 anta Antenna A Designation.
anta Antenna A Designation.

Name of antenna A connected to receiver.
of 1-7 characters.
5.3.1.6 ANTB Antenna B Designation.
antb Antenna B Designation.

Name of antenna B connected to receiver.
of 1-7 characters.
5.3.1.7 apstate Abis Path State.
apstate State of the Abis path within the

specified TG.
SPEECH/DATA The Abis path is used

for speech/data.
CF SIGNALLING The Abis path is used

for CF signalling.
TRXC SIGNALLING
The Abis path is used
for TRXC signalling.
CF AND TRXC SIGNALLING

The Abis path is used
for TRXC and CF signalling.
IDLE The Abis path is not used.
5.3.1.8 arfcn Absolute Radio Frequency Channel Number.
arfcn Absolute Radio Frequency Channel Number.

Represents the frequency to which a receiver
or transmitter is tuned, or the frequency
associated with a timeslot handler. The
parameter is a an ARFCN value in the
range 0 to 1023, or HOP if frequency hopping.
For a transmitter, HOP is only printed when
synthesized frequency hopping.
5.3.1.9 band Frequency Band.
band Frequency Band.

Frequency band supported by transmitter/
receiver. GSM, DCS or PCS.
GSM GSM frequency band supported.

DCS DCS frequency band supported.
PCS PCS frequency band supported.
5.3.1.10 bla Blocking Origon Action Not Completed.
bla Blocking Origon Action Not Completed.

Blocking origin of blocking due to action not
completed.
This variable is printed as a hexadecimal
number representing a sixteen bit map.
Value range H'0000 - H'FFFF.
The bit map may be read as follows:
bits 0 to 3:
bit 3 2 1 0
+-----+-----+-----+-----+
| BNP | BNL | BNR | BNU |
+-----+-----+-----+-----+
BNU Object needs reset and unconditional

load or reset and loading are in
progress
BNR Object needs reset and load check
or the reset and loading are in progress
BNL Object needs load check or loading
in progress
BNP Object needs polling or polling in
progress
bits 4 to 7:
bit 7 6 5 4
+-----+-----+-----+-----+
| BNS | BND | BNI | BNT |
+-----+-----+-----+-----+
BNT Object needs testing or testing

in progress
BNI Object needs intermittent test or
intermittent test in progress
BND Object needs updating of MO data
BNS Object needs start
bits 8 to 9:
bit 9 8
+-----+-----+
| BNO | BNM |
+-----+-----+
BNM Object needs to be manually

deblocked (BTS initiated)
BNO Object needs loop test or loop test
in progress
Bits 10 to 15 are spare.
This variable is not valid for managed

object instances of class TG.
5.3.1.11 blo Blocking Origin of Automatic Blocking.
blo Blocking Origin of Automatic Blocking.

bits 0 to 3:
bit 3 2 1 0
+-----+-----+-----+-----+
| TG | AS | AT | AP |
+-----+-----+-----+-----+
AP Object blocked from own supervision

permanently
AT Object blocked from own supervision
temporarily
AS Object blocked due to fault suspected
TG Object blocked from TG
bits 4 to 7:
bit 7 6 5 4
+-----+-----+-----+-----+
| X | OML | TGC | TRXC|
+-----+-----+-----+-----+
TRXC Object blocked from TRXC

TGC Object blocked from TGC
OML Object blocked from OML
X Spare.
bits 8 to 11:
bit 11 10 9 8
+-----+-----+-----+-----+
| LOOP| LOM | CF | LMT |
+-----+-----+-----+-----+
LMT Object blocked due to local

maintenance activities
CF Object blocked from CF
LOM Object blocked due to local mode
LOOP Object blocked due to loop test
failure
bits 12 to 15 are spare.
This variable is not valid for

managed object instances of class
TG.
5.3.1.12 blstate Blocking State of a Managed Object.
blstate Blocking State of a Managed Object.

The blocking state of a managed object
is printed as one of the values listed
in a priority order below. If more than
one blocking is active then
only the highest priority is printed.
BLL Load in progress. The Managed
Object may be blocked or in
operation.
BLT Blocked due to testing.

MBL Manually blocked.
BLO Automatically blocked.
BLA Blocked due to activity needed.
5.3.1.13 bpc BPC Individual.
bpc BPC Individual.

The individual printed is the BPC individual,
a numeric value in the range 0 to 4095.
5.3.1.14 bspwr Base Station Nominal Power.
bspwr Base Station Nominal Power.

Numeric value in the range 0 to 63, specified
in dBm.
5.3.1.15 bts BTS State.
bts BTS State.

The BTS state is the last known state of the
managed object in the BTS.
The possible BTS states are:
RES The managed object is in state RESET.
STA The managed object is in state STARTED.
DIS The managed object is in state
DISABLED.
ENA The managed object is in state ENABLED.

of three characters.
5.3.1.16 btshwrev BTS Hardware Revision.
btshwrev BTS Hardware Revision.

The BTS hardware revision gives the hardware
revision of the managed object.
There may be a number of hardware revisions
associated with each managed object.
This parameter consists of a string 31
characters long.
5.3.1.17 btsswver BTS Software Version.
btsswver BTS Software Version.
The BTS software version describes the

software package in the BTS.
This is a string fifteen characters long
of the form type-gen-rev-var.
type BTS Manufacturer.

Identifies the BTS manufacturer.
This field is three characters long.
gen BTS Generation.

A term to seperate BTSs from the same
manufacturer, which are conceptually
different over the Abis interface.
rev BTS Revision.

A term used to seperate BTSs from the
same manufacturer and within a genera-
tion which supports different sets of
functions and procedures over the
Abis interface.
var BTS Variant.

A term used to seperate different BTS
software packages of the same
manufacturer, generation and revision.
5.3.1.18 cell Cell Designation.
cell Cell Designation.

The cell to which the TRXC or TX managed
object is dedicated to.
ALL The TRXC or the TX is not

dedicated to a particular cell
5.3.1.19 chgr Channel Group.
chgr Channel Group.

A channel group is a subset of the frequencies
used in a cell
Numeral 0-15.
5.3.1.20 chcomb Channel Combination.
chcomb Channel Combination.

One of:
BCCH BCCH + CCCH

SDCCH8 SDCCH/8 * 8
SDCCH4 BCCH + CCCH + SDCCH/4 * 4
CBCH8 SDCCH/8 * 7 + CBCH
CBCH4 BCCH + CCCH + SDCCH/4 * 3 + CBCH
TCH TCH/F
5.3.1.21 class class
class Class
The class of the most severe alarm in the
external alarm list. Class may be 1 or 2,
1 being the most severe.
5.3.1.22 c0f Carrier Zero Filling.
c0f Carrier Zero Filling.

YES Carrier zero filling is turned on.
NO Carrier zero filling is turned off.
5.3.1.23 comb Combiner.
comb Combiner.
Combiner type used in the TG.
FLT or HYB.
FLT Filter combiner

HYB Hybrid combiner
5.3.1.24 concnt Counter for the Number of Connection Setup Attempts.
concnt Counter for the Number of Connection Setup

Attempts.
This parameter is only valid for managed
object instances of type TS.
The value range is between 0 and 65535.
5.3.1.25 conerrcnt Counter for the Number of Abnormally Terminated Connections.
conerrcnt Counter for the Number of Abnormally

Terminated
Connections.
This parameter is only valid for managed
object instances of type TS.
5.3.1.26 conf BTS Configuration State.
conf BTS configuration state.

Each logical unit has a configuration state.
UNCONF The logical unit is not configured.
CONF The logical unit is configured.
ENA The logical unit is enabled.
This parameter is represented by a string of

six characters.
5.3.1.27 Configuration Data may be Inconsistent
CONFIGURATION DATA MAY BE INCONSISTENT

An access lock could not be taken on the TG,
therefore configuration may be in progress.
The data printed may be inconsistent.
5.3.1.28 confact Concentration Factor.
confact Maximum allowed LAPD concentration factor

in the TG.
5.3.1.29 crc Cyclic Redundancy Check.
crc Cyclic Redundancy Check.

YES Cyclic Redundancy Check is performed.
NO Cycic Redundancy Check is not performed.
5.3.1.30 ctei TGC Application Terminal Endpoint Identifier.
ctei TGC Application Terminal Endpoint Identifier.
LAPD element used for L2 addressing to TGC

application in a TRXC.
5.3.1.31 date Date.
date Date.
The date the error was received, in the format
yy-mm-dd, where yy represents the year, mm the
month and dd the date that the error was
entered into the log.
This is a string eight characters long.
5.3.1.32 dcp Digital Connection Point.
dcp Digital connection point number used as

termination point in the BTS for the
Abis path.
5.3.1.33 dcp1 Digital Connection Point.
dcp1 Digital connection point number used for the

signalling path to the TRXC.
5.3.1.34 dcp2 Digital Connection Point.
dcp2 Digital connection point number used for the

speech and data connections to the TRXC.
Two dcp2s should be given. The first dcp2
will be associated with TSs 0 to 3 and the
second dcp2 will be associated with TSs 4
to 7.
5.3.1.35 dev Device.
dev Device
[Mandatory description of device.]
Logical device used to connect the managed
object DP to Digital Path supervision
functions.
Transmission device used for the Abis

path.
Transcoder device.
Format is of the type "devicetype-individual",

Transcoder MUX/DEMUX individuals are valid if
2,3,4,5,6,7,8 ... 5467
5.3.1.36 dev1 Device.
dev1 [Mandatory description of device.]

Transmission device used for the signalling
path to the TRXC.
5.3.1.37 dev2 Device.
dev2 [Mandatory description of device.]

Transmission devices used for speech and
data connections to the TRXC.
Two devices should be given. The first
device will be associated with TSs 0 to 3
and the second device will be associated with
TSs 4 to 7.
5.3.1.38 devs Device.
devs Transcoder/Rate Adaptor device or

Transceiver Handler device.
5.3.1.39 devt Device.
devt Transmission device.
5.3.1.40 emg Extension Module Group.
emg Extension Module Group.

Identifies the Transmission Remote Interface
used for the TG. This parameter is represented
by a string of 1-15 characters.
5.3.1.41 EOT DURING PRINTOUT
EOT DURING PRINTOUT Operator Initiated Inhibition.
5.3.1.42 extfcode1b External Fault Code, Class 1B.
extfcode1b External Fault Code, Class 1B.

A fault external to the TG that affects
managed object functionality.
This is a number between 0 and 15
representing a fault code.
See operational instruction BTS Fault
Analysis for references to BTS Operation
and Maintenance Manuals. These manuals
contain information on how to decode the
faults.
5.3.1.43 extfcode2b External Fault Code, Class 2B.
extfcode2b External Fault Code, Class 2B.

A fault external to the TG that does not
affect managed object functionality.
contain information on how
to decode the faults.
5.3.1.44 ext1bmap External Fault Map Class 1B.
ext1bmap External Fault Map Class 1B.

A map which identifies faults external to
the TG that do affect Managed Object
functionality. The map is printed as a
hexadecimal number four characters long
where each digit of the number
represents four bits of the binary fault map,
for example, 0011 means bits 0 and 4 are set.
See operational instruction BTS FAULT
ANALYSIS for references to BTS Operation
and Maintenance Manuals. These operational
manuals contain information on how to
decode the fault map.
5.3.1.45 ext2bmap External Fault Map Class 2B.
ext2bmap External Fault Map Class 2B.

A map which identifies faults external to
the TG that do not affect Managed Object
functionality.
The map is printed as a hexadecimal number
four characters long where each digit of
the number represents four bits of the
binary fault map, for example, 1000 means
bit 15 is set.
See operational instruction BTS FAULT
ANALYSIS for references to BTS Operation
decode the fault map.
5.3.1.46 FAILED MO'S EXIST
FAILED MO'S EXIST Appears when subordinate managed

objects have failed to load and
none could be printed.
5.3.1.47 FAULT INTERRUPT
FAULT INTERRUPT Fault interruption during printout.
5.3.1.48 fcode1a Internal Fault Code, Class 1A.
fcode1a Internal Fault Code, Class 1A.

A fault internal to the TG that affects
It is also used for internal fault codes
class 1 for some BTS versions.
The fault is 'A' meaning that faulty HW is part
of the signalling managed object.
See operational instruction BTS Fault Analysis
for references to BTS Operation and
Maintenance Manuals.
These manuals contain information on how to
decode the faults.
5.3.1.49 fcode1b Internal Fault Code, Class 1B.
fcode1b Internal Fault Code, Class 1B.

A fault internal to the TG that affects managed
object functionality.
The fault is 'B' meaning that the origin of
the fault is external to the signalling
managed object.
for references to BTS Operation and Maintenance
Manuals. These manuals contain information on
how to decode the faults.
5.3.1.50 fcode2a Internal Fault Code, Class 2A.
fcode2a Internal Fault Code, Class 2A.

A fault internal to the TG that does not affect
It is also used for internal fault codes
The fault is 'A' meaning that faulty HW is
part of the signalling managed object.
This is a number between 0 and 47 representing
a fault code.
Manuals.
These manuals contain information on how to
decode the faults.
5.3.1.51 fhop Frequency Hopping.
fhop Frequency Hopping.

The frequency hopping to be performed in
the TG. BB or SY.
BB Baseband hopping.
SY Synthesiser hopping.
5.3.1.52 hsn Hopping Sequence Number.
hsn Hopping Sequence Number

Numeric value in the range 0 to 63.
5.3.1.53 icm Idle Channel Measurement.
icm Idle Channel Measurement.
Indicates value of Idle Channel Measurement

(ON/OFF)
5.3.1.54 idev Device Individual
idev Format is of the type "devicetype-individual",

Transcoder DEMUX individuals are valid if they
belong to the following series ...
3,4,5,6,8,9,10,11,13,14 ... 5412.5413 ...
5.3.1.55 INSUFFICIENT TRX EQUIPMENT
INSUFFICIENT TRX EQUIPMENT

Insufficient managed objects of class
RX or TS, with suitable capabilities
are available within this TG to meet
the cell requirement.
5.3.1.56 INSUFFICIENT TX EQUIPMENT
INSUFFICIENT TX EQUIPMENT
Insufficient managed objects of class TX,
with suitable capabilities are available
within this TG to meet the cell
requirement at the time of the configu-
ration. If more TX equipment has become
available since configurtion was started,
the cell must be halted and activated to
include these TXs in the configuration.
5.3.1.57 intercnt Counter for the Number of Intermittent Faults.
intercnt Counter for the Number of Intermittent Faults.

This counter measures the number of intermit-
tent faults on a managed object instance,
except in the case of a TG managed object
instance where the counter measures the
number of intermittent faults that occurred
in the subordinate managed object instances.
5.3.1.58 io IO Device.
io IO device to which the result printout

is directed.
5.3.1.59 loadresult Loadresult
loadresult Result of attempt to load the managed

object. This is not printed if the
command was aborted before loading
took place.
LOADED
The managed object instance
has been loaded.
MO NOT LOADABLE FROM THE BSC

The managed object is loaded
from another loadable managed
object within the BTS.
ABORTED BY OTHER FUNCTION

Software loading is aborted due
to another function with higher

priority wanting access to the
processed managed object instance.
DISKFILE NOT FOUND

Operational Software required for
the managed object is not found
in IOG.
DISKFILE ACCESS ERROR

Unable to access the file in
IOG.
DISKFILE FORMAT ERROR

Unable to load the operational
software required for the managed
object instance due to file
incorrectly formatted.
INSUFFICIENT MEMORY
object instance due to insufficient
BSC memory.
BUFFER CONGESTION
Allocation of dynamic buffer
failed.
TOO HIGH CONCENTRATION ON TRH

object instance due to inability
to set up a communication link
because of processor capacity
limitations in the transceiver
handler. Too many TRXCs are
specified on the same transmission
device.
NO TRH AVAILABLE
software because there is no
available tranceiver handler.
LOADING FAILED
The communication between the
BSC and the managed object in
the BTS has failed during the
software loading process.
5.3.1.60 lmo Blocking Origin of Logical Managed Object.
lmo Blocking Origin of Logical Managed Object.

This variable is only printed for managed
object instances of class TS and TF.

Logical Managed Object LTF.
Bits 4 to 7:
bit 7 6 5 4
+-----+-----+-----+-----+
| X | ENA | CRN | X |
+-----+-----+-----+-----+
X Spare
CRN LTF blocked due to
creation in progress.
ENA LTF blocked due to not
enabled
Bits 8 to 11 :
bit 11 10 9 8
+-----+-----+-----+-----+
| X | X | X | MO |
+-----+-----+-----+-----+
MO LTF blocked from TF.

X Spare
Logical Managed object LTS.
Bits 4 to 7:
bit 7 6 5 4
+-----+-----+-----+-----+
| X | ENA | CRN | X |
+-----+-----+-----+-----+
CRN LTS blocked due to

creation in progress.
ENA LTS blocked due to not
enabled
X Spare
Bits 8 to 11:
bit 11 10 9 8
+-----+-----+-----+-----+
| DEV | RSL | LTF | MO |
+-----+-----+-----+-----+
MO LTS blocked from TS.

LTF LTS blocked from LTF
RSL LTS blocked from RSL
DEV LTS blocked from speech/data
device
Bits 12 to 15:
bit 15 14 13 12
+------+-----+-----+-----+
| CHG | X |SYNCB| X |
+------+-----+-----+-----+
X Spare
SYNCB LTS blocked due to synchronization
fault in BTS.
(Speech/data connection)
CHG Blocked due to change
5.3.1.61 maio Mobile Allocation Index Offset.
maio Mobile Allocation Index Offset.

5.3.1.62 mo Managed Object Instance.
mo Managed Object Instance.

RXCTA for the format and value range of
this parameter. The format is mo**,
where ** is the managed object.
Examples: motx, morx
5.3.1.63 model Model
Describes which BTS Logical Model the managed

object type belongs to. G01 or G12.
G01 The BTS Logical Model supported by

the Ericsson BTS RBS200.
G12 The BTS Logical Model supported by

the Ericsson BTS RBS2000.
5.3.1.64 MORE FAILED MANAGED OBJECTS EXIST
MORE FAILED MANAGED OBJECTS EXIST

Indicates too many subordinate
managed objects have failed to
load.
5.3.1.65 moty Managed Object Type.
moty Managed Object Type.

RXCTA for the format of this parameter.
5.3.1.66 mp Measuring Program
mp Identity of measuring program (MP)

Numeral 0 - 255.
5.3.1.67 mpstate Measuring Program State
mpstate Current state of the measuring program
DEFINED - An mp has been defined by

command RXHMI but no time
schedule has yet been
initiated.
SCHEDULED - A time schedule has been set

for this mp.
5.3.1.68 mpwr Maximum Transmitter Power.
mpwr Maximum Transmitter Power.

The parameter is expressed in dBm.
5.3.1.69 No abis paths exist
NO ABIS PATHS EXIST

Appears when ALL has been given in the
terminate command and no Abis paths are
connected to the specified transceiver
group.
5.3.1.70 NO FAULT INDICATIONS
NO FAULT INDICATIONS
The test of the managed object individual
has taken place and no faults were found.
5.3.1.71 NONE
NONE NONE is obtained if there is no defined

managed object for the specified MOTY.
In 37/190 83-CNT 241 1111 Uen:

NONE No measuring program is defined for
use by this function.
In 36/190 83-CNT 241 1111 Uen:
NONE No Transceiver Group with suitable
TX and reduced HFS existed.
5.3.1.72 NO PARAMETERS
NO PARAMETERS There is no administration data existing
for the specified managed object.
5.3.1.73 offs Frame Number Offset.
offs Frame Number Offset.

This parameter represents the time difference
from the TF acting as master in another TG.
Numerical. The parameter is expressed as a
number of TDMA frames.
5.3.1.74 repl Replacement Unit.
repl Replacement Unit.

The identifier of a faulty hardware unit.
This is a number between 0 and 47.
contain information on how
to find the replacement unit.
5.3.1.75 replmap Replacement Units Map.
replmap Replacement Units Map.

The identifier of a number of possibly faulty
hardware units.
twelve characters long where each digit of
the number represents four bits of the
binary fault map.
find the replacement units.
5.3.1.76 result Result
result Result of command.
Examples of common results:
ORDERED
The command was ordered for the
managed object.
EXECUTED
The command was executed for the
managed object.
FUNCTION BUSY
Function busy.
MO BUSY
is currently in use by another
function.
MO NOT IN VALID STATE

The managed object instance is
not in a correct state to be
executed by this command.
Correct state is COM.
MO NOT DEFINED
is not defined.
COMMAND ABORTED BY ANOTHER FUNCTION

The command is aborted due to
another function with higher
priority wanting access to the
processed managed object
instance.
ABORTED BY OPERATOR
Software loading is aborted due to
operator command RX***.
SUPERIOR MO NOT IN VALID STATE

One or more superior units are
not in a correct state.
[description of valid states]
result Result of the command.
EXECUTED
in service.
ABORTED
The process of bringing the managed
object into service was aborted.
The managed object is not in service.
SUBORDINATE MO NOT IN VALID STATE

One or more subordinate units are
not in a correct state.
[description of valid states]
MO IS ENABLED
is currently enabled.
SUBORDINATE MO IS ENABLED
has a subordinate object
that is currently enabled.
MO HOLDS ACTIVE TGC

holds the active TGC

application.
FORCE PARAMETER REQUIRED

can never be blocked without
the FORCE parameter.
MO CARRIES UNBLOCKABLE CHANNEL

carries a channel that cannot
be blocked without use of the
FORCE parameter.
DEBLOCKING ALREADY IN PROGRESS

currently being deblocked by
another manual deblocking command.
LOADING FAILED
The communication between the
BSC and the managed object in
BTS has failed during the
software loading process.
MO NOT LOADABLE FROM THE BSC

The managed object is loaded
from another loadable managed
object within the BTS.
MO LOADING ALREADY IN PROGRESS

Program loading for managed object
is already active due to another
program load command.
DISKFILE NOT FOUND

Operational Software required for
the managed object is not found
in IOG11.
DISKFILE ACCESS ERROR

Unable to access the file in
IOG11.
DISKFILE FORMAT ERROR

object instance due to file
incorrectly formatted.
INSUFFICIENT MEMORY
object instance due to insufficient
BSC memory.
BUFFER CONGESTION
Allocation of dynamic buffer
failed.
BLOCKED
The managed object is not in global
state OPER and is therefore not
available to the configuration
function.
CONFIG
The managed object is configured
with the indicated parameters.
FAILED
An attempt to configure this
managed object was not successful.
N/A
The managed object is not of class
RX, TG, TS, TX or DP therefore
configuration data is not
appropriate.
UNUSED
The managed object is not
configured, no other parameters
are printed for this managed
object.
CONFIG
The managed object is configured
with the indicated parameters.
UNCONFIG
The managed object is not
configured, no other parameters
are printed for this managed
object.
BUSY
is currently in use by another
function.
N/A
The managed object is not of class
TS, therefore configuration
hopping data is not
appropriate.
UNDEF
not defined.
TEST WAS PERFORMED

The test has been performed
and the faults if any were
found are printed later. If
no faults were found then
this is also indicated later.
BTS COMMUNICATION FAILURE

The test was not performed
because there was a BTS
communication or link
failure.
LOADING FAILED
The test failed because
loading of the managed
object was unsuccessful.
TEST NOT PERFORMED BY BTS

because the BTS did not
allow the test to be
performed (it does not
mean that communication
to the BTS failed).
TEST SUCCESSFUL
The test has been performed
and is successful.
LOADING FAILED
The test has failed because
loading of the managed object
instance was unsuccessful.
BTS COMMUNICATION FAILURE

There is a BTS communication or
link failure.
TEST FAILED
The test has been unsuccessful.
IMPOSSIBLE TO CLOSE LOOP

Impossible to close loop at
the BTS.
TEST NOT PERFORMED BY BTS

because the BTS would not
allow the test to be carried
out.
DEVICE NOT ACTIVATED

because no speech/data device
was seized for this
managed object.
ABIS PATH IN USE

The Abis path is currently
in use.
DEVICE CANNOT BE CONNECTED TO TRANSCEIVER

GROUP
The device specified is of
a type which cannot be
connected to a transceiver
group.
DIGITAL CONNECTION POINT ALREADY SEIZED

The digital connection
point is already connected
to the BTS.
DIGITAL CONNECTION POINT NOT SEIZED

The digital connection
point is not used.
MAX NO OF ABIS PATHS EXCEEDED PER BTS

LOGICAL MODEL
Not more than 2048 Abis
paths can be defined per
BTS logical model.
MAX NO OF ABIS PATHS EXCEEDED PER TG

Not more than 62 Abis
paths can be defined
per TG.
MISMATCH BETWEEN NUMBER OF ARGUMENTS

The number of DEV and DCP
arguments do not match.
NO MORE CONNECTIONS ALLOWED ON TRANSMISSION

DEVICE
No more Abis paths can be
connected to this
transmission device.
TRANSMISSION DEVICE IN INCORRECT STATE

The transmission device is
not in the correct state.
EXECUTED
The blocking order was successful

for this device.
DEVICE SEMIPERMANENT BUSY

semipermanent busy.
Specify again using the FORCE

parameter.
The command cannot operate on the

specified device.

EXECUTED
The deblocking was successful

for this device.
The command cannot operate on the

specified device.

DEVICE SEMIPERMANENT BUSY

semipermanent busy.
DEVICE CANNOT BE DEBLOCKED
The device cannot be deblocked.
Use command STDEP to check the

state of the device.
result SUCCESSFUL
A configuration was made for
this TG and extra TX equipment
is incorporated in the HFS.
UNSUCCESSFUL
A configuration was made for
this TG, however no extra
TX equipment is incorporated
in the HFS.
5.3.1.77 rsite Radio Site.
rsite Radio Site.

Identity of the radio site where the TG is
located. This parameter is represented by a string
of 3-15 characters.
5.3.1.78 ru Replacement Unit Index
ru Replacement Unit Index

The replacement unit index is used to show
that the four strings belong to the same
replacement unit. This is a number between

0 and 9.
5.3.1.79 rulogicalid Replacement Unit Logical Identity
rulogicalid Replacement Unit Logical Identity

The replacement unit logical identity
gives the replacement unit logical
identity of a managed object.
There may be a number of replacement unit
logical identities associated with each
managed object.
5.3.1.80 ruposition Replacement Unit Posistion
ruposition The replacement unit position gives the

replacement unit posistion of the managed
object. There may be a number of replacement
unit posistions associated with each managed
object.
5.3.1.81 rurevision Replacement Unit Revision
rurevision Replacement Unit Revision

The replacement unit revision gives the
replacement unit revision of the managed
object. There may be a number of replace-
ment unit revisions associated with each
managed object.
5.3.1.82 ruserialno Replacement Unit Serial Number
ruserialno Replacement Unit Serial Number

The replacement unit serial number gives the
replacement unit serial number of the managed
object. There may be a number of replacement
unit serial numbers associated with each
managed object.
5.3.1.83 rxd Receiver Diversity.
rxd Receiver diversity.

Combination of receiver antennae to be used.
A, B or AB.
A Antenna A used only.
B Antenna B used only.
AB Receiver diversity employed using
antennae A and B.
5.3.1.84 sbits Spare Bits.
sbits Spare Bits (8-bit binary number)
It is used to set bits in PCM

(Sa4-Sa8) and in TS16 (Sm1-Sm3)
(TS=time slot).
The PCM is specified as a binary
number according to the following

format:
Sa8 Sa7 Sa6 Sa5 Sa4 Sm3 Sm2 Sm1.
5.3.1.85 starttime Start Time
starttime Start time for the HFS extension.

Expressed as yymmdd hh.mm. or DIRECT
DIRECT - given when an HFS extension

is initiated immediately without use of
time supervision block, eg. by command
RXHEI.
5.3.1.86 state State.
state State of managed object instance.

This is not printed if the managed object
instance has not been defined.
DEF Out of service.

COM Manually blocked.
PREOP Pre-operational.
NOOP Temporarily out of operation.
OPER Operational.
FAIL Permanently out of operation.
5.3.1.87 swveract Actual Software Version.
swveract Actual Software Version

If the parameter is shown for a managed
object of managed object class TG, this is
the software version which is currently
loaded in all the TRXCs which has not
specified a specific software version
and, if BTS Logical Model G12, CF which
has not specified a specific software
version. If the parameter is shown for a
managed object of managed object class
TRXC/CF, this is a specific software
version currently loaded in the specific
TRXC/CF.
5.3.1.88 swverrepl Replacement Software Version.
swverrepl Replacement Software Version.

If the parameter is shown for a managed
object of managed object class TG, this is
the software version which will replace the
actual in the TRXCs which has DEFAULT
specified as replacement software version
and, if BTS Logical Model G12, CF which has
DEFAULT specified as replacement sofware
version at the next command ordered program
load or function change, or when then the
TRXC is brought into service. If the
parameter is shown for a managed object of
managed object class TRXC/CF, this is a
specific software version to be loaded in
the specific TRXC/CF at the next command

ordered program load or function change, or
when then the TRXC/CF is brought into
service.
DEFAULT Given for managed object of

managed object class TRXC or CF
when the software version to be
loaded is that of the superior TG
managed object.
5.3.1.89 tei Terminal Endpoint Identifier.
tei Terminal Endpoint Identifier.

LAPD element used for L2 addressing to a
TRXC and CF.
5.3.1.90 TF not Synchronized
TF NOT SYNCHRONIZED
The managed objects within the TG are not
currently used to support the cell because
the TF is not synchronized.
5.3.1.91 tfmode Timing Function Synchronization Mode.
tfmode Timing Function Synchronization Mode.

Mode of the timing function in the TG.
M, S or SA.
M Master. Synchronized towards PCM
network and distributing
synchronization to other TFs.
S Slave. Synchronized towards other TFs.
SA Standalone. Synchronized towards PCM
network.
5.3.1.92 tgc TGC Application State.
tgc TGC Application State.

The state of the TGC application in the TRXC.
The TGC may be in state TGC standby or TGC
active.
This is represented by:
A TGC active.
S TGC standby.
5.3.1.93 tgcoord Coordination on TG level.
tgcoord Coordination on TG level.

Indication of whether alarm coorination
is on TG level or MO level.
ON Alarm coordination on TG level

OFF Alarm coordination on MO level
5.3.1.94 time Time.
time Time.
The time the error was received, in the format
hh-mm-ss, where hh represents the hour, mm the
minute and ss the second that the error was
entered into the log.
This is a string eight characters long.
5.3.1.95 tn Time Slot Number.
tn Time Slot Number.

5.3.1.96 txad TX Logical Address.
txad TX Logical Address.
TX logical address associated with a

transmitter or a timeslot handler. The
parameter is a numeric value in the range
0 to 31, or HOP if given for a timeslot
handler and baseband frequency hopping.
5.3.1.97 xra Extended Range
xra Extended Range
YES The time slot handler is an extended

range time slot handler. It can support
traffic at a distance of greater then
35 km between the mobile station and the
base station.
NO The time slot handler is not an extended

range time slot handler.
5.3.1.98 1amap Internal Fault Map Class 1A.
1amap Internal Fault Map Class 1A.

A map which identifies faults internal to
the TG that affect Managed Object Instance
functionality. The faults are 'A', meaning
that faulty HW is part of the signalling
managed object. This map is also used to
represent internal fault class 1 for some
BTS versions.
twelve characters long, where each digit
of the number represents four bits of the
binary fault map, for example, 000000000011
means bits 4 and 0 are set.
Manuals. These operational manuals contain
information on how to decode the fault map.
5.3.1.99 1bmap Internal Fault Map Class 1B.
1bmap Internal Fault Map Class 1B.

the TG that affect Managed Object Instance
functionality. The faults are 'B', meaning
that the origin of the fault is
external to the signalling managed object.
means bit 9 is set.
for references to BTS Operation and
Maintenance Manuals.
These operational manuals contain information
on how to decode the fault map.
5.3.1.100 2amap Internal Fault Map Class 2A.
2amap Internal Fault Map Class 2A.

the TG that do not affect Managed Object
Instance functionality. The faults are 'A',
meaning that faulty HW is part of
the signalling managed object. This map is
also used to represent internal faults
means bits 44 and 45 are set.
manuals contain information on how
to decode the fault map.
5.4 TAS Command Fault code information

1. COMMAND NOT SUPPORTED FOR THIS MO
details
The command is not supported for

the specified managed object type
2 CANNOT MIX DIFFERENT BTS LOGICAL MODELS
details
The MO parameter specified managed object
instances from more than
one BTS logical model.
3 TOO MANY ARGUMENTS
details
details More than 6 Transcoder MUX devices
were specified or more than
3 devices specified.
4 WRONG MO CLASS
details
The specified managed object type has an unsuitable MO class.

possible classification of permitted managed object classes]
5 MO BUSY
details

currently in use by another function.
6 MO NOT IN VALID STATE
details
The managed object instance is not
in an appropriate state. The managed
object cannot already be defined.
7 MAXIMUM NUMBER OF MOTY EXCEEDED
details
No more managed objects of the specified managed object
type can be defined due to lack of MO data individuals.
Increase the MO data file in the RXCMSD block.
8 FUNCTION CHANGE OF MOTY ALREADY IN PROGRESS

MOTY = moty
details
[moty] The managed object type for which
the function change is in progress.
9 MO CANNOT BE UNDEFINED
details
Data connection(s) for the managed object exist.
10 FUNCTION CHANGE OF MOTY NOT IN PROGRESS
details
Function change of the specified MO type is not in progress
11 COMMAND NOT ALLOWED AFTER START
details
The command is not allowed to be executed after a start. The command

will be allowed again after a restart.
12 NO MORE MO CAN BE DEFINED IN THE BTS LOGICAL MODEL

RESTRICTING BLOCK = block
details
No more managed objects can be defined in this BTS logical model

due to a lack of task individuals in a block. To be able to
define more managed objects in the BTS logical model, the number
of task individuals in the restricting block must be increased.
13 NO MORE MO CAN BE DEFINED IN BSC
details
No more managed objects of this class can be defined in this BSC. The maximum
allowed number of managed object instances of this managed object class is reached.
14 NO MORE CONNECTIONS ALLOWED ON TRANSMISSION DEVICE
details
No more connections are allowed
to this transmission device.
15 RSITE CONVERSION TABLE FULL
details No more radio site identities can be loaded into the radio site conversion table.
16 CANNOT MIX DIFFERENT MANAGED OBJECT CLASSES
details
The managed objects specified in the command must belong to the same
managed object class.
17 TOO MANY TRANSMISSION DEVICES SPECIFIED
details
Too many transmission devices were specified in the command
18 THE SPECIFIED CELL DOES NOT EXIST
The specified cell has not been defined. Command RLDEI may be used to define a cell.
19 CHGR ALREADY CONNECTED TO A TG
details
The channel group is already connected to a TG.
20 COMMAND ABORTED BY ANOTHER FUNCTION
details
The command is aborted due to another function with higher priority wanting
access to the processed managed object instance.
21 DEVICE CANNOT BE CONNECTED TO DIGITAL PATH
details
The device specified is of a type
which cannot be connected to a DP
managed object.
22 DIP SUPERVISION LOGICAL DEVICE ALREADY CONNECTED
details
The device specified is already
connected to a DP managed object
23 SPARE
24 TEI NOT UNIQUE ON TRANSMISSION DEVICE
details
The specified TEI/CTEI has already
been assigned to a managed object
which uses the same transmission
device.
25 TEI NOT UNIQUE IN TG
details
The specified TEI/CTEI has already been assigned to a managed object

which uses the same transmission device.
26 ILLEGAL TF MODE TRANSITION
details
TF MODE can only be changed to or from stand-alone mode
27 DEVICE DEFINITION NOT ALLOWED
details
Transmission devices for speech and data must be removed

before new ones can be defined.
28 CHGR NOT HALTED
details
The channel group is not halted. Command RLSTC may be used to halt a channel
group.
29 CHGR NOT DEFINED
details
The channel group is not defined. Command RLCFI may be used to define a channel
group.
30 SPARE
31 NO MORE CHGR CAN BE CONNECTED
details
No more channel groups can be connected to this managed object
32 CHGR NOT CONNECTED
details
The channel group is not connected to the specified managed object.
33 ILLEGAL HOPPING TYPE AND COMBINER COMBINATION
details
Synthesised hopping is not possible with a filter combiner
34 RSITE CONNECTION TABLE BUSY
details
The RSITE connection table is busy. Try again later
35 TRANSMISSION DEVICE IN INCORRECT STATE
details
The transmission device is not in the correct state
36 DIGITAL CONNECTION POINT ALREADY CONNECTED
details
The digital connection point is already connected
37 TOO MANY DIGITAL CONNECTION POINTS SPECIFIED
details
Too many digital connection points have been specified

in the command
38 COMMAND NOT VALID FOR EXTERNAL CELLS
details
The cell specified is external and not allowed in the command
39 DEVICE CANNOT BE CONNECTED TO TRANSCEIVER
details
The device specified is of a type which cannot be connected to a

transceiver.
40 INSUFFICIENT LAPD CONCENTRATION FACTOR
details
Insufficient LAPD concentration
factor on transmission device.
It is only allowed to concentrate
TRXCs on the same transmission
device up to and including the
LAPD concentration factor used
on the transmission device.
The restricting LAPD concentration
factor may be specified for any
transceiver group using the
transmission device.
41 MAXIMUM LAPD CONCENTRATION FACTOR CANNOT BE DECREASED
Maximum concentration factor can

only be decreased if the number
of TRXCs sharing a transmission
device is less or equal to the
new value.
42 MAXIMUM LAPD CONCENTRATION FACTOR CANNOT BE INCREASED
Maximum LAPD concentration factor can

not be increased due to processor
capacity limitations in the transceiver
handler.
43 SPARE
44 SPARE
45 FUNCTION NOT SUPPORTED.
details
This function is not supported by the BTS
46 SPARE
details
Measuring program already defined (The specified measuring program
identity has already been defined in time supervision block).
47 MAXIMUM NUMBER OF MEASURING PROGRAMS ALREADY DEFINED FOR

THE FUNCTION
details
There is already a measuring program defined for use by this function.
48 MAXIMUM NUMBER OF MEASURING PROGRAMS ALREADY DEFINED
details
It is not possible to define any more

measuring programs in the time
supervision block.
49 HFS EXTENSION FUNCTION IN PROGRESS
details
The function is currently in use by another source.:
49 SPARE
50 CANNOT MIX DIFFERENT TRANSCODER DEVICE TYPES
details
Device types RXCTRD and RXCTRD1

were mixed in the same command
6 Link Handling Subsystem, LHS

6.1.1 Commands RIETI, RIETE, Radio Interface Equipm. Type, Init/End
RADIO INTERFACE EQUIPMENT TYPE, INITIATE
RIETI:DEV=dev,EQMTYPE=eqmtype;
RADIO INTERFACE EQUIPMENT TYPE, END
RIETE:DEV=dev...;
6.1.2 Commands RISPI, RISPE RISPP Radio Interface Semiperm. Path,

Init/End/Print
RADIO INTERFACE SEMIPERMANENT PATH, INITIATE

+ + + + + +
RISPI:TSLOT1=tslot1,TSLOT2=tslot2 |, NAME=name | |,PRI=pri | |,REL |;
+ + + + + +
RADIO INTERFACE SEMIPERMANENT PATH, END
RISPE:TSLOT=tslot...;
RADIO INTERFACE SEMIPERMANENT PATH, PRINT
+ +
| |
| + ++ ++ + |
|EMG=ALL |,STATE=state||,PRI=pri||,REL| |
| + ++ ++ + |
| |
| |
| |
| + + |
RISPP: + |emrs | + ++ ++ ++;
|EMG=emg,EMRS= + + |,STATE=state||,PRI=pri||,REL||
| |ALL | + ++ ++ +|
| + + |
| |
|TSLOT=tslot.... |
| |
|NAME=name |
+ +
6.1.3 Commands RICSC, RICSP, Clock Sync. status, Print/Change
RADIO INTERFACE CLOCK SYNCHRONIZATION STATUS, CHANGE
RICSC:EMG=emg,EMRS=emrs;
RADIO INTERFACE CLOCK SYNCHRONIZATION STATUS, PRINT
+ +
|EMG=ALL |
| |
| + + |
RICSP: + |emrs....| +;
|EMG=emg,EMRS= + + |
| |ALL | |
| + + |
+ +
6.1.4 Commands RILSP, RILTP , Line Terminal (Status), PRINT
RADIO INTERFACE LINE TERMINAL, PRINT
+ +
| EMG=ALL |
| + + |
| | emrs... | |
RILTP: + EMG=emg, EMRS= + + +;
| | ALL | |
| + + |
| DEV=dev... |
+ +
RADIO INTERFACE LINE TERMINAL STATUS, PRINT
+ +
| EMG=ALL @,STATE=state ` |
| |
| + + |
| | emrs... | |
| EMG=emg, EMRS= + + @,STATE=state ` |
RILSP: + | ALL | +;
| + + |
| |
| DEV=dev... |
| |
| TSLOT=tslot... |
+ +
6.1.5 Commands RIRTI, RITTI, Radio Selector Test & Line Terminal Test
.RADIO INTERFACE RADIO SELECTOR TEST, INITIATE
RIRTI:EMG=emg,EMRS=emrs;
RADIO INTERFACE LINE TERMINAL TEST, INITIATE
RITTI:DEV=dev;
6.1.6 commands RIBLI, RIBLE, Radio Interface, Blocking/Deblocking
RADIO INTERFACE BLOCKING, INIT
+ +
|EMG=emg,EMRS=emrs|
RIBLI: + + ;
|DEV=dev... |
+ +
RADIO INTERFACE BLOCKING, END
+ +
|EMG=emg,EMRS=emrs|
RIBLE: + + ;
|DEV=dev... |
+ +
6.1.7 Commands RISTP, RIDCP, Radio Selector (Disturbance counters) PRINT
RADIO INTERFACE RADIO SELECTOR DISTURBANCE COUNTERS, PRINT
+ +
|emrs... |
RIDCP:EMG=emg,EMRS= + +;
|ALL |
+ +
RADIO INTERFACE RADIO SELECTOR STATUS, PRINT
+ +
|emrs....|
RISTP:EMG=emg,EMRS= + +;
|ALL |
+ +
6.1.8 RADIO INTERFACE LAPD CONCENTRATOR ,

RICCI/RICCE/RICCP/RICBI/RICBE/RICBP
RADIO INTERFACE LAPD CONCENTRATOR CONNECTION, INIT
RICCI: CONCB=concb, CTSLOT=ctslot, NCTSLOT=nctslot, TEI=tei ;
E.g. RICCI: CONCB=RILCO-0, CTSLOT=RILT-1-4, NCTSLOT=NCTSLOT-9-7, TEI=1 ;
RADIO INTERFACE LAPD CONCENTRATOR CONNECTION, END
+ +
|CTSLOT=ctslot....|
RICCE: + + ;
|NCTSLOT=nctslot. |
+ +
E.g.RICCE: NCSTSLOT=RILT-9-31;
RADIO INTERFACE LAPD CONCENTRATOR CONNECTION, PRINT
+ +
| EMG=ALL |
| + + |
RICCP | | + + | |
| | emg |, EMRS= emrs + | | ;
| EMG=+ + + | |
| | ALL | |
| + + |
+ +
RADIO INTERFACE LAPD CONCENTRATOR BOARD, INITIATE
RICBI:DEV=dev, CONCB=concb ;
E.g.RICBI:DEV=RILT-4,CONCB=RILCO-8 ;
RADIO INTERFACE LAPD CONCENTRATOR BOARD, END
RICBE:DEV= dev ;
E.g. RICBE:DEV= RILT-4 ;
RADIO INTERFACE LAPD CONCENTRATOR BOARD, PRINT
+ +
| CONCB=concb |
| |
| DEV=dev |
| + + |
RICCP | | + + | |
| | emg |, EMRS= emrs + | | ;
| EMG=+ + + | |
| | ALL | |
| + + |
+ +
6.2 LHS Faultcode Information

FAULT CODE 2
EMRS NOT CONNECTED TO EM
The indicated EMRS is not
connected to EM.
FAULT CODE 3
DEVICE NOT FULLY CONNECTED
The device is not fully connected.
FAULT CODE 4
EQUIPMENT TYPE DOES NOT EXIST
The specified equipment type does
not exist.
FAULT CODE 6
NAME NOT DEFINED
The given name does not exist.
FAULT CODE 10
EMRS TEMPORARILY BUSY WITH OTHER TASKS
The EMRS is temporarily busy
with other tasks.
FAULT CODE 12
DEVICE ALREADY CONNECTED TO EQUIPMENT TYPE
The device is already connected
to an equipment type.
FAULT CODE 13
DEVICE NOT CONNECTED TO EQUIPMENT TYPE
The device is not connected to
any equipment type.
FAULT CODE 16
DEVICE NOT MANUALLY BLOCKED
Device not manually blocked.
FAULT CODE 18
EMRS NOT MANUALLY BLOCKED
The EMRS must be manually
blocked to execute this command.
FAULT CODE 19
EMRS ALREADY MANUALLY BLOCKED
The EMRS is already manually
blocked.
FAULT CODE 20
TOO MANY TIMESLOTS SPECIFIED
Too many timeslots are
specified by the same command.
FAULT CODE 21
TIMESLOT ALREADY CONNECTED
The indicated timeslot is
already used in a semipermanent
path.
FAULT CODE 23
FAULTY EQUIPMENT TYPE
The specified device is connected
to faulty equipment type.
FAULT CODE 24
FAULTY DEVICE STATE
The indicated device must not be
in a manually blocked state.
FAULT CODE 25
TIMESLOTS NOT IN THE SAME EMRS
The timeslots are not connected
to the same EMRS.
FAULT CODE 26
TIMESLOT IS SYSTEM BUSY
The indicated timeslot is used
by the system for frame
synchronization or for control

signalling.
FAULT CODE 27
ERROR IN EMRS Error in EMRS.
It is not possible to initiate
a semipermanent path in th EMRS.
FAULT CODE 28
STORAGE SPACE EXCEEDED IN RISPC
No storage space in RISPC.
FAULT CODE 29
DEVICE SEMIPERMANENTLY CONNECTED
The indicated device is semi-
permanently connected.
FAULT CODE 30
TIMESLOTS NOT IN THE SAME DEVICE
The indicated timeslot does
not belong to the same device
as the previous timeslot.
FAULT CODE 31
EM BLOCKED
The command cannot be executed
while the EM is blocked.
FAULT CODE 33
TOO MANY DEVICES SPECIFIED
A maximum of 16 devices can be
given in the same command.
FAULT CODE 35
DEVICE NOT CONNECTED TO EM
The specified device is not
connected to EM.
FAULT CODE 36
TIMESLOT IN TEST
The indicated timeslot is occupied
by test.
FAULT CODE 37
STANDBY INLET FAULTY
The standby synchronization inlet
must not be faulty to execute this
command.
FAULT CODE 38
STANDBY SYNCHRONIZATION DEVICE BLOCKED
The device used as standby
synchronization inlet must not
be manually blocked or control
blocked to execute this command.
FAULT CODE 39
EMRS MANUALLY BLOCKED
The indicated EMRS must not be
manually blocked to execute this
command.
FAULT CODE 40
STANDBY INLET NOT CONNECTED
The device used as standby synchro-
nization inlet is not fully
connected.
FAULT CODE 41
DEVICE CONNECTED TO DIGITAL PATH
The indicated device is connected
to a digital path.
FAULT CODE 43
DEVICE EXCEPT THE EXECUTIVE INLET NOT BLOCKED
All the devices in the EMRS except
the device used as executive
synchronization inlet must be
manually blocked to execute this
command.
FAULT CODE 47
TOO MANY EMRS SPECIFIED
A maximum of 16 EMRSs can be
given in the same command.
FAULT CODE 50
NO SYNCHRONIZATION INLETS DEBLOCKED
A device used as synchronization
inlet must be manually deblocked
to execute this command.
FAULT CODE 51
NO SYNCHRONIZATION INLET DEFINED
The command cannot be executed
since no synchronization inlet
is defined.
FAULT CODE 53
SEMIPERMANENT CONNECTION IN SYNCHRONIZATION DEVICE
The device used as executive
synchronization inlet contains
semipermanent connection(s).
FAULT CODE 54
INCOMPATIBLE TYPE OF HARDWARE
The hardware is not equipped
with a standby synchronization
facility.
FAULT CODE 55
RICS TEMPORARILY BUSY
The function block RICS is
temporarily busy with other
tasks.
FAULT CODE 56
NO ANSWER FROM EMRP
It is not possible to determine
if the hardware is equipped with

a standby synchcronization
facility.
FAULT CODE 57
STORAGE SPACE EXEEDED IN RISPH
No storage space in RISPH.
FAULT CODE 58
TIMESLOT NOT CONNECTED BY COMMAND RISPI
The indicated timeslot is not
connected to a path set up by
command RISPI.
FAULT CODE 59
DEVICE ALREADY CONNECTED TO CONCENTRATOR BOARD
The specified device is already
connected to a LAPD concentrator
board.
FAULT CODE 60
CONCENTRATOR BOARD ALREADY CONNECTED TO DEVICE
The specified LAPD concentrator
board is already connected to a
device.
FAULT CODE 61
CONCENTRATOR BOARD NOT CONNECTED TO EM
board is not connected to EM.
FAULT CODE 62
DEVICE NOT CONNECTED TO CONCENTRATOR BOARD
The device is not connected a
LAPD concentrator board.
FAULT CODE 63
CONCENTRATORS CONNECTED ON CONCENTRATOR BOARD
The indicated device has LAPD
concentrators connected.
FAULT CODE 64
TOO MANY CONCENTRATOR BOARDS SPECIFIED
A maximum of 16 LAPD concentrator
boards can be specified by the
same command.
FAULT CODE 65
CONCENTRATOR BOARD NOT FULLY CONNECTED
board is not fully connected.
FAULT CODE 66
TEI VALUE ALREADY USED FOR THE CONCENTRATOR
The specified TEI value has
already been used for the
LAPD concentrator.
FAULT CODE 67
TOO MANY TEI VALUES SPECIFIED
Too many TEI values have been

specified in the command.
FAULT CODE 69
TIMESLOTS AND CONCENTRATOR BOARD NOT IN SAME EMRS
The specified timeslots and
LAPD concentrator board are
not connected to the same
EMRS.
FAULT CODE 70
TOO MANY NCTSLOTS CONNECTED TO CONCENTRATOR
Too many non-concentrated
timeslots are connected
to the LAPD concentrator.
FAULT CODE 71
NOT ENOUGH TIMESLOTS AVAILABLE ON CONCENTRATOR BOARD
There are not enough timeslots
available for the LAPD
concentrator.
FAULT CODE 74
RILT DEVICE AND CONCENTRATOR BOARD NOT IN THE SAME EMG
The specified device and LAPD
concentrator board are not
connected to the same EMG.
FAULT CODE 75
FAULTY SPECIFICATION OF TSLOT
The indicated timeslot has been
specified in a faulty context.
FAULT CODE 76
TSLOT NOT CONN TO CONCENTRATOR
The indicated timeslot is not
connected to a concentrator.
FAULT CODE 77
TOO MANY DEVICES SPECIFIED
A maximum of 16 RILT devices
can be specified by the samme
command.
FAULT CODE 78
DEVICE CONNECTED TO CONCENTRATOR BOARD
The indicated device is
connected to a LAPD concentrator
board.
FAULT CODE 79
TEST LOOP PATH DEFINED
A test loop path is defined
for the stated LAPD concentrator
board.Disconnection of the test
loop path has failed.
FAULT CODE 80
TOO MANY CONCENTRATORS SPECIFIED
More than 10 LAPD concentrators
are not allowed to be specified
for a LAPD concentrator board.
7 Radio O&M Subsystem, ROS

7.1 Command description
7.1.1 Call path tracing in the BSC, RAPTI
+ +
| DEV=dev |
RAPTI:| LCH=lch +;
| CIC=cic |
+ +
7.1.2 Commands RADPI/RADPE/RADPP, BSC (CCITT) Destination Point Code

Initiate
INITIATE
RADPI:DPC=dpc,NEI=nei;
END
RADPE;
PRINT
RADPP;
7.1.3 Commands RADCI/RACPE/RADCP, BSC (ANSI) Destination Point Code

Initiate
INITIATE
RADCI:SP=sp;
END
RADCE;
PRINT
RADCP;
7.1.4 Commands RARMC, RARMP Transmission Type
CHANGE
RARMC: TRANSMTYPE=transmtype;
PRINT
RADMP;
7.1.5 Commands RASIC, RASIP, Signalling Type
CHANGE
RASIC: SIGTYPE=sigtype;
PRINT
RASIP;
7.1.6 commands RASSI/RASSE/RASAR/RASSC/RASAP, Seizure Supervision of

Devices,
SEIZURE SUPERVISION OF DEVICES, INITIATE
RASSI:DETY=dety;
SEIZURE SUPERVISION OF DEVICES, END
+ +
RASSE:DETY=dety |,PERM|;
+ +
SEIZURE SUPERVISION OF DEVICES, PRINT
RASSP:DETY=dety;
SEIZURE SUPERVISION OF DEVICES, RESET
RASAR:DETY=dety;
SEIZURE SUPERVISION OF DEVICES, CHANGE
+ +
|PL=pl ACL=acl`|
RASSC:DETY=dety,+ +;
|ACL=acl |
+ +
7.2 Commands RATRI/RATRE/RATRP, Cell Traffis

Recording commands
RADIO CONTROL ADMINISTRATION CELL TRAFFIC RECORDING, INITIATE
RATRI: CELL=cell, EVENT=event, DTIME=dtime,
+ +
| EV |
RTYPE = + + ;
| EV & ME TIMEW=timew |
+ +
RADIO CONTROL ADMINISTRATION CELL TRAFFIC RECORDING, END
RATRE;
RADIO CONTROL ADMINISTRATION CELL TRAFFIC RECORDING, PRINT
RATRP;
8 ROS, Command Faultcode information

FAULT CODE 1
SUPERVISION IS ALREADY CONNECTED
FAULT CODE 2
SUPERVISION IS ALREADY DISCONNECTED
FAULT CODE 3
CELL NOT DEFINED
FAULT CODE 4
SUPERVISION CANNOT BE DISCONNECTED WHEN ALARM
IS ISSUED
FAULT CODE 5
SUPERVISION DATA NOT LOADED
FAULT CODE 6
INVALID DEVICE TYPE SPECIFIED
FAULT CODE 7
DEVICE TYPE DOES NOT HAVE PPS FUNCTION
Device type does not have the

Pre-Post Service state function
associated with it.
FAULT CODE 9
INCORRECT ALARM LIMIT VALUE SPECIFIED
FAULT CODE 10
SUPERVISION IS ALREADY PERMANENTLY DISCONNECTED
FAULT CODE 11
ALARM CLASS CANNOT BE CHANGED, ALARM ISSUED
FAULT CODE 12
A LOWER ALARM LIMIT VALUE IS GREATER THAN
A HIGHER ALARM LIMIT VALUE
A lower alarm limit value

greater than a higher alarm
limit value.
Action:
Ensure a higher alarm limit
value is greater than a lower
alarm limit value.
FAULT CODE 13
TWO OR MORE ALARM LIMITS MAY NOT HAVE THE SAME
ALARM CLASS
Two or more alarm limits

are not allowed to have the
same alarm class.
Action:
Ensure that different alarm
classes are used when more
than one alarm limits are given.
FAULT CODE 14
NO ALARM GIVEN
Alarm resetting ordered but

no alarm has been given.
FAULT CODE 15
INVALID TIME PERIOD SPECIFIED
Specified period length not

within the limits.
FAULT CODE 18
NO DEVICE DATA AVAILABLE FOR OUTPUT
No device data available

for output.
FAULT CODE 20
THE DEVICE IS NOT IN PPS
The device is not in PPS.
FAULT CODE 22
CIC NOT DEFINED
CIC has not been

connected to the device.
FAULT CODE 23
CIC ALREADY DEFINED
CIC already connected to

the device.
FAULT CODE 24
CIC ALREADY USED FOR ANOTHER DEVICE
The CIC has already been used

for another device.
FAULT CODE 25
RECORDING NOT ACTIVE
FAULT CODE 27
DESTINATION POINT CODE ALREADY LOADED
FAULT CODE 28
DESTINATION POINT CODE NOT LOADED
Destination point code and

Network Indicator not loaded.
FAULT CODE 29
DATA CHANGE IN PROGRESS
Command not allowed, data

change command in progress.
FAULT CODE 30
DATA CHANGE COMMAND HAS BEEN INITIATED
Data change command has

been initiated.
FAULT CODE 31
ALL DEVICES ARE NOT IN PPS
All devices are not in

pre-post service state.
FAULT CODE 33
MEASURING PROGRAM ALREADY OCCUPIED
Measuring program already defined.

(The specified measuring program
identity has already been defined.)
FAULT CODE 35
RECORDING ALREADY INITIATED FOR ORDERED CELL
FAULT CODE 38
COMMAND NOT VALID FOR EXTERNAL CELLS
The command must not be used

for external cells.
FAULT CODE 41
TRANSCEIVER TEST EQUIPMENT ALREADY DEFINED
The transceiver test equipment is

already defined in the cell.
FAULT CODE 42
TRANSCEIVER TEST EQUIPMENT NOT DEFINED
No transceiver test equipment is

defined in the cell.
FAULT CODE 43
TRANSCEIVER AUTOMATIC SUPERVISION ACTIVE
The transceiver test equipment

can not be deleted due to the
transceiver automatic supervision
is active in the cell.
FAULT CODE 44
TRANSCEIVER PERIODIC TEST ACTIVE
The transceiver periodic test is

already active for the BSC.
FAULT CODE 45
TRANSCEIVER PERIODIC TEST NOT ACTIVE
The Transceiver periodic test is

not active for the BSC.
FAULT CODE 46
CELL INCLUDED IN TRANSCEIVER PERIODIC TEST
The cell is already included

in the transceiver periodic
test.
FAULT CODE 47
CELL EXCLUDED FROM TRANSCEIVER PERIODIC TEST
The cell is already excluded

from the transceiver periodic
test.
FAULT CODE 48
TOO MANY CELLS SPECIFIED
Too many cells are specified.
FAULT CODE 50
CELL STATE NOT ACTIVE
The cell must be in state ACTIVE.
FAULT CODE 51
INCLUDED IN PERIODIC TEST AND AUTOMATIC SUPERVISION ACTIVE
The transceiver test data can not

be changed due to both the transceiver
automatic supervision and the
transceiver periodic test is active
in the cell.
FAULT CODE 52
TOO MANY SIMULTANEOUS TRANSCEIVER TESTS
Too many simultaneous transceiver

tests are in progress.
FAULT CODE 53
TRANSCEIVER TEST IN PROGRESS
A transceiver test is in progress

in the cell.
FAULT CODE 54
DESTINATION POINT CODE NOT IN ACCORDANCE WITH SIGNALLING TYPE
Destination point code not in accordance

with signalling type.
FAULT CODE 55
DEVICE FILE SIZE GREATER THAN ZERO -
RESTRICTING BLOCK = block
At least one device file size is greater

than zero
FAULT CODE 56
BSC EXCHANGE PROPERTY DESIGNATION NOT RECOGNIZED.
The designation is incorrectly spelled

or the function related to this desig-
nation is not supported by this
exchange.
FAULT CODE 57
BSC EXCHANGE PROPERTY VALUE NOT ACCEPTED
Value for this designation

not accepted.
Action: See Application Information
for block ROEPC.
FAULT CODE 58
DATA MISMATCH
This property value cannot be

accepted before other data is changed.
for block ROEPC.
FAULT CODE 59
FILE SIZE ALTERATION NEEDED
This property value cannot be

accepted before file size alteration
is performed.
for block ROEPC.
FAULT CODE 61
REARRANGEMENT ALREADY IN PROGRESS
Immediate or Periodic rearrangement

already in progress.
FAULT CODE 62
TRH LOAD DATA CHANGE IN PROGRESS
Modification of TRH load data

by a command is in progress
FAULT CODE 63
TOO MANY INTERVALS REQUESTED
The number of requested intervals

has not been monitored
FAULT CODE 64
MEASURING PROGRAM NOT FOUND
All measuring programs are already occupied
FAULT CODE 65
SWITCHING NETWORK TERMINAL IS NOT
CONNECTED TO THE SWITCH
Stated switching network

terminal is not connected to
the switch.
FAULT CODE 66
DP DEFINED
The number of defined DP individuals

are not equal to zero.
FAULT CODE 67
MAXIMUM NUMBER OF RECORDINGS IN PROGRESS
Maximum number of simultaneous recordings

are already in progress.
FAULT CODE 68
LOAD DATA DOES NOT EXIST FOR THIS SNT TYPE
Load data does not exist for this SNT type
FAULT CODE 69
NEW LOAD VALUES RECEIVED
New load values have been calculated
FAULT CODE 70
THE FUNCTION IS ALREADY INITIATED
The function cannot be initiated again when it

is already initiated.
9 Radio Control Subsystem, RCS

9.1.1 Radio Control Cell System Type, RLTYI/RLTYP/RYLTE/RYLTC
INITIATE
RLTYI:GSYSTYPE=gsystype;
PRINT
RLTYP;
END
RLTYE;
RLTYC: GSYSTYPE=gsystype ;
9.1.2 Commands RLDEI, RLDEP, RLDEE, RLDEC, Definition Of Cell
INITIATE
+ +
RLDEI:CELL=cell |,EXT | , CSYSTYPE= csystype;
+ +
CHANGE
+
|
|+ + + +
RLDEC:CELL=cell +| ,CGI=cgi | | ,BSIC=bsic |
|+ + + +
|
+
+ + + +
| ,BCCHNO=bcchno | | ,AGBLK=agblk |
+ + + +
+ + + +
| ,MFRMS=mfrms | | ,BCCHTYPE=bcchtype|
+ + + +
+
|
+ + + +|
| ,FNOFFSET=fnoffset | | ,XRANGE=xrange |+ ;
+ + + +|
|
PRINT
+ +
| cell... |
| |
RLDEP:CELL=+ + ++ , CSYSTYPE= csystype ;
| |,EXT ||
| ALL + +|
| |,XRANGE ||
+ + ++
END
RLDEE:CELL=cell;
9.1.3 Commands RLDSI, RLDSE, Definition of subcell,
INITIATE
RLDSI:CELL=cell...;
END
RLDSE:CELL=cell...;
9.1.4 Commands RLDTC, RLDTP, Data administration TSC,
CHANGE
RLDTC:CELL=cell, SCTYPE=sctype, TSC=tsc;
PRINT
+ +
| cell... |
RLDTP:CELL=+ +;
| ALL |
+ +
9.1.5 Commands RLCFI, RLCFP, RLCFE, RLCHC, Config. Frequency Data,
INITIATE
+ +
|,DCHNO=dchno... |
| |
RLCFI:CELL=cell + +;
|,CHGR=chgr ,DCHNO=dchno... |
| |
+ +
PRINT
+ +
| |
| + + |
| cell, |,CHGR=chgr... | |
RLCFP: CELL=+ + + +;
| cell... |
| |
| ALL |
END
RLCFE:CELL=cell,DCHNO=dchno...;
CONFIGURATION FREQUENCY HOPPING DATA, CHANGE
+ +
| + + |
+ + |,HOP=hop |,HSN=hsn| |
RLCHC:CELL=cell |,CHGR=chgr| + + + +;
+ + | |
|,HSN=hsn |
+ +
9.1.6 Commands RLDGI, RLDGE, RLDGC, Definition Of Channel Group,
INITIATE
+ +
RLDGI: CELL=cell,CHGR=chgr... |,SCTYPE=sctype |;
+ +
CHANGE
RLDGC:CELL=cell,CHGR=chgr...,SCTYPE=sctype;
PRINT
+ +
| cell... |
RLDGP: CELL=+ + ;
| ALL |
+ +
END
RLDGE:CELL=cell,CHGR=chgr...;
9.2 Commands RLDCI, RLDCP, RLDCE, Diff. Channel Alloc.

Data
INITIATE
+ +
RLDCI:|EMERGPRL=emergprl|;
+ +
PRINT
RLDCP;
END
RLDCE;
9.2.1 Commands RLMFC, RLMFP, RLMFE, Measurement Frequencies
CHANGE
+ + + +
RLMFC:CELL=cell,MBCCHNO=mbcchno...| ,LISTTYPE=listtype | |, MRNIC | ;
+ + + +
PRINT
+ +
| cell... | + +
RLMFP:CELL= + + | ,LISTTYPE=listtype | ;
| ALL | + +
+ +
END
+ +
| mbcchno... | + + + +
RLMFE:CELL=cell,MBCCHNO= + + | ,LISTTYPE=listtype | |, MRNIC | ;
| ALL | + + + +
+ +
9.2.2 Commands RLCPC, RLCPP, Config. Power Data
CHANGE
+ + + +
| | sctype | |
RLCPC:CELL=cell |,SCTYPE= + + |
| | ALL | |
+ + + +
+ +
|+ + + + + +|
+|,MSTXPWR=mstxpwr | |,BSPWRT=bspwrt | |,BSPWRB=bspwrb |+;
|+ + + + + +|
+ +
PRINT
+ +
| cell... |
| |
RLCPP: CELL= + + + + ;
| ALL |,EXT | |
| + + |
+ +
9.3 Command RLCCC, Config Control Channel Data
CHANGE
+
|+ ++ ++ +
RLCCC:CELL=cell+|,TN=tn ||,CHGR=chgr ||,SDCCH=sdcch |
|+ ++ ++ +
+
+
+ +|
|,CBCH=cbch |+;
+ +|
+
9.3.1 Commands RLBDC, RLDBP, Configuration BPC DATA
CHANGE
+ +
| |
RLBDC:CELL=cell|,CHGR=chgr |,NUMREQBPC=numreqbpc;
| |
+ +
PRINT
+ +
| |
| + + |
| cell |,CHGR=chgr... | |
RLBDP: CELL=+ + + +;
| cell... |
| |
| ALL |
+ +
9.3.2 Commands RLCAC, RLCAP, BSC Ciphering Algorithm
CHANGE
RLCAC: ALG=alg;
PRINT
RLCAP;
9.3.3 Commands RLSTC, RLSTP, Cell STATE,
CHANGE
+ + ++
| |chgr...||
RLSTC:CELL=cell|,CHGR=+ +|,STATE=state;
| |ALL ||
+ + ++
PRINT
+ +
| cell... |
| |
RLSTP:CELL= + + + + ;
| ALL |,STATE=state| |
| + + |
+ +
9.3.4 Commands RLCXC, RLCXP, Configuration, DTX Downlink,
CHANGE
RLCXC:CELL=cell, DTXD=dtxd;
PRINT
+ +
| cell... |
RLCXP:CELL= + + ;
| ALL |
+ +
9.3.5 Commands RLCRP, Cell Resources
PRINT
+ +
|cell... |
RLCRP:CELL=+ +;
|ALL |
+ +
9.4 Commands RLNRI, RLNRE, RLNRC, RLNRP,

Neighbouring Relation
INITIATE
+ +
RLNRI:CELL=cell,CELLR=cellr | ,SINGLE | ;
+ +
PRINT
+
| + +
+
| + + + +
RLNRC:CELL=cell,CELLR=cellr + | ,CS=cs | | ,CAND=cand |
| + + + +
+
+ + + +
+ + | | KOFFSETP=koffsetp | |
| ,KHYST=khyst | |, + + |
+ + | | KOFFSETN=koffsetn | |
+ + + +
+ + + +
+ + | | LOFFSETP=loffsetp | |
| ,LHYST=lhyst | |, + + |
+ + | | LOFFSETN=loffsetn | |
+ + + +
+ + + +
+ + | | TROFFSETP=troffsetp | |
| ,TRHYST=trhyst | |, + + |
+ + | | TROFFSETN=troffsetn | |
+ + + +
+
+ + + + |
| ,AWOFFSET=awoffset | | ,BQOFFSET=bqoffset | +;
+ + + + |
+
PRINT
+ + + +
| | cellr... | |
| CELL=cell ,CELLR= + + | + +
RLNRP: + | ALL | + | ,NODATA | ;
| CELL=ALL + + | + +
| |
+
END
RLNRE:CELL=cell,CELLR=cellr;
9.4.1 Cell locating Area, RLLAP
PRINT } ~ ! lai... ! RLLAP:LAI= \ [ ; ! ALL ! | {
9.5 Commands RLLDP, RLLDC, Cell Locating Disconnect

Data
PRINT
+ +
| cell... |
RLLDP:CELL= + + ;
| ALL |
+ +
CHANGE
+ +
|+ + + +|
RLLDC:CELL=cell +| ,MAXTA=maxta | | ,RLINKUP=rlinkup |+ ;
|+ + + +|
+ +
9.6 Commands RLLOC, RLLOP, Cell Locating Data
CHANGE
+ + + +
| | sctype | |
RLLOC:CELL=cell |,SCTYPE= + + |
| | ALL | |
+ + + +
+
| + + + +
+ |,BSPWR=bspwr | |,BSTXPWR=bstxpwr |
| + + + +
+
+ + + +
|,BSRXMIN=bsrxmin| |,BSRXSUFF=bsrxsuff |
+ + + +
+ + + +
|,MSRXMIN=msrxmin | |,MSRXSUFF=msrxsuff |
+ + + +
+ + + + + +
|,SCHO=scho | |,MISSNM=missnm | |,AW=aw |
+ + + + + +
+
+ + |
| ,EXTPEN=extpen | + ;
+ + |
+
PRINT
+ +
| cell... |
| |
RLLOP:CELL= + + + + ;
| ALL | ,EXT | |
| + + |
+ +
9.7 Commands RLLUC, Locating Urgeny Data,
CHANGE
+ + + +
| | sctype | |
RLLUC:CELL=cell |,SCTYPE= + + |
| | ALL | |
+ + + +
+
| + + + +
+ |,QLIMUL=qlimul | |,QLIMDL=qlimdl |
| + + + +
+
+
+ + + + |
|,TALIM=talim | |,CELLQ=cellq | +;
+ + + + |
+
9.8 Commands RLLBC, Locating BSC Data,
CHANGE
+
|+ + + +
RLLBC: +| TAAVELEN=taavelen | | ,TINIT=tinit |
|+ + + +
+
+ + + +
| ,TALLOC=talloc | | ,TURGEN=turgen |
+ + + +
+ + + +
| ,EVALTYPE=evaltype | | ,TINITAW=tinitaw |
+ + + +
+ + + +
| ,TALLOCAW=tallocaw | | ,ASSOC=assoc |
+ + + +
+
+ + + +|
| ,IBHOASS=ibhoass | | ,IBHOSICH=ibhosich |+ ;
+ + + +|
+
9.9 Commands RLLFP, Locating FILTER Data
CHANGE
+
|+ + + +
RLLFC:CELL=cell +| ,SSEVALSD=ssevalsd | | ,QEVALSD=qevalsd |
|+ + + +
+
+ + + +
| ,SSEVALSI=ssevalsi | | ,QEVALSI=qevalsi |
+ + + +
+ + + +
| ,SSLENSD=sslensd | | ,QLENSD=qlensd |
+ + + +
+ + + +
| ,SSLENSI=sslensi | | ,QLENSI=qlensi |
+ + + +
+
+ + + +|
| ,SSRAMPSD=ssrampsd | | ,SSRAMPSI=ssrampsi |+ ;
+ + + +|
+
PRINT
+ +
| cell... |
RLLFP:CELL= + + ;
| ALL |
+ +
9.10 Commands RLLHC,RLLHP , Locating Hierarchical Data
CHANGE
+
|+ + + +
RLLHC:CELL=cell +| ,LEVEL=level | | ,LEVTHR=levthr |
|+ + + +
+
+ + + +
| ,LEVHYST=levhyst | | ,PSSTEMP=psstemp |
+ + + +
+
+ +|
| ,PTIMTEMP=ptimtemp |+ ;
+ +|
+
PRINT
+ +
| cell... |
| |
RLLHP:CELL=+ + + + + + ;
| ALL | ,LEVEL=level | | ,EXT | |
| + + + + |
+ +
9.11 Commands RLOLC, RLOLP,Locating Overlaid Subcell

Data
CHANGE
+
| + + + +
RLOLC:CELL=cell + | ,LOL=lol | | ,LOLHYST=lolhyst |
| + + + +
+
+
+ + + + |
| ,TAOL=taol | | ,TAOLHYST=taolhyst | + ;
+ + + + |
+
PRINT
+ +
| cell... |
RLOLP:CELL= + + ;
| ALL |
+ +
9.12 Commands RLLPC, Locating Penalty Data
CHANGE
+
|+ + + +
RLLPC:CELL=cell +| ,PTIMHF=ptimhf | | ,PTIMBQ=ptimbq |
|+ + + +
+
+ + + +
| ,PTIMTA=ptimta | | ,PSSHF=psshf |
+ + + +
+
+ + + +|
| ,PSSBQ=pssbq | | ,PSSTA=pssta |+ ;
+ + + +|
+
9.13 Commands RLIHP, RLIHC, Locating Intracell Handover

Data
PRINT
+ +
| cell... |
RLIHP:CELL= + + ;
| ALL |
+ +
CHANGE
+ + + +
| | sctype | |
RLIHC:CELL=cell |,SCTYPE= + + |
| | ALL | |
+ + + +
+
| + + + +
+ |,IHO=iho | |,MAXIHO=maxiho |
| + + + +
+
+ + + +
|,TMAXIHO=tmaxiho | |,TIHO=tiho |
+ + + +
+ + + +
| | ,SSOFFSETULP=ssoffsetulp | |
| + + |
| | ,SSOFFSETULN=ssoffsetuln | |
+ + + +
+ + + +
| | ,SSOFFSETDLP=ssoffsetdlp | |
| + + |
| | ,SSOFFSETDLN=ssoffsetdln | |
+ + + +
+ + + +
| | ,QOFFSETULP=qoffsetulp | |
| + + |
| | ,QOFFSETULN=qoffsetuln | |
+ + + +
+ + + + +
| | ,QOFFSETDLP=qoffsetdlp | | |
| + + | +;
| | ,QOFFSETDLN=qoffsetdln | | |
+ + + + +
9.13.1 Commands RLURI, RLURP
PRINT
RLURP:MP=mp;
INIT
+ +
| cell... |
RLURI:MP=mp,LVUN=lvun,CELL= + + ,NP;
| ALL |
+ +
9.14 Commands RLPCI, RLPCP, RLPCC , Dynamic MS PWR

Cell Control Data
CELL DATA INIT
RLPCI:CELL=cell;
CELL DATA CHANGE
+ + + +
| | sctype | |
RLPCC:CELL=cell |,SCTYPE= + + |
| | ALL | |
+ + + +
+
|+ + + +
+| ,SSDES=ssdes | | , LCOMPUL=lcompul |
|+ + + +
+
+ + + +
| ,QDESUL=qdesul | | ,INIDES=inides |
+ + + +
+ +
| ,INILEN=inilen |
+ +
+ + + +
| ,PMARG=pmarg | | ,QLEN=qlen |
+ + + +
+ + + +
| ,DTXFUL=dtxful | | ,QCOMPUL=qcompul |
+ + | +
+ + + +
| ,QDESUL=qdesul | | ,REGINT=regint | + ;
+ + + +
CELL DATA PRINT

+ +
| cell... |
RLPCP:CELL= + + ;
| ALL |
+ +
CELL DATA END
RLPCE:CELL=cell;
9.15 Commands RLBCI, RLBCP, RLBCC , Dynamic BTS

PWR Cell Control Data
INIT
RLBCI:CELL=cell;
CHANGE
+ +
| + + |
| | sctype | |
RLBCC:CELL=cell |,SCTYPE= + + |
| | ALL | |
+ + + +
+
|
|+ + + +
+| ,SDCCHREG=sdcchreg | |, REGINTDL =rgeintdl |
|+ + + +
|
+
+ + + +
| ,SSDESDL=ssdesdl | | ,SSLENDL=sslendl |
+ + + +
+ + + +
| ,SSDYNDL=ssdyndl | | ,PWRDYNDL=pwrdyndl |
+ + + +
+ + + +
| ,QLENDL=qlendl | | ,QVALDL=qvaldl |
+ + + +
+ + + +
| ,LCOMPDL=lcompdl | | ,QDESDL=qdesdldl |
+ + + +
+ +
| ,QCOMPDL=qcompdl
+ +
+ + +
| + + | |
| | BSPWRMINP=bspwrminp| | |
|, + + | + ;
| | BSPWRMINN=bspwrminn| | |
+ + + + |
+
PRINT
+ +
| cell... |
RLBCP:CELL= + + ;
| ALL |
+ +
END
RLBCE:CELL=cell;
9.15.1 Commands RLMBI, RLMBC, RLMBP, RLMBP, Cell Broadc. Message
INITIATE
+ +
RLMBI:CELL=cell, ID=id, CODE=code | ,UPDATE=update |
+ +
+ + + + + +
| ,MODE=mode | | ,NUMPAGES=numpages | | ,LANG=lang | ;
+ + + + + +
CHANGE
+ +
RLMBC: CELL=cell, ID=id, CODE=code | ,PAGE=page |
+ +
+ +
,TEXT=text... | ,PNO=pno |;
+ +
PRINT
+ +
| ID=id, CODE=code| + +
RLMBP:CELL=cell,+ + | ,NOTEXT |;
| ID=ALL | + +
+ +
END
+ +
| ID=id, CODE=code |
RLMBE:CELL=cell, + + ;
| ID=ALL |
+ +
9.15.2 Commands RLMTI, RLMTP, Cell Broadcast Distr. Time
INITIATE
RLMTI: CELL=cell, ID=id, CODE=code, SDATE=sdate, STIME=stime
+ +
| ,EDATE=edate, ETIME=etime | ,REP=rep;
+ +
PRINT
+ +
| ID=id, CODE=code |
| |
RLMTP:CELL=cell, + + + + ;
| ID=ALL | ,STATE=state | |
| + + |
+ +
9.16 System Information
9.16.1 Commands RLSSC, RLSSP, System Info SACCH & BCCH Data
CHANGE
+
|+ + + +
RLSSC:CELL=cell +| ,ACCMIN=accmin | | ,CCHPWR=cchpwr |
|+ + + +
+
+ + + +
| ,CRH=crh | | ,DTXU=dtxu |
+ + + +
+ + + +
| ,NCCPERM=nccperm... | | ,RLINKT=rlinkt |
+ + + +
+
+ + + + |
| ,MCBR=mcbr | | ,NECI=neci | + ;
+ + + + |
+
print
+ +
| cell... |
RLSSP:CELL=+ + ;
| ALL |
+ +
9.16.2 Commands RLSBC, RLSBP, System info BCCH Data
CHANGE
+
| + + + +
|+ + | | acc... | |
RLSBC:CELL=cell +| ,CB=cb | | ,ACC= + + |
|+ + | | CLEAR | |
| + + + +
+
+ + + +
| ,MAXRET=maxret | | ,TX=tx |
+ + + +
+ + + +
| ,ATT=att | | ,T3212=t3212 |
+ + + +
+ + + +
| ,CBQ=cbq | | ,CRO=cro |
+ + + +
+
|
+ + + + + + |
| ,TO=to | | ,PT=pt | |ECSC=ecsc | + ;
+ + + + | | |
|
+
PRINT
+ +
| cell... |
RLSBP:CELL=+ + ;
| ALL |
+ +
9.16.3 Commands RLSMC, RLSMP , System Information BCCH Message

Distribution
CHANGE
RLSMC:CELL=cell,SIMSG=simsg...,MSGDIST=msgdist;
PRINT
+ +
| |
| cell... |
RLSMP:CELL= + + + + + + ;
| ALL |,SIMSG=simsg| |,MSGDIST=msgdist| |
| + + + + |
+ +
9.16.4 Commands RLVLI, RLVLC, RLVLP, RLVLE, Sup. of Logical Channels,
INITIATE
RLVLI:CELL=cell..., CHTYPE=chtype;
+ +
RLVLI:CHTYPE=chtype |, SUPSTATE=supstate | ;
+ +
CHANGE
+ +
| PL=pl ,AL=acl` |
RLVLC: CELL=cell..., CHTYPE=chtype, + + ;
| ACL=acl |
+ +
PRINT
RLVLP;
END
RLVLE:CHTYPE=chtype;
+ +
| cell... |
RLVLE:CELL= + +, CHTYPE=chtype;
| ALL |
+ +
9.16.5 Commands RLVAP, RLVAR, Supervision of ALARM,
PRINT
RLVAP;
RESET
RLVAR: CHTYPE=chtype ;
9.16.6 Commands RLSLI, RLSLC, RLSLP, RLSLE, Supervision of Logical

Channels Availability,
INITIATE
+ +
RLSLI:CELL=cell...|,SCTYPE=sctype| ;
+
CHANGE
+ +
+ + |,LVA=lva ,AC=acl` |
RLSLC:CELL=cell...|,SCTYPE=sctype| + +
+ + |,ACL=acl |
+ +
,CHTYPE=chtype;
PRINT
+ +
| cell... |
RLSLP:CELL= + +;
| ALL |
+ +
END
+ + + +
RLSLE:CELL=cell...|,SCTYPE=sctype| |,PERM |;
+ + + +
9.16.7 CELL CONNECTION OF CELL TO CHANNEL ALLOCATION ,

RLHPC/RLHPP
RADIO CONTROL CELL CONNECTION OF CELL TO
CHANNEL ALLOCATION, CHANGE
RLHPC: CELL=cell, CHAP=chap ;
RADIO CONTROL CELL CONNECTION OF CELL TO
CHANNEL ALLOCATION, PRINT
+
+ + |
+ | cell.. | |
| CELL= + | |
| | ALL | |
| + + |
RLHPP: | | ;
| + + |
| | chap...| +
| CHAP= + + |
| | ALL | |
| + + |
+ +
9.16.8 CELL IDLE CHANNEL MEASUREMENT CHANGE,

RLIMC/RLIMI/RLIMP
RADIO CONTROL CELLIDLE CHANNEL MEASUREMENT, CHANGE
+
| + + + + + +
RLIMC : CELL= cell + |, INTAVE=intave | |,LIMIT1= limit1 | |, LIMIT2= limit2 |
| + + + + + +
+
+
+ + + + |
|, LIMIT3= limit3 | |, LIMIT4= limit4 | |;
| + + + |
RADIO CONTROL CELLIDLE CHANNEL MEASUREMENT, INIT
+ +
RLIMI: CELL=cell |, NOALLOC | ;
+ +
RADIO CONTROL CELLIDLE CHANNEL MEASUREMENT, PRINT
+ +
| cell.. |
RLIMP : CELL= + |
| ALL |
+ +
RADIO CONTROL CELLIDLE CHANNEL MEASUREMENT, END
RLIMI: CELL=cell ;
9.16.9 CELL LOAD SHARING DATA , RLLCC/RLLCE/RLLCP
RADIO CONTROL CELL LOAD SHARING DATA , CHANGE
+
| + + + +
RLLCC: CELL= cell + | CLSLEVEL= clslevel | | , CLSACC=clsacc |
| + + + +
+
|
+ + |
|, HOCLSACC=hoclasac | | ;
+ + |
+
RADIO CONTROL CELL LOAD SHARING DATA , PRINT
+ +
| cell.. |
RLLCP : CELL= + |
| ALL |
+ +
RADIO CONTROL CELL LOAD SHARING DATA , INIT
RLLCI : CELL= cell...;
RADIO CONTROL CELL LOAD SHARING DATA , END
RLLCE : CELL= cell...;
9.16.10 BSC LOAD SHARING DATA , RLLSI/RLLSE/RLLSP
RADIO CONTROL CELL BSC LOAD SHARING , END
RLLSE ;
RADIO CONTROL CELL BSC LOAD SHARING , INTI
RLLSI ;
RADIO CONTROL CELL BSC LOAD SHARING , PRINT
RLLSP ;
9.16.11 CELL BSC BAND OPERATING MODE CHANGE, RLOMC/RLOMP
RADIO CONTROL CELL BSC BAND OPERATING MODE, CHANGE
RLOMC:MODE= mode ;
RADIO CONTROL CELL BSC BAND OPERATING MODE, PRINT
RLOMP;
9.16.12 CELL BSC DIFF. CHANN. ALLOC. PRIO. PROFILE,

RLLPPC/RLLPI/RLLPE
RADIO CONTROL CELL BSC DIFFERENTIAL CHANNEL ALLOCATION
PRIORITY PROFILE, CHANGE
+ +
| + + + + |
RLPPC : PP= pp, PRL=prl + |, PRL= prl | |, PROBF= probf | | ;
| + + + + |
+ +
PRIORITY PROFILE, END
RLLPE :PP =pp ;
+ +
PRIORITY PROFILE, PRINT
+ +
| pp.. |
RLPPP : PP= + |
| ALL |
+ +
PRIORITY PROFILE, INIT
RLLPI :PP =pp ;
PRIORITY PROFILE, print
+ +
| pp.. |
RLLPP : PP= + |
| ALL |
+ +
9.16.13 CELL BSC DIFF. CHANN. ALLOC. PRIO. TO RESOURCE TYPE ,

RLPRC/RLPRI/RLPRP
TO RESOURCE TYPE, CHANGE
+ +
RLPRC: CELL=cell |, SCTYPE=sctype | , CHTYPR= chtype, PP=pp ;
+ +
TO RESOURCE TYPE, PRINT
+
+ + |
+ | pp.. | |
| PP= + | |
| | ALL | |
| + + |
RLPRP: | | ;
| + + |
| | chap...| + + |
| CELL= + + |, CHTYPE=chtype | |
| | ALL | + + |
| + + |
+ +
9.16.14 CELL BSC DIFF. CHANN. ALLOC. STATISTICS,

RLSCE/RLSCE/RLSCP/RLDSP
STATISTICS COLLECTION , END
RLSCE ;
STATISTICS COLLECTION , INIT
RLSCI:STATSINT= statsint ;
STATISTICS COLLECTION , PRINT
RLSCP ;
STATISTICS DATA, PRINT
+ +
| cell.. | + +
RLSDP : CELL= + | |, IO=io | ;
| ALL | + +
+ +
9.17 RCS fault codes

9.17.1 Fault Codes in Numerical Order
1. CELL ALREADY DEFINED
It is not allowed to define the same cell several times. A new cell designation must be given.
2 BTS EQUIPMENT DEDICATED TO CELL
A managed object in the BTS is dedicated for use in this cell. An MO is identified in details.
Use command RXMOC to remove the dedication.
3 CELL NOT DEFINED
4 CELL STATE NOT HALTED
5 SUPERVISION OF LOGICAL CHANNELS IS DEFINED
6 NCCPERM NOT DEFINED
The parameter NCCPERM has to be defined before activating the cell. Use the command
RLSSC to define NCCPERM.
7 CELL AND CELLR MUST NOT BE SAME
It is not allowed to use the same names for both CELL and CELLR. It is not possible for a cell
to be its own neighbour.
8 CGI IS NOT UNIQUE
The CGI is already used for another cell. It must be unique.
9 CELLR NOT DEFINED
10 NUMBER OF CELL RELATIONS EXCEEDED
It is only allowed to define up to 64 neighbours belonging to one cell.
11 MAXIMUM NUMBER OF CELL RELATIONS IN BSC EXCEEDED
The cell relation file in the BSC is full. It is only allowed to define up to 4096 relations in the
BSC.
12 CHANNEL GROUP ALREADY DEFINED
The channel specified in details is already defined for the cell.
13 LAI NOT DEFINED
The Location Area Identification is not defined.
14 MBCCHNO ALREADY GIVEN
The measurement frequency has already been given.
15 ACC ALREADY GIVEN
The same Access Control Class has already been given.
16 NCCPERM ALREADY GIVEN
The same PLMN Colour Code permitted has already been given.
17 MISMATCH BETWEEN AGBLK AND BCCHTYPE
The parameters COMB/COMBC cannot be given if the parmater AGBLK has already been
defined with too large a value. See parameter range values.
18 END DATE NOT GREATER THAN START DATE
EDATE is not greater than SDATE or EDATE equal to SDATE and ETIME is not greater than
STIME.
19 CELL RESOURCES HAVE CHANGED
Cell Resources have changed since printout started.
20 MBCCHNO EXCEEDS VALUE RANGE
It is only allowed to specify measurement frequencies with a value range of maximum 278 per
cell if the Global system type is PCS 1900 or DCS 1800. If the Global system type is MIXED
and the Cell system type is GSM the maximum value range is 256 for the other band.
21 MAXIMUM NUMBER OF MBCCHNO EXCEEDED
It is only allowed to define up to 32 measurement frequencies in a list. If the Global system

type is MIXED and the Cell system type is GSM it is only allowed to define up to 22
measurement frequencies in the other band.
22 SEIZURE SUPERVISION OF LOGICAL CHANNELS IS DEFINED
The cell cannot be deleted due to seizure supervision of logical channels. Seizure supervision
must be disconnected using the command RLVLE.
23 CELL IS CONNECTED TO TG
The cell cannot be deleted due to TG connection. A TG is identified in details. The connection
to the transceiver group must be removed using the command RXTCE.
24 FREQUENCY NOT CONNECTED TO CELL
Invalid DCHNO parameter.
25 CHANGING TO EXISTING STATE
26 NO TG CONNECTED
No transceiver group is connected to the cell or channel group.
27 CELL DATA CHANGE IN PROGRESS
Modification of cell data by a command is in progress.
28 RF CHANNEL NUMBER ALREADY USED
The absolute RF channel number is already used for another channel type.
29 STATISTICS COLLECTION IN PROGRESS
The differential channel allocation statistics collection is ON. The Command RLSCE may used
to end the differential channel allocation statistics collection.
30 SIZE ALTERATION EVENT SAE=0 NOT PERFORMED
Individuals are not defined in LOAS. This must be done before the paging function can request
processor capacity. At least one individual must be defined.
31 MBCCHNO NOT DEFINED
The measurement frequency is not defined in the cell.
32 RELATION ALREADY EXISTS
The given relation already exists. The command RLNRE may be used to delete the existing
relationship.
33 CELL RELATION NOT DEFINED
34 BSPWRB VALUE NOT SUPPORTED
The given BSPWRB value is not supported by the BTS.
35 BSPWRT VALUE NOT SUPPORTED
The given BSPWRT value is not supported by the BTS.
36 CBCH REQUIRES AN SDCCH
It is not allowed to specify CBCH = yes for a channel group where SDCCH = 0.
36 MEASURING PROGRAM NOT DEFINED FOR THIS FUNCTION
No measuring program with specified number is defined in this function.
37 RF CHANNEL NUMBER OUT OF RANGE
38 COMMAND NOT VALID FOR EXTERNAL CELLS
39 MSRXSUFF NOT DEFINED
40 MSRXMIN NOT DEFINED
41 BCCHNO NOT DEFINED
42 BSIC NOT DEFINED
43 BSPWR NOT DEFINED
44 BSPWRB NOT DEFINED
The parameter BSPWRB has to be defined before activating the cell. Use the command
RLCPC to define BSPWRB.
45 BSPWRT NOT DEFINED
The parameter BSPWRT has to be defined before activating the cell. Use the command
RLCPC to define BSPWRT.
46 BSTXPWR NOT DEFINED
47 CCHPWR NOT DEFINED
The parameter CCHPWR has to be defined before activating the cell. Use the command
RLSSC to define CCHPWR.
48 CGI NOT DEFINED
49 DTXU NOT DEFINED
The parameter DTXU has to be defined before activating the cell. Use the command RLSSC to
define DTXU.
50 UNDEFINED NEIGHBOURING CELLS RECORDING IS ACTIVE
The cell cannot be deleted due to undefined neighbouring cells recording for the cell.
Undefined neighbouring cells recording must be stopped using the command TRTSE.
51 MSTXPWR NOT DEFINED
52 CHANNEL TYPE NOT VALID FOR SUBCELL TYPE
The specified channel type can not exist in the specified subcell type.
53 SIMSG ALREADY GIVEN
The same System Information message has already been given.
54 NOT ALL CHANNEL GROUPS CAN BE ACTIVATED
Not all channel groups can be activated. Give the command again, specifying channel groups
separately.
55 TRANSCEIVER TEST EQUIPMENT IS DEFINED
The cell cannot be deleted due to transceiver test equipment being defined in the cell. Use
command RATTE to delete the transceiver test equipment.
56 SUPERVISION IS ACTIVE
Supervision is active for current channel type. Before a new cell can be added/removed, the
supervision must be passive. Action: Use RLVLP for printout of seizure supervision of logical
channels data.
57 INCORRECT ALARM LIMIT VALUE SPECIFIED
Alarm limit greater than the maximum possible number of channels of this type in the cell.
58 BSRXSUFF NOT DEFINED
59 BSRXMIN NOT DEFINED
60 PRIORITY PROFILE NOT DEFINED
The priority profile is not defined. The command RLPPI may be used to define the priority
profile.
61 SUPERVISION IS ALREADY CONNECTED
62 SUPERVISION IS ALREADY DISCONNECTED
63 SUPERVISION IS ALREADY PERMANENTLY DISCONNECTED
Supervision is already permanently disconnected.
64 PARAMETER NOT VALID FOR FILTER TYPE
The filter length and ramping length parameters are only valid when corresponding filter types
are not FIR filters ie. evaluation selection parameter must be greater than 5.
65 RELATION MUST BE SINGLE WHEN CELLR IS EXTERNAL
The relation to an external cell must be SINGLE as it is not possible to alter data in another
BSC.
66 BSTXPWR NOT DEFINED FOR OVERLAID SUBCELL
67 PARAMETER CS NOT VALID FOR EXTERNAL CELLR
Paramter CS may not be used if CELLR is an external cell.
68 CBCH NOT VALID FOR SCTYPE OVERLAID
CBCH is not valid for channel groups belonging to overlaid subcells.
69 MSTXPWR NOT DEFINED FOR OVERLAID SUBCELL
70 LOL NOT DEFINED FOR OVERLAID SUBCELL
71 TAOL NOT DEFINED FOR OVERLAID SUBCELL
72 DISTRIBUTION IS ACTIVE
Distribution times for the message are already defined. This can be removed, along with the
message using command RLMBE.
73 BSPWRT NOT DEFINED FOR OVERLAID SUBCELL
74 PRAMETER NOT VALID FOR CELL LEVEL
Parameters LEVHYST, LEVTHR, PTIMTEMP and PSSTEMP are not valid for umbrella level
cells.
75 PARAMETER NOT VALID FOR EXTENDED RANGE CELL
76 COMMAND NOT VALID FOR EXTENDED RANGE CELLS
The command must not be used for extended range cells.
77 GLOBAL SYSTEM TYPE ALREADY INITIATED
Global system type is already initiated.
78 CELLS DEFINED IN THE BSC
One or more cells are defined in the BSC. The system type parameter can not be removed when
cells are defined.
79 NO GLOBAL SYSTEM TYPE INITIATED
80 SUPERVISION CANNOT BE DISCONNECTED WHEN ALARM IS ISSUED
Supervision cannot be disconnected until the alarm has been reset.
81 GSM PHASE 2 FUNCTIONALITY NOT SUPPORTED
The command is only valid for cells which are connected to BTS equipment which supports
GSM phase 2 System Information.
82 ALARM CLASS CANNOT BE CHANGED, ALARM ISSUED
Alarm class may not be changed while an alarm is issued on specified channel type and cell.
83 INVALID TIME PERIOD SPECIFIED
Specified period length not within the limits.
84 NO ALARM GIVEN
Alarm resetting ordered but no alarm had been given.
85 PARAMETER NOT ALLOWED FOR CELLS WITH SUBCELL STRUCTURE
The parameter is not allowed for a cell with a subcell structure.
86 SUBCELL STRUCTURE NOT DEFINED
86 SUBCELL STRUCTURE IS NOT DEFINED
A subcell type must not be specified in this command if a subcell structure is not defined for
the cell.
87 SUBCELL STRUCTURE IS DEFINED
88 CHANNEL GROUP CONTAINS CONTROL CHANNELS
Channel groups containing BCCH or CBCH channels cannot be moved to the overlaid subcell.
89 TALIM VALUE NOT ALLOWED
The value of TALIM defined is only valid for an extended range cell.
90 CHANNEL GROUP CONNECTED TO TG
Channel groups must be disconnected from the TG before deletion. Action: Use command
RXTCE to disconnect the channel group from the TG.
91 BCCH FREQUENCY NOT ALLOWED
It is not possible to remove the BCCH frequency channel with this command.
92 MAXIMUM NUMBER OF SDCCH/CBCH ALREADY DEFINED
The maximum number of SDCCH and/or CBCH are already defined for this cell.
93 DESIGNATED TN IS FULL
Insufficient frequencies are available to support the specified SDCCH within the channel
group.
94 MAXTA VALUE NOT ALLOWED
The value of MAXTA defined is only valid for an extended range cell.
95 RP ACTION NOT COMPLETE
Not enough pages due to deletion of messages. Try later (after 5 seconds).
96 CHGR NOT DEFINED
97 TN VALUE NOT ALLOWED
The time slot number specified is not valid for a cell which has been defined as an extended
range cell.
98 MAXIMUM NUMBER OF CHGR DEFINED
99 MAXIMUM NUMBER OF DCHNO DEFINED
The maximum number of RF channels is defined for this cell or channel group.
100 DCHNO IS DEFINED WITHIN A CHANNEL GROUP
The absolute RF channel number is assigned to a CHGR within the cell.
101 CHANNEL GROUP 0 CANNOT BE REMOVED WITH THIS COMMAND
Channel group 0 cannot be removed with this command. The default channel group is removed
at cell deletion.
102 PARAMETER NOT VALID FOR SUBCELL TYPE
103 SUBCELL STRUCTURE ALREADY DEFINED
The cell already has a subcell structure defined.
104 PARAMETER NOT VALID FOR INTERNAL CELLS
EXTPEN must not be specified for internal cells.
105 PARAMETER NOT VALID FOR EXTERNAL CELLS
106 CHANNEL GROUP NOT HALTED
107 MAXIMUM NUMBER OF INTERNAL CELLS DEFINED
The internal cell file is full. Use size alteration event number 298 to increase the size of the file.
108 MAXIMUM NUMBER OF EXTERNAL CELLS DEFINED
The external cell file is full. Use size alteration event number 299 to increase the size of the
file.
109 MESSAGE ALREADY DEFINED
The same combination of message id and message code must not be used more than once
within a cell.
110 MAXIMUM NUMBER OF PAGES PER CELL EXCEEDED
The limit of 15 pages per cell has been exceeded. Existing messages may be removed by the
command RLMBE.
111 MESSAGE NOT DEFINED
112 PAGE NUMBER NOT ALLOWED
The page number must not be greater than the parameter NUMPAGES in command RLMBI.
113 PAGE NUMBER MISSING
The page number must be given as this message is a multipage one.
114 INCORRECT PACKAGE NUMBER
If a message is to be entered in two parts the first part must be entered first. Then the second
part must be specified as package number 2.
115 INCORRECT TEXT TYPE
The text type must be as defined by the parameter MODE in command RLMBI.
116 MESSAGE TEXT TOO LONG
If the MML text mode is used a maximum of 93 characters are permitted.
117 MESSAGE NOT FULLY DEFINED
The message is not fully defined. A page or package is yet to be entered The command
RLMBC can be used to define message text.
118 START DATE HAS PASSED
The start DATE and/or TIME has passed.
119 MESSAGE DISTRIBUTION FINISHED
Message text cannot be altered as distribution time has ended.
120 CELL STATE NOT ACTIVE
The cell has not been activated. The command RLSTC may be used to activate the cell.
121 CHANNEL GROUP ALREADY IN SUBCELL
The channel group is already allocated to the subcell type specified.
122 CHANNEL GROUP 0 IS NOT ACTIVE
Channel group 0 is not active. Give command RLSTC again and specify channel group 0.
123 CHANNEL GROUPS OTHER THAN 0 EXIST
Parameter CHGR must be specified when channel groups other than channel group 0 exist.
Action: Re-issue the command specifying the desired channel group.
124 FREQUENCY NOT CONNECTED TO CHANNEL GROUP
Frequency not connected to channel group. Command RLCFI may be used to connect a
frequency to the channel group.
125 OVERLAID SUBCELL CONTAINS CHANNEL GROUPS
The subcell structure cannot be removed until the channel groups in the overlaid subcell are
removed. Command RLDGC can be used to move a channel group to the underlaid subcell or
RLDGE will delete the channel group.
126 FREQUENCY REQUIRED FOR CONTROL CHANNELS
It is not possible to remove the RF channel specified, as it is required to support the control
channels in its channel group.
127 COUNTER FILE FOR INTERNAL NEIGHBOUR CELL IS FULL
The file holding handover counter data for relations where the neighbour cell is internal is full.
Increase the file with size alteration event SAE=522.
128 COUNTER FILE FOR EXTERNAL NEIGHBOUR CELL IS FULL
The file holding handover counter data for relations where the neighbour cell is external is full.
Increase the file with size alteration event SAE=523.
129 PRIORITY PROFILE IS CONNECTED TO RESOURCE TYPES
It is not allowed to delete a priority profile while resources are connected to it. These may be
connected to other priority profiles using the command RLPRC.
130 PRIORITY PROFILE ALREADY DEFINED
It is not allowed to define the same priority profile several times. A new priority profile
designation must be given.
131 GSM PHASE IS NOT KNOWN
BCCH is not created and deblocked.
132 RECORDING ALREADY IN PROGRESS
Too late to give more RLURI-commands when a TRTSI-command has been given to the time
supervision function.
133 MEASURING PROGRAM ALREADY OCCUPIED
The specified measuring program identity has already been occupied.
134 RECORDING ALREADY INITIATED FOR ORDERED CELL
Ordered cell has already been given in an earlier command.
135 MEASURING PROGRAM MUST BE THE SAME AS IN PREVIOUS COMMAND
If several RLURI-commands are given the measuring program number must be the same.
136 NO CELLS DEFINED
No cells have been defined in the BSC.
137 CELL = ALL NOT ALLOWED WHEN COMMAND ALREADY GIVEN
Cell = ALL can only be given in the first RLURI-command.
138 NO CELLS DEFINED OF SPECIFIED SYSTEM TYPE
There are not cells defined of the specified system type.
139 FUNCTION IS ALREADY ACTIVATED
The Load Sharing function is already activated.
140 FUNCTION IS ALREADY DEACTIVATED
The load sharing function is already deactivated.
141 GLOBAL SYSTEM TYPE IS NOT MIXED
The command is only valid for mixed global system type. The global system type can be
changed by command RLTYC.
142 TOO MANY ARGUMENTS
Too many cell designations specified in the command.
143 GLOBAL SYSTEM TYPE IS MIXED
The global system type is MIXED. Parameter CSYSTYPE must be used to set the cell system
type.
144 CSYSTYPE NOT IN ACCORDANCE WITH THE GLOBAL SYSTEM TYPE
Parameter CSYSTYPE was given a value conflicting with the global system type. The global
system type is not MIXED. Command RLTYC may be used to change the global system type.
145 CHANNEL EVENT RECORDING IS ACTIVE
The cell cannot be deleted due to channel event recording for the cell. Channel event recording
must be stopped using the command RACEE.
146 CELL(S) WITH ANOTHER CSYSTYPE EXISTS
The Global system type does not match with the cell system type in one or more cells.
147 ICM INITIATED IN CELL
Idle Channel Measurement is already initiated in the cell.
148 LIMITS MUST ASCEND
Idle channel interference limits must be in ascending order.
149 SYSTYPE NOT IN ACCORDANCE WITH GSYSTYPE
The given system type is not in accordance with the global system type.
150 SUPERVISION IS PASSIVE
Supervision is already passive for the specified channel type.
151 CELL(S) WITH WRONG MEASUREMENT FREQUENCY BANDS EXISTS
Cell(s) with measurement frequencies in bands other than the global system type exists.
152 MAXIMUM NUMBER OF PRIORITY PROFILES DEFINED
Maximum number of priority profiles is already defined for the BSC.
153 DEFAULT PRIORITY PROFILE NOT VALID
It is not allowed to change the data in the default priority profile or to delete it or to use it as a
name for defining a new priority profile.
154 ICM ALREADY PASSIVE
Idle channel measurement is already passive in this cell.
155 BSC MULTI BAND OPERATION MODE IS ENABLED
The BSC MULTI BAND OPERATION MODE must be disabled for a global system type
which is not mixed.
10 Translation between the ABIS O&M IWD

and BSC command parameters
10.1 BTS logical model G01
ABIS O&M IWD | BSC Command | BSC

parameters | Parameters | Commands
----------------------+-------------------------+---------
BCC VALUE | bcc, part of BSIC | RLDEC
| |
BS_AG_BLKS_RES | AGBLK | RLDEC
| |
BSIC | BSIC | RLDEC
| |
BS_PA_MFRMS | MFMRS | RLDEC
| |
CBCH INDICATOR | CBCH, Identifier | RLCCC
0 = No CBCH | NO |
1 = CBCH | YES |
| |
COMBINATION | BCCHTYPE, Identifier | RLDEC
05 = BCCH Combined | COMB, COMBC |
04 = BCCH Not Comb. | NCOMB |
| |
03 = SDCCH | SDCCH | RLCCC
| |
EXTENDED RANGE | XRANGE, Identifier | RLDEC
INDICATOR | |
1 = Extended Range | Yes |
0 = Normal | No |
| |
FILE TRANSFER TYPE | | RXPLI
00 = Conditional | UC not specified |
01 = Unconditional | UC specified |
| |
FN OFFSET | FNOFFSET | RLDEC
| |
FREQUENCY LIST,ARFCN | BCCHNO | RLDEC
| DCHNO | RLCFI
| |
FREQUENCY SPECIFIER | BCCHNO | RLDEC
| DCHNO | RLCFI
| HOP | RLCHC
| |
HSN | HSN | RLCHC

----------------------+-------------------------+---------
ICM BOUNDARY | LIMIT1, | RLIMC
PARAMETERS | LIMIT2, |
| LIMIT3, |
| LIMIT4, |
| INTAVE |
| |
ICM INDICATOR | No parameter, set by | RLIMI,
| the commands themselves | RLIME
0 = ICM off | RLIME |
1,2 = ICM on | RLIMI |
| |
POWER | BSPWRB, BSPWRT | RLCPC
| |
RECEIVER DIVERSITY | RXD, Identifier | RXMOC,
01 = Receiver B | B | RXMOI
02 = Receiver A | A |
03 = Receiver A+B | AB |
| |
T3105 | RLINKT | RLSSC
| |
TEI VALUE | CTEI | RXMOC,
| | RXMOI
| |
TF MODE | TFMODE, Identifier | RXMOC,
00 = Master | M | RXMOI
01 = Standalone | SA |
02 = Slave | S |
| |
TIME SLOT NUMBER | TN | RLCCC
| |
TSC | TSC | RLDTC
| bcc, part of BSIC | RLDEC
10.2 BTS Logical Model G12

----------------------+-------------------------+---------
BCC | bcc, part of BSIC | RLDEC
| |
BS_AG_BLKS_RES | AGBLK | RLDEC
| |
BSIC | BSIC | RLDEC
| |
BS_PA_MFRMS | MFMRS | RLDEC
| |
CBCH INDICATOR | CBCH, Identifier | RLCCC
0 = No CBCH | NO |
1 = CBCH | YES |
| |
COMBINATION | BCCHTYPE, Identifier | RLDEC
05 = BCCH Combined | COMB, COMBC |
04 = BCCH Not Comb. | NCOMB |
| |
03 = SDCCH | SDCCH | RLCCC
| |
CELL NAME | CELL | Used by a
| | large
| | number of
| | commands,
| | for
| | example
| | RLDEC
| |
EXTENDED RANGE | XRANGE, Identifier | RLDEC
INDICATOR | |
1 = Extended Range | Yes |
0 = Normal | No |
| |
FN OFFSET | FNOFFSET | RLDEC
| |
FREQUENCY LIST,ARFCN | BCCHNO | RLDEC
| DCHNO | RLCFI

----------------------+-------------------------+---------
FREQUENCY | BCCHNO | RLDEC
SPECIFIER RX | DCHNO | RLCFI

| HOP | RLCHC
| |
FREQUENCY | BCCHNO | RLDEC
SPECIFIER TX | DCHNO | RLCFI
| HOP | RLCHC
| |
HSN | HSN | RLCHC
| |
ICM BOUNDARY | LIMIT1, | RLIMC
PARAMETERS | LIMIT2, |
| LIMIT3, |
| LIMIT4, |
| INTAVE |
| |
ICM INDICATOR | No parameter, set by | RLIMI,
| the commands themselves | RLIME
0 = ICM off | RLIME |
1,2 = ICM on | RLIMI |
| |
IS CONNECTION LIST | DCP1 and DCP2 | RXMOC,
| | RXMOI
| DCP | RXAPI
| |
N1 | N1 | DTQSC
| |
N3 | N3 | DTQSC
| |
N4 | N4 | DTQSC
| |
POWER | BSPWRB, BSPWRT | RLCPC
| |
RECEIVER DIVERSITY | RXD, Identifier | RXMOC,
01 = Receiver B | B | RXMOI
02 = Receiver A | A |
03 = Receiver A+B | AB |
| |
S BITS SETTING | SBITS | DTIDC
| |
T3105 | RLINKT | RLSSC
| |
TF MODE | TFMODE, Identifier | RXMOC,
00 = Master | M | RXMOI
01 = Standalone | SA |
02 = Slave | S |
| |
TIME SLOT NUMBER | TN | RLCCC
| |
TSC | TSC | RLDTC
| bcc, part of BSIC | RLDEC

A Quick Ref For Commandhandling

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

A Quick Ref For Commandhandling

Caricato da

Copyright:

Formati disponibili

A Quick Ref for commandhandling of the APT 210 09 R7 (CMER6.

1/BSC_POLO) Page 1 of 132

A QUICK REF FOR COMMANDHANDLING

5.2.1 Comand parameter, alphabetical order

LHS ANT 239 03 =R1

RCS ANT 240 06 =R1

TAS ANT 241 06 =R1

ROS ANT 248 04 =R1

RTS ANT 242 01 =R1

This document is stored in DELTA:

2 Managed object handling

2.2 Managed Object Specific Properties

2.3 Operation and Maintenance Communication

4 Radio Transmission Subsystem, RTS

RADIO TRANSMISSION DEVICE SOFTWARE UNIT, LOAD

RADIO TRANSMISSION DEVICE SOFTWARE UNIT,

4.1.2 TRA Pool handling (RRTPC/RRTPE/RRTPI/RRTPP)

RADIO TRANSMISSION TRANSCODER POOL

4.1.3 TRA Pool Mean Hold Supervision handling (RRMSE/RRMSI/RRMSP)

RADIO TRANSMISSION TRANSCODER POOL MEAN HOLD SUPERVISION

4.1.4 TRA Pool Mean Hold Supervision Alarm Handling (RRMAP/RRMAR)

4.1.5 TRA Pool Idle Supervision Handling (RRISE/RRISI/RRISP)

4.1.6 Manual blocking/deblocking TRA devices (RRTBI/RRTBE)

4.1.7 Line level handling (RRLLC/RRLLP)

Line level, Change

Line level Print

4.1.8 TRH LOAD (RA-HII/HDC/HDP/HHP/HTP/HPP/HLC/HAR/HEP)

TRH LOAD DISTRIBUTION IMMEDIATE , PRINT

TRH LOAD DISTRIBUTION DISTRIBUTION PERIODIC, INITIATE

TRH LOAD MONITORING AND DISTRIBUTION DATA , CHANGE

TRH LOAD MONITORING AND DISTRIBUTION DATA , PRINT

TRH LOAD LOAD TABLE, PRINT

TRH DEVICE LOAD TABLE, PRINT

TRH LOAD PERIODIC DISTRIBUTION STATE, PRINT

TRH LOAD TRESHOLD DATA , PRINT

TRH LOAD TRESHOLD DATA , CHANGE

TRH LOAD TRESHHOLD EXCEEDED, RESET

TRH EVENT LOG PRINT

4.2 RTS command parameter information

4.2.1.1 ACL - Alarm Class

ACL=acl Specifies the type of alarm to be isued

DEV=dev Transcoder multiplexed (MUX) device to be blocked.

Format is of the type "devicetype-individual";

4.2.1.3 DLN Dwnlink negative Line Level

DLN=dln Downlink negative Line Level

4.2.1.4 DLP Dwnlink positive Line Level

DLP=dlp Downlink positive Line level

FORCE Force Adjustment

4.2.1.6 LIM1 - Limit 1

4.2.1.7 LIM2 - Limit 2

4.2.1.8 MHTLIM - Mean Hold Time Limit

MHTLIM Mean Hold Time

4.2.1.9 PRINTDEV - Print Devices

4.2.1.10 RNOTRA - Required number of transcoder resources

4.2.1.11 TRAPOOL, Transcoder Pool

TRAPOOL=trapool Identifier 1 - 7 characters.

4.2.1.12 SNT - Switching Network Terminal

SNT=snt Switching network terminal associated with the

4.2.1.13 SUID- Software Unit Identity

SUID=suid Software Unit Identity

4.2.1.14 SUNAME-Software Unit Name

Software Unit Identity