Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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 ....................................................................................40
Notes on KPIs for Particular Data Services ..........................40
Notes on KPI Definitions in ETSI Specification ....................40
Event List ................................................................................41
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 of the 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(51)
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(51)
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(51)
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(51)
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(51)
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(51)
Event Name
CSFB Call Initiation
Symb.
Description/Extra Information
lte
g
w
g
w
Datalink Failure
Dedicated Mode
Dropped Call
g
w
Ascom (2014)
Drop type
Cause
CC cause
Document:
NT13-21914
7(51)
Event Name
Symb.
Description/Extra Information
EGPRS MS Out Of
Memory
Emergency Call
Failure
g
w
Emergency Call
Success
g
w
2.
WCDMA:
Ascom (2014)
1.
2.
Document:
NT13-21914
8(51)
Event Name
Symb.
Description/Extra Information
EPS events: Some of these, tagged lg below, are unique to LG chipset devices.
EPS NAS Signaling
Failure
lte
lg
lte
lg
lte
lg
lte
lg
lte
lg
lte
lg
lte
Extra information:
Ascom (2014)
Document:
NT13-21914
9(51)
Event Name
Symb.
Description/Extra Information
EPS Transmission
Mode Changed
lte
EUTRAN ANR
Neighbor Reported
lte
EUTRAN Attach
Complete
lte
EUTRAN Attach
Failure
lte
EUTRAN Detach
Accept
lte
Attach type
Failure cause
lte
Ascom (2014)
Document:
NT13-21914
10(51)
Event Name
EUTRAN Interfrequency Handover
Failed
Symb.
*
lte
Description/Extra Information
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:
lte
lte
EARFCN
EUTRAN Reselection
Time After CSFB Call
lte
EARFCN
Ascom (2014)
Document:
NT13-21914
11(51)
Event Name
EUTRAN RRC A1
Event
Symb.
Description/Extra Information
lte
EUTRAN RRC A2
Event
lte
EUTRAN RRC A3
Event
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(51)
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(51)
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(51)
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(51)
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(51)
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(51)
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.
2.
3.
Ascom (2014)
Document:
NT13-21914
18(51)
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.
2.
3.
Ascom (2014)
Document:
NT13-21914
19(51)
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.
2.
3.
Ascom (2014)
Document:
NT13-21914
20(51)
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
2.
3.
Ascom (2014)
Document:
NT13-21914
21(51)
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
g
w
PDP Context
Activation Failure
g
w
PDP Context
Deactivation
g
w
PDU Error
PS Attach
g
w
Ascom (2014)
Document:
NT13-21914
22(51)
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(51)
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(51)
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(51)
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
T200 Expired
T3126 Expired
T3162 Expired
T3168 Expired
T3170 Expired
w
g
Ascom (2014)
26(51)
3.1
Introduction
3.2
Ascom (2014)
Document:
NT13-21914
27(51)
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(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
3.3.1
Call Initialization
3.3.2
Call Attempt
3.3.3
Ascom (2014)
Document:
NT13-21914
29(51)
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(51)
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(51)
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(51)
CDMA Events
Event Name
Symb.
Blocked Call
(red)
Call Attempt
(gray)
Description/Extra Information
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.
MO call: Origination (ACH) message sent with a
voice Service Option.
MT call: Page Response (ACH) message
received with a voice Service Option.
Call End
Call Established
(green)
Call Initiation
Call Setup
Dedicated Mode
Dropped Call
EV-DO 1x
Tune-away
EV-DO Access
Failure
EV-DO Access
Success
Ascom (2014)
Document:
NT13-21914
33(51)
Event Name
EV-DO Connection
Success
Symb.
Description/Extra Information
An EV-DO connection attempt completed
successfully.
Triggered by EV-DO Connection Attempt Report.
EV-DO Dynamic
Rate
EV-DO Handoff
1 Active
EV-DO Handoff
2 Actives
EV-DO Handoff
3 Actives
EV-DO Handoff
4 Actives
EV-DO Handoff
5 Actives
EV-DO Handoff
6 Actives
Ascom (2014)
Document:
NT13-21914
34(51)
Event Name
EV-DO Island
Symb.
Description/Extra Information
There is only a single active EV-DO pilot and no
candidates.
Triggered by EV-DO Pilot Sets Ver2 Report.
EV-DO Session
Failure
EV-DO Session
Success
Idle Handoff
Idle Handoff To
Analog
Idle Handoff To
CDMA
Idle Handoff To
EV-DO
Idle Mode
Ascom (2014)
Document:
NT13-21914
35(51)
Event Name
Missing CDMA
Neighbor
Symb.
Description/Extra Information
See algorithm description in section 4.1.
(olive
green
bar on
the right)
Narrowband
Interference
No Service Mode
Packet Mode
Polluter
Ascom (2014)
Soft Handoff
Complete
Traffic Handoff To
Analog
Document:
NT13-21914
36(51)
Event Name
Symb.
Traffic Handoff To
CDMA
Description/Extra Information
System change from Analog or EV-DO to 1x
during traffic.
Triggered by System Determination Last Main
Action Report.
Traffic Handoff To
EV-DO
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
, where
Ascom (2014)
7.
8.
If
9.
If
such that
Document:
NT13-21914
is a polluter.
37(51)
5.1
Ascom (2014)
Document:
NT13-21914
38(51)
5.2
Ascom (2014)
Document:
NT13-21914
39(51)
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
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
40(51)
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
41(51)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
First ACK
Cutoff point
Time in seconds
Outcome
Cause
Details of failure
Time in seconds
Details of failure
Time in seconds
Ascom (2014)
Document:
NT13-21914
42(51)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Cutoff point
Time in seconds
Outcome
Cause
Details of failure
Time in seconds
Details of failure
Time in seconds
Details of failure
Time in seconds
Cutoff point
Time in seconds
HTTP End
Outcome
HTTP Error
Cause
Details of failure
Time in seconds
Ascom (2014)
Document:
NT13-21914
43(51)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
HTTP Start
Cutoff point
Time in seconds
Outcome
Cause
Details of failure
Time in seconds
Time in seconds
(unrelated to KPIs)
IP events
IP Interruption Time
Time in seconds
Outcome
Ascom (2014)
This event is currently generated only when an LTE network is involved in the handover.
Document:
NT13-21914
44(51)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Cause
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
45(51)
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/en-us/library/
system.net.networkinformation.operationalstatus.aspx
5
Ascom (2014)
Document:
NT13-21914
46(51)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
SRVCC events
SRVCC Handover
Interruption Time (User
Plane)
Time in ms
Outcome
Streaming Start
Streaming Error
Cause
Streaming Intermediate
VSQI
MOS value
Ascom (2014)
Document:
NT13-21914
47(51)
Event Name
Streaming Quality MTQI
Symb.
Associated KPI
(or Description)
Extra Info
MOS value
MOS value
Streaming Reproduction
Cutoff
Streaming Reproduction
Start Delay
Time in seconds
Streaming Reproduction
Start Failure
Streaming Service
Access Time
Time in seconds
Streaming State
Outcome
Cause
IP address
IP address; Time in
seconds
Outcome
Cause
IP address
TCP events
Ascom (2014)
Document:
NT13-21914
48(51)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
Destination; Reached
(True/False)
Destination
UDP events
UDP Download End
Outcome
Cause
Packet loss in %
IP address
Outcome
Cause
Packet loss in %
IP address
VoIP events
(KPIs based on MTSI
events, which see)
VoIP End
Outcome
VoIP Error
Cause
VoIP Start
Ascom (2014)
Document:
NT13-21914
49(51)
Event Name
Symb.
Associated KPI
(or Description)
Extra Info
WAP events
WAP Activation Failure
Time in ms
WAP End
Outcome
WAP Error
Cause
Time in seconds
Time in seconds
Time in seconds
Time in seconds
WAP Start
Ascom (2014)
Document:
NT13-21914
50(51)
Symb.
Description/Extra Information
AQM Session
Complete
AQM Synched
Handover Speech
Interruption Downlink
Speech Interruption
Time Downlink
Ascom (2014)
Document:
NT13-21914
51(51)