Trace Principles

Principles of the Message Tracing

Figure 1 shows the principles of the message tracing.

Figure 1 Principles of the message tracing

Internal Procedure for Creating a Tracing Task

1. When you create a tracing task on the LMT, the LMT sends a binary command to the OMU to
create the task.
2. The OMU assigns an ID to the task and forwards the command to the debugging module of the
specified board.
3. After receiving the command, the debugging module records the filter parameters of the trace data
in the filter table and notifies the service module.
4. The service module updates the local filter table according to the message from the debugging
module.

Internal Procedure for Closing a Tracing Task

1. When you close a tracing task on the LMT, the LMT sends a binary command to the OMU to delete
the task.
2. The OMU forwards the command to the specified board according to the task ID.
3. The debugging module and service module delete the task from the filter table.

Internal Procedure for the Service Module to Report Traced Messages to the LMT

1. The service module compares the collected messages against the local filter table and reports the
qualified messages to the OMU.
2. The OMU forwards the traced messages to the LMT that creates the task according to the task ID.
3. The LMT translates the messages and displays them on the tracing window.
 of two SCCPCHs.
Tracing BSSAP Messages on the A Interface
This section describes how to trace Base Station Subsystem Application Part (BSSAP) messages by site
on the A interface through the LMT. BSSAP messages include BSSMAP, DTAP, paging, and other
messages.

Prerequisites

 You have logged in to the LMT.

 The communication between the BSC6910 and the BTS is normal.

Context

A maximum of sixteen A interface tracing tasks can be started simultaneously.

Procedure

1. Click Trace on the LMT main page. The Trace tab page is displayed.
2. On Trace Navigation Tree, choose Trace > GSM Services > A Interface Trace. The A Interface
Trace dialog box is displayed, as shown in Figure 1.
Figure 1 Message tracing on the A interface

3. In the A Interface Trace dialog box, set parameters in the default Basic tab page and select
BSSAP under Trace Type.
 DPC (HEX): indicates the destination signaling point to be traced. To query it, run the LST
N7DPC command.
 For description of Trace Mode, see BSC Interface Signaling Tracing Mode.
4. In the BSSAP tab page, set parameters under Message Type and Cell.
 NOTE:
 Cell ID: indicates the index of a cell. To query it, run the LST GCELL command.
5. Click Submit.

Tracing CS Domain Messages on the Um Interface

The Um interface is the interface between a BTS and MSs. This section describes how to trace the layer
3 signaling messages in the CS domain on the Um interface, based on cells or TRXs. You can perform
this task to locate a fault in the following scenarios: timeslot assignment failure, abnormal releases, and
handover failure.

Prerequisites

 You have logged in to the LMT.

 The communication between the BSC6910 and the MSC is normal.

Context

A maximum of sixteen CS tracing tasks on the Um interface can be started simultaneously.

You can start this task on the LMT to monitor the interworking of signaling messages over the Um
interface.
To start a tracing task, you can select the following operations:

 Tracing by the cell or TRX

 Tracing the required types of message

Procedure

1. Click Trace on the LMT main page. The Trace tab page is displayed.
2. Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Um Interface CS
Trace. The Um Interface CS Trace dialog box is displayed, as shown in Figure 1.
 Figure 1 CS domain message tracing on the Um interface

3. In the Um Interface CS Trace dialog box, set the parameters as required.

 Trace Type: Select Paging, Other, or both Paging and Other for this parameter. If Paging is
selected, only the paging messages are traced. If Other is selected, the messages except the
paging messages are traced. If both Paging and Other are selected, all messages are
traced.
 Filter Flag: This parameter can be set to Cell or TRX. When this parameter is set to Cell, you
can set the cell to be traced by specifying Cell ID. When this parameter is set to TRX, you
can set the TRX to be traced by specifying TRX ID.
 Cell ID: indicates the index of a cell. To query it, run the LST GCELL command.
 TRX ID: indicates the number of a TRX. You can query it by running the LST GTRX
command.
 For description of Trace Mode, see BSC Interface Signaling Tracing Mode.
4. Click Submit.

Tracing PS Domain Messages on the Um Interface

The Um interface is the interface between a BTS and MSs. This section describes how to trace PS
domain messages on the Um Interface, including the DUMMY messages, system information messages,
null paging messages, and data block messages. You can perform this task to locate a fault when PS
assignment failure and abnormal TBF release occur.

Prerequisites

 You have logged in to the LMT.

  The communication between the BSC6910 and the SGSN is normal.
 The communication between the BSC6910 and the BTS is normal.
 The configuration type of PCU is Built-in PCU.

Context

A maximum of five PS tracing tasks on the Um interface can be started simultaneously.

Procedure

1. Click Trace on the LMT main page. The Trace tab page is displayed.
2. Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Um Interface PS
Trace. The Um Interface PS Trace dialog box is displayed, as shown in Figure 1.
Figure 1 PS domain message tracing on the Um interface

3. In the Um Interface PS Trace dialog box, set parameters as required.

 Trace Type can be set to Cell or TRX. When Cell is selected, you can set the cell to be
traced by specifying Cell ID. When TRX is selected, you can set the TRX to be traced by
specifying TRX ID.
 Cell ID: indicates the index of a cell. To query it, run the LST GCELL command.
 TRX ID: indicates the number of a TRX. You can query it by running the LST GTRX
command.
 For description of Trace Mode, see BSC Interface Signaling Tracing Mode.
4. Click Submit.