Overview New Features of Romes 18 - 2 PDF

R&S® ROMES4 Release 18.
2
New Features
R&S® ROMES4 Coverage Measurement Software

Order-No. 1117.6885.04
Contents
1 Introduction .......................................................................................................... 3
2 General Information ............................................................................................. 5
Overall GUI Redesign .............................................................................................................. 5
New Layout of Welcome Page ................................................................................................ 5
Icon size adaptation and Light/Dark mode ............................................................................ 6
Using FTP to transfer crash reports ...................................................................................... 7
Update of Graphic library used by ROMES ........................................................................... 8
Grid View Enhancements ........................................................................................................ 8
3 Basic Views .......................................................................................................... 8

Device Grid View ...................................................................................................................... 8
Configuration Screen Update ................................................................................................. 8
Multiple Signal Configuration ................................................................................................. 9
Line Chart ...............................................................................................................................10
Column Chart .........................................................................................................................11
Range Chart ............................................................................................................................12
Chart Error conditions ...........................................................................................................12
Grid View .................................................................................................................................13
Configuration screen update ................................................................................................13
4 NB-IoT Scanner ................................................................................................. 14

Automatic Channel Detection for NB-IoT ............................................................................14
NB-IoT Scanner Configuration without using MDL ............................................................14
NB-IoT Scanner configuration dialog Overview .................................................................15
In-Band mode .........................................................................................................................19
Guard Band mode ..................................................................................................................21
Stand Alone mode ..................................................................................................................28
No 3GPP Band mode .............................................................................................................29
Position Estimator .................................................................................................................30
NPSS Power and CINR Signals and Events ........................................................................30
NPSS Power and CINR Signals ............................................................................................30
NPSS Power Signal Tooltips .................................................................................................31
The NPSS Power and CINR configuration in Preference settings ....................................32
The NPSS Power and CINR events configuration in the preference settings .................33
NPSS Power and CINR signals in Views .............................................................................34
NSSS Power Signal Expected Range ...................................................................................35
Frame Time of Arrival ............................................................................................................38
Frame Time of Arrivals in Signal tree ..................................................................................39
Frame Time of Arrival Tooltips .............................................................................................39
Rohde & Schwarz ROMES4 release 18.2 1
Frame Time of Arrival signal in Views .................................................................................41
5 5GNR Scanner ................................................................................................... 44

Configuration ..........................................................................................................................44
Top N Pool Configuration......................................................................................................44
Settings Page .........................................................................................................................44
ROMES Signals ......................................................................................................................45
5G NR Scanner Views ............................................................................................................46
Top N View ..............................................................................................................................46
SSS CINR View .......................................................................................................................47
Chart view ...............................................................................................................................47
SSB Performance View..........................................................................................................49
SSB History View ...................................................................................................................49
ROMES Map ............................................................................................................................51
Driver .......................................................................................................................................51
Export ......................................................................................................................................54
Multiple Band Versions .........................................................................................................57
6 LTE Scanner ...................................................................................................... 62

7 NB-IoT Scanner ................................................................................................. 62
8 UMTS Scanner................................................................................................... 62
9 GSM Scanner..................................................................................................... 62
10 TETRA Scanner ................................................................................................. 62
11 TETRA Radio ..................................................................................................... 62
12 3GPP Mobiles .................................................................................................... 62
Support of Exelonix NB-IoT Modules...................................................................................62
SQUAD support in QualiPoc for unrooted phones ............................................................64
13 DQA ................................................................................................................... 65
DQA Jobs for NB-IoT Modules .............................................................................................65
NB-IoT Attach .........................................................................................................................66
NB-IoT Detach ........................................................................................................................66
NB-IoT Ping .............................................................................................................................67
NB-IoT Send UDP ...................................................................................................................67
14 Import / Export functionalities ............................................................................. 68

15 Navigation Views................................................................................................ 68
Route Track Measurement Points ........................................................................................68
New R&S UI Theme for ROMESMAP ....................................................................................69
Representation of satellites per GNSS Technology in GPS Info View .............................70

MapInfo MapX 32-bit version supported..............................................................................70
16 NPA ................................................................................................................... 71
LTE-M Statistics .....................................................................................................................71
Further NB-IoT mobile statistics ..........................................................................................72
NQA Call Table: Display of Call Type and filter on MOC/MTC...........................................74
LTE MIMO 4x4 Tx Count in MIMO Analyzer .........................................................................74
LTE MIMO 4x4 Rank Indicator analysis ...............................................................................75
DQA Ping analysis .................................................................................................................77
DQA Ping test result and KPI split by device ......................................................................78
Memory usage information dialog and customizable alarming ........................................78
Various format and range adaptations ................................................................................80
Adaptation of floating number decimals for power values ...............................................80
Frequency format for values in the UMTS TopN view aligned with other views .............80
RSRQ range for LTE Mobile Statistics/Coverage Cell Statistics aligned with other
views........................................................................................................................................81
1 Introduction
A significant number of improvements and enhancements of existing features have been included in the
recent release of ROMES 18.2.
The table below summarizes the most important features and their benefits.
Feature Benefit Section
Overall GUI Redesign Bringing the refreshed and new, modern overall User
2.1
Experience.
New Layout of Welcome Page Part of the general GUI redesign improving the overall
2.2
design and usability of the entire software.
Icon size adaptation and Advanced tool´s UI scalability improves the overall user
2.3
Light/Dark mode experience.
Using FTP to transfer crash Automatic FTP transfer of crash reports to provide
2.4
reports better visibility for R&D on eventual issues.
Update of Graphic library used Improved performance of the tool when using more
2.5
in ROMES views in parallel.
Grid View Enhancements Enabling more visualisation flexibility in Grid Views. 2.6
NB-IoT scanner ACD Automatic Channel Detection of NB-IoT carriers (all
4.2
operation modes are supported).
NB-IoT position estimator Estimate the site locations of NB-IoT eNodeBs from
4.3
scanner measurements.
NB-IoT scanner primary sync NB-IoT synchronization signal measurements are also
4.4
measurements available for primary synchronization signals.

5GNR Scanning 5GNR scanner measurements on SSB blocks for
5
coverage and beamforming evaluation.
Support of Exelonix NB-IoT The Exelonix NB-IoT Modules are now fully integrated in
Modules ROMES, while offering more comfortable and faster way 12.1
to configure the required tests.
SQUAD speech quality for An additional, for customers more affordable licensing
Qualipoc Unrooted phones option, for speech quality measurements on unrooted 12.2
Qualipoc phones has been introduced.
DQA Jobs for NB-IoT Modules Additional predefined IoT jobs are implemented to cover 13.1
a broader set of IoT Testing Use Cases.
Route Track Measurement Route Track View is enhanced to be able to display also
15.1
Points measurement points.
New R&S UI Theme for A new, dark UI Theme in ROMESMAP, is available from
15.2
ROMESMAP this release.
Satellites per GNSS Better visibility on visible satellites for GPS positioning,
Technology representation in as well as the grouping on GNSS technologies. 15.3
GPS Info View
MapInfo MapX 32-bit version 32-bit version of MapX control is now supported also in
15.4
supported 64-bit MapX module version.
NPA: LTE-M Statistics LTE-M Statistics about CE Level, PRACH, PUSCH
16.1
conditions and QPing results introduced.
NPA: Further NB-IoT mobile Additional NB-IoT analysis results on RTT, eDRX and
16.2
statistics PSM introduced.
NPA: NQA Call Table: Display Improved visualisation of results through filtering on
of Call Type and filter on mobile originated calls (MOC) and mobile terminated 16.3
MOC/MTC calls (MTC).
NPA: LTE MIMO 4x4 Tx Count Improved analysis and problem spots identification for
16.4
in MIMO Analyzer MIMO usage.
NPA: LTE MIMO 4x4 Rank Additional information indicating MIMO Rank for the
16.5
Indicator Analysis improved analysis of the radio performance.
NPA: DQA Ping analysis Improved Ping result visualization and a problem table
creation for Pings that are above a configurable 16.6
threshold.
NPA: DQA Ping test result and Device information included in analysis to better
16.7
KPI split by device distinguish between different results.
NPA: Memory usage Display of the memory usage of the NPA GUI process
information dialog and and occupied space. Additionally, an alarming option is 16.8
customizable alarming available once a certain threshold is reached.
NPA: Various format NPA power floating values, UMTS frequency values in
adaptations TopN View and RSRQ ranges adapted to be consistent 16.9
throughout the toolchain.

