Sei sulla pagina 1di 89

10/10/2019 Nemo Analyze KPI List

Nemo Analyze KPI List


AMPS

Serving system and band


Recorded when channel configuration information changes.
Serving system
Recorded when channel configuration information changes.
Serving band
Recorded when channel configuration information changes.
L3 signaling
Recorded when a Layer 3 or an NAS signaling message is sent or received.
L3 message search
Searches for user-defined messages, with user-defined string in the message name
Channel number
Recorded when channel configuration information changes.
Rx level
MS power level
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Channel type
SAT
L3 signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message
Downlink Band
Handover events
Handover attempt
Handover success
Handover failure

AMPS Scanner

Rx level
RX level selected channel
RX level Nth best
RX level top N

Analysis

Ec/Io active set best with geodesic BTS ref. information


Information on best serving cell from the BTS reference file.
Active set best cell geodesic BTS ref. information
Information on best serving cell from the BTS reference file.
CPICH Ec/N0 selected carrier with geodesic information (BTS ref.)
Information on scanned pilots from the BTS reference file.
Serving cell geodesic information (BTS ref.)
Information on best serving cell from the BTS reference file.
Current region mobile
Polygon region where the datapoint at given time falls into
Problem events
The query returns all problem events in Nemo fileformat. Results can be displayed in grid, colorcoded map, and print value
on the map.
Current region scanner UMTS
Ec/N0 CPICH Nth best with geodesic information (BTS ref.)
Information on scanned Nth best pilot from the BTS reference file.
Rx level top N with BTS ref. geodesic information

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 1/89


10/10/2019 Nemo Analyze KPI List
Information on TOP N scanned BCCH channels from the BTS reference file.
RSRP Nth best selected carriers with geodesic information (BTS ref.)
EC/N0 CPICH Nth best selected carriers with geodesic information (BTS ref.)
Current region scanner GSM
Rx level Nth best selected channels with geodesic BTS ref. information
Information on Nth best scanned BCCH channel from the BTS reference file.
UMTS neighbor list optimizer
This KPI suggests neighborlist based on scanner data for all cells encountered in the measurement data. Input data is
binned geographically to bins of user-definable size. Serving cell and neighboring cells are calculated for each bin based on
CPICH Ec/N0. For each serving cell, neighboring cells are divided to active and monitored cells based on the user-definable
threshold from the serving cell. Serving cells that do not exist in a bin for minimum distance of the user-definable
threshold, are filtered out.
UMTS to UMTS missing neighbor analysis
This analysis is based on NMISS events recorded by Nemo Outdoor. Missing neighbor analysis UMTS intra-frequency
provides the same analysis without relying on Nemo Outdoor missing neighbor measurements. List of all missing neighbor
and best active set cell pairs where the missing neighbor is within user defined window from the best active set cell.
Missing neighbor analysis UMTS scanner only
Missing neighbour analysis using scanner only. Requires a scanner capable of decoding system information signaling
messages. Output is list of all missing neighbor and serving cell pairs where the missing neighbor is within user defined
window from the serving cell. Analysis is done for TOP N pilots detected by the scanner in selected channel
Missing neighbor analysis GSM inter-system
List of possible missing UMTS neighbors of GSM cell(s) found from the measurement data. Only the N best scanned UMTS
cells per carrier are included in the analysis, where N is user definable. Only the missing neighbors measured for longer
than user definable time threshold are reported.
Missing neighbor analysis GSM
List of possible missing GSM neighbors found from the measurement data, where only missing neighbors withing user-
definable window from the serving cell are considered. Missing neighbors measured longer than user definable time
threshold are reported.
Missing neighbor analysis UMTS inter-system
List of possible missing GSM neighbors of UMTS cell(s) found from the measurement data. Only the N best scanned GSM
BCCH channels are included in the analysis, where N is user definable. Only the missing neighbors measured for longer
than user definable time threshold are reported.
Missing neighbor analysis UMTS intra-frequency
List of possible missing neighbors found from the measurement data, where the missing neigbor Ec/N0 is within user
defined window from the best active set cell Ec/N0. Only the missing neighbors measured for longer than user definable
time threshold are reported.
Missing neighbor analysis UMTS inter-frequency
List of possible UMTS inter-frequency missing neighbors found from the measurement data, where the missing neigbor
Ec/N0 is within user defined window from the best active set cell Ec/N0. Only the missing neighbors measured for longer
than user definable time threshold are reported.
Missing neighbor analysis CDMA
List of all missing neighbor and best active set cell pairs where the missing neighbor is within user defined window from
the best active set cell.
Missing neighbor analysis UMTS based on detected set
List of all missing neighbor and best active set cell pairs where the missing neighbor is within user defined window from
the best active set cell. Missing neighbor detection is done by comparing mobile 1st active set cell measurements and
detected set measurements. Scanner is not needed.
MOS DL analysis LTE IMS voice
Grid of all DL MOS samples, with the average value of all key RF and LTE IMS voice parameters from the time period of
the MOS speech sample
MOS DL analysis GSM
Grid of all DL MOS samples, with the average value of all key RF parameters from the time period of the MOS speech
sample
MOS DL analysis GSM and UMTS
Grid of all DL MOS samples, with the average value of all key RF parameters from the time period of the MOS speech
sample
MOS DL analysis GSM and UMTS limited parameter set
Grid of all DL MOS samples, with the average value of the most important RF parameters from the time period of the MOS
speech sample
GSM hopping channel interference analysis
Lists all hopping channels in the measurement data, ordered by the average C/I. Helps in spotting the traffic channels with
interference. Drill down is possible from each channel to look the C/I on the map.
Problem survey per category
Distribution of all failure events found in the measurements data, grouped by failure type. Drill down is possible to each
group, and further to individual failures by double-clicking on the pie, or legend.
Problem survey per file
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 2/89
10/10/2019 Nemo Analyze KPI List
Number of different failure events found in the measurements data, grouped by the measurment type. Drill down is
possible to each file by right-clicking on the row.
Problem survey per cell
Number of different failure events found in the measurements data, grouped by the cell. Drill down is possible to each cell
by double-clicking on the row.
UMTS SHO overhead (%) RNC level
Percentage of cell level SHO overhead calculated with following formula: ((AS_size_1_count + AS_size_2_count +
AS_size_3_count)/(AS_size_1_count + AS_size_2_count / 2 + AS_size_3_count / 3)-1)*100
UMTS SHO overhead (%) cell level
Percentage of cell level SHO overhead calculated with following formula: ((AS_size_1_count + AS_size_2_count * 2 +
AS_size_3_count * 3)/(AS_size_1_count + AS_size_2_count + AS_size_3_count)-1)*100
HSUPA low throughput root cause analysis
Gives the reason for low throughput in HSUPA. Threshold for low throughput is user-definable, root causes are not give for
throughputs higher than the threshold. Diagnostic is calculated only for HSUPA data collected during uplink data transfer.
Applicaple for Qualcomm-chipset terminals data only.
UMTS 900 band clearance analysis
Automatically detects and lists interfering GSM channels on the UMTS 900 band. It can be drilled down with double-click
from each channel to see situation in map. Input parameters: ARFCN range to be analysed and Rx level threshold. If
needed ARFCN range spans over EGSM and GSM bands, then two ranges may be defined EGSM (975-1023) and GSM900
(0-124).
EVDO mobile cross-feeder/overspilling analysis
Number of samples measured in cell service area, and number of samples measured out of the service area reported per
each cell. Only the samples where the cell was stongest are considered. Serving area is defined by the beam width in
degrees, and cell radius in meters. Results are in descending order by number of samples out of the serving area, giving
first in the list the possible cross-feeder and overspilling cases
CDMA mobile cross-feeder/overspilling analysis
Number of samples measured in cell service area, and number of samples measured out of the service area reported per
each cell. Only the samples where the cell was stongest are considered. Serving area is defined by the beam width in
degrees, and cell radius in meters. Results are in descending order by number of samples out of the serving area, giving
first in the list the possible cross-feeder and overspilling cases
EVDO scanner cross-feeder/overspilling analysis
Number of samples measured in cell service area, and number of samples measured out of the service area reported per
each cell. Only the samples where the cell was stongest are considered. Serving area is defined by the beam width in
degrees, and cell radius in meters. Results are in descending order by number of samples out of the serving area, giving
first in the list the possible cross-feeder and overspilling cases
CDMA scanner cross-feeder/overspilling analysis
Number of samples measured in cell service area, and number of samples measured out of the service area reported per
each cell. Only the samples where the cell was stongest are considered. Serving area is defined by the beam width in
degrees, and cell radius in meters. Results are in descending order by number of samples out of the serving area, giving
first in the list the possible cross-feeder and overspilling cases
GSM mobile cross-feeder/overspilling analysis
Number of samples measured in cell service area, and number of samples measured out of the service area reported per
each cell. Only the samples where the cell was stongest are considered. Serving area is defined by the beam width in
degrees, and cell radius in meters. Results are in descending order by number of samples out of the serving area, giving
first in the list the possible cross-feeder and overspilling cases
GSM scanner cross-feeder/overspilling analysis
Number of samples measured in cell service area, and number of samples measured out of the service area reported per
each cell. Only the samples where the cell was stongest are considered. Serving area is defined by the beam width in
degrees, and cell radius in meters. Results are in descending order by number of samples out of the serving area, giving
first in the list the possible cross-feeder and overspilling cases
UMTS mobile cross-feeder/overspilling analysis
Number of samples measured in cell service area, and number of samples measured out of the service area reported per
each cell. Only the samples where the cell was stongest are considered. Serving area is defined by the beam width in
degrees, and cell radius in meters. Results are in descending order by number of samples out of the serving area, giving
first in the list the possible cross-feeder and overspilling cases
UMTS scanner cross-feeder/overspilling analysis
Number of samples measured in cell service area, and number of samples measured out of the service area reported per
each cell. Only the samples where the cell was stongest are considered. Serving area is defined by the beam width in
degrees, and cell radius in meters. Results are in descending order by number of samples out of the serving area, giving
first in the list the possible cross-feeder and overspilling cases
Scrambling code clash analysis
Finds Scrambling codes where the scrambling code has been among the top N of the scanned scrambling codes, and the
scanner has decoded two or more different cell IDs within user-defined distance for the same scrambling code
BCCH clash analysis
Finds BCCH channels where the BCCH has been among the top N of the scanned BCCHs, and two or more different BSICs
have been decoded within user-defined distance for the same BCCH
BCCH clash analysis drilldown route

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 3/89


10/10/2019 Nemo Analyze KPI List
Finds BCCH channels where the BCCH has been among the top N of the scanned BCCHs, and two or more different BSICs
have been decoded within user-defined distance for the same BCCH
Pilot pollution analysis UMTS scanner
List of cells where pilot pollution occured. Top 10 polluter cells are also listed. Pilot pollution is defined as: Number of
simultaneously measured cells within user defined window from the best cell in terms of Ec/N0 is above user defined
threshold, when best cell RSCP is above user defined threshold.
Call attempt failure analysis
Call drop analysis
Uses neighbour cell count, signal strength / quality between serving cell and neighbour cells to find reason dropped call.
Audio quality MOS analysis per call
RRC connection drop analysis
RRC connection attempt failure analysis
RACH failure analysis
LTE scanner cross-feeder analysis
Compares RSRP between antenna ports to find possible cross-feeders. Delta will be calculated for every PCI and the
highest delta among PCIs of one event will be reported. For every PCI at least one TX port must have better RSRP than
the given RSRP threshold filter, then the delta between ports is calculated and the difference is reported if it's bigger than
the given difference threshold filter.
LTE scanner cell counter
Finds unique cells using location estimate.
LTE mobile cell locator
Finds unique cells using location estimate.
LTE scanner cell locator
Finds unique cells using location estimate.
UMTS scanner cell locator
Finds unique cells using location estimate.
UMTS mobile cell locator
Finds unique cells using location estimate.

CDMA

Markov expected mux


Recorded when the mobile reports the information.
Markov actual mux
Recorded when the mobile reports the information.
Transfer reason
Recorded when values are received from the mobile in slotted mode.
Pilot number
Recorded when values are received from the mobile in slotted mode.
Walsh code for paging indicators
Recorded when values are received from the mobile in slotted mode.
Paging indicator power offset
Power difference between paging indicator and pilot channel.
Broadcast indicator support
Recorded when values are received from the mobile in slotted mode.
Broadcast indicator walsh code
Recorded when values are received from the mobile in slotted mode.
Broadcast indicator power level
Recorded when values are received from the mobile in slotted mode.
Configuration change indicator support
Recorded when values are received from the mobile in slotted mode.
Configuration change walsh code
Recorded when values are received from the mobile in slotted mode.
Configuration change power level
Recorded when values are received from the mobile in slotted mode.
Indicator demodulation result
Recorded when values are received from the mobile in slotted mode.
Indicator type
Recorded when values are received from the mobile in slotted mode.
THB threshold for paging indicator
Recorded when values are received from the mobile in slotted mode.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 4/89


10/10/2019 Nemo Analyze KPI List

THI threshold for paging indicator


Recorded when values are received from the mobile in slotted mode.
Indicator position
Recorded when values are received from the mobile in slotted mode.
Indicator amplitude on I channel
Recorded when values are received from the mobile in slotted mode.
Indicator amplitude on Q channel
Recorded when values are received from the mobile in slotted mode.
Common pilot energy
Recorded when values are received from the mobile in slotted mode.
Diversity pilot energy
Recorded when values are received from the mobile in slotted mode.
RX power antenna 0
RX power antenna 1
RSCP active set Nth best
RSCP active set
RSCP candidate set
RSCP neighbor set
RSCP remainder set
R-SCH1 to pilot ratio
R-DCCH to pilot ratio
F-SCH1 current power control subchannel outer loop setpoint
F-SCH1 minimum power control subchannel outer loop setpoint
F-SCH1 maximum power control subchannel outer loop setpoint
F-DCCH current power control subchannel outer loop setpoint
F-DCCH minimum power control subchannel outer loop setpoint
F-DCCH maximum power control subchannel outer loop setpoint
Active set best cell BTS ref. information
Information on best serving cell from the BTS reference file
Cell name active set best (BTS ref.)
Name of the best serving cell from the BTS reference file
Measured cell list (BTS ref.)
Distincs list of measured active, candidate, neighbor, and remainder cells by the mobile
Ec/Io neighbour set with BTS ref. information
Information on active set from the BTS reference file
Ec/Io candidate set with BTS ref. information
Information on active set from the BTS reference file
Ec/Io active set with BTS ref. information
Information on active set from the BTS reference file
Serving system and band
Recorded when channel configuration information changes.
Serving system
Recorded when channel configuration information changes.
Serving band
Recorded when channel configuration information changes.
Number of missing CDMA neighbors
PHCHI info
Rake finger allocation
FER
Total (fundamental channel + supplemental channel) frame error rate value reported by mobile.
FER F-FCH target
FER F-SCH0 target
FER F-DCCH target
FER F-FCH
FER F-SCH0
FER F-DCCH
Missing neighbor Ec/I0

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 5/89


10/10/2019 Nemo Analyze KPI List

Missing neighbor diff. to strongest


Difference between missing neighbor and the best cell seen by the terminal in dB
Missing neighbor RSCP
L3 signaling
Recorded when a Layer 3 or an NAS signaling message is sent or received.
L3 message search
Searches for user-defined messages, with user-defined string in the message name
Packet technology
Packet technology during data transfer
Packet technology between nemo events DAA to DAD or DAF
Ec/I0 total to active set
Ratio of total Ec/I0 over all sets to total Ec/I0 over active set in decibels. Can be used to indicate pilot pollution
Ec/I0 active set combined
RSCP active set combined
QPCH paging indicator rate
Recorded when values are received from the mobile in slotted mode.
Data rate. Currently valid values are 4800 and 9600.
Paging slot number
Recorded when values are received from the mobile in slotted mode.
Rx power
Number of measured pilots
Active set size
Ec/I0 active set
Ec/I0 active set average
Ec/I0 candidate set
Ec/I0 neighbor set
Ec/I0 remainder set
Ec/I0 active set best
RSCP selected pilot number
Received pilot power (dBm)
Ec/I0 selected pilot number
Ec/I0 Nth best
Pilot number active set best
Vocoder rate forward
Recorded when vocoder rate changes.
Vocoder rate reverse
Recorded when vocoder rate changes.
RLP reverse user throughput
RLP forward user throughput
RLP reverse retransmission rate
RLP forward retransmission rate
CDMA channel type
Channel number
T_COMP (Comparison threshold)
Active set versus candidate set comparison threshold (L3 value). To get the actual T_ADD value, divide the value by two
and change the sign.
MCC
MIN_P_REV (Minimum protocol revision level)
Mobile network code
NID (Network ID)
SEARCH_WIN_A (Size of active search window)
Size of active search window. Searchers are used to find multipath signals to improve signal reception. Search_Win_A
(active) is used to search active and candidate pilots. Active sets are channels that are associated with the forward
channel traffic which are assigned to the mobile station. Candidate pilots are searched from additional multipaths in the
same channels.
SEARCH_WIN_R (Size of remaining search window)
Searchers are used to find multipath signals to improve signal reception. Search_Win_R (remaining) is used to search the
remaining pilot set. Remaining set of all possible pilots in the system that are not currently assigned to any of the other

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 6/89


10/10/2019 Nemo Analyze KPI List
sets.
SEARCH_WIN_N (Size of neighbor search window)
Size of neighbor search window. Searchers are used to find multipath signals to improve signal reception. Search_Win_N
(neighbor) is used to search adjacent pilots. Candidate set of pilots received by the mobile station whose power exceeds a
certain threshold and could be demodulated.
SID (System ID)
T_ADD (Pilot detection threshold)
To get the actual T_ADD value, divide the value by two and change the sign.
T_DROP (Pilot drop threshold)
To get the actual T_ADD value, divide the value by two and change the sign.
T_TDROP (Pilot drop timer threshold)
Slotted mode
Slotted mode is used for power conservation while a mobile station is in idle mode. The MS monitors only selected time
slots on the Paging Channel.
L3 signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message
Missing neighbor analysis CDMA
List of all missing neighbor and best active set cell pairs where the missing neighbor is within user defined window from
the best active set cell.
Pilot pollution number of polluting cells
Number of (EcIo>EcIo_Tadd) > 3 and (EcIo_max -EcIo_min) within 3dB
Downlink Band
Number of pilots above Ec/I0 threshold
Number of pilots where the Ec/I0 is higher than user-definable threshold
Number of cells within X dB window from the best
Number of cells where the Ec/I0 is within user-definable window from the best cell
Cell reselection
Handover events
Handover attempt
Handover success
Handover duration
Markov frame error rate
Markov frame rates
Burst frame error rate
Pilot number Nth best
Searcher state
Searcher queue
Searcher priority
Searcher frequency offset
Searcher status per pilot
Searcher status peak
F-FCH current setpoint
F-FCH minimum setpoint
F-FCH maximum setpoint
F-SCH0 current setpoint
F-SCH0 minimum setpoint
F-SCH0 maximum setpoint

CDMA Scanner

RSCP selected channel


RSCP selected pilot number
RSCP best
Delay selected channel
The time difference between actual received signal and expected point in time derived from the GPS time.
Delay

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 7/89


10/10/2019 Nemo Analyze KPI List
The time difference between actual received signal and expected point in time derived from the GPS time. This parameter
is also known as time offset.
Delay profile
RSSI
Wide-band carrier power including thermal noise, co-carrier and adjacent carrier interference, and noise generated in the
receiver.
RSSI selected carrier
Ec/Io
Ec/Io selected channel
Ec/Io selected pilot number
Pilot number best
Ec/Io best
Ec/Io Nth best
RSCP Nth best selected carriers
Ec/I0 Nth best selected carriers
L3 signaling
Scanning configuration
Defines scanning settings.
Number of pilots within X dB window from the best
Number of cells where the Ec/I0 is within user-definable window from the best cell
RSCP Nth best
Delay spread selected channel
The time between the first and the last multi-path peak component inside the search window above the PN threshold.

CDMA:Data

Packet technology during data transfer


Packet technology between nemo events DAA to DAD or DAF

CDMA:Finger

Transmit diversity power level


Subchannel
Locked antennas
Ec/I0 antenna 0
Ec/I0 for finger tracking RX0
Ec/I0 antenna 1
Ec/I0 for finger tracking RX1
Ec/I0
If antenna configuration is 2, then this represents Ec/Io for the paired fingers.
Reference finger
Assigned finger
Transmit diversity mode

CDMA:Power control

Percentage of "DL power up" commands


Forward power control subchannel indicator
Subchannel indicator is set by the BTS to indicate to a MS if the primary inner loop estimation should be preformed on the
received F-FCH or F-DCH.
Forward power control operation mode indicator
Forward Power Control (FPC) is used by the Mobile Station (MS) to control the power levels on a traffic channel to optimize
the Frame Error Rate (FER). There are several different FPC modes explained in 3GPP2 C.S0011-E.
Forward power control subchannel gain
See 3GPP2 C.S0005-F subclause 3.7.2.3.2.21.
Percentage of "UL power up" commands
TX power
TX power control step size
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 8/89
10/10/2019 Nemo Analyze KPI List

Upper limit on TX power


Closed loop adjustment
Max power limited
Reports whether max power protection is in effect.
R-FCH to pilot ratio
R-SCH0 to pilot ratio

CDMA:RACH

Access channel number


Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
PN randomization delay
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
INIT_PWR (access probe initial power)
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Initial power is a correction factor used by mobile stations in open-loop power estimation for initial transmission on an
Access Channel.
Probe TX level
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Probe count
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Probe seq. count
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Access probe sequence count.
PWR_STEP (access probe power step)
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Mobile stations increase the transmission power in an access probe sequence.
Access nominal transmit power offset
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Nominal transmit power offset is a correction factor used by mobile stations in open-loop power estimation.
NUM_STEP (access probe number of steps)
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Access probes consist of a preamble and a message for channel access. Access probes are sent in a sequence of one or
more access probes. Transmitted power is incremented in each probe. Note that the parameter value is one less than the
actual maximum number of steps.
Number of persistence tests performed
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Persistence is a probability measurement done by the mobile station to determine if it should transmit on a given access
channel.
Sequence backoff
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Time between access probe sequences.
Probe backoff
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Time between access probes.
Inteference correction
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Interference correction is calculated from the Ec/I0 of the strongest active set pilot and from the interference correction
threshold.
Transmit gain adjust
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 9/89


10/10/2019 Nemo Analyze KPI List

Time to complete the attempt


Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.

CDMA:RLP statistics

Service ID
Number of resets
Received fill frames
Received blank frames
Received null frames
Received new data frames
Received fundamental data frames
Received bytes
Received RLP erasures
Received multiplexer erasures
Transmitted NAKs
Transmitted retransmitted frames
Number of NAK aborts
Transmitted idle frames
Transmitted new data frames
Transmitted fundamental data frames
Transmitted bytes
Last RTT
Number of 20-ms time frames for the last round-trip time measurement
Block of bytes used
Received NAKs
Total number of negative acknowledgement frames received.
Largest block of consecutive erasures
Number of retransmitted frames not found
Received retransmitted frames
Received idle frames

CDMA:SHO

Soft-softer handover status CDMA


Status of the soft handover. Soft:2-way HO to 2 distinct sites, Softer: 2-way HO to cells of 1 distinct site, Soft-Softer: 3-
way HO to cells of 2 distinct sites, Soft-Soft: 3-way HO to 3 distinct sites, Softer-Softer: 3-way handoff to cells of 1
distinct site, 4-way soft: all 4-way soft and softer HOs, 5-way soft: all 5-way soft and softer HOs, 6-way soft: all 6-way
soft and softer HOs, 2-way, soft-softer status unknown: 2-way HO where there is no BTS reference available, 3-way, soft-
softer status unknown: 3-way HO where there is no BTS reference available
Soft handover
Recorded when the active set changes. Event information is based on RRC signaling with UMTS FDD.
Number of pilots added
Recorded when the active set changes. Event information is based on RRC signaling with UMTS FDD.
Number of pilots removed
Recorded when the active set changes. Event information is based on RRC signaling with UMTS FDD.
Added pilot number
Removed pilot number
Soft handover failure

CDMA:Service configuration

Service option
Forward traffic type
F-DCCH radio configuration
R-DCCH radio configuration
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 10/89
10/10/2019 Nemo Analyze KPI List

F-SCH multiplex option


F-SCH radio configuration
F-SCH coding
F-SCH frame size
F-SCH frame offset
F-SCH maximum rate
R-SCH multiplex option
R-SCH radio configuration
Reverse traffic type
R-SCH coding
R-SCH frame size
R-SCH frame offset
R-SCH maximum rate
Encryption mode
F-FCH and F-DCCH multiplex option
R-FCH and R-DCCH multiplex option
F-FCH bits per frame
R-FCH bits per frame
F-FCH radio configuration
R-FCH radio configuration

Circuit-switched data

