SJ-20121213161606-024-ZXWR RNC (V3.12.10) Calling Trace Operation Guide PDF

ZXWR RNC
Radio Network Controller

Calling Trace Operation Guide
Version:V3.12.10
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2013 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 20130407 First Edition
Serial Number: SJ-20121213161606-024
Publishing Date: 2013-04-07(R1.0)
SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Signaling Tracing Software Functions .................................................................. 1-1
1.2 Signaling Tracing Software Structure ................................................................... 1-1
1.3 Deployment ....................................................................................................... 1-2
1.4 Recommended Server Configurations ................................................................. 1-3
1.5 Basic Concepts .................................................................................................. 1-3
Chapter 2 Software Installation and Startup............................................ 2-1

2.1 RCT Installation Flow ......................................................................................... 2-1
2.2 Installing the RCT Server Software...................................................................... 2-1
2.3 Installing the RCT Client Software ....................................................................... 2-7
2.4 Starting the RCT Server Program ...................................................................... 2-10
2.5 Starting the RCT Client Program ....................................................................... 2-12
Chapter 3 Signaling Tracing Operation .................................................... 3-1

3.1 Overview ........................................................................................................... 3-1
3.2 NE Management ................................................................................................ 3-1
3.2.1 NE Management Window ......................................................................... 3-1
3.2.2 Adding an NE........................................................................................... 3-3
3.2.3 Link Operations........................................................................................ 3-4
3.3 Subscriber Tracing ............................................................................................. 3-6
3.3.1 Subscriber Trace Window ......................................................................... 3-6
3.3.2 Task Operation Rights .............................................................................. 3-9
3.3.3 Creating a Task ...................................................................................... 3-10
3.3.4 Monitoring a Task ................................................................................... 3-14
3.3.5 Monitoring Multiple Tasks........................................................................ 3-17
3.3.6 Viewing Data.......................................................................................... 3-20
3.3.7 Opening a Historical Data File ................................................................. 3-21
3.3.8 Viewing Historical Data Files ................................................................... 3-22
3.3.9 Setting Client Parameters ....................................................................... 3-23
3.3.10 Creating Multiple Signaling Tracing Tasks Simultaneously....................... 3-23
3.3.11 Replaying a Historical Data File ............................................................. 3-26
3.3.12 Importing a Decoding Library ................................................................ 3-26
3.3.13 Searching Tasks................................................................................... 3-27

3.3.14 MML Commands Related to Signaling Tracing Tasks.............................. 3-29
3.4 Offline Tool....................................................................................................... 3-31
Appendix A Common Problems and Troubleshooting .......................... A-1

A.1 The State of a Task Is Always STARTING............................................................ A-1
A.2 RCT Server Startup Failure ................................................................................ A-1
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II

About This Manual
Purpose
The NetNumen U31 R18 MOSS signaling tracing software performs signaling tracing for
NEs (RNC or BSC) of various systems, including UMTS, GSM, and TD-SCDMA.
This manual describes the basic functions, installation procedure, and operations of the
signaling tracing software (in the following sections, the software is called RCT for short).
Intended Audience
l Network optimization engineers
l Maintenance engineers
l Testing engineers
What Is in This Manual
Chapter Summary
Chapter 1, Overview Describes the basic functions, installation modes, software

structure, deployment modes, recommended server
configurations, and some basic concepts of the RCT.
Chapter 2, Software Installation and Describes the installation and startup procedure of the RCT.
Startup
Chapter 3, Signaling Tracing Describes the operations related to NE management and

Operations subscriber tracing in the RCT.
Appendix A, Common Problems and Describes some common problems in using the RCT and the
Troubleshooting relevant troubleshooting methods.
Related Documentation
The following documentation is related to this manual:
l NetNumen U31 R18 Unified Element Management System Security Management
Operation Guide
l NetNumen U31 R18 Unified Element Management System System Management
Operation Guide
Conventions
This manual uses the following typographical conventions:
Typeface Meaning
Note: provides additional information about a certain topic.

II

Chapter 1
Overview
Table of Contents
Signaling Tracing Software Functions.........................................................................1-1
Signaling Tracing Software Structure..........................................................................1-1
Deployment................................................................................................................1-2
Recommended Server Configurations ........................................................................1-3
Basic Concepts ..........................................................................................................1-3
1.1 Signaling Tracing Software Functions

The signaling tracing software is a component of the MOSS system. In this document, it
is called RCT for short.
The RCT is used to locate and analyze problems when the network becomes faulty,
the calls are disconnected, the services become abnormal, or users perform network
optimization. With RCT, users can trace and observe the real-time signaling data and
measurement reports, which facilitates maintenance personnel to locate faults and
perform system debugging.
The RCT implements real-time signaling tracing and management for multiple NEs. It
supports real-time signaling tracing for multiple 2G/3G NEs (RNCs or BSCs).
In the RCT, the signaling tracing for an NE is implemented in the form of a signaling tracing
task. The traced objects include terminals, cells, and network interfaces.
1.2 Signaling Tracing Software Structure

The RCT uses client/server structure, which includes multiple clients and a server.
l The clients are connected to the server. Users can customize signaling tracing tasks,
start signaling tracing tasks, and query signaling tracing results at the clients.
l The server is connected to an actual NE (RNC or BSC), obtains and forwards the
traced signaling messages. The server supports multi-client access.
After the RCT is started at a client, it is connected to the RCT server through the RCT client,
and the server is directly connected to an NE or connected to an NE through a forwarding
module, see Figure 1-1.
1-1

ZXWR RNC Calling Trace Operation Guide
Figure 1-1 Software System Structure
1.3 Deployment
The RCT uses client/server structure. According to the server position, there are two server
deployment modes:
l Independent server deployment
l Co-EMS server deployment
In both modes, it is recommended to separately install the RCT software at a disk partition.
Independent Server Deployment

In the independent server deployment mode, the RCT server is deployed at the EMS side,
that is, at the network segment where EMS is located. The RCT server is separated from
the EMS server. The RCT server software is operating independently.
The RCT server software communicates with an NE (RNC or BSC) through the forwarding
module of Operation & Maintenance Module (OMM). Figure 1-2 shows the deployment
mode.
Figure 1-2 RCT Server Software Installed Independently
1-2

Chapter 1 Overview
Co-EMS Server Deployment

In the co-EMS server deployment mode, the RCT server software is integrated into the
EMS server. With this deployment mode, RCT and EMS shares the same server, which
saves the hardware cost. To use this deployment mode, it is necessary to ensure that the
EMS server has sufficient processing capability. Figure 1-3 shows the deployment mode.
Figure 1-3 RCT Server Software Integrated into the EMS Server
1.4 Recommended Server Configurations

Table 1-1 lists the recommended server configurations in the independent server
deployment mode.
Table 1-1 Recommended Server Configurations in the Independent Server Deployment

Mode
Device Configuration
Recommended server SUN v4 SPARC Enterprise T5220
Central Processing Unit (CPU) 64 virtual CPUs
Physical memory 32 GB
1.5 Basic Concepts

Signaling tracing is implemented in the form of a task. To create a signaling tracing task,
it is necessary to specify the task name, task description, task type, traced objects, and
object parameters to be traced.
Before using the RCT software, users should grasp some basic knowledge of RCT, which
are described in the following sections.
NE States
In the RCT, users should create an NE according to the actual IP address and port number
of the corresponding actual NE (RNC or BSC). Users can trace the signaling of the NE only
after the connection between the created NE and the actual NE (RNC or BSC) is created.
An NE created in the RCT can have four states: Off, On, Connecting, and
Disconnecting. Figure 1-4 shows the conversion relation among the four states.
1-3