2 General Information
Overall GUI Redesign
With 18.2 release, ROMES has been completely redesigned and refreshed with the, modern GUI. The
functionalities, Menus and their position have not been changed, meaning that the organization of the
Views and their sub-categories is left like in earlier releases. The dominant colors are corresponding the
overall visual appearance of Rohde & Schwarz.
The scalability of the new GUI has been brought to the next level, which is realized through the
configurability of the Icons on the top, the adaptation of their size and also the possibility to move out the
Menu Bar and/or Icons Toolbar to gain more visualization space of the measurement views, like shown in
the screenshot below.
New Layout of Welcome Page

With a general GUI redesign for this Version, ROMES Welcome page got a new Layout. As visible in the
screenshot below, the recent Workspaces and recent Measurements are on the left side of the page.
Available Devices are easily visible on the right hand side. All of the mentioned lists have new Icons of the
same size. The handling of the Welcome Page parts is not changed and is a pure UI improvement.

Icon size adaptation and Light/Dark mode
In order to accommodate various user use cases, the customization dialog in Main Menu: Tools /
Customize is removed and the user is able to quickly switch the overall ROMES Theme between Light
and Dark modes. Dark mode has been redesigned for measurements during the night providing the better
visibility and handling in the tool. Multiple themes in parallel are not allowed. The “Night drive mode” is
renamed to just Light and Dark mode. The theme can be switched using Main Menu  View  UI Theme.
Please be aware that Light and Dark Modes are currently not supported in all dialogs and the rest of the
GUI redesign will take place in release 18.3.
In the same submenu, an user may change as well the icon size. This size is then adapted only in the
main toolbar and all other icons are fixed in size. Adaption of the icon size takes place immediately.
The Dark Mode with Large Icons:

Using FTP to transfer crash reports
From this release, in case of the ROMES crash, user is notified with the message/window like below:
The user can create report with further information and description:
There is a possibility to send the crash report by Mail or by automatically uploading it via FTP. If the file is
too large for an e-mail, the corresponding button is greyed out, like in the example above.

Update of Graphic library used by ROMES
ROMES makes use of a third party graphics library (BCGCPro). This library has been updated to version
27.3 to allow better performance of the tool when using multiple views in parallel. The views that currently
use this library include:
- LTE MIMO
- LTE Carrier Aggregation View
- LTE Modulation View
- LTE CA Downlink Performance View
- LTE CA Uplink Performance View
- Mobiles Serving Cell View.
Grid View Enhancements

The following enhancements have been made to the ROMES Generic Grid View:
1) Added support for configuration of a cell as a column chart
2) Added support for configuration of a cell as a range chart.
3) Ability to add multiple ROMES signals to a cell that is configured as either a line chart, column
chart or range chart.
4) Added the current position cursor to line and range charts
3 Basic Views
Device Grid View
Note: the following applies to both the Device Grid View and Grid View. The grid view section will only
contain the screen shots where there is a difference in UI for the different views.
Configuration Screen Update
The device grid configuration screen has been updated to the following entries the cell attributes Display
list
“Standard” – cell configured to display the value of a single signal with optionally a “Bar”, “Color” or
“Trend” attribute.
“Legend” – for cells configured as Line, Column or Range options, there can be a legend for the chart
included to be displayed in the cell.
“Column” – are the signals configured in the cell to be displayed in a column type chart?
“Range” – are the signals configured in the cell to be displayed in a range type chart?

Multiple Signal Configuration
A cell may contain multiple ROMES signals by first configuring the cell as line, column, or range chart.
Multiple signals may then be added to the cell by dragging and dropping the desired signals from the
ROMES signal tree. The signals can also be added changing a cell type from Empty to Signal Value and
add the signals from the cell configuration screen. This screen may be accessed for a cell that has been
previously configured as a line, column or range type by double clicking on that cell.
The signals are added on the screen by either dragging and droping the desired signals from the
“Available Signals” onto the “Selected Signal” tree or by clicing the “>” button to add the signsls. The
maxiumum number of signals that will be allowed to be added are determined by the cell type that is
configured. For Signal and Name and Source cell type only one signal will be allowed to be added. For
Signal Value, Standard Cell types will hava a maximum of one signal allowed. For Line and Column chart
types a maximum of 4 signals will be allowed. For the range chart type a maximum of 8 signals will be
allowed. The user may see the maximum allowed signals for the selected chart type by looking at the text
label next to the “Selected Signals” label.
Once signals have been added to the “Selected Signals” tree they order of the signals my be changed by
selecting a signals and clicking the “Up” or “Down” button to move the selected signal up or down in the
signal order.
Signals may be removed from the cell by with selecting one or more signals in the “Selected Signals” tree
and then clicking the “<” to remove the selected cells. All currently selected signals may be removed from
the cell by clicking the “<<” button.
Note: if a cell contains muliple signals and the cell type is changed to a type that allows for fewer signals
the signals over the maximum number of signals for the newly configured cell type will be automatically
removed.

Line Chart
A cell configured with the Line chart attribute will display the configured signals in a line graph type of
chart. This line chart will track the signal values of a range of 30 seconds of the replay or measurement.
The displayed black line represent the current time of the replay or measurement. For replay with file
scanning the graph will show a range of -15 seconds to plus 15 seconds from the current time of the
replay. This range may be changed by changing the “Trending Seconds” setting on the configuration
screen. For measurements and replays without file scanning the graph will by default show a range of -27
seconds to + 3 seconds ( range can be changed by changing Trending Seconds” setting on the
configuration screen the low end of the range will be – 90% of the configured value and the high end will
be 10% of the configured value).
If all selected signals are of the same type then only one Y axis will be configured for the chart.
If more than one type of signal is configured then each signal will have its own axis label on the chart.
The display of the chart legend is optional and may hidden by unselecting the “Legend” attribute from the
Cell Attributes Display Type List on the configuration screen

Column Chart
A cell configured with the “Column” attribute will display the current value of the configured signals in a
column type of chart.
If all selected signals are of the same type then only one Y axis will be configured for the chart
If more than one type of signal is configured then each signal will have its’ own axis label on the chart
The display of the chart legend is optional and may hidden by unselecting the “Legend” attribute from the
Cell Attributes Display Type List on the configuration screen

