ZXWR RNC (V3.09.30) Radio Network Controller Calling Trace Operation Guide

ZXWR RNCRadio Network Controller

Calling Trace Operation Guide

Version: 3.09.30

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright 2011 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 20100713 First Edition (V3.09.30.03)

R1.1 20100903 Updated:

1. 1.1 Software Functions

2. 2.1 Calling Trace Software Installation Overview

3. 2.2 Installing Procedures

4. 3.2 Starting Calling Trace Software Client

5. 3.4.3 Deleting NE

6. 3.5.5 Stopping Tasks

7. 3.5.8.1 Signaling Trace Toolbar Introduction (Table 3)

Added:

1. 1.4 the section "Networking Modes" is newly added after the

subsection (1.3.5) "RNL or TNL Module".

2. 2.3 the section " Configuration and Startup of MRM" is newly

added after the section " Installing Procedures"


R1.2 20101118 The following sections have been updated:

1. Software Functions

2. CT Manager Module

3. CT Server Module

4. Task Life Cycle

5. Software Performance

6. NE Management

7. Adding NE

8. Deleting NE

9. Modifying NE

10. Connecting Link

11. Disconnecting Link

12. Entering User Tracing

13. Monitoring Task

14. Signaling Trace Tool-bar Introduction

15. Saving All

16. Saving Selected Signaling

17. Searching

18. Filtering

19. Starting Monitor

20. Stopping Monitor

21. Suspend Or Restore Refreshing

22. Displaying in Full Screen

23. Original Code Source

24. Detailed Decoding

25. Deleting All

26. Suspend Or Restore Scrolling

R2.0 20110228 Second Edition(V3.09.30.09)

The following sections have been added Deployment Mode,

Independent Server Deployment, Sharing EMS Server

Deployment, Local NE Deployment, Tasks Synchronization,

Installing Calling Trace Software Server, Installing Calling Trace

Software Client, Port Offset Configuration, Viewing Data, Viewing

Trace Files Offline, Configuring Holiday, Setting User Password.

The following sections have been updaeedPreface, Calling Trace

Software Installation Overview, Configuration and Startup of MRM,

Entering NE Management Interface, Adding NE, Deleting NE,

Modifying NE, Connecting Links, Disconnecting Links, Entering

User Tracing, Trace Tasks Management, Starting Tasks, Stopping

Tasks, Deleting Tasks, Monitoring Tasks, Opening and Closing

Toolbar, Opening and Closing Statusbar, Opening and Closing

Message Checking, Closing Window, Locking Screen, Settting the


System, Setting Login User Information, Querying System Time,

Logging Out, Exiting the System

The following sections have been deleted Networking Modes,

Software Performance, Installing Calling Software Procedures.

Serial Number: SJ-20100603155704-018

Publishing Date: 2011-02-28(R2.0)

ContentsAbout This Manual ......................................................................................... I

Chapter 1 Basic Concept ........................................................................... 1-1

1.1 Software Functions............................................................................................. 1-1

1.2 Installation Modes .............................................................................................. 1-2

1.3 Software Modules .............................................................................................. 1-2

1.3.1 CT Client Module ..................................................................................... 1-2

1.3.2 CT Server Module .................................................................................... 1-3

1.3.3 CT Manager Module................................................................................. 1-3

1.3.4 CT Agent Module ..................................................................................... 1-3

1.3.5 RNL Or TNL Module................................................................................. 1-3

1.4 Deployment Modes ............................................................................................ 1-3

1.4.1 Independent Server Deployment ............................................................... 1-4

1.4.2 Deployment of Sharing EMS Server .......................................................... 1-5

1.4.3 Local NE Deployment ............................................................................... 1-6

1.5 Basic Concepts .................................................................................................. 1-7

1.5.1 Task Life Cycle......................................................................................... 1-7

1.5.2 Task Types .............................................................................................. 1-8

1.5.3 Tasks Synchronization .............................................................................. 1-9

Chapter 2 Software Installation................................................................. 2-1

2.1 Calling Trace Software Installation Overview........................................................ 2-1

2.2 Installing the Calling Trace Software Server ......................................................... 2-2

2.3 Installing Calling Trace Software Client .............................................................. 2-12

2.4 Port Offset Configuration .................................................................................. 2-16

2.5 Configuration and Startup of MRM..................................................................... 2-17

Chapter 3 Basic Operations ...................................................................... 3-1

3.1 Starting Calling Trace Software Server ................................................................ 3-1

3.2 Starting Calling Trace Software Client ................................................................. 3-3

3.3 Software Interface .............................................................................................. 3-4

3.4 Network Element Management ........................................................................... 3-6

3.4.1 Entering NE Management Interface........................................................... 3-6

3.4.2 Adding NE ............................................................................................... 3-7

3.4.3 Deleting NE ............................................................................................. 3-9

3.4.4 Modifying NE ......................................................................................... 3-10

I

3.4.5 Link Operation ........................................................................................3-11

3.4.6 User Tracing .......................................................................................... 3-13

3.4.7 Opening Data File .................................................................................. 3-44

3.4.8 Setting Client Parameters ....................................................................... 3-45

3.4.9 Viewing Trace Files Offline...................................................................... 3-46

3.5 Window ........................................................................................................... 3-47

3.5.1 Switching Window .................................................................................. 3-47

3.5.2 Opening and Closing Toolbar .................................................................. 3-48

3.5.3 Opening and Closing Statusbar............................................................... 3-49

3.5.4 Opening and Closing Message Checking................................................. 3-50

3.5.5 Closing Windows.................................................................................... 3-52

3.6 System Menu................................................................................................... 3-53

3.6.1 Locking Screen ...................................................................................... 3-53

3.6.2 Setting Print ........................................................................................... 3-55

3.6.3 User Customizing................................................................................... 3-56

3.6.4 Setting User Password ........................................................................... 3-60

3.6.5 Querying System Time ........................................................................... 3-61

3.6.6 Logging Out ........................................................................................... 3-62

3.6.7 Exiting The System ................................................................................ 3-63

Appendix A Troubleshooting ................................................................... A-1

A.1 Task Status Is Starting........................................................................................A-1

A.2 Software Server can not be Started.....................................................................A-1

Figures............................................................................................................. I

Tables .............................................................................................................V

Glossary .......................................................................................................VII

II

About This ManualPurpose

This manual presents the basic concepts, installation procedures, and operation methodsof the calling trace software. It helps maintenance personnels and technicians to locateand analyze fault causes and do troubleshooting in time.

What Is In This Manual

This manual includes four chapters and an appendix.

Chapter Summary

Chapter 1 Basic Concepts Introduces the basic function, installation mode,

structure and performance of calling tracing

software. It enables users to get an initial

understanding of the calling trace software and

lay the basis for future application.

Chapter 2 Installation Presents the installation procedures of the calling

trace software.

Chapter 3 Basic Operations Describes the basic operations of the calling

trace software, including entering/exiting the

system, NE management operation, users tracing

operation, tool and window operation.

Chapter 4 General Problems and Solutions Lists the solutions for two kinds of general

problems of the calling trace software.

Appendix Glossaries Presents the full English names of the glossaries.

Intended Audience

The intended audiences of this manual are as follows:

l Network optimization engineersl Maintenance engineersl Testing engineers

Reference

This manual references to the following document:

l ZXWRRNC (V3.09.30) Radio Network Controller Operation andMaintenanceModuleSoftware Installation Guide

I

Chapter 1Basic ConceptTable of Contents

