SJ-20140527134054-018-ZXUR 9000 UMTS (V4.13.10.15) Calling Trace Operation Guide_582765.pdf

ZXUR 9000 UMTS
Radio Network Controller
Calling Tracing Operation Guide
Version: V4.13.10.15
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn

LEGAL INFORMATION
Copyright © 2014 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 the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2014-07-31 First Edition
Serial Number: SJ-20140527134054-018
Publishing Date: 2014-07-31 (R1.0)
SJ-20140527134054-018|2014-07-31 (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 Architecture............................................................... 1-1
1.3 Deployment ....................................................................................................... 1-2
1.4 Recommended Server Configurations ................................................................. 1-2
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-11
2.4 Starting the RCT Server Program...................................................................... 2-18
2.5 Starting the RCT Client Program ....................................................................... 2-19
Chapter 3 Signaling Tracing Operations..................................................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-5
3.3 Subscriber Tracing ............................................................................................. 3-6
3.3.1 Subscriber Trace Window ......................................................................... 3-6
3.3.2 Importing a Decode Library..................................................................... 3-10
3.3.3 Creating a Task.......................................................................................3-11
3.3.4 Creating a Signaling Tracing Task for Multiple NEs................................... 3-15
3.3.5 Monitoring a Task................................................................................... 3-17
3.3.6 Performing the Joint Monitoring of Signaling Data .................................... 3-21
3.3.7 Viewing Signaling Data........................................................................... 3-22
3.3.8 Opening a Historical Data File................................................................. 3-24
3.3.9 Viewing Multiple Historical Data Files....................................................... 3-25
3.3.10 Replaying MTM Signaling Data ............................................................. 3-25
3.3.11 Setting the Maximum Number of Records .............................................. 3-26
3.3.12 Setting the Data Saving Mode............................................................... 3-26
Appendix A Common Problems and Troubleshooting.......................... A-1
I

A.1 Task Start Failure...............................................................................................A-1
A.2 RCT Server Startup Failure ................................................................................A-1
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II

About This Manual
Purpose
This manual provides instructions for installing and using the signaling tracing software,
RNC Call Trace (RCT). The basic functions of the RCT software include the creation and
monitoring of tracing tasks.
Intended Audience
This manual is intended for:
l Network optimization engineers
l Maintenance engineers
l Testing engineers
What Is in This Manual
This manual contains the following chapters and appendix.
Chapter 1, Overview Describes the basic functions, installation modes, software
structure, deployment modes, recommended server
configurations, and some basic concepts of the RCT system.
Chapter 2, Software Installation and
Startup
Describes the installation and startup procedure of the RCT
system.
Chapter 3, Signaling Tracing
Operations
Describes the operations related to NE management and
subscriber tracing in the RCT system.
Appendix A, Common Problems and
Troubleshooting
Describes some common problems in using the RCT system
and the relevant troubleshooting methods.
Conventions
This manual uses the following conventions.
Italics Variables in commands. It may also refer to other related manuals and
documents.
Bold Menus, menu options, function names, input fields, option button names,
check boxes, drop-down lists, dialog box names, window names,
parameters, and commands.
Constant width Text that you type, program codes, filenames, directory names, and
function names.
Note: provides additional information about a topic.
I

This page intentionally left blank.
II

Chapter 1
Overview
Table of Contents
Signaling Tracing Software Functions.........................................................................1-1
Signaling Tracing Software Architecture .....................................................................1-1
Deployment................................................................................................................1-2
Recommended Server Configurations........................................................................1-2
Basic Concepts ..........................................................................................................1-3
1.1 Signaling Tracing Software Functions
The signaling tracing software (RCT) is a component of the Mobile Operation Support
System (MOSS). The RCT software is used to locate and analyze problems when a
network failure occurs, a call is disconnected, the service exception occurs, or the network
is being optimized. By using the RCT software, you can trace and observe real-time
signaling data and measurement reports, which facilitates fault locating and system
debugging.
The RCT software implements real-time signaling tracing and management for multiple
Network Elements (NEs). It supports real-time signaling tracing for multiple 2G/3G NEs
(RNCs or BSCs).
In the RCT system, 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 Architecture
The RCT system uses the client/server architecture, which includes multiple clients and a
server.
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.
l The clients are connected to the server. You can customize signaling tracing tasks,
start signaling tracing tasks, and query signaling tracing results at the clients.
After the RCT system is started on a client, it is connected to the RCT server through the
RCT client, and the server is connected to an NE, see Figure 1-1.
1-1

ZXUR 9000 UMTS Calling Tracing Operation Guide
Figure 1-1 Software System Architecture
1.3 Deployment
The RCT system uses the client/server architecture. 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 the Operation & Maintenance Module (OMM).
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.
1.4 Recommended Server Configurations
For the recommended server configurations in the independent server deployment mode,
refer to Table 1-1.
1-2

Chapter 1 Overview
Table 1-1 Recommended Server Configurations in the Independent Server Deployment
Mode
Device Configuration
Recommended server SUN v4 SPARC Enterprise T5220
CPU 64 virtual CPUs
Physical memory 32 GB
Disk space 60 GB or greater
Network transmission bandwidth 64 KB/s or higher
1.5 Basic Concepts
Before using the RCT system, users should learn the following basic knowledge:
NE States
In the RCT system, users should create an NE in accordance with 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 RCT can have four states: Off, On, Connecting, and Disconnecting.
Figure 1-2 shows the conversion relationship among the four states.
Figure 1-2 NE State Conversion
1-3

l After an NE is created in the RCT system, 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 becomes Disconnecting, and 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 Create the signaling tracing task
l Start the signaling tracing task
l Stop the signaling tracing task
Figure 1-3 shows the conversion relationship among the task states.
Figure 1-3 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 changes to START. If the task fails
to be started, the task state remains STOP.
à For an NE whose state is On, after its corresponding sub-tasks are started, the
states of such sub-tasks become START.
1-4

Chapter 1 Overview
à For an NE whose state is Off, after its corresponding sub-tasks are started, the
system prompts that the NE is not connected.
à For an NE whose state is Connecting, after its corresponding sub-tasks are
started, the states of such sub-tasks become STARTING.
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 whose state is On, after its corresponding sub-tasks are stopped, the
states of such sub-tasks become STOP.
à For an NE whose state is Connecting, after its corresponding sub-tasks are
stopped, the states of such sub-tasks become STOPPING.
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 state
of corresponding tasks become START.
l Only the tasks in the START state can collect the signaling of the corresponding NEs.
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 system sends task synchronization messages to NEs every 30 minutes, and
it automatically sets the state of the started signaling tracing tasks to SYNC, that is,
the state of being synchronized.
Note:
à During timing synchronization, users need not perform any operation on the
corresponding signaling tracing tasks.
à If a task exists on an NE but does not exist in the RCT system, the NE
automatically deletes the task.
à If a task does not exist on an NE but exists in the RCT system, the NE
automatically creates the task and starts the task in the RCT system, and the
task state becomes START.
l Non-timing synchronization
The RCT system automatically initiates task synchronization every time a link between
the RCT system and an NE is established. If a link between the RCT system and an
1-5

NE is broken, the states of the corresponding tasks being started are set to SYNC,
and the tasks will be synchronized when the link is reestablished.
1-6

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-11
Starting the RCT Server Program.............................................................................2-18
Starting the RCT Client Program ..............................................................................2-19
2.1 RCT Installation Flow
The following describes the installation and configuration flow of the RCT system:
1. Prepare for the installation.
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.
c. Configure and start the message forwarding module in the Operation &
Maintenance Module (OMM). The OMM software version package contains the
message forwarding module.
2. Install the RCT server software.
3. Install the RCT client software.
The subsequent 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 procedure,
the disk space path is /datafile/u01.
2-1

3. A new instance named as RCT is created for RCT.
The instance is different from the instance used in the Element Management System
(EMS). It is recommended to install the database instance and the RCT server software
on the same disk. In the following example, the file saving path is /datafile/u01.
Steps
1. Enter the RCT version package 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, see Figure 2-1.
Figure 2-1 ZTE RCT Setup—Select Language Window
3. Select English from the Language list, and click Next. The ZTE RCT
Setup—License Agreement window is displayed, see Figure 2-2.
2-2

Chapter 2 Software Installation and Startup
Figure 2-2 ZTE RCT Setup - License agreement Window
4. Select I accept the license agreement, and click Next. The ZTE RCT Setup—Select
Installation Style window is displayed, see Figure 2-3.
Figure 2-3 ZTE RCT Setup—Select Installation Style Window
5. In accordance with the description in the Tips about current installation style area,
select the installation mode. In this example, select Initial Installation and Server
program.
2-3

6. Click Next. The ZTE RCT Setup—Network Scale window is displayed, in which only
Scale1 is available, see Figure 2-4.
Figure 2-4 ZTE RCT Setup—Network Scale Window
7. Click Next. The ZTE RCT Setup—Select Product window is displayed, see Figure
2-5.
Figure 2-5 ZTE RCT Setup—Select Product Window
a. Select the product signaling tracing modules to be installed.
2-4

For detailed information about the modules, refer to Table 2-1.
Table 2-1 Signaling Tracing Modules
Module Description
AG RNC TRACE (Optional) AG RNC V4 NE signaling tracing module
UMTS RNC TRACE (Optional) UMTS RNC V3 NE signaling tracing module
COMMON (Required) Common function module on the signaling tracing
server
TD RNC TRACE (Optional) TD-SCDMA RNC V3 NE signaling tracing module
UROP BSC TRACE (Optional) GSM BSC V3/V4 NE signaling tracing module
UROP RNC TRACE (Optional) UMTS RNC V4 NE signaling tracing module
UROP TDRNC TRACE (Optional) TD-SCDMA RNC V4 NE signaling tracing module
For example,
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.
b. In the Program Area Path text box, enter the installation directory of the RCT
server software, for example, /datafile/u01/rct.
You can also click the Browse button to select the installation directory.
By default, Data Area Path and Program Area Path are consistent. You can also
specify a different installation directory.
8. Click Next. The ZTE RCT Setup—Database Connection Configuration window is
displayed, see Figure 2-6.
2-5

Figure 2-6 ZTE RCT Setup—Database Connection Configuration Window
9. Set the required parameters.
For a description of the parameters in the ZTE RCT Setup—Database Connection
Configuration window, refer to Table 2-2.
Table 2-2 Parameters in the ZTE RCT Setup—Database Connection Configuration
Window
Parameter Setting Instruction
Database Type Select Oracle from the drop-down list
Oracle Connection Type Select sid from the drop-down list.
Database IP or Hostname Enter the IP address or host name of the Oracle server.
Database Port Use the default value 1521.
Oracle SID or Service Name Enter the SID (for example, RCT) of the instance created
for the RCT.
Database Superuser Name Enter the user name system the Oracle database
Password Enter the password of the system user.
10. Click Test Database Connection. After the database connection is verified
successfully, click Next. The ZTE RCT Setup—Database Config window is
2-6

Figure 2-7 ZTE RCT Setup—Database Config Window
Generally, there is no need to adjust the database file size.
11. Click Next. The ZTE RCT Setup—Host Information Config window is displayed,
see Figure 2-8.
Figure 2-8 ZTE RCT Setup—Host Information Config Window
12. From the Master server IP or hostname list, select the IP address of the RCT server.
2-7

13. Click Next. The ZTE RCT Setup—System Information Detection window is
displayed, and the detection results (Pass) are displayed in the Detect Result
column, see Figure 2-9.
Figure 2-9 ZTE RCT Setup—System Information Detection Window
14. Click Next. The ZTE RCT Setup—Installation Information Confirmation window is
Figure 2-10 ZTE RCT Setup—Installation Information Confirmation Window
2-8

15. Confirm the installation information and click Install. The ZTE RCT Setup—Unzip and
Copy Files window is displayed, and the system starts decompressing and copying
the files.
16. After the files are decompressed and copied, click Next. A message is displayed,
asking whether to execute the SQL scripts.
17. Click Yes. The ZTE RCT Setup—Installation Database window is displayed, and
the system starts installing the database, see Figure 2-11.
Figure 2-11 ZTE RCT Setup—Installation Database Window
18. After the installation is completed, click Next. The ZTE RCT Setup—Parameter Set
window is displayed, see Figure 2-12.
2-9

Figure 2-12 ZTE RCT Setup—Parameter Set Window
a. In the left navigation tree, click Common Property, click Main node IP on the
Server tab, and then enter the IP address of the RCT server in Value of config.
b. Use the default settings for other parameters and then click Save.
19. Click Next. The ZTE RCT Setup—System Initialization window is displayed,
showing the system initialization progress, see Figure 2-13.
Figure 2-13 ZTE RCT Setup—System Initialization Window
2-10

20. After the initialization is completed, click Next. The ZTE RCT Setup—Installation
Finished window is displayed, see Figure 2-14.
Figure 2-14 ZTE RCT Setup—Installation Finished Window
21. Click Finish. The RCT server software is installed successfully.
– 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 version package directory, and double-click the setup.bat file. The
Installation window is displayed.
2. Enter a temporary installation file path and press Enter, or press Enter directly to use
the default temporary installation file path. After the files are decompressed, the ZTE
RCT Setup—Select Language window is displayed, see Figure 2-15.
2-11

Figure 2-15 ZTE RCT Setup—Select Language Window
3. Select English from the Language list, and click Next. The ZTE RCT
Setup—License Agreement window is displayed, see Figure 2-16.
Figure 2-16 ZTE RCT Setup—License Agreement Window
4. Select I accept the license agreement, and click Next. The ZTE RCT Setup—Select
Installation Style window is displayed, see Figure 2-17.
2-12

Figure 2-17 ZTE RCT Setup—Select Installation Style Window
5. Select Initial Installation and Client Program, and then click Next. The ZTE RCT
Setup—Select Product window is displayed, see Figure 2-18.
Figure 2-18 ZTE RCT Setup—Select Product Window
a. Select the product signaling tracing modules to be installed.
2-13

Note:
The same product modules must be selected when the RCT server and the client
are installed.
b. In the Program Area Path text box, enter the installation directory of the RCT
client software, or click the Browse button to select an installation path.
By default, Data Area Path and Program Area Path are consistent. You can also
specify different installation directories for the two areas.
6. Click Next. If the installation directory does not exist, a message is displayed, asking
whether to create the directory.
7. Click Yes. The ZTE RCT Setup—System Information Detection window is
displayed, and the detection results (Pass) are displayed in the Detect Result
column, see Figure 2-19.
Figure 2-19 ZTE RCT Setup—System Information Detection Window
8. Click Next. The ZTE RCT Setup—Installation Information Confirmation window is
2-14

Figure 2-20 ZTE RCT Setup—Installation Information Confirmation Window
9. Confirm the installation information, and click Install. The ZTE RCT Setup—Unzip
and Copy Files window is displayed, and the system starts decompressing and
copying the files, see Figure 2-21.
Figure 2-21 ZTE RCT Setup—Unzip and Copy Files Window
2-15

10. After the files are decompressed and copied, click Next. The ZTE RCT
Setup—Parameter Set window is displayed, see Figure 2-22.
Figure 2-22 ZTE RCT Setup—Parameter Set Window
The default parameter setting is recommended, and you need not set any parameter
in this window.
11. Click Next. A message is displayed, asking whether to initialize all the clients.
12. Click Yes. The ZTE RCT Setup—System Initialization window is displayed, and the
system initialization is started, see Figure 2-23.
2-16

Figure 2-23 ZTE RCT Setup—System Initialization Window
13. After the initialization is completed, click Next. The ZTE RCT Setup—Installation
Finished window is displayed, see Figure 2-24.
Figure 2-24 ZTE RCT Setup—Installation Finished Window
14. Click Finish. The RCT client software installation is completed.
2-17

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 bash-3.00# no
hup ./console.sh & command. The NetNumen(TM) Unified Management System -
Console window is displayed, see Figure 2-25.
Figure 2-25 NetNumen(TM) Unified Management System—Console Window
All the server processes must be started successfully. Figure 2-25 shows that the RCT
server is started successfully.
2. After all the processes are started successfully, execute the bash-3.00# ps -ef|grep data
file/u01/rct command to filter the processes under the RCT server program installation
path (for example, datafile/u01/rct/export/home/omc/rct), and verify that
the signaling tracing process is started successfully.
If the information of the following three process is returned, it indicates that the
signaling tracing process is started successfully.
2-18

root 15434 15377 0 10:50:09 ? 9:17 /export/home/omc/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.
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.
2.5 Starting the RCT Client Program
This procedure describes how to start the RCT client program.
Steps
1. Start the RCT client program. The Login - RCT Client window is displayed, see Figure
2-26.
Figure 2-26 Login - RCT Client Dialog Box
The RCT client program can be started by one of the following methods:
2-19

l Enter the RCT client installation directory, and double-click the ums-clientc
lient.exe file.
l Select Start > All Programs > RCT Unified Management System > RCT Client.
l Double-click the icon on the desktop.
2. Enter the user name, password, and the IP address (for example, 10.62.100.145) of
the RCT server.
3. Click OK. The NetNumen Unified Management System - RCT Client window is
displayed, indicating that the client is started successfully.
2-20

Chapter 3
Signaling Tracing Operations
Table of Contents
Overview....................................................................................................................3-1
NE Management ........................................................................................................3-1
Subscriber Tracing .....................................................................................................3-6
3.1 Overview
After logging in to the RCT system through RCT Client, the following two types of
operations can be performed:
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. It
helps the RCT system acquire the signaling information from an actual NE (Radio
Network Controller (RNC) or Base Station Controller (BSC)).
l Subscriber tracing
Subscriber tracing involves the operations of creating a signaling tracing task,
checking the signaling data acquired through a signaling tracing task, modifying a
signaling tracing task, and deleting a signaling tracing task.
Moreover, the RCT system also provides an offline tool that allows you to directly open
and decode downloaded signaling data files without logging in to the RCT server through
a RCT client.
3.2 NE Management
3.2.1 NE Management Window
Before performing NE management operations, you are required to open the NE
Management window on the RCT client by using either of the following two methods:
l Click on the toolbar.
l Select Maintenance > NE Management from the menu bar.
Figure 3-1 shows the NE Management window.
3-1

Figure 3-1 NE Management Window
Note:
In the NE Management window, the operations on an NE in the RCT system do not change
the configuration of the actual NE (RNC or BSC).
The NE Management window provides a toolbar for convenient management operations.
For a description of the shortcut buttons on the toolbar, refer to Table 3-1.
Table 3-1 NE Management Toolbar
Button Description
Adds an NE.
Deletes an NE.
Modifies an NE.
Refreshes the NE list.
Establishes the link with an actual NE.
Disconnects the link with an actual NE.
Acquires the name of a cell or Node B that is configured in the
EMS.
3-2

Chapter 3 Signaling Tracing Operations
3.2.2 Adding an NE
This procedure describes how to add the information of an NE in the RCT system in
accordance with the IP address and port number of the corresponding actual NE (RNC
or BSC).
This operation only registers the NE information in the software. It helps establish a link
between the RCT system and the 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. Set the required parameters.
For a description of the NE parameters, refer to Table 3-2.
Table 3-2 NE Parameters Description
Parameter Description
Name NE name. The name of the NE must be unique in the system. It is
recommended to enter the same name as the actual NE (RNC or BSC).
ID Office ID of the NE.
3-3

Parameter Description
Type NE type. The options are MUTI, TD, UMTS, and GSM. After an NE
type is selected, the available NE versions under the drop-down list
change accordingly.
l If MUTI is selected, two version must be selected for the multi-mode
NE (GSM/UMTS or GSM/TD-SCDMA), for example, GSM BSC
V4/UMTS RNC V4 or GSM BSC V4/TD-SCDMA RNC V4.
l If GSM is selected, only one version can be selected for the GSM
NE (GSM BSC V3 or GSM BSC V4 NE).
l If UMTS is selected, only one version can be selected for the UMTS
NE (UMTS RNC V3 or UMTS RNC V4 NE).
l If TD is selected, only one version can be selected for the
TC-SCDMA NE (TD-SCDMA RNC V3 or TD-SCDMA RNC V4 NE.
IP Address IP address of the forwarding module of OMM.
Port Monitoring port of the forwarding module. The default value is 35059.
Remark Additional information.
3. Click OK. The added NE is displayed in the NE Management window and the NE
state is Off.
The NE can be modified or deleted when it is in Off state. The NE state changes to On
after the link between the RCT system and the actual NE is successfully established.
After that, the RCT system can acquire signaling information from the NE.
Note:
If the version of an NE is modified, for example, from version A to version B, the tracing
task related to this NE change accordingly.
l If version B also supports the type of tracing task created for version A, the tracing
task remains with all parameters unchanged.
l If version B does not support the type of tracing task created for version A, the
tracing task is automatically deleted by the RCT system.
Therefore, after the version of an NE is modified, you must check whether related
parameters need to be modified for the tracing tasks created for the previous version
and modify these parameters when required so that these tasks are still applicable to
the new version.
Only the admin user can modify the version number of an NE. Before the modification,
the user must ensure that this NE is only operated by a single user.
3-4

3.2.3 Link Operations
Before using the RCT system, you must 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
This procedure describes how to establish a link between the RCT system and an actual
NE (RNC or BSC).
Context
After selecting an added NE in the RCT system, you can establish a physical link between
the selected NE and the corresponding actual NE (RNC or BSC), on which the signaling
information is transferred.
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.
2. Use either of the following two methods to establish a link between the selected NE
and the corresponding actual NE (RNC or BSC).
l Right-click the selected NE, and select connect from the shortcut menu.
If State of the selected NE is converted from Off to On, it indicates that the link is
established successfully.
If State of the selected NE remains Connecting, it indicates that the link fails to be
established.
Note:
If the link establishment fails, you can perform the following troubleshooting operations:
l Verify that the forwarding module and the NE are started properly.
l Verify that the RCT system and the forwarding module are connected properly,
and verify that the forwarding module and the actual NEs are connected properly.
l Verify that the forwarding module is configured properly.
3-5

3.2.3.2 Disconnecting a Link
This procedure describes how to disconnect a link between the RCT system and an actual
NE (RNC or BSC).
Context
If a tracing task related to the NE is in START state, the task state changes to SYNC after
the link between the RCT system and the NE is disconnected. If the link recovers, the task
state changes to START again.
Steps
1. In the NE Management window, select an NE to be disconnected from the
corresponding actual NE.
2. Use either of the following two methods to disconnect the link between the selected
NE and the corresponding actual NE (RNC or BSC).
l Right-click the selected NE, and select disconnect from the shortcut menu.
If State of the selected NE is converted from On to Disconnecting, and then converted
to Off, it indicates that the link is disconnected successfully.
If State of the selected NE remains Disconnecting, it indicates that the link fails to be
disconnected.
3.3 Subscriber Tracing
3.3.1 Subscriber Trace Window
Before using the tracing functions of the RCT system, you are required to open the
Subscriber Trace window on the client by using either of the following methods:
l Click on the toolbar.
l Select Maintenance > Subscriber Trace from the menu bar.
Figure 3-3 shows the Subscriber Trace window.
3-6

Figure 3-3 Subscriber Trace Window
1. Navigation tree
2. Task list
3. Operation result area
4. Object task
5. Subtask
6. Task attributes area
Navigation Tree
The left navigation tree (Subscriber Trace) organizes the available functions in the window
in a tree structure. You can double-click a node to implement the corresponding function.
For a description of these functions, refer to Table 3-3.
Table 3-3 Subscriber Trace Tree
Node Description
Create Task Creates a subscriber tracing task.
Open Data File Opens a local signaling file.
Open Multi Data Files Opens multiple local signaling tracing files
simultaneously.
Trace Task Management Switches to the task manager tab.
Set Client Parameter Sets the maximum number of records displayed in the
list-type signaling tracing window.
Create Multi Ne Task Creates a signaling tracing task for multiple NEs.
Replay MTM Signaling File Replays the signaling data contained in a file.
Import decode library Imports a decoding library into the RCT server.
Task Manager Tab
An object task is created in accordance with a specific task type. An object task can contain
multiple subtasks of multiple NEs, multiple versions, and multiple subtypes.
In the task list, you can double-click an object task to display the subtasks contained in the
object task. A subtask is named as follows: object task name_subtask number_N
E name_NE version
3-7

The state of a subtask can be START, STOP, STARTING, STOPPING, or SYNC.
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.
A shortcut menu is displayed after an object task or subtask is right-clicked. For detailed
information of the shortcut menu, refer to Table 3-4.
Table 3-4 Commands on the Shortcut Menu
Command Description
Start Task Starts a single subtask or all subtasks of an object task.
Stop Task Stops a single subtask or all subtasks of an object task.
Delete Task Deletes a single subtask or all subtasks of an object task.
Update SubTask Info Modifies the attributes of a subtask in STOP state.
After you click this command on the shortcut menu, the attributes
of the selected subtask in the task attributes area become
modifiable.
Commit Update Task Confirms the modification of a subtask. After the attributes of a
subtask are modified, you can click this command to confirm and
submit the modification.
Undo This Modify Cancels the modification of a subtask. After the attributes of a
subtask are modified, you can click this command to cancel the
modification.
Update Group Task Info Modifies an object task. After this command is selected, the Add
SubTask dialog box is displayed. You can add a subtask for the
object task.
Set Timing Task Schedules an object task. After this command is selected, the
Set Run Time dialog box is displayed. You can set the start time
and end time for the selected object task.
Monitor Displays the signaling data of a single subtask.
After you select a subtask, right-click the subtask, and select this
command from the shortcut menu, the signaling tab is displayed,
showing the signaling data traced by the subtask.
Multi Monitor Displays the signaling data of multiple subtasks.
After you select an object task, right-click the task, and select this
command from the shortcut menu. The Multi Monitor dialog
box is displayed. You can set conditions to display the signaling
data of multiple subtasks. For detailed instruction, refer to 3.3.6
Performing the Joint Monitoring of Signaling Data.
3-8

Command Description
View Data Displays the signaling tracing file related to a subtask.
After you select a subtask, right-click the subtask, and select this
command from the shortcut menu, the View Data dialog box is
displayed, listing all signaling tracing files related to the subtask.
You can view the contents of a file, download a file to the local
disk, or delete a file in this dialog box.
Refresh The RCT system allows multiple clients to perform task
management simultaneously. If a client performs task
management, the other clients can see the operation result only
after the server makes a response.
This command is used to synchronize the task states between
the server and the local client.
Open All TaskNodes Expands all the object task nodes to display all subtasks under
these object tasks.
Close All TaskNodes Collapses all the object task nodes and only the object tasks are
displayed.
Find Task Searches for a task in accordance with the specified conditions
such as NE name or task name.
Note:
Only the admin user or the user who creates a task can modify, delete, start, and stop this
task and delete historical data files related to the task. The other users can only query and
monitor the task.
Signaling Tab
The traced signaling data is displayed on the signaling tab, see Figure 3-4.
3-9

Figure 3-4 Signaling Tab
3.3.2 Importing a Decode Library
A decode library is a collection of DLL files that are provided and released by an NE. For
detailed information about the decode library, refer to the release note of the NE software
version.
The DLL files in a decode library are called for decoding the signaling messages in
summary or details and obtaining the original code streams. The decode library of an NE
can be imported and uploaded to the RCT server through an RCT client. All files in the
corresponding directory of the decode library are imported into the RCT system. An RCT
client automatically downloads the decode libraries stored on the server after connecting
to the server no matter whether it already has the latest decode libraries.
This procedure describes how to import the decode library of an NE into the RCT client.
Prerequisite
The decode library of the NE is acquired.
Steps
1. In the Subscriber Trace window, double-click the Import decode library node in the
left navigation tree. The Choose Version dialog box is displayed, see Figure 3-5.
3-10

Figure 3-5 Choose Version Dialog Box
2. Select an NE version, and click OK. The Please Select DecodeLib Directory dialog
box is displayed.
3. Select the directory corresponding to the decode library and click Upload. The
selected directory is uploaded to the RCT client. After all files in the directory are
uploaded, a message is displayed, asking you to restart the client.
4. Click Yes. After the client is restarted and connected to the server again, the client
automatically downloads the decode library from the server when you open the
Subscriber Trace window.
3.3.3 Creating a Task
Before tracing the signaling data of an NE, a signaling tracing task must be created. This
procedure describes how to create a signaling tracing task.
Prerequisite
You have added the NE and established a link between the NE and the RCT system.
Steps
1. In the Subscriber Trace window, double-click the Create Task node in the left
navigation tree. The Create Task dialog box is displayed, see Figure 3-6.
3-11

Figure 3-6 Create Task Dialog Box—Package Task Info
2. Enter a unique name in the Task Name test box and select a task type from the Task
Type list.
For a description of all supported task types, refer to Table 3-5.
Table 3-5 Task Types
Task Type Applicable Product Task Purpose
UE GSM, UMTS, and
TD-SCDMA
Traces the signaling data related to a GSM,
UMTS, or TD-SCDMA UE.
CELL UMTS, TD-SCDMA, and
GSM
Traces the signaling data related to a cell.
OFFICE-IU UMTS and TD-SCDMA Traces the signaling data between an RNC and
the core network, including the signaling data in
the PS domain and CS domain.
OFFICE-IUB UMTS and TD-SCDMA Traces the signaling data between an RNC and
a Node B.
OFFICE-IUR UMTS Traces the signaling data between an RNC and
an adjacent RNC.
OFFICE-IUR-G TD-SCDMA and GSM Traces the public signaling data over the Rnlc
Iurg interface.
SM TD-SCDMA Traces the signaling data related to services in
a cell.
3-12

Task Type Applicable Product Task Purpose
MBMS UMTS and TD-SCDMA Specifies the MBMS SessionID or the cell using
the MBMS and traces the signaling data related
to MBMS.
ABIS GSM Traces the signaling data related to the Abis
interface.
GB GSM Traces the signaling data related to the Gb
interface.
A GSM Traces the signaling data related to the A
interface.
3. Click NEXT. The Create Task dialog box is updated, see Figure 3-7.
Figure 3-7 Create Task Dialog Box—NE List
4. Perform the following operations to add a subtask:
3-13

Note:
If the task is created for tracing the signaling data of multiple NEs with different
versions, you need to repeat this step to add multiple subtasks one at a time by
selecting the corresponding NE, NE version, and subtask type.
a. In the NE List area, click an NE tab.
b. In the Ne Version area, click an NE version tab.
c. In the SubTask Type area, click a subtask type tab.
d. Click add. The items involved in the subtask are displayed in the lower part of the
dialog box, see Figure 3-8.
Figure 3-8 Create Task Dialog Box—Subtask
3-14

e. Select the required items for tracing the related signaling data.
5. Click FINISH. The signaling tracing task is created and displayed in the task list.
Note:
l After a task is created, the default task state is STOP. You must start the task
before performing relevant signaling tracing operations.
l The attributes of the task can be modified when it is in STOP state. After modifying
the attributes of the task, you must right-click the task and select Commit Update
Task or Undo This Modify to confirm or cancel the modification before any other
operations.
3.3.4 Creating a Signaling Tracing Task for Multiple NEs
If the RCT system needs to trace the signaling data of multiple UEs from multiple NEs, a
signaling tracing subtask with the same parameter settings can be created in these NEs
at a time. This procedure describes how to create a signaling tracing task for multiple NEs
at a time.
Steps
1. In the Subscriber Trace window, double-click the Create Multi Ne Task node in the
left navigation tree. The Create Multi Ne Task dialog box is displayed, see Figure 3-9.
3-15

Figure 3-9 Create Multi Ne Task Dialog Box—Selecting NEs
2. Enter a task name in the Task Name text box and select an NE version in the Choose
Version area. The NEs of the selected version are listed in the lower part of the dialog
box.
3. Select one or multiple NEs, and click NEXT. The task parameters are displayed, see
Figure 3-10.
3-16

Figure 3-10 Create Multi Ne Task Dialog Box—Setting Task Parameters
4. Enter the IMSIs of the required UEs in the value cell corresponding to UEID, select
the other required items, and then click FINISH. The signaling tracing task is created
and displayed in the task list on the task manager tab. This task contains multiple
subtasks with the same parameter settings, which correspond to the selected NEs.
Note:
The default task state is STOP. You must start the task before performing any signaling
tracing operations.
3.3.5 Monitoring a Task
This procedure describes how to monitor a started signaling tracing subtask and view the
traced signaling data.
3-17

Steps
1. In the Subscriber Trace window, right-click a subtask to be monitored and select
Monitor from the shortcut menu. The signaling tracing window is displayed. The data
display format in the signaling tracing window varies with different subtask types.
l Figure 3-11 shows a signaling tracing window in which signaling data is displayed
in a list.
Figure 3-11 Signaling Tracing Window—Signaling Data Displayed in a List
In this signaling tracing window, a toobar is available for managing the displayed
signaling data. For a description of the shortcut buttons on the toolbar, refer to
Table 3-6.
Table 3-6 Toolbar Buttons for Managing Signaling Data in the List
Button Description
Saves all the displayed signaling data to a local file. The
supported file formats are XLS, XLSX, XML, TXT, or CSV.
Saves the selected signaling data to a local file. The
supported file formats are XLS, XLSX, XML, TXT, or CSV.
Searches for the signaling messages that meet the specified
conditions.
Filters the signaling data according to the specified filter
conditions. The filtering results are displayed in a new
window.
3-18

Button Description
Counts the number of signaling messages containing
different fields in the current window.
Highlights the contents in the Direction column in a specific
color according to the transmission direction of signaling
messages.
Displays the latest obtained signaling data in real time on
the signaling tab.
Stops displaying the latest obtained signaling data in real
time on the signaling tab.
Stops refreshing the signaling data on the signaling tab.
Only the previously reported signaling data is displayed.
Resumes refreshing the signaling data on the signaling tab.
Displays the signaling data on the signaling tab in full
screen.
Exits the full-screen display mode.
Displays the Flow source tab, on which the traced signaling
data is displayed in the form of flow source.
Displays the Decoding Results tab and the Tree Decoding
Results tab, on which the detailed decoding information
is displayed in the form of detailed information or a tree
structure.
Deletes all the signaling data on the signaling tab.
Pauses the signaling data on the signaling tab from
scrolling.
Resumes the scrolling of the signaling data on the signaling
tab.
l Figure 3-12 shows the signaling tracing window in which signaling data is
displayed in a line chart.
3-19

Figure 3-12 Signaling Tracing Window—Signaling Data Displayed in a Line
Chart
On the upper part of the signaling tracing window, the traced indicators are
displayed in real time in the form of a line chart. On the lower part of the window,
the detailed indicator information is displayed. In this signaling tracing window,
you can only view the signaling data but cannot perform any operation on the
data.
l Figure 3-13 shows the signaling tracing window in which signaling data is
displayed in graph format.
3-20

Figure 3-13 Signaling Tracing Window—Signaling Data Displayed in Graph
Format
In this signaling tracing window, you can only view the signaling data but cannot
perform any operation on the data.
3.3.6 Performing the Joint Monitoring of Signaling Data
Joint monitoring allows you to view the signaling data reported by different signaling tracing
subtasks in one window. It facilitates signaling observation and analysis and can be used
for tracing the signaling data of a single UE in multiple NEs.
This procedure describes how to perform the joint monitoring of signaling data traced by
multiple sub-tasks.
Steps
1. In the Subscriber Trace window, right-click a task on the task manager tab and select
Multi Monitor from the shortcut menu. The Multi Monitor dialog box is displayed, see
Figure 3-14.
3-21

Figure 3-14 Multi Monitor Dialog Box
2. Select an NE version in the Choose Version area and select a task type from the
Task Type list. The subtasks meeting the conditions are displayed in the lower part of
the dialog box. A keyword can be entered in the test box to filter the subtasks by task
name.
3. Select the required subtasks and click OK. All the signaling data traced by the selected
subtasks is displayed on the signaling tab.
3.3.7 Viewing Signaling Data
The RCT system allows you to view the data in a signaling data file generated by a subtask
and download the file to the local client. This procedure describes how to view the signaling
data in a data file stored on the RCT server.
Context
The RCT system automatically generates a signaling data file in CSV format for each
subtask on the server. When the number of signaling records in the CSV file reaches
3-22

10000, the RCT system compresses the CSV file into a ZIP file and generates a new CSV
file to continue saving the signaling records for the subtask.
The naming rule of the CSV files is object task name_subtask number_NE name_NE
version-Dfile generation time.csv.
Prerequisite
The system already generates signaling data files for the selected subtask on the server.
Steps
1. On the task manager tab, right-click the required subtask 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 signaling data file and click Show. The data in the selected signaling data file
is displayed on the signaling tab, see Figure 3-16.
3-23

Figure 3-16 Signaling Data File
3. (Optional) Perform the following operations in the View Data dialog box as required:
l Click the Download button. The selected data file is saved to the local client.
l Click the Download All button. All the data files related to the subtask are saved
to the local client.
l Click the Delete button. The selected data file is deleted from the RCT server.
l Click the Delete All button. All the signaling data files displayed in the View Data
dialog box are deleted from the RCT server.
3.3.8 Opening a Historical Data File
You can open a historical signaling data files stored on the local client and view the
signaling data in the data file. This procedure describes how to open a historical signaling
data file.
Prerequisite
The signaling data file (CSV or ZIP files) is available on the local client.
Steps
1. In the Subscriber Trace window, double-click the Open Data File node in the left
navigation tree. The Open dialog box is displayed.
2. Select the path where the signaling data files are stored, select the signaling data file
to be opened, and then click the Open button. The signaling data in the selected file
is displayed on the signaling tab.
3-24

3.3.9 Viewing Multiple Historical Data Files
The RCT system allows you to view the signaling data in multiple signaling data files in the
same window, which helps analyze the correlation among signaling data. This procedure
describes how to view the data in multiple historical signaling data files on the client.
Prerequisite
l The signaling data files (CSV or ZIP files) are available on the client.
l The signaling data files to be opened at a time must be generated by the same type
of subtasks that are created for NEs of the same type and version.
Steps
1. In the Subscriber Trace window, double-click the Open Multi Data Files node in the
left navigation tree. The Choose Version dialog box is displayed.
2. Select the NE version in the Choose Version area, select a task type from the Task
Type list, and then click OK. The Open dialog box is displayed.
3. Select the path where the signaling data files are stored, select the files to be opened,
and then click the Open button. The signaling data in the selected data files is
displayed on the signaling tab.
3.3.10 Replaying MTM Signaling Data
This procedure describes how to replay the signaling data in a Measurement Trace
Management (MTM) signaling file (CSV or ZIP file) in graph format.
Note:
Only the MTM signaling file recording UMTS signaling data can be replayed.
Prerequisite
The MTM signaling data file (CSV or ZIP file) is available on the local client.
Steps
1. In the Subscriber Trace window, double-click the Replay MTM Signaling File node
in the left navigation tree. The Open dialog box is displayed.
2. Select the required MTM signaling data and click Open. The system replays the
signaling data in graph format on the signaling tab.
3-25

3.3.11 Setting the Maximum Number of Records
This procedure describes how to set the maximum number of signaling records displayed
in the list-type signaling tracing window.
Steps
1. In the Subscriber Trace window, double-click the Set Client Parameter node in the
left navigation tree. The Local Setting dialog box is displayed, see Figure 3-17.
Figure 3-17 Local Setting Dialog Box
2. Click the required maximum number of records to be displayed in the data table and
click Ok.
3.3.12 Setting the Data Saving Mode
The RCT system supports two modes for saving the data reported by signaling tracing
tasks on the server. This procedure describes how to set the data saving mode on the
server.
Steps
1. In the Subscriber Trace window, double-click the Set Server Parameter node in the
left navigation tree. The Server Parameter Setting dialog box is displayed, see Figure
3-18.
Figure 3-18 Server Parameter Setting Dialog Box
2. Click Yes or No as required and then click Ok.
3-26

If... Then...
If Yes is selected The system generates a new file for saving the reported
data every time when a task is started.
If No is selected l If a data file is already generated for a task, the
system saves the reported data in this file every time
when the task is started. The system generates a
new data file for the task only when the size of the
existing data file reaches the limit.
l If no data file has been generated for a task, the
system generates a data file when this task is
started.
3-27

3-28

Appendix A
Common Problems and
Troubleshooting
Table of Contents
Ÿ Task Start Failure.................................................................................................... A-1
Ÿ RCT Server Startup Failure .................................................................................... A-1
A.1 Task Start Failure
Symptom
In the Task List window, Task State of a task is still STOP after start the task.
Cause
This may be caused by a problem of the link between the RCT system and the
corresponding NE (RNC or BSC).
Troubleshooting
Resolve the link fault between the RCT system and the actual NE (RNC or BSC) first and
then restart the task.
A.2 RCT Server Startup Failure
Symptom
The RCT server fails to start.
Cause
The possible causes of a RCT server startup failure are:
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 verify that the database can
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
verify that the database monitoring process is 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 "RCT"
has ... instance(s), it indicates that the RCT database listener is not
started properly. Go to step 3.
3. Execute the following commands to start the RCT database listener:
lsnrctl stop
lsnrctl start
4. Verify that the database listener is started properly.
à If the database listener is operating properly, go to step 5.
A-2

Appendix A Common Problems and Troubleshooting
à If the database listener is not operating properly, 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 is displayed, 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. Execute the following command to connect the RCT database instance.
sqlplus system/oracle@rct
à If the database instance is 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 of the
RCT database instance, and go to step 6.
l In the case that the FTP process cannot be started, verify that the RCT server IP
address is consistent with that configured in the processes on the RCT server. Figure
A-2 shows the detailed IP address information displayed at the RCT server console.
A-3

Figure A-2 RCT Server IP Address
If the IP address displayed in Figure A-2 is different from the RCT server IP address,
modify the RCT server IP address to make the two addresses the same. The problem
is resolved.
A-4

Figures
Figure 1-1 Software System Architecture..................................................................1-2
Figure 1-2 NE State Conversion ...............................................................................1-3
Figure 1-3 Task State Conversion .............................................................................1-4
Figure 2-1 ZTE RCT Setup—Select Language Window............................................2-2
Figure 2-2 ZTE RCT Setup - License agreement Window.........................................2-3
Figure 2-3 ZTE RCT Setup—Select Installation Style Window ..................................2-3
Figure 2-4 ZTE RCT Setup—Network Scale Window................................................2-4
Figure 2-5 ZTE RCT Setup—Select Product Window ...............................................2-4
Figure 2-6 ZTE RCT Setup—Database Connection Configuration Window...............2-6
Figure 2-7 ZTE RCT Setup—Database Config Window ............................................2-7
Figure 2-8 ZTE RCT Setup—Host Information Config Window .................................2-7
Figure 2-9 ZTE RCT Setup—System Information Detection Window ........................2-8
Figure 2-10 ZTE RCT Setup—Installation Information Confirmation Window ............2-8
Figure 2-11 ZTE RCT Setup—Installation Database Window....................................2-9
Figure 2-12 ZTE RCT Setup—Parameter Set Window............................................ 2-10
Figure 2-13 ZTE RCT Setup—System Initialization Window ................................... 2-10
Figure 2-14 ZTE RCT Setup—Installation Finished Window ................................... 2-11
Figure 2-15 ZTE RCT Setup—Select Language Window........................................ 2-12
Figure 2-16 ZTE RCT Setup—License Agreement Window .................................... 2-12
Figure 2-17 ZTE RCT Setup—Select Installation Style Window .............................. 2-13
Figure 2-18 ZTE RCT Setup—Select Product Window............................................ 2-13
Figure 2-19 ZTE RCT Setup—System Information Detection Window .................... 2-14
Figure 2-20 ZTE RCT Setup—Installation Information Confirmation Window........... 2-15
Figure 2-21 ZTE RCT Setup—Unzip and Copy Files Window ................................. 2-15
Figure 2-22 ZTE RCT Setup—Parameter Set Window............................................ 2-16
Figure 2-23 ZTE RCT Setup—System Initialization Window ................................... 2-17
Figure 2-24 ZTE RCT Setup—Installation Finished Window ................................... 2-17
Figure 2-25 NetNumen(TM) Unified Management System—Console
Window................................................................................................. 2-18
Figure 2-26 Login - RCT Client Dialog Box ............................................................. 2-19
Figure 3-1 NE Management Window ........................................................................3-2
Figure 3-2 Add Dialog Box........................................................................................3-3
I

Figure 3-3 Subscriber Trace Window ........................................................................3-7
Figure 3-4 Signaling Tab ......................................................................................... 3-10
Figure 3-5 Choose Version Dialog Box ................................................................... 3-11
Figure 3-6 Create Task Dialog Box—Package Task Info ......................................... 3-12
Figure 3-7 Create Task Dialog Box—NE List........................................................... 3-13
Figure 3-8 Create Task Dialog Box—Subtask ......................................................... 3-14
Figure 3-9 Create Multi Ne Task Dialog Box—Selecting NEs .................................. 3-16
Figure 3-10 Create Multi Ne Task Dialog Box—Setting Task Parameters ................ 3-17
Figure 3-11 Signaling Tracing Window—Signaling Data Displayed in a List ............ 3-18
Figure 3-12 Signaling Tracing Window—Signaling Data Displayed in a Line
Chart .................................................................................................... 3-20
Figure 3-13 Signaling Tracing Window—Signaling Data Displayed in Graph
Format.................................................................................................. 3-21
Figure 3-14 Multi Monitor Dialog Box ...................................................................... 3-22
Figure 3-15 View Data Dialog Box .......................................................................... 3-23
Figure 3-16 Signaling Data File............................................................................... 3-24
Figure 3-17 Local Setting Dialog Box...................................................................... 3-26
Figure 3-18 Server Parameter Setting Dialog Box................................................... 3-26
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 2-1 Signaling Tracing Modules ........................................................................2-5
Table 2-2 Parameters in the ZTE RCT Setup—Database Connection Configuration
Window....................................................................................................2-6
Table 3-1 NE Management Toolbar...........................................................................3-2
Table 3-2 NE Parameters Description .......................................................................3-3
Table 3-3 Subscriber Trace Tree ...............................................................................3-7
Table 3-4 Commands on the Shortcut Menu .............................................................3-8
Table 3-5 Task Types .............................................................................................. 3-12
Table 3-6 Toolbar Buttons for Managing Signaling Data in the List .......................... 3-18
III

Tables
IV

Glossary
Abis
- Abis Interface between BSC and BTS
BSC
- Base Station Controller
CPU
- Central Processing Unit
CS
- Circuit Switched
DLL
- Dynamic Link Library
EMS
- Element Management System
GSM
- Global System for Mobile Communications
IMSI
- International Mobile Subscriber Identity
MBMS
- Multimedia Broadcast/Multicast Service
MOSS
- Mobile Operation Support System
MTM
- Measurement Trace Management
NE
- Network Element
OMM
- Operation & Maintenance Module
PS
- Packet Switched
RCT
- RNC Call Trace
RNC
- Radio Network Controller
TD-SCDMA
- Time Division-Synchronization Code Division Multiple Access
V

UE
- User Equipment
UMTS
- Universal Mobile Telecommunication System
VI

SJ-20140527134054-018-ZXUR 9000 UMTS (V4.13.10.15) Calling Trace Operation Guide_582765.pdf

More Related Content

Similar to SJ-20140527134054-018-ZXUR 9000 UMTS (V4.13.10.15) Calling Trace Operation Guide_582765.pdf (20)

SJ-20140527134054-018-ZXUR 9000 UMTS (V4.13.10.15) Calling Trace Operation Guide_582765.pdf