SFD Truecall Umts 63

TrueCall
System Features Document

T r u e C a lS y s te mF e a tu r e s Do c u me n t
Software Version 6.3.0

Rev. 001 / 2020-03-31
Mobile Access
Appendix B: UMTS KPIs
© NETSCOUT CONFIDENTIAL & PROPRIETARY

Use of this product is subject to the End User License Agreement available at http://www.NetScout.com/legal/terms-and-
conditions or which accompanies the product at the time of shipment or, if applicable, the legal agreement executed by and
between NetScout Systems, Inc. or one of its wholly-owned subsidiaries ("NETSCOUT") and the purchaser of this product
("Agreement").
Government Use and Notice of Restricted Rights: In U.S. government ("Government") contracts or subcontracts, Customer will
provide that the Products and Documentation, including any technical data (collectively "Materials"), sold or delivered pursuant
to this Agreement for Government use are commercial as defined in Federal Acquisition Regulation ("FAR") 2.101and any
supplement and further are provided with RESTRICTED RIGHTS. All Materials were fully developed at private expense. Use,
duplication, release, modification, transfer, or disclosure ("Use") of the Materials is restricted by the terms of this Agreement and
further restricted in accordance with FAR 52.227-14 for civilian Government agency purposes and 252.227-7015 of the Defense
Federal Acquisition Regulations Supplement ("DFARS") for military Government agency purposes, or the similar acquisition
regulations of other applicable Government organizations, as applicable and amended. The Use of Materials is restricted by the
terms of this Agreement, and, in accordance with DFARS Section 227.7202 and FAR Section 12.212, is further restricted in
accordance with the terms of NETSCOUT'S commercial End User License Agreement. All other Use is prohibited, except as
described herein.
This Product may contain third-party technology. NETSCOUT may license such third-party technology and documentation ("Third-
Party Materials") for use with the Product only. In the event the Product contains Third-Party Materials, or in the event you have
the option to use the Product in conjunction with Third-Party Materials (as identified by NETSCOUT in the Documentation
provided with this Product), then such third-party materials are provided or accessible subject to the applicable third-party terms
and conditions contained either in the "Read Me" or "About" file located in the Software or on an Application CD provided with
this Product, or in an appendix located in the documentation provided with this Product. To the extent the Product includes
Third-Party Materials licensed to NETSCOUT by third parties, those third parties are third-party beneficiaries of, and may enforce,
the applicable provisions of such third-party terms and conditions.
Open-Source Software Acknowledgement: This product may incorporate open-source components that are governed by the GNU
General Public License ("GPL") or licenses that are compatible with the GPL license ("GPL Compatible License"). In accordance
with the terms of the GNU GPL, NETSCOUT will make available a complete, machine-readable copy of the source code
components of this product covered by the GPL or applicable GPL Compatible License, if any, upon receipt of a written request.
Please identify the product and send a request to:
NETSCOUT SYSTEMS, INC
GNU GPL Source Code Request

310 Littleton Road
Westford, MA 01886
Attn: Legal Department
TrueCall System Features Document 2

Ver. 6.3.0 | 2020-03-31
992-0608-08 Rev. 001
To the extent applicable, the following information is provided for FCC compliance of Class A devices:
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the
FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required
to correct the interference at their own expense.
Modifications to this product not authorized by NETSCOUT could void the FCC approval and terminate your authority to
operate the product. Please also see NETSCOUT's Compliance and Safety Warnings for NetScout Hardware Products
document, which can be found in the documents accompanying the equipment, or in the event such document is not
included with the product, please see the compliance and safety warning section of the user guides and installation
manuals.
No portion of this document may be copied, photocopied, reproduced, translated, or reduced to any electronic medium or
machine form without prior consent in writing from NETSCOUT. The information in this document is subject to change without
notice and does not represent a commitment on the part of NETSCOUT.
The products and specifications, configurations, and other technical information regarding the products described or referenced
in this document are subject to change without notice and NETSCOUT reserves the right, at its sole discretion, to make changes at
any time in its technical information, specifications, service, and support programs. All statements, technical information, and
recommendations contained in this document are believed to be accurate and reliable but are presented "as is" without
warranty of any kind, express or implied. You must take full responsibility for their application of any products specified in this
document. NETSCOUT makes no implied warranties of merchantability or fitness for a purpose as a result of this document or
the information described or referenced within, and all other warranties, express or implied, are excluded.
Except where otherwise indicated, the information contained in this document represents the planned capabilities and intended
functionality offered by the product and version number identified on the front of this document. Screen images depicted in this
document are representative and intended to serve as example images only.
Copyright NETSCOUT 2009-2020. All rights reserved.
992-0608-08-001
200331

Table of Contents
T r u e C a lS y s te mF e a tu r e s Do c u me n t 1
T a b le o fC o n te n ts 4
What’s New 5
A Common UMTS Overview 6
A.1 Common UMTS KPIs 6
A.2 Call Attribute / LSR Field: Descriptions and Units 45
A.3 Common UMTS Enumerated Values 60
B TrueCall LSR Data Types 74

What’s New
Feature ID Description
F-10390 TrueCall Support for Serving System PLMN ID and 5G NSA ERs
This feature adds the following function groups to TrueCall:
l Serving System PLMN-ID (Controlled Release in 6.3.0)
l New 5G NSA Call Table attributes
The following Call Attributes/LSRs were added, modified, or deleted for 6.3.0.
Call Attribute/LSR Description of Change

PLMN ID New Call Attribute for all vendors (Controlled Release in 6.3.0)

A Common UMTS Overview
GeoSoft RAN is a prerequisite for support of TrueCall KPIs, Call Attributes, and LSR fields in a Common UMTS client.
The vendors supported by the Common UMTS Client are:
l Huawei OSSii NBI

l Nokia
l ZTE
l Ericsson GPEH
If a vendor is not in a customer network, any vendor-specific (not Common) KPIs and Call Attributes and LSR fields specific to that vendor
can be configured on the TrueCall server to be hidden.
A.1 Common UMTS KPIs

The following maps and KPIs are supported in TrueCall for Common UMTS:
Note: KPI Explorer Headings are in bold text.

Ver. 6.3.0 | 2020-03-31 A Common UMTS Overview
992-0608-08 Rev. 001
KPI Name Description Unit Vendor Widget Support
Map KPI Top Top Top

Explorer NE Subscriber Device
Best Server by PSC of the cell with the most occurrences as Last RSCP PSC in the PSC All √
Occurrence selected calls located in the bin.
Accessibility
RRC
Establishment
RRC Connection Number of records with the New Connection Start Type. # All √ √ √ √ √
Requests
RRC Connection Number of records with New Connection Start Type for which # All √ √ √ √ √
Requests CS RRC Connection Request with CS domain indication is received.
Domain
RRC Connection Number of records with New Connection Start Type for which # All √ √ √ √ √
Requests PS RRC Connection Request with PS domain indication is received.
Domain
RRC Failed Number of records with the Failed Attempt RRC Setup Result . # All √ √ √ √ √
Attempts
RRC Failed Number of records with the Failed Attempt RRC Setup Result for # All √ √ √ √ √
Attempts CS which RRC Connection Request with CS domain indication is
Domain received.
RRC Failed Number of records with the Failed Attempt RRC Setup Result for # All √ √ √ √ √
Attempts PS which RRC Connection Request with PS domain indication is
Domain received.
RRC Failed Percentage of RRC Connection Establishment procedures that % All √ √ √ √ √
Attempt Rate fail determined by dividing the number of RRC Failed Attempts by
the number of RRC Connection Requests.

992-0608-08 Rev. 001
Map KPI Top Top Top

RRC Failed Percentage of CS domain RRC Connection Establishment % All √ √ √ √ √
Attempt Rate procedures that fail determined by dividing the number of RRC
CS Domain Failed Attempts CS Domain by the number of RRC Connection
Requests CS Domain.
RRC Failed Percentage of PS domain RRC Connection Establishment % All √ √ √ √ √
Attempt Rate PS procedures that fail determined by dividing the number of RRC
Domain Failed Attempts PS Domain by the number of RRC Connection
Requests PS Domain.
RAB
Establishment
CS Domain
CS RAB Setup Number of new CS Radio Access Bearers (RABs) requested with # All √ √ √ √ √
Attempts the RANAP RAB Assignment procedure.
CS RAB Setup Number of CS Radio Access Bearers (RABs) requested with the # All √ √ √ √ √
Failures RANAP RAB Assignment procedure that fail to be established
CS RAB Setup Percentage of CS Radio Access Bearers (RABs) requested with % All √ √ √ √ √
Failure Rate the RANAP RAB Assignment procedure that fail to be established
PS Domain
PS RAB Setup Number of new PS Radio Access Bearers (RABs) requested with # All √ √ √ √ √
Attempts the RANAP RAB Assignment procedure.
PS RAB Setup Number of PS Radio Access Bearers (RABs) requested with the # All √ √ √ √ √
Failures RANAP RAB Assignment procedure that fail to be established
PS RAB Setup Percentage of PS Radio Access Bearers (RABs) requested with % All √ √ √ √ √
Failure Rate the RANAP RAB Assignment procedure that fail to be established
Security
Mode Control

992-0608-08 Rev. 001
Map KPI Top Top Top

RANAP Security Number of RANAP Security Mode procedures started by the # All √ √ √ √ √
Mode Attempts Network.
RANAP Security Number of RANAP Security Mode procedures started by the # All √ √ √ √ √
Mode Failures Network that fail.
RANAP Security Percentage of RANAP Security Mode procedures started by the % All √ √ √ √ √
Mode Failure Network that fail.
Rate
Paging
Paging Type
1
Type 1 Paging Number of Paging Type 1 pages successfully completed as # All √ √ √ √ √
Successes indicated by reception of either an RRM Paging Response or
GMM Service Request indicating a paging response
Paging Type
2
Type 2 Paging Number of Paging Type 2 page attempts as indicated by the RRC # All √ √ √ √ √
Attempts Paging Type 2 message.
Type 2 Paging Number of Paging Type 2 pages that fail as indicated by the # All √ √ √ √ √
Failures absence of an RRM Paging Response or GMM Service Request
that marks it as a paging response.
Type 2 Paging Percentage of Paging Type 2 page attempts that fail. % All √ √ √ √ √
Failure Rate
Retainability
RRC
Connections

992-0608-08 Rev. 001
Map KPI Top Top Top

Normal The Normal Releases KPI includes records with Final Disposition # All √ √ √ √ √
Releases Normal Release, Redirection, Cell Change Order and IRAT Cell
Reselection as well as those with Final Disposition Relocation Out
that are outgoing IRAT handovers.
Dropped The Dropped Connections KPI includes records with Final # All √ √ √ √ √
Connections Disposition Dropped Connection and Failed Incoming Relocation.
Dropped Dropped Connections as a percentage of the sum of Normal % All √ √ √ √ √
Connection Releases and Dropped Connections where Normal Releases
Rate includes records with Final Disposition Normal Release,
Redirection, Cell Change Order and IRAT Cell Reselection as well
as those with Final Disposition Relocation Out that are outgoing
IRAT handovers, and where Dropped Connections includes
records with Final Disposition Dropped Connection and Failed
Incoming Relocation.
CS RABs
CS RABs Number of Radio Access Bearers (RABs) released in the CS # All √ √ √ √ √
Released domain is determined from the number of CS RABs released
including CS RABs setup as a result of RANAP Relocation
Resource Allocation as well as RANAP RAB Establishment
procedures. The Number of CS RABs Released includes CS RABs
for which radio bearers are present at the end of the connection,
including connections released as a result of a serving RNC
relocation.

992-0608-08 Rev. 001
Map KPI Top Top Top

CS RABs Number of Radio Access Bearers (RABs) that are released # All √ √ √ √ √
Dropped abnormally in the CS domain is determined by aggregating the
number of CS RABs released as a result of RANAP signaling
connection or RAB release procedure that has RANAP Cause
indicating abnormal release together with the number of CS
RABs released as a result of a dropped RRC connection. At the
end of the call, all CS RABs that remain active are counted as CS
RAB Drops if the call has been determined to a Dropped
Connection. A Dropped connection is call for which (1) a RANAP
IU RELEASE COMMAND has been received and for which the last
RANAP IU RELEASE COMMAND has Cause not indicative of a
normal release, or, (2) an RRC Connection Release has been
received with Release Cause indicative of an abnormal release ,
or (3) a RANAP IU RELEASE REQUEST is received. and a RANAP IU
RELEASE COMMAND Is either not received or has Cause Release
Due to UTRAN Generated Reason, and the last RANAP IU
RELEASE REQUEST has Cause indicative of abnormal release, or
(4) was dropped due to failure of the URA update procedure, or
(5) was dropped due to the failure of the cell update procedure.
RANAP Cause values other than those contained in the following
list are considered to be indicative of abnormal release:
Successful Relocation, Release Due To UTRAN Generated
Reason, User Inactivity, Time Critical Relocation, No Remaining
RAB, Release Due To UE Generated Signaling Connection
Release, Resource Optimization Relocation, Normal Release, CS
Fallback Triggered, and Network Optimization. The following RRC
Release Cause values are considered to be indicative of
abnormal release: Preemptive Release, Congestion,
Reestablishment Reject.

992-0608-08 Rev. 001
Map KPI Top Top Top

CS RAB Drop Percentage of active Radio Access Bearers (RABs) that are % All √ √ √ √ √
Rate dropped in the CS domain as determined by dividing the number
of CS RABs released abnormally by the total number of CS RABs
released.
PS RABs
PS RABs Number of Radio Access Bearers (RABs) released in the PS # All √ √ √ √ √
Released domain is determined from the number of PS RABs released
including PS RABs setup as a result of RANAP Relocation
Resource Allocation as well as RANAP RAB Establishment
procedures. The Number of PS RABs Released includes PS RABs
for which radio bearers are present at the end of the connection,
including connections released as a result of a serving RNC
relocation.

992-0608-08 Rev. 001
Map KPI Top Top Top

PS RABs Number of Radio Access Bearers (RABs) that are released # All √ √ √ √ √
Dropped abnormally in the PS domain is determined by aggregating the
number of PS RABs released as a result of RANAP signaling
connection or RAB release procedure that has RANAP Cause
indicating abnormal release together with the number of PS
RABs released as a result of a dropped RRC connection. At the
end of the call, all PS RABs that remain active are counted as PS
RAB Drops if the call has been determined to a Dropped
Connection. A Dropped connection is call for which (1) a RANAP
IU RELEASE COMMAND has been received and for which the last
RANAP IU RELEASE COMMAND has Cause not indicative of a
normal release, or, (2) an RRC Connection Release has been
received with Release Cause indicative of an abnormal release ,
or (3) a RANAP IU RELEASE REQUEST is received. and a RANAP IU
RELEASE COMMAND Is either not received or has Cause Release
Due to UTRAN Generated Reason, and the last RANAP IU
RELEASE REQUEST has Cause indicative of abnormal release, or
(4) was dropped due to failure of the URA update procedure, or
(5) was dropped due to the failure of the cell update procedure.
RANAP Cause values other than those contained in the following
list are considered to be indicative of abnormal release:
Successful Relocation, Release Due To UTRAN Generated
Reason, User Inactivity, Time Critical Relocation, No Remaining
RAB, Release Due To UE Generated Signaling Connection
Release, Resource Optimization Relocation, Normal Release, CS
Fallback Triggered, and Network Optimization. The following RRC
Release Cause values are considered to be indicative of
abnormal release: Preemptive Release, Congestion,
Reestablishment Reject.

992-0608-08 Rev. 001
Map KPI Top Top Top

PS RAB Drop Percentage of active Radio Access Bearers (RABs) that are % All √ √ √ √ √
Rate dropped in the PS domain as determined by dividing the number
of PS RABs released abnormally by the total number of PS RABs
released.
Utilization
Unique IMSIs Number of unique IMSI contained in the set of records processed # All √ √ √ √
Median Note: The duration includes time required to release the Iu s All √ √ √ √
Duration interface as well as all radio links.
CS Demand Total CS Demand is calculated by dividing total CS RAB use over Erlang All √ √ √ √ √
all calls by the length of the query.
CS Demand per CS Demand per IMSI is calculated by dividing Total CS Demand mErlang All √ √ √ √
IMSI by the number of unique IMSIs and then multiplying the quotient
by 1000.
Minutes of
Use (MOU)
CS MOU Total minutes of CS RAB use m All √ √ √ √ √
PS MOU Total minutes of PS RAB use m All √ √ √ √ √
PS
Throughput
User
Throughput
Mean UL User [Ericsson] Mean uplink user throughput kbps Ericsson √ √ √ √ √
Throughput
Mean DL User [Ericsson] Mean downlink user throughput kbps Ericsson √ √ √ √ √
Throughput

992-0608-08 Rev. 001
Map KPI Top Top Top

MAC-d PDU
PS Overall
MAC-d PDU PS [Nokia] Mean throughput of all uplink PS traffic calculated at the kbps Nokia √ √ √ √ √
Mean Data Rate MAC-d sublayer by dividing the sum of all uplink streaming,
UL interactive and background PDU data amounts by the sum of the
collection period durations.
MAC-d PDU PS [Nokia] Mean throughput of all downlink PS traffic calculated at kbps Nokia √ √ √ √ √
Mean Data Rate the MAC-d sublayer by dividing the sum of all downlink
DL streaming, interactive and background PDU data amounts by the
sum of the collection period durations.
MAC-d PDU
Peak By
Category
MAC-d PDU [Nokia] Peak throughput of uplink PS streaming traffic calculated kbps Nokia √ √ √ √ √
Streaming Max at the MAC-d sublayer by taking the maximum rate of the ratios
Data Rate UL of the uplink PS streaming data amount for each period by the
duration of the counting period (no greater than 20 seconds).
MAC-d PDU [Nokia] Peak throughput of downlink PS streaming traffic kbps Nokia √ √ √ √ √
Streaming Max calculated at the MAC-d sublayer by taking the maximum rate of
Data Rate DL the ratios of the downlink PS streaming data amount for each
period by the duration of the counting period (no greater than 20
seconds).
MAC-d PDU [Nokia] Peak throughput of uplink PS interactive traffic kbps Nokia √ √ √ √ √
Interactive Max calculated at the MAC-d sublayer by taking the maximum rate of
Data Rate UL the ratios of the uplink PS interactive data amount for each
seconds).

