CMW NBIoT UE UserManual V3-8-30 en 12

R&S®CMW290/500
NB-IoT UE Firmware Applications

User Manual
(;ÜÆç2)
1178568902
Version 12
This user manual describes the following options for R&S®CMW500 and R&S®CMW290:
● R&S®CMW-KM300 (NB-IoT R13/14, TX measurement, uplink)
● R&S®CMW-KM012 (TX measurement, multi-evaluation list mode)
● R&S®CMW-KS300 (NB-IoT R13/14, generic signaling)
● R&S®CMW-KE100 (basic fading support: AWGN generator)
● R&S®CMW-KE500 (LTE fading profiles TS 36.521, excerpts)
© 2021 Rohde & Schwarz GmbH & Co. KG

Mühldorfstr. 15, 81671 München, Germany
Phone: +49 89 41 29 - 0
Email: info@rohde-schwarz.com
Internet: www.rohde-schwarz.com
Subject to change – data without tolerance limits is not binding.
R&S® is a registered trademark of Rohde & Schwarz GmbH & Co. KG.
Trade names are trademarks of the owners.
1178.5689.02 | Version 12 | R&S®CMW290/500
The following abbreviations are used throughout this manual: R&S®CMW is abbreviated as R&S CMW.
R&S®CMW290/500 Contents
Contents
1 Preface.................................................................................................... 9
1.1 Documentation Overview............................................................................................. 9
1.1.1 Getting Started Manual / Quick Start Guide....................................................................9
1.1.2 User Manual and Help.................................................................................................... 9
1.1.3 Features & Functions...................................................................................................... 9
1.1.4 Basic Safety Instructions...............................................................................................10
1.1.5 Data Sheet and Brochure..............................................................................................10
1.1.6 Release Notes and Open-Source Acknowledgment (OSA)..........................................10
1.1.7 Application Notes, Application Cards, White Papers, etc..............................................10
1.2 How to Read Firmware Application Chapters.......................................................... 10
1.2.1 General Description.......................................................................................................11
1.2.2 Application Sheets.........................................................................................................11
1.2.3 GUI Reference...............................................................................................................11
1.2.4 Programming Examples................................................................................................ 11
1.2.5 Command Reference.................................................................................................... 11
2 NB-IoT Signaling.................................................................................. 13
2.1 What's New.................................................................................................................. 13
2.2 General Description.................................................................................................... 13
2.2.1 Test Setup..................................................................................................................... 14
2.2.2 Initiating Signaling Tests................................................................................................14
2.2.3 Internal Fading.............................................................................................................. 15
2.2.4 Connection States.........................................................................................................16
2.2.5 Operation Modes...........................................................................................................18
2.2.6 Physical DL Channels and Signals............................................................................... 20
2.2.7 UL Resources in Time and Frequency Domain............................................................ 21
2.2.8 Scheduling Type UL RMC.............................................................................................23
2.2.9 Scheduling Type DL RMC.............................................................................................24
2.2.10 User-Defined Scheduling.............................................................................................. 24
2.2.11 Operating Bands........................................................................................................... 27
2.2.12 Data Tests..................................................................................................................... 30
2.2.13 Trigger Signals.............................................................................................................. 31
User Manual 1178.5689.02 ─ 12 3

2.2.14 Cell Reselection Setup..................................................................................................31

2.3 GUI Reference............................................................................................................. 32
2.3.1 Main View......................................................................................................................33
2.3.2 Signaling Control...........................................................................................................44
2.3.3 Using the Shortcut Softkeys..........................................................................................45
2.3.4 General Settings........................................................................................................... 46
2.3.5 RF Settings................................................................................................................... 47
2.3.6 Internal Fading.............................................................................................................. 52
2.3.7 Downlink Power Levels................................................................................................. 57
2.3.8 Uplink Power Control.................................................................................................... 58
2.3.9 Physical Cell Setup....................................................................................................... 61
2.3.10 Network Settings........................................................................................................... 71
2.3.11 Connection Configuration..............................................................................................80
2.3.12 UE Measurement Report Settings.............................................................................. 104
2.3.13 Messaging (SMS) Parameters.................................................................................... 104
2.3.14 Message Monitoring Settings......................................................................................109
2.3.15 Shortcut Configuration.................................................................................................110
2.3.16 Debug Configuration....................................................................................................110
2.4 Programming............................................................................................................. 112
2.4.1 General Configuration................................................................................................. 112
2.5 Command Reference................................................................................................ 126
2.5.1 Conventions and General Information........................................................................ 127
2.5.2 Connection Control and States................................................................................... 133
2.5.3 Event Log.................................................................................................................... 135
2.5.4 UE Info........................................................................................................................ 137
2.5.5 UE Capabilities............................................................................................................138
2.5.6 UE Measurement Report............................................................................................ 147
2.5.7 Routing Settings..........................................................................................................149
2.5.8 Internal Fading............................................................................................................ 160
2.5.9 Downlink Power Levels............................................................................................... 167
2.5.10 Uplink Power Control.................................................................................................. 168
2.5.11 Physical Cell Setup..................................................................................................... 172
2.5.12 Network Settings......................................................................................................... 185
User Manual 1178.5689.02 ─ 12 4

2.5.13 Connection Configuration............................................................................................198

2.5.14 Messaging (SMS)........................................................................................................240
2.5.15 Message Monitoring Settings......................................................................................249
2.6 List of commands..................................................................................................... 249
3 NB-IoT BLER Measurement.............................................................. 257

3.1 Performing a BLER Measurement........................................................................... 257
3.2 GUI Reference........................................................................................................... 258
3.2.1 Measurement Main View.............................................................................................258
3.2.2 Measurement Control..................................................................................................259
3.2.3 Measurement Results................................................................................................. 259
3.2.4 Settings....................................................................................................................... 262
3.3 Programming.............................................................................................................264
3.3.1 Configuring a BLER Measurement............................................................................. 264
3.3.2 Performing a BLER Measurement.............................................................................. 265
3.3.3 Performing a Confidence BLER Measurement........................................................... 265
3.4.2 Measurement Control and States............................................................................... 270
3.4.3 Measurement Settings................................................................................................ 272
3.5 List of commands..................................................................................................... 278
4 NB-IoT Multi-Evaluation Measurement............................................ 279

4.1 What's New................................................................................................................ 279
4.2 General Description.................................................................................................. 279
4.2.1 Test Setup................................................................................................................... 279
4.2.2 How to Measure an Uplink NB-IoT Signal...................................................................280
4.2.3 Scope of the Measurement......................................................................................... 280
4.2.4 Parallel Signaling and Measurement.......................................................................... 282
4.2.5 List Mode.....................................................................................................................282
4.2.6 NB-IoT UL Signal Properties.......................................................................................287
4.3 GUI Reference........................................................................................................... 291
User Manual 1178.5689.02 ─ 12 5

4.3.3 Signal Routing and Analyzer Settings.........................................................................306

4.3.4 Measurement Control Settings....................................................................................309
4.3.5 Trigger Settings........................................................................................................... 317
4.3.6 Limit Settings...............................................................................................................319
4.3.7 Shortcut Configuration................................................................................................ 326
4.3.8 Additional Softkeys and Hotkeys.................................................................................326
4.4 Programming.............................................................................................................328
4.4.1 General Examples.......................................................................................................328
4.4.2 Using the List Mode.................................................................................................... 332
4.5.2 General Measurement Settings.................................................................................. 342
4.5.3 Multi-Evaluation Measurement Commands................................................................ 347
4.5.4 Combined Signal Path Commands............................................................................. 407
4.6 List of commands..................................................................................................... 409
5 NB-IoT NPRACH Measurement.........................................................414

5.1 What's New................................................................................................................ 414
5.2 General Description.................................................................................................. 414
5.2.1 Test Setup................................................................................................................... 414
5.2.2 How to Measure an Uplink NPRACH Signal...............................................................414
5.2.3 Defining the Scope of the Measurement.....................................................................415
5.2.4 Parallel Signaling and Measurement.......................................................................... 416
5.2.5 Calculation of Modulation Results...............................................................................416
5.2.6 NB-IoT Preamble Structure.........................................................................................417
5.3 GUI Reference........................................................................................................... 418
5.3.3 Signal Routing and Analyzer Settings.........................................................................428
5.3.4 Measurement Control Settings....................................................................................428
5.3.5 Trigger Settings........................................................................................................... 432
5.3.6 Limit Settings...............................................................................................................434
5.3.7 Shortcut Configuration................................................................................................ 436
5.3.8 Additional Softkeys and Hotkeys.................................................................................436
User Manual 1178.5689.02 ─ 12 6

5.4 Programming.............................................................................................................436
5.4.1 Key Features...............................................................................................................437
5.4.2 Specifying General and Common Measurement Settings.......................................... 437
5.4.3 Specifying Required NPRACH Settings......................................................................438
5.4.4 Specifying Measurement-Specific Settings.................................................................438
5.4.5 Configuring the Trigger System...................................................................................438
5.4.6 Specifying Limits......................................................................................................... 438
5.4.7 Performing Single-Shot Measurements...................................................................... 439
5.4.8 Single-Shot and Continuous Measurements...............................................................440
5.5.2 General Measurement Settings.................................................................................. 446
5.5.3 NPRACH Measurement Commands...........................................................................446
5.5.4 Combined Signal Path Commands............................................................................. 471
5.6 List of commands..................................................................................................... 471
Index....................................................................................................474
User Manual 1178.5689.02 ─ 12 7

User Manual 1178.5689.02 ─ 12 8

R&S®CMW290/500 Preface
Documentation Overview
1 Preface
● Documentation Overview.......................................................................................... 9
● How to Read Firmware Application Chapters......................................................... 10
1.1 Documentation Overview

This chapter provides an overview of the R&S CMW user documentation. Most docu-
ments are available in PDF format on the customer web.
The customer web is a section of GLORIS, the global Rohde & Schwarz information
system, see https://gloris.rohde-schwarz.com. A registration is required.
1.1.1 Getting Started Manual / Quick Start Guide
Depending on your instrument model, there is either a getting started manual or a

quick start guide.
The document introduces the R&S CMW and describes how to set up and start work-
ing with the product.
A PDF file is available on the customer web.
1.1.2 User Manual and Help
Separate user manuals are provided for the base unit and the firmware applications:
● The base unit manual describes the base software and common features of the
firmware applications. It also describes basic principles for manual operation and
remote control. The manual includes the contents of the getting started manual or
quick start guide.
● Additional documents, like this one, describe the firmware applications, including
the graphical user interface of each application and the remote control commands.
All user manuals are available on the customer web.
The contents of the user manuals are also available as help in the R&S CMW. The
help offers quick, context-sensitive access to the information needed for operation and
programming. If you perform a software update, the help is also updated.
1.1.3 Features & Functions
The features & functions documents list the available software options and the related
features, settings and measurement results. The documents are available on the cus-
tomer web.
User Manual 1178.5689.02 ─ 12 9

How to Read Firmware Application Chapters
1.1.4 Basic Safety Instructions
Contains safety instructions in many languages.

The printed document is delivered with the instrument.
1.1.5 Data Sheet and Brochure
The data sheet contains the technical specifications of the R&S CMW. It also lists the
options and their order numbers and optional accessories.
The brochure provides an overview of the instrument and deals with the specific char-
acteristics.
The documents are available on the customer web.
1.1.6 Release Notes and Open-Source Acknowledgment (OSA)
The release notes list new features, improvements and known issues per software ver-
sion and installation package.
The open source acknowledgment provides verbatim license texts of the used open-
source software.
1.1.7 Application Notes, Application Cards, White Papers, etc.
These documents deal with special applications or background information on particu-

lar topics.
1.2 How to Read Firmware Application Chapters
Each firmware application is described in a separate chapter. These chapters can be

read independently of each other. However, they are all organized as follows:
1. General description
2. Application sheets (optional)
3. GUI reference
4. Programming examples
5. Command reference
User Manual 1178.5689.02 ─ 12 10

1.2.1 General Description
This chapter provides a general description of the firmware application, independent of

a specific operation mode (manual or remote control). Background information related
to the network standard is given as far as it is directly related to configurable parame-
ters.
1.2.2 Application Sheets
This optional chapter provides short application examples for selected issues and rela-
ted background information.
1.2.3 GUI Reference
The GUI reference describes the manual operation of the firmware application via the
graphical user interface (GUI).
The description of a configuration dialog usually starts with a screenshot presenting the
preset values of the parameters. Sometimes, preset values are modified to enable hid-
den parts of a dialog. Below the screenshot, all shown parameters are described. For
each single parameter, a link to the corresponding command description in the com-
mand reference is provided. Ranges for numeric parameters and reset values are
given there.
For measurement results, links to the corresponding command descriptions are provi-
ded (commands to retrieve the results).
1.2.4 Programming Examples
The programming examples show how to control and configure the firmware applica-
tion via a remote-control program and how to retrieve measurement results. The exam-
ples consist of comprehensive command sequences. You can check just a single com-
mand of a sequence to get an example for the syntax of this single command. But you
can also consider an entire sequence showing the commands in the context of a com-
mand script, under consideration of dependencies and required orders of the com-
mands.
The command sequences are written with the intention to list most commands of the
firmware application. They do not show the fastest way for a given configuration task.
The fastest way would use many reset values and omit the corresponding commands.
The examples are referenced by the command descriptions of the command refer-
ence.
1.2.5 Command Reference
The command reference provides information on the remote commands of the firm-
ware application. The commands are grouped according to their function.
User Manual 1178.5689.02 ─ 12 11

Each command description indicates the syntax of the command header and of the
parameters. For input parameters, the allowed ranges, reset values and default units
are listed. Most commands have a command form and a query form. Exceptions are
marked by "Setting only", "Query only" or "Event". Furthermore, a link to the program-
ming examples is provided and the first software version supporting the command is
indicated.
User Manual 1178.5689.02 ─ 12 12

R&S®CMW290/500 NB-IoT Signaling
General Description
2 NB-IoT Signaling
The NB-IoT signaling firmware application is available as option R&S CMW-KS300. It
emulates an NB-IoT cell and communicates with the UE under test. The UE can syn-
chronize to the downlink signal and attach to the PS domain. A connection can be set
up.
The application requires an SUA as signaling unit. The SUW is not supported.
Tests can be performed using the NB-IoT multi-evaluation measurement (option
R&S CMW-KM300).
Data transfer tests can be performed using the data application unit (DAU, option
R&S CMW-B450x and R&S CMW-KM050).
The NB-IoT signaling application provides also RX measurements, see Chapter 3,
"NB-IoT BLER Measurement", on page 257.
2.1 What's New

This documentation describes version 3.8.30 and higher of the NB-IoT signaling appli-
cation. Compared to version 3.8.20, it provides the following new features or changes.
● Connection timers T310, N310, N311
● UE capability request selection, see UE Capabilities Request
● Confidence BLER measurements, see:
– Confidence BLER measurements
– Confidence BLER results
– Confidence BLER
● The maximal value of out-o-sync timer increased, see:
CONFigure:NIOT:SIGN:CELL:TOUT:OOSYnc
2.2 General Description

The following sections describe how to use the R&S CMW for NB-IoT signaling tests
and provide background information.
● Test Setup............................................................................................................... 14
● Initiating Signaling Tests..........................................................................................14
● Internal Fading........................................................................................................ 15
● Connection States...................................................................................................16
● Operation Modes.....................................................................................................18
● Physical DL Channels and Signals......................................................................... 20
● UL Resources in Time and Frequency Domain...................................................... 21
● Scheduling Type UL RMC.......................................................................................23
● Scheduling Type DL RMC.......................................................................................24
User Manual 1178.5689.02 ─ 12 13

General Description
● User-Defined Scheduling........................................................................................ 24
● Operating Bands..................................................................................................... 27
● Data Tests............................................................................................................... 30
● Trigger Signals........................................................................................................ 31
● Cell Reselection Setup............................................................................................31
2.2.1 Test Setup
The basic test setup uses a bidirectional RF connection between the tester and the
device under test (DUT). It carries both the downlink and the uplink signal:
● The R&S CMW transmits the downlink signal to which the DUT can synchronize to
perform an attach. The downlink signal is used to transfer signaling messages and
user data to the DUT.
● The DUT transmits an uplink signal that the R&S CMW can receive, decode and
analyze.
For this setup, the DUT is connected to one of the bidirectional RF COM connectors at
the front panel of the R&S CMW. No additional cabling and no external trigger are nee-
ded. The input level ranges of all RF COM connectors are identical.
UL signal
R&S CMW RF COM

UE
DL signal
Figure 2-1: Test setup
2.2.2 Initiating Signaling Tests
The required settings vary depending on the measurement to be performed. However,

the following general procedure is applicable to most measurements.
1. Connect your UE to the R&S CMW (see Chapter 2.2.1, "Test Setup", on page 14).
2. Open the "NB-IoT signaling" firmware application.
3. Configure the signaling application according to your test case.

You can modify the most important settings directly in the main view. The "Config"
hotkey provides access to the configuration dialog box.
4. To turn on the DL signal, press ON | OFF. Alternatively, right-click the "NB-IoT Sig-
naling" softkey and click ON.
Wait until the "NB-IoT Signaling" softkey indicates the "ON" state and the hour
glass symbol has disappeared.
5. Switch on the UE.

The UE synchronizes to the DL signal and attaches. Note the connection states
displayed in the main view.
User Manual 1178.5689.02 ─ 12 14

General Description
6. If the RRC state is "Idle", press the "Connect" hotkey.

Whether this step is required depends on the setting "Keep RRC Connection".
7. To switch to the measurement application, press the "NB-IoT TX Meas" or "NB-IoT

RX Meas" softkey. The NB-IoT RX measurements are part of the "NB-IoT Signal-
ing" firmware application. The NB-IoT TX measurements are available as option
R&S CMW-KM300.
8. Configure and start the measurement.
If the UE fails to attach

Check the following R&S CMW settings:
● The "Frequency" of the generated DL signal must be within the frequency band
supported by the UE.
● The configured "NRS EPRE" must be sufficient so that the UE under test can
receive the DL signal.
● The "Uplink Power Control" settings must be appropriate so that the UL signal is
strong enough to be received and decoded by the R&S CMW.
● The UE capabilities must be in accordance with the security settings in the "Net-
work" section of the configuration dialog.
● For data application tests, the configured C-IoT optimization type must be suppor-
ted by the UE.
● The configured uplink subcarrier spacing must be supported by the UE.
If the measurement does not start

If the measurement does not start at all while the signaling application generates a
downlink signal, verify that the combined signal path scenario is selected in the mea-
surement.
2.2.3 Internal Fading
Testing under realistic air interface conditions is important in order to verify the receiver
performance and the correct operation of the protocol stack implementation. For exam-
ple, block error rates can be evaluated.
The fading uses one SUA partition. The SUA comes with a fading simulator. It manipu-
lates the generated downlink I/Q data stream to emulate typical signal conditions at the
receiver.
The following options are required to use the internal fading simulator:
● Option R&S CMW-KE100 for basic fading support and AWGN generator.
● Option R&S CMW-KE500 for LTE fading profiles TS 36.521
2.2.3.1 Fading Simulator
Multi-path fading is an effect which occurs in real world situations. A signal sent from
the base station follows the direct line of sight and/or takes routes with reflections. The
User Manual 1178.5689.02 ─ 12 15

General Description
phase-shifted signals sum up at the receiving antenna. If the receiver is moving, there
are also frequency-shifted signals.
The internal fading simulator supports multipath propagation conditions defined in
annex B.2 of 3GPP TS 36.101.
A faded signal has a higher crest factor than an unfaded one. To avoid distortion, the
baseband signal must be attenuated before entering the fading module. The necessary
attenuation (insertion loss) depends on the selected fading profile.
In NB-IoT signaling, the insertion loss at the baseband level can be calculated auto-
matically or set manually. It is automatically compensated on the HF level. The com-
pensation implies a shift of the allowed DL power range to the same extent, but in
opposite direction.
2.2.3.2 AWGN Generator
Additional white Gaussian noise (AWGN) is typically modeled in receiver tests,

because it can lead to a decrease of throughput. The quality of the received signal is
affected by the ratio of the signal power to the surrounding traffic noise level (signal to
noise ratio). The modulated signals from neighbor cells simply appear as noise. This
effect is simulated by adding AWGN to the signal.
The internal fading module supports AWGN insertion with configurable bandwidth and
signal to noise ratio. Insertion loss at the baseband level is calculated and compensa-
ted automatically at the HF.
AWGN insertion via the signaling unit is disabled for fading scenarios (see "AWGN"
on page 58).
2.2.4 Connection States
An NB-IoT connection is always a packet-switched connection. The main connection

states are described in the following table. The states are displayed in the main view
as "Packet Switched" (PS) state.
PS state Description
"(Cell) Off" No downlink signal transmission
"(Cell) On" The R&S CMW emulates an NB-IoT cell, transmitting an NB-IoT signal to which the UE
can synchronize. After synchronization, the UE can initiate an attach towards the instru-
ment.
"Attached" Synchronization and attach have been performed.

There is no radio resource control (RRC) connection (RRC state = idle).
"Connection An RRC connection has been established (RRC state = connected).

Established" User data can be exchanged. The R&S CMW can vary connection parameters and per-
form transmitter or receiver tests.
Note that short RRC idle periods are possible without a PS state change, for example, for
redirection.
User Manual 1178.5689.02 ─ 12 16

General Description
State transitions can be initiated by the instrument or by the UE. The transitions
between "Cell On" and "Connection Established" depend on whether the setting "Keep
RRC Connection" is enabled, or not. The following figure provides an overview.
Keep RRC Keep RRC

connection connection
Cell off Cell off
DL signal DL signal
ON / OFF ON / OFF
Cell on Cell on
Connect/
Detach Connect Detach Resume
Attached SMS Attached SMS
Disconnect/
Disconnect Suspend
Connection Connection
established SMS SMS
established
Figure 2-2: PS state transitions with and without Keep RRC Connection
Dotted line = Action initiated by instrument

Dashed line = Action initiated by UE
In addition to the main states shown in the table and the figure, the instrument indi-
cates the following transitory states:
● "Signaling in Progress"
For example, displayed during the attach procedure.
● "Connection in Progress"
Displayed during connection setup.
● "Sending Message"
Displayed while an SMS message is sent to the MS.
● "Receiving Message"
Displayed while an SMS message is received from the MS. To check the received
message, see Chapter 2.3.13.2, "Incoming SMS", on page 108.
● "Disconnect in Progress"
User Manual 1178.5689.02 ─ 12 17

General Description
Additional transitions
The list of transitions in Figure 2-2 is not complete. The "Off" state can be reached from
any state by turning off the cell signal. Moreover, incidents like a loss of the radio link
cause additional transitions.
2.2.5 Operation Modes
There are three NB-IoT operation modes defined by 3GPP. All three modes are sup-
ported by the signaling application.
This section provides background information for the three operation modes.
● Standalone Operation............................................................................................. 18
● Guard-Band Operation............................................................................................18
● In-Band Operation...................................................................................................19
2.2.5.1 Standalone Operation
In the standalone operation mode, the used spectrum is dedicated to NB-IoT only. So
the frequencies are not shared with another technology.
One possible deployment scenario is, to use no longer needed GSM spectrum for NB-
IoT. An NB-IoT carrier fits perfectly into a no longer used GSM channel.
Another scenario is, to use new spectrum for NB-IoT.
2.2.5.2 Guard-Band Operation
In the guard-band operation mode, the NB-IoT carrier is located in the guard band of
an LTE carrier. So the NB-IoT carrier uses already available LTE spectrum, without
reducing the capacity of the LTE carrier. But there can be interference between NB-IoT
and LTE.
The NB-IoT signaling application generates an NB-IoT cell signal and an LTE cell sig-
nal. The LTE signal contains no synchronization signals and no broadcast information.
So the UE cannot synchronize to the LTE cell signal. But the LTE signal contains cell-
specific reference signal (CRS) symbols. The other LTE OFDM symbols contain QPSK
modulated uncorrelated pseudo-random data. All LTE OFDM symbols have the same
power level.
Carrier frequency and channel raster offset

To maintain the orthogonality to the LTE carrier, the NB-IoT center frequency must fol-
low the subcarrier raster. So the possible NB-IoT frequencies in each guard band have
a spacing of 15 kHz, the downlink subcarrier spacing.
Another aspect is, that the UE uses the 100-kHz channel raster for cell search. For that
reason, 3GPP allows only NB-IoT DL frequencies with the smallest possible offset from
the 100-kHz channel raster. For cell BWs with an even total number of RBs, a DL
User Manual 1178.5689.02 ─ 12 18

General Description
channel raster offset of 2.5 kHz is allowed. For cell BWs with an odd total number of
RBs, a DL channel raster offset of 7.5 kHz is allowed.
The UL/DL separation for the guard-band mode and the in-band mode differs from the
UL/DL separation for the standalone mode by 7.5 kHz. In the lower guard band, the
spacing is greater. In the upper guard band, it is smaller. The UL channel raster offset
differs by 7.5 kHz from the DL channel raster offset.
The following tables list the used NB-IoT carrier position in the upper guard band
depending on the LTE cell BW. For the lower guard band, all values have the opposite
sign.
Table 2-1: NB-IoT carrier positions in the upper guard band
5 MHz 10 MHz 15 MHz 20 MHz
Downlink Frequency offset to LTE 2400 kHz 4600 kHz 7200 kHz 9100 kHz
Channel raster offset 7.5 kHz -2.5 kHz 7.5 kHz -2.5 kHz
Uplink Frequency offset to LTE 2400 kHz 4600 kHz 7200 kHz 9100 kHz
Channel raster offset 0 kHz -10 kHz 0 kHz -10 kHz
The NB-IoT signaling application takes care of all the dependencies. You configure the
NB-IoT RF frequency as for the standalone mode, for example via a channel number.
And you select the upper or lower guard band. The software calculates the resulting
LTE carrier frequencies and the channel raster offsets automatically. The channel ras-
ter offsets are added to the configured NB-IoT RF frequencies.
2.2.5.3 In-Band Operation
In the in-band operation mode, an NB-IoT carrier uses a small part of an LTE carrier.
The resources are flexibly assigned to LTE or to NB-IoT, only to one technology at a
time. So there is no interference between LTE and NB-IoT. But the capacity available
for LTE is reduced by NB-IoT.
As for the guard-band operation mode, the NB-IoT signaling application generates an
NB-IoT cell signal and an LTE cell signal. If both cells share a physical cell ID (mode
"Inband-SamePCI"), the UE can use the LTE CRS OFDM symbols for NB-IoT.
Carrier frequency and channel raster offset

In the in-band operation mode, the NB-IoT carrier uses exactly the frequency span of
an LTE resource block (RB). In the LTE downlink, the center subcarrier is not used. A
resource block covers 180 kHz, a DL subcarrier 15 kHz.
The following figure illustrates the DL frequencies in the center of a 10-MHz LTE chan-
nel.
User Manual 1178.5689.02 ─ 12 19

General Description
RB index LTE DC
Offset to DC carrier / kHz carrier
Channel raster offset / kHz
RB 19 RB 20 RB 21 RB 22 RB 23 RB 24 RB 25 RB 26 RB 27 RB 28 RB 29 RB 30
... -997.5 -817.5 -637.5 -457.5 -277.5 -97.5 97.5 277.5 457.5 637.5 817.5 997.5 ...
2.5 -17.5 -37.5 42.5 22.5 2.5 -2.5 -22.5 -42.5 37.5 17.5 -2.5
Figure 2-3: Resource block frequencies, DL 10-MHz LTE channel
You can see that the resource blocks have different offsets to the LTE 100-kHz channel
raster, the so-called channel raster offset. For cell BWs with an even total number of
RBs, there are absolute DL channel raster offsets from 2.5 kHz to 42.5 kHz. For cell
BWs with an odd total number of RBs, the absolute DL channel raster offsets range
from 7.5 kHz to 47.5 kHz.
Large DL channel raster offsets are a problem, because the UE uses the 100-kHz
channel raster for cell search. For that reason, 3GPP allows only NB-IoT DL frequen-
cies with the smallest possible offset (2.5 kHz or 7.5 kHz). The RBs around the center
of the LTE channel are also not allowed, because they carry synchronization signals.
The following table lists the RB indices that are allowed for NB-IoT, depending on the
LTE cell BW.
Table 2-2: LTE RB indices allowed for NB-IoT in-band operation, depending on LTE cell BW
3 MHz 5 MHz 10 MHz 15 MHz 20 MHz
RBs 2, 12 2, 7, 17, 4, 9, 14, 19, 2, 7, 12, 17, 22, 27, 32, 4, 9, 14, 19, 24, 29, 34, 39, 44,
22 30, 35, 40, 45 42, 47, 52, 57, 62, 67, 72 55, 60, 65, 70, 75, 80, 85, 90, 95
In contrast to the LTE DL, the LTE UL uses the center subcarrier. As a consequence,
the UL channel raster offset differs by 7.5 kHz from the DL channel raster offset. For
carriers below the LTE DC carrier, the UL offset equals the DL offset plus 7.5 kHz. For
carriers above the LTE DC carrier, the UL offset equals the DL offset minus 7.5 kHz.
The NB-IoT signaling application takes care of all the dependencies. You configure the
NB-IoT RF frequency as for the standalone mode, for example via a channel number.
And you select which allowed resource block you want to use for NB-IoT. The software
calculates the resulting LTE carrier frequencies and the channel raster offsets automat-
ically. The channel raster offsets are added to the configured NB-IoT RF frequencies.
2.2.6 Physical DL Channels and Signals
The NB-IoT downlink uses the physical channels and signals listed in the following
tables.
User Manual 1178.5689.02 ─ 12 20

General Description
Table 2-3: Physical DL channels
Physical DL channel Purpose
Narrowband physical broadcast channel Provides physical layer information of the cell to be read during
(NPBCH) cell search, e.g. system frame number, scheduling of SIB-NB,
transmit antenna info, NRS ports
Narrowband physical downlink control Carries UE-specific control information, like scheduling infor-
channel (NPDCCH) mation
Carries ACK/NACK indicators for uplink packets
Narrowband physical downlink shared Carries user data

channel (NPDSCH)
Table 2-4: Physical DL signals
Physical DL signal Purpose
Narrowband reference signal (NRS) For demodulation
Narrowband primary synchronization sig- Acquisition of cell timing, frequency synchronization, detection
nal (NPSS) of cell identity
Narrowband secondary synchronization
signal (NSSS)
Wake up signal (WUS) Indicates whether the UE has to decode subsequent physical
channel. Transmitted on NPBCH, 11 symbols for in-band, 14
symbols for standalone and guard-band operation.
2.2.7 UL Resources in Time and Frequency Domain
The channel bandwidth for NB-IoT is 200 kHz. At both edges, 10 kHz are not allocated
(guard band). The remaining 180 kHz can be allocated to UEs.
The 180 kHz are divided into subcarriers. There are two different modes:
● 3.75 kHz subcarrier spacing, bandwidth divided into 48 subcarriers
● 15 kHz subcarrier spacing, bandwidth divided into 12 subcarriers
In the time domain, the smallest unit is an SC-FDMA symbol. Each symbol contains a
guard time called cyclic prefix (CP). A time slot contains seven SC-FDMA symbols with
normal CP. A time slot for 3.75 kHz subcarrier spacing ends with a guard period (GP,
no UL signal).
Depending on the subcarrier spacing, the slot length is 2 ms or 0.5 ms. A radio frame
of 10 ms contains 5 slots or 20 slots.
Durations are often stated in sample intervals Ts. Ts can be calculated from the sam-
pling frequency 30.72 MHz: 1 Ts = 1/30.72 MHz ≈ 32.55 ns.
The following table and figures summarize this information.
User Manual 1178.5689.02 ─ 12 21

General Description
Subcarriers Slots Symbol duration
Spacing No. Duration Per frame CP Data Note
3.75 kHz 48 2 ms, 61440 Ts 5 256 Ts 8192 Ts GP at end of slot

2304 Ts
15 kHz 12 0.5 ms, 15360 Ts 20 symbol 1: 160 Ts 2048 Ts -

symbol n: 144 Ts
SC-FDMA symbol
3.75 kHz Normal CP, 256 Ts ≈ 8.3 µs Data, 8192 Ts ≈ 266.7 µs
Guard
2304 Ts
≈ 75 µs
Slot 0 Slot 1 Slot 2 Slot 3 Slot 4
2 ms
1 radio frame = 10 ms = 5 slots
Figure 2-4: Frame structure for 3.75 kHz subcarrier spacing
SC-FDMA symbol
Normal CP, 144 Ts ≈ 4.7 µs

15 kHz Data, 2048 Ts ≈ 66.7 µs
First symbol: 160 Ts ≈ 5.2 µs
7 SC-FDMA symbols with normal CP
0.5 ms
Figure 2-5: Frame structure for 15 kHz subcarrier spacing
User Manual 1178.5689.02 ─ 12 22

General Description
2.2.7.1 Resource Unit Allocation
For allocation to a UE, the UL resources are grouped into resource units (RU). A
resource unit comprises a certain number of subcarriers (SC) in the frequency domain
and a certain number of slots in the time domain.
The allowed values depend on the NPUSCH format and on the subcarrier spacing, as
listed in the following table.
Table 2-5: Number of subcarriers and slots per resource unit
NPUSCH SC spacing No of SC SC offset No of slots Modulation RU duration

format
1 3.75 kHz 1 0 to 47 16 BPSK, QPSK 32 ms
15 kHz 1 0 to 11 16 BPSK, QPSK 8 ms
3 0, 3, 6, 9 8 QPSK 4 ms
6 0, 6 4 QPSK 2 ms
12 0 2 QPSK 1 ms
2 3.75 kHz 1 0 to 47 4 BPSK 8 ms
15 kHz 1 0 to 11 4 BPSK 2 ms
2.2.8 Scheduling Type UL RMC
UL reference measurement channels are intended for UL RF tests, specified in 3GPP

TS 36.521, chapter 6. You can use them for the NB-IoT multi-evaluation measurement.
The UL RMCs are defined in 3GPP TS 36.521, Annex A.2.4. The signaling application
uses the UL scheduling patterns defined there. A pattern determines which subframes
are scheduled.
In the signaling application, a UL RMC can be defined via the following set of parame-
ters:
● Number of subcarriers (no of SC)
● Position of the first subcarrier (start SC)
● MCS index, determining the modulation scheme and the transport block size
● Number of resource units (no of RU)
● Number of repetitions
The parameter combinations supported by the R&S CMW for NPUSCH format 1 are
listed in the following table, depending on the SC spacing.
Table 2-6: UL RMC parameters, NPUSCH format 1
SC spacing No of SC Start SC MCS No of RU Repetitions
3.75 kHz 1 0 to 47 0 2 1
3 1 1
15 kHz 1 0 to 11 0 2 1
User Manual 1178.5689.02 ─ 12 23

General Description
SC spacing No of SC Start SC MCS No of RU Repetitions
3 1 1
3 0, 3, 6, 9 5 1 1
6 0, 6 5 1 1
12 0 5 1 1
The settings for NPUSCH format 2 are not configurable. The following table lists which
parameter combination is used by the R&S CMW.
Table 2-7: UL RMC parameters, NPUSCH format 2
SC spacing Start SC No of SC Modulation No of RU Repetitions
3.75 kHz 38 1 BPSK 1 1
15 kHz 0
2.2.9 Scheduling Type DL RMC
DL reference measurement channels are intended for DL RF tests, specified in 3GPP

TS 36.521, chapter 7 and 8. You can use them for BLER measurements.
The DL RMCs are defined in 3GPP TS 36.521, table A.3.2-1c/1ca. The signaling appli-
cation uses the DL scheduling patterns defined there. A pattern determines which sub-
frames are scheduled.
In the signaling application, a DL RMC can be defined via the following set of parame-
ters:
● Number of subcarriers (no of SC)
● Position of the first subcarrier (start SC)
● Number of subframes (no of SF)
The parameter combinations supported by the R&S CMW are listed in the following
table.
Table 2-8: Parameter combinations for DL RMC scheduling
No of SC Start SC MCS No of SF Repetitions
12 0 6 1 1
2.2.10 User-Defined Scheduling
In addition to RMCs required by conformance tests, the signaling application supports

flexibly configurable user-defined scheduling.
User Manual 1178.5689.02 ─ 12 24

General Description
The signaling application sends a UL grant or a DL grant to the UE at each possible

search space occasion. A configurable pattern defines the sequence of grants (UL
grants only, DL grants only, alternating UL/DL grants, no grants at all).
The granted scheduling is defined via a set of parameters:
● Number of subcarriers
● Position of the first subcarrier
● Number of DL subframes or UL resource units
The parameter combinations supported by the R&S CMW are described in the follow-
ing sections. The UL settings apply to NPUSCH format 1. The parameters for
NPUSCH format 2 are not configurable. They are identical to the NPUSCH format 2
values for RMCs, see Table 2-7.
Number and position of subcarriers

The allowed number of subcarriers depends on the direction and on the subcarrier
spacing. The allowed positions for the first subcarrier depend on the number of subcar-
riers and on the subcarrier spacing. The following table lists the dependencies.
Table 2-9: Number of subcarriers and start subcarrier
Direction SC spacing No of SC Start SC
UL 3.75 kHz 1 0 to 47
15 kHz 1 0 to 11
3 0, 3, 6, 9
6 0, 6
12 0
DL 15 kHz 12 0
Transport block size (TBS)

Transport block size depends on the number of resource units (uplink) or subframes
(downlink), MCS index, and number of subcarriers.
The allowed number of resource units (uplink) or subframes (downlink) depends on the
MCS index and on the 3GPP release version. In 3GPP Rel. 14, the allowed parameter
range is extended compared to 3GPP Rel. 13.
The TBS dependencies are defined in 3GPP TS 36.213, sections 16.4.1 and 16.5.1.
The following tables list the TBS dependencies for both Rel.13 and Rel. 14.
Note, that the R&S CMW settings for MCS, number of resource units (uplink) or sub-
frames (downlink) must match the 3GPP release capability of the UE.
User Manual 1178.5689.02 ─ 12 25

General Description
Table 2-10: TBS in uplink
MCS Number of resource units
1 2 3 4 5 6 8 10
01) 16 32 56 88 120 152 208 256
11) 24 56 88 144 176 208 256 344
21) 32 72 144 176 208 256 328 424
3 40 104 176 208 256 328 440 568
4 56 120 208 256 328 408 552 680
5 72 144 224 328 424 504 680 872
6 88 176 256 392 504 600 808 1000
7 104 224 328 472 584 712 1000 12243)
8 120 256 392 536 680 808 10963) 13843)
9 136 296 456 616 776 936 12563) 15443)
10 144 328 504 680 872 1000 13843) 17363)
112) 176 376 584 776 1000 11923) 16083) 20243)
122) 208 440 680 1000 11283) 13523) 18003) 22803)
132) 2243) 4883) 7443) 10323) 12563) 15443) 20243) 25363)
1)TBS values are shown für No. of subcarriers > 1. For No. of subcarriers = 1, TBS values are different
than the values in the table, but the TBS values do not differ between Rel. 13 and Rel. 14.
2)An additional restriction is defined in 3GPP TS 36.213, section 16.5.1: If the number of subcarriers
equals 1, the MCS indices 11, 12, and 13 are not allowed.
3) Introduced in Rel. 14. Not supported by Rel. 13 UE.
Table 2-11: TBS in downlink
MCS Number of subframes
1 2 3 4 5 6 8 10
01) 16 32 56 88 120 152 208 256
11) 24 56 88 144 176 208 256 344
21) 32 72 144 176 208 256 328 424
3 40 104 176 208 256 328 440 568
4 56 120 208 256 328 408 552 680
5 72 144 224 328 424 504 680 8722)
6 88 176 256 392 504 600 8082) 10322)
7 104 224 328 472 584 680 9682) 12242)
8 120 256 392 536 680 8082) 10962) 13522)
9 136 296 456 616 7762) 9362) 12562) 15442)
User Manual 1178.5689.02 ─ 12 26

General Description
MCS Number of subframes
1 2 3 4 5 6 8 10
10 144 328 504 680 8722) 10322) 13842) 17362)
11 176 376 584 776 10002) 11922) 16082) 20242)
12 208 440 680 10002) 11282) 13522) 18002) 22802)
13 2242) 4882) 7442) 10322) 12562) 15442) 20242) 25362)
1) TBS values are shown für No. of subcarriers > 1. For No. of subcarriers = 1, TBS values are different
than the values in the table, but the TBS values do not differ between Rel. 13 and Rel. 14.
2) Only for release 14.
Repetitions
User-defined scheduling supports the following numbers of repetitions:
● UL: 1, 2, 4, 8, 16, 32, 64, 128
● DL: 1, 2, 4, 8, 16, 32, 64, 128, 192, 256, 384, 512, 768, 1024, 1536, 2048
Maximal possible throughput

All generated physical DL channels and signals share resources provided on single
carrier (see Chapter 2.2.6, "Physical DL Channels and Signals", on page 20). There-
fore, the possible throughput of user data (at NPDSCH) is smaller than the theoretical
peak value of 126 kbps.
Data rates depend on the selected scheduling pattern, refer to "Pattern" on page 86.
For the maximal possible throughput, configure the parameters as follows:
1. Enable HARQ
2. Set No. of HARQ Processes = 2
3. Set Scheduling Type = "User defined"
4. Set Pattern = "Alternating DL/UL"
5. In DL, set MCS Index = 13
6. In DL, set the number of "Subframes" to 10, see Resource Units, Subframes
7. In UL, set the number of "Subcarriers" to 12, see Subcarriers, Start Subcarrier
8. In UL, set MCS Index = 13
9. In UL, set the number of "Resource Units" to 10, see Resource Units, Subframes
2.2.11 Operating Bands
The carrier frequencies for NB-IoT signals are defined in 3GPP TS 36.101. Each oper-
ating band contains carrier frequencies identified by channel numbers (EARFCN, E-
UTRA absolute radio frequency channel number). The assignment between channel
numbers N and carrier center frequencies F is defined as:
User Manual 1178.5689.02 ─ 12 27

General Description
N = 10 x (F - FOffset)/MHz + NOffset
The tables in this section provide an overview of all supported operating bands. For
each band, they list the offset frequencies FOffset, the channel number offsets NOffset, the
channel numbers N and the carrier center frequencies F.
The table for uplink signals lists also the separation between uplink carrier frequencies
and downlink carrier frequencies.
The RF frequencies are configured according to the tables in this section, independent
of the operation mode. In the guard-band operation mode and the in-band operation
mode, there are channel raster offsets added to the configured RF frequencies, see
Chapter 2.2.5, "Operation Modes", on page 18.
Table 2-12: Operating bands for uplink signals
Band FOffset, UL / MHz NOffset, UL Channel NUL FUL / MHz (FDL-FUL) / MHz
1 1920 18000 18000 to 18599 1920 to 1979.9 190
2 1850 18600 18600 to 19199 1850 to 1909.9 80
3 1710 19200 19200 to 19949 1710 to 1784.9 95
4 1710 19950 19950 to 20399 1710 to 1754.9 400
5 824 20400 20400 to 20649 824 to 848.9 45
7 2500 20750 20750 to 21449 2500 to 2569.9 120
8 880 21450 21450 to 21799 880 to 914.9 45
9 1749.9 21800 21800 to 22149 1749.9 to 1784.8 95
10 1710 22150 22150 to 22749 1710 to 1769.9 400
11 1427.9 22750 22750 to 22949 1427.9 to 1447.8 48
12 699 23010 23010 to 23179 699 to 715.9 30
13 777 23180 23180 to 23279 777 to 786.9 -31
14 788 23280 23280 to 23379 788 to 797.9 -30
17 704 23730 23730 to 23849 704 to 715.9 30
18 815 23850 23850 to 23999 815 to 829.9 45
19 830 24000 24000 to 24149 830 to 844.9 45
20 832 24150 24150 to 24449 832 to 861.9 -41
21 1447.9 24450 24450 to 24599 1447.9 to 1462.8 48
22 3410 24600 24600 to 25399 3410 to 3489.9 100
24 1626.5 25700 25700 to 26039 1626.5 to 1660.4 -101.5
25 1850 26040 26040 to 26689 1850 to 1914.9 80
26 814 26690 26690 to 27039 814 to 848.9 45
27 807 27040 27040 to 27209 807 to 823.9 45
28 703 27210 27210 to 27659 703 to 747.9 55
User Manual 1178.5689.02 ─ 12 28

General Description
Band FOffset, UL / MHz NOffset, UL Channel NUL FUL / MHz (FDL-FUL) / MHz
30 2305 27660 27660 to 27759 2305 to 2314.9 45
31 452.5 27760 27760 to 27809 452.5 to 457.4 10
65 1920 131072 131072 to 131971 1920 to 2009.9 190
66 1710 131972 131972 to 132671 1710 to 1779.9 400
68 698 132672 132672 to 132971 698 to 727.9 55
70 1695 132972 132972 to 133121 1695 to 1710 300
71 663 133122 133122 to 133471 663 to 698 -46
72 451 133472 133472 to 133521 451 to 456 10
73 450 133522 133522 to 133571 450 to 455 10
74 1427 133572 133572 to 134001 1427 to 1470 48
85 698 134002 134002 to 134181 698 to 716 30
Table 2-13: Operating bands for downlink signals
Band FOffset, DL / MHz NOffset, DL Channel NDL FDL / MHz
1 2110 0 0 to 599 2110 to 2169.9
2 1930 600 600 to 1199 1930 to 1989.9
3 1805 1200 1200 to 1949 1805 to 1879.9
4 2110 1950 1950 to 2399 2110 to 2154.9
5 869 2400 2400 to 2649 869 to 893.9
7 2620 2750 2750 to 3449 2620 to 2689.9
8 925 3450 3450 to 3799 925 to 959.9
9 1844.9 3800 3800 to 4149 1844.9 to 1879.8
10 2110 4150 4150 to 4749 2110 to 2169.9
11 1475.9 4750 4750 to 4949 1475.9 to 1495.8
12 729 5010 5010 to 5179 729 to 745.9
13 746 5180 5180 to 5279 746 to 755.9
14 758 5280 5280 to 5379 758 to 767.9
17 734 5730 5730 to 5849 734 to 745.9
18 860 5850 5850 to 5999 860 to 874.9
19 875 6000 6000 to 6149 875 to 889.9
20 791 6150 6150 to 6449 791 to 820.9
21 1495.9 6450 6450 to 6599 1495.9 to 1510.8
22 3510 6600 6600 to 7399 3510 to 3589.9
24 1525 7700 7700 to 8039 1525 to 1558.9
User Manual 1178.5689.02 ─ 12 29

General Description
Band FOffset, DL / MHz NOffset, DL Channel NDL FDL / MHz
25 1930 8040 8040 to 8689 1930 to 1994.9
26 859 8690 8690 to 9039 859 to 893.9
27 852 9040 9040 to 9209 852 to 868.9
28 758 9210 9210 to 9659 758 to 802.9
30 2350 9770 9770 to 9869 2350 to 2359.9
31 462.5 9870 9870 to 9919 462.5 to 467.4
65 2110 65536 65536 to 66435 2110 to 2199.9
66 2110 66436 66436 to 67135 2110 to 2179.9
68 753 67536 67536 to 67835 753 to 782.9
70 1995 68336 68336 to 68485 1995 to 2020
71 617 68586 68586 to 68935 617 to 652
72 461 68936 68936 to 68985 461 to 466
73 460 68986 68986 to 69035 460 to 455
74 1475 69036 69036 to 69465 1475 to 1517
85 728 70366 70366 to 70545 728 to 746
2.2.12 Data Tests
The NB-IoT signaling application provides a test mode, using only layer 1 and 2 of the
protocol stack. And it provides a data application mode that supports also layer 3.
To use the data application mode, you need the following options in addition to the
"NB-IoT signaling" application:
● Data application unit (DAU, R&S CMW-B450x, mandatory)
● IPv4 enabler (R&S CMW-KA100, mandatory)
IPv6 enabler (R&S CMW-KA150, optional)
● DAU measurements (R&S CMW-KM050, optional)
● Installed DAU software package
Configure a scheduling type with uplink and downlink scheduling. You can use user-
defined scheduling with alternating UL/DL pattern.
In data application mode, you can perform IP-based data tests using the DAU mea-
surements.
For further reference:
● To enable the data application mode, see "Connection Type" on page 81.
● For step-by-step instructions, refer to the data application unit documentation.
User Manual 1178.5689.02 ─ 12 30

General Description
2.2.13 Trigger Signals
The NB-IoT signaling application provides trigger signals that can be used by other
R&S CMW applications to synchronize to the generated NB-IoT downlink signal.
To address the trigger signals in remote commands, use the following strings, with 
replaced by the instance number of the signaling application:
● "NB-IoT Sig: NPUSCH format 1 Trigger"
● "NB-IoT Sig: NPUSCH format 2 Trigger"
● "NB-IoT Sig: NPRACH Trigger"
NPUSCH trigger, format 1/2

Trigger event at the beginning of the first UL slot of each NPUSCH transmission with
format 1/2.
There are two trigger signals, one for transmissions with NPUSCH format 1 and the
other one for transmissions with NPUSCH format 2.
The signals can be used to trigger NB-IoT multi-evaluation measurements (option
R&S CMW-KM300).
For combined signal path measurements, the signaling application sets the trigger
source of the multi-evaluation measurement as follows:
● If the configured scheduling includes a UL, the NPUSCH format 1 trigger signal is
selected.
● If the configured scheduling comprises only a DL, the NPUSCH format 2 trigger
signal is selected.
You can modify the trigger source selection in the measurement, so that you can mea-
sure NPUSCH format 1 and 2 for schedulings with UL and DL.
NPRACH trigger
Trigger event for each received NPRACH preamble. When a preamble has been suc-
cessfully received and detected by the signaling application, a trigger signal is gener-
ated 10 ms after the start of the preamble.
The NPRACH trigger signal can be used to trigger NB-IoT "NPRACH" measurements
(option R&S CMW-KM300). When the measurement receives a trigger event, it evalu-
ates already measured data to provide results for the preamble.
2.2.14 Cell Reselection Setup
The following example explains, how to configure network for cell reselection mecha-
nism:
1. Configure basic parameters of NB-IoT serving cell and NB-IoT target reselection
cell:
User Manual 1178.5689.02 ─ 12 31

GUI Reference
a) Select output path for NB-IoT signaling application, in this example "NB-IoT
Sig1" providing serving cell, see "RF Output (TX)" on page 49.
b) Select different output path for another NB-IoT signaling application, in this
example "NB-IoT Sig2" providing target cell. Use different TX modules for the
two applications.
c) Set appropriate attenuation for "NB-IoT Sig1" and "NB-IoT Sig2", see "External
Attenuation" on page 49
d) Specify different TACs for "NB-IoT Sig1" and "NB-IoT Sig2":
Set TAC to 1 for "NB-IoT Sig1"
Set TAC to 2 for "NB-IoT Sig2"
e) Disable Keep RRC Connection for "NB-IoT Sig1" and "NB-IoT Sig2"
f) Activate Enable Advanced Settings for "NB-IoT Sig1" and "NB-IoT Sig2"
g) Set different E-UTRAN cell identifiers: 0001 0000 0000 for "NB-IoT Sig1" and
0001 0000 0001 for "NB-IoT Sig2", see "E-UTRAN Cell Identifier" on page 75
2. Configure and enable neighbor cell in "NB-IoT Sig1" (in this example band 3, chan-
nel 1200, cell ID 1), see Chapter 2.3.10.1, "Neighbor Cell Settings", on page 72.
3. Configure serving cell via "NB-IoT Sig1" and target cell via "NB-IoT Sig2" according
to the neighbor cell settings. Use different channels for the both cells.
a) Select operating band for "NB-IoT Sig1" and "NB-IoT Sig2", in this example
both set to 3, see "Operating Band, Channel, Frequency" on page 50
b) Set different DL channels: 1575 for "NB-IoT Sig1" and 1200 for "NB-IoT Sig2",
see "Operating Band, Channel, Frequency" on page 50
c) Set physical channel IDs: 0 for "NB-IoT Sig1" and 1 for "NB-IoT Sig2", see
"Physical Cell ID" on page 62
4. Configure both cells according to cell reselection settings in "NB-IoT Sig1", see
Chapter 2.3.10.2, "Cell Reselection Settings", on page 73.
a) Set NRS EPRE to -85 dBm for "NB-IoT Sig1" and -75 dBm for "NB-IoT Sig2",
see "NRS EPRE" on page 57.
5. Switch on NB-IoT serving cell via "NB-IoT Sig1".
6. Perform mobile registration on the NB-IoT serving cell.
7. Switch on NB-IoT target cell via "NB-IoT Sig2". Wait for up to 3 minutes.
The UE reselects to the target cell.
2.3 GUI Reference

The following sections provide detailed reference information on the parameters of the
NB-IoT signaling application. Most parameters can be configured via a single configu-
ration dialog. Additional dialogs allow you to configure the measurements included in
the signaling application.
User Manual 1178.5689.02 ─ 12 32

GUI Reference
Many of the signaling parameters are available in a subset of connection states only.
Temporarily unavailable parameters are grayed out in the configuration dialogs; hot-
keys appear and disappear dynamically, depending on the connection state.
The screenshots in this chapter show the GUI with all available options installed.
Depending on the installed options, some parameters are not configurable (display the
default value) or are not visible at all. The required options are stated.
The GUI reference is structured as follows.

● Main View................................................................................................................33
● Signaling Control.....................................................................................................44
● Using the Shortcut Softkeys....................................................................................45
● General Settings..................................................................................................... 46
● RF Settings............................................................................................................. 47
● Internal Fading........................................................................................................ 52
● Downlink Power Levels........................................................................................... 57
● Uplink Power Control.............................................................................................. 58
● Physical Cell Setup................................................................................................. 61
● Network Settings..................................................................................................... 71
● Connection Configuration........................................................................................80
● UE Measurement Report Settings........................................................................ 104
● Messaging (SMS) Parameters.............................................................................. 104
● Message Monitoring Settings................................................................................109
● Shortcut Configuration...........................................................................................110
● Debug Configuration............................................................................................. 110
2.3.1 Main View
The main view of the signaling application shows status information and information
derived from the uplink signal on the left and the most important settings on the right.
All settings in this view can also be accessed via the configuration dialog.
For a description of available hotkeys, refer to Chapter 2.3.2, "Signaling Control",
on page 44.
User Manual 1178.5689.02 ─ 12 33

GUI Reference
Figure 2-6: NB-IoT signaling main view
For descriptions of the individual areas of the view, refer to the subsections.
● Connection Status...................................................................................................34
● Event Log................................................................................................................35
● UE Info.................................................................................................................... 35
● UE Capabilities........................................................................................................36
● UE Measurement Report........................................................................................ 42
● Settings................................................................................................................... 43
2.3.1.1 Connection Status
Access: NB-IoT signaling main view > "Connection Status" pane.

The connection status pane displays the following information.
Figure 2-7: Connection status pane of the main view
For background information about the displayed states, see Chapter 2.2.4, "Connec-
tion States", on page 16.
For control of the states, see Chapter 2.3.2, "Signaling Control", on page 44.
User Manual 1178.5689.02 ─ 12 34

GUI Reference
Cell
Displays the current state (or state transition) of the downlink signal generator.
Remote command:
SOURce:NIOT:SIGN:CELL:STATe
Packet Switched
Displays the current state or state transition of the packet-switched network domain.
Remote command:
FETCh:NIOT:SIGN:PSWitched:STATe?
RRC State
Indicates whether an RRC connection is established ("Connected") or not ("Idle").
Remote command:
SENSe:NIOT:SIGN:RRCState?
2.3.1.2 Event Log
Access: NB-IoT signaling main view > "Event Log" pane.

The event log pane reports events and errors like PS connection state changes and
RRC connection establishment/release.
The button to the right clears the displayed event entries.
Figure 2-8: Event log pane of the main view
Event log entries

Each entry consists of a timestamp, an icon indicating the category of the event and a
short text describing the event.
Meaning of the category icons: = information, warning and error
Remote command:
SENSe:NIOT:SIGN:ELOG:LAST?
SENSe:NIOT:SIGN:ELOG:ALL?
CLEan:NIOT:SIGN:ELOG
2.3.1.3 UE Info
Access: NB-IoT signaling main view > select "UE Info" in the field below the "Event
Log" pane.
User Manual 1178.5689.02 ─ 12 35

GUI Reference
The "UE Info" pane displays UE-related information for an attached UE.
Figure 2-9: UE info pane of the main view
IMEI
International mobile equipment identity (IMEI) received from the UE.
Remote command:
SENSe:NIOT:SIGN:UESinfo:IMEI?
IMSI
International mobile subscriber identity (IMSI) received from the UE.
Remote command:
SENSe:NIOT:SIGN:UESinfo:IMSI?
Default Bearer
List of all established default bearers, one line per bearer.
Each line contains the following information:
● Default bearer ID, composed as follows: <EPS default bearer ID> (<APN>)
Example: "5 (cmw500.rohde.schwarz.com)" means default bearer 5, with access
point name "cmw500.rohde.schwarz.com"
● IPv4 address assigned to the UE for this bearer
● IPv6 prefix assigned to the UE for this bearer
Remote command:
CATalog:NIOT:SIGN:UESinfo:DEFBearer?
SENSe:NIOT:SIGN:UESinfo:UEADdress:IPV<version>?
2.3.1.4 UE Capabilities
Access: NB-IoT signaling main view > select "UE Capabilities" in the field below the
"Event Log" pane.
The UE capabilities characterize the radio access capabilities of the UE. The capability
information is specified in 3GPP TS 36.331.
"UE Capabilities" pane displays the most important UE capabilities.
User Manual 1178.5689.02 ─ 12 36

GUI Reference
Figure 2-10: UE capabilities in the main view
To maximize the UE capabilities pane and display all capability information, press the
button to the right.
The provided UE capability information is described in the subsections.
● RRC Connection Establishment..............................................................................37
● General UE Capability Information..........................................................................38
● RF UE Capabilities..................................................................................................38
● PDCP UE Capabilities.............................................................................................39
● MAC UE Capabilities...............................................................................................40
● Physical Layer UE Capabilities............................................................................... 40
● Paging UE Capabilities........................................................................................... 42
RRC Connection Establishment

The UE capability information in this section is received during the RRC connection
establishment, before authentication.
Figure 2-11: RRC connection capability info
Multi-Tone......................................................................................................................37
Multi-Carrier.................................................................................................................. 37
User Plane C-IoT Optimization..................................................................................... 38
Multi-Tone
Indicates whether the UE supports NPUSCH multi-tone transmissions.
This information is received in an RRC connection request.
Remote command:
SENSe:NIOT:SIGN:UECapability:RRC:MTONe?
Multi-Carrier
Indicates whether the UE supports multi-carrier operation.
This information is received in an RRC connection request.
Remote command:
SENSe:NIOT:SIGN:UECapability:RRC:MCARrier?
User Manual 1178.5689.02 ─ 12 37

GUI Reference
User Plane C-IoT Optimization

Indicates whether the UE supports user plane C-IoT EPS optimization.
This information is received in an RRC connection setup complete message.
Remote command:
SENSe:NIOT:SIGN:UECapability:RRC:UPLane?
General UE Capability Information

The UE capability information in this section and the following sections is received after
authentication. It is sent by the UE in the information element "UE-Capability-NB".
At the highest level, the information element lists the following information.
Figure 2-12: General UE capabilities
Release......................................................................................................................... 38
UE Category..................................................................................................................38
Multiple DRB................................................................................................................. 38
Release
Supported access stratum release.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:RELease?
UE Category
The UE category for NB-IoT is a combined uplink and downlink category. The meaning
of the category values is defined in 3GPP TS 36.306.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:CATegory?
Multiple DRB
Support of multiple data radio bearers.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:MDRB?
RF UE Capabilities
This section indicates the supported operating bands and other RF capabilities.
Figure 2-13: RF UE capabilities
User Manual 1178.5689.02 ─ 12 38

GUI Reference
Supported Bands.......................................................................................................... 39
Multi-NS-Pmax.............................................................................................................. 39
Power Class 14 dBm.....................................................................................................39
Supported Bands
The UE supports all listed operating bands.
Column "Power Class 20 dBm" indicates for each supported band, whether the UE
supports a power class with 20 dBm (class 5) in that band. "No" means that the UE
supports a power class with 23 dBm (class 3).
For NB-IoT power classes, see 3GPP TS 36.101, section 6.2.2F.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:BANDs?
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:BANDs:ALL?
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:POWClass?
Multi-NS-Pmax
Defines whether the UE supports the handling of multiple "NS-Pmax" values. The mul-
tiple values are broadcast as "NS-PmaxList-NB".
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:MPMax?
Power Class 14 dBm

Indicates whether the UE's maximum output power is 14 dBm (class 6).
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:POWFourteen
PDCP UE Capabilities
The following UE capability information indicates in which way the UE supports the
packet data convergence protocol (PDCP) described in 3GPP TS 36.323.
Figure 2-14: PDCP UE capabilities
Supported ROHC Profiles............................................................................................. 39

Max Num ROHC Context Sessions.............................................................................. 40
Supported ROHC Profiles

Support of the robust header compression profiles with the stated profile identifiers
(0x0002, 0x0003, ...).
The profiles are defined in 3GPP TS 36.323, Table 5.5.1.1.
User Manual 1178.5689.02 ─ 12 39

GUI Reference
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:PROFiles?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:ROHC?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:ROHC:ALL?
Max Num ROHC Context Sessions

Maximum number of header compression context sessions supported by the UE.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:MAXSessions?
MAC UE Capabilities
This section indicates MAC capabilities of the UE as specified in 3GPP TS 36.321.
Figure 2-15: MAC UE capabilities
Data Inactivity Monitoring

Indicates whether the UE supports data inactivity monitoring.
Remote command:
SENSe:NIOT:SIGN:UECapability:MAC:DINactmon?
Release Assistance Indication

Indicates whether the UE supports release assistance indication.
Remote command:
SENSe:NIOT:SIGN:UECapability:MAC:RELassind?
earlyData-UP
Indicates whether the UE supports early data transmission in user plane (UP) C-IoT
EPS optimized mode. (See also "C-IoT Optimization" on page 82.)
Remote command:
SENSe:NIOT:SIGN:UECapability:MAC:EDATa?
Physical Layer UE Capabilities

This section indicates physical layer capabilities of the UE.
Figure 2-16: Physical layer UE capabilities
User Manual 1178.5689.02 ─ 12 40

GUI Reference
Multi-Tone......................................................................................................................41
Multi-Carrier.................................................................................................................. 41
Multi-Carrier NPRACH.................................................................................................. 41
Two HARQ Processes.................................................................................................. 41
Interference Randomization.......................................................................................... 41
SR with HARQ-ACK / SR without HARQ-ACK............................................................. 41
Multi-Tone
Indicates whether the UE supports NPUSCH multi-tone transmissions.
This information is received in the information element "UE-Capability-NB".
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MTONe?
Multi-Carrier
Indicates whether the UE supports multi-carrier operation.
This information is received in the information element "UE-Capability-NB".
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MCARrier?
Multi-Carrier NPRACH
Indicates whether the UE supports NPRACH on non-anchor carrier, as specified in
3GPP TS 36.321 and 36.331.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MCRRier:
NPRach?
Two HARQ Processes

Indicates whether the UE supports two HARQ processes in DL and UL.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:TWOHarq?
Interference Randomization
Indicates whether the UE supports interference randomization in connected mode as
specified in 3GPP TS 36.211.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:INTRand?
SR with HARQ-ACK / SR without HARQ-ACK

Indicates whether the UE supports a scheduling request (SR) with HARQ acknowledg-
ment and SR without HARQ-ACK.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:SR:HARQack:
WITH
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:SR:HARQack:
WOUT
User Manual 1178.5689.02 ─ 12 41

GUI Reference
Paging UE Capabilities
This section indicates paging capabilities of the UE.
Figure 2-17: Paging UE capabilities
Multi-Carrier Paging...................................................................................................... 42
Wake Up Signal.............................................................................................................42
WUS Min Gap eDRX.....................................................................................................42
Multi-Carrier Paging
Indicates whether the UE supports paging on non-anchor carriers, as specified in
3GPP TS 36.304.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:MTICarrier?
Wake Up Signal
Indicates whether the UE supports wake up signal (WUS) for paging in DRX in FDD.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:WUS:ENABle?
WUS Min Gap eDRX

Indicates the minimum gap the UE supports between WUS and associated paging
occasion (PO) for eDRX as specified by 3GPP in TS 36.304.
Remote command:
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:WUS:MINGap:EDRX?
2.3.1.5 UE Measurement Report
Access: NB-IoT signaling main view > below the "Event Log" area, select "UE Mea-
surement Report".
The displayed information is retrieved from measurement reports provided by the con-
nected UE. The individual report values are defined in 3GPP TS 36.133.
Figure 2-18: Measurement report in the main view
The minimized default presentation shows all measurement report values for the serv-
ing NB-IoT cell.
To maximize the area also horizontally, press the button again.
User Manual 1178.5689.02 ─ 12 42

GUI Reference
The measurement results are described in the following.
RSRP for serving NB-IoT cell

The reference signal received power (RSRP) denotes the average power of the
resource elements carrying cell-specific reference signals.
The measurement report displays the reported dimensionless value and in brackets
the corresponding measured value range.
Remote command:
SENSe:NIOT:SIGN:UEReport:RSRP?
SENSe:NIOT:SIGN:UEReport:RSRP:RANGe?
RSRQ for serving NB-IoT cell

The reference signal received quality (RSRQ) is calculated as RSRQ = N×RSRP / (E-
UTRA carrier RSSI). N is the number of resource blocks in the measurement band-
width. The "E-UTRA carrier RSSI" denotes the average of the total received power
(including interferers, and so on), observed in OFDM symbols containing reference
symbols for antenna port 0.
The measurement report displays the reported dimensionless value and in brackets
the corresponding measured value range.
Remote command:
SENSe:NIOT:SIGN:UEReport:RSRQ?
SENSe:NIOT:SIGN:UEReport:RSRQ:RANGe?
2.3.1.6 Settings
Access: NB-IoT signaling main view > "Cell" and "Connection" areas
The main view provides the most important settings for fast access.
Figure 2-19: Settings in the main view
User Manual 1178.5689.02 ─ 12 43

GUI Reference
Upper Part
The upper part contains the following settings:
● RF frequency settings
See Chapter 2.3.5.2, "RF Frequency", on page 50
● Most important DL power parameters
See Chapter 2.3.7, "Downlink Power Levels", on page 57
● Most important UL power parameters
See Chapter 2.3.8, "Uplink Power Control", on page 58 and "UL Subcarrier Spac-
ing" on page 62
Lower Part
The contents of the lower part depend on the scheduling type. Refer to:
● Chapter 2.3.11.2, "UL RMC Connection Settings", on page 84
● Chapter 2.3.11.3, "DL RMC Connection Settings", on page 85
● Chapter 2.3.11.4, "User-Defined Scheduling Settings", on page 86
2.3.2 Signaling Control
The individual connection states are controlled via the ON | OFF key, via hotkeys and
via the UE.
The available hotkeys depend on the current connection state. All possible hotkeys are
described in the following.
For background information, refer to Chapter 2.2.4, "Connection States", on page 16.
ON | OFF (key) / NB-IoT Signaling (softkey).................................................................44
Connection control hotkeys...........................................................................................44
ON | OFF (key) / NB-IoT Signaling (softkey)
To turn the DL signal transmission on or off, use the ON | OFF key or right-click the
softkey. The current state is shown by the softkey. The signal transmission can be
switched off any time, independent of the current connection state. A yellow hour glass
symbol indicates that the signaling generator is turned on or off.
Remote command:
SOURce:NIOT:SIGN:CELL:STATe
SOURce:NIOT:SIGN:CELL:STATe:ALL?
Connection control hotkeys

Any interaction with a UE requires an NB-IoT downlink signal (cell). If the signal is
available (state ON, no hour glass), the UE can attach and connection control hotkeys
can be present in the hotkey bar.
The possible hotkeys are listed in the following table.
User Manual 1178.5689.02 ─ 12 44

GUI Reference
Hotkey Description
"Connect" Sets up an RRC connection.

The RRC state changes from "Idle" to "Connected".
"Disconnect" Releases the RRC connection.

The RRC state changes from "Connected" to "Idle".
"Detach" Send a detach request to the UE and detach the UE (independent of UE

reaction to the request).
"Send SMS" Send an SMS message to the UE.
"Suspend" Suspends the RRC connection.

The RRC state changes from "Connected" to "Idle", the UE stores the AS
context.
Prerequisites: at least one active data radio bearer and enabled checkbox
Release Cause
"Resume" Resumes a suspended RRC connection.

The RRC state changes from "Connected" to "Idle". Radio bearer is auto-
matically set up, the AS context stored by the UE is used.
Remote command:
CALL:NIOT:SIGN:PSWitched:ACTion
2.3.3 Using the Shortcut Softkeys
When using the NB-IoT signaling application and an NB-IoT measurement in parallel,
use a shortcut softkey to switch to the measurement.
Using one of these softkeys, ensures that the measurement is configured compatible
to the settings of the signaling application. When you use the softkey to switch to a TX
measurement, the combined signal path scenario is activated automatically in the mea-
surement.
Consequences:
● The measurement and the signaling application can be used in parallel, i.e. both
DL signal transmission and measurement can be switched on.
● The signaling RF settings are also used for the measurement.
● Some measurement control settings are configured compatible with the signaling
settings.
● A suitable trigger signal provided by the signaling application is selected as trigger
source for the measurement.
If the softkey label equals "Go to...", the softkey opens a dialog box with a list of all
available measurements. If the softkey label indicates a measurement name instead of
User Manual 1178.5689.02 ─ 12 45

GUI Reference
"Go to...", this measurement has been assigned to the softkey as fixed target, see
Chapter 2.3.15, "Shortcut Configuration", on page 110.
Three shortcut softkeys are available and can be set to different fixed targets.
Figure 2-20: Dialog box opened by Go to... softkey
Select Menu
Selects the target measurement you want to switch to.
Select as fixed target

Sets the selected measurement as fixed target of the softkey. The softkey label indi-
cates the measurement name and switches directly to the selected target without
opening the dialog box.
When the dialog box has been disabled, you can still change the target measurement
or re-enable the dialog box using the configuration menu, see Chapter 2.3.15, "Short-
cut Configuration", on page 110.
Go to / Cancel
Press the "Go to" button to switch to the selected measurement or "Cancel" to abort.
2.3.4 General Settings
Access: "NB-IoT Signaling" softkey > "Config" hotkey > top of the configuration dialog.
The general settings are at the top of the configuration dialog. Configure them accord-
ing to your test scenario, before configuring any other settings.
Figure 2-21: Top of dialog
The general settings are described in the following.
Scenario
Different test scenarios require different sets of parameters. Selecting a scenario hides/
shows parts of the GUI as required by the scenario. The active scenario determines,
for example, whether fading is used. It determines also the number of component carri-
ers.
The current software version supports only the "Standard Cell" scenario.
● "Standard Cell":
Standard LTE cell with one RF input path and one RF output path.
User Manual 1178.5689.02 ─ 12 46

GUI Reference
● "Standard Cell Fading":

"Standard Cell" plus fading and/or AWGN insertion.
An additional parameter "Fader" is displayed, refer to Fading.
Options R&S CMW-KE100/-KE500 are required.
● "1CC - Fading - 2x1":
Tx diversity with fading: Two signals of one NB-IoT cell transmitted via two antenna
ports are faded and combined to one RF output connector.
Tx diversity increases the signal to noise ratio at the receiver side and thus the
robustness of data transmission with fading.
An additional parameter "Fader" is displayed, refer to Fading.
Options R&S CMW-KE100/-KE500 are required.
Remote command:
ROUTe:NIOT:SIGN:SCENario[:FLEXible]:SCELl
ROUTe:NIOT:SIGN:SCENario:SCFading[:FLEXible]:INTernal
ROUTe:NIOT:SIGN:SCENario:TROFading[:FLEXible]:INTernal
Fading
This parameter is displayed for the fading scenarios. Only internal fading is supported.
The fader setting selects an SUA partition. The numbering is reversed, so that the low-
est fader number selects the highest SUA partition. This reverse numbering allows you
to select the same number for the fader and the baseband unit, because they address
different SUA partitions.
Example: Baseband unit "2.SUA4" selects SUA partition 4 in CMW 2. Fader "2.Fader4"
selects SUA partition 1 in CMW 2. So they can be combined.
The fader selection offers only values compatible with the baseband setting. If there is
only one possible value, the selection is grayed out, displaying this value.
Remote command:
Base Band Unit

Selects the signaling unit to be used. This setting is especially useful for multi-CMW
setups, to control which instrument is used.
Remote command:
2.3.5 RF Settings
Access: "Config" hotkey > "RF Settings" section.

The parameters in this section configure the RF input and output paths.
User Manual 1178.5689.02 ─ 12 47

GUI Reference
Figure 2-22: RF settings
For descriptions of the parameters, refer to the subsections.

● RF Signal Routing................................................................................................... 48
● RF Frequency......................................................................................................... 50
● Expected Uplink Power........................................................................................... 51
2.3.5.1 RF Signal Routing
Access: "Config" hotkey > "RF Settings" > "RF Output (TX)" and "RF Input (RX)" sec-
tions.
This section configures the RF input path and the RF output path.
Depending on your hardware configuration, there are dependencies between some

parameters. Configure the settings in the following order to access all possible values:
1. Select the signaling unit. See "Base Band Unit" on page 47.
In a multi-CMW setup, this action selects also the instrument.
2. Select the RF connector.
3. Select the RF converter.
Figure 2-23: RF path settings
RF Output (TX)..............................................................................................................49
└ Connector, Converter......................................................................................49
└ External Attenuation........................................................................................49
└ External Delay Compensation........................................................................ 49
RF Input (RX)................................................................................................................ 49
└ Connector, Converter......................................................................................49
└ External Attenuation........................................................................................49
└ External Delay Compensation........................................................................ 50
User Manual 1178.5689.02 ─ 12 48

GUI Reference
RF Output (TX)
The following parameters configure the RF output path of the R&S CMW.
Connector, Converter ← RF Output (TX)

Selects the output path for the generated RF signals, that means the output connector
and the TX module.
Remote command:
External Attenuation ← RF Output (TX)

Defines the value of an external attenuation (or gain, if the value is negative) in the out-
put path. With an external attenuation of x dB, the power of the generated signal is
increased by x dB. The actual generated levels are equal to the displayed values plus
the external attenuation.
If a correction table for frequency-dependent attenuation is active for the chosen con-
nector, the table name and a button are displayed. Press the button to display the table
entries.
Remote command:
CONFigure:NIOT:SIGN:RFSettings:EATTenuation:OUTPut<n>
External Delay Compensation ← RF Output (TX)

Defines the value of an external time delay in the output path. A delay can, for exam-
ple, be caused by a long optical fiber cable or by an additional instrument in the output
path.
As a result, the downlink signal is sent earlier, so that the downlink signal arrives at the
UE without delay.
Remote command:
CONFigure:NIOT:SIGN:RFSettings:EDC:OUTPut
RF Input (RX)
The following parameters configure the RF input path of the R&S CMW.
Connector, Converter ← RF Input (RX)

Selects the input path for the measured RF signal, i.e. the input connector and the RX
module to be used.
Remote command:
External Attenuation ← RF Input (RX)

Defines the value of an external attenuation (or gain, if the value is negative) in the
input path. The power readings are corrected by the external attenuation value.
The external attenuation value is also used in the calculation of the maximum configu-
rable input power value.
nector, then the table name and a button are displayed. Press the button to display the
table entries.
User Manual 1178.5689.02 ─ 12 49

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:RFSettings:EATTenuation:INPut
External Delay Compensation ← RF Input (RX)

Defines the value of an external time delay in the input path, for example caused by a
long optical fiber cable.
The signaling application uses this information to compensate for the delay and to syn-
chronize the uplink and the downlink despite the delay.
Remote command:
CONFigure:NIOT:SIGN:RFSettings:EDC:INPut
2.3.5.2 RF Frequency
Access: "Config" hotkey > "RF Settings" > "RF Frequency" section.
This section configures the operating band and the channel/frequency for uplink and
downlink.
The uplink settings configure the center frequency of the RF analyzer. The downlink
settings configure the carrier center frequency of the generated NB-IoT signal.
Figure 2-24: Frequency settings
Operating Band, Channel, Frequency...........................................................................50

Frequency Offset...........................................................................................................51
User-Defined Band Definition........................................................................................51
Operating Band, Channel, Frequency

To specify the DL and UL frequencies, select an operating band first, then enter a valid
channel number or frequency for UL or DL. The related frequency or channel number
and the parameters for the other direction are calculated automatically.
The relation between operating band, carrier frequencies and channel numbers is
defined by 3GPP (see Chapter 2.2.11, "Operating Bands", on page 27).
In standalone operation, you can also define your own operating band, see User-
Defined Band Definition.
User Manual 1178.5689.02 ─ 12 50

GUI Reference
In guard-band and in-band operation, there are channel raster offsets added to the
configured RF frequencies, see Chapter 2.2.5, "Operation Modes", on page 18.
Remote command:
CONFigure:NIOT:SIGN:BAND
CONFigure:NIOT:SIGN:RFSettings:CHANnel:DL
CONFigure:NIOT:SIGN:RFSettings:CHANnel:UL
CONFigure:NIOT:SIGN:RFSettings:ALL:BWCHannel
Frequency Offset
You can specify positive or negative offsets to be added to the carrier center frequen-
cies. This setting is useful, for example, if the UE has a frequency offset relative to the
channels defined by 3GPP.
Remote command:
CONFigure:NIOT:SIGN:RFSettings:FOFFset:DL
CONFigure:NIOT:SIGN:RFSettings:FOFFset:UL
User-Defined Band Definition

Configures your own operating band. Enabling user-defined band sets also operating
band to "User Defined", see Operating Band, Channel, Frequency.
To configure the DL and UL frequencies, specify first a UL/DL separation and downlink
minimum frequency value. Set the frequency range indirectly via minimum and maxi-
mum channel numbers. The related UL frequency range is calculated automatically.
Set the UL minimum channel to define channel numbering in uplink.
The band indicator is configurable. The supported channel spacing is fixed (100 kHz).
User-defined bands are relevant for standalone operation only.
Remote command:
CONFigure:NIOT:SIGN:RFSettings:UDEFined:SET
CONFigure:NIOT:SIGN:RFSettings:UDEFined:CHANnel:UL:MAXimum?
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:DL:MAXimum?
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:UL:MAXimum?
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:UL:MINimum?
2.3.5.3 Expected Uplink Power
Access: "Config" hotkey > "RF Settings" > "RF Power Uplink" section.
The following parameters configure the expected uplink power.
Figure 2-25: RF uplink power settings
User Manual 1178.5689.02 ─ 12 51

GUI Reference
Exp. Nominal Power..., Margin

These parameters configure the expected UL power. Two modes are available:
● "According to UL Power Control Settings"
The UL power is calculated automatically from the UL power control settings. The
resulting expected nominal power is displayed for information. The displayed refer-
ence level is calculated as:
Reference Level = Expected Nominal Power + 12 dB Margin
For UL power control settings, see Chapter 2.3.8, "Uplink Power Control",
on page 58.
● "Manual"
In manual mode, the expected nominal power and a margin can be defined man-
ually. The displayed reference level is calculated as:
Reference Level = Expected Nominal Power + Margin
The margin is used to account for the known variations (crest factor) of the RF input
signal power.
Note: The actual input power at the connectors must be within the level range of the
selected RF input connector; refer to the data sheet. If all power settings are config-
ured correctly, the actual power equals the "Reference Level" minus the "External
Attenuation (Input)" value.
Remote command:
CONFigure:NIOT:SIGN:RFSettings:ENPMode
CONFigure:NIOT:SIGN:RFSettings:ENPower
CONFigure:NIOT:SIGN:RFSettings:UMARgin
Mixer Level Offset

Varies the input level of the mixer in the analyzer path. A negative offset reduces the
mixer input level. A positive offset increases the level. Optimize the mixer input level
according to the properties of the uplink signal.
Mixer level Advantages Possible shortcomings

offset
< 0 dB Suppression of distortion (e.g. of the inter- Lower dynamic range (due to smaller sig-
modulation products generated in the nal-to-noise ratio)
mixer)
> 0 dB High signal-to-noise ratio, higher dynamic Risk of intermodulation, smaller overdrive
range reserve
Remote command:
CONFigure:NIOT:SIGN:RFSettings:MLOFfset
Access: "Config" hotkey > "Internal Fading" section.

This node is only visible, if a fading scenario is selected.
For general prerequisites/required options and background information, see Chap-
ter 2.2.3, "Internal Fading", on page 15.
User Manual 1178.5689.02 ─ 12 52

GUI Reference
Figure 2-26: Internal fading settings
Access: "Config" hotkey > "Internal Fading" node > "Fading Simulator (Extended)" sec-
tion.
The node enables and sets up the fading simulator. For background information, see
Chapter 2.2.3.1, "Fading Simulator", on page 15.
Only extended fading is supported. Standard fading is no longer relevant.
Figure 2-27: Fading simulator settings
For carrier aggregation scenarios, you can configure all settings per component carrier.
Enable........................................................................................................................... 53
Profile............................................................................................................................ 53
Restart Event................................................................................................................ 54
Start Seed..................................................................................................................... 54
Insertion Loss................................................................................................................54
Doppler Frequency Mode, Doppler Frequency............................................................. 55
Enable
Enables/disables the fading simulator.
Remote command:
CONFigure:NIOT:SIGN:FADing:FSIMulator:ENABle
Profile
Selects a propagation condition profile.
User Manual 1178.5689.02 ─ 12 53

GUI Reference
The following profiles are available:

● Delay profiles for low, medium and high delay spread environments:
– "Extended pedestrian A" model (EPA), maximum Doppler frequency 5 Hz
– "Extended vehicular A" model (EVA), maximum Doppler frequency 5 Hz, 70 Hz
or 200 Hz
– "Extended typical urban" model (ETU), maximum Doppler frequency 30 Hz, 70
Hz or 300 Hz
All profiles are available with low, medium and high correlation level.
The delay profiles are defined in 3GPP TS 36.101, annex B.2.
● High-speed train (HST) scenario defined in 3GPP TS 36.101, annex B.3
● Multi-path profile used for CQI tests with parameter specifications of 3GPP TS
36.521-1, chapter 9.3 "CQI Reporting under fading conditions"
Remote command:
CONFigure:NIOT:SIGN:FADing:FSIMulator:PROFile
Restart Event
There are the following modes.
"Auto" Fading starts automatically with the downlink signal.
"Manual" Fading is started and restarted manually. A "Restart" button is dis-
played.
Remote command:
CONFigure:NIOT:SIGN:FADing:FSIMulator:RESTart:MODE
CONFigure:NIOT:SIGN:FADing:FSIMulator:RESTart
Start Seed
Sets the start seed for the pseudo-random fading algorithm. This setting ensures
reproducible fading conditions.
Remote command:
CONFigure:NIOT:SIGN:FADing:FSIMulator:GLOBal:SEED
Insertion Loss
The insertion loss is the attenuation at the fader input. It can be calculated automati-
cally or you can define it manually.
"Normal" The insertion loss is calculated automatically, based on the currently
selected Profile.
"User" Specify the insertion loss value. A lower insertion loss allows for a
higher downlink power but can result in clipping.
You can use the displayed information "Clipped Samples" to find the
lowest insertion loss value for which no clipping occurs. For scenarios
with several output paths, the information is displayed per path.
Remote command:
CONFigure:NIOT:SIGN:FADing:FSIMulator:ILOSs:MODE
CONFigure:NIOT:SIGN:FADing:FSIMulator:ILOSs:LOSS
SENSe:NIOT:SIGN:FADing:FSIMulator:ILOSs:
CSAMples<ClippingCounter>?
User Manual 1178.5689.02 ─ 12 54

GUI Reference
Doppler Frequency Mode, Doppler Frequency

The maximum Doppler frequency can be calculated automatically or you can define it
manually.
"Normal" The maximum Doppler frequency is calculated automatically, based
on the currently selected Profile.
"User" Specify the maximum Doppler frequency.
Remote command:
CONFigure:NIOT:SIGN:FADing:FSIMulator:DSHift:MODE
CONFigure:NIOT:SIGN:FADing:FSIMulator:DSHift
2.3.6.2 DL Settings
Access: "Config" hotkey > "Internal Fading" node > "DL Settings" section.
The node displays noise power values, calculated from the downlink power, the cell
bandwidth and the fading module AWGN settings.
For carrier aggregation scenarios, this information is available per component carrier.
The reference point for the power values is the RF output connector.
Figure 2-28: Noise information
Noise (System BW) Power

Displays the noise power on the downlink channel, i.e. within the cell bandwidth.
Remote command:
CONFigure:NIOT:SIGN:FADing:POWer:NOISe?
Noise (Total BW) Power

Displays the total noise power, within and outside of the cell bandwidth.
The total noise power is irrelevant for 3GPP test cases. They specify the SNR or the
noise power within the cell bandwidth. The total noise power is only displayed for com-
patibility reasons with Rohde & Schwarz signal generators.
Remote command:
CONFigure:NIOT:SIGN:FADing:POWer:NOISe:TOTal?
Signal + Noise (System BW) Power

Displays the total power (signal + noise) on the downlink channel, i.e. within the cell
bandwidth.
Remote command:
CONFigure:NIOT:SIGN:FADing:POWer:SUM?
User Manual 1178.5689.02 ─ 12 55

GUI Reference
2.3.6.3 Fading Module AWGN
Access: "Config" hotkey > "Internal Fading" node > "Fading Module AWGN" section.
The node enables and configures the AWGN insertion via the fading module. For back-
ground information, see Chapter 2.2.3.2, "AWGN Generator", on page 16.
Figure 2-29: AWGN settings
For carrier aggregation scenarios, you can configure the settings per component car-
rier.
If you combine contiguous carrier aggregation with AWGN, we recommend the follow-
ing AWGN settings:
● Enable AWGN for one carrier only.
● Configure the frequency offset to shift the noise center frequency to the center fre-
quency of the aggregated bandwidth.
● Increase the "Min. Noise/System BW Ratio" so that the noise bandwidth equals the
aggregated bandwidth.
These settings avoid undesired effects due to overlapping noise bandwidths of adja-
cent carriers.
Enable
Enables/disables AWGN insertion via the fading module.
Remote command:
CONFigure:NIOT:SIGN:FADing:AWGN:ENABle
Frequency Offset
Shifts the center frequency of the noise bandwidth relative to the carrier center fre-
quency.
Remote command:
CONFigure:NIOT:SIGN:FADing:AWGN:FOFFset
Min. Noise/System BW Ratio

Configures the minimum ratio between the noise bandwidth and the cell bandwidth.
Remote command:
CONFigure:NIOT:SIGN:FADing:AWGN:BWIDth:RATio
Noise Bandwidth
Displays the actual noise bandwidth, resulting from the "Min. Noise/System BW Ratio"
and the cell bandwidth.
User Manual 1178.5689.02 ─ 12 56

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:FADing:AWGN:BWIDth:NOISe?
Effective Signal BW
Displays the part of the cell bandwidth that is dedicated to the downlink subcarriers.
Signal/Noise Ratio
Specifies the signal to noise ratio.
Remote command:
CONFigure:NIOT:SIGN:FADing:AWGN:SNRatio
2.3.7 Downlink Power Levels
Access: "Config" hotkey > "Downlink Power Levels" section.

This section defines power levels of physical downlink channels and physical downlink
signals.
Figure 2-30: DL power levels
NRS EPRE....................................................................................................................57
NPDSCH, NPDCCH, NPBCH EPRE............................................................................ 57
OCNG........................................................................................................................... 57
AWGN........................................................................................................................... 58
NRS EPRE
Defines the energy per resource element (EPRE) of the narrowband reference signal
(NRS). The NRS EPRE corresponds to the DL power averaged over all resource ele-
ments carrying the NRS within one subcarrier (15 kHz).
The power offset of the NPSS and the NSSS EPRE relative to the NRS EPRE is 0 dB.
Remote command:
CONFigure:NIOT:SIGN:DL:NRSepre:LEVel
NPDSCH, NPDCCH, NPBCH EPRE

Displays the energy per resource element (EPRE) of the NPDSCH, NPDCCH and
NPBCH.
The power offset relative to the NRS EPRE is 0 dB for 1 antenna port, as defined in
3GPP TS 36.213, section 16.2.2.
OCNG
Enables or disables the OFDMA channel noise generator (OCNG). OCNG for NB-IoT
is defined in 3GPP TS 26.101, annex A.5.3.
User Manual 1178.5689.02 ─ 12 57

GUI Reference
If the checkbox is enabled, the OCNG signal is sent in all unused downlink subframes
and covers the entire channel bandwidth. OCNG is not used to fill partly used sub-
frames, only to fill unused subframes.
The EPRE for OCNG equals the NRS EPRE. The signal uses QPSK modulation and
contains uncorrelated pseudo random data.
Remote command:
CONFigure:NIOT:SIGN:DL:OCNG
AWGN
Total level of the additional white Gaussian noise (AWGN) interferer in dBm/15 kHz
(the spectral density integrated across one subcarrier). The reference point for this
power setting is the RF output connector.
If the checkbox is enabled, the AWGN signal is added to the DL signal for the entire
channel bandwidth.
Remote command:
CONFigure:NIOT:SIGN:DL:AWGN
2.3.8 Uplink Power Control
This section defines parameters related to the control of the UE uplink power by the
instrument.
2.3.8.1 General Power Control Parameters
Access: "Config" hotkey > "Uplink Power Control" > highest level of the "Uplink Power
Control" section.
Figure 2-31: UL power control settings, highest level
Uplink Nominal Power...................................................................................................58

Exp. NPRACH Preamble Power................................................................................... 59
Exp. NPUSCH Format 1/2 Nom. Power........................................................................59
Max. Allowed Power P-Max.......................................................................................... 59
Uplink Nominal Power

Defines a nominal power value for the UL, applicable if the indicated subcarrier alloca-
tion is used. The indicated subcarrier allocation is the maximum allocation allowed for
the configured subcarrier spacing.
If the UE transmits an NPUSCH with this subcarrier allocation, the expected transmit
power equals the configured value.
User Manual 1178.5689.02 ─ 12 58

GUI Reference
The parameter is part of the basic UL power settings. It is only relevant and configura-
ble if the "Advanced NPRACH/NPUSCH Power" settings are disabled. The power val-
ues sent to the UE are calculated from the "Uplink Nominal Power" and are displayed
in the node "Advanced NPRACH and NPUSCH Power".
Remote command:
CONFigure:NIOT:SIGN:UL:NPUSch:ULNPower
Exp. NPRACH Preamble Power

Displays the expected power of the first preamble.
The value depends on the "preambleInitialReceivedTargetPower" ("Preamble Initial
Received Target Power" on page 60) and on the pathloss. For details, see 3GPP TS
36.321 section 5.1.
Maximum UE TX power limitations, for example due to the UE category, are not con-
sidered.
Remote command:
SENSe:NIOT:SIGN:UL:ADPower:ENPPpower?
Exp. NPUSCH Format 1/2 Nom. Power

Displays the expected NPUSCH power, for the NPUSCH formats 1 and 2, according to
3GPP TS 36.213, section 16.2.1.1.1. The calculation does not consider maximum UE
TX power limitations, for example, due to the UE category.
Most of the advanced power settings influence this value.
You can use the displayed values to verify your configuration: With a correct configura-
tion, the expected NPRACH power and the expected NPUSCH format 1 power are
close together. Otherwise, the NPRACH cannot be detected and the attach procedure
fails.
Remote command:
SENSe:NIOT:SIGN:UL:ADPower:EFNPower<format>?
Max. Allowed Power P-Max

Specifies the maximum allowed output power for the UE in the cell. The UE output
power must not exceed this value.
If the checkbox is enabled, the configured value is signaled to the UE within the system
information. If it is disabled, the parameter has no effect.
Remote command:
CONFigure:NIOT:SIGN:UL:PMAX
2.3.8.2 Advanced NPRACH and NPUSCH Power Settings
Access: "Config" hotkey > "Uplink Power Control" > "Advanced NPRACH/NPUSCH
Power" section.
By default, the basic settings apply. Only the "Uplink Nominal Power" is configurable.
The advanced settings are not configurable and the grayed-out values indicate the
used basic settings.
User Manual 1178.5689.02 ─ 12 59

GUI Reference
If you enable the advanced settings, the grayed-out values become configurable.
Instead, the "Uplink Nominal Power" parameter is disabled.
Figure 2-32: Advanced power settings
Enable Advanced Settings............................................................................................ 60

NRS Power................................................................................................................... 60
Pathloss........................................................................................................................ 60
Preamble Initial Received Target Power....................................................................... 60
P0 Nominal NPUSCH................................................................................................... 61
Pathloss Compensation Alpha...................................................................................... 61
Enable Advanced Settings

Enables configuration of the advanced parameters.
If disabled, the following parameters are grayed out and display the used basic set-
tings.
Remote command:
CONFigure:NIOT:SIGN:UL:ADPower:ENABle
NRS Power
Specifies the parameter "nrs-Power", signaled to the UE as NPDSCH configuration
parameter (see 3GPP TS 36.331, section 6.7.3.2).
The value is used by the UE to determine the pathloss, see 3GPP TS 36.213 section
16.2.1.1.
Remote command:
CONFigure:NIOT:SIGN:UL:ADPower:NRSPower
Pathloss
Displays the pathloss resulting from the "NRS Power" on page 60 and the "NRS
EPRE" on page 57.
Remote command:
SENSe:NIOT:SIGN:UL:ADPower:PATHloss?
Preamble Initial Received Target Power

Specifies the parameter "preambleInitialReceivedTargetPower", signaled to the UE as
common RACH parameter (see 3GPP TS 36.331, section 6.3.2).
In 3GPP TS 36.213, section 16.2.1.1 this parameter is called PO_PRE.
The value is used by the UE, for example, to calculate the power of the first preamble.
Remote command:
CONFigure:NIOT:SIGN:UL:ADPower:PIRPower
User Manual 1178.5689.02 ─ 12 60

GUI Reference
P0 Nominal NPUSCH
Specifies the parameter "p0-NominalNPUSCH", signaled to the UE as uplink power
control parameter (see 3GPP TS 36.331, section 6.7.3.2).
In 3GPP TS 36.213, section 16.2.1.1 this parameter is called PO_NOMINAL_NPUSCH,c.
Remote command:
CONFigure:NIOT:SIGN:UL:ADPower:PNNPusch
Pathloss Compensation Alpha

Specifies the parameter "alpha", signaled to the UE as uplink power control parameter
(see 3GPP TS 36.331, section 6.7.3.2).
In 3GPP TS 36.213, section 16.2.1.1 this parameter is called αc.
Remote command:
CONFigure:NIOT:SIGN:UL:ADPower:PCALpha
2.3.9 Physical Cell Setup
This section defines physical layer attributes of the simulated cell.

● General Physical Cell Settings................................................................................61
● In-Band / Guard-Band Configuration.......................................................................62
● NPRACH Configuration...........................................................................................65
● Coverage Enhancement Configuration................................................................... 66
● Wake Up Signal Configuration................................................................................ 67
● Early Data Transmission Configuration...................................................................69
2.3.9.1 General Physical Cell Settings
Access: "Config" hotkey > "Physical Cell Setup" > top of the "Physical Cell Setup" sec-
tion.
Figure 2-33: Cell parameters
Duplex Mode................................................................................................................. 61
UL Subcarrier Spacing.................................................................................................. 62
Physical Cell ID............................................................................................................. 62
Operation Mode............................................................................................................ 62
Duplex Mode
Selects the duplex mode. The current software version supports only FDD, not TDD.
Remote command:
CONFigure:NIOT:SIGN:DMODe
User Manual 1178.5689.02 ─ 12 61

GUI Reference
UL Subcarrier Spacing
Selects the uplink subcarrier spacing (3.75 kHz or 15 kHz).
Remote command:
CONFigure:NIOT:SIGN:CELL:SCSPacing
Physical Cell ID
The cell ID is used for the generation of synchronization signals. During cell search,
the UE determines the cell ID from the secondary synchronization signal.
The physical cell ID can be set independent of the cell identifier sent to the UE via
broadcast (see "E-UTRAN Cell Identifier" on page 75).
Remote command:
CONFigure:NIOT:SIGN:CELL:PCID
Operation Mode
Selects the operation mode. The UE is informed about this setting via the "operation-
ModeInfo" in the master information block (MIB).
For the "Standalone Mode", there are no specific additional settings. For the other
modes, configure also the "In-Band / Guard-Band" settings.
Remote command:
CONFigure:NIOT:SIGN:CELL:OPERmode
2.3.9.2 In-Band / Guard-Band Configuration
Access: "Config" hotkey > "Physical Cell Setup" > "In-Band / Guard-Band" section.
This node configures settings for the operation modes "Guard-Band Operation" and
"In-Band Operation".
For background information, see Chapter 2.2.5, "Operation Modes", on page 18.
Figure 2-34: In-band /guard-band configuration
Enable Flexible UL/DL Separation................................................................................ 63

LTE Bandwidth.............................................................................................................. 63
LTE Control Region Size...............................................................................................63
NRS-CRS Power Offset................................................................................................ 63
In-Band PCI...................................................................................................................63
User Manual 1178.5689.02 ─ 12 62

GUI Reference
In-Band (DL/UL) Carrier Position.................................................................................. 64

Guard-Band Carrier Position.........................................................................................64
Guard-Band Uplink Carrier Position..............................................................................64
LTE Frequency..............................................................................................................64
NB-IoT Channel Raster Offset...................................................................................... 65
Enable Flexible UL/DL Separation

When enabled, UL and DL frequencies can be configured independently, ignoring the
fixed "UL/DL Separation" value, see "User-Defined Band Definition" on page 51.
When disabled, changing the frequency in one direction changes also the frequency in
the other direction using fixed "UL/DL Separation" value.
Remote command:
CONFigure:NIOT:SIGN:CELL:IBGBand:FLEXdlul:ENABle
LTE Bandwidth
Channel bandwidth for the generated LTE signal.
Remote command:
CONFigure:NIOT:SIGN:CELL:IBGBand:BANDwidth
LTE Control Region Size

Only for the in-band operation mode.
Configures how many OFDM symbols at the beginning of each DL subframe are used
for the LTE PDCCH. These symbols cannot be used for NB-IoT. So a larger value
reduces the NB-IoT DL throughput.
The value is signaled to the UE in the system information (SIB1-NB, eutraControlRe-
gionSize).
Remote command:
CONFigure:NIOT:SIGN:CELL:IBGBand:CRSize
NRS-CRS Power Offset

Defines the power offset of the NB-IoT NRS symbols relative to the LTE CRS symbols.
For "In-Band Operation" with "Same PCI", this information is signaled to the UE in the
system information (SIB1-NB, nrs-CRS-PowerOffset).
Remote command:
CONFigure:NIOT:SIGN:CELL:IBGBand:POFFset
In-Band PCI
Only for the in-band operation mode. Selects whether the NB-IoT cell uses the same
physical cell ID as the LTE cell.
The UE is informed about this setting via the "operationModeInfo" in the MIB.
"Same PCI" Signaling value "Inband-SamePCI". The NB-IoT cell and the LTE cell
share a physical cell ID. The UE can use the LTE cell-specific refer-
ence signal (CRS).
"Different PCI" Signaling value "Inband-DifferentPCI". The NB-IoT cell and the LTE
cell have different physical cell IDs. The UE must use the narrowband
reference signal (NRS).
User Manual 1178.5689.02 ─ 12 63

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:CELL:IBGBand:IPCI
In-Band (DL/UL) Carrier Position

Only for the in-band operation mode. Specifies the number of the LTE resource block
at the NB-IoT carrier position.
Modifying the "In-Band Carrier Position" shifts the LTE channel relative to the NB-IoT
carrier frequency, configured via the RF settings, see Chapter 2.3.5.2, "RF Frequency",
on page 50.
The shift of uplink channel can be specified individually.
● If disabled, the UL and DL carriers use the specified "In-Band Carrier Position"
PRB index value.
● If enabled, the UL carrier uses the specified "In-Band Uplink Carrier Position" and
DL carrier uses the "In-Band Carrier Position" PRB index value.
Only certain values are allowed, depending on the cell bandwidth, see Table 2-2.
Remote command:
CONFigure:NIOT:SIGN:CELL:IBGBand:IBCPosition
CONFigure:NIOT:SIGN:CELL:IBGBand:IBUCposition
Guard-Band Carrier Position

Only for the guard-band operation mode. Defines whether the NB-IoT carrier is located
in the lower guard band or in the upper guard band of an LTE channel.
The NB-IoT carrier frequency is configured via the RF settings, see Chapter 2.3.5.2,
"RF Frequency", on page 50.
Modifying the "Guard-Band Carrier Position" shifts the LTE channel relative to the NB-
IoT carrier.
For frequency and channel raster offsets, refer to Chapter 2.2.5.2, "Guard-Band Oper-
ation", on page 18.
Remote command:
CONFigure:NIOT:SIGN:CELL:IBGBand:GBCPosition
Guard-Band Uplink Carrier Position

Only for the guard-band operation mode. Specifies the individual shift of uplink channel
in LTE subcarrier index.
● If disabled, both UL and DL NB-IoT carriers use the default fixed subcarrier index
value.
● If enabled, the UL carrier uses the specified "Guard-band Uplink Carrier Position”"
subcarrier index value and DL carrier uses the default fixed subcarrier index value.
Remote command:
CONFigure:NIOT:SIGN:CELL:IBGBand:GBUCposition
LTE Frequency
Displays the center frequency of the generated LTE cell signal. The frequency is calcu-
lated from the NB-IoT RF frequency, the LTE cell bandwidth and the setting "In-Band
Carrier Position" or "Guard-Band Carrier Position".
For the standalone mode, no LTE cell signal is generated.
User Manual 1178.5689.02 ─ 12 64

GUI Reference
Remote command:
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:DL?
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:UL?
NB-IoT Channel Raster Offset

Displays the offset of the NB-IoT carrier center frequency from the channel raster, that
means from the configured RF frequency, see Chapter 2.3.5.2, "RF Frequency",
on page 50.
The center frequency of the NB-IoT carrier equals the configured RF frequency plus
the displayed offset.
The DL channel raster offset is signaled to the UE via the MIB.
For the standalone mode, the channel raster offset is zero.
Remote command:
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:DL?
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:UL?
2.3.9.3 NPRACH Configuration
Access: "Config" hotkey > "Physical Cell Setup" > NPRACH section.
This node configures settings related to the random access procedure.
Figure 2-35: NPRACH configuration
No Response to Preambles.......................................................................................... 65
Power Ramping Step.................................................................................................... 66
Preamble Format.......................................................................................................... 66
Max. Number of Preamble Transmissions.................................................................... 66
No Response to Preambles
By default, the signaling application responds to received preambles, so that the UE
can perform an attach. Alternatively, received preambles can be ignored (no
response), so that the UE continues to send preambles and NPRACH measurements
can be performed (included in R&S CMW-KM300).
"Off" The signaling application responds to received preambles.
"On" Any received preambles are ignored by the signaling application (no
response).
Remote command:
CONFigure:NIOT:SIGN:CELL:NPRach:NOResponse
User Manual 1178.5689.02 ─ 12 65

GUI Reference
Power Ramping Step

Specifies the transmit power difference between two consecutive preambles. This
value is broadcast to the UE.
If you set the step size to 0 dB, the preamble power is kept constant by the UE. Thus
you can use a constant expected nominal power setting during an NPRACH measure-
ment.
Remote command:
CONFigure:NIOT:SIGN:CELL:NPRach:PRAMping
Preamble Format
Selects the preamble format.
Format "0" CP length = 66.7 µs (2048 Ts), preamble duration = 5.6 ms
Format "1" CP length = 266.7 µs (8192 Ts), preamble duration = 6.4 ms
Remote command:
CONFigure:NIOT:SIGN:CELL:NPRach:PREFormat
Max. Number of Preamble Transmissions

The value is signaled to the UE as "preambleTransMax-CE".
Remote command:
CONFigure:NIOT:SIGN:CELL:NPRach:MAXTrans
2.3.9.4 Coverage Enhancement Configuration
Access: "Config" hotkey > "Physical Cell Setup" > Coverage Enhancement section.
The section configures the coverage enhancement (CE) parameters.
Figure 2-36: Coverage enhancement configuration
Number of Threshold.................................................................................................... 66
CE Level 0 to 2..............................................................................................................67
Repetitions per Preamble x...........................................................................................67
NPDCCH Num. Repetitions RA x................................................................................. 67
RSRP Threshold x........................................................................................................ 67
CE Level Report............................................................................................................67
Number of Threshold
The highest CE level supported by the eNodeB for NPRACH.
User Manual 1178.5689.02 ─ 12 66

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:CELL:CENHt:NTHReshold
CE Level 0 to 2
The UE selects one of these levels, see "RSRP Threshold".
A higher CE level means a higher coverage enhancement (for example more repeti-
tions / higher power).
Repetitions per Preamble x

Specifies the maximal number of repetitions per preamble transmission attempt (repeti-
tions with same preamble and power) for the selected CE level.
The setting is signaled to the UE via the field "numRepetitionPerPreambleAttempt".
Remote command:
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:ZERO
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:ONE
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:TWO
NPDCCH Num. Repetitions RA x

Sets the maximal number of NPDCCH repetitions during random access (RA) proce-
dure for the selected CE level.
Remote command:
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:ZERO
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:ONE
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:TWO
RSRP Threshold x
Threshold for selection of a CE level by the UE. The UE compares the measured
RSRP to the configured "RSRP Threshold" values and selects the CE level accord-
ingly. The value is signaled to the UE in "rsrp-ThresholdsPrachInfoList".
With increasing CE level, the "RSRP Threshold" setting must decrease. CE level 0 has
no "RSRP Threshold" setting. It can be used by the UE for all RSRP levels larger than
the "RSRP Threshold" of CE level 1.
Remote command:
CONFigure:NIOT:SIGN:CELL:CENHt:RSRPthr:ONE
CONFigure:NIOT:SIGN:CELL:CENHt:RSRPthr:TWO
CE Level Report
Queries the CE level reported by the UE.
Remote command:
SENSe:NIOT:SIGN:CELL:CENHt:REPCelev?
2.3.9.5 Wake Up Signal Configuration
Access: "Config" hotkey > "Physical Cell Setup" > "Wake Up Signal" section.
User Manual 1178.5689.02 ─ 12 67

GUI Reference
The section configures the parameters of information element (IE) WUS-Config-NB.

The IE is signaled to specify the wake-up signal (WUS) configuration according to
3GPP TS 36.331.
Figure 2-37: Wake up signal configuration
Enable WUS..................................................................................................................68
Disable Paging.............................................................................................................. 68
Max Duration Factor......................................................................................................68
Num POs.......................................................................................................................68
First PO Position........................................................................................................... 69
No. of DRX Cycles Relaxed.......................................................................................... 69
Time Offset....................................................................................................................69
Enable WUS
If enabled, the wake-up signal (WUS) configuration is provided in system information.
WUS indicates the upcoming paging occasion (PO) that has to be monitored by the UE
supporting WUS. The UE ignores all other POs (without WUS indication) and remains
in DRX or eDRX.
WUS events are displayed in the Event Log pane.
Remote command:
CONFigure:NIOT:SIGN:CELL:WUSignal:ENABle
Disable Paging
Disables or enables the paging associated with a WUS transmission.
The UE monitors all indicated POs anyway.
Remote command:
CONFigure:NIOT:SIGN:CELL:WUSignal:PAGing:DISable
Max Duration Factor

Sets the maximum WUS duration, expressed as a ratio of Rmax, refer to "Max. No. Rep-
etitions Rmax < UE Specific Search Space" on page 96.
Remote command:
CONFigure:NIOT:SIGN:CELL:WUSignal:DURFactor:MAX
Num POs
Sets the number of consecutive paging occasions (PO) mapped to one WUS. The val-
ues > 1 apply only to a UE in eDRX state.
User Manual 1178.5689.02 ─ 12 68

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:CELL:WUSignal:NUMPos
First PO Position
Sets the first PO to send paging.
Remote command:
CONFigure:NIOT:SIGN:CELL:WUSignal:NUMPos
No. of DRX Cycles Relaxed

Sets the maximum No. of consecutive DRX cycles during which the UE can skip serv-
ing cell measurement. Instead, the UE can use WUS for synchronization.
The parameter is relevant for the UE in DRX or eDRX state.
Remote command:
CONFigure:NIOT:SIGN:CELL:WUSignal:DRXCycles:RELaxed
Time Offset
Sets the offset from the end of the configured maximum WUS duration to the associ-
ated PO for DRX, eDRX with a short non-zero gap, or eDRX with long non-zero gap.
Remote command:
CONFigure:NIOT:SIGN:CELL:WUSignal:DRX:TOFFset
CONFigure:NIOT:SIGN:CELL:WUSignal:EDRX:TOFFset:SHORt
CONFigure:NIOT:SIGN:CELL:WUSignal:EDRX:TOFFset:LONG
2.3.9.6 Early Data Transmission Configuration
Access: "Config" hotkey > "Physical Cell Setup" > "Early Data Transmission" section.
Configures the early data transmission (EDT) for data transmission during the random
access procedure.
Figure 2-38: Wake up signal configuration
CP-EDT Enable / UP-EDT Enable................................................................................ 69

EDT Small TBS Subset Enable.....................................................................................70
EDT Small TBS Enabled...............................................................................................70
TBS............................................................................................................................... 71
CP-EDT Enable / UP-EDT Enable

Enables or disables early data transmission (EDT) in control plane (CP) and user plan
(UP) CIoT EPS optimized mode.
● For data application mode, the selection must follow the selection of C-IoT Optimi-
zation.
User Manual 1178.5689.02 ─ 12 69

GUI Reference
Refer to "Connection Type" on page 81

● For test mode, EDT is not supported.
You can check the UE capabilities in main view, see MAC UE Capabilities.
Remote command:
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:CPEDt
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:UPEDt
EDT Small TBS Subset Enable

The small transport block size (TBS) subset must be enabled for:
● UE performing CP-EDT with small TBS and small TBS subset
● CP-EDT on non-anchor carrier
● CP-EDT with non-IP data transmission
● UP-EDT UE capability display
● UP-EDT on non-anchor carrier
● UP-EDT on anchor carrier
● UP-EDT arrival event information
When EDT small TBS is enabled, the TBS values are used as follows:
Table 2-14: EDT TBS with edt-SmallTBS-Enabled set to true
For TBS set to EDT small TBS subset enable Supported TBS values
408 enabled / disabled 328, 408
504 enabled 328, 408, 504

disabled 408, 504
584 enabled 328, 408, 504, 584

disabled 408, 584
680 enabled 328, 456, 584, 680

disabled 456, 680
808 enabled 328, 504, 680, 808

disabled 504, 808
936 enabled 328, 456, 712, 936

disabled 504, 936
1000 enabled 328, 536, 778, 1000

disabled 536. 1000
Remote command:
CONFigure:NIOT:SIGN:CELL:EDT:SMALl:ENABle:TBS:SUBSet
EDT Small TBS Enabled

The small transport block size (TBS) must be enabled for:
● UE performing CP-EDT with small TBS and small TBS subset
● CP-EDT with different CE-levels
● CP-EDT on non-anchor carrier
● CP-EDT with non-IP data transmission
● UP-EDT UE capability display
● UP-EDT on non-anchor carrier
User Manual 1178.5689.02 ─ 12 70

GUI Reference
● UP-EDT on anchor carrier

● UP-EDT arrival event information
Remote command:
CONFigure:NIOT:SIGN:CELL:EDT:SMALl:ENABle:TBS
TBS
Transport block size depends on the number of resource units and MCS index.
Table 2-15: RUs and MCS for EDT
MCS Used MCS

index
for TBS = 328, 408, 504, or 584 for TBS = 608 for TBS = 808, 936, or 1000
3 3 3 4
4 4 4 5
5 5 5 6
6 6 8 8
7 8 10 10
Remote command:
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:TBS:VALue
2.3.10 Network Settings
The "Network" settings configure parameters of the simulated radio network.
Figure 2-39: Network settings
For parameter descriptions, refer to the subsections.

● Neighbor Cell Settings............................................................................................ 72
● Cell Reselection Settings........................................................................................ 73
● Identity.....................................................................................................................74
● Security................................................................................................................... 75
● UE Identity...............................................................................................................76
● Timers..................................................................................................................... 76
● Time........................................................................................................................ 78
● Synchronization.......................................................................................................79
User Manual 1178.5689.02 ─ 12 71

GUI Reference
2.3.10.1 Neighbor Cell Settings
Access: "Config" hotkey > "Network" > "Neighbor Cell" section.

This section defines neighbor cell information to be broadcast to the UE. You can
define several NB-IoT neighbor cell entries. The signaling messages for broadcast of
neighbor cell information are defined in 3GPP TS 36.331.
Figure 2-40: Neighbor cell settings
To configure the neighbor cell entries, press the "Edit" button.
Figure 2-41: Neighbor cell list configuration dialog
Only the enabled entries are broadcast.

The individual neighbor cell settings are described in the following.
NB-IoT
For an NB-IoT neighbor cell entry, you can specify the operating band and downlink
channel number, the physical layer cell ID and the "QOffset".
Parameter "QOffset" corresponds to the value "q-OffsetCell" in 3GPP TS 36.331,
which equals "Qoffsets,n" in 3GPP TS 36.304. It is used by the UE when evaluating
candidates for cell reselection or triggering conditions for measurement reporting.
If the channel number of an entry and the currently used channel number are identical,
the parameters are written into system information block 4 (intra-frequency cell rese-
lection). Otherwise they are written into system information block 5 (inter-frequency cell
reselection).
The list supports up to 16 active neighbor cell entries. The active entries can use up to
five different channel numbers. Active entries with the same channel number must
have different cell IDs.
Remote command:
CONFigure:NIOT:SIGN:NCELl:NIOT:CELL<n>
User Manual 1178.5689.02 ─ 12 72

GUI Reference
2.3.10.2 Cell Reselection Settings
Access: "Config" hotkey > "Network" > "Cell Reselection" section.

The parameters in this section define cell reselection information to be transmitted in
the system information blocks SIB1 and SIB3. For detailed information, refer to 3GPP
TS 36.304 and 3GPP TS 36.331.
How to configure network for cell reselection is described in Chapter 2.2.14, "Cell
Reselection Setup", on page 31.
Figure 2-42: Settings for cell reselection
S IntraSearch................................................................................................................ 73
S NonIntraSearch..........................................................................................................73
Q qualmin......................................................................................................................73
Q Rxlevmin....................................................................................................................73
Q Hyst........................................................................................................................... 74
T Reselection................................................................................................................ 74
S IntraSearch
Sets the threshold SIntraSearch for intra-frequency measurements.
The threshold is configured in dB. System information block 3 contains the configured
value divided by 2.
Remote command:
CONFigure:NIOT:SIGN:CELL:RESelection:SEARch:INTRasearch
S NonIntraSearch
Sets the threshold SnonIntraSearch for inter-frequency measurements.
The threshold is configured in dB. System information block 3 contains the configured
value divided by 2.
Remote command:
CONFigure:NIOT:SIGN:CELL:RESelection:SEARch:NINTrasearch
Q qualmin
Sets minimum required quality level in the target cell.
Remote command:
CONFigure:NIOT:SIGN:CELL:RESelection:QUALity
Q Rxlevmin
Sets minimum required received RSRP level in the target cell in dBm (Qrxlevmin).
User Manual 1178.5689.02 ─ 12 73

GUI Reference
The level is configured in dBm. System information block 1 contains the configured
value divided by 2.
Remote command:
Q Hyst
Sets the hysteresis for the cell reselection algorithm.
Remote command:
T Reselection
Sets the time hysteresis for the cell reselection algorithm.
Remote command:
CONFigure:NIOT:SIGN:CELL:RESelection:TIME
2.3.10.3 Identity
Access: "Config" hotkey > "Network" > "Identity" section.

This section configures identities of the simulated radio network. The values are trans-
ferred to the UE under test via broadcast.
Figure 2-43: Network identity settings
MCC.............................................................................................................................. 74
MNC.............................................................................................................................. 74
TAC............................................................................................................................... 74
E-UTRAN Cell Identifier................................................................................................ 75
MCC
Specifies the three-digit mobile country code (MCC).
Remote command:
CONFigure:NIOT:SIGN:CELL:MCC
MNC
Specifies the mobile network code (MNC). A two or three-digit MNC can be set.
Remote command:
CONFigure:NIOT:SIGN:CELL:MNC
CONFigure:NIOT:SIGN:CELL:MNC:DIGits
TAC
Specifies the tracking area code (TAC).
User Manual 1178.5689.02 ─ 12 74

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:CELL:TAC
E-UTRAN Cell Identifier

Specifies the E-UTRAN cell identifier, unique within a PLMN. It is sent to the UE via
broadcast and can be set independent of the physical cell ID (see "Physical Cell ID"
on page 62).
Remote command:
CONFigure:NIOT:SIGN:CELL:CID:EUTRan
2.3.10.4 Security
Access: "Config" hotkey > "Network" > "Security" section.

The "Security Settings" configure parameters for the authentication procedure and for
integrity protection.
Figure 2-44: Security settings
Authentication............................................................................................................... 75
Security......................................................................................................................... 75
Integrity Algorithm......................................................................................................... 75
Secret Key.....................................................................................................................76
Milenage........................................................................................................................76
OPc............................................................................................................................... 76
Authentication
Enables or disables authentication, to be performed during the attach procedure.
Authentication requires a test USIM. An appropriate 3GPP USIM can be obtained from
Rohde & Schwarz (R&S CMW-Z06, stock no. 1209.2010.02).
Remote command:
CONFigure:NIOT:SIGN:CELL:SECurity:AUTHenticat
Security
Enables or disables security. With enabled security, the UE uses integrity protection for
signaling. This setting is only relevant if authentication is enabled.
Remote command:
CONFigure:NIOT:SIGN:CELL:SECurity:SECurity
Integrity Algorithm
Selects an algorithm for integrity protection.
User Manual 1178.5689.02 ─ 12 75

GUI Reference
NULL means that integrity protection is disabled. Use this setting for UEs which do not
support any integrity algorithm.
Remote command:
CONFigure:NIOT:SIGN:CELL:SECurity:IALGorithm
Secret Key
The secret key K is used for the authentication procedure (including a possible integrity
check). The value is entered as 32-digit hexadecimal number.
The integrity check fails unless the secret key is equal to the value stored on the test
USIM of the UE. The test USIM R&S CMW-Z06 is compatible with the default setting of
this parameter.
Remote command:
CONFigure:NIOT:SIGN:CELL:SECurity:SKEY
Milenage
Enable this parameter to use a USIM with MILENAGE algorithm set.
Remote command:
CONFigure:NIOT:SIGN:CELL:SECurity:MILenage
OPc
The key OPc is used for authentication and integrity check procedures with the MILE-
NAGE algorithm set (parameter "Milenage" enabled). The value is entered as 32-digit
hexadecimal number.
Remote command:
CONFigure:NIOT:SIGN:CELL:SECurity:OPC
2.3.10.5 UE Identity
Access: "Config" hotkey > "Network" > "UE Identity" section.

The "UE Identity" settings configure the default IMSI.
Figure 2-45: UE identity settings
Default IMSI
International mobile subscriber identity (IMSI)
14 to 16 digits are allowed.
Remote command:
CONFigure:NIOT:SIGN:CELL:UEIDentity:IMSI
2.3.10.6 Timers
Access: "Config" hotkey > "Network" > "Timers" section.

The parameters in this section configure timers.
User Manual 1178.5689.02 ─ 12 76

GUI Reference
Figure 2-46: Timer settings
Out of Sync................................................................................................................... 77
T3324............................................................................................................................ 77
T3412............................................................................................................................ 77
T3412 Extended............................................................................................................77
Out of Sync
The "Out of Sync" timer specifies the time after which the instrument, having waited for
a signal from the connected UE, releases the connection. The timer is started when an
uplink grant message is sent to the UE.
Remote command:
CONFigure:NIOT:SIGN:CELL:TOUT:OOSYnc
T3324
Timer "T3324" defines how long the UE stays in idle mode after a transition from RRC
connected to RRC idle. When the timer expires, the UE enters the power-saving mode
(PSM).
The T3324 value is only signaled to the UE if the UE requests PSM and PSM is
allowed, see "PSM Allowed" on page 98.
If the checkbox is off, the value requested by the UE is returned. If the checkbox is on,
the configured value is returned.
Remote command:
CONFigure:NIOT:SIGN:CELL:TOUT:T3324
T3412
Timer "T3412" controls the initiation of a periodic tracking area update by the UE.
If the timer is disabled, no periodic tracking area update is required.
Remote command:
CONFigure:NIOT:SIGN:CELL:TOUT:T3412
T3412 Extended
The extended T3412 setting allows much longer timeout values than the T3412 setting.
If the UE supports extended values for T3412, it uses this setting instead of the T3412
setting.
Configure the timer in seconds. The setting is displayed for information in days, hours,
minutes and seconds.
Remote command:
CONFigure:NIOT:SIGN:CELL:TOUT:TEXT
User Manual 1178.5689.02 ─ 12 77

GUI Reference
2.3.10.7 Time
Access: "Config" hotkey > "Network" > "Time" section.

The "Time" section allows you to send configurable date and time information to the
UE. Thus you can update the date and time displayed by the mobile. In a real network,
this service is typically used to send the current local time to the UE.
Figure 2-47: Time settings
Time Source.................................................................................................................. 78
Date / Time (UTC)......................................................................................................... 78
Daylight Saving Time.................................................................................................... 78
Local Time Zone Offset................................................................................................. 78
Send Time..................................................................................................................... 79
Send Network Name..................................................................................................... 79
Time Source
This parameter selects the date and time source that delivers the coordinated universal
time (UTC) date, the UTC time, the current daylight saving time offset and the time
zone offset.
"CMW Time" Selects the current CMW (Windows) date and time as source.
"Date / Time" Selects the other settings in this section as source.
Remote command:
CONFigure:NIOT:SIGN:CELL:TIME:TTSRc
Date / Time (UTC)

Defines the UTC date and time to be used if "Time Source" is set to "Date / Time".
Remote command:
CONFigure:NIOT:SIGN:CELL:TIME:TDATe
CONFigure:NIOT:SIGN:CELL:TIME:TTME
Daylight Saving Time

Specifies a daylight saving time (DST) offset to be used if "Time Source" is set to
"Date / Time".
You can disable DST or enable it with an offset of +1 hour or +2 hours.
Remote command:
CONFigure:NIOT:SIGN:CELL:TIME:DSTime
Local Time Zone Offset

Defines the time zone offset to be used if "Time Source" is set to "Date / Time".
User Manual 1178.5689.02 ─ 12 78

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:CELL:TIME:LTZoffset
Send Time
Press "Now" to send the date and time information to the UE. This action is only possi-
ble if an RRC connection has been established.
"at Attach" selects whether the date and time information is sent to the UE during the
attach procedure or not.
Remote command:
CONFigure:NIOT:SIGN:CELL:TIME:SNOW
CONFigure:NIOT:SIGN:CELL:TIME:SATTach
Send Network Name

Enable, to signal the full and short network name within date and time information.
Remote command:
CONFigure:NIOT:SIGN:CELL:TIME:SNName
2.3.10.8 Synchronization
Access: "Config" hotkey > "Network" > "Synchronization" section.

The parameters in this section configure the synchronization to other signaling applica-
tions.
Figure 2-48: Synchronization settings
Synchronization Zone
Select the same synchronization zone in all signaling applications that you want to syn-
chronize. "None" means that the application is not synchronized to other signaling
applications.
Synchronizing signaling applications means synchronizing the used system time. This
feature is useful, for example, for evaluation of message logs, because the time
stamps in the logs are synchronized.
Synchronizing two NB-IoT signaling applications means also synchronizing the used
system frame numbers.
Remote command:
CONFigure:NIOT:SIGN:CELL:SYNC:ZONE
Synchronization Offset
Configures the timing offset at cell start, relative to the time zone.
Without offset, the cell signal starts with system frame number 0 and a system time
according to the time zone. With an offset, the cell starts with system frame number 0
plus the offset and a system time according to the time zone plus the offset.
User Manual 1178.5689.02 ─ 12 79

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:CELL:SYNC:OFFSet
2.3.11 Connection Configuration
This section defines parameters for the connection, for example the resource configu-
ration to be allocated to the UE.
For parameter descriptions, refer to the subsections.
● Miscellaneous Connection Settings, Part 1.............................................................80
● UL RMC Connection Settings................................................................................. 84
● DL RMC Connection Settings................................................................................. 85
● User-Defined Scheduling Settings.......................................................................... 86
● HARQ Settings........................................................................................................87
● Non-Anchor Configuration - Rel.13......................................................................... 88
● Non-Anchor Configuration - Rel.14 Paging.............................................................90
● Non-Anchor Configuration - Rel.14 RACH..............................................................95
● NPDCCH Settings...................................................................................................96
● Miscellaneous Connection Settings, Part 2.............................................................97
● Connected DRX Settings........................................................................................ 99
● eDRX (Idle Mode) Settings................................................................................... 101
● Scheduling Request Settings................................................................................101
● Timers Settings..................................................................................................... 103
2.3.11.1 Miscellaneous Connection Settings, Part 1
Access: "Config" hotkey > "Connection" > top of the "Connection" section.
This section describes the following "Connection" settings.
Figure 2-49: Connection configuration settings
User Manual 1178.5689.02 ─ 12 80

GUI Reference
Connection Type........................................................................................................... 81
Testmode.......................................................................................................................81
└ Use "Activate Testmode" Message................................................................. 81
└ IP Version........................................................................................................81
Data Application............................................................................................................ 82
└ C-IoT Optimization.......................................................................................... 82
└ IP Version........................................................................................................82
Destination Server.........................................................................................................82
Keep RRC Connection..................................................................................................82
Release Cause..............................................................................................................83
Release Assistance Indication...................................................................................... 83
Data Inactivity Timer......................................................................................................83
Scheduling Type............................................................................................................83
Connection Type
Configures the connection type to be applied at the R&S CMW.
"Testmode" The test mode uses only layer 1 and 2 of the protocol stack. Layer 3
is not used. This mode is suitable for any signaling tests not involving
the data application unit (DAU).
For the attach, the signaling application uses control plane C-IoT EPS
optimization, as defined in 3GPP TS 36.508.
"Data Applica- The data application mode supports also layer 3, required for IP-
tion" based services. Select this mode for data application measurements
with the DAU.
This value requires an installed DAU.
Remote command:
CONFigure:NIOT:SIGN:CONNection:CTYPe
Testmode
This node configures settings for the test mode.
Use "Activate Testmode" Message ← Testmode

When enabled, an "ACTIVATE TEST MODE" message is sent to the UE in "Test-
mode". No loop mode is requested. Test modes are specified in 3GPP TS 36.509 and
36.508.
Remote command:
CONFigure:NIOT:SIGN:CONNection:TMODe
IP Version ← Testmode
Specifies which IP versions are allowed in test mode.
"IPv4 only" Only IPv4 allowed. IPv6 is not used, even if requested by the UE.
This value is recommended.
"IPv4/IPv6" Both IPv4 and IPv6 are allowed. The IP versions are used as reques-
ted by the UE.
Remote command:
CONFigure:NIOT:SIGN:CONNection:TMODe:IPVersion
User Manual 1178.5689.02 ─ 12 81

GUI Reference
Data Application
This node configures settings for the data application mode.
C-IoT Optimization ← Data Application

Selects the C-IoT optimization type to be used for the attach: user plane (UP-mode) or
control plane (CP-mode) C-IoT EPS optimization.
The C-IoT optimization types are defined in 3GPP TS 36.508.
Remote command:
CONFigure:NIOT:SIGN:CONNection:DAPPlication:CIOT
IP Version ← Data Application

Specifies which IP versions are allowed in data application mode.
"IPv4/IPv6" Both IPv4 and IPv6 are allowed. The IP versions are used as reques-
ted by the UE.
"Non-IP" Non-IP data delivery (NIDD) is used.
Remote command:
CONFigure:NIOT:SIGN:CONNection:DAPPlication:IPVersion
Destination Server
Specifies the destination server IP address (IPv4) and destination UDP port for non-IP
data delivery.
Remote command:
CONFigure:NIOT:SIGN:CONNection:DSERver:IPVFaddress
CONFigure:NIOT:SIGN:CONNection:DSERver:PORT
Keep RRC Connection

Selects whether the RRC connection is kept or released after attach.
"Enabled" The RRC connection established during attach is kept when the
attach procedure is completed.
For a subsequent connection setup, the already established RRC
connection is used. So the connection setup is faster. After a discon-
nect, the RRC connection is still kept.
"Disabled" ● For "Connection Type" = "Testmode", the RRC connection estab-
lished during attach is released immediately when the attach pro-
cedure is completed.
● For "Connection Type" = "Data Application", there is an additional
setting "Inactivity Timer". The RRC connection established during
attach is released when the attach procedure is completed and
there has been no activity on the connection (no traffic) for the
configured time.
Remote command:
CONFigure:NIOT:SIGN:CONNection:RRC:KEEP
CONFigure:NIOT:SIGN:CONNection:RRC:TIMer
User Manual 1178.5689.02 ─ 12 82

GUI Reference
Release Cause
Selects the behavior for the state transitions of an RRC connection.
See also "Connection control hotkeys" on page 44.
"other" The hotkey "Connect" establishes RRC connection with the UE. The
connection state changes to RRC_CONNECTED.
You can release the existing RRC connection using the hotkey "Dis-
connect". The state changes from connection established
(RRC_CONNECTED) to idle (RRC_IDLE).
"rrc-Suspend" You can suspend the existing RRC connection using the hotkey "Sus-
pend". The state changes from connection established (RRC_CON-
NECTED) to idle (RRC_IDLE).
Prerequisites: C-IoT Optimization must be set to "U-Plane" and Keep
RRC Connection must be set to "Disabled".
The hotkey "Resume" restores the previous connections and the
state changes again to RRC_CONNECTED.
Remote command:
CONFigure:NIOT:SIGN:CONNection:RRC:RELCause
Release Assistance Indication

Enables release assistance indication. With this R14 feature, the network triggers RRC
release upon no UL or DL activity.
Remote command:
CONFigure:NIOT:SIGN:CONNection:RAI:ENABle
Data Inactivity Timer

Enables/disables and sets data inactivity timer. When there is no traffic for the config-
ured time, both the UE and the eNodeB release the connection.
Remote command:
CONFigure:NIOT:SIGN:CONNection:DIT:ENABle
CONFigure:NIOT:SIGN:CONNection:DIT:TIMer
Scheduling Type
Selects the channel type to be scheduled for the UE.
"UL RMC" The instrument allocates a 3GPP-compliant reference measurement
channel for UL tests (3GPP TS 36.521, chapter 6).
For configuration, see Chapter 2.3.11.2, "UL RMC Connection Set-
tings", on page 84.
"DL RMC" The instrument allocates a 3GPP-compliant reference measurement
channel for DL tests (3GPP TS 36.521, chapter 7 and 8).
For configuration, see Chapter 2.3.11.3, "DL RMC Connection Set-
tings", on page 85.
"User defined" User-defined scheduling, with configurable DL/UL pattern.
For configuration, see Chapter 2.3.11.4, "User-Defined Scheduling
Settings", on page 86.
Remote command:
CONFigure:NIOT:SIGN:CONNection:STYPe
User Manual 1178.5689.02 ─ 12 83

GUI Reference
2.3.11.2 UL RMC Connection Settings
Access: "Config" hotkey > "Connection" > "UL RMC Scheduling" section.
The parameters in this section configure a 3GPP-conform UL RMC. The settings apply
if "Scheduling Type" on page 83 = "UL RMC".
The settings are used for NPUSCH format 1. The settings for NPUSCH format 2 are
fixed.
There are dependencies between the settings. Configure the settings from the top to
the bottom.
For valid parameter combinations, see Chapter 2.2.8, "Scheduling Type UL RMC",
on page 23.
Figure 2-50: UL RMC connection settings
Subcarriers, Start Subcarrier.........................................................................................84

MCS Index.................................................................................................................... 84
Resource Units..............................................................................................................84
Repetitions.................................................................................................................... 84
Subcarriers, Start Subcarrier

Number of scheduled subcarriers and offset of the first scheduled subcarrier from the
edge of the transmission bandwidth.
Remote command:
CONFigure:NIOT:SIGN:CONNection:RMC:UL
MCS Index
MCS index value. It determines the modulation scheme and the transport block size,
which are displayed for information.
Remote command:
CONFigure:NIOT:SIGN:CONNection:RMC:UL:MCSindex?
Resource Units
Number of resource units.
Remote command:
Repetitions
Selects the number of NPUSCH repetitions.
Remote command:
User Manual 1178.5689.02 ─ 12 84

GUI Reference
2.3.11.3 DL RMC Connection Settings
Access: "Config" hotkey > "Connection" > "DL RMC Scheduling" section.
The parameters in this section configure a 3GPP-conform DL RMC. The settings apply
if "Scheduling Type" on page 83 = "DL RMC".
There are dependencies between the settings. Configure the settings from the top to
the bottom.
For valid parameter combinations, see Chapter 2.2.9, "Scheduling Type DL RMC",
on page 24.
Figure 2-51: DL RMC connection settings

MCS Index.................................................................................................................... 85
Subframes.....................................................................................................................85
Repetitions.................................................................................................................... 85

Remote command:
CONFigure:NIOT:SIGN:CONNection:RMC:DL
MCS Index
Remote command:
CONFigure:NIOT:SIGN:CONNection:RMC:DL:MCSindex?
Subframes
Number of subframes.
Remote command:
Repetitions
Selects the number of NPDSCH repetitions.
Remote command:
User Manual 1178.5689.02 ─ 12 85

GUI Reference
2.3.11.4 User-Defined Scheduling Settings
Access: "Config" hotkey > "Connection" > "User-Defined Scheduling" section.

The parameters in this section apply if "Scheduling Type" on page 83 = "User defined".
The UL settings are used for NPUSCH format 1. The settings for NPUSCH format 2
are fixed.
There are dependencies between the settings. Configure the UL or DL settings from
the top left to the bottom.
For valid parameter combinations, see Chapter 2.2.10, "User-Defined Scheduling",
on page 24.
Figure 2-52: Settings for user-defined scheduling
Pattern...........................................................................................................................86
MCS Index.................................................................................................................... 87
Resource Units, Subframes.......................................................................................... 87
Repetitions.................................................................................................................... 87
Pattern
The signaling application sends a UL grant or a DL grant to the UE at each possible
search space occasion.
The pattern defines the sequence of the grants.
"Alternating Alternating DL grants and UL grants are sent. The provided data rate
DL/UL" is 3.2 kbps on DL and 150 kbps on UL. See also "Maximal possible
throughput" on page 27.
This scheduling can be used for end-to-end data connections.
"Continuous Only UL grants are sent. The provided data rate is 158.5 kbps.
UL" This scheduling can be used for multi-evaluation measurements.
This scheduling cannot be used for end-to-end data connections.
"Continuous Only DL grants are sent. The provided data rate is 79.5 kbps using
DL" the maximum number of subframes 10.
This scheduling can be used for BLER tests.
User Manual 1178.5689.02 ─ 12 86

GUI Reference
"Continuous Only DL grants are sent. The provided maximum data rate is 95 kbps
DL 95 kbps" with the number of subframes set to 10.
This scheduling can be used for BLER tests.
"No schedul- No UL or DL grants are sent. The other settings in this section are
ing" ignored.
This scheduling can be used to check whether the UE transmits with-
out permission.
Remote command:
CONFigure:NIOT:SIGN:CONNection:UDEFined:UDPattern

Remote command:
CONFigure:NIOT:SIGN:CONNection:UDEFined:UL[:SET<setNr>]
CONFigure:NIOT:SIGN:CONNection:UDEFined:DL[:SET<setNr>]
MCS Index
Remote command:
CONFigure:NIOT:SIGN:CONNection:UDEFined:UL:MCSindex?
CONFigure:NIOT:SIGN:CONNection:UDEFined:DL:MCSindex?
Resource Units, Subframes

Number of resource units for the UL and number of subframes for the DL.
The settings must match the UE release capability, see "Transport block size (TBS) "
on page 25.
Remote command:
Repetitions
Selects the number of repetitions of each transmission.
Remote command:
2.3.11.5 HARQ Settings
Access: "Config" hotkey > "Connection" > "HARQ" section.

The following parameters configure the HARQ procedure for downlink and uplink trans-
missions.
User Manual 1178.5689.02 ─ 12 87

GUI Reference
Figure 2-53: Settings for HARQ procedure
HARQ............................................................................................................................88
No. of HARQ Processes............................................................................................... 88
Max. No. of Transmissions............................................................................................88
HARQ
Enables or disables hybrid automatic repeat request (HARQ).
Remote command:
CONFigure:NIOT:SIGN:CONNection:HARQen
No. of HARQ Processes

Specifies the number of HARQ processes.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NUMHqpc
Max. No. of Transmissions

Specifies the maximum number of transmissions, including initial transmissions and
retransmissions.
Remote command:
CONFigure:NIOT:SIGN:CONNection:MAXNumtr
2.3.11.6 Non-Anchor Configuration - Rel.13
Access: "Config" hotkey > "Connection" > "Non-Anchor Configuration" > "Non-Anchor -
Rel.13"section.
In Rel.13, the RRC connection procedure can contain an additional carrier for user
data transmission in UL and DL, the non-anchor carrier. Synchronization, broadcast
information and paging are only received on the anchor carrier in Rel.13.
The non-anchor carrier is supported only in standalone operation mode.
User Manual 1178.5689.02 ─ 12 88

GUI Reference
Figure 2-54: Non-anchor configuration for Rel.13
Enable Non-Anchor Rel. 13.......................................................................................... 89

DL/ UL Frequency......................................................................................................... 89
Downlink Bitmap........................................................................................................... 89
Downlink Gap................................................................................................................89
Gap Threshold.............................................................................................................. 90
Gap Periodicity..............................................................................................................90
Gap Duration Coefficient...............................................................................................90
NRS Power Offset.........................................................................................................90
Enable Non-Anchor Rel. 13

Enables non-anchor carrier for the transmission of user data.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:ENABle
DL/ UL Frequency
Specifies the frequencies for non-anchor carriers. The non-anchor channels in Rel.13
carry only user data (NPDSCH/ NPUSCH).
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:CHANnel:DL
CONFigure:NIOT:SIGN:CONNection:NAC:CHANnel:UL
Downlink Bitmap
A bitmap can be provided indicating the allowed DL subframes for downlink data trans-
mission.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:DBMap
CONFigure:NIOT:SIGN:CONNection:NAC:EXBitmap
Downlink Gap
A transmission gap is specified to postpone the NPSDCH transmission. For NPDSCH
carrying the BCCH, there are no gaps in the transmission. See 3GPP TS 36.211, sec-
tion 10.2.3.4 Mapping to resource elements.
If active, you can choose between the DL gap for anchor or explicit non-anchor config-
uration.
● "No Gap": Transmission gap not active
User Manual 1178.5689.02 ─ 12 89

GUI Reference
● "Anchor Gap" (IE DL-GapConfig-NB): The downlink gap configuration for

NPDCCH and NPDSCH. Downlink gaps apply to all NPDCCH/NPDSCH transmis-
sions except for BCCH.
● "Explicit Gap" (dl-GapNonAnchor): Downlink transmission gap configuration for
the anchor/ non-anchor carrier.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:DGAP
Gap Threshold
Specifies the maximum number of NPDCCH repetitions (dl-GapThreshold) configured
for non-anchor data carrier before the DL transmission gap is applied.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:GAPTh
Gap Periodicity
Periodicity (dl-GapPeriodicity) of a DL transmission gap in number of subframes.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:GAPPeriod
Gap Duration Coefficient

Coefficient (dl-GapDurationCoeff) to calculate the gap duration of a DL transmission:
Duration in No. of subframes = (dl-GapDurationCoeff) x
(dl-GapPeriodicity)
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:GAPDc
NRS Power Offset

Specifies the power of a non-anchor carrier relative to the level of narrowband refer-
ence signal (NRS).
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:NRSPo
2.3.11.7 Non-Anchor Configuration - Rel.14 Paging
Access: "Config" hotkey > "Connection" > "Non-Anchor Configuration" > "Non-Anchor -
Rel.14 Paging"section.
This section configures the non-anchor carriers for paging (in addition to the Rel.13
non-anchor carrier for the transmission of user data). Multiple non-anchor carriers for
paging (and random access) are supported from Rel.14.
The non-anchor carrier is supported only in standalone operation mode. Up to two non-
anchor carriers can be configured for paging.
User Manual 1178.5689.02 ─ 12 90

GUI Reference
Figure 2-55: Non-anchor configuration for paging in Rel.14
Enable Non-Anchor - Rel.14 Paging............................................................................. 91

Paging Weight Anchor...................................................................................................91
Enable Non-Anchor Carrier...........................................................................................92
DL Channel................................................................................................................... 92
DL Channel Offset.........................................................................................................92
Downlink Bitmap........................................................................................................... 92
Downlink Gap................................................................................................................92
Gap Threshold.............................................................................................................. 93
Gap Periodicity..............................................................................................................93
Gap Duration Coefficient...............................................................................................93
NRS Power Offset.........................................................................................................93
Enable PCCH Configuration......................................................................................... 93
Num. Repetition Paging................................................................................................ 94
Paging Weight...............................................................................................................94
Enable WUS Configuration........................................................................................... 94
Max Duration Factor......................................................................................................94
Enable Non-Anchor - Rel.14 Paging

Enables the paging via non-anchor carriers.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:ENABle
Paging Weight Anchor

Sets and enables the weight of the anchor carrier for uneven paging load distribution
across the carriers. If the value of w0 is applied, the anchor carrier is not used for pag-
ing.
User Manual 1178.5689.02 ─ 12 91

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:PWANchor
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:PWANchor:ENABle
Enable Non-Anchor Carrier

Enables/disables paging for the corresponding non-anchor carrier. Up to two non-
anchor carriers are supported.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:ENABle
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:ENABle
DL Channel
Specifies the DL channel number or frequency for non-anchor paging carriers.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:
CHANnel:DL
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:
CHANnel:DL
DL Channel Offset
Sets the DL channel offset of the NB-IoT channel number to EARFCN as defined in
3GPP TS 36.101, section 5.7.3F Carrier frequency and EARFCN for category NB1 and
NB2.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:OFFSet:
DL
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:OFFSet:
DL
Downlink Bitmap
A bitmap can be provided indicating the allowed DL subframes for downlink paging via
non-anchor carriers.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DBMap
EXBitmap
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DBMap
EXBitmap
Downlink Gap
A transmission gap is specified to postpone the paging transmission via non-anchor
carriers.
If active, you can choose between the DL gap for anchor or explicit non-anchor config-
uration.
● "No Gap": Transmission gap not active
User Manual 1178.5689.02 ─ 12 92

GUI Reference
● "Anchor Gap" (IE DL-GapConfig-NB): The downlink gap configuration for

NPDCCH and NPDSCH. Downlink gaps apply to all NPDCCH/NPDSCH transmis-
sions except for BCCH.
● "Explicit Gap" (dl-GapNonAnchor): Downlink transmission gap configuration for
the anchor/ non-anchor carrier.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DGAP
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DGAP
Gap Threshold
for non-anchor paging carrier before the DL transmission gap is applied.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPTh
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPTh
Gap Periodicity
Periodicity (dl-GapPeriodicity) of a DL transmission gap for paging via non-anchor car-
riers in number of subframes.
Remote command:
GAPPeriod
GAPPeriod
Gap Duration Coefficient

Coefficient (dl-GapDurationCoeff) to calculate the gap duration of a DL paging trans-
mission via non.anchor carriers:
(dl-GapPeriodicity)
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPDc
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPDc
NRS Power Offset

Specifies the power of a non-anchor paging carrier relative to the level of narrowband
reference signal (NRS).
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:NRSPo
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:NRSPo
Enable PCCH Configuration

Enables the paging via the corresponding non-anchor carrier. The related settings are
signaled via IE SystemInformationBlockType22-NB in field PCCH-Config-NB-r14.
User Manual 1178.5689.02 ─ 12 93

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:
ENABle
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:
ENABle
Num. Repetition Paging

Enables/disables and sets the maximum number of repetitions for paging transmis-
sions over the corresponding non-anchor carrier.
Configuration allows you also to set spare bits 1 to 4.
Remote command:
NREP
NREP
Paging Weight
Sets and enables the relative weight of the corresponding non-anchor paging carrier
for uneven paging load distribution across the carriers.
Remote command:
PWEight
PWEight
PWEight:ENABle
PWEight:ENABle
Enable WUS Configuration

Enables the wake-up signal (WUS) for non-anchor paging carriers.
See also Chapter 2.3.9.5, "Wake Up Signal Configuration", on page 67.
Remote command:
WUSConf:ENABle
WUSConf:ENABle
Max Duration Factor

Sets the maximal duration of WUS for non-anchor paging carriers expressed in factor
of subframes 1/x.
Remote command:
DURFactor:MAX
DURFactor:MAX
User Manual 1178.5689.02 ─ 12 94

GUI Reference
2.3.11.8 Non-Anchor Configuration - Rel.14 RACH
Access: "Config" hotkey > "Connection" > "Non-Anchor Configuration" > "Non-Anchor
Rel.14 RACH" section.
This section configures the non-anchor carriers for random access procedure (in addi-
tion to the Rel.13 non-anchor carrier for the transmission of user data). Multiple non-
anchor carriers for random access (and paging) are supported from Rel.14.
The non-anchor carrier is supported only in standalone operation mode. Up to two non-
anchor carriers can be configured for random access.
Figure 2-56: Non-anchor configuration for RACH in Rel.14
Enable Non-Anchor Rel. 14 RACH............................................................................... 95

NPRACH Probability Anchor.........................................................................................95
Enable Non-Anchor Carrier...........................................................................................95
UL Channel................................................................................................................... 96
UL Channel Offset.........................................................................................................96
Enable Non-Anchor Rel. 14 RACH

Enables the random access (RA) procedure via non-anchor carriers.
The related settings are signaled via IE SystemInformationBlockType22-NB.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:ENABle
NPRACH Probability Anchor

Enables and sets the selection probability for the anchor carrier NPRACH resource.
Value zero means, that the anchor carrier is not used for random access. All non-
anchor carriers NPRACH resources have equal probability between them.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:NPRach:PROB:ANCHor:
ENABle
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:NPRach:PROB:ANCHor
Enable Non-Anchor Carrier

Enables the random access via the corresponding non-anchor carrier. Up to two non-
anchor carriers are supported.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:ENABle
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:ENABle
User Manual 1178.5689.02 ─ 12 95

GUI Reference
UL Channel
Specifies the UL channel number or frequency for non-anchor RA carrier.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:CHANnel:
UL
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:CHANnel:
UL
UL Channel Offset
Sets the UL channel offset of the NB-IoT channel number to EARFCN as defined in
3GPP TS 36.101, section 5.7.3F Carrier frequency and EARFCN for category NB1 and
NB2.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:OFFSet:UL
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:OFFSet:UL
2.3.11.9 NPDCCH Settings
Access: "Config" hotkey > "Connection" > "NPDCCH" section.

The following parameters configure narrowband physical downlink control channel
(NPDCCH) as defined in 3GPP TS 36.213.
For overview of physical DL channels description, refer to Chapter 2.2.6, "Physical DL
Channels and Signals", on page 20.
Figure 2-57: NPDCCH settings
Max. No. Repetitions Rmax < UE Specific Search Space............................................ 96

No. Repetitions..............................................................................................................97
Start SF......................................................................................................................... 97
Offset.............................................................................................................................97
Max. No. Repetitions Rmax < Common Search Space - Paging..................................97
Max. No. Repetitions Rmax < UE Specific Search Space

Specifies the maximum number of repetitions Rmax for NPDCCH transmissions speci-
fied for the UE.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NPDCch:MXNRep
User Manual 1178.5689.02 ─ 12 96

GUI Reference
No. Repetitions
Specifies the number of repetitions R for actual NPDCCH transmissions related to
Rmax. The absolute number of NPDCCH repetitions in a subframe is also displayed.
The transmission is repeated over consecutive NB-IoT downlink subframes.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NPDCch:NREP
CONFigure:NIOT:SIGN:CONNection:NPDCch:NRRepr?
Start SF
Specifies NPDCCH starting position as a subframe. Start SF results in the displayed
periodicity of NPDCCH transmissions.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NPDCch:STSF
CONFigure:NIOT:SIGN:CONNection:NPDCch:PERiod?
Offset
Shifts the start SF related to Rmax value. Absolute value in subframes is displayed for
information.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NPDCch:OFFSt
CONFigure:NIOT:SIGN:CONNection:NPDCch:SFOFfst?
Max. No. Repetitions Rmax < Common Search Space - Paging

Specifies the maximum number of repetitions Rmax for NPDCCH transmissions with
paging used in the cell.
Remote command:
CONFigure:NIOT:SIGN:CONNection:NPDCch:CSS:MAXNrep
2.3.11.10 Miscellaneous Connection Settings, Part 2
Access: "Config" hotkey > "Connection" > the highest level of the "Connection" section,
lower part.
This section describes the following "Connection" settings.
Figure 2-58: Connection configuration settings
User Manual 1178.5689.02 ─ 12 97

GUI Reference
Default Paging Cycle.....................................................................................................98

PCCH-Config nB........................................................................................................... 98
RRC Allow Paging After SI Transmission..................................................................... 98
BCCH Mod. Period Coeff.............................................................................................. 98
PSM Allowed.................................................................................................................98
Interference Randomization.......................................................................................... 99
Connected DRX............................................................................................................ 99
eDRX (Idle Mode)......................................................................................................... 99
Enable Paging Collision Report.................................................................................... 99
Scheduling Request...................................................................................................... 99
UE Capabilities Request............................................................................................... 99
Timers........................................................................................................................... 99
Default Paging Cycle

Selects the cell-specific default paging cycle (128, 256, 512 or 1024 radio frames). The
value is signaled to the UE as "defaultPagingCycle" and used by the UE as input for
the calculation of paging radio frame and subframe positions.
The R&S CMW considers the setting when sending paging messages.
Remote command:
CONFigure:NIOT:SIGN:CONNection:DPCYcle
PCCH-Config nB
Configures the field "nB" in the "PCCH-Config-NB" in system information block 2.
The value is used by the UE as input for the calculation of paging radio frame and pag-
ing occasion according to 3GPP TS 36.304, chapter 7.
Remote command:
CONFigure:NIOT:SIGN:CONNection:PCNB
RRC Allow Paging After SI Transmission

Enables/ disables paging after the transmission of system information (SI) message.
If enabled, this parameter is especially useful to avoid paging collisions with SIB mes-
sages. The support by the UE is required.
Remote command:
CONFigure:NIOT:SIGN:CONNection:RRCPasitrans
BCCH Mod. Period Coeff.

Configures the field "modificationPeriodCoeff" in the "BCCH-Config-NB" in system
information block 2.
Remote command:
CONFigure:NIOT:SIGN:CONNection:BMPC
PSM Allowed
Specifies whether a UE request for power-saving mode (PSM) is accepted or rejected.
See also 3GPP TS 24.301, section 5.3.11 "Power saving mode".
If you enable the checkbox, a PSM request is answered with timer T3324, see "T3324"
on page 77.
User Manual 1178.5689.02 ─ 12 98

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:CONNection:PSMallowed
Interference Randomization
Enables the interference randomization to improve the diversity of scrambling
sequence in Rel.14.
Remote command:
CONFigure:NIOT:SIGN:CONNection:INTRandom
Connected DRX
Refer to Chapter 2.3.11.11, "Connected DRX Settings", on page 99.
eDRX (Idle Mode)

Refer to Chapter 2.3.11.12, "eDRX (Idle Mode) Settings", on page 101
Enable Paging Collision Report

Enables or disables the report of MAC scheduling collisions in event messages. If
enabled, the reports are visible in the main view > "Event Log".
Remote command:
CONFigure:NIOT:SIGN:CONNection:EPCReport
Scheduling Request
Refer to Chapter 2.3.11.13, "Scheduling Request Settings", on page 101.
UE Capabilities Request
Selects, whether the R&S CMW performs the UE capabilities inquiry repeatedly or
once only.
Remote command:
CONFigure:NIOT:SIGN:CONNection:UECRequest
Timers
Refer to Chapter 2.3.11.14, "Timers Settings", on page 103.
2.3.11.11 Connected DRX Settings
Access: "Config" hotkey > "Connection" > Connected DRX section.

The section configures settings for discontinuous reception (DRX) of the UE during an
established connection. If DRX is enabled, the UE monitors the NPDCCH discontinu-
ously and thus reduces battery consumption. The related signaling parameters are
configurable and specified in 3GPP TS 36.321, chapter 5.7.
DRX cycles have a fixed length and start with a fixed "On" time during which the UE
receiver is active. After the "On" time, there is an opportunity for DRX.
Active MAC padding and uplink RB allocation cause NPDCCH traffic and prevent DRX.
The following settings are available.
User Manual 1178.5689.02 ─ 12 99

GUI Reference
Figure 2-59: Connected DRX settings
The unit "PDCCH Subframes" used in this context refers to subframes with NPDCCH.
Connected DRX.......................................................................................................... 100
On Duration Timer.......................................................................................................100
Inactivity Timer............................................................................................................ 100
Retransmission Timer................................................................................................. 100
DRX Cycle...................................................................................................................100
Start Offset.................................................................................................................. 101
UL Retransmission Timer............................................................................................101
Connected DRX
Enables or disables DRX in connected status.
Remote command:
CONFigure:NIOT:SIGN:CONNection:CDRX:ENABle
On Duration Timer
The UE "on" time at the beginning of each DRX cycle ("onDurationTimer").
Remote command:
CONFigure:NIOT:SIGN:CONNection:CDRX:ODTimer
Inactivity Timer
No. of NPDCCH subframes after the subframe in which the DL or UL HARQ RTT timer
expires ("drx-InactivityTimer").
Remote command:
CONFigure:NIOT:SIGN:CONNection:CDRX:ITIMer
Retransmission Timer
"On" time if the UE expects a DL retransmission ("drx-RetransmissionTimer"). If the
timer expires, the UE stops all DL HARQ processes. The timer expires early when the
retransmission is received.
Remote command:
CONFigure:NIOT:SIGN:CONNection:CDRX:RTIMer
DRX Cycle
Duration of one DRX cycle.
Remote command:
CONFigure:NIOT:SIGN:CONNection:CDRX:DCYCle
User Manual 1178.5689.02 ─ 12 100

GUI Reference
Start Offset
Offset shifting a DRX cycle (drxStartOffset).
Remote command:
CONFigure:NIOT:SIGN:CONNection:CDRX:SOFFset
UL Retransmission Timer
Maximum number of subframes until a grant for UL retransmission is received. If the
timer (drx-ULRetransmissionTimer) expires, the UE stops all UL HARQ processes.
Remote command:
CONFigure:NIOT:SIGN:CONNection:CDRX:ULRetrtimer
2.3.11.12 eDRX (Idle Mode) Settings
Access: "Config" hotkey > "Connection" > eDRX (Idle Mode) section.
This section configures extended discontinuous reception (eDRX) in idle mode used
for power saving.
Enabled
Enables or disables eDRX.
If enabled, the UE is informed about the eDRX cycle length and the paging time win-
dow size. Each eDRX cycle includes one paging time window during which the UE
monitors the NPDCCH for paging messages. The remaining time of the cycle, the UE
does not monitor the NPDCCH.
Remote command:
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:ENABle
Paging Time Window

Duration of one paging time window in idle mode, in subframes.
Remote command:
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:PTWindow
Cycle Length
Duration of one extended DRX cycle in idle mode, in radio frames.
Remote command:
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:CLENgth
2.3.11.13 Scheduling Request Settings
Access: "Config" hotkey > "Connection" > Scheduling Request section.

This section configures Rel. 15 scheduling request (SR) related parameters and
resources.
User Manual 1178.5689.02 ─ 12 101

GUI Reference
Prerequisites: Connection Type = "Data Application".
Figure 2-60: Scheduling request configuration
No Response to SR
If enabled, the R&S CMW does not allocate resource for SR and sends no UL DCI
response.
Remote command:
CONFigure:NIOT:SIGN:CONNection:SREQuest:NRESponse
With HARQ-ACK / Without HARQ-ACK

Enables or disables scheduling requests with or without HARQ-ack for NB-IoT trans-
mission.
Consider also UE capabilities (see "SR with HARQ-ACK / SR without HARQ-ACK"
on page 41).
Remote command:
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WITH
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT
Carrier Index
Sets the nprach-CarrierIndex: 0 for anchor carrier, 1 non-anchor carrier one, 2 for non-
anchor carrier two
1 and 2 are only configurable if non-anchor Rel.14 RACH carriers are enabled. Refer
to Chapter 2.3.11.8, "Non-Anchor Configuration - Rel.14 RACH", on page 95.
Remote command:
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:
CINDex
Resource Index
Selects the index of the NPRACH resource in the NPRACH-ParametersList.
The number of NPRACH resources equals to the number of configured CE levels.
Thus, index 2 (respectively 3) is only configurable if CE level 1 (respectively CE levels
1 and 2) is enabled. Refer to Chapter 2.3.9.4, "Coverage Enhancement Configuration",
on page 66.
The first entry in the list has index ‘1’, the second entry has index ‘2’, the third entry has
index ‘3’.
Currently, only NPRACH-ParametersList-Fmt0Fmt1 is supported.
User Manual 1178.5689.02 ─ 12 102

GUI Reference
Remote command:
RINDex
Subcarrier Index
Sets the NPRACH resource format and the index of the subcarrier in NPRACH-Param-
etersList.
Remote command:
SCINdex:FMT
SCINdex:FMT:VALue
P0 SR
Sets the p0-SR-r15 to specify target power for SR without HARQ-ACK. (See 3GPP TS
36.213, section 16.2.1.2.1.)
Remote command:
PSR
Alpha
Sets the fractional power control parameter alpha-r15 for SR without HARQ-ACK. See
TS 36.213, section 16.2.1.2.1.
Remote command:
ALPHa
2.3.11.14 Timers Settings
Access: "Config" hotkey > "Connection" > Timers section.

This section configures general timers and counters for connection reestablishment.
T310, N310, N311

Sets the number of out-of-sync ( N310) and in-sync (N311) indications and T310 timer
related to RRC connection reestablishment procedures.
N310 is the number of consecutive out-of-sync indications signaled from lower layers.
If reached, it triggers T310 timer.
N311 is the number of consecutive in-sync indications signaled from lower layers. If
reached, it stops T310 timer.
If T310 timer expires, the connection is released (the UE enters RRC_IDLE).
User Manual 1178.5689.02 ─ 12 103

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:CONNection:TIMer:NTELeven
CONFigure:NIOT:SIGN:CONNection:TIMer:NTTen
CONFigure:NIOT:SIGN:CONNection:TIMer:TTTen
2.3.12 UE Measurement Report Settings
Access: "Config" hotkey > "UE Measurement Report".

The section configures the UE measurement report. The report is shown in the main
signaling view, see Chapter 2.3.1.5, "UE Measurement Report", on page 42.
Figure 2-61: UE measurement report settings
Report
Enables or disables the UE measurement report.
Remote command:
CONFigure:NIOT:SIGN:UEReport:ENABle
2.3.13 Messaging (SMS) Parameters
Access: "Config" hotkey > "Messaging (SMS)" section.

The node configures parameters of the short message service (SMS). Sending a short
message to the UE is triggered via hotkey, see "Connection control hotkeys"
on page 44.
Figure 2-62: SMS parameters
2.3.13.1 Outgoing SMS
Access: "Config" hotkey > "Messaging (SMS)" node > "Outgoing" section.
The node configures outgoing mobile-terminating short messages.
User Manual 1178.5689.02 ─ 12 104

GUI Reference
Figure 2-63: Outgoing SMS parameters
Large SMS Handling................................................................................................... 105

Outgoing Message Handling.......................................................................................106
Outgoing SMS.............................................................................................................106
Outgoing SMS binary.................................................................................................. 106
Protocol Identifier........................................................................................................ 106
Data Coding / Character Set....................................................................................... 106
User Data Header....................................................................................................... 106
Coding Group..............................................................................................................107
Message Class............................................................................................................107
Originator SMSC Address...........................................................................................107
Originating Address.....................................................................................................107
Service Center Time Stamp........................................................................................ 107
From File..................................................................................................................... 108
└ Select File..................................................................................................... 108
└ Message Encoding, Message Text, Message Length...................................108
Last Message Sent..................................................................................................... 108
Large SMS Handling

Selects the handling of messages exceeding 160 characters.
"Truncate" The SMS is truncated to 160 characters, the rest is discarded.
"Multiple SMS" Up to five concatenated messages are sent, consisting in sum of up
to 800 characters.
User Manual 1178.5689.02 ─ 12 105

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:LHANdling
Outgoing Message Handling

Selects whether the message text is defined via the GUI or read from a file.
"Use Internal" Use the message text configured via the GUI (Outgoing SMS or Out-
going SMS binary).
"From File" Read the text from the file selected via "From File" on page 108.
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:MESHandling
Outgoing SMS
Defines the message contents for outgoing 7-bit ASCII messages. Up to 800 charac-
ters are allowed.
This text is used for "Outgoing Message Handling" = "Use Internal" plus "Data Coding /
Character Set" = "7bit".
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:INTernal
Outgoing SMS binary

Defines the message contents for outgoing 8-bit binary messages. The contents are
entered as hexadecimal numbers. Up to 1400 digits are allowed.
This text is used for "Outgoing Message Handling" = "Use Internal" plus "Data Coding /
Character Set" = "8bit".
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:BINary
Protocol Identifier
Specifies the TP protocol identifier (TP-PID) value to be sent. The meaning of the val-
ues is defined in 3GPP TS 23.040 chapter 9.2.3.9.
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:PIDentifier
Data Coding / Character Set

Selects between the 7-bit ASCII message ("Outgoing SMS" on page 106) and the 8-bit
binary message ("Outgoing SMS binary" on page 106).
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:DCODing
User Data Header

To add a header to the TP user data field, enable the checkbox and configure the
header via the hex value. The structure of the user data header is defined in 3GPP TS
23.040, chapter 9.2.3.24.
The hex value configures the following parts of the header:
● Information element identifier (IEI, one octet)
Currently supported values: #H05, #H70 to #H7F
User Manual 1178.5689.02 ─ 12 106

GUI Reference
● Length of information element (IEIDL, one octet)

● Information element data (IED, 0 to n octets)
The signaling application sets the TP-UDHI automatically, according to the checkbox.
With enabled checkbox, it sends the hex value to the UE and uses the correct number
of fill bits in the header. It evaluates the IEIa and applies the correct message concate-
nation and header repetition.
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:UDHeader
Coding Group
Selects the coding group to be indicated to the message recipient in the TP-Data-Cod-
ing-Scheme field. See also 3GPP TS 23.038.
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:CGRoup
Message Class
Selects the message class to be indicated to the message recipient in the TP-Data-
Coding-Scheme field. See also 3GPP TS 23.038.
"None" means that no message class is sent.
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:MCLass
Originator SMSC Address

Short message service center address, to be sent to the recipient.
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:OSADdress
Originating Address
Address of the originator of the SMS, to be sent to the recipient.
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:OADDress
Service Center Time Stamp
Service center time stamp, to be sent to the recipient.

You can configure the time stamp in two ways:
● Select the time source "CMW Time".
The time stamp is set according to the current date and time of the operation sys-
tem.
● Select the time source "Date / Time" and configure the time stamp value via the
parameter "Date / Time".
User Manual 1178.5689.02 ─ 12 107

GUI Reference
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:TSOurce
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:DATE
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:TIME
From File
This node selects a file containing the message to be transmitted.

The file is used for Outgoing Message Handling = "From File".
Select File ← From File

Selects a file from the system drive folder @USERDATA\sms\NBIOT\Send or one of its
subfolders. Store your message files there, using the file extension .sms.
The supported encodings are 7-bit ASCII, 8-bit binary and 16-bit Unicode.
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:FILE
Message Encoding, Message Text, Message Length ← From File

Displays information about the message in the selected file.
Remote command:
CONFigure:NIOT:SIGN:SMS:OUTGoing:FILE:INFO?
Last Message Sent

Indicates whether the last outgoing short message transfer was "Successful" or
"Failed".
The displayed value is reset to the default value "---" whenever the cell is switched on
and when a new transfer is initiated. A new session always starts with the default
value.
Remote command:
SENSe:NIOT:SIGN:SMS:OUTGoing:INFO:LMSent?
2.3.13.2 Incoming SMS
Access: "Config" hotkey > "Messaging (SMS)" node > "Incoming" section.
The node displays information about incoming mobile-originating short messages.
User Manual 1178.5689.02 ─ 12 108

GUI Reference
Figure 2-64: Incoming SMS parameters
Select File
Selects a file from the system drive folder @USERDATA\sms\NBIOT\Received.
Incoming messages are stored there with the file extension .sms.
Only messages received in the current session are available. The files are deleted dur-
ing startup.
Remote command:
CONFigure:NIOT:SIGN:SMS:INComing:FILE
CONFigure:NIOT:SIGN:SMS:INComing:FILE:INFO?
Data Coding / Character Set

Indicates whether the last received message is a 7-bit ASCII message, an 8-bit binary
message or a 16-bit Unicode message.
Remote command:
SENSe:NIOT:SIGN:SMS:INComing:INFO:DCODing?
Message Text / Message Length

Show the text and length of the last received SMS message.
Remote command:
SENSe:NIOT:SIGN:SMS:INComing:INFO:MTEXt?
SENSe:NIOT:SIGN:SMS:INComing:INFO:MLENgth?
Clear Message Text

The button resets all parameters related to a received message.
The message information is deleted. The "message read" flag is set to true.
Remote command:
SENSe:NIOT:SIGN:SMS:INFO:LRMessage:RFLag?
CLEan:NIOT:SIGN:SMS:INComing:INFO:MTEXt
2.3.14 Message Monitoring Settings
Messages exchanged between the NB-IoT signaling application and the UE can be
monitored. For this purpose, the messages are sent to an external PC.
User Manual 1178.5689.02 ─ 12 109

GUI Reference
Figure 2-65: Message monitoring settings
Add NB-IoT Signaling to logging

Enables or disables message monitoring for the NB-IoT signaling application.
Remote command:
CONFigure:NIOT:SIGN:MMONitor:ENABle
Logging PC IPv4 Address

Selects the IP address to which the messages are sent for monitoring.
The address pool is configured globally, see "Setup" dialog, section "Logging".
Remote command:
CONFigure:NIOT:SIGN:MMONitor:IPADdress
2.3.15 Shortcut Configuration
Access: "Config" hotkey > "Shortcut Softkey" section.

This section configures the three shortcut softkeys that provide a fast way to switch to
selectable measurements.
See also Chapter 2.3.3, "Using the Shortcut Softkeys", on page 45.
Figure 2-66: Shortcut configuration
Select Menu
Selects a measurement. The corresponding shortcut softkey opens a dialog presenting
this measurement as default target or uses the measurement as fixed target.
Select as fixed Target

Configures and renames the corresponding shortcut softkey.
● Enabled: The softkey directly opens the measurement selected via Select Menu.
● Disabled: The softkey opens a dialog box for selection of the target measurement.
2.3.16 Debug Configuration
Access: "Config" hotkey > "Debug" section.
User Manual 1178.5689.02 ─ 12 110

GUI Reference
The "Debug" node configures the log file generation.
Do not enable the debug mode during regular operation. It impacts the test perfor-
mance, timing, system drive usage, and so on.
Figure 2-67: Debug configuration
The settings are not affected by a reset or preset. They are not stored in save files. A
reboot restores the default settings.
Write Logs Now........................................................................................................... 111
Cell Restart with Logs Reset....................................................................................... 111
Enable Debug Settings................................................................................................ 111
Signaling Unit Shutdown During Signal Off................................................................. 111
Complete Logs.............................................................................................................111
PHY/MAC Log, U-Plane Data Log...............................................................................112
Write Logs Now

Writes the NB-IoT log files to the system drive.
Cell Restart with Logs Reset

Switches the cell signal off and on again with empty logs.
Enable Debug Settings

Enables the configuration of the "Debug Settings".
Signaling Unit Shutdown During Signal Off

The complete log files are written if the signaling unit is shut down. The signaling unit is
shut down if the instrument is shut down or if the CMW software is terminated.
With enabled checkbox, the signaling unit is also shut down if the cell signal is
switched off. So switching off the cell delivers log files.
Complete Logs
With disabled checkbox, only a reduced set of log files is written if the NB-IoT signaling
instance is replaced by another signaling instance due to a resource conflict. This
behavior saves time and system drive space.
With enabled checkbox, a complete set of log files is written if the NB-IoT signaling
instance is replaced by another signaling instance.
User Manual 1178.5689.02 ─ 12 111

Programming
PHY/MAC Log, U-Plane Data Log

These settings configure the level of detail of the log files.
2.4 Programming
The following sections provide programming examples for the NB-IoT signaling appli-
cation.
The examples contain SCPI commands supported by the R&S CMW and the following
symbolic scripting commands:
● // <comment>:
A <comment> ignored by the used programming tool
● WHILE <query> <> <value>:
Waits until the <query> returns a certain <value>, e.g. a specific state is reached.
● WAITKEY <message>:
Displays a dialog box with a <message> and waits until you close the box.
● General Configuration........................................................................................... 112
2.4.1 General Configuration
The NB-IoT signaling application is programmed as follows:

● The application is controlled by SCPI commands with the following syn-
tax: ...:NIOT:SIGN:....
● After a *RST, the DL signal is switched off.
To activate the DL signal, use SOURce:NIOT:SIGN:CELL:STATe ON.
Query the cell state using SOURce:NIOT:SIGN:CELL:STATe:ALL?. The result
ON,ADJ indicates that the DL signal is available.
● To initiate a connection setup, let the UE attach.
For details, see Chapter 2.4.1.20, "Setting Up a Connection", on page 123.
2.4.1.1 Initialization
// *****************************************************************************
// Initial system-reset
// *****************************************************************************
*RST; *OPC?
*CLS; *OPC?
2.4.1.2 Configuring the Signal Paths
// *****************************************************************************
// Query available scenarios. Configure the standard cell scenario.
// *****************************************************************************
CATalog:NIOT:SIGN:SCENario?
User Manual 1178.5689.02 ─ 12 112

Programming
ROUTe:NIOT:SIGN:SCENario:FLEXible:SCELl SUA1,RF1C,RX1,RF1C,TX1
CONFigure:NIOT:SIGN:RFSettings:EATTenuation:OUTPut 2
CONFigure:NIOT:SIGN:RFSettings:EATTenuation:INPut 2
2.4.1.3 Configuring Internal Fading
// *****************************************************************************
// Select a standard cell scenario with internal fading.
// *****************************************************************************
ROUTe:NIOT:SIGN:SCENario:SCFading:INTernal RF2C,RX1,RF2C,TX1,FAD1
// *****************************************************************************
// Configure fading: Enable the fading simulator,
// select a fading profile, start fading automatically,
// set start seed, calculate insertion loss automatically,
// specify max Doppler frequency. Query clipping samples.
// *****************************************************************************
CONFigure:NIOT:SIGN:FADing:FSIMulator:ENABle ON
CONFigure:NIOT:SIGN:FADing:FSIMulator:PROFile EP5Low
CONFigure:NIOT:SIGN:FADing:FSIMulator:RESTart:MODE AUTO
CONFigure:NIOT:SIGN:FADing:FSIMulator:GLOBal:SEED 0
CONFigure:NIOT:SIGN:FADing:FSIMulator:ILOSs:MODE NORMal
CONFigure:NIOT:SIGN:FADing:FSIMulator:DSHift:MODE USER
CONFigure:NIOT:SIGN:FADing:FSIMulator:DSHift 6
SENSe:NIOT:SIGN:FADing:FSIMulator:ILOSs:CSAMples?
// *****************************************************************************
// Configure AWGN insertion for downlink:
// Enable AWGN, no frequency offset, set min noise/system BW ratio,
// set signal to noise ratio and query calculated noise power.
// *****************************************************************************
CONFigure:NIOT:SIGN:FADing:AWGN:ENABle ON
CONFigure:NIOT:SIGN:FADing:AWGN:FOFFset 0
CONFigure:NIOT:SIGN:FADing:AWGN:BWIDth:RATio 1
CONFigure:NIOT:SIGN:FADing:AWGN:SNRatio 1
CONFigure:NIOT:SIGN:FADing:POWer:NOISe?
2.4.1.4 Specifying General Settings
// *****************************************************************************
// Define the time delay to be compensated in output and input paths.
// *****************************************************************************
CONFigure:NIOT:SIGN:RFSettings:EDC:OUTPut 5E-9
CONFigure:NIOT:SIGN:RFSettings:EDC:INPut 5E-9
// *****************************************************************************
// Select manual expected nominal power mode and specify the expected power,
// the user margin and the mixer level offset.
// *****************************************************************************
User Manual 1178.5689.02 ─ 12 113

Programming
CONFigure:NIOT:SIGN:RFSettings:ENPMode MANual
CONFigure:NIOT:SIGN:RFSettings:ENPower -25
CONFigure:NIOT:SIGN:RFSettings:UMARgin 3
CONFigure:NIOT:SIGN:RFSettings:MLOFfset 1
2.4.1.5 Configuring Operating Bands and Channels
// *****************************************************************************
// Specify operating band plus DL channel number and query the
// automatically calculated UL channel number.
// Configure frequency offsets for DL and UL.
// *****************************************************************************
CONFigure:NIOT:SIGN:BAND OB8
CONFigure:NIOT:SIGN:RFSettings:CHANnel:DL 3500 ;UL?
CONFigure:NIOT:SIGN:RFSettings:FOFFset:DL 100
CONFigure:NIOT:SIGN:RFSettings:FOFFset:UL -200
2.4.1.6 Configuring DL Power Levels
// *****************************************************************************
// Define the NRS EPRE level and enable the OFDMA channel noise generator.
// Enable and configure AWGN.
// *****************************************************************************
CONFigure:NIOT:SIGN:DL:NRSepre:LEVel -80
CONFigure:NIOT:SIGN:DL:OCNG ON
CONFigure:NIOT:SIGN:DL:AWGN -100
2.4.1.7 Configuring UL Power Settings
// *****************************************************************************
// Define the uplink nominal power directly (basic UL power configuration).
// Query the resulting parameter values signaled to the UE.
// *****************************************************************************
CONFigure:NIOT:SIGN:UL:NPUSch:ULNPower -30.5
SENSe:NIOT:SIGN:UL:ADPower:ENPPpower?
SENSe:NIOT:SIGN:UL:ADPower:EFNPower1?
// *****************************************************************************
// Alternatively, enable advanced UL power configuration,
// define the parameter values to be signaled to the UE and
// query values calculated from the parameters.
// *****************************************************************************
CONFigure:NIOT:SIGN:UL:ADPower:ENABle ON
CONFigure:NIOT:SIGN:UL:ADPower:NRSPower 10
CONFigure:NIOT:SIGN:UL:ADPower:PIRPower -100
CONFigure:NIOT:SIGN:UL:ADPower:PNNPusch -80
CONFigure:NIOT:SIGN:UL:ADPower:PCALpha DOT7
User Manual 1178.5689.02 ─ 12 114

Programming
SENSe:NIOT:SIGN:UL:ADPower:PATHloss?
SENSe:NIOT:SIGN:UL:ADPower:ENPPpower?
// *****************************************************************************
// Define maximum allowed UE power.
// *****************************************************************************
CONFigure:NIOT:SIGN:UL:PMAX 3
2.4.1.8 Configuring Physical Cell Setup
// *****************************************************************************
// Select FDD, the UL subcarrier spacing and define the physical cell ID.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:DMODe FDD
CONFigure:NIOT:SIGN:CELL:SCSPacing S15K
CONFigure:NIOT:SIGN:CELL:PCID 10
// *****************************************************************************
// Configure the standalone operation mode.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:OPERmode SALM
// *****************************************************************************
// Alternatively, configure the in-band operation mode.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:OPERmode IBOP
CONFigure:NIOT:SIGN:CELL:IBGBand:FLEXdlul:ENABle OFF
CONFigure:NIOT:SIGN:CELL:IBGBand:BANDwidth B100
CONFigure:NIOT:SIGN:CELL:IBGBand:POFFset ZERO
CONFigure:NIOT:SIGN:CELL:IBGBand:CRSize CRS2
CONFigure:NIOT:SIGN:CELL:IBGBand:IPCI SAME
CONFigure:NIOT:SIGN:CELL:IBGBand:IBCPosition 9
CONFigure:NIOT:SIGN:CELL:IBGBand:IBUCposition 4
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:DL?
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:UL?
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:DL?
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:UL?
// *****************************************************************************
// Alternatively, configure the guard-band operation mode.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:OPERmode GBOP
CONFigure:NIOT:SIGN:CELL:IBGBand:GBCPosition LOW
CONFigure:NIOT:SIGN:CELL:IBGBand:GBUCposition ON,606
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:DL?
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:UL?
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:DL?
User Manual 1178.5689.02 ─ 12 115

Programming
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:UL?
// *****************************************************************************
// Configure NPRACH settings.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:NPRach:NOResponse OFF
CONFigure:NIOT:SIGN:CELL:NPRach:PRAMping S6
CONFigure:NIOT:SIGN:CELL:NPRach:PREFormat 1
CONFigure:NIOT:SIGN:CELL:NPRach:MAXTrans T10
// *****************************************************************************
// Configure coverage enhancements for all CE levels: No. of threshold,
// repetitions for preamble and random access, set threshold.
// Query the CE level reported by the DUT.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:CENHt:NTHReshold 1
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:ZERO 4
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:ONE 8
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:TWO 8
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:ZERO R16
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:ONE R16
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:TWO R16
CONFigure:NIOT:SIGN:CELL:CENHt:RSRPthr:ONE -80
CONFigure:NIOT:SIGN:CELL:CENHt:RSRPthr:TWO -80
SENSe:NIOT:SIGN:CELL:CENHt:REPCelev?
// *****************************************************************************
// Configure wake up signal (WUS): enable WUS and associated paging, set max
// duration factor, No. of paging occasions (PO), first PO position,
// No. of relaxed DRX cycles, time offset for DRX and eDRX with short gap.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:WUSignal:ENABle ON
CONFigure:NIOT:SIGN:CELL:WUSignal:PAGing:DISable OFF
CONFigure:NIOT:SIGN:CELL:WUSignal:DURFactor:MAX R16
CONFigure:NIOT:SIGN:CELL:WUSignal:NUMPos ONE
CONFigure:NIOT:SIGN:CELL:WUSignal:FPOPos 1
CONFigure:NIOT:SIGN:CELL:WUSignal:DRXCycles:RELaxed 8
CONFigure:NIOT:SIGN:CELL:WUSignal:DRX:TOFFset 16E-2
CONFigure:NIOT:SIGN:CELL:WUSignal:EDRX:TOFFset:SHORt 16E-2
CONFigure:NIOT:SIGN:CELL:WUSignal:EDRX:TOFFset:LONG OFF
// *****************************************************************************
// Configure early data transmission (EDT): disable CP-EDT, enable UP-EDT,
// enable EDT small TBS subset and EDT small TBS, set TBS value.
// Query the used TBS values.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:CPEDt OFF
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:UPEDt ON
CONFigure:NIOT:SIGN:CELL:EDT:SMALl:ENABle:TBS:SUBSet ON
CONFigure:NIOT:SIGN:CELL:EDT:SMALl:ENABle:TBS ON
User Manual 1178.5689.02 ─ 12 116

Programming
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:TBS:VALue B584
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:TBS:VALue?
2.4.1.9 Configuring Network Settings
// *****************************************************************************
// Specify MCC, 2-digit MNC and tracking area code.
// Configure E-UTRAN cell ID.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:MCC 262
CONFigure:NIOT:SIGN:CELL:MNC:DIGits TWO
CONFigure:NIOT:SIGN:CELL:MNC 30
CONFigure:NIOT:SIGN:CELL:TAC 1384
CONFigure:NIOT:SIGN:CELL:CID:EUTRan #B10000010001000
// *****************************************************************************
// Enable authentication and integrity protection.
// Define integrity algorithm, secret key and OPc. Enable milenage.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:SECurity:AUTHenticat ON
CONFigure:NIOT:SIGN:CELL:SECurity:SECurity ON
CONFigure:NIOT:SIGN:CELL:SECurity:IALGorithm S3G
CONFigure:NIOT:SIGN:CELL:SECurity:SKEY #H000102030405060708090A0B0C0D0E0F
CONFigure:NIOT:SIGN:CELL:SECurity:OPC #H000010B00091006000F00000A0005000
CONFigure:NIOT:SIGN:CELL:SECurity:MILenage ON
// *****************************************************************************
// Configure timers.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:TOUT:OOSYnc 10
CONFigure:NIOT:SIGN:CELL:TOUT:T3324 10
CONFigure:NIOT:SIGN:CELL:TOUT:T3412 180
CONFigure:NIOT:SIGN:CELL:TOUT:TEXT 18600
// *****************************************************************************
// Configure time: Select a time source and configure date, time,
// DST and time zone offset.
// Enable sending of the information during attach.
// Send the information to the UE now. Let signal the full and short network
// name within date and time information.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:TIME:TTSRc DATE
CONFigure:NIOT:SIGN:CELL:TIME:TDATe 24,10,2012
CONFigure:NIOT:SIGN:CELL:TIME:TTME 12,40,30
CONFigure:NIOT:SIGN:CELL:TIME:DSTime P1H
CONFigure:NIOT:SIGN:CELL:TIME:LTZoffset 1
CONFigure:NIOT:SIGN:CELL:TIME:SATTach ON
CONFigure:NIOT:SIGN:CELL:TIME:SNOW
CONFigure:NIOT:SIGN:CELL:TIME:SNName ON
User Manual 1178.5689.02 ─ 12 117

Programming
// *****************************************************************************
// Synchronize the signaling application to zone 1.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:SYNC:ZONE Z1
CONFigure:NIOT:SIGN:CELL:SYNC:OFFSet 0
2.4.1.10 Configuring Neighbor Cells and Reselection
// *****************************************************************************
// Specify 2 neighbor cell entries.
// *****************************************************************************
CONFigure:NIOT:SIGN:NCELl:NIOT:CELL1 ON, OB1, 300, 1, ZERO, ON
CONFigure:NIOT:SIGN:NCELl:NIOT:CELL2 ON, OB2, 900, 2, P1, OFF
// *****************************************************************************
// Specify general reselection parameters for the cell.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:RESelection:SEARch:INTRasearch OFF
CONFigure:NIOT:SIGN:CELL:RESelection:SEARch:NINTrasearch OFF
CONFigure:NIOT:SIGN:CELL:RESelection:QUALity -15,-135,4
CONFigure:NIOT:SIGN:CELL:RESelection:TIME 3
2.4.1.11 Configuring General Connection Settings
// *****************************************************************************
// Select the test mode and configure it. Prepare settings for data
// application mode including IP addressing for non-IP data connections.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:CTYPe TEST
CONFigure:NIOT:SIGN:CONNection:TMODe ON
CONFigure:NIOT:SIGN:CONNection:TMODe:IPVersion IPV4
CONFigure:NIOT:SIGN:CONNection:DAPPlication:CIOT CPL
CONFigure:NIOT:SIGN:CONNection:DAPPlication:IPVersion NIP
CONFigure:NIOT:SIGN:CONNection:DSERver:IPVFaddress '192.168.168.2'
CONFigure:NIOT:SIGN:CONNection:DSERver:PORT 192.168.168.2 4366
// *****************************************************************************
// Configure RRC connection complete release. Configure release assistance
// indication including data inactivity timer. Configure default paging cycle,
// PCCH-Config nB. Allow RRC paging after SI transmission. Set BCCH
// modification period coefficient. Allow PSM. Enable interference
// randomization and paging collision report. Set the UE capabilities reporting.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:RRC:KEEP OFF
CONFigure:NIOT:SIGN:CONNection:RRC:RELCause OTHer
CONFigure:NIOT:SIGN:CONNection:RRC:TIMer 4
CONFigure:NIOT:SIGN:CONNection:RAI:ENABle ON
CONFigure:NIOT:SIGN:CONNection:DIT:ENABle ON
User Manual 1178.5689.02 ─ 12 118

Programming
CONFigure:NIOT:SIGN:CONNection:DIT:TIMer 80
CONFigure:NIOT:SIGN:CONNection:DPCYcle P256
CONFigure:NIOT:SIGN:CONNection:PCNB 2T
CONFigure:NIOT:SIGN:CONNection:RRCPasitrans ON
CONFigure:NIOT:SIGN:CONNection:BMPC 64
CONFigure:NIOT:SIGN:CONNection:PSMallowed ON
CONFigure:NIOT:SIGN:CONNection:INTRandom ON
CONFigure:NIOT:SIGN:CONNection:EPCReport ON
CONFigure:NIOT:SIGN:CONNection:UECRequest ONE
// *****************************************************************************
// Specify the timers N310, N311 and T310
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:TIMer:NTTen T5
CONFigure:NIOT:SIGN:CONNection:TIMer:NTELeven T1
CONFigure:NIOT:SIGN:CONNection:TIMer:TTTen MS40
2.4.1.12 Configuring UL RMCs
// *****************************************************************************
// Select the scheduling type.
// Configure a UL RMC with full subcarrier allocation.
// Query the resulting MCS index and transport block size.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:STYPe ULRMc
CONFigure:NIOT:SIGN:CONNection:RMC:UL SC12, 0, MI5, NRU01, NR1
CONFigure:NIOT:SIGN:CONNection:RMC:UL:MCSindex?
2.4.1.13 Configuring DL RMCs
// *****************************************************************************
// Select the scheduling type.
// Configure a DL RMC with full subcarrier allocation.
// Query the resulting MCS index and transport block size.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:STYPe DLRMc
CONFigure:NIOT:SIGN:CONNection:RMC:DL KEEP, KEEP, MI6, NSF01, NR1
CONFigure:NIOT:SIGN:CONNection:RMC:DL:MCSindex?
2.4.1.14 Configuring User-Defined Channels
// *****************************************************************************
// Select the scheduling type. Select the grant pattern.
// Configure the UL and DL channels.
// Query the resulting MCS indices and transport block sizes.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:STYPe UDEF
CONFigure:NIOT:SIGN:CONNection:UDEFined:UDPattern DLUL
User Manual 1178.5689.02 ─ 12 119

Programming
CONFigure:NIOT:SIGN:CONNection:UDEFined:UL SC12, 0, MI5, NRU01, NR1

CONFigure:NIOT:SIGN:CONNection:UDEFined:DL KEEP, KEEP, MI6, NSF03, NR1
CONFigure:NIOT:SIGN:CONNection:UDEFined:UL:MCSindex?
CONFigure:NIOT:SIGN:CONNection:UDEFined:DL:MCSindex?
2.4.1.15 Configuring HARQ
// *****************************************************************************
// Configure HARQ for the downlink: enable HARQ, allow max. 4 transmissions and
// set the number of HARQ transmissions to 1.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:HARQen ON
CONFigure:NIOT:SIGN:CONNection:MAXNumtr 4
CONFigure:NIOT:SIGN:CONNection:NUMHqpc 1
2.4.1.16 Configuring Non-Anchor Parameters
// *****************************************************************************
// Configure the standalone operation mode required for non-anchor carrier.
// *****************************************************************************
CONFigure:NIOT:SIGN:CELL:OPERmode SALM
// *****************************************************************************
// Enable non-archor configuration for user data. Set DL and UL non-anchor
// channels, explicit non-anchor bitmap. Cofigure explicit non-anchor DL gap:
// set gap threshold, periodicity, duration coefficient. Set NRS power offset.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:NAC:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:CHANnel:DL 320 Ch
CONFigure:NIOT:SIGN:CONNection:NAC:CHANnel:UL 18320 Ch
CONFigure:NIOT:SIGN:CONNection:NAC:DBMap EXB
CONFigure:NIOT:SIGN:CONNection:NAC:EXBitmap B#1100110
CONFigure:NIOT:SIGN:CONNection:NAC:DGAP EXG
CONFigure:NIOT:SIGN:CONNection:NAC:GAPDc 2
CONFigure:NIOT:SIGN:CONNection:NAC:GAPTh N128
CONFigure:NIOT:SIGN:CONNection:NAC:GAPPeriod SF128
CONFigure:NIOT:SIGN:CONNection:NAC:NRSPo N12
// *****************************************************************************
// Enable non-archor configuration for paging. Set and enable the paging
// weight for anchor carrier. Enable paging for both non-anchor carriers,
// set: DL non-anchor channel,channel offset, non-anchor bitmap. Set explicit
// non-anchor DL gap:set gap threshold, periodicity, duration coefficient.
// Set NRS power offset.
//
// Enable paging for both non-anchor carriers. Set No. of paging
// repetitions and paging weight per non-anchor carrier.
//
//Enable wake up signal for both non-anchor carriers, set its duration factor.
User Manual 1178.5689.02 ─ 12 120

Programming
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:PWANchor w2
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:PWANchor:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:CHANnel:DL 302Ch
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:CHANnel:DL 340Ch
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:OFFSet:DL V0
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:OFFSet:DL V0
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DBMap EXB
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DBMap NOB
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:EXBitmap B#1011110
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DGAP EXG
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DGAP EXG
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPTh N64
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPTh N32
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPPeriod SF64
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPPeriod SF128
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPDc 4
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPDc 1
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:NRSPo ZERO
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:NRSPo N4
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:NREP R8
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:NREP R1
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:PWEight W2
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:PWEight:ENABle OFF
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:WUSConf:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:WUSConf:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DURFactor:MAX R32
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DURFactor:MAX R2
// *****************************************************************************
// Enable randomm access via non-anchor carriers. Enable also random access
// via anchor carrier and set its probability
// For random access, use non-anchor carrier one, disable it for carrier two.
// Set UL channel and channel offset for non-anchor carrier one.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:NPRach:PROB:ANCHor:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:NPRach:PROB:ANCHor R6
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:ENABle ON
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:ENABle OFF
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:CHANnel:UL 18360Ch
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:OFFSet:UL VN2
User Manual 1178.5689.02 ─ 12 121

Programming
2.4.1.17 Configuring NPDCCH
// *****************************************************************************
// Configure NPDCCH: Rmax for UE, repetitions, query the number of repetitions.
// Set start SF, query resulting periodicity. Set offset related to Rmax,
// query resulting offset in subframes. Set Rmax for paging in the cell.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:NPDCch:MXNRep 8
CONFigure:NIOT:SIGN:CONNection:NPDCch:NREP RMAX
CONFigure:NIOT:SIGN:CONNection:NPDCch:NRRepr?
CONFigure:NIOT:SIGN:CONNection:NPDCch:STSF 16
CONFigure:NIOT:SIGN:CONNection:NPDCch:PERiod?
CONFigure:NIOT:SIGN:CONNection:NPDCch:OFFSt 0
CONFigure:NIOT:SIGN:CONNection:NPDCch:SFOFfst?
CONFigure:NIOT:SIGN:CONNection:NPDCch:CSS:MAXNrep R8
2.4.1.18 Configuring Discontinuous Reception
// *****************************************************************************
// Enable DRX in connected status. Set on duration timer, insctivity timer,
// retransmission timer, DRX cycle length, DRX start offset,
// UL retransmission timer.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:CDRX:ENABle ON
CONFigure:NIOT:SIGN:CONNection:CDRX:ODTimer PSF8
CONFigure:NIOT:SIGN:CONNection:CDRX:ITIMer PSF4
CONFigure:NIOT:SIGN:CONNection:CDRX:RTIMer PSF4
CONFigure:NIOT:SIGN:CONNection:CDRX:DCYCle SF1024
CONFigure:NIOT:SIGN:CONNection:CDRX:SOFFset 32
CONFigure:NIOT:SIGN:CONNection:CDRX:ULRetrtimer PSF24
// *****************************************************************************
// Enable extended DRX and configure the eDRX settings for the idle mode.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:ENABle ON
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:PTWindow W5K12
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:CLENgth L4K
2.4.1.19 Configuring Scheduling Request
// *****************************************************************************
// Let the eNodeB respond to SR. Enable the SR with and without HARQ-ack.
// Set carrier, subcarrier and resource index, power and alpha.
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:SREQuest:NRESponse ON
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WITH ON
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT OFF
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:CINDex TWO
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:SCINdex:FMT FT2
User Manual 1178.5689.02 ─ 12 122

Programming
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:RINDex TWO
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:SCINdex:FMT:VALue 10
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:PSR -10
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:ALPHa DOT8
2.4.1.20 Setting Up a Connection
// *****************************************************************************
// Connect the UE (switched off). Switch on the DL signal. Query the cell
// state until it equals ON,ADJ (DL signal available at RF connector).
// *****************************************************************************
WAITKEY >Ensure that the UE is connected to the instrument and switched off<
SOURce:NIOT:SIGN:CELL:STATe ON
WHILE SOURce:NIOT:SIGN:CELL:STATe:ALL? <> "ON,ADJ"
// *****************************************************************************
// Proceeding WITHOUT "Keep RRC Connection":
// Switch on the UE and wait until it is attached (state = ATT).
// Initiate an RRC connection and wait until it is established (state = CEST).
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:RRC:KEEP OFF
WAITKEY >Switch on the UE<
WHILE FETCh:NIOT:SIGN:PSWitched:STATe? <> "ATT"
CALL:NIOT:SIGN:PSWitched:ACTion CONNect
WHILE FETCh:NIOT:SIGN:PSWitched:STATe? <> "CEST"
// *****************************************************************************
// Proceeding WITH "Keep RRC Connection":
// Switch on the UE and wait until the connection is established (state = CEST).
// *****************************************************************************
CONFigure:NIOT:SIGN:CONNection:RRC:KEEP ON
WAITKEY >Switch on the UE<
WHILE FETCh:NIOT:SIGN:PSWitched:STATe? <> "CEST"
// *****************************************************************************
// Query the RRC connection state. It must be "CONN".
// *****************************************************************************
SENSe:NIOT:SIGN:RRCState?
2.4.1.21 Querying UE Information
// *****************************************************************************
// Query all UE information results.
// *****************************************************************************
SENSe:NIOT:SIGN:UESinfo:IMEI?
SENSe:NIOT:SIGN:UESinfo:IMSI?
CATalog:NIOT:SIGN:UESinfo:DEFBearer?
User Manual 1178.5689.02 ─ 12 123

Programming
SENSe:NIOT:SIGN:UESinfo:UEADdress:IPV4?
SENSe:NIOT:SIGN:UESinfo:UEADdress:IPV6?
2.4.1.22 Querying UE Capability Reports
// *****************************************************************************
// Query UE capability information received during RRC connection setup.
// *****************************************************************************
SENSe:NIOT:SIGN:UECapability:RRC:MTONe?
SENSe:NIOT:SIGN:UECapability:RRC:MCARrier?
SENSe:NIOT:SIGN:UECapability:RRC:UPLane?
// *****************************************************************************
// Query general UE capability information.
// *****************************************************************************
SENSe:NIOT:SIGN:UECapability:TRANsfer:RELease?
SENSe:NIOT:SIGN:UECapability:TRANsfer:CATegory?
SENSe:NIOT:SIGN:UECapability:TRANsfer:MDRB?
// *****************************************************************************
// Query RF UE capability information.
// *****************************************************************************
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:BANDs?
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:BANDs:ALL?
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:MPMax?
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:POWClass?
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:POWFourteen
// *****************************************************************************
// Query PDCP UE capability information.
// *****************************************************************************
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:MAXSessions?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:PROFiles?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:ROHC?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:ROHC:ALL?
// *****************************************************************************
// Query MAC layer UE capability information.
// *****************************************************************************
SENSe:NIOT:SIGN:UECapability:MAC:EDATa?
SENSe:NIOT:SIGN:UECapability:MAC:DINactmon?
SENSe:NIOT:SIGN:UECapability:MAC:RELassind?
// *****************************************************************************
// Query physical layer UE capability information.
// *****************************************************************************
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MTONe?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MCARrier?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MCRRier:NPRach?
User Manual 1178.5689.02 ─ 12 124

Programming
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:TWOHarq?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:INTRand?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:SR:HARQack:WITH?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:SR:HARQack:WOUT?
// *****************************************************************************
// Query paging UE capability information.
// *****************************************************************************
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:MTICarrier?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:WUS:ENABle?
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:WUS:MINGap:EDRX?
2.4.1.23 Querying UE Measurement Reports
// *****************************************************************************
// Enable UE measurements reporting.
// *****************************************************************************
CONFigure:NIOT:SIGN:UEReport:ENABle ON
// *****************************************************************************
// Query all UE measurement reports.
// *****************************************************************************
SENSe:NIOT:SIGN:UEReport:RSRP?
SENSe:NIOT:SIGN:UEReport:RSRP:RANGe?
SENSe:NIOT:SIGN:UEReport:RSRQ?
SENSe:NIOT:SIGN:UEReport:RSRQ:RANGe?
2.4.1.24 Sending / Receiving a Short Message
// *****************************************************************************
// Configure support of concatenated SMS.
// *****************************************************************************
CONFigure:NIOT:SIGN:SMS:OUTGoing:LHANdling MSMS
// *****************************************************************************
// Configure outgoing messages directly:
// ASCII message text, binary message contents, TP-PID, data coding,
// user data header, coding group, message class,
// SC address, originating address, service center time stamp.
// Send the message and query whether the transmission was successful.
// *****************************************************************************
CONFigure:NIOT:SIGN:SMS:OUTGoing:MESHandling INTernal
CONFigure:NIOT:SIGN:SMS:OUTGoing:INTernal "Testing SMS 012!.#\*%+-/()<>?=;@$,"
CONFigure:NIOT:SIGN:SMS:OUTGoing:BINary #H0125498fa3bc8d348
CONFigure:NIOT:SIGN:SMS:OUTGoing:PIDentifier #H0
CONFigure:NIOT:SIGN:SMS:OUTGoing:DCODing BIT7
CONFigure:NIOT:SIGN:SMS:OUTGoing:UDHeader #H050415820000
CONFigure:NIOT:SIGN:SMS:OUTGoing:CGRoup GDCoding
CONFigure:NIOT:SIGN:SMS:OUTGoing:MCLass CL2
User Manual 1178.5689.02 ─ 12 125

Command Reference
CONFigure:NIOT:SIGN:SMS:OUTGoing:OSADdress '543221'
CONFigure:NIOT:SIGN:SMS:OUTGoing:OADDress '3526735'
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:TSOurce DATE
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:DATE 15,5,2014
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:TIME 14,40,50
CALL:NIOT:SIGN:PSWitched:ACTion SMS; *OPC?
SENSe:NIOT:SIGN:SMS:OUTGoing:INFO:LMSent?
// *****************************************************************************
// Reset parameters related to an already received short message.
// Wait until a message from the UE has been received.
// Query information about the received message: encoding, message content,
// message length, message segments.
// *****************************************************************************
CLEan:NIOT:SIGN:SMS:INComing:INFO:MTEXt
WAITKEY >Send short message from UE<
WHILE SENSe:NIOT:SIGN:SMS:INFO:LRMessage:RFLag? <> "OFF"
SENSe:NIOT:SIGN:SMS:INComing:INFO:DCODing?
SENSe:NIOT:SIGN:INComing:INFO:MTEXt?
SENSe:NIOT:SIGN:SMS:INComing:INFO:MLENgth?
SENSe:NIOT:SIGN:SMS:INComing:INFO:SEGMent?
// *****************************************************************************
// Configure outgoing messages via a file:
// Select message file and query file information.
// *****************************************************************************
CONFigure:NIOT:SIGN:SMS:OUTGoing:MESHandling FILE
CONFigure:NIOT:SIGN:SMS:OUTGoing:FILE "@USERDATA\sms\LTE\Send\myfile.sms"
CONFigure:NIOT:SIGN:SMS:OUTGoing:FILE:INFO?
// *****************************************************************************
// Get information about an old received short message:
// Select a message file and query information about it.
// *****************************************************************************
CONFigure:NIOT:SIGN:SMS:INComing:FILE "@USERDATA\sms\NBIOT\Received\rx_001.sms"
CONFigure:NIOT:SIGN:SMS:INComing:FILE:INFO?
2.5 Command Reference

The following sections provide detailed reference information on the remote con-
trol commands of the NB-IoT signaling application.
● Conventions and General Information.................................................................. 127
● Connection Control and States............................................................................. 133
● Event Log..............................................................................................................135
● UE Info.................................................................................................................. 137
● UE Capabilities......................................................................................................138
● UE Measurement Report...................................................................................... 147
User Manual 1178.5689.02 ─ 12 126

Command Reference
● Routing Settings....................................................................................................149
● Internal Fading...................................................................................................... 160
● Downlink Power Levels......................................................................................... 167
● Uplink Power Control............................................................................................ 168
● Physical Cell Setup............................................................................................... 172
● Network Settings................................................................................................... 185
● Connection Configuration......................................................................................198
● Messaging (SMS)..................................................................................................240
● Message Monitoring Settings................................................................................249
2.5.1 Conventions and General Information
The following sections describe the most important conventions and general informa-
tion concerning the command reference.
2.5.1.1 SIGN
SIGN is used as abbreviation of SIGNaling<instance>. For better readability,

only the abbreviated form (which is also accepted by the instrument) is given in the
command reference.
The <instance> is relevant for instruments supporting several instances of the same
firmware application. It can be omitted if the instrument supports only one instance, or
to address the first instance.
2.5.1.2 Values for Signal Path Selection
Which connectors and modules can be specified in a command, depends on the instal-
led hardware and the active subinstrument or instance .
This chapter lists all values available for path selection. Depending on your configura-
tion, only a subset is relevant for you. Virtual connector names are only relevant for
setting commands. Queries return the physical connector names.
Additional information is available in the base software documentation. It describes typ-
ical instrument configurations with the allowed RF connector - TX/RX module combina-
tions and the mapping of virtual connector names to physical connectors.
Single-CMW setup
Selection values:
● Signaling unit SUA:
SUA1 | SUA2 | SUA3 | SUA4 | SUA5 | SUA6
SUA partition 1, 2, 3, 4, 5, 6
● RX module:
RX1 | RX2 | RX3 | RX4
● TX module:
TX1 | TX2 | TX3 | TX4
● RX connector:
User Manual 1178.5689.02 ─ 12 127

Command Reference
RF1C | RF2C | RF3C | RF4C | RFAC | RFBC

RF 1 COM to RF 4 COM plus virtual connector names
● TX connector:
RF1O | RF3O | RFAO
RF 1 OUT and RF 3 OUT plus virtual connector name
● I/Q output connector:
IQ2O | IQ4O | IQ6O | IQ8O
DIG IQ OUT 2 to 8
● SUA as fader:
FAD1 | FAD2 | FAD3 | FAD4 | FAD5 | FAD6
SUA fader 1 to 6
The SUA fader numbering is reversed. The highest SUA fader uses the lowest
SUA partition.
CMWflexx setup with R&S CMWC and several R&S CMW500

Selection values:
● Signaling unit SUA:
SUA<a>: CMW <a>, SUA partition 
Example SUA21: CMW 2, SUA partition 1
● RX module:
RX11 | RX12 | RX13 | RX14 | RX21 | RX22 | RX23 | RX24
RX<a>: CMW <a>, RX 
Example RX24: CMW 2, RX module 4
● TX module:
TX11 | TX12 | TX13 | TX14 | TX21 | TX22 | TX23 | TX24
TX31 | TX32 | TX33 | TX34 | TX41 | TX42 | TX43 | TX44
TX<a>: CMW <a>, TX 
Example TX13: CMW 1, TX module 3
● RX connector:
R11C | R12C | R13C | R14C | R21C | R22C | R23C | R24C
R<a>C: CMW <a>, connector RF COM
Example R12C: CMW 1, RF 2 COM
● TX connector:
R11O | R13O | R21O | R23O | R31O | R33O | R41O | R43O
R<a>O: CMW <a>, connector RF OUT
Example R21O: CMW 2, RF 1 OUT
User Manual 1178.5689.02 ─ 12 128

Command Reference
● I/Q output connector:

I12O | I14O | I16O | I18O | I22O | I24O | I26O | I28O
I32O | I34O | I36O | I38O | I42O | I44O | I46O | I48O
I<a>O: CMW <a>, connector DIG IQ OUT 
Example I24O: CMW 2, DIG IQ OUT 4 of
● SUA as fader:
FAD<a>: CMW <a>, SUA fader 
The SUA fader numbering is reversed. The highest SUA fader uses the lowest
SUA partition.
For CMW 1, you can alternatively use the single-CMW selection values.
2.5.1.3 Keywords
Selected keywords used in the command description are described in the following.
● Command usage
If the usage is not explicitly stated, the command allows you to set parameters and
query parameters. Otherwise, the command usage is stated as follows:
– "Setting only": The command can only be used to set parameters.
– "Query only": The command can only be used to query parameters.
– "Event": The command initiates an event.
● Parameter usage
The parameter usage is indicated by the keyword preceding the parameters:
– "Parameters" are sent with a setting or query command and are returned as
the result of a query.
– "Setting parameters" are sent with a setting command.
– "Query parameters" are sent with a query command, to refine the query.
– "Return values" are returned as the result of a query.
● Parameter type
The parameter type is indicated by one of the following keywords, at the beginning
of the parameter description:
– "string": characters enclosed in quotation marks (" or ')
– "numeric", "decimal": decimal number
– "integer": integer number
– "float": floating point number
– "hex": hexadecimal number starting with #H
– "binary": binary number starting with #B
– "block": binary block data (number of length digits + length digits giving number
of data bytes + data bytes + EOS)
Enumerated values are explicitly listed, separated by pipes (example: A | B | C).
● Firmware/Software:
User Manual 1178.5689.02 ─ 12 129

Command Reference
Indicates the lowest software version supporting the command. Command

enhancements in later software versions are also indicated.
2.5.1.4 Reliability Indicator
The first value in the output arrays of FETCh...?, READ...? and CALCulate...?
queries indicates the most severe error that has occurred during the measurement.
Example for an output array: 0, 10.22, 10.15, 10.01, 10.29, 100 (reliability = 0, followed
by 5 numeric measurement values).
The reliability indicator has one of the following values:
● 0 ("No Error"):
Measurement values available, no error detected.
● 1 ("Measurement Timeout"):
The measurement has been stopped after the configured measurement timeout.
Measurement results can be available. However, at least a part of the measure-
ment provides only INValid results or has not completed the full statistic count.
● 2 ("Capture Buffer Overflow"):
The measurement configuration results in a capture length that exceeds the availa-
ble memory.
● 3 ("Input Overdriven") / 4 ("Input Underdriven"):
The accuracy of measurement results can be impaired because the input signal
level was too high / too low.
● 6 ("Trigger Timeout"):
The measurement could not be started or continued because no trigger event was
detected.
● 7 ("Acquisition Error"):
The R&S CMW could not properly decode the RF input signal.
● 8 ("Sync Error"):
The R&S CMW could not synchronize to the RF input signal.
● 9 ("Uncal"):
Due to an inappropriate configuration of resolution bandwidth, video bandwidth or
sweep time, the measurement results are not within the specified data sheet limits.
● 15 ("Reference Frequency Error"):
The instrument has been configured to use an external reference signal. But the
reference oscillator could not be phase-locked to the external signal (for example
signal level too low, frequency out of range or reference signal not available at all).
● 16 ("RF Not Available"):
The measurement could not be started because the configured RF input path was
not active.
This problem can occur if a measurement is started in combined signal path mode
and the controlling application has not yet activated the input path.
● 17 ("RF Level Not Settled") / 18 ("RF Frequency Not Settled"):
The measurement could not be started because the R&S CMW was not yet ready
to deliver stable results after a change of the input signal power / the input signal
frequency.
User Manual 1178.5689.02 ─ 12 130

Command Reference
● 19 ("Call Not Established"):

For measurements: The measurement could not be started because no signaling
connection to the DUT was established.
For DAU IMS service: Establishing a voice over IMS call failed.
● 20 ("Call Type Not Usable"):
For measurements: The measurement could not be started because the estab-
lished signaling connection had wrong properties.
For DAU IMS service: The voice over IMS settings could not be applied.
● 21 ("Call Lost"):
For measurements: The measurement was interrupted because the signaling con-
nection to the DUT was lost.
For DAU IMS service: The voice over IMS call was lost.
● 23 ("Missing Option"):
An action cannot be executed due to a missing option.
For GPRF generator: The ARB file cannot be played due to a missing option.
● 24 ("Invalid RF Setting"):
The desired RF TX level or RF RX reference level could not be applied.
● 25 ("Level Overrange"):
The RF TX level is in overrange. The signal quality can be degraded.
● 26 ("Resource Conflict"):
The application could not be started or has been stopped due to a conflicting hard-
ware resource or software option that is allocated by another application.
Stop the application that has allocated the conflicting resources and try again.
● 28 ("Unexpected Parameter Change"):
One or more measurement configuration parameters were changed while the mea-
surement completed. The results were not obtained with these new parameter val-
ues. Repeat the measurement. This situation can only occur in remote single-shot
mode.
● 29 ("Invalid RF Frequency Setting"):
The desired RF TX frequency or RF RX frequency could not be applied.
● 30 ("File Not Found"):
The specified file could not be found.
● 40 ("ARB File CRC Error"):
The cyclic redundancy check of the ARB file failed. The ARB file is corrupt and not
reliable.
● 42 ("ARB Header Tag Invalid"):
The ARB file selected in the GPRF generator contains an invalid header tag.
● 43 ("ARB Segment Overflow"):
The number of segments in the multi-segment ARB file is higher than the allowed
maximum.
● 44 ("ARB File Not Found"):
The selected ARB file could not be found.
● 45 ("ARB Memory Overflow"):
The ARB file length is greater than the available memory.
● 46 ("ARB Sample Rate Out of Range"):
The clock rate of the ARB file is either too high or too low.
User Manual 1178.5689.02 ─ 12 131

Command Reference
● 47 ("ARB Cycles Out of Range"):

The repetition mode equals "Single Shot" and the playback length is too long.
Reduce the playback length or set the repetition mode to "Continuous".
<Length> = (<Cycles> * <Samples> + <Additional Samples>) / <Clock Rate>
● 50 ("Startup Error"):
The data application unit (DAU), a DAU service or a DAU measurement could not
be started. Execute a DAU self-test.
● 51 ("No Reply"):
The DAU has received no response, for example for a ping request.
● 52 ("Connection Error")
A connection setup failed or a connection was lost.
For DAU: The DAU could not establish a connection to internal components.
Restart the instrument.
● 53 ("Configuration Error"):
The current DAU configuration is incomplete or wrong and could not be applied.
Check especially the IP address configuration.
● 54 ("Filesystem Error"):
The system drive of the DAU is full or corrupt. Execute a DAU self-test.
● 60 ("Invalid RF-Connector Setting")
The individual segments of a list mode measurement with R&S CMWS use differ-
ent connector benches. All segments must use the same bench.
Check the "Info" dialog for the relevant segment numbers.
● 70 ("Wrong Standard")
The standard of the measured signal does not match the configured standard.
● 71 ("Wrong Bandwidth")
The bandwidth of the measured signal does not match the configured bandwidth.
● 72 ("Wrong Burst Type")
The burst type of the measured signal does not match the configured burst type.
● 73 ("MIMO Signal Detected")
The measurement expects a SISO signal and detected a MIMO signal. Use a
MIMO receive mode to measure this signal.
● 74 ("More Streams than Antennas")
The measured signal has more streams than expected due to the configured num-
ber of antennas. Increase the configured number of antennas to measure this sig-
nal.
● 75 ("Matrix Inversion Failed")
The inversion of the channel matrix failed for a MIMO measurement. Check that
the antennas are connected correctly to the instrument.
● 76 ("SIG CRC Failed")
The cyclic redundancy check of a SIGNAL field failed.
● 77 ("Parity Check Failed")
The parity check of a SIGNAL field failed.
● 78 ("Bursts Not Identical")
In training mode for composite MIMO measurements, at least some symbols of
sequential bursts need to be identical to be used as training data. Setting a fix
scrambler initialization can solve this problem.
User Manual 1178.5689.02 ─ 12 132

Command Reference
● 79 ("Wrong Modulation")
The modulation type of the measured signal does not match the configured modu-
lation type.
● 93 ("OCXO Oven Temperature Too Low"):
The accuracy of measurement results can be impaired because the oven-control-
led crystal oscillator has a too low temperature. After switching-on the instrument,
the OCXO requires a warm-up phase to reach its operating temperature.
● 101 ("Firmware Error"):
Indicates a firmware or software error. If you encounter this error for the first time,
restart the instrument.
If the error occurs again, consider the following hints:
– Firmware errors can often be repaired by restoring the factory default settings.
– If a software package has not been properly installed, this failure is often indi-
cated in the "Setup" dialog, section "SW/HW-Equipment > Installed Software".
– Check for software updates correcting the error. Updates are provided in the
customer web on GLORIS (registration required): https://gloris.rohde-
schwarz.com.
If you get firmware errors even with the properly installed latest software version,
send a problem report including log files to Rohde & Schwarz.
● 102 ("Unidentified Error"):
Indicates an error not covered by other reliability values. For troubleshooting, follow
the steps described for "101 (firmware error)".
● 103 ("Parameter Error"):
Indicates that the measurement could not be performed due to internal conflicting
parameter settings.
A good approach to localize the conflicting settings is to start with a reset or preset
or even restore the factory default settings. Then reconfigure the measurement
step by step and check when the error occurs for the first time.
If you need assistance to localize the conflicting parameter settings, contact Rohde
& Schwarz (see http://www.service.rohde-schwarz.com).
● 104 ("Not Functional"):
The application could not be started with the configured parameter set.
2.5.2 Connection Control and States
The commands in the following sections control the connection to the UE and retrieve
connection-related information.
SOURce:NIOT:SIGN:CELL:STATe...............................................................................133
SOURce:NIOT:SIGN:CELL:STATe:ALL?...................................................................... 134
SENSe:NIOT:SIGN:RRCState?...................................................................................134
CALL:NIOT:SIGN:PSWitched:ACTion.......................................................................... 135
FETCh:NIOT:SIGN:PSWitched:STATe?........................................................................135
SOURce:NIOT:SIGN:CELL:STATe <MainState>
Turns the generator (the cell) on or off.
User Manual 1178.5689.02 ─ 12 133

Command Reference
Parameters:
<MainState> ON | OFF | 1 | 0
OFF: generator switched off
ON: generator switched on
Example: See Setting Up a Connection
Firmware/Software: V3.7.20
Manual operation: See "Cell" on page 35
SOURce:NIOT:SIGN:CELL:STATe:ALL?
Returns detailed information about the "NB-IoT Signaling" generator state.
Return values:
<MainState> OFF | ON
OFF: generator switched off
ON: generator switched on
<SyncState> PENDing | ADJusted
PENDing: generator turned on (off) but signal not yet (still) avail-
able
ADJusted: physical output signal corresponds to main genera-
tor state
Usage: Query only
Manual operation: See "ON | OFF (key) / NB-IoT Signaling (softkey)" on page 44
SENSe:NIOT:SIGN:RRCState?
Queries whether an RRC connection is established (connected) or not (idle).
Return values:
<State> IDLE | CONNected
Usage: Query only
Manual operation: See "RRC State" on page 35
User Manual 1178.5689.02 ─ 12 134

Command Reference
CALL:NIOT:SIGN:PSWitched:ACTion <PSAction>
Controls the PS state.
Setting parameters:
<PSAction> CONNect | DISConnect | SMS | DETach | HANDover |
RESume | SUSPend
CONNect: Set up an RRC connection.
DISConnect: Release the RRC connection.
SMS: Send an SMS
DETach: Detach the UE
RESume: Resume the suspended RRC connection
SUSPend: Suspend the established RRC connection
Usage: Event
Firmware/Software: V3.7.30, V3.7.60: added SMS
V3.8.20: added RESume, SUSPend
Manual operation: See "Connection control hotkeys" on page 44
Queries the PS state, see also Chapter 2.2.4, "Connection States", on page 16.
Return values:
<PS State> OFF | ON | ATTached | CESTablished | DISConnect |
CONNecting | SIGNaling | SMESsage | RMESsage
OFF: signal off
ON: signal on
ATTached: UE attached
CESTablished: Connection established
DISConnect: Disconnect in progress
CONNecting: Connection setup in progress
SIGNaling: Signaling in progress
SMESsage: Sending message
RMESsage: Receiving message
*RST: OFF
Usage: Query only
Firmware/Software: V3.7.20, V3.7.60: added SMESsage, RMESsage
Manual operation: See "Packet Switched" on page 35
2.5.3 Event Log
The following commands retrieve event log entries and clear the log.
User Manual 1178.5689.02 ─ 12 135

Command Reference
SENSe:NIOT:SIGN:ELOG:LAST?............................................................................... 136
SENSe:NIOT:SIGN:ELOG:ALL?..................................................................................136
CLEan:NIOT:SIGN:ELOG...........................................................................................136
SENSe:NIOT:SIGN:ELOG:LAST?
Queries the latest entry of the event log.
Return values:
<Timestamp> string
Timestamp of the entry as string
<Category> INFO | WARNing | ERRor | CONTinue
Category of the entry, as indicated in the main view by an icon
<Event> string
Text string describing the event, e.g. "RRC Connection
Established"
Usage: Query only
Manual operation: See "Event log entries" on page 35
SENSe:NIOT:SIGN:ELOG:ALL?
Queries all entries of the event log.
For each entry, three parameters are returned, from oldest to latest entry: {<Time-
stamp>, <Category>, <Event>}entry 1, {<Timestamp>, <Category>, <Event>}entry 2, ...
Return values:
<Timestamp> string
Timestamp of the entry as string
<Category> INFO | WARNing | ERRor | CONTinue
Category of the entry, as indicated in the main view by an icon
<Event> string
Text string describing the event, e.g. "RRC Connection
Established"
Usage: Query only
CLEan:NIOT:SIGN:ELOG
Clears the event log.
Usage: Event
User Manual 1178.5689.02 ─ 12 136

Command Reference
2.5.4 UE Info
The following queries retrieve information about the connected mobile as shown in the
"UE Info" area of the main view.
SENSe:NIOT:SIGN:UESinfo:IMEI?..............................................................................137
SENSe:NIOT:SIGN:UESinfo:IMSI?..............................................................................137
CATalog:NIOT:SIGN:UESinfo:DEFBearer?................................................................... 137
SENSe:NIOT:SIGN:UESinfo:UEADdress:IPV<version>?............................................... 138
SENSe:NIOT:SIGN:UESinfo:IMEI?
Queries the IMEI of the UE.
Return values:
<IMEI> string
IMEI as string with up to 18 digits
Example: See Querying UE Information
Usage: Query only
Manual operation: See "IMEI" on page 36
SENSe:NIOT:SIGN:UESinfo:IMSI?
Queries the IMSI of the UE.
Return values:
<IMSI> string
IMSI as string with up to 16 digits
Usage: Query only
Manual operation: See "IMSI" on page 36
CATalog:NIOT:SIGN:UESinfo:DEFBearer?
Queries the IDs of all established default bearers.
Return values:
<ID> string
Comma-separated list of strings, one string per ID
User Manual 1178.5689.02 ─ 12 137

Command Reference

Usage: Query only
Manual operation: See "Default Bearer" on page 36
SENSe:NIOT:SIGN:UESinfo:UEADdress:IPV<version>?
Returns the IPv4 addresses (<version> = 4) or the IPv6 prefixes (<version> = 6)
assigned to the UE by the R&S CMW.
Suffix: .
<version> 4, 6
Return values:
<IPAddresses> string
Comma-separated list of IP address/prefix strings
Usage: Query only
Manual operation: See "Default Bearer" on page 36
2.5.5 UE Capabilities
The commands in this section retrieve UE capability information as shown in the "UE
Capabilities" area of the main view.
SENSe:NIOT:SIGN:UECapability:MAC:EDATa?............................................................139
SENSe:NIOT:SIGN:UECapability:MAC:DINactmon?..................................................... 139
SENSe:NIOT:SIGN:UECapability:MAC:RELassind?...................................................... 139
SENSe:NIOT:SIGN:UECapability:RRC:MTONe?...........................................................140
SENSe:NIOT:SIGN:UECapability:RRC:MCARrier?........................................................140
SENSe:NIOT:SIGN:UECapability:RRC:UPLane?.......................................................... 140
SENSe:NIOT:SIGN:UECapability:TRANsfer:CATegory?.................................................140
SENSe:NIOT:SIGN:UECapability:TRANsfer:MDRB?..................................................... 141
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:MTICarrier?................................... 141
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:WUS:ENABle?............................... 141
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:WUS:MINGap:EDRX?.................... 141
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:MAXSessions?.................................142
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:PROFiles?.......................................142
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:ROHC?........................................... 142
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:ROHC:ALL?.................................... 143
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:INTRand?................................... 143
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MCARrier?..................................143
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MCRRier:NPRach?......................144
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MTONe?.....................................144
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:SR:HARQack:WITH.....................144
User Manual 1178.5689.02 ─ 12 138

Command Reference
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:SR:HARQack:WOUT................... 145
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:TWOHarq?................................. 145
SENSe:NIOT:SIGN:UECapability:TRANsfer:RELease?................................................. 145
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:BANDs?...............................................145
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:BANDs:ALL?........................................ 146
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:MPMax?.............................................. 146
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:POWClass?..........................................147
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:POWFourteen...................................... 147
SENSe:NIOT:SIGN:UECapability:MAC:EDATa?
Indicates whether the UE supports early data transmission in user plane (UP) C-IoT
EPS optimized mode.
Return values:
<Data> NO | YES
Example: See Querying UE Capability Reports
Usage: Query only
Manual operation: See "earlyData-UP" on page 40
SENSe:NIOT:SIGN:UECapability:MAC:DINactmon?
Indicates whether the UE supports data inactivity monitoring.
Return values:
<DINActMon> NO | YES
Usage: Query only
Manual operation: See "Data Inactivity Monitoring" on page 40
SENSe:NIOT:SIGN:UECapability:MAC:RELassind?
Indicates whether the UE supports release assistance indication.
Return values:
<RELAssIndi> NO | YES
Usage: Query only
Manual operation: See "Release Assistance Indication" on page 40
User Manual 1178.5689.02 ─ 12 139

Command Reference
SENSe:NIOT:SIGN:UECapability:RRC:MTONe?
Returns whether the UE supports NPUSCH multi-tone transmissions, as indicated by
the UE in an RRC connection request.
Return values:
<MultiTone> NO | YES
Usage: Query only
Manual operation: See "Multi-Tone" on page 37
SENSe:NIOT:SIGN:UECapability:RRC:MCARrier?
Returns whether the UE supports multi-carrier operation, as indicated by the UE in an
RRC connection request.
Return values:
<MultiCarrier> NO | YES
Usage: Query only
Manual operation: See "Multi-Carrier" on page 37
SENSe:NIOT:SIGN:UECapability:RRC:UPLane?
Returns whether the UE supports user plane C-IoT EPS optimization, as indicated by
the UE in an RRC connection setup complete message.
Return values:
<UserPlaneCOpt> NO | YES
Usage: Query only
Manual operation: See "User Plane C-IoT Optimization" on page 38
SENSe:NIOT:SIGN:UECapability:TRANsfer:CATegory?
Returns the reported UE category.
Return values:
<UECategory> NB1 | NB2
User Manual 1178.5689.02 ─ 12 140

Command Reference
Usage: Query only

Firmware/Software: V3.7.20, V3.7.40: added NB2
Manual operation: See "UE Category" on page 38
SENSe:NIOT:SIGN:UECapability:TRANsfer:MDRB?
Returns whether the UE supports multiple data radio bearers.
Return values:
<MultipleDRB> NO | YES
Usage: Query only
Manual operation: See "Multiple DRB" on page 38
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:MTICarrier?
Indicates whether the UE supports paging on non-anchor carriers, as specified in
3GPP TS 36.331 and 36.304.
Return values:
<MultiCrPaging> NO | YES
Usage: Query only
Manual operation: See "Multi-Carrier Paging" on page 42
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:WUS:ENABle?
Returns whether the UE supports wake up signal.
Return values:
<Enable> OFF | ON
Usage: Query only
Manual operation: See "Wake Up Signal" on page 42
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:WUS:MINGap:EDRX?
Indicates the minimum gap the UE supports between WUS and associated paging
occasion (PO) for eDRX as specified by 3GPP in TS 36.213 and TS 36.304.
User Manual 1178.5689.02 ─ 12 141

Command Reference
Return values:
<WUSMGeDRX> decimal
Range: 40 ms, 240 ms, 1000 ms, 2000 ms
Default unit: ms
Usage: Query only
Manual operation: See "WUS Min Gap eDRX" on page 42
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:MAXSessions?
Returns the maximum number of header compression context sessions supported by
the UE.
Return values:
<MaxCSessions> CS2 | CS4 | CS8 | CS12
2, 4, 8, 12 parallel sessions
Usage: Query only
Manual operation: See "Max Num ROHC Context Sessions" on page 40
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:PROFiles?
Returns which ROHC profiles the UE supports.
The information is returned per ROHC profile. The values have the same order as the
profile names returned by the command SENSe:NIOT:SIGN:UECapability:
TRANsfer:PDCP:ROHC?.
Return values:
<Enable> NO | YES
Comma-separated list of values, one value per profile
Usage: Query only
Manual operation: See "Supported ROHC Profiles" on page 39
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:ROHC?
Returns a list of ROHC profile names, as reference for the command SENSe:NIOT:
SIGN:UECapability:TRANsfer:PDCP:PROFiles?.
User Manual 1178.5689.02 ─ 12 142

Command Reference
Return values:
<Profiles> string
Comma-separated list of strings, one string per profile
Usage: Query only
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:ROHC:ALL?
Returns a list of ROHC profile support information.
For each profile, a pair of values is returned:
{<Profiles>, <Enable>}1, {<Profiles>, <Enable>}2, ...
Return values:
<Profiles> string
Name of the profile, as string, for example "Profile0x0002"
<Enable> NO | YES
Support of the profile
Usage: Query only
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:INTRand?
Indicates whether the UE supports interference randomization in connected mode as
specified in 3GPP TS 36.211.
Return values:
<InterfeRandom> NO | YES
Usage: Query only
Manual operation: See "Interference Randomization" on page 41
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MCARrier?
Returns whether the UE supports multi-carrier operation, as indicated by the UE in the
information element "UE-Capability-NB".
Return values:
<MultiCarrier> NO | YES
User Manual 1178.5689.02 ─ 12 143

Command Reference

Usage: Query only
Manual operation: See "Multi-Carrier" on page 41
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MCRRier:NPRach?
Indicates whether the UE supports NPRACH on non-anchor carrier, as specified in
3GPP TS 36.321 and 36.331.
Return values:
<MCARnprach> NO | YES
Usage: Query only
Manual operation: See "Multi-Carrier NPRACH" on page 41
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MTONe?
Returns whether the UE supports NPUSCH multi-tone transmissions, as indicated by
the UE in the information element "UE-Capability-NB".
Return values:
<MultiTone> NO | YES
Usage: Query only
Manual operation: See "Multi-Tone" on page 41
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:SR:HARQack:WITH
<value>
Indicates whether the UE supports scheduling request with HARQ-ACK.
Parameters:
<SRwithHARQack> NO | YES
Manual operation: See "SR with HARQ-ACK / SR without HARQ-ACK" on page 41
User Manual 1178.5689.02 ─ 12 144

Command Reference
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:SR:HARQack:WOUT
<value>
Indicates whether the UE supports scheduling request without HARQ-ACK.
Parameters:
<SRnoHARQack> NO | YES
Manual operation: See "SR with HARQ-ACK / SR without HARQ-ACK" on page 41
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:TWOHarq?
Indicates whether the UE supports two HARQ processes in DL and UL.
Return values:
<TwoHarqProc> NO | YES
Usage: Query only
Manual operation: See "Two HARQ Processes" on page 41
SENSe:NIOT:SIGN:UECapability:TRANsfer:RELease?
Returns the access stratum release supported by the UE.
Return values:
<Release> R13 | R14 | R15
Usage: Query only
Firmware/Software: V3.7.20, V3.7.60: added R14, V3.7.80: added R15
Manual operation: See "Release" on page 38
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:BANDs?
Returns all operating bands supported by the UE.
User Manual 1178.5689.02 ─ 12 145

Command Reference
Return values:
<Bands> OB1 | OB2 | OB3 | OB4 | OB5 | OB7 | OB8 | OB9 | OB10 |
OB11 | OB12 | OB13 | OB14 | OB17 | OB18 | OB19 | OB20 |
OB74 | OB85 | UDEF
Comma-separated list of all supported bands:
OBx: Standardized operating band
UDEF: User-defined operating band
Usage: Query only
Firmware/Software: V3.7.20, some bands added in later releases
Manual operation: See "Supported Bands" on page 39
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:BANDs:ALL?
Returns all operating bands supported by the UE and whether the UE supports a
power class with 20 dBm in a band.
For each supported band, a pair of values is returned:
{<Bands>, <PowerClass>}1, {<Bands>, <PowerClass>}2, ...
Return values:
<Bands> OB1 | OB2 | OB3 | OB4 | OB5 | OB7 | OB8 | OB9 | OB10 |
OB74 | OB85 | UDEF
<PowerClass> NO | YES
Support of power class with 20 dBm in the band
Usage: Query only
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:MPMax?
Returns whether the UE supports the handling of multiple "NS-Pmax" values.
Return values:
<MultiNSPmax> NO | YES
Usage: Query only
User Manual 1178.5689.02 ─ 12 146

Command Reference
Manual operation: See "Multi-NS-Pmax" on page 39
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:POWClass?
Returns whether the UE supports a power class with 20 dBm.
The information is returned per supported band. The values have the same order as
the bands returned by the command SENSe:NIOT:SIGN:UECapability:
TRANsfer:RF:BANDs?.
Return values:
<PowerClass> NO | YES
Comma-separated list of values, one value per supported band
Usage: Query only
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:POWFourteen <PowFourteen>
Indicates whether the UE supports a power class 6 with the maximum output power of
14 dBm.
Parameters:
<PowFourteen> NO | YES
*RST: NO
Manual operation: See "Power Class 14 dBm" on page 39
2.5.6 UE Measurement Report
The following commands enable UE measurement reporting and retrieve information

about the connected mobile as shown in the "UE Measurement Report" area of the
main view.
CONFigure:NIOT:SIGN:UEReport:ENABle................................................................... 148
SENSe:NIOT:SIGN:UEReport:RSRP?......................................................................... 148
SENSe:NIOT:SIGN:UEReport:RSRP:RANGe?............................................................. 148
SENSe:NIOT:SIGN:UEReport:RSRQ?.........................................................................148
SENSe:NIOT:SIGN:UEReport:RSRQ:RANGe?.............................................................149
User Manual 1178.5689.02 ─ 12 147

Command Reference
CONFigure:NIOT:SIGN:UEReport:ENABle <Enable>
Parameters:
<Enable> OFF | ON
*RST: False
Example: See Querying UE Measurement Reports
Manual operation: See "Report" on page 104
SENSe:NIOT:SIGN:UEReport:RSRP?
Returns the RSRP reported by the UE as dimensionless index.
Return values:
<RSRP> decimal
Range: 0 to 113
Usage: Query only
Manual operation: See "RSRP for serving NB-IoT cell" on page 43
SENSe:NIOT:SIGN:UEReport:RSRP:RANGe?
Returns the RSRP value range, corresponding to the RSRP index reported by the UE.
Return values:
<Lower> decimal
Range: -156 dBm to -44 dBm
<Upper> decimal
Usage: Query only
Manual operation: See "RSRP for serving NB-IoT cell" on page 43
SENSe:NIOT:SIGN:UEReport:RSRQ?
Returns the RSRQ reported by the UE as dimensionless index.
Return values:
<RSRQ> decimal
Range: -30 to 46
User Manual 1178.5689.02 ─ 12 148

Command Reference

Usage: Query only
Manual operation: See "RSRQ for serving NB-IoT cell" on page 43
SENSe:NIOT:SIGN:UEReport:RSRQ:RANGe?
Returns the RSRQ value range corresponding to the dimensionless index values
reported for the serving NB-IoT cell.
Return values:
<Lower> float
Range: -34 dB to 2.5 dB
Default unit: dB
<Upper> float
Range: -34 dB to 2.5 dB
Default unit: dB
Usage: Query only
Manual operation: See "RSRQ for serving NB-IoT cell" on page 43
2.5.7 Routing Settings
The following commands configure the signal input and output paths.
● Scenario Selection and Signal Routing.................................................................149
● RF Path Properties................................................................................................152
● Signal Settings...................................................................................................... 153
● User-Defined Band Configuration......................................................................... 157
2.5.7.1 Scenario Selection and Signal Routing
The commands in this section configure the scenario and select the paths for the gen-
erated downlink signal (output) and the analyzed signal (input).
CATalog:NIOT:SIGN:SCENario?..................................................................................150
ROUTe:NIOT:SIGN:SCENario?................................................................................... 150
ROUTe:NIOT:SIGN?.................................................................................................. 150
ROUTe:NIOT:SIGN:SCENario[:FLEXible]:SCELl...........................................................151
ROUTe:NIOT:SIGN:SCENario:SCFading[:FLEXible]:INTernal.........................................151
ROUTe:NIOT:SIGN:SCENario:TROFading[:FLEXible]:INTernal...................................... 152
User Manual 1178.5689.02 ─ 12 149

Command Reference
CATalog:NIOT:SIGN:SCENario?
Lists current scenarios.
Return values:
<Scenarios> SCEL | SCF | TROF
SCEL: "Standard Cell"
SCF: "Standard Cell - Fading"
TROF: "1CC - Fading - 2x1"
Example: See General Configuration
Usage: Query only
Firmware/Software: V3.7.40, V3.7.60: added SCF, TROF
Options: For fading scenarios: R&S CMW-KE100 and -KE500
ROUTe:NIOT:SIGN:SCENario?
Returns the active scenario.
Return values:
<Scenario> SCEL | SCF | TROF
<Fader> INTernal
Only internal fader at SUA supported, only returned for fading
scenarios
Usage: Query only
Firmware/Software: V3.7.20, V3.7.60: added <Scenario> SCF, TROF and <Fader>
Options: For fading scenarios: R&S CMW-KE100 and -KE500
ROUTe:NIOT:SIGN?
Returns the configured routing settings.
For possible connector and converter values, see Chapter 2.5.1.2, "Values for Signal
Path Selection", on page 127.
Return values:
<Scenario> SCEL | SCF | TROF
Active scenario
<RXConnector> RF connector for the input path
<RXConverter> RX module for the input path
User Manual 1178.5689.02 ─ 12 150

Command Reference
<TXConnector> RF connector for the output path

<TXConverter> TX module for the output path
<Fader> Internal fader, only returned for fading scenarios
Usage: Query only
Firmware/Software: V3.7.20, V3.7.60: <Scenario> SCF, TROF and <Fader>
ROUTe:NIOT:SIGN:SCENario[:FLEXible]:SCELl <BBBoard>, <RXConnector>,

<RXConverter>, <TXConnector>, <TXConverter>
Activates the scenario "Standard Cell" and selects the signal paths.
For possible parameter values, see Chapter 2.5.1.2, "Values for Signal Path Selection",
on page 127.
Parameters:
<BBBoard> Signaling unit
Example: See Chapter 2.4.1.2, "Configuring the Signal Paths",
on page 112
Manual operation: See "Scenario" on page 46
ROUTe:NIOT:SIGN:SCENario:SCFading[:FLEXible]:INTernal <PCCBBBoard>,
<RXConnector>, <RXConverter>, <TXConnector>, <TXConverter>,
<PCCFadingBoard>
Activates the scenario "Standard Cell Fading" and selects the signal paths.
on page 127.
Parameters:
<PCCBBBoard> Signaling unit
<PCCFadingBoard> Internal fader
User Manual 1178.5689.02 ─ 12 151

Command Reference
Options: R&S CMW-KE100 and -KE500

ROUTe:NIOT:SIGN:SCENario:TROFading[:FLEXible]:INTernal <PCCBBBoard>,
<RXConnector>, <RXConverter>, <TXConnector>, <TXConverter>,
<PCCFadingBoard>
Activates the scenario "1CC - Fading - 2x1" and selects the signal paths.
on page 127.
Parameters:
<PCCBBBoard> Signaling unit
<PCCFadingBoard> Internal fader
2.5.7.2 RF Path Properties
The following commands define path properties to be compensated (external attenua-

tion and time delay).
CONFigure:NIOT:SIGN:RFSettings:EATTenuation:OUTPut<n>...................................... 152
CONFigure:NIOT:SIGN:RFSettings:EATTenuation:INPut............................................... 153
CONFigure:NIOT:SIGN:RFSettings:EDC:OUTPut......................................................... 153
CONFigure:NIOT:SIGN:RFSettings:EDC:INPut.............................................................153
CONFigure:NIOT:SIGN:RFSettings:EATTenuation:OUTPut<n> <ExtRFOutAtt>
Defines an external attenuation (or gain, if the value is negative), to be applied to the
output connector.
Suffix: .
<n> 1..2
Output path
Parameters:
<ExtRFOutAtt> numeric
Range: -50 dB to 90 dB
*RST: 0 dB
Default unit: dB
User Manual 1178.5689.02 ─ 12 152

Command Reference

on page 112
Firmware/Software: V3.7.20, V3.7.60: added suffix <n>
Manual operation: See "External Attenuation" on page 49
CONFigure:NIOT:SIGN:RFSettings:EATTenuation:INPut <ExtRFInAtt>
input connector.
Parameters:
<ExtRFInAtt> numeric
*RST: 0 dB
Default unit: dB
on page 112
Manual operation: See "External Attenuation" on page 49
CONFigure:NIOT:SIGN:RFSettings:EDC:OUTPut <Time>
CONFigure:NIOT:SIGN:RFSettings:EDC:INPut <Time>
Defines the value of an external time delay in the output path and in the input path, so
that it can be compensated.
Parameters:
<Time> numeric
Range: 0 s to 20E-6 s
*RST: 0s
Default unit: s
Example: See Specifying General Settings
Manual operation: See "External Delay Compensation" on page 50
2.5.7.3 Signal Settings
The following commands provide settings for the downlink and uplink signals.
CONFigure:NIOT:SIGN:RFSettings:ALL:BWCHannel.................................................... 154
CONFigure:NIOT:SIGN:BAND.................................................................................... 154
CONFigure:NIOT:SIGN:RFSettings:CHANnel:DL.......................................................... 154
CONFigure:NIOT:SIGN:RFSettings:CHANnel:UL.......................................................... 154
CONFigure:NIOT:SIGN:RFSettings:FOFFset:DL...........................................................155
CONFigure:NIOT:SIGN:RFSettings:FOFFset:UL...........................................................155
CONFigure:NIOT:SIGN:RFSettings:ENPMode..............................................................155
User Manual 1178.5689.02 ─ 12 153

Command Reference
CONFigure:NIOT:SIGN:RFSettings:ENPower...............................................................156
CONFigure:NIOT:SIGN:RFSettings:UMARgin...............................................................156
CONFigure:NIOT:SIGN:RFSettings:MLOFfset.............................................................. 157
CONFigure:NIOT:SIGN:RFSettings:ALL:BWCHannel <Band>, <DLChannel>

Selects the operating band and the downlink channel number.
Parameters:
<Band> OB1 | OB2 | OB3 | OB4 | OB5 | OB7 | OB8 | OB9 | OB10 |
OB74 | OB85 | UDEF
Selects the operating band
*RST: OB1
<DLChannel> decimal
DL channel number
Range: depends on operating band
Manual operation: See "Operating Band, Channel, Frequency" on page 50
CONFigure:NIOT:SIGN:BAND <Band>
Selects the operating band (OB).
Parameters:
OB74 | OB85 | UDEF
*RST: OB1
Example: See Configuring Operating Bands and Channels
CONFigure:NIOT:SIGN:RFSettings:CHANnel:DL <Channel>
CONFigure:NIOT:SIGN:RFSettings:CHANnel:UL <Channel>
Select the DL and UL channel. They must be valid for the current operating band.
User Manual 1178.5689.02 ─ 12 154

Command Reference
By default, channels are specified via channel numbers. By appending a Hz unit (e.g.
Hz, kHz, MHz), you can set or query the channel via its center frequency (only integer
numbers accepted).
Setting the UL or the DL channel is sufficient. The other channel is calculated and set
automatically.
For channel numbers and frequencies depending on operating bands, see Chap-
ter 2.2.11, "Operating Bands", on page 27.
Parameters:
<Channel> decimal
Default unit: Ch
Example: CONFigure:NIOT:SIGN:RFSettings:CHANnel:DL? Hz
Returns the frequency in Hz
Firmware/Software: V3.7.20, V3.7.50: added unit Hz
CONFigure:NIOT:SIGN:RFSettings:FOFFset:DL <Offset>
CONFigure:NIOT:SIGN:RFSettings:FOFFset:UL <Offset>
Specifies a positive or negative frequency offset to be added to the center frequency of
the configured DL or UL channel.
Parameters:
<Offset> numeric
Range: -100E+3 Hz to 100E+3 Hz
*RST: 0 Hz
Default unit: Hz
Manual operation: See "Frequency Offset" on page 51
CONFigure:NIOT:SIGN:RFSettings:ENPMode <Mode>
Selects the expected nominal power mode. The expected nominal power of the UL sig-
nal can be defined manually or calculated automatically, according to the UL power
control settings.
For manual configuration, see:
● CONFigure:NIOT:SIGN:RFSettings:ENPower on page 156
● CONFigure:NIOT:SIGN:RFSettings:UMARgin on page 156
User Manual 1178.5689.02 ─ 12 155

Command Reference
For UL power control settings, see Chapter 2.5.10, "Uplink Power Control",
on page 168.
Parameters:
<Mode> MANual | ULPC
MANual
The expected nominal power and margin are specified manually.
ULPC
The expected nominal power is calculated according to the UL
power control settings. For the margin, 12 dB are applied.
*RST: ULPC
Manual operation: See "Exp. Nominal Power..., Margin" on page 52
CONFigure:NIOT:SIGN:RFSettings:ENPower <ExpectedPower>
Sets the expected nominal power of the UL signal in manual mode.
If the expected nominal power is calculated automatically according to the UL power
control settings, you can only query the result.
To configure the expected nominal power mode, see CONFigure:NIOT:SIGN:
RFSettings:ENPMode on page 155.
Parameters:
<ExpectedPower> numeric
In manual mode, the range of the expected nominal power can
be calculated as follows:
Range (expected nominal power) = range (input power) + exter-
nal attenuation - margin
The input power range is stated in the data sheet.
*RST: 23 dBm
Default unit: dBm
CONFigure:NIOT:SIGN:RFSettings:UMARgin <UserMargin>
Sets the margin that the R&S CMW adds to the expected nominal power to determine
the reference level in manual mode. If the expected nominal power is calculated auto-
matically according to the UL power control settings, a fix margin of 12 dB is used
instead.
The reference level minus the external input attenuation must be within the power
range of the selected input connector; refer to the data sheet.
User Manual 1178.5689.02 ─ 12 156

Command Reference
Refer also to the following commands:

● CONFigure:NIOT:SIGN:RFSettings:ENPMode on page 155
● CONFigure:NIOT:SIGN:RFSettings:ENPower on page 156
● CONFigure:NIOT:SIGN:RFSettings:EATTenuation:INPut
on page 153
Parameters:
<UserMargin> numeric
Range: 0 dB to (55 dB + external attenuation - expected
nominal power)
*RST: 12 dB
Default unit: dB
CONFigure:NIOT:SIGN:RFSettings:MLOFfset <MixLevOffset>
Varies the input level of the mixer in the analyzer path.
Parameters:
<MixLevOffset> numeric
*RST: 0 dB
Default unit: dB
Manual operation: See "Mixer Level Offset" on page 52
2.5.7.4 User-Defined Band Configuration
The following commands define user-specific operating band.

CONFigure:NIOT:SIGN:RFSettings:UDEFined:CHANnel:UL:MAXimum?........................ 157
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:DL:MAXimum?.................... 158
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:UL:MAXimum?.................... 158
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:UL:MINimum?..................... 158
CONFigure:NIOT:SIGN:RFSettings:UDEFined:SET...................................................... 159
CONFigure:NIOT:SIGN:RFSettings:UDEFined:CHANnel:UL:MAXimum?
Queries the maximum channel number in uplink for user-defined operating band.
Return values:
<Channel> decimal
User Manual 1178.5689.02 ─ 12 157

Command Reference
Usage: Query only

Manual operation: See "User-Defined Band Definition" on page 51
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:DL:MAXimum?
Queries the maximum downlink frequency for user-defined operating band.
Return values:
<Frequency> decimal
Range: 0 Ch to 262.143E+3 Ch
Default unit: Ch
Usage: Query only
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:UL:MAXimum?
Queries the maximum uplink frequency for user-defined operating band.
Return values:
<Frequency> decimal
Default unit: Hz
Usage: Query only
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:UL:MINimum?
Queries the minimum uplink frequency for user-defined operating band.
Return values:
<Frequency> decimal
Default unit: Hz
Usage: Query only
User Manual 1178.5689.02 ─ 12 158

Command Reference
CONFigure:NIOT:SIGN:RFSettings:UDEFined:SET <Band>, <UDefEnable>,

<BandInd>, <ULDLSep>, <DLMinCh>, <DLMaxCh>, <DLMinFreq>, <ULMinCh>
Configures the user-defined operating band.
Parameters:
<Band> UDEF
User-defined band
<UDefEnable> OFF | ON
Enable / disables user-defined band
*RST: OFF
<BandInd> numeric
Band indicator
Range: 1 to 256
*RST: 1
<ULDLSep> decimal
UL / DL separation value
Default unit: Hz
<DLMinCh> decimal
Minimum channel number in downlink
Default unit: Ch
<DLMaxCh> decimal
Maximum channel number in downlink
Default unit: Ch
<DLMinFreq> decimal
Minimum frequency in downlink
*RST: 2.11E+9 Hz
Default unit: Hz
<ULMinCh> decimal
Minimum channel number in uplink
Default unit: Ch
User Manual 1178.5689.02 ─ 12 159

Command Reference
The following commands configure the internal fader of the R&S CMW.
The following commands configure the fading simulator of the internal fader for down-
link.
CONFigure:NIOT:SIGN:FADing:FSIMulator:DSHift........................................................160
CONFigure:NIOT:SIGN:FADing:FSIMulator:DSHift:MODE............................................. 160
CONFigure:NIOT:SIGN:FADing:FSIMulator:ENABle......................................................161
CONFigure:NIOT:SIGN:FADing:FSIMulator:GLOBal:SEED............................................161
CONFigure:NIOT:SIGN:FADing:FSIMulator:ILOSs:LOSS...............................................161
CONFigure:NIOT:SIGN:FADing:FSIMulator:ILOSs:MODE............................................. 162
CONFigure:NIOT:SIGN:FADing:FSIMulator:PROFile.....................................................162
CONFigure:NIOT:SIGN:FADing:FSIMulator:RESTart..................................................... 163
CONFigure:NIOT:SIGN:FADing:FSIMulator:RESTart:MODE.......................................... 163
SENSe:NIOT:SIGN:FADing:FSIMulator:ILOSs:CSAMples<ClippingCounter>?.................163
CONFigure:NIOT:SIGN:FADing:FSIMulator:DSHift <Frequency>
Sets the maximum Doppler frequency for the fading simulator.
A setting is only allowed in USER mode (see CONFigure:NIOT:SIGN:FADing:
FSIMulator:DSHift:MODE).
Parameters:
<Frequency> numeric
Range: 1 Hz to 2000 Hz
*RST: 5 Hz
Default unit: Hz
Example: See Configuring Internal Fading
Manual operation: See "Doppler Frequency Mode, Doppler Frequency" on page 55
CONFigure:NIOT:SIGN:FADing:FSIMulator:DSHift:MODE <Mode>
Sets the Doppler shift mode.
Parameters:
<Mode> NORMal | USER
NORMal: The maximum Doppler frequency is determined by the
fading profile.
USER: The maximum Doppler frequency is configurable.
*RST: NORM
User Manual 1178.5689.02 ─ 12 160

Command Reference
Manual operation: See "Doppler Frequency Mode, Doppler Frequency" on page 55
CONFigure:NIOT:SIGN:FADing:FSIMulator:ENABle <Enable>
Enables/disables the fading simulator.
Parameters:
<Enable> OFF | ON
Manual operation: See "Enable" on page 53
CONFigure:NIOT:SIGN:FADing:FSIMulator:GLOBal:SEED <Seed>
Sets the start seed for the pseudo-random fading algorithm.
Parameters:
<Seed> numeric
Range: 0 to 9
*RST: 0
Manual operation: See "Start Seed" on page 54
CONFigure:NIOT:SIGN:FADing:FSIMulator:ILOSs:LOSS <InsertionLoss>
Sets the insertion loss for the fading simulator.
A setting is only allowed in USER mode (see CONFigure:NIOT:SIGN:FADing:
FSIMulator:ILOSs:MODE).
Parameters:
<InsertionLoss> numeric
Range: 0 dB to 18 dB
*RST: 0 dB
Default unit: dB
User Manual 1178.5689.02 ─ 12 161

Command Reference
Manual operation: See "Insertion Loss" on page 54
CONFigure:NIOT:SIGN:FADing:FSIMulator:ILOSs:MODE <InsertLossMode>
Sets the insertion loss mode.
Parameters:
<InsertLossMode> NORMal | USER
NORMal: The insertion loss is determined by the fading profile.
USER: The insertion loss is configurable.
*RST: NORM
CONFigure:NIOT:SIGN:FADing:FSIMulator:PROFile <Profile>
Selects a propagation condition profile for fading.
Parameters:
<profile> EP5Low | EP5Medium | EP5High | EV5Low | EV5Medium |
EV5High | EV7Low | EV7Medium | EV7High | EVL200 |
EVM200 | EVH200 | ET3Low | ET3Medium | ET3High |
ET7Low | ET7Medium | ET7High | ETL30 | ETM30 | ETH30 |
HSTRain | CTESt
EP5Low | EP5Medium | EP5High
EPA, 5-Hz Doppler, low/medium/high correlation
EV5Low | EV5Medium | EV5High
EVA, 5-Hz Doppler, low/medium/high correlation
EV7Low | EV7Medium | EV7High
EVL200 | EVM200 | EVH200
ETL30 | ETM30 | ETH30
ETU, 30-Hz Doppler, low/medium/high correlation
ET7Low | ET7Medium | ET7High
ET3Low | ET3Medium | ET3High
HSTRain
High-speed train scenario
CTESt
Multi-path profile for CQI tests
*RST: EP5Low
User Manual 1178.5689.02 ─ 12 162

Command Reference

Manual operation: See "Profile" on page 53
CONFigure:NIOT:SIGN:FADing:FSIMulator:RESTart
Restarts the fading process in MANual mode (see also CONFigure:NIOT:SIGN:
FADing:FSIMulator:RESTart:MODE).
Usage: Event
Manual operation: See "Restart Event" on page 54
CONFigure:NIOT:SIGN:FADing:FSIMulator:RESTart:MODE <RestartMode>
Sets the restart mode of the fading simulator.
Parameters:
<RestartMode> AUTO | MANual
AUTO: fading automatically starts with the DL signal
MANual: fading is started and restarted manually (see
CONFigure:NIOT:SIGN:FADing:FSIMulator:
RESTart)
*RST: AUTO
Manual operation: See "Restart Event" on page 54
SENSe:NIOT:SIGN:FADing:FSIMulator:ILOSs:CSAMples<ClippingCounter>?
Returns the percentage of clipped samples for the output path number.
Suffix: .
<ClippingCounter> 1..2
Output path number
Return values:
<ClippedSamples> float
Range: 0 % to 100 %
Default unit: %
User Manual 1178.5689.02 ─ 12 163

Command Reference

Usage: Query only
2.5.8.2 DL Settings
The following commands query noise power information for downlink.

CONFigure:NIOT:SIGN:FADing:POWer:NOISe?...........................................................164
CONFigure:NIOT:SIGN:FADing:POWer:NOISe:TOTal?................................................. 164
CONFigure:NIOT:SIGN:FADing:POWer:SUM?............................................................. 165
CONFigure:NIOT:SIGN:FADing:POWer:NOISe?
Queries the calculated noise power on the DL channel, i.e. within the cell bandwidth.
Return values:
<NoisePower> float
Default unit: dBm
Usage: Query only
Manual operation: See "Noise (System BW) Power" on page 55
CONFigure:NIOT:SIGN:FADing:POWer:NOISe:TOTal?
Queries the total noise power.
Return values:
<NoisePower> float
Default unit: dBm
Usage: Query only
Manual operation: See "Noise (Total BW) Power" on page 55
User Manual 1178.5689.02 ─ 12 164

Command Reference
CONFigure:NIOT:SIGN:FADing:POWer:SUM?
Queries the calculated total power (signal + noise) on the DL channel, i.e. within the
cell bandwidth.
Return values:
<Power> float
Default unit: dBm
Usage: Query only
Manual operation: See "Signal + Noise (System BW) Power" on page 55
2.5.8.3 Fading Module AWGN
The following commands configure the AWGN generator of the internal fader for down-
link.
CONFigure:NIOT:SIGN:FADing:AWGN:BWIDth:NOISe?............................................... 165
CONFigure:NIOT:SIGN:FADing:AWGN:BWIDth:RATio.................................................. 165
CONFigure:NIOT:SIGN:FADing:AWGN:ENABle............................................................166
CONFigure:NIOT:SIGN:FADing:AWGN:FOFFset.......................................................... 166
CONFigure:NIOT:SIGN:FADing:AWGN:SNRatio........................................................... 166
CONFigure:NIOT:SIGN:FADing:AWGN:BWIDth:NOISe?
Queries the noise bandwidth.
Return values:
<NoiseBandwidth> float
Range: 0 Hz to 80E+6 Hz
Default unit: Hz
Usage: Query only
Manual operation: See "Noise Bandwidth" on page 56
CONFigure:NIOT:SIGN:FADing:AWGN:BWIDth:RATio <Ratio>
Specifies the minimum ratio between the noise bandwidth and the cell bandwidth.
User Manual 1178.5689.02 ─ 12 165

Command Reference
Parameters:
<Ratio> numeric
Range: 1 to 1000
*RST: 1
Manual operation: See "Min. Noise/System BW Ratio" on page 56
CONFigure:NIOT:SIGN:FADing:AWGN:ENABle <Enable>
Enables or disables AWGN insertion via the fading module.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Enable" on page 56
CONFigure:NIOT:SIGN:FADing:AWGN:FOFFset <Offset>
Shifts the center frequency of the noise bandwidth relative to the carrier center fre-
quency.
Parameters:
<Offset> numeric
*RST: 0 Hz
Default unit: Hz
CONFigure:NIOT:SIGN:FADing:AWGN:SNRatio <Ratio>
Specifies the signal to noise ratio for the AWGN inserted on the internal fading module.
User Manual 1178.5689.02 ─ 12 166

Command Reference
Parameters:
<Ratio> numeric
*RST: 0 dB
Default unit: dB
Manual operation: See "Signal/Noise Ratio" on page 57
2.5.9 Downlink Power Levels
The following commands define power levels of physical downlink channels and sig-
nals.
CONFigure:NIOT:SIGN:DL:NRSepre:LEVel..................................................................167
CONFigure:NIOT:SIGN:DL:OCNG...............................................................................167
CONFigure:NIOT:SIGN:DL:AWGN.............................................................................. 168
CONFigure:NIOT:SIGN:DL:NRSepre:LEVel <Level>
Defines the energy per resource element (EPRE) of the narrowband reference signal
(NRS). The power levels of resource elements used for other channels/signals are
derived from this power level.
The allowed value range depends on many settings, for example on the used connec-
tor, the external attenuation, the AWGN state and the operation mode.
Parameters:
<Level> numeric
*RST: -85 dBm/15kHz
Example: See Configuring DL Power Levels
Manual operation: See "NRS EPRE" on page 57
CONFigure:NIOT:SIGN:DL:OCNG <OCNG>
Enables or disables the OFDMA channel noise generator (OCNG).
Parameters:
<OCNG> OFF | ON
*RST: OFF
Manual operation: See "OCNG" on page 57
User Manual 1178.5689.02 ─ 12 167

Command Reference
CONFigure:NIOT:SIGN:DL:AWGN <AWGN>
Specifies the total level of the additional white Gaussian noise (AWGN) interferer. The
unit dBm/15 kHz indicates the spectral density integrated across one subcarrier.
The range depends on several parameters. It is a subset of the range of the RS EPRE.
Parameters:
<AWGN> numeric | ON | OFF
Range: depends on many parameters
*RST: -98 dBm/15kHz, OFF
Default unit: dBm/15kHz
Additional parameters: OFF | ON (disables | enables the AWGN
interferer)
Manual operation: See "AWGN" on page 58
2.5.10 Uplink Power Control
The following commands define parameters related to UE uplink power control by the
instrument.
2.5.10.1 General Power Control Parameters
The following commands are related to the parameters at the highest level of the
"Uplink Power Control" section.
CONFigure:NIOT:SIGN:UL:NPUSch:ULNPower........................................................... 168
SENSe:NIOT:SIGN:UL:ADPower:ENPPpower?............................................................ 169
SENSe:NIOT:SIGN:UL:ADPower:EFNPower<format>?................................................. 169
CONFigure:NIOT:SIGN:UL:PMAX............................................................................... 169
CONFigure:NIOT:SIGN:UL:NPUSch:ULNPower <Power>
Defines a cell-specific nominal power value for maximum subcarrier allocation in the
UL. The maximum allowed allocation depends on the subcarrier spacing.
This command is only relevant for basic configuration and rejected if advanced config-
uration is active.
Parameters:
<Power> numeric
Range: -50 dBm to 34 dBm
*RST: 23 dBm
Default unit: dBm
Example: See Configuring UL Power Settings
User Manual 1178.5689.02 ─ 12 168

Command Reference
Manual operation: See "Uplink Nominal Power" on page 58
SENSe:NIOT:SIGN:UL:ADPower:ENPPpower?
Queries the expected power of the first preamble, resulting from the UL power control
settings.
Return values:
<Power> float
Default unit: dBm
Usage: Query only
Manual operation: See "Exp. NPRACH Preamble Power" on page 59
SENSe:NIOT:SIGN:UL:ADPower:EFNPower<format>?
Queries the expected NPUSCH power, for the NPUSCH formats 1 and 2.
Suffix: .
<format> 1, 2
Return values:
<ExpectedPower> float
Default unit: dBm
Usage: Query only
Manual operation: See "Exp. NPUSCH Format 1/2 Nom. Power" on page 59
CONFigure:NIOT:SIGN:UL:PMAX <Power>
Specifies the maximum allowed UE power.
Parameters:
<Power> numeric | ON | OFF
*RST: 24 dBm
Default unit: dBm
Additional parameters: OFF | ON (disables | enables signaling of
the value to the UE)
Manual operation: See "Max. Allowed Power P-Max" on page 59
User Manual 1178.5689.02 ─ 12 169

Command Reference
2.5.10.2 Advanced NPRACH and NPUSCH Power Settings
The following commands define advanced uplink power control parameters.

CONFigure:NIOT:SIGN:UL:ADPower:ENABle.............................................................. 170
CONFigure:NIOT:SIGN:UL:ADPower:NRSPower..........................................................170
SENSe:NIOT:SIGN:UL:ADPower:PATHloss?................................................................170
CONFigure:NIOT:SIGN:UL:ADPower:PIRPower........................................................... 171
CONFigure:NIOT:SIGN:UL:ADPower:PNNPusch.......................................................... 171
CONFigure:NIOT:SIGN:UL:ADPower:PCALpha............................................................171
CONFigure:NIOT:SIGN:UL:ADPower:ENABle <Enable>
Enables or disables advanced configuration of the NPRACH and open loop power set-
tings via the other CONFigure:NIOT:SIGN:UL:ADPower:... commands.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Enable Advanced Settings" on page 60
CONFigure:NIOT:SIGN:UL:ADPower:NRSPower <NRefSignalPower>
Specifies the "nrs-Power" value, signaled to the UE if advanced UL power configura-
tion applies.
Parameters:
<NRefSignalPower> numeric
*RST: 42 dBm
Default unit: dBm
Manual operation: See "NRS Power" on page 60
SENSe:NIOT:SIGN:UL:ADPower:PATHloss?
Queries the pathloss resulting from the advanced UL power settings.
Return values:
<Pathloss> float
Default unit: dB
Usage: Query only
User Manual 1178.5689.02 ─ 12 170

Command Reference
Manual operation: See "Pathloss" on page 60
CONFigure:NIOT:SIGN:UL:ADPower:PIRPower <TargetPower>
Specifies the "preambleInitialReceivedTargetPower" value, signaled to the UE if
advanced UL power configuration applies.
Parameters:
<TargetPower> numeric
Increment: 2 dB
*RST: -104 dBm
Default unit: dBm
Manual operation: See "Preamble Initial Received Target Power" on page 60
CONFigure:NIOT:SIGN:UL:ADPower:PNNPusch <P0NomNPUSCH>
Specifies the "p0-NominalNPUSCH" value, signaled to the UE if advanced UL power
configuration applies.
Parameters:
<P0NomNPUSCH> numeric
*RST: -115 dBm
Default unit: dBm
Manual operation: See "P0 Nominal NPUSCH" on page 61
CONFigure:NIOT:SIGN:UL:ADPower:PCALpha <PathCompAlpha>
Specifies the value of parameter "alpha", signaled to the UE if advanced UL power
configuration applies.
Parameters:
<PathCompAlpha> ZERO | DOT4 | DOT5 | DOT6 | DOT7 | DOT8 | DOT9 | ONE
ZERO: 0
DOT4 ... DOT9: 0.4 ... 0.9
ONE: 1.0
*RST: ONE
User Manual 1178.5689.02 ─ 12 171

Command Reference
Manual operation: See "Pathloss Compensation Alpha" on page 61
2.5.11 Physical Cell Setup
The commands in this section configure physical layer attributes of the simulated cell.
● General Cell Settings............................................................................................ 172
● In-Band / Guard-Band Configuration.....................................................................173
● NPRACH Settings................................................................................................. 177
● Coverage Enhancement Settings......................................................................... 179
● Wake Up Signal Settings...................................................................................... 181
● Early Data Transmission Settings......................................................................... 183
2.5.11.1 General Cell Settings
The commands in this section configure main parameters of the simulated cell.
CONFigure:NIOT:SIGN:DMODe..................................................................................172
CONFigure:NIOT:SIGN:CELL:OPERmode................................................................... 172
CONFigure:NIOT:SIGN:CELL:PCID.............................................................................173
CONFigure:NIOT:SIGN:CELL:SCSPacing....................................................................173
CONFigure:NIOT:SIGN:DMODe <Mode>
Specifies the duplex mode. The current version only supports FDD.
Parameters:
<Mode> FDD
*RST: FDD
Example: See Configuring Physical Cell Setup
Manual operation: See "Duplex Mode" on page 61
CONFigure:NIOT:SIGN:CELL:OPERmode <OpMode>
Selects the operation mode.
Parameters:
<OpMode> SALM | GBOP | IBOP
SALM: standalone mode
GBOP: guard-band operation mode
IBOP: in-band operation mode
*RST: SALM
User Manual 1178.5689.02 ─ 12 172

Command Reference
Manual operation: See "Operation Mode" on page 62
CONFigure:NIOT:SIGN:CELL:PCID <ID>
Defines the physical cell ID used for the generation of the synchronization signals.
Parameters:
<ID> decimal
Range: 0 to 503
*RST: 0
Manual operation: See "Physical Cell ID" on page 62
CONFigure:NIOT:SIGN:CELL:SCSPacing <SubCarrSpacing>
Selects the uplink subcarrier spacing.
Parameters:
<SubCarrSpacing> S3K75 | S15K
S3K75: 3.75 kHz
S15K: 15 kHz
*RST: S15K
Firmware/Software: V3.7.20, V3.7.30 added S3K75
Manual operation: See "UL Subcarrier Spacing" on page 62
2.5.11.2 In-Band / Guard-Band Configuration
The commands in this section configure the parameters for in-band or guard-band
operation.
CONFigure:NIOT:SIGN:CELL:IBGBand:FLEXdlul:ENABle............................................. 174
CONFigure:NIOT:SIGN:CELL:IBGBand:BANDwidth......................................................174
CONFigure:NIOT:SIGN:CELL:IBGBand:CRSize........................................................... 174
CONFigure:NIOT:SIGN:CELL:IBGBand:POFFset......................................................... 175
CONFigure:NIOT:SIGN:CELL:IBGBand:IPCI................................................................ 175
CONFigure:NIOT:SIGN:CELL:IBGBand:IBCPosition..................................................... 175
CONFigure:NIOT:SIGN:CELL:IBGBand:IBUCposition................................................... 176
CONFigure:NIOT:SIGN:CELL:IBGBand:GBCPosition....................................................176
CONFigure:NIOT:SIGN:CELL:IBGBand:GBUCposition..................................................176
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:DL?....................................................177
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:UL?....................................................177
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:DL?........................................... 177
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:UL?........................................... 177
User Manual 1178.5689.02 ─ 12 173

Command Reference
CONFigure:NIOT:SIGN:CELL:IBGBand:FLEXdlul:ENABle <Enable>
Enables or disables the dependency between UL and DL carrier frequencies for in-
band and guard-band operation.
Parameters:
<Enable> OFF | ON
ON: UL and DL frequencies can be configured independently
OFF: changing the frequency in one direction changes also the
frequency in the other direction using fixed "UL/DL Separation"
value.
*RST: OFF
Manual operation: See "Enable Flexible UL/DL Separation" on page 63
CONFigure:NIOT:SIGN:CELL:IBGBand:BANDwidth <Bandwidth>
Channel bandwidth for the generated LTE signal.
Parameters:
<Bandwidth> B030 | B050 | B100 | B150 | B200
LTE cell bandwidth in MHz: 3, 5, 10, 15, or 20
B030 is only allowed for "In-Band Operation". It cannot be used
in operation mode "Guard-Band Operation".
*RST: B100
Manual operation: See "LTE Bandwidth" on page 63
CONFigure:NIOT:SIGN:CELL:IBGBand:CRSize <CtrlRegionSize>
Configures the control region size for the in-band operation mode.
Parameters:
<CtrlRegionSize> CRS1 | CRS2 | CRS3
1, 2 or 3 OFDM symbols at the beginning of each DL subframe
*RST: CRS1
Manual operation: See "LTE Control Region Size" on page 63
User Manual 1178.5689.02 ─ 12 174

Command Reference
CONFigure:NIOT:SIGN:CELL:IBGBand:POFFset <PowerOffset>
Sets the power offset of the NB-IoT NRS symbols relative to the LTE CRS symbols.
Parameters:
<PowerOffset> N6 | N4D7 | N3 | N1D7 | ZERO | P1 | P1D2 | P2 | P3 | P4 |
P4D2 | P5 | P6 | P7 | P8 | P9
Power offset in dB: -6, -4.77, -3, -1.77, 0, 1, 1.23, 2 to 4, 4.23, 5
to 9
*RST: ZERO
Firmware/Software: V3.7.40, V3.7.50: changed usage (query only) and range exten-
ded, V3.8.20: changed usage - setting possible
Manual operation: See "NRS-CRS Power Offset" on page 63
CONFigure:NIOT:SIGN:CELL:IBGBand:IPCI <InbandPCI>
Selects the PCI mode for the in-band operation mode. It indicates whether the NB-IoT
cell uses the same physical cell ID as the LTE cell.
Parameters:
<InbandPCI> SAME | DIFF
SAME: "Inband-SamePCI"
DIFF: "Inband-DifferentPCI"
*RST: SAME
Manual operation: See "In-Band PCI" on page 63
CONFigure:NIOT:SIGN:CELL:IBGBand:IBCPosition <IBCarrPos>
Specifies the number of the LTE RB at the NB-IoT channel position, for the in-band
operation mode.
Only specific values within the stated range are allowed, depending on the LTE chan-
nel BW, see Table 2-2.
Parameters:
<IBCarrPos> numeric
Range: 2 to 95
*RST: 4
Manual operation: See "In-Band (DL/UL) Carrier Position" on page 64
User Manual 1178.5689.02 ─ 12 175

Command Reference
CONFigure:NIOT:SIGN:CELL:IBGBand:IBUCposition <CarPos>
Specifies the number of the LTE RB at the NB-IoT UL channel position, for the in-band
operation.
Parameters:
<CarPos> numeric | ON | OFF
Range: 0 to 49
*RST: 0
Additional parameters: OFF | ON (disables | enables the shift of
the UL channel)
Manual operation: See "In-Band (DL/UL) Carrier Position" on page 64
CONFigure:NIOT:SIGN:CELL:IBGBand:GBCPosition <GBCarrPos>
Selects the upper or lower guard band for guard-band operation mode.
Parameters:
<GBCarrPos> UP | LOW
*RST: UP
Manual operation: See "Guard-Band Carrier Position" on page 64
CONFigure:NIOT:SIGN:CELL:IBGBand:GBUCposition <CarPos>
Specifies the LTE subcarrier index at the NB-IoT UL channel position for the guard-
band operation.
Parameters:
<CarPos> numeric | ON | OFF
LTE subcarrier index for UL
Range: 306 to 327
*RST: 306
Additional parameters: OFF | ON (disables | enables the shift of
uplink channel)
User Manual 1178.5689.02 ─ 12 176

Command Reference
Manual operation: See "Guard-Band Uplink Carrier Position" on page 64
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:DL?
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:UL?
Query the DL and UL LTE carrier center frequencies resulting from the in-band mode
or guard-band mode settings.
Return values:
<Frequency> float
Default unit: Hz
Usage: Query only
Manual operation: See "LTE Frequency" on page 64
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:DL?
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:UL?
Query the DL and UL channel raster offsets resulting from the in-band mode or guard-
band mode settings.
For the standalone mode, the channel raster offset is zero.
Return values:
<ChannelOffset> float
Default unit: Hz
Usage: Query only
Manual operation: See "NB-IoT Channel Raster Offset" on page 65
2.5.11.3 NPRACH Settings
The commands in this section configure settings related to the random access proce-
dure.
CONFigure:NIOT:SIGN:CELL:NPRach:NOResponse.................................................... 177
CONFigure:NIOT:SIGN:CELL:NPRach:PRAMping........................................................ 178
CONFigure:NIOT:SIGN:CELL:NPRach:PREFormat...................................................... 178
CONFigure:NIOT:SIGN:CELL:NPRach:MAXTrans........................................................ 178
CONFigure:NIOT:SIGN:CELL:NPRach:NOResponse <NoResponse>
Selects whether the signaling application ignores received preambles or not.
User Manual 1178.5689.02 ─ 12 177

Command Reference
Parameters:
<NoResponse> OFF | ON
OFF: respond to received preambles
ON: ignore received preambles
*RST: OFF
Manual operation: See "No Response to Preambles" on page 65
CONFigure:NIOT:SIGN:CELL:NPRach:PRAMping <PowerRamping>
Specifies the transmit power difference between two consecutive preambles.
Parameters:
<PowerRamping> S0 | S2 | S4 | S6
0 dB, 2 dB, 4 dB, 6 dB
*RST: S2
Manual operation: See "Power Ramping Step" on page 66
CONFigure:NIOT:SIGN:CELL:NPRach:PREFormat <NPRACHpreForm>
Selects the preamble format.
Parameters:
<NPRACHpreForm> 0 | 1
*RST: 0
Manual operation: See "Preamble Format" on page 66
CONFigure:NIOT:SIGN:CELL:NPRach:MAXTrans <MaxTrans>
Configures the maximum number of preamble transmissions.
Parameters:
<MaxTrans> T6 | T10 | T50
T<n>: max <n> transmissions
*RST: T6
User Manual 1178.5689.02 ─ 12 178

Command Reference
Manual operation: See "Max. Number of Preamble Transmissions" on page 66
2.5.11.4 Coverage Enhancement Settings
The commands in this section configure the coverage enhancement (CE) parameters.
CONFigure:NIOT:SIGN:CELL:CENHt:NTHReshold.......................................................179
SENSe:NIOT:SIGN:CELL:CENHt:REPCelev?.............................................................. 179
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:ZERO.................................................. 180
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:ONE.................................................... 180
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:TWO................................................... 180
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:ZERO....................................... 180
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:ONE......................................... 180
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:TWO........................................ 180
CONFigure:NIOT:SIGN:CELL:CENHt:RSRPthr:ONE.....................................................180
CONFigure:NIOT:SIGN:CELL:CENHt:RSRPthr:TWO.................................................... 180
CONFigure:NIOT:SIGN:CELL:CENHt:NTHReshold <nrthreshold>
Specifies the maximum number of CE levels supported and signaled by the NB-IoT
eNodeB.
Parameters:
No.Of_Threshold numeric
0: only CE level 0 supported
1: levels 0, 1 supported
2: levels 0, 1, 2 supported
Range: 0 to 2
*RST: 0
Example: See Configuring Physical Cell Setup.
Manual operation: See "Number of Threshold" on page 66
SENSe:NIOT:SIGN:CELL:CENHt:REPCelev?
Queries the CE level reported by the UE.
Return values:
<CE_Level> decimal
Range: 0 to 2
Usage: Query only
Manual operation: See "CE Level Report" on page 67
User Manual 1178.5689.02 ─ 12 179

Command Reference
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:ZERO <RepperPreamble0>
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:ONE <RepperPreamble1>
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:TWO <repperpreamble2>
Specifies the number of repetitions per preamble transmission attempt (repetitions with
same preamble and power) for the selected CE level (..ZERO, ..:ONE, or ..:TWO).
Parameters:
RepPerPreamble 1 | 2 | 4 | 8 | 16 | 32 | 64 | 128
Maximum repetitions per preamble for the selected CE level
*RST: Preamble 0 to 2: 1, 4, 8 repetitions
Manual operation: See "Repetitions per Preamble x" on page 67
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:ZERO <Nrep>
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:ONE <MNRep>
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:TWO <Nrep>
Sets the maximum number of NPDCCH repetitions during random access (RA) proce-
dure for the selected CE level (..ZERO, ..:ONE, or ..:TWO).
Parameters:
<Nrep> R1 | R2 | R4 | R8 | R16 | R32 | R64 | R128 | R256 | R512 |
R1024 | R2048
*RST: R16
Manual operation: See "NPDCCH Num. Repetitions RA x" on page 67
CONFigure:NIOT:SIGN:CELL:CENHt:RSRPthr:ONE <rsrpthr>
CONFigure:NIOT:SIGN:CELL:CENHt:RSRPthr:TWO <rsrpthr>
Defines the RSRP threshold for NPRACH for the selected CE level( ..:ONE
or ..:TWO).
The value is defined per CE level. With increasing CE level, the RSRP threshold must
decrease.
Parameters:
<rsrpthr> numeric
*RST: Level 1: -70 dBm , level 2: -80 dBm
Manual operation: See "RSRP Threshold x" on page 67
User Manual 1178.5689.02 ─ 12 180

Command Reference
2.5.11.5 Wake Up Signal Settings
The commands in this section configure wake up signal (WUS) for battery saving.
CONFigure:NIOT:SIGN:CELL:WUSignal:DRX:TOFFset.................................................181
CONFigure:NIOT:SIGN:CELL:WUSignal:DRXCycles:RELaxed...................................... 181
CONFigure:NIOT:SIGN:CELL:WUSignal:DURFactor:MAX............................................. 181
CONFigure:NIOT:SIGN:CELL:WUSignal:EDRX:TOFFset:LONG.................................... 182
CONFigure:NIOT:SIGN:CELL:WUSignal:EDRX:TOFFset:SHORt................................... 182
CONFigure:NIOT:SIGN:CELL:WUSignal:ENABle..........................................................182
CONFigure:NIOT:SIGN:CELL:WUSignal:FPOPos.........................................................183
CONFigure:NIOT:SIGN:CELL:WUSignal:NUMPos........................................................ 183
CONFigure:NIOT:SIGN:CELL:WUSignal:PAGing:DISable..............................................183
CONFigure:NIOT:SIGN:CELL:WUSignal:DRX:TOFFset <TODRX>
ated PO for DRX with a non-zero gap.
Parameters:
<TODRX> numeric
In ms: 40, 80, 160, 240
*RST: 40
Manual operation: See "Time Offset" on page 69
CONFigure:NIOT:SIGN:CELL:WUSignal:DRXCycles:RELaxed <DRXRelaxed>
Sets the maximum No. of consecutive relaxed DRX cycles during which the UE can
use WUS for synchronization.
Parameters:
<DRXRelaxed> 1, 2, 4, 8
*RST: 1
Manual operation: See "No. of DRX Cycles Relaxed" on page 69
CONFigure:NIOT:SIGN:CELL:WUSignal:DURFactor:MAX <MDF>
Sets the maximal duration of WUS.
User Manual 1178.5689.02 ─ 12 181

Command Reference
Parameters:
<MDF> R128 | R64 | R32 | R16 | R8 | R4 | R2
Rx: Maximal duration of WUS expressed in factor of subframes
1/x
*RST: R128
Manual operation: See "Max Duration Factor" on page 68
CONFigure:NIOT:SIGN:CELL:WUSignal:EDRX:TOFFset:LONG <TOffset>
Sets and enables the offset from the end of the configured maximum WUS duration to
the associated PO for eDRX with a long non-zero gap.
Parameters:
<TOffset> numeric | ON | OFF
In ms: 1000, 2000
*RST: 1000
Additional parameters: OFF | ON (disables | enables the long
non-zero gap.)
CONFigure:NIOT:SIGN:CELL:WUSignal:EDRX:TOFFset:SHORt <TOffset>
ated PO for eDRX with a short non-zero gap.
Parameters:
<TOffset> numeric
In ms: 40, 80, 160, 240
*RST: 40
CONFigure:NIOT:SIGN:CELL:WUSignal:ENABle <Enable>
Enables or disables wake up signal (WUS).
Parameters:
<Enable> OFF | ON
*RST: OFF
User Manual 1178.5689.02 ─ 12 182

Command Reference

Manual operation: See "Enable WUS" on page 68
CONFigure:NIOT:SIGN:CELL:WUSignal:FPOPos <FirstPO>
Sets the first PO to send paging.
Parameters:
<FirstPO> numeric
Range: 1 to 1
*RST: 1
CONFigure:NIOT:SIGN:CELL:WUSignal:NUMPos <NumPO>
Sets the number of consecutive POs mapped to one WUS.
Parameters:
<NumPO> ONE | TWO | FOUR
*RST: ONE
Manual operation: See "Num POs" on page 68
CONFigure:NIOT:SIGN:CELL:WUSignal:PAGing:DISable <Disable>
Disables or enables the paging associated with a WUS transmission.
Parameters:
<Disable> OFF | ON
*RST: OFF
Manual operation: See "Disable Paging" on page 68
2.5.11.6 Early Data Transmission Settings
The following commands configure early data transmission during random acess pro-
cedure.
User Manual 1178.5689.02 ─ 12 183

Command Reference
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:CPEDt....................................................... 184
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:TBS:VALue................................................ 184
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:UPEDt....................................................... 184
CONFigure:NIOT:SIGN:CELL:EDT:SMALl:ENABle:TBS................................................ 184
CONFigure:NIOT:SIGN:CELL:EDT:SMALl:ENABle:TBS:SUBSet.................................... 185
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:CPEDt <enable>
Enables or disables EDT in control plan (CP) CIoT EPS optimized mode.
Parameters:
<enable> OFF | ON
Manual operation: See "CP-EDT Enable / UP-EDT Enable" on page 69
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:TBS:VALue <enable>
Sets the No. of resource units for by early data transmission.
Parameters:
<enable> B328 | B408 | B504 | B584 | B680 | B808 | B936 | B1000
Transport block size (TBS) in No. of RUs.
*RST: B328
Manual operation: See "TBS" on page 71
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:UPEDt <enable>
Enables or disables EDT in user plan (UP) CIoT EPS optimized mode.
Parameters:
<enable> OFF | ON
Manual operation: See "CP-EDT Enable / UP-EDT Enable" on page 69
CONFigure:NIOT:SIGN:CELL:EDT:SMALl:ENABle:TBS <enable>
Enables or disables small TBS for EDT.
Parameters:
<enable> OFF | ON
*RST: OFF
User Manual 1178.5689.02 ─ 12 184

Command Reference

Manual operation: See "EDT Small TBS Enabled" on page 70
CONFigure:NIOT:SIGN:CELL:EDT:SMALl:ENABle:TBS:SUBSet <enable>
Enables or disables the small TBS subset for EDT.
Parameters:
<enable> OFF | ON
*RST: OFF
Manual operation: See "EDT Small TBS Subset Enable" on page 70
2.5.12 Network Settings
The commands in this section configure parameters of the simulated radio network.
● Neighbor Cell Settings.......................................................................................... 185
● Reselection Settings............................................................................................. 186
● Identity Settings.....................................................................................................188
● Security Settings................................................................................................... 190
● UE Identity.............................................................................................................192
● Timer Settings....................................................................................................... 192
● Time Settings........................................................................................................ 194
● Synchronization Settings.......................................................................................198
2.5.12.1 Neighbor Cell Settings
The following command defines neighbor cell information to be broadcast to the UE.
CONFigure:NIOT:SIGN:NCELl:NIOT:CELL<n> <Enable>, <Band>, <Channel>,

<CellID>, <QOffset>
Configures the entry number <n> of the NB-IoT neighbor cell list.
For channel number ranges depending on operating bands see Chapter 2.2.11, "Oper-
ating Bands", on page 27.
Note that only 5 entries with different channel numbers can be active at a time. Entries
with the same channel number must have different cell IDs.
Suffix: .
<n> 1..16
User Manual 1178.5689.02 ─ 12 185

Command Reference
Parameters:
<Enable> OFF | ON
Enables or disables the entry
*RST: OFF
OB74 | OB85
Standardized operating band
*RST: OB1
<Channel> integer
Downlink channel number
<CellID> integer
Physical layer cell ID
Range: 0 to 503
*RST: 0
<QOffset> N24 | N22 | N20 | N18 | N16 | N14 | N12 | N10 | N8 | N6 | N5 |
N4 | N3 | N2 | N1 | ZERO | P1 | P2 | P3 | P4 | P5 | P6 | P8 | P10 |
P12 | P14 | P16 | P18 | P20 | P22 | P24
Corresponds to value "q-OffsetCell" in 3GPP TS 36.331
N24 to N1: -24 dB to -1 dB
ZERO: 0 dB
P1 to P24: 1 dB to 24 dB
*RST: ZERO
Manual operation: See "NB-IoT" on page 72
2.5.12.2 Reselection Settings
The following commands define cell reselection information to be broadcast to the UE.
CONFigure:NIOT:SIGN:CELL:RESelection:QUALity......................................................186
CONFigure:NIOT:SIGN:CELL:RESelection:SEARch:INTRasearch................................. 187
CONFigure:NIOT:SIGN:CELL:RESelection:SEARch:NINTrasearch................................ 187
CONFigure:NIOT:SIGN:CELL:RESelection:TIME.......................................................... 188
CONFigure:NIOT:SIGN:CELL:RESelection:QUALity <Qqualmin>, <Qrxlevmin>,

<Qhyst>
Defines the power levels required for cell reselection. They are transmitted to the UE in
the system information.
User Manual 1178.5689.02 ─ 12 186

Command Reference
Parameters:
<Qqualmin> numeric | ON | OFF
Minimum required quality level in the reselection target cell.
Range: -34 dB to -3 dB
*RST: OFF
Additional parameters: OFF | ON (disables | enables transmis-
sion of the information element)
<Qrxlevmin> numeric
Minimum required RX level at a UE antenna for reselection to
the target cell
Increment: 2 dBm
*RST: -140 dBm
<Qhyst> numeric
Hysteresis
Increment: 1 dB, 2 dB for hysteresis values 6 dB to 24dB
*RST: 0 dB
Example: See Configuring Neighbor Cells and Reselection
Manual operation: See "Q qualmin" on page 73
CONFigure:NIOT:SIGN:CELL:RESelection:SEARch:INTRasearch
<Sintrasearch>
Defines the threshold SIntraSearch. The value divided by 2 is broadcast to the UE in SIB3.
Parameters:
<Sintrasearch> numeric
Increment: 2 dB
*RST: 62 dB
Default unit: dB
Manual operation: See "S IntraSearch" on page 73
CONFigure:NIOT:SIGN:CELL:RESelection:SEARch:NINTrasearch
<Snonintrasearch>
Defines the threshold SnonIntraSearch. The value divided by 2 is broadcast to the UE in
SIB3.
User Manual 1178.5689.02 ─ 12 187

Command Reference
Parameters:
<Snonintrasearch> numeric
Increment: 2 dB
*RST: 62 dB
Manual operation: See "S NonIntraSearch" on page 73
CONFigure:NIOT:SIGN:CELL:RESelection:TIME <Treselections>
Sets the time hysteresis for the cell reselection algorithm.
Parameters:
<Treselections> numeric
Range: 0 s to 21 s
Increment: 3s
*RST: 0s
Default unit: s
Manual operation: See "T Reselection" on page 74
2.5.12.3 Identity Settings
The following commands configure identities of the simulated radio network.

CONFigure:NIOT:SIGN:CELL:MCC............................................................................. 188
CONFigure:NIOT:SIGN:CELL:MNC:DIGits................................................................... 189
CONFigure:NIOT:SIGN:CELL:MNC............................................................................. 189
CONFigure:NIOT:SIGN:CELL:TAC.............................................................................. 189
CONFigure:NIOT:SIGN:CELL:CID:EUTRan................................................................. 189
CONFigure:NIOT:SIGN:CELL:MCC <MCC>
Specifies the three-digit mobile country code (MCC). You can omit leading zeros.
Parameters:
<MCC> decimal
Range: 0 to 999
*RST: 1
Example: See Configuring Network Settings
Manual operation: See "MCC" on page 74
User Manual 1178.5689.02 ─ 12 188

Command Reference
CONFigure:NIOT:SIGN:CELL:MNC:DIGits <NoDigits>
Specifies the number of digits of the mobile network code (MNC).
For setting the MNC, see CONFigure:NIOT:SIGN:CELL:MNC.
Parameters:
<NoDigits> TWO | THRee
*RST: TWO
Manual operation: See "MNC" on page 74
CONFigure:NIOT:SIGN:CELL:MNC <MNC>
Specifies the mobile network code (MNC). You can omit leading zeros.
A two or three-digit MNC can be set, see CONFigure:NIOT:SIGN:CELL:MNC:
DIGits.
Parameters:
<MNC> decimal
Range: 0 to 99 or 999
*RST: 1
Manual operation: See "MNC" on page 74
CONFigure:NIOT:SIGN:CELL:TAC <TAC>
Specifies the tracking area code.
Parameters:
<TAC> decimal
Range: 0 to 65535
*RST: 1
Manual operation: See "TAC" on page 74
CONFigure:NIOT:SIGN:CELL:CID:EUTRan <CID>
Specifies the E-UTRAN cell identifier (28-digit binary number).
User Manual 1178.5689.02 ─ 12 189

Command Reference
Parameters:
<CID> binary
Range: #B0 to #B1111111111111111111111111111
*RST: #B100000000
Manual operation: See "E-UTRAN Cell Identifier" on page 75
2.5.12.4 Security Settings
The following commands configure parameters for the authentication procedure and
for integrity protection.
CONFigure:NIOT:SIGN:CELL:SECurity:AUTHenticat.................................................... 190
CONFigure:NIOT:SIGN:CELL:SECurity:SECurity.......................................................... 190
CONFigure:NIOT:SIGN:CELL:SECurity:IALGorithm...................................................... 190
CONFigure:NIOT:SIGN:CELL:SECurity:SKEY.............................................................. 191
CONFigure:NIOT:SIGN:CELL:SECurity:MILenage........................................................ 191
CONFigure:NIOT:SIGN:CELL:SECurity:OPC................................................................191
CONFigure:NIOT:SIGN:CELL:SECurity:AUTHenticat <Enable>
Enables or disables authentication, to be performed during the attach procedure.
Parameters:
<Enable> OFF | ON
*RST: ON
Manual operation: See "Authentication" on page 75
CONFigure:NIOT:SIGN:CELL:SECurity:SECurity <Enable>
Enables or disables security (integrity protection).
Parameters:
<Enable> OFF | ON
*RST: ON
Manual operation: See "Security" on page 75
CONFigure:NIOT:SIGN:CELL:SECurity:IALGorithm <Algorithm>
Selects an algorithm for integrity protection.
User Manual 1178.5689.02 ─ 12 190

Command Reference
Parameters:
<Algorithm> NULL | S3G | AES
NULL: no integrity protection
S3G: SNOW3G (EIA1) algorithm
AES: AES (EIA2) algorithm
*RST: S3G
Manual operation: See "Integrity Algorithm" on page 75
CONFigure:NIOT:SIGN:CELL:SECurity:SKEY <SecretKey>
Defines the secret key K as 32-digit hexadecimal number. You can omit leading zeros.
K is used for the authentication procedure including a possible integrity check.
Parameters:
<SecretKey> hex
Range: #H0 to
#HFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
*RST: #H000102030405060708090A0B0C0D0E0F
Manual operation: See "Secret Key" on page 76
CONFigure:NIOT:SIGN:CELL:SECurity:MILenage <Enable>
Enables or disables using the MILENAGE algorithm set instead of the standard algo-
rithms.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Milenage" on page 76
CONFigure:NIOT:SIGN:CELL:SECurity:OPC <OPC>
Specifies the key OPc as 32-digit hexadecimal number.
User Manual 1178.5689.02 ─ 12 191

Command Reference
Parameters:
<OPC> hex
Range: #H00000000000000000000000000000000 to
#HFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
*RST: #H00000000000000000000000000000000
Manual operation: See "OPc" on page 76
2.5.12.5 UE Identity
The following command configures the default IMSI.
CONFigure:NIOT:SIGN:CELL:UEIDentity:IMSI <Value>
Specifies the default IMSI.
Parameters:
<Value> string
String value, containing 14 to 16 digits.
*RST: '001010123456063'
Manual operation: See "Default IMSI" on page 76
2.5.12.6 Timer Settings
The commands in this section configure timers.

CONFigure:NIOT:SIGN:CELL:TOUT:OOSYnc.............................................................. 192
CONFigure:NIOT:SIGN:CELL:TOUT:T3324..................................................................193
CONFigure:NIOT:SIGN:CELL:TOUT:T3412..................................................................193
CONFigure:NIOT:SIGN:CELL:TOUT:TEXT...................................................................194
CONFigure:NIOT:SIGN:CELL:TOUT:OOSYnc <value>
Specifies the time after which the instrument, having waited for a signal from the con-
nected UE, releases the connection.
Parameters:
<value> numeric
Range: 1 s to 180 s
*RST: 5s
Default unit: s
Firmware/Software: V3.7.30, V3.8.30: range increased
Manual operation: See "Out of Sync" on page 77
User Manual 1178.5689.02 ─ 12 192

Command Reference
CONFigure:NIOT:SIGN:CELL:TOUT:T3324 <Value>
Configures timer T3324, that means the idle time before PSM, see also CONFigure:
NIOT:SIGN:CONNection:PSMallowed.
The information element supports the values 1 to 31 combined with the units 2 sec-
onds, 1 minute and 6 minutes.
This command configures the timer value in seconds. So there are three subranges
with different increments.
Parameters:
<Value> numeric | ON | OFF
The parameter configures a checkbox (ON | OFF) or a timer
value.
ON
A PSM request is answered with the configured timer value.
Setting a timer value sets also ON.
OFF
The configured timer value is ignored and the user-requested
value is returned to the UE after a PSM request.
Range: 2 s to 11160 s
Increment: 2 s (2 s to 62 s), 60 s (120 s to 1860 s), 360 s (2160
s to 11160 s)
*RST: OFF (2 s)
Manual operation: See "T3324" on page 77
CONFigure:NIOT:SIGN:CELL:TOUT:T3412 <Value>
Configures timer T3412 for periodic tracking area updates.
The information element supports the values 1 to 31 combined with the units 2 sec-
onds, 1 minute and 6 minutes.
This command configures the timer value in seconds. So there are three subranges
with different increments.
Parameters:
<Value> numeric | ON | OFF
The parameter configures a checkbox (ON | OFF) or a timer
value.
ON
Enables the timer and transmission of the timer value.
Setting a timer value sets also ON.
OFF
Disables the timer and transmission of the timer value.
Range: 2 s to 11160 s
User Manual 1178.5689.02 ─ 12 193

Command Reference
Increment: 2 s (2 s to 62 s), 60 s (120 s to 1860 s), 360 s (2160

s to 11160 s)
*RST: OFF (2 s)
Manual operation: See "T3412" on page 77
CONFigure:NIOT:SIGN:CELL:TOUT:TEXT <value>
Configures an extended value for timer T3412.
The information element supports the values 1 to 31 combined with the units 2 s, 30 s,
1 min, 10 min, 1 h, 10 h and 320 h.
This command configures the timer value in seconds. So there are subranges with dif-
ferent increments.
Parameters:
<value> numeric | ON | OFF
Range: 2 s to 35712000 s
Increment: see table
*RST: OFF (2 s)
Additional parameters: OFF | ON (disables | enables the timer)
Manual operation: See "T3412 Extended" on page 77
Range Increment Remark
2 s to 62 s 2s
90 s to 930 s 30 s 900 s = 15 min
960 s to 1860 s 60 s 1800 s = 30 min
2400 s to 18600 s 600 s 18000 s = 5 h
21600 s to 111600 s 3600 s 111600 s = 1 d, 7 h
144000 s to 1116000 s 36000 s 1116000 s = 12 d, 22 h
1152000 s to 35712000 s 1152000 s 35712000 s = 413 d, 8 h
2.5.12.7 Time Settings
The commands in this section configure and send date and time information to the UE.
CONFigure:NIOT:SIGN:CELL:TIME:DSTime................................................................ 195
CONFigure:NIOT:SIGN:CELL:TIME:LTZoffset.............................................................. 195
CONFigure:NIOT:SIGN:CELL:TIME:SATTach...............................................................195
CONFigure:NIOT:SIGN:CELL:TIME:SNOW..................................................................196
User Manual 1178.5689.02 ─ 12 194

Command Reference
CONFigure:NIOT:SIGN:CELL:TIME:TDATe.................................................................. 196
CONFigure:NIOT:SIGN:CELL:TIME:TTME................................................................... 196
CONFigure:NIOT:SIGN:CELL:TIME:TTSRc..................................................................197
CONFigure:NIOT:SIGN:CELL:TIME:SNName...............................................................197
CONFigure:NIOT:SIGN:CELL:TIME:DSTime <Enable>
Specifies a daylight saving time (DST) offset for the time source DATE (see
CONFigure:NIOT:SIGN:CELL:TIME:TTSRc on page 197)
Parameters:
<Enable> P1H | P2H
P1H: +1h offset if DST is ON
P2H: +2h offset if DST is ON
*RST: OFF (P1H)
Additional parameters: OFF | ON (disables | enables DST)
Manual operation: See "Daylight Saving Time" on page 78
CONFigure:NIOT:SIGN:CELL:TIME:LTZoffset <TimeZoneOffset>
Specifies the time zone offset for the time source DATE (see CONFigure:NIOT:
SIGN:CELL:TIME:TTSRc on page 197).
Parameters:
<TimeZoneOffset> numeric
Range: -19.75 h to 19.75 h
Increment: 0.25 h
*RST: 0h
Default unit: h
Manual operation: See "Local Time Zone Offset" on page 78
CONFigure:NIOT:SIGN:CELL:TIME:SATTach <Enable>
Specifies whether the date and time information is sent to the UE during the attach pro-
cedure or not.
Parameters:
<Enable> OFF | ON
ON: send date and time at attach
OFF: do not send date and time at attach
*RST: OFF
User Manual 1178.5689.02 ─ 12 195

Command Reference

Manual operation: See "Send Time" on page 79
CONFigure:NIOT:SIGN:CELL:TIME:SNOW
Triggers the transfer of the date and time information to the UE.
Usage: Event
Manual operation: See "Send Time" on page 79
CONFigure:NIOT:SIGN:CELL:TIME:TDATe <Day>, <Month>, <Year>

Specifies the UTC date for the time source DATE (see CONFigure:NIOT:SIGN:
CELL:TIME:TTSRc on page 197)
Parameters:
<Day> integer
Range: 1 to 31
*RST: 11
<Month> integer
Range: 1 to 12
*RST: 11
<Year> integer
Range: 2011 to 2099
*RST: 2011
Manual operation: See "Date / Time (UTC)" on page 78
CONFigure:NIOT:SIGN:CELL:TIME:TTME <Hour>, <Minute>, <Second>

Specifies the UTC time for the time source DATE (see CONFigure:NIOT:SIGN:
CELL:TIME:TTSRc on page 197)
Parameters:
<Hour> integer
Range: 0 to 23
*RST: 11
User Manual 1178.5689.02 ─ 12 196

Command Reference
<Minute> integer
Range: 0 to 59
*RST: 11
<Second> integer
Range: 0 to 59
*RST: 0
Manual operation: See "Date / Time (UTC)" on page 78
CONFigure:NIOT:SIGN:CELL:TIME:TTSRc <SourceTime>
Selects the date and time source.
The time source DATE is configured via the following commands:
● CONFigure:NIOT:SIGN:CELL:TIME:TDATe
● CONFigure:NIOT:SIGN:CELL:TIME:TTME
● CONFigure:NIOT:SIGN:CELL:TIME:DSTime
● CONFigure:NIOT:SIGN:CELL:TIME:LTZoffset
Parameters:
<SourceTime> CMWTime | DATE
CMWTime: Windows date and time
DATE: Date and time specified via remote commands
*RST: CMWT
Manual operation: See "Time Source" on page 78
CONFigure:NIOT:SIGN:CELL:TIME:SNName <SendNetName>
If enabled, sends the full and short network name within date and time signaling to the
UE.
Parameters:
<SendNetName> OFF | ON
*RST: ON
Manual operation: See "Send Network Name" on page 79
User Manual 1178.5689.02 ─ 12 197

Command Reference
2.5.12.8 Synchronization Settings
The commands in this section configure the synchronization to other signaling applica-
tions.
CONFigure:NIOT:SIGN:CELL:SYNC:ZONE................................................................. 198
CONFigure:NIOT:SIGN:CELL:SYNC:OFFSet............................................................... 198
CONFigure:NIOT:SIGN:CELL:SYNC:ZONE <Zone>
Selects the synchronization zone for the signaling application.
Parameters:
<Zone> NONE | Z1
NONE: no synchronization
Z1: synchronization to zone 1
*RST: Z1
Firmware/Software: V3.7.20, V3.7.30 changed *RST
Manual operation: See "Synchronization Zone" on page 79
CONFigure:NIOT:SIGN:CELL:SYNC:OFFSet <Offset>
Configures the timing offset relative to the time zone.
Parameters:
<Offset> numeric
*RST: 0s
Default unit: s
Manual operation: See "Synchronization Offset" on page 79
2.5.13 Connection Configuration
The commands in this section define parameters for the supported scheduling types.
● General Connection Settings................................................................................ 199
● Timers and Counters Settings...............................................................................204
● Data Application Settings......................................................................................205
● UL RMC Settings.................................................................................................. 207
● DL RMC Settings.................................................................................................. 209
● User-Defined Scheduling Settings........................................................................ 210
● HARQ Settings......................................................................................................214
● NPDCCH Settings.................................................................................................215
● Non-Anchor Configuration Rel.13......................................................................... 218
User Manual 1178.5689.02 ─ 12 198

Command Reference
● Non-Anchor configuration Rel.14 - Paging............................................................222

● Non-Anchor configuration Rel.14 - RACH.............................................................231
● Discontinuous Reception Settings........................................................................ 233
● Scheduling Request Settings................................................................................237
2.5.13.1 General Connection Settings
The following commands define general connection parameters.

CONFigure:NIOT:SIGN:CONNection:BMPC................................................................. 199
CONFigure:NIOT:SIGN:CONNection:CTYPe................................................................199
CONFigure:NIOT:SIGN:CONNection:DIT:ENABle......................................................... 200
CONFigure:NIOT:SIGN:CONNection:DIT:TIMer............................................................ 200
CONFigure:NIOT:SIGN:CONNection:DPCYcle............................................................. 200
CONFigure:NIOT:SIGN:CONNection:INTRandom.........................................................201
CONFigure:NIOT:SIGN:CONNection:PCNB................................................................. 201
CONFigure:NIOT:SIGN:CONNection:PSMallowed........................................................ 201
CONFigure:NIOT:SIGN:CONNection:RAI:ENABle.........................................................202
CONFigure:NIOT:SIGN:CONNection:RRC:KEEP..........................................................202
CONFigure:NIOT:SIGN:CONNection:RRC:RELCause...................................................202
CONFigure:NIOT:SIGN:CONNection:RRC:TIMer.......................................................... 202
CONFigure:NIOT:SIGN:CONNection:RRCPasitrans......................................................203
CONFigure:NIOT:SIGN:CONNection:STYPe................................................................ 203
CONFigure:NIOT:SIGN:CONNection:TMODe............................................................... 203
CONFigure:NIOT:SIGN:CONNection:TMODe:IPVersion................................................ 204
CONFigure:NIOT:SIGN:CONNection:UECRequest....................................................... 204
CONFigure:NIOT:SIGN:CONNection:BMPC <Coefficient>
Configures the field "modificationPeriodCoeff" in the "BCCH-Config-NB" in system
information block 2.
Parameters:
<Coefficient> C16 | C32 | C64 | C128
*RST: C32
Example: See Configuring General Connection Settings
Manual operation: See "BCCH Mod. Period Coeff." on page 98
CONFigure:NIOT:SIGN:CONNection:CTYPe <Type>
Selects the connection type to be applied.
User Manual 1178.5689.02 ─ 12 199

Command Reference
Parameters:
<Type> TESTmode | DAPPlication
TESTmode: for signaling tests not involving the DAU
DAPPlication: for data application measurements using the
DAU
*RST: TEST
Options: For DAPPlication: installed DAU
Manual operation: See "Connection Type" on page 81
CONFigure:NIOT:SIGN:CONNection:DIT:ENABle <ENable>
Enables/disables the data inactivity timer.
Parameters:
<ENable> OFF | ON
*RST: OFF
Manual operation: See "Data Inactivity Timer" on page 83
CONFigure:NIOT:SIGN:CONNection:DIT:TIMer <Timer>
Specifies the data inactivity timer.
Parameters:
<Timer> numeric | 1 | 2 | 3 | 5 | 7 | 10 | 15 | 20 | 40 | 50 | 60 | 80 | 100 |
120 | 150 | 180
*RST: 1
Default unit: s
Manual operation: See "Data Inactivity Timer" on page 83
CONFigure:NIOT:SIGN:CONNection:DPCYcle <Cycle>
Selects the cell-specific default paging cycle.
Parameters:
<Cycle> P128 | P256 | P512 | P1K
128, 256, 512 or 1024 radio frames
*RST: P128
User Manual 1178.5689.02 ─ 12 200

Command Reference

Manual operation: See "Default Paging Cycle" on page 98
CONFigure:NIOT:SIGN:CONNection:INTRandom <Enable>
Enables / disables interference randomization.
Parameters:
<Enable> OFF | ON
*RST: OFF
Example: See Configuring General Connection Settings.
Manual operation: See "Interference Randomization" on page 99
CONFigure:NIOT:SIGN:CONNection:PCNB <Value>
Configures the field "nB" in the "PCCH-Config-NB" in system information block 2.
Parameters:
<Value> N4T | N2T | NT | NT2 | NT4 | NT8 | NT16 | NT32 | NT64 |
NT128 | NT256 | NT512 | NT1K
4T, 2T, T, T/2, T/4, T/8, T/16, T/32, T/64, T/128, T/256, T/512, T/
1024
*RST: NT
Manual operation: See "PCCH-Config nB" on page 98
CONFigure:NIOT:SIGN:CONNection:PSMallowed <Allowed>
Specifies whether a UE request for power-saving mode (PSM) is accepted or rejected.
If you want to accept PSM requests, configure also timer T3324, see CONFigure:
NIOT:SIGN:CELL:TOUT:T3324 on page 193.
Parameters:
<Allowed> OFF | ON
*RST: OFF
Manual operation: See "PSM Allowed" on page 98
User Manual 1178.5689.02 ─ 12 201

Command Reference
CONFigure:NIOT:SIGN:CONNection:RAI:ENABle <Enable>
Enables / disables information element (IE) release assistance indication.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Release Assistance Indication" on page 83
CONFigure:NIOT:SIGN:CONNection:RRC:KEEP <Enable>
Selects whether the RRC connection is kept or released after attach.
Parameters:
<Enable> OFF | ON
OFF: The RRC connection is released.
ON: The RRC connection is kept.
*RST: ON
Manual operation: See "Keep RRC Connection" on page 82
CONFigure:NIOT:SIGN:CONNection:RRC:RELCause <RRCRelCause>
Selects the behavior for the state transitions of an RRC connection.
Parameters:
<RRCRelCause> SUSPend | OTHer
SUSPend: suspend/resume used for state transitions
OTHer: connect/disconnect used for state transitions
Manual operation: See "Release Cause" on page 83
CONFigure:NIOT:SIGN:CONNection:RRC:TIMer <Timer>
Configures the inactivity timeout for disabled "Keep RRC Connection" (CONFigure:
NIOT:SIGN:CONNection:RRC:KEEPOFF).
User Manual 1178.5689.02 ─ 12 202

Command Reference
Parameters:
<Timer> numeric
Range: 1 s to 255 s
*RST: 5s
Default unit: s
Manual operation: See "Keep RRC Connection" on page 82
CONFigure:NIOT:SIGN:CONNection:RRCPasitrans <Enable>
Enables or disables RRC paging after SI transmission.
Parameters:
<Enable> OFF | ON
*RST: Disable
Manual operation: See "RRC Allow Paging After SI Transmission" on page 98
CONFigure:NIOT:SIGN:CONNection:STYPe <Type>
Selects the scheduling type.
Parameters:
<Type> ULRMc | DLRMc | UDEF
ULRMc: UL RMC
DLRMc: DL RMC
UDEF: user-defined scheduling
*RST: ULRM
Example: See Configuring UL RMCs
Manual operation: See "Scheduling Type" on page 83
CONFigure:NIOT:SIGN:CONNection:TMODe <Enable>
Specifies whether the UE is forced into a test mode. If enabled, the message "ACTI-
VATE TEST MODE" is sent to the UE.
Parameters:
<Enable> OFF | ON
*RST: ON
User Manual 1178.5689.02 ─ 12 203

Command Reference
Manual operation: See "Use "Activate Testmode" Message" on page 81
CONFigure:NIOT:SIGN:CONNection:TMODe:IPVersion <IPversion>
Specifies which IP versions are allowed in test mode.
Parameters:
<IPversion> IPV4 | IPV46
IPv4 only, IPv4/IPv6
*RST: IPV4
Manual operation: See "IP Version" on page 81
CONFigure:NIOT:SIGN:CONNection:UECRequest <value>
Selects, whether the R&S CMW performs the UE capabilities inquiry repeatedly or
once only.
Parameters:
<value> REPeated | ONE
*RST: REP
Manual operation: See "UE Capabilities Request" on page 99
2.5.13.2 Timers and Counters Settings
The following commands configure general counters and timers used for connection
estnblishment.
CONFigure:NIOT:SIGN:CONNection:TIMer:NTELeven..................................................204
CONFigure:NIOT:SIGN:CONNection:TIMer:NTTen....................................................... 205
CONFigure:NIOT:SIGN:CONNection:TIMer:TTTen........................................................205
CONFigure:NIOT:SIGN:CONNection:TIMer:NTELeven <Timer>
Sets the number of consecutive in-sync indications (N311) signaled from lower layers
that stops the timer T310, see:
User Manual 1178.5689.02 ─ 12 204

Command Reference
Parameters:
<Timer> T1 | T2 | T3 | T4 | T5 | T6 | T8 | T10
Value of N311 as threshold
*RST: T1
Manual operation: See "T310, N310, N311" on page 103
CONFigure:NIOT:SIGN:CONNection:TIMer:NTTen <Timer>
Sets the number of consecutive out-of-sync indications (N310) signaled from lower lay-
ers thet triggers the timer T310, see:
Parameters:
<Timer> T1 | T2 | T3 | T4 | T6 | T8 | T10 | T20
Value of N310 as threshold
*RST: T2
CONFigure:NIOT:SIGN:CONNection:TIMer:TTTen <Timer>
Sets the expiry of the timer T310 in ms.
The timer is triggered when counter N310 (consecutive out-of-sync indications) is
reached.
The timer is stopped when counter N311 (consecutive in-sync indications) is reached.
Parameters:
<Timer> MS0 | MS02 | MS05 | MS10 | MS20 | MS40 | MS80
*RST: MS10
2.5.13.3 Data Application Settings
The following commands configure data application connections.
User Manual 1178.5689.02 ─ 12 205

Command Reference
CONFigure:NIOT:SIGN:CONNection:DAPPlication:CIOT...............................................206
CONFigure:NIOT:SIGN:CONNection:DAPPlication:IPVersion.........................................206
CONFigure:NIOT:SIGN:CONNection:DSERver:IPVFaddress......................................... 206
CONFigure:NIOT:SIGN:CONNection:DSERver:PORT................................................... 207
CONFigure:NIOT:SIGN:CONNection:DAPPlication:CIOT <Plane>
Selects the C-IoT optimization type to be used for the attach in data application mode.
Parameters:
<Plane> CPL | UPL
Control plane or user plane C-IoT optimization
*RST: CPL
Manual operation: See "C-IoT Optimization" on page 82
CONFigure:NIOT:SIGN:CONNection:DAPPlication:IPVersion <IPversion>
Specifies whether the IP connection or non-IP data delivery (NIDD) is used in data
application mode.
For IP connections, also the allowed IP versions are selected.
Parameters:
<IPversion> IPV4 | IPV6 | IPV46 | NIP
IPv4 only, IPv6 only, IPv4/IPv6, non-IP
*RST: IPV46
Firmware/Software: V3.7.30, V3.7.70: added NIP
Manual operation: See "IP Version" on page 82
CONFigure:NIOT:SIGN:CONNection:DSERver:IPVFaddress <address>
Specifies the destination server IP address (IPv4) for non-IP data delivery.
Parameters:
<Address> string
IP address as string
*RST: 192.168.168.2
Example: CONF:NIOT:SIGN:CONN:DSER:IPVF '192.168.168.2'
See Configuring General Connection Settings.
Manual operation: See "Destination Server" on page 82
User Manual 1178.5689.02 ─ 12 206

Command Reference
CONFigure:NIOT:SIGN:CONNection:DSERver:PORT <port>
Specifies the destination UDP port for non-IP data delivery.
Parameters:
<port> numeric
Range: 1 to 65.535E+3
*RST: 4366
Manual operation: See "Destination Server" on page 82
2.5.13.4 UL RMC Settings
The following commands define parameters for the scheduling type "UL RMC".
CONFigure:NIOT:SIGN:CONNection:RMC:UL..............................................................207
CONFigure:NIOT:SIGN:CONNection:RMC:UL:MCSindex?............................................ 208
CONFigure:NIOT:SIGN:CONNection:RMC:FORMat?.................................................... 208
CONFigure:NIOT:SIGN:CONNection:RMC:UL <Subcarriers>, <StartSubcarrier>,

<MCSindex>, <ResourceUnits>, <Repetitions>
Configures an uplink reference measurement channel (UL RMC) for NPUSCH format
1.
Only certain value combinations are accepted, see Chapter 2.2.8, "Scheduling Type
UL RMC", on page 23.
Parameters:
<Subcarriers> SC1 | SC3 | SC6 | SC12
Number of subcarriers
*RST: SC1
<StartSubcarrier> numeric
Start subcarrier
Range: 0 to 47
*RST: 0
<MCSindex> MI0 | MI3 | MI5
MCS index value
*RST: MI0
<ResourceUnits> NRU01 | NRU02
Number of resource units
*RST: NRU02
User Manual 1178.5689.02 ─ 12 207

Command Reference
<Repetitions> NR1
Number of NPUSCH repetitions
*RST: NR1
Manual operation: See "Subcarriers, Start Subcarrier" on page 84
CONFigure:NIOT:SIGN:CONNection:RMC:UL:MCSindex?
Queries the configured MCS index and the resulting modulation scheme and transport
block size for the scheduling type UL RMC for NPUSCH format 1, see Chapter 2.2.8,
"Scheduling Type UL RMC", on page 23.
Return values:
<MCSindex> MI0 | MI3 | MI5
MCS index value
<Modulation> QPSK
Modulation scheme
<TransBlockSize> decimal
Transport block size
Usage: Query only
Manual operation: See "MCS Index" on page 84
CONFigure:NIOT:SIGN:CONNection:RMC:FORMat?
Queries scheduling parameters for a UL RMC for NPUSCH format 2. These settings
are not configurable.
Return values:
<Subcarriers> SC1
<StartSubcarrier> decimal
Range: 0 to 45
<Modulation> BPSK
<ResourceUnits> NRU01
<Repetitions> NR1 | NR2 | NR4 | NR8 | NR16 | NR32 | NR64 | NR128
Usage: Query only
User Manual 1178.5689.02 ─ 12 208

Command Reference
Manual operation: See "Resource Allocation" on page 312
2.5.13.5 DL RMC Settings
The following commands define parameters for the scheduling type "DL RMC".
CONFigure:NIOT:SIGN:CONNection:RMC:DL..............................................................209
CONFigure:NIOT:SIGN:CONNection:RMC:DL:MCSindex?............................................ 210
CONFigure:NIOT:SIGN:CONNection:RMC:DL <Subcarriers>, <StartSubcarrier>,

<MCSindex>, <Subframes>, <Repetitions>
Configures a downlink reference measurement channel (DL RMC). Only certain value
combinations are accepted, see Chapter 2.2.9, "Scheduling Type DL RMC",
on page 24.
Parameters:
<Subcarriers> SC12 | KEEP
Number of subcarriers (only in the query form of the command)
This parameter is not editable, for the setting, use value "KEEP".
*RST: SC12
<StartSubcarrier> 0 | KEEP
Start subcarrier (only in the query form of the command)
*RST: 0
<MCSindex> MI6
MCS index value
*RST: MI6
<Subframes> NSF01
Number of subframes
*RST: NSF01
<Repetitions> NR1
Number of NPDSCH repetitions
*RST: NR1
Example: See Configuring DL RMCs
User Manual 1178.5689.02 ─ 12 209

Command Reference
CONFigure:NIOT:SIGN:CONNection:RMC:DL:MCSindex?
block size for the scheduling type DL RMC, see Chapter 2.2.9, "Scheduling Type DL
RMC", on page 24.
Return values:
<MCSindex> MI6
MCS index value
<Modulation> QPSK
Modulation scheme
Example: See Configuring DL RMCs
Usage: Query only
2.5.13.6 User-Defined Scheduling Settings
The following commands define parameters for the scheduling type "User defined".
CONFigure:NIOT:SIGN:CONNection:UDEFined:UDPattern........................................... 210
CONFigure:NIOT:SIGN:CONNection:UDEFined:DL[:SET<setNr>].................................. 211
CONFigure:NIOT:SIGN:CONNection:UDEFined:UL[:SET<setNr>]..................................212
CONFigure:NIOT:SIGN:CONNection:UDEFined:DL:MCSindex?.....................................212
CONFigure:NIOT:SIGN:CONNection:UDEFined:UL:MCSindex?.....................................213
CONFigure:NIOT:SIGN:CONNection:UDEFined:FORMat?............................................ 213
CONFigure:NIOT:SIGN:CONNection:UDEFined:UDPattern <Pattern>
Selects the pattern of grants sent to the UE.
Parameters:
<Pattern> DL | UL | DLUL | NOS | DL95
DL: continuous DL grants
UL: continuous UL grants
DLUL: alternating DL/UL grants
NOS: no scheduling / no grants
DL95: continuous DL 95 kbps
*RST: DLUL
Example: See Configuring User-Defined Channels
Firmware/Software: V3.7.20, V3.7.30 added NOS, DL95
Manual operation: See "Pattern" on page 86
User Manual 1178.5689.02 ─ 12 210

Command Reference
<Subcarriers>, <StartSubcarrier>, <MCSindex>, <Subframes>, <Repetitions>
Configures the downlink user-defined scheduling. Only certain value combinations are
accepted, see Chapter 2.2.10, "User-Defined Scheduling", on page 24.
Suffix: .
<setNr> 1
For future use
Parameters:
<Subcarriers> SC12 | KEEP
Number of subcarriers (only in the query form of the command)
*RST: SC12
<StartSubcarrier> 0 | KEEP
Start subcarrier (only in the query form of the command)
*RST: 0
<MCSindex> MI0 | MI1 | MI2 | MI3 | MI4 | MI5 | MI6 | MI7 | MI8 | MI9 | MI10 |
MI11 | MI12 | MI13
MCS index value
*RST: MI6
<Subframes> NSF01 | NSF02 | NSF03 | NSF04 | NSF05 | NSF06 | NSF08 |
NSF10
Number of subframes
*RST: NSF01
<Repetitions> NR1 | NR2 | NR4 | NR8 | NR16 | NR32 | NR64 | NR128 |
NR192 | NR256 | NR384 | NR512 | NR768 | NR1K | NR1536 |
NR2K
Number of NPDSCH repetitions: 1, 2, 4, ..., 512, 768, 1024,
1536, 2048
*RST: NR1
Firmware/Software: V3.7.20, V3.7.50: added <Repetitions> NR16, NR32, NR64,
NR128, NR192, NR256, NR384, NR512, NR768, NR1K,
NR1536, NR2K
V3.7.60: added <MCSindex> MI13
User Manual 1178.5689.02 ─ 12 211

Command Reference
<Subcarriers>, <StartSubcarrier>, <MCSindex>, <ResourceUnits>,
<Repetitions>
Configures the uplink user-defined scheduling for NPUSCH format 1.
Only certain value combinations are accepted, see Chapter 2.2.10, "User-Defined
Scheduling", on page 24.
Suffix: .
<setNr> 1
For future use
Parameters:
<Subcarriers> SC1 | SC3 | SC6 | SC12
*RST: SC1
<StartSubcarrier> numeric
Range: 0 to 47
*RST: 0
MI11 | MI12 | MI13
MCS index value
*RST: MI5
<ResourceUnits> NRU01 | NRU02 | NRU03 | NRU04 | NRU05 | NRU06 | NRU08 |
NRU10
*RST: NRU01
<Repetitions> NR1 | NR2 | NR4 | NR8 | NR16 | NR32 | NR64 | NR128
*RST: NR1
NR64, NR128
V3.7.60: added <MCSindex> MI13
CONFigure:NIOT:SIGN:CONNection:UDEFined:DL:MCSindex?
block size for DL user-defined scheduling, see Chapter 2.2.10, "User-Defined Schedul-
ing", on page 24.
User Manual 1178.5689.02 ─ 12 212

Command Reference
Return values:
MI11 | MI12 | MI13
MCS index value
<Modulation> QPSK
Modulation scheme
Usage: Query only
Firmware/Software: V3.7.20, V3.7.60: added <MCSindex> MI13
CONFigure:NIOT:SIGN:CONNection:UDEFined:UL:MCSindex?
block size for UL user-defined scheduling for NPUSCH format 1, see Chapter 2.2.10,
"User-Defined Scheduling", on page 24.
Return values:
MI11 | MI12 | MI13
MCS index value
<Modulation> QPSK
Modulation scheme
Usage: Query only
Firmware/Software: V3.7.20, V3.7.60: added <MCSindex> MI13
CONFigure:NIOT:SIGN:CONNection:UDEFined:FORMat?
Queries scheduling parameters for UL user-defined scheduling for NPUSCH format 2.
These settings are not configurable.
Return values:
<Subcarriers> SC1
User Manual 1178.5689.02 ─ 12 213

Command Reference
<StartSubcarrier> decimal
Range: 0 to 45
<Modulation> BPSK
<ResourceUnits> NRU01
<Repetitions> NR1 | NR2 | NR4 | NR8 | NR16 | NR32 | NR64 | NR128 |
NR192 | NR256 | NR384 | NR512 | NR768 | NR1K | NR1536 |
NR2K
Number of NPUSCH repetitions: 1, 2, 4, ..., 512, 768, 1024,
1536, 2048
Usage: Query only
NR512, NR768, NR1K, NR1536, NR2K
Manual operation: See "Resource Allocation" on page 312
2.5.13.7 HARQ Settings
The following commands configure HARQ connection settings.

CONFigure:NIOT:SIGN:CONNection:HARQen............................................................. 214
CONFigure:NIOT:SIGN:CONNection:MAXNumtr.......................................................... 214
CONFigure:NIOT:SIGN:CONNection:NUMHqpc........................................................... 215
CONFigure:NIOT:SIGN:CONNection:HARQen <HarqEnable>
Enables or disables HARQ for downlink transmissions.
Parameters:
<HarqEnable> OFF | ON
*RST: OFF
Example: See Configuring HARQ
Manual operation: See "HARQ" on page 88
CONFigure:NIOT:SIGN:CONNection:MAXNumtr <MaxNumTr>
Specifies the maximum number of transmissions, including initial transmissions and
retransmissions.
Parameters:
<MaxNumTr> decimal
Range: 2 to 4
*RST: 4
User Manual 1178.5689.02 ─ 12 214

Command Reference
Manual operation: See "Max. No. of Transmissions" on page 88
CONFigure:NIOT:SIGN:CONNection:NUMHqpc <NumHrqProc>
Specifies the number of HARQ processes.
Parameters:
<NumHrqProc> decimal
Range: 1 to 2
*RST: 1
Firmware/Software: V3.7.40, V3.7.60: range extended
Manual operation: See "No. of HARQ Processes" on page 88
2.5.13.8 NPDCCH Settings
The following commands configure narrowband physical downlink control channel

(NPDCCH).
CONFigure:NIOT:SIGN:CONNection:NPDCch:CSS:MAXNrep....................................... 215
CONFigure:NIOT:SIGN:CONNection:NPDCch:MXNRep................................................216
CONFigure:NIOT:SIGN:CONNection:NPDCch:NREP....................................................216
CONFigure:NIOT:SIGN:CONNection:NPDCch:NRRepr?............................................... 216
CONFigure:NIOT:SIGN:CONNection:NPDCch:OFFSt................................................... 217
CONFigure:NIOT:SIGN:CONNection:NPDCch:PERiod?................................................ 217
CONFigure:NIOT:SIGN:CONNection:NPDCch:SFOFfst?............................................... 217
CONFigure:NIOT:SIGN:CONNection:NPDCch:STSF.....................................................218
CONFigure:NIOT:SIGN:CONNection:NPDCch:CSS:MAXNrep <MNRep>
Specifies the maximum number of repetitions for NPDCCH transmissions with paging
(Rmax).
The Rmax value is signaled as npdcch-NumRepetitionPaging.
Parameters:
<MNRep> R1 | R2 | R4 | R8 | R16 | R32 | R64 | R128 | R256 | R512 |
R1024 | R2048
*RST: R8
Example: See Configuring NPDCCH
Manual operation: See "Max. No. Repetitions Rmax < Common Search Space -
Paging" on page 97
User Manual 1178.5689.02 ─ 12 215

Command Reference
CONFigure:NIOT:SIGN:CONNection:NPDCch:MXNRep <MxNrRep>
Specifies the maximum number of repetitions for NPDCCH transmissions for the UE.
Parameters:
<MxNrRep> 2^x, where x = {0 to 11}
*RST: 1
Manual operation: See "Max. No. Repetitions Rmax < UE Specific Search Space"
on page 96
CONFigure:NIOT:SIGN:CONNection:NPDCch:NREP <NrRep>
Specifies the number of repetitions for NPDCCH transmissions related to Rmax, see:
The number of NPDCCH repetitions equals to one of these values:
● Rmax
● Rmax / 2
● Rmax / 4
● Rmax / 8
Parameters:
<NrRep> RMAX | RMAX2 | RMAX4 | RMAX8
*RST: RMAX
Manual operation: See "No. Repetitions" on page 97
CONFigure:NIOT:SIGN:CONNection:NPDCch:NRRepr?
Queries the number of repetitions R for actual NPDCCH transmissions. The value
depends on the following settings:
CONFigure:NIOT:SIGN:CONNection:NPDCch:NREP
Return values:
<NrofRepR> 2^x, where x = {0 to 11}
Usage: Query only
User Manual 1178.5689.02 ─ 12 216

Command Reference
Manual operation: See "No. Repetitions" on page 97
CONFigure:NIOT:SIGN:CONNection:NPDCch:OFFSt <offst>
Specifies the NPDCCH offset related to Rmax, see:
Parameters:
<offst> decimal
Value x, offset is then calculated as x*1/8, i.e. {0, 1/8, 1/4, 3/8}
Range: 0 to 3
*RST: 2
Manual operation: See "Offset" on page 97
CONFigure:NIOT:SIGN:CONNection:NPDCch:PERiod?
Queries the periodicity T of NPDCCH transmissions. The value depends on the follow-
ing settings:
CONFigure:NIOT:SIGN:CONNection:NPDCch:STSF
Return values:
<PeriodT> decimal
Usage: Query only
Manual operation: See "Start SF" on page 97
CONFigure:NIOT:SIGN:CONNection:NPDCch:SFOFfst?
Queries the NPDCCH offset in subframes. The value depends on the following set-
tings:
CONFigure:NIOT:SIGN:CONNection:NPDCch:OFFSt
Return values:
<SFOffst> decimal
Range: 0 to 3072
Default unit: subframes
User Manual 1178.5689.02 ─ 12 217

Command Reference
Usage: Query only

Manual operation: See "Offset" on page 97
CONFigure:NIOT:SIGN:CONNection:NPDCch:STSF <startSF>
Specifies NPDCCH starting subframe.
Available values depend on Rmax setting, see
Parameters:
<startSF> decimal | 1 | 2 | 4 | 8 | 16 | 32 | 48 | 64
1: corresponds to starting subframe 1.5
2 to 64: the number of starting subframe
Default unit: subframe
Manual operation: See "Start SF" on page 97
2.5.13.9 Non-Anchor Configuration Rel.13
The following commands are related to non-anchor configuration for the transmission
of user data.
CONFigure:NIOT:SIGN:CONNection:NAC:CHANnel:DL................................................ 218
CONFigure:NIOT:SIGN:CONNection:NAC:CHANnel:UL................................................ 219
CONFigure:NIOT:SIGN:CONNection:NAC:DBMap........................................................219
CONFigure:NIOT:SIGN:CONNection:NAC:DGAP......................................................... 219
CONFigure:NIOT:SIGN:CONNection:NAC:ENABle....................................................... 220
CONFigure:NIOT:SIGN:CONNection:NAC:EXBitmap.................................................... 220
CONFigure:NIOT:SIGN:CONNection:NAC:GAPDc........................................................220
CONFigure:NIOT:SIGN:CONNection:NAC:GAPPeriod.................................................. 221
CONFigure:NIOT:SIGN:CONNection:NAC:GAPTh........................................................ 221
CONFigure:NIOT:SIGN:CONNection:NAC:NRSPo........................................................221
CONFigure:NIOT:SIGN:CONNection:NAC:CHANnel:DL <DLChannel>
Specifies the DL non-anchor channel for data transmission as DL frequency or channel
No.
Parameters:
<DLChannel> decimal
2110.0 MHz to 2169.9 MHz
Range: 0 Ch to 599 Ch
*RST: Ch
User Manual 1178.5689.02 ─ 12 218

Command Reference
Example: See Configuring Non-Anchor Parameters.

Manual operation: See "DL/ UL Frequency" on page 89
CONFigure:NIOT:SIGN:CONNection:NAC:CHANnel:UL <ULChannel>
Specifies the UL non-anchor channel as an uplink frequency or channel No.
Parameters:
<ULChannel> decimal
1920.0 MHz to 1979.9 MHz
*RST: 18320 Ch
Manual operation: See "DL/ UL Frequency" on page 89
CONFigure:NIOT:SIGN:CONNection:NAC:DBMap <BitMap>
Defines the bitmap to be used for the scheduling of DL channel carrying user data. If
an explicit non-anchor bitmap is used, the allowed DL subframes are specified via:
CONFigure:NIOT:SIGN:CONNection:NAC:EXBitmap
Parameters:
<BitMap> NOB | ANB | EXB
NOB: no bitmap
ANB: anchor bitmap
EXB: explicit non-anchor bitmap
*RST: NOB
Manual operation: See "Downlink Bitmap" on page 89
CONFigure:NIOT:SIGN:CONNection:NAC:DGAP <DGap>
Defines the transmission gap configuration to be applied for DL data transmission
scheduling for non-anchor carrier.
Parameters:
<DGap> NOG | ANG | EXG
NOG: no gap
ANG: anchor gap
EXG: explicit non-anchor gap
*RST: NOG
User Manual 1178.5689.02 ─ 12 219

Command Reference

Manual operation: See "Downlink Gap" on page 89
CONFigure:NIOT:SIGN:CONNection:NAC:ENABle <Enable>
Enables or disables DL non-anchor configuration.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Enable Non-Anchor Rel. 13" on page 89
CONFigure:NIOT:SIGN:CONNection:NAC:EXBitmap <ExBMap>
Specifies the allowed DL subframes for anchor or non-anchor data transmissions. The
anchor or non-anchor carrier is selected by:
CONFigure:NIOT:SIGN:CONNection:NAC:DBMap.
Parameters:
<ExBMap> binary
Explicit bitmap
Range: B#0 to B#1111111111
CONFigure:NIOT:SIGN:CONNection:NAC:GAPDc <GapDc>
Sets the gap duration coefficient (dl-GapDurationCoeff) for data transmission via
non-anchor carrier.
The duration of the transmission gap is calculated as:
(dl-GapPeriodicity)
See also CONFigure:NIOT:SIGN:CONNection:NAC:GAPPeriod.
Parameters:
<GapDc> numeric | 1 | 2 | 3 | 4
x: specifies the gap duration coefficient x/8: 1/8, 1/4, 3/8, or 1/2
*RST: 1
User Manual 1178.5689.02 ─ 12 220

Command Reference

Manual operation: See "Gap Duration Coefficient" on page 90
CONFigure:NIOT:SIGN:CONNection:NAC:GAPPeriod <Periodicity>
Selects the transmission gap cycle (64, 128, 256, or 512 subframes) for data transmis-
sion via non-anchor carrier.
Parameters:
<Periodicity> SF64 | SF128 | SF256 | SF512
Periodicity in subframes.
*RST: SF64
Manual operation: See "Gap Periodicity" on page 90
CONFigure:NIOT:SIGN:CONNection:NAC:GAPTh <GapTh>
for data transmission via non-anchor carrier before the DL transmission gap is applied.
Parameters:
<GapTh> N32 | N64 | N128 | N256
Number of NPDCCH repetitions
*RST: N32
Manual operation: See "Gap Threshold" on page 90
CONFigure:NIOT:SIGN:CONNection:NAC:NRSPo <NRSPo>
Specifies the power offset for non-anchor carrier for data transmission relative to NRS
level.
Parameters:
<NRSPo> N12 | N10 | N8 | N6 | N4 | N2 | ZERO | P3
Negative (Nx), 0 dB (ZERO), or positive (Px) power offset. The
"x" denotes value in dB.
*RST: ZERO
Example: To set the power offset of -12 dB, execute:
CONF:NIOT:SIGN:CONN:NAC:NRSP N12
See Configuring Non-Anchor Parameters.
User Manual 1178.5689.02 ─ 12 221

Command Reference
Manual operation: See "NRS Power Offset" on page 90
2.5.13.10 Non-Anchor configuration Rel.14 - Paging
The following commands are related to non-anchor configuration for paging.

CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:CHANnel:DL...............223
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:CHANnel:DL.............. 223
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DBMap...................... 223
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DBMap......................223
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DGAP........................ 224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DGAP....................... 224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DURFactor:MAX......... 224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DURFactor:MAX........ 224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:ENABle......................224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:ENABle..................... 224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:EXBitmap...................225
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:EXBitmap.................. 225
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPDc...................... 225
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPDc......................225
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPPeriod................. 226
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPPeriod................ 226
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPTh.......................226
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPTh...................... 226
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:NRSPo...................... 227
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:NRSPo......................227
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:OFFSet:DL.................227
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:OFFSet:DL................ 227
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:ENABle............228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:ENABle........... 228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:NREP.............. 228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:NREP..............228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:PWEight.......... 228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:PWEight.......... 228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:PWEight:
ENABle...............................................................................................................229
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:PWEight:
ENABle...............................................................................................................229
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:WUSConf:ENABle...... 229
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:WUSConf:ENABle...... 229
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:ENABle........................................... 230
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:PWANchor.......................................230
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:PWANchor:ENABle...........................230
User Manual 1178.5689.02 ─ 12 222

Command Reference
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:CHANnel:DL
<DLChannel>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:CHANnel:DL
<DLChannel>
Specifies the DL non-anchor paging carrier as DL frequency or channel No.
Commands for carrier ..:ONE:.. and ..:TWO:.. are provided.
Parameters:
<DLChannel> decimal
2110.0 MHz to 2169.9 MHz
*RST: 340 Ch
Manual operation: See "DL Channel" on page 92
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DBMap
<BitMap>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DBMap
<BitMap>
Defines the bitmap to schedule paging for the corresponding carrier. If an explicit non-
anchor bitmap is used, the allowed DL subframes are specified via:
EXBitmap or
EXBitmap
Parameters:
<BitMap> NOB | ANB | EXB
NOB: no bitmap
ANB: anchor bitmap
EXB: explicit non-anchor bitmap
*RST: NOB
User Manual 1178.5689.02 ─ 12 223

Command Reference
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DGAP
<GapDc>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DGAP
<GapDc>
Defines the transmission gap configuration to be applied for non-anchor paging sched-
uling.
Parameters:
<GapDc> NOG | ANG | EXG
NOG: no gap
ANG: anchor gap
EXG: explicit non-anchor gap
*RST: NOG
Manual operation: See "Downlink Gap" on page 92
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DURFactor:
MAX <MaxDFactor>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DURFactor:
MAX <MaxDFactor>
Sets the maximal duration of WUS for non-anchor paging carriers.
Parameters:
<MaxDFactor> R128 | R64 | R32 | R16 | R8 | R4 | R2
Rx: Maximal duration of WUS expressed in factor of subframes
1/x
*RST: R128
Manual operation: See "Max Duration Factor" on page 94
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:ENABle
<Enable>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:ENABle
<Enable>
Enables/disables paging for the corresponding non-anchor carrier.
User Manual 1178.5689.02 ─ 12 224

Command Reference
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Enable Non-Anchor Carrier" on page 92
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:EXBitmap
<ExBMap>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:EXBitmap
<ExBMap>
Specifies the allowed DL subframes for anchor or non-anchor paging scheduling. The
anchor or non-anchor paging carrier is selected by:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DBMap or
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DBMap.
Parameters:
<ExBMap> binary
Explicit bitmap
Range: B#0 to B#1111111111
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPDc
<GapDc>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPDc
<GapDc>
Sets the gap duration coefficient (dl-GapDurationCoeff) for paging non-anchor
carrier.
The duration of the transmission gap is calculated as:
(dl-GapPeriodicity)
See also CONFigure:NIOT:SIGN:CONNection:NAC:GAPPeriod.
User Manual 1178.5689.02 ─ 12 225

Command Reference
Parameters:
<GapDc> numeric | 1 | 2 | 3 | 4
x: specifies the gap duration coefficient x/8: 1/8, 1/4, 3/8, or 1/2
*RST: 1
Manual operation: See "Gap Duration Coefficient" on page 93
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPPeriod
<Periodicity>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPPeriod
<Periodicity>
Selects the transmission gap cycle (64, 128, 256, or 512 subframes) for non-anchor
paging carrier.
Parameters:
<Periodicity> SF64 | SF128 | SF256 | SF512
Periodicity in subframes.
*RST: SF64
Manual operation: See "Gap Periodicity" on page 93
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPTh
<GapTh>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPTh
<GapTh>
Specifies the maximum number of NPDCCH repetitions configured for non-anchor
paging carrier before the DL transmission gap is applied.
Parameters:
<GapTh> N32 | N64 | N128 | N256
Number of NPDCCH repetitions
*RST: N32
Manual operation: See "Gap Threshold" on page 93
User Manual 1178.5689.02 ─ 12 226

Command Reference
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:NRSPo
<NRSPo>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:NRSPo
<NRSPo>
Specifies the power offset for non-anchor paging carrier relative to NRS level.
Parameters:
<NRSPo> N12 | N10 | N8 | N6 | N4 | N2 | ZERO | P3
Negative (Nx), 0 dB (ZERO), or positive (Px) power offset. The
"x" denotes value in dB.
*RST: ZERO
Example: To set the power offset of -12 dB for non-anchor carrier one,
execute:
CONF:NIOT:SIGN:CONN:NAC:PAG:CARR:ONE:NRSP N12
Manual operation: See "NRS Power Offset" on page 93
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:OFFSet:DL
<DLChannel>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:OFFSet:DL
<DLChannel>
Sets the DL carrier channel offset of the NB-IoT channel number to EARFCN.
Parameters:
<DLChannel> VN10 | VN9 | VN8 | VN7 | VN6 | VN5 | VN4 | VN3 | VN2 | VN1 |
VNHF | V0 | V1 | V2 | V3 | V4 | V5 | V6 | V7 | V8 | V9
VNx: channel number offset in the range {-10, -9, -8,-7, -6, -5,
-4, -3, -2, -1}
VNHF: channel number offset of -0.5
Vx: channel number offset in the range {0, 1, 2, 3, 4, 5, 6, 7, 8,
9}.
*RST: V0
Manual operation: See "DL Channel Offset" on page 92
User Manual 1178.5689.02 ─ 12 227

Command Reference
ENABle <Enable>
ENABle <Enable>
Enables/disables paging via the corresponding non-archor carrier.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Enable PCCH Configuration" on page 93
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:NREP
<Enable>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:NREP
<Enable>
Enables/disables and sets the maximum number of repetitions for paging transmis-
sions over the corresponding non-anchor carrier.
Parameters:
<Enable> R1 | R2 | R4 | R8 | R16 | R32 | R64 | R128 | R256 | R512 |
R1024 | R2048 | SP4 | SP3 | SP2 | SP1 | ON | OFF
Rx: No. of repetitions NREP for NPDSCH
SPx: spare bits 1 to 4
Additional parameters: OFF | ON (disables | enables the paging
for the selected non-anchor carrier)
*RST: R1
Manual operation: See "Num. Repetition Paging" on page 94
PWEight <PWeight>
PWEight <PWeight>
Sets the relative weight of the non-anchor paging carrier for uneven paging load distri-
bution across the carriers. For activation, refer to CONFigure:NIOT:SIGN:
CONNection:NAC:PAGing:CARRier:ONE:PCCH:PWEight:ENABle
User Manual 1178.5689.02 ─ 12 228

Command Reference
Parameters:
<PWeight> W1 | W2 | W3 | W4 | W5 | W6 | W7 | W8 | W9 | W10 | W11 |
W12 | W13 | W14 | W15 | W16
*RST: W1
Example: Use the non-anchor carrier one for paging in 1/16 cases:
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:
CARRier:ONE:PCCH:PWEight W16
Firmware/Software: V3.7.80, V3.8.20: removed values ON/OFF
Manual operation: See "Paging Weight" on page 94
PWEight:ENABle <PWeight>
PWEight:ENABle <PWeight>
Acivates/deactivates the uneven paging load distribution across the non-anchor carri-
ers. For the setting of paging weight, refer to CONFigure:NIOT:SIGN:
CONNection:NAC:PAGing:CARRier:ONE:PCCH:PWEight
Parameters:
<PWeight> OFF | ON
*RST: OFF
Manual operation: See "Paging Weight" on page 94
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:WUSConf:
ENABle <Enable>
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:WUSConf:
ENABle <Enable>
Enables or disables wake-up signal (WUS) for non-anchor paging carriers.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Enable WUS Configuration" on page 94
User Manual 1178.5689.02 ─ 12 229

Command Reference
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:ENABle <Enable>
Enables/disables the paging via non-anchor carriers.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Enable Non-Anchor - Rel.14 Paging" on page 91
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:PWANchor <pwanchor>
Sets the relative weight of the anchor paging carrier for uneven paging load distribution
across the anchor and non-anchor carriers.
The value w0 means, that the anchor carrier is not used for paging.
For activation, refer to CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:
PWANchor:ENABle
Parameters:
<pwanchor> W0 | W1 | W2 | W3 | W4 | W5 | W6 | W7 | W8 | W9 | W10 | W11 |
W12 | W13 | W14 | W15 | W16
*RST: W0
Firmware/Software: V3.7.80, V3.8.20: removed values ON/OFF
Manual operation: See "Paging Weight Anchor" on page 91
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:PWANchor:ENABle
<pwanchor>
Enables/disables the uneven paging load distribution across the anchor and non-
anchor carriers. For the setting of paging weight, refer to CONFigure:NIOT:
SIGN:CONNection:NAC:PAGing:PWANchor.
Parameters:
<pwanchor> OFF | ON
*RST: OFF
Manual operation: See "Paging Weight Anchor" on page 91
User Manual 1178.5689.02 ─ 12 230

Command Reference
2.5.13.11 Non-Anchor configuration Rel.14 - RACH
The following commands are related to non-anchor configuration for random access
procedure.
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:CHANnel:UL................ 231
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:CHANnel:UL................231
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:ENABle........................231
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:ENABle....................... 231
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:OFFSet:UL.................. 232
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:OFFSet:UL.................. 232
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:ENABle............................................. 232
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:NPRach:PROB:ANCHor..................... 232
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:NPRach:PROB:ANCHor:ENABle......... 233
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:CHANnel:UL
<ULChannel>
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:CHANnel:UL
<ULChannel>
Specifies the UL non-anchor RA carrier as UL frequency or channel No.
Parameters:
<ULChannel> numeric
1920.0 MHz to 1979.9 MHz
Range: 18E+3 Ch to 18.599E+3 Ch
*RST: 18.34E+3 Ch
Manual operation: See "UL Channel" on page 96
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:ENABle
<Enable>
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:ENABle
<Enable>
Enables the random access via the corresponding non-anchor carrier.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Enable Non-Anchor Carrier" on page 95
User Manual 1178.5689.02 ─ 12 231

Command Reference
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:OFFSet:UL
<ULChannel>
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:OFFSet:UL
<ULChannel>
Sets the UL carrier channel offset of the NB-IoT channel number to EARFCN.
Parameters:
<ULChannel> VN10 | VN9 | VN8 | VN7 | VN6 | VN5 | VN4 | VN3 | VN2 | VN1 |
VNHF | V0 | V1 | V2 | V3 | V4 | V5 | V6 | V7 | V8 | V9
VNx: channel number offset in the range {-10, -9, -8,-7, -6, -5,
-4, -3, -2, -1}
VNHF: channel number offset of -0.5
Vx: channel number offset in the range {0, 1, 2, 3, 4, 5, 6, 7, 8,
9}.
*RST: V0
Manual operation: See "UL Channel Offset" on page 96
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:ENABle <Enable>
Enables the random access (RA) procedure via non-anchor carriers.
The related settings are signaled via IE SystemInformationBlockType22-NB.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Enable Non-Anchor Rel. 14 RACH" on page 95
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:NPRach:PROB:ANCHor
<pwanchor>
Sets the selection probability for the anchor carrier NPRACH resource. All non-anchor
carriers NPRACH resources have equal probability between them.
User Manual 1178.5689.02 ─ 12 232

Command Reference
Parameters:
<pwanchor> ZERO | R16 | R15 | R14 | R13 | R12 | R11 | R10 | R9 | R8 | R7 |
R6 | R5 | R4 | R3 | R2
ZERO: anchor carrier not used for random access procedure
Rx: probability of 1/x to use anchor carrier for random access
procedure
*RST: ZERO
Manual operation: See "NPRACH Probability Anchor" on page 95
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:NPRach:PROB:ANCHor:
ENABle <ENable>
Enables/disables anchor carrier NPRACH resources. The probability for use of anchor
random access (RA) carrier is set via:
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:NPRach:PROB:ANCHor.
Parameters:
<ENable> OFF | ON
*RST: Disable
Default unit: OFF
Manual operation: See "NPRACH Probability Anchor" on page 95
2.5.13.12 Discontinuous Reception Settings
The following commands configure DL discontinuous reception in downlink in connec-

ted and idle status.
CONFigure:NIOT:SIGN:CONNection:CDRX:DCYCle.....................................................233
CONFigure:NIOT:SIGN:CONNection:CDRX:ENABle.....................................................234
CONFigure:NIOT:SIGN:CONNection:CDRX:ITIMer.......................................................234
CONFigure:NIOT:SIGN:CONNection:CDRX:ODTimer................................................... 234
CONFigure:NIOT:SIGN:CONNection:CDRX:RTIMer..................................................... 235
CONFigure:NIOT:SIGN:CONNection:CDRX:SOFFset................................................... 235
CONFigure:NIOT:SIGN:CONNection:CDRX:ULRetrtimer...............................................235
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:ENABle.......................................... 235
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:PTWindow......................................236
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:CLENgth........................................ 236
CONFigure:NIOT:SIGN:CONNection:EPCReport.......................................................... 236
CONFigure:NIOT:SIGN:CONNection:CDRX:DCYCle <Cycle>
Configures the duration of one DRX cycle.
User Manual 1178.5689.02 ─ 12 233

Command Reference
Parameters:
<Cycle> SF256 | SF512 | SF1024 | SF1280 | SF1536 | SF2048 |
SF2560 | SF3072 | SF4096 | SF4608 | SF5120 | SF6144 |
SF7680 | SF8192 | SF9216 | SF10240
SFn means n subframes
*RST: SF10
Example: See Configuring Discontinuous Reception.
Manual operation: See "DRX Cycle" on page 100
CONFigure:NIOT:SIGN:CONNection:CDRX:ENABle <Enable>
Enables or disables DRX.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Connected DRX" on page 100
CONFigure:NIOT:SIGN:CONNection:CDRX:ITIMer <Timer>
Configures the "drx-InactivityTimer".
Parameters:
<Timer> PSF0 | PSF1 | PSF2 | PSF3 | PSF4 | PSF8 | PSF16 | PSF32
PSFn means n NPDCCH subframes
*RST: PSF1
Manual operation: See "Inactivity Timer" on page 100
CONFigure:NIOT:SIGN:CONNection:CDRX:ODTimer <Timer>
Configures the onDurationTimer of a DRX cycle.
Parameters:
<Timer> PSF1 | PSF2 | PSF3 | PSF4 | PSF8 | PSF16 | PSF32
*RST: PSF3
User Manual 1178.5689.02 ─ 12 234

Command Reference
Manual operation: See "On Duration Timer" on page 100
CONFigure:NIOT:SIGN:CONNection:CDRX:RTIMer <Timer>
Configures the "drx-RetransmissionTimer".
Parameters:
<Timer> PSF0 | PSF1 | PSF2 | PSF4 | PSF6 | PSF8 | PSF16 | PSF24 |
PSF33
*RST: PSF1
Manual operation: See "Retransmission Timer" on page 100
CONFigure:NIOT:SIGN:CONNection:CDRX:SOFFset <Offset>
Configures the "drxStartOffset", shifting all DRX cycles.
Parameters:
<Offset> numeric
Range: 0 to 255
*RST: 0
Manual operation: See "Start Offset" on page 101
CONFigure:NIOT:SIGN:CONNection:CDRX:ULRetrtimer <ULRetransTimer>
Configures the DRX UL retransmission timer.
Parameters:
<ULRetransTimer> PSF0 | PSF1 | PSF2 | PSF4 | PSF6 | PSF8 | PSF16 | PSF24 |
PSF33 | PSF40 | PSF64 | PSF80 | PSF96 | PSF112 | PSF128 |
PSF160 | PSF320
*RST: PSF1
Manual operation: See "UL Retransmission Timer" on page 101
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:ENABle <Enable>
Enables or disables eDRX.
User Manual 1178.5689.02 ─ 12 235

Command Reference
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Enabled" on page 101
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:PTWindow <Window>
Configures the duration of one paging time window in idle mode.
Parameters:
<Window> W2K56 | W5K12 | W7K68 | W10K | W12K | W15K | W17K |
W20K | W23K | W25K | W28K | W30K | W33K | W35K | W38K |
W40K
Duration in subframes.
2560, 5120, 7680, 10240, 12800, 15360, 17920, 20480, 23040,
25600, 28160, 30720, 33280, 35840, 38400, 40960
*RST: W2K56
Manual operation: See "Paging Time Window" on page 101
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:CLENgth <Length>
Configures the duration of one eDRX cycle in idle mode.
Parameters:
<Length> L2K | L4K | L8K | L16K | L32K | L65K | L0M1 | L0M2 | L0M5 |
L1M
Duration in radio frames
2048, 4096, 8192, 16384, 32768, 65536, 131072, 262144,
524288, 1048576
*RST: L2K
Manual operation: See "Cycle Length" on page 101
CONFigure:NIOT:SIGN:CONNection:EPCReport <Enable>
Enables or disables the paging collision report.
User Manual 1178.5689.02 ─ 12 236

Command Reference
Parameters:
<Enable> OFF | ON
*RST: ON
Manual operation: See "Enable Paging Collision Report" on page 99
2.5.13.13 Scheduling Request Settings
The following commands configure response to scheduling request and resources for
random access.
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WITH...................................237
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT................................. 237
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:ALPHa......... 238
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:CINDex........ 238
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:PSR.............238
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:RINDex........ 239
SCINdex:FMT......................................................................................................239
SCINdex:FMT:VALue............................................................................................239
CONFigure:NIOT:SIGN:CONNection:SREQuest:NRESponse........................................ 239
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WITH <Enable>
Enables or disables scheduling requests with HARQ-ack for NB-IoT transmission.
Parameters:
<Enable> OFF | ON
*RST: OFF
Example: See Configuring Scheduling Request
Manual operation: See "With HARQ-ACK / Without HARQ-ACK" on page 102
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT <Enable>
Enables or disables scheduling requests without HARQ-ack for NB-IoT transmission.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "With HARQ-ACK / Without HARQ-ACK" on page 102
User Manual 1178.5689.02 ─ 12 237

Command Reference
ALPHa <alpha>
Sets the fractional power control parameter alpha-r15 for SR without HARQ-ACK.
Parameters:
<alpha> ZERO | DOT4 | DOT5 | DOT6 | DOT7 | DOT8 | DOT9 | ONE
0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1
*RST: ONE
Manual operation: See "Alpha" on page 103
CINDex <Enable>
Sets the NPRACH carrier index for SR without HARQ-ack.
Parameters:
<Enable> ZERO | ONE | TWO
ZERO: anchor carrier
ONE: non-anchor carrier one
TWO: non-anchor carrier two
Manual operation: See "Carrier Index" on page 102
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:PSR
<P0SR>
Sets the p0-SR-r15 to specify target power for SR without HARQ-ACK.
Parameters:
<P0SR> numeric
*RST: -104 dBm
Default unit: dBm
Manual operation: See "P0 SR" on page 103
User Manual 1178.5689.02 ─ 12 238

Command Reference
RINDex <Enable>
Selects the index of the NPRACH resource in the NPRACH-ParametersList for the UL
carrier indicated by nprach-CarrierIndex.
Parameters:
<Enable> ONE | TWO | THRE
The first entry in the list has index ‘1’, the second entry has
index ‘2’, the third entry has index ‘3’.
Manual operation: See "Resource Index" on page 102
SCINdex:FMT <Format>
Selects the NPRACH resource format.
Parameters:
<Format> FT01 | FT2
Manual operation: See "Subcarrier Index" on page 103
SCINdex:FMT:VALue <Format>
Sets the index of the subcarrier in NPRACH-ParametersList for the indicated UL car-
rier.
Parameters:
<Format> numeric
Range: 20 to 23
*RST: 20
Manual operation: See "Subcarrier Index" on page 103
CONFigure:NIOT:SIGN:CONNection:SREQuest:NRESponse <Enable>
If enabled, the R&S CMW ignores scheduling requests from the UE and sends no
response.
User Manual 1178.5689.02 ─ 12 239

Command Reference
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "No Response to SR" on page 102
2.5.14 Messaging (SMS)
The following commands configure parameters of the short message service (SMS)
and return information about received short messages.
CLEan:NIOT:SIGN:SMS:INComing:INFO:MTEXt.......................................................... 240
CONFigure:NIOT:SIGN:SMS:INComing:FILE............................................................... 241
CONFigure:NIOT:SIGN:SMS:INComing:FILE:INFO?.....................................................241
CONFigure:NIOT:SIGN:SMS:OUTGoing:BINary........................................................... 241
CONFigure:NIOT:SIGN:SMS:OUTGoing:CGRoup........................................................ 242
CONFigure:NIOT:SIGN:SMS:OUTGoing:DCODing....................................................... 242
CONFigure:NIOT:SIGN:SMS:OUTGoing:FILE.............................................................. 242
CONFigure:NIOT:SIGN:SMS:OUTGoing:FILE:INFO?....................................................243
CONFigure:NIOT:SIGN:SMS:OUTGoing:INTernal......................................................... 243
CONFigure:NIOT:SIGN:SMS:OUTGoing:LHANdling......................................................243
CONFigure:NIOT:SIGN:SMS:OUTGoing:MCLass......................................................... 244
CONFigure:NIOT:SIGN:SMS:OUTGoing:MESHandling................................................. 244
CONFigure:NIOT:SIGN:SMS:OUTGoing:OADDress......................................................245
CONFigure:NIOT:SIGN:SMS:OUTGoing:OSADdress.................................................... 245
CONFigure:NIOT:SIGN:SMS:OUTGoing:PIDentifier...................................................... 245
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:DATE............................................ 245
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:TIME.............................................246
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:TSOurce....................................... 246
CONFigure:NIOT:SIGN:SMS:OUTGoing:UDHeader......................................................247
SENSe:NIOT:SIGN:SMS:INComing:INFO:DCODing?....................................................247
SENSe:NIOT:SIGN:SMS:INComing:INFO:MLENgth?.................................................... 247
SENSe:NIOT:SIGN:SMS:INComing:INFO:MTEXt?........................................................248
SENSe:NIOT:SIGN:SMS:INFO:LRMessage:RFLag?.....................................................248
SENSe:NIOT:SIGN:SMS:OUTGoing:INFO:LMSent?..................................................... 248
CLEan:NIOT:SIGN:SMS:INComing:INFO:MTEXt
Resets all parameters related to a received SMS message. The message text and the
information about the message length are deleted. The "message read" flag is set to
true.
Example: See Sending / Receiving a Short Message
Usage: Event
Manual operation: See "Clear Message Text" on page 109
User Manual 1178.5689.02 ─ 12 240

Command Reference
CONFigure:NIOT:SIGN:SMS:INComing:FILE <SMSFile>
Selects the file of a received message. You can display information about the selected
file via the command CONFigure:NIOT:SIGN:SMS:INComing:FILE:INFO?.
Parameters:
<SMSFile> string
Path of the file as string, for example:
"@USERDATA\sms\NBIOT\Received\rx_001.sms"
Manual operation: See "Select File" on page 109
CONFigure:NIOT:SIGN:SMS:INComing:FILE:INFO?
Displays information about the file selected via CONFigure:NIOT:SIGN:SMS:
INComing:FILE.
Return values:
<MessageEncoding> string
Encoding of the message as string (7-bit "ascii", 8-bit "binary",
16-bit "Unicode")
<MessageText> string
Message text as string
<MessageLength> decimal
Number of characters in the message
Range: 0 to 10E+3
<MessageSegments> decimal
Number of segments
Range: 0 to 1000
Usage: Query only
CONFigure:NIOT:SIGN:SMS:OUTGoing:BINary <SMSbinary>
Defines the message contents for outgoing 8-bit binary messages.
Parameters:
<SMSbinary> numeric
Message contents as hexadecimal number with up to 1400 dig-
its
User Manual 1178.5689.02 ─ 12 241

Command Reference

Manual operation: See "Outgoing SMS binary" on page 106
CONFigure:NIOT:SIGN:SMS:OUTGoing:CGRoup <CodingGroup>
Selects the coding group to be indicated to the message recipient in the TP-Data-Cod-
ing-Scheme field.
Parameters:
<CodingGroup> GDCoding | DCMClass
GDCoding: General data coding
DCMClass: Data coding / message class
*RST: GDC
Manual operation: See "Coding Group" on page 107
CONFigure:NIOT:SIGN:SMS:OUTGoing:DCODing <DataCoding>
Selects the data coding for outgoing messages.
Parameters:
<DataCoding> BIT7 | BIT8
BIT7: 7-bit encoded ASCII message
BIT8: 8-bit encoded binary message
*RST: BIT7
Manual operation: See "Data Coding / Character Set" on page 106
CONFigure:NIOT:SIGN:SMS:OUTGoing:FILE <SMSFile>
Selects a file containing the message to be transmitted.
Parameters:
<SMSFile> string
Path of the file as string, for example:
"@USERDATA\sms\NBIOT\Send\example_ascii.sms"
User Manual 1178.5689.02 ─ 12 242

Command Reference
CONFigure:NIOT:SIGN:SMS:OUTGoing:FILE:INFO?
Displays information about the file selected via CONFigure:NIOT:SIGN:SMS:
OUTGoing:FILE.
Return values:
Encoding of the message as string (7-bit ASCII, 8-bit binary, 16-
bit Unicode)
Number of characters in the message
Range: 0 to 10E+3
Usage: Query only
Manual operation: See "Message Encoding, Message Text, Message Length"
on page 108
CONFigure:NIOT:SIGN:SMS:OUTGoing:INTernal <SMSInternal>
Defines the message text for outgoing 7-bit ASCII messages.
Parameters:
<SMSInternal> string
Message contents as string with up to 800 characters
*RST: "R&S Short Message Service Text.The quick brown
fox jumps over the lazy dog.THE QUICK BROWN
FOX JUMPS OVER THE LAZY DOG.
0123456789 !"#\*%+-/()<>?=;@$,"
Manual operation: See "Outgoing SMS" on page 106
CONFigure:NIOT:SIGN:SMS:OUTGoing:LHANdling <LSMSHandling>
Selects the handling of messages exceeding 160 characters.
User Manual 1178.5689.02 ─ 12 243

Command Reference
Parameters:
<LSMSHandling> TRUNcate | MSMS
TRUNcate: The SMS is truncated to 160 characters, the rest is
discarded.
MSMS: Up to five concatenated messages are sent, consisting
in sum of up to 800 characters.
*RST: TRUN
Manual operation: See "Large SMS Handling" on page 105
CONFigure:NIOT:SIGN:SMS:OUTGoing:MCLass <MessageClass>
Selects the message class to be indicated to the message recipient in the TP-Data-
Coding-Scheme field.
Parameters:
<MessageClass> CL0 | CL1 | CL2 | CL3 | NONE
CL0, CL1, CL2, CL3: Class 0 to 3
NONE: Do not send message class
*RST: NONE
Manual operation: See "Message Class" on page 107
CONFigure:NIOT:SIGN:SMS:OUTGoing:MESHandling <OutgoingMsgHandling>
Selects whether an outgoing message is defined directly via the GUI/commands or
read from a file.
For file selection, see CONFigure:NIOT:SIGN:SMS:OUTGoing:FILE
on page 242.
Parameters:
<OutgoingMsgHandling>
INTernal | FILE
INTernal: message defined directly
FILE: message specified via a file
*RST: INT
Manual operation: See "Outgoing Message Handling" on page 106
User Manual 1178.5689.02 ─ 12 244

Command Reference
CONFigure:NIOT:SIGN:SMS:OUTGoing:OADDress <OrigAddress>
Specifies the originating address to be sent to the message recipient.
Parameters:
<OrigAddress> string
Address as string
*RST: '764332637249279'
Manual operation: See "Originating Address" on page 107
CONFigure:NIOT:SIGN:SMS:OUTGoing:OSADdress <OrigSMSCAddress>
Specifies the originator short message service center address to be sent to the recipi-
ent.
Parameters:
<OrigSMSCAddress> string
Address as string
*RST: '764332637249279'
Manual operation: See "Originator SMSC Address" on page 107
CONFigure:NIOT:SIGN:SMS:OUTGoing:PIDentifier <ID>
Specifies the TP protocol identifier (TP-PID) value to be sent.
Parameters:
<ID> numeric
Range: #H0 to #HFF
*RST: #H0
Manual operation: See "Protocol Identifier" on page 106
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:DATE <Day>, <Month>,

<Year>
Specifies the date of the service center time stamp for CONFigure:NIOT:SIGN:
SMS:OUTGoing:SCTStamp:TSOurce DATE.
User Manual 1178.5689.02 ─ 12 245

Command Reference
Parameters:
<Day> integer
Range: 1 to 31
*RST: 11
<Month> integer
Range: 1 to 12
*RST: 11
<Year> integer
Range: 2011 to 9999
*RST: 2011
Manual operation: See "Service Center Time Stamp" on page 107
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:TIME <Hour>, <Minute>,

<Second>
Specifies the time of the service center time stamp for CONFigure:NIOT:SIGN:
SMS:OUTGoing:SCTStamp:TSOurce DATE.
Parameters:
<Hour> integer
Range: 0 to 23
*RST: 11
<Minute> integer
Range: 0 to 59
*RST: 11
<Second> integer
Range: 0 to 59
*RST: 0
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:TSOurce <SourceTime>
Selects the source for the service center time stamp.
The date and time for the source DATE is configured via the following commands:
● CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:DATE
● CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:TIME
User Manual 1178.5689.02 ─ 12 246

Command Reference
Parameters:
<SourceTime> CMWTime | DATE
CMWTime: Current date and time of the operation system
DATE: Date and time specified via remote commands
*RST: CMWT
CONFigure:NIOT:SIGN:SMS:OUTGoing:UDHeader <Header>
Configures the TP user data header.
Parameters:
<Header> numeric | ON | OFF
Up to 16 hexadecimal digits
Range: #H0 to #HFFFFFFFFFFFFFFFF
*RST: OFF
Additional parameters: OFF | ON (disables | enables sending
the header)
Manual operation: See "User Data Header" on page 106
SENSe:NIOT:SIGN:SMS:INComing:INFO:DCODing?
Returns the data coding of the last message received from the UE.
Return values:
Encoding as string ("7bit" ASCII, "8bit" binary, "16bit" Unicode)
Usage: Query only
Manual operation: See "Data Coding / Character Set" on page 109
SENSe:NIOT:SIGN:SMS:INComing:INFO:MLENgth?
Returns the length of the last SMS message received from the UE.
Return values:
Number of characters of the message
User Manual 1178.5689.02 ─ 12 247

Command Reference

Usage: Query only
Manual operation: See "Message Text / Message Length" on page 109
SENSe:NIOT:SIGN:SMS:INComing:INFO:MTEXt?
Returns the text of the last SMS message received from the UE.
Return values:
Usage: Query only
Manual operation: See "Message Text / Message Length" on page 109
SENSe:NIOT:SIGN:SMS:INFO:LRMessage:RFLag?
Queries the "message read" flag for the last received message.
The flag is true (ON) in the following cases:
● No SMS message has been received.
● The last received SMS message has been read, seeSENSe:NIOT:SIGN:
SMS:INComing:INFO:MTEXt? on page 248.
● The last received SMS message has been deleted, see CLEan:NIOT:SIGN:
SMS:INComing:INFO:MTEXt on page 240.
Return values:
<LastRecMessRead> OFF | ON
OFF: unread message available
ON: no unread message available
Usage: Query only
Manual operation: See "Clear Message Text" on page 109
SENSe:NIOT:SIGN:SMS:OUTGoing:INFO:LMSent?
Indicates, whether the last message was sent successfully or not.
Return values:
<LastMessageSent> SUCCessful | FAILed
User Manual 1178.5689.02 ─ 12 248

List of commands

Usage: Query only
Manual operation: See "Last Message Sent" on page 108
2.5.15 Message Monitoring Settings
The following commands configure message monitoring for NB-IoT signaling applica-
tion.
CONFigure:NIOT:SIGN:MMONitor:ENABle.................................................................. 249
CONFigure:NIOT:SIGN:MMONitor:IPADdress.............................................................. 249
CONFigure:NIOT:SIGN:MMONitor:ENABle <Enable>
Enables or disables message monitoring for the NB-IoT signaling application.
Parameters:
<Enable> OFF | ON
*RST: OFF
Manual operation: See "Add NB-IoT Signaling to logging" on page 110
CONFigure:NIOT:SIGN:MMONitor:IPADdress <Index>
Selects the IP address to which signaling messages are sent for message monitoring.
The address pool is configured globally via
CONFigure:BASE:MMONitor:IPADdress<n>.
A query returns both the current index and the resulting IP address.
Parameters:
<Index> IP1 | IP2 | IP3
Address pool index
Return values:
<IPAddress> string
Used IP address as string
Manual operation: See "Logging PC IPv4 Address" on page 110
2.6 List of commands

CALL:NIOT:SIGN:PSWitched:ACTion...................................................................................................... 135
CATalog:NIOT:SIGN:SCENario?...............................................................................................................150
User Manual 1178.5689.02 ─ 12 249

List of commands
CATalog:NIOT:SIGN:UESinfo:DEFBearer?.............................................................................................. 137
CLEan:NIOT:SIGN:ELOG.........................................................................................................................136
CLEan:NIOT:SIGN:SMS:INComing:INFO:MTEXt.....................................................................................240
CONFigure:NIOT:SIGN:BAND..................................................................................................................154
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:ONE..................................................................180
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:TWO................................................................. 180
CONFigure:NIOT:SIGN:CELL:CENHt:NPDCch:MNRep:ZERO............................................................... 180
CONFigure:NIOT:SIGN:CELL:CENHt:NTHReshold................................................................................. 179
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:ONE..............................................................................180
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:TWO............................................................................. 180
CONFigure:NIOT:SIGN:CELL:CENHt:REPPpre:ZERO............................................................................180
CONFigure:NIOT:SIGN:CELL:CENHt:RSRPthr:ONE...............................................................................180
CONFigure:NIOT:SIGN:CELL:CENHt:RSRPthr:TWO.............................................................................. 180
CONFigure:NIOT:SIGN:CELL:CID:EUTRan.............................................................................................189
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:CPEDt................................................................................. 184
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:TBS:VALue..........................................................................184
CONFigure:NIOT:SIGN:CELL:EDT:ENABle:UPEDt................................................................................. 184
CONFigure:NIOT:SIGN:CELL:EDT:SMALl:ENABle:TBS..........................................................................184
CONFigure:NIOT:SIGN:CELL:EDT:SMALl:ENABle:TBS:SUBSet............................................................ 185
CONFigure:NIOT:SIGN:CELL:IBGBand:BANDwidth................................................................................174
CONFigure:NIOT:SIGN:CELL:IBGBand:CRSize...................................................................................... 174
CONFigure:NIOT:SIGN:CELL:IBGBand:FLEXdlul:ENABle...................................................................... 174
CONFigure:NIOT:SIGN:CELL:IBGBand:GBCPosition..............................................................................176
CONFigure:NIOT:SIGN:CELL:IBGBand:GBUCposition........................................................................... 176
CONFigure:NIOT:SIGN:CELL:IBGBand:IBCPosition............................................................................... 175
CONFigure:NIOT:SIGN:CELL:IBGBand:IBUCposition............................................................................. 176
CONFigure:NIOT:SIGN:CELL:IBGBand:IPCI........................................................................................... 175
CONFigure:NIOT:SIGN:CELL:IBGBand:POFFset....................................................................................175
CONFigure:NIOT:SIGN:CELL:MCC..........................................................................................................188
CONFigure:NIOT:SIGN:CELL:MNC..........................................................................................................189
CONFigure:NIOT:SIGN:CELL:MNC:DIGits...............................................................................................189
CONFigure:NIOT:SIGN:CELL:NPRach:MAXTrans.................................................................................. 178
CONFigure:NIOT:SIGN:CELL:NPRach:NOResponse..............................................................................177
CONFigure:NIOT:SIGN:CELL:NPRach:PRAMping.................................................................................. 178
CONFigure:NIOT:SIGN:CELL:NPRach:PREFormat.................................................................................178
CONFigure:NIOT:SIGN:CELL:OPERmode...............................................................................................172
CONFigure:NIOT:SIGN:CELL:PCID......................................................................................................... 173
CONFigure:NIOT:SIGN:CELL:RESelection:QUALity................................................................................186
CONFigure:NIOT:SIGN:CELL:RESelection:SEARch:INTRasearch......................................................... 187
CONFigure:NIOT:SIGN:CELL:RESelection:SEARch:NINTrasearch........................................................ 187
CONFigure:NIOT:SIGN:CELL:RESelection:TIME.................................................................................... 188
CONFigure:NIOT:SIGN:CELL:SCSPacing............................................................................................... 173
CONFigure:NIOT:SIGN:CELL:SECurity:AUTHenticat.............................................................................. 190
CONFigure:NIOT:SIGN:CELL:SECurity:IALGorithm................................................................................ 190
CONFigure:NIOT:SIGN:CELL:SECurity:MILenage...................................................................................191
CONFigure:NIOT:SIGN:CELL:SECurity:OPC...........................................................................................191
CONFigure:NIOT:SIGN:CELL:SECurity:SECurity.................................................................................... 190
CONFigure:NIOT:SIGN:CELL:SECurity:SKEY......................................................................................... 191
CONFigure:NIOT:SIGN:CELL:SYNC:OFFSet.......................................................................................... 198
CONFigure:NIOT:SIGN:CELL:SYNC:ZONE.............................................................................................198
User Manual 1178.5689.02 ─ 12 250

List of commands
CONFigure:NIOT:SIGN:CELL:TAC...........................................................................................................189
CONFigure:NIOT:SIGN:CELL:TIME:DSTime........................................................................................... 195
CONFigure:NIOT:SIGN:CELL:TIME:LTZoffset......................................................................................... 195
CONFigure:NIOT:SIGN:CELL:TIME:SATTach..........................................................................................195
CONFigure:NIOT:SIGN:CELL:TIME:SNName..........................................................................................197
CONFigure:NIOT:SIGN:CELL:TIME:SNOW............................................................................................. 196
CONFigure:NIOT:SIGN:CELL:TIME:TDATe............................................................................................. 196
CONFigure:NIOT:SIGN:CELL:TIME:TTME.............................................................................................. 196
CONFigure:NIOT:SIGN:CELL:TIME:TTSRc............................................................................................. 197
CONFigure:NIOT:SIGN:CELL:TOUT:OOSYnc......................................................................................... 192
CONFigure:NIOT:SIGN:CELL:TOUT:T3324............................................................................................. 193
CONFigure:NIOT:SIGN:CELL:TOUT:T3412............................................................................................. 193
CONFigure:NIOT:SIGN:CELL:TOUT:TEXT.............................................................................................. 194
CONFigure:NIOT:SIGN:CELL:UEIDentity:IMSI........................................................................................ 192
CONFigure:NIOT:SIGN:CELL:WUSignal:DRX:TOFFset.......................................................................... 181
CONFigure:NIOT:SIGN:CELL:WUSignal:DRXCycles:RELaxed...............................................................181
CONFigure:NIOT:SIGN:CELL:WUSignal:DURFactor:MAX...................................................................... 181
CONFigure:NIOT:SIGN:CELL:WUSignal:EDRX:TOFFset:LONG............................................................ 182
CONFigure:NIOT:SIGN:CELL:WUSignal:EDRX:TOFFset:SHORt........................................................... 182
CONFigure:NIOT:SIGN:CELL:WUSignal:ENABle.................................................................................... 182
CONFigure:NIOT:SIGN:CELL:WUSignal:FPOPos................................................................................... 183
CONFigure:NIOT:SIGN:CELL:WUSignal:NUMPos.................................................................................. 183
CONFigure:NIOT:SIGN:CELL:WUSignal:PAGing:DISable.......................................................................183
CONFigure:NIOT:SIGN:CONNection:BMPC............................................................................................ 199
CONFigure:NIOT:SIGN:CONNection:CDRX:DCYCle.............................................................................. 233
CONFigure:NIOT:SIGN:CONNection:CDRX:ENABle...............................................................................234
CONFigure:NIOT:SIGN:CONNection:CDRX:ITIMer................................................................................. 234
CONFigure:NIOT:SIGN:CONNection:CDRX:ODTimer.............................................................................234
CONFigure:NIOT:SIGN:CONNection:CDRX:RTIMer............................................................................... 235
CONFigure:NIOT:SIGN:CONNection:CDRX:SOFFset............................................................................. 235
CONFigure:NIOT:SIGN:CONNection:CDRX:ULRetrtimer........................................................................ 235
CONFigure:NIOT:SIGN:CONNection:CTYPe........................................................................................... 199
CONFigure:NIOT:SIGN:CONNection:DAPPlication:CIOT........................................................................ 206
CONFigure:NIOT:SIGN:CONNection:DAPPlication:IPVersion................................................................. 206
CONFigure:NIOT:SIGN:CONNection:DIT:ENABle....................................................................................200
CONFigure:NIOT:SIGN:CONNection:DIT:TIMer.......................................................................................200
CONFigure:NIOT:SIGN:CONNection:DPCYcle........................................................................................ 200
CONFigure:NIOT:SIGN:CONNection:DSERver:IPVFaddress..................................................................206
CONFigure:NIOT:SIGN:CONNection:DSERver:PORT.............................................................................207
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:CLENgth.................................................................236
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:ENABle...................................................................235
CONFigure:NIOT:SIGN:CONNection:EDRX:IMODe:PTWindow..............................................................236
CONFigure:NIOT:SIGN:CONNection:EPCReport.................................................................................... 236
CONFigure:NIOT:SIGN:CONNection:HARQen........................................................................................ 214
CONFigure:NIOT:SIGN:CONNection:INTRandom................................................................................... 201
CONFigure:NIOT:SIGN:CONNection:MAXNumtr..................................................................................... 214
CONFigure:NIOT:SIGN:CONNection:NAC:CHANnel:DL......................................................................... 218
CONFigure:NIOT:SIGN:CONNection:NAC:CHANnel:UL......................................................................... 219
CONFigure:NIOT:SIGN:CONNection:NAC:DBMap.................................................................................. 219
CONFigure:NIOT:SIGN:CONNection:NAC:DGAP....................................................................................219
User Manual 1178.5689.02 ─ 12 251

List of commands
CONFigure:NIOT:SIGN:CONNection:NAC:ENABle................................................................................. 220
CONFigure:NIOT:SIGN:CONNection:NAC:EXBitmap.............................................................................. 220
CONFigure:NIOT:SIGN:CONNection:NAC:GAPDc.................................................................................. 220
CONFigure:NIOT:SIGN:CONNection:NAC:GAPPeriod............................................................................ 221
CONFigure:NIOT:SIGN:CONNection:NAC:GAPTh.................................................................................. 221
CONFigure:NIOT:SIGN:CONNection:NAC:NRSPo.................................................................................. 221
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:CHANnel:DL.................................... 223
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DBMap.............................................223
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DGAP...............................................224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:DURFactor:MAX.............................. 224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:ENABle............................................ 224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:EXBitmap.........................................225
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPDc.............................................225
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPPeriod.......................................226
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:GAPTh............................................. 226
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:NRSPo.............................................227
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:OFFSet:DL.......................................227
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:ENABle................................. 228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:NREP....................................228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:PWEight................................228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:PCCH:PWEight:ENABle.................. 229
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:ONE:WUSConf:ENABle........................... 229
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:CHANnel:DL....................................223
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DBMap............................................ 223
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DGAP.............................................. 224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:DURFactor:MAX............................. 224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:ENABle............................................224
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:EXBitmap........................................ 225
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPDc............................................ 225
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPPeriod...................................... 226
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:GAPTh............................................ 226
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:NRSPo............................................ 227
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:OFFSet:DL...................................... 227
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:ENABle................................ 228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:NREP................................... 228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:PWEight............................... 228
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:PCCH:PWEight:ENABle................. 229
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:CARRier:TWO:WUSConf:ENABle...........................229
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:ENABle.................................................................... 230
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:PWANchor............................................................... 230
CONFigure:NIOT:SIGN:CONNection:NAC:PAGing:PWANchor:ENABle..................................................230
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:CHANnel:UL...................................... 231
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:ENABle.............................................. 231
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:ONE:OFFSet:UL.........................................232
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:CHANnel:UL......................................231
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:ENABle..............................................231
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:CARRier:TWO:OFFSet:UL........................................ 232
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:ENABle...................................................................... 232
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:NPRach:PROB:ANCHor............................................232
CONFigure:NIOT:SIGN:CONNection:NAC:RACH:NPRach:PROB:ANCHor:ENABle.............................. 233
User Manual 1178.5689.02 ─ 12 252

List of commands
CONFigure:NIOT:SIGN:CONNection:NPDCch:CSS:MAXNrep................................................................215
CONFigure:NIOT:SIGN:CONNection:NPDCch:MXNRep......................................................................... 216
CONFigure:NIOT:SIGN:CONNection:NPDCch:NREP..............................................................................216
CONFigure:NIOT:SIGN:CONNection:NPDCch:NRRepr?.........................................................................216
CONFigure:NIOT:SIGN:CONNection:NPDCch:OFFSt............................................................................. 217
CONFigure:NIOT:SIGN:CONNection:NPDCch:PERiod?......................................................................... 217
CONFigure:NIOT:SIGN:CONNection:NPDCch:SFOFfst?........................................................................ 217
CONFigure:NIOT:SIGN:CONNection:NPDCch:STSF.............................................................................. 218
CONFigure:NIOT:SIGN:CONNection:NUMHqpc...................................................................................... 215
CONFigure:NIOT:SIGN:CONNection:PCNB.............................................................................................201
CONFigure:NIOT:SIGN:CONNection:PSMallowed...................................................................................201
CONFigure:NIOT:SIGN:CONNection:RAI:ENABle................................................................................... 202
CONFigure:NIOT:SIGN:CONNection:RMC:DL.........................................................................................209
CONFigure:NIOT:SIGN:CONNection:RMC:DL:MCSindex?..................................................................... 210
CONFigure:NIOT:SIGN:CONNection:RMC:FORMat?..............................................................................208
CONFigure:NIOT:SIGN:CONNection:RMC:UL.........................................................................................207
CONFigure:NIOT:SIGN:CONNection:RMC:UL:MCSindex?..................................................................... 208
CONFigure:NIOT:SIGN:CONNection:RRC:KEEP.................................................................................... 202
CONFigure:NIOT:SIGN:CONNection:RRC:RELCause............................................................................ 202
CONFigure:NIOT:SIGN:CONNection:RRC:TIMer.................................................................................... 202
CONFigure:NIOT:SIGN:CONNection:RRCPasitrans................................................................................203
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WITH.......................................................... 237
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT.........................................................237
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:ALPHa.............................. 238
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:CINDex............................. 238
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:PSR.................................. 238
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:RINDex............................. 239
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:SCINdex:FMT...................239
CONFigure:NIOT:SIGN:CONNection:SREQuest:HARQack:WOUT:NPRach:SCINdex:FMT:VALue........239
CONFigure:NIOT:SIGN:CONNection:SREQuest:NRESponse.................................................................239
CONFigure:NIOT:SIGN:CONNection:STYPe........................................................................................... 203
CONFigure:NIOT:SIGN:CONNection:TIMer:NTELeven........................................................................... 204
CONFigure:NIOT:SIGN:CONNection:TIMer:NTTen..................................................................................205
CONFigure:NIOT:SIGN:CONNection:TIMer:TTTen.................................................................................. 205
CONFigure:NIOT:SIGN:CONNection:TMODe.......................................................................................... 203
CONFigure:NIOT:SIGN:CONNection:TMODe:IPVersion..........................................................................204
CONFigure:NIOT:SIGN:CONNection:UDEFined:DL:MCSindex?.............................................................212
CONFigure:NIOT:SIGN:CONNection:UDEFined:DL[:SET<setNr>]..........................................................211
CONFigure:NIOT:SIGN:CONNection:UDEFined:FORMat?..................................................................... 213
CONFigure:NIOT:SIGN:CONNection:UDEFined:UDPattern.................................................................... 210
CONFigure:NIOT:SIGN:CONNection:UDEFined:UL:MCSindex?.............................................................213
CONFigure:NIOT:SIGN:CONNection:UDEFined:UL[:SET<setNr>]..........................................................212
CONFigure:NIOT:SIGN:CONNection:UECRequest..................................................................................204
CONFigure:NIOT:SIGN:DL:AWGN........................................................................................................... 168
CONFigure:NIOT:SIGN:DL:NRSepre:LEVel............................................................................................. 167
CONFigure:NIOT:SIGN:DL:OCNG........................................................................................................... 167
CONFigure:NIOT:SIGN:DMODe...............................................................................................................172
CONFigure:NIOT:SIGN:FADing:AWGN:BWIDth:NOISe?.........................................................................165
CONFigure:NIOT:SIGN:FADing:AWGN:BWIDth:RATio............................................................................165
CONFigure:NIOT:SIGN:FADing:AWGN:ENABle...................................................................................... 166
User Manual 1178.5689.02 ─ 12 253

List of commands
CONFigure:NIOT:SIGN:FADing:AWGN:FOFFset.....................................................................................166
CONFigure:NIOT:SIGN:FADing:AWGN:SNRatio..................................................................................... 166
CONFigure:NIOT:SIGN:FADing:FSIMulator:DSHift.................................................................................. 160
CONFigure:NIOT:SIGN:FADing:FSIMulator:DSHift:MODE...................................................................... 160
CONFigure:NIOT:SIGN:FADing:FSIMulator:ENABle................................................................................161
CONFigure:NIOT:SIGN:FADing:FSIMulator:GLOBal:SEED.....................................................................161
CONFigure:NIOT:SIGN:FADing:FSIMulator:ILOSs:LOSS........................................................................161
CONFigure:NIOT:SIGN:FADing:FSIMulator:ILOSs:MODE.......................................................................162
CONFigure:NIOT:SIGN:FADing:FSIMulator:PROFile...............................................................................162
CONFigure:NIOT:SIGN:FADing:FSIMulator:RESTart............................................................................... 163
CONFigure:NIOT:SIGN:FADing:FSIMulator:RESTart:MODE................................................................... 163
CONFigure:NIOT:SIGN:FADing:POWer:NOISe:TOTal?...........................................................................164
CONFigure:NIOT:SIGN:FADing:POWer:NOISe?..................................................................................... 164
CONFigure:NIOT:SIGN:FADing:POWer:SUM?........................................................................................ 165
CONFigure:NIOT:SIGN:MMONitor:ENABle..............................................................................................249
CONFigure:NIOT:SIGN:MMONitor:IPADdress......................................................................................... 249
CONFigure:NIOT:SIGN:NCELl:NIOT:CELL<n>........................................................................................ 185
CONFigure:NIOT:SIGN:RFSettings:ALL:BWCHannel..............................................................................154
CONFigure:NIOT:SIGN:RFSettings:CHANnel:DL.................................................................................... 154
CONFigure:NIOT:SIGN:RFSettings:CHANnel:UL.................................................................................... 154
CONFigure:NIOT:SIGN:RFSettings:EATTenuation:INPut.........................................................................153
CONFigure:NIOT:SIGN:RFSettings:EATTenuation:OUTPut<n>.............................................................. 152
CONFigure:NIOT:SIGN:RFSettings:EDC:INPut....................................................................................... 153
CONFigure:NIOT:SIGN:RFSettings:EDC:OUTPut................................................................................... 153
CONFigure:NIOT:SIGN:RFSettings:ENPMode.........................................................................................155
CONFigure:NIOT:SIGN:RFSettings:ENPower..........................................................................................156
CONFigure:NIOT:SIGN:RFSettings:FOFFset:DL..................................................................................... 155
CONFigure:NIOT:SIGN:RFSettings:FOFFset:UL..................................................................................... 155
CONFigure:NIOT:SIGN:RFSettings:MLOFfset......................................................................................... 157
CONFigure:NIOT:SIGN:RFSettings:UDEFined:CHANnel:UL:MAXimum?............................................... 157
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:DL:MAXimum?...........................................158
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:UL:MAXimum?...........................................158
CONFigure:NIOT:SIGN:RFSettings:UDEFined:FREQuency:UL:MINimum?............................................158
CONFigure:NIOT:SIGN:RFSettings:UDEFined:SET................................................................................ 159
CONFigure:NIOT:SIGN:RFSettings:UMARgin..........................................................................................156
CONFigure:NIOT:SIGN:SMS:INComing:FILE.......................................................................................... 241
CONFigure:NIOT:SIGN:SMS:INComing:FILE:INFO?...............................................................................241
CONFigure:NIOT:SIGN:SMS:OUTGoing:BINary......................................................................................241
CONFigure:NIOT:SIGN:SMS:OUTGoing:CGRoup...................................................................................242
CONFigure:NIOT:SIGN:SMS:OUTGoing:DCODing................................................................................. 242
CONFigure:NIOT:SIGN:SMS:OUTGoing:FILE......................................................................................... 242
CONFigure:NIOT:SIGN:SMS:OUTGoing:FILE:INFO?..............................................................................243
CONFigure:NIOT:SIGN:SMS:OUTGoing:INTernal................................................................................... 243
CONFigure:NIOT:SIGN:SMS:OUTGoing:LHANdling................................................................................243
CONFigure:NIOT:SIGN:SMS:OUTGoing:MCLass....................................................................................244
CONFigure:NIOT:SIGN:SMS:OUTGoing:MESHandling...........................................................................244
CONFigure:NIOT:SIGN:SMS:OUTGoing:OADDress................................................................................245
CONFigure:NIOT:SIGN:SMS:OUTGoing:OSADdress..............................................................................245
CONFigure:NIOT:SIGN:SMS:OUTGoing:PIDentifier................................................................................ 245
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:DATE.....................................................................245
User Manual 1178.5689.02 ─ 12 254

List of commands
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:TIME......................................................................246
CONFigure:NIOT:SIGN:SMS:OUTGoing:SCTStamp:TSOurce................................................................246
CONFigure:NIOT:SIGN:SMS:OUTGoing:UDHeader................................................................................247
CONFigure:NIOT:SIGN:UEReport:ENABle.............................................................................................. 148
CONFigure:NIOT:SIGN:UL:ADPower:ENABle......................................................................................... 170
CONFigure:NIOT:SIGN:UL:ADPower:NRSPower.................................................................................... 170
CONFigure:NIOT:SIGN:UL:ADPower:PCALpha.......................................................................................171
CONFigure:NIOT:SIGN:UL:ADPower:PIRPower......................................................................................171
CONFigure:NIOT:SIGN:UL:ADPower:PNNPusch.................................................................................... 171
CONFigure:NIOT:SIGN:UL:NPUSch:ULNPower...................................................................................... 168
CONFigure:NIOT:SIGN:UL:PMAX............................................................................................................ 169
FETCh:NIOT:SIGN:PSWitched:STATe?................................................................................................... 135
ROUTe:NIOT:SIGN:SCENario:SCFading[:FLEXible]:INTernal................................................................. 151
ROUTe:NIOT:SIGN:SCENario:TROFading[:FLEXible]:INTernal...............................................................152
ROUTe:NIOT:SIGN:SCENario?................................................................................................................ 150
ROUTe:NIOT:SIGN:SCENario[:FLEXible]:SCELl..................................................................................... 151
ROUTe:NIOT:SIGN?................................................................................................................................. 150
SENSe:NIOT:SIGN:CELL:CENHt:REPCelev?......................................................................................... 179
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:DL?.................................................................... 177
SENSe:NIOT:SIGN:CELL:IBGBand:CHANnel:OFFSet:UL?.................................................................... 177
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:DL?............................................................................. 177
SENSe:NIOT:SIGN:CELL:IBGBand:FREQuency:UL?............................................................................. 177
SENSe:NIOT:SIGN:ELOG:ALL?...............................................................................................................136
SENSe:NIOT:SIGN:ELOG:LAST?............................................................................................................ 136
SENSe:NIOT:SIGN:FADing:FSIMulator:ILOSs:CSAMples<ClippingCounter>?.......................................163
SENSe:NIOT:SIGN:RRCState?................................................................................................................ 134
SENSe:NIOT:SIGN:SMS:INComing:INFO:DCODing?............................................................................. 247
SENSe:NIOT:SIGN:SMS:INComing:INFO:MLENgth?..............................................................................247
SENSe:NIOT:SIGN:SMS:INComing:INFO:MTEXt?..................................................................................248
SENSe:NIOT:SIGN:SMS:INFO:LRMessage:RFLag?...............................................................................248
SENSe:NIOT:SIGN:SMS:OUTGoing:INFO:LMSent?............................................................................... 248
SENSe:NIOT:SIGN:UECapability:MAC:DINactmon?............................................................................... 139
SENSe:NIOT:SIGN:UECapability:MAC:EDATa?...................................................................................... 139
SENSe:NIOT:SIGN:UECapability:MAC:RELassind?................................................................................ 139
SENSe:NIOT:SIGN:UECapability:RRC:MCARrier?..................................................................................140
SENSe:NIOT:SIGN:UECapability:RRC:MTONe?..................................................................................... 140
SENSe:NIOT:SIGN:UECapability:RRC:UPLane?.....................................................................................140
SENSe:NIOT:SIGN:UECapability:TRANsfer:CATegory?.......................................................................... 140
SENSe:NIOT:SIGN:UECapability:TRANsfer:MDRB?............................................................................... 141
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:MTICarrier?........................................................... 141
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:WUS:ENABle?...................................................... 141
SENSe:NIOT:SIGN:UECapability:TRANsfer:PAGing:WUS:MINGap:EDRX?...........................................141
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:MAXSessions?........................................................ 142
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:PROFiles?............................................................... 142
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:ROHC:ALL?.............................................................143
SENSe:NIOT:SIGN:UECapability:TRANsfer:PDCP:ROHC?.................................................................... 142
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:INTRand?........................................................... 143
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MCARrier?..........................................................143
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MCRRier:NPRach?............................................ 144
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:MTONe?.............................................................144
User Manual 1178.5689.02 ─ 12 255

List of commands
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:SR:HARQack:WITH........................................... 144
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:SR:HARQack:WOUT......................................... 145
SENSe:NIOT:SIGN:UECapability:TRANsfer:PHYSical:TWOHarq?......................................................... 145
SENSe:NIOT:SIGN:UECapability:TRANsfer:RELease?...........................................................................145
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:BANDs:ALL?.................................................................146
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:BANDs?........................................................................ 145
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:MPMax?........................................................................146
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:POWClass?.................................................................. 147
SENSe:NIOT:SIGN:UECapability:TRANsfer:RF:POWFourteen...............................................................147
SENSe:NIOT:SIGN:UEReport:RSRP:RANGe?........................................................................................ 148
SENSe:NIOT:SIGN:UEReport:RSRP?..................................................................................................... 148
SENSe:NIOT:SIGN:UEReport:RSRQ:RANGe?........................................................................................149
SENSe:NIOT:SIGN:UEReport:RSRQ?..................................................................................................... 148
SENSe:NIOT:SIGN:UESinfo:IMEI?...........................................................................................................137
SENSe:NIOT:SIGN:UESinfo:IMSI?...........................................................................................................137
SENSe:NIOT:SIGN:UESinfo:UEADdress:IPV<version>?.........................................................................138
SENSe:NIOT:SIGN:UL:ADPower:EFNPower<format>?...........................................................................169
SENSe:NIOT:SIGN:UL:ADPower:ENPPpower?.......................................................................................169
SENSe:NIOT:SIGN:UL:ADPower:PATHloss?...........................................................................................170
SOURce:NIOT:SIGN:CELL:STATe........................................................................................................... 133
SOURce:NIOT:SIGN:CELL:STATe:ALL?.................................................................................................. 134
User Manual 1178.5689.02 ─ 12 256

R&S®CMW290/500 NB-IoT BLER Measurement
Performing a BLER Measurement
3 NB-IoT BLER Measurement

The BLER measurement is installed together with the NB-IoT signaling application. To
access the measurement, press the softkey "NB-IoT RX Meas" in the NB-IoT signaling
main view.
The measurement sends data to the UE via the NPDSCH. It evaluates the positive
acknowledgments (ACK) and negative acknowledgments (NACK) returned by the UE
to determine the block error ratio (BLER) and the throughput.
The measurement is especially suitable to assess the characteristics and the perfor-
mance of the UE receiver at low RF power levels.
3.1 Performing a BLER Measurement

To measure the downlink BLER, you need a connection with data transfer in the down-
link.
In test mode, set up a DL connection. You can, for example, use a DL RMC. This
scheduling type includes data transfer on the MAC layer.
When you start the measurement, the R&S CMW sends data to the UE via the
NPDSCH. The UE confirms each received transmission with an ACK or NACK via the
NPUSCH. The R&S CMW calculates the DL BLER from the received ACKs and
NACKs.
Confidence BLER measurements

In a normal BLER measurement, typically a fixed number of samples is transmitted,
leading to a fixed test time. The idea behind confidence BLER measurements is to
apply probability theory and predict a range for the BLER at an early stage of the mea-
surement. The measurement is stopped if the probability of the UE to pass or fail the
receiver quality test is large enough (early pass or early fail decision).
Confidence BLER measurements can reduce test times considerably, especially if the
BLER of a receiver is extremely low or high. They are specified in annex G of 3GPP
TS 36.521 as "Statistical Testing".
To perform a confidence BLER measurement, configure especially the following mea-
surement settings (refer to Chapter 3.2.4, "Settings", on page 262):
● Set "Stop Condition" to "Confidence Level"
● Select the "Error Ratio Calculation" according to the test case
● Configure the "Minimum Test Time" according to the test case
● Select a "Limit Error Rate"
Depending on this selection, the pass/fail decision is made according to the rules
specified in 3GPP TS 36.521 annex G.2 or annex G.4.
User Manual 1178.5689.02 ─ 12 257

GUI Reference
3.2 GUI Reference

The BLER measurement is part of the RX measurements that are installed with the
NB-IoT signaling application.
Access: NB-IoT signaling main view > "NB-IoT RX Meas" softkey
The BLER view and configuration dialog are described in this chapter.
● Measurement Main View.......................................................................................258
● Measurement Control............................................................................................259
● Measurement Results........................................................................................... 259
● Settings................................................................................................................. 262
3.2.1 Measurement Main View
The BLER view provides the measurement results on the left. They are described in
the following.
The connection status information displayed at the bottom is the same as in the NB-IoT
signaling main view.
On the right, the view shows common settings of the NB-IoT signaling application, see
Chapter 2.3.1.6, "Settings", on page 43.
To switch to the signaling application, press the "NB-IoT Signaling" softkey two times.
The "Config" hotkey opens either the configuration dialog of the measurement or the
configuration dialog of the signaling application, depending on which softkey is active.
The following figure shows the main BLER view.
User Manual 1178.5689.02 ─ 12 258

GUI Reference
Figure 3-1: BLER main view
3.2.2 Measurement Control
To turn the measurement on or off, select the control softkey and press [ON | OFF] or
[RESTART | STOP]. Alternatively, right-click the control softkey.
BLER (Softkey)
The softkey shows the current measurement state. Additional measurement substates
can be retrieved via remote control.
Remote command:
INITiate:NIOT:SIGN:BLER
STOP:NIOT:SIGN:BLER
ABORt:NIOT:SIGN:BLER
FETCh:NIOT:SIGN:BLER:STATe?
FETCh:NIOT:SIGN:BLER:STATe:ALL?
3.2.3 Measurement Results
Access: "NB-IoT Signaling" main view > "NB-IoT RX Meas" softkey.
User Manual 1178.5689.02 ─ 12 259

GUI Reference
The main view of the BLER measurement shows the measurement results and the
most important settings of the "NB-IoT signaling" application.
Additional settings of the "NB-IoT signaling" application can be accessed via the "Sig-
naling Parameters" softkey and the related hotkeys.
The "BLER Config"/"Config" hotkeys open either the configuration dialog of the mea-
surement or the configuration dialog of the signaling application, depending on which
softkey is active.
Figure 3-2: BLER main view (confidence BLER)
The BLER view provides the measurement results on the left.

On the right, the view shows common settings of the NB-IoT signaling application, see
Chapter 2.3.1.6, "Settings", on page 43.
Result tables
● "ACK / NACK / DTX":
Number of positive and negative acknowledgments received via the NPUSCH
since the start of the measurement. No answer at all (no ACK, no NACK) is coun-
ted as DTX.
The results are presented as absolute number and as percentage relative to the
number of DL transmissions.
● "Retransmission":
Absolute number of DL acknowledgments retransmitted by HARQ process.
Note, that retransmissions have an impact on the calculation of maximal possible
throughput.
User Manual 1178.5689.02 ─ 12 260

GUI Reference
● "BLER":
Block error ratio, percentage of DL transmissions for which no acknowledgment
has been received. The formula used to calculate the BLER is configurable, see
"Error Ratio Calculation" on page 263. By default the following formula is used:
BLER = (NACK + DTX) / (ACK + NACK + DTX)
● "Throughput":
Throughput calculated from the number of acknowledged DL bits, divided by the
time.
– "Average" absolute value: Average throughput since the start of the measure-
ment.
– "Average" relative value: Average throughput as percentage of the maximum
reachable throughput.
– "Max. poss." value: Maximum reachable throughput, assuming that all downlink
transmissions are acknowledged.
The value depends on the scheduling configuration and the channel condition.
Bad channel conditions can result in higher max possible throughput, because
more DL retransmissions are scheduled.
● "Samples":
Number of already sent DL transmissions.
● "UL BLER Results":
– "CRC Pass / Fail": Number of received UL transport blocks with passed / failed
CRC check
– "DTX": Number of UL transport blocked scheduled but no UL transmission
received
– "BLER": Block error ratio; the following formula is used:
(CRC Fail + DTX) / (CRC Pass + CRC Fail + DTX)
– "Throughput": Throughput calculated from the "CRC Pass / Fail" results and
the theoretical maximum UL throughput.
The uplink throughput indicates the average UL throughput since the start of
the measurement. The theoretical maximum throughput is calculated from the
UL settings, assuming that all scheduled UL transport bocks are CRC pass.
Remote command:
FETCh:NIOT:SIGN:BLER:ABSolute?
FETCh:NIOT:SIGN:BLER:RELative?
FETCh:NIOT:SIGN:BLER:UL:ABSolute?
FETCh:NIOT:SIGN:BLER:UL:RELative?
Confidence BLER results

● "Pass/Fail":
The pass/fail decision is based on the BLER results.
When a pass/fail decision has been made , one of the following result values is dis-
played:
– "Early Pass" / "Early Fail":
An early pass or early fail limit was exceeded and an early decision has been
made.
– "Pass" / "Fail":
The configured minimum test time is larger than the early decision table. The
pass/fail decision has been made using the test limit.
● "Specified BLER Level":
User Manual 1178.5689.02 ─ 12 261

GUI Reference
Indicates the currently configured "Limit Error Rate".

Remote command:
FETCh:NIOT:SIGN:BLER:CONFidence?
3.2.4 Settings
Access: "BLER" softkey > "BLER Config" hotkey.

The settings configure the scope of the measurement.
Figure 3-3: BLER settings
Repetition.................................................................................................................... 262
Stop Condition.............................................................................................................262
No. of Samples............................................................................................................263
Error Ratio Calculation................................................................................................ 263
Confidence BLER........................................................................................................263
└ Minimum Test Time.......................................................................................263
└ Limit Error Rate.............................................................................................263
Repetition
Defines how often the measurement is repeated.
"Continuous" The measurement is continued until it is explicitly terminated. The
results are periodically updated.
"Single-Shot" The measurement stops automatically, depending on the configured
"Stop Condition" either when the configured "No. of Subframes" has
been processed or when a confidence BLER measurement result is
available.
Remote command:
CONFigure:NIOT:SIGN:BLER:REPetition
Stop Condition
Selects whether a BLER measurement without stop condition or a confidence BLER
measurement with early decision concept is performed.
"None" The measurement is performed according to its "Repetition" mode
and the specified "No. of Samples". No confidence BLER result is
determined.
User Manual 1178.5689.02 ─ 12 262

GUI Reference
"Confidence A confidence BLER measurement is performed. The measurement

Level" stops when the configured "Minimum Test Time" has passed and a
pass/fail decision has been made, so that a confidence BLER result
(e.g. "Early Pass") is available. The "Repetition" is automatically set
to "Single-Shot".
Remote command:
CONFigure:NIOT:SIGN:BLER:SCONdition
No. of Samples
For measurements without stop condition, this parameter defines the number of DL
transmissions to be processed per measurement cycle (a single-shot measurement
covers one measurement cycle).
For confidence BLER measurements, this parameter specifies only the length of the
throughput result trace. It does not influence the duration of the measurement.
Remote command:
CONFigure:NIOT:SIGN:BLER:SAMPles
Error Ratio Calculation

Selects the formula to be used for calculation of the BLER from the number of ACK,
NACK and DTX. NPDSCH decoding errors result in NACK while NPDCCH decoding
errors result in DTX.
3GPP TS 36.521 specifies which formula must be used for a certain test.
The following formulae are available:
● BLER = (NACK + DTX) / (ACK + NACK + DTX)
● BLER = DTX / (ACK + NACK + DTX)
● BLER = NACK / (ACK + NACK + DTX)
● BLER = NACK / (ACK + NACK)
Remote command:
CONFigure:NIOT:SIGN:BLER:ERCalc
Confidence BLER
The following parameters configure parameters only relevant for confidence BLER
measurements.
Minimum Test Time ← Confidence BLER

Specifies the minimum test time of a confidence BLER measurement as number of
processed samples. During this time, no pass/fail decision is allowed.
Minimum test times are, for example, specified in 3GPP TS 36.521 annex G.4. They
are necessary if the test conditions introduce fluctuations disturbing the statistical inde-
pendence of the single bit error events (e.g. multipath fading). A minimum test time
ensures that the fluctuations are averaged out.
Remote command:
CONFigure:NIOT:SIGN:BLER:CONFidence:MTTime
Limit Error Rate ← Confidence BLER

Selects the limit error ratio for a confidence BLER measurement. The selection deter-
mines, for example, the used pass/fail decision rules.
User Manual 1178.5689.02 ─ 12 263

Programming
The minimum test time and the error ratio calculation formula are independent of this
selection, so configure also these parameters as desired.
"0.1%, 1%" Pass/fail decision according to 3GPP TS 36.521 annex G.4
"5%" Pass/fail decision according to 3GPP TS 36.521 annex G.2
Remote command:
CONFigure:NIOT:SIGN:BLER:CONFidence:LERate
3.3 Programming
The BLER measurement provided by the NB-IoT signaling application is programmed
as follows:
● The application is controlled by SCPI commands with the following syn-
tax: ...:NIOT:SIGN:BLER:...
● After a *RST, the measurement is switched off.
You can start the measurement using INIT:NIOT:SIGN:BLER and retrieve the
results using FETCh commands.
The examples in this section focus on commands directly related to the BLER mea-
surement. For general configuration of the signaling application and setting up the con-
nection, refer to Chapter 2.4.1, "General Configuration", on page 112.
● Configuring a BLER Measurement....................................................................... 264
● Performing a BLER Measurement........................................................................ 265
● Performing a Confidence BLER Measurement..................................................... 265
3.3.1 Configuring a BLER Measurement

// *****************************************************************************
// Configure a continuous BLER measurement without stop condition and
// with 1000 samples per measurement cycle. ACK and NACK contribute to the BLER.
// *****************************************************************************
CONFigure:NIOT:SIGN:BLER:SCONdition NONE
CONFigure:NIOT:SIGN:BLER:REPetition CONT
CONFigure:NIOT:SIGN:BLER:SAMPles 1000
CONFigure:NIOT:SIGN:BLER:ERCalc ERC4
// *****************************************************************************
// Configure a confidence BLER measurement.
// The stop condition "Confidence Level" sets also the repetition.
// NACK and DTX contribute to the BLER.
// Set minimum test time, ER limit 5%.
// *****************************************************************************
CONFigure:NIOT:SIGN:BLER:SCONdition CLEV
CONFigure:NIOT:SIGN:BLER:ERCalc ERC1
CONFigure:NIOT:SIGN:BLER:CONFidence:MTTime 2
CONFigure:NIOT:SIGN:BLER:CONFidence:LERate P050
User Manual 1178.5689.02 ─ 12 264

Command Reference
3.3.2 Performing a BLER Measurement

// *****************************************************************************
// Start the BLER measurement. Wait until the measurement is running.
// *****************************************************************************
INITiate:NIOT:SIGN:BLER
WHILE FETCh:NIOT:SIGN:BLER:STATe:ALL? <> "RUN","ADJ","ACT"
// *****************************************************************************
// Query the measurement results.
// *****************************************************************************
FETCh:NIOT:SIGN:BLER:ABSolute?
FETCh:NIOT:SIGN:BLER:RELative?
FETCh:NIOT:SIGN:BLER:UL:ABSolute?
FETCh:NIOT:SIGN:BLER:UL:RELative?
3.3.3 Performing a Confidence BLER Measurement

// *****************************************************************************
// Start a confidence BLER measurement and return the pass/fail results.
// *****************************************************************************
CONFigure:NIOT:SIGN:BLER:SCONdition CLEV
INITiate:NIOT:SIGN:BLER
FETCh:NIOT:SIGN:BLER:CONFidence?

The following sections describe the commands related to the BLER measurement.
● Measurement Control and States......................................................................... 270
● Measurement Settings.......................................................................................... 272
The following chapters describe the most important conventions and general informa-
3.4.1.1 SIGN
SIGN is used as abbreviation of SIGNaling<instance>. For better readability,

command reference.
User Manual 1178.5689.02 ─ 12 265

Command Reference
firmware application. It can be omitted if the instrument supports only one instance, or
to address the first instance.
3.4.1.2 Keywords
● Command usage
● Parameter usage
● Parameter type
User Manual 1178.5689.02 ─ 12 266

Command Reference

● 0 ("No Error"):
ble memory.
detected.
● 9 ("Uncal"):
not active.
frequency.
User Manual 1178.5689.02 ─ 12 267

Command Reference
mode.
reliable.
maximum.
● 51 ("No Reply"):
User Manual 1178.5689.02 ─ 12 268

Command Reference
nal.
lation type.
User Manual 1178.5689.02 ─ 12 269

Command Reference
schwarz.com.
parameter settings.
3.4.2 Measurement Control and States
The following commands control the measurement and return the current measure-
ment state.
INITiate:NIOT:SIGN:BLER.......................................................................................... 270
STOP:NIOT:SIGN:BLER.............................................................................................270
ABORt:NIOT:SIGN:BLER........................................................................................... 270
FETCh:NIOT:SIGN:BLER:STATe?............................................................................... 271
FETCh:NIOT:SIGN:BLER:STATe:ALL?........................................................................ 271
INITiate:NIOT:SIGN:BLER
STOP:NIOT:SIGN:BLER
ABORt:NIOT:SIGN:BLER
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
User Manual 1178.5689.02 ─ 12 270

Command Reference
● ABORt... halts the measurement immediately. The measurement enters the

"OFF" state. All measurement values are set to NAV. Allocated resources are
released.
Use FETCh...STATe? to query the current measurement state.
Usage: Event
Manual operation: See "BLER (Softkey)" on page 259
FETCh:NIOT:SIGN:BLER:STATe?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<State> OFF | RUN | RDY
OFF: measurement off, no resources allocated, no results
RUN: measurement running, synchronization pending or adjus-
ted, resources active or queued
RDY: measurement terminated, valid results can be available
*RST: OFF
Usage: Query only
FETCh:NIOT:SIGN:BLER:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measure-
ment substates are relevant for running measurements only. Use FETCh:...:STATe?
to query the main measurement state only. Use INITiate..., STOP...,
Return values:
<MainState> OFF | RUN | RDY
*RST: OFF
<SyncState> PEND | ADJ | INV
PEND: waiting for resource allocation, adjustment, hardware
switching ("pending")
ADJ: adjustments finished, measurement running ("adjusted")
INV: not applicable, <MainState> OFF or RDY ("invalid")
User Manual 1178.5689.02 ─ 12 271

Command Reference
<ResourceState> QUE | ACT | INV

QUE: measurement without resources, no results available
("queued")
ACT: resources allocated, acquisition of results in progress but
not complete ("active")
Usage: Query only
3.4.3 Measurement Settings
The following commands configure the BLER measurement.

CONFigure:NIOT:SIGN:BLER:CONFidence:LERate......................................................272
CONFigure:NIOT:SIGN:BLER:CONFidence:MTTime.....................................................272
CONFigure:NIOT:SIGN:BLER:ERCalc......................................................................... 273
CONFigure:NIOT:SIGN:BLER:REPetition.....................................................................273
CONFigure:NIOT:SIGN:BLER:SAMPles.......................................................................273
CONFigure:NIOT:SIGN:BLER:SCONdition................................................................... 274
CONFigure:NIOT:SIGN:BLER:TOUT........................................................................... 274
CONFigure:NIOT:SIGN:BLER:CONFidence:LERate <Rate>
Selects the limit error ratio for a confidence BLER measurement.
Parameters:
<Rate> P001 | P010 | P050
P001: 0.1 %, 3GPP TS 36.521 annex G.4
P010: 1 %, 3GPP TS 36.521 annex G.4
P050: 5 %, 3GPP TS 36.521 annex G.2
*RST: P050
Example: See Configuring a BLER Measurement
Manual operation: See "Limit Error Rate" on page 263
CONFigure:NIOT:SIGN:BLER:CONFidence:MTTime <Time>
Specifies a minimum test time for confidence BLER measurements.
Parameters:
<Time> numeric
Minimum number of processed samples
Range: 0 to 10E+6
Increment: 2000
*RST: 0
User Manual 1178.5689.02 ─ 12 272

Command Reference

Manual operation: See "Minimum Test Time" on page 263
CONFigure:NIOT:SIGN:BLER:ERCalc <Algorithm>
Selects the formula to be used for calculation of the BLER from the number of ACK,
NACK and DTX.
Parameters:
<Algorithm> ERC1 | ERC2 | ERC3 | ERC4
ERC1: BLER = (NACK + DTX) / (ACK + NACK + DTX)
ERC2: BLER = DTX / (ACK + NACK + DTX)
ERC3: BLER = NACK / (ACK + NACK + DTX)
ERC4: BLER = NACK / (ACK + NACK)
*RST: ERC1
Manual operation: See "Error Ratio Calculation" on page 263
CONFigure:NIOT:SIGN:BLER:REPetition <Repetition>
Specifies whether the measurement is stopped after a single shot or repeated continu-
ously.
Parameters:
<Repetition> SINGleshot | CONTinuous
SINGleshot: Single-shot measurement
CONTinuous: Continuous measurement
*RST: SING
Manual operation: See "Repetition" on page 262
CONFigure:NIOT:SIGN:BLER:SAMPles <Samples>
Defines the number of DL transmissions to be processed per measurement cycle.
For confidence BLER measurements, this parameter specifies only the length of the
throughput result trace but does not influence the duration of the measurement.
Parameters:
<Samples> integer
Range: 1 to 500E+3
*RST: 100
User Manual 1178.5689.02 ─ 12 273

Command Reference

Firmware/Software: V3.7.20, V3.7.30: range enhanced and *RST changed, V3.7.40:
range enhanced
Manual operation: See "No. of Samples" on page 263
CONFigure:NIOT:SIGN:BLER:SCONdition <StopCondition>
Selects whether a BLER measurement without stop condition or a confidence BLER
measurement with early decision concept is performed.
Parameters:
<StopCondition> NONE | CLEVel
NONE: no stop condition, no early termination of measurement
CLEVel: confidence BLER measurement
*RST: NONE
Manual operation: See "Stop Condition" on page 262
CONFigure:NIOT:SIGN:BLER:TOUT <Timeout>
Defines a timeout for the measurement. The timer is started when the measurement is
initiated via a READ or INIT command. It is not started if the measurement is initiated
manually ([ON | OFF] key or [RESTART | STOP] key).
When the measurement has completed the first measurement cycle (first single shot),
the statistical depth is reached and the timer is reset.
If the first measurement cycle has not been completed when the timer expires, the
measurement is stopped. The measurement state changes to RDY. The reliability indi-
cator is set to 1, indicating that a measurement timeout occurred. Still running READ,
FETCh or CALCulate commands are completed, returning the available results. At
least for some results, there are no values at all or the statistical depth has not been
reached.
A timeout of 0 s corresponds to an infinite measurement timeout.
Parameters:
<Timeout> numeric
Default unit: s
The following commands retrieve the results of the BLER measurement.
User Manual 1178.5689.02 ─ 12 274

Command Reference
FETCh:NIOT:SIGN:BLER:CONFidence?......................................................................275
FETCh:NIOT:SIGN:BLER:ABSolute?...........................................................................275
FETCh:NIOT:SIGN:BLER:RELative?........................................................................... 276
FETCh:NIOT:SIGN:BLER:UL:ABSolute?......................................................................277
FETCh:NIOT:SIGN:BLER:UL:RELative?...................................................................... 277
FETCh:NIOT:SIGN:BLER:CONFidence?
Returns the pass/fail result of a confidence BLER measurement.
Return values:
<Reliability> decimal
<Confidence> RUNNing | EPASs | EFAil | PASS | FAIL
RUNNing: result not yet provided
EPASs, EFAil: early pass, early fail
PASS, FAIL: pass, fail
Example: See Performing a Confidence BLER Measurement
Usage: Query only
Manual operation: See "Confidence BLER results" on page 261
FETCh:NIOT:SIGN:BLER:ABSolute?
Returns the absolute results of the BLER measurement.
Return values:
See Reliability Indicator
<ACK> decimal
Number of received acknowledgments
<NACK> decimal
Number of received negative acknowledgments
<Samples> decimal
Number of already processed DL transmissions
<Throughput> float
Two comma-separated values: average throughput and maxi-
mum reachable throughput
Default unit: bit/s
<DTX> decimal
Number of sent scheduled subframes for which no ACK and no
NACK has been received
<Retransmission> decimal
Number of DL retransmissions
User Manual 1178.5689.02 ─ 12 275

Command Reference
Example: SeePerforming a BLER Measurement

Usage: Query only
Firmware/Software: V3.7.20, V3.7.70: added <Retransmission>
Manual operation: See "Result tables" on page 260
FETCh:NIOT:SIGN:BLER:RELative?
Returns the relative results of the BLER measurement.
Return values:
<ACK> float
Received acknowledgments (percentage of sent scheduled sub-
frames)
Range: 0 % to 100 %
Default unit: %
<NACK> float
Received negative acknowledgments (percentage of sent
scheduled subframes)
Range: 0 % to 100 %
Default unit: %
<BLER> float
Block error ratio (percentage of sent scheduled subframes for
which no ACK has been received)
Range: 0 % to 100 %
Default unit: %
<ThroughputRel> float
Average throughput (as percentage of maximum reachable
throughput)
Range: 0 % to 100 %
Default unit: %
<DTX> float
Percentage of sent scheduled subframes for which no ACK and
no NACK has been received
Range: 0 % to 100 %
Default unit: %
Usage: Query only
User Manual 1178.5689.02 ─ 12 276

Command Reference
FETCh:NIOT:SIGN:BLER:UL:ABSolute?
Returns the uplink results of the BLER measurement.
Return values:
<CRC Pass> decimal
Number of received subframes with passed CRC check
Range: 0 to 2E+9
<CRC Fail> decimal
Number of received subframes with failed CRC check
Range: 0 to 2E+9
<Throughput abs> decimal
Average uplink throughput
Range: 0 bit/s to 200E+6 bit/s
<DTX> decimal
Number of sent scheduled UL subframes for which no data has
been received
Range: 0 to 2E+9
Usage: Query only
FETCh:NIOT:SIGN:BLER:UL:RELative?
Returns the uplink results of the BLER measurement.
Return values:
<CRC Pass> decimal
Number of received subframes with passed CRC check
Range: 0 to 2E+9
<CRC Fail> decimal
Number of received subframes with failed CRC check
Range: 0 to 2E+9
User Manual 1178.5689.02 ─ 12 277

List of commands
<Throughput Rel> decimal

Average uplink throughput (as percentage of maximum reacha-
ble throughput)
Range: 0 % to 100 %
<DTX> float
Number of sent scheduled UL subframes for which no data has
been received
Range: 0 to 2E+9
<BLER> float
Block error ratio
Range: 0 % to 100 %
Usage: Query only

ABORt:NIOT:SIGN:BLER......................................................................................................................... 270
CONFigure:NIOT:SIGN:BLER:CONFidence:LERate................................................................................272
CONFigure:NIOT:SIGN:BLER:CONFidence:MTTime.............................................................................. 272
CONFigure:NIOT:SIGN:BLER:ERCalc..................................................................................................... 273
CONFigure:NIOT:SIGN:BLER:REPetition................................................................................................ 273
CONFigure:NIOT:SIGN:BLER:SAMPles...................................................................................................273
CONFigure:NIOT:SIGN:BLER:SCONdition.............................................................................................. 274
CONFigure:NIOT:SIGN:BLER:TOUT........................................................................................................274
FETCh:NIOT:SIGN:BLER:ABSolute?....................................................................................................... 275
FETCh:NIOT:SIGN:BLER:CONFidence?................................................................................................. 275
FETCh:NIOT:SIGN:BLER:RELative?........................................................................................................276
FETCh:NIOT:SIGN:BLER:STATe:ALL?.................................................................................................... 271
FETCh:NIOT:SIGN:BLER:STATe?............................................................................................................271
FETCh:NIOT:SIGN:BLER:UL:ABSolute?..................................................................................................277
FETCh:NIOT:SIGN:BLER:UL:RELative?.................................................................................................. 277
INITiate:NIOT:SIGN:BLER........................................................................................................................ 270
STOP:NIOT:SIGN:BLER...........................................................................................................................270
User Manual 1178.5689.02 ─ 12 278

R&S®CMW290/500 NB-IoT Multi-Evaluation Measurement
General Description
4 NB-IoT Multi-Evaluation Measurement

The NB-IoT multi-evaluation measurement provides quick and flexible TX tests on
Release 13 NB-IoT uplink signals.
The TX tests cover the following UE transmitter properties:
● UE output power per subcarrier over the entire bandwidth (inband emissions)
● UE output power per slot (power monitor)
● OFF/ON power (power dynamics)
● Modulation accuracy per SC-FDMA symbol (EVM, magnitude error, phase error)
● Modulation accuracy per modulation symbol (EVM)
● I/Q constellation diagram
● Out-of-band emissions (spectrum emission mask and ACLR)
Many of the tests and conformance requirements are specified in 3GPP TS 36.101 or
3GPP TS 36.521.
The multi-evaluation measurement requires option R&S CMW-KM300.
4.1 What's New

This documentation describes version 3.8.30 and higher of the NB-IoT UE multi-evalu-
ation measurement. Compared to version 3.8.20, it provides separate documentation
for instrument models R&S CMW290 and R&S CMW500. R&S CMW100 is still sup-
ported with separate documentation.

The NB-IoT multi-evaluation measurement captures an uplink (UL) NB-IoT signal and
provides the TX measurement results.
The following sections describe how to perform and configure the measurement.
● Test Setup............................................................................................................. 279
● How to Measure an Uplink NB-IoT Signal.............................................................280
● Scope of the Measurement................................................................................... 280
● Parallel Signaling and Measurement.................................................................... 282
● List Mode...............................................................................................................282
● NB-IoT UL Signal Properties.................................................................................287
4.2.1 Test Setup
Connect the external RF signal source (mobile station, signal generator etc.) to one of
the bidirectional RF connectors on the front panel of the R&S CMW.
User Manual 1178.5689.02 ─ 12 279

General Description
4.2.2 How to Measure an Uplink NB-IoT Signal
After connecting your NB-IoT UE to the R&S CMW, you must adjust at least the follow-
ing analyzer settings to the properties of the analyzed UL signal:
● Analyzer "Frequency"
● "Expected Nominal Power", "External Attenuation (Input)" and "User Margin"
Recommended values: "Expected Nominal Power" = peak power of the UE signal
during the measurement; "User Margin" = 0 dB. The smallest possible value of the
"Expected Nominal Power" plus the "User Margin" ensures maximum dynamic
range.
For synchronization to the received signal and proper decoding, some settings must be
in accordance with the measured signal. In particular, ensure that the following param-
eters match up:
● "Subcarrier Spacing"
● "NPUSCH Format"
● All "Resource Allocation" settings
● "Physical Cell ID" and "Delta Seq. Shift"
● "Modulation Scheme"
With matching "Measurement Control" settings, the R&S CMW is able to decode the
signal and determine its frame timing. No additional measurement trigger is required.
Non-matching "Measurement Control" settings generally result in large EVM results or
in an error message.
4.2.3 Scope of the Measurement
For each trigger event, the NB-IoT multi-evaluation measurement can capture up to
256 consecutive slots. The number of captured slots is configured as "No. of Measure
Slots".
If you use a power trigger, the slot sequence starts with the beginning of the first
resource unit of an NPUSCH transmission.
The captured slot sequence with the length "No. of Measure Slots" contributes as fol-
lows to the individual measurements:
● The "Power Monitor" shows the entire slot sequence. The sequence can contain
allocated slots and not-allocated slots.
● The modulation and spectrum results are derived from all allocated slots within the
slot sequence. Not-allocated slots do not contribute. Allocated slots exceeding the
"No. of Measure Slots" do also not contribute.
Modulation measurements include EVM, magnitude error, phase error, I/Q and
inband emissions.
Spectrum measurements include spectrum emission and ACLR results.
To get the maximum measurement speed for these results, set "No. of Measure
Slots" to the number of slots in the transmission, including repetitions.
● For the "Power Dynamics" results, one slot sequence delivers one set of results
(OFF ON OFF power).
User Manual 1178.5689.02 ─ 12 280

General Description
The OFF power after the last allocated slot can only be measured, if all allocated
resource units are captured, including repetitions. To measure the complete result
sequence (OFF ON OFF), you must set "No. of Measure Slots" equal to or greater
than the number of slots in the transmission, including repetitions.
Examples
Assume that you have NPUSCH format 1 with 3 subcarriers. So there are 8 slots per
resource unit. One resource unit is allocated. The NPUSCH transmission is repeated
(repetitions = 2).
So your NPUSCH signal contains a continuous sequence of 16 allocated slots.
If you set "No. of Measure Slots" to 10, you get the following results:
● The power monitor covers the first 10 slots. Measuring one slot sequence increa-
ses the statistic count by 1.
● The first 10 slots contribute to the modulation and spectrum results. Measuring one
slot sequence increases the statistic count by 10.
● The OFF power after the last allocated slot cannot be measured. Only the OFF
power before the first allocated slot and the ON power are measured. Measuring
one slot sequence increases the statistic count by 1.
Trigger event
Modulation and spectrum 10 slots
Power monitor 10 slots
OFF Power dynamics ON Not captured
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
One resource unit Repetition Time
Figure 4-1: Measured slots with No. of Measure Slots = 10
If you set "No. of Measure Slots" to 20, you get the following results:
● The power monitor covers 20 slots (16 allocated slots plus 4 not-allocated slots).
Measuring one slot sequence increases the statistic count by 1.
● The 16 allocated slots contribute to the modulation and spectrum results. Measur-
ing one slot sequence increases the statistic count by 16.
● All power dynamics results are measured (OFF ON OFF). Measuring one slot
sequence increases the statistic count by 1.
User Manual 1178.5689.02 ─ 12 281

General Description
Trigger event
Modulation and spectrum 16 slots
Power monitor 20 slots

OFF
Power dynamics ON OFF
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
One resource unit Repetition Time
Figure 4-2: Measured slots with No. of Measure Slots = 20
If you set the number of measured slots to 16, you get the same results as with 20
slots - at least for modulation, spectrum and power dynamics results. The change
would only affect the power monitor, where you would see 16 slots instead of 20 slots.
4.2.4 Parallel Signaling and Measurement
You can use the multi-evaluation measurement in parallel to the NB-IoT signaling appli-
cation (option R&S CMW-KS300). Set up a connection to the UE with the signaling
application. Then measure the resulting uplink signal with the multi-evaluation mea-
surement.
To use both applications in parallel, the combined signal path scenario must be activa-
ted (see "Scenario = Combined Signal Path" on page 306). Most signal routing and
analyzer settings and some measurement control settings are then configured by the
signaling application. The multi-evaluation measurement displays the corresponding
signaling settings instead of its own settings. These signaling settings can be config-
ured both in the measurement GUI and in the GUI of the signaling application.
To configure these settings via remote commands, use the commands of the signaling
application. For a mapping table, see Chapter 4.5.4, "Combined Signal Path Com-
mands", on page 407.
The most important signaling parameters not relevant for standalone measurements
can nevertheless be configured both in the measurement GUI and in the GUI of the
signaling application. In the measurement GUI, they can be accessed via hotkeys.
Whenever the combined signal path scenario is activated or the controlling application
is changed, the frame trigger signal provided by the controlling signaling application is
selected automatically as trigger source.
4.2.5 List Mode
The NB-IoT multi-evaluation list mode requires option R&S CMW-KM012. In this mode,
the measurement interval is subdivided into segments, according to basic uplink signal
User Manual 1178.5689.02 ─ 12 282

General Description
properties like expected power, frequency and NPUSCH configuration (format,

resource units, subcarriers, repetitions).
The subcarrier spacing cannot be changed during the measurement. Configure sepa-
rate measurements for different subcarrier spacings.
4.2.5.1 List Mode Configuration
Each segment contains an integer number of slots and is measured at constant ana-
lyzer settings. In each segment, a single NPUSCH transmission is measured.
The NPUSCH transmission must start with the first slot of the segment. At the end of a
segment, you can have additional slots without NPUSCH transmission.
The figure below shows two segments with different lengths and signal properties. The
NPUSCH configuration is listed in the figure. Blue rectangles depict slots of an
NPUSCH transmission.
The grey slots are part of the configured segment length. But there is no NPUSCH
transmission in these slots.
Trigger event
Format 1 Format 1
1 SC (16 slots) 12 SC (2 slots)
1 RU 1 RU
1 repetition 2 repetition
NPUSCH 16 slots NPUSCH 4 slots
Time
Segment no. 1 Segment no. 2
You can configure up to 2000 segments in total as preparation for list mode measure-
ments. One list mode measurement can cover up to 1000 segments with in total up to
4000 measured slots. For details, see Maximum number of measured slots. That
means, for each measurement you select a range of up to 1000 segments to be mea-
sured from the total range of up to 2000 configured segments.
In list mode, the R&S CMW can measure modulation results (including inband emis-
sion results), ACLR and spectrum emission results. The measured quantities can be
enabled or disabled individually for each segment.
A segment without any enabled measurements is called inactive segment. Inactive
segments are useful for time-consuming UE reconfiguration. For that purpose, you
define alternating active and inactive segments. In the active segments, you measure
the signal. In the inactive segments, you reconfigure the UE for the next measured
segment.
The measurement expects the start of the NPUSCH transmission at the start of the
segment. If the NPUSCH transmission starts later, you can configure an evaluation off-
User Manual 1178.5689.02 ─ 12 283

General Description
set so that the measurement starts later. The evaluation offset specifies how many
slots at the beginning of the segment are ignored.
The statistical length defines the number of slots to be measured per segment. You
can measure an entire NPUSCH transmission or only a part of it. The "current" result
of a segment refers to the last measured slot of the statistical length. Additional statisti-
cal values (average, minimum, maximum and standard deviation) are calculated for the
entire statistical length. The following figure provides a summary.
Trigger event
Eval. offset Statistical length 13 slots Last measured slot

4 slots Calculation of statistical results CURRent result
Time
NPUSCH transmission
Two consecutive segments are often measured at different analyzer settings. The
R&S CMW changes the analyzer settings in the last two slots of a segment. These last
two slots of each segment are automatically excluded from the measurement.
Results of other slots that cannot be measured accurately (because of overflow, low
signal or synchronization error) can also be discarded automatically (parameter Mea-
sure on Exception = Off). The reached statistical length, a reliability indicator for the
measurement and a reliability indicator for the segment are included in most measure-
ment results.
Maximum number of measured slots

The limit of 4000 measured slots comprises measured slots included in a statistical
length. The not measured slots of an active segment do not contribute. Other contribu-
tions that "cost" slots are inactive segments and triggering of a segment.
All segments selected for the measurement are considered. In the worst case, the sum
of the following components must not exceed 4000:
● One slot per inactive segment
● Two times the number of triggered segments
● Per active segment: Slots in the statistic count of the segment plus three slots
Trigger modes
A list mode measurement can either be triggered only once, or it can be retriggered at
the beginning of specified segments.
In "Once" mode, a trigger event is only required to start the measurement. As a result,
the entire range of segments (up to 1000) is measured without additional trigger event.
The trigger is rearmed after the measurement has been finished. The retrigger flag of
User Manual 1178.5689.02 ─ 12 284

General Description
the first segment specifies which trigger source is used (IF power trigger or trigger
source configured via global trigger settings). The retrigger flags of subsequent seg-
ments are ignored.
The "Once" mode is recommended for UL signals with accurate timing over the entire
range of segments.
In "Segment" mode, the retrigger flag of each segment is evaluated. It defines whether
the measurement waits for a trigger event before measuring the segment, or not and
which trigger source is used. For the first segment, the value OFF is interpreted as ON.
Retriggering the measurement is recommended, if the timing of the first slot of a seg-
ment is inaccurate, for example because of signal reconfiguration at the UE. Further-
more, retriggering from time to time can compensate for a possible time drift of the UE.
In the following example, the "Segment" mode is enabled. The measurement stops
when the second segment has been captured and waits for a trigger event from the
globally configured trigger source, before capturing the third segment. After the third
segment, it waits for a trigger event from the IF power trigger source, before capturing
the fourth segment.
Trigger event Trigger event Trigger event

Global source Global source IF power
Retrigger flag Retrigger flag Trigger Retrigger flag Trigger Retrigger flag
OFF OFF armed ON armed IF power
? ?
Time
Segment no. 1 Segment no. 2 Segment no. 3 Segment no. 4
Configuration of segments and measurement
Segment configuration and measurement are independent from each other. To perform
a sequence of measurements at maximum speed, proceed as follows:
1. Configure all segments ever needed.
The R&S CMW supports a range of up to 2000 configured segments.
2. Select up to 1000 consecutive segments within the configured segment range

(consider the maximum number of measured slots).
3. Measure the selected segments.
4. Repeat steps 2 and 3 as often as needed.
User Manual 1178.5689.02 ─ 12 285

General Description
The list mode is essentially a single-shot remote control application. When a measure-
ment is initiated in list mode, all defined segments are measured once. Afterwards, the
results can be retrieved using FETCh commands.
The following remote control commands are used for list mode settings and result
retrieval.
Table 4-1: List mode commands
Parameters SCPI commands
Activate / deactivate list mode CONFigure:NIOT:MEAS:MEValuation:LIST
Range of measured segments CONFigure:NIOT:MEAS:MEValuation:LIST:LRANge
Segment configuration (fre- CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:

quency, NPUSCH format, num- SETup
ber of slots, ...)
Statistical length and result CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:

activation MODulation etc.
Trigger mode TRIGger:NIOT:MEAS:MEValuation:LIST:MODE
RF connector As defined via scenario, see "Scenario = StandAlone" on page 306
Retrieve results FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:...

See Chapter 4.5.3.19, "List Mode Results", on page 396.
The segment number <no> for configure commands is an absolute num-
ber (1 to 2000). The segment number <no> for result retrieval is a rela-
tive number within the range of measured segments (1 to 1000).
Example: Segment 1 to 100 configured. Segment 50 to 59 measured.
For result retrieval <no> = 1 refers to segment 50, <no> = 10 to segment
59.
You can deactivate the list mode via a command and also via the GUI:
1. Go to local using the corresponding hotkey.
The active list mode is indicated in the upper right corner of the current view by the
words "List Mode!".
2. Open the configuration dialog box.
3. In section "Measurement Control", select another measurement mode.
Global and list mode parameters

Some settings are available as special list mode settings and as multi-evaluation set-
tings (e.g. NPUSCH format, frequency and modulation scheme). In list mode, the
R&S CMW ignores these multi-evaluation parameters. All other settings not available
as special list mode settings are taken from the multi-evaluation measurement, e.g.:
● "Subcarrier Spacing"
● "External Attenuation"
● "Measure on Exception"
● Trigger settings
User Manual 1178.5689.02 ─ 12 286

General Description
4.2.5.2 Offline Mode and Offline Segment
In list mode, it is possible to select the results of a single segment for display in the
measurement diagram (see also "Offline Segment Nr. < List Mode" on page 316). This
"offline mode" offers several advantages:
● Check of the measurement results (e.g. while developing test scripts)
● Calculation and display of additional measurement results (traces). Use the
FETCh:NIOT:MEAS:MEValuation:TRACe:... commands to retrieve these
results.
After a list mode measurement is completed, the measurement diagram shows the last
segment measured. Calculation of the offline results in an arbitrary segment requires a
two-stage measurement:
1. Start a single-shot list mode measurement
(INITiate:NIOT:MEAS:MEValuation) to collect all measurement data.
2. Select the offline segment

(CONFigure:NIOT:MEAS:MEValuation:LIST:OSINdex <Segment>).
3. Initiate a second measurement (repeat INITiate:NIOT:MEAS:MEValuation).
4. Go to local to view the results.
The second measurement stage implies a calculation of all measurement results in the
offline segment from the existing raw data. No new measurement data is acquired. By
repeating this second stage for different segments, you can obtain a complete set of
measurement results over the entire measurement length.
Reconfiguration of the measurement

To obtain consistent results in the second measurement stage, the raw data must still
correspond to the measurement settings. Avoid any reconfiguration that would require
a new measurement, if you wish to reuse your data in offline mode.
4.2.6 NB-IoT UL Signal Properties
This section describes the following selected topics related to NB-IoT UL signal proper-
ties.
● Resources in Time and Frequency Domain..........................................................287
● Resource Unit Allocation.......................................................................................289
● Frequency Bands..................................................................................................289
4.2.6.1 Resources in Time and Frequency Domain
The channel bandwidth for the NB-IoT uplink is 200 kHz. At both edges, 10 kHz are not
allocated (guard band). The remaining 180 kHz can be allocated to UEs.
User Manual 1178.5689.02 ─ 12 287

General Description
The 180 kHz are divided into subcarriers. There are two different modes:
● 3.75 kHz subcarrier spacing, bandwidth divided into 48 subcarriers
● 15 kHz subcarrier spacing, bandwidth divided into 12 subcarriers
In the time domain, the smallest unit is an SC-FDMA symbol. Each symbol contains a
guard time called cyclic prefix (CP). A time slot contains seven SC-FDMA symbols with
normal CP. A time slot for 3.75 kHz subcarrier spacing ends with a guard period (GP,
no UL signal).
Depending on the subcarrier spacing, the slot length is 2 ms or 0.5 ms. A radio frame
of 10 ms contains 5 slots or 20 slots.
Durations are often stated in sample intervals Ts. Ts can be calculated from the sam-
pling frequency 30.72 MHz: 1 Ts = 1/30.72 MHz ≈ 32.55 ns.
The following table and figures summarize this information.
Subcarriers Slots Symbol duration
Spacing No. Duration Per frame CP Data Note
3.75 kHz 48 2 ms, 61440 Ts 5 256 Ts 8192 Ts GP at end of slot

2304 Ts
15 kHz 12 0.5 ms, 15360 Ts 20 symbol 1: 160 Ts 2048 Ts -

symbol n: 144 Ts
SC-FDMA symbol
3.75 kHz Normal CP, 256 Ts ≈ 8.3 µs Data, 8192 Ts ≈ 266.7 µs
Guard
2304 Ts
≈ 75 µs
2 ms
Figure 4-3: Frame structure for 3.75 kHz subcarrier spacing
User Manual 1178.5689.02 ─ 12 288

General Description
SC-FDMA symbol
Normal CP, 144 Ts ≈ 4.7 µs

15 kHz Data, 2048 Ts ≈ 66.7 µs
First symbol: 160 Ts ≈ 5.2 µs
7 SC-FDMA symbols with normal CP
0.5 ms
Figure 4-4: Frame structure for 15 kHz subcarrier spacing
4.2.6.2 Resource Unit Allocation
For allocation to a UE, the resources are grouped into resource units (RU). A resource
unit comprises a certain number of subcarriers (SC) in the frequency domain and a
certain number of slots in the time domain.
The allowed values depend on the NPUSCH format and on the subcarrier spacing, as
listed in the following table.
Table 4-2: Number of subcarriers and slots per resource unit
NPUSCH SC spacing No. of SC SC offset No. of slots Modulation RU duration

format
1 3.75 kHz 1 0 to 47 16 BPSK, QPSK 32 ms
15 kHz 1 0 to 11 16 BPSK, QPSK 8 ms
3 0, 3, 6, 9 8 QPSK, 16QAM 4 ms
6 0, 6 4 QPSK, 16QAM 2 ms
12 0 2 QPSK, 16QAM 1 ms
2 3.75 kHz 1 0 to 47 4 BPSK 8 ms
15 kHz 1 0 to 11 4 BPSK 2 ms
You can allocate a sequence of several resource units and define repetitions for the
resource unit sequence.
4.2.6.3 Frequency Bands
The carrier frequencies for NB-IoT uplink signals are defined in 3GPP TS 36.101. Each
operating band contains uplink carrier frequencies identified by channel numbers
User Manual 1178.5689.02 ─ 12 289

General Description
(EARFCN, E-UTRA absolute radio frequency channel number). The assignment

between channel numbers N and carrier center frequencies F is defined as:
N = 10 x (F - FOffset)/MHz + NOffset
The table below provides an overview of all NB-IoT uplink channels. For each band, it
lists the offset frequency FOffset, channel number N, channel number offset NOffset and
carrier center frequency F.
Band FOffset / MHz NOffset Channel no N F / MHz
1 1920 18000 18000 to 18599 1920 to 1979.9
2 1850 18600 18600 to 19199 1850 to 1909.9
3 1710 19200 19200 to 19949 1710 to 1784.9
4 1710 19950 19950 to 20399 1710 to 1754.9
5 824 20400 20400 to 20649 824 to 848.9
7 2500 20750 20750 to 21449 2500 to 2569.9
8 880 21450 21450 to 21799 880 to 914.9
9 1749.9 21800 21800 to 22149 1749.9 to 1784.8
10 1710 22150 22150 to 22749 1710 to 1769.9
11 1427.9 22750 22750 to 22949 1427.9 to 1447.8
12 699 23010 23010 to 23179 699 to 715.9
13 777 23180 23180 to 23279 777 to 786.9
14 788 23280 23280 to 23379 788 to 797.9
17 704 23730 23730 to 23849 704 to 715.9
18 815 23850 23850 to 23999 815 to 829.9
19 830 24000 24000 to 24149 830 to 844.9
20 832 24150 24150 to 24449 832 to 861.9
21 1447.9 24450 24450 to 24599 1447.9 to 1462.8
22 3410 24600 24600 to 25399 3410 to 3489.9
24 1626.5 25700 25700 to 26039 1626.5 to 1660.4
25 1850 26040 26040 to 26689 1850 to 1914.9
26 814 26690 26690 to 27039 814 to 848.9
27 807 27040 27040 to 27209 807 to 823.9
28 703 27210 27210 to 27659 703 to 747.9
30 2305 27660 27660 to 27759 2305 to 2314.9
31 452.5 27760 27760 to 27809 452.5 to 457.4
65 1920 131072 131072 to 131971 1920 to 2009.9
66 1710 131972 131972 to 132671 1710 to 1779.9
User Manual 1178.5689.02 ─ 12 290

GUI Reference
Band FOffset / MHz NOffset Channel no N F / MHz
68 698 132672 132672 to 132971 698 to 727.9
70 1695 132972 132972 to 133121 1695 to 1710
71 663 133122 133122 to 133471 663 to 698
72 451 133472 133472 to 133521 451 to 456
73 450 133522 133522 to 133571 450 to 455
74 1427 133572 133572 to 134001 1427 to 1470
85 698 134002 134002 to 134181 698 to 716
4.3 GUI Reference

The following sections provide detailed reference information on the graphical user
interface (GUI) and the parameters of the NB-IoT multi-evaluation measurement.
● Signal Routing and Analyzer Settings...................................................................306
● Measurement Control Settings..............................................................................309
● Trigger Settings.....................................................................................................317
● Limit Settings.........................................................................................................319
● Shortcut Configuration.......................................................................................... 326
● Additional Softkeys and Hotkeys...........................................................................326
Multi Evaluation (Softkey)

Remote command:
INITiate:NIOT:MEAS:MEValuation
ABORt:NIOT:MEAS:MEValuation
STOP:NIOT:MEAS:MEValuation
FETCh:NIOT:MEAS:MEValuation:STATe?
FETCh:NIOT:MEAS:MEValuation:STATe:ALL?
User Manual 1178.5689.02 ─ 12 291

GUI Reference
The results of the NB-IoT multi-evaluation measurement are displayed in several differ-
ent views. Use the "Display" parameters to select the views and to change the appear-
ance and contents of the views. The views are described in the following sections.
● Overview............................................................................................................... 292
● View Error Vector Magnitude................................................................................ 293
● Views Magnitude Error, Phase Error.....................................................................294
● View Inband Emissions......................................................................................... 295
● View Spectrum Emission Mask.............................................................................296
● View Spectrum ACLR........................................................................................... 298
● View I/Q Constellation...........................................................................................299
● View Power Monitor.............................................................................................. 300
● View Power Dynamics.......................................................................................... 301
● View TX Measurement..........................................................................................303
● Selecting and Modifying Views............................................................................. 304
● Using Markers....................................................................................................... 304
● Common View Elements.......................................................................................305
4.3.2.1 Overview
In the overview, a selection of the following results can be displayed:

● EVM (vs SC-FDMA symbol)
● Magnitude error
● Phase error
● Inband emissions
● Spectrum emission mask
● Spectrum ACLR
● Power monitor
● Power dynamics
● Most important results of detailed view "TX Measurement"
User Manual 1178.5689.02 ─ 12 292

GUI Reference
Figure 4-5: Result overview
The results to be measured and displayed in the overview can be limited using the hot-
key "Assign Views", see Chapter 4.3.8, "Additional Softkeys and Hotkeys",
on page 326.
You can enlarge one of the diagrams in the overview and show a detailed view with
additional measurement results, see Chapter 4.3.2.11, "Selecting and Modifying
Views", on page 304. The traces and bar graphs are described in the following sec-
tions.
4.3.2.2 View Error Vector Magnitude
The view shows one or two diagrams and a statistical overview of results per slot.
User Manual 1178.5689.02 ─ 12 293

GUI Reference
Figure 4-6: Error Vector Magnitude view
● Upper diagram
The bar graph shows the EVM for each SC-FDMA symbol in the measured slot.
The symbols are numbered from 0 to 6, with the reference symbol labeled 3.
Each value is an RMS value or a peak value over all modulation symbols in the
SC-FDMA symbol. The title above the bar graph indicates whether RMS or peak
values are currently displayed. To switch between RMS and peak values, use the
softkey - hotkey combination "Display" - "Select Trace".
● Lower diagram
The lower diagram shows the EVM for all modulation symbols in the measured
slot. The results in the upper diagram are calculated from these data.
For a description of the statistical overview, see Chapter 4.3.2.10, "View TX Measure-
ment", on page 303.
For the parameters at the bottom, see Chapter 4.3.2.13, "Common View Elements",
on page 305.
For query of the diagram contents via remote control, see Chapter 4.5.3.9, "EVM
Results (Traces)", on page 377.
4.3.2.3 Views Magnitude Error, Phase Error
Both views show a diagram and a statistical overview of results per slot.
User Manual 1178.5689.02 ─ 12 294

GUI Reference
Figure 4-7: Magnitude Error view
The diagrams (bar graphs) show the average magnitude error and phase error for
each SC-FDMA symbol in the measured slot. The symbols are numbered from 0 to 6,
with the reference symbol labeled 3.
The bar graphs show RMS-averaged and therefore positive values. The average runs
over all modulation symbols in the SC-FDMA symbol.
For a description of the statistical overview, see Chapter 4.3.2.10, "View TX Measure-
ment", on page 303.
on page 305.
For query of the diagram contents via remote control, see:
● Chapter 4.5.3.10, "Magnitude Error Results (Traces)", on page 379
● Chapter 4.5.3.11, "Phase Error Results (Traces)", on page 380
4.3.2.4 View Inband Emissions
The inband emissions are displayed in a diagram and as a table of statistical results.
User Manual 1178.5689.02 ─ 12 295

GUI Reference
Figure 4-8: Inband Emissions view
The diagram shows the average power in all subcarriers of the measured slot. So it
shows a power vs. frequency representation. The powers are normalized to the current
SC power.
The figure shows that SC number 6 is allocated. The power of the remaining, non-allo-
cated subcarriers must be below the red limit line.
The inband emissions are calculated after compensation of the I/Q origin offset.
For details about the table results, see Chapter 4.3.2.10, "View TX Measurement",
on page 303.
on page 305.
For query of the diagram contents via remote control, see Chapter 4.5.3.12, "Inband
Emission Results", on page 380.
4.3.2.5 View Spectrum Emission Mask
The spectrum emission mask results are displayed in a diagram and as a table of stat-
istical results. Additional margin results can be shown/hidden via hotkey.
User Manual 1178.5689.02 ─ 12 296

GUI Reference
Figure 4-9: Spectrum Emission Mask view
The measurement covers a symmetric frequency range of 4 MHz around the carrier
center frequency.
According to 3GPP TS 36.521, the measurement must be carried out at maximum out-
put power of the UE.
See also Chapter 4.3.6.6, "Spectrum Emission Mask", on page 323.
Margin results
To show/hide the margin results, use the softkey - hotkey combination "Display" - "Mar-
gin On | Off".
Figure 4-10: Emission mask, margin results
A margin indicates the vertical distance between the spectrum emission mask limit line
and a trace. For each emission mask area, the margin represents the "worst" value,
i.e. the minimum determined for the frequencies of the area:
User Manual 1178.5689.02 ─ 12 297

GUI Reference
Margin = minimum (P(f)mask - P(f)trace)
A negative margin indicates that the trace is located above the limit line, i.e. the limit is
exceeded.
The margin result display presents for each active area an "X [MHz]" and a "Y [dB]"
value, for negative ("neg") and positive ("pos") offset frequencies. The Y value indi-
cates the margin (worst value within area). The X value indicates the frequency offset
at which the margin value was found. These frequency offsets are indicated relative to
the center frequency.
The screenshot above shows margin results for the current trace. Corresponding mar-
gin results are displayed for all active traces (current, average, maximum trace). In this
context, "Average" means "margins for average trace" and not "average values of mar-
gins for current trace". "Minimum" means "margins for maximum trace" (resulting in
minimum margins).
The "Total TX Power" in the table indicates the TX power measured in the frequency
domain within 400 kHz around the carrier center frequency. For other table results, see
Chapter 4.3.2.10, "View TX Measurement", on page 303.
on page 305.
For query of the spectrum emission mask results via remote control, see Chap-
ter 4.5.3.13, "Spectrum Emission Results", on page 382.
4.3.2.6 View Spectrum ACLR
The adjacent channel leakage ratio (ACLR) results are displayed in a diagram and as a
table of statistical results.
User Manual 1178.5689.02 ─ 12 298

GUI Reference
Figure 4-11: ACLR view
The diagram shows the mean power in the assigned NB-IoT channel as central bar.
The other bars indicate the mean powers in the adjacent GSM channels and in the
adjacent UTRA channels. All values are absolute power levels in dBm.
The displayed absolute limit lines are calculated from the configured relative ACLR lim-
its. They are only displayed for adjacent channels with a power level above the config-
ured absolute limit.
The ACLR values resulting from the measured powers are displayed in the table below
the diagram. According to 3GPP TS 36.521, the ACLR is defined as the mean power in
the assigned NB-IoT channel divided by the mean power in an adjacent channel. The
mean power in the assigned NB-IoT channel is also displayed.
The filters used for the ACLR measurement are compliant with 3GPP TS 36.521.
According to this specification, ACLR tests must be carried out at maximum output
power of the UE.
on page 305.
For query of the ACLR results via remote control, see Chapter 4.5.3.14, "ACLR Spec-
trum Results", on page 386.
4.3.2.7 View I/Q Constellation
The constellation diagram shows the modulation symbols in the measured slot as
points in the I/Q plane.
User Manual 1178.5689.02 ─ 12 299

GUI Reference
Figure 4-12: I/Q constellation diagram
The constellation diagrams depend on the modulation type. For an ideal signal, the
QPSK constellation diagram consists of four points, on a circle around the origin, with
relative phase angles of 90 deg. An ideal BPSK constellation diagram consists of two
points, with equal distance to the origin. The I value of each point equals its Q value.
Constellation diagrams give a graphical representation of the signal quality and can
help to reveal typical modulation errors causing signal distortions.
The NB-IoT constellation diagram shows the following peculiarities:
● The I/Q amplitudes correspond to the values that the R&S CMW uses for the EVM
calculation: A possible I/Q origin offset is already subtracted out.
● Due to the properties of the NB-IoT signal, a pure I/Q imbalance causes circular
constellation points.
For the parameters on the right, see Chapter 4.3.2.13, "Common View Elements",
on page 305.
For query of the diagram contents, see Chapter 4.5.3.15, "I/Q Constellation Results",
on page 388.
4.3.2.8 View Power Monitor
The power monitor view displays the power in the captured slots.
User Manual 1178.5689.02 ─ 12 300

GUI Reference
Figure 4-13: Power monitor
Each power value is RMS averaged over the entire slot, excluding 20 μs at each slot
border. For 3.75 kHz spacing, the guard period at the end of each slot is also excluded.
The number of slots to be captured and shown on the X-axis is configurable, see "No.
of Measure Slots" on page 311.
The power monitor can be used for power control tests, see 3GPP TS 36.521, 6.3.5F
"Power Control for category NB1".
on page 305.
For query of the power monitor results via remote control, see Chapter 4.5.3.16,
"Power Monitor Results", on page 389.
4.3.2.9 View Power Dynamics
The power dynamics view shows a diagram and a statistical overview of related power
results.
The following figure shows measurement results for the general ON/OFF time mask.
User Manual 1178.5689.02 ─ 12 301

GUI Reference
Figure 4-14: Power Dynamics view
There are two diagrams. One shows the start of the first allocated resource unit (RU).
The other one shows the end of the last allocated RU.
The covered time intervals shown on the X-axis are as follows:
● The origin 0 µs marks the start of the first allocated RU in the left diagram and the
end of the last allocated RU in the right diagram.
● For 3.75 kHz SC spacing, the axis covers -2200 µs to 2200 µs.
● For 15 kHz SC spacing, the axis covers -1100 µs to 1100 µs.
The individual ON and OFF power areas are labeled in the diagrams. Exclusion peri-
ods are marked by gray vertical bars.
The table below the diagrams shows a statistical evaluation of the ON power and OFF
power values. For a definition of the values, see Chapter 4.3.6.8, "Power Dynamics
Limits", on page 324.
For the parameters at the bottom of the view, see Chapter 4.3.2.13, "Common View
Elements", on page 305.
For query of the diagram and table contents via remote control, see Chapter 4.5.3.17,
"Power Dynamics Results", on page 389.
User Manual 1178.5689.02 ─ 12 302

GUI Reference
Measurement configuration
To detect the start of the first RU correctly, configure appropriate trigger settings (for
example power trigger for the rising edge, no delay).
To measure the end of the last allocated RU and the "OFF Power (after)", configure the
resource allocation settings according to your signal properties. Configure a sufficient
number of measured slots (at least length of allocated resource units, including repeti-
tions).
See also Chapter 4.2.3, "Scope of the Measurement", on page 280.
4.3.2.10 View TX Measurement
This view contains tables of statistical results for the TX and RX measurements.
Figure 4-15: TX measurement
The table provides an overview of statistical values obtained in the measured slot.
Other detailed views provide a subset of these values:
● Resource allocation: Configured subcarrier allocation, see "No. of Subcarriers,
Start Subcarrier" on page 313
● EVM, magnitude error ("MErr"), phase error ("PhErr"):
For the SC-FDMA data symbols (all symbols except reference symbol), RMS and
peak values are provided.
The DMRS value refers to the reference symbol (demodulation reference signal).
User Manual 1178.5689.02 ─ 12 303

GUI Reference
● I/Q offset: The I/Q offset is estimated from the distribution of the constellation
points.
● Carrier frequency error: offset between the measured carrier frequency and the
nominal RF frequency of the measured channel
● Timing error: difference between the actual timing and the expected timing
The timing error measurement requires an "external" trigger signal to derive the
expected timing.
The unit Ts stands for the sample interval, see Chapter 4.2.6.1, "Resources in Time
and Frequency Domain", on page 287.
● Occupied bandwidth (OBW): width of the frequency range that contains 99% of the
total integrated power of the transmitted spectrum
● TX power: RMS averaged power over all samples in the slot, equivalent to the sum
of the powers of all (allocated and non-allocated) SCs
● Peak power: peak power of all samples in the slot
● SC power: arithmetic mean value of the average powers in all allocated subcarriers
For query of the results via remote control, see Chapter 4.5.3.18, "Modulation Results
(Single Values)", on page 392.
For the parameters below the table, see Chapter 4.3.2.13, "Common View Elements",
on page 305.
4.3.2.11 Selecting and Modifying Views
Press the "Display" softkey to show hotkeys for view configuration. They change the
appearance and contents of the active view. The following hotkeys are available at the
bottom of the GUI:
Hotkey Description
"Select View ..." Switch to a certain detailed view or overview.

Alternatively, select a diagram in the overview and press [ENTER] or the
rotary knob.
"Select Trace ..." Select the trace types to be displayed in the view.
"X Scale... / Y Scale..." Modify the ranges of the X-axis and the Y-axis.
"Margin On | Off" For the spectrum emission mask measurement: Show or hide margin
results.
4.3.2.12 Using Markers
Press the "Marker" softkey to show hotkeys for marker configuration. They activate
markers and modify their position. The following hotkeys are available at the bottom of
the GUI:
User Manual 1178.5689.02 ─ 12 304

GUI Reference
Hotkey Description
"Ref. Marker..." Enable or disable the reference marker and select the marker position. If sev-
eral traces can be displayed, a trace can also be selected.
"Marker 1/2..." Enable or disable marker 1 or 2 and define the marker position (absolute or rel-
ative to the reference marker).
Depending on the trace mode, a trace can also be selected.
"Select Trace Mode" Define whether markers 1 and 2 are set to the same trace as the reference
marker (collective) or to selectable individual traces.
4.3.2.13 Common View Elements
This section describes elements that are displayed in most views.
Current settings
The most important settings of the NB-IoT NPRACH measurement are displayed at the
top of the measurement dialog.
Statistics in the result tables

Most result diagrams and result tables provide statistical results.
The statistical values are calculated as follows:
● "Current": Result obtained in the last measurement interval. For some modulation
results, an RMS value and a peak value are available. They are calculated as the
average and peak of all samples in the measured slot.
● "Average": Weighted average of all "Current" values since the start of the mea-
surement.
● "Extreme", "Max", "Min": Largest or smallest "Current" value since the start of
the measurement. For EVM, magnitude error and phase error, the extreme value of
all modulation symbols in the slot. No average over data symbols is involved.
● "StdDev": Standard deviation of all "Current" values since the start of the mea-
surement.
Statistic Count
Progress bar for the measurement. During the first single shot after the start of the
measurement, the bar shows the number of elapsed measurement intervals relative to
the configured "Statistic Count". A filled progress bar indicates that the first shot is
complete and the statistical depth has been reached.
Out of Tolerance
Percentage of measurement intervals that were failed because they exceeded the lim-
its in the diagram.
Modulation
Displays the configured modulation scheme, see "Modulation Scheme < Modulation"
on page 315.
User Manual 1178.5689.02 ─ 12 305

GUI Reference
4.3.3 Signal Routing and Analyzer Settings
Access: "Multi Evaluation" tab > "Config" hotkey > top of the configuration dialog.
The parameters at the top of the configuration tree configure the RF input path. Most
parameters are common measurement settings. They have the same value in all NB-
IoT measurements (NPRACH measurement and multi-evaluation measurement).
Figure 4-16: Signal routing and analyzer settings
Duplex Mode............................................................................................................... 306

Scenario = StandAlone............................................................................................... 306
Scenario = Combined Signal Path.............................................................................. 306
Scenario = Measure@ProtocolTest............................................................................ 307
RF Routing.................................................................................................................. 307
External Attenuation (Input)........................................................................................ 307
Band / Channel / Frequency....................................................................................... 308
Frequency Offset.........................................................................................................308
Expected Nominal Power............................................................................................308
User Margin.................................................................................................................309
Mixer Level Offset....................................................................................................... 309
Duplex Mode
Displays the duplex mode of the signal. In Release 13, NB-IoT supports only FDD.
Scenario = StandAlone
The measurement is used standalone, as non-signaling measurement.
Remote command:
ROUTe:NIOT:MEAS:SCENario:SALone
ROUTe:NIOT:MEAS:SCENario?
ROUTe:NIOT:MEAS?
Scenario = Combined Signal Path
Allows you to use an NB-IoT signaling application (option R&S CMW-KS300) in paral-
lel to the NB-IoT measurement.
The additional parameter "Controlled by" selects the signaling application.
User Manual 1178.5689.02 ─ 12 306

GUI Reference
Most parameters described in this section display values determined by the signaling
application. The corresponding measurement settings are remembered in the back-
ground and displayed again when switching back to the standalone scenario.
Connection status information of the signaling application is displayed at the bottom of
the measurement views. Softkeys and hotkeys provide access to the settings of the
signaling application and allow you to switch the downlink signal on or off, see Chap-
ter 4.3.8, "Additional Softkeys and Hotkeys", on page 326.
For additional information, see Chapter 4.2.4, "Parallel Signaling and Measurement",
on page 282.
Remote command:
ROUTe:NIOT:MEAS:SCENario:CSPath
ROUTe:NIOT:MEAS?
Scenario = Measure@ProtocolTest
Allows you to use a protocol test application in parallel to the measurement. The proto-
col test application is selected by the additional parameter "Controlled by".
The signal routing and analyzer settings described in this section are ignored by the
measurement application. Configure the corresponding settings within the protocol test
application.
Remote command:
ROUTe:NIOT:MEAS:SCENario:MAPRotocol
RF Routing
Selects the input path for the measured RF signal, i.e. the input connector and the RX
module to be used.
In the standalone (SA) scenario, these parameters are controlled by the measurement.
In the combined signal path (CSP) scenario, they are controlled by the signaling appli-
cation.
For connector and converter settings in the combined signal path scenario, use one of
the ROUTe:NIOT:SIGN:SCENario:... signaling commands.
Remote command:
ROUTe:NIOT:MEAS:SCENario:SALone (SA)
ROUTe:NIOT:SIGN:SCENario:... (CSP)
External Attenuation (Input)

Defines the value of an external attenuation (or gain, if the value is negative) in the
input path. The power readings are corrected by the external attenuation value.
The external attenuation value is also used in the calculation of the maximum configu-
rable input power value.
nector, then the table name and a button are displayed. Press the button to display the
table entries.
In the standalone (SA) scenario, this parameter is controlled by the measurement. In
the combined signal path (CSP) scenario, it is controlled by the signaling application.
User Manual 1178.5689.02 ─ 12 307

GUI Reference
Remote command:
CONFigure:NIOT:MEAS:RFSettings:EATTenuation (SA)
CONFigure:NIOT:SIGN:RFSettings:EATTenuation:INPut (CSP)
Band / Channel / Frequency

Center frequency of the RF analyzer. Set this frequency to the frequency of the mea-
sured RF signal to obtain a meaningful measurement result. The relation between
operating band, frequency and channel number is defined by 3GPP (see Chap-
ter 4.2.6.3, "Frequency Bands", on page 289).
You can specify the RF frequency in two ways:
● Enter the frequency directly. The band and channel settings can be ignored or used
for validation of the entered frequency. For validation, select the designated band.
The channel number resulting from the selected band and frequency is displayed.
For an invalid combination, no channel number is displayed.
● Select a band and enter a channel number valid for this band. The measurement
calculates the resulting frequency.
In the standalone (SA) scenario, these parameters are controlled by the measurement.
In the combined signal path (CSP) scenario, they are controlled by the signaling appli-
cation. In the guard-band operation mode and the in-band operation mode, there are
channel raster offsets added to the configured RF frequencies. The offsets are only
displayed in the GUI of the signaling application.
Remote command:
CONFigure:NIOT:MEAS:BAND (SA)
CONFigure:NIOT:MEAS:RFSettings:FREQuency (SA)
CONFigure:NIOT:SIGN:BAND (CSP)
CONFigure:NIOT:SIGN:RFSettings:CHANnel:UL (CSP)
Frequency Offset
Positive or negative frequency offset to be added to the specified center frequency of
the RF analyzer.
Remote command:
CONFigure:NIOT:MEAS:RFSettings:FOFFset (SA)
CONFigure:NIOT:SIGN:RFSettings:FOFFset:UL (CSP)
Expected Nominal Power

Defines the nominal power of the RF signal to be measured. An appropriate value for
NB-IoT signals is the peak output power at the DUT during the measurement. The
"Ref. Level" is calculated as follows:
Reference level = Expected Nominal Power + User Margin
Note: The actual input power at the connectors must be within the level range of the
selected RF input connector; refer to the data sheet. If all power settings are config-
ured correctly, the actual power equals the "Reference Level" minus the "External
Attenuation (Input)" value.
User Manual 1178.5689.02 ─ 12 308

GUI Reference
Remote command:
CONFigure:NIOT:MEAS:RFSettings:ENPower (SA)
CONFigure:NIOT:SIGN:RFSettings:ENPMode (CSP)
CONFigure:NIOT:SIGN:RFSettings:ENPower (CSP)
User Margin
Margin that the measurement adds to the expected nominal power to determine its ref-
erence power (reference level). The margin is typically used to account for the known
variations of the RF input signal power, for example, the variations due to a specific
channel configuration.
The variations (crest factor) depend on the signal parameters, in particular the modula-
tion scheme. If the "Expected Nominal Power" is set to the peak power during the mea-
surement, a 0 dB user margin is sufficient.
Remote command:
CONFigure:NIOT:MEAS:RFSettings:UMARgin (SA)
CONFigure:NIOT:SIGN:RFSettings:UMARgin (CSP)
Mixer Level Offset

Varies the input level of the mixer in the analyzer path. A negative offset reduces the
mixer input level. A positive offset increases the mixer input level. Optimize the mixer
input level according to the properties of the measured signal.
Mixer level Advantages Possible shortcomings

offset
< 0 dB Suppression of distortion (e.g. of the inter- Lower dynamic range (due to smaller sig-
modulation products generated in the nal-to-noise ratio)
mixer)
> 0 dB High signal-to-noise ratio, higher dynamic Risk of intermodulation, smaller overdrive
range reserve

Remote command:
CONFigure:NIOT:MEAS:RFSettings:MLOFfset (SA)
CONFigure:NIOT:SIGN:RFSettings:MLOFfset (CSP)
4.3.4 Measurement Control Settings
The "Measurement Control" parameters configure the scope of the NB-IoT multi-evalu-
ation measurement.
While the combined signal path scenario is active, some of the measurement control
parameters display values determined by the controlling signaling application. For
User Manual 1178.5689.02 ─ 12 309

GUI Reference
these parameters, a hint is given in the parameter description. See also "Scenario =
Combined Signal Path" on page 306.
● Control Settings, Part 1......................................................................................... 310
● Control Settings, Part 2......................................................................................... 313
4.3.4.1 Control Settings, Part 1
Access: "Config" hotkey > upper part of the "Measurement Control" section.
This section describes the following "Measurement Control" settings.
Figure 4-17: Measurement control settings - part 1
Repetition.................................................................................................................... 310
Stop Condition.............................................................................................................311
Measurement Mode.....................................................................................................311
Measure on Exception.................................................................................................311
No. of Measure Slots...................................................................................................311
Cyclic Prefix................................................................................................................ 312
Channel Bandwidth..................................................................................................... 312
Subcarrier Spacing......................................................................................................312
NPUSCH Format.........................................................................................................312
Resource Allocation.................................................................................................... 312
└ No. of Subcarriers, Start Subcarrier..............................................................313
└ No. of Resource Units...................................................................................313
└ No. of Repetitions......................................................................................... 313
└ No. of Slots per RU....................................................................................... 313
Repetition
Defines how often the measurement is repeated if it is not stopped explicitly or by a
failed limit check.
● Continuous: The measurement is continued until it is explicitly terminated. The
● Single-Shot: The measurement is stopped after one measurement cycle.
User Manual 1178.5689.02 ─ 12 310

GUI Reference
Single-shot is preferable if only a single measurement result is required under fixed

conditions, which is typical for remote-controlled measurements. The continuous mode
is suitable to monitor the evolution of the measurement results and to observe how
they depend on the measurement configuration, which is typically done in manual con-
trol.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:REPetition
Stop Condition
Specifies the conditions for an early termination of the measurement:
● "None": The measurement is performed according to its "Repetition" mode and
"Statistic Count", irrespective of the limit check results.
● "On Limit Failure": The measurement is stopped when one of the limits is excee-
ded, irrespective of the repetition mode set. If no limit failure occurs, it is performed
according to its "Repetition" mode and "Statistic Count". Use this setting for mea-
surements that are intended for checking limits, e.g. production tests.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:SCONdition
Measurement Mode
Selects/displays the measurement mode.
● "Normal":
In normal mode, the measurement uses a constant reference level for the entire
measurement duration.
● "Multi Eval List Mode":
The list mode can only be enabled via remote control command. When it has been
enabled, "Multi Eval List Mode" is displayed as measurement mode. You can dis-
able it by selecting another mode.
For an introduction to the list mode, see Chapter 4.2.5, "List Mode", on page 282.
Option R&S CMW-KM012 is required.
While the combined signal path scenario is active, this parameter is not configurable.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:MMODe
Measure on Exception
Specifies whether results that the measurement identifies as faulty or inaccurate are
rejected. A faulty result occurs, for example, when an overload is detected. In remote
control, the cause of the error is indicated by the "reliability indicator".
● Off: Faulty results are rejected. The measurement is continued. The statistical
counters are not reset. Use this mode to ensure that a single faulty result does not
affect the entire measurement.
● On: Results are never rejected. Use this mode for development purposes, if you
want to analyze the reason for occasional wrong transmissions.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:MOEXception
No. of Measure Slots

Length of the captured sequence of slots.
User Manual 1178.5689.02 ─ 12 311

GUI Reference
This setting determines the slot sequence measured for the power monitor view.
And this setting is important for power dynamics measurements, to measure the OFF
power after the last allocated resource unit, see Chapter 4.2.3, "Scope of the Measure-
ment", on page 280.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:NSLots
Cyclic Prefix
Only the normal cyclic prefix length is supported.
Channel Bandwidth
Displays the channel bandwidth. The bandwidth is fixed for NB-IoT signals.
Subcarrier Spacing
Selects the subcarrier spacing, 3.75 kHz or 15 kHz. Set this parameter in accordance
with your measured signal.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:SCSPacing (SA)
CONFigure:NIOT:SIGN:CELL:SCSPacing (CSP)
NPUSCH Format
Specifies the format of the NPUSCH, format 1 or format 2.
The format influences for example the allowed resource allocation values, see Chap-
ter 4.2.6.2, "Resource Unit Allocation", on page 289.
If you select an NPUSCH trigger signal as trigger source, the NPUSCH format is set
automatically.
In the combined signal path (CSP) scenario, the signaling application sets the trigger
signal and thus the NPUSCH format automatically. If there is an NPUSCH with format
1 (scheduling type with UL), format 1 is set. If there is no NPUSCH with format 1
(scheduling type with DL only), format 2 is set.
If format 1 is set by the signaling application, but you want to measure format 2, set the
trigger source selection to the format 2 signal.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:NPFormat
Resource Allocation
Configure the settings according to the resource allocation of the measured signal.
Configure the settings in the following order:
● Subcarrier spacing and NPUSCH format
● Number of subcarriers
● Start subcarrier
For background information, see:
● Chapter 4.2.6.1, "Resources in Time and Frequency Domain", on page 287
● Chapter 4.2.6.2, "Resource Unit Allocation", on page 289
User Manual 1178.5689.02 ─ 12 312

GUI Reference

Remote command:
CONFigure:NIOT:SIGN:CONNection:RMC:UL (CSP)
CONFigure:NIOT:SIGN:CONNection:UDEFined:UL[:SET<setNr>] (CSP)
CONFigure:NIOT:SIGN:CONNection:RMC:FORMat? (CSP)
CONFigure:NIOT:SIGN:CONNection:UDEFined:FORMat? (CSP)
The commands for the standalone (SA) scenario are listed in the following.
No. of Subcarriers, Start Subcarrier ← Resource Allocation

Number of subcarriers per resource unit and offset of the first allocated subcarrier from
the edge of the transmission bandwidth.
The allowed values depend on the configured subcarrier spacing and on the NPUSCH
format.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:SUBCarrier (SA)
No. of Resource Units ← Resource Allocation

Number of resource units allocated for the NPUSCH.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:NRUNits (SA)
No. of Repetitions ← Resource Allocation

Number of NPUSCH repetitions.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:NREPetitions (SA)
No. of Slots per RU ← Resource Allocation

Displays the number of slots of one resource unit.
The value depends on the subcarrier spacing and on the number of subcarriers per
resource unit.
4.3.4.2 Control Settings, Part 2
Access: "Config" hotkey > lower part of the "Measurement Control" section.
User Manual 1178.5689.02 ─ 12 313

GUI Reference
Figure 4-18: Measurement control settings - part 2
Physical Cell ID........................................................................................................... 314

Delta Seq. Shift........................................................................................................... 314
Freq. Sync. Range...................................................................................................... 315
Modulation Scheme < Modulation...............................................................................315
Statistic Count............................................................................................................. 315
EVM Excl. Periods Leading/Lagging < Modulation..................................................... 316
OBW Mode < Emission Mask < Spectrum..................................................................316
Select ACLR < ACLR < Spectrum.............................................................................. 316
Time Mask < Dynamics < Power.................................................................................316
Enable < List Mode..................................................................................................... 316
Offline Segment Nr. < List Mode................................................................................. 316
Physical Cell ID
Adjust this parameter to the physical cell ID used by the measured signal. This setting
is required to ensure that the R&S CMW can synchronize to the signal and perform
channel estimation.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:PLCid (SA)
CONFigure:NIOT:SIGN:CELL:PCID (CSP)
Delta Seq. Shift

Delta sequence shift value (Δss) used to calculate the sequence shift pattern for the
NPUSCH. Adjust this value to the measured signal to ensure that the R&S CMW can
synchronize to the signal and perform channel estimation.
User Manual 1178.5689.02 ─ 12 314

GUI Reference
Remote command:
CONFigure:NIOT:MEAS:MEValuation:DSS
Freq. Sync. Range

Specifies the frequency synchronization range.
High The frequency sync. range is ±1.8 kHz for subcarrier spacing
3.75 kHz and ±7 kHz for subcarrier spacing 15 kHz.
Low ±0.2 kHz for subcarrier spacing 3.75 kHz and ±0.8 kHz for subcarrier
spacing 15 kHz. Use this value when the high frequency synchroniza-
tion range cannot be achieved or is not required.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:FSYRange
Modulation Scheme < Modulation

Selects the used modulation scheme. Adjust this value to the measured signal.
The allowed values depend on the configured NPUSCH format and on the number of
allocated subcarriers, see Chapter 4.2.6.2, "Resource Unit Allocation", on page 289.
Configure the resource allocation before configuring this setting.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:MODulation:MSCHeme (SA)
See "Resource Allocation" on page 312 for CSP.
Statistic Count
Defines the number of measurement intervals per measurement cycle.
Scope of the individual statistic counts:
● Modulation:
Used by the views EVM, magnitude error, phase error, inband emissions, I/Q dia-
gram and TX measurement.
One interval comprises one slot.
● Emission mask:
Spectrum emission mask, one interval comprises one slot.
● ACLR:
Spectrum ACLR, one interval comprises one slot.
● Power:
Power dynamics, one interval comprises one complete diagram.
Power monitor, one interval comprises the number of slots specified via parameter
No. of Measure Slots.
The measurement provides independent statistic counts for different results. In single-
shot mode, a measurement with a completed statistic count is stopped, even if another
measurement with an incomplete statistic count is still running.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:SCOunt:MODulation
CONFigure:NIOT:MEAS:MEValuation:SCOunt:SPECtrum:SEMask
User Manual 1178.5689.02 ─ 12 315

GUI Reference
CONFigure:NIOT:MEAS:MEValuation:SCOunt:SPECtrum:ACLR
CONFigure:NIOT:MEAS:MEValuation:SCOunt:POWer
EVM Excl. Periods Leading/Lagging < Modulation

The settings allow you to exclude the first (leading) and the last (lagging) SC-FDMA
symbol of each NPUSCH transmission from the modulation measurements.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:MODulation:EEPeriods:NPUSch:
LEADing
LAGGing
OBW Mode < Emission Mask < Spectrum

Sets the mode of occupied bandwidth (OBW) calculation.
99 % band- The calculation of OBW is based on 99 % of UE TX power.
width
-26 dBc band- The calculation of OBW considers the signal above -26 dBc band-
width width.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:SPECtrum:SEMask:OBWMode
Select ACLR < ACLR < Spectrum

Specifies which adjacent channels are evaluated: GSM channels and/or UTRA chan-
nels.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:SPECtrum:ACLR:ENABle
Time Mask < Dynamics < Power

Displays the type of time mask used for power dynamics measurements.
The general on/off time mask is defined in 3GPP TS 36.521, section 6.3.4F.
See also Chapter 4.3.6.8, "Power Dynamics Limits", on page 324.
Enable < List Mode

The list mode can only be enabled via remote control command. When the list mode
has been enabled, the checkbox allows you to disable the list mode.
You can disable the list mode also by changing the measurement mode, see "Mea-
surement Mode" on page 311.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:LIST
Offline Segment Nr. < List Mode

Selects the list mode segment to be displayed in the measurement diagram. To select
a segment number, the list mode must be enabled.
Option R&S CMW-KM012 is required.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:LIST:OSINdex
User Manual 1178.5689.02 ─ 12 316

GUI Reference
4.3.5 Trigger Settings
Access: "Config" hotkey > "Trigger" section.

The trigger settings configure the trigger system for the NB-IoT multi-evaluation mea-
surement.
Figure 4-19: Trigger settings
Trigger Source.............................................................................................................317
Trigger Slope...............................................................................................................317
Trigger Threshold........................................................................................................ 317
Trigger Delay...............................................................................................................318
Trigger Timeout........................................................................................................... 318
Min Trigger Gap.......................................................................................................... 318
Trigger Source
Selects the source of the trigger event.
Only the measurement-specific trigger sources are listed here. Additional trigger sour-
ces are provided by the base software and by other applications like the GPRF genera-
tor. For a description of these trigger sources, refer to the documentation of the corre-
sponding software part.
"Free Run (No The measurement starts immediately after it is initiated, without any
Sync)" synchronization. This trigger mode can only be used for power moni-
tor, ACLR and emission mask measurements.
"IF Power" The measurement is triggered by the power of the received signal,
converted into an IF signal. The trigger event coincides with the rising
or falling edge of the detected burst.
Remote command:
TRIGger:NIOT:MEAS:MEValuation:SOURce
TRIGger:NIOT:MEAS:MEValuation:CATalog:SOURce?
Trigger Slope
Selects whether the trigger event is generated at the rising edge or at the falling edge
of the trigger pulse. This setting is relevant for power trigger sources.
Remote command:
TRIGger:NIOT:MEAS:MEValuation:SLOPe
Trigger Threshold
Defines the input signal power where a trigger event is generated for power trigger
sources.
User Manual 1178.5689.02 ─ 12 317

GUI Reference
The threshold is a dB value, relative to the reference level minus the external attenua-
tion. If the reference level equals the maximum output power of the DUT and the exter-
nal attenuation settings are correct, the trigger threshold is relative to the maximum
input power.
A low threshold ensures that the input signal is always detected. A higher threshold
can prevent unintended trigger events.
Remote command:
TRIGger:NIOT:MEAS:MEValuation:THReshold
Trigger Delay
Delays the start of the measurement relative to the trigger event. This setting has no
influence on "Free Run" measurements.
Remote command:
TRIGger:NIOT:MEAS:MEValuation:DELay
Trigger Timeout
Sets a time after which a started measurement must have received a trigger event. If
no trigger event is received, a trigger timeout is indicated in manual operation mode. In
remote control mode, the measurement is stopped. The parameter can be disabled so
that no timeout occurs.
This setting has no influence on "Free Run" measurements.
Remote command:
TRIGger:NIOT:MEAS:MEValuation:TOUT
Min Trigger Gap

Defines a minimum duration of the power-down periods (gaps) between two triggered
power pulses. This setting is valid for "(IF) Power" trigger sources.
The trigger system is controlled by a timer which is reset to zero in the following instan-
ces:
● At the IF power-down ramp of each triggered or untriggered pulse, even if the pre-
vious counter has not yet elapsed. A power-down ramp is detected when the signal
power falls below the trigger threshold.
● At the beginning of each measurement. The minimum gap defines the minimum
time between the start of the measurement and the first trigger event.
The trigger system is rearmed when the timer has reached the specified minimum gap.
Start of No trigger Trigger No trigger Trigger

measure- event event event event
ment
Trigger Trigger armed
Minimum Minimum armed Min. Min. Min.
Trigger Trigger Trigger Trigger Trigger
Gap Gap Gap Gap Gap
User Manual 1178.5689.02 ─ 12 318

GUI Reference
This parameter can be used to prevent unwanted trigger events due to fast power var-
iations.
Remote command:
TRIGger:NIOT:MEAS:MEValuation:MGAP
4.3.6 Limit Settings
The following sections give an overview of the NB-IoT multi-evaluation limit settings
and the related conformance test requirements.
Conformance requirements for NB-IoT UE transmitter tests are specified in 3GPP TS
36.521, section 6, "Transmitter Characteristics".
● EVM, Magnitude Error and Phase Error Limits..................................................... 319
● Frequency Error Limits..........................................................................................320
● I/Q Origin Offset Limits..........................................................................................320
● Inband Emissions Limits....................................................................................... 321
● Occupied Bandwidth Limits...................................................................................322
● Spectrum Emission Mask......................................................................................323
● ACLR Limits.......................................................................................................... 324
● Power Dynamics Limits.........................................................................................324
4.3.6.1 EVM, Magnitude Error and Phase Error Limits
Access: "Config" hotkey > "Limits" > "Modulation" section.

A poor modulation accuracy of the UE transmitter increases the transmission errors in
the uplink channel of the network and decreases the system capacity. The error vector
magnitude (EVM) is the critical quantity to assess the modulation accuracy of an NB-
IoT UE.
According to 3GPP, the EVM measured at UE output powers ≥ -40 dBm must not
exceed 17.5 %.
Characteristics Refer to 3GPP TS 36.521 V14.2.0, section... Specified limit
EVM (RMS) 6.5.2.1F.1 Error Vector Magnitude (EVM) for category NB1 ≤ 17.5 %
EVM, magnitude error, phase error limit settings

The EVM limits can be set in the configuration dialog, along with limits for the other
measured quantities.
Figure 4-20: Limit settings for EVM, magnitude and phase error
User Manual 1178.5689.02 ─ 12 319

GUI Reference
Remote command:
CONFigure:NIOT:MEAS:MEValuation:LIMit:EVMagnitude
CONFigure:NIOT:MEAS:MEValuation:LIMit:MERRor
CONFigure:NIOT:MEAS:MEValuation:LIMit:PERRor
4.3.6.2 Frequency Error Limits
Access: "Config" hotkey > "Limits" > "Modulation" > "Frequency Error [ppm]" setting.
3GPP defines the required accuracy of the UE modulated carrier frequency in ppm of
the nominal carrier frequency. The requirements differ for nominal carrier frequencies
below and above 1 GHz.
Characteristics Refer to 3GPP TS 36.521 V14.2.0, section... Frequency Specified limit
Frequency error 6.5.1F Frequency Error for category NB1 ≤ 1 GHz < 0.2 ppm
> 1 GHz < 0.1 ppm
Frequency error limit settings

The frequency error limits can be set in the configuration dialog.
Figure 4-21: Frequency error limit settings
Remote command:
CONFigure:NIOT:MEAS:MEValuation:LIMit:FERRor
4.3.6.3 I/Q Origin Offset Limits
Access: "Config" hotkey > "Limits" > "Modulation" > "IQ Offset" section.
An I/Q origin offset is due to an additive sinusoid waveform at the frequency of the ref-
erence signal. The standard specifies the I/Q origin offset power limit as a function of
the output power of the UE transmitter (see "TX power" in the table).
Characteristics Refer to 3GPP TS 36.521 V14.2.0, section... TX power Spec. limit
I/Q origin offset 6.5.2.2F Carrier leakage for category NB1 > 0 dBm -24.2 dBc
0 dBm to -30 dBm -19.2 dBc
< -30 dBm to -40 dBm -9.2 dBc
I/Q origin offset limit settings

I/Q origin offset limits for three different TX power ranges can be set in the configura-
tion dialog.
User Manual 1178.5689.02 ─ 12 320

GUI Reference
Figure 4-22: I/Q origin offset limit settings
Remote command:
CONFigure:NIOT:MEAS:MEValuation:LIMit:IQOFfset
4.3.6.4 Inband Emissions Limits
Access: "Config" hotkey > "Limits" > "Modulation" > "IBE" section.
The inband emission is the relative UE output power in non-allocated subcarriers
(SCs). Inband emissions are interferers in the subcarrier range that is potentially used
by other connected UEs. 3GPP defines a complex combined inband emission limit
described below.
The combined limit can be determined via the following rules:
● The minimum of the combined limit is -30 dB. In the R&S CMW, this general mini-
mum is configurable.
● A general component is considered for all non-allocated SCs.
● For non-allocated SCs at image frequencies of allocated SCs, an IQ image compo-
nent is added to the general component.
● For SCs at the carrier frequency or next to the carrier frequency, an IQ offset com-
ponent is added to the general component.
So the most complex limit must be determined for a non-allocated SC located both at
an image frequency and next to the carrier frequency. In that case, the general compo-
nent, the IQ image component and the IQ offset component have to be added. Then
the result must be compared to the general minimum and the bigger value of both
applies.
The following table provides an overview of the three components.
Component Value Applicable SCs
General See formula below table Non-allocated SCs
IQ image -24.2 dB Image frequencies
IQ offset -24.2 dBc to -9.2 dBc, depending on TX power Carrier frequency

See Chapter 4.3.6.3, "I/Q Origin Offset Limits",
on page 320
The general limit is derived using the following formula:
User Manual 1178.5689.02 ─ 12 321

GUI Reference
   All SC   
 15  10  log10  , 
   No SC   
 5  ( Offset  1) 
Limit General  max  18  ,  dB  0.8 dB
  No SC  
  SC Power    SC Power Meas 
 
 
The variables are defined as follows:

● <All SC> = total number of subcarriers within the channel bandwidth
● <No SC> = number of allocated subcarriers
● <Offset> = distance of the SC from the closest allocated SC
● <SC Power> = -57 (configurable)
● <SC Power Meas> = arithmetic mean value of the average powers in all allocated
subcarriers (dBm/subcarrier)
IBE min 6.5.2.3F In-band emissions for non-allocated RB for category NB1 See table above
Inband emission limit settings

The general minimum, the variable <SC Power>, the IQ image component and the IQ
offset component can be set in the configuration dialog.
Figure 4-23: Inband emissions limit settings
Remote command:
CONFigure:NIOT:MEAS:MEValuation:LIMit:IBE
CONFigure:NIOT:MEAS:MEValuation:LIMit:IBE:IQOFfset
4.3.6.5 Occupied Bandwidth Limits
Access: "Config" hotkey > "Limits" > "Spectrum" > "OBW Limit" setting.
The occupied bandwidth is the bandwidth that contains 99 % of the total integrated
power of the transmitted spectrum. According to 3GPP, the occupied bandwidth must
be less than the theoretical channel bandwidth (200 kHz).
User Manual 1178.5689.02 ─ 12 322

GUI Reference
Occupied bandwidth (OBW) 6.6.1F Occupied bandwidth for category NB1 < 200 kHz
OBW limit settings

The limit for the occupied bandwidth can be set in the configuration dialog.
Figure 4-24: OBW limit setting
Remote command:
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:OBWLimit
4.3.6.6 Spectrum Emission Mask
Access: "Config" hotkey > "Limits" > "Spectrum" > "Emission Mask" section.
The energy, that spills outside the designated radio channel, increases the interference
with adjacent channels and decreases the system capacity. The amount of unwanted
off-carrier energy is assessed by the out-of-band emissions (excluding spurious emis-
sions). They are specified in terms of the spectrum emission mask and the adjacent
channel leakage power ratio (ACLR).
3GPP specifies a general spectrum emission mask.
Characteristics Refer to 3GPP TS 36.521 V14.2.0, section...
Emission mask 6.6.2.1F Spectrum Emission Mask for category NB1
Emission mask settings

The spectrum emission mask can be defined in the configuration dialog. The following
figure shows the settings. For each emission mask area, you can define the frequency
borders and set an upper power limit for each frequency border. The resulting points
are connected via straight limit lines.
Figure 4-25: Emission mask settings
User Manual 1178.5689.02 ─ 12 323

GUI Reference
The start and stop frequencies of each emission mask area are defined relative to the
edge of the 200-kHz channel.
Example: Assume 0.3 MHz as start frequency and 0.5 MHz as stop frequency. The
resulting area ranges from +0.4 MHz to +0.6 MHz relative to the carrier frequency. As
all ranges are symmetrical, it ranges also from -0.4 MHz to -0.6 MHz relative to the car-
rier frequency.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:LIMit<no>
4.3.6.7 ACLR Limits
Access: "Config" hotkey > "Limits" > "Spectrum" > "ACLR" section.
The adjacent channel leakage power ratio (ACLR) limits complement the spectrum
emission mask. The ACLR is defined as the mean power in the NB-IoT channel divi-
ded by the mean power in an adjacent GSM or UTRA channel.
The relative ACLR limit must be evaluated only, if the measured adjacent channel
power is greater than -50 dBm (absolute limit). In that case, the ACLR must be greater
than the limits listed in the following table.
Characteristics Refer to 3GPP TS 36.521 V14.2.0, section... Relative limit
ACLR 6.6.2.3F Adjacent Channel Leakage power Ratio for category GSM: 19.2 dB
NB1 UTRA: 36.2 dB
ACLR limit settings

The limits can be set in the configuration dialog.
Figure 4-26: ACLR limit settings
The default settings are suitable to check the 3GPP requirements. The relative limits
are only evaluated, if the corresponding absolute limit is exceeded. If you disable an
absolute limit, the corresponding enabled relative limit is always evaluated.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:LIMit:ACLR:GSM
CONFigure:NIOT:MEAS:MEValuation:LIMit:ACLR:UTRA
4.3.6.8 Power Dynamics Limits
Access: "Config" hotkey > "Limits" > "Power" > "Dynamics" section.
Transmission at excessive uplink power increases interference to other channels. A too
low uplink power increases transmission errors. 3GPP defines a general ON/OFF time
mask. The mask contains limits for the UL power in slots not used for transmission
(transmit OFF power), slots used for transmission (transmit ON power) and the power
ramping between them.
User Manual 1178.5689.02 ─ 12 324

GUI Reference
Three power values must be measured:

● ON power, at the beginning of the first allocated resource unit
● OFF power before the ON power
● OFF power after the last allocated resource unit
The measurement duration for the three powers depends on the subcarrier spacing.
For 3.75 kHz subcarrier spacing, each power must be measured for 2 ms (one slot).
For 15 kHz subcarrier spacing, each power must be measured for 1 ms (two slots).
There is a transient period of 20 µs at the beginning of the first allocated resource unit
and after the last allocated resource unit. These transient periods are excluded from
the measurement.
For 3.75 kHz subcarrier spacing, the 2304 Ts gap at the end of each slot, when the UE
is not transmitting, is also excluded.
The following figure provides an overview of the relevant time intervals. The power
dynamics measurement determines the ON power, the OFF power (before) and the
OFF power (after), using the indicated time intervals.
No resource allocation (before) Resource units allocated No resource allocation (after)
20 µs 20 µs
OFF power ON power OFF power
15 kHz: 1 ms 15 kHz: 1 ms 15 kHz: 1 ms
3.75 kHz: 2 ms – 2304 Ts 3.75 kHz: 2 ms – 2304 Ts 3.75 kHz: 2 ms – 2304 Ts
Figure 4-27: OFF/ON transitions
The OFF power must not exceed -48.5 dBm. The ON power must be between -18.5
dBm and -3.5 dBm.
ON power 6.3.4F.1 General ON/OFF time mask for category NB1 ≥ -18.5 dBm, ≤ -3.5
dBm
OFF power 6.3.4F.1 General ON/OFF time mask for category NB1 ≤ -48.5 dBm
Power dynamics limit settings

The limits can be set in the configuration dialog.
Figure 4-28: Power dynamics limit settings
User Manual 1178.5689.02 ─ 12 325

GUI Reference
Remote command:
CONFigure:NIOT:MEAS:MEValuation:LIMit:PDYNamics
Access: "Config" hotkey > "Generator Shortcut" setting.

This section configures a shortcut softkey that provides a fast way to access the GPRF
generator from the measurement.
The setting is a common measurement setting. It has the same value in all NB-IoT
measurements (NPRACH measurement and multi-evaluation measurement).
Generator Shortcut
Selects a GPRF generator instance. Softkeys for the selected instance are added to
the softkey panel.
4.3.8 Additional Softkeys and Hotkeys
The measurement provides some softkey/hotkey combinations which have no equiva-

lent in the configuration dialog. Most of these hotkeys provide display configurations
(like diagram scaling). They are self-explanatory and do not have any remote-control
commands assigned.
The remaining softkeys > hotkeys are described below.
The softkeys "Signaling Parameter" and "NB-IoT Signaling" are displayed only if the
combined signal path scenario is active and are provided by the "NB-IoT Signaling"
application selected as master application. See also "Scenario = Combined Signal
Path" on page 306.
The softkeys "ARB / List Mode" and "GPRF Generator" are displayed only if the stand-
alone scenario is active and the generator shortcut is enabled, see Chapter 4.3.7,
"Shortcut Configuration", on page 326.
While one of the signaling or generator softkeys is selected, the "Config" hotkey opens
the configuration dialog of the generator or signaling application, not the configuration
dialog of the measurement.
Multi Evaluation, NPRACH > Assign Views

Selects the view types to be displayed in the overview. The R&S CMW does not evalu-
ate the results for disabled views. Therefore, limiting the number of assigned views can
speed up the measurement.
Remote command:
CONFigure:NIOT:MEAS:MEValuation:RESult[:ALL]
CONFigure:NIOT:MEAS:MEValuation:RESult:PDYNamics etc.
User Manual 1178.5689.02 ─ 12 326

GUI Reference
CONFigure:NIOT:MEAS:PRACh:RESult[:ALL]
CONFigure:NIOT:MEAS:PRACh:RESult:PVPReamble etc.
Signaling Parameter > ...

Provides access to the most essential settings of the "NB-IoT Signaling" application.
Remote command:
Use the commands of the signaling application.
NB-IoT Signaling
Select this softkey and press [ON | OFF] to turn the downlink signal transmission on or
off. Alternatively, right-click the softkey.
Press the softkey two times (select it and press it again) to switch to the signaling
application.
Remote command:
Use the commands of the signaling application.
ARB / List Mode > ...

Provides access to the most important ARB and list mode settings of the GPRF gener-
ator.
Remote command:
Use the commands of the GPRF generator.
GPRF Generator
Select this softkey and press [ON | OFF] to turn the GPRF generator on or off. Alterna-
tively, right-click the softkey.
Press the softkey two times (select it and press it again) to switch to the generator
application.
The hotkeys assigned to this softkey provide access to the most important GPRF gen-
erator settings.
Remote command:
Use the commands of the GPRF generator.
Suppress "Cell Off" Message
This setting is located in the configuration tree. It is only visible if the combined signal
path scenario is active.
The checkbox suppresses a warning that is displayed if the "... Signaling" softkey is
selected and the cell signal is on and you press [ON | OFF]. The warning asks you
whether you really want to switch off the cell signal.
Remote command:
n/a
User Manual 1178.5689.02 ─ 12 327

Programming
4.4 Programming
The following sections provide programming examples for the NB-IoT multi-evaluation
measurement.
● General Examples.................................................................................................328
● Using the List Mode.............................................................................................. 332
4.4.1 General Examples
The NB-IoT multi-evaluation measurement is programmed as follows:

● The measurement is controlled by SCPI commands with the following syn-
tax: ...NIOT:MEAS:MEValuation...
● Use general commands of the type ...:NIOT:MEAS... (no :MEValuation
mnemonic) to define the signal routing and perform RF and analyzer settings.
● After a *RST, the measurement is switched off. Use
READ:NIOT:MEAS:MEValuation...? to initiate a single-shot measurement and
retrieve the results. You can also start the measurement using
INIT:NIOT:MEAS:MEValuation and retrieve the results using
FETCh:NIOT:MEAS:MEValuation...?.
● For synchronization and proper decoding, some UE signal settings must be in
accordance with the measured signal; see Chapter 4.4.1.2, "Specifying Required
4.4.1.1 Specifying General and Common Measurement Settings
// *****************************************************************************
// *****************************************************************************
*RST; *OPC?
*CLS; *OPC?
// *****************************************************************************
// Define signal routing and perform RF and analyzer settings:
// Center frequency 1850 MHz, frequency offset 1 kHz, peak power -2 dBm,
// no user margin and 1 dB mixer level offset.
// *****************************************************************************
ROUTe:NIOT:MEAS:SCENario:SALone RF1C, RX1
CONFigure:NIOT:MEAS:RFSettings:EATTenuation 2
CONFigure:NIOT:MEAS:BAND OB2
CONFigure:NIOT:MEAS:RFSettings:FREQuency 1850E+6
CONFigure:NIOT:MEAS:RFSettings:FOFFset 1000
CONFigure:NIOT:MEAS:RFSettings:ENPower -2
CONFigure:NIOT:MEAS:RFSettings:UMARgin 0
CONFigure:NIOT:MEAS:RFSettings:MLOFfset 1
User Manual 1178.5689.02 ─ 12 328

Programming
4.4.1.2 Specifying Required Settings
// *****************************************************************************
// Specify required UE signal settings:
// subcarrier spacing, NPUSCH format, resource allocation, physical cell ID,
// delta sequence shift value, frequency sync range, modulation scheme.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:SCSPacing S15K
CONFigure:NIOT:MEAS:MEValuation:NPFormat F1
CONFigure:NIOT:MEAS:MEValuation:SUBCarrier 3, 6
CONFigure:NIOT:MEAS:MEValuation:NRUNits NRU04
CONFigure:NIOT:MEAS:MEValuation:NREPetitions NR2
CONFigure:NIOT:MEAS:MEValuation:PLCid 10
CONFigure:NIOT:MEAS:MEValuation:DSS 5
CONFigure:NIOT:MEAS:MEValuation:FSYRange HIGH
CONFigure:NIOT:MEAS:MEValuation:MODulation:MSCHeme QPSK
4.4.1.3 Specifying Measurement-Specific Settings
// *****************************************************************************
// Define stop condition (stop on limit failure), error handling, timeout and
// number of slots per captured sequence.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:SCONdition SLFail
CONFigure:NIOT:MEAS:MEValuation:MOEXception ON
CONFigure:NIOT:MEAS:MEValuation:TOUT 3600
CONFigure:NIOT:MEAS:MEValuation:NSLots 20
// *****************************************************************************
// Specify modulation measurement settings: 20 statistics cycles, no exclusion
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:SCOunt:MODulation 20
CONFigure:NIOT:MEAS:MEValuation:MODulation:EEPeriods:NPUSch:LEADing OFF
CONFigure:NIOT:MEAS:MEValuation:MODulation:EEPeriods:NPUSch:LAGGing OFF
// *****************************************************************************
// Specify spectrum measurement settings: measurement length of 30 slots,
// OBW mode and for ACLR measure all adjacent channels.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:SCOunt:SPECtrum:ACLR 30
CONFigure:NIOT:MEAS:MEValuation:SCOunt:SPECtrum:SEMask 30
CONFigure:NIOT:MEAS:MEValuation:SPECtrum:SEMask:OBWMode BW99
CONFigure:NIOT:MEAS:MEValuation:SPECtrum:ACLR:ENABle ON, ON
// *****************************************************************************
// Specify power measurement settings: 30 statistics cycles
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:SCOunt:POWer 30
User Manual 1178.5689.02 ─ 12 329

Programming
4.4.1.4 Configuring the Trigger System
// *****************************************************************************
// Set source, slope, trigger level, delay, timeout, minimum trigger gap.
// *****************************************************************************
TRIGger:NIOT:MEAS:MEValuation:SOURce 'IF Power'
TRIGger:NIOT:MEAS:MEValuation:SLOPe FEDGe
TRIGger:NIOT:MEAS:MEValuation:THReshold -30
TRIGger:NIOT:MEAS:MEValuation:DELay 0.0001
TRIGger:NIOT:MEAS:MEValuation:TOUT 1
TRIGger:NIOT:MEAS:MEValuation:MGAP 0.003
4.4.1.5 Specifying Limits
// *****************************************************************************
// Define modulation limits.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:LIMit:EVMagnitude 20, 40
CONFigure:NIOT:MEAS:MEValuation:LIMit:MERRor 20, OFF
CONFigure:NIOT:MEAS:MEValuation:LIMit:PERRor 20, OFF
CONFigure:NIOT:MEAS:MEValuation:LIMit:FERRor ON, 0.15, 0.1
CONFigure:NIOT:MEAS:MEValuation:LIMit:IQOFfset ON, -26, -21, -11
CONFigure:NIOT:MEAS:MEValuation:LIMit:IBE ON, -20, -60, -27
CONFigure:NIOT:MEAS:MEValuation:LIMit:IBE:IQOFfset -26, -21, -11
// *****************************************************************************
// Define ACLR limits.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:LIMit:ACLR:GSM 20, -50
CONFigure:NIOT:MEAS:MEValuation:LIMit:ACLR:UTRA 35, -50
// *****************************************************************************
// Define spectrum emission limits.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:OBWLimit 199E+3
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:LIMit1 ON,1.5E+4,8.5E+4,23.0,1.0
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:LIMit2 ON,1.1E+5,1.3E+5,-4.5,-5.5
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:LIMit3 ON,1.6E+5,2.8E+5,-8.6,-25.4
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:LIMit4 ON,3.1E+5,4.8E+5,-28,-33
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:LIMit5 ON,5.1E+5,1.7E+6,-33,-33
// *****************************************************************************
// Define power dynamics limits.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:LIMit:PDYNamics ON, 26, 20, -48.8
User Manual 1178.5689.02 ─ 12 330

Programming
4.4.1.6 Performing Measurements
// *****************************************************************************
// Enable all measurements.
// *****************************************************************************
CONF:NIOT:MEAS:MEValuation:RESult:ALL ON,ON,ON,ON,ON,ON,ON,ON,ON,ON
// *****************************************************************************
// Start a measurement, return average EVM bar graph values.
// Start a measurement, return average EVM bar graph values, magnitude error
// bar graph values. maximum magnitude error and phase bar graph values.
// *****************************************************************************
INIT:NIOT:MEAS:MEValuation
Pause 5000
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:AVERage?
FETCh:NIOT:MEAS:MEValuation:MERRor:CURRent?
FETCh:NIOT:MEAS:MEValuation:MERRor:MAXimum?
FETCh:NIOT:MEAS:MEValuation:PERRor:MAXimum?
// *****************************************************************************
// Query modulation traces, bar graph values and statistical values
// obtained in the last measurement, without re-starting the measurement.
// *****************************************************************************
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:MAXimum?
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:MAXimum?
FETCh:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:MAXimum?
FETCh:NIOT:MEAS:MEValuation:MERRor:AVERage?
FETCh:NIOT:MEAS:MEValuation:MERRor:MAXimum?
FETCh:NIOT:MEAS:MEValuation:PERRor:AVERage?
FETCh:NIOT:MEAS:MEValuation:PERRor:MAXimum?
FETCh:NIOT:MEAS:MEValuation:TRACe:IQ?
FETCh:NIOT:MEAS:MEValuation:MODulation:CURRent?
FETCh:NIOT:MEAS:MEValuation:MODulation:EXTReme?
// *****************************************************************************
// Query inband emission results.
// *****************************************************************************
FETCh:NIOT:MEAS:MEValuation:TRACe:IEMissions?
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:AVERage?
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:EXTReme:SCINdex?
// *****************************************************************************
// Query spectrum emission results.
// *****************************************************************************
FETCh:NIOT:MEAS:MEValuation:TRACe:SEMask:AVERage?
FETCh:NIOT:MEAS:MEValuation:TRACe:SEMask:MAXimum?
FETCh:NIOT:MEAS:MEValuation:SEMask:AVERage?
FETCh:NIOT:MEAS:MEValuation:SEMask:EXTReme?
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:ALL?
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:MINimum:POSitiv?
User Manual 1178.5689.02 ─ 12 331

Programming
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:MINimum:NEGativ?
// *****************************************************************************
// Query ACLR results.
// *****************************************************************************
FETCh:NIOT:MEAS:MEValuation:TRACe:ACLR:CURRent?
FETCh:NIOT:MEAS:MEValuation:TRACe:ACLR:AVERage?
FETCh:NIOT:MEAS:MEValuation:ACLR:CURRent?
FETCh:NIOT:MEAS:MEValuation:ACLR:AVERage?
// *****************************************************************************
// Query power monitor results.
// *****************************************************************************
FETCh:NIOT:MEAS:MEValuation:TRACe:PMONitor?
// *****************************************************************************
// Query power dynamics results.
// *****************************************************************************
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:AVERage?
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:MAXimum?
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:AVERage?
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:MAXimum?
FETCh:NIOT:MEAS:MEValuation:PDYNamics:AVERage?
FETCh:NIOT:MEAS:MEValuation:PDYNamics:MINimum?
FETCh:NIOT:MEAS:MEValuation:PDYNamics:MAXimum?
// *****************************************************************************
// Query limit check results.
// *****************************************************************************
CALCulate:NIOT:MEAS:MEValuation:ACLR:CURRent?
CALCulate:NIOT:MEAS:MEValuation:SEMask:CURRent?
CALCulate:NIOT:MEAS:MEValuation:MODulation:CURRent?
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:AVERage?
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:MINimum?
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:MAXimum?
4.4.2 Using the List Mode
The NB-IoT multi-evaluation list mode is programmed as follows:

tax: ...NIOT:MEAS:MEValuation:LIST...
● Use general commands of the type ...:NIOT:MEAS... (no :MEValuation
mnemonic) to define the signal routing and perform RF and analyzer settings.
● After a *RST, the measurement is switched off and the list mode is disabled. Use
CONFigure:NIOT:MEAS:MEValuation:LIST ON to enable the list mode and
INIT:NIOT:MEAS:MEValuation to initiate a single-shot measurement.
User Manual 1178.5689.02 ─ 12 332

Programming
● Use FETCh:NIOT:MEAS:MEValuation:LIST:...? commands to retrieve the

results.
Speeding up list mode measurements

List mode tests are often used in production lines. The same tests are repeated for dif-
ferent UEs. Optimizing the test duration is important.
Consider the following rules to minimize the test duration:
● Reduce the number and size of the segments and the statistical length as far as
possible for your use case.
● Enable only the results that you need / disable the other result calculations.
● To reset the system repeatedly, use partial reset commands instead of the global
reset command *RST.
Example: Use SYSTem:RESet 'NB-IoT Meas1' to reset the NB-IoT measure-
ment instance 1.
4.4.2.1 Specifying Global Measurement Settings
// *****************************************************************************
// Reset
// *****************************************************************************
SYSTem:RESet 'NB-IoT Meas1'; *OPC?
*CLS; *OPC?
// *****************************************************************************
// Define signal routing and external attenuation.
// *****************************************************************************
// *****************************************************************************
// Specify required UE signal settings not configurable per segment:
// subcarrier spacing, physical cell ID, delta sequence shift value.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:SCSPacing S15K
CONFigure:NIOT:MEAS:MEValuation:PLCid 10
CONFigure:NIOT:MEAS:MEValuation:DSS 5
4.4.2.2 Specifying List Mode Settings
// *****************************************************************************
// Segment 1, NPUSCH: format F1, 1 RU, 1 repetition, 1 SC - means 16 slots
// segment length 18 slots, power 1 dBm, frequency 1.95 GHz
// *****************************************************************************
CONF:NIOT:MEAS:MEV:LIST:SEGM1:SET 18,1,OB1,1.95E+9,F1,1,0,NRU01,NR1,ON,0
// *****************************************************************************
// Segment 2, NPUSCH: format F1, 1 RU, 2 repetitions, 12 SC - means 4 slots
User Manual 1178.5689.02 ─ 12 333

Programming
// segment length 6 slots, power 3 dBm, frequency 1.95 GHz

// *****************************************************************************
CONF:NIOT:MEAS:MEV:LIST:SEGM2:SET 6,3,OB1,1.95E+9,F1,12,0,NRU01,NR2,IFPower,0
// *****************************************************************************
// Enable modulation results except phase error for both segments.
// Set statistical length to entire NPUSCH duration.
// *****************************************************************************
CONF:NIOT:MEAS:MEValuation:LIST:SEGMent1:MODulation 16,ON,ON,ON,OFF,ON,QPSK
CONF:NIOT:MEAS:MEValuation:LIST:SEGMent2:MODulation 4,ON,ON,ON,OFF,ON,QPSK
// *****************************************************************************
// Enable all spectrum emission results for segment 2.
// Enable the GSM ACLR results for segment 2 (no UTRA results).
// Set statistical length to entire NPUSCH duration.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent2:SEMask 4,ON
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent2:ACLR 4,ON,OFF,ON
// *****************************************************************************
// Select both segments for measurement and evaluate retrigger flags.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:LIST:LRANge 1,2
TRIGger:NIOT:MEAS:MEValuation:LIST:MODE SEGMent
// *****************************************************************************
// Enable the list mode.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:LIST ON
4.4.2.3 Performing Single-Shot Measurements
// *****************************************************************************
// Start single-shot measurement.
// Return the individual segment reliability indicators.
// *****************************************************************************
FETCh:NIOT:MEAS:MEValuation:LIST:SRELiability?
// *****************************************************************************
// Return average and extreme modulation results.
// Return extreme inband emission results.
// *****************************************************************************
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent1:MODulation:AVERage?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent2:MODulation:AVERage?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent1:MODulation:EXTReme?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent2:MODulation:EXTReme?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent1:IEMission:MARGin:EXTReme?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent2:IEMission:MARGin:EXTReme?
User Manual 1178.5689.02 ─ 12 334

Command Reference
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent1:IEMission:MARGin:EXTReme:SCINdex?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent2:IEMission:MARGin:EXTReme:SCINdex?
// *****************************************************************************
// Return average and extreme spectrum emission results.
// Return spectrum emission margins: X- and Y-values of minimum margins and
// Y-values of all margins.
// *****************************************************************************
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent2:SEMask:AVERage?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent2:SEMask:EXTReme?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent2:SEMask:MARGin:MINimum:POSitiv?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent2:SEMask:MARGin:MINimum:NEGativ?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent2:SEMask:MARGin:ALL?
// *****************************************************************************
// Return current and average ACLR results.
// *****************************************************************************
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent2:ACLR:CURRent?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent2:ACLR:AVERage?
// *****************************************************************************
// Select segment no. 2 as offline segment (and implicitly enable the
// offline mode). Restart the measurement to calculate all results in
// segment 2. Go to local to view the results.
// *****************************************************************************
CONFigure:NIOT:MEAS:MEValuation:LIST:OSINdex 2
&GTL

The following sections provide detailed reference information on the remote control
commands of the NB-IoT multi-evaluation measurement and the general commands
applicable to all NB-IoT measurements.
● General Measurement Settings............................................................................ 342
● Multi-Evaluation Measurement Commands.......................................................... 347
● Combined Signal Path Commands....................................................................... 407
User Manual 1178.5689.02 ─ 12 335

Command Reference
4.5.1.1 MEAS
MEAS is used as abbreviation of "MEASurement<instance>". For better readability,

command reference.
measurement application. It can be omitted if the instrument supports only one
instance, or to address the first instance.
4.5.1.2 FETCh, READ and CALCulate Commands
All commands are used to retrieve measurement results:

● FETCh... returns the results of the measurement cycle after the cycle is com-
plete. Before sending a FETCh..., start the measurement via an INITiate....
● READ... starts a new single-shot measurement and returns the results.
● CALCulate... returns one limit check result per FETCh result:
– OK: The FETCh result is located within the limits or no limit has been defined/
enabled for this result.
– ULEU ("User limit exceeded upper"): An upper limit is violated. The FETCh
result is located above the limit.
– ULEL ("User limit exceeded lower"): A lower limit is violated. The FETCh result
is located below the limit.
4.5.1.3 Current and Statistical Results
The measurement is repeated according to the selected statistic count and repetition
mode. Consecutive measurement values are stored and used to calculate statistical
results.
Commands for result query often contain a mnemonic that indicates which results are
returned: CURRent, AVERage, EXTReme, MINimum, MAXimum or SDEViation.
4.5.1.4 Values for RF Path Selection
To select an RF input path, you must specify an RF connector and an RX module (con-
verter).
Which connectors and modules can be specified in a command, depends on the instal-
led hardware, the test setup and the active subinstrument or instance .
This chapter lists all values available for path selection. Depending on your configura-
tion, only a subset is relevant for you. Virtual connector names are only relevant for
setting commands. Queries return the physical connector names.
Additional information is available in the base unit documentation. It describes typical
instrument configurations with the allowed RF connector - TX/RX module combinations
and the mapping of virtual connector names to physical connectors.
User Manual 1178.5689.02 ─ 12 336

Command Reference
Single R&S CMW500 / 270 / 290

RF path selection values:
● RX module:
RX1 | RX2 | RX3 | RX4
● RX connector:
One R&S CMW plus one R&S CMWS

● RX module:
RX1 | RX2 | RX3 | RX4
● RX connector:
R11 | R12 | R13 | R14 | R15 | R16 | R17 | R18
R21 | R22 | R23 | R24 | R25 | R26 | R27 | R28
R31 | R32 | R33 | R34 | R35 | R36 | R37 | R38
RA1 | RA2 | RA3 | RA4 | RA5 | RA6 | RA7 | RA8
RB1 | RB2 | RB3 | RB4
R<m><n>: R&S CMWS connector <m>.<n>
RA<n>: virtual name for R1<n> / R3<n>
RB<n>: virtual name for R2<n> / R2<n+4>
CMWflexx setup with R&S CMWC and several R&S CMW500

● RX module:
RX<a>: CMW <a>, RX 
Example RX34: RX module 4 of CMW 3
● RX connector:
Example R34C: RF 4 COM of CMW 3
For CMW 1, you can alternatively use the single-CMW RF path selection values.
4.5.1.5 Keywords
● Command usage
User Manual 1178.5689.02 ─ 12 337

Command Reference
● Parameter usage
● Parameter type
In list mode, a zero reliability indicator indicates that the results in all measured seg-
ments are valid. A non-zero value indicates that an error occurred in at least one of the
measured segments.
● 0 ("No Error"):
ble memory.
User Manual 1178.5689.02 ─ 12 338

Command Reference
detected.
● 9 ("Uncal"):
not active.
frequency.
User Manual 1178.5689.02 ─ 12 339

Command Reference
mode.
reliable.
maximum.
● 51 ("No Reply"):
User Manual 1178.5689.02 ─ 12 340

Command Reference
nal.
lation type.
schwarz.com.
User Manual 1178.5689.02 ─ 12 341

Command Reference

parameter settings.
4.5.2 General Measurement Settings
The commands valid for all NB-IoT measurements are divided into the groups listed
below.
● Signal Routing.......................................................................................................342
● Analyzer Settings.................................................................................................. 344
4.5.2.1 Signal Routing
The following commands configure the scenario, select the input path for the measured
signal and define an external attenuation value.
ROUTe:NIOT:MEAS:SCENario:SALone....................................................................... 342
ROUTe:NIOT:MEAS:SCENario:CSPath....................................................................... 343
ROUTe:NIOT:MEAS:SCENario:MAPRotocol.................................................................343
ROUTe:NIOT:MEAS:SCENario?..................................................................................343
ROUTe:NIOT:MEAS?................................................................................................. 344
CONFigure:NIOT:MEAS:RFSettings:EATTenuation....................................................... 344
ROUTe:NIOT:MEAS:SCENario:SALone <RXConnector>, <RFConverter>

Activates the standalone scenario and selects the RF input path for the measured RF
signal.
For possible connector and converter values, see Chapter 4.5.1.4, "Values for RF Path
Selection", on page 336.
Parameters:
<RFConverter> RX module for the input path
Example: See Specifying General and Common Measurement Settings
Manual operation: See "Scenario = StandAlone" on page 306
User Manual 1178.5689.02 ─ 12 342

Command Reference
ROUTe:NIOT:MEAS:SCENario:CSPath <Master>[, <Carrier>]

Activates the combined signal path scenario and selects the master application and
carrier. The master controls most signal routing settings, analyzer settings and some
measurement control settings while the combined signal path scenario is active.
Parameters:
<Master> string
String parameter selecting the master application
Example: 'NB-IoT Sig1' or 'NB-IoT Sig2'
<Carrier> string
For future use
Manual operation: See "Scenario = Combined Signal Path" on page 306
ROUTe:NIOT:MEAS:SCENario:MAPRotocol [<Controler>]
Activates the Measure@ProtocolTest scenario and optionally selects the controlling
protocol test application.
The signal routing and analyzer settings are ignored by the measurement application.
Configure the corresponding settings within the protocol test application used in paral-
lel.
Setting parameters:
<Controler> string
String parameter selecting the protocol test application
Example: 'Protocol Test1'
Usage: Event
Manual operation: See "Scenario = Measure@ProtocolTest" on page 307
Returns the active scenario.
Return values:
<Scenario> SALone | SALone | CSPath | MAPRotocol
SALone: Standalone (non-signaling)
CSPath: Combined signal path
MAPRotocol: Measure at protocol test
Usage: Query only
User Manual 1178.5689.02 ─ 12 343

Command Reference
ROUTe:NIOT:MEAS?
Returns the configured routing settings.
For possible connector and converter values, see Chapter 4.5.1.4, "Values for RF Path
Selection", on page 336.
Return values:
<Scenario> SALone | SALone | CSPath | MAPRotocol
SALone: Standalone (non-signaling)
CSPath: Combined signal path
MAPRotocol: Measure at protocol test
<Controller> string
Controlling application for scenario CSPath or MAPRotocol
<RFConverter> RX module for the input path
Usage: Query only
CONFigure:NIOT:MEAS:RFSettings:EATTenuation <RFinputExtAtt>
input connector.
For the combined signal path scenario, use CONFigure:NIOT:SIGN:
RFSettings:EATTenuation:INPut.
Parameters:
<RFinputExtAtt> numeric
*RST: 0 dB
Default unit: dB
Manual operation: See "External Attenuation (Input)" on page 307
4.5.2.2 Analyzer Settings
The following commands configure the RF input path.

CONFigure:NIOT:MEAS:BAND................................................................................... 345
CONFigure:NIOT:MEAS:RFSettings:FREQuency..........................................................345
CONFigure:NIOT:MEAS:RFSettings:FOFFset.............................................................. 346
User Manual 1178.5689.02 ─ 12 344

Command Reference
CONFigure:NIOT:MEAS:RFSettings:ENPower..............................................................346
CONFigure:NIOT:MEAS:RFSettings:UMARgin............................................................. 346
CONFigure:NIOT:MEAS:RFSettings:MLOFfset............................................................. 347
CONFigure:NIOT:MEAS:BAND <Band>
Selects the operating band (OB).
For the combined signal path scenario, use CONFigure:NIOT:SIGN:BAND.
Parameters:
OB74 | OB85
*RST: OB1
Firmware/Software: V3.5.10, some bands added in later versions
Manual operation: See "Band / Channel / Frequency" on page 308
CONFigure:NIOT:MEAS:RFSettings:FREQuency <AnalyzerFreq>
Selects the center frequency of the RF analyzer.
Using the unit CH, the frequency can be set via the channel number. The allowed
channel number range depends on the operating band, see Chapter 4.2.6.3, "Fre-
quency Bands", on page 289.
RFSettings:CHANnel:UL.
The supported frequency range depends on the instrument model and the available
options. The supported range can be smaller than stated here. Refer to the preface of
your model-specific base unit manual.
Parameters:
<AnalyzerFreq> numeric
Range: 70E+6 Hz to 6E+9 Hz
*RST: 1.95E+9 Hz
Default unit: Hz
Manual operation: See "Band / Channel / Frequency" on page 308
User Manual 1178.5689.02 ─ 12 345

Command Reference
CONFigure:NIOT:MEAS:RFSettings:FOFFset <Offset>
Specifies a positive or negative frequency offset to be added to the carrier center fre-
quency (CONFigure:NIOT:MEAS:RFSettings:FREQuency).
RFSettings:FOFFset:UL.
Parameters:
<Offset> numeric
*RST: 0 Hz
Default unit: Hz
CONFigure:NIOT:MEAS:RFSettings:ENPower <ExpNomPow>
Sets the expected nominal power of the measured RF signal.
For the combined signal path scenario, use:
● CONFigure:NIOT:SIGN:RFSettings:ENPMode
● CONFigure:NIOT:SIGN:RFSettings:ENPower
Parameters:
<ExpNomPow> numeric
The range of the expected nominal power can be calculated as
follows:
Range (Expected Nominal Power) = Range (Input Power) +
External Attenuation - User Margin
*RST: 0 dBm
Default unit: dBm
Manual operation: See "Expected Nominal Power" on page 308
CONFigure:NIOT:MEAS:RFSettings:UMARgin <UserMargin>
Sets the margin that the measurement adds to the expected nominal power to deter-
mine the reference power. The reference power minus the external input attenuation
must be within the power range of the selected input connector. Refer to the data
sheet.
RFSettings:UMARgin.
User Manual 1178.5689.02 ─ 12 346

Command Reference
Parameters:
<UserMargin> numeric
Range: 0 dB to (55 dB + external attenuation - expected
nominal power)
*RST: 0 dB
Default unit: dB
Manual operation: See "User Margin" on page 309
CONFigure:NIOT:MEAS:RFSettings:MLOFfset <MixLevOffset>
Varies the input level of the mixer in the analyzer path.
RFSettings:MLOFfset.
Parameters:
<MixLevOffset> numeric
*RST: 0 dB
Default unit: dB
Manual operation: See "Mixer Level Offset" on page 309
4.5.3 Multi-Evaluation Measurement Commands
The commands for the NB-IoT multi-evaluation measurement are divided into the
groups listed below. The general measurement settings also affect the measurement,
see Chapter 4.5.2, "General Measurement Settings", on page 342.
● Enabling Results and Views..................................................................................349
● Measurement Control Parameters........................................................................ 351
● List Mode Settings.................................................................................................360
● Limits Modulation.................................................................................................. 369
● Limits Spectrum.................................................................................................... 374
● Limits Power..........................................................................................................376
● EVM Results (Traces)........................................................................................... 377
● Magnitude Error Results (Traces)......................................................................... 379
● Phase Error Results (Traces)................................................................................380
● Inband Emission Results.......................................................................................380
● Spectrum Emission Results.................................................................................. 382
● ACLR Spectrum Results....................................................................................... 386
User Manual 1178.5689.02 ─ 12 347

Command Reference
● I/Q Constellation Results.......................................................................................388

● Power Monitor Results.......................................................................................... 389
● Power Dynamics Results...................................................................................... 389
● Modulation Results (Single Values)...................................................................... 392
● List Mode Results..................................................................................................396
4.5.3.1 Measurement Control and States
ment state.
INITiate:NIOT:MEAS:MEValuation............................................................................... 348
STOP:NIOT:MEAS:MEValuation..................................................................................348
ABORt:NIOT:MEAS:MEValuation................................................................................ 348
FETCh:NIOT:MEAS:MEValuation:STATe?.................................................................... 348
FETCh:NIOT:MEAS:MEValuation:STATe:ALL?............................................................. 349
INITiate:NIOT:MEAS:MEValuation
STOP:NIOT:MEAS:MEValuation
ABORt:NIOT:MEAS:MEValuation
"RUN" state.
surement.
released.
Example: See Performing Measurements
Usage: Event
Manual operation: See "Multi Evaluation (Softkey)" on page 291
FETCh:NIOT:MEAS:MEValuation:STATe?
User Manual 1178.5689.02 ─ 12 348

Command Reference
Return values:
<MeasStatus> OFF | RUN | RDY
*RST: OFF
Usage: Query only
FETCh:NIOT:MEAS:MEValuation:STATe:ALL?
Return values:
*RST: OFF
("queued")
Usage: Query only
4.5.3.2 Enabling Results and Views
The following commands select the evaluated results and the displayed views.
User Manual 1178.5689.02 ─ 12 349

Command Reference
CONFigure:NIOT:MEAS:MEValuation:RESult[:ALL].......................................................350
CONFigure:NIOT:MEAS:MEValuation:RESult:EVMagnitude...........................................351
CONFigure:NIOT:MEAS:MEValuation:RESult:MERRor..................................................351
CONFigure:NIOT:MEAS:MEValuation:RESult:PERRor.................................................. 351
CONFigure:NIOT:MEAS:MEValuation:RESult:IEMissions.............................................. 351
CONFigure:NIOT:MEAS:MEValuation:RESult:IQ...........................................................351
CONFigure:NIOT:MEAS:MEValuation:RESult:TXM....................................................... 351
CONFigure:NIOT:MEAS:MEValuation:RESult:SEMask.................................................. 351
CONFigure:NIOT:MEAS:MEValuation:RESult:ACLR..................................................... 351
CONFigure:NIOT:MEAS:MEValuation:RESult:PMONitor................................................351
CONFigure:NIOT:MEAS:MEValuation:RESult:PDYNamics.............................................351
CONFigure:NIOT:MEAS:MEValuation:RESult[:ALL] <EVM>, <MagnitudeError>,

<PhaseError>, <InbandEmissions>, <IQ>, <TXMeasurement>, <SpecEmMask>,
<ACLR>[, <PowerMonitor>, <PowerDynamics>]
Enables or disables the evaluation of results and shows or hides the views in the multi-
evaluation measurement. This command combines most other
CONFigure:NIOT:MEAS:MEValuation:RESult... commands.
Parameters:
<EVM> OFF | ON
Error vector magnitude
OFF: Do not evaluate results, hide the view
ON: Evaluate results and show the view
*RST: ON
<MagnitudeError> OFF | ON
*RST: ON
<PhaseError> OFF | ON
*RST: OFF
<InbandEmissions> OFF | ON
*RST: ON
<IQ> OFF | ON
I/Q constellation diagram
*RST: OFF
<TXMeasurement> OFF | ON
TX measurement statistical overview
*RST: ON
<SpecEmMask> OFF | ON
Spectrum emission mask
*RST: ON
<ACLR> OFF | ON
Adjacent channel leakage power ratio
*RST: ON
User Manual 1178.5689.02 ─ 12 350

Command Reference
<PowerMonitor> OFF | ON
*RST: ON
<PowerDynamics> OFF | ON
*RST: OFF
Firmware/Software: V3.5.10, V3.7.60: reset values changed (formerly all ON)
Manual operation: See "Multi Evaluation, NPRACH > Assign Views" on page 326
CONFigure:NIOT:MEAS:MEValuation:RESult:EVMagnitude <Enable>
CONFigure:NIOT:MEAS:MEValuation:RESult:MERRor <Enable>
CONFigure:NIOT:MEAS:MEValuation:RESult:PERRor <Enable>
CONFigure:NIOT:MEAS:MEValuation:RESult:IEMissions <Enable>
CONFigure:NIOT:MEAS:MEValuation:RESult:IQ <Enable>
CONFigure:NIOT:MEAS:MEValuation:RESult:TXM <Enable>
CONFigure:NIOT:MEAS:MEValuation:RESult:SEMask <Enable>
CONFigure:NIOT:MEAS:MEValuation:RESult:ACLR <Enable>
CONFigure:NIOT:MEAS:MEValuation:RESult:PMONitor <Enable>
CONFigure:NIOT:MEAS:MEValuation:RESult:PDYNamics <Enable>
Enables or disables the evaluation of results and shows or hides the views in the multi-
evaluation measurement.
Mnemonic View type Mnemonic View type
EVMagnitude Error vector magnitude TXM TX meas. statistical overview
MERRor Magnitude error SEMask Spectrum emission mask
PERRor Phase error ACLR Adj. channel leakage power ratio
IEMissions Inband emissions PMONitor Power monitor
IQ I/Q constellation diagram PDYNamics Power dynamics
For reset values, see CONFigure:NIOT:MEAS:MEValuation:RESult[:ALL].

Parameters:
<Enable> OFF | ON
*RST: ON, (OFF for IQ, PDYNamics, PERRor)
Firmware/Software: V3.5.10, V3.7.60: several reset values changed (formerly all ON)
4.5.3.3 Measurement Control Parameters
The following commands define general measurement control parameters for the multi-
evaluation measurement.
User Manual 1178.5689.02 ─ 12 351

Command Reference
CONFigure:NIOT:MEAS:MEValuation:TOUT................................................................ 352
CONFigure:NIOT:MEAS:MEValuation:REPetition..........................................................353
CONFigure:NIOT:MEAS:MEValuation:SCONdition........................................................ 353
CONFigure:NIOT:MEAS:MEValuation:MMODe............................................................. 353
CONFigure:NIOT:MEAS:MEValuation:MOEXception..................................................... 354
CONFigure:NIOT:MEAS:MEValuation:NSLots.............................................................. 354
CONFigure:NIOT:MEAS:MEValuation:SCSPacing.........................................................354
CONFigure:NIOT:MEAS:MEValuation:NPFormat.......................................................... 354
CONFigure:NIOT:MEAS:MEValuation:SUBCarrier.........................................................355
CONFigure:NIOT:MEAS:MEValuation:NRUNits............................................................ 355
CONFigure:NIOT:MEAS:MEValuation:NREPetitions......................................................356
CONFigure:NIOT:MEAS:MEValuation:PLCid................................................................ 356
CONFigure:NIOT:MEAS:MEValuation:DSS.................................................................. 356
CONFigure:NIOT:MEAS:MEValuation:FSYRange......................................................... 357
CONFigure:NIOT:MEAS:MEValuation:MODulation:MSCHeme....................................... 357
CONFigure:NIOT:MEAS:MEValuation:MODulation:EEPeriods:NPUSch:LEADing.............357
CONFigure:NIOT:MEAS:MEValuation:MODulation:EEPeriods:NPUSch:LAGGing............ 358
CONFigure:NIOT:MEAS:MEValuation:SCOunt:MODulation............................................358
CONFigure:NIOT:MEAS:MEValuation:SCOunt:SPECtrum:SEMask................................ 358
CONFigure:NIOT:MEAS:MEValuation:SCOunt:SPECtrum:ACLR....................................359
CONFigure:NIOT:MEAS:MEValuation:SPECtrum:ACLR:ENABle.................................... 359
CONFigure:NIOT:MEAS:MEValuation:SPECtrum:SEMask:OBWMode............................ 359
CONFigure:NIOT:MEAS:MEValuation:SCOunt:POWer.................................................. 360
CONFigure:NIOT:MEAS:MEValuation:TOUT <Timeout>
reached.
Parameters:
<Timeout> numeric
Default unit: s
Example: See Specifying Measurement-Specific Settings
User Manual 1178.5689.02 ─ 12 352

Command Reference
CONFigure:NIOT:MEAS:MEValuation:REPetition <Repetition>
Specifies the repetition mode of the measurement. The repetition mode specifies
whether the measurement is stopped after a single shot or repeated continuously. Use
CONFigure:..:MEAS:...:SCOunt to determine the number of measurement
intervals per single shot.
Parameters:
*RST: SING
CONFigure:NIOT:MEAS:MEValuation:SCONdition <StopCondition>
Qualifies whether the measurement is stopped after a failed limit check or continued.
SLFail means that the measurement is stopped and reaches the RDY state when one
of the results exceeds the limits.
Parameters:
<StopCondition> NONE | SLFail
NONE: Continue measurement irrespective of the limit check
SLFail: Stop measurement on limit failure
*RST: NONE
CONFigure:NIOT:MEAS:MEValuation:MMODe <MeasurementMode>
Selects the measurement mode.
Parameters:
<MeasurementMode> NORMal | MELMode
NORMal: normal mode
MELMode: multi-evaluation list mode
*RST: NORM
Options: R&S CMW-KM012 for MELMode
Manual operation: See "Measurement Mode" on page 311
User Manual 1178.5689.02 ─ 12 353

Command Reference
CONFigure:NIOT:MEAS:MEValuation:MOEXception <MeasOnException>
Specifies whether measurement results that the R&S CMW identifies as faulty or inac-
curate are rejected.
Parameters:
<MeasOnException> OFF | ON
OFF: Faulty results are rejected
ON: Results are never rejected
*RST: OFF
Manual operation: See "Measure on Exception" on page 311
CONFigure:NIOT:MEAS:MEValuation:NSLots <NofSlots>
Configures the length of the captured sequence of slots.
Parameters:
<NofSlots> integer
Range: 1 to 256
*RST: 16
Manual operation: See "No. of Measure Slots" on page 311
CONFigure:NIOT:MEAS:MEValuation:SCSPacing <SubCarrSpacing>
Selects the subcarrier spacing.
For the combined signal path scenario, use CONFigure:NIOT:SIGN:CELL:
SCSPacing.
Parameters:
<SubCarrSpacing> S3K75 | S15K
3.75 kHz or 15 kHz
*RST: S3K75
Example: See Specifying Required Settings
Manual operation: See "Subcarrier Spacing" on page 312
CONFigure:NIOT:MEAS:MEValuation:NPFormat <NPUSChFormat>
Specifies the format of the NPUSCH.
User Manual 1178.5689.02 ─ 12 354

Command Reference
Parameters:
<NPUSChFormat> F1 | F2
*RST: F1
Manual operation: See "NPUSCH Format" on page 312
CONFigure:NIOT:MEAS:MEValuation:SUBCarrier <NofSubCarrier>, <Offset>

Specifies the subcarrier configuration of the allocated resource units.
For the combined signal path scenario, use the uplink scheduling commands of the
signaling application.
Parameters:
<NofSubCarrier> 1 | 3 | 6 | 12
Number of subcarriers per resource unit
The allowed values have dependencies, see Chapter 4.2.6.2,
"Resource Unit Allocation", on page 289.
*RST: 1
<Offset> integer
Offset of the first allocated subcarrier from the edge of the trans-
mission bandwidth
For a subcarrier spacing of 3.75 kHz / 15 kHz, n equals 48 / 12.
Range: 0 to n - <NofSubCarrier>
*RST: 0
Manual operation: See "No. of Subcarriers, Start Subcarrier" on page 313
CONFigure:NIOT:MEAS:MEValuation:NRUNits <NofRU>
Specifies the number of resource units allocated for the NPUSCH.
Parameters:
<NofRU> NRU01 | NRU02 | NRU03 | NRU04 | NRU05 | NRU06 | NRU08 |
NRU10
*RST: NRU01
Manual operation: See "No. of Resource Units" on page 313
User Manual 1178.5689.02 ─ 12 355

Command Reference
CONFigure:NIOT:MEAS:MEValuation:NREPetitions <NofRepetitions>
Specifies the number of NPUSCH repetitions.
Parameters:
<NofRepetitions> NR1 | NR2 | NR4 | NR8 | NR16 | NR32 | NR64 | NR128 |
NR256 | NR512 | NR1K | NR2K
Number of NPUSCH repetitions: 1, 2, 4, ..., 512, 1024, 2048
*RST: NR1
Manual operation: See "No. of Repetitions" on page 313
CONFigure:NIOT:MEAS:MEValuation:PLCid <PhsLayerCellID>
Specifies the physical layer cell ID.
For the combined signal path scenario, use CONFigure:NIOT:SIGN:CELL:
PCID.
Parameters:
<PhsLayerCellID> integer
Range: 0 to 503
*RST: 0
Manual operation: See "Physical Cell ID" on page 314
CONFigure:NIOT:MEAS:MEValuation:DSS <DeltaSeqShift>
Specifies the delta sequence shift value (Δss) used to calculate the sequence shift pat-
tern for the NPUSCH.
Parameters:
<DeltaSeqShift> integer
Range: 0 to 29
*RST: 0
Manual operation: See "Delta Seq. Shift" on page 314
User Manual 1178.5689.02 ─ 12 356

Command Reference
CONFigure:NIOT:MEAS:MEValuation:FSYRange <FSR>
Specifies the frequency synchronization range.
Parameters:
<FSR> LOW | HIGH
*RST: HIGH
Manual operation: See "Freq. Sync. Range" on page 315
CONFigure:NIOT:MEAS:MEValuation:MODulation:MSCHeme <ModScheme>
Selects the modulation scheme used by the measured signal.
This setting is only used in standalone scenario.
● For the standalone scenario, BPSK, QPSK, and 16QAM are supported.
● For the combined signal path scenario, use the uplink scheduling commands of the
Parameters:
<ModScheme> BPSK | QPSK | Q16
For 16QAM, multiple subcarriers per RU must be in use (No. of
SC > 1). See Resource Unit Allocation
Firmware/Software: V3.5.10, 3.8.13: added <ModScheme> Q16
Manual operation: See "Modulation Scheme < Modulation" on page 315
LEADing <Leading>
Defines an exclusion period at the beginning of each NPUSCH transmission. The
excluded symbols are ignored for modulation results.
Parameters:
<Leading> OFF | S1
OFF: no exclusion
S1: exclude first symbol
*RST: OFF
Manual operation: See "EVM Excl. Periods Leading/Lagging < Modulation"
on page 316
User Manual 1178.5689.02 ─ 12 357

Command Reference
LAGGing <Lagging>
Defines an exclusion period at the end of each NPUSCH transmission. The excluded
symbols are ignored for modulation results.
Parameters:
<Lagging> OFF | S1
OFF: no exclusion
S1: exclude first symbol
*RST: OFF
Manual operation: See "EVM Excl. Periods Leading/Lagging < Modulation"
on page 316
CONFigure:NIOT:MEAS:MEValuation:SCOunt:MODulation <StatisticCount>
Specifies the statistic count of the measurement. The statistic count is equal to the
number of measurement intervals per single shot.
Parameters:
<StatisticCount> numeric
Number of measurement intervals (slots)
Range: 1 slot to 1000 slots
*RST: 20 slots
Manual operation: See "Statistic Count" on page 315
CONFigure:NIOT:MEAS:MEValuation:SCOunt:SPECtrum:SEMask
<StatisticCount>
Parameters:
*RST: 20 slots
User Manual 1178.5689.02 ─ 12 358

Command Reference
CONFigure:NIOT:MEAS:MEValuation:SCOunt:SPECtrum:ACLR
<StatisticCount>
Parameters:
*RST: 20 slots
CONFigure:NIOT:MEAS:MEValuation:SPECtrum:ACLR:ENABle <UTRA>,
<GSM>
Enables or disables the evaluation of the adjacent UTRA channels and the adjacent
GSM channels.
Parameters:
<UTRA> OFF | ON
*RST: ON
<GSM> OFF | ON
*RST: ON
Manual operation: See "Select ACLR < ACLR < Spectrum" on page 316
CONFigure:NIOT:MEAS:MEValuation:SPECtrum:SEMask:OBWMode <Mode>
Sets the mode of occupied bandwidth measurement.
Parameters:
<Mode> BW99 | M26
99 % or -26 dBc bandwidth
*RST: BW99
Example: See Specifying Measurement-Specific Settings.
Manual operation: See "OBW Mode < Emission Mask < Spectrum" on page 316
User Manual 1178.5689.02 ─ 12 359

Command Reference
CONFigure:NIOT:MEAS:MEValuation:SCOunt:POWer <StatisticCount>
Parameters:
Number of measurement intervals
Range: 1 to 1000
*RST: 1
4.5.3.4 List Mode Settings
The following commands configure the list mode. For retrieving list mode results, see
Chapter 4.5.3.19, "List Mode Results", on page 396.
For a description of the list mode, see Chapter 4.2.5, "List Mode", on page 282.
The segment number <no> in the following commands refers to the complete range of
configured segments (1..2000).
CONFigure:NIOT:MEAS:MEValuation:LIST.................................................................. 360
CONFigure:NIOT:MEAS:MEValuation:LIST:LRANge..................................................... 361
CONFigure:NIOT:MEAS:MEValuation:LIST:OSINdex.....................................................361
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SETup..................................361
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation.......................... 364
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask............................... 365
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:ACLR...................................365
TRIGger:NIOT:MEAS:MEValuation:LIST:MODE............................................................ 366
CONFigure:NIOT:MEAS:MEValuation:LIST <Enable>
Enables or disables the list mode.
Parameters:
<Enable> OFF | ON
OFF: Disable list mode
ON: Enable list mode
*RST: OFF
Example: See Specifying List Mode Settings
Options: R&S CMW-KM012
Manual operation: See "Enable < List Mode" on page 316
User Manual 1178.5689.02 ─ 12 360

Command Reference
CONFigure:NIOT:MEAS:MEValuation:LIST:LRANge <StartIndex>,
<NrSegments>
Selects a range of measured segments. The segments must be configured using
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SETup.
Parameters:
<StartIndex> numeric
First measured segment in the range of configured segments
Range: 1 to 2000
*RST: 1
<NrSegments> numeric
Number of measured segments
Range: 1 to 1000
*RST: 10
CONFigure:NIOT:MEAS:MEValuation:LIST:OSINdex <OfflineSegIndex>
Selects the segment to be displayed in offline mode. The index refers to the range of
measured segments, see CONFigure:NIOT:MEAS:MEValuation:LIST:
LRANge.
Setting a value also enables the offline mode.
Parameters:
<OfflineSegIndex> numeric | ON | OFF
Range: 1 to <number of measured segments>
*RST: OFF
Additional parameters: OFF (disables the offline mode)
Example: See Performing Single-Shot Measurements
Manual operation: See "Offline Segment Nr. < List Mode" on page 316
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SETup
<SegmentLength>, <Level>, <Band>, <Frequency>, <NPUSChFormat>,
<NofSubcarrier>, <StartSC>, <NofRUs>, <NofRepetitions>, <RetriggerFlag>,
<EvaluatOffset>
Defines the length and analyzer settings of segment <no>. This command must be
sent for all segments to be measured (CONFigure:NIOT:MEAS:MEValuation:
LIST:LRANge).
User Manual 1178.5689.02 ─ 12 361

Command Reference
The supported frequency range depends on the instrument model and the available
options. The supported range can be smaller than stated here. Refer to the preface of
your model-specific base unit manual.
Suffix: .
<no> 1..2000
Segment number
Parameters:
<SegmentLength> integer
Number of slots in the segment
Range: 1 to 2000
*RST: 1
<Level> numeric
Expected nominal power in the segment. The range can be cal-
culated as follows:
Range (Expected Nominal Power) = Range (Input Power) +
External Attenuation - User Margin
*RST: 0 dBm
Default unit: dBm
OB74 | OB85
*RST: OB1
<Frequency> numeric
Carrier center frequency used in the segment
Range: 70E+6 Hz to 6E+9 Hz
*RST: 1.95E+9 Hz
Default unit: Hz
<NPUSChFormat> F1 | F2
Format of the NPUSCH.
*RST: F1
<NofSubcarrier> 1 | 3 | 6 | 12
Number of subcarriers per resource unit
The allowed values have dependencies, see Chapter 4.2.6.2,
"Resource Unit Allocation", on page 289.
*RST: 1
User Manual 1178.5689.02 ─ 12 362

Command Reference
<StartSC> integer
Offset of the first allocated subcarrier from the edge of the trans-
mission bandwidth
For a subcarrier spacing of 3.75 kHz / 15 kHz, n equals 48 / 12.
Range: 0 to n - <NofSubCarrier>
*RST: 0
<NofRUs> NRU01 | NRU02 | NRU03 | NRU04 | NRU05 | NRU06 | NRU08 |
NRU10
Number of resource units allocated for the NPUSCH
*RST: NRU01
<NofRepetitions> NR1 | NR2 | NR4 | NR8 | NR16 | NR32 | NR64 | NR128 |
NR256 | NR512 | NR1K | NR2K
Number of NPUSCH repetitions: 1, 2, 4, ..., 512, 1024, 2048
*RST: NR1
<RetriggerFlag> OFF | ON | IFPower
Specifies whether the measurement waits for a trigger event
before measuring the segment, or not.
For the first segment, the value OFF is always interpreted as
ON.
For subsequent segments, the retrigger flag is ignored for trigger
mode ONCE and evaluated for trigger mode SEGMent, see
TRIGger:NIOT:MEAS:MEValuation:LIST:MODE
on page 366.
OFF
Measure the segment without retrigger.
ON
Wait for a trigger event from the trigger source configured via
TRIGger:NIOT:MEAS:MEValuation:SOURce
on page 367.
IFPower
Wait for a trigger event from the trigger source "IF Power".
*RST: ON
<EvaluatOffset> integer
Number of slots at the beginning of the segment that are not
evaluated
Range: 0 to 1000
*RST: 0
Firmware/Software: V3.7.20, some bands added in later versions
User Manual 1178.5689.02 ─ 12 363

Command Reference
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation
<ModStatistics>, <ModEnable>, <EVMenable>, <MagErrorEnable>,
<PhaseErrEnable>, <IBEenable>, <ModScheme>
Defines settings for modulation measurements in list mode for segment <no>.
Suffix: .
<no> 1..2000
Segment number
Parameters:
<ModStatistics> integer
Statistical length in slots
Range: 1 to 1000
*RST: 20
Default unit: Slot
<ModEnable> OFF | ON
Enables or disables the measurement of modulation results
ON
Modulation results are measured according to the other enable
flags in this command. Modulation results for which there is no
explicit enable flag are also measured (e.g. I/Q offset, frequency
error and timing error).
OFF
No modulation results at all are measured. The other enable
flags in this command are ignored.
*RST: OFF
<EVMenable> OFF | ON
Enables or disables the measurement of EVM
*RST: OFF
<MagErrorEnable> OFF | ON
Enables or disables the measurement of magnitude error
*RST: OFF
<PhaseErrEnable> OFF | ON
Enables or disables the measurement of phase error
*RST: OFF
<IBEenable> OFF | ON
Enables or disables the measurement of inband emissions
*RST: OFF
User Manual 1178.5689.02 ─ 12 364

Command Reference
<ModScheme> BPSK | QPSK | Q16

Modulation scheme used by the NB-IoT uplink signal: BPSK,
QPSK, 16QAM
For 16QAM, multiple subcarriers per RU must be in use (No. of
SC > 1). See Resource Unit Allocation
*RST: QPSK
Firmware/Software: V3.7.20, 3.8.13: added <ModScheme> Q16
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask
<SEMstatistics>, <SEMenable>
Defines settings for spectrum emission measurements in list mode for segment <no>.
Suffix: .
<no> 1..2000
Segment number
Parameters:
<SEMstatistics> integer
Range: 1 to 1000
*RST: 20
<SEMenable> OFF | ON
Enables or disables the measurement of spectrum emission
trace and margin results
*RST: OFF
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:ACLR
<ACLRstatistics>, <ACLRenable>, <UTRAenable>, <GSMenable>
Defines settings for ACLR measurements in list mode for segment <no>.
Suffix: .
<no> 1..2000
Segment number
User Manual 1178.5689.02 ─ 12 365

Command Reference
Parameters:
<ACLRstatistics> integer
Range: 1 to 1000
*RST: 20
<ACLRenable> OFF | ON
Enables or disables the measurement of ACLR results
ON
ACLR results are measured according to the other enable flags
in this command. ACLR results for which there is no explicit
enable flag are also measured (e.g. power in the NB-IoT chan-
nel).
OFF
No ACLR results at all are measured. The other enable flags in
this command are ignored.
*RST: OFF
<UTRAenable> OFF | ON
Enables or disables the evaluation of adjacent UTRA channels
*RST: OFF
<GSMenable> OFF | ON
Enables or disables the evaluation of adjacent GSM channels
*RST: OFF
TRIGger:NIOT:MEAS:MEValuation:LIST:MODE <Mode>
Specifies the trigger mode for list mode measurements. For configuration of retrigger
flags, see CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:
SETup on page 361.
Parameters:
<Mode> ONCE | SEGMent
ONCE: A trigger event is only required to start the measure-
ment. As a result, the entire range of segments to be measured
is captured without additional trigger event. The retrigger flag of
the first segment is evaluated. The other retrigger flags are
ignored.
SEGMent: The retrigger flag of each segment is evaluated. It
defines whether the measurement waits for a trigger event
before capturing the segment, or not.
*RST: ONCE
User Manual 1178.5689.02 ─ 12 366

Command Reference

4.5.3.5 Trigger Settings
The following commands define the trigger parameters.

TRIGger:NIOT:MEAS:MEValuation:CATalog:SOURce?..................................................367
TRIGger:NIOT:MEAS:MEValuation:SOURce................................................................ 367
TRIGger:NIOT:MEAS:MEValuation:SLOPe...................................................................368
TRIGger:NIOT:MEAS:MEValuation:THReshold.............................................................368
TRIGger:NIOT:MEAS:MEValuation:DELay................................................................... 368
TRIGger:NIOT:MEAS:MEValuation:TOUT.................................................................... 369
TRIGger:NIOT:MEAS:MEValuation:MGAP....................................................................369
TRIGger:NIOT:MEAS:MEValuation:CATalog:SOURce?
Lists all trigger source values that can be set using TRIGger:NIOT:MEAS:
MEValuation:SOURce.
Return values:
<Sourcelist> string
Comma-separated list of all supported values. Each value is rep-
resented as a string.
Usage: Query only
Manual operation: See "Trigger Source" on page 317
TRIGger:NIOT:MEAS:MEValuation:SOURce <Source>
Selects the source of the trigger events. Some values are always available. They are
listed below. Depending on the installed options, additional values are available. You
can query a list of all supported values via TRIGger:...:CATalog:SOURce?.
Parameters:
<Source> string
'Free Run (No Sync)'
Free run without synchronization
'IF Power'
Power trigger (received RF power)
*RST: 'IF Power'
Example: See Configuring the Trigger System
User Manual 1178.5689.02 ─ 12 367

Command Reference
TRIGger:NIOT:MEAS:MEValuation:SLOPe <Slope>
Qualifies whether the trigger event is generated at the rising or at the falling edge of
the trigger pulse (valid for external and power trigger sources).
Parameters:
<Slope> REDGe | FEDGe
REDGe: Rising edge
FEDGe: Falling edge
*RST: REDG
Manual operation: See "Trigger Slope" on page 317
TRIGger:NIOT:MEAS:MEValuation:THReshold <TrigThreshold>
Defines the trigger threshold for power trigger sources.
Parameters:
<TrigThreshold> numeric | ON | OFF
*RST: -20 dB
Default unit: dB (full scale, i.e. relative to reference level minus
external attenuation)
Manual operation: See "Trigger Threshold" on page 317
TRIGger:NIOT:MEAS:MEValuation:DELay <Delay>
Defines a time delaying the start of the measurement relative to the trigger event. This
setting has no influence on free run measurements.
Parameters:
<Delay> numeric
Range: -250E-6 s to 250E-6 s
*RST: 0s
Default unit: s
Manual operation: See "Trigger Delay" on page 318
User Manual 1178.5689.02 ─ 12 368

Command Reference
TRIGger:NIOT:MEAS:MEValuation:TOUT <TriggerTimeOut>
Selects the maximum time that the measurement waits for a trigger event before it
stops in remote control mode or indicates a trigger timeout in manual operation mode.
Parameters:
<TriggerTimeOut> numeric | ON | OFF
Range: 0.01 s to 167772.15 s
*RST: 0.1 s
Default unit: s
Additional parameters: OFF | ON (disables | enables the time-
out)
Manual operation: See "Trigger Timeout" on page 318
TRIGger:NIOT:MEAS:MEValuation:MGAP <MinTrigGap>
Sets a minimum time during which the IF signal must be below the trigger threshold
before the trigger is armed so that an IF power trigger event can be generated.
Parameters:
<MinTrigGap> numeric
Range: 0 s to 0.01 s
*RST: 250E-6 s
Default unit: s
Manual operation: See "Min Trigger Gap" on page 318
4.5.3.6 Limits Modulation
The following commands define limits for results which characterize the modulation
accuracy.
CONFigure:NIOT:MEAS:MEValuation:LIMit:EVMagnitude..............................................369
CONFigure:NIOT:MEAS:MEValuation:LIMit:MERRor.....................................................370
CONFigure:NIOT:MEAS:MEValuation:LIMit:PERRor..................................................... 371
CONFigure:NIOT:MEAS:MEValuation:LIMit:FERRor..................................................... 371
CONFigure:NIOT:MEAS:MEValuation:LIMit:IQOFfset.................................................... 372
CONFigure:NIOT:MEAS:MEValuation:LIMit:IBE............................................................ 372
CONFigure:NIOT:MEAS:MEValuation:LIMit:IBE:IQOFfset.............................................. 373
CONFigure:NIOT:MEAS:MEValuation:LIMit:EVMagnitude <RMS>, <Peak>

Defines upper limits for the RMS and peak values of the error vector magnitude (EVM).
User Manual 1178.5689.02 ─ 12 369

Command Reference
Parameters:
<RMS> numeric | ON | OFF
Range: 0 % to 100 %
*RST: 17.5 %, ON
Default unit: %
Additional parameters: OFF | ON (disables the limit check | ena-
bles the limit check using the previous/default limit values)
<Peak> numeric | ON | OFF
Range: 0 % to 100 %
*RST: 35 %, OFF
Default unit: %
Example: See Specifying Limits
Manual operation: See "EVM, magnitude error, phase error limit settings"
on page 319
CONFigure:NIOT:MEAS:MEValuation:LIMit:MERRor <RMS>, <Peak>

Defines upper limits for the RMS and peak values of the magnitude error.
Parameters:
Range: 0 % to 100 %
*RST: 17.5 %, OFF
Default unit: %
Range: 0 % to 100 %
*RST: 35 %, OFF
Default unit: %
on page 319
User Manual 1178.5689.02 ─ 12 370

Command Reference
CONFigure:NIOT:MEAS:MEValuation:LIMit:PERRor <RMS>, <Peak>

Defines symmetric limits for the RMS and peak values of the phase error. The limit
check fails if the absolute value of the measured phase error exceeds the specified val-
ues.
Parameters:
Range: 0 deg to 180 deg
*RST: 17.5 deg, OFF
Default unit: deg
*RST: 35 deg, OFF
Default unit: deg
on page 319
CONFigure:NIOT:MEAS:MEValuation:LIMit:FERRor <FreqErrEnable>,
<FreqErrLow>, <FreqErrHigh>
Defines upper limits for the carrier frequency error.
Parameters:
<FreqErrEnable> OFF | ON
OFF: disables the limit check
ON: enables the limit check
*RST: ON
<FreqErrLow> numeric | ON | OFF
Upper limit for frequencies up to 1 GHz
Range: 0 ppm to 1 ppm
*RST: 0.2 ppm
<FreqErrHigh> numeric | ON | OFF
Upper limit for frequencies above 1 GHz
*RST: 0.2 ppm
User Manual 1178.5689.02 ─ 12 371

Command Reference
Manual operation: See "Frequency error limit settings" on page 320
CONFigure:NIOT:MEAS:MEValuation:LIMit:IQOFfset <Enable>, <Offset1>,

<Offset2>, <Offset3>
Defines upper limits for the I/Q origin offset. Three different limits can be set for three
TX power ranges. For details, see Chapter 4.3.6.3, "I/Q Origin Offset Limits",
on page 320.
Parameters:
<Enable> OFF | ON
*RST: ON
<Offset1> numeric
I/Q origin offset limit for high TX power range
Range: -256 dBc to 256 dBc
*RST: -24.2 dBc
Default unit: dBc
<Offset2> numeric
I/Q origin offset limit for intermediate TX power range
*RST: -19.2 dBc
Default unit: dBc
<Offset3> numeric
I/Q origin offset limit for low TX power range
*RST: -9.2 dBc
Default unit: dBc
Manual operation: See "I/Q origin offset limit settings" on page 320
CONFigure:NIOT:MEAS:MEValuation:LIMit:IBE <Enable>, <Minimum>,

<SCPower>, <IQImage>
Defines parameters used for calculation of an upper limit for the inband emissions, see
Chapter 4.3.6.4, "Inband Emissions Limits", on page 321.
Parameters:
<Enable> OFF | ON
*RST: ON
User Manual 1178.5689.02 ─ 12 372

Command Reference
<Minimum> numeric
*RST: -30 dB
Default unit: dB
<SCPower> numeric
*RST: -57 dBm
Default unit: dBm
<IQImage> numeric
*RST: -24.2 dB
Default unit: dB
Manual operation: See "Inband emission limit settings" on page 322
CONFigure:NIOT:MEAS:MEValuation:LIMit:IBE:IQOFfset <Offset1>, <Offset2>,

<Offset3>
Defines I/Q origin offset values used for calculation of an upper limit for the inband
emissions. Three different values can be set for three TX power ranges, see Chap-
ter 4.3.6.4, "Inband Emissions Limits", on page 321.
Parameters:
<Offset1> numeric
Offset for high TX power range
*RST: -24.2 dBc
Default unit: dBc
<Offset2> numeric
Offset for intermediate TX power range
*RST: -19.2 dBc
Default unit: dBc
<Offset3> numeric
Offset for low TX power range
*RST: -9.2 dBc
Default unit: dBc
Manual operation: See "Inband emission limit settings" on page 322
User Manual 1178.5689.02 ─ 12 373

Command Reference
4.5.3.7 Limits Spectrum
The following commands define ACLR and spectrum emission limits.

CONFigure:NIOT:MEAS:MEValuation:LIMit:ACLR:GSM................................................ 374
CONFigure:NIOT:MEAS:MEValuation:LIMit:ACLR:UTRA...............................................374
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:OBWLimit......................................375
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:LIMit<no>......................................375
CONFigure:NIOT:MEAS:MEValuation:LIMit:ACLR:GSM <RelativeLevel>,
<AbsoluteLevel>
Defines a relative and absolute limit for the ACLR measured in the adjacent GSM
channel.
Parameters:
<RelativeLevel> numeric | ON | OFF
*RST: 19.2 dB
Default unit: dB
<AbsoluteLevel> numeric | ON | OFF
*RST: -50 dBm
Default unit: dBm
Manual operation: See "ACLR limit settings" on page 324
CONFigure:NIOT:MEAS:MEValuation:LIMit:ACLR:UTRA <RelativeLevel>,
<AbsoluteLevel>
Defines a relative and absolute limit for the ACLR measured in the adjacent UTRA
channel.
Parameters:
<RelativeLevel> numeric | ON | OFF
*RST: 36.2 dB
Default unit: dB
User Manual 1178.5689.02 ─ 12 374

Command Reference
<AbsoluteLevel> numeric | ON | OFF

*RST: -50 dBm
Default unit: dBm
Manual operation: See "ACLR limit settings" on page 324
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:OBWLimit <OBWlimit>
Defines an upper limit for the occupied bandwidth.
Parameters:
<OBWlimit> numeric | ON | OFF
Range: 0 Hz to 1E+6 Hz
*RST: 200E+3 Hz
Default unit: Hz
Manual operation: See "OBW limit settings" on page 323
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:LIMit<no> <Enable>,
<FrequencyStart>, <FrequencyStop>, <PowerLevelStart>, <PowerLevelStop>
Defines the emission mask area <no>.
Suffix: .
<no> 1..12
Number of the emission mask area
Parameters:
<Enable> OFF | ON
OFF: disables the check of these requirements
ON: enables the check of these requirements
*RST: ON for area 1 to 5, OFF for area 6 to 12
<FrequencyStart> numeric
Start frequency of the area, relative to the edges of the channel
bandwidth
Range: 0 MHz to 1.9 MHz
*RST: depends on the area number
Default unit: Hz
User Manual 1178.5689.02 ─ 12 375

Command Reference
<FrequencyStop> numeric
Stop frequency of the area, relative to the edges of the channel
bandwidth
Range: 0 MHz to 1.9 MHz
Default unit: Hz
<PowerLevelStart> numeric
Upper limit at the <FrequencyStart>
Default unit: dBm
<PowerLevelStop> numeric
Upper limit at the <FrequencyEnd>
Default unit: dBm
Manual operation: See "Emission mask settings" on page 323
4.5.3.8 Limits Power
The following command defines limits for results which characterize the power dynam-
ics of the signal.
CONFigure:NIOT:MEAS:MEValuation:LIMit:PDYNamics <Enable>,
<OnPowerUpper>, <OnPowerLower>, <OffPowerUpper>
Defines limits for the ON power and OFF power determined with the power dynamics
measurement.
Parameters:
<Enable> OFF | ON
*RST: ON
<OnPowerUpper> numeric
Upper limit for the "ON power"
*RST: -3.5 dBm
Default unit: dBm
User Manual 1178.5689.02 ─ 12 376

Command Reference
<OnPowerLower> numeric
Lower limit for the "ON power"
*RST: -18.5 dBm
Default unit: dBm
<OffPowerUpper> numeric
Upper limit for the "OFF power"
*RST: -48.5 dBm
Default unit: dBm
Firmware/Software: V3.5.10, V3.7.20: reset values adapted to specification changes
Manual operation: See "Power dynamics limit settings" on page 325
4.5.3.9 EVM Results (Traces)
The following commands return the EVM trace results of the multi-evaluation measure-
ment.
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:CURRent?........................................... 377
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:AVERage?........................................... 377
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:MAXimum?.......................................... 377
READ:NIOT:MEAS:MEValuation:EVMagnitude:CURRent?............................................ 377
READ:NIOT:MEAS:MEValuation:EVMagnitude:AVERage?............................................ 378
READ:NIOT:MEAS:MEValuation:EVMagnitude:MAXimum?........................................... 378
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:CURRent?..................................378
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:AVERage?..................................378
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:MAXimum?.................................378
READ:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:CURRent?................................... 378
READ:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:AVERage?...................................378
READ:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:MAXimum?..................................378
FETCh:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:CURRent?................................. 378
FETCh:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:AVERage?................................. 378
FETCh:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:MAXimum?................................ 378
READ:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:CURRent?...................................378
READ:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:AVERage?.................................. 379
READ:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:MAXimum?................................. 379
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:CURRent?
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:AVERage?
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:MAXimum?
READ:NIOT:MEAS:MEValuation:EVMagnitude:CURRent?
User Manual 1178.5689.02 ─ 12 377

Command Reference
READ:NIOT:MEAS:MEValuation:EVMagnitude:AVERage?
READ:NIOT:MEAS:MEValuation:EVMagnitude:MAXimum?
Returns the values of the EVM RMS bar graphs for the SC-FDMA symbols in the mea-
sured slot. The results of the current, average and maximum bar graphs can be
retrieved.
See also Chapter 4.3.2.2, "View Error Vector Magnitude", on page 293.
Return values:
Reliability Indicator
<Results> float
Comma-separated list of 7 results, for SC-FDMA symbol 0 to 6
Default unit: %
Usage: Query only
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:CURRent?
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:AVERage?
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:MAXimum?
READ:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:CURRent?
READ:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:AVERage?
READ:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:MAXimum?
Returns the values of the EVM peak bar graphs for the SC-FDMA symbols in the mea-
sured slot. The results of the current, average and maximum bar graphs can be
retrieved.
See also Chapter 4.3.2.2, "View Error Vector Magnitude", on page 293.
Return values:
<Results> float
Default unit: %
Usage: Query only
FETCh:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:CURRent?
FETCh:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:AVERage?
FETCh:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:MAXimum?
READ:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:CURRent?
User Manual 1178.5689.02 ─ 12 378

Command Reference
READ:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:AVERage?
READ:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:MAXimum?
Returns the values of the EVM vs modulation symbol trace. See also Chapter 4.3.2.2,
"View Error Vector Magnitude", on page 293.
Return values:
<Ratio> float
Comma-separated list of EVM values, one value per modulation
symbol
Default unit: %
Usage: Query only
4.5.3.10 Magnitude Error Results (Traces)
The following commands return the magnitude error vs. SC-FDMA symbol results of
the multi-evaluation measurement.
FETCh:NIOT:MEAS:MEValuation:MERRor:CURRent?
FETCh:NIOT:MEAS:MEValuation:MERRor:AVERage?
FETCh:NIOT:MEAS:MEValuation:MERRor:MAXimum?
READ:NIOT:MEAS:MEValuation:MERRor:CURRent?
READ:NIOT:MEAS:MEValuation:MERRor:AVERage?
READ:NIOT:MEAS:MEValuation:MERRor:MAXimum?
Returns the values of the magnitude error bar graphs for the SC-FDMA symbols in the
measured slot. The results of the current, average and maximum bar graphs can be
retrieved.
See also Chapter 4.3.2.3, "Views Magnitude Error, Phase Error", on page 294.
Return values:
<Results> float
Default unit: %
Usage: Query only
User Manual 1178.5689.02 ─ 12 379

Command Reference
4.5.3.11 Phase Error Results (Traces)
The following commands return the phase error vs. SC-FDMA symbol results of the
multi-evaluation measurement.
FETCh:NIOT:MEAS:MEValuation:PERRor:CURRent?
FETCh:NIOT:MEAS:MEValuation:PERRor:AVERage?
FETCh:NIOT:MEAS:MEValuation:PERRor:MAXimum?
READ:NIOT:MEAS:MEValuation:PERRor:CURRent?
READ:NIOT:MEAS:MEValuation:PERRor:AVERage?
READ:NIOT:MEAS:MEValuation:PERRor:MAXimum?
Returns the values of the phase error bar graphs for the SC-FDMA symbols in the
measured slot. The results of the current, average and maximum bar graphs can be
retrieved.
See also Chapter 4.3.2.3, "Views Magnitude Error, Phase Error", on page 294.
Return values:
<Results> float
Default unit: deg
Usage: Query only
4.5.3.12 Inband Emission Results
The following commands return the inband emission trace results of the multi-evalua-
tion measurement.
FETCh:NIOT:MEAS:MEValuation:TRACe:IEMissions?.................................................. 380
READ:NIOT:MEAS:MEValuation:TRACe:IEMissions?................................................... 380
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:CURRent?................................... 381
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:AVERage?................................... 381
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:EXTReme?.................................. 381
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:SDEViation?.................................381
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:CURRent:SCINdex?......................381
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:EXTReme:SCINdex?.....................381
FETCh:NIOT:MEAS:MEValuation:TRACe:IEMissions?
READ:NIOT:MEAS:MEValuation:TRACe:IEMissions?
Returns the values of the inband emissions trace. See also Chapter 4.3.2.4, "View
Inband Emissions", on page 295.
User Manual 1178.5689.02 ─ 12 380

Command Reference
Return values:
<Power> float
Comma-separated list of power values, one value per subcarrier
For 15 kHz SC spacing, 12 power values are returned.
For 3.75 kHz SC spacing, 48 power values are returned.
Default unit: dBm
Usage: Query only
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:CURRent?
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:AVERage?
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:EXTReme?
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:SDEViation?
Return the limit line margin results for the inband emissions. The CURRent margin indi-
cates the minimum (vertical) distance between the inband emissions limit line and the
current trace. A negative result indicates that the limit is exceeded.
The AVERage, EXTReme and SDEViation values are calculated from the current mar-
gins. The margin results cannot be displayed at the GUI.
Return values:
<OutOfTolerance> decimal
Out of tolerance result, i.e. percentage of measurement inter-
vals of the statistic count for modulation measurements exceed-
ing the specified inband emission limits.
Default unit: %
<Margin> float
Default unit: dB
Usage: Query only
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:CURRent:SCINdex?
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:EXTReme:SCINdex?
Return subcarrier indices for inband emission margins. At these SC indices, the
CURRent and EXTReme margins have been detected (see FETCh:NIOT:MEAS:
MEValuation:IEMission:MARGin:CURRent? and ...:EXTReme).
User Manual 1178.5689.02 ─ 12 381

Command Reference
Return values:
ing the specified inband emission limits.
Default unit: %
<SCindex> decimal
Subcarrier index
Usage: Query only
4.5.3.13 Spectrum Emission Results
The following commands return the spectrum emission results of the multi-evaluation
measurement.
FETCh:NIOT:MEAS:MEValuation:TRACe:SEMask:CURRent?....................................... 382
FETCh:NIOT:MEAS:MEValuation:TRACe:SEMask:AVERage?....................................... 382
FETCh:NIOT:MEAS:MEValuation:TRACe:SEMask:MAXimum?...................................... 383
READ:NIOT:MEAS:MEValuation:TRACe:SEMask:CURRent?........................................ 383
READ:NIOT:MEAS:MEValuation:TRACe:SEMask:AVERage?........................................ 383
READ:NIOT:MEAS:MEValuation:TRACe:SEMask:MAXimum?....................................... 383
CALCulate:NIOT:MEAS:MEValuation:SEMask:CURRent?............................................. 383
CALCulate:NIOT:MEAS:MEValuation:SEMask:AVERage?............................................. 383
FETCh:NIOT:MEAS:MEValuation:SEMask:CURRent?...................................................383
FETCh:NIOT:MEAS:MEValuation:SEMask:AVERage?.................................................. 383
FETCh:NIOT:MEAS:MEValuation:SEMask:SDEViation?................................................ 383
READ:NIOT:MEAS:MEValuation:SEMask:CURRent?....................................................383
READ:NIOT:MEAS:MEValuation:SEMask:AVERage?....................................................383
READ:NIOT:MEAS:MEValuation:SEMask:SDEViation?................................................. 383
CALCulate:NIOT:MEAS:MEValuation:SEMask:EXTReme?............................................ 384
FETCh:NIOT:MEAS:MEValuation:SEMask:EXTReme?..................................................384
READ:NIOT:MEAS:MEValuation:SEMask:EXTReme?...................................................384
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:ALL?..............................................385
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:CURRent:NEGativ?........................ 386
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:CURRent:POSitiv?..........................386
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:AVERage:NEGativ?........................ 386
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:AVERage:POSitiv?..........................386
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:MINimum:NEGativ?........................ 386
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:MINimum:POSitiv?..........................386
FETCh:NIOT:MEAS:MEValuation:TRACe:SEMask:CURRent?
FETCh:NIOT:MEAS:MEValuation:TRACe:SEMask:AVERage?
User Manual 1178.5689.02 ─ 12 382

Command Reference
FETCh:NIOT:MEAS:MEValuation:TRACe:SEMask:MAXimum?
READ:NIOT:MEAS:MEValuation:TRACe:SEMask:CURRent?
READ:NIOT:MEAS:MEValuation:TRACe:SEMask:AVERage?
READ:NIOT:MEAS:MEValuation:TRACe:SEMask:MAXimum?
Returns the values of the spectrum emission traces. The results of the current, aver-
age and maximum traces can be retrieved.
See also Chapter 4.3.2.5, "View Spectrum Emission Mask", on page 296.
Return values:
<Power> float
Comma-separated list of 1067 power results
The value in the middle of the result array corresponds to the
center frequency.
The test point separation between two results equals 3.75 kHz.
Default unit: dBm
Usage: Query only
CALCulate:NIOT:MEAS:MEValuation:SEMask:CURRent?
CALCulate:NIOT:MEAS:MEValuation:SEMask:AVERage?
FETCh:NIOT:MEAS:MEValuation:SEMask:CURRent?
FETCh:NIOT:MEAS:MEValuation:SEMask:AVERage?
FETCh:NIOT:MEAS:MEValuation:SEMask:SDEViation?
READ:NIOT:MEAS:MEValuation:SEMask:CURRent?
READ:NIOT:MEAS:MEValuation:SEMask:AVERage?
READ:NIOT:MEAS:MEValuation:SEMask:SDEViation?
Return the current, average and standard deviation single value results of the spec-
trum emission measurement.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
vals of the statistic count for spectrum emission measurements
exceeding the specified spectrum emission mask limits.
Default unit: %
User Manual 1178.5689.02 ─ 12 383

Command Reference
<OBW> float
Occupied bandwidth
Default unit: Hz
<TXpower> float
Total TX power within 400 kHz
Default unit: dBm
Usage: Query only
CALCulate:NIOT:MEAS:MEValuation:SEMask:EXTReme?
FETCh:NIOT:MEAS:MEValuation:SEMask:EXTReme?
READ:NIOT:MEAS:MEValuation:SEMask:EXTReme?
Return the extreme single value results of the spectrum emission measurement.
Return values:
Default unit: %
<OBW> float
Occupied bandwidth
Default unit: Hz
<TXpowerMin> float
Minimum total TX power
Default unit: dBm
<TXpowerMax> float
Maximum total TX power
Default unit: dBm
Usage: Query only
User Manual 1178.5689.02 ─ 12 384

Command Reference
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:ALL?
Returns spectrum emission mask margin results. A negative margin indicates that the
trace is located above the limit line, i.e. the limit is exceeded.
Results are provided for the current, average and maximum traces. For inactive areas,
NCAP is returned.
Return values:
Default unit: %
<MarginCurrNeg> float
Comma-separated list of 12 margin results
For the current trace, area 1 to 12, negative frequency offsets
Default unit: dB
<MarginCurrPos> float
For the current trace, area 1 to 12, positive frequency offsets
Default unit: dB
<MarginAvgNeg> float
For the average trace, area 1 to 12, negative frequency offsets
Default unit: dB
<MarginAvgPos> float
For the average trace, area 1 to 12, positive frequency offsets
Default unit: dB
<MarginMinNeg> float
For the maximum trace, area 1 to 12, negative frequency offsets
Default unit: dB
<MarginMinPos> float
For the maximum trace, area 1 to 12, positive frequency offsets
Default unit: dB
Usage: Query only
User Manual 1178.5689.02 ─ 12 385

Command Reference
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:CURRent:NEGativ?
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:CURRent:POSitiv?
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:AVERage:NEGativ?
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:AVERage:POSitiv?
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:MINimum:NEGativ?
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:MINimum:POSitiv?
Returns spectrum emission mask margin results. A negative margin indicates that the
trace is located above the limit line, i.e. the limit is exceeded.
The individual commands provide results for the CURRent, AVERage and maximum
traces (resulting in MINimum margins), for NEGative and POSitive offset frequen-
cies.
Each command returns pairs of X and Y values of the margins for emission mask
areas 1 to 12. Result array structure:
<Reliability>, <OutOfTolerance>, {<MarginX>, <MarginY>}area 1, {...}area 2, ..., {...}area 12
For inactive areas, NCAP is returned.

Return values:
Default unit: %
<MarginPosX> float
X-position of margin
Default unit: Hz
<MarginPosY> float
Y-value of margin
Default unit: dB
Usage: Query only
4.5.3.14 ACLR Spectrum Results
The following commands return the results of the ACLR spectrum multi-evaluation
measurement.
User Manual 1178.5689.02 ─ 12 386

Command Reference
FETCh:NIOT:MEAS:MEValuation:TRACe:ACLR:CURRent?.......................................... 387
FETCh:NIOT:MEAS:MEValuation:TRACe:ACLR:AVERage?.......................................... 387
READ:NIOT:MEAS:MEValuation:TRACe:ACLR:CURRent?............................................387
READ:NIOT:MEAS:MEValuation:TRACe:ACLR:AVERage?............................................387
CALCulate:NIOT:MEAS:MEValuation:ACLR:CURRent?.................................................388
CALCulate:NIOT:MEAS:MEValuation:ACLR:AVERage?................................................ 388
FETCh:NIOT:MEAS:MEValuation:ACLR:CURRent?...................................................... 388
FETCh:NIOT:MEAS:MEValuation:ACLR:AVERage?......................................................388
READ:NIOT:MEAS:MEValuation:ACLR:CURRent?....................................................... 388
READ:NIOT:MEAS:MEValuation:ACLR:AVERage?....................................................... 388
FETCh:NIOT:MEAS:MEValuation:TRACe:ACLR:CURRent?
FETCh:NIOT:MEAS:MEValuation:TRACe:ACLR:AVERage?
READ:NIOT:MEAS:MEValuation:TRACe:ACLR:CURRent?
READ:NIOT:MEAS:MEValuation:TRACe:ACLR:AVERage?
Returns the absolute powers as displayed in the ACLR diagram. The current and aver-
age values can be retrieved. See also Chapter 4.3.2.6, "View Spectrum ACLR",
on page 298.
Return values:
<UTRAneg> float
Power in the adjacent UTRA channel with lower frequency
Default unit: dBm
<GSMneg> float
Power in the adjacent GSM channel with lower frequency
Default unit: dBm
<NBNIOT> float
Power in the allocated NB-IoT channel
Default unit: dBm
<GSMpos> float
Power in the adjacent GSM channel with higher frequency
Default unit: dBm
<UTRApos> float
Power in the adjacent UTRA channel with higher frequency
Default unit: dBm
Usage: Query only
User Manual 1178.5689.02 ─ 12 387

Command Reference
CALCulate:NIOT:MEAS:MEValuation:ACLR:CURRent?
CALCulate:NIOT:MEAS:MEValuation:ACLR:AVERage?
FETCh:NIOT:MEAS:MEValuation:ACLR:CURRent?
FETCh:NIOT:MEAS:MEValuation:ACLR:AVERage?
READ:NIOT:MEAS:MEValuation:ACLR:CURRent?
READ:NIOT:MEAS:MEValuation:ACLR:AVERage?
Returns the relative ACLR values as displayed in the table below the ACLR diagram.
The current and average values can be retrieved.
See also Chapter 4.3.2.6, "View Spectrum ACLR", on page 298.
Return values:
<UTRAneg> float
ACLR for the adjacent UTRA channel with lower frequency
Default unit: dB
<GSMneg> float
ACLR for the adjacent GSM channel with lower frequency
Default unit: dB
<NBNIOT> float
Power in the allocated NB-IOT channel
Default unit: dBm
<GSMpos> float
ACLR for the adjacent GSM channel with higher frequency
Default unit: dB
<UTRApos> float
ACLR for the adjacent UTRA channel with higher frequency
Default unit: dB
Usage: Query only
4.5.3.15 I/Q Constellation Results
The following command returns the results in the I/Q constellation diagram.
FETCh:NIOT:MEAS:MEValuation:TRACe:IQ?
Returns the results in the I/Q constellation diagram as pairs of I/Q values:
<Reliability>, {<IPhase>, <QPhase>}point 1, {...}point 2, ..., {...}point n
See also Chapter 4.3.2.7, "View I/Q Constellation", on page 299
User Manual 1178.5689.02 ─ 12 388

Command Reference
Return values:
<IPhase> float
Normalized I amplitude
<QPhase> float
Normalized Q amplitude
Usage: Query only
4.5.3.16 Power Monitor Results
The following commands return the power monitor results of the multi-evaluation mea-
surement.
FETCh:NIOT:MEAS:MEValuation:TRACe:PMONitor?
READ:NIOT:MEAS:MEValuation:TRACe:PMONitor?
Returns the power monitor results for all captured slots. The number of captured slots
is configurable, see CONFigure:NIOT:MEAS:MEValuation:NSLots.
Return values:
<Power> float
Comma-separated list of power values, one value per captured
slot
Default unit: dBm
Usage: Query only
4.5.3.17 Power Dynamics Results
The following commands return the results of the power dynamics measurement.
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:CURRent?..................................390
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:AVERage?..................................390
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:MAXimum?.................................390
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:CURRent?................................... 390
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:AVERage?...................................390
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:MAXimum?..................................390
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:CURRent?........................ 391
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:AVERage?........................ 391
User Manual 1178.5689.02 ─ 12 389

Command Reference
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:MAXimum?....................... 391
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:CURRent?..........................391
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:AVERage?......................... 391
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:MAXimum?........................ 391
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:CURRent?........................................391
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:AVERage?........................................391
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:MINimum?........................................391
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:MAXimum?.......................................391
FETCh:NIOT:MEAS:MEValuation:PDYNamics:CURRent?............................................. 391
FETCh:NIOT:MEAS:MEValuation:PDYNamics:AVERage?............................................. 391
FETCh:NIOT:MEAS:MEValuation:PDYNamics:MINimum?............................................. 391
FETCh:NIOT:MEAS:MEValuation:PDYNamics:MAXimum?............................................ 391
FETCh:NIOT:MEAS:MEValuation:PDYNamics:SDEViation?...........................................391
READ:NIOT:MEAS:MEValuation:PDYNamics:CURRent?.............................................. 391
READ:NIOT:MEAS:MEValuation:PDYNamics:AVERage?.............................................. 392
READ:NIOT:MEAS:MEValuation:PDYNamics:MINimum?.............................................. 392
READ:NIOT:MEAS:MEValuation:PDYNamics:MAXimum?............................................. 392
READ:NIOT:MEAS:MEValuation:PDYNamics:SDEViation?............................................392
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:CURRent?
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:AVERage?
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:MAXimum?
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:CURRent?
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:AVERage?
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:MAXimum?
Return the values of the left power dynamics trace (start of first allocated RU). The
results of the current, average and maximum traces can be retrieved.
See also Chapter 4.3.2.9, "View Power Dynamics", on page 301.
Return values:
<Power> float
Comma-separated list of 1408 power values
The 705th value refers to the time 0 µs, the start of the first allo-
cated RU.
The other details depend on the subcarrier spacing, see table.
Default unit: dBm
Usage: Query only
User Manual 1178.5689.02 ─ 12 390

Command Reference
Table 4-3: Trace structure depending on subcarrier spacing
SC spacing Covered time Value spacing
3.75 kHz -2200 μs to 2196.875 μs 3.125 μs
15 kHz -1100 μs to 1098.4375 μs 1.5625 μs
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:CURRent?
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:AVERage?
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:MAXimum?
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:CURRent?
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:AVERage?
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:MAXimum?
Return the values of the right power dynamics trace (end of last allocated RU). The
results of the current, average and maximum traces can be retrieved.
Return values:
<Power> float
Comma-separated list of 1408 power values
The 705th value refers to the time 0 µs, the end of the last alloca-
ted RU.
The other details depend on the subcarrier spacing, see table.
Default unit: dBm
Usage: Query only
Table 4-4: Trace structure depending on subcarrier spacing
SC spacing Covered time Value spacing
3.75 kHz -2200 μs to 2196.875 μs 3.125 μs
15 kHz -1100 μs to 1098.4375 μs 1.5625 μs
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:CURRent?
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:AVERage?
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:MINimum?
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:MAXimum?
FETCh:NIOT:MEAS:MEValuation:PDYNamics:CURRent?
FETCh:NIOT:MEAS:MEValuation:PDYNamics:AVERage?
FETCh:NIOT:MEAS:MEValuation:PDYNamics:MINimum?
FETCh:NIOT:MEAS:MEValuation:PDYNamics:MAXimum?
FETCh:NIOT:MEAS:MEValuation:PDYNamics:SDEViation?
READ:NIOT:MEAS:MEValuation:PDYNamics:CURRent?
User Manual 1178.5689.02 ─ 12 391

Command Reference
READ:NIOT:MEAS:MEValuation:PDYNamics:AVERage?
READ:NIOT:MEAS:MEValuation:PDYNamics:MINimum?
READ:NIOT:MEAS:MEValuation:PDYNamics:MAXimum?
READ:NIOT:MEAS:MEValuation:PDYNamics:SDEViation?
Return the current, average, minimum, maximum and standard deviation single value
results of the power dynamics measurement.
Return values:
vals of the statistic count for power dynamics measurements
exceeding the specified power dynamics limits.
Default unit: %
<OffPowerBefore> float
Default unit: dBm
<OnPowerRMS> float
Default unit: dBm
<OnPowerPeak> float
Default unit: dBm
<OffPowerAfter> float
Default unit: dBm
Usage: Query only
4.5.3.18 Modulation Results (Single Values)
The following commands return the statistical modulation results.

CALCulate:NIOT:MEAS:MEValuation:MODulation:CURRent?........................................ 393
CALCulate:NIOT:MEAS:MEValuation:MODulation:AVERage?........................................ 393
FETCh:NIOT:MEAS:MEValuation:MODulation:CURRent?..............................................393
FETCh:NIOT:MEAS:MEValuation:MODulation:AVERage?............................................. 393
FETCh:NIOT:MEAS:MEValuation:MODulation:SDEViation?........................................... 393
READ:NIOT:MEAS:MEValuation:MODulation:CURRent?...............................................393
READ:NIOT:MEAS:MEValuation:MODulation:AVERage?...............................................393
READ:NIOT:MEAS:MEValuation:MODulation:SDEViation?............................................ 393
CALCulate:NIOT:MEAS:MEValuation:MODulation:EXTReme?....................................... 394
FETCh:NIOT:MEAS:MEValuation:MODulation:EXTReme?............................................ 394
READ:NIOT:MEAS:MEValuation:MODulation:EXTReme?..............................................394
User Manual 1178.5689.02 ─ 12 392

Command Reference
CALCulate:NIOT:MEAS:MEValuation:MODulation:CURRent?
CALCulate:NIOT:MEAS:MEValuation:MODulation:AVERage?
FETCh:NIOT:MEAS:MEValuation:MODulation:CURRent?
FETCh:NIOT:MEAS:MEValuation:MODulation:AVERage?
FETCh:NIOT:MEAS:MEValuation:MODulation:SDEViation?
READ:NIOT:MEAS:MEValuation:MODulation:CURRent?
READ:NIOT:MEAS:MEValuation:MODulation:AVERage?
READ:NIOT:MEAS:MEValuation:MODulation:SDEViation?
Return the current, average and standard deviation single value results.
Return values:
<1_Reliability> decimal
<2_OutOfTol> decimal
ing the specified modulation limits.
Default unit: %
<3_EVM_RMS> float
Error vector magnitude RMS value
Default unit: %
<4_EVMpeak> float
Error vector magnitude peak value
<5_MagErrorRMS> float
Magnitude error RMS value
Default unit: %
<6_MagErrPeak> float
Magnitude error peak value
Default unit: %
<7_PhErrorRMS> float
Phase error RMS value
Default unit: deg
<8_PhErrorPeak> float
Phase error peak value
Default unit: deg
<9_IQOffset> float
I/Q origin offset
Default unit: dBc
User Manual 1178.5689.02 ─ 12 393

Command Reference
<10_FreqError> float
Carrier frequency error
Default unit: Hz
<11_TimingError> float
Transmit time error
Default unit: Ts
<12_TXpower> float
User equipment power
Default unit: dBm
<13_PeakPower> float
User equipment peak power
Default unit: dBm
<14_SCPower> float
Power in allocated subcarriers
Default unit: dBm
<15_EVM_DMRS> float
Error vector magnitude DMRS value
Default unit: %
<16_MagErrDMRS> float
Magnitude error DMRS value
Default unit: %
<17_PhErrorDMRS> float
Phase error DMRS value
Default unit: deg
<18_Reserved> NAV
For future use
<19_Reserved> NAV
For future use
Usage: Query only
CALCulate:NIOT:MEAS:MEValuation:MODulation:EXTReme?
FETCh:NIOT:MEAS:MEValuation:MODulation:EXTReme?
READ:NIOT:MEAS:MEValuation:MODulation:EXTReme?
Returns the extreme single value results.
User Manual 1178.5689.02 ─ 12 394

Command Reference
Return values:
Default unit: %
<3_EVM_RMS> float
Default unit: %
<4_EVMpeak> float
Default unit: %
Default unit: %
Default unit: %
Default unit: deg
Default unit: deg
<9_IQOffset> float
I/Q origin offset
Default unit: dBc
Default unit: Hz
Transmit time error
Default unit: Ts
<12_TXpowerMin> float
Minimum user equipment power
Default unit: dBm
User Manual 1178.5689.02 ─ 12 395

Command Reference
<13_TXpowerMax> float
Maximum user equipment power
Default unit: dBm
<14_PeakPowerMin> float
Minimum user equipment peak power
Default unit: dBm
<15_PeakPowerMax>float
Maximum user equipment peak power
Default unit: dBm
<16_SCPowerMin> float
Minimum SC power
Default unit: dBm
<17_SCPowerMax> float
Maximum SC power
Default unit: dBm
<18_EVM_DMRS> float
Default unit: %
Default unit: %
Default unit: deg
<21_Reserved> NAV
For future use
<22_Reserved> NAV
For future use
Usage: Query only
4.5.3.19 List Mode Results
The following commands return the list mode results for a selected segment.
To configure the list mode, use the commands described in Chapter 4.5.3.4, "List Mode
For a description of the list mode, see Chapter 4.2.5, "List Mode", on page 282.
User Manual 1178.5689.02 ─ 12 396

Command Reference
The segment number <no> in the following commands refers to the range of measured
segments (1..1000), see CONFigure:NIOT:MEAS:MEValuation:LIST:
LRANge on page 361. It can differ from the absolute segment number used for seg-
ment configuration.
The commands return two reliability indicators. The first indicator covers all measured
segments. The second indicator considers only the selected segment.
FETCh:NIOT:MEAS:MEValuation:LIST:SRELiability?.....................................................397
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:ACLR:CURRent?........................ 398
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:ACLR:AVERage?........................ 398
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:CURRent?......399
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:AVERage?......399
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:EXTReme?.....399
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:SDEViation?... 399
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:CURRent:
SCINdex?........................................................................................................... 400
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:
EXTReme:SCINdex?........................................................................................... 400
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:CURRent?................400
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:AVERage?................400
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:SDEViation?............. 400
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:EXTReme?...............402
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:CURRent?.....................404
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:AVERage?.....................404
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:SDEViation?.................. 404
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:EXTReme?....................404
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:ALL?................405
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:CURRent:
NEGativ?............................................................................................................ 406
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:CURRent:
POSitiv?............................................................................................................. 406
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:AVERage:
NEGativ?............................................................................................................ 406
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:AVERage:
POSitiv?............................................................................................................. 406
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:MINimum:
NEGativ?............................................................................................................ 406
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:MINimum:
POSitiv?............................................................................................................. 406
FETCh:NIOT:MEAS:MEValuation:LIST:SRELiability?
Returns the segment reliability for all measured list mode segments.
A common reliability indicator of zero indicates that the results in all measured seg-
ments are valid. A non-zero value indicates that an error occurred in at least one of the
measured segments. If you get a non-zero common reliability indicator, you can use
this command to retrieve the individual reliability values of all measured segments for
further analysis.
User Manual 1178.5689.02 ─ 12 397

Command Reference
Return values:
<SegReliability> decimal
Comma-separated list of values, one per measured segment
The meaning of the returned values is the same as for the com-
mon reliability indicator, see previous parameter.
Usage: Query only
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:ACLR:CURRent?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:ACLR:AVERage?
Return ACLR single value results for segment <no> in list mode.
Suffix: .
<no> 1..1000
Return values:
Reliability indicator for the segment
<StatistExpired> decimal
Reached statistical length in slots
Default unit: slot
Percentage of measured slots with failed limit check
Default unit: %
<UTRAneg> float
ACLR for the adjacent UTRA channel with lower frequency
<GSMneg> float
ACLR for the adjacent GSM channel with lower frequency
<NBNIOT> float
Power in the NB-IoT channel
<GSMpos> float
ACLR for the adjacent GSM channel with higher frequency
<UTRApos> float
ACLR for the adjacent UTRA channel with higher frequency
User Manual 1178.5689.02 ─ 12 398

Command Reference

Usage: Query only
CURRent?
AVERage?
EXTReme?
SDEViation?
Return the inband emission limit line margin results for segment <no> in list mode.
The CURRent margins indicate the minimum (vertical) distance between the limit line
and the current trace. A negative result indicates that the limit is exceeded.
The AVERage, EXTReme and SDEViation values are calculated from the current mar-
gins.
Suffix: .
<no> 1..1000
Return values:
Default unit: %
<Margin> float
Default unit: dB
Usage: Query only
User Manual 1178.5689.02 ─ 12 399

Command Reference
CURRent:SCINdex?
EXTReme:SCINdex?
Return subcarrier indices for inband emission margins for segment <no> in list mode.
At these SC indices, the CURRent and EXTReme margins have been detected.
Suffix: .
<no> 1..1000
Return values:
Default unit: slot
Default unit: %
<SCindex> decimal
Subcarrier index
Usage: Query only
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:CURRent?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:AVERage?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:
SDEViation?
Returns current, average and standard deviation modulation single value results for
segment <no> in list mode.
Suffix: .
<no> 1..1000
Return values:
<1_Reliability> Reliability Indicator
<2_SegReliability> Reliability indicator for the segment
<3_StatistExpired> Reached statistical length in slots
User Manual 1178.5689.02 ─ 12 400

Command Reference
<4_OutOfTol> Percentage of measured slots with failed limit check

Default unit: %
<5_EVM_RMS> Error vector magnitude RMS value
Default unit: %
<6_EVMpeak> Error vector magnitude peak value
Default unit: %
<7_MagErrorRMS> Magnitude error RMS value
Default unit: %
<8_MagErrPeak> Magnitude error peak value
Default unit: %
<9_PhErrorRMS> Phase error RMS value
Default unit: deg
<10_PhErrorPeak> Phase error peak value
Default unit: deg
<11_IQOffset> I/Q origin offset
Default unit: dBc
<12_FreqError> Carrier frequency error
Default unit: Hz
<13_TimingError> Transmit time error
Default unit: Ts
<14_TXpower> User equipment power
Default unit: dBm
<15_PeakPower> User equipment peak power
Default unit: dBm
<16_SC_Power> Power in allocated subcarriers
Default unit: dBm
<17_EVM_DMRS> Error vector magnitude DMRS value
Default unit: %
<18_MagErrDMRS> Magnitude error DMRS value
Default unit: %
<19_PhErrorDMRS> Phase error DMRS value
Default unit: deg
Usage: Query only
User Manual 1178.5689.02 ─ 12 401

Command Reference
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:EXTReme?
Returns extreme modulation single value results for segment <no> in list mode.
Suffix: .
<no> 1..1000
Return values:
<2_SegReliability> decimal
<3_StatistExpired> decimal
Default unit: slot
Default unit: %
<5_EVM_RMS> float
Default unit: %
<6_EVMpeak> float
Default unit: %
Default unit: %
Default unit: %
Default unit: deg
Default unit: deg
<11_IQOffset> float
I/Q origin offset
Default unit: dBc
User Manual 1178.5689.02 ─ 12 402

Command Reference
Default unit: Hz
Transmit time error
Default unit: Ts
<14_TXpowerMin> float
Minimum user equipment power
Default unit: dBm
<15_TXpowerMax> float
Maximum user equipment power
Default unit: dBm
<16_PeakPowerMin> float
Minimum user equipment peak power
Default unit: dBm
<17_PeakPowerMax>float
Maximum user equipment peak power
Default unit: dBm
<18_SC_PowerMin> float
Minimum SC power
Default unit: dBm
<19_SC_PowerMax> float
Maximum SC power
Default unit: dBm
<20_EVM_DMRS> float
Default unit: %
Default unit: %
Default unit: deg
Usage: Query only
User Manual 1178.5689.02 ─ 12 403

Command Reference
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:CURRent?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:AVERage?
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:SDEViation?
Return spectrum emission single value results for segment <no> in list mode.
Suffix: .
<no> 1..1000
Return values:
Default unit: %
Default unit: %
<OBW> float
Occupied bandwidth
Default unit: Hz
<TXpower> float
Total TX power within 400 kHz
Default unit: dBm
Usage: Query only
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:EXTReme?
Returns spectrum emission extreme results for segment <no> in list mode.
Suffix: .
<no> 1..1000
Return values:
User Manual 1178.5689.02 ─ 12 404

Command Reference
Default unit: slot
Default unit: %
<OBW> float
Occupied bandwidth
Default unit: Hz
<TXpowerMin> float
Minimum total TX power
Default unit: dBm
<TXpowerMax> float
Maximum total TX power
Default unit: dBm
Usage: Query only
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:ALL?
Returns limit line margin values, i.e. vertical distances between the spectrum emission
mask limit line and a trace, for segment <no> in list mode.
Suffix: .
<no> 1..1000
Return values:
Default unit: %
Default unit: %
User Manual 1178.5689.02 ─ 12 405

Command Reference
<MarginCurrNeg> float
For the current trace, area 1 to 12, negative frequency offsets
Default unit: dB
<MarginCurrPos> float
For the current trace, area 1 to 12, positive frequency offsets
<MarginAvgNeg> float
For the average trace, area 1 to 12, negative frequency offsets
Default unit: dB
<MarginAvgPos> float
For the average trace, area 1 to 12, positive frequency offsets
Default unit: dB
<MarginMinNeg> float
For the maximum trace, area 1 to 12, negative frequency offsets
Default unit: dB
<MarginMinPos> float
For the maximum trace, area 1 to 12, positive frequency offsets
Default unit: dB
Usage: Query only
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:
CURRent:NEGativ?
CURRent:POSitiv?
AVERage:NEGativ?
AVERage:POSitiv?
MINimum:NEGativ?
MINimum:POSitiv?
Return spectrum emission mask margin results for segment <no> in list mode.
User Manual 1178.5689.02 ─ 12 406

Command Reference
The individual commands provide results for the CURRent, AVERage and maximum
traces (resulting in MINimum margins) for NEGative and POSitive offset frequen-
cies.
Each command returns pairs of X and Y values of the margins for emission mask
areas 1 to 12. Result array structure:
<Reliability>, <SegReliability>, <StatistExpired>, <OutOfTolerance>, {<MarginX>,
<MarginY>}area 1, {...}area 2, ..., {...}area 12
For inactive areas, NCAP is returned.

Suffix: .
<no> 1..1000
Return values:
Default unit: %
Default unit: %
<MarginMinPosX> float
X-position of margin
Default unit: Hz
<MarginMinPosY> float
Y-value of margin
Default unit: dB
Usage: Query only
4.5.4 Combined Signal Path Commands
For some settings, the command to be used depends on the active scenario. While the
combined signal path (CSP) scenario is active, these settings are configured via com-
mands of the signaling application. While the standalone (SA) scenario is active, they
are configured via measurement commands.
User Manual 1178.5689.02 ─ 12 407

Command Reference
The following mapping tables provide an overview for general measurement settings
and for multi-evaluation measurement commands.
Table 4-5: Mapping for general measurement settings
Setting Commands for SA scenario Commands for CSP scenario
Connector, converter ROUTe:NIOT:MEAS:SCENario:SALone ROUTe:NIOT:MEAS:SCENario:CSPath

ROUTe:NIOT:SIGN:SCENario[:
FLEXible]:SCELl
External attenuation CONFigure:NIOT:MEAS:RFSettings: CONFigure:NIOT:SIGN:RFSettings:

EATTenuation EATTenuation:INPut
Band CONFigure:NIOT:MEAS:BAND CONFigure:NIOT:SIGN:BAND
Frequency, channel CONFigure:NIOT:MEAS:RFSettings: CONFigure:NIOT:SIGN:RFSettings:

FREQuency CHANnel:UL
Frequency offset CONFigure:NIOT:MEAS:RFSettings: CONFigure:NIOT:SIGN:RFSettings:

FOFFset FOFFset:UL
Expected nominal CONFigure:NIOT:MEAS:RFSettings: CONFigure:NIOT:SIGN:RFSettings:

power ENPower ENPMode
CONFigure:NIOT:SIGN:RFSettings:
ENPower
User margin CONFigure:NIOT:MEAS:RFSettings: CONFigure:NIOT:SIGN:RFSettings:

UMARgin UMARgin
Mixer level offset CONFigure:NIOT:MEAS:RFSettings: CONFigure:NIOT:SIGN:RFSettings:

MLOFfset MLOFfset
Table 4-6: Mapping for multi-evaluation measurement commands
Setting Commands for SA scenario Commands for CSP scenario
Measurement mode CONFigure:NIOT:MEAS:MEValuation: Fixed value NORMal

MMODe
Subcarrier spacing CONFigure:NIOT:MEAS:MEValuation: CONFigure:NIOT:SIGN:CELL:SCSPacing

SCSPacing
Resource allocation CONFigure:NIOT:MEAS:MEValuation: CONFigure:NIOT:SIGN:CONNection:RMC:

SUBCarrier UL
CONFigure:NIOT:MEAS:MEValuation: CONFigure:NIOT:SIGN:CONNection:
NRUNits UDEFined:UL[:SET<setNr>]
CONFigure:NIOT:MEAS:MEValuation: CONFigure:NIOT:SIGN:CONNection:RMC:
NREPetitions FORMat?
CONFigure:NIOT:MEAS:MEValuation: CONFigure:NIOT:SIGN:CONNection:
MODulation:MSCHeme UDEFined:FORMat?
Physical cell ID CONFigure:NIOT:MEAS:MEValuation: CONFigure:NIOT:SIGN:CELL:PCID

PLCid
User Manual 1178.5689.02 ─ 12 408

List of commands

ABORt:NIOT:MEAS:MEValuation............................................................................................................. 348
CALCulate:NIOT:MEAS:MEValuation:ACLR:AVERage?..........................................................................388
CALCulate:NIOT:MEAS:MEValuation:ACLR:CURRent?.......................................................................... 388
CALCulate:NIOT:MEAS:MEValuation:MODulation:AVERage?................................................................ 393
CALCulate:NIOT:MEAS:MEValuation:MODulation:CURRent?.................................................................393
CALCulate:NIOT:MEAS:MEValuation:MODulation:EXTReme?............................................................... 394
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:AVERage?................................................................ 391
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:CURRent?................................................................ 391
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:MAXimum?............................................................... 391
CALCulate:NIOT:MEAS:MEValuation:PDYNamics:MINimum?................................................................ 391
CALCulate:NIOT:MEAS:MEValuation:SEMask:AVERage?...................................................................... 383
CALCulate:NIOT:MEAS:MEValuation:SEMask:CURRent?...................................................................... 383
CALCulate:NIOT:MEAS:MEValuation:SEMask:EXTReme?..................................................................... 384
CONFigure:NIOT:MEAS:BAND................................................................................................................ 345
CONFigure:NIOT:MEAS:MEValuation:DSS..............................................................................................356
CONFigure:NIOT:MEAS:MEValuation:FSYRange....................................................................................357
CONFigure:NIOT:MEAS:MEValuation:LIMit:ACLR:GSM..........................................................................374
CONFigure:NIOT:MEAS:MEValuation:LIMit:ACLR:UTRA........................................................................ 374
CONFigure:NIOT:MEAS:MEValuation:LIMit:EVMagnitude.......................................................................369
CONFigure:NIOT:MEAS:MEValuation:LIMit:FERRor............................................................................... 371
CONFigure:NIOT:MEAS:MEValuation:LIMit:IBE.......................................................................................372
CONFigure:NIOT:MEAS:MEValuation:LIMit:IBE:IQOFfset....................................................................... 373
CONFigure:NIOT:MEAS:MEValuation:LIMit:IQOFfset..............................................................................372
CONFigure:NIOT:MEAS:MEValuation:LIMit:MERRor...............................................................................370
CONFigure:NIOT:MEAS:MEValuation:LIMit:PDYNamics......................................................................... 376
CONFigure:NIOT:MEAS:MEValuation:LIMit:PERRor............................................................................... 371
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:LIMit<no>.............................................................. 375
CONFigure:NIOT:MEAS:MEValuation:LIMit:SEMask:OBWLimit..............................................................375
CONFigure:NIOT:MEAS:MEValuation:LIST..............................................................................................360
CONFigure:NIOT:MEAS:MEValuation:LIST:LRANge............................................................................... 361
CONFigure:NIOT:MEAS:MEValuation:LIST:OSINdex.............................................................................. 361
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:ACLR...........................................................365
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation................................................. 364
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask.......................................................365
CONFigure:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SETup......................................................... 361
CONFigure:NIOT:MEAS:MEValuation:MMODe........................................................................................353
CONFigure:NIOT:MEAS:MEValuation:MODulation:EEPeriods:NPUSch:LAGGing..................................358
CONFigure:NIOT:MEAS:MEValuation:MODulation:EEPeriods:NPUSch:LEADing.................................. 357
CONFigure:NIOT:MEAS:MEValuation:MODulation:MSCHeme................................................................357
CONFigure:NIOT:MEAS:MEValuation:MOEXception............................................................................... 354
CONFigure:NIOT:MEAS:MEValuation:NPFormat.....................................................................................354
CONFigure:NIOT:MEAS:MEValuation:NREPetitions................................................................................356
CONFigure:NIOT:MEAS:MEValuation:NRUNits....................................................................................... 355
CONFigure:NIOT:MEAS:MEValuation:NSLots......................................................................................... 354
CONFigure:NIOT:MEAS:MEValuation:PLCid........................................................................................... 356
CONFigure:NIOT:MEAS:MEValuation:REPetition.................................................................................... 353
CONFigure:NIOT:MEAS:MEValuation:RESult:ACLR............................................................................... 351
User Manual 1178.5689.02 ─ 12 409

List of commands
CONFigure:NIOT:MEAS:MEValuation:RESult:EVMagnitude................................................................... 351
CONFigure:NIOT:MEAS:MEValuation:RESult:IEMissions........................................................................351
CONFigure:NIOT:MEAS:MEValuation:RESult:IQ..................................................................................... 351
CONFigure:NIOT:MEAS:MEValuation:RESult:MERRor........................................................................... 351
CONFigure:NIOT:MEAS:MEValuation:RESult:PDYNamics......................................................................351
CONFigure:NIOT:MEAS:MEValuation:RESult:PERRor............................................................................351
CONFigure:NIOT:MEAS:MEValuation:RESult:PMONitor......................................................................... 351
CONFigure:NIOT:MEAS:MEValuation:RESult:SEMask............................................................................351
CONFigure:NIOT:MEAS:MEValuation:RESult:TXM................................................................................. 351
CONFigure:NIOT:MEAS:MEValuation:RESult[:ALL].................................................................................350
CONFigure:NIOT:MEAS:MEValuation:SCONdition.................................................................................. 353
CONFigure:NIOT:MEAS:MEValuation:SCOunt:MODulation.................................................................... 358
CONFigure:NIOT:MEAS:MEValuation:SCOunt:POWer............................................................................360
CONFigure:NIOT:MEAS:MEValuation:SCOunt:SPECtrum:ACLR............................................................359
CONFigure:NIOT:MEAS:MEValuation:SCOunt:SPECtrum:SEMask........................................................ 358
CONFigure:NIOT:MEAS:MEValuation:SCSPacing...................................................................................354
CONFigure:NIOT:MEAS:MEValuation:SPECtrum:ACLR:ENABle............................................................ 359
CONFigure:NIOT:MEAS:MEValuation:SPECtrum:SEMask:OBWMode................................................... 359
CONFigure:NIOT:MEAS:MEValuation:SUBCarrier...................................................................................355
CONFigure:NIOT:MEAS:MEValuation:TOUT........................................................................................... 352
CONFigure:NIOT:MEAS:RFSettings:EATTenuation................................................................................. 344
CONFigure:NIOT:MEAS:RFSettings:ENPower........................................................................................ 346
CONFigure:NIOT:MEAS:RFSettings:FOFFset......................................................................................... 346
CONFigure:NIOT:MEAS:RFSettings:FREQuency.................................................................................... 345
CONFigure:NIOT:MEAS:RFSettings:MLOFfset........................................................................................347
CONFigure:NIOT:MEAS:RFSettings:UMARgin........................................................................................ 346
FETCh:NIOT:MEAS:MEValuation:ACLR:AVERage?................................................................................388
FETCh:NIOT:MEAS:MEValuation:ACLR:CURRent?................................................................................ 388
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:AVERage?....................................................................377
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:CURRent?.................................................................... 377
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:MAXimum?...................................................................377
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:AVERage?......................................................... 378
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:CURRent?......................................................... 378
FETCh:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:MAXimum?........................................................ 378
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:AVERage?........................................................... 381
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:CURRent:SCINdex?............................................ 381
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:CURRent?........................................................... 381
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:EXTReme:SCINdex?...........................................381
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:EXTReme?.......................................................... 381
FETCh:NIOT:MEAS:MEValuation:IEMission:MARGin:SDEViation?........................................................ 381
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:ACLR:AVERage?...............................................398
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:ACLR:CURRent?............................................... 398
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:AVERage?.......................... 399
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:CURRent:SCINdex?........... 400
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:CURRent?.......................... 399
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:EXTReme:SCINdex?..........400
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:EXTReme?......................... 399
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:IEMission:MARGin:SDEViation?....................... 399
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:AVERage?..................................... 400
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:CURRent?......................................400
User Manual 1178.5689.02 ─ 12 410

List of commands
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:EXTReme?.................................... 402
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:MODulation:SDEViation?...................................400
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:AVERage?........................................... 404
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:CURRent?........................................... 404
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:EXTReme?.......................................... 404
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:ALL?......................................405
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:AVERage:NEGativ?.............. 406
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:AVERage:POSitiv?............... 406
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:CURRent:NEGativ?.............. 406
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:CURRent:POSitiv?................406
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:MINimum:NEGativ?.............. 406
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:MARGin:MINimum:POSitiv?................406
FETCh:NIOT:MEAS:MEValuation:LIST:SEGMent<no>:SEMask:SDEViation?........................................ 404
FETCh:NIOT:MEAS:MEValuation:LIST:SRELiability?.............................................................................. 397
FETCh:NIOT:MEAS:MEValuation:MERRor:AVERage?............................................................................379
FETCh:NIOT:MEAS:MEValuation:MERRor:CURRent?............................................................................379
FETCh:NIOT:MEAS:MEValuation:MERRor:MAXimum?...........................................................................379
FETCh:NIOT:MEAS:MEValuation:MODulation:AVERage?...................................................................... 393
FETCh:NIOT:MEAS:MEValuation:MODulation:CURRent?.......................................................................393
FETCh:NIOT:MEAS:MEValuation:MODulation:EXTReme?..................................................................... 394
FETCh:NIOT:MEAS:MEValuation:MODulation:SDEViation?....................................................................393
FETCh:NIOT:MEAS:MEValuation:PDYNamics:AVERage?...................................................................... 391
FETCh:NIOT:MEAS:MEValuation:PDYNamics:CURRent?...................................................................... 391
FETCh:NIOT:MEAS:MEValuation:PDYNamics:MAXimum?..................................................................... 391
FETCh:NIOT:MEAS:MEValuation:PDYNamics:MINimum?...................................................................... 391
FETCh:NIOT:MEAS:MEValuation:PDYNamics:SDEViation?................................................................... 391
FETCh:NIOT:MEAS:MEValuation:PERRor:AVERage?............................................................................ 380
FETCh:NIOT:MEAS:MEValuation:PERRor:CURRent?............................................................................ 380
FETCh:NIOT:MEAS:MEValuation:PERRor:MAXimum?........................................................................... 380
FETCh:NIOT:MEAS:MEValuation:SEMask:AVERage?............................................................................ 383
FETCh:NIOT:MEAS:MEValuation:SEMask:CURRent?............................................................................ 383
FETCh:NIOT:MEAS:MEValuation:SEMask:EXTReme?........................................................................... 384
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:ALL?.......................................................................385
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:AVERage:NEGativ?............................................... 386
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:AVERage:POSitiv?................................................ 386
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:CURRent:NEGativ?............................................... 386
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:CURRent:POSitiv?.................................................386
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:MINimum:NEGativ?............................................... 386
FETCh:NIOT:MEAS:MEValuation:SEMask:MARGin:MINimum:POSitiv?.................................................386
FETCh:NIOT:MEAS:MEValuation:SEMask:SDEViation?......................................................................... 383
FETCh:NIOT:MEAS:MEValuation:STATe:ALL?........................................................................................ 349
FETCh:NIOT:MEAS:MEValuation:STATe?................................................................................................348
FETCh:NIOT:MEAS:MEValuation:TRACe:ACLR:AVERage?................................................................... 387
FETCh:NIOT:MEAS:MEValuation:TRACe:ACLR:CURRent?................................................................... 387
FETCh:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:AVERage?.........................................................378
FETCh:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:CURRent?......................................................... 378
FETCh:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:MAXimum?........................................................378
FETCh:NIOT:MEAS:MEValuation:TRACe:IEMissions?............................................................................380
FETCh:NIOT:MEAS:MEValuation:TRACe:IQ?......................................................................................... 388
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:AVERage?......................................................... 390
User Manual 1178.5689.02 ─ 12 411

List of commands
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:CURRent?......................................................... 390
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:MAXimum?........................................................ 390
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:AVERage?...............................................391
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:CURRent?............................................... 391
FETCh:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:MAXimum?..............................................391
FETCh:NIOT:MEAS:MEValuation:TRACe:PMONitor?............................................................................. 389
FETCh:NIOT:MEAS:MEValuation:TRACe:SEMask:AVERage?............................................................... 382
FETCh:NIOT:MEAS:MEValuation:TRACe:SEMask:CURRent?............................................................... 382
FETCh:NIOT:MEAS:MEValuation:TRACe:SEMask:MAXimum?.............................................................. 383
INITiate:NIOT:MEAS:MEValuation............................................................................................................ 348
READ:NIOT:MEAS:MEValuation:ACLR:AVERage?................................................................................. 388
READ:NIOT:MEAS:MEValuation:ACLR:CURRent?................................................................................. 388
READ:NIOT:MEAS:MEValuation:EVMagnitude:AVERage?..................................................................... 378
READ:NIOT:MEAS:MEValuation:EVMagnitude:CURRent?..................................................................... 377
READ:NIOT:MEAS:MEValuation:EVMagnitude:MAXimum?.................................................................... 378
READ:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:AVERage?...........................................................378
READ:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:CURRent?...........................................................378
READ:NIOT:MEAS:MEValuation:EVMagnitude:PEAK:MAXimum?..........................................................378
READ:NIOT:MEAS:MEValuation:MERRor:AVERage?............................................................................. 379
READ:NIOT:MEAS:MEValuation:MERRor:CURRent?............................................................................. 379
READ:NIOT:MEAS:MEValuation:MERRor:MAXimum?............................................................................ 379
READ:NIOT:MEAS:MEValuation:MODulation:AVERage?........................................................................393
READ:NIOT:MEAS:MEValuation:MODulation:CURRent?........................................................................ 393
READ:NIOT:MEAS:MEValuation:MODulation:EXTReme?.......................................................................394
READ:NIOT:MEAS:MEValuation:MODulation:SDEViation?..................................................................... 393
READ:NIOT:MEAS:MEValuation:PDYNamics:AVERage?....................................................................... 392
READ:NIOT:MEAS:MEValuation:PDYNamics:CURRent?........................................................................391
READ:NIOT:MEAS:MEValuation:PDYNamics:MAXimum?...................................................................... 392
READ:NIOT:MEAS:MEValuation:PDYNamics:MINimum?........................................................................392
READ:NIOT:MEAS:MEValuation:PDYNamics:SDEViation?.....................................................................392
READ:NIOT:MEAS:MEValuation:PERRor:AVERage?..............................................................................380
READ:NIOT:MEAS:MEValuation:PERRor:CURRent?..............................................................................380
READ:NIOT:MEAS:MEValuation:PERRor:MAXimum?.............................................................................380
READ:NIOT:MEAS:MEValuation:SEMask:AVERage?............................................................................. 383
READ:NIOT:MEAS:MEValuation:SEMask:CURRent?..............................................................................383
READ:NIOT:MEAS:MEValuation:SEMask:EXTReme?............................................................................ 384
READ:NIOT:MEAS:MEValuation:SEMask:SDEViation?...........................................................................383
READ:NIOT:MEAS:MEValuation:TRACe:ACLR:AVERage?.................................................................... 387
READ:NIOT:MEAS:MEValuation:TRACe:ACLR:CURRent?.....................................................................387
READ:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:AVERage?.......................................................... 379
READ:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:CURRent?.......................................................... 378
READ:NIOT:MEAS:MEValuation:TRACe:EVMSymbol:MAXimum?......................................................... 379
READ:NIOT:MEAS:MEValuation:TRACe:IEMissions?............................................................................. 380
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:AVERage?...........................................................390
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:CURRent?...........................................................390
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:MAXimum?..........................................................390
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:AVERage?................................................ 391
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:CURRent?................................................ 391
READ:NIOT:MEAS:MEValuation:TRACe:PDYNamics:POST:MAXimum?............................................... 391
READ:NIOT:MEAS:MEValuation:TRACe:PMONitor?...............................................................................389
User Manual 1178.5689.02 ─ 12 412

List of commands
READ:NIOT:MEAS:MEValuation:TRACe:SEMask:AVERage?.................................................................383
READ:NIOT:MEAS:MEValuation:TRACe:SEMask:CURRent?.................................................................383
READ:NIOT:MEAS:MEValuation:TRACe:SEMask:MAXimum?................................................................383
ROUTe:NIOT:MEAS:SCENario:CSPath................................................................................................... 343
ROUTe:NIOT:MEAS:SCENario:MAPRotocol............................................................................................343
ROUTe:NIOT:MEAS:SCENario:SALone................................................................................................... 342
ROUTe:NIOT:MEAS:SCENario?...............................................................................................................343
ROUTe:NIOT:MEAS?................................................................................................................................344
STOP:NIOT:MEAS:MEValuation...............................................................................................................348
TRIGger:NIOT:MEAS:MEValuation:CATalog:SOURce?........................................................................... 367
TRIGger:NIOT:MEAS:MEValuation:DELay...............................................................................................368
TRIGger:NIOT:MEAS:MEValuation:LIST:MODE.......................................................................................366
TRIGger:NIOT:MEAS:MEValuation:MGAP............................................................................................... 369
TRIGger:NIOT:MEAS:MEValuation:SLOPe.............................................................................................. 368
TRIGger:NIOT:MEAS:MEValuation:SOURce........................................................................................... 367
TRIGger:NIOT:MEAS:MEValuation:THReshold........................................................................................368
TRIGger:NIOT:MEAS:MEValuation:TOUT................................................................................................369
User Manual 1178.5689.02 ─ 12 413

R&S®CMW290/500 NB-IoT NPRACH Measurement
General Description
5 NB-IoT NPRACH Measurement

The NB-IoT NPRACH measurement provides quick and flexible tests on NB-IoT FDD
random access preambles. The tests cover the following UE transmitter properties:
● Modulation accuracy for each NPRACH symbol (EVM, magnitude error, phase
error)
● Transmit OFF power, transmit ON power and power ramping between them (power
dynamics)
The NPRACH measurement requires option R&S CMW-KM300.
5.1 What's New

This documentation describes version 3.8.30 and higher of the NB-IoT NPRACH mea-
surement. Compared to version 3.7.30, it provides only editorial changes.

The NB-IoT NPRACH measurement captures an uplink (UL) NPRACH signal and pro-
vides TX measurement results for the random access preambles. Only FDD signals
can be measured. Option R&S CMW-KM300 is required.
The following sections describe how to perform and configure the measurement.
● Test Setup............................................................................................................. 414
● How to Measure an Uplink NPRACH Signal.........................................................414
● Defining the Scope of the Measurement...............................................................415
● Parallel Signaling and Measurement.................................................................... 416
● Calculation of Modulation Results.........................................................................416
● NB-IoT Preamble Structure...................................................................................417
5.2.1 Test Setup
Connect the external RF signal source (mobile station, signal generator etc.) to one of
the bidirectional RF connectors on the front panel of the R&S CMW.
5.2.2 How to Measure an Uplink NPRACH Signal
The measurement expects an NB-IoT NPRACH UL signal. Any other signals do not
yield measurement results (e.g. an NB-IoT UL signal for an established connection).
User Manual 1178.5689.02 ─ 12 414

General Description
After connecting your NB-IoT UE to the R&S CMW, you have to adjust at least the fol-
lowing measurement settings to the properties of the analyzed NPRACH signal:
● Analyzer "Frequency"
● "Expected Nominal Power"
Optionally "User Margin" and "External Attenuation (Input)"
Recommended values:
– "Expected Nominal Power" = peak power of the UE signal during the measure-
ment
– "User Margin" = 0 dB
The smallest possible value of the "Expected Nominal Power" plus the "User Mar-
gin" ensures the maximum dynamic range.
● "NPRACH Preamble Format"
The default trigger settings are often suitable.
5.2.3 Defining the Scope of the Measurement
A single-shot NB-IoT NPRACH measurement comprises one measurement cycle

which comprises a configurable number of measurement intervals (statistic count).
In this context, two types of result views must be distinguished:
● Single-preamble measurements evaluate one preamble per measurement inter-
val. The related views display results for the current measurement interval (one
preamble). They also provide a statistical evaluation for the already measured pre-
ambles (e.g. average within measurement cycle, extreme value since start of mea-
surement).
Examples for single-preamble result views are "Error Vector Magnitude" and
"Power Dynamics".
● Multi-preamble measurements evaluate up to 32 consecutive preambles per
measurement interval. The related views present the results per preamble, for all
preambles of the current measurement interval. No statistical evaluation over sev-
eral measurement intervals is performed.
The preambles captured within one measurement interval are labeled 1 to n, with n
≤ 32. Single-preamble measurements evaluate the preamble labeled 1.
The time between two preambles is configurable. If no preamble is found, the mea-
surement continues and there are no demodulation results for that label.
Examples for multi-preamble result views are "EVM vs Preamble" and "Power vs
Preamble".
The scope of the measurement is configured in section "Measurement Control" of the
configuration tree. The most important parameters are:
● "Repetition" on page 429
● "Number of Preambles" on page 430
● "Period of Preambles" on page 430
● "Statistic Count" on page 430
● "Statistic Count" on page 431
User Manual 1178.5689.02 ─ 12 415

General Description
Example: Limited sequence of preambles with increasing power

Scenario: A sequence of 10 preambles with increasing power is measured. Main result
of interest is the TX power of the individual preambles (verify correct ramping up of
preamble power by UE).
Used view: "Power vs Preamble"
Settings: statistic count = 1, number of preambles = 10, repetition = single shot
Example: Statistical evaluation for preambles with constant power

Scenario: The EVM is measured for 100 preambles, so that the average and the maxi-
mum value can be evaluated.
Used view: "EVM"
Settings: statistic count = 100, number of preambles = 1, repetition = single shot
5.2.4 Parallel Signaling and Measurement
The NPRACH measurement can be used in parallel to the NB-IoT signaling application
(option R&S CMW-KS300). The signaling application emulates an NB-IoT cell signal
so that the UE tries to attach and sends random access preambles. These preambles
can then be measured using the NPRACH measurement.
To use both applications in parallel, the combined signal path scenario must be activa-
ted (see "Scenario = Combined Signal Path" on page 306). Most signal routing and
analyzer settings are then configured by the signaling application. The NPRACH mea-
surement displays the corresponding signaling settings instead of its own settings.
These signaling settings can be configured both in the measurement GUI and in the
GUI of the signaling application.
To configure these settings via remote commands, the commands of the signaling
application must be used. For a mapping table, see Chapter 5.5.4, "Combined Signal
Path Commands", on page 471.
The most important signaling parameters not relevant for standalone measurements
can nevertheless be configured both in the measurement GUI and in the GUI of the
signaling application. In the measurement GUI, they can be accessed via hotkeys.
Whenever the combined signal path scenario is activated or the controlling application
is changed, the NPRACH trigger signal provided by the controlling signaling application
is selected automatically as trigger source.
5.2.5 Calculation of Modulation Results
Modulation results are based on a comparison between the measured signal and an
ideal reference waveform.
3GPP TS 36.101, annex F defines that the EVM calculation must be based on two dif-
ferent FFT processing windows in the time domain, separated by the "EVM window
User Manual 1178.5689.02 ─ 12 416

General Description
length". The minimum test requirement applies to the larger of the two obtained EVM
values.
The two FFT processing windows start in the cyclic prefix (CP) at the beginning of the
preamble. The cyclic prefix is a copy of the end of the preamble sequence.
Preamble
copy end of preamble

Cyclic prefix (CP)
Figure 5-1: Cyclic extension of preamble
The EVM window between the start of the two FFT processing windows is centered on
the cyclic prefix. The EVM window length is specified in the standard, depending on
the preamble format (see 3GPP TS 36.101, section F.5.F).
FFT processing window for EVM l
EVM window EVM window
FFT processing window for EVM h
Figure 5-2: EVM window definition
The EVM for a signal with good modulation accuracy is expected to be largely inde-
pendent of the EVM window size. Differences between EVMh and EVMl arise, for
example, due to the effects of time domain windowing of FIR pulse shaping.
EVM window settings

Use the settings in the section "Config... > Measurement Control > Modulation > EVM
Window Length" to adjust the length of the EVM window (see "EVM Window Length"
on page 431). The minimum value of one FFT symbol means that EVMh equals EVMl.
Use the setting "Config... > Measurement Control > Modulation > EVM Window Posi-
tion" to select whether the result diagrams (traces) are calculated for low or high EVM
window position, see "EVM Window Position" on page 431. Statistical tables provide
results for both window positions.
5.2.6 NB-IoT Preamble Structure
In the time domain, a single preamble consists of four symbol groups. And a symbol
group consists of one cyclic prefix (CP) and five symbols.
The length of the CP depends on the preamble format (PF). There are two preamble
formats defined by 3GPP, format 0 and format 1. The symbol length is fixed.
Lengths are often defined in multiples of the basic time unit Ts (1 Ts = 1/30.72 MHz ≈
32.55 ns).
User Manual 1178.5689.02 ─ 12 417

GUI Reference
The following figure provides an overview.
One preamble without repetitions (PF0: 5.6 ms, PF1: 6.4 ms)
One symbol group
Cyclic prefix
Symbol Symbol Symbol Symbol Symbol
PF0: 2048 Ts
8192 Ts 8192 Ts 8192 Ts 8192 Ts 8192 Ts
PF1: 8192 Ts
Figure 5-3: Preamble structure in the time domain
The frequency domain covers 180 kHz and is divided into 48 subcarriers, each
3.75 kHz wide. The subcarriers are numbered from 0 to 47.
Preambles are transmitted on a single subcarrier with frequency hopping between the
symbol groups. The following figure shows an example for the transmission of a single
preamble.
Subcarriers
Time
Figure 5-4: Single preamble with frequency hopping between symbol groups
For more details, see 3GPP TS 36.211 section 10.1.6.1 "Time and frequency struc-
ture".
5.3 GUI Reference

The following sections provide detailed reference information on the graphical user
interface (GUI) and the parameters of the NB-IoT NPRACH measurement.
User Manual 1178.5689.02 ─ 12 418

GUI Reference
● Signal Routing and Analyzer Settings...................................................................428
● Measurement Control Settings..............................................................................428
● Limit Settings.........................................................................................................434
● Shortcut Configuration.......................................................................................... 436
● Additional Softkeys and Hotkeys...........................................................................436
NPRACH (Softkey)
Remote command:
INITiate:NIOT:MEAS:PRACh
STOP:NIOT:MEAS:PRACh
ABORt:NIOT:MEAS:PRACh
FETCh:NIOT:MEAS:PRACh:STATe?
FETCh:NIOT:MEAS:PRACh:STATe:ALL?
The results of the NB-IoT NPRACH measurement are displayed in several different
views. Use the "Display" parameters to select the views and to change the appearance
and contents of the views. The views are described in the following sections.
● Overview............................................................................................................... 419
● Views EVM, Magnitude Error, Phase Error...........................................................420
● Views EVM vs Preamble, Power vs Preamble......................................................421
● View I/Q Constellation...........................................................................................423
● View Power Dynamics.......................................................................................... 424
● View TX Measurement..........................................................................................425
● Selecting and Modifying Views............................................................................. 426
● Using Markers....................................................................................................... 426
● Common View Elements.......................................................................................427
5.3.2.1 Overview
In the overview, a selection of the following results can be displayed:

● Error vector magnitude
User Manual 1178.5689.02 ─ 12 419

GUI Reference
● Magnitude error
● Phase error
● Error vector magnitude vs preamble
● Power vs preamble
● Power dynamics
● Most important results of the view "TX Measurement"
Figure 5-5: NPRACH result overview
The results to be measured and displayed in the overview can be limited using the hot-
key "Assign Views", see Chapter 4.3.8, "Additional Softkeys and Hotkeys",
on page 326.
You can enlarge one of the diagrams in the overview and show a detailed view with
additional measurement results, see Chapter 5.3.2.7, "Selecting and Modifying Views",
on page 426. The traces are described in the following sections.
5.3.2.2 Views EVM, Magnitude Error, Phase Error
This section applies to the following detailed views:

● "Error Vector Magnitude"
● "Magnitude Error"
● "Phase Error"
User Manual 1178.5689.02 ─ 12 420

GUI Reference
Each of these single-preamble views shows a diagram and a statistical overview of

results.
Figure 5-6: Error Vector Magnitude view
The diagram shows the EVM / magnitude error / phase error in all 20 symbols of the
preamble. The values are RMS-averaged over the samples in each symbol.
For a description of the table rows, see Chapter 5.3.2.6, "View TX Measurement",
on page 425.
For table columns and other elements, refer to Chapter 5.3.2.9, "Common View Ele-
ments", on page 427.
● FETCh:NIOT:MEAS:PRACh:TRACe:EVM:CURRent? etc.
● FETCh:NIOT:MEAS:PRACh:TRACe:MERRor:CURRent? etc.
● FETCh:NIOT:MEAS:PRACh:TRACe:PERRor:CURRent? etc.
5.3.2.3 Views EVM vs Preamble, Power vs Preamble
This section applies to the following detailed views:

● "Error Vector Magnitude vs Preamble"
● "Power vs Preamble"
Each of these multi-preamble views shows a diagram and a statistical overview of
results.
User Manual 1178.5689.02 ─ 12 421

GUI Reference
Figure 5-7: EVM vs Preamble view
Result diagram
The diagram shows results for a configurable number of preambles (up to 32), labeled
1 to n. The preambles are captured within one measurement interval, with a configura-
ble periodicity.
● "Error Vector Magnitude vs Preamble":
The diagram displays EVM RMS values. For each preamble, either the result
determined for low EVM window position or the result determined for high EVM
window position is shown - whichever is higher. So for this diagram, the setting
EVM Window Position is ignored.
● "Power vs Preamble":
The diagram displays TX power values (received power, RMS averaged over all
samples within the preamble duration).
● FETCh:NIOT:MEAS:PRACh:TRACe:EVPReamble? etc.
● FETCh:NIOT:MEAS:PRACh:TRACe:PVPReamble? etc.
Result table
The table below the diagram shows additional results. Each column corresponds to
one preamble with the preamble label indicated as column title.
The upper rows correspond to the results presented in the "TX Measurement" view.
For a description, see Chapter 5.3.2.6, "View TX Measurement", on page 425.
User Manual 1178.5689.02 ─ 12 422

GUI Reference
The row "Reliability" provides a reliability indicator for each preamble. For a description
of the individual values, see Chapter 5.5.1.5, "Reliability Indicator", on page 442.
For query of the table contents via remote control, see FETCh:NIOT:MEAS:
PRACh:MODulation:PREamble<Number>? etc.
5.3.2.4 View I/Q Constellation
This single-preamble view shows the symbols as points in the I/Q plane.
Figure 5-8: I/Q constellation diagram
An NPRACH preamble signal is not modulated. So all 20 symbols are on a single point
in the I/Q plane. It would be hard to read such an I/Q diagram.
To improve the usefulness of the diagram, the measurement maps the four symbol
groups to the positions of QPSK symbols. The first symbol group is on the upper right.
The other symbol groups follow anti-clockwise (2nd on upper left, 3rd on lower left, 4th
on lower right).
So in each QPSK position, you see the five symbols of a symbol group.
For the elements on the right, refer to Chapter 5.3.2.9, "Common View Elements",
on page 427.
For query of the diagram contents via remote control, see FETCh:NIOT:MEAS:
PRACh:TRACe:IQ?.
User Manual 1178.5689.02 ─ 12 423

GUI Reference
5.3.2.5 View Power Dynamics
This single-preamble view shows a diagram and a statistical overview of related power
results.
Figure 5-9: Power Dynamics view
The diagram shows the UE output power vs. time, sampled with 96 Ts (3.125 µs). The
trace covers the range from -1200 µs to +7596.875 µs relative to the start of the pre-
amble.
In the example screenshot, you can distinguish the four symbol groups. The first two
symbol groups use subcarriers near the edge of the bandwidth. The last two symbol
groups use subcarriers near the center of the bandwidth. At the edge of the bandwidth,
the power is slightly lower than in the center.
The table below the diagram shows ON power and OFF power values. According to
3GPP, the ON power is the mean UE output power over the preamble, i.e. over the
NPRACH measurement period, see Table 5-1. In addition to this value, the result table
lists also the peak power within the measurement period. The ON power measurement
period is marked by a green horizontal bar in the diagram.
The OFF power is the mean power during 1 ms before and after the ON power mea-
surement period. A transient period of 20 µs next to the ON power measurement
period is excluded. The transient period is indicated by gray vertical bars in the dia-
gram.
User Manual 1178.5689.02 ─ 12 424

GUI Reference
Table 5-1: Measurement period for ON power
Preamble format Measurement period
0 5.6 ms
1 6.4 ms
For additional information, refer to Chapter 5.3.2.9, "Common View Elements",

on page 427.
For query of the power dynamics results via remote control, see:
● FETCh:NIOT:MEAS:PRACh:TRACe:PDYNamics:CURRent? etc.
● FETCh:NIOT:MEAS:PRACh:PDYNamics:CURRent? etc.
5.3.2.6 View TX Measurement
This single-preamble view contains tables of statistical results for the NPRACH mea-
surement.
Figure 5-10: TX measurement
The table provides an overview of statistical values obtained from the measured pre-
amble. Other detailed views provide a subset of these values.
● EVM, magnitude error ("MErr"), phase error ("PhErr"):
The R&S CMW calculates RMS and peak values for low and high EVM window
position (l/h); see Chapter 5.2.5, "Calculation of Modulation Results", on page 416.
User Manual 1178.5689.02 ─ 12 425

GUI Reference
● Frequency error: offset between the measured carrier frequency and the nominal
RF frequency of the measured radio channel
● Timing error: Difference between the actual timing and the expected timing. The
timing error measurement requires an "external" trigger signal to derive the expec-
ted timing.
Suitable trigger signals are, for example, the NPRACH trigger signal provided by
the signaling application or an external trigger fed in via the rear panel.
The unit Ts stands for the basic time unit, see Chapter 5.2.6, "NB-IoT Preamble
Structure", on page 417.
● TX power: received power, RMS averaged over all samples within the preamble
duration
● Peak power: peak power of all samples within the preamble duration
For additional information, refer to Chapter 5.3.2.9, "Common View Elements",
on page 427.
For query of the table contents via remote control, see Chapter 5.5.3.17, ""TX Mea-
surement" Results (Single Values)", on page 465.
5.3.2.7 Selecting and Modifying Views
Press the "Display" softkey to show hotkeys for view configuration. They change the
appearance and contents of the active view. The following hotkeys are available at the
bottom of the GUI:
Hotkey Description
"Select View ..." Switch to a certain detailed view or overview.

Alternatively, select a diagram in the overview and press [ENTER] or the
rotary knob.
"Select Trace ..." Select the trace types to be displayed in the view.
"X Scale... / Y Scale..." Modify the ranges of the X-axis and the Y-axis.
Additional options are available in the "Measurement Control" section of the configura-
tion dialog.
5.3.2.8 Using Markers
Press the "Marker" softkey to show hotkeys for marker configuration. They activate
markers and modify their position. The following hotkeys are available at the bottom of
the GUI:
User Manual 1178.5689.02 ─ 12 426

GUI Reference
Hotkey Description
"Ref. Marker ..." Enable or disable the reference marker and select the marker position. If sev-
eral traces can be displayed, a trace can also be selected.
"Marker 1 /2 ..." Enable or disable marker 1 or 2 and define the marker position (absolute or rel-
ative to the reference marker).
Depending on the trace mode, a trace can also be selected.
"Select Trace Mode" Define whether markers 1 and 2 are set to the same trace as the reference
marker (collective) or to selectable individual traces.
5.3.2.9 Common View Elements
This section describes elements that are displayed in most views.
Current settings
The most important settings of the NB-IoT NPRACH measurement are displayed at the
top of the measurement dialog.
Statistics in the result tables

Most result diagrams and result tables provide statistical results.
The statistical values are calculated as follows:
● "Current": Result obtained in the last measurement interval. For some modulation
results, an RMS value and a peak value are available. They are calculated as the
average and peak of all samples in the measured slot.
● "Average": Weighted average of all "Current" values since the start of the mea-
surement.
● "Extreme", "Max", "Min": Largest or smallest "Current" value since the start of
the measurement. For EVM, magnitude error and phase error, the extreme value of
all modulation symbols in the slot. No average over data symbols is involved.
● "StdDev": Standard deviation of all "Current" values since the start of the mea-
surement.
For description of individual table rows, see Chapter 5.3.2.5, "View Power Dynamics",
on page 424.
Statistic Count
Progress bar for the measurement. During the first single shot after the start of the
measurement, the bar shows the number of measured preambles relative to the con-
figured "Statistic Count". A filled progress bar indicates that the first shot is complete
and the statistical depth has been reached.
Out of Tolerance
Percentage of measurement intervals (preambles) that were failed because they
exceeded the limits in the diagram.
User Manual 1178.5689.02 ─ 12 427

GUI Reference
5.3.3 Signal Routing and Analyzer Settings
Access: "NPRACH" tab > "Config" hotkey > top of the configuration dialog.
The following parameters configure the RF input path. All parameters are common
measurement settings, i.e. they have the same value as in the multi-evaluation mea-
surement.
Figure 5-11: Signal routing and analyzer settings
For a description of the settings, see Chapter 4.3.3, "Signal Routing and Analyzer Set-
tings", on page 306.
5.3.4 Measurement Control Settings
The "Measurement Control" parameters configure the scope of the NB-IoT NPRACH
measurement and inform the measurement about preamble-related signal properties
normally determined by higher layers.
● General Measurement Control Settings................................................................428
● Modulation Settings...............................................................................................430
● Power Settings...................................................................................................... 431
5.3.4.1 General Measurement Control Settings
Access: "Config" hotkey > "Measurement Control" section.

Figure 5-12: Measurement Control settings - general part
User Manual 1178.5689.02 ─ 12 428

GUI Reference
Repetition.................................................................................................................... 429
Stop Condition.............................................................................................................429
Measure on Exception................................................................................................ 429
Channel Bandwidth..................................................................................................... 429
NPRACH Preamble Format........................................................................................ 430
Number of Preambles................................................................................................. 430
Period of Preambles....................................................................................................430
Repetition
Defines how often the measurement is repeated if it is not stopped explicitly or by a
failed limit check.
● Continuous: The measurement is continued until it is explicitly terminated. The
● Single-Shot: The measurement is stopped after one measurement cycle.
Single-shot is preferable if only a single measurement result is required under fixed
conditions, which is typical for remote-controlled measurements. The continuous mode
is suitable to monitor the evolution of the measurement results and to observe how
they depend on the measurement configuration, which is typically done in manual con-
trol.
Remote command:
CONFigure:NIOT:MEAS:PRACh:REPetition
Stop Condition
Specifies the conditions for an early termination of the measurement:
● "None": The measurement is performed according to its "Repetition" mode and
"Statistic Count", irrespective of the limit check results.
● "On Limit Failure": The measurement is stopped when one of the limits is excee-
ded, irrespective of the repetition mode set. If no limit failure occurs, it is performed
according to its "Repetition" mode and "Statistic Count". Use this setting for mea-
surements that are intended for checking limits, e.g. production tests.
Remote command:
CONFigure:NIOT:MEAS:PRACh:SCONdition
Measure on Exception
Specifies whether results that the measurement identifies as faulty or inaccurate are
rejected. A faulty result occurs, for example, when an overload is detected. In remote
control, the cause of the error is indicated by the "reliability indicator".
● Off: Faulty results are rejected. The measurement is continued. The statistical
counters are not reset. Use this mode to ensure that a single faulty result does not
affect the entire measurement.
● On: Results are never rejected. Use this mode for development purposes, if you
want to analyze the reason for occasional wrong transmissions.
Remote command:
CONFigure:NIOT:MEAS:PRACh:MOEXception
Channel Bandwidth
Displays the channel bandwidth. The bandwidth is fixed for NB-IoT signals.
User Manual 1178.5689.02 ─ 12 429

GUI Reference
NPRACH Preamble Format

Enter the NPRACH preamble format used by the UE.
For background information, see Chapter 5.2.6, "NB-IoT Preamble Structure",
on page 417.
Remote command:
CONFigure:NIOT:MEAS:PRACh:PFORmat
Number of Preambles
Specifies the number of preambles to be captured per measurement interval for multi-
preamble result views, for example "EVM vs Preamble" and "Power vs Preamble".
Single-preamble views evaluate only one preamble per measurement interval. To ach-
ieve maximum measurement speed for these views, set "Number of Preambles" to 1.
See also Chapter 5.2.3, "Defining the Scope of the Measurement", on page 415.
Remote command:
CONFigure:NIOT:MEAS:PRACh:NOPReambles
Period of Preambles
Specifies the period expected between subsequent preambles.
See also Chapter 5.2.3, "Defining the Scope of the Measurement", on page 415.
Remote command:
CONFigure:NIOT:MEAS:PRACh:POPReambles
5.3.4.2 Modulation Settings
The following parameters configure the modulation settings of the NB-IoT NPRACH
measurement.
Figure 5-13: Modulation settings
Statistic Count............................................................................................................. 430

EVM Window Length...................................................................................................431
EVM Window Position.................................................................................................431
Statistic Count
Defines the number of measurement intervals per measurement cycle. A measurement
cycle is the duration of a single-shot measurement.
For single-preamble modulation measurements, the measurement interval is comple-
ted when the R&S CMW has measured one full preamble (four symbol groups). The
preamble length depends on the preamble format, see Chapter 5.2.6, "NB-IoT Pream-
ble Structure", on page 417.
User Manual 1178.5689.02 ─ 12 430

GUI Reference
For multi-preamble measurements, the measurement interval is completed when the

configured number of preambles has been measured, see "Number of Preambles"
on page 430.
The measurement provides independent statistic counts for modulation results and
power dynamics results. In single-shot mode and with a shorter modulation statistic
count, the modulation evaluation is stopped while the R&S CMW still continues provid-
ing new power dynamics results.
Remote command:
CONFigure:NIOT:MEAS:PRACh:SCOunt:MODulation
EVM Window Length

Length of the EVM window in samples. The standard (3GPP TS 36.101, annex F)
specifies the window length as a function of the preamble format.
The R&S CMW uses the "Current" value. This value is linked to the value in the table,
corresponding to the current preamble format.
The window length defines the two sets of "l / h" modulation quantities in the result
tables; see Chapter 5.2.5, "Calculation of Modulation Results", on page 416.
The minimum value of one FFT symbol means that EVMh equals EVMl.
Remote command:
CONFigure:NIOT:MEAS:PRACh:MODulation:EWLength
EVM Window Position

Position of the EVM window used for calculation of the trace results. While result tables
show both the results for low and high EVM window position, the diagram results are
only determined for the selected window position.
Remote command:
CONFigure:NIOT:MEAS:PRACh:MODulation:EWPosition
5.3.4.3 Power Settings
The following parameters configure the power settings of the NB-IoT NPRACH mea-
surement.
Figure 5-14: Power settings
Statistic Count
Defines the number of measurement intervals per measurement cycle. A measurement
cycle is the duration of a single-shot measurement.
For power dynamics measurements, the measurement interval is completed when the
R&S CMW has measured one preamble plus the preceding and the following power
OFF time.
User Manual 1178.5689.02 ─ 12 431

GUI Reference
The measurement provides independent statistic counts for modulation results and
power dynamics results. In single-shot mode and with a shorter modulation statistic
count, the modulation evaluation is stopped while the R&S CMW still continues provid-
ing new power dynamics results.
Remote command:
CONFigure:NIOT:MEAS:PRACh:SCOunt:PDYNamics
5.3.5 Trigger Settings
Access: "NPRACH" tab > "Config" hotkey > "Trigger" section.

The "Trigger" parameters configure the trigger system for the NB-IoT NPRACH mea-
surement.
Figure 5-15: Trigger settings
Trigger Source.............................................................................................................432
Trigger Slope...............................................................................................................433
Trigger Threshold........................................................................................................ 433
Trigger Timeout........................................................................................................... 433
Min Trigger Gap.......................................................................................................... 433
Trigger Source
Selects the source of the trigger event.
Only the measurement-specific trigger sources are listed here. Additional trigger sour-
ces are provided by the base software and by other applications like the GPRF genera-
tor. For a description of these trigger sources, refer to the documentation of the corre-
sponding software part.
"IF Power" The measurement is triggered by the power ramp of the received pre-
ambles, converted into an IF signal. The trigger event coincides with
the rising or falling edge of the detected burst (i.e. the start or end of
the preamble for an NPRACH UL signal).
The minimum trigger gap must be large enough to ensure that the
measurement is not retriggered within a preamble. It must be small
enough to ensure that the trigger system is rearmed before the next
preamble starts. The default value is often appropriate, see Min Trig-
ger Gap.
Remote command:
TRIGger:NIOT:MEAS:PRACh:SOURce
TRIGger:NIOT:MEAS:PRACh:CATalog:SOURce?
User Manual 1178.5689.02 ─ 12 432

GUI Reference
Trigger Slope
the trigger pulse. This setting has no influence on the evaluation of trigger pulses provi-
ded by other firmware applications.
Remote command:
TRIGger:NIOT:MEAS:PRACh:SLOPe
Trigger Threshold
Defines the input signal power where a trigger event is generated for power trigger
sources.
The threshold is a dB value, relative to the reference level minus the external attenua-
tion. If the reference level equals the maximum output power of the DUT and the exter-
nal attenuation settings are correct, the trigger threshold is relative to the maximum
input power.
A low threshold ensures that the input signal is always detected. A higher threshold
can prevent unintended trigger events.
Remote command:
TRIGger:NIOT:MEAS:PRACh:THReshold
Trigger Timeout
Sets a time after which an initiated measurement must have received a trigger event. If
no trigger event is received, a trigger timeout is indicated in manual operation mode. In
remote control mode, the measurement is automatically stopped. The parameter can
be disabled so that no timeout occurs.
Remote command:
TRIGger:NIOT:MEAS:PRACh:TOUT
Min Trigger Gap

Defines a minimum duration of the power-down periods (gaps) between two triggered
power pulses. This setting is valid for "(IF) Power" trigger sources.
The trigger system is controlled by a timer which is reset to zero in the following instan-
ces:
● At the IF power-down ramp of each triggered or untriggered pulse, even if the pre-
vious counter has not yet elapsed. A power-down ramp is detected when the signal
power falls below the trigger threshold.
● At the beginning of each measurement. The minimum gap defines the minimum
time between the start of the measurement and the first trigger event.
The trigger system is rearmed when the timer has reached the specified minimum gap.
User Manual 1178.5689.02 ─ 12 433

GUI Reference
Start of No trigger Trigger No trigger Trigger

measure- event event event event
ment
Trigger Trigger armed
Minimum Minimum armed Min. Min. Min.
Trigger Trigger Trigger Trigger Trigger
Gap Gap Gap Gap Gap
This parameter can be used to prevent unwanted trigger events due to fast power var-
iations within a preamble.
The minimum trigger gap must be large enough to ensure that the measurement is not
retriggered within a preamble. It must be small enough to ensure that the trigger sys-
tem is rearmed before the next preamble starts. The default value is often appropriate.
Remote command:
TRIGger:NIOT:MEAS:PRACh:MGAP
5.3.6 Limit Settings
The following sections give an overview of the NPRACH measurement limit settings
and the related conformance test requirements.
Conformance requirements for NB-IoT transmitter tests are specified in 3GPP TS
36.521, section 6, "Transmitter Characteristics".
● Transmit Modulation Limits................................................................................... 434
● Power Dynamics Limits.........................................................................................435
5.3.6.1 Transmit Modulation Limits
Access: "NPRACH" tab > "Config" hotkey > "Limits" > "Modulation" section.
A poor modulation accuracy of the UE transmitter increases the transmission errors in
the uplink channel of the network and decreases the system capacity. The error vector
magnitude (EVM) is the critical quantity to assess the modulation accuracy of a UE.
According to 3GPP, the EVM measured at UE output powers ≥ −40 dBm must not
exceed 17.5 %.
EVM (RMS) 6.5.2.1F.1 Error Vector Magnitude (EVM) for category NB1 ≤ 17.5 %
Modulation limit settings

The EVM limits can be set in the configuration dialog, along with limits for the other
measured quantities.
User Manual 1178.5689.02 ─ 12 434

GUI Reference
Figure 5-16: Modulation limit settings
Remote command:
CONFigure:NIOT:MEAS:PRACh:LIMit:EVMagnitude
CONFigure:NIOT:MEAS:PRACh:LIMit:MERRor
CONFigure:NIOT:MEAS:PRACh:LIMit:PERRor
CONFigure:NIOT:MEAS:PRACh:LIMit:FERRor
5.3.6.2 Power Dynamics Limits
Access: "NPRACH" tab > "Config" hotkey > "Limits" > "Power" > "Dynamics" section.
Transmission at excessive uplink power increases interference to other channels. A too
low uplink power increases transmission errors. For NPRACH transmission, 3GPP
defines a time mask. The mask contains limits for the UL power during preamble trans-
mission (transmit ON power), without preamble transmission (transmit OFF power) and
the power ramping in-between.
The ON power is specified as the mean UE output power over the preamble (more
exactly, over the NPRACH measurement period, see Table 5-1). For the OFF power,
the mean power has to be measured for 1 ms before and after the preamble. A transi-
ent period of 20 µs next to the NPRACH measurement period is excluded.
The following figure provides a summary of the time periods relevant for ON and OFF
power limits.
1 ms (OFF) Preamble 1 ms (OFF)
20 µs 20 µs
OFF power ON power OFF power
(1 ms – µs) (NPRACH meas. period) (1 ms – µs)
Figure 5-17: Measurement periods for ON/OFF power
The OFF power must not exceed -48.5 dBm. The ON power must be in the range
-18.5 dBm to -3.5 dBm.
User Manual 1178.5689.02 ─ 12 435

Programming
ON power 6.3.4F.2 NPRACH Time Mask for Category NB1 ≥ -18.5 dBm, ≤ -3.5 dBm
OFF power 6.3.4F.2 NPRACH Time Mask for Category NB1 ≤ -48.5 dBm
Power dynamics limit settings

The limits for ON and OFF power can be set in the configuration dialog.
Figure 5-18: Power dynamics limit settings
Remote command:
CONFigure:NIOT:MEAS:PRACh:LIMit:PDYNamics
Access: "Config" hotkey > "Generator Shortcut" setting.

This section configures a shortcut softkey that provides a fast way to access the GPRF
generator from the measurement.
The setting is a common measurement setting. It has the same value in all NB-IoT
measurements (NPRACH measurement and multi-evaluation measurement).
Generator Shortcut
Selects a GPRF generator instance. Softkeys for the selected instance are added to
the softkey panel.
5.3.8 Additional Softkeys and Hotkeys
See Chapter 4.3.8, "Additional Softkeys and Hotkeys", on page 326.
5.4 Programming
The following sections provide programming examples for the NB-IoT NPRACH mea-
surement.
User Manual 1178.5689.02 ─ 12 436

Programming
● Key Features.........................................................................................................437
● Specifying General and Common Measurement Settings.................................... 437
● Specifying Required NPRACH Settings................................................................438
● Specifying Measurement-Specific Settings...........................................................438
● Configuring the Trigger System............................................................................ 438
● Specifying Limits................................................................................................... 438
● Performing Single-Shot Measurements................................................................ 439
● Single-Shot and Continuous Measurements.........................................................440
5.4.1 Key Features
The NB-IoT NPRACH measurement is programmed as follows:

tax: ...NIOT:MEAS:PRACh...
● Use general commands of the type ...:NIOT:MEAS... (no :PRACh mnemonic)
to define the signal routing and perform RF and analyzer settings.
● After a *RST, the measurement is switched off. Use
READ:NIOT:MEAS:PRACh...? to initiate a single-shot measurement and retrieve
the results. You can also start the measurement using INIT:NIOT:MEAS:PRACh
and retrieve the results using FETCh:NIOT:MEAS:PRACh...?.
● For synchronization and proper decoding, some UE signal settings must be in
accordance with the measured signal; see Chapter 5.4.3, "Specifying Required
NPRACH Settings", on page 438.
5.4.2 Specifying General and Common Measurement Settings

// *****************************************************************************
// *****************************************************************************
*RST; *OPC?
*CLS; *OPC?
// *****************************************************************************
// Define signal routing and perform RF and analyzer settings:
// Center frequency 1850 MHz, frequency offset 1 kHz, peak power -2 dBm,
// no user margin and 1 dB mixer level offset.
// *****************************************************************************
CONFigure:NIOT:MEAS:BAND OB2
CONFigure:NIOT:MEAS:RFSettings:FREQuency 1850E+6
CONFigure:NIOT:MEAS:RFSettings:FOFFset 1000
CONFigure:NIOT:MEAS:RFSettings:ENPower -2
CONFigure:NIOT:MEAS:RFSettings:UMARgin 0
CONFigure:NIOT:MEAS:RFSettings:MLOFfset 1
User Manual 1178.5689.02 ─ 12 437

Programming
5.4.3 Specifying Required NPRACH Settings

// *****************************************************************************
// Specify required UE signal settings: NPRACH preamble format
// *****************************************************************************
CONFigure:NIOT:MEAS:PRACh:PFORmat 0
5.4.4 Specifying Measurement-Specific Settings

// *****************************************************************************
// Define stop condition (stop on limit failure), statistic counts (20 cycles),
// error handling, number of preambles, periodicity of preambles.
// *****************************************************************************
CONFigure:NIOT:MEAS:PRACh:SCONdition SLFail
CONFigure:NIOT:MEAS:PRACh:SCOunt:MODulation 20
CONFigure:NIOT:MEAS:PRACh:SCOunt:PDYNamics 20
CONFigure:NIOT:MEAS:PRACh:MOEXception ON
CONFigure:NIOT:MEAS:PRACh:TOUT 3600
CONFigure:NIOT:MEAS:PRACh:NOPReambles 10
CONFigure:NIOT:MEAS:PRACh:POPReambles MS160
// *****************************************************************************
// Specify EVM window length for all preamble formats.
// Specify the EVM window position for traces.
// *****************************************************************************
CONFigure:NIOT:MEAS:PRACh:MODulation:EWLength 120, 450
CONFigure:NIOT:MEAS:PRACh:MODulation:EWPosition HIGH
5.4.5 Configuring the Trigger System

// *****************************************************************************
// Set trigger source, slope, threshold, timeout and minimum trigger gap.
// *****************************************************************************
TRIGger:NIOT:MEAS:PRACh:SOURce 'IF Power'
TRIGger:NIOT:MEAS:PRACh:SLOPe FEDGe
TRIGger:NIOT:MEAS:PRACh:THReshold -30
TRIGger:NIOT:MEAS:PRACh:TOUT 1
TRIGger:NIOT:MEAS:PRACh:MGAP 0.00006
5.4.6 Specifying Limits

// *****************************************************************************
// Define modulation limits.
// *****************************************************************************
CONFigure:NIOT:MEAS:PRACh:LIMit:EVMagnitude 20, 40
CONFigure:NIOT:MEAS:PRACh:LIMit:MERRor 20, OFF
CONFigure:NIOT:MEAS:PRACh:LIMit:PERRor 20, OFF
User Manual 1178.5689.02 ─ 12 438

Programming
CONFigure:NIOT:MEAS:PRACh:LIMit:FERRor 150
// *****************************************************************************
// Define power dynamics limits.
// *****************************************************************************
CONFigure:NIOT:MEAS:PRACh:LIMit:PDYNamics ON, -3.7, -18.5, -48.8
5.4.7 Performing Single-Shot Measurements

// *****************************************************************************
// Enable all measurements.
// *****************************************************************************
CONFigure:NIOT:MEAS:PRACh:RESult:ALL ON,ON,ON,ON,ON,ON,ON,ON
// *****************************************************************************
// Start single-shot measurement, return average EVM trace.
// Query the measurement state (should be "RDY").
// *****************************************************************************
READ:NIOT:MEAS:PRACh:TRACe:EVM:AVERage?
FETCh:NIOT:MEAS:PRACh:STATe?
// *****************************************************************************
// Retrieve SC numbers for single\-preamble measurements.
// Retrieve SC numbers for preamble 3 and 4 of multi\-preamble measurements.
// *****************************************************************************
FETCh:NIOT:MEAS:PRACh:MODulation:SCSGroup?
FETCh:NIOT:MEAS:PRACh:MODulation:SCSGroup:PREamble3?
FETCh:NIOT:MEAS:PRACh:MODulation:SCSGroup:PREamble4?
// *****************************************************************************
// Read other traces obtained in the last
// measurement without re-starting the measurement.
// *****************************************************************************
FETCh:NIOT:MEAS:PRACh:TRACe:MERRor:AVERage?
FETCh:NIOT:MEAS:PRACh:TRACe:MERRor:MAXimum?
FETCh:NIOT:MEAS:PRACh:TRACe:PERRor:AVERage?
FETCh:NIOT:MEAS:PRACh:TRACe:PERRor:MAXimum?
FETCh:NIOT:MEAS:PRACh:TRACe:EVPReamble?
FETCh:NIOT:MEAS:PRACh:TRACe:PVPReamble?
FETCh:NIOT:MEAS:PRACh:TRACe:IQ?
FETCh:NIOT:MEAS:PRACh:TRACe:PDYNamics:AVERage?
FETCh:NIOT:MEAS:PRACh:TRACe:PDYNamics:MAXimum?
// *****************************************************************************
// Read single value results obtained in the last measurement
// without re-starting the measurement.
// *****************************************************************************
FETCh:NIOT:MEAS:PRACh:MODulation:AVERage?
FETCh:NIOT:MEAS:PRACh:MODulation:EXTReme?
User Manual 1178.5689.02 ─ 12 439

Command Reference
FETCh:NIOT:MEAS:PRACh:MODulation:PREamble4?
FETCh:NIOT:MEAS:PRACh:PDYNamics:AVERage?
FETCh:NIOT:MEAS:PRACh:PDYNamics:MINimum?
FETCh:NIOT:MEAS:PRACh:PDYNamics:MAXimum?
// *****************************************************************************
// Read limit check results obtained in the last measurement
// without re-starting the measurement.
// *****************************************************************************
CALCulate:NIOT:MEAS:PRACh:MODulation:AVERage?
CALCulate:NIOT:MEAS:PRACh:MODulation:EXTReme?
CALCulate:NIOT:MEAS:PRACh:PDYNamics:AVERage?
CALCulate:NIOT:MEAS:PRACh:PDYNamics:MINimum?
CALCulate:NIOT:MEAS:PRACh:PDYNamics:MAXimum?
5.4.8 Single-Shot and Continuous Measurements

// *****************************************************************************
// Start single-shot measurement, return magnitude error trace,
// return phase error trace (without repeating the measurement).
// Query the measurement state (should be "RDY").
// *****************************************************************************
INIT:NIOT:MEAS:PRACh
FETCh:NIOT:MEAS:PRACh:TRACe:MERRor:AVERage?
FETCh:NIOT:MEAS:PRACh:TRACe:PERRor:AVERage?
FETCh:NIOT:MEAS:PRACh:STATe?
// *****************************************************************************
// Start continuous measurement and wait for 5 ms.
// Return average EVM trace.
// Query measurement state and substates (should be "RUN,ADJ,ACT").
// *****************************************************************************
CONFigure:NIOT:MEAS:PRACh:REPetition CONTinuous
INIT:NIOT:MEAS:PRACh
Pause 5000
FETCh:NIOT:MEAS:PRACh:TRACe:EVM:AVERage?
FETCh:NIOT:MEAS:PRACh:STATe:ALL?

The following sections provide detailed reference information on the remote control
commands of the NB-IoT NPRACH measurement.
● General Measurement Settings............................................................................ 446
● NPRACH Measurement Commands.....................................................................446
● Combined Signal Path Commands....................................................................... 471
User Manual 1178.5689.02 ─ 12 440

Command Reference
5.5.1.1 MEAS
MEAS is used as abbreviation of "MEASurement<instance>". For better readability,

command reference.
measurement application. It can be omitted if the instrument supports only one
instance, or to address the first instance.
5.5.1.2 FETCh, READ and CALCulate Commands
All commands are used to retrieve measurement results:

● FETCh... returns the results of the measurement cycle after the cycle is com-
plete. Before sending a FETCh..., start the measurement via an INITiate....
● READ... starts a new single-shot measurement and returns the results.
● CALCulate... returns one limit check result per FETCh result:
– OK: The FETCh result is located within the limits or no limit has been defined/
enabled for this result.
– ULEU ("User limit exceeded upper"): An upper limit is violated. The FETCh
result is located above the limit.
– ULEL ("User limit exceeded lower"): A lower limit is violated. The FETCh result
is located below the limit.
5.5.1.3 Current and Statistical Results
The measurement is repeated according to the selected statistic count and repetition
mode. Consecutive measurement values are stored and used to calculate statistical
results.
Commands for result query often contain a mnemonic that indicates which results are
returned: CURRent, AVERage, EXTReme, MINimum, MAXimum or SDEViation.
5.5.1.4 Keywords
● Command usage
User Manual 1178.5689.02 ─ 12 441

Command Reference

● Parameter usage
● Parameter type
● 0 ("No Error"):
ble memory.
User Manual 1178.5689.02 ─ 12 442

Command Reference
detected.
● 9 ("Uncal"):
not active.
frequency.
User Manual 1178.5689.02 ─ 12 443

Command Reference

mode.
reliable.
maximum.
● 51 ("No Reply"):
User Manual 1178.5689.02 ─ 12 444

Command Reference
nal.
lation type.
schwarz.com.
User Manual 1178.5689.02 ─ 12 445

Command Reference

parameter settings.
5.5.2 General Measurement Settings
The commands valid for all NB-IoT measurements are described here: Chapter 4.5.2,
"General Measurement Settings", on page 342.
5.5.3 NPRACH Measurement Commands
The commands for the NB-IoT NPRACH measurement are divided into the groups lis-
ted below.
● Enabling Results and Views..................................................................................448
● Measurement Parameters - General Part............................................................. 450
● Modulation Measurement Settings........................................................................453
● Power Measurement Settings............................................................................... 454
● Limits (Modulation)................................................................................................457
● Limits (Power)....................................................................................................... 459
● Detected Subcarriers............................................................................................ 459
● EVM vs. Symbol Results (Traces)........................................................................ 461
● Magnitude Error Results (Traces)......................................................................... 461
● Phase Error Results (Traces)................................................................................462
● EVM vs. Preamble Results (Traces)..................................................................... 462
● Power vs. Preamble Results (Traces)...................................................................463
● I/Q Constellation Results (Traces)........................................................................ 463
● Power Dynamics Results (Traces)........................................................................464
● "TX Measurement" Results (Single Values)..........................................................465
● EVM / Power vs. Preamble Results (Single Values)............................................. 468
● Power Dynamics Results (Single Values)............................................................. 470
5.5.3.1 Measurement Control and States
ment state.
User Manual 1178.5689.02 ─ 12 446

Command Reference
INITiate:NIOT:MEAS:PRACh...................................................................................... 447
STOP:NIOT:MEAS:PRACh......................................................................................... 447
ABORt:NIOT:MEAS:PRACh........................................................................................447
FETCh:NIOT:MEAS:PRACh:STATe?........................................................................... 447
FETCh:NIOT:MEAS:PRACh:STATe:ALL?.....................................................................448
INITiate:NIOT:MEAS:PRACh
STOP:NIOT:MEAS:PRACh
ABORt:NIOT:MEAS:PRACh
"RUN" state.
surement.
released.
Example: See Single-Shot and Continuous Measurements
Usage: Event
Manual operation: See "NPRACH (Softkey)" on page 419
FETCh:NIOT:MEAS:PRACh:STATe?
Return values:
<MeasStatus> OFF | RUN | RDY
*RST: OFF
Usage: Query only
User Manual 1178.5689.02 ─ 12 447

Command Reference
FETCh:NIOT:MEAS:PRACh:STATe:ALL?
Return values:
*RST: OFF
("queued")
Usage: Query only
5.5.3.2 Enabling Results and Views
The following commands select the evaluated results and the displayed views.
CONFigure:NIOT:MEAS:PRACh:RESult[:ALL]..............................................................449
CONFigure:NIOT:MEAS:PRACh:RESult:EVMagnitude.................................................. 450
CONFigure:NIOT:MEAS:PRACh:RESult:MERRor......................................................... 450
CONFigure:NIOT:MEAS:PRACh:RESult:PERRor..........................................................450
CONFigure:NIOT:MEAS:PRACh:RESult:IQ.................................................................. 450
CONFigure:NIOT:MEAS:PRACh:RESult:PDYNamics.................................................... 450
CONFigure:NIOT:MEAS:PRACh:RESult:TXM...............................................................450
CONFigure:NIOT:MEAS:PRACh:RESult:EVPReamble.................................................. 450
CONFigure:NIOT:MEAS:PRACh:RESult:PVPReamble.................................................. 450
User Manual 1178.5689.02 ─ 12 448

Command Reference
CONFigure:NIOT:MEAS:PRACh:RESult[:ALL] <EVM>, <MagnitudeError>,

<PhaseError>, <IQ>, <PowerDynamics>, <TXMeasurement>[,
<EVMvsPreamble>, <PowervsPreamble>]
Enables or disables the evaluation of results and shows or hides the views in the
NPRACH measurement. This command combines all other
CONFigure:NIOT:MEAS:PRACh:RESult... commands.
Parameters:
<EVM> OFF | ON
Error vector magnitude
*RST: ON
<MagnitudeError> OFF | ON
Magnitude error
*RST: OFF
<PhaseError> OFF | ON
Phase error
*RST: OFF
<IQ> OFF | ON
I/Q constellation diagram
*RST: OFF
<PowerDynamics> OFF | ON
Power dynamics
*RST: ON
<TXMeasurement> OFF | ON
Statistical overview
*RST: ON
<EVMvsPreamble> OFF | ON
Error vector magnitude vs preamble
*RST: OFF
<PowervsPreamble> OFF | ON
Power vs preamble
*RST: OFF
User Manual 1178.5689.02 ─ 12 449

Command Reference
CONFigure:NIOT:MEAS:PRACh:RESult:EVMagnitude <Enable>
CONFigure:NIOT:MEAS:PRACh:RESult:MERRor <Enable>
CONFigure:NIOT:MEAS:PRACh:RESult:PERRor <Enable>
CONFigure:NIOT:MEAS:PRACh:RESult:IQ <Enable>
CONFigure:NIOT:MEAS:PRACh:RESult:PDYNamics <Enable>
CONFigure:NIOT:MEAS:PRACh:RESult:TXM <Enable>
CONFigure:NIOT:MEAS:PRACh:RESult:EVPReamble <Enable>
CONFigure:NIOT:MEAS:PRACh:RESult:PVPReamble <Enable>
Enables or disables the evaluation of results and shows or hides the views in the
NPRACH measurement.
The mnemonic after "RESult" denotes the view type: error vector magnitude, magni-
tude error, phase error, I/Q constellation diagram, power dynamics, TX measurement
statistical overview, error vector magnitude vs preamble, power vs preamble
For reset values, see CONFigure:NIOT:MEAS:PRACh:RESult[:ALL].
Parameters:
<Enable> OFF | ON
*RST: Depends on measurement
5.5.3.3 Measurement Parameters - General Part
The following commands define general measurement control parameters for the
NPRACH measurement.
CONFigure:NIOT:MEAS:PRACh:TOUT........................................................................450
CONFigure:NIOT:MEAS:PRACh:REPetition................................................................. 451
CONFigure:NIOT:MEAS:PRACh:SCONdition............................................................... 451
CONFigure:NIOT:MEAS:PRACh:MOEXception............................................................ 452
CONFigure:NIOT:MEAS:PRACh:PFORmat.................................................................. 452
CONFigure:NIOT:MEAS:PRACh:NOPReambles...........................................................452
CONFigure:NIOT:MEAS:PRACh:POPReambles........................................................... 452
CONFigure:NIOT:MEAS:PRACh:TOUT <Timeout>
User Manual 1178.5689.02 ─ 12 450

Command Reference
reached.
Parameters:
<Timeout> numeric
Default unit: s
CONFigure:NIOT:MEAS:PRACh:REPetition <Repetition>
Specifies the repetition mode of the measurement. The repetition mode specifies
whether the measurement is stopped after a single shot or repeated continuously. Use
CONFigure:..:MEAS:...:SCOunt to determine the number of measurement
intervals per single shot.
Parameters:
*RST: SING
CONFigure:NIOT:MEAS:PRACh:SCONdition <StopCondition>
Qualifies whether the measurement is stopped after a failed limit check or continued.
SLFail means that the measurement is stopped and reaches the RDY state when one
of the results exceeds the limits.
Parameters:
<StopCondition> NONE | SLFail
NONE: Continue measurement irrespective of the limit check
SLFail: Stop measurement on limit failure
*RST: NONE
User Manual 1178.5689.02 ─ 12 451

Command Reference
CONFigure:NIOT:MEAS:PRACh:MOEXception <MeasOnException>
Specifies whether measurement results that the R&S CMW identifies as faulty or inac-
curate are rejected.
Parameters:
<MeasOnException> OFF | ON
OFF: Faulty results are rejected
ON: Results are never rejected
*RST: OFF
Manual operation: See "Measure on Exception" on page 429
CONFigure:NIOT:MEAS:PRACh:PFORmat <PreambleFormat>
Specifies the NPRACH preamble format used by the UE.
Parameters:
<PreambleFormat> numeric
Range: 0 to 1
*RST: 0
Example: See Specifying Required NPRACH Settings
Manual operation: See "NPRACH Preamble Format" on page 430
CONFigure:NIOT:MEAS:PRACh:NOPReambles <NumberPreamble>
Specifies the number of preambles to be captured per measurement interval.
Parameters:
<NumberPreamble> numeric
Range: 1 to 32
*RST: 1
Manual operation: See "Number of Preambles" on page 430
CONFigure:NIOT:MEAS:PRACh:POPReambles <PeriodPreamble>
Specifies the periodicity of preambles to be captured for multi-preamble result views.
User Manual 1178.5689.02 ─ 12 452

Command Reference
Parameters:
<PeriodPreamble> MS40 | MS80 | MS160 | MS240 | MS320
Periodicity in ms
*RST: MS80
Manual operation: See "Period of Preambles" on page 430
5.5.3.4 Modulation Measurement Settings
The following commands specify settings for the modulation measurements.

CONFigure:NIOT:MEAS:PRACh:SCOunt:MODulation...................................................453
CONFigure:NIOT:MEAS:PRACh:MODulation:EWLength............................................... 453
CONFigure:NIOT:MEAS:PRACh:MODulation:EWPosition..............................................454
CONFigure:NIOT:MEAS:PRACh:SCOunt:MODulation <StatisticCount>
Parameters:
Range: 1 to 1000
*RST: 2
Example: See
CONFigure:NIOT:MEAS:PRACh:MODulation:EWLength
<EVMwindowLength>(2)
Specifies the EVM window length in samples for all preamble formats.
Parameters:
<LengthFormat0> integer
<LengthFormat1> Length for preamble format 0 and 1
Range: Format 0: 1 to 128, format 1: 1 to 512
*RST: Format 0: 110, format 1: 494
Default unit: sample
Manual operation: See "EVM Window Length" on page 431
User Manual 1178.5689.02 ─ 12 453

Command Reference
CONFigure:NIOT:MEAS:PRACh:MODulation:EWPosition <EVMwindowPos>
Specifies the position of the EVM window used for calculation of the trace results.
Parameters:
<EVMwindowPos> LOW | HIGH
*RST: LOW
Manual operation: See "EVM Window Position" on page 431
5.5.3.5 Power Measurement Settings
The following commands specify settings for power dynamics measurements.
CONFigure:NIOT:MEAS:PRACh:SCOunt:PDYNamics <StatisticCount>
Parameters:
Range: 1 to 1000
*RST: 1
5.5.3.6 Trigger Settings
The following commands define the trigger parameters.

TRIGger:NIOT:MEAS:PRACh:CATalog:SOURce?.........................................................454
TRIGger:NIOT:MEAS:PRACh:SOURce........................................................................455
TRIGger:NIOT:MEAS:PRACh:SLOPe.......................................................................... 455
TRIGger:NIOT:MEAS:PRACh:THReshold.................................................................... 455
TRIGger:NIOT:MEAS:PRACh:TOUT............................................................................456
TRIGger:NIOT:MEAS:PRACh:MGAP...........................................................................456
TRIGger:NIOT:MEAS:PRACh:CATalog:SOURce?
Lists all trigger source values that can be set using TRIGger:NIOT:MEAS:
PRACh:SOURce.
User Manual 1178.5689.02 ─ 12 454

Command Reference
Return values:
<Sourcelist> string
Comma-separated list of all supported values. Each value is rep-
resented as a string.
Usage: Query only
TRIGger:NIOT:MEAS:PRACh:SOURce <Source>
Selects the source of the trigger events. Some values are always available. They are
listed below. Depending on the installed options, additional values are available. You
can query a list of all supported values via TRIGger:...:CATalog:SOURce?.
Parameters:
<Source> string
'IF Power': Power trigger (received RF power)
*RST: 'IF Power'
TRIGger:NIOT:MEAS:PRACh:SLOPe <Slope>
the trigger pulse (valid for external and power trigger sources).
Parameters:
<Slope> REDGe | FEDGe
REDGe: Rising edge
FEDGe: Falling edge
*RST: REDG
Manual operation: See "Trigger Slope" on page 433
TRIGger:NIOT:MEAS:PRACh:THReshold <TrigThreshold>
Defines the trigger threshold for power trigger sources.
User Manual 1178.5689.02 ─ 12 455

Command Reference
Parameters:
<TrigThreshold> numeric | ON | OFF
*RST: -20 dB
Default unit: dB (full scale, i.e. relative to reference level minus
external attenuation)
Manual operation: See "Trigger Threshold" on page 433
TRIGger:NIOT:MEAS:PRACh:TOUT <TriggerTimeOut>
Selects the maximum time that the measurement waits for a trigger event before it
stops in remote control mode or indicates a trigger timeout in manual operation mode.
Parameters:
<TriggerTimeOut> numeric | ON | OFF
Range: 0.01 s to 167772.15 s
*RST: 0.1 s
Default unit: s
Additional parameters: OFF | ON (disables | enables the time-
out)
Manual operation: See "Trigger Timeout" on page 433
TRIGger:NIOT:MEAS:PRACh:MGAP <MinTrigGap>
Sets a minimum time during which the IF signal must be below the trigger threshold
before the trigger is armed so that an IF power trigger event can be generated.
Parameters:
<MinTrigGap> numeric
*RST: 50E-6 s
Default unit: s
Manual operation: See "Min Trigger Gap" on page 433
User Manual 1178.5689.02 ─ 12 456

Command Reference
5.5.3.7 Limits (Modulation)
The following commands define limits for results which characterize the modulation
accuracy of the NPRACH signal.
CONFigure:NIOT:MEAS:PRACh:LIMit:EVMagnitude..................................................... 457
CONFigure:NIOT:MEAS:PRACh:LIMit:MERRor............................................................ 457
CONFigure:NIOT:MEAS:PRACh:LIMit:PERRor.............................................................458
CONFigure:NIOT:MEAS:PRACh:LIMit:FERRor.............................................................458
CONFigure:NIOT:MEAS:PRACh:LIMit:EVMagnitude <RMS>, <Peak>

Defines upper limits for the RMS and peak values of the error vector magnitude (EVM).
Parameters:
Range: 0 % to 100 %
*RST: 17.5 %, ON
Default unit: %
Range: 0 % to 100 %
*RST: 35 %, OFF
Default unit: %
Manual operation: See "Modulation limit settings" on page 434
CONFigure:NIOT:MEAS:PRACh:LIMit:MERRor <RMS>, <Peak>

Defines upper limits for the RMS and peak values of the magnitude error.
Parameters:
Range: 0 % to 100 %
*RST: 17.5 %, OFF
Default unit: %
User Manual 1178.5689.02 ─ 12 457

Command Reference

Range: 0 % to 100 %
*RST: 35 %, OFF
Default unit: %
CONFigure:NIOT:MEAS:PRACh:LIMit:PERRor <RMS>, <Peak>

Defines symmetric limits for the RMS and peak values of the phase error. The limit
check fails if the absolute value of the measured phase error exceeds the specified val-
ues.
Parameters:
*RST: 17.5 deg, OFF
Default unit: deg
*RST: 35 deg, OFF
Default unit: deg
CONFigure:NIOT:MEAS:PRACh:LIMit:FERRor <FrequencyError>
Defines an upper limit for the carrier frequency error.
Parameters:
<FrequencyError> numeric | ON | OFF
*RST: 0.1 ppm, ON
User Manual 1178.5689.02 ─ 12 458

Command Reference
5.5.3.8 Limits (Power)
The following command defines limits for results which characterize the power dynam-
ics of the NPRACH signal.
CONFigure:NIOT:MEAS:PRACh:LIMit:PDYNamics <Enable>, <OnPowerUpper>,

<OnPowerLower>, <OffPowerUpper>
Defines limits for the ON power and OFF power determined with the power dynamics
measurement.
Parameters:
<Enable> OFF | ON
*RST: ON
<OnPowerUpper> numeric
Upper limit for the ON power
*RST: -3.5 dBm
Default unit: dBm
<OnPowerLower> numeric
Lower limit for the ON power
*RST: -18.5 dBm
Default unit: dBm
<OffPowerUpper> numeric
Upper limit for the OFF power
*RST: -48.5 dBm
Default unit: dBm
Manual operation: See "Power dynamics limit settings" on page 436
5.5.3.9 Detected Subcarriers
The following commands return in which subcarriers preambles have been received.
FETCh:NIOT:MEAS:PRACh:MODulation:SCSGroup?................................................... 460
FETCh:NIOT:MEAS:PRACh:MODulation:SCSGroup:PREamble<Number>?................... 460
User Manual 1178.5689.02 ─ 12 459

Command Reference
FETCh:NIOT:MEAS:PRACh:MODulation:SCSGroup?
Returns the numbers of the subcarriers used by the symbol groups of the preamble, for
single-preamble measurements.
See also Chapter 5.2.6, "NB-IoT Preamble Structure", on page 417.
Return values:
<SubCarr1> decimal
Subcarrier number for the first symbol group
<SubCarr2> decimal
Subcarrier number for the second symbol group
<SubCarr3> decimal
Subcarrier number for the third symbol group
<SubCarr4> decimal
Subcarrier number for the fourth symbol group
Usage: Query only
FETCh:NIOT:MEAS:PRACh:MODulation:SCSGroup:PREamble<Number>?
Returns the numbers of the subcarriers used by the symbol groups of a selected pre-
amble, for multi-preamble measurements.
See also Chapter 5.2.6, "NB-IoT Preamble Structure", on page 417.
Suffix: .
<Number> 1..32
Selects a preamble from the range of measured preambles
Return values:
<SubCarr1> decimal
Subcarrier number for the first symbol group
<SubCarr2> decimal
Subcarrier number for the second symbol group
<SubCarr3> decimal
Subcarrier number for the third symbol group
<SubCarr4> decimal
Subcarrier number for the fourth symbol group
User Manual 1178.5689.02 ─ 12 460

Command Reference

Usage: Query only
5.5.3.10 EVM vs. Symbol Results (Traces)
The following commands return the EVM vs. symbol traces of the NPRACH measure-
ment.
FETCh:NIOT:MEAS:PRACh:TRACe:EVM:CURRent?
FETCh:NIOT:MEAS:PRACh:TRACe:EVM:AVERage?
FETCh:NIOT:MEAS:PRACh:TRACe:EVM:MAXimum?
READ:NIOT:MEAS:PRACh:TRACe:EVM:CURRent?
READ:NIOT:MEAS:PRACh:TRACe:EVM:AVERage?
READ:NIOT:MEAS:PRACh:TRACe:EVM:MAXimum?
Return the values of the EVM vs. symbol traces. Each value is averaged over the sam-
ples in one preamble symbol. The results of the current, average and maximum traces
can be retrieved.
See also Chapter 5.3.2.2, "Views EVM, Magnitude Error, Phase Error", on page 420.
Return values:
<Results> float
Comma-separated list of 20 results, one result per symbol
Default unit: %
Usage: Query only
5.5.3.11 Magnitude Error Results (Traces)
The following commands return the magnitude error vs. symbol traces of the NPRACH
measurement.
FETCh:NIOT:MEAS:PRACh:TRACe:MERRor:CURRent?
FETCh:NIOT:MEAS:PRACh:TRACe:MERRor:AVERage?
FETCh:NIOT:MEAS:PRACh:TRACe:MERRor:MAXimum?
READ:NIOT:MEAS:PRACh:TRACe:MERRor:CURRent?
READ:NIOT:MEAS:PRACh:TRACe:MERRor:AVERage?
READ:NIOT:MEAS:PRACh:TRACe:MERRor:MAXimum?
Return the values of the magnitude error traces. Each value is averaged over the sam-
ples in one preamble symbol. The results of the current, average and maximum traces
can be retrieved.
User Manual 1178.5689.02 ─ 12 461

Command Reference
Return values:
<Results> float
Default unit: %
Usage: Query only
5.5.3.12 Phase Error Results (Traces)
The following commands return the phase error vs. symbol traces of the NPRACH
measurement.
FETCh:NIOT:MEAS:PRACh:TRACe:PERRor:CURRent?
FETCh:NIOT:MEAS:PRACh:TRACe:PERRor:AVERage?
FETCh:NIOT:MEAS:PRACh:TRACe:PERRor:MAXimum?
READ:NIOT:MEAS:PRACh:TRACe:PERRor:CURRent?
READ:NIOT:MEAS:PRACh:TRACe:PERRor:AVERage?
READ:NIOT:MEAS:PRACh:TRACe:PERRor:MAXimum?
Return the values of the phase error traces. Each value is averaged over the samples
in one preamble symbol. The results of the current, average and maximum traces can
be retrieved.
Return values:
<Results> float
Default unit: dBm
Usage: Query only
5.5.3.13 EVM vs. Preamble Results (Traces)
The following commands return the EVM vs. preamble trace of the NPRACH measure-
ment.
User Manual 1178.5689.02 ─ 12 462

Command Reference
FETCh:NIOT:MEAS:PRACh:TRACe:EVPReamble?
READ:NIOT:MEAS:PRACh:TRACe:EVPReamble?
Return the values of the EVM vs. preamble traces.
See also Chapter 5.3.2.3, "Views EVM vs Preamble, Power vs Preamble",
on page 421.
Return values:
<Results> float
Comma-separated list of 32 EVM values, for preamble 1 to 32
(NCAP for not measured preambles)
Default unit: %
Usage: Query only
5.5.3.14 Power vs. Preamble Results (Traces)
The following commands return the power vs. preamble trace of the NPRACH mea-
surement.
FETCh:NIOT:MEAS:PRACh:TRACe:PVPReamble?
READ:NIOT:MEAS:PRACh:TRACe:PVPReamble?
Return the values of the power vs. preamble traces.
on page 421.
Return values:
<Results> float
Comma-separated list of 32 power values, for preamble 1 to 32
(NCAP for not measured preambles)
Default unit: dBm
Usage: Query only
5.5.3.15 I/Q Constellation Results (Traces)
The following command returns the results in the I/Q constellation diagram.
User Manual 1178.5689.02 ─ 12 463

Command Reference
FETCh:NIOT:MEAS:PRACh:TRACe:IQ?
Returns the results in the I/Q constellation diagram.
The return order is: <Reliability>, <IPhase>1, <QPhase>1, <IPhase>2, <QPhase>2, ...
See also Chapter 5.3.2.4, "View I/Q Constellation", on page 423.

Return values:
<IPhase> float
Normalized I amplitude
<QPhase> float
Normalized Q amplitude
Usage: Query only
5.5.3.16 Power Dynamics Results (Traces)
The following commands return the results in the power dynamics diagram.
FETCh:NIOT:MEAS:PRACh:TRACe:PDYNamics:CURRent?
FETCh:NIOT:MEAS:PRACh:TRACe:PDYNamics:AVERage?
FETCh:NIOT:MEAS:PRACh:TRACe:PDYNamics:MAXimum?
READ:NIOT:MEAS:PRACh:TRACe:PDYNamics:CURRent?
READ:NIOT:MEAS:PRACh:TRACe:PDYNamics:AVERage?
READ:NIOT:MEAS:PRACh:TRACe:PDYNamics:MAXimum?
Return the values of the power dynamics traces. Each value is sampled with 96 Ts,
corresponding to 3.125 µs. The results of the current, average and maximum traces
can be retrieved.
Return values:
<Power> float
2816 power values, from -1200 µs to +7596.875 µs relative to
the start of the preamble. The values have a spacing of
3.125 µs. The 385th value is at the start of the preamble (0 µs).
Default unit: dBm
Usage: Query only
User Manual 1178.5689.02 ─ 12 464

Command Reference
5.5.3.17 "TX Measurement" Results (Single Values)
The following commands return the statistical modulation results as presented in the
"TX Measurement" view.
CALCulate:NIOT:MEAS:PRACh:MODulation:CURRent?............................................... 465
CALCulate:NIOT:MEAS:PRACh:MODulation:AVERage?............................................... 465
FETCh:NIOT:MEAS:PRACh:MODulation:CURRent?.....................................................465
FETCh:NIOT:MEAS:PRACh:MODulation:AVERage?.....................................................465
FETCh:NIOT:MEAS:PRACh:MODulation:SDEViation?.................................................. 465
READ:NIOT:MEAS:PRACh:MODulation:CURRent?...................................................... 465
READ:NIOT:MEAS:PRACh:MODulation:AVERage?...................................................... 465
READ:NIOT:MEAS:PRACh:MODulation:SDEViation?................................................... 465
CALCulate:NIOT:MEAS:PRACh:MODulation:EXTReme?.............................................. 467
FETCh:NIOT:MEAS:PRACh:MODulation:EXTReme?....................................................467
READ:NIOT:MEAS:PRACh:MODulation:EXTReme?..................................................... 467
CALCulate:NIOT:MEAS:PRACh:MODulation:CURRent?
CALCulate:NIOT:MEAS:PRACh:MODulation:AVERage?
FETCh:NIOT:MEAS:PRACh:MODulation:CURRent?
FETCh:NIOT:MEAS:PRACh:MODulation:AVERage?
FETCh:NIOT:MEAS:PRACh:MODulation:SDEViation?
READ:NIOT:MEAS:PRACh:MODulation:CURRent?
READ:NIOT:MEAS:PRACh:MODulation:AVERage?
READ:NIOT:MEAS:PRACh:MODulation:SDEViation?
Return the current, average and standard deviation single value results.
Return values:
Default unit: %
<3_EVM_RMSLow> float
EVM RMS value, low EVM window position
Default unit: %
<4_EVM_RMSHigh> float
EVM RMS value, high EVM window position
Default unit: %
User Manual 1178.5689.02 ─ 12 465

Command Reference
<5_EVMpeakLow> float
EVM peak value, low EVM window position
Default unit: %
<6_EVMpeakHigh> float
EVM peak value, high EVM window position
Default unit: %
<7_MErr_RMSLow> float
Magnitude error RMS value, low EVM window position
Default unit: %
<8_MErr_RMSHigh> float
Magnitude error RMS value, high EVM window position
Default unit: %
<9_MErrPeakLow> float
Magnitude error peak value, low EVM window position
Default unit: %
<10_MErrPeakHigh> float
Magnitude error peak value, high EVM window position
Default unit: %
<11_PErr_RMSLow> float
Phase error RMS value, low EVM window position
Default unit: deg
<12_PErr_RMSHigh> float
Phase error RMS value, high EVM window position
Default unit: deg
<13_PErrPeakLow> float
Phase error peak value, low EVM window position
Default unit: deg
<14_PErrPeakHigh> float
Phase error peak value, high EVM window position
Default unit: deg
Default unit: Hz
Transmit time error
Default unit: Ts (basic time unit)
User Manual 1178.5689.02 ─ 12 466

Command Reference
<17_TXpower> float
Default unit: dBm
Default unit: dBm
Usage: Query only
CALCulate:NIOT:MEAS:PRACh:MODulation:EXTReme?
FETCh:NIOT:MEAS:PRACh:MODulation:EXTReme?
READ:NIOT:MEAS:PRACh:MODulation:EXTReme?
Returns the extreme single value results.
Return values:
<1_Reliability> Reliability Indicator
<2_OutOfTol> Out of tolerance result, i.e. percentage of measurement inter-
Default unit: %
<3_EVM_RMSlow> EVM RMS value, low EVM window position
Default unit: %
<4_EVM_RMShigh> EVM RMS value, high EVM window position
Default unit: %
<5_EVMpeakLow> EVM peak value, low EVM window position
Default unit: %
<6_EVMpeakHigh> EVM peak value, high EVM window position
Default unit: %
<7_MErr_RMSlow> Magnitude error RMS value, low EVM window position
Default unit: %
<8_MErr_RMShigh> Magnitude error RMS value, high EVM window position
Default unit: %
<9_MErrPeakLow> Magnitude error peak value, low EVM window position
Default unit: %
<10_MErrPeakHigh> Magnitude error peak value, high EVM window position
Default unit: %
User Manual 1178.5689.02 ─ 12 467

Command Reference
<11_PErr_RMSlow> Phase error RMS value, low EVM window position

Default unit: deg
<12_PErr_RMSh> Phase error RMS value, high EVM window position
Default unit: deg
<13_PErrPeakLow> Phase error peak value, low EVM window position
Default unit: deg
<14_PErrPeakHigh> Phase error peak value, high EVM window position
Default unit: deg
<15_FreqError> Carrier frequency error
Default unit: Hz
<16_TimingError> Transmit time error
<17_TXpowerMin> Minimum user equipment power
Default unit: dBm
<18_TXpowerMax> Maximum user equipment power
Default unit: dBm
<19_PeakPowMin> Minimum user equipment peak power
Default unit: dBm
<20_PeakPowMax> Maximum user equipment peak power
Default unit: dBm
Usage: Query only
5.5.3.18 EVM / Power vs. Preamble Results (Single Values)
The following commands return the single value modulation results as presented in the
"EMV vs Preamble" and "Power vs Preamble" views.
FETCh:NIOT:MEAS:PRACh:MODulation:PREamble<Number>?
READ:NIOT:MEAS:PRACh:MODulation:PREamble<Number>?
Return the single value results of the "EVM vs Preamble" and "Power vs Preamble"
views, for a selected preamble.
on page 421.
Suffix: .
<Number> 1..32
Number of the preamble for which the results are queried
User Manual 1178.5689.02 ─ 12 468

Command Reference
Return values:
<2_PreambleRel> decimal
Reliability indicator for the preamble
<3_EVM_RMSLow> float
EVM RMS value, low EVM window position
Default unit: %
<4_EVM_RMSHigh> float
EVM RMS value, high EVM window position
Default unit: %
<5_EVMpeakLow> float
EVM peak value, low EVM window position
Default unit: %
<6_EVMpeakHigh> float
EVM peak value, high EVM window position
Default unit: %
<7_MErr_RMSLow> float
Magnitude error RMS value, low EVM window position
Default unit: %
<8_MErr_RMSHigh> float
Magnitude error RMS value, high EVM window position
Default unit: %
<9_MErrPeakLow> float
Magnitude error peak value, low EVM window position
Default unit: %
<10_MErrPeakHigh> float
Magnitude error peak value, high EVM window position
Default unit: %
<11_PErr_RMSLow> float
Phase error RMS value, low EVM window position
Default unit: deg
<12_PErr_RMSH> float
Phase error RMS value, high EVM window position
Default unit: deg
<13_PErrPeakLow> float
Phase error peak value, low EVM window position
Default unit: deg
User Manual 1178.5689.02 ─ 12 469

Command Reference
<14_PErrPeakHigh> float
Phase error peak value, high EVM window position
Default unit: deg
Default unit: Hz
Transmit time error
<17_TXpower> float
Default unit: dBm
Default unit: dBm
Usage: Query only
5.5.3.19 Power Dynamics Results (Single Values)
The following commands return the statistical results of the power dynamics measure-
ment.
CALCulate:NIOT:MEAS:PRACh:PDYNamics:CURRent?
CALCulate:NIOT:MEAS:PRACh:PDYNamics:AVERage?
CALCulate:NIOT:MEAS:PRACh:PDYNamics:MINimum?
CALCulate:NIOT:MEAS:PRACh:PDYNamics:MAXimum?
FETCh:NIOT:MEAS:PRACh:PDYNamics:CURRent?
FETCh:NIOT:MEAS:PRACh:PDYNamics:AVERage?
FETCh:NIOT:MEAS:PRACh:PDYNamics:MINimum?
FETCh:NIOT:MEAS:PRACh:PDYNamics:MAXimum?
FETCh:NIOT:MEAS:PRACh:PDYNamics:SDEViation?
READ:NIOT:MEAS:PRACh:PDYNamics:CURRent?
READ:NIOT:MEAS:PRACh:PDYNamics:AVERage?
READ:NIOT:MEAS:PRACh:PDYNamics:MINimum?
READ:NIOT:MEAS:PRACh:PDYNamics:MAXimum?
READ:NIOT:MEAS:PRACh:PDYNamics:SDEViation?
Return the current, average, minimum, maximum and standard deviation single value
results of the power dynamics measurement.
User Manual 1178.5689.02 ─ 12 470

List of commands
Return values:
vals of the statistic count for power dynamics measurements
exceeding the specified power dynamics limits.
Default unit: %
<OffPowerBefore> float
OFF power before the preamble
Default unit: dBm
<OnPowerRMS> float
ON power mean value
Default unit: dBm
<OnPowerPeak> float
ON power peak value
Default unit: dBm
<OffPowerAfter> float
OFF power after the preamble
Default unit: dBm
Usage: Query only
5.5.4 Combined Signal Path Commands
For some settings, the command to be used depends on the active scenario. While the
combined signal path (CSP) scenario is active, these settings are configured via com-
mands of the signaling application. While the standalone (SA) scenario is active, they
are configured via measurement commands.
There are no NPRACH measurement settings controlled by the signaling application.
For general measurement settings, see Table 4-5.

ABORt:NIOT:MEAS:PRACh..................................................................................................................... 447
CALCulate:NIOT:MEAS:PRACh:MODulation:AVERage?.........................................................................465
CALCulate:NIOT:MEAS:PRACh:MODulation:CURRent?.........................................................................465
CALCulate:NIOT:MEAS:PRACh:MODulation:EXTReme?........................................................................467
CALCulate:NIOT:MEAS:PRACh:PDYNamics:AVERage?........................................................................ 470
User Manual 1178.5689.02 ─ 12 471

List of commands
CALCulate:NIOT:MEAS:PRACh:PDYNamics:CURRent?........................................................................ 470
CALCulate:NIOT:MEAS:PRACh:PDYNamics:MAXimum?....................................................................... 470
CALCulate:NIOT:MEAS:PRACh:PDYNamics:MINimum?........................................................................ 470
CONFigure:NIOT:MEAS:PRACh:LIMit:EVMagnitude............................................................................... 457
CONFigure:NIOT:MEAS:PRACh:LIMit:FERRor........................................................................................458
CONFigure:NIOT:MEAS:PRACh:LIMit:MERRor.......................................................................................457
CONFigure:NIOT:MEAS:PRACh:LIMit:PDYNamics................................................................................. 459
CONFigure:NIOT:MEAS:PRACh:LIMit:PERRor....................................................................................... 458
CONFigure:NIOT:MEAS:PRACh:MODulation:EWLength.........................................................................453
CONFigure:NIOT:MEAS:PRACh:MODulation:EWPosition.......................................................................454
CONFigure:NIOT:MEAS:PRACh:MOEXception....................................................................................... 452
CONFigure:NIOT:MEAS:PRACh:NOPReambles..................................................................................... 452
CONFigure:NIOT:MEAS:PRACh:PFORmat............................................................................................. 452
CONFigure:NIOT:MEAS:PRACh:POPReambles......................................................................................452
CONFigure:NIOT:MEAS:PRACh:REPetition............................................................................................ 451
CONFigure:NIOT:MEAS:PRACh:RESult:EVMagnitude............................................................................450
CONFigure:NIOT:MEAS:PRACh:RESult:EVPReamble............................................................................450
CONFigure:NIOT:MEAS:PRACh:RESult:IQ............................................................................................. 450
CONFigure:NIOT:MEAS:PRACh:RESult:MERRor................................................................................... 450
CONFigure:NIOT:MEAS:PRACh:RESult:PDYNamics..............................................................................450
CONFigure:NIOT:MEAS:PRACh:RESult:PERRor.................................................................................... 450
CONFigure:NIOT:MEAS:PRACh:RESult:PVPReamble............................................................................450
CONFigure:NIOT:MEAS:PRACh:RESult:TXM..........................................................................................450
CONFigure:NIOT:MEAS:PRACh:RESult[:ALL].........................................................................................449
CONFigure:NIOT:MEAS:PRACh:SCONdition.......................................................................................... 451
CONFigure:NIOT:MEAS:PRACh:SCOunt:MODulation.............................................................................453
CONFigure:NIOT:MEAS:PRACh:SCOunt:PDYNamics............................................................................ 454
CONFigure:NIOT:MEAS:PRACh:TOUT....................................................................................................450
FETCh:NIOT:MEAS:PRACh:MODulation:AVERage?...............................................................................465
FETCh:NIOT:MEAS:PRACh:MODulation:CURRent?...............................................................................465
FETCh:NIOT:MEAS:PRACh:MODulation:EXTReme?..............................................................................467
FETCh:NIOT:MEAS:PRACh:MODulation:PREamble<Number>?............................................................ 468
FETCh:NIOT:MEAS:PRACh:MODulation:SCSGroup:PREamble<Number>?..........................................460
FETCh:NIOT:MEAS:PRACh:MODulation:SCSGroup?.............................................................................460
FETCh:NIOT:MEAS:PRACh:MODulation:SDEViation?............................................................................465
FETCh:NIOT:MEAS:PRACh:PDYNamics:AVERage?.............................................................................. 470
FETCh:NIOT:MEAS:PRACh:PDYNamics:CURRent?.............................................................................. 470
FETCh:NIOT:MEAS:PRACh:PDYNamics:MAXimum?............................................................................. 470
FETCh:NIOT:MEAS:PRACh:PDYNamics:MINimum?.............................................................................. 470
FETCh:NIOT:MEAS:PRACh:PDYNamics:SDEViation?........................................................................... 470
FETCh:NIOT:MEAS:PRACh:STATe:ALL?................................................................................................ 448
FETCh:NIOT:MEAS:PRACh:STATe?........................................................................................................447
FETCh:NIOT:MEAS:PRACh:TRACe:EVM:AVERage?............................................................................. 461
FETCh:NIOT:MEAS:PRACh:TRACe:EVM:CURRent?............................................................................. 461
FETCh:NIOT:MEAS:PRACh:TRACe:EVM:MAXimum?............................................................................ 461
FETCh:NIOT:MEAS:PRACh:TRACe:EVPReamble?................................................................................463
FETCh:NIOT:MEAS:PRACh:TRACe:IQ?..................................................................................................464
FETCh:NIOT:MEAS:PRACh:TRACe:MERRor:AVERage?....................................................................... 461
FETCh:NIOT:MEAS:PRACh:TRACe:MERRor:CURRent?....................................................................... 461
FETCh:NIOT:MEAS:PRACh:TRACe:MERRor:MAXimum?...................................................................... 461
User Manual 1178.5689.02 ─ 12 472

List of commands
FETCh:NIOT:MEAS:PRACh:TRACe:PDYNamics:AVERage?................................................................. 464
FETCh:NIOT:MEAS:PRACh:TRACe:PDYNamics:CURRent?..................................................................464
FETCh:NIOT:MEAS:PRACh:TRACe:PDYNamics:MAXimum?................................................................ 464
FETCh:NIOT:MEAS:PRACh:TRACe:PERRor:AVERage?........................................................................462
FETCh:NIOT:MEAS:PRACh:TRACe:PERRor:CURRent?........................................................................462
FETCh:NIOT:MEAS:PRACh:TRACe:PERRor:MAXimum?.......................................................................462
FETCh:NIOT:MEAS:PRACh:TRACe:PVPReamble?................................................................................463
INITiate:NIOT:MEAS:PRACh.................................................................................................................... 447
READ:NIOT:MEAS:PRACh:MODulation:AVERage?................................................................................ 465
READ:NIOT:MEAS:PRACh:MODulation:CURRent?................................................................................ 465
READ:NIOT:MEAS:PRACh:MODulation:EXTReme?............................................................................... 467
READ:NIOT:MEAS:PRACh:MODulation:PREamble<Number>?............................................................. 468
READ:NIOT:MEAS:PRACh:MODulation:SDEViation?............................................................................. 465
READ:NIOT:MEAS:PRACh:PDYNamics:AVERage?................................................................................470
READ:NIOT:MEAS:PRACh:PDYNamics:CURRent?................................................................................470
READ:NIOT:MEAS:PRACh:PDYNamics:MAXimum?...............................................................................470
READ:NIOT:MEAS:PRACh:PDYNamics:MINimum?................................................................................470
READ:NIOT:MEAS:PRACh:PDYNamics:SDEViation?.............................................................................470
READ:NIOT:MEAS:PRACh:TRACe:EVM:AVERage?.............................................................................. 461
READ:NIOT:MEAS:PRACh:TRACe:EVM:CURRent?...............................................................................461
READ:NIOT:MEAS:PRACh:TRACe:EVM:MAXimum?............................................................................. 461
READ:NIOT:MEAS:PRACh:TRACe:EVPReamble?................................................................................. 463
READ:NIOT:MEAS:PRACh:TRACe:MERRor:AVERage?........................................................................ 461
READ:NIOT:MEAS:PRACh:TRACe:MERRor:CURRent?.........................................................................461
READ:NIOT:MEAS:PRACh:TRACe:MERRor:MAXimum?....................................................................... 461
READ:NIOT:MEAS:PRACh:TRACe:PDYNamics:AVERage?...................................................................464
READ:NIOT:MEAS:PRACh:TRACe:PDYNamics:CURRent?................................................................... 464
READ:NIOT:MEAS:PRACh:TRACe:PDYNamics:MAXimum?..................................................................464
READ:NIOT:MEAS:PRACh:TRACe:PERRor:AVERage?......................................................................... 462
READ:NIOT:MEAS:PRACh:TRACe:PERRor:CURRent?......................................................................... 462
READ:NIOT:MEAS:PRACh:TRACe:PERRor:MAXimum?........................................................................ 462
READ:NIOT:MEAS:PRACh:TRACe:PVPReamble?................................................................................. 463
STOP:NIOT:MEAS:PRACh.......................................................................................................................447
TRIGger:NIOT:MEAS:PRACh:CATalog:SOURce?................................................................................... 454
TRIGger:NIOT:MEAS:PRACh:MGAP....................................................................................................... 456
TRIGger:NIOT:MEAS:PRACh:SLOPe...................................................................................................... 455
TRIGger:NIOT:MEAS:PRACh:SOURce....................................................................................................455
TRIGger:NIOT:MEAS:PRACh:THReshold................................................................................................455
TRIGger:NIOT:MEAS:PRACh:TOUT........................................................................................................ 456
User Manual 1178.5689.02 ─ 12 473

R&S®CMW290/500 Index
Index
A Default paging cycle
NB-IoT signaling ......................................................... 98
Add NB-IoT signaling to logging ...................................... 110 Delta seq. shift
Application cards ............................................................... 10 NB-IoT multi-evaluation measurement ..................... 314
Application notes ............................................................... 10 DL RMC
Assign views NB-IoT signaling ......................................................... 24
NB-IoT measurement ............................................... 326 DL RMC connection settings
Authentication NB-IoT signaling ................................................... 85, 86
NB-IoT signaling ......................................................... 75 Documentation overview ..................................................... 9
AWGN Doppler frequency
NB-IoT signaling ......................................................... 58 NB-IoT signaling ......................................................... 55
AWGN fading module Downlink power levels
DRX cycle
B NB-IoT signaling ....................................................... 100
Duplex mode
Band NB-IoT measurement ............................................... 306
NB-IoT measurement ............................................... 308 NB-IoT signaling ......................................................... 61
NB-IoT signaling ......................................................... 50
Brochure ............................................................................ 10 E
C eDRX
NB-IoT signaling ............................................... 101, 103
Cell identifier Effective signal BW
Cell reselection Event log
Description .................................................................. 31 NB-IoT signaling ......................................................... 35
NB-IoT signaling ......................................................... 73 EVM window length
Channel NB-IoT NPRACH measurement ............................... 431
NB-IoT measurement ............................................... 308 EVM window position
NB-IoT signaling ......................................................... 50 NB-IoT NPRACH measurement ............................... 431
Channel bandwidth Expected nominal power
NB-IoT multi-evaluation measurement ..................... 312 NB-IoT measurement ............................................... 308
NB-IoT NPRACH measurement ............................... 429 NB-IoT signaling ......................................................... 52
Clear External attenuation
NB-IoT signaling ....................................................... 109 NB-IoT signaling ......................................................... 49
Coding group External attenuation (input)
NB-IoT signaling ....................................................... 107 NB-IoT measurement ............................................... 307
Combined signal path commands External delay compensation
NB-IoT multi-evaluation measurement ..................... 407 NB-IoT signaling ......................................................... 49
NB-IoT NPRACH measurement ............................... 471
Connected DRX F
NB-IoT signaling ......................................................... 99
Connection control hotkeys Fading profile
Connection states Fading simulator
Connection type Features & functions ........................................................... 9
NB-IoT signaling ......................................................... 81 Frequency
Cyclic prefix NB-IoT measurement ............................................... 308
NB-IoT multi-evaluation measurement ..................... 312 NB-IoT signaling ......................................................... 50
Frequency offset
D NB-IoT measurement ............................................... 308
NB-IoT signaling ......................................................... 51
Data coding / character set
NB-IoT signaling ............................................... 106, 109 G
Data inactivity timer
NB-IoT signaling ......................................................... 83 Getting started manual ........................................................ 9
Data sheet ......................................................................... 10 Go to
Debug NB-IoT signaling ......................................................... 46
NB-IoT signaling ........................................................110
Default IMSI
NB-IoT signaling ......................................................... 76
User Manual 1178.5689.02 ─ 12 474

H N
HARQ settings NB-IoT BLER
NB-IoT signaling ......................................................... 87 NB-IoT signaling ....................................................... 257
Help ..................................................................................... 9 NB-IoT BLER measurement
Hysteresis for reselection Command reference ................................................. 265
NB-IoT signaling ......................................................... 74 GUI reference ........................................................... 258
Programming ............................................................ 264
I NB-IoT multi-evaluation measurement
Command reference ................................................. 335
Inactivity timer GUI reference ........................................................... 291
NB-IoT signaling ....................................................... 100 Limits ........................................................................ 319
Insertion loss Measurement description ......................................... 279
NB-IoT signaling ......................................................... 54 Programming ............................................................ 328
Integrity algorithm Results ...................................................................... 292
NB-IoT signaling ......................................................... 75 NB-IoT NPRACH measurement
K GUI reference ........................................................... 418
Limits ........................................................................ 434
Keep RRC connection Measurement description ......................................... 414
NB-IoT signaling ......................................................... 82 Programming ............................................................ 436
Results ...................................................................... 419
L NB-IoT signaling
Large SMS handling
General description ..................................................... 13
NB-IoT signaling ....................................................... 105
GUI reference ............................................................. 32
Limits
Programming .............................................................112
NB-IoT multi-evaluation measurement ..................... 319
Softkey ........................................................................ 44
Neighbor cell
List mode
NB-IoT signaling ......................................................... 72
Noise
Logging PC IPv4 address
NB-IoT signaling ......................................................... 55
NB-IoT signaling ........................................................110
Noise bandwidth
M NB-IoT signaling ......................................................... 56
NPRACH preamble format
Margin NB-IoT NPRACH measurement ............................... 430
NB-IoT signaling ......................................................... 52 NPRACH settings
Marker NB-IoT signaling ......................................................... 65
NB-IoT multi-evaluation measurement ..................... 304 NPUSCH format
NB-IoT NPRACH measurement ............................... 426 NB-IoT multi-evaluation measurement ..................... 312
Max. allowed power P-Max NRS EPRE
MCC Number of preambles
Measure on exception
NB-IoT multi-evaluation measurement ......................311 O
OCNG
Measurement mode
NB-IoT signaling ......................................................... 57
NB-IoT multi-evaluation measurement ......................311
On duration timer
Message class
NB-IoT signaling ....................................................... 100
NB-IoT signaling ....................................................... 107
Open source acknowledgment (OSA) ............................... 10
Message length
Originating address
NB-IoT signaling ....................................................... 109
NB-IoT signaling ....................................................... 107
Message text
Originator SMSC address
NB-IoT signaling ....................................................... 109
NB-IoT signaling ....................................................... 107
Minimum noise/system BW ratio
Out of sync
NB-IoT signaling ......................................................... 56
NB-IoT signaling ......................................................... 77
Mixer level offset
Outgoing message handling
NB-IoT measurement ............................................... 309
NB-IoT signaling ....................................................... 106
NB-IoT signaling ......................................................... 52
Outgoing SMS
MNC
NB-IoT signaling ....................................................... 106
NB-IoT signaling ......................................................... 74
Outgoing SMS binary
Modulation scheme
NB-IoT signaling ....................................................... 106
User Manual 1178.5689.02 ─ 12 475

P Secret key
NB-IoT signaling ......................................................... 76
Period of preambles Security
Physical cell ID Select as fixed target
NB-IoT multi-evaluation measurement ..................... 314 NB-IoT signaling ..................................................46, 110
NB-IoT signaling ......................................................... 62 Select menu
Physical cell setup NB-IoT signaling ..................................................46, 110
NB-IoT signaling ......................................................... 61 Service center time stamp
Power-saving mode NB-IoT signaling ....................................................... 107
NB-IoT signaling ......................................................... 98 Signal to noise ratio
Programming NB-IoT signaling ......................................................... 57
NB-IoT BLER measurement ..................................... 264 Signaling parameter
NB-IoT multi-evaluation measurement ..................... 328 NB-IoT measurement ............................................... 327
NB-IoT NPRACH measurement ............................... 436 SMS file selection
NB-IoT signaling ........................................................112 NB-IoT signaling ............................................... 108, 109
Protocol identifier Start offset (DRX)
NB-IoT signaling ....................................................... 106 NB-IoT signaling ....................................................... 101
Start seed
Q NB-IoT signaling ......................................................... 54
Statistic count
Q qualmin NB-IoT multi-evaluation measurement ..................... 315
NB-IoT signaling ......................................................... 73 Statistic count (dynamics)
Quick start guide ................................................................. 9 NB-IoT NPRACH measurement ............................... 431
Statistic count (modulation)
R NB-IoT NPRACH measurement ............................... 430
Stop condition
Release assistance indication NB-IoT multi-evaluation measurement ......................311
Release notes ................................................................... 10 Subcarrier spacing
Repetition NB-IoT signaling ......................................................... 62
NB-IoT NPRACH measurement ............................... 429 T
Resource allocation
NB-IoT multi-evaluation measurement ..................... 312 T3324
Restart event NB-IoT signaling ......................................................... 77
NB-IoT signaling ......................................................... 54 T3412
Results NB-IoT signaling ......................................................... 77
NB-IoT multi-evaluation measurement ..................... 292 TAC
Retransmission timer Test mode
NB-IoT signaling ....................................................... 100 NB-IoT signaling ......................................................... 81
RF routing Test setups
RMC Time hysteresis for reselection
NB-IoT signaling ................................................... 23, 24 NB-IoT signaling ......................................................... 74
Routing Trigger settings
NB-IoT signaling ......................................................... 49 NB-IoT multi-evaluation measurement ..................... 317
S Trigger signals
NB-IoT signaling ......................................................... 31
S NonIntraSearch
NB-IoT signaling ......................................................... 73 U
Safety instructions ............................................................. 10
Scenario UE capabilities
NB-IoT signaling ......................................................... 46 UE info
Scheduling request NB-IoT signaling ......................................................... 35
NB-IoT signaling ....................................................... 101 UE measurement report
Scheduling type NB-IoT signaling ......................................................... 42
NB-IoT signaling ......................................................... 83 UL retransmission timer
Scheduling type DL RMC NB-IoT signaling ....................................................... 101
NB-IoT signaling ......................................................... 24 UL RMC
Scheduling type UL RMC NB-IoT signaling ......................................................... 23
NB-IoT signaling ......................................................... 23 UL RMC connection settings
Scheduling type user-defined NB-IoT signaling ......................................................... 84
NB-IoT signaling ......................................................... 24
User Manual 1178.5689.02 ─ 12 476

Uplink nominal power

NB-IoT signaling ......................................................... 58
User data header
NB-IoT signaling ....................................................... 106
User manual ........................................................................ 9
User margin
NB-IoT measurement ............................................... 309
User-defined channels
NB-IoT signaling ......................................................... 24
W
White papers ..................................................................... 10
User Manual 1178.5689.02 ─ 12 477

CMW NBIoT UE UserManual V3-8-30 en 12

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CMW NBIoT UE UserManual V3-8-30 en 12

Uploaded by

Copyright:

Available Formats

R&S®CMW290/500

NB-IoT UE Firmware Applications

© 2021 Rohde & Schwarz GmbH & Co. KG

1178.5689.02 | Version 12 | R&S®CMW290/500

User Manual 1178.5689.02 ─ 12 3

2.2.14 Cell Reselection Setup..................................................................................................31

User Manual 1178.5689.02 ─ 12 4

2.5.13 Connection Configuration............................................................................................198

3 NB-IoT BLER Measurement.............................................................. 257

4 NB-IoT Multi-Evaluation Measurement............................................ 279

User Manual 1178.5689.02 ─ 12 5

4.3.3 Signal Routing and Analyzer Settings.........................................................................306

5 NB-IoT NPRACH Measurement.........................................................414

User Manual 1178.5689.02 ─ 12 6

User Manual 1178.5689.02 ─ 12 7

User Manual 1178.5689.02 ─ 12 8

1.1 Documentation Overview

1.1.1 Getting Started Manual / Quick Start Guide

Depending on your instrument model, there is either a getting started manual or a

1.1.2 User Manual and Help

1.1.3 Features & Functions

User Manual 1178.5689.02 ─ 12 9

1.1.4 Basic Safety Instructions

Contains safety instructions in many languages.

1.1.5 Data Sheet and Brochure

1.1.6 Release Notes and Open-Source Acknowledgment (OSA)

1.1.7 Application Notes, Application Cards, White Papers, etc.

These documents deal with special applications or background information on particu-

1.2 How to Read Firmware Application Chapters

Each firmware application is described in a separate chapter. These chapters can be

2. Application sheets (optional)

User Manual 1178.5689.02 ─ 12 10

1.2.1 General Description

This chapter provides a general description of the firmware application, independent of

1.2.2 Application Sheets

1.2.3 GUI Reference

1.2.4 Programming Examples

1.2.5 Command Reference

User Manual 1178.5689.02 ─ 12 11

User Manual 1178.5689.02 ─ 12 12

2.1 What's New

2.2 General Description

User Manual 1178.5689.02 ─ 12 13

2.2.1 Test Setup

R&S CMW RF COM

Figure 2-1: Test setup

2.2.2 Initiating Signaling Tests

The required settings vary depending on the measurement to be performed. However,

2. Open the "NB-IoT signaling" firmware application.

3. Configure the signaling application according to your test case.

5. Switch on the UE.

User Manual 1178.5689.02 ─ 12 14

6. If the RRC state is "Idle", press the "Connect" hotkey.

7. To switch to the measurement application, press the "NB-IoT TX Meas" or "NB-IoT

8. Configure and start the measurement.

If the UE fails to attach

If the measurement does not start

2.2.3 Internal Fading

2.2.3.1 Fading Simulator

User Manual 1178.5689.02 ─ 12 15

2.2.3.2 AWGN Generator

Additional white Gaussian noise (AWGN) is typically modeled in receiver tests,

2.2.4 Connection States