Range Chart
A cell configured with the Range chart attribute will display the configured signals in a range graph type of
chart. This type of chart will track a signals change in state with bar showing encompassing the time of
signal changed to that state till the time the signal changed to a different state. The range chart will track
the signal values of a range of 30 seconds of the replay or measurement.
The displayed black line represent the current time of the replay or measurement. For replay with file
scanning the graph will show a range of -15 seconds to plus 15 seconds from the current time of the
replay. This range may be changed by changing the “Trending Seconds” setting on the configuration
screen. For measurements and replays without file scanning the graph will by default show a range of -27
seconds to + 3 seconds ( range can be changed by changing Trending Seconds” setting on the
configuration screen the low end of the range will be – 90% of the configured value and the high end will
be 10% of the configured value).
Chart Error conditions
To correctly draw the column, line, or range chart, the view requires a minimum amount of space. A single
cell is typically not sufficient to allow this. The minimum merge range of cell is 5x2 to allow for a type chart
to drawn. If the user attempts to change a cell that has a merge range of less than 5x2 to a line, column or
range chart the following error message will be presented:
There are also occasions where a chart that is set to the minumum of 5x2 cell can still not be shown
based on other configuration factors such as the length of the signal names, and presence of a legend. In
this condition once the view is taken out of configuraiton mode the cell will show a “Chart N/A” message in
place of the chart and the cell background will be changed to red.
Grid View
Configuration screen update
The grid configuration screen has been updated to the following entries the cell attributes Display list:
“Standard” – cell configured to display the value of a single signal with optionally a “Bar”, “Color” or
“Trend” attribute.
“Legend” – for cells configured as Line, Column or Range options, there can be a legend for the chart
included to be displayed in the cell.
“Column” – are the signals configured in the cell to be displayed in a column type chart?
“Range” – are the signals configured in the cell to be displayed in a range type chart?
For an explanation of the new elements of the configuration sceen see the previous “Device grid view”
section of this document.

4 NB-IoT Scanner
Automatic Channel Detection for NB-IoT
The ACD feature of ROMES now also supports NB-IoT. The ACD for NB-IoT requires an active LTE ACD
on the same bands. ROMES checks the configuration at the start of the measurement and will not start
the measurement in the case of a misconfigured ACD (LTE bands do not match with NB-IoT bands).
If a LTE ACD is active it will always activate automatically all active NB-IoT ACD bands for the LTE ACD.
This means for each band which is activated in the NB-IoT ACD, the LTE ACD will also perform an ACD
search and report the results.
The NB-IoT ACD supports all three NB-IoT modes and will search for Inband, Guardband and Standalone
channels.
It is recommended to use the ACD wizard to set up an ACD task. Using the wizard ensures that the LTE
ACD is configured accordingly. The ACD will always search for NB-IoT carriers in all three NB-IoT modes.
If required, the modes can be adapted on the NB-IoT scanners’ ACD configuration page.
The found channel is visualized in the ACD View as an orange rectangle.
NB-IoT Scanner Configuration without using MDL

The MDL is one of the parameters for configuring NB-IoT scanner frequency.
Using MDLs is not straightforward. The MDL will not be used in new NB-IoT scanner configuration shown
below (replaced by f, f2).
This document will focus on non-virtual channel configuration for the In-Band, Guard Band and Stand
Alone modes.
All verifications will not be enabled if “No 3GPP Band” mode is selected

NB-IoT Scanner configuration dialog Overview
4.2.1.1 Launch NB-IoT Scanner configuration dialog
To launch NB-IoT Scanner Configuration dialog:

1. Double clicking TSME NB-IoT button shown below to launch NB IoT Scanner Configuration dialog.
Then double click Open Configuration button to launch the NB-IoT Scanner Configuration dialog
2. It can also be launched from main menu, Hardware -> Add/Remove…Ctrl+H

Then select a driver, TSME NB-IoT or TSMW NB-IoT from the list.
Click OK to accept the selection.
Screenshot below shows NB-IoT Scanner Configuration dialog box.

4.2.1.2 NB-IoT Scanner configuration dialog Layout
By default, the Nb-IoT Scanner Tab is selected on the left pane.

The right pane shows a Channel Grid with a few buttons at bottom of the screen.
The grid Channels column has three choices:
 Disabled
 Enabled
 Virtual
Following configuration discussion is for Enabled channels.
Other related columns:
 Name: the name of the channel;
 f[MHz]: the primary center frequency of the NB-IoT channel;
 f2[MHz]: the secondary center frequency of the NB-IoT channel;
 NB EARFCN: the NB EARFCN;
 Band: the NB-IoT band, will be prepopulated with all valid, NB-IoT supported bands;
 Mode: Measurement mode. The possible modes are: In-Band, Guard Band and Stand Alone
mode;
4.2.1.2.1 Open Configuration Dialog the very First Time

A channel row is populated with default parameters.

4.2.1.2.2 Configuration dialog opened with preconfigured channels
If some channels have already be configured, opening the configuration dialog will show all the
preconfigured channels.
The screenshot below shows a configuration dialog with previously configured channels
4.2.1.2.3 Buttons for configuring channels

Buttons are available for Adding, Removing or Cloning channels
 Add – Add a new channel with default parameters populated
 Remove – Remove the highlighted channel;
 Clone – Clone / copy the highlighted channel
4.2.1.2.4 Measurement Modes
NB-IoT scanner configuration has three modes:

1. In-Band mode
2. Guard Band mode
3. Stand Alone mode
In both, In-Band and Guard Band modes, a note is displayed next to the Clone button:
Note: To enter the frequency please click Frequency, EARFCN or Band column.
When changing mode to a different one, the channel record parameters will be reinitialized,
the frequency in one mode may not be valid in other mode.
In In-Band and Guard Band modes, if Band is not “No 3GPP Band”, the configuration helper
dialog must be used to configure the NB-IoT frequencies.
In-Band mode
In In-Band mode, the NB-IoT center frequencies are located inside LTE band and occupy predefined
resource blocks.
4.2.2.1.1 Inband Frequency Calculator helper dialog
1. In In-Band mode, clicking f[MHz], f2[MHz], EARFCN or Band will launch Inband Frequency
Calculator helper dialog box.
2. Entering a valid LTE EARFCN, the corresponding LTE Bandwidth dropdown will be populated with all
possible valid band widths.
The NB-IoT Frequency and NB-IoT EARFCN will be calculated and displayed.

3. If the entered LTE EARFCN is invalid, the LTE Bandwidth and Used PRB for NB-IoT will be cleared.
The NB-IoT Frequency and NB-IoT EARFCN will show “---“.
The Apply button will be disabled.
4. After having entered a valid LTE EARFCN, the user can then select a bandwidth from the LTE
Bandwidth dropdown list. The Used PRB for NB-IoT will be populated with all possible valid
Resource Blocks.
5. Select a PRB from the Used PRB for NB-IoT, the NB-IoT frequency and NB EARFCN will be
calculated and displayed.
6. Click Apply button to accept the frequency or Cancel button to cancel the selection. In either case, the
dialog will be dismissed.
7. If the Apply button is clicked, the calculated frequency and NB-IoT EARFCN will be populated to
f{MHz], NB EARFCN and Band columns of the channel accordingly and, f2[MHz] will be .00.

Guard Band mode
In Guard Band mode, the NB-IoT center frequencies are located on the edges of the LTE band.
It is possible that for a given NB EARFCN, there may be two valid NB-IoT frequencies, says fa and fb.
Where:
fb - fa = 15KHz
The grid column f2[MHz] shows the second frequency if any.
4.2.3.1 NB Guard Band Frequency Calculator Helper dialog
1. In Guard Band mode, clicking f[MHz], f2[MHz], EARFCN or Band will launch NB Guard Band
Frequency Calculator helper dialog box.

