Events in tems products

Prepared by: Date: Document:
Ascom Network Testing 2/26/2014 NT13-21914
© Ascom (2014)
TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.
No part of this document may be reproduced in any form without the written permission of the copyright holder.
The contents of this document are subject to revision without notice due to continued progress in methodology, design and
manufacturing. Ascom shall have no liability for any error or damage of any kind resulting from the use of this document.
Events in TEMS Products

© Ascom (2014) Document:
NT13-21914
Contents
1 Introduction................................................................ 1
1.1 Product Versions Covered by This Document .......................1
2 GSM/WCDMA/LTE/TD-SCDMA Events..................... 1
2.1 Event List ..................................................................................2
3 GSM and WCDMA Call Events: Detailed
Description ............................................................... 27
3.1 Introduction.............................................................................27
3.2 Event State Machine...............................................................27
3.3 Description of Call Events .....................................................29
3.3.1 Call Initialization........................................................................29
3.3.2 Call Attempt..............................................................................29
3.3.3 Call Attempt Retry.....................................................................29
3.3.4 Call Setup.................................................................................30
3.3.5 Call Established........................................................................30
3.3.6 Call Re-established...................................................................30
3.3.7 Call End....................................................................................30
3.3.8 Blocked Call..............................................................................31
3.3.9 Dropped Call.............................................................................32
4 CDMA Events ........................................................... 33
4.1 Algorithm for Pilot Pollution and Missing Neighbor
Detection in CDMA .................................................................37
5 Overviews of Selected Event Families ..................38
5.1 Cell Reselection/Neighbor Measurements............................38
5.2 RAT Transition Events ...........................................................39
6 Data Service Testing Events...................................40
6.1 General....................................................................................40
6.2 Notes on KPIs for Particular Data Services ..........................40
6.3 Notes on KPI Definitions in ETSI Specification ....................40
6.4 Event List ................................................................................41
7 Media Quality Events...............................................51

NT13-21914 1(51)
1 Introduction
This document describes events that are generated in TEMS products. The
material is derived from TEMS Investigation documentation but is equally
valid for TEMS Symphony and TEMS Automatic as detailed in section 1.1
(except for occasional minor details, which are noted individually in the
document).
Please note, however, that it is not necessarily possible for every single
event listed here to be generated in all of the products; this depends, for
one thing, on what services each product supports.
1.1 Product Versions Covered by This Document
The present document is valid for:
 TEMS Investigation 15.3
 TEMS Symphony 7.2
 TEMS Automatic 9.2
2 GSM/WCDMA/LTE/TD-SCDMA Events
Events in this category are generated by devices supporting at least one of
the technologies GSM, WCDMA, LTE, and TD-SCDMA.
The following is to be noted:
 For TD-SCDMA devices a subset of the listed events can be generated
(in both TD-SCDMA and GSM mode). The extra information given in the
table is rarely provided with events originating from TD-SCDMA
devices. There are also a number of TD-SCDMA specific events.
Call events also encompass VoIP calls. For convenience, this is covered in
the present section rather than in chapter 6, “Data Service Testing Events”.
The asterisk column uses the following codes:
Code Meaning
c Requires that a cell file has been loaded.
e Generated in EDGE mode.
g Generated in GSM mode.
ga Generated by GAN-capable device interacting with a GANC.
lte Generated in LTE mode.
ps Generated for packet-switched (specifically, VoIP calls).
sg Generated during GSM scanning.

NT13-21914 2(51)
Code Meaning
sw Generated during WCDMA scanning.
td Generated in TD-SCDMA mode (and unique to that mode).
w Generated in WCDMA mode.
2.1 Event List
Event Name Symb. * Description/Extra Information
Authentication
Failure
g
w
The authentication or ciphering failed.
Can be generated for both packet-
switched and circuit-switched.
Extra information: GMM/MM cause (if
available).
Baton Handover td Successful baton handover in
TD-SCDMA.
Baton Handover
Failure
td An attempted baton handover in
TD-SCDMA failed.
Call events (Blocked Call; Call*; Dropped Call): Some of these events are also
generated for VoIP. They are marked “ps” in the asterisk column. The extra
information sent with VoIP call events does not include or block/drop type or any
cause values; it does however include certain other items listed below.
Most of these events have a piece of extra information “Call Domain”, which is
either “Circuit Switched” or “Packet Switched”. This is not repeated for the
individual events below.
Blocked Call
(red)
g
w
ga
ps
GSM/WCDMA/TD-SCDMA: Call
abnormally ended prior to Call Established
event (for example because all traffic
channels were busy).
GAN: Layer 3 message Activate Channel
Failure received prior to Call Established.
Extra information:
• Block type
• CC cause
• RR cause
• Call time (time since Call Initiation
event)

NT13-21914 3(51)
Call Attempt
(gray)
g
w
ga
ps
GSM: A traffic channel was requested
(through the Layer 3 message Channel
Request). (Note that the request could
also be for a signaling channel, in which
case no call is actually attempted; the two
types of request cannot be distinguished.)
WCDMA/TD-SCDMA: An RRC
Connection Request was sent following
initiation of an MO or MT call.
GAN:
• (MO call) GAN Layer 3 message
Request sent with establishment cause
64 (TCH/H sufficient) or 224 (TCH/F
needed).
• (MT call) GAN Layer 3 message Paging
Request received.
PS: Triggered by SIP Invite Request.
Call Attempt Retry
(gray)
g
w
A call attempt (see the event Call Attempt)
was repeated. Triggered by Channel
Request/RRC Connection Request.
Call End g
w
ps
A call was terminated. This event is
normally triggered by
• (CS:) the CC message Release
• (PS:) the message SIP Bye.
Extra information:
• Call end cause (usually one of “MS
initiated release”, “NW initiated
release”, “User busy”)
• Call duration
Call Established
(green)
g
w
ga
ps
A call was established. The event is
triggered by
• (GSM/WCDMA/TD-SCDMA:) the
Layer 3 message Connect (MO call) or
Connect Acknowledge (MT call)
• (GAN:) the Layer 3 message Activate
Channel Complete
• (PS:) the message SIP Invite Response
with status code 200 = OK.
Call Initiation g
w
An MO call was initiated by a script (the
equivalent of the “yes” button being
pressed on the handset). This event is
normally triggered by a report from the PC
communication protocol, never by a
Layer 3 message.
This event precedes Call Attempt.

NT13-21914 4(51)
Call Re-established
(green)
g
w
Following a radio link failure, a call was re-
established (a drop thus being prevented).
Technology-specific details:
GSM: New traffic channel assigned within
20 s.  3GPP 45.008, section 6.7.2
WCDMA: New traffic channel assigned
before T314 timer expired.  3GPP
25.331, section 8.3.1.13
This event can occur only if call re-
establishment is enabled in the network. If
it is not, a call will be automatically
dropped in this situation.
Call Setup g
w
ga
ps
A call was set up by the device. The event
is triggered by
• (GSM/WCDMA/TD-SCDMA:) one of the
Layer 3 messages Alerting or Connect
• (GAN:) the GAN Layer 3 message
Activate Channel
• (PS:) the message SIP Invite Response
with status code 180 = Ringing.
Extra information:
• Call direction (MO/MT)
• Call setup time (measured from Call
Attempt, i.e. the first call attempt)
• User setup time (measured from Call
Initiation, thus more accurately
reflecting the user-perceived setup
time; obtained only for MO calls in
scripts)
Cell Change Order
From UTRAN
g Successful cell change order: handover
from UTRAN to GSM packet data
channel. Generated after entering GSM
mode.
Only occurs when the change takes place
from Cell_DCH mode. If it takes place
from a Common channel, the event Cell
Reselection From UTRAN is generated
instead.
Cell Change Order
From UTRAN Failure
w Cell change order from UTRAN failed.
Cell Reselection g
w
Cell reselection within GSM or within
UTRAN (intra-frequency).
Extra information (GSM): BCCH ARFCN
and BSIC of new cell.