Requested CS bitrate
Indicates the requested data call resources. Recorded when data call is initiated or reconfigured.
Channel coding
Recorded when data call resources have changed.
CS data mode
Indicates the requested data call resources. Recorded when data call is initiated or reconfigured.
Modem type
Indicates the requested data call resources. Recorded when data call is initiated or reconfigured.
Number of UL timeslots
Recorded when data call resources have changed.
Number of CS data timeslots uplink.
Number of DL timeslots
Recorded when data call resources have changed.
Number of CS data timeslots downlink.
CS data timeslots uplink
CS data timeslots downlink
Data channel request UMTS
Indicates the requested data call resources. Recorded when data call is initiated or reconfigured.
Data channel request GSM
Indicates the requested data call resources. Recorded when data call is initiated or reconfigured.
RRLP signaling
Recorded when an RRLP signaling message is sent or received.

DVB-H

DVB type
Recorded when DVB-H channel configuration changes.
DVB-H service state
Recorded when DVB-H channel configuration changes.
DVB-H frequency
Recorded when DVB-H channel configuration changes.
DVB-H cell ID
Recorded when DVB-H channel configuration changes.
DVB-H transmission mode

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 11/89


10/10/2019 Nemo Analyze KPI List
Recorded when DVB-H channel configuration changes.
Also known as OFDM mode or FFT length.
DVB-H modulation
Recorded when DVB-H channel configuration changes.
DVB-H code rate low priority
Recorded when DVB-H channel configuration changes.
DVB-H code rate high priority
Recorded when DVB-H channel configuration changes.
DVB-H guard time
Recorded when DVB-H channel configuration changes.
DVB-H MPE-FEC code rate low priority
Recorded when DVB-H channel configuration changes.
DVB-H MPE-FEC code rate high priority
Recorded when DVB-H channel configuration changes.
DVB-H hierarchy
Recorded when DVB-H channel configuration changes.
DVB-H FER before FEC
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
DVB-H FER after FEC
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
DVB-H frame count
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
DVB-H FER and MFER
Parameter show 0 when FER = 0 and MFER = 0. 1 when FER > 0 and MFER = 0. 2 when FER > 0 and MFER > 0.
DVB-H BER before viterbi
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
DVB-H BER after viterbi
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
DVB-H Rx level best
The best value of Rx level over the reporting period
DVB-H Rx level
Recorded when parameter sample is received from the device.
DVB-H carrier to noise ratio
Recorded when parameter sample is received from the device.
DVB-H signal quality
Recorded when parameter sample is received from the device.
DVB-H throughput
Recorded when parameter sample is received from the device.

DVB-H Scanner

Frequency
Carrier RSSI
DVB-H MER
Scanning configuration
Defines scanning settings.

EVDO

Random variable
Random variable represents the random variable that was used to calculate the new reverse rate (Rev 0 only).
Transition probability
Transition probability that was used to calculate the new reverse rate (Rev 0 only).
Condition RRI
Condition reverse rate provides the reverse rate that was calculated based on the above factors (Rev 0 only).
Actual RRI
Actual reverse rate. This should be less than condition RRI or there is not enough data to be sent (Rev 0 only).
Padding bytes
Number of padding bytes included in the reverse link packets (Rev 0 only).
Multiuser ACK ratio

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 12/89


10/10/2019 Nemo Analyze KPI List

DRC gain boost


DSC gain boost
Slot for DRC lock update
ACK channel status
Forced ACK/NAK ratio
Represents the ratio of forced ACK/NAKs.
ACK ratio
Physical layer throughput UL per carrier
Physical layer throughput DL per carrier
Active users
EVDO MCC
See ITU-T recommendation E.212.
EVDO MNC
Search window activate set
Search window candidate set
Search window neighbor set
Pilot add
Pilot drop
Pilot compare
Pilot drop timer
Soft slope
Inequality criterion for adding or dropping a pilot from the active set.
Add intercept
Drop intercept
Set maximum age
Channel number
RX power
EV RSCP active set Nth best
EV RSCP active set
EV RSCP candidate set
EV RSCP neighbor set
EV RSCP remainder set
Reverse activity bit
DRC lock period
DRC lock period indicates which RPC bits are 'hold' (Rel 0).
TX throttle
TX throttle indicates how often TX channel gains are being throttled during the previous reporting period (Rev A).
TX max power usage
Indicates how often TX AGC was at maximum power during the previous reporting period.
TX min power usage
Indicates how often TX AGC was at minimum power during the previous reporting period.
Transmission mode
Indicates the transmission mode of the data packets being transmitted (Rev A).
Physical layer packet size.
RRI channel to pilot ratio (Rev A).
DSC channel to pilot ratio (Rev A).
AUX channel to data channel ratio
Number of "UL power hold" commands
Number of received "UL power hold" commands (BTS to mobile).
TX T2P
FRAB
Fast reverse activity bit soft decision max.
QRAB
Quick reverse activity bit hard decision.
QRABps
Quick reverse activity bit value based on pilot strength.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 13/89


10/10/2019 Nemo Analyze KPI List

Active set best cell BTS ref. information


Information on best serving cell from the BTS reference file
Cell name active set best EVDO (BTS ref.)
Name of the best serving cell from the BTS reference file
Measured cell list (BTS ref.)
Distincs list of measured active, candidate, neighbor, and remainder cells by the mobile
EV Ec/Io neighbour set with BTS ref. information
Information on active set from the BTS reference file
EV Ec/Io candidate set with BTS ref. information
Information on active set from the BTS reference file
EV Ec/Io active set with BTS ref. information
Information on active set from the BTS reference file
PER single-user
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Separate measurement event is logged for each serving cell with LTE.
PER multi-user
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Separate measurement event is logged for each serving cell with LTE.
PER reverse
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Separate measurement event is logged for each serving cell with LTE.
Physical layer throughput UL
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Separate measurement event is logged for each serving cell with LTE.
Physical layer throughput DL
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Separate measurement event is logged for each serving cell with LTE.
Single-user throughput DL
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Separate measurement event is logged for each serving cell with LTE.
Multi-user throughput DL
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Separate measurement event is logged for each serving cell with LTE.
DRC set percentage
Recorded when parameter sample is received from the device.
Packet technology
EV Ec/I0 total to active set
Ratio of total Ec/I0 over all sets to total Ec/I0 over active set in decibels. Can be used to indicate pilot pollution
Soft-softer handover status EVDO
Status of the soft handover. Soft:2-way HO to 2 distinct sites, Softer: 2-way HO to cells of 1 distinct site, Soft-Softer: 3-
way HO to cells of 2 distinct sites, Soft-Soft: 3-way HO to 3 distinct sites, Softer-Softer: 3-way handoff to cells of 1
distinct site, 4-way soft: all 4-way soft and softer HOs, 5-way soft: all 5-way soft and softer HOs, 6-way soft: all 6-way
soft and softer HOs, 2-way, soft-softer status unknown: 2-way HO where there is no BTS reference available, 3-way, soft-
softer status unknown: 3-way HO where there is no BTS reference available
EV Ec/I0 active set combined
EV RSCP active set combined
Access terminal state
Packet channel type
Packet carrier number
DRC index
Average over 16 samples.
DRC index per carrier
PER instantaneous per carrier
Recorded when frame error rate reports are received from the device.
PER short per carrier
Recorded when frame error rate reports are received from the device.
PER long per carrier
Recorded when frame error rate reports are received from the device.
Signal-to-interference and noise ratio
Signal-to-interference and noise ratio Nth best
Number of measured pilots evdo
EV RSCP selected pilot number
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 14/89
10/10/2019 Nemo Analyze KPI List
Received pilot power (dBm)
EV Ec/I0 selected pilot number
Unexpected P-ARQ NACKs
Number of P-ARQ NACKs received after an H-ARQ ACK was already received for same packet.
HiCap Subpacket 0 ACKs
HiCap Subpacket 1 ACKs
HiCap Subpacket 2 ACKs
HiCap Subpacket 3 ACKs
HiCapp ARQ NACKs
LoLat Subpacket 0 ACKs
LoLat Subpacket 1 ACKs
LoLat Subpacket 2 ACKs
LoLat Subpacket 3 ACKs
LoLat P-ARQ NACKs
TC packets good
TC packes bad
TC packets decoded in selected slot
Multi carrier forward link packet header info
Recorded when parameters change.
RX power antenna 0
RX power antenna 1
EV Active set size
EV Ec/I0 active set
EV Ec/I0 candidate set
EV Ec/I0 neighbor set
EV Ec/I0 remainder set
EV Ec/I0 active set best
EV Ec/I0 Nth best
EV Pilot number active set best
Reportable
This parameter is only valid for EVDO Rev B active set cells.
Scheduler tag
This parameter is only valid for EVDO Rev B active set cells.
RLP reverse user throughput
RLP forward user throughput
RLP reverse retransmission rate
RLP forward retransmission rate
SID (System ID)
EV Number of cells within X dB window from the best
Number of cells where the Ec/I0 is within user-definable window from the best cell
EV Number of pilots above Ec/I0 threshold
Number of pilots where the Ec/I0 is higher than user-definable threshold
Handover events
Handover attempt
Handover success
SNP signaling
Recorded when an SNP signaling message is sent or received.
Burst frame error rate
EV Pilot number Nth best
PER instantaneous
Recorded when frame error rate reports are received from the device.
PER short
Recorded when frame error rate reports are received from the device.
PER long
Recorded when frame error rate reports are received from the device.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 15/89


10/10/2019 Nemo Analyze KPI List

Searcher state
Searcher window size
Searcher MSTR
Searcher status per pilot
Searcher status peak
Sector ID
128-bit sector address of the serving sector.
Sector subnet identifier
Hybrid mode
Reverse rate limit (Rev 0 only)
Recorded when parameters change.
Current rate (Rev 0 only)
Recorded when parameters change.
Combined busy bit (Rev 0 only)
Recorded when parameters change.
Reverse Activity Bit (RAB) is a control bit sent in regular intervals that indicates if the access network is busy or not.
Maximum PA headroom available (Rev 0 only)
Recorded when parameters change.
DRC cover
Cover used to transmit DRC.
DSC value
Data source control value transmitted by the mobile (Rev A only).
MAC index
DRC cover per pilot
RPC cell index
DRC lock
Slot FRAB
Slot fast reverse activity bit.
Slot QRAB
Slot quick reverse activity bit.

EVDO Scanner

EV RSCP selected channel


EV RSCP selected pilot number
EV RSCP best
Delay selected carrier
The time difference between actual received signal and expected point in time derived from the GPS time.
EV RSCP Nth best selected carriers
EV Ec/I0 Nth best selected carriers
SNP signaling
Recorded when an SNP signaling message is sent or received.
RSSI selected carrier
Ec/I0
Ec/I0 selected carrier
Ec/I0 selected pilot number
Ec/I0 best
EV Ec/I0 Nth best
EV RSCP Nth best
RSSI
Delay spread selected carrier
The time between the first and the last multi-path peak component inside the search window above the PN threshold.

EVDO:Connection

Connection attempt
Recorded when connection layer is connected.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 16/89


10/10/2019 Nemo Analyze KPI List

Connection release
Recorded when connection layer is released.
ALMP state
Initialization protocol state
Idle protocol state
Connected protocol state
Route update protocol state
Overhead message protocol state

EVDO:FCH packets

CC38400 Good
Counter for 38.4 k control channel packets with good CRC
CC38400 Bad
Counter for 38.4 k control channel packets with bad CRC
TC307200Short Good
Counter for 302.2 (short) traffic channel packets with good CRC
TC307200Short Bad
Counter for 302.2 (short) traffic channel packets with bad CRC
TC307200Long Good
Counter for 307.2 (long) traffic channel packets with good CRC
TC307200Long Bad
Counter for 307.2 (long) traffic channel packets with bad CRC
TC614400Short Good
Counter for 614.4 k (short) traffic channel packets with good CRC
TC614400Short Bad
Counter for 614.4 k (short) traffic channel packets with bad CRC
TC614400Long Good
Counter for 614.4 k (long) traffic channel packets with good CRC
TC614400Long Bad
Counter for 614.4 k (long) packets decoded in 2 slots
TC921600 Good
Counter for 921.6 k traffic channel packets with good CRC
TC921600 Bad
Counter for 921.6 k traffic channel packets decoded with bad CRC
CC76800 Good
Counter for 76.8 k control channel packets with good CRC
TC1228800Short Good
Counter for 1228.8 k (short) traffic channel packets with good CRC
TC1228800Short Bad
Counter for 1228.8 k (short) traffic channel packets with bad
TC1228800Long Good
Counter for 1228.8 (long) traffic channel packets with good CRC
TC1228800Long Bad
Counter for 1228.8 (long) traffic channel packets with bad CRC
TC1843200 Good
Counter for 1843.2 k traffic channel packets with good CRC
TC1843200 Bad
Counter for 1843.2 k traffic channel packets with bad CRC
TC2457600 Good
Counter for 2457 k traffic channel packets with good CRC
TC2457600 Bad
Counter for 2457 k traffic channel packets with bad CRC
CC76800 Bad
Counter for 76.8 k control channel packets with bad CRC
TC38400 Good
Counter for 38.4 k traffic channel packets with good CRC
TC38400 Bad
Counter for 38.4 k traffic channel packets with bad CRC
TC76800 Good

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 17/89


10/10/2019 Nemo Analyze KPI List
Counter for 76.8 k traffic channel packets with good CRC
TC76800 Bad
Counter for 76.8 k traffic channel packets with bad CRC
TC153600 Good
Counter for 156.6 k traffic channel packets with good CRC
TC153600 Bad
Counter for 156.6 k traffic channel packets with bad CRC

EVDO:Finger

Ec/I0
If antenna configuration is 2, then this represents Ec/Io for the paired fingers.
Ec/I0 antenna 0
Ec/I0 for finger tracking RX0
Ec/I0 antenna 1
Ec/I0 for finger tracking RX1
Finger locked
Absolute finger offset
Note that the accuracy can be greater than one chip.
Pilot number
Finger index
Index of the demodulator finger
RPC cell index
Value/index assigned to a cell by AT.
ASP index
Value/index assigned to a sector by AT.

EVDO:Power control

Power limited/Channel
Power amplifier/Channel
Percentage of "UL power up" commands
TX power
TX power (rev B)
Closed loop adjustment value
Closed loop adjustment value (rev B)
TX pilot power
TX open loop power
TX power determined by the open loop adjust mechanism
TX pilot power (rev B)
DRC channel to pilot ratio
ACK channel to pilot ratio
Data channel to pilot ratio
PA max
Maximum recommended headroom available (Rev A). The mobile station indicates the available Power Amplifier (PA)
headroom to the access network. The access network can assign carriers based on the mobile stations available power
amplifier headroom.

EVDO:RACH

Number of probes sent in last probe sequence


Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Number of probe sequences sent for this access attempt
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Maximum number of probe sequences
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 18/89


10/10/2019 Nemo Analyze KPI List

Probe sequence result


Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Number of probes per probe sequence
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Access PN
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
PN of the sector that sends the ACAck or the TCA message.
Access sector ID
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Sector ID on which the access probe was sent.
Access color code
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Color code on which the access probe was sent.

EVDO:RLP statistics

Service ID
Identifies RLP service.
Received NAKs
Retransmitted bytes
Transmitted new data bytes
Transmitted bytes
NAK timeouts
Contains NAK timeouts and aborts.
Reset count
Total resets that have occurred, initiated either by the AN or the AT.
Resets requested by the AT
Reset ACKs received from the AN
Resets requested by the AN
Received NAKs in bytes
Number of retransmitted frames not found
Received duplice bytes
Received retransmitted bytes
Received new data bytes
Received bytes
Transmitted NAKs
Transmitted NAKs in bytes
Received frames
Received new frames
Received retransmitted frames
Received frames with first data unit
Received frames with last data unit
Transmitted frames
Transmitted new frames
Retransmitted frames
Transmitted frames with first data unit
Transmitted frames with last data unit
Link flow ID
Route number
Flow protocol
Route protocol
Packet stream
Whether link flow is packet-based.
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 19/89
10/10/2019 Nemo Analyze KPI List

Sequence type
Whether link flow is doing segment-based sequencing.
Multilink multi-flow RLP forward link statistics
Multilink multi-flow RLP forward link QN instance statistics
Multilink multi-flow RLP reverse link statistics
Multilink multi-flow RLP RX processing statistics

EVDO:Session

Session attempt
Session state
Summary session layer states

GAN

Serving system and band


Recorded when channel configuration information changes.
Serving system
Recorded when channel configuration information changes.
Serving band
Recorded when channel configuration information changes.
Signal quality serving
Signal quality neighbours
RSSI serving
RSSI neighbours
Location area update failure
Recorded based on MM layer3 signaling when location area update has failed. This measurement event terminates the
location area update state.
Location area update attempt
Recorded when the mobile starts location area update using MM layer3 signaling message. This measurement event
begins the location area update state.
Location area update success
Recorded based on MM layer3 signaling when location area update has been successful. This measurement event
terminates the location area update state.
Location area update time
Routing area update failure
Recorded based on GMM signaling when routing area update is successful. This measurement event terminates the routing
area update attempt state.
Routing area update attempt
Recorded based on GMM signaling when routing area update is attempted. This measurement event begins the routing
area update attempt state.
Routing area update success
Recorded based on GMM signaling when routing area update is successful. This measurement event terminates the routing
area update attempt state.
Routing area update time
Cell identification
Cell identity of the current cell. For GSM this is 16 bit value, for UMTS this is 28 bit value (RNC ID + 16 bit cell ID), and for
LTE this is 28 bit value (eNB ID + 8 bit cell ID).
Location area code
GAN state
Recorded when GAN-specific channel information changes.
GAN channel number
Recorded when GAN-specific channel information changes.
GAN base station identification code
Recorded when GAN-specific channel information changes.
GANC IP address
GANC security gateway IP address
Recorded when GAN-specific channel information changes.
L3 signaling
Recorded when a Layer 3 or an NAS signaling message is sent or received.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 20/89


10/10/2019 Nemo Analyze KPI List

GAN signaling
Packet technology
Packet technology during data transfer
Packet technology between nemo events DAA to DAD or DAF
Packet state
Routing area code
LLC throughput uplink
The value of this parameter is calculated based on the SDUs that are stransferred through the LLC layer. Missing and
erroneous LLC blocks are excluded from the throughput calculation.
LLC throughput downlink
The value of this parameter is calculated based on the SDUs that are successfully transferred through the LLC layer.
Missing and erroneous LLC blocks are excluded from the throughput calculation.
LLC retransmission rate uplink
Cell reselection
Handover events
Handover attempt
Handover success
Handover failure
WLAN throughput uplink
WLAN throughput downlink

GSM

Serving and neighbor cell information


Information on serving and neighbouring cels from the BTS reference file
Measured cell list mobile GSM (BTS ref.)
List of distinct serving and neighbouring cells measured by the mobile.
Serving cell BTS ref. information
Information on best serving cell from the BTS reference file
Cell name (BTS ref.)
Name of the best serving cell from the BTS reference file
Serving system and band
Recorded when channel configuration information changes.
Serving system
Recorded when channel configuration information changes.
Serving band
Recorded when channel configuration information changes.
BCCH and BSIC (octal)
This parameter returns BCCH and BSIC of the serving cell. BCCH and BSIC are concatenated as one integer, where two
last digits represent the BSIC.
BCCH and BSIC (decimal)
This parameter returns BCCH and BSIC of the serving cell. BCCH and BSIC are concatenated as one integer, where two
last digits represent the BSIC.
Base station identification code
Base station identity code (octal)
Network color code
Base station color code
RX level full
The received signal level of all TDMA frames. See 3GPP TS 145.008 subclause 8.4.
RX level sub
The received signal level of the subset of the TDMA frames. See 3GPP TS 145.008 subclause 8.4.
Rx level full selected BSIC
Rx level sub selected BSIC
Rx level full selected cell ID (BTS ref.)
Coverage footprint of a cell with selected cell ID. Cell ID is looked upfrom associated BTS reference file.
Rx level sub selected cell ID (BTS ref.)
Coverage footprint of a cell with selected cell ID. Cell ID is looked upfrom associated BTS reference file.
Rx level full selected channel
Rx level sub selected channel
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 21/89
10/10/2019 Nemo Analyze KPI List

C1 criterion
Path loss criterion parameter C1 is used for cell selection and reselection. See 3GPP TS 145.008 subclause 6.4 (with GPRS,
also subclause 10.1.2).
C2 criterion
The reselection criterion C2 is used for cell reselection. This parameter is used for cell reselection when the value of the
path loss criterion C1 is over zero. See 3GPP TS 145.008 subclause 6.4.
Neighbor list
List of GSM and UMTS neighbors seen by the terminal
Number of missing GSM neighbors
C31 criterion
The signal level threshold criterion parameter C31 is used to determine whether prioritized hierarchical GPRS and LSA cell
re-selection shall apply. See 3GPP TS 145.008 subclause 10.1.2.
C32 criterion
The cell ranking criterion C32 is used in selecting cells from cells that have the same priority. See 3GPP TS 145.008
subclause 10.1.2.
HCS priority class
Defines the cell re-selection order of the cells. See 3GPP TS 145.008 subclause 10.1.3.
HCS threshold
See 3GPP TS 145.008 subclause 10.1.2.
RX quality full
Quality value measured on every TDMA frame. Use this value when DTX is inactive. See 3GPP TS 145.008 subclause 8.4.
RX quality sub
Quality value measured over the subset of every TDMA frame. Use this value when DTX is active. See 3GPP TS 145.008
subclause 8.4.
Frame error rate full
This calculation assumes all 25 frames of the SACCH multiframe have been sent. Just like RXQual Full, when DL DTX is on,
FER FULL will become invalid. This is because only 2 or 3 frames are sent when DL DTX is on.
Frame error rate sub
FER Sub is calculated as the ratio of erroneous frames to number of sent frames. With EFR speech, only 2 out of the 25
are sent when DL DTX is on. With AMR speech, either 2 or 3 frames will be sent.
Frame error rate TCH
This calculation concentrates only on TCH frames. It is also more robust when DL DTX is changing. This is because it
concentrates on the ratio of TCH frame errors to TCH frames sent.
DTX downlink
Defines if the DTX is used during the previous reporting period.
MS power level (dBm)
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
MS power level
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Radiolink timeout
Recorded when the radio link timeout changes.
The counter used in determining when the radio link failure condition is declared. The value of the counter is decreased by
one when SACCH message decoding fails. When decoding succeeds, it is increased by two. If the value of the counter
drops to zero, the radio link failure condition is declared. See 3GPP TS 145.008 subclause 5.
Timing advance
Recorded when timing advance changes.
Reported timing advance.
C/I average
C/I average is calculated over the reporting period. The C/I average is the average of all C/I values per hopping channel
(and timeslot with GPRS) when this information is available. If C/I per hopping channel or per timeslot is not available, the
C/I average calculation method is vendor specific.
C/I per timeslot
Separate C/I result for each dedicated GRPS timeslot. C/I calculation method is vendor specific.
C/I per hopping channel
C/I per hopping channel worst
Channel number and C/I of the hopping channel with worst C/I
RSSI per hopping channel
Distance based RX level average from scanner for serving cell
RX level Nth best
Nth best Rx level among serving and neighbouring cells.
RX level Nth best (dBuV/m)
Nth best Rx level among serving and neighbouring cells.
RX level Nth best neighbor

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 22/89


10/10/2019 Nemo Analyze KPI List

Missing neighbor RX level


Mobile country code
Recorded when service state or mobility information changes.
See ITU-T recommendation E.212.
Operator
Mobile network code
Recorded when service state or mobility information changes.
TMSI
Recorded when service state or mobility information changes.
Temporary mobile subscriber identity. See 3GPP TS 124.008 subclause 10.5.1.4 and 3GPP TS 123.003 subclause 2.4.
P-TMSI
Recorded when service state or mobility information changes.
Packet temporary mobile subscriber identity. See 3GPP TS 124.008 subclause 10.5.1.4 and 3GPP TS 123.003 subclause
2.7.
Location area update failure
Recorded based on MM layer3 signaling when location area update has failed. This measurement event terminates the
location area update state.
Location area update attempt
Recorded when the mobile starts location area update using MM layer3 signaling message. This measurement event
begins the location area update state.
Location area update success
Recorded based on MM layer3 signaling when location area update has been successful. This measurement event
terminates the location area update state.
Location area update time
Routing area update failure
Recorded based on GMM signaling when routing area update is successful. This measurement event terminates the routing
area update attempt state.
Routing area update attempt
Recorded based on GMM signaling when routing area update is attempted. This measurement event begins the routing
area update attempt state.
Routing area update success
Recorded based on GMM signaling when routing area update is successful. This measurement event terminates the routing
area update attempt state.
Routing area update time
Cell identification
Cell identity of the current cell. For GSM this is 16 bit value, for UMTS this is 28 bit value (RNC ID + 16 bit cell ID), and for
LTE this is 28 bit value (eNB ID + 8 bit cell ID).
Cell identifications measured
RX level neighbor
Location area code
DTX uplink
Radiolink timeout maximum
Defines the maximum value for the radio link timeout counter.
Extended channel type
BCCH channel
Timeslot number
Hopping status
HSN
Hopping sequence number. See 3GPP TS 144.018 subclause 10.5.2.5.
MAIO
Mobile allocation index offset. See 3GPP TS 144.018 subclause 10.5.2.5.
Hopping channels
L3 signaling
Recorded when a Layer 3 or an NAS signaling message is sent or received.
L3 message search
Searches for user-defined messages, with user-defined string in the message name
L2 signaling
Recorded when a Layer 3 or an NAS signaling message is sent or received.
L3 signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 23/89