2. The NB Guard Band Frequency Calculator helper dialog has two buttons:
 Use LTE bandwidth – LTE bandwidth will be used to calculate NB-IoT frequenci(es).
 Use NB EARFCN – NB EARFCN will be used to calcualte NB-IoT frequenci(es).
Clicking the button will switch the calculation mode
4.2.3.2 Bandwidth mode
Clicking Use LTE bandwidth button, the calculation switches to Bandwidth Mode.
1. Entering a valid LTE EARFCN, the corresponding LTE Bandwidth dropdown will be populated with all
possible valid bandwidths.

2. If the entered LTE EARFCN is invalid, the LTE Bandwidth dropdown list will be cleared.
The Apply button will be disabled and the user can still click ‘Cancel’ button.

3. With a valid LTE EARFCN, user can select a Bandwidth from the LTE Bandwidth dropdown list. The
NB EARFCN, frequency 1, frequency 2 dropdown list will be populated with all possible valid
combination of NB EARFCN, frequency 1, frequency 2.
The dropdown list is of following format:

NB EARFCN, frequency 1, frequency 2
Where
NB EARFCN is the NB-IoT channel number
Frequency 1 is the calculated primary frequency based on the LTE EARFCN
Frequency 2 is the calculated secondary frequency based on the LTE EARFCN
The frequency 1 will be populated to f[MHz] grid column and frequency 2 will be populated to f2[MHz]
grid column if it is available.
E.g. the highlighted selection in screenshot above,
NB EARFCN = 521
Frequency 1 = 2162.0925 MHz
Frequency 2 = 2162.1075 MHz
--- means the second frequency is not available.
If two frequencies, (i.e. fa and fb and fb > fa) are available, it must satisfy the following formula:
fb - fa = 15KHz
Both frequencies will be sent to the scanner and scanner will try both and detect and use the correct one.
The correct frequency will be observed during measuring and replay in such as BCH tree view and Top N
pool Center Frequency signal and list.
Both frequencies will also be reported in the measurement file system info box as shown in list below.
User can highlight the measurement file to see the system information.
If secondary frequency is not configured, Center Frequency2 will display.
Count of all measured channels: 2

Selected Channels:
Channel Name: NB-IoT Channel 1
LTE Band: Band 1 (FDD)
NB EARFCN: 53
Center Frequency: 2115292.5 kHz
M[DL]: -1.0 (Informative only)
Center Frequency2: 2115307.5 kHz
M[DL] 2: 1.0 (Informative only)
Mode: NB Guard Band
max. Delay Speed: 4 µs
max. Speed: 100 Km/h
Rate per second: 10.0

BCH Demod: MIB(Rep: 1.000 s);SIB1(Rep: 1.000 s);SIB2(Rep: 1.000 s);SIB3(Rep: 1.000
s);SIB4(Rep: 1.000 s);SIB5(Rep: 1.000 s);SIB14(Rep: 1.000 s);SIB15(Rep: 1.000 s);SIB16(Rep:
1.000 s);SIB20(Rep: 1.000 s);SIB22(Rep: 1.000 s);

NB EARFCN: 167
Mode: NB Guard Band

BCH Demod: MIB;SIB1;SIB2;SIB4;SIB5;SIB14;SIB15;SIB16;SIB20;SIB22;
4. Click Apply button to accept the frequencies or Cancel button to cancel the selection. In either case,
the dialog will be closed.
5. If Apply button is clicked, the calculated frequencies, NB EARFCN and Band will be populated to
f{MHz], f2[MHz], NB EARFCN and Band columns of the channel accordingly.
4.2.3.3 NB EARFCN mode
Clicking Use NB EARFCN button, the calculation switches to NB EARFCN mode.

With a valid LTE EARFCN
1. Entering a valid NB EARFCN, the corresponding NB-IoT frequency 1 and NB-IoT frequency 2 are
calculated and displayed. Note that the NB-IoT frequency 2 may show “---“

2. If the entered NB EARFCN is invalid, the NB-IoT frequency 1 and NB-IoT frequency 2 will be
cleared.
The Apply button will be disabled. User can still click Cancel button though.

3. With a valid LTE EARFCN and NB EARFCN, one or two frequencies may displayed
Screenshot above shows two frequencies scenario

NB-IoT Frequency 1 = 2134.2925 MHz
NB-IoT Frequency 2 = 2134.3075 MHz
--- means the second frequency is not available with NB EARFCN = 244.
If two frequencies, say fa and fb and fb > fa, are available, it must satisfy following formula:
fb - fa = 15KHz
Both frequencies will be sent to the scanner and scanner will try both and detect and use the correct one.
The correct frequency will be seen during measuring and replay in, such as BCH tree view and Top N pool
Center Frequency signal and list.
Both frequencies will also be reported in the measurement file system info box as shown in list below. The
user can highlight the measurement file to see the system information.
If secondary frequency is not configured, Center Frequency2 will display.
Count of all measured channels: 2

Selected Channels:
NB EARFCN: 53
Mode: NB Guard Band

BCH Demod: MIB(Rep: 1.000 s);SIB1(Rep: 1.000 s);SIB2(Rep: 1.000 s);SIB3(Rep: 1.000
s);SIB4(Rep: 1.000 s);SIB5(Rep: 1.000 s);SIB14(Rep: 1.000 s);SIB15(Rep: 1.000 s);SIB16(Rep:
1.000 s);SIB20(Rep: 1.000 s);SIB22(Rep: 1.000 s);

NB EARFCN: 167
Mode: NB Guard Band

BCH Demod: MIB;SIB1;SIB2;SIB4;SIB5;SIB14;SIB15;SIB16;SIB20;SIB22;
4. Click Apply button to accept the frequencies or Cancel button to cancel the selection. In either case,
the dialog will be closed.
5. If Apply button is clicked, the calculated frequencies, NB EARFCN and Band will be populated to
f{MHz], f2[MHz], NB EARFCN and Band columns of the channel accordingly.
Stand Alone mode
In Stand Alone mode and Band is not ”No 3GPP Band”, column f[MHz], EARFCN and Band are editable.
The f2[MHz] is still read only.
If any of the f[MHz], EARFCN or Band changes, the other two will be recalculated accordingly.
If user changes the frequency, new EARFCN and Band will be recalculated:
4.2.4.1 Frequency Associated with Unique Band
If the entered frequency is associated with a valid, NB-IoT supported and unique NB EARFCN, the new
frequency will be accepted and the calculated NB EARFCN, Band NB EARFCN and Band will be applied.
4.2.4.2 Frequency Associated with Multiple Bands

If the entered frequency is valid and supports NB-IoT, but associated with multiple bands, e.g. Band 1 and
Band 4 share the same starting frequency, then a Bands Helper dialog displays:
User selects an entry from the list and click Apply to accept it.
The selected Band and NB EARFCN will be populated.
If user click Cancel button, the first choice of the list will be applied.
4.2.4.3 Frequency Invalid

If the new frequency does not support NB-IoT or is invalid, EARFCN column shows “---“, and Band will be
set to “No 3GPP Band”.
No 3GPP Band mode
The Band column has a special value: “No 3GPP Band”. If this value is selected or set, the channel
column f[MHz], EARFCN can be manually changed without validation or recalculation.

