SFD TrueCall Common-LTE 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 A: Common LTE 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
Common LTE What’s New 5

A Common LTE KPIs 7
A.1 Common LTE KPIs 8
A.2 Common LTE Call Attributes / LSR Fields: Descriptions and Units 65
A.3 Common LTE Enumerated Values 114
B TrueCall LSR Data Types 142

Common LTE What’s New
Feature ID Description
F-10236 TrueCall/nGenius TrueCall Support for Huawei OSSii NBI CQI and PHR KPIs
This feature provides Huawei LTE OSSii-based NBI CQI and PHR Call Attributes/LSR
fields and KPIS in TrueCall.
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 and KPIs
The following KPIs were added, modified, or deleted for 6.3.0:
KPI Description of Change

Mean CQI Added support for Huawei
Power Headroom Added support for Huawei
SgNB Change Attempts New KPI for Ericsson, Samsung, Huawei.
SgNB Change Failures
SgNB Change Successes
SgNB Change Failure Rate
SgNB Modification Attempts
SgNB Modification Failures
SgNB Modification Successes
SgNB Modification Failure Rate
The following Call Attributes/LSRs were added, modified, or deleted for 6.3.0:
Call Attribute/LSR Description of Change

Start Timing Advance Updated help description
End Timing Advance Updated help description
Mean CQI Added support for Huawei
CQI Cell Added support for Huawei
UE Power Headroom Added support for Huawei

Ver. 6.3.0 | 2020-03-31 Common LTE What’s New
992-0608-08 Rev. 001
Call Attribute/LSR Description of Change

5G EN-DC SgNB Change Attempts New Call Attribute for Ericsson, Samsung, Huawei.
5G EN-DC SgNB Change Failures
5G EN-DC SgNB Modification
Attempts
5G EN-DC SgNB Modification
Failures
LTE PLMN-ID New Call Attribute for all vendors. Controlled Release in 6.3.0.

A Common LTE KPIs
GeoSoft RAN is a prerequisite for the TrueCall Common LTE client.
Vendors that are supported by the TrueCall Common LTE client are
l Ericsson
l Huawei OSSii NBI
l Nokia
l Alcatel-Lucent (Nokia PCMD)
l Samsung
l ZTE
l Altiostar
TrueCall servers can be configured to hide vendor-specific KPIs and Call Attributes for the vendors that are not in an operator’s network.
Because Nokia does not provide support in the traceport as part of the current OSSii agreement between NETSCOUT and Nokia, the
following specification must be provided by the customer to NETSCOUT Sales under a three-way NDA between NETSCOUT, Nokia, and the
customer:
Nokia Data Collection and Analytics Platforms (DCAP)
LTE GEO Interface
Interface Specification

Ver. 6.3.0 | 2020-03-31 A Common LTE KPIs
992-0608-08 Rev. 001
DN10819673
V18.2.1
Approval Date – 2018-08-03
Please contact NETSCOUT PLM for more information.
A.1 Common LTE KPIs

The following table displays descriptions and units of the Common LTE KPIs:
Note: KPI Explorer Headings are in bold text.
Nokia PCMD is referred to as Alcatel-Lucent in this section.
KPI Name Description Unit Vendor Widget Support
Map KPI Top NE Top Top Device

Explorer Subscriber
Accessibility
RRC
Establishment

992-0608-08 Rev. 001

Explorer Subscriber
RRC Connection Number of RRC Connections # All √ √ √ √ √
Requests determined to be new RRC
connections due to receipt of an
RRC Connection Request, RRC
Connection Setup, RRC Connection
Setup Complete, RRC Connection
Reject message, RRC Connection
Request NB, RRC Connection Setup
NB, RRC Connection Setup
Complete NB, RRC Connection
Resume Request NB, RRC
Connection Resume NB or RRC
Connection Resume Complete NB.
Connection requests for which only
RRC Connection Resume Request,
RRC Connection Resume, or RRC
Connection Resume Complete are
received, and for which no other
aforementioned message is
received, are not counted.
RRC Setup Number of RRC Connection # All √ √ √ √ √
Failures Establishment attempts that fail
because of RRC Connection Setup
Timeout or RRC Connection Reject
including NB-IoT calls and RRC
Connection Resume (NB-IoT only)
establishment requests.

992-0608-08 Rev. 001

Explorer Subscriber
RRC Successes [Ericsson] Number of successful # Ericsson √ √ √
RRC connection establishments
including NB-IoT and successful
NB-IoT RRC connection resumes.
Non-NB-IoT RRC connection resume
procedures are not counted unless
they fallback to RRC connection
establishment.
RRC Setup Failed RRC establishments as a % All √ √ √ √ √
Failure Rate percentage of RRC attempts,
including NB-IoT and successful
NB-IoT RRC connection resume
procedures. Non-NB-IoT RRC
connection resumes are not
considered in the calculation.
S1 Initial √
Context
Establishment
S1 Initial Context Number of S1 Initial Context Setup # All √ √ √ √ √
Setup Attempts Response + S1 Initial Context Setup
Failure. Includes NB-IoT calls.
S1 Initial Context Number of S1 Initial Context Setup # All √ √ √ √ √
Setup Failures Failure messages. Includes NB-IoT
calls.
S1 Initial Context S1 Initial Context Setup Failures / S1 % All √ √ √ √ √
Setup Failure Initial Context Attempts. Includes
Rate NB-IoT calls.

992-0608-08 Rev. 001

Explorer Subscriber
Failed Attempts Number of RRC Connection setup # All √ √ √ √ √
failures + S1 Initial Context Setup
Failure + NAS authentication failure
during NAS Attach. Both WB-E-
EUTRAN and NB-IoT failed attempts
are counted. RRC Connection
resume failures are counted as
failed attempts.
Failed Attempt Failed Attempts as a percentage of % All √ √ √ √ √
Rate RRC Connection Requests including
NB-IoT RRC Connection Resume
Requests, but not non-NB-IoT RRC
Connection Resume Requests.
Includes NB-IoT calls.
NAS
Attach Attempts Number of Initial Attach Requests at # Ericsson, √ √ √ √ √
connection establishment Nokia,
Samsung,
Huawei,
ZTE,
Altiostar
Attach Rejects Number of Initial Attach Rejects at # Ericsson, √ √ √ √ √
Samsung,
Huawei,
ZTE,
Altiostar

992-0608-08 Rev. 001

Explorer Subscriber
Attach Reject Ratio between Attach Rejects and % Ericsson, √ √ √ √
Rate Attach Requests Nokia,
Samsung,
Huawei,
ZTE,
Altiostar
Tracking Area Number of Tracking Area Update # Ericsson, √ √ √ √ √
Update Attempts Requests at connection Nokia,
establishment Samsung,
Huawei,
ZTE,
Altiostar
Tracking Area Number of Tracking Area Update # Ericsson, √ √ √ √ √
Update Rejects Rejects at connection establishment Nokia,
that are not ciphered Samsung,
Huawei,
ZTE,
Altiostar
Tracking Area Ratio between Tracking Area % Ericsson, √ √ √ √
Update Reject Update Rejects and Tracking Area Nokia,
Rate Update Requests Samsung,
Huawei,
ZTE,
Altiostar

992-0608-08 Rev. 001

Explorer Subscriber
Service Requests Number of Service Requests at # Ericsson, √ √ √ √ √
Samsung,
Huawei,
ZTE,
Altiostar
Service Rejects Number of Service Rejects at # Ericsson, √ √ √ √ √
Samsung,
Huawei,
ZTE,
Altiostar
Service Reject Ratio between Service Rejects and % Ericsson, √ √ √ √
Rate Service Requests Nokia,
Samsung,
Huawei,
ZTE,
Altiostar
Extended Number of Extended Service # Ericsson, √ √ √ √ √
Service Requests at connection Nokia,
Requests establishment Samsung,
Huawei,
ZTE,
Altiostar

992-0608-08 Rev. 001

Explorer Subscriber
Extended Number of Extended Service # Ericsson, √ √ √ √ √
Service Rejects Rejects at connection establishment Nokia,
Samsung,
Huawei,
ZTE,
Altiostar
Extended Ratio between Extended Service % Ericsson, √ √ √ √
Service Reject Rejects and Extended Service Nokia,
Rate Requests Samsung,
Huawei,
ZTE,
Altiostar
Detach Requests Number of UE Initiated Detach # Ericsson, √ √ √ √ √
by UE Requests at connection Nokia,
establishment Samsung,
Huawei,
ZTE,
Altiostar
eRAB
eRAB Attempts Number of eRAB setup attempts # All √ √ √ √ √
contained in S1 Initial Context Setup
Request and S1 eRAB Setup
Request messages

992-0608-08 Rev. 001

Explorer Subscriber
eRAB Failed Number of eRAB setup attempts # All √ √ √ √ √
Attempts failed due to: S1 Initial Context
Setup Failure + S1 Initial Context
Setup Response or S1 eRAB Setup
Response not indicating eRAB
establishment
eRAB Failed Failed eRAB setup attempts as a % All √ √ √ √ √
Attempt Rate percentage of total eRAB setup
attempts
VoLTE eRAB
VoLTE eRAB Number of QCI1 eRAB setup # All √ √ √ √ √
Attempts attempts contained in S1 Initial
Context Setup Request and S1 eRAB
Setup Request messages
VoLTE eRAB Number of QCI1 eRAB setup # All √ √ √ √ √
Failed Attempts attempts failed due to: S1 Initial
Context Setup Failure + S1 Initial
Context Setup Response or S1 eRAB
Setup Response not indicating eRAB
establishment
VoLTE eRAB Failed QCI1 eRAB setup attempts as % All √ √ √ √ √
Failed Attempt a percentage of total QCI1 eRAB
Rate setup attempts

992-0608-08 Rev. 001

Explorer Subscriber
VoLTE eRAB Number of VoLTE failed attempts # All √ √ √ √ √
Failed Attempts with cause of X2 handover, S1
Due to Mobility handover, CSFB, and Redirection
towards 1XRTT. This is not counted
in VoLTE failed attempts.
Video Call
eRAB
Video Call eRAB Number of QCI2 eRAB setup # All √ √ √ √ √
Attempts attempts contained in S1 Initial
Context Setup Request and S1 eRAB
Setup Request messages
Video Call eRAB The count of failed QCI2 eRAB setup # All √ √ √ √ √
Failed Attempts attempts
Video Call eRAB Video Call Attempt Failures / Video % All √ √ √ √ √
Failed Attempt Call Attempts
Rate
Retainability
Releases Normal Releases + Dropped # All √ √ √ √ √
Connections + Redirections +
Outgoing IRAT HO Successes. Both
WB-E-UTRAN and NB-IoT releases
are counted. RRC connections that
are successfully suspended are
also counted as release events.

992-0608-08 Rev. 001

Explorer Subscriber
Normal Releases Number of releases with these # All √ √ √ √ √
S1AP Release Causes - Radio
Access Layer Cause of User
Inactivity or Load Balancing
Tracking Area Update Required or
CS Fall Back Triggered or UE Not
Available For PS Service, Non-
Stratum Access Layer Cause of
Normal Release or Detach. Calls
that are successfully suspended are
considered to be normal releases.
Dropped Number of releases with S1AP # All √ √ √ √ √
Connections Release Cause other than those
considered as Normal Releases. A
non-default GeoSoft RAN
configuration option that excludes
S1AP release cause 'NAS
Unspecified' from this is available.
Includes NB-IoT drops.
Dropped Dropped connections as a % All √ √ √ √ √
Connection Rate percentage of releases. A non-
default GeoSoft RAN configuration
option that excludes S1AP release
cause 'NAS Unspecified' from this is
available. Includes NB-IoT releases
and drops.
Releases with The connections released with data # Ericsson √ √ √ √ √
Data Lost lost

992-0608-08 Rev. 001

Explorer Subscriber
Release with Ratio between connection releases % Ericsson √ √ √ √
Data Lost Rate with data lost and all the releases
Dropped Number of abnormal Releases with # Ericsson √ √ √ √ √
Connections with data lost.
Data Lost
Dropped Ratio between dropped connections % Ericsson √ √ √ √
Connections with with data lost and all the releases
Data Lost Rate
Reestablishment Number of RRC Reestablishment # All √ √ √ √ √
Attempts Request messages. Includes NB-IoT
Reestablishment attempts.
Reestablishment Number of RRC Reestablishment # All √ √ √ √ √
Failures Failure messages. Includes NB-IoT
Reestablishment failures.
Reestablishment Failed RRC Reestablishment % All √ √ √ √ √
Failure Rate Attempts as a percentage of total
RRC Reestablishment Attempts.
Includes NB-IoT Reestablishment
attempts and failures.
eRAB

992-0608-08 Rev. 001

Explorer Subscriber
eRAB Release Number of eRABs in the active state # All √ √ √ √ √
Attempts for which explicit release is
requested in S1 eRAB Release
Indication or S1 eRAB Release
Command message, or which are
implicitly released by being active
at the time of RRC connection
release including Normal Release,
Dropped Connection and
Redirection
eRAB Normal Number of active eRABs released # All √ √ √ √ √
Releases normally when the RRC connection
closed due to Redirection or Normal
Release, or when the eRAB Id of the
eRAB is explicitly released in an S1
eRAB Release Indication or eRAB
Release Command
eRAB Drops Number of eRABs not admitted # All √ √ √ √ √
during outgoing X2 or S1 handover
+ number of active eRABs released
by S1 eRAB Release Indication or S1
eRAB Release Command with S1
cause indicating connection or
eRAB drop + number of eRABs
active at the time of a dropped
connection

992-0608-08 Rev. 001

Explorer Subscriber
eRAB Drop Rate eRAB drops as percentage of total % All √ √ √ √ √
eRABs setup successfully i.e. eRAB
Drops / (eRAB Attempts - eRAB
Failed Attempts)
eRAB Drops with eRAB Drops with data lost # Ericsson √ √ √ √ √
Data Lost
eRAB Drop with eRAB Drops with data lost divided % Ericsson √ √ √ √ √
Data Lost Rate by eRAB Release Attempts
VoLTE
VoLTE eRAB Number of QCI1 eRABs in the active # All √ √ √ √ √
Release state for which explicit release is
Attempts requested in S1 eRAB Release
Indication or S1 eRAB Release
Command message, or which are
implicitly released by being active
at the time of RRC connection
release including Normal Release,
Dropped Connection and
Redirection

992-0608-08 Rev. 001

Explorer Subscriber
VoLTE eRAB Number of QCI1 eRABs not # All √ √ √ √ √
Drops admitted during outgoing X2 or S1
handover + number of active QCI1
eRABs released by S1 eRAB
Release Indication or S1 eRAB
Release Command with S1 cause
indicating connection or eRAB drop
+ number of QCI1 eRABs active at
the time of a dropped connection
VoLTE eRAB VoLTE eRAB drops as percentage of % All √ √ √ √ √
Drop Rate total VoLTE eRABs setup
successfully i.e. VoLTE eRAB Drops /
(VoLTE eRAB Attempts - VoLTE
eRAB Failed Attempts)
Video Call
Video Call eRAB The count of QCI2 eRAB release # All √ √ √ √ √
Release attempts
Attempts
Video Call eRAB A QCI2 eRAB drop is when there is # All √ √ √ √ √
Drops an active QCI1 eRAB and we see
RRC Drop, or the established eRAB
cannot be handed over to the target
cell
Video Call eRAB Video Call eRAB Drops / (Video Call % All √ √ √ √ √
Drop Rate eRAB Attempts - Video Call eRAB
Failed Attempts)
Quality

992-0608-08 Rev. 001

Explorer Subscriber
Mean RRC Setup Mean time between RRC ms All √ √ √ √ √
Time Connection Setup Request and RRC
Connection Setup Complete across
all calls. Includes NB-IoT RRC
Connection Setup and NB-IoT RRC
Connection Resume procedure
setup times. Non-NB-IoT RRC
setup times are not considered in
this calculation.
Mean Mean E-UTRAN connection setup ms Samsung √ √ √ √ √
Connection time of E-UTRAN connections
Setup Time ending in the area. Setup time is
calculated from RRC Connection
Request until the latter of end of the
UE Capability Enquiry procedure or
S1AP Initial UE Context Setup
procedure and is only available for
sessions that have CSL.

992-0608-08 Rev. 001

Explorer Subscriber
Mean eRAB Mean time between RRC ms All √ √ √ √ √
Setup Time Connection Setup Request and RRC
Connection Setup Complete across
all Calls. Includes NB-IoT RRC
Connection Setup and NB-IoT RRC
setup times. Non-NB-IoT RRC
setup times are not considered in
this calculation.
Mean VoLTE Mean time between QCI1 eRAB ms All √ √ √ √ √
eRAB Setup setup attempt and QCI1 eRAB setup
Time success
Mean Video Call Mean time between QCI2 eRAB ms All √ √ √ √ √
eRAB Setup setup attempt and QCI2 eRAB setup
Time success

992-0608-08 Rev. 001

Explorer Subscriber
RLC DL Retransmitted DL RLC bytes for the % Samsung √ √ √ √ √
Retransmit Rate RRC connections as a percentage of
(Samsung) transmitted DL RLC bytes for the
RRC connections. Note that this
ratio can be greater than 100%
when the sum of RLC RL
Retransmitted Data Volume in the
aggregated CSLs exceeds the sum
of RLC DL Data Volume in the
aggregated CSLs. In the past, the
RLC Data Volume counts contained
in the CSL have been known to
reflect only the activity from the
time of the last intra-eNB handover
at the eNB and thus may not reflect
all of the activity described by the
CSL record.
Coverage

992-0608-08 Rev. 001

Explorer Subscriber
Mean CQI [Ericsson, ALU] Mean CQI. Alcatel- √ √ √ √ √
[Samsung] Mean Channel Quality Lucent,
Indicator taken at the end of the Ericsson,
RRC connections. Samsung,
[Altiostar] Mean Channel Quality Altiostar,
Indicator (CQI) calculated as the Nokia,
mean of the last received average Huawei
CQI in the VSE_DL_SCHED of each
connection.
[Nokia] Mean Channel Quality
Indicator (CQI) calculated as the
mean of the last valid received
wideband CQI received in the
utMeanLaWbCqi field of the MAC_
DL-UeThroughput events of each
connection.
[Huawei] Mean Channel Quality
Indicator (CQI) calculated as the
mean of the last valid received
wideband CQI received in the DL
Wideband CQI Code0 field of the UE
periodic radio link MR and UE
periodic radio link MR MDT events
of each connection.
Mean RSRP Power-weighted mean of last dBm All √ √ √ √ √
measured serving cell RSRP from
the Measurement Report

992-0608-08 Rev. 001

Explorer Subscriber
Median RSRP Median of last measured serving dBm All √ √ √ √ √
cell RSRP from the Measurement
Report
Mean RSRQ Arithmetic mean of last measured dB All √ √ √ √ √
serving cell RSRQ from the
Measurement Report
Power Mean of last Power Headroom dB All √ √ √ √ √
Headroom measurement of each RRC
connection. Derived from Power
Headroom in Vendor Specific
Events. In the case of Huawei,
Power Headroom is taken from the
DL Wideband CQI Code0 field of the
UE periodic radio link MR and UE
periodic radio link MR MDTevents.
Mean UE Tx [Samsung] Mean of the Last UE Tx dBm Samsung √ √ √ √ √
Power Power of the calls.

992-0608-08 Rev. 001

Explorer Subscriber
Mean UL RX [Samsung] The KPI is the arithmetic Samsung √ √ √ √ √
Interference mean of the Last UL Rx Interference
Power Power of each sampled call. For
Samsung, the last valid MAC_RX_
INTERFERENCE_UL from the VSE
Periodic RF Information message
events received over the call is
used to determine the last uplink
received interference power of a
call. Received interference power is
defined in 3GPP TS 36.214 as the
uplink received interference power,
including thermal noise, within one
physical resource block's bandwidth
of the resource block size in the
frequency domain.
Mean PUSCH [Samsung, Ericsson, Nokia, dB Ericsson, √ √ √ √ √
SINR Altiostar] Mean of last PUSCH SINR Nokia,
measurement of each RRC Samsung,
connection. Derived from PUSCH Altiostar
SINR contained in Vendor Specific
Events
Mean PUCCH Mean of last PUCCH SINR dB Ericsson, √ √ √ √ √
SINR measurement of each RRC Samsung
connection. Derived from PUCCH
SINR contained in Vendor Specific
Events

992-0608-08 Rev. 001

Explorer Subscriber
Mean UL SINR Average UL Signal to Interference dB Alcatel- √ √ √ √ √
Noise Ratio Lucent,
ZTE
TA Distance 95th Ninety-fifth percentile distance of Meters All √
Percentile the UE calculated from end timing or
advance and may be expressed in miles
meters or miles.
TA Bin1 Percentage of calls with end % All √
Percentage distance to intersite distance ratio
greater than 0.0 but less than 0.7,
where end distance is based on the
timing advance at the call end
greater than or equal to 0.7 but less
than 1.0, where end distance is
based on the timing advance at call
end
greater than or equal to 1.0 but less
than 1.5, where end distance is
based on the timing advance at call
end

992-0608-08 Rev. 001

Explorer Subscriber
greater or equal to than 1.5, where
end distance is based on the timing
advance at call end
Overshooting Severity of overshooting based on All √
Severity timing advance at call end
Mean NE Mean cell intersite distance is Meters All √
Intersite calculated based upon the contents or
Distance of the Network Element table and miles
may be expressed in meters or
miles.
Best Server by PCI of the serving cell with the most All √
Occurrence occurrences
Best Server PCI are ranked by the highest total PCI All √
RSRP of the serving cell PCI and up
to six neighbor PCIs for all calls
ending inside the bin. The value for
the bin is the best PCI by this
ranking. Each PCI is assigned a
color on the map. Move the mouse
over a bin to see the best PCI for
that bin. Note that the Best Server
Cell performs a similar ranking but
is more accurate because it uses
ECGI to identify the cells.

992-0608-08 Rev. 001

Explorer Subscriber
Best Server The Power-weighted mean RSRP of dBm All √
RSRP the best server using the ranking
according to "Best Server [PCI]"
Best Server Arithmetic mean RSRQ of best dB All √
RSRQ server
2nd Best Server PCI of the second best cell PCI All √
determined from RSRP of end cell
2nd Best Server Power-weighted mean RSRP of the dBm All √
RSRP second best server
2nd Best Server Arithmetic mean RSRQ of the dB All √
RSRQ second best server
3rd Best Server PCI of the third best cell determined PCI All √
from RSRP of end cell
3rd Best Server Power-weighted mean RSRP of the dBm All √
RSRP third best server
3rd Best Server Arithmetic mean RSRQ of the third dB All √
RSRQ best server
4th Best Server PCI of the fourth best cell PCI All √
4th Best Server Power-weighted mean RSRP of the dBm All √
RSRP fourth best server
4th Best Server Arithmetic mean RSRQ of the fourth dB All √
RSRQ best server
5th Best Server PCI of the fifth best cell determined PCI All √

992-0608-08 Rev. 001

Explorer Subscriber
RSRP fifth best server
5th Best Server Arithmetic mean RSRQ of the fifth dB All √
RSRQ best server
6th Best Server PCI of the sixth best cell determined PCI All √
RSRP sixth best server
6th Best Server Arithmetic mean RSRQ of the sixth dB All √
RSRQ best server
7th Best Server PCI of the seventh best cell PCI All √
RSRP seventh best server
7th Best Server Arithmetic mean RSRQ of the dB All √
RSRQ seventh best server
Dominance Count of unique PCI with mean # All √
Count RSRP within 5dB of best server
Mobility
Outgoing
Intra LTE
Handover
Intra-
frequency
Intra-eNB

992-0608-08 Rev. 001