NT13-21914 5(51)
Cell Reselection
From UTRAN
g Cell reselection from UTRAN to GSM.
Generated after entering GSM mode.
Cell Reselection To
EUTRAN
lte Cell reselection from UTRAN or GSM to
EUTRAN. Generated after entering LTE
mode.
Extra information:
• New cell EARFCN and PCI
• Old cell UARFCN and SC (WCDMA) or
ARFCN and BSIC (GSM)
Cell Reselection To
UTRAN
w Cell reselection from GSM to UTRAN.
Generated after entering WCDMA mode.
Channel Switch From
HSDPA
td Successful switch from HS-PDSCH to
DPCH.
Channel Switch From
HSDPA Failure
td Switch from HS-PDSCH to DPCH failed.
Channel Switch To
HSDPA
td Successful switch from DPCH (3GPP
Release 99) to HS-PDSCH.
Channel Switch To
HSDPA Failure
td Switch from DPCH to HS-PDSCH failed.
Compressed Mode
Entered
w The device entered compressed mode.
Compressed Mode
Exited
w The device left compressed mode.
CS Call Initiated on
IP Call Request
(Incoming)
g
w
A VoIP (IP) call was requested by the
user, but instead a CS voice call was
initiated by the UE.
CS Call Initiated on
IP Call Request
(Outgoing)
g
w
Answering of a VoIP (IP) call was
intended by the user, but instead the UE
answered it by initiating a CS voice call.

NT13-21914 6(51)
CSFB events: Some of these events have a piece of extra information “Call
Domain”, which however always takes the value “Circuit Switched”. The CS
fallback events are generated only in the CS domain.
CSFB Blocked Call
(red)
g
w
lte
A CS fallback call was blocked. This can
happen in several ways:
• The Extended Service Request timed
out without any response from network,
or the network responded with Service
Reject. In this case the CS fallback
procedure never reaches the RAT
change stage.
• RAT change to UTRAN/GERAN failed,
as indicated by the event EUTRAN
RRC Connection Release Redirected
Failure.
• After successful RAT change to
UTRAN/GERAN, the CS call setup
failed (CS “Blocked Call” event
generated).
Extra information:
• Block type
Regarding CS fallback in general, see
 3GPP 23.272.
CSFB Call Attempt
(gray)
lte A CS fallback call attempt was made.
Triggered by Layer 3 message NAS
Extended Service Request.
Extra information:
CSFB Call
Established (green)
g
w
A CS fallback call was established.
Triggered by the Layer 3 message
Connect (MO call) or Connect
Acknowledge (MT call).
Extra information:
• Target technology (WCDMA/GSM)

NT13-21914 7(51)
CSFB Call Initiation lte A CS fallback call was initiated by a
Service Control script. This event is
normally triggered by a report from the PC
communication protocol, never by a
Layer 3 message.
This event is generated if the device has
previously performed Combined EPS/IMSI
Attach, thereby notifying the network that
it desires to be able to make CS fallback
calls. If no such attach command has
been observed, the event is not
generated.
CSFB Call Setup g
w
A CS fallback call was set up. Triggered
by Layer 3 message Alerting.
Extra information:
• Target technology (WCDMA/GSM)
• Call setup time (measured from CSFB
Call Attempt, i.e. the first call attempt)
• User setup time (measured from CSFB
Call Initiation, thus more accurately
reflecting the user-perceived setup
time. Obtained only for MO calls in
scripts. If no CSFB Call Initiation event
was generated, the user setup time
cannot be computed.)
CSFB During IP Call
Setup
g
w
The call setup procedure was initiated as
a VoIP (IP) call, but before the call setup
was completed, the call setup procedure
was handed over to the CS domain.
Datalink Failure g Datalink failure caused by unsolicited
Disconnected Mode response or
sequence error.
Dedicated Mode g The device entered dedicated mode.
Extra information: BCCH ARFCN and
BSIC.
Dropped Call g
w
Call abnormally ended after Call
Established event.
Extra information:
• Drop type
• Cause
• CC cause
• Call duration (time since Call
Established event)

NT13-21914 8(51)
EGPRS MS Out Of
Memory
e The device’s status buffer filled up, so that
the device is no longer able to use
Incremental Redundancy on the downlink
for link quality control. Consequently it is
forced to switch to using Link Adaptation.
Emergency Call
Failure
g
w
This event is generated for an emergency
call (after call end) if its duration was
shorter than 35 s. The call is then
regarded as failed because it is not certain
that a position fix was obtained within
such a short time.
Detailed trigger conditions: Step 1 as for
Emergency Call Success, but duration
criteron not satisfied in step 2.
Emergency Call
Success
g
w
This event is generated for an emergency
call (after call end) if it had a duration of at
least 35 s. It can then be regarded as
certain that a position fix was obtained.
Detailed trigger conditions:
GSM:
1. CM Service Request sent with Service
Type = 2 (“Emergency call
establishment”).
2. Call successfully set up and maintained
for at least 35 s (counting from step 1)
with TCH available without a break
throughout this time.
WCDMA:
1. RRC Connection Request sent with
establishment cause = “Emergency
call”.
2. Call successfully set up and maintained
for at least 35 s (counting from step 1)
with TCH available without a break
throughout this time.

NT13-21914 9(51)
EPS events: Some of these, tagged “lg” below, are unique to LG chipset devices.
EPS NAS Signaling
Failure
lte
lg
EPS NAS signaling failed.
Extra information: Details the nature of
the failure, e.g.:
“Release with cause Load Balancing TAU
Required by network”
“Release with cause Redirection by
network”
“Data transmission failure caused by RRC
mobility”
“Service loss”
EPS NAS Timer
Expiry
lte
lg
An EPS NAS timer expired.
Extra information: “Timer T<nnnn>
expired”, where <nnnn> = 3411, 3402,
etc.
EPS RACH Failure lte
lg
An EPS random access procedure failed.
EPS RACH Success lte
lg
An EPS random access procedure
succeeded.
EPS Radio Problem lte
lg
An EPS NAS radio problem occurred. This
event partially overlaps with EPS RRC
Timer Expiry.
Extra information: Problem cause, e.g.:
“MAC out of sync”
”RLC max RETX”
“Integrity failure”
“Timer T300 expired”
EPS RRC Timer
Expiry
lte
lg
An EPS RRC timer expired.
Extra information: “Timer T<nnn>
expired”, where <nnnn> = 300, 301, 304,
etc.
EPS TDD UL/DL
Configuration
Changed
lte TDD subframe configuration changed.
 3GPP 36.211, table 4.2-1
Extra information:
• Old subframe configuration
• New subframe configuration
Each subframe configuration is
represented as a string where U = uplink,
D = downlink, and S = special subframe.
Example: “D:S:U:U:U:D:S”.

NT13-21914 10(51)
EPS Transmission
Mode Changed
lte Change of EPS transmission mode.
Compare the LTE information element
Transmission Mode.
EUTRAN ANR
Neighbor Reported
lte The device reported CGI for a cell
identified as a missing neighbor by the
Automatic Neighbor Relation mechanism.
 3GPP 36.300, sections 22.3.2a,
22.3.3–4; 3GPP 36.331, section 5.5
Extra information: Type of ANR
neighbor: intra-frequency, inter-frequency,
or Inter-RAT.
EUTRAN Attach
Complete
lte The device successfully attached to
EUTRAN. Triggered by EPS Attach
Complete.
Extra information:
• Attach type: EPS attach result in Attach
Accept message
• Attach time: Time from Attach Request
to Attach Complete
EUTRAN Attach
Failure
lte Attach to EUTRAN failed. Triggered by
Attach Reject or timeout.
Extra information:
• Attach type
• Failure cause
EUTRAN Detach
Accept
lte The device successfully detached from
EUTRAN. Triggered by EPS Detach
Accept.
Extra information:
• Attach type detached from
• Detach time: Time from Detach
Request to Detach Accept
EUTRAN Inter-
frequency Handover
lte Intra-RAT, inter-frequency, handover
signaled by the eNodeB.  3GPP 36.331,
section 5.3.5.4
Triggered by Layer 3 message RRC
Connection Reconfiguration with
targetPhyCellId differing from serving cell
ID, and on different EARFCN.
Extra information:
• Old EARFCN, new EARFCN
• Old cell ID, new cell ID
• Handover interruption time

