28 Tracing Function

RAN Feature Description
Table of Contents
Table of Contents
Chapter 28 Tracing Function..................................................................................................... 28-1
28.1 Introduction................................................................................................................... 28-1
28.1.1 Definition............................................................................................................. 28-1
28.1.2 Purposes............................................................................................................ 28-1
28.1.3 Terms.................................................................................................................. 28-1
28.1.4 Abbreviations...................................................................................................... 28-2
28.2 Availability..................................................................................................................... 28-3
28.2.1 Network Elements Involved................................................................................28-3
28.2.2 Software Releases............................................................................................. 28-3
28.3 Impact........................................................................................................................... 28-4
28.3.1 On System Performance....................................................................................28-4
28.3.2 On Other Features.............................................................................................. 28-4
28.4 Technical Description.................................................................................................... 28-4
28.4.1 Overview of the Tracing Function.......................................................................28-4
28.4.2 Control Modules................................................................................................. 28-4
28.4.3 SPU.................................................................................................................... 28-5
28.4.4 Working Principle of the Message Tracing..........................................................28-6
28.4.5 Authority for Tracing............................................................................................ 28-7
28.4.6 Overview of the Tracing Management Function.................................................28-7
28.4.7 Message Tracing over Standard Interfaces........................................................28-8
28.4.8 Message Tracing of Transport Network Layer....................................................28-9
28.4.9 Call Tracing....................................................................................................... 28-10
28.4.10 Cell Tracing..................................................................................................... 28-11
28.4.11 OS Tracing...................................................................................................... 28-11
28.4.12 Redirect Tracing.............................................................................................. 28-11
28.4.13 CDT Tracing................................................................................................... 28-12
28.4.14 Location Tracing............................................................................................. 28-12
28.5 Capabilities................................................................................................................. 28-13
28.6 Implementation........................................................................................................... 28-13
28.6.1 Routine Operations of the Tracing Function.....................................................28-13
28.6.2 Creating Trace Tasks........................................................................................ 28-13
28.6.3 Browsing Traced Messages Online..................................................................28-16
28.6.4 Saving Tracing Results.....................................................................................28-17
28.6.5 Stopping/Restarting Trace Tasks......................................................................28-19
28.6.6 Closing Trace Tasks..........................................................................................28-20
28.6.7 Browsing Traced Messages Offline..................................................................28-20
28.6.8 Alarms............................................................................................................... 28-23
Huawei Technologies Proprietary
i
Table of Contents
28.6.9 Counters........................................................................................................... 28-23

28.7 References.................................................................................................................. 28-23

ii
List of Figures
List of Figures
Figure 28-1 Diagram of message tracing............................................................................28-5
Figure 28-2 Working principle of the message tracing........................................................28-6
Figure 28-3 Choosing a tracing object..............................................................................28-14
Figure 28-4 MTP3B Protocol Tracing dialog box............................................................28-15
Figure 28-5 Message browse window...............................................................................28-16
Figure 28-6 Message Browser dialog box.......................................................................28-17
Figure 28-7 Save dialog box............................................................................................. 28-19
Figure 28-8 Opening a file containing traced messages...................................................28-21
Figure 28-9 Displaying traced messages..........................................................................28-22

iii
List of Tables
List of Tables
Table 28-1 NEs required for the tracing function.................................................................28-3
Table 28-2 RAN product and related version.......................................................................28-3
Table 28-3 Message tracing over standard interfaces.........................................................28-8
Table 28-4 Message tracing of transport network layer.......................................................28-9
Table 28-5 Call tracing....................................................................................................... 28-10
Table 28-6 Cell tracing....................................................................................................... 28-11
Table 28-7 OS tracing........................................................................................................ 28-11
Table 28-8 Redirect tracing................................................................................................28-11
Table 28-9 CDT tracing..................................................................................................... 28-12
Table 28-10 Location tracing............................................................................................. 28-12

iv
Chapter 28 Tracing Function