Software Functions.....................................................................................................1-1Installation Modes ......................................................................................................1-2Software Modules ......................................................................................................1-2Deployment Modes ....................................................................................................1-3Basic Concepts ..........................................................................................................1-7

1.1 Software FunctionsThe calling trace software is an independent multiple NEs tracing management software,supporting visit of multiple clients, and supporting task tracing of multiple RNC NEs.

Generally, when errors occur with the network, calls break down, services becomeabnormal, or users are optimizing the network, the calling trace software can be used tolocate and analyze the faults. For those faults that can not be traced, the calling tracesoftware can help to determine the next step by analyzing the traced signaling.

With the calling trace software, users can easily trace and observe the real-time signalingmessage that the system reports. In addition, it facilitates the maintenance personnel tolocate faults and debug the system.

Calling trace exists in the form of calling trace task and measure trace task, aiming at suchobjects as mobile stations, cells and every network interface. At present, the system canprovide calling trace tasks at both radio network layer and transmission network layer atthe same time.

Functions relating to the calling trace software, such as system monitoring, rights control,log management, refer to the following documents:

l NetNumen M31(RAN) Mobile Network Element Management System SafetyManagement Operation Guide

l NetNumen M31(RAN) Mobile Network Element Management System PerformanceManagement Operation Guide

Note:

The calling trace software of the present version only provides functional modules of NEmanagement and users tracing.

1-1

SJ-20100603155704-018|2011-02-28(R2.0) ZTE Proprietary and Confidential

ZXWR RNC Calling Trace Operation Guide

1.2 Installation ModesAt present, the calling trace software adopts the client-server mode, as shown in Figure1-1.

In this mode, as soon as the calling trace software starts, the users connect to the callingtrace server through the calling trace client and then the server directly connects to theNE, as shown inFigure 1-1.

Figure 1-1 Client-Server-NE Mode

1.3 Software ModulesThe call trace software consists of CT Client module, CT Server Module, CT Manager onROMP board, CT Agent module on RNC board, and modules of RNL and TNL.

The relationships among all modules are shown in Figure 1-2.

Figure 1-2 Calling Trace Software Structure

1.3.1 CT Client ModuleCT Client module, the user software client, needs to be connected to the server when it isused to customize and start signaling trace tasks, and query signaling results.

The CT Client module is used independently as an independent calling trace client.

1-2


Chapter 1 Basic Concept

1.3.2 CT Server ModuleCT Server locates at the user software end to set up links with RNC and forward signalingtrace tasks and results.

CT Server is used independently as an independent calling trace server end.

CT Server connects with ROMP on RNC, intercommunicates with CT Manager module onROMP, and obtains message of signaling trace.

1.3.3 CT Manager ModuleCT Manager module resides on ROMP, forwarding trace control messages andsummarizing trace data messages.

l CT Manager receives the trace control messages from CT Server and forwards to CTAgent module on corresponding boards.

l CT Manager module receives the trace data messages from CT Agent module onRNC boards and forwards to CT Server.

l CT Manager module is the unique path between CT board software module and CTServer. The system controls the data flow and limits the trace control parameters inCT Manager module, such as, limits the signaling trace message traffic at the client.

l CTManager module informs CT Server of the configuration data modification reportedfrom CT board, detects and traces the connection/disconnection of communicationlink at the client in real time.

1.3.4 CT Agent ModuleCT Agent module is distributed on all boards. It connects with RNL application modules,and forwards trace control messages and trace data messages.

l CT Agent module receives the trace control messages from CT Manager, andforwards to the corresponding RNL application modules.

l CT Agent module receives the trace data message from all board RNL applicationmodules, and forwards to CT Manager.

l CT Agent, together with CT Manager, controls the data flow.

1.3.5 RNL Or TNL ModuleRNL or TNL module receives the calling trace control messages from CT Agent andstarts radio signaling/transmission signaling application processing modules on thecorresponding boards. It processes the signaling and data, and then sends the processedsignaling data to CT Agent module.

1.4 Deployment ModesRCT is a real-time signaling trace tool of multiple NEs. It is of client/server structure, needsto be deployed independently, and supports multiple clients tracing.

1-3



According to the deployed location of the software at the server, the deployment modes ofRCT fall into three kinds as follows:

l Independent server deploymentl Sharing EMS server deploymentl NE local deployment

1.4.1 Independent Server Deployment

Networking Modes

As an independent server, the calling trace server is deployed on EMS (EMS networksegment). It is separated from the EMS server, runs independently.

If EMS network segment does not connect to OMM network of ROMP, deploy MRM onOMM. The calling trace software server connects to RNC through MRM on OMM so as toexecute signaling trace operation. The specific deployment is shown in Figure 1-3.

Figure 1-3 Installing Calling Trace Software Server Independently

Requirement on Resources

Under the mode that the server is deployed independently, the requirement on resourcesis shown in .

Item Requirement

Recommended Server sun v4 SPARC Enterprise T5220 (virtual CPUs:

64, physical memory: 32G)

CPU Occupancy 10%

Memory Usage 2 G (RCT software occupies 1200M, the

database instance occupies 800M)

Disk Space 49546 M

Bandwidth 0.32 Mbps

1-4



Limitations

Under the mode that the server is deployed independently, the calling trace software hasthe following limitations:

l Support the trace of all tasks for 7*24 hours, and at most support 20 UE signalingtasks.

l At most support 4hour continuous observe of such real-time tasks as RTV and MTM.l At most support 0.5hour continuous trace of signaling tasks of the IU transmission

layer.l At most support 3day continuous trace of such other signaling tasks as cell signaling

tasks, and office direction signaling tasks.l Support offline trace of code stream tasks on the user plane.

1.4.2 Deployment of Sharing EMS Server

Networking Mode

The Server module can be integrated into the EMS server so that the calling tracesoftware can have centralized management on multiple NEs. Consequently, the callingtrace software can share the same server with EMS only if EMS still has processingcapability, which saves hardware costs. The specific deployment is shown inFigure 1-4.

Figure 1-4 Calling Trace Software Server is Integrated Into EMS Server

Note:

The server shared with EMS can run such operation systems as WINDOWS2003, LINUXor SOLARIS, while the client must run WINDOWS operation system.

The corresponding decoding database of the calling trace server, which is installed ondifferent operation platforms, is to decode signaling code streams. The decoding databaseis integrated into installation software.

Requirement on Resources

Under the deployment mode that the EMS server is shared, the requirement on resourcesis shown in .

1-5



Item Requirement

CPU Occupancy 10%

Memory Usage 2 G (RCT software occupies 1200 M, the

database instance occupies 800 M)

Disk Space 49546 M

Bandwidth 0.32 Mbps

Limitations

Under the deployment mode that the EMS server is shared, the calling trace software hasthe following limitations:

l Does not support the trace of all tasks for 7*24 hours. At most support 3daycontinuous trace and 20 UE signaling tasks.

l At most support 2hour continuous observe of such real-time tasks as RTV and MTM.l At most support 0.5hour continuous trace of signaling tasks of the IU transmission

layer.l At most support 1day continuous trace of such other signaling tasks as cell signaling

tasks, and office direction signaling tasks.l Support offline trace of code stream tasks on the user plane.

1.4.3 Local NE Deployment

The Calling Trace Software is Deployed at Local NE

For non-signaling-trace users, such as, users in the lab or during site access, the callingtrace software needs to be used as an on line signaling monitor tool to provide deploymentmodes for local NEs.

For local deployment, one MRM needs to be deployed on OMM so as not to affect therunning of OMM. The deployment mode of it is the same as other two deployment modes.The Server module and the Client module of the calling trace software can be run on twoPCs or on one PC simultaneously. The specific deployment mode is shown in Figure 1-5.

