Professional Documents
Culture Documents
TEMS Investigation KPI Definitions - Video Telephony
TEMS Investigation KPI Definitions - Video Telephony
TEMS Investigation KPI Definitions - Video Telephony
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
Contents
1. 2. Introduction ................................................................1 KPIs for Video Telephony..........................................1
2.1. 2.2. 2.3. 2.4. Service Non-Accessibility [%] .................................................1 Service Access Time [s] ..........................................................1 Call Cut-off Ratio [%] ..............................................................2 Signaling Diagram...................................................................3
2009-05-14
1.
Introduction
This document describes in detail how KPIs (Key Performance Indicators) for the video telephony service are calculated in TEMS Investigation 8.0. Note that KPIs are computed only for mobile-originated (MO) calls, not for mobileterminated (MT) calls. The KPI definitions are based on ETSI TS 102 250-2 V1.4.1. How input data to KPI calculations is collected is not dealt with in this document.
2.
2.1.
Denotes the probability that the end-customer cannot access the service when requested although the phone indicates having network coverage: # of unsuccessful call attempts Service Non-Accessibility [%] = ------------------------------------------- x 100 total # of call attempts Start trigger: RRC Connection Request message sent. There can be more than one RRC Connection Request message per call attempt; the first message shall then be taken as start trigger. Trigger point 1 in section 2.4 Stop trigger: Connect message received from the MSC. In an unsuccessful call attempt, this trigger point is never reached. Trigger point 30 in section 2.4
2.2.
Denotes the time from the moment the send button is pressed on the calling phone (after input of MSISDN) until the calling phone receives the Connect message:
Start trigger: RRC Connection Request message sent. There can be more than one RRC Connection Request message per call attempt; the first message shall then be taken as start trigger. Trigger point 1 in section 2.4
1(3)
2009-05-14
Stop trigger: Connect message received from the MSC. Trigger point 30 in section 2.4
2.3.
Denotes the probability that a successful service access is ended by a cause other than the intentional termination of the user (calling or called party): # of dropped calls Call Cut-off Ratio [%] = ------------------------------------------- x 100 # of successful call attempts Start trigger: Connect message received. Trigger point 30 in section 2.4 Stop trigger: Disconnect message sent. Trigger point 35 in section 2.4
2(3)
Public
2009-05-14
2.4.
UE
Signaling Diagram
Network
1 4 5 7 9 12 13 Service 16 17 19 22 24 25 28 30 33 Quality
RRC Connection Request RRC Connection Setup Insynch Ind RRC Connection Setup Complete CM Service Request Security Mode Command Security Mode Complete Idenity Request Identity Response Setup Call Proceeding Radio Bearer Setup Radio Bearer Setup Complete Alerting Connect Connect Ack
2 3 6 8 10 11 14 15 18 20 21 23 26 27 32 34
Conversation
35 38 39 42 43 46 47
Disconnect Relaese Release complete Radio Bearer Release Radio Bearer Release Complete RRC Connection Release RRC Connection Release Complete
36 37 40 41 44 45 48
3(3)