CMW DataApplicationUnit UserManual V3!5!21 en 14
CMW DataApplicationUnit UserManual V3!5!21 en 14
CMW DataApplicationUnit UserManual V3!5!21 en 14
(;L2)
User Manual
1173.9528.02 14
R&SCMW-B450A/B/D
Contents
Contents
1 Preface.................................................................................................... 7
1.1
1.2
1.2.1
General Description........................................................................................................ 8
1.2.2
Application Sheets.......................................................................................................... 8
1.2.3
GUI Reference................................................................................................................ 8
1.2.4
Programming Examples..................................................................................................8
1.2.5
Command Reference...................................................................................................... 9
Test Setup....................................................................................................................12
3.2
3.2.1
3.2.2
3.2.3
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
4 GUI Reference...................................................................................... 38
4.1
4.1.1
Overview Tab................................................................................................................ 39
4.1.2
IP Config Tab................................................................................................................ 40
4.1.3
DNS Tab....................................................................................................................... 46
4.1.4
FTP Tab........................................................................................................................ 50
R&SCMW-B450A/B/D
Contents
4.1.5
HTTP Tab......................................................................................................................52
4.1.6
IMS Tab.........................................................................................................................53
4.1.7
ePDG Tab..................................................................................................................... 76
4.1.8
4.2
4.2.1
RAN Selection...............................................................................................................86
4.2.2
Overview Tab................................................................................................................ 87
4.2.3
Ping Tab........................................................................................................................88
4.2.4
IPerf Tab....................................................................................................................... 90
4.2.5
Throughput Tab.............................................................................................................94
4.2.6
4.2.7
IP Logging Tab..............................................................................................................98
4.2.8
4.2.9
4.2.10
4.2.11
4.2.12
5 Programming......................................................................................127
5.1
5.1.1
5.1.2
5.1.3
5.1.4
5.1.5
5.1.6
5.1.7
5.1.8
5.1.9
5.2
5.2.1
5.2.2
5.2.3
5.2.4
R&SCMW-B450A/B/D
Contents
5.2.5
5.2.6
5.2.7
5.2.8
5.2.9
5.2.10
Performing IP Analysis................................................................................................142
6.1.1
MEAS<i>..................................................................................................................... 145
6.1.2
Keywords.................................................................................................................... 145
6.1.3
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
6.2.7
HTTP Service..............................................................................................................170
6.2.8
IMS Service.................................................................................................................171
6.2.9
6.3
6.3.1
RAN Selection.............................................................................................................213
6.3.2
6.3.3
IPerf Measurement......................................................................................................218
6.3.4
Throughput Measurement...........................................................................................227
6.3.5
6.3.6
IP Logging................................................................................................................... 235
6.3.7
IP Analysis.................................................................................................................. 239
6.3.8
IP Replay.....................................................................................................................258
6.3.9
6.3.10
R&SCMW-B450A/B/D
Contents
7.1
7.1.1
7.1.2
7.1.3
7.1.4
7.1.5
7.1.6
7.2
7.3
7.4
7.5
Corruption Rate.........................................................................................................286
List of Commands..............................................................................289
Index....................................................................................................296
R&SCMW-B450A/B/D
Preface
How to Read Firmware Application Chapters
1 Preface
The operation of the R&S CMW is described in several user manuals:
The R&S CMW user manual describes the base software, common features of the
firmware applications and basic principles for manual operation and remote control.
There is a separate manual version for each R&S CMW model.
Additional user manuals, like this document, describe the firmware applications.
There is only one version of these manuals for all R&S CMW models.
Rohde & Schwarz provides registered users a "CMW Customer Web" section on
GLORIS, the Global Rohde & Schwarz Information System: https://extranet.rohdeschwarz.com. From this resource, you can download software updates, waveform
library updates and documentation updates, for example updates of this document.
R&SCMW-B450A/B/D
Preface
How to Read Firmware Application Chapters
R&SCMW-B450A/B/D
Preface
How to Read Firmware Application Chapters
R&SCMW-B450A/B/D
ePDG service:
IMS server:
Throughput measurement:
Additional commands for trace query with a unique counter value per result,
see FETCh:DATA:MEAS<i>:THRoughput:TRACe:OVERall:ULINk:
EXTended?
10
R&SCMW-B450A/B/D
General Description
3 General Description
The Data Application Unit (DAU, option R&S CMW-B450A or -B450B or -B450D) provides a common data testing solution for supported radio access technologies.
It allows you to test End-to-End (E2E) IP data transfer and to perform user plane (Uplane) tests for an IP connection to a mobile. The connection can be set up via a signaling application or a protocol test application.
The DAU is independent of the underlying radio access network. It provides a common
user plane handling and ensures data continuity during handover from one radio
access technology to another one.
The DAU also hosts IP services that have been optimized for high throughput and are
running in an isolated controlled environment to ensure reproducible test results.
IP services
The following internal IP services are currently available:
IP Multimedia Subsystem (IMS) server supporting voice over IMS and SMS over
IMS (R&S CMW-KAA20 required)
Evolved packet data gateway (ePDG) for WLAN offloading (R&S CMW-KA065
required)
You can use the FTP and HTTP services for example to access the built-in DAU web
server from the mobile. If desired, you can add own web pages to the server. An additional hard disk provided with the DAU allows the storage of large media files for data
transfer tests.
The IMS server allows an IMS client on the mobile to register to the IMS domain.
Optionally, an authentication can be performed. After successful registration, you can
initiate mobile-originating and mobile-terminating voice over IMS calls. With two registered mobiles, you can perform mobile-to-mobile calls. Short messages over IMS are
also possible.
The DNS server can be used to answer DNS queries for IPv4 addresses, IPv6
addresses and domains supporting a specific service. The DNS server database is
configurable. Thus you can for example redirect the mobile to the web server of the
DAU when it tries to browse a specific Internet domain. DNS queries for which the local
database contains no matching entry can be forwarded to an external DNS server.
The ePDG acts as gateway to an untrusted WLAN network. It provides security mechanisms required for WLAN offloading tests where an IPsec tunnel from the core network through the WLAN network to the DUT must be set up.
The mini service layer for eMBMS provides unicast and multicast services for eMBMS
tests, controlled via CMWcards or via protocol test applications.
11
R&SCMW-B450A/B/D
General Description
Test Setup
IPerf measurement, testing the throughput and reliability, using TCP/IP and
UDP/IP
DNS request measurement, monitoring all DNS queries addressed to the internal
DNS server
IP logging application, creating log files of the IP traffic at the LAN DAU connector
or between DAU and mobile
IP analysis application, monitoring and analyzing the uplink and downlink IP traffic
of the mobile (R&S CMW-KM051 required in addition to R&S CMW-KM050)
Audio delay measurement, analyzing the transit time and timing error of voice call
audio packets
The DAU supports the internet protocols IPv4 and IPv6. Both can be used individually
or in parallel, depending on the IP connection established by the Radio Access Network. IPv4 requires option R&S CMW-KA100, IPv6 requires additionally option R&S
CMW-KA150.
Option R&S CMW-KA150 is also required for IP multicast traffic (IPv4 or IPv6) and
thus for eMBMS tests.
Usually, the DAU is installed on the R&S CMW that establishes the IP connection to
the mobile. If all expansion slots of this R&S CMW are occupied by other hardware
options, a DAU installed on another R&S CMW can be used instead. For such an
"external DAU" setup, option R&S CMW-KA120 is required on both instruments.
You can control the DAU manually via a graphical user interface or remotely via SCPI
commands. Protocol test applications can control the DAU via the CDAU interface.
The following sections describe possible test setups and the related initial configuration
of the network settings. They also provide an introduction to the DAU measurements.
12
R&SCMW-B450A/B/D
General Description
Test Setup
It depends on the application used to set up the IP connection and its configuration,
whether one or more RF connections are required and which RF connectors can be
used. For details refer to the documentation of the relevant signaling application or to
the protocol test documentation and set up the RF connection(s) as described there.
The used RF path (connector and converter) is known by the used application, but not
by the DAU. The DAU accesses the established IP connection via an internal ethernet
connection to the signaling units.
For scenarios involving only one downlink carrier and one uplink carrier, you use typically an RF COM connector, e.g. RF 1 COM, as shown in the following figure.
If you want to access external services with the mobile, connect the external network to
the LAN DAU connector at the rear panel of the instrument. Typically, you connect
your company LAN. With this setup, the mobile can access the network connected to
the LAN DAU connector and other networks reachable via this network, e.g. an application server in the internet. It can also access embedded DAU services, as with a
standalone setup.
Note that only the LAN DAU connector allows the DAU and thus the mobile to access
an external network and can be used for U-plane tests. The other LAN connectors of
the instrument cannot be used for this purpose. Especially do never connect your company LAN to the LAN SWITCH connector.
Connecting an external network, or not?
If you use a standalone test setup, you can use the predefined internal IP configuration. The default IP settings of the DAU are compatible to a standalone setup. No IP
network configuration is required. But the mobile can only access the embedded DAU
services, not an external network.
13
R&SCMW-B450A/B/D
General Description
Test Setup
If you connect an external network, you must configure the IP network settings of the
DAU compatible to the connected network. So more configuration than for a standalone setup is required. In return, the mobile can access the external network.
Table 3-1: Overview of setup characteristics
Standalone test setup
14
R&SCMW-B450A/B/D
General Description
Test Setup
Figure 3-2: Test setup with external DAU and connection to company LAN
The patch cable is only functional if the "Lan Remote" network adapter is integrated
into the internal IPv4 subnet of the instrument. For configuration of a compatible "Lan
Remote" IP address, refer to the description of the "Setup" dialog in the R&S CMW
user manual.
In the R&S CMW without DAU, you must enable the usage of the external DAU and
enter information about the subnet of the R&S CMW with DAU. These settings are provided by the application that establishes the IP connection, for example the LTE signaling application. Refer to the documentation of that application.
You can connect only one instrument without DAU to an instrument with DAU. You can
use the DAU for IP connections at both instruments, even simultaneously. However,
15
R&SCMW-B450A/B/D
General Description
Adapting the DAU IP Configuration
note that the DAU resources are shared by all applications using the DAU. To reach
high data rates, it may be required to use the DAU for one application at a time.
16
R&SCMW-B450A/B/D
General Description
Adapting the DAU IP Configuration
a) For a standalone setup, select "Automatic R&S CMW500 Network (standalone)" for IPv4 and IPv6. No further configuration is required.
b) For a setup with external network, configure the settings compatible to your
network, either by defining a static configuration or by using dynamic mechanisms supported by your network.
For an introduction to IP address formats and to the IP configuration methods
supported by the DAU, refer to the following sections.
For a description of the "IP Config" tab and its configuration dialog, see Chapter 4.1.2, "IP Config Tab", on page 40.
Please note that your changes may not apply to applications that are already generating a downlink signal. To ensure that your changes are effective for a protocol test,
restart the test. To apply them to a signaling application, switch the downlink signal off
and on again in the signaling application.
17
R&SCMW-B450A/B/D
General Description
Adapting the DAU IP Configuration
zeros within a block and by replacing consecutive blocks of zeros by a double colon
(only once per address).
Example - the following addresses are equivalent:
fcb1:cafe:0001:86c1:0000:0000:0000:0001
fcb1:cafe:1:86c1:0000:0000:0000:1
fcb1:cafe:1:86c1::1
The initial bits of an address are called prefix and identify the subnet. The maximum
length of the prefix is 64 bits. The remaining bits are called interface identifier and
uniquely identify a link within the subnet.
The DAU must know both its own address and the prefix identifying its subnet. This
information can be combined into a single string by appending the prefix length to the
address. Example: The address fcb1:cafe:1:86c1::1 with the initial 64 bits identifying the subnet can be written as fcb1:cafe:1:86c1::1/64.
IPv6 prefixes are written in the same notation (address + length). Prefixes with less
than 64 bits indicate a whole group of 64-bit prefixes with the same initial digits.
Examples for prefixes:
The DAU can use IP addresses/prefixes predefined within its software. This
method is appropriate for a standalone setup. The mobile can address the DAU,
but not any other host.
The DAU can request and receive dynamic IP addresses/prefixes from an external
network via the LAN DAU connector. The mobile can address both the DAU and
also hosts in external networks.
The following sections provide more detailed information about the three methods. For
IPv4, the same method is used for DAU addresses and mobile addresses. For IPv6,
you can also combine static and dynamic methods, i.e. use a static configuration of the
DAU address and a dynamic configuration of the mobile prefixes or vice versa. The
predefined configuration always applies to DAU and mobile.
18
R&SCMW-B450A/B/D
General Description
Adapting the DAU IP Configuration
The IPv4 and IPv6 configuration are completely independent, so you can use different
methods.
Predefined automatic address configuration
This method can only be used for a standalone setup, without connection of an external network. It is available for IPv4 and IPv6 and configures all address information
automatically. So you do not need to configure any IP addresses or prefixes at the
DAU, neither for the mobile, nor for the DAU.
This method is active by default.
Static address configuration
This method allows you to connect an external network or host to the LAN DAU connector. Configure all addresses and prefixes so that they are compatible to the external
network, typically your company network. It is advisable to contact the network administrator prior to configuration. The default values are usually not compatible to an external network and they are not routable in the Internet. But they can be used when connecting a host directly.
For IPv4, all configured static IP addresses must belong to the connected network.
Enter its subnet mask, specify the DAU address and define the mobile address pool. In
order to access internet servers, specify also the gateway address.
For IPv6, assign an IPv6 address to the DAU and define the IPv6 prefix pool for
mobiles. The DAU must belong to a subnet of the external network. For communication
with hosts outside of this subnet, specify an adequate default router belonging to the
subnet of the DAU. Additionally you may configure routes to other default routers or
instruments equipped with a DAU, see "Routing configuration" on page 20.
Dynamic address configuration
This method allows you to connect an external network or host to the LAN DAU connector. Addresses and prefixes are requested from the external network.
For IPv4, the IP address information is configured dynamically using DHCPv4. A
DHCP server must be available in the external network.
For IPv6, the DAU performs IPv6 autoconfiguration. It obtains IP address information
via Router Advertisements (RA) and/or via DHCPv6. The external network must either
contain a router supporting router advertisements or a DHCPv6 server - or both, configured compatible to each other.
Example, RA + DHCPv6: The router advertisement contains an IPv6 prefix and allows
the host (the DAU) to generate its own address using this prefix. It also indicates that
stateful configuration (DHCPv6) must be used to obtain optional information, like DNS
server addresses.
Depending on the content of the router advertisements, it may happen that the DAU
ends up with two assigned IPv6 addresses: one assigned via router advertisements
and one assigned via DHCPv6. In that case, both addresses are displayed in the "IP
Config" tab.
19
R&SCMW-B450A/B/D
General Description
Adapting the DAU IP Configuration
Dynamic configuration of the IPv6 prefix pool for the mobiles can be done via DHCP
prefix delegation. The external network must contain a router supporting prefix delegation via DHCPv6. The router delegates an IPv6 prefix to the DAU, typically with less
than 64 bit. The DAU is allowed to create 64-bit prefixes from the delegated prefix and
to assign the prefixes to mobiles.
Routing configuration
For IPv4, no routes need to be defined manually. The mobile, the DAU and external
network nodes connected to the DAU belong to the same subnet. So they know how to
reach each other. The configured gateway allows you to reach destinations outside of
the subnet.
For IPv6, the mobile and the DAU belong to different subnets. Thus some administration may be required to ensure that packets addressed to a specific mobile are routed
to the DAU where the mobile is connected. The administration tasks to be performed
depend on the use case and the configuration of the external network. Basically, you
must ensure that packets with a mobile IPv6 prefix as destination are routed to the correct DAU.
At the DAU, you can configure manual routes for packets sent by the mobile. To configure routes makes sense for destination addresses that do not belong to the subnet
of the DAU and cannot be reached via the configured default router. You could for
example route traffic for certain destinations to a different default router. Or you could
route packets for another mobile connected to another R&S CMW/DAU to that DAU.
Example: The mobile prefix pool of another DAU contains 64 bit prefixes starting with
fcb1:abab:cdcd. To create routes for all these prefixes, create a single route for the
prefix fcb1:abab:cdcd::/48 and specify the IP address of the other DAU as router
address.
20
R&SCMW-B450A/B/D
General Description
Configuring and Starting DAU Services
The interface identifier is a 64-bit value. It is sent via a NAS signaling message.
The used message depends on the RAT. Examples:
For GSM or WCDMA: "Activate PDP Context Accept"
For LTE: "Establish Default EPS Bearer Context Request"
3. The DAU sends an IPv6 prefix to the mobile.
The prefix is a 64-bit value. It is sent after the flow activation (bearer establishment)
in an ICMPv6 router advertisement message.
Any subsequent router advertisement messages also include the prefix. They are
sent to the mobile periodically and if the mobile sends a router solicitation message.
4. The mobile composes an IPv6 address.
It uses the received interface identifier to form a link-local IPv6 address as follows:
fe80::<interface identifier>.
Additionally, the mobile can form a global IPv6 address. For the global address, the
mobile must use the received prefix and can use the received interface identifier or
select a different one. The address is combined as follows:
<prefix>::<interface identifier>.
Example: Prefix fcb1:abab:cdcd:efe0::/64, interface identifier 1
Global IPv6 address fcb1:abab:cdcd:efe0::1/64
Chapter 3.6, "Using the ePDG Service for WLAN Offload", on page 30
21
R&SCMW-B450A/B/D
General Description
Configuring and Running DAU Measurements
22
R&SCMW-B450A/B/D
General Description
Using the IMS Server
2. Find out which IP address has been assigned to the mobile. You may for example
check the message log files created by the protocol test.
3. Open the "Data Application Measurements" dialog.
For detailed steps see "Opening the "Data Application Measurements" dialog"
on page 23.
4. Configure and start a DAU measurement, for example "Ping" or "IPerf".
For most measurements, you must enter the IP address of the mobile to select the
IP connection to be analyzed.
See also "Configuring and starting a DAU measurement" on page 23.
Protocol tests may also integrate DAU measurements into their test sequence. In that
case, the protocol test controls the DAU via the so-called CDAU interface to configure
the measurement settings and retrieve the measurement results.
While the CDAU interface is used, the GUI of the DAU is hidden in a similar way as
during a remote control session with SCPI commands. When the GUI is displayed
again, the settings valid prior to the CDAU session are restored automatically and the
displayed results are reset.
Opening the "Data Application Measurements" dialog
1. Press MEASURE to open the "Measurement Controller" dialog.
2. Enable "Data Appl. > Measurements"
3. Press "Data Meas" on the task bar at the bottom.
The "Data Application Measurements" dialog opens. The "Overview" tab provides a
summary of the measurement states.
Configuring and starting a DAU measurement
1. Select the corresponding tab, for example, "Ping".
2. Configure the settings available directly on the tab or accessible via the "Config"
hotkey.
3. Select the topmost softkey, for example "Ping", and press ON/OFF to start the
measurement.
The measurement results are provided in the same tab.
23
R&SCMW-B450A/B/D
General Description
Using the IMS Server
This section provides an overview of the IMS server settings, followed by several basic
step-by-step procedures:
General settings
The "Config" hotkey accesses the general settings. They select whether the internal IMS server or an external IMS network is used.
The remainder of this section assumes that you use the internal IMS server.
For a GUI description, see Chapter 4.1.6.5, "General IMS Settings", on page 57.
P-CSCF settings
The "P-CSCF" hotkey accesses settings related to the simulated P-CSCF. They
define the P-CSCF address and the reaction of the P-CSCF on incoming SIP messages from a mobile.
You can define several P-CSCF profiles with different addresses and settings. A
list of all P-CSCFs is sent to the mobile. The mobile selects a P-CSCF from the list
for registration.
Two P-CSCF profiles are predefined and ready-to-use, one for IPv4 and one for
IPv6.
For a GUI description, see Chapter 4.1.6.6, "P-CSCF Settings", on page 58.
Subscriber settings
The "Subscriber" hotkey accesses settings related to the tested mobiles. They
define the private user ID, the public user IDs and authentication settings.
You can define several subscriber profiles, for example if you use SIM cards with
different properties. If all your test SIM cards have the same properties, one subscriber profile is sufficient.
The applicable profile is selected via the user ID included in SIP messages from
the mobile.
For a GUI description, see Chapter 4.1.6.7, "Subscriber Settings", on page 61.
24
R&SCMW-B450A/B/D
General Description
Using the IMS Server
d) Press OK.
2. Press ON | OFF or right-click the "IMS Service" softkey and click ON.
The IMS service is started. Wait until the "IMS Service" softkey displays the state
"ON".
3. Configure the signaling application to be used, for example the LTE signaling application. Usually, you must explicitly enable data tests in the signaling application.
For details, refer to the documentation of the signaling application.
4. Let the mobile register/attach to the signaling application.
Afterwards, the UE automatically registers also to the IMS server. You can check
the successful registration in the "General IMS Info" area on the IMS tab.
25
R&SCMW-B450A/B/D
General Description
Using the IMS Server
The displayed URI is generated automatically and registered in addition to the public user IDs configured for the subscriber profile. Each registration with a different
IP address gets a unique URI, even if the same subscriber profile is used.
If the registration to the IMS fails, see "Troubleshooting a failed registration"
on page 29.
Setting up a mobile-originating voice over IMS call
Initial situation: The mobile has registered to the IMS server. There is only one virtual
subscriber profile "Virtual 1". The GUI shows the "IMS" tab of the "Data Application
Control" dialog.
1. Press the "Virtual Subscriber" hotkey.
A dialog box opens.
2. Configure the "Virtual 1" tab as follows:
a) Set the "Signaling Type" compatible to your mobile (call setup with or without
SIP preconditions).
b) For all other settings, we use the default values:
26
R&SCMW-B450A/B/D
General Description
Using the IMS Server
4. Perform an echo test. Speak a word into the microphone of the mobile and check
that the word is returned to the loudspeaker of the mobile.
For further tests, you can create additional virtual subscriber profiles with a different
behavior or a different media endpoint. Enter a different public user ID for each
profile. To call a specific virtual subscriber, call its public user ID.
Setting up a mobile-terminating voice over IMS call
Initial situation: The mobile has registered to the IMS server. The GUI shows the "IMS"
tab of the "Data Application Control" dialog.
1. Press the "Virtual Subscriber" hotkey.
A dialog box opens.
2. Configure the "Virtual 1" tab as follows:
a) Set the "Signaling Type" compatible to your mobile (call setup with or without
SIP preconditions).
b) Configure the audio codec settings compatible to your mobile.
c) For video calls, configure the video codec settings compatible to your mobile.
d) For "Media Endpoint", we use the default value "Loopback".
3. Press the
button.
The mobile-terminating call (MTC) settings of the virtual subscriber are displayed.
Most settings are a copy of the already configured virtual subscriber settings. The
virtual subscriber profile is kept unmodified, even if you change the copied settings
here.
4. Configure the following call settings:
a) Select the "Destination" to be called.
b) Select the "Call Type".
27
R&SCMW-B450A/B/D
General Description
Using the IMS Server
7. Perform an echo test. Speak a word into the microphone of the mobile and check
that the word is returned to the loudspeaker of the mobile.
For further tests, you can create additional virtual subscriber profiles with different
call settings.
Upgrading an audio call to a video call
Initial situation: You have set up an audio call. The GUI shows the "IMS" tab of the
"Data Application Control" dialog.
1. Select the audio call entry in the "Events" area of the main view. The relevant entry
indicates the event and the status "Established".
2. Press the "Update Call" softkey.
A dialog box opens.
3. Change the "Call Type" to "Video".
4. Set the "Video Codec" compatible to your mobile.
5. Press the "Update" button.
6. Check the "Events" area of the main view. If the mobile accepts the modification,
the event changes to .
You can check the established video call also at your mobile.
Sending a short message (SMS) to the mobile
Initial situation: The mobile has registered to the IMS server. The GUI shows the "IMS"
tab of the "Data Application Control" dialog.
1. Press the "Virtual Subscriber" hotkey.
A dialog box opens.
2. Press the
button.
The mobile-terminating short message settings of the virtual subscriber are displayed.
3. Configure all settings:
a) Select the "Destination" to which the message shall be sent.
b) Select the "SMS Type".
28
R&SCMW-B450A/B/D
General Description
Using the IMS Server
and the
29
R&SCMW-B450A/B/D
General Description
Using the ePDG Service for WLAN Offload
30
R&SCMW-B450A/B/D
General Description
Using the eMBMS Service
31
R&SCMW-B450A/B/D
General Description
Using the eMBMS Service
The mini service layer of the DAU provides all eMBMS services required for eMBMS
tests. It supports for example the following features:
Unicast services:
Bootstrap function
Associated delivery procedures, for example file repair function and reception
reports
Multicast services
The eMBMS mini service layer does not provide a graphical user interface. It cannot be
configured directly via the DAU software.
Instead, it is configured and controlled comfortably via CMWcards or via protocol test
applications. Even the IP replay application is controlled in that way for eMBMS tests.
You do not need to configure it via the DAU software.
The following figure provides a graphical overview.
32
R&SCMW-B450A/B/D
General Description
Using the Hard Disk of the DAU
To change the drive letter, use the hotkey "Network Drive Map" of the "Data Application Control" dialog.
The samba share provides the following directories:
dau_logging:
This folder contains log files for service purposes. They are intended for use by
Rohde & Schwarz only.
It also contains files with encryption keys for IPsec. You can enter these keys in a
network protocol analyzer, in order to analyze IP log files of encrypted connections,
see Chapter 3.11, "Configuring Wireshark for IPsec", on page 36.
dau_tools:
Contains tools which can be installed on the mobile for data testing. The tools are
also available on the web portal of the DAU.
ftp_anon:
Anonymous FTP users have write access to this directory (upload / delete). For the
other directories they have only read access (download).
ip_analysis:
This directory contains csv files created via the "Export DB" function of the "IP
Analysis" application, see "Export DB (hotkey)" on page 103.
33
R&SCMW-B450A/B/D
General Description
Accessing the Built-in Web Server
ip_logging:
This directory contains log files created via the "IP Logging" application, see Chapter 4.2.7, "IP Logging Tab", on page 98. You may delete, copy or rename these
files.
ip_replay:
This directory is used by the "IP Replay" application, see Chapter 4.2.9, "IP Replay
Tab", on page 115. If you want to replay packet capture files, store them in this
directory.
multimedia:
When you add pages to the web portal of the DAU, the related files are stored in
directory multimedia/web_server/user/web_pages/.
rohde-schwarz:
This folder contains internal configuration files and is for use by Rohde & Schwarz
only.
34
R&SCMW-B450A/B/D
General Description
Accessing the Built-in Web Server
You can load the web pages using the "IP address" of the DAU shown in the "IP Config" tab. Type it into your Internet browser: http://<IP_address>, for example,
http://172.22.1.201. If you want to use domain names instead of IP addresses,
please configure and start the DNS server, see Chapter 4.1.3, "DNS Tab",
on page 46.
The built-in web portal on the DAU is based on a wiki solution. It is divided into two
parts:
"Main": This part is predefined by Rohde & Schwarz and provides the following:
"OMA XHTML Tests": set of XHTML tests specified by the Open Mobile Alliance
"DAU Status": overview of the states of the DAU services and the state of the
DAU
"Tools": programs which can be installed on the host behind the mobile for data
testing
For example, you can download the iperf remote configuration program which
is required on the mobile to perform iperf measurements. See also Chapter 3.10, "Configuring Iperf on the Mobile", on page 36.
The tools are also available on the samba share.
"DAU Help": The document you are currently reading. This help is a copy of the
help that is embedded in the "CMW" program.
"User": This part is empty by default. As usual for a wiki, you can add own web
pages to this part and modify them using the built-in editor.
35
R&SCMW-B450A/B/D
General Description
Configuring Wireshark for IPsec
Note: When updating the data testing support package, the "User" pages may be
lost. Back up your files before updating the software. All "User" web files are stored
on the hard disk of the DAU in the directory multimedia/web_server/user/
web_pages/, see Figure 3-6.
During an iperf measurement, the tool at mobile side shows the IP performance of the
downlink, while the DAU shows the IP performance of the uplink.
36
R&SCMW-B450A/B/D
General Description
Configuring Wireshark for IPsec
Typically, you use the "IP logging" application of the DAU to create log files of a connection. And you use Wireshark to analyze the created pcap files.
If the connection is encrypted, you must provide the used encryption keys to Wireshark. For this purpose, the DAU stores the used encryption keys on the samba share.
Encrypted ePDG connections
To provide encryption keys for ePDG connections to Wireshark, proceed as follows.
1. Establish the ePDG connections.
2. Access the samba share of the DAU, folder dau_logging\logs\DAU.
3. Open the file epdg-esp_sa.
The file contains a list of encryption keys for the ESP protocol. It also indicates the
path of the file esp_sa in the Wireshark installation.
4. Copy the encryption keys to the file esp_sa.
5. Open the file epdg-ikev2_decryption_table.
The file contains a list of encryption keys for the IKEv2 protocol. It also indicates
the path of the file ikev2_decryption_table in the Wireshark installation.
6. Copy the encryption keys to the file ikev2_decryption_table.
7. (Re-)start Wireshark.
You can now use Wireshark to analyze log files of the ePDG connections.
For each new ePDG connection, new keys are generated. So you must repeat the
procedure for new connections.
Encrypted IMS connections
IMS connections can also be encrypted via IPsec. In that case, the same keys are
used for all connections - as long as you do not modify the related authentication settings. So you need to provide the encryption keys to Wireshark only once.
As for ePDG connections, the encryption keys are stored on the samba share in the
folder dau_logging\logs\DAU.
Copy the keys from the file ims-esp_sa to the file esp_sa of the Wireshark installation.
37
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
4 GUI Reference
This section provides detailed reference information on the Graphical User Interface
(GUI) of the Data Application Unit (DAU).
The GUI of the DAU provides two main dialogs:
The "Data Application Control" dialog allows you to configure and control global
DAU IP services (e.g. FTP, HTTP) and to configure the IP network settings of the
DAU.
It can be opened from the "Setup" dialog of the instrument and from the "Data
Application Measurements" dialog.
The "Data Application Measurements" dialog allows you to configure and control IP
services dedicated to a specific IP connection (e.g. IPerf, network impairments).
The DAU measurements must be enabled in the "Measurement Controller" dialog
and can then be accessed via the task bar.
Overview Tab.......................................................................................................... 39
IP Config Tab.......................................................................................................... 40
DNS Tab................................................................................................................. 46
FTP Tab.................................................................................................................. 50
HTTP Tab................................................................................................................52
IMS Tab...................................................................................................................53
ePDG Tab............................................................................................................... 76
Common Softkeys, Hotkeys and Parameters......................................................... 85
38
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
39
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
4.1.2.1
Displayed Information............................................................................................. 40
General Configuration.............................................................................................42
IPv4 Configuration...................................................................................................42
IPv6 Configuration...................................................................................................44
Displayed Information
The "IP Config" tab displays the current IP configuration of the DAU.
40
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
The parameter "LAN DAU Status" at the top of the tab indicates the state of the LAN
DAU connector at the rear panel, i.e. whether an active external network is connected
or not. Note that an external network connected to the LAN DAU connector is ignored
by the DAU if a standalone setup is selected in the settings, see "IPv4 Address Configuration" on page 43 and "LAN IPv6 Address Configuration" on page 45.
The current IPv4 configuration and the general IP settings are displayed in the left half
of the tab, the IPv6 configuration in the right half. The values result either directly from
DAU settings described in the following sections or have been assigned dynamically by
a connected external network.
The current DAU IP addresses displayed at the top can be used to address the DAU,
e.g. to access the internal web server or other DAU services.
If the Dynamic Host Configuration Protocol (DHCP) is selected as configuration
method, an additional parameter "DHCPv4 Status" or "DHCPv6 Status" is shown. This
parameter indicates via a colored icon whether the dynamic configuration via DHCP
was successful and the network connection works properly (green icon) or not (yellow
icon).
Related commands
The following commands allow you to query the displayed addresses and prefixes.
For the mobile address/prefix pools there is a separate command for each configuration method. So all pools can be queried, the displayed currently used pools as well as
the currently inactive pools.
Remote command:
SENSe:DATA:CONTrol:IPVFour:CURRent:IPADdress?
SENSe:DATA:CONTrol:IPVFour:CURRent:SMASk?
SENSe:DATA:CONTrol:IPVFour:CURRent:GIP?
41
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
SENSe:DATA:CONTrol:IPVFour:STATic:ADDResses:CATalog?
SENSe:DATA:CONTrol:IPVFour:DHCP:ADDResses:CATalog?
SENSe:DATA:CONTrol:IPVFour:AUTomatic:ADDResses:CATalog?
SENSe:DATA:CONTrol:IPVSix:CURRent:IPADdress?
SENSe:DATA:CONTrol:IPVSix:CURRent:DROuter?
SENSe:DATA:CONTrol:IPVSix:STATic:PREFixes:CATalog?
SENSe:DATA:CONTrol:IPVSix:DHCP:PREFixes:CATalog?
SENSe:DATA:CONTrol:IPVSix:AUTomatic:PREFixes:CATalog?
SENSe:DATA:CONTrol:IPVSix:MANual:ROUTing:CATalog?
4.1.2.2
General Configuration
To modify the general configuration, press the "Config" hotkey. The general settings
are located at the top of the dialog box.
IPv4 Configuration
To modify the IPv4 configuration press the "Config" hotkey and select the tab "IPv4
Address Configuration".
The available settings are described below. For additional information see Chapter 3.2.2, "IP Address Configuration Methods", on page 18.
42
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
43
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
IPv6 Configuration
To modify the IPv6 configuration press the "Config" hotkey and select the tab "IPv6
Address Configuration".
The available settings are described below. For additional information see Chapter 3.2.2, "IP Address Configuration Methods", on page 18.
44
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
45
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
DNS queries from a mobile to a foreign/external DNS server are forwarded by the
DAU like any other IP packets with a foreign destination address. The DAU does
not recognize them as DNS queries.
DNS queries addressed to the DAU are handled by the local DNS server of the
DAU. Optionally, the DAU can forward a query to a foreign DNS server if the local
DNS server database does not contain a matching entry.
46
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
DNS queries of type A, AAAA and SRV are supported. The DAU measurement
"DNS Requests" allows you to monitor all DNS queries addressed to the DAU, see
Chapter 4.2.6, "DNS Requests Tab", on page 96.
The DNS tab displays a summary of the DAU settings related to the DNS service.
47
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
48
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
49
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
CONFigure:DATA:CONTrol:DNS:ASERvices:ADD
CONFigure:DATA:CONTrol:DNS:ASERvices:DELete
SENSe:DATA:CONTrol:DNS:ASERvices:CATalog?
Test Primary Foreign DNS Server (softkey)
The softkey opens a dialog that allows to test whether the primary foreign DNS server
is reachable and whether it returns IP addresses for a specific domain.
The test uses the primary DNS server addresses resulting from section Foreign DNS
server (statically defined addresses or DHCP override values).
To perform a test, enter the domain to be resolved and press the "Start Test" button.
During a test the DAU sends a ping request to the IPv4 and IPv6 addresses of the foreign DNS server to test whether it is reachable. The result is displayed in the dialog in
column "Server available".
If the server is reachable, the DAU sends DNS queries of type A and type AAAA to the
IPv4 and to the IPv6 address of the foreign DNS server, four queries in total. The
results are shown in the dialog. The "A/AAAA Resource Record" columns indicate
whether the server has returned an IP address (yellow dash = no result, red cross =
failure, green checkmark = success).
Remote command:
CONFigure:DATA:CONTrol:DNS:TEST:DOMain
CONFigure:DATA:CONTrol:DNS:TEST:STARt
SENSe:DATA:CONTrol:DNS:TEST:RESults?
DNS Server Control
Start or stop the internal DNS server using the ON | OFF or RESTART | STOP keys.
Alternatively, right-click the "Local DNS Server" softkey.
The softkey shows the current state.
Remote command:
SOURce:DATA:CONTrol:DNS:STATe
50
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
With service type "FTP Server", FTP users can access the samba share of the DAU.
Anonymous FTP users can download data from the samba share and have full access
rights for the subdirectory ftp_anon (delete, download, upload). The access rights of
registered users are configurable per user.
See also Chapter 3.8, "Using the Hard Disk of the DAU", on page 33.
An FTP server runs on the R&S CMW. You can configure it via the
"FTP Server Settings".
"FTP Traffic
Generator"
The R&S CMW acts as a traffic generator which creates dummy data.
You can download dummy data to the mobile or upload files from the
mobile to the instrument. Note that uploaded files are actually not
stored. When running long-term tests this avoids the risk of running
out of data or filling up the internal disk drive of the DAU.
Remote command:
CONFigure:DATA:CONTrol:FTP:STYPe
FTP Server Settings
Configure the FTP server via the checkboxes.
Remote command:
CONFigure:DATA:CONTrol:FTP:ENConnection
CONFigure:DATA:CONTrol:FTP:IPVSix
51
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
CONFigure:DATA:CONTrol:FTP:AUSer
CONFigure:DATA:CONTrol:FTP:DUPLoad
FTP User Accounts FTP Server Settings
Use the "... user account" softkeys to configure the FTP user accounts. For each user,
you can specify the user credentials and access rights for data upload, download and
deletion.
Remote command:
CONFigure:DATA:CONTrol:FTP:USER:ADD
SENSe:DATA:CONTrol:FTP:USER:CATalog?
CONFigure:DATA:CONTrol:FTP:USER:DELete
Service Control
Start or stop the service using the ON | OFF or RESTART | STOP keys. Alternatively,
right-click the "FTP Service" softkey.
The softkey shows the current service state.
Remote command:
SOURce:DATA:CONTrol:FTP:STATe
52
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
If an external IMS network is used instead of the internal IMS server, only the address
of the external P-CSCF is configured at the DAU. In that case, IMS services are transparent to the DAU. Besides the P-CSCF address, the DAU has no information about
the IMS network. It does not even know whether the mobile has registered or not.
The DAU sends the P-CSCF address to the mobile via a signaling message, for example via an ACTIVATE PDP CONTEXT ACCEPT message.
53
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
While usage of the internal IMS server requires option R&S CMW-KAA20, usage of an
external IMS server is possible without this option.
The main view areas, the softkeys and the IMS server settings are described in detail
in the following sections.
4.1.6.1
54
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
CONFigure:DATA:CONTrol:IMS2:UPDate:CALL:ID
CONFigure:DATA:CONTrol:IMS2:UPDate:AMR:TYPE
CONFigure:DATA:CONTrol:IMS2:UPDate:AMR:ALIGnment
CONFigure:DATA:CONTrol:IMS2:UPDate:AMR:CODec<CodecIdx>:ENABle
CONFigure:DATA:CONTrol:IMS2:UPDate:VIDeo:CODec
CONFigure:DATA:CONTrol:IMS2:UPDate:VIDeo:ATTRibutes
CONFigure:DATA:CONTrol:IMS2:UPDate:CALL:TYPE
CONFigure:DATA:CONTrol:IMS2:UPDate:PERForm
Release Call (softkey)
This softkey is active if at least one call is established.
The softkey opens a dialog box where you can select the calls to be released.
Remote command:
SENSe:DATA:CONTrol:IMS2:RELease:LIST?
CONFigure:DATA:CONTrol:IMS2:RELease:CALL:ID
Deregister Mobile (softkey)
This softkey is active if at least one mobile has registered.
The softkey opens a dialog box where you can select the mobiles to be deregistered.
Remote command:
CONFigure:DATA:CONTrol:IMS2:MOBile<UE>:DERegister
4.1.6.2
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:
55
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
SENSe:DATA:CONTrol:IMS2:GINFo?
4.1.6.3
Event Log
A new line is added to the top of the "Events" area whenever a new call is set up or a
short message is sent or received.
When a call state changes, the corresponding line is updated.
To clear the area, switch the IMS server off and on again. To view details for a call or a
message, select the line and check the lower part of the main view, see Chapter 4.1.6.4, "Event Details", on page 56.
Entries
Each line in the "Events" area provides the following information:
Timestamp: Time when the current status was reached.
Source: Calling party / message sender
Destination: Called party / message recipient
"VSn": Virtual subscriber number n
"Sn": Subscriber number n
Event: Indicates the type of the event.
Event Details
The lower part of the main view shows detailed information for the currently selected
entry of the "Events" area.
56
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
For a call, the information covers the entire history from the call setup to the current
state. Each status change is listed with its timestamp. Important call settings are also
listed.
The ID shown at the top is an automatically generated unique ID, identifying the event
in the DAU.
For a short message, important message properties and the message text are listed.
57
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
The threshold is fixed and equals 1300 characters per SIP message.
For shorter SIP messages, UDP is used. For longer SIP messages,
TCP is used.
"TCP Only"
"UDP Only"
"Custom"
Remote command:
CONFigure:DATA:CONTrol:IMS2:TRANsport:SELection
CONFigure:DATA:CONTrol:IMS2:THReshold:VALue
P-CSCF IPv4/IPv6 Address
Configures the IPv4 and IPv6 address of an external P-CSCF.
Remote command:
CONFigure:DATA:CONTrol:IMS2:EXTern:PCSCf:ADDRess:IPVFour
CONFigure:DATA:CONTrol:IMS2:EXTern:PCSCf:ADDRess:IPVSix
4.1.6.6
P-CSCF Settings
Press the "P-CSCF" hotkey to open the "P-CSCF Configuration" dialog box.
58
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
A list of all P-CSCFs is sent to the mobile. The mobile selects a P-CSCF from the list
for registration.
A possible use case is to configure P-CSCF 1 and 2 so that they reject the registration
and P-CSCF 3 and 4 so that they accept the registration. Then check whether the
mobile retries registration with another P-CSCF.
The settings are explained in the following.
Add / Delete Tab........................................................................................................... 59
IP Address.....................................................................................................................59
Behavior........................................................................................................................ 60
Failure........................................................................................................................... 60
Registration................................................................................................................... 60
Subscription.................................................................................................................. 60
OK (button)....................................................................................................................60
Add / Delete Tab
creates a new tab / P-CSCF. The maximum number of tabs is ten.
deletes the currently selected tab. Tab 1 and 2 cannot be deleted.
Remote command:
CONFigure:DATA:CONTrol:IMS2:PCSCf:ADD
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:DELete
SENSe:DATA:CONTrol:IMS2:PCSCf:CATalog?
IP Address
Defines the IP address of the P-CSCF. You can specify an IPv4 or an IPv6 address.
Assign a different address to each profile.
59
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
The addresses of profile 1 and 2 are fixed. Profile 1 uses the IPv4 address of the DAU,
profile 2 the IPv6 address.
Remote command:
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:IPADdress
Behavior
Defines the behavior of the P-CSCF when it receives a SIP message from the mobile.
"Normal"
"Failure"
Remote command:
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:BEHaviour
Failure
Selects a failure code to be returned to the mobile for "Behavior" = "Failure".
Some failure messages support the header field "Retry After". It is filled with the configured time.
Remote command:
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:FAILurecode
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:RETRyafter
Registration
Defines a minimum, maximum and default value for the registration expiration time
(duration of the registration).
The values are used as follows:
If the mobile does not include an expiration interval in its REGISTER message, the
configured "Default" value is used as expiration time for the registration.
If the mobile suggests an expiration interval in its REGISTER message:
If the suggested value is between the configured "Min" and "Max" value, the
suggested value is used as expiration time.
If the suggested value is outside of the configured "Min" / "Max" range, the registration is rejected.
Remote command:
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:REGexp
Subscription
Defines a minimum, maximum and default value for the subscription expiration time.
The logic is the same as for "Registration", with SUBSCRIBE messages instead of
REGISTER messages.
Remote command:
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:SUBexp
OK (button)
When you press the OK button, the internal list of P-CSCF profiles is updated according to your changes.
For remote control, this action must be explicitly triggered via a command.
60
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
CONFigure:DATA:CONTrol:IMS2:PCSCf:CREate
4.1.6.7
Subscriber Settings
Press the "Subscriber" hotkey to open the "Subscribers Configuration" dialog box.
It configures profiles for tested mobiles.
You can create up to 5 subscriber profiles with different private user IDs and properties. Each profile is displayed on a separate tab. Profile 1 is always available.
A profile is selected automatically when a SIP message from the mobile is received.
The user ID included in the SIP message is compared to the user IDs in the profiles.
Depending on the message type, the mobile sends a public user ID or a private user
ID. A profile contains one private user ID and up to ten public user IDs.
If you have several mobiles with the same test SIM card, you can use the same subscriber profile for all these mobiles.
The settings are explained in the following.
Add / Delete Tab........................................................................................................... 62
Private User ID..............................................................................................................62
Authentication............................................................................................................... 62
Key Generation Algorithm............................................................................................. 62
Key................................................................................................................................ 63
61
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
AMF...............................................................................................................................63
OPc............................................................................................................................... 63
RES Length...................................................................................................................63
IPSec.............................................................................................................................63
Integrity Algorithm......................................................................................................... 63
Encryption Algorithm..................................................................................................... 64
Public User IDs............................................................................................................. 64
OK (button)....................................................................................................................64
Add / Delete Tab
creates a new tab / subscriber. The maximum number of tabs is five.
deletes the currently selected tab. Tab 1 cannot be deleted.
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber:ADD
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:DELete
SENSe:DATA:CONTrol:IMS2:SUBScriber:CATalog?
Private User ID
Specifies the private User ID as stored on the ISIM or in the mobile.
If you are not sure which ID is used by your mobile, you can analyze SIP register messages sent by your mobile. The private user ID is contained in the header as username="...".
If the private user ID of the mobile is not assigned to any subscriber profile, authentication will fail.
Each subscriber profile must have a different private user ID.
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:PRIVateid
Authentication
Specifies whether authentication is performed during the registration procedure and
selects the authentication and key agreement (AKA) version to be used (see RFC
3310 and RFC 4169).
If authentication is enabled, the settings in section "Authentication Data" must be compatible to the mobile. And the authentication and key agreement version must be supported by the mobile. Otherwise registration will fail.
Authentication may require a test ISIM. An appropriate ISIM can be obtained from
Rohde & Schwarz (R&S CMW-Z04, stock no. 1207.9901.02). The default settings are
compatible to this ISIM.
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:SCHeme
Key Generation Algorithm
Specifies which algorithm set is used by the ISIM: MILENAGE algorithms (see 3GPP
TS 35.205) or XOR algorithms.
62
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:ALGorithm
Key
The authentication key K is used for the authentication procedure (including a possible
integrity check). The value is entered as 32-digit hexadecimal number.
The key K must be equal to the value stored on the test ISIM or the mobile. Otherwise
authentication fails.
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:KEY
AMF
Specifies the Authentication Management Field (AMF) to be used for the authentication
procedure. The value is entered as 4-digit hexadecimal number.
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:AMF
OPc
The key OPc is used for authentication and integrity check procedures with the MILENAGE algorithm set. If you use this algorithm set, specify the OPc used by the ISIM.
The value is entered as 32-digit hexadecimal number.
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:OPC
RES Length
Specifies the length of the authentication response in bits. The calculated response is
truncated to the specified length before it is sent to the mobile.
Some mobiles require a specific response length.
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:RESLength
IPSec
Specifies whether the IMS server supports IP security mechanisms.
If IPsec is supported by the IMS server but not by the mobile, the session is not rejected. It is established without IPsec.
To use Wireshark for connections with IPsec, see Chapter 3.11, "Configuring Wireshark for IPsec", on page 36.
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ENABle
Integrity Algorithm
Selects an algorithm for integrity protection via IPsec. The supported algorithms are
HMAC-MD5-96 (see RFC 2403) and HMAC-SHA-1-96 (see RFC 2404).
Configure this setting compatible to your mobile.
63
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ALGorithm:
INTegrity
Encryption Algorithm
Selects an algorithm for encryption via IPsec. The supported algorithms are DESEDE3-CBC (see RFC 2451) and AES-CBC (see RFC 3602). NO_CIPH means no
encryption/ciphering.
Configure this setting compatible to your mobile.
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ALGorithm:
ENCRyption
Public User IDs
If the mobile sends a public user ID that is not assigned to any subscriber profile, the
first profile is used. So for tests with this profile, you do not need to enter public user
IDs.
To use another profile, enter all public user IDs stored on the ISIM or in the mobile. Do
not assign the same user ID to several profiles.
A 4-digit number is automatically assigned to each profile.
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:PUBLicuserid<Index>
OK (button)
When you press the OK button, the internal list of subscriber profiles is updated
according to your changes.
For remote control, this action must be explicitly triggered via a command.
Remote command:
CONFigure:DATA:CONTrol:IMS2:SUBScriber:CREate
4.1.6.8
64
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
65
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
IP.....................................................................................................................70
RTP Port......................................................................................................... 70
Cmd Port.........................................................................................................71
AMR Alignment............................................................................................... 71
Audioboard....................................................................................................................71
Enable DTX in DL........................................................................................... 71
Force Mode.....................................................................................................71
(button)................................................................................................................... 71
(button)................................................................................................................... 72
OK (button)....................................................................................................................72
Add / Delete Tab
creates a new tab / virtual subscriber. The maximum number of tabs is twenty.
deletes the currently selected tab. Tab 1 cannot be deleted.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub:ADD
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:DELete
SENSe:DATA:CONTrol:IMS2:VIRTualsub:CATalog?
Public User ID
For incoming mobile-originating calls, the called virtual subscriber is selected via its
public user ID.
By default, the first virtual subscriber profile has a wildcard "*" as ID. Any incoming
calls, for which no profile with a matching public user ID is found, are routed to this virtual subscriber. If you want to use this mechanism, do not modify the ID.
For additional virtual subscribers, define a different public user ID for each profile.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:ID
Behavior
Defines how the virtual subscriber reacts to a call from the tested mobile.
"Answer"
"NoAnswer"
"Declined"
"Busy Here"
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:BEHaviour
Signaling Type
Specifies whether a voice call session is established with or without quality of service
preconditions. For a call with preconditions, a certain quality of service is ensured by
reserving network resources before alerting the called user. SIP preconditions are
defined in RFC 3312 and RFC 4032. See also 3GPP TS 24.229.
"Preconditions" SIP signaling as for a call with preconditions
"Without Preconditions"
66
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
"Simple"
"Require
100rel"
"Require Precondition"
"Without Preconditions,
With 183"
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:SIGNalingtyp
Dedicated Bearer
Enables the automatic setup of a dedicated bearer, if a VoIMS connection is established. If the checkbox is disabled, the IMS server does not set up dedicated bearers
for calls to/from this virtual subscriber.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:BEARer
Audio
This node configures the codec to be used for audio calls.
Codec Audio
Selects the voice codec type to be used.
To use the EVS codec with the audio board, option R&S CMW-KS104 is required.
"AMR"
"AMR-WB"
"EVS"
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AMR:TYPE
AMR Audio
This node configures the wideband and narrowband AMR codec.
67
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Only the full payload is octet aligned. Fewer padding bits are needed.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AMR:ALIGnment
Codec Rates AMR Audio
Selects the supported AMR codec rates. For the wideband AMR, there are 9 codec
rates (index 0 to 8). For the narrowband AMR, there are 8 codec rates (index 0 to 7).
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AMR:CODec<CodecIdx>:
ENABle
EVS Audio
This node configures the EVS codec.
The same settings apply to the downlink (sending) and the uplink
(receiving). A node "Common" is displayed for configuration of the
settings.
"Send/
Receive"
There are separate settings for the downlink and the uplink. The
nodes "Send (DL)" and "Receive (UL)" are displayed for configuration
of the settings.
68
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
"Header Full
Only"
"Not Present"
The SDP parameter is not present (no value). This must have the
same effect as the value 0.
"Enable"
"Not Present"
The SDP parameter is not present (no value). This must have the
same effect as the value 1.
"Enable"
"Not Present"
The SDP parameter is not present (no value). This must have the
same effect as the value 1.
"Enable"
"Present All"
69
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
"Not Present"
The SDP parameter is not present (no value). This must have the
same effect as the value 0.
Video
Selects the video codec to be used for video calls to the tested mobile.
You can also specify codec attributes.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:VIDeo:CODec
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:VIDeo:ATTRibutes
Media Endpoint
Configures the routing of an audio signal or video signal received from the mobile. The
setting applies to incoming and outgoing calls.
"Loopback"
The signal from the mobile is routed back immediately. A word spoken into the microphone of the mobile is returned to the loudspeaker
of the mobile.
"Forward"
The RTP packets from the mobile are forwarded to an external media
endpoint from Rohde & Schwarz. The packets returned by the media
endpoint are forwarded to the mobile. This method can be used to
implement an alternative loopback mechanism.
The RTCP packets are not forwarded. They are looped back by the
IMS server.
Packet forwarding is not supported for EVS audio codecs.
"Audioboard"
The signal from the mobile is routed to the speech decoder of the
audio board. The signal returned by the speech encoder of the audio
board is forwarded to the mobile.
Select this value to perform audio measurements for voice over IMS.
The audio board is provided by R&S CMW-B400B, the speech codec
by R&S CMW-B405A.
To use the EVS codec with the audio board, option R&S CMWKS104 is required.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MEDiaendpoin
Forward
Specifies settings for Media Endpoint = "Forward":
IP Forward
IPv4 or IPv6 address of the media endpoint
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:FORWard
RTP Port Forward
Port for RTP packet forwarding
70
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:FORWard
Cmd Port Forward
Port for the command interface between the DAU and the Rohde & Schwarz media
endpoint.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:FORWard
AMR Alignment Forward
Enter the AMR alignment mode used by the media endpoint.
You can use different modes towards the mobile and towards the media endpoint. See
also "AMR Alignment Mode" on page 68.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:FORWard
Audioboard
Specifies settings for Media Endpoint = "Audioboard":
Enable DTX in DL Audioboard
Enables voice activity detection and the generation of comfort noise parameters during
silence periods. The parameters are sent to the mobile in silence indicator frames.
This setting is not configurable for the EVS audio codec.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AUDioboard
Force Mode Audioboard
Selects the codec rate or bit rate used by the speech codec of the audio board. The
offered values depend on the setting "Codec" on page 67.
Typically, audio tests are performed with a specific rate. Specify this rate here and
ensure that it is enabled in the codec settings.
"SDP"
All rates are allowed. The rate requested by the mobile is used. If it
sends several rates, the highest one is used.
"xxx kbit/s"
"Primary xxx
kbps"
"AMR-WB IO
xxx kbps"
"Follow CMR"
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AUDioboard
(button)
Accesses the view for mobile-terminating calls, see Chapter 4.1.6.9, "Mobile-Terminating Calls", on page 72.
71
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
(button)
Accesses the view for mobile-terminating short messages, see Chapter 4.1.6.10,
"Short Messages", on page 75.
OK (button)
When you press the OK button, the internal list of virtual subscriber profiles is updated
according to your changes.
For remote control, this action must be explicitly triggered via a command.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub:CREate
4.1.6.9
Mobile-Terminating Calls
Mobile-terminating voice over IMS calls are configured and initiated via the "Virtual
Subscribers Configuration" dialog box.
Press the "Virtual Subscriber" hotkey to open the dialog box. In the dialog box, press
to access the view for mobile-terminating calls. It is shown in the followthe button
ing figure.
Most call settings are also available as virtual subscriber settings, for example the signaling type and all codec settings. If you modify these virtual subscriber settings, the
72
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
corresponding call settings are also modified automatically. Vice versa, if you modify
call settings, this does not affect virtual subscriber settings.
Thus you can use your created virtual subscribers as templates for the call settings
and additionally fine-tune the call settings.
To initiate a call, proceed as follows:
1. Select a virtual subscriber tab at the top.
The related call settings are displayed.
2. Modify the call settings as desired.
3. Press the "Call" button.
For more detailed instructions, see "Setting up a mobile-terminating voice over IMS
call" on page 27.
The view contents are described in the following.
(button)................................................................................................73
(button)................................................................................................................... 73
(button)................................................................................................................... 73
Destination.................................................................................................................... 73
Call Type....................................................................................................................... 74
Signaling Type.............................................................................................................. 74
Audio Codec..................................................................................................................74
Video Codec, Video Attributes...................................................................................... 74
Dedicated Bearer.......................................................................................................... 74
AMR Settings................................................................................................................ 74
EVS Settings................................................................................................................. 74
Call (button)...................................................................................................................74
(button)
Accesses the virtual subscriber view of the dialog box, see Chapter 4.1.6.8, "Virtual
Subscriber Settings", on page 64.
(button)
Accesses this view (no effect when view is already displayed).
(button)
Accesses the view for mobile-terminating short messages, see Chapter 4.1.6.10,
"Short Messages", on page 75.
Destination
Selects the destination to be called. The list is filled during registration.
Each destination has the following format: <Contact ID>[<Public User ID>], for example "1001[tel:5551001]".
The <Contact ID> is a unique four-digit number, assigned automatically during registration. The first digit equals the number of the subscriber profile. The remaining three
digits are a counter. Example: The first registration for subscriber profile 1 gets <Contact ID> = 1001.
73
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
The <Public User ID> equals tel:555<Contact ID>. During registration, this public user
ID is registered in addition to the public user IDs configured for the used subscriber
profile.
Remote command:
SENSe:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:DESTination:LIST?
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:DESTination
Call Type
Selects the type of call to be set up: audio call or video call.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:TYPE
Signaling Type
Signaling type as in the virtual subscriber profile, see "Signaling Type" on page 66.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:SIGType
Audio Codec
Audio codec selection as in the virtual subscriber profile, see "Codec" on page 67.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:TYPE
Video Codec, Video Attributes
Video codec settings as in the virtual subscriber profile, see "Video" on page 70.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:VIDeo:CODec
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:VIDeo:
ATTRibutes
Dedicated Bearer
Dedicated bearer setting as in the virtual subscriber profile, see "Dedicated Bearer"
on page 67.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:BEARer
AMR Settings
AMR codec settings as in the virtual subscriber profile, see "AMR" on page 67.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:ALIGnment
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:
CODec<CodecIdx>:ENABle
EVS Settings
EVS codec settings as in the virtual subscriber profile, see "EVS" on page 68.
Call (button)
The "Call" button initiates a voice over IMS call to the mobile.
74
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
The dialog box is closed automatically. You can check the call state in the "Events"
area of the main view.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:CALL
4.1.6.10
Short Messages
Incoming mobile-originating short messages sent from the mobile to a virtual subscriber are displayed in the main view, see Chapter 4.1.6.4, "Event Details",
on page 56.
Mobile-terminating short messages to be sent to the mobile are configured and initiated via the "Virtual Subscribers Configuration" dialog box. This dialog box is described
in the following.
Press the "Virtual Subscriber" hotkey to open the dialog box. In the dialog box, press
the button
to access the view for mobile-terminating short messages. It is shown in
the following figure.
(button)................................................................................................76
(button)................................................................................................................... 76
(button)................................................................................................................... 76
Destination.................................................................................................................... 76
75
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
SMS Type..................................................................................................................... 76
Text............................................................................................................................... 76
Send (button)................................................................................................................ 76
(button)
Accesses the virtual subscriber view of the dialog box, see Chapter 4.1.6.8, "Virtual
Subscriber Settings", on page 64.
(button)
Accesses the view for mobile-terminating calls, see Chapter 4.1.6.9, "Mobile-Terminating Calls", on page 72.
(button)
Accesses this view (no effect when view is already displayed).
Destination
Selects the destination to which the short message shall be sent.
The list of destinations is the same as for mobile terminating calls, see "Destination"
on page 73.
Remote command:
SENSe:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:DESTination:LIST?
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:DESTination
SMS Type
Selects the type of the short message to be sent to the mobile. You can send short
messages using 3GPP or 3GPP2 signaling procedures. For 3GPP2, there is a variant
with delivery acknowledgment and one without acknowledgment.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:TYPE
Text
Specifies the text of the short message to be sent to the mobile.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:TEXT
Send (button)
Sends a short message with the specified settings to the mobile.
The dialog box is closed automatically. You can check the message transfer in the
"Events" area of the main view and at the mobile.
Remote command:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:SEND
76
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
In a 3GPP core network, the ePDG is the gateway to an untrusted non-3GPP access
technology, for example to a WLAN gateway. The main role of the ePDG is to provide
security mechanisms. For a secure connection via the untrusted WLAN, an IPsec tunnel is established between the DUT and the ePDG.
The ePDG is for example used for WLAN traffic offload tests. See also Chapter 3.6,
"Using the ePDG Service for WLAN Offload", on page 30.
The ePDG tab shows an event log and information about established IPsec tunnels
between the ePDG and DUTs.
4.1.7.1
77
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Service Control
Start or stop the service using the ON | OFF or RESTART | STOP keys. Alternatively,
right-click the "ePDG Service" softkey.
The softkey shows the current service state.
4.1.7.2
If there are established connections for several DUTs (IMSIs), a separate node is displayed for each IMSI.
Connection information
There is one row per connection, providing the following information:
Connection ID, displayed in square brackets. The ID is for example used in the
event log when events related to this connection occur.
Access point name (APN)
DUT IPv4 and IPv6 address
78
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
SENSe:DATA:CONTrol:EPDG:CONNections:IMSI?
4.1.7.4
4.1.7.5
ePDG IP Configuration
Configures the IPv4 and IPv6 address of the ePDG.
Remote command:
CONFigure:DATA:CONTrol:EPDG:ADDRess:IPVFour
CONFigure:DATA:CONTrol:EPDG:ADDRess:IPVSix
ePDG ID Configuration
Configures the type and the value of the ePDG identification.
The ePDG identifies itself according to these settings in messages to the DUT.
The ID types are specified in RFC 5996. The following types are supported:
"ID_IPv4_ADDR": four-octet IPv4 address
"ID_FQDN": fully-qualified domain name string
"ID_RFC822_ADDR": fully-qualified RFC 822 email address string
"ID_IPV6_ADDR": sixteen-octet IPv6 address
"ID_KEY_ID": opaque octet stream
79
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
CONFigure:DATA:CONTrol:EPDG:ID:TYPE
CONFigure:DATA:CONTrol:EPDG:ID:VALue
4.1.7.6
IKE Settings
This section is related to the IPsec protocol internet key exchange version 2 (IKEv2). It
is used for authentication before setup of an IPsec tunnel.
All enabled values are supported by the ePDG. The value to be used will be negotiated
with the DUT.
In each section, at least one value supported by your DUT must be enabled. Otherwise, authentication will fail.
To use Wireshark for connections with IPsec, see Chapter 3.11, "Configuring Wireshark for IPsec", on page 36.
The listed values are specified in RFC 5996. That RFC references other RFCs indicated in the following in brackets.
Encryption..................................................................................................................... 80
PRF............................................................................................................................... 80
Integrity......................................................................................................................... 81
Diffie Hellman................................................................................................................81
Encryption
Selects the encryption algorithms supported by the ePDG. In the current software version, only one value is available: "ENCR_AES_CBC" (see RFC 3602).
Remote command:
CONFigure:DATA:CONTrol:EPDG:IKE:ENCRyption
PRF
Selects the pseudorandom functions supported by the ePDG.
Available values:
"PRF_HMAC_MD5" (RFC 2104)
80
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
CONFigure:DATA:CONTrol:EPDG:IKE:PRF
Integrity
Selects the integrity protection algorithms supported by the ePDG.
Available values:
"AUTH_HMAC_SHA1_96" (RFC 2404)
"AUTH_HMAC_MD5_96" (RFC 2403)
"AUTH_AES_XCBC_96" (RFC 3566)
Remote command:
CONFigure:DATA:CONTrol:EPDG:IKE:INTegrity
Diffie Hellman
Selects the Diffie-Hellman groups supported by the ePDG.
Available values (specified in RFC 5996 and RFC 6989):
"DH_GROUP_1": 768-bit MODP
"DH_GROUP_2": 1024-bit MODP
"DH_GROUP_5": 1536-bit MODP
"DH_GROUP_14": 2048-bit MODP
Remote command:
CONFigure:DATA:CONTrol:EPDG:IKE:DHGRoup
4.1.7.7
ESP Settings
This section is related to the IPsec protocol encapsulating security payload (ESP). It is
used for encryption of data for transfer via an IPsec tunnel.
All enabled values are supported by the ePDG. The value to be used will be negotiated
with the DUT.
In each section, at least one value supported by your DUT must be enabled.
Encryption..................................................................................................................... 81
Integrity......................................................................................................................... 82
Encryption
Selects the encryption algorithms supported by the ePDG.
The available values are the same as for IKEv2, see "Encryption" on page 80.
81
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
CONFigure:DATA:CONTrol:EPDG:ESP:ENCRyption
Integrity
Selects the integrity protection algorithms supported by the ePDG.
The available values are the same as for IKEv2, see "Integrity" on page 81.
Remote command:
CONFigure:DATA:CONTrol:EPDG:ESP:INTegrity
4.1.7.8
IPv4 Type...................................................................................................................... 82
IPv6 Type...................................................................................................................... 82
IPv6 Address Length.....................................................................................................82
IPv4 Type
Attribute type field of the P_CSCF_IP4_ADDRESS configuration attribute.
Remote command:
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVFour:TYPE
IPv6 Type
Attribute type field of the P_CSCF_IP6_ADDRESS configuration attribute.
Remote command:
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVSix:TYPE
IPv6 Address Length
Length field of the P_CSCF_IP6_ADDRESS configuration attribute.
Remote command:
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVSix:ADDRess:LENGth
4.1.7.9
Authentication Settings
The settings in this section are related to the authentication procedure. They must be
compatible to the SIM of the DUT. Otherwise, authentication will fail.
82
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
IMSI...............................................................................................................................83
Authentication Algorithm............................................................................................... 83
Secret Key.....................................................................................................................83
RAND............................................................................................................................ 83
AMF...............................................................................................................................83
Key Type....................................................................................................................... 83
Authentication OPc........................................................................................................ 84
IMSI
15-digit international mobile subscriber identity (IMSI), must match the IMSI on the SIM
Remote command:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:IMSI
Authentication Algorithm
Key generation algorithm set used by the SIM: MILENAGE algorithms (see 3GPP TS
35.205) or XOR algorithms
Remote command:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:ALGorithm
Secret Key
Authentication key K as 32-digit hexadecimal number, as stored on the SIM or the DUT
Remote command:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:KEY
RAND
Random number to be used
Remote command:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:RAND
AMF
Authentication management field as 4-digit hexadecimal number
Remote command:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:AMF
Key Type
Key type to be used with the MILENAGE algorithm set (fixed value)
83
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Remote command:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:KEY:TYPE
Authentication OPc
OPc value used by the SIM, as 32-digit hexadecimal number
Only relevant and configurable if the MILENAGE algorithm set is used, see "Authentication Algorithm" on page 83
Remote command:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:OPC
4.1.7.10
Enable
Enables dead peer detection.
Remote command:
CONFigure:DATA:CONTrol:EPDG:DPD:ENABle
Interval, Timeout
If the ePDG receives no packets via an established tunnel within the configured "Interval", the ePDG sends a message to the DUT.
If the ePDG receives no answer to this message within the configured "Timeout", it
releases the IPsec tunnel.
Remote command:
CONFigure:DATA:CONTrol:EPDG:DPD:INTerval
CONFigure:DATA:CONTrol:EPDG:DPD:TIMeout
4.1.7.11
Certificate Settings
The following settings are related to SSL certificates.
If you want to use SSL without certificates, disable the checkbox.
If you want to use an SSL certificate:
Store the server certificate file and the key file with the private key of the server on
the samba share, in the directory security\certificates\epdg.
Only pem files are supported.
84
R&SCMW-B450A/B/D
GUI Reference
Data Application Control Dialog
Ensure that the ePDG ID used in the server certificate matches the configured
ePDG ID, see "ePDG ID Configuration" on page 79.
Select the key file and the certificate file via the following parameters. The list
offers only pem files stored in the correct directory on the samba share.
Enable........................................................................................................................... 85
Server Key, Server Certificate.......................................................................................85
Enable
Enables the usage of certificates for SSL.
Remote command:
CONFigure:DATA:CONTrol:EPDG:CERTificate:ENABle
Server Key, Server Certificate
Select the key file and the certificate file. Only pem files are listed.
Remote command:
CONFigure:DATA:CONTrol:EPDG:CERTificate:KEY
CONFigure:DATA:CONTrol:EPDG:CERTificate:CERTificate
85
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Remote command:
SOURce:DATA:CONTrol:STATe
Select Applic (hotkey)
Selects the tab to be displayed in the "Data Application Control" dialog.
Network Drive map (hotkey)
The DAU has a hard disk which can be used for data storage. This drive can be
accessed from the Microsoft Windows Explorer.
The hotkey opens a dialog for changing the assigned drive letter.
RAN Selection.........................................................................................................86
Overview Tab.......................................................................................................... 87
Ping Tab..................................................................................................................88
IPerf Tab................................................................................................................. 90
Throughput Tab.......................................................................................................94
DNS Requests Tab................................................................................................. 96
IP Logging Tab........................................................................................................98
IP Analysis Tab..................................................................................................... 101
IP Replay Tab....................................................................................................... 115
Audio Delay Tab....................................................................................................118
Network Impairments............................................................................................ 122
Common Softkeys and Hotkeys............................................................................124
86
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
87
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
88
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Result Diagram............................................................................................................. 89
Average / Minimum / Maximum.....................................................................................89
'No Reply' Count........................................................................................................... 89
Config............................................................................................................................90
Measurement Control....................................................................................................90
Result Diagram
The diagram provides a graphical presentation of the measured ping latency for each
ping request. The X-axis indicates the processed ping requests, with the last processed request labeled 0, the previously processed request labeled -1 and so on.
Remote command:
FETCh:DATA:MEAS<i>:PING?
READ:DATA:MEAS<i>:PING?
Average / Minimum / Maximum
The values below the diagram indicate the average, minimum and maximum of all values in the diagram.
Remote command:
FETCh:DATA:MEAS<i>:PING:OVERall?
'No Reply' Count
Indicates the number of ping requests with no reply. In the result diagram, such
requests are displayed as gaps (ping latency = 0 ms).
The reason for the latest ping request with no reply is indicated below the parameter,
e.g. timeout or no route to host.
89
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Remote command:
FETCh:DATA:MEAS<i>:PING:NRCount?
Config
Configures the properties of the ping command.
"Destination IP": IP address that you want to ping
"Interval": pinging interval
"Timeout": timeout for unanswered ping requests
"Payload": packet size used as probe
"Ping Count": number of echo request packets to be sent
You can change values that are not grayed out even during the measurement, for
example, the "Interval".
Remote command:
CONFigure:DATA:MEAS<i>:PING:DIPaddress
CONFigure:DATA:MEAS<i>:PING:INTerval
CONFigure:DATA:MEAS<i>:PING:TIMeout
CONFigure:DATA:MEAS<i>:PING:PSIZe
CONFigure:DATA:MEAS<i>:PING:PCOunt
Measurement Control
Turn the measurement on or off using the ON | OFF or RESTART | STOP keys. Alternatively, right-click the "Ping" softkey.
The softkey shows the current measurement state. Additional measurement substates
may be retrieved via remote control.
Remote command:
INITiate:DATA:MEAS<i>:PING
STOP:DATA:MEAS<i>:PING
ABORt:DATA:MEAS<i>:PING
FETCh:DATA:MEAS<i>:PING:STATe?
FETCh:DATA:MEAS<i>:PING:STATe:ALL?
90
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Figure 4-37: Role of servers and client instances in the context of IPerf
The "IPerf" tab allows you to configure up to 8 server instances and 8 client instances
at the DAU in parallel. For configuration of IPerf at the mobile side, see Chapter 3.10,
"Configuring Iperf on the Mobile", on page 36.
The main view of the "IPerf" tab shows the first three instances together with the main
parameters. To display all instances, press the softkey "Expand Table".
The diagram below the instances displays the measurement results.
All instances can be fully configured using the "IPerf Config" dialog, which can be
opened via the "Config" hotkey.
91
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
The elements of the main view and of the configuration dialog are described below.
Results.......................................................................................................................... 92
Test Duration.................................................................................................................92
Packet Size................................................................................................................... 92
Server Settings..............................................................................................................93
Client Settings............................................................................................................... 93
Measurement Control....................................................................................................94
Results
The bar graph indicates up to three result bars per instance:
"Uplink": bit rate measured in uplink direction for active server instances
"Downlink": bit rate transmitted in downlink direction for active client instances
"Lost Packets": percentage of packets lost during the measurement, for active
server instances with protocol type UDP
The uplink and downlink bit rates are also indicated in the instance table above the bar
graph. The lost packet percentage is also indicated below the bar graph.
Remote command:
FETCh:DATA:MEAS<i>:IPERf:CLIent?
READ:DATA:MEAS<i>:IPERf:CLIent?
FETCh:DATA:MEAS<i>:IPERf:SERVer?
READ:DATA:MEAS<i>:IPERf:SERVer?
FETCh:DATA:MEAS<i>:IPERf:ALL?
Test Duration
Defines the time the test should last.
Remote command:
CONFigure:DATA:MEAS<i>:IPERf:TDURation
Packet Size
Defines the packet size for IPerf tests (payload bytes), applicable to UDP and TDD.
92
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
The packet size is especially important if you want to use a low UDP bit rate. In order
to reach this bit rate, configure the packet size according to the following rules:
Convert the bit rate to byte/s and divide it by an integer number (divisor n) to derive
the packet size.
Use the smallest possible divisor n, resulting in an integer packet size.
Ensure that the packet size is smaller than or equal to the maximum payload size,
resulting from the configured MTU (MTU minus overhead), see also "Maximum
Transmission Unit (MTU)" on page 42. If necessary, use a larger divisor n.
Example:
MTU = 1500 byte, UDP bit rate = 23 kbit/s = 2875 byte/s
The smallest possible divisor n equals 5. It results in a packet size of 575 byte. This
packet size is smaller than the maximum payload size.
With a packet size of 575 byte, exactly 5 packets are transferred per second, in order
to reach a bit rate of 23 kbit/s (5 * 575 byte/s * 8 bit/byte = 23 kbit/s).
Remote command:
CONFigure:DATA:MEAS<i>:IPERf:PSIZe
Server Settings
Defines the properties of the server instances for uplink direction (DAU receives data
from the mobile):
"Use"
Specifies whether the server instance is used.
"UDP or TCP"
Selects the protocol type to be used.
"Port"
Specifies the LAN DAU port number for the connection. This value must match the
mobile's client port settings.
"Window size"
Specifies the TCP receiving window size (for TCP only)
Remote command:
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:ENABle
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:PROTocol
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:PORT
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:WSIZe
Client Settings
Defines the properties of the client instances for downlink direction (DAU sends data to
the mobile).
"Use"
Specifies whether the client instance is used.
"UDP or TCP"
Selects the protocol type to be used.
"Port"
Specifies the LAN DAU port number for the connection. This value must match the
mobile's server port settings.
"UE IP Address"
Specifies the IP address of the mobile.
"Window size"
93
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Specifies the size of the NACK window (in kByte), for TCP only.
"Parallel Connections"
Specifies the number of parallel connections for the selected port, for TCP only.
"Bit rate"
Specifies the maximum bit rate to be transferred, for UDP only.
If the bit rate is not reached, check the packet size, see "Packet Size" on page 92.
Remote command:
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:ENABle
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PROTocol
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PORT
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:IPADdress
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:WSIZe
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PCONnection
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:BITRate
Measurement Control
Turn the measurement on or off using the ON | OFF or RESTART | STOP keys. Alternatively, right-click the "Iperf" softkey.
The softkey shows the current measurement state. Additional measurement substates
may be retrieved via remote control.
Remote command:
INITiate:DATA:MEAS<i>:IPERf
STOP:DATA:MEAS<i>:IPERf
ABORt:DATA:MEAS<i>:IPERf
FETCh:DATA:MEAS<i>:IPERf:STATe?
FETCh:DATA:MEAS<i>:IPERf:STATe:ALL?
94
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Results.......................................................................................................................... 95
Settings......................................................................................................................... 95
Measurement Control....................................................................................................96
Results
The diagram shows the overall throughput on IP level vs. time.
"Uplink" indicates the received bit rate measured at the DAU while "Downlink" indicates
the bit rate transmitted to the mobile. In downlink direction, the throughput values on
RLC or MAC level can differ from those on IP level.
Below the diagram, the measured/transmitted current, minimum and maximum
throughput values are displayed.
Remote command:
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:ULINk[:CURRent]?
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:DLINk[:CURRent]?
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:ULINk:EXTended?
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:DLINk:EXTended?
READ:DATA:MEAS<i>:THRoughput:OVERall:ULINk?
READ:DATA:MEAS<i>:THRoughput:OVERall:DLINk?
Plus corresponding FETCh commands.
Settings
Press the "Config" hotkey to access the measurement settings.
95
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
"Interval": displays the time interval between two throughput measurement results
"Max. array size": specifies the maximum number of result values in the result trace
Example: Interval 1 s plus size 5 means that there are up to 5 results in the trace,
at the X-axis positions "0 s" to "-4 s". Older results are discarded.
"Traces visibility": allows you to show / hide the individual traces in the diagram
Remote command:
SENSe:DATA:MEAS<i>:THRoughput:INTerval?
CONFigure:DATA:MEAS<i>:THRoughput:MCOunt
Measurement Control
Turn the measurement on or off using the ON | OFF or RESTART | STOP keys. Alternatively, right-click the "Throughput" softkey.
The softkey shows the current measurement state. Additional measurement substates
may be retrieved via remote control.
Remote command:
INITiate:DATA:MEAS<i>:THRoughput
STOP:DATA:MEAS<i>:THRoughput
ABORt:DATA:MEAS<i>:THRoughput
FETCh:DATA:MEAS<i>:THRoughput:STATe?
FETCh:DATA:MEAS<i>:THRoughput:STATe:ALL?
96
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Results.......................................................................................................................... 97
Settings......................................................................................................................... 97
Measurement Control....................................................................................................98
Results
The "Request Count" indicates the number of recorded DNS queries.
The table below provides a list of the recorded requests and answers, including the following information for each request:
"Client IP": IP address of the client (mobile) that has sent the DNS request
"Requested Domain / Application": Information that shall be resolved by the DNS
query. A type A or type AAAA DNS query indicates a domain, while a type SRV
DNS query indicates an application name.
"Resolved IP / Domain": Information returned for the DNS query. A successful type
A or type AAAA DNS query returns the IP address of the requested domain. A successful type SRV DNS query returns a domain supporting the requested application.
"Timestamp": Time when the query was received.
Remote command:
SENSe:DATA:MEAS<i>:DNSRequests:RCOunt?
SENSe:DATA:MEAS<i>:DNSRequests?
Settings
Press the "Config" hotkey to access the measurement settings.
97
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
"Max. Index Count": specifies the maximum length of the result list (number of
requests). The result list is stored in a ring buffer. When it is full, the first result line
is deleted whenever a new result line is added to the end.
Remote command:
CONFigure:DATA:MEASurement<inst>:DNSRequests:MICount
Measurement Control
Turn the measurement on or off using the ON | OFF or RESTART | STOP keys. Alternatively, right-click the "DNS Requests" softkey.
The softkey shows the current measurement state. Additional measurement substates
may be retrieved via remote control.
Remote command:
INITiate:DATA:MEAS<i>:DNSRequests
STOP:DATA:MEAS<i>:DNSRequests
ABORt:DATA:MEAS<i>:DNSRequests
FETCh:DATA:MEAS<i>:DNSRequests:STATe?
FETCh:DATA:MEAS<i>:DNSRequests:STATe:ALL?
98
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
You can for example copy/paste the currently selected log file to a USB stick or delete
a log file. Or you can change an automatically assigned file name.
Before pressing a hotkey, select the desired folder or file in the "IP Logging" tab.
99
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Settings
Press the "Config" hotkey to access the IP logging settings.
"Logging Interface":
Selects which interface shall be monitored. To monitor the communication at the
LAN DAU connector, select "LAN-DAU".
To monitor the communication with the mobile, select "U-Plane..." depending on
the traffic type to be monitored:
"U-Plane IP": IP unicast traffic, for example relevant for LTE, WCDMA, GSM,
WLAN and CDMA2000 1xEV-DO (eHRPD)
"U-Plane PPP": PPP encapsulated IP traffic, for example relevant for
CDMA2000 1xRTT / 1xEV-DO (HRPD)
"U-Plane Multicast": IP multicast traffic, for example relevant for LTE
With this selection, only the downlink multicast traffic is monitored. The unicast
answers in the uplink are not monitored. Option R&S CMW-KA150 is required
for multicast traffic.
"Log File Name":
If IP logging is on, the name of the currently used log file is displayed. If IP logging
is off, a file with the displayed name will be created when logging is started.
The name is defined automatically. It contains information about the DAU measurement instance, the logging interface and an index. The index is increased
automatically, so that an existing file is never overwritten.
"Advanced Settings":
The advanced settings allow you to limit logging. "0" means no limit.
"File Size": limits the size of the log file. When this file size is reached, logging
stops.
"Packet Counter": limits the number of IP packets to be logged. When this
number of packets is reached, logging stops.
"Snap Length": limits the number of bytes to be logged for each IP packet. If
the packet is longer, only the specified number of bytes is logged. The remaining bytes of the packet are ignored.
Remote command:
CONFigure:DATA:MEAS<i>:IPLogging:TYPE
SENSe:DATA:MEAS<i>:IPLogging:FNAMe?
CONFigure:DATA:MEAS<i>:IPLogging:FSIZe
CONFigure:DATA:MEAS<i>:IPLogging:PCOunter
CONFigure:DATA:MEAS<i>:IPLogging:PSLength
Logging Control
Turn logging on or off using the ON | OFF or RESTART | STOP keys. Alternatively,
right-click the "IP Logging" softkey.
100
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
The softkey shows the current state. Additional substates may be retrieved via remote
control.
Remote command:
INITiate:DATA:MEAS<i>:IPLogging
STOP:DATA:MEAS<i>:IPLogging
ABORt:DATA:MEAS<i>:IPLogging
FETCh:DATA:MEAS<i>:IPLogging:STATe?
FETCh:DATA:MEAS<i>:IPLogging:STATe:ALL?
Analysis of reasons for too low throughput. Use the "TCP Analysis" view to check
the number of retransmissions, the TCP window size and the overhead.
Option R&S CMW-KM051 is required for "IP Analysis". Without this option, the "IP
Analysis" tab is hidden.
4.2.8.1
Overview
The results of the "IP Analysis" application are displayed in an overview and several
detailed views. The overview summarizes the most important results. If you are interested in a specific part of the overview, expand this part by opening the related
detailed view.
For a description of the individual results, refer to the detailed view sections.
101
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
102
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Export DB (hotkey)
Stores the IP analysis result database to a .csv file on the DAU hard disk.
Remote command:
CONFigure:DATA:MEAS<i>:IPANalysis:EXPortdb
Measurement Control
Turn the measurement on or off using the ON | OFF or RESTART | STOP keys. Alternatively, right-click the "IP Analysis" softkey.
The softkey shows the current measurement state. Additional measurement substates
may be retrieved via remote control.
Remote command:
INITiate:DATA:MEAS<i>:IPANalysis
STOP:DATA:MEAS<i>:IPANalysis
ABORt:DATA:MEAS<i>:IPANalysis
FETCh:DATA:MEAS<i>:IPANalysis:STATe?
FETCh:DATA:MEAS<i>:IPANalysis:STATe:ALL?
4.2.8.2
103
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Results........................................................................................................................ 104
Threshold Configuration..............................................................................................105
Results
A threshold check is performed for three properties of each connection, for the downlink as well as for the uplink. If a threshold is exceeded, this is indicated by a red NOK
or FULL, otherwise a green OK is displayed.
The three checked properties are:
"TCP Win.":
Current TCP window size as percentage of the negotiated maximum window size.
The maximum window size defines how many bytes may be transmitted without
waiting for an acknowledgment. Or in other words: how many unacknowledged
bytes may be on the way simultaneously.
If the current window size reaches the maximum window size, no more packets are
sent until acknowledgments are received. So a too small maximum window size
decreases the throughput.
"Retrans.":
Retransmisions as percentage of all transmissions.
Retransmissions decrease the throughput.
"Overhead":
Percentage of the packet consumed by headers (non-payload part of the packet).
A high overhead reduces the payload and thus the throughput.
In addition to the threshold check results for these properties, the downlink and uplink
throughput are displayed for each connection.
Select a connection to display additional properties in the lower table:
IP Source / Destination: Address and port of the source that has initiated the connection and of the destination addressed by the source.
104
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Maximum TCP Window: Maximum TCP window size negotiated for the connection.
Current TCP Window, Retransmitted Data, Overhead: Measured values used for
the threshold checks.
Remote command:
SENSe:DATA:MEAS<i>:IPANalysis:TCPanalysis:FLOWid?
SENSe:DATA:MEAS<i>:IPANalysis:TCPanalysis:DETails?
FETCh:DATA:MEAS<i>:IPANalysis:TCPanalysis:ALL?
Threshold Configuration
Press the "Config" hotkey to access the threshold settings.
Remote command:
CONFigure:DATA:MEAS<i>:IPANalysis:TCPanalysis:TWSThreshold
CONFigure:DATA:MEAS<i>:IPANalysis:TCPanalysis:TRTHreshold
CONFigure:DATA:MEAS<i>:IPANalysis:TCPanalysis:TOTHreshold
4.2.8.3
105
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Select a filter column and enter a filter text. You can enter a single value or a commaseparated list of values. Wildcards are not supported.
Results
The top of the view provides statistical information.
The table in the lower part lists the following information for each connection:
"Conn. Status": Connection still open or already closed
"L4 Prot.": Layer 4 protocol (transport layer)
"L7 Prot.": Layer 7 protocol (application layer)
"IP Source", "Source Port": IP address and port of the source that has initiated the
connection
106
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
"IP Destination", "Dest. Port": IP address and port of the destination addressed by
the source
"Overh. Down / Up": Percentage of a packet consumed by headers (non-payload
part of the packet), for downlink and uplink
"Avg. P-Size Down / Up": Average packet size for downlink and uplink
Remote command:
SENSe:DATA:MEAS<i>:IPANalysis:IPConnect:STATistics?
SENSe:DATA:MEAS<i>:IPANalysis:IPConnect:FLOWid?
FETCh:DATA:MEAS<i>:IPANalysis:IPConnect:ALL?
4.2.8.4
107
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
The term "Remote Destination" refers to the partner destination of the mobile (mobile
at one end of the connection, "Remote Destination" at the other end).
Remote command:
FETCh:DATA:MEAS<i>:IPANalysis:DPCP:DPConnection?
Data Per Protocol
The view provides an overview of the amount of data transported via the individual protocols since the measurement was started.
Remote command:
FETCh:DATA:MEAS<i>:IPANalysis:DPCP:DPPRotocol?
Data Per Layer
The view provides a layer-based overview of the amount of data transported since the
measurement was started.
108
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
109
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
You can select an application and display information for a lower layer.
To navigate to the next lower layer:
Double-click an entry in the "Application" column, or
Select an entry in the "Application" column and press the hotkey "Detailed View"
In the following example, this action has been performed three times, to navigate from
the application layer (IMS) through layer 7 (RTP) and layer 4 (UDP) to layer 3 (IPv6).
This path is displayed as "Selected Application Path".
110
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
The lower diagram displays a history of the open and close events (number of connections opened or closed per second).
The history covers the previous hour. Configure the X-axis to select the time period
you are interested in. The two diagrams are synchronized and show the same time
period.
111
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
As a result, the IDs of all connections opened at the "Start Events" marker position
are listed above the diagram. The IDs of all connections closed at the "End Events"
marker position are listed below the diagram.
Results
The upper diagram displays the total throughput (uplink plus downlink) of selected connections vs. time. The X-axis indicates the time in seconds, with 0 corresponding to
"now".
The lower diagram indicates the number of connections opened per second as positive
bars and the number of connections closed per second as negative bars. The labels
above/below the bars indicate the ID of one opened/closed connection. To improve the
display of labels, zoom into the diagram (scale the X-axis). To display all IDs of a
selected bar, see Using markers to display IDs in the lower diagram.
Remote command:
CONFigure:DATA:MEAS<i>:IPANalysis:FTTRigger:TRACe<TraceIndex>:
TFLowid
FETCh:DATA:MEAS<i>:IPANalysis:FTTRigger:TRACes<TraceIndex>:
FTHRoughput?
FETCh:DATA:MEAS<i>:IPANalysis:FTTRigger:TRIGger:STARt?
FETCh:DATA:MEAS<i>:IPANalysis:FTTRigger:TRIGger:END?
4.2.8.6
Table columns:
"Id.": Call ID
112
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
"Details": Selects the calls, for which detailed information shall be displayed in the
subtabs of the lower part
"Flows": IDs of the flows used by the call
The same IDs are displayed in other views, for example the "IP Connectivity" view
and the "Flow Throughput and Trigger" view. So you can use the flow IDs to correlate the information in different views.
"Call": Call type audio, video or emergency
"Origin": Mobile-terminating (MT) call initiated by the DAU or mobile-originating
(MO) call initiated by the mobile
"State": One of the following call states:
Ringing - MT call setup started, mobile is ringing
Established - call established
Released - established call has been released
Hold - call on hold
"Start": Time when the call setup was initiated (INVITE message sent/received)
"Setup": Duration of the call setup procedure (from INVITE message to first RTP
packet)
"Duration": Duration of the call (from INVITE message to BYE/Cancel)
"User From": User ID or phone number of the calling party
For an MO call the calling party is the UE. For an MT call, the calling party is the
DAU, simulating a calling UE.
"User To": User ID or phone number of the called party
For an MT call the called party is the UE. For an MO call, the called party is the
DAU, simulating a called UE.
Remote command:
FETCh:DATA:MEAS<i>:IPANalysis:VOIMs:ALL?
Flows Info subtab (lower part)
This subtab displays a table with one line per flow and direction. The listed flows are
related to the calls selected in the upper part, column "Details".
113
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Remote command:
SENSe:DATA:MEAS<i>:IPANalysis:VOIMs:FLOWs?
Packets Meas subtab (lower part)
This subtab displays the results of packet measurements for the calls selected in the
upper part, column "Details". You can display the bar graphs of up to four calls in parallel. Each X-axis label corresponds to one call.
114
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Remote command:
SENSe:DATA:MEAS<i>:IPANalysis:VOIMs:JITTer?
115
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
116
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Remote command:
SENSe:DATA:MEAS<i>:IPReplay:INFofile?
SENSe:DATA:MEAS<i>:IPReplay:PROGress?
Connection Information (lower part of tab)
The lower part of the tab lists all IP connections contained in the pcap file that is
selected in the upper part.
The information listed for each IP connection includes:
The layer 4 protocol and the number of IP packets
The IP address and port number of the sender (source) and of the recipient (destination) of the IP packets
Remote command:
SENSe:DATA:MEAS<i>:IPReplay:TRAFficfile?
Play/Stop (hotkeys)
The "Play" hotkey starts replaying the playlist. The "Stop" hotkey aborts replaying. It is
not possible to pause and continue a replay.
The "Play" hotkey is only active if the "IP Replay" application is running and the playlist
is not empty.
Remote command:
CONFigure:DATA:MEAS<i>:IPReplay:PLAYall
CONFigure:DATA:MEAS<i>:IPReplay:STOPall
Clear Playlist (hotkey)
The "Clear Playlist" hotkey is only active if the "IP Replay" application is switched off.
117
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
The left part lists all pcap files stored in the directory ip_replay of the samba share.
The right part displays the playlist contents.
Double-click a file on the left to add it to the playlist. Double-click a file in the playlist to
remove it from the list.
For each file in the list, you can configure how often the file shall be replayed and to
which network interface:
"U-Plane IP": IP unicast traffic to the mobile
"U-Plane Multicast": IP multicast traffic to the mobile
"LAN-DAU": IP traffic to the LAN DAU connector
Remote command:
FETCh:DATA:MEAS<i>:IPReplay:FILelist?
CONFigure:DATA:MEAS<i>:IPReplay:CREatelist
CONFigure:DATA:MEAS<i>:IPReplay:ITERation
CONFigure:DATA:MEAS<i>:IPReplay:INTerface
Application Control
Turn the "IP Replay" application on or off using the ON | OFF or RESTART | STOP
keys. Alternatively, right-click the "IP Replay" softkey.
The softkey shows the current state. Additional substates may be retrieved via remote
control.
Remote command:
INITiate:DATA:MEAS<i>:IPReplay
STOP:DATA:MEAS<i>:IPReplay
ABORt:DATA:MEAS<i>:IPReplay
FETCh:DATA:MEAS<i>:IPReplay:STATe?
FETCh:DATA:MEAS<i>:IPReplay:STATe:ALL?
118
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
For calls with the media endpoint "Audioboard", "Uplink" and "Downlink" results are
displayed.
For calls with the media endpoint "Loopback", only "Loopback" results are displayed.
119
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
120
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
For "Uplink" and "Loopback", ensure that the DUT has enough audio input to send an
audio packet every 20 ms. Silence periods may result in skipped audio packets and
peaks in the trace. A peak every 8 samples for example means that the DUT has sent
an audio packet every 160 ms.
Remote command:
READ:DATA:MEAS<i>:ADELay:TRACe:ULINk[:CURRent]?
READ:DATA:MEAS<i>:ADELay:TRACe:DLINk[:CURRent]?
READ:DATA:MEAS<i>:ADELay:TRACe:LOOPback[:CURRent]?
Plus corresponding FETCh commands.
Time of Arrival Result Diagram
The lower diagram shows the timing error of audio packets received in the uplink direction. Ideally, an audio packet is received every 20 ms and a flat line at 0 ms is shown.
Remote command:
READ:DATA:MEAS<i>:ADELay:TRACe:TAULink[:CURRent]?
READ:DATA:MEAS<i>:ADELay:TRACe:TALoopback[:CURRent]?
Plus corresponding FETCh commands.
Result Table
The table below the diagrams provides a statistical evaluation for all measurement
results.
The "Current" value refers to the sample number 0 in the diagrams.
The "Average", "Minimum" and "Maximum" values are calculated from all results since
the beginning of the measurement.
Remote command:
READ:DATA:MEAS<i>:ADELay:ULINk?
READ:DATA:MEAS<i>:ADELay:DLINk?
READ:DATA:MEAS<i>:ADELay:LOOPback?
READ:DATA:MEAS<i>:ADELay:TAULink?
READ:DATA:MEAS<i>:ADELay:TALoopback?
Plus corresponding FETCh commands.
Settings
Press the "Config" hotkey to access the measurement settings.
"Interval": displays the fixed time interval between two display updates
"Samples per Interval": displays the fixed number of measurement samples per
interval
"Maximum Samples": configures the maximum size of the X-axis of the diagrams.
Measured data is kept within that range. Older data is discarded.
121
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Remote command:
CONFigure:DATA:MEAS<i>:ADELay:SPINterval?
CONFigure:DATA:MEAS<i>:ADELay:SAMPles?
CONFigure:DATA:MEAS<i>:ADELay:MSAMples
Measurement Control
Turn the measurement on or off using the ON | OFF or RESTART | STOP keys. Alternatively, right-click the "Audio Delay" softkey.
The softkey shows the current measurement state. Additional measurement substates
may be retrieved via remote control.
Remote command:
INITiate:DATA:MEAS<i>:ADELay
STOP:DATA:MEAS<i>:ADELay
ABORt:DATA:MEAS<i>:ADELay
FETCh:DATA:MEAS<i>:ADELay:STATe?
FETCh:DATA:MEAS<i>:ADELay:STATe:ALL?
122
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
The configuration table contains seven columns, each providing a set of impairments.
A set of impairments is either applied to a specific default bearer, identified via the destination IP address or to a specific dedicated bearer, identified via destination IP
address plus port range.
To apply network impairments to a bearer, configure one of the columns according to
your needs: Specify the destination IP address and the port range of the bearer and
configure the impairments. Enable the column via the checkbox at the top and press
the button "Impairm. ON" at the bottom of the dialog.
The individual settings are described briefly below. For a more detailed description of
the effects of the individual settings, see Chapter 7, "Annex: Network Impairments",
on page 275.
Used............................................................................................................................123
IP Address, Port Range Start/End.............................................................................. 123
Packetloss Rate.......................................................................................................... 123
Delay........................................................................................................................... 123
Jitter, Jitter Distribution................................................................................................124
Reordering Rate..........................................................................................................124
Duplicates Rate...........................................................................................................124
Corruption Rate...........................................................................................................124
Network Impairment Activation................................................................................... 124
Used
A set of impairments is only applied if this parameter is enabled. Ensure that you
enable only one set for a certain default bearer or dedicated bearer at a time.
Remote command:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:ENABle
IP Address, Port Range Start/End
These parameters select the bearer to which the impairments shall be applied. To
specify a default bearer, enter its destination IP address and specify zero for both port
parameters. To specify a dedicated bearer, enter its destination IP address and the
port range used by the bearer.
As IPv6 address, you can enter an IPv6 address or an IPv6 prefix. Examples:
IPv6 address: fc01:abab:cdcd:efe0::2
IPv6 prefix: fc01:abab:cdcd:efe0::/64
Remote command:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:IPADdress
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:PRANge
Packetloss Rate
On average, the specified percentage of outgoing IP packets will be discarded.
Remote command:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:PLRate
Delay
Delays all outgoing IP packets by the specified time.
123
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Remote command:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:DELay
Jitter, Jitter Distribution
The jitter specifies a packet delay variation. The maximum accepted jitter value equals
the specified delay time.
The distribution of the total delays is defined via the "Jitter Distribution". You can configure a uniform distribution, a normal (Gaussian) distribution, a pareto or a pareto normal distribution.
For details, see Chapter 7.1, "Delay and Jitter", on page 275.
Remote command:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:JITTer
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:JDIStribut
Reordering Rate
On average, the indicated percentage of outgoing packets is reordered. Reordering is
only possible, if a sufficient delay time is specified.
Remote command:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:RRATe
Duplicates Rate
On average, the indicated percentage of outgoing packets is duplicated.
Remote command:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:DRATe
Corruption Rate
On average, the indicated percentage of outgoing packets is corrupted, by introducing
a single bit error anywhere in the packet (header or payload).
Remote command:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:CRATe
Network Impairment Activation
To apply network impairments, you must configure and enable a set of impairments
(one table column) and globally activate network impairments.
You can activate/deactivate network impairments via the buttons "Impairm. ON/OFF" in
the configuration dialog.
The "Network Impairm." softkey also shows the current state.
Remote command:
SOURce:DATA:MEAS<i>:NIMPairment:STATe
124
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
Description
Marker (softkey)
Some measurements provide a "Marker" softkey for configuration of markers in result
diagrams. Press the softkey to display the related hotkeys. Which of the following hotkeys are available, depends on the measurement.
Hotkey
Description
"Ref. Marker"
Enable or disable the reference marker and select the marker position. If several 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 relative to the reference marker). If several traces can be displayed, a trace can
also be selected.
125
R&SCMW-B450A/B/D
GUI Reference
Data Application Measurements
126
R&SCMW-B450A/B/D
Programming
Data Application Control
5 Programming
The following sections provide programming examples for the data application unit.
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 <expression>:
Waits until the <expression> is not / no longer true. The <expression> usually evaluates a value returned by a query.
WAITKEY <message>:
Displays a dialog box with a <message> and waits until the box is closed by the
user.
PAUSE <time>:
Waits a certain number of seconds.
127
R&SCMW-B450A/B/D
Programming
Data Application Control
128
R&SCMW-B450A/B/D
Programming
Data Application Control
129
R&SCMW-B450A/B/D
Programming
Data Application Control
130
R&SCMW-B450A/B/D
Programming
Data Application Control
// *****************************************************************************
SENSe:DATA:CONTrol:FTP:USER:CATalog?
CONFigure:DATA:CONTrol:FTP:USER:ADD 'user1', 'newpwdxyz', ON, ON, ON
CONFigure:DATA:CONTrol:FTP:USER:ADD 'usernametypo', 'pwd', ON, ON, ON
CONFigure:DATA:CONTrol:FTP:USER:DELete 'usernametypo'
// *****************************************************************************
// Start the FTP service.
// *****************************************************************************
SOURce:DATA:CONTrol:FTP:STATe ON
The remaining commands in this section are only relevant if the internal IMS server is
used.
Using the internal IMS server
// *****************************************************************************
// Specify that the internal IMS server shall be used and
// configure the UDP/TCP threshold.
// *****************************************************************************
CONFigure:DATA:CONTrol:IMS2:SUSage INTernal
131
R&SCMW-B450A/B/D
Programming
Data Application Control
CONFigure:DATA:CONTrol:IMS2:TRANsport:SELection CUSTom
CONFigure:DATA:CONTrol:IMS2:THReshold:VALue 1000
132
R&SCMW-B450A/B/D
Programming
Data Application Control
CONFigure:DATA:CONTrol:IMS2:SUBScriber:CREate
SENSe:DATA:CONTrol:IMS2:SUBScriber:CATalog?
133
R&SCMW-B450A/B/D
Programming
Data Application Control
// Switch the mobile on and wait until it has registered to the IMS server.
// You can for example query the information in the "Info" area until it
// reports successful registration. Or insert a pause into your script.
// *****************************************************************************
SENSe:DATA:CONTrol:IMS2:GINFo?
Releasing a call
// *****************************************************************************
// Query a list of all established calls and release one call.
// *****************************************************************************
SENSe:DATA:CONTrol:IMS2:RELease:LIST?
CONFigure:DATA:CONTrol:IMS2:RELease:CALL:ID '4Mjh7g2CFmd0pMG9Gi93j-8lyly7fzPA'
134
R&SCMW-B450A/B/D
Programming
Data Application Control
// *****************************************************************************
// Send the message.
// *****************************************************************************
CONFigure:DATA:CONTrol:IMS2:VIRTualsub1:MTSMs:SEND
// *****************************************************************************
// Query the event log contents.
// Query details for one event log entry.
// *****************************************************************************
SENSe:DATA:CONTrol:IMS2:EVENts?
SENSe:DATA:CONTrol:IMS2:HISTory? 'Id.3880694434@fc01:abab:cdcd:efe0::1'
Deregistering a mobile
// *****************************************************************************
// Configure the short message.
// *****************************************************************************
CONFigure:DATA:CONTrol:IMS2:MOBile1:DERegister
135
R&SCMW-B450A/B/D
Programming
Data Application Measurements
// *****************************************************************************
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVFour:TYPE 20
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVSix:TYPE 21
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVSix:ADDRess:LENGth L16
// *****************************************************************************
// Configure authentication settings.
// *****************************************************************************
CONFigure:DATA:CONTrol:EPDG:AUTHentic:IMSI '001010123456063'
CONFigure:DATA:CONTrol:EPDG:AUTHentic:ALGorithm MILenage
CONFigure:DATA:CONTrol:EPDG:AUTHentic:KEY #H102030405060708090A0B0C0D0E0F
CONFigure:DATA:CONTrol:EPDG:AUTHentic:RAND #H12ACF4321
CONFigure:DATA:CONTrol:EPDG:AUTHentic:AMF #H8000
CONFigure:DATA:CONTrol:EPDG:AUTHentic:OPC #H1233CB71954A9F4E48A5994E37A02BAF
// *****************************************************************************
// Configure dead peer detection.
// *****************************************************************************
CONFigure:DATA:CONTrol:EPDG:DPD:ENABle ON
CONFigure:DATA:CONTrol:EPDG:DPD:INTerval 5
CONFigure:DATA:CONTrol:EPDG:DPD:TIMeout 30
// *****************************************************************************
// Configure the certificate usage for SSL.
// *****************************************************************************
CONFigure:DATA:CONTrol:EPDG:CERTificate:ENABle ON
CONFigure:DATA:CONTrol:EPDG:CERTificate:KEY "myKeyFile.pem"
CONFigure:DATA:CONTrol:EPDG:CERTificate:CERTificate "myCertificateFile.pem"
136
R&SCMW-B450A/B/D
Programming
Data Application Measurements
137
R&SCMW-B450A/B/D
Programming
Data Application Measurements
138
R&SCMW-B450A/B/D
Programming
Data Application Measurements
139
R&SCMW-B450A/B/D
Programming
Data Application Measurements
140
R&SCMW-B450A/B/D
Programming
Data Application Measurements
141
R&SCMW-B450A/B/D
Programming
Data Application Measurements
// Query the results relevant for the media endpoint type "Audioboard".
// *****************************************************************************
FETCh:DATA:MEAS:ADELay:TRACe:ULINk:CURRent?
FETCh:DATA:MEAS:ADELay:TRACe:DLINk:CURRent?
FETCh:DATA:MEAS:ADELay:TRACe:TAULink:CURRent?
FETCh:DATA:MEAS:ADELay:ULINk?
FETCh:DATA:MEAS:ADELay:DLINk?
FETCh:DATA:MEAS:ADELay:TAULink?
// *****************************************************************************
// Query the results relevant for the media endpoint type "Loopback".
// *****************************************************************************
FETCh:DATA:MEAS:ADELay:TRACe:LOOPback:CURRent?
FETCh:DATA:MEAS:ADELay:TRACe:TALoopback:CURRent?
FETCh:DATA:MEAS:ADELay:LOOPback?
FETCh:DATA:MEAS:ADELay:TALoopback?
//
//
// *****************************************************************************
SENSe:DATA:MEAS:IPANalysis:TCPanalysis:FLOWid? 3
FETCh:DATA:MEAS:IPANalysis:TCPanalysis:ALL?
SENSe:DATA:MEAS:IPANalysis:TCPanalysis:DETails? 3
// *****************************************************************************
// Query the "IP Connectivity" results:
//
142
R&SCMW-B450A/B/D
Programming
Data Application Measurements
//
//
// *****************************************************************************
SENSe:DATA:MEAS:IPANalysis:IPConnect:STATistics?
SENSe:DATA:MEAS:IPANalysis:IPConnect:FLOWid? 3
FETCh:DATA:MEAS:IPANalysis:IPConnect:ALL?
// *****************************************************************************
// Query the "Data Pie Charts" results:
//
//
//
//
// Query the data per application results of the application layer.
// Navigate to the next lower layer for the IMS application.
// Query the data per application results of layer 7 (for the IMS application).
// *****************************************************************************
FETCh:DATA:MEAS:IPANalysis:DPCP:DPConnection?
FETCh:DATA:MEAS:IPANalysis:DPCP:DPPRotocol?
FETCh:DATA:MEAS:IPANalysis:DPCP:DPLayer? APP
FETCh:DATA:MEAS:IPANalysis:DPCP:DPAPplic?
CONFigure:DATA:MEAS:IPANalysis:DPCP:DPAPplic:APP 'IMS'
FETCh:DATA:MEAS:IPANalysis:DPCP:DPAPplic?
// *****************************************************************************
// Assign connection number 3 to the throughput trace number 3.
// Query the "Flow Throughput and Event Trigger" results:
//
//
//
// *****************************************************************************
CONFigure:DATA:MEAS:IPANalysis:FTTRigger:TRACe3:TFLowid 3
FETCh:DATA:MEAS:IPANalysis:FTTRigger:TRACes3:FTHRoughput?
FETCh:DATA:MEAS:IPANalysis:FTTRigger:TRIGger:STARt?
FETCh:DATA:MEAS:IPANalysis:FTTRigger:TRIGger:END?
// *****************************************************************************
// Query the "Voice Over IMS" results:
//
//
//
//
measured jitter
// *****************************************************************************
FETCh:DATA:MEAS:IPANalysis:VOIMs:ALL?
SENSe:DATA:MEAS:IPANalysis:VOIMs:FLOWs? 34, 36, DL, VIDeo
SENSe:DATA:MEAS:IPANalysis:VOIMs:PERDtx? 132
SENSe:DATA:MEAS:IPANalysis:VOIMs:JITTer? 132
// *****************************************************************************
// Store the IP analysis result database to a file
143
R&SCMW-B450A/B/D
Programming
Data Application Measurements
// *****************************************************************************
CONFigure:DATA:MEAS:IPANalysis:EXPortdb
144
R&SCMW-B450A/B/D
Command Reference
Conventions and General Information
6 Command Reference
The following sections provide detailed reference information on the remote control
commands related to the Data Application Unit (DAU).
6.1.1 MEAS<i>
MEAS<i> is used as abbreviation of "MEASurement<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.
See also: "Firmware Applications" in the R&S CMW user manual, chapter "Remote
Control"
6.1.2 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:
Parameter usage
The parameter usage is indicated by the keyword preceding the parameter(s):
"Parameters" are sent with a setting or query command and are returned as
the result of a query
"Query parameters" are only sent with a query command (to refine the query)
Firmware/Software:
145
R&SCMW-B450A/B/D
Command Reference
Conventions and General Information
0 (OK):
Measurement values available, no error detected.
1 (Measurement Timeout):
The measurement has been stopped after the (configurable) measurement timeout. Measurement results may be available, however, at least a part of the measurement provides only INValid results or has not completed the full statistic count.
3 (Overdriven) / 4 (Underdriven):
The accuracy of measurement results may 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.
146
R&SCMW-B450A/B/D
Command Reference
Conventions and General Information
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.
21 (Call Lost):
For measurements: The measurement was interrupted because the signaling connection to the DUT was lost.
For DAU IMS service: The voice over IMS call was lost.
23 (Missing Option):
The ARB file cannot be played by the GPRF generator due to a missing option.
24 (Invalid RF Setting):
The desired RF TX level or RF RX reference level could not be applied.
26 (Resource Conflict):
The application could not be started or has been stopped due to a conflicting hardware resource or software option that is allocated by another application.
Stop the application that has allocated the conflicting resources and try again.
50 (Startup Error):
147
R&SCMW-B450A/B/D
Command Reference
Data Application Control
The Data Application Unit (DAU), a DAU service or a DAU measurement could not
be started. Please execute a DAU selftest.
51 (No Reply):
The DAU has received no response, for example for a ping request.
52 (Connection Error):
The DAU could not establish a connection to internal components. Please restart
the instrument.
53 (Configuration Error):
The current DAU configuration by the user is incomplete or wrong and could not be
applied. Check especially the IP address configuration.
54 (Filesystem Error):
The hard disk of the DAU is full or corrupt. Please execute a DAU selftest.
Firmware errors can often be repaired by restoring the factory default settings.
To restore these settings, restart your instrument and press the "Factory
Default" softkey during startup.
If a software package (update) has not been properly installed this is often indicated in the "Setup" dialog, section "SW/HW-Equipment > Installed Software".
A software update correcting the error may be available. Updates are e.g. provided in the "CMW Customer Web" on GLORIS (registration required): https://
extranet.rohde-schwarz.com.
If you get firmware errors even with the properly installed latest software version,
please send a problem report including log files to Rohde & Schwarz.
148
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Reset
The Data Application Control settings are considered as system settings and are thus
not affected by the command *RST.
However, the commands SYSTem:RESet:BASE and SYSTem:RESet:ALL reset also
system settings, including the Data Application Control settings. The "*RST:" information in the command descriptions indicates the result of these commands.
The commands for "Data Application Control" are divided into the following groups.
OFF | PENDing | ON
OFF: DAU switched off
PEND: DAU has been switched on and is booting
ON: DAU switched on and ready for operation
*RST:
Example:
ON
Firmware/Software: V3.0.10
Manual operation:
149
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:MTU <MaxTransUnit>
Specifies the MTU, that is the maximum IP packet size that can be transmitted without
fragmentation.
Parameters:
<MaxTransUnit>
Example:
Range:
552 byte to 4096 byte
*RST:
1500 byte
Default unit: byte
See Configuring General IP Settings
Firmware/Software: V3.2.20
Manual operation:
CONFigure:DATA:CONTrol:IPVFour:ADDRess:TYPE <AddressType>
Selects the type of the IPv4 configuration.
Parameters:
<AddressType>
Example:
AUT
Firmware/Software: V1.0.15.20
Manual operation:
150
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IPVFour:STATic:IPADdress <IPAddress>
Sets the IP address of the DAU to be used for static IPv4 configuration.
Parameters:
<IPAddress>
IP address as string
Range:
*RST:
Example:
'0.0.0.0' to '255.255.255.255'
'192.168.168.170'
Firmware/Software: V1.0.15.20
Manual operation:
CONFigure:DATA:CONTrol:IPVFour:STATic:SMASk <SubnetMask>
Defines the subnet mask for static IPv4 configuration.
Parameters:
<SubnetMask>
Example:
'0.0.0.0' to '255.255.255.255'
'255.255.255.0'
Firmware/Software: V1.0.15.20
Manual operation:
CONFigure:DATA:CONTrol:IPVFour:STATic:GIP <GatewayIP>
Defines the address of an external gateway to be used for static IPv4 configuration.
Parameters:
<GatewayIP>
IP address as string
Range:
*RST:
Example:
'0.0.0.0' to '255.255.255.255'
'192.168.168.1'
Firmware/Software: V1.0.15.20
Manual operation:
SENSe:DATA:CONTrol:IPVFour:CURRent:IPADdress?
Queries the current IPv4 address of the DAU.
Return values:
<IPAddress>
IP address as string
Range:
Example:
'0.0.0.0' to '255.255.255.255'
151
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:IPVFour:CURRent:SMASk?
Queries the subnet mask of the current IPv4 data testing configuration.
Return values:
<SubnetMask>
'0.0.0.0' to '255.255.255.255'
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:IPVFour:CURRent:GIP?
Queries the current IPv4 address of the gateway server.
Return values:
<GatewayIP>
IP address as string
Range:
'0.0.0.0' to '255.255.255.255'
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:IPVFour:STATic:ADDResses:ADD <IPAddress>
Adds a new IP address to the mobile IPv4 address pool for static IPv4 configuration.
Setting parameters:
<IPAddress>
IP address as string
Range:
'0.0.0.0' to '255.255.255.255'
Example:
Usage:
Event
Firmware/Software: V1.0.15.20
Manual operation:
152
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IPVFour:STATic:ADDResses:DELete <IPAddress>
Deletes an address from the mobile IPv4 address pool for static IPv4 configuration.
Setting parameters:
<IPAddress>
IP address to be deleted, either identified via its index number or
as string
Range:
Example:
Usage:
Event
Firmware/Software: V1.0.15.20
Manual operation:
SENSe:DATA:CONTrol:IPVFour:STATic:ADDResses:CATalog?
Queries the current mobile IPv4 address pool configured statically.
Return values:
<IPAddress>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:IPVFour:DHCP:ADDResses:CATalog?
Queries the current mobile IPv4 address pool configured via DHCPv4.
Return values:
<IPAddress>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:IPVFour:AUTomatic:ADDResses:CATalog?
Queries the current mobile IPv4 address pool configured automatically (standalone
setup).
153
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Return values:
<IPAddress>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:IPVSix:ADDRess:TYPE <AddressType>
Selects the method to be used for IPv6 DAU address configuration.
Parameters:
<AddressType>
Example:
AUTO
Firmware/Software: V1.0.15.20
V3.0.10: all parameter values changed
Manual operation:
154
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IPVSix:STATic:ADDRess <IPAddress>
Sets the IP address of the DAU to be used for static IPv6 configuration.
Parameters:
<IPAddress>
Example:
'fcb1:cafe::1/64'
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:IPVSix:STATic:DROuter <Router>
Sets the IP address of the external default router to be used for static IPv6 configuration.
Parameters:
<Router>
Example:
'fcb1:cafe::1'
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:IPVSix:CURRent:IPADdress?
Queries the current IPv6 address of the DAU.
Return values:
<IPAddress>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:IPVSix:CURRent:DROuter?
Queries the IPv6 address currently used to address the default router.
Return values:
<DefRouter>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
155
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Manual operation:
CONFigure:DATA:CONTrol:IPVSix:MOBile:PREFix:TYPE <PrefixType>
Selects the method to be used for mobile IPv6 prefix configuration.
This setting is only relevant for test setups with connected external network. It is
ignored for a Standalone test setup (AUTO set via CONFigure:DATA:CONTrol:
IPVSix:ADDRess:TYPE on page 154).
Parameters:
<PrefixType>
STATic | DHCP
STATic: static IP configuration
DHCP: DHCP prefix delegation
*RST:
Example:
STAT
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:IPVSix:STATic:PREFixes:ADD <Prefix>
Adds a new 64 bit prefix to the mobile IPv6 prefix pool for static IPv6 configuration.
Setting parameters:
<Prefix>
String, e.g. 'fcb1:abab:cdcd:efe0::/64'
Example:
Usage:
Event
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:IPVSix:STATic:PREFixes:DELete <Prefix>
Deletes an address from the mobile IPv6 prefix pool for static IPv6 configuration.
Setting parameters:
<Prefix>
Entry to be deleted, either identified via its index number or its
prefix string
Range:
Example:
Usage:
Event
Firmware/Software: V3.0.10
Manual operation:
156
R&SCMW-B450A/B/D
Command Reference
Data Application Control
SENSe:DATA:CONTrol:IPVSix:STATic:PREFixes:CATalog?
Queries the current mobile IPv6 prefix pool configured statically.
Return values:
<Prefixes>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:IPVSix:DHCP:PREFixes:CATalog?
Queries the current mobile IPv6 prefix pool configured via DHCP prefix delegation.
Return values:
<Prefixes>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:IPVSix:AUTomatic:PREFixes:CATalog?
Queries the current mobile IPv6 prefix pool configured automatically (standalone
setup).
Return values:
<Prefixes>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:IPVSix:ROUTing:TYPE <RoutingType>
Selects the mechanism to be used for IPv6 route configuration. The configured routes
are only relevant for packets sent by the mobile with destination addresses neither
belonging to the subnet of the DAU nor reachable via the default router.
157
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<RoutingType>
MANual
In the current software version the value is fixed.
MANual: manually configured routes
*RST:
Example:
MANual
Firmware/Software: V3.0.10
Manual operation:
Example:
Usage:
Event
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:IPVSix:MANual:ROUTing:DELete <Prefix>
Deletes an entry from the pool of manual routes for IPv6.
Setting parameters:
<Prefix>
Entry to be deleted, either identified via its index number or its
prefix string
Range:
Example:
Usage:
Event
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:IPVSix:MANual:ROUTing:CATalog?
Queries the pool of manual routes for IPv6.
The two values listed below are returned for each route: {<Prefixes>, <Routers>}entry 0,
{<Prefixes>, <Routers>}entry 1, ...
158
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Return values:
<Prefixes>
<Routers>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:DNS:PRIMary:STYPe <SType>
CONFigure:DATA:CONTrol:DNS:SECondary:STYPe <SType>
Select the primary and secondary DNS server type.
159
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<SType>
Example:
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:DNS:CURRent:IPVFour:PRIMary:ADDRess?
Queries the IPv4 address sent to the mobile as primary DNS server address.
Return values:
<CDNSPrimIP4>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:DNS:CURRent:IPVFour:SECondary:ADDRess?
Queries the IPv4 address sent to the mobile as secondary DNS server address.
Return values:
<CDNSSecIP4>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:DNS:CURRent:IPVSix:PRIMary:ADDRess?
Queries the IPv6 address sent to the mobile as primary DNS server address.
Return values:
<CDNSPrimIP6>
Example:
Usage:
Query only
160
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:DNS:CURRent:IPVSix:SECondary:ADDRess?
Queries the IPv6 address sent to the mobile as secondary DNS server address.
Return values:
<CDNSSecIP6>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:DNS:FOReign:IPVFour:PRIMary:ADDRess
<FDNSPrimIP4>
Specifies the IPv4 address of the foreign primary DNS server.
Parameters:
<FDNSPrimIP4>
Example:
'0.0.0.0' to '255.255.255.255'
'192.168.168.171'
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:DNS:FOReign:IPVFour:SECondary:ADDRess
<FDNSSecIP4>
Specifies the IPv4 address of the foreign secondary DNS server.
Parameters:
<FDNSSecIP4>
Example:
'0.0.0.0' to '255.255.255.255'
'192.168.168.171'
Firmware/Software: V3.0.10
Manual operation:
161
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:DNS:FOReign:IPVSix:PRIMary:ADDRess
<FDNSPrimIP6>
Specifies the IPv6 address of the foreign primary DNS server.
Parameters:
<FDNSPrimIP6>
Example:
'fcb1:cafe::2'
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:DNS:FOReign:IPVSix:SECondary:ADDRess
<FDNSSecIP6>
Specifies the IPv6 address of the foreign secondary DNS server.
Parameters:
<FDNSSecIP6>
Example:
'fcb1:cafe::2'
Firmware/Software: V3.0.10
Manual operation:
OFF | ON
DHCPv4 address, primary DNS server
*RST:
<PrimIP6>
ON
OFF | ON
DHCPv6 address, primary DNS server
*RST:
<SecIP4>
ON
OFF | ON
DHCPv4 address, secondary DNS server
*RST:
ON
162
R&SCMW-B450A/B/D
Command Reference
Data Application Control
<SecIP6>
OFF | ON
DHCPv6 address, secondary DNS server
*RST:
Example:
ON
Firmware/Software: V3.2.20
Manual operation:
Example:
Usage:
Event
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:DNS:LOCal:DELete <URLorIP>
Deletes an entry from the database of the local DNS server for type A or type AAAA
DNS queries.
Each entry consists of two strings, one specifying a domain and the other indicating the
assigned IP address. Enter one of these strings to select the entry to be deleted.
Setting parameters:
<URLorIP>
String selecting the entry to be deleted
Example:
Usage:
Event
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:DNS:LOCal:CATalog?
Queries the entries of the local DNS server database for type A or type AAAA DNS
queries.
163
R&SCMW-B450A/B/D
Command Reference
Data Application Control
The two values listed below are returned for each database entry: {<Url>, <IP>}entry 0,
{<Url>, <IP>}entry 1, ...
Return values:
<Url>
<IP>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
<Protocol>
UDP | TCP
<Port>
Range:
Example:
Usage:
Event
0 to 65654
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:DNS:ASERvices:DELete <Name>
Deletes an entry from the database of the local DNS server for type SRV DNS queries.
Setting parameters:
<Name>
String specifying the service name of the entry to be deleted
Example:
Usage:
Event
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:DNS:ASERvices:CATalog?
Queries the entries of the local DNS server database for type SRV DNS queries.
164
R&SCMW-B450A/B/D
Command Reference
Data Application Control
The four values listed below are returned for each database entry: {<Name>, <Url>,
<Protocol>, <Port>}entry 0, {...}entry 1, ...
Return values:
<Name>
<Url>
<Protocol>
UDP | TCP
<Port>
Range:
Example:
Usage:
Query only
0 to 65654
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:DNS:TEST:DOMain <Domain>
Specifies the domain to be resolved during a test of the foreign DNS server.
Parameters:
<Domain>
Example:
'www.rohde-schwarz.com'
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:CONTrol:DNS:TEST:STARt
Starts a test of the foreign DNS server.
Example:
Usage:
Event
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:CONTrol:DNS:TEST:RESults?
Queries the results of a foreign DNS server test.
NONE indicates that no result is available (e.g. no test started yet).
"Successful query" means that the domain could be resolved and the DNS server has
returned an IP address.
165
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Return values:
<V4SAvailable>
<V4AResRec>
<V44AResRec>
<V6SAvailable>
<V6AResRec>
<V64AResRec>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SOURce:DATA:CONTrol:DNS:STATe <Control>
Starts or stops the local DNS server.
Setting parameters:
<Control>
ON | OFF
Switch the service ON or OFF
Return values:
<State>
OFF | ON | PENDing
OFF: service switched off
ON: service switched on
PEND: service activation or deactivation ongoing
*RST:
Example:
OFF
Firmware/Software: V3.0.10
Manual operation:
166
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:FTP:STYPe <ServiceType>
Selects the FTP service type.
The other CONFigure:DATA:CONTrol:FTP:... commands configure the FTP
server. They are not relevant, if the service type TGENerator is selected.
Parameters:
<ServiceType>
SERVer | TGENerator
SERVer: an FTP server runs on the R&S CMW
TGENerator: the R&S CMW acts as a traffic generator
*RST:
Example:
SERV
Firmware/Software: V1.0.15.20
Manual operation:
CONFigure:DATA:CONTrol:FTP:ENConnection <ExtNetConn>
Specifies whether access to the FTP server is allowed from an external network (via
LAN DAU).
Parameters:
<ExtNetConn>
OFF | ON
OFF: not allowed
ON: allowed
*RST:
Example:
ON
Firmware/Software: V1.0.15.20
Manual operation:
CONFigure:DATA:CONTrol:FTP:IPVSix <IPv6Enable>
Specifies whether the FTP server supports IPv6.
167
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<IPv6Enable>
OFF | ON
OFF: IPv4 support only
ON: support of IPv4 and IPv6
*RST:
Example:
ON
Firmware/Software: V1.0.15.20
V3.0.10: *RST value changed
Manual operation:
CONFigure:DATA:CONTrol:FTP:AUSer <Anonymous>
Specifies whether access to the FTP server is allowed for anonymous users.
Parameters:
<Anonymous>
OFF | ON
OFF: not allowed
ON: allowed
*RST:
Example:
ON
Firmware/Software: V1.0.15.20
Manual operation:
CONFigure:DATA:CONTrol:FTP:DUPLoad <DataUpload>
Specifies whether data upload to the FTP server is allowed for anonymous users.
Parameters:
<DataUpload>
OFF | ON
OFF: not allowed
ON: allowed
*RST:
Example:
ON
Firmware/Software: V1.0.15.20
Manual operation:
168
R&SCMW-B450A/B/D
Command Reference
Data Application Control
<Password>
Password as string
<DeleteAllowed>
OFF | ON
<DownloadAllowed> OFF | ON
<UploadAllowed>
OFF | ON
Example:
Usage:
Event
Firmware/Software: V1.0.15.20
Manual operation:
SENSe:DATA:CONTrol:FTP:USER:CATalog?
Queries the existing FTP user accounts and their permissions.
The four values listed below are returned for each FTP user: {<User>, <DeleteAllowed>, <DownloadAllowed>, <UploadAllowed>}user 1, {...}user 2, ..., {...}user n.
Return values:
<User>
<DeleteAllowed>
OFF | ON
OFF: delete forbidden
ON: delete allowed
<DownloadAllowed> OFF | ON
OFF: download forbidden
ON: download allowed
<UploadAllowed>
OFF | ON
OFF: upload forbidden
ON: upload allowed
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
Example:
169
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Usage:
Event
Firmware/Software: V1.0.15.20
V3.0.10: <Password> now optional
Manual operation:
SOURce:DATA:CONTrol:FTP:STATe <Control>
Starts or stops the FTP service.
Setting parameters:
<Control>
ON | OFF
Switch the service ON or OFF
Return values:
<State>
OFF | ON | PENDing
OFF: service switched off
ON: service switched on
PEND: service activation or deactivation ongoing
*RST:
Example:
OFF
Firmware/Software: V1.0.15.20
Manual operation:
CONFigure:DATA:CONTrol:HTTP:ENConnection <ExtNetConn>
Specifies whether access to the internal web server is allowed from an external network (via LAN DAU).
Parameters:
<ExtNetConn>
OFF | ON
OFF: not allowed
ON: allowed
*RST:
Example:
ON
Firmware/Software: V1.0.15.20
Manual operation:
170
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:HTTP:IPVSix <IPv6Enable>
Specifies whether the internal web server supports IPv6.
Parameters:
<IPv6Enable>
OFF | ON
OFF: IPv4 support only
ON: support of IPv4 and IPv6
*RST:
Example:
ON
Firmware/Software: V1.0.15.20
V3.0.10: *RST value changed
Manual operation:
SOURce:DATA:CONTrol:HTTP:STATe <Control>
Starts or stops the HTTP service.
Setting parameters:
<Control>
ON | OFF
Switch the service ON or OFF
Return values:
<State>
OFF | ON | PENDing
OFF: service switched off
ON: service switched on
PEND: service activation or deactivation ongoing
*RST:
Example:
OFF
Firmware/Software: V1.0.15.20
Manual operation:
171
R&SCMW-B450A/B/D
Command Reference
Data Application Control
6.2.8.1
SOURce:DATA:CONTrol:IMS2:STATe <Control>
Starts or stops the IMS service and the IMS server.
Setting parameters:
<Control>
ON | OFF
Switch the service ON or OFF
Return values:
<State>
OFF | ON | PENDing
OFF: service switched off
ON: service switched on
PEND: service activation or deactivation ongoing
*RST:
Example:
OFF
Firmware/Software: V3.5.10
Manual operation:
SENSe:DATA:CONTrol:IMS2:GINFo?
Queries all entries of the "General IMS Info" area.
For each entry, three parameters are returned, from oldest to latest entry: {<Timestamp>, <InfoType>, <GenericInfo>}entry 1, {<Timestamp>, <InfoType>, <GenericInfo>}entry 2, ...
Return values:
<Timestamp>
<InfoType>
<GenericInfo>
172
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Example:
Usage:
Query only
Firmware/Software: V3.5.10
Manual operation:
SENSe:DATA:CONTrol:IMS2:EVENts?
Queries all entries of the event log.
For each entry, six parameters are returned: {<ID>, <Timestamps>, <Source>, <Destination>, <Type>, <State>}entry 1, {<ID>, ..., <State>}entry 2, ...
Return values:
<ID>
<Timestamps>
<Source>
<Destination>
<Type>
<State>
Example:
Usage:
Query only
Firmware/Software: V3.5.10
Manual operation:
SENSe:DATA:CONTrol:IMS2:HISTory? <ID>
Queries details for a selected event log entry.
The returned sequence depends on the type of the entry:
For a call entry, eight values are returned for each recorded state:
{<HistoryState>, <HistoryTimestamps>, <SignalingType>,
<AMRType>, <AMRAlignMode>, <AMRMode>, <VideoCodec>,
<VideoAttributes>}state 1, {...}state 2, ..., {...}state n
173
R&SCMW-B450A/B/D
Command Reference
Data Application Control
If a parameter is not relevant for a state, INV is returned for this parameter.
Query parameters:
<ID>
Return values:
<SMSTimestamps>
<SMSType>
<SMSEncoding>
<SMSText>
<HistoryState>
<AMRType>
<AMRAlignMode>
OCTetaligned | BANDwidtheff
AMR voice codec alignment mode of the call
<AMRMode>
<VideoCodec>
H263 | H264
Video codec of the video call
<VideoAttributes>
Example:
Usage:
Query only
Firmware/Software: V3.5.10
V3.5.21: codec type EVS
Manual operation:
174
R&SCMW-B450A/B/D
Command Reference
Data Application Control
SENSe:DATA:CONTrol:IMS2:MOBile<UE>:STATus?
Queries the state of a subscriber.
Suffix:
<UE>
Return values:
<Status>
.
1..5
Profile number of the subscriber to be queried
UNRegistered | REGistered | EXPired
Mobile unregistered, registered or registration expired
Usage:
Query only
Firmware/Software: V3.5.10
6.2.8.2
CONFigure:DATA:CONTrol:IMS2:UPDate:CALL:ID <ID>
Selects the call that shall be updated. To query a list of IDs, see CONFigure:DATA:
CONTrol:IMS2:RELease:CALL:ID on page 178.
All other UPDate commands affect the call selected via this command.
Parameters:
<ID>
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:UPDate:AMR:TYPE <AudioCodec>
Selects the new audio codec type for a call update: AMR NB, AMR WB or EVS.
175
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<AudioCodec>
Example:
NARR
Firmware/Software: V3.5.10
V3.5.21: codec type EVS
Manual operation:
CONFigure:DATA:CONTrol:IMS2:UPDate:AMR:ALIGnment <AMRAlignment>
Selects the new AMR voice codec alignment mode for a call update.
Parameters:
<AMRAlignment>
OCTetaligned | BANDwidtheff
OCTetaligned: octet-aligned
BANDwidtheff: bandwidth-efficient
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:UPDate:AMR:CODec<CodecIdx>:ENABle
<CodecRate>
Enables or disables an AMR codec rate for a call update.
Suffix:
<CodecIdx>
Parameters:
<CodecRate>
.
1..9
Selects the codec rate via its index.
OFF | ON
OFF: codec rate not supported
ON: codec rate supported
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:UPDate:VIDeo:CODec <VideoCodec>
Selects the video codec for a call update.
Parameters:
<VideoCodec>
H263 | H264
H.263 or H.264 codec
*RST:
H263
176
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:UPDate:VIDeo:ATTRibutes <VideoAttributes>
Configures video codec attributes for a call update.
Parameters:
<VideoAttributes>
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:UPDate:CALL:TYPE <CallType>
Selects the new call type for a call update.
Parameters:
<CallType>
AUDio | VIDeo
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:UPDate:PERForm
Initiates the call update.
The settings configured via the UPDate commands are applied to the call selected via
CONFigure:DATA:CONTrol:IMS2:UPDate:CALL:ID on page 175.
Example:
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
SENSe:DATA:CONTrol:IMS2:RELease:LIST?
Queries the IDs of all established calls.
Return values:
<Ids>
Example:
Usage:
Query only
177
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:RELease:CALL:ID <ID>
Queries a list of call IDs or releases a call selected via its ID.
Setting parameters:
<ID>
ID as string, selecting the call to be released
Return values:
<IDs>
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:MOBile<UE>:DERegister
Deregisters a registered subscriber from the IMS server.
Suffix:
<UE>
.
1..5
Profile number of the subscriber to be deregistered
Example:
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
6.2.8.3
General Settings
The following commands configure basic IMS service settings.
CONFigure:DATA:CONTrol:IMS2:SUSage....................................................................... 178
CONFigure:DATA:CONTrol:IMS2:TRANsport:SELection....................................................179
CONFigure:DATA:CONTrol:IMS2:THReshold:VALue........................................................ 179
CONFigure:DATA:CONTrol:IMS2:EXTern:PCSCf:ADDRess:IPVFour..................................179
CONFigure:DATA:CONTrol:IMS2:EXTern:PCSCf:ADDRess:IPVSix....................................180
CONFigure:DATA:CONTrol:IMS2:SUSage <ServerUsage>
Selects whether the internal IMS server of the DAU or an external IMS network shall
be used for IMS services.
Parameters:
<ServerUsage>
INTernal | EXTernal
*RST:
178
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Example:
Firmware/Software: V3.5.10
Options:
Manual operation:
UDP
Firmware/Software: V3.5.21
Manual operation:
Example:
1 to 65535
1
Firmware/Software: V3.5.21
Manual operation:
CONFigure:DATA:CONTrol:IMS2:EXTern:PCSCf:ADDRess:IPVFour <IPv4Addr>
Specifies the IPv4 address of an external P-CSCF.
179
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<IPv4Addr>
Example:
'192.168.168.200'
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:EXTern:PCSCf:ADDRess:IPVSix <IPv6Addr>
Specifies the IPv6 address of an external P-CSCF.
Parameters:
<IPv6Addr>
Example:
'fcb1:cafe::200'
Firmware/Software: V3.5.10
Manual operation:
6.2.8.4
P-CSCF Settings
The following commands configure the simulated P-CSCFs.
CONFigure:DATA:CONTrol:IMS2:PCSCf:ADD..................................................................180
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:DELete........................................................ 181
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:IPADdress................................................... 181
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:BEHaviour................................................... 181
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:FAILurecode................................................ 181
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:RETRyafter.................................................. 182
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:REGexp.......................................................182
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:SUBexp....................................................... 183
CONFigure:DATA:CONTrol:IMS2:PCSCf:CREate............................................................. 183
SENSe:DATA:CONTrol:IMS2:PCSCf:CATalog?................................................................184
CONFigure:DATA:CONTrol:IMS2:PCSCf:ADD
Creates a new P-CSCF profile.
Example:
Usage:
Event
Firmware/Software: V3.5.10
Options:
R&S CMW-KAA21
Manual operation:
180
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:DELete
Deletes the P-CSCF profile number <p>.
Suffix:
<p>
.
3..10
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:IPADdress <IPAddress>
Defines the IP address of the P-CSCF number <p>.
Suffix:
<p>
Parameters:
<IPAddress>
Example:
.
1..10
IPv4 or IPv6 address string
Example: '172.22.1.201' or 'fc01:cafe::1/64'
See Configuring IMS Services
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:BEHaviour <Behaviour>
Defines the behavior of the P-CSCF number <p> when it receives a SIP message from
the mobile.
Suffix:
<p>
.
1..10
Parameters:
<Behaviour>
NORMal | FAILure
NORMal: normal behavior
FAILure: return failure code
*RST:
Example:
NORM
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:FAILurecode <FailureCode>
Defines a failure code for the P-CSCF number <p>, behavior = FAIL.
181
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Suffix:
<p>
Parameters:
<FailureCode>
.
1..10
BADRequest | FORBidden | NOTFound | INTerror |
UNAVailable | BUSYeveryw
BADRequest: 400 Bad Request
FORBidden: 403 Forbidden
NOTFound: 404 Not Found
INTerror: 500 Server Internal Error
UNAVailable: 503 Service Unavailable
BUSYeveryw: 600 Busy Everywhere
*RST:
Example:
BADR
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:RETRyafter <RetryAfter>
Defines the contents of the "Retry After" header field for the P-CSCF number <p>,
behavior = FAIL.
Suffix:
<p>
Parameters:
<RetryAfter>
Example:
.
1..10
*RST:
0s
Default unit: s
See Configuring IMS Services
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:REGexp <RegExpMin>,
<RegExpDefault>, <RegExpMax>
Defines registration expiration times for the P-CSCF number <p>.
Suffix:
<p>
.
1..10
Parameters:
<RegExpMin>
182
R&SCMW-B450A/B/D
Command Reference
Data Application Control
<RegExpDefault>
<RegExpMax>
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:SUBexp <SubsExpMin>,
<SubsExpDefault>, <SubsExpMax>
Defines subscription expiration times for the P-CSCF number <p>.
Suffix:
<p>
.
1..10
Parameters:
<SubsExpMin>
<SubsExpDefault>
<SubsExpMax>
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:PCSCf:CREate
Updates the internal list of P-CSCF profiles.
If your command script modifies any P-CSCF settings, you must insert this command
before you can use the modified profiles, for example for registration.
It is sufficient to insert the command once, after the last P-CSCF configuration command / before the profiles are used.
Example:
183
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
SENSe:DATA:CONTrol:IMS2:PCSCf:CATalog?
Queries a list of all P-CSCF profile names.
Return values:
<Catalog>
Example:
Usage:
Query only
Firmware/Software: V3.5.11
Manual operation:
6.2.8.5
Subscriber Settings
The following commands configure subscriber profiles for the tested mobiles.
CONFigure:DATA:CONTrol:IMS2:SUBScriber:ADD...........................................................184
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:DELete................................................. 185
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:PRIVateid............................................. 185
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:SCHeme........................... 185
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:ALGorithm.........................186
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:KEY..................................186
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:AMF................................. 186
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:OPC................................. 187
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:RESLength............................................187
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ENABle....................................... 187
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ALGorithm:INTegrity..................... 188
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ALGorithm:ENCRyption................ 188
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:PUBLicuserid<Index>.............................188
CONFigure:DATA:CONTrol:IMS2:SUBScriber:CREate...................................................... 189
SENSe:DATA:CONTrol:IMS2:SUBScriber:CATalog?.........................................................189
CONFigure:DATA:CONTrol:IMS2:SUBScriber:ADD
Creates a new subscriber profile.
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
184
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:DELete
Deletes the subscriber profile number <s>.
Suffix:
<s>
.
2..5
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:PRIVateid <PrivateId>
Specifies the private user ID of the subscriber profile number <s>.
Suffix:
<s>
.
1..5
Parameters:
<PrivateId>
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:SCHeme
<AuthScheme>
Specifies whether authentication shall be performed for the subscriber profile number
<s> and selects the authentication and key agreement version to be used.
Suffix:
<s>
.
1..5
Parameters:
<AuthScheme>
Example:
NOA
Firmware/Software: V3.5.10
Manual operation:
185
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:ALGorithm
<AuthKeyGenAlg>
Specifies which algorithm set is used for the subscriber profile number <s>.
Suffix:
<s>
.
1..5
Parameters:
<AuthKeyGenAlg>
XOR | MILenage
*RST:
Example:
MIL
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:KEY <AuthKey>
Defines the authentication key K for the subscriber profile number <s>.
Suffix:
<s>
.
1..5
Parameters:
<AuthKey>
Example:
'0x000102030405060708090a0b0c0d0e0f'
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:AMF <AuthAmf>
Specifies the Authentication Management Field (AMF) for the subscriber profile number <s>.
Suffix:
<s>
.
1..5
Parameters:
<AuthAmf>
Example:
'0x0000'
Firmware/Software: V3.5.10
Manual operation:
186
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:OPC <AuthOPc>
Specifies the key OPc for the subscriber profile number <s>.
Suffix:
<s>
.
1..5
Parameters:
<AuthOPc>
Example:
'0xcb9dcdc5b9258e6dca4760379fb82581'
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:RESLength <ResLength>
Specifies the length of the authentication response for the subscriber profile number
<s>.
Suffix:
<s>
Parameters:
<ResLength>
Example:
.
1..5
Range:
32 bit to 128 bit
*RST:
32 bit
Default unit: bit
See Configuring IMS Services
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ENABle <IPSec>
Enables or disables support of the IP security mechanisms by the IMS server for subscriber profile number <s>.
Suffix:
<s>
.
1..5
Parameters:
<IPSec>
OFF | ON
*RST:
Example:
OFF
Firmware/Software: V3.5.10
Manual operation:
187
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ALGorithm:INTegrity
<IntegrityAlg>
Selects an integrity protection algorithm for subscriber profile number <s>.
Suffix:
<s>
.
1..5
Parameters:
<IntegrityAlg>
HMMD | HMSH
HMMD: HMAC-MD5-96
HMSH: HMAC-SHA-1-96
*RST:
Example:
HMSH
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ALGorithm:ENCRyption
<EncryptionAlg>
Selects an encryption algorithm for subscriber profile number <s>.
Suffix:
<s>
.
1..5
Parameters:
<EncryptionAlg>
Example:
NOC
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:PUBLicuserid<Index>
<PublicUserIds>
Defines public user ID number <Index> for the subscriber profile number <s>.
Suffix:
<s>
.
1..5
<Index>
1..10
Parameters:
<PublicUserIds>
Example:
188
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:SUBScriber:CREate
Updates the internal list of subscriber profiles.
If your command script modifies any subscriber settings, you must insert this command
before you can use the modified profiles, for example for registration.
It is sufficient to insert the command once, after the last subscriber configuration command / before the profiles are used.
Example:
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
SENSe:DATA:CONTrol:IMS2:SUBScriber:CATalog?
Queries a list of all subscriber profile names.
Return values:
<Catalog>
Example:
Usage:
Query only
Firmware/Software: V3.5.11
Manual operation:
6.2.8.6
189
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AUDioboard.......................................... 195
CONFigure:DATA:CONTrol:IMS2:VIRTualsub:CREate...................................................... 195
SENSe:DATA:CONTrol:IMS2:VIRTualsub:CATalog?.........................................................195
CONFigure:DATA:CONTrol:IMS2:VIRTualsub:ADD
Creates a new virtual subscriber profile.
Example:
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:DELete
Deletes the virtual subscriber profile number <v>.
Suffix:
<v>
.
2..20
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:ID <ID>
Specifies the public user ID of the virtual subscriber number <v>.
Suffix:
<v>
.
1..20
Parameters:
<ID>
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:BEHaviour <Behaviour>
Defines the reaction of virtual subscriber number <v> to incoming calls.
Suffix:
<v>
.
1..20
190
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<Behaviour>
Example:
ANSW
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:SIGNalingtyp <SigType>
Specifies whether a voice call session with virtual subscriber number <v> is established with or without quality of service preconditions.
Suffix:
<v>
Parameters:
<SigType>
.
1..20
PRECondit | NOPRecondit | SIMPle | REQU100 |
REQuprecondi | WOTPrec183
PRECondit
With preconditions
NOPRecondit
Without preconditions
SIMPle
Simplified call flow, without preconditions
REQU100
Require 100rel, without preconditions
REQuprecondi
Require precondition, with preconditions
WOTPrec183
With 183, without preconditions
*RST:
Example:
NOPR
Firmware/Software: V3.5.10
V3.5.21: REQU100, REQuprecondi, WOTPrec183
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:BEARer <Bearer>
Enables the automatic setup of a dedicated bearer for calls of virtual subscriber number <v>.
191
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Suffix:
<v>
.
1..20
Parameters:
<Bearer>
OFF | ON
*RST:
Example:
OFF
Firmware/Software: V3.5.21
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AMR:TYPE <Type>
Selects the audio codec type for voice over IMS calls with virtual subscriber number
<v>: AMR NB, AMR WB or EVS.
Suffix:
<v>
.
1..20
Parameters:
<Type>
Example:
NARR
Firmware/Software: V3.5.10
V3.5.21: codec type EVS
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AMR:ALIGnment <AlignMode>
Selects the AMR voice codec alignment mode for voice over IMS calls with virtual subscriber number <v>.
Suffix:
<v>
.
1..20
Parameters:
<AlignMode>
OCTetaligned | BANDwidtheff
OCTetaligned: octet-aligned
BANDwidtheff: bandwidth-efficient
*RST:
Example:
OCT
Firmware/Software: V3.5.10
Manual operation:
192
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AMR:CODec<CodecIdx>:
ENABle <CodecRate>
Enables or disables a codec rate for the currently active AMR type of virtual subscriber
number <v>, see CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AMR:
ALIGnment.
Suffix:
<v>
.
1..20
<CodecIdx>
1..9
Selects the codec rate via its index.
Parameters:
<CodecRate>
OFF | ON
OFF: codec rate not supported
ON: codec rate supported
*RST:
Example:
OFF
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:VIDeo:CODec <Codec>
Selects the codec for video calls of virtual subscriber number <v>.
Suffix:
<v>
.
1..20
Parameters:
<Codec>
H263 | H264
H.263 or H.264 codec
*RST:
Example:
H263
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:VIDeo:ATTRibutes <Attributes>
Configures codec attributes for video calls of virtual subscriber number <v>.
Suffix:
<v>
.
1..20
Parameters:
<Attributes>
Example:
193
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MEDiaendpoin <MediaEndpoint>
Configures the media endpoint for virtual subscriber number <v>.
Suffix:
<v>
.
1..20
Parameters:
<MediaEndpoint>
Example:
LOOP
Firmware/Software: V3.5.10
Manual operation:
.
1..20
Parameters:
<IPAddress>
<Port>
<CmdPort>
1000
<AMRAlign>
'172.22.2.2'
1000
OCTetaligned | BANDwidtheff
AMR alignment mode used by the media endpoint
OCTetaligned: octet-aligned
BANDwidtheff: bandwidth-efficient
*RST:
BAND
Firmware/Software: V3.5.10
Manual operation:
194
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AUDioboard <Instance>,
<DTXEnable>, <ForceModeNB>, <ForceModeWB>
Configures the audio board for virtual subscriber number <v>.
Suffix:
<v>
.
1..20
Parameters:
<Instance>
INST1
For future use
*RST:
<DTXEnable>
INST1
OFF | ON
Enable comfort noise in the downlink
*RST:
<ForceModeNB>
OFF
<ForceModeWB>
FREE
Example:
FREE
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub:CREate
Updates the internal list of virtual subscriber profiles.
If your command script modifies any virtual subscriber settings, you must insert this
command before you can use the modified profiles, for example for call setup.
It is sufficient to insert the command once, after the last virtual subscriber configuration
command / before the profiles are used.
Example:
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
SENSe:DATA:CONTrol:IMS2:VIRTualsub:CATalog?
Queries a list of all virtual subscriber profile names.
195
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Return values:
<Catalog>
Example:
Usage:
Query only
Firmware/Software: V3.5.11
Manual operation:
6.2.8.7
Mobile-Terminating Calls
The following commands configure and control mobile-terminating voice over IMS
calls.
SENSe:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:DESTination:LIST?........................... 196
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:DESTination...............................196
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:TYPE........................................ 197
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:SIGType.................................... 197
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:BEARer..................................... 198
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:TYPE................................ 198
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:ALIGnment........................ 199
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:CODec<CodecIdx>:
ENABle...............................................................................................................199
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:VIDeo:CODec............................ 199
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:VIDeo:ATTRibutes...................... 200
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:CALL.........................................200
SENSe:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:DESTination:LIST?
Queries a list of all possible destination strings for mobile-terminating calls.
Suffix:
<v>
.
1..20
Return values:
<Destinations>
Example:
Usage:
Query only
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:DESTination
<Destination>
Specifies the destination to be called by virtual subscriber number <v>.
To query a list of all possible destination strings, see SENSe:DATA:CONTrol:IMS2:
VIRTualsub<v>:MTCall:DESTination:LIST? on page 196.
196
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Suffix:
<v>
.
1..20
Parameters:
<Destination>
Destination string
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:TYPE <Type>
Selects the type of call to be initiated by virtual subscriber <v>: audio call or video call.
Suffix:
<v>
.
1..20
Parameters:
<Type>
AUDio | VIDeo
*RST:
Example:
AUD
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:SIGType <SigType>
Specifies whether a mobile-terminating call from virtual subscriber number <v> is
established with or without quality of service preconditions.
Suffix:
<v>
.
1..20
197
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<SigType>
NOPR
Firmware/Software: V3.5.10
V3.5.21: REQU100, REQuprecondi, WOTPrec183
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:BEARer <Bearer>
Enables the automatic setup of a dedicated bearer, if a voice over IMS call is established for virtual subscriber number <v>.
Suffix:
<v>
.
1..20
Parameters:
<Bearer>
OFF | ON
*RST:
OFF
Firmware/Software: V3.5.21
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:TYPE <Type>
Selects the audio codec type for mobile-terminating calls from virtual subscriber number <v>.
Suffix:
<v>
.
1..20
Parameters:
<Type>
Firmware/Software: V3.5.10
V3.5.21: codec type EVS
198
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:ALIGnment
<AlignmentMode>
Selects the AMR voice codec alignment mode for mobile-terminating calls from virtual
subscriber number <v>.
Suffix:
<v>
.
1..20
Parameters:
<AlignmentMode>
OCTetaligned | BANDwidtheff
OCTetaligned: octet-aligned
BANDwidtheff: bandwidth-efficient
*RST:
OCT
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:
CODec<CodecIdx>:ENABle <CodecRate>
Enables or disables a codec rate for mobile-terminating calls from virtual subscriber
number <v>.
The rate applies to the currently active AMR type, see CONFigure:DATA:CONTrol:
IMS2:VIRTualsub<v>:MTCall:AMR:TYPE.
Suffix:
<v>
.
1..20
<CodecIdx>
1..9
Selects the codec rate via its index.
Parameters:
<CodecRate>
OFF | ON
OFF: codec rate not supported
ON: codec rate supported
*RST:
OFF
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:VIDeo:CODec <Codec>
Selects the codec for mobile-terminating video calls of virtual subscriber number <v>.
Suffix:
<v>
.
1..20
199
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<Codec>
H263 | H264
H.263 or H.264 codec
*RST:
H263
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:VIDeo:ATTRibutes
<Attributes>
Configures codec attributes for mobile-terminating video calls of virtual subscriber
number <v>.
Suffix:
<v>
.
1..20
Parameters:
<Attributes>
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:CALL
Initiates the setup of a voice over IMS call, from virtual subscriber number <v> to the
mobile.
Suffix:
<v>
.
1..20
Example:
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
6.2.8.8
Short Messages
The following commands configure and control mobile-terminating short messages.
SENSe:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:DESTination:LIST?.......................... 200
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:DESTination..............................201
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:TYPE........................................201
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:TEXT........................................202
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:SEND....................................... 202
SENSe:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:DESTination:LIST?
Queries a list of all possible destination strings for mobile-terminating short messages.
200
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Suffix:
<v>
.
1..20
Return values:
<Destinations>
Example:
Usage:
Query only
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:DESTination
<Destination>
Specifies the destination to which short messages shall be sent by virtual subscriber
number <v>.
To query a list of all possible destination strings, see SENSe:DATA:CONTrol:IMS2:
VIRTualsub<v>:MTSMs:DESTination:LIST? on page 200.
Suffix:
<v>
.
1..20
Parameters:
<Destination>
Destination string
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:TYPE <Type>
Selects the message type for short messages to be sent by virtual subscriber number
<v>.
Suffix:
<v>
.
1..20
Parameters:
<Type>
Example:
GPP
Firmware/Software: V3.5.10
Manual operation:
201
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:TEXT <Text>
Defines the message text for short messages to be sent by virtual subscriber number
<v>.
Suffix:
<v>
.
1..20
Parameters:
<Text>
Example:
Firmware/Software: V3.5.10
Manual operation:
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:SEND
Initiates a short message transfer from virtual subscriber number <v> to the mobile.
Suffix:
<v>
.
1..20
Example:
Usage:
Event
Firmware/Software: V3.5.10
Manual operation:
6.2.9.1
202
R&SCMW-B450A/B/D
Command Reference
Data Application Control
SENSe:DATA:CONTrol:EPDG:CONNections:IMSI?
Queries all IMSIs for which ePDG connections are established.
Return values:
<IMSI>
Usage:
Firmware/Software: V3.5.20
6.2.9.2
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:ADDRess:IPVFour <IPv4Address>
Specifies the IPv4 address of the ePDG.
Parameters:
<IPv4Address>
Example:
'192.168.1.201'
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:ADDRess:IPVSix <IPv6Address>
Specifies the IPv6 address of the ePDG.
Parameters:
<IPv6Address>
Example:
'fc01::1'
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
203
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Manual operation:
CONFigure:DATA:CONTrol:EPDG:ID:TYPE <IDType>
Configures the type of the ePDG identification.
Parameters:
<IDType>
Example:
FQDN
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:ID:VALue <IDValue>
Configures the value of the ePDG identification.
Parameters:
<IDValue>
Identification as string
*RST:
Example:
'Epdg.rs.org'
Firmware/Software: V3.5.20
6.2.9.3
Options:
R&S CMW-KA065
Manual operation:
IKE Settings
The following commands configure settings for the IKEv2 protocol.
CONFigure:DATA:CONTrol:EPDG:IKE:ENCRyption..........................................................204
CONFigure:DATA:CONTrol:EPDG:IKE:PRF..................................................................... 205
CONFigure:DATA:CONTrol:EPDG:IKE:INTegrity.............................................................. 205
CONFigure:DATA:CONTrol:EPDG:IKE:DHGRoup.............................................................206
CONFigure:DATA:CONTrol:EPDG:IKE:ENCRyption <AESCBC>
Selects the supported encryption algorithms for the IKEv2 protocol.
Currently, only "ENCR_AES_CBC" (CBC) is possible.
204
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<AESCBC>
OFF | ON
*RST:
Example:
OFF
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
OFF | ON
PRF_HMAC_MD5
*RST:
<PRFSHA1>
OFF
OFF | ON
PRF_HMAC_SHA1
*RST:
Example:
OFF
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:IKE:INTegrity <HMAC_MD5_96>,
<HMAC_SHAI_96>, <AES_XCB_96>
Selects the supported integrity protection algorithms for the IKEv2 protocol.
Parameters:
<HMAC_MD5_96>
OFF | ON
AUTH_HMAC_MD5_96
*RST:
<HMAC_SHAI_96>
OFF
OFF | ON
AUTH_HMAC_SHA1_96
*RST:
<AES_XCB_96>
OFF
OFF | ON
AUTH_AES_XCBC_96
*RST:
Example:
OFF
Firmware/Software: V3.5.20
205
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Options:
R&S CMW-KA065
Manual operation:
OFF | ON
*RST:
<DHGroup2>
OFF | ON
*RST:
<DHGroup5>
OFF
OFF | ON
*RST:
Example:
OFF
OFF | ON
*RST:
<DHGroup14>
OFF
OFF
Firmware/Software: V3.5.20
6.2.9.4
Options:
R&S CMW-KA065
Manual operation:
ESP Settings
The following commands configure settings for the ESP protocol.
CONFigure:DATA:CONTrol:EPDG:ESP:ENCRyption........................................................ 206
CONFigure:DATA:CONTrol:EPDG:ESP:INTegrity............................................................. 207
CONFigure:DATA:CONTrol:EPDG:ESP:ENCRyption <AESCBC>
Selects the supported encryption algorithms for the ESP protocol.
Currently, only "ENCR_AES_CBC" (CBC) is supported.
Parameters:
<AESCBC>
OFF | ON
*RST:
Example:
OFF
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
206
R&SCMW-B450A/B/D
Command Reference
Data Application Control
OFF | ON
AUTH_HMAC_MD5_96
*RST:
<SHAI96>
OFF
OFF | ON
AUTH_HMAC_SHA1_96
*RST:
<XCBC96>
OFF
OFF | ON
AUTH_AES_XCBC_96
*RST:
Example:
OFF
Firmware/Software: V3.5.20
6.2.9.5
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVFour:TYPE <PCSCFIPV4TYP>
Sets the attribute type field of the P_CSCF_IP4_ADDRESS configuration attribute.
Parameters:
<PCSCFIPV4TYP>
Example:
Range:
*RST:
0 to 65535
20
Firmware/Software: V3.5.21
Manual operation:
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVSix:TYPE <PCSCFIPV6TYP>
Sets the attribute type field of the P_CSCF_IP6_ADDRESS configuration attribute.
207
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<PCSCFIPV6TYP>
Example:
Range:
*RST:
0 to 65535
21
Firmware/Software: V3.5.21
Manual operation:
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVSix:ADDRess:LENGth
<IPVSixADDLGH>
Sets the length field of the P_CSCF_IP6_ADDRESS configuration attribute.
Parameters:
<IPVSixADDLGH>
L16 | L17
*RST:
Example:
L16
Firmware/Software: V3.5.21
Manual operation:
6.2.9.6
Authentication Settings
The following commands configure settings for the authentication procedure.
CONFigure:DATA:CONTrol:EPDG:AUTHentic:IMSI.......................................................... 208
CONFigure:DATA:CONTrol:EPDG:AUTHentic:ALGorithm..................................................209
CONFigure:DATA:CONTrol:EPDG:AUTHentic:KEY...........................................................209
CONFigure:DATA:CONTrol:EPDG:AUTHentic:RAND........................................................ 209
CONFigure:DATA:CONTrol:EPDG:AUTHentic:AMF.......................................................... 209
CONFigure:DATA:CONTrol:EPDG:AUTHentic:KEY:TYPE................................................. 210
CONFigure:DATA:CONTrol:EPDG:AUTHentic:OPC.......................................................... 210
CONFigure:DATA:CONTrol:EPDG:AUTHentic:IMSI <AuthIMSI>
Specifies the IMSI of the SIM card.
Parameters:
<AuthIMSI>
Example:
'001010123456789'
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
208
R&SCMW-B450A/B/D
Command Reference
Data Application Control
CONFigure:DATA:CONTrol:EPDG:AUTHentic:ALGorithm <AuthAlg>
Specifies the key generation algorithm set used by the SIM.
Parameters:
<AuthAlg>
XOR | MILenage
*RST:
Example:
XOR
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:KEY <AuthKey>
Defines the secret key K as 32-digit hexadecimal number. Leading zeros may be omitted.
Parameters:
<AuthKey>
Range:
*RST:
Example:
#H0 to
#HFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
#H000102030405060708090A0B0C0D0E0F
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:RAND <AuthRAND>
Defines the random number RAND as 32-digit hexadecimal number. Leading zeros
may be omitted.
Parameters:
<AuthRAND>
Range:
*RST:
Example:
#H0 to
#HFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
#H55555555555555555555555555555555
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:AMF <AuthAMF>
Specifies the Authentication Management Field (AMF) as 4-digit hexadecimal number.
Leading zeros may be omitted.
209
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<AuthAMF>
Example:
Range:
*RST:
#H0 to #HFFFF
#H0000
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:KEY:TYPE <AuthKeyType>
Selects the key type to be used with the MILENAGE algorithm set.
Currently, only OPc is supported.
Parameters:
<AuthKeyType>
OPC
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:AUTHentic:OPC <AuthOPC>
Specifies the key OPc as 32-digit hexadecimal number. Leading zeros may be omitted.
Parameters:
<AuthOPC>
Range:
*RST:
Example:
#H00000000000000000000000000000000 to
#HFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
#HCD63CB71954A9F4E48A5994E37A02BAF
Firmware/Software: V3.5.20
6.2.9.7
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:DPD:ENABle <DPDENABLE>
Enables dead peer detection.
210
R&SCMW-B450A/B/D
Command Reference
Data Application Control
Parameters:
<DPDENABLE>
OFF | ON
*RST:
Example:
OFF
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:DPD:INTerval <DPDInterval>
Configures the inactivity time interval for dead peer detection.
Parameters:
<DPDInterval>
Example:
Range:
1 s to 100 s
*RST:
1s
Default unit: s
See Configuring the ePDG Service
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:DPD:TIMeout <DPDTimeout>
Configures the no answer timeout for dead peer detection.
Parameters:
<DPDTimeout>
Example:
Range:
1 s to 10E+3 s
*RST:
10 s
Default unit: s
See Configuring the ePDG Service
Firmware/Software: V3.5.20
6.2.9.8
Options:
R&S CMW-KA065
Manual operation:
Certificate Settings
The following commands configure settings related to SSL certificates.
CONFigure:DATA:CONTrol:EPDG:CERTificate:ENABle.................................................... 212
CONFigure:DATA:CONTrol:EPDG:CERTificate:KEY......................................................... 212
CONFigure:DATA:CONTrol:EPDG:CERTificate:CERTificate.............................................. 212
211
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
CONFigure:DATA:CONTrol:EPDG:CERTificate:ENABle <CertificateEnable>
Enables the usage of certificates for SSL.
Parameters:
<CertificateEnable>
OFF | ON
*RST:
Example:
OFF
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:CERTificate:KEY <CertificateKeyFile>
Selects the server key file to be used for SSL.
Parameters:
<CertificateKeyFile> Filename as string, without path
Example:
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
CONFigure:DATA:CONTrol:EPDG:CERTificate:CERTificate <CertificateFile>
Selects the server certificate file to be used for SSL.
Parameters:
<CertificateFile>
Example:
Firmware/Software: V3.5.20
Options:
R&S CMW-KA065
Manual operation:
RAN Selection.......................................................................................................213
Ping Measurement................................................................................................ 213
IPerf Measurement................................................................................................218
Throughput Measurement.....................................................................................227
212
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
CONFigure:DATA:MEAS<i>:RAN <RAN>
Selects an installed signaling application instance. A complete list of all supported values can be displayed using CONFigure:DATA:MEAS<i>:RAN:CATaloge?.
Parameters:
<RAN>
Example:
Firmware/Software: V1.0.15.20
Manual operation:
CONFigure:DATA:MEAS<i>:RAN:CATaloge?
Lists all signaling applications that can be selected using CONFigure:DATA:
MEAS<i>:RAN.
Return values:
<RAN>
Comma separated list of all supported values. Each value is represented as a string.
Example:
Usage:
Query only
Firmware/Software: V1.0.15.20
Manual operation:
213
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
CONFigure:DATA:MEAS<i>:PING:DIPaddress................................................................. 214
CONFigure:DATA:MEAS<i>:PING:INTerval......................................................................214
CONFigure:DATA:MEAS<i>:PING:TIMeout...................................................................... 214
CONFigure:DATA:MEAS<i>:PING:PSIZe......................................................................... 215
CONFigure:DATA:MEAS<i>:PING:PCOunt.......................................................................215
INITiate:DATA:MEAS<i>:PING........................................................................................ 215
STOP:DATA:MEAS<i>:PING.......................................................................................... 215
ABORt:DATA:MEAS<i>:PING......................................................................................... 215
FETCh:DATA:MEAS<i>:PING:STATe?............................................................................ 216
FETCh:DATA:MEAS<i>:PING:STATe:ALL?......................................................................216
FETCh:DATA:MEAS<i>:PING?....................................................................................... 217
READ:DATA:MEAS<i>:PING?.........................................................................................217
FETCh:DATA:MEAS<i>:PING:OVERall?.......................................................................... 218
FETCh:DATA:MEAS<i>:PING:NRCount?......................................................................... 218
CONFigure:DATA:MEAS<i>:PING:DIPaddress <IPAddress>
Specifies the destination IP address for the ping command.
Parameters:
<IPAddress>
Example:
'172.22.1.100'
Firmware/Software: V1.0.15.20
Manual operation:
CONFigure:DATA:MEAS<i>:PING:INTerval <Interval>
Specifies the interval between two ping requests.
Parameters:
<Interval>
Example:
Range:
0.2 s to 10 s
*RST:
1s
Default unit: s
See Performing a Ping Measurement
Firmware/Software: V1.0.15.20
Manual operation:
CONFigure:DATA:MEAS<i>:PING:TIMeout <Timeout>
Specifies a timeout for ping requests.
Parameters:
<Timeout>
Example:
Range:
1 s to 9 s
*RST:
2s
Default unit: s
See Performing a Ping Measurement
214
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Firmware/Software: V3.2.20
Manual operation:
CONFigure:DATA:MEAS<i>:PING:PSIZe <PacketSize>
Specifies the payload size of echo request packets.
Parameters:
<PacketSize>
Example:
Range:
0 byte to 65507 byte
*RST:
100 byte
Default unit: byte
See Performing a Ping Measurement
Firmware/Software: V1.0.15.20
V3.0.10: range and *RST value changed
Manual operation:
CONFigure:DATA:MEAS<i>:PING:PCOunt <PingCount>
Specifies the number of echo request packets to be sent.
Parameters:
<PingCount>
Example:
Range:
*RST:
1 to 1000
100
Firmware/Software: V1.0.15.20
Manual operation:
INITiate:DATA:MEAS<i>:PING
STOP:DATA:MEAS<i>:PING
ABORt:DATA:MEAS<i>:PING
Starts, stops, or aborts the measurement:
STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. Allocated resources remain allocated to the
measurement.
215
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Usage:
Event
Firmware/Software: V1.0.15.20
Manual operation:
FETCh:DATA:MEAS<i>:PING: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:
<MeasState>
OFF
Example:
Usage:
Query only
Firmware/Software: V1.0.15.20
Manual operation:
FETCh:DATA:MEAS<i>:PING:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measurement substates are relevant for running measurements only. Use
FETCh:...:STATe? to query the main measurement state only. Use INITiate...,
STOP..., ABORt... to change the measurement state.
Return values:
<MainState>
OFF
216
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<SyncState>
<ResourceState>
Usage:
Query only
Firmware/Software: V1.0.15.20
Manual operation:
FETCh:DATA:MEAS<i>:PING?
READ:DATA:MEAS<i>:PING?
Queries the measured ping characteristics.
After the reliability indicator, three results are returned for each ping request:
<Reliability>, {<ReqNo>, <Timestamp>, <Latency>}request 1, {...}request 2, ...
The number of ping requests is specified by CONFigure:DATA:MEAS<i>:PING:
PCOunt.
Return values:
<Reliability>
<ReqNo>
-1000 to 0
<Timestamp>
<Latency>
Example:
Usage:
Query only
Firmware/Software: V1.0.15.20
V3.0.10: latency unit changed from ms to s
Manual operation:
217
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
FETCh:DATA:MEAS<i>:PING:OVERall?
Query the statistical ping results over all ping requests.
Return values:
<Reliability>
<MinPing>
<MaxPing>
<AveragePing>
Example:
Usage:
Query only
Firmware/Software: V3.2.11
Manual operation:
FETCh:DATA:MEAS<i>:PING:NRCount?
Queries the number of ping requests that have not been answered (no reply).
Return values:
<ReqNo>
Range:
Example:
Usage:
Query only
0 to 1000
Firmware/Software: V3.0.10
Manual operation:
218
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PROTocol............................................ 221
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PORT.................................................. 222
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:IPADdress............................................222
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:WSIZe................................................. 222
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PCONnection........................................223
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:BITRate............................................... 223
INITiate:DATA:MEAS<i>:IPERf....................................................................................... 223
STOP:DATA:MEAS<i>:IPERf.......................................................................................... 223
ABORt:DATA:MEAS<i>:IPERf.........................................................................................223
FETCh:DATA:MEAS<i>:IPERf:STATe?............................................................................224
FETCh:DATA:MEAS<i>:IPERf:STATe:ALL?..................................................................... 224
FETCh:DATA:MEAS<i>:IPERf:SERVer?.......................................................................... 225
READ:DATA:MEAS<i>:IPERf:SERVer?........................................................................... 225
FETCh:DATA:MEAS<i>:IPERf:CLIent?............................................................................ 226
READ:DATA:MEAS<i>:IPERf:CLIent?..............................................................................226
FETCh:DATA:MEAS<i>:IPERf:ALL?................................................................................ 226
CONFigure:DATA:MEAS<i>:IPERf:TDURation <TestDuration>
Defines the time the test should last.
Parameters:
<TestDuration>
Example:
Range:
1 s to 1E+6 s
*RST:
1000 s
Default unit: s
See Performing an IPerf Measurement
Firmware/Software: V1.0.15.20
Manual operation:
CONFigure:DATA:MEAS<i>:IPERf:PSIZe <PacketSize>
Defines the packet size for IPerf tests.
Parameters:
<PacketSize>
Example:
Range:
40 byte to 65507 byte
*RST:
1470 byte
Default unit: byte
See Performing an IPerf Measurement
Firmware/Software: V3.2.20
Manual operation:
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:ENABle <Enable>
Activates or deactivates an IPerf server instance.
219
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Suffix:
<Index>
Parameters:
<Enable>
.
1..8
Selects the server instance
OFF | ON
*RST:
Example:
Firmware/Software: V2.0.20
Manual operation:
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:PROTocol <Protocol>
Selects the protocol type to be used for an IPerf server instance.
Suffix:
<Index>
Parameters:
<Protocol>
.
1..8
Selects the server instance
UDP | TCP
UDP: use the User Datagram Protocol for data transfer
TCP: use the Transport Control Protocol for data transfer
*RST:
Example:
TCP
Firmware/Software: V2.0.20
Manual operation:
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:PORT <Port>
Defines the LAN DAU port number for an IPerf server instance.
Suffix:
<Index>
Parameters:
<Port>
Example:
.
1..8
Selects the server instance
Range:
*RST:
0 to 65535
5001 to 5008 for instance 1 to 8
Firmware/Software: V2.0.20
Manual operation:
220
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:WSIZe <WindowSize>
Specifies the size of the NACK window for an IPerf server instance. Only applicable for
protocol type TCP.
Suffix:
<Index>
Parameters:
<WindowSize>
Example:
.
1..8
Selects the server instance
Range:
0 kByte to 10.24E+3 kByte
*RST:
0 kByte
Default unit: kByte
See Performing an IPerf Measurement
Firmware/Software: V2.0.20
Manual operation:
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:ENABle <Enable>
Activates or deactivates an IPerf client instance.
Suffix:
<Index>
Parameters:
<Enable>
.
1..8
Selects the client instance
OFF | ON
*RST:
Example:
Firmware/Software: V2.0.20
Manual operation:
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PROTocol <Protocol>
Selects the protocol type to be used for an IPerf client instance.
Suffix:
<Index>
Parameters:
<Protocol>
.
1..8
Selects the client instance
UDP | TCP
UDP: use the User Datagram Protocol for data transfer
TCP: use the Transport Control Protocol for data transfer
*RST:
Example:
TCP
Firmware/Software: V2.0.20
221
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Manual operation:
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PORT <Port>
Defines the LAN DAU port number for an IPerf client instance.
Suffix:
<Index>
Parameters:
<Port>
Example:
.
1..8
Selects the client instance
Range:
*RST:
0 to 65535
5001 to 5008 for instance 1 to 8
Firmware/Software: V2.0.20
Manual operation:
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:IPADdress <IPAddress>
Specifies the IP address of the mobile for an IPerf client instance.
Suffix:
<Index>
Parameters:
<IPAddress>
.
1..8
Selects the client instance
String containing the IP address
*RST:
Example:
'172.22.1.100'
Firmware/Software: V2.0.20
Manual operation:
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:WSIZe <WindowSize>
Specifies the size of the NACK window for an IPerf client instance. Only applicable for
protocol type TCP.
Suffix:
<Index>
Parameters:
<WindowSize>
Example:
.
1..8
Selects the client instance
Range:
0 kByte to 10.24E+3 kByte
*RST:
0 kByte
Default unit: kByte
See Performing an IPerf Measurement
Firmware/Software: V2.0.20
222
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Manual operation:
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PCONnection <ParConn>
Specifies the number of parallel connections for an IPerf client instance. Only applicable for protocol type TCP.
Suffix:
<Index>
Parameters:
<ParConn>
Example:
.
1..8
Selects the client instance
Range:
*RST:
1 to 4
1
Firmware/Software: V2.0.20
Manual operation:
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:BITRate <BitRate>
Defines the maximum bit rate for an IPerf client instance. Only applicable for protocol
type UDP.
Suffix:
<Index>
Parameters:
<BitRate>
.
1..8
Selects the client instance
Maximum bit rate to be transferred
Range:
0 bit/s to 1E+9 bit/s
*RST:
1 bit/s
Default unit: bit/s
Example:
Firmware/Software: V2.0.20
Manual operation:
INITiate:DATA:MEAS<i>:IPERf
STOP:DATA:MEAS<i>:IPERf
ABORt:DATA:MEAS<i>:IPERf
Starts, stops, or aborts the measurement:
STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. Allocated resources remain allocated to the
measurement.
223
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Usage:
Event
Firmware/Software: V1.0.15.20
Manual operation:
FETCh:DATA:MEAS<i>:IPERf: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:
<MeasState>
Usage:
OFF
Query only
Firmware/Software: V1.0.15.20
Manual operation:
FETCh:DATA:MEAS<i>:IPERf:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measurement substates are relevant for running measurements only. Use
FETCh:...:STATe? to query the main measurement state only. Use INITiate...,
STOP..., ABORt... to change the measurement state.
224
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Return values:
<MainState>
<SyncState>
OFF
<ResourceState>
Usage:
Query only
Firmware/Software: V1.0.15.20
Manual operation:
FETCh:DATA:MEAS<i>:IPERf:SERVer?
READ:DATA:MEAS<i>:IPERf:SERVer?
Queries the uplink throughput for all server instances.
Return values:
<Reliability>
<UpBandwidth>
Example:
Usage:
Query only
Firmware/Software: V2.0.20
Manual operation:
225
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
FETCh:DATA:MEAS<i>:IPERf:CLIent?
READ:DATA:MEAS<i>:IPERf:CLIent?
Queries the downlink throughput for all client instances.
Return values:
<Reliability>
<DownBandwidth>
Example:
Usage:
Query only
Firmware/Software: V2.0.20
Manual operation:
FETCh:DATA:MEAS<i>:IPERf:ALL?
Queries all client and server results of the IPerf measurement.
For each server/client instance five results are returned, from instance 1 to instance 8:
<Reliability>, {<ServerCounter>, <ClientCounter>, <UpBandwidth>, <PackErrRate>,
<DownBandwidth>}instance 1, {...}instance 2, ..., {...}instance 8
IPerf results are usually queried within a loop, in order to monitor the results over some
time. IPerf delivers new results once per second. If your loop is faster, several consecutive queries deliver the same results. Use the <ServerCounter> and <ClientCounter>
to identify redundant results and discard them.
Return values:
<Reliability>
<ServerResultCounter>
Counter for server results
The first result delivered by IPerf is labeled 0, the second result
1, and so on.
<ClientResultCounter>Counter for client results
The first result delivered by IPerf is labeled 0, the second result
1, and so on.
<UpBandwidth>
<PackErrRate>
Percentage of lost packets, determined for active server instances with protocol type UDP
Range:
0 % to 100 %
Default unit: %
<DownBandwidth>
Example:
226
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Usage:
Query only
Firmware/Software: V3.2.20
Manual operation:
SENSe:DATA:MEAS<i>:THRoughput:INTerval?
Queries the time interval between two throughput measurement results.
Return values:
<Interval>
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:MEAS<i>:THRoughput:MCOunt <MaxCount>
Specifies the total number of throughput results to be measured.
227
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Parameters:
<MaxCount>
Example:
Range:
*RST:
5 to 3600
5
Firmware/Software: V2.0.10
V3.0.10: Range and *RST value changed
Manual operation:
INITiate:DATA:MEAS<i>:THRoughput
STOP:DATA:MEAS<i>:THRoughput
ABORt:DATA:MEAS<i>:THRoughput
Starts, stops, or aborts the measurement:
STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. Allocated resources remain allocated to the
measurement.
Usage:
Event
Firmware/Software: V2.0.10
Manual operation:
FETCh:DATA:MEAS<i>:THRoughput: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.
228
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Return values:
<MeasState>
OFF
Example:
Usage:
Query only
Firmware/Software: V2.0.10
Manual operation:
FETCh:DATA:MEAS<i>:THRoughput:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measurement substates are relevant for running measurements only. Use
FETCh:...:STATe? to query the main measurement state only. Use INITiate...,
STOP..., ABORt... to change the measurement state.
Return values:
<MainState>
<SyncState>
OFF
<ResourceState>
Usage:
Query only
229
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Firmware/Software: V2.0.10
Manual operation:
FETCh:DATA:MEAS<i>:THRoughput:TRACe:OVERall:ULINk[:CURRent]?
FETCh:DATA:MEAS<i>:THRoughput:TRACe:OVERall:DLINk[:CURRent]?
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:ULINk[:CURRent]?
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:DLINk[:CURRent]?
Query the values of the overall throughput trace in uplink (ULINk) or downlink (DLINk)
direction.
The trace values are returned from left to right (first to last measurement), one result
per interval, see CONFigure:DATA:MEAS<i>:THRoughput:MCOunt on page 227.
Return values:
<Reliability>
<Results>
Example:
Usage:
Query only
Firmware/Software: V2.0.10
Manual operation:
FETCh:DATA:MEAS<i>:THRoughput:TRACe:OVERall:ULINk:EXTended?
FETCh:DATA:MEAS<i>:THRoughput:TRACe:OVERall:DLINk:EXTended?
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:ULINk:EXTended?
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:DLINk:EXTended?
Query the values of the overall throughput trace in uplink (ULINk) or downlink (DLINk)
direction.
The trace values are returned from left to right (first to last measurement). There are
two values per interval:
<Reliability>, {<Counter>, <Result>}interval 1, {...}interval 2, ..., {...}interval n
The counter is useful if you want to perform repeated queries and combine the
returned result traces.
To configure the number of intervals, see CONFigure:DATA:MEAS<i>:
THRoughput:MCOunt on page 227.
Return values:
<Reliability>
<Counter>
230
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<Result>
Range:
0 bit/s to 150E+6 bit/s
Default unit: bit/s
Usage:
Query only
Firmware/Software: V3.5.21
Manual operation:
FETCh:DATA:MEAS<i>:THRoughput:OVERall:ULINk?
READ:DATA:MEAS<i>:THRoughput:OVERall:ULINk?
Query the statistical results of the throughput measurement in uplink direction.
Return values:
<Reliability>
<ThCurrUpLink>
Current throughput
Range:
<ThMinUpLink>
Minimum throughput
Range:
<ThMaxUpLink>
Maximum throughput
Range:
<ThAvgUpLink>
Average throughput
Range:
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
FETCh:DATA:MEAS<i>:THRoughput:OVERall:DLINk?
READ:DATA:MEAS<i>:THRoughput:OVERall:DLINk?
Query the statistical results of the throughput measurement in downlink direction.
Return values:
<Reliability>
<ThCurrDLink>
Current throughput
Range:
0 bit/s to 150E+6 bit/s
Default unit: bit/s
<ThMinDLink>
Minimum throughput
Range:
0 bit/s to 150E+6 bit/s
Default unit: bit/s
<ThMaxDLink>
Maximum throughput
Range:
0 bit/s to 150E+6 bit/s
Default unit: bit/s
231
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<ThAvgDLink>
Average throughput
Range:
0 bit/s to 150E+6 bit/s
Default unit: bit/s
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:MEASurement<inst>:DNSRequests:MICount <MaxIndexCount>
Specifies the maximum length of the result list for "DNS Requests" measurements.
The result list is stored in a ring buffer. When it is full, the first result line is deleted
whenever a new result line is added to the end.
Parameters:
<MaxIndexCount>
Example:
1 to 1000
1000
Firmware/Software: V3.0.10
Manual operation:
INITiate:DATA:MEAS<i>:DNSRequests
STOP:DATA:MEAS<i>:DNSRequests
ABORt:DATA:MEAS<i>:DNSRequests
Starts, stops, or aborts the measurement:
232
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. Allocated resources remain allocated to the
measurement.
Usage:
Event
Firmware/Software: V3.0.10
Manual operation:
FETCh:DATA:MEAS<i>:DNSRequests: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:
<MeasState>
Usage:
OFF
Query only
Firmware/Software: V3.0.10
Manual operation:
FETCh:DATA:MEAS<i>:DNSRequests:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measurement substates are relevant for running measurements only. Use
FETCh:...:STATe? to query the main measurement state only. Use INITiate...,
STOP..., ABORt... to change the measurement state.
233
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Return values:
<MainState>
<SyncState>
OFF
<ResourceState>
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:MEAS<i>:DNSRequests:RCOunt?
Queries the number of already monitored DNS requests.
Return values:
<ReqCount>
Number of requests
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
SENSe:DATA:MEAS<i>:DNSRequests?
Queries information about the monitored DNS requests.
After the reliability indicator, four results are returned for each DNS request:
<Reliability>, {<ClientIP>, <URL>, <IP>, <Timestamp>}request 1, {...}request 2, ...
234
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<ClientIP>
<URL>
<IP>
<Timestamp>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
6.3.6 IP Logging
The commands in this section are related to the IP logging application. They configure
and control IP logging and return the current state of the application.
CONFigure:DATA:MEAS<i>:IPLogging:TYPE...................................................................235
SENSe:DATA:MEAS<i>:IPLogging:FNAMe?.................................................................... 236
CONFigure:DATA:MEAS<i>:IPLogging:FSIZe...................................................................236
CONFigure:DATA:MEAS<i>:IPLogging:PCOunter............................................................. 236
CONFigure:DATA:MEAS<i>:IPLogging:PSLength............................................................. 237
INITiate:DATA:MEAS<i>:IPLogging................................................................................. 237
STOP:DATA:MEAS<i>:IPLogging....................................................................................237
ABORt:DATA:MEAS<i>:IPLogging...................................................................................237
FETCh:DATA:MEAS<i>:IPLogging:STATe?......................................................................238
FETCh:DATA:MEAS<i>:IPLogging:STATe:ALL?............................................................... 238
CONFigure:DATA:MEAS<i>:IPLogging:TYPE <LoggingType>
Selects the interface to be monitored.
Parameters:
<LoggingType>
Example:
UPIP
235
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Firmware/Software: V3.0.10
V3.2.40: added UPMulti
Options:
Manual operation:
SENSe:DATA:MEAS<i>:IPLogging:FNAMe?
Queries the current or next log file name.
If IP logging is on, the name of the currently used log file is returned.
If IP logging is off, the name of the file to be created in the next logging session is
returned.
Return values:
<FileName>
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:MEAS<i>:IPLogging:FSIZe <FileSize>
Configures the maximum log file size. When this file size is reached, logging stops.
The default value 0 byte means that no limit is defined.
Parameters:
<FileSize>
Example:
Range:
0 byte to 1E+9 byte
*RST:
0 byte
Default unit: byte
See Performing IP Logging
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:MEAS<i>:IPLogging:PCOunter <PacketCounter>
Configures the maximum number of IP packets to be logged. When this number of
packets is reached, logging stops.
The default value 0 means that no limit is defined.
Parameters:
<PacketCounter>
Example:
Range:
*RST:
0 to 1E+6
0
236
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:MEAS<i>:IPLogging:PSLength <PktSnapLength>
Configures the maximum number of bytes to be logged for each IP packet. If the
packet is longer, only the specified number of bytes is logged. The remaining bytes of
the packet are ignored.
The default value 0 means that no limit is defined.
Parameters:
<PktSnapLength>
Example:
Range:
0 byte to 65565 byte
*RST:
0 byte
Default unit: byte
See Performing IP Logging
Firmware/Software: V3.5.20
Manual operation:
INITiate:DATA:MEAS<i>:IPLogging
STOP:DATA:MEAS<i>:IPLogging
ABORt:DATA:MEAS<i>:IPLogging
Starts, stops, or aborts the measurement:
STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. Allocated resources remain allocated to the
measurement.
Usage:
Event
Firmware/Software: V3.0.10
Manual operation:
237
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
FETCh:DATA:MEAS<i>:IPLogging: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:
<MeasState>
OFF
Example:
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
FETCh:DATA:MEAS<i>:IPLogging:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measurement substates are relevant for running measurements only. Use
FETCh:...:STATe? to query the main measurement state only. Use INITiate...,
STOP..., ABORt... to change the measurement state.
Return values:
<MainState>
<SyncState>
OFF
238
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<ResourceState>
Usage:
Query only
Firmware/Software: V3.0.10
Manual operation:
6.3.7 IP Analysis
The commands in this section are related to the IP analysis application.
6.3.7.1
INITiate:DATA:MEAS<i>:IPANalysis
STOP:DATA:MEAS<i>:IPANalysis
ABORt:DATA:MEAS<i>:IPANalysis
Starts, stops, or aborts the measurement:
STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. Allocated resources remain allocated to the
measurement.
239
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Usage:
Event
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
FETCh:DATA:MEAS<i>:IPANalysis: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:
<MeasState>
Usage:
OFF
Query only
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
FETCh:DATA:MEAS<i>:IPANalysis:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measurement substates are relevant for running measurements only. Use
FETCh:...:STATe? to query the main measurement state only. Use INITiate...,
STOP..., ABORt... to change the measurement state.
240
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Return values:
<MainState>
<SyncState>
OFF
<ResourceState>
Usage:
Query only
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
CONFigure:DATA:MEAS<i>:IPANalysis:EXPortdb
Stores the IP analysis result database to a .csv file on the DAU hard disk.
Example:
Usage:
Event
Firmware/Software: V3.2.40
6.3.7.2
Options:
R&S CMW-KM051
Manual operation:
241
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
CONFigure:DATA:MEAS<i>:IPANalysis:RESult[:ALL]........................................................242
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:TCPanalysis............................................. 242
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:IPConnect................................................ 242
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:DPCP...................................................... 242
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:VOIMs..................................................... 243
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:FTTRigger................................................243
CONFigure:DATA:MEAS<i>:IPANalysis:RESult[:ALL] <TCPAnalysis>,
<IPConnect>, <DPCP>, <FTTRigger>, <VOIMs>
Enables or disables the display of the individual detailed views and the evaluation of
the related results. This command combines all other
CONFigure:DATA:MEAS<i>:IPANalysis:RESult... commands.
Parameters:
<TCPAnalysis>
OFF | ON
"TCP Analysis" view
OFF: Do not evaluate results, hide the view
ON: Evaluate results and show the view
*RST:
<IPConnect>
ON
OFF | ON
"IP Connectivity" view
*RST:
<DPCP>
ON
OFF | ON
"Data Pie Charts" view
*RST:
<FTTRigger>
ON
OFF | ON
"Flow Throughput and Event Trigger" view
*RST:
<VOIMs>
ON
OFF | ON
"Voice over IMS" view
*RST:
Example:
ON
Firmware/Software: V3.2.11
V3.2.40: added <VOIMs>
Options:
R&S CMW-KM051
Manual operation:
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:TCPanalysis <Enable>
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:IPConnect <Enable>
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:DPCP <Enable>
242
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:VOIMs <Enable>
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:FTTRigger <Enable>
Enables or disables the display of the individual detailed views and the evaluation of
the related results.
The mnemonic after "RESult" denotes the view: "TCP Analysis", "IP Connectivity",
"Data Pie Charts", "Voice over IMS" and "Flow Throughput and Event Trigger".
Parameters:
<Enable>
OFF | ON
OFF: Do not evaluate results, hide the view
ON: Evaluate results and show the view
*RST:
ON
Firmware/Software: V3.2.11
V3.2.40: added
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:VOIMs
6.3.7.3
Options:
R&S CMW-KM051
Manual operation:
CONFigure:DATA:MEAS<i>:IPANalysis:TCPanalysis:TWSThreshold <Threshold>
Defines a threshold (upper limit) for the current TCP window size as percentage of the
negotiated maximum window size.
Parameters:
<Threshold>
Example:
Range:
0 % to 100 %
*RST:
90 %
Default unit: %
See Performing IP Analysis
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
243
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
CONFigure:DATA:MEAS<i>:IPANalysis:TCPanalysis:TRTHreshold <Threshold>
Defines a threshold (upper limit) for TCP retransmissions as percentage of all transmissions.
Parameters:
<Threshold>
Example:
Range:
0 % to 100 %
*RST:
10 %
Default unit: %
See Performing IP Analysis
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
CONFigure:DATA:MEAS<i>:IPANalysis:TCPanalysis:TOTHreshold <Threshold>
Defines a threshold (upper limit) for the TCP overhead as percentage of the packet
consumed by headers.
Parameters:
<Threshold>
Example:
Range:
0 % to 100 %
*RST:
50 %
Default unit: %
See Performing IP Analysis
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
SENSe:DATA:MEAS<i>:IPANalysis:TCPanalysis:FLOWid? <FlowID>
Queries the threshold check and throughput results for a specific connection, selected
via its flow ID.
Query parameters:
<FlowID>
Return values:
<ThDown>
<TCPWSDown>
OK | FULL
Threshold check result for downlink TCP window size
<RetrDown>
OK | NOK
Threshold check result for downlink retransmissions
244
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<OverhDown>
OK | NOK
Threshold check result for downlink overhead
<ThUp>
<TCPWSUp>
OK | FULL
Threshold check result for uplink TCP window size
<RetrUp>
OK | NOK
Threshold check result for uplink retransmissions
<OverhUp>
OK | NOK
Threshold check result for uplink overhead
Example:
Usage:
Query only
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
FETCh:DATA:MEAS<i>:IPANalysis:TCPanalysis:ALL?
Queries the threshold check and throughput results for all connections.
After the reliability indicator, nine results are returned for each connection (flow):
<Reliability>, {<FlowID>, <ThDown>, <TCPWSDown>, <RetrDown>, <OverhDown>,
<ThUp>, <TCPWSUp>, <RetrUp>, <OverhUp>}connection 1, {...}connection 2, ...
Return values:
<Reliability>
<FlowID>
<ThDown>
<TCPWSDown>
OK | FULL
Threshold check result for downlink TCP window size
<RetrDown>
OK | NOK
Threshold check result for downlink retransmissions
<OverhDown>
OK | NOK
Threshold check result for downlink overhead
<ThUp>
<TCPWSUp>
OK | FULL
Threshold check result for uplink TCP window size
245
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<RetrUp>
OK | NOK
Threshold check result for uplink retransmissions
<OverhUp>
OK | NOK
Threshold check result for uplink overhead
Example:
Usage:
Query only
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
SENSe:DATA:MEAS<i>:IPANalysis:TCPanalysis:DETails? <FlowID>
Queries the "TCP Analysis" details for a specific connection, selected via its flow ID.
Query parameters:
<FlowID>
Return values:
<IPAddrSource>
<IPPortSource>
0 to 65654
<IPAddrDest>
<IPPortDest>
0 to 65654
0 % to 100 %
<OverhDown>
<CurrTCPWSUp>
0 % to 100 %
<MaxTCPWSUp>
Range:
<RetrUp>
Range:
not used to not used
Default unit: %
246
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<OverhUp>
Example:
Usage:
Query only
Firmware/Software: V3.2.11
6.3.7.4
Options:
R&S CMW-KM051
Manual operation:
IP Connectivity Results
The following commands return the results of the "IP Connectivity" view.
SENSe:DATA:MEAS<i>:IPANalysis:IPConnect:STATistics?...............................................247
SENSe:DATA:MEAS<i>:IPANalysis:IPConnect:FLOWid?.................................................. 247
FETCh:DATA:MEAS<i>:IPANalysis:IPConnect:ALL?.........................................................248
SENSe:DATA:MEAS<i>:IPANalysis:IPConnect:STATistics?
Queries the statistical information provided by the "IP Connectivity" view.
Return values:
<NoOfConn>
<NoOfOpenC>
<NoOfClosedC>
<OpenTCPC>
<ClosedTCPC>
Range:
0 to not used
<OpenUDPC>
Range:
0 to not used
<ClosedUDPC>
Range:
0 to not used
Example:
Usage:
Query only
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
SENSe:DATA:MEAS<i>:IPANalysis:IPConnect:FLOWid? <FlowID>
Queries the "IP Connectivity" results for a specific connection, selected via its flow ID.
Query parameters:
<FlowID>
247
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Return values:
<ConnStatus>
OPEN | CLOSed
Connection status
<Protocol>
<DPIProtocol>
<IPAddrSource>
<IPPortSource>
0 to 65654
<IPAddrDest>
<IPPortDest>
<OverhDown>
0 to 65654
<OverhUp>
<AvgPSDown>
<AvgPSUp>
Example:
Usage:
Query only
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
FETCh:DATA:MEAS<i>:IPANalysis:IPConnect:ALL?
Queries the "IP Connectivity" results for all connections.
After the reliability indicator, results are returned per connection (flow):
<Reliability>, {<FlowID>, <ConnStatus>, <LST>, <SysClock>, <Protocol>, <DPIProtocol>, <IPAddrSource>, <IPPortSource>, <IPAddrDest>, <IPPortDest>, <OverhDown>,
<OverhUp>, <AvgPSDown>, <AvgPSUp>}connection 1, {...}connection 2, ...
Return values:
<Reliability>
248
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<FlowID>
<ConnStatus>
OPEN | CLOSed
Connection status
<LST>
<SysClock>
0 to 99
<Protocol>
<DPIProtocol>
<IPAddrSource>
<IPPortSource>
0 to 65654
<IPAddrDest>
<IPPortDest>
<OverhDown>
0 to 65654
<OverhUp>
<AvgPSDown>
<AvgPSUp>
Example:
Usage:
Query only
Firmware/Software: V3.2.11
V3.2.40: added <LST> and <SysClock>
Options:
R&S CMW-KM051
Manual operation:
249
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
6.3.7.5
CONFigure:DATA:MEAS<i>:IPANalysis:DPCP:DPAPplic:APP <AppSelected>
Selects a layer of the "Data per Application" pie chart view.
You can navigate from the current layer to the next lower or higher layer. The initial
current layer is the application layer. The lower layers are layer 7, layer 4 and layer 3.
To query the entries (strings) of the current layer, see FETCh:DATA:MEAS<i>:
IPANalysis:DPCP:DPAPplic? on page 252.
Parameters:
<AppSelected>
Example:
Firmware/Software: V3.2.40
Options:
R&S CMW-KM051
Manual operation:
CONFigure:DATA:MEAS<i>:IPANalysis:DPCP:DPLayer:LAYer <Layer>
Selects an analysis layer for the "Data per Layer" pie chart view.
Parameters:
<Layer>
FEATure | APP | L7 | L4 | L3
*RST:
APP
Firmware/Software: V3.2.50
Options:
R&S CMW-KM051
Manual operation:
FETCh:DATA:MEAS<i>:IPANalysis:DPCP:DPConnection?
Queries the "Data per Connection" results.
After the reliability indicator, three results are returned for each connection:
250
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<RemDestination>
<ConnData>
<ConnPercent>
Example:
Usage:
Query only
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
FETCh:DATA:MEAS<i>:IPANalysis:DPCP:DPPRotocol?
Queries the "Data per Protocol" results.
After the reliability indicator, three results are returned for each protocol:
<Reliability>, {<Protocol>, <ProtData>, <ProtPercent>}protocol 1, {...}protocol 2, ...
Return values:
<Reliability>
<Protocol>
<ProtData>
<ProtPercent>
Example:
Usage:
Query only
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
251
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
FETCh:DATA:MEAS<i>:IPANalysis:DPCP:DPLayer? <LayerDepth>
Queries the "Data per Layer" results.
After the reliability indicator, three values are returned for each result table row:
<Reliability>, {<Layer>, <LayerData>, <LayerPercent>}row 1, {...}row 2, ...
Query parameters:
<LayerDepth>
FEATure | APP | L7 | L4 | L3
Selects the highest layer at which the packets are analyzed
Return values:
<Reliability>
<Layer>
<LayerData>
<LayerPercent>
Example:
Usage:
Query only
Firmware/Software: V3.2.40
Options:
R&S CMW-KM051
Manual operation:
FETCh:DATA:MEAS<i>:IPANalysis:DPCP:DPAPplic?
Queries the "Data per Application" results of the current layer. To navigate between the
layers, see CONFigure:DATA:MEAS<i>:IPANalysis:DPCP:DPAPplic:APP
on page 250.
After the reliability indicator, three values are returned for each result table row:
<Reliability>, {<App>, <AppData>, <AppPercent>}row 1, {...}row 2, ...
Return values:
<Reliability>
<App>
<AppData>
252
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<AppPercent>
Example:
Usage:
Query only
Firmware/Software: V3.2.40
6.3.7.6
Options:
R&S CMW-KM051
Manual operation:
CONFigure:DATA:MEAS<i>:IPANalysis:FTTRigger:TRACe<TraceIndex>:TFLowid
<FlowID>
Assigns a connection (flow ID) to a trace index.
Suffix:
<TraceIndex>
Parameters:
<FlowID>
.
1..10
Selects the trace to which the connection (flow ID) shall be
assigned
Flow ID of the connection to be assigned to the trace index
*RST:
Example:
<FlowID> = <TraceIndex>
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
FETCh:DATA:MEAS<i>:IPANalysis:FTTRigger:TRACes<TraceIndex>:
FTHRoughput?
Queries a selected throughput trace.
The trace is selected via its trace index. To assign a specific connection to a trace
index, see CONFigure:DATA:MEAS<i>:IPANalysis:FTTRigger:
TRACe<TraceIndex>:TFLowid.
253
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Suffix:
<TraceIndex>
.
1..10
Selects the trace that shall be returned.
Return values:
<Reliability>
<FlowID>
<Throughput>
Example:
Usage:
Query only
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
FETCh:DATA:MEAS<i>:IPANalysis:FTTRigger:TRIGger:STARt?
Queries the event trigger trace for "open" events.
After the reliability indicator, two values are returned per "open" event:
<Reliability>, {<FlowID>, <TimeElapsed>}event 1, {<FlowID>, <TimeElapsed>}event 2, ...
Return values:
<Reliability>
<FlowID>
<TimeElapsed>
Example:
Usage:
Query only
Firmware/Software: V3.2.11
Options:
R&S CMW-KM051
Manual operation:
FETCh:DATA:MEAS<i>:IPANalysis:FTTRigger:TRIGger:END?
Queries the event trigger trace for "close" events.
After the reliability indicator, two values are returned per "close" event:
<Reliability>, {<FlowID>, <TimeElapsed>}event 1, {<FlowID>, <TimeElapsed>}event 2, ...
Return values:
<Reliability>
<FlowID>
254
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<TimeElapsed>
Example:
Usage:
Query only
Firmware/Software: V3.2.11
6.3.7.7
Options:
R&S CMW-KM051
Manual operation:
FETCh:DATA:MEAS<i>:IPANalysis:VOIMs:ALL?
Queries the call table in the upper part of the "Voice Over IMS" view.
The results are returned row by row (call by call):
<Reliability>, {<ConID>, ..., <UserTo>}call 1, {...}call 2, ..., {...}call n
Return values:
<Reliability>
<ConID>
Call ID
<FlowsIDs>
<Type>
<Origin>
MT | MO | UNK
MT: mobile-terminating call
MO: mobile-originating call
UNK: unknown
<State>
<StartTime>
String indicating the time when the call setup was initiated
<SetupTime>
255
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<Duration>
<UserFrom>
<UserTo>
Example:
Usage:
Query only
Firmware/Software: V3.2.40
Options:
R&S CMW-KM051
Manual operation:
<Type>
Query parameters:
<SessionID>
Return values:
<Codec>
<SeqNumber>
<NumPack>
<Throughput>
Example:
Usage:
Query only
Firmware/Software: V3.2.40
Options:
R&S CMW-KM051
256
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Manual operation:
SENSe:DATA:MEAS<i>:IPANalysis:VOIMs:PERDtx? <ConID>
Queries the packets measurement results for a selected voice over IMS call.
To get a list of all calls and their IDs, use FETCh:DATA:MEAS<i>:IPANalysis:
VOIMs:ALL? on page 255.
Query parameters:
<ConID>
Return values:
<PERUp>
<PERDown>
<DTXUp>
<DTXDown>
Example:
Usage:
Query only
Firmware/Software: V3.2.40
Options:
R&S CMW-KM051
Manual operation:
SENSe:DATA:MEAS<i>:IPANalysis:VOIMs:JITTer? <ConID>
Queries the jitter results for a selected voice over IMS call.
To get a list of all calls and their IDs, use FETCh:DATA:MEAS<i>:IPANalysis:
VOIMs:ALL? on page 255.
Query parameters:
<ConID>
Return values:
<JitterMaxUp>
<JitterAvgUp>
257
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<JitterMinUp>
<JitterMaxDown>
<JitterAvgDown>
<JitterMinDown>
Example:
Usage:
Query only
Firmware/Software: V3.2.40
Options:
R&S CMW-KM051
Manual operation:
6.3.8 IP Replay
The commands in this section are related to the IP replay application.
6.3.8.1
258
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Parameters:
<FileName>
<Iteration>
File name as a string. Specify the file name with extension but
without path, for example "myfile.pcap".
Specifies how often the file is replayed
Range:
*RST:
<NetworkInterface>
0 to 10E+3
1
LANDau | IP | MULTicast
LANDau: IP traffic to the LAN DAU connector
IP: IP unicast traffic to the mobile
MULTicast: IP multicast traffic to the mobile
*RST:
Example:
MULT
Firmware/Software: V3.2.50
Manual operation:
CONFigure:DATA:MEAS<i>:IPReplay:REMovelist
Removes all files from the playlist. This is only possible in the measurement state OFF.
Example:
Usage:
Event
Firmware/Software: V3.2.50
Manual operation:
File name as a string. Specify the file name with extension but
without path, for example "myfile.pcap".
Specifies how often the file is replayed
Range:
*RST:
Example:
0 to 10E+3
1
Firmware/Software: V3.2.50
Manual operation:
259
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
LANDau | IP | MULTicast
LANDau: IP traffic to the LAN DAU connector
IP: IP unicast traffic to the mobile
MULTicast: IP multicast traffic to the mobile
*RST:
Example:
MULT
Firmware/Software: V3.2.50
Manual operation:
CONFigure:DATA:MEAS<i>:IPReplay:PLAYall
Starts replaying the playlist.
Example:
Usage:
Event
Firmware/Software: V3.2.50
Manual operation:
CONFigure:DATA:MEAS<i>:IPReplay:STOPall
Stops replaying the playlist.
Example:
Usage:
Event
Firmware/Software: V3.2.50
Manual operation:
SENSe:DATA:MEAS<i>:IPReplay:PROGress?
Queries the replay progress for all files in the playlist. This is only possible while the
playlist is replayed.
The results are returned as follows:
260
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<Progress>
Range:
0 % to 100 %
Default unit: %
Example:
Usage:
Query only
Firmware/Software: V3.2.50
Manual operation:
6.3.8.2
INITiate:DATA:MEAS<i>:IPReplay
STOP:DATA:MEAS<i>:IPReplay
ABORt:DATA:MEAS<i>:IPReplay
Starts, stops, or aborts the measurement:
STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. Allocated resources remain allocated to the
measurement.
Usage:
Event
Firmware/Software: V3.2.50
Manual operation:
261
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
FETCh:DATA:MEAS<i>:IPReplay: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:
<MeasState>
OFF
Example:
Usage:
Query only
Firmware/Software: V3.2.50
Manual operation:
FETCh:DATA:MEAS<i>:IPReplay:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measurement substates are relevant for running measurements only. Use
FETCh:...:STATe? to query the main measurement state only. Use INITiate...,
STOP..., ABORt... to change the measurement state.
Return values:
<MainState>
<SyncState>
OFF
262
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<ResourceState>
Usage:
Query only
Firmware/Software: V3.2.50
Manual operation:
6.3.8.3
File Information
The following commands query information about the files in the ip_replay directory
and in the playlist.
FETCh:DATA:MEAS<i>:IPReplay:FILelist?.......................................................................263
SENSe:DATA:MEAS<i>:IPReplay:INFofile?......................................................................263
SENSe:DATA:MEAS<i>:IPReplay:TRAFficfile?................................................................. 264
FETCh:DATA:MEAS<i>:IPReplay:FILelist?
Queries a list of all files in the directory ip_replay of the samba share.
Return values:
<Files>
Example:
Usage:
Query only
Firmware/Software: V3.5.10
Manual operation:
SENSe:DATA:MEAS<i>:IPReplay:INFofile? <FileName>
Queries information about a selected file in the playlist.
If the file has not yet been analyzed and the measurement state is RUN, the command
triggers file analysis. The analysis takes some time. Repeat the command until the
analysis results are available.
Query parameters:
<FileName>
File name as a string. Specify the file name with extension but
without path, for example "myfile.pcap".
Return values:
<NumberOfPackets> Number of IP packets in the file
<FileSize>
<Bitrate>
263
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
<Duration>
Default unit: s
<Type>
String indicating the file type and information about the capturing
application
<Encapsulation>
Example:
Usage:
Query only
Firmware/Software: V3.2.50
Manual operation:
SENSe:DATA:MEAS<i>:IPReplay:TRAFficfile? <FileName>
Queries information about all IP connections contained in a selected file of the playlist.
If the file has not yet been analyzed and the measurement state is RUN, the command
triggers file analysis. The analysis takes some time. Repeat the command until the
analysis results are available.
The results are returned as follows:
{<L4Protocol>, <NoOfPackets>, ..., <IPDstPort>}conn 1, {...}conn 2, ...
Query parameters:
<FileName>
File name as a string. Specify the file name with extension but
without path, for example "myfile.pcap".
Return values:
<L4Protocol>
<NoOfPackets>
<IPSrcAddress>
<IPSrcPort>
<IPDstAddress>
<IPDstPort>
Example:
Usage:
Query only
Firmware/Software: V3.2.50
Manual operation:
264
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
CONFigure:DATA:MEAS<i>:ADELay:SAMPles?............................................................... 265
CONFigure:DATA:MEAS<i>:ADELay:SPINterval?.............................................................265
CONFigure:DATA:MEAS<i>:ADELay:MSAMples.............................................................. 266
INITiate:DATA:MEAS<i>:ADELay.................................................................................... 266
STOP:DATA:MEAS<i>:ADELay.......................................................................................266
ABORt:DATA:MEAS<i>:ADELay..................................................................................... 266
FETCh:DATA:MEAS<i>:ADELay:STATe?........................................................................ 266
FETCh:DATA:MEAS<i>:ADELay:STATe:ALL?..................................................................267
FETCh:DATA:MEAS<i>:ADELay:TRACe:ULINk[:CURRent]?............................................. 268
FETCh:DATA:MEAS<i>:ADELay:TRACe:DLINk[:CURRent]?............................................. 268
FETCh:DATA:MEAS<i>:ADELay:TRACe:LOOPback[:CURRent]?...................................... 268
READ:DATA:MEAS<i>:ADELay:TRACe:ULINk[:CURRent]?...............................................268
READ:DATA:MEAS<i>:ADELay:TRACe:DLINk[:CURRent]?...............................................268
READ:DATA:MEAS<i>:ADELay:TRACe:LOOPback[:CURRent]?........................................268
FETCh:DATA:MEAS<i>:ADELay:TRACe:TAULink[:CURRent]?..........................................268
FETCh:DATA:MEAS<i>:ADELay:TRACe:TALoopback[:CURRent]?.................................... 268
READ:DATA:MEAS<i>:ADELay:TRACe:TAULink[:CURRent]?........................................... 268
READ:DATA:MEAS<i>:ADELay:TRACe:TALoopback[:CURRent]?..................................... 268
FETCh:DATA:MEAS<i>:ADELay:ULINk?......................................................................... 269
FETCh:DATA:MEAS<i>:ADELay:DLINk?......................................................................... 269
FETCh:DATA:MEAS<i>:ADELay:LOOPback?...................................................................269
READ:DATA:MEAS<i>:ADELay:ULINk?...........................................................................269
READ:DATA:MEAS<i>:ADELay:DLINk?...........................................................................269
READ:DATA:MEAS<i>:ADELay:LOOPback?....................................................................269
FETCh:DATA:MEAS<i>:ADELay:TAULink?...................................................................... 269
FETCh:DATA:MEAS<i>:ADELay:TALoopback?................................................................ 269
READ:DATA:MEAS<i>:ADELay:TAULink?....................................................................... 269
READ:DATA:MEAS<i>:ADELay:TALoopback?................................................................. 269
CONFigure:DATA:MEAS<i>:ADELay:SAMPles?
Queries the fixed duration of a measurement interval.
Return values:
<Interval>
Range:
1s
Default unit: s
Example:
Usage:
Query only
Firmware/Software: V3.5.20
Manual operation:
CONFigure:DATA:MEAS<i>:ADELay:SPINterval?
Queries the fixed number of measurement samples per interval.
Return values:
<SmplPerInterval>
Range:
Example:
50
265
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Usage:
Query only
Firmware/Software: V3.5.20
Manual operation:
CONFigure:DATA:MEAS<i>:ADELay:MSAMples <MaxSamples>
Configures the maximum number of samples that can be displayed in the result diagrams. The traces cover the sample range -<MaxSamples> + 1 to 0.
Parameters:
<MaxSamples>
Example:
Range:
*RST:
1500 to 6000
3000
Firmware/Software: V3.5.20
Manual operation:
INITiate:DATA:MEAS<i>:ADELay
STOP:DATA:MEAS<i>:ADELay
ABORt:DATA:MEAS<i>:ADELay
Starts, stops, or aborts the measurement:
STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. Allocated resources remain allocated to the
measurement.
Usage:
Event
Firmware/Software: V3.5.20
Manual operation:
FETCh:DATA:MEAS<i>:ADELay: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.
266
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Return values:
<MeasState>
Usage:
OFF
Query only
Firmware/Software: V3.5.20
Manual operation:
FETCh:DATA:MEAS<i>:ADELay:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measurement substates are relevant for running measurements only. Use
FETCh:...:STATe? to query the main measurement state only. Use INITiate...,
STOP..., ABORt... to change the measurement state.
Return values:
<MainState>
<SyncState>
OFF
<ResourceState>
Usage:
Query only
Firmware/Software: V3.5.20
267
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Manual operation:
FETCh:DATA:MEAS<i>:ADELay:TRACe:ULINk[:CURRent]?
FETCh:DATA:MEAS<i>:ADELay:TRACe:DLINk[:CURRent]?
FETCh:DATA:MEAS<i>:ADELay:TRACe:LOOPback[:CURRent]?
READ:DATA:MEAS<i>:ADELay:TRACe:ULINk[:CURRent]?
READ:DATA:MEAS<i>:ADELay:TRACe:DLINk[:CURRent]?
READ:DATA:MEAS<i>:ADELay:TRACe:LOOPback[:CURRent]?
Query the values of the audio delay traces "Uplink", "Downlink" and "Loopback".
The trace values are returned from left to right, from sample number -n to sample number 0. n equals the configured maximum number of samples minus one, see
CONFigure:DATA:MEAS<i>:ADELay:MSAMples on page 266.
Return values:
<Reliability>
<Results>
Example:
Usage:
Query only
Firmware/Software: V3.5.20
Manual operation:
FETCh:DATA:MEAS<i>:ADELay:TRACe:TAULink[:CURRent]?
FETCh:DATA:MEAS<i>:ADELay:TRACe:TALoopback[:CURRent]?
READ:DATA:MEAS<i>:ADELay:TRACe:TAULink[:CURRent]?
READ:DATA:MEAS<i>:ADELay:TRACe:TALoopback[:CURRent]?
Query the values of the time of arrival traces "Uplink" and "Loopback".
The trace values are returned from left to right, from sample number -n to sample number 0. n equals the configured maximum number of samples minus one, see
CONFigure:DATA:MEAS<i>:ADELay:MSAMples on page 266.
Return values:
<Reliability>
<Results>
Example:
Usage:
Query only
Firmware/Software: V3.5.20
Manual operation:
268
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
FETCh:DATA:MEAS<i>:ADELay:ULINk?
FETCh:DATA:MEAS<i>:ADELay:DLINk?
FETCh:DATA:MEAS<i>:ADELay:LOOPback?
READ:DATA:MEAS<i>:ADELay:ULINk?
READ:DATA:MEAS<i>:ADELay:DLINk?
READ:DATA:MEAS<i>:ADELay:LOOPback?
Query the statistical audio delay results for "Uplink", "Downlink" and "Loopback".
Return values:
<Reliability>
<Results>
Example:
Usage:
Query only
Firmware/Software: V3.5.20
Manual operation:
FETCh:DATA:MEAS<i>:ADELay:TAULink?
FETCh:DATA:MEAS<i>:ADELay:TALoopback?
READ:DATA:MEAS<i>:ADELay:TAULink?
READ:DATA:MEAS<i>:ADELay:TALoopback?
Query the statistical time of arrival results for "Uplink" and "Loopback".
Return values:
<Reliability>
<Results>
Example:
Usage:
Query only
Firmware/Software: V3.5.20
Manual operation:
269
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:DELay................................................ 271
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:JITTer................................................ 272
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:JDIStribut........................................... 272
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:RRATe............................................... 272
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:DRATe............................................... 273
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:CRATe............................................... 273
SOURce:DATA:MEAS<i>:NIMPairment:STATe.................................................................273
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:ENABle <Enable>
Enables or disables a set of network impairments.
To apply network impairments, this feature must also be enabled globally, see
SOURce:DATA:MEAS<i>:NIMPairment:STATe on page 273.
Suffix:
<Index>
Parameters:
<Enable>
.
1..7
Selects the set of network impairments
OFF | ON
*RST:
Example:
OFF
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:IPADdress <IPAddress>
Specifies the destination address of the bearer to be impaired.
Suffix:
<Index>
Parameters:
<IPAddress>
.
1..7
Selects the set of network impairments
String indicating a full IPv4 address or a full IPv6 address or an
IPv6 prefix
*RST:
Example:
'172.22.1.100'
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:PRANge <StartPort>,
<EndPort>
Specifies the port range used by the dedicated bearer to be impaired. If you want to
impair a default bearer, enter 0 for both parameters.
270
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Suffix:
<Index>
Parameters:
<StartPort>
.
1..7
Selects the set of network impairments
Range:
*RST:
0 to 65535
0
<EndPort>
Range:
*RST:
0 to 65535
0
Example:
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:PLRate <PacketLossRate>
Specifies the packet loss rate for a set of network impairments.
Suffix:
<Index>
Parameters:
<PacketLossRate>
Example:
.
1..7
Selects the set of network impairments
Range:
0 % to 100 %
*RST:
0%
Default unit: %
See Configuring Network Impairments
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:DELay <Delay>
Specifies the delay for a set of network impairments.
Suffix:
<Index>
Parameters:
<Delay>
Example:
.
1..7
Selects the set of network impairments
Range:
0 s to 10 s
*RST:
0s
Default unit: s
See Configuring Network Impairments
Firmware/Software: V3.0.10
Manual operation:
271
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:JITTer <Jitter>
Specifies the jitter for a set of network impairments. The jitter must be smaller than or
equal to the configured delay.
Suffix:
<Index>
Parameters:
<Jitter>
Example:
.
1..7
Selects the set of network impairments
Range:
0 s to 10 s
*RST:
0s
Default unit: s
See Configuring Network Impairments
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:JDIStribut <JitterDistr>
Specifies the jitter distribution for a set of network impairments.
Suffix:
<Index>
Parameters:
<JitterDistr>
.
1..7
Selects the set of network impairments
UNIForm | NORMal | PAReto | PNORmal
Uniform, normal, pareto and pareto normal distribution
*RST:
Example:
NORM
Firmware/Software: V3.0.30
Manual operation:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:RRATe <ReorderRate>
Specifies the reordering rate for a set of network impairments.
Suffix:
<Index>
Parameters:
<ReorderRate>
Example:
.
1..7
Selects the set of network impairments
Range:
0 % to 100 %
*RST:
0%
Default unit: %
See Configuring Network Impairments
Firmware/Software: V3.0.10
272
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Manual operation:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:DRATe <DuplicateRate>
Specifies the percentage of packets to be duplicated.
Suffix:
<Index>
Parameters:
<DuplicateRate>
Example:
.
1..7
Selects the set of network impairments
Range:
0 % to 100 %
*RST:
0%
Default unit: %
See Configuring Network Impairments
Firmware/Software: V3.0.10
Manual operation:
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:CRATe <CorruptRate>
Specifies the percentage of packets that shall be corrupted.
Suffix:
<Index>
Parameters:
<CorruptRate>
Example:
.
1..7
Selects the set of network impairments
Range:
0 % to 100 %
*RST:
0%
Default unit: %
See Configuring Network Impairments
Firmware/Software: V3.0.10
Manual operation:
SOURce:DATA:MEAS<i>:NIMPairment:STATe <Control>
Switches network impairments globally on or off. When on, the enabled sets of network
impairments are applied to the bearers defined in these sets.
To enable a set of impairments, see CONFigure:DATA:MEAS<i>:
NIMPairments<Index>:ENABle on page 270.
Setting parameters:
<Control>
ON | OFF
Switch network impairments ON or OFF
273
R&SCMW-B450A/B/D
Command Reference
Data Application Measurements
Return values:
<NIState>
OFF | PENDing | ON
OFF: impairments switched off
PEND: switching on/off the impairments is ongoing
ON: impairments switched on
*RST:
Example:
OFF
Firmware/Software: V3.0.10
Manual operation:
274
R&SCMW-B450A/B/D
The DAU applications "IP Analysis" and "IP Logging" monitor the outgoing traffic after
the network impairments have been applied. They have no information about the unimpaired traffic.
Analysis of packet retransmission with network impairments
In order to recognize a retransmitted packet, the "IP Analysis" application must receive
both the initially transmitted packet and the retransmitted packet.
If the initially transmitted packet gets lost after passing the application, the retransmitted packet is counted correctly by the "IP Analysis" application (for example packet
loss on the RF connection to a mobile).
If the initially transmitted packet gets lost before passing the application, the retransmitted packet is counted as initial transmission, not as retransmission (for example
packet loss rate configured as network impairment).
In the latter case you may want to use the "IP Logging" application to analyze the
retransmissions, for example by checking for retransmission requests.
The network impairments functionality of the DAU is based on the netem Linux kernel
module (see http://www.linuxfoundation.org/collaborate/workgroups/networking/
netem).
For configuration and control of network impairments, see Chapter 4.2.11, "Network
Impairments", on page 122.
The following sections illustrate the effect of the individual network impairment settings.
275
R&SCMW-B450A/B/D
The results are shown in the following sections. Dashed gray lines in the figures indicate the configured delay value the configured jitter value.
Minimum RTT
Maximum RTT
Average RTT
0.16 ms
0.55 ms
0.31 ms
276
R&SCMW-B450A/B/D
Minimum RTT
Maximum RTT
Average RTT
70.19 ms
70.80 ms
70.38 ms
Within the interval [delay - jitter, delay + jitter], the measured RTT values are distributed uniformly. The following figure shows the distribution of 1000 measured RTT values (previous figure shows the first 300 of these 1000 values).
277
R&SCMW-B450A/B/D
Minimum RTT
Maximum RTT
Average RTT
60.32 ms
80.38 ms
70.39 ms
For an ideal Gaussian distribution of the RTT values, the mean value of the distribution equals the delay and the standard deviation of the distribution equals the jitter.
The interval [ - , + ] contains 68.27 % of all RTT values. The interval [ - 2, +
2] contains 95.45 %.
The following figure shows the distribution of 1000 measured RTT values (previous figure shows the first 300 of these 1000 values).
278
R&SCMW-B450A/B/D
Minimum RTT
Maximum RTT
Average RTT
39.45 ms
100.79 ms
70.51 ms
279
R&SCMW-B450A/B/D
The following figure shows the distribution of 1000 measured RTT values (previous figure shows the first 300 of these 1000 values).
Minimum RTT
Maximum RTT
Average RTT
63.67 ms
110.50 ms
69.81 ms
Figure 7-9: RTT vs. ping request, pareto normal jitter distribution
280
R&SCMW-B450A/B/D
The following figure shows the distribution of 1000 measured RTT values (previous figure shows the first 300 of these 1000 values).
Minimum RTT
Maximum RTT
Average RTT
55.30 ms
109.19 ms
70.41 ms
281
R&SCMW-B450A/B/D
Figure 7-11: Reordering rate vs. measurement interval (10 % reordering configured)
Figure 7-12: Reordering rate vs. measurement interval (25 % reordering configured)
The following figures show the distribution of the reordering rates over all measured
intervals.
282
R&SCMW-B450A/B/D
Figure 7-15: Duplicates rate vs. measurement interval (10 % duplicates configured)
283
R&SCMW-B450A/B/D
Figure 7-16: Duplicates rate vs. measurement interval (25 % duplicates configured)
The following figures show the distribution of the duplicates rates over all measured
intervals.
284
R&SCMW-B450A/B/D
Figure 7-19: Packet loss rate vs. measurement interval (10 % loss configured)
Figure 7-20: Packet loss rate vs. measurement interval (25 % loss configured)
The following figures show the distribution of the packet loss rates over all measured
intervals.
285
R&SCMW-B450A/B/D
Figure 7-21: Packet loss rate distribution (10 % packet loss configured)
Figure 7-22: Packet loss rate distribution (25 % packet loss configured)
286
R&SCMW-B450A/B/D
Figure 7-23: Corruption rate vs. measurement interval (10 % corruption configured)
Figure 7-24: Corruption rate vs. measurement interval (25 % corruption configured)
The following figures show the distribution of the corruption rates over all measured
intervals.
287
R&SCMW-B450A/B/D
288
R&SCMW-B450A/B/D
List of Commands
List of Commands
ABORt:DATA:MEAS<i>:ADELay...................................................................................................................266
ABORt:DATA:MEAS<i>:DNSRequests......................................................................................................... 232
ABORt:DATA:MEAS<i>:IPANalysis...............................................................................................................239
ABORt:DATA:MEAS<i>:IPERf.......................................................................................................................223
ABORt:DATA:MEAS<i>:IPLogging................................................................................................................237
ABORt:DATA:MEAS<i>:IPReplay................................................................................................................. 261
ABORt:DATA:MEAS<i>:PING....................................................................................................................... 215
ABORt:DATA:MEAS<i>:THRoughput............................................................................................................228
CONFigure:DATA:CONTrol:DNS:ASERvices:ADD.......................................................................................164
CONFigure:DATA:CONTrol:DNS:ASERvices:DELete.................................................................................. 164
CONFigure:DATA:CONTrol:DNS:FOReign:IPVFour:PRIMary:ADDRess..................................................... 161
CONFigure:DATA:CONTrol:DNS:FOReign:IPVFour:SECondary:ADDRess.................................................161
CONFigure:DATA:CONTrol:DNS:FOReign:IPVSix:PRIMary:ADDRess....................................................... 162
CONFigure:DATA:CONTrol:DNS:FOReign:IPVSix:SECondary:ADDRess................................................... 162
CONFigure:DATA:CONTrol:DNS:FOReign:UDHCp......................................................................................162
CONFigure:DATA:CONTrol:DNS:LOCal:ADD...............................................................................................163
CONFigure:DATA:CONTrol:DNS:LOCal:DELete.......................................................................................... 163
CONFigure:DATA:CONTrol:DNS:PRIMary:STYPe....................................................................................... 159
CONFigure:DATA:CONTrol:DNS:SECondary:STYPe...................................................................................159
CONFigure:DATA:CONTrol:DNS:TEST:DOMain.......................................................................................... 165
CONFigure:DATA:CONTrol:DNS:TEST:STARt.............................................................................................165
CONFigure:DATA:CONTrol:EPDG:ADDRess:IPVFour.................................................................................203
CONFigure:DATA:CONTrol:EPDG:ADDRess:IPVSix................................................................................... 203
CONFigure:DATA:CONTrol:EPDG:AUTHentic:ALGorithm........................................................................... 209
CONFigure:DATA:CONTrol:EPDG:AUTHentic:AMF.....................................................................................209
CONFigure:DATA:CONTrol:EPDG:AUTHentic:IMSI..................................................................................... 208
CONFigure:DATA:CONTrol:EPDG:AUTHentic:KEY..................................................................................... 209
CONFigure:DATA:CONTrol:EPDG:AUTHentic:KEY:TYPE...........................................................................210
CONFigure:DATA:CONTrol:EPDG:AUTHentic:OPC.....................................................................................210
CONFigure:DATA:CONTrol:EPDG:AUTHentic:RAND.................................................................................. 209
CONFigure:DATA:CONTrol:EPDG:CERTificate:CERTificate....................................................................... 212
CONFigure:DATA:CONTrol:EPDG:CERTificate:ENABle.............................................................................. 212
CONFigure:DATA:CONTrol:EPDG:CERTificate:KEY................................................................................... 212
CONFigure:DATA:CONTrol:EPDG:DPD:ENABle..........................................................................................210
CONFigure:DATA:CONTrol:EPDG:DPD:INTerval.........................................................................................211
CONFigure:DATA:CONTrol:EPDG:DPD:TIMeout......................................................................................... 211
CONFigure:DATA:CONTrol:EPDG:ESP:ENCRyption...................................................................................206
CONFigure:DATA:CONTrol:EPDG:ESP:INTegrity........................................................................................ 207
CONFigure:DATA:CONTrol:EPDG:ID:TYPE.................................................................................................204
CONFigure:DATA:CONTrol:EPDG:ID:VALue............................................................................................... 204
CONFigure:DATA:CONTrol:EPDG:IKE:DHGRoup....................................................................................... 206
CONFigure:DATA:CONTrol:EPDG:IKE:ENCRyption.................................................................................... 204
CONFigure:DATA:CONTrol:EPDG:IKE:INTegrity......................................................................................... 205
CONFigure:DATA:CONTrol:EPDG:IKE:PRF.................................................................................................205
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVFour:TYPE........................................................................... 207
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVSix:ADDRess:LENGth......................................................... 208
CONFigure:DATA:CONTrol:EPDG:PCSCf:IPVSix:TYPE..............................................................................207
289
R&SCMW-B450A/B/D
List of Commands
CONFigure:DATA:CONTrol:FTP:AUSer........................................................................................................168
CONFigure:DATA:CONTrol:FTP:DUPLoad...................................................................................................168
CONFigure:DATA:CONTrol:FTP:ENConnection........................................................................................... 167
CONFigure:DATA:CONTrol:FTP:IPVSix....................................................................................................... 167
CONFigure:DATA:CONTrol:FTP:STYPe.......................................................................................................167
CONFigure:DATA:CONTrol:FTP:USER:ADD................................................................................................168
CONFigure:DATA:CONTrol:FTP:USER:DELete........................................................................................... 169
CONFigure:DATA:CONTrol:HTTP:ENConnection........................................................................................ 170
CONFigure:DATA:CONTrol:HTTP:IPVSix.....................................................................................................171
CONFigure:DATA:CONTrol:IMS2:EXTern:PCSCf:ADDRess:IPVFour......................................................... 179
CONFigure:DATA:CONTrol:IMS2:EXTern:PCSCf:ADDRess:IPVSix............................................................180
CONFigure:DATA:CONTrol:IMS2:MOBile<UE>:DERegister........................................................................ 178
CONFigure:DATA:CONTrol:IMS2:PCSCf:ADD............................................................................................. 180
CONFigure:DATA:CONTrol:IMS2:PCSCf:CREate........................................................................................ 183
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:BEHaviour............................................................................. 181
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:DELete.................................................................................. 181
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:FAILurecode..........................................................................181
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:IPADdress............................................................................. 181
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:REGexp.................................................................................182
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:RETRyafter............................................................................182
CONFigure:DATA:CONTrol:IMS2:PCSCf<p>:SUBexp................................................................................. 183
CONFigure:DATA:CONTrol:IMS2:RELease:CALL:ID................................................................................... 178
CONFigure:DATA:CONTrol:IMS2:SUBScriber:ADD..................................................................................... 184
CONFigure:DATA:CONTrol:IMS2:SUBScriber:CREate................................................................................ 189
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:ALGorithm............................................... 186
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:AMF......................................................... 186
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:KEY......................................................... 186
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:OPC.........................................................187
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:AUTHenticati:SCHeme.................................................. 185
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:DELete...........................................................................185
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ALGorithm:ENCRyption...................................... 188
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ALGorithm:INTegrity........................................... 188
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:IPSec:ENABle................................................................187
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:PRIVateid.......................................................................185
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:PUBLicuserid<Index>.................................................... 188
CONFigure:DATA:CONTrol:IMS2:SUBScriber<s>:RESLength.................................................................... 187
CONFigure:DATA:CONTrol:IMS2:SUSage................................................................................................... 178
CONFigure:DATA:CONTrol:IMS2:THReshold:VALue...................................................................................179
CONFigure:DATA:CONTrol:IMS2:TRANsport:SELection............................................................................. 179
CONFigure:DATA:CONTrol:IMS2:UPDate:AMR:ALIGnment........................................................................176
CONFigure:DATA:CONTrol:IMS2:UPDate:AMR:CODec<CodecIdx>:ENABle............................................. 176
CONFigure:DATA:CONTrol:IMS2:UPDate:AMR:TYPE.................................................................................175
CONFigure:DATA:CONTrol:IMS2:UPDate:CALL:ID..................................................................................... 175
CONFigure:DATA:CONTrol:IMS2:UPDate:CALL:TYPE................................................................................177
CONFigure:DATA:CONTrol:IMS2:UPDate:PERForm................................................................................... 177
CONFigure:DATA:CONTrol:IMS2:UPDate:VIDeo:ATTRibutes..................................................................... 177
CONFigure:DATA:CONTrol:IMS2:UPDate:VIDeo:CODec............................................................................ 176
CONFigure:DATA:CONTrol:IMS2:VIRTualsub:ADD..................................................................................... 190
CONFigure:DATA:CONTrol:IMS2:VIRTualsub:CREate................................................................................ 195
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AMR:ALIGnment............................................................192
290
R&SCMW-B450A/B/D
List of Commands
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AMR:CODec<CodecIdx>:ENABle................................. 193
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AMR:TYPE.................................................................... 192
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:AUDioboard................................................................... 195
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:BEARer..........................................................................191
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:BEHaviour......................................................................190
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:DELete...........................................................................190
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:FORWard.......................................................................194
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:ID................................................................................... 190
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MEDiaendpoin............................................................... 194
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:ALIGnment............................................... 199
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:CODec<CodecIdx>:ENABle.....................199
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:AMR:TYPE........................................................ 198
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:BEARer............................................................. 198
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:CALL................................................................. 200
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:DESTination...................................................... 196
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:SIGType............................................................ 197
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:TYPE................................................................. 197
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:VIDeo:ATTRibutes............................................ 200
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:VIDeo:CODec....................................................199
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:DESTination..................................................... 201
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:SEND............................................................... 202
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:TEXT................................................................ 202
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:TYPE................................................................ 201
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:SIGNalingtyp..................................................................191
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:VIDeo:ATTRibutes.........................................................193
CONFigure:DATA:CONTrol:IMS2:VIRTualsub<v>:VIDeo:CODec................................................................ 193
CONFigure:DATA:CONTrol:IPVFour:ADDRess:TYPE..................................................................................150
CONFigure:DATA:CONTrol:IPVFour:STATic:ADDResses:ADD...................................................................152
CONFigure:DATA:CONTrol:IPVFour:STATic:ADDResses:DELete.............................................................. 153
CONFigure:DATA:CONTrol:IPVFour:STATic:GIP.........................................................................................151
CONFigure:DATA:CONTrol:IPVFour:STATic:IPADdress..............................................................................151
CONFigure:DATA:CONTrol:IPVFour:STATic:SMASk................................................................................... 151
CONFigure:DATA:CONTrol:IPVSix:ADDRess:TYPE.................................................................................... 154
CONFigure:DATA:CONTrol:IPVSix:MANual:ROUTing:ADD.........................................................................158
CONFigure:DATA:CONTrol:IPVSix:MANual:ROUTing:DELete.................................................................... 158
CONFigure:DATA:CONTrol:IPVSix:MOBile:PREFix:TYPE...........................................................................156
CONFigure:DATA:CONTrol:IPVSix:ROUTing:TYPE.....................................................................................157
CONFigure:DATA:CONTrol:IPVSix:STATic:ADDRess..................................................................................155
CONFigure:DATA:CONTrol:IPVSix:STATic:DROuter................................................................................... 155
CONFigure:DATA:CONTrol:IPVSix:STATic:PREFixes:ADD.........................................................................156
CONFigure:DATA:CONTrol:IPVSix:STATic:PREFixes:DELete.................................................................... 156
CONFigure:DATA:CONTrol:MTU.................................................................................................................. 150
CONFigure:DATA:MEAS<i>:ADELay:MSAMples......................................................................................... 266
CONFigure:DATA:MEAS<i>:ADELay:SAMPles?.......................................................................................... 265
CONFigure:DATA:MEAS<i>:ADELay:SPINterval?........................................................................................265
CONFigure:DATA:MEAS<i>:IPANalysis:DPCP:DPAPplic:APP.................................................................... 250
CONFigure:DATA:MEAS<i>:IPANalysis:DPCP:DPLayer:LAYer...................................................................250
CONFigure:DATA:MEAS<i>:IPANalysis:EXPortdb....................................................................................... 241
CONFigure:DATA:MEAS<i>:IPANalysis:FTTRigger:TRACe<TraceIndex>:TFLowid....................................253
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:DPCP................................................................................ 242
291
R&SCMW-B450A/B/D
List of Commands
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:FTTRigger......................................................................... 243
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:IPConnect..........................................................................242
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:TCPanalysis...................................................................... 242
CONFigure:DATA:MEAS<i>:IPANalysis:RESult:VOIMs............................................................................... 243
CONFigure:DATA:MEAS<i>:IPANalysis:RESult[:ALL].................................................................................. 242
CONFigure:DATA:MEAS<i>:IPANalysis:TCPanalysis:TOTHreshold............................................................244
CONFigure:DATA:MEAS<i>:IPANalysis:TCPanalysis:TRTHreshold............................................................ 244
CONFigure:DATA:MEAS<i>:IPANalysis:TCPanalysis:TWSThreshold......................................................... 243
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:BITRate.........................................................................223
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:ENABle......................................................................... 221
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:IPADdress.....................................................................222
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PCONnection................................................................ 223
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PORT............................................................................ 222
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:PROTocol..................................................................... 221
CONFigure:DATA:MEAS<i>:IPERf:CLIent<Index>:WSIZe........................................................................... 222
CONFigure:DATA:MEAS<i>:IPERf:PSIZe.....................................................................................................219
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:ENABle....................................................................... 219
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:PORT..........................................................................220
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:PROTocol................................................................... 220
CONFigure:DATA:MEAS<i>:IPERf:SERVer<Index>:WSIZe.........................................................................221
CONFigure:DATA:MEAS<i>:IPERf:TDURation.............................................................................................219
CONFigure:DATA:MEAS<i>:IPLogging:FSIZe.............................................................................................. 236
CONFigure:DATA:MEAS<i>:IPLogging:PCOunter........................................................................................236
CONFigure:DATA:MEAS<i>:IPLogging:PSLength........................................................................................ 237
CONFigure:DATA:MEAS<i>:IPLogging:TYPE.............................................................................................. 235
CONFigure:DATA:MEAS<i>:IPReplay:CREatelist........................................................................................ 258
CONFigure:DATA:MEAS<i>:IPReplay:INTerface..........................................................................................260
CONFigure:DATA:MEAS<i>:IPReplay:ITERation......................................................................................... 259
CONFigure:DATA:MEAS<i>:IPReplay:PLAYall.............................................................................................260
CONFigure:DATA:MEAS<i>:IPReplay:REMovelist....................................................................................... 259
CONFigure:DATA:MEAS<i>:IPReplay:STOPall............................................................................................ 260
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:CRATe........................................................................ 273
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:DELay......................................................................... 271
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:DRATe........................................................................ 273
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:ENABle........................................................................270
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:IPADdress................................................................... 270
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:JDIStribut.................................................................... 272
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:JITTer..........................................................................272
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:PLRate........................................................................ 271
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:PRANge...................................................................... 270
CONFigure:DATA:MEAS<i>:NIMPairments<Index>:RRATe........................................................................ 272
CONFigure:DATA:MEAS<i>:PING:DIPaddress............................................................................................ 214
CONFigure:DATA:MEAS<i>:PING:INTerval..................................................................................................214
CONFigure:DATA:MEAS<i>:PING:PCOunt.................................................................................................. 215
CONFigure:DATA:MEAS<i>:PING:PSIZe..................................................................................................... 215
CONFigure:DATA:MEAS<i>:PING:TIMeout.................................................................................................. 214
CONFigure:DATA:MEAS<i>:RAN................................................................................................................. 213
CONFigure:DATA:MEAS<i>:RAN:CATaloge?.............................................................................................. 213
CONFigure:DATA:MEAS<i>:THRoughput:MCOunt...................................................................................... 227
CONFigure:DATA:MEASurement<inst>:DNSRequests:MICount..................................................................232
292
R&SCMW-B450A/B/D
List of Commands
FETCh:DATA:MEAS<i>:ADELay:DLINk?......................................................................................................269
FETCh:DATA:MEAS<i>:ADELay:LOOPback?.............................................................................................. 269
FETCh:DATA:MEAS<i>:ADELay:STATe:ALL?............................................................................................. 267
FETCh:DATA:MEAS<i>:ADELay:STATe?.................................................................................................... 266
FETCh:DATA:MEAS<i>:ADELay:TALoopback?........................................................................................... 269
FETCh:DATA:MEAS<i>:ADELay:TAULink?..................................................................................................269
FETCh:DATA:MEAS<i>:ADELay:TRACe:DLINk[:CURRent]?...................................................................... 268
FETCh:DATA:MEAS<i>:ADELay:TRACe:LOOPback[:CURRent]?...............................................................268
FETCh:DATA:MEAS<i>:ADELay:TRACe:TALoopback[:CURRent]?............................................................ 268
FETCh:DATA:MEAS<i>:ADELay:TRACe:TAULink[:CURRent]?...................................................................268
FETCh:DATA:MEAS<i>:ADELay:TRACe:ULINk[:CURRent]?...................................................................... 268
FETCh:DATA:MEAS<i>:ADELay:ULINk?......................................................................................................269
FETCh:DATA:MEAS<i>:DNSRequests:STATe:ALL?................................................................................... 233
FETCh:DATA:MEAS<i>:DNSRequests:STATe?...........................................................................................233
FETCh:DATA:MEAS<i>:IPANalysis:DPCP:DPAPplic?................................................................................. 252
FETCh:DATA:MEAS<i>:IPANalysis:DPCP:DPConnection?......................................................................... 250
FETCh:DATA:MEAS<i>:IPANalysis:DPCP:DPLayer?.................................................................................. 252
FETCh:DATA:MEAS<i>:IPANalysis:DPCP:DPPRotocol?.............................................................................251
FETCh:DATA:MEAS<i>:IPANalysis:FTTRigger:TRACes<TraceIndex>:FTHRoughput?..............................253
FETCh:DATA:MEAS<i>:IPANalysis:FTTRigger:TRIGger:END?...................................................................254
FETCh:DATA:MEAS<i>:IPANalysis:FTTRigger:TRIGger:STARt?................................................................254
FETCh:DATA:MEAS<i>:IPANalysis:IPConnect:ALL?................................................................................... 248
FETCh:DATA:MEAS<i>:IPANalysis:STATe:ALL?.........................................................................................240
FETCh:DATA:MEAS<i>:IPANalysis:STATe?................................................................................................ 240
FETCh:DATA:MEAS<i>:IPANalysis:TCPanalysis:ALL?................................................................................245
FETCh:DATA:MEAS<i>:IPANalysis:VOIMs:ALL?......................................................................................... 255
FETCh:DATA:MEAS<i>:IPERf:ALL?............................................................................................................. 226
FETCh:DATA:MEAS<i>:IPERf:CLIent?.........................................................................................................226
FETCh:DATA:MEAS<i>:IPERf:SERVer?...................................................................................................... 225
FETCh:DATA:MEAS<i>:IPERf:STATe:ALL?.................................................................................................224
FETCh:DATA:MEAS<i>:IPERf:STATe?........................................................................................................ 224
FETCh:DATA:MEAS<i>:IPLogging:STATe:ALL?.......................................................................................... 238
FETCh:DATA:MEAS<i>:IPLogging:STATe?................................................................................................. 238
FETCh:DATA:MEAS<i>:IPReplay:FILelist?...................................................................................................263
FETCh:DATA:MEAS<i>:IPReplay:STATe:ALL?............................................................................................262
FETCh:DATA:MEAS<i>:IPReplay:STATe?................................................................................................... 262
FETCh:DATA:MEAS<i>:PING:NRCount?..................................................................................................... 218
FETCh:DATA:MEAS<i>:PING:OVERall?...................................................................................................... 218
FETCh:DATA:MEAS<i>:PING:STATe:ALL?................................................................................................. 216
FETCh:DATA:MEAS<i>:PING:STATe?.........................................................................................................216
FETCh:DATA:MEAS<i>:PING?..................................................................................................................... 217
FETCh:DATA:MEAS<i>:THRoughput:OVERall:DLINk?................................................................................231
FETCh:DATA:MEAS<i>:THRoughput:OVERall:ULINk?................................................................................231
FETCh:DATA:MEAS<i>:THRoughput:STATe:ALL?......................................................................................229
FETCh:DATA:MEAS<i>:THRoughput:STATe?............................................................................................. 228
FETCh:DATA:MEAS<i>:THRoughput:TRACe:OVERall:DLINk:EXTended?.................................................230
FETCh:DATA:MEAS<i>:THRoughput:TRACe:OVERall:DLINk[:CURRent]?................................................ 230
FETCh:DATA:MEAS<i>:THRoughput:TRACe:OVERall:ULINk:EXTended?.................................................230
FETCh:DATA:MEAS<i>:THRoughput:TRACe:OVERall:ULINk[:CURRent]?................................................ 230
INITiate:DATA:MEAS<i>:ADELay................................................................................................................. 266
293
R&SCMW-B450A/B/D
List of Commands
INITiate:DATA:MEAS<i>:DNSRequests........................................................................................................232
INITiate:DATA:MEAS<i>:IPANalysis............................................................................................................. 239
INITiate:DATA:MEAS<i>:IPERf..................................................................................................................... 223
INITiate:DATA:MEAS<i>:IPLogging.............................................................................................................. 237
INITiate:DATA:MEAS<i>:IPReplay................................................................................................................ 261
INITiate:DATA:MEAS<i>:PING......................................................................................................................215
INITiate:DATA:MEAS<i>:THRoughput.......................................................................................................... 228
READ:DATA:MEAS<i>:ADELay:DLINk?....................................................................................................... 269
READ:DATA:MEAS<i>:ADELay:LOOPback?............................................................................................... 269
READ:DATA:MEAS<i>:ADELay:TALoopback?.............................................................................................269
READ:DATA:MEAS<i>:ADELay:TAULink?................................................................................................... 269
READ:DATA:MEAS<i>:ADELay:TRACe:DLINk[:CURRent]?........................................................................268
READ:DATA:MEAS<i>:ADELay:TRACe:LOOPback[:CURRent]?................................................................ 268
READ:DATA:MEAS<i>:ADELay:TRACe:TALoopback[:CURRent]?..............................................................268
READ:DATA:MEAS<i>:ADELay:TRACe:TAULink[:CURRent]?.................................................................... 268
READ:DATA:MEAS<i>:ADELay:TRACe:ULINk[:CURRent]?........................................................................268
READ:DATA:MEAS<i>:ADELay:ULINk?....................................................................................................... 269
READ:DATA:MEAS<i>:IPERf:CLIent?.......................................................................................................... 226
READ:DATA:MEAS<i>:IPERf:SERVer?........................................................................................................225
READ:DATA:MEAS<i>:PING?...................................................................................................................... 217
READ:DATA:MEAS<i>:THRoughput:OVERall:DLINk?................................................................................. 231
READ:DATA:MEAS<i>:THRoughput:OVERall:ULINk?................................................................................. 231
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:DLINk:EXTended?.................................................. 230
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:DLINk[:CURRent]?..................................................230
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:ULINk:EXTended?.................................................. 230
READ:DATA:MEAS<i>:THRoughput:TRACe:OVERall:ULINk[:CURRent]?..................................................230
SENSe:DATA:CONTrol:DNS:ASERvices:CATalog?.....................................................................................164
SENSe:DATA:CONTrol:DNS:CURRent:IPVFour:PRIMary:ADDRess?........................................................ 160
SENSe:DATA:CONTrol:DNS:CURRent:IPVFour:SECondary:ADDRess?.................................................... 160
SENSe:DATA:CONTrol:DNS:CURRent:IPVSix:PRIMary:ADDRess?...........................................................160
SENSe:DATA:CONTrol:DNS:CURRent:IPVSix:SECondary:ADDRess?...................................................... 161
SENSe:DATA:CONTrol:DNS:LOCal:CATalog?.............................................................................................163
SENSe:DATA:CONTrol:DNS:TEST:RESults?...............................................................................................165
SENSe:DATA:CONTrol:EPDG:CONNections:IMSI?.....................................................................................203
SENSe:DATA:CONTrol:FTP:USER:CATalog?..............................................................................................169
SENSe:DATA:CONTrol:IMS2:EVENts?........................................................................................................ 173
SENSe:DATA:CONTrol:IMS2:GINFo?.......................................................................................................... 172
SENSe:DATA:CONTrol:IMS2:HISTory?........................................................................................................173
SENSe:DATA:CONTrol:IMS2:MOBile<UE>:STATus?.................................................................................. 175
SENSe:DATA:CONTrol:IMS2:PCSCf:CATalog?........................................................................................... 184
SENSe:DATA:CONTrol:IMS2:RELease:LIST?..............................................................................................177
SENSe:DATA:CONTrol:IMS2:SUBScriber:CATalog?................................................................................... 189
SENSe:DATA:CONTrol:IMS2:VIRTualsub:CATalog?................................................................................... 195
SENSe:DATA:CONTrol:IMS2:VIRTualsub<v>:MTCall:DESTination:LIST?.................................................. 196
SENSe:DATA:CONTrol:IMS2:VIRTualsub<v>:MTSMs:DESTination:LIST?................................................. 200
SENSe:DATA:CONTrol:IPVFour:AUTomatic:ADDResses:CATalog?...........................................................153
SENSe:DATA:CONTrol:IPVFour:CURRent:GIP?..........................................................................................152
SENSe:DATA:CONTrol:IPVFour:CURRent:IPADdress?...............................................................................151
SENSe:DATA:CONTrol:IPVFour:CURRent:SMASk?....................................................................................152
SENSe:DATA:CONTrol:IPVFour:DHCP:ADDResses:CATalog?.................................................................. 153
294
R&SCMW-B450A/B/D
List of Commands
SENSe:DATA:CONTrol:IPVFour:STATic:ADDResses:CATalog?.................................................................153
SENSe:DATA:CONTrol:IPVSix:AUTomatic:PREFixes:CATalog?.................................................................157
SENSe:DATA:CONTrol:IPVSix:CURRent:DROuter?.................................................................................... 155
SENSe:DATA:CONTrol:IPVSix:CURRent:IPADdress?................................................................................. 155
SENSe:DATA:CONTrol:IPVSix:DHCP:PREFixes:CATalog?........................................................................ 157
SENSe:DATA:CONTrol:IPVSix:MANual:ROUTing:CATalog?.......................................................................158
SENSe:DATA:CONTrol:IPVSix:STATic:PREFixes:CATalog?.......................................................................157
SENSe:DATA:MEAS<i>:DNSRequests:RCOunt?.........................................................................................234
SENSe:DATA:MEAS<i>:DNSRequests?.......................................................................................................234
SENSe:DATA:MEAS<i>:IPANalysis:IPConnect:FLOWid?............................................................................ 247
SENSe:DATA:MEAS<i>:IPANalysis:IPConnect:STATistics?........................................................................ 247
SENSe:DATA:MEAS<i>:IPANalysis:TCPanalysis:DETails?......................................................................... 246
SENSe:DATA:MEAS<i>:IPANalysis:TCPanalysis:FLOWid?.........................................................................244
SENSe:DATA:MEAS<i>:IPANalysis:VOIMs:FLOWs?...................................................................................256
SENSe:DATA:MEAS<i>:IPANalysis:VOIMs:JITTer?.....................................................................................257
SENSe:DATA:MEAS<i>:IPANalysis:VOIMs:PERDtx?.................................................................................. 257
SENSe:DATA:MEAS<i>:IPLogging:FNAMe?................................................................................................ 236
SENSe:DATA:MEAS<i>:IPReplay:INFofile?................................................................................................. 263
SENSe:DATA:MEAS<i>:IPReplay:PROGress?............................................................................................ 260
SENSe:DATA:MEAS<i>:IPReplay:TRAFficfile?............................................................................................ 264
SENSe:DATA:MEAS<i>:THRoughput:INTerval?.......................................................................................... 227
SOURce:DATA:CONTrol:DNS:STATe.......................................................................................................... 166
SOURce:DATA:CONTrol:FTP:STATe........................................................................................................... 170
SOURce:DATA:CONTrol:HTTP:STATe........................................................................................................ 171
SOURce:DATA:CONTrol:IMS2:STATe......................................................................................................... 172
SOURce:DATA:CONTrol:STATe...................................................................................................................149
SOURce:DATA:MEAS<i>:NIMPairment:STATe............................................................................................273
STOP:DATA:MEAS<i>:ADELay.................................................................................................................... 266
STOP:DATA:MEAS<i>:DNSRequests...........................................................................................................232
STOP:DATA:MEAS<i>:IPANalysis................................................................................................................ 239
STOP:DATA:MEAS<i>:IPERf........................................................................................................................ 223
STOP:DATA:MEAS<i>:IPLogging................................................................................................................. 237
STOP:DATA:MEAS<i>:IPReplay...................................................................................................................261
STOP:DATA:MEAS<i>:PING.........................................................................................................................215
STOP:DATA:MEAS<i>:THRoughput............................................................................................................. 228
295
R&SCMW-B450A/B/D
Index
Index
Symbols
A
AMR alignment mode ........................................................ 68
Assigning IPv6 address to mobile ..................................... 20
Audio board for IMS .......................................................... 70
Audio codec ...................................................................... 74
Audio delay ..................................................................... 118
Authentication ................................................................... 62
C
Call setup voice over IMS ................................................. 23
Call type ............................................................................ 74
Configuring
DAU IP addresses ...................................................... 18
DAU IP configuration .................................................. 16
DAU measurements ................................................... 22
DAU services .............................................................. 21
Current DAU IP settings .............................................. 39, 40
D
Data application control
DNS tab ...................................................................... 46
ePDG tab .................................................................... 76
FTP tab ....................................................................... 50
HTTP tab .................................................................... 52
IMS tab ....................................................................... 53
IP config tab ................................................................ 40
Overview tab ............................................................... 39
Programming ............................................................ 127
Data application measurements
Audio delay ............................................................... 118
DNS requests ............................................................. 96
IP analysis ................................................................ 101
IP logging .................................................................... 98
IP replay .................................................................... 115
IPerf ............................................................................ 90
Ping ............................................................................. 88
Programming ............................................................ 127
Throughput ................................................................. 94
Data application unit
Data application control .............................................. 38
Data application measurements ................................. 86
Description .................................................................. 11
GUI reference ............................................................. 38
Data pie charts ................................................................ 107
DAU
Web portal .................................................................. 34
Web server ................................................................. 34
DAU unit softkey ............................................................... 85
Delay ............................................................................... 275
DNS requests .................................................................... 96
DNS server info for the mobile .......................................... 48
DNS tab ............................................................................. 46
Drive mapping (DAU) ........................................................ 86
Duplicates rate ................................................................ 283
F
Failure code ...................................................................... 60
Flow throughput and event trigger .................................. 110
Foreign DNS server .......................................................... 49
FTP server settings ........................................................... 51
FTP service type ............................................................... 51
FTP tab ............................................................................. 50
FTP user accounts ............................................................ 52
G
General IMS info area ....................................................... 55
General IMS settings ......................................................... 57
H
Hard disk (DAU)
Change drive mapping ................................................ 86
Using ........................................................................... 33
HTTP tab ........................................................................... 52
Hypertext transfer protocol ................................................ 52
I
IMS config dialog box ........................................................ 57
IMS service status ............................................................. 54
IMS services ...................................................................... 23
IMS softkeys ...................................................................... 54
IMS subscriber settings ..................................................... 61
IMS tab .............................................................................. 53
IMS virtual subscribers ...................................................... 64
Internal DNS entries .......................................................... 49
IP address configuration ................................................... 40
IP analysis ....................................................................... 101
IP config tab ...................................................................... 40
IP connectivity ................................................................. 105
IP logging .......................................................................... 98
IP replay .......................................................................... 115
Iperf
Configuring the mobile ................................................ 36
IPerf ...................................................................................90
IPsec ................................................................................. 63
IPv4 address configuration ................................................ 43
J
Jitter ................................................................................ 275
L
LAN DAU connector .......................................................... 12
LAN DAU status ................................................................ 40
296
R&SCMW-B450A/B/D
Index
Measurements
Configuring, running ................................................... 22
Media endpoint ..................................................................70
Mobile
Iperf configuration ....................................................... 36
Mobile IPv4 address pool .................................................. 44
Mobile-terminating VoIMS calls ......................................... 72
N
Network drive map ............................................................ 86
Network impairments ...................................................... 275
W
Web portal ......................................................................... 34
Web server
Accessing ................................................................... 34
O
OMA XHTML tests ............................................................ 34
Overview tab
Data application control .............................................. 39
Data application measurements ................................. 87
P
P-CSCF address ......................................................... 58, 59
P-CSCF behavior .............................................................. 60
P-CSCF settings ............................................................... 58
Packet loss rate ............................................................... 285
Ping ................................................................................... 88
Private user ID .................................................................. 62
Programming
Data application control ............................................ 127
Data application measurements ............................... 127
Public user ID .............................................................. 64, 66
R
RAN selection ................................................................... 86
Rebooting the DAU ........................................................... 85
Register mobile to IMS ...................................................... 23
Registration expiration time ............................................... 60
Reordering rate ............................................................... 281
Running
DAU measurements ................................................... 22
DAU services .............................................................. 21
S
Select RAN ........................................................................ 87
Signaling type ..............................................................66, 74
SMS over IMS ............................................................. 23, 75
SMS type ........................................................................... 76
Subscriber settings IMS .................................................... 61
Subscription expiration time .............................................. 60
T
Test setup
Data application unit ................................................... 12
Throughput (DAU) ............................................................. 94
U
Use IMS server as ............................................................. 58
297