1-6



Figure 1-5 The Calling Trace Software is Deployed at Local NE

1.5 Basic ConceptsCalling trace exists in the form of calling trace tasks. When creating the calling trace tasks,users define task name, task description, task type, and calling trace object correspondingto the task type and traced parameter information.

Therefore, it is necessary to know about basic knowledge about the calling trace taskbefore using the calling trace software.

1.5.1 Task Life CycleThe calling trace task has a comprehensive life cycle that ranges from creating callingtrace tasks, maintaining calling trace task status to deleting calling trace tasks.

The comprehensive calling trace task life cycle is shown inFigure 1-6.

1-7



Figure 1-6 Calling Trace Task Life Cycle

As shown inFigure 1-6, the calling trace system supports the calling trace tasks in twostatuses: suspending status and running status. The present task status depends on useroperation, link status of the client and RNC NE. Only the calling trace tasks in the runningstatus can collect the signaling message and measurement graphs corresponding to thetask and display at the client.

1.5.2 Task TypesThere are six types of tasks that the calling trace software allows to trace, as shown inTable 1-1.

Table 1-1 Task Types

Type Home Board Purpose

UE Trace ROMP/RCP The trace task is to take UE as a tracing object.

1-8



Type Home Board Purpose

OFFICE-IU Trace ROMP/RAP To trace the signaling between RNC and CN

(Core Network), including PS domain signaling

trace and CS domain signaling trace.

OFFICE-IUR Trace ROMP/RCP To trace the signaling between RNC and

adjacent RNC.

OFFICE-IUB Trace ROMP/RCP To trace the signaling between RNC and

NODE B.

CELL Trace ROMP/RCP The trace task is to take CELL as a tracing

object.

MBMS Trace ROMP/RCP To designate session ID of MBMS, and the cell

where MBMS locates, and trace the signaling

related to MBMS.

1.5.3 Tasks SynchronizationThe calling trace software supports to synchronize tasks between itself and RNC NE inthe following two modes:

l Timing synchronization: The calling trace software sends task synchronizationmessages to NEs every 30 seconds, and the task status started will be changed toSYNC (under the status of being synchronized).

l For tasks in NEs but not in the calling trace software, they will be deleted by NEsautomatically.

l For tasks in the calling trace software but not in NEs, their status will be changed toSTOP automatically.

Caution!

When tasks are being synchronized as scheduled, please do not operate on them.

l Non-timing synchronization: The calling trace software will automatically initiate asynchronization of tasks when links are being connected. When links are interrupted,the status of the task being started will be set as SYNC by the software for latersynchronization.

TNL tasks can not be synchronized.

1-9



This page intentionally left blank.

1-10


Chapter 2Software InstallationTable of Contents

Calling Trace Software Installation Overview ..............................................................2-1Installing the Calling Trace Software Server ...............................................................2-2Installing Calling Trace Software Client.....................................................................2-12Port Offset Configuration ..........................................................................................2-16Configuration and Startup of MRM ...........................................................................2-17

2.1 Calling Trace Software Installation OverviewThe calling trace software consists of message routing module (MRM), the client, and theserver. The calling trace software installation package can complete the installation of theserver and client at one time. MRM is carried in OMM release package, you can completethe deployment of MRM according to Configuration and Startup of MRM. It does notneed to install MRM independently.

In Windows environment, the calling trace software installation procedures are as follows:

Note:

The installation method of the calling trace software under the environment of LINUX andSolaris, refer to the corresponding contents in this manual.

1. Installation preparation.

a. Oracle 10g database is installed.

b. Create a new example for calling trace software in Oracle database.

2. Installing the software server.

Installing the software client.

Setting port offset parameters.

Configuration and startup of MRM.

2-1



2.2 Installing the Calling Trace Software Server

Abstract

To introduce the installation procedures of the calling trace software server.

Prerequisites

1. Oracle 10g server is installed.2. To create a calling trace software instance (different from the instance used by NM

software).3. To modify the process as 400 when creating a calling trace software instance, as

shown in Figure 2-1.

Figure 2-1 Modifying Processes

4. The calling trace software can not be run simultaneously with NM server software onone PC.

Steps

1. The calling trace software installation directory is opened, and double-click setup.bat to install it.

2. The EMS System Installation window pops up. Press Enter and select the savingaddress that is for saving temporarily installed files by default.

3. The Select Language interface pops up, and select English from the pull-down boxaccording to the installation environment, as shown in Figure 2-2.

2-2


Chapter 2 Software Installation

Figure 2-2 Select Language

The language selected on the present interface is the language shown on the runningsoftware interface after the calling trace software is installed.

4. Click Next to bring up the License agreement interface, and check I accept thelicense agreement.

5. Click Next, and the Select Installation Style interface is opened, as shown in Figure2-3.

Figure 2-3 Select Installation Style

You can select the installation style according to the description in the right pane ofTips about current installation style.

2-3



6. Click the Next button, and the Network scale interface is opened, as shown in Figure2-4.

Figure 2-4 Network scale

You can select the network scale according to the description in the right pane of Tipsabout current selected scale.

7. Click Next, and the Select product interface is opened, as shown inFigure 2-5.

Figure 2-5 Select product

Check All Products.

Type the installation directory of the calling trace software in Program Area Path, orclick to select the installation path automatically.

2-4



Though Data Area Path is consistent with Program Area Path by default, you canset a different installation directory in Data Area Path as needed.

Note:

The item of CORBA Notify Service product is optional, thus enabling objectcommunications between different platforms and languages.

All other products must be selected.

8. Click Next, and the Database connection config interface is opened, as shown inFigure 2-6.

Figure 2-6 Database connection config

l Select ORACLE from the drop-down menu of Database type.l Database IP or hostname is the IP address of the Oracle server.l Database port is 1521 by default.l Database superuser name is the name of system users in Oracle environment.l Password is the same as the password that used by system users in Oracle

environment.l Click the Test Database Connection button to check whether the database is

connected successfully.

9. Click Next, and the Database Config interface is opened, and the database size ofUCA should be set the following :

a. Choose UCA in the Database Config interface to bring up a UCA pane under theinterface, as shown in Figure 2-7.

2-5



Figure 2-7 UCA config in Database config

b. Double-click the records in UCA config to bring up a Database config dialog box,as shown in Figure 2-8.

Figure 2-8 Database config

Note:

Due to the calling trace software does not have high requirement on alarms, thedisk space for saving alarm information can not be configured as large, you can setthe disk space size of alarms occupied as 1024 MB in Need disk space size(M).

2-6



c. Click OK, and the setting of UCA config completes.

10. Click Next, and the Host information config interface is opened, as shown in Figure2-10.

Figure 2-9 Host information config

Type the IP address, where the server is located, in Main process server address.

11. Click Next, and the System information detection interface is opened, as shown inFigure 2-10.

2-7



Figure 2-10 System information detection

12. Click the Next button to bring up the Installation Info Confirm interface, confirm theproducts information.

13. ClickNext, and theUnzip and Copy File interface is opened, as shown in Figure 2-11.

Figure 2-11 Unzip and Copy File

14. After unzip completes, click Next, and the Confirm interface of whether to executethese SQLs currently is opened, as shown in Figure 2-12.

2-8



Figure 2-12 Confirm

15. Click Yes, and the Installation database interface is opened, as shown in Figure 2-13.

Figure 2-13 Installation database

16. After the installation completes, clickNext, and theParameter Set interface is opened,as shown inFigure 2-14.

2-9



