E2E Network Field Performance For Offer and Field Acceptance - I-HSPA Definitions Rel.3

1/82 COO RA RD SA NE Network Performance
Pavel Romanenko For internal use only

1/22/2010
Network Performance
COO RA RD SA NE
For internal use only,
E2E Network Field

Performance for Offer and
Field Acceptance
I-HSPA - Definitions and Measurements Methods.
Rel. 3.0
Version: Approved 1.0

1/22/2010
Revision History
Version Date Change Notes

0.1 12/16/009 Draft version
1.0 22/01/2010 Approved
Authors
The following persons have collaborated on this document:
Name Department
Pavel Romanenko COO RA RD SA NE

1/22/2010
Content:
1. Introduction....................................................................... 5
2. Key Performance Indicators for Voice quality ................ 6

2.1. Voice quality Mean Opinion Score (MOS)..................................................... 6
3. Key Performance Indicators for CS Services, Setup

and Release....................................................................... 7
3.1 CS (AMR Voice) RAB Establishment Success Rate ..................................... 7
3.2 CS Voice AMR Call Setup Success Rate ..................................................... 9
3.3 CS Video Call Setup Success Rate ............................................................ 10
3.4 Fast Call Setup Time from Cell_PCH, MOC ............................................... 11
3.5 Fast Call Setup Time from Cell_PCH, MTC ................................................ 12
3.6 CS Voice Call Drop Rate ............................................................................ 13
3.7 CS Video Call Drop Rate ............................................................................ 14
4. Key Performance Indicators for PS Service, Setup,

Update and Release........................................................ 15
4.1 PS RAB Establishment Success Rate ........................................................ 15
4.2 PS call Setup Success Rate ....................................................................... 17
4.3 PS Session Drop Rate................................................................................ 18
4.4 PS Attach Time .......................................................................................... 19
4.5 PS Attach Success Rate............................................................................. 20
4.6 PS Session Drop Rate................................................................................ 22
5. Key Performance Indicators for Service Area Update . 23

5.1. Location Update Time ................................................................................ 23
5.2. Location Update Success Rate................................................................... 24
5.3. IMSI Attach Success Rate .......................................................................... 25
5.4. Routing Area Update Time ......................................................................... 26
5.5. Routing Area Update Success Rate ........................................................... 28
6. RRC Connection Establishment Success Rate ............ 29
7. Key Performance Indicators for Mobility ...................... 31

7.1. Inter Adapter HO Success Ratio................................................................. 31
7.2. HSDPA Inter-frequency Hard Handover Ratio ............................................ 33
7.3. Inter-frequency Handover Interruption Time ............................................... 35
7.4. I-HSPA to 2G Handover Success Rate....................................................... 36
7.5. I-HSPA to 2G Handover Interruption Time.................................................. 40
7.6. I-HSPA to 3G PS Handover Success Rate ................................................. 41
1/22/2010
7.7. IHSDPA Serving Cell Change Success Rate.............................................. 44
8. Key Performance Indicators for Data Content

activation and interruption time..................................... 48
8.1 PS PDP Context Activation Time................................................................ 48
8.2 PS PDP Context Activation Time combined with GPRS Attach procedure.. 50
8.3 HSPA Call Setup time ................................................................................ 54
8.4 PS FACH to CELL_DCH Transition Interruption Time ................................ 57
8.5 E-DCH/HS-DSCH Cell Change Interruption Time....................................... 60
9. HSPA Throughput for different UL/DL RAB

combinations .................................................................. 63
9.1 HSPA Throughput for different UL/DL RAB combinations, 16 QAM............ 63
9.2 HSPA Throughput, 64 QAM ....................................................................... 66
10. Round Trip Time for FACH, DCH, HS-DSCH, E-DCH .... 67
11. Application-specific Key Performance Indicators........ 68

11.1 SMS Mobile Originated (MO) Delivery Time ............................................... 68
11.2 SMS MT Delivery Time............................................................................... 71
11.3 MMS MO Delivery Time.............................................................................. 74
11.4 MMS MT Delivery Time .............................................................................. 76
12. Abbreviations.................................................................. 79
13. References ...................................................................... 81

1/22/2010
1. Introduction
The target of this document is to provide general description, technical description
and measurements’ conditions of dedicated I-HSPA Rel. 3 Key Performance
Indicators’ group.
This group is proprietary set of defined KPIs for end user. Those End to End (E2E)
KPIs are proposed to be useful for detailed I-HSPA NW analysis to be able to
interpret the network behaviour, highlight the key factors of network monitoring and
to anticipate potential performance problems. That KPIs collection was based on
System Performance Specification Document, [1] and also relative with previous
RAN (RU 10, RU 20) main KPIs lists.
Current document can be used in IHSPA Rollout projects in internal NSN analysis,
and in global NPO issues, not mandatory related to specific projects. This
documents main audience is Network Planning and Optimization Specialists, RNC
engineers, and any internal NSN employee, interested in IHSPA main KPIs results.
For each KPI a set of most important information is provided (some are given only,
when applicable):
KPI name
Definition basic information about trigger points
Methodology of description of measurement procedure

measuring
Assumptions and pre- background information, important during measurement

conditions
Formula provided for Success and Drop Rates KPIs
Notes additional useful information
Related counters/KPIs’ reference to similar KPIs in document

numbers
Message flow provided for time Related counters/KPIs’ numbers for

monitoring of procedure correctness and for Success
Rates KPIs to indicate trigger points with incrementing PM
Counters
Please, note, that presented version is initial. The document was created when some other
documents that could be used like reference were not created yet. That is the reason why
some KPIs’ details are missing. Mostly that is concerning related counters/KPIs for PM based
Performance Indicators and message flows figures. Presented Indicators will be updated by
separate document.
1/22/2010
2. Key Performance Indicators for Voice quality

2.1. Voice quality Mean Opinion Score (MOS)
Voice quality Mean Opinion Score (MOS)
Definition Voice quality Mean Opinion Score (MOS) is result of a subjective

