Vous êtes sur la page 1sur 9

TEMS Investigation Call

Event Definitions
Technical Reference

TEMS Investigation Call Event Definitions

2009-05-14

Ascom 2009. All rights reserved.


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.

Public

2009-05-14

TEMS Investigation Call Event Definitions

Contents
1.
2.

Introduction ................................................................1
Description of Call Events.........................................1
2.1. Event State Machine ...............................................................1
2.2. Description of Call Events.......................................................3
2.2.1.
2.2.2.
2.2.3.
2.2.4.
2.2.5.
2.2.6.
2.2.7.
2.2.8.

TMS-06:000205 Uen Rev B

Call Initialization ......................................................................................3


Call Attempt ............................................................................................3
Call Attempt Retry...................................................................................3
Call Setup ...............................................................................................4
Call Established ......................................................................................4
Call End ..................................................................................................4
Blocked Call ............................................................................................5
Dropped Call ...........................................................................................5

2009-05-14

TEMS Investigation Call Event Definitions

1.

Introduction

This document provides an in-depth description of how 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).

2.

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.

TMS-06:000205 Uen Rev B

1(5)

TEMS Investigation Call Event Definitions

2009-05-14

Channel Request

(W2) RRC Connection


Setup Received

RRC Connection Setup Complete

Channel Release or
Immediate Assignment Reject

RRC Connection Reject

RRC Connection Setup

(G1) GSM Channel Requested


Channel Request

(W1) RRC Connection


Requested

RRC Connection Request

RRC Connection
Request

Immediate Assignment

(G2) GSM Channel Assigned

(W3) RRC Connection


Setup Complete Received
)
(UL
up
Setu
Set
p (D

L)

Setup (DL)

Setup (UL)

(1) CALL INIT

Setup (UL)

(0) NULL

Setup (DL)
Re

Connect

(4) CALL
DELIVERED

Call Confirmed

ase

Re
lea
se

Rele

se

(11) DISCONNECT
REQUEST

Release or
Release Complete

Alerting

lea

Disconnect (UL)

States
1,4,6,7,8,9

(12) DISCONNECT
INDICATION

(6) CALL
PRESENT

Disconnect (DL)

States
4, 7, 8, 9, 10

Connect
Co

nn

(9) MT CALL
CONFIRMED
ec

Alerting

(10) ACTIVE

Connect Acknowledge

(8) CONNECT
REQUEST

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-97-8-10. The central part of the diagram, including states 11 and 12, is concerned
with the handling of call disconnects.

2(5)

Public

2009-05-14

TEMS Investigation Call Event Definitions

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:

TMS-06:000205 Uen Rev B

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.

3(5)

TEMS Investigation Call Event Definitions

2.2.4.

2009-05-14

Call Setup

This event is generated in the following circumstances:


3.

Connect message received in state Call Init or in state MT Call Confirmed.

4.

Alerting message received in state Call Init or state MT Call Confirmed.

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

Extra Information
1.

Call end cause, one of the following strings:

2.

4(5)

MS initiated release
NW initiated release
User busy
Not a call, procedure completed with a SDCCH
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.

Public

2009-05-14

TEMS Investigation Call Event Definitions

2.2.7.

Blocked Call

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

Block type, one of the following:

No Immediate Assignment
No Traffic Channel Assignment
No Alerting or Connect
No Connect
No Call Confirmed
No Connect Acknowledge
No RRC Connection Setup
No RRC Connection Setup Complete
RRC Connection Reject
Abnormal RRC Connection Release
No Setup
No Radio Bearer Setup Complete
N-300 and T-300 expiry

2.

CC Cause: <str>, where <str> is a string. Included if the message that


generated the event included CC cause.

3.

"RR Cause: <str>", where <str> is a string. Included if the message that
generated the event included RR cause.

4.

Call time in ms, indicating the time since the event Call Initialization.

2.2.8.

Dropped Call

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

Drop type, one of the following:


Abnormal network
Abnormal RRC Connection Release
No service

TMS-06:000205 Uen Rev B

2.

Cause: <str>, where <str> is a string describing the cause of the drop.

3.

CC Cause: <str>, where <str> is a string. Included if the message that


generated the event included CC cause.

4.

Call duration in ms, indicating the time since the event Call Established.

5(5)