28.1 Introduction
28.1.1 Definition
The interface tracing function in a mobile telecommunications system is of key
importance for the Operation and Maintenance (O&M). An operator who is familiar
with the system procedures can verify the data and troubleshoot the problems
through checking the interface messages traced by the BSC6800.
The BSC6800 provides the following types of interface tracing:
Message Tracing over Standard Interfaces
Message Tracing of Transport Network Layer
Call Tracing
Cell Tracing
OS Tracing
Redirect Tracing
CDT Tracing
Location Tracing
28.1.2 Purposes
You can quickly verify the data and troubleshoot a fault by checking the messages on
different interfaces.
28.1.3 Terms
Term
UE tracing
Description
The UE tracing consists of the following two types:
UE tracing (on the user plane and the signaling plane)

This task is performed to trace the call-related information of a
specified UE on the signaling plane and on the user plane
during a call.
UE tracing (standard interface)

This task is performed to trace signaling messages of a
specified UE over Iu, Iur, Iub, and Uu interfaces during a call.

1
Term
IOS tracing
Description
This task is performed to trace a specified number of calls which
access a specified cell continuously. The number of calls can be
defined when the task is started.
The number of calls can be set when the task is started.
The messages during the call procedure are traced.
Cell tracing
The cell tracing is used to measure the following two types of

messages:
Common signaling messages on the Iub interface of one or

more specified cells
Customized messages that contain information about UEs in

the cells
CDT tracing
The CDT tracing (detailed call tracing) is used to trace the following
messages:
OS tracing
Standard interface messages of the UE
Messages on the user plane and signaling plane of the UE
OS tracing is used to trace the messages inside the Operating

System (OS).
Redirect
Redirect tracing is used to trace the print information of the serial
tracing
ports on the board subsystem.
OM-DBG
OM-DBG is an internal module of the SPU. It has the following

functions:
Receiving tasks sent from the BAM
Generating filter tables
Maintaining the task check between the BAM and the SPU
Maintaining the message channels between the trace tasks and

the LMT
Informing the traffic processing module of the change of trace

tasks
Providing message channels from the traffic processing module

to the BAM or LMT
Providing interfaces for reporting data messages of the traffic

module
Providing interfaces for flow control

2
28.1.4 Abbreviations
Abbreviation
Full Spelling
BAM
Back Administration Module
IMEI
International Mobile Equipment Identity
IMSI
International Mobile Subscriber Identity
LMT
Local Maintenance Terminal
P-TMSI
Packet Temporary Mobile Subscriber Identity
RAN
Radio Access Network
SAAL
Signaling ATM Adaptation Layer
SCCP
Signaling Connection and Control Part
SPU
Signaling process Unit
TMSI
Temporary Mobile Subscriber Identity
LAC
Location Area Code
LAN
Local Area Network
RAC
Routing Area Code
UMTS
Universal Mobile Telecommunications System
28.2 Availability
28.2.1 Network Elements Involved
Table 1.1 describes the Network Element required for the tracing function.
Table 1.1 NEs required for the tracing function
UE
NodeB
RNC
MSC
MGW
SGSN
GGSN
HLR
Server

3
Note:
: Not required
: Required
Note:
This chapter describes only the availability of the NodeB and the RNC.
28.2.2 Software Releases

Table 1.1 describes the version of RAN product that supports the tracing function.
Table 1.1 RAN product and related version
Product
RNC
Version
BSC6800
V100R002 and later releases
28.3 Impact
28.3.1 On System Performance
A message trace task occupies a lot of system resources. Therefore, do not execute
this task when the system carries heavy traffic. Ensure that the message tracing
window is closed when a message trace task is completed.
To ensure effective use of the system resources, Huawei recommends that you start
only one group of tasks in the following three groups:
CDT tracing and UE trace (standard interface message)
Call tracing and cell tracing
Message tracing over interfaces such as Iub, Iur, Iu, standard protocols such as
Q.AAL2, SAAL, SCCP, MTP3-b tracing and realtime status monitoring function
28.3.2 On Other Features

None.

4
28.4 Technical Description

28.4.1 Overview of the Tracing Function
The system that performs the tracing function consists of the following components:
Control modules for message tracing on the OMC side
Signaling Processing Unit (SPU) on the RNC side
This section describes functions, working principles, and process of message tracing
performed on the whole system.
28.4.2 Control Modules