Figure 1-4 NE State Conversion
l After an NE is created in the RCT, the initial state of the created NE is Off.
l After the link between the created NE and the actual NE is established successfully,
the state of the created NE becomes On. If the link between the created NE and the
actual NE fails to be established, the state of the created NE remains Connecting.
l After the link between the created NE and the actual NE is broken manually, the state
of the created NE first becomes Disconnecting, then becomes Off.
l If the link between the created NE, which is in the On state, and the actual NE is
broken, the state of the created NE becomes Connecting. If the link between the two
is recovered, the state of the created NE becomes On.
Task States
A complete life cycle of a signaling tracing task is:
l Creating the signaling tracing task
l Starting the signaling tracing task
1-4

Chapter 1 Overview
l Stopping the signaling tracing task

Figure 1-5 shows the conversion relation among the task states.
Figure 1-5 Task State Conversion
l After a signaling tracing task is created, the initial state of the task is STOP.
l After the task is manually started, the task state becomes START. If the task fails to
be started, the task state remains STARTING.
For an NE which is in the On state, after a sub-task corresponding to it is started,

the sub-task state becomes START.
For an NE which is in the Off state, after a sub-task corresponding to it is started,

the system will prompt that the NE is not connected.
1-5

For an NE which is in the Connecting state, after a sub-task corresponding to it

is started, the sub-task state becomes STARTING. After the NE state becomes
On, the sub-task state becomes START.
l After the task is manually stopped, the task state becomes STOP. If the task fails to
be stopped, the task state remains STOPPING.
For an NE which is in the On state, after a sub-task corresponding to it is stopped,
the sub-task state becomes STOP.
For an NE which is in the Connecting state, after a sub-task corresponding to it
is stopped, the sub-task state becomes STOPPING. After the NE state becomes
On, the sub-task state becomes STOP.
l If the NE corresponding to a task in the START state is disconnected, the task state
becomes SYNC. The signaling tracing software performs synchronization with the
actual NEs every 30 minutes, and in such cases, the states of the corresponding
signaling tracing tasks become SYNC.
l After an NE link is recovered or the automatic synchronization is completed, the
corresponding task state becomes START.
l Only the tasks in the START state can collect the signaling of the corresponding NEs.
Task Types
Table 1-2 describes the types of tasks traced in RCT.
Table 1-2 Task Types
Task Type Supported System Task Purpose
Tracing the signaling related to UEs of UMTS,

UE UMTS, TD-SCDMA, GSM
TD-SCDMA, or GSM
CELL UMTS, TD-SCDMA, GSM Tracing the signaling related to cells
Tracing the signaling between RNC and core

OFFICE-IU UMTS, TD-SCDMA network, including PS domain tracing and CS
domain tracing
Tracing the signaling between RNC and an

OFFICE-IUB UMTS, TD-SCDMA Node B (including one or multiple physical cell
nodes)
Tracing the signaling between an RNC and its

OFFICE-IUR UMTS
neighbor RNCs
Tracing the common signaling of the Rnlc Iurg

OFFICE-IUR-G TD-SCDMA
interface
SM TD-SCDMA Tracing the signaling related to cell services
Tracing the signaling related to MBMS with a

MBMS UMTS, TD-SCDMA
specified Session ID or in a cell that has MBMS.
ABIS GSM Tracing the signaling related to the Abis.
1-6

Chapter 1 Overview
Task Type Supported System Task Purpose
GB GSM Tracing the signaling related to the GB interface
A GSM Tracing the signaling related to the A interface
Task Synchronization
A signaling tracing task can be synchronized with the actual NE (RNC or BSC) in the
following two ways:
l Timing synchronization: The RCT sends the task synchronization message to the
NEs every 30 minutes, and the software automatically sets the state of the started
signaling tracing tasks to SYNC, that is, the state of being synchronized.
Note:
During timing synchronization, do not perform any operation on the corresponding
signaling tracing tasks.
If a task exists at an NE but does not exist in RCT, the task is automatically deleted
by the NE.
If a task does not exist at an NE but exists in RCT, the NE automatically creates
the task and starts the task in RCT, and the task state becomes START.
l Non-timing synchronization: The RCT automatically initiates task synchronization

every time a link between RCT and an NE is established. If a link between RCT and
an NE is broken, the state of the corresponding task being started is set to SYNC,
and the task is synchronized when the link is reestablished.
1-7

This page intentionally left blank.
1-8

Chapter 2
Software Installation and
Startup
Table of Contents
RCT Installation Flow .................................................................................................2-1
Installing the RCT Server Software.............................................................................2-1
Installing the RCT Client Software ..............................................................................2-7
Starting the RCT Server Program.............................................................................2-10
Starting the RCT Client Program ..............................................................................2-12
2.1 RCT Installation Flow

The following describes the RCT installation and configuration flow:
1. Installation preparation
a. Install the Oracle 10g database.
b. Create a new instance for the RCT in the Oracle 10g database. In this document,
the instance is named as RCT.
2. Configure and start the message forwarding module in OMM: The OMM software
version package contains the message forwarding module.
3. Install the RCT server software.
4. Install the RCT client software.
The following sections only describe how to install the RCT sever software and the RCT
client software.
2.2 Installing the RCT Server Software

This procedure describes how to install the RCT server software in the Solaris operating
system.
Prerequisite
1. The Oracle 10g database is installed.
2. An independent disk space is reserved for the RCT server software on the server, and
the disk space is at least 60 GB. In the installation example given in this section, the
disk space path is /export/home/omc/rct.
3. A new instance named as RCT is created for the RCT. Pay attention that the instance
is different from the instance used in EMS. It is recommended to install the database
2-1

instance and the RCT server software on the same disk. In the following example, the
file saving path is /export/home/omc/rct.
Steps
1. Enter the RCT installation directory, and execute the following command to install the
RCT server software.
./setup.sh
2. Press Enter to use the default temporary installation file path, or enter the temporary
installation file path and press Enter. The ZTE RCT Setup - Select language window
is displayed.
3. Select English from the Language drop-down list box, and click Next. The ZTE RCT
Setup - License agreement window is displayed.
4. Select I accept the license agreement, and click Next. The ZTE RCT Setup - Select
installation style window is displayed, see Figure 2-1.
Figure 2-1 ZTE RCT Setup - Select Installation Style Window
According to the description in the Tips about current installation style area, select
the installation mode. Here, select Normal Installation and Server program.
5. Click Next. The ZTE RCT Setup - Network scale window is displayed.
At present, only Scale1 is available.
6. Click Next. The ZTE RCT Setup - Select Product window is displayed, see Figure
2-2.
2-2

Chapter 2 Software Installation and Startup
Figure 2-2 ZTE RCT Setup - Select Product Window
Select the product signaling tracing modules to be installed. For a description of the
modules, refer to Table 2-1.
Table 2-1 Signaling Tracing Modules
Module Description
UMTS RNC TRACE UMTS RNC V3 NE signaling tracing module, optional
COMMON Common function module on the signaling tracing server, mandatory
TD RNC TRACE TD-SCDMA RNC V3 NE signaling tracing module, optional
UROP BSC TRACE GSM BSC V4 NE signaling tracing module, optional
UROP RNC TRACE UMTS RNC V4 NE signaling tracing module, optional
UROP TDRNC TRACE TD-SCDMA RNC V4 NE signaling tracing module, optional
l If it is required to trace a GSM BSC V4 NE and a TD-SCDMA RNC V4 NE, select

COMMON, UROP BSC TRACE, and UROP TDRNC TRACE.
l If it is required to trace a GSM BSC V4 NE and a UMTS RNC V4 NE, select
COMMON, UROP BSC TRACE, and UROP RNC TRACE.
In the Program Area Path text box, enter the installation directory of the RCT server
software such as /export/home/omc/rct. Users can also click the Browse...
button to select the installation directory.
By default, Data Area Path and Program Area Path are consistent. Users can also
specify a different installation directory.
2-3

