Nokia Siemens Networks

GSM/EDGE BSS, rel.

RG10(BSS), operating
documentation, issue 05

Reference

TRXSIG Monitoring
DN00216433
Issue 4-0
Approval Date 03/02/2009 00:00:00

TRXSIG Monitoring

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2010. All rights reserved

Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment.
Some of the parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal
injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected
has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen und Sachschden fhren.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die
Anlagen installiert und wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene
Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.

Id:0900d805805a2a10

DN00216433
Issue 4-0

TRXSIG Monitoring

Table of Contents
This document has 21 pages.
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

DN00216433
Issue 4-0

Overview of TRXSIG Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

TRXSIG Monitoring - command descriptions. . . . . . . . . . . . . . . . . . . . . . 8

Id:0900d805805a2a10

TRXSIG Monitoring

Id:0900d805805a2a10

DN00216433
Issue 4-0

TRXSIG Monitoring

Summary of changes

Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes made between issues 4-0 and 3-0
In chapter TRXSIG Monitoring - command descriptions, section O - OUTPUTS: under
Syntax, BTS_ID has been changed to (1 - 3000).
Changes made between issues 3-0 and 2-0
The following changes have been made to the chapter TRXSIG Monitoring - command
descriptions:

In Parameter explanations, TRX identification value range has been changed to 1 to

24.
In the section M - START MONITORING: the execution printout of command
example M has been updated.
In the section O - OUTPUTS: under Syntax, BTS_ID has been changed to (1 - 2000)
and TRX_ID to (1 - 24).

Changes made between issues 2-0 and 1-0

The document has been revised throughout to comply with the latest documentation
standards.
The name of the document has been changed from TGMONI to TRXSIG Monitoring.
Execution printouts in chapter two have been updated.

DN00216433
Issue 4-0

Id:0900d805805a2a07

Overview of TRXSIG Monitoring

TRXSIG Monitoring

1 Overview of TRXSIG Monitoring

The TRXSIG Monitoring is a service terminal extension that can be used in the DX 200
BSC.
The TRXSIG Monitoring commands are used for monitoring and decoding the Abis
telecom interface messages between the BSC and the base transceiver stations
(BTSs). The messages are encoded according to the GSM ETSI interface specifications.
TRXSIG Monitoring can monitor two different kinds of telecom messages, Abis
messages and system information messages (the default is both). You can also set
transparent and non-transparent monitoring on (the default is both). The messages are
encoded according to these different notations:

T (Type only, fixed length, only element identifier included),

V (Value only, fixed length, no element identifier included),
TV (Type and Value, fixed length, element identifier included), and
TLV (Type, Length and Value, variable length, element identifier and length indicator included, total length of information element, for variable length, lower and upper
limits).

TRXSIG Monitoring outputs the messages to the service terminal in a decoded form.
You can also set different trigger methods for messages according to the monitored
TRX_id.
By default, the messages are output to TERMINAL, but you can also direct the output
into the unit memory.
Using TRXSIG Monitoring service terminal extension
You can access TRXSIG Monitoring either via the actual service terminal in the Operation and Maintenance Unit (OMU) of the BSC or via the MML terminal (with the ZDDS;
command).
When using the extension for the first time, you have to link it to the service terminal of
the OMU with the command ZLE. You need to give the following parameters:

the character to be used for the extension, and

the naming characters of the module containing the extension.

In these instructions, the letter 1 is used as the name of the extension. The name of the
extension module is TGM_BXSX. Thus, the installation command is the following:
ZLE:1,TGM_BXSX;
TRXSIG Monitoring operates in the Operation and Maintenance Unit (OMU) of the BSC
and includes the following commands:
M START MONITORING This command monitors, decodes, and outputs Abis
telecom messages in the terminal or saves them in the memory buffer
according to the mode you have defined.
T EXCLUDING

With this command you can define excluded messages. Some

messages are set to be excluded by default. See the output command
for those messages.

Id:0900d805805a2a0a