NT13-21914 11(51)
EUTRAN Inter-
frequency Handover
Failed
lte Intra-RAT, inter-frequency, handover
failed. Triggered by expiry of the T304
timer configured in the RRC Connection
Reconfiguration message.  3GPP
36.331, section 5.3.5.6
Extra information:
• Old EARFCN, new EARFCN
EUTRAN Intra-
frequency Handover
lte Intra-RAT, intra-frequency, handover
signaled by the eNodeB.  3GPP 36.331,
section 5.3.5.4
Triggered by Layer 3 message RRC
Connection Reconfiguration with
targetPhyCellId differing from serving cell
ID, but on same EARFCN.
Extra information:
• EARFCN
EUTRAN Intra-
frequency Handover
Failed
lte Intra-RAT, intra-frequency, handover
failed. Triggered by expiry of the T304
timer configured in RRC Connection
Reconfiguration message.  3GPP
36.331, section 5.3.5.6
Extra information:
• EARFCN
EUTRAN Reselection
Time After CSFB Call
lte This event carries performance
information on the switch back to LTE
after hangup of a CS fallback call.
Extra information:
• Idle to LTE time: Time in seconds from
entering idle mode (in UMTS) to
reception of System Information Block
on LTE.
• SIB 19 to LTE time: Time in seconds
from reception of System Information
Block Type 19 (UMTS) to reception of
System Information Block on LTE.

NT13-21914 12(51)
EUTRAN RRC A1
Event
lte Measurement Report containing A1 event
sent from device: serving cell is better
than threshold.  3GPP 36.331, section
5.5.4.2
Extra information: Serving cell readings.
EUTRAN RRC A2
Event
sent from device: serving cell is worse
than threshold.  3GPP 36.331, section
5.5.4.3
Extra information: Serving cell readings.
EUTRAN RRC A3
Event
sent from device: neighbor is offset better
than serving cell.  3GPP 36.331, section
5.5.4.4
Extra information: Serving cell and
neighbor readings.
EUTRAN RRC A4
Event
sent from device: neighbor is better than
threshold.  3GPP 36.331, section
5.5.4.5
Extra information: Neighbor readings.
EUTRAN RRC A5
Event
sent from device: serving cell is worse
than threshold1 and neighbor is better
than threshold2.  3GPP 36.331, section
5.5.4.6
Extra information: Serving cell and
neighbor readings.
EUTRAN RRC
Connection Reject
lte An RRC connection was rejected.
EUTRAN RRC
Connection Release
Redirected Attempt
lte An RRC connection was redirected.
Triggered by EPS RRC Connection
Release message with redirection flag.
Extra information: Redirection control
information from RRC Connection
Release message.
EUTRAN RRC
Connection Release
Redirected Failure
lte Redirection of RRC connection failed; the
device returned to EUTRAN without
successful new connection setup.

NT13-21914 13(51)
EUTRAN RRC
Connection Release
Redirected Success
lte
w
g
1
Successful new connection setup
following EPS RRC Connection Release
message with redirection flag. Triggered
by one these messages:
• WCDMA: RRC Connection Setup
Complete
• GSM: Immediate Assignment
• GPRS/EDGE: Packet Uplink/Downlink
Assignment
• EV-DO: Traffic Channel Complete
• 1x: Service Connect
Extra information:
• Technology and cell to which the device
was redirected.
• Redirection control information from
RRC Connection Release message.
• RRC Reconnect Time, measured from
RRC Connection Release to the
relevant message above.
EUTRAN RRC
Established (green)
lte An RRC connection was established.
Triggered by RRC Connection Setup
Complete message.
Extra information: Establishment cause.
Handover g Successful inter-cell handover in GSM.
Handover Failure g Inter-cell handover in GSM failed.
Handover From
EUTRAN
w Successful handover from EUTRAN to
UTRAN. Generated after entering
WCDMA mode.
Extra information:
• Handover type: PS or SRVCC
• Source RAT, target RAT
• Handover interruption time, measured
from Mobility From EUTRA Command
(with Handover To UTRAN indication)
to Handover To UTRAN Complete.
Handover From
EUTRAN Failure
lte Handover from EUTRAN to UTRAN failed.
1
Also occurs in 1x and EV-DO in case of redirection to either of these technologies.

NT13-21914 14(51)
Handover From GAN ga Successful handover from GAN to
GERAN (GSM).
Triggered by GAN Layer 3 message
Handover Command if followed by
Deregister or if a period of 2 s passes
without Handover Failure being received.
Handover From GAN
Failure
ga Handover from GAN to GERAN (GSM)
failed.
Handover Failure.
Handover From
UTRAN
g Successful handover from UTRAN to
GSM. Generated after entering GSM
mode.
Handover From
UTRAN Failure
w Handover from UTRAN to GSM failed.
Handover Intracell g Successful intra-cell handover in GSM.
Handover Intracell
Failure
g Intra-cell handover in GSM failed.
Handover To
EUTRAN
lte Successful handover from UTRAN to
EUTRAN. Generated after entering LTE
mode.
Extra information: Handover interruption
time, measured from “Handover From
UTRAN Command-EUTRA” to “RRC
Reconfiguration Complete”.
Handover To
EUTRAN Failure
w Handover from UTRAN to EUTRAN failed.
Handover To GAN ga Successful handover from GERAN (GSM)
to GAN.
Handover Complete.
Handover To GAN
Failure
ga Handover from GERAN (GSM) to GAN
failed.
Triggered if TU3920 timer expires after
Handover Access without Handover
Complete being received. TU3920 is a
timer included in the Register Accept
message sent from the GANC.
Handover To UTRAN w Successful handover from GSM to
UTRAN. Generated after entering
WCDMA mode.

NT13-21914 15(51)
Handover To UTRAN
Failure
g Handover from GSM to UTRAN failed.
HS Serving Cell HO w Successful HSPA serving cell handover.
The same symbol is used as for Inter-
frequency Handover, since HSPA serving
cell handover is handled in a similar way
(and differently from UMTS soft
handover).
HS Serving Cell HO
Failure
w HSPA serving cell handover failed.
The same symbol is used as for Inter-
frequency Handover Failure (compare HS
Serving Cell HO).
Idle Mode g The device entered idle mode.
BSIC.
Inter-frequency Cell
Reselection
w Successful WCDMA inter-frequency cell
reselection.
Extra information: New UARFCN; new
SC.
Inter-frequency
Handover
w
td
Successful inter-frequency handover in
WCDMA or TD-SCDMA.
Extra information: New UARFCN.
Inter-frequency
Handover Failure
w
td
Inter-frequency handover in WCDMA or
TD-SCDMA failed.
Intra-frequency Hard
Handover
w
td
Successful intra-frequency hard handover
in WCDMA or TD-SCDMA.
Intra-frequency Hard
Handover Failure
w
td
Intra-frequency hard handover in WCDMA
or TD-SCDMA failed.
Limited Service Mode g The GSM device entered limited service
mode (emergency calls only).
Location Area
Update
g
w
The device changed location areas.
Extra information: Location update type
(LUT).
Location Area
Update Failure
g
w
The device failed to change its location
area.
Extra information: Cause; location
update type (LUT).

NT13-21914 16(51)
Measurement
Report 1
w Intra-frequency measurement report sent
from device (UMTS reporting events “1A”,
“1B”, etc.).  3GPP 25.331, section 14.1
Extra information: Type of UMTS event.
Measurement
Report 2
w Inter-frequency measurement report sent
“2B”, etc.).  3GPP 25.331, section 14.2
Measurement
Report 3
w Inter-RAT measurement report sent from
device (UMTS reporting events “3A”, “3B”,
etc.).  3GPP 25.331, section 14.3
Measurement
Report 4
w Traffic volume measurement report sent
“4B”).  3GPP 25.331, section 14.4
Measurement
Report 5
w Quality measurement report sent from
device (UMTS reporting event “5A”).
 3GPP 25.331, section 14.5