voice quality test often used to compare speech codec
algorithms, where listeners associate a one to five quality score
to speech samples. MOS is not absolute value.
The results between different tests can not be directly compared.
If the tests include the same codecs then results are pretty
comparable but if tests include different codec then results should
not be directly compared.
The higher MOS – the better is quality of the call.
Methodology of • Leave the Voice Call to run for at least 30 minutes – 1 hour to
measuring collect MOS samples (time period can be longer if determined to
be required by both Nokia and TMO.
• The voice quality is considered to be good when MOS (scale 1-
5) >3. With RAN 1.5.2 ED2, 12.2 kbps AMR, MOS ~3.6 on
average.
• Whether UEs & CN are supposed to be working ideally, MOS
reflects the Block / Frame Error Rate.
Assumptions and pre- For the best objective results recommended to make tests covering
conditions different cases:
• Stationary and Mobile user
• UE in Soft and Hard HO region
• UE in ISHO to 2G
• UE in compresses and in non-compresses modes
Formula
Notes The mean opinion score (MOS) provides a numerical indication of

the perceived quality of received media after compression and/or
transmission. The MOS is expressed as a single number in the
range 1 to 5, where 1 is lowest perceived quality, and 5 is the
highest perceived quality with one decimal precision. There are
many techniques used for calculating the MOS score of any voice
sample but the most commonly used are PSQM & PESQ.
Related counters/KPIs’
numbers
1/22/2010
3. Key Performance Indicators for CS Services,

Setup and Release
3.1 CS (AMR Voice) RAB Establishment Success Rate
CS (AMR Voice) RAB Establishment Success Rate
Definition The CS RAB (Radio Access Bearer) Establishment Success Rate is the ratio
between the number of successful RAB establishments for AMR Voice and the
number of attempted RAB establishments for AMR service. A RAB
establishment success is defined by submission of a RAB ASSIGNMENT
RESPONSE message by the RNC towards an MSC/MSC-S via the Iu interface
This RAB ASSIGNMENT RESPONSE message must contain the information
element RAB ID for the requested RAB in the “RABs Setup or Modified” group.
RAB establishment attempt is defined by the reception of the MSC/MSC-S
initiated RAB ASSIGMENT REQUEST message at the RNC.
Methodology • Test with trace mobile or Uu interface monitor in stationary use

of
• UE status: standby, subscriber CS attached
measuring
• Perform a voice call setup
• Verify the Success Rate by calculating ratio from the definition
Assumptions
and pre-
conditions
Formula number _ of ( RANAP _ RAB _ ASSIGN _ RESPONSE )

RABCS = * 100%
number _ of ( RANAP _ RAB _ ASSIGN _ REQUEST )
Notes For the unsuccessful cases, a RAB ASSIGNMENT REQUEST message can
also be answered with an Iu RELEASE REQUEST message by the RNC
instead of an RAB ASSIGNMENT RESPONSE message. That has been the
reason to provide the KPI for the success case only.
Related
KPIs
KPI based UTRAN

on PM Short name:
Counters
Aggregation Level: RNC, cell
1/22/2010
Figure 3.1 CS ATTACH message flow

1/22/2010
3.2 CS Voice AMR Call Setup Success Rate
CS Voice AMR Call Setup Success Rate
Definition Ratio between successfully established CS voice calls (AMR12.2 kbps

codec) compared to the overall number of voice call establishment
attempts. Voice Call Setup Time [s] denotes the length of time period it
takes to access the Voice service successfully, meaning that voice
connection is established. Voice Call Setup Time will be derived from the
successfully established short calls. The Call Setup Time (CST) is defined
as the period of time between the transmission of the RRC Connection
Request message from the UE, and the reception of the Direct Transfer
(Alerting) message

of measuring
• Perform a voice call setup to a PLMN within same country
• Perform one call setup attempt every 90s even if one attempt fails. If a call
is not established within 30s it shall be considered as failed.
• Verify the call setup time by recording the interval between RRC
CONNECTION REQUEST and L3 Alert at the UE side
Assumptions • The ISUP interface option in the MSC/MSC-S is assumed for the
and pre- connection towards the PSTN.
conditions
Formula number _ of ( ALERT )

CSSRVoice = * 100%
number _ of ( RRC _ CONNECTION _ REQUEST )
Notes
Related
KPIs/counters
KPI based on UTRAN

PM Counters Short name:
Aggregation Level: ADA
1/22/2010
3.3 CS Video Call Setup Success Rate

CS Video Call Setup Success Rate, MO
Definition The Call Setup Success Rate for a CS Video (Bearer Service 30 64kbps) is the
ratio between successful call establishments compared to the overall number of
call establishment attempts.
The successful establishment of a video call on the UE side is defined by the
successful reception of the layer 3 CC ALERT message at the UE. The video
call establishment attempt is the submission of the RRC CONNECTION
REQUEST message with Alerting of the establishment cause “Originating
Conversational Call” by the UE. This assumes the UE is the initiator of the call.

of
measuring
• Perform a video call setup to a PLMN within same country
• Perform one call setup attempt every 90s even if one attempt fails. If a call is
not established within 30s it shall be considered as failed.
• Verify the call setup time by recording the interval between RRC
CONNECTION REQUEST and L3 Alert at the UE side
Assumptions
and pre-
conditions
Formula number _ of ( ALERT )

CSSRVideo = * 100%
Notes Video Call Setup Time (CS64) will be derived from the successfully established
short calls. The Call Setup Time (CST) is defined as the period of time between
the transmission of the RRC Connection Request message from the UE, and
the reception of the Direct Transfer (Alerting) message.
Video Call Setup Time [s] denotes the length of time period it takes to access
the Video service successfully, meaning that video connection is established.
The time does not include the time taken for the UEs to display the video on the
screens.
Related
KPIs
KPI based UTRAN

on PM Short name:
Counters
Aggregation Level: RNC
1/22/2010
3.4 Fast Call Setup Time from Cell_PCH, MOC

Fast Call Setup Time from Cell_PCH, MOC
Definition Due to the feature "Fast Call Setup from Cell_PCH", RAN initiates MO AMR
Call Setup or MT PS Call Setup faster than without the feature activated,
This feature is invoked in the following transitions,
• when the CELL UPDATE (CU) message is sent by UE (UL direction) with
TVM IE set and single RAB, in case of CU message with TVM IE set and
Multiple RABs the direct transition is not done
• when RACH measurements indicate good radio conditions
• different capacity thresholds configured on Iu-PS are also defined for
moving UE to CELL_FACH or CELL_DCH in case of DL data permitting
an enhanced monitoring of Iu-PS buffers;
• in case of bad radio conditions the transition from PCH → FACH to DCH is
done automatically without waiting for any trigger in CELL_FACH state
• In case of DL, paging and resource reservation are done in parallel
The performance indicators of this feature usage include the MO / MT AMR
Call Setup from CELL_IDLE state.
Fast Call Setup Time from Cell_PCH, MOC is calculated from "Cell Update"
to "Alerting".

of measuring
Assumptions
and pre-
conditions
Formula
Notes
Related
KPIs/counters
1/22/2010
3.5 Fast Call Setup Time from Cell_PCH, MTC

Fast Call Setup Time from Cell_PCH, MOC
Definition Due to feature "Fast Call Setup from Cell_PCH", RAN initiates MO AMR
Call Setup or MT PS Call Setup faster than without the feature activated,
This feature is invoked in the following transitions,
• when the CELL UPDATE (CU) message is sent by UE (UL direction) with
TVM IE set and single RAB, in case of CU message with TVM IE set and
Multiple RABs the direct transition is not done
• when RACH measurements indicate good radio conditions
• different capacity thresholds configured on Iu-PS are also defined for
moving UE to CELL_FACH or CELL_DCH in case of DL data permitting an
enhanced monitoring of Iu-PS buffers;
• in case of bad radio conditions the transition from PCH → FACH to DCH
is done automatically without waiting for any trigger in CELL_FACH state
• In case of DL, paging and resource reservation are done in parallel
• The performance indicators of this feature usage include the MO / MT
AMR Call Setup from CELL_IDLE state.
• Fast Call Setup Time from Cell_PCH, MTC is calculated from "Paging" to
"Alerting".

of measuring
Assumptions
and pre-
conditions
Formula
Notes
Related
KPIs/counters
1/22/2010
3.6 CS Voice Call Drop Rate

CS Voice Call Drop Rate
Definition Ratio between abnormally released voice calls and the overall number of
established voice calls. For the purpose of end-to-end measurements, an
abnormal release of a voice call is defined as any call termination at the UE
side which has not been triggered by the mobile user at the UE side or its
corresponding peer party.
I-HSPA Rel. 3 support CS services, and that makes the command flows of CS
Voice Service Drop quite similar to previous RU versions.

of
measuring
• Perform a voice call setup to a PLMN within same country or to UE in the
same MSC/MSC-S
• Trigger subsequent call setup using appropriate test automation
• Certain time of call duration (90-120 sec) should be agreed
Assumptions • The Call Drop Rate as being initiated by the UTRAN is strongly influenced by
and pre- the radio network planning process and the resulting coverage in the actual
conditions network. Therefore, it is important to ensure that the good radio and coverage
conditions are met.
• Call drops being initiated by the MSC/MSC-S due to internal failures might
occur but the assumed probability is equal or less than 10-4. Thus, for the
overall calculation of a call drop rate, the MSC/MSC-S initiated call drop rate is
compared to the I-HSPA radio link initiated call drop rate.
• For the purpose of a call drop measurement, any IN inter-working in the core
network and to O&M intervention are excluded.
Formula number _ of (CONNECT _ ACKNOWLEDGE − DISCONNECT )

CDRVoice = *100%
number _ of (CONNECT _ ACKNOWLEDGE )
Notes The Call Drop Rate shall indicate how many of the voice calls are abnormally
released by the UMTS network (core network and UTRAN) instead of being
released by a mobile service user.
The successful establishment of a CS call on the UE side is defined by
submitting the CC CONNECT ACKNOWLEDGE message by the UE (after
previous reception of the CC CONNECT message). For the purpose of a UE
measurement, a call drop is given if the call is not regularly released by the UE
itself after a certain holding time. A regular release is given if the UE terminates
the call by submitting a CC DISCONNECT message.
1/22/2010
3.7 CS Video Call Drop Rate

CS Video Call Drop Rate
Definition Ratio between abnormally released CS Video calls and the overall number of
established CS Video calls. For the purpose of end-to-end measurements, an
abnormal release of a video call is defined as any call termination at the UE
side which has not been triggered by the mobile user at the UE side or its
corresponding peer party.
I-HSPA Rel. 3 support CS services, and that makes the command flows of CS
Video Service Drop quite similar to previous RU versions.

of
measuring
• Perform a video call setup to UE in the same MSC/MSC-S
• Trigger subsequent call setup using appropriate test automation
• Certain time of call duration (90 – 120 sec) should be agreed
Assumptions • The Call Drop Rate as being initiated by the UTRAN is strongly influenced by
and pre- the radio network planning process and the resulting coverage in the actual
conditions network. Therefore, it is important to ensure that the good radio and coverage
conditions are met.
• Call drops being initiated by the MSC due to internal failures might occur but
the assumed probability is equal or less than 10-4. Thus, for the overall
calculation of a call drop rate, the MSC initiated call drop rate is neglect able
compared to the UTRAN initiated call drop rate.
• For the purpose of a call drop measurement, any IN inter-working in the core
network and to O&M intervention are excluded.
Formula number _ of (CONNECT _ ACKNOWLEDGE − DISCONNECT )

CDRVideo = * 100%
number _ of (CONNECT _ ACKNOWLEDGE )
Notes The Video Call Drop Rate shall indicate how many of the video calls are
abnormally released by the UMTS network (core network and UTRAN) instead
of being released by a mobile service user.
The successful establishment of a CS call on the UE side is defined by
submitting the CC CONNECT ACKNOWLEDGE message by the UE (after
previous reception of the CC CONNECT message). For the purpose of a UE
measurement, a call drop is given if the call is not regularly released by the UE
itself after a certain holding time. A regular release is given if the UE terminates
the call by submitting a CC DISCONNECT message.
1/22/2010
4. Key Performance Indicators for PS Service,

Setup, Update and Release
4.1 PS RAB Establishment Success Rate
PS RAB Establishment Success Rate
Definition The PS RAB (Radio Access Bearer) Establishment Success Rate is the ratio
between the number of successful RAB establishments and the number of
attempted RAB establishments for PS services. RAB establishment success is
defined by submission of a RAB ASSIGNMENT RESPONSE message by the
ADA towards an SGSN (Serving GPRS Support Node) via the Iu interface. This
RAB ASSIGNMENT RESPONSE message must contain the information
element RAB ID for the requested RAB in the “RABs Setup or Modified” group.
An RAB establishment attempt is defined by the reception of an SGSN initiated
RAB ASSIGMENT REQUEST message at the ADA.
Methodology • Test with trace mobile

of measuring
• UE status: standby, subscriber PS attached
• Trigger subsequent PDP context activation procedures
• Verify the RAB Establishment Success Rate calculating ration from the
definition
Formula number _ of ( RANAP _ RAB _ ASSIGN _ RESPONSE )

RABPS = * 100%
number _ of ( RANAP _ RAB _ ASSIGN _ REQUEST )
Notes For the unsuccessful cases, a RAB ASSIGNMENT REQUEST message can
also be answered with an Iu RELEASE REQUEST message by the ADA
instead of an RAB ASSIGNMENT RESPONSE message. That has been the
reason to provide the KPI for the success case only.
KPI based on Core,

PM Counters Short name: sgsn_822a (SG6.0)
1/22/2010
Figure 4.1.PS RAB Establishment procedure message flow

1/22/2010
4.2 PS call Setup Success Rate

PS Call Setup Success Rate
Definition For Packet Call is recommended to describe the service setup process not
similar with CS Call, but based on the packet session setup. When the
session is set up, it means that there is data to be received or to be sent.
The packet session setup is here considered to be the point when the
reservation of a transport channel starts.
Ratio between successfully established PS calls compared to the overall
number of PS call establishment attempts.
The PS Call flow may be defined started by submission of the RRC
message CONNECTION REQUEST (refer to [3GPP25331]) and the
reception of the layer 3 message ACTIVATE PDP CONTEXT ACCEPT
(refer to [3GPP24008]) at a UE.
The PS Session Drop Rate is the ratio between successfully setup PS
sessions attempts and the total number PS sessions setup attemts.
Methodology • test with UE/laptop or PC

of measuring
• the UE or a connected device (e.g. laptop) represents the client side, an
FTP server represents the server side
• the FTP or HTTP application shall be deployed for the PS session by
starting a file download
• trigger subsequent PS sessions using appropriate test automation
a PS session duration of 90 s shall be applied
Assumptions
and pre-
conditions
Formula number _ of ( PS _ session _ setup _ successes )

PCSSR = * 100%
number _ of ( PS _ session _ setup _ attempts )
Notes For the unsuccessful cases, a RAB ASSIGNMENT REQUEST message
can also be answered with an Iu RELEASE REQUEST message by the
ADA instead of an RAB ASSIGNMENT RESPONSE message. That has
been the reason to provide the KPI for the success case only.
Related
KPIs/counters
KPI based on UTRAN

PM Counters Short name:
Aggregation Level: ADA
1/22/2010
4.3 PS Session Drop Rate

Session Drop Rate
Definition Any call termination at the UE side which has not been triggered by the
mobile user at the UE side or its corresponding peer party. This excludes
regular session terminations from the I-HSPA network side such as IN
inter-working or release due to O&M intervention. The PS Session Drop
Rate is the ratio between abnormally released PS sessions and the overall
number of established PS session.

of measuring
• UE status: subscriber PS attached, PDP context established
• perform at least two (soft-) handover procedures while the session is
active
• a PS session duration of 90 s shall be applied
• verify application status using application layers analyser (e.g. Ethereal)
Assumptions Reasons for a session drop caused by the UMTS network include:
and pre- • Abnormal release of a RAB by the UTRAN (without RAB re-establishment
conditions before the PS session abnormally terminates)
• De-activation of the PDP context by the core network (excluding IN, HLR
or OM inter-working)
• Stop of data transfer by the I-HSPA network
• Violation of requested Quality of Service for the PDP context (e.g.
significant packet loss, high delay)
Formula number _ of ( Abnormal _ Session _ Drops )

SDR = * 100%
number _ of ( Success _ Session )
Notes A PS session is defined as an active IP-based service running on top of the
GPRS service as defined in [3GPP23.060].
Related
counters/KPIs’
numbers
KPI based on
PM Counters
1/22/2010
4.4 PS Attach Time

PS Attach Time
Definition The PS Attach Time is the interval between the submission of the
RRC message CONNECTION REQUEST (refer to [3GPP25331])
and the reception of the layer 3 message ATTACH ACCEPT
(refer to [3GPP24008]) at a UE.
Methodology of • Test with trace UE

measuring
• UE status: switched off, subscriber PS detached
• Switch the UE on and trigger the PS Attach procedure (power
on)
• Verify the Attach time by using a tracing UE
Assumptions and pre-

conditions
Formula -
Notes The procedure is the GPRS ATTACH according to

[3GPP24.008].
numbers
1/22/2010
4.5 PS Attach Success Rate

PS Attach Success Rate
Definition The successful Attach procedure on the UE side is defined as the ratio
between number of ATTACH ACCEPT messages from the SGSN being
received at the UE (refer to [3GPP24008]) and the number of RRC
CONNECTION REQUEST messages (with establishment cause Registration)
according to [3GPP25331] being sent from the UE.
Methodology • Test with trace UE

of
• UE status: switched off, subscriber PS detached
measuring
• Switch the UE on and trigger the PS Attach procedure (power on)
• Verify the Attach time by using a tracing UE
Assumptions • Unsuccessful Attach procedures due to missing subscriptions or

and pre- unsupported configuration of an individual UE shall be excluded.
conditions
Formula number _ of ( ATTACH _ ACCEPT )

PSATTSR = * 100%
Notes The procedure is the GPRS ATTACH according to [3GPP24.008].
Related
counters/KPI
s’ numbers
KPI based Aggregation Level: SGSN, Routing Area

on PM Short name: sgsn_720a (SG6.0)
Counters
Aggregation Level: SGSN
1/22/2010
RRC CONNECTION REQUEST
RRC DOWNLINK DIRECT TRANSFER (L3 AATTACH ACCEPT)
Figure 4.2.PS Attach procedure message flow

1/22/2010
4.6 PS Session Drop Rate

Session Drop Rate
Definition A call termination at the UE side which has not been triggered by the mobile
user at the UE side or its corresponding peer party. This excludes regular
session terminations from the UMTS network side such as IN inter-working or
release due to O&M intervention. The PS Session Drop Rate is the ratio
between abnormally released PS sessions and the overall number of
established PS session.

of measuring
• UE status: subscriber PS attached, PDP context established
• perform at least two (soft-) handover procedures while the session is active
• a PS session duration of 90 s shall be applied
• verify application status using application layers analyser (e.g. Ethereal)
Assumptions Reasons for a session drop caused by the UMTS network include:
and pre-
• Abnormal release of a RAB by the UTRAN (without RAB re-establishment
conditions
before the PS session abnormally terminates)
• De-activation of the PDP context by the core network (excluding IN, HLR or
OM inter-working)
• Stop of data transfer by the UMTS network
• Violation of requested Quality of Service for the PDP context (e.g. significant
packet loss, high delay)
Formula number _ of ( Abnormal _ Session _ Drops )

SDR = * 100%
number _ of ( Success _ Session )
Notes A PS session is defined as an active IP-based service running on top of the
GPRS service as defined in [3GPP23.060].
Related KPIs
KPI based on Core

PM Counters Short name: PS_2G_3G_SGSN_SM_Deact_01

1/22/2010
5. Key Performance Indicators for Service Area

Update
5.1. Location Update Time
CS Location Update Time
Definition The Location Area Update Time is the interval between the
submission of the RRC message RRC CONNECTION
REQUEST (refer to [3GPP25331]) and the reception of the layer
3 message LOCATION UPDATE ACCEPT (refer to
[3GPP24008]) at a UE.
Methodology of • Switch the UE on to perform LUP procedure

measuring
• Verify the LUP time by using a tracing UE
Assumptions and pre- • It is assumed that an Intra-MSC/MSC-S Location Update

conditions procedure is performed from a UE to an MSC/MSC-S/VLR that
has already stored the associated subscriber record in the VLR
(no change of MSC/MSC-S area since the last detach).
Formula -
Notes
numbers
1/22/2010
5.2. Location Update Success Rate

Location Update Success Rate
Definition The successful Location Update procedure on the UE side is defined as the
ratio between number of LOCATION UPDATE ACCEPT messages from the
MSC-S/VLR being received at the UE (refer to [3GPP24008]) and the number
of RRC CONNECTION REQUEST messages (with establishment cause
Registration) according to [3GPP25331] being sent from the UE. The
LOCATION UPDATE procedure is specified in [3GPP23012].
Shortly, this KPI is Ratio of successful location update and attempt location
update in percentage for 3G subscriber.

of
• trigger subsequent Location Update procedures by turning on the UE or
measuring
using an appropriate script
• Verify the Location Update Success Rate by recording the number of
successful Location Updates and the number of corresponding attempts on
the UE side
• Location update due to change of Location Area where the new Location
Area belongs to the same MSC
• No subscriber data is fetched from the HLR
• At each attempt, the RRC CONNECTION REQUEST message from the UE
is sent, and the reception of the DT LOCATION UPDATING ACCEPT
message in the UE is confirmed before timeout occurs.
• The timeout interval for the LU procedure is 30 seconds, meaning: if the
procedure was not completed after 30 seconds it is considered as failure.
Note that the timeout value of 30 seconds is no system internal value
Assumptions • It is assumed that an Intra-MSC/MSC-S Location Update procedure is

and pre- performed from a UE to an MSC/MSC-S/VLR that has already stored the
conditions associated subscriber record in the VLR (no change of MSC/MSC-S area
since the last detach).
• Unsuccessful Location Update procedures due to missing subscriptions or
unsupported configuration of an individual UE shall be excluded.
Formula number _ of ( LOCATION _UPDATE _ ACCEPT )

CSLUPSR = * 100%
Notes
Related
counters/KPI
s’ numbers
1/22/2010
5.3. IMSI Attach Success Rate

IMSI Attach Success Rate
Definition IMSI Attach Success Rate is Ratio of successful IMSI attach and attempt
IMSI attach in percentage for 3G subscriber.
Methodology • An authentication vector is requested from the HLR and authentication is

of measuring included.
• At each attempt, the RRC CONNECTION REQUEST message from the
UE is sent, and the reception of the DT LOCATION UPDATING ACCEPT
message in the UE is confirmed before timeout occurs.
• The timeout interval for the attach procedure is 30 seconds, meaning: if
the procedure was not completed after 30 seconds it is considered as
failure.
• Note that the timeout value of 30 seconds is no system internal value.
Assumptions
and pre-
conditions
Formula # successful attach attempts

Attach Success Ratio [%] = ∗100
total # of attach attempts
Notes
Related
counters/KPIs’
numbers
1/22/2010
5.4. Routing Area Update Time

Routing Area Update Time
Definition Routing Area Update Time is the interval between the submission
of the RRC message RRC CONNECTION REQUEST (refer to
[3GPP25331]) and the reception of the layer 3 message
ROUTING AREA UPDATE ACCEPT (refer to [3GPP24008]) at a
UE.
Methodology of UE status: IDLE, subscriber PS attached

measuring Perform RAU procedure
Verify the RAU time by using a tracing UE.
Assumptions and pre- Authentication procedure and MAP Update Location procedure
conditions are options that are not used during Routing Area Update.
No SGSN change since last RA Update.
Unsuccessful RAU procedures due to missing subscriptions or
unsupported configuration of an individual UE shall be excluded.
Formula -
Notes
numbers
1/22/2010
Figure 5.1.Routing Area Update message flow

1/22/2010
5.5. Routing Area Update Success Rate

Routing Area Update Success Rate
Definition The successful RAU procedure on the UE side is defined as the ratio between
number of ROUTING AREA UPDATE ACCEPT messages from the SGSN
being received at the UE (refer to [3GPP24008]) and the number of RRC
CONNECTION REQUEST messages (with establishment cause Registration)
according to [3GPP25331] being sent from the UE.
Methodology • Perform RAU procedure

of
• Verify the RAU time by using a tracing UE.
measuring
Assumptions • Authentication procedure and MAP Update Location procedure are options
and pre- that are not used during Routing Area Update.
conditions
• No SGSN change since last RA Update.
• Unsuccessful RAU procedures due to missing subscriptions or unsupported
configuration of an individual UE shall be excluded.
Formula number _ of ( ROUTING _ AREA _ UPDATE _ ACCEPT )

PSRAUSR = * 100%
Notes The RAU procedure is specified in [3GPP24008].
Related
counters/KPI
s’ numbers
KPI based Core

on PM Short name: sgsn_761a (SG6.0)
Counters
1/22/2010
6. RRC Connection Establishment

Success Rate
RRC Connection Establishment Success Rate
Definition RRC Connection Establishment Success Rate is the ratio between the
number of success RRC connection establishments and the number of all
attempted RRC connection establishments. Attempt is defined by the
reception of an UE initiated RRC CONNECTION REQUEST message at the
RNC. RRC connection establishment success is defined by reception of a
RRC CONNECTION SETUP COMPLETE message by the RNC.
Radio resource performance indicators: RRC Setup and Access Complete
Ratio from the network point of view, RRC Setup and Access Complete Ratio
from user point of view and RRC Success Ratio from user perspective are
based on RRC Connection Establishment Success Rate and can be
summarized by that.

of measuring
• Perform a voice call setup
• Verify the Success Rate by calculating ratio from the definition
Assumptions • The recommended target value shall exclude the effects when UEs submit
and pre- subsequently RRC CONNECTION REQUEST messages without waiting for
conditions reception of the corresponding response message, or without waiting until
timer T300 is expired. That would increase the number of establishment
attempts, and consequently affect the overall ratio. The same effect may occur
in case of bad radio conditions or blocking within UTRAN.
Formula number _ of ( RRC _ CONN _ SETUP _ COMPLETE )

RRCSR = * 100%
Notes RRC Connection Request message is sent from UE; the I-HSPA Adapter
takes admission decision, creates the radio link for the UE and then responds
with RRC Connection Setup. UE moves to Cell DCH state and responds with
RRC Connection Setup Complete message, which includes the capabilities of
the UE.
Related Counter: Service Level measurement Counters

counters/KPIs KPI:IHSHA_5003a
’ numbers
1/22/2010
Figure 6.1.RRC Connection Establishment message flow
Figure 6.2.RRC Connection Normal Release message flow

1/22/2010
7. Key Performance Indicators for Mobility
7.1. Inter Adapter HO Success Ratio
Inter Adapter HO Ratio
Definition HSDPA INTER ADAPTER INTRA FREQUENCY HARD HANDOVER

RATIO is the ratio between the number of SUCCEED INTER ADAPTER
HANDOVERS and ATTEMPTED INTER ADAPTER HANDOVERS.
Methodology
of measuring
Assumptions Performing Handover is intra-frequency

and pre-
conditions
Formula number _ of (InterADAHO success )

InterADAHO SR = * 100%
number _ of (InterADAHO attempts )
Notes The purpose of role switch procedure is to enable inter-RNC (Adapter)
relocation, and also retaining the (original source) source RNC (Adapter)
radio link even after the relocation. This is a deviation from the 3GPP
specification for relocation and needs special RNSAP extensions. The UE
active set before and after the role switch does not change. Inter Adapter
HO used with Iur*: Iur Interface between Adapters. With the Feature Mobility
Optimisation a new message is introduced, which informs the source
adapter, whether a CTS or which kind of CTS has to be performed.
Related
counters/KPI
s’ numbers
1/22/2010
Figure 7.1 Inter Adapter intra Frequency Handover Procedure Message flow
1/22/2010
7.2. HSDPA Inter-frequency Hard Handover Ratio

Inter-frequency Handover Interruption Time with Compressed Mode
Definition HSDPA Inter-frequency Hard Handover Ratio is the ratio between the
number of SUCCEED HSDPA INTER-FREQUENCY HANDOVERS and
ATTEMPTED HSDPA INTER-FREQUENCY HANDOVERS.
HSDPA Inter-Frequency Hard Handover Success Rate indicator is over
the reporting period. KPI includes Intra-ADA and Inter ADA/RNC IFHO.

measuring
• The test is carried out by performing FTP uploading
Assumptions
and pre-
conditions
Formula number _ of ( HSDPA IFHO success )

HSDPA IFHO SR = * 100%
number _ of ( HSDPA IFHO attempts )
Notes Only IFHO execution phase is included and not IFHO-measurement

phase.
Related Counter: Service Level measurement Counters

counters/KPIs’ IHSPA_5032a
numbers
1/22/2010
Figure 7.2 Inter Frequency Hard Handover Procedure Message flow

1/22/2010
7.3. Inter-frequency Handover Interruption Time
Inter-frequency Handover Interruption Time
Definition The Hard-Handover Interruption Time (Inter-frequency HO) is time between

last correct data packet sent in UL on old frequency and first correct data
packet sent on Iu Interface in UL on new frequency in target cell.
Measurement could be done with continuous generated UDP traffic in UL to
avoid any additional delay because TCP behaviour or with FTP UL transfer.

of measuring
• The test is carried out by performing FTP uploading
• The interruption time shall be measured using the output of a continuous
data transfer
Assumptions
and pre-
conditions
Formula
Notes
Related
counters/KPI
s’ numbers
1/22/2010
7.4. I-HSPA to 2G Handover Success Rate

I-HSPA to 2G Handover Success Rate
Definition Outgoing Inter System Hard Handover Success Ratio to 2G for the
reporting period in the Source Cell of the Hard Handover. Includes both
coverage based handovers.

of measuring
• UE status: active, PMM connected, subscriber PS attached, PDP
context activated
• trigger subsequent I-HSPA to GSM Inter-System Handover procedures
• Verify the I-HSPA to GSM Inter-System Handover Success Rate by
recording the number of successful Routing Area Updates and the
number of corresponding Cell Change Order From UTRAN messages on
the UE side
Assumptions • Inter SGSN Handover (separate SGSNs for 2G and I-HSPA)

and pre-
conditions
Formula Inter system HO success (NRT + CS enabling HO)

IHSPA 2G HSRPSl = * 100%
Inter system HO attempts (NRT + CS enabling HO)
Notes For reference, the signalling flows for I-HSPA to 2G HO from CELL_DCH
and from CELL_FACH states are also presented.
Related KPI:IHSHA_5025a
counters/KPIs
numbers
1/22/2010
Figure 7.3.I-HSPA to 2G Handover Success Rate message flow

1/22/2010
Figure 7.4.I-HSPA to 2G Handover Success Rate for PS call in CELL_DCH case,

message flow
1/22/2010
Figure 7.5.I-HSPA to 2G Handover Success Rate for PS call in CELL_FACH case,

message flow
1/22/2010
7.5. I-HSPA to 2G Handover Interruption Time

PS UMTS to GSM Inter-System Handover Interruption Time
Definition The PS UMTS to GSM Handover Interruption Time is defined as the

interval between the reception of the last data packet in UMTS coverage,
and the reception of the first data packet in GSM coverage at the UE side.

measuring
• The test is carried out by sending continuous PING messages or FTP
download and logging the reception of the reply from the server at the UE.
• Initial status of UE before starting one ping group: PMM: CONNECTED in
CELL-DCH state using a Background or Interactive PDP context.
• The interruption time shall be measured using the output of a continuous
data transfer (e.g. FTP application) of the used operating system with a
comparable measurement tool,.
Assumptions • Inter SGSN Handover (separate SGSNs for 2G and IHSPA)

and pre-
• Due to fact that MSC/MSC-S sends Data packets towards UE in parallel
conditions
during Handover procedure, overall Interruption Time depends on UE
decision when to switch from I-HSPA to GSM.
Formula
Notes
Related
counters/KPIs’
numbers
1/22/2010
7.6. I-HSPA to 3G PS Handover Success Rate

I-HSPA to 3G PS Handover Success Rate
Definition Current KPI is Outgoing PS Inter System Hard Handover Success Ratio to
3G for the reporting period in the Source Cell of the Hard Handover.
Includes both coverage based handovers.

of
• UE status: active, PMM connected, subscriber PS attached, PDP context
measuring
activated
• I-HSPA and WCDMA belongs to one RNC
Assumptions
and pre-
conditions
Formula IHSPA_3G PS_HO success

IHSPA 3G HSRPSl = * 100%
IHSPA_3G PS_ attempts
Notes The Key case for I-HSPA is Redirection from Idle Mode to 3G for
unsupported UE, the signalling command scenario is provided.
counters/KPI
s’ numbers
1/22/2010
Figure 7.6.I-HSPA to 3G Handover Success Rate for PS call message flow

1/22/2010
Figure 7.7.I-HSPA is Redirection from Idle Mode to 3G for unsupported UE

message flow
1/22/2010
7.7. IHSDPA Serving Cell Change Success Rate

IHSDPA Serving Cell Change Success Rate
Definition IHSDPA Serving Cell Change Success Rate shows the rate between
IHSDPA Serving Cell Change attempts and IHSDPA Serving Cell Change
successes.
IHSDPA Serving Cell Change Success Rate over the reporting period in the
Source Cell.

of
• UE status: active, PMM connected, subscriber PS attached, PDP context
measuring
activated
Assumptions
and pre-
conditions
Formula IHSDPA SC success

IHSDPA SCC SRl = * 100%
IHSDPA SC attempts
Notes Different Serving Cell Change and Inter ADA I-HSPA HOs scenarios are
presented in signalling flows.
counters/KPI
s’ numbers
1/22/2010
Figure 7.8.Inter-Adapter Cell Change without Iur in same RAC message flow
Figure 7.9.Inter-Adapter Cell Change without Iur in different RAC

message flow
1/22/2010
Figure 7.10.Inter-Adapter Handover with Iur in URA_PCH case message flow

1/22/2010
Figure 7.11.Intra-Adapter Handover with UE in CELL_DCH case message flow

1/22/2010
8. Key Performance Indicators for Data Content

activation and interruption time
8.1 PS PDP Context Activation Time
PS PDP Context Activation Time
Definition The PDP Context Activation Time is the interval between the
submission of the RRC message CONNECTION REQUEST
(refer to [3GPP25331]) and the reception of the layer 3 message
ACTIVATE PDP CONTEXT ACCEPT (refer to [3GPP24008]) at a
UE.
Methodology of • Test with trace UE (stationary use)

measuring
• UE status: standby, subscriber PS attached
• Perform a PDP CONTEXT ACTIVATION procedure to an APN
within the same PLMN
• The PDP context shall be activated with normal QoS parameters
as being used for typical applications (web-surfing, e-mail or ftp
downloads). Hence the requested traffic class shall be
Background or Interactive and the requested maximum bit rate in
downlink direction shall not exceed 384 kbps.
• Verify the context activation time by using a tracing UE
• Time is including Authentication and Ciphering Request
procedure
Assumptions and pre- • It is assumed that during the PDP context activation no HLR
conditions inter-working is performed in the core network. P-TMSI
Reallocation is considered as an option that is not to be used.
• The corresponding IP address shall be assigned dynamically by
the GGSN without additional inter-working to an external DHCP
server at the Gi interface. RADIUS inter-working at the Gi
interface shall be excluded, as well
• During Test Network measurements Boomerang Fast Automatic
Testing (BFAT) SW was used. The measurements were
performed with stationary users.
Formula -
Notes
numbers
1/22/2010
Figure 8.1.PDP Context Activation without GPRS Attach message flow

1/22/2010
8.2 PS PDP Context Activation Time combined with

GPRS Attach procedure
PS PDP Context Activation Time combined with GPRS Attach procedure
Definition The PDP Context Activation Time is the interval between the
(refer to [3GPP25331]) and the reception of the layer 3 message
ACTIVATE PDP CONTEXT ACCEPT (refer to [3GPP24008]) at a
UE.

measuring
• UE status: standby, subscriber is not PS attached
• Perform combined GPRS ATTACH and PDP CONTEXT
ACTIVATION procedure to an APN within the same PLMN
• The PDP context shall be activated with normal QoS parameters
as being used for typical applications (web-surfing, e-mail or ftp
downloads). Hence the requested traffic class shall be
Background or Interactive and the requested maximum bit rate in
downlink direction shall not exceed 384 kbps.
interface shall be excluded, as well
• During Test Network measurements Boomerang Fast Automatic
Testing (BFAT) SW was used. The measurements were
performed with stationary users.
Formula -
Notes As some private case, PDP Context activation with Direct Tunnel
signalling glow is provided also.
numbers
1/22/2010
Figure 8.2.PDP Context Activation combined with GPRS Attach procedure,

message flow, 1/2
1/22/2010
Figure 8.3.PDP Context Activation combined with GPRS Attach procedure

message flow, 2/2
1/22/2010
Figure 8.4.PDP Context Activation in case of Direct Tunnel message flow

1/22/2010
8.3 HSPA Call Setup time

HSPA Call Setup time
Definition The HSPA Call Setup time is the interval between the submission
of the RRC message CONNECTION REQUEST (refer to
[3GPP25331]) and the reception of the layer 3 message RADIO
BEARER RECONFIGURATION COMPLETE (refer to
[3GPP24008]) at Adapter.

measuring
• UE status: standby, subscriber is not PS attached
• Perform combined GPRS ATTACH and PDP CONTEXT
ACTIVATION procedure to an APN within the same PLMN
• Perform FTP Upload or Download request to initiate Bit Rate
Adaptation procedure
interface shall be excluded, too.
Formula -
Notes
numbers
1/22/2010
Figure 8.5 HSPA Call Setup message flow, 1/2

1/22/2010
Figure 8.6.HSPA Call Setup time message flow, 2/2

1/22/2010
8.4 PS FACH to CELL_DCH Transition Interruption

Time
PS FACH to CELL_DCH Transition Interruption Time
Definition The Forward Access Channel (FACH) is a downlink transport channel. The
FACH is transmitted over the entire cell. The FACH can be transmitted
using power setting described in The Dedicated Channel (DCH) is a
downlink or uplink transport channel. The DCH is transmitted over the entire
cell or over only a part of the cell using e.g. beam-forming antennas.
Procedure begins from reception of RRC MEASUREMENT REPORT with
event 4A (indicates PS RAB buffer overflow on UL or DL) and finishes by
reception of FP CELL_DCH CAPACITY ALLOCATION. Procedures is
according to [3GPP TS25.331] and [3GPP 25.435].

of measuring
• PDP Context activated
• Perform FTP transfer in CELL_FACH state
• The interruption time shall be measured using interface analyser
Assumptions • The procedure for CTS FACH to HS-DSCH is the same as the procedure
and pre- for RAB Establishment from FACH to HS-DSCH, except that the RRC
conditions procedure is Transport Channel Reconfiguration, instead of Radio Bearer
Setup.
• The trigger for CTS from FACH to HS-DSCH is the same as the trigger
from FACH to DCH, caused by sending Measurement Report (event 4A)
which indicates PS RAB buffer overflow on UL or DL.
Formula -
Notes This scenario happens when UE attempts to send amount of data requiring
more capacity than is offered by CELL_FACH state. The PS CTS from
FACH to HS-DSCH Interruption time is measurement to see how long take
RRC State Transition between these States.
The return process scenario flow is presented.
Related
counters/KPI
s’ numbers
1/22/2010
Figure 8.7.FACH to CELL_DCH transition message flow

1/22/2010
Figure 8.8.CELL_DCH to FACH to transition message flow

1/22/2010
8.5 E-DCH/HS-DSCH Cell Change Interruption Time

HS-DSCH Cell Change Interruption Time
Definition The Enhanced Dedicated Channel (E-DCH) is an uplink transport channel..

The High Speed Downlink Shared Channel is a downlink transport channel
shared by several UEs. The HS-DSCH is associated with one downlink
DPCH, and one or several Shared Control Channels (HS-SCCH). The HS-
DSCH is transmitted over the entire cell or over only part of the cell using
e.g. beam-forming antennas.
The current task has two definitions:
Intra-Adapter
Interruption Time in case Intra ADA Cell Change measures time of
successful procedure seen as frame between last received PDU user data
packet on old cell and first received user data packet on new cell. Both cells
belong to the same Adapter.
Trigger for Intra-ADA Cell Change is Measurement Report with 1A event.
Measurement report initializing RAN to start intra-BTS serving HS-DSCH
Cell change.
Time is measured to physical Channel Reconfiguration Complete message.
Inter-Adapter
Interruption Time in case Inter-ADA Cell Change measures time of
successful procedure seen as frame between last received PDU user data
packet on old ADA and first received user data packet on new ADA.
Trigger for Inter-ADA Change is Measurement Report with 1C event.

of measuring
• PDP Context activated
• Only Serving HSDPA cell is within Active Set
• Perform FTP transfer and initiate handover between HSDPA capable cells
• The interruption time shall be measured using interface analyser
Assumptions
and pre-
conditions
Formula -
Notes When UE detects much better HSDPA cell then the current HSDPA serving
cell it starts HS-DSCH Cell Change procedure to keep the best
performance. UE can have in the Active Set another HSDPA cell but in the
same time user traffic will be sent only by one serving HSDPA cell. New
Measurement ID (event 1D) is setup after HS-DSCH establishment. It allows
monitoring and informing UTRAN about the best reachable HSDPA cells
within the Active Set. However, when Event 1D is sent in Measurement
Report Active Set Update procedure is not performed.
1/22/2010
Figure 8.9.Message flow Intra-ADA Cell Change

1/22/2010
Figure 8.10.Inter –Adapter Cell Change without old cell deletion message flow
1/22/2010
9. HSPA Throughput for different UL/DL RAB

combinations
9.1 HSPA Throughput for different UL/DL RAB
combinations, 16 QAM
HSPA Throughput for different UL/DL RAB combinations, 16 QAM
Definition That is combination of HSPA throughputs for different UL/DL RAB

combinations. The main HSDPA characterized KPI are for following
UL/DL conditions: 16QAM, 5 codes, 16QAM, 10 codes, 16QAM, 15
codes.
HSUPA task to perform: 16QAM, 15 codes.
Current KPIs are achieving with usage of Peak FTP application HSPA
throughput. BLER target was set to 1% both in UL and DL.
The HSPA Throughput is defined as the actual throughputs on FTP
level in HSPA UL/DL direction over an established bearer in a given
time interval FTP throughput excludes the transmission of TCP and IP
headers on top of each FTP packet.
Methodology of • Test with UE connected to laptop or PC in stationary use

measuring
• PDP context shall be established in advance
• Define appropriate settings in APN and ensure that HLR profile does
not limit Data Rates for USims
• UE in Cell DCH state
• The measurement shall be obtained by averaging an mutually agreed
number of file transfers
Assumptions and • Recommended to put FTP server out of any internal or external
pre-conditions firewalls to definitely avoid NW blocking elements
• The FTP server shall be located directly at the border of the PLMN.
That is for PS services the Gi of the GGSN interface. Additional delays
between the border and the server shall be excluded.
• In order to minimise the impact of the slow start behaviour of TCP, the
measurement shall exclude an appropriate start interval in relation to the
complete file transfer time.
Formula transferred_volume _ UL / DL[bytes]*8

HSPA _ UL/DL =
transfer_time[s]
Related Counters: 92003 NodeB HSDPA (WCDMA BTS)
counters/KPIs’ KPIs:
numbers
1/22/2010
TCP (FTP-DATA) TCP ACK

packet packet
1500 bytes 40 bytes
IP header 20 bytes IP header 20 bytes
TCP header 20 bytes TCP header 20 bytes
FTP payload (data)

1460 bytes
Figure 9.1.IP packets for FTP

1/22/2010
Figure 9.2.FTP download scenario

1/22/2010
9.2 HSPA Throughput, 64 QAM

Methodology of measuring, Assumptions and pre-conditions Formula and Related
counters/KPIs’ numbers are the same as for previous subchapter. Only definitions
part has specifics and presented below.
HSPA Throughput, 64 QAM
Definition HSDPA 64QAM (RAN1643) feature enables higher HSDPA bit rates as
compared to existing QPSK and 16QAM schemes, and it offers possibilities
for subscription differentiation and additional data service revenue.
In addition to a single user peak rate enhancement, the average cell
throughput is also increased, which improves both end-user experience and
overall network efficiency.
3GPP Rel7 introduces 64QAM modulation for HSDPA, which increases the
HSDPA peak data rate up to 21.1 Mbps. New HSDPA terminal categories
13, 14, 17 & 18 support 64QAM. Practical throughput that can be achieved
with this feature is limited by radio reception.
Maximum theoretical throughput 21.1 Mbps of category 14 and category 18
terminals would require the use of coding rate close to one, that is, error-
free reception without error correction coding. Targeting error-free reception
reduces the system efficiency and capacity. In all practical conditions the
throughput will be decreased if used coding rates are close to one.
Quality of radio reception depends on aspects such as received signal
strength, radio channel and interference. 64QAM is even more sensitive to
the quality of radio reception than 16QAM. The link adaptation algorithm in
the BTS (MAC-ehs) selects 64QAM when the channel quality is sufficient
and the UE is 64QAM capable.
64QAM provides 3 -15 % higher average HSDPA cell and user throughput,
depending on the radio conditions and UE receiver.
64QAM is an optional feature for the UE. 64QAM capability is
signaled to RNC in RRC connection setup.
1/22/2010
10. Round Trip Time for FACH, DCH, HS-DSCH,

E-DCH
Round Trip Time for DCH and FACH
Definition The Round Trip Time is defined as the interval between

submission of a datagram (e.g. ICMP ECHO REQUEST)
from the UE, and the reception of the corresponding reply
datagram (e.g. ICMP ECHO REPLY) back at the UE side.
Methodology of • Test with UE connected to a laptop or PC in stationary use

measuring
• Initial status of UE before starting the PING application:
PMM: CONNECTED Iu connection established, RAB
established) using a Background or Interactive PDP context.
• For measurement on the DCH: Before starting the Ping
application ensure that the UE is in CELL_DCH state by
triggering user data transfer (e.g. via FTP), stop the data
transfer and start the Ping application
• Initial ping shall be measured separately and the
consecutive pings shall be averaged
• Round Trip Time (RTT) is measured using the output of a
Ping application (e.g. MS-DOS prompt and its ping
application, e.g. “ping –l size host”) of the used operating
system or with a comparable measurement tool,
• The test is carried out by sending continuous messages to
a server (e.g. FTP or HTTP server) and logging the
reception of the reply from the server at the UE.
• RTT shall be measured with an appropriate automatic
measurement system at the client side.
• One valid measurement sample shall be obtained by
averaging of the 10 RTT values which are valid for each
measuring cycle of the RAB under test.
Assumptions and pre- • The server responding to the ICMP ECHO REQUEST
conditions messages shall be located directly at the Gi interface.
Additional delays between the GGSN and the server shall
be excluded.
Formula -
Notes
numbers
1/22/2010
11. Application-specific Key Performance