992-0608-08 Rev. 001
Map KPI Top Top Top

MAC-d PDU [Nokia] Peak throughput of downlink PS interactive traffic kbps Nokia √ √ √ √ √
Interactive Max calculated at the MAC-d sublayer by taking the maximum rate of
Data Rate DL the ratios of the downlink PS interactive data amount for each
seconds).
MAC-d PDU [Nokia] Peak throughput of uplink PS background traffic kbps Nokia √ √ √ √ √
Background calculated at the MAC-d sublayer by taking the maximum rate of
Max Data Rate the ratios of the uplink PS background data amount for each
UL period by the duration of the counting period (no greater than 20
seconds).
MAC-d PDU [Nokia] Peak throughput of downlink PS background traffic kbps Nokia √ √ √ √ √
Background calculated at the MAC-d sublayer by taking the maximum rate of
Max Data Rate the ratios of the downlink PS background data amount for each
DL period by the duration of the counting period (no greater than 20
seconds).
MAC-d PDU
Mean By
Category
MAC-d PDU [Nokia] Mean throughput of uplink PS streaming traffic kbps Nokia √ √ √ √ √
Streaming calculated at the MAC-d sublayer by dividing the sum of uplink
Mean Data Rate streaming PDU data amounts by the sum of the collection period
UL durations containing streaming data.
MAC-d PDU [Nokia] Mean throughput of downlink PS streaming traffic kbps Nokia √ √ √ √ √
Streaming calculated at the MAC-d sublayer by dividing the sum of uplink
DL durations containing streaming data.

992-0608-08 Rev. 001
Map KPI Top Top Top

MAC-d PDU [Nokia] Mean throughput of uplink PS interactive traffic kbps Nokia √ √ √ √ √
Interactive calculated at the MAC-d sublayer by dividing the sum of uplink
UL durations containing interactive data.
MAC-d PDU [Nokia] Mean throughput of downlink PS interactive traffic kbps Nokia √ √ √ √ √
Interactive calculated at the MAC-d sublayer by dividing the sum of uplink
DL durations containing interactive data.
MAC-d PDU [Nokia] Mean throughput of uplink PS background traffic kbps Nokia √ √ √ √ √
Background calculated at the MAC-d sublayer by dividing the sum of uplink
UL durations containing background data.
MAC-d PDU [Nokia] Mean throughput of downlink PS background traffic kbps Nokia √ √ √ √ √
Background calculated at the MAC-d sublayer by dividing the sum of uplink
DL durations containing background data.
PS Data
Volume
MAC-d PDU
PS Overall
MAC-d PDU PS [Nokia] Total uplink data volume of PS streaming data, PS kbytes Nokia √ √ √ √ √
Volume UL interactive data, and PS background data RABs calculated at the
MAC-d sublayer on the basis of Megamon Throughput Ticket
messages.

992-0608-08 Rev. 001
Map KPI Top Top Top

MAC-d PDU PS [Nokia] Total downlink data volume of PS streaming data, PS kbytes Nokia √ √ √ √ √
Volume DL interactive data, and PS background data RABs calculated at the
MAC-d sublayer on the basis of Megamon Throughput Ticket
messages.
MAC-d PDU
By Category
MAC-d PDU [Nokia] Total uplink data volume of PS streaming data RABs kbytes Nokia √ √ √ √ √
Streaming calculated at the MAC-d sublayer on the basis of Megamon
Volume UL Throughput Ticket messages.
MAC-d PDU [Nokia] Total downlink data volume of PS streaming data RABs kbytes Nokia √ √ √ √ √
Streaming calculated at the MAC-d sublayer on the basis of Megamon
Volume DL Throughput Ticket messages.
MAC-d PDU [Nokia] Total uplink data volume of PS interactive data RABs kbytes Nokia √ √ √ √ √
Interactive calculated at the MAC-d sublayer on the basis of Megamon
MAC-d PDU [Nokia] Total downlink data volume of PS interactive data RABs kbytes Nokia √ √ √ √ √
Interactive calculated at the MAC-d sublayer on the basis of Megamon
MAC-d PDU [Nokia] Total uplink data volume of PS background Data RABs kbytes Nokia √ √ √ √ √
Background calculated at the MAC-d sublayer on the basis of Megamon
MAC-d PDU [Nokia] Total downlink data volume of PS background data RABs kbytes Nokia √ √ √ √ √
Background calculated at the MAC-d sublayer on the basis of Megamon
Mobility

992-0608-08 Rev. 001
Map KPI Top Top Top

Soft
Handover
Radio Link
Additions to
Active Set
SHO RL Active This KPI is an implementation of the Attempted Radio Link # All √ √ √ √ √
Set Addition Additions to Active Link Set (UE side) KPI described in TS 32.405.
Attempts This count includes all soft handover radio link addition attempts,
including softer handover radio link addition attempts, which are
a special case of soft handover where two cells of the active set
are served from the same Node B.
SHO RL Active This KPI is an implementation of the Failed Radio Link Additions to # All √ √ √ √ √
Set Addition Active Link Set (UE side) KPI described in TS 32.405. This count
Failures includes all soft handover radio link addition failures, including
softer handover radio link addition failures, which are a special
case where two cells of the active set are served from the same
Node B.
SHO RL Active Calculated by dividing SHO RL Active Set Addition Failures by % All √ √ √ √ √
Set Addition SHO RL Active Set Addition Attempts. This count includes all soft
Failure Rate handover radio link addition failures and attempts, including
softer handover radio link additions and attempts, which are a
special case of soft handover radio link addition failures and
attempts where two cells of the active set are served from the
same Node B.
Radio Link
Deletions from
Active Set

992-0608-08 Rev. 001
Map KPI Top Top Top

SHO RL Active This KPI is an implementation of the Attempted radio link # All √ √ √ √ √
Set Deletion deletions from Active Link Set (UE side) KPI described in TS
Attempts 32.405. This count includes all soft handover radio link deletion
attempts, including softer handover radio link deletion attempts,
which are a special case of soft handover where two cells of the
active set are served from the same Node B.
SHO RL Active This KPI is an implementation of the Failed Radio Link Deletions # All √ √ √ √ √
Set Deletion to Active Link Set (UE side) KPI described in TS 32.405. This count
Failures includes all soft handover radio link deletion failures, including
softer handover radio link deletion failures, which are a special
case of soft handover where two cells of the active set are
served from the same Node B.
SHO RL Active Calculated by dividing SHO RL Active Set Deletion Failures by % All √ √ √ √ √
Set Deletion SHO RL Active Set Deletion Attempts. This count includes all soft
Failure Rate handover radio link deletion failures and attempts, including
softer handover radio link deletion failures and attempts, which
are a special case of soft handover where two cells of the active
set are served from the same Node B.
IRAT
Handovers
IRAT Handover Number of IRAT outgoing handover attempts indicated by the # All √ √ √ √ √
Out Attempts number of Handover From UTRAN Attempted messages sent
IRAT Handover Number of IRAT outgoing handover attempts for which a RANAP # All √ √ √ √ √
Out Failures Iu Release Command indicating successful outgoing relocation is
absent
IRAT Handover Calculated by dividing IRAT Handover Out Failures by IRAT % All √ √ √ √ √
Out Failure Rate Handover Out Attempts.

992-0608-08 Rev. 001
Map KPI Top Top Top

to GSM
Relocation to Number of IRAT outgoing handover attempts to GSM indicated # All √ √ √ √ √
GSM Attempts by the number of Handover From UTRAN Attempted messages
indicating either the GSM or GERAN-Iu target technology.
Relocation to Number of IRAT outgoing handover attempts to GSM for which a # All √ √ √ √ √
GSM Failures RANAP Iu Release Command indicating successful outgoing
relocation is absent.
Relocation to Calculated by dividing Relocation to GSM Failures by Relocation % All √ √ √ √ √
GSM Failure to GSM Attempts.
Rate
to E-UTRA
Relocation to E- Number of IRAT outgoing handover attempts to E-UTRA indicated # All √ √ √ √ √
UTRA Attempts by the number of Handover From UTRAN Attempted messages
indicating E-UTRA as the target technology
Relocation to E- Number of IRAT outgoing handover attempts to E-UTRA for which # All √ √ √ √ √
UTRA Failures a RANAP Iu Release Command indicating successful outgoing
relocation is absent
Relocation to E- Calculated by dividing Relocation to E-UTRA Failures by % All √ √ √ √ √
UTRA Failure Relocation to E-UTRA Attempts.
Rate
IFHO
IFHO Attempts [Ericsson] Number of inter-frequency handover attempts # ERC √ √ √ √ √
IFHO Failures [Ericsson] Number of inter-frequency handover failures # ERC √ √ √ √ √
IFHO Failure [Ericsson] Inter-frequency handover failure rate % ERC √ √ √ √ √
Rate

992-0608-08 Rev. 001
Map KPI Top Top Top

