Beruflich Dokumente
Kultur Dokumente
Prepared by:
Ascom Network Testing
Date:
2/26/2014
Document:
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.
Contents
Ascom (2014)
Introduction ................................................................ 1
1.1
2.1
3.1
3.2
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7
3.3.8
3.3.9
Introduction.............................................................................27
Event State Machine ...............................................................27
Description of Call Events .....................................................29
Call Initialization ........................................................................29
Call Attempt ..............................................................................29
Call Attempt Retry.....................................................................29
Call Setup .................................................................................30
Call Established ........................................................................30
Call Re-established...................................................................30
Call End ....................................................................................30
Blocked Call..............................................................................31
Dropped Call.............................................................................32
4.1
5.1
5.2
6.1
6.2
6.3
6.4
General ....................................................................................43
Notes on KPIs for Particular Data Services ..........................43
Notes on KPI Definitions in ETSI Specification ....................43
Event List ................................................................................44
Document:
NT13-21914
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 products; this depends, for one
thing, on what services each product supports.
1.1
GSM/WCDMA/LTE/TD-SCDMA 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:
Ascom (2014)
Code
Meaning
ga
lte
ps
sg
Document:
NT13-21914
1(58)
Code
Meaning
sw
td
2.1
Event List
Event Name
Symb.
Authentication
Failure
Description/Extra Information
g
w
Baton Handover
td
Baton Handover
Failure
td
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:
Ascom (2014)
Block type
CC cause
RR cause
Document:
NT13-21914
2(58)
Event Name
Symb.
Call Attempt
(gray)
Description/Extra Information
g
w
ga
ps
Call End
g
w
g
w
ps
Extra information:
Call Established
(green)
Call Initiation
g
w
ga
ps
g
w
Call duration
(GSM/WCDMA/TD-SCDMA:) the
Layer 3 message Connect (MO call) or
Connect Acknowledge (MT call)
Ascom (2014)
Document:
NT13-21914
3(58)
Event Name
Symb.
Description/Extra Information
(green)
g
w
Following a radio link failure, a call was reestablished (a drop thus being prevented).
Call Re-established
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 reestablishment is enabled in the network. If
it is not, a call will be automatically
dropped in this situation.
Call Setup
g
w
ga
ps
Extra information:
Cell Reselection
g
w
Ascom (2014)
Document:
NT13-21914
4(58)
Event Name
Symb.
Description/Extra Information
Cell Reselection
From UTRAN
Cell Reselection To
EUTRAN
lte
Ascom (2014)
Cell Reselection To
UTRAN
td
td
Channel Switch To
HSDPA
td
Channel Switch To
HSDPA Failure
td
Compressed Mode
Entered
Compressed Mode
Exited
CS Call Initiated on
IP Call Request
(Incoming)
g
w
CS Call Initiated on
IP Call Request
(Outgoing)
g
w
Document:
NT13-21914
5(58)
Event Name
Symb.
Description/Extra Information
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
Extra information:
Block type
lte
(gray)
CSFB Call
Established
(green)
g
w
Ascom (2014)
Document:
NT13-21914
6(58)
Event Name
CSFB Call Setup
Symb.
*
g
w
Description/Extra Information
A CS fallback call was set up. Triggered
by Layer 3 message Alerting.
Extra information:
g
w
Datalink Failure
Dedicated Mode
Dropped Call
g
w
EGPRS MS Out Of
Memory
Ascom (2014)
Drop type
Cause
CC cause
Document:
NT13-21914
7(58)
Event Name
Emergency Call
Failure
Symb.
Description/Extra Information
g
w
Emergency Call
Success
g
w
EPS events: Some of these, tagged lg below, are unique to LG chipset devices.
EPS NAS Signaling
Failure
lte
lg
Ascom (2014)
Document:
NT13-21914
8(58)
Event Name
Symb.
Description/Extra Information
lte
lg
lte
lg
lte
lg
lte
lg
lte
lg
lte
Extra information:
lte
EUTRAN ANR
Neighbor Reported
lte
Ascom (2014)
Document:
NT13-21914
9(58)
Event Name
EUTRAN Attach
Complete
Symb.
*
lte
Description/Extra Information
The device successfully attached to
EUTRAN. Triggered by EPS Attach
Complete.
Extra information:
EUTRAN Attach
Failure
lte
EUTRAN Detach
Accept
lte
Attach type
Failure cause
lte
lte
Ascom (2014)
Document:
NT13-21914
10(58)
Event Name
EUTRAN Intrafrequency Handover
Symb.
Description/Extra Information
lte
lte
EARFCN
EUTRAN Reselection
Time After CSFB Call
lte
EARFCN
EUTRAN RRC A1
Event
lte
EUTRAN RRC A2
Event
lte
Ascom (2014)
Document:
NT13-21914
11(58)
Event Name
EUTRAN RRC A3
Event
Symb.
Description/Extra Information
lte
EUTRAN RRC A4
Event
lte
EUTRAN RRC A5
Event
lte
EUTRAN RRC
Connection Reject
lte
EUTRAN RRC
Connection Release
Redirected Attempt
lte
EUTRAN RRC
Connection Release
Redirected Failure
Ascom (2014)
lte
Document:
NT13-21914
12(58)
Event Name
Symb.
EUTRAN RRC
Connection Release
Redirected Success
*
lte
w
g
1
Description/Extra Information
Successful new connection setup
following EPS RRC Connection Release
message with redirection flag. Triggered
by one these messages:
Extra information:
EUTRAN RRC
Established
lte
(green)
Handover
Handover Failure
Handover From
EUTRAN
Handover From
EUTRAN Failure
Ascom (2014)
lte
13(58)
Event Name
Handover From GAN
Symb.
*
ga
Description/Extra Information
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.
ga
Handover From
UTRAN
Handover From
UTRAN Failure
Handover Intracell
Handover Intracell
Failure
Handover To
EUTRAN
lte
Handover To
EUTRAN Failure
Handover To GAN
ga
Handover To GAN
Failure
ga
Handover To UTRAN
Ascom (2014)
Document:
NT13-21914
14(58)
Event Name
Symb.
Description/Extra Information
Handover To UTRAN
Failure
HS Serving Cell HO
HS Serving Cell HO
Failure
Idle Mode
Inter-frequency Cell
Reselection
Inter-frequency
Handover
w
td
Inter-frequency
Handover Failure
w
td
Intra-frequency Hard
Handover
w
td
Intra-frequency Hard
Handover Failure
w
td
Location Area
Update
g
w
Location Area
Update Failure
g
w
Ascom (2014)
Document:
NT13-21914
15(58)
Event Name
Measurement
Report 1
Symb.
Description/Extra Information
Measurement
Report 2
Measurement
Report 3
Measurement
Report 4
Measurement
Report 5
Measurement
Report 6
Measurement
Report 7
Ascom (2014)
Document:
NT13-21914
16(58)
Event Name
Missing GSM
Neighbor
Symb.
Description/Extra Information
sg
(yellow
bar on
the right)
g
(yellow
bar on
the right)
Ascom (2014)
Document:
NT13-21914
17(58)
Event Name
Missing LTE
Neighbor
Symb.
(yellow
bar on
the right)
Description/Extra Information
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).
2. A cell not defined as a neighbor of the
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 cells
neighbor list is detected, but at least
one cell is detected besides the
strongest cell. (The event is then
triggered regardless of the strength of
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):
Ascom (2014)
Document:
NT13-21914
18(58)
Event Name
Missing TD-SCDMA
Neighbor
Symb.
(yellow
bar on
the right)
Description/Extra Information
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.
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
TD-SCDMA (TEMS Investigation
specific remark).
2. A cell not defined as a neighbor of the
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 cells
neighbor list is detected, but at least
one cell is detected besides the
strongest cell. (The event is then
triggered regardless of the strength of
that cell.)
The signal power measure used in the
comparisons is Ec/Io.
Extra information: UARFCN plus the
following (different for each of the three
cases listed above):
Ascom (2014)
Document:
NT13-21914
19(58)
Event Name
Missing WCDMA
Intra-frequency
Neighbor
Symb.
*
w
(yellow
bar on
the right)
Description/Extra Information
This is a WCDMA event based on UE
data. The event does not require a cell
file.
Triggered in the following cases:
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:
Ascom (2014)
Document:
NT13-21914
20(58)
Event Name
Missing WCDMA
Neighbor
Symb.
(yellow
bar on
the right)
*
(c)
sw
Description/Extra Information
This event is based on WCDMA scan
data. It requires either
Ascom (2014)
Document:
NT13-21914
21(58)
Event Name
More Than 3 Strong
SCs
Symb.
*
sw
(red bar
on the
right)
Description/Extra Information
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
Packet Mode
PDP Context
Activation 2
g
w
PDP Context
Activation Failure 2
g
w
PDP Context
Deactivation 2
g
w
PDU Error
PS Attach 2
g
w
Ascom (2014)
Document:
NT13-21914
22(58)
Event Name
PS Attach Failure
Symb.
2
*
g
w
Description/Extra Information
The device failed to attach to the packet
service.
Extra information: Attach type; failure
cause.
PS Channel Type
Switch Complete
PS Channel Type
Switch Failure
PS Data Interruption
Time Due To CSFB
g
w
PS Detach
g
w
PS RAB Channel
Rate Switch
Complete
PS RAB Channel
Rate Switch Failure
Radio Bearer
Reconfiguration
Failure
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.
Ascom (2014)
Document:
NT13-21914
23(58)
Event Name
Radio Bearer Setup
Failure
Symb.
Description/Extra Information
Radio Link
Replacement
Radio Link
Replacement Failure
Ringing
g
w
g
w
Rove In To GAN
ga
Rove In To GAN
Failure
ga
Ascom (2014)
Document:
NT13-21914
24(58)
Event Name
Symb.
Rove In To GAN
Redirect
*
ga
Description/Extra Information
When reselecting from GSM to GAN, the
device was redirected from the default
GANC to a different GANC.
Triggered by GAN Layer 3 message
Register Redirect.
ga
ga
RRC Connection
Abnormal Release
RRC Connection
Reject
RRC Established
(green)
w
(red)
Scanning Mode
sg
Security Mode
Failure
SHO Procedure
Complete
SHO Procedure
Complete Without
Measurement Control
Ascom (2014)
Document:
NT13-21914
25(58)
Event Name
Silent Call
Symb.
*
g
w
Description/Extra Information
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
SMS Received
g
w
SMS Sent
g
w
w
g
Ascom (2014)
26(58)
3.1
Introduction
3.2
Ascom (2014)
Document:
NT13-21914
27(58)
Channel Request
RRC Connection
Request
Channel Request
Immediate Assignment
)
(UL
Setu
p (D
L)
Setup (DL)
Setup (UL)
Setup (UL)
(0) NULL
Setup (DL)
(6) CALL
PRESENT
Re
le
as
e
(11) DISCONNECT
REQUEST
Release or
Release Complete
Alerting
Connect
(4) CALL
DELIVERED
Re
lea
se
Rele
ase
Call Confirmed
Disconnect (UL)
States
1,4,6,7,8,9
(12) DISCONNECT
INDICATION
Disconnect (DL)
States
4, 7, 8, 9, 10
Connect
(9) MT CALL
CONFIRMED
t
ec
nn
Co
Alerting
(10) ACTIVE
(8) CONNECT
REQUEST
Connect Acknowledge
Connect
(7) CALL
RECEIVED
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.
Ascom (2014)
Document:
NT13-21914
28(58)
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
3.3.1
Call Initialization
3.3.2
Call Attempt
3.3.3
Ascom (2014)
Document:
NT13-21914
29(58)
3.3.4
Call Setup
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 reestablished (a drop thus being prevented; the UE never leaves state
ACTIVE).
Technology-specific details:
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
Document:
NT13-21914
30(58)
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.
3.3.8.1 Extra Information
Ascom (2014)
"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.
Document:
NT13-21914
31(58)
3.3.9
Dropped Call
This event is generated if the call is abnormally ended after the event Call
Established.
3.3.9.1 Extra Information
Ascom (2014)
Cause: <str>, where <str> is a string describing the cause of the drop.
Call duration in ms, indicating the time since the event Call Established.
Document:
NT13-21914
32(58)
CDMA 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 designation MR below refers to device mode reports.
Event Name
Symb.
Description/Extra Information
Call events (Blocked Call; Call*; Dropped Call): Some of these events are also
generated for VoIP.
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
Call Attempt
(gray)
Call End
Call Established
(green)
Ascom (2014)
Document:
NT13-21914
33(58)
Event Name
Symb.
Call Setup
Description/Extra Information
Triggered by Service Connect Completion
(RTCH) message.
Extra information:
CSFB events: Some of these events have a piece of extra information Call
Domain, which however always takes the value Circuit Switched.
CSFB Blocked Call
(red)
CSFB Call
Established
Ascom (2014)
(green)
Document:
NT13-21914
34(58)
Event Name
CSFB Call Setup
Symb.
Description/Extra Information
Triggered by one of the following:
Extra information:
Dedicated Mode
Dropped Call
EV-DO 1x
Tune-away
EV-DO Access
Failure
Ascom (2014)
Document:
NT13-21914
35(58)
Event Name
EV-DO Access
Success
Symb.
Description/Extra Information
An EV-DO access attempt completed
successfully.
Triggered by EV-DO Access Attempt Report.
Extra information: Sector sending ACAck
message.
EV-DO Connection
Failure
EV-DO Connection
Success
EV-DO Handoff
1 Active
EV-DO Handoff
2 Actives
EV-DO Handoff
3 Actives
EV-DO Handoff
4 Actives
Ascom (2014)
Document:
NT13-21914
36(58)
Event Name
EV-DO Handoff
5 Actives
Symb.
Description/Extra Information
Handoff in EV-DO traffic mode, five pilots in
active set.
Extra information: See EV-DO Handoff
1 Active.
EV-DO Handoff
6 Actives
EV-DO Island
EV-DO Session
Failure
EV-DO Session
Success
Idle Handoff
Idle Handoff To
Analog
Ascom (2014)
Document:
NT13-21914
37(58)
Event Name
Symb.
Idle Handoff To
CDMA
Description/Extra Information
System change from Analog or EV-DO to 1x in
idle mode.
Triggered by System Determination Last Main
Action Report.
Extra information: New RF channel.
Idle Handoff To
EV-DO
Idle Mode
Missing CDMA
Neighbor
Narrowband
Interference
No Service Mode
Packet Mode
Polluter
Ascom (2014)
Document:
NT13-21914
38(58)
Event Name
Symb.
Description/Extra Information
Soft Handoff
Complete
Traffic Handoff To
Analog
Traffic Handoff To
CDMA
4.1
1.
2.
Identify all
, where
.
3.
Let
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
Ascom (2014)
, where
39(58)
Ascom (2014)
7.
8.
If
9.
If
such that
Document:
NT13-21914
is a polluter.
40(58)
5.1
Ascom (2014)
Document:
NT13-21914
41(58)
5.2
Ascom (2014)
Document:
NT13-21914
42(58)
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 have nothing 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
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 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
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.
Ascom (2014)
Document:
NT13-21914
43(58)
6.4
Event List
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Cause
ABM Start
ABM Stop
Attach Failure
Time in ms
Outcome
Cause
Outcome
Cause
Attach events
DNS events
Email events
Ascom (2014)
Document:
NT13-21914
44(58)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
First ACK
Cutoff point
Cutoff point
Cutoff point
Time in seconds
Time in seconds
Time in seconds
Outcome
Cause
Details of failure
Details of failure
Details of failure
Ascom (2014)
Document:
NT13-21914
45(58)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Time in seconds
Time in seconds
Time in seconds
Details of failure
Details of failure
Details of failure
Time in seconds
Time in seconds
Time in seconds
Cutoff point
Cutoff point
Cutoff point
Time in seconds
Ascom (2014)
Document:
NT13-21914
46(58)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Time in seconds
Time in seconds
Outcome
Cause
Details of failure
Details of failure
Details of failure
Time in seconds
Time in seconds
Time in seconds
Details of failure
Details of failure
Details of failure
Time in seconds
Time in seconds
Ascom (2014)
Document:
NT13-21914
47(58)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Time in seconds
Details of failure
Details of failure
Details of failure
Time in seconds
Time in seconds
Time in seconds
Cutoff point
Cutoff point
Cutoff point
Time in seconds
Time in seconds
Time in seconds
HTTP End
Outcome
HTTP Error
Cause
Details of failure
Ascom (2014)
Document:
NT13-21914
48(58)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Details of failure
Details of failure
Time in seconds
Time in seconds
Time in seconds
HTTP Start
Cutoff point
Cutoff point
Cutoff point
Time in seconds
Time in seconds
Time in seconds
Outcome
Cause
Details of failure
Ascom (2014)
Document:
NT13-21914
49(58)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Details of failure
Details of failure
Time in seconds
Time in seconds
Time in seconds
Time in seconds
(unrelated to KPIs)
IP events
IP Interruption Time
Time in seconds
Outcome
Cause
Ascom (2014)
This event is currently generated only when an LTE network is involved in the handover.
Document:
NT13-21914
50(58)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Time in seconds
Time in seconds
Outcome
Cause
Time in seconds
Time in seconds
Time in seconds
Time in seconds
Connection type
(NDIS/RAS); IP address
MTSI events
Ascom (2014)
Document:
NT13-21914
51(58)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Connection type
(NDIS/RAS)
(unrelated to KPIs)
Cause
(unrelated to KPIs)
Time in ms
Ping End
Ping Error
Cause
Ping Start
Ping Timeout
Network Disconnect
PDP context events
Ping events
SIP events
SIP Invite Handshake
Time
Reference: msdn.microsoft.com/enus/library/system.net.networkinformation.operationalstatus.aspx
5
Ascom (2014)
Document:
NT13-21914
52(58)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
SRVCC events
SRVCC Handover
Interruption Time (User
Plane)
Time in ms
Streaming events: The set of events generated differs between streaming clients and protocols.
Streaming End
Outcome
Streaming Error
Cause
Streaming Intermediate
VSQI
MOS value
MOS value
Ascom (2014)
Document:
NT13-21914
53(58)
Event Name
Streaming Quality VSQI
Symb.
Associated KPI
(or Description)
Extra Info
MOS value
Streaming Reproduction
Cutoff
Streaming Reproduction
Start Delay
Time in seconds
Streaming Reproduction
Start Failure
Streaming Service
Access Time
Time in seconds
Streaming Start
Streaming State
Time in seconds
Time in seconds
TCP events
TCP Connection Idle
Time Stop
Ascom (2014)
Document:
NT13-21914
54(58)
Event Name
Symb.
Extra Info
Associated KPI
(or Description)
Outcome
Cause
IP address
IP address; Time in
seconds
Outcome
Cause
IP address
Destination; Reached
(True/False)
Destination
UDP events
UDP Download End
Outcome
Cause
Packet loss in %
IP address
Outcome
Cause
Packet loss in %
Ascom (2014)
Document:
NT13-21914
55(58)
Event Name
UDP Upload Start
Symb.
Associated KPI
(or Description)
Extra Info
IP address
VoIP events
VoIP End
Outcome
VoIP Error
Cause
Time in ms
(unrelated to KPIs)
Generated on handover during
a VoIP talkspurt and indicates
time gap between last RTP
packet in old cell and first RTP
packet in new cell.
Note: For this time to be
correct, IP sniffing must not be
configured for Optimized
Performance (TEMS
Investigation specific remark).
VoIP Start
Time in ms
WAP End
Outcome
WAP Error
Cause
Time in seconds
WAP events
Ascom (2014)
Document:
NT13-21914
56(58)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Time in seconds
Time in seconds
Time in seconds
WAP Start
Ascom (2014)
Document:
NT13-21914
57(58)
Symb.
Description/Extra Information
AQM Session
Complete
AQM Synched
Handover Speech
Interruption Downlink
Speech Interruption
Time Downlink
Ascom (2014)
Document:
NT13-21914
58(58)