7. (Optional) Click Next. If the entered installation directory does not exist, the system
will prompt whether to create the directory. Click Yes.
8. Click Next. The ZTE RCT Setup - Database Connection Configuration window is
displayed, see Figure 2-3.
Figure 2-3 ZTE RCT Setup - Database Connection Configuration Window
For a description of the parameters in the ZTE RCT Setup - Database connection
config window, refer to Table 2-2.
Table 2-2 Database Connection Parameters
Parameter Value Description
Database Type Select Oracle from the drop-down list box
Oracle Connection Type Oracle database connection types, which can be

l sid
l servicename
Database IP or Hostname IP address or host name of the Oracle server

Floating IP address of the Oracle server used in the
dual-computer environment
Database Port Use the default value 1521
2-4

Parameter Value Description
Oracle SID or Service Name The parameter value varies in accordance with the
Oracle Connection Type parameter:
l If Oracle Connection Type is set to sid, set this
parameter to a database instance created for the
RCT, for example, RCT.
l If Oracle Connection Type is set to servicename,
set this parameter to the RCT database service
name, for example, teh IP address of the RCT
database server.
Database Superuser Name The system user name of the Oracle database
Password The password of the system user of the Oracle database
After setting the parameters, click Test Database Connection to verify whether the
database can be connected successfully.
9. After database connection is verified successfully, click Next. The ZTE RCT Setup -
Database Configuration window is displayed, see Figure 2-4.
Figure 2-4 ZTE RCT Setup - Database Configuration Window
Normally, there is no need to adjust the database file size.

10. Click Next. The ZTE RCT Setup - Host Information Configuration window is
2-5

Figure 2-5 ZTE RCT Setup - Host Information Configuration Window
In the The master server address or hostname text box, enter the IP address of the
RCT server.
11. Click Next. The ZTE RCT Setup - System Information Detection window is
displayed. The detection result Pass is displayed in the Detect Result column.
12. Click Next. The ZTE RCT Setup - Installation Information Confirm window is
displayed.
13. Confirm the installation information, and click Install. The ZTE RCT Setup - Unzip
and Copy Files window is displayed. The system starts decompressing and copying
the files.
14. After the files are decompressed and copied, click Next. The Confirm dialog box is
displayed, asking users whether to execute the SQL script.
15. Click Yes. The ZTE RCT Setup - Installation Database window is displayed. The
system starts installing the database.
16. After the installation is completed, click Next. The ZTE RCT Setup - Parameter set
window is displayed, see Figure 2-6.
2-6

Figure 2-6 ZTE RCT Setup - Parameter Set Window
Set Main node IP to the IP address of the RCT server, and use default values for other
parameters.
17. Click Save All, and click Next. The Confirm dialog box is displayed, asking whether
to initialize all the clients.
18. Click Yes. The ZTE RCT Setup - System Initialization window is displayed. The
system initialization starts.
19. After the initialization is completed, click Next. The ZTE RCT Setup - Installation
Finished window is displayed.
20. Click Finish. The RCT server software installation is completed.
End of Steps
2.3 Installing the RCT Client Software

This procedure describes how to install the RCT client software.
Steps
1. Enter the RCT installation directory, and double-click the setup.bat file to install the
RCT client software.
2. The Installation window is displayed. Press Enter to use the default temporary
installation file path.
Users can also enter a temporary installation file path and press Enter.
2-7

3. After the files are decompressed, the ZTE RCT Setup - Select Language window is
displayed. Select English from the Language drop-down list box.
4. Click Next. The ZTE RCT Setup - License Agreement window is displayed.
5. Select I accept the license agreement, and click Next. The ZTE RCT Setup - Select
Installation Style window is displayed, see Figure 2-7.
Figure 2-7 ZTE RCT Setup - Select Installation Style Window
According to the description in the Tips about current installation style area, select
the installation mode. Here, select Normal Installation and Client Program.
6. Click Next. The ZTE RCT Setup - Select Product window is displayed, see Figure
2-8.
2-8

Figure 2-8 ZTE RCT Setup - Select Product Window
Select the product signaling tracing modules to be installed. The descriptions of these
modules are the same as those described in 2.2 Installing the RCT Server Software.
In the Program Area Path text box, enter the installation directory of the RCT client
software. Users can also click the Browse... button to select the installation path.
By default, Data Area Path and Program Area Path are consistent. Users can also
specify a different installation directory.
7. Click Next. If the installation directory does not exist, the Confirm dialog box is
displayed, asking users whether to create the directory.
8. Click Yes. The ZTE RCT Setup - System Information Detection window is displayed.
The detection result Pass is displayed in the Detect Result column.
9. Click Next. The ZTE RCT Setup - Installation Information Confirm window is
displayed.
10. Confirm the installation information, and click Install. The ZTE RCT Setup - Unzip
and Copy Files window is displayed. The system starts decompressing and copying
the files.
11. After the files are decompressed and copied, click Next. The ZTE RCT Setup -
Parameter Set window is displayed, see Figure 2-9.
2-9

Figure 2-9 ZTE RCT Setup - Parameter Set Window
There is no need to set any parameter in this window, and users can use the default
parameter setting.
12. Click Next. The Confirm dialog box is displayed, asking whether to initialize all the
clients.
13. Click Yes. The ZTE RCT Setup - System Initialization window is displayed. The
system initialization starts.
14. After the initialization is completed, click Next. The ZTE RCT Setup - Installation
Finished window is displayed.
15. Click Finish. The RCT client software installation is completed.
End of Steps
2.4 Starting the RCT Server Program

This procedure describes how to start the RCT server program.
Steps
1. Enter the RCT server software installation directory, and execute the following
command to start the RCT server program, see Figure 2-10.
bash-3.00# nohup ./console.sh &
2-10

Figure 2-10 Server Processes Started Successfully
All the server processes must be started successfully. Figure 2-10 shows that the RCT
server is started successfully.
2. After all the processes are started successfully, execute the following command to filter
the processes under the RCT installation path (such as /export/home/omc/rct)
to verify whether the signaling tracing process is started successfully.
bash-3.00# ps -ef|grep /export/home/omc/rct
If the information of the following three process is returned, it indicates that the
signaling tracing process is started successfully.
root 15434 15377 0 10:50:09 ? 9:17 /datafile/u01/rct/jdk/jdk/solaris/bin/

sparcv9/zte_uep1 -Dcom.zte.ums.console.
zte_console1 -Xms20m -Xmx60m -Djava.lib
sparcv9/zte_rct1 -Dcom.zte.ums.console.
2-11

Note:
Users can stop or start UEP Process and RCT process respectively.
l To stop a process, select the process in the left console tree, and click the Stop
button on the right.
l To start a process, select the process in the left console tree, and click the Start
button on the right.
End of Steps
2.5 Starting the RCT Client Program

This section describes how to start the RCT client program.
Steps
1. Use one of the following methods to start the RCT client program.
l Enter the RCT client installation directory, and double-click the \ums-client\c
lient.exe file.
l Select Start > All Programs > RCT Unified Management System > RCT Client.
l Double-click the icon on the desktop.

The Login - RCT Client dialog box is displayed, see Figure 2-11.
Figure 2-11 Login - RCT Client Dialog Box
2. In the Login - RCT Client dialog box, enter User Name, Password, and Server
Address.
Set Server Address to RCT server IP address:port number (31100). For example,
set Server Address to 10.62.100.201:31100.
2-12

3. Click OK. The NetNumen Unified Management System - RCT Client window
appears, and the client is started successfully.
End of Steps
2-13

2-14

