Professional Documents
Culture Documents
HUAWEI SEQ Analyst Basic KPI Mannual
HUAWEI SEQ Analyst Basic KPI Mannual
Issue 01
Date 2017-02-28
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
The KQI/KPI system for the Huawei-provided SEQ Analyst is a scientific calculation and
measurement system. For details, see the contents in the Calculation Formula and
Measurement Point column of each KQI/KPI.
The cell information (2G cells, 3G service areas, and 4G cells) collected by the SEQ
Analyst is the end cell information obtained from the core network. The system cannot
obtain the cell update information only from the wireless network. As a result, the system
can fill the cell information collected from core network messages. The filled cell
information is inconsistent with actual data.
A/Iu-CS MSC
Nc MSC
(BICC/ISUP)
Nc (SIP) MSC
The KQIs/KPIs of NEs contain only signaling-plane KPIs and measured on their corresponding NEs.
The KQIs/KPIs in the SEQ Analyst are calculated based on the data collected from inter-NE interfaces
and counters measured at measurement points. The KQIs/KPIs of NEs are different from those of the
SEQ Analyst due to different measurement points of the NEs and SEQ Analyst.
Indicator
GSM KPI
− GSM MO Call
Call Success Rate(%) [GSM Successful GSM Call Attempts(times): On MSC Pool, MSC
Call(times)]/[GSM Call the calling party side, measure
Attempts(times)] the number of CM Service
Request messages at
measurement point 1 shown in
IStep 1Figure 1.1.
GSM Successful Call(times):
Measure the number of times
the Alerting message is
received (at measurement point
4 shown in IStep 1Figure 1.1)
after the CM Service Request
message.
TCH Assignment [Successful TCH TCH Assignment MSC Pool, MSC
Success Rate(%) Assignments(times)]/ Attempts(times): On the calling
[TCH Assignment party side, measure the number
Attempts(times)] of Assignment Request
messages at measurement point
2 shown in IStep 1Figure 1.1.
Successful TCH
Assignments(times): On the
calling party side, measure the
number of Assignment
Complete messages at
measurement point 3 shown in
− GSM MT Call
Call Success [GSM Successful GSM Call Attempts(times): MSC Pool, MSC
Rate(%) Call(times)]/[GSM Call On the called party side,
Attempts(times)] measure the number of
Paging Response messages
at measurement point 1
shown in IStep 1Figure 1.2.
GSM Successful Call(times):
Measure the number of
Alerting messages received
by the MSC from the
terminating BSC (at
Average Call [GSM Call Setup GSM Call Setup Duration: On MSC Pool, MSC
Connection Delay(s) Duration]/[GSM the called party side,
Successful Call(times)] measure the number of
Alerting messages at
measurement point 4 shown
in IStep 1Figure 1.2.
GSM Successful Call(times):
On the called party side,
measure the total interval
between Paging Response
messages and Alerting
messages from measurement
point 1 to measurement 4
shown in IStep 1Figure 1.2.
(ALOC)Average [GSM Call Answered GSM Call Answered MSC Pool, MSC
Answered Call Duration]/[GSM Answered Duration: On the called party
Duration(s) Call(times)] side, measure the total
duration from the time when
the called party sends the
Connect Ack message (at
measurement point 8 shown
in IStep 1Figure 1.2) and the
time when the call ends.
GSM Answered Call(times):
On the called party side,
measure the number of
Connect Ack messages at
measurement point 5 shown
in IStep 1Figure 1.2.
Seized Call Traffic [GSM Call Seized GSM Call Seized Duration: On MSC Pool, MSC
Intensity(Erl) Duration]/$CYCLE the called party side, measure
the total interval between the
time when the called party
receives the Setup message (at
measurement point 7 shown in
IStep 1Figure 1.2) and the time
when the call ends.
Answered Call [GSM Call Answered GSM Call Answered Duration: MSC Pool, MSC
Traffic Intensity(Erl) Duration]/$CYCLE On the called party side,
measure the total duration from
the time when the called party
sends the Connect Ack message
(at measurement point 8 shown
in IStep 1Figure 1.2) and the
time when the call ends.
UMTS KPI
− UMTS MO Call
Call Success Rate(%) [UMTS Successful UMTS Call Attempts(times): MSC Pool, MSC
Call(times)]/[UMTS Call On the calling party side,
Attempts(times)] measure the number of CM
Service Request messages at
measurement point 1 shown in
IStep 1Figure 1.3.
UMTS Successful Call(times):
On the calling party side,
measure the number of
Alerting messages (at
measurement point 4 shown in
IStep 1Figure 1.3) after CM
Service Request messages.
RAB Assignment [Successful RAB RAB Assignment MSC Pool, MSC
Success Rate(%) Assignments(times)]/ Attempts(times): On the
[RAB Assignment calling party side, measure the
Attempts(times)] number of RAB Assignment
Request messages at
measurement point 2 shown in
IStep 1Figure 1.3.
Successful RAB
Assignments(times): On the
calling party side, measure the
number of RAB Assignment
Response messages at
measurement point 3 shown in
IStep 1Figure 1.3.
(ASR)Call Answer [UMTS Answered UMTS Answered Call(times): MSC Pool, MSC
− UMTS MT Call
Call Success Rate(%) [UMTS Successful UMTS Call Attempts(times): MSC Pool, MSC
Call(times)]/[UMTS Call On the called party side,
Attempts(times)] measure the number of
Paging Response
messages at measurement
point 1 shown in IStep
1Figure 1.4.
UMTS Successful
Call(times): On the called
party side, measure the
number of Alerting
messages (at measurement
point 4 shown in IStep
1Figure 1.4) after Paging
Response messages.
RAB Assignment [Successful RAB Assignment MSC Pool, MSC
Success Rate(%) Assignments(times)]/ Attempts(times): On the
[Assignment called party side, measure
Attempts(times)] the number of RAB
Assignment Request
messages at measurement
point 2 shown in IStep
1Figure 1.4.
Successful RAB
Assignments(times): On
the called party side,
measure the number of
RAB Assignment
Response messages at
measurement point 3
shown in IStep 1Figure 1.4.
(ASR)Call Answer [UMTS Answered UMTS Answered MSC Pool, MSC
Rate(%) Call(times)]/[UMTS Call Call(times): On the called
Attempts(times)] party side, measure the
number of Connect Ack
messages at measurement
point 5 shown in IStep
1Figure 1.4.
UMTS Call Attempts(times):
On the called party side,
measure the number of
Paging Response
messages at measurement
point 1 shown in IStep
1Figure 1.4.
Call Drop Rate After [UMTS Call Drops After UMTS Call Drops After MSC Pool, MSC
Answer Before Answer Before Answer Before
Release(%) Release(times)]/([UMTS Release(times): Measure
Call Drops After Answer the total number of Iu
Before Release(times)]+ Release Request messages
[UMTS Call Releases after Connect Ack and
After Answer(times)]) before Disconnect at
measurement point 6
shown in IStep 1Figure 1.4.
UMTS Call Releases After
Answer(times): Measure
the number of Disconnect,
Release, Release
Complete, or Iu Release
Command messages at
measurement point 9, 10,
11 or 12 shown in IStep
1Figure 1.4 after the
terminating MSC sends
Connect Ack messages to
the calling party.
Average Call [UMTS Call Setup UMTS Successful MSC Pool, MSC
Connection Delay(s) Duration]/[UMTS Call(times): On the called
Successful Call(times)] party side, measure the
number of Alerting
messages at measurement
point 4 shown in IStep
1Figure 1.4.
UMTS Call Setup Duration:
On the called party side,
measure the total interval
between Paging Response
messages and Alerting
messages.
(ALOC)Average [UMTS Call Answered UMTS Call Answered MSC Pool, MSC
Answered Call Duration]/[UMTS Duration: On the called
Duration(s) Answered Call(times)] party side, measure the
total duration from the time
when the called party sends
the Connect Ack message
(at measurement point 8
shown in IStep 1Figure
1.4) and the time when the
call ends.
UMTS Answered
Call(times): On the called
party side, measure the
number of Connect Ack
messages at measurement
point 5 shown in IStep
1Figure 1.4.
Seized Call Traffic [UMTS Call Seized UMTS Call Seized Duration: MSC Pool, MSC
Intensity(Erl) Duration]/$CYCLE On the called party side,
measure the total interval
between the time when the
called party receives the Setup
message (at measurement
point 7 shown in IStep 1Figure
1.4) and the time when the call
ends.
Answered Call Traffic [UMTS Call Answered UMTS Call Answered MSC Pool, MSC
Intensity(Erl) Duration]/$CYCLE Duration: On the called party
side, measure the total
duration from the time when
the called party sends the
Connect Ack message (at
measurement point 8 shown in
IStep 1Figure 1.4) and the
time when the call ends.
measurement 7 shown in
IStep 1Figure 1.4.
Measurement Point
Indicator
Table 1.1 lists PIs for calculating SMS indicators.
Measurement Point
Figure 1.1 shows the measurement points for SMS Origination Success Rate.
Indicator
Table 1.1 lists PIs for calculating relevant location update indicators.
Measurement Points
Figure 1.1 shows the measurement points when a 2G subscriber (MS) moves to another
location area served by the same MSC.
Figure 1.2 shows the measurement points when a 3G subscribers (UE) moves to another
location area served by the same MSC.
Figure 1.3 shows the measurement points for IMSI Detach by the same MSC.
Indicator
Table 1.1 lists the PI for calculating handover indicators.
GSM [Successful GSM Handover- Successful GSM Handover- MSC Pool, MSC,
Handover-out out(times)]/[GSM Handover- out(times): Measure the number BSC, RNC, cell
Success Rate out Requests(times)] of Clear COMMAND messages
sent from the source MSC to the
source BTS. It is measured at
measurement point 4 shown in
IStep 1Figure 1.1.
GSM Handover-out
Requests(times): Measure the
number of HANDOVER
REQUIRED messages sent from
the source BSC to the source
MSC. It is measured at
measurement point 1 shown in
IStep 1Figure 1.1.
GSM [Successful GSM Handover- Successful GSM Handover- MSC Pool, MSC,
Handover-in in(times)]/[GSM Handover-in in(times): Measure the number of BSC, RNC, cell
Success Rate Requests(times)] HANDOVER COMPLETE
messages sent from the target
BSC to the target MSC. It is
measured at measurement point 3
shown in IStep 1Figure 1.1.
GSM Handover-in Requests(times):
Measure the number of
HANDOVER REQUEST
messages sent from the target
MSC to the target BSC. It is
measured at measurement point 2
shown in IStep 1Figure 1.1.
UMTS [Successful UMTS Handover- Successful UMTS Handover- MSC Pool, MSC,
Handover-out out(times)]/[UMTS Handover- out(times): Measure the number BSC, RNC, cell
Success Rate out Requests(times)] of IU RELEASE COMMAND
messages sent by the source MSC
to the source RNC to indicate a
successful handover. It is
measured at measurement point 2
shown in IStep 1Figure 1.2.
UMTS Handover-out
Requests(times): Measure the
number of RELOCATION
REQUIRED messages sent from
the source RNC (RNC-A) to the
source MSC (3G-MSC-A). It is
measured at measurement point 1
Measurement Point
Indicator
Table 1.1 lists the indicators for paging analysis.
CLF/REL/CALL_ONHOOK
/DISCONNECT/REL/480
messages (at measurement
point 1 shown in IStep 1Figure
1.2) to the MSCb.
Iu Interface First [Iu Interface First-time Paging Iu Interface First Paging MSC Pool, MSC,
Paging Success Response(times)]/([Iu Interface Response(times): Measure the BSC, RNC, cell,
Rate(%) Paging Failures(times)]+[Iu number of times that RNC 2 sends LAC
Interface Paging Paging Rsp messages to the MSC
Response(times)]) during first-time paging over the
Iu interface.
Iu Interface [Iu Interface User Paging Iu Interface User Paging MSC Pool, MSC,
Average User Response Delay(ms)]/[Iu Response Delay(ms): Measure BSC, RNC, cell,
Paging Response Interface Paging the interval between the first LAC
Delay(ms) Response(times)] Paging message and the
Paging Rsp message.
Iu Interface Paging
Response(times): Measure the
total number of times that RNC
2 sends Paging Rsp messages
to the MSC.
Measurement Point
Figure 1.1 and Figure 1.2 shows the measurement points for A Interface Paging Success
Rate.
Indicators
User Connected [User Connected User Connected Call(times): Measure the MSC
Call Rate(%) Call(times)]/[Call number of ACM, ANM or CON messages
Attempts(times)] (measurement point 2 for ACM,
measurement point 3 for ANM, and
measurement point 6 for CON). These
measurement points are shown in IStep
1Figure 1.1.
Call Attempts(times): Measure the number of
IAM messages at measurement point 1
shown in IStep 1Figure 1.1.
(ASR)Call ([Answered Answered Call(times): Measure the number MSC
Answer Rate(%) Call(times)]+ of ANM messages at measurement point 3
[Direct Answer shown in IStep 1Figure 1.1.
Times])/[/Call Direct Answer Times: Measure the number of
Attempts(times)] CON messages at measurement point 6
shown in IStep 1Figure 1.1.
Call Attempts(times): Measure the number of
IAM messages at measurement point 1
shown in IStep 1Figure 1.1.
(ACD)Average [Call Seized Call Seized Duration: Measure the time MSC
Seized Call Duration]/[Call length between the IAM message and the
Duration(s) Attempts(times)] RLC message, that is, from measurement
point 1 to measurement point 5 shown in
IStep 1Figure 1.1.
Call Attempts(times): Measure the number of
IAM messages at measurement point 1
shown in IStep 1Figure 1.1.
(ALOC)Average [Call Answered Call Answered Duration: Measure the time MSC
Answered Call Duration]/ length between the ANM message and the
Measurement Point
Figure 1.1 shows the measurement points.
Calculation Formulas
User Connected [User Connected User Connected Call(times): Measure the MSC
Call Rate(%) Call(times)]/[Call number of 180 RINGING or INVITE 200
Attempts(times)] OK messages (measurement point 2 for
180 RINGING, measurement point 3 for
INVITE 200 OK). These measurement
points are shown in IStep 1Figure 1.1.
Call Attempts(times): Measure the number
of INVITE messages at measurement point
1 shown in IStep 1Figure 1.1.
(ASR)Call ([Answered Call]+ Answered Call(times): Measure the number MSC
Answer [Direct Call of calls during which the INVITE 200 OK
Rate(%) Answers(times)])/ message and the 180 RINGING message
[Call are found at measurement point 3 shown in
Attempts(times)] IStep 1Figure 1.1.
Direct Call Answers(times): Measure the
number of calls during which the INVITE
200 OK message is found but the 180
RINGING message is not found at
measurement point 3 shown in IStep
1Figure 1.1.
Call Attempts(times): Measure the number
of INVITE messages at measurement point
1 shown in IStep 1Figure 1.1.
(ACD)Average [Call Seized Call Seized Duration: Measure the time MSC
Seized Call Duration]/[Call length between the INVITE message and
Duration(s) Attempts(times)] the BYE 200 OK message, that is, from
measurement point 1 to measurement point
6 shown in IStep 1Figure 1.1.
Call Attempts(times): Measure the number
of INVITE messages at measurement point
1 shown in IStep 1Figure 1.1.
(ALOC)Averag [Call Answered Call Answered Duration: Measure the time MSC
e Answered Call Duration]/ length between the INVITE 200 OK
Duration [Answered message and the BYE 200 OK message,
Call(times)] that is, from measurement point 3 to
measurement point 6 shown in IStep
1Figure 1.1.
Answered Call(times): Measure the number
of calls during which the INVITE 200 OK
message and the 180 RINGING message
are found at measurement point 3 shown in
IStep 1Figure 1.1.
Seized Call [Call Seized Call Seized Duration: Measure the time length MSC
Measurement Point
Figure 1.1 shows the measurement points.
Indicator
Table 1.1 lists the CS network KPIs for network performance monitoring.
Measurement Points
Gb/Iu-PS SGSN
Gn/Gp GGSN
S1-MME MME
S4/S11 SGW
The KQIs/KPIs of NEs contain only signaling-plane KPIs and measured on their corresponding NEs.
The KQIs/KPIs in the SEQ Analyst are calculated based on the data collected from inter-NE interfaces
and counters measured at measurement points. The KQIs/KPIs of NEs are different from those of the
SEQ Analyst due to different measurement points of the NEs and SEQ Analyst.
The KQIs/KPIs of NEs are different from those of the SEQ Analyst because the following KQI/KPI
measurement methods of the NEs and SEQ Analyst are different:
NE messages: Number of requests = Number of successes + Number of Rejects (number of failures
for all causes)
SEQ Analyst messages: Number of requests = Number of successes + Number of failures (number
of failures for standard SM causes + Number of failures for 996 User Detach + Number of failures
for 997 Iu connection Release + Number of failures without causes)
Failure causes 996 and 997 are customized in the SEQ Analyst. For details, see the protocol description
information.
996: Measure that the service fails upon receiving the detach request.
996: Measure that the service fails upon receiving Iu release request or Iu release command.
Typically, the low activation success rate and low attach success rate on the Iu-PS or S1-MME interface
are related to these two causes. That is, the failures caused by non-SM causes are not used in calculating
the number of failures on NEs.
Indicator
Table 1.1 lists the PIs for indicators related to PS attach processes. To collect the required
data, the NetProbe3010 must be deployed.
Measurement Point
Figure 1.1 shows the measurement points of GPRS attach process.
Indicator
Table 1.1 lists the PIs for RAU indicators. The NetProbe3010 probe servers must be deployed
at the data collection interfaces.
Measurement Point
RAU includes intra-SGSN RAU and inter-SGSN RAU. This section describes the inter-SGSN
RAU process, as shown in Figure 1.1.
Indicator
Table 1.1 lists the PIs for PDP indicators. The NetProbe3010 probe servers must be deployed
at the data collection interfaces.
Iu mode PDP [PDP Activation PDP Activation Success Times: Iu-PS 3G service
Activation Success Times]/ Measure the number of Activate area, RNC,
Success Rate [PDP Activation PDP context Accept messages at SGSN, SGSN
(%) Requests] measurement point 2 shown in Pool
IStep 1Figure 1.1.
PDP Activation Requests: Measure
the number of Activate PDP
context Request messages at
measurement point 1 shown in
IStep 1Figure 1.1.
Iu mode PDP [PDP Activation PDP Activation Delay: Measure the Iu-PS 3G service
Activation Delay]/[PDP interval between the Activate PDP area, RNC,
Delay Activation Success context Request message and the SGSN, SGSN
Times] Activate PDP context Accept Pool
message at measurement points 1
and 2 shown in IStep 1Figure 1.1.
PDP Activation Success Times:
Measure the number of Activate
PDP context Accept messages at
measurement point 2 shown in
IStep 1Figure 1.1.
Iu mode PDP [PDP Modification PDP Modification Success Times: Iu-PS 3G service
Modification Success Times]/ Measure the number of Modify area, RNC,
Success Rate [PDP Modification PDP Context Response messages SGSN, SGSN
(%) Requests] at measurement point 2 shown in Pool
IStep 1Figure 1.2.
PDP Modification Requests:
Measure the number of Modify
PDP Context Request messages
at measurement point 1 shown in
Measurement Point
Interface-Specific PDP Context Activation Processes
Figure 1.1 shows the PDP context activation procedure initiated by an MS over the Iu
interface.
Indicator
Table 1.1 lists the PIs for service request indicators. To analyze service request indicators, you
need to deploy NetProbe3010 probes on Iu-PS interface to collect the related data.
Service [Service Request Service Requests: Measure the number of 3G service area,
Request Successes]/[Service Service Request messages at RNC, SGSN,
Success Rate Requests] measurement point 1 shown in IStep SGSN Pool
(%) 1Figure 1.1.
Service Request Successes: Measure the
number of Service Accept messages at
measurement point 2 shown in IStep
1Figure 1.1.
Service [Service Request Service Requests with Service Type 3G service area,
Request Success Times with Signaling: Measure the number of RNC, SGSN,
Success Rate Service Type Signaling]/ Service Request messages at SGSN Pool
with Service [Service Requests with measurement point 1 shown in IStep
Type Data Success Times with Service Accept message at measurement SGSN Pool
Service Type Data] points 1 and 2 shown in IStep 1Figure
1.1.
Service Request Success Times with
Service Type Data: Measure the number
of Service Accept messages at
measurement point 2 shown in IStep
1Figure 1.1.
Service [Service Request Delay Service Request Delay with Service Type 3G service area,
Request Delay with Service Type Paging Response: Measure the interval RNC, SGSN,
with Service Paging Response]/ between the Service Request message SGSN Pool
Type Paging [Service Request and the Service Accept message at
Response Success Times with measurement points 1 and 2 shown in
Service Type Paging IStep 1Figure 1.1.
Response] Service Request Success Times with
Service Type Paging Response: Measure
the number of Service Accept messages
at measurement point 2 shown in IStep
1Figure 1.1.
Measurement Points
Figure 1.1 shows the measurement points.
Indicator
Table 1.1 lists the PIs for RAB setup, modification, and release indicators. To analyze RAB
indicator-related KPIs, you need to deploy NetProbe3010 probes on Iu-PS interface to collect
RAB indicator-related data.
RAB Setup [RAB Setup Delay]/ RAB Setup Delay: Measure 3G service
Delay [RAB Setup Success the length of time between area, RNC,
Times] measurement point 1 and SGSN, SGSN
measurement point 2 shown Pool
in IStep 1Figure 1.1.
RAB Setup Success Times:
Measure the number of
RAB ASSIGNMENT
RESPONSE messages at
measurement point 2 shown
in IStep 1Figure 1.1.
RAB Setup [RAB Setup Success RAB Setup Requests: 3G service
Success Times]/[RAB Setup Measure the number of area, RNC,
Rate Requests] RAB ASSIGNMENT SGSN, SGSN
REQUEST messages at Pool
measurement point 1 shown
in IStep 1Figure 1.1.
RAB Setup Success Times:
Measure the number of
RAB ASSIGNMENT
RESPONSE messages at
measurement point 2 shown
in IStep 1Figure 1.1.
Measurement Points
Figure 1.1 shows the measurement points.
Indicator
Table 1.1 lists the KPIs for Iu-PS interface indicators. To analyze Iu-PS interface KPIs, you
need to deploy NetProbe3010 probes on the Iu-PS interface to collect related data.
1.1.
Iu mode PS Paging PS Paging Delay: Measure Iu-PS 3G service
PS Delay/PS Paging the interval between the area, RNC,
Paging Success Times Paging message and SGSN,
Delay Service Request message SGSN Pool
in a successful Iu mode PS
Paging procedure in a
specified period in IStep
1Figure 1.1.
PS Paging Success Times:
Measure the number of
Service Request messages
at measurement point 2
shown in IStep 1Figure
1.1.
Measurement Point
Figure 1.1 shows the measurement points of Iu mode PS Paging.
2.3 Gb Interface
2.3.1 Attach Indicators
Definition
Attach indicators include GPRS attach, combined GPRS/IMSI attach, and other indicators.
Before accessing a packet switched (PS) network, a mobile station (MS) must send an attach
request to the serving GPRS support node (SGSN) to register with the PS network.
Indicator
Table 1.1 lists the PIs for indicators related to PS attach processes. To collect the required
data, the NetProbe3010 must be deployed.
1.1.
Measurement Point
This section describes the attach process, and measurement points of related KPIs. Figure 1.1
shows the measurement points of the attach process.
Indicator
Table 1.1 lists the PIs for RAU indicators. The NetProbe3010 probe servers must be deployed
at the data collection interfaces.
Measurement Point
RAU includes intra-SGSN RAU and inter-SGSN RAU. This section describes the inter-SGSN
RAU process, as shown in Figure 1.1.
Indicator
Table 1.1 lists the PIs for PDP indicators. The NetProbe3010 probe servers must be deployed
at the data collection interfaces.
1.1.
Gb mode PDP [PDP Modification PDP Modification Success Gb 2G cell, BSC,
Modification Success Times]/ Times: Measure the SGSN, SGSN
Success Rate (%) [PDP Modification number of Modify PDP Pool
Requests] Context Response
messages at measurement
point 2 shown in IStep
1Figure 1.2.
PDP Modification
Requests: Measure the
number of Modify PDP
Context Request
messages at measurement
point 1 shown in IStep
1Figure 1.2.
Gb mode PDP [PDP Modification PDP Modification Delay: Gb 2G cell, BSC,
Modification Delay]/[PDP Measure the interval SGSN, SGSN
Delay Modification between the Modify PDP Pool
Success Times] Context Request message
and the Modify PDP
Context Response
message. It indicates the
interval between
measurement points 1 and
2 shown in IStep 1Figure
1.2.
PDP Modification Success
Times: Measure the
number of Modify PDP
Context Response
messages at measurement
point 2 shown in IStep
1Figure 1.2.
Measurement Point
Interface-Specific PDP Context Activation Processes
Figure 1.1 shows the PDP context activation procedure initiated by a mobile station (MS)
over the Gb interface.
2.3.4 Paging - Gb
Definition
Gb interface indicators measure the success rates and delays during PS paging between
subscribers over the Gb interface. Carriers can properly readjust these KPIs to improve
network performance.
Indicator
Table 1.1 lists the KPIs for Gb interface indicators. To analyze Gb interface KPIs, you need to
deploy NetProbe3010 probes on the Gb interface to collect related data.
Measurement Point
Figure 1.1 shows the measurement points of Gb mode PS Paging.
Indicator
Table 1.1 lists the KPIs for the PDP process. To analyze Gn/Gp interface KPIs, you need to
deploy NetProbe3010 probes on the Gn/Gp interface to collect related data.
Create PDP [Success Times of Create PDP Context Gn/Gp SGSN, GGSN
Context Create PDP Procedures: Measure the
Procedure Context number of Create PDP
Success Rate Procedure]/ Context Request messages at
(%) [Create PDP measurement point 1 shown in
Context IStep 1Figure 1.1.
Procedures] Success Times of Create PDP
Measurement Points
Figure 1.1 shows the measurement points.
Indicator
Table 1.1 lists the PIs for E-RAB indicators.
E-RAB Setup [E-RAB Setup Success Times]/ E-RAB Setup Success 4G cell, eNodeB,
Success Rate (%) [E-RAB Setup Requests] Times: Measure the total MME, MME Pool
number of E-RAB
Setup Response
messages indicating
successful E-RAB setup.
It is counted at
measurement point 2 in
IStep 1Figure 1.1.
E-RAB Setup Requests:
Measure the total
number of E-RAB
Setup Request messages
in a specified period. It is
counted at measurement
point 1 in IStep 1Figure
1.1.
E-RAB Setup Delay [E-RAB Setup Delay]/[E-RAB E-RAB Setup Delay: 4G cell, eNodeB,
Setup Success Times] Measure the total delay MME, MME Pool
from E-RAB Setup
Request messages to E-
RAB Setup Response
messages for successful
E-RAB setup in a
specified period. It is
counted at measurement
points 1 and 2 in IStep
1Figure 1.1.
E-RAB Setup Success
Times: Measure the total
number of E-RAB
Setup Response
messages indicating
successful E-RAB setup.
It is counted at
measurement point 2 in
IStep 1Figure 1.1.
Measurement Point
Figure 1.1 show the measurement points of E-RAB setup.
Indicator
Table 1.1 lists the PIs for tracking area update indicators.
Normal TAU Success [Normal TAU Success Times]/ Normal TAU Success 4G cell, eNodeB,
Rate (%) [Normal TAU Requests] Times: Measure the total MME, MME Pool
number of TAU
Complete messages
indicating successful
tracking area update in a
specified period. It is
counted at measurement
point 2 in IStep 1Figure
1.1 when Update Type
is set to TA updating.
Normal TAU Requests:
Measure the total
number of TAU
Request messages in a
specified period. It is
counted at measurement
point 1 in IStep 1Figure
1.1 when Update Type
is set to TA updating.
Normal TAU Delay [Normal TAU Delay]/[Normal Normal TAU Delay: 4G cell, eNodeB,
TAU Success Times] Measure the total delay MME, MME Pool
from the TAU Request
messages to the TAU
Complete messages for
successful tracking area
update in a specified
period. It is counted at
measurement points 1
and 2 in IStep 1Figure
1.1 when Update Type
is set to TA updating.
Normal TAU Success
Times: Measure the total
number of TAU
Complete messages
indicating successful
tracking area update in a
specified period. It is
counted at measurement
point 2 in IStep 1Figure
1.1 when Update Type
is set to TA updating.
Periodic TAU Success [Periodic TAU Success Periodic TAU Success 4G cell, eNodeB,
Rate (%) Times]/[Periodic TAU Times: Measure the total MME, MME Pool
Requests] number of TAU
Complete messages
indicating successful
tracking area update in a
specified period. It is
counted at measurement
point 2 in IStep 1Figure
1.1 when Update Type
is set to periodic
updating.
Periodic TAU Requests:
Measure the total
number of TAU
Request messages in a
specified period. It is
counted at measurement
point 1 in IStep 1Figure
1.1 when Update Type
is set to TA updating.
Periodic TAU Delay [Periodic TAU Delay]/ Periodic TAU Delay: 4G cell, eNodeB,
[Periodic TAU Success Times] Measure the total delay MME, MME Pool
from the TAU Request
messages to the TAU
Complete messages for
successful tracking area
update in a specified
period. It is counted at
measurement points 1
and 2 shown in IStep
1Figure 1.1 when
Update Type is set to
periodic updating.
Periodic TAU Success
Times: Measure the total
number of TAU
Complete messages
indicating successful
tracking area update in a
specified period. It is
counted at measurement
point 2 in IStep 1Figure
1.1 when Update Type
is set to periodic
updating.
Combined TA/LA [Combined TA/LA Updating Combined TA/LA 4G cell, eNodeB,
Updating Success Rate Success Times]/[Combined Updating Success MME, MME Pool
(%) TA/LA Updating Requests] Times: Measure the
number of the TAU
Complete messages
indicating successful
combined TA/LA update
in a specified period. It
is counted at
measurement point 2 in
IStep 1Figure 1.1 when
Measurement Point
Figure 1.1 shows the measurement points of tracking area update KPIs.
Figure 1.1 Measurement points of normal TAU and periodic TAU KPIs
Indicator
Table 1.1 lists the KPIs for S1-MME interface indicators. To analyze S1-MME interface KPIs,
you need to deploy NetProbe3010 probes on the S1-MME interface to collect related data.
Measurement Point
Figure 1.1 shows the measurement points of S1-MME PS Paging.
Indicator
Table 1.1 lists the PIs for S1-MME attach indicators.
S1-MME Attach [S1-MME Attach Success S1-MME Attach Success 4G cell, eNodeB,
Success Rate (%) Times]/[S1-MME Attach Times: Measure the total MME, MME Pool
Requests] number of Attach
Complete messages
indicating successful
attach at measurement
point 2 shown in IStep
1Figure 1.1.
S1-MME Attach Requests:
Measure the total number
of Attach Request
messages at measurement
point 1 shown in IStep
1Figure 1.1.
S1-MME Attach [S1-MME Attach Delay]/ S1-MME Attach Delay: 4G cell, eNodeB,
Delay [S1-MME Attach Success Measure the total delay MME, MME Pool
Times] from the Attach Request
messages to the Attach
Complete messages for
successful attach in a
specified period. It is
counted at measurement
points 1 and 2 in IStep
1Figure 1.1.
S1-MME Attach Success
Times: Measure the total
number of Attach
Complete messages
indicating successful
attach in a specified
period. It is counted at
measurement point 2 in
IStep 1Figure 1.1.
S1-MME EPS Attach [S1-MME EPS Attach S1-MME EPS Attach 4G cell, eNodeB,
Success Rate (%) Success Times]/[S1-MME Success Times: Measure MME, MME Pool
EPS Attach Requests] the total number of
Attach Complete
messages indicating
successful attach in a
specified period. It is
counted at measurement
point 2 in IStep 1Figure
1.1.
S1-MME EPS Attach
Requests: Measure the
total number of Attach
Request messages in a
specified period. It is
counted at measurement
point 1 in IStep 1Figure
1.1.
S1-MME EPS Attach [S1-MME EPS Attach S1-MME EPS Attach 4G cell, eNodeB,
Delay Delay]/[S1-MME EPS Delay: Measure the total MME, MME Pool
Attach Success Times] delay from the Attach
Request messages to the
Attach Complete
messages for successful
attach in a specified
period. It is counted at
measurement points 1 and
2 in IStep 1Figure 1.1.
S1-MME EPS Attach
Success Times: Measure
Measurement Point
Figure 1.1 shows the measurement points of S1-MME attach KPIs.
Indicator
Table 1.1 lists the PIs for S1-MME service request indicators.
number of Initial
Context Setup
Complete messages
indicating successful
S1-MME service
request in a specified
period. It is counted at
measurement point 2 in
IStep 1Figure 1.1.
S1-MME Service
Requests: Measure the
total number of
NAS:Service Request
messages in a specified
period. It is counted at
measurement point 1 in
IStep 1Figure 1.1.
S1-MME Service [S1-MME Service Request S1-MME Service 4G cell, eNodeB,
Request Delay Delay]/[S1-MME Service Request Delay: Measure MME, MME Pool
Request Success Times] the total delay from the
NAS:Service Request
messages to the Initial
Context Setup Complete
messages for successful
S1-MME service
request in a specified
period. It is counted at
measurement points 1
and 2 in IStep 1Figure
1.1.
S1-MME Service
Request Success Times:
Measure the total
number of Initial
Context Setup
Complete messages
indicating successful
S1-MME service
request in a specified
period. It is counted at
measurement point 2 in
IStep 1Figure 1.1.
Measurement Point
Figure 1.1 shows the measurement points of S1-MME service request KPIs.
Indicator
Table 1.1 lists the PIs for UE requested PDN connection indicators.
messages indicating
successful UE requested
PDN connection setup in
a specified period. It is
counted at measurement
point 2 in IStep 1Figure
1.1.
UE Requested PDN
Connectivity Requests:
Measure the total
number of PDN
Connectivity Request
messages in a specified
period. It is counted at
measurement point 1 in
IStep 1Figure 1.1.
UE Requested PDN [UE Requested PDN UE Requested PDN 4G cell, eNodeB,
Connectivity Delay Connectivity Delay]/[UE Connectivity Delay: MME, MME Pool
Requested PDN Measure the total delay
Connectivity Success from the PDN
Times] Connectivity Request
messages to the Activate
Default EPS Bearer
Context Request/PDN
Connectivity Accept
messages for successful
UE requested PDN
connection setup in a
specified period. It is
counted at measurement
points 1 and 2 in IStep
1Figure 1.1.
UE Requested PDN
Connectivity Success
Times: Measure the total
number of Activate
Default EPS Bearer
Context Request/PDN
Connectivity Accept
messages indicating
successful UE requested
PDN connection setup in
a specified period. It is
counted at measurement
point 2 in IStep 1Figure
1.1.
Measurement Point
Figure 1.1 shows the measurement points of UE requested PDN connection KPIs.
2.5.7 Handover
Definition
By analyzing handover and path switch processes, you can obtain the average success rates
and average delays of handover and path switch. Based on these indicators, you can obtain
handover information. By improving the handover related KPIs, you can optimize the
network performance.
The NetProbe3010 is used to collect raw signaling data from an LTE network.
Indicator
Table 1.1 lists the PIs for handover indicators.
Measurement Point
Figure 1.1 and Figure 1.2 show the measurement points of handover request, path switch
KPIs respectively.
Indicator
Table 1.1 lists relevant session creation indicators.
at measurement point 2
shown in IStep 1Figure
1.1.
The name of a KPI varies depending on the area for which the KPI is calculated. Create Session
Success Rate is used as an example here. The mapping between areas and specific KPI names is as
follows:
SGW: S4/S11 Create Session Success Rate
SGSN: S4 Create Session Success Rate
MME: S11 Create Session Success Rate
Measurement Point
The service flow of S4-interface KPIs and that of S11-interface KPIs are similar. The measurement
points of S11-interface KPIs are described in this section as an example. The difference between the two
interfaces is that the S4 interface is the interface between the S4-SGSN and the SGW, the S11 interface
is the interface between the MME and the SGW.
Figure 1.1 shows the measurement points for S11 Session Creation indicators.
average success rate of S4/S11 interface dedicated bearer creation and the average delay from
initiating a dedicated bearer creation request to receiving the message indicating that the
dedicated bearer has been created successfully. Based on these indicators, you can obtain the
running status of the evolved packet system (EPS) and the response speed of relevant network
devices. This provides data for system adjustment and expansion. By adjusting the KPIs
related to default bearer creation, you can optimize the network performance and hardware to
improve the response speed of the system and user satisfaction.
The NetProbe3010 is used to collect raw signaling data from an LTE network.
Indicator
Table 1.1 lists relevant bearer creation indicators.
The name of a KPI varies depending on the area for which the KPI is calculated. Create Bearer Success
Rate is used as an example here. The mapping between areas and specific KPI names is as follows:
SGW: S4/S11 Create Bearer Success Rate
SGSN: S4 Create Bearer Success Rate
MME: S11 Create Bearer Success Rate
Measurement Point
The service flow of S4-interface KPIs and that of S11-interface KPIs are similar. The measurement
points of S11-interface KPIs are described in this section as an example. The difference between the two
interfaces is that the S4 interface is the interface between the S4-SGSN and the SGW, the S11 interface
is the interface between the MME and the SGW.
Figure 1.1 shows the measurement points for Bearer Creation indicators.
provides data for system adjustment and expansion. By adjusting the KPIs related to default
bearer creation, you can optimize the network performance and hardware to improve the
response speed of the system and user satisfaction.
The NetProbe3010 is used to collect raw signaling data from an LTE network.
Indicator
Table 1.1 lists relevant bearer update indicators.
Measurement Point
The service flow of S4-interface KPIs and that of S11-interface KPIs are similar. The measurement
points of S11-interface KPIs are described in this section as an example. The difference between the two
interfaces is that the S4 interface is the interface between the S4-SGSN and the SGW, the S11 interface
is the interface between the MME and the SGW.
Figure 1.1 shows the measurement points for Bearer Update indicators.
DNS Query [First DNS Query First DNS Query Gn, NetProbe3010 Entire
Success Rate Successes(MS)]/ Successes(MS): Measure S1-U, network,
[First DNS Query the accumulative number S5/S8 DNS
Requests(MS)] of DNS Response server
messages at measurement
Measurement Point
Figure 1.1 shows the measurement points of DNS indicators in a PS web service flow.
Figure 1.2 shows the measurement points of DNS indicators in an EPC web service flow.
Figure 1.2 Measurement points of DNS indicators in an EPC web service flow
PAYLOAD between
measurement point 8 and
measurement point 10 shown
in IStep 1Figure 1.1.
Downlink [Downlink Downlink Out-of-Order: In the Gn, NetProbe3010 SGSN,
TCP Out-of- TCP Out-of- downlink process, measure the S1-U, SGW,
Order Rate Order number of the out-of-order S5/S8 PGW,
Packets]/ TCP DATA messages between GGSN
[Downlink measurement point 5 and BSC,
Packets] measurement point 7 shown in RNC,
IStep 1Figure 1.1. eNodeB
TCP Downlink Packets (with
Payload): Measure all the
downlink packets with
PAYLOAD at measurement
point 5 and measurement point
7 shown in IStep 1Figure 1.1.
Server Side [Uplink Total Uplink Total RTT: Measure the Gn, NetProbe3010 SGSN,
Round Trip RTT]/[Uplink amount of time between S1-U, SGW,
Time RTT Times] measurement points 8 and 9 S5/S8 PGW,
shown in IStep 1Figure 1.1. GGSN
Uplink RTT Times: Measure the BSC,
number of uplink total RTTs at RNC,
measurement point 10 shown eNodeB
in IStep 1Figure 1.1.
Client Side [Downlink Downlink Total RTT: Measure Gn, NetProbe3010 SGSN,
Round Trip Total RTT]/ the amount of time between 5 S1-U, SGW,
Time [Downlink and 6 shown in IStep 1Figure S5/S8 PGW,
RTT Times] 1.1. GGSN
Downlink RTT Times: Measure BSC,
the number of downlink total RNC,
RTTs at measurement point 7 eNodeB
shown in IStep 1Figure 1.1.
Measurement Points
Figure 1.1 and Figure 1.2 show the measurement points for TCP Indicators.
Traffic indicators measure the traffic on Layer 4, which includes user-plane traffic on the IP layer but
does not include traffic on the GTP layer.
Total Packets [Uplink Packets] - Gn, Gp, S1-U, NetProbe For details, see
+[Downlink S5/S8 3010 Table 2.2.
Packets]
Total [Uplink Traffic]+ - Gn, Gp, S1-U, NetProbe For details, see
Traffic(MB) [Downlink S5/S8 3010 Table 2.2.
Traffic]
Uplink [Uplink Traffic] Uplink Traffic: Gn, Gp, S1-U, NetProbe For details, see
Traffic(MB) Measure the traffic S5/S8 3010 Table 2.2.
between measurement
points 8 and 10 in IStep
1Figure 1.1.
Downlink [Downlink Downlink Traffic: Gn, Gp, S1-U, NetProbe For details, see
Traffic(MB) Traffic] Measure the traffic S5/S8 3010 Table 2.2.
between measurement
points 5 and 7 in IStep
1Figure 1.1.
Uplink [Uplink Packets] Uplink Packets: Gn, Gp, S1-U, NetProbe For details, see
Packets Measure the number of S5/S8 3010 Table 2.2.
all data packets sent
from the UE in the
service procedure in
IStep 1Figure 1.1.
Downlink [Downlink Downlink Packets: Gn, Gp, S1-U, NetProbe For details, see
Packets Packets] Measure the number of S5/S8 3010 Table 2.2.
all data packets
received by the UE in
the service procedure in
IStep 1Figure 1.1.
Total -
SGSN, SGW, PGW, GGSN
Location BSC, RNC, eNodeB
2G Cell, 3G Service Area, 4G Cell
APN APN
Protocol Protocol Category, Protocol
Subscriber TOP N
Device Brand
Device Model
Device Device Technology
Device Type
Device OS
Website TOP N
Access Type 2G, 3G, 4G
Measurement Points
Figure 1.1 and Figure 1.2 shows the measurement points for traffic KQIs/KPIs.
Indicator
lists the PS network KPIs for network performance monitoring.
Table 1.2 lists the indicators for EPC network performance monitoring.
Request
messages
measured in a
specified period
of time.
Measure the
number of
point 1 shown
in Figure
#cn_98_fm_02
0001/fig_01.
S11 [S11 Dedicated S11 Dedicated S11 NetProbe30 MME Pool,
Dedicate Bearer Creation Bearer Creation 10 State
d Bearer Success Times]/ Success
Creation [S11 Dedicated Counts:
Success Bearer Creation Indicates the
Rate (%) Requests] number of
Create Bearer
Response
messages that
carry a success
indicator
measured in a
specified period
of time.
Measure the
number of
point 2 shown
in Figure IStep
1Figure 1.1.
S11 Dedicated
Bearer Creation
Requests:
Indicates the
number of
Create Bearer
Request
messages
measured in a
specified period
of time.
Measure the
number of
point 1 shown
in Figure IStep
1Figure 1.1.
specified period
of time.
Measure the
number of
point 2 shown
in Figure IStep
1Figure 1.2.
S5/S8 Dedicated
Bearer Creation
Requests:
Indicates the
number of
Create Bearer
Request
messages
measured in a
specified period
of time.
Measure the
number of
point 1 shown
in Figure IStep
1Figure 1.2.
S1- [S1-MME Attach S1-MME Attach S1- NetProbe30 eNodeB,
MME Success Times]/ Success Times: MME 10 MME Pool,
Attach [S1-MME Attach Indicates the State
Success Requests] number of
Rate (%) Attach
Complete
messages that
carry a success
indicator
measured in a
specified period
of time when
the Attach
Type is EPS
Attach,
Combined
EPS/IMSI
Attach, or
Emergency
Attach.
Measure the
number of
point 2 shown
in Figure IStep
1Figure 1.3.
S1-MME Attach
Requests:
Indicates the
number of
Attach
Request
messages
measured in a
specified period
of time when
the Attach
Type is EPS
Attach,
Combined
EPS/IMSI
Attach, or
Emergency
Attach.
Measure the
number of
point 1 shown
in Figure IStep
1Figure 1.3.
UE [UE Requested UE Requested S1- NetProbe30 eNodeB,
Requeste PDN Connectivity PDN MME 10 MME Pool,
d PDN Success Times]/ Connectivity State
Connecti [UE Requested Success Times:
vity PDN Connectivity Indicates the
Success Requests] number of
Rate (%) Activate
Default EPS
Bearer
Context
Request/PDN
Connectivity
Accept
messages that
carry a success
indicator
measured in a
specified period
of time.
Measure the
number of
point 2 shown
in Figure
#cn_98_fm_02
0001/fig_06.
UE Requested
PDN
Connectivity
Requests:
Indicates the
number of
PDN
Connectivity
Request
messages
measured in a
specified period
of time.
Measure the
number of
point 1 shown
in Figure
#cn_98_fm_02
0001/fig_06.
S1- [S1-MME Service S1-MME S1- NetProbe30 eNodeB,
MME Request Success Service MME 10 MME Pool,
Service Times]/[S1-MME Request State
Request Service Requests] Success Times:
Success Indicates the
Rate (%) number of
Initial Context
Setup
Complete
messages that
carry a success
indicator
measured in a
specified period
of time.
Measure the
number of
point 2 shown
in Figure
#cn_98_fm_02
0001/fig_07.
S1-MME
Service
Requests:
Indicates the
number of
NAS:Service
Request
messages
measured in a
specified period
of time.
Measure the
number of
point 1 shown
in Figure
#cn_98_fm_02
0001/fig_07.
TAU [TAU Success TAU Success S1- NetProbe30 eNodeB,
Success Times]/[TAU Times: MME 10 MME Pool,
Rate (%) Requests] Indicates the State
number of TAU
Complete
messages that
carry a success
indicator
measured in a
specified period
of time when
Update Type is
periodic
updating.
Measure the
number of
point 2 shown
in Figure
#cn_98_fm_02
0001/fig_08.
TAU Requests:
Indicates the
number of TAU
Request
messages
measured in a
specified period
of time when
Update Type is
periodic
updating.
Measure the
number of
point 1 shown
in Figure
#cn_98_fm_02
0001/fig_08.
Measurement Points
IStep 1Figure 1.1, Figure 1.2, Figure 1.3, Figure 1.4 shows the measurement points.
Figure 1.5, Figure 1.6, Figure 1.7, Figure 1.8, Figure 1.9 shows the measurement points.
Indicator
Table 1.1 lists the PIs for traffic monitoring indicators.
1Figure 1.1.
NOTE
For detailed error code
description, see Failure
Cause Configuration.
between the
outgoing ANM and
the REL messages,
that is, from
measurement point 3
to measurement
point 4 shown in
IStep 1Figure 1.1.
Incoming [Incoming Incoming ANM Nc NetProbe9 Trunk
ALOC Conversation Count: Measures the 000 Group
Duration]/ number of incoming
[Incoming ANM messages at
ANM Count] measurement point 3
shown in IStep
1Figure 1.1.
Incoming
Conversation
Duration: Measures
the length of time
between the
incoming ANM and
the REL messages,
that is, from
measurement point 3
to measurement
point 4 shown in
IStep 1Figure 1.1.
Measurement Point
Figure 1.1 shows the measurement points KPIs.
Indicator
Table 1.1 lists the CS network KPIs for key area monitoring.
MT Video Call [MT Video Call MT Video Call Attempt A/Iu NetPr 3G/Cu
Attempt Counts Attempt Counts: On the calling obe90 stomiz
Counts] party side, measure the 00 ed
number of Paging Area
Response messages at
measurement point 1
shown in IStep 1Figure
1.2.
MT Video Call [MT Video Call MT Video Call Success A/Iu NetPr 3G/Cu
Success Counts Success Counts: On the calling obe90 stomiz
Counts] party side, measure the 00 ed
number of Alerting Area
message is received (at
measurement point 4
shown in IStep 1Figure
1.2) after Paging
Response messages.
Video [MT Video Call MT Video Call Success A/Iu NetPr 3G/Cu
Termination Success Counts: On the called obe90 stomiz
Call Success Counts]/[MT party side, measure 00 ed
Rate Video Call the number of Paging Area
Attempt Response messages
Counts] at measurement point
1 shown in IStep
1Figure 1.2.
MT Video Call Success
Counts: On the called
party side, measure
the number of no
Alerting message is
received (at
measurement point 4
shown in IStep
1Figure 1.2) after
Paging Response
messages.
Normal [Normal The type of events is A/Iu NetPr 2G/3G
Location Location Normal Location Update. obe90 /Custo
Update Attempt Update Attempt Normal Location 00 mized
Counts Counts] Update Success Area
Normal [Normal Counts: Measure the A/Iu NetPr 2G/3G
Location Location number of Location obe90 /Custo
Update Success Update Success updating accept 00 mized
Counts Counts] messages at Area
Measurement Point
Indicator
Table 1.1 lists the PS network KPIs for key area monitoring.
messages. It is measured at
measurement point 1 shown inIStep
1Figure 1.4.
Inter-RAU attempts in Gb mode:
Measures the number of times that
the Routing Area Update Request
messages. It is measured at
measurement point 1 shown inIStep
1Figure 1.4/
Uplink [Uplink Uplink Traffic: measures the traffic Gn NetProb
Traffic Traffic] between measurement points 7 and 9 e3010
shown inIStep 1Figure 1.6.
Downlin [Downlink Downlink Traffic: measures the traffic Gn NetProb
k Traffic Traffic] between measurement points 4 and 6 e3010
shown inIStep 1Figure 1.6.
WEB [Web Page Web Page Request Counts: Measure the Gn NetProb
Page Request number of the first HTTP GET e3010
Request Counts] messages at measurement point 9 shown
Counts in Figure 1 of Page Response Success
Rate.
WEB [Web Page Web Page Response Success Counts: Gn NetProb
Page Response Measure the number of the first HTTP e3010
Response Success Reply 200 OK messages at
Success Counts] measurement point 10 shown in Figure
Counts 1 of Page Response Delay.
WEB [Web Page Web Page Request Counts: Measure Gn NetProb
Page Response the number of the first HTTP GET e3010
Response Success messages at measurement point 9
Success Counts]/ shown in Figure 1 of Page Response
Rate (%) [Web Page Success Rate.
Requests] Web Page Response Success Counts:
Measure the number of the first
HTTP Reply 200 OK messages at
measurement point 10 shown in
Figure 1 of Page Response Delay.
WEB [Pages Pages Size: Measure the total size of Gn NetProb
Page Size]/[Page all ∑ 1n HTTP Reply DATA e3010
Downloa Download messages.
d Delay] Page Download Delay: Σ (On the
Throughp calling party side, the length of time
ut between the first HTTP GET and
the last HTTP Reply DATA n
message minus the intervals between
Measurement Points
Indicator
Table 1.1 lists the EPC network KPIs for key area monitoring.
updating.
Combined TA/LA Updating Success
Times: Indicates the number of the
TAU Complete messages in a
specified period. After a UE
performs combined EPS/IMSI
attach, if the location of a UE
changes, combined TA/LA update is
required. It is counted at
measurement point 2 in IStep
1Figure 1.4 when Update Type is
set to combined TA/LA updating.
TAU [TAU TAU Success Counts: S1- NetProb
Success Success Normal TAU Success Times: MME e3010
Rate (%) Counts]/ Indicates the total number of TAU
[TAU Complete messages in a
Request
specified period. It is measured at
Counts]
measurement point 2 in IStep
1Figure 1.4 when Update Type
is set to TA updating.
Periodic TAU Success Times:
Indicates the total number of TAU
Complete messages in a
specified period. It is counted at
measurement point 2 in IStep
1Figure 1.4 when Update Type
is set to periodic updating.
Combined TA/LA Updating
Success Times: Indicates the
number of the TAU Complete
messages in a specified period.
After a UE performs combined
EPS/IMSI attach, if the location
of a UE changes, combined
TA/LA update is required. It is
counted at measurement point 2
in IStep 1Figure 1.4 when
Update Type is set to combined
TA/LA updating.
TAU Request Counts:
Normal TAU Requests: Indicates
the total number of TAU
Request messages in a
specified period. It is measured at
measurement point 1 in IStep
WEB [Pages Pages Size: Measure the total size of S1-U NetProb
Page Size]/[Page all ∑ 1n HTTP Reply DATA e3010
Downloa Download messages.
d Delay] Page Download Delay: Σ (On the
Throughp calling party side, the length of time
ut between the first HTTP GET and
the last HTTP Reply DATA n
message minus the intervals between
different page download.)
Measurement Points
Figure 1.4 Measurement points of normal TAU and periodic TAU KPIs
Indicators
Table 1.1
Table 1.2
Table 1.3
Link Measures the number of times when the link status is NetProbe9000
Unreachable faulty in the monitored period (60s).
Count
Link Measures the duration (in seconds) when the link NetProbe9000
Unreachable status is faulty in the monitored period (60s).
Duration
TX Peak Traffic Measures the peak transmit traffic rate on a link in the NetProbe9000
Rate (%) monitored period (60s) every 5 seconds.
Peak transmit traffic rate is calculated using this
formula: Total size of messages sent in 5 seconds x
8/5.
RX Peak Measures the peak receive traffic rate on a link in the NetProbe9000
Traffic Rate monitored period (60s) every 5 seconds.
Out of Service Measures the number of times when the link status is NetProbe9000
faulty in the monitored period (60s).
TX Peak Measure the peak TX utilization of a link within the NetProbe9000
Utilization monitor period (60s). Link utilization is measured
every 5 seconds, and the highest link utilization is
recorded.
Utilization = ((N x 8)/(M x 5)) x 100%
N: total size of MSU messages within 5s; unit: byte
M: link bandwidth, which is 2 Mbps
(2*1000*1000); unit: bps
RX Peak Measure the peak RX utilization of a link within the NetProbe9000
Utilization monitor period (60s). Link utilization is measured
every 5 seconds, and the highest link utilization is
recorded.
Utilization = ((N x 8)/(M x 5)) x 100%
N: total size of MSU messages within 5s; unit: byte
M: link bandwidth, which is 2 Mbps
(2*1000*1000); unit: bps
TX Util erlang Measures the average transmit link utilization in the NetProbe9000
monitored period (60s).
Utilization = ((N x 8)/(M x 60)) x 100%
N: total size of MSU messages within 60s; unit:
byte
M: link bandwidth, which is 2 Mbps
(2*1000*1000); unit: bps
RX Util erlang Measures the average receive link utilization in the NetProbe9000
monitored period (60s).
Utilization = ((N x 8)/(M x 60)) x 100%
N: total size of MSU messages within 60s; unit:
byte
M: link bandwidth, which is 2 Mbps
(2*1000*1000); unit: bps
TX MSU Measures the number of MSU messages sent over a NetProbe9000
Messages link in the monitored period (60s).
RX MSU Measures the number of MSU messages received NetProbe9000
Messages over a link in the monitored period (60s).
TX MSU Measures the number of octets of the SIF and SIO in NetProbe9000
Octets an MSU message sent over a link.
TX MSU Measures the number of octets of the SIF and SIO in NetProbe9000
Octets an MSU message received over a link.
Indicator
Table 1.1 lists the PIs for CSFB performance analysis MO fallback indicators.
Measurement Points
Figure 1.1 show the measurement points for CSFB MO fallback KPIs.
Indicator
Table 1.1 lists the PIs for CSFB performance analysis MT fallback indicators.
(times MSC,
) TAI,
ECGI,
CGI/S
AI
MT [MT Fallback MT Fallback Success Times: SGs, NetPr Admin
Fallba Requests] - Measure the total number of S1- obe30 istrativ
ck [MT Fallback MSC receive to Location MME, 10, e
Failur Success Times] Update Request messages or A, Iu- NetPr Regio
e Paging Response messages at CS obe90 ns,
Times measurement point 2 or 3 in 00 MME,
(times IStep 1Figure 1.1. MSC,
) MT Fallback Requests: Measure TAI,
the total number of MME ECGI,
receive Extended Service CGI/S
Request messages at AI
measurement point 1 in IStep
1Figure 1.1.
MT [MT Fallback MT Fallback Delay: Measure the SGs, NetPr Admin
Avera Delay]/[MT total delay from MME receive S1- obe30 istrativ
ge Fallback Extended Service Request MME, 10, e
Fallba Success Times] messages (measurement point A, Iu- NetPr Regio
ck 1) to MSC receive to Location CS obe90 ns,
Delay( Update Request messages or 00 MME,
ms) Paging Response messages MSC,
(measurement point 2 or 3) in TAI,
IStep 1Figure 1.1. ECGI,
MT Fallback Success Times: CGI/S
Measure the total number of AI
MSC receive to Location
Update Request messages or
Paging Response messages at
measurement point 2 or 3 in
IStep 1Figure 1.1.
Measurement Points
Figure 1.1 show the measurement points for CSFB MT fallback KPIs.
Indicator
Table 1.1 lists the PIs for CSFB performance analysis MO fallback call indicators.
Measurement Points
Figure 1.1 shows the measurement points for CSFB MO fallback call KPIs.
Figure 1.2 shows the measurement points for CSFB MO fallback call KPIs on
PROGRESS announcements.
Figure 1.1 Measurement points for CSFB MO fallback call KPIs (1)
Figure 1.2 Measurement points for CSFB MO fallback call KPIs (2)
Indicator
Table 1.1 lists the PIs for CSFB performance analysis MT fallback call indicators.
Measurement Points
Figure 1.1 show the measurement points for CSFB MT fallback call KPIs.
Indicator
Table 1.1 lists the PIs for CSFB performance analysis return indicators.
Return [Return Success Return Success Times: Measure SGs, NetPr Admin
Succe Times]/[Return the total number of TAU S1- obe30 istrativ
ss Requests] Request messages the eNodeB MME, 10, e
Rate( sends to the MME at A, Iu- NetPr Regio
%) measurement point 2 in IStep CS obe90 ns,
1Figure 1.1 and IStep 1Figure 00 MME,
1.2. MSC,
Return Requests: Measure the TAI,
total number of ECGI,
CLEAR_COMMAND/IU_RE CGI/S
LEASE_COMMAND AI
messages the MSC sends to the
BSC/RNC at measurement
point 1 in IStep 1Figure 1.1
and IStep 1Figure 1.2.
Return [MOC Return Measure the total number of SGs, NetPr Admin
Reque Requests] + CLEAR_COMMAND/IU_RELE S1- obe30 istrativ
sts(tim [MTC Return ASE_COMMAND messages the MME, 10, e
es) Requests] MSC sends to the BSC/RNC at A, Iu- NetPr Regio
measurement point 1 in IStep CS obe90 ns,
1Figure 1.1 and IStep 1Figure 1.2. 00 MME,
MSC,
TAI,
ECGI,
CGI/S
AI
Return [MOC Return Measure the total number of TAU SGs, NetPr Admin
Succe Success Times] Request messages the eNodeB S1- obe30 istrativ
ss + [MTC Return sends to the MME at measurement MME, 10, e
Times Success Times] point 2 in IStep 1Figure 1.1 and A, Iu- NetPr Regio
Measurement Points
Figure 1.1 and Figure 1.2 show the measurement points for CSFB return KPIs.
Indicator
Table 1.1 lists the PIs for CSFB performance analysis paging indicators.
Pagin [Paging Success Paging Success Times: Measure SGs NetPr Admin
g Times]/[First the total number of MME send obe30 istrativ
Succe Paging Service Request messages at 10 e
ss Requests] measurement point 2 in IStep Regio
Rate( 1Figure 1.1. ns,
%) First Paging Requests: Measure MME,
the total number of MME MSC,
receive Paging Request TAI,
messages at measurement point ECGI,
1 in IStep 1Figure 1.1. CGI/S
AI
First [First Paging Measure the total number of MME SGs NetPr Admin
Pagin Requests] receive Paging Request messages obe30 istrativ
g at measurement point 1 in IStep 10 e
Reque 1Figure 1.1. Regio
sts(tim ns,
es) MME,
MSC,
TAI,
ECGI,
CGI/S
AI
Pagin [Paging Success Measure the total number of MME SGs NetPr Admin
g Times] send Service Request messages at obe30 istrativ
Succe measurement point 2 in IStep 10 e
ss 1Figure 1.1. Regio
Times ns,
(times MME,
) MSC,
TAI,
ECGI,
CGI/S
AI
Pagin [First Paging Paging Success Times: Measure SGs NetPr Admin
g Requests]– the total number of MME send obe30 istrativ
Failur [Paging Success Service Request messages at 10 e
e Times] measurement point 2 in IStep Regio
Times 1Figure 1.1. ns,
(times First Paging Requests: Measure MME,
) the total number of MME MSC,
receive Paging Request TAI,
messages at measurement point ECGI,
1 in IStep 1Figure 1.1. CGI/S
AI
Avera [Total Paging Total Paging Response Delay: SGs NetPr Admin
ge Response Measure the total delay from obe30 istrativ
Pagin Delay]/[Paging MME receive to Paging 10 e
g Success Times] Request messages Regio
Delay( (measurement point 1) to MME ns,
ms) send Service Request messages MME,
(measurement point 2) in IStep MSC,
1Figure 1.1. TAI,
Paging Success Times: Measure ECGI,
the total number of MME send CGI/S
Service Request messages at AI
measurement point 2 in IStep
1Figure 1.1.
Measurement Points
Figure 1.1 show the measurement points for CSFB paging KPIs.
Indicator
Table 1.1 lists the PIs for CSFB performance analysis tracing area update indicators.
TAU [Fallback TAU Fallback TAU Success: Measure S1- NetPr Admin
Succe Success]/ the total number of MME send MME obe30 istrativ
ss [Fallback TAU eNodeB TAU Accept messages 10 e
Rate( Requests] at measurement point 2 in Regio
%) IStep 1Figure 1.1 and IStep ns,
1Figure 1.2. MME,
Fallback TAU Requests: MSC,
Measure the total number of TAI,
eNodeB send MME TAU ECGI,
Request messages at CGI/S
measurement point 1 in IStep AI
1Figure 1.1 and IStep 1Figure
1.2.
Fallba [Fallback TAU Measure the total number of S1- NetPr Admin
ck Requests] eNodeB send MME TAU Request MME obe30 istrativ
TAU messages at measurement point 1 10 e
Reque in IStep 1Figure 1.1 and IStep Regio
sts(tim 1Figure 1.2. ns,
es) MME,
MSC,
TAI,
ECGI,
CGI/S
AI
Fallba [Fallback TAU Measure the total number of MME S1- NetPr Admin
ck Success] send eNodeB TAU Accept MME obe30 istrativ
TAU messages at measurement point 2 10 e
Succe in IStep 1Figure 1.1 and IStep Regio
ss(tim 1Figure 1.2. ns,
es) MME,
MSC,
TAI,
ECGI,
CGI/S
AI
TAU [Fallback TAU Fallback TAU Success: Measure S1- NetPr Admin
Failur Requests] - the total number of MME send MME obe30 istrativ
e [Fallback TAU eNodeB TAU Accept messages 10 e
Times Success] at measurement point 2 in Regio
(times IStep 1Figure 1.1 and IStep ns,
) 1Figure 1.2. MME,
Fallback TAU Requests: MSC,
Measure the total number of TAI,
eNodeB send MME TAU ECGI,
Request messages at CGI/S
measurement point 1 in IStep AI
1Figure 1.1 and IStep 1Figure
1.2.
Measurement Points
Figure 1.1 and Figure 1.2 show the measurement points for CSFB tracing area update KPIs.
Figure 1.1 Measurement points for CSFB tracing area update KPIs (1)
Figure 1.2 Measurement points for CSFB tracing area update KPIs (2)
Indicator
Table 1.1 lists the PIs for CSFB performance analysis fallback location update indicators.
e MME,
Succe MSC,
ss TAI,
Times ECGI,
(times CGI/S
) AI
Fallba [Fallback Fallback Location Update A, Iu- NetPr Admin
ck Location Success Times: Measure the CS obe90 istrativ
Locati Update total number of MSC send 00 e
on Requests]- Location Update Accept Regio
Updat [Fallback messages at measurement point ns,
e Location 2 in IStep 1Figure 1.1 and MME,
Failur Update Success IStep 1Figure 1.2. MSC,
e Times] Fallback Location Update TAI,
Times Requests: Measure the total ECGI,
(times number of MSC receive to CGI/S
) Location Update Request AI
messages at measurement point
1 in IStep 1Figure 1.1 and
IStep 1Figure 1.2.
Measurement Points
Figure 1.1 and Figure 1.2 show the measurement points for CSFB fallback location update
KPIs.
Figure 1.1 Measurement points for CSFB fallback location update KPIs (1)
Figure 1.2 Measurement points for CSFB fallback location update KPIs (2)
Indicator
Table 1.1 lists the KPIs for CSFB neighboring cell analysis.
Measurement Points
Figure 1.1 shows the measurement points for Fallback Location Update Ratio in a call
process.
Indicator
Table 1.1 lists the KPIs for CSFB delay analysis.
Measurement Points
Figure 1.1 and Figure 1.2 show the measurement points for CSFB delay KPIs in a call
process.
CSMO Fallback Call Success Rate KPIs Displayed in the Fishbone Diagram
Table 1.1 displays CSMO Fallback Call Success Rate KPIs as the main branch (fish body) in
the fishbone diagram.
Table 1.1 CSMO Fallback Call Success Rate KPIs (fish body)
Message Number Message Ratios Average Delay Dimension
of
Messages
Table 1.2 displays CSMO Fallback Call Success Rate KPIs as the branches (fishbone) in the
fishbone diagram.
CSMT Fallback Call Success Rate KPIs Displayed in the Fishbone Diagram
Table 1.1 displays CSMT Fallback Call Success Rate KPIs as the main branch (fish body) in
the fishbone diagram.
Table 1.1 CSMT Fallback Call Success Rate KPIs (fish body)
Message Number Message Ratios Average Delay Dimension
of
Messages
Table 1.2 displays CSMT Fallback Call Success Rate KPIs as the branches (fishbone) in the
fishbone diagram.
diagram
Indicator
Table 1.1 lists PIs for calculating relevant voice indicators (including those calculated based
on location update indicators).
Table 1.1 Voice indicators (those calculated based on location update indicators)
Indicato Calculation Measurement Point Data Prob Acce
r Formula Coll e ss
ectio /Thi Net
n rd- wor
Inter Part k
face y
Syst
em
11BV [MO Call Drops]/ MO Call Drops: For inbound ISUP NetP Entir
Call [MO Call roamers, measure the number robe e
Completi Answers] x 100% of Disconnect/Clear 9000 netw
on Rate Command/Release/Release ork
(%) Complete messages.
MO Call Answers: For inbound
roamers, measure the number
of ISUP ANM messages at
measurement point 3 shown in
IStep 1Figure 1.3.
12BV [Total MO Call Total MO Call Duration: For ISUP NetP Entir
Average Duration]/[MO inbound roamers, Σ (the length robe e
Length Call Answers] x of time between the CC 9000 netw
of Call 100% Connect and the CC ork
(s) Disconnect message.)
MO Call Answers: For inbound
roamers, measure the number
of ISUP ANM messages at
measurement point 3 shown in
IStep 1Figure 1.3.
Measurement Point
Figure 1.1 shows the measurement points of location update indicators.
Figure 1.2 shows the measurement points of mobile originated (MO) call indicators.
Indicator
Table 1.1 lists the PIs for relevant SMS indicators.
1.1.
24BH [MT SMS Total MT SMS Total Delay: For MAP NetP Entir
MT SMS Delay]/[MT SMS outbound roamers, Σ (the robe e
Access Successes] length of time between the 9000 netw
Delay MAP FSM and the MAP ork
(ms) FSM Ack message, that is,
from measurement point 3 to
measurement point 4 shown in
IStep 1Figure 1.1.)
MT SMS Successes: For
outbound roamers, measure
the number of MAP FSM Ack
messages at measurement
point 4 shown in IStep 1Figure
1.1.
Measurement Point
Figure 1.1 shows the measurement points of SMS indicators.
Indicator
Table 1.1 lists PIs for calculating relevant data indicators (including those calculated based on
location update indicators).
Table 1.1 Data indicators (including those calculated based on location update indicators)
Indicato Calculation Measurement Point Data Prob Acce
r Formula Coll e ss
ectio /Thir Net
n d- work
Inter Party
face Syst
em
39BV [Total RTT]/ Total RTT: Indicates the sum of Gp NetPr Entire
Roundtrip [Total TCP the average uplink round trip obe3 netwo
Time Connect time (RTT) multiplied by the 010 rk
(ms) Success uplink RTT times and the
Times] average downlink RTT
multiplied by the downlink RTT
times.
Total TCP Connect Success
Times: For inbound roamers,
measure the number of TCP
ACK messages.
40BH [Retransmitte Retransmitted TCP Packets: For Gp NetPr Entire
Packet d TCP outbound roamers, measure the obe3 netwo
Loss Rate Packets]/ number of retransmitted TCP 010 rk
(%) [Total TCP DATA messages.
Packets] x Total TCP Packets: For outbound
100% roamers, measure the total
number of TCP DATA
messages.
40BV [Retransmitte Retransmitted TCP Packets: For Gp NetPr Entire
Packet d TCP inbound roamers, measure the obe3 netwo
Loss Rate Packets]/ number of retransmitted TCP 010 rk
(%) [Total TCP DATA messages.
Packets] x Total TCP Packets: For inbound
100% roamers, measure the total
number of TCP DATA
messages.
Measurement Point