DN00216433
Issue 4-0

TRXSIG Monitoring

Overview of TRXSIG Monitoring

T TRIGGERING This command starts monitoring in a specific link when the message
you have defined has arrived to monitoring.
F FILTERING

This command filters the messages you have defined in monitoring.

O OUTPUTS

This command monitors, decodes, and outputs the Abis telecom

messages from the memory buffer. Outputs also include excluded messages, the trigger table, the filter table, and the message types output
command.
You can interrupt the output by pressing CTRL-C.

Related topics
Service Terminal

DN00216433
Issue 4-0

Id:0900d805805a2a0a

TRXSIG Monitoring - command descriptions

TRXSIG Monitoring

2 TRXSIG Monitoring - command descriptions

?
M
E
T
F
O
Z

.....
.....
.....
.....
.....
.....
.....

MENU / HELP
START MONITORING
EXCLUDING
TRIGGERING
FILTERING
OUTPUTS
EXIT

M - START MONITORING
Function

Use the command M to start the monitoring and decoding of the Abis telecom messages.
TRXSIG Monitoring ensures the existence of the given BCFs/TRXs from the BSS Radio
Network Configuration Database.
You can stop monitoring by pressing CTRL-C. If messages are monitored into the
memory and it is filled up, the computer stops the monitoring. First <one> character of
<message mode>, <trans mode> or <process> identifies the value.

Syntax

Parameter explanations

Z1M:BTS_ID
MSG
TP/NP
PRB
OUT

[-TRX_ID]...:
= <message mode>:
= <trans mode >:
= <process
>:
= <TERM/<pointer[,end] >:;

BTS identification BTS_ID

The identification of the monitored base station function. The possible values range from
1 up to the maximum number of BTSs. You can give multiple BTSs by using the characters & and &&. The parameter is obligatory.
Note that the maximum number of simultaneously monitored telecom links is 128.
Therefore, you cannot monitor all the defined BTSs in a large configuration at the same
time.
TRX identification TRX_ID
The identification of the monitored TRX in the BTS. Possible values range from 1 to 24.
If a value is not given, all the existing TRXs under the BTS are monitored. The parameter
is optional.
message mode MSG
The mode of the message output. The possible values are:
H(EADER) ...... Only the header of the message is printed
I(SYS INFO) ...... Only system information messages
L(3) ...... Only L3 information elem is printed
E(XCLUDE) ...... All messages except excluded
X(heX) ...... The whole message (data in hex )
F(ULL) ...... The whole message is printed (default)
HEADER outputs only the headers of the messages.
SYS INFO monitors only the messages containing system information.

Id:0900d805805a2a0d

DN00216433
Issue 4-0

TRXSIG Monitoring

TRXSIG Monitoring - command descriptions

L3 monitors only messages containing the L3 information element.

The EXCLUDE mode bypasses the messages you have set to be excluded (bypassed
messages are set with the E-command).
The HEX mode prints out data in hexadecimal form.
FULL is the default mode and prints out all possible messages from the processes you
have defined.
trans mode TP/NP
The mode of the transparent message output. The possible values are:
O(FF) ...... Messages including a message discriminator are skipped
F(ULL) ..... Message data including a message discriminator is decoded and
output (default)
TP is for transparent discriminator messages and NP is for NON-Transparent discriminator messages.
process PRB
The mode of the process output. The possible values are:
A(BIPRB) ...... ABIPRB messages are decoded and output
S(YIPRB) ...... SYIPRB messages are decoded and output
B(OTH) ..... All possible processes(ABIPRB and SYIPRB) are output (default)
Monitored process for Abis telecom message.
output device OUT
The target of the output. The possible values are:
TERM .............. Service terminal (default)
selector.offset,end_address ... GDT slot, offset
and end address
(for example, G40.0,3FFFF)
The end address is optional. You can use it to limit the buffer memory size that the
TRXSIG Monitoring uses when the monitored messages are directed to the memory
buffer. This is useful, for example, when message monitoring is directed to the same
GDT slot in the same computer unit in which the Abis telecom messages are monitored.
Configuring the memory area correctly for both monitoring tasks prevents the different
tasks' monitoring messages from overwriting each other's memory area. If the end
address is not used in the command, TRXSIG Monitoring uses the maximum GDT slot
end address given by the system.
Examples