Indicators
11.1 SMS Mobile Originated (MO) Delivery Time
SMS MO Delivery Time
Definition The SMS MO Delivery Time is the interval between the

(refer to [3GPP25331]) and the submission of the RRC message
CONNECTION RELEASE at a UE.
Different scenarios are provided by SMS in CS and PS domains
perform different measurements results.

measuring
• Send a short message from the trace UE to another mobile user
within the same mobile network
• Use a short message length of 160 Bytes (characters)
• Short message transfer shall be done on DCH (UTRAN
configuration)
• Verify the SMS delivery time by using a tracing UE
Assumptions and pre- • It is assumed that during the short message transfer no HLR
conditions inter-working is performed in the core network.
Formula -
Notes
numbers
1/22/2010
Figure 11.1.SMS MO CS procedure message flow

1/22/2010
Figure 11.2.SMS MO PS procedure message flow

1/22/2010
11.2 SMS MT Delivery Time

SMS MT Delivery Time
Definition The SMS delivery time MT is the interval between the reception
of a RRC PCH Paging message (refer to [3GPP25331]) and the
reception of the SMS layer 3 message CP-DATA at a UE.
Different scenarios are provided by SMS in CS and PS domains
perform different measurements results.

measuring
• Send a short message from the trace UE to another mobile user
within the same mobile network
• Verify the SMS delivery time by using a tracing UE
• The PAGING procedure as initiated by the core network is
assumed to be successful with the first paging request sent by
the MSC.
Formula -
Notes
numbers
1/22/2010
Figure 11.3.SMS MT CS procedure message flow

