Message Tracing (GBSS17.0 - Draft A)

GSM BSS
GBSS17.0
Message Tracing Feature Parameter

Description
Issue
Draft A
Date
2014-07-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue Draft A (2014-07-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
GSM BSS
Message Tracing Feature Parameter Description
Contents
Contents
1 About This Document..................................................................................................................1
1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................1
2 Overview.........................................................................................................................................3
2.1 Introduction....................................................................................................................................................................3
2.2 NEs Supporting the Feature............................................................................................................................................3
3 Interface Message Tracing...........................................................................................................5

3.1 Overview of Message Tracing........................................................................................................................................6
3.2 Architecture of Interface Message Tracing....................................................................................................................6
3.3 Basic Flow......................................................................................................................................................................7
3.4 Tracing Management......................................................................................................................................................8
4 User Signaling Tracing...............................................................................................................10

4.1 Overview of User Signaling Tracing............................................................................................................................11
4.2 Single User CS Tracing................................................................................................................................................11
4.2.1 Selecting Characteristic Word...................................................................................................................................11
4.2.2 Selecting Type of Interface to Be Traced..................................................................................................................12
4.3 Single User PS Tracing.................................................................................................................................................12
4.3.1 Selecting Characteristic Word...................................................................................................................................12
4.3.2 Selecting Type of Interface to Be Traced..................................................................................................................12
5 Parameters.....................................................................................................................................13
6 Counters........................................................................................................................................14
7 Glossary.........................................................................................................................................15
8 Reference Documents.................................................................................................................16

ii
GSM BSS
1 About This Document
About This Document
1.1 Scope
This document describes Message Tracing, including its technical principles, related features,
network impact, and engineering guidelines.
This document covers the following features:
l
MRFD-210801 Interface Message Tracing
MRFD-210802 User Signaling Tracing
1.2 Intended Audience

This document is intended for personnel who:
l
Need to understand the features described herein
Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l
Feature change
Changes in features of a specific product version
Editorial change
Changes in wording or addition of information that was not described in the earlier version
Draft A (2014-07-30)
Compared with 01 (2014-04-30) of GBSS16.0, Draft A (2014-07-30) of GBSS17.0 includes the
following changes.

GSM BSS
1 About This Document
Change Type
Change Description
Parameter Change
Feature change
Added the description about

requiring causes for starting a
message tracing in 2.1
Introduction.
None
Editorial change
None
None

GSM BSS
2 Overview
Overview
2.1 Introduction
The MRFD-210801 Interface Message Tracing feature provides online or offline interface
message tracing and retrospection and therefore facilitates device management. The integrated
interface message tracing simplifies the procedure for monitoring radio interfaces and therefore
is useful for network optimization and troubleshooting.
The MRFD-210802 User Signaling Tracing feature enables operators to easily monitor the
interface signaling for certain MSs and therefore is useful for network optimization and
troubleshooting. While user signaling is traced, personal information of some subscribers, such
as IMSI, MSISDN, and IMEI may be required. To secure the personal information, User
Signaling Tracing enables the personal information to be processed anonymously. You are
advised to comply with applicable laws or corporate privacy regulations when executing the
task and take ample measures to fully protect user data, such as enabling the anonymization
function, typing the causes for starting a message tracing, and deleting the folders saving user
tracing records after anonymization.
2.2 NEs Supporting the Feature

Table 2-1 NEs supporting the feature
Feature Name
BSC6900
BSC6910
GBTS
eGBTS
Interface
Message
Tracing
User Signaling
Tracing

GSM BSS
2 Overview
NOTE
indicates that the NE supports this feature. indicates that the NE does not support this feature.

GSM BSS
3 Interface Message Tracing
Interface Message Tracing
This section describes the architecture, basic flow, and tracing management of interface message
tracing.

GSM BSS
3.1 Overview of Message Tracing

The Interface Message Tracing feature enables interface messages to be traced in online mode
and reviewed in offline mode.
Huawei MBSC provides the integrated interface message tracing for both the GSM base station
system (GBSS) and radio access network (RAN) system.
This feature enables users to trace interface messages in the GBSS or RAN system can be traced
in real time, stop message updating, save the traced messages, review message tracing results,
and check the time when the messages are sent. This way, the maintenance personnel can
accurately locate and solve problems. In addition, all the interfaces have the condition filtering
function that helps the maintenance personnel reduce the number of traced messages, improving
the tracing accuracy.
This feature also simplifies the process of monitoring the signaling over the radio transmission
interfaces and facilitates network optimization and fault rectification.
3.2 Architecture of Interface Message Tracing

Figure 3-1 shows the architecture of interface message tracing.
Figure 3-1 Architecture of interface message tracing
NMS: short for Network Management System. The NMS may be from another vendor or be
developed by the operator. It is interconnected with Huawei Element Management System
(EMS) over the northbound interface (NBI). The NMS analyzes the traced interface messages,
therefore facilitating network optimization and troubleshooting.
LMT: short for Local Maintenance Terminal. The LMT provides the interface message tracing
function and enables operators to view the message tracing results in offline mode.

GSM BSS
EMS: short for Element Management System. The EMS is used for NE operation and
maintenance. The interface message tracing functions provided by the EMS are as follows:
message parsing, message comparison, message reviewing, and message filtering. Huawei EMS
is connected to an MBSC over a Man Machine Language (MML) interface. Over the MML
interface, files regarding interface messages are transmitted using the File Transfer Protocol
(FTP).
NE: short for Network element. An NE collects and reports traced interface messages.
In conclusion, the EMS (U2000) initiates a tracing task and sends to the NE the requirements
of the tracing task (including the interface messages to be traced and filtering conditions). The
NE collects the traced interface messages in accordance with the requirements and reports the
results to the EMS.
3.3 Basic Flow

The basic flow of interface message tracing involves the following aspects:
l
Starting an interface message tracing task
Deleting a message tracing task
Collecting and reporting traced messages to the NMS by the NE
In addition, the comparison results of the traced messages can be exported by using the
U2000, and be submitted to the NMS for further analysis.
l
Starting an interface message tracing task

An interface message tracing task can be created and started on the U2000 client, and the
related command is sent to the NE.
After receiving the command, the OM main control module of the NE allocates an ID for
this task, and then forwards the task to the trace processing module on a specified board.
Then, the trace processing module on the board saves the preset requirements and filtering
conditions to a local file.
Collecting and reporting traced messages to the NMS by the NE

The trace processing module on the specified board captures the interface messages that
fulfill the requirements and filtering conditions, and then reports these messages to the OM
main control module.
After that, the OM main control module of the NE reports the related interface message to
the U2000 based on task ID.
If a scheduled tracing task is started, the OM main control module of the NE saves the
traced interface messages as a file and transmits the file to the U2000 using the FTP.
Finally, the U2000 parses the traced messages and saves the results to the database.
Deleting an interface message tracing task

An interface message tracing task can be deleted on the U2000 client, and the related
command is sent to the NE.
After receiving the command, the OM main control module of the NE forwards this
command to the trace processing module of a specified board. Then, the board deletes this
task.

GSM BSS
3.4 Tracing Management

When the NE starts a tracing task, the specified interface messages are traced. In this process,
the tracing task can be deleted or stopped. Figure 3-2 shows the position of the BSC6900 in the
network and its external interfaces.
Figure 3-2 Position of the BSC in the network and its external interfaces
A interface message tracing

A interface message tracing involves the following messages:
BSSAP, SCCP, SCTP, M3UA, MTP3, and MTP2.
Abis interface message tracing-GBTS

Abis interface message tracing consists of Abis interface CS message tracing and Abis
interface PS message tracing. The Abis interface circuit switched (CS) message tracing
involves the radio signaling link (RSL), operation and maintenance link (OML), extended
signaling link (ESL), extended maintenance link (EML), and link access procedure on the
D channel (LAPD) messages. Among these messages, LAPD messages are selected and
filtered by site number or TRX number; the RSL, OML, ESL, and EML messages are
selected and filtered by message type, such as measurement report (MR), paging message,
and channel request message. The packet switched (PS) messages over the Abis interface
are selected and filtered by cell and TRX.

GSM BSS
Abis interface message tracing-eGBTS

Abis interface message tracing consists of Abis interface CS message tracing and Abis
interface PS message tracing. The Abis interface CS message tracing involves the RSL,
CSL, and SCTP messages. Among these messages, RSL messages are selected and filtered
by message type, such as MR, page message, or channel request message. CSL is selected
and filtered by message type. Stream Control Transmission Protocol (SCTP) messages are
selected and filtered by SCTP link identifier and message type. The PS messages over the
Abis interface are selected and filtered by cell or TRX.
Pb interface message tracing

Application layer messages and LAPD messages can be traced over the Pb interface. The
LAPD messages can be traced by timeslot number and the application layer messages can
be traced by message type (for example, paging message) or by site number.
NOTE
The BSC6910 does not support the Pb interface message tracing.

The eGBTS does not support the LAPD message tracing.
Um interface message tracing

The Um interface tracing consists of Um interface CS message tracing and Um interface
PS message tracing. The Um interface CS messages are selected and filtered by cell and
TRX, and the Um interface PS messages can be selected and filtered by message type, such
as empty paging message, system information, and data block.
Gb interface message tracing

The Gb interface message tracing consists of Gb interface PTP message tracing and Gb
interface SIG message tracing in the PS domain.
Group call message tracing

In a group call message tracing, VGCS messages and VBS messages are traced over the
A, Abis, and Um interfaces. These messages are used to analyze the causes of the call
procedure failure.
BSC-CBC interface message tracing

In a BSC-CBC interface message tracing, the interface signaling between the BSC and the
Cell Broadcast Center (CBC) is traced. The signaling is used to locate faults that occur
during message query, BIND, or SOCKET connection.
Inter-BSC interface message tracing

In an inter-BSC interface tracing, the messages for common measurement and information
exchange between the BSCs are traced. These messages are used to locate faults that occur
in the common measurement procedure.
Ater interface CS message tracing

CS signaling messages are traced over the Ater interface. The Ater interface is used for the
connection between the BM and the TC in the case that the TC is configured at the MSC
side.
NOTE
The BSC6910 does not support CS Ater interface message tracing.

GSM BSS
4 User Signaling Tracing
User Signaling Tracing
This section describes the MRFD-210802 User Signaling Tracing feature.

10
GSM BSS
4.1 Overview of User Signaling Tracing

Single user tracing is performed by entering the characteristic identities of the MS on the BSC
LMT or the NMS. The characteristic identities include IMSI, TMSI, MSISDN, and IMEI. The
host parses the signaling messages of each call. If the information about an MS matches the
characteristic identities of the MS to be traced, the signaling of this call is reported to the OMC
for display. The User Signaling Tracing feature enable users to trace signaling messages of an
MS on different interfaces, save the messages, and review the message tracing result. This way,
the number of traced messages on each interface can be reduced, improving the troubleshooting
efficiency and facilitating the problem locating of a single MS.
User signaling tracing is classified into the following types:
l
Single user CS tracing
Single user PS tracing
4.2 Single User CS Tracing

In a single user CS message tracing, you can specify the MS to be traced by IMSI, TMSI,
MSISDN, or IMEI, and the call information associated with the MS is displayed on the LMT.
The single user CS tracing supports the following functions:
l
Tracing messages by specifying a characteristic identity including TMSI, IMSI, MSISDN,

IMEI, CHANINFO, and CELLID
Tracing user messages on the A, Abis, Um, and LB interfaces
4.2.1 Selecting Characteristic Word

You can trace CS messages of a specified MS by selecting a characteristic identity. After any
type of a characteristic identity is selected, the host automatically sends to the LMT the messages
with the specified characteristic identity.
TMSI: When the MS accesses the network with its TMSI, you can trace the signaling messages
in the call by specifying the TMSI of the MS.
IMSI: When the MS accesses the network with its IMSI, you can trace the signaling messages
in the call by specifying the IMSI of the MS.
MSISDN: If you attempt to trace an MS by MSISDN, use the number of the peer MS. That is,
if the calling MS is to be traced, you need to set the MSISDN to that of the called MS. If the
called MS is to be traced, you need to set the MSISDN to that of the calling MS, that is, the
incoming number displayed on the called MS.
IMEI: When the MS accesses the network with its IMEI, you can trace the MS by its IMEI.
CHANINFO: used to trace all the calls on a specified TCH
CELLID: It is used to trace information about all calls in a specified cell. However, measurement
report messages of calls in the cell are controlled by the All Measurement Reports option. If
this option is selected, all measurement report messages of all calls can be traced. If this option
is not selected, measurement report messages of a maximum of six calls can be traced.

11
GSM BSS
NOTE
l Check the reallocation policy on the MSC side when tracing user signaling by TMSI or IMSI of an
MS. If the TMSI reallocation is enabled on the MSC side, you may fail to trace the user signaling of
the specified MS because the TMSI may change after reallocation. If the TMSI is assigned to an MS
by the MSC, the MS access the network with its TMSI. In this case, you may fail to trace the MS by
its TMSI.
l Enable the MSC to obtain the IMEI of an MS when tracing user signaling by IMEI.
4.2.2 Selecting Type of Interface to Be Traced

You can trace the user messages on the A, Abis, Um, and LB interfaces simultaneously or
independently. The messages traced over multiple interfaces can be displayed on the same
window of the LMT.
4.3 Single User PS Tracing

In a single user PS message tracing, you can specify the MS to be traced by IMSI or TLLI, and
the information on the PS service associated with the MS is displayed on the LMT.
The single user PS tracing supports the following functions:
l
Tracing the messages of a specified MS by IMSI or TLLI
Tracing the messages on the Abis interface, Um interface, and Gb interface
4.3.1 Selecting Characteristic Word

You can trace the PS messages of a single MS by characteristic identity. After either type of
preceding characteristic identities is selected, the host automatically sends to the LMT the
messages with the characteristic identity.
IMSI: When the MS accesses the network with its IMSI, you can trace signaling messages by
specifying the IMSI.
TLLI: You can trace an MS by specifying its TLLI.
The traced PS messages of a single MS include the messages with the specific characteristic
identity and the messages involved in the same call procedure with the specific characteristic
identity.
4.3.2 Selecting Type of Interface to Be Traced

You can trace the user PS messages on the Abis, Um, and Gb interfaces simultaneously or
independently. You can trace only the PTP messages on the Gb interface. The messages traced
over multiple interfaces can be displayed on the same window of the LMT.

12
GSM BSS
5 Parameters
Parameters
There are no specific parameters associated with this feature.

13
GSM BSS
6 Counters
Counters
There are no specific counters associated with this feature.

14
GSM BSS
7 Glossary
Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

15
GSM BSS
8 Reference Documents
Reference Documents
There are no specific reference documents associated with this feature.

16

Message Tracing (GBSS17.0 - Draft A)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Message Tracing (GBSS17.0 - Draft A)

Uploaded by

Copyright:

Available Formats

GSM BSS

Message Tracing Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Issue Draft A (2014-07-30)

Huawei Proprietary and Confidential

3 Interface Message Tracing...........................................................................................................5

4 User Signaling Tracing...............................................................................................................10

Issue Draft A (2014-07-30)

Huawei Proprietary and Confidential

1 About This Document

About This Document

MRFD-210801 Interface Message Tracing

MRFD-210802 User Signaling Tracing

1.2 Intended Audience

Need to understand the features described herein

Work with Huawei products

1.3 Change History

Huawei Proprietary and Confidential

1 About This Document

Added the description about

Issue Draft A (2014-07-30)

Huawei Proprietary and Confidential

2.2 NEs Supporting the Feature

Issue Draft A (2014-07-30)

Huawei Proprietary and Confidential

Issue Draft A (2014-07-30)

Huawei Proprietary and Confidential

3 Interface Message Tracing

Interface Message Tracing

Issue Draft A (2014-07-30)

Huawei Proprietary and Confidential

3 Interface Message Tracing

3.1 Overview of Message Tracing

3.2 Architecture of Interface Message Tracing

Huawei Proprietary and Confidential

3 Interface Message Tracing

3.3 Basic Flow

Starting an interface message tracing task

Deleting a message tracing task

Collecting and reporting traced messages to the NMS by the NE

Starting an interface message tracing task

Collecting and reporting traced messages to the NMS by the NE

Deleting an interface message tracing task

Issue Draft A (2014-07-30)

Huawei Proprietary and Confidential

3 Interface Message Tracing

3.4 Tracing Management

A interface message tracing

Abis interface message tracing-GBTS

Issue Draft A (2014-07-30)

Huawei Proprietary and Confidential

3 Interface Message Tracing

Abis interface message tracing-eGBTS

Pb interface message tracing

The BSC6910 does not support the Pb interface message tracing.

Um interface message tracing

Gb interface message tracing

Group call message tracing

BSC-CBC interface message tracing