1. Monitor and decode the Abis telecom messages of BTSs 1 and 2.

Z1M:1&2;
2. Monitor all the Abis telecom message headers of the BTSs ranging from BTSs 10 to
20. Output is directed to G40.0.
Z1M:10&&20:MSG=HEADER:OUT=G40.0;
3. Monitor these BTSs at the same time : BTS 7 TRX 1, BTS 8 TRX 2 and BTSs
from 9 to 12.
Z1M:7-1&8-2&9&&12;
4. Monitor all ABIPRB messages from BTSs 15 to 40.

DN00216433
Issue 4-0

Id:0900d805805a2a0d

TRXSIG Monitoring - command descriptions

TRXSIG Monitoring

Z1M:15&&40:PRB=A;
5. Monitor all system information messages in BTS 15 TRX 1 and TRX 11.
Z1M:151&11:MSG=I;
Execution printouts

The execution printout consists of the following components:

1. Monitoring header (monitored BTSs and monitoring modes). If any defined trigger,
filter or excluded messages exist, they are shown at the beginning of the monitoring
start phase. For example, if you have defined some filters on and start monitoring,
TRXSIG Monitoring shows the messages first.
2. Message Header: D-channel number, Calendar time, BTS identity , TRX identity,
Discriminators, Abis telecom message name and number. If the message is not
found, the text UNKNOWN is printed instead of the name.
3. Element data: Abis telecom element data decoded as described in the Abis telecom
interface. If the element is not found, the text UNKNOWN is printed instead of the
identification text. However, the data is printed in hexadecimal form.
The execution printout of command example M is:

00MAN> Z1M:1&2-1
Monitored BTS (TRX): 0001 (01) 0001 (02) 0002 (05)
Monitoring modes: MSG = FULL, TP = FULL, NP = FULL, PRB = BOTH

***************** DCS = 4
************** 2006-09-14
From BSC to BTS-0001 TRX-02
Radio Link Layer Management
Transparent
DATA REQUEST (01H)
Channel Number
- Bm + ACCHs
- Timeslot : 0
Link Identifier
- Sapi : 0
- Channel type : FACCH or SDCCH
- Normal priority
L3 Information
ALERTING (CC)

12:33:24.44 ****

******* DCS = 3
************** 2006-09-14
12:33:24.48 ****
From BTS-0001 TRX-01 to BSC
Common Channel Management
NON_Transparent
CHANNEL REQUIRED (13H)
Channel Number
- Uplink CCCH (RACH)
- Timeslot : 0
Request Reference
- establishment cause : 248
- random reference : 25
- T1' : 0, - T2 : 0, - T3 : 0
Access Delay
- value : 0 (00h)
***************** DCS = 3
************** 2006-09-14
From BSC to BTS-0001 TRX-01
Dedicated Channel Management
NON_Transparent
CHANNEL ACTIVATION (21H)
Channel Number

10

Id:0900d805805a2a0d

12:33:24.49 ****

DN00216433
Issue 4-0

TRXSIG Monitoring

TRXSIG Monitoring - command descriptions

- SDCCH/4 + ACCH sub-channel : 1

- Timeslot : 0
Activation Type
- procedure is : an initial activation
- immediate assignment procedure
Channel Mode
- DTX is not applied in the downlink
- Signalling
- SDCCH
- no resources required
BS Power :
level 0
MS Power :
level 2
Timing Advance :
0
SACCH Information
- SYSTEM INFO 5
06H, 1DH,
00H, 00H,
00H, 00H,
- SYSTEM INFO 6
06H, 1EH,
4EH, 21H,
2BH, 2BH,

