Beruflich Dokumente
Kultur Dokumente
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 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.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
20100713
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"
Revision No.
Revision Date
Revision Reason
R1.2
20101118
R2.0
20110228
Second Edition(V3.09.30.09)
The following sections have been added Deployment Mode,
Independent
Server
Deployment,
Sharing
EMS
Server
Revision No.
Revision Date
Revision Reason
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.
Contents
About 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
Figures............................................................................................................. I
Tables .............................................................................................................V
Glossary .......................................................................................................VII
II
Summary
Chapter 2 Installation
Appendix Glossaries
Intended Audience
The intended audiences of this manual are as follows:
l
l
l
Reference
This manual references to the following document:
l
ZXWR RNC (V3.09.30) Radio Network Controller Operation and Maintenance Module
Software Installation Guide
II
Chapter 1
Basic Concept
Table of Contents
Software Functions.....................................................................................................1-1
Installation Modes ......................................................................................................1-2
Software Modules ......................................................................................................1-2
Deployment Modes ....................................................................................................1-3
Basic Concepts ..........................................................................................................1-7
Note:
The calling trace software of the present version only provides functional modules of NE
management and users tracing.
1-1
SJ-20100603155704-018|2011-02-28(R2.0)
1-2
SJ-20100603155704-018|2011-02-28(R2.0)
CT Manager receives the trace control messages from CT Server and forwards to CT
Agent module on corresponding boards.
CT Manager module receives the trace data messages from CT Agent module on
RNC boards and forwards to CT Server.
CT Manager module is the unique path between CT board software module and CT
Server. The system controls the data flow and limits the trace control parameters in
CT Manager module, such as, limits the signaling trace message traffic at the client.
CT Manager module informs CT Server of the configuration data modification reported
from CT board, detects and traces the connection/disconnection of communication
link at the client in real time.
CT Agent module receives the trace control messages from CT Manager, and
forwards to the corresponding RNL application modules.
CT Agent module receives the trace data message from all board RNL application
modules, and forwards to CT Manager.
CT Agent, together with CT Manager, controls the data flow.
According to the deployed location of the software at the server, the deployment modes of
RCT fall into three kinds as follows:
l
l
l
Requirement on Resources
Under the mode that the server is deployed independently, the requirement on resources
is shown in .
Item
Requirement
Recommended Server
CPU Occupancy
10%
Memory Usage
Disk Space
49546 M
Bandwidth
0.32 Mbps
1-4
SJ-20100603155704-018|2011-02-28(R2.0)
Limitations
Under the mode that the server is deployed independently, the calling trace software has
the following limitations:
l
l
l
l
l
Support the trace of all tasks for 7*24 hours, and at most support 20 UE signaling
tasks.
At most support 4hour continuous observe of such real-time tasks as RTV and MTM.
At most support 0.5hour continuous trace of signaling tasks of the IU transmission
layer.
At most support 3day continuous trace of such other signaling tasks as cell signaling
tasks, and office direction signaling tasks.
Support offline trace of code stream tasks on the user plane.
Note:
The server shared with EMS can run such operation systems as WINDOWS2003, LINUX
or SOLARIS, while the client must run WINDOWS operation system.
The corresponding decoding database of the calling trace server, which is installed on
different operation platforms, is to decode signaling code streams. The decoding database
is integrated into installation software.
Requirement on Resources
Under the deployment mode that the EMS server is shared, the requirement on resources
is shown in .
1-5
SJ-20100603155704-018|2011-02-28(R2.0)
Item
Requirement
CPU Occupancy
10%
Memory Usage
Disk Space
49546 M
Bandwidth
0.32 Mbps
Limitations
Under the deployment mode that the EMS server is shared, the calling trace software has
the following limitations:
l
l
l
l
l
Does not support the trace of all tasks for 7*24 hours. At most support 3day
continuous trace and 20 UE signaling tasks.
At most support 2hour continuous observe of such real-time tasks as RTV and MTM.
At most support 0.5hour continuous trace of signaling tasks of the IU transmission
layer.
At most support 1day continuous trace of such other signaling tasks as cell signaling
tasks, and office direction signaling tasks.
Support offline trace of code stream tasks on the user plane.
1-6
SJ-20100603155704-018|2011-02-28(R2.0)
1-7
SJ-20100603155704-018|2011-02-28(R2.0)
As shown inFigure 1-6, the calling trace system supports the calling trace tasks in two
statuses: suspending status and running status. The present task status depends on user
operation, link status of the client and RNC NE. Only the calling trace tasks in the running
status can collect the signaling message and measurement graphs corresponding to the
task and display at the client.
Home Board
Purpose
UE Trace
ROMP/RCP
1-8
SJ-20100603155704-018|2011-02-28(R2.0)
Type
Home Board
Purpose
OFFICE-IU Trace
ROMP/RAP
OFFICE-IUR Trace
ROMP/RCP
OFFICE-IUB Trace
ROMP/RCP
CELL Trace
ROMP/RCP
MBMS Trace
ROMP/RCP
l
l
Caution!
When tasks are being synchronized as scheduled, please do not operate on them.
1-9
SJ-20100603155704-018|2011-02-28(R2.0)
1-10
SJ-20100603155704-018|2011-02-28(R2.0)
Chapter 2
Software Installation
Table of Contents
Calling Trace Software Installation Overview ..............................................................2-1
Installing the Calling Trace Software Server ...............................................................2-2
Installing Calling Trace Software Client.....................................................................2-12
Port Offset Configuration ..........................................................................................2-16
Configuration and Startup of MRM ...........................................................................2-17
Note:
The installation method of the calling trace software under the environment of LINUX and
Solaris, 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
SJ-20100603155704-018|2011-02-28(R2.0)
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 on
one PC.
Steps
1. The calling trace software installation directory is opened, and double-click setup.b
at to install it.
2. The EMS System Installation window pops up. Press Enter and select the saving
address that is for saving temporarily installed files by default.
3. The Select Language interface pops up, and select English from the pull-down box
according to the installation environment, as shown in Figure 2-2.
2-2
SJ-20100603155704-018|2011-02-28(R2.0)
The language selected on the present interface is the language shown on the running
software interface after the calling trace software is installed.
4. Click Next to bring up the License agreement interface, and check I accept the
license agreement.
5. Click Next, and the Select Installation Style interface is opened, as shown in Figure
2-3.
Figure 2-3 Select Installation Style
You can select the installation style according to the description in the right pane of
Tips about current installation style.
2-3
SJ-20100603155704-018|2011-02-28(R2.0)
6. Click the Next button, and the Network scale interface is opened, as shown in Figure
2-4.
Figure 2-4 Network scale
You can select the network scale according to the description in the right pane of Tips
about current selected scale.
7. Click Next, and the Select product interface is opened, as shown inFigure 2-5.
Figure 2-5 Select product
Though Data Area Path is consistent with Program Area Path by default, you can
set a different installation directory in Data Area Path as needed.
Note:
The item of CORBA Notify Service product is optional, thus enabling object
communications between different platforms and languages.
All other products must be selected.
8. Click Next, and the Database connection config interface is opened, as shown in
Figure 2-6.
Figure 2-6 Database connection config
l
l
l
l
l
l
9. Click Next, and the Database Config interface is opened, and the database size of
UCA should be set the following :
a. Choose UCA in the Database Config interface to bring up a UCA pane under the
interface, as shown in Figure 2-7.
2-5
SJ-20100603155704-018|2011-02-28(R2.0)
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, the
disk space for saving alarm information can not be configured as large, you can set
the disk space size of alarms occupied as 1024 MB in Need disk space size(M).
2-6
SJ-20100603155704-018|2011-02-28(R2.0)
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 in
Figure 2-10.
2-7
SJ-20100603155704-018|2011-02-28(R2.0)
12. Click the Next button to bring up the Installation Info Confirm interface, confirm the
products information.
13. Click Next, and the Unzip 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 execute
these SQLs currently is opened, as shown in Figure 2-12.
2-8
SJ-20100603155704-018|2011-02-28(R2.0)
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, click Next, and the Parameter Set interface is opened,
as shown inFigure 2-14.
2-9
SJ-20100603155704-018|2011-02-28(R2.0)
Parameters on this interface do not need to be configured, and you can select default
configuration for them.
17. Click Next to bring up the Confirm dialog box that inquires you whether to initialize all
client scenes, as shown in Figure 2-15.
Figure 2-15 Confirm
18. Click Next, and the System Initialization interface is opened, as shown in Figure
2-16.
2-10
SJ-20100603155704-018|2011-02-28(R2.0)
19. After the initialization completes, click Next, and the Installation finished interface is
opened, as shown in Figure 2-17.
Figure 2-17 Installation Finished
2-11
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. The calling trace software installation directory is opened, and double-click setup.b
at to install it.
2. The EMS System Installation window pops up. Press Enter and select the saving
address that is for saving temporarily installed files by default.
3. The Select language interface is opened. Select English from the drop down menu
according 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 running
software interface after the calling trace software is installed.
4. Click Next to bring up the License agreement interface, and check I accept the
license agreement.
5. Click Next, and the Select Installation Style interface is opened, as shown in Figure
2-19.
2-12
SJ-20100603155704-018|2011-02-28(R2.0)
You can select the installation style according to the description in the right pane of
Tips about current installation style.
6. Click Next, and the Select product interface is opened, as shown inFigure 2-20.
Figure 2-20 Select product
Note:
The item of CORBA Notify Service product is optional, thus enabling object
communications between different platforms and languages.
All other products must be selected.
7. Click Next, and the System information detection interface is opened, as shown in
Figure 2-21.
Figure 2-21 System information detection
8. Click the Next button to bring up the Installation Info Confirm interface, confirm the
products information.
9. Click Next, and the Unzip and Copy File interface is opened.
10. After the installation completes, click Next, and the Parameter Set interface is opened,
as shown inFigure 2-22.
2-14
SJ-20100603155704-018|2011-02-28(R2.0)
Parameters on this interface do not need to be configured, and you can select default
configuration for them.
11. Click Next to bring up the Confirm dialog box that inquires you whether to initialize all
client scenes, as shown in Figure 2-23.
Figure 2-23 Confirm
2-15
SJ-20100603155704-018|2011-02-28(R2.0)
Example
Follow-Up Action
File Name
Modification
ums-server\utils\consol
deploy-console.properti
console.server-
e\conf
es
socket.port=32101
console.rmi.port=32102
10-rct-hostAgent.xml
<port>32103</port>
ums-server\utils\consol
deploy-console.properti
console.rmi.port=32106
e\works\console1\conf
es
console.serversocket.port=32103
ums-server\works\globa
usf.usf.ems.baseport=10000
deploy-usf.properties
usf.components.ftp.server.inter-
l\deploy
nalport=31111
/uep/snmpproxy/conf/V1/port=31165
/uep/snmpproxy/conf/V2C/port=31161
/uep/snmpproxy/conf/V3/port=31164
jboss.tomcat.http.internalport=31108
jboss.tomcat.https.internalport=31127
usf.components.clocksync.sync.internalport=31124
global-ftpserver-proxy.
Ftp.proxy.service.con-
properties
fig.port=31121
2-16
SJ-20100603155704-018|2011-02-28(R2.0)
File Path
File Name
Modification
ums-server\works\uep\d
deploy-web.properties
usf.core.web.base.port=31750
deploy-uep-port.propert
usf.core.uep.base.port=31400
eploy
ies
If RCT has been configured with SFTP, the configuration parameters of the 3 files under the
ums-server\works\sftpd\deploy directory should be modified, as shown in Table
2-2.
Table 2-2 Configuration File Table (2) of Port Offet
File Path
File Name
Modification
ums-server\works\sftpd
deploy-sftpd.properties
SFtpServer.server.config.port=31128
\deploy
deploy-sftpd-consoleage
usf.consoleagent.process.sftpd.
nt.properties
agent.serversocket.port=31128
deploy-sftpd-proxy.prop
SFtp.proxy.service.con-
erties
fig.port=31129
Note:
The config.properties file is to configure the IP address of OMM, and the IP address
of 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 the
MRM runs, such as:
bindAddr=10.9.1.129
2-17
SJ-20100603155704-018|2011-02-28(R2.0)
Note:
The MRM is started automatically with the calling trace software, so it does not need to be
started manually.
Starting/Stopping of MRM
l
l
Interfaces started on Console: Start and stop signaling transfer on the Console.
No interface started on the Console:
2-18
SJ-20100603155704-018|2011-02-28(R2.0)
Chapter 3
Basic Operations
Table of Contents
Starting Calling Trace Software Server .......................................................................3-1
Starting Calling Trace Software Client .......................................................................3-3
Software Interface ......................................................................................................3-4
Network Element Management ..................................................................................3-6
Window ....................................................................................................................3-47
System Menu ...........................................................................................................3-53
Note:
At present, the calling trace software is not integrated into NetNumen software, and it
needs to be installed independently. Therefore, it is not recommended to be used by
common 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-ser
ver\console.bat under the program directory.
b. The system generates a shortcut Network Mage Console after the calling trace
software is installed. Double-click to start the server, as shown in Figure 3-1.
3-1
SJ-20100603155704-018|2011-02-28(R2.0)
c. After the calling trace software is installed, the system will automatically add the
startup program to Start > Program. Click Network Manage System Console
to 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 are
started automatically and successfully, and the server is started successfully, as shown
in 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
3-2
SJ-20100603155704-018|2011-02-28(R2.0)
Note:
UEP Process and RCT Process can be started or stopped separately by selecting
or
.
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 the
desktop after the calling trace software is installed. Double-click the shortcut to
start 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 a
startup program to Start > Program. Click Network Manage System Client to
start 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 Figure
3-6.
3-3
SJ-20100603155704-018|2011-02-28(R2.0)
3. Click OK. The NetNumen Unified Management System interface pops up, and the
client is started successfully, as shown in Figure 3-7.
Figure 3-7 NetNumen Unified Management System
End of Steps
3-4
SJ-20100603155704-018|2011-02-28(R2.0)
As shown in Figure 3-8, the calling trace software interface consists of six parts. The
function of every part is described as below:
1. System menu bar
The calling trace software system menu is available to the system menu bar. Users
can 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-5
SJ-20100603155704-018|2011-02-28(R2.0)
The command tree structure of present functional modules is available to the tree node
window. Right-click a single operation command in the tree node, and the system will
execute this operation.
4. Working area
The working area falls into Signaling > Measurement > Task Management, which
displays signaling information, measurement report and task list of present tracing
tasks.
5. Message checking window
The message checking window displays interaction message generated by the
communication between the calling trace client and the foreground NE. The interaction
message includes prompt message and error message.
6. Status bar
The tool bar displays communication status of the calling trace software client and
foreground NE.
Note:
Operations on the Network Element Management interface are only to be performed on
RNC information of the calling trace software, which does not change the actual RNC.
Steps
1. In the software main interface, you can enter the NE management interface in two
modes, as shown in Figure 3-9.
3-6
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
End of Steps
3.4.2 Adding NE
Abstract
To add RNC (NE) information according to IP address and port number of RNC, and to
provide a prerequisite for setting up physical links.
Steps
1. The NE Management interface is opened. You can add NE through the following two
methods:
3-7
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
Click .
Right-click to select Add from the drop-down menu, as shown in Figure 3-11
l
l
l
NE name: users can input NE name manually, but it can not be duplicated with
the name of the existing NEs.
ID: input RNCID.
Type: by default.
3-8
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
Port Number:
RCT connects to NEs through MRM: Configure the port as the monitoring
port (35059 by default) of the computer on which the MRM resides.
3.4.3 Deleting NE
Prerequisites
In the calling trace software system, there is an RNC NE) 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
SJ-20100603155704-018|2011-02-28(R2.0)
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 is
disconnected.
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
SJ-20100603155704-018|2011-02-28(R2.0)
3. The Add window pops up. Users can add NE information as needed, as shown in
Figure 3-16.
Figure 3-16 Add NE Window
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 two
modes:
3-11
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
click .
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 to
1, as shown in Figure 3-17.
Figure 3-17 NE Connecting Link
End of Steps
Steps
1. Select the NE whose link needs to be disconnected, and you can disconnect its link in
the following two modes:
3-12
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
Click .
Right-click to select disconnect, as shown in Figure 3-18.
Figure 3-18 Disconnecting Link
End of Steps
3-13
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. In the calling trace software, you can enter Subscriber Trace in the following two
methods:
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
End of Steps
3-14
SJ-20100603155704-018|2011-02-28(R2.0)
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 the
interface, as shown in Figure 3-22.
Figure 3-22 Creating Task Node
3-15
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
Task Name: Type the created tasks name, which can not be duplicated with that
of the existings.
Select the object type of tasks to be created from the pull-down menu of Task
Type.
3. Click Next to select NE and sub-task type that belong to the task, and click Add in the
Sub Task Type tab to be traced, as shown in Figure 3-24.
3-16
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
Note:
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.
To select the type of creating sub-tasks in Sub-task Type.
3-17
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. Double-click Trace Task Management on the Subscriber Trace tree node at the right
side 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, as
shown in Figure 3-26.
Figure 3-26 Task List
End of Steps
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 Start
Task 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 starting
the object task.
2. The trace task completes automatically once Task Status is changed from Stop to
Start in Task List.
3-19
SJ-20100603155704-018|2011-02-28(R2.0)
Note:
The created and started tasks on the server are displayed on the client that have
access to the server.
End of Steps
Steps
1. Select the tracing tasks to be suspended in the Task List window. Right-click to select
Stop 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 this
object task once by stopping the object task.
3-20
SJ-20100603155704-018|2011-02-28(R2.0)
2. Task stopping completes if Task Status is changed from START to STOP in Task List.
End of Steps
Steps
1. Select the tasks to be monitored in the Task List window, and right-click to select
Monitor from the drop-down menu, as shown in Figure 3-29.
3-21
SJ-20100603155704-018|2011-02-28(R2.0)
3-22
SJ-20100603155704-018|2011-02-28(R2.0)
Note:
You can check the detailed information of a signaling through doubleclicking it
in Signaling Trace Task .
3-23
SJ-20100603155704-018|2011-02-28(R2.0)
End of Steps
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 Data
from the drop-down menu, as shown in Figure 3-32.
3-24
SJ-20100603155704-018|2011-02-28(R2.0)
3. Choose a data file. Click Show, a Monitor interface of tasks pops up, and you can
view the detailed calling trace data.
3-25
SJ-20100603155704-018|2011-02-28(R2.0)
Note:
Operations of viewing calling trace data, refer to the Signaling Trace Task
Management section.
End of Steps
Example
Follow-Up Action
l
l
Click Download, and the data file selected can be saved locally.
Click Download All, and all data files under this task can be saved locally.
Note:
Signaling trace management needs to be operated under the monitoring mode after the
task is started. Users select a task in the task list, and right-click to select Monitor from
the pull-down menu.
After users have started a signaling trace task, RNC will periodically report signaling trace
information which is set on the signaling trace task.
The operation control signalings displaying and saving mode in the signaling display
window can be achieved via such operations as saving, searching, filtering, starting
monitor, stopping monitor, suspending refreshing, full screen displaying code source,
detailed decoding, deleting all and suspending scrolling, etc. These operations are only
available to signaling trace tasks.
Abstract
To introduce every buttons function on the tool-bar of the signaling trace window in the
monitoring mode.
The Monitor window is opened. If signaling trace tasks are created by users, the tool bar
is shown asFigure 3-34, and every buttons function is shown as Table 3-2.
Figure 3-34 Tool-bar Introduction
3-26
SJ-20100603155704-018|2011-02-28(R2.0)
Icon
Save all
Effect
Description
None
None
signaling on the
interface, and the output
format is csv.
Search
According to the
The shortcut is
displayed columns
Ctrl+F.
To filter according to
be displayed in a new
window.
Start monitor
To monitor tasks.
Stop monitor
To stop monitoring
tasks.
monitoring.
Interface
None
Pause/Restore refresh
stopped/Restore
refreshing
Full screen/Exit full
The interface is
screen
displayed in full
None
Double-click one
signaling.
code source.
3-27
SJ-20100603155704-018|2011-02-28(R2.0)
Operation
Icon
Specific decoding
Delete all
Effect
Description
To display specific
Double-click one
decoding information of
signaling data.
code source.
Irreversible operation.
on the interface.
Pause/Restore scroll
None
switching to
automatically
scroll/Stopping
automatically scroll.
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 from
present 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
SJ-20100603155704-018|2011-02-28(R2.0)
2. The Save dialog box pops up. Set the filename and saving path, and the system will
save all selected signaling information in the format of *.csv after clicking the Save
button, as shown in Figure 3-36.
Figure 3-36 Setting Save Path
End of Steps
3-29
SJ-20100603155704-018|2011-02-28(R2.0)
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.
generated from present signaling trace tasks that are selected by users.
It is
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 continuous
signaling information or press Ctrl to select multiple signaling information in each
section.
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
SJ-20100603155704-018|2011-02-28(R2.0)
3. The Save dialog box pops up. Set the filename and saving path, and the system
will automatically save the selected signaling information in the format of *.csv after
clicking 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 is
compliant 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 the
following two methods:
l Click .
l Right-click to select Search from the pull-down menu, as shown in Figure 3-39
3-31
SJ-20100603155704-018|2011-02-28(R2.0)
2. The Search dialog box pops up. After setting searching condition, click the Search
button and the system will locate the signaling information that is compliant with the
searching condition in the Signaling Trace window Figure 3-40, as shown in Figure
3-40.
Figure 3-40 Setting Search Condition
End of Steps
3-32
SJ-20100603155704-018|2011-02-28(R2.0)
3.4.6.8.5 Filtering
Abstract
The signaling information in accord with the filtering conditions is displayed in the
Signaling 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 through
the following two methods:
l Click .
l Right-click to select Filter from the pull-down menu 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, click
the OK button and the system will display the signaling result that is compliant with the
filtering conditions, as shown in Figure 3-42.
3-33
SJ-20100603155704-018|2011-02-28(R2.0)
or
End of Steps
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. Its
effect 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
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. The Signaling Trace window is opened. You can start to monitor through the following
two methods:
l Click .
l Right-click Start Monitor, as shown in Figure 3-43
Figure 3-43 Starting Monitor
End of Steps
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 of
tasks.
Prerequisites
There is signaling information running in the signaling trace system.
Tasks are stopped monitoring, and they are unavailable.
3-35
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. The Signaling Trace window is opened. You can stop monitoring through the following
two 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
Abstract
To suspend or restore signaling display function reported from RNC, and the signaling
trace 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 are
started signaling tracing tasks relating to this NE.
Steps
l
Suspend refreshing: the Signaling Trace window is opened. The system will
automatically suspend the display function of signaling reported from RNC, and
suspend displaying the signaling information of the Signaling Trace window after
you suspend refreshing through the following two methods:
3-36
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
Click .
Right-click to select Suspend from the pull-down menu, as shown in Figure 3-45
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 screen
through 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
SJ-20100603155704-018|2011-02-28(R2.0)
End of Steps
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 original
code 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
SJ-20100603155704-018|2011-02-28(R2.0)
2. Under the Signaling Trace window, the Flow Source tab pops up, as shown in Figure
3-48.
Figure 3-48 Flow Source Window
End of Steps
Abstract
To display all detailed decoding of the selected signaling.
3-39
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. The Signaling Trace window is opened. You can display the detailed decoding
through 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 shown
in Figure 3-50.
3-40
SJ-20100603155704-018|2011-02-28(R2.0)
End of Steps
Abstract
To delete all signaling on the interface, which does not affect running of signaling trace
tasks.
Prerequisites
In the signaling trace system, there is signaling information to be deleted.
Steps
1. The Signaling Trace window is opened, you can delete signaling through the following
two 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
SJ-20100603155704-018|2011-02-28(R2.0)
Note:
This operation procedure is irreversible.
This procedure is to delete the signaling displayed in the monitoring mode, which does
not delete the signaling files in the signaling trace task.
End of Steps
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 the
window.
3-42
SJ-20100603155704-018|2011-02-28(R2.0)
Note:
Suspend or restore scrolling is different from suspend refreshing as the following:
l
l
Suspend refreshing: Stop the display function of signaling reported from RNC, the
system suspends displaying signaling information.
Suspend scrolling: Suspend scroll displaying of signaling information only, which does
not affect RNC reporting signaling.
Prerequisites
The signaling trace system is running properly and connecting to RNC, and there are
started signaling trace tasks relating to this RNC in the system.
Steps
1. Suspend scrolling: the Signaling Trace window is opened. The system will scroll
to display the last signaling record of Signaling Trace after you suspend signaling
information 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
SJ-20100603155704-018|2011-02-28(R2.0)
2. Return to scrolling: in suspend scrolling status, click , and the system will restore
scrolling to display the last record of the Signaling Trace window.
End of Steps
Steps
1. Double-click Open data file in the Subscriber Trace tree node of the left pane, as
shown 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 in
Figure 3-54.
3-44
SJ-20100603155704-018|2011-02-28(R2.0)
End of Steps
3-45
SJ-20100603155704-018|2011-02-28(R2.0)
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 shown
in Figure 3-57.
Figure 3-57 Local Setting
End of Steps
Note:
Operations of offline viewing trace files can only be performed under the environment of
the Windows operation system.
3-46
SJ-20100603155704-018|2011-02-28(R2.0)
Prerequisites
Latest decoding database files have been installed.
Context
Steps
1. Run the run.bat file under the installation ums-client\tools\rct-offline
directory of the RCT, and a language select dialog box pops up, as shown in Figure
3-58.
Figure 3-58 language select
2. Select the language to be displayed. Click OK, the RCT Offline View Toll window
pops 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 Signaling
Trace Task Management section.
3.5 Window
Function 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 function
of windows.
Prerequisites
In the calling trace software system, there are more than two functional windows.
3-47
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. There are three modes of switching among multiple windows in the calling trace
software:
and
to achieve
l Click Window > Back, and Window > Forward or click
switching between two neighbor windows, as shown in Figure 3-59.
Figure 3-59 Window Switching Menu
l
l
End of Steps
2. The system executes opening or closing operation of the toolbar, as shown in Figure
3-62.
Figure 3-62 Closing Toolbar
End of Steps
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 the
system will display the statusbar if it is not displayed before being selected, which is
called closing and opening operation, as shown in Figure 3-63.
3-49
SJ-20100603155704-018|2011-02-28(R2.0)
2. The system executes opening and closing operation of the statusbar, as shown in
Figure 3-64.
Figure 3-64 Closing Status Bar
End of Steps
3-50
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. The Calling Trace Software interface is opened, and select Window > Message
Area. 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 being
selected, 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 shown
in Figure 3-66.
Figure 3-66 Opening Message Checking
3-51
SJ-20100603155704-018|2011-02-28(R2.0)
Different message can be checked separately through the Hint Message tab and the
Error Message tab in the Show Message window.
End of Steps
Prerequisites
There are windows displayed in the calling trace software system.
Steps
1. You can close windows in the following two modes:
l Click Window > 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
Click on the upper right corner of the calling trace software interface to close
the current windows, or select from the pull-down menu of Close, as shown in
Figure 3-68.
3-52
SJ-20100603155704-018|2011-02-28(R2.0)
End of Steps
Steps
1. The Calling Trace Software interface is opened. You can lock screens in the following
two modes:
l Click the System > Lock Screen menu, as shown in Figure 3-69.
Figure 3-69 Lock Screen
Click the
2. The Select Lock Type window pops up, as shown in Figure 3-70.
3-53
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
Lock Screen: current interface is invisible, and the Lock Screen interface pops
up. It is unlocked by inputting password.
Lock Operation : current operation interface is visible. Press Ctrl+U and the Lock
Screen 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 shown
in Figure 3-72.
Figure 3-72 Lock Screen Window
End of Steps
3-54
SJ-20100603155704-018|2011-02-28(R2.0)
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 Figure
3-73.
Figure 3-73 Print Setup
3-55
SJ-20100603155704-018|2011-02-28(R2.0)
To set printing according to different requirements in these three tabs of General, Page
Setup, and Advanced.
3. Click OK to start printing.
End of Steps
Prerequisites
The calling trace software is running properly.
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
3-56
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
l
l
The Auto Screen Lock Time tab: select whether to start Auto Locking Screen,
and set locking time and mode.
The Auto Logout tab : select whether to start Auto Logout, and set waiting time.
The Message Area tab : set hint message and error message shown in the
Signaling Tracing window.
The Query Settings tab : set querying result quantity shown in each page in
querying tables.
End of Steps
Steps
1. The Calling Trace Software interface is opened. Click System > User Customize >
Login User Info Setting, as shown in Figure 3-77.
3-57
SJ-20100603155704-018|2011-02-28(R2.0)
2. The Login User Info Setting window pops up, as shown in Figure 3-78.
Figure 3-78 Login User Info Setting Window
End of Steps
Prerequisites
The calling trace software is running properly.
Steps
1. The Calling Trace Software view is opened. Click System > Customize > Holiday
Configuration, as shown in Figure 3-79.
3-58
SJ-20100603155704-018|2011-02-28(R2.0)
3. Click New, the Holiday dialog box pops up, and fill in the holiday configuration
information as needed, as shown in Figure 3-81.
3-59
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-81
Alternatively, you can click Modify and Delete to configure the holiday separately.
End of Steps
Prerequisites
To set the user password for logging in to the client in the calling trace software system..
Steps
1. The Calling Trace Software view is opened.
Setting, as shown in Figure 3-82.
3-60
SJ-20100603155704-018|2011-02-28(R2.0)
2.
The User Password Setting dialog box pops up, as shown in Figure 3-83.
Figure 3-83 User Password Setting Window
Steps
1. The Calling Trace Software interface is opened. Click the System > Query System
Time menu, as shown in Figure 3-84.
3-61
SJ-20100603155704-018|2011-02-28(R2.0)
2. The Query System Time window pops up, as shown in Figure 3-85.
Figure 3-85 Query System Time Window
End of Steps
Steps
1. The Calling Trace Software interface is opened. You can log out the client in the
following two modes:
l Click System > Logout, as shown in Figure 3-86.
3-62
SJ-20100603155704-018|2011-02-28(R2.0)
Click
on the toolbar.
2. The Confirm dialog box pops up. Click OK to log out the system..
End of Steps
Steps
1. The Calling Trace Software interface is opened. Click System > Exit, and the system
will be closed, as shown in Figure 3-87.
Figure 3-87 Exit System
End of Steps
3-63
SJ-20100603155704-018|2011-02-28(R2.0)
3-64
SJ-20100603155704-018|2011-02-28(R2.0)
Appendix A
Troubleshooting
Table of Contents
Task Status Is Starting ............................................................................................ A-1
Software Server can not be Started ........................................................................ A-1
Solution
Task Status is STARTING indicating that this task is in starting status, and it is ineffective
to restart this task at this time. To stop this task and to restart it when Task Status is
returned to STOP.
Solution
l
Either main processes can not be started or all operations can not be used even
starting succeeds.
1. Check specific operation information of main processes to see whether a hint is
showing that the database can not be connected, as shown in Figure A-1.
A-1
SJ-20100603155704-018|2011-02-28(R2.0)
3. If calling trace software service and monitoring of the database are started already,
stop and restart them.
4. If the FTP process can not be started, check your computers IP address to
see whether it is the same as the IP address on the console of the calling trace
software server, as shown in Figure A-3.
A-2
SJ-20100603155704-018|2011-02-28(R2.0)
Appendix A Troubleshooting
If they are different, which means that the IP address of your computer is different
from the binding IP address when the software is being installed. Therefore, to
modify your computers IP address to its original.
A-3
SJ-20100603155704-018|2011-02-28(R2.0)
A-4
SJ-20100603155704-018|2011-02-28(R2.0)
Figures
Figure 1-1 Client-Server-NE Mode ............................................................................ 1-2
Figure 1-2 Calling Trace Software Structure.............................................................. 1-2
Figure 1-3 Installing Calling Trace Software Server Independently............................ 1-4
Figure 1-4 Calling Trace Software Server is Integrated Into EMS Server................... 1-5
Figure 1-5 The Calling Trace Software is Deployed at Local NE ............................... 1-7
Figure 1-6 Calling Trace Task Life Cycle ................................................................... 1-8
Figure 2-1 Modifying Processes................................................................................ 2-2
Figure 2-2 Select Language...................................................................................... 2-3
Figure 2-3 Select Installation Style ............................................................................ 2-3
Figure 2-4 Network scale .......................................................................................... 2-4
Figure 2-5 Select product.......................................................................................... 2-4
Figure 2-6 Database connection config ..................................................................... 2-5
Figure 2-7 UCA config in Database config ................................................................ 2-6
Figure 2-8 Database config....................................................................................... 2-6
Figure 2-9 Host information config ............................................................................ 2-7
Figure 2-10 System information detection ................................................................. 2-8
Figure 2-11 Unzip and Copy File............................................................................... 2-8
Figure 2-12 Confirm .................................................................................................. 2-9
Figure 2-13 Installation database .............................................................................. 2-9
Figure 2-14 Parameter Set...................................................................................... 2-10
Figure 2-15 Confirm ................................................................................................ 2-10
Figure 2-16 System Initialization ............................................................................. 2-11
Figure 2-17 Installation Finished ............................................................................. 2-11
Figure 2-18 Select language ................................................................................... 2-12
Figure 2-19 Select Installation Style ........................................................................ 2-13
Figure 2-20 Select product...................................................................................... 2-13
Figure 2-21 System information detection ............................................................... 2-14
Figure 2-22 Parameter Set...................................................................................... 2-15
Figure 2-23 Confirm ................................................................................................ 2-15
Figure 3-1 Network Manage Console Shortcut Icon .................................................. 3-2
Figure 3-2 Network Manage Console Startup Menu.................................................. 3-2
Figure 3-3 Starting Server Processes ....................................................................... 3-2
I
II
Figures
III
............................................................................................................ 3-60
IV
Tables
Table 1-1 Task Types ................................................................................................ 1-8
Table 2-1 Configuration File Table (1) of Port Offet.................................................. 2-16
Table 2-2 Configuration File Table (2) of Port Offet.................................................. 2-17
Table 3-1 Shortcut Introduction ................................................................................. 3-5
Table 3-2 Tool-bar Button Introduction..................................................................... 3-27
Tables
Glossary
3GPP
- 3rd Generation Partnership Project
ATM
- Asynchronous Transfer Mode
CN
- Core Network
CS
- Circuit Switched
EMS
- Electromagnetic Susceptibility
FTP
- File Transfer Protocol
GSM
- Global System for Mobile Communication
IP
- Internet Protocol
MBMS
- Multimedia Broadcast/Multicast Service
PS
- Packet Switched domain
RNC
- Radio Network Controller
RNL
- Radio Network Layer
TNL
- Transmission Network Layer
UE
- User Equipment
UMTS
- Universal Mobile Telecommunication System
UTRAN
- UMTS Terrestrial Radio Access Network
VII