Chapter 3
Signaling Tracing Operation
Table of Contents
Overview ....................................................................................................................3-1
NE Management ........................................................................................................3-1
Subscriber Tracing .....................................................................................................3-6
Offline Tool ...............................................................................................................3-31
3.1 Overview
After logging in to the RCT through a RCT client, users can perform the following two types
of operations:
l NE management
NE management involves a series of basic operations, including adding an NE,
deleting an NE, modifying an NE, establishing a link, and disconnecting a link. Such
operations help RCT obtain the signaling information from an actual NE (RNC or
BSC).
l Subscriber tracing
Subscriber tracing involves a series of basic operations, including creating a signaling
tracing task, checking the signaling data obtained through a signaling tracing task,
modifying a signaling tracing task, and deleting a signaling tracing task.
The RCT also provides an offline tool. With this tool, users can directly open and
decode downloaded signaling tracing data files without logging in to the RCT server
from a RCT client.
3.2 NE Management
3.2.1 NE Management Window
Opening the NE Management Window
In the NetNumen Unified Management System - RCT Client window, click the (NE
Management) toolbutton on the toolbar, or select Maintenance > NE Management. The
NE Management window is displayed, see Figure 3-1.
3-1

Figure 3-1 NE Management Window
Note:
In the NE Management window, the operations are performed only for the NEs in RCT,
and the configurations of the actual NEs (RNC or BSC) will not be modified.
Toolbar of the NE Management Window

Table 3-1 describes the toolbuttons on the toolbar of the NE Management window.
Table 3-1 Toolbar of the NE Management Window
Button Description
Add an NE
Delete an NE
Modify an NE
Refresh the NE list
Establish the link with an actual NE
Disconnect the link with an actual NE
3-2

Chapter 3 Signaling Tracing Operation
3.2.2 Adding an NE
Users can add the information of an NE according to the address and port number of the
corresponding actual NE (RNC or BSC), making preparation for establishing the physical
link between RCT and the actual NE.
The operation of creating an NE in RCT only registers the NE information in the software,
facilitating users to establish a link between RCT and the corresponding actual NE.
Steps
1. In the NE Management window, use either of the following methods to open the Add
dialog box.
l On the toolbar, click .
l Right-click the blank area in the NE Management window and select Add from
the shortcut menu.
The Add dialog box is displayed, see Figure 3-2.
Figure 3-2 Add Dialog Box
2. In the Add dialog box, add the NE information.

Table 3-2 describes the parameters in the Add dialog box.
3-3

Table 3-2 Parameters in the Add Dialog Box
Parameter Description
Name The name of an NE must be unique, and must be a combination of

number, alphabet, -, and _. It is recommended to keep the name of
an NE the same with that of the corresponding actual NE (RNC or BSC).
Type Users can select MUTI, TD, UMTS, or GSM from the Type drop-down
list box, and the corresponding NE versions available are displayed.
If MUTI is selected, users can select multiple NE versions
simultaneously; otherwise, users can only select one NE version.
IP Address If the RCT server is directly connected to the NE, set this parameter to
the IP address of the NE.
If the RCT server is connected to the NE through the forwarding module,
set this parameter to the IP address of the forwarding module.
Port If the RCT server is directly connected to the NE, set this parameter to
the monitoring port of the NE. The monitoring port number of NEs (V3)
is 5057 while the monitoring port number of NEs (V4) is 5059.
If the RCT server is connected to the NE through the forwarding module,
set this parameter to the monitoring port of the forwarding module. The
default value is 35059.
The combination of IP Address and Port must be unique.
Remark Other remark information
3. Click OK. The NE is added.

The added NE is in the Off state. Users must perform the link establishment operation
to make the NE convert from the Off state to the On state. After that, the added NE
is connected to the corresponding actual NE, and the signaling information can be
obtained.
Users can delete or modify an NE that is in the Off state.
End of Steps
3.2.3 Link Operations

Before using RCT, users should connect the system with the actual NEs (RNC or BSC) first.
The link operations related to the actual NEs involve establishing links and disconnecting
links.
3.2.3.1 Establishing a Link

After selecting an added NE, users can establish a physical link between the selected
NE and the corresponding actual NE (RNC or BSC), on which the signaling information is
transmitted.
This procedure describes how to establish a link.
3-4

Prerequisite
The NE information is added in the NE Management window.
Steps
1. In the NE Management window, select an NE to be connected to the corresponding
actual NE. Users can use either of the following two methods to establish a link
between the selected NE and the corresponding actual NE (RNC or BSC).
l On the toolbar, click .
l Right-click the NE to be connected to an actual NE, and select connect from the
shortcut menu.
State of the selected NE is converted from Off to On, which indicates that the link is
established successfully.
If State of the NE is always Connecting, the link fails to be established. You can
perform the following troubleshooting operations:
l Verify that the forwarding module and the NE are started properly.
l Verify that the RCT and the forwarding module are connected properly, and verify
that the forwarding module and the NE are connected properly.
l Verify that the forwarding module is configured properly.
End of Steps
3.2.3.2 Disconnecting a Link

This procedure describes how to disconnect a link between RCT and an actual NE (RNC
or BSC).
Context
After a link is disconnected, all the signaling tracing tasks related to the NE whose states
are START are automatically converted to the SYNC state. After the link is recovered, the
states of the corresponding signaling tracing tasks will be converted to START again.
Steps
1. In the NE Management window, select an NE to be disconnected from the
corresponding actual NE. Users can use either of the following two methods to
disconnect the link between the selected NE and the corresponding actual NE (RNC
or BSC).
l In the toolbar, click .
l Right-click the NE to be disconnected from the corresponding actual NE, and
select disconnect from the shortcut menu.
State of the selected NE is first converted from On to Disconnecting, and then

converted to Off, indicating that the link is disconnected successfully.
3-5

If State of the NE is always Disconnecting, it indicates that the link fails to be

disconnected.
End of Steps
3.3 Subscriber Tracing

3.3.1 Subscriber Trace Window
Opening the Subscriber Trace Window
In the NetNumen Unified Management System - RCT Client window, click the
(Subscriber Trace) tool button on the toolbar, or select Maintenance > Subscriber
Trace. The Subscriber Trace window is displayed, see Figure 3-3.
Figure 3-3 Subscriber Trace Window
1. Subscriber Trace tree 3. Operation result area 5. Object task

2. Task list 4. Task properties area 6. Subtask
Object tasks are created in accordance with task type. An object task can contain multiple
subtasks created for multiple NEs, multiple versions, and multiple sub-types.
In the task list, double-click an object task. The subtasks contained in the object task
are displayed. A subtask is named as follows: object task name_subtask no._NE
name-NE version
3-6

The state of a subtask can be START, STOP, STARTING, STOPPING, and SYNC.
By default, 100 subscriber tracing tasks can be running simultaneously. For tasks created
for NEs of different systems, if they have the same UEID, they are considered as the
same task. Users can modify the value parameter in the server-conf-rct.xml file
under the ums-server/procs/ppus/omc.ppu/omc-rct-trace.pmu/rct-trace-
taskmanage-osf.par/conf directory to set the number of tasks to be started. At most
1000 tasks can be started.
If the states of all the subtasks of an object task are the same, the object task state is also
the same as that of its subtasks. For example, if the states of all the subtasks of an object
task are START, the object task state is also START.
If the states of the subtasks of an object task are not the same, the object task sate is
WARNING.
The Subscriber Trace tree provides several functional nodes in the left pane. For a
description of these nodes, refer to Table 3-3.
Table 3-3 Nodes in the Subscriber Trace Tree
Node Description
Create Task Users can select this menu item to create a subscriber tracing
task.
Open Data File Users can select this menu item to open a local signaling tracing
file.
Open Multi Data Files Users can select this menu item to open multiple local signaling
tracing files.
Trace Task Management Users can select this menu item to switch to the task manager
tab.
Set Client Parameter Users can select this menu item to set the maximum records
displayed in the list-type monitoring window.
Create Multi Ne Task Users can select this menu item to create a signaling tracing
task that is operating under multiple NEs.
Replay MTM Signaling File Users can select this menu item to replay signaling data in a file.
Import decode library Users can select this menu item to import the decoding library in
a file to the RCT client.
Right-click an object task or a subtask, a shortcut menu appears. Table 3-4 describes the
menu items on the shortcut menu.
Table 3-4 Shortcut Menu Items
Shortcut Menu Item Description
Start Task Users can select this menu item to start a selected task.
Users can start a single subtask or all the subtasks under the
selected object task.
3-7