00H,
00H,
00H,
4EH,
64H,
2BH,

00H,
00H,
04H
21H,
01H,
2BH

00H, 00H, 00H,

00H, 00H, 00H,
25H, F0H, 81H,
00H, 36H, 13H,

******* DCS = 3
************** 2006-09-14
12:33:24.50 ****
From BTS-0001 TRX-01 to BSC
Dedicated Channel Management
NON_Transparent
CHANNEL ACTIVATION ACK (22H)
Channel Number
- SDCCH/4 + ACCH sub-channel : 1
- Timeslot : 0
Frame Number
- T1 : 0 - T2 : 0 - T3 : 0
***************** DCS = 3
************** 2006-09-14
From BSC to BTS-0001 TRX-01
Common Channel Management
NON_Transparent
IMMEDIATE ASSIGN COMMAND (16H)
Channel Number
- Downlink CCCH (PCH + AGCH)
- Timeslot : 0
Full Immediate Assign Info
IMMEDIATE ASSIGNMENT (RR)
Page Mode
- Normal paging
Dedicated mode or TBF
- Dedicated Mode Resource
- Downlink : 40
Channel Description
- SDCCH/4 + SACCH/C4 or CBCH subchannel : 1
- timeslot : 0
- training sequence code : 0
- hopping : Single RF channel
- ARFCN : 1 (01h)
Request Reference
- establishment cause : 248
- random reference : 25
- T1' : 0, - T2 : 0, - T3 : 0
Timing Advance : 0
Mobile Allocation
- Length : 0
IA Rest Octets
2B 2B 2B 2B 2B 2B 2B 2B 2B 2B 2B

DN00216433
Issue 4-0

12:33:24.51 ****

Id:0900d805805a2a0d

11

TRXSIG Monitoring - command descriptions

TRXSIG Monitoring

******* DCS = 3
************** 2006-09-14
12:33:24.52 ****
From BTS-0001 TRX-01 to BSC
Radio Link Layer Management
NON_Transparent
ESTABLISH INDICATION (06H)
Channel Number
- SDCCH/4 + ACCH sub-channel : 1
- Timeslot : 0
Link Identifier
- Sapi : 0
- Channel type : FACCH or SDCCH
- Normal priority
L3 Information
CM SERVICE REQUEST (MM)
CM Service Type
- Mobile orig. call or packet mode connect
Ciphering Key Seq. Nbr
- value : No key is available (7h)
Mobile Station Classmark 2
- Revision level : Used by phase 2 mobile stations
- Classmark Sending option is not implemented
- encryption algorithm A5/1 available
- RF power capability class 1
- PS capability present
- SS screening indicator for phase 2
- short message capability present
- No VBS capability or no notifications wanted
- No VGCS capability or no notifications wanted
- MS does support extension band G1
- Additional MS capabilities are described in the Classmark 3
- CMSP: Not supported
- A5/3 algorithm NOT available
- A5/2 algorithm NOT available
Mobile Identity
- Length : 5
- TMSI : FF0E889B6

******* DCS = 3
************** 2006-09-14
12:33:24.54 ****
From BTS-0001 TRX-01 to BSC
Radio Link Layer Management
Transparent
DATA INDICATION (02H)
Channel Number
- SDCCH/4 + ACCH sub-channel : 1
- Timeslot : 0
Link Identifier
- Sapi : 0
- Channel type : FACCH or SDCCH
- Normal priority
L3 Information
CLASSMARK CHANGE (RR)
Mobile Station Classmark 2
- Revision level : Used by phase 2 mobile stations
- Classmark Sending option is not implemented
- encryption algorithm A5/1 available
- RF power capability class 1
- PS capability present
- SS screening indicator for phase 2
- short message capability present

12

Id:0900d805805a2a0d

DN00216433
Issue 4-0

TRXSIG Monitoring

TRXSIG Monitoring - command descriptions

- No VBS capability or no notifications wanted