Position Estimator
With ROMES 18.2, the Position Estimator also supports NB-IoT. The user can select in the Position
Estimators configuration dialog, if positions of NB-IoT cells shall be estimated. The configuration also
checks if the settings of the NB-IoT scanners are optimal for the Position Estimator.
The results of the Position Estimation is shown in the NB-IoT BCH View and the ROMES Map View.
Note: The NB-IoT scanner requires a lot RF time of the scanner device. Thus the scanner measurement
rates for other technologies may drop significantly, what can lead to worse Position Estimation results as
you would have gotten without the NB-IoT scanner.
NPSS Power and CINR Signals and Events
NPSS Power and CINR Signals
NPSS Power and CINR signals have been added to Top N Pool and Template Signal trees.
To find the signals related to primary sync signal measurements in signal tree, enter NPSS in the
available Signals search box to show the related signals.

NPSS Power Signal Tooltips
The NPSS Power tooltips describe the measurement value.

The NPSS Power and CINR configuration in Preference settings
Like in other technologies, the user can change the color and value scale.

The NPSS Power and CINR events configuration in the preference settings
Like in other technologies, the user can configure events for NPSS related signals.

NPSS Power and CINR signals in Views
1. NPSS Power and CINR signals can be added to Alphanumeric and TopN views.

2. NPSS Power and CINR Signals are optional by default in Top N View.
NSSS Power Signal Expected Range

NSSS Power signal expected range is now -150 to 10 (in Power Frequency, Template and Top N Pool
signal trees).

Value descriptions in the tooltips:

Frame Time of Arrival
Frame TOA (Time of Arrival) or Frame Arrival Time, or Frame Time, is calculated using
 PPS (Pulse Per Second), Offset to PPS
Or
Internal Block (receiver based) time and offset
 Frame type (FDD or TDD)
There are two type of frame Time of Arrival: GPS PPS ToA and Block Time ToA
When using GPS PPS, the value is a shift/drift pertaining to the RF grid, the value is always less than the
frame length.
When using Block Time and Offset, the values are generated by internal clock.
The calculation:
 The calculation formula for FDD type of frame
Frame Time = ((Internal TOA + 5 ms) modulo 10 ms ) - 5 ms
 The calculation formula for TDD type of frame
Frame Time = ((Internal TOA + 2.5 ms) modulo 5 ms ) – 2.5 ms
Where
 ms is millisecond
 Internal TOA is PPS + ArrivalTimeOffset or Block Time and Offset
 Dislay unit is millisecond
 Modulo is the operation that takes the remainder of a division of two double operands.
 5 ms and 10 ms are frame lengths of FDD and TDD frames respectively
Notes:
1. ROMES 18.2 or higher must be used to record and show ToA Time. Replaying early recorded
measurement file will show empty or ”---‘ for those signals;
2. The signal is available in Top N Pool and Template signal trees.
3. The GPS PPS values require GPS antenna and module and the signal values take a little bit time
(probably a minute) to be available
4. The frame ToA signals do not have events.
5. The ToA signals by Block Time will always be available if ROMES 18.2 or higher is used.

Frame Time of Arrivals in Signal tree
Frame Time of Arrival Tooltips
1. Top N Pool Frame Time of Arrival tooltips describing the measurement values.

2. Power Frequency Frame Time of Arrival tooltip describing the measurement values.
3. Template Frame Time of Arrival tooltip describing the measurement values.

Frame Time of Arrival signal in Views
4.6.3.1 Frame Time of Arrival signals in Alphanumeric and TopN views

Frame Time of Arrival signal can be used in Alphanumeric and TopN views.

Later both will be available (after GPS PPS detection).
4.6.3.2 Frame Time of Arrival Signal is optional

Frame Time of Arrival signals are optional by default in Top N View

4.6.3.3 Frame Time of Arrival Signal in Preference dialog
The ToA signal color scale customization is disabled.

5 5GNR Scanner
Configuration
Top N Pool Configuration
The Top N Configuration Page is the Standard Configuration Page for TopNs. We have six different TopN
Values:
RSRP, RSRQ and CINR, each per Beam and per Cell
The values per cell are taking into account all beams of the cell, which fulfill the thresholds specified on
the Settings Page of the 5G NR Technology. The linear average value over all beams is fed into the TopN
algorithm.
Settings Page
The Settings Page allows the user to specify the SS-PBCH-Block Power of the cells. This value is used for
calculating the Pathloss Values.
The Threshold Values for Cell Ranking are used for the Cell TopN Ranking.

ROMES Signals
The 5G NR Technology provides signals for the TopN pools and Template Signals which shall be used to
get the measurement parameters of a specific gNodeB

5G NR Scanner Views
Beam Text: The beam is visualized as follows:
If beam value is available: “beamIndex”, e.g. “5”
If beam is not available, but beamIndexMod8 is available: “**beamIndexMod8”, e.g. “**3”
If none is available: “-“
Top N View
The Top N View is a standard TopN View as used by all Scanner Technologies.
The content of Beam column depends on the ranking value of the selected TopN pool. If the TopN Pool is
a Beam related pool, the beam column shows the beam text. If the TopN Pool is cell related, the beam
column show the beam text followed by the TopN related measurement value for all beam taken into
account (averaging over beams matching with the threshold values).
SSS CINR View
The CINR View shows the CIR of the different beams:
Chart view
The Chart View shows the n best beams over all (independent from TopN Pool configurations). The view
can be filtered by PCI and Frequency.

The View shows all beams sorted by the selected sorting algorithm. The View is independent from any
TopN Pools, and gets all data unsorted. The sorting is done in the view itself. The background color of the
columns corresponds to the PCI and the color of the column to the BeamIndex.
The Filter accepts string of the following format:

[Beam@]PCI;[Beam@]PCI;…
Please Note,that the beam value of the filter works as follow:
1. If the beam index is available the beam is accepted only if the beam index matched the filter
value
2. If the beam index is not available
a. If the beam index mod 8 is available the beam is accepted only if the beam index mod 8
matched the filter value
b. If the beam index mod 8 is not available the beam is not accepted
Examples for Filters:
449 All beams of gNBs with PCI 449 are shown
31@449 Only the beam 31 of PCI 449 is shown
449;12@1005 All beams of gNB with PCI 449 and the beam 12 of PIC 1005 are shown
Note: The Chart View is not connected to the TopN Pools. It sorts the reported beams every time new
measurement values are reported by SS-SINR.

SSB Performance View
The user can select the TopN Pool, which has to be visualized by pressing the according blue button on
the upper left corner. Only TopN Pools, which are based on cell specific signals, are applicable for this
view.
The left part of the view shows the best n members of the pool. For each member, the background column
in the color of the corresponding PCI visualizes the average value. In the front m bars for the m best
beams of the cell are drawn in the color of the Beam Index.
N and m are configurable
On the right chart, the values of the n best cells are drawn over time. The background color is correspond
to the PCU of the best member (Top1).
SSB History View

The history view shows the Top N PCIs and beams over time. It requires a cell specific Top N Pool, which
can selected in the upper left corner. For each TopN Cell, the band, GSCN, PCI and best SSB is shown.

The Maximum number of Top N Cells can be configured, range from 1 to 6.
The max number of Beam Indexes can alas be configured, range from 1 to 5.

