SM ZXMBW AGW Performance Statistics Training Material

ZXMBW AGW
Performance Statistics and Analysis
Training Material
Version 3.08.10
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2006 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
Contents
Performance Management Concepts .................1

Description of Performance Management ........................... 1
Common Concepts.......................................................... 3
Performance Index and System Performance
Relationship ....................................................... 3
Performance Measurement Format Introduction .............. 3
Measurement Item ..................................................... 5
Measurement Object Type............................................ 5
Measurement Objects ................................................. 5
Measurement Types .................................................... 5
Counters ................................................................... 5
Collection Granularity .................................................. 6
Calculation Index........................................................ 6
QoS .......................................................................... 6
Performance Task Configuration Guide .............7

Overview of Creating and Running Performance Statistics
Task...................................................................... 7
Overview of Creating and Running Performance QoS
Task...................................................................... 9
Measurement Job Management .......................................10
Creating a Measurement Job .......................................10
Deleting a Measurement Job .......................................16
Handing up a Performance Measurement Job.................17
Activating a Performance Measurement Job...................18
Modifying a Measurement Job .....................................19
Exporting a Measurement Job Data ..............................21
Finding Measurement Job Data ....................................22
Calculation Index Management........................................23
Creating a Calculation Index .......................................23
Deleting a Calculation Index........................................28
Modifying a Calculation Index......................................29
Exporting Calculation Index ........................................31
Finding Calculation Index............................................31

Performance Threshold Management ................................32
Creating Performance QoS Job ....................................32
Deleting Performance QoS Job.....................................39
Handing Up Performance QoS Job ................................40
Activating Performance QoS Job ..................................41
Modifying Performance QoS Job...................................41
Exporting Performance QoS Job...................................42
Finding QoS Job ........................................................43
Performance Statistic Query............................................45
Querying Performance Data by Measurement Job
Condition..........................................................45
Customized Performance Data Query ...........................46
Exporting the Data Query Result..................................49
Saving the Query Condition to the Favorite ...................50
Maintenance of Performance Alarm Data ........ 53

Data Backup .................................................................53
Backing up Performance Rule ......................................53
Backing up Performance Data......................................54
Backing up Periodic Task.............................................55
Backing up Alarm Rule Data ........................................56
Backing up History Alarm Data ....................................56
Backing up History Notification Data.............................57
Data Restore.................................................................58
Restoring Performance Data........................................58
Restoring Performance Rule ........................................59
Restoring Periodic Task ...............................................59
Restoring Alarm Rule Data ..........................................60
Restoring History Alarm Data ......................................60
Restoring History Notification Data...............................61
Data Deletion................................................................61
Deleting Performance Data .........................................61
Deleting History Alarm Data ........................................62
Deleting History Notification Data ................................63
Periodic Task Management ..............................................63
Adding a Task to Back up Performance Rule ..................63
Adding a Task to Back up Performance Data ..................64
Adding a Task to Back up Periodic Task .........................65
Adding a Task to Delete Performance Data ....................66
Adding a Task to Back up Alarm Rule............................67
Adding a Task to Back up Historical Alarm .....................67

Adding a Task to Back up Information ..........................68
Adding a Task to Delete History Alarm Data...................68
Adding a Task to Delete History Notification Data ...........69
Suspending Periodic Task............................................69
Activating Periodic Task ..............................................70
Stopping Periodic Task................................................70
Showing Periodic Task ................................................70
Performance Data Analysis ............................. 71

Introduction to Data Analysis ..........................................71
General Data Analysis ....................................................72
Comparative Analysis of Time..........................................72
Comparative Analysis of Modules .....................................73
Comprehensive Analysis of Performance Statistics and
Alarm Information .................................................73
Comprehensive Analysis of Performance Statistics and
Log Information ....................................................74
Performance Measurement Item

Reference ........................................................ 75
AGW Load Measurement.................................................75
Mean Ratio of the CPU Usage (%) ................................75
Peak Ratio of the CPU Usage(%)..................................75
Mean Ratio of the Memory Usage (%) ..........................76
Peak Ratio of the Memory Usage (%) ...........................76
Mean Ratio of the Hard Disk Usage(1/10000) ................76
Service Process Measurement .........................................76
Number of Successful Access ......................................76
Number of Unsuccessful Access Owing to BS Side ..........79
Number of Unsuccessful Access Owing to AAA
Server..............................................................81
Number of Unsuccessful Access Owing to HA .................81
Number of Unsuccessful Access Owing to DHCP
Server..............................................................82
Number of Unsuccessful Access Owing to AGW ..............82
Number of Exit Owing to Wireless Side .........................83
Number of Exit Owing to AGW .....................................84
Number of Exit Owing to HA........................................84
Number of Exit Owing to AAA Server ............................85
Number of Successful Handover with Service Flow .........85
R3R6 Interface User Packet Measurement .........................86
Mega-number of Data Packets Received from R6

Reference Point .................................................86
Mega-number of Data Packets Sent to R6 Reference
Point ................................................................86
Mega-bytes of Data Packets Received from R6
Reference Point .................................................87
Mega-bytes of Data Packets Sent to R6 Reference
Point ................................................................87
Mega-number of Data Packets Received from R3
Reference Point .................................................88
Mega-number of Data Packets Sent to R3 Reference
Point ................................................................89
Mega-bytes of Data Packets Received from R3
Reference Point .................................................89
Mega-bytes of Data Packets Sent to R3 Reference
Point ................................................................90
AGW Context Resource Measurement ...............................90
Number of Occupied MS Contexts in AGW
(Authenticator) .................................................90
Total Number of MS Contexts in AGW (Authenticator) .................................................................91
Number of Occupied Service Flows in AGW (DPF)...........91
Total Number of Service Flows in AGW (DPF).................92
Number of Occupied MS Contexts in AGW (PC) ..............92
Total Number of MS Contexts in AGW (PC) ....................93
Number of Occupied EVL Contexts in FA .......................93
Total Number of EVL Contexts in FA .............................94
IP Pool Alloc Measurement for Every IP Pool ......................94
Number of Occupied IP Addresses by the IP Pool ...........94
Total Number of IP Addresses by the IP pool .................95
KPI Measurement ..........................................................95
Ratio of Successful Access (%) ....................................95
List of Glossary................................................ 97
Chapter
Performance
Management Concepts
Table of Contents:
Description of Performance Management ............................... 1
Common Concepts.............................................................. 3
Description of Performance
Management
Description
Function
The performance management manages the performance of the

mobile network. Through monitoring the network running status,
the performance management ensures that the network is running
effectively, steadily and safely. Through collecting and analyzing
the data of the network equipment, it provides the network administrator with plentiful and complete running data, so that the
network administrator can make a proper running policy according
to the network running status in order to ensure that the network
runs effectively.
The performance management performs the following functions:
Measurement job management
Service quality monitoring
Performance analysis
Report system
The implementation of the performance management is mainly

driven by the measurement job.
The completion of a detailed
measurement job defines some data collection modes, storage and
transmission methods, and the displayed contents and processing
methods of the final performance data.
Principle
The operator can create the performance statistic task, set the
start time at the network management client, and collect the data
from the foreground through the OMM server. The performance
data collected by the system are stored in the OMM server. The
operator can query the measurement result from the OMM server
through the query conditions set in the network management
client.
Create the performance statistics job
Confidential and Proprietary Information of ZTE CORPORATION
ZXMBW AGW Training Material
As shown in Figure 1, first, the operator should input the job

information about the performance statistic at the client. Then,
the management module of the client sends the job creation
message to the corresponding server according to the location
information of the performance statistic job created. After receiving the job creation message from the client, the server
judges the validity. After the judgment, it is required to enter
the job data to the database and save it. At the same time,
the server merges the tasks and create the corresponding relationship with the foreground network element. At last, the
system generates a successful message.
FIGURE 1 PERFORMANCE STATISTICS JOB CREATION
Modify the performance statistics job

The user can modify the status information of the task on the
interface of the client. The client synchronizes the information
to the server. The server queries the whole information of the
related task and then modify the table of the database.
Delete the performance statistics job

When it is required to delete the task, the user performs the
deletion operation on the interface of the client. The client
Chapter 1 Performance Management Concepts
sends the deletion information of the task to be deleted to

the server. After receiving the deletion information, the server
queries the whole information of the task to be deleted from
the database, and then delete the job. After that, the system
generates the successful deletion message.
Query the performance statistics job

The user selects the query condition from the operation interface of the client, and then the client updates the query command to the server. Then the server directly queries all the job
information meeting the query condition from the database and
return the information to the client. The client updates the job
display interface according to the query result returned.
Common Concepts
Performance Index and System
Performance Relationship
Description
Performance index is the data reflecting system operation status, and it reflects the performance of a module within a period
in ZXMBW AGW foreground. System status can be known through
measuring its performance. Periodical test on performance index
is required to carry out to know system operation status, figure
out and resolve faults by using performance measurement data.
System performance reflects system operation status, and performance measurement can measure system performance index, so
as to analyze network operation status and provide basis and verification methods for network optimization.
Relationship
Performance measurement functional module of OMC is used

to calculate and analyze performance index of the foreground.
The contents calculated by performance measurement functional
module include foreground service performance, operation performance of ZXMBW AGW boards.
Performance measurement provides performance index data,
which can be analyzed to obtain system operation status.
Performance Measurement Format

Introduction
Description
Format of each performance measurement item in this manual is

the same, which includes the following contents.
Name
Description
Measurement Triggering Point
Name
Description
Measurement
Triggering Point
Accumulation
Method
Collection Method
Accumulation Method
Collection Method
It means the name of performance measurement items, which is

the same as shown in OMC performance management interface.
It is the explanation to performance index.
It describes the triggering and accumulation process for performance measurement items.
It includes the following accumulation methods.
Accumulate by module M (Max/Min/Sum/Average/Latest), and

module means the module number or subunit of the CPU.
Accumulate by time T (Max/Min/Sum/Average/Latest).
Accumulate by object O (Max/Min/Sum/Average/Latest).
Whether to measure repeated signaling number and flow. RT

means to retransmit the measurement, RF means the method
of retransmitting but not to measure or not retransmitting.
Collection method for performance measurement items are as

shown in Table 1.
TABLE 1 COLLECTION METHOD
Value
CC
Name
Collect and
Count
Description
There is a running counter in the measured NE,
used to carry out calculation counting. At the
beginning of every collection period, the counter
is reset to a predefined value (usually as 0),
and the value of the counter when the collection
period ends is the valid collection result.
Gauge means the dynamic variables changed
Gauge
DER
Gauge
Discrete
Event Regis
tration
SI
Status Insp
ection
bidirectionally (means can be increased or decr

eased), the type of these variables is integer or
solid pattern. The variable value read when coll
ection period ends is the valid collection result.
It is a kind of measurement method on a group

of events corresponding to the measured attri
butes. The N times appearance of a specified
event in this group of events is used as trigge
ring point for driving measurement process to
generate measurement value. The value of N
depends on the frequency of the appearance
of specified event. The measurement value
is reset when every collection period begins.
When the collection period ends, a valid collect
ion result is obtained as per the corresponding
measurement value.
There are some internal counters in the measu
rement NE, and these counters are read as per
preset sampling frequency continuously. Measu
rement value of Status Inspection is reset when
every collection period begins. When a collect
ion period ends, a valid collection result is obta
ined according to all the sampled value in this
period.
Chapter 1 Performance Management Concepts
Measurement Item
Description
Measurement Item is a set of attributes associated with the same

collection of objects. AGW measurement system is divided into
the following type of information::
AGW IP PooL
AGW Network Element
Measurement Object Type

Introduction
A measurement type is categorization of a collection of related

objects with the same attribute, such as the object type of the
signaling link and the IMSI code. It also includes the type of the
network element.
Measurement Objects
Introduction
The measurement object can be defined as the physical entity or

logical entity and their combination to be measured, such as the
whole exchange, a signaling network element and a link.
Measurement Types
Introduction
The measure type is the basic unit of the measurement, which can
measure the different indices of the measurement objects. Different measurement objects have different measurement types. The
measurement types are selected according to the index that is required to be measured.
The NetNumen(TM) M30 AGW platform numbers the measurement
types under each Network Element (NE) uniformly which is convenient for the user to query.
Counters
Description
The counter is a measurement index in the measurement type,

and each measurement type has multiple measurement indices.
Relation Graph
Refer to for the relationship between the measurement type and

the counter.
FIGURE 2 RELATIONSHIP BETWEEN MEASUREMENT TYPE AND COUNTER
Collection Granularity
Description
The collection granularity refers to the cycle of collecting data from

the foreground board. The system can set the collection granularities as 5 minutes, 15 minutes and 1 hour.
Calculation Index
Description
The calculation index is used to evaluate the performance of the

equipment, which is obtained through performing the arithmetic
on measurement items. The system has preset some calculation
indices according to the common application.
QoS
Description
The Quality of Service (QoS) is a type of security mechanism of the