1/22/2010
Figure 11.4.SMS MT PS procedure message flow

1/22/2010
11.3 MMS MO Delivery Time

MMS MO Delivery Time
Definition The MMS delivery time is the interval between the submission of
the RRC message CONNECTION REQUEST (refer to
[3GPP25331]) and the sending RRC CONNECTION RELEASE
COMPLETE message after GPRS Detach procedure at a UE.

measuring
• UE status: idle mode, subscriber PS attached
• Send a multimedia message from the trace UE to another
mobile user within the same mobile network
• Size of the multimedia message shall be 100 Kbyte
• Verify the MMS delivery time by using a tracing UE.
• The measurement assumes the usage of the Wireless Session
Protocol (WSP) for MMS.
Formula -
Notes MO MMS includes following sub-procedures: GPRS Attach, PDP

Context Activation, RAB Reconfiguration, Actual MMS Data
transfer, PDP Context Deactivation, GPRS Detach, RAB release.
numbers
1/22/2010
Figure 11.5.Message flow MMS MO procedure

1/22/2010
11.4 MMS MT Delivery Time

MMS MT Delivery Time
Definition The MMS delivery time MT is the interval between the reception
of a RRC PCH Paging message (refer to [3GPP25331]) and the
reception of the MMS content (WSP RSLT, refer to [WSP230]) at
a UE.