SRNS
Context
Transfers
Cell Change
Orders
CCO Attempts Calculated from the number of RRC Cell Change Order From # All √ √ √ √ √
UTRAN messages sent from source the RNC to the UE
CCO Failures Calculated from the number of RRC Cell Change Order From # All √ √ √ √ √
UTRAN procedures executed for which a RRC Cell Change Order
From UTRAN Failure message is not received and for which an Iu
Release Command indicating a successful change order is not
received.
CCO Failure Calculated by dividing CCO Failures by CCO Attempts. % All √ √ √ √ √
Rate
UE Controlled Calculated from the number of RANAP SRNS Context Request # All √ √ √ √ √
SRNS Context message unrelated to RRC Cell Change Order procedures that
Transfers are received. This count includes successful outgoing packet
switched inter-RAT handovers, UE controlled, as defined in TS
32.405 as well as UE controlled intra-RAT SRNS (Serving Radio
Network System) Context Transfers that occur as a result of cell
selection by the UE to different SRNS followed by Routing Area
Update.
Outgoing
Relocation

992-0608-08 Rev. 001
Map KPI Top Top Top

Relocation Out Number of Number of RANAP Relocation Preparation procedures # All √ √ √ √ √
Attempts attempted determined as the total of all Relocation Required
messages, Relocation Command messages without
corresponding Relocation Required message, and Iu Release
Command message for which neither corresponding Relocation
Required nor corresponding Relocation Required event have
been received.
Relocation Out Number of RANAP Relocation Preparations for which the RANAP # All √ √ √ √ √
Preparation Relocation Command is not received.
Failures
Relocation Out Calculated by dividing Relocation Out Preparation Failures by % All √ √ √ √ √
Preparation Relocation Out Preparation Attempts.
Failure Rate
Relocation Out Number of RANAP Relocation procedures for which a RANAP Iu # All √ √ √ √ √
Failures Release Command indicating successful outgoing relocation has
not been received.
Relocation Out Percentage of RANAP Relocation procedures for which a RANAP % All √ √ √ √ √
Failure Rate Iu Release Command indicating successful outgoing relocation
has not been received
To UTRAN
Relocation Out Only outgoing relocation procedures for which a RANAP # All √ √ √ √ √
to UTRAN Relocation Required indicating relocation to UTRAN is available
Attempts are considered in this calculation.
Preparation are considered in this calculation.
Failures

992-0608-08 Rev. 001
Map KPI Top Top Top

Relocation Out Only outgoing relocation procedures for which a RANAP % All √ √ √ √ √
Preparation are considered in this calculation.
Failure Rate
Failures are considered in this calculation.
Relocation Out Only outgoing relocation procedures for which a RANAP % All √ √ √ √ √
Failure Rate are considered in this calculation.
To GSM
Relocation Out Only outgoing relocation procedures that include a RANAP # All √ √ √ √ √
to GSM Relocation Required indicating relocation to GSM are considered
Attempts in this calculation.
Preparation in this calculation.
Failures
Relocation Out Only outgoing relocation procedures that include a RANAP % All √ √ √ √ √
Preparation in this calculation.
Failure Rate
to GSM Failures Relocation Required indicating relocation to GSM are considered
in this calculation.

992-0608-08 Rev. 001
Map KPI Top Top Top

to GSM Failure Relocation Required indicating relocation to GSM are considered
Rate in this calculation.
to E-UTRA
to E-UTRAN Relocation Required indicating relocation to E-UTRAN are
Attempts considered in this calculation.
Preparation considered in this calculation.
Failures
Preparation considered in this calculation.
Failure Rate
Failures considered in this calculation.
Failure Rate considered in this calculation.
to Unknown
RAT

992-0608-08 Rev. 001
Map KPI Top Top Top

Relocation Out Number of Number of RANAP Relocation Preparation procedures # All √
to Unknown attempted determined as the total of all Relocation Required
RAT Attempts messages, Relocation Command messages without
corresponding Relocation Required message, and Iu Release
Command message for which neither corresponding Relocation
Required nor corresponding Relocation Required event have
been received and for which the target RAT is undetermined.
Relocation Out Number of RANAP Relocation Preparations for which the RANAP # All √
to Unknown Relocation Command is not received and for which the target
RAT RAT is undetermined.
Preparation
Failures
Relocation Out Calculated by dividing Relocation Out to Unknown RAT % All √
to Unknown Preparation Failures by Relocation Out to Unknown RAT
RAT Attempts.
Preparation
Failure Rate
Relocation Out Number of RANAP Relocation procedures for which the target # All √
to Unknown RAT is undetermined for which a RANAP Iu Release Command
RAT Failures indicating successful outgoing relocation has not been received.
Relocation Out Percentage of RANAP Relocation procedures for which the % All √
to Unknown target RAT is undetermined for which a RANAP Iu Release
RAT Failure Command indicating successful outgoing relocation has not been
Rate received.
Relocation In
Overall
Attempts

992-0608-08 Rev. 001
Map KPI Top Top Top

Relocation In This KPI includes all combinations of CS and PS domain and UE # All √ √ √ √ √
Attempts involved as well as UE not involved incoming relocations as
described in TS 32.405. Individual KPI counts as described in TS
32.405 can be derived by applying the appropriate Relocation In
Type and Relocation In Domain filters.
Relocation In Calculated by taking the sum of Relocation In Preparation # All √ √ √ √ √
Failures Failures and Relocation In Execution Failures.
Relocation In Calculated by dividing Relocation In Failures by Relocation In % All √ √ √ √ √
Failure Rate Attempts
Resource
Allocations
Reloc in Number of incoming relocation attempts that fail to return the # All √ √ √ √ √
Resource RANAP Relocation Request Acknowledge message
Allocation
Failures
Reloc in Calculated by dividing Relocation in Resource Allocation Failures % All √ √ √ √ √
Resource by Relocation In Attempts.
Allocation
Failure Rate
Relocation
In Executions
Reloc in Failure to relocate to the target RNC is determined by the # All √ √ √ √ √
Execution absence of all of the following events: RRC Cell Update Confirm,
Failures RRC URA Update Confirm, uplink DCCH RRC message, RRC
Handover to UTRAN Complete and RANAP Relocation Detect.

992-0608-08 Rev. 001
Map KPI Top Top Top

Reloc in Calculated by dividing Relocation in Execution Failures by the % All √ √ √ √ √
Execution number of successful Relocation Resource Allocation
Failure Rate procedures.
Relocations
In from 2G
with PDP
Relocations In Number of RANAP Relocation Requests with RAB Setup Item # All √ √ √ √ √
from 2G with indicating a PS RAB and which are incoming IRAT handovers from
PDP Attempts GSM or CDMA2000 radio access technologies.
Relocations In Number of Relocations In Attempts from 2G with PDP that fail to # All √ √ √ √ √
from 2G with receive the RRC Handover to UTRAN Command message.
PDP Failures
Relocations In Calculated by dividing Relocations In Fails from 2G with PDP by % All √ √ √ √ √
from 2G with Relocations In Attempts from 2G with PDP.
PDP Failure
Rate
IRAT
Relocations In
IRAT Relocation Number of incoming IRAT relocation attempts for which the # All √ √ √ √ √
In Attempts RANAP Relocation Request message indicates an IRAT handover
in the To Target RNC Container IE.
IRAT Relocation Number of incoming IRAT relocation attempts for which the # All √ √ √ √ √
In Failures Handover to UTRAN Complete is not received
IRAT Relocation Calculated by dividing IRAT Relocation In Failures by IRAT % All √ √ √ √ √
In Failure Rate Relocation In Attempts.

992-0608-08 Rev. 001
Map KPI Top Top Top

Radio
Environment
Statistics
Mean Ec/Io at Arithmetic mean of the Ec/Io from the Measured Results on dB All √ √ √ √ √
Access RACH of the initial RRC Connection Request or Cell Update
message used to access the UTRAN.
Mean RSCP In the case of Top NE, the power mean of RSCP for the NE dBm All √ √ √ √ √
contained in the last measurement report reported for each
connection is calculated.
Median RSCP In the case of Top NE, the median RSCP for the NE contained in dBm All √ √ √ √ √
the last measurement report reported for each connection is
calculated.
Mean Ec/Io In the case of Top NE, the arithmetic mean Ec/Io for the NE dB All √ √ √ √ √
contained in the last measurement report reported for each
connection is calculated.
Median Ec/Io In the case of Top NE, the median Ec/Io for the NE contained in dB All √ √ √ √ √
the last measurement report reported for each connection is
calculated.
Mean UE TX Mean of the last UE transmitted power of each call. The last UE dBm All √ √ √ √ √
Power transmitted power of a call is derived by taking the value of the
last ue-TransmittedPowerFDD received in a Measurement
Report message and converting to dBm using the formula dbm =
(ue-TransmittedPowerFDD -71 + 0.5).

992-0608-08 Rev. 001
Map KPI Top Top Top

Pilot Polluters Mean pilot polluters based on the last RSCP measurement of the # All √ √
calls. The number of pilot polluters for a call is calculated from
the number of cells in the last intra-frequency or RACH
measurement report with RSCP within the pilot pollution
threshold of the best RSCP measurement. The best RSCP
measurement server is excluded from the count of pilot
polluters. The pilot pollution threshold is configured by TrueCall
ETL server command line argument and can be set between 0.1
dBm and 10.0 dBm in 0.1 dBm increments with a default value of
5.0 dBm.
Mean In the case of Top NE, the first reported propagation for the NE is meters All √ √ √ √ √
Propagation taken from each connection.
Delay
Quality
RRC
Connection
Setup
Mean RRC Mean RRC Connection Establishment time measured as the time ms All √ √ √ √ √
Setup Time difference between the reception of the RRC Connection Setup
Complete and RRC Connection Request messages
Max RRC Setup Maximum RRC Connection Establishment time measured as the ms All √ √ √ √ √
Time time difference between the reception of the RRC Connection
Setup Complete and RRC Connection Request messages
CS RAB
Setup Time
Mean CS RAB Mean CS RAB Setup Time measured between RANAP RAB ms All √ √ √ √ √
Setup Time Assignment Response and RANAP Assignment Request

992-0608-08 Rev. 001
Map KPI Top Top Top

Maximum CS Maximum RRC Connection Establishment time measured as the ms All √ √ √ √ √
RAB Setup Time time difference between the reception of the RRC Connection
Setup Complete and RRC Connection Request messages
PS RAB
Setup Time
Mean PS RAB Mean PS RAB Setup Time measured between RANAP RAB ms All √ √ √ √ √
Setup Time Assignment Response and RANAP Assignment Request
Maximum PS Maximum PS RAB Setup Time measured between RANAP RAB ms All √ √ √ √ √
RAB Setup Time Assignment Response and RANAP Assignment Request
Data Call
Setup
Mean Data Call Mean data call setup time measured as the difference between ms All √ √ √ √ √
Setup Time the first NAS Session Management Activate PDP Context Accept
and RRC Connection Request messages when the first signaling
connection established for the RRC connection is the PS signaling
connection used to transfer the first NAS Session Management
Activate PDP Context Accept.
Max Data Call Maximum data call setup time measured as the difference ms All √ √ √ √ √
Setup Time between the first NAS Session Management Activate PDP
Context Accept and RRC Connection Request messages when the
first signaling connection established for the RRC connection is
the PS signaling connection used to transfer the first NAS
Session Management Activate PDP Context Accept.

992-0608-08 Rev. 001
Map KPI Top Top Top

Mean Data Call Mean data call setup time measured as the difference measured ms √ √ √ √ √
Setup Time to as the difference between the first PS RANAP RAB Assignment
RAB Response and the RRC Connection Request messages when the
first signaling connection established for the RRC connection is
the PS signaling connection used to transfer the first PS RANAP
RAB Assignment Response.
Voice Call
Setup
Mean Voice Call Mean voice call setup time measured as the difference between ms All √ √ √ √ √
Setup Time first NAS Call Control Connect and RRC Connection Request
messages when the initial signaling connection is set up for the
CS domain and carries the first NAS Call Control Connect
message.
Max Voice Call Maximum voice call setup time measured as the difference ms All √ √ √ √ √
Setup Time between first NAS Call Control Connect and RRC Connection
Request messages when the initial signaling connection is set up
for the CS domain and carries the first NAS Call Control Connect
message.
Mean Voice Call Mean voice call setup time measured as the difference between ms All √ √ √ √ √
Setup Time to the first CS RANAP RAB Assignment Response and the RRC
RAB Connection Request messages when the initial signaling
connection is set up for the CS domain and carries the first CS
RANAP RAB Assignment Response.
CSFB Call
Setup Time

992-0608-08 Rev. 001
Map KPI Top Top Top

Mean CSFB Call Mean voice call setup time on connections with RRC Connection ms All √ √ √ √ √
Setup Time Request, CM Service Request or Location Updating messages
with CSFB indication measured as the difference between first
NAS Call Control Connect and RRC Connection Request
message.
Max CSFB Call Maximum voice call setup time on connections with RRC ms All √ √ √ √ √
Setup Time Connection Request, CM Service Request or Location Updating
message containing CSFB indication measured between first
NAS Call Control Connect and RRC Connection Request
message.
Incoming IRAT
Handover
Incoming IRAT Mean incoming IRAT HO execution time measured as the time ms All √ √ √ √ √
HO Mean Exec difference between the reception of the RRC Handover to UTRAN
Time Message and the RANAP Relocation Request messages
Incoming IRAT Maximum incoming IRAT HO execution time measured as the ms All √ √ √ √ √
HO Max Exec time difference between the reception of the RRC Handover to
Time UTRAN Message and the RANAP Relocation Request messages
Coverage
Propagation Ninety-fifth percentile distance calculated from start propagation Meters All √
Delay 95th delay. Ninety-fifth percentile distance may be expressed in or miles
Percentile either units of meters or mile in the Client.