Figure 2-14 Parameter Set

Parameters on this interface do not need to be configured, and you can select defaultconfiguration for them.

17. Click Next to bring up the Confirm dialog box that inquires you whether to initialize allclient scenes, as shown in Figure 2-15.

Figure 2-15 Confirm

18. Click Next, and the System Initialization interface is opened, as shown in Figure2-16.

2-10



Figure 2-16 System Initialization

19. After the initialization completes, click Next, and the Installation finished interface isopened, as shown in Figure 2-17.

Figure 2-17 Installation Finished

Click Finish, and the installation of programs completes.

End of Steps

2-11



2.3 Installing Calling Trace Software Client

Abstract

To introduce how to install the calling trace software client.

Steps

1. The calling trace software installation directory is opened, and double-click setup.bat to install it.

2. The EMS System Installation window pops up. Press Enter and select the savingaddress that is for saving temporarily installed files by default.

3. The Select language interface is opened. Select English from the drop down menuaccording to the installation environment, as shown in Figure 2-18.

Figure 2-18 Select language

The language selected on the present interface is the language shown on the runningsoftware interface after the calling trace software is installed.

4. Click Next to bring up the License agreement interface, and check I accept thelicense agreement.

5. Click Next, and the Select Installation Style interface is opened, as shown in Figure2-19.

2-12



Figure 2-19 Select Installation Style

You can select the installation style according to the description in the right pane ofTips about current installation style.

6. Click Next, and the Select product interface is opened, as shown inFigure 2-20.

Figure 2-20 Select product

Check All Products.

Type the installation directory of the calling trace software in Program Area Path, orclick to select the installation path automatically.

Though Data Area Path is consistent with Program Area Path by default, you canset a different installation directory in Data Area Path as needed.

2-13



Note:

The item of CORBA Notify Service product is optional, thus enabling objectcommunications between different platforms and languages.

All other products must be selected.

7. Click Next, and the System information detection interface is opened, as shown inFigure 2-21.

Figure 2-21 System information detection

8. Click the Next button to bring up the Installation Info Confirm interface, confirm theproducts information.

9. Click Next, and the Unzip and Copy File interface is opened.

10. After the installation completes, clickNext, and theParameter Set interface is opened,as shown inFigure 2-22.

2-14



Figure 2-22 Parameter Set

Parameters on this interface do not need to be configured, and you can select defaultconfiguration for them.

11. Click Next to bring up the Confirm dialog box that inquires you whether to initialize allclient scenes, as shown in Figure 2-23.

Figure 2-23 Confirm

12. Click Next, and the System Initialization interface is opened.

13. After the initialization completes, click Next, and the Installation finished interface isopened.

14. Click Finish, and the installation of programs completes.

End of Steps

2-15



Example

Follow-Up Action

2.4 Port Offset Configuration

Abstract

When RCT is deployed as sharing the EMS server, port offset operations should beexecuted.

To log in the system as a root user and modify the configuration files of RCT, as shown inTable 2-1 and Table 2-2.

Table 2-1 Configuration File Table (1) of Port Offet

File Path File Name Modification

deploy-console.properti

es

console.server-

socket.port=32101

console.rmi.port=32102

ums-server\utils\consol

e\conf

10-rct-hostAgent.xml 32103

ums-server\utils\consol

e\works\console1\conf

deploy-console.properti

es

console.rmi.port=32106

console.server-

socket.port=32103

deploy-usf.properties usf.usf.ems.baseport=10000

usf.components.ftp.server.inter-

nalport=31111

/uep/snmp-

proxy/conf/V1/port=31165

/uep/snmp-

proxy/conf/V2C/port=31161

/uep/snmp-

proxy/conf/V3/port=31164

jboss.tomcat.http.internal-

port=31108

jboss.tomcat.https.internal-

port=31127

usf.compo-

nents.clocksync.sync.internal-

port=31124

ums-server\works\globa

l\deploy

global-ftpserver-proxy.

properties

Ftp.proxy.service.con-

fig.port=31121

2-16




deploy-web.properties usf.core.web.base.port=31750ums-server\works\uep\d

eploy

deploy-uep-port.propert

ies

usf.core.uep.base.port=31400

If RCT has been configured with SFTP, the configuration parameters of the 3 files under theums-server\works\sftpd\deploy directory should be modified, as shown in Table2-2.

Table 2-2 Configuration File Table (2) of Port Offet


deploy-sftpd.properties SFtpServer.server.con-

fig.port=31128

deploy-sftpd-consoleage

nt.properties

usf.consoleagent.process.sftpd.

agent.serversocket.port=31128

ums-server\works\sftpd

\deploy

deploy-sftpd-proxy.prop

erties

SFtp.proxy.service.con-

fig.port=31129

2.5 Configuration and Startup of MRMThe operation object of MRM (message routing module) is OMM.

Parameter configuration of MRM.

The config.properties file under the OMM installation directory ums-svr/tools/rct_v2_server_w/conf is opened. Each item should be configured. The config.pro

perties file is shown as the following:

#Thu May 20 15:58:06 CST 2010

bindAddr=127.0.0.1

port = 35059

ip_port=127.0.0.1:5057

Note:

The config.properties file is to configure the IP address of OMM, and the IP addressof RNC NE OMP. The MRM should be restarted if the configuration is valid.

1. Modify the bindAddr item: It indicates the IP address of the computer on which theMRM runs, such as:

bindAddr=10.9.1.129

2-17



the IP address of the OMM :10.9.1.129

2. port: It is the port of the computer on which the MRM runs. The port No. is 35059 bydefault and does not need to be modified.

3. Modify the IP address of RNC NE OMP, such as:

ip_port=127.0.0.1:5057

The IP address of the OMP board is 127.0.0.1. The port No. is 5057.

Note:

The MRM is started automatically with the calling trace software, so it does not need to bestarted manually.

Starting/Stopping of MRM

l Interfaces started on Console: Start and stop signaling transfer on the Console.l No interface started on the Console:

Stop the MRM: Log in to Linux, enter the ums-svr/bin/consolemml directory,and execute ums-svr/bin/consolemml.

Type Y and press Enter to restart the MRM, and the processes of the MRM willbe added to the Console.

2-18


Chapter 3Basic OperationsTable of Contents

Starting Calling Trace Software Server .......................................................................3-1Starting Calling Trace Software Client .......................................................................3-3Software Interface ......................................................................................................3-4Network Element Management ..................................................................................3-6Window ....................................................................................................................3-47System Menu ...........................................................................................................3-53

3.1 Starting Calling Trace Software Server

Abstract

To introduce how to start the calling trace software server.

Note:

At present, the calling trace software is not integrated into NetNumen software, and itneeds to be installed independently. Therefore, it is not recommended to be used bycommon users but only for advanced users in fault tracing and locating.

Prerequisites

The server and the client of the calling trace software are installed.

Steps

1. There are three modes of starting the calling trace software server.

a. The installation program directory is opened, and double-click the file \ums-server\console.bat under the program directory.

b. The system generates a shortcut Network Mage Console after the calling tracesoftware is installed. Double-click to start the server, as shown in Figure 3-1.

3-1



Figure 3-1 Network Manage Console Shortcut Icon

c. After the calling trace software is installed, the system will automatically add thestartup program to Start > Program. Click Network Manage System Consoleto start the program, as shown in Figure 3-2.

Figure 3-2 Network Manage Console Startup Menu

2. The Network Manage Console interface is opened, all processes of the server arestarted automatically and successfully, and the server is started successfully, as shownin Figure 3-3.

Figure 3-3 Starting Server Processes