Measurement
Report 6
w UE-internal measurement report sent from
device (UMTS reporting events “6A”, “6B”,
etc.).  3GPP 25.331, section 14.6
Measurement
Report 7
w UE positioning measurement report sent
“7B”, etc.).  3GPP 25.331, section 14.7

NT13-21914 17(51)
Missing GSM
Neighbor (yellow
bar on
the right)
sg This is a GSM event based on scan data
that includes decoded BSIC and System
Information. The event does not require a
cell file.
It is assumed that the strongest cell with
decoded BSIC is the serving cell. Among
other cells with decoded BSIC, the six
strongest ones are looked up in the
strongest cell’s neighbor list (which is
extracted from System Information
messages). For each cell that is not in the
neighbor list, an instance of this event is
generated.
The event is only generated once for each
combination of assumed serving cell
(ARFCN + BSIC) and missing neighbor
(ARFCN).
BSIC of serving cell; ARFCN, BSIC, and
signal strength (in dBm) of missing
neighbor.
Missing GSM
Neighbor, GSM
Symmetry
(yellow
bar on
the right)
g This is a GSM event based on UE data. It
does not require a cell file.
Triggered in when the source cell of a
handover is not in the target cell’s
neighbor list.
Cells are compared with respect to
ARFCN and BSIC. If BSIC is not
available, the event will not be triggered.
The event triggering is delayed two
seconds after the handover to ensure that
the entire neighbor list of the target cell
has been received.
Extra information: Serving cell ARFCN
and BSIC (i.e. new serving cell after
handover); missing neighbor ARFCN and
BSIC (i.e. old serving cell prior to
handover).

NT13-21914 18(51)
Missing LTE
Neighbor (yellow
bar on
the right)
This event is based on LTE scan data. It
requires that a cell file is loaded and that
the currently strongest cell has a neighbor
list defined in that file.
Triggered in the following cases:
1. A cell not defined as a neighbor of the
strongest cell is more than n dB
stronger than at least one neighbor of
the strongest cell. The margin n dB is
set in the General window under LTE
(TEMS Investigation specific remark).
strongest cell is within n dB of the
strongest cell. (The event is then
triggered regardless of the strength of
defined neighbors.)
3. No cell from the strongest cell’s
neighbor list is detected, but at least
one cell is detected besides the
that cell.)
The signal power measure used in the
comparisons is RSRQ.
Extra information: EARFCN plus the
following (different for each of the three
cases listed above):
• Case 1: Defined neighbor Cell Identity
and RSRQ; missing neighbor Cell
Identity and RSRQ.
• Case 2: Strongest cell Cell Identity;
missing neighbor Cell Identity and
RSRQ.
• Case 3: Strongest cell Cell Identity;
missing neighbor Cell Identity.

NT13-21914 19(51)
Missing TD-SCDMA
Neighbor (yellow
bar on
the right)
This event is based on TD-SCDMA scan
data. It requires that a cell file is loaded
and that the currently strongest cell has a
neighbor list defined in that file.
set in the General window under
TD-SCDMA (TEMS Investigation
specific remark).
defined neighbors.)
that cell.)
comparisons is Ec/Io.
Extra information: UARFCN plus the
• Case 1: Defined neighbor CPID and
Ec/Io; missing neighbor CPID and
Ec/Io.
• Case 2: Strongest cell CPID; missing
neighbor CPID and Ec/Io.
• Case 3: Strongest cell CPID; missing
neighbor CPID.

NT13-21914 20(51)
Missing WCDMA
Intra-frequency
Neighbor
(yellow
bar on
the right)
w This is a WCDMA event based on UE
data. The event does not require a cell
file.
1. The strongest active set member lies
between –18 dB and –12 dB, and the
strongest detected neighbor is stronger
than –12 dB.
2. The strongest active set member is
stronger than –12 dB, and the strongest
detected neighbor is stronger than
–12 dB.
3. A detected neighbor exists, although no
active set member or monitored
neighbor exists.
The signal strength measure used in the
comparisons is CPICH Ec/No.
Extra information:
• Cases 1 and 2 above: Priority (“1” and
“2” respectively); strongest active set
member SC and Ec/No; missing
neighbor SC and Ec/No.
• Case 3: Missing neighbor SC and
Ec/No.

NT13-21914 21(51)
Missing WCDMA
Neighbor (yellow
bar on
the right)
(c)
sw
This event is based on WCDMA scan
data. It requires either
• that the scan data includes decoded
SIBs, or
• that a cell file is loaded and that the
currently strongest cell has a neighbor
list defined in that file.
If both SIB and cell file data are available,
the SIBs are used and the cell file is
ignored.
set in the General window under
WCDMA (TEMS Investigation specific
remark).
defined neighbors.)
that cell.)
comparisons is Aggr Ec.
Extra information: UARFCN plus the
• Case 1: Defined neighbor SC and
Ec/Io; missing neighbor SC and Ec/Io.
• Case 2: Strongest cell SC; missing
neighbor SC and Ec/Io.
• Case 3: Strongest cell SC; missing
neighbor SC.

NT13-21914 22(51)
More Than 3 Strong
SCs (red bar
on the
right)
sw This event is based on WCDMA scan
data.
The information element Poss No of AS
Members (with argument = power
threshold n dB governed by the Missing
Neighbor Margin setting in the General
window under WCDMA) is larger than 3,
and all the detected scrambling codes are
stronger than –100 dBm. (TEMS
Investigation specific mechanism.)
Extra information: UARFCN.
No Service Mode g The device entered no service mode,
since it could not find a control channel.
Packet Mode g The device entered packet mode
(switched to a PDCH).
BSIC.
PDP Context
Activation
g
w
A PDP context was successfully activated.
Extra information:
Setup time, counted from the first RRC
Connection Request message to Activate
PDP Context Accept.
PDP context completion time, counted
from the first Activate PDP Context
Request message to Activate PDP
Context Accept.
PDP Context
Activation Failure
g
w
Activation of a PDP context failed.
Extra information: Failure cause.
PDP Context
Deactivation
g
w
An active PDP context was deactivated.
PDU Error g Protocol Data Unit error caused by syntax
error in Layer 3 message.
PS Attach g
w
The device successfully attached to the
packet service.
Extra information: Attach type; attach
completion time.

NT13-21914 23(51)
PS Attach Failure 2 g
w
The device failed to attach to the packet
service.
Extra information: Attach type; failure
cause.
PS Channel Type
Switch Complete
w A switch between a dedicated data
channel and a common data channel
succeeded.
Extra information: Direction of switch:
“Dedicated to Common” or “Common to
Dedicated”.
PS Channel Type
Switch Failure
w A switch between a dedicated data
channel and a common data channel
failed.
Extra information: Direction of switch:
“Dedicated to Common” or “Common to
Dedicated”.
PS Data Interruption
Time Due To CSFB
g
w
This event reports the IP interruption time
during RAT change to UTRAN/GERAN
due to initiation of a CS fallback call.
Always generated in conjunction with the
IP Interruption event (TEMS Investigation
specific remark).
Extra information: Interruption time in
ms. Measured from last received IP
packet in EUTRAN to first received IP
packet in UTRAN/GERAN.
PS Detach g
w
The device successfully detached from
the packet service.
PS RAB Channel
Rate Switch
Complete
w The spreading factor, and hence the data
rate, was changed successfully for the
radio access bearer.
Extra information: Uplink and downlink
spreading factors.
PS RAB Channel
Rate Switch Failure
w A change of spreading factor failed for the
radio access bearer.
Extra information: Uplink and downlink
spreading factors.
Radio Bearer
Reconfiguration
Failure
w The device could not reconfigure the radio
bearer.
Extra information: Cause value.
2 Retained here although a similar event exists among the data service testing events (see
chapter 6). The latter (only) is used as input to KPIs.