Shortcut Menu Item Description
Stop Task Users can select this menu item to stop a started tracing task.
Users can stop a single subtask or all the subtasks under the
selected object task.
Delete Task Users can select this menu item to delete a single subtask or
press Ctrl and Shift to select multiple subtasks and then delete
them.
Update SubTask Info Users can select this menu item to modify the properties of a
selected subtask that is in the STOP state. After this menu item
is selected, users can modify the subtask properties in the task
properties area.
Commit Update Task After the subtask properties are modified, users can select this
menu item to submit the modification.
Undo This Modify Users can select this menu item to cancel the modification of
the subtask properties.
Update Group Task Info After right-clicking an object task, if users select this menu
item from the shortcut menu, the Create SubTask dialog box
appears. Users can create a new subtask for the object task.
Monitor After right-clicking a subtask, if users select this menu item from
the shortcut menu, the system switches to the signaling tab, on
which the signaling data traced by the subtask is displayed.
Multi Monitor Users can select this menu item to display the signaling data
reported by multiple NE tracing tasks in one window. Normally,
it is applied in single-subscriber multi-NE tracing, facilitating
signaling observation and analysis.
View Data Users can select this menu item to display the signaling tracing
files related to the subtask. Users can view, download, and
delete the files.
Refresh RCT allows multiple clients to perform task management

simultaneously. If a client performs task management, other
clients can see the operation result only after the server makes a
response.
Users can select this menu item to synchronize the latest tasks'
states on the server to the local client.
Open All TaskNodes Users can select this menu item to expand all the object task
nodes, and all the subtasks are displayed.
Close All TaskNodes Users can select this menu item to collapse the object task
nodes, and only the object task list is displayed.
Find Task Users can select this menu item to find tasks in accordance with
parameters such as NE name and task name.
3-8

Signaling Tab
On the signaling tab, users can view the traced signaling data, see Figure 3-4.
Figure 3-4 Signaling Tab
1. Traced data list 2. Decoding Results tab and 3. Flow source list box
Tree Decoding Results tab
When the number of signaling records displayed in the traced data list reaches the set
maximum number, if a new signaling is reported, the first signaling displayed in the list will
be deleted.
For example, suppose the maximum number of signaling records displayed at the client is
set to 2000. When the number of signaling records displayed in the traced data list reaches
2000, if another five signalings are reported, the first five signaling records displayed in the
list will be deleted.
3.3.2 Task Operation Rights

In the RCT system, task operation rights are related to users. Only the creator of a task
and the admin user can modify, delete, start, or stop the task. Other users can only query
and monitor tasks.
The creator of a task and the admin user can also delete signaling tracing files generated
by the task. Other users can only view and download the signaling tracing files.
The task manager tab displays the information of users who create tasks, see Figure 3-5.
3-9

Figure 3-5 User Information
3.3.3 Creating a Task

This procedure describes how to create a signaling tracing task.
Prerequisite
The NE to be traced is created and the NE link is established successfully.
Steps
1. In the Subscriber Trace window, double-click the Create Task node in the Subscriber
Trace tree. The Create Task dialog box is displayed.
2. Set Task Name and Task Type, see Figure 3-6.
3-10

Figure 3-6 Creating a Task - Step 1
Table 3-5 describes the parameters in the Create Task dialog box.
Table 3-5 Parameters in the Create Task Dialog Box
Task Name Task name. The name of a task must be unique, and can only be
a combination of number, alphabet, "-", and "_".
Task Type Users can select the task type from the Task Type drop-down
list box.
3. Click NEXT. The Create Task dialog box is displayed, see Figure 3-7.
3-11

4. In the NE List area, click an NE tab. In the Ne Version area, click an NE tab. In the
SubTask Type area, click a subtask tab, and click add. The Create Task dialog box
is displayed, see Figure 3-8.
3-12

5. In the SubTask Type area, select the tracing items.

l If a task involves various versions of multiple NEs, you must set parameters in the
NE List area, Ne Version area, and SubTask Type area respectively.
l The values entered in the Value column must be correct, otherwise, the system
will prompt the correct format and value range.
The IMSI parameter sets the IMSI type of the UE to be traced. For example, the
parameter can be set to IMSI, TMSI, or PTMSI.
The UEID parameter sets the IMSI ID(s) of the UE(s) to be traced. You can enter
multiple IMSI IDs, and separate them by ";".
IMSI ID can be a number between 0 and 9 with a length from 1 to 15 bits. TMSI
and PTMSI can be a BCD code with a length of 8 bits.
l If the select all items check box is selected, all filtering items in this area will be
selected. If the select all items check box is cleared, all filtering items in this area
will not be selected.
6. Click FINISH. The signaling tracing task is created and displayed in the task list.
3-13

After a task is created, the default task state is STOP. You must start the task before
performing relevant signaling tracing operations.
For a task whose state is STOP, you can modify the filtering items to be traced.
End of Steps
3.3.4 Monitoring a Task

This procedure describes how to monitor a started signaling tracing task and view the
traced signaling data of each subtask.
Steps
1. In the Subscriber Trace window, right-click a subtask to be monitored in the task list,
and select Monitor from the shortcut menu. According to the selected subtask type,
the corresponding signaling tracing window will be displayed.
l Figure 3-9 shows the list-type signaling tracing window.
Figure 3-9 List-Type Signaling Tracing Window
The Data tab displays the traced signaling information while other tabs display
logs, KPIs, delay, and statistics related to the signaling.
On the Data tab, double-click a signaling. The detailed decoding information and
flow source of the signaling are displayed in the right pane.
The traced signalings that are abnormal will be highlighted in the window.
3-14

The list-type signaling tracing window provides some toolbuttons on the toolbar.
For a description of these toolbuttons, refer to Table 3-6.
Table 3-6 Toolbar in the List-Type Signaling Tracing Window
Toolbutton Description
Save all Users can click this toolbutton to save all the displayed
signaling data to a specified local file. The saved file format
can be XLS, XML, TXT, or *.CSV.
If the file format is XLS, XML, or TXT, all the displayed
signalings and the corresponding detailed decoding
information and flow source can be saved to a specified
local file.
If the file format is CSV, all the displayed signalings can be
saved to a specified local file.
Save selected Users can click this toolbutton to save the selected signaling
data to a specified local file. The saved file format can be
*.XLS, *.XML, *.TXT, or *.CSV.
If the file format is XLS, XML, or TXT, the selected signalings
and the corresponding detailed decoding information and
flow source can be saved to a specified local file.
If the file format is CSV, the selected signalings can be saved
to a specified local file.
Search On the signaling tab, users can click this toolbutton to

search the signaling messages that satisfy the set search
condition.
Filter Users can click this toobutton to filter signaling according to

the set filtering condition, and the filtered result is displayed
in a new window.
Start monitoring Users can click this toolbutton to display the obtained latest
signaling data in real time on the signaling tab.
Stop monitoring Users can click this toolbutton to stop displaying the obtained
latest signaling data in real time on the signaling tab.
Pause refreshing After users click this toolbutton, the latest traced signaling
data will not be displayed on the signaling tab, and only the
previously reported signaling data is displayed.
Recover refreshing After users click this toolbutton, the latest traced signaling
data will continue to be displayed on the signaling tab.
Display in full screen Users can click this toolbutton to display the signaling data
on the signaling tab in full screen.
Exit display in full Users can click this toolbutton to exit the full-screen display
screen mode.
3-15