network, and it is also a technique that is used to solve the network
delay and blocking problems. When the network is overloaded or
congested, the QoS ensures that the important service traffic is
not delayed or discarded and that the network runs efficiently.
Chapter
Performance Task
Configuration Guide
Table of Contents:
Overview of Creating and Running Performance Statistics
Task ................................................................................. 7
Overview of Creating and Running Performance QoS Task ........ 9
Measurement Job Management ...........................................10
Calculation Index Management............................................23
Performance Threshold Management ....................................32
Performance Statistic Query................................................45
Overview of Creating and

Running Performance
Statistics Task
Introduction
The process of performing, creating, and running performance

measurement job is basically the same for all measurement items.
Figure 3 introduces the schematic flow of the performance measurement job operation.
FIGURE 3 PERFORMANCE STATISTICS OPERATION FLOW
Operation
Before commencing with the operation, ensure the following:
Connection between the foreground equipment and the background network management server is normal.
The user has logged in the ZTE network management client

successfully.
The performance measurement job has been created.
The performance data are in the performance database and

exchange office exists.
The user can customize the measurement items. Measurement

items include measurement object and regular object.
Creating performance measurement job: To define this measurement object, the personal needs to conform to certain level of
granularity and rules. Refer to Creating a Measurement Job.
Chapter 2 Performance Task Configuration Guide
The performance measurement job newly created need to be in

active state. Only after certain amount of time can information be
collected about the job. Change the state of performance measurement job depending on need. Refer to Activating a Performance Measurement Job.
Operations related to performance measurement include querying,
exporting performance data, and performance data management.
Overview of Creating and

Running Performance QoS
Task
Introduction
The operation of QoS task is basically the same for all measurement items.
Figure 4 introduces the operational flow of the performance QoS
task.
FIGURE 4 26 PERFORMANCE QOS OPERATION FLOW
Operation
Before commencing with the operation, ensure the following:
Connection between the foreground equipment and the background network management server is normal.

successfully.
The performance data are in the performance database and

exchange office exists.
Before the user creates performance QoS job the user may define
new calculation item as needed. Refer to Creating a Calculation
Index.
If the calculation result exceeds the preset threshold then the performance QoS log is generated and reported to alarm module. Refer to Creating Performance QoS Job.
The newly created performance QoS job has been activated status
and only after certain amount of time can information be collected
about the job. Refer to Activating Performance QoS Job.
Operations related to performance measurement include querying,
deleting, and exporting performance data, and performance data
management.
Measurement Job
Management
Creating a Measurement Job
Prerequisite
Context

successfully.
Data configuration of AGW is complete.
In order to collect the performance data of the AGW foreground

NEs, and send the collected performance data to the background
network management through the message, it is required to create the performance measurement job in the performance management.
For the measurement object types of AGW, refer to ZXMBW AGW
WiMAX Wireless Access Gateway Performance Measurement Item
Reference.
Steps
10
1. Click View > Performance Management on the unified network management client. Performance Management main
window appears as shown in Figure 5.
FIGURE 5 PERFORMANCE MANAGEMENT MAIN WINDOW
2. Following three methods can be used to create the measurement job.
Click Performance Management > Create Measurement Job menu.

From the main menu, click Performance Management
> Measurement Job (K), and then click
icon on the
toolbar.
Expand the Net Element View navigation tree, right-click
the AGW exchange or the type of the specific measurement
object, and then click Create Measurement Job from the
rightclick menu.
Measurement Job dialog box appears as shown in Figure 6.
11
FIGURE 6 MEASUREMENT JOB DIALOG BOX (GENERAL INFORMATION TAB)
For the parameter description, refer to Table 2.