992-0608-08 Rev. 001
Map KPI Top Top Top

Propagation Percentage of calls with start distance to intersite distance ratio % All √
Delay Bin1 greater than 0.0 but less than 0.7, where start distance is based
Percentage on the propagation delay at call start.
Delay Bin2 greater than or equal to 0.7 but less than 1.0, where start
Percentage distance is based on the propagation delay at call start.
Delay Bin3 greater than or equal to 1.0 but less than 1.5, where start
Percentage distance is based on the propagation delay at call start.
Delay Bin4 greater or equal to than 1.5, where start distance is based on the
Percentage propagation delay at call start.
Overshooting Severity of overshooting based on propagation delay at call start. 0 All √
Severity
Mean NE Mean cell intersite distance is calculated from the Network Meters All √
Intersite Element table, and may be expressed in either meters or miles. or miles
Distance
UE
Environment
Indoor RCs
Indoor RCs Number of Radio Connections with Environment set to Indoor # All √ √ √ √
Indoor Percentage of Radio Connections with Environment set to Indoor % All √ √ √ √
Mobile RCs
Mobile RCs Number of Radio Connections with Environment set to Mobile # All √ √ √ √
Mobile Percentage of Radio Connections with Environment set to Mobile % All √ √ √ √

992-0608-08 Rev. 001
Map KPI Top Top Top

Outdoor
Stationary RCs
Outdoor Number of Radio Connections with Environment set to Outdoor # All √ √ √ √
Stationary RCs Stationary
Outdoor Percentage of Radio Connections with Environment set to % All √ √ √ √
Stationary Outdoor Stationary
NAS
SM
Procedures
PDP Context
Activation
Activate PDP Number of SM Activate PDP Context Request messages. # All √ √ √ √ √
Context
Attempts
Activate PDP Number of SM Activate PDP Context Request messages for # All √ √ √ √ √
Context Failures which there is no corresponding SM Activate PDP Context Accept
message.
Activate PDP Calculated by dividing Activate PDP Context Failures by Activate % All √ √ √ √ √
Context Failure PDP Context Attempts.
Rate
Secondary
PDP Context
Activation

992-0608-08 Rev. 001
Map KPI Top Top Top

Activate Number of SM Activate Secondary PDP Context Request # All √ √ √ √ √
Secondary PDP messages.
Context
Attempts
Activate Number of SM Activate PDP Context Request messages for # All √ √ √ √ √
Secondary PDP which there is no corresponding SM Activate Secondary PDP
Context Failures Context Accept message.
Activate Calculated by dividing Activate Secondary PDP Context Failures % All √ √ √ √ √
Secondary PDP by Activate Secondary PDP Context Attempts
Context Failure
Rate
PDP Context
Modification
Network-
Initiated
Network Modify Number of SM Modify PDP Context Request messages sent in # All √ √ √ √ √
PDP Context the downlink direction.
Attempts
Network Modify Number of SM Modify PDP Context Request messages sent in # All √ √ √ √ √
PDP Context the downlink direction for which there is no corresponding uplink
Failures SM Modify PDP Context Accept message.
Network Modify Calculated by dividing Network Modify PDP Context Failures by % All √ √ √ √ √
PDP Context Network Modify PDP Context Attempts.
Failure Rate
MS-Initiated

992-0608-08 Rev. 001
Map KPI Top Top Top

MS Modify PDP Number of SM Modify PDP Context Request messages received # All √ √ √ √ √
Context in the uplink direction.
Attempts
MS Modify PDP Number of SM Modify PDP Context Request messages received # All √ √ √ √ √
Context Failures in the uplink direction for which there is no corresponding
downlink SM Modify PDP Context Accept message.
MS Modify PDP Calculated by dividing MS Modify PDP Context Failures by MS % All √ √ √ √ √
Context Failure Modify PDP Context Attempts.
Rate
SMS
MO SMS
MO SMS Number of SMS RP-DATA (ms->n). # All √ √ √ √ √
Attempts
MO SMS Number of SMS RP-DATA (ms->n) for which there is no # All √ √ √ √ √
Failures corresponding SMS RP-ACK (n->ms).
MO SMS Failure Calculated by dividing MO SMS Failures by MO SMS Attempts. % All √ √ √ √ √
Rate
MT SMS
MT SMS Number of SMS RP-DATA (n->ms). # All √ √ √ √ √
Attempts
MT SMS Number of SMS RP-DATA (n->ms) for which there is no # All √ √ √ √ √
Failures corresponding SMS RP-ACK (ms->n).
MT SMS Failure Calculated by dividing MT SMS Failures by MT SMS Attempts. % All √ √ √ √ √
Rate
MM

992-0608-08 Rev. 001
Map KPI Top Top Top

CS
Authentication
Procedures
MM Number of MM Authentication Request messages. # All √ √ √ √ √
Authentication
Attempts
MM Number of MM Authentication Request messages for which # All √ √ √ √ √
Authentication there is no corresponding MM Authentication Response
Failures message.
MM Calculated by dividing MM Authentication Failures by MM % All √ √ √ √ √
Authentication Authentication Attempts.
Failure Rate
CS Identity
Request
Procedures
MM Identity Number of MM Identity Request messages with Type of Identity # All √ √ √ √ √
Request IMSI, IMEI, IMEISV or TMSI.
Attempts
MM Identity Number of MM Identity Request messages with Type of Identity # All √ √ √ √ √
Request IMSI, IMEI, IMEISV or TMSI for which there is no corresponding
Failures MM Identity Response message.
MM Identity Calculated by dividing MM Identity Request Failures by MM % All √ √ √ √ √
Request Failure Identity Request Attempts.
Rate

992-0608-08 Rev. 001
Map KPI Top Top Top

Location
Updates with
Follow-on
Request
LAU Follow-on Number of MM Location Updating Request messages with # All √ √ √ √ √
Attempts follow-on request pending indication.
LAU Follow-on Number of MM Location Updating Request messages with # All √ √ √ √ √
Failures follow-on request pending indication for which there is no
corresponding MM Location Updating Accept message.
LAU Follow-on Calculated by dividing LAU Follow-on Failures by LAU Follow-on % All √ √ √ √ √
Failure Rate Attempts.
Location
Updates No
Follow-on
Request
LAU No Follow- Number of MM Location Updating Request messages without # All √ √ √ √ √
on Attempts follow-on request pending indication.
LAU No Follow- Number of MM Location Updating Request messages without # All √ √ √ √ √
on Failures follow-on request pending indication for which there is no
LAU No Follow- Calculated by dividing LAU No Follow-on Failures by LAU No % All √ √ √ √ √
on Failure Rate Follow-on Attempts.
IMSI Attach
with Follow-on
Request

992-0608-08 Rev. 001
Map KPI Top Top Top

IMSI Attach Number of MM Location Updating Request messages with # All √ √ √ √ √
Follow-on Location Updating Type set to IMSI Attach and with follow-on
Attempts request pending indication.
IMSI Attach Number of MM Location Updating Request messages with # All √ √ √ √ √
Follow-on Location Updating Type set to IMSI Attach and with follow-on
Failures request pending indication for which there is no corresponding
MM Location Updating Accept message.
IMSI Attach Calculated by dividing IMSI Attach Follow-on Failures by IMSI % All √ √ √ √ √
Follow-on Attach Follow-on Attempts.
Failure Rate
IMSI Attach
No Follow-on
Request
IMSI Attach No Number of MM Location Updating Request messages with # All √ √ √ √ √
Follow-on Location Updating Type set to IMSI Attach and without follow-on
Attempts request pending indication.
IMSI Attach No Number of MM Location Updating Request messages with # All √ √ √ √ √
Follow-on Location Updating Type set to IMSI Attach and without follow-on
Failures request pending indication for which there is no corresponding
MM Location Updating Accept message.
IMSI Attach No Calculated by dividing IMSI Attach No Follow-on Failures by IMSI % All √ √ √ √ √
Follow-on Attach No Follow-on Attempts.
Failure Rate
Periodic
Location
Updates

992-0608-08 Rev. 001
Map KPI Top Top Top

LAU Periodic Number of MM Location Updating Request messages with # All √ √ √ √ √
Attempts Location Updating Type set to periodic.
LAU Periodic Number of MM Location Updating Request messages with # All √ √ √ √ √
Failures Location Updating Type set to periodic for which there is no
LAU Periodic Calculated by dividing LAU Periodic Failures by LAU Periodic % All √ √ √ √ √
GMM
PS
Authentication
Procedures
GMM Number of GMM Authentication and Ciphering Request # All √ √ √ √ √
Authentication messages.
Attempts
GMM Number of GMM Authentication and Ciphering Request # All √ √ √ √ √
Authentication messages for which there is no corresponding GMM
Failures Authentication and Ciphering Response message.
GMM Calculated by dividing GMM Authentication Failures by GMM % All √ √ √ √ √
Authentication Authentication Attempts.
Failure Rate
PS Identity
Request
Procedures
GMM Identity Number of GMM Identity Request messages with Type of Identity # All √ √ √ √ √
Request set to indicate IMSI, IMEI, IMEISV or TMSI.
Attempts

992-0608-08 Rev. 001
Map KPI Top Top Top

GMM Identity Number of GMM Identity Request messages with Type of Identity # All √ √ √ √ √
Request set to indicate IMSI, IMEI, IMEISV or TMSI for which there is no
Failures corresponding GMM Identity Response message.
GMM Identity Calculated by dividing GMM Identity Request Failures by GMM % All √ √ √ √ √
Request Failure Identity Request Attempts.
Rate
GPRS Attach
with Follow-on
Request
GPRS Attach Number of GMM Attach Request messages with follow-on # All √ √ √ √ √
Follow-on request pending indication.
Attempts
GPRS Attach Number of GMM Attach Request messages with follow-on # All √ √ √ √ √
Follow-on request pending indication for which there is no corresponding
Failures GMM Attach Accept message.
GPRS Attach Calculated by dividing GPRS Attach Follow-on Failures by GPRS % All √ √ √ √ √
Follow-on Attach Follow-on Attempts.
Failure Rate
GPRS Attach
No Follow-on
Request
GPRS Attach No Number of GMM Attach Request messages with no follow-on # All √ √ √ √ √
Follow-on request pending indication.
Attempts

992-0608-08 Rev. 001
Map KPI Top Top Top

GPRS Attach No Number of GMM Attach Request messages with no follow-on # All √ √ √ √ √
Follow-on request pending indication for which there is no corresponding
Failures GMM Attach Accept message.
GPRS Attach No Calculated by dividing GPRS Attach No Follow-on Failures by % All √ √ √ √ √
Follow-on GPRS Attach No Follow-on Attempts
Failure Rate
Normal
GPRS Detach
Normal GPRS Number of uplink GMM Detach Request messages with Type of # All √ √ √ √ √
Detach Detach set to indicate normal detach.
Attempts
Normal GPRS Number of uplink GMM Detach Request messages with Type of # All √ √ √ √ √
Detach Failures Detach indicating normal detach for which there is no
corresponding downlink GMM Detach Accept message.
Normal GPRS Calculated by dividing Normal GPRS Detach Failures by Normal % All √ √ √ √ √
Detach Failure GPRS Detach Attempts
Rate
RAU with
Follow-on
Request
RAU Follow-on Number of GMM Routing Area Update Request messages with # All √ √ √ √ √
Attempts follow-on request pending indicated.
RAU Follow-on Number of GMM Routing Area Update Request messages with # All √ √ √ √ √
Failures follow-on request pending indicated for which there is no
corresponding GMM Routing Area Update Accept message.

992-0608-08 Rev. 001
Map KPI Top Top Top

RAU Follow-on Calculated by dividing RAU Follow-on Failures by RAU Follow-on % All √ √ √ √ √
RAU No
Follow-on
Request
RAU No Follow- Number of GMM Routing Area Update Request messages with # All √ √ √ √ √
on Attempts no follow-on request pending indicated.
RAU No Follow- Number of GMM Routing Area Update Request messages with # All √ √ √ √ √
on Failures no follow-on request pending indicated for which there is no
corresponding GMM Routing Area Update Accept message.
RAU No Follow- Calculated by dividing RAU No Follow-on Failures by RAU No % All √ √ √ √ √
on Failure Rate Follow-on Attempts.
RAU Periodic
RAU Periodic Number of GMM Routing Area Update Request messages with # All √ √ √ √ √
Attempts Update Type set to indicate periodic updating.
RAU Periodic Number of GMM Routing Area Update Request messages with # All √ √ √ √ √
Failures Update Type set to indicate periodic updating for which there is
no corresponding GMM Routing Area Update Accept message.
RAU Periodic Calculated by dividing RAU Periodic Failures by RAU Periodic % All √ √ √ √ √

992-0608-08 Rev. 001
A.2 Call Attribute / LSR Field: Descriptions and Units

The following Call Attributes and LSR Fields are available in Common UMTS:
Note: All fields present in the Call Table are also present in the Fragment table.
Refer to TrueCall LSR Data Types for descriptions of each available data type.
Refer to Common UMTS Enumerated Values to see the enumerated values when LSR Unit is shown as "enum."
Attribute Vendors LSR LSR LSR Range Description