Control modules consist of the LMT and the BAM, as shown in Figure 1.1.
LMT
Non-call
tracing
OM-DBG
Transparent
transmission
Task maintenance
of Non-call tracing
Task
processing
Call
tracing
Call trace agent
Task maintenance
of call tracing
BAM
SPU
Figure 1.1 Diagram of message tracing
I. LMT
The LMT performs the following functions:
Sending the trace task to the BAM
Displaying the execution results that are sent from the BAM
II. BAM
The BAM broadcasts the trace task that is send from the LMT to the SPU on the
corresponding board.
For the non-call trace task, the BAM transparently transmits it to the SPU.
For the call trace task, the call trace agent module in the BAM performs
centralized management.
The call trace agent has the following functions:
Receiving the tracing requirements from the LMT

5
Creating, modifying, or terminating a trace task
Converting the requirements of the trace task into specified tracing conditions,
and then sending them to the SPU
Receiving the data report provided by the SPU and reporting it to the LMT or
analyzing it
28.4.3 SPU
The SPU can be embedded into the mobile services processing unit. The SPU
performs the following functions:
Receiving the tracing command sent from the control modules
Determining the object to be traced
Tracing that object when it is triggered by a standard interface message or a

customized message between the modules
Duplicating the traced message and sending it to the control modules
To carry more information, the data sent to the control modules can carry some other
basic information such as the arriving time of the message.
Tracing of the subscribers by the SPU consists of the following:
Tracing of messages on each standard interface on the RNC
Tracing of customized messages between different interfaces on modules of the

RNC
The tracing of the subscribers can be further divided into the following:
Tracing of messages on a standard interface
Tracing of customized messages between different interfaces on multiple

modules
Tracing of messages of one type
Tracing of messages of all the types
Tracing of messages on all the interfaces
When a specified event related to the traced message occurs, the SPU copies the
message and sends it to the trace agent of the control modules. Then the trace agent
performs the following according to the message types:
For the standard interface message, the trace agent decodes the message
according to the interface type.
For the customized message, the trace agent displays the message directly.
28.4.4 Working Principle of the Message Tracing

Figure 1.1 shows the working principles of the message tracing.

6
Service
module
BAM
Binary
command
LMT
Maintain
module
Debugging
module
FAM boards
Figure 1.1 Working principle of the message tracing

The internal process of the trace task creation is as follows:
1)
The operator creates a trace task on the LMT, and the LMT sends a binary
command to the BAM server to create the task.
2)
The BAM server 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 tracing 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.
The internal process of the trace task closure is as follows:

1)
The operator closes a trace task on the LMT, and the LMT sends a binary
command to the BAM server to delete the task.
5)
The BAM server forwards the command to the specified board according to the
task number.
6)
The debugging and service modules delete the task from the filter table.
The internal process for the service module to report traced messages to the LMT is
as follows:
1)
The service module filters the collected messages according to the filter
parameters in the local filter table and reports the messages meeting the
requirements to the BAM server.
7)
The BAM server forwards the traced messages to the LMT that creates the task
according to the task number.
8)
The LMT translates the messages and displays them on the interface.
28.4.5 Authority for Tracing

The operators at the following levels can execute the trace tasks:
admin
USER
7
OPERATOR
ADMINISTRATOR
CUSTOM entitled to use command group G_10
28.4.6 Overview of the Tracing Management Function

This function is used to trace:
Messages over standard interfaces
Messages on signaling links
Internal messages
It is applicable to routine equipment maintenance, debugging, and fault location.

The BSC6800 provides the following tracings:
Message Tracing over Standard Interfaces
Message Tracing of Transport Network Layer
Call Tracing
OS Tracing
Redirect Tracing
CDT Tracing
Location Tracing
28.4.7 Message Tracing over Standard Interfaces

This task is performed to trace messages over the Iu, Iur, Iub, and Uu interfaces, as
listed in Table 1.1.
Table 1.1 Message tracing over standard interfaces
Task
Function
Iu interface
This task is performed to trace signaling messages over the Iu
tracing
interface, including connection-oriented messages and

connectionless messages.
You can start the Iu interface tracing in the LMT to monitor the
exchange situations of signaling messages over the Iu interface.
You can specify different Destination Point Codes (DPC) or WSPUb
subsystems for tracing. For tracing, you can either specify all
message types or only the message types concerned.