ROMES Map
The supports 5G NR currently with an underlay for the scanner data. The inner underlay represents the
PCI, the outer underlay the Beam Index of the Top1 of the selected TopN Pool. Like in other technologies,
any signal can be added to the map (by drag and drop or the configuration dialog) which becomes the
innermost layer.
Driver
5GNR is a new scanner driver, which can be loaded from the hardware configuration page.

The configuration page is similar to the other scanners.
The user can edit the following columns:

 Name: user name of channel
 SSref: A popup dialog appears which checks the validity of the given frequency and offers the
possible GSCN, bands and Patterns. The user has to select one of those possibilities. By pressing
Apply, these settings will be applied to the channels configuration.

While the user is entering the digits of the frequency, the combo box will show all valid settings,
which are close to the given frequency.
If the entered frequency matches an SSref, the matched item will be selected and displayed
If the entered frequency does not match any SSref in the list, the one just below the entered
frequency will be selected and displayed.
If the entered frequency is below all possible SSref, the first available item will be selected and
displayed.
 Band/GSCN/SSB Pattern: A popup dialog appears, which checks the validity of the given GSCN,
and offers the possible frequencies, bands and patterns. The user has to select one of those
possibilities. By pressing Apply, these settings will be applied to the channels configuration.
While the user is entering the digits of the GSCN, the combo box will show all valid settings, which
are close to the given GSCN.
If the entered GSCN matches a GSCN in the list, the matched item will be selected and displayed
If the entered GSCN does not match any GSCN in the list, the one just below the entered GSCN
will be selected and displayed.
If the entered GSCN is below all possible GSCN, the first available item will be selected and
displayed
 SSB Periodicity: The user has to select, which periodicity of the SSB shall be assumed by the
scanner
 Rate: Max. measurement rate for this channel
 Advanced: Select Open to open the advanced settings for the channel.
While the normal mode checks, if the frequency is valid (TS38.101) and if the selected Case applies for
selected band, the use may switch to an “expert mode”, which allows the user to enter any frequency and
combination of values. No validation is available in expert mode. Band and GSCN do not apply in the
expert mode.
To enable the export mode open the channels advanced options dialog and check the “Expert Input
Mode” option.
The configured channel information will be saved in measurement file.
Export
The Scanner Data Transmitter Export Module supports the both CIR Exports and Raw Data Export for 5G
NR.
Select 5G NR for the Scanner Raw Data:
The raw export module generates csv a file with the follow columns
Date;Time;UTC;Latitude;Longitude;Altitude;Speed;Heading;#Sat;GSCN;SSRef;Band;PCI;Beam;BeamMo
d8;RSSI;SS-SINR;SS-RSRP;SS-RSRQ;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;449;;;-86.8;15.5;-76.8;-4.7;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;449;;;-86.8;20.1;-76.9;-4.1;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;1005;33;1;-86.8;16.5;-84.3;-5.3;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;449;;;-86.8;16.2;-78.6;-3.4;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;1005;2;2;-86.8;14.6;-73.4;-3.8;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;779;;;-86.8;20.3;-78.1;-3.6;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;779;;;-86.8;16.6;-78.1;-4.6;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;336;41;1;-86.8;16.6;-76.7;-5.1;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;892;;6;-86.8;16.7;-76.3;-4.2;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;336;10;2;-86.8;14.5;-76.3;-4.3;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;892;;7;-86.8;14.5;-76.8;-5.9;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;336;43;3;-86.8;9.8;-77.9;-3.3;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;892;;0;-86.8;14.8;-75.9;-3.2;
02.07.2018;15:17:00.993;;;;;;;;24400;28155360000;257;1005;0;0;-86.8;16.2;-84.8;-5.8;
02.07.2018;15:17:01.093;;;;;;;;24400;28155360000;257;449;;;-86.4;15.3;-78.5;-4.1;
CIR export data

Timestamp;Longitude;Latitude;Color;PCI;Beam;Power [dBm];P total [dBm];SSRef[MHz];Max. Delay
[µs];Time Delta [µs];BTS ID;
782 ms;-;-;;1005;0;-79.46;-77.90;26738.40;2.01;1.66;64192960;
782 ms;-;-;;1005;33;-73.09;-71.47;26738.40;2.71;1.50;192971;
782 ms;-;-;;1005;2;-75.86;-73.83;26738.40;1.74;0.96;192982;
782 ms;-;-;;449;-;-82.08;-80.83;26738.40;2.12;0.00;86241;
782 ms;-;-;;449;-;-96.03;-95.87;26738.40;1.32;0.68;64086252;
782 ms;-;-;;449;-;-77.08;-75.23;26738.40;2.38;1.30;86263;
782 ms;-;-;;892;**6;-72.75;-71.48;26738.40;1.74;0.00;171266;
782 ms;-;-;;892;**7;-70.13;-70.12;26738.40;1.52;1.33;171277;
782 ms;-;-;;892;**0;-92.46;-90.74;26738.40;2.52;1.50;171288;
782 ms;-;-;;336;41;-88.10;-85.13;26738.40;1.88;0.00;64547;
782 ms;-;-;;336;10;-77.71;-77.31;26738.40;2.14;0.93;64558;
782 ms;-;-;;336;43;-96.60;-94.96;26738.40;2.35;0.44;64569;
782 ms;-;-;;779;-;-83.92;-82.74;26738.40;0.88;0.00;149572;
782 ms;-;-;;779;-;-75.82;-75.56;26738.40;2.10;0.58;149583;
882 ms;-;-;;1005;0;-73.96;-73.04;26738.40;2.60;1.60;64192960;
...
CIR peak export data

Timestamp;Longitude;Latitude;Color;PCI;Beam;SS-Ref [MHz];Power [dBm];P total [dBm];Delay
[µs];Match.Guard.Per.;BTS ID;
782 ms;-;-;;1005;0;26738.40;-82.52;-77.90;2.01;0/0 (0.00%);64192960;
782 ms;-;-;;1005;0;26738.40;-81.67;-77.90;1.76;0/0 (0.00%);64192960;
782 ms;-;-;;1005;0;26738.40;-82.18;-77.90;0.83;0/0 (0.00%);64192960;
782 ms;-;-;;1005;0;26738.40;-83.23;-77.90;0.35;0/0 (0.00%);64192960;
782 ms;-;-;;1005;0;26738.40;-80.58;-77.90;1.66;0/0 (0.00%);64192960;
782 ms;-;-;;1005;33;26738.40;-73.92;-71.47;1.79;0/0 (0.00%);192971;
782 ms;-;-;;1005;33;26738.40;-76.19;-71.47;2.71;0/0 (0.00%);192971;
782 ms;-;-;;1005;33;26738.40;-76.23;-71.47;1.52;0/0 (0.00%);192971;
782 ms;-;-;;1005;33;26738.40;-74.44;-71.47;1.21;0/0 (0.00%);192971;
782 ms;-;-;;1005;33;26738.40;-73.58;-71.47;2.35;0/0 (0.00%);192971;
782 ms;-;-;;1005;2;26738.40;-76.74;-73.83;0.78;0/0 (0.00%);192982;
782 ms;-;-;;1005;2;26738.40;-77.88;-73.83;1.74;0/0 (0.00%);192982;

782 ms;-;-;;1005;2;26738.40;-76.41;-73.83;1.22;0/0 (0.00%);192982;
...
Multiple Band Versions