NT13-21914 24(51)
Radio Bearer Setup
Failure
w The device could not set up the radio
bearer.
Radio Link Addition w One or several radio links were added.
Extra information: Added scrambling
codes; soft handover type; event type.
Radio Link Addition
Failure
w Addition of one or several radio links
failed.
Radio Link Removal w One or several radio links were removed.
Extra information: Removed scrambling
codes; event type.
Radio Link Removal
Failure
w Removal of one or several radio links
failed.
Radio Link
Replacement
w Combined addition and removal of radio
links.
Extra information: Added scrambling
codes; removed scrambling codes; soft
handover type; event type.
Radio Link
Replacement Failure
w Addition or removal of one or several radio
links failed.
Ringing g The GSM device started emitting a ringing
signal.
Routing Area Update g
w
The device changed routing areas.
Routing Area Update
Failure
g
w
The device failed to change its routing
area.
Rove In To GAN ga Successful reselection from GSM to GAN.
Register Accept.
Rove In To GAN
Failure
ga Reselection from GSM to GAN failed.
Register Reject or by the TU3904 timer
expiring after Register Request is sent.

NT13-21914 25(51)
Rove In To GAN
Redirect
ga When reselecting from GSM to GAN, the
device was redirected from the default
GANC to a different GANC.
Register Redirect.
Rove Out From GAN ga Successful reselection from GAN to GSM.
Deregister.
Rove Out From GAN
Failure
ga Reselection from GAN to GSM failed.
Triggered when the information element
“GA-RC/GA-CSR State” switches to
Deregistered without Deregister message
being received. (TEMS Investigation
specific remark.)
RRC Connection
Abnormal Release
w An RRC connection was abnormally
released.
RRC Connection
Reject
w An RRC connection was rejected.
 3GPP 25.331, section 10.3.3.31
RRC Established
(green)
w An RRC connection was established.
Triggered by RRC Connection Setup
Complete message.
Extra information: Establishment cause.
RRC Protocol Error
(red)
w An RRC protocol error occurred.
Scanning Mode sg The GSM device entered scanning mode,
i.e. it started some type of scanning.
Security Mode
Failure
w A security mode command failed.
SHO Procedure
Complete
w Soft handover: Active set update
procedure completed with Measurement
Control message.
SHO Procedure
Complete Without
Measurement Control
w Soft handover: Active set update
procedure completed without a
Measurement Control message (because
another soft handover procedure started).
Extra information: One of “Addition”,
“Removal”, “Replacement”.

NT13-21914 26(51)
Silent Call g
w
A silent call was detected by the AQM
algorithm: all system signaling was OK,
but the audio was not transferred in both
directions. The event is triggered 27.5 s
after the last Stop DTMF Acknowledge
message.
See the document “AQM in TEMS
Products”.
SMS Error g
w
Transfer of an SMS message failed
(during either sending or receiving).
SMS Received g
w
An SMS message was successfully
received.
SMS Sent g
w
Sending of an SMS message was
successfully competed.
T200 Expired g A Layer 2 Timeout occurred.
T3126 Expired g A Channel Request Timeout occurred.
T3162 Expired g A Packet Queuing Timeout occurred.
T3168 Expired g A Packet Assignment Timeout occurred.
T3170 Expired g A Packet Channel Request Timeout
occurred.
VCC Handover From
EUTRAN
w
g
3
Voice Call Continuity handover of VoLTE
call from EUTRAN to UTRAN/GERAN.
Extra information: Handover type:
SRVCC (Single Radio VCC) or DRVCC
(Dual Radio VCC).
3 Also occurs in 1x and EV-DO in case of redirection to either of these technologies.

NT13-21914 27(51)
3 GSM and WCDMA Call Events:
Detailed Description
3.1 Introduction
This chapter provides an in-depth description of how GSM and WCDMA
call events are generated. By “calls” are meant voice calls as well as video
calls (the latter in WCDMA only).
The document should be regarded as supplementary to the account of the
call events in chapter 2.
3.2 Event State Machine
When explaining the generation of call events, it is helpful to refer to the
state machine depicted below.

NT13-21914 28(51)
The state machine covers both WCDMA and GSM. The top left part shows
the WCDMA service setup, while the top right part shows the service setup
in GSM. Note that these setup procedures are generic and not unique to
the speech service. MO calls are represented by states 1-4-10; MT calls
are represented by states 6-9-7-8-10. The central part of the diagram,
including states 11 and 12, is concerned with the handling of call
disconnects.
(0) NULL
States
4, 7, 8, 9, 10
(11) DISCONNECT
REQUEST
(10) ACTIVE
(4) CALL
DELIVERED
(1) CALL INIT Setup (UL)
Alerting
Connect
(6) CALL
PRESENT
(9) MT CALL
CONFIRMED
Disconnect (UL)
Disconnect (DL)
(12) DISCONNECT
INDICATION
Release
Setup (DL)
Call Confirmed
(7) CALL
RECEIVED
(8) CONNECT
REQUEST
Alerting
ConnectConnect Acknowledge
States
1,4,6,7,8,9
Release or
Release Complete
Release
Connect
Release
(W1) RRC Connection
Requested
(W2) RRC Connection
Setup Received
(W3) RRC Connection
Setup Complete Received
(G1) GSM Channel Requested
(G2) GSM Channel Assigned
ChannelRequest
RRCConnectionRequest
Channel Request
RRC Connection
Request
ChannelReleaseor
ImmediateAssignmentReject
RRC Connection Setup
RRCConnectionReject
RRC Connection Setup Complete
Immediate Assignment
Setup (UL)
Setup (DL) Setup (DL)
Setup (UL)
Connect

NT13-21914 29(51)
Each state has a tag “[X]n” where [X] is an (optional) letter and n is a
number. States without a letter are valid in both GSM and WCDMA; states
with “G” in front of the number are valid only for GSM; states with “W” in
front of the number are valid only for WCDMA.
Layer 3 and CC messages are represented by arrows. For certain
messages the direction (UL or DL) is indicated. Please note that the
depiction of the message traffic and state transitions is a simplified one,
with only the most important mechanisms included. Note in particular that a
transition to state NULL can take place from any state following one of the
events Blocked Call or Dropped Call; such state transitions are not shown
in the diagram.
3.3 Description of Call Events
3.3.1 Call Initialization
This event is generated only when the call is initiated by a command
sequence and only for mobile-originated (MO) calls. The event is triggered
by a phone mode report (i.e. not by a Layer 3 message) which in turn is
generated at the time the “yes” (or “send”) key is pressed.
3.3.2 Call Attempt
This event is generated in the following circumstances:
1. (GSM) Channel Request message with establishment cause “Speech”
received in state NULL.
2. (WCDMA) RRC Connection Request message with establishment
cause “Speech” received in state NULL.
3. Setup message received in state NULL. This can occur when a channel
has been set up for a service other than speech and a CM Service
Request has been received to change the reason for the channel
setup. (The CM Service Request message itself does not have a cause
value indicating whether speech is being requested, so it is not possible
to have the Call Attempt event triggered by CM Service Request.)
3.3.3 Call Attempt Retry
1. (GSM) Channel Request message with establishment cause “Speech”
received in state GSM Channel Requested.
2. (WCDMA) RRC Connection Request message with establishment
cause “Speech” received in state RRC Connection Requested.

NT13-21914 30(51)
3.3.4 Call Setup
1. Connect message received in state Call Init or in state MT Call
Confirmed.
2. Alerting message received in state Call Init or state MT Call Confirmed.
3.3.4.1 Extra Information
 Call direction: “MO call” or “MT call”.
 Call setup time in ms, measured from Call Attempt, i.e. the first call