10/10/2019 Nemo Analyze KPI List

Measured cells GSM


Unique combinations of BSIC and BCCH.
Downlink Band
Cell reselection GSM to UMTS
Cell reselection inter-system
Cell reselection UMTS to GSM
Cell reselection
Handover events
Handover attempt
Handover success
Handover duration
Handover attempt inter-system
Handover attempt GSM to UMTS
Handover success inter-system
Handover success GSM to UMTS
Handover attempt UMTS to GSM
Handover success UMTS to GSM
Handover failure
Handover failure inter-system
Handover failure UMTS to GSM
Handover failure GSM to UMTS
Average serving cell RX level per BCCH
C/A measurement RSSI
Signal strength for center channel.
C/A minimum
Carrier to adjacent channel ratio between center channel and the strongest adjacent channel.
C/A measurement RSSI -1
The RSSI value of the adjacent channel. The adjacent channel is 200 kHz lower than the frequency of the center channel.
C/A -1
The value of C/A -1 parameter is the ratio between center channel RSSI and adjacent channel RSSI. The adjacent channel
frequency is 200 kHz lower than the frequency of the center channel.
C/A measurement RSSI -2
The RSSI value of the adjacent channel. The adjacent channel is 400 kHz lower than the frequency of the center channel.
C/A -2
The value of C/A -2 parameter is the ratio between center channel RSSI and adjacent channel RSSI. The adjacent channel
frequency is 400 kHz lower than the frequency of the center channel.
C/A measurement RSSI +1
The RSSI value of the adjacent channel. The adjacent channel is 200 kHz higher than the frequency of the center channel.
C/A +1
The value of C/A +1 parameter is the ratio between center channel RSSI and adjacent channel RSSI. The adjacent
channel frequency is 200 kHz higher than the frequency of the center channel.
C/A measurement RSSI +2
The RSSI value of the adjacent channel. The adjacent channel is 400 kHz higher than the frequency of the center channel.
C/A +2
The value of C/A +2 parameter is the ratio between center channel RSSI and adjacent channel RSSI. The adjacent
channel frequency is 400 kHz higher than the frequency of the center channel.
Modulation 2G/3G

GSM Scanner

Measured cell list scanner GSM (BTS ref.)


List of distinct cells measured by the scanner.
C/I selected channel
C/I Nth best
C/I selected NCC
C/I
SCH RX level selected channel

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 24/89


10/10/2019 Nemo Analyze KPI List

SCH RX level Nth best


SCH RX level selected NCC
SCH RX level
RX level
RX level selected NCC
RX level selected cell ID (BTS ref.)
BSIC (octal) selected channel
RX level selected channel
Rx level top N with BTS ref. information
RX level top N
Rx level top N selected channels with BTS ref. info
Number of BCCHs within X dB from the best
Number of cells where the RSRP is within user-definable window from the best cell
RX level top N selected channels
RX level top N selected NCC
RX level Nth best selected channels
RX level Nth best selected channels MNC
RX level MNC
RX level Nth best selected channels (dBuV/m)
RX level Nth best selected NCC
Cell name Nth best selected channels
Cell identification Nth best selected channels
Cell name Nth best
Cell identification Nth best
Rx level Nth best selected channels with BTS ref. information
Rx level Nth best selected NCC with BTS ref. information
RX level Nth best
RX level distance based average selected carriers
RX level Nth best distance based average selected carriers
Rx level Nth best with BTS ref. information
BSIC Nth best
BSIC Nth best (octal)
Channel and BSIC Nth best
This parameter returns channel number and BSIC of the Nth best channel in terms of Rx level. Channel number and BSIC
are concatenated as one integer, where two last digits represent the BSIC.
BCCH Nth best
This parameter returns BCCH of the Nth best channel in terms of Rx level.
BCCH Nth best selected channels
This parameter returns BCCH of the Nth best channel in terms of Rx level.
ARFCN Nth best selected channels
This parameter returns ARFCN (channel number) of the Nth best channel in terms of Rx level.
Frequency Nth best selected channels
This parameter returns ARFCN (channel number) of the Nth best channel in terms of Rx level.
Channel and BSIC (octal) Nth best
This parameter returns channel number and BSIC of the Nth best channel in terms of Rx level. Channel number and BSIC
are concatenated as one integer, where two last digits represent the BSIC.
Channel and BSIC (octal) Nth best selected channels
This parameter returns channel number and BSIC of the Nth best channel in terms of Rx level. Channel number and BSIC
are concatenated as one integer, where two last digits represent the BSIC.
L3 signaling
L3 message search
Searches for user-defined messages, with user-defined string in the message name
Cellscan and Scan events combined
L3 signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 25/89


10/10/2019 Nemo Analyze KPI List

Scanning configuration
Defines scanning settings.
C/A
Ratio between channel and adjacent channels (dB)
C/A selected NCC
Ratio between channel and adjacent channels (dB)
Cellscan
Recorded when parameter sample is received from the device. With GSM the system information messages, and with
UMTS and LTE the system information blocks, are decoded to produce the information required for this measurement
event.
Interference analysis

GSM:GPRS/EDGE

Packet RX quality
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
See 3GPP TS 145.008 subclause 8.2.3.1. This parameter is only recorded for GPRS.
C value
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Received signal level of each paging block monitored by the MS according to its current DRX mode and its paging group.
See 3GPP TS 145.008 subclause 10.2.3.1. This parameter is only recorded for GPRS.
Signal variance
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Average variance of signal level (C value). See 3GPP TS 145.008 subclause 10.2.3.1. This parameter is only recorded for
GPRS.
Timeslot interference
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Timeslot interference level relative to C value. See 3GPP TS 145.008 subclause 10.3. This parameter is only recorded for
GPRS.
Downlink signaling counter current
Recorded when downlink signaling counter value changes.
The counter used in determining when the downlink signaling failure condition is declared. Whenever the message is
decoded in the paging subchannel; if the message decoding is successful, the DSC counter is increased by one; if the
message decoding fails, the DSC counter is decreased by four. The downlink signaling failure condition is declared if the
DSC counter drops to zero or below. See 3GPP TS 145.008 subclause 6.5.
Downlink signaling counter maximum
Recorded when downlink signaling counter value changes.
The maximum value of the DSC counter.
BEP mean class GMSK
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Recorded only when EGPRS is used.
See 3GPP TS 145.008 subclause 8.2.3.2.
BEP CV class GMSK
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Recorded only when EGPRS is used.
See 3GPP TS 145.008 subclause 8.2.3.2.
BEP mean class 8-PSK
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Recorded only when EGPRS is used.
See 3GPP TS 145.008 subclause 8.2.3.2.
BEP CV class 8-PSK
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Recorded only when EGPRS is used.
See 3GPP TS 145.008 subclause 8.2.3.2.
RLC/MAC and L3 signaling
RLC/MAC/L3/RRC signaling DL and UL separated
RLC/MAC/L3/RRC signaling
RLC/MAC message search
Searches for user-defined messages, with user-defined string in the message name
RLC/MAC signaling
LLC signaling
Recorded when an LLC signaling message is sent or received.
Packet technology
Packet technology during data transfer

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 26/89


10/10/2019 Nemo Analyze KPI List
Packet technology between nemo events DAA to DAD or DAF
Packet state
Routing area code
Radio priority
The RLC/MAC radio priority level for uplink user data transmission.
Priority access THR
Priority access threshold.
Split PG cycle
The split PG cycle parameter defines the DRX period.
Packet channel coding uplink
Packet channel coding downlink
Number of packet timeslots uplink
Number of packet timeslots downlink
Number of packet timeslots downlink and uplink
Network mode of operation
Network control order
Incremental redundancy status uplink
This is same as resegment bit in RLC/MAC signaling messages and also known as ARQ mode. See 3GPP TS 144.060
subclause 8.1.1.
PBCCH status
GPRS cell reselection hysteresis
GPRS cell reselection penalty time
Packet timeslots downlink
Packet timeslots uplink
BLER DL
RLC blocks total
The total number of received RLC layer PDUs.
RLC blocks erroneous
The number of erroneously received RLC layer PDUs.
RLC throughput uplink
The value of this parameter is calculated based on the SDUs that are successfully transferred through the RLC layer.
Missing and erroneous RLC blocks are excluded from the throughput calculation.
RLC throughput downlink
The value of this parameter is calculated based on the SDUs that are successfully transferred through the RLC layer.
Missing and erroneous RLC blocks are excluded from the throughput calculation.
RLC retransmission rate uplink
LLC throughput uplink
The value of this parameter is calculated based on the SDUs that are stransferred through the LLC layer. Missing and
erroneous LLC blocks are excluded from the throughput calculation.
LLC throughput downlink
The value of this parameter is calculated based on the SDUs that are successfully transferred through the LLC layer.
Missing and erroneous LLC blocks are excluded from the throughput calculation.
LLC retransmission rate uplink
Temporary logical link identity
Recorded when TBF allocation is modified. This information can be based on RLC/MAC and layer3 signaling, or on trace
messages received from the device.
TBF uplink establishment failed
Recorded after TBF uplink establishment attempt. The recorded information is based on RLC/MAC and layer3 signaling
messages.
TBF uplink establishment aborted
Recorded after TBF uplink establishment attempt. The recorded information is based on RLC/MAC and layer3 signaling
messages.
TBF uplink establishment rejected
Recorded after TBF uplink establishment attempt. The recorded information is based on RLC/MAC and layer3 signaling
messages.
Number of uplink TBFs
Recorded when TBF allocation is modified. This information can be based on RLC/MAC and layer3 signaling, or on trace
messages received from the device.
Number of downlink TBFs
Recorded when TBF allocation is modified. This information can be based on RLC/MAC and layer3 signaling, or on trace
messages received from the device.
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 27/89
10/10/2019 Nemo Analyze KPI List

TFI uplink
RLC window size uplink
TFI downlink
RLC window size downlink
RLC/MAC signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message
EDGE coding DL distribution
EDGE coding UL distribution
GPRS coding DL distribution
GPRS coding UL distribution
Uplink TBF establishment cause
Recorded after TBF uplink establishment attempt. The recorded information is based on RLC/MAC and layer3 signaling
messages.
TBF UL establishment status
Recorded after TBF uplink establishment attempt. The recorded information is based on RLC/MAC and layer3 signaling
messages.

LTE

Cell reselection U-plane interruption time


The time from the last packet in the old cell to the first packet in the new cell. This parameter is only recorded during the
data transfer and only for LTE to LTE, LTE to HSPA, and HSPA to LTE cell reselections and redirections.
RLC downlink throughput
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Total downlink RLC throughput is calculated over all radio bearers. The value of this parameter is calculated based on the
SDUs that are successfully transferred through the RLC layer. Missing and erroneous RLC blocks are excluded from the
throughput calculation.
RLC downlink block rate
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Total number of correctly or incorrectly received RLC PDUs calculated from all active radio bearers.
RLC downlink BLER
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Total downlink RLC BLER calculated from all activate radio bearers.
RLC downlink throughput per RB
The value of this parameter is calculated based on the SDUs that are successfully transferred through the RLC layer.
Missing and erroneous RLC blocks are excluded from the throughput calculation.
RLC downlink block rate per RB
The number of correctly or incorrectly received RLC PDUs from the defined radio bearer.
RLC downlink BLER per RB
RLC uplink throughput
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Total uplink RLC throughput. The value of this parameter is calculated based on the SDUs that are successfully transferred
through the RLC layer. Missing and erroneous RLC blocks are excluded from the throughput calculation.
RLC uplink block rate
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Total number of correctly or incorrectly transmitted RLC PDUs calculated from all active radio bearers.
RLC uplink retransmission rate
Total uplink RLC retransmission rate calculated from all active radio bearers.
RLC uplink throughput per RB
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
The value of this parameter is calculated based on the SDUs that are successfully transferred through the RLC layer.
Missing and erroneous RLC blocks are excluded from the throughput calculation.
RLC uplink block rate per RB
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
The number of correctly or incorrectly transmitted RLC PDUs from the defined radio bearer.
RLC uplink retransmission rate per RB
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
PDCP downlink throughput
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Total downlink PDCP throughput is calculated over all radio bearers. The value of this parameter is calculated based on the
SDUs that are successfully transferred through the PDCP layer. Missing and erroneous PDCP blocks are excluded from the
throughput calculation.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 28/89


10/10/2019 Nemo Analyze KPI List

PDCP downlink block rate


Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Total number of correctly or incorrectly received PDCP PDUs calculated from all active radio bearers.
PDCP downlink throughput per RB
The value of this parameter is calculated based on the SDUs that are successfully transferred through the PDCP layer.
Missing and erroneous PDCP blocks are excluded from the throughput calculation.
PDCP downlink block rate per RB
The number of correctly or incorrectly received PDCP PDUs from the defined radio bearer.
PDCP uplink throughput
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Total uplink PDCP throughput. The value of this parameter is calculated based on the SDUs that are successfully
transferred through the PDCP layer. Missing and erroneous PDCP blocks are excluded from the throughput calculation.
PDCP uplink block rate
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Total number of correctly or incorrectly transmitted PDCP PDUs calculated from all active radio bearers.
PDCP uplink throughput per RB
The value of this parameter is calculated based on the SDUs that are successfully transferred through the PDCP layer.
Missing and erroneous PDCP blocks are excluded from the throughput calculation.
PDCP uplink block rate per RB
The number of correctly or incorrectly transmitted PDCP PDUs from the defined radio bearer.
PDSCH scheduled throughput/PRB
Scheduled throughput per PRB is the average throughput per PRB over the TTIs where PRB resources are allocated. This is
calculated by summing PDSCH throughput per PRB during the reporting period and this is divided by number of allocated
PRBs during the reporting period.
Channel number
Tracking area code
Tracking area code of the current serving cell. See 3GPP TS 124.301 subclause 9.9.3.32.
Max TX power
Physical cell identity
Transmission mode
See 3GPP TS 136.213 subclase 7.1.
TTI bundling
See 3GPP TS 136.321 subclause 5.4.2.
Detected TX antenna ports
DL bandwidth
TDD UL/DL configuration
TDD UL/DL configuration defines the symbols that are allocated for uplink and downlink. See 3GPP 36.211 subclause 4.2.
Cyclic prefix UL
This is uplink cyclic prefix. Extended cyclic prefix can reduce inter-symbol-interference when multipath components have
significant arrival time deviation from each other.
C-RNTI
Cell Radio Network Temporary Identifier. A dynamic identity assigned by eNodeB and is valid as long as the UE is
connected to that eNB.
RSRP Nth best
RSRP of the Nth strongest cell, where the strongest cell is selected in terms of RSRP
Distance based RSRP average from scanner for serving cell
RSRP Nth best selected set
RSRP of the Nth strongest cell of selected set (active/monitored/detected), where the strongest cell is selected in terms of
RSRP
RSRP Nth best selected set (dBuV/m)
RSRP of the Nth strongest cell of selected set (active/monitored/detected), where the strongest cell is selected in terms of
RSRP
RSRP selected PCI
RSRP serving cell primary and secondary carriers
RSRQ serving cell primary and secondary carriers
RSRQ serving cell delta primary vs. secondary carrier
Difference between primary and secondary cell measured RSRQ (dB)
RSRP serving cell delta primary vs. secondary carrier
Difference between primary and secondary cell measured RSRP (dBm)
RSRP serving cell primary
RSRP serving cell secondary 0
RSRP serving cell secondary 1
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 29/89
10/10/2019 Nemo Analyze KPI List

RSRP listed set


RSRP detected set
RSRP serving cell primary with BTS ref. information
RSRP serving cell secondary with BTS ref. information
RSRP listed set with BTS ref. information
RSRP detected set with BTS ref. information
RSRQ Nth best
RSRQ of the Nth strongest cell, where strongest cell is selected in terms of RSRP
RSRQ Nth best selected set
RSRQ of the Nth strongest cell of selected set (active/monitored/detected), where strongest cell is selected in terms of
RSRP
RSRQ selected PCI
RSRQ serving cell primary
RSRQ serving cell secondary 0
RSRQ serving cell secondary 1
RSRQ listed set
RSRQ detected set
E-UTRAN carrier RSSI
E-UTRAN carrier RSSI Nth best selected set
E-UTRAN carrier RSSI of the Nth strongest cell of selected set (active/monitored/detected), where the strongest cell is
selected in terms of RSRP
RS SNR
The calculation method for this parameter is device specific and can change between the devices.
Timing advance
Recorded when timing advance changes.
Timing advance is used to adjust uplink transmission timing in a way that allows node B to receive transmissions from all
UEs simultanously. The timing advance is relative to downlink radio frame received by UE. This parameter is the same as
N_TA parameter divided by 16. See 3GPP TS 36.213 subclause 4.2.3 and 3GPP TS 36.211 subclause 8.
TX power PUCCH
The average transmit power for PUCCH calculated over the reporting period. See 3GPP TS 36.213 subclause 5.1.2.1.
TX power PUSCH
The average transmit power for PUSCH calculated over the reporting period. See 3GPP TS 36.213 subclause 5.1.1.1.
TX power headroom (PUSCH)
The average UE power headroom reported from the same reporting period as PUSCH TX power. See 3GPP TS 36.213
subclause 5.1.1.2.
TX power PUSCH adjustment
The average PUSCH power control adjustment during the last reporting period. Same as f(i) parameter in 3GPP TS 36.213
subclause 5.1.1.1.
TX power PUCCH adjustment
The average PUCCH power control adjustment during the last reporting period. Same as g(i) parameter in 3GPP TS 36.213
subclause 5.1.2.1.
PUSCH TPC count
The number of times this TPC command is received since the previous report.
PUSCH TPC
This is the same as delta_PUSCH. See 3GPP TS 136.213 subclause 5.1.1.
PUCCH TPC count
The number of times this TPC command is received since the previous report.
PUCCH TPC
This is the same as delta_PUCCH. See 3GPP TS 136.123 subclause 5.1.2.
PBCH block rate
PBCH BLER
Physical Downlink Shared Channel (PDSCH) block error rate. Block error rate (BLER) is the number of received erroneous
blocks per total number of sent blocks. Erroneous blocks are found with the cyclic redundancy check (CRC), see 3GPP TS
34.121-1 subclause F.6.1.1.
PDSCH throughput
The throughput is calculated from all received transport blocks including TBs with CRC failure.
PDSCH throughput delta primary vs. secondary carrier
Difference between measured PDSCH throughput of the primary and secondary LTE carrier aggregation componen carriers
PDSCH throughput for codeword 0
PDSCH throughput for codeword 1

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 30/89


10/10/2019 Nemo Analyze KPI List

PDSCH block rate


The number of received transport blocks since the last report including TBs with CRC failure.
PDSCH BLER
The ratio of transport blocks with CRC check accepted to all received TBs.
PDCCH BLER estimation
This parameter estimates PDCCH BLER by calculating number of undetected and missed downlink grants. The parameter
does not contain all possible PDCCH errors so it is more of an indicative rathern than an absolute ratio of errors in the
PDCCH channel. Note that the exact calculation method of the parameter can change in the future.
PUSCH throughput
This is calculated from all transmitted transport blocks including TBs that are not delivered succesfully or are delivered
redundantly.
Measurement event
Recorded when a UMTS measurement event is transmitted to the network based on signaling messages.
See 3GPP TS 136.331 subclause 5.5.4.
Measurement ID
Recorded when a UMTS measurement event is transmitted to the network based on signaling messages.
See 3GPP TS 136.331 subclause 5.5.
Serving cell BTS ref. information
Information on best serving cell from the BTS reference file
Cell name (BTS ref.)
Name of the best serving cell from the BTS reference file
Serving system and band
Recorded when channel configuration information changes.
Serving system
Recorded when channel configuration information changes.
Mobile country code
Recorded when service state or mobility information changes.
See ITU-T recommendation E.212.
Operator
Mobile network code
Recorded when service state or mobility information changes.
TMSI
Recorded when service state or mobility information changes.
Temporary mobile subscriber identity. See 3GPP TS 124.008 subclause 10.5.1.4 and 3GPP TS 123.003 subclause 2.4.
P-TMSI
Recorded when service state or mobility information changes.
Packet temporary mobile subscriber identity. See 3GPP TS 124.008 subclause 10.5.1.4 and 3GPP TS 123.003 subclause
2.7.
MME group ID
Recorded when service state or mobility information changes.
Mobility Management Entity (MME) group identification is used to differentiate between pools of MMEs. See 3GPP TS
123.003.
Automatic neighbour relation information
Recorded when the CGI is configured to measure or reported by the mobile.
MME code
Recorded when service state or mobility information changes.
Identifies Mobility Management Entities (MME) within the MME pool areas. See 3GPP TS 123.003.
M-TMSI
Recorded when service state or mobility information changes.
M-Temporary Moblie subscriber Identity. See 3GPP TS 123.003.
Tracking area update attempt
Recorded based on EMM signaling when tracking area update is attempted. For more information about the tracking area
update procedure, see 3GPP TS 124.301 subclause 5.5.3. This measurement event begins the tracking area update
attempt state.
Tracking area update success
Recorded based on EMM signaling when tracking area update is successful. For more information about the tracking area
update procedure, see 3GPP TS 124.301 subclause 5.5.3. This measurement event terminates the tracking area update
attempt state.
Tracking area update failure
Recorded based on EMM signaling when tracking area update is successful. For more information about the tracking area
update procedure, see 3GPP TS 124.301 subclause 5.5.3. This measurement event terminates the routing area update
attempt state.
Tracking area update time
Time from tracking area update attempt (Nemo event TUA) to success (Nemo event TUS)
Cell identification
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 31/89
10/10/2019 Nemo Analyze KPI List
Cell identity of the current cell. For GSM this is 16 bit value, for UMTS this is 28 bit value (RNC ID + 16 bit cell ID), and for
LTE this is 28 bit value (eNB ID + 8 bit cell ID).
Location area code
LTE carrier aggregation status
Indicates whether LTE CA is in use at given time. CA is differentiated for different amounts of composite carriers (CCs)
L3 signaling
Recorded when a Layer 3 or an NAS signaling message is sent or received.
Packet technology
Packet technology during data transfer
Packet technology between nemo events DAA to DAD or DAF
Packet state
L3 signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message
Pilot pollution number of polluting cells
Number of cells that are within user defined window from the active set best cell in terms of RSRQ, when active set best
RSRP is above, and active set best RSRQ is below use defined threshold.
EPS bearer allocation attempt
Recorded when the EPS bearer allocation is attempted. This is based on the NAS signaling or information received from
the trace interface. Also this can be logged to the beginning of the measurement file to indicate already established EPS
bearer.
EPS bearer allocation success
Recorded when the EPS bearer allocation succeeded. This is based on NAS signaling or information received from the trace
interface. Also this can be logged to the beginning of the measurement file to indicate already established EPS bearer.
EPS bearer release
Recorded when the EPS bearer is released. This is based on NAS signaling or information received from the trace
interface.
EPS bearer allocation failure
F-factor mobile (CINR estimate)
Estimate of SNR/CINR assuming all cells are fully loaded. Calculation: best cell RSCP / (2nd best RSRP + 3rd best RSRP +
... + Thermal noise (-132dBm)). Expressed in decibels
Number of cells within X dB window from the best
Number of cells where the RSRP is within user-definable window from the best cell
Cell reselection inter-system
Cell reselection
Handover events
Handover attempt
Handover success
Handover failure
Handover duration
With the LTE this defines the handover duration containing handover processing and interrupt time. Time from the
handover initiating RRC signaling message to the succesfully completed RACH procedure in the new cell.
Handover to preamble time
Time from handover attempt (RRC signaling message) to the first random access preamble (MSG1) in the target cell. Only
support for LTE to LTE handovers.
Handover U-plane interruption time
Defines the time from the last packet in the old cell to the first packet in the new cell.
Handover attempt inter-system
Handover success inter-system
Handover failure inter-system
RSRP/Antenna port
Currently the recording interval is about two times per second. This measurement event is currently only logged for
serving cells.
RSRQ/Antenna port
Currently the recording interval is about two times per second. This measurement event is currently only logged for
serving cells.
E-UTRAN carrier RSSI/Antenna port
Currently the recording interval is about two times per second. This measurement event is currently only logged for
serving cells.
RS SNR/Antenna port
LTE cell frame timing

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 32/89


10/10/2019 Nemo Analyze KPI List

PDCCH CFI 1 percentage


Defines how many percent of subframes are using CFI 1 meaning that 1 symbol (2 when 1.4 MHz bandwidth) is allocated
for PDCCH. See 3GPP TS 36.212 subclause 5.3.4.
PDCCH CFI 2 percentage
Defines how many percent of subframes are using CFI 2 meaning that 2 symbols (3 when 1.4 MHz bandwidth) are
allocated for PDCCH. See 3GPP TS 36.212 subclause 5.3.4.
PDCCH CFI 3 percentage
Defines how many percent of subframes are using CFI 3 meaning that 3 symbols (4 when 1.4 MHz bandwidth) are
allocated for PDCCH. See 3GPP TS 36.212 subclause 5.3.4.
LTE secondary serving cells
LTE pathloss