Tip:

All processes of the server must be started successfully.

End of Steps

Follow-Up Action

l If it is necessary to stop a process, select this process and click .

3-2


Chapter 3 Basic Operations

l If it is necessary to start a process, select this process and click .

Note:

UEP Process and RCT Process can be started or stopped separately by selectingor .

3.2 Starting Calling Trace Software Client

Abstract

To introduce how to start the calling trace software client.

Prerequisites

The calling trace software server is started.

Steps

1. There are three modes of starting the calling trace software client:

a. The installation program directory is opened. Double-click the file \ums-client\client.exe under the program directory.

b. The system will generate a shortcut Network Manage System Client on thedesktop after the calling trace software is installed. Double-click the shortcut tostart the client, as shown in Figure 3-4.

Figure 3-4 NMS Client Shortcut Icon

c. After the calling trace software is installed, the system will automatically add astartup program to Start > Program. Click Network Manage System Client tostart the program, as shown in Figure 3-5.

Figure 3-5 NMS Client Starting Menu

2. The Login interface pops up, and input corresponding information, as shown in Figure3-6.

3-3



Figure 3-6 Login

3. Click OK. The NetNumen Unified Management System interface pops up, and theclient is started successfully, as shown in Figure 3-7.

Figure 3-7 NetNumen Unified Management System

End of Steps

3.3 Software InterfaceThe calling trace software interface is shown as Figure 3-8.

3-4



Figure 3-8 Calling Trace Interface Description

1. System menu bar2. Tool bar

3. Tree node window4. Working area

5. Message checking window6. Status bar

As shown in Figure 3-8, the calling trace software interface consists of six parts. Thefunction of every part is described as below:

1. System menu bar

The calling trace software system menu is available to the system menu bar. Userscan complete operation tasks of calling trace through the system menu.

2. Tool bar

Shortcut operation icons of the calling trace software are available to the tool bar.

There are six shortcut icons provided by the system at present, as shown in Table 3-1.

Table 3-1 Shortcut Introduction

Name Short Icon

Logout

Locking Screen

Window Exit

Window Forward

User Trace

NE Management

3. Tree Node Window

3-5



The command tree structure of present functional modules is available to the tree nodewindow. Right-click a single operation command in the tree node, and the system willexecute this operation.

4. Working area

The working area falls into Signaling > Measurement > Task Management, whichdisplays signaling information, measurement report and task list of present tracingtasks.

5. Message checking window

The message checking window displays interaction message generated by thecommunication between the calling trace client and the foreground NE. The interactionmessage includes prompt message and error message.

6. Status bar

The tool bar displays communication status of the calling trace software client andforeground NE.

3.4 Network Element ManagementOn the Network Element Management interface, users can complete such operations asadding, deleting and modifying RNC, connecting link and disconnecting link.

Note:

Operations on the Network Element Management interface are only to be performed onRNC information of the calling trace software, which does not change the actual RNC.

3.4.1 Entering NE Management Interface

Abstract

The NE Management interface is opened in the calling trace software.

Steps

1. In the software main interface, you can enter the NE management interface in twomodes, as shown in Figure 3-9.

3-6



Figure 3-9 NE management

l Click , and the NE management interface pops up.l Select Maintenance > Management, and the NE management interface pops

up, as shown in Figure 3-10.

Figure 3-10 Selecting NE Management

End of Steps

3.4.2 Adding NE

Abstract

To add RNC (NE) information according to IP address and port number of RNC, and toprovide a prerequisite for setting up physical links.

Steps

1. The NE Management interface is opened. You can add NE through the following twomethods:

3-7



l Click .l Right-click to select Add from the drop-down menu, as shown in Figure 3-11

Figure 3-11 Add NE

2. The Add interface pops up, as shown in Figure 3-12.

Figure 3-12 Add NE

l NE name: users can input NE name manually, but it can not be duplicated withthe name of the existing NEs.

l ID: input RNCID.l Type: by default.

3-8



l Link type: by default.l IP address:

RCT connects to NEs directly: Type the IP address of the OMP.

RCT connects to NEs through MRM: Configure the IP address as the IPaddress where the MRM resides. It is also the binding IP address configuredin the Configuration and Startup of MRM section.

l Port Number:

RCT connects to NEs directly: Type 5057 by default.

RCT connects to NEs through MRM: Configure the port as the monitoringport (35059 by default) of the computer on which the MRM resides.

3. Click OK, and adding NE completes.

End of Steps

3.4.3 Deleting NE

Prerequisites

In the calling trace software system, there is an RNCNE) message needs to be deleted,and this NE is disconnected.

Steps

1. Select the NE information to be deleted from the NE Management interface.

2. You can delete an NE through the following two mode:l Click .l Right-click to select Delete from the drop-down menu, as shown in Figure 3-13

Figure 3-13 Deleting NE Menu

3-9



3. The Confirm window pops up. Click Yes to delete, as shown in Figure 3-14.

Figure 3-14 Confirm

End of Steps

3.4.4 Modifying NE

Abstract

To modify parameters of RNC (NE) information added by users.

Prerequisites

A piece of RNC (NE) information to be modified exists in the system, and this NE isdisconnected.

Steps

1. Select the information to be modified from the NE Management interface.

2. You can modify NE information in the following two methods:l Click .l Right-click to select Modify from the drop-down menu, as shown in Figure 3-15

Figure 3-15 Modifying NE

3-10



3. The Add window pops up. Users can add NE information as needed, as shown inFigure 3-16.

Figure 3-16 Add NE Window

4. Click OK, and NE information is added.

End of Steps

3.4.5 Link OperationTo connect to RNC before you using the calling trace system. Link operation relating toRNC contains setting up link and interrupting link.

3.4.5.1 Connecting Link

Abstract

To connect socket link to RNC (NE) according to the added RNC (NE), and to connectphysical link for transmission of control information and data information.

Prerequisites

Relative NE information is added to NE Management.

Steps

1. Select an NE to be link connected, and set up links for this NE in the following twomodes:

3-11



l click .l Right-click to select connect from the drop-down menu, as shown in Figure 3-17.

2. Connecting link succeeds once the status of the selected NE has changed from 0 to1, as shown in Figure 3-17.

Figure 3-17 NE Connecting Link

End of Steps

3.4.5.2 Disconnecting Link

Abstract

To release link connection between NM software and RNC (NE), and to release the socketlink occupied by the software client.

After the link is disconnected, status of all calling trace tasks relating to this NE will bechanged into Suspend. If it is recovered to link of corresponding NEs, the correspondingtask status will return to Run.

Steps

1. Select the NE whose link needs to be disconnected, and you can disconnect its link inthe following two modes:

3-12



l Click .l Right-click to select disconnect, as shown in Figure 3-18.

Figure 3-18 Disconnecting Link

2. If NE status of the selected NE has changed from 1 to 0, the link is disconnectedsuccessfully, as shown inFigure 3-19.

Figure 3-19 Disconnecting NE Link

End of Steps

3.4.6 User TracingThe user tracing interface is to complete such operations as setting up, managing,modifying, deleting and monitoring of trace tasks.

3-13



3.4.6.1 Entering Subscriber Trace

Abstract

To introduce how to enter the subscriber trace interface.

Steps

1. In the calling trace software, you can enter Subscriber Trace in the following twomethods:l Click the button on the tool bar.l Select Maintenance > Subscriber Trace, as shown in Figure 3-20.

Figure 3-20 Subscriber Trace Menu Bar

2. The Subscriber Trace interface pops up, as shown in Figure 3-21.

Figure 3-21 Subscriber Trace

