UD - nBA - Metric User Guide - 630

nGenius Business Analytics
Metrics User Guide

Me tr ic s Us e r Gu id e
Software Version 6.3

Rev. 001
April 2020
© NETSCOUT CONFIDENTIAL & PROPRIETARY

Ver. 6.3 | April 2020
992-0690-08 Rev. 001
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
Metrics User Guide 2

Ver. 6.3 | April 2020
992-0690-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-0690-08-001

Table of Contents
Me tr ic s Us e r Gu id e 1
T a b le o fC o n te n ts 4
What's New in nGenius Business Analytics 6.3 Metrics User Guide 6
Revision History 7
1 Introduction 8
1.1 About nBA Metrics 8
2 6.1.1.1213 Metric Pack 9
3 Control Plane Metrics - Data Fields Descriptions 10
3.1 EMM Attach-S1-MME 11
3.2 ESM Dedicated_Bearer_Activation - S1-MME 12
3.3 ESM Default_Bearer_Activation - S1-MME 13
3.4 ESM PDN_Connectivity - S1-MME 14
3.5 GMM Attach – Gb 15
3.6 GMM Attach – IuPS 16
3.7 GTP v1 – Gn 17
3.8 GTP v2 -S11 18
4 User Plane Metrics 20
5 Voice Metrics 23
5.1 Media Management 24
5.2 VoLTE Call Management 25
5.2.1 The Invite - VoLTE Call Management 26
5.3 VoLTE Call Registration 29
5.3.1 VoLTE Call Management 29
A Appendix A - ASI Data Set Field Descriptions (Subscriber Tables only) 30
A.1 Control Plane Data Set Field Description 31
A.2 User Plane Data Set Field Descriptions 35
A.3 Media Data Set Field Descriptions 39
A.4 Message Name Detail 44
A.4.1 DIAMETER 44

Ver. 6.3 | April 2020
992-0690-08 Rev. 001
A.4.2 GTP 45
A.4.3 SIP Control 46
A.4.4 S1-AP/S1-MME 46
A.4.5 Gb/IuPS 47
A.4.6 GSMA 47
A.4.7 IuCS 48
A.4.8 ISUP 48
A.4.9 BICC 49
A.4.10 MAP 50
A.4.11 CAP 51

Ver. 6.3 | April 2020 What's New in nGenius Business Analytics 6.3 Metrics User Guide
992-0690-08 Rev. 001
What's New in nGenius Business

Analytics 6.3 Metrics User Guide
There are no enhancements for nGenius Business Analytics 6.3 Metrics User Guide.

Revision History
The revision history shows the documentation updates for this release. These updates include new
features and changes to existing features. They also include changes resulting from documentation
requests and issues.
Date Revision Reference Summary

April 2020 001 - Initial Release

1 Introduction
This user guide details the formula of the default metrics delivered as part of nBA.
1.1 About nBA Metrics

nBA allows formula of ASI field values to be used to create Metrics. The formulae of default Metrics
are documented here, together with their definition, to allow end users to edit and create their own
metrics.
Adaptive Service Intelligence (ASI) is NETSCOUT’s patented technology for efficient, real-time,
contextual measurement and analysis of service, network, application and subscriber experience.
Section 1 Appendix A - ASI Data Set Field Descriptions (Subscriber Tables only) contains a description
of the ASI data set fields used to create these Metrics.

2 6.1.1.1213 Metric Pack
The 6.1.1.1213 release of nBAintroduces the following changes:
Explorer:
l EMM Attach labels prefixed with ‘4G’ and moved to new ‘NETSCOUT_DATA’ Pack
l IuPS GMM Attach labels prefixed with ‘3G’ and moved to new ‘NETSCOUT_DATA’ Pack
l ESM Dedicated, Default Bearer and PDN Connectivity Metrics in new ‘NETSCOUT_DATA’
Pack
l 2G Attach Metrics in new ‘NETSCOUT_DATA’ Pack
l New Metrics Retransmission Rate, TCP Latency, Round Trip Time and Time to First Byte in
new ‘NETSCOUT_DATA’ Pack
l New ‘NETSCOUT_VOICE’ Metric Pack including VoLTE Media and Call Metrics.
l These are available for new deployments by default; otherwise upgrading customers need
to download and import the new metric packs and manually reconfigure their metric
libraries as required to align with their existing Metrics and maintain support for existing
dashboards.
MicroStrategy:
l New Control Plane EMM folder containing 4G Attach Metrics

l New Control Plane ESM folder containing ESM Dedicated, Default Bearer and PDN
Connectivity Metrics
l New Metrics Retransmission Rate, TCP Latency, Round Trip Time and Time to First Byte in
User Plane folder.
l New SIP folder containing VoLTE Call Metrics.
l New Media VoLTE RTP folder containing VoLTE Media Metrics
l These are available for new deployments by default and automatically merged into the
customer’s existing metric folders during an upgrade.

3 Control Plane Metrics - Data Fields
Descriptions
The following Data Control Plane Metrics are available in Explorer and MicroStrategy by default
(unless otherwise indicated).

Ver. 6.3 | April 2020 3 Control Plane Metrics - Data Fields Descriptions
992-0690-08 Rev. 001
3.1 EMM Attach-S1-MME

The following Metrics have been created by counting the number of rows where the value of the Message field is ‘EMM-ATTACH’ and the
value of the Status field is either ‘Error, Success or Timeout’.
Metric Label Computation

4G Attach Attempt Count where Message is EMM-ATTACH
4G Attach Avg Duration (ms) (SUM (Response Time/1000)/SUM Event Count) where Message is EMM-ATTACH and Status is Success
4G Attach Fail Count where Message is EMM-ATTACH and Status is Error
4G Attach Fail Rate % (Attach_Fail_Count/( Attach_Fail_Count+ Attach_Success_Count)) *100
4G Attach Success Count where Message is EMM-ATTACH and Status is Success
4G Attach Success Rate % (Attach_Success_Count/( Attach_Fail_Count+ Attach_Success_Count) )*100
4G Attach Timeout Rate % (Attach_Timeouts_Count/ Attach_Attempts_Count)*100
4G Attach Timeouts Count where Message is EMM-ATTACH and Status is Timeout

992-0690-08 Rev. 001
3.2 ESM Dedicated_Bearer_Activation - S1-MME

The following Metrics have been created by counting the number of rows where the value of the Message field is ‘ESM-ACT-DED-BEAR’ and
the value of the Status field is either ‘Error, Success or Timeout’.