- No VGCS capability or no notifications wanted
- MS does support extension band G1
- Additional MS capabilities are described in the Classmark 3
- CMSP: Not supported
- A5/3 algorithm NOT available
- A5/2 algorithm NOT available
Mobile Station Classmark 3
- encryption algorithm A5/4 not available
- encryption algorithm A5/5 not available
- encryption algorithm A5/6 not available
- encryption algorithm A5/7 not available
- Multiband Supported :
P-GSM not supported
E-GSM or R-GSM supported
DCS 1800 supported
- Radio capability 1 : 2
- Radio capability 2 : 2
- Multislot capability
- Multislot class : 1
- ME has preference for def. alphapet over UCS2
- MS does not support extended measurements
- MS Positioning Method Capability
- MS assisted E-OTD not supported
- MS based E-OTD not supported
- MS assisted GPS not supported
- MS based GPS supported
- Conventional GPS not supported
- Gsm 1900 associated radio capability : 2
- UMTS FDD not supported
- UMTS 3.84 Mcps TDD not supported
- CDMA2000 not supported
- DTM GPRS multislot class :
Multislot class 5 supported
- Single slot DTM not supported
- DTM EGPRS multislot class :
Multislot class 5 supported
- UMTS 1.28 Mcps TDD not supported
- GERAN feature package 1 not supported

******* DCS = 3
************** 2006-09-14
12:33:24.57 ****
From BTS-0001 TRX-01 to BSC
Radio Link Layer Management
Transparent
DATA INDICATION (02H)
Channel Number
- SDCCH/4 + ACCH sub-channel : 1
- Timeslot : 0
Link Identifier
- Sapi : 0
- Channel type : FACCH or SDCCH
- Normal priority
L3 Information
DTM REQUEST
Temporary Logical Link Identity
53261
Channel Request Description 2 - Packet access reason: User Data
- Peak Troughput Class : 4
- Radio Priority : 0

DN00216433
Issue 4-0

Id:0900d805805a2a0d

13

TRXSIG Monitoring - command descriptions

TRXSIG Monitoring

- RLC Mode : acknowledged

- LLC PDU : is SACK or ACK
- RLC Octet Count : 10328 (2858h)

***************** DCS = 3
************** 2006-09-14
From BSC to BTS-0001 TRX-01
Radio Link Layer Management
Transparent
DATA REQUEST (01H)
Channel Number
- SDCCH/4 + ACCH sub-channel : 1
- Timeslot : 0
Link Identifier
- Sapi : 0
- Channel type : FACCH or SDCCH
- Normal priority
L3 Information
DTM REJECT
Wait Indication
- T3122/T3142 timeout value : 2 (02h)

12:33:24.58 ****

******* DCS = 4
************** 2006-09-14
12:34:19.67 ****
From BTS-0002 TRX-05 to BSC
Common Channel Management
NON_Transparent
CCCH LOAD INDICATION (12H)
Channel Number
- Uplink CCCH (RACH)
- Timeslot : 0
RACH Load
- Slot:3240 Busy:0
Access:0
******* DCS = 4
************** 2006-09-14
12:34:19.68 ****
From BTS-0002 TRX-05 to BSC
Common Channel Management
NON_Transparent
CCCH LOAD INDICATION (12H)
Channel Number
- Downlink CCCH (PCH + AGCH)
- Timeslot : 0
Paging Load :
0000h
******* DCS = 4
************** 2006-09-14
12:34:21.58 ****
From BTS-0002 TRX-05 to BSC
TRX Management
NON_Transparent
RF RESOURCE INDICATION (19H)
Resource Information
- interf. levels for ch :
20:1 28:1 30:1 38:1 09:1 0A:1
0B:1 0E:1

Monitoring only SYSTEM INFO Abis telecom messages:

00MAN> Z1M:1&2:MSG=I;

Monitored BTS(TRX): 0001(01) 0001(02) 0002(05)