Datatype Units
Vendor All string enum N/A Vendor associated with the stream used to populate the call record.
End Latitude All double degrees 90.000000..-90.000000 End latitude of call determined by Geolocation Engine
[degrees]
End Longitude All double degrees 180.000000..-180.000000 End longitude of call determined by Geolocation Engine
[degrees]
Confidence All string enum N/A TrueCall provides three different confidence levels of uncertainty. For MLE
and ARC, High confidence represents <200m, Medium confidence
represents 200m - 300m, and Low confidence represents >300m. For RSM,
High confidence represents < 0.2 ISD, Medium confidence represents 0.2 -
0.3 ISD, and Low confidence represents > 0.3 ISD. The Geolocation
Confidence is an estimation coming inherently from a probability algorithm,
and gives a quantitative quality-measure of the calculated geolocation. It is
important to note that the confidence level is not a direct accuracy
measure, and low confidence does not necessarily mean a poor accuracy.
Geolocations with a Low confidence level represents that the call provided
few predictors, resulting in a wider area of likely location. This effect is
greater in environments where there are large Inter-Site Distances. For
these types of calls, the uncertainty of the geolocation is higher, and is thus
provided to the user as being of a lower confidence level.
Environment All string enum N/A Indicates the indoor/outdoor and mobile/stationary categorization of the
call by TrueCall.

992-0608-08 Rev. 001

Datatype Units
IMSI All string no units 000000000000000..999999999999 International Mobile Subscriber Identity (IMSI) of the UE
Roaming All string no units N/A Service Provider of the UE as determined from the IMSI
Group
IMEI All string no units 00000000-000000-0..99999999- International Mobile Equipment Identity (IMEI) of the UE
999999-9
SVN All int64 no units 00..99 Software Version Number as determined from the IMEISV
Model All string no units N/A Model of the UE as determined from the TAC (Type Allocation Code) of the
IMEI.
Make All string no units N/A Make of the UE as determined from the TAC (Type Allocation Code) of the
IMEI.
P-TMSI All uint64 no units 0..4294967295 Last Packet Temporary Mobile Subscriber Identity (P-TMSI) assigned to the
UE during the connection
TMSI All uint64 no units 0..4294967295 Last Temporary Mobile Subscriber Identity (TMSI) assigned to the UE
during the connection
Start Time All time no units 1/1/1970 00:00..12/31/9999 23:59 Timestamp of the Megamon Call Start event that initiates the session
Duration All duration no units 0..99999999:59 Duration of call determined by the difference between the timestamp of
the last received event and Megamon Call Start. Note: The duration
includes time required to release the Iu interface as well as all radio links.
End Time All time no units 1/1/1970 00:00..12/31/9999 23:59 Timestamp of the last event received for the call during the session.

992-0608-08 Rev. 001

Datatype Units
Fragment All string enum N/A Fragment Trigger specifies the trigger event that closed the fragment.
Trigger 'Terminal Fragment' indicates the last fragment of the call. 'Enter cell-DCH'
indicates a fragment closed when the UE transitions to RRC state cell-DCH.
'Tracking Cell Change' indicates a fragment closed when a new cell-DCH
tracking cell is selected because the prior tracking cell has been removed
from the active set. The tracking cell is preferentially selected in the
following order from among active set cells: the last HS-DSCH serving cell,
the lastE-DCH serving cell, the cell in the active set with the best RSCP
measurement in the last RSCP measurement report, or selected from the
remaining members of the active set. 'PSC Reconfiguration' indicates a
fragment closed when a UE in cell-DCH state is reconfigured to a cell not
previously in the active set. 'PSC Reconfiguration' can be considered a
proxy for a hard handover event. 'Carrier Frequency Change' indicates a
change is the carrier frequency of the best serving cell of the connection.
'Serving Cell Change' indicates a change in the serving cell when the call is
in RRC state cell-FACH, cell-PCH or URA-PCH. Fragment Trigger is set to
fragments but not to the call table.
Trigger Count All int64 # 0..9223372036854775807 The Trigger Count indicates the number of trigger events received during
the fragment that were not acted upon because the minimum fragment
duration threshold was not met. The Trigger Count is only relevant to the
Fragment Viewer, and will be 'N/A' when no event triggers were
suppressed during the fragment.
Start Type All string enum N/A Indicates one of Connection Request, Cell Update, URA Update, IRAT
Handover, Relocation or Unknown as the call start type.
Final All string enum N/A Final Disposition of session as determined from the state machine.
Disposition

992-0608-08 Rev. 001

Datatype Units
Service Type All string enum N/A Service Type displays the traffic type as determined from RANAP RAB
establishment attempts in CS and PS domains, or if no RABs are
established, then SMS will be displayed if SMS traffic is carried over the
connection, and if neither PS nor CS RAB establishment is attempted, and
no SMS traffic is carried over the connection, then the Service Type is
displayed as 'Others.'
Data Use All duration no units 0..99999999:59 Data use is calculated by tracking the time over which at least one PS RAB
is in the Assigned state during the fragment or call.
Voice Use All duration no units 0..99999999:59 Voice use is calculated by tracking the time over which at least one CS RAB
is in the Assigned state during the fragment or call.
Start RNC ID All int64 no units 0..65535 RNC ID of the Start Cell, either the initial cell after an incoming relocation or
the cell at which RRC Connection Establishment occurs.
Start Cell All string no units 0..65535 Start Cell as determined from either the initial cell after an incoming
relocation or the cell at which RRC Connection Establishment occurs.
Start PSC All int64 no units 0..511 Primary Scrambling Code (PSC) of the Start Cell, either the initial cell after
an incoming relocation or the cell at which RRC Connection Establishment
occurs.
Start Node B All string no units N/A Name of the controlling Node B of the Start Cell, either the initial cell after
Name an incoming relocation or the cell at which RRC Connection Establishment
occurs.
Start LAC All int64 no units 0..65535 Start LAC (Location Area Code) of the call session
Start RAC All int64 no units 0..255 Start RAC (Routing Area Code) of the call session
Start SAC All int64 no units 0..65535 Start SAC (Service Area Code) of the call session

992-0608-08 Rev. 001

Datatype Units
End RNC ID All int64 no units 0..65535 RNC ID of the End Cell, either a member of the last Active Set in Cell-DCH
state, or else the last serving cell when in Cell-FACH, Cell-PCH or Cell-URA
states
End Cell All string no units 0..65535 End Cell as determined from either a member of the last Active Set in Cell-
DCH state, or else the last serving cell when in Cell-FACH, Cell-PCH or Cell-
URA states.
End PSC All int64 no units 0..511 PSC (Primary Scrambling Code) of the End Cell, either a member of the last
Active Set in Cell-DCH state, or else the last serving cell when in Cell-FACH,
Cell-PCH or Cell-URA states.
End Node B All string no units N/A Name of the controlling Node B of the End Cell, either a member of the last
Name Active Set in Cell-DCH state, or else the last serving cell when in Cell-FACH,
Cell-PCH or Cell-URA states.
Start DL All int64 no units 0..16383 Downlink UTRA Absolute Radio Frequency Channel Number (UARFCN) of
UARFCN the Start Cell.
End DL All int64 no units 0..16383 Downlink UTRA Absolute Radio Frequency Channel Number (UARFCN) of
UARFCN the End Cell.
RRC Setup All string enum N/A Shows RRC Connection Establishment procedure result when the
Result connection originates within the monitored Radio Network System (RNS).
Setup Time All duration no units 0..99999999:59 Time that transpires from RRC Connection Request to RRC Connection
Setup Complete.
RRC Domain All string enum N/A Domain indicated in the RRC Connection Request message. Only set when
the RRC Connection Request message is received.
Establishment All string enum N/A Establishment Cause from the RRC Connection Request. Note that
Cause Establishment Cause is not provided on connections that relocate to the
controlling RNC of the session.
Cell Update All string enum N/A Cell Update Cause populated from the initial Cell Update message when
Cause Start Type is Cell Update.

992-0608-08 Rev. 001

Datatype Units
CM Service All string enum N/A Service Type of initial CM (Connection Management) Service Request. The
Type CM Service Request is a Circuit Switched (CS) domain Mobility
Management message.
GMM Service All string enum N/A Service Type of first GPRS Mobility Management Service Request received.
Type The Service Request is a Packet Switched (PS) domain GPRS Mobility
Management message.
CSFB All bool boolean True, False Set to true if the RRC Connection Request used to establish the connection
contains a CSFB indication or if a received NAS CM Service Request or
Location Updating Request contains Additional Update Parameters
indicating CSMO (Circuit Switched Mobile Originating) or CSMT (Circuit
Switched Mobile Terminating).
CSMO All bool boolean True, False Indication that the call session originates as a Circuit Switched Fall Back
Mobile Originating Call (CSMO).
Voice Call All duration no units 0..99999999:59 Difference between timestamps of NAS CC Connect and Call Start when
Setup Time the initial signaling connection is CS.
Data Call All duration no units 0..99999999:59 Difference between timestamps of SM Activate PDP Context Accept and
Setup Time Call Start when the initial signaling connection is PS
RANAP All string enum N/A RANAP Cause from last RANAP Iu Release Command message.
Release Cause
Next to Last Iu All string enum N/A RANAP Cause from next to last RANAP Iu Release Command message.
Release
Command
Cause
Iu Release All string enum N/A RANAP Cause from last RANAP Iu Release Request message.
Request
Cause

992-0608-08 Rev. 001

Datatype Units
RRC Release All string enum N/A RRC Release Cause value from the last RRC Connection Release message.
Cause
Relocation In All string enum N/A RANAP Cause indicating the reason for an incoming relocation procedure.
Cause
Relocation In All string enum N/A Indicates if the incoming relocation procedure is UE-involved or UE-not-
Type involved.
Relocation In All string enum N/A Indicates if the incoming relocation occurs over the CS or PS domain.
Domain
Relocation In All string enum N/A RANAP Failure Cause from the RANAP Relocation Failure message.
Failure Cause
Incoming IRAT All string enum N/A Source Technology of the Incoming IRAT Handover as indicated by the
HO Relocation Request.
Technology
Incoming IRAT All duration enum N/A Indicates time taken to complete an incoming IRAT handover measured as
Setup Time the difference between the timestamps of the RRC Handover To UTRAN
Complete and Call Start events.
Ec/Io at All double dB -24.25..0 Ec/Io of the serving cell contained in the initiating RRC Connection Request
Access [dB] or Cell Update Measured Results on RACH.
Last Best All double dBm -120.5..-24.5 Best RSCP (Received Signal Code Power) in last RRC intra-frequency
RSCP [dBm] measurement report of the fragment or call.
Last Best Ec/Io All double dB -24.25..0 Best Ec/Io (Signal to Interference Ratio) in last RRC intra-frequency
[dB] measurement report of the fragment or call.
Last Best All time no units 1/1/1970 00:00..12/31/9999 23:59 Timestamp of the last reported intra-frequency RSCP measurement of the
RSCP Time call or fragment.
Last Best All int64 no units 0..65535 RNC ID of the cell with the best RSCP in the last RRC intra-frequency
RSCP RNC ID measurement report containing RSCP of the call or fragment.
Last Best All int64 no units 0..65535 Cell identity of the cell with the best RSCP in the last RRC intra-frequency
RSCP Cell measurement report containing RSCP of the call or fragment.

992-0608-08 Rev. 001

Datatype Units
Last Best All int64 no units 0..511 PSC (Primary Scrambling Code) of the cell with best RSCP in the last RRC
RSCP PSC intra-frequency measurement report of the fragment or cell with RSCP.
Last Best Ec/Io All time no units 1/1/1970 00:00..12/31/9999 23:59 Timestamp of the last reported intra-frequency Ec/Io measurement of the
Time call or fragment.
Last Best Ec/Io All int64 no units 0..65535 RNC ID of the cell with best Ec/Io in the last RRC intra-frequency
RNC ID measurement report of the fragment or call containing Ec/Io.
Last Best Ec/Io All int64 no units 0..65535 Cell identity of the cell in the last RRC intra-frequency measurement report
Cell containing Ec/Io in the fragment or call.
Last Best Ec/Io All int64 no units 0..511 PSC (Primary Scrambling Code) of the cell with the best Ec/Io measurement
PSC in the last intra-frequency measurement report of the fragment or call with
Ec/Io.
Last N1 RSCP All double dBm -120.5..-24.5 Second best RSCP (Received Signal Code Power), Neighbor 1 RSCP, of the
[dBm] last RRC intra-frequency measurement report with RSCP.
Last N1 RSCP All int64 no units 0..65535 RNC ID of second best server (neighbor 1) by RSCP in last RRC intra-
RNC ID frequency measurement report with RSCP.
Last N1 RSCP All int64 no units 0..65535 Cell identity of second best server (neighbor 1) by RSCP in last RRC intra-
Cell frequency measurement report with RSCP.
Last N2 RSCP All double dBm -120.5..-24.5 Third best RSCP (Received Signal Code Power), Neighbor 2 RSCP, of the last
[dBm] RRC intra-frequency measurement report with RSCP.
Last N2 RSCP All int64 no units 0..65535 RNC ID of the server with third best RSCP in the last RRC intra-frequency
RNC ID measurement report with RSCP.
Last N2 RSCP All int64 no units 0..65535 Cell identity of the server with third best RSCP in the last RRC intra-
Cell frequency measurement report with RSCP.
Last N3 RSCP All double dBm -120.5..-24.5 Fourth best RSCP (Received Signal Code Power), Neighber 3 RSCP, of the
[dBm] last RRC intra-frequency measurement report with RSCP.
Last N3 RSCP All int64 no units 0..65535 RNC ID of the server with fourth best RSCP, Neighbor 3 RSCP, in the last
RNC ID RRC intra-frequency measurement report with RSCP.

992-0608-08 Rev. 001