1. The 5G Scanner supports two band specification versions: TS 38 101 Ver 15.1.0 and TS 38 101 Ver
15.2.0.
The band version can be selected in “Tec for 5G NR Scanner dialog”.
From main menu, Technologies -> Tec for 5G NR Scanner, and then choose from 5G Band Version
dropdown list.
2. When replaying a measurement file that contains a different band version, the band version will be
changed to replay the measurement file properly, and it will switch back when the measurement file is
closed.
3. The band version will be locked if
a. A measurement file is opened with a different band version;
Close the measurement file will unlock it
b. Channels are configured using 5G scanner configuration dialog;
Removing the scanner driver from hardware menu will unlock it
When band version is locked, it cannot be changed in TEC for 5G NR Scanner dialog and the reason
is displayed.
Band version locked by opened measurement file:
Band version locked by configured scanner channel:

4. When band version is locked by scanner channel, open measurement file will be either disabled or
canceled with a popup warning dialog
Open button is disabled:

When try to open the file directly, following popup displays

5. When band version is locked by an opened measurement file with different band version, 5G NR
Scanner configuration will be disabled

6 LTE Scanner
7 NB-IoT Scanner
8 UMTS Scanner
9 GSM Scanner
10 TETRA Scanner
11 TETRA Radio
12 3GPP Mobiles
Support of Exelonix NB-IoT Modules
The following Exelonix Modules are now supported in ROMES.
 R410M (Qualcomm Chipset) – also officially reselled by Rohde & Schwarz
 N211 (Neul Chipset)
These UEs now offer also Band Forcing in the UEs configuration dialog. Please note, that band forcing
requires a reboot of the UE. It is recommended to force the UE before doing the measurement, and not as
part of the measurements configuration.
Note: If the Qualcomm R410M device has been added to ROMES by using the Qualcomm Wizard, you
may have to remove the corresponding entry from the file “My ROMES\ Configuration\ QualcommMobiles
V462.xml”, in order to get access to the new features.

These modules now also offer preconfigured DQA Jobs, which allow to do the following tests (note that
one test is chipset depndant):
Job R410 N211
NB-IoT Attach Available Available
NB-IoT Detach Available Available
NB-IoT Send UDP Available Available
NB-IoT Ping Not available Available

SQUAD support in QualiPoc for unrooted phones
Speech quality MOS can now be performed also based on SQUAD license, together to the already
supported POLQA license. During the QualiPoc installation for Unrooted phones in ROMES, SQUAD
drivers and libraries will be also installed during the driver loading process.
This is necessary to perform speech quality tests with MOS on unrooted phones, when a SQUAD license
is available on the phone.

13 DQA
DQA Jobs for NB-IoT Modules
New Jobs for Exelonix NB-IoT Modules have been integrated. All NB-IoT Jobs do run on the module and
are commanded by AT commands. No windows IP stack, modem or network connection is involved in
these tests.
As these tests are all based on AT commands, the results can be found in the GSM Signal Branch.
Note: AT Commands are the basic communication method to 3GPP modules, starting with GSM.

The DQA Message View show detail of the current tests.
NB-IoT Attach
The Attach job switches on the modules and commands the module to attach to a specific network,
defined by MCC and MNC.
The may either wait until AT+CGATT returns 1 or continue immediately after having sent out the
commands.
NB-IoT Detach
The Detach Job switches off the module.

NB-IoT Ping
The NB-IoT Ping job uses proprietary AT commands to send pings from the module to the specified IP
address. The user can either specify a maximum amount of pings or a duration of the test.
The test is validated as OK if more than 50% of the pings are successful.
NB-IoT Send UDP
This job sends UDP packets with the content of Message to a specific IP address and port. The format to
specify address and port is: <IP address>:<Port>

If the server is supposed to send back some byte, the job can wait for this response.
14 Import / Export functionalities
15 Navigation Views
Route Track Measurement Points
Route Track View is now able to display points instead of lines. By using the Route Track View context
menu, a configuration dialog can be opened and from section <Value visualizing>, through <Signal values
as circle> option, an additional way of visualizing can be configured.
After the rescan, the Route Track will be displayed as single circles for each measurement point.

New R&S UI Theme for ROMESMAP
Together with the refreshed light theme, the Dark UI Theme is available in the ROMESMAP:
1. UI Theme light:
2. UI Theme Dark:

Representation of satellites per GNSS Technology in GPS Info
View
In GSP Info view, there are further information on satellites and their grouping per GNSS technology. User
is able to see the amount of visible satellites, as well as the further breakdown depending on the GNSS
technology.
MapInfo MapX 32-bit version supported

MapInfo has discontinued supporting MapX product. ROMESMAP engine has been upgraded to 64-bit
version, however 32-bit version will be supported through the registry modification. It has to be kept in
mind, that R&S is not able to guarantee this functionality.
The MapInfo MapX module is a 32bit ActiveX control, to enable the 64bit ROMESMAP/MapXPlugin using
this 32bit module, after Romes installation finished you have to modify the registry.
For this you will find two registry files located in:
C:\ProgramData\Rohde&Schwarz\My ROMES\MapInfoReg
Double click both reg files.
Now start Romes, open the Route Track View, from Route Track main menu
select: <Import – MapInfo Layer> and import a MapInfo GeoSet.

16 NPA
LTE-M Statistics
NPA has been enhanced to provide the analysis on specific LTE-M (eMTC) parameters. The results are
aggregated (like in NB-IoT) on LTE-M specific parameters. Following statistic is available:
- CE level (example shown in the screenshot below)
- PRACH Final TxPower
- PRACH Message Results
- PRACH Preamble (MSG1) Transmission Count
- PRACH Number of Repetition
- PRACH Final TxPower vs. MSG1 Transmission Count
- PRACH Final TxPower vs. Number of Repetition
- PUSCH TxPower / Repetitions
- PUSCH TxPower
- PUCCH TxPower
- PUSCH Average Repetitions
- eMTC Layer 1 (RSRP, RSRQ, SINR) grouped by CE level
- QPing/NPing Statistics: RTT, Result, Retries grouped by CE level

Example of PRACH LTE-M statistic in NPA:
Further NB-IoT mobile statistics

Additional IoT analysis has been implemented in NPA from this release:
1) Ping Round Trip Time (RTT): added to the result page of NB-IoT Throughput Analysis
2) The actually used eDRX configuration: it is read from the EMM_Attach_Accept message and
corresponding eDRX statistic is displayed on the result page NB-IoT Mobile statistics within
the tab CE Level / eDRX / PSM:

3) Power Save Mode (PSM): aggregated to a list showing the power save duration information

NQA Call Table: Display of Call Type and filter on MOC/MTC
The call list now includes an additional column showing more information on call type:
- mobile originated calls (MOC)
- mobile terminated calls (MTC).
A context filter allows to filter on a specific call type:
The filtering option is also available on the result page for speech quality:
LTE MIMO 4x4 Tx Count in MIMO Analyzer

The MIMO analyzer was extended with the Tx Antenna count from the MIB of each LTE cell. This provides
new possibilities in analyzing the MIMO performance.
The map at the page “LTE MIMO Problems” has a new layer which shows the Tx Antenna count of the
cells. This represents the number of Tx Antennas detected on air for a certain base station. The cells are
sorted by their TX Antenna count (higher = better).

The tooltip of the raster elements contains a new column. This column shows the TX Antenna count of the
cell.
A new pie chart shows the distribution of the TX Antenna count of the LTE cells per network provider.
LTE MIMO 4x4 Rank Indicator analysis