End of Steps

3-14



3.4.6.2 Creating Tasks

Abstract

Users need to create a tracing task before executing calling trace tasks. The status of thedefault task is Suspend after the task is created. Users only start corresponding tracingtasks when it is necessary to execute the tracing task.

Prerequisites

An NE is created and communication links are established successfully.

Steps

1. Double-click Create Task on the Subscriber Trace node at the right side of theinterface, as shown in Figure 3-22.

Figure 3-22 Creating Task Node

2. The Create Task interface pops up, as shown in Figure 3-23.

3-15



Figure 3-23 Create Task

l Task Name: Type the created tasks name, which can not be duplicated with thatof the existings.

l Select the object type of tasks to be created from the pull-down menu of TaskType.

3. Click Next to select NE and sub-task type that belong to the task, and click Add in theSub Task Type tab to be traced, as shown in Figure 3-24.

3-16



Figure 3-24 Selecting NE and Sub Task Type

Note:l To select the NE of creating a task in NE List. If the task relates to multiple NEs,

it needs to be created in every NE.l To select the type of creating sub-tasks in Sub-task Type.

4. Set task parameters, and click Finish to complete task creation.

End of Steps

3.4.6.3 Managing Trace Tasks

Abstract

To query trace tasks as needed in user-created trace tasks.

3-17



Steps

1. Double-click Trace Task Management on the Subscriber Trace tree node at the rightside of the interface, as shown in Figure 3-25.

Figure 3-25 Trace Task Management

2. The Task List window pops up. Select different tasks to check their properties, asshown in Figure 3-26.

Figure 3-26 Task List

End of Steps

3.4.6.4 Starting Tasks

Abstract

As needed, to manually start the trace task in the trace tasks created by users.

stop due to link broken, but the trace task will be restarted once the link is restored.

3-18



Users either start a single sub-task or start all sub-tasks of a certain object task once.

Steps

1. Select the trace tasks to be started in the Task List window. Right-click to select StartTask from the drop-down menu, as shown in Figure 3-27.

Figure 3-27 Starting Tasks

Note:

Users either start a single sub-task or start all sub-tasks of this task once by startingthe object task.

2. The trace task completes automatically once Task Status is changed from Stop toStart in Task List.

3-19



Note:

The created and started tasks on the server are displayed on the client that haveaccess to the server.

End of Steps

3.4.6.5 Stopping Tasks

Abstract

To stop the started tracing tasks.

As for the started tracing task, if its link is interrupted, the system will automatically changeits status from START to STOP.

Users either stop a single sub-task or stop all sub-tasks of a certain object task.

Steps

1. Select the tracing tasks to be suspended in the Task List window. Right-click to selectStop Task from the drop-down menu, as shown in Figure 3-28.

Note:

Users either select stopping a single sub-task or select stopping all sub-tasks of thisobject task once by stopping the object task.

3-20



Figure 3-28 Stopping Tasks

2. Task stopping completes if Task Status is changed from START to STOP in Task List.

End of Steps

3.4.6.6 Monitoring Tasks

Abstract

To monitor the started tasks.

Steps

1. Select the tasks to be monitored in the Task List window, and right-click to selectMonitor from the drop-down menu, as shown in Figure 3-29.

3-21



Figure 3-29 Monitor

2. Two kinds of Window pop up according to different sub-tasks created.l Signaling trace task: The Signaling Trace Taskwindow is displayed in Signaling

Working Area, and the signaling trace task can be checked in the Signaling tab,as shown in Figure 3-30.

3-22



Figure 3-30 Signaling Trace Window

Note:

You can check the detailed information of a signaling through doubleclicking itin Signaling Trace Task .

l Measurement trace task: the Measurement Trace Task window is displayed inMeasurement Working Area, and measurement trace task can be checked inthe Measurement tab, as shown in Figure 3-31.

3-23



Figure 3-31 Measurement Trace Window

End of Steps

3.4.6.7 Viewing Data

Abstract

To view the signaling trace files of a single task saved on the server, and to download andto save them to the local client as needed.

Prerequisites

The signaling trace files are saved on the server.

Steps

1. In the Task List window, select a task to be viewed, and right-click to select View Datafrom the drop-down menu, as shown in Figure 3-32.

3-24



Figure 3-32 View Data

2. A View Data dialog box pops up, as shown in Figure 3-33.

Figure 3-33 View Data Dialog Box

3. Choose a data file. Click Show, a Monitor interface of tasks pops up, and you canview the detailed calling trace data.

3-25



Note:

Operations of viewing calling trace data, refer to the Signaling Trace TaskManagement section.

End of Steps

Example

Follow-Up Action

l Click Download, and the data file selected can be saved locally.l Click Download All, and all data files under this task can be saved locally.

3.4.6.8 Signaling Trace Task Management

Note:

Signaling trace management needs to be operated under the monitoring mode after thetask is started. Users select a task in the task list, and right-click to select Monitor fromthe pull-down menu.

After users have started a signaling trace task, RNC will periodically report signaling traceinformation which is set on the signaling trace task.

The operation control signalings displaying and saving mode in the signaling displaywindow can be achieved via such operations as saving, searching, filtering, startingmonitor, stopping monitor, suspending refreshing, full screen displaying code source,detailed decoding, deleting all and suspending scrolling, etc. These operations are onlyavailable to signaling trace tasks.

3.4.6.8.1 Signaling Trace Tool-bar Introduction

Abstract

To introduce every buttons function on the tool-bar of the signaling trace window in themonitoring mode.

The Monitor window is opened. If signaling trace tasks are created by users, the tool baris shown asFigure 3-34, and every buttons function is shown as Table 3-2.

Figure 3-34 Tool-bar Introduction

3-26



Table 3-2 Tool-bar Button Introduction

Operation Icon Effect Description

Save all To save all signaling on

the interface, and the

output format is csv.

None

Save selected To save the selected

signaling on the

interface, and the output

format is csv.

None

Search According to the

displayed columns

name, search from the

selected signaling to

the downward. It will

automatically shift to the

top when it searches to

the bottom.

The shortcut is

Ctrl+F.

Filter To filter according to

the filtering conditions

selected by users, and

its result is displayed

in the new created

interface.

Filtering results will

be displayed in a new

window.

Start monitor To monitor tasks. The task is monitored

Stop monitor To stop monitoring

tasks.

The task is stopped

monitoring.

Pause/Restore refresh Interface

stopped/Restore

refreshing

None

Full screen/Exit full

screen

The interface is

displayed in full

screen/To restore from

full screen to non full

screen.

None

Code source To display code source

of the present selected

signaling.

Double-click one

signaling also triggers

code source.

3-27



Operation Icon Effect Description

Specific decoding To display specific

decoding information of

signaling data.

Double-click one

signaling also triggers

code source.

Delete all To delete all signaling

on the interface.

Irreversible operation.

Pause/Restore scroll The table displays

switching to

automatically

scroll/Stopping

automatically scroll.

None

3.4.6.8.2 Saving All

Abstract

To save all signaling in the file format of *.csv.

Note:

Signaling information is the operation object of saving all signaling. It is generated frompresent signaling trace tasks that are selected by users.

Steps

1. The Signaling window is opened. You can save all by using the following methods:l Click .l Right-click to select Save All from the pull-down menu, as shown in Figure 3-35

3-28



Figure 3-35 Save All

2. The Save dialog box pops up. Set the filename and saving path, and the system willsave all selected signaling information in the format of *.csv after clicking the Savebutton, as shown in Figure 3-36.

Figure 3-36 Setting Save Path

End of Steps

3-29