LTE Scanner

P-SCH CINR
The ratio between synchronization channel received power and interference and noise from the same synchronization
signal set.
LTE RRC signaling
RSRP Nth best distance based average selected carriers
RSRP distance based average selected carriers
Carrier RSSI (frequency scanning mode) selected channel
Carrier RSSI (frequency scanning mode)
Carrier RSSI (OFDM scanning mode) selected channel
Carrier RSSI (OFDM scanning mode)
RS CINR Nth strongest cell selected carriers
RS CINR top N cell selected carriers with BTS ref. info
RS CINR top N cell selected carriers
RS Carrier RSSI Nth strongest cell selected carriers
RSRQ Nth best selected carriers with BTS ref. info
RSRQ Nth best selected carriers
RSRQ distance based average selected carriers
RSRQ top N selected carriers with BTS ref. info
RSRQ top N selected carriers
RSRP Nth best selected carriers with BTS ref. info
RSRP Nth best selected carriers
RSRP Nth best selected carriers MNC
RSRP MNC
RSRP Nth best selected carriers (dBuV/m)
RSRP top N selected carriers with BTS ref. info
RSRP top N selected carriers
L3 signaling
LTE RRC signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message
Scanning configuration
Defines scanning settings.
F-factor scanner (CINR estimate)
Estimate of SNR/CINR assuming all cells are fully loaded. Calculation: best cell RSCP / (2nd best RSRP + 3rd best RSRP +
... + Thermal noise (-132dBm)). Expressed in decibels
F-factor scanner
F-factor indicates the interference conditions assuming all cells are fully loaded (worst case scenario). Calculation: (2nd
best RSRP + 3rd best RSRP + ... + Thermal noise (-132dBm))/best cell RSCP.
Number of pilots within X dB window from the best
Number of cells where the RSRP is within user-definable window from the best cell
Cellscan
Recorded when parameter sample is received from the device. With GSM the system information messages, and with
UMTS and LTE the system information blocks, are decoded to produce the information required for this measurement
event.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 33/89


10/10/2019 Nemo Analyze KPI List

Cyclic prefix DL
Detected TX antenna ports
RSRP selected PCI scanner
RS Carrier RSSI selected PCI scanner
Scanning result indication
The parameter contains the status of the measurement result. This is a bit field so the value of the parameter is the sum
of all simultaneouns measurement statuses, e.g. if the antenna power imbalance and frequency offset too large conditions
happen simultaneously the recorded value would be three.
2x2 MIMO rank estimation/PRB (Rohde & Schwarz)
2x2 MIMO rank estimation/PRB (Nemo FSR1)
2x2 MIMO condition number/PRB (Rohde & Schwarz)
2x2 MIMO condition number/PRB (Nemo FSR1)
2x4 MIMO rank estimation/PRB (Rohde & Schwarz)
2x4 MIMO rank estimation/PRB (Nemo FSR1)
2x4 MIMO condition number/PRB (Rohde & Schwarz)
2x4 MIMO condition number/PRB (Nemo FSR1)
RSRP/PRB
CINR/PRB
2x2 MIMO condition number (PCTel)
Physical resource block scanning results (PCTel)
Physical resource block OLSM CQI (PCTel)
RS scanning results per antenna port
RSRP, RSRQ, and CINR reported per cell per antenna port
RSRP selected antenna port
RSRPs readings of selected antenna port
RS Carrier RSSI selected antenna port
RSSI readings of selected antenna port
RSRQ selected antenna port
RSRQ readings of selected antenna port
RS CINR selected antenna port
RSRQ readings of selected antenna port
RSRP
Reference signal received power is the linear average of the power contributions of the resource elements that carry cell-
specific reference signals within the considered measurement frequency. 3GPP TS 36.214 subclause 5.1.1.
RS CINR Nth strongest cell
CINR of the Nth strongest cell in terms of RSRP
RSRQ Nth strongest cell
RSRQ of the Nth strongest cell in terms of RSRP
S-SCH received CINR Nth strongest cell
S-SCH received CINR of the Nth strongest cell
P-SCH received quality Nth strongest cell
P-SCH received quality of the Nth strongest cell
S-SCH received quality Nth strongest cell
S-SCH received quality of the Nth strongest cell
S-SCH received power Nth strongest cell
S-SCH received power of the Nth strongest cell
P-SCH received power Nth strongest cell
P-SCH received power of the Nth strongest cell
RSRP Nth strongest cell
RSRP of the Nth strongest cell
Physical cell ID Nth strongest cell
PCI of the Nth strongest cell in terms of RSRP
RS Carrier RSSI Nth strongest cell
RSSI of the Nth strongest cell in terms of RSRP
RSRQ selected PCI scanner
RSRQ
Reference signal received quality is the ratio N * RSRP / E-UTRA carrier RSSI, where N is the number of resource blocks of
the E-UTRA carrier RSSI measurement bandwidth. The measurements in the numerator and denominator are made over
the same set of resource blocks. 3GPP TS 36.214 subclause 5.1.3.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 34/89


10/10/2019 Nemo Analyze KPI List

RS CINR selected PCI scanner


CINR
Ratio between the reference signal received power (RSRP) and the interference and noise from the same reference signal
set.
Time offset RS
Delay spread
The unit of the parameter is 32.552ns that is the same as the Ts parameter defined by 3GPP TS 136.211 subclause 4.
P-SCH RSRP
Linear average over the power contributions of the resource elements that carry primary synchronization signal.
P-SCH RSRQ
The ratio between P-SCH reference power (P-SCH RP) and linear average of total received power measured over OFDM
symbols and resource blocks, including primary synchronization (P-SCH) signal. The measurements in the numerator and
denominator are made over the same set of resource blocks.
S-SCH RSRP
Linear average over the power contributions of the resource elements that carry secondary synchronization signal.
S-SCH RSRQ
The ratio between S-SCH reference power (S-SCH RP) and linear average of total received power measured over OFDM
symbols and resource blocks, including secondary synchronization (S-SCH) signal. The measurements in the numerator
and denominator are made over the same set of resource blocks.
S-SCH CINR
The ratio between synchronization channel received power and interference and noise from the same synchronization
signal set.
Time offset SCH
PBCH RSRP
Currently support for this parameter has not been implemented.
PBCH RSRQ
Currently support for this parameter has not been implemented.
PBCH CINR
Currently support for this parameter has not been implemented.
Time offset PBCH

LTE:Link adaptation

Requested throughput
Requested rank distribution
Requested rank (mode)
The most common requested rank over the reporting period
Wideband CQI for codeword 0
This is the average wideband CQI calculated over the reporting period. See 3GPP TS 36.213 subclause 7.2.
Wideband CQI for codeword 1
This is the average wideband CQI calculated over the reporting period. See 3GPP TS 36.213 subclause 7.2.
Subband CQI for codeword 0
The subband CQI is the average calculated over the subbands defined by higher layer or selected by mobile. This reported
subband CQI value is furthermore averaged over the reporting period before it is logged to the measurement event. More
information about CQI see 3GPP TS 36.213 subclause 7.2.
Subband CQI for codeword 1
The subband CQI is the average calculated over the subbands defined by higher layer or selected by mobile. This reported
subband CQI value is furthermore averaged over the reporting period before it is logged to the measurement event. More
information about CQI see 3GPP TS 36.213 subclause 7.2.
Wideband PMI
The logged value is the most commonly used value during the reporting period. A user equipment uses Precoding Matrix
Indicator (PMI) to inform the eNodeB which precoding matrix should be used for downlink transmission according to the
rank indication. See 3GPP TS 136.213 subclause 7.2.4.
CQI for codeword 0 per subband
The average channel quality index value over the reporting period for defined subband. Not available when the best M
select mode is used. More information about CQI see 3GPP TS 36.213 subclause 7.2.
CQI for codeword 1 per subband
The average channel quality index value over the reporting period for defined subband. Not available when the best M
select mode is used. More information about CQI see 3GPP TS 36.213 subclause 7.2.
PRB utilization DL delta primary vs. secondary carrier
Difference between DL PRB utilization percentage of primary and secondary carriers in LTE carrier aggregation (%)
PRB utilization DL
Downlink PRB utilization proportional to bandwidth and reporting period.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 35/89


10/10/2019 Nemo Analyze KPI List

PRB utilization DL/Index


PRB utilization UL
Uplink PRB utilization proportional to bandwidth and reporting period.
PRB utilization UL/Index
PDSCH average transport block size
PDSCH maximum transport block size
PUSCH average transport block size
PUSCH maximum transport block size
LTE link adaptation parameter distribution downlink
LTE PDSCH PRBs allocated (mode)
The most common number of PRBs allocated over the reporting period
LTE PDSCH PRBs allocated (avg)
Average number of PRBs allocated over the reporting period
LTE PUSCH PRBs allocated (mode)
The most common number of PRBs allocated over the reporting period
LTE PUSCH PRBs allocated (avg)
Average number of PRBs allocated over the reporting period
LTE PDSCH PRBs allocated distribution
LTE PUSCH PRBs allocated distribution
PDSCH modulation codeword 0 (mode)
The most common value of the PDSCH modulation codeword 0 over the reporting period
PDSCH MCS index for codeword 0 (mode)
The most common value of the PDSCH MCS index for codeword 0 over the reporting period
PDSCH modulation codeword 1 (mode)
The most common value of the PDSCH modulation codeword 1 over the reporting period
PDSCH MCS index for codeword 1 (mode)
The most common value of the MCS index for codeword 1 over the reporting period
PDSCH rank 2 percentage
Percentage of Rank 2 (2x2 MIMO) over the reporting period
PDSCH rank (mode)
The most common value of the PDSCH rank over the reporting period
LTE link adaptation parameter distribution uplink
PUSCH MCS index for codeword 0 (mode)
The most common value of the PUSCH MCS index for codeword 0 over the reporting period
PUSCH modulation codeword 0 (mode)
The most common value of the PUSCH modulation codeword 0 over the reporting period
PUSCH rank (mode)
The most common value of the PUSCH rank over the reporting period
LTE DL active TTIs rate
Percentage of TTIs over the reporting periond (200ms or 100ms depending on the terminal) when there has been data
allocated to the terminal.

LTE:MAC

MAC downlink block rate


Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
Number of succesfully received transport blocks excluding redundant TBs.
MAC downlink BLER 3rd+
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
The ratio of 3rd or more retransmission to all received TBs.
MAC downlink BLER 1st
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
The ratio of 1st retransmissions to all received TBs.
MAC downlink BLER 2nd
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 36/89
10/10/2019 Nemo Analyze KPI List
session. Separate measurement event is logged for each serving cell with LTE.
The ratio of 2nd retransmissions to all received TBs.
MAC downlink BLER
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
The ratio of erroneously received transport blocks to all received transport blocks.
MAC downlink residual BLER
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
Defines the ratio of transport blocks that HARQ was not able to correct and RLC layer has to fix. The ratio of HARQ failed
transport blocks to new transmissions.
MAC downlink throughput
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
MAC throughput that is calculated from succesfully received SDUs. With the devices that do not support MAC throughput
parameter the estimation of MAC throughput is calculated from succesfully received transport blocks. The estimation is a
little bit higher than the real MAC throughput since it includes MAC header, MAC control data, and padding to the
throughput.
MAC downlink new blocks
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
The number of received new (1st attempt) transport blocks since the last report.
MAC downlink redundant retransmission
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
The ratio of transport blocks that were already correctly received and have unnecessarily been retransmitted (duplicated
transmission). This happens when the ACK message sent by the mobile is decoded or received incorrectly, or not received
at all, by the the base station.
MAC uplink retransmission rate 3rd+
Recorded when measurement sample is received from the device.
The ratio of 3rd or more retransmissions to all transmitted TBs.
MAC uplink retransmission rate 1st
Recorded when measurement sample is received from the device.
The ratio of 1st retransmissions to all transmitted TBs.
MAC uplink retransmission rate 2nd
Recorded when measurement sample is received from the device.
The ratio of 2nd retransmissions to all transmitted TBs.
MAC uplink retransmission rate
Recorded when measurement sample is received from the device.
The ratio of retransmitted transport blocks to all transmitted TBs.
MAC uplink residual BLER
Recorded when measurement sample is received from the device.
Defines the ratio of transport blocks that HARQ was not able to correct and RLC layer have to fix. The ratio of HARQ failed
transport blocksk to new transmissions.
MAC uplink block rate
Recorded when measurement sample is received from the device.
The number of successfully transmitted transport blocks since previous report.
MAC uplink throughput
Recorded when measurement sample is received from the device.
The throughput that is calculated from succesfully transmitted MAC SDUs. With the devices that do not support MAC
throughput parameter the estimation of MAC throughput is calculated from succesfully delivered transport blocks. The
estimation is a little bit higher than the real MAC throughput since it includes MAC headers, MAC control data, and
padding.

LTE:RACH

RACH PUSCH power


Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
For successful RACH procedures this contains the TX power used for message sending in PUSCH.
RACH preamble initial TX power
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 37/89


10/10/2019 Nemo Analyze KPI List
TX power used for the first preamble. See 3GPP TS 36.321 subclause 5.1.3.
RACH type
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
More information about RACH procedure in LTE see 3GPP TS 36.213 subclause 6 and 3GPP TS 36.321 subclause 5.1.
RACH preamble responses with PUSCH resource
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH preamble responses with backoff time
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH result
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH contention resolution failures
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH pathloss
An estimate of the radio condition for the RACH procedure. Pathloss is used for initial TX power. See 3GPP TS 36.213
subclause 6.1.
RACH preamble count
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Defines the number of preambles that were sent during the RACH procedure. This is the same as
PREAMBLE_TRANSMISSION_COUNTER after end of the RACH procedure.
RACH maximum preamble count
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
This is the same as preambleTransMax. See 3GPP TS 136.133 subclause 6.3.2 and 136.321 subclause 5.1.
RACH reason
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Reason for the RACH procedure.
RACH preamble step
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
This parameter is the same as power ramping step. 3GPP TS 36.321 subclause 5.1.
RACH preamble index
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
The preamble index of the last successfully transmitted preamble. This is only valid for successful RACH procedures. This
parameter is same as preamble sequence or random access preamble ID (RAPID). See 3GPP TS 136.321 subclause 5.
RACH access delay
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Time from initial MSG1 to MSG2 for non-contention based RACH procedures and time from initial MSG1 to MSG4 for
contention based RACH procedures. Valid only for succesful RACH procedures.
RACH logical root sequence index
Logical root Zadoff-Chu sequence order number. See 3GPP 136.211 subclause 5.7.2.
TDD special subframe configuration
This parameter defines the duration of special subframes between uplink and downlink switching. See 3GPP 136.211
subclause 4.2.
EMM substate
See 3GPP 124.301 subclause 5.1.3.
CQI periodic reporting mode
See 3GPP TS 136.213 subclause 7.2.2.
CQI aperiodic reporting mode
This is the same as cqi-ReportModeAperiodic parameter in CQI-ReportConfig. More information see 3GPP TS 136.213
subclause 7.2.1.

LTE:RRC

LTE RRC signaling


RRC state
See 3GPP TS 136.331 subclause 4.2.1.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 38/89


10/10/2019 Nemo Analyze KPI List

RLC/MAC/L3/RRC signaling DL and UL separated


RLC/MAC/L3/RRC signaling
LTE RRC signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message
RRC connection attempt
RRC connection connected
Recorded based on RRC signaling when RRC connection is established. This measurement event begins the RRC
connection state.
RRC connection disconnected
Recorded based on RRC signaling when RRC connection is released. This measurement event terminates the RRC
connection state.
LTE RRC connection dropped
Recorded based on RRC signaling when RRC connection is released. This measurement event terminates the RRC
connection state.
RRC connection attempt failure
Recorded based on RRC signaling when RRC connection attempt fails. This measurement event terminates the RRC
connection attempt state.
RRC re-establishment
Recorded based on RRC signaling after successful or failed RRC connection re-establishment.

Messages REMS:Standard and REMS:CSelBSInfo

RxLevAccess

Messages REMS:Standard and REMS:DMNMActivation

Band

Messages REMS:Standard and REMS:DMNMDetection

Result

Messages REMS:Standard and REMS:InvalidFrames

Number

Messages REMS:Standard and REMS:LostChannel

ChannelType
Criteria

Messages REMS:Standard and REMS:RSelCharacteristics

CurrentCCH
CurrentThreshold
CurrentPreferentialCriteria
CCH
PreferentialCriteria
Threshold
BN

Messages REMS:Standard and REMS:TCHParameters

DownLinkScrambling
UpLinkScrambling

Nortel
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 39/89
10/10/2019 Nemo Analyze KPI List

RRC signaling

Other

All events
Event IDs of all occured Nemo file format Events
Selected events
Selected event IDs of all occured Nemo file format events
Measurement duration
All BTS reference cells
BTS custom parameter
This query returns custom column from the BTS file for the currently serving cell as specified by the user. Ht
Service off
Recorded when service state or mobility information changes.
Service on
Recorded when service state or mobility information changes.
Service info status
Recorded when service state or mobility information changes.
Date
Geographical bin area
Measurement file info
Measurement time
Modem message
Recorded when modem message is sent to or received from the device. At the moment this message is only logged when
Send Modem Message functionality is used from Nemo Outdoor.
Textual note
Recorded when textual note is recorded by the user.
Voice note
Marker
Recorded when the user adds a marker to the measurement.
Error text
Lock radio off
Lock channel
Lock sector
Lock system
Lock band
Lock cell barring
LTE lock sector
Invex backplane health information
Invex UIC health information
Invex HIM health information

Other:GPS

Velocity
Height
Distance
GPS fix quality
Number of satellites
Latitude and longitude
Latitude and longitude binned (MGRS)
Returns coordinates binned to squares of 1, 10, 100,1000, 10 000, or 100 000 meter side length, binned accorgin to
MGRS grid system.

Packet-switched data

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 40/89


10/10/2019 Nemo Analyze KPI List

Packet data activation attempt


Packet data activation success
Packet data deactivation
Packet data connection dropped
Packet data activation failure
Access point name

Packet-switched data:Attach

Attach session
Information per attach session, time range between Nemo events GAA and GAD/GAF. Can be used as input in KPI
workbench to group other data per attach session
Attach attempt
Attach attempt success
Attach attempt failure
Detach
Attach setup time
Detach distribution
PS status

Packet-switched data:PDP context

PDP context session


Information per PDP context session, time range between Nemo events PAA and PAD/PAF. Can be used as input in KPI
workbench to group other data per PDP context session
PDP context activation attempt
PDP context activation success
PDP context deactivation
PDP context dropped
PDP context activation failure
Access point name
Packet protocol address
Received IP address.
Header compression
Data compression
PDP context activation time
PS status

Packet-switched data:QoS

Minimum accepted QoS


Recorded when new QoS profile is requested or reconfigured. Information is based on configured QoS settings and NAS
signaling.
Requested QoS
Recorded when new QoS profile is requested or reconfigured. Information is based on configured QoS settings and NAS
signaling.
Negotiated QoS
Recorded when the first QoS configuration is received or the current one is reconfigured. This information is based on NAS
signaling.

Services

Problem events
The query returns all problem events in Nemo fileformat. Results can be displayed in grid, colorcoded map, and print value
on the map.

Services:CEM Observer

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 41/89


10/10/2019 Nemo Analyze KPI List

CEM Observer problem report survey


Recorded when a service quality note is recorded by the user. This is an answer to a predefined question presented to the
user.
CEM Observer individual problem reports
Recorded when a service quality note is recorded by the user. This is an answer to a predefined question presented to the
user.

Services:Data transfer

Data transfer threads


Number of concurrent data transfers.
Data transfer attempt number
Transferred bytes uplink total
Transferred bytes downlink total
Download progress (%)
Percentage of bytes transferred over the total file size
Upload progress (%)
Percentage of bytes transferred over the total file size
Application protocol
Shows the currently active application protocol, can be used to be plotted on the map
Data transfer session
Information per file transfer session, time range between Nemo events DREQ and DCOMP. Can be used as input in KPI
workbench to group other data per file transfer
Data server session
Information per data server session, time range between Nemo events DAA and DAD/DAF. Can be used as input in KPI
workbench to group other data per data server session
Data transfer cycle information
List of all data transfer cycles with information on each session trigger point
Data server connection attempt
Data server disconnect
Data server connect
Data server connect failure
Data server connection dropped
Data transfer host address
Connection address. With MMS this is the MMS service center address.
Data transfer host port
IP port.
File transfer request
File transfer complete
DNS host name resolution time
Recorded after DNS query.
See 3GPP TS 102.25 subclause 5.11.
DNS resolved address
Recorded after DNS query.
The DNS query result in the IP format. When multiple IP addresses is received for the domain name the first recorded IP
address is used by the recording tool.
Data transfer IP service access time
Time from DREQ to moment when socket connection has been established and first data packet is send.
Data transfer IP termination time
Time from last data packet to the DCOMP when all connections has been terminated and data transfer is finished.
File transfer dropped
File size
Amount of data to be transferred.
File transfer upload time
Time delay in seconds from file transfer request (DREQ nemo event) to file transfer complete (DCOMP nemo event). At the
precence of "IP access time" and "IP termination time" information elements in the DCOMP event,the transfer time is
according to ETSI TS 102 250-2 specification.
File transfer download time
Time delay in seconds from file transfer request (DREQ nemo event) to file transfer complete (DCOMP nemo event) At the
precence of "IP access time" and "IP termination time" information elements in the DCOMP event,the transfer time is
according to ETSI TS 102 250-2 specification.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 42/89


10/10/2019 Nemo Analyze KPI List

Data server session time


Time delay in seconds from data server connection success (DAC nemo event) to data server disconnect (DAD nemo
event)
Data connection setup time
Time from data server connection attempt to successfull connection (time from DAA to DAC events)
Data time to connect
File transfer success/failure distribution
Data disconnect distribution
PS status
Data transfer status
Data transfer session statistics
Key radio and application metrics per data transfer. All the radio metrics are aggregated for the duration of the data
transfer, between DREQ and DCOMP Nemo events.

Services:Data transfer:Jitter

Packet jitter uplink


Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement.
Packet jitter downlink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement.

Services:Data transfer:PPP

PPP throughput uplink


PPP throughput downlink
Transferred PPP bytes uplink
Cumulative amount of data transferred in uplink direction during the packet session.
Transferred PPP bytes downlink
Cumulative amount of data transferred in downlink direction during the packet session.

Services:Data transfer:Throughput

Application throughput uplink per session


Application throughput uplink
Application throughput uplink average per file transfer
Average application throughput per each uplink file transfer (Average between DREQ and DCOMP Nemo events). At the
precence of "IP access time" and "IP termination time" information elements in the DCOMP event, this average is
according to ETSI TS 102 250-2 specification.
Application throughput downlink per session
Application throughput downlink
Application throughput downlink average per file transfer
Average application throughput per each downlink file transfer (Average between DREQ and DCOMP Nemo events). At the
precence of "IP access time" and "IP termination time" information elements in the DCOMP event, this average is
according to ETSI TS 102 250-2 specification.
Transferred bytes uplink
This is a cumulative byte count from the beginning of the transfer.
Transferred bytes downlink
This is a cumulative byte count from the beginning of the transfer.

Services:Dropbox

Dropbox transaction attempt


Dropbox transaction success
Dropbox transaction failure
Dropbox transaction time
Delay from DAA event (user initiates the transaction) to DCOMP event (transaction is successfully completed)

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 43/89


10/10/2019 Nemo Analyze KPI List

Services:FTP

FTP server connection attempt


FTP server disconnect
FTP server connect
FTP server connect failure
FTP server connection dropped
FTP file transfer attempt
FTP file transfer success
FTP file transfer dropped

Services:Facebook

Facebook access attempt


Checks validity of User Access Token.
Facebook access success
User Access Token is valid.
Facebook access failure
User Access Token is invalid or expired.
Facebook transaction attempt
Facebook transaction success
Facebook transaction failure
Facebook transaction time
Delay from DAA event (user initiates the transaction) to DCOMP event (transaction is successfully completed)
Facebook operation
Facebook timeout
Facebook connection time
Time delay in seconds from Facebook connection attempt (DAA nemo event) to Facebook connection connect (DAC nemo
event)
Facebook transfer time

Services:HTTP

HTTP attempt
HTTP success
HTTP failure
HTTP content
Recorded after data transfer has been completed and WAP/HTML content has been parsed.

Services:HTTP browsing

HTTP browsing attempt


HTTP browsing success
HTTP browsing failure

Services:IMAP

IMAP server connection attempt


IMAP server disconnect
IMAP server connect
IMAP server connect failure
IMAP server connection dropped
IMAP file transfer attempt
IMAP file transfer success
IMAP file transfer dropped

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 44/89


10/10/2019 Nemo Analyze KPI List

Services:Instagram

Instagram transaction attempt


Instagram transaction success
Instagram transaction failure
Instagram transaction time
Delay from DAA event (user initiates the transaction) to DCOMP event (transaction is successfully completed)
Instagram connection time
Time delay in seconds from Instagram connection attempt (DAA nemo event) to Instagram connection connect (DAC
nemo event)
Instagram transfer time
Instagram connection attempt
Instagram connection success
Instagram connection failure