attempt; this is not included if Call Attempt was triggered by the Setup
message (see section 3.3.2, step 2).
 User setup time in ms, measured from Call Initialization (thus more
accurately reflecting the user-perceived setup time). Included only if the
Call Initialization event has been previously generated, i.e. for MO calls
in a command sequence.
3.3.5 Call Established
This event is generated when entering state Active following the message
Connect (MO call) or Connect Acknowledge (MT call).
3.3.6 Call Re-established
This event is generated when, following a radio link failure, a call is re-
established (a drop thus being prevented; the UE never leaves state
ACTIVE).
Technology-specific details:
 GSM: New traffic channel assigned within 20 s.  3GPP 45.008,
section 6.7.2
 WCDMA: New traffic channel assigned before T314 timer expired.
 3GPP 25.331, section 8.3.1.13
This event can occur only if call re-establishment is enabled in the network.
If it is not, a call will be automatically dropped in this situation. The same
thing happens if the re-establishment fails (compare section 3.3.9.1).
3.3.7 Call End
1. Release message sent or received by phone, causing return to state
NULL without any of the events Blocked Call or Dropped Call having
been generated during the call.
2. Channel Release message received in state GSM Channel Assigned.
The following event information is then appended: “Not a call,
procedure completed with a SDCCH” (cf. below).

NT13-21914 31(51)
 Call end cause, one of the following strings:
o MS initiated release
o NW initiated release
o User busy
o Not a call, procedure completed with a SDCCH
o Technical drop: Release Missing
 Call duration in ms, indicating the time elapsing between the event Call
Established and the message Disconnect or (if, exceptionally, no
Disconnect is received) the message Release.
3.3.8 Blocked Call
This event is generated if the call is abnormally ended before the event Call
Established is generated.
 Block type, one of the following:
o No Immediate Assignment
o No Traffic Channel Assignment
o No Alerting or Connect
o No Connect
o No Call Confirmed
o No Connect Acknowledge
o No RRC Connection Setup
o No RRC Connection Setup Complete
o RRC Connection Reject
o Abnormal RRC Connection Release
o No Setup
o No Radio Bearer Setup Complete
o N-300 and T-300 expiry
 “CC Cause: <str>”, where <str> is a string. Included if the message that
generated the event included CC cause.
 "RR Cause: <str>", where <str> is a string. Included if the message that
generated the event included RR cause.
 Call time in ms, indicating the time since the event Call Initialization.

NT13-21914 32(51)
3.3.9 Dropped Call
This event is generated if the call is abnormally ended after the event Call
Established.
 Drop type, one of the following:
o Abnormal network
o Abnormal RRC Connection Release
o No service
o Re-establishment failure
o T313 expired
 “Cause: <str>”, where <str> is a string describing the cause of the drop.
 “CC Cause: <str>”, where <str> is a string. Included if the message that
generated the event included CC cause.
 Call duration in ms, indicating the time since the event Call Established.

NT13-21914 33(51)
4 CDMA Events
Event Name Symb. Description/Extra Information
Blocked Call
(red)
Unexpected change to idle or init state before
Call Established, or Order (PCH) Message
received with one of the order codes “Reorder”,
“Intercept”, “Registration Reject”, or “Release”.
Call Attempt
(gray)
MO call: Origination (ACH) message sent with a
voice Service Option.
MT call: Page Response (ACH) message
received with a voice Service Option.
Call Attempt Retry
(gray)
A call attempt (see Call Attempt) was repeated.
Call End Triggered by Order (RTCH) Message or Order
(FTCH) Message with order code “Release”.
Call Established
(green)
MO call: Triggered by Service Connect
Completion (RTCH) Message.
MT call: Order (RTCH) Message with order code
“Connect”.
Call Initiation Triggered by Protocol Report containing dialed
number.
Call Setup A call was set up by the device. Triggered by
Service Connect Completion (RTCH) Message.
Dedicated Mode The device is in traffic state.
Dropped Call Unexpected change to idle or init state after Call
Established.
EV-DO 1x
Tune-away
The device suspended the EV-DO service to
look for 1x paging.
Triggered by EV-DO Tuneaway Information
Report.
EV-DO Access
Failure
An EV-DO access attempt failed.
Triggered by EV-DO Access Attempt Report.
EV-DO Access
Success
An EV-DO access attempt completed
successfully.
Triggered by EV-DO Access Attempt Report.
EV-DO Connection
Failure
An EV-DO connection attempt failed.
Triggered by EV-DO Connection Attempt Report.

NT13-21914 34(51)
EV-DO Connection
Success
An EV-DO connection attempt completed
successfully.
Triggered by EV-DO Connection Attempt Report.
EV-DO Dynamic
Rate
The device switched back from fixed rate to
dynamic rate during an EV-DO session.
Triggered by occurrence of fixed rate end time
(see EV-DO Fixed Rate).
EV-DO Fixed Rate The device entered fixed rate mode for a period
of time during an EV-DO session.
Triggered by receipt of Fixed Mode Enable
Message (containing a given end time).
EV-DO Handoff
1 Active
The EV-DO active set was reduced to a single
pilot.
Extra information:
• EV-DO Rev. A: PN offset of each active pilot.
• EV-DO Rev. B: RF channel(s) and PN offset
of each active pilot (to one pilot PN may
correspond multiple RF channels:
<Channel 1>-<PN 1>, <Channel 2>-
<PN 1>, ...)
EV-DO Handoff
2 Actives
Handoff in EV-DO traffic mode, two pilots in
active set.
Extra information: See EV-DO Handoff
1 Active.
EV-DO Handoff
3 Actives
Handoff in EV-DO traffic mode, three pilots in
active set.
1 Active.
EV-DO Handoff
4 Actives
Handoff in EV-DO traffic mode, four pilots in
active set.
1 Active.
EV-DO Handoff
5 Actives
Handoff in EV-DO traffic mode, five pilots in
active set.
1 Active.
EV-DO Handoff
6 Actives
Handoff in EV-DO traffic mode, six pilots in
active set.
1 Active.

NT13-21914 35(51)
EV-DO Island There is only a single active EV-DO pilot and no
candidates.
Triggered by EV-DO Pilot Sets Ver2 Report.
EV-DO Session
Failure
An EV-DO session attempt failed.
Triggered by EV-DO Session Attempt Ver2
Report.
EV-DO Session
Success
An EV-DO session attempt completed
successfully.
Triggered by EV-DO Session Attempt Ver2
Report.
Hard Handoff Handoff in traffic state to another frequency, a
different band, a different pilot set, or another
frame offset, or a combination of these.
Triggered by Active Set Change.
Extra information:
• If band changed: RF mode (EV-DO or 1x);
new band; new RF channel; new top pilot PN.
• If only channel changed: RF mode; new RF
channel.
Idle Handoff Idle handoff 1x to 1x or EV-DO to EV-DO.
Triggered by Active Set Change.
Extra information:
• If band changed: RF mode (EV-DO or 1x);
new band; new RF channel; new top pilot PN.
• If only channel changed: RF mode; new RF
channel.
Idle Handoff To
Analog
System change from 1x or EV-DO to Analog in
idle mode.
Triggered by System Determination Last Main
Action Report.
Idle Handoff To
CDMA
System change from Analog or EV-DO to 1x in
idle mode.
Action Report.
Idle Handoff To
EV-DO
System change from 1x to EV-DO in idle mode.
Action Report.
Extra information: New RF channel.
Idle Mode The device is in init state or entered idle mode.

NT13-21914 36(51)
Missing CDMA
Neighbor (olive
green
bar on
the right)
See algorithm description in section 4.1.
Narrowband
Interference
Generated in the course of narrowband
interference scanning.
Triggered when an in-band RF channel has a
strength exceeding the average in-band RSSI by
an amount at least equal to Interference Offset.
The latter margin is set in the General window
(TEMS Investigation specific remark).
The event is generated only once for a given
interferer in the course of a scan. Furthermore, if
interference is detected on several contiguous
RF channels, only one event is reported for all of
these channels.
No Service Mode The mobile is searching for serving network, or
is in sleep mode.
Packet Mode The device entered data traffic mode.
Polluter
(red bar
on the
right)
See algorithm description in section 4.1.
Soft Handoff 2-Way Soft handoff in 1x traffic mode, two pilots in
active set.
Soft Handoff 3-Way Soft handoff in 1x traffic mode, three pilots in
active set.
Soft Handoff 4-Way Soft handoff in 1x traffic mode, four pilots in
active set.
Soft Handoff 5-Way Soft handoff in 1x traffic mode, five pilots in
active set.
Soft Handoff 6-Way Soft handoff in 1x traffic mode, six pilots in active
set.
Soft Handoff
Complete
Active set in 1x reduced to a single pilot.
Traffic Handoff To
Analog
System change from 1x to Analog during traffic.
Action Report.