measuring
• UE status: idle mode, subscriber CS and PS attached
• “Immediate Retrieval” mode shall be activated in the UE to start
download of MM content automatically after reception of the short
message
• Send a multimedia message to the trace UE from the same
mobile network
• Size of the multimedia message shall be 30 Kbyte
• Verify the MMS delivery time by using a tracing UE.
• The measurement assumes the usage of the Wireless Session
Protocol (WSP) for MMS.
• The PAGING procedure as initiated by the core network is
assumed to be successful with the first paging request sent by
the MSC.
• It is assumed that the MMS notification sent to the UE contains
the full URL for the MMS content. Multiple short message
notifications due to fragmented URL strings (full URL is too long
to be sent in one short message) are excluded.
Formula -
Notes
numbers
1/22/2010
Figure 11.6.Message flow MMS MT procedure, 1/2

1/22/2010
Figure 11.7.Message flow MMS MT procedure, 2/2

1/22/2010
12. Abbreviations
3GPP 3rd Generation Partnership Project (www.3gpp.org)

AAL2 ATM Adaptation Layer 2
ALCAP Access Link Control Application Protocol
ASN.1 Abstract Syntax Notation One
BC Base Station System Mobile Application Part
BS Common Pilot Channel
BSSMAP Dedicated Control CHannel
CFN (CPICH) Received energy per chip divided by in band power density
CN Gateway GPRS Support Node
CPICH High Speed Downlink Packet Access
CRC MSC-Server
CS Public Switched Telephony Network
DCCH Radio Access Network Application Part
DCH (CPICH) Received Signal Code Power
DL Received Total Wideband Power
Ec/No UMTS Terrestrial Radio Access Network
E2E End-to-End
FDD Frequency Division Duplex
FP Frame Protocol
FTP File Transfer Protocol
GGSN Gateway GPRS Support Node
GoS High Speed Downlink Packet Access
HDLC MSC-Server
HLR Public Switched Telephony Network
HSDPA Radio Access Network Application Part
ICMP (CPICH) Received Signal Code Power
IMEI Received Total Wideband Power
IMSI UMTS Terrestrial Radio Access Network
ISUP ISDN User Part
IP Internet Protocol
KPI Key Performance Indicators
L3 Layer 3
MAP Mobile Application Part
MGW Media Gateway
MOC Mobile Originated Call
MMC Mobile Mobile Call
MMS Multimedia Messaging Service
MOS Mean Opinion Score
MSC Mobile Switching Center
MSC-S MSC-Server
MTC Public Switched Telephony Network
NBAP Radio Access Network Application Part
1/22/2010
NE (CPICH) Received Signal Code Power

