2003330 Nokia BSC S10.5 ED, Vers. 2, Product Documentation TGMONI dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 1 (25) TGMONI The information in this documentation 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's customers only for the purposes of the agreement under which the documentation is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia 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 cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the documentation are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the documentation. Nokia's liability for any errors in the documentation is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or the information in it. This documentation and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this documentation may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright © Nokia Corporation 2003. All rights reserved. 2 (25) # Nokia Corporation Nokia Proprietary and Confidential dn00216433 Issue 1-0 en Contents Contents Contents 3 List of tables 4 List of figures 5 1 Introduction to TGMONI 7 2 Command decriptions of TGMONI 9 Glossary 25 dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 3 (25) TGMONI List of tables 4 (25) # Nokia Corporation Nokia Proprietary and Confidential dn00216433 Issue 1-0 en List of figures List of figures dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 5 (25) TGMONI 6 (25) # Nokia Corporation Nokia Proprietary and Confidential dn00216433 Issue 1-0 en Introduction to TGMONI 1 Introduction to TGMONI Purpose of the TGMONI program block The Trxsig Monitoring Program Block (TGMONI) is a service terminal extension that can be used in the DX 200 BSC. The TGMONI commands are used for monitoring and decoding the Abis TELECOM interface messages between the BSC and the base tranceiver stations. The messages are encoded according to the GSM ETSI interface specifications. TGMONI is able to monitor two different kinds of Telecom messages, Abis messages and System Information messages (the default is both). The user is also able to 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), TLV (Type, Length and Value, variable length, element identifier and length indicator included, total length of informtion element, for variable length, lower and upper limits) and TGMONI outputs them to the service terminal in a decoded form. The user can also set different trigger methods for messages according to the monitored TRX_id. By default, messages are output to TERMINAL. The user can also direct output into unit memory. How to use the TGMONI service terminal extension The user can access TGMONI either via the actual service terminal in the Operation and Manitenance Unit (OMU) of the BSC or via the MML terminal (with the command ZDDS; ). dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 7 (25) TGMONI When using the extension for the first time, the user has to link it to the service terminal of the OMU with the command ZLE . The following parameters are given: the caracter to be used for the extension, and the naming characters of the module containing the extension. In this document, 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; For more information, see User's Manual of the Service Terminal. General description of TGMONI The TGMONI operates in the Operation and Maintenance Unit (OMU) of the BSC and implements 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 defined by the user. T EXCLUDING With this command the user is able to define excluded messages. Some messages are set to be excluded by default. See the output command for those messages. T TRIGGERING This command will start monitoring in a specific link when the message defined by the user has arrived to monitoring. F FILTERING This command will filter the messages defined by the user 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. The user can interrupt the output by pressing CTRL-C. 8 (25) # Nokia Corporation Nokia Proprietary and Confidential dn00216433 Issue 1-0 en Command decriptions of TGMONI 2 Command decriptions of TGMONI Main menu The main level menu provides the following commands: ABIS TELECOM MONITORING COMMANDS ? M E T F O Z ..... .... ..... ..... ..... ..... .... MENU/HELP START MONITORING EXCLUDING TRIGGERING FILTERING OUTPUTS EXIT START MONITORING - M FUNCTION The command 'M' is used for starting the monitoring and decoding the Abis TELECOM messages. PARAMETERS BTS identification, TRX identification, message mode, trans mode, process and output device. SYNTAX The Start Monitoring command syntax: Z1M:BTS_ID [-TRX_ID]...: MSG = <message mode>: TP/NP = <trans mode >: PRB = <process >: OUT = <TERM/<pointer [, end] >:; PARAMETER EXPLANATIONS BTS identification BTS_ID dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 9 (25) TGMONI The identification of the monitored base station function. Possible values range from 1 up to the maximum amount of the BTS. The user can give multiple BTSs by using the characters & and &&. The parameter is obligatory. Note: the maximum possible amount of simultaneously monitored TELECOM links is 128, so it's not possible to monitor all the defined BTSs at the same time in a large configuration. TRX identification TRX_ID The identification of the monitored TRX in the BTS. Possible values range from 1 to 16. If a value is not given, then all the existing TRXs under the BTS are monitored. The parameter is optional. message mode MSG The mode of the message output. 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 will output only the headers of the messages. SYS INFO will monitor only the messages containing system information from SYIPRB.L3 will monitor only messages containing the L3 information element. The EXCLUDE mode bypasses the messages the user has set to be exluded (bypassed messages are set with the E-command). The HEX mode will print out data in hexadecimal form. FULL is the default mode and will print out all possible messages from the processes defined by the user. trans mode TP/NP The mode of the transparent message output. Possible values are: 10 (25) # Nokia Corporation Nokia Proprietary and Confidential dn00216433 Issue 1-0 en Command decriptions of TGMONI 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. 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 (e.g.G40.0,3FFFF) The end address is optional. It can be used to limit the buffer memory size that the TGMONI 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, TGMONI 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; dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 11 (25) TGMONI 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. Z1M:15&&40:PRB=A; 5. Monitor all System Information messages in BTS 15 TRX 1 and TRX 11 Z1M:151&11:MSG=I; ADDITIONAL INFORMATION The user can stop monitoring by pressing CTRL-C. If messages are monitored into memory and it is filled up, the monitoring is stopped by the computer. First (one) character of <message mode> , <trans mode> or <process> identifies the value. OPERATION The TGMONI ensures the existence of the given BCFs/TRXs from the BSS Radio Network Configuration Database (BSDATA). Only an existing BCF/TRX link sends a monitoring message to the monitored Abis TELECOM Program Blocks (ABIPRB and/or SYIPRB). The ABIPRB and/or the SYIPRB sends an acknowledgement message and starts sending copies of Abis TELECOM messages to the TGMONI. The TGMONI decodes and outputs the messages to the user according to the output mode. After receiving a CTRL-C, the TGMONI sends a monitoring reset message to the monitored process (ABIPRB and/or SYIPRB). 12 (25) # Nokia Corporation Nokia Proprietary and Confidential dn00216433 Issue 1-0 en Command decriptions of TGMONI 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 the user has defined some filters on and starts monitoring, TGMONI will show 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 following is an example of an execution printout: 00:MAN> Z1M:1&2-5 Monitored BTS (TRX): 001 (01) 001 (02) 002 (05) Monitoring modes: MSG = FULL, TP = FULL, NP = FULL, PRB = BOTH ***************** DCS = 2 ************** 2001-01-18 From BSC to BTS-001 TRX-01 Radio Link Layer Management Transparent DATA REQUEST (1H) Channel Number - SDCCH/4 + ACCH sub-channel : 0 - Timeslot : 0 Link Identifier - Sapi : 0 - Channel type : FACCH or SDCCH - Normal priority L3 Information LOCATION UPDATING ACCEPT (MM) Location Area Id. - MCC : 234, - MNC : 15, - LAC : 4369 (1111h) Mobile Identity - Length : 5 - TMSI : 11118E775600 ******* DCS = 2 ************** 20001-01-18 From BTS-001 TRX-01 to BSC Radio Link Layer Management Transparent DATA INDICATION (2H) Channel Number dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 14:11:34.75 **** 14:11:35.15 **** 13 (25) TGMONI - SDCCH/4 + ACCH sub-channel : 0 - Timeslot : 0 Link Identifier - Sapi : 0 - Channel type : FACCH or SDCCH - Normal priority L3 Information TMSI REALLOCATION COMPLETE (MM) ***************** DCS = 2 ************** 20001-01-18 From BSC to BTS-001 TRX-01 Radio Link Layer Management Transparent DATA REQUEST (1H) Channel Number - SDCCH/4 + ACCH sub-channel : 0 - Timeslot : 0 Link Identifier - Sapi : 0 - Channel type : FACCH or SDCCH - Normal priority L3 Information CHANNEL RELEASE (RR) RR Cause - Normal event 14:11:35.47 **** ***************** DCS = 2 ************** 20001-01-18 From BSC to BTS-001 TRX-01 Dedicated Channel Management NON_Transparent DEACTIVATE SACCH (25H) Channel Number - SDCCH/4 + ACCH sub-channel : 0 - Timeslot : 0 14:11:36.06 **** ******* DCS = 2 ************** 20001-01-18 14:11:36.30 **** From BTS-001 TRX-01 to BSC Radio Link Layer Management NON_Transparent RELEASE INDICATION (9H) Channel Number - SDCCH/4 + ACCH sub-channel : 0 - Timeslot : 0 Link Identifier - Sapi : 0 - Channel type : FACCH or SDCCH - Normal priority ***************** DCS = 2 ************** 20001-01-18 From BSC to BTS-001 TRX-01 Dedicated Channel Management NON_Transparent RF CHANNEL RELEASE (2EH) Channel Number - SDCCH/4 + ACCH sub-channel : 0 - Timeslot : 0 ******* DCS = 2 14 (25) ************** 20001-01-18 # Nokia Corporation Nokia Proprietary and Confidential 14:11:36.67 **** 14:11:37.18 **** dn00216433 Issue 1-0 en Command decriptions of TGMONI From BTS-001 TRX-01 to BSC Dedicated Channel Management NON_Transparent RF CHANNEL RELEASE ACK (33H) Channel Number - SDCCH/4 + ACCH sub-channel : 0 - Timeslot : 0 Monitoring only SYSTEM INFO Abis TELECOM messages: 00:MAN> Z1M:1&2:MSG=I; Monitored BTS (TRX): 001 (01) 001 (02) 002 (05) Monitoring modes: MSG = SYS INFOs, TP = FULL, NP = FULL, PRB = BOTH ***************** DCS = 2 ************** 20001-01-18 14:11:28.77 **** From BSC to BTS-001 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-001 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 dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 14:11:29.58 **** 15 (25) TGMONI - BCCH allocation seq. number : 0 - BA : ***************** DCS = 2 ************** 20001-01-18 From BSC to BTS-001 TRX-01 TRX Management NON_Transparent SACCH FILLING (1AH) System Info Type SYSTEM INFORMATION 6 L3 Information SYSTEM INFO TYPE 6 (RR) Cell Identity - 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 14:11:30.18 **** SEMANTIC 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 ***/ 16 (25) # Nokia Corporation Nokia Proprietary and Confidential dn00216433 Issue 1-0 en Command decriptions of TGMONI The user has given an output segment (for example a GDT slot) that is not writable. /*** SYNTAX ERROR ***/ Illegal parameter name or value is given. EXCLUDING - E FUNCTION The command 'E' is used to define the "excluded messages" that will be bypassed during the monitoring. PARAMETERS number SYNTAX The Excluding command syntax: Z1E (C):NBR (,NBR,NBR,...); PARAMETER EXPLANATIONS number The number of the excluded message. The number is given in decimal or hexadecimal format: number,number,number ... maximum amount of messages is 16 (for example E:26 or EH:1A ) Excluding is useful when the user wants to drop unwanted messages out from the monitoring output. These messages do not point to any specific BTS or TRX. The setting will be on for all monitored links. The user 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; dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 17 (25) TGMONI ADDITIONAL INFORMATION The excluded messages are excluded from all of the monitored links. OPERATION TGMONI gets Abis TELECOM messages and outputs them if they are not defined in the excluded list. SEMANTIC ERROR MESSAGES /*** NO MESSAGE TYPE FOUND ***/ The user has given a message number that is not found. TRIGGERING - T FUNCTION The command 'T' is used for defining a monitoring table for triggered messages. PARAMETERS BTS identification, TRX identification, number SYNTAX The Monitoring command syntax: Z1T:BTS_ID (-TRX_ID),NUMBER; PARAMETER EXPLANATIONS BTS identification The identification of the monitored base station function. Possible values range from 1 to 248. The user can give multiple BTSs by using the characters & and &&. The parameter is obligatory. Note: 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 16. 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. 18 (25) # Nokia Corporation Nokia Proprietary and Confidential dn00216433 Issue 1-0 en Command decriptions of TGMONI The triggering table is used for starting the monitoring after certain messages for different TRX links. The maximum amount of triggering settings is 128 messages. Triggering is used for monitoring when the user wants to start outputting the message monitoring after a certain message has appeared in the defined link. EXAMPLES 1. Set triggering for BTS 1 TRX 4 and the message number is 19. Z1T:1-4,19 2. Set triggering for BTS 3 and the message number is 20. Z1T:3,20 SEMANTIC ERROR MESSAGES /*** NO MESSAGE TYPE FOUND ***/ The user has given a message number but it is not defined. /*** BTS NOT FOUND The user has given a BTS number but it is not defined in the radio network. /*** TRX NOT FOUND The user has given a TRX number but it is not defined in the radio network. /*** TRX NOT FOUND UNDER BTS ***/ The user has given a TRX number but it is not defined under the given BTS in the radio network. FILTERING - F FUNCTION The command 'F ' is used to define a monitoring table for filtered messages. PARAMETERS dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 19 (25) TGMONI BTS identification, TRX identification, number SYNTAX The Filtering command syntax: Z1F:BTS_ID (-TRX_ID),NUMBER; PARAMETER EXPLANATIONS BTS identification The identification of the monitored base station function. Possible values range from 1 to 248. The user can give multiple BTSs by using the characters & and &&. The parameter is obligatory. Note: 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 16. If a value is not given, then all the TRXs in the BTS are filtered. The parameter is optional. number The number of the desired filttering message for the defined BTS+TRX combination. Filtering is used when the user doesn't 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 and the message number is 97. Z1F:1-4,97 2. Set filtering for BTS 3 and the message number is 19. Z1F:3,19 SEMANTIC ERROR MESSAGES 20 (25) # Nokia Corporation Nokia Proprietary and Confidential dn00216433 Issue 1-0 en Command decriptions of TGMONI /*** NO MESSAGE TYPE FOUND ***/ The user has given a message number that is not defined. /*** BTS NOT FOUND The user has given a BTS number that is not defined in the radio network. /*** TRX NOT FOUND The user has given a TRX number that is not defined in the radio network. /*** TRX NOT FOUND UNDER BTS ***/ The user has given a TRX number that is not defined under the given BTS in the radio network. OUTPUTS - O FUNCTION The command 'O' is used 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). The user can also output excluded messages, the trigger table and the filter table. PARAMETERS address, BTS_id, TRX_id, number SYNTAX The different Outputs command 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, dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 21 (25) TGMONI or all the triggering settings. BTS_ID TRX_ID (1 - 248) (1 - 16) 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 - 248) (1 - 16) 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 given in the monitoring start command for the OUT parameter, which defines the monitoring buffer. BTS identification The identification of the monitored base station function. Possible values range from 1 to 248. The user can give multiple BTSs by using the characters & and &&. The parameter is optional. 22 (25) # Nokia Corporation Nokia Proprietary and Confidential dn00216433 Issue 1-0 en Command decriptions of TGMONI TRX identification The identification of the monitored TRX in the BTS. Possible values range from 1 to 16. If a value is not given, then all the TRXs in the BTS are filtered. The parameter is optional. number The number of the message type. Default excluded messages are: 18 : (12h) CCCH LOAD INDICATION 25 : (19h) RF RESOURCE INDICATION The user is able to define more excluded messages. Userdefined messages are valid only while the user doesn't 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. Filtering is used in monitoring when the user doesn't 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; dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 23 (25) TGMONI 5. Display message types Z1OM; 6. Display excluded messages Z1OE; (The monitoring start command should be, for example, Z1M:3:MSG=E;) SEMANTIC ERROR MESSAGES /*** SEGMENT NOT READABLE ***/ The user has given an input segment (for example a GDT slot) that is not readable. /*** NO MESSAGE TYPE FOUND ***/ The user has given a message number that is not defined. /*** BTS NOT FOUND The user has given a BTS number that is not defined in the radio network. /*** TRX NOT FOUND The user has given a TRX number that is not defined in the radio network. /*** TRX NOT FOUND UNDER BTS ***/ The user has given a TRX number that is not defined under the given BTS in the radio network. 24 (25) # Nokia Corporation Nokia Proprietary and Confidential dn00216433 Issue 1-0 en Glossary Glossary BTS Base Tranceiver Station. TRX The transceiver (TRX) is a function which transmits and receives a radio carrier and handles baseband and frame functions. MS Mobile Station. MML Man Machine Language. OMU The TGMONI extension is operated from the Operation and Maintenance Unit (OMU). The ABIPRB and SYIPRB processes are located in the BCSU. For example, hard disks and disk drives are also connected to the OMU. BCSU The Base Station Controller Signalling Unit (BCSU) performs those BSC functions that are highly dependent on the volume of traffic. It consists of two parts corresponding to the A and Abis interfaces.Processes ABIPRB and SYIPRB are located in the Base Station Controller Signalling Unit (BCSU) computer unit. Messages from those processes can be monitored in real time with the Monitoring command M in the TGMONI service terminal. ABIPRB The Abis-interface program block. ABIPRB provides the layer 3 signaling services in the Abis telecom interface between the BSC and the BTS. After a successful monitoring start, all desired message transfers between ABIPRB and BTS are also sent to TGMONI. SYIPRB The system information sending program block. SYIPRB provides the layer 3 signaling services (System Information) in the Abis telecom interface between the BSC and the BTS. After a successful monitoring start, all desired message transfers between SYIPRB and BTS are also sent to TGMONI. TRXSIG The telecom signaling channel between the BSC and TRXs. T, V, TV, TLV Coding methods of the message element used in the Abis Telecom interface. BTS id Each BTS under the same BCF has an unique number from 1 up to the maximum amount of BTSs. The number comes from the radio network plan. TRX id Each TRX under the same BTS has an unique number from 1 up to the maximum amount of TRXs. The number comes from the radio network plan. Transparent BTS has to take or has taken no specific action with Abis TELECOM messages. Non-Transparent BTS has to take some action because of a message and messages which are the result from actions taken by the BTS in the Abis interface. dn00216433 Issue 1-0 en # Nokia Corporation Nokia Proprietary and Confidential 25 (25)