GAPM Manual
GAPM Manual
(XÖXUP)
4072.4037.32 ─ 15
Monitoring and Network Testing
Manual
© 2017 Rohde & Schwarz GmbH & Co. KG
Mühldorfstr. 15, 81671 München, Germany
Phone: +49 89 41 29 - 0
Fax: +49 89 41 29 12 164
Email: [email protected]
Internet: www.rohde-schwarz.com
Subject to change – Data without tolerance limits is not binding.
R&S® is a registered trademark of Rohde & Schwarz GmbH & Co. KG.
Trade names are trademarks of their owners.
The following abbreviations are used throughout this manual: R&S®GAPM is abbreviated to R&S GAPM. R&S®MBR100 is abbrevi-
ated to R&S MBR100. R&S®MBR200 is abbreviated to R&S MBR200. R&S®MDU100 is abbreviated to R&S MDU100.
R&S®GAF850/900 is abbreviated to R&S GAF850/900.
R&S®GAPM Contents
Contents
1 Characteristics....................................................................................... 7
1.1 Introduction................................................................................................................... 7
1.2 System Overview.......................................................................................................... 8
2 Preparation............................................................................................. 9
2.1 Unpacking and Checking............................................................................................. 9
2.2 General Safety Instructions......................................................................................... 9
2.3 System Setup.............................................................................................................. 10
2.3.1 Desktop Operation........................................................................................................ 10
2.3.2 Rack Mounting.............................................................................................................. 10
2.3.3 R&S GAPM LAN Cabling.............................................................................................. 11
2.3.4 R&S MBR100 Antenna Cabling.................................................................................... 11
2.3.5 R&S MBR100 Backplane Cabling.................................................................................13
2.3.6 R&S MBR200 Antenna Cabling.................................................................................... 15
2.3.7 R&S MBR200 Backplane Cabling.................................................................................17
2.3.8 R&S Target Ping Device (Optional).............................................................................. 18
2.3.9 Voice Biometrics Unit (Optional)................................................................................... 21
2.4 Startup..........................................................................................................................22
3 Operating Concept...............................................................................23
3.1 Client Overview........................................................................................................... 23
3.2 Supplementary Concepts...........................................................................................28
3.2.1 Identity Chains.............................................................................................................. 28
3.2.2 MSISDN Number Normalization................................................................................... 29
3.2.3 SMS Concatenation...................................................................................................... 29
3.2.4 Target Ping....................................................................................................................30
3.2.5 Voice Biometrics Unit.................................................................................................... 31
3.2.6 GPRS Support.............................................................................................................. 36
3.3 Disk and Session Management................................................................................. 37
3.4 Database Migration..................................................................................................... 39
3.5 Data Processing Concepts.........................................................................................40
3.5.1 Primary Filter.................................................................................................................40
3.5.2 Call Records Prioritization.............................................................................................41
Manual 4072.4037.32 ─ 15 3
R&S®GAPM Contents
3.5.3 Truncation..................................................................................................................... 42
3.5.4 Archiving....................................................................................................................... 44
4 Operation at a Glance.......................................................................... 45
4.1 Speaker Identification (Optional)...............................................................................50
4.2 Keyword Spotting (Optional)......................................................................................53
4.3 Language Identification (Optional)............................................................................55
5 Operation.............................................................................................. 57
5.1 R&S GAPM Client-to-Server Connection.................................................................. 57
5.2 Monitoring Channel Information................................................................................61
5.3 Measurement Control................................................................................................. 63
5.4 Managing Call Record Information............................................................................68
5.4.1 View Filter..................................................................................................................... 68
5.4.2 Preferences...................................................................................................................78
5.4.3 Listening to Voice Calls.................................................................................................88
5.4.4 Call Duration................................................................................................................. 96
5.4.5 Voice Prints................................................................................................................... 98
5.4.6 Language Scores.......................................................................................................... 99
5.4.7 Displaying SMS Results..............................................................................................100
5.4.8 Tracking Call Records from the Same Identity............................................................102
5.4.9 Anchoring Call Record View....................................................................................... 103
5.4.10 Adding Bookmarks...................................................................................................... 103
5.4.11 Adding Call Comments............................................................................................... 104
5.4.12 Setting the Call Priority................................................................................................106
5.4.13 Set KC and Reset KC Calculation...............................................................................110
5.4.14 Current KC Calculations..............................................................................................111
5.4.15 Copying Call Record Contents....................................................................................112
5.4.16 Deleting Call Records................................................................................................. 113
5.4.17 Saving Result Files to Disk......................................................................................... 118
5.4.18 Canceling Result File Request....................................................................................118
5.4.19 Exporting Call Data..................................................................................................... 119
5.4.20 Importing or Exporting a Target List............................................................................123
5.4.21 Importing or Exporting a Friend List............................................................................ 125
5.4.22 Importing or Exporting a TAC List............................................................................... 126
Manual 4072.4037.32 ─ 15 4
R&S®GAPM Contents
Manual 4072.4037.32 ─ 15 5
R&S®GAPM Contents
7 Annex.................................................................................................. 237
7.1 Channel Numbers in GSM........................................................................................ 237
7.2 Target and Friend Lists - Export/Import Format.................................................... 237
Index....................................................................................................239
Manual 4072.4037.32 ─ 15 6
R&S®GAPM Characteristics
Introduction
1 Characteristics
1.1 Introduction
The R&S GAPM Test System is a passive GSM monitoring system designed to moni-
tor GSM network traffic in order to detect and statistically evaluate received call events
(voice calls and SMS).
It consists of the following components:
● Multi-band receivers (R&S MBR100 and/or R&S MBR200)
● R&S GAPM server unit (R&S MDU100) including server software
● R&S GAPM client software running on a laptop or desktop PC
● A gigabit switch connecting all the components into a network via RJ45 ethernet
connection
● Omni-directional antennas
● Optional: R&S Target Ping Device Kit (TRM-3T module, USB cable, antenna)
● Optional: R&S Voice Biometrics Unit consisting of Speaker Identification
(R&S GAPM-SID) , Keyword Spotting (R&S GAPM-KWS) and Language Identifica-
tion (R&S GAPM-LID)
● Optional: R&S IMSI Catcher Detection, R&S GAPM-ICD
The R&S MBR100 is capable of receiving signals in the GSM 850 (824 MHz to
894 MHz), GSM 900 (890 MHz to 960 MHz), GSM 1800 (1710 MHz to 1880 MHz) and
GSM 1900 (1850 MHz to 1990 MHz) frequency bands. Normally, for each band two
R&S MBR100s are used, i.e. one for monitoring the uplink (reverse channel) and one
for the downlink (forward channel) between the mobile and the GSM base station.
Each R&S MBR200 can be configured to receive signals from 2 channels at any time
from any combinations of frequency bands and/or uplink/downlink channels.
The R&S GAPM is also capable to monitor in hopping GSM networks. Irrespective of
the GSM channel and the GSM time-slot the target is using at a given network pro-
vider, it will be monitored by the R&S GAPM Test System.
The R&S GAPM server software controls the operations of the R&S GAPM Test Sys-
tem and manages the collected data in the database. The R&S GAPM client software
provides an interactive user interface to retrieve valuable information from the system.
Manual 4072.4037.32 ─ 15 7
R&S®GAPM Characteristics
System Overview
Manual 4072.4037.32 ─ 15 8
R&S®GAPM Preparation
General Safety Instructions
2 Preparation
To remove the R&S GAPM from its packaging and check the equipment for complete-
ness proceed as follows:
1. Pull off the polystyrene protection pads from the rear feet and then carefully
remove the pads from the handles at the front.
2. Pull off the corrugated cardboard cover that protects the rear of the unit.
3. Carefully unthread the corrugated cardboard cover at the front that protects the
handles and remove it.
4. Check the equipment for completeness using the delivery note and the accessory
lists for the various items.
5. Check the delivered items for any damage. If there is damage, immediately contact
the carrier who delivered it. Make sure not to discard the box and packing material.
Packing material
Retain the original packing material. If the R&S GAPM needs to be transported or ship-
ped at a later date, the packing material can be used to prevent control elements and
connectors from being damaged.
Manual 4072.4037.32 ─ 15 9
R&S®GAPM Preparation
System Setup
Overheating
The R&S GAPM should be used in an area where the ambient temperature does not
exceed 0 °C to +40 °C. The R&S GAPM is fan cooled and must be installed with suffi-
cient space along the sides to ensure a free flow of air. Make sure that there is suffi-
cient room for hot air to escape from the equipment.
If the rack is exposed to high ambient temperatures, sufficient ventilation must be
ensured for the rack.
Installation
Do not remove the enclosures when inserting the R&S GAPM in the rack.
Manual 4072.4037.32 ─ 15 10
R&S®GAPM Preparation
System Setup
Connect all devices via a gigabit switch and one of the LAN connectors (see Fig-
ure 1-1).
R&S MDU100 NIC Port 2: The NIC Port 2 is to be used for internal subnet connections
to the MBRs, only use this port for R&S GAPM system setup!
R&S MDU100 NIC Port 1: The NIC Port 1 provides a DHCP client for connection to
other server networks.
2.3.4.1 R&S MBR100 Antenna Cabling without R&S GAF850 / R&S GAF900 Uplink Filter
2.3.4.2 R&S MBR100 Antenna Cabling with R&S GAF850 / R&S GAF900 Uplink Filter
Manual 4072.4037.32 ─ 15 11
R&S®GAPM Preparation
System Setup
Manual 4072.4037.32 ─ 15 12
R&S®GAPM Preparation
System Setup
To ensure that all receivers get the same clock signal, use a so-called Daisy Chain. I.e.
the first receiver provides the second receiver with a reference frequency signal and so
forth. The last receiver provides the first receiver with a reference frequency signal. By
software one of the receivers is set to use the internal frequency as reference fre-
quency. This mechanism ensures that all receivers use the same signal as reference
frequency signal.
Manual 4072.4037.32 ─ 15 13
R&S®GAPM Preparation
System Setup
Figure 2-6: Reference frequency: Daisy-Chain cabling from REF IN X27 to REF OUT X28
Ensure that the reference frequency cabling is always a closed Daisy Chain loop.
For measurement all R&S MBR100 devices have to be switched on regardless of how
many are being used for the current measurement.
The same Daisy Chaining are used for distributing the trigger signal.
Manual 4072.4037.32 ─ 15 14
R&S®GAPM Preparation
System Setup
Figure 2-7: Trigger: Daisy-Chain cabling from Trigger X25 to AUX Audio X11B
Ensure that the trigger cabling is always a closed Daisy Chain loop.
For measurement all R&S MBR100 devices have to be switched on regardless of how
many are being used for the current measurement.
2.3.6.1 R&S MBR200 Antenna Cabling without R&S GAF850 / R&S GAF900 Uplink Filter
For connecting both antennas, connector X11 V/U/SHF No. 1 and V/U/SHF No. 2
needs to be used.
Manual 4072.4037.32 ─ 15 15
R&S®GAPM Preparation
System Setup
2.3.6.2 R&S MBR200 Antenna Cabling with R&S GAF850 / R&S GAF900 Uplink Filter
The following figures show the antenna cabling with R&S GAF900 as an example. For
cabling with R&S GAF850 the same connections are used.
Figure 2-10: R&S GAF900 antenna cabling with R&S MBR200: overview
Manual 4072.4037.32 ─ 15 16
R&S®GAPM Preparation
System Setup
To ensure that all receivers get the same clock signal, use a so-called Daisy Chain. I.e.
the first receiver provides the second receiver with a reference frequency signal and so
forth. The last receiver provides the first receiver with a reference frequency signal. By
software one of the receivers is set to use the internal frequency as reference fre-
quency. This mechanism ensures that all receivers use the same signal as reference
frequency signal.
Figure 2-12: Reference frequency: Daisy-Chain cabling from REF IN X41 to REF OUT X42
Ensure that the reference frequency cabling is always a closed Daisy Chain loop.
For measurement all R&S MBR200 devices have to be switched on regardless of how
many are being used for the current measurement.
Manual 4072.4037.32 ─ 15 17
R&S®GAPM Preparation
System Setup
The same Daisy Chaining is used for distributing the trigger signal.
Figure 2-13: Trigger: Daisy-Chain cabling from Trigger X44 to AUX Audio X17
Ensure that the trigger cabling is always a closed Daisy Chain loop.
For measurement all R&S MBR200 devices have to be switched on regardless of how
many are being used for the current measurement.
To be able to use the Target Ping feature an R&S Target Ping Device is necessary.
This device basically consists of an TRM-3T module where a separate SIM card (not
included) needs to be fixed. The Target Ping SMSs will be sent via the respective pro-
vider of the SIM card.
Each Target Ping SMS may incur costs based on the SIM card provider's terms and
conditions.
The required USB driver is already preinstalled in the R&S GAPM client notebook and
R&S GAPM server unit. If a different client PC/laptop is used, the driver must be instal-
led from the R&S GAPM firmware and utilities CD.
Manual 4072.4037.32 ─ 15 18
R&S®GAPM Preparation
System Setup
Front view
Connection Description
USB mini B connector Data connection to R&S GAPM client notebook or R&S GAPM
server unit
LED display (3 LEDs) Status indicator (for network and operating status)
Rear view
Connection Description
Miniature SIM card holder Slider for 3.0 V and 1.8 V SIM cards
Manual 4072.4037.32 ─ 15 19
R&S®GAPM Preparation
System Setup
For the operation a miniature SIM card (3.0 V or 1.8 V, according to the guideline in
GAM 11.12) is needed.
The SIM card must be inserted into the holder ("slider") on the back.
Make sure that the modem is switched off (USB disconnected).
Press the small yellow button next to the drawer of the holder. The slider will then be
moved out a little bit.
Pull out the slider and insert the SIM card. Pay attention to the correct position. In the
slider there is a small cut off corner so that the SIM card can only be used in the
defined position.
Carefully push the slider back into the TRM-3T module. The slider must move in easily
and must not be wedged.
Manual 4072.4037.32 ─ 15 20
R&S®GAPM Preparation
System Setup
LED display
There are 3 LEDs (red, yellow, green) used for checking the GSM and operating sta-
tus.
Table 2-4: USB status indication (red LED)
The Voice Biometrics Unit (VBU) consists of Speaker Identification (SID), Keyword
Spotting (KWS) and Language Identification (LID). These components of the VBU are
Manual 4072.4037.32 ─ 15 21
R&S®GAPM Preparation
Startup
optional and require a software license. To use these optional components, the follow-
ing is required:
● The VBU installation package RSVoiceBiometrics-<xxx>.<xxx>.deb which is sup-
plied on its own installation CD.
● An R&S GAPM dongle having SID and/or KWS and/or LID option activated.
● An additional SID/KWS/LID-specific dongle.
Install the VBU installation package together with the R&S GAPM software on the
same R&S MDU100/MDU200 or on a dedicated R&S MDU100/MDU200 if certain per-
formance requirements shall be met.
Connect an R&S GAPM dongle having the SID/KWS/LID option enabled to a USB
port.
Connect the SID/KWS/LID-specific dongle to a USB port.
2.4 Startup
After correct setup all devices may be switched on.
The R&S MBR100/R&S MBR200 and the laptop are configured to obtain their IP
address via DHCP.
The R&S MDU100 provides the DHCP service.
The R&S MDU100 booting time is about 3 minutes.
Ensure that the time between switching on R&S MDU100 and R&S MBR100/
R&S MBR200 is less than 2 minutes.
Manual 4072.4037.32 ─ 15 22
R&S®GAPM Operating Concept
Client Overview
3 Operating Concept
Manual 4072.4037.32 ─ 15 23
R&S®GAPM Operating Concept
Client Overview
A status bar at the bottom of the screen provides quick feedback on connection status
with host server, message transaction load between client and server, and the hard-
ware status.
In between the toolbar and the status bar is the main view area. It consists of multiple
views displaying different information related to the monitored mobile services. The
views are designed to provide an overall perspective at a glance and to focus on spe-
cific data that is of any interest.
Manual 4072.4037.32 ─ 15 24
R&S®GAPM Operating Concept
Client Overview
The R&S GAPM client consists of views, which can be docked within the main view or
floated as a top-level view on the desktop. All views can be moved, resized and closed
if not needed.
Views can also be closed by clicking the "Close" button on the view’s title bar.
Similarly, views can be opened or closed via the main menu, under "View".
When exiting the program, all locations, sizes and states (docked or undocked, open or
closed) of the views are stored so that the next time the program is launched it will
remember its previous settings.
Manual 4072.4037.32 ─ 15 25
R&S®GAPM Operating Concept
Client Overview
Once the R&S GAPM Test System has been started, the channel and call information
populating the "Channel Information" and "Call Record Information" views can be seen.
In the "Call Record Information" view, all detected mobile services will appear as
records (each record occupying one row). The latest record will be inserted at the top
of the view. As there could be new records being detected all the time, older call
records will move downwards. To lock the view to the scrollbar position, enable the
"Anchor" button on the toolbar. Locking the view often makes it easier to look at the
records.
For each call record, useful information such as called/calling number, whether it is a
voice or SMS call, its IMEI, IMSI or TMSI value, MCC-MNC, LAC, etc, can be seen.
These are the call metadata in the call records.
Some of the call metadata may not be available which is indicated by an empty cell in
the call record table.
Typical reasons for missing call metadata are:
● The data has not been transmitted between BTS and MS for the respective call.
● The message transmitting this information could not be decoded due to receiving
conditions, for instance the uplink could not be received with the present antenna
configuration.
● The data has been transmitted in a ciphered part of the communication and no
deciphering key is available.
Manual 4072.4037.32 ─ 15 26
R&S®GAPM Operating Concept
Client Overview
Under certain circumstances the content of a call event may be decoded. This is the
case if the content is transmitted unciphered or if a deciphering key is provided. In this
case the "Call Record State" column contains information about the current processing
state. The "Termination Cause" column may give more detailed information on how the
process of decoding terminated. The "Call Record State" column is color-coded so that
the states can be easily identify at a glance. To customize the color code, refer to
Chapter 5.4.2.1, "Call Record Cell Colors", on page 78.
The "Service Request Type" column shows the type of call event being decoded. It can
either be a Call Request, an SMS, a Location Update Request or some other known
requests. Depending on the information received on air this attribute might not be avail-
able in all cases, or only after decoding, in which case "Unknown Request" will be dis-
played.
All the Call Records will be assigned an ID (Call Record ID). Older session databases
that are migrated may still contain call records that are not assigned any IDs and are
simply referred to as "Archived".
Manual 4072.4037.32 ─ 15 27
R&S®GAPM Operating Concept
Supplementary Concepts
Call records listed in the view can be filtered to narrow down the search. This helps to
display only call records that are of interest, and also to set up a target list that can be
stored on the server. To customize the view filter, refer to Chapter 5.4.1, "View Filter",
on page 68.
Each received call record originates from a mobile phone identity, which refers to a
SIM card having an IMSI and a temporarily valid TMSI.
The R&S GAPM Test System identifies call records that belong to the same identity,
and links up all those call records in the database with Identity Chains. This process is
automatically performed whenever new call records are received or relevant informa-
tion pertaining to the mobile phone identity within the call records are updated.
Call records with the same IMSI will be linked into an Identity Chain.
A mobile phone will only transmit its IMSI under certain conditions, therefore it is possi-
ble that no call records containing the IMSI from a mobile phone entity were received
within the recording session. In this case, the system may still identify call records that
belong to the mobile phone entity based on the TMSI that has been transmitted. The
system will track and take into account any further TMSI changes (such as during
TMSI reallocations) within a call appropriately.
Identity chains mainly serve the following purposes:
Manual 4072.4037.32 ─ 15 28
R&S®GAPM Operating Concept
Supplementary Concepts
● A call record's information is enhanced with another call record's information that
belongs to the same identity.
● Cipher keys may be applied to a number of call records.
● The Target and Friend List processing procedures are closely related and apply
the Identity Chains functionalities.
● The identity relationships of call records are valuable information. When a call
record is selected in the "Call Record Information" view, all the records belonging
to the same identity will be displayed in rows of light blue color. Refer to Chap-
ter 5.4.8, "Tracking Call Records from the Same Identity", on page 102.
The subscriber telephone number for both voice call and SMS may be displayed in the
"Remote/Target Number" column.
The call record service request type "SMS Request" consists of one or several RPDU
packets. The RPDU packets are independent of the direction of the call setup (MO or
MT), they are not necessarily related and they may be individual SMSs or parts of a
concatenated SMS. They can also have different directions (SC -> MS, MS -> SC).
That means that from one SMS Request may come several SMS records or none if it
contains a part of a concatenated SMS, which was already partially captured. For SMS
Request call records, the "SMS Content" column stays empty and in the "Results" view
each RPDU packet is separately displayed.
Manual 4072.4037.32 ─ 15 29
R&S®GAPM Operating Concept
Supplementary Concepts
The call record service request type "SMS" contains the captured SMS that may have
been combined from several RPDUs and the SMS Request call records. Therefore
there is no "Termination Cause". The SMS call records may have the content of the
captured SMSs displayed in the "SMS Content" column. For a concatenated SMS, the
whole message will be displayed in the "Results" view, together with some additional
comments.
The "Target Ping"’ feature allows to covertly reveal a target’s presence if it is within the
receiving range of the R&S GAPM Test System. If only the MSISDN of a target is
known, Target Ping may help to reveal more of the target’s identity parameters such as
the IMSI, IMEI and/or TMSI.
The Target Ping device pings the target with a known MSISDN by first sending out a
silent SMS to the real network via the air interface. The network provider transfers the
silent SMS via the provider backbone to the BTS nearest to the target. The BTS then
sends the silent SMS to the target via the air interface. The target receives the silent
SMS, such that the silent SMS will not be visible nor notified to the target.
If the target is still within the receiving range of the R&S GAPM Test System, the target
can be traced in the "Call Record Information" view.
The configuration of the Target Ping device can be found in Chapter 5.7.4, "Other
Devices Configurations", on page 203.
The target can be pinged from the Target List as seen in Chapter 5.6.1, "Sending Tar-
get Ping", on page 169.
Manual 4072.4037.32 ─ 15 30
R&S®GAPM Operating Concept
Supplementary Concepts
Provider check
There is no control of the silent SMS once it is sent out through the air interface to the
SMSC. Network providers may check the SMS for reserved flags for network internal
purposes, resulting in modification of certain flags, or possibly even isolating the SMS
to prevent it from being forwarded out to the target. Although there are various meth-
ods to keep the SMS silent on the target mobile device, it is unlikely that it will remain
silent due to network provider intervention. Thus it is recommended to perform a pro-
vider check on suitable providers before sending out silent SMSs to the real target. The
provider checks will reveal if important flags are removed by the SMSC.
For information on how to perform a provider check refer to Chapter 5.7.4, "Other Devi-
ces Configurations", on page 203.
The Target Ping device provides the Target Ping feature without the requirement of
special support from the network provider.
In some cases, it may be advantageous to send a Target Ping SMS directly to the
SMSC, for instance through the SS7 line, provided that appropriate agreements can be
arranged with the network providers or middlemen. Rohde & Schwarz may provide
technical support in order to connect the R&S GAPM with an external interface on a
project-specific basis.
Introduction
The optional Voice Biometrics Unit (VBU) consists of Speaker Identification, Keyword
Spotting and Language Identification based on audio samples which have been collec-
ted from a target identified for surveillance. The VBU is a software module running in
its own process provided as a dedicated installation package. The VBU can share the
same hardware with a R&S GAPM installation or – if advanced performance require-
ments shall be met – installed on a dedicated server hardware. Appropriate licenses
are available for purchase depending on:
● The number of processor cores to be used by the VBU.
● The kind of required voice biometrics functionality, i.e. Speaker Identification (SID),
Keyword Spotting (KWS) or Language Identification (LID).
Manual 4072.4037.32 ─ 15 31
R&S®GAPM Operating Concept
Supplementary Concepts
The VBU provides its services via a network interface which is already supported by
the R&S GAPM. The services are not limited to the R&S GAPM, but also available to
arbitrary client applications if the VBU network interface is implemented with a known
network address.
Speaker Identification
The Speaker Identification module (SID) creates biometric voice prints based on audio
samples. Supported audio formats are:
● The R&S GAPM-specific pck format
● Uncompressed wave format,1 or 2 channels, 16 bits per sample and channel
The voice prints returned by the VBU to the client are binary data blocks, not depend-
ing on language, containing a set of parameters characterizing the speaker related to
the audio sample. An important parameter, when creating voice prints from audio sam-
ples, is the minimum Net Speech Length(NSL). During generation of voice prints from
audio samples, the SID determines the actual length of net speech content. An
increasing amount of NSL corresponds to better quality of the generated voice prints.
Therefore, a sufficient amount of Net Speech Length is desirable, especially when cre-
ating voice prints which shall serve as a reference when defining voice print targets in
the R&S GAPM.
Manual 4072.4037.32 ─ 15 32
R&S®GAPM Operating Concept
Supplementary Concepts
The second crucial functionality of the SID is to compare pairs of voice prints and cal-
culate a score value telling how similar the speakers in both audio samples are. The
valid range of scores calculated by the SID is between 0 and 100. If searching for real
life matches, only scores above 90 are of actual interest. The fine tuning of the appro-
priate score threshold (to consider a pair of voice prints matches each other) depends
on the quality and source of the audio samples and requires real time evaluation.
The R&S GAPM fully supports the Speaker Identification interface. If enabled, for each
link direction decoded and minimum Net Speech Length fulfilled, a voice print is cre-
ated and stored in the session. Each new voice print is compared to all reference voice
prints defined in the target attributes. Based on the calculated score and the score
threshold defined in the voice biometrics settings dialog, matching call records are pre-
sented in the target list view. The basic workflow for identifying speakers based on
voice print targets comprises the following steps:
1. Enable SID and set the appropriate configuration parameters, refer to Chap-
ter 5.7.5, "Voice Biometrics Unit", on page 206
2. Define voice print targets. These can be based on available audio samples or on
decoded call records in the current session. Refer to Chapter 5.6.3, "Creating
Voice Print from Wave File", on page 176 and to Chapter 5.6, "Target and Friend
Lists", on page 154.
4. The R&S GAPM creates voice prints for each decoded or decoding call with
respect to the configured minimum Net Speech Length. The status of the voice
print calculations for each call record can be checked in the voice print column in
the call record view. Refer to Chapter 5.4.5, "Voice Prints", on page 98.
Manual 4072.4037.32 ─ 15 33
R&S®GAPM Operating Concept
Supplementary Concepts
5. Analyze and fine tune the target matches by using the tools provided by the target
list widget and adjusting the score threshold of SID.
Keyword Spotting
The Keyword Spotting (KWS) module allows defining keywords by entering text and
specifying the corresponding language (i.e. dictionary) in the target list editor. The type
of languages and number of processor cores can be used depending on the purchased
licenses. If enabled, KWS processes the speech content of decoded call records and
searches for the available uplink and downlink audio stream, for matching keywords
regarding the specified language. A confidence value is calculated for each language-
dependent keyword detected in the voice call record. All candidates having a confi-
dence value less than the configurable "Accept Threshold" are discarded, the remain-
ing candidates are stored and can be filtered by adjusting the "Confidence" parameter
which determines whether a candidate is considered as a target.
The basic workflow for using Keyword Spotting comprises the following steps:
1. Configure the correct hostname or IP address and port of the system where the
Voice Biometrics Unit is running.
2. Enable KWS.
3. Define targets for KWS. For details, refer to Chapter 5.6.5, "Defining Targets for
Keyword Spotting", on page 184
4. Check if a reasonable "Acceptance Threshold" has been configured and set the
confidence value.
Manual 4072.4037.32 ─ 15 34
R&S®GAPM Operating Concept
Supplementary Concepts
6. Analyze the candidates that provide matches and improve the recognition rate by
adjusting the confidence value.
Language Identification
The Language Identification (LID) module allows to detect languages in provided audio
samples. The number of processor cores used for language identification depends on
the type of purchased licenses. If enabled, LID processes the speech content of deco-
ded call records and determines a rank of detected languages for the available uplink
and downlink audio stream. Detected languages are discarded if the corresponding
score does not exceed the configured "Discard Threshold" and "Relative Score [%]".
The later configuration parameter defines a second threshold "Thresh2nc"- depending
on the best score found - which must be exceeded by a language score to be assigned
a rank:
Thresh2nd = Scorebest * Threshrel % / 100
Only languages meeting these two requirements are stored for each call record and
link direction. Languages can be used for filtering call records and for defining target
definitions with language attributes.
1. Configure the correct hostname or IP address and port of the system where the
Voice Biometrics Unit is running.
2. Enable LID
3. Define targets with certain languages. For how to define language attributes, refer
to Chapter 5.6.6, "Defining Targets with Language Attributes", on page 186
4. Check if a reasonable "Discard threshold" and "Relative Score" have been config-
ured.
Manual 4072.4037.32 ─ 15 35
R&S®GAPM Operating Concept
Supplementary Concepts
6. Analyze the candidates that provide matches and improve the recognition rate by
adjusting the configuration parameters.
For enabling GPRS support in the Server Configurations tab, refer to Chapter 5.7.1,
"Server Configuration", on page 192
Enabling GPRS support imposes significant load to the server, hence it is recommen-
ded to disable GPRS support if it is not needed.
If GPRS is enabled, the R&S GAPM detects temporary block flows (TBF) during replay
or measurement. If a Temporary Logical Link Identifier (TLLI) could be associated with
a TBF, a related call record with service request type “TBF” is created and stored in the
current session. All decoded TBFs sharing the same TLLI, mobile network code (MNC)
and mobile country code (MCC) are combined to a TBF call record in the session data-
base. The TLLI is displayed in the TMSI column.
When decoding temporary block flows, the R&S GAPM decodes the RLC/MAC layer
and writes LLC messages to the corresponding result files. The LLC messages can be
displayed by selecting a TBF record in the call record information view and opening the
message sequence chart (MSC) in the result view. The MSC provides information
about the addressed Service Access Point (SAPI) and the layer protocol on top of LLC.
If no encryption is applied, the payload (e.g. IP data) carried by the SNDCP layer, can
be exported by using the call data export. The payload data is exported into text files if
“WAV/TXT” is checked.
Manual 4072.4037.32 ─ 15 36
R&S®GAPM Operating Concept
Disk and Session Management
Figure 3-16: Export call data dialog with "WAV/TXT" checked for export of IP data
When the decoded messages of the currently selected TBF record are displayed, the
following GPRS specific message layer types are supported:
● RLC/MAC
● LLC: The layer type is followed by the decoded service access point identifiers
(SAPI)
Manual 4072.4037.32 ─ 15 37
R&S®GAPM Operating Concept
Disk and Session Management
The R&S MDU100 server is equipped with up to three internal disks. Optional external
storage devices may be attached to the USB ports. Apart from the system disk usually
installed at drive bay 0, all disks are hot-swappable. All disks, including the system
disk, can be used to store data, i.e. databases, session and recording files.
A database serves as a container for sessions, as well as for a target/friend list which
applies to the contained sessions. Deleting an entire database hence will delete all
contained sessions and the target/friend list.
A session mainly serves as container for call records and decoding results. Depending
on the presence of optional devices, they may also contain additional data like GPS
information, antenna matrix information, etc.
If data recording is enabled, a recording file stores the entire raw data incoming from
the R&S MBR receivers. This provides the opportunity to recreate all call records and
decoding results from the recording file. Recording files are physically located at disk
level. However, a session may hold links to recording files.
Replay is initiated at session level and means replaying all recording files linked to the
session in chronological order. A recording file linked to a session is not necessarily
located at the same disk. A session may even have links to recording files on several
disks. Together with hot-swapping, data recording may thus be distributed onto more
disks than the system can be equipped with at a time, without stopping and restarting
the measurement.
Manual 4072.4037.32 ─ 15 38
R&S®GAPM Operating Concept
Database Migration
Figure 3-18: Session management view showing a session that needs migration
The sessions within the database can have the following states, which are displayed in
the "Status" column (see the figure above).
● "Ready" - Shows that the session is compatible with the current software version
and it is ready to be opened if required.
● "Needs Migration" - Shows that the session is using an old software version and
it will need to be migrated in order to be used with the current client software ver-
sion. Right-click on the session and select "Open Session" in the context menu.
A "Confirmation Request" dialog box will appear to confirm the migration of the
session. Click "OK" to start migration.
Manual 4072.4037.32 ─ 15 39
R&S®GAPM Operating Concept
Data Processing Concepts
Figure 3-21: Session "Demo Test" successfully migrated and opened for use
The R&S GAPM is able to detect all active GSM calls in the bands that it is monitoring.
Furthermore, it also allows a more focused monitoring by using filters to select calls
with specific criteria.
The highest level filtering is performed via the primary filter. All the call records that are
received by the R&S MBR receivers will be filtered by the primary filter before being
sent to the session database.
Filtering of the call records can be further refined with the custom filter and target fil-
ters. These filters provide a filtered selection of call records from the session database
to be displayed on the client GUI software in the "Call Records Information" view.
The R&S GAPM does not normally require the use of a primary filter since it has no
limitations regarding the number of GSM channels that can be monitored concurrently.
Primary filters can be helpful to reduce the amount of session data and/or operational
setups such as excluding local networks from being monitored in border control sce-
narios.
Manual 4072.4037.32 ─ 15 40
R&S®GAPM Operating Concept
Data Processing Concepts
Primary filter settings do not affect the data stored in recorded files. This means that a
recording contains all the call records, even if primary filters were applied during
recording.
All the call records will be displayed in the "Call Record Information" view if the file is
replayed with primary filters disabled.
Each call record has a priority value that controls the assignment of resources during a
measurement. The relevant resources are calculation slots for key recovery and call
decoding slots. Call records with a higher priority value will be processed before call
records with a lower priority value.
The priority values from 1 to 100 have no significance during replay where only priority
value 0 will have an effect.
The default priorities per service request type can be adjusted in Chapter 5.5.5.3, "Pri-
ority Settings", on page 150.
The call records of a certain service type may be skipped by assigning priority value 0.
Priority value 0 is effective for replay as well, although other priority values will have no
effect on replay.
Manual 4072.4037.32 ─ 15 41
R&S®GAPM Operating Concept
Data Processing Concepts
3.5.3 Truncation
Data truncation allows the system to reduce the amount of data that is stored in a ses-
sion by deleting call records according to certain filtering rules. This will allow the size
of the data that is stored in the session to be significantly reduced when not all the call
record events are of specific interest.
A typical truncation setting is to delete the call records that could not be decoded or are
of minor interest, such as the Location Update Request records, while retaining all the
target-related call records.
The relevant settings can be adjusted in Chapter 5.5.5.2, "Truncation Filter Settings",
on page 148.
Preconfigured truncation settings that are installed together with the client software can
also be loaded to be applied.
Truncation can be applied as follows:
● Periodically.
● When a session becomes idle, e.g. because all the call records have been pro-
cessed, after stopping the measurement or replay.
● When a session is closed.
The periodical truncation is closely tied to the demodulation buffer processing. The fol-
lowing diagram shows an overview of the data processing time sequence.
Manual 4072.4037.32 ─ 15 42
R&S®GAPM Operating Concept
Data Processing Concepts
Figure 3-22: Data processing time sequence for truncation and archiving call records
The incoming demodulation burst data is filled into the demodulation data buffer. Once
the buffer is filled up to its entire size, the oldest data is deleted in order to give space
for new incoming data, working like a large FIFO (First-In-First-Out). The time the
demodulation buffer will cover depends on the on-the-air occupancy of the GSM time
slots. In the worst-case scenario, it would suffice to be able to hold about five minutes
of traffic. However, in practice, the occupancy rate is much lower than this, with the
buffer time typically being larger than 30 minutes.
Call records that have a starting time after the buffer time limit, meaning that they can-
not be decoded anymore due to the lack of demodulation data, will become the target
for the periodic truncation. Call records that are 'younger' may still be decoded for any
useful information, as they may turn out to contain target-relevant records.
Manual 4072.4037.32 ─ 15 43
R&S®GAPM Operating Concept
Data Processing Concepts
Truncation takes place before archiving. Therefore in the event that call records are
moved to an archived session, the call records will be truncated consistently while
applying the current truncation settings.
3.5.4 Archiving
The R&S GAPM can operate over a long period of time with adequate hard disk space
resources. Although the system may handle large databases, the size still needs to be
limited to meet the real-time processing requirements and responsiveness to client
requests. Automatic archiving here will assist by continuously moving older records of
the active session into archived sessions.
The advantages of automatic archiving is that it is performed in the background without
the need to stop the current measurement and start a new measurement manually.
This will ensure that the call records are being recorded all the time instead of having
any unrecorded call records due to the lapse while stopping and starting a measure-
ment. Furthermore, identity chains will not be disrupted this way, which is important for
target detection and key reuse.
During replay of a recording file, the data may be processed into a session that is iden-
tical to those of the previous measurement or a previous replay. Within the active ses-
sion, duplicates of call records will be eliminated and relevant data will be reused. In
order to allow archived data to be reused in the same fashion, the system uses a new
generation of archived data for any new replay represented by a replay index. For a
new replay, the archives of the previous generation will be consumed into the active
session, effectively acting like a big virtual session.
Manual 4072.4037.32 ─ 15 44
R&S®GAPM Operation at a Glance
4 Operation at a Glance
This chapter describes the steps to perform some basic operational tasks. It shall pro-
vide a quick start guide when operating the system. It is assumed that the system is
set to its factory defaults.
Step 1: Prepare the system as described in Chapter 2, "Preparation", on page 9.
Step 2: Connect the client to the server.
Click on the "Connect" button to launch the "Connection Settings" dialog box.
In field "Host IP" enter the R&S MDU100 host address and click the "OK" button.
If connection is successful, the status bar shows "Connected".
Step 3: Perform the basic configurations.
Open the "Configuration Settings" view by clicking the "Configuration Settings" button
in the toolbar.
Make sure all R&S MBR100/R&S MBR200 receivers are configured to downlink and
uplink bands appropriate for the target GSM network environment.
Manual 4072.4037.32 ─ 15 45
R&S®GAPM Operation at a Glance
Manual 4072.4037.32 ─ 15 46
R&S®GAPM Operation at a Glance
On the "Session Management view", you can create a new DB and a new session on
the system disk.
Open the "Channel Information" view:
The "Channel Information" view displays the channel information data.
Manual 4072.4037.32 ─ 15 47
R&S®GAPM Operation at a Glance
Manual 4072.4037.32 ─ 15 48
R&S®GAPM Operation at a Glance
The call records appear in the "Call Record Information" view where call records can
be displayed and managed.
Figure 4-8: Call records streaming into call record information view
Manual 4072.4037.32 ─ 15 49
R&S®GAPM Operation at a Glance
Speaker Identification (Optional)
The "Session Management" view shows how the file is written to the disk.
Step 6: Stop the measurement.
Click the "Stop" button to stop the measurement.
Step 7: Start a replay.
Click the "Start Replay" button. The recorded and current call records appear in the
"Call Record Information" view.
Manual 4072.4037.32 ─ 15 50
R&S®GAPM Operation at a Glance
Speaker Identification (Optional)
Step 3: Configure and activate a call record filter to display all decoded calls and
show the column "Voice Prints" in the call record view.
The changing background colors and arrows in the voice prints column indicate for
which call records voice prints are calculated by the VBU.
Manual 4072.4037.32 ─ 15 51
R&S®GAPM Operation at a Glance
Speaker Identification (Optional)
Step 3: Select a call record having a voice print and define a target based on the
remote (i.e. downlink) voice print.
Manual 4072.4037.32 ─ 15 52
R&S®GAPM Operation at a Glance
Keyword Spotting (Optional)
Step 4: The call record selected in Step3 should generate in the target list view
as a matching record with score value 100.0.
Figure 4-13: Display of matching identities and corresponding score value calculated by SID
By dragging the score slider for "SID Score" in the target list view, the threshold for
speaker identification can be adjusted.
Manual 4072.4037.32 ─ 15 53
R&S®GAPM Operation at a Glance
Keyword Spotting (Optional)
Step 2: Open the Voice Biometrics Unit, configure the correct VBU host and port
and enable Keyword Spotting.
Make sure that "Enable Keyword Spotting" is checked and the mandatory dictionaries
have a green check mark.
Step 3: Check the speech content of decoded call records and identify some
keywords suitable for target definition.
Step 4: Define the keywords identified in step 3 as targets.
For details about defining keyword spotting targets, refer to Chapter 5.6.5, "Defining
Targets for Keyword Spotting", on page 184.
Step 5: Check the identity records displayed in the target list view and optimize
the detection result by adjusting the confidence value with the slider.
Manual 4072.4037.32 ─ 15 54
R&S®GAPM Operation at a Glance
Language Identification (Optional)
Figure 4-17: Match records found before adjustment of the confidence value
Figure 4-18: Match records found after adjustment of the confidence value
Step 6: Display and select the call record containing the keyword and open the
call result view with “KWS” checked.
The call result view displays markers where the keywords were detected in the audio
stream.
Manual 4072.4037.32 ─ 15 55
R&S®GAPM Operation at a Glance
Language Identification (Optional)
Step 3: Find decoded calls having a language entry in the column "Language
Scores"
Step 4: Define languages identified in step 3 as targets. For details how to define
language targets refer to Chapter 5.6.6, "Defining Targets with Language Attrib-
utes", on page 186
Manual 4072.4037.32 ─ 15 56
R&S®GAPM Operation
R&S GAPM Client-to-Server Connection
5 Operation
If there is another client connected to the server, the "Logon Request" dialog box will
display the name of the user that is currently connected to the server.
Manual 4072.4037.32 ─ 15 57
R&S®GAPM Operation
R&S GAPM Client-to-Server Connection
Manual 4072.4037.32 ─ 15 58
R&S®GAPM Operation
R&S GAPM Client-to-Server Connection
The server name or the IP address can be entered. For example, "gapm101025" which
is the server name and the IP address 172.25.xxx.yyy (please confirm the IP address
of the R&S GAPM server unit) can be both used. The "Default Port" button will set the
client port number to a default value. The port number must be a value from 1 to
65535. The client needs to be set with the same port number that the server unit is
configured with. The standard installation of the R&S GAPM server will always be con-
figured with the default port of 3210. The connection dialog box can also be launched
from the main menu ("File"> "Connect").
The R&S GAPM client provides a status bar to display basic system status data. The
left-most field shows the client-to-server network connection status. It also displays the
R&S GAPM host server address, connected user name and connected server port.
The second field shows the message traffic loading between client and server.
The third field shows the generic load information between client and server.
Manual 4072.4037.32 ─ 15 59
R&S®GAPM Operation
R&S GAPM Client-to-Server Connection
Figure 5-9: Connection rejected due to another client currently connected to server
Click the "OK" button to force the client to disconnect from the server, or "No" to exit
without connecting.
Figure 5-10: Connection successful by forcing the other client to disconnect from the server
The other client will be disconnected from the server, and a dialog box will appear on
the client's display.
Figure 5-11: Other client's display to inform on a forced disconnection from the server
Manual 4072.4037.32 ─ 15 60
R&S®GAPM Operation
Monitoring Channel Information
Make sure that the specific user has been added into the server's access list, and the
correct credentials are recorded in the access list that is obtained from the server.
There is an access control feature which allows only specific users that are listed in an
access list to be able to get connected to the server. If the access list is not configured
by the system administrator, the system will allow access for all users. Refer to Chap-
ter 5.7.7, "Server Administration", on page 215 on how to configure the access list.
The status bar will display "Disconnected", and all the views will be cleared.
When the application is closed, it will automatically disconnect from the server. Discon-
nection can also be triggered from the main menu ("File" > "Disconnect").
The R&S GAPM client is always updated with the latest data from the server. However,
requests can still be made to reload the client’s data from the server. This allows some
of the status information, such as the network traffic monitoring, to be reset.
Manual 4072.4037.32 ─ 15 61
R&S®GAPM Operation
Monitoring Channel Information
The view is empty when the client is not connected to the server. Once connected, it
will start to display information from the server.
The received signal level is displayed by bars. The range is between -110 dBm and
0 dBm.
Under each bar a percentage is displayed. The percentage indicates the rate of suc-
cessfully decoded frames in the last update interval. The light green corresponds to
100% and the red corresponds to 0%. There is a full range of colors in between
depending on the percentage value.
The value under the percentage is the bit error rate. For the first ARFCN (1) it is 0e-03
(0 * 10-3 = 0.000 = 0). For the second it is 16e-03 = 16 * 10-3 = 0.016. The value is
calculated by the system considering ONLY the frames successfully decoded.
The channel information data is periodically updated.
Double-click on a specific channel or press the ENTER key to get more data as shown
below:
Manual 4072.4037.32 ─ 15 62
R&S®GAPM Operation
Measurement Control
Select the folder and save the channel information as a .CSV file.
Manual 4072.4037.32 ─ 15 63
R&S®GAPM Operation
Measurement Control
This view provides access to the typical operations like starting and stopping a mea-
surement, starting and stopping data recording, starting and stopping a replay.
Starting a measurement
All Call Record data produced by measurement will be stored into a session. Define
the target session in the "Select Session" box of the "Measurement Control" view by
first selecting a disk and a database. Then enter an appropriate name for a new ses-
sion. The session will be located within the selected database on the selected disk.
In order to create a new session use "New Session..." in the "Session Management"
view.
For cases where the measurement data is to be added to the data of a previous mea-
surement or replay, the "Session" field allows an existing session to be selected as
well.
Manual 4072.4037.32 ─ 15 64
R&S®GAPM Operation
Measurement Control
Data recording can be started immediately at measurement start, or later during mea-
surement. To start the data recording at measurement start, select a disk in the
"Recording File" box. Note that this does not necessarily need to be the same disk
where the session is located. Enter a file name for the data recording file. Upon clicking
the "Generate Filename" button the system will create a name containing the current
date and time. This name can be changed afterwards. Tick the "Enable Recording"
checkbox. Once the "Start Measurement" button is clicked, the system creates the
recording file while starting the measurement.
Data recording can also be started at a later time, however, by executing the same
steps.
Recording can be stopped at any time by simply unticking the "Enable Recording"
checkbox. In this case the file will be closed.
Each recording file written in the context of a session is automatically linked to that
session. The "Replay/Measurement" box lists all recording files linked to the currently
selected session. If a recording file is currently being written, its current size will be dis-
played.
Supposed that a recording is being stopped by unticking the "Enable Recording"
checkbox. Then a new file name is entered and the recording is started again. For the
time when no recording was active, no data will be recorded to either file. In order to
ensure that the complete data without gap is stored while opening a new file, use the
button "New Recording" after entering a new file name.
Replaying
A session with one or more links to recording files can be replayed. A session created
during measurement with data recording enabled can be replayed at once, because
recording files created during measurement will be automatically linked to the session.
To start a replay, select the session in the "Select Session" box and click the "Start
Replay" button.
The replay speed can be adjusted with a "Replay Speed" slider. The minimum value of
0.0 corresponds to pausing the replay, and the maximum value of 3.0/Max causes the
replay to speed up to the maximum permissible speed of the system.
Click the "Set Realtime" button to set the replay speed value to 1.0 in order to emulate
the behavior and speed of a live measurement.
Click the "Set Max Replay Speed" button to set the replay speed value to 3.0/Max in
order to obtain the optimum maximum speed of replay from the system.
Recording files can be manually linked to a session within the "Session Management"
view.
The session recorded during a measurement may contain additional information like
GPS data, antenna matrix switching information, etc. Linking recording files to a new
session and replaying them may lack this additional information in comparison to
replaying the original session.
Manual 4072.4037.32 ─ 15 65
R&S®GAPM Operation
Measurement Control
The progress of the file currently being replayed is displayed in the "Replay/Measure-
ment" box. The progress is indicated with a percentage of the call records being
replayed, together with the start date and time, and the end date and time (in closed
brackets) of the call records within the recording file.
While the replay is ongoing, the replay time location can be accessed quickly by vary-
ing the progress bar.
Double-click on the progress bar to enable a sliding indicator.
Select the timing location to jump to in terms of percentage (%), with the exact timing
displayed at the top left section of the "Replay/Measurement" box. Click on the "Jump"
button to jump to the selected replay time.
If there is any overlapping of identical call records in the recording files that are linked
to a session, they will be replaced by the newly created records. Some relevant data
like session keys and user comments will, however, be taken over from the duplicate
record. Handling of duplicate records is a regular task when replaying the same record-
ing file into the same session again.
Manual 4072.4037.32 ─ 15 66
R&S®GAPM Operation
Measurement Control
Resuming replay
Click on the "Start Replay" button to resume the replay of the recording files that has
been stopped.
If the progress of the previous replay is less than 100%, the replay will be continued
from where it was previously stopped. However, the system will take into account the
synchronization requirements and call records with ongoing calls. That is the reason
why the actual replay continue time will be earlier than the previous replay stop time.
If the progress of the previous replay is completed at 100%, clicking on the "Start
Replay" button will cause the recording file to be replayed from the beginning. A dialog
box will appear to confirm whether to start the replay from the beginning again.
Figure 5-21: Warning dialog box to restart replay from the beginning
Resetting replay
Resetting replay allows the replay to be forced to start from the beginning of the recor-
ded files irrespective of the progress of the previous replay.
Manual 4072.4037.32 ─ 15 67
R&S®GAPM Operation
Managing Call Record Information
Manual 4072.4037.32 ─ 15 68
R&S®GAPM Operation
Managing Call Record Information
Click the "Next Filter" button to activate the next view filter.
Manual 4072.4037.32 ─ 15 69
R&S®GAPM Operation
Managing Call Record Information
Make the desired changes to the "Filter Properties" settings. Click "Add" to include the
settings to the active filters. Multiple filter properties can be added to an active filter.
Manual 4072.4037.32 ─ 15 70
R&S®GAPM Operation
Managing Call Record Information
Click "Save..." to save the active filter settings with a .fil extension. The active filter set-
tings are saved as a user-defined filter.
Click "OK" to accept and submit the new active filter settings to the server. Click "Can-
cel" to cancel any changes.
Manual 4072.4037.32 ─ 15 71
R&S®GAPM Operation
Managing Call Record Information
The "No Filters (View all records)" default filter allows all call records to be viewed in
the "Call Record Information" view.
The name of the currently active filter that is used is shown in the "Active Filter" list.
If the active filter settings are not saved, and the "OK" button is clicked, the "Filter (Not
in list)" temporary filter is created. This is a temporary file storing the filter setting that is
automatically removed when new active filter settings are edited. Do remember to save
the active filter settings that are needed and commonly used.
Predefined filters are active filters that are provided by the installation package. They
are denoted by a blue file icon.
User-defined filters are active filters that can be individually customized and saved.
They are denoted by a green file icon.
The following sections describe how filter criteria can be added, removed or edited.
Manual 4072.4037.32 ─ 15 72
R&S®GAPM Operation
Managing Call Record Information
Predefined or user-defined active filter settings can be loaded for the filter properties to
be edited.
The location of the predefined filters can be seen and user-defined filters can be set in
"Preferences" on the "Watch Directories" tab.
The path for the predefined filters is set in the same folder as the GAPM_GUI.exe file
upon installation from the .msi installation file. It is not recommended to change the
path locations of the predefined filters.
Manual 4072.4037.32 ─ 15 73
R&S®GAPM Operation
Managing Call Record Information
Manual 4072.4037.32 ─ 15 74
R&S®GAPM Operation
Managing Call Record Information
Changes can be made to any filter properties by selecting the type of the relevant filter.
Click the "Apply" button to include the changed settings to the "Active Filters" settings.
Once the active filter has been submitted to the server, the "Call Record" view or "Tar-
get Record View" starts populating with call record entries that fulfill the filter criteria.
The changes to the filter type are not implemented if the "OK" button is clicked without
clicking the "Apply" button first.
Click the "Remove All" button to remove all the filter types from the "Filter Settings".
Filter types
This section describes the functionality of some of the filters that are used.
Call Duration
The "Call Duration" filter allows the voice calls in the "Call Record Information" view to
be filtered. The function of the "Call Duration" is to display those call records with voice
calls that have a duration exceeding the specified value (in seconds).
Figure 5-30: Excluding voice calls with duration of less than 10 seconds
Time Span
The "Time Span" filter defines a time window in seconds from the current real-time /
replay time until the given time span into the past. The function of the "Time Span" is to
display only call records with "UTC Start Time" within this time window. This reduces
the size of the "Call Record Information" view as older call records are removed.
Manual 4072.4037.32 ─ 15 75
R&S®GAPM Operation
Managing Call Record Information
Figure 5-31: Showing call records for time span of less than 60 seconds only
Time Period
The "Time Period" filter allows the time period of the call records in the "Call Record
Information" view to be filtered. The function of the "Time Period" is to either display
only the call records that fall in between the time period (by setting an "INCL" filter), or
to display only the call records that fall out of the time period (by setting an "EXCL" fil-
ter).
The time period can be configured in the "Filter Settings" dialog box under "Filter Prop-
erties","Filter Type:" "Time Period". Select the start time and the end time of the time
period to be filtered.
Manual 4072.4037.32 ─ 15 76
R&S®GAPM Operation
Managing Call Record Information
Manual 4072.4037.32 ─ 15 77
R&S®GAPM Operation
Managing Call Record Information
5.4.2 Preferences
The "Preferences" dialog box allows to customize the look-and-feel of the R&S GAPM
client software. The settings are automatically saved when the application is closed,
and retrieved when it is relaunched. The factory settings can always be reverted with
the click of button.
In the "Call Record Information" view, there are columns such as the "Call Record
State" showing various states of calls being monitored, as well as other columns show-
ing other states or results. Each state or result can be explicitly represented by colors
to make it easier to distinguish between different states. These colors can be custom-
ized with the "Edit colors" button.
Manual 4072.4037.32 ─ 15 78
R&S®GAPM Operation
Managing Call Record Information
All columns in the "Call Record Information" view can be set to hidden. This provides a
choice to have an overall view (see everything) or a focused view, where unwanted
columns are hidden.
Manual 4072.4037.32 ─ 15 79
R&S®GAPM Operation
Managing Call Record Information
Unselect any column that is not required to be displayed in the "Call Records Informa-
tion" view. Click on the "Select All" button to enable all columns to be visible.
Click on the up or down arrow to move the display order of the columns. This order
appears in the leftmost column in the "Call Record Information" view.
Select "Default Order" to set the display order to factory default settings.
The general settings for date and time standard, call wave preload timings, maximum
call duration histogram, and call wave plot can be configured here.
Manual 4072.4037.32 ─ 15 80
R&S®GAPM Operation
Managing Call Record Information
Date/time standard
In the "Call Record Information" view, the first two columns show the start time and end
time of each call entry. This time can be displayed as UTC time (Universal Time Coor-
dinated) or local time.
The "Date/Time" tab of the "Preferences" dialog sets the preferred time standard to be
used throughout the entire client application.
Date/time settings can also be switched from the context menu.
Manual 4072.4037.32 ─ 15 81
R&S®GAPM Operation
Managing Call Record Information
Manual 4072.4037.32 ─ 15 82
R&S®GAPM Operation
Managing Call Record Information
Window position/state
The window position/state is loaded/saved at startup and exit automatically, it can also
be edited in "Preference" as position/state profile.
To add the current window position/state as a profile click on the name and start edit-
ing. After editing, click on "Add Current Window Position/State" to add the new profile.
To delete a profile right-click on the item in the profile combo box and select "Remove
<profile name>".
A shortcut to select the window position/state profile is also available in the main tool-
bar.
The maximum number of target notification entries to be displayed in the "Target Notifi-
cation" view can be set from 0 to 10000. The default is 500.
The target call records that have been acknowledged can be hidden and not displayed
in the "Target Notification" field by enabling the "Hide acknowledged target notification"
checkbox.
Manual 4072.4037.32 ─ 15 83
R&S®GAPM Operation
Managing Call Record Information
The alert settings for errors, warnings and new debugging information can be config-
ured in the "Alert" field.
There are 5 categories of events that can be selectively enabled:
● Critical Error
● Error
● Warning
● Info
● Debug Info
Select the checkbox to enable the alert.
Configure the alert mode as follows:
● Off
The alert feature is completely disabled.
● Alert Window
The alert feature is enabled with a popup window.
Manual 4072.4037.32 ─ 15 84
R&S®GAPM Operation
Managing Call Record Information
Manual 4072.4037.32 ─ 15 85
R&S®GAPM Operation
Managing Call Record Information
The event alert toolbar will have a spinning display and the alert tone will be stopped
temporarily until the timer for the snooze function is up after which the alert toolbar
blinks once again in red color and the alert tone is activated again. New incoming
event alerts will not cause an alert during the snoozing period.
Click the "Close" button to close the "AlertDialog" box.
The location path for the predefined and user-defined filters can be located in the
"Watch Directories" tab.
The default path locations should not be changed.
Manual 4072.4037.32 ─ 15 86
R&S®GAPM Operation
Managing Call Record Information
Manual 4072.4037.32 ─ 15 87
R&S®GAPM Operation
Managing Call Record Information
When a call record has been successfully decoded by the server, the output is a result
file. If the captured service is a voice call, the resulting output is an audio stream of the
call. If the service is an SMS, the output is the text message.
Not all captured call records produce result files. Only call records with the status
"Decoding Finished" have a corresponding result file created in the server.
All call records will have a valid call record ID. During replay, the system will continue
with increasing call record IDs starting from the last one.
Manual 4072.4037.32 ─ 15 88
R&S®GAPM Operation
Managing Call Record Information
Listening to decoded voice calls is similar to playing an audio file. Voice data can be
played, paused, stopped, and the playing position can be adjusted. There may be a
small delay before playing starts because the client is buffering the streamed data from
the server.
The controls to play, pause and stop playback are found inside the "Call Record State"
field. The slider bars to adjust the playing position and volume levels will appear at the
bottom of the "Call Record Information" view once playing is started.
R&S GAPM is able to perform live streaming of ongoing voice calls.
Manual 4072.4037.32 ─ 15 89
R&S®GAPM Operation
Managing Call Record Information
Click the "Stop" icon inside the "Call Record State" field.
If playback has reached the end of the stream, it will automatically stop. If more data
are expected, it will wait and continue playback once new voice data is received.
Click the "Mute" icon to mute the audio sound. To un-mute click on the same icon.
When muted, the icon changes.
The "Mute" icon will toggle the icon design to indicate if the audio sound is muted or
un-muted.
Manual 4072.4037.32 ─ 15 90
R&S®GAPM Operation
Managing Call Record Information
The wave chart shows whether there is any audible content, and where it is located in
the voice call. The marker (represented by a thick red line) will slide along the wave
chart in correspondence with the voice call being played concurrently.
There are several ways of optimizing the graphical wave display.
To activate a zoom window, right-click to drag a red window over an area within the
"Results" view window in order to select the area of viewing interest.
Left-click in the "Results" view to bring the marker directly to the exact location for the
voice call to be played immediately.
Right-click in the "Results" view to display at the previous zoom level.
Left double-click in the "Results" view to display at the "Full scale" level.
Click "+" to provide a zoom-in factor of 2.
Click "-" to provide a zoom-out factor of 2.
Select the list box to define a zoom scale for "Full scale" and several predefined zoom
scale boundaries. "Variable" is shown when the zoom scale of the graphical wave dis-
play is not within the predefined values.
Manual 4072.4037.32 ─ 15 91
R&S®GAPM Operation
Managing Call Record Information
Enable the "Follow Marker" checkbox in order to allow all the zoom actions to focus on
the marker. The graphical wave display will also follow the marker's sliding movement
when playing a voice call so that the marker will always appear in the "Results" view.
The control panel functions are similar to the controls in the "Call Record Information"
view.
Click on the "Uplink" button to view the graphical wave display for the uplink voice call,
which is displayed in orange color.
Click on the "Downlink" button to view the graphical wave display for the downlink
voice call, which is displayed in blue color.
Click on the "Combined" button to view the graphical wave display for both the uplink
and the downlink voice call, which are superimposed on each other.
Manual 4072.4037.32 ─ 15 92
R&S®GAPM Operation
Managing Call Record Information
Figure 5-52: Combined uplink and downlink voice call wave display
Click on the "Split" button to view the graphical wave display for both the uplink and the
downlink voice call, which are separated into top and bottom display, respectively.
Figure 5-53: Split uplink and downlink voice call wave display
Enable the "Event" checkbox to view the main events layer 3 message occurrences on
the graphical wave display.
The message events will appear as dots, with their exact timing appearance that is
synchronized with the graphical wave display.
Enable the "Level" checkbox to view the uplink and/or downlink voice call power levels.
The reference levels can be compared to the values at the right side of the graphical
wave display.
The uplink voice call power levels are displayed in dark orange color and the downlink
voice call power levels are displayed in dark blue color.
Manual 4072.4037.32 ─ 15 93
R&S®GAPM Operation
Managing Call Record Information
Hovering the mouse pointer over the event dots will show more details of the particular
event, such as the date and time the event occurred at a certain power level, and the
layer 3 message type.
Manual 4072.4037.32 ─ 15 94
R&S®GAPM Operation
Managing Call Record Information
The events such as pressing on the keypads can be observed with the tool tip over a
"DTMF" event to determine the actual key that has been pressed.
The "Results" view can be linked to the call records in the "Call Record Information"
view.
The "Up" button selects the previous call record from the "Call Record Information"
view.
The "Down" button selects the next call record from the "Call Record Information" view.
The "Played Record" button behaves like a bookmark and selects the call record that is
currently playing.
The "MSC Table" button activates the Message Sequence Chart (MSC) table.
The MSC table displays all the layer 2 and layer 3 messages that are recorded in rela-
tion to a voice call. The UTC time stamp, frame number, channel information, message
uplink or downlink direction, message type, and the hexadecimal representation of the
message contents are displayed.
Double-clicking on any message will show the details of the decoded layer 3 message.
Manual 4072.4037.32 ─ 15 95
R&S®GAPM Operation
Managing Call Record Information
The MSC table filters can be selected to display only the layer 2 or layer 3 messages,
and also to display only the uplink or downlink messages.
The MSC table message contents can be saved as a text file with the "Save" pushbut-
ton.
The call duration of the voice call is highlighted inside the "UTC Start Time" column.
The highlighted call duration bar provides an estimation of the time of the ongoing
voice call. This permits the operator to determine at a glance by looking at the duration
of the decoded voice call whether the call provides substantial information.
The call duration settings can be configured from the context menu.
Manual 4072.4037.32 ─ 15 96
R&S®GAPM Operation
Managing Call Record Information
Unselect "Show Call Duration" to change from the "Call Duration" column back to the
"UTC End Time" column.
Figure 5-61: Entering maximum display value for call duration histogram
Manual 4072.4037.32 ─ 15 97
R&S®GAPM Operation
Managing Call Record Information
This allows filtering out call records with substantially useful voice traffic in conjunction
with the call duration information.
A call record with long call duration time and low UL or DL content ratio percentage
means that it does not contain much useful information.
The column "Voice Prints" in the call record information view provides two pieces of
information: The background color of the voice print cell and the displayed arrows. The
colors encode the current calculation state, and the arrows indicate the addressed
voice print’s link directions. After a voice print was calculated and stored in the session
database, its Net Speech Length is displayed to the left of the corresponding arrow.
For details on the SID operating concept refer to Chapter 3.2.5, "Voice Biometrics
Unit", on page 31.
For details on how to configure the SID refer to Chapter 5.7.5, "Voice Biometrics Unit",
on page 206.
Figure 5-63: Voice Prints column, display of voice print calculation state and net speech length of
voice prints
The following list gives an explanation of the combinations of colors and arrows dis-
played in the voice print column:
Gray
No voice print calculation is required because the call record has no speech content
available.
Manual 4072.4037.32 ─ 15 98
R&S®GAPM Operation
Managing Call Record Information
The column "Language Scores" provides several pieces of information both the current
calculation state and the result of a previously run language identification. The calcula-
tion state corresponds to the background color of the "Language Scores" cell. The lan-
guage ID and the achieved score are provided as textual information. The associated
link direction is indicated by up/down arrows. The cell displays the language having the
highest score. All detected languages meeting the configuration parameters are availa-
ble as tooltips. The R&S GAPM supports language identification in SMS records by
default. Language Identification by processing the audio content of call records
requires the optional Voice Biometrics unit described in Chapter 3.2.5, "Voice Biomet-
rics Unit", on page 31.
For details on language identification refer to Chapter 3.2.5, "Voice Biometrics Unit",
on page 31. A description how to configure LID is given in Chapter 5.7.5, "Voice Bio-
metrics Unit", on page 206
Manual 4072.4037.32 ─ 15 99
R&S®GAPM Operation
Managing Call Record Information
Figure 5-64: The Language Score column displays the calculation state, the language name and
score of the best result
The colors and arrows shown in the "Language Scores" column have the same mean-
ing as described in Chapter 5.4.5, "Voice Prints", on page 98 for voice prints.
The decoded SMS messages can be read in the "SMS Content" column located in the
"Call Record Information" view.
The decoded SMS messages can also be read in the "Results" view for more addi-
tional information related to the SMS such as the SMSC information and coding
scheme used.
Figure 5-66: Results view showing SMS text and additional information
There may be missing parts in case some parts are not received by the system.
In the "Results" view, the total number of SMS required for a concatenated SMS can
be identified by looking at the "Number of ConcatSMS", and the "Sequence Number"
for the sequence number of the RPDU packets.
The "Call Record Information" view allows to track call record entries from the same
SIM card, i.e. with the same IMSI. Thus, related call record entries are easily identified
from the view.
When a call record entry is selected, the entire row is highlighted. Other call record
entries from the same SIM card as the selected one will be highlighted as well in light
blue.
The tracking of the call records employs the identity chains method where the TMSI
change is also recorded in order to trace a target more effectively.
For the concept of identity chains, refer to Chapter 3.2.1, "Identity Chains", on page 28.
When a lot of new call record information is received from the server, the view will
scroll down continuously. This feature allows locking the view, and provides easier
viewing and control of the view.
Click the "Anchor Call Record View" button on the toolbar.
To deactivate, simply click on the "Anchor Call Record View" toolbar button again.
When scrolling up and down the "Call Record Information" view to look at call records,
there may be a need to bookmark certain call records that are of particular interest so
that they can be located and viewed in detail later.
Right-click to select "Toggle bookmark on current call record" (or Crtl-F3) on the call
record to set a bookmark, indicated by a red flag on the leftmost column of the call
record. To disable the bookmark, select "Toggle bookmark on current call record" (or
Crtl-F3) again.
Select "Next Bookmark" (or F3) and "Previous Bookmark" (or Alt-F3) to step through all
the call records that are being bookmarked.
Select "Remove all bookmarks" to clear all bookmarks in the "Call Record Information"
view.
This command is used to add comments to call record entries. These comments are
text-based and can be up to 100 characters long including blank spaces.
Comments are displayed in the last column of each call record entry.
The call record ID of the selected entry is shown for user verification.
If there is an existing comment in the call record, it will be shown in the comment edit-
ing area.
Add or edit the comment as required. Copying and pasting into the area is possible.
Click the "OK" button to accept the comment and submit to the server, or "Cancel" to
cancel the task.
The "Clear text" button clears the entire comment editing area.
The server will respond and update the call comment column of the call record entry.
The priority of the single call record entry may be increased to ensure that it gets deco-
ded first. Decreasing the priority means that other entries are decoded earlier.
These settings can only be configured on call records that have not yet been decoded.
Select "Set Call Priority…" to launch the "Call Priority Settings" dialog box.
The priority value ranges from 0 to 100, where 100 is the highest priority value.
Select "Set Highest Priority" to set the selected call records to the highest priority value
of 100.
All resources are channeled to decode this particular call record with the highest prior-
ity.
Set KC...
Allows to set a KC for a call record manually. This requires the call record to be in "KC
not determined" or "KC not determinable" state.
Reset KC Calculation
Resets the KC calculation state to "KC calculation required" for all call records which
are in "KC not determined" or "KC not determinable" state.
Every ciphered call record that needs to be decoded will require an external unit to cal-
culate a KC value, in order to obtain the call metadata such as the voice calls and SMS
messages.
The call record with the highest priority value in the "Call Record Information" view
under "Priority" column will have its call record calculated by the external unit with high
urgency, followed by other call records with lower priority.
When a call record is being calculated by an external unit, the "Call Record State" col-
umn will show that it is in the process of calculating a KC value in the call record with a
"Computing KC .. xx%" state.
Once the calculation has completed, the state will change to "Decoding call". When the
decoding has completed, the state will change to "Decoding finished", and the call met-
adata will be available.
Contents of the "Call Record" table cells can be copied to the computer clipboard.
Call record entries on the server may be deleted. If the call record entry contains a
result file, it is removed from the server as well.
Once the call record is deleted from the server, the corresponding entry on the call
record information table is removed.
Figure 5-82: Selecting to delete call records from call record information window
Click the "Delete Filtered Call Records" button or menu selection list to launch the
"Delete Call Records" dialog box.
Refer to "Saving and loading active filters" on page 72 on how to save or load the
active filter settings.
Refer to "Adding filter properties" on page 73 on how to edit the filter criterion type val-
ues.
The "Keep Target Records" checkbox allows to exclude all target records from being
deleted.
Click the "Delete" button to delete all call records that fulfill the filter criterion values
after setting up the active filter.
Click the "Cancel" button to abort.
Voice and SMS result files can be saved to the client’s local drives. Voice result files
are saved as PCM wave format (WAV), while SMS are saved as text file (TXT). Stan-
dard Windows programs, such as Windows Media Player and Notepad, can be used to
open the exported result files.
As file names are generated automatically, it is only needed to select the target folder.
If a file with a similar file name already exists in the target folder, it will be overwritten.
After a request has been submitted to save a result file, it can be canceled if the down-
load is still in progress.
All or a subset of the call record data and decoding results can be exported to the cli-
ent PC. The main menu item "Exports..." opens the "Export Call Data..." dialog.
Enter or browse the folder to which the exported data shall be saved.
Select one or more export types by ticking the appropriate check boxes.
When "CSV" is enabled, a single ASCII file named calldata.csv containing one line
per exported call record will be saved. The "Columns..." button can then be selected in
order to open the "Select Call Record Columns" dialog box. Check/uncheck the col-
umns within the "Call Record Information" view that will be exported. The sequence in
which the columns are exported can be changed with the up/down arrow buttons.
When "PCK/SMS" is enabled, one compressed output file per exported decoding result
will be saved. Each file name is uniquely related to the call record and is referenced in
the CSV file.
When "WAV/TXT" is enabled, one decoded output file per exported decoding result will
be saved. Each file name is uniquely related to the call record and its name without
extension is referenced in the CSV file.
When "Include Column Header" is ticked, the first line in the CSV file will contain col-
umn header text and the second line will contain the first data record. Otherwise data
records will start with the first line.
When "Delete Call Data From Server After Exported" is ticked, all exported call records
will be deleted permanently from the server. Call records not selected for export will not
be deleted. If measurement and/or decoding is still ongoing, additional call records
and/or decoding results may be created during and after export. In this case only the
call records initially selected for export will be deleted.
Select the set of call records to be exported. "Selected Call Records" will export only
those call records that are selected in the "Call Record Information" View.
"All Call Records" will export all currently available call records of the currently opened
session.
"Call Record Filter" will export only call records that fulfill the values set in the filter cri-
terion types.
Refer to "Saving and loading active filters" on page 72 on how to save or load the
active filter settings.
Refer to "Adding filter properties" on page 73 on how to edit the filter criterion type val-
ues.
Figure 5-89: Selecting to apply call record filter for call data export
The "Target Filter Mode" allows the selection for filter criterion types to be effective for
all call records, target records only, or non-target records only.
Click "Save..." to save the settings in the "Export Call Data" dialog box as a Call Data
Export (*.cde) file.
Click "Load..." to load the settings from a Call Data Export (*.cde) file into the "Export
Call Data" dialog box.
Click "OK" to start exporting the call data file.
Click "Cancel" to abort.
A WAV file contains the audio data of a decoded voice call and can be played with
most standard audio playback tools.
A TXT file contains the textual content of a decoded SMS call. The file may have multi-
byte-coded content if the language setting of the SMS requires. It can be displayed
with most standard text viewers. PCK and SMS files are compressed intermediate for-
mats of WAV and TXT data as they are used internally on the R&S MDU100 server.
Files of these formats are of significantly smaller size than the respective fully decoded
files of WAV and TXT format. PCK and SMS files can be fully decoded to WAV and
TXT files by using the Rohde & Schwarz command line tool pck2wav.exe. This tool
can be found in the installation folder (C:\Program Files\GAPM) of the R&S GAPM cli-
ent installation. pck2wav.exe is a Windows executable and allows batch processing
of multiple input files.
If the client is disconnected from the server, any outstanding downloads will be cancel-
led automatically.
While downloading is in progress, no actions can be performed on any call records.
When all result files have been saved, an information message box will pop up.
The target list contains a list of target names and their attributes. The target list can be
imported from the client PC to the server, or exported from the server to the client PC.
The main menu item "Import Target List..." opens the "Import Target List" dialog.
Enter or browse the folder from which the target list shall be imported.
When "Replace" is enabled, the imported data replace the entire target list in the
server database.
Click "OK" to begin importing the target list.
Or click "Cancel" to abort.
The main menu entry "Export Target List..." opens the "Save Exported Target List
to ..." dialog.
Figure 5-92: Naming and selecting location for the exported target list
Enter or browse the folder to which the exported target list shall be saved.
Click "Save" to begin exporting the target list as a .csv file.
Or click "Cancel" to abort.
If a target list having voice print attributes is exported, the following export files are cre-
ated:
2. One zip file per voice print attribute listed in the target list. The zip files contain the
binary voice print and the original audio sample, in wave or pck format, from which
the voice print is calculated. The related csv file contains a reference to the zip file
for each voice print attribute.
Figure 5-93: Files generated if a target list with two voice print attributes is exported
If a target list is imported with voice prints, the csv file containing the target list must be
in the same directory as the referenced zip files. Alternatively, the target list file and the
referenced zip files containing the voice prints can be compressed to a single zip file. A
description of import/export format for target lists is given in Chapter 7.2, "Target and
Friend Lists - Export/Import Format", on page 237
The friend list contains a list of friend names and their attributes. The friend list can be
imported from the client PC to the server, or exported from the server to the client PC.
The main menu entry "Import Friend List..." opens the "Import Friend List" dialog.
Enter or browse the folder from which the friend list shall be imported.
Figure 5-96: Selecting the name and location to export friend list
Enter or browse the folder to which the exported friend list shall be saved.
Click "Save" to begin exporting the friend list as a .csv file.
Or click "Cancel" to abort.
The TAC list contains a list of mobile phone names and their Type Approval Codes
(TAC) to identify the brand and model of the mobile phones. The TAC list can be
imported from the client PC to the server, or exported from the server to the client PC.
The main menu entry "Import TAC List..." opens the "Import TAC List" dialog.
Enter or browse the folder from which the TAC list shall be imported.
Figure 5-99: Selecting the name and location for exporting TAC list
Enter or browse the folder to which the exported TAC list shall be saved.
Click "Save" to begin exporting the TAC list as a .csv file.
The tree nodes at the first level of the "Session Management" view show the currently
installed disks.
The system disk is essential and thus always installed. It can only be replaced when
the R&S MDU100 is switched off. All other internal and external disks are hot-swappa-
ble and may hence be installed and removed while the system is online.
The system resolves references to a disk first by its unique serial number, then by its
logical name. This is especially important regarding recording files linked to sessions.
As long as a recording file is available at the original disk, or at a copy of the original
disk with the same logical name, it can be resolved in the context of a session with the
original link. If applicable, the system will prompt to update links appropriately.
Nevertheless it should be avoided to assign the same name to different disks, except
when creating a copy of the disk is actually the intention. The possibility to rename an
initialized disk should be used rarely and with caution.
Mounting a disk
A disk is automatically mounted once it is inserted into an internal drive bay or connec-
ted to an USB port of the R&S MDU100 server. The system will display the new disk
some seconds after connecting it. Mounting a disk manually is only required when the
disk had been unmounted and the disk was not removed, but shall become available
for use again.
Unmounting a disk
Unmounting a disk may be rejected by the system when files on the disk are still open.
This is especially the case when a database or a session is still open on that disk, or
when a recording file is being replayed or recorded.
Initializing a disk
A disk must be initialized for being used with the R&S GAPM system. This mainly cre-
ates an R&S GAPM specific directory structure on the disk and assigns a disk name in
the R&S GAPM context. Each new disk must be initialized once before it can be used
with the R&S GAPM system. Once it is initialized it can be removed and inserted again
into any R&S GAPM system and will be recognized as an R&S GAPM disk device.
Note that a disk can be re-initialized by just initiating the procedure again. In this case
all R&S GAPM specific data will be erased, however! This can be used as a quick
erase procedure for all R&S GAPM data.
If a disk contains other data before initializing it for R&S GAPM usage, these data will
usually not be removed. It is assumed, however, that the directory and file structure are
not accidentally overlapping with the structure used by the R&S GAPM system. Hence
the capacity available for R&S GAPM data will be reduced by the amount of the other
data. Manually deleting these data will make the full disk capacity available to the
R&S GAPM system.
Renaming a disk
This allows to change the disk name in the R&S GAPM context which is initially
assigned during disk initialization. Note that after changing the disk name, references
to its object from other disks will only be resolvable by the disk serial number, not by
the name anymore. This limits the possibility to create a one-to-one-copy of this disk
and should hence be done only for a good reason.
Formatting a disk
Formatting a disk will erase all data on the disk. This includes R&S GAPM specific data
as well as any other data.
By initiating a disk format an operating system format will be executed. This is normally
only required when a disk is not yet formatted. Note that only one disk can be format-
ted at a time.
Target/friend lists can be copied from other databases using export and import of a tar-
get/friend list.
The initialization process (refer to Chapter 5.5.1, "Disk Management", on page 128)
creates on the disk a folder called "recording". When the operator records a measure-
ment, the recording file will be physically saved in the "Recording Files" folder on the
selected disk. Each disk inserted in the server has its own "Recording Files" folder.
The disk contains the "Recording Files" folder and one or more databases created by
the operator.
Select a database and open the context menu to display the available options:
The session is a container for call data records successfully decoded and current ses-
sion events. The current session events are GPS information and current antenna
matrix configurations.
Select a session to open before measurements, and close the session if it is no longer
needed after measurements. When opening another session while the current one is
still open, the latter will be automatically closed.
The session can also be deleted or renamed. Please be aware that data will be lost
when a session is deleted (current session events and the call data records that are
successfully decoded).
Select "Start Measurement" or "Start Replay" to automatically open the session. These
functions are accessible in the "Session Management" view.
A recording file can be added to a session by using the "Add To Session …" option.
A window will pop up with all available recording files from that disk. To select more
than one file, press the CTRL key and while doing so select the required files.
This operation will not move the recording files saved in the "Recording Files" folder. A
link will be created in the session to each individual recording file. The link contains the
disk name, disk serial number and the recording file name. When a session is removed
or deleted, only the links to the recording files will be deleted. The recording files will
still be available in the "Recording Files" folder.
To remove a recording file from a session, select the "Remove from Session" context
menu option.
This operation will delete the links to all the recording files assigned to that session.
An archive session behaves similarly to an active session. When opened, the call
records and data content can be processed in the same way. However, an archive
session cannot be used to start a new measurement or replay. Instead its root session
needs to be opened as the active session in order to perform this task.
The progress of the copy operation is displayed in the "Event Log" view on the "Tasks"
tab. The copy operation can be canceled at any time with the "Cancel" button.
An "INFO" popup window will appear after the session is successfully pasted.
The session database and recording files can be imported to and exported out of the
R&S GAPM Test System for backup purposes.
The export of large amounts of session data that requires a long time will be displayed
in the "Event Log" view under the "Tasks" tab. Click on the "Cancel" button in order to
terminate the export immediately.
Select the session data and recording files to be imported and click "OK".
Recording files are generated when a measurement is recorded. The recording files
are saved in the "Recording Files" folder. Each disk (system or data disk) has its own
"Recording Files" folder. Before starting to record the data captured by the MBRs (Multi
Band Receivers) select a disk and give a name to the recording file.
It is possible to replay the files at any time after they have been recorded and saved.
The "Session Management" view shows the timing statistics for the recorded files that
are replayed.
Before a recorded file is replayed, the "Details" column shows the start date and time,
and the end date and time (in brackets) when the recording took place.
During replay the "Details" column shows the percentage of call records that are suc-
cessfully replayed and the current replay call record's date and time, followed by the
start date and time, and the end date and time (in brackets) of the recorded file.
Once the replay for the recorded file is completed, the "Details" column shows that
100% of the call records have been successfully replayed, followed by the start date
and time, and the end date and time (in brackets) of the recorded file.
The data processing configuration enables you to determine how the call records are
processed in terms of primary filter, truncation filter, call records priority settings and
the archiving settings.
Refer to Chapter 3.5, "Data Processing Concepts", on page 40 for an explanation of
the features that these settings control.
In the main menu select "File" > "Session Data Processing Configuration".
Figure 5-122: Launching session data processing configuration from main menu
Figure 5-123: Opening data processing configuration from "Session Management" view
The "Data Processing Configuration" dialog box will be opened as denoted with the
session name on the header of the dialog box. The configurations created here will
only apply to the particular session with the session name denoted.
A newly created session will inherit its data processing configuration from the session
template.
Select "Restore Default" in order to reset all the parameters of the data processing
configuration to the template settings.
The default setting will only apply to the current settings tab.
The"Data Processing Configuration (Template)" dialog box can be opened via the
"Session Template" item of in the main menu.
The "Data Processing Configuration (Template)" dialog box provides a session tem-
plate with all the values used whenever a new session is created.
Select "Restore Default" in order to reset all the parameters in the "Data Processing
Configuration (Template)" dialog box to the factory default settings.
The default setting will only apply to the current settings tab.
For an explanation of the primary filters see Chapter 3.5.1, "Primary Filter",
on page 40.
The following sections show the user interfaces for setting primary filters' criteria.
To add a filter criterion, set the mode of the criterion to "INCL" (Include) or "EXCL"
(Exclude).
Enter the desired criterion values in the "Values" field.
Click the "Apply" button to submit the changes.
The status bar will show a primary filter status icon if the primary filter is activated.
To remove a filter criterion, click the "Remove" button.
Click the "Apply" button to submit the changes.
To disable all filter criteria, click the "Remove All" button, which means that the primary
filter is disabled.
The truncation filter settings define which call records will be kept in the session data-
base after truncation. The call records not matching this filter criterion will be deleted
during the truncation.
For an explanation of truncation see Chapter 3.5.3, "Truncation", on page 42.
Select the filter criterion type for filtering the truncated call records.
Truncated call records that corresponds to the filter values will be stored in the server
database, all other call records will be deleted.
Select "Keep Target Records" to allow all target call records to be stored in the server
database regardless of the filter criterion types that are set.
Remove all active filters and select "Keep Target Records" will allow all the call records
to be deleted by the truncation filter except the target call records.
Figure 5-129: Truncation filter will only keep target call records
Remove all active filters and unselect "Keep Target Records" will allow all the call
records to be stored in the server database, which means that the truncation filter is
disabled.
The priority settings allow to define the priority to be assigned according to the initial
service request type.
For an explanation of priorities see Chapter 3.5.2, "Call Records Prioritization",
on page 41.
Select the "Priority Settings" tab in the "Data Processing Configuration" dialog box.
The initial service request type of the call records are shown with the set priority value.
Change the priority value in the "Priorities" column. Call records with the same initial
service request type is decoded based on their set priority value.
The lowest priority that can be set is 0, which means that the particular initial service
request type of call records is never calculated and decoded at all.
The highest priority that can be set is 100.
The target priority for all the target call records can be set.
The service request type may change as a result of decoding. The priority value, how-
ever, are assigned according to the initial service request type. The target criteria may
also become known only as a result of decoding. As a result in some cases the effec-
tive priority will not be the target priority value. However, following call records that are
identified as belonging to the same identity chain will get target priority.
The archiving settings allow to define the parameters for automatic archiving.
For an explanation of archiving see Chapter 3.5.4, "Archiving", on page 44.
Select the "Archiving Settings" tab in the "Data Processing Configuration" dialog box.
The default values for the "Database load limit" and the "Upper records limit" are used
in order to strike a balance between achieving a session database of a large enough
call records size and optimizing the processing performance of the system.
The "Archive Size" parameters create new archives based on either a size-rule or a
time-rule archiving.
The size-rule archiving creates an archive based on selecting a "Fixed number of
records" in the "Archiving Duration" field, and choosing the exact size of the archive
based on the "Maximum number of records per archive" setting.
The time-rule archiving creates an archive based on the time duration set in the
"Archiving Duration" field, as long as the number of call records in the archive falls
between the "Minimum number of records per archive" and "Maximum number of
records per archive" settings.
The time-rule archiving creates an archive with the time fragmentation based on the
UTC time.
The following are the UTC time stamps which will be used as a trigger to generate new
archives as long as the minimum and maximum call records conditions are met.
● Archiving Duration: One Hour
UTC Time : 00:00, 01:00, 02:00, 03:00, ....... 23:00
● Archiving Duration: Two Hours
UTC Time: 00:00, 02:00, 04:00, 06:00 ....... 22:00
● Archiving Duration: Four Hours
UTC Time: 00:00, 04:00, 08:00, 12:00, ....... 20:00
● Archiving Duration: Six Hours
UTC Time: 00:00, 06:00, 12:00, 18:00
● Archiving Duration: Eight Hours
UTC Time: 00:00, 08:00, 16:00
● Archiving Duration: Twelve Hours
UTC Time: 00:00, 12:00
● Archiving Duration: Daily (based on number of days as well)
UTC Time: 00:00 (based on number of days as well)
Example 1: Measurement is started at 09:45 with an archiving duration of one hour, the
1st archive will be from 09:45 to 10:00, and the 2nd archive will be from 10:00 to 11:00,
and so on.
Example 2: Measurement is started at 09:45 with an archiving duration of four hours,
the 1st archive will be from 09:45 to 12:00, and the 2nd archive will be from 12:00 to
16:00, and so on.
Example 3: Measurement is started at 09:45 with an archiving duration of daily for 1
day, the 1st archive will be from 09:45 to 00:00 for the 1st day, and the 2nd archive will
be from 00:00 to 00:00 for the 2nd day, and so on.
information only. Data processing for target relevant call records is performed with
higher priority than for other call records.
Friend lists serve to protect call information related to relevant identities. A call record
that matches the identity filter definition in the friend list are not visible in the "Call
Record Information" view. The call contents such as audio data and SMS text mes-
sages are not decoded.
For the case of overlapping target and friend filter definitions, the friend filter definitions
take precedence when filtering call records.
To view all call records for the target list and to remove the view of all call records for
the friend list, switch to target list mode. This can be done with the group of buttons at
the top left corner of the call record view.
The target definition line allows you to key in known information about the target.
The target matching identities are created automatically by the system from call
records that fulfill some (or all) of the target definition line parameters and thus cannot
be edited.
If the system has learned more information from newer call records that falls under the
matching identity of a particular target, the Target/Friend list view updates the informa-
tion back to the target definition line.
In some situations, where the system manages to obtain multiple entries for a particu-
lar field, such as the IMSI (where a target is using more than 1 SIM card) and IMEI
(where a target is using more than 1 mobile phone), the Target/Friend list view also
reflects the information as separate field entries within the target definition line.
If the call record that corresponds to the matching identity is deleted, it is also removed
from the target matching identity list.
If the call records are archived, the matching identities that correspond to the call
records are not displayed. The matching identities of the call records only appear if the
archive is viewed or reloaded by replay.
If the call records are truncated with the "Keep target records" checkbox disabled, they
are removed from the target matching identity list. If the call records are truncated with
the "Keep target records" checkbox enabled, the call records are archived and the tar-
get matching identity list only appears if the archive is viewed or reloaded by replay.
A phone number in the target matching identity that ends with ® indicates that it is a
remote target phone number.
A new entry is created in the table with the "Target Name" field enabled for editing.
Enter a suitable name for this target.
The following diagram shows the status flow of the use of the editor when using the
keyboard for navigation.
When using the mouse, a single right-click simulates the ENTER key to progress into
the lower levels of the editor.
Press the "Enter" key to move back to the top level of table selection mode after mak-
ing any modifications. Previous values entered can be saved at this level.
There may be a red row to indicate that there are new values keyed in but they have
not been saved yet.
Figure 5-143: New values entered but not saved in the editor
The dialog box prompting to save changes may appear when moving away from the
current row or if the "ESC" key is pressed from the current row while new values are
entered.
Click "Save" to save the changes made, or click "Discard" to cancel any changes
made.
Figure 5-145: Target names column reflecting the targets listed in the target list
For a call record that belongs to a target from the target list, the name of the target is
listed inside the "Target Names" column.
Multiple target definitions may match the same call record. In this case, multiple target
names are displayed.
The target names also allow to identity chains to be recorded and viewed. This allows
the tracking of the call records for that particular target even if there is a TMSI or IMEI
change.
Figure 5-146: Identity chains for targets when a target call record is selected
When call records are being exported (refer to Chapter 5.4.19, "Exporting Call Data",
on page 119), the target names are exported together. This allows more detailed track-
ing of the target when the target needs to be analyzed on multiple call records.
Figure 5-147: Remote target names column showing TargetC communicating with TargetB
This identifies the call records of the users that communicate directly with the targets
within the target lists in terms of voice calls or SMS.
A new entry is created in the table with the "Friend Name" field enabled for editing.
Enter a suitable name for this friend.
Adding to the target/friend list directly from the call record view
When a target/friend is found by call record matching, its parameters can be extracted
and used to create a target/friend definition. It is then added to the target/friend list.
Adding a target directly from the call record view is equivalent to adding all target
parameters of all call records belonging to this identity chain manually. It works even
when the IMSI of this identity is unknown.
Select the call record entry of the target/friend by clicking it with the mouse or using the
UP and DOWN keys to navigate to the desired row.
To add to the target list, click the "Add to Target List" button on the toolbar, or select it
from the main menu under "File".
A dialog box appears requesting a name for this target.
Enter the desired name and click "OK". A new entry is added to the target list based on
the parameters extracted from the selected call record entry. To abort, click "Cancel".
The selected call record can also be added to an existing target definition. By checking
the "Add to existing definition" box, a list of target definitions are displayed and the
"Target Definition name" input field is disabled. Click on the target definition entry in the
list and click "OK", the call record is added into the existing entry.
For call records that have been processed by SID (Speaker Identification Unit) and
have voice prints in either downlink or uplink, the voice prints (either uplink or downlink)
can be added to the target list.
The "Add to target list" function can also be accessed from the "Call Record Informa-
tion" view’s context menu, or by keyboard shortcut CTRL-T.
To add to the friend list, click the "Add to Friend List" button on the toolbar, or select it
from the main menu under "File".
A dialog box appears requesting a name for this friend.
Enter the desired name and click "OK". A new entry is added to the friend list based on
the parameters extracted from the selected call record entry. To abort, click "Cancel".
Select a name and a new target with the target definition line of the matching identity
fields are created.
Wildcards must be selected carefully, else an exhaustive search causes a huge vol-
ume of target loads and reduce the performance of the system when it is handling the
target/friend list.
The keyword definition matching considers SMS records that have any of the keywords
if more than one keyword is entered in the "Key Word" column.
Figure 5-160: SMS word spotting with any match in multiple keyword
The keyword definition matching considers SMS records that have a wildcard criterion
with a "*" in the middle or end of the keyword.
The keyword definition matching does not consider SMS records that have a wildcard
criterion with a "*" in the front of the keyword.
Click on the target to highlight the target that is selected. The "Ctrl" key can be used to
select multiple targets.
Figure 5-163: Selecting Target01 and Target02 to be displayed in call records information view
The call records of the selected targets are displayed in the "Call Records Information"
view.
A target match row can also be selected to show matched target records in "Call
Records Information" view.
Figure 5-164: Call records of Target01 and Target02 being displayed in call records information view
A target with available phone number in the target list can be pinged to check if it can
be located in the receiving range of the R&S GAPM test system.
The option "Send target ping…" is available only for the definition entry of a target and
not visible for matching lines.
Ensure that the ping device is ready, and the target ping is enabled in "Configuration
Settings".
Right-click on a target in the target list that contains at least one MSISDN, and select
"Send target ping..." to send a silent SMS to the target.
The operator may be away from the system, or busy looking and working with other
views, when a target's call record arrives. Therefore, it is important to provide timely
alerts and notification when a target call record is received by the system. These can
be handled by the "Target Notification" view.
If "Start Target Notification" is selected, an empty and new "Target Notification" view is
opened. All new incoming targets' call records are recorded.
If "Start Target Notification (Send previous)" is selected, all previously detected target
records are immediately sent to the "Target Notification" view. All new incoming tar-
gets' call records are recorded .
Figure 5-167: Selecting to start target notification view from main menu
The "Target Notification" view opens at the bottom within the "Call Record Information"
view.
Take note of the active window that is selected when applying tools such as filtering.
When the "Target Notification" view is selected and is the currently active window,
there is a blue outlined box around it.
When the "Call Record Information" view is selected and is the currently active win-
dow, the blue outlined box is around the "Call Record Information" view.
Once the "Target Notification" view is started, call records that belong to the targets in
the target list is displayed, with the newest incoming call records streaming in from the
top (row number 1).
Figure 5-169: New incoming target call records indicated by red row numbers
The red highlighted row numbers indicate that the incoming target call records have
not been acknowledged.
Select "Acknowledged Target Marker", "Toggle Acknowledged" (or using key F5) to
toggle the target call record from unacknowledged mode to acknowledged mode. The
red highlighted row numbers disappear if the target call records are acknowledged.
Performing the same action toggles the target call record from acknowledged mode
back to unacknowledged mode.
Select "Mark All Acknowledged" (or using key SHIFT-F5) to acknowledge all target call
records in the "Target Notification" view, or "Mark All Un-Acknowledged" to unacknowl-
edge all target call records in the "Target Notification" view.
If the GUI client software is closed, all the acknowledgments made to the target call
records are lost.
Select "Hide Acknowledged Target Notification" to remove all the acknowledged target
call records from the "Target Notification" view.
Figure 5-171: Hiding acknowledged target call records from target notification view
Figure 5-172: Context menu to show that target notification alert is enabled
Click on "Target Alert Enabled" or press SHIFT+F6 to disable target notification alert.
Figure 5-173: Context menu to show that target notification alert is disabled
Click on "Target Alert Disabled" or press SHIFT+F6 to enable target notification alert.
When a new incoming target record is received, the target notification alert toolbar
blinks in red color.
Figure 5-175: Selecting the target notification alert period for snoozing
The target notification alert toolbar will have a spinning display and the alert tone will
be stopped temporarily until the timer for the snooze function is up after which the alert
toolbar blinks once again in red color and the alert tone is activated again. New incom-
ing target call records do not cause an alert during the snoozing period.
Alternatively, from the main menu select "View" > "Stop Target Notification" to close
the "Target Notification" view.
Figure 5-178: Selecting to stop target notification view from main menu
The target notification view can be optimized to show a maximum size of row entries
and to highlight unacknowledged target call records. This can be performed in Chap-
ter 5.4.2.4, "Setting Alerts and Notifications View Attributes", on page 83.
One or more wave files can be uploaded to server as the voice print for a target defini-
tion.
Figure 5-179: Create voice print from wave file context menu
The "Create voice print from wave file" menu item is only enabled where there is an
available SID (Speaker Identification) processing unit. The status can be checked in
"Unit Information" under "SID manager".
If a voice print already existed for the target definition, a warning dialog prompts "A
voice print already exists for this target definition. Do you want to continue and replace
it?"
Select "OK" to replace the voice print. To abort, click "Cancel".
One or more wave files can be selected by clicking the "Browse..." button. The channel
selection applies to all files in the upload.
Figure 5-181: Upload wave file progress indication in task panel of event log
The uploading progress of the wave files can be monitored in the "Event Log" view
under the "Tasks" tab.
Once the import is successfully done, the event log displays a "Succeeded" informa-
tion.
For details of the explanation of voice print column, refer to Chapter 5.6.4, "Defining
Targets with Voice Prints", on page 178.
The "SID Score" and "KWS" slider bars in the "Target List" view are convenient short-
cuts to Chapter 5.7.5, "Voice Biometrics Unit", on page 206. Changing the value cau-
ses VBU to recalculate the matching target records in "Target List".
To use speaker identification, the attribute type "Voice Print" must be set in a target
definition. Voice prints are binary data blocks containing a set of parameters character-
izing a speaker. For details, refer to Chapter 3.2.5, "Voice Biometrics Unit",
on page 31. These attributes can be defined for a target definition by using the follow-
ing sources:
1. Based on a session containing decoded call records with voice prints, a new voice
print target can be created or a call record’s voice print can be added to an existing
target definition. A description of the workflow for creation or modification is provi-
ded in Chapter 5.6, "Target and Friend Lists", on page 154.
2. One or more audio files can be imported into a certain target definition. The sup-
ported format is WAVE, 1 or 2 channels, 16 bits per channel and sample without
compression. If several audio files are selected for import, the GAPM concatenates
all audio files and generates a single voice print before assigning it to the target
definition. For details refer to Chapter 5.6.3, "Creating Voice Print from Wave File",
on page 176.
Target definitions with voice print store the original audio sample which can be
replayed:
● If a voice print attribute was created based on a call record, its corresponding pck
file is stored with the attribute.
● If a voice print attribute was created after importing a wave file, the original audio
sample is stored with the attribute.
Voice print attributes are fully covered by the export/import of target definitions. If target
definitions with voice print attributes are exported, for each voice print attribute a ZIP
file is created in the export directory. The ZIP files contain the binary file representing
the voice print and the audio samples, from which the voice print was created. For
details, refer to Chapter 5.4.20, "Importing or Exporting a Target List", on page 123.
Figure 5-184: Voice Print attribute field with uplink/downlink filter buttons
The voice print field provides uplink/downlink buttons to control whether call records
matching a voice print target in uplink and/or downlink shall be taken into account in
the Target/Friend List view.
Figure 5-188: Blacklist activation state and content displayed in voice print field
Figure 5-190: Net speech length the target voice print is based on
Figure 5-191: Controls for removal of the voice print target or replay of the audio source
1. The uplink audio stream of a call record corresponds to the identity of the caller,
i.e. the IMSI stored with the call record. If the uplink audio stream of a call record is
blacklisted, its IMSI is added to the blacklist. The uplink voice prints of all call
records having this IMSI are not compared to the voice print target definition the
blacklist belongs to. The identity of an uplink audio stream can be added to a target
definition's blacklist by opening the context menu in the target/friend list view for
the corresponding match record. The context menu only shows the item "Add iden-
tity to voice print blacklist" for identity records having a match with the target defini-
tion in uplink direction.
2. The downlink audio stream of a call record has nothing to do with the call record’s
identity but is related to the remote speaker of whom no identity is known. There-
fore, it is not possible to associate the voice print of the downlink audio stream with
an IMSI which could be blacklisted. Instead, the call record itself is added to the
blacklist which prevents its downlink audio stream from being compared to the tar-
get definition the blacklist belongs to. In order to add a call record to a certain tar-
get definition’s blacklist, the filter "Display call records matching selected target def-
inition" must be activated and a target definition must be selected in the "Target/
Friend List" view. In the next step, the context menu must be opened in the "Call
Record Information" view for the call record to be blacklisted and the menu item
"Add call record to voice print blacklist" shall be chosen.
After IMSIs or call records were added to a blacklist, the voice print column in the Tar-
get/Friend List view displays the number of IMSIs/call records in a target definition’s
blacklist separated by “/”:
Figure 5-195: Target definition having one call record in its blacklist
The blacklist can be enabled or disabled temporarily by the check box in the voice print
field. If a blacklist is disabled, blacklisted call records are displayed in the call record
view. Members of a blacklist have a black background color in the record ID column.
Figure 5-196: Blacklisted call records have a record ID column with black background color
An entire blacklist is cleared by opening the context menu for a target definition in the
Target/Friend List view and selecting "Clear voice print blacklist" from the menu.
Call records can be removed selectively from a blacklist by selecting "Remove call
record from voice print blacklist" from the context menu.
Keyword spotting targets are defined in the target list editor by entering the keyword
followed by "@<dictionary name>" in the column "Key Word". When the "@" character
is entered into the "Key Word" the list of available dictionaries is displayed for auto
completion.
If a language is not available because the license has expired or of other reasons, the
dictionary name is displayed in red.
After changing the keywords in a target definition, the confidence values are recalcula-
ted and the match records in the target list view are updated. By adjusting the KWS
slider which controls the confidence threshold, the number of false keyword matches
can be minimized.
By opening the result view for a certain target call record, the matching keywords can
be displayed. The calculated confidence value and exact position in the call is available
via tooltip.
Figure 5-201: Display of keyword matches in call records with confidence value and exact position
For more information on how to define targets, refer to Chapter 5.6, "Target and Friend
Lists", on page 154.
The column "Key Word" in the target/friend list view supports specifying languages as
target attributes by starting editing with "@". The editor opens a completion list of all
supported languages you can pick from.
After finishing the edit process, the configured language attributes are displayed with a
leading "@" in the "Key Word" column, followed by the language name and a unique
language tag.
Target and friend groups have been introduced to provide a new level of hierarchy for
organizing target and friend definitions. Definitions are assigned to exactly one group
or no group, i.e. a definition cannot be a member of more than one group. The "Target
Groups" panel displays the current hierarchy of groups and definitions in a tree and
provides the following functionality via toolbar buttons and context menus:
● Create target/friend groups
● Delete target/friend groups
● Rename target/friend groups
● Create target/friend definitions with a group
● Change the group membership of target/friend definitions
● Activate and deactivate target definitions
● Filter definitions in the target/friend list table by selecting groups and definitions in
the group tree
● Expand the group tree
● Hide and show the target tree
Figure 5-210: Move target definitions to new group via context menu.
After triggering "Move definition to group", a dialog prompts where you can choose the
destination group or no group. Alternatively, a definition can be moved to a new group
via drag and drop.
Figure 5-212: Active and inactive target definitions with corresponding check state. Inactive defini-
tions are displayed in the target/friend list table with grey background.
The activation state of definitions selected in the "Target Groups" panel is toggled by
triggering the context menu item "Toggle activation state of definition(s)"
the table is filtered accordingly. The target definition filter can be combined with call
record filtering by activating the icon . Thus you can filter the target records displayed
in the call record view by a single mouse click on a target group or definition in the
"Target Groups" panel.
Configuration setting is where the R&S GAPM Test System settings can be viewed
and changes can be made.
Select from the main menu "Settings" , "Configuration…" to open the "Configuration
Settings" dialog box. It can also be launched via the toolbar button.
The "Server Configuration" tab shows the current settings of the server. These configu-
rations are reported to the R&S GAPM client whenever it connects to the server or
reloads from the server.
Applying changes
Make all necessary changes to the server.
Click the "Apply" button to submit the changes.
Some settings reduce the server performance due to higher processing demands.
When these settings are chosen, a warning message pops up to remind of the conse-
quences.
The default settings can be restored by clicking the "Default Configuration" button.
Server configuration settings are described in more detail here. The main settings are
Enable Output, External Unit, Antenna Matrix and Calculation Methods.
When "Enable Output" is checked, the server will generate results for voice/SMS calls
that have been successfully decoded and vice versa if it is unchecked.
The External Unit has two settings. The first setting, "Use External Unit", selects
whether to use the external unit to decipher the monitored calls. If "External Unit" is
checked, the host address can also be set. During connection to the server, the exter-
nal unit’s address is automatically set by the server.
If there is more than one external unit connected to the R&S GAPM system, multiple
external units can be used in parallel by setting the external units' IP addresses here.
The IP addresses of the multiple external units can be entered in a single line with a ";"
as a separator, or in multiple lines in the text field.
The antenna matrix allows the use of an antenna distributor to assign each
R&S MBR100 receiver to an optimal receiving antenna. To configure the antenna
matrix, refer to Chapter 5.7.3, "Antenna Matrix", on page 200.
Be careful when setting the slider to the end positions! Choosing the value 0.0 causes
putting maximum effort to the calculation of a single call, while the number of pro-
cessed calls significantly decreases. Choosing the value 10.0 maximizes the number
of processed calls while possibly missing valuable content of calls with a Kc that basi-
cally could have been determined with more calculation effort.
The default value of 5.0 is a good choice for a well-balanced operation.
The calculation heuristics internally uses a statistics window to derive the best calcula-
tion strategy. Changes in the network environment that influence this strategy thus are
taken into account with a corresponding time delay. There is no need for user control
to support this process.
However, in the case that the system is going to work in a different network environ-
ment it may be useful to reset the heuristics entirely or partially. By restarting the statis-
tics with an empty state information the new strategy is applied much faster.
Clicking the button "Heuristics Reset" with an empty "MCC-MNC List" field causes the
entire heuristics to be reset. This may be useful after taking the system to another loca-
tion. Entering one or more MCC-MNCs in the "MCC-MNC List" field allows resetting
the heuristics for specific providers. This may be useful if a network provider made
substantial changes to its network implementation, e.g. by updating the BTS firmware.
The enhanced heuristics calculation mode can be enabled by the selection of the
"Enhanced Calculation" pulldown list. The enhanced heuristics calculations may signifi-
cantly improve calculation success rate, however at the cost of calculation perform-
ance of the entire system. There is a choice of performing enhanced calculations on
the targets only by selecting "Targets Only", or on all call records by selecting "On"
(should be avoided if there are extremely large number of incoming call records).
The remaining settings are related to event logging and reporting on the R&S GAPM
Test System.
For Demod DB and GSM Decoder log level, the settings specify which event should be
logged on the server.
Settings such as "Info", "Debug Info" require more computational resources from the
server. Thus, enabling them generates the following warning message as a reminder.
The "MBR Configurations" tab shows the current settings of all R&S MBR100/
R&S MBR200 units connected to the system. All detected R&S MBR100/R&S MBR200
units are shown in a list.
Each R&S MBR100 can be set to receive from one of the following GSM bands:
GSM 900, GSM 1800, GSM 1900 and GSM 850. In addition, it can be set to receive
either the uplink, or the downlink signals.
When an R&S MBR100 is enabled, it is used by the R&S GAPM system for measure-
ment. For example, if four R&S MBR100 are connected to the R&S GAPM system and
a measurement needs to be performed with GSM 900 band, then only two
R&S MBR100 units need to be enabled with one set to uplink and the other set to
downlink.
If an R&S MBR100 is enabled but is not connected to the R&S GAPM system, then the
hardware status will show "Not Ready".
If four R&S MBR100 units are cabled to each other, all of them must be switched on
and connected to the server, even if only one R&S MBR100 is enabled and used for
measurement.
The settings of the R&S MBR200 units will be the same as those of R&S MBR100
units. Each single R&S MBR200 unit will show up as two entries in the "Configuration
Settings" view, denoted by the same serial number but with a different end number of
'1' or '2', corresponding to the numbering of the respective antenna input connectors, to
represent the two independent band processing channels.
Each R&S MBR200 can be set to receive from up to two of the following GSM bands:
GSM 900, GSM 1800, GSM 1900 and GSM 850. In addition, it can be set to receive
either the uplink, or the downlink signals.
When an R&S MBR200 is enabled, it is used by the R&S GAPM system for measure-
ment. For example, if two R&S MBR200 are connected to the R&S GAPM system and
a measurement is performed with GSM 900 band, then only one R&S MBR200 unit
needs to be enabled with one set to uplink and another set to downlink. If the measure-
ment is performed with only GSM 900/1800 downlink signals, then only one
R&S MBR200 unit needs to be enabled with one entry set to GSM 900 downlink band
and the other entry set to GSM 1800 downlink band.
If two R&S MBR200 units are cabled to each other, all of them must be switched on
and connected to the server, even if only one R&S MBR200 is enabled and used for
measurement.
The "Disconnect" button is used to reset the state of the R&S MBR100/R&S MBR200
by disconnecting it from the R&S GAPM system. Once disconnected, the
R&S MBR100/R&S MBR200 will reconnect with the R&S GAPM again. Upon connec-
tion, all previous error states that might have been stored in the R&S GAPM system for
this particular R&S MBR100/R&S MBR200 are cleared, thus resetting it.
To remove the R&S MBR100/R&S MBR200 from the list, select the MBR and click the
"Delete Selected MBRs" button. Take note that when an R&S MBR100/R&S MBR200
is still connected, it cannot be deleted from the list.
R&S MBR100/R&S MBR200 settings can only be changed while data processing is not
running.
In the "Options" section, the "Use External BPF for Uplink MBRs" checkbox is used
when the R&S MBR100/R&S MBR200 is connected to external bandpass filters such
as the R&S GAF850 or R&S GAF900. The bandpass filter allows the filtering of the
uplink signals, which will ensure better performance of the receivers when capturing
call records from mobile phones.
The antenna matrix performs the functions of an antenna distributor. It allows the
selection for a receiver to be connected to a specific receiving antenna, or for receivers
to be connected simultaneously with other receivers to a well positioned and optimally
designed receiving antenna.
The receivers (R&S MBR100) are connected to the antenna matrix output ports, and
the receiving antennas are connected to the antenna matrix input ports.
An example of the connections can be as follows:
● R&S MBR100 Output Port 1 <-- Antenna Input Port 1
● R&S MBR100 Output Port 2 <-- Antenna Input Port 2
The antenna matrix connections for R&S MBR200 are similar to the connection set-
tings for the R&S MBR100, but with two output ports from the antenna matrix going to
a single R&S MBR200.
The antenna matrix can be enabled in the "Configuration Settings" dialog box on the
"Server Configurations" tab in the "Antenna Matrix" section.
Check under "Use Antenna Matrix" and in the "Host/IP Address" field enter the LAN
address of the antenna matrix.
The antenna matrix can be configured in the "Configuration Settings" dialog box on the
"MBR Configurations" tab in the "Antenna Matrix" section of each R&S MBR receiver.
The R&S MBR receivers are identified by their serial numbers. Ensure that the correct
antenna matrix output port is selected for each receiver according to the physical con-
nections, and choose the required receiving antenna that needs to be routed to the
receiver.
The antenna matrix configurations for the input port in the "MBR Configurations" tab
can be dynamically switched during a measurement in order to select the best-posi-
tioned receiving antenna to be used for measurements.
However, the antenna matrix configurations for the output port and antenna name can-
not be modified during an ongoing measurement. Stop the measurement in order to re-
assign any antenna matrix output port numbers or antenna name.
An antenna matrix input port can get assigned a more descriptive name than "Antenna
1". For example, the name "Directional Antenna" may be used if a directional antenna
is connected to the antenna matrix input port. Select the respective port number from
the antenna matrix input port list, then press the ENTER key to show the "Edit Antenna
Name" dialog box. Key in the name for the receiving antenna that is connected to the
antenna matrix input port.
The "Other Devices Configurations" tab allows the Target Ping device to be set up.
The Target Ping devices can be connected to the R&S GAPM server unit (called
Server Target Ping device) and/or connected to the R&S GAPM client PC (called Local
Server Target Ping device).
When the "Enabled" option for the Target Ping device is checked and its COM port is
selected, the Target Ping feature will be enabled.
The COM port drop-down list displays those COM ports that have been configured for
the Target Ping device. Select the known COM port used for the modem port of the
Target Ping device.
The Target Ping device drivers must first be installed on the client PC in order for the
list box to display the relevant COM ports that can be selected for the Local Target
Ping device. The drivers for the R&S GAPM server unit are always pre-installed.
If the COM port does not represent a Target Ping device modem port, a NOT CON-
NECTED status will be displayed.
If the COM port successfully connects to the Target Ping device modem port, a
READY status will be displayed.
If all the COM ports do not represent a working Target Ping device modem port, an
error popup will appear.
The "Test Ping" button allows a silent test SMS to be sent to an MSISDN that is
entered into the list box.
When both the Server Target Ping device and the Local Target Ping device are activa-
ted, connected, and enabled, the R&S GAPM Test System will select and prioritize the
Local Target Ping device. There will be no need to deactivate or disable the Server
Target Ping device.
Closing the R&S GAPM Client GUI will not deactivate or disable the Server Target
Ping device. The Server Target Ping device will still remain persistent unless it is physi-
cally deactivated or disconnected, or disabled in the "Other Devices Configurations"
settings.
In order to test if the MSISDN of the Target Ping device is correct, place the prefix
#Ps# before the MSISDN in the edit field of the Test Ping (e.g. #Ps#+491774xxxxx).
This will send a normal SMS and in the "Event Log" on the "Unit Information" tab, the
Target Ping device can be checked if it has received the SMS. A message will pop up
to report that this SMS is tampered by the provider, which can be ignored for this
MSISDN check.
The "Unit Information" tab of the Event Log indicates that the Target ping was first sent
out, followed by a status report from the SMSC indicating that the SMS has been deliv-
ered a few seconds later. There is no information on any incoming SMS detected by
the Target Ping device, neither is there any popup message on a tampered SMS,
which signifies that the SMS is indeed a silent SMS.
The provider has tampered with the silent SMS flags, and hence it is not recommended
to use this network provider.
However, the Target Pings sent with this provider may still be silent in some cases.
There are various methods to cause the SMS not to be displayed at the user mobile
device, which are probably not all removed by the SMSC.
The "Voice Biometrics Unit" tab in the R&S GAPM Configuration Dialog provides a
section for setting the following SID specific parameters:
Low Score
Calculated scores lower than "Low Score" are discarded. "Low Score" also defines the
score lower boundary which can be configured by dragging the Score Slider explained
next.
Score
Calculated scores meeting or exceeding this value are considered as a speaker match-
ing a voice print target. The score value can be set to a value between "Low Score"
and 100 by dragging the slider or entering the value into the input field. After the
change of score, the new threshold is applied to all scores previously calculated
among voice prints and voice print targets and the target matches are updated accord-
ingly. No actual recalculation of scores is done because all calculated scores down to
the "Low Score" have been cached by the R&S GAPM.
print" column of the call record view. For the color coding of voice print calculation sta-
tus, refer to Chapter 5.4.5, "Voice Prints", on page 98.
# Licenses
Indicates how many processor cores are supported by the purchased license for SID. If
no SID license is available or a license has expired, the number of licenses is 0.
The "Voice Biometrics Unit" tab in the R&S GAPM Configuration Dialog provides a
section for setting the following KWS specific parameters:
Accept Threshold
During the operation of KWS each decoded call record’s speech content is analyzed
and each potential matching keyword is assigned with a confidence value. By setting
the "Accept Threshold", all matching candidates having a confidence value below this
threshold are discarded.
Available Dictionaries
If KWS is enabled and connected successfully to the VBU, the supported dictionary
names are listed here. A green check mark indicates that a dictionary was allocated
successfully by the R&S GAPM.
# Licenses
Indicates how many processor cores are supported by the purchased license for KWS.
If no KWS license is available or a license has expired, the number of licenses is 0.
The "Voice Biometrics Unit" tab in the R&S GAPM Configuration Dialog provides a
section for setting the following LID specific parameters:
Enable
If checked, the R&S GAPM connects to the host and port specified in the field "Voice
Biometrics Host" to enable and configure the Language Identification unit. The Voice
Biometrics Unit manager in the unit info tab displays the current connection status:
success or error. If LID is enabled but the VBU has no appropriate license, an error
message will be sent to the R&S GAPM and an alarm will be triggered if enabled.
the "Language Score" column of the call record view. For the color coding of language
score calculation status, refer to Chapter 5.4.5, "Voice Prints", on page 98.
Relative Score
LID calculates for each detected languages a score and orders the results by descend-
ing scores. The "Relative Score" ScoreRel% configured by the user is used to calculate.
Discard Threshold
All language score less than the "Discard Threshold" are discarded.
# Licenses
Indicates how many processor cores are supported by the purchased license for LID. If
no LID license is available or a license has expired, the number of licenses is 0.
# Languages
Displays the number of supported languages.
Show Languages
If this button is clicked, the list of supported languages is displayed including a long
name and the corresponding language tag according to BCP 47 and ISO 639.
Figure 5-240: List of supported languages including the unique language tag
The "ICD Configurations" panel allows switching on/off the detection algorithm and
store different configuration sets.
While a measurement is running, the reported detection events are not influenced by
any parameter change.
The configuration parameters are grouped into parameters (Param: ...) and weighting
factors (WF: ...).
The parameters group controls the computational threshold of the detection score
value. When a calculated score is above the given "Param: DetectionScore(%)", the
base station carrier will be reported as "used by an IMSI Catcher".
The weighting factors group is used to control the calculation of the score value itself,
which means that the characteristics and weighting of a base station to be used can be
defined.
Weighting factors can be adjusted from negative to positive values:
● "0": The ICD detection characteristic is switched off.
● Positive value: The ICD detection characteristic is enabled and used to detect a
base station to be used by an IMSI Catcher.
● Negative value : The ICD detection characteristic is enabled and used to detect a
base station not to be used by an IMSI Catcher.
All enabled weighting factors are used to calculate the detection score for a base sta-
tion carrier.
Be careful when changing the parameters: depending on the values, a real base sta-
tion carrier may be reported as "used by an IMSI Catcher" or vice versa.
Click the "Apply" button and the configuration set is saved. Subsequently, select the
set in the drop down combo box.
This tab allows performing server administration tasks remotely via the R&S GAPM cli-
ent. The client opens a secured-shell (SSH) channel with the server in order to send
commands.
Some of the tasks are:
● Displaying the server/decoder unit and SID unit log. Their log files may be down-
loaded to the client as well.
● Monitoring server/decoder service and SID state.
● Starting and stopping server/decoder and SID daemon services.
● Installing programs on the server.
● Uninstalling programs on the server.
Ensure the host name or the host IP address is entered correctly first before starting
any server administration tasks.
Similarly for Retrieving All Log Files, instead of displaying the logs in a view, the logs
are written to files and downloaded to the client. This is useful when encountering
problems and need to send the log files to technical support centers for analysis.
All log file commands require a user password, while services commands require a
root password.
Enter the R&S GAPM root password (default = gapmroot). Enable the checkbox to
remember the password for subsequent commands.
Click the "OK" button to update the services status, or "Cancel" to abort the command.
The "Output" field will also display the SSH output on the server.
Figure 5-250: Server/decoder and SID unit state, and installed software version
Left click on the "Sys. Info." button. Enable the "include all logs" checkbox if all the
complete system information log files are required.
A dialog box requesting the R&S GAPM root password pops up. For system informa-
tion log files extraction, root access is needed.
Enter the R&S GAPM root password (default = gapmroot). Enable the checkbox to
remember the password for subsequent commands.
A dialog box requesting for the location to save the system information result files will
appear.
Choose the location to save the zipped file. The file format will be
"gapm_sys_info_gapm<serial_no>_<date>_<time>.tar.gz".
Right-clicking on the "Sys. Info." button allows a customized script file for extracting
system information files to be executed. The file should always come from a reliable
source.
Enter the R&S GAPM root password (default = gapmroot). Enable the checkbox to
remember the password for subsequent commands.
Click the "OK" button to start or stop the services, or "Cancel" to abort the command.
When stopping services, a dialog box appears to get confirmation before proceeding.
The DEB file is uploaded from client to server via FTP transfer. Once uploaded, it will
be installed. The output field shows the SSH output during installation. It also asks for
the root password before installing.
When uninstalling server software, a dialog box appears to obtain confirmation before
proceeding.
The passwords are automatically remembered by the system if the "Remember pass-
word for this Session" checkbox is enabled when keying in passwords.
To avoid unauthorized access to server administration tasks, the user password and
root password can be cleared at the end of the session via the "Clear User Password"
and "Clear Root Password" buttons.
To enhance the security features to provide access only to approved users, an access
list is created in order to grant clearance to all the users within the access list to use
the software.
During every log on attempt, the GUI Client implicitly sends the Windows SID as cre-
dential to the server to be verified against the access list in the server. The access list
must contain the matching user name and credential pair in order to be granted access
to the server.
Click the "Access List" button to access the list.
If prompted by the system, key in the root password to download the access list from
the server.
Figure 5-259: Displaying the current access list from the server
To add an existing system user, select "Add User…" from the dropdown menu and
select the user name to generate the credentials automatically. This method will only
provide the required credentials if the access list management is done on the same cli-
ent unit from which the access shall take place later.
To manually add a user, select "Manually Add User…" from the dropdown menu to
insert an empty row into the table. Double-click on the empty row to manually enter
user name and the credentials.
Enable the "Enable Logon for all users" checkbox only in order to grant access to the
server for all users.
Enable the "Disable Logon for all users" checkbox only in order to block access to the
server for all users.
Disable both the "Enable Logon for all users" and "Disable Logon for all users" check-
boxes in order to grant access for authorised users to the server that are listed in the
access list only.
To delete an entry in the editor, right-click on the entry to bring up the context menu
and choose "Remove item from list".
Click the "Close" button to upload the list and save the list in the server.
detects/reports those "false" base stations which meet the user definable "false" crite-
ria.
The IMSI catcher detection runs in parallel to all of the other system features, yet it
does not require a KC calculation unit to be connected.
The group of GUI elements: Toolbar ICD display button, view menu ICD item, ICD
record view, channel information IMSI catcher filter button, ICD settings in preference
panel and configuration panel are only available when the optional feature is activated.
IMSI catcher detection records are tabulated data; a table organized by columns with
rows represent IMSI catcher activity events. It is possible to delete events; add com-
ments to events and filter call records by IMSI catcher events.
As with the Call Record view display, the ICD record information display is a dockable
widget with a show/hide button in the toolbar.
Clicking the filter button, the "Channel Information" displays IMSI catcher channels
only.
● "Delete"
Deletes the IMSI catcher event record.
● "Show all records"
Causes an active call record filter to be created and applied with the start time, end
time and channel number of the IMSI catcher event.
Click the "Event Log View" button in the toolbar to view the "Event Log".
The "Unit Information" tab displays the state of each functional unit within the
R&S GAPM Test System. It uses a tree format to categorize units into unit types and
their instances. Each unit instance’s state is shown together with additional event infor-
mation.
The "Unit Usage" tab shows utilization of resources (memory, disk space, etc.) for
each single unit in the system. For instance, a unit’s total disk space is shown together
with how much space has been allocated to various files and folders within it. Bar
charts or other diagrams may be displayed next to the resource information.
The "Log Messages" tab displays any important messages logged by the software dur-
ing runtime. It is only meant for reporting errors back to the developers. This view is
normally not opened and is checked only when there are problems detected.
The disk usage display at the top right corner of the GUI shows information on the hard
disk memory usage. A yellow indication when it is above 50% and a red indication
when it is over 80% provides the warning to perform adequate memory maintenance
before the hard disk space runs out.
The recommended installation procedure is: first remove/uninstall the old server soft-
ware, then update the client and finally update the server.
the tab "Server Administration". In the host field enter the host name or the IP address
of the R&S MDU100 server to be updated.
Before installing a new version, the previous version must be uninstalled. Click the but-
ton "Uninstall". Enter the R&S MDU100 root password when prompted (default is:
gapmroot).
Enable the checkbox "Remember password for this session" to avoid entering the
same password again during the installation.
In the case that a PuTTY Security Alert requests caching the host address, there is a
need to confirm this with "Yes" in order to proceed. Wait until the uninstalling has been
completed. This may take a few seconds.
The connection with the server will be broken. Click "OK" to continue.
Click the button "Install…". A file selection box will request to select an DEB package
file for installation, e.g. gapm-1.17.deb. Wait until the installation has been comple-
ted. This may take a few seconds. Click "Close" to complete installation.
There is no need to connect the client to the R&S MDU100 server by a TCP client con-
nection in order to perform the outlined steps. If a client connection to the same
R&S MDU100 is established, the connection will break while uninstalling the software.
This is a normal consequence of stopping the R&S GAPM services. It is not harmful to
have a TCP connection to another server during the update procedure.
3. No R&S GAPM dongle is attached to the USB port of the VBU host or the dongle
has no VBU option activated:
Use the R&S GAPM Server Administration Panel to connect to the VBU host and
click "Retrieve All Log Files…". In this case the log file of the VBU unit
(GAPM_SIdentifier<XXX>.log) shall contain the following messages:
SW_MODULE_INIT_ERROR | CRITICAL ERROR | GAPM_SIdentifierRTC | main-
loop.cpp | 167 | Cannot open hardlock! Trying again in 30 s
Go to main menu "Help" and select "About GAPM Client…" to launch the correspond-
ing dialog box.
The popup dialog box shows the software version of the R&S GAPM Client Unit.
Go to main menu "Help" and select "Release Notes…" to launch the release notes.
The release notes show the latest updates and bug fixes for the latest software ver-
sion.
Go to main menu "Help" and select "User Manual…" to launch the user manual.
The user manual shows the operating procedures of the R&S GAPM Test System.
7 Annex
The following table summarizes the attributes recognized by the GAPM during import
Index
A F
About GAPM Client ......................................................... 233 Friend list ......................................................................... 125
Adding bookmarks .......................................................... 103
Adding call comments ..................................................... 104 G
Anchoring call record view .............................................. 103
Antenna cabling GPS string format .............................................................. 87
R&S MBR100 ............................................................. 11
R&S MBR200 ............................................................. 15 H
Antenna matrix ................................................................ 200
Archiving ........................................................................... 44 Help menu ....................................................................... 233
Archiving settings ............................................................ 152
I
B Identity Chains ................................................................. 28
Backplane cabling Importing and exporting session data ............................. 138
R&S MBR100 ............................................................. 13 Importing friend list .......................................................... 125
R&S MBR200 ............................................................. 17 Importing TAC list ............................................................ 126
Importing target list .......................................................... 123
C
K
Call comments ................................................................ 104
Call data .......................................................................... 119 KC calculations ............................................................... 111
Call duration ...................................................................... 96
Call priority ...................................................................... 106 L
Call record ....................................................................... 113
LAN cabling ....................................................................... 11
Call record contents ........................................................ 112
Language scores ...............................................................99
Call record state colors ..................................................... 78
Listening to voice calls ...................................................... 88
Call record view ............................................................... 103
Log messages ................................................................. 230
Call records prioritization ................................................... 41
Canceling result file request ............................................ 118 M
Channel information .......................................................... 61
Channel numbers in GSM ............................................... 237 Measurement control ........................................................ 63
Characteristics .................................................................... 7 Monitoring channel information ......................................... 61
Client overview .................................................................. 23 MSISDN number normalization ......................................... 29
Client-to-server connection ............................................... 57
Copying call record contents ........................................... 112 O
Create voice print from wave file ..................................... 176
Other devices configurations ........................................... 203
D
P
Data processing concepts ................................................. 40
Data processing configuration ......................................... 142 Path for predefined and user-defined filters ...................... 86
Database and session management ............................... 131 Preferences ....................................................................... 78
Database management ................................................... 131 Preparation ..........................................................................9
Database migration ........................................................... 39 Primary filter ...................................................................... 40
Date standard .................................................................... 80 Primary filter settings ....................................................... 146
Defining targets with language attributes ........................ 186 Priority settings ................................................................ 150
Deleting call records ........................................................ 113
Disk and session management ......................................... 37 R
Disk management ........................................................... 128
Disk usage ...................................................................... 231 R&S MBR100 configurations .......................................... 197
Displaying SMS results ................................................... 100 R&S MBR200 configurations .......................................... 197
R&S Target Ping device .................................................... 18
E Rack mounting .................................................................. 10
Recording files ................................................................ 141
Event log ......................................................................... 229 Release Notes ................................................................. 234
Exporting call data ........................................................... 119 Result file ........................................................................ 118
Exporting friend list .......................................................... 125 Result files ....................................................................... 118
Exporting TAC list ........................................................... 126
Exporting target list ......................................................... 123 S
Safety .................................................................................. 9
Saving result files to disk ................................................. 118
T
TAC list ............................................................................ 126
Target and Friend Groups ............................................... 186
Target and friend lists ...................................................... 154
Target list ........................................................................ 123
Target notification ............................................................ 170
Target notification view attributes ...................................... 83
Target ping ........................................................................ 30
targets friends export formats ......................................... 237
Time standard ................................................................... 80
Tracking call records ....................................................... 102
Truncation ......................................................................... 42
Truncation filter settings .................................................. 148
U
Unit Information ............................................................... 229
Unit usage ....................................................................... 229
Unpacking and Checking .................................................... 9
Updating the client .......................................................... 231
Updating the server ......................................................... 231
User Manual .................................................................... 235
V
View filter ........................................................................... 68
Voice Biometrics Unit ........................................................ 31
Configuration ............................................................ 206
Troubleshooting ........................................................ 232
Voice calls ......................................................................... 88
W
Watch directories .............................................................. 86