TEMS Investigation Call Event

Definitions

Prepared by:
Ascom Network Testing

Date:
5/6/2013

Document:
NT13-20145

Ascom (2013)
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 (2013)

Introduction ................................................................ 1

Description of Call Events ........................................ 1

2.1
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
2.2.8
2.2.9

Event State Machine .................................................................1

Description of Call Events .......................................................3
Call Initialization ..........................................................................3
Call Attempt ................................................................................3
Call Attempt Retry.......................................................................3
Call Setup ...................................................................................3
Call Established ..........................................................................4
Call Re-established.....................................................................4
Call End ......................................................................................4
Blocked Call................................................................................5
Dropped Call...............................................................................6

Document:
NT13-20145

Introduction

This document provides an in-depth description of how GSM and WCDMA

call events are generated in TEMS Investigation. 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 the user documentation (Information Elements and Events
volume).

Description of Call Events

2.1

Event State Machine

When explaining the generation of call events in TEMS Investigation, it is

helpful to refer to the state machine depicted below.

Ascom (2013)

Document:
NT13-20145

1(6)

Channel Request

RRC Connection
Request

(W2) RRC Connection

Setup Received

RRC Connection Setup Complete

Channel Request

RRC Connection Setup

(G1) GSM Channel Requested

Channel Release or
Immediate Assignment Reject

RRC Connection Reject

RRC Connection Request

(W1) RRC Connection

Requested

Immediate Assignment

(G2) GSM Channel Assigned

(W3) RRC Connection

Setup Complete Received

up
Set

)
(UL
Setu
p (D
L)

Setup (DL)

Setup (UL)

(1) CALL INIT

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 (2013)

Document:
NT13-20145

2(6)

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.

2.2

Description of Call Events

2.2.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.

2.2.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.)

2.2.3

Call Attempt Retry

This event is generated in the following circumstances:

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.

2.2.4

Call Setup

This event is generated in the following circumstances:

Ascom (2013)

Document:
NT13-20145

3(6)

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.
2.2.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 2.2.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.

2.2.5

Call Established

This event is generated when entering state Active following the message
Connect (MO call) or Connect Acknowledge (MT call).

2.2.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:

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 2.2.9.1).

2.2.7

Call End

This event is generated in the following circumstances:

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).

Ascom (2013)

Document:
NT13-20145

4(6)

2.2.7.1 Extra Information

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.

2.2.8

Blocked Call

This event is generated if the call is abnormally ended before the event Call
Established is generated.
2.2.8.1 Extra Information

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

Ascom (2013)

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.

Document:
NT13-20145

5(6)

2.2.9

Dropped Call

This event is generated if the call is abnormally ended after the event Call
Established.
2.2.9.1 Extra Information

Drop type, one of the following:

o Abnormal network
o Abnormal RRC Connection Release
o No service
o Re-establishment failure
o T313 expired

Ascom (2013)

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.

Document:
NT13-20145

6(6)