TEMS Investigation Call Event Definitions

Technical Reference

design and manufacturing. No part of this document may be reproduced in any form without the written permission of the copyright holder.TEMS Investigation Call Event Definitions 2009-05-14  Ascom 2009. All rights reserved. Ascom shall have no liability for any error or damage of any kind resulting from the use of this document. All other trademarks are the property of their respective holders. The contents of this document are subject to revision without notice due to continued progress in methodology. TEMS is a trademark of Ascom. Public .

... 2......................4 Call Established ........ 2........ Event State Machine ........................................................ 2................................1................2..5..........1 2...............................................................2....................................................................................................................................4 Call End ..................2.........................................................2009-05-14 TEMS Investigation Call Event Definitions Contents 1.2..............................................2..5 TMS-06:000205 Uen Rev B .................2...........2............6.......................... 2.3 Call Attempt Retry... 2.2..... Description of Call Events...............................4.......1 Description of Call Events................................................3 Call Attempt ....5 Dropped Call ... 2........................... 2........... 2.......3 2.......................................2.........1 2........3...................................2...............................4 Blocked Call ........................ Introduction ..... Call Initialization ...........................7.....8..........1...................................................................3 Call Setup ...........................

.

1.2009-05-14 TEMS Investigation Call Event Definitions 1. TMS-06:000205 Uen Rev B 1(5) . it is helpful to refer to the state machine depicted below. The document should be regarded as supplementary to the account of the call events in the user documentation (“Information Elements and Events” volume). 2. 2. 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). Description of Call Events Event State Machine When explaining the generation of call events in TEMS Investigation.

7.6. MT calls are represented by states 6-97-8-10. The central part of the diagram.9 Disconnect (UL) (12) DISCONNECT INDICATION Connect Disconnect (DL) States 4.4. 8. 7.TEMS Investigation Call Event Definitions 2009-05-14 RRC Connection Request Channel Request RRC Connection Request (W1) RRC Connection Requested RRC Connection Reject (G1) GSM Channel Requested Channel Release or Immediate Assignment Reject Channel Request RRC Connection Setup Immediate Assignment (W2) RRC Connection Setup Received RRC Connection Setup Complete (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 Re Setup (DL) (6) CALL PRESENT lea se Alerting Rele Release or Release Complete ase (11) DISCONNECT REQUEST Call Confirmed Connect (4) CALL DELIVERED Re lea se States 1. 10 Co nn ec t (9) MT CALL CONFIRMED Alerting (10) ACTIVE Connect Acknowledge (8) CONNECT REQUEST Connect (7) CALL RECEIVED The state machine covers both WCDMA and GSM. 9. 2(5) Public . The top left part shows the WCDMA service setup. is concerned with the handling of call disconnects. MO calls are represented by states 1-4-10. Note that these setup procedures are generic and not unique to the speech service. while the top right part shows the service setup in GSM. including states 11 and 12.8.

3. 3.2. states with “G” in front of the number are valid only for GSM. States without a letter are valid in both GSM and WCDMA. TMS-06:000205 Uen Rev B 3(5) . so it is not possible to have the Call Attempt event triggered by CM Service Request.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. Please note that the depiction of the message traffic and state transitions is a simplified one. Setup message received in state NULL. 2. 2. 2. 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. with only the most important mechanisms included. (GSM) Channel Request message with establishment cause “Speech” received in state GSM Channel Requested. 2. states with “W” in front of the number are valid only for WCDMA.) 2. The event is triggered by a phone mode report (i.1. Call Attempt This event is generated in the following circumstances: 1. 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. (WCDMA) RRC Connection Request message with establishment cause “Speech” received in state RRC Connection Requested. (The CM Service Request message itself does not have a cause value indicating whether speech is being requested.e. not by a Layer 3 message) which in turn is generated at the time the “yes” (or “send”) key is pressed. Description of Call Events Call Initialization This event is generated only when the call is initiated by a command sequence and only for mobile-originated (MO) calls.2. 2.2.2. For certain messages the direction (UL or DL) is indicated. Layer 3 and CC messages are represented by arrows. Call Attempt Retry 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. such state transitions are not shown in the diagram.

Alerting message received in state Call Init or state MT Call Confirmed. step 2). Included only if the Call Initialization event has been previously generated. Call setup time in ms. procedure completed with a SDCCH” (cf. measured from Call Initialization (thus more accurately reflecting the user-perceived setup time). Extra Information 1. The following event information is then appended: “Not a call. Call Established This event is generated when entering state Active following the message Connect (MO call) or Connect Acknowledge (MT call). procedure completed with a SDCCH Technical drop: Release Missing Call duration in ms.5. Call end cause. 4(5) Public . measured from Call Attempt.2. for MO calls in a command sequence. Channel Release message received in state GSM Channel Assigned. i. Extra Information   Call direction: “MO call” or “MT call”. causing return to state NULL without any of the events Blocked Call or Dropped Call having been generated during the call. below). User setup time in ms.6. indicating the time elapsing between the event Call Established and the message Disconnect or (if. this is not included if Call Attempt was triggered by the Setup message (see section 2.2. exceptionally. no Disconnect is received) the message Release.  2. Connect message received in state Call Init or in state MT Call Confirmed. one of the following strings: MS initiated release NW initiated release User busy Not a call.2.2. 2.TEMS Investigation Call Event Definitions 2009-05-14 2.      2. Call Setup This event is generated in the following circumstances: 3. Call End This event is generated in the following circumstances: 1. 2.e.4. i. Release message sent or received by phone. 4.2.e. the first call attempt.

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 “CC Cause: <str>”. 3. where <str> is a string. 2.2. Call duration in ms. TMS-06:000205 Uen Rev B 5(5) . Included if the message that generated the event included CC cause. Included if the message that generated the event included CC cause. "RR Cause: <str>". one of the following:              2. Extra Information 1. where <str> is a string. “Cause: <str>”. 4. Dropped Call This event is generated if the call is abnormally ended after the event Call Established. indicating the time since the event Call Established.7. Blocked Call This event is generated if the call is abnormally ended before the event Call Established is generated. Included if the message that generated the event included RR cause. one of the following:  Abnormal network  Abnormal RRC Connection Release  No service 2. Extra Information 1.8. Call time in ms. Drop type. indicating the time since the event Call Initialization. Block type. 3. “CC Cause: <str>”.2009-05-14 TEMS Investigation Call Event Definitions 2. 4. where <str> is a string.2. where <str> is a string describing the cause of the drop.

Sign up to vote on this title
UsefulNot useful