Services:Iperf

File size TCP


Amount of data to be transferred. For time based transfers this information is not available.
File size UDP
Amount of data to be transferred. For time based transfers this information is not available.
Data transfer threads TCP
Number of concurrent data transfers.
Data transfer threads UDP
Number of concurrent data transfers.
Packet error rate downlink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement event for the documented UDP-based protocols.
The ratio of erroneously received packets to total number of received packets.
Packet error rate uplink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement event for the documented UDP-based protocols.
The ratio of erroneously transferred packets to total number of transferred packets.
Transferred packets downlink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement event for the documented UDP-based protocols.
Transferred packets uplink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement event for the documented UDP-based protocols.
Erroneous packets uplink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement event for the documented UDP-based protocols.
Erroneous packets downlink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement event for the documented UDP-based protocols.

Services:Kodiak IPA

Kodiak IPA send attempt


Kodiak IPA receive attempt
Kodiak IPA send success
Kodiak IPA receive success
Kodiak IPA send failure
Kodiak IPA receive failure
Kodiak server registration attempt
Recorded when the user initiates the SIP server (or similar) registration attempt. This measurement event begins the SIP
server registration attempt state.
Kodiak server registration failed
Recorded when registration to the SIP server (or similar) fails. This measurement event terminates the SIP server
registration attempt state.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 45/89


10/10/2019 Nemo Analyze KPI List

Kodiak server registration completed


Recorded when registration to the SIP server (or similar) succeeded and the connection is now established to the SIP
server. This measurement event begins the SIP server registerion state.
Kodiak server deregistered
Recorded when the device is deregistered from the SIP server (or similar). This measurement event terminates the SIP
server registration state.
Kodiak server deregistered abnormally
Recorded when the device is deregistered from the SIP server (or similar). This measurement event terminates the SIP
server registration state.

Services:LTE IMS voice

LTE IMS voice server registration attempt


Recorded when the user initiates the SIP server (or similar) registration attempt. This measurement event begins the SIP
server registration attempt state.
LTE IMS voice server registration failed
Recorded when registration to the SIP server (or similar) fails. This measurement event terminates the SIP server
registration attempt state.
LTE IMS voice server registration completed
Recorded when registration to the SIP server (or similar) succeeded and the connection is now established to the SIP
server. This measurement event begins the SIP server registerion state.
LTE IMS voice server deregistered
Recorded when the device is deregistered from the SIP server (or similar). This measurement event terminates the SIP
server registration state.
LTE IMS voice server deregistered abnormally
Recorded when the device is deregistered from the SIP server (or similar). This measurement event terminates the SIP
server registration state.
RTP jitter DL
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately about 500ms.
RTP packet error rate
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately about 500ms.
RTP interarrival time downlink
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately about 500ms.
During the reporting period the maximum duration between two received voice RTP packets.
RTP bytes downlink
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately about 500ms.
Number of RTP downlink bytes transferred after last update.
RTP bytes uplink
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately about 500ms.
Number of RTP uplink bytes transferred after last update.
RTP packets downlink
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately about 500ms.
Number of RTP downlink packets transferred after last update.
RTP packets uplink
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately about 500ms.
Number of RTP uplink packets transferred after last update.
Talk rate
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately 500ms.
Ratio of talk frames to all frames.
Dequeue underflow
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately 500ms.
The number of the audio frames that have not been available in the de-jitter buffer during the playback.
Consecutive dequeue underflow
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately 500ms.
The longest consecutive missed audio frames during the playback. The audio interruption time is this parameter
mupltiplied by frame length that is currently 20 ms.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 46/89


10/10/2019 Nemo Analyze KPI List

Queue size (talk)


Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately 500ms.
The maximum size of the dejitter buffer during the reporting period.
Queue size (silence)
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately 500ms.
The maximum size of the dejitter buffer during the reporting period.
Frame delay (talk)
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately 500ms.
During the reporting period the maximum duration the RTP packet has been in the dejitter buffer before the usage.
Frame delay (silence)
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately 500ms.
During the reporting period the maximum duration the RTP packet has been in the dejitter buffer before the usage.
Robust header compression DL
Robust header compression UL
LTE IMS voice codec
Recorded when VoIP information changes.
LTE IMS voice SIP handshake time

Services:LinkedIn

LinkedIn transaction attempt


LinkedIn transaction success
LinkedIn transaction failure
LinkedIn transaction time
Delay from DAA event (user initiates the transaction) to DCOMP event (transaction is successfully completed)
LinkedIn connection time
Time delay in seconds from LinkedIn connection attempt (DAA nemo event) to LinkedIn connection connect (DAC nemo
event)
LinkedIn transfer time
LinkedIn connection attempt
LinkedIn connection success
LinkedIn connection failure

Services:MMS