3.4.6.8.3 Saving Signaling Selected

Abstract

To select the signaling to be saved in the file format of *.csv.

Note:

Signaling information is the operation object of saving the signaling selected. It isgenerated from present signaling trace tasks that are selected by users.

Prerequisites

In the signaling trace system, there is signaling information to be saved.

Steps

1. The Signaling window is opened. Either press Shift to select multiple continuoussignaling information or press Ctrl to select multiple signaling information in eachsection.

2. Save the signaling selected through the following two methods.l Click under the signaling window.l Right-click to select Save Selected from the pull-down menu, as shown in Figure

3-37.

Figure 3-37 Saving Selected Signaling

3-30



3. The Save dialog box pops up. Set the filename and saving path, and the systemwill automatically save the selected signaling information in the format of *.csv afterclicking the Save button, as shown in Figure 3-38.

Figure 3-38 Setting Save Path

End of Steps

3.4.6.8.4 Searching

Abstract

According to the searching condition set by users, to search signaling information that iscompliant with the condition in the signaling display window.

Prerequisites

In the signaling tracing system, and there is signaling information to be searched.

Steps

1. The Signaling Trace window is opened. You can search signaling through thefollowing two methods:l Click .l Right-click to select Search from the pull-down menu, as shown in Figure 3-39

3-31



Figure 3-39 Search

2. The Search dialog box pops up. After setting searching condition, click the Searchbutton and the system will locate the signaling information that is compliant with thesearching condition in the Signaling Trace window Figure 3-40, as shown in Figure3-40.

Figure 3-40 Setting Search Condition

End of Steps

3-32



3.4.6.8.5 Filtering

Abstract

The signaling information in accord with the filtering conditions is displayed in theSignaling Display window according to the filtering conditions preset.

Prerequisites

In the signaling trace system, and there is signaling information to be filtered.

Steps

1. The Signaling Trace window is opened. You can execute filtering operations throughthe following two methods:l Click .l Right-click to select Filter from the pull-downmenu popped up, as shown in Figure

3-41

Figure 3-41 Filtering

2. The Filter dialog box pops up. After setting the condition of displaying filtering, clicktheOK button and the system will display the signaling result that is compliant with thefiltering conditions, as shown in Figure 3-42.

3-33



Figure 3-42 Setting Filter Conditions

You can right-click or to add or delete filtering conditions.

End of Steps

3.4.6.8.6 Starting Monitor

Abstract

To start monitoring the stopped signalling trace tasks.

Note:

Monitoring is running on the calling trace server after the signaling trace task is started. Itseffect is to display the traced signaling on the client.

Prerequisites

In the signaling trace system , there is signaling information stopped.

The Starting Monitor button can not be operated because tasks are in monitoring status.

3-34



Steps

1. The Signaling Tracewindow is opened. You can start to monitor through the followingtwo methods:l Click .l Right-click Start Monitor, as shown in Figure 3-43

Figure 3-43 Starting Monitor

End of Steps

3.4.6.8.7 Stopping Monitor

Abstract

To stop monitoring of signaling trace tasks in execution.

Note:

To stop monitoring that does not affect signaling trace tasks and does not stop running oftasks.

Prerequisites

There is signaling information running in the signaling trace system.

Tasks are stopped monitoring, and they are unavailable.

3-35



Steps

1. TheSignaling Tracewindow is opened. You can stopmonitoring through the followingtwo methods:l Click .l Right-click to select Stop Monitor from the pull-down menu, as shown in Figure

3-44

Figure 3-44 Stopping Monitor

End of Steps

3.4.6.8.8 Suspending Or Restoring Refreshing

Abstract

To suspend or restore signaling display function reported from RNC, and the signalingtrace system also suspends saving the signaling information of signaling display window.

Prerequisites

The signaling trace system is running properly and connecting to RNC, and there arestarted signaling tracing tasks relating to this NE.

Steps

l Suspend refreshing: the Signaling Trace window is opened. The system willautomatically suspend the display function of signaling reported from RNC, andsuspend displaying the signaling information of the Signaling Trace window afteryou suspend refreshing through the following two methods:

3-36



l Click .l Right-click to select Suspend from the pull-down menu, as shown in Figure 3-45

Figure 3-45 Suspend Refreshing

l Restore refreshing: in suspend refreshing status, re-click to restore the displayingfunction of signaling reported from RNC, and the system will also restore savingsignaling information of the Signaling Trace window.

End of Steps

3.4.6.8.9 Displaying In Full Screen

Abstract

The signaling trace task window is displayed in full screen.

Steps

1. The Signaling Trace window is opened. You can display the tracing task in full screenthrough the following two methods:l Click .l Right-click to select Full Screen from the pull-down menu, as shown in Figure

3-46

3-37



Figure 3-46 Full Screen Displaying

2. The Signaling Trace window is displayed in full screen.

3. Re-click the button to restore the Signaling Trace window to its original size.

End of Steps

3.4.6.8.10 Original Code Stream

Abstract

To display original code stream of the selected signaling.

Steps

1. Select a single signaling in the Signaling Trace window. You can display the originalcode stream through the following two methods:l Click .l Right-click to select Flow Source from the pull-down menu, as shown in Figure

3-47

3-38



Figure 3-47 Selecting Flow Source

2. Under the Signaling Trace window, the Flow Source tab pops up, as shown in Figure3-48.

Figure 3-48 Flow Source Window

End of Steps

3.4.6.8.11 Detailed Decoding

Abstract

To display all detailed decoding of the selected signaling.

3-39



Steps

1. The Signaling Trace window is opened. You can display the detailed decodingthrough the following two methods:l Select a single signaling , and click .l After selecting a single signaling, right-click to select Detailed Decoding from

the pull-down menu, as shown in Figure 3-49

Figure 3-49 Detailed Decoding

2. Under the Signaling Trace window, the Detailed Information tab pops up, as shownin Figure 3-50.

3-40



Figure 3-50 Detailed Decoding Window

End of Steps

3.4.6.8.12 Deleting All

Abstract

To delete all signaling on the interface, which does not affect running of signaling tracetasks.

Prerequisites

In the signaling trace system, there is signaling information to be deleted.

Steps

1. The Signaling Tracewindow is opened, you can delete signaling through the followingtwo methods:l Select a signaling, and click .l Right-click to select Delete All from the pull-down menu, as shown in Figure 3-51

3-41



Figure 3-51 Delete All

2. All signaling is deleted from the Signaling Trace window.

Note:

This operation procedure is irreversible.

This procedure is to delete the signaling displayed in the monitoring mode, which doesnot delete the signaling files in the signaling trace task.

End of Steps

3.4.6.8.13 Suspending Or Restoring Scrolling

Abstract

To set the displaying mode of signaling in the window.

To set the system whether automatically scroll to display the last record of signaling in thewindow.

3-42



Note:

Suspend or restore scrolling is different from suspend refreshing as the following:

l Suspend refreshing: Stop the display function of signaling reported from RNC, thesystem suspends displaying signaling information.

l Suspend scrolling: Suspend scroll displaying of signaling information only, which doesnot affect RNC reporting signaling.

Prerequisites

The signaling trace system is running properly and connecting to RNC, and there arestarted signaling trace tasks relating to this RNC in the system.

Steps

1. Suspend scrolling: the Signaling Trace window is opened. The system will scrollto display the last signaling record of Signaling Trace after you suspend signalinginformation in the following two methods:l Click .l Right-click to select Suspend Scroll from the pull-down menu, and , as shown in

Figure 3-52

Figure 3-52 Suspend Scrolling

3-43



