Documente Academic
Documente Profesional
Documente Cultură
2010-10-08
Ascom 2010. 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
2010-10-08
Contents
1. 2. Introduction ................................................................. 1 Service Independent KPIs .......................................... 1
2.1. 2.2. 2.3. 2.4. 2.5. 2.6. Network Unavailability [%] ...................................................... 1 Attach Failure Ratio [%] .......................................................... 1 Attach Setup Time [s] .............................................................. 2 PDP Context Activation Failure Ratio [%] ............................... 2 PDP Context Activation Time [s] ............................................. 2 PDP Context Cut-off Ratio [%] ................................................ 3
3.
2010-10-08
1.
Introduction
This document describes in detail how KPIs (Key Performance Indicators) for the WAP service are calculated in TEMS Investigation. How input data to KPI calculations is collected is not dealt with in this document.
2.
2.1.
Denotes the probability that no packet-switched network is available in the cell currently used by the customer. In GSM, the phone has access to a PS network if it has received System Information 13. This message is read once per KPI measurement cycle, at the beginning of the cycle. In WCDMA, matters are simpler: the phone is always known to have access to a PS network. The information element "Mode - System" in TEMS Investigation indicates whether the phone is connected to a WCDMA or a GSM network.
# of unsuccessful attempts to access PS network Network Unavailability [%] = -------------------------------------------------------------------- x 100 total # of attempts to access PS network
Because of the nature of this KPI, no start or stop triggers can be identified for it in the signaling diagrams.
2.2.
Denotes the probability that a subscriber cannot attach to the GPRS/UMTS PS network: # of unsuccessful attach attempts Attach Failure Ratio [%] = ----------------------------------------------- x 100 total # of attach attempts Start trigger: Phone sending Attach Request message. Trigger point 1 in sections 3.15 Stop trigger: Phone receiving Attach Accept/Reject message. Trigger point 4 in sections 3.15
1(9)
2010-10-08
2.3.
Denotes the length of the time period taken to attach to the GPRS/UMTS PS network:
Start trigger: Phone sending Attach Request message. Trigger point 1 in sections 3.15 Stop trigger: Phone receiving Attach Accept message. Trigger point 4 in sections 3.15
2.4.
Denotes the probability that the PDP context cannot be activated. It is the ratio of unsuccessful PDP context activation attempts to the total number of PDP context activation attempts:
# of unsuccessful PDP context activation attempts PDP Context Activation Failure Ratio [%] = ---------------------------------------------------------------------- x 100 total # of PDP context activation attempts
Start trigger: Phone sending PDP Context Activation Request message. Trigger point 5 in sections 3.15 Stop trigger: Phone receiving PDP Context Activation Accept message. Trigger point 8 in sections 3.15
2.5.
Denotes the length of the time period taken to activate a PDP context:
PDP Context Activation Time [s] = tPDP Context Activation Accept tPDP Context Activation Request
Start trigger: Phone sending PDP Context Activation Request message. Trigger point 5 in sections 3.15 Stop trigger: Phone receiving PDP Context Activation Accept message. Trigger point 8 in sections 3.15
2(9)
Public
2010-10-08
2.6.
Denotes the probability that a PDP context is deactivated without this being initiated intentionally by the user:
# of PDP context deactivations (not initiated by user) PDP Context Cut-off Ratio [%] = ------------------------------------------------------------------------ x 100 total # of successfully activated PDP contexts
Start trigger: Phone receiving PDP Context Activation Accept message. Trigger point 8 in sections 3.15 Stop trigger: Phone receiving the last data packet containing content. Trigger point 20 in sections 3.15 PDP context deactivation not initiated intentionally by the user can be caused by either SGSN failure or GGSN failure, so the PDP context may be deactivated either by the SGSN or by the GGSN. Note: The precondition for measuring this parameter is that a PDP context has been successfully established.
3.
(not in ETSI)
3.1.
Denotes the probability that a subscriber cannot access the service successfully due to a failure that has occurred either during PDP context activation or during service access. This means that the data transfer cannot be started: # of unsuccessful attempts Service Non-Accessibility [%] = -------------------------------------- x 100 total # of attempts Start trigger: PDP Context Activation Request sent. Trigger point 5 in section 3.15 Stop trigger: Reception of the first data packet containing content. Trigger point 18 in section 3.15
3.2.
Denotes the period of time it takes to access a service successfully, from the moment the dial-up connection is established until the first data packet is received:
3(9)
2010-10-08
Start trigger: PDP Context Activation Request sent. Trigger point 5 in section 3.15 Stop trigger: Reception of the first data packet containing content. Trigger point 18 in section 3.15
3.3.
Denotes the probability that, after successfully activating a PDP context, a subscriber cannot access the service, so that the data transfer cannot be started: # of unsuccessful service accesses IP Service Access Failure Ratio [%] = -------------------------------------------------- x 100 total # of service access attempts Start trigger: WSP Connect Request sent. Trigger point 9 in section 3.15 Stop trigger: Reception of the first data packet containing content. Trigger point 18 in section 3.15
3.4.
Denotes the time period needed to establish a TCP/IP connection to the WAP server, from sending the initial query to a server until the first data packet is received:
IP Service Setup Time [s] = treception of first data packet tfirst [SYN] sent
Start trigger: WSP Connect Request sent. Trigger point 9 in section 3.15 Stop trigger: Reception of the first data packet containing content. Trigger point 18 in section 3.15
3.5.
Denotes the average data rate measured throughout the entire connect time (application throughput):
4(9)
Public
2010-10-08
file size (kB) x 8 Mean Data Rate [kbit/s] = ----------------------------------tlast data packet tfirst data packet Start trigger: Reception of the first data packet containing content. Trigger point 18 in section 3.15 Stop trigger: Reception of the last data packet containing content. Trigger point 20 in section 3.15
3.6.
Denotes the probability that a data transfer cannot be completed when it has been started successfully: # of incomplete data transfers Data Transfer Cut-off Ratio [%] = ----------------------------------------------------- x 100 # of successfully started data transfers Start trigger: Reception of the first data packet containing content. Trigger point 18 in section 3.15 Stop trigger: Reception of the last data packet containing content. Trigger point 20 in section 3.15
3.7.
Denotes the probability that the subscriber cannot activate the WAP session: # of failed WAP activations WAP Activation Failure Ratio [%] = ----------------------------------------------- x 100 total # of WAP activation requests Start trigger: WSP Connect Request sent. Trigger point 9 in section 3.15 Stop trigger: WSP Connect Reply received. Trigger point 12 in section 3.15
3.8.
Denotes the length (in ms) of the time period taken to activate the WAP session:
WAP Activation Time [ms] = tWSP Connect Reply tWSP Connect Request
5(9)
2010-10-08
Start trigger: WSP Connect Request sent. Trigger point 9 in section 3.15 Stop trigger: WSP Connect Reply received. Trigger point 12 in section 3.15
3.9.
Denotes the probability that a WAP page request is unsuccessful after a timeout period. This parameter is only calculated if the WAP activation attempt and/or the PDP Context activation attempt is successful. # of failed WAP page requests WAP Page Request Failure Ratio [%] = -------------------------------------------- x 100 total # of WAP page requests
Start trigger: WAP Get URL sent. Trigger point 15 in section 3.15 Stop trigger: Reception of the first data packet containing content. Trigger point 18 in section 3.15
3.10.
Denotes the time (in seconds) elapsed from selection of the WAP page link until reception of the first data packet containing WAP page content. Only successful measurements are taken into account when calculating the average time:
WAP Page Request Time [s] = treception of first data packet tselection of WAP site
Start trigger: WAP Get URL sent. Trigger point 15 in section 3.15 Stop trigger: Reception of the first data packet containing content. Trigger point 18 in section 3.15
3.11.
Denotes the time (in seconds) taken to load the requested portal homepage including all images and navigational elements, i.e. the average time between initiation of WAP service access and the display of the homepage via GPRS/UMTS. Only successful measurements are taken into account when calculating the average time.
6(9)
Public
2010-10-08
WAP Portal Access Time [s] = tappearance of WAP portal homepage tinitiation of access
Start trigger: PDP Context Activation Request sent. Trigger point 5 in section 3.15 Stop trigger: Reception of the last data packet containing content. Trigger point 20 in section 3.15
3.12.
Denotes the probability that the requested portal homepage, including all images and navigational elements, is not successfully downloaded:
# failed WAP portal homepage download atts WAP Portal Non-accessibility [%] = -------------------------------------------------------------- x 100 total # WAP portal homepage download atts
Start trigger: PDP Context Activation Request sent. Trigger point 5 in section 3.15 Stop trigger: Reception of the last data packet containing content. Trigger point 20 in section 3.15
3.13.
Denotes the time (in seconds) needed to download the requested portal homepage, including all images and navigational elements. Only successful measurements are taken into account when calculating the average time.
WAP Site Access Time [s] = tappearance of WAP page tselection of WAP site
Start trigger: WAP Get URL sent. Trigger point 15 in section 3.15 Stop trigger: Reception of the last data packet containing content. Trigger point 20 in section 3.15
3.14.
Denotes the probability that a WAP page, including all images and navigational elements, is not successfully downloaded. This parameter uses the GPRS/UMTS service. When starting the test, a WAP connection between the mobile and the WAP server already exists.
7(9)
2010-10-08
# failed WAP site access attempts WAP Site Non-accessibility [%] = ------------------------------------------------ x 100 total # WAP site access attempts Start trigger: WAP Get URL sent. Trigger point 15 in section 3.15 Stop trigger: Reception of the last data packet containing content. Trigger point 20 in section 3.15
8(9)
Public
2010-10-08
3.15.
UE
Signaling Diagram
Network
Attach Request Attach Response PDP Context Activation PDP Context Activation Accept WSP Connect Request WSP Connect Reply WTP [ACK] WAP Get URL WAP Data [first block]
2 3 6 7 10 11 14 16 17
Data
Data Transfer
20
19
9(9)