NT13-21914 37(51)
Traffic Handoff To
CDMA
System change from Analog or EV-DO to 1x
during traffic.
Action Report.
Traffic Handoff To
EV-DO
System change from 1x to EV-DO during traffic.
Action Report.
4.1 Algorithm for Pilot Pollution and Missing
Neighbor Detection in CDMA
1. Order all pilot responses by descending . Discard pilots that lie below
the noise floor (which is technology and frequency band dependent).
2. Identify all pilots whose strength exceeds , where
.
3. Let , where is the maximum number of fingers that a receiver
can demodulate.
4. For , check whether the strongest pilot is in the neighbor list. Any
pilot not in the neighbor list is flagged as a missing neighbor.
5. Calculate
6. Calculate
where is the largest integer such that
.
7. Calculate the percentage of useful energy .
8. If , there is no pilot pollution.
9. If , then each pilot such that is a polluter.

NT13-21914 38(51)
5 Overviews of Selected Event Families
5.1 Cell Reselection/Neighbor Measurements
Please note that this diagram also includes a number of information
elements (blue).
Cell reselection and inter-RAT neighbor measurements; missing neighbor events.

NT13-21914 39(51)
5.2 RAT Transition Events
RAT transition events; handover/handoff, cell reselection, and others.

NT13-21914 40(51)
6 Data Service Testing Events
6.1 General
These events are generated in the course of PS data service testing. Many
of them serve as input to the computation of data service KPI statistics in
TEMS Discovery. KPIs are defined in the document “KPI Definitions in
TEMS Products”, doc.no. NT13-25359. Individual KPIs in that document
are referred to in the table in section 6.4.
Certain data service testing events do not have anything to do with KPIs:
chiefly, those consisting of a service designation plus one of the suffixes
“Start”, “End”, or “Error”. These events signify simply that a data service
session has started, ended, or aborted because of an error (of whatever
kind; the cause is specified in the extra information).
Call events for VoIP are dealt with in chapter 2.
6.2 Notes on KPIs for Particular Data Services
 MMS Notification and MMS End-to-end KPIs are based on multiple KPI
events; this is not indicated in the table below.
 No KPI events exist for email because of the ubiquitous use of
encryption in connection with that service, which makes it impossible to
obtain many of the measurements that would be required for KPI
calculation.
 No KPI events exist for SMS. The SMS events in section 2.1 are
unrelated to KPI computation.
 The MMS, WAP, and RTP streaming KPIs exist for TEMS Investigation
only.
6.3 Notes on KPI Definitions in ETSI Specification
The ETSI KPI specification ( ETSI TS 102 250-2) describes two slightly
different methods of KPI measurement, called “Method A” and “Method B”
respectively. TEMS Investigation supports both of these; measurements
according to Methods A and B may be delivered in two separate instances
of the event, or they may both be given in the same event instance.

NT13-21914 41(51)
6.4 Event List
Event Name Symb. Extra Info
Associated KPI
(or Description)
ABM (Available bandwidth measurement) events
ABM Error Cause –
ABM Start For each ABM server:
Server ID; Server IP
address; Server port
–
ABM Stop – –
AQM events (VoIP)
AQM Session Complete Phone number; synch time –
AQM Session Failure Phone number; synch time –
AQM Session Start – –
Attach events
Attach Failure – Attach Failure Ratio (%)
Attach Setup Time Time in ms Attach Setup Time (s)
DNS events
DNS Host Name
Resolution Failure
Domain name(s); DNS
server address
–
DNS Host Name
Resolution Time
Domain name(s); DNS
server address; Resolution
time in seconds
–
Email events
Email Receive End Outcome – (No KPIs defined for email)
Email Receive Error Cause
Email Receive Start POP3 server IP address or
host name
Email Send End Outcome
Email Send Error Cause
Email Send Start SMTP server IP address or
host name

NT13-21914 42(51)
Associated KPI
(or Description)
ETSI marker events
First SYN Marker of the time First [SYN] sent
First SYN ACK Marker of the time Reception of [SYN, ACK]
First ACK Marker of the time Reception of the [ACK] from
the [SYN, ACK]
First HTTP Post Marker of the time Sending of the first GET
command
First HTTP Get Marker of the time Sending of the first POST
command
First Packet With Content Marker of the time Sending / Reception of the first
data packet containing content
Received FIN ACK Marker of the time Reception of [FIN, ACK]
FTP download events: Not obtained for SFTP.
FTP Download Data
Transfer Cutoff
Cutoff point Data Transfer Cut-off Ratio (%)
FTP Download Data
Transfer Time
Time in seconds Data Transfer Time (s)
FTP Download End Outcome –
FTP Download Error Cause –
FTP Download IP Service
Access Failure
Details of failure IP Service Access Failure
Ratio (%)
FTP Download IP Service
Setup Time
Time in seconds IP Service Setup Time (s)
FTP Download Mean
Data Rate
Data rate in kbit/s Mean Data Rate (kbit/s)
FTP Download Service
Not Accessible
Details of failure Service Non-Accessibility (%)
FTP Download Setup
Time
Time in seconds Setup Time (s)
FTP Download Start File path and name –

NT13-21914 43(51)
Associated KPI
(or Description)
FTP upload events: Not obtained for SFTP.
FTP Upload Data
Transfer Cutoff
FTP Upload Data
Transfer Time
FTP Upload End Outcome –
FTP Upload Error Cause –
FTP Upload IP Service
Access Failure
Ratio (%)
FTP Upload IP Service
Setup Time
FTP Upload Mean Data
Rate
FTP Upload Service Not
Accessible
FTP Upload Setup Time Time in seconds Setup Time (s)
FTP Upload Start File path and name –
HTTP events: General
HTTP Service Not
Accessible
HTTP Setup Time Time in seconds Setup Time (s)
HTTP events: Get
HTTP Data Transfer
Cutoff
HTTP Data Transfer Time Time in seconds Data Transfer Time (s)
HTTP End Outcome –
HTTP Error Cause –
HTTP IP Service Access
Failure
Ratio (%)
HTTP IP Service Setup
Time

NT13-21914 44(51)
Associated KPI
(or Description)
HTTP Mean Data Rate Data rate in kbit/s Mean Data Rate (kbit/s)
HTTP Start IP address or host name –
HTTP events: Post
HTTP Post Data Transfer
Cutoff
HTTP Post Data Transfer
Time
HTTP Post End Outcome –
HTTP Post Error Cause –
HTTP Post IP Service
Access Failure
Ratio (%)
HTTP Post IP Service
Setup Time
HTTP Post Mean Data
Rate
HTTP Post Start HTTP server script URL –
IP events
IP Interruption Time Time in seconds – (unrelated to KPIs)
Generated on handover and
indicates time gap between last
IP packet in old cell and first IP
packet in new cell.4
Note: For this time to be
correct, IP sniffing must not be
configured for “Optimized
Performance”.
MMS receive events
MMS Receive Data
Transfer Cutoff
– Data Transfer Cut-off Ratio (%)
MMS Receive Data
Transfer Time
MMS Receive End Outcome –
4 This event is currently generated only when an LTE network is involved in the handover.