Datatype Units
Last N3 RSCP All int64 no units 0..65535 Cell identity of the server with fourth best RSCP, Neighbor 3 RSCP, in the
Cell last RRC intra-frequency measurement report with RSCP.
Last N1 Ec/Io All double dB -24.25..0 Second best Ec/Io (Signal to Interference Ratio), Neighbor 1 Ec/Io, of the last
[dB] RRC intra-frequency measurement report with Ec/Io.
Last N1 Ec/Io All int64 no units 0..65535 RNC ID of server with second best Ec/Io, Neighbor 1, in last RRC intra-
RNC ID frequency measurement report with Ec/Io.
Last N1 Ec/Io All int64 no units 0..65535 Cell identity of server with second best Ec/Io, Neighbor 1, in last RRC intra-
Cell frequency measurement report with Ec/Io.
Last N2 Ec/Io All double dB -24.25..0 Third best Ec/Io (Signal to Interference Ratio), Neighbor 2 Ec/Io, of the last
Last N2 Ec/Io All int64 no units 0..65535 RNC ID of server with third best Ec/Io, Neighbor 2, in last RRC intra-
Last N2 Ec/Io All int64 no units 0..65535 Cell identity of server with third best Ec/Io, Neighbor 2, in last RRC intra-
Cell frequency measurement report with Ec/Io.
Last N3 Ec/Io All double dB -24.25..0 Fourth best Ec/Io (Signal to Interference Ratio), Neighbor 3 Ec/Io, of the last
Last N3 Ec/Io All int64 no units 0..65535 RNC ID of server with fourth best Ec/Io, Neighbor 3, in last RRC intra-
Last N3 Ec/Io All int64 no units 0..65535 Cell identity of server with fourth best Ec/Io, Neighbor 3, in the last RRC
Cell intra-frequency measurement report with Ec/Io.
Last UE Tx All double dBm -70.5..33.5 UE transmission power read from the last received ue-
Power [dBm] TransmittedPowerFDD information element and converted to dBm using
the formula dbm = (0.5 + ue-TransmittedPowerFDD -71).

992-0608-08 Rev. 001

Datatype Units
Pilot Polluters All int64 # 0..31 Pilot Polluters for a call is the number of pilot polluters for the call, which is
calculated from the number of cells in the last intra-frequency or RACH
measurement report with RSCP within the pilot pollution threshold of the
best RSCP measurement, excluding the cell of the best RSCP measurement.
The pilot pollution threshold is configured by TrueCall ETL server command
line argument and can be set between 0.1 dBm and 10.0 dBm in 0.1 dBm
increments with a default value of 5.0 dBm. Pilot Polluters for a fragment is
the number of pilot polluters for the fragment, which is calculated from the
number of cells in the last intra-frequency or RACH measurement report of
the fragment with RSCP within the pilot pollution threshold of the best RSCP
measurement, excluding the cell of the best RSCP measurement of the
fragment.
Initial All double meters 0..239382 Propagation Delay as reported in the earliest NBAP or RNSAP Radio Link
Propagation Setup Request and expressed in either meters or miles.
Delay
[Meters/Miles]
Last All double meters 0..239382 Propagation Delay as reported in the last NBAP or RNSAP Radio Link Setup
Propagation Request containing propagation delay for the fragment or call and
Delay expressed in either meters or miles.
[Meters/Miles]
Last All time no units 1/1/1970 00:00..12/31/9999 23:59 Timestamp of the last reported propagation delay for the call or fragment.
Propagation
Delay Time
Last All int64 no units 0..65535 RNC ID of the last reported propagation delay for the call or fragment.
Propagation
Delay RNC ID

992-0608-08 Rev. 001

Datatype Units
Last All int64 no units 0..65535 Cell identity of the last reported propagation delay for the call or fragment.
Propagation
Delay Cell
Attempted All int64 # 0..9223372036854775807 Number of radio link additions attempted using the RRC active set update
Radio Link procedure. This count includes all soft handover radio link addition
Additions attempts including softer handover radio link addition attempts.
Failed Radio All int64 # 0..9223372036854775807 Number of radio link addition attempts that fail determined as the
Link Additions difference between Attempted Radio Link Additions and Successful Radio
Link Additions. This count includes all soft handover radio link additions that
fail including softer handover radio link additions that fail.
Attempted All int64 # 0..9223372036854775807 Number of radio link deletions attempted using the RRC active set update
Radio Link procedure. This count includes all soft handover radio link deletion
Deletions attempts including softer handover radio link deletion attempts.
Failed Radio All int64 # 0..9223372036854775807 Number of radio link deletion attempts that fail determined as the
Link Deletions difference between Attempted Radio Link Deletions and Successful Radio
Link Deletions. This ratio considers all soft handover radio link deletion
attempts that fail including softer handover radio link deletion attempts
that fail.
CCO Target All string enum N/A Target Radio Access Technology (RAT) of the last Cell Change Order from
Technology UTRAN attempt as determined from the last "Cell Change Order From
UTRAN" message received.
CCO Target All int64 no units 0..1023 Target GSM ARFCN of the last Cell Change Order from UTRAN attempt as
ARFCN determined from the last "Cell Change Order From UTRAN" message
received.
CCO Failure All string enum N/A Inter-RAT Change Failure from the last RRC Cell Change Order From UTRAN
Cause Failure message.
Relocation All string enum N/A RANAP Cause indicating the reason for the last outgoing relocation
Outgoing procedure attempt as determined from the last RANAP "Relocation
Cause Required" message received.

992-0608-08 Rev. 001

Datatype Units
Relocation All string enum N/A RANAP Cause indicating the reason for the last outgoing relocation
Outgoing procedure failure as determined from the "Relocation Preparation Failure"
Failure Cause message.
Relocation All string enum N/A RANAP Relocation Type for the last outgoing relocation procedure attempt
Outgoing Type as determined from the "Relocation Required" message, or else when
unavailable, as can be inferred from the "Relocation Command" message.
Relocation All string enum N/A Domain of the last outgoing relocation procedure attempt as determined
Outgoing from the content of the last RANAP "Relocation Required" message.
Signalling
Domain
Relocation All string enum N/A Target technology of the last RANAP Relocation Preparation procedure is
Outgoing determined from the last received RANAP RELOCATION REQUIRED
Target message.
Technology
Outgoing All string enum N/A Target Radio Access Technology (RAT) of the last outgoing inter-RAT
Handover handover attempt as determined from the RRC "Handover From UTRAN
Target Command".
Technology
Outgoing IRAT All string enum N/A Outgoing IRAT Handover Failure Cause is populated with the cause value
Handover contained in the last Handover from UTRAN Failure message when
Failure Cause received.
Redirected All string enum N/A Redirected Radio Access Technology (RAT) as determined from the content
Technology of the last "RRC Connection Release" indicating redirection.
Redirected All int64 no units 0..262143 Redirected EARFCN, UARFCN or ARFCN determined from the content of the
ARFCN last "RRC Connection Release" indicating redirection.
IFHO Attempts Ericsson int64 # 0..9223372036854775807 [Ericsson] Sum of the INTERNAL_IFHO_EXECUTION_ACTIVE GPEH
messages received with indication of success or failure.

992-0608-08 Rev. 001

Datatype Units
IFHO Failures Ericsson int64 # 0..9223372036854775807 [Ericsson] Sum of the INTERNAL_IFHO_EXECUTION_ACTIVE GPEH
messages received with indication of failure.
Trace ID All int64 no units 0..18446744073709551615 Nokia Megamon: Call Identifier contained in the Megamon EMIL GEO
interface message header and which is unique on the serving RNC for the
duration of the RRC connection. Others, the session identifier from GeoSoft
RAN.
Mean CS RAB All duration no units 0..99999999:59 Mean CS RAB (Circuit-Switched Domain Radio Access Bearer) Setup Time
Setup Time calculated as the difference between RANAP RAB Assignment Response
and RAB Assignment Request.
Max CS RAB All duration no units 0..99999999:59 Maximum CS RAB (Circuit-Switched Domain Radio Access Bearer) Setup
Setup Time Time calculated as the difference between RANAP RAB Assignment
Response and RAB Assignment Request.
Mean PS RAB All duration no units 0..99999999:59 Mean PS RAB (Packet-Switched Domain Radio Access Bearer) Setup Time
Setup Time calculated as the difference between RANAP RAB Assignment Response
and RAB Assignment Request.
Max PS RAB All duration no units 0..99999999:59 Maximum PS RAB (Packet-Switched Domain Radio Access Bearer) Setup
Setup Time Time calculated as the difference between RANAP RAB Assignment
Response and RAB Assignment Request.
CS RAB All int64 # 0..9223372036854775807 Number of CS RAB (Circuit-Switched Domain Radio Access Bearer)
Establishment establishment attempts as indicated by the number of RABs to established
Attempts in RANAP RAB Assignment Request messages.
PS RAB All int64 # 0..9223372036854775807 Number of PS RAB (Packet-Switched Domain Radio Access Bearer)
Establishment establishment attempts as indicated by the number of RABs to established
Attempts in RANAP RAB Assignment Request messages.
CS RAB All int64 # 0..9223372036854775807 Number of RANAP RAB establishment attempts that fail in the CS domain
Establishment as indicated by the number of failed to setup RABs indicated in RANAP RAB
Failures Establishment Response messages.

992-0608-08 Rev. 001

Datatype Units
PS RAB All int64 # 0..9223372036854775807 Number of RANAP RAB establishment attempts that fail in the PS domain
Establishment as indicated by the number of failed to setup RABs indicated in RANAP RAB
Failures Establishment Response messages.
CS RABs All int64 # 0..9223372036854775807 The number of CS RAB abnormal releases is determined by aggregating CS
Dropped RABs closed with RANAP RAB or signaling connection release procedure
with RANAP Cause indicating abnormal release and CS RABs released as
result of a dropped RRC connection.
PS RABs All int64 # 0..9223372036854775807 The number of PS RAB abnormal releases is determined by aggregating PS
Dropped RABs closed with RANAP RAB or signaling connection release procedure
with RANAP Cause indicating abnormal release and PS RABs released as
result of a dropped RRC connection.
Average UL Nokia double kbps 0..147573952589676412920 [Nokia] Mean throughput of all uplink PS traffic calculated at the MAC-d
Data Rate sublayer by dividing the sum of all uplink streaming, interactive and
[kbps] background PDU data amounts by the sum of the collection period
durations.
Average DL Nokia double kbps 0..147573952589676412920 [Nokia] Mean throughput of all downlink PS traffic calculated at the MAC-d
Data Rate sublayer by dividing the sum of all downlink streaming, interactive and
[kbps] background PDU data amounts by the sum of the collection period
durations.
UL PS Nokia double kbytes 18446744073709551.615 [Nokia] Total uplink data volume of PS streaming data RABs calculated at
Streaming the MAC-d sublayer on the basis of Megamon Throughput Ticket
Data Volume messages.
[kbytes]
DL PS Nokia double kbytes 18446744073709551.615 [Nokia] Total downlink data volume of PS streaming data RABs calculated
Streaming at the MAC-d sublayer on the basis of Megamon Throughput Ticket
[kbytes]

992-0608-08 Rev. 001

Datatype Units
UL PS Nokia double kbytes 18446744073709551.615 [Nokia] Total uplink data volume of PS interactive data RABs calculated at
Interactive the MAC-d sublayer on the basis of Megamon Throughput Ticket
[kbytes]
DL PS Nokia double kbytes 18446744073709551.615 [Nokia] Total downlink data volume of PS interactive data RABs calculated
Interactive at the MAC-d sublayer on the basis of Megamon Throughput Ticket
[kbytes]
UL PS Nokia double kbytes 18446744073709551.615 [Nokia] Total uplink data volume of PS background Data RABs calculated at
Background the MAC-d sublayer on the basis of Megamon Throughput Ticket
[kbytes]
DL PS Nokia double kbytes 18446744073709551.615 [Nokia] Total downlink data volume of PS background data RABs calculated
Background at the MAC-d sublayer on the basis of Megamon Throughput Ticket
[kbytes]
Mean UL User Ericsson double kbps 0..16383 [Ericsson] Mean uplink throughput is the sum of the uplink user plane
Throughput throughput events (kbit/s) contained in the INTERNAL_PACKET_
[kbps] DEDICATED_THROUGHPUT GPEH message divided by the number of
uplink user plane throughput events. Mean uplink throughput measures
uplink RLC payloads of packet interactive radio bearers on a dedicated
connection over all RACH, DCH and E-DCH transport channels.
Mean DL User Ericsson double kbps 0..16383 [Ericsson] Mean downlink throughput is the sum of the downlink user plane
Throughput throughput events (kbit/s) contained in the INTERNAL_PACKET_
[kbps] DEDICATED_THROUGHPUT GPEH message divided by the number of
downlink user plane throughput events. Mean downlink throughput
measures downlink RLC payloads of RLC payloads of packet interactive
radio bearers on a dedicated connection over all FACH, DCH and HS-DSCH
transport channels.

992-0608-08 Rev. 001

Datatype Units
Intersite All double meters 0..239382 Intersite distance of the start cell of the connection is calculated from the
Distance Network Element table, and may be expressed in either miles or meters in
[Meters/Miles] the Call Table, but will be exported in meters in LSR output.
Range ISD All double no units 0..239382 Range as determined using the Last Propagation Delay of the call or
Ratio fragment.
Global ID All string no units 0..9223372036854775807 [LSR only] A random string generated by TrueCall which provides a global
call record identifier for the composite call record of the call or fragment.
This is expected to be unique within the domain of a given IRIS server.
Global ID is not expressed in Call Table.
Fragment ID All int64 no units 0..9223372036854775807 [LSR only] An integer identifier assigned to a fragment of a fragmented call
which is unique for a given Global ID. TrueCall associates Fragment IDs to
fragments in increasing order starting with the value '1.' Fragment ID is not
expressed in Call Table.
Composite All bool boolean True, False Indicates a composite call that consists of more than one call fragment. In
Call UMTS, fragmentation is performed by the GSR state machine.
PLMN ID All int64 no units 0..9223372036854775807 PLMN-ID of start cell
A.3 Common UMTS Enumerated Values