8
Task
Function
Iur
This task is performed to trace signaling messages over the Iur
interface
interface, including connection-oriented messages and
tracing
connectionless messages.
You can start the Iur interface tracing in the LMT to monitor the
exchange situations of signaling messages over the Iur interface.
You can specify different DPCs or WSPUb subsystems for tracing.
For tracing, you can specify either all message types or only the
message types concerned.
Iub
This task is performed to trace signaling messages over the Iub
interface
interface, that is, NodeB Application Part (NBAP) messages.
tracing
You can start the Iub interface tracing in the LMT to monitor the
exchange situations of signaling messages over the Iub interface.
You can specify all NodeBs, or all ports of a NodeB, or one port of a
NodeB for tracing. Also, you can trace either the messages processed
by one or several WSPUb subsystems, or the messages of one type
or of all the types concerned.
Uu
This task is performed to trace signaling messages over the Uu
interface
interface.
tracing
You can start the Uu interface tracing in the LMT to monitor the
exchange situations of signaling messages over the Uu interface.
You can specify one or more cells or RNCs for tracing. Also, you can
trace all Uu interface message types or only the message types
concerned.
Note:
A maximum of six trace tasks can be performed simultaneously over the lu, lur, lub,
and Uu interfaces.
28.4.8 Message Tracing of Transport Network Layer

This task is performed to trace the messages of the following:
Q.ATM Adaptation Layer type 2 (QAAL2)
Signaling Connection and Control Part (SCCP)
Message Transfer Part level 3 - Broadband (MTP3-B)

9
Signaling ATM Adaptation Layer (SAAL)
Stream Control Transmission Protocol (SCTP)
For details, refer to Table 1.1.

Table 1.1 Message tracing of transport network layer
Task
Function
QAAL2
This task is performed to trace messages of the QAAL2.
protocol
It is performed to detect the setup failure or release abnormality of an
tracing
ATM Adaptation Layer type 2 (AAL2) connection on the user plane.

It also helps you judge whether the local or peer end is normal or not
by checking whether the ESTABLISH_REQUEST message is sent
and by checking the replied messages.
SCCP
This task is performed to trace messages of the SCCP, including
protocol
connection-oriented messages and connectionless messages.
tracing
It is performed to locate the problems that lead to the failure of the Iu

or Iur connection setup and the release abnormity.
MTP3-B
This task is performed to trace messages of the MTP3-B, including:
protocol
MTP3-B upper layer (QAAL2 and SCCP) messages
MTP3-B signaling link test messages
MTP3-B signaling network management messages
tracing
It is performed to locate the problem that leads to the unavailability of

an MTP3B link when the corresponding SAAL link is available. The
method is to check the consistency of the Originating signaling Point
Code (OPC), DPC, and Signaling Link Selection code (SLS) in the
sent and received SLTM messages with the negotiated data.
SAAL
This task is performed to trace messages of the SAAL.
protocol
tracing
the SAAL link.

If there are only outgoing but no incoming RNC messages, it is an
indication that the lower layer link (PVC) or the peer end works
abnormally.

10
Task
Function
SCTP
This task is performed to trace messages of the SCTP.
protocol
tracing
the SCTP link.

When the NCP or CCP is not functional, you can start the SCTP
protocol trace task to query the information of the SCTP link
concerned.
28.4.9 Call Tracing

During a call, this task is performed to trace messages of a UE over:
Standard interfaces
Signaling plane
User plane
It is also performed to trace multiple calls simultaneously (IOS tracing). For details,
refer to Table 1.1.
Table 1.1 Call tracing
Task
Function
UE tracing
This task is performed to trace signaling messages of a specified
(standard
UE over Iu, Iur, Iub, and Uu interfaces during a call.
interface)
To start a trace task, first specify the identifier of the UE (IMSI,

TMSI, P-TMSI, or IMEI).
You can choose one or more interfaces to trace.
You can choose Close dedicated measurement report and
Close RRC measurement report to mask the dedicated
measurement report for the Iub interface and the RRC
measurement report for the Uu interface.
UE tracing
This task is performed to trace the call-related information of a
(signaling plane
specified UE on the signaling plane and on the user plane during
and user plane)
a call.
To start a trace task, first specify the identifier of the UE to trace
(IMSI, TMSI, P-TMSI, or IMEI), and then choose the events to
trace the required signaling plane and user plane information.