NT13-21914 45(51)
Associated KPI
(or Description)
MMS Receive Error Cause –
MMS Receive Start – –
MMS Retrieval Failure – MMS Retrieval Failure Ratio
(MT) (%)
MMS Retrieval Time Time in seconds MMS Retrieval Time (MT) (s)
MMS send events
MMS Send Data Transfer
Cutoff
MMS Send Data Transfer
Time
MMS Send End Outcome –
MMS Send Error Cause –
MMS Send Failure – MMS Send Failure Ratio (MO)
(%)
MMS Send Start – –
MMS Send Time Time in seconds MMS Send Time (MO) (s)
MTSI events
MTSI Registration Failure – MTSI Registration Failure Ratio
(%)
MTSI Registration Time Time in seconds MTSI Registration Time (s)
MTSI Session Completion
Failure
– MTSI Session Completion
Failure Ratio (%)
MTSI Session Completion
Time
Time in seconds –
MTSI Session Setup
Failure
– MTSI Session Setup Failure
Ratio (%)
MTSI Session Setup Time Time in seconds MTSI Session Setup Time (s)
Network connect events
Network Connect Connection type
(NDIS/RAS); IP address
Network Unavailability (%)

NT13-21914 46(51)
Associated KPI
(or Description)
Network Connect Attempt Connection type
(NDIS/RAS)
– (unrelated to KPIs)
Triggered when a Network
Connect activity starts
executing.
Network Connect Error Cause Network Unavailability (%)
Network Connection Lost – – (unrelated to KPIs)
Triggered when the operational
state of the .NET network
interface changes to Down for
a device to which Network
Connect was previously
applied.5 Generated only for
NDIS connections.
Network Disconnect – –
PDP context events
PDP Context Activation
Time
Time in ms PDP Context Activation Time
(s)
PDP Context Cutoff – PDP Context Cut-off Ratio (%)
Ping events
Ping End Max. delay; Min. delay;
Avg. delay; Success count;
Failed count
–
Ping Error Cause –
Ping Roundtrip Time Time in seconds; Ping size;
IP address
Ping Roundtrip Time (ms)
Ping Start IP address or host name –
Ping Timeout – –
SIP events
SIP Invite Handshake
Time
Time between SIP Invite
and SIP Invite Response
messages
–
5 Reference:  msdn.microsoft.com/en-us/library/
system.net.networkinformation.operationalstatus.aspx

NT13-21914 47(51)
Associated KPI
(or Description)
Social network testing events
Social Network Logon
Rate
Logon Success Count /
Logon Attempt Count × 100
(%)
–
These events report
percentages/averages
aggregated over the whole
execution of a Social Network
activity rather than single
instances of success/failure or
elapsed time.
Social Network Weibo
Average Time
Weibo Total Duration /
Weibo Success Count ×
100 (%)
Failure Rate
Weibo Failure Count /
(Weibo Attempt Count –
Weibo Timeout Count) ×
100 (%)
(timeouts are disregarded in
this calculation)
Success Rate
Weibo Success Count /
Weibo Attempt Count × 100
(%)
SRVCC events
SRVCC Handover
Interruption Time (User
Plane)
Time in ms –
Time from last RTP report on
LTE to first UMTS DL Vocoder
report on UTRAN/GERAN.
Streaming events: Common to HTTP and RTP
Streaming End Outcome –
Streaming Start HTTP: File URL
RTP: File path and name
–
Streaming events: HTTP-specific
Streaming Quality MOS Avg. audio MOS; Avg.
absolute video MOS; Avg.
relative video MOS; Avg.
audio–video MOS
– (No KPI defined)
Event gives overall VQmon
scores for an entire streaming
session.
Streaming events: RTP-specific
Streaming Error Cause –
Streaming Intermediate
VSQI
MOS value Streaming Quality (MOS-VSQI)
Event gives average of the
latest 30 values of Streaming
VSQI.

NT13-21914 48(51)
Associated KPI
(or Description)
Streaming Quality MTQI MOS value – (No KPI defined)
Event gives overall MTQI score
for an entire streaming session.
Streaming Quality VSQI MOS value Streaming Quality (MOS-VSQI)
Event gives overall VSQI score
for an entire streaming session.
Streaming Reproduction
Cutoff
– Reproduction Cut-off Ratio (%)
Start Delay
Time in seconds Reproduction Start Delay (s)
Start Failure
– Reproduction Start Failure
Ratio (%)
Streaming Service
Access Time
Time in seconds Service Access Time (s)
Streaming Service Not
Accessible
– Service Non-Accessibility (%)
Streaming Session Cutoff – Streaming Session Cut-off
Ratio (%)
Streaming State State of RTP streaming
video client: one of
“Connecting”, “Negotiating”,
“Prebuffering”,
“Reproducing”,
“Rebuffering”, “Finished”
–
TCP events
TCP Download End Outcome – (No KPIs defined for TCP)
TCP Download Error Cause
TCP Download Start IP address
TCP Handshake Time IP address; Time in
seconds
TCP Upload End Outcome
TCP Upload Error Cause
TCP Upload Start IP address

NT13-21914 49(51)
Associated KPI
(or Description)
Trace Route events
Trace Route End Destination; Reached
(True/False)
– (No KPIs defined for Trace
Route)
Trace Route Hop Hop sequence no.; IP
address reached; Hop time
Trace Route Start Destination
Trace Route Timeout Hop sequence no.; IP
address targeted
UDP events
UDP Download End Outcome – (No KPIs defined for UDP)
UDP Download Error Cause
UDP Download Packet
Loss
Packet loss in %
UDP Download Start IP address
UDP Upload End Outcome
UDP Upload Error Cause
UDP Upload Packet Loss Packet loss in %
UDP Upload Start IP address
VoIP events
VoIP End Outcome – (KPIs based on “MTSI”
events, which see)
VoIP Error Cause
VoIP Lost Packets Count
During Handover
No. of missing RTP packets
from handover start (RRC
Reconfiguration Command)
to successful playback of
first RTP packet after
handover (RRC
Reconfiguration Complete)
–
VoIP Start Cause (e.g. “A-Party
calling”); Client used
– (KPIs based on “MTSI”
events, which see)

NT13-21914 50(51)
Associated KPI
(or Description)
WAP events
WAP Activation Failure – WAP Activation Failure Ratio
(%)
WAP Activation Time Time in ms WAP Activation Time (ms)
WAP End Outcome –
WAP Error Cause –
WAP Page Data Transfer
Cutoff
WAP Page Data Transfer
Time
WAP Page Mean Data
Rate
WAP Page Request
Failure
– WAP Page Request Failure
Ratio (%)
WAP Page Request Time Time in seconds WAP Page Request Time (s)
WAP Portal Access Time Time in seconds WAP Portal Access Time (s)
WAP Portal Not
Accessible
– WAP Portal Non-accessibility
(%)
WAP Site Access Time Time in seconds WAP Site Access Time (s)
WAP Site Not Accessible – WAP Site Non-accessibility (%)
WAP Start URL; Connection method –

NT13-21914 51(51)
7 Media Quality Events
Under this heading are collected events pertaining to audio quality
measurement and audio perception.
AQM Out of Synch The synchronization between the AQM module
and the Call Generator was lost. See the
document “AQM in TEMS Products”.
AQM Session
Complete
The device completed a Voice Quality activity
normally.
Extra information: Phone number; synch time.
AQM Session Failure The device aborted a Voice Activity abnormally
because of an error.
Extra information: Phone number; synch time.
AQM Session Start The device started executing a Voice Quality
activity.
AQM Sync Failure Synchronization was never achieved within the
duration of the (intended) audio quality
measurement. As a consequence, no AQM
output was obtained.
AQM Synched The synchronization between the AQM module
and the Call Generator was re-established. See
the document “AQM in TEMS Products”.
Handover Speech
Interruption Downlink
The information element Speech Interruption
Downlink took on the value “Silence detected” at
some point in connection with a handover.
Extra information: Length of silent period; type
of handover.
Speech Interruption
Time Downlink
The information element Speech Interruption
Downlink had the value “Silence detected” for at
least 100 ms.
Extra information: Length of silent period.

Events in tems products

More Related Content

What's hot (20)

Similar to Events in tems products (20)

Recently uploaded (20)

Events in tems products