The following enumerated values are available for Common UMTS.
Attribute Description
Vendor Vendor associated with the stream used to populate the call record.
End Latitude End latitude of call determined by Geolocation Engine
[degrees]

992-0608-08 Rev. 001
End Longitude End longitude of call determined by Geolocation Engine
[degrees]
Confidence TrueCall provides three different confidence levels of uncertainty. For MLE and ARC, High confidence represents <200m, Medium
confidence represents 200m - 300m, and Low confidence represents >300m. For RSM, High confidence represents < 0.2 ISD,
Medium confidence represents 0.2 - 0.3 ISD, and Low confidence represents > 0.3 ISD. The Geolocation Confidence is an
estimation coming inherently from a probability algorithm, and gives a quantitative quality-measure of the calculated geolocation.
It is important to note that the confidence level is not a direct accuracy measure, and low confidence does not necessarily mean a
poor accuracy. Geolocations with a Low confidence level represents that the call provided few predictors, resulting in a wider area
of likely location. This effect is greater in environments where there are large Inter-Site Distances. For these types of calls, the
uncertainty of the geolocation is higher, and is thus provided to the user as being of a lower confidence level.
Environment Indicates the indoor/outdoor and mobile/stationary categorization of the call by TrueCall.
IMSI International Mobile Subscriber Identity (IMSI) of the UE
Roaming Service Provider of the UE as determined from the IMSI
Group
IMEI International Mobile Equipment Identity (IMEI) of the UE
SVN Software Version Number as determined from the IMEISV
Model Model of the UE as determined from the TAC (Type Allocation Code) of the IMEI.
Make Make of the UE as determined from the TAC (Type Allocation Code) of the IMEI.
P-TMSI Last Packet Temporary Mobile Subscriber Identity (P-TMSI) assigned to the UE during the connection
TMSI Last Temporary Mobile Subscriber Identity (TMSI) assigned to the UE during the connection
Start Time Timestamp of the Megamon Call Start event that initiates the session
Duration Duration of call determined by the difference between the timestamp of the last received event and Megamon Call Start. Note: The
duration includes time required to release the Iu interface as well as all radio links.
End Time Timestamp of the last event received for the call during the session.

992-0608-08 Rev. 001
Fragment Fragment Trigger specifies the trigger event that closed the fragment. 'Terminal Fragment' indicates the last fragment of the call.
Trigger 'Enter cell-DCH' indicates a fragment closed when the UE transitions to RRC state cell-DCH. 'Tracking Cell Change' indicates a
fragment closed when a new cell-DCH tracking cell is selected because the prior tracking cell has been removed from the active
set. The tracking cell is preferentially selected in the following order from among active set cells: the last HS-DSCH serving cell, the
lastE-DCH serving cell, the cell in the active set with the best RSCP measurement in the last RSCP measurement report, or selected
from the remaining members of the active set. 'PSC Reconfiguration' indicates a fragment closed when a UE in cell-DCH state is
reconfigured to a cell not previously in the active set. 'PSC Reconfiguration' can be considered a proxy for a hard handover event.
'Carrier Frequency Change' indicates a change is the carrier frequency of the best serving cell of the connection. 'Serving Cell
Change' indicates a change in the serving cell when the call is in RRC state cell-FACH, cell-PCH or URA-PCH. Fragment Trigger is set
to fragments but not to the call table.
Trigger Count The Trigger Count indicates the number of trigger events received during the fragment that were not acted upon because the
minimum fragment duration threshold was not met. The Trigger Count is only relevant to the Fragment Viewer, and will be 'N/A'
when no event triggers were suppressed during the fragment.
Start Type Indicates one of Connection Request, Cell Update, URA Update, IRAT Handover, Relocation or Unknown as the call start type.
Final Final Disposition of session as determined from the state machine.
Disposition
Service Type Service Type displays the traffic type as determined from RANAP RAB establishment attempts in CS and PS domains, or if no RABs
are established, then SMS will be displayed if SMS traffic is carried over the connection, and if neither PS nor CS RAB establishment
is attempted, and no SMS traffic is carried over the connection, then the Service Type is displayed as 'Others.'
Data Use Data use is calculated by tracking the time over which at least one PS RAB is in the Assigned state during the fragment or call.
Voice Use Voice use is calculated by tracking the time over which at least one CS RAB is in the Assigned state during the fragment or call.
Start RNC ID RNC ID of the Start Cell, either the initial cell after an incoming relocation or the cell at which RRC Connection Establishment occurs.
Start Cell Start Cell as determined from either the initial cell after an incoming relocation or the cell at which RRC Connection Establishment
occurs.
Start PSC Primary Scrambling Code (PSC) of the Start Cell, either the initial cell after an incoming relocation or the cell at which RRC
Connection Establishment occurs.
Start Node B Name of the controlling Node B of the Start Cell, either the initial cell after an incoming relocation or the cell at which RRC
Name Connection Establishment occurs.

992-0608-08 Rev. 001
Start LAC Start LAC (Location Area Code) of the call session
Start RAC Start RAC (Routing Area Code) of the call session
Start SAC Start SAC (Service Area Code) of the call session
End RNC ID RNC ID of the End Cell, either a member of the last Active Set in Cell-DCH state, or else the last serving cell when in Cell-FACH, Cell-
PCH or Cell-URA states
End Cell End Cell as determined from either a member of the last Active Set in Cell-DCH state, or else the last serving cell when in Cell-
FACH, Cell-PCH or Cell-URA states.
End PSC PSC (Primary Scrambling Code) of the End Cell, either a member of the last Active Set in Cell-DCH state, or else the last serving cell
when in Cell-FACH, Cell-PCH or Cell-URA states.
End Node B Name of the controlling Node B of the End Cell, either a member of the last Active Set in Cell-DCH state, or else the last serving cell
Name when in Cell-FACH, Cell-PCH or Cell-URA states.
Start DL Downlink UTRA Absolute Radio Frequency Channel Number (UARFCN) of the Start Cell.
UARFCN
End DL Downlink UTRA Absolute Radio Frequency Channel Number (UARFCN) of the End Cell.
UARFCN
RRC Setup Shows RRC Connection Establishment procedure result when the connection originates within the monitored Radio Network System
Result (RNS).
Setup Time Time that transpires from RRC Connection Request to RRC Connection Setup Complete.
RRC Domain Domain indicated in the RRC Connection Request message. Only set when the RRC Connection Request message is received.
Establishment Establishment Cause from the RRC Connection Request. Note that Establishment Cause is not provided on connections that
Cause relocate to the controlling RNC of the session.
Cell Update Cell Update Cause populated from the initial Cell Update message when Start Type is Cell Update.
Cause
CM Service Service Type of initial CM (Connection Management) Service Request. The CM Service Request is a Circuit Switched (CS) domain
Type Mobility Management message.
GMM Service Service Type of first GPRS Mobility Management Service Request received. The Service Request is a Packet Switched (PS) domain
Type GPRS Mobility Management message.

992-0608-08 Rev. 001
CSFB Set to true if the RRC Connection Request used to establish the connection contains a CSFB indication or if a received NAS CM
Service Request or Location Updating Request contains Additional Update Parameters indicating CSMO (Circuit Switched Mobile
Originating) or CSMT (Circuit Switched Mobile Terminating).
CSMO Indication that the call session originates as a Circuit Switched Fall Back Mobile Originating Call (CSMO).
Voice Call Difference between timestamps of NAS CC Connect and Call Start when the initial signaling connection is CS.
Setup Time
Data Call Difference between timestamps of SM Activate PDP Context Accept and Call Start when the initial signaling connection is PS
Setup Time
RANAP RANAP Cause from last RANAP Iu Release Command message.
Release Cause
Next to Last Iu RANAP Cause from next to last RANAP Iu Release Command message.
Release
Command
Cause
Iu Release RANAP Cause from last RANAP Iu Release Request message.
Request
Cause
RRC Release RRC Release Cause value from the last RRC Connection Release message.
Cause
Relocation In RANAP Cause indicating the reason for an incoming relocation procedure.
Cause
Relocation In Indicates if the incoming relocation procedure is UE-involved or UE-not-involved.
Type
Relocation In Indicates if the incoming relocation occurs over the CS or PS domain.
Domain
Relocation In RANAP Failure Cause from the RANAP Relocation Failure message.
Failure Cause

992-0608-08 Rev. 001
Incoming IRAT Source Technology of the Incoming IRAT Handover as indicated by the Relocation Request.
HO
Technology
Incoming IRAT Indicates time taken to complete an incoming IRAT handover measured as the difference between the timestamps of the RRC
Setup Time Handover To UTRAN Complete and Call Start events.
Ec/Io at Ec/Io of the serving cell contained in the initiating RRC Connection Request or Cell Update Measured Results on RACH.
Access [dB]
Last Best Best RSCP (Received Signal Code Power) in last RRC intra-frequency measurement report of the fragment or call.
RSCP [dBm]
Last Best Ec/Io Best Ec/Io (Signal to Interference Ratio) in last RRC intra-frequency measurement report of the fragment or call.
[dB]
Last Best Timestamp of the last reported intra-frequency RSCP measurement of the call or fragment.
RSCP Time
Last Best RNC ID of the cell with the best RSCP in the last RRC intra-frequency measurement report containing RSCP of the call or fragment.
RSCP RNC ID
Last Best Cell identity of the cell with the best RSCP in the last RRC intra-frequency measurement report containing RSCP of the call or
RSCP Cell fragment.
Last Best PSC (Primary Scrambling Code) of the cell with best RSCP in the last RRC intra-frequency measurement report of the fragment or
RSCP PSC cell with RSCP.
Last Best Ec/Io Timestamp of the last reported intra-frequency Ec/Io measurement of the call or fragment.
Time
Last Best Ec/Io RNC ID of the cell with best Ec/Io in the last RRC intra-frequency measurement report of the fragment or call containing Ec/Io.
RNC ID
Last Best Ec/Io Cell identity of the cell in the last RRC intra-frequency measurement report containing Ec/Io in the fragment or call.
Cell
Last Best Ec/Io PSC (Primary Scrambling Code) of the cell with the best Ec/Io measurement in the last intra-frequency measurement report of the
PSC fragment or call with Ec/Io.

992-0608-08 Rev. 001
Last N1 RSCP Second best RSCP (Received Signal Code Power), Neighbor 1 RSCP, of the last RRC intra-frequency measurement report with RSCP.
[dBm]
Last N1 RSCP RNC ID of second best server (neighbor 1) by RSCP in last RRC intra-frequency measurement report with RSCP.
RNC ID
Last N1 RSCP Cell identity of second best server (neighbor 1) by RSCP in last RRC intra-frequency measurement report with RSCP.
Cell
Last N2 RSCP Third best RSCP (Received Signal Code Power), Neighbor 2 RSCP, of the last RRC intra-frequency measurement report with RSCP.
[dBm]
Last N2 RSCP RNC ID of the server with third best RSCP in the last RRC intra-frequency measurement report with RSCP.
RNC ID
Last N2 RSCP Cell identity of the server with third best RSCP in the last RRC intra-frequency measurement report with RSCP.
Cell
Last N3 RSCP Fourth best RSCP (Received Signal Code Power), Neighber 3 RSCP, of the last RRC intra-frequency measurement report with RSCP.
[dBm]
Last N3 RSCP RNC ID of the server with fourth best RSCP, Neighbor 3 RSCP, in the last RRC intra-frequency measurement report with RSCP.
RNC ID
Last N3 RSCP Cell identity of the server with fourth best RSCP, Neighbor 3 RSCP, in the last RRC intra-frequency measurement report with RSCP.
Cell
Last N1 Ec/Io Second best Ec/Io (Signal to Interference Ratio), Neighbor 1 Ec/Io, of the last RRC intra-frequency measurement report with Ec/Io.
[dB]
Last N1 Ec/Io RNC ID of server with second best Ec/Io, Neighbor 1, in last RRC intra-frequency measurement report with Ec/Io.
RNC ID
Last N1 Ec/Io Cell identity of server with second best Ec/Io, Neighbor 1, in last RRC intra-frequency measurement report with Ec/Io.
Cell
Last N2 Ec/Io Third best Ec/Io (Signal to Interference Ratio), Neighbor 2 Ec/Io, of the last RRC intra-frequency measurement report with Ec/Io.
[dB]
Last N2 Ec/Io RNC ID of server with third best Ec/Io, Neighbor 2, in last RRC intra-frequency measurement report with Ec/Io.
RNC ID