Dedicated_Bearer_Activation Attempt Count where Message is ESM-ACT-DED-BEAR
Dedicated_Bearer_Activation Avg Duration (ms) (SUM (Response Time/1000)/SUM Event Count) where Message is ESM-ACT-
DED-BEAR and Status is Success
Dedicated_Bearer_Activation Fail Count where Message is ESM-ACT-DED-BEAR and Status is Error
Dedicated_Bearer_Activation Fail Rate % (Attach_Fail_Count/( Attach_Fail_Count+ Attach_Success_Count)) *100
Dedicated_Bearer_Activation Success Count where Message is ESM-ACT-DED-BEAR and Status is Success
Dedicated_Bearer_Activation Success Rate % (Attach_Success_Count/( Attach_Fail_Count+ Attach_Success_Count) )*100
Dedicated_Bearer_Activation Timeout Rate % (Attach_Timeouts_Count/ Attach_Attempts_Count)*100
Dedicated_Bearer_Activation Timeouts Count where Message is ESM-ACT-DED-BEAR and Status is Timeout

992-0690-08 Rev. 001
3.3 ESM Default_Bearer_Activation - S1-MME

The following Metrics have been created by counting the number of rows where the value of the Message field is ‘ESM-ACT-DEF-BEAR’ and

Default_Bearer_Activation Attempt Count where Message is ESM-ACT-DEF-BEAR
Default_Bearer_Activation Avg Duration (SUM (Response Time/1000)/SUM Event Count) where Message is ESM-ACT-DEF-BEAR and Status is
(ms) Success
Default_Bearer_Activation Fail Count where Message is ESM-ACT-DEF-BEAR and Status is Error
Default_Bearer_Activation Fail Rate % (Attach_Fail_Count/( Attach_Fail_Count+ Attach_Success_Count)) *100
Default_Bearer_Activation Success Count where Message is ESM-ACT-DEF-BEAR and Status is Success
Default_Bearer_Activation Success Rate % (Attach_Success_Count/( Attach_Fail_Count+ Attach_Success_Count) )*100
Default_Bearer_Activation Timeout Rate % (Attach_Timeouts_Count/ Attach_Attempts_Count)*100
Default_Bearer_Activation Timeouts Count where Message is ESM-ACT-DEF-BEAR and Status is Timeout

992-0690-08 Rev. 001
3.4 ESM PDN_Connectivity - S1-MME

The following Metrics have been created by counting the number of rows where the value of the Message field is ‘ESM-PDN-CONNECT’ and

PDN_Connectivity Attempt Count where Message is ESM-PDN-CONNECT
PDN_Connectivity Avg Duration (ms) (SUM (Response Time/1000)/SUM Event Count) where Message is ESM-PDN-CONNECT and Status is Success
PDN_Connectivity Fail Count where Message is ESM-PDN-CONNECT and Status is Error
PDN_Connectivity Fail Rate % (Attach_Fail_Count/( Attach_Fail_Count+ Attach_Success_Count)) *100
PDN_Connectivity Success Count where Message is ESM-PDN-CONNECT and Status is Success
PDN_Connectivity Success Rate % (Attach_Success_Count/( Attach_Fail_Count+ Attach_Success_Count) )*100
PDN_Connectivity Timeout Rate % (Attach_Timeouts_Count/ Attach_Attempts_Count)*100
PDN_Connectivity Timeouts Count where Message is ESM-PDN-CONNECT and Status is Timeout

992-0690-08 Rev. 001
3.5 GMM Attach – Gb

The following Metrics have been created by counting the number of rows where the value of the Message field is ‘GMM-ATTACH’ and the
value of the Status field is either ‘Error, Success or Timeout’.

2G Attach Attempt Count where Message is GMM-ATTACH
2G Attach Avg Duration (ms) (SUM (Response Time/1000)/SUM Event Count) where Message is GMM-ATTACH and Status is Success
2G Attach Fail Count where Message is GMM-ATTACH and Status is Error
2G Attach Fail Rate % (Attach_Fail_Count/( Attach_Fail_Count+ Attach_Success_Count))*100
2G Attach Success Count where Message is GMM-ATTACH and Status is Success
2G Attach Timeouts Count where Message is GMM-ATTACH and Status is Timeout

992-0690-08 Rev. 001
3.6 GMM Attach – IuPS

The following Metrics have been created by counting the number of rows where the value of the Message field is ‘IuPS-GMM-ATTACH’ and

3G Attach Attempt Count where Message is IuPS-GMM-ATTACH
3G Attach Avg Duration (ms) (SUM (Response Time/1000)/SUM Event Count) where Message is IuPS-GMM-ATTACH and Status is Success
3G Attach Fail Count where Message is IuPS-GMM-ATTACH and Status is Error
3G Attach Fail Rate % (Attach_Fail_Count/( Attach_Fail_Count+ Attach_Success_Count)) *100
3G Attach Success Count where Message is IuPS-GMM-ATTACH and Status is Success
3G Attach Timeouts Count where Message is IuPS-GMM-ATTACH and Status is Timeout

992-0690-08 Rev. 001
3.7 GTP v1 – Gn
Metrics have been created by counting the number of rows where the value of the Message field is ‘V1_Create_PDP’ and the value of the
Status field is either ‘Fail, Success or Timeout’.
The following metrics have been created:

Create PDP Attempt Count where Message is V1_Create_PDP
Create PDP Avg Duration (ms) (SUM (Response Time/1000)/SUM Event Count) where Message is V1_Create_PDP and Status is Success
Create PDP Fail Count where Message is V1_Create_PDP and Status is Error
Create PDP Fail Rate % (Create_PDP_Fail_Count/(Create_PDP_Success_Count+ Create_PDP_Fail_Count))*100
Create PDP Success Count where Message is V1_Create_PDP and Status is Success
Create PDP Success Rate % (Create_PDP_Success_Count/(Create_PDP_Success_Count+ Create_PDP_Fail_Count))*100
Create PDP Timeout Rate % (Create_PDP Timeouts_Count / Create_PDP_Attempts_Count)*100
Create PDP Timeouts Count where Message is V1_Create_PDP and Status is Timeout

992-0690-08 Rev. 001
3.8 GTP v2 -S11

Metrics have been created by counting the number of rows where the value of the Message field is ‘V2_Create_Bearer’ / ‘V2_Create_
Session’ / ‘V2_Delete_Bearer’ / ‘V2_Modify_Bearer’ (as appropriate) and the value of the Status field is either ‘Fail, Success or Timeout’.
The following metrics have been created:

Create Bearer Attempt Count where Message is V2_Create_Bearer
Create Bearer Avg Duration (ms) (SUM (Response Time/1000)/SUM Event Count) where Message is V2_Create_Bearer and Status is Success
Create Bearer Fail Count where Message is V2_Create_Bearer and Status is Error
Create Bearer Fail Rate % (Create_Bearer_Fail_Count/(Create_Bearer_Success_Count+ Create_Bearer_Fail_Count))*100
Create Bearer Success Count where Message is V2_Create_Bearer and Status is Success
Create Bearer Success Rate % (Create_Bearer_Success_Count/(Create_Bearer_Success_Count+ Create_Bearer_Fail_Count))*100
Create Bearer Timeout Rate % (Create_Bearer_Timeouts_Count/ Create_Bearer_Attempts_Count)*100
Create Bearer Timeouts Count where Message is V2_Create_Bearer and Status is Timeout
Create Session Attempt Count where Message is V2_Create_Session
Create Session Avg Duration (ms) SUM (Response Time/1000)/SUM Event Count) where Message is V2_Create_Session and Status is Success
Create Session Fail Count where Message is V2_Create_Session and Status is Error
Create Session Fail Rate % (Create_Session_Fail_Count/( Create_Session_Fail_Count+ Create_Session_Success_Count ))*100
Create Session Success Count where Message is V2_Create_Session and Status is Success
Create Session Success Rate % (Create_Session_Success_Count/( Create_Session_Fail_Count+ Create_Session_Success_Count)) *100
Create Session Timeout Rate % (Create_Session_Timeouts_Count/ Create_Session_Attempts) *100
Create Session Timeouts Count where Message is V2_Create_Session and Status is Timeout
Delete Bearer Attempt Count where Message is V2_Delete_Bearer
Delete Bearer Avg Duration (ms) SUM (Response Time/1000)/SUM Event Count) where Message is V2_Delete_Bearer and Status is Success
Delete Bearer Fail Count where Message is V2_Delete_Bearer and Status is Error
Delete Bearer Fail Rate % (Delete_Bearer_Fail_Count/( Delete_Bearer_Fail_Count+ Delete_Bearer_Success_Count))*100

992-0690-08 Rev. 001

Delete Bearer Success Count where Message is V2_Delete_Bearer and Status is Success
Delete Bearer Success Rate % (Delete_Bearer_Success_Count/( Delete_Bearer_Fail_Count+ Delete_Bearer_Success_Count)) *100
Delete Bearer Timeout Rate % (Delete_Bearer_Timeouts_Count/ Delete_Bearer_Attempts_Count)*100
Delete Bearer Timeouts Count where Message is V2_Delete_Bearer and Status is Timeout
Modify Bearer Attempt Count where Message is V2_Modify_Bearer
Modify Bearer Avg Duration (ms) (SUM (Response Time/1000)/SUM Event Count) where Message is V2_Modify_Bearer and Status is Success
Modify Bearer Fail Count where Message is V2_Modify_Bearer and Status is Error
Modify Bearer Fail Rate % (Modify_Bearer_Fail_Count/( Modify_Bearer_Fail_Count+ Modify_Bearer_Success_Count))*100
Modify Bearer Success Count where Message is V2_Modify_Bearer and Status is Success
Modify Bearer Success Rate % (Modify_Bearer_Success_Count/( Modify_Bearer_Fail_Count+ Modify_Bearer_Success_Count))*100
Modify Bearer Timeout Rate % (Modify_Bearer_Timeouts_Count/ Modify_Bearer_Attempts_Count)*100
Modify Bearer Timeouts Count where Message is V2_Modify_Bearer and Status is Timeout

4 User Plane Metrics
The following User Plane Metrics have been created in Explorer and MicroStrategy by default (unless
otherwise indicated). Any MicroStrategy Metric in the User Plane folder which is not documented
here is no longer supported and can be moved to a separate folder or deleted. The exception is the
Request, Success, Fail Metrics, which exist in MicroStrategy but will be added to Explorer in a future
release.

Ver. 6.3 | April 2020 4 User Plane Metrics
992-0690-08 Rev. 001

Avg Downlink RTR (%) (SUM Download Retransmitted Packets/SUM Download Packets)*100.
This is filtered for rows where the denominator >0 to avoid including rows where there is no
measurement.
Avg Downlink TCP Latency (ms) SUM (Total Download TCP/1000)/SUM TCP Count.
measurement.
Avg Downlink Throughput (kbps) (SUM (Download Effective Bytes * 8)/SUM (Download_Active_Time / 1000) /1000)
This is filtered for rows where Download Effective Bytes > 50KB and Download Active Time
>20ms in order to only include measurements where large payloads are more likely to have
experienced a sustained representative speed. The filters can be adjusted for different
application types. Should be used to measure a single Application and RAT only to avoid
averaging services with different characteristics.
Avg RTR (%) (SUM Download+Upload Retransmitted Packets/SUM Download+Upload Packets)*100.
measurement.
Avg RTT (ms) SUM (Total RTT/1000)/SUM Success Count.
measurement.
Avg TTFB (ms) SUM (Total TTFB ms)/SUM TTFB Count.
measurement

Ver. 6.3 | April 2020 4 User Plane Metrics
992-0690-08 Rev. 001

Avg Uplink RTR (%) (SUM Upload Retransmitted Packets/SUM Upload Packets)*100.
measurement.
Avg Uplink TCP Latency (ms) SUM (Total Upload TCP/1000)/SUM TCP Count.
measurement.
Avg Uplink Throughput (kbps) SUM (Unload Effective Bytes * 8)/SUM (Upload_Active_Time / 1000) /1000)
This is filtered for rows where Upload Effective Bytes > 50KB and Upload Active Time >20ms in
order to only include measurements where large payloads are more likely to have experienced
a sustained representative speed. The filters can be adjusted for different application types. .
Should be used to measure a single Application and RAT only to avoid averaging services with
different characteristics.
Bytes Downlink (kB) SUM Download_Bytes/1000
Bytes Uplink (kB) SUM Upload_Bytes/1000
Effective Bytes Downlink (kB) SUM Download Effective Bytes /1000
Effective Bytes Uplink (kB) SUM Upload Effective Bytes /1000
Total Bytes (kB) SUM (Upload_Bytes + Download_Bytes)/1000
Total Effective Bytes (kB) SUM (Effective_Download_Bytes+ Effective_Upload_Bytes)/1000
Total Packets SUM Download_Packets+ Upload_Packets
The Explorer default metric pack also includes examples of including a filter for RAT in order to distinguish between 3G, 4G and HSPA and a
filter for Application in order to distinguish FTP traffic.
The Explorer default metric pack also includes examples of Unique counts for various dimensions, where the Aggregation method for the
defined dimension is ‘Cardinality’.