Monitoring modes: MSG = SYS INFOs, TP = FULL, NP = FULL, PRB = BOTH

***************** DCS = 2

************** 20001-01-18

14

Id:0900d805805a2a0d

14:11:28.77 ****

DN00216433
Issue 4-0

TRXSIG Monitoring

TRXSIG Monitoring - command descriptions

From BSC to BTS-0001 TRX-01

Common Channel Management
NON_Transparent
BCCH INFORMATION (11H)
Channel Number
- BCCH
- Timeslot : 0
System Info Type
SYSTEM INFORMATION 4
Full BCCH Information
SYSTEM INFO TYPE 4 (RR)
Location Area Id.
- MCC : 234, - MNC : 15, - LAC : 4369 (1111h)
Cell Selection Params
- cell reselect hysteresis : 4 dB
- MS_TXPWR_MAX_CCH : 5
- RXLEV_ACCESS_MIN : 5 (-106 - -105 dBm)
- new estab causes are not supported
- SI 4 rest octest (if present), used
RACH Control Parameters
- max retransmissions : 4
- number of slots : 10
- cell is barred
- call reestab. not allowed
- Emergency call allowed
- allowed acc. classes :
0 1 2 3 4 5 6 7 8 9 11 12 13 14 15
SI 4 Rest Octets :
2B, 2B, 2B, 2B, 2B, 2B, 2B, 2B, 2B,
2B

***************** DCS = 2
************** 20001-01-18
From BSC to BTS-0001 TRX-01
TRX Management
NON_Transparent
SACCH FILLING (1AH)
System Info Type
SYSTEM INFORMATION 5
L3 Information
SYSTEM INFO TYPE 5 (RR)
Neighbour Cells Descr.
- format id : bit map 0
- IE carries the complete BA
- BCCH allocation seq. number : 0
- BA :

14:11:29.58 ****

***************** DCS = 2 ************** 20001-01-18 14:11:30.18 ****

From BSC to BTS-0001 TRX-01
TRX Management
NON_Transparent
SACCH FILLING (1AH)
System Info Type
SYSTEM INFORMATION 6
L3 Information
SYSTEM INFO TYPE 6 (RR)
Cell Identity

DN00216433
Issue 4-0

Id:0900d805805a2a0d

15

TRXSIG Monitoring - command descriptions

TRXSIG Monitoring

- cell id value : 3950 (0204h)

Location Area Id.
- MCC : 234, - MNC : 15, - LAC : 4369 (1111h)
Cell Options (BCCH)
- BCCH included in meas. results
- MSs shall not use DTX
- RLT : 20 SACCH multiframes
NCC Permitted
- NCCs : 0, N = 1
SI 6 Rest Octets :
- DTM is supported in the serving cell
- RAC : 10 (0Ah)
- MAX LAPDm : Any message segmented in up to 9 LAPDm frames
- ARFCN indicates 1800 band
- GPRS Ms TXPWR max CCH : 5
Execution error
messages

/*** BTS NOT FOUND ***/

There are no existing BTSs in the monitoring set command.
/*** TRX NOT FOUND ***/
There are no existing TRXs in the monitoring set command.
/*** BTS NUMBER OUT OF RANGE ***/
The BTS number is not valid.
/*** TRX NUMBER OUT OF RANGE ***/
The TRX number is not valid.
/*** TRX NOT FOUND UNDER BTS ***/
There are no existing TRXs under the monitored BTS.
/*** SEGMENT FULL, MONITORING STOPPED ***/
The output segment is full.
/*** SEGMENT NOT WRITABLE ***/
You have given an output segment (for example a GDT slot) that is not writable.
/*** SYNTAX ERROR> ***/
You have given an illegal parameter name or value.
E - EXCLUDING

Function

Use the command E to define 'excluded messages' that are bypassed during the monitoring.
The excluded messages are excluded from all of the monitored links.
TRXSIG Monitoring receives Abis telecom messages and outputs them if they are not
defined in the excluded list.