Toolbutton Description
Flow source Users can click this toolbutton to open the Flow source list
box, in which the traced signaling data is displayed in the
form of flow source.
Users can also double-click a signaling to open the Flow
source list box.
Detailed decoding Users can click this toolbutton to open the Decoding
Results tab and the Tree Decoding Results tab, on which
the traced signaling data is displayed in the form of detailed
information or in the form of a tree.
Delete all Users can click this toolbutton to delete all the signaling data
on the signaling tab.
Pausing scrolling Users can click this toolbutton to make the scrolling display
of the signaling data on the signaling tab pause.
Recover scrolling Users can click this toolbutton to recover the scrolling display
of the signaling data on the signaling tab.
l Figure 3-10 shows the curve-type signaling tracing window.
Figure 3-10 Curve-Type Signaling Tracing Window
In the upper part of the curve-type signaling tracing window, the traced indexes
are displayed in real time in the form of a curve. In the lower part of the window,
the detailed index information is displayed. In the curve-type signaling tracing
3-16

window, users can only view the traced signaling data and cannot perform any
operation on the data.
l Figure 3-11 shows the diagram-type signaling tracing window.
Figure 3-11 Diagram-Type Signaling Tracing Window
In the diagram-type signaling tracing window, users can only view the traced
signaling data and cannot perform any operation on the data.
End of Steps
3.3.5 Monitoring Multiple Tasks

This procedure describes how to monitor multiple signaling tracing tasks of NEs. All
reported signalings are displayed in one window. Normally, it is applied in single-subscriber
multi-NE tracing, facilitating signaling observation and analysis.
Steps
1. On the task manager tab, right-click the Task List area, and select Multi Monitor
from the shortcut menu. The Multi Monitor dialog box is displayed, see Figure 3-12.
3-17

Figure 3-12 Multi Monitor Dialog Box
2. Select a NE version and task type. The corresponding tasks are displayed, see Figure
3-13.
3-18

Figure 3-13 Multi Monitor Dialog Box
3. Select the tasks to be monitored (multiple tasks can be selected), and click OK. The
information of the selected tasks is displayed on the signaling tab, see Figure 3-14.
3-19

Figure 3-14 Traced Signaling
End of Steps
3.3.6 Viewing Data

This procedure describes how to view signaling tracing data.
After selecting a subtask, users can view the related signaling tracing files on the server
and download the files to a local client. The file format can be CSV and ZIP.
Context
The RCT can automatically generate the signaling tracing files of CSV format on the server
for each subtask. When the number of signaling records saved in a file reaches 10000, the
file is compressed into a ZIP file, and another new CSV file will be generated to continue
saving the signaling records.
The signaling tracing file format is *.CSV. The file is named as object task
name_subtask no._NE name_NE version-Dfile generation time.csv.
The file generation time is in the form of YYMMDDHHMMSS. For example, a
signaling tracing file automatically generated by the server can be named as
TASK_1_umts-UMTSV4_4.11.20-D120223110643.csv.
The format of compressed signaling tracing files is ZIP, and the files can be named as
subtask name-Dfile generation time.zip.
3-20

Prerequisite
The signaling tracing files are available on the server.
Steps
1. In the task list, right-click the subtask to be viewed, and select View Data from the
shortcut menu. The View Data dialog box is displayed, see Figure 3-15.
Figure 3-15 View Data Dialog Box
2. Select a data file and click the Show button. The monitoring window is displayed,
showing the detailed signaling data of the selected subtask.
l You can click the Download button to save a selected signaling tracing file to the
local client.
l You can click the Download All button to save all the signaling tracing files related
to the subtask to the local client.
l You can click the Delete button to delete a selected signaling tracing file from the
RCT server.
l You can click the Delete All button to delete all the displayed signaling tracing
files from the RCT server.
End of Steps
3.3.7 Opening a Historical Data File

This procedure describes how to open a signaling tracing file downloaded to the local client.
3-21

Prerequisite
The signaling tracing files of the CSV and ZIP format are downloaded to the local client.
Steps
1. In the Subscriber Trace window, double-click the Open Data File node in the
Subscriber Trace tree. The Open dialog box is displayed.
2. Enter the path and name of the file to be opened, and click the Open button. The
system switches to the signaling tab, on which the signaling tracing data contained
in the file is displayed.
End of Steps
3.3.8 Viewing Historical Data Files

This procedure describes how to simultaneously open multiple signaling tracing files
downloaded to the local client.
Steps
1. In the ZTE RCT System-Client window, double-click the Open Multi Data Files node
in the Subscriber Trace tree. The Choose Version dialog box is displayed, see
Figure 3-16.
Figure 3-16 Choose Version Dialog Box
2. Select a NE version and task type, and click OK. The Open dialog box is displayed.
3-22

Note:
The NE types, NE versions, and task types defined in the files to be viewed must be
consistent with the setting in this step; otherwise, the files will fail to be opened.
3. Select the files, and click the Open button. The system switches to the signaling tab,
which displays the signaling tracing data contained in the files.
End of Steps
3.3.9 Setting Client Parameters

This procedure describes how to set the maximum number of signaling records that are
displayed in the list-type signaling tracing window.
Steps
1. In the ZTE RCT System-Client window, double-click the Set Client Parameter node
in the Subscriber Trace tree. The Local Setting dialog box is displayed, see Figure
3-17.
Figure 3-17 Local Setting Dialog Box
2. Set Data Table Capability, and click Ok.
After the setting is completed, at most the set maximum number of signaling records
are displayed on the signaling tab.
End of Steps
3.3.10 Creating Multiple Signaling Tracing Tasks Simultaneously

This procedure describes how to create multiple signaling tracing tasks simultaneously.
Context
Users can simultaneously create multiple signaling tracing tasks for multiple UEs and NEs
by specifying the same signaling tracing task parameters.
3-23

Steps
1. In the ZTE RCT System-Client window, double-click the Create Multi Ne Task node
in the Subscriber Trace tree. TheCreate Multi Ne Task dialog box is displayed, see
Figure 3-18.
Figure 3-18 Create Multi Ne Task Dialog Box - Step 1
2. Set the task name, and select an NE version. The corresponding NEs are displayed.
3. Select one or multiple NEs, and click NEXT. The Create Multi Ne Task dialog box is
refreshed, see Figure 3-19.
3-24

Figure 3-19 Create Multi Ne Task Dialog Box - Step 2
4. Select the filtering items, and click FINISH. The task is created and displayed in the
task list.
The values entered in the Value column must be correct, otherwise, the system will
prompt the correct format and value range.
The IMSI parameter sets the IMSI type of the UE to be traced. For example, the
parameter can be set to IMSI, TMSI, or PTMSI.
The ImsiID parameter sets the IMSI ID(s) of the UE(s) to be traced. You can enter
multiple IMSI IDs, and separate them by ";".
IMSI ID can be a number between 0 and 9 with a length from 1 to 15 bits. TMSI and
PTMSI can be a BCD code with a length of 8 bits.
After a task is created, the default task state is STOP. You must start the task before
performing relevant signaling tracing operations.
For a task whose state is STOP, you can modify the filtering items to be traced.
End of Steps
3-25

3.3.11 Replaying a Historical Data File

This procedure describes how to replay curve-type signaling data and diagram-type
signaling data contained in an MTM file. The format of signaling tracing files can be CSV
or ZIP.
Prerequisite
Signaling tracing files of CSV or ZIP format are downloaded from the RCT server.
Steps
1. In the ZTE RCT System-Client window, double-click the Replay MTM Signaling File
node in the Subscriber Trace tree. The Open dialog box is displayed.
2. Select a curve-type or diagram-type signaling tracing data file, and click the Open
button. The signaling tracing data is displayed on the signaling tab, see Figure 3-20.
Figure 3-20 Replayed Historical Data File
If the selected file is not of curve-type or diagram-type, the signaling tracing data cannot
be replayed, and the system will gives a error message box.
End of Steps
3.3.12 Importing a Decoding Library

This procedure describes how to import the decoding library in a file to the RCT server to
decoding signaling.
Only the admin user can import decoding libraries.
3-26