11
Task
IOS tracing
Function
This task is performed to trace a specified number of calls which
access a specified cell continuously. To be more specific, it is
performed to trace the messages generated by the calls.
Suppose that the specified number of continuous calls is N. If N
calls are already being traced, the system does not trace any
newly accessed calls. If the number becomes less than N
because of the termination of some calls, the system
automatically traces new calls till the number of calls being
traced reaches N.
You can choose the message types by choosing trace events.
You can also choose one or more cells to trace.
28.4.10 Cell Tracing

Table 1.1 describes the cell tracing.
Table 1.1 Cell tracing
Task
Cell tracing
Function
This task is performed to trace NBAP common messages or
USER_VOLUME events in one or more specified cells. The
USER_VOLUME event includes some customized messages of UE
statistical information.
You can specify one or more cells to trace.
You can also choose the message types by choosing trace events.
A maximum of 32 cells can be traced simultaneously.
28.4.11 OS Tracing
This task is performed to trace the internal messages of the Operating System (OS).
For details, refer to Table 1.1.

12
Table 1.1 OS tracing

Task
Function
OS tracing
This task is performed to trace messages between:
The exchange module of the BAM and the internal modules of

the boards in the WRBSs
The internal modules of boards in the WRBSs.
In addition to the messages between different modules, this task can

be performed to trace messages sent by and to a module itself.
You can choose the tracing types.
28.4.12 Redirect Tracing

This task is performed to trace the COM port printing information of a specified board
subsystem. For details, refer to Table 1.1.
Table 1.1 Redirect tracing
Task
Function
Redirect
This task is performed to redirect the COM port printing information of a
tracing
specified subsystem to the message browse window of the LMT.

To start a trace task, specify the subrack and slot numbers of the board
and the subsystem number.
28.4.13 CDT Tracing

Table 1.1 describes the Call Data Tracing (CDT) tracing.

13
Table 1.1 CDT tracing

Task
CDT tracing
Function
This task is performed to trace messages of a UE over standard
interfaces, on user plane, and on signaling plane during a call.
It helps you monitor the signaling exchange procedures over
standard interfaces and the user plane, in addition to the uplink and
downlink data during the whole call procedure.
To start a CDT, specify the UE to be traced.
You can also choose the interfaces and message types to trace.
A maximum of two CDT trace tasks can be performed
simultaneously.
Note:
The task of UE tracing (standard interface) and the task of CDT tracing cannot be
performed simultaneously for the same UE.
A maximum of six CDT and UE tracing (standard interface) tasks can be performed
simultaneously for different UEs. Among the six tasks, at most two CDT trace tasks
can be performed simultaneously.
A maximum of 15 IOS and UE tracing (signaling plane and user plane) tasks can be
performed simultaneously. Among the 15 tasks, at most 8 IOS or UE tracing
(signaling plane and user plane) tasks can be performed simultaneously.
28.4.14 Location Tracing

Table 1.1 describes the location tracing.
Table 1.1 Location tracing
Task
Function
Location
This task is performed to trace the results of a location tracing
Tracing
initiated by the CN. This task can also simulate the CN to initiate a
location tracing and trace the results.
Based on different settings, this task can simulate location tracing for
different situations.

14
28.5 Capabilities
None.
28.6 Implementation
28.6.1 Routine Operations of the Tracing Function
This section describes the following:
Creating Trace Tasks
Browsing Traced Messages Online
Saving Tracing Results
Stopping/Restarting Trace Tasks
Closing Trace Tasks
Browsing Traced Messages Offline
28.6.2 Creating Trace Tasks

I. Task Description
This task is performed to create a trace task. After a task is created, system begins
tracing messages. The results are displayed in the message browse window in real
time.
Note:
The trace task occupies a lot of resources. Therefore, execute the task when the
system is not busy.
II. Prerequisites
There are two prerequisites:
The LMT is started.
You have logged in to the BSC6800 system with an account authorized for the
tracing management.
III. Operation Procedure