Explorer Subscriber
Intra-Freq Intra- Number of intra-frequency intra- # Ericsson √ √ √ √ √
eNB HO Prep eNB HO preparation attempts
Attempts
Intra-Freq Intra- Number of intra-frequency intra- # Ericsson √ √ √ √ √
eNB HO Prep eNB HO preparation failures
Failures
Intra-Freq Intra- Number of RRC Connection # All √ √ √ √ √
eNB HO Exec Reconfiguration messages
Attempts containing Mobility Control Info IE
without target carrier frequency or
target carrier equals to the source
carrier when target carrier is
present when neither X2 nor S1
outgoing handover is underway
Intra-Freq Intra- Number of RRC Reestablishment # All √ √ √ √ √
eNB HO Exec Request when reestablishment
Failures cause indicates Radio Link Failure
or HO failure and when there is an
intra-f intra-eNB HO triggered
Intra-Freq Intra- Intra_freq intra_eNB HO Exec % All √ √ √ √ √
eNB HO Failure Failures / Intra_freq intra_eNB HO
Rate Exec Attempts
Inter-eNB X2

992-0608-08 Rev. 001

Explorer Subscriber
Intra-Freq X2 HO In the X2 HO Preparation Request # All √ √ √ √ √
Prep Attempts message, target carrier is unknown.
So the HO preparation attempt is
counted as intra-f at first and then
is corrected when RRC
Reconfiguration message is
available (target carrier info can be
obtained from this message)
Intra-Freq X2 HO Number of RRC Reestablishment # All √ √ √ √ √
Prep Failures Request when reestablishment
cause indicates Radio Link
Failure/HO Failure after outgoing X2
handover preparation has been
successfully completed. Because
target carrier info is unknown if HO
preparation fails, all HO
preparation failures are counted as
intra-f HO preparation failures
Intra-Freq X2 HO Number of RRC Connection # All √ √ √ √ √
Exec Attempts Reconfiguration messages
containing Mobility Control Info IE
target carrier equals the source
carrier if target carrier is present
after outgoing X2 handover
preparation has been successfully
completed

992-0608-08 Rev. 001

Explorer Subscriber
Intra-Freq X2 HO Number of RRC Reestablishment # All √ √ √ √ √
Exec Failures Request when reestablishment
Failure/HO Failure and when there
is an intra-f X2 HO triggered
Intra-Freq X2 HO Intra_freq X2 HO Prep Failures + % All √ √ √ √ √
Failure Rate Intra_freq X2 HO Exec
Failures)/Intra_freq X2 HO Prep
Attempts
Inter-eNB S1
Intra-Freq S1 HO In the S1 HO Preparation Request # All √ √ √ √ √
So each HO preparation attempt is

992-0608-08 Rev. 001

Explorer Subscriber
Intra-Freq S1 HO Number of RRC Reestablishment # All √ √ √ √ √
Prep Failures Request when reestablishment
Failure/HO Failure after outgoing S1
successfully completed. Because
target carrier info is unknown if HO
preparation fails, all HO
preparation failures are counted as
intra-freq HO preparation failures
Intra-Freq S1 HO Number of RRC Connection # All √ √ √ √ √
target carrier equals source carrier
if target carrier is present after
outgoing S1 handover preparation
has been successfully completed
Intra-Freq S1 HO Number of RRC Reestablishment # All √ √ √ √ √
is a intra-f S1 HO is triggered
Intra-Freq S1 HO Intra_freq S1 HO Prep Failures + % All √ √ √ √ √
Failure Rate Intra_freq S1 HO Exec
Failures)/Intra_freq S1 HO Prep
Attempts

992-0608-08 Rev. 001

Explorer Subscriber
Inter-
frequency
Intra-eNB
Inter-Freq Intra- Number of inter-frequency intra- # Ericsson √ √ √ √ √
eNB HO Prep eNB HO preparation attempts
Attempts
Inter-Freq Intra- Number of inter-frequency intra- # Ericsson √ √ √ √ √
eNB HO Prep eNB HO preparation failures
Failures
Inter-Freq Intra- Number of RRC Connection # All √ √ √ √ √
eNB HO Exec Reconfiguration messages
Attempts containing Mobility Control Info IE
and target carrier not equal to the
source carrier when neither X2 nor
S1 outgoing handover is underway
Inter-Freq Intra- Number of RRC Reestablishment # All √ √ √ √ √
eNB HO Exec Request when reestablishment
Failures cause indicates Radio Link
is an inter-f intra-eNB HO triggered
Inter-Freq Intra- Inter_freq intra_eNB HO Exec % All √ √ √ √ √
eNB HO Failure Failures / Inter_freq intra_eNB HO
Rate Exec Attempts
Inter-eNB X2

992-0608-08 Rev. 001

Explorer Subscriber
Inter-Freq X2 HO In the X2 HO Preparation Request # All √ √ √ √ √
So all HO preparation attempts are
Inter-freq X2 HO Inter-frequency X2 HO Preparation # All √ √ √ √ √
Preparation Failures
Failures
Inter-Freq X2 HO Number of RRC Connection # All √ √ √ √ √
source carrier after outgoing X2
successfully completed
Inter-Freq X2 HO Number of RRC Reestablishment # All √ √ √ √ √
Failure/HO Failure and there is an
inter-freq X2 HO is triggered

992-0608-08 Rev. 001

Explorer Subscriber
Inter-Freq X2 HO Inter_freq X2 HO Exec % All √ √ √ √ √
Failure Rate Failures/Inter_freq X2 HO Prep
Attempts. Inter_freq X2 HO Prep
Failures not included here since it
cannot be determined from L3
messages
Inter-eNB S1
Inter-Freq S1 HO In the S1 HO Preparation Request # All √ √ √ √ √
So all HO preparation attempts are
Inter-Freq S1 HO Inter-frequency X2 HO Preparation # All √ √ √ √ √
Prep Failures Failures
Inter-Freq S1 HO Number of RRC Connection # All √ √ √ √ √
source carrier after outgoing S1
successfully completed

992-0608-08 Rev. 001

Explorer Subscriber
Inter-Freq S1 HO Number of RRC Reestablishment # All √ √ √ √ √
Failure/HO Failure and there is a
inter-freq S1 HO is triggered
Inter-Freq S1 HO Inter_freq S1 HO Exec % All √ √ √ √ √
Failure Rate Failures/Inter_freq S1 HO Prep
Attempts. Inter_freq S1 HO Prep
Failures not included here since it
cannot be determined from L3
messages
Inter-RAT
Outgoing IRAT [Ericsson, Nokia, Samsung, Huawei, # Ericsson, √ √ √ √ √
HO Prep ZTE, Altiostar] Number of S1AP Nokia,
Attempts Handover Required messages with Samsung,
Handover Type indicating LTE to Huawei,
UTRAN or LTE to GERAN handover ZTE,
+ number of S1AP Uplink Altiostar
CDMA2000 Tunneling messages
with CDMA2000 RAT Type
indication 1xRTT or HRPD

992-0608-08 Rev. 001

Explorer Subscriber
HO to 2G Prep [Ericsson, Nokia, Samsung, Huawei, # Ericsson, √ √ √ √ √
Attempts ZTE, Altiostar] Number of S1AP Nokia,
Handover Required messages with Samsung,
GERAN handover + number of S1AP ZTE,
Uplink CDMA2000 Tunneling Altiostar
messages that include CDMA2000
RAT Type 1xRTT
HO to 3G Prep [Ericsson, Nokia, Samsung, Huawei, # Ericsson, √ √ √ √ √
Attempts ZTE, Altiostar] Number of S1AP Nokia,
Handover Required messages with Samsung,
UTRAN handover + number of S1AP ZTE,
Uplink CDMA2000 Tunneling Altiostar
messages with CDMA2000 RAT
Type HRPD indication
Outgoing IRAT [Ericsson, Nokia, Samsung, Huawei, # Ericsson, √ √ √ √ √
HO Failures ZTE, Altiostar] Outgoing IRAT HO Nokia,
Prep Attempts - Outgoing IRAT HO Samsung,
Successes to 3GPP and 3GPP2 Huawei,
ZTE,
Altiostar
Outgoing IRAT [Ericsson, Nokia, Samsung, Huawei, % Ericsson, √ √ √ √ √
HO Failure Rate ZTE, Altiostar] Outgoing IRAT HO Nokia,
Failures / Outgoing IRAT HO Prep Samsung,
Attempts Huawei,
ZTE,
Altiostar

992-0608-08 Rev. 001

Explorer Subscriber
Incoming
Prep Attempts
HO from 2G [Ericsson, Nokia, Samsung, Huawei, # Ericsson, √ √ √ √ √
Prep Attempts ZTE, Altiostar] Incoming Inter-RAT Nokia,
Handover Attempts from 2G (GSM). Samsung,
When Handover Type in the Huawei,
incoming S1 HO Request indicates ZTE,
GERANtoLTE Altiostar
HO from 3G [Ericsson, Nokia, Samsung, Huawei, # Ericsson, √ √ √ √ √
Prep Attempts ZTE, Altiostar] Incoming Inter-RAT Nokia,
Handover Attempts from 3G Samsung,
(UMTS). When Handover Type in Huawei,
the incoming S1 HO Request ZTE,
indicates UTRANtoLTE Altiostar
CSFB

992-0608-08 Rev. 001

Explorer Subscriber
CS Fallback Counted if one of the following # All √ √ √ √ √
Attempts conditions is met and RRC
Connection Re-establishment
procedure is not subsequently
attempted at the eNB: the
connection is released with S1AP
Cause "CS Fallback Triggered" or
"UE Not Available for PS Service";
an RRC Mobility From E-UTRA
Command message containing
CSFB indication is received; an
S1AP Initial Context Setup Request
is received with CS Fallback
Indicator; an S1AP UE Context
Modification Request message with
CS Fallback Indicator; an HO From
EUTRA Preparation Request to
CDMA 2000 with dual Rx TX
Redirect Indicator. Note that a
maximum of one attempt per call is
counted
CSFB to GERAN Counted if the last CSFB attempt in # All √
a call is towards GERAN
CSFB to UTRA Counted if the last CSFB attempt in # All √
a call is towards UTRA
CSFB to 1xRTT Counted if the last CSFB attempt in # All √
a call is towards 1xCSFB

992-0608-08 Rev. 001

Explorer Subscriber
Enhanced CSFB Counted if the last CSFB attempt in # All √
to 1xRTT a call is towards e1xCSFB
CSFB to UMTS Count of CSFB Attempts to UMTS # Alcatel- √ √ √ √ √
and GSM and GSM Lucent
SRVCC HO Number of calls where an SRVCC # All √ √ √ √ √
Attempts Handover Indication is received in
an S1AP Handover Required
message
Redirections RRC Connection Release containing # All √ √ √ √ √
both Redirected Absolute Radio
Frequency Channel Number and
Redirected Radio Access
Technology is received or S1AP
Release Cause is received and the
S1AP Release Cause indicates
Radio Access Layer cause of Inter-
Radio Access Technology
Redirection, Redirection towards
1xRTT or Handover Desirable for
Radio Reason. NB-IoT RRC
connection releases with redirected
carrier information are not included
in the KPI.
Redirections Radio Access Technology derived # All √ √
Intra LTE from RRC Redirected Carrier
Information of the RRC Connection
Release message is EUTRA

992-0608-08 Rev. 001

Explorer Subscriber
Redirections To Radio Access Technology derived # All √ √
UTRAN from RRC Redirected Carrier
Release message is UTRA-FDD or
UTRA-TDD or UTRA-TDD-r10
GERAN from RRC Redirected Carrier
Release message is GERAN
CDMA2000 from RRC Redirected Carrier
HRPD Information of the RRC Connection
Release message is CDMA2000-
HRPD
CDMA2000 from RRC Redirected Carrier
1xRTT Information of the RRC Connection
Release message is CDMA2000-
1xRTT
Utilization
RRC
Unique IMSI Number of unique IMSI seen across # All √ √ √ √
all calls

992-0608-08 Rev. 001

Explorer Subscriber
Mean Trace Mean duration of the cell trace per s All √ √
Duration call, where the duration of each call
is calculated as the sum of the
fragment durations. This duration
will differ from the difference
between call start and end times
due to clock differences as well as
overlap between consecutive
fragments. [Samsung] CSL calls
without 3GPP cell trace events are
not included in the mean
calculation. [Altiostar] Calls
consisting entirely of Altiostar
internal events are excluded from
the mean calculation.
User Traffic Total trace duration across all calls Er All √ √ √ √ √
Erlangs as a percentage of the query
duration
VoLTE eRAB
Mean VoLTE Mean QCI1 eRAB duration across s All √ √ √ √ √
eRAB Duration all successful calls
VoLTE Erlangs Total VoLTE call duration across all Er All √ √ √ √ √
calls as a percentage of the query
duration
VoLTE eRABs Number of new setup VoLTE eRABs All √ √ √ √
with Emergency with emergency ARP
ARP

992-0608-08 Rev. 001

Explorer Subscriber
Video Call
eRAB
Mean Video Call Mean QCI2 eRAB duration across s Ericsson, √ √ √ √ √
eRAB Duration all successful calls Nokia,
Samsung,
Huawei,
ZTE,
Altiostar
Carrier
Aggregation
Carrier Sum over all calls of the time that Ericsson, √ √ √ √ √
Aggregation Carrier Aggregation service is Nokia,
Service Time provided. Samsung,
Huawei,
ZTE,
Altiostar,
Alcatel-
Lucent
Carrier Mean percentage of RRC connected Ericsson, √ √ √ √ √
Aggregation time that Carrier Aggregation Nokia,
Service Rate service is active Samsung,
Huawei,
ZTE,
Altiostar,
Alcatel-
Lucent
RLC

992-0608-08 Rev. 001

Explorer Subscriber
RLC Data Sum of RLC PDU bytes transmitted kbytes Samsung, √ √ √ √ √
Volume DL by the E-UTRAN to UEs in the user Alcatel-
plane for E-UTRAN connections Lucent
within the filtered set. The downlink
volume does not include
retransmitted RLC PDUs. When
intra-eNB handovers occur during
the connection, only counts after
the final intra-eNB handover at an
eNB visit are included in the count
RLC Data Sum of RLC PDU bytes received by kbytes Samsung, √ √ √ √ √
Volume UL the E-UTRAN from UEs in the user Alcatel-
plane for E-UTRAN connections Lucent
within the filtered set. When intra-
eNB handovers occur during the
connection, only counts after the
final intra-eNB handover at an eNB
visit are included in the count
RLC PDU DL Includes only downlink PDUs kbytes Alcatel- √ √ √ √ √
Retransmit retransmitted on Best Effort Lucent,
Volume bearers (QCI values 5-9) at the RLC Samsung
level
RLC DL Rate is calculated based on the % Alcatel- √ √ √ √ √
Retransmit Rate ratio of PDU Kbytes retransmitted Lucent,
to PDU Kbytes transmitted for the Samsung
first time on downlink Best Effort
bearers at the RLC level.

992-0608-08 Rev. 001

Explorer Subscriber
RLC SDU UL UL RLC SDU GBR & BE Received kbytes Alcatel- √ √ √ √ √
Volume bytes Lucent
RLC UL UL RLC SDU average throughput for kbps Alcatel- √ √ √ √ √
Throughput BE bearers Lucent
RLC DL DL RLC PDU average throughput for kbps Alcatel- √ √ √ √ √
Throughput BE bearers Lucent
S1-U GTP-U
S1-U Data [Samsung] Sum of downlink GTP kbytes Samsung √ √ √ √ √
Volume DL PDU bytes received from SGW over
the S1-U interface for E-UTRAN
connections within the filtered set
S1-U Data [Samsung] Sum of uplink GTP PDU kbytes Samsung √ √ √ √ √
Volume UL bytes transmitted to SGW over the
S1-U interface for E-UTRAN
connections within the filtered set
Mean Downlink [Samsung] Mean Downlink IP kbps Samsung √ √ √ √ √
IP Throughput Throughput calculated by dividing
the sum of S1-U DL Data Volumes
(based on CSL rxDataFromSG over
all RABs) for which CSL Call
Segment Duration is greater than
zero by the sum of CSL Call
Segment Durations for the calls.

992-0608-08 Rev. 001

Explorer Subscriber
Mean Uplink IP [Samsung] Mean Uplink IP kbps Samsung √ √ √ √ √
Throughput Throughput calculated by dividing
the sum of S1-U UL Data Volumes
(based on CSL txDataToSG over all
RABs) for which CSL Call Segment
Duration is greater than zero by the
sum of CSL Call Segment Durations
for the calls.
MAC
MAC Volume DL [Ericsson] Total successfully kbytes Ericsson, √ √ √ √ √
transferred DL volume at MAC Nokia
layer
[Nokia] Cumulative number of bytes
sent over non-GBR as well as GBR
downlink bearers as measured at
the MAC layer. Downlink MAC bytes
are read from the
utDlsSentNonGbrBytes and
utDlsSentGbrBytes fields of the
periodic MAC_DL_UeThroughput
message. It is assumed that the
Nokia non-GBR and GBR downlink
byte counts are incremental for the
call session and do not wrap-
around at 4294967295 bytes.

992-0608-08 Rev. 001

Explorer Subscriber
MAC Volume UL [Ericsson] Total successfully kbytes Ericsson, √ √ √ √ √
transferred UL volume at MAC Nokia
layer [Nokia] The cumulative
number of bytes received over non-
GBR as well as GBR uplink bearers
as measured at the MAC layer.
Uplink MAC bytes are read from the
utUlsReceivedNonGbrBytes and
utUlsReceivedGbrBytes fields of the
periodic MAC_UL_UeThroughput
message. It is assumed that the
Nokia non-GBR and GBR uplink byte
counts are incremental for the call
session and do not wrap-around at
4294967295 bytes.

992-0608-08 Rev. 001

Explorer Subscriber
Mean MAC [Nokia] Total number of bytes sent kpbs Nokia √ √ √ √ √
Throughput DL in the downlink over both GBR as
well as non-GBR bearers at the
MAC layer divided by the
accumulated collection period for
the selected call set. The number of
GBR bytes is accumulated over
utDlsSentGbrBytes of the MAC_DL_
UeThroughput event and the
number of non_GBR bytes is
accumulated over
utDlsSentNonGbrBytes of the MAC_
DL_UeThroughput event. The
collection period of each MAC_DL_
UeThroughput is taken as the sum
of utSingleCWTx (number of single
codeword transmissions) and
utDualCWTx (number of dual
codeword transmissions). It is
assumed that the Nokia non-GBR
and GBR downlink byte counts are
incremental for the call session and
do not wrap-around at 4294967295
bytes.

992-0608-08 Rev. 001

Explorer Subscriber
Mean MAC [Nokia] Total number of bytes kpbs Nokia √ √ √ √ √
Throughput UL received in the uplink over both
GBR as well as non-GBR bearers at
the MAC layer divided by the
the selected call set. The number of
GBR bytes is accumulated over
utUlsReceivedGbrBytes of the
MAC_UL_UeThroughput event and
the number of non_GBR bytes is
accumulated over
utUlsReceivedNonGbrBytes of the
MAC_UL_UeThroughput event. The
collection period of each MAC_UL_
UeThroughput is taken from
utNumOfReceivedTxAll (number of
received transmissions). It is
assumed that the Nokia non-GBR
and GBR uplink byte counts are
incremental for the call session and
do not wrap-around at 4294967295
bytes.
HARQ DL Downlink HARQ Retransmissions # Alcatel- √ √ √ √ √
Retransmissions for Transmission Scheduled by DS Lucent
by DS
HARQ DL HARQ DL Retransmissions by DS / % Alcatel- √ √ √ √ √
Retransmit Rate HARQ DL Initial Transmissions by Lucent
by DS DS

992-0608-08 Rev. 001

Explorer Subscriber
MAC UL PDUs UL Total MAC PDUs for Initial # Alcatel- √ √ √ √ √
Transmission Lucent
HARQ DL Initial Initial Hybrid Automatic Repeat # Alcatel- √ √ √ √ √
Transmissions Request transmissions in the Lucent
by DS downlink.
DL TTIs UE Total number of downlink TTIs # Alcatel- √ √ √ √ √
Scheduled scheduled to the UE during the Lucent
PCMD collection interval.
Mean DL TTIs UE Mean number of downlink TTIs # Alcatel- √ √ √ √ √
Scheduled scheduled to the UE per eNB PCMD Lucent
DL MIMO TTIs Total downlink Transmission Time # Alcatel- √ √ √ √ √
UE Scheduled Intervals (TTIs) scheduled while the Lucent
UE is in the Multiple-Input Multiple-
Output (MIMO) state.
Mean DL MIMO Mean number of downlink # Alcatel- √ √ √ √ √
TTIs UE Transmission Time Intervals (TTIs) Lucent
Scheduled scheduled per eNB PCMD while the
UE is in the Multiple-Input Multiple-
Output (MIMO) state.
PDCP

992-0608-08 Rev. 001

Explorer Subscriber
PDCP DRB [Ericsson, Altiostar, Huawei] Total kbytes Ericsson, √ √ √ √ √
Volume DL DRB volume in downlink for PDCP Altiostar,
SDUs. For Huawei, the DL Data Huawei
Volume of each E-RAB contained in
the E-RAB Throughput Stat List of
each Huawei throughput periodic
statistical event is summed over
each composite call record to
provide uplink PDCP SDU data
volume.
PDCP DRB [Ericsson, Altiostar, Huawei] Total kbytes Ericsson, √ √ √ √ √
Volume UL DRB volume in uplink for PDCP Altiostar,
SDUs. For Huawei, the UL Data Huawei
Volume of each E-RAB contained in
the E-RAB Throughput Stat List of
each Huawei throughput periodic
statistical event is summed over
each composite call record to
provide uplink PDCP SDU data
volume.
PDCP
Throughput
Mean PDCP DRB [Ericsson] Mean DL throughput for kbps Ericsson √ √ √ √ √
Throughput DL PDCP DRB
Mean PDCP DRB [Ericsson] Mean UL throughput for kbps Ericsson √ √ √ √ √
Throughput UL PDCP DRB

992-0608-08 Rev. 001

Explorer Subscriber
Mean PDCP [Huawei] Total number of PDCP kbps Huawei √ √ √ √ √
Throughput DL SDU bytes received in the downlink
over all E-RABs divided by the
the selected calls. The number of
downlink PDCP SDU bytes is
accumulated over DL Data Volume
of the E-RAB Throughput Stat List
entry for each E-RAB for every
Huawei throughput periodic
statistical event received. The
collection period of each Huawei
throughput periodic statistical event
is determined by taking the largest
collection period among the
Throughput Stat List DL Data
Transmission Time entries for the
E-RABs. It is assumed that the
downlink PDCP SDU byte counts are
reset for each E-RAB at the onset of
the each collection period.

992-0608-08 Rev. 001

Explorer Subscriber
Mean PDCP [Huawei] Total number of PDCP kbps Huawei √ √ √ √ √
Throughput UL SDU bytes received in the uplink
over all E-RABs divided by the
the selected calls. The number of
uplink PDCP SDU bytes is
accumulated over UL Data Volume
of the E-RAB Throughput Stat List
entry for each E-RAB for every
Huawei throughput periodic
statistical event received. The
collection period of each Huawei
throughput periodic statistical event
is determined by taking the largest
collection period among the
Throughput Stat List UL Data
Transmission Time entries for the
E-RABs. It is assumed that the
uplink PDCP SDU byte counts are
reset for each E-RAB at the onset of
UE Environment
Indoor RCs
Indoor RCs Count of Radio Connections # All √ √ √ √ √
identified as Indoor
Indoor Percentage of Radio Connections % All √ √ √ √ √
Percentage identified as indoor

992-0608-08 Rev. 001