NM Received Total Wideband Power
PLMN UMTS Terrestrial Radio Access Network
PM Performance Measurement
PN Pseudo Noise
PPP Point-to-Point Protocol
PS Packet Switched
PSTN Public Switched Telephony Network
QoS Quality of Service
RA Routing Area
RAB Radio Access Bearer
RANAP Radio Access Network Application Part
RAS (CPICH) Received Signal Code Power
RAU Received Total Wideband Power
RB UMTS Terrestrial Radio Access Network
RNC Radio Network Controller
RRC Radio Resource Control
RSCP (CPICH) Received Signal Code Power
RTWP Received Total Wideband Power
SGSN Serving GPRS Support Node
SMS Short Message Service
SRB Signalling Radio Bearer
TCP Transmission Control Protocol
TMSI Temporary Mobile Subscriber Identity
TrFO Transcoder Free Operation
TTI Transmission Time Interval
UDI Unrestricted Digital Information
UE User Equipment
UL UpLink
UTRAN UMTS Terrestrial Radio Access Network
VLR Visitor Location Register
1/22/2010
13. References
Reference number Document name
[1] CP RAS SPS CAP IHSPA Adapter Rel. 3
3GPP TS 22.002, V5.x.x, Circuit Bearer Services

[2] (BS) supported by a Public Land Mobile Network
(PLMN)
3GPP TS 22.105, V5.x.x, Service aspects;