Steps
1. In the ZTE RCT System-Client window, double-click the Import decode library node
in the Subscriber Trace tree. The Choose Version dialog box is displayed, see
Figure 3-21.
Figure 3-21 Choose Version Dialog Box
2. Select a NE version, and click OK. The Please Select DecodeLib Directory dialog
box is displayed.
3. Select the directory where the decoding library is located, and click the Upload button.
The selected decoding library is uploaded to the RCT server.
After the upload is completed, a message box is displayed, indicating that the decoding
library is uploaded.
Note:
The RCT client can obtain the decoding library from the RCT server after being
restarted.
End of Steps
3.3.13 Searching Tasks

This procedure describes how to search tasks in accordance with task parameters such
as task name, cell ID, and IMSI.
3-27

Steps
1. Press Ctrl+F or right-click the task list and select Find Task from the shortcut menu.
The Search Task dialog box is displayed, see Figure 3-22.
Figure 3-22 Search Task Dialog Box
For a description of the parameters in the Search Task dialog box, refer to Table 3-7.
Table 3-7 Parameters in the Search Task Dialog Box
Ne Name The name of an NE-related task.

This parameter is optional.
Search Type This parameter is mandatory.

The value range is Task Name, cellId, and Imsi.
Search Value Key word for searching tasks. This parameter and the Search Type
parameter are used together for searching all tasks that are of the search
type and contain the key word.
This parameter is optional.
2. Set relevant parameters, and click Search All. The search result is displayed, see
Figure 3-23.
3-28

Figure 3-23 Search Task Dialog Box (Search Result)
3. Click Next. The searched tasks are highlighted sequentially.

End of Steps
3.3.14 MML Commands Related to Signaling Tracing Tasks

In the RCT system, users can query, start, and stop signaling tracing tasks through MML
commands in the MML Terminal window.
Only the creator of a task and the admin user can start and stop the task through MML
commands.
Opening the MML Terminal Window

At the RCT client, select Configuration > MML Terminal > Open MML Terminal, or click
the button on the toolbar. The MML Terminal window is displayed, see Figure 3-24.
3-29

Figure 3-24 MML Terminal Window
There are three functional nodes under the RCT TASK MANAGE node:
QUERYALLTASK(QUERYALLTASK), STARTTASK(STARTTASK), and
STOPTASK(STOPTASK).
Querying all Tasks

Click the QUERYALLTASK(QUERYALLTASK) node under the RCT TASK MANAGE
node, and click the button on the right Command Processing tab. All RCT tasks are
displayed on the Command Result tab, see Figure 3-25.
3-30

Figure 3-25 Command Result Tab
Starting an RCT Task

Click the STARTTASK(STARTTASK) node under the RCT TASK MANAGE node, enter
the RCT task name in the TaskName text box, and click the button. The specified task
is started, and the command execution information is displayed on the Command Result
tab.
Stopping an RCT Task

Click the STOPTASK(STOPTASK) node under the RCT TASK MANAGE node, enter the
RCT task name in the TaskName text box, and click the button. The specified task is
stopped, and the command execution information is displayed on the Command Result
tab.
3.4 Offline Tool

The RCT provides an offline tool. With this tool, users can directly open and decode
downloaded signaling tracing files without logging in to the RCT server from a RCT client.
The format of signaling tracing files can be CSV or ZIP.

The decoding libraries of the offline tool are located under the ums-client\tools\rc
t-offline\procs\lib directory at the RCT client. Before using the offline tool, users
3-31

must copy the decoding library files of various NE versions to the corresponding NE version
directories under the ums-client\tools\rct-offline\procs\lib directory.
Opening the Offline Tool

1. Double-click the run.bat file under the installation directory at the RCT client. The
language select dialog box is displayed.
2. Select English, and click OK. The RCT Offline Tool window is displayed, see Figure
3-26.
Figure 3-26 RCT Offline Tool Window
Users can open one or multiple signaling tracing files in the RCT Offline Tool window.
Opening a Signaling Tracing File

1. Select File > Open File, or click the button on the toolbar. The Open dialog box is
displayed.
2. Select a file, and click the Open button. The signaling tracing data in the file is
3-32

Figure 3-27 Displayed Signaling Tracing Data
Right-click a signaling tracing data. The shortcut menu is displayed, and users can
select relevant menu items to perform operations including saving, searching, and
filtering signaling tracing data, and displaying flow source and decoding information.
Opening Multiple Signaling Tracing Files

1. Select File > Files Import. The Choose Version And Task Type dialog box is
3-33

Figure 3-28 Choose Version And Task Type Dialog Box
Note:
The NE types, NE versions, and task types defined in the files to be opened must be
consistent with the setting in this step; otherwise, the files will fail to be opened.
2. Select an NE version and task type, and click OK. The Open dialog box is displayed.
3. Select one or multiple files, and click the Open button. The signaling tracing data in
the file(s) is displayed in the window.
3-34

Appendix A
Common Problems and
Troubleshooting
Table of Contents
The State of a Task Is Always STARTING............................................................... A-1
RCT Server Startup Failure .................................................................................... A-1
A.1 The State of a Task Is Always STARTING

Symptom
In the Task List window, Task State of a task is always STARTING.
Analysis
Because Task State of the task is always STARTING, it indicates that the task is not started
successfully.
If the link between RCT and an actual NE (RNC or BSC) is abnormal, the corresponding
signaling tracing task will not be started successfully.
Troubleshooting
Remove the link fault between the RCT and the actual NE (RNC or BSC). The task state
is automatically converted to START.
A.2 RCT Server Startup Failure

Symptom
The RCT server fails to start properly.
Analysis
Usually, the RCT server startup failure is due to the following two causes:
l The main process cannot be started or the main process starts successfully but all
operations are unavailable.
l The File Transfer Protocol (FTP) process cannot be started.
A-1

Troubleshooting
l In the case that the main process cannot be started or the main process starts
successfully but all operations are unavailable, perform the following troubleshooting
operations:
1. Check the detailed information of the main process to see whether the database
cannot be connected, see Figure A-1.
Figure A-1 Detailed Information of Running Processes
2. Log in to the system as the Oracle user and execute the following command to
check whether the database monitoring process can be started properly.
lsnrctl status
If the command result contains a character string Service "RCT" has

... instance(s), it indicates that the RCT database listener is started
properly. Skip step 3 and go to step 5.
If the command result does not contain a character string Service "RC
T" has ... instance(s), it indicates that the RCT database listener
cannot be started properly. Go to step 3.
3. Execute the following commands to start the RCT database listener:
lsnrctl stop
lsnrctl start
4. Check whether the database listener is started properly.
If the database listener is normal, go to step 5.
A-2

Appendix A Common Problems and Troubleshooting
If the database listener is abnormal, it indicates that the RCT database

listener configuration is incorrect. Modify the configuration, and go to step 5.
5. Execute the following command to connect the RCT database instance:
sqlplus system/oracle@rct
If the SQL> prompt appears, it indicates that the database instance is

connected successfully and the RCT database is started properly. The
problem is resolved.
If the database instance cannot be connected successfully, it indicates that
the RCT database instance cannot be started properly. Go to step 6.
6. Execute the following commands to restart the RCT database instance:
bash-3.00$ export ORACLE_SID=RCT
bash-3.00$ sqlplus /nolog
SQL> conn sys/oracle as sysdba
SQL> shutdown immediate
SQL> startup
7. Connect the RCT database instance.
If the database instance can be connected successfully, the problem is
resolved.
If the database instance cannot be connected, it indicates that the RCT
database instance is not installed properly. Modify the configuration, and go
to step 6.
l In the case that the FTP process cannot be started, check whether the IP address of
the server is consistent with that of the RCT server. Figure A-2 shows the detailed IP
address information displayed at the server console.
A-3

Figure A-2 RCT Server IP Address
If the IP address displayed in Figure A-2 differs from the RCT server IP address.
modify the server IP address to make it be consistent with the displayed IP address.
The problem is resolved.
A-4

