Professional Documents
Culture Documents
Document
Status: Standard
Revision: 13.4
Table of Contents
Document Information.............................................................................4
Abstract ........................................................................................................... 4
Supported Release Version ................................................................................... 4
Revision History ..................................................................................................... 4
About This Document .............................................................................6
Purpose ........................................................................................................... 6
Intended Audience ................................................................................................. 6
Document Conventions .......................................................................................... 6
Document Organization ......................................................................................... 7
Related Reading .................................................................................................... 7
Customer Service Help Desk ..................................................................8
Airspan Encourages Comments ............................................................................ 8
1 Introduction .........................................................................................9
1.1 Data Availability ............................................................................................. 9
1.1.1 Tabular Display .............................................................................................. 9
1.1.2 Graphical Display ........................................................................................... 9
1.1.3 Periodic File Export ...................................................................................... 10
1.1.4 Northbound Interface.................................................................................... 11
1.2 Data Retention............................................................................................. 11
2 Understanding Performance Management ........................................12
2.1 LTE Performance Management................................................................... 12
2.2 Backhaul Performance Management .......................................................... 21
2.2.1 iBridge 2 ....................................................................................................... 21
2.2.2 iBridge 440 ................................................................................................... 22
2.2.3 iBridge 460 ................................................................................................... 24
2.2.4 Relay ............................................................................................................ 25
2.2.5 Relay eNodeB .............................................................................................. 27
2.3 Netspan Performance Management ............................................................ 27
2.4 LTE and Backhaul Statistics Calculations ................................................... 29
2.4.1 LTE Statistics Chart Calculations ................................................................. 29
Tables
Table 1. Typographic Conventions ......................................................................................................... 6
Table 2. Periodic File Export Configuration .......................................................................................... 10
Table 3. Data Retention Configuration ................................................................................................. 11
Table 4. eNodeB csv File Indexes ........................................................................................................ 15
Table 5. eNodeB csv File Index Name Description .............................................................................. 20
Table 6. iBridge 2 csv File Indexes ....................................................................................................... 22
Table 7. iBridge 2 csv File Index Name Description ............................................................................. 22
Table 8. iBridge LOS csv File Indexes ................................................................................................. 23
Table 9. iBridge LOS csv File Index Name Description ....................................................................... 23
Table 10. iBridge NLOS csv File Indexes ............................................................................................. 24
Table 11. iBridge NLOS csv File Index Name Description ................................................................... 25
Table 12. Relay csv File Indexes .......................................................................................................... 26
Table 13. Relay csv File Index Name Description ................................................................................ 26
Table 14. Netspan csv File Indexes ..................................................................................................... 28
Table 15. Netspan csv File Index Name Description ........................................................................... 28
Table 16. LTE Statistics Formulae ....................................................................................................... 29
Table 17. iBridge LOS Chart Calculations ............................................................................................ 30
Table 18. iBridge NLOS Chart Calculations ......................................................................................... 31
Table 19. Backhaul Statistics Formulae for iBridge NLOS Terminals .................................................. 32
Table 20. Relay Chart Calculations ...................................................................................................... 33
Table 21. Cell Identity Parameters ....................................................................................................... 38
Figures
Figure 1: vLteCellInfo_DDMMYYYY_hhmm1_hhmm2.csv Contents .................................................. 38
Document Information
Abstract
This document and the Netspan Counters and KPIs Reference List in the Excel format (included in
the ARD-D00740_Netspan Counters and KPIs Reference Guide_ SR17.00_Standard_Rev xx.x
folder) provides a detailed and complete overview of the supported SR17.00 counters and KPIs, and
how they are organised in Netspan.
ARD-D00740_Netspan Counters and KPIs Reference Guide_SR17.00_Preliminary_Rev xx.x folder
also contains the PDF version of the Netspan Counters and KPIs Reference List.
Revision History
This section lists only the changes associated with the chapters included in this overview document.
System Release
and Revision
Details Summary of Changes
Revision 13.4
SR17.00/Rev 13.4 Updated this document with information relevant for Rev 13.4
Updated iBridge 2: added iBridge 2 Device Statistics to the list of statistics types
For changes related to counters and KPIs, see the Netspan Counters and KPIs
Reference List.
Revision 13.3
SR17.00/Rev 13.3 Updated this document with information relevant for Rev 13.3
For changes related to counters and KPIs, see the Netspan Counters and KPIs
Reference List.
Revision 13.2
SR17.00/Rev 13.2 Updated this document with information relevant for Rev 13.2
For changes related to counters and KPIs, see the Netspan Counters and KPIs
Reference List.
Revision 13.1
System Release
and Revision
Details Summary of Changes
o Viewing Backhaul Counters and KPIs > iBridge 2 Counters and KPIs
Updated Periodic File Export to include a description about Folder Per PLMN
Revision 13.0
SR17.00/Rev 13.0 Updated LTE Performance Management to include the following new statistics
types to the list:
o CSFB per PLMN
o Dynamic ACB
o Radio Resource Utilization for VoLTE per MCS
o VoLTE WB CQI
Updated LTE Performance Management to include the details of the new
vLteVolteWbCqiStatsCsv file
Updated Table 5. eNodeB csv File Index Name Description to include the definition
of CQIIndex
Updated Table 16. LTE Statistics Formulae to include RF Measurements >
Wideband CQI Chart Calculations
Lists the details of the csv files in which the counters are collected
Lists the counter groups
Describes how the KPIs are calculated
Guides you on how to view and access counters
The Netspan Counters and KPIs Reference List covers the following:
Intended Audience
This document is intended for the network performance management personnel who monitor and
optimise the network.
Document Conventions
This document uses the following typographic conventions.
Convention Element
Document Organization
Chapter Contents
Provides an overview of the data availability and data retention
1 Introduction
of the LTE and backhaul counters
Related Reading
The following documents contain related information:
Note: To avail Airspan’s Customer Care Help Desk support, you must be a registered user and must have a
valid support contract. To register, click here and fill the Registration form.
To create and update issue logs, send e-mails to Customer Care Help Desk. Once you submit your
issue, the system generates a new issue and sends an issue number for your reference. The system
uses this issue number to categorize and store e-mails under the appropriate issue.
To help Customer Care Help Desk identify your issue, include the issue number and your Customer
Care Helpdesk account details in all further communications.
1 Introduction
Performance Management is a functionality of the network management to collect data that can be
used to analyse and optimise a given configuration of the network. This network management system
functionality proactively identifies potential issues and thereby reduces call drops, improves the QoS,
enhances user experience, and allows optimum network usage.
This functionality focuses on performance monitoring, optimizing, and troubleshooting of the wireless
network that is based on collecting and post-processing of the data.
The performance data that is collected from the network elements (according to the schedule
established by the element manager) includes counters, KPIs, and statistics.
Tabular Display
Graphical Display
Northbound Interface
Note: Counters retrieved using the methods listed above can have a value (with a defined range) or can be
kept empty (in case the counter is not pegged by the node or the feature is not implemented by the node).
Provides multiple filter options in the Netspan GUI based on the statistics type, node type, and
data type (raw, hourly, and daily).
Performs ad hoc export of the counters table to a csv file for post analysis and reporting.
Obtains counters from the nodes in real time and displays in a tabular format (using the
Update from the Node button). You can also set to refresh this display automatically every
15, 30, or 45 seconds. This feature is useful in the troubleshooting scenarios.
Provides multiple filter options in the Netspan GUI based on the statistics type, data range,
data type (raw, hourly, and daily), and associated statistics features.
Displays counters in charts from the nodes in real time (using the Reload button). This feature
is useful in troubleshooting scenarios.
Enables you to resize the graphs and customize the display interval.
Type Description
Enabled Specifies whether Statistics CSV File Generation
is Enabled or Disabled.
Note:
To collect the csv files through periodic file
export, select this parameter.
You can set a value for the following
parameters only if the Enabled checkbox is
selected.
File Interval Specifies how often you want to generate the csv
files (for example―5 min, 15 min, 30 min, 60 min,
or daily).
Delete After Days Specifies the retention period of the collected files.
CSV File Rule The rule based on which the csv statistics file
generation operates:
If One File per Collection Period is selected,
Netspan writes one csv file per statistics type.
If One File per Granularity Period is selected,
Netspan writes one csv file per start time and
end time for each statistics type.
Type Description
<counter group1>.csv.zip
<counter group2>.csv.zip
…
Folder Per PLMN Exports the statistics csv files to a different folder
per PLMN.
Note: For a csv file, if there are no counters generated for any node in the network, the file is not generated in
that granularity period.
Note: All csv files generated in Netspan are zipped into a single file with the following file format:
<Server_hostname>_Stats_ddmmyyyy_hhmm_hhmm.zip
Where:
Server_hostname = hostname of the server
Ddmmyyyy = date of the zip file created
hhmm_hhmm = start and end time of the granularity period of the file
The various csv files generated by Netspan are described in the section of this document associated
with the relevant supported technology.
Hourly data 1 0 28
Daily data 4 0 28
Important: Performance data is retained in the csv files. The number of days that this data is retained is
configurable. Airspan recommends that the data be retained for up to a maximum of 30 days.
Netspan offers the ability to enable, disable, and set granularity period per type of counter groups
using the eNodeB’s Management profile.
Note: If a feature is not available in a particular network element version, the associated counters are marked
as not available in an advanced version of Netspan.
ANR
Backhaul QoS
Carrier Aggregation
CMAS
CSFB
Dynamic ACB
E-RAB
eMBMS
Equipment Measurements
ETWS
Events
GTP
Handover
Incoming Handover
HARQ
Link Adaptation
Lite CoMP
MME Overload
Neighbour Management
Paging
Per PLMN
Positioning Measurements
RF Measurements
RRC Connection
RSRP Measurement
RSRQ Measurement
SON
Sub-band CQI
Timing Advance
VoLTE Quality
VoLTE WB CQI
Counters collected from the LTE nodes are also collected in the csv files. The following are the files
that are collected through Netspan:
vLteCellInfo_ddmmyyyy_hhmm_hhmm.csv
Note: The parameters in this csv file are used for performance management purposes. For more
information on the parameters you can find in this csv file, see A Addition of CM Data to the PM
Export Files.
vLteCmasStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteEmbmsStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteEquipMeasStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteERabPerQciStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteERabStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteEthernetCounterPerPortStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteEtwsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteHarqStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteHoPerTargetCellStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteHoStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteLinkAdaptationStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteLiteCompStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteMmeStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLtePagingStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLtePerCellPerQciStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLtePerCellStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLtePerPlmnPerQciStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLtePerPlmnStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLtePerSubBandCqiStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteRachAccessDelayStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteRachPreamblesSentStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteRbPerQciStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteRbStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteRfMeasStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteRrcPerEarfcnStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteRrcStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteRruPerQciStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteRruStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteRsrpMeasurementStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteRsrqMeasurementStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteS1StatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteSonStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteStatsCsfbCsv_ddmmyyyy_hhmm_hhmm.csv
vLteTimingAdvanceStatsCsv_ddmmyyyy_hhmm_hhmm.csv
vLteVolteWbCqiStatsCsv_ddmmyyyy_hhmm_hhmm.csv
For a relevant counter group type, each file contains the counters for all nodes. The counters
associated to each file are explained in this document.
Note: Performance data generated by the eNodeB is stored in non-persistent tables that is deleted on an
eNodeB reboot. In the event of a reboot, a maximum of 1 hour PM data can be lost.
Note: The eNodeB persistently keeps last 12 iterations (granularity) of counters in its tables. Depending on the
granularity period set, data can be kept for 1 hour (at 5 minutes granularity), 3 hours (at 15 minutes
granularity), 6 hours (at 30 minute granularity), or the lowest of the above in case of a mixture of granularities.
Note: Netspan collects all 12 iterations (granularity) of counters (in its tables) from an eNodeB at every poll. If
Netspan polling misses a particular granularity of counter collection (for example, due to loss of
communication), the counter data is captured in the next Netspan poll as long as it is within the 12 iterations
and data is present in the eNodeB. The missing data is added to the same granularity period visible to the
Netspan GUI, NBIF, and periodic csv files.
The counters have leading indexes identifying the node, counter collection time, and node
functionality based parameters in each line of the csv file. The indexes available in the csv files
associated to eNodeB are listed in Table 4.
Table 4. eNodeB csv File Indexes
Retransmission Index
BSName/NodeName
SubBandCqiIndex
DateandTimeStart
GranularityPeriod
DateandTimeEnd
SoftwareVersion
LiteCompIndex
McsAllocIndex
csv File Name
BinMaxValue
BinMinValue
SubBandCqi
CellNumber
IPaddress
PortName
SCTPPort
CQIIndex
QCIIndex
CellId
MCC
MNC
vLteCel
lInfo_d
dmmyy
yy_hh ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
mm_hh
mm.csv
vLteCm
asStats
Csv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteEm
bmsSta
tsCsv_
ddmmy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
yyy_hh
mm_hh
mm.csv
Retransmission Index
BSName/NodeName
SubBandCqiIndex
DateandTimeStart
GranularityPeriod
DateandTimeEnd
SoftwareVersion
LiteCompIndex
McsAllocIndex
csv File Name
BinMaxValue
BinMinValue
SubBandCqi
CellNumber
IPaddress
PortName
SCTPPort
CQIIndex
QCIIndex
CellId
MCC
MNC
vLteEq
uipMea
sStats
Csv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteER
abPerQ
ciStats
Csv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteER
abStats
Csv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteEth
ernetC
ounter
PerPort
StatsC
sv_dd ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
mmyyy
y_hhm
m_hhm
m.csv
vLteEt
wsCsv
_ddmm
yyyy_h ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
hmm_h
hmm.c
sv
vLteHa
rqStats
Csv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteHo
PerTar
getCell
StatsC
sv_dd ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
mmyyy
y_hhm
m_hhm
m.csv
vLteHo
StatsC
sv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
Retransmission Index
BSName/NodeName
SubBandCqiIndex
DateandTimeStart
GranularityPeriod
DateandTimeEnd
SoftwareVersion
LiteCompIndex
McsAllocIndex
csv File Name
BinMaxValue
BinMinValue
SubBandCqi
CellNumber
IPaddress
PortName
SCTPPort
CQIIndex
QCIIndex
CellId
MCC
MNC
vLteLin
kAdapt
ationSt
atsCsv
_ddmm ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
yyyy_h
hmm_h
hmm.c
sv
vLteLit
eComp
StatsC
sv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteM
meStat
sCsv_d
dmmyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
yy_hh
mm_hh
mm.csv
vLtePa
gingSta
tsCsv_
ddmmy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
yyy_hh
mm_hh
mm.csv
vLtePer
CellPer
QciStat
sCsv_d
dmmyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
yy_hh
mm_hh
mm.csv
vLtePer
CellSta
tsCsv_
ddmmy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
yyy_hh
mm_hh
mm.csv
vLtePer
PlmnP
erQciSt
atsCsv
_ddmm ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
yyyy_h
hmm_h
hmm.c
sv
vLtePer
PlmnSt
atsCsv
_ddmm
yyyy_h ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
hmm_h
hmm.c
sv
Retransmission Index
BSName/NodeName
SubBandCqiIndex
DateandTimeStart
GranularityPeriod
DateandTimeEnd
SoftwareVersion
LiteCompIndex
McsAllocIndex
csv File Name
BinMaxValue
BinMinValue
SubBandCqi
CellNumber
IPaddress
PortName
SCTPPort
CQIIndex
QCIIndex
CellId
MCC
MNC
vLtePer
SubBa
ndCqiS
tatsCsv
_ddmm ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
yyyy_h
hmm_h
hmm.c
sv
vLteRa
chAcce
ssDela
yStats
Csv_dd ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
mmyyy
y_hhm
m_hhm
m.csv
vLteRa
chPrea
mblesS
entStat
sCsv_d ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
dmmyy
yy_hh
mm_hh
mm.csv
vLteRb
PerQci
StatsC
sv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteRb
StatsC
sv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteRf
MeasSt
atsCsv
_ddmm
yyyy_h ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
hmm_h
hmm.c
sv
vLteRrc
PerEarf
cnStats
Csv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteRrc
StatsC
sv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
Retransmission Index
BSName/NodeName
SubBandCqiIndex
DateandTimeStart
GranularityPeriod
DateandTimeEnd
SoftwareVersion
LiteCompIndex
McsAllocIndex
csv File Name
BinMaxValue
BinMinValue
SubBandCqi
CellNumber
IPaddress
PortName
SCTPPort
CQIIndex
QCIIndex
CellId
MCC
MNC
vLteRr
uPerQc
iStatsC
sv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteRr
uStats
Csv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteRsr
pMeas
uremen
tStatsC
sv_dd ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
mmyyy
y_hhm
m_hhm
m.csv
vLteRsr
qMeas
uremen
tStatsC
sv_dd ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
mmyyy
y_hhm
m_hhm
m.csv
vLteS1
StatsC
sv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteSo
nStats
Csv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteSta
tsCsfb
Csv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
vLteTi
mingAd
vanceS
tatsCsv
_ddmm ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
yyyy_h
hmm_h
hmm.c
sv
Retransmission Index
BSName/NodeName
SubBandCqiIndex
DateandTimeStart
GranularityPeriod
DateandTimeEnd
SoftwareVersion
LiteCompIndex
McsAllocIndex
csv File Name
BinMaxValue
BinMinValue
SubBandCqi
CellNumber
IPaddress
PortName
SCTPPort
CQIIndex
QCIIndex
CellId
MCC
MNC
vLteVol
teWbC
qiStats
Csv_dd
mmyyy ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ ᵡ
y_hhm
m_hhm
m.csv
For a description of the eNodeB csv file index names, see Table 5.
BinMinValue and BinMaxValue The Bin Min and Bin Max value which can be one of
the following combinations:
BinMinValue BinMaxValue
1 3
4 4
5 5
6 6
7 7
8 8
9 10
11 20
21 50
51 100
101 200
iBridge 2 RF Stats
IbMmStatsEthernetCsv_ddmmyyyy_hhmm_hhmm.csv
IbMmStatsRfCsv_ddmmyyyy_hhmm_hhmm.csv
IbMmStatsQosCsv_ddmmyyyy_hhmm_hhmm.csv
IbMmStatsThroughputCsv_ddmmyyyy_hhmm_hhmm.csv
For a relevant counter group type, each file contains the counters for all nodes. The counters
associated to each file are explained in the Netspan Counters and KPIs Reference List.
Note: For a csv file, if there are no counters generated for any node in the network, the file is not generated in
that granularity period.
The counters have leading indexes identifying the node, counter collection time, and node
functionality based parameters in each line of the csv file. The indexes available in the csv files
associated to iBridge 2 are listed in Table 6.
Table 6. iBridge 2 csv File Indexes
Granularity
NodeName
DateTime
DateTime
Software
csv File
Version
Period
Name
Start
End
IbMmStatsEthernetCsv_ddmmyyyy_hhmm_hhmm.csv
IbMmStatsRfCsv_ddmmyyyy_hhmm_hhmm.csv
IbMmStatsQosCsv_ddmmyyyy_hhmm_hhmm.csv
IbMmStatsThroughputCsv_ddmmyyyy_hhmm_hhmm.csv
For a description of the iBridge 2 csv file index names, see Table 7.
Table 7. iBridge 2 csv File Index Name Description
IP Stats
RF Stats
Ib11IpStatsCsv_ddmmyyyy_hhmm_hhmm.csv
Ib11RfStatsCsv_ ddmmyyyy_hhmm_hhmm.csv
Ib11QosPerQciStatsCsv_ddmmyyyy_hhmm_hhmm.csv
For a relevant counter group type, each file contains the counters for all nodes. The counters
associated to each file are explained in the Netspan Counters and KPIs Reference List.
Note: For a csv file, if there are no counters generated for any node in the network, the file is not generated in
that granularity period.
The counters have leading indexes identifying the node, counter collection time, and node
functionality based parameters in each line of the csv file. The indexes available in the csv files
associated to iBridge 440 are listed in Table 8.
MacAddress
PeerWlan
DateTime
DateTime
WlanMac
Software
Address
csv File
Version
Priority
Name
Name
Node
Start
End
Ib11IpStatsCsv_ddmmyyyy
_hhmm_hhmm.csv ᵡ ᵡ
Ib11RfStatsCsv_ddmmyyyy
_hhmm_hhmm.csv ᵡ ᵡ
Ib11QosPerQciStatsCsv_dd
mmyyyy_hhmm_hhmm.csv ᵡ ᵡ ᵡ
For a description of the iBridge 440 csv file index names, see Table 9.
Note: For counter collection, it is strongly recommended to set the granularity period to 15 minutes or above
for iB460.
Netspan provides the ability to enable, disable and set the granularity period per counter group type
using the iBridge’s Management profile.
Statistics for iB460 are defined in these groups:
iBridgeBaseAirInterfaceStatsCsv_ddmmyyyy_hhmm_hhmm.csv
iBridgeBaseAirInterfaceUsageStatsCsv_ddmmyyyy_hhmm_hhmm.csv
iBridgeBaseConnectionActivityStatsCsv_ddmmyyyy_hhmm_hhmm.csv
iBridgeBaseTermDataStatsCsv_ddmmyyyy_hhmm_hhmm.csv
iBridgeBaseTermRfStatsCsv_ddmmyyyy_hhmm_hhmm.csv
For a relevant counter group type, each file contains the counters for all nodes. The counters
associated to each file are explained in the Netspan Counters and KPIs Reference List.
Note: For a csv file, if there are no counters generated for any node in the network, the file is not generated in
that granularity period.
The counters have leading indexes identifying the node, counter collection time, and node
functionality based parameters in each line of the csv file. The indexes available in the csv files
associated to iBridge 460 are listed in Table 10.
DateTime
Software
Software
Address
csv File
Version
Version
SysUp
Name
Node
Term
Time
Start
Mac
End
iBridgeBaseAirInterfaceStats
Csv_ddmmyyyy_hhmm_hhmm.c ᵡ ᵡ ᵡ
sv
iBridgeBaseAirInterfaceUsage
StatsCsv_ddmmyyyy_hhmm_hh ᵡ ᵡ ᵡ
mm.csv
iBridgeBaseTermDataStats
Csv_ddmmyyyy_hhmm_hhmm.c ᵡ ᵡ
sv
TermName
DateTime
DateTime
Software
Software
Address
csv File
Version
Version
SysUp
Name
Node
Term
Time
Start
Mac
End
iBridgeBaseTermRfStatsCsv_dd
mmyyyy_hhmm_hhmm.csv ᵡ
For a description of the iBridge 460 csv file index names, see Table 11.
2.2.4 Relay
Netspan uses SNMP to collect counters from Relay, namely iR460.
The counters are collected from the Relay at regular intervals set by Netspan. You can set the
granularity period for counter collection to 5, 15, 30, or 60 minutes.
Counters collected from the Relay nodes are also collected in the csv files. The following are the files
that are collected through Netspan:
Statistics for Relay are defined in these groups:
Interface Stats
Radio Stats
Neighbour Interference Stats
Per QCI Stats
Note: Per QCI Stats is only applicable to iRelay, AirDensity and AirUnity.
Note: Per QCI Stats is only applicable to iRelay, AirDensity and AirUnity.
Counters collected from the Relay nodes are also collected in the csv files. The following are the files
that are collected through Netspan:
RelayStatsPdnAvailabilityPerApnCsv_ddmmyyyy_hhmm_hhmm.csv
RelayStatsPerMcsCsv_ddmmyyyy_hhmm_hhmm.csv
RelayStatsPerNbrPciCsv_ddmmyyyy_hhmm_hhmm.csv
RelayStatsPerNodeCsv_ddmmyyyy_hhmm_hhmm.csv
RelayStatsPerQciCsv_ddmmyyyy_hhmm_hhmm.csv
For a relevant counter group type, each file contains the counters for all nodes. The counters
associated to each file are explained in the Netspan Counters and KPIs Reference List.
Note: For a csv file, if there are no counters generated for any node in the network, the file is not generated in
that granularity period.
The counters have leading indexes identifying the node, counter collection time, and node
functionality based parameters in each line of the csv file. The indexes available in the csv files
associated to Relay are listed in Table 12.
DateTime
DateTime
Software
BSName
csv File
Version
Period
Name
Start
Mcs
End
Qci
Pci
RelayStatsPdnAvailabilityPerApnC
sv_ddmmyyyy_hhmm_hhmm.csv ᵡ ᵡ ᵡ
RelayStatsPerMcsCsv_ddmmyyyy
_hhmm_hhmm.csv ᵡ ᵡ ᵡ
RelayStatsPerNbrPciCsv_ddmmyy
yy_hhmm_hhmm.csv ᵡ ᵡ ᵡ
RelayStatsPerNodeCsv_ddmmyyy
y_hhmm_hhmm.csv ᵡ ᵡ ᵡ ᵡ
RelayStatsPerQciCsv_ddmmyyyy_
hhmm_hhmm.csv ᵡ ᵡ ᵡ
For a description of the Relay csv file index names, see Table 13.
AirUnity 420
AirUnity 480
AirUnity 54X
AirUnity 587
AirDensity 386
AirDensity 420
AirDenisty 480
AirSpeed/AirStrand: The AirUnity product is a self-contained device, which combines LTE eNodeB
functionality with an LTE based backhaul solution. This outdoor product provides LTE coverage.
AirSpeed/AirStrand variants include:
AirSpeed 1200
AirSpeed 1250
AirStrand 1200
The counters for Relay and eNodeB apply to Relay eNodeB too.
For information on Relay eNodeB counters, see the Netspan Counters and KPIs Reference List
(included in the ARD-D00740_Netspan Counters and KPIs Reference Guide folder).
Netspan offers the ability to enable, disable, and set granularity period per type of counter groups
using the Global Server Configuration of Netspan.
These groups include:
Server Statistics
Network Statistics
Counters collected from Netspan are also collected in the csv files.
The following are the files that are collected through Netspan:
vServerStatsPerDiskCsv_ddmmyyyy_hhmm_hhmm.csv
vServerStatsPerProcessCsv_ddmmyyyy_hhmm_hhmm.csv
vNetworkStatsCsv_ddmmyyyy_hhmm_hhmm.csv
For a relevant counter group type, each file contains the counters for all nodes. The counters
associated to each file are explained in the Netspan Counters and KPIs Reference List.
The counters have leading indexes identifying the node, counter collection time, and node
functionality based parameters in each line of the csv file.
The indexes available in the csv files associated to Netspan are listed in Table 14.
Table 14. Netspan csv File Indexes
vServerStatsPerDiskCsv_ddmmyyyy
_hhmm_hhmm.csv
vServerStatsPerProcessCsv_ddmmy
yyy_hhmm_hhmm.csv ᵡ ᵡ
vNetworkStatsCsv_ddmmyyyy_hhm
m_hhmm.csv ᵡ ᵡ
For a description of the iBridge NLOS csv file index names, see Table 15.
KPI Formula
CSFB Parameter Transfer Rate 100 x (Number of CSFB Responses) ÷ (Number of
CSFB Requests)
Percentage of Successful Downlink Transport Blocks (100 x Total number of successful downlink transport
blocks) ÷ Total number of downlink transport blocks
Percentage of Faulty Downlink Transport Blocks (100 x Total number of faulty downlink transport
blocks) ÷ Total number of downlink transport blocks
Percentage of Successful Uplink Transport Blocks (100 x Total number of successful uplink transport
blocks) ÷ Total number of uplink transport blocks
Percentage of Faulty Uplink Transport Blocks (100 x Total number of faulty uplink transport blocks)
÷ Total number of uplink transport blocks
Maximum Wideband CQI Maximum of all CQI values (1 to 15) for that row
Minimum Wideband CQI Minimum of all CQI values (1 to 15) for that row
Average Wideband CQI Average of all CQI values (1 to 15) for that row
Direction Description
Level of spectral efficiency on downlink
Spectral Efficiency
over time
Direction Description
Level of uplink CINR measurement over
CINR
time
Table 19 lists the formulae used for calculating throughput and HARQ statistics on iBridge NLOS
terminals.
Node Restarts
Number of node restarts on the channel
Throughput (Channel)
Node Restarts
Number of node restarts on the terminal
(Terminal)
PHY Restarts
Number of PHY restarts on the terminal
(Terminal)
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑏𝑢𝑟𝑠𝑡𝑠
÷ 𝐼𝑛𝑡𝑒𝑟𝑣𝑎𝑙 𝑖𝑛 𝑠𝑒𝑐𝑜𝑛𝑑𝑠 𝑏𝑒𝑡𝑤𝑒𝑒𝑛 𝑠𝑢𝑐𝑐𝑒𝑠𝑠𝑖𝑣𝑒 𝑚𝑒𝑎𝑠𝑢𝑟𝑒𝑚𝑒𝑛𝑡𝑠
Bursts
𝐻𝐴𝑅𝑄 𝑈𝐿 𝐵𝑢𝑟𝑠𝑡𝑠 = (𝐻𝐴𝑅𝑄 𝑈𝐿 𝐴𝑐𝑘𝑠 + 𝐻𝐴𝑅𝑄 𝑈𝐿 𝑁𝑎𝑐𝑘𝑠)
𝐻𝐴𝑅𝑄 𝐷𝐿 𝐵𝑢𝑟𝑠𝑡𝑠 = (𝐻𝐴𝑅𝑄 𝐷𝐿 𝐴𝑐𝑘𝑠 + 𝐻𝐴𝑅𝑄 𝐷𝐿 𝑁𝑎𝑐𝑘𝑠)
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝐴𝑐𝑘𝑠
Acks
HARQ ÷ 𝐼𝑛𝑡𝑒𝑟𝑣𝑎𝑙 𝑖𝑛 𝑠𝑒𝑐𝑜𝑛𝑑𝑠 𝑏𝑒𝑡𝑤𝑒𝑒𝑛 𝑠𝑢𝑐𝑐𝑒𝑠𝑠𝑖𝑣𝑒 𝑚𝑒𝑎𝑠𝑢𝑟𝑒𝑚𝑒𝑛𝑡𝑠
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑁𝑎𝑐𝑘𝑠
Nacks
÷ 𝐼𝑛𝑡𝑒𝑟𝑣𝑎𝑙 𝑖𝑛 𝑠𝑒𝑐𝑜𝑛𝑑𝑠 𝑏𝑒𝑡𝑤𝑒𝑒𝑛 𝑠𝑢𝑐𝑐𝑒𝑠𝑠𝑖𝑣𝑒 𝑚𝑒𝑎𝑠𝑢𝑟𝑒𝑚𝑒𝑛𝑡𝑠
Node Restarts
Number of node restarts on the terminal
(terminal)
CC: The network element maintains a running count of the event being counted. The counter
is reset to 0 at the beginning of each granularity period.
Gauge: Gauge represents the dynamic variables that might change in either direction. Its
value can be an integer or a real number. If a gauge produces low and high tide marks for a
granularity period (for example―the minimum and maximum call duration), it is reinitialized at
the beginning of the granularity period.
DER: DER indicates a measurement of a specified event where every Nth event is taken into
account. The value of N depends on the frequency of occurrence of the event that is being
measured. The DER measurement is reset at the beginning of the granularity period and will
only have a valid result at the end of the granularity period.
SI: The network elements maintain the internal counts for resource management purposes.
These counts are read at a predetermined rate; the rate is usually based upon the expected
rate of change of the count value. The SI measurement is reset at the beginning of the
granularity period and will only have a valid result at the end of the granularity period.
Date Range: Specify the range of date that you want the chart to cover.
Data Type: Specify the time interval that you want the chart to cover (that is, Raw, Hourly, or
Daily).
IP Statistics
Netspan periodically reads this information and uses it to compute the transmitted and received
packets per second and bytes per second. When reporting, Netspan reports the dropped packets and
errors rates as separate items, and TX and RX errors as a combined item.
The main iBridge440 interfaces include the following:
ether1-local
wlan1-gateway
Netspan collects IP statistics for each interface.
Note: iB440 reports instantaneous statistics to Netspan at each collection period as it does not
store counters locally. This is a hardware limitation of iB440. As a result, granularity period is fixed
at 15 minutes per iB440 node by Netspan. If an instance of counter collection is missed at a
granularity period due to communications failure with the node, the following instance whenever the
communication is restored with Netspan, the counters in IP Statistics will be aggregated with data
from any missed granularity period. OSS systems need to cater to this by checking for
DateTimeStart and DateTimeEnd within the Ib11IpStatsCsv csv files to determine the granularity of
IP Statistics counters and then publish KPI accordingly.
RF Statistics
RF Statistics is categorized into the following groups:
RF Counters
RF Characteristics
RF characteristics (which are not counters) are configured by the users:
Tx Power (dBm)
Frequency (MHz)
Bandwidth (MHz)
Packets
Bytes
Dropped
B Abbreviations
Term Expansion
3GPP Third Generation Partnership Project
Ack Acknowledgement
BE Best effort
BS Base station
CC Cumulative counter
DL Downlink
IP Internet Protocol
LOS Line-of-sight
NLOS Non-line-of-sight
Term Expansion
OSS Operational support systems
RF Radio frequency
Rx Receive
SI Status Inspection
Tx Transmit
UE User equipment
UL Uplink