Explorer Subscriber
Outdoor RCs
Outdoor Count of Radio Connections # All √ √ √ √ √
Stationary RCs identified as outdoor stationary
Outdoor Percentage of Radio Connections % All √ √ √ √ √
Stationary identified as outdoor stationary
Percentage
Mobile RCs
Mobile RCs Count of Radio Connections # All √ √ √ √ √
identified as mobile
Mobile Percentage of Radio Connections % All √ √ √ √ √
Percentage identified as mobile
Connections Number of connections # Ericsson √
Best Server Cell Cells identified by ECGI are ranked Cell ID All √
by the highest total RSRP of the
serving cell and up to six neighbor
cells for all calls ending inside the
bin. The value for the bin is the PCI
of the best cell by this ranking. Each
PCI is assigned a color on the map.
Move the mouse over a bin to see
the PCI and other information about
the best cell for that bin.
Best Server Cell The Power-weighted mean RSRP of dBm All √
RSRP the best server using the ranking
according to "Best Server Cell [PCI]"

992-0608-08 Rev. 001

Explorer Subscriber
Best Server Cell Arithmetic mean of the RSRQ of the dB All √
RSRQ best server
2nd Best Server ECGI of the cell determined to be Cell ID All √
Cell the second best by RSRP
2nd Best Server Power mean of the RSRP of the dBm All √
Cell RSRP second best server
2nd Best Server Arithmetic mean of the RSRQ of the dB All √
Cell RSRQ second best server
3rd Best Server ECGI of the cell determined to be Cell ID All √
Cell the third best by RSRP
3rd Best Server Power mean of the RSRP of the third dBm All √
Cell RSRP best server
3rd Best Server Arithmetic mean of the RSRQ of the dB All √
Cell RSRQ third best server
4th Best Server ECGI of the cell determined to be Cell ID All √
Cell the fourth best by RSRP
4th Best Server Power mean of the RSRP of the dBm All √
Cell RSRP fourth best server
4th Best Server Arithmetic mean of the RSRQ of the dB All √
Cell RSRQ fourth best server
Cell the fifth best by RSRP
5th Best Server Power mean of the RSRP of the fifth dBm All √

992-0608-08 Rev. 001

Explorer Subscriber
Cell RSRQ fifth best server
Cell the sixth best by RSRP
6th Best Server Power mean of the RSRP of the sixth dBm All √
Cell RSRQ sixth best server
Cell the seventh best by RSRP
7th Best Server Power mean of the RSRP of the dBm All √
Cell RSRP seventh best server
Cell RSRQ seventh best server
Best Server Cell ECGI of the serving cell with the Cell ID All √
By Occurrence most occurrences
Average Average geolocation accuracy of all All √
Geolocation calls
Confidence
RLF Reports
RLF Reports Number of RLF reports received # Ericsson, √ √
Nokia,
Samsung,
Huawei,
ZTE,
Altiostar

992-0608-08 Rev. 001

Explorer Subscriber
RACH Failure Number of RLF reports with RLF # Ericsson, √ √
Count cause 'RACH Failure'. Nokia,
Samsung,
Huawei,
ZTE,
Altiostar
RLC MaxNum Number of RLF reports with RLF # Ericsson, √ √
Retransmission cause 'RLC MaxNumRetx'. Nokia,
Count Samsung,
Huawei,
ZTE,
Altiostar
RLF T310 Expiry Number of RLF reports with RLF # Ericsson, √ √
Count cause 't310 Expiry'. Nokia,
Samsung,
Huawei,
ZTE,
Altiostar
RLF T312 Expiry Number of RLF reports with RLF # Ericsson, √ √
Count cause 't312 Expiry'. Nokia,
Samsung,
Huawei,
ZTE,
Altiostar

992-0608-08 Rev. 001

Explorer Subscriber
RLF Offended Average RSRP for RLF offended cell dBm Ericsson, √ √
RSRP Nokia,
Samsung,
Huawei,
ZTE,
Altiostar
RLF Offended Average RSRQ for RLF offended cell dB Ericsson, √ √
RSRQ Nokia,
Samsung,
Huawei,
ZTE,
Altiostar
5G EN-DC
SgNB Addition Number of 5G EN-DC SgNB # Ericsson, √ √ √ √ √
Attempts addition attempts Samsung,
Huawei,
Alcatel-
Lucent
SgNB Addition Number of 5G EN-DC SgNB # Ericsson, √ √ √ √ √
Failures addition failures Samsung,
Huawei,
Alcatel-
Lucent

992-0608-08 Rev. 001

Explorer Subscriber
SgNB Addition 5G EN-DC addition failures divided % Ericsson, √ √ √ √ √
Failure Rate by addition attempts Samsung,
Huawei,
Alcatel-
Lucent
SgNB Drops Number of 5G EN-DC drops # Ericsson, √ √ √ √ √
Samsung,
Huawei,
Alcatel-
Lucent
SgNB Drop Rate 5G EN-DC drops divided by number % Ericsson, √ √ √ √ √
of established SgNB connections Samsung,
Huawei,
Alcatel-
Lucent
Downlink Downlink data volume transmitted kb Ericsson, √ √ √ √ √
Volume by SgNB during EN-DC from X2 or Samsung,
S1 Secondary RAT Usage Report Huawei
Uplink Volume Uplink data volume received by kb Ericsson, √ √ √ √ √
SgNB during EN-DC from X2 or S1 Samsung,
Secondary RAT Usage Report Huawei
Duration Rate 5G EN-DC duration divided by total % Ericsson, √ √ √ √ √
RRC duration Samsung,
Huawei,
Alcatel-
Lucent

992-0608-08 Rev. 001

Explorer Subscriber
SgNB Change Number of 5G EN-DC SgNB change # Ericsson, √ √ √ √ √
Attempts attempts Samsung,
Huawei
Failures failures Samsung,
Huawei
Successes successes Samsung,
Huawei
SgNB Change 5G EN-DC SgNB change failures % Ericsson, √ √ √ √ √
Failure Rate divided by SgNB change attempts Samsung,
Huawei
SgNB Number of 5G EN-DC SgNB # Ericsson, √ √ √ √ √
Modification modification attempts Samsung,
Attempts Huawei
Modification modification failures Samsung,
Failures Huawei
Modification modification successes Samsung,
Successes Huawei
SgNB 5G EN-DC SgNB modification % Ericsson, √ √ √ √ √
Modification failures divided by SgNB Samsung,
Failure Rate modification attempts Huawei

992-0608-08 Rev. 001

Explorer Subscriber
NR RSRP Mean RSRP of last 5G EN-DC PSCell dBm Ericsson, √ √ √ √ √
Samsung,
Huawei
NR RSRQ Mean RSRQ of last 5G EN-DC PSCell dB Ericsson, √ √ √ √ √
Samsung,
Huawei
NR DL SINR Mean downlink SINR of last 5G EN- dB Ericsson, √ √ √ √ √
DC PSCell Samsung,
Huawei
Maximum Maximum number of carrier # Ericsson, √ √ √ √ √
Number of components, including LTE PCC, Samsung,
Carrier SCC, and 5G EN-DC Huawei,
Components Alcatel-
Lucent
Average Time averaged number of carrier # Ericsson, √ √ √ √ √
Number of components, including LTE PCC, Samsung,
Carrier SCC, and 5G EN-DC Huawei,
Components Alcatel-
Lucent

992-0608-08 Rev. 001
A.2 Common LTE Call Attributes / LSR Fields: Descriptions and Units
The following Call Attributes and LSR Fields are available in the Common LTE Call Table:
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 LTE Enumerated Values to see the enumerated values when LSR Unit is shown as "enum."
Nokia PCMD is referred to as Alcatel-Lucent in this section.
Attribute Vendors LSR LSR LSR Range Description

Datatype Units
End Latitude All double degrees 90.000000..-90.000000 Latitude of the UE end start location determined by TrueCall. Not set
[degrees] for NB-IoT calls.
End Longitude All double degrees 180.000000..-180.000000 Longitude of the UE call end location determined by TrueCall. Not set
[degrees] for NB-IoT calls.

992-0608-08 Rev. 001

Datatype Units
Confidence All string enum N/A TrueCall provides four 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. 'MDT
GPS' is the location from MDT report. It's only reported in LTE. 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. NB-IoT calls are always set to
indicate unknown confidence.
Environment All string enum N/A Indicates whether the call was determined to be indoor, mobile or
outdoor stationary. Not set for NB-IoT calls.
IMSI All string no units 000000000000000..999999999999 International Mobile Subscriber Identity of the UE
IMEI All string no units 00000000-000000-0..99999999- International Mobile Equipment Identity (IMEI) of the UE. Type
999999-9 Allocation Code (TAC)-Serial Number (SNR)-Check digit
SVN All int64 no units 00..99 Software Version Number in IMEISV
Roaming Group All string no units N/A Service Provider of the UE as determined from the IMSI
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

992-0608-08 Rev. 001

Datatype Units
Service Type All string enum N/A Service Type is set to 'Voice and Data' to indicate the presence of QCI 1
eRAB, otherwise to 'Data Only'.
Trace ID Huawei, int64 no units 0..18446744073709551615 [Huawei, Samsung, ZTE, Ericsson, Nokia, Altiostar] Contains the Cell
Samsung, Trace Recording Reference of the Cell Trace instance upon which the
ZTE, call record is based. In the case of Samsung, the Trace Recording
Ericsson, Session Reference taken from CSL, VSE TA Value, VSE Periodic RF
Nokia, Information, VSE Throughput Information, or RRC, S1AP or X2AP Trace
Altiostar Information is used as Call ID. In the case of Altiostar, the Trace Id is
taken as the complete value of the TRACE_REFERENCE_ID of the TRACE
EVENT HEADER. The least significant two bytes of the TRACE_
REFERENCE_ID is coded with the Trace Recording Session Reference of
the cell trace session.
Start m-TMSI All int64 no units 0..4294967295 MME Temporary Mobile Subscriber Identity (m-TMSI) from RRC
Connection Request or S1 Initial UE Message. In the case of Samsung,
when otherwise not available from 3GPP message events, start m-
TMSI may be taken from the CSL.
Start Time All time no units 1/1/1970 00:00..12/31/9999 23:59 Start time for the Call, taken from the timestamp of the earliest Cell
Trace event
Duration All duration no units 0..99999999:59 Duration of the RRC connection, calculated as the sum of the durations
of the fragments. For ALU LTE, call duration is the difference between
the first start time and last end time in all fragments. When used in a
fragment, the duration is calculated as the difference between the
timestamps of the first and last Cell Trace events received. For
Samsung LTE, the duration of a fragment or call is calculated based on
the later of the two timestamps, the timestamp of the last ASN.1 event
received or the timestamp of the Disconnection Information of the CSL
associated with the fragment or call.

992-0608-08 Rev. 001

Datatype Units
End Time All time no units 1/1/1970 00:00..12/31/9999 23:59 End time for the Call, taken from the timestamp of the last Cell Trace
event. In the case of Samsung, the end time of the call or fragment is
taken as the later of the two timestamps, the timestamp of the last
ASN.1 event or the timestamp of the Disconnection Information of the
CSL.
Start Type All string no units N/A Provides information on how the RRC Connection started at the serving
cell
End Type All string enum N/A Provides information on how the RRC Connection ended at the serving
cell

992-0608-08 Rev. 001

Datatype Units
Final Disposition All string enum N/A Final Disposition of the RRC Connection at the serving cell is
determined as follows: (1) If an RRC Connection Request message was
received for the call and the RRC connection fails to be established,
then Final Disposition is set to indicate Failed Attempt; (2) If an NB-IoT
RRC Connection Resume was received for the call and the RRC
connection fails to be resumed or established, then Final Disposition is
set to indicate Failed Attempt; (3) Otherwise, if an RRC Connection
Request message was received for the call and the S1AP signaling
connection to the MME is unsuccessful, then Final Disposition is set to
indicate Failed Attempt; (4) Otherwise, if the trace starts as a result of
the RRC Connection Re-establishment procedure, and the RRC
Connection Re-establishment procedure fails, then Final Disposition is
set to indicate Failed Reestablishment; (5) Otherwise, if a successful
outgoing X2 Handover or outgoing S1 Handover take place, then Final
Disposition is set to indicate Outgoing Handover; (6) Otherwise, if an
RRC Connection Release containing both Redirected Absolute Radio
Frequency Channel Number and Redirected Radio Access Technology
is received, then Final Disposition is set to indicate Redirection; (7)
Otherwise, if an S1AP Release Cause is received, and the S1AP Release
Cause indicates Radio Access Layer Cause User Inactivity, Load
Balancing Tracking Area Update Required or CS Fall Back Triggered or
UE Not Available For PS Service, then the Final Disposition is set to
indicate Normal Release; (8) Otherwise, if an S1AP Release Cause is
received, and the S1AP Release Cause indicates Radio Access Layer
Cause inter-Radio Access Technology Redirection, Redirection towards
1xRTT or Handover Desirable for Radio Reason, then the Final
Disposition is set to indicate Redirection; (9) Otherwise, if an S1AP
Release Cause is received, and the S1AP Release Cause indicates
Radio Access Layer Cause Successful Handover, then the Final
Disposition is set to indicate Outgoing Handover; (10) Otherwise, if an
S1AP Release Cause is received, and the S1AP Release Cause indicates

992-0608-08 Rev. 001

Datatype Units
Non-Stratum Access Layer Cause Normal Release or Detach, then the
Final Disposition is set to indicate Normal Release; (11) Otherwise, if an
S1AP Release Cause is received, and the S1AP Release Cause indicates
Non-Stratum Access Layer Cause Authentication Failure, then the Final
Disposition is set to indicate Failed Attempt; (12) Otherwise, if an S1AP
Release Cause is received other than those specified earlier, then the
Final Disposition is set to indicate Dropped Connection; (13) Otherwise,
if an RRC Connection Release is received with release cause indicating
RRC suspend, then the Final Disposition is set to indicate Normal
Release; (14) Otherwise the Final Disposition is set to indicate
Unknown.
Start Cell All string no units 0..999999268435455 Cell Id or cell name of the first serving cell from the Cell Trace event.
When otherwise not set from 3GPP events, in the case of Samsung, the
Start Cell may be determined from Connection Information of the first
associated CSL.
Start eNB All int64 no units 0..1048575 eNB ID or eNB name of the first serving cell from the Cell Trace event.
When otherwise not set from 3GPP events, in the case of Samsung, the
Start eNB may be determined from Connection Information of the first
associated CSL.
Start PCI All int64 no units 0..503 Physical Cell Identity of the first serving cell. In the case of Samsung,
the Start PCI may be determined from Connection Information of the
first associated CSL.
Start EARFCN DL All int64 no units 0..262143 Downlink E-UTRAN Absolute Radio Frequency Channel Number of the
first serving cell
Start GUMMEI All string no units 111.00.000.000..999.999.65535.255 Globally Unique MME Identifier of the first serving MME taken from the
Cell Trace event
Start Tracking All int64 no units 0..65535 Tracking Area Code from the S1 Initial UE Message. In the case of
Area Code Altiostar, Tracking Area Code may also be read from the VSE_TAI
event.

992-0608-08 Rev. 001

Datatype Units
Start MME UE All int64 no units 0..4294967295 In the case of Samsung, when MME S1AP ID is not available from 3GPP
S1AP ID message events, Start MME S1AP ID shall be read from the CSL. In the
case of Altiostar, when MME S1AP ID may be read from the VSE_MME_
UE_S1AP_ID event.
Start eNB UE All int64 no units 0..16777215 In the case of Samsung, when eNB S1AP ID is not available from 3GPP
S1AP ID message events, Start eNB S1AP ID shall be read from the CSL. In the
case of Altiostar, when eNB S1AP ID may be read from the VSE_ENB_
UE_S1AP_ID event.
End Cell All string no units 0..999999268435455 ECGI or cell name of the last serving cell from the Cell Trace event.
When otherwise not available, in the case of Samsung LTE, the end
ECGI may be taken from Disconnection Information of the CSL.
End eNB All int64 no units 0..1048575 eNB ID or eNB name of the last serving cell from the Cell Trace event.
When otherwise not available, in the case of Samsung LTE, the end
eNB ID or eNB name may be derived from the CGI taken from
Disconnection Information of the CSL.
End PCI All int64 no units 0..503 Physical Cell Identity of the last serving cell. In the case of Samsung
LTE, the end PCI may be read from the Disconnection Information of
the last CSL associated with the call.
End EARFCN DL All int64 no units 0..262143 Downlink E-UTRAN Absolute Radio Frequency Channel Number of the
last serving cell
End MME UE All int64 no units 0..4294967295 MME UE S1AP ID from the last known S1AP message event. In the case
S1AP ID of Samsung, End MME UE S1AP ID in the fragment may be set based
on the content of CSL. In the case of Altiostar, End MME UE S1AP ID in
the fragment may be set based on the content of the VSE_MME_UE_
S1AP_ID event. The End MME UE S1AP ID of the call will be based on
the End MME UE S1AP ID of the last fragment of the call.

992-0608-08 Rev. 001