TABLE 2 PARAMETER DESCRIPTION
TAB)
Parameter
OF
MEASUREMENT JOB DIALOG BOX (GENERAL INFORMATION
Meaning
Instruction
Name
Measurement job name
It is recommended that the name

reflect the measurement job and
it should be different from the
existing job name
Creator
The current subscriber by default
Status
Suspend or activate
The measurement job is invalid

when it is handed up
Beginning time
Refers to the beginning time of the
Ending time
Refers to the end time of

measurement job
12
measurement job
The beginning time should not be

set earlier than the system time of
the client; otherwise the beginning
time set will fail.
The end time should be later than
the beginning time
Parameter
Running cycle
Running time
section
Meaning
Instruction
Refers the duration of performing

the measurement job on validated
period. The running cycle has two
types: by date or by week
Click button to set the date

according to the week or the month.
Select the blank in the Action area,
and then click the data to deselect
the date
Perform the test in the running

period set, which can be one day or
one period of time in one day
Click button and select the

blank in the Action area frame. And
then click the data to deselect the
time
3. Set the general information of the measurement job in the

General Information section.
4. Click Next button or select Location Information tab. The
Location Information tabbed section appears as shown in
Figure 7.
FIGURE 7 MEASUREMENT JOB DIALOG BOX (LOCATION INFORMATION TAB)
5. Select AGW from the Net Element Type drop-down list, expand the AGW node, and then select AGW exchange to be measured as shown in Figure 8.
13
FIGURE 8 LOCATION INFORMATION SETTING
6. Click Next button or click Measurement Type Information

tab. The Measurement Type Information tabbed section
appears as shown in Figure 9.
14
FIGURE 9 MEASUREMENT JOB DIALOG BOX (MEASUREMENT TYPE INFORMATION TAB)
7. On the left pane, expand AGW Measurement node and select

the measurement type as shown in Figure 10.
15
FIGURE 10 SELECTED AGW MEASUREMENT TYPE
Note:
In the Net Element View navigation tree of the Performance
Management section, right-click the measurement type under the exchange and select View Measurement Type Information menu from the shortcut menu. The list of the counters
included in the measurement type is displayed.
8. Click OK button to finish the creation.

END OF STEPS.
Result
The measurement job created is displayed on the measurement

job list. The collection data is reported when the collection cycle
arrives.
Deleting a Measurement Job

Prerequisite
16

successfully.
Context
Steps
The performance measurement job has been accomplished .

For details, refer to Handing up a Performance Measurement
Job.
This topic explains the procedure to delete a measurement job.

Only the suspended job can be deleted.
1. Click Views > Performance Management on the unified network management client. Performance Management main
window appears.
2. From the main menu, click Performance management >
Measurement Job(K). Measurement Job tabbed section
appears on the right pane.
3. Select the network element from the Net Element View navigation tree. Corresponding measurement Jobs are displayed.
Note:
All the measurement jobs created previously are displayed on
the measurement Job list by default.
4. The following two methods can be used to delete the measurement job:
Right-click the measurement job to be deleted from the

Measurement Job list and select Delete Measurement
Job menu to delete the selected measurement job.
Select the measurement job to be deleted from the Measurement Job list and then click
icon on the toolbar.
5. Confirm Deleting dialog box appears, click Yes button on the

Confirm Deleting dialog box to delete the measurement job.
END OF STEPS.
Result
This operation deletes the measurement job from the database

directly.
Handing up a Performance
Measurement Job
Prerequisite
Context
Steps

successfully.
If it is necessary to stop collecting the foreground performance

data according to the rule of the job when the measurement task is
on the activated status, it is only required to suspend the measurement job. Only the activated measurement jobs can be handed up.
window appears.
17

Note:
4. The following two methods can be used to suspend the measurement job.
Right-click the activated measurements job from the Measurement Job list, and then click Suspend from the shortcut menu.
Select the activated measurement job from the Measurement Job list and click
button.
Note:
Click
button to toggle between activated and suspended
states of a measurement job.
END OF STEPS.
Result
The measurement job is in the suspended status. This operation

means that the job information is deleted from the foreground
network element, and the foreground network element does not
collect the performance data corresponding to the job, but the all
the information of the measurement job is still saved in the local
database.
Activating a Performance
Measurement Job
Prerequisite
18

successfully.
Context
If it is necessary to collect the foreground performance data according to the rule of the job when the measurement job is on the
suspended status, it is only required to activate the measurement
job. Only the suspended measurement job can be activated.
Steps
window appears.

Note:
4. The following two methods can be used to activate the measurement job.
Right-click the suspended measurements job from the

Measurement Job list, and then click Activate from the
shortcut menu.
Select the suspended measurement job from the Measurement Job list and click
button.
Note:
Click
states of a measurement job.
END OF STEPS.
Result
After the job is activated, the job information is synchronized to

the foreground network element. The foreground network element
converts the measurement job information to the corresponding
network element measurement job and then collects the performance data. The collected performance data is reported to the
local database and saved in the database throught the network
element.
Modifying a Measurement Job

Prerequisite

successfully.
The performance measurement job has been handed up.
Context
This topic explains the procedure to modify the measurement job

that has been created, including the name, ending time, running
cycle, running time section, and the collection object. But the
creator, status, location information and the measurement object
type can not be modified.
Steps
window appears.
19
2. From the main menu, click Performance Management >

Measurement Job (K). Measurement Job Management
tabbed section appears on the right pane.
3. Select the network element from the Net Element View navigation tree.
Note:
All the measurement jobs that have been created are displayed
in the Measurement Job Management list by default.
4. Double-click the measurement job to be modified. The Measurement Job dialog box appears as shown in Figure 11.
FIGURE 11 MODIFYING MEASUREMENT JOB

TAB)
Parame
ter
OF
MEASUREMENT JOB DIALOG BOX (GENERAL INFORMATION
Meaning
Instruction
Name
Measurement job name
It should indicate the measurement job

clearly and it should be different from
the existing job name
Creator
The current subscriber by default
20
Parame
ter
Meaning
Instruction
The measurement job is invalid when
it is handed up
Status
Suspend or activate
Beginning
Refers to the beginning time of the
time
measurement job
Ending
time
Refers to the end time of measurement

job
The end time should be later than the

beginning time
Refers to the duration of performing the

measurement job on validated period.
The running cycle has two types: by
date or by week

Select the blank in the Action area, and
then click the data to deselect the date
Perform the test in the running period

set, which can be one day or one period
of time in one day
Click button and select the blank

in the Action area frame. And then click
the data to deselect the time
Running
cycle
Running
time sect
ion
The beginning time should not be set

earlier than the system time of the
client; otherwise the beginning time set
will fail.
5. Modify required parameters.

6. Select Measurement Type Information tab to modify the
object collected.
7. Click OK button to save the modification information to the
database and update the measurement job list.
Note:
During the modification, the user can click Cancel button to
abort the modification procedure anytime.
END OF STEPS.
Result
Modification of measurement job is complete.
Exporting a Measurement Job Data

Prerequisite
Context
Steps

successfully.
The performance measurement job has been added.
This topic explains the procedure to export the measurement job

data. At present, the following four formats are supported: Excel,
PDF, HTML, and TTF.
window appears.
21
Note:
4. Select the measurement job. For selecting multiple measurement jobs, hold down Ctrl key and select the measurement
jobs.
5. The following two methods can be used to export the required
measurement job data.
Click
button on the toolbar.
Right-click on the selected Measurement Job list, and

then click Export menu.
6. Select the save path, file name, and file type in the Save dialog
box.
7. Click Save button to export the job list to the file.
END OF STEPS.
Result
Exporting of measurement job data is complete.
Finding Measurement Job Data

Prerequisite
Context
Steps
The connection between the foreground equipment and the

background network management server is normal.

successfully.
The performance measurement job has been added.
This topic explains the procedure to find the performance measurement job that has been created through the filter.
window appears.
22
Note:
4. The following two methods can be used to find the measurement job data.
Click
Right-click on the Measurement Job List and select Data

Query menu from the right-click menu.
appears in the left of the toolbar.
5. Input the filter text.

END OF STEPS.
Result
The performance data that corresponds to the measurement job

is displayed.
Calculation Index
Management
Creating a Calculation Index
Prerequisite
Context
Steps

successfully.
The data configuration of the exchange has been completed.
Before creating the performance QoS job, the subscriber can

customize the new calculation item in order to set the job alarm
threshold.
window appears.
2. Expand the Net Element View navigation tree, right-click on
detail object of the AGW exchange, and then click View Measurement Type Information menu as shown in Figure 12.
23
FIGURE 12 VIEW MEASUREMENT TYPE INFORMATION
All the calculation items that have been created are displayed
in the Calculation item list as shown in Figure 13.
24
FIGURE 13 LIST
OF
MEASUREMENT TYPE
3. Perform any of the following methods to open Calculation

Item dialog box as shown in Figure 14.
Click
button.
Right-click anywhere in right pane, and then click New

Create Calculation option from the right-click menu.
25
FIGURE 14 CALCULATION ITEM DIALOG BOX

TABLE 4 CALCULATION ITEM PARAMETERS
Parame
ters
Meanings
Remarks
Index
Name
The name of the new calculation

item
The name should be different from the

existing name
Formula
It is formulated according to the

arithmetic of the statistics item
The formula should not be a constant
Data Type
The system supports three types:

integer, float and percent
Select it according to the formula
Filter Text
Click button to filter out

nonessential index items on the
right pane
4. Input the name of the new calculation item in the Index Name
text box (it should be different with the existing index name).
5. Click the drop-down list of the Data Type, and then select data
type according to the formula.
26
Note:
The data type includes the Integer, Float, and Percent.
6. Edit the formula according to the counter and the operator.

7. Click OK button. The system judges if the formula is valid.
Note:
If the formula is invalid, an error prompt appears; if the formula is valid, the new calculation item is added to the list. During creating the calculation item, the user can click the Cancel
button to cancel the creation.
END OF STEPS.
Result
The calculation item to be created is displayed on the Calculation

item list as shown in Figure 15.
FIGURE 15 ADDED CALCULATION ITEM
Example
Table 5 describes the edit process of formula (C40616010C40616004)/C40616008*100 as an example.
27
TABLE 5 EDIT PROCESS

N
o.
Operation
Click ( on the key pad
On the right pane of the dialog box, click AGW Context

Resource Measurement > Number of occupied EVL
Contexts in FA
Click on the key pad.

Resource Measurement > Number of occupied MS Contexts
in AGW(Authenticator)
Click ) on the key pad.
Click / on the key pad.

Resource Measurement > Number of occupied MS Contexts
in AGW(PC)
Click * on the key pad.
Click 1 and then 00 on the key pad.
Deleting a Calculation Index

Prerequisite
Context
Steps

successfully.
The calculation item has been created.
The QoS job that uses this calculation item has been deleted.
This topic explains the procedure to delete the calculation item.

window appears.
2. Expand Net Element View navigation tree, right-click on detail object of the AGW exchange, and then click View Measurement Type Information menu as shown in Figure 12.
Note:
3. The following two methods can be used to delete the calculation

item:
Right-click the calculation item in the right list, and click

Delete calculation Item menu from the right-click menu.
Select the calculation item from the list and then click
button from the toolbar.
Confirm Deleting dialog box appears.
28
Note:
A deleted calculation item can not be recovered.
4. Click Yes for confirming deletion.

END OF STEPS.
Result
After the calculation item is deleted, all the information of the calculation item is deleted from the database.
Modifying a Calculation Index

Prerequisite
Context
Steps

successfully.
The calculation item has been added.
This topic explain the procedure to modify the calculation item that
has been created.
window appears.
2. Expand the Net Element View navigation tree, right-click on
detail object of the AGW exchange, and then click View Measurement Type Information menu as shown in Figure 12.
Note:
3. Double-click the calculation item to be modified. The Calculation Item dialog box appears as shown in Figure 16.
29
FIGURE 16 MODIFY CALCULATION ITEM DIALOG BOX
The network element object of the calculation item and its corresponding parameter that belong to the calculation item can
be modified. For the parameter description, refer to Table 6.
TABLE 6 CALCULATION ITEM PARAMETERS
Param
eters
Meanings
Remarks
Index
Name
The name of the new calculation

item
The name should be different from the existing

name
Formula
It is formulated according to the

arithmetic of the statistics item
The formula should not be a constant
Data
Type
The system supports three types:

integer, float and percent
Select it according to the formula
Filter
Text
Click button to filter out

nonessential index items on the
right pane
4. Click OK button to save the modification.

END OF STEPS.
Result
30
The information of the calculation item that is modified is displayed

on the Calculation Item list.
Exporting Calculation Index

Prerequisite

successfully.
Context
This topic describes the steps for exporting a calculation Item.

At present, the following four formats are supported: Excel, PDF,
HTML and TTF.
Steps
window appears.
Note:
in the Calculation Item list as shown in Figure 13.
3. The following two methods can be used to delete the calculation

item:
Click on the calculation item to be exported from the item

list on the right pane and then click
In the Calculation Item list, right-click the calculation
item to be exported, and then click Export from the pop-up
menu.
The Save dialog box appears.

box.
5. Click Save button to export the calculation item.
END OF STEPS.
Result
Exporting calculation item is successful.
Finding Calculation Index

Prerequisite

successfully.
Context
This topic describes the steps for finding a calculation item by filtering out other calculation item in the item list.
Steps
window appears.
31
Note:
in the Calculation Item list as shown in Figure 13.
3. The following two methods can be used to find the calculation

index.
Click
Right-click on the Measurement Type list and click Measurement Type menu from the right-click menu.
appears in the left of the toolbar.
4. Input search text for the calculation item.
Note:
The item list narrows down to the required calculation index
depending on the search string entered.
END OF STEPS.
Result
Calculation index search is complete.
Performance Threshold
Management
Creating Performance QoS Job
Prerequisite
32

successfully.
The calculation item has been created according to the requirements. For the details, refer to Creating a Calculation Index.
Context
The performance QoS job is used to monitor the AGW measurement data with the preset duration. When the calculated index is
larger or lower than the designated threshold, the system generates an alarm.
Steps
window appears.
2. Following three methods can be used to create the performance QoS job.
Click Performance Management > Create Perforamce

Threshold menu.
From the main menu, click Performance Management
> Performance Threshold, and then click
icon on the
toolbar.
Expand Net Element View navigation tree, right-click the
AGW exchange or the type of the specific measurement
object, and then click Create Performance Threshold
from the right-click menu.
Performance Threshold dialog box appears as shown in Figure 17.

FIGURE 17 PERFORMANCE THRESHOLD DIALOG BOX (GENERAL INFORMATION TAB)

INFORMATION TAB)
Parame
ter
OF
PERFORMANCE THRESHOLD DIALOG BOX (GENERAL
Meaning
Instruction
Name
QoS job name
It is recommended that the name

reflects the QoS job and it should be
different with the existing name
Creator
The current user
33
Parame
ter
Meaning
Instruction
The QoS job is invalid when it is handed
up
Status
Inactive or inactive
Beginning
It refers to the beginning time of the
time
QoS job
Ending
time
It refers to the end time of QoS job
The end time should be later than the

beginning time
It refers to the duration of performing

the QoS job on validated period. The
running cycle has two types: by date
or by week

Select the blank in the Action area,
and then click the date to deselect the
date
Perform the test in the running period

set, which can be one day or one period
of time in one day
Click button and select the blank

in the Action area frame. And then
click the data to deselect the time
Running
cycle
Running
time sect
ion
The beginning time should not be set

earlier than the system time of the
client; otherwise the beginning time
set will fail.
Note:
If the foreground is not synchronized, the status of created job
must read as Inactive. The system may report errors if it is
in Active state.
3. Set the general information of the measurement job in the

General Information section.
4. Click Next button or select Location Information tab. The
Location Information tabbed section appears as shown in
Figure 18.
34
FIGURE 18 PERFORMANCE THRESHOLD DIALOG BOX (LOCATION INFORMATION TAB)
5. Select AGW from the Net Element Type drop-down list, expand the AGW node, and then select AGW exchange to be measured.
6. Click Next button or click Measurement Object Information
tab. The Measurement Object Information tabbed section
35
FIGURE 19 PERFORMANCE THRESHOLD DIALOG BOX (MEASUREMENT OBJECT INFORMATION TAB)
Note:
After selecting measurement type in the left pane, measurement object appears in the right pane.
7. On the left pane, select the measurement type; on the right

list, expand the Measurement Object node, and select the
collection object corresponding to the measurement type.
8. Click Next button or click Threshold Setting tab.
The
Threshold Setting tabbed section appears as shown in Figure
20.
36
FIGURE 20 PERFORMANCE THRESHOLD DIALOG BOX (THRESHOLD SETTING TAB)
9. Click Add button. The Threshold Editor dialog box appears

as shown in Figure 21.
FIGURE 21 THRESHOLD EDITOR DIALOG BOX
10. Click
button. The Select Counter dialog box appears as
shown in Figure 22.
37
FIGURE 22 SELECT COUNTER DIALOG BOX
11. Select the counter or calculation item.

12. Set 4 levels of alarm thresholds and the deltas on Threshold
Editor dialog box shown in Figure 21, and then click OK. Refer
to Table 8 for setting parameters in Threshold Editor dialog
box.
TABLE 8 ALARM PARAMETER SETTING
Parameter
38
Meaning
Instruction
Upper Alarm
The larger the threshold value is,

the more possible the alarm is
generated
Lower Alarm
The smaller the threshold value

is, the more possible the alarm
is generated
Parameter
Critical
value
Major value
Minor value
Warning
value
Meaning
When the performance index
exceeds the threshold, the
alarm is generated; when the
performance index is lower
than the threshold, the alarm
is recovered. When the Upper
Alarm option is selected, the
threshold order is Critical value
> Major value > Minor value >
Warning value
It is a lagged value set in order
to avoid when the QoS alarm
shakes frequently between alarm
and the alarm recovery status
Delta
Alarm sugg
est
Input the default alarm

processing suggestion to
give some prompts to the alarm
processor
Instruction
The unit of the

alarm threshold
is related to
the unit of the
measurement
index
It is recommen
ded to set the
delta. Input 0 if
there is no delta
-
13. Click Commit button to add a performance threshold. The

Performance Threshold dialog box becomes active dialog
box.
14. Click OK button to finish the creation or Cancel button to abort
this creation.
END OF STEPS.
Result
The QoS job created is displayed on the Performance Threshold

list. If the monitoring value exceeds a threshold, the alarm of
the corresponding level is generated. After entering the Alarm
Management interface, the performance statistics alarm can be
checked in the corresponding office direction.
Deleting Performance QoS Job

Prerequisite
Context
Steps

successfully.
The performance QoS job has been created.
This topic explains the procedure to delete the QoS job that is
not used any more. The job can be deleted when it is under the
activated status.
window appears.
2. Click Performance Management > Performance Threshold or click
. The Performance Threshold tabbed section
appears.
3. The following two methods can be used to delete the performance QoS job:
Right-click the performance QoS job to be deleted from

the Performance QoS Job list and select Delete Perfor-
39
mance QoS Job menu to delete the selected measurement

job.
Select the performance QoS job to be deleted from the

Performance QoS Job list and then click
icon on the
toolbar.
4. Confirm Deleting dialog box appears, click Yes button on the

Confirm Deleting dialog box to delete the performance QoS
job.
END OF STEPS.
Result
Deletion of a performance QoS job is complete.
Handing Up Performance QoS Job

Prerequisite
Context
Steps

successfully.
If it is required to stop triggering alarms according to the set

threshold of the measurement object when the QoS job is in the
activated status, it is only required to suspend the QoS job. This
operation is only done for the activated QoS task.
window appears.
appears.
3. The following two methods can be used to suspend the performance QoS job.
Right-click the activated measurements job from the Performance QoS Job list, and then click Suspend from the
shortcut menu.
Select the activated measurement job from the Performance QoS Job list and click
button.
Note:
Click
states of a performance QoS job.
END OF STEPS.
Result
40
The performance QoS job is on the suspended status. The suspended operation means the job is not be in the activated status
and does not perform the performance threshold calculation, but
the all the information of the QoS job is still saved in the local
database.
Activating Performance QoS Job

Prerequisite
Context
Steps

successfully.
The performance QoS job is in suspended state.
If it is required to collect the foreground performance data according to the rule of the job when the QoS job is on the suspended
status, it is required to activate this performance measurement
job. This operation is only done for the suspended QoS job.
window appears.
appears.
3. The following two methods can be used to activate the performance QoS job.
Right-click the suspended performance QoS job from the

Performance QoS Job list, and then click Activate from
the shortcut menu.
Select the suspended performance QoS job from the Performance QoS Job list and click
button.
Note:
Click
states of a performance QoS job.
END OF STEPS.
Result
Activation of suspended performance QoS job is complete.
Modifying Performance QoS Job

Prerequisite
Context
Steps

successfully.
The performance QoS job is created.
This topic describes the procedure to modify the QoS job that has
been created, including the name, ending time, running cycle running time section, collection object and threshold. But the creator,
status, location information and measurement object can not be
modified.
window appears.
41

appears.
3. Select the network element from the Net Element View navigation tree.
Note:
All the QoS jobs that have been created are displayed on the
Performance Threshold tabbed section.
4. Double-click the QoS job to be modified. The Performance

Threshold dialog box for the selected QoS job appears.
5. In the General Information page, modify the general information of the QoS job. For parameter description, refer to
Table 7.
6. Click Measurement Object Information tab to modify the
collection object.
7. Click Threshold Setting tab to modify alarm threshold of the
calculation item.
8. Click Commit command to save the modification.
9. Click OK button to save the modification information about QoS
job to the database and then update the QoS job list.
Note:
During the modification, the user can click Cancel button to
cancel the modification.
END OF STEPS.
Result
Modification of performance QoS job is complete.
Exporting Performance QoS Job

Prerequisite
Context
Steps

successfully.
This topic describes the steps for exporting the QoS job data. At
present, the following four formats are supported: Excel, PDF,
HTML, and TTF.
window appears.
appears.
42
3. Select the network element from the Net Element View navigation tree. Corresponding performance QoS Jobs are displayed.
Note:
All the performance QoS jobs created previously are displayed
on the performance QoS Job list by default.
4. Select the performance QoS job. For selecting multiple QoS

jobs, hold down Ctrl key and select the performance QoS jobs.
5. The following two methods can be used to export the performance QoS job data.
Click
Right-click on the selected Performance QoS Job list, and

then click Export menu.
box.
7. Click Save button to export the job list to the file.
END OF STEPS.
Result
Exporting performance QoS job is successful.
Finding QoS Job

Prerequisite
Context
Steps

successfully.
This topic describes the steps for finding a QoS job data by filtering
out other QoS job data.
window appears.
appears.
3. Select the network element from the Net Element View navigation tree. Corresponding performance QoS Jobs are displayed.
Note:
All the performance QoS jobs created previously are displayed
on the performance QoS Job list by default.
4. The following two filtering methods can be used.
43
Click
Right-click any of the items in the item list on the right

pane, and then click Find Performance Threshold from
the shortcut menu.
On the right side, a search field appears as shown in Figure 23.

FIGURE 23 SEARCH FIELD (PERFORMANCE QOS JOB)
5. Input search text for QoS job.

The item list narrows down to the required QoS job depending
on the search string entered.
END OF STEPS.
Result
44
Searching of performance QoS job is complete.
Performance Statistic Query

Querying Performance Data by
Measurement Job Condition
Prerequisite
Context
Steps


successfully.
The performance measurement job has been created. And the

performance data are in the performance database.
ZXMBW AGW system collects the performance data from the

foreground according to the customized measurement job and
then stores the performance data collected to the database of the
server.
window appears.
2. From the main menu, click Performance Management >
Note:
4. The following two methods can be used to query the data according to the measurement job condition.
Select the measurement job from the list and then click
button.
Right-click the measurement job from the list and then click
Query by Measurement Job Condition.
Query dialog box appears. Default tab is Location Information.

5. Select the location information of the network element from
the Net Element Type drop-down list box.
tab.
7. Click Next button or click Time Information tab.
45
8. Click OK button. The detailed query data is displayed on the

window.
END OF STEPS.
Result
The performance data that corresponds to the job condition is displayed on the Data window.
Customized Performance Data Query

Prerequisite
Context
Steps


successfully.

This topic describes how to query the performance data collected

by the measurement job according to the specified conditions.
window appears.
2. Expand the Net Element View navigation tree, right-click the
AGW exchange or the specific measurement objects, and then
click Data Query menu. The Query dialog box appears as
shown in Figure 24.
46
FIGURE 24 QUERY DIALOG BOX
3. In Location Information tab, select AGW for the Net Element Type and then select the location information.
tab. The Measurement Type Information tabbed section
47
FIGURE 25 QUERY DIALOG BOX (MEASUREMENT TYPE INFORMATION TAB)
5. Select the measurement type.

6. Click Next button or click Time Information tab. The Time
Information tabbed section appears as shown in Figure 26.
48
FIGURE 26 QUERY DIALOG BOX (TIME INFORMATION TAB)
7. Input parameters for time information and then click OK button. Data that meet the query condition is displayed.
END OF STEPS.
Result
The performance data that corresponds to the query condition is

displayed on the Data window. In the query result, the collection
granularity displays the corresponding second. For example, if the
granularity is 15 minutes, the display result is 900 seconds.
Exporting the Data Query Result

Prerequisite
Context


successfully.

This topic describes the steps for saving the performance statistics
data as a file format. At present, the following four formats are
supported: Excel, PDF, HTML and TTF.
49
Steps
1. Query the performance data according to the measurement job

condition or data query. The result is displayed on the Data
tab section.
2. The following two methods can be used to export the query
result:
Click
icon on the toolbar
In the data query list, right-click and click Export menu.
3. Select the save path, file name and file type in the Save dialog,
and click Save button. The query result is exported to the file.
END OF STEPS.
Result
Exporting of the data query result is complete.
Saving the Query Condition to the

Favorite
Prerequisite
Context
Steps


successfully.
Customized performance data query has been performed. Refer to Customized Performance Data Query.
This topic describes the procedure to save the query condition to

the system after the customization query in order to query the
data with the same query condition later.
1. Query the performance data. The query results are displayed
in the Data window.
2. Click
button on the toolbar. The Please Input Name dialog
box appears as shown in Figure 27.
FIGURE 27 PLEASE INPUT NAME DIALOG BOX
3. Enter Name and Description of the query condition. In general, select the default value.
4. Click OK button to save the query condition.
END OF STEPS.
50
Result
Click the Query Favorite tab on the navigation column of the

main window of the network management, and the saved query
condition is seen. For the second query, it is only required to double-click the query condition.
51
This page is intentionally blank.
52
Chapter
Maintenance of
Performance Alarm
Data
Table of Contents:
Data Backup .....................................................................53
Data Restore.....................................................................58
Data Deletion....................................................................61
Periodic Task Management ..................................................63
Data Backup
Backing up Performance Rule
Prerequisite
Context
Enter the MML command terminal.
Perform this operation to backup performance rule. The backup of

performance rule includes measurement task, performance QoS
task, and customized KPI item.
For restoration of performance rule, refer to Restoring Performance
Rule.
Enter the commandBAKPMRULE:FILENAME=FILENAME,FILEPATH
=FILEPATH,SRCNEID=SRCNEID;.
To backup the performance rule of network element 1 and to save
the backup file to C drive on the server and if the file name is
20071201 the command is the following.
BAKPMRULE:FILENAME=20071201,FILEPATH=c:,SRCNEID=1;
Parame
ter
FILEN
AME
Description
File name of
backup file.
Remark
Mandatory parameter.
53
Parame
ter
FILEPATH
SRCNEID
Result
Description
Backup path
Backup
network
element ID
Remark
Mandatory parameter. Path of the file is
needed to be entered to save the file to a
specified location on the server.
Mandatory parameter. The ID of the
network element the backup data belongs
to.
Backup of performance rule is successful and the file is saved in

zip file format.
Backing up Performance Data

Prerequisite
Context
The ID of the exchange office exists.
Perform this operation to backup performance data in the background database.

For restoration of performance data, refer to Restoring Performance Data.
Enter the commandBAKPMDATA:FILENAME=FILENAME,FILEPAT
H=FILEPATH,SRCNEID=SRCNEID,MEASUREGR=MEASUREGR,STYLE
=STYLE,TIME1=TIME1,TIME2=TIME2,PMTYPEID=PMTYPEID,ISCLE
AN=ISCLEAN;.
To backup the performance data of network element 1 between
2007-12-01 10 39 33 and 2007-12-02 10 39 33 and if the backup
granularity is 1 hour and path points to C driver then and if the file
name is 20071201, the command is following. (ISCLEAN=Y will
delete the data from the server)
BAKPMDATA:FILENAME=20071201,FILEPATH=c:,SRCNEID=1,MEAS
UREGR=HOUR,STYLE=BETWEEN,TIME1=20071201
10:39:33,TIME2
=2007120210:39:33,PMTYPEID=ALL,ISCLEAN=N;

Parame
ter
Description
Remark
FILENAME
File name of backup

file.
FILEPATH
Backup path
Mandatory parameter. Path of the file is needed to be

entered to save the file to a specified location on the
server.
SRCNEID
Backup network
element ID
Mandatory parameter. The ID of the network element

the backup data belongs to.
MEASUR
Type of the backup
Mandatory parameter. This refers to the type of the
EGR
data table
54
backup table. Four measurement granularities can be

chosen; 5 minutes, 15 minutes, 1 hour, or 1 day.
Chapter 3 Maintenance of Performance Alarm Data
Parame
ter
Description
Remark
STYLE
Backup style
Mandatory parameter. Chose between and before. If

between is chosen, specify beginning time and end time.
If before is chosen, specify beginning time. The command
goes into effect immediately.
TIME1
Beginning time
TIME2
Ending time
PMTYPEID
Measurement type
Mandatory parameter. Select the type data of the

measurement to be measured. The default value is ALL.
ISCLEAN
Use this command to

clear data from the
server.
Mandatory parameter. Option to delete the original data

in the database after it has been backed up.
Note:
When choosing backup style if before option has been chosen and
if data clearance is required then by system default granularity
for deletion is 1 day. The data is deleted after one day. If before
option has been chosen and if data clearance is not required then
by system default granularity for backup is every 3 days.
Result
Backup of performance data is successful and the file is saved in

zip file format.
Backing up Periodic Task

Prerequisite
Context
Perform this operation to backup periodic tasks in the background

database. Refer to Periodic Task Management.
For restoration of periodic task, refer to Restoring Periodic Task.
Enter the commandBAKCYCLETASK:FILENAME=FILENAME,FILEP
ATH=FILEPATH;.
To backup all periodic tasks to C drive on the server and if the file
name is 20071201 the command is following.
BAKCYCLETASK:FILENAME=20071201,FILEPATH=c:;

Param
eter
Description
Remark
FILEN
AME
File name of
backup file.
FILEP
ATH
Backup path
Mandatory parameter. Path of the file is needed to be entered

to save the file to a specified location on the server.
55
Result
Backup of periodic task is successful and the file is saved in zip file
format.
Backing up Alarm Rule Data

Prerequisite
Context
Perform this operation to backup data of alarm rule in the background database. .
For restoration of alarm rule data, refer to Restoring Alarm Rule
Data.
Enter the commandBAKFMRULE:FILENAME=FILENAME,FILEPATH
=FILEPATH;.
To backup all alarm rule data to C drive on the server and if the
file name is 20071201 the command is following.
BAKFMRULE:FILENAME=20071201,FILEPATH=c:;

Param
eter
Description
Remark
FILEN
AME
File name of
backup file.
FILEP
ATH
Backup path
Mandatory parameter. Path of the file is needed to be entered to

save the file to a specified location on the server.
Result
Backup of alarm rule data is successful and the file is saved in zip
file format.
Backing up History Alarm Data

Prerequisite
Context

This topic describes how to back up the history alarm data related
to the performance.
For restoration of historic alarm data, refer to Restoring History
Alarm Data.
Enter the commandBAKALARM:FILENAME=FILENAME,FILEPATH
=FILEPATH,STYLE=STYLE,TIME1=TIME1,TIME2=TIME2,SEVERITY
=SEVERITY,ISCLEAN=ISCLEAN;.
To backup historic alarm data with severity as CRITICAL (there are
4 severity levels WARNING, MAJOR, MINOR, and CRITICAL) between 2007-12-01 10:02:55 and 2007-12-02 10:02:55 and path
points to C driver then and if the file name is 20071201 the command is the following. (ISCLEAN=Y will delete the data from the
server)
56
BAKALARM:FILENAME=20071201,FILEPATH=c:,STYLE=BETWEEN,TI
ME1=2007120110:02:55,TIME2=2007120210:02:55,SEVERITY=CRITI
CAL,ISCLEAN=N;
Param
eter
Description
Remark
FILEN
AME
File name of backup

file.
FILEP
ATH
Backup path
Mandatory parameter. Path of the file is needed to be

entered to save the file to a specified location on the server.
STYLE
Backup style
between is chosen, specify beginning time and end time.

If before is chosen, specify beginning time. The command
goes into effect immediately.
TIME1
Beginning time
TIME2
Ending time
SEVER
ITY
Alarm level
Mandatory parameter. There are 4 severity levels, WARNING,

MAJOR, MINOR, and CRITICAL.
ISCLEAN
Use this command

to clear data from
the server.
Mandatory parameter. Option to delete the original data in

the database after it has been backed up.
Result
Backup of historic alarm data is successful and the file is saved in

zip file format.
Backing up History Notification Data

Prerequisite
Context
Perform this operation to backup historic notification data in the

background database.
For restoration of historic notification data, refer to Restoring History Notification Data.
Enter the commandBAKINFORM:FILENAME=FILENAME,FILEPAT
H=FILEPATH,STYLE=STYLE,TIME1=TIME1,TIME2=TIME2,ISCLEAN
=ISCLEAN;.
To backup historic notification data to C drive on the server between the time frame of 2007-12-01 10:02:55 and 2007-12-02
10:02:55 and if the file name is 20071201 the command is following.
BAKINFORM:FILENAME=20071201,FILEPATH=c:,STYLE=BETWEEN,T
IME1=2007120110:02:55,TIME2=2007120210:02:55,ISCLEAN=N;
57

Parame
ter
Description
Remark
FILEN
AME
File name of
backup file.
FILEPATH
Backup path
Mandatory parameter. Path of the file is needed to be entered
STYLE
Backup style
Mandatory parameter. Chose between and before. If between

is chosen, specify beginning time and end time. If before is
chosen, specify beginning time. The command goes into effect
immediately.
TIME1
Beginning time
TIME2
Ending time
ISCLEAN
Use this
command to
clear data from
the server.
Result
to save the file to a specified location on the server.
Mandatory parameter. Option to delete the original data in the

database after it has been backed up.
Backup of historic notification data is successful and the file is

saved in zip file format.
Data Restore
Restoring Performance Data
Prerequisite
Context
Performance data has been backed up. Refer to Backing up

Performance Data.
Perform this operation to restore performance data to the background database.

Enter the commandRESTOREPMDATA:FILENAME=FILENAME,FILE
PATH=FILEPATH,SRCNEID=SRCNEID,OVERWRITE=OVERWRITE;.
To restore performance data of network element 1 and to save
20071201. Also, overwriting of existing data table is not required
then the command is following.
RESTOREPMDATA:FILENAME=20071201,FILEPATH=c:,SRCNEID=1,OV
ERWRITE=N;
58

Parameter
Description
Remark
FILENAME
File name of
backup file.
FILEPATH
Backup path
Mandatory parameter. Path of the file saved at a specified

location on the server.
SRCNEID
Backup network
element ID
Mandatory parameter. The ID of the network element the

backup data belongs to.
OVERWRITE
Overwrite file
Mandatory parameter. Choose Y to overwrite the existing

data table and N to not to overwrite.
Result
Postrequisite
Restoration of performance data is complete.

Restart the server.
Restoring Performance Rule

Prerequisite
Context
Performance rule has been backed up. Refer to Backing up

Performance Rule.
Perform this operation to restore performance rules already

backed up including measurement task, performance QoS task,
and user-defined KPI items.
Enter the commandRESTOREPMRULE:FILENAME=FILENAME,FILE
PATH=FILEPATH,SRCNEID=SRCNEID,TARNEID=TARNEID;.
To restore performance rules of network element 1 and to save
20071201, then the command is following.
RESTOREPMRULE:FILENAME=20071201,FILEPATH=c:,SRCNEID=1,TA
RNEID=2;
Result
Postrequisite
Restoration of performance rules is complete.

Restart the server.
Restoring Periodic Task

Prerequisite
Context
Periodic task has been baked up. Refer to Backing up Periodic

Task.
Perform this operation to restore periodic task.

Enter the commandRESTORECYCLETASK:FILENAME=FILENAME,F
ILEPATH=FILEPATH;.
59
To restore all the periodic tasks in the backup file of which the name
is 20071201 under the directory c. The command is as follows:
RESTORECYCLETASK:FILENAME=20071201,FILEPATH=c:;
Result
Postrequisite
Restoration of periodic task is complete.

Restart the server.
Restoring Alarm Rule Data

Prerequisite
Context
Alarm rule data has been backed up. Refer to Backing up Alarm
Rule Data.
Perform this operation to restore alarm rule data.

Enter the commandRESTOREFMRULE:FILENAME=FILENAME,FILE
PATH=FILEPATH;.
To restore all alarm rule data in the database alarm table of the
backup file (20071201) under the directory c. The command is as
follows:
RESTOREFMRULE:FILENAME=20071201,FILEPATH=c:;
Result
Postrequisite
Restoration of alarm rule data is complete.

Restart the sever.
Restoring History Alarm Data

Prerequisite
Context
Historic alarm data has been backed up. Refer to Backing up

History Alarm Data.
Perform this operation to restore historic alarm data.

Enter the commandRESTOREALARM:FILENAME=FILENAME,FILEP
ATH=FILEPATH,OVERWRITE=OVERWRITE;.
To restore all historical alarm data in the database alarm table of
the backup file (20071201) under the directory c. The command
is as follows:
RESTOREALARM:FILENAME=20071201,FILEPATH=c:OVERWRITE=N;
Result
60
Restoration of historic alarm data is complete.
Postrequisite
Restart the server.
Restoring History Notification Data

Prerequisite
Context
Historic notification data has been backed up. Refer to Backing

up History Notification Data.
Perform this operation to restore historic notification data.

Enter the commandRESTOREINFORM:FILENAME=FILENAME,FILE
PATH=FILEPATH,OVERWRITE=OVERWRITE;.
To restore all alarm rule data in the database alarm table of the
backup file (20071201) under the directory c. The command is as
follows:
RESTOREINFORM:FILENAME=20071201,FILEPATH=c:,OVERWRITE
=N;
Result
Postrequisite
Restoration of historic notification data is complete.

Restart the sever.
Data Deletion
Deleting Performance Data
Prerequisite
Context
Perform this operation to delete performance data in the background database

Enter the commandDELPMDATA:SRCNEID=SRCNEID,MEASUREGR
=MEASUREGR,STYLE=STYLE,Time1=Time1,Time2=Time2,PMTYPEID
=PMTYPEID;.
To delete performance data of network element 1 between 200802-03 11:12:40 and 2008-02-04 11:12:40 and if the file name is
20071201, then command is as follows. (Deletion style chosen is
1).
DELPMDATA:SRCNEID=1,MEASUREGR=HOUR,STYLE=BETWEEN,Tim
e1=2008020311:12:40,Time2=2008020411:12:40,PMTYPEID=ALL;
61

Parame
ter
Description
Remark
SRCNEID
Backup network element

ID to be deleted.
MEASUR
Type of the backup data
EGR
table.
STYLE
Backup style
Mandatory parameter. Chose between and before.

If BETWEEN is chosen, specify beginning time and
end time. If BEFORE is chosen, specify beginning
time. The command goes into effect immediately.
TIME1
Beginning time
TIME2
Ending time
PMTYPEID
Measurement type

measurement to be measured. The default value
is ALL
Result
Mandatory parameter. The ID of the network

element the backup data belongs to.
Mandatory parameter. This refers to the type of
the backup table. Four measurement granularities
can be chosen; 5 minutes, 15 minutes, 1 hour, and
1 day.
Deleting of performance data is complete.
Deleting History Alarm Data

Prerequisite
Context
Perform this operation to delete historic alarm data in the background database.
Enter the commandDELALARM:STYLE=STYLE,Time1=Time1,Time2
=Time2,SEVERITY=SEVERITY;.
To delete historic alarm data with severity as WARNING and MINOR
(there are 4 severity levels, WARNING MAJOR, MINOR, and CRITICAL) between 2007-12-01 11:41:05 and 2007-12-02 11:41:05
and if the file name is 20071201, the command is as follows:
DELALARM:STYLE=BETWEEN,Time1=20071201
=2007120211:41:05,SEVERITY="MINOR"&"WARNING";
11:41:05,Time2

Parame
ter
Description
Remark
SRCNEID
Backup network
element ID to be
deleted.

the backup data belongs to.
MEASUR
EGR
Type of the backup

data table.
Mandatory parameter. This refers to the type of the

backup table. Four measurement granularities can be
chosen; 5 minutes, 15 minutes, 1 hour, and 1 day.
62
Parame
ter
Description
Remark
STYLE
Backup style

BETWEEN is chosen, specify beginning time and end
time. If BEFORE is chosen, specify beginning time. The
command goes into effect immediately.
TIME1
Beginning time
TIME2
Ending time
PMTYP
EID
Measurement type

measurement to be measured. The default value is ALL
Result
Deleting of historic alarm data is complete.
Deleting History Notification Data

Prerequisite
Context
Perform this operation to delete historic notification data in the

background database.
Enter the commandDELINFORM:Time1=Time1,Time2=Time2;.
To delete historic notification data between 2007-12-01 11:41:05
and 2007-12-02 11:41:05, the command is as follows:
DELINFORM:Time1=2007120111:41:05,Time2=2007120211:41:05;
Result
Deleting of historic notification data is complete.
Periodic Task Management

Adding a Task to Back up
Performance Rule
Prerequisite
Context
Perform this operation to add new task for performance rule

backup including measurement task, performance QoS task, and
user-defined KPI item.
To add new task for performance rule backup, enter the command:ADDBAK_PM_RULE_TASK:TASKNAME=TASKNAME,FILEPATH
=FILEPATH,SRCNEID=SRCNEID,PERIODTYPE=PERIODTYPE,PERIOD
NUM=PERIODNUM,STARTTIME=STARTTIME,FILENAME=FILENAME;.
63
To add new task for backing up periodic performance rule for network element 1 named TASK1 with the backup file saved to the C
drive every day, then the command is as follow:
ADDBAK_PM_RULE_TASK:TASKNAME=TASK1,FILEPATH=C:,SRCNEID
=1,PERIODTYPE=DAY,PERIODNUM=1;
Parame
ter
Description
Remark
TASKN
AME
Name of the task.
Mandatory parameter. Unique identity of the task.
FILEPATH
Backup path.
Mandatory parameter. Storage path of backup file
SRCNEID
Network element ID.

that the data belongs to.
PERIODT
YPE
Backup frequency.
Mandatory parameter. A total of 4 frequency can be

chosen; hour, week, and month
PERIOD
NUM
Number of frequency
present.
Mandatory parameter. The total number of frequency

present.
STARTT
IME
Start time
Mandatory parameter. Starting time of task execution
FILENAME
Backup file name.
Mandatory parameter. File name.
Result
Addition of new task for performance rule backup is complete.
Adding a Task to Back up

Performance Data
Prerequisite
Context
Perform this operation to add new task for performance data

backup.
To add new task for performance data backup, enter the command:ADDBAK_PM_DATA_TASK:TASKNAME=TASKNAME,FILEPATH
=FILEPATH,SRCNEID=SRCNEID,PMDATATYPE=PMDATATYPE,STYL
E=STYLE,PERIODTYPE=PERIODTYPE,PERIODNUM=PERIODNUM,I
SCLEAN=ISCLEAN,DAYBEFORE=DAYBEFORE,STARTTIME=START
TIME,FILENAME=FILENAME;.
To add new task for performance data backup for network element
1 named TASK1 with the backup file saved to the C drive every day
and with data table type being HOUR_DATA, then the command is
as follow:
ADDBAK_PM_DATA_TASK:TASKNAME=TASK1,FILEPATH=C:,SRCNE
ID=1,PMDATATYPE=HOUR_DATA,STYLE=INTRADAY,PERIODTYPE
=DAY,PERIODNUM=1,ISCLEAN=N,DAYBEFORE=90;
64

Parame
ter
Description
Remark
TASKNAME
Name of the task.
FILEPATH
Backup path.
SRCNEID
Network element ID.

PMDATAT
YPE
Data table type
STYLE
Backup style

between is chosen, specify beginning time and end
time. If before is chosen, specify beginning time. The
PERIODT
YPE
Backup frequency.

PERIOD
NUM
Number of frequency
present.

present.
ISCLEAN
Use this command to

clear data from the
server.
Mandatory parameter. Option to delete the original

data in the database after it has been backed up.
DAYBEF
ORE
Time duration for data

to be backed up.
Mandatory parameter. The range is 1-800. The default

value is 90.
STARTT
IME
Start time
FILENAME
Backup file name.
Result
Addition of new task for performance data backup is complete.
Adding a Task to Back up Periodic

Task
Prerequisite
Context
Perform this operation to add new task for periodic data backup.
To add new task for periodic data backup, enter the command:ADDCYCLE_BAK_TASK:TASKNAME=TASKNAME,FILEPAT
H=FILEPATH,PERIODTYPE=PERIODTYPE,PERIODNUM=PERIOD
NUM,STARTTIME=STARTTIME,FILENAME=FILENAME;.
To add new task for periodic data backup for network element 1
named TASK1 with the backup file saved to the C drive every day
and with data table type being HOUR_DATA , then the command
is as follow:
ADDCYCLE_BAK_TASK:TASKNAME=TASK1,FILEPATH=C:,PERIODTYP
E=DAY,PERIODNUM=1;
65

Parame
ter
Description
Remark
TASKN
AME
Name of the task.
FILEPATH
Backup path.
PERIODT
YPE
Backup frequency.

PERIOD
NUM
Number of frequency
present.

present.
STARTT
IME
Start time
FILENAME
Backup file name.
Result
Addition of new task for periodic data backup is complete.
Adding a Task to Delete Performance

Data
Prerequisite
Context
Perform this operation to add new task for deleting performance

data.
To add new task for deleting performance data, enter the command:ADDREMOVE_PM_DATA_TASK:TASKNAME=TASKNAME,SRCN
EID=SRCNEID,PMDATATYPE=PMDATATYPE,PERIODTYPE=PERIOD
TYPE,PERIODNUM=PERIODNUM,STYLE=STYLE,STARTTIME=START
TIME,DAYBEFORE=DAYBEFORE;.
To add new task for deleting performance data for network element
1 named TASK1 with the backup file saved to the C drive every day
and with data table type being HOUR_DATA, then the command is
as follow. (Time duration for data to be backed up is 90)
ADDREMOVE_PM_DATA_TASK:TASKNAME=TASK1,SRCNEID=1,PMDATA
TYPE=HOUR_DATA,PERIODTYPE=DAY,PERIODNUM1,STYLE=INTRA
DAY,DAYBEFORE90;

Parameter
Description
Remark
TASKNAME
Name of the task.
SRCNEID
Network element ID.

PMDATAT
YPE
Data table type
66
Parameter
Description
Remark
STYLE
Backup style

between is chosen, specify beginning time and end
time. If before is chosen, specify beginning time. The
PERIODT
YPE
Backup frequency

chosen; hour, week, and month.
PERIODNUM
Number of frequency
present.

present.
DAYBEFORE
Time duration for data

to be backed up
Mandatory parameter. The range is 1-800. The

default value is 90.
STARTTIME
Start time
Result
Addition new task for deleting performance data is complete.
Adding a Task to Back up Alarm Rule

Prerequisite
Context
Perform this operation to add new task for alarm rule data backup.
To add new task for alarm rule data backup, enter the command:
ADDBAK_FM_RULE_TASK:TASKNAME=TASKNAME,FILEP
ATH=FILEPATH,PERIODTYPE=PERIODTYPE,PERIODNUM=PERIOD
NUM,STARTTIME=STARTTIME,FILENAME=FILENAME;.
To add new task for alarm rule data backup named TASK1 with the
backup file saved to the C drive every day and with period type
being DAY, then the command is as follow:
ADDBAK_FM_RULE_TASK:TASKNAME=TASK1,FILEPATH=C:,PERIODT
YPE=DAY,PERIODNUM=1;
Result
Addition new task for alarm rule data backup is complete.
Adding a Task to Back up Historical

Alarm
Prerequisite
Context
Perform this operation to add new task for historic alarm data
backup.
To add new task for historic alarm data backup, enter the
command
:ADDBAK_ALARM_TASK:TASKNAME=TASKNAME,FI
LEPATH=FILEPATH,FILENAME=FILENAME,STARTTIME=START
TIME,PERIODTYPE=PERIODTYPE,PERIODNUM=PERIODNUM,STYLE
=STYLE,DAYBEFORE=DAYBEFORE,ISCLEAN=ISCLEAN;
67
To add new task for historic alarm data backup named TASK1 with
the backup file saved to the C drive every day and with period type
being DAY, then the command is as follows. (Original data is not
to be deleted)
ADDBAK_ALARM_TASK:TASKNAME=TASK1,FILEPATH=C:,PERIODTYP
E=DAY,PERIODNUM=1,STYLE=INTRADAY,DAYBEFORE=90,ISCLEAN
=N;
Result
Addition of new task for historic alarm data backup is complete.
Adding a Task to Back up Information

Prerequisite
Context
Perform this operation to add new task for notification data backup.
Steps
To add new task for historic notification data backup, Enter

the command:
ADDBAK_INFORM_TASK:TASKNAME=TASKNAME,F
ILEPATH=FILEPATH,FILENAME=FILENAME,STARTTIME=START
TIME,PERIODTYPE=PERIODTYPE,PERIODNUM=PERIODNUM,STYLE
=STYLE,DAYBEFORE=DAYBEFORE,ISCLEAN=ISCLEAN;
To add new task for historic notification data backup named TASK1
with the backup file saved to the C drive every day and with period
type being DAY, the command is as follows. (Time duration for data
to be backed up is 90 and original data is not to be deleted)
ADDBAK_INFORM_TASK:TASKNAME=TASK1,FILEPATH=C:,PERIODTY
PE=DAY,PERIODNUM=1,STYLE=INTRADAY,DAYBEFORE=90,ISCLEAN
=N;
END OF STEPS.
Result
Addition of new task for notification data backup is complete.
Adding a Task to Delete History

Alarm Data
Prerequisite
Context
Perform this operation to add new task for deleting historic alarm
data.
To add new task for deleting historic alarm data, enter the
command :ADDREMOVE_ALARM_TASK:TASKNAME=TASKNAME,PERI
ODTYPE=PERIODTYPE,PERIODNUM=PERIODNUM,STARTTIMESTART
TIME,DAYBEFORE=DAYBEFORE,STYLE=STYLE;
To add new task for deleting historic alarm data named TASK1 with
period type being DAY and the time duration for data to be backed
up is 90 with original data is not to be deleted, the command is as
follows:
68
ADDREMOVE_ALARM_TASK:TASKNAME=TASK1,PERIODTYPE=DAY,PE
RIODNUM=1,DAYBEFORE=90,STYLE=INTRADAY;
Result
Addition new task for deleting historic alarm data is complete.
Adding a Task to Delete History

Notification Data
Prerequisite
Context
Perform this operation to add new task for deleting historic notification data.
To add new task for deleting historic notification data, enter the
command
:ADDREMOVE_INFORM_TASK:TASKNAME=TASKNAME,P
ERIODTYPE=PERIODTYPE,PERIODNUM=PERIODNUM,STARTTIME
STARTTIME,DAYBEFORE=DAYBEFORE,STYLE=STYLE;
To add new task for deleting historic notification data named TASK1
with period type being DAY and the time duration for data to be
backed up is 90 with original data is not to be deleted, the command is as follows:
ADDREMOVE_INFORM_TASK:TASKNAME=TASK1,PERIODTYPE=DAY,P
ERIODNUM=1,DAYBEFORE=90,STYLE=INTRADAY;
Result
Addition new task for deleting historic notification data is complete.
Suspending Periodic Task

Prerequisite
Context
Periodic task has been created and is in active state.
Perform this operation to suspend active periodic tasks. To reactivate the suspended task, refer to Activating Periodic Task.
Only the tasks that are in active states can be suspended. Suspending tasks does not terminate the tasks. Suspended tasks can
be reactivated but terminated tasks cannot be reactivated.
To suspend active tasks, enter the command:SUSPENDBAKTASK:T
ASKID=TASKID;
To suspend active task named TASK1, the command is as follows:
SUSPENDBAKTASK:TASKID=1;
Result
Suspending an activated task is complete.
69
Activating Periodic Task

Prerequisite
Context
Periodic task has been created and is in suspended state.
Perform this operation to activate suspended periodic tasks. Activating a periodic task can only be performed on suspended state.
To activate suspended tasks, enter the command:ACTIVEBAKTAS
K:TASKID=TASKID;
To activate suspended task named TASK1, the command is as follows:
ACTIVEBAKTASK:TASKID=1;
Result
Activating a suspended task is complete.
Stopping Periodic Task

Prerequisite
Context

Perform this operation to stop periodic tasks.
To terminate periodic tasks, enter the command:STOPBAKTASK:T
ASKID=TASKID;
To terminate periodic task named TASK1, the command is as follows:
STOPBAKTASK:TASKID=1;
Result
Termination of periodic task is complete.
Showing Periodic Task

Prerequisite
Context

Perform this operation to query periodic tasks.
To query periodic tasks, enter the command:SHOWBAKTASK:TASK
ID=TASKID,STATUSSTATUS;
To query periodic task, the command is as follows:
SHOWBAKTASK;
Result
70
Querying of periodic task is complete.
Chapter
Performance Data
Analysis
Table of Contents:
Introduction to Data Analysis ..............................................71
General Data Analysis ........................................................72
Comparative Analysis of Time .............................................72
Comparative Analysis of Modules .........................................73
Comprehensive Analysis of Performance Statistics and Alarm
Information ......................................................................73
Comprehensive Analysis of Performance Statistics and Log Information .........................................................................74
Introduction to Data Analysis

Description
Modes of Data
Analysis
eneral Steps for

Data Analysis
Through monitoring the performance of each NE in the system,

querying and analyzing performance data and related data reports,
user can master system real-time operating status, and find and
rectify system network or NE performance variation, which improves the service quality and operation efficiency of the whole
system.
The methods for analyzing system operating status are listed as
follows.
General data analysis
Comparative analysis of time
Comparative analysis of module
Comprehensive analysis of performance statistics and alarms
Comprehensive analysis of performance statistics data and log
The general steps for data analysis are listed as follows.

1. Login OMC network management platform, and enter performance management main window.
2. In performance management, collect performance statistics
specifications by using the methods of task management and
system analysis.
3. Stop performance statistics and output statistics result.
4. Analyze according to performance statistics result.
5. Judge system operating status according to data analysis result.
71
General Data Analysis

Description
Analysis Steps
Switching maintenance personnel should record the important performance data (Such as highest CPU load) to a customerized Excel
table during daily maintenance, and perform horizontal and vertical comparison as per the data in the table.
Selecting Group by Time instead of Group by Location or Group

by Attribute helps to analyze whether the data generated during a certain time segment is missing. This helps in analyzing
the time of data to check whether the time segments are consecutive.
Selecting Group by Location instead of Group by Time helps to

analyze all the measured data within a period of time. The data
of each measurement item and each module during a certain
time segment can be obtained in this way.
The steps for a general data analysis are listed as follows.

1. Judge whether there is data being 0, if there is, then analyze
whether it is proper.
2. Analyze whether each data complies with normal logical relationship.
Example
In performance statistics, judge whether there is data being 0. If

there is, analyze whether it is proper. The example is listed as
follows.
Times of requests are not 0, while times of successful requests

are 0, which indicates that there may be faults on the system
(It may be that the link between wireless side and AGW, or
between AGW and AAA is broken).
The peak value (or average value) of board CPU or memory

is 0, which indicates that the board may be faulty (It may be
board power-off automatically, exiting service automatically or
board hardware faults).
In normal traffic, sometimes it is normal that the times of call

failure caused by various reasons are 0.
Comparative Analysis of
Time
Description
Through data comparison and analysis in different time segments,

for the performance data collected from the same measurement
items, the changes on system performance and traffic with the
changing of time can be obtained.
When analyzing performance statistics data, the changes on system service performance index and OSS performance index (that
is CPU/memory usage) can be obviously known by referring to the
changes on the traffic in busy and idle time.
Example
72
The maintenance personnel is analyzing system busy/idle situation

in a day, so he can query the average occupation rate of CPU and
Chapter 4 Performance Data Analysis
memory in AGW load measurement during a day. Select Group

by Hour facilitates to obtain the data generated during 24 hours
during the day. It helps to know the busy/idle state of the system.
Chart Display function of the system aids in visual display of query
results in a curve.
Comparative Analysis of
Modules
Description
Through module comparison can analyze whether the traffic on

each module is basically even or not.
Even traffic on each module can ensure that there is no module
becoming system bottleneck because of heavy load, meanwhile
there is also no module which is not fully used because of low
load.
Example
The maintenance personnel is comparing the CPU occupation rate

and MEM occupation rate of module 1# and module 3#, so he
can perform comparative analysis of module through self-defined
query.
Comprehensive Analysis of
Performance Statistics and
Alarm Information
Description
Generally when the system becomes faulty, it is reflected through

different ways.
When querying performance index data, if abnormality is found,
record the time segment that abnormality occurs, then query
whether related alarms are generated in this time segment, and
whether the alarm is still there.
Example
Within a period of time, user successful access rate is 0 in an office, and connection timeout times are nearly equal to the number
of exiting owing to AAA server. Through querying the alarms information in this period, the alarm that link between AGW and AAA
server is broken is found. Later on, the reason that AAA server is
powered off abnormally is found.
73
Comprehensive Analysis of
Performance Statistics and
Log Information
Description
Changes on performance index data is closely related to configured

data. If the configured data is not correct, it may cause performance statistics data variation.
When querying performance index data, if abnormality is found,
record the time segment when abnormality occurs, then query
whether there are related operations log, and analyze whether the
operations may cause the variation. If confirmed, then modify the
data at proper time, and observe performance index data again.
74
Appendix
Performance
Measurement Item
Reference
Table of Contents:
AGW Load Measurement...........................................................
Service Process Measurement ...................................................
R3R6 Interface User Packet Measurement ...................................
AGW Context Resource Measurement .........................................
IP Pool Alloc Measurement for Every IP Pool ................................
KPI Measurement ....................................................................
75
76
86
90
94
95
AGW Load Measurement

Mean Ratio of the CPU Usage (%)
Name
Description
Accumulation
Method
Collection Method
Mean Ratio of the CPU Usage (%)

Calculate the percentage of average CPU load in a measurement
period.
It adopts M accumulation Method.
It adopts CC collection method.
Peak Ratio of the CPU Usage(%)

Name
Description
Accumulation
Method
Collection Method
Peak Ratio of the CPU Usage (%)

Calculate the percentage of the peak CPU load in a measurement
period.
It adopts M accumulation method.
75
Mean Ratio of the Memory Usage (%)

Name
Description
Accumulation
method
Collection Method
Mean Ratio of the Memory Usage (%)

Calculate the percentage of average memory usage in a measurement period.
Peak Ratio of the Memory Usage (%)

Name
Description
Accumulation
Method
Collection Method
Peak Ratio of the Memory Usage (%)

Calculate the percentage of peak memory usage in a measurement
period.
Mean Ratio of the Hard Disk

Usage(1/10000)
Name
Description
Accumulation
Method
Collection Method
Mean Ratio of the Hard Disk Usage (1/10000)

Calculate the ratio value (%%) of hard disk usage in a measurement period.
Service Process
Measurement
Number of Successful Access
Name
Description
76
Number of Successful Access

Calculate the number of times that the user accesses and obtains
IP address successfully in a measurement period.
Chapter A Performance Measurement Item Reference
Measurement
Triggering Point
When AGW detects that MS finishes network registration, obtains

IP address successfully, carries out network service normally, then
AGW calculates it as user successful access.
For Simple IP DHCP Proxy mode users

AGW and MS completes network registration and establishes
ISF flow, AGW simulates the interaction for DHCP Server and
MS, and distributes IP address. After AGW sends DHCP Ack
messages, it calculates as successful user access, as shown in
Figure 28.
FIGURE 28 SIMPLE IP DHCP PROXY MODE
For Simple IP DHCP Relay mode users

After AGW finishes network registration with MS and establishes ISF flow, as DHCP Relay agent, AGW relays the DHCP
message between MS and DHCP Server. After AGW completes
DHCP Ack message relay to MS, it calculates as successful
user access, as shown in Figure 29.
77
FIGURE 29 SIMPLE IP DHCP RELAY MODE
For PMIP mode users

After AGW completes network registration with MS and establishes ISF flow, it receives DHCP message from MS and triggers PMIP registration. After AGW sends DHCP Ack message
to MS, it calculates as successful user access, as shown in Figure 30.
FIGURE 30 PMIP MODE
For CMIP mode users

After AGW completes network registration with MS and establishes ISF flow, as the FA, AGW receives MIP signaling from MS.
After AGW sends RRP message to MS, it calculates as successful user access, as shown in Figure 31.
78
FIGURE 31 CMIP MODE
Pay attention to the following situations.
Accumulation
Method
Collection Method
Under the situation that last access of the MS is not unregistered, if new access and registration process is originated
again, AGW considers access service as transient interruption.
After establishes initial service flow successfully with MS, it calculates as a successful access. The previous MS access is released, and AGW calculates it as a unregistration originated by
BS side.
Under the situation that users last access is not completed,

and the user originates a new access attempt, now previous
uncompleted access process is terminated directly and AGW
does not calculate it.
Under the situation that users last access is successful, the

user originates a new access and fails, AGW calculates this
access flow as unsuccessful access.
Under the situation that AGW requires MS to keep IP address,

DPF function finds user address renewal failure (MS is transient
interrupted, after originates secondary access, the DHCP and
MIP flows originated by the user are all considered as renewal
flows), now if DHCP or MIP flow fails, AGW calculates this flow
as user unregistration according to exact reasons.

Number of Unsuccessful Access

Owing to BS Side
Name
Number of Unsuccessful Access Owing to BS Side
79
Description
Measurement
Triggering Point
Calculate the number of times that user fails to access in a measurement period, and the failure is caused by BS side.
When BS accesses, it answers with failure response, or no response, which causes that access process can not continue. The
details are listed as follows.
AGW does not receive MS_PreAttachment_Ack message till

it is timeout or it indicates failure in MS_PreAttachment_Ack
message.
AGW does not receive EAP_Transfer response message from

BS side during authentication process till it is timeout.
After AGW sends Key_Change_Directive message, it indicates as failure in Key_Change_Ack response message from
BS side.
AGW does not receive MS_Attachment_Req message till it

is timeout, or it indicates failure in MS_Attachment_Ack response message, or it is timeout while AGW waiting for MS_Attachment_Ack message.
AGW does not receive Path_Reg_Rsp message during ISF

flow creating process till it is timeout, or receives the message
indicating failure.
For non-secondary access, after MS completes service flow creation, it does not originate flow to obtain IP address, or MS
does not originate DHCP Request message and the flow is
unsuccessful, which results in obtaining IP address timeout.
Failure caused by key message check error (It does not affect the
judgement when the message can not be decoded), the details are
shown as follows.
Mandatory parameters negotiation is error in MS_PreAttachment_Req message sent by BS, and AGW sends failed
MS_PreAttachment_Rsp response, then AGW calculates it
as unsuccessful access (excluding request message discarded
and rejected because of overload control; discarded messages
after NSP disabled is not calculated too).
Mandatory parameters negotiation is error in MS_Attachment_Req message sent by BS, and AGW sends failed
MS_Attachment_Rsp response, then AGW calculates it as
unsuccessful access.
Mandatory parameters negotiation is error in Path_Reg_Rsp

message in ISF service flow sent by BS, and AGW sends failed
Path_Reg_Ack response, then AGW calculates it as unsuccessful access.
Failure caused by flow conflict during access, the details are shown
as follows.
Accumulation
Method
80
During MS establishing ISF and PSF flow, MS is carrying out

handover and handover is not completed normally. So access
process is not completed successfully, then AGW calculates it
as unsuccessful access owing to BS side.
During MS accessing, before obtaining IP address successfully,

BS originates network exiting, which causes unsuccessful access.
Collection Method

Owing to AAA Server
Name
Number of Unsuccessful Access Owing to AAA Server
Description
Calculate the number of times that uses fails to access in a measurement period, and the failure is caused by AAA server.
Measurement
Triggering Point
AAA causes unsuccessful access during accessing, and the details

are listed as follows.
Accumulation
Method
Collection Method
AGW sends Radius Access_Request message, and AAA

server does not response or the response message is rejection, then AGW calculates it as unsuccessful access owing to
AAA server.
AGW receives Radius Access_Challage message sent from

AAA server, and error parameters are carried, which causes
that AGW can not resolute normally, then AGW calculates it as
unsuccessful access owing to AAA server.
AGW receives Radius Access_Accept message sent from

AAA Server, and error parameters are carried, which causes
that AGW can not resolute correctly, or authorization fails
because key authorization information is insufficient, then
AGW calculates it as unsuccessful access owing to AAA server.
During MS accessing, it receives Disconnect Req message

sent from AAA, which causes that access process is terminated.


Owing to HA
Name
Number of Unsuccessful Access Owing to HA
Description
Calculate the number of times that user fails to access in a measurement period, and failure is caused by HA.
Measurement
Triggering Point
HA causes unsuccessful access during accessing, and the details

There is no response after sending RRQ during MIP process,

which causes obtaining IP address timeout.
RRP message is rejected after sending RRQ during MIP

process, which causes obtaining IP address timeout.
Under PMIP DHCP Relay mode, HA denies the address assigned

by DHCP Server, and it assigns new address for the user, which
81
causes address conflict and result in user release, then AGW

calculates it as unsuccessful access owing to HA side.
Accumulation
Method
Collection Method


Owing to DHCP Server
Name
Description
Measurement
Triggering Point
Number of Unsuccessful Access Owing to DHCP Server

Calculate the number of times that user fails to access in a measurement period, and failure is caused by DHCP server.
DHCP causes unsuccessful access during accessing, and the details
After DHCP sends Discovery message, obtaining IP address is

timeout, and DHCP server side does not response correctly.
After DHCP sends Discovery message, it receives NAK message.
After DHCP sends Request message, it receives NAK message.
After DHCP sends Request message, obtaining IP address is

timeout, and DHCP server side does not response correctly.
Note:
This performance measurement item is effective to DHCP Relay
mode of both simple IP and mobile IP.
Accumulation
Method
Collection Method


Owing to AGW
Name
Description
Measurement
Triggering Point
Number of Unsuccessful Access Owing to AGW

Calculate the number of times that user fails to access in a measurement period, and failure is caused by AGW.
AGW causes unsuccessful access during accessing, and the details
82
AGW context resources are inadequate, which causes that user

fails to access.
Accumulation
Method
Collection Method
AGW internal GGUP board is reset, which causes that current

user fails to access
AGW DB fails to call the interface, which causes that user fails
to access.
During user accessing and before obtaining IP address, administrator originates user release, which causes that user fails to
access.

Number of Exit Owing to Wireless

Side
Name
Description
Measurement
Triggering Point
Number of Exit Owing to Wireless Side

Calculate the number of times that user deregisters because of
wireless side in a measurement period.
Deregistration caused by layer 2 deregistration event, and the details are listed as follows.
Deregistration originated through Path_Dreg_Req message

by MS.
Deregistration
originated
tExit_MS_State_Change message by BS.
MS informs CMAC_Key_Count to reach the maximum value

through CMAC_Key_Count message to trigger AGW to originate deregistration.
MS is at IDLE status, and it carries poweroff notification

through LU_Req message, which triggers deregistration.
MS is handover or exits IDLE status, and ISF flow recreation

is lost, which causes that AGW triggers deregistration.
Under the condition that users last access is completed, and

it originates new access again, then MS previous access is released, and AGW calculates it as a deregistration originated by
MS.
through
Ne-
Deregistration originated by layer 3 deregistration event, and the

details are listed as follows.
MS originates deregistration through DHCP Release message.
MS originates deregistration through DHCP Decline message.
For users under Simple IP DHCP Relay mode and PMIP

DHCP Relay mode, DHCP process renewal fails, which causes
deregistration, and it is calculated as deregistration caused by
BS side. (DHCP Server does not deregister user actively, so
there is no independent measurement items for it.)
MS originates deregistration through RRQ Lifetime = 0 message.
83
Deregistration caused by MS status timeout, and the details are

listed as follows.
AGW judges that MS is not re-authenticated normally, which

causes AK Lifetime timeout and originates MS deregistration.
During
the process
that AGW judges
MS, it causes
IDLE_Mode_Timeout timeout, and administrator requires
deregistration, then AGW deregisters the user.
PMIP/Simple IP DHCP Proxy/CMIP release expires, and MS

does not re-let, which causes AGW to trigger deregistration.
(There is no lease management for Simple IP DHCP Relay in
AGW.)
Deregistration caused by MS status inconsistency, and the details

Accumulation
Method
Collection Method
AGW receives handover request under IDLE status, and it

judges that the status is inconsistent, which triggers deregistration and network exiting.
AGW enters IDLE status, and system judges the status is inconsistent, which triggers deregistration.

Number of Exit Owing to AGW

Name
Description
Measurement
Triggering Point
Accumulation
Method
Collection Method
Number of Exit Owing to AGW

Calculate the number of times that user deregisters caused by
AGW in a measurement period.
AAA delivers Idle-timeout, but there is no flow for the users in

a long time, which causes deregistration.
Execute deleting NSP in batch from OMC network management, and the user deregisters caused by single-user deleting.
Deregistration caused by GGUP board reset.

Number of Exit Owing to HA

Name
Description
Measurement
Triggering Point
84
Number of Exit Owing to HA

Calculate the number of times that user deregisters caused by HA
in a measurement period.
HA sends valid Revocation Req message actively, and AGW

deregisters the users.
After MS sends RRQ, it receives Revocation message from

HA, and AGW deregisters the users.
Accumulation
Method
Collection Method
MIP renews, and HA side returns renewal failure, which causes

MIP dialog timeout, and AGW deregisters the users.
MS originates MIP renewal, and HA returns Lifetime=0 in RRP,

which causes that AGW deregisters the users.

Number of Exit Owing to AAA Server

Name
Description
Measurement
Triggering Point
Accumulation
Method
Collection Method
Number of Exit Owing to AAA Server

Calculate the number of times that user deregisters caused by AAA
server in a measurement period.
AGW receives valid Radius Disconnect_Req message sent

from AAA server, and AGW deregisters the users.
MS originates pre-pay, and the quota delivered by AAA has

been exhausted, then AGW deregisters the users.

Number of Successful Handover with

Service Flow
Name
Description
Measurement
Triggering Point
Number of Successful Handover with Service Flow

Calculate the number of service flow handover handled by AGW in
a measurement period, and handover is successfully completed.
The controlled handover is completed normally, and AGW receives handover Path_Reg_Ack message, confirming handover is correct.
Non-controlled handover is completed normally, and AGW receives handover Path_Reg_Ack message, confirming handover is correct.
When ISF and PSF establishment is not completed, the controlled handover occurs on MS.
When SF and PSF establishment is not completed, non-controlled handover occurs on MS.

85
Note:
Under the condition that there is no service flow, AGW judges that
CMAC_Key_Count and BSID are all updated, then AGW is not
responsible for MS handover.
Accumulation
Method
Collection method

R3R6 Interface User Packet

Measurement
Mega-number of Data Packets
Received from R6 Reference Point
Name
Description
Mega-number of Data Packets Received from R6 Reference Point

Calculate the number of user interface messages received by R6
reference point in a measurement period.
Note:
R6 media interface measurement items include user R2 signaling.
Measurement
Triggering Point
Accumulation
Method
Collection Method
For non-fragmentation messages, after GGUP board of AGW

receives messages and verifies them, it judges them as R6
messages and collects the calculation.
For fragmentation messages (GRE encapsulation outer layer IP

fragmentation messages), after GGLP board regroups, GGUP
board receives messages and does not need to regroup. After
AGW judges the message as R6 media interface message, it
collects the calculation.

Mega-number of Data Packets Sent

to R6 Reference Point
Name
86
Mega-number of Data Packets Sent to R6 Reference Point
Description
Calculate the number of user interface messages sent from R6

Note:
Measurement
Triggering Point
Accumulation
Method
Collection Method

sends the message to link layer transmitting queue, it collects
the calculation.
For the messages requiring fragmentation, after AGW finishes

R6 message fragmentation and GRE encapsulation, it sends
the messages to link layer transmitting queue one by one, and
calculates one by one.

Mega-bytes of Data Packets

Name
Description
Mega-bytes of Data Packets Received from R6 Reference Point

Calculate the number of user interface bytes received by R6 reference point in a measurement period.
Note:
Measurement
Triggering Point
Accumulation
Method
Collection Method

receives the messages and verifies them, it judges them as R6
messages, then it collects the calculation.
For fragmentation messages (outer layer fragmentation), after

GGLP regroups, GGUP receives messages and does not need to
regroup. AGW judges the message as R6 message, then collect
the calculation. The calculated items are regrouped messages.

Mega-bytes of Data Packets Sent to

R6 Reference Point
Name
Mega-bytes of Data Packets Sent to R6 Reference Point
87
Description
Calculate the number of user interface bytes sent by R6 reference

point in a measurement period.
Note:
Measurement
Triggering Point
Accumulation
Method
Collection Method
For non-fragmentation messages, after GGUP boards of AGW

sends the slicking messages to link layer queue, it collect the
calculation.
For messages require fragmentation, after GGUP board of AGW

finishes messages fragmentation and encapsulation, and when
sends the messages to link layer queue one by one, it collects the calculation one by one. Every message includes bytes
number encapsulated by R6 media interface.

Mega-number of Data Packets

Name
Description
Mega-number of Data Packets Received from R3 Reference Point

Calculate the number of user interface messages received by R3
Note:
R3 interface excludes DHCP signaling and MIP signaling dispatched
by AGW.
Measurement
Triggering Point
88
User interface sends uplink user data messages, and the details
For non-fragmentation messages of Simple IP users, after

GGUP board of AGW receives them and judges them as
user R3 media interface messages, it collects the calculation
directly.
For fragmentation messages of Simple IP users, after GGUP

boards of AGW receives them, it does not regroup. Similarly
after it judges them as R3 messages according to user address,
it collects the calculation directly.
For non-fragmentation messages of IPinIP type of MIP users,

they are judged as user messages according to internal address
after received, it collects the calculation on messages directly.
For fragmentation messages of IPinIP type of MIP users, regroup by GGUP board, and when GGUP board judges IPinIP
internal encapsulated message is user message, then it collects the calculation on regrouped messages.
Accumulation
Method
Collection Method

Mega-number of Data Packets Sent

to R3 Reference Point
Name
Description
Measurement
Triggering Point
Accumulation
Method
Collection Method
Mega-number of Data Packets Sent to R3 Reference Point

Calculate the number of user interface messages sent by R3 reference point in a measurement period.

sends the messages to link layer transmitting queue, it collects
the calculation.
For the messages requiring fragmentation, after GGUP board of

AGW finishes messages fragmentation and sends them to link
layer transmitting queue one by one, it collects the calculation
one by one.

Mega-bytes of Data Packets

Name
Description
Measurement
Triggering Point
Mega-bytes of Data Packets Received from R3 Reference Point

Calculate the number of user interface bytes received by R3 reference point in a measurement period.
For non-fragmentation messages of Simple IP users, after

GGUP board of AGW receives them and judges them as
user R3 media interface messages, it calculates the whole
messages directly.
For fragmentation messages of Simple IP users, after GGLP

and GGUP board of AGW receive them, they do not regroup.
Similarly after judge them as R3 media interface messages
according to user address, it calculates the whole messages
directly.
For non-fragmentation messages encapsulated by IPinIP of MIP

users, after GGUP board of AGW receives them and judges
them as user messages according to internal encapsulated IP
messages address, it calculates the whole messages directly.
For fragmentation (IPinIP outer layer fragmentation) messages

encapsulated by IPinIP of MIP users, GGUP board of AGW regroups the messages, and when GGUP board judges internal
encapsulated IP messages as user messages, it calculate the
regrouped messages.

89
Note:
Messages statistics of MIP users includes IPinIP encapsulation
header.
Accumulation
Method
Collection Method

Mega-bytes of Data Packets Sent to

R3 Reference Point
Name
Description
Measurement
Triggering Point
Mega-bytes of Data Packets Sent to R3 Reference Point

Calculate the number of user interface bytes sent by R3 reference
point in a measurement period.
For non-fragmentation messages, GGUP board of AGW sends

R3 messages to link layer transmitting queue, and collects the
calculation.
For messages requiring fragmentation, after GGUP board of

AGW finishes messages fragmentation and IPinIP encapsulation to MIP user messages, it sends the fragmentation messages to link layer queue one by one, and calculate every message one by one.
Note:
MIP user messages include the bytes encapsulated by IPinIP.
Accumulation
Method
Collection Method

AGW Context Resource

Measurement
Number of Occupied MS Contexts in
AGW (Authenticator)
Name
90
Number of Occupied MS Contexts in AGW (Authenticator)
Description
Measurement
Triggering Point
Calculate the number of used MS contexts in AGW Authenticator

logical functional entity in a measurement period.
Performance measurement calls database interface periodically.
Note:
Query the fields of MS contexts number in the logical functional
entity of database table AGW Authenticator through calling database interface.
Accumulation
Method
Collection Method

Total Number of MS Contexts in

AGW (Authenticator)
Name
Total Number of MS Contexts in AGW (Authenticator)
Description
Calculate the total number of MS contexts in AGW Authenticator

logical functional entity in a measurement period.
Measurement
Triggering Point
Note:
entity of database table AGW Authenticator through calling database interface.
Accumulation
Method
Collection Method

Number of Occupied Service Flows

in AGW (DPF)
Name
Description
Number of Occupied Service Flows in AGW (DPF)

Calculate the number of occupied service flow in AGW DPF logical
functional entity in a measurement period.
91
Measurement
Triggering Point
Note:
Query the fields of service flow number in the logical functional
entity of database table AGW DPF through calling database interface.
Accumulation
Method
Collection Method

Total Number of Service Flows in

AGW (DPF)
Name
Description
Measurement
Triggering Point
Total Number of Service Flows in AGW (DPF)

Calculate the total number of service flow in AGW DPF logical functional entity in a measurement period.
Note:
Query the fields of service flow number in the logical functional
entity of database table AGW DPF through calling database interface.
Accumulation
Method
Collection Method

Number of Occupied MS Contexts in

AGW (PC)
Name
Description
92
Number of Occupied MS Contexts in AGW (PC)

Calculate the number of occupied MS contexts in AGW PC logical
functional entity in a measurement period.
Measurement
Triggering Point
Note:
Query the fields of occupied MS contexts number in the logical
functional entity of database table AGW Authenticator through calling database interface.
Accumulation
Method
Collection Method

IT adopts CC collection method.
Total Number of MS Contexts in

AGW (PC)
Name
Description
Measurement
Triggering Point
Total Number of MS Contexts in AGW (PC)

Calculate the total number of MS contexts in AGW PC logical functional entity in a measurement period.
Note:
entity of database table AGW PC through calling database interface.
Accumulation
Method
Collection Method

Number of Occupied EVL Contexts

in FA
Name
Description
Number of Occupied EVL Contexts in FA

Calculate the number of occupied EVL contexts in FA logical functional entity in a measurement period.
93
Measurement
Triggering Point
Note:
Query fields number of occupied EVL contexts in the logical functional entity of database table FA through calling database interface.
Accumulation
Method
Collection Method

Total Number of EVL Contexts in FA

Name
Description
Measurement
Triggering Point
Total Number of EVL Contexts in FA

Calculate the total number of EVL contexts in FA logical functional
entity in a measurement period.
Note:
Query fields number of EVL contexts in the logical functional entity
of database table FA through calling database interface.
Accumulation
Method
Collection Method

IP Pool Alloc Measurement

for Every IP Pool
Number of Occupied IP Addresses
by the IP Pool
Name
Description
94
Number of Occupied IP Addresses by the IP Pool

Calculate the number of occupied IP addresses in AGW IP pool in
a measurement period.
Measurement
Triggering Point
Query database specified interface periodically.
Note:
Query the fields number of occupied IP addresses in database table
AGW IP pool through calling database interface.
Accumulation
Method
Collection Method

Total Number of IP Addresses by the

IP pool
Name
Description
Measurement
Triggering Point
Total Number of IP Addresses by the IP pool

Calculate the total number of IP addresses in AGW IP pool in a
measurement period.
Query database specified interface periodically.
Note:
Query the fields number of IP addresses in database table AGW IP
pool through calling database interface.
Accumulation
Method
Collection Method

KPI Measurement
Ratio of Successful Access (%)
Name
Ratio of Successful Access (%)
Description
Calculate the ratio of successful user access in a measurement

period.
Calculation
Formula
Ratio of user successful access = Number of Successful Access *

100 / ( Number of Unsuccessful Access Owing to BS Side + Number of Unsuccessful Access Owing to AAA Server + Number of Unsuccessful Access Owing to HA + Number of Unsuccessful Access
Owing to AGW + Number of Unsuccessful Access Owing to DHCP
Server + Number of Successful Access)
95
This page is intentionally blank.
96
List of Glossary
AGW - ASN Gateway
CMIP - Client Mobile IP
DHCP - Dynamic Host Configuration Protocol
FA - Foreign Agent
GGLP - AGW Line Processor of GE interface
GGUP - AGW GTP-U Processor
GRE - Generic Routing Encapsulation
ISF - Initial Server Flow
MIP - Mobile IP
MS - Mobile Station
OMC - Operations & Maintenance Center
OMM - Operation Maintenance Module
PMIP - Proxy-Mobile IP
PSF - Preparative Server Flow
97

SM ZXMBW AGW Performance Statistics Training Material

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SM ZXMBW AGW Performance Statistics Training Material

Caricato da

Copyright:

Formati disponibili

ZXMBW AGW

Performance Statistics and Analysis

Performance Management Concepts .................1

Performance Task Configuration Guide .............7

Finding Calculation Index............................................31

Maintenance of Performance Alarm Data ........ 53

Adding a Task to Back up Historical Alarm .....................67

Performance Data Analysis ............................. 71

Performance Measurement Item

Mega-number of Data Packets Received from R6

The performance management manages the performance of the

Measurement job management

Service quality monitoring

The implementation of the performance management is mainly

Create the performance statistics job

Confidential and Proprietary Information of ZTE CORPORATION

ZXMBW AGW Training Material

As shown in Figure 1, first, the operator should input the job

Modify the performance statistics job

Delete the performance statistics job

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Performance Management Concepts

sends the deletion information of the task to be deleted to

Query the performance statistics job

Performance measurement functional module of OMC is used

Performance Measurement Format

Format of each performance measurement item in this manual is

Measurement Triggering Point

Confidential and Proprietary Information of ZTE CORPORATION

ZXMBW AGW Training Material

It means the name of performance measurement items, which is

Accumulate by module M (Max/Min/Sum/Average/Latest), and

Accumulate by time T (Max/Min/Sum/Average/Latest).

Accumulate by object O (Max/Min/Sum/Average/Latest).

Whether to measure repeated signaling number and flow. RT

Collection method for performance measurement items are as

bidirectionally (means can be increased or decr

It is a kind of measurement method on a group

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Performance Management Concepts

Measurement Item is a set of attributes associated with the same

AGW Network Element

Measurement Object Type

A measurement type is categorization of a collection of related

The measurement object can be defined as the physical entity or

The counter is a measurement index in the measurement type,

Refer to for the relationship between the measurement type and

Confidential and Proprietary Information of ZTE CORPORATION

ZXMBW AGW Training Material

FIGURE 2 RELATIONSHIP BETWEEN MEASUREMENT TYPE AND COUNTER

The collection granularity refers to the cycle of collecting data from

The calculation index is used to evaluate the performance of the

The Quality of Service (QoS) is a type of security mechanism of the

Confidential and Proprietary Information of ZTE CORPORATION

Overview of Creating and

The process of performing, creating, and running performance

Confidential and Proprietary Information of ZTE CORPORATION

ZXMBW AGW Training Material

FIGURE 3 PERFORMANCE STATISTICS OPERATION FLOW

Before commencing with the operation, ensure the following:

The user has logged in the ZTE network management client

The performance measurement job has been created.

The performance data are in the performance database and

The user can customize the measurement items. Measurement