2. Return to scrolling: in suspend scrolling status, click , and the system will restorescrolling to display the last record of the Signaling Trace window.

End of Steps

3.4.7 Opening Data File

Abstract

To open signaling trace files.

Suffix format of calling tracing files is *.csv.

Steps

1. Double-click Open data file in the Subscriber Trace tree node of the left pane, asshown in Figure 3-53.

Figure 3-53 Opening Data File

2. Select the signaling trace file saved in the system, and its format is .csv, as shown inFigure 3-54.

3-44



Figure 3-54 Selecting Data File

3. The defined signaling trace file is opened, as shown in Figure 3-55.

Figure 3-55 Opening Signaling Trace File

End of Steps

3.4.8 Setting Client Parameters

Abstract

To set parameters for the data table of the client.

3-45



Steps

1. Double-click the Set Client Parameter node under Subscriber Trace of the left pane,as shown in Figure 3-56.

Figure 3-56 Set Client Parameter

2. The Local Setting window pops up, and users can set data table capability, as shownin Figure 3-57.

Figure 3-57 Local Setting

End of Steps

3.4.9 Viewing Trace Files Offline

Abstract

When the client can not be connected to the server, RCT supports offline checking thesignaling trace files.

Note:

Operations of offline viewing trace files can only be performed under the environment ofthe Windows operation system.

3-46



Prerequisites

Latest decoding database files have been installed.

Context

Steps

1. Run the run.bat file under the installation ums-client\tools\rct-offlinedirectory of the RCT, and a language select dialog box pops up, as shown in Figure3-58.

Figure 3-58 language select

2. Select the language to be displayed. Click OK, the RCT Offline View Toll windowpops up, select the .csv file to be read as needed.

3. Click File > Open, and the Open window pops up

End of Steps

Follow-Up Action

For the specific operations (after the .csv file has been opened), refer to the SignalingTrace Task Management section.

3.5 WindowFunction of windows is to set switching among multiple functional windows.

As needed, users can open and close windows and the defined view bars in the functionof windows.

3.5.1 Switching Window

Abstract

To describe switching among multiple functional windows in the calling trace software.

Prerequisites

In the calling trace software system, there are more than two functional windows.

3-47



Steps

1. There are three modes of switching among multiple windows in the calling tracesoftware:l Click Window > Back, and Window > Forward or click and to achieve

switching between two neighbor windows, as shown in Figure 3-59.

Figure 3-59 Window Switching Menu

l Directly select window to be displayed in the Window menul Click the drop-down menu on the upper right of the calling trace software in-

terface. Select a window to be displayed as needed from the multiple openedfunctional menus, as shown in Figure 3-60.

Figure 3-60 Pull-down Menu

End of Steps

3.5.2 Opening and Closing Toolbar

Steps

1. The Calling Trace Software interface is opened and selectWindow > Toolbar. Thesystem will close the toolbar if it is displayed before being selected, and the system willdisplay the toolbar if it is not displayed before being selected, which is called closingand opening operation, as shown in Figure 3-61.

3-48



Figure 3-61 Opening Toolbar

2. The system executes opening or closing operation of the toolbar, as shown in Figure3-62.

Figure 3-62 Closing Toolbar

End of Steps

3.5.3 Opening and Closing Statusbar

Prerequisites

The calling trace software is running properly.

Steps

1. The Calling Trace Software interface is opened, and select Window > Status Bar.The system will close the statusbar if it is displayed before being selected, and thesystem will display the statusbar if it is not displayed before being selected, which iscalled closing and opening operation, as shown in Figure 3-63.

3-49



Figure 3-63 Opening Status Bar

2. The system executes opening and closing operation of the statusbar, as shown inFigure 3-64.

Figure 3-64 Closing Status Bar

End of Steps

3.5.4 Opening and Closing Message Checking

Prerequisites


3-50



Steps

1. The Calling Trace Software interface is opened, and select Window > MessageArea. The system will close the message area if it is displayed before being selected,and the system will display the message area if it is not displayed before beingselected, which is called closing and opening operation, as shown in Figure 3-65.

Figure 3-65 Closing Message Checking

2. The system executes opening and closing operation of message checking, as shownin Figure 3-66.

Figure 3-66 Opening Message Checking

3-51



Different message can be checked separately through the Hint Message tab and theError Message tab in the Show Message window.

End of Steps

3.5.5 Closing Windows

Abstract

To close each window displayed in the calling trace software.

Prerequisites

There are windows displayed in the calling trace software system.

Steps

1. You can close windows in the following two modes:l ClickWindow > Close Current window , and click Close All Windows or Close

Other Windows to close the windows displayed, as shown in Figure 3-67.

Figure 3-67 Closing Window Operation

l Click on the upper right corner of the calling trace software interface to closethe current windows, or select from the pull-down menu of Close, as shown inFigure 3-68.

3-52



Figure 3-68 Close Menu

Close current window: currently displayed window.

Close all windows: all opened windows in the software.

Close other windows: save currently displayed windows and closenon-displayed windows on the interface.

End of Steps

3.6 System MenuUsers can lock screen, set printing, customize, check system time, log out and exit systemthrough the system menu.

3.6.1 Locking Screen

Abstract

To lock the calling trace client, users have to re-login if they want to reuse it.

Steps

1. TheCalling Trace Software interface is opened. You can lock screens in the followingtwo modes:l Click the System > Lock Screen menu, as shown in Figure 3-69.

Figure 3-69 Lock Screen

l Click the button on the toolbar.

2. The Select Lock Type window pops up, as shown in Figure 3-70.

3-53



Figure 3-70 Select Lock Type

l Lock Screen: current interface is invisible, and the Lock Screen interface popsup. It is unlocked by inputting password.

l Lock Operation : current operation interface is visible. PressCtrl+U and the LockScreen interface pops up to unlock.

3. Click OK, and the Confirm window pops up, as shown in Figure 3-71.

Figure 3-71 Confirm Window

4. Click OK, and the Lock Screen window pops up, and the screen is locked, as shownin Figure 3-72.

Figure 3-72 Lock Screen Window

End of Steps

3-54



3.6.2 Setting Print

Abstract

To print signaling trace files.

Prerequisites

There are signaling files need to be printed in the calling trace software system.

Steps

1. The calling trace software is opened. Click System > Print Setup, as shown in Figure3-73.

Figure 3-73 Print Setup

2. The Print Setup window pops up, as shown in Figure 3-74.

Figure 3-74 Print Setup Interface

3-55



To set printing according to different requirements in these three tabs ofGeneral, PageSetup, and Advanced.

3. Click OK to start printing.

End of Steps

3.6.3 User CustomizingUsers can set the system, login information, and holiday configuration through the UserCustomize menu.

3.6.3.1 Setting the System

Abstract

To set system parameters in the System window as needed.

Prerequisites


Steps

1. The Calling Trace Software interface is opened. Click System > User Customize >System Setting, as shown in Figure 3-75.

Figure 3-75 System Setting Menu

2. The System Setting window pops up, as shown in Figure 3-76.

3-56



Figure 3-76 System Setting Window

l The Auto Screen Lock Time tab: select whether to start Auto Locking Screen,and set locking time and mode.

l The Auto Logout tab : select whether to start Auto Logout, and set waiting time.l The Message Area tab : set hint message and error message shown in the

Signaling Tracing window.l The Query Settings tab : set querying result

ZXWR RNC (V3.09.30) Radio Network Controller Calling Trace Operation Guide

Documents

Transcript of ZXWR RNC (V3.09.30) Radio Network Controller Calling Trace Operation Guide