[3]
Services and Service Capabilities
3GPP TS 23.ß12, V5.x.x, Location management

[4]
procedures
3GPP TS 23.107, V5.x.x, QoS Concept and

[5]
Architecture
3GPP TS 23.060, V5.x.x, General Packet Radio

[6]
Service (GPRS), Service description, Stage 2
3GPP TS 24.008, V5.x.x, Mobile radio interface

[7] Layer 3 specification, Core network protocols;
Stage 3
3GPP TS 24.011, V5.x.x, Point-to-Point (PP)

[8] Short Message Service (SMS) support on mobile
radio interface
3GPP TS 35.133, V5.x.x, Requirements for

[9]
support of radio resource management (FDD)
3GPP TS 25.331, V5.x.x, Radio Resource

[10]
Control (RRC), Protocol Specification
1/22/2010
3GPP TS 48.008, V5.x.x, Mobile Switching

[11] Centre - Base Station System (MSC-BSS)
interface; Layer 3 specification
ITU-T Recommendation P.862, Perceptual

evaluation of speech quality (PESQ): An
[12]
objective method for end-to-end speech quality
assessment
E2E Network Field Performance for Offer and

[13]
Field Acceptance - Overview for all technologies
E2E Network Field Performance for Offer and

[14] Field Acceptance – UMTS; Measurement
Conditions and Targets
WCDMA RAN Key Performance Indicators, Rel.