5 Voice Metrics
The following Voice Metrics have been created in Explorer and MicroStrategy by default (unless
otherwise indicated).

Ver. 6.3 | April 2020 5 Voice Metrics
992-0690-08 Rev. 001
5.1 Media Management

QCI=1 filters for Conversational Voice.
Note: in MicroStrategy, the below Metrics are included in the Voice Media Management folder. The remaining Metrics in the Media folder
are components of the below and not documented individually.

RTP Avg Jitter (ms) SUM Jitter/( SUM Acceptable Jitter + SUM Warning Jitter + SUM Critical Jitter).
This is filtered for rows where QCI=1 and the denominator >0 to avoid including rows where there is no
measurement.
RTP Avg Latency (ms) SUM IP Round Trip Delay/( SUM Acceptable Delay + SUM Warning Delay+ SUM Critical Delay)
measurement.
RTP Avg MOS (score) (SUM Absolute MOS/( SUM Acceptable Degradation + SUM Warning Degradation + SUM Critical_
Degradation))/100.
measurement.
Note, the 100 multiplier is required to compensate for integer format of stored values.
RTP Avg Packet Loss Rate (%) SUM Packets Lost/( SUM Acceptable Packet Loss + SUM Warning Packet Loss + SUMCritical_Packet Loss).
measurement.
RTP Call Gap Ratio (%) (SUM Total Middle Gap Duration/SUM Total Stream Duration) *100.
This is filtered for rows where QCI=1 and Total Stream Duration >0 to avoid including rows where there is no
measurement.
RTP Handover Gap Ratio (%) (SUM Media Handover Middle Gap/(SUM Media Short Middle Gap + SUM Media Long Middle Gap) *100
measurement.

992-0690-08 Rev. 001
5.2 VoLTE Call Management

The default Metric Pack includes directional (MO/MT) variants of the below by including a filter for Client Server Entry Type=Client – Server
(MO) or Server – Client (MT). The non-directional variants include a filter for Client Server Entry Type=Client-Server OR Server-Client.
Metrics include a file for Response Code not being in the range 300-399 to avoid counting re-directed calls.

992-0690-08 Rev. 001
5.2.1 The Invite - VoLTE Call Management

4G Avg Answer Delay (ms) SUM (Response Time/1000)/SUM Event Count
This is filtered for rows where:
l Application is SIP or SIP_TCP
l Message is Answer Delay_SIP or Answer Delay_SIP_T
l Response Code is not in range 300-399
l Response Time >0
l Client Server Entry Type=Client-Server OR Server-Client.
Note: The Answer Delay message type can have zero response time values associated with it, so a filter for
response time>0 is required here.
4G Avg Call Duration (sec) SUM (Response Time/1000)/SUM Event Count. This is filtered for rows where:
l Message is Call Duration_SIP or Call Duration_SIP_T
Note: The Call Duration message type does not have zero response time value associated with it, so a filter for
response time>0 is not required here.
4G Avg Call Setup Time (ms) SUM (Response Time/1000)/SUM Event Count.
This is filtered for rows where:
l Application is SIP or SIP_TCP l Message is Invite or INVITE_T l Status is SUCCESS
Note: Successful Invites do not have zero response time value associated with them, so a filter for response
time>0 is not required here.

992-0690-08 Rev. 001

4G Call Answers COUNT rows where:
l Message is Answer Delay_SIP or Answer Delay_SIP_T
l Response Time >0
Note: The Answer Delay message type can have zero response time values associated with it, so a filter for
4G Call Attempts COUNT rows where:
l Application is SIP or SIP_TCP l Message is Invite or INVITE_T l Status is not INFO
Note: Invite messages can have supplementary rows where the Status is INFO, so these need to be filtered out
to avoid double counting of Invites.
4G Call Drops COUNT rows where:
l Message is BYE or BYE_T
l Response Code is in range 15500-15998 OR is 20000 OR is 20001
Note: Response codes 15500-15998, 20000 and 20001 are custom indicators that exist for the specific
purpose of identifying dropped calls and are included in INFO message types. They are generated once per
call and provide a more accurate determination of call drops vs counting errored BYEs etc. 15500-15998
reflect the existence of the SIP Reason Header. 20000 and 20001 are included to capture failed or aged out
events respectively. Note 20001 not available in 6.1.1.1000.

992-0690-08 Rev. 001

4G Call Completions COUNT rows where:

l Message is BYE or BYE_T
l Response Code is 20002
Note: Response code 20002 is a custom indicator that exists for the specific purpose of identifying a
completed call and is included in INFO message types. It is generated once per call and provides a more
accurate determination of call completions vs counting successful BYEs etc, where multiple BYE events can
occur when both parties hang up at the same time.
4G Call Completion Rate % 4G Call Completions/(4G Call drop s + 4G Call Completions)*100
4G Call Drop Rate % (4G Call drop s/(4G Call drop s + 4G Call Completions))*100
4G Call Setup Fail COUNT rows where:
l Application is SIP or SIP_TCP l Message is Invite or INVITE_T l Status is ERROR
4G Call Setup Success COUNT rows where:
l Application is SIP or SIP_TCP l Message is Invite or INVITE_T l Status is SUCCESS
4G Call Setup Fail Rate % (4G Call Setup Fail/4G Call Attempts)*100
4G Call Setup Success Rate % (4G Call Setup Success/4G Call Attempts)*100
The Explorer default metric pack also includes examples of Unique IMSI counts, where the Aggregation method for the Subscriber IMSI
field is ‘Cardinality’.

992-0690-08 Rev. 001
5.3 VoLTE Call Registration

The following Metrics have been created by counting the number of rows where the value of the Message field is ‘REGISTER’ or ‘REGISTER_
T’ and the value of the Status field is either ‘Error, Success or Timeout’.
5.3.1 VoLTE Call Management

Call Registration Attempts Count where Application is ‘SIP’ or ‘SIP_TCP’ and Message is ‘REGISTER’ or ‘REGISTER_T’ and Status not
‘INFO’ (to avoid counting any supplementary Info messages).
Call Registration Avg Duration (ms) SUM (Response Time/1000)/SUM Event Count. This is filtered for rows where:
l Message is REGISTER or REGISTER_T
l Response Time >0
Note: The Registration message type can have zero response time values associated with it, so a filter for
Call Registration Fail Count where Application is ‘SIP’ or ‘SIP_TCP’ and Message is ‘REGISTER’ or ‘REGISTER_T’ and Status is
‘ERROR’.
Call Registration Success Count where Application is ‘SIP’ or ‘SIP_TCP’ and Message is ‘REGISTER’ or ‘REGISTER_T’ and Status is
‘SUCCESS’.
Call Registration Fail Rate (%) Call Registration Fail / (Call Registration Attempts) *100
Call Registration Success Rate (%) Call Registration Success / (Call Registration Attempts) *100
The Explorer default metric pack also includes examples of Unique IMSI counts, where the Aggregation method for the Subscriber IMSI
field is ‘Cardinality’.

A Appendix A - ASI Data Set Field
Descriptions (Subscriber Tables only)
This section describes the fields available for creating Metrics and Filters, in the ASI Subscriber Tables.
Whilst the Explorer User Labels are listed here, equivalent field names are available in MicroStrategy.
Notes:
1 Fields marked ‘1’ are only available in the 5-min aggregate tables. Consult your system
administrator on retention time for these fields.
2 Fields marked ‘2’ are only available with special configuration.

Ver. 6.3 | April 2020 A Appendix A - ASI Data Set Field Descriptions (Subscriber Tables only)
992-0690-08 Rev. 001
A.1 Control Plane Data Set Field Description

Explorer User Label Description
APN APN String (provisioned in nG1)
Application Application Name Example: GTP_V2C
Application Group Application Group Example: Mobile
Application Protocol Application Protocol Type Code (Subject to Protocol) Example: GTP_V2C
Called Party 1 Called Address (Subject to Protocol) Example: SIP +15878386520
Calling Party 1 Calling Address (Subject to Protocol) Example: SIP +10286944778
Cell Area 1 Cell Area – Location Area Code – 2G/3G Example: 73410 (decimal)
Cell City 1 Custom provisioning field.
Cell ID 1 Cell ID, from User location information / ECGI as applicable Example: 4277 (decimal)
Cell Lat 1 Custom provisioning field
Cell Long 1 Custom provisioning field
Cell MCC 1 Cell MCC
Cell MNC 1 Cell MNC
Cell Region 1 Custom provisioning field
Cell Subdivision 1 Custom provisioning field
Cell Type 1 2G, 3G or 4G
Cell Updated 1 Cell Updated / Enriched from Access signaling
Client Server Entry Type For Gm isolation purposes [SIP]
[0] - Client to Server
[3] - Server to Client
CSFB Indicator 1 CSFB [MO/MT] flag
Destination Host Destination Host Example: 'SGW1'

992-0690-08 Rev. 001

Destination IP Address 2 Destination Host IP address Example:
IPv4 representation: (e.g. 10.122.0.218)
Where applicable IPv6 Addresses are expanded to full representation
Destination Realm Diameter Name Destination Realm (DIAMETER) Example: epc.mncDDD,mccEEE,3gppnetwork.org
Device Unique ID for probe and interface Example: SBO-S2-4895-1_LTE:if4_S11 (Site-APN)
Diameter Host Destination Name Destination Host (DIAMETER) Example:
MmecXX.mmegiYYYY,mme.epc.mncAAA,mccBBB,3gpp network.org
Diameter Host Origin Name Origin Host (DIAMETER)
Example: XXXX.YYYY.ZZ.operator.net
Diameter Realm Origin Name Origin Realm (DIAMETER)
Example: epc.mncAAA,mccBBB,3gppnetwork.org
Direction
DPC 1 Destination Point Code (Select Protocols) Example: 3457
HPLMN Home PLMN based on MCC/MNC
Example: Afghanistan Roshan
Message NETSCOUT message name for Procedure/Event
Message Protocol Protocol Type Code (Subject to Protocol) Example: CREATE_SES
OPC 1 Origination Point Code (Select Protocols) Example: 3456
outer_client_host_ip_address
Outer Client Host
outer_server_host_ip_address
Outer Server Host
RAT Current Radio Access Technology type, if available E.g. GERAN, UTRAN, EUTRAN.
Response Code Response Code
Example: DTAP CC 21

992-0690-08 Rev. 001

Response Description Response Description
Example: DTAP CC Call rejected
Response Time (usec) Round Trip Time in microseconds
Source Host Source Host
Example: 'MME1'
Source IP Address 2 Source Host IP address
Example:
Speech Indicator 1 Detection of "Speech" -- A, IuCS
Status Transaction Status:
SUCCESS indicates transaction was successful. This value is generally used as a filter for
‘Success’ type Metrics.
ERROR indicates receipt of a response code which is specified as an Error in nG1. This value
is generally used as a filter for ‘Fail’ type Metrics.
TIMEOUT indicates the time to wait for a response, was exceeded, specified in nG1. This
value is generally used as a filter for ‘Timeout’ type Metrics.
INFO indicates that the message contains supplementary information: it is best practice to
exclude INFO message from metrics in order to avoid counting duplicate rows.
FAILURE indicates a problem processing the result: this condition should not generally be
used as the basis for network metrics and should rarely occur.
AGEOUT indicates that the record has been aged out due to excessive time waiting for a
response.
Subscriber Age Custom provisioning field
Subscriber Company Custom provisioning field
Subscriber Gender Custom provisioning field
Subscriber IMSI Handset IMSI
Example: 310120000153518

992-0690-08 Rev. 001

Subscriber IP Address 1,2 Subscriber IP Address [IPv4] / [IPv6] Examples:
IPv6 Addresses are expanded to full representation (e.g.
2001:4888:0202:fff3:00a0:0108:0000:0003)
Subscriber MCC Subscriber home Mobile Country Code e.g. 310
Subscriber MNC Subscriber home Mobile Network Code e.g. 120
Subscriber MSISDN Handset MSISDN
Example: 8176802489
Subscriber Plan Custom provisioning field
Subscriber Segment Custom provisioning field
Timestamp 5-minute UTC for start of period.
Example: 2017-09-28 10:10:00
Tracking Area Code 1 Tracking Area Code
Transaction Start Timestamp1 Transaction Start Time Example:
2017-08-22
15:58:09.229000 UTC
User Equipment IMEISV 1 IMEISV or IMEI.
User Equipment Manufacturer Custom provisioning fields
User Equipment Model Custom provisioning fields
User Equipment SV Software Version
User Equipment TAC User Equipment Type Allocation Code
VPLMN Visited MCC/MNC based on MCC/MNC Example: Ireland_eircom Ltd

992-0690-08 Rev. 001
A.2 User Plane Data Set Field Descriptions

Application Application Name e.g Netflix
Application Group Application Group e.g. Web
Application Protocol Application Group e.g. NETFLIX
Cell Area 1 Cell Area – Location Area Code – 2G/3G
Example: 73410 (decimal)
Cell City 1 Custom provisioning fields
Cell ID 1 Cell ID, from User location information / ECGI as applicable
Example: 4277 (decimal)
Cell MCC 1 Cell MCC
Cell MNC 1 Cell MNC
Cell Type 1 2G, 3G, or 4G
Cell Updated 1 Cell Updated / Enriched from Access signaling
Device Unique name for probe and interface
Example: SBO-S2-4895-1_LTE:if4_S11 (Site-APN)
Download Active Time (msec) Time in milliseconds in 5 minute period for which Avg. DL Throughput is calculated
Download Bytes Total number of uplink bytes (bytes are counted starting from Ethernet header, including TCP
retransmissions)
Download Effective Bytes Number of downlink bytes detected above TCP/IP for any user plane transaction
Download Max Throughput (kbps) Maximum bearer bitrate in DL direction from application effective bytes in kbps

992-0690-08 Rev. 001

Download Packets Total number of packets from server to client (including retransmissions)
Download Retransmitted Packets Number of downlink packets detected above TCP/IP for any user plane retransmission transaction
Download Throughput Bucket 1 Number of throughput samples falling in bin 1, as defined in ISNG.
Fail Total number of requests with failed responses, not including timeouts
HPLMN Home PLMN based on Mcc / MNC Example:
Afghanistan Roshan
Outer Tunnel Client Host Client-side tunnel host name
Outer Tunnel Client IP Client-side tunnel node IP address
(First seen for the flow record)

Client-side (source) IP address of the encapsulated flow:
Example: IPv4 representation: (e.g. 10.122.0.218)
Outer Tunnel Server Host Server-side tunnel host name
Outer Tunnel Server IP Server-side tunnel node IP address
(First seen for the flow record)

Server-side (source) IP address of the encapsulated flow:
Example: IPv4 representation: (e.g. 10.122.0.219)
Packet Type Packet Type (TCP/UDP)
Peak RTT (usec) Peak 5 minute round trip time at the application level in usec
Quality Indicator QCI
Service Provider S1-U/S11 Only
RAT Current Radio Access Technology type, if available
E.g. GERAN, UTRAN, EUTRAN.
Request Total number of requests (including retries)
Subscriber Age Custom provisioning field.

992-0690-08 Rev. 001

Subscriber Company Custom provisioning field.
Subscriber Gender Custom provisioning field.
Example: 310120000153518
Subscriber IP Address 1 Subscriber IP Address [IPv4] / [IPv6]
Example:
IPv6 Addresses are expanded to full representation (e.g.
2001:4888:0202:fff3:00a0:0108:0000:0003)
Example: 8176802489
Subscriber Plan Custom provisioning field.
Subscriber Segment Custom provisioning field.
Success Total number of requests with successful responses, not including timeouts
TCP Count Count towards TCP Latencies over the period.
Timeout Received Response after a designated time boundary
Example:
2017-09-28 10:10:00
Total Download TCP (usec) Total Downlink Latency over the Period
Total RTT (usec) Total response time across all transactions in usec
Total TTFB (usec) Total TTFB across all transactions in usec.
Total Upload TCP (usec) Total Uplink Latency over the Period.
Tracking Area Code 1 Tracking Area Code
TTFB Count Count of events towards TTFB - A Mean TTFB may be calculated by using Count and Total values.

992-0690-08 Rev. 001

Upload Active Time (msec) Time in miliseconds in 5 minute period for which Avg. UL Throughput is calculated
Upload Bytes Total number of uplink bytes (bytes are counted starting from Ethernet header, including TCP
retransmissions)
Upload Effective Bytes Number of uplink bytes detected above TCP/IP for any user plane transaction
Upload Max Throughput (kbps) Maximum bearer bitrate in UL direction from application effective bytes in kbps
Upload Packets Total number of packets from client to server (including retransmissions)
UPload Retransmitted Packets Number of uplink packets detected above TCP/IP for any user plane retransmission transaction
Upload Throughput Bucket 1 Number of throughput samples falling in bin 1, as defined in ISNG.
Upload Throughput Bucket 2 Number of throughput samples falling in bin 2, as defined in ISNG.
UPload Throughput Bucket 3 Number of throughput samples falling in bin 3, as defined in ISNG.
User Equipment Manufacturer Custom provisioning field.
User Equipment Model Custom provisioning field.
User Equipment SV Software Version.
User Equipment TAC User Equipment Type Allocation Code.
VPLMN Visited MCC/MNC based on MCC/MNC
Example:
Ireland_eircom Ltd

992-0690-08 Rev. 001
A.3 Media Data Set Field Descriptions

Absolute MOS (sum) Absolute MOS sum (weighted by time in seconds). Dividing this by network_deg_bkts will give average absolute MOS
value * 100.
Acceptable Degradation Acceptable Degradation (secs)
(secs)
Acceptable Delay (secs) Acceptable Delay (secs)
Acceptable Jitter (secs) Acceptable Jitter (secs)
Acceptable Packet Loss Acceptable Packet Loss (secs)
(secs)
Active Time (secs) Active Time (secs)
Bitrate Count Number of active seconds of media traffic within selected time period with valid Active Media Bitrate
Call Direction (M) Direction (M) Values:
MO MT
where supported.
Called Party 1 Called Address (Subject to Protocol) Example: SIP +15878386520
Calling Party 1 Calling Address (Subject to Protocol) Example: SIP +10286944778
Cell Area 1 Cell Area – Location Area Code – 2G/3G Example: 73410 (decimal)
Cell City 1 Custom provisioning fields.
Cell ID 1 Cell ID, from User location information / ECGI as applicable Example: 4277 (decimal)
Cell MCC 1 Cell MCC
Cell MNC 1 Cell MNC

992-0690-08 Rev. 001

Cell Type Name 1 2G, 3G or 4G
Cell Updated 1 Cell Updated / Enriched from Access signalling
Codec (M) Codec Name Example: G.711_u-law
Critical Degradation Critical Degradation (secs)
(secs)
Critical Delay (secs) Critical Delay (secs)
Critical Jitter (secs) Critical Jitter (secs)
Critical Packet Loss Critical Packet Loss (secs)
(secs)
Destination Host Media Destination host name
Destination IP Address Media Destination IP address
(M) Example: IPv4 representation: (e.g. 10.122.0.219)
Destination Port (M) Media Destination Port Number Example: 24430 (decimal)
Device Unique ID for probe and interface
Example: SBO-S2-4895-1_LTE:if4_S11 (Site-APN)
Direction (M) Direction (M) Values:
MO MT
where supported
DSCP Indicator DSCP Marker
DTMF Present (M) 1 DTMF Present (M) 1=True
End Gap (M) 1 End Gap (M) 1=True
Expected Packets Number of Expected (Received + Lost) media packets reported during selected time period
HPLMN Home PLMN based on MCC/MNC
Example: Afghanistan_Roshan

992-0690-08 Rev. 001

IP Round Trip Delay IP round trip delay sum (weighted by time in seconds). Dividing this by round_trip_bkts will give average IP round trip
(sum) delay in ms. Round Trip delay value used for sum depends on nG1 round trip delay mode (end-to-end or source)
Jitter (sum) Jitter sum (weighted by time in seconds). Dividing this by jitter_bkts will give average jitter value in ms. Jitter value used
for sum depends on nG1 jitter mode (max or average).
Long Call (M) Long Call (M) 1=True
Media Completed (M) Media Completed (M) 1=True
Media Handover Middle Number of Handover Middle Gaps reported during selected time period (using "Middle Gap" nG1 thresholds).
Gap
Media Long Middle Gap Number of Long Middle Gaps reported during selected time period (using "Middle Gap" nG1 thresholds)
Media Short Middle Gap Number of Short Middle Gaps reported during selected time period (using "Middle Gap" nG1 thresholds)
Middle Gap (M) Middle Gap (M) 1=True
Min MOS (score) Worst (minimum) IP MOS * 100 within selected time period
Outer Tunnel Client Host Client-side tunnel host name
Outer Tunnel Client IP 1 Outer Source
IPv4 address or IPv6 table index
Outer Tunnel Server Server-side tunnel host name
Host
Outer Tunnel Server IP 1 Outer Destination IPv4 address or IPv6 table index
Packet Loss Percent Avg Packets Loss Rate % within the selected time period
(sum)
Packet Lost (sum) Packets Lost within the selected time period
Peak Jitter (msec) Worst (maximum) Jitter in ms within selected time period
Peak Packet Loss (%) Worst (maximum) Packet Loss % * 100 within selected time period
Peak RTT (msec) Worst (maximum) Round Trip Delay in ms within selected time period
QoS Mismatch QoS Mismatch (M) 1=True

992-0690-08 Rev. 001

Quality Indicator QCI
Service Provider S1- U/S11 Only
RAT Current Radio Access Technology type, if available. E.g. GERAN, UTRAN, EUTRAN.
Short Call (M) Short Call (M) 1=True
Silent Stream (M) Silent Stream (M) 1=True
Single Direction (M) Single Direction (M) 1=True
Source Host Media Source host name
Source IP Address (M) 1 Source Host IP address Example:
Start Gap (M) Start Gap (M) 1=True
Subscriber Age Custom provisioning field.
Subscriber Company Custom provisioning field.
Subscriber Gender Custom provisioning field.
Example: 310120000153518
Example: 8176802489
Subscriber Plan Custom provisioning field.
Subscriber Port (M) 1 Media Source Port Number Example: 49120 (decimal)
Subscriber Segment Custom provisioning field.
Example: 2017-09-28 10:10:00
Total Bitrate Weighted sum of Active Payload Bitrate in bps

992-0690-08 Rev. 001

Total Middle Gap Total Middle Gap duration in ms reported during the selected time period.
Duration (msec)
Total Stream Duration Total Media duration in ms reported during the selected time period
(msec)
User Equipment Custom provisioning field
Manufacturer
User Equipment Model Custom provisioning field
User Equipment SV Software Version
User Equipment TAC User Equipment Type Allocation Code
VPLMN Visited MCC/MNC based on MCC/MNC Example: Ireland_eircom Ltd
Warning Degradation Warning Degradation (secs)
(secs)
Warning Delay (secs) Warning Delay (secs)
Warning Jitter (secs) Warning Jitter (secs)
Warning Packet Loss Warning Packet Loss (secs)
(secs)

992-0690-08 Rev. 001
A.4 Message Name Detail

The following messages are supported:
A.4.1 DIAMETER
Protocol Type Message Name 3GPP Command Code
DIAMETER D-AuthInfo-T 318
DIAMETER D-Authentic-T 265
DIAMETER D-InSubData-T 319
DIAMETER D-CreditCtrl-T 272
DIAMETER D-MMAuth-T 303
DIAMETER D-UpatedLoc-T 316
DIAMETER D-DelSubData-T 320
DIAMETER D-CancelLoc-T 317
DIAMETER D-PurgeUE-T 321
DIAMETER D-ReAuth-T 258
DIAMETER D-AbortSession-T 274
DIAMETER D-Account-T 271
DIAMETER D-ME-Id-Check-T 324
DIAMETER Diameter Binding 999
DIAMETER LocUpdate 501

992-0690-08 Rev. 001
A.4.2 GTP
Protocol Type Transaction Name 3GPP 29.274 Transaction Type
GTPv2 V2_Create_Bearer 95/96
GTPv2 V2_Create_Session 32/33
GTPv2 V2_Delete_Bearer 66/67
GTPv2 V2_Modify_Bearer 34/35
Protocol Type Transaction Name 3GPP 29.060 Transaction Type

GTPv1 V2_Create_PDP 16/17

992-0690-08 Rev. 001
A.4.3 SIP Control

Protocol Type Transaction Name RFC Reference
SIP Invite See RFC 3261
SIP BYE See RFC 3261
SIP UPDATE See RFC 3261
SIP REGISTER See RFC 3261
SIP CANCEL See RFC 3261
SIP RE-Register_SIP See RFC 3261
SIP Message-SMS See RFC 3261
A.4.4 S1-AP/S1-MME
Protocol Type Transaction Name 3GPP Reference
S1AP-EMM EMM-ATTACH See 24.301
S1AP-EMM EMM-DETACH See 24.301
S1AP-ESM ESM-ACT-DED-BEAR See 24.301
S1AP-ESM ESM-ACT-DEF-BEAR See 24.301
S1AP-ESM ESM-PDN-CONNECT See 24.301
S1AP-EMM EMM-ATTACH See 24.301
S1AP-EMM EMM-DETACH See 24.301
S1AP-EMM EMM_CP_SERV_REQ See 24.301

992-0690-08 Rev. 001
A.4.5 Gb/IuPS
SM SM_ACTIVATE Table 10.4a/3GPP TS 24.008
SM SM_DEACTIVATE Table 10.4a/3GPP TS 24.008
GMM GMM_ATTACH Table 10.4/3GPP TS 24.008
GMM GMM_DETACH Table 10.4/3GPP TS 24.008
IU_GMM IuPS-GMM-ATTACH Table 10.4/3GPP TS 24.008
IU_GMM IuPS-GMM-DETACH Table 10.4/3GPP TS 24.008
IU_SM IuPS-SM-ACTIVATE Table 10.4a/3GPP TS 24.008
IU_SM IuPS-SM-DEACTIVATE Table 10.4a/3GPP TS 24.008
A.4.6 GSMA
GSMA MO_CALL_SETUP See 24.008 for triggers
GSMA MT_CALL_SETUP See 24.008 for triggers
GSMA EMERGENCY_CALL_SET See 24.008 for triggers
GSMA MO_ANSWERED_CALL See 24.008 for triggers
GSMA MT_ANSWERED_CALL See 24.008 for triggers
GSMA EMERGENCY_ANSW_CALL See 24.008 for triggers
GSMA MO_RELEASE_CALL See 24.008 for triggers
GSMA MT_RELEASE_CALL See 24.008 for triggers
GSMA EMERGENCY_REL_CALL See 24.008 for triggers
GSMA MO_CALL_DUR See 24.008 for triggers
GSMA MT_CALL_DUR See 24.008 for triggers
GSMA EMERGENCY_CALL See 24.008 for triggers

992-0690-08 Rev. 001
A.4.7 IuCS
IUCS MO_CALL_SETUP See 24.008 for triggers
IUCS MT_CALL_SETUP See 24.008 for triggers
IUCS EMERGENCY_CALL_SET See 24.008 for triggers
IUCS MO_ANSWERED_CALL See 24.008 for triggers
IUCS MT_ANSWERED_CALL See 24.008 for triggers
IUCS EMERGENCY_ANSW_CALL See 24.008 for triggers
IUCS MO_RELEASE_CALL See 24.008 for triggers
IUCS MT_RELEASE_CALL See 24.008 for triggers
IUCS EMERGENCY_REL_CALL See 24.008 for triggers
IUCS MO_CALL_DUR See 24.008 for triggers
IUCS MT_CALL_DUR See 24.008 for triggers
IUCS EMERGENCY_CALL See 24.008 for triggers
A.4.8 ISUP
Protocol Type Transaction Name ITU Reference
ITU-ISUP Answer Delay_ISUP Various
ITU-ISUP CallTeardown Various
ITU-ISUP Call Setup_ISUP Various
ITU-ISUP Call Duration_ISUP Various
Note: Variants of ISUP are supported with the same message types; please consult NETSCOUT for further details.

992-0690-08 Rev. 001
A.4.9 BICC
BICC Call Setup_BICC 3GPP TS 29.414
BICC Answer Delay_BICC 3GPP TS 29.414
BICC Call Duration_BICC 3GPP TS 29.414
BICC CallTeardown 3GPP TS 29.414

992-0690-08 Rev. 001
A.4.10 MAP
MAP Provide Subscr Loca 3GPP TS 29.002
MAP Any Time Interrog 3GPP TS 29.002
MAP Provide Subscr Info 3GPP TS 29.002
MAP AnyTime Subs Intero 3GPP TS 29.002
MAP Unstructured SSReq 3GPP TS 29.002
MAP Proc Unstr SSReq 3GPP TS 29.002
MAP Send Auth Info 3GPP TS 29.002
MAP SendIdentification 3GPP TS 29.002
MAP MO ForwardSM 3GPP TS 29.002
MAP RoutingInfoForSM 3GPP TS 29.002
MAP MT ForwardSM 3GPP TS 29.002
MAP SendRoutInfoForGprs 3GPP TS 29.002
MAP UpdateGprsLocation 3GPP TS 29.002
MAP SendRoutingInfo 3GPP TS 29.002
MAP ActiveSS 3GPP TS 29.002
MAP RegisterSS 3GPP TS 29.002
MAP SendParameters 3GPP TS 29.002
MAP Del Subscr Data 3GPP TS 29.002
MAP Ins Subscriber Data 3GPP TS 29.002
MAP Provide Roaming Number 3GPP TS 29.002
MAP CancelLocation 3GPP TS 29.002
MAP UpdateLocation 3GPP TS 29.002

992-0690-08 Rev. 001
A.4.11 CAP
CAP Initial DP_CAP 3GPP TS 29.078
CAP Connect 3GPP TS 29.078
CAP Connect SMS 3GPP TS 29.078
CAP Continue 3GPP TS 29.078
CAP Continue SMS 3GPP TS 29.078
CAP Release Call 3GPP TS 29.078
CAP Release SMS 3GPP TS 29.078
CAP Connect To Resource 3GPP TS 29.078


UD - nBA - Metric User Guide - 630

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

UD - nBA - Metric User Guide - 630

Uploaded by

Copyright:

Available Formats

nGenius Business Analytics

Metrics User Guide

Software Version 6.3

© NETSCOUT CONFIDENTIAL & PROPRIETARY

NETSCOUT SYSTEMS, INC

GNU GPL Source Code Request

Metrics User Guide 2

Copyright NETSCOUT 2009-2020. All rights reserved.

Metrics User Guide 3

What's New in nGenius Business Analytics 6.3 Metrics User Guide 6

Metrics User Guide 4

Metrics User Guide 5

What's New in nGenius Business

Metrics User Guide 6

Date Revision Reference Summary

Metrics User Guide 7

1.1 About nBA Metrics

Metrics User Guide 8

l New Control Plane EMM folder containing 4G Attach Metrics

Metrics User Guide 9

Metrics User Guide 10

3.1 EMM Attach-S1-MME

Metric Label Computation

Metrics User Guide 11

3.2 ESM Dedicated_Bearer_Activation - S1-MME

Metric Label Computation

Metrics User Guide 12

3.3 ESM Default_Bearer_Activation - S1-MME

Metric Label Computation

Metrics User Guide 13

3.4 ESM PDN_Connectivity - S1-MME

Metric Label Computation

Metrics User Guide 14

3.5 GMM Attach – Gb

Metric Label Computation

Metrics User Guide 15

3.6 GMM Attach – IuPS

Metric Label Computation

Metrics User Guide 16

The following metrics have been created:

Metric Label Computation

Metrics User Guide 17

3.8 GTP v2 -S11

The following metrics have been created:

Metric Label Computation

Metrics User Guide 18

Metric Label Computation

Metrics User Guide 19

Metrics User Guide 20

Metric Label Computation

Metrics User Guide 21

Metric Label Computation

Metrics User Guide 22

Metrics User Guide 23

5.1 Media Management

Metric Label Computation

Metrics User Guide 24

5.2 VoLTE Call Management

Metrics User Guide 25

5.2.1 The Invite - VoLTE Call Management

Metrics User Guide 26

Metric Label Computation

Metrics User Guide 27