MMS filename
For send MMS message type this is a name of the MMS message file. For retrieved and notification MMS types this a MMS
message reference (that is in a practice a content location in a URI form).
MMS send failure
MMS receive failure
MMS receive success
MMS send success
MMS send attempt
MMS notification received
MMS delivery report received
MMS receive attempt
MMS retrieval time
Definition according to ETSI TS 102 250-2: MMS retrieval time (MT) [s]. The time elapsing between the WAP get request
and the completion of the download of the MMS is be described by this parameter. Computation: MMS retrieval time (MT)
[s] = t2 - t1. t1: time when WAP get request is initiated by the terminal. t2: MMS is completely received, The m-
notifyResp.Ind is sent by the terminal (MT). Only those MMS are counted where the MMS receive attempt is included in
the measurement data.
MMS send time
Time elapsing from pushing the send button after the editing of a MMS-message to the completion of the data transfer is
described by this parameter. Computation: MMS send time (MO) [s] = t2 - t1. t1: send button is pushed (PDP context
activation is initiated by the terminal, followed by connection to WAP gateway. t2: MMS is completely sent to the MMSC,

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 47/89


10/10/2019 Nemo Analyze KPI List
m-send.conf (where Response Status: $80 = M_RS_OK) is received by the terminal (MO). Only those MMS are counted
where the MMS send attempt is included in the measurement data.
MMS notification time
Definition according to ETSI TS 102 250-2: MMS notification time (MO/MT) [s]. The time elapsing from the complete
submission of the Multimedia-Message to the MMSC to the reception of the Notification (MT). Computation: MMS
notification time [s] = t2 ? t1. t1: MMS is completely sent to the MMSC, m-send.conf (where Response Status: $80 =
M_RS_OK) is received by the terminal (MO). t2: Notification is received by the terminal (m-Notif.ind is received by the
terminal). NOTE: make sure that during the measurement, time sync between MO and MT test terminals exists, either by
measuring with single Outdoor and two measurement terminals, or by using GPS time in both measurement units.
MMS end to end delivery time
Definition according to ETSI TS 102 250-2: MMS End-to-end Delivery Time (MO/MT) [s]. The time elapsing from pushing
of the send button to the reception of the MMS by the b-parties mobile. Computation: MMS end-to-end delivery time [s] =
t2 ? t1. t1: send button is pushed in terminal (MO). t2: MMS is received completely by the terminal (MT), The M-resp.ind
is received completely by the MS (MT), and the MS (MT) sends the m-notify-resp.ind. NOTE: make sure that during the
measurement, time sync between MO and MT test terminals exists.

Services:POP3

POP3 server connection attempt


POP3 server disconnect
POP3 server connect
POP3 server connect failure
POP3 server connection dropped
POP3 mail transfer attempt
POP3 mail transfer success
POP3 mail transfer dropped

Services:Packet session

Session state
Summary session layer states
ALMP state
Initialization protocol state
Idle protocol state
Connected protocol state
Route update protocol state
Overhead message protocol state

Services:Ping

Ping round trip time


Ping lost packet
Ping session settings
Ping session-level settings inlcluding host address, packet size, and ping timeout setting. All the following individual ping
attempts belonging to the session are transmitted with settings as indicated here.

Services:PoC

Push-to-talk communication type


Recorded when the push-to-talk state changes.
RTP signaling
Recorded when an RTP signaling message is sent or received.
RTP jitter downlink
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately about 500ms.
PoC session attempt
Recorded when the user initiates the push-to-talk session activation attempt. This measurement event begins the push-to-
talk session activation attempt state.
PoC session connected

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 48/89


10/10/2019 Nemo Analyze KPI List
Recorded when push-to-talk session activation is successful. This measurement event begins the push-to-talk session
state.
PoC session disconnected
Recorded when push-to-talk session is terminated. This measurement event terminates the push-to-talk session state.
PoC session attempt failure
Recorded when push-to-talk session activation fails. This measurement event terminates the push-to-talk session
activation attempt state.
Group attach time
Recorded when push-to-talk session activation is successful. This measurement event begins the push-to-talk session
state.
Time from POC server connection to successful group attach.
POC login time
Recorded when push-to-talk session activation is successful. This measurement event begins the push-to-talk session
state.
Time from POC server login attempt to connection.
Push-to-talk state
Recorded when the push-to-talk state changes.
POC server address
Recorded when push-to-talk session activation is successful. This measurement event begins the push-to-talk session
state.
Push-to-talk user identity
Recorded when the push-to-talk state changes.

Services:SFTP

SFTP server connection attempt


SFTP server disconnect
SFTP server connect
SFTP server connect failure
SFTP server connection dropped
SFTP file transfer attempt
SFTP file transfer success
SFTP file transfer dropped

Services:SMS

SMS send time


Definition according to ETSI TS 102 250-2: Access Delay SMS MO (AD SMS-MO). Time between sending a Short Message
to a Short Message Centre (SMC) and receiving the notification from the Short Message Centre. Computation: Access
Delay SMS MO (AD SMS-MO) = t2 - t1. t1: time when "send" button is pushed in terminal (MO). t2: point of time when
the terminal (MO) receives confirmation from the SMS centre. Only those SMS are counted where the SMS receive attempt
is included in the measurement data.
SMS end to end delivery time
Definition according to ETSI TS 102 250-2: SMS End-to-end Delivery Time (MO/MT) [s]. The time elapsing from pushing of
the send button to the reception of the MMS by the b-parties mobile. NOTE: make sure that during the measurement,
time sync between MO and MT test terminals exists.
SMS send failure
SMS status report received
SMS receive success
SMS send success
SMS send attempt

Services:SMTP

SMTP server connection attempt


SMTP server disconnect
SMTP server connect
SMTP server connect failure
SMTP server connection dropped
SMTP mail transfer attempt
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 49/89
10/10/2019 Nemo Analyze KPI List

SMTP mail transfer success


SMTP mail transfer dropped

Services:Streaming\YouTube

YouTube video state


Recorded when the data stream state changes.
Data transfer stream bandwidth
Recorded when the data stream state changes.
Non-measured stream throughput that have to be used to be able to receive data stream without breaks.
YouTube video resolution
Recorded when the data stream state changes.
The string format is XxY, e.g. 1920x1080.
YouTube video total duration
Recorded when the data stream state changes.
YouTube video current position
Recorded when the data stream state changes.
Data transfer stream content type
Recorded when the data stream state changes.
Data transfer stream video codec
Recorded when the data stream state changes.
Data transfer stream audio codec
Recorded when the data stream state changes.
Data transfer stream file size
Amount of data to be transferred.
Video quality MOS
Video quality BVQA MOS (PEVQ-S)
Audio quality MOS streaming
Average quality value during one audio sample.
Packet error rate downlink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement event for the documented UDP-based protocols.
The ratio of erroneously received packets to total number of received packets.
Transferred packets downlink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement event for the documented UDP-based protocols.
Transferred packets uplink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement event for the documented UDP-based protocols.
Erroneous packets uplink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement event for the documented UDP-based protocols.
Erroneous packets downlink
Recorded semi-periodically when application layer data is transferred to or received from the server. The measurement
event is written simultaneously with the DRATE measurement event for the documented UDP-based protocols.
YouTube video request failed (Video reproduction not started)
Streaming sessions where the video reproductino never started.
YouTube video request failed (Initial buffering not started)
Streaming sessions where the video buffering never started.
YouTube video dropped
Streaming sessions where the video reproduction started but was dropped in the middle.
YouTube video request
YouTube video successfully completed
Streaming sessions where the whole video was successfully reproduced. Sessions with interruptions in the middle of the
stream are included in the metric
YouTube video successfully started (buffering started)
Streaming request that successfully reached the buffering state (Nemo event DSS with buffering status).That is, the
streaming client started to download and buffer the data but streaming reproduction did not yet start.
YouTube video rebuffering
Event for interrupted video stream, where stream is frozen and streaming client starts rebuffering
YouTube video rebuffering rate
Percentage of the total streaming session time where stream is frozen and streaming client starts rebuffering

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 50/89


10/10/2019 Nemo Analyze KPI List

YouTube session time


Time from stream start to stream end (From DREQ event to DCOMP event). Only successful streams are included.
YouTube video initial buffering time
Delay between the point when buffering is indicated by the streaming client, to the point of time when streaming
reproducing is started by the streaming client.
YouTube video access time to buffering
Time from requesting the stream, to the point when buffering is indicated by the streaming client.
YouTube video access time
Time from requesting the stream, to the point when stream reproducion is indicated by the streaming client.
YouTube video player initialization time
Time per streaming session from the first Nemo DREQ event with streaming protocol to the first Nemo DSS event with
status "Stopped". Indicates the time to initialize the video player software.
YouTube video access time
Time per streaming session from the first Nemo DSS event with status "Stopped" to the following Nemo DSS event with
status "Buffering". Indicates the time the elapsed when the video player finds the stream, excluding the intial buffering
time before reprduction starts.
YouTube video download time
Total time per streaming session the video was downloaded in.

Services:Trace route

Traceroute attempt
Recorded when data transfer is requested to or from the server. Begins the data transfer state.
Trace route
One measurement event is recorded for each trace route host.

Services:Twitter

Twitter transaction attempt


Twitter transaction success
Twitter transaction failure
Twitter transaction time
Delay from DAA event (user initiates the transaction) to DCOMP event (transaction is successfully completed)
Twitter connection time
Time delay in seconds from Twitter connection attempt (DAA nemo event) to Twitter connection connect (DAC nemo
event)
Twitter transfer time
Twitter connection attempt
Twitter connection success
Twitter connection failure

Services:USSD

USSD send attempt


Recorded when SMS, MMS, or USSD message sending is attempted or a message is received. This measurement event
begins the SMS, MMS, and USSD transmission state.
USSD receive attempt
USSD send success
USSD receive success
USSD send failure
USSD receive failure

Services:VoIP

Skype server registration attempt


Recorded when the user initiates the SIP server (or similar) registration attempt. This measurement event begins the SIP
server registration attempt state.
Skype server registration failed
Recorded when registration to the SIP server (or similar) fails. This measurement event terminates the SIP server
registration attempt state.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 51/89


10/10/2019 Nemo Analyze KPI List

Skype server registration completed


Recorded when registration to the SIP server (or similar) succeeded and the connection is now established to the SIP
server. This measurement event begins the SIP server registerion state.
Skype server deregistered
Recorded when the device is deregistered from the SIP server (or similar). This measurement event terminates the SIP
server registration state.
Skype server deregistered abnormally
Recorded when the device is deregistered from the SIP server (or similar). This measurement event terminates the SIP
server registration state.
SIP server registration attempt
SIP server registration failed
Recorded when registration to the SIP server (or similar) fails. This measurement event terminates the SIP server
registration attempt state.
SIP server registration completed
Recorded when registration to the SIP server (or similar) succeeded and the connection is now established to the SIP
server. This measurement event begins the SIP server registerion state.
SIP server deregistered
Recorded when the device is deregistered from the SIP server (or similar). This measurement event terminates the SIP
server registration state.
SIP server deregistered abnormally
Recorded when the device is deregistered from the SIP server (or similar). This measurement event terminates the SIP
server registration state.
RTP jitter DL
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately about 500ms.
RTP round-trip-time
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately about 500ms.
RTP packet error rate
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Sampling period is approximately about 500ms.
Ratio of missing RTP packets to all RTP packets that should have been received during the reporting period. Number of lost
and total number of RTP packets are derived from RTP sequence number (packets are either lost or arrive too late).
VoIP codec
Recorded when VoIP information changes.
Currently used VoIP codec that can change during the VoIP call. This is the same as what is configured as audio media
(m=audio) in the SDP part of the SIP message. See more RFC 4566.
Push-to-talk state (QChat)
Recorded when voice call configuration or state changes.
Push-to-talk state (Kodiak)
Recorded when voice call configuration or state changes.
SIP signaling
Recorded when an SIP signaling message is sent or received.
SIP signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message

Services:Voice/video call

Nemo event call attempt


Call attempt (CAA) event with Nemo logfiles. Call initiation event with TEMS logfiles
Call type
Nemo event call connected
Call connected (CAC) event with Nemo logfiles. TEMS events map to this parameter as follows: TEMS event "Call Attempt"
equals to Nemo event "Call connected" with status value "Traffic channel", TEMS event "Call Setup" equals to Nemo event
Call connected with status value "Alerting", TEMS event "Call established" equals to Nemo event "Call connected" with
status value "Called party answered"
Nemo event call disconnected
Corresponds to Call disconnect (CAD) event in Nemo logfiles. With TEMS logfiles, corresponds to "Call End" and "Dropped
Call" events
Nemo event call dropped
Corresponds to Call disconnected (CAD) event in Nemo logfiles with status value inequal to "Normal disconnect". With
TEMS logfiles, corresponds to "Dropped call" event, and "Blocked call" event, if it was written before Alerting was reached.
Nemo event call attempt failure

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 52/89


10/10/2019 Nemo Analyze KPI List
"Call attempt failure" (CAF) event with Nemo logfiles. With TEMS logfiles corresponds to "Blocked call" events appearing
before Alerting.
Call session
Definition according to ETSI TS 102 250-2. Applicaple for UMTS and GSM only. List of all calls with relevant information.
Can be used as input in KPI workbench to group other data pr call
E2E Call session
List of all calls with relevant end to end information from both A and B side of the call. Works only with E2E call data made
with nemo collection tools. Query must be executed across both A and B side logfiles.
Non-LTE Nemo event call attempt
Call attempt, definition according to Nemo events, CAA event with measured system not LTE.
Non-LTE Nemo event call connected
Call connected (CAC) event with Nemo logfiles. TEMS events map to this parameter as follows: TEMS event "Call Attempt"
equals to Nemo event "Call connected" with status value "Traffic channel", TEMS event "Call Setup" equals to Nemo event
Call connected with status value "Alerting", TEMS event "Call established" equals to Nemo event "Call connected" with
status value "Called party answered"
Non-LTE Nemo event call disconnected
Corresponds to Call disconnect (CAD) event in Nemo logfiles, where the corresponding call attempt event (CAA) has
measured system not LTE. With TEMS logfiles, corresponds to "Call End" and "Dropped Call" events
Non-LTE Nemo event call dropped
Corresponds to Call disconnected (CAD) event in Nemo logfiles with status value inequal to "Normal disconnect" and
corresponding call attemt (CAA) event not having measured system LTE. With TEMS logfiles, corresponds to "Dropped
call" event, and "Blocked call" event, if it was written before Alerting was reached.
Non-LTE Nemo event call attempt failure
"Call attempt failure" (CAF) event with Nemo logfiles where the corresponding call attempt event (CAA) has not measured
system LTE. With TEMS logfiles corresponds to "Blocked call" events appearing before Alerting.
Call attempt
Definition according to ETSI TS 102 250-2. Event for voice and video call attempts, excluding attempts where terminal
was out of service, call was failed due to test system. With TEMS logfiles, corresponds to "Call Initiation" event with the
exclusions mentioned above.
Call attempt excluded
Calls excluded according to call testing definition in ETSI TS 102 250-2. That is, call attempts where terminal was out of
service, or call was failed due to test system. With TEMS files excluded "Call Initiation" events.
Call connected
Definition according to ETSI TS 102 250-2. Connected voice and video calls (Nemo event CAC). Trigger point for the event
is user-definable. if user selects Alerting as the trigger point, event is written from any of the three following events,
whichever occurs first: L3 ALERTING message is received, B-party user busy is detected, or if call is connected (ALERTING
message not used). if user selectes Called party answered as trigger point, event is written when called party answers the
call. Calls where disconnect or failure event is not found from the measurement data are filtered out. TEMS events map to
this parameter as follows: TEMS event "Call Setup" equals to Nemo event Call connected with status value "Alerting",
TEMS event "Call established" equals to Nemo event "Call connected" with status value "Called party answered"
Call disconnected
Definition according to ETSI TS 102 250-2. Event for disconnected voice and video calls. Trigger point for the call
connected is user-definable, definition of call connected affects also the disconnect . if user selects Alerting as the trigger
point for call connected, event is written for calls intentionally disconnected by A-party after L3 ALERTING message is
received,. if user selects Called party answered as trigger point for call connected, event is written for calls intentionally
disconnected by A-party after called party has answered the call. With TEMS logfiles, corresponds to "Call End" event.
Call dropped
Definition according to ETSI TS 102 250-2. Applicaple for UMTS and GSM only. Event for dropped voice and video calls.
Trigger point for the event is user-definable. if user selects Alerting as the trigger point for call connected, event is written
for calls dropped after L3 ALERTING message is received. if user selects Called party answered as trigger point for call
connected, event is written for calls dropped after called party has answered the call. Dropped calls due to test system
failure are excluded. With TEMS logfiles, corresponds to "Dropped call" events and "Blocked call" events written before
Alerting was reached.
Call re-establishment
Definition according to ETSI TS 102 250-2. Applicaple for UMTS and GSM only. Event for dropped voice and video calls.
Trigger point for the event is user-definable. if user selects Alerting as the trigger point for call connected, event is written
for calls dropped after L3 ALERTING message is received. if user selects Called party answered as trigger point for call
connected, event is written for calls dropped after called party has answered the call. Dropped calls due to test system
failure are excluded.
Call attempt failure
Definition according to ETSI TS 102 250-2. Applicaple for UMTS and GSM only. Event for failed voice and video call
attempts. Trigger point for the event is user-definable. if user selects Alerting as the trigger point for call connected, event
is written for calls failed before L3 ALERTING message is received. if user selects Called party answered as trigger point for
call connected, event is written for calls failed before called party has answered the call. Failed calls due to test system
failure are excluded. With TEMS logfiles corresponds to "Blocked call" events appearing before Alerting.
Call setup time selected trigger
Time from call attempt (Nemo event CAA) to selected trigger point in seconds. Only mobile originated calls considered.
E2E Call setup time to B-party ALERTING
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 53/89
10/10/2019 Nemo Analyze KPI List
Time from call attempt (Nemo event CAA) in A-side to L3 ALERTING message in B-side in seconds. Works only with E2E
call data made with nemo collection tools. Query must be executed across both A and B side logfiles.
Call setup time to ALERTING
Time from call attempt (Nemo event CAA) to L3 ALERTING message in seconds.
Call setup time to CONNECTED
Time from call attempt (Nemo event CAA) to call connected (Nemo event CAC3) in seconds.
Call setup time to ALERTING WCDMA
Time from call attempt (Nemo event CAA) to L3 ALERTING message in seconds. Only mobile originated calls started in
WCDMA considered.
Call setup time to ALERTING GSM
Time from call attempt (Nemo event CAA) to L3 ALERTING message in seconds. Only mobile originated calls started in
GSM considered.
Call setup time to PROGRESS
Time from call attempt (Nemo event CAA) to L3 PROGRESS message in seconds. Only mobile originated calls considered.
MO Call setup time from RRC_CONNECTION_REQUEST to ALERTING
Call setup time from RRC_CONNECTION_REQUEST message to ALERTING message in seconds. Only mobile originated
calls considered.
Call setup time to traffic ch accessed
Time from call attempt (Nemo event CAA) to point where traffic channel accessed (Nemo event CAC1). Only mobile
originated calls considered.
MO Call setup time to called party answered
Time from call attempt (Nemo event CAA) to point of time when call is answered by B-party (Nemo event CAC3 in
seconds. Only mobile originated calls considered.
Voice quality server call end to end time
Time from call attempt (Nemo event CAA) to point of time when call is alerting (answered in CDMA) at B-party in seconds
CS status
Call attempt failure signaling matrix
List of failed call attempts and indication of the occurance of each signaling message belonging to the procedure
Voice call session statistics
Key metrics per voice call. All the radio metrics are aggregated for the duration of the call, between CAA and CAD Nemo
events.
Voice codec distribution in 2G/3G

Services:Voice/video call:CSFB

CSFB call attempt


Definition according to ETSI TS 102 250-2. Event for voice and video call attempts, excluding attempts where terminal
was out of service, call was failed due to test system. With TEMS logfiles, corresponds to "Call Initiation" event with the
exclusions mentioned above.
CSFB call connected
Definition according to ETSI TS 102 250-2. Connected voice and video calls (Nemo event CAC). Trigger point for the event
is user-definable. if user selects Alerting as the trigger point, event is written from any of the three following events,
whichever occurs first: L3 ALERTING message is received, B-party user busy is detected, or if call is connected (ALERTING
message not used). if user selectes Called party answered as trigger point, event is written when called party answers the
call. Calls where disconnect or failure event is not found from the measurement data are filtered out. TEMS events map to
this parameter as follows: TEMS event "Call Setup" equals to Nemo event Call connected with status value "Alerting",
TEMS event "Call established" equals to Nemo event "Call connected" with status value "Called party answered"
CSFB call disconnected
Definition according to ETSI TS 102 250-2. Event for disconnected voice and video calls. Trigger point for the call
connected is user-definable, definition of call connected affects also the disconnect . if user selects Alerting as the trigger
point for call connected, event is written for calls intentionally disconnected by A-party after L3 ALERTING message is
received,. if user selects Called party answered as trigger point for call connected, event is written for calls intentionally
disconnected by A-party after called party has answered the call. With TEMS logfiles, corresponds to "Call End" event.
CSFB call dropped
Definition according to ETSI TS 102 250-2. Applicaple for UMTS and GSM only. Event for dropped voice and video calls.
Trigger point for the event is user-definable. if user selects Alerting as the trigger point for call connected, event is written
for calls dropped after L3 ALERTING message is received. if user selects Called party answered as trigger point for call
connected, event is written for calls dropped after called party has answered the call. Dropped calls due to test system
failure are excluded. With TEMS logfiles, corresponds to "Dropped call" events and "Blocked call" events written before
Alerting was reached.
CSFB call attempt failure
Definition according to ETSI TS 102 250-2. Applicaple for UMTS and GSM only. Event for failed voice and video call
attempts. Trigger point for the event is user-definable. if user selects Alerting as the trigger point for call connected, event
is written for calls failed before L3 ALERTING message is received. if user selects Called party answered as trigger point for
call connected, event is written for calls failed before called party has answered the call. Failed calls due to test system
failure are excluded. With TEMS logfiles corresponds to "Blocked call" events appearing before Alerting.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 54/89


10/10/2019 Nemo Analyze KPI List

CSFB Nemo event call attempt


CSFB call attempt, definition according to Nemo events, CAA event with measured system LTE and call type voice.
CSFB Nemo event call connected
Call connected (CAC) event with Nemo logfiles. TEMS events map to this parameter as follows: TEMS event "Call Attempt"
equals to Nemo event "Call connected" with status value "Traffic channel", TEMS event "Call Setup" equals to Nemo event
Call connected with status value "Alerting", TEMS event "Call established" equals to Nemo event "Call connected" with
status value "Called party answered"
CSFB Nemo event call disconnected
Corresponds to Call disconnect (CAD) event in Nemo logfiles, where the corresponding call attempt event (CAA) has LTE
measured system and call type is voice. With TEMS logfiles, corresponds to "Call End" and "Dropped Call" events
CSFB Nemo event call dropped
Corresponds to Call disconnected (CAD) event in Nemo logfiles with status value inequal to "Normal disconnect" and
corresponding call attemt (CAA) event having LTE measured system and call type voice. With TEMS logfiles, corresponds
to "Dropped call" event, and "Blocked call" event, if it was written before Alerting was reached.
CSFB Nemo event call attempt failure
"Call attempt failure" (CAF) event with Nemo logfiles where the corresponding call attempt event (CAA) has LTE measured
system and call type voice. With TEMS logfiles corresponds to "Blocked call" events appearing before Alerting.
Call setup time to ALERTING CSFB
LTE CS Fallback call setup time. Time from call attempt (Nemo event CAA) to L3 ALERTING message in seconds. Only
mobile originated calls considered.
Call setup time to CONNECTED CSFB
LTE CS Fallback call setup time. Time from call attempt (Nemo event CAA) to L3 CONNECTED message in seconds.

Services:Voice/video call:LTE IMS voice

Call setup time to ALERTING LTE IMS voice


Call setup time for LTE IMS voice. Time from call attempt (Nemo event CAA, SIP:Invite) to alerting tone (SIP:Ringing,
Nemo event: CAC2) in seconds. Only mobile originated calls considered.
Call setup time to ALERTING LTE IMS voice (RRC connected)
Call setup time for LTE IMS voice. Time from call attempt (Nemo event CAA, SIP:Invite) to alerting tone (SIP:Ringing,
Nemo event: CAC2) in seconds. Only mobile originated calls considered where call was initiated in RRC state connected.
Call setup time to ALERTING LTE IMS voice (RRC idle)
Call setup time for LTE IMS voice. Time from call attempt (Nemo event CAA, SIP:Invite) to alerting tone (SIP:Ringing,
Nemo event: CAC2) in seconds. Only mobile originated calls considered where call was initiated in RRC state idle.
LTE IMS voice call attempt
Definition according to ETSI TS 102 250-2. Event for voice and video call attempts, excluding attempts where terminal
was out of service, call was failed due to test system. With TEMS logfiles, corresponds to "Call Initiation" event with the
exclusions mentioned above.
LTE IMS voice call connected
Definition according to ETSI TS 102 250-2. Connected voice and video calls (Nemo event CAC). Trigger point for the event
is user-definable. if user selects Alerting as the trigger point, event is written from any of the three following events,
whichever occurs first: L3 ALERTING message is received, B-party user busy is detected, or if call is connected (ALERTING
message not used). if user selectes Called party answered as trigger point, event is written when called party answers the
call. Calls where disconnect or failure event is not found from the measurement data are filtered out. TEMS events map to
this parameter as follows: TEMS event "Call Setup" equals to Nemo event Call connected with status value "Alerting",
TEMS event "Call established" equals to Nemo event "Call connected" with status value "Called party answered"
LTE IMS voice call disconnected
Definition according to ETSI TS 102 250-2. Event for disconnected voice and video calls. Trigger point for the call
connected is user-definable, definition of call connected affects also the disconnect . if user selects Alerting as the trigger
point for call connected, event is written for calls intentionally disconnected by A-party after L3 ALERTING message is
received,. if user selects Called party answered as trigger point for call connected, event is written for calls intentionally
disconnected by A-party after called party has answered the call. With TEMS logfiles, corresponds to "Call End" event.
LTE IMS voice call dropped
Definition according to ETSI TS 102 250-2. Applicaple for UMTS and GSM only. Event for dropped voice and video calls.
Trigger point for the event is user-definable. if user selects Alerting as the trigger point for call connected, event is written
for calls dropped after L3 ALERTING message is received. if user selects Called party answered as trigger point for call
connected, event is written for calls dropped after called party has answered the call. Dropped calls due to test system
failure are excluded. With TEMS logfiles, corresponds to "Dropped call" events and "Blocked call" events written before
Alerting was reached.
LTE IMS voice call attempt failure
Definition according to ETSI TS 102 250-2. Applicaple for UMTS and GSM only. Event for failed voice and video call
attempts. Trigger point for the event is user-definable. if user selects Alerting as the trigger point for call connected, event
is written for calls failed before L3 ALERTING message is received. if user selects Called party answered as trigger point for
call connected, event is written for calls failed before called party has answered the call. Failed calls due to test system
failure are excluded. With TEMS logfiles corresponds to "Blocked call" events appearing before Alerting.

Services:Voice/video call:Video
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 55/89
10/10/2019 Nemo Analyze KPI List

Video protocol
Video call quality index
Video FER
Number of erroneous frames received.
Video frame rate uplink
Video frame rate downlink
Video rate downlink
Video rate uplink

Services:Voice/video call:VoLTE:AMR

AMR mode downlink LTE


AMR mode uplink LTE

Services:Voice/video call:Voice:AMR

AMR initial codec mode


Recorded when AMR information is modified based on the trace messages of the device.
AMR initial codec mode indicator
Recorded when AMR information is modified based on the trace messages of the device.
AMR first hysteresis
AMR first threshold
Recorded when AMR information is modified based on the trace messages of the device.
AMR second threshold
AMR second hysteresis
Recorded when AMR information is modified based on the trace messages of the device.
AMR third threshold
AMR third hysteresis
Recorded when AMR information is modified based on the trace messages of the device.
AMR number of active codecs
Recorded when AMR information is modified based on the trace messages of the device.
AMR active codecs
Recorded when AMR information is modified based on the trace messages of the device.
AMR mode uplink GSM
Recorded when AMR information is modified based on the trace messages of the device.
AMR mode uplink UMTS
Recorded when AMR information is modified based on the trace messages of the device.
AMR mode downlink GSM
Recorded when AMR information is modified based on the trace messages of the device.
AMR mode downlink UMTS
Recorded when AMR information is modified based on the trace messages of the device.
AMR last mode command
Recorded when AMR information is modified based on the trace messages of the device.
Last mode command within mode set.
AMR last mode request
Recorded when AMR information is modified based on the trace messages of the device.
Last mode request within mode set.
AMR channel type
Recorded when AMR information is modified based on the trace messages of the device.
AMR link quality estimate
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
AMR UL codec mode distribution
AMR DL codec mode distribution

Services:Voice/video call:Voice:Voice quality

Audio quality echo sample type

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 56/89


10/10/2019 Nemo Analyze KPI List
Recorded after voice quality sample is transmitted and the echo of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality echo annoyance
Recorded after voice quality sample is transmitted and the echo of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality echo level
Recorded after voice quality sample is transmitted and the echo of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
This is same as echo return loss parameter.
Audio quality echo delay
Recorded after voice quality sample is transmitted and the echo of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality echo occurrence
Recorded after voice quality sample is transmitted and the echo of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Defines the ratio of echo in the reported echo sample.
Audio quality diff to tolerance
Recorded after voice quality sample is transmitted and the echo of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Defines the measured echo level difference to the tolerance curve defined by ITU-T record G.131.
Audio reception RX state
Recorded during audio reception.
Audio quality MOS (PESQ-LQ) DL
PESQ audio quality score mapped to PESQ-LQ Mean Opinion Score (MOS) scale. PESQ-LQ is a non-standard mapping.
Audio quality MOS (PESQ-LQ) UL
PESQ audio quality score mapped to PESQ-LQ Mean Opinion Score (MOS) scale. PESQ-LQ is a non-standard mapping.
Audio quality sample filename UL
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality reference sample filename UL
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio sample duration UL
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality test type
Recorded when the measurement tool achieves synchronization with the transferred voice quality sample. This
measurement event is recorded only during voice quality measurements.
Audio quality synchronization status
Recorded when the measurement tool achieves synchronization with the transferred voice quality sample. This
measurement event is recorded only during voice quality measurements.
Audio quality MOS DL with channel type/speech codec
MOS DL samples with the GSM and UMTS speech codec at the beginning of the MOS score assessing period
Audio quality MOS DL (PSM mobile) with channel type/speech codec
MOS DL samples with the GSM and UMTS speech codec at the beginning of the MOS score assessing period
Audio quality MOS (PSM mobile) DL
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality MOS DL
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Average quality value during one audio sample.
Audio quality speech activity
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality delay mean
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality delay min
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
See description for audio quality delay mean -parameter.
Audio quality delay max
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
See description for audio quality delay mean -parameter.
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 57/89
10/10/2019 Nemo Analyze KPI List

Audio quality delay std


Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
See description for audio quality delay mean -parameter.
Audio quality SNR
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality SQI
Speech quality index. Only available with TEMS measurements.
Audio quality SQI MOS
Speech quality index expressed on the MOS scale. Only available with TEMS measurements.
Audio quality sample filename DL
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Name of the audio sample file stored on disk during measurement. Empty if the file is not saved.
Audio quality reference sample filename DL
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality sample duration DL
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality insertion gain
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Gain calculated for active signal in active periods. dB difference between active signal of reference and degraded signals
(calculated as of degraded minus of reference signal). Typical value is 0 dB for digital signal.
Audio quality noise gain
Recorded after voice quality sample is received and the MOS score of the sample is calculated. This measurement event is
recorded only during voice quality measurements.
Audio quality signal status
Recorded when the measurement tool achieves synchronization with the transferred voice quality sample. This
measurement event is recorded only during voice quality measurements.
This parameter has never been logged and it is deprecated.
Avg. audio quality MOS DL per 1st active scr
Avg. audio quality MOS DL per BCCH
Audio quality MOS UL with channel type/speech codec
Audio quality MOS values from the server logfile, and the coordinates from corresponding mobile logfile. The query has to
be executed for the mobile logfile, and the server side logfilehas to be in the database. Server side UL MOS values are
automatically correlated with the mobile file. When run with filters, the filtering is based on attributes, such as system,
scrambling code, etc, from the corresponding mobile logfile. Note that there needs to be time sync between the server and
mobile logfiles. Also, the phone number of the server line has to be configured to the server so that it appears in the
server logfile header.
Audio quality MOS UL
Audio quality MOS values from the server logfile, and the coordinates from corresponding mobile logfile. The query has to
be executed for the mobile logfile, and the server side logfilehas to be in the database. Server side UL MOS values are
automatically correlated with the mobile file. When run with filters, the filtering is based on attributes, such as system,
scrambling code, etc, from the corresponding mobile logfile. The parameter needs to be executed over a folder containing
both server file, and corresponding mobile logfile. Note that there needs to be time sync between the server and mobile
logfiles. Also, the phone number of the server line has to be configured to the server so that it appears in the server logfile
header.
Audio quality mean Average quality value during one audio sample.
Audio quality MOS UL with time offset
Audio quality MOS values from the server logfile, and the coordinates from corresponding mobile logfile. The query has to
be executed for the mobile logfile, and the server side logfilehas to be in the database. Server side UL MOS values are
automatically correlated with the mobile file. When run with filters, the filtering is based on attributes, such as system,
scrambling code, etc, from the corresponding mobile logfile. The parameter needs to be executed over a folder containing
both server file, and corresponding mobile logfile. Note that there needs to be time sync between the server and mobile
logfiles. Also, the phone number of the server line has to be configured to the server so that it appears in the server logfile
header. Time offset of the UL MOS samples is adjustable in case the server and mobile times were not aligned at the time
of the test.
Audio quality type DL
Audio quality type UL

Services:WAP

WAP attempt

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 58/89


10/10/2019 Nemo Analyze KPI List

WAP success
WAP failure
WAP content
Recorded after data transfer has been completed and WAP/HTML content has been parsed.

Spectrum scanner

Resolution bandwidth
To be able to scan large bandwidth spectrums, the total sweep bandwidth must be divided into smaller parts. The
resolution bandwidth defines the size of the smaller parts, each of which is scanned separately.
Sweep bandwidth
The total scanned bandwidth that is divided into smaller parts before the scanning.
Sweep minimum RX level
Minimum RX levels measured over bandwidth of 'resolution bandwidth'.
Sweep maximum RX level
Maximum RX levels measured over bandwidth of 'resolution bandwidth'.
Sweep center frequency
Sweep average RX level selected frequency
Sweep average RX level
The linear average of RX levels measured over bandwidth of 'resolution bandwidth'.
Spectrum scan
Scanning configuration
Defines scanning settings.

TD-SCDMA

TD-SCDMA uplink repetition length


TD-SCDMA uplink repetition period
Valid values are 1, 2, 4, 8, 16, 32, and 64
TD-SCDMA downlink repetition length
TD-SCDMA downlink repetition period
Valid values are 1, 2, 4, 8, 16, 32, and 64
TD-SCDMA physical channel type
Physical channel direction
Timeslot
TD-SCDMA spreading factor
TD-SCDMA channelisation code
Midamble configuration
Valid values are 2, 4, 6, 8, 10, 12, 14, and 16.
Midamble shift
PCCPCH C/I
Number of "UL power up" commands
Number of received "UL power up" commands (BTS to mobile).
Number of "UL power down" commands
Number of received "UL power down" commands (BTS to mobile).
Percentage of "UL power up" commands
In percentage the number of "UL power up" commands from all commands. If this value is 100%, all commands request
to increase power.
Number of "DL power up" commands
Number of sent "DL power up" commands (mobile to BTS).
Number of "DL power down" commands
Number of sent "DL power down" commands (mobile to BTS).
Percentage of "DL power up" commands
In percentage the number of "DL power up" commands from all commands. If this value is 100%, all commands request
to increase power.
Neighborlist
List of neighbors seen by the terminal
Radio bearer info

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 59/89


10/10/2019 Nemo Analyze KPI List
Recorded when UMTS radio bearer allocation is modified. Currently based on information received from the trace interface
of the device.
Transport channel info
Recorded when UMTS transport channel allocation is modified. Currently based on information received from the trace
interface of the device.
BLER selected transport channel
BLER transport channels
Frame error rate
Mobile country code
Recorded when service state or mobility information changes.
See ITU-T recommendation E.212.
Operator
Mobile network code
Recorded when service state or mobility information changes.
TMSI
Recorded when service state or mobility information changes.
Temporary mobile subscriber identity. See 3GPP TS 124.008 subclause 10.5.1.4 and 3GPP TS 123.003 subclause 2.4.
P-TMSI
Recorded when service state or mobility information changes.
Packet temporary mobile subscriber identity. See 3GPP TS 124.008 subclause 10.5.1.4 and 3GPP TS 123.003 subclause
2.7.
Location area update failure
Recorded based on MM layer3 signaling when location area update has failed. This measurement event terminates the
location area update state.
Location area update attempt
Recorded when the mobile starts location area update using MM layer3 signaling message. This measurement event
begins the location area update state.
Location area update success
Recorded based on MM layer3 signaling when location area update has been successful. This measurement event
terminates the location area update state.
Location area update time
Cell identification
Cell identity of the current cell. For GSM this is 16 bit value, for UMTS this is 28 bit value (RNC ID + 16 bit cell ID), and for
LTE this is 28 bit value (eNB ID + 8 bit cell ID).
Location area code
RRC state
RRC state during data transfer
RRC state filtered from the tim instants where data transfer is active (between DREQ and DCOMP nemo events
DRX cycle length
Defines how often paging indications are monitored.
L3 signaling
Recorded when a Layer 3 or an NAS signaling message is sent or received.
RRC and L3 signaling
L3 message search
Searches for user-defined messages, with user-defined string in the message name
Packet technology
Packet technology during data transfer
Packet technology between nemo events DAA to DAD or DAF
Packet state
Routing area code
Network mode of operation
BLER DL
RLC throughput uplink
The value of this parameter is calculated based on the SDUs that are successfully transferred through the RLC layer.
Missing and erroneous RLC blocks are excluded from the throughput calculation.
RLC throughput downlink
The value of this parameter is calculated based on the SDUs that are successfully transferred through the RLC layer.
Missing and erroneous RLC blocks are excluded from the throughput calculation.
TX power control step size
Signal-to-interference ratio target
Current target SIR at update time.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 60/89


10/10/2019 Nemo Analyze KPI List

Signal-to-interference ratio
See 3GPP TS 125.215 subclause 5.2.2.
TX power
Channel number
TD-SCDMA pilot pollution
Number of cells that are within user defined window from the best cell in terms of RSCP, when best RSCP is above user
defined threshold.
Treselection
The time which the new cell has had to be ranked better than the old cell before cell reselection is possible. See 3GPP TS
25.304 subclause 5.2.6.1.4.
Measurement event
Recorded when a UMTS measurement event is transmitted to the network based on signaling messages.
Cell reselection
Handover events
Handover attempt
Handover success
Handover failure
Timing advance
Timeslot ISCP
Timeslot RSCP
Cell parameters ID
Max TX power
DPCH channel number
RSCP serving cell
RSCP neighbour cells
Pathloss serving cell
Pathloss neighbour cells
Carrier RSSI
RLC throughput uplink per radio bearer
Uplink RLC throughput for specified radio bearer.
RLC throughput downlink per radio bearer
Downlink RLC throughput for specified radio bearer.
RLC retransmission rate uplink per radio bearer

TD-SCDMA Scanner

Carrier RSSI (frequency scanning mode) selected channel


Ec/I0 PCCPCH selected channel
The received energy per chip divided by the relevant measured power density (noise and signal) in the wide band.
Ec/I0 SYNC DL selected channel
The received energy per chip divided by the relevant measured power density (noise and signal) in the wide band.
Time offset PCCPCH selected channel
Position of a selected pilot.
Time offset SYNC DL selected channel
Position of a selected pilot.
SIR PCCPCH selected channel
SIR SYNC DL selected channel
RSCP PCCPCH selected channel
RSCP SYNC DL selected channel
Carrier RSSI (pilot scanning mode) PCCPCH selected channel
Carrier RSSI (pilot scanning mode) SYNC DL selected channel

TD-SCDMA:Cell reselection criteria

Srxlev active set


Srxlev monitored set

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 61/89


10/10/2019 Nemo Analyze KPI List

Srxlev detected set


Hrxlev active set
Hrxlev monitored set
Hrxlev detected set
Rrxlev active set
Rrxlev monitored set
Rrxlev detected set

TD-SCDMA:HSDPA

MAC number of ACK/NACK messages sent


Recorded when parameter sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session.
MAC-hs block error rate downlink
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session.
MAC-hs residual block error rate
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session.
HSDPA MAC-hs block rate
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
HSDPA MAC-hs throughput
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
HSDPA MAC-hs 1st retransmission rate
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
Number of blocks retransmitted after the first transmission attempt.
HSDPA MAC-hs 2nd retransmission rate
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
Number of blocks retransmitted after the second transmission attempt.
HSDPA MAC-hs 3rd+ retransmission rate
Recorded when measurement sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session. Separate measurement event is logged for each serving cell with LTE.
Number of blocks retransmitted after the third or later transmission attempt.
HSDPA UE category
Defines the current maximum possible HSDPA UE category. This is limited by cell configuration and UE capabilities.
HSDPA physical layer requested throughput
HSDPA CQI distribution
CQI (mode)
The most common CQI value over the reporting period
HS-SCCH usage
Recorded every 200 milliseconds to indicate HS-SCCH channel usage based on the trace messages of the mobile. This
measurement event is recorded simultaneously with the PLAID measurement event.
HARQ Throughput
Recorded every 200 milliseconds to indicate HSDPA HARQ throughput based on the trace messages of the mobile. This
measurement event is recorded simultaneously with the PLAID measurement event.
HARQ BLER
Recorded every 200 milliseconds to indicate HSDPA HARQ throughput based on the trace messages of the mobile. This
measurement event is recorded simultaneously with the PLAID measurement event.
HARQ number of packets transferred
Recorded every 200 milliseconds to indicate HSDPA HARQ throughput based on the trace messages of the mobile. This
measurement event is recorded simultaneously with the PLAID measurement event.
HSDPA HS-SCCH C/I
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 62/89
10/10/2019 Nemo Analyze KPI List
Recorded when the information is received from the device.
HSDPA HS-SCCH ISCP
Recorded when the information is received from the device.
HSDPA HS-SCCH RSCP
Recorded when the information is received from the device.
HSDPA HS-SCCH SIR
Recorded when the information is received from the device.
HSDPA HS-PDSCH SIR
Recorded when the information is received from the device.
HSDPA HS-PDSCH ISCP
Recorded when the information is received from the device.
HSDPA HS-PDSCH RSCP
Recorded when the information is received from the device.
HSDPA HS-PDSCH C/I

TD-SCDMA:HSDPA:Link adaptation

HSDPA HS-PDSCH throughput


HSDPA retransmission rate percentage
HSDPA number of codes percentage
HSDPA modulation percentage
HSDPA transport block size percentage
HSDPA transport block size statistics
HSDPA transport block size (mode)
The most common value of the transport block size over the reporting period
HSDPA number of codes (mode)
The most common value of number of multicodes over the reporting period
HSDPA modulation (mode)
The most common value of modulation over the reporting period
HSDPA link adaptation parameter distribution

TD-SCDMA:RACH

RACH message length


Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH SYNC UL initial TX power
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Initial transmission power.
RACH SYNC UL power
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Power of last SYNC UL.
RACH TX power
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Total transmission power used in RACH message part (control + data).
RACH SYNC UL step
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH SYNC UL count
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Transmitted preamble transmission count.
RACH SYNC UL maximum count
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Valid values are 1, 2, 4, and 8. This is the same as _Max SYNC_UL Transmissions_ parameter signaled by network in RRC
layer and it defines the maximum number of preamble attempts.
RACH PCCPCH pathloss

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 63/89


10/10/2019 Nemo Analyze KPI List
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH FPACH status
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH desired UpPCH RX power
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH desired UpRACH RX power
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH max preamble cycles
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Maximum number of preamble cycles.

TD-SCDMA:RRC

RRC and L3 signaling


RRC message search
Searches for user-defined messages, with user-defined string in the message name
RRC signaling
RRC connection attempt
Recorded based on RRC signaling when RRC connection is attempted. This measurement event begins the RRC connection
attempt state.
RRC connection connected
Recorded based on RRC signaling when RRC connection is established. This measurement event begins the RRC
connection state.
RRC connection disconnected
RRC connection attempt failure
Recorded based on RRC signaling when RRC connection attempt fails. This measurement event terminates the RRC
connection attempt state.

TDMA

Serving system and band


Recorded when channel configuration information changes.
Serving system
Recorded when channel configuration information changes.
Serving band
Recorded when channel configuration information changes.
L3 signaling
Recorded when a Layer 3 or an NAS signaling message is sent or received.
L3 message search
Searches for user-defined messages, with user-defined string in the message name
Channel number
Recorded when channel configuration information changes.
Timeslot number
In case of HSCSD data test call, used timeslots are listed in a DCHI event.
Rx level
Neighbor RX levels
BER class
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
BER class value reported by mobile.
Timing alignment
Reported timing alignment.
MS power level
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Channel type
NW type
PSID2
PSID (private system identification) value 2.
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 64/89
10/10/2019 Nemo Analyze KPI List

PSID4
PSID (private system identification) value 4.
REG PERIOD
If not available, set to -1.
RNUM
If LAREG parameter has the value of 1, RNUM parameter will have a value.
LAREG
PSID3
PSID (private system identification) value 3.
Digital color code
L3 signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message
Downlink Band
Handover events
Handover attempt
Handover success
Handover failure

TDMA Scanner

Rx level
RX level selected channel
RX level Nth best
RX level top N

TETRA

Call type
Serving system
Recorded when channel configuration information changes.
Serving band
Recorded when channel configuration information changes.
Band
Channel number
Subchannel
Extended subchannel
Slot number
BER
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Bit error rate that is calculated with training sequence algorithm.
Message error rate
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
TX power
MS transit power.
TX power change
TX power control algorithm
RSSI best
RSSI selected channel
RSSI serving cell
RSSI neighbor cells
RSSI Nth best neighbor
Push-to-talk communication type
Recorded when the push-to-talk state changes.
Push-to-talk state
L3 signaling
Recorded when a Layer 3 or an NAS signaling message is sent or received.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 65/89


10/10/2019 Nemo Analyze KPI List

L3 message search
Searches for user-defined messages, with user-defined string in the message name
LLC signaling
Recorded when an LLC signaling message is sent or received.
L3 signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message
CS status

TETRA:Encryption

Encryption
Air interface encryption
Recorded when ciphering information is modified.
Ciphering KSG
Recorded when ciphering information is modified.
Ciphering SCK
Recorded when ciphering information is modified.

TETRA:Mobility management

LAC
Location area update failure
Recorded based on MM layer3 signaling when location area update has failed. This measurement event terminates the
location area update state.
Location area update attempt
Recorded when the mobile starts location area update using MM layer3 signaling message. This measurement event
begins the location area update state.
Location area update success
Recorded based on MM layer3 signaling when location area update has been successful. This measurement event
terminates the location area update state.
Location area update time
Cell reselection
Handover events
Handover attempt
Handover success
Handover failure

Tetrapol:Custom attributes:Mode Test

BestServerRxLev
BestServerChannel
BestServerFrequency
2ndBestServerRxLev
2ndBestServerChannel
2ndBestServerFrequency
ExtendBestServerRxLev
ExtendBestServerChannel
ExtendBestServerFrequency

Tetrapol:Custom attributes:Specific REMS

Speech Rx Duration
Speech Tx Duration
PTT Duration
ST Transmitted Power

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 66/89


10/10/2019 Nemo Analyze KPI List

Tetrapol:Custom attributes:Standard and REMS

CCH Selection
RB Selection
Nominal Frame Error Rate
MeanRxLevCCHx
MeanRxLevCCHx with BTS ref. information
RxLev_CCH39k
CurrentMeanRxLev
EstimatedTxPower
NborMeanRxLev_X
BestNborCellRxLev
BestNborCellCCH
2ndBestNborCellRxLev
2ndBestNborCellCCH
FrameErrorRate Level
ChannelMonitoring
TrafficChannel

Tetrapol:Dedicated Radio Link

InvalidFrames_Number

Tetrapol:Event Data:Common and Standard, REMS and Test

Terminal_Mode
TemperatureAlarm
InvalidMessage
Text_Message

Tetrapol:Event Data:Specific REMS

CommSuspended
CommReestablishment
CommServiceDenied
CommReady
STAlarm
CommEnter
CommLeave
PTTRequest
PTTRelease

Tetrapol:Event Data:Standard and REMS

CSelStart
CSelDistribTKGList
CSelDistribEmergencyList
CSelDistribMOCHList
DMNMActivation
DMNMDetection
LostChannel
RSelGMSKDetection_NOK
RSelBestNeighbourCell

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 67/89


10/10/2019 Nemo Analyze KPI List

CSelRegistration_OK
CSelRegistration_NOK
Fast_Registration
Tunnel_Out
Tunnel_In
EventNewTRState
Cell_Memorization

Tetrapol:Independent:GPS Data

Distance
Latitude and longitude

Tetrapol:Messages REMS:Messages common and Standard, REMS and Test:GPSInfo

NbSat
Speed

Tetrapol:Messages REMS:Messages common and Standard, REMS and Test:Info

Source
Level
Code
Label

Tetrapol:Messages REMS:Messages common and Standard, REMS and Test:STInfo

HardwareType
SecondaryHardwareType
LinkType
ProjectType
SoftwareVersion
MaxNominalTxPower

Tetrapol:Messages REMS:Messages common and Standard, REMS and Test:STSetup

SerialPort
UseInterfaceBox
ProjectName
ChannelSpacing
DuplexSpacing
InitChannel
XVCO
ChannelOffset
SerialBaudRate

Tetrapol:Messages REMS:Messages common and Standard, REMS and Test:STState

Power
STMode

Tetrapol:Messages REMS:Messages common and Standard, REMS and


Test:TemperatureAlarm

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 68/89


10/10/2019 Nemo Analyze KPI List

State

Tetrapol:Messages REMS:Mode Test:AvRLinkQual

AvRLinkQual BERCl1
AvRLinkQual BERCl2
AvRLinkQual BER
AvRLinkQual FER
TotalNbFrames

Tetrapol:Messages REMS:Mode Test:RLinkQual

RLinkQual BERCl1
RLinkQual BERCl2
RLinkQual BER
RLinkQual FER
TotalNbFrames

Tetrapol:Messages REMS:Mode Test:RxLev

Channel
RxLev

Tetrapol:Messages REMS:REMS Specific:CommInit

InterfaceVersion
STAddress
SerialNumber
SoftwareService
NominalOG
ResetOrigin
Trap1
Trap2
Alarm
DebugFlag
DebugClass
ForwardState
HostAddress
STRange
STType
LoudSpeakerState
SpeechVolume
ToneVolume
PTTPriority

Tetrapol:Messages REMS:REMS Specific:CommLeave

CallType

Tetrapol:Messages REMS:REMS Specific:CommReady

CipheringKeyIndex

Tetrapol:Messages REMS:REMS Specific:CommSuspended

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 69/89


10/10/2019 Nemo Analyze KPI List

CommType

Tetrapol:Messages REMS:REMS Specific:ConfigTypeCallBehaviour

AcceptIncomingCall

Tetrapol:Messages REMS:REMS Specific:ConfigTypeCommBehaviour

AutoEntryInFallBackMOCH
AutoEntryInBroadcastCall
LocalManualKey
PTTInBroadcastCall
OutgoingExternGroupCall
AutoIncomingCallAnswer
PriorityScanMode
DMNM

Tetrapol:Messages REMS:REMS Specific:ConfigTypeDataBehaviour

DataImplicitAddressing

Tetrapol:Messages REMS:REMS Specific:ConfigTypeMonitoring

MOCH
Emergency
COV
EmergencyNotification
CrisisNotification
BroadcastNotification
CallCompositionNotification
OverloadNotification
CellActivationInd
StatusInd

Tetrapol:Messages REMS:REMS Specific:CrisisList

CrisisId

Tetrapol:Messages REMS:REMS Specific:EmergencyList

EmergencyId

Tetrapol:Messages REMS:REMS Specific:EncryptionState

CipheringType
OverCipheringKeyIndex

Tetrapol:Messages REMS:REMS Specific:FrameErrorRate

Frame Error Rate

Tetrapol:Messages REMS:REMS Specific:MOCHList

Priority
MOCHId
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 70/89
10/10/2019 Nemo Analyze KPI List

Tetrapol:Messages REMS:REMS Specific:ParamCellForcing

CellForcingType

Tetrapol:Messages REMS:REMS Specific:ParamDMEncription

AccessType
Activated

Tetrapol:Messages REMS:REMS Specific:ParamDMTransmitPower

Value

Tetrapol:Messages REMS:REMS Specific:ParamGatheringComm

Reference

Tetrapol:Messages REMS:REMS Specific:STAlarm

AlarmType

Tetrapol:Messages REMS:REMS Specific:SignalStrengh

SignalStrength_BarLevel

Tetrapol:Messages REMS:REMS Specific:SpeechState

EndCause

Tetrapol:Messages REMS:REMS Specific:TKGList

Available
Merged
TKGId

Tetrapol:Messages REMS:REMS Specific:TalkingParty

CallerId

Tetrapol:Messages REMS:REMS Specific:VoiceRecord

RecordedFilename
ReferenceFilename
ListeningQual
EffortQual

Tetrapol:Messages REMS:REMS Specific:WriteParamFailure

ParameterType
CauseType
CauseParamWriteFailure

Tetrapol:Messages REMS:Standard and REMS:CSelBSInfo

CCRConfig

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 71/89


10/10/2019 Nemo Analyze KPI List

CCRParam
BNNb
ChannelId

Tetrapol:Messages REMS:Standard and REMS:CSelCCHAnalysis

SynchroCCH
SystemInfoMode
BCH
ROAM
ECCH
ATTA
MuxType
Sim
CountryCode
Network
Version
SystemIdMode
LocId
Scrambling
TxMax
RadioTimeOut
PwrAdjust
SystemTime
MinRegClass
MinServClass

Tetrapol:Messages REMS:Standard and REMS:CSelDistribMOCHList

CellRadioType
Revision
DC
CSO
CSG
CellDistribMode
Index
COVId
CallPriority
GroupId
MOCHType
AdditionalParticipants
NeighbourCellId

Tetrapol:Messages REMS:Standard and REMS:CSelOGDeliv

OGType
OG

Tetrapol:Messages REMS:Standard and REMS:CSelRegistration

CurrentCellId
SelRegType

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 72/89


10/10/2019 Nemo Analyze KPI List

Tetrapol:Messages REMS:Standard and REMS:CSelStart

SelType
Restriction
BNId
RSW
BS
PreferentialBN
CSelStart Cause
CSelStart Type
CSelRegistration Result

Tetrapol:Messages REMS:Standard and REMS:CSelTKGDeliv

TKGType
OGId

Tetrapol:Messages REMS:Standard and REMS:DTGClose

Cause

Tetrapol:Messages REMS:Standard and REMS:DTGOpen

AppId
ContextReference

Tetrapol:Messages REMS:Standard and REMS:NeighbourCell

BNType
Loc
Exp

Tetrapol:Messages REMS:Standard and REMS:RSelBestNeighbourCell

SelectionCriteria

Tetrapol:Messages REMS:Standard and REMS:RSelMeans

MeansType
C1
C2

Tetrapol:Messages REMS:Standard and REMS:TxPower

TxPower Level

Tetrapol:Queries

Nominal FER
RxLev selected channel
RxLev min
RxLev max
RxLev average

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 73/89


10/10/2019 Nemo Analyze KPI List

Tetrapol:Statistics data

RSelDuration
FastRSelDuration
CSelDuration

UMTS

Cell reselection U-plane interruption time


The time from the last packet in the old cell to the first packet in the new cell. This parameter is only recorded during the
data transfer and only for LTE to LTE, LTE to HSPA, and HSPA to LTE cell reselections and redirections.
Softer handover
Number of cells in handover from same site
Ec/N0 and RSCP active set with BTS ref. information
Information on active set from the BTS reference file
Measured cell list UMTS (BTS ref.)
List of distinct measured active, monitored, detecte, and undetected cells.
Ec/N0 and RSCP monitored set with BTS ref. information
Information on monitored set from the BTS reference file
Serving cell BTS ref. information
Information on best serving cell from the BTS reference file
Cell name (BTS ref.)
Name of the best serving cell from the BTS reference file
Serving system and band
Recorded when channel configuration information changes.
Serving system
Recorded when channel configuration information changes.
Serving band
Recorded when channel configuration information changes.
Neighbor list
List of GSM and UMTS neighbors seen by the terminal
Radio bearer info
Recorded when UMTS radio bearer allocation is modified. Currently based on information received from the trace interface
of the device.
Transport channel info
Recorded when UMTS transport channel allocation is modified. Currently based on information received from the trace
interface of the device.
Number of missing UMTS neighbors
Finger Ec/N0
The received energy per chip divided by the power density of the band.
Finger RSCP
The received signal code power of single code.
Ec/N0 active set
Ec/N0 monitored set
Ec/N0 detected set
Ec/N0 undetected set
BLER selected transport channel
BLER transport channels
Active, monitored and detected set cells information
Distance based RSCP CPICH average from scanner for serving cell
RSCP active set
RSCP monitored set
RSCP detected set
RSCP undetected set
RSCP vs. Ec/N0
Scatter or colorgrid of Ec/N0 vs RSCP for active set cells
Missing neighbor Ec/N0
Missing neighbor diff. to strongest
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 74/89
10/10/2019 Nemo Analyze KPI List
Difference between missing neighbor and the best cell seen by the terminal in dB
Missing neighbor RSCP
Mobile country code
Recorded when service state or mobility information changes.
See ITU-T recommendation E.212.
Operator
Mobile network code
Recorded when service state or mobility information changes.
TMSI
Recorded when service state or mobility information changes.
Temporary mobile subscriber identity. See 3GPP TS 124.008 subclause 10.5.1.4 and 3GPP TS 123.003 subclause 2.4.
P-TMSI
Recorded when service state or mobility information changes.
Packet temporary mobile subscriber identity. See 3GPP TS 124.008 subclause 10.5.1.4 and 3GPP TS 123.003 subclause
2.7.
Location area update failure
Recorded based on MM layer3 signaling when location area update has failed. This measurement event terminates the
location area update state.
Location area update attempt
Recorded when the mobile starts location area update using MM layer3 signaling message. This measurement event
begins the location area update state.
Location area update success
Recorded based on MM layer3 signaling when location area update has been successful. This measurement event
terminates the location area update state.
Location area update time
Routing area update failure
Recorded based on GMM signaling when routing area update is successful. This measurement event terminates the routing
area update attempt state.
Routing area update attempt
Recorded based on GMM signaling when routing area update is attempted. This measurement event begins the routing
area update attempt state.
Routing area update success
Recorded based on GMM signaling when routing area update is successful. This measurement event terminates the routing
area update attempt state.
Routing area update time
Cell identification
Cell identity of the current cell. For GSM this is 16 bit value, for UMTS this is 28 bit value (RNC ID + 16 bit cell ID), and for
LTE this is 28 bit value (eNB ID + 8 bit cell ID).
Carrier number
Neighbor Srxlev criterion
Cell selection criterion S based on RX level. This value is only available during the UMTS mode. See 3GPP TS 25.304
subclause 5.2.3 cell selection process.
RX level neighbor
Location area code
Addition window
Addition window for event 1A. Cells within addition window range from the best serving CPICH will be added to the active
set. The value is calculated using the following formula: R1A - H1A / 2 where R1A is reporting range constant for event 1A
and H1A is hysteresis parameter for event 1A. See 3GPP TS 25.331.
Time to trigger 1A
Indicates the period of time during which the event condition must be satisfied before sending a Measurement Report with
event 1A. See 3GPP TS 25.331.
Drop window
Drop window for event 1B. Cell is removed from the active set if it falls below the drop window range from the best cell in
the active set. The value is calculated using the following formula: R1 B + H1 B / 2 where R1B is reporting range constant
for event 1B and H1B is hysteresis parameter for event 1B. See 3GPP TS 25.331.
Time to trigger 1B
Indicates the period of time during which the event condition must be satisfied before sending a Measurement Report with
event 1B. See 3GPP TS 25.331.
Replacement window
If a monitored-set cell becomes better than a cell in the active set, the active set cell will be replaced with the better one.
See 3GPP TS 25.331.
Time to trigger 1C
Indicates the period of time during which the event condition must be satisfied before sending a Measurement Report with
event 1C. See 3GPP TS 25.331.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 75/89


10/10/2019 Nemo Analyze KPI List

Spreading factor downlink


If multiple CCTrCh channels are used, the reported spreading factor is for CCTrCh with physical control channel.
Min spreading factor uplink
Minimum allowed uplink spreading factor.
DRX cycle length
Defines how often paging indications are monitored.
Max TX power
Maximum allowed uplink power.
L3 signaling
Recorded when a Layer 3 or an NAS signaling message is sent or received.
RRC and L3 signaling
RLC/MAC/L3/RRC signaling DL and UL separated
RLC/MAC/L3/RRC signaling
L3 message search
Searches for user-defined messages, with user-defined string in the message name
RLC message search
Searches for user-defined messages, with user-defined string in the message name
RLC signaling
Recorded when an RLC signaling message is sent or received.
Routing area code
Network mode of operation
Avg. Tx power per 1st active scr code
BLER DL
Soft-softer handover status
Status of the soft handover. Soft:2-way HO to 2 distinct sites, Softer: 2-way HO to cells of 1 distinct site, Soft-Softer: 3-
way HO to cells of 2 distinct sites, Soft-Soft: 3-way HO to 3 distinct sites, Softer-Softer: 3-way handoff to cells of 1
distinct site, 4-way soft: all 4-way soft and softer HOs, 5-way soft: all 5-way soft and softer HOs, 6-way soft: all 6-way
soft and softer HOs, 2-way, soft-softer status unknown: 2-way HO where there is no BTS reference available, 3-way, soft-
softer status unknown: 3-way HO where there is no BTS reference available
RLC throughput uplink
The value of this parameter is calculated based on the SDUs that are successfully transferred through the RLC layer.
Missing and erroneous RLC blocks are excluded from the throughput calculation.
RLC throughput downlink
The value of this parameter is calculated based on the SDUs that are successfully transferred through the RLC layer.
Missing and erroneous RLC blocks are excluded from the throughput calculation.
RLC retransmission rate uplink
TX power
The total UE transmitted power on one carrier. See 3GPP TS 125.215 subclause 5.1.7.
TX power control algorithm
TX power control step size
Compressed mode
Percentage of "UL power up" commands
In percentage the number of "UL power up" commands from all commands. If this value is 100%, all commands request
to increase power.
Percentage of "DL power up" commands
In percentage the number of "DL power up" commands from all commands. If this value is 100%, all commands request
to increase power.
Signal-to-interference ratio target
Current target SIR at update time.
Signal-to-interference ratio
See 3GPP TS 125.215 subclause 5.2.2.
BS diversity state
Base Station TX closed loop diversity state.
DL Power control mode
BER pilot bit
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Bit error rate of downlink DPCCH (dedicated physical control channel) pilot bits.
BER TFCI
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
Estimated raw BER before channel coding based on TFCI bits.
Carrier RSSI

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 76/89


10/10/2019 Nemo Analyze KPI List
Wide-band carrier power including thermal noise, co-carrier and adjacent carrier interference, and noise generated in the
receiver.
Number of active set cells
CFN-SFN difference in frames (OFF) active set
CFN-SFN difference in frames (OFF) monitored set
CFN-SFN difference in frames (OFF) detected set
CFN-SFN difference in chips (Tm) active set
CFN-SFN difference in chips (Tm) monitored set
CFN-SFN difference in chips (Tm) detected set
Scrambling codes active set
Scrambling codes monitored set
Scrambling codes detected set
Scrambling codes undetected set
Number of monitored set cells
Number of detected set cells
Number of undetected set cells
Uplink DPDCH bitrate
L3 signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message
Number of scrambling codes added
Recorded when the active set changes. Event information is based on RRC signaling with UMTS FDD.
Number of scrambling codes removed
Recorded when the active set changes. Event information is based on RRC signaling with UMTS FDD.
Added scrambling code number
Removed scrambling code number
Soft handover event
Recorded when the active set changes. Event information is based on RRC signaling with UMTS FDD.
Time being 1st active scr
Percentage of time out from the total, when a scrambling code has been the best in active set
Dropped RRC connections per 1st active scr
Dropped RRC connections by best active set scrambling code
Dropped call due ISHO failure per 1st active scr
Dropped calls due inter system handover failure grouped by first active set scrambling code
UMTS to UMTS missing neighbor analysis
This analysis is based on NMISS events recorded by Nemo Outdoor. Missing neighbor analysis UMTS intra-frequency
provides the same analysis without relying on Nemo Outdoor missing neighbor measurements. List of all missing neighbor
and best active set cell pairs where the missing neighbor is within user defined window from the best active set cell.
Time being missing neighbor
Percentage of time for each missing neighbor scrambling code out from the total elapsed time for all missing neighbors
Missing GSM neighbor per 1st active scr
Missing GSM neighbors per best active set scrambling code
Number of missing GSM neighbors per 1st active scr
Number of missing GSM neighbors per best active set scrambling code
CPICH Ec/N0 and RSCP table
Pilot pollution number of polluting cells
Number of cells that are within user defined window from the active set best cell in terms of Ec/N0, when active set best
RSCP is above, and active set best Ec/N0 is below use defined threshold.
Pilot pollution number of polluting cells per channel
Number of cells that are within user defined window from the active set best cell in terms of Ec/N0, when active set best
RSCP is above, and active set best Ec/N0 is below use defined threshold.
Pilot pollution cells
Cells that are within user defined window from the active set best cell in terms of Ec/N0, when active set best RSCP is
above, and active set best Ec/N0 is below use defined threshold.
Measured cells UMTS
Unique combinations of channel number and scrambling code. Note that scrambling codes may overlap.
Treselection
The time which the new cell has had to be ranked better than the old cell before cell reselection is possible. See 3GPP TS
25.304 subclause 5.2.6.1.4.
Measurement event
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 77/89
10/10/2019 Nemo Analyze KPI List
Recorded when a UMTS measurement event is transmitted to the network based on signaling messages.
Downlink Band
Scr. code active set best
Ec/N0 best active set
RSCP best active set
Ec/N0 Nth best selected set
RSCP Nth best selected set
RSCP Nth best selected set (dBuV/m)
Ec/N0 selected Cell ID (BTS ref.)
Ec/N0 selected scrambling code
RSCP selected cell ID (BTS ref.)
RSCP selected scrambling code
Ec/N0 Nth best active set
Ec/N0 Nth best
RSCP Nth best
G-factor estimate
Calculation: Best serving cell RSCP/(2nd best RSCP + 3rd best RSCP + ... + Thermal noise (-101dBm)) estimates the G-
factor with the assumption that all cells are equally loaded
Number of cells within X dB window from the best
Number of cells where the CPICH Ec/N0 is within user-definable window from the best cell
Spreading factor downlink during downlink data transfer
Spreading factor filtered from the time instants where data transfer is active (between DREQ and DCOMP nemo events)
Min spreading factor uplink during uplink data transfer
Spreading factor filtered from the time instants where data transfer is active (between DREQ and DCOMP nemo events)
Cell reselection GSM to UMTS
Cell reselection inter-system
Cell reselection UMTS to GSM
Cell reselection
Handover events
Handover attempt
Handover success
Handover duration
Handover attempt inter-system
Handover attempt GSM to UMTS
Handover success inter-system
Handover success GSM to UMTS
Handover attempt UMTS to GSM
Handover success UMTS to GSM
Soft handover failure
Handover failure
Handover failure inter-system
Handover failure UMTS to GSM
Handover failure GSM to UMTS
Monitored set size distribution
Average RSCP and Ec/N0 per 1st active scr code
Scr. code Nth best
Frame error rate
Calculated from the speech frames.
Pathloss active set
Pathloss monitored set
Pathloss detected set
Pathloss undetected set
Pathloss best active set
Pathloss selected scrambling code

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 78/89


10/10/2019 Nemo Analyze KPI List

Pathloss Nth best


RLC throughput uplink per radio bearer
Uplink RLC throughput for specified radio bearer.
RLC throughput downlink per radio bearer
Downlink RLC throughput for specified radio bearer.
RLC retransmission rate uplink per radio bearer
Modulation 2G/3G

UMTS Scanner

Delay CPICH
Delay P-SCH
Delay S-SCH
Delay profile CPICH
Delay spread CPICH
Timeslot scan P-SCH
Wideband RSSI
Wideband RSSI selected carrier
RSCP CPICH
RSCP CPICH distance based average selected carriers
RSCP CPICH Nth best distance based average selected carriers
RSCP CPICH selected carrier
RSCP CPICH selected cell ID (BTS ref.)
RSCP CPICH selected scrambling code
RSCP CPICH best
RSCP CPICH Nth best
RSCP P-SCH
RSCP S-SCH
RSCP CPICH (Tx diversity)
RSCP PPCH
Ec/N0 CPICH
Ec/N0 CPICH selected carrier
Ec/N0 CPICH selected cell ID (BTS ref.)
Ec/N0 CPICH selected scrambling code
Scrambling code best
Ec/N0 CPICH best
Ec/N0 CPICH Nth best
Ec/N0 CPICH distance based average selected carriers
Ec/N0 CPICH Nth best with BTS ref. information
Ec/N0 CPICH selected carrier with BTS ref. information
Measured CPICH list selected carrier (BTS ref.)
Ec/N0 P-SCH
Ec/N0 S-SCH
Ec/N0 CPICH (Tx diversity)
Ec/N0 PPCH
SIR CPICH
SIR CPICH selected scrambling code
SIR CPICH best
RSCP CPICH top N selected carriers
RSCP CPICH Nth best selected carriers
RSCP CPICH Nth best selected carriers MNC
RSCP CPICH MNC
RSCP CPICH Nth best selected carriers (dBuV/m)

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 79/89


10/10/2019 Nemo Analyze KPI List

Channel number Nth best selected carriers


SC Nth best selected carriers
EC/N0 CPICH Nth best selected carriers
EC/N0 CPICH top N selected carriers
L3 signaling
Cellscan and Scan events combined
Carrier RSSI (frequency scanning mode)
Carrier power including thermal noise, co-carrier and adjacent carrier interference, and noise generated in the receiver.
RRC signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message
RRC signaling
Scanning configuration
Defines scanning settings.
Pilot pollution
Number of cells that are within user defined window from the active set best cell in terms of Ec/N0, when active set best
RSCP is above, and active set best Ec/N0 is below use defined threshold.
G-factor estimate
Calculation: Best cell RSCP/(2nd best RSCP + 3rd best RSCP + ... + Thermal noise (-101dBm)) estimates the G-factor
with the assumption that all cells are equally loaded
Number of CPICH within X dB window from the best
Number of cells where the CPICH Ec/N0 is within user-definable window from the best cell
Cellscan
Recorded when parameter sample is received from the device. With GSM the system information messages, and with
UMTS and LTE the system information blocks, are decoded to produce the information required for this measurement
event.

UMTS:Cell reselection criteria

Hqual active set


Hqual monitored set
Hqual detected set
Hrxlev active set
Hrxlev monitored set
Hrxlev detected set
Rrxlev active set
Rrxlev monitored set
Rrxlev detected set
Rqual active set
Rqual monitored set
Rqual detected set
Squal active set
Squal monitored set
Squal detected set
Srxlev active set
Srxlev monitored set
Srxlev detected set

UMTS:HSDPA

HSDPA CQI distribution


An estimate of the link adaptation (transport block size, the modulation type, the number of parallel codes, and the
spreading factor) required to enable correct reception with reasonable block error rate. The measured value is reported
periodically to the network. This information can be used for data scheduling and link adaptation. When the secondary CQI
has a valid value, the range of the parameter is limited to values 0-14. See 3GPP TS 125.214 subclause 6A.2.
HSDPA CQI distribution for secondary stream
An estimate of the link adaptation (transport block size, the modulation type, the number of parallel codes, and the
spreading factor) required to enable correct reception with reasonable block error rate. The measured value is reported

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 80/89


10/10/2019 Nemo Analyze KPI List
periodically to the network. This information can be used for data scheduling and link adaptation. This parameter is always
n/a when CQI type B is used. See 3GPP TS 125.214 subclause 6A.2.
HSDPA CQI type
See 3GPP TS 125.214 subclause 6A.1.2.2.
HSDPA MAC-hs ACK/NACK count
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session.
The total number of ACK and NACK status messages sent to the uplink by MAC-hs layer.
HSDPA MAC-hs block error rate
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session.
The ratio of erroneously received MAC-hs PDUs to all received MAC-hs PDUs.
HSDPA MAC-hs residual block error rate
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session.
The ratio of transport blocks that have not been fixed by HARQ (in the MAC-hs layer) to all 'new data' indicated transport
blocks (= first attempts).
HSDPA MAC-hs block rate
The total number of MAC-hs PDUs received during the reporting interval.
HSDPA MAC-hs throughput
The value of this parameter is calculated based on the SDUs that are successfully received through the MAC-hs layer.
Missing and erroneous MAC-hs blocks are excluded from the throughput calculation. When exact MAC-hs SDUs are not
available the approximation of the MAC-hs throughput is calculated based on transport block sizes ignoring incorrect or
duplicated transport blocks. This causes a minor error between reported throughput and real MAC-hs throughput but it still
provides a very good approximation of the real MAC-hs throughput.
HSDPA percentage (DTX)
HS-DSCH activity rate
Percentage of TTIs over the reporting periond (200ms or 100ms depending on the terminal) when there has been data
allocated to the terminal.
HSDPA MAC-hs 1st retransmission rate
The ratio of MAC-hs PDUs retransmitted after the first transmission attempt.
HSDPA MAC-hs 2nd retransmission rate
The ratio of MAC-hs PDUs retransmitted after the second transmission attempt.
HSDPA MAC-hs 3rd+ retransmission rate
The ratio of MAC-hs PDUs retransmitted after the third or later transmission attempt.
HSDPA MAC-hs redundant retransmission rate
The ratio of MAC-hs PDUs that has already been correctly received and has unnecessarily been retransmitted (duplicated
transmission). This happens when the ACK message sent by the mobile is decoded or received incorrectly, or not received
at all, by the the base station.
HSDPA HS-DSCH measurement power offset
Measurement power offset. This parameter is configured in RRC layer.
HSDPA #HS-SCCHs
HSDPA serving HS-DSCH scrambling code
HSDPA serving HS-DSCH sc and cell name primary (BTS ref.)
HSDPA serving HS-DSCH sc and cell name secondary (BTS ref.)
HSDPA 64QAM
HSDPA MAC header type
Defines what kind of MAC header is used for HSDPA.
HSDPA used UE category
Defines the current maximum possible HSDPA UE category. This is limited by cell configuration and UE capabilities. The
value can be smaller than the maximum UE category supported by the mobile if for example the currently used cell is
restricting the UE category (either MAC-ehs or dual cell mode is not supported).
HSDPA dual carrier status
HSDPA MIMO rank 2 request ratio
Defines the percentage of time MIMO was requested using CQI values. This is the ratio of double CQI values to total of
type A CQI values. This parameter is also known as rank indicator.
HSDPA CQI (mode)
The most common CQI value over the reporting period
HSDPA CQI for secondary stream (mode)
The most common secondary stream CQI value over the reporting period
Packet technology/RRC state during data transfer
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 81/89
10/10/2019 Nemo Analyze KPI List

Packet technology
Packet technology during data transfer
Packet technology between nemo events DAA to DAD or DAF
Avg. MAC-HS throughput per scrambling code
HS-SCCH usage
Recorded every 200 milliseconds to indicate HS-SCCH channel usage based on the trace messages of the mobile. This
measurement event is recorded simultaneously with the PLAID measurement event.
Defines the ratio of TTIs when new or retransmitted data is indicated using this HS-SCCH channelisation code. Note that
the sum of the percentages is 200 when the measurement event contains information about primary and secondary
HSDPA cells.
HS-SCCH usage combined
HS-SCCH usage combined is parameter where all channels usage percentages are summed together
HARQ Throughput
Recorded every 200 milliseconds to indicate HSDPA HARQ throughput based on the trace messages of the mobile. This
measurement event is recorded simultaneously with the PLAID measurement event.
The value of the parameter is calculated from the transport block sizes for each HARQ process separately.
HARQ BLER
Recorded every 200 milliseconds to indicate HSDPA HARQ throughput based on the trace messages of the mobile. This
measurement event is recorded simultaneously with the PLAID measurement event.
The ratio of erroneously received MAC-hs PDUs to all received MAC-hs PDUs for each HARQ process separately.
HSDPA physical layer requested throughput
Computational throughput based on the transport block sizes indicated by the CQI values. In MIMO mode, only CQI type A
is used for the calculation. This is the throughput that would have been achieved if the network had sent the link
adaptation parameters defined by the CQI.
Number of active HS-SCCHs
Number of HS-SCCHs that have being active (hs-scch usage > 0) during the reporting interval
G-factor estimate
Calculation: Best serving cell RSCP/(2nd best RSCP + 3rd best RSCP + ... + Thermal noise (-101dBm)) estimates the G-
factor with the assumption that all cells are equally loaded
HSDPA MIMO
MIMO Ec/N0
Currently the recording interval is about two times per second. This measurement event is currently only logged for
serving cells.
MIMO RSCP
Currently the recording interval is about two times per second. This measurement event is currently only logged for
serving cells.
MIMO RSSI
Currently the recording interval is about two times per second. This measurement event is currently only logged for
serving cells.

UMTS:HSDPA:Link adaptation

HSDPA link adaptation parameter distribution


HSDPA number of codes distribution
HSDPA modulation distribution
HSDPA transport block size statistics
HSDPA MIMO usage ratio
The percentage of TTIs during the reporting period when dual stream transfer is used. This value displays the exact
amount of MIMO used with HSDPA.
HSDPA transport block size (mode)
The most common value of the transport block size over the reporting period
HSDPA transport block size for secondary stream (mode)
The most common value of the secondary stream transport block size over the reporting period
HSDPA number of codes (mode)
The most common value of number of multicodes over the reporting period
HSDPA effective coding (mode)
The most common value of effective coding over the reporting period
HSDPA effective coding for secondary stream (mode)
The most common value of secondary stream effective coding over the reporting period
HSDPA HS-SCCH type (mode)
The most common value of HS-SCCH type over the reporting period
HSDPA modulation (mode)
The most common value of modulation over the reporting period

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 82/89


10/10/2019 Nemo Analyze KPI List

HSDPA 16QAM percentage


Percentage of 64QAM modulation over the reporting period.
HSDPA 64QAM percentage
Percentage of 64QAM modulation over the reporting period.
HSDPA modulation for secondary stream (mode)
The most common value of secondary stream modulation over the reporting period
HSDPA MAC-hs BLER (mode)
The most common value of MAC-hs BLER over the reporting period
HSDPA MAC-hs BLER for secondary stream (mode)
The most common value of secondary stream MAC-hs BLER over the reporting period
HSDPA HS-PDSCH throughput
High-Speed Physical Downlink Shared Channel throughput is calculated from all (also retransmitted) transport blocks
received from the HS-DSCH transport channel and divided by sample duration. This parameter is also known as HSDPA
physical channel throughput or served throughput.
HSDPA scheduled throughput
HSDPA MAC-hs BLER percentage

UMTS:HSUPA

HSUPA MAC-e throughput


The value of this parameter is calculated based on the SDUs that are successfully transferred through the MAC-e layer.
Missing and erroneous MAC-e blocks are excluded from the throughput calculation. Approximation of MAC-e throughput is
calculated from transport block sizes if real MAC-e throughput is not provided by diagnostic interface of the device.
Approximation is a little bit higher than real MAC-e throughput since it contains MAC headers and padding.
HSUPA MAC-e block rate
The total number of MAC-e PDUs transmitted during the reporting period.
HSUPA HARQ BLER
Calculated as: MAC-e 1st + 2nd + 3rd retransmission rate
HSUPA MAC-e 1st retransmission rate
The ratio of MAC-e PDUs retransmitted after the first transmission attempt.
HSUPA MAC-e 2nd retransmission rate
The ratio of MAC-e PDUs retransmitted after the second transmission attempt.
HSUPA MAC-e 3rd+ retransmission rate
The ratio of MAC-e PDUs retransmitted after the third or later transmission attempt.
HSUPA E-DPDCH throughput
E-DPDCH throughput is calculated from all (including retransmitted) transport blocks transmitted in the E-DCH transport
channel.
HSUPA E-DCH information
HSUPA E-TFCI table index
HSUPA AGCH channelisation code
HSUPA happy bit delay condition
HSUPA E-DPCCH/DPCCH power offset
HSUPA secondary E-RNTI
HSUPA primary E-RNTI
HSUPA rate matching mode
Defines how retransmitted data is combined.
HSUPA PLnon-max
Puncturing limit used to determine the combination of SF and number of codes that are used for transmitting E-DCH with
certain data rate.
HSUPA TTI
HSUPA transmission time interval.
HSUPA UE category
Defines the current maximum possible HSUPA UE category. This is limited by cell configuration and UE capabilities.

UMTS:HSUPA:Link adaptation

HSUPA happy bit status percentage


The measurement event contains information on the state of the happy bit transmitted by the mobile to the network
during an HSUPA session. The measurement event is recorded simultaneously with the PLAIU measurement event. The
measurement event is logged only for primary serving cell with DC-HSUPA.
Defines how often happy bit status was set happy during previous reporting interval excluding DTX TTIs.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 83/89


10/10/2019 Nemo Analyze KPI List

HSUPA happy bit DTX percentage


The measurement event contains information on the state of the happy bit transmitted by the mobile to the network
during an HSUPA session. The measurement event is recorded simultaneously with the PLAIU measurement event. The
measurement event is logged only for primary serving cell with DC-HSUPA.
How many TTIs DTX was used during previous reporting period.
HSUPA E-TFC selection limited by max power percentage
Percentage of frames when larger E-TFCI selection would cause exceeding of the maximum allowed TX power usage.
HSUPA E-TFC selection limited by serving grant percentage
Percentage of frames when larger E-TFCI cannot be selected since it would require more power than allowed by current
serving grant.
HSUPA E-TFC selection limited by lack of data percentage
Percentage of frames when larger E-TFCI cannot be selected since mobile's output buffers doesn't contain enough data.
HSUPA non-serving ACK percentage
Defines how often only non-serving E-DCH cell has reported ACK. Non-transmitting frames are ignored.
HSUPA non-serving grant down percentage
Defines how often non-serving E-DCH cell has reported grant down even if serving E-DCH cell has reported grant up or
hold. Non-transmitting frames are ignored.
HSUPA link adaptation parameter distribution
HSUPA E-TFCI (mode)
The most common value of E-TFCI over the reporting period
HSUPA spreading codes (mode)
The most common value of spreading codes over the reporting period
HSUPA absolute grant
Recorded when serving grant is modified using E-AGCH channel. Note that this measurement event is not necessarily
recorded exactly with the correct timestamp because of limitations in the trace interface of the mobile. For the same
reason, there can be multiple AGRANT measurement events with the same timestamp. In these cases, the order of the
measurement events is the order of the E-AGCH modifications.
HSUPA serving grant
The measurement event contains statistical information on the used serving grant based on the trace interface. The
measurement event is reported during an HSUPA session simultaneously with the PLAIU measurement event. Separate
measurement event is logged for each serving cell with DC-HSUPA.
HSUPA serving grant (mode)
The most common value of serving grant over the reporting period
HSUPA serving grant utilization
SG utilization is total of all transferred scheduled bits divided by bits that could have been transferred if appropriate
serving grant index would have been used. This is approximately same as the ratio between transferred throughput and
serving grant throughput
HSUPA E-TFC selection limited by mux restriction percentage
Percentage of frames when larger E-TFCI cannot be selected since MAC-d flows containing data cannot be multiplexed
together with currently selected MAC-d flow. Allowed multiplexing is defined by E-DCH MAC-d flow multiplexing list -
parameter in 3GPP TS 125.331 subclause 10.3.5.1b.
HSUPA E-TFC selection limited by HARQ restriction percentage
Percentage of frames when larger E-TFCI cannot be selected since certain MAC-d flows cannot be send using current used
HARQ process. Allowed HARQ processes per MAC-d flow is controlled by 2ms non-scheduled transmission grant HARQ
process allocation -parameter in 3GPP TS 125.331 subclause 10.3.5.1b. Non-zero only when 2ms subframes are used.
HSUPA granted throughput
The throughput that would have been achieved if all power defined by the serving grant had been used for the data
transmission.

UMTS:HSUPA:Scheduling info

HSUPA SI highest priority logical channel ID


The measurement event contains statistical information on the transmitted Scheduling Information based on the trace
interface. The measurement event is reported during an HSUPA session simultaneously with the PLAIU measurement
event. The measurement event is logged only for primary serving cell with DC-HSUPA.
HSUPA SI highest priority logical channel buffer status
The measurement event contains statistical information on the transmitted Scheduling Information based on the trace
interface. The measurement event is reported during an HSUPA session simultaneously with the PLAIU measurement
event. The measurement event is logged only for primary serving cell with DC-HSUPA.
HSUPA SI total E-DCH buffer status
The measurement event contains statistical information on the transmitted Scheduling Information based on the trace
interface. The measurement event is reported during an HSUPA session simultaneously with the PLAIU measurement
event. The measurement event is logged only for primary serving cell with DC-HSUPA.
This is a mode of all E-DCH buffer status received during reporting period.
HSUPA SI total E-DCH buffer status minimum

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 84/89


10/10/2019 Nemo Analyze KPI List
The measurement event contains statistical information on the transmitted Scheduling Information based on the trace
interface. The measurement event is reported during an HSUPA session simultaneously with the PLAIU measurement
event. The measurement event is logged only for primary serving cell with DC-HSUPA.
This is a minimum of all E-DCH buffer status received during reporting period.
HSUPA SI total E-DCH buffer status maximum
The measurement event contains statistical information on the transmitted Scheduling Information based on the trace
interface. The measurement event is reported during an HSUPA session simultaneously with the PLAIU measurement
event. The measurement event is logged only for primary serving cell with DC-HSUPA.
This is a maximum of all E-DCH buffer status received during reporting period.
HSUPA SI UE power headroom
The measurement event contains statistical information on the transmitted Scheduling Information based on the trace
interface. The measurement event is reported during an HSUPA session simultaneously with the PLAIU measurement
event. The measurement event is logged only for primary serving cell with DC-HSUPA.
This is mode of all UE power headrooms received during reporting period.
HSUPA SI UE power headroom minimum
The measurement event contains statistical information on the transmitted Scheduling Information based on the trace
interface. The measurement event is reported during an HSUPA session simultaneously with the PLAIU measurement
event. The measurement event is logged only for primary serving cell with DC-HSUPA.
This is minimum of all UE power headrooms received during reporting period.
HSUPA SI UE power headroom maximum
The measurement event contains statistical information on the transmitted Scheduling Information based on the trace
interface. The measurement event is reported during an HSUPA session simultaneously with the PLAIU measurement
event. The measurement event is logged only for primary serving cell with DC-HSUPA.
This is maximum of all UE power headrooms received during reporting period.

UMTS:RACH

Primary CPICH Tx power


Constant value
RACH initial TX power
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
TX power Initial transmission power.
RACH preamble step
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Preamble step size.
RACH preamble count
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Transmitted preamble transmission count.
RACH TX power
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
Total transmission power used in RACH message part (control + data).
RACH maximum preamble count
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
This is the same as 'Preamble Retrans Max' parameter signaled by network in RRC layer and it defines the maximum
number of preamble attempts.
RACH AICH status
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH data channel gain
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH control channel gain
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
RACH power offset
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.
This is the same as Pp-m parameter in RRC specification. Power offset between the last transmitted preamble and the
control part of the message.
RACH message length
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 85/89


10/10/2019 Nemo Analyze KPI List

UL interference
Recorded after random access to the network has been attempted. With UMTS FDD, a RACHI measurement event is
recorded for each random access procedure.

UMTS:RRC

RRC state
RRC state during data transfer
RRC state filtered from the tim instants where data transfer is active (between DREQ and DCOMP nemo events
RRC and L3 signaling
RLC/MAC/L3/RRC signaling DL and UL separated
RLC/MAC/L3/RRC signaling
RRC message search
Searches for user-defined messages, with user-defined string in the message name
RRC signaling parameter search
Searches for user-defined text inside decoded messages, and returns the following field for the first match. With the
search start text it is possible to configure, that search starts after first occurence of another text in the decoded message
RRC signaling
RRC connection attempt
Recorded based on RRC signaling when RRC connection is attempted. This measurement event begins the RRC connection
attempt state.
RRC connection connected
Recorded based on RRC signaling when RRC connection is established. This measurement event begins the RRC
connection state.
RRC connection disconnected
RRC connection attempt failure
Recorded based on RRC signaling when RRC connection attempt fails. This measurement event terminates the RRC
connection attempt state.
Dropped RRC connection
Recorded based on RRC signaling when RRC connection is released. This measurement event terminates the RRC
connection state.

WLAN

WLAN RSSI Nth best


WLAN max transfer rate
WLAN security mode
WLAN IP address
The IP address for the WLAN access point.
Signal quality serving
Signal quality neighbours
RSSI serving
RSSI neighbours

WiMAX

WiMAX pilot pollution


Number of cells that are within user defined window from the best cell in terms of RSSI, when best RSSI is above and
CINR is below user defined threshold.
Handover events
Handover attempt
Handover success
Handover duration
With the LTE this defines the handover duration containing handover processing and interrupt time. Time from the
handover initiating RRC signaling message to the succesfully completed RACH procedure in the new cell.
Handover to preamble time
Time from handover attempt (RRC signaling message) to the first random access preamble (MSG1) in the target cell. Only
support for LTE to LTE handovers.
Handover U-plane interruption time
Defines the time from the last packet in the old cell to the first packet in the new cell.
file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 86/89
10/10/2019 Nemo Analyze KPI List

Handover failure
MAC signaling
WiMAX frame ratio downlink
WiMAX frame ratio uplink
WiMAX coding type used on DL-MAP
WiMAX repetition coding used on DL-MAP
WiMAX base station ID
Six colon separated hex values.
WiMAX MAC state
WiMAX frequency
WiMAX FFT size
WiMAX bandwidth
WiMAX RSSI
Signal strength.
WiMAX RSSI deviation
WiMAX CINR
Channel to interference-noise ratio.
WiMAX CINR deviation
Channel to interference-noise ratio devitaion.
WiMAX neighbor RSSI
WiMAX neighbor RSSI deviation
WiMAX neighbor CINR
WiMAX neighbor CINR deviation
WiMAX TX power
MS transmit power.
WiMAX TX reference power
WiMAX TX power headroom
WiMAX PER
Recorded when parameter sample is received from the device and the received sample differs from the previous result.
This UMTS measurement event is recorded simultaneously with the PLAID measurement event and only during HSDPA
session.
WiMAX frame lost ratio
Recorded when frame error rate reports are received from the device.
WiMAX TX power BS offset
WiMAX initial ranging max TX power
WiMAX BS EIRP
Base station effective isotrophic radiated power.
WiMAX BS noise + interference level
WiMAX MAC throughput uplink
WiMAX MAC throughput downlink
WiMAX MAC packet rate uplink
WiMAX MAC packet rate downlink
WiMAX preamble index
WiMAX IDCell
WiMAX segment

WiMAX Scanner

Carrier RSSI (frequency scanning mode)


RSSI of all subcarriers.
Carrier RSSI (OFDM scanning mode)
RSSI of all subcarriers.
Carrier RSSI (OFDM scanning mode) Nth best
RSSI of the best subcarrier
WiMAX frequency and preamble index of best cell
Frequency and preamble index of the best cell in terms of preamble RSSI. Last 3 digits are representing the preamble
index.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 87/89


10/10/2019 Nemo Analyze KPI List

WiMAX preamble RSSI selected frequency


WiMAX preamble RSSI
WiMAX preamble RSSI Nth best
WiMAX preamble CINR Nth best
WiMAX preamble CINR
WiMAX preamble delay
WiMAX preamble CINR selected frequency
Channel to interference-noise ratio.
WiMAX preamble delay selected frequency
Scanning configuration
Defines scanning settings.

WiMAX:Link adaptation

WiMAX effective bits per symbol uplink


WiMAX effective bits per symbol downlink
WiMAX effective bits per symbol uplink (mode)
The most common effective bits per symbol value over the reporting period
WiMAX effective bits per symbol downlink (mode)
The most common effective bits per symbol value over the reporting period
WiMAX uplink adaptation parameter distribution
WiMAX uplink adaptation parameter distribution (FF 1)
WiMAX downlink adaptation parameter distribution
WiMAX downlink adaptation parameter distribution (FF 1)
WiMAX modulation uplink
WiMAX modulation downlink

hidden

Handover during LTE IMS voice call


Handovers filtered where call state has passed ALERTING (between CAC and CAD nemo events
Audio quality MOS DL during LTE IMS voice call
Handover U-plane interruption time with HOA type
Aggregated Data Transfer
Aggregated Data
Aggregated RX Level Sub Mean
Aggregated RX Quality Sub Mean
Aggregated RSCP Mean
Aggregated Ec/N0 Mean
Aggregated RSRP Mean
Aggregated RSRQ Mean
Aggregated RS SNR Mean
Aggregated Technology Weight
Aggregated Packet Technology Weight During Data Transfer
Aggregated Bytes Per Second DL Mean
Aggregated Bytes Per Second UL Mean
Session Attach
Aggregated PDP context activation
Aggregated Session Time
Aggregated Voice Call
Aggregated Voice Call Counter
Session Audio Score Mean
Session Attach Setup Time
Session Server Connection Establishment Time

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 88/89


10/10/2019 Nemo Analyze KPI List

iDEN

Domain status
Recorded when service state or mobility information changes.
Channel number
Color code
Frequency
Cell identifier
Adaptation rate
Cutback level
Monitor all flag
Monitor paging subchannel
Interconnect paging subchannel
Packet data paging subchannel
Dispatch paging subchannel
Interleave
Offset
Subslot
Extended color code
RX level
RX level neighbor
SQE
Carrier SQE neighbor
Sync count
Sync count neighbor
Serving system and band
Recorded when channel configuration information changes.
Serving system
Recorded when channel configuration information changes.
Serving band
Recorded when channel configuration information changes.
Push-to-talk state (iDEN)
Recorded when voice call configuration or state changes.
L3 signaling
Recorded when a Layer 3 or an NAS signaling message is sent or received.
Cell reselection
Handover events
Handover attempt
Handover success
Handover failure

iDEN Scanner

RX level
SQE
Noise + interference level
Scanning configuration
Defines scanning settings.

file:///C:/Program Files/Anite/Nemo Analyze/Documentation/AnalyzeKPI.html 89/89

Potrebbero piacerti anche