Take creating the task of tracing messages of MTP3-B as an example. The procedure
is as follows:
1)
Click the Maintenance tab on the Local Maintenance Terminal window.

15
2)
Unfold the Trace Management node, and then unfold the Interface Trace Task
node.
The tracing objects are displayed, as shown in Figure 2.1.
Figure 2.1 Choosing a tracing object
Note:
For the location tracing, unfold the Trace Management node, and then unfold the
Location Trace node. Choose Location Reporting Control.
3)
Double-click the tracing object MTP3B.

The MTP3B Protocol Tracing dialog box as shown in Figure 3.1 opens up for
parameter setting.

16
Figure 3.1 MTP3B Protocol Tracing dialog box
Note:
If the Autosave to File checkbox is selected, the system saves the tracing results in
the .tmf format. For details, refer to 28.6.4"Saving Tracing Results."
4)
Set the parameters in the dialog box.
5)
Click OK to start the trace task.

The system displays traced signaling messages in the message browse window
in real time, as shown in Figure 5.1.

17
Figure 5.1 Message browse window
28.6.3 Browsing Traced Messages Online

I. Task Description
This task is performed to browse or query the traced messages in the message
browse window after the trace task is created.
II. Prerequisites
A trace task is started.
Traced messages are reported.

1)
Browse or query the traced messages in the message browse window.

18
Note:
You can right-click the message browse window, and perform the following
operations:
Choose Stop Trace Task to stop the task.
Choose Restart Trace Task to restart the task.
Choose Auto Scroll, and the messages in the window are automatically refreshed
in real time and are scrolled upward.
Choose Clear Messages to remove all messages in the window.
Choose Close All xxx Message Trace Tasks (xxx stands for specific trace tasks)
to close the trace tasks.
2)
Choose Property to query the task properties.
To learn about the details of a message, double-click it.

The Message Browser dialog box as shown in Figure 2.1 opens up, displaying
the details of the message.
Figure 2.1 Message Browser dialog box
28.6.4 Saving Tracing Results

There are two ways of saving tracing results: auto saving and manual saving.
19
I. Task Description
This task is performed to save the traced messages in the LMT.
II. Prerequisites
Traced messages are reported.
III. Automatically Saving Traced Messages

When a trace task is created, the default setting is to save all messages displayed in
the message browse window in the .tmf format.
The default saving path is <Installation directory>\client\output\main\BSC6800\<LMT
software version number>\trace.
Note:
The system saves every 5,000 messages in a file. From message 5,001, a serial
number is added in the file name. For example, MTP3-B messages 5,001 to
10,000 are saved in a file with the name of office name_MTP3B_yy-mm
-dd_hh-mm-ss_1.tmf.
You can use the Trace Viewer to browse offline the messages saved in the .tmf
format. For detail, refer to 28.6.7"Browsing Traced Messages Offline."
IV. Manually Saving Traced Messages

When the trace task is running, you can manually save all or part of the messages in
the message browse window in the .tmf, .txt or .csv format. The procedure is as
follows:
1)
Create a trace task in the LMT. For detail, refer to 28.6.2"Creating Trace Tasks."
2)
Right-click the message browse window, and choose Save All Messages on the
shortcut menu. Or choose the messages to be saved, right-click them and
choose Save Selected Messages on the shortcut menu.
The Save dialog box as shown in Figure 2.1 opens up.

20
Figure 2.1 Save dialog box

3)
Enter a file name, and choose the file type and saving path.
The
default
saving
path
directory>\client\output\main\BSC6800\<LMT
software
is
<installation
version>\trace.
The
default name is office name_trace type _yy-mm-dd_hh-mm-ss.tmf.

4)
Click Save to save the file in the specified path.
28.6.5 Stopping/Restarting Trace Tasks

I. Task Description
You can stop a trace task when it is not needed, and restart it later.
II. Prerequisite

To stop the trace task, right-click the message browse window, and choose Stop
Trace Task.
To restart the trace task, right-click the message browse window, and choose Restart
Trace Task.

21
28.6.6 Closing Trace Tasks

I. Task Description
This task is performed to close a trace task when it is not needed any more.
II. Prerequisite