Syntax
Parameter explanations

Z1E(C):NBR(,NBR,NBR,...);
number
The number of the excluded message. The number is given in decimal or hexadecimal
format:

16

Id:0900d805805a2a0d

DN00216433
Issue 4-0

TRXSIG Monitoring

TRXSIG Monitoring - command descriptions

number,number,number ... maximum amount of messages is 16

(for example E:26 or EH:1A)
Excluding is useful when you want to leave unwanted messages out.
These messages do not point to any specific BTS or TRX. The setting is on for all monitored links.
You can give the command EC; to clear all defined excluded messages.
Examples

1. Excluding messages PAGING COMMAND (21, 15h) and SACCH INFO MODIFY
(52, 34h).
Set excluding messages:
Z1E:21,52;
Start monitoring:
Z1M:BTS_id:MSG=E;

Execution error
messages

/*** NO MESSAGE TYPE FOUND ***/

You have given a message number that is not found.
T - TRIGGERING

Function

Use the command T to define a monitoring table for triggered messages.

Syntax
Parameter explanations

Z1T:BTS_ID(-TRX_ID),NUMBER;
BTS identification
The identification of the monitored base station function. Possible values range from 1
up to the maximum number of BTSs. You can give multiple BTSs by using the characters & and &&. The parameter is obligatory.
Note that a maximum combination of 128 BTSs/TRXs can be triggered simultaneously.
TRX identification
The identification of the monitored TRX in the BTS. Possible values range from 1 to 24.
If a value is not given, then all the TRXs in the BTS are triggered. The parameter is
optional.
number
The number of desired triggering message for the defined BTS+TRX combination.

Examples

1. Set triggering for BTS 1 TRX 4. The message number is 19.

Z1T:1-4,19
2. Set triggering for BTS 3. The message number is 20.
Z1T:3,20

Execution error
messages

/*** NO MESSAGE TYPE FOUND ***/

You have given a message number that is not defined in the radio network.
/*** BTS NOT FOUND ***/
You have given a BTS number that is not defined in the radio network.
/*** TRX NOT FOUND ***/

DN00216433
Issue 4-0

Id:0900d805805a2a0d

17

TRXSIG Monitoring - command descriptions

TRXSIG Monitoring

You have given a TRX number that is not defined in the radio network.
/*** BTS NOT FOUND UNDER BTS ***/
You have given a TRX number that is not defined under the given BTS in the radio
network.
F - FILTERING
Function
Syntax
Parameter explanations

Use the command F to define a monitoring table for filtered messages.

Z1F:BTS_ID(-TRX_ID),NUMBER;
BTS identification
The identification of the monitored base station function. Possible values range from 1
up to the maximum number of BTSs. You can give multiple BTSs by using the characters & and &&. The parameter is obligatory.
Note that a maximum combination of 128 BTSs/TRXs can be filtered simultaneously.
TRX identification
The identification of the monitored TRX in the BTS. Possible values range from 1 to 24.
If a value is not given, all the TRXs in the BTS are filtered. The parameter is optional.
number
The number of the desired filtering message for the defined BTS+TRX combination.
Filtering is used when you do not want to output a certain message in a certain link. The
maximum number of messages filtered out is 64 messages.

Examples

1. Set filtering for BTS 1 TRX 4. The message number is 97.

Z1F:1-4,97
2. Set filtering for BTS 3. The message number is 19.
Z1F:3,19

Execution error
messages

/*** NO MESSAGE TYPE FOUND ***/

You have given a message number that is not defined in the radio network.
/*** BTS NOT FOUND ***/
You have given a BTS number that is not defined in the radio network.
/*** TRX NOT FOUND ***/
You have given a TRX number that is not defined in the radio network.
/*** BTS NOT FOUND UNDER BTS ***/
You have given a TRX number that is not defined under the given BTS in the radio
network.
O - OUTPUTS

Function

18