For a true 4×4 MIMO measurement, 4 receivers and 4 Rx antennas are needed to be measured and
determine the so-called H-matrix of the 4×4 setup, including the 16 individual paths Tx_i/Rx_j (i,j = 0, 1, 2,
3). The rank represents the maximum number of possible independent layers (data streams) and the
condition number is a measure for channel quality. Condition numbers are dependent on the rank and
cannot be compared between different ranks.The NPA LTE MIMO analyzer can handle Rank (1…4) by
the mobile and the scanner Rank values for MIMO mode 2x2, 4x2 and 4x4.
To improve the data visualization the pages LTE MIMO Charts and LTE MIMO Problems are restructured.
A page for mobile results and a page for scanner results are available. Both pages can be selected from
the overview page.
New Page “LTE MIMO Mobile” contains:

- a Map which shows the
o Mobile problems
o Binned values with the mobile efficiency layers for DL / UL
- Updated - Scatter plots of mobile values from the PCC cells up to Rank 4
- New - Pie charts of the mobile rank per device from the PCC cells
- Efficiency charts and tables

- Table with the analyzed mobile problems
New Page “LTE MIMO Scanner” contains:

- a Map which shows the
o Scanner problems
o Binned values with the MIB TX Antenna and Rank (new MIMO mode 2x2/4x2/4x4) layers

- New bar charts for the Rank values (each cell from each bin) distribution for the MIMO Modes
2x2/4x2/4x4
- Chart of the condition number (CN) distribution for MIMO mode 2x2
- Pie charts of the distribution of eNB TX antenna cell count per Provider
- Table with the analyzed scanner problems
The tooltip of the raster elements of both maps contains all analyzed cells, from scanner and mobile.
DQA Ping analysis

The DQA analyzer for the Ping tests was extended and the result page shows more charts and a problem
table.
Following charts are added:
- Pie Charts with Job Result grouped by RAT
- Pie Charts with Job Result grouped by Network Provider
- Pie Charts with Ping Series success ratio per Network Provider
A Problem is created for each Ping test series where a defined number of pings or the failure ratio (count
of all ping in relation to failed pings of a single ping test) of the series is above a configurable threshold.
The threshold are part of the DQA KPI Overview processor configuration.

DQA Ping test result and KPI split by device
The KPIs and results from the ping test are analyzed and collected for each mobile device separately. The
device columns in the example below shows the setup time and the same device identification like the
ROMES does.
The table with all jobs at the Ping page is extended with the columns Device, so it’s easier to distinguish
between the jobs.
Furthermore, the bar chart and the table with RTT values get the device as new identification. The results
at the bar chart are grouped by Device, provider and RAT.
Memory usage information dialog and customizable alarming

The feature is a new dialog which can be reached via the “Help/Memory Usage” menu. It directly opens
the corresponding dialog.

The dialog shows an overview of general memory metrics of the system and the GUI process:
For more information regarding each specific metric, there is a tooltip that appears once the cursor hovers
over it.
The Notifications tab, which can be reached at the top, opens a table which holds defined alarms. By
choosing an alarm in the dropdown menu and pressing “Add” or the return-key, the alarm is added to the
table. If the user wants to delete an alarm, he can choose the row of the table and press the delete-key.

The alarms are automatically set once the user presses “OK” or “Apply” and are automatically deleted
once the alarm is triggered or if the user presses “Cancel”.
To give the user some guidance, there is a “Help” dialog which appears after pressing the “?” button:
Various format and range adaptations
Adaptation of floating number decimals for power values
Some of the views in the NPA had inconsistent floating precisions in regard of dB and dBm values. Thus,
NPA has changed all dBm/dB precision to have 1 decimal precision in accordance with the standard.
Frequency format for values in the UMTS TopN view aligned with other
views
The frequency values in the TopN Raster Element table were formatted in Hz instead of MHz. This has
been changed to be consistent with other views within NPA and ROMES.

RSRQ range for LTE Mobile Statistics/Coverage Cell Statistics aligned with
other views
The range of RSRQ in the “LTE Mobile Statistic Layer 1” has been aligned with other views.
Changed the range of RSRQ in the “LTE Mobile Coverage Cell Statistics” according to the Change
Request.

Overview New Features of Romes 18 - 2 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Overview New Features of Romes 18 - 2 PDF

Загружено:

Авторское право:

Доступные форматы

R&S® ROMES4 Release 18.

R&S® ROMES4 Coverage Measurement Software

3 Basic Views .......................................................................................................... 8

4 NB-IoT Scanner ................................................................................................. 14

5 5GNR Scanner ................................................................................................... 44

6 LTE Scanner ...................................................................................................... 62

14 Import / Export functionalities ............................................................................. 68

Rohde & Schwarz ROMES4 release 18.2 2

Rohde & Schwarz ROMES4 release 18.2 3

Rohde & Schwarz ROMES4 release 18.2 4

New Layout of Welcome Page

Rohde & Schwarz ROMES4 release 18.2 5

The Dark Mode with Large Icons:

Rohde & Schwarz ROMES4 release 18.2 6

Rohde & Schwarz ROMES4 release 18.2 7

Grid View Enhancements

Configuration Screen Update

Rohde & Schwarz ROMES4 release 18.2 8

Rohde & Schwarz ROMES4 release 18.2 9

Rohde & Schwarz ROMES4 release 18.2 10

Rohde & Schwarz ROMES4 release 18.2 11

Chart Error conditions

Configuration screen update

Rohde & Schwarz ROMES4 release 18.2 13

NB-IoT Scanner Configuration without using MDL

Rohde & Schwarz ROMES4 release 18.2 14

4.2.1.1 Launch NB-IoT Scanner configuration dialog

To launch NB-IoT Scanner Configuration dialog:

2. It can also be launched from main menu, Hardware -> Add/Remove…Ctrl+H

Rohde & Schwarz ROMES4 release 18.2 15

Click OK to accept the selection.

Screenshot below shows NB-IoT Scanner Configuration dialog box.

Rohde & Schwarz ROMES4 release 18.2 16

By default, the Nb-IoT Scanner Tab is selected on the left pane.

4.2.1.2.1 Open Configuration Dialog the very First Time

Rohde & Schwarz ROMES4 release 18.2 17

4.2.1.2.3 Buttons for configuring channels

4.2.1.2.4 Measurement Modes

NB-IoT scanner configuration has three modes:

Rohde & Schwarz ROMES4 release 18.2 18

4.2.2.1.1 Inband Frequency Calculator helper dialog

Rohde & Schwarz ROMES4 release 18.2 19

Rohde & Schwarz ROMES4 release 18.2 20

4.2.3.1 NB Guard Band Frequency Calculator Helper dialog

Rohde & Schwarz ROMES4 release 18.2 21

4.2.3.2 Bandwidth mode

Rohde & Schwarz ROMES4 release 18.2 22

Rohde & Schwarz ROMES4 release 18.2 23

The dropdown list is of following format:

Count of all measured channels: 2

Rate per second: 10.0

Channel Name: NB-IoT Channel 2

Rate per second: 10.0

4.2.3.3 NB EARFCN mode

Clicking Use NB EARFCN button, the calculation switches to NB EARFCN mode.

Rohde & Schwarz ROMES4 release 18.2 25

Rohde & Schwarz ROMES4 release 18.2 26

Screenshot above shows two frequencies scenario

Count of all measured channels: 2

Rate per second: 10.0

Channel Name: NB-IoT Channel 2

Rate per second: 10.0

Stand Alone mode