Figures
Figure 1-1 Software System Structure ...................................................................... 1-2
Figure 1-2 RCT Server Software Installed Independently.......................................... 1-2
Figure 1-3 RCT Server Software Integrated into the EMS Server.............................. 1-3
Figure 1-4 NE State Conversion ............................................................................... 1-4
Figure 1-5 Task State Conversion ............................................................................. 1-5
Figure 2-1 ZTE RCT Setup - Select Installation Style Window .................................. 2-2
Figure 2-2 ZTE RCT Setup - Select Product Window ................................................ 2-3
Figure 2-3 ZTE RCT Setup - Database Connection Configuration Window ............... 2-4
Figure 2-4 ZTE RCT Setup - Database Configuration Window .................................. 2-5
Figure 2-5 ZTE RCT Setup - Host Information Configuration Window ....................... 2-6
Figure 2-6 ZTE RCT Setup - Parameter Set Window ................................................ 2-7
Figure 2-7 ZTE RCT Setup - Select Installation Style Window .................................. 2-8
Figure 2-8 ZTE RCT Setup - Select Product Window ................................................ 2-9
Figure 2-9 ZTE RCT Setup - Parameter Set Window .............................................. 2-10
Figure 2-10 Server Processes Started Successfully................................................ 2-11
Figure 2-11 Login - RCT Client Dialog Box.............................................................. 2-12
Figure 3-1 NE Management Window ........................................................................ 3-2
Figure 3-2 Add Dialog Box ........................................................................................ 3-3
Figure 3-3 Subscriber Trace Window ........................................................................ 3-6
Figure 3-4 Signaling Tab ........................................................................................... 3-9
Figure 3-5 User Information .................................................................................... 3-10
Figure 3-6 Creating a Task - Step 1......................................................................... 3-11
Figure 3-9 List-Type Signaling Tracing Window....................................................... 3-14
Figure 3-10 Curve-Type Signaling Tracing Window................................................. 3-16
Figure 3-11 Diagram-Type Signaling Tracing Window ............................................. 3-17
Figure 3-12 Multi Monitor Dialog Box ...................................................................... 3-18
Figure 3-13 Multi Monitor Dialog Box ...................................................................... 3-19
Figure 3-14 Traced Signaling .................................................................................. 3-20
Figure 3-15 View Data Dialog Box .......................................................................... 3-21
Figure 3-16 Choose Version Dialog Box ................................................................. 3-22

Figure 3-17 Local Setting Dialog Box ...................................................................... 3-23

Figure 3-18 Create Multi Ne Task Dialog Box - Step 1 ............................................ 3-24
Figure 3-19 Create Multi Ne Task Dialog Box - Step 2 ............................................ 3-25
Figure 3-20 Replayed Historical Data File ............................................................... 3-26
Figure 3-21 Choose Version Dialog Box ................................................................. 3-27
Figure 3-22 Search Task Dialog Box ....................................................................... 3-28
Figure 3-23 Search Task Dialog Box (Search Result).............................................. 3-29
Figure 3-24 MML Terminal Window......................................................................... 3-30
Figure 3-25 Command Result Tab .......................................................................... 3-31
Figure 3-26 RCT Offline Tool Window ..................................................................... 3-32
Figure 3-27 Displayed Signaling Tracing Data ........................................................ 3-33
Figure 3-28 Choose Version And Task Type Dialog Box.......................................... 3-34
Figure A-1 Detailed Information of Running Processes .............................................A-2
Figure A-2 RCT Server IP Address ...........................................................................A-4
II

Tables
Table 1-1 Recommended Server Configurations in the Independent Server
Deployment Mode.................................................................................... 1-3
Table 1-2 Task Types ................................................................................................ 1-6
Table 2-1 Signaling Tracing Modules ........................................................................ 2-3
Table 2-2 Database Connection Parameters ............................................................ 2-4
Table 3-1 Toolbar of the NE Management Window.................................................... 3-2
Table 3-2 Parameters in the Add Dialog Box ............................................................. 3-4
Table 3-3 Nodes in the Subscriber Trace Tree .......................................................... 3-7
Table 3-4 Shortcut Menu Items ................................................................................. 3-7
Table 3-5 Parameters in the Create Task Dialog Box .............................................. 3-11
Table 3-6 Toolbar in the List-Type Signaling Tracing Window .................................. 3-15
Table 3-7 Parameters in the Search Task Dialog Box .............................................. 3-28
III

Tables
IV

Glossary
Abis
- Abis Interface between BSC and BTS
BSC
- Base Station Controller
CPU
- Central Processing Unit
CS
- Circuit Switched
EMS
- Element Management System
FTP
- File Transfer Protocol
GSM
- Global System for Mobile Communications
IP
- Internet Protocol
MBMS
- Multimedia Broadcast/Multicast Service
MML
- Man Machine Language
MOSS
- Mobile Operation Support System
MTM
- Measurement Trace Management
NE
- Network Element
Node B
- Node B
OMM
- Operation & Maintenance Module
PS
- Packet Switched
RCT
- RNC Call Trace

RNC
- Radio Network Controller
TD-SCDMA
- Time Division-Synchronization Code Division Multiple Access
UE
- User Equipment
UMTS
- Universal Mobile Telecommunication System
VI

SJ-20121213161606-024-ZXWR RNC (V3.12.10) Calling Trace Operation Guide PDF

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

SJ-20121213161606-024-ZXWR RNC (V3.12.10) Calling Trace Operation Guide PDF

Uploaded by

Copyright:

Available Formats

ZXWR RNC

Radio Network Controller

Revision No. Revision Date Revision Reason

R1.0 20130407 First Edition

Serial Number: SJ-20121213161606-024

Publishing Date: 2013-04-07(R1.0)

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

Chapter 2 Software Installation and Startup............................................ 2-1

Chapter 3 Signaling Tracing Operation .................................................... 3-1

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

Appendix A Common Problems and Troubleshooting .......................... A-1

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 1, Overview Describes the basic functions, installation modes, software

Chapter 3, Signaling Tracing Describes the operations related to NE management and

Note: provides additional information about a certain topic.

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

1.1 Signaling Tracing Software Functions

1.2 Signaling Tracing Software Structure

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

Figure 1-1 Software System Structure

Independent Server Deployment

Figure 1-2 RCT Server Software Installed Independently

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

Co-EMS Server Deployment

1.4 Recommended Server Configurations

Table 1-1 Recommended Server Configurations in the Independent Server Deployment

Recommended server SUN v4 SPARC Enterprise T5220

Central Processing Unit (CPU) 64 virtual CPUs

1.5 Basic Concepts

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

Figure 1-4 NE State Conversion

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

l Stopping the signaling tracing task

Figure 1-5 Task State Conversion

For an NE which is in the On state, after a sub-task corresponding to it is started,

For an NE which is in the Off state, after a sub-task corresponding to it is started,

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

For an NE which is in the Connecting state, after a sub-task corresponding to it

Table 1-2 Task Types

Task Type Supported System Task Purpose

Tracing the signaling related to UEs of UMTS,

CELL UMTS, TD-SCDMA, GSM Tracing the signaling related to cells

Tracing the signaling between RNC and core

Tracing the signaling between RNC and an

Tracing the signaling between an RNC and its

Tracing the common signaling of the Rnlc Iurg

SM TD-SCDMA Tracing the signaling related to cell services

Tracing the signaling related to MBMS with a

ABIS GSM Tracing the signaling related to the Abis.

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

Task Type Supported System Task Purpose

GB GSM Tracing the signaling related to the GB interface

A GSM Tracing the signaling related to the A interface

l Non-timing synchronization: The RCT automatically initiates task synchronization

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

2.1 RCT Installation Flow

2.2 Installing the RCT Server Software

SJ-20121213161606-024|2013-04-07(R1.0) ZTE Proprietary and Confidential

Figure 2-1 ZTE RCT Setup - Select Installation Style Window