Datatype Units
End eNB UE All int64 no units 0..16777215 eNB UE S1AP ID from the last known S1AP message event. In the case
S1AP ID of Samsung, End eNB UE S1AP ID in the fragment may be set based on
the content of CSL. In the case of Altiostar, End eNB UE S1AP ID in the
fragment may be set based on the content of the VSE_ENB_UE_S1AP_
ID event. The End eNB UE S1AP ID of the call will be based on the End
eNB UE S1AP ID of the last fragment of the call.
Establishment All string enum N/A Establishment Cause based on the RRC Connection Request or NB-IoT
Cause RRC Connection Resume message received in the Cell Trace session.
RRC Setup All string enum N/A Indicates success or failure of the RRC connection setup procedure in a
Result new RRC connection, including resumed NB-IoT RRC connections.
Setup Time All duration no units 0..99999999:59 Calculated as the time difference between RRC Connection Request
and RRC Connection Setup Complete, or between the NB-IoT RRC
Resume Request and the NB-IoT RRC Connection Resume Complete or
NB-IoT RRC Connection Setup Complete.
S1 Setup Result All string enum N/A Indicates success (reception of S1 Initial Context Setup Response) or
failure (reception of S1 Initial Context Setup Failure) of the S1AP UE
Context Setup procedure
RRC Release Ericsson, string enum N/A [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Release Cause from
Cause Nokia, RRC Connection Release message
Samsung,
Huawei,
ZTE,
Altiostar
S1 Release Ericsson, string enum N/A [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] S1AP Release
Cause Nokia, Cause taken from the UE Context Release or Initial Context Setup
Samsung, Failure messages
Huawei,
ZTE,
Altiostar

992-0608-08 Rev. 001

Datatype Units
RSRP [dBm] All double dBm -141..-44 Reference Signal Received Power (RSRP) of the serving cell from the
last available Measurement Report. In the case of Samsung, when no
Measurement Report is available, RSRP may be taken from RF
Information contained in the CSL.
RSRQ [dB] All double dB -20..-3 Reference Signal Received Quality (RSRQ) of the serving cell from the
last available Measurement Report. In the case of Samsung, when no
Measurement Report is available, RSRQ may be taken from RF
Information contained in the CSL.
DL SINR [dB] All double dB -23.5..40 DL SINR of the serving cell from last Measurement Report

992-0608-08 Rev. 001

Datatype Units
Start Timing All double meters 0..240405 For vendors other than Samsung or Altiostar, Start Timing Advance of
Advance each fragment is set to the earliest timing advance of the fragment.
[Meters/Miles] Start timing advance of the call is the start timing advance of the first
fragment of the call with start timing advance. Not set for NB-IoT calls.
[Samsung] For a fragment, if both periodic MAC and Type 1 timing
advance are available, the earliest Type 1 timing advance is taken as
start timing advance for the fragment if it is earlier, or no later than the
value of the Type 1 timer advance timer, than the earliest periodic
MAC timing advance, or else earliest periodic MAC timing advance is
used as start timing advance; otherwise, if Type 1 timing advance is
available, but periodic MAC timing advance is not, then the earliest
Type 1 timing advance is taken as start timing advance; otherwise, if
periodic MAC timing advance is available, but Type 1 timing advance is
not, then the earliest MAC timing advance is taken as start timing
advance; otherwise, if connection timing advance is present in the CSL,
then start timing advance is taken as start timing advance. The start
timing advance of the call is take as the start timing advance of the first
constituent fragment of the call, and if start timing advance is N.A. in
the first fragment, it will also be N.A. in the call record. The value of the
Type 1 timing advance timer is configurable with a default value of 6
seconds. Values of 0 for MAC timing advance or CSL timing advance
are converted to 19 meters. [Altiostar] For a fragment, if both periodic
MAC and Type 1 timing advance are available, the earliest Type 1
timing advance is taken as start timing advance for the fragment if it is
earlier, or no later than the value of the Type 1 timer advance timer,
than the earliest periodic MAC timing advance, or else earliest periodic
MAC timing advance is used as start timing advance; otherwise, if Type
1 timing advance is available, but periodic MAC timing advance is not,
then the earliest Type 1 timing advance is taken as start timing
advance; otherwise, if periodic MAC timing advance is available, but
Type 1 timing advance is not, then the earliest MAC timing advance is

992-0608-08 Rev. 001

Datatype Units
taken as start timing advance; The start timing advance of the call is
take as the start timing advance of the first constituent fragment of the
call, and if start timing advance is N.A. in the first fragment, it will also
be N.A. in the call record. The value of the Type 1 timing advance timer
is configurable with a default value of 6 seconds. MAC TA of 0 is
converted to 19 meters in the case of Altiostar. [Huawei] Start Timing
Advance can be read from any of the following events: UE periodic
radio link MR, UE periodic radio link MR MDT, UE Period TA and UE
Period TA MDT.

992-0608-08 Rev. 001

Datatype Units
End Timing All double meters 0..240405 For vendors other than Samsung or Altiostar, End Timing Advance of a
Advance fragment is set to the last timing advance of the fragment. End timing
[Meters/Miles] advance of a call is set to the end timing advance of the last fragment
with end timing advance. Not set for NB-IoT calls. [Samsung] In the
case of a Samsung fragment, if Type 1 timing advance (Tadv) and
Disconnect CSL timing advance are present in the fragment, end
timing advance is set to the last Tadv if it is later than, or no earlier
than the value of the Type 1 timer advance timer from, the Disconnect
CSL timing advance, or else end timing advance is taken from
Disconnect CSL timing advance; otherwise, if both Tadv and periodic
MAC timing advance are present in the fragment, end timing advance
is set to the last Tadv if it is either later than, or no earlier than the
value of the last Type 1 timer advance timer from, the last periodic
MAC timing advance, or else is set to the last periodic MAC timing
advance; otherwise, if Disconnect CSL timing advance is present in the
fragment, it is taken as end timing advance for the fragment;
otherwise, if Tadv timing advance is present in the fragment, the last
Tadv timing advance received is taken as end timing advance;
otherwise, if periodic MAC timing advance is present in the fragment, it
is taken as end timing advance for the fragment; otherwise, end timing
advance is not set. Values of 0 for MAC timing advance or CSL timing
advance are converted to 19 meters. [Altiostar] If both Tadv and
periodic MAC timing advance are present in the fragment, end timing
advance is set to the last Tadv if it is either later than, or no earlier than
the value of the Type 1 timer advance timer from the last periodic MAC
timing advance, or else is set to the last periodic MAC timing advance;
otherwise, if Tadv timing advance is present in the fragment, the last
Tadv timing advance received is taken as end timing advance;
otherwise, if periodic MAC timing advance is present in the fragment,
the last timing advance received is taken as end timing advance for the

992-0608-08 Rev. 001

Datatype Units
fragment; otherwise, end timing advance is not set. End timing
advance of a call is set to the end timing advance of the last fragment.
Note: Type 1 timing advance (Tadv), Samsung's and Altiostar's
implementation of TADV described in TS 36.133, Section 10.3.1 Report
mapping, provides 2Ts resolution for timing advance less than or equal
to 4096Ts, and 8Ts resolution for timing advance greater than 4096Ts.
MAC timing advance, the timing advance utilized in MAC timing
advance commands, is described in TS 36.213, section 4.2.3, and
provides 16Ts granularity. The value of the Type 1 timing advance
timer is configurable with a default value of 6 seconds. MAC TA of 0 is
converted to 19 meters in the case of Altiostar. [Huawei] End Timing
Advance can be read from any of the following events: UE periodic
radio link MR, UE periodic radio link MR MDT, UE Period TA and UE
Period TA MDT.
Start Timing All string no units 0..999999268435455 Cell Id or cell name of the first timing advance cell. This will generally
Advance Cell be equal to the start cell, but when the earliest timing advance comes
from a cell other than the start cell, the start timing advance cell will
differ. Not set for NB-IoT calls.
End Timing All string no units 0..999999268435455 Cell Id or cell name of the last timing advance cell. This will generally
Advance Cell be equal to the end cell, but when the last timing advance comes from
a cell other than the end cell, the end timing advance cell will differ. Not
set for NB-IoT calls.

992-0608-08 Rev. 001

Datatype Units
UE Category All string enum N/A Downlink UE Category includes values for WB-E-UTRAN and NB-IoT.
When more than one UE Category is available, a prioritization rule is
defined which prioritizes the most recently defined UE Categories over
older UE Categories. When Downlink UE Category is not available for a
WB-E-UTRAN call, the pre-Release 12 UE Category is used to
determine the UE Category. For an NB-IoT call, the UE Category
indicates NB2 if indication of NB2 is received, or NB1 if NB1 is
indicated but NB2 is not, or is not set if neither indication is received. In
the case of Samsung only, when UE Category is not available from
standard 3GPP signaling, UE Category may be taken from the DL
Category of the CSL. In the case of Alcatel-Lucent PCMD, UE Category
is derived from the 'UE Category' (field number 223) of the PCMD
rather than from 3GPP signaling. In the case of Ericsson only, when UE
Category is not available from standard 3GPP signaling, UE Category
may be derived from EVENT_PARAM_UE_CATEGORY_FLEX of the
INTERNAL_PROC_UE_CTXT_RELEASE event.
Radio Type All string enum N/A E-UTRAN Radio Type, if available, is set to indicate either WB-E-UTRAN,
the part of E-UTRAN that excludes NB-IoT, or NB-IoT (Narrowband
Internet of Things). NB-IoT allows access to network services via E-
UTRAN with channel bandwidth limited to 180 kHz, or 5G EN-DC (E-
UTRAN NE Dual Connectivity).
LTE PLMN-ID All string no units 0..FFFFFF PLMN-ID of LTE start cell.

992-0608-08 Rev. 001

Datatype Units
EPS Ericsson, string enum N/A [Ericsson, Huawei, Samsung, Nokia] CIoT (Cellular Internet of Things)
Optimization Huawei, EPS (Evolved Packet System) Optimization. Although other CIoT
Samsung, Optimizations are supported, and more than one optimization may be
Nokia utilized in the course of a connection, this call table attribute is limited
to User Plane (UP) and Control Plane (CP) CIoT EPS Optimizations. This
attribute Indicates 'UP CIot' if UP CIoT EPS Optimization is used during
the call, or else indicates 'CP CIoT' if CP CIoT EPS Optimization is used
during the call, or else the protobuf field is not included when there is
no indication of either UP CIoT EPS Optimization nor CP CIoT EPS
Optimization.
RRC Re- All int64 # 0..9223372036854775807 Number of RRC Connection Reestablishment Request messages during
establishment the session
Attempts
RRC Re- All int64 # 0..9223372036854775807 Number of RRC Connection Reestablishment Complete messages
establishment during the session
Successes
RRC Re- All int64 # 0..9223372036854775807 Number of RRC Connection Reestablishment Reject messages during
establishment the session
Failures
Intra-frequency All int64 # 0..9223372036854775807 Number of RRC Connection Reconfiguration messages containing
Intra-eNB HO Mobility Control Info IE without target carrier frequency when neither
Attempts X2 nor S1 outgoing handover is underway
Intra-frequency All int64 # 0..9223372036854775807 Number of RRC Connection Reestablishment Request messages
Intra-eNB HO received at source cell when intra-eNB intra-frequency handover is
Failures underway
Inter-frequency All int64 # 0..9223372036854775807 Number of RRC Connection Reconfiguration messages containing
Intra-eNB HO Mobility Control Info IE with target carrier frequency when neither X2
Attempts nor S1 outgoing handover is underway

992-0608-08 Rev. 001

Datatype Units
Inter-frequency All int64 # 0..9223372036854775807 Number of RRC Connection Reestablishment Request messages
Intra-eNB HO received at source cell when intra-eNB inter-frequency handover is
Failures underway
Intra-frequency All int64 # 0..9223372036854775807 Number of outgoing X2AP Handover Request messages for which
X2 HO Prep there is no related RRC Connection Reconfiguration message that
Attempts indicates inter-frequency handover. This count includes inter-
frequency handover preparation attempts that fail
Intra-frequency All int64 # 0..9223372036854775807 Number of incoming X2AP Handover Preparation Failure messages
X2 HO Prep and outgoing X2AP Handover Cancel messages that occur before the
Failures handover execution phase has been entered. Note that both inter-
frequency and intra-frequency X2 handover preparation failure events
are included in this count.
Intra-frequency All int64 # 0..9223372036854775807 Intra-frequency X2 Handover Execution Attempts
X2 HO Exec
Attempts
Intra-frequency All int64 # 0..9223372036854775807 Number of outgoing X2AP Handover Cancel messages and RRC
X2 HO Exec Connection Reestablishment Request messages received after an RRC
Failures Connection Reconfiguration message event that indicates intra-
frequency handover and is related to an ongoing X2 handover
Intra-frequency All int64 # 0..9223372036854775807 Intra-frequency X2 Handover Execution Successes
X2 HO Exec
Successes
Inter-frequency All int64 # 0..9223372036854775807 Number of outgoing X2AP Handover Request messages for which
X2 HO Prep there is a related RRC Connection Reconfiguration message that
Attempts indicates inter-frequency handover and the handover preparation
succeeded
Inter-frequency All int64 # 0..9223372036854775807 Inter-frequency X2 Handover Preparation Failures
X2 HO Prep
Failures

992-0608-08 Rev. 001

Datatype Units
Inter-frequency All int64 # 0..9223372036854775807 Inter-frequency X2 Handover Execution Attempts
X2 HO Exec
Attempts
Inter-frequency All int64 # 0..9223372036854775807 Number of outgoing X2AP Handover Cancel message and RRC
X2 HO Exec Connection Reestablishment Request messages received after an RRC
Failures Connection Reconfiguration message event that indicates inter-
frequency handover and is related to an ongoing X2 handover
Inter-frequency All int64 # 0..9223372036854775807 Inter-frequency X2 Handover Execution Successes
X2 HO Exec
Successes
Intra-frequency All int64 # 0..9223372036854775807 Number of S1AP Handover Required messages for which there is no
S1 HO Prep related RRC Connection Reconfiguration message event indicating
Attempts inter-frequency handover. This count includes inter-frequency
handover preparation attempts that fail as well as all intra-frequency
preparation attempts regardless of success or failure
Intra-frequency All int64 # 0..9223372036854775807 Number of S1AP Handover Preparation Failure messages and S1AP
S1 HO Prep Handover Cancel messages that occur before the handover execution
Failures phase has been entered. Note that both inter-frequency and intra-
frequency S1 handover preparation failure events are included in this
count.
Intra-frequency All int64 # 0..9223372036854775807 Number of RRC Connection Reestablishment Request messages
S1 HO Exec received after RRC Connection Reconfiguration message event that
Failures includes intra-frequency handover indication and that is related to an
ongoing outgoing S1 handover procedure
Intra-frequency All int64 # 0..9223372036854775807 Intra-frequency S1 Handover Execution Successes
S1 HO Exec
Successes

992-0608-08 Rev. 001

Datatype Units
Inter-frequency All int64 # 0..9223372036854775807 Number of S1AP Handover Required messages for which there is a
S1 HO Prep related RRC Connection Reconfiguration message event indicating
Attempts inter-frequency handover and the handover preparation succeeded
Inter-frequency All int64 # 0..9223372036854775807 Inter-frequency S1 Handover Preparation Failures
S1 HO Prep
Failures
Inter-frequency All int64 # 0..9223372036854775807 Number of RRC Connection Reestablishment Request messages
S1 HO Exec received after RRC Connection Reconfiguration message event that
Failures includes inter-frequency handover indication and that is related to an
ongoing outgoing S1 handover procedure
Inter-frequency All int64 # 0..9223372036854775807 Inter-frequency S1 Handover Execution Successes
S1 HO Exec
Successes
IRAT HO Ericsson, int64 # 0..9223372036854775807 [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Number of S1AP
Attempts Nokia, Handover Required messages with Handover Type indicating LTE to
Samsung, UTRAN or LTE to GERAN handover added to the number of S1AP Uplink
Huawei, CDMA2000 Tunneling messages with CDMA2000 RAT Type indication
ZTE, 1xRTT or HRPD
Altiostar
Handover Out to Ericsson, int64 # 0..9223372036854775807 [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Number of S1AP
2G Nokia, Handover Required messages with Handover Type indicating LTE to
Samsung, GERAN handover added to the number of S1AP Uplink CDMA2000
Huawei, Tunneling messages that include CDMA2000 RAT Type 1xRTT
ZTE,
Altiostar

992-0608-08 Rev. 001

Datatype Units
Handover Out to Ericsson, int64 # 0..9223372036854775807 [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Number of S1AP
3G Nokia, Handover Required messages with Handover Type indicating LTE to
Samsung, UTRAN handover added to the number of S1AP Uplink CDMA2000
Huawei, Tunneling messages with CDMA2000 RAT Type HRPD indication
ZTE,
Altiostar
Handover Cause Ericsson, string enum N/A [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Set based on Cause
Nokia, IE of the last X2AP Handover Request received or sent, last S1AP
Samsung, Handover Required sent or last S1AP Handover Request received
Huawei,
ZTE,
Altiostar
Last HO Source Ericsson, string no units 0..999999268435455 [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] ECGI or cell name of
Cell Nokia, source cell of last handover.
Samsung,
Huawei,
ZTE,
Altiostar
Last HO Target All string no units 0..999999268435455 ECGI or cell name of target cell of last handover.
Cell
Last HO Type Ericsson, string enum N/A [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Handover type of
Nokia, last handover
Samsung,
Huawei,
ZTE,
Altiostar

992-0608-08 Rev. 001

Datatype Units
Last HO Ericsson, string enum N/A [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Indicates the result
Disposition Nokia, of the last attempted outgoing handover. Indicates success or the
Samsung, reason why the handover was not completed
Huawei,
ZTE,
Altiostar
S1 Outgoing HO Ericsson, string enum N/A [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Value of the last
Type Nokia, S1AP Handover Type taken from the S1AP Handover Required
Samsung, message
Huawei,
ZTE,
Altiostar
S1 Incoming HO Ericsson, string enum N/A [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Value of the last
Type Nokia, S1AP Handover Type taken from the S1AP Handover Request message
Samsung,
Huawei,
ZTE,
Altiostar
Mobility from E- Ericsson, string enum N/A [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Purpose from the
UTRA Purpose Nokia, Mobility from E-UTRA Command message
Samsung,
Huawei,
ZTE,
Altiostar
Redirected Ericsson, int64 no units 0..262143 [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] ARFCN or Carrier
ARFCN Nokia, Frequency derived from the RRC Redirected Carrier Information of the
Samsung, RRC Connection Release message
Huawei,
ZTE,
Altiostar

992-0608-08 Rev. 001

Datatype Units
Redirected All string enum N/A Radio Access Technology derived from RRC Redirected Carrier
System Information of the RRC Connection Release message
VoLTE eRAB All duration no units 0..99999999:59 Accumulation of QCI1 eRAB durations calculated from time of eRAB
Duration setup as a result of S1 Initial Context Setup, S1 eRAB Setup, X2
Handover Preparation or S1 Handover Resource Allocation to eRAB
release as result of S1 eRAB Release, RRC connection release, or
outgoing handover
VoLTE eRAB All duration no units 1/1/1970 00:00..12/31/9999 23:59 Mean of all QCI1 eRAB setup times of new eRABs established as a
Setup Time result of the S1AP eRAB Setup and Initial Context Setup procedures as
well as existing eRABs established at target eNBs as a result of S1AP
Handover Resource Allocation and X2AP Handover Preparation
procedures
VoLTE eRAB All int64 # 0..9223372036854775807 Number of QCI1 eRAB setup attempts contained in S1 Initial Context
Attempts Setup Request and S1 eRAB Setup Request messages
VoLTE eRAB All int64 # 0..9223372036854775807 Number of QCI1 eRABs in the process of being setup when an S1 Initial
Failed Attempts Context Setup Failure message is received and the number of QCI1
eRABs in the process of being setup for which a S1 Initial Context Setup
Response or S1 eRAB Setup Response message is received that does
not include an established confirmation for the eRAB ID
VoLTE eRAB All int64 # 0..9223372036854775807 Number of VoLTE failed attempts with cause of X2 handover, S1
Failed Attempts handover, CSFB, and Redirection towards 1XRTT.
Due to Mobility
VoLTE eRAB All int64 # 0..9223372036854775807 Number of QCI1 eRABs in the active state for which explicit release is
Release requested in S1 eRAB Release Indication or S1 eRAB Release
Attempts Command message, or which are implicitly released by being active at
the time of RRC connection release including Normal Release, Dropped
Connection and Redirection

992-0608-08 Rev. 001

Datatype Units
VoLTE eRAB All int64 # 0..9223372036854775807 Number of QCI 1 eRABs not admitted during outgoing X2 or S1
Drops handover + number of active QCI1 eRABs released by S1 eRAB Release
Indication or S1 eRAB Release Command with S1 cause indicating
connection or eRAB drop + number of QCI1 eRABs active at the time of
a dropped connection
Video Call eRAB All duration no units 0..99999999:59 Total duration of QCI=2 E-RAB duration in one fragment or call.
Duration
Video Call eRAB All duration no units 0..99999999:59 Mean setup time of QCI=2 E-RABs setup during one fragment. The
Setup Time mean setup time for a call is the mean of the mean setup times of the
constituent fragments.
Video Call eRAB All int64 # 0..9223372036854775807 Number of QCI=2 E-RAB setup attempts in one fragment or call.
Attempts
Video Call eRAB All int64 # 0..9223372036854775807 Number of QCI=2 E-RAB setup attempts that fail during one fragment
Failed Attempts or call.
Video Call eRAB All int64 # 0..9223372036854775807 Number of QCI=2 E-RABs released during one fragment or call,
Release including those dropped.
Attempts
Video Call eRAB All int64 # 0..9223372036854775807 Number of QCI=2 E-RAB dropped during one fragment or call, including
Drops those for which setup fails.
SRVCC All bool boolean True, False Set to true if an SRVCC (Single Radio Voice Call Continuity) Operation
Capability Possible indication is received in any of the following message types:
X2AP Handover Request, S1AP Handover Request or S1AP Initial
Context Setup Request
SRVCC HO All string enum N/A Set to the domain indicated if an SRVCC Handover indication is
Indication received in an S1AP Handover Required message

992-0608-08 Rev. 001

Datatype Units
QCI List All ints_t no units N/A The QCI list consists of the QCI of each eRAB that is successfully
established during the session including eRABs newly established and
eRABs admitted to the eNB as a result of incoming handover. In the
case of Samsung, the QCI list may be taken from the CSL when the
necessary 3GPP message cell trace events are not available.
ARP List All ints_t no units N/A The ARP list consists of the QCI of each eRAB that is successfully
established during the session including eRABs newly established and
eRABs admitted to the eNB as a result of incoming handover.
CSFB All bool boolean True, False Set to true if one of the following conditions is met and RRC Connection
Re-establishment procedure is not subsequently attempted at the eNB:
the connection is released with S1AP Cause "CS Fallback Triggered" or
"UE Not Available for PS Service"; an RRC Mobility From E-UTRA
Command message containing CSFB indication is received; an S1AP
Initial Context Setup Request is received with CS Fallback Indicator; an
S1AP UE Context Modification Request message with CS Fallback
Indicator; an HO From EUTRA Preparation Request to CDMA 2000 with
dual Rx TX Redirect Indicator
CSFB Type All string enum N/A CSFB Type of last CSFB attempt
CSFB Result All string enum N/A CSFB Result of last CSFB attempt
eRAB Setup All duration no units 0..99999999:59 Mean of all RAB setup times of new eRABs established as a result of
Time the S1AP eRAB Setup and Initial Context Setup procedures as well as
existing eRABs established at target eNBs as a result of S1AP
Handover Resource Allocation and X2AP Handover Preparation
procedures
eRAB Attempts All int64 # 0..9223372036854775807 Number of eRAB setup attempts contained in S1 Initial Context Setup
Request and S1 eRAB Setup Request messages

992-0608-08 Rev. 001

Datatype Units
eRAB Successes All int64 # 0..9223372036854775807 Number of eRABs included in eRAB Setup Lists in S1 eRAB Setup
Response and S1 Initial Context Setup Response messages for which
eRAB-ID has also been included in an eRAB to be Setup List in either an
S1 eRAB Setup Request or S1 Initial Context Setup Request message
eRAB Failed All int64 # 0..9223372036854775807 Number of eRABs in the process of being setup when an S1 Initial
Attempts Context Setup Failure message is received and the number of eRABs in
the process of being setup for which a S1 Initial Context Setup
Response or S1 eRAB Setup Response message is received that does
not include an established confirmation for the eRAB ID
eRAB Release All int64 # 0..9223372036854775807 Number of eRABs in the active state for which explicit release is
Attempts requested in S1AP S1 eRAB Release Indication or S1 eRAB Release
Command message, or which are implicitly released by being active at
the time of RRC connection release including Normal Release, Dropped
Connection and Redirection
eRAB Drops All int64 # 0..9223372036854775807 Number of eRABs not admitted during outgoing X2 or S1 handover +
number of active eRABs released by S1 eRAB Release Indication or S1
eRAB Release Command with S1 cause indicating connection or eRAB
drop + number of eRABs active at the time of a dropped connection
eRAB Normal All int64 # 0..9223372036854775807 Number of active eRABs released normally when the RRC connection
Releases closed due to Redirection or Normal Release, or when the eRAB Id of
the eRAB is explicitly released in an S1 eRAB Release Indication or
eRAB Release Command
Last RRC All string no units 0..999999268435455 ECGI or cell name of the serving cell at the time of the last RRC
Measurement measurement report. For Samsung, this is taken from the CSL
Cell Disconnection Information ECI when last measurement information is
taken from the CSL for the call or fragment.
Last RRC All time no units 1/1/1970 00:00..12/31/9999 23:59 Time of the last RRC Measurement Report. For Samsung, the last RRC
Measurement measurement report time is set to the Disconnection Information time
Time of the CSL when the last measurement report is taken from the CSL.

992-0608-08 Rev. 001

Datatype Units
Last RRC Ericsson, int64 no units 0..262143 The eARFCN of the last RRC Measurement Report
Measurement Nokia,
eARFCN Samsung,
Huawei,
ZTE,
Altiostar
Num of All int64 # 0..8 Number of neighbor cells contained in the last RRC measurement
Neighbors [#] report. For Samsung, when the last measurement report is taken from
the CSL, the number of neighbor cells of the fragment or call is
determined from the number of neighbor cells indicated in the CSL
Adjacent Information.
N1 PCI All int64 no units 0..503 PCI for neighbor 1 in last RRC Measurement Report. For Samsung,
when 3GPP Measurement Reports are unavailable N1 PCI may be
taken from the Adjacent Information of the CSL.
N1 Cell All string no units 0..999999268435455 Cell ID or cell name of the first neighbor cell
N1 RSRP [dBm] All double dBm -141..-44 RSRP for neighbor 1 in last RRC Measurement Report. For Samsung,
when 3GPP Measurement Report are missing, N1 RSRP may be taken
from CSL Adjacent Information.
N1 RSRQ [dB] All double dB -20..-3 RSRQ for neighbor 1 in last RRC Measurement Report. For Samsung,
when 3GPP Measurement Report are missing, N1 RSRQ may be taken
from CSL Adjacent Information.
N2 Cell All string no units 0..999999268435455 Cell ID or cell name of the 2nd neighbor cell
when 3GPP Measurement Reports are unavailable N2 RSRP may be
taken from CSL Adjacent Information.

992-0608-08 Rev. 001

Datatype Units
when 3GPP Measurement Reports are unavailable N2 RSRQ may be
N3 Cell All string no units 0..999999268435455 Cell ID or cell name of the 3rd neighbor cell
when 3GPP Measurement Reports are unavailable N3 RSRP may be
when 3GPP Measurement Reports are unavailable N3 RSRQ may be
N4 PCI All int64 no units 0..503 PCI for neighbor 4 in last RRC Measurement Report.
N4 Cell All string no units 0..999999268435455 Cell ID or cell name of the 4th neighbor cell
N4 RSRP [dBm] All double dBm -141..-44 RSRP for neighbor 4 in last RRC Measurement Report.
N4 RSRQ [dB] All double dB -20..-3 RSRQ for neighbor 4 in last RRC Measurement Report.

992-0608-08 Rev. 001

Datatype Units
TA Distance All double meters 0..240405 Timing Advance Distance for the End Cell may be expressed in either
[Meters/Miles] meters or miles in the call table, and in meters only in the LSR output.
Not set for NB-IoT calls.
Intersite All double meters 0..240405 Inter Site Distance for End Cell is determined from calculations based
Distance on the content of the Network Element table. Inter Site Distance for
[Meters/Miles] End Cell may be expressed in either meters or miles in the call table,
and in meters only in LSR output. Not set for NB-IoT calls.
Range ISD Ratio All double no units 0..240405 Range as determined by TA or Propagation Delay (Ratio of TA Distance
to InterSite Distance for End Cell). Not set for NB-IoT calls.
Vendor All string enum N/A Vendor for this Call
UE Power All double dB -23..40 Last Power Headroom Information expressed in dB. In the case of
Headroom [dB] Samsung LTE, the last valid value of MAC power headroom received in
the VSE Periodic RF Information event is used as last power headroom.
In the case of Nokia LTE, power headroom is taken from the last
received MAC PHR event for the session. In the case of Altiostar, the
last UE Power Headroom of the fragment or call is read from the last
received VSE_UL_SCHED event containing valid avg_phr field. In the
case of Huawei, the last UE Power Headroom of the fragment or call is
read from the last received UE periodic radio link MR or UE periodic
radio link MR MDT event containing valid DL Wideband CQI Code0 field.
Last UE Tx Samsung double dBm -17..23 [Samsung] Transmission power of UE when the call disconnects from
Power [dBm] the eNB. Samsung estimates UE transmission power from Power
Headroom Reports from UE. The Last UE TX Power of a fragment
reflects the value of the ueTxPower field of the last CSL associated with
the fragment, while the Last UE TX Power shown in the Call Table
reflects the value of ueTxPower field of the last fragment of the call.

992-0608-08 Rev. 001

Datatype Units
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 as they are created starting with
the value '1.' Fragment ID is not expressed in Call Table.
Composite Call All bool boolean True, False Indicates a composite call that has been created from more than one
constituent call fragment by the LTE Call Stitcher function.
Last VoLTE eRAB All time no units 1/1/1970 00:00..12/31/9999 23:59 Last VoLTE eRAB start time
Start Time
Last VoLTE eRAB All time no units 1/1/1970 00:00..12/31/9999 23:59 Last VoLTE eRAB end time
End Time
Last VoLTE eRAB All duration no units 0..99999999:59 Last VoLTE eRAB end time minus last VoLTE start time and VoLTE setup
Duration time
Last VoLTE eRAB All string enum N/A Last VoLTE eRAB release cause
Release Cause
Last Video Call All string enum N/A Last video call eRAB release cause
eRAB Release
Cause
VoLTE eRABs All int64 # 0..9223372036854775807 Number of VoLTE eRAB with emergency ARP
with Emergency
ARP

992-0608-08 Rev. 001

Datatype Units
Mean PDCP Huawei double kbps 0..147573952589676412920 [Huawei] Total number of PDCP SDU bytes received in the uplink over
Throughput UL all E-RABs divided by the accumulated collection period. The number of
[kbps] uplink PDCP SDU bytes is accumulated over UL Data Volume of the E-
RAB Throughput Stat List entry for each E-RAB for every Huawei
throughput periodic statistical event received. The collection period of
each Huawei throughput periodic statistical event is determined by
taking the largest collection period among the Throughput Stat List UL
Data Transmission Time entries for the E-RABs. It is assumed that the
uplink PDCP SDU byte counts are reset for each E-RAB at the onset of
Mean PDCP Huawei double kbps 0..147573952589676412920 [Huawei] Total number of PDCP SDU bytes received in the downlink
Throughput DL over all E-RABs divided by the accumulated collection period. The
[kbps] number of downlink PDCP SDU bytes is accumulated over DL Data
Volume of the E-RAB Throughput Stat List entry for each E-RAB for
every Huawei throughput periodic statistical event received. The
collection period of each Huawei throughput periodic statistical event
is determined by taking the largest collection period among the
Throughput Stat List DL Data Transmission Time entries for the E-
RABs. It is assumed that the downlink PDCP SDU byte counts are reset
for each E-RAB at the onset of the each collection period.
PUSCH SINR Nokia, double dB -1000..1000 [Nokia, Samsung, Ericsson, Altiostar] Last reported uplink PUSCH
[dB] Samsung, signal-to-interference-plus-noise ratio (SINR). For Nokia LTE, PUSCH
Ericsson, SINR is read from the MAC UL SINR message. For Samsung LTE,
Altiostar PUSCH SINR is read from the VSE Periodic RF Information event. For
Altiostar, PUSCH SINR of the fragment or call is read from the last
received VSE_UL_SCHED event containing valid Avg_sinr field.

992-0608-08 Rev. 001

Datatype Units
E-UTRAN Samsung duration no units 0..99999999:59 [Samsung] E-UTRAN access network setup time: This is defined as the
Connection difference between the CSL Setup and Attempt Times. The Setup time
Setup Time is the timestamp of the Initial Context Setup Response message for the
times at which the handover process ends normally and the call enters
the connected state. The Attempt time is the timestamp of the RRC
Connection Request message or the Handover Request message
Call Type Samsung string enum N/A [Samsung] Samsung CSL Call Type of the CSL record
Call Release Samsung string enum N/A [Samsung] Samsung Call Summary Log (CSL) Call Release Cause taken
Cause from the last CSL
Last RRC Samsung string enum N/A [Samsung] The last RRC Connection Reestablishment case of the call
Reestablishment with QCI #1. This is taken from the last CSL RRE Information block
Case received.
Mean Samsung double no units 0..15 [Samsung] Mean CQI calculated from all CQI counts contained in all
Cumulative CQI received VSE_PERIODIC_RF_INFORMATION events. This is the weighted
average of the MAC_CQI_0..MAC_CQI_15 fields of the received VSE_
PERIODIC_RF_INFORMATION events during the call or fragment.
Last CQI Samsung int64 no units 0..15 [Samsung] Last CQI associated with the RRC Connection taken from the
CSL
Last UL Rx Samsung double dBm -1000..1000 [Samsung] The last received value for uplink received interference
Interference power, including thermal noise, is taken from the last received VSE
Power [dBm] Periodic RF Information event received for the call session. Received
interference power is read from the MAC_RX_INTERFERENCE_UL field
of the VSE Periodic RF Information message event. This measurement
corresponds to the 'Received Interference Power' defined in 3GPP TS
36.214.
PUCCH SINR Samsung, double dB -1000..1000 [Samsung, Ericsson] Last PUCCH SINR expressed in dB. For Samsung
[dB] Ericsson LTE, the last valid PUCCH SINR received in the VSE Periodic RF
Information event is utilized.

992-0608-08 Rev. 001

Datatype Units
RLC PDU DL Samsung, int64 bytes 0..9223372036854775807 [Samsung] For Samsung LTE, Downlink RLC PDU bytes transmitted
Volume [bytes] Alcatel- calculated by summing over all eRAB of the CSL. [ALU] Number of
Lucent bytes sent in the downlink direction for the first time over best effort
bearers (QCI value 5-9) only over the RLC interface . Collected over
both Secondary and Tertiary PCMD records.
RLC PDU UL Samsung, int64 bytes 0..9223372036854775807 [Samsung] For Samsung LTE, uplink RLC PDU bytes received calculated
Volume [bytes] Alcatel- by summing over all eRAB of the CSL. [ALU] Number of uplink RLC PDU
Lucent bytes received over best effort bearers (QCI values 5-9} including
retransmissions. This is the aggregation over both secondary and
tertiary PCMD records for the subscriber during the call.
RLC PDU DL Samsung, int64 bytes 0..9223372036854775807 [Samsung] Downlink RLC PDU bytes retransmitted calculated by
Retransmitted Alcatel- summing over all eRAB of the CSL. [ALU] Downlink RLC bytes
Volume [bytes] Lucent retransmitted over best effort (QCI values 5-9) bearers only. The total
is collected over both secondary and tertiary PCMD records.
RLC PDU DL Samsung, double % 0..922337203685477580700 [Samsung] Ratio of RLC DL Retransmitted Data Volume (bytes) to RLC
Retransmit Rate Alcatel- DL Data Volume (bytes) expressed as a percentage. Note that this ratio
[%] Lucent can be greater than 100% when the value of RLC RL Retransmitted
Data Volume in the CSL exceeds the value of RLC DL Data Volume in
the CSL. In the past, the RLC Data Volume counts contained in the CSL
have been known to reflect only the activity from the time of the last
intra-eNB handover at the eNB and thus may not reflect all of the
activity described by the CSL record. [ALU] Ratio of DL RLC BE
Retransmitted kbytes to DL RLC BE Transmitted kbytes.
S1-U UL Data Samsung int64 bytes 0..9223372036854775807 [Samsung] Uplink GTP-U PDU data volume on S1-U interface in bytes
Volume [bytes] summed over all eRAB of the CSL
S1-U DL Data Samsung int64 bytes 0..9223372036854775807 [Samsung] Downlink GTP-U PDU data volume on S1-U interface in
Volume [bytes] bytes summed over all eRAB of the CSL

992-0608-08 Rev. 001

Datatype Units
Mean Uplink IP Samsung double kbps 0..9223372036854775807 [Samsung] Mean Uplink IP Throughput calculated by dividing S1-U UL
Throughput Data Volume (based on CSL txDataToSG over all RABs) divided by CSL
[kbps] Call Segment Duration.
Mean Downlink Samsung double kbps 0..9223372036854775807 [Samsung] Mean Downlink IP Throughput calculated by dividing S1-U
IP Throughput DL Data Volume (based on CSL rxDataFromSG over all RABs) divided
[kbps] by CSL Call Segment Duration.
MAC DL RE Samsung int64 resource 0..9223372036854775807 [Samsung] Total downlink assigned resource element count
[resource elements accumulated over all valid MAC_RE_DL contained in received VSE_
elements] PERIODIC_RF_INFORMATION events.
MAC UL RE Samsung int64 resource 0..9223372036854775807 [Samsung] Total uplink assigned resource element count accumulated
[resource elements over all valid MAC_RE_UL contained in received VSE_PERIODIC_RF_
elements] INFORMATION events.
MAC DL RB Samsung int64 resource 0..9223372036854775807 [Samsung] Total downlink assigned resource block count accumulated
[resource blocks over all valid MAC_RB_DL contained in received VSE_PERIODIC_RF_
blocks] INFORMATION events.
MAC UL RB Samsung int64 resource 0..9223372036854775807 [Samsung] Total downlink assigned resource block count accumulated
[resource blocks over all valid MAC_RB_UL contained in received VSE_PERIODIC_RF_
blocks] INFORMATION events.
MAC DL RE/RB Samsung double no units 0..9223372036854775807 [Samsung] Ratio of total MAC DL RE to total MAC DL RB.
MAC UL RE/RB Samsung double no units 0..9223372036854775807 [Samsung] Ratio of total MAC UL RE to total MAC UL RB.
Last DL UE to Samsung double no units 0..2147483647 [Samsung] Ratio of downlink scheduled TTI for the UE to the total
Cell TTI Ratio downlink TTI for the cell. Calculated as the ratio of MAC_TTI_DL / MAC_
TTI_DL_CELL_TOTAL in the last VSE_PERIODIC_RF_INFORMATION event
received.
Last UL UE to Samsung double no units 0..2147483647 [Samsung] Ratio of uplink scheduled TTI for the UE to the total uplink
Cell TTI Ratio TTI for the cell. Calculated as the ratio of MAC_TTI_UL / MAC_TTI_UL_
CELL_TOTAL in the last VSE_PERIODIC_RF_INFORMATION event
received.

992-0608-08 Rev. 001

Datatype Units
Mean eNB Rank Samsung, double no units 0..9223372036854775807 [Samsung] Mean eNB Rank Indicator calculated as the ratio of
Indicator Ericsson weighted downlink rank indicator counts to unweighted downlink
indicator counts over all received VSE_PERIODIC_RF_INFORMATION
events. The numerator is calculated as the sum of MAC_RI_DL_0 +
MAC_RI_DL_1 + MAC_RI_DL_2 + MAC_RI_DL_3 over each VSE_PERIODIC_
RF_INFORMATION received and the denominator is calculated as the
sum of MAC_RI_DL_0 + MAC_RI_DL_1 + MAC_RI_DL_2 + MAC_RI_DL_3
over each VSE_PERIODIC_RF_INFORMATION received. [Ericsson]
Sample weighted mean of Rank Indicator.
Mean UE Rank Samsung double no units 0..9223372036854775807 [Samsung] Mean UE Rank Indicator calculated as the ratio of weighted
Indicator uplink rank indicator counts to unweighted uplink indicator counts over
all received VSE_PERIODIC_RF_INFORMATION events. The numerator is
calculated as the sum of (MAC_RI_UL_0*1) + (MAC_RI_UL_1*2) + (MAC_
RI_UL_2*3) + (MAC_RI_UL_3*4) over each VSE_PERIODIC_RF_
INFORMATION received and the denominator is calculated as the sum
of MAC_RI_UL_0 + MAC_RI_UL_1 + MAC_RI_UL_2 + MAC_RI_UL_3 over
each VSE_PERIODIC_RF_INFORMATION received.
Mean MAC BLER Samsung double % 0..100 [Samsung] Mean MAC uplink BLER (Block Error Rate) calculated by
UL [%] dividing the sum of all VSE_PERIODIC_RF_INFORMATION.MAC_BLER_UL
content by the count of all valid VSE_PERIODIC_RF_INFORMATION.MAC_
BLER_UL received, including the value zero.
Transmission Samsung, double % 0..100 [Samsung] Transmission Mode 1 percentage calculated by dividing the
Mode 1 [%] Ericsson number of Transmission Mode 1 (MAC_TX_MODE_1) counts by the
total number of transmission mode counts (MAC_TX_MODE_1..MAC_
TX_MODE_10) counts received in VSE_PERIODIC_RF_INFORMATION
events. [Ericsson] Transmission Mode 1 percentage calculated from
received INTERNAL_PER_RADIO_UE_MEASUREMENT events

992-0608-08 Rev. 001

Datatype Units

992-0608-08 Rev. 001

Datatype Units
Transmission Samsung, double % 0..100 [Samsung] Transmission Mode 10 percentage calculated by dividing
Mode 10 [%] Ericsson the number of Transmission Mode 10 (MAC_TX_MODE_10) counts by
the total number of transmission mode counts (MAC_TX_MODE_
1..MAC_TX_MODE_10) counts received in VSE_PERIODIC_RF_
INFORMATION events. [Ericsson] Transmission Mode 10 percentage
calculated from received INTERNAL_PER_RADIO_UE_MEASUREMENT
events

992-0608-08 Rev. 001

Datatype Units
VoLTE RTP Gap Samsung bool boolean True, False [Samsung] A VoLTE no RTP gap indication is indicated if a received CSL
indicates that a PDCP or MAC uplink or downlink gap between RTP
packets has been detected over a QCI#1 radio bearer. No RTP gaps
are determined from the MAC_UP_NO_RTP, MAC_DL_NO_RTP, PDCP_
UL_NO_RTP and PDCP_DL_NO_RTP fields of the Call Debugging
Information of the CSLs associated with the call. A no RTP gap is
detected within the PDCP layer when uplink or downlink traffic for a
QCI#1 radio bearer is not detected for the period of the Samsung
noRtpTimer. A no RTP is detected within the MAC layer if scheduling is
not executed for a downlink or uplink section of a QCI#1 radio bearer
within expected time limit when RTP packets are waiting to be
transmitted.
VoLTE One Way Samsung bool boolean True, False [Samsung] A VoLTE one-way audio warning is indicated when either of
Audio Warning the RLC uplink or downlink no-packet delay exceeds the no-packet
delay threshold set by IRIS, or when either the RLC uplink or downlink
zero-BO count exceeds the zero-BO count threshold set by IRIS. The
RLC no-packet delay is taken from the RLC_UL_NO_PACKET_DELAY of
CSL Call Debugging Information for the uplink and from the RLC_DL_
NO_PACKET_DELAY of CSL Call Debugging Information for the
downlink. No-packet delay counts measure the number of TTIs from
setup of a QCI#1 bearer until the reception of the first packet. RLC
zero-BO counts are taken from the RLC_UL_ZERO_BO_CNT of CSL Call
Debugging Information for the uplink and from the RLC_DL_ZERO_BO_
CNT of CSL Call Debugging Information for the downlink. The zero-BO
count is the number of times that BO is zero for a QCI#1 radio bearer
in the indicated direction for a duration greater than that of the
noRtpTimer.

992-0608-08 Rev. 001

Datatype Units
VoLTE Samsung bool boolean True, False [Samsung] VoLTE scheduling error indicates that the RLC downlink no
Scheduling Error scheduling count for at least one CSL exceeds the threshold set by IRIS.
The VoLTE downlink no scheduling count is read from the CSL RLC_DL_
NO_SCHEDULING field of the CSL Call Debugging Information. The
VoLTE downlink no scheduling count indicates the number of times that
downlink BO is present for a QCI#1 radio bearer for a duration longer
than that allowed by the noRtpTimer.
VoLTE ROHC Samsung bool boolean True, False [Samsung] VoLTE ROHC error indicates that the VoLTE ROHC
Error decompression error count exceeds the threshold set in IRIS in at least
one CSL associated with the call. The ROHC_DECOMP_ERR_CNT count
of the CSL Call Debugging Information is read to determine the VoLTE
ROHC decompression error count. The VoLTE decompression error
count is determined within PDCP for QCI#1 radio bearer.
UDC Enabled Samsung bool no units True, False [Samsung] Indicates whether Uplink Data Compression (UDC) has
been enabled during the fragment or call.
Carrier Ericsson, int64 ms 0..9223372036854775807 Total time that Carrier Aggregation Service was active
Aggregation Nokia,
Service Time Samsung,
[ms] Huawei,
ZTE,
Altiostar,
Alcatel-
Lucent

992-0608-08 Rev. 001

Datatype Units
Carrier Ericsson, double % 0..922337203685477580700 Ratio of total Carrier Aggregation Service time to call duration
Aggregation Nokia,
Service Rate [%] Samsung,
Huawei,
ZTE,
Altiostar,
Alcatel-
Lucent
CSL Event Samsung string enum N/A [Samsung] CSL Event contains the reason for closing the CSL, which
can be release of the RRC connection, redirection or handover to other
eNB or Radio Access Technology (RAT)
Call Segment Samsung duration no units 0..99999999:59 [Samsung] Calculated from the difference between the Disconnect and
Duration Attempt timestamps in the Call Summary Log and corresponds to the
portion of the call summarized in the log
Angle of Arrival Nokia, double degrees 0..359.5 [Nokia, ZTE] Last reported Angle of Arrival in degrees. In the case of
ZTE Nokia LTE, the value is taken from the last valid Angle of Arrival
contained in a MAC AOA event.
Mean MAC Nokia double kbps 0..147573952589676412920 [Nokia] Total number of bytes received in the uplink over both GBR as
Throughput UL well as non-GBR bearers at the MAC layer divided by the accumulated
[kbps] collection period. The number of GBR bytes is accumulated over
utUlsReceivedGbrBytes of the MAC_UL_UeThroughput event and the
number of non_GBR bytes is accumulated over
utUlsReceivedNonGbrBytes of the MAC_UL_UeThroughput event. The
collection period of each MAC_UL_UeThroughput is taken from
utNumOfReceivedTxAll (number of received transmissions). It is
assumed that the Nokia non-GBR and GBR uplink byte counts are
incremental for the call session and do not wrap-around at
4294967295 bytes.

992-0608-08 Rev. 001

Datatype Units
Mean MAC Nokia double kbps 0..147573952589676412920 [Nokia] Total number of bytes sent in the downlink over both GBR as
Throughput DL well as non-GBR bearers at the MAC layer divided by the accumulated
[kbps] collection period. The number of GBR bytes is accumulated over
utDlsSentGbrBytes of the MAC_DL_UeThroughput event and the
number of non_GBR bytes is accumulated over utDlsSentNonGbrBytes
of the MAC_DL_UeThroughput event. The collection period of each
MAC_DL_UeThroughput is taken as the sum of utSingleCWTx (number
of single codeword transmissions) and utDualCWTx (number of dual
codeword transmissions). It is assumed that the Nokia non-GBR and
GBR downlink byte counts are incremental for the call session and do
not wrap-around at 4294967295 bytes.
Initial NAS Ericsson, string enum N/A [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] The initial NAS
Request Nokia, request
Samsung,
Huawei,
ZTE,
Altiostar
Initial NAS Ericsson, string enum N/A [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar]The response to
Response Nokia, initial NAS request
Samsung,
Huawei,
ZTE,
Altiostar
OEM RRC Setup Ericsson string enum N/A [Ericsson] Ericsson internal cause value for RRC setup
Cause
OEM S1 Setup Ericsson string enum N/A [Ericsson] Internal S1 Initial UE Context Setup Cause
Cause
OEM S1 Release Ericsson string enum N/A [Ericsson] S1 UE Context Release Cause In Ericsson Internal Event
Cause

992-0608-08 Rev. 001

Datatype Units
OEM Internal Ericsson string enum N/A [Ericsson] Internal Release Cause
Release Cause
Release with Ericsson string enum N/A [Ericsson] eRAB released with data in buffer
Data Lost
Data Lost Ericsson bool boolean TRUE,FALSE [Ericsson] Data lost at session release
Release Node Ericsson string enum N/A [Ericsson] The release node for the UE context
Mean CQI Ericsson, double no units 0..15 [Ericsson,ALU] Mean CQI in last eNB measurement report. [Samsung]
Alcatel- Last CQI associated with the RRC Connection taken from the CSL.
Lucent, [Altiostar] Last received valid average value received in the fragment
Samsung, or call read from the avg_cqi field of the VSE_DL_SCHED event. [Nokia]
Altiostar, Last received valid average value for wideband Channel Quality
Nokia, Indicator received in the utMeanLaWbCqi field of the MAC_DL-
Huawei UeThroughput event. [Huawei] Last received valid value for wideband
Channel Quality Indicator received in the DL Wideband CQI Code0 field
of the UE periodic radio link MR and UE periodic radio link MR MDT
events.
CQI Cell Ericsson, string no units 0..999999268435455 [Ericsson, Altiostar, Nokia, Huawei] Cell for last mean CQI
Altiostar,
Nokia,
Huawei
MAC Volume DL Ericsson, int64 bytes 0..9223372036854775807 [Ericsson] DL MAC volume during the RRC connection [Nokia] The
[bytes] Nokia cumulative number of bytes sent over non-GBR as well as GBR
downlink bearers. Downlink MAC bytes are read from the
utDlsSentNonGbrBytes and utDlsSentGbrBytes fields of the periodic
MAC_DL_UeThroughput message. It is assumed that the Nokia non-
GBR and GBR downlink byte counts are incremental for the call session
and do not wrap-around between events.

992-0608-08 Rev. 001

Datatype Units
MAC Volume UL Ericsson, int64 bytes 0..9223372036854775807 [Ericsson] UL MAC volume during the RRC connection [Nokia] The
[bytes] Nokia cumulative number of bytes received over non-GBR as well as GBR
uplink bearers. Uplink MAC bytes are read from the
utUlsReceivedNonGbrBytes and utUlsReceivedGbrBytes fields of the
periodic MAC_UL_UeThroughput message. It is assumed that the Nokia
non-GBR and GBR uplink byte counts are incremental for the call
session and do not wrap-around between events.
PDCP Volume Ericsson, int64 bytes 0..9223372036854775807 [Ericsson, Altiostar, Huawei] DL PDCP DRB volume during the RRC
DL [bytes] Altiostar, connection. Altiostar downlink PDCP volume is calculated from VSE_
Huawei PDCP total_DL_bytes. For Huawei, the DL Data Volume of each E-RAB
contained in the E-RAB Throughput Stat List of each Huawei throughput
periodic statistical event is summed over each fragment and the
composite call record to provide downlink PDCP SDU data volume.
PDCP Volume Ericsson, int64 bytes 0..9223372036854775807 [Ericsson, Altiostar, Huawei] UL PDCP DRB volume during the RRC
UL [bytes] Altiostar, connection. Altiostar uplink PDCP volume is calculated from VSE_PDCP
Huawei total_UL_bytes. For Huawei, the UL Data Volume of each E-RAB
contained in the E-RAB Throughput Stat List of each Huawei throughput
periodic statistical event is summed over each fragment and the
composite call record to provide uplink PDCP SDU data volume.
Mean PDCP DRB Ericsson int64 kbps 0..16777215 [Ericsson] Mean DL throughput for PDCP DRB
Throughput DL
[kbps]
Mean PDCP DRB Ericsson int64 kbps 0..16777215 [Ericsson] Mean UL throughput for PDCP DRB
Throughput UL
[kbps]
Mobile Number Alcatel- int64 no units 0..999999999999999 [ALU] Mobile Subscriber ISDN (Integrated Services Digital Network)
Lucent Number

992-0608-08 Rev. 001

Datatype Units
End m-TMSI Alcatel- int64 no units 0..4294967295 [ALU, Ericsson, Nokia, Huawei, ZTE, Altiostar] m-TMSI at PCMD end OR
Lucent, the m-TMSI will be picked from NAS message if possible when
Ericsson, Diameter feature is active and a new GUTI assignment is detected.
Nokia,
Huawei,
ZTE,
Altiostar
eNB CFCQ Alcatel- string enum N/A [ALU] This field indicates the Final Class Qualifier code for the UE
Lucent Context. It is used with CFC and SCFCQ to identify the disposition for
the procedure
eNB SCFCQ Alcatel- string enum N/A [ALU] This field indicates the Secondary Final Class Qualifier code for
Lucent the UE Context.
Procedure Alcatel- string enum N/A [ALU]MME Procedure Call Final Class Qualifier
SCFCQ Lucent
Mobility Trigger Alcatel- string enum N/A [ALU] Includes Invalid, radio condition, congestion control, CSFB, load
Reason Lucent balancing, active UE capacity limit during OOT-to-active transition, CAC
failure
Start Trigger Alcatel- string enum N/A [ALU] Trigger for initiation of the PCMD
Reason Lucent
Procedure ID Alcatel- string enum N/A [ALU] MME Procedure ID
Lucent
S1AP Procedure Alcatel- string enum N/A [ALU] S1 Cause values specified in 36.413
Context Lucent
Qualifier
Type of Initiation Alcatel- string enum N/A [ALU] Includes Invalid, UE Origin, UE Term and Handover
Lucent
End GUMMEI All string no units 111.00.000.000..999.999.65535.255 End Globally Unique MME Identifier (GUMMEI) of the last fragment, or
in the case of a fragment, the end GUMMEI of the fragment.

992-0608-08 Rev. 001

Datatype Units
Last Inter-cell Alcatel- string enum N/A [ALU] This parameter indicates success or the failure reason code of
Intra-eNB HO Lucent last inter-cell, intra-eNodeB Handover failure for the interval that the
Disposition UE is served by the eNodeB.
Last X2 HO Alcatel- string enum N/A [ALU] This parameter indicates success or the failure reason code of
Disposition Lucent last X2 Handover failure
Last S1 HO Alcatel- string enum N/A [ALU] This parameter indicates success or the failure reason code of
Disposition Lucent last S1 Handover failure
Last intra-cell Alcatel- string enum N/A [ALU] This parameter indicates success or the failure reason code of
HO Disposition Lucent last intra-cell Handover failure
RLC SDU UL Alcatel- double kbytes 0..1.7976931348623158 E + 308 [ALU] UL RLC SDU GBR & BE Received bytes
Volume [kbytes] Lucent
MAC UL PDUs Alcatel- int64 # 0..9223372036854775807 [ALU] UL Total MAC PDUs for Initial Transmission
Lucent
HARQ DL Initial Alcatel- int64 # 0..9223372036854775807 [ALU] Number of DL Initial HARQ Transmissions
Transmissions Lucent
by DS
HARQ DL Alcatel- int64 # 0..9223372036854775807 [ALU] Number of DL HARQ Retransmissions
Retransmissions Lucent
by DS
Mean UL SINR Alcatel- double dB -30.1..71.45 [ALU, ZTE] Average UL Signal to Interference Noise Ratio
[dB] Lucent,
ZTE
HARQ DL Alcatel- double % 0..922337203685477580700 [ALU] (Number of DL HARQ Retransmissions)/(Number of DL Initial
Retransmit Rate Lucent HARQ Transmissions)
by DS [%]
DL TTIs UE Alcatel- int64 # 0..9223372036854775807 [ALU] Total number of downlink TTIs scheduled to the UE during the
Scheduled Lucent PCMD collection interval.

992-0608-08 Rev. 001

Datatype Units
DL MIMO TTIs Alcatel- int64 # 0..9223372036854775807 [ALU] Total number of downlink TTIs scheduled to the UE when the UE
UE Scheduled Lucent is in a MIMO transmission state.
RLC UL Alcatel- double kbps 0..147573952589676412920 [ALU] UL RLC SDU Transmitted bytes divided by the # of TTIs UE's UL
Throughput Lucent RLC BE PDU received
[kbps]
RLC DL Alcatel- double kbps 0..147573952589676412920 [ALU] DL RLC PDU Transmitted bytes divided by the DL data
Throughput Lucent Transmission time for BE bears
[kbps]
Last 1xCSFB Alcatel- string enum N/A [ALU] This parameter indicates the failure reason code of last 1xCSFB
Failure Code Lucent
Last e1xCSFB Alcatel- string enum N/A [ALU] This parameter indicates success or the failure reason code of
Failure Code Lucent last e1xCSFB
RLF Reports Ericsson, int64 # 0..9223372036854775807 Number of RLF Report received
Nokia,
Samsung,
Huawei,
ZTE,
Altiostar
RLF Cause Ericsson, string enum N/A RLF cause in RLF report
Nokia,
Samsung,
Huawei,
ZTE,
Altiostar

992-0608-08 Rev. 001

Datatype Units
MDT Location Ericsson, time no units 1/1/1970 00:00..12/31/9999 23:59 Time of last MDT location report from any fragment of the call. MDT
Time Nokia, location is set to call end location if it is within certain time. Default is
Samsung, 12s.
Huawei,
ZTE,
Altiostar
MDT Latitude Ericsson, double degrees 90.000000..-90.000000 Latitude reported in last MDT from any fragment of the call. MDT
[degrees] Nokia, location is set to call end location if it is within certain time. Default is
Samsung, 12s.
Huawei,
ZTE,
Altiostar
MDT Longitude Ericsson, double degrees 180.000000..-180.000000 Longitude reported in last MDT in any fragment. MDT location is set to
[degrees] Nokia, call end location if it is within certain time. Default is 12s.
Samsung,
Huawei,
ZTE,
Altiostar
MDT Altitude Ericsson, double meters -32767..32767 Altitude reported in last MDT data from last fragment of the call.
[meters] Nokia, Positive is above WGS84 ellipsoid surface. Negative is below WGS84
Samsung, ellipsoid surface.
Huawei,
ZTE,
Altiostar
MDT Accuracy Ericsson, int64 meters 0..1800000 Uncertainty in meters of last MDT location from last fragment of the
[meters] Nokia, call
Samsung,
Huawei,
ZTE,
Altiostar

992-0608-08 Rev. 001

Datatype Units
MDT Speed Ericsson, int64 km/h 0..65535 Horizontal speed in kilometers per hour from last MDT in last fragment
[km/h] Nokia, of the call
Samsung,
Huawei,
ZTE,
Altiostar
Number of All int64 # 0..9223372036854775807 Number of cross vendor stitching in the composite call.
Cross Vendor
Stitching
5G NR Serving Ericsson, string no units 0..99999968719476735 NR CGI of last 5G EN-DC PSCell
Cell Samsung,
Huawei,
Alcatel-
Lucent
5G NR Serving Ericsson, int64 no units 0..1007 PCI of last 5G EN-DC PSCell
PCI Samsung,
Huawei,
Alcatel-
Lucent
5G NR Serving Ericsson, int64 no units 0..3279165 ARFCN of last 5G EN-DC PSCell
ARFCN Samsung,
Huawei,
Alcatel-
Lucent
5G EN-DC Ericsson, duration no units 0..99999999:59 The duration for 5G EN-DC
Duration Samsung,
Huawei,
Alcatel-
Lucent

992-0608-08 Rev. 001

Datatype Units
5G EN-DC Ericsson, float % 0..100 The ratio of 5G EN-DC duration to total RRC duration
Duration Rate Samsung,
[%] Huawei,
Alcatel-
Lucent
Maximum Ericsson, int64 # 0..32 Maximum number of carrier components during the RRC. LTE PCC,
Number of Samsung, SCC, and 5G EN-DC are included.
Carrier Huawei,
Components Alcatel-
Lucent
Average Ericsson, float no units 0..32 Time weighted average number of carrier components during the RRC.
Number of Samsung, LTE PCC, SCC, and 5G EN-DC are included. It's calculated by total
Carrier Huawei, duration of all carrier components divided by RRC duration.
Components Alcatel-
Lucent
5G EN-DC SgNB Ericsson, int64 # 0..9223372036854775807 Number of 5G EN-DC SgNB addition attempts.
Addition Samsung,
Attempts Huawei,
Alcatel-
Lucent
5G EN-DC SgNB Ericsson, int64 # 0..9223372036854775807 Number of 5G EN-DC SgNB addition failures
Addition Failures Samsung,
Huawei,
Alcatel-
Lucent

992-0608-08 Rev. 001

Datatype Units
5G EN-DC SgNB Ericsson, int64 # 0..9223372036854775807 Number of 5G EN-DC SgNB abnormal releases
Drops Samsung,
Huawei,
Alcatel-
Lucent
Last 5G EN-DC Ericsson, string enum N/A The X2 release cause for last 5G EN-DC SgNB release
Release Cause Samsung,
Huawei
5G EN-DC Ericsson, int64 bytes 0..9223372036854775807 Downlink data volume transmitted by SgNB during 5G EN-DC from X2
Downlink Samsung, or S1 'Secondary RAT Data Usage Report'
Volume [bytes] Huawei
5G EN-DC Ericsson, int64 bytes 0..9223372036854775807 Uplink data volume received by SgNB during 5G EN-DC from X2 or S1
Uplink Volume Samsung, 'Secondary RAT Data Usage Report'
[bytes] Huawei
Time of Last RRC Ericsson, time no units 1/1/1970 00:00..12/31/9999 23:59 Time of last LTE RRC Measurement Report with 5G NR Cell
Measurement Samsung,
Report with 5G Huawei
NR Cell
5G NR Last Ericsson, string no units 0..99999968719476735 NR CGI of last 5G EN-DC measurement cell
Cell Huawei
5G NR Last Ericsson, int64 no units 0..1007 PCI of last 5G EN-DC measurement cell
PCI Huawei
5G NR Last Ericsson, int64 no units 0..3279165 ARFCN of last 5G EN-DC measurement cell
ARFCN Huawei

992-0608-08 Rev. 001

Datatype Units
5G NR RSRP Ericsson, float dBm -157..-30 RSRP for last 5G EN-DC measurement cell
[dBm] Samsung,
Huawei
5G NR RSRQ Ericsson, float dB -43.5..20 RSRQ for last 5G EN-DC measurement cell
[dB] Samsung,
Huawei
5G NR DL SINR Ericsson, float dB -23.5..40 DL SINR for last 5G EN-DC measurement cell
[dB] Samsung,
Huawei
SSB Index 0 in Ericsson, int64 no units 0..63 SSB Index 0 in last 5G EN-DC measurement
Last 5G NR Samsung,
Measurement Huawei
RSRP for Last Ericsson, float dBm -157..-30 RSRP for SSB Index 0 in last 5G EN-DC measurement
SSB Index 0 Samsung,
[dBm] Huawei
RSRQ for Last Ericsson, float dB -43.5..20 RSRQ for SSB Index 0 in last 5G EN-DC measurement
SSB Index 0 [dB] Samsung,
Huawei
DL SINR for Last Ericsson, float dB -23.5..40 DL SINR for SSB Index 0 in last 5G EN-DC measurement
SSB Index 0 [dB] Samsung,
Huawei
5G EN-DC SgNB Ericsson, int64 # 0..3279165 Number of 5G EN-DC SgNB change attempts during the call
Change Samsung,
Attempts Huawei
5G EN-DC SgNB Ericsson, int64 # 0..3279165 Number of 5G EN-DC SgNB change failures during the call
Change Failures Samsung,
Huawei

992-0608-08 Rev. 001

Datatype Units
5G EN-DC SgNB Ericsson, int64 # 0..3279165 Number of 5G EN-DC SgNB Modification attempts during the call
Modification Samsung,
Attempts Huawei
5G EN-DC SgNB Ericsson, int64 # 0..3279165 Number of 5G EN-DC SgNB Modification failures during the call
Modification Samsung,
Failures Huawei
A.3 Common LTE Enumerated Values

The following enumerated values are available for Common LTE.
Attribute Enumerated Values

End Latitude Latitude of the UE end start location determined by TrueCall. Not set for NB-IoT calls.
[degrees]
End Longitude Longitude of the UE call end location determined by TrueCall. Not set for NB-IoT calls.
[degrees]
Confidence TrueCall provides four 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. 'MDT GPS' is the location from MDT report. It's only reported in LTE. 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. NB-IoT
calls are always set to indicate unknown confidence.
Environment Indicates whether the call was determined to be indoor, mobile or outdoor stationary. Not set for NB-IoT calls.
IMSI International Mobile Subscriber Identity of the UE
IMEI International Mobile Equipment Identity (IMEI) of the UE. Type Allocation Code (TAC)-Serial Number (SNR)-Check digit

992-0608-08 Rev. 001

SVN Software Version Number in IMEISV
Roaming Group Service Provider of the UE as determined from the IMSI
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
Service Type Service Type is set to 'Voice and Data' to indicate the presence of QCI 1 eRAB, otherwise to 'Data Only'.
Trace ID [Huawei, Samsung, ZTE, Ericsson, Nokia, Altiostar] Contains the Cell Trace Recording Reference of the Cell Trace instance upon which the call record is
based. In the case of Samsung, the Trace Recording Session Reference taken from CSL, VSE TA Value, VSE Periodic RF Information, VSE Throughput
Information, or RRC, S1AP or X2AP Trace Information is used as Call ID. In the case of Altiostar, the Trace Id is taken as the complete value of the TRACE_
REFERENCE_ID of the TRACE EVENT HEADER. The least significant two bytes of the TRACE_REFERENCE_ID is coded with the Trace Recording Session
Reference of the cell trace session.
Start m-TMSI MME Temporary Mobile Subscriber Identity (m-TMSI) from RRC Connection Request or S1 Initial UE Message. In the case of Samsung, when otherwise not
available from 3GPP message events, start m-TMSI may be taken from the CSL.
Start Time Start time for the Call, taken from the timestamp of the earliest Cell Trace event
Duration Duration of the RRC connection, calculated as the sum of the durations of the fragments. For ALU LTE, call duration is the difference between the first start
time and last end time in all fragments. When used in a fragment, the duration is calculated as the difference between the timestamps of the first and last
Cell Trace events received. For Samsung LTE, the duration of a fragment or call is calculated based on the later of the two timestamps, the timestamp of the
last ASN.1 event received or the timestamp of the Disconnection Information of the CSL associated with the fragment or call.
End Time End time for the Call, taken from the timestamp of the last Cell Trace event. In the case of Samsung, the end time of the call or fragment is taken as the later
of the two timestamps, the timestamp of the last ASN.1 event or the timestamp of the Disconnection Information of the CSL.
Start Type Provides information on how the RRC Connection started at the serving cell
End Type Provides information on how the RRC Connection ended at the serving cell

992-0608-08 Rev. 001

Final Disposition Final Disposition of the RRC Connection at the serving cell is determined as follows: (1) If an RRC Connection Request message was received for the call and
the RRC connection fails to be established, then Final Disposition is set to indicate Failed Attempt; (2) If an NB-IoT RRC Connection Resume was received for
the call and the RRC connection fails to be resumed or established, then Final Disposition is set to indicate Failed Attempt; (3) Otherwise, if an RRC
Connection Request message was received for the call and the S1AP signaling connection to the MME is unsuccessful, then Final Disposition is set to
indicate Failed Attempt; (4) Otherwise, if the trace starts as a result of the RRC Connection Re-establishment procedure, and the RRC Connection Re-
establishment procedure fails, then Final Disposition is set to indicate Failed Reestablishment; (5) Otherwise, if a successful outgoing X2 Handover or
outgoing S1 Handover take place, then Final Disposition is set to indicate Outgoing Handover; (6) Otherwise, if an RRC Connection Release containing both
Redirected Absolute Radio Frequency Channel Number and Redirected Radio Access Technology is received, then Final Disposition is set to indicate
Redirection; (7) Otherwise, if an S1AP Release Cause is received, and the S1AP Release Cause indicates Radio Access Layer Cause User Inactivity, Load
Balancing Tracking Area Update Required or CS Fall Back Triggered or UE Not Available For PS Service, then the Final Disposition is set to indicate Normal
Release; (8) Otherwise, if an S1AP Release Cause is received, and the S1AP Release Cause indicates Radio Access Layer Cause inter-Radio Access
Technology Redirection, Redirection towards 1xRTT or Handover Desirable for Radio Reason, then the Final Disposition is set to indicate Redirection; (9)
Otherwise, if an S1AP Release Cause is received, and the S1AP Release Cause indicates Radio Access Layer Cause Successful Handover, then the Final
Disposition is set to indicate Outgoing Handover; (10) Otherwise, if an S1AP Release Cause is received, and the S1AP Release Cause indicates Non-Stratum
Access Layer Cause Normal Release or Detach, then the Final Disposition is set to indicate Normal Release; (11) Otherwise, if an S1AP Release Cause is
received, and the S1AP Release Cause indicates Non-Stratum Access Layer Cause Authentication Failure, then the Final Disposition is set to indicate Failed
Attempt; (12) Otherwise, if an S1AP Release Cause is received other than those specified earlier, then the Final Disposition is set to indicate Dropped
Connection; (13) Otherwise, if an RRC Connection Release is received with release cause indicating RRC suspend, then the Final Disposition is set to indicate
Normal Release; (14) Otherwise the Final Disposition is set to indicate Unknown.
Start Cell Cell Id or cell name of the first serving cell from the Cell Trace event. When otherwise not set from 3GPP events, in the case of Samsung, the Start Cell may
be determined from Connection Information of the first associated CSL.
Start eNB eNB ID or eNB name of the first serving cell from the Cell Trace event. When otherwise not set from 3GPP events, in the case of Samsung, the Start eNB
may be determined from Connection Information of the first associated CSL.
Start PCI Physical Cell Identity of the first serving cell. In the case of Samsung, the Start PCI may be determined from Connection Information of the first associated
CSL.
Start EARFCN DL Downlink E-UTRAN Absolute Radio Frequency Channel Number of the first serving cell
Start GUMMEI Globally Unique MME Identifier of the first serving MME taken from the Cell Trace event
Start Tracking Tracking Area Code from the S1 Initial UE Message. In the case of Altiostar, Tracking Area Code may also be read from the VSE_TAI event.
Area Code

992-0608-08 Rev. 001

Start MME UE In the case of Samsung, when MME S1AP ID is not available from 3GPP message events, Start MME S1AP ID shall be read from the CSL. In the case of
S1AP ID Altiostar, when MME S1AP ID may be read from the VSE_MME_UE_S1AP_ID event.
Start eNB UE In the case of Samsung, when eNB S1AP ID is not available from 3GPP message events, Start eNB S1AP ID shall be read from the CSL. In the case of
S1AP ID Altiostar, when eNB S1AP ID may be read from the VSE_ENB_UE_S1AP_ID event.
End Cell ECGI or cell name of the last serving cell from the Cell Trace event. When otherwise not available, in the case of Samsung LTE, the end ECGI may be taken
from Disconnection Information of the CSL.
End eNB eNB ID or eNB name of the last serving cell from the Cell Trace event. When otherwise not available, in the case of Samsung LTE, the end eNB ID or eNB
name may be derived from the CGI taken from Disconnection Information of the CSL.
End PCI Physical Cell Identity of the last serving cell. In the case of Samsung LTE, the end PCI may be read from the Disconnection Information of the last CSL
associated with the call.
End EARFCN DL Downlink E-UTRAN Absolute Radio Frequency Channel Number of the last serving cell
End MME UE MME UE S1AP ID from the last known S1AP message event. In the case of Samsung, End MME UE S1AP ID in the fragment may be set based on the content
S1AP ID of CSL. In the case of Altiostar, End MME UE S1AP ID in the fragment may be set based on the content of the VSE_MME_UE_S1AP_ID event. The End MME UE
S1AP ID of the call will be based on the End MME UE S1AP ID of the last fragment of the call.
End eNB UE eNB UE S1AP ID from the last known S1AP message event. In the case of Samsung, End eNB UE S1AP ID in the fragment may be set based on the content of
S1AP ID CSL. In the case of Altiostar, End eNB UE S1AP ID in the fragment may be set based on the content of the VSE_ENB_UE_S1AP_ID event. The End eNB UE S1AP
ID of the call will be based on the End eNB UE S1AP ID of the last fragment of the call.
Establishment Establishment Cause based on the RRC Connection Request or NB-IoT RRC Connection Resume message received in the Cell Trace session.
Cause
RRC Setup Indicates success or failure of the RRC connection setup procedure in a new RRC connection, including resumed NB-IoT RRC connections.
Result
Setup Time Calculated as the time difference between RRC Connection Request and RRC Connection Setup Complete, or between the NB-IoT RRC Resume Request and
the NB-IoT RRC Connection Resume Complete or NB-IoT RRC Connection Setup Complete.
S1 Setup Result Indicates success (reception of S1 Initial Context Setup Response) or failure (reception of S1 Initial Context Setup Failure) of the S1AP UE Context Setup
procedure
RRC Release [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Release Cause from RRC Connection Release message
Cause

992-0608-08 Rev. 001

S1 Release [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] S1AP Release Cause taken from the UE Context Release or Initial Context Setup Failure messages
Cause
RSRP [dBm] Reference Signal Received Power (RSRP) of the serving cell from the last available Measurement Report. In the case of Samsung, when no Measurement
Report is available, RSRP may be taken from RF Information contained in the CSL.
RSRQ [dB] Reference Signal Received Quality (RSRQ) of the serving cell from the last available Measurement Report. In the case of Samsung, when no Measurement
Report is available, RSRQ may be taken from RF Information contained in the CSL.
DL SINR [dB] DL SINR of the serving cell from last Measurement Report
Start Timing For vendors other than Samsung or Altiostar, Start Timing Advance of each fragment is set to the earliest timing advance of the fragment. Start timing
Advance advance of the call is the start timing advance of the first fragment of the call with start timing advance. Not set for NB-IoT calls. [Samsung] For a fragment,
[Meters/Miles] if both periodic MAC and Type 1 timing advance are available, the earliest Type 1 timing advance is taken as start timing advance for the fragment if it is
earlier, or no later than the value of the Type 1 timer advance timer, than the earliest periodic MAC timing advance, or else earliest periodic MAC timing
advance is used as start timing advance; otherwise, if Type 1 timing advance is available, but periodic MAC timing advance is not, then the earliest Type 1
timing advance is taken as start timing advance; otherwise, if periodic MAC timing advance is available, but Type 1 timing advance is not, then the earliest
MAC timing advance is taken as start timing advance; otherwise, if connection timing advance is present in the CSL, then start timing advance is taken as
start timing advance. The start timing advance of the call is take as the start timing advance of the first constituent fragment of the call, and if start timing
advance is N.A. in the first fragment, it will also be N.A. in the call record. The value of the Type 1 timing advance timer is configurable with a default value of
6 seconds. Values of 0 for MAC timing advance or CSL timing advance are converted to 19 meters. [Altiostar] For a fragment, if both periodic MAC and Type
1 timing advance are available, the earliest Type 1 timing advance is taken as start timing advance for the fragment if it is earlier, or no later than the value
of the Type 1 timer advance timer, than the earliest periodic MAC timing advance, or else earliest periodic MAC timing advance is used as start timing
advance; otherwise, if Type 1 timing advance is available, but periodic MAC timing advance is not, then the earliest Type 1 timing advance is taken as start
timing advance; otherwise, if periodic MAC timing advance is available, but Type 1 timing advance is not, then the earliest MAC timing advance is taken as
start timing advance; The start timing advance of the call is take as the start timing advance of the first constituent fragment of the call, and if start timing
advance is N.A. in the first fragment, it will also be N.A. in the call record. The value of the Type 1 timing advance timer is configurable with a default value of
6 seconds. MAC TA of 0 is converted to 19 meters in the case of Altiostar. [Huawei] Start Timing Advance can be read from any of the following events: UE
periodic radio link MR, UE periodic radio link MR MDT, UE Period TA and UE Period TA MDT.

992-0608-08 Rev. 001

End Timing For vendors other than Samsung or Altiostar, End Timing Advance of a fragment is set to the last timing advance of the fragment. End timing advance of a
Advance call is set to the end timing advance of the last fragment with end timing advance. Not set for NB-IoT calls. [Samsung] In the case of a Samsung fragment, if
[Meters/Miles] Type 1 timing advance (Tadv) and Disconnect CSL timing advance are present in the fragment, end timing advance is set to the last Tadv if it is later than, or
no earlier than the value of the Type 1 timer advance timer from, the Disconnect CSL timing advance, or else end timing advance is taken from Disconnect
CSL timing advance; otherwise, if both Tadv and periodic MAC timing advance are present in the fragment, end timing advance is set to the last Tadv if it is
either later than, or no earlier than the value of the last Type 1 timer advance timer from, the last periodic MAC timing advance, or else is set to the last
periodic MAC timing advance; otherwise, if Disconnect CSL timing advance is present in the fragment, it is taken as end timing advance for the fragment;
otherwise, if Tadv timing advance is present in the fragment, the last Tadv timing advance received is taken as end timing advance; otherwise, if periodic
MAC timing advance is present in the fragment, it is taken as end timing advance for the fragment; otherwise, end timing advance is not set. Values of 0 for
MAC timing advance or CSL timing advance are converted to 19 meters. [Altiostar] If both Tadv and periodic MAC timing advance are present in the
fragment, end timing advance is set to the last Tadv if it is either later than, or no earlier than the value of the Type 1 timer advance timer from the last
periodic MAC timing advance, or else is set to the last periodic MAC timing advance; otherwise, if Tadv timing advance is present in the fragment, the last
Tadv timing advance received is taken as end timing advance; otherwise, if periodic MAC timing advance is present in the fragment, the last timing advance
received is taken as end timing advance for the fragment; otherwise, end timing advance is not set. End timing advance of a call is set to the end timing
advance of the last fragment. Note: Type 1 timing advance (Tadv), Samsung's and Altiostar's implementation of TADV described in TS 36.133, Section 10.3.1
Report mapping, provides 2Ts resolution for timing advance less than or equal to 4096Ts, and 8Ts resolution for timing advance greater than 4096Ts. MAC
timing advance, the timing advance utilized in MAC timing advance commands, is described in TS 36.213, section 4.2.3, and provides 16Ts granularity. The
value of the Type 1 timing advance timer is configurable with a default value of 6 seconds. MAC TA of 0 is converted to 19 meters in the case of Altiostar.
[Huawei] End Timing Advance can be read from any of the following events: UE periodic radio link MR, UE periodic radio link MR MDT, UE Period TA and UE
Period TA MDT.
Start Timing Cell Id or cell name of the first timing advance cell. This will generally be equal to the start cell, but when the earliest timing advance comes from a cell other
Advance Cell than the start cell, the start timing advance cell will differ. Not set for NB-IoT calls.
End Timing Cell Id or cell name of the last timing advance cell. This will generally be equal to the end cell, but when the last timing advance comes from a cell other than
Advance Cell the end cell, the end timing advance cell will differ. Not set for NB-IoT calls.
UE Category Downlink UE Category includes values for WB-E-UTRAN and NB-IoT. When more than one UE Category is available, a prioritization rule is defined which
prioritizes the most recently defined UE Categories over older UE Categories. When Downlink UE Category is not available for a WB-E-UTRAN call, the pre-
Release 12 UE Category is used to determine the UE Category. For an NB-IoT call, the UE Category indicates NB2 if indication of NB2 is received, or NB1 if
NB1 is indicated but NB2 is not, or is not set if neither indication is received. In the case of Samsung only, when UE Category is not available from standard
3GPP signaling, UE Category may be taken from the DL Category of the CSL. In the case of Alcatel-Lucent PCMD, UE Category is derived from the 'UE
Category' (field number 223) of the PCMD rather than from 3GPP signaling. In the case of Ericsson only, when UE Category is not available from standard
3GPP signaling, UE Category may be derived from EVENT_PARAM_UE_CATEGORY_FLEX of the INTERNAL_PROC_UE_CTXT_RELEASE event.

992-0608-08 Rev. 001

Radio Type E-UTRAN Radio Type, if available, is set to indicate either WB-E-UTRAN, the part of E-UTRAN that excludes NB-IoT, or NB-IoT (Narrowband Internet of
Things). NB-IoT allows access to network services via E-UTRAN with channel bandwidth limited to 180 kHz, or 5G EN-DC (E-UTRAN NE Dual Connectivity).
LTE PLMN-ID PLMN-ID of LTE start cell.
EPS [Ericsson, Huawei, Samsung, Nokia] CIoT (Cellular Internet of Things) EPS (Evolved Packet System) Optimization. Although other CIoT Optimizations are
Optimization supported, and more than one optimization may be utilized in the course of a connection, this call table attribute is limited to User Plane (UP) and Control
Plane (CP) CIoT EPS Optimizations. This attribute Indicates 'UP CIot' if UP CIoT EPS Optimization is used during the call, or else indicates 'CP CIoT' if CP CIoT
EPS Optimization is used during the call, or else the protobuf field is not included when there is no indication of either UP CIoT EPS Optimization nor CP CIoT
EPS Optimization.
RRC Re- Number of RRC Connection Reestablishment Request messages during the session
establishment
Attempts
RRC Re- Number of RRC Connection Reestablishment Complete messages during the session
establishment
Successes
RRC Re- Number of RRC Connection Reestablishment Reject messages during the session
establishment
Failures
Intra-frequency Number of RRC Connection Reconfiguration messages containing Mobility Control Info IE without target carrier frequency when neither X2 nor S1 outgoing
Intra-eNB HO handover is underway
Attempts
Intra-frequency Number of RRC Connection Reestablishment Request messages received at source cell when intra-eNB intra-frequency handover is underway
Intra-eNB HO
Failures
Inter-frequency Number of RRC Connection Reconfiguration messages containing Mobility Control Info IE with target carrier frequency when neither X2 nor S1 outgoing
Intra-eNB HO handover is underway
Attempts
Inter-frequency Number of RRC Connection Reestablishment Request messages received at source cell when intra-eNB inter-frequency handover is underway
Intra-eNB HO
Failures

992-0608-08 Rev. 001

Intra-frequency Number of outgoing X2AP Handover Request messages for which there is no related RRC Connection Reconfiguration message that indicates inter-
X2 HO Prep frequency handover. This count includes inter-frequency handover preparation attempts that fail
Attempts
Intra-frequency Number of incoming X2AP Handover Preparation Failure messages and outgoing X2AP Handover Cancel messages that occur before the handover
X2 HO Prep execution phase has been entered. Note that both inter-frequency and intra-frequency X2 handover preparation failure events are included in this count.
Failures
Intra-frequency Intra-frequency X2 Handover Execution Attempts
X2 HO Exec
Attempts
Intra-frequency Number of outgoing X2AP Handover Cancel messages and RRC Connection Reestablishment Request messages received after an RRC Connection
X2 HO Exec Reconfiguration message event that indicates intra-frequency handover and is related to an ongoing X2 handover
Failures
Intra-frequency Intra-frequency X2 Handover Execution Successes
X2 HO Exec
Successes
Inter-frequency Number of outgoing X2AP Handover Request messages for which there is a related RRC Connection Reconfiguration message that indicates inter-frequency
X2 HO Prep handover and the handover preparation succeeded
Attempts
Inter-frequency Inter-frequency X2 Handover Preparation Failures
X2 HO Prep
Failures
Inter-frequency Inter-frequency X2 Handover Execution Attempts
X2 HO Exec
Attempts
Inter-frequency Number of outgoing X2AP Handover Cancel message and RRC Connection Reestablishment Request messages received after an RRC Connection
X2 HO Exec Reconfiguration message event that indicates inter-frequency handover and is related to an ongoing X2 handover
Failures

992-0608-08 Rev. 001

Inter-frequency Inter-frequency X2 Handover Execution Successes
X2 HO Exec
Successes
Intra-frequency Number of S1AP Handover Required messages for which there is no related RRC Connection Reconfiguration message event indicating inter-frequency
S1 HO Prep handover. This count includes inter-frequency handover preparation attempts that fail as well as all intra-frequency preparation attempts regardless of
Attempts success or failure
Intra-frequency Number of S1AP Handover Preparation Failure messages and S1AP Handover Cancel messages that occur before the handover execution phase has been
S1 HO Prep entered. Note that both inter-frequency and intra-frequency S1 handover preparation failure events are included in this count.
Failures
Intra-frequency Number of RRC Connection Reestablishment Request messages received after RRC Connection Reconfiguration message event that includes intra-
S1 HO Exec frequency handover indication and that is related to an ongoing outgoing S1 handover procedure
Failures
Intra-frequency Intra-frequency S1 Handover Execution Successes
S1 HO Exec
Successes
Inter-frequency Number of S1AP Handover Required messages for which there is a related RRC Connection Reconfiguration message event indicating inter-frequency
S1 HO Prep handover and the handover preparation succeeded
Attempts
Inter-frequency Inter-frequency S1 Handover Preparation Failures
S1 HO Prep
Failures
Inter-frequency Number of RRC Connection Reestablishment Request messages received after RRC Connection Reconfiguration message event that includes inter-
S1 HO Exec frequency handover indication and that is related to an ongoing outgoing S1 handover procedure
Failures
Inter-frequency Inter-frequency S1 Handover Execution Successes
S1 HO Exec
Successes
IRAT HO [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Number of S1AP Handover Required messages with Handover Type indicating LTE to UTRAN or LTE to
Attempts GERAN handover added to the number of S1AP Uplink CDMA2000 Tunneling messages with CDMA2000 RAT Type indication 1xRTT or HRPD

992-0608-08 Rev. 001

Handover Out to [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Number of S1AP Handover Required messages with Handover Type indicating LTE to GERAN handover
2G added to the number of S1AP Uplink CDMA2000 Tunneling messages that include CDMA2000 RAT Type 1xRTT
Handover Out to [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Number of S1AP Handover Required messages with Handover Type indicating LTE to UTRAN handover
3G added to the number of S1AP Uplink CDMA2000 Tunneling messages with CDMA2000 RAT Type HRPD indication
Handover Cause [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Set based on Cause IE of the last X2AP Handover Request received or sent, last S1AP Handover Required
sent or last S1AP Handover Request received
Last HO Source [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] ECGI or cell name of source cell of last handover.
Cell
Last HO Target ECGI or cell name of target cell of last handover.
Cell
Last HO Type [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Handover type of last handover
Last HO [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Indicates the result of the last attempted outgoing handover. Indicates success or the reason why the
Disposition handover was not completed
S1 Outgoing HO [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Value of the last S1AP Handover Type taken from the S1AP Handover Required message
Type
S1 Incoming HO [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Value of the last S1AP Handover Type taken from the S1AP Handover Request message
Type
Mobility from E- [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] Purpose from the Mobility from E-UTRA Command message
UTRA Purpose
Redirected [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] ARFCN or Carrier Frequency derived from the RRC Redirected Carrier Information of the RRC Connection
ARFCN Release message
Redirected Radio Access Technology derived from RRC Redirected Carrier Information of the RRC Connection Release message
System
VoLTE eRAB Accumulation of QCI1 eRAB durations calculated from time of eRAB setup as a result of S1 Initial Context Setup, S1 eRAB Setup, X2 Handover Preparation or
Duration S1 Handover Resource Allocation to eRAB release as result of S1 eRAB Release, RRC connection release, or outgoing handover
VoLTE eRAB Mean of all QCI1 eRAB setup times of new eRABs established as a result of the S1AP eRAB Setup and Initial Context Setup procedures as well as existing
Setup Time eRABs established at target eNBs as a result of S1AP Handover Resource Allocation and X2AP Handover Preparation procedures

992-0608-08 Rev. 001

VoLTE eRAB Number of QCI1 eRAB setup attempts contained in S1 Initial Context Setup Request and S1 eRAB Setup Request messages
Attempts
VoLTE eRAB Number of QCI1 eRABs in the process of being setup when an S1 Initial Context Setup Failure message is received and the number of QCI1 eRABs in the
Failed Attempts process of being setup for which a S1 Initial Context Setup Response or S1 eRAB Setup Response message is received that does not include an established
confirmation for the eRAB ID
VoLTE eRAB Number of VoLTE failed attempts with cause of X2 handover, S1 handover, CSFB, and Redirection towards 1XRTT.
Failed Attempts
Due to Mobility
VoLTE eRAB Number of QCI1 eRABs in the active state for which explicit release is requested in S1 eRAB Release Indication or S1 eRAB Release Command message, or
Release which are implicitly released by being active at the time of RRC connection release including Normal Release, Dropped Connection and Redirection
Attempts
VoLTE eRAB Number of QCI 1 eRABs not admitted during outgoing X2 or S1 handover + number of active QCI1 eRABs released by S1 eRAB Release Indication or S1 eRAB
Drops Release Command with S1 cause indicating connection or eRAB drop + number of QCI1 eRABs active at the time of a dropped connection
Video Call eRAB Total duration of QCI=2 E-RAB duration in one fragment or call.
Duration
Video Call eRAB Mean setup time of QCI=2 E-RABs setup during one fragment. The mean setup time for a call is the mean of the mean setup times of the constituent
Setup Time fragments.
Video Call eRAB Number of QCI=2 E-RAB setup attempts in one fragment or call.
Attempts
Video Call eRAB Number of QCI=2 E-RAB setup attempts that fail during one fragment or call.
Failed Attempts
Video Call eRAB Number of QCI=2 E-RABs released during one fragment or call, including those dropped.
Release
Attempts
Video Call eRAB Number of QCI=2 E-RAB dropped during one fragment or call, including those for which setup fails.
Drops
SRVCC Set to true if an SRVCC (Single Radio Voice Call Continuity) Operation Possible indication is received in any of the following message types: X2AP Handover
Capability Request, S1AP Handover Request or S1AP Initial Context Setup Request

992-0608-08 Rev. 001

SRVCC HO Set to the domain indicated if an SRVCC Handover indication is received in an S1AP Handover Required message
Indication
QCI List The QCI list consists of the QCI of each eRAB that is successfully established during the session including eRABs newly established and eRABs admitted to
the eNB as a result of incoming handover. In the case of Samsung, the QCI list may be taken from the CSL when the necessary 3GPP message cell trace
events are not available.
ARP List The ARP list consists of the QCI of each eRAB that is successfully established during the session including eRABs newly established and eRABs admitted to
the eNB as a result of incoming handover.
CSFB Set to true if one of the following conditions is met and RRC Connection Re-establishment procedure is not subsequently attempted at the eNB: the
connection is released with S1AP Cause "CS Fallback Triggered" or "UE Not Available for PS Service"; an RRC Mobility From E-UTRA Command message
containing CSFB indication is received; an S1AP Initial Context Setup Request is received with CS Fallback Indicator; an S1AP UE Context Modification
Request message with CS Fallback Indicator; an HO From EUTRA Preparation Request to CDMA 2000 with dual Rx TX Redirect Indicator
CSFB Type CSFB Type of last CSFB attempt
CSFB Result CSFB Result of last CSFB attempt
eRAB Setup Mean of all RAB setup times of new eRABs established as a result of the S1AP eRAB Setup and Initial Context Setup procedures as well as existing eRABs
Time established at target eNBs as a result of S1AP Handover Resource Allocation and X2AP Handover Preparation procedures
eRAB Attempts Number of eRAB setup attempts contained in S1 Initial Context Setup Request and S1 eRAB Setup Request messages
eRAB Successes Number of eRABs included in eRAB Setup Lists in S1 eRAB Setup Response and S1 Initial Context Setup Response messages for which eRAB-ID has also
been included in an eRAB to be Setup List in either an S1 eRAB Setup Request or S1 Initial Context Setup Request message
eRAB Failed Number of eRABs in the process of being setup when an S1 Initial Context Setup Failure message is received and the number of eRABs in the process of
Attempts being setup for which a S1 Initial Context Setup Response or S1 eRAB Setup Response message is received that does not include an established
confirmation for the eRAB ID
eRAB Release Number of eRABs in the active state for which explicit release is requested in S1AP S1 eRAB Release Indication or S1 eRAB Release Command message, or
Attempts which are implicitly released by being active at the time of RRC connection release including Normal Release, Dropped Connection and Redirection
eRAB Drops Number of eRABs not admitted during outgoing X2 or S1 handover + number of active eRABs released by S1 eRAB Release Indication or S1 eRAB Release
Command with S1 cause indicating connection or eRAB drop + number of eRABs active at the time of a dropped connection
eRAB Normal Number of active eRABs released normally when the RRC connection closed due to Redirection or Normal Release, or when the eRAB Id of the eRAB is
Releases explicitly released in an S1 eRAB Release Indication or eRAB Release Command

992-0608-08 Rev. 001

Last RRC ECGI or cell name of the serving cell at the time of the last RRC measurement report. For Samsung, this is taken from the CSL Disconnection Information ECI
Measurement when last measurement information is taken from the CSL for the call or fragment.
Cell
Last RRC Time of the last RRC Measurement Report. For Samsung, the last RRC measurement report time is set to the Disconnection Information time of the CSL
Measurement when the last measurement report is taken from the CSL.
Time
Last RRC The eARFCN of the last RRC Measurement Report
Measurement
eARFCN
Num of Number of neighbor cells contained in the last RRC measurement report. For Samsung, when the last measurement report is taken from the CSL, the
Neighbors [#] number of neighbor cells of the fragment or call is determined from the number of neighbor cells indicated in the CSL Adjacent Information.
N1 PCI PCI for neighbor 1 in last RRC Measurement Report. For Samsung, when 3GPP Measurement Reports are unavailable N1 PCI may be taken from the
Adjacent Information of the CSL.
N1 Cell Cell ID or cell name of the first neighbor cell
N1 RSRP [dBm] RSRP for neighbor 1 in last RRC Measurement Report. For Samsung, when 3GPP Measurement Report are missing, N1 RSRP may be taken from CSL
N1 RSRQ [dB] RSRQ for neighbor 1 in last RRC Measurement Report. For Samsung, when 3GPP Measurement Report are missing, N1 RSRQ may be taken from CSL
N2 Cell Cell ID or cell name of the 2nd neighbor cell
N2 RSRP [dBm] RSRP for neighbor 2 in last RRC Measurement Report. For Samsung, when 3GPP Measurement Reports are unavailable N2 RSRP may be taken from CSL
N2 RSRQ [dB] RSRQ for neighbor 2 in last RRC Measurement Report. For Samsung, when 3GPP Measurement Reports are unavailable N2 RSRQ may be taken from CSL
N3 Cell Cell ID or cell name of the 3rd neighbor cell

992-0608-08 Rev. 001

N3 RSRP [dBm] RSRP for neighbor 3 in last RRC Measurement Report. For Samsung, when 3GPP Measurement Reports are unavailable N3 RSRP may be taken from CSL
N3 RSRQ [dB] RSRQ for neighbor 3 in last RRC Measurement Report. For Samsung, when 3GPP Measurement Reports are unavailable N3 RSRQ may be taken from CSL
N4 PCI PCI for neighbor 4 in last RRC Measurement Report.
N4 Cell Cell ID or cell name of the 4th neighbor cell
N4 RSRP [dBm] RSRP for neighbor 4 in last RRC Measurement Report.
N4 RSRQ [dB] RSRQ for neighbor 4 in last RRC Measurement Report.
TA Distance Timing Advance Distance for the End Cell may be expressed in either meters or miles in the call table, and in meters only in the LSR output. Not set for NB-
[Meters/Miles] IoT calls.
Intersite Inter Site Distance for End Cell is determined from calculations based on the content of the Network Element table. Inter Site Distance for End Cell may be
Distance expressed in either meters or miles in the call table, and in meters only in LSR output. Not set for NB-IoT calls.
[Meters/Miles]
Range ISD Ratio Range as determined by TA or Propagation Delay (Ratio of TA Distance to InterSite Distance for End Cell). Not set for NB-IoT calls.
Vendor Vendor for this Call

992-0608-08 Rev. 001

UE Power Last Power Headroom Information expressed in dB. In the case of Samsung LTE, the last valid value of MAC power headroom received in the VSE Periodic RF
Headroom [dB] Information event is used as last power headroom. In the case of Nokia LTE, power headroom is taken from the last received MAC PHR event for the
session. In the case of Altiostar, the last UE Power Headroom of the fragment or call is read from the last received VSE_UL_SCHED event containing valid
avg_phr field. In the case of Huawei, the last UE Power Headroom of the fragment or call is read from the last received UE periodic radio link MR or UE
periodic radio link MR MDT event containing valid DL Wideband CQI Code0 field.
Last UE Tx [Samsung] Transmission power of UE when the call disconnects from the eNB. Samsung estimates UE transmission power from Power Headroom Reports
Power [dBm] from UE. The Last UE TX Power of a fragment reflects the value of the ueTxPower field of the last CSL associated with the fragment, while the Last UE TX
Power shown in the Call Table reflects the value of ueTxPower field of the last fragment of the call.
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 as they are created starting with the value '1.' Fragment ID is not expressed in Call Table.
Composite Call Indicates a composite call that has been created from more than one constituent call fragment by the LTE Call Stitcher function.
Last VoLTE eRAB Last VoLTE eRAB start time
Start Time
Last VoLTE eRAB Last VoLTE eRAB end time
End Time
Last VoLTE eRAB Last VoLTE eRAB end time minus last VoLTE start time and VoLTE setup time
Duration
Last VoLTE eRAB Last VoLTE eRAB release cause
Release Cause
Last Video Call Last video call eRAB release cause
eRAB Release
Cause
VoLTE eRABs Number of VoLTE eRAB with emergency ARP
with Emergency
ARP

992-0608-08 Rev. 001

Mean PDCP [Huawei] Total number of PDCP SDU bytes received in the uplink over all E-RABs divided by the accumulated collection period. The number of uplink PDCP
Throughput UL SDU bytes is accumulated over UL Data Volume of the E-RAB Throughput Stat List entry for each E-RAB for every Huawei throughput periodic statistical
[kbps] event received. The collection period of each Huawei throughput periodic statistical event is determined by taking the largest collection period among the
Throughput Stat List UL Data Transmission Time entries for the E-RABs. It is assumed that the uplink PDCP SDU byte counts are reset for each E-RAB at the
onset of the each collection period.
Mean PDCP [Huawei] Total number of PDCP SDU bytes received in the downlink over all E-RABs divided by the accumulated collection period. The number of downlink
Throughput DL PDCP SDU bytes is accumulated over DL Data Volume of the E-RAB Throughput Stat List entry for each E-RAB for every Huawei throughput periodic
[kbps] statistical event received. The collection period of each Huawei throughput periodic statistical event is determined by taking the largest collection period
among the Throughput Stat List DL Data Transmission Time entries for the E-RABs. It is assumed that the downlink PDCP SDU byte counts are reset for each
E-RAB at the onset of the each collection period.
PUSCH SINR [Nokia, Samsung, Ericsson, Altiostar] Last reported uplink PUSCH signal-to-interference-plus-noise ratio (SINR). For Nokia LTE, PUSCH SINR is read from the
[dB] MAC UL SINR message. For Samsung LTE, PUSCH SINR is read from the VSE Periodic RF Information event. For Altiostar, PUSCH SINR of the fragment or call
is read from the last received VSE_UL_SCHED event containing valid Avg_sinr field.
E-UTRAN [Samsung] E-UTRAN access network setup time: This is defined as the difference between the CSL Setup and Attempt Times. The Setup time is the
Connection timestamp of the Initial Context Setup Response message for the times at which the handover process ends normally and the call enters the connected
Setup Time state. The Attempt time is the timestamp of the RRC Connection Request message or the Handover Request message
Call Type [Samsung] Samsung CSL Call Type of the CSL record
Call Release [Samsung] Samsung Call Summary Log (CSL) Call Release Cause taken from the last CSL
Cause
Last RRC [Samsung] The last RRC Connection Reestablishment case of the call with QCI #1. This is taken from the last CSL RRE Information block received.
Reestablishment
Case
Mean [Samsung] Mean CQI calculated from all CQI counts contained in all received VSE_PERIODIC_RF_INFORMATION events. This is the weighted average of the
Cumulative CQI MAC_CQI_0..MAC_CQI_15 fields of the received VSE_PERIODIC_RF_INFORMATION events during the call or fragment.
Last CQI [Samsung] Last CQI associated with the RRC Connection taken from the CSL
Last UL Rx [Samsung] The last received value for uplink received interference power, including thermal noise, is taken from the last received VSE Periodic RF
Interference Information event received for the call session. Received interference power is read from the MAC_RX_INTERFERENCE_UL field of the VSE Periodic RF
Power [dBm] Information message event. This measurement corresponds to the 'Received Interference Power' defined in 3GPP TS 36.214.

992-0608-08 Rev. 001

PUCCH SINR [Samsung, Ericsson] Last PUCCH SINR expressed in dB. For Samsung LTE, the last valid PUCCH SINR received in the VSE Periodic RF Information event is
[dB] utilized.
RLC PDU DL [Samsung] For Samsung LTE, Downlink RLC PDU bytes transmitted calculated by summing over all eRAB of the CSL. [ALU] Number of bytes sent in the
Volume [bytes] downlink direction for the first time over best effort bearers (QCI value 5-9) only over the RLC interface . Collected over both Secondary and Tertiary PCMD
records.
RLC PDU UL [Samsung] For Samsung LTE, uplink RLC PDU bytes received calculated by summing over all eRAB of the CSL. [ALU] Number of uplink RLC PDU bytes
Volume [bytes] received over best effort bearers (QCI values 5-9} including retransmissions. This is the aggregation over both secondary and tertiary PCMD records for the
subscriber during the call.
RLC PDU DL [Samsung] Downlink RLC PDU bytes retransmitted calculated by summing over all eRAB of the CSL. [ALU] Downlink RLC bytes retransmitted over best effort
Retransmitted (QCI values 5-9) bearers only. The total is collected over both secondary and tertiary PCMD records.
Volume [bytes]
RLC PDU DL [Samsung] Ratio of RLC DL Retransmitted Data Volume (bytes) to RLC DL Data Volume (bytes) expressed as a percentage. Note that this ratio can be greater
Retransmit Rate than 100% when the value of RLC RL Retransmitted Data Volume in the CSL exceeds the value of RLC DL Data Volume in the CSL. In the past, the RLC Data
[%] Volume counts contained in the CSL have been known to reflect only the activity from the time of the last intra-eNB handover at the eNB and thus may not
reflect all of the activity described by the CSL record. [ALU] Ratio of DL RLC BE Retransmitted kbytes to DL RLC BE Transmitted kbytes.
S1-U UL Data [Samsung] Uplink GTP-U PDU data volume on S1-U interface in bytes summed over all eRAB of the CSL
Volume [bytes]
S1-U DL Data [Samsung] Downlink GTP-U PDU data volume on S1-U interface in bytes summed over all eRAB of the CSL
Volume [bytes]
Mean Uplink IP [Samsung] Mean Uplink IP Throughput calculated by dividing S1-U UL Data Volume (based on CSL txDataToSG over all RABs) divided by CSL Call Segment
Throughput Duration.
[kbps]
Mean Downlink [Samsung] Mean Downlink IP Throughput calculated by dividing S1-U DL Data Volume (based on CSL rxDataFromSG over all RABs) divided by CSL Call
IP Throughput Segment Duration.
[kbps]
MAC DL RE [Samsung] Total downlink assigned resource element count accumulated over all valid MAC_RE_DL contained in received VSE_PERIODIC_RF_INFORMATION
[resource events.
elements]

992-0608-08 Rev. 001

MAC UL RE [Samsung] Total uplink assigned resource element count accumulated over all valid MAC_RE_UL contained in received VSE_PERIODIC_RF_INFORMATION
[resource events.
elements]
MAC DL RB [Samsung] Total downlink assigned resource block count accumulated over all valid MAC_RB_DL contained in received VSE_PERIODIC_RF_INFORMATION
[resource events.
blocks]
MAC UL RB [Samsung] Total downlink assigned resource block count accumulated over all valid MAC_RB_UL contained in received VSE_PERIODIC_RF_INFORMATION
[resource events.
blocks]
MAC DL RE/RB [Samsung] Ratio of total MAC DL RE to total MAC DL RB.
MAC UL RE/RB [Samsung] Ratio of total MAC UL RE to total MAC UL RB.
Last DL UE to [Samsung] Ratio of downlink scheduled TTI for the UE to the total downlink TTI for the cell. Calculated as the ratio of MAC_TTI_DL / MAC_TTI_DL_CELL_TOTAL
Cell TTI Ratio in the last VSE_PERIODIC_RF_INFORMATION event received.
Last UL UE to [Samsung] Ratio of uplink scheduled TTI for the UE to the total uplink TTI for the cell. Calculated as the ratio of MAC_TTI_UL / MAC_TTI_UL_CELL_TOTAL in the
Cell TTI Ratio last VSE_PERIODIC_RF_INFORMATION event received.
Mean eNB Rank [Samsung] Mean eNB Rank Indicator calculated as the ratio of weighted downlink rank indicator counts to unweighted downlink indicator counts over all
Indicator received VSE_PERIODIC_RF_INFORMATION events. The numerator is calculated as the sum of MAC_RI_DL_0 + MAC_RI_DL_1 + MAC_RI_DL_2 + MAC_RI_DL_3
over each VSE_PERIODIC_RF_INFORMATION received and the denominator is calculated as the sum of MAC_RI_DL_0 + MAC_RI_DL_1 + MAC_RI_DL_2 + MAC_
RI_DL_3 over each VSE_PERIODIC_RF_INFORMATION received. [Ericsson] Sample weighted mean of Rank Indicator.
Mean UE Rank [Samsung] Mean UE Rank Indicator calculated as the ratio of weighted uplink rank indicator counts to unweighted uplink indicator counts over all received
Indicator VSE_PERIODIC_RF_INFORMATION events. The numerator is calculated as the sum of (MAC_RI_UL_0*1) + (MAC_RI_UL_1*2) + (MAC_RI_UL_2*3) + (MAC_RI_UL_
3*4) over each VSE_PERIODIC_RF_INFORMATION received and the denominator is calculated as the sum of MAC_RI_UL_0 + MAC_RI_UL_1 + MAC_RI_UL_2 +
MAC_RI_UL_3 over each VSE_PERIODIC_RF_INFORMATION received.
Mean MAC BLER [Samsung] Mean MAC uplink BLER (Block Error Rate) calculated by dividing the sum of all VSE_PERIODIC_RF_INFORMATION.MAC_BLER_UL content by the
UL [%] count of all valid VSE_PERIODIC_RF_INFORMATION.MAC_BLER_UL received, including the value zero.
Transmission [Samsung] Transmission Mode 1 percentage calculated by dividing the number of Transmission Mode 1 (MAC_TX_MODE_1) counts by the total number of
Mode 1 [%] transmission mode counts (MAC_TX_MODE_1..MAC_TX_MODE_10) counts received in VSE_PERIODIC_RF_INFORMATION events. [Ericsson] Transmission
Mode 1 percentage calculated from received INTERNAL_PER_RADIO_UE_MEASUREMENT events

992-0608-08 Rev. 001

Transmission [Samsung] Transmission Mode 10 percentage calculated by dividing the number of Transmission Mode 10 (MAC_TX_MODE_10) counts by the total number
Mode 10 [%] of transmission mode counts (MAC_TX_MODE_1..MAC_TX_MODE_10) counts received in VSE_PERIODIC_RF_INFORMATION events. [Ericsson] Transmission

992-0608-08 Rev. 001

VoLTE RTP Gap [Samsung] A VoLTE no RTP gap indication is indicated if a received CSL indicates that a PDCP or MAC uplink or downlink gap between RTP packets has been
detected over a QCI#1 radio bearer. No RTP gaps are determined from the MAC_UP_NO_RTP, MAC_DL_NO_RTP, PDCP_UL_NO_RTP and PDCP_DL_NO_RTP
fields of the Call Debugging Information of the CSLs associated with the call. A no RTP gap is detected within the PDCP layer when uplink or downlink traffic
for a QCI#1 radio bearer is not detected for the period of the Samsung noRtpTimer. A no RTP is detected within the MAC layer if scheduling is not executed
for a downlink or uplink section of a QCI#1 radio bearer within expected time limit when RTP packets are waiting to be transmitted.
VoLTE One Way [Samsung] A VoLTE one-way audio warning is indicated when either of the RLC uplink or downlink no-packet delay exceeds the no-packet delay threshold set
Audio Warning by IRIS, or when either the RLC uplink or downlink zero-BO count exceeds the zero-BO count threshold set by IRIS. The RLC no-packet delay is taken from the
RLC_UL_NO_PACKET_DELAY of CSL Call Debugging Information for the uplink and from the RLC_DL_NO_PACKET_DELAY of CSL Call Debugging Information
for the downlink. No-packet delay counts measure the number of TTIs from setup of a QCI#1 bearer until the reception of the first packet. RLC zero-BO
counts are taken from the RLC_UL_ZERO_BO_CNT of CSL Call Debugging Information for the uplink and from the RLC_DL_ZERO_BO_CNT of CSL Call
Debugging Information for the downlink. The zero-BO count is the number of times that BO is zero for a QCI#1 radio bearer in the indicated direction for a
duration greater than that of the noRtpTimer.
VoLTE [Samsung] VoLTE scheduling error indicates that the RLC downlink no scheduling count for at least one CSL exceeds the threshold set by IRIS. The VoLTE
Scheduling Error downlink no scheduling count is read from the CSL RLC_DL_NO_SCHEDULING field of the CSL Call Debugging Information. The VoLTE downlink no scheduling
count indicates the number of times that downlink BO is present for a QCI#1 radio bearer for a duration longer than that allowed by the noRtpTimer.
VoLTE ROHC [Samsung] VoLTE ROHC error indicates that the VoLTE ROHC decompression error count exceeds the threshold set in IRIS in at least one CSL associated
Error with the call. The ROHC_DECOMP_ERR_CNT count of the CSL Call Debugging Information is read to determine the VoLTE ROHC decompression error count.
The VoLTE decompression error count is determined within PDCP for QCI#1 radio bearer.
UDC Enabled [Samsung] Indicates whether Uplink Data Compression (UDC) has been enabled during the fragment or call.
Carrier Total time that Carrier Aggregation Service was active
Aggregation
Service Time
[ms]
Carrier Ratio of total Carrier Aggregation Service time to call duration
Aggregation
Service Rate [%]
CSL Event [Samsung] CSL Event contains the reason for closing the CSL, which can be release of the RRC connection, redirection or handover to other eNB or Radio
Access Technology (RAT)
Call Segment [Samsung] Calculated from the difference between the Disconnect and Attempt timestamps in the Call Summary Log and corresponds to the portion of the
Duration call summarized in the log

992-0608-08 Rev. 001

Angle of Arrival [Nokia, ZTE] Last reported Angle of Arrival in degrees. In the case of Nokia LTE, the value is taken from the last valid Angle of Arrival contained in a MAC
AOA event.
Mean MAC [Nokia] Total number of bytes received in the uplink over both GBR as well as non-GBR bearers at the MAC layer divided by the accumulated collection
Throughput UL period. The number of GBR bytes is accumulated over utUlsReceivedGbrBytes of the MAC_UL_UeThroughput event and the number of non_GBR bytes is
[kbps] accumulated over utUlsReceivedNonGbrBytes of the MAC_UL_UeThroughput event. The collection period of each MAC_UL_UeThroughput is taken from
utNumOfReceivedTxAll (number of received transmissions). It is assumed that the Nokia non-GBR and GBR uplink byte counts are incremental for the call
session and do not wrap-around at 4294967295 bytes.
Mean MAC [Nokia] Total number of bytes sent in the downlink over both GBR as well as non-GBR bearers at the MAC layer divided by the accumulated collection period.
Throughput DL The number of GBR bytes is accumulated over utDlsSentGbrBytes of the MAC_DL_UeThroughput event and the number of non_GBR bytes is accumulated
[kbps] over utDlsSentNonGbrBytes of the MAC_DL_UeThroughput event. The collection period of each MAC_DL_UeThroughput is taken as the sum of
utSingleCWTx (number of single codeword transmissions) and utDualCWTx (number of dual codeword transmissions). It is assumed that the Nokia non-GBR
and GBR downlink byte counts are incremental for the call session and do not wrap-around at 4294967295 bytes.
Initial NAS [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar] The initial NAS request
Request
Initial NAS [Ericsson, Nokia, Samsung, Huawei, ZTE, Altiostar]The response to initial NAS request
Response
OEM RRC Setup [Ericsson] Ericsson internal cause value for RRC setup
Cause
OEM S1 Setup [Ericsson] Internal S1 Initial UE Context Setup Cause
Cause
OEM S1 Release [Ericsson] S1 UE Context Release Cause In Ericsson Internal Event
Cause
OEM Internal [Ericsson] Internal Release Cause
Release Cause
Release with [Ericsson] eRAB released with data in buffer
Data Lost
Data Lost [Ericsson] Data lost at session release
Release Node [Ericsson] The release node for the UE context

992-0608-08 Rev. 001

Mean CQI [Ericsson,ALU] Mean CQI in last eNB measurement report. [Samsung] Last CQI associated with the RRC Connection taken from the CSL. [Altiostar] Last
received valid average value received in the fragment or call read from the avg_cqi field of the VSE_DL_SCHED event. [Nokia] Last received valid average
value for wideband Channel Quality Indicator received in the utMeanLaWbCqi field of the MAC_DL-UeThroughput event. [Huawei] Last received valid value
for wideband Channel Quality Indicator received in the DL Wideband CQI Code0 field of the UE periodic radio link MR and UE periodic radio link MR MDT
events.
CQI Cell [Ericsson, Altiostar, Nokia, Huawei] Cell for last mean CQI
MAC Volume DL [Ericsson] DL MAC volume during the RRC connection [Nokia] The cumulative number of bytes sent over non-GBR as well as GBR downlink bearers.
[bytes] Downlink MAC bytes are read from the utDlsSentNonGbrBytes and utDlsSentGbrBytes fields of the periodic MAC_DL_UeThroughput message. It is assumed
that the Nokia non-GBR and GBR downlink byte counts are incremental for the call session and do not wrap-around between events.
MAC Volume UL [Ericsson] UL MAC volume during the RRC connection [Nokia] The cumulative number of bytes received over non-GBR as well as GBR uplink bearers. Uplink
[bytes] MAC bytes are read from the utUlsReceivedNonGbrBytes and utUlsReceivedGbrBytes fields of the periodic MAC_UL_UeThroughput message. It is assumed
that the Nokia non-GBR and GBR uplink byte counts are incremental for the call session and do not wrap-around between events.
PDCP Volume [Ericsson, Altiostar, Huawei] DL PDCP DRB volume during the RRC connection. Altiostar downlink PDCP volume is calculated from VSE_PDCP total_DL_bytes.
DL [bytes] For Huawei, the DL Data Volume of each E-RAB contained in the E-RAB Throughput Stat List of each Huawei throughput periodic statistical event is summed
over each fragment and the composite call record to provide downlink PDCP SDU data volume.
PDCP Volume [Ericsson, Altiostar, Huawei] UL PDCP DRB volume during the RRC connection. Altiostar uplink PDCP volume is calculated from VSE_PDCP total_UL_bytes. For
UL [bytes] Huawei, the UL Data Volume of each E-RAB contained in the E-RAB Throughput Stat List of each Huawei throughput periodic statistical event is summed
over each fragment and the composite call record to provide uplink PDCP SDU data volume.
Mean PDCP DRB [Ericsson] Mean DL throughput for PDCP DRB
Throughput DL
[kbps]
Mean PDCP DRB [Ericsson] Mean UL throughput for PDCP DRB
Throughput UL
[kbps]
Mobile Number [ALU] Mobile Subscriber ISDN (Integrated Services Digital Network) Number
End m-TMSI [ALU, Ericsson, Nokia, Huawei, ZTE, Altiostar] m-TMSI at PCMD end OR the m-TMSI will be picked from NAS message if possible when Diameter feature is
active and a new GUTI assignment is detected.
eNB CFCQ [ALU] This field indicates the Final Class Qualifier code for the UE Context. It is used with CFC and SCFCQ to identify the disposition for the procedure
eNB SCFCQ [ALU] This field indicates the Secondary Final Class Qualifier code for the UE Context.

992-0608-08 Rev. 001

Procedure [ALU]MME Procedure Call Final Class Qualifier
SCFCQ
Mobility Trigger [ALU] Includes Invalid, radio condition, congestion control, CSFB, load balancing, active UE capacity limit during OOT-to-active transition, CAC failure
Reason
Start Trigger [ALU] Trigger for initiation of the PCMD
Reason
Procedure ID [ALU] MME Procedure ID
S1AP Procedure [ALU] S1 Cause values specified in 36.413
Context
Qualifier
Type of Initiation [ALU] Includes Invalid, UE Origin, UE Term and Handover
End GUMMEI End Globally Unique MME Identifier (GUMMEI) of the last fragment, or in the case of a fragment, the end GUMMEI of the fragment.
Last Inter-cell [ALU] This parameter indicates success or the failure reason code of last inter-cell, intra-eNodeB Handover failure for the interval that the UE is served by
Intra-eNB HO the eNodeB.
Disposition
Last X2 HO [ALU] This parameter indicates success or the failure reason code of last X2 Handover failure
Disposition
Last S1 HO [ALU] This parameter indicates success or the failure reason code of last S1 Handover failure
Disposition
Last intra-cell [ALU] This parameter indicates success or the failure reason code of last intra-cell Handover failure
HO Disposition
RLC SDU UL [ALU] UL RLC SDU GBR & BE Received bytes
Volume [kbytes]
MAC UL PDUs [ALU] UL Total MAC PDUs for Initial Transmission
HARQ DL Initial [ALU] Number of DL Initial HARQ Transmissions
Transmissions
by DS

992-0608-08 Rev. 001

HARQ DL [ALU] Number of DL HARQ Retransmissions
Retransmissions
by DS
Mean UL SINR [ALU, ZTE] Average UL Signal to Interference Noise Ratio
[dB]
HARQ DL [ALU] (Number of DL HARQ Retransmissions)/(Number of DL Initial HARQ Transmissions)
Retransmit Rate
by DS [%]
DL TTIs UE [ALU] Total number of downlink TTIs scheduled to the UE during the PCMD collection interval.
Scheduled
DL MIMO TTIs [ALU] Total number of downlink TTIs scheduled to the UE when the UE is in a MIMO transmission state.
UE Scheduled
RLC UL [ALU] UL RLC SDU Transmitted bytes divided by the # of TTIs UE's UL RLC BE PDU received
Throughput
[kbps]
RLC DL [ALU] DL RLC PDU Transmitted bytes divided by the DL data Transmission time for BE bears
Throughput
[kbps]
Last 1xCSFB [ALU] This parameter indicates the failure reason code of last 1xCSFB
Failure Code
Last e1xCSFB [ALU] This parameter indicates success or the failure reason code of last e1xCSFB
Failure Code
RLF Reports Number of RLF Report received
RLF Cause RLF cause in RLF report
MDT Location Time of last MDT location report from any fragment of the call. MDT location is set to call end location if it is within certain time. Default is 12s.
Time
MDT Latitude Latitude reported in last MDT from any fragment of the call. MDT location is set to call end location if it is within certain time. Default is 12s.
[degrees]

992-0608-08 Rev. 001

MDT Longitude Longitude reported in last MDT in any fragment. MDT location is set to call end location if it is within certain time. Default is 12s.
[degrees]
MDT Altitude Altitude reported in last MDT data from last fragment of the call. Positive is above WGS84 ellipsoid surface. Negative is below WGS84 ellipsoid surface.
[meters]
MDT Accuracy Uncertainty in meters of last MDT location from last fragment of the call
[meters]
MDT Speed Horizontal speed in kilometers per hour from last MDT in last fragment of the call
[km/h]
Number of Number of cross vendor stitching in the composite call.
Cross Vendor
Stitching
5G NR Serving NR CGI of last 5G EN-DC PSCell
Cell
5G NR Serving PCI of last 5G EN-DC PSCell
PCI
5G NR Serving ARFCN of last 5G EN-DC PSCell
ARFCN
5G EN-DC The duration for 5G EN-DC
Duration
5G EN-DC The ratio of 5G EN-DC duration to total RRC duration
Duration Rate
[%]
Maximum Maximum number of carrier components during the RRC. LTE PCC, SCC, and 5G EN-DC are included.
Number of
Carrier
Components

992-0608-08 Rev. 001

Average Time weighted average number of carrier components during the RRC. LTE PCC, SCC, and 5G EN-DC are included. It's calculated by total duration of all
Number of carrier components divided by RRC duration.
Carrier
Components
5G EN-DC SgNB Number of 5G EN-DC SgNB addition attempts.
Addition
Attempts
5G EN-DC SgNB Number of 5G EN-DC SgNB addition failures
Addition Failures
5G EN-DC SgNB Number of 5G EN-DC SgNB abnormal releases

Drops
Last 5G EN-DC The X2 release cause for last 5G EN-DC SgNB release
Release Cause
5G EN-DC Downlink data volume transmitted by SgNB during 5G EN-DC from X2 or S1 'Secondary RAT Data Usage Report'
Downlink
Volume [bytes]
5G EN-DC Uplink data volume received by SgNB during 5G EN-DC from X2 or S1 'Secondary RAT Data Usage Report'
Uplink Volume
[bytes]
Time of Last RRC Time of last LTE RRC Measurement Report with 5G NR Cell
Measurement
Report with 5G
NR Cell
5G NR Last NR CGI of last 5G EN-DC measurement cell
Measurement
Cell

992-0608-08 Rev. 001

5G NR Last PCI of last 5G EN-DC measurement cell
Measurement
PCI
5G NR Last ARFCN of last 5G EN-DC measurement cell
Measurement
ARFCN
5G NR RSRP RSRP for last 5G EN-DC measurement cell
[dBm]
5G NR RSRQ RSRQ for last 5G EN-DC measurement cell
[dB]
5G NR DL SINR DL SINR for last 5G EN-DC measurement cell
[dB]
SSB Index 0 in SSB Index 0 in last 5G EN-DC measurement
Last 5G NR
Measurement
RSRP for Last RSRP for SSB Index 0 in last 5G EN-DC measurement
SSB Index 0
[dBm]
RSRQ for Last RSRQ for SSB Index 0 in last 5G EN-DC measurement
SSB Index 0 [dB]
DL SINR for Last DL SINR for SSB Index 0 in last 5G EN-DC measurement
SSB Index 0 [dB]
5G EN-DC SgNB Number of 5G EN-DC SgNB change attempts during the call
Change
Attempts
5G EN-DC SgNB Number of 5G EN-DC SgNB change failures during the call
Change Failures

992-0608-08 Rev. 001

5G EN-DC SgNB Number of 5G EN-DC SgNB Modification attempts during the call
Modification
Attempts
5G EN-DC SgNB Number of 5G EN-DC SgNB Modification failures during the call
Modification
Failures

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 Common-LTE 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 Common-LTE 63

Uploaded by

Copyright:

Available Formats

TrueCall

System Features Document

Software Version 6.3.0

Appendix A: Common LTE 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

Common LTE What’s New 5

TrueCall System Features Document 4

The following KPIs were added, modified, or deleted for 6.3.0:

KPI Description of Change

Call Attribute/LSR Description of Change

TrueCall System Features Document 5

Call Attribute/LSR Description of Change

TrueCall System Features Document 6

Nokia Data Collection and Analytics Platforms (DCAP)

LTE GEO Interface

TrueCall System Features Document 7

Approval Date – 2018-08-03

Please contact NETSCOUT PLM for more information.

A.1 Common LTE KPIs

Note: KPI Explorer Headings are in bold text.

Nokia PCMD is referred to as Alcatel-Lucent in this section.

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 8

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 9

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 10

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 11

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 12

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 13

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 14

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 15

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 16

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 17

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 18

KPI Name Description Unit Vendor Widget Support

Map KPI Top NE Top Top Device

TrueCall System Features Document 19

KPI Name Description Unit Vendor Widget Support