[15]
RAS06, Pre-release, Trial, System Library, v.2
RNC Counters – RNW Part, Rel. RAS06, Pre-

[16]
release, Trial, System Library, v.2
RNC Counters – Transport and HW Part, Rel.

[17]
RAS06, Pre-release, Trial, System Library, v.2
Nokia SGSN Counter, Rel. SG6.0 CD2, Product

[18]
Documentation
ETSI TS 102 250-2 V1.4.1; Speech Processing,

Transmission and Quality Aspects (STQ); Part 2:
[19]
Definition of Quality of Service parameters and
their computation

E2E Network Field Performance For Offer and Field Acceptance - I-HSPA Definitions Rel.3

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E2E Network Field Performance For Offer and Field Acceptance - I-HSPA Definitions Rel.3

Uploaded by

Copyright:

Available Formats

1/82 COO RA RD SA NE Network Performance

Pavel Romanenko For internal use only

E2E Network Field

Version: Approved 1.0

Version Date Change Notes

The following persons have collaborated on this document:

Pavel Romanenko COO RA RD SA NE

2. Key Performance Indicators for Voice quality ................ 6

3. Key Performance Indicators for CS Services, Setup

4. Key Performance Indicators for PS Service, Setup,

5. Key Performance Indicators for Service Area Update . 23

6. RRC Connection Establishment Success Rate ............ 29

7. Key Performance Indicators for Mobility ...................... 31

7.7. IHSDPA Serving Cell Change Success Rate.............................................. 44

8. Key Performance Indicators for Data Content

9. HSPA Throughput for different UL/DL RAB

11. Application-specific Key Performance Indicators........ 68

13. References ...................................................................... 81

Definition basic information about trigger points

Methodology of description of measurement procedure

Assumptions and pre- background information, important during measurement

Formula provided for Success and Drop Rates KPIs

Notes additional useful information

Related counters/KPIs’ reference to similar KPIs in document

Message flow provided for time Related counters/KPIs’ numbers for

2. Key Performance Indicators for Voice quality

Definition Voice quality Mean Opinion Score (MOS) is result of a subjective

Notes The mean opinion score (MOS) provides a numerical indication of

3. Key Performance Indicators for CS Services,

Methodology • Test with trace mobile or Uu interface monitor in stationary use

Formula number _ of ( RANAP _ RAB _ ASSIGN _ RESPONSE )

KPI based UTRAN

Figure 3.1 CS ATTACH message flow

3.2 CS Voice AMR Call Setup Success Rate

CS Voice AMR Call Setup Success Rate

Definition Ratio between successfully established CS voice calls (AMR12.2 kbps

Methodology • Test with trace mobile or Uu interface monitor in stationary use

Formula number _ of ( ALERT )

KPI based on UTRAN

3.3 CS Video Call Setup Success Rate

Methodology • Test with trace mobile or Uu interface monitor in stationary use

Formula number _ of ( ALERT )

KPI based UTRAN

3.4 Fast Call Setup Time from Cell_PCH, MOC

Methodology • Test with trace mobile or Uu interface monitor in stationary use

3.5 Fast Call Setup Time from Cell_PCH, MTC

Methodology • Test with trace mobile or Uu interface monitor in stationary use

3.6 CS Voice Call Drop Rate

Methodology • Test with trace mobile or Uu interface monitor in stationary use

Formula number _ of (CONNECT _ ACKNOWLEDGE − DISCONNECT )

3.7 CS Video Call Drop Rate

Methodology • Test with trace mobile or Uu interface monitor in stationary use

Formula number _ of (CONNECT _ ACKNOWLEDGE − DISCONNECT )

4. Key Performance Indicators for PS Service,

4.1 PS RAB Establishment Success Rate

PS RAB Establishment Success Rate

Methodology • Test with trace mobile

Formula number _ of ( RANAP _ RAB _ ASSIGN _ RESPONSE )

KPI based on Core,

Figure 4.1.PS RAB Establishment procedure message flow

4.2 PS call Setup Success Rate

Methodology • test with UE/laptop or PC