You can choose either of the following operations to close the task:
Click
in the top right corner of the message browse window.
Right-click the message browse window, and choose Close All xxx Message
Trace Tasks (xxx stands for specific trace tasks, for example, Close All
MTP3BMessage Trace Tasks).
28.6.7 Browsing Traced Messages Offline

I. Task Description
This task is performed to use the Trace Viewer to browse offline the traced messages
saved in the .tmf format.
Note:
You can find the .txt or .csv files in the saving directory. You can double-click them to
read the traced messages.
II. Prerequisite
The traced messages have been saved in the .tmf format.

To browse traced messages offline, perform the following steps:
1)
Choose either of the following ways to start Trace Viewer.
Click
on the toolbar on the Local Maintenance Terminal window.
Choose Start > All Programs > Huawei Local Maintenance Terminal >
Trace Viewer.
The Open dialog box as shown in Figure 1.1 opens up.

22
Figure 1.1 Opening a file containing traced messages

2)
Choose a file and click Open. Or double-click the file.

The default path for the files is <installation
directory>\client\output\main\BSC6800\<LMT software version number>\trace.
The window displays traced messages saved in the file, as shown in Figure 2.1.

23
Figure 2.1 Displaying traced messages

3)
Browse these messages, or double-click one to learn about its details, as shown
in 28.6.3 IIIFigure 2.1.
4)
To browse other saved messages, choose File > Open. In the Open dialog box,
choose and open files to read the traced messages saved in the files.
Note:
In the Trace Viewer, you can also perform the following operations:
Right-click and choose Save All Messages to save all the messages in the
window in .tmf or .txt format.
Right-click and choose Save Selected Messages to save selected messages in

.tmf or .txt format.
Right-click and choose Find to locate a message.
Right-click and choose Properties to learn about the properties of the task that the
tracing result corresponds to.
Click any button on the title bar to sequence the messages in the window by No.,
time, subrack No., direction, DPC, or content.

24
28.6.8 Alarms
None.
28.6.9 Counters
None.
28.7 References
None.

25

28 Tracing Function

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

28 Tracing Function

Hochgeladen von

Copyright:

Verfügbare Formate

RAN Feature Description

RAN Feature Description

28.6.9 Counters........................................................................................................... 28-23

Huawei Technologies Proprietary

RAN Feature Description

Huawei Technologies Proprietary

RAN Feature Description

Huawei Technologies Proprietary

RAN Feature Description

Chapter 28 Tracing Function

Chapter 28 Tracing Function

Message Tracing over Standard Interfaces

Message Tracing of Transport Network Layer

UE tracing (on the user plane and the signaling plane)

UE tracing (standard interface)

Huawei Technologies Proprietary

RAN Feature Description

Chapter 28 Tracing Function

The cell tracing is used to measure the following two types of

Common signaling messages on the Iub interface of one or

Customized messages that contain information about UEs in

Standard interface messages of the UE

Messages on the user plane and signaling plane of the UE

OS tracing is used to trace the messages inside the Operating

Redirect tracing is used to trace the print information of the serial

ports on the board subsystem.

OM-DBG is an internal module of the SPU. It has the following

Receiving tasks sent from the BAM

Generating filter tables

Maintaining the message channels between the trace tasks and

Informing the traffic processing module of the change of trace

Providing message channels from the traffic processing module

Providing interfaces for reporting data messages of the traffic

Providing interfaces for flow control

Huawei Technologies Proprietary

RAN Feature Description

Chapter 28 Tracing Function

Back Administration Module

International Mobile Equipment Identity

International Mobile Subscriber Identity

Local Maintenance Terminal

Packet Temporary Mobile Subscriber Identity

Radio Access Network

Signaling ATM Adaptation Layer

Signaling Connection and Control Part

Signaling process Unit

Temporary Mobile Subscriber Identity

Location Area Code

Local Area Network

Routing Area Code

Universal Mobile Telecommunications System

Huawei Technologies Proprietary

RAN Feature Description

Chapter 28 Tracing Function

28.2.2 Software Releases

V100R002 and later releases

CDT tracing and UE trace (standard interface message)

Call tracing and cell tracing

28.3.2 On Other Features

Huawei Technologies Proprietary

RAN Feature Description

Chapter 28 Tracing Function

28.4 Technical Description