Use the command O to output the monitoring buffer to the service terminal after the
monitoring to the buffer is stopped (the monitoring has started, for example, with the
OUT=G40.0 parameter). You can also output excluded messages, the trigger table, and
the filter table.

Id:0900d805805a2a0d

DN00216433
Issue 4-0

TRXSIG Monitoring

TRXSIG Monitoring - command descriptions

Syntax
P:pointer[,end];
Note: pointer and end values must be the same that were given
in the monitoring command for the monitoring buffer.
pointer:

(e.g. G40.0[,3FFFF])

E;
This shows the list of the excluded messages.
Monitoring is shown in FULL (exclude) mode at the beginning of the monitoring.

T(:BTS_ID-(TRX_ID));
This shows the list of triggerings if there is any.
You can show the triggerings along BTS_id, or BTS_id and TRX_id,
or all the triggering settings.
BTS_ID
TRX_ID

(1 - 3000)
(1 - 24)

Default is: Show all the triggering settings.

F(:BTS_ID-(TRX_ID));
This shows the list of filterings if there is any.
You can show the filterings along BTS_id, or BTS_id and TRX_id,
or all the filtering settings.
BTS_ID
TRX_ID

(1 - 3000)
(1 - 24)

Default is: Show all the filtering setting.

M(H)(:NUMBER);
!
The number is HEX.
Output the message types or all the possible
types according to the number.
NUMBER: Decimal number of type.
The default is: Output all types.

Parameter explanations

address
The address of the monitoring memory. The address is given in the following format:
SELECTOR.OFFSET,END_ADDRESS ... GDT slot, offset
and end address (e.g.G40.0,3FFFF)
The address must be the same as the one given in the monitoring start command for the
OUT parameter, which defines the monitoring buffer.

DN00216433
Issue 4-0

Id:0900d805805a2a0d

19

TRXSIG Monitoring - command descriptions

TRXSIG Monitoring

BTS_id
The identification of the monitored base station function. The possible values range from
1 up to the maximum number of BTSs. You can give multiple BTSs by using the characters & and &&. The parameter is optional.
TRX_id
The identification of the monitored TRX in the BTS. The possible values range from 1 to
24. If a value is not given, all the TRXs in the BTS are filtered. The parameter is optional.
number
The number of the message type.
18 : (12h) CCCH LOAD INDICATION
25 : (19h) RF RESOURCE INDICATION
You can define more excluded messages. User-defined messages are valid only while
you do not exit the service terminal extension.
The triggering table is used for starting the monitoring after certain messages appear in
different TRX links. The maximum number of triggering settings is 128 messages.
You can use filtering in monitoring when you do not want certain messages to appear in
the monitoring output. The maximum number of filtering settings is 64 messages.
Message types can also be displayed.
Examples

1. Output from G40.0.

Z1OP:G40.0;
Monitoring start command has been, for example:
Z1M:5:OUT=G40.0;
2. Display the triggering table.
Z1OT;
3. Display triggering from BTSs 1 to 20.
Z1OT:1&&20;
4. Display the filtering table.
Z1OF;
5. Display message types.
Z1OM;
6. Display excluded messages.
Z1OE;
The monitoring start command should be, for example:
Z1M:3:MSG=E;

Execution error
messages

/*** SEGMENT NOT READABLE ***/

You have given an input segment (for example, a GDT slot) that is not readable.
/*** NO MESSAGE TYPE FOUND ***/
You have given a message number, but it is not defined.
/*** BTS NOT FOUND ***/

20

Id:0900d805805a2a0d

DN00216433
Issue 4-0

TRXSIG Monitoring

TRXSIG Monitoring - command descriptions

You have given a BTS number that is not defined in the radio network.
/*** TRX NOT FOUND ***/
You have a TRX number that is not defined in the radio network.
/*** TRX NOT FOUND UNDER BTS ***/
You have given a TRX number that is not defined under the given BTS in the radio
network.

DN00216433
Issue 4-0

Id:0900d805805a2a0d

21