992-0608-08 Rev. 001
Last N2 Ec/Io Cell identity of server with third best Ec/Io, Neighbor 2, in last RRC intra-frequency measurement report with Ec/Io.
Cell
Last N3 Ec/Io Fourth best Ec/Io (Signal to Interference Ratio), Neighbor 3 Ec/Io, of the last RRC intra-frequency measurement report with Ec/Io.
[dB]
Last N3 Ec/Io RNC ID of server with fourth best Ec/Io, Neighbor 3, in last RRC intra-frequency measurement report with Ec/Io.
RNC ID
Last N3 Ec/Io Cell identity of server with fourth best Ec/Io, Neighbor 3, in the last RRC intra-frequency measurement report with Ec/Io.
Cell
Last UE Tx UE transmission power read from the last received ue-TransmittedPowerFDD information element and converted to dBm using the
Power [dBm] formula dbm = (0.5 + ue-TransmittedPowerFDD -71).
Pilot Polluters Pilot Polluters for a call is the number of pilot polluters for the call, which is calculated from the number of cells in the last intra-
frequency or RACH measurement report with RSCP within the pilot pollution threshold of the best RSCP measurement, excluding
the cell of the best RSCP measurement. The pilot pollution threshold is configured by TrueCall ETL server command line argument
and can be set between 0.1 dBm and 10.0 dBm in 0.1 dBm increments with a default value of 5.0 dBm. Pilot Polluters for a
fragment is the number of pilot polluters for the fragment, which is calculated from the number of cells in the last intra-frequency
or RACH measurement report of the fragment with RSCP within the pilot pollution threshold of the best RSCP measurement,
excluding the cell of the best RSCP measurement of the fragment.
Initial Propagation Delay as reported in the earliest NBAP or RNSAP Radio Link Setup Request and expressed in either meters or miles.
Propagation
Delay
[Meters/Miles]
Last Propagation Delay as reported in the last NBAP or RNSAP Radio Link Setup Request containing propagation delay for the fragment
Propagation or call and expressed in either meters or miles.
Delay
[Meters/Miles]

992-0608-08 Rev. 001
Last Timestamp of the last reported propagation delay for the call or fragment.
Propagation
Delay Time
Last RNC ID of the last reported propagation delay for the call or fragment.
Propagation
Delay RNC ID
Last Cell identity of the last reported propagation delay for the call or fragment.
Propagation
Delay Cell
Attempted Number of radio link additions attempted using the RRC active set update procedure. This count includes all soft handover radio
Radio Link link addition attempts including softer handover radio link addition attempts.
Additions
Failed Radio Number of radio link addition attempts that fail determined as the difference between Attempted Radio Link Additions and
Link Additions Successful Radio Link Additions. This count includes all soft handover radio link additions that fail including softer handover radio
link additions that fail.
Attempted Number of radio link deletions attempted using the RRC active set update procedure. This count includes all soft handover radio
Radio Link link deletion attempts including softer handover radio link deletion attempts.
Deletions
Failed Radio Number of radio link deletion attempts that fail determined as the difference between Attempted Radio Link Deletions and
Link Deletions Successful Radio Link Deletions. This ratio considers all soft handover radio link deletion attempts that fail including softer
handover radio link deletion attempts that fail.
CCO Target Target Radio Access Technology (RAT) of the last Cell Change Order from UTRAN attempt as determined from the last "Cell
Technology Change Order From UTRAN" message received.
CCO Target Target GSM ARFCN of the last Cell Change Order from UTRAN attempt as determined from the last "Cell Change Order From
ARFCN UTRAN" message received.
CCO Failure Inter-RAT Change Failure from the last RRC Cell Change Order From UTRAN Failure message.
Cause

992-0608-08 Rev. 001
Relocation RANAP Cause indicating the reason for the last outgoing relocation procedure attempt as determined from the last RANAP
Outgoing "Relocation Required" message received.
Cause
Relocation RANAP Cause indicating the reason for the last outgoing relocation procedure failure as determined from the "Relocation
Outgoing Preparation Failure" message.
Failure Cause
Relocation RANAP Relocation Type for the last outgoing relocation procedure attempt as determined from the "Relocation Required" message,
Outgoing Type or else when unavailable, as can be inferred from the "Relocation Command" message.
Relocation Domain of the last outgoing relocation procedure attempt as determined from the content of the last RANAP "Relocation Required"
Outgoing message.
Signalling
Domain
Relocation Target technology of the last RANAP Relocation Preparation procedure is determined from the last received RANAP RELOCATION
Outgoing REQUIRED message.
Target
Technology
Outgoing Target Radio Access Technology (RAT) of the last outgoing inter-RAT handover attempt as determined from the RRC "Handover
Handover From UTRAN Command".
Target
Technology
Outgoing IRAT Outgoing IRAT Handover Failure Cause is populated with the cause value contained in the last Handover from UTRAN Failure
Handover message when received.
Failure Cause
Redirected Redirected Radio Access Technology (RAT) as determined from the content of the last "RRC Connection Release" indicating
Technology redirection.
Redirected Redirected EARFCN, UARFCN or ARFCN determined from the content of the last "RRC Connection Release" indicating redirection.
ARFCN

992-0608-08 Rev. 001
IFHO Attempts [Ericsson] Sum of the INTERNAL_IFHO_EXECUTION_ACTIVE GPEH messages received with indication of success or failure.
IFHO Failures [Ericsson] Sum of the INTERNAL_IFHO_EXECUTION_ACTIVE GPEH messages received with indication of failure.
Trace ID Nokia Megamon: Call Identifier contained in the Megamon EMIL GEO interface message header and which is unique on the serving
RNC for the duration of the RRC connection. Others, the session identifier from GeoSoft RAN.
Mean CS RAB Mean CS RAB (Circuit-Switched Domain Radio Access Bearer) Setup Time calculated as the difference between RANAP RAB
Setup Time Assignment Response and RAB Assignment Request.
Max CS RAB Maximum CS RAB (Circuit-Switched Domain Radio Access Bearer) Setup Time calculated as the difference between RANAP RAB
Mean PS RAB Mean PS RAB (Packet-Switched Domain Radio Access Bearer) Setup Time calculated as the difference between RANAP RAB
Max PS RAB Maximum PS RAB (Packet-Switched Domain Radio Access Bearer) Setup Time calculated as the difference between RANAP RAB
CS RAB Number of CS RAB (Circuit-Switched Domain Radio Access Bearer) establishment attempts as indicated by the number of RABs to
Establishment established in RANAP RAB Assignment Request messages.
Attempts
PS RAB Number of PS RAB (Packet-Switched Domain Radio Access Bearer) establishment attempts as indicated by the number of RABs to
Establishment established in RANAP RAB Assignment Request messages.
Attempts
CS RAB Number of RANAP RAB establishment attempts that fail in the CS domain as indicated by the number of failed to setup RABs
Establishment indicated in RANAP RAB Establishment Response messages.
Failures
PS RAB Number of RANAP RAB establishment attempts that fail in the PS domain as indicated by the number of failed to setup RABs
Establishment indicated in RANAP RAB Establishment Response messages.
Failures
CS RABs The number of CS RAB abnormal releases is determined by aggregating CS RABs closed with RANAP RAB or signaling connection
Dropped release procedure with RANAP Cause indicating abnormal release and CS RABs released as result of a dropped RRC connection.

992-0608-08 Rev. 001
PS RABs The number of PS RAB abnormal releases is determined by aggregating PS RABs closed with RANAP RAB or signaling connection
Dropped release procedure with RANAP Cause indicating abnormal release and PS RABs released as result of a dropped RRC connection.
Average UL [Nokia] Mean throughput of all uplink PS traffic calculated at the MAC-d sublayer by dividing the sum of all uplink streaming,
Data Rate interactive and background PDU data amounts by the sum of the collection period durations.
[kbps]
Average DL [Nokia] Mean throughput of all downlink PS traffic calculated at the MAC-d sublayer by dividing the sum of all downlink streaming,
Data Rate interactive and background PDU data amounts by the sum of the collection period durations.
[kbps]
UL PS [Nokia] Total uplink data volume of PS streaming data RABs calculated at the MAC-d sublayer on the basis of Megamon
Streaming Throughput Ticket messages.
Data Volume
[kbytes]
DL PS [Nokia] Total downlink data volume of PS streaming data RABs calculated at the MAC-d sublayer on the basis of Megamon
Streaming Throughput Ticket messages.
Data Volume
[kbytes]
UL PS [Nokia] Total uplink data volume of PS interactive data RABs calculated at the MAC-d sublayer on the basis of Megamon
Interactive Throughput Ticket messages.
Data Volume
[kbytes]
DL PS [Nokia] Total downlink data volume of PS interactive data RABs calculated at the MAC-d sublayer on the basis of Megamon
Interactive Throughput Ticket messages.
Data Volume
[kbytes]
UL PS [Nokia] Total uplink data volume of PS background Data RABs calculated at the MAC-d sublayer on the basis of Megamon
Background Throughput Ticket messages.
Data Volume
[kbytes]

992-0608-08 Rev. 001
DL PS [Nokia] Total downlink data volume of PS background data RABs calculated at the MAC-d sublayer on the basis of Megamon
Background Throughput Ticket messages.
Data Volume
[kbytes]
Mean UL User [Ericsson] Mean uplink throughput is the sum of the uplink user plane throughput events (kbit/s) contained in the INTERNAL_
Throughput PACKET_DEDICATED_THROUGHPUT GPEH message divided by the number of uplink user plane throughput events. Mean uplink
[kbps] throughput measures uplink RLC payloads of packet interactive radio bearers on a dedicated connection over all RACH, DCH and E-
DCH transport channels.
Mean DL User [Ericsson] Mean downlink throughput is the sum of the downlink user plane throughput events (kbit/s) contained in the INTERNAL_
Throughput PACKET_DEDICATED_THROUGHPUT GPEH message divided by the number of downlink user plane throughput events. Mean
[kbps] downlink throughput measures downlink RLC payloads of RLC payloads of packet interactive radio bearers on a dedicated
connection over all FACH, DCH and HS-DSCH transport channels.
Intersite Intersite distance of the start cell of the connection is calculated from the Network Element table, and may be expressed in either
Distance miles or meters in the Call Table, but will be exported in meters in LSR output.
[Meters/Miles]
Range ISD Range as determined using the Last Propagation Delay of the call or fragment.
Ratio
Global ID [LSR only] A random string generated by TrueCall which provides a global call record identifier for the composite call record of the
call or fragment. This is expected to be unique within the domain of a given IRIS server. Global ID is not expressed in Call Table.
Fragment ID [LSR only] An integer identifier assigned to a fragment of a fragmented call which is unique for a given Global ID. TrueCall
associates Fragment IDs to fragments in increasing order starting with the value '1.' Fragment ID is not expressed in Call Table.
Composite Indicates a composite call that consists of more than one call fragment. In UMTS, fragmentation is performed by the GSR state
Call machine.
PLMN ID PLMN-ID of start cell

Ver. 6.3.0 | 2020-03-31 B TrueCall LSR Data Types
992-0608-08 Rev. 001
B TrueCall LSR Data Types

The following provides a description of the data types listed in this document:
string
A string consists of a sequence of ASCII coded characters.
The strings for “Start GUMMEI” and “End GUMMEI” consist of 4 period-separated integers which
indicate, from left to right, the following: MCC, MNC, MME Group ID, and MME Code. In the
following example, the MCC is 405, the MNC is 874, the MME Group ID is 32771, and the MME Code
is 7 :
405.874.32771.007
The string for “Global ID” is formatted as a hexadecimal string. An example is shown below:
7aa5a16ef55bb27f7e643d24f22624f7a207d500
double
A double consists of an IEEE 754 double-precision binary floating-point format: binary64. It consists
of a sign (1 bit), an exponent (11 bits), and a fraction (52 bits). LSR displays a double of a sequence of
ASCII coded. It may be expressed as a sequence of digits, followed by an optional period, which, if
included, will be followed with an additional sequence of digits. This may be followed with an
exponent.
https://en.wikipedia.org/wiki/Double-precision_floating-point_format
int64
A sequence of digits which may be preceded with a negative sign.
UMTS P-TMSI and TMSI are expressed in hexadecimal as shown below:
dae80c05
time
A time is an ASCII string which represents the date, i.e., month (M), day (D), and year (Y) together with
a time, which consists of an hour (h) and minute (m). It is formatted as follows:
MM/DD/YYYY hh:mm
Examples are shown below for June 6, 2019 9 AM and December 12, 1999 at 11:50 PM:
6/6/2019 9:00
12/12/1999 23:59
duration
A duration is an ASCII string which represents a time interval, and comes in four formats:

Ver. 6.3.0 | 2020-03-31 B TrueCall LSR Data Types
992-0608-08 Rev. 001
1. second(s) with one millisecond precision and formatted as follows for durations of less than 1
minute: 00:ss.zzz
2. minutes and seconds with 1 second precision formatted as follows: mm:ss
3. hours, minutes, and seconds with 1 second precision formatted as follows: h:mm:ss
4. zero seconds is formatted as follows: 00:00
Examples are shown below for each case:
1. 10010 milliseconds: 00:10.010

2. 5 minutes, 10010 milliseconds: 05:10
3. 3 hours, 10 minutes, 2500 milliseconds: 3:10:03
4. Zero milliseconds 00:00
bool
A bool data type is displayed as ASCII code “TRUE” or “FALSE.”
float
The float data type is used in LTE in place of “double” when the Permission is set to “5G NSA.” It has
represents the same data type as “double.”


SFD Truecall Umts 63

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SFD Truecall Umts 63

Uploaded by

Copyright:

Available Formats

TrueCall

System Features Document

Software Version 6.3.0

Appendix B: UMTS KPIs

© NETSCOUT CONFIDENTIAL & PROPRIETARY

NETSCOUT SYSTEMS, INC

GNU GPL Source Code Request

TrueCall System Features Document 2

Copyright NETSCOUT 2009-2020. All rights reserved.

TrueCall System Features Document 3

TrueCall System Features Document 4

Call Attribute/LSR Description of Change

TrueCall System Features Document 5

The vendors supported by the Common UMTS Client are:

l Huawei OSSii NBI

A.1 Common UMTS KPIs

Note: KPI Explorer Headings are in bold text.

TrueCall System Features Document 6

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 7

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 8

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 9

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 10

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 11

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 12

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 13

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 14

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 15

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 16

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 17

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 18

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 19

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 20

KPI Name Description Unit Vendor Widget Support

Map KPI Top Top Top

TrueCall System Features Document 21