Prepared by: Date: Document:

Ascom Network Testing 8/8/2013 NT13-24169

Ascom (2013). TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.
No part of this document may be reproduced in any form without the written permission of the copyright holder.
The contents of this document are subject to revision without notice due to continued progress in methodology, design and
manufacturing. Ascom shall have no liability for any error or damage of any kind resulting from the use of this document.




TEMS Automatic 9.2 Technical Product
Description






Ascom (2013) Document:
NT13-24169


Contents
1 Introduction ................................................................ 1
1.1 Key Features of TEMS Automatic ............................................1
1.2 Who Is TEMS Automatic Intended For? ..................................2
1.3 Where to Find More Information ..............................................2
2 New Features and Functionality ............................... 3
2.1 Whats New in TEMS Automatic 9.2 ........................................3
2.2 What Was New in TEMS Automatic 9.1 ...................................4
2.3 What Was New in TEMS Automatic 9.0 ...................................4
3 Overview of TEMS Automatic ................................... 5
4 How TEMS Automatic Works .................................... 6
4.1 Testing Capabilities ..................................................................6
4.1.1 Voice Testing ..............................................................................6
4.1.2 Data Service Testing ..................................................................7
4.1.3 Scanning ....................................................................................9
4.2 Operator Console for Remote Probe Administration .............9
4.2.1 Workflows: Test Script Administration .........................................9
4.2.2 Probe Administration ................................................................ 11
4.2.3 System Administration .............................................................. 12
4.3 Measurement Probes: Remote Test Units (RTUs) ................ 12
4.3.1 Deployment: Mobile vs. Fixed Probes ....................................... 12
4.3.2 Radio vs. Ethernet Testing ........................................................ 12
4.3.3 Data Upload .............................................................................. 13
4.3.4 RTU Base Unit Characteristics ................................................. 13
4.4 Real-time Status Indicator (RSI): Local GUI ...................... 14
4.5 Quality Test Nodes ................................................................. 15
4.5.1 CallGenerator ........................................................................... 15
4.5.2 Mobile CallGenerator (MCG) .................................................... 16
4.5.3 PS Data Test Nodes ................................................................. 16
4.6 Post-processing with TEMS Discovery ............................. 17
5 Product Package, System Components ................ 18
5.1 Product Package Overview .................................................... 18
5.2 RTUs ........................................................................................ 18
5.2.1 Device Support ......................................................................... 18
5.2.2 Some Examples of Typical RTU Device Configurations ............ 19
5.2.3 Device Capabilities ................................................................... 19
5.2.4 CS Voice Quality Testing .......................................................... 20





Ascom (2013) Document:
NT13-24169


5.2.5 PS Data Quality Testing ............................................................ 21
5.2.6 Interference Measurements ...................................................... 22
5.2.7 Measurement Control Capabilities ............................................ 23
5.2.8 Measurement Trigger Capabilities ............................................ 24
5.2.9 Data Upload Trigger Capabilities .............................................. 24
5.2.10 Scanning Capabilities of RTU Devices/External Scanners ........ 25
5.2.11 RTU Capabilities ....................................................................... 26
5.2.12 RTU-5 Technical Specifications ................................................ 26
5.2.13 RTU-5 Environmental Specifications ......................................... 27
6 TEMS Automatic System Configuration ................ 28
6.1 Scalability Options ................................................................. 28
6.2 Hardware and Software Requirements ................................. 28
6.3 Intra-system Communication ................................................. 28





Ascom (2013) Document:
NT13-24169 1(28)


1 Introduction
For true end-to-end testing of UMTS wireless networks, Ascom offers the air interface
monitoring tool TEMS Automatic.
TEMS Automatic helps operators to:
Increase revenue: Problems can be located and fixed before they start affecting
customers, improving customer satisfaction and cutting churn. Fewer blocked and
dropped calls means more call time and higher earnings, and a higher quality of
service also helps attract new subscribers.
Boost efficiency: Being autonomous, TEMS Automatic is highly cost- and staff-
efficient, providing a comprehensive and continuously updated overview of network
quality.
Optimize investments: A wireless telecom network represents a huge investment
and needs optimizing to bring the best possible return. TEMS Automatic provides
the means both to collect the relevant data and to conduct analyses on which to
base wise investment decisions. It can also be used to test new features before
rollout to ensure their performance in the live network.
TEMS Automatic provides comprehensive data collection support, including service
testing over packet-switched and circuit-switched radio bearers, The product supports
all major radio technogies, such as UMTS, CDMA and LTE, for the worldwide market.
1.1 Key Features of TEMS Automatic
TEMS Automatic is a multi-purpose solution for data collection and end-to-end testing,
developed for 24/7 monitoring, troubleshooting, and benchmarking. It produces multi-
level output, spanning the whole range from raw route data to KPIs.
TEMS Automatic provides users with:
Insight into the end-users perception of the network, thanks to measurements
taken in the air interface rather than at network nodes (where other monitoring tools
are used). A faithful measure of the end-to-end quality is obtained both for voice
(using PESQ) and for data transfer.
24/7 measurements without the cost of 24/7 staff. Every corner of the network is
probed around the clock by autonomous data collecting units. The state of the
network as perceived by subscribers can be fed back to technicians and modified at
a pace approaching real-time control.
Automated measurements in the truest sense. Not only test calls and
measurements, but also data uploading and system configuration are carried out
automatically. This enables rapid feedback on the state of the network almost in
real-time to the entire organization, all the way from RF engineers in the field to
management.
Benchmarking capabilities in the form of multi-device test units and mechanisms
for careful synchronization of test calls and data sessions.
Remotely configurable data collecting probes. Test units can have their
measurement instructions and their software uploaded from a central administration
console.





Ascom (2013) Document:
NT13-24169 2(28)


1.2 Who Is TEMS Automatic Intended For?
TEMS Automatic is designed to benefit all levels of the operators organization:
RF engineers are notified of all sorts of local malfunctions (weak signal reception,
bad C/I, low data throughput, etc.), prompting them to try out various tweaks to the
network configuration. TEMS Automatic provides KPIs with drill-down functionality
for evaluating network problem areas.
Managers are able to supervise the organizations processes and services. They
can keep track of KPIs (dropped call rate targets, for example) by studying reports
automatically distilled from measurement data at user-specified times. They are
aided in making decisions on investments and organizational improvements. By
getting a tighter grip on the networks end-to-end voice and data quality, the
company is also in a better position to offer customers reliable service level
agreements.
Network planners learn about spots with recurrent problems by requesting
statistics confined to specific areas. This helps them reveal deficiencies in the
network layout or the underlying theoretical models, also providing input for
improvements. As a result they are able to boost network utilization and get
maximum mileage out of the existing network before new investments are made.
Marketing staff can extract statistics on usage patterns, furnishing the basis for
precisely targeted advertising campaigns. Being more intimately familiar with the
networks quality of service, they can also work out more advanced and precise
charges for various services. It is less risky to promise, and charge for, quality that
has been thoroughly assured.
The customer care unit can order coverage information to enlighten customers
who are making complaints or enquiries. Complaints can be cross-checked against
network status reports to help determine whether a problem resides in the network
or in the customers handset.
1.3 Where to Find More Information
Our monthly newsletter TEMS News contains articles on new TEMS product releases
and their features, general information on the TEMS portfolio, and much more. To sign
up for this free service, go to www.ascom.com/nt/en/index-nt/nt-news.htm and click the
TEMS News link. In this section of our website you can also read our press releases
and find out about upcoming events where Ascom Network Testing will participate.
You can also follow Ascom Network Testing on Facebook, LinkedIn and YouTube, as
well as subscribe to our RSS feed. Links are provided in the Follow Us section
at www.ascom.com/networktesting.






Ascom (2013) Document:
NT13-24169 3(28)


2 New Features and Functionality
2.1 Whats New in TEMS Automatic 9.2
The new features in the TEMS Automatic 9.2 release are described in more detail in
the separate document TEMS Automatic 9.2 Whats New.
What follows is a concise summary of the new features in TEMS Automatic 9.2 running
RTU-5 with Windows 7 (not valid for probes running Windows XP).
Windows 7 with support for dynamic TCP/IP, enabling enhanced stress testing (file
upload/download).
HTTP file upload: an add-on to our existing HTTP file download capability.
Streaming testing over TCP/IP, using a public server like YouTube, with MOS
quality scores calculated by the VQmon algorithm.
Iperf 3.0 support, addressing the need for more efficient stress testing.
Email (SMTP, POP3/IMAP) service testing, optionally with attachments.
Multi-RAB mobile-originated call setup enhanced to support voice testing in
combination with testing of any PS service and computation of associated KPIs,
bringing tests closer to real-life end user behavior. Both mobile-to-mobile and
mobile-to-fixed connections can be tested.
Scanning with PCTEL SeeGull MX, a multi-technology scanner. Either one MX or
two EX units can be connected to the RTU-5. The MX requires its own direct power
supply, while the EX can be powered from the RTU-5.
Support for workflows, a TEMS common component for design and verification of
test scripts. For quicker access, the workflow designer is integrated with the
Operator Console.
The RTU-5 supports the new TRP logfile format. Please note that *.trp logfiles
require TEMS Discovery for post-processing.
The RTU-5 can house the following measurement devices:
o PCI-e Ericsson F3607 EU & US UMTS
o PCI-e Sierra Wireless MC7700/MC7710 EU & US UMTS/LTE
The RTU software platform is multi-technology ready, being capable of supporting
other devices as well as other technologies (such as CDMA or TD-LTE) on request.
For TEMS Automatic 9.2 this is offered as a service; please contact an Ascom
sales representative for further details.
The Operator Console is capable of managing a mixed RTU fleet containing both
RTU-5 units running Windows 7 (TEMS Automatic 9.2) and older RTUs configured with
Windows XP (TEMS Automatic 9.0).
For post-processing, TEMS Discovery is required to support logfiles uploaded from
RTU-5 units with Windows 7.





Ascom (2013) Document:
NT13-24169 4(28)



2.2 What Was New in TEMS Automatic 9.1
(TEMS Automatic 9.1 was never released externally. It introduced a subset of the
features listed for TEMS Automatic 9.2 in section 2.1 above.)
2.3 What Was New in TEMS Automatic 9.0
Below is a concise summary of the new features in TEMS Automatic 9.0. These
features are described in more detail in the TEMS Automatic 9.0 Technical Product
Description.
Introduction of RTU-5 hardware platform.
Introduction of LTE support.
New measurement device: Sierra Wireless MC77x0 (UMTS/LTE).
Enhanced voice testing with POLQA support for mobile-to-mobile testing with
support for narrowband (8 kHz) as well as super-wideband (SWB, 48 kHz).
Support for PCTEL SeeGull EX scanner.
A set of new KPIs for DNS lookup and HTTP downlink file transfer.






Ascom (2013) Document:
NT13-24169 5(28)


3 Overview of TEMS Automatic
For data service as well as voice testing, whether for benchmarking or general-purpose
quality monitoring, TEMS Automatic uses RTUs (Remote Test Units). These are
autonomous data-collecting devices installed in vehicles traveling the network area, or
alternatively in fixed locations such as airports and shopping malls.
RTUs interact with quality test nodes for voice telephony and data services. A built-in
GPS unit records driving routes.
System administration is done from the Operator Console, which can be operated
through a Web interface. A key part of this administration is the assignment of work
orders to RTUs, telling them where, when, and how to perform their testing.
RTUs make regular contact with the fixed side of the system in order to upload logfiles
and receive new instructions. The logfiles are subsequently stored in a TEMS
Discovery relational database for post-processing.

TEMS Automatic system overview.
TEMS Automatic deserves its name in a multitude of ways, one basic design principle
being that the system should do a maximum of work while requiring a minimum of user
intervention. Automation therefore pervades all the chief tasks performed: from
registration of new RTUs (done by the unit of its own accord), through measurement
and testing (handled autonomously by the RTU as instructed in work orders), to
delivery of collected data (uploads are initiated by the RTUs themselves according to
whatever schedule has been laid down).
TEMS Automatic is easy to learn and use, employing a familiar operating system and
standardized system components. Administration is straightforward and hassle-free:
from the Operator Console, which can optionally be accessed through a Web interface,
users have a complete overview of test units, work orders, and server applications.
From the Operator Console the performance of each RTU can be monitored in real
time, and the test units can be upgraded remotely with new software and device
firmware.
RTUs (Remote
Test Units)
mounted in
vehicles
Fixed-
mounted
RTU
Fixed part of TEMS
Automatic system
Operator
Console for
administration





Ascom (2013) Document:
NT13-24169 6(28)


4 How TEMS Automatic Works
This chapter goes into more detail regarding the core functionality of TEMS Automatic:
Testing capabilities voice, data, scanning
Administration Operator Console
Measurement probes RTUs
Local GUI RSI
Quality Test Nodes including CallGenerator
The chapter is rounded out with a sketch of the post-processing tool TEMS Discovery.
4.1 Testing Capabilities
4.1.1 Voice Testing
4.1.1.1 Mobile-to-mobile vs. Mobile-to-fixed
Circuit-switched voice can be tested in a variety of configurations: mobile-to-mobile
between RTUs, or between devices in the same RTU; or mobile-to-fixed with RTU
devices engaging a CallGenerator connected to a PSTN network, using analog PSTN
or digital E1 (ISD) voice boards.
Mobile-originated and mobile-terminated calls are distinct categories, and
comprehensive data is logged from both caller and receiver.
Voice calls can be combined with concurrent data sessions in multi -RAB testing. The
main objective here is usually to find out how the data traffic affects the performance of
the CS voice service. Any of the supported data services can be involved in multi-RAB
testing.
4.1.1.2 Quality Measurement
TEMS Automatic has several algorithms for assessing audio quality in general and
speech quality in particular:
POLQA (Perceptual Objective Listening Quality Assessment), standardized as ITU
Recommendation P.863. POLQA is measured in a mobile-to-mobile configuration
RTU to RTU, or RTU to Mobile CallGenerator , and operates in either narrowband
(3003400 Hz) or super-wideband (5014000 Hz) mode.
PESQ (Perceptual Evaluation of Speech Quality), standardized as ITU
Recommendation P.862.1. PESQ is measured in a mobile-to-fixed configuration
(RTU to CallGenerator) as well as in a mobile-to-mobile configuration (RTU to RTU,
or RTU to Mobile CallGenerator
1
).


1
The Mobile CallGenerator is simply a modified RTU-4Gs unit, playing precisely the same role in voice
testing as the stationary CallGenerator. See section 7.1.2.





Ascom (2013) Document:
NT13-24169 7(28)


SQI (Speech Quality Index), which uses radio link parameters to calculate the
perceived speech quality on a radio channel.
Both PESQ and POLQA are designed to mimic human speech perception. Throughout
test calls, a speech sentence is played on the voice channel. The two algorithms
compute a quality estimate by comparing the transmitted sentence with the undistorted
reference, also taking the fixed-side equipment into account.
PESQ and POLQA are both part of a larger package of audio quality measurements
(AQM) that also includes echo delay and attenuation, speech path delay, voice jitter,
volume level, and silent call detection.
By using PESQ/POLQA and SQI together it is possible to detect non-radio problems
that affect speech quality (suggested by a good SQI and a bad PESQ/POLQA value
occurring simultaneously).
POLQA offers differentiated narrowband and super-wideband modes, which make it
possible to compare PSTN and ISDN speech quality to that achieved with all
commonly used speech codecs in mobile networks (for example, AMR-WB).
4.1.2 Data Service Testing
4.1.2.1 General: KPIs and Events
TEMS Automatic measures throughput and decode error/retransmission rates for data
transfer in UMTS (including HSPA/HSPA+). Throughput figures always include the
application-level throughput, that is, that experienced by the user operating the FTP
client, streaming client, or HTTP Web browser.
For packet-switched data transfer, TEMS Automatic offers a set of KPIs for rigorously
describing the performance of PS data services as perceived by the end-user. These
include PS end-to-end access time, mean throughput, and transfer time. Further KPIs
indicate failure rates: PS end-to-end non-accessibility and data transfer cut-off ratio.
A couple of measures at a lower level are KPIs in their own right (PS unavailability,
attach time, attach failure ratio). Other measures of a similar nature, such as PS
service access time, are given as PIs (performance indicators).
Various events report on the status of the data connection, such as PS Attach/Detach,
PDP Context Activation/Deactivation, and Routing Area Update.
4.1.2.2 IP Data Logging
TEMS Automatic has the capability to record application layer signaling for PS services
(IP data logging). This is an important tool for troubleshooting PS services. Within an
RTU work order, the function can be switched on and off for each PS data service
testing action.
The IP packets are recorded in the PCAP format, which is used by several open-
source packet sniffer applications including Wireshark. TEMS Automatic archives the
IP data together with the regular TEMS logfiles holding RF data, and the IP and TEMS
data are time-aligned in the process.





Ascom (2013) Document:
NT13-24169 8(28)


4.1.2.3 Configuration of TCP Settings
One common reason that expected wireless data throughput rates are not achieved is
a non-optimal configuration of the TCP protocol in the client. TCP profiles, defining key
parameters such as send and receive window sizes, can therefore be configured from
the Operator Console and assigned individually to RTU devices. A suite of predefined
TCP profiles for LTE, HSPA, EDGE, and GPRS is delivered with TEMS Automatic.
4.1.2.4 Choice of Data Connection: NDIS vs. RAS
Like TCP settings, the choice of data connection type RAS or NDIS substantially
affects end-user performance, especially for high throughputs. For users desiring to
take full advantage of HSPA throughput capabilities, an NDIS data connection is
preferable to RAS. Test unit devices supporting NDIS can therefore be configured from
the Operator Console to use either NDIS or RAS.
4.1.2.5 Video Streaming
TEMS Automatic can test video streaming over HTTP from video upload sites on the
Web (public servers), using Internet Explorer 9 as Web browser.
The viewer-perceived streaming quality is evaluated using the VQmon algorithm.
Developed by Telchemy, VQmon bases its scoring on a parametric model taking IP
sniffing data (among other things) as input. The algorithm is content-sensitive, which
means that it allows properties of the streamed video to influence the quality scores,
preventing inexpertly shot or edited footage from unduly biasing the scores. For
example, VQmon detects blank or frozen images as well as suspiciously blurry footage
that might result from the camera not being properly controlled.
4.1.2.6 Messaging
TEMS Automatic comes with comprehensive support for testing of SMS, MMS, and
email messaging, where messages are exchanged between RTUs. Crucial
performance metrics calculated include average transfer time and send failure rate.
For receiving of email, IMAP is offered as an option alongside POP3. The IMAP
(Internet Message Access) protocol for email retrieval is a refinement of POP3, which it
is gradually supplanting. Emails may optionally contain attachments.
4.1.2.7 Throughput and Latency Measurements
The throughput limits of the network can be probed using a number of services, notably
FTP or Iperf. The latter service is specifically designed to gauge maximum TCP and
UDP bandwidth performance by interacting with an Iperf server.
Network latency is conveniently measured with Ping.
4.1.2.8 Web Browsing
HTTP sessions can be conducted either with Internet Explorer (version 7 or 9) or with
the RTUs own internal Web browser. For tests aiming to imitate user behavior and
operating conditions as closely as possible, it is advantageous to use a commercial
browser like Internet Explorer. The RTU-internal browser, on the other hand, is more





Ascom (2013) Document:
NT13-24169 9(28)


suitable when the focus is on judging network performance rather than on emulating
the users experience.
4.1.3 Scanning
Scanning of radio frequency carriers is useful, for example, in comparing frequency
plans with the reality of the live network. With TEMS Automatic, this can easily be done
across wide areas of UMTS (GSM as well as WCDMA) and LTE networks.
GSM and WCDMA scanning can be done either with the RTUs internal Ericsson
F3607gw embedded module or with an external PCTEL SeeGull MX/EX/EX mini
scanning receiver.
1

GSM scanning in TEMS Automatic encompasses BSIC decoding, System Information
decoding, and C/I measurement.
In WCDMA it is possible to do Top-N CPICH scanning on up to 12 UARFCNs at a time,
as well as BCH (SIB) decoding.
System Information/SIB data underlies the generation of missing neighbor events.
Basing neighbor analysis on broadcast information is a robust approach in that it does
not rely on cell files, which have to be kept rigorously up-to-date to provide good input
to the analysis.
LTE scanning is performed with an external scanner (PCTEL SeeGull MX/EX LTE).
Some examples of scanning options are:
RSSI scanning
Signal scanning
Spectrum scanning
Enhanced power scanning
Example of configuration options: For Enhanced power scanning, the bandwidth of an
EARFCN to be scanned can be selected from 100 kHz up to 20 MHz, and the
resolution can be adjusted in steps of 2.5 kHz.
4.2 Operator Console for Remote Probe Administration
The Operator Console is a PC-based client application whose principal function is to
control the measurement probes (RTUs). It incorporates a design tool for composing
RTU workflows. Other tasks handled from the Operator Console include monitoring of
server applications as well as various system administration tasks.
4.2.1 Workflows: Test Script Administration
Every operation of a test probe is controlled by a workflow, specifying what
measurements to make, where and when to make them, and for how long. The
structure of the workflow supports sequential as well as parallel testing, the latter
including multi-RAB testing (concurrent voice and data sessions).


1
Scanning with the Ericsson F3607gw module will be reintroduced in TEMS Automatic 9.2.1.





Ascom (2013) Document:
NT13-24169 10(28)


A workflow may consist of a simple task or multiple tasks, whose execution may be
governed by control logic: loops, branching, ifelse conditions, and more.
Also notable in this context is the possibility of running multiple PS data sessions within
the same PDP context, with fixed or random-length pauses between the sessions.
The user can also control whether or not PS Attach and PS Detach will be performed
for every measurement and included in the logfile. If the user enables the work order
option Always PS Attached, several data sessions can be run consecutively, and no
Detach/Attach sequence is performed between measurements (for example: PS Attach
PDP Context Activation Measurement PDP Context Deactivation PDP
Context Activation Measurement ...). This pattern provides a closer mimicking of
end-user behavior: an entire testing sequence can be conducted within the same PDP
context, just as a commercial smartphone would.
In the script designer, a workflow is assembled by picking measurement activities from
the left-hand pane and inserting them by drag and drop at the desired position, as
exemplified in the screenshot that follows.

Workflow scripts are currently compatible with RTU-5 units equipped with TEMS
Automatic 9.2 software. Earlier probes use the older work order structure for testing
instructions.
4.2.1.1 Data Recording
During execution of a work order, radio parameters in combination with IP trace
parameters are recorded; during data service testing, the performance of the data
connection is measured in parallel.





Ascom (2013) Document:
NT13-24169 11(28)


As a stress test, an FTP transfer can be conducted for a fixed length of time (for
example, 30 seconds) using a very large file which will not be exhausted within that
time. The average application throughput is then computed for the session.
Certain functions such as audio quality measurement are optional, and their use is
therefore specified in the work order. Some other aspects of test unit behavior, one
example being speech codec preferences, are also set in each work order.
4.2.1.2 Measurement Triggers
When and where to execute a work order is governed by a set of triggers. Specifically,
the execution may be restricted to particular time intervals or particular areas, or be
conditioned by the values of network parameters. Work orders also have a parameter
governing how frequently the work order should be executed.
4.2.2 Probe Administration
4.2.2.1 Configuration
For each RTU the following information can be inspected in the Operator Console:
RTU parameters constituting the unique identity of the test unit
SIM settings
SIM switch settings: Installed SIM cards and hardware capabilities
APN settings
TCP/IP settings
Workflow assignment, current and previous
When not needed for the testing currently being done, RTU devices can be switched
off remotely from the Operator Console to free up system resources and enhance the
performance of testing with other devices.
4.2.2.2 Monitoring
The system monitors status reports from fielded RTUs and indicates the status of each
unit in the Operator Console.
An error condition reported by a test unit is signaled in the Operator Console interface
by tagging the test unit icon with a red or yellow bell.
A further RTU health check can be done by inspecting the log of events reported by
each test unit.
Finally, the Operator Console also displays RTU usage statistics: up time, measuring
time, GPS coverage, and more.
4.2.2.3 Software Upgrades
The software of RTUs and the firmware of RTU devices can be upgraded remotely
from the Operator Console interface.





Ascom (2013) Document:
NT13-24169 12(28)


All available software and firmware releases are arranged in a tree structure, where
they are sorted by release number, cellular technology, and supporting hardware. A
software upgrade is made by drag-and-drop to the target RTU group. The version
numbers of the software and firmware currently running on an RTU can be inspected in
its properties dialog.
4.2.2.4 Data Upload
RTU data upload behavior, too, is specified by the Operator Console user. A range of
options is provided: the RTU may be set to upload at a fixed time of day, or right after
each test is finished, or when the vehicle ignition is turned off. Regarding the wake-up
upload, see section 4.3.3.
There is also the possibility of uploading selected logfiles manually, from selected
RTUs. This is done with the Manual Upload Tool, launched from the Operator Console.
4.2.3 System Administration
Among system administration functions may be mentioned the ability to control and
differentiate user access to the Operator Console. New users can be assigned to
predefined user groups with set privileges.
4.3 Measurement Probes: Remote Test Units (RTUs)
4.3.1 Deployment: Mobile vs. Fixed Probes
RTUs are primarily intended as unattended mobile probes to be installed in vehicles,
preferably ones that are in intensive circulation and cover a lot of ground, such as taxis,
company cars, or buses used for public transportation. Trains and ferries, too, may be
suitable as RTU carriers.
Traveling outdoors, the RTUs will usually have line-of-sight to GPS satellites, enabling
positioning of measurement data using the RTUs built-in GPS or a connected external
GPS.
While designed mainly for outdoor use, RTUs can also be deployed indoors. They are
then installed in fixed locations with known coordinates: in airports, subway/railway/bus
stations, shopping malls, sport and entertainment venues, or other public places.
4.3.2 Radio vs. Ethernet Testing
The core area of application of TEMS Automatic is testing of mobile networks, and
specifically their radio interfaces in their successive incarnations UMTS, CDMA/
EV-DO, and LTE.
Follwoing the trend of handsets interacting with both fixed and mobile telephony
networks, TEMS Automatic has the ability to do PS data service testing over an
Ethernet connection, using fixed-mounted RTUs.





Ascom (2013) Document:
NT13-24169 13(28)


4.3.3 Data Upload
RTUs automatically upload their data to the fixed side on a regular basis, according to
user-specified rules. Compare section 4.2.2.4. An advanced option of special interest is
the wake-up upload, where the RTU starts up independently of regular operation (for
example, at night) to transfer its data, and then goes back to sleep.
Uploads take place over any device that is currently assigned to this task. The upload
device can be either dedicated, in which case it is not used for measurement, or
shared, which means it is tasked with both upload and measurement (though not
simultaneously).
For stationary RTUs, the Ethernet port can be used for data testing and even for data
upload of log files.
4.3.4 RTU Base Unit Characteristics
The RTU is based on a ruggedized computer platform, accommodating up to four
measurement devices in its four internal PCI-e slots, and further equipped with two
USB ports where external measurement devices can be connected.
Additionally, the RTU is configured with an in-built 8-slot SIM switch, seamlessly
shared across all measurement devices and accessible from the outside, so that SIMs
can be easily changed.
The RTU also includes an internal GPS, essential for mobility. Alternatively, the RTU
can connect to an external GPS, which can of course be one with dead reckoning
facilities.
RTUs can be cascade connected, which is ideal when several RTUs are installed at
the same location: the test units can then share a GPS and be monitored with the
same Remote Status Indicator application.
1

All of the above strengths render the RTU base unit flexible and scalable and hence
fit for a variety of benchmarking and quality monitoring scenarios. Benchmarking
becomes scrupulously fair by employing the same measurement devices for all parties
being compared.
Embedded measurement devices (PCI-e modules) commonly used at present are
Ericsson F3607gw Mobile Broadband Modules and Sierra Wireless MC7700/MC7710
data cards.
External devices supported using the USB ports are PCTEL EX and MX, and
simplifying the installation they can be mounted onto the RTU by means of a special
mounting plate.
The RTU has an external power outlet, through which it can power supply external
devices such as a PCTEL EX scanner. Please note that the PCTEL MX scanner must
have its own direct power supply; it cannot use the RTU external power outlet.
Extrernal accessories like antenna combiners and uninterruptible power supply (UPS)
can be mounted onto the RTU by means of a special mounting plate.


1
This function will be reintroduced in TEMS Automatic 9.2.1.





Ascom (2013) Document:
NT13-24169 14(28)


Protective covers can be fastened onto the front and rear panels of the RTU to protect
cables and cable connectors, making the RTU installation even more reliable and
robust.
The RTU is stackable: Up to four RTU units can be mounted effortlessly on top of
each other by means of a simple stacking kit with spring pins, without any need for
tools. See the image on the right below.
For demanding tasks like stress tests or lab tests, any RTU devices not in use can be
switched off remotely from the Operator Console to free up system resources and
enhance performance.
Please refer to the Product Package Description for further details on configuration
options and performance characteristics.


Top left: Remote Test Unit (RTU-5), front panel. Bottom left: RTU-5, rear panel. Right: Two RTUs
(RTU-4Gs model) stacked using the stacking kit. Note the spring pins, which make for easy
mounting. On the RTU-5, all cables exit through the rear panel, further simplifying the mounting
procedure.
4.4 Real-time Status Indicator (RSI): Local GUI
RTUs operate autonomously without requiring human interaction. Nonetheless, it may
sometimes be desirable to monitor the status of RTUs more closely. For this purpose
TEMS Automatic offers Real-time Status Indicator (RSI) as an option with RTU. This is
an auxiliary application installed on a laptop PC which displays status information on
the RTUs connected to it. Such a setup enables the vehicle driver to effortlessly
supervise all data collecting units.
The RSI application is particularly useful during directed testing, such as benchmarking
sessions where the tester is assigned to perform a predetermined number of calls. It is
then easy to verify that the correct number of calls is in fact made.
RSI monitors RTU measurement activities (CS, PS, scanning), the status of each
internal and external device, data uploads, GPS coverage, DSP status, memory usage,





Ascom (2013) Document:
NT13-24169 15(28)


and software upgrading. A set of line charts show important radio parameters. Finally,
a map view is provided to allow inspection of RTU driving routes.
RSI can be connected to the RTUs either via a router or with a LAN cable using a
daisy-chain configuration. Data can be displayed for up to 18 connected devices.

Screenshot of Real-time Status Indicator (RSI). The symbols along the time axis indicate events
such as voice calls, data service testing, and data uploads.
4.5 Quality Test Nodes
The quality test nodes in the TEMS Automatic system are used for end-to-end testing
of customer-perceived voice and data service quality.
4.5.1 CallGenerator
The CallGenerator is a stationary component based on a commodity server platform. It
has processing power to concurrently calculate test scores for a whole fleet of RTUs
calling in. The test calls, which can be both mobile-originated (MO) and mobile-
terminated (MT), are carried by telephone lines connected to digital or PSTN (analog)
voice boards.
The CallGenerator configuration very thoroughly supports CS voice testing, both
narrowband and wideband, with a rich set of KPIs being computed which are aligned
with ETSI definitions. Among these are MOS scores calculated for PESQ and POLQA..
Additionally, the CallGenerator has the capability to measure things like echo delay and
attenuation, speech path delay, voice jitter, volume level, as well as the TEMS-specific
SQI quality index. It also detects silent calls.





Ascom (2013) Document:
NT13-24169 16(28)


To enable calculation of PESQ/POLQA, authentic speech sentences are played on the
voice channel during test calls. The CallGenerator computes the quality scores for the
uplink, while the RTU handles the downlink calculation.
Recordings scoring sufficiently low on the PESQ or POLQA scale (the user sets the
threshold) are saved to a special directory, where they can be inspected and replayed
using suitable software. The recordings are A-law quantized with 8 bits and have 8 kHz
sampling frequency.
The CallGenerator also has a facility for recognition of tone signals emitted by the
mobile station. Registered tone signals are recorded in the database.
PCI Express or PCI boards are used in the CallGenerator to allow greater flexibility in
selecting PC hardware, either digital E1 (ISDN) boards or PSTN boards.
4.5.2 Mobile CallGenerator (MCG)
The Mobile CallGenerator is a mobile unit (a modified RTU-5) whose function is entirely
analogous to the stationary CallGenerator. That is, test units dial the MCG giving
instructions for the voice test that is to follow, and the MCG responds by calling back. It
needs to be noted that the call handling capacity of the MCG is limited by the number
of devices it has installed.
4.5.3 PS Data Test Nodes
Data test nodes can be located within the operators network or anywhere in the
Internet. They consist of a computer running Microsoft IIS FTP server or Microsoft IIS
Web server. Data test nodes for streaming are named streaming data nodes.
By deploying data test nodes both within their own cellular network and elsewhere in
the Internet, operators can determine whether communication problems reside in their
own infrastructure or have external causes.
Over a packet-switched connection, all supported data services can be tested.
When testing FTP, the data test node will be the RAS/FTP server in the TEMS
Automatic system, or any Microsoft IIS FTP server that allows the test unit to read
and write data.
When testing HTTP download, the data test node can be any Web site.
For HTTP file upload, the destination can be any HTTP server, which however
needs to have a special script installed.
Iperf testing is done against a server running Iperf software.
Streaming using public servers is designed to work with most commonly used
streaming sites.
Email has support for both POP3 and IMAP on the receiving side, while the sender
uses SMTP.
For further details, please refer to the tables in section 5.2.





Ascom (2013) Document:
NT13-24169 17(28)


4.6 Post-processing with TEMS Discovery
TEMS Discovery is Ascoms state-of-the-art post-processing tool for wireless network
data, including data from TEMS Automatic. This product is covered in its own Technical
Product Description, to which we refer; here, we will only state a few highlights of
TEMS Discovery.
Unmatched range of processed data. No competing product can match the
variety of information elements that TEMS Discovery handles, allowing thorough
analysis of the data collected.
Easy and extensive customization capabilities: The various views and data
explorers can be arranged in countless combinations. Data can be presented in
multiple sub-views for easy side-by-side comparison, or in more conventional views
with maps, time series, messages, tables, histograms, and reports the choice is
yours. In addition, TEMS Discovery includes a fully customizable report template
builder, key information settings, analysis sets for specific tasks, and much more.
Low total cost of ownership: The software can be deployed with minimal IT
system requirements and with minimal dependence on third-party software. Large
volumes of data are handled with low memory demand, and the intuitive, easy-to-
learn interface speeds up analysis. There is also integrated online access to free or
low-cost GIS data sources.
Flexible deployment architecture: The network configuration is easy with minimal
platform requirements, allowing engineers to collaborate across functional roles and
locations. The processed data, refined into highly organized information with an
unlimited number of composite data sets, is instantly accessible throughout the
organization.







Ascom (2013) Document:
NT13-24169 18(28)


5 Product Package, System Components
5.1 Product Package Overview
The standard product package consists mainly of the following components:
TEMS Automatic system license (comprising licenses for all TEMS Automatic
components)
User documentation DVDs.
Please note that DVDs with TEMS Automatic software and requisite third-party
applications are not included in the product package, since these applications are
installed on-site for the customer by Ascom Network Testing staff.
Test units are likewise not part of the TEMS Automatic product package but are
ordered separately, along with the accessories required for in-vehicle installation. At
the RTU level, too, a number of features are options which are ordered separately for
each RTU, including the data card and licenses for connecting various external
devices, for mobile-to-mobile voice testing with RTUs, for PESQ/POLQA voice quality
measurement, and for testing various other services.
5.2 RTUs
5.2.1 Device Support
5.2.1.1 RTU-4 (Windows XP) with TEMS Automatic 9.0
RTU-4Gs with Windows XP, with dedicated upload device
o Sierra Wireless MC8700 UMTS/HSPA+
o Sierra Wireless MC8801 UMTS/HSPA+
o Sierra Wireless MC7700 LTE MIMO/UMTS HSPA+
o Sierra Wireless MC7710 LTE MIMO/UMTS HSPA+
o Ericsson F3607 EU/US UMTS HSDPA
o External scanning: PCTEL EX GSM/WCDMA/LTE
o Device scanning: Ericsson F3607 EU/US GSM/WCDMA
5.2.1.2 RTU-5 (Windows XP) with TEMS Automatic 9.0
RTU-5 with Windows XP, with or without dedicated upload device
o Sierra Wireless MC7700 LTE MIMO/UMTS HSPA+(100 Mbit/s)
o Sierra Wireless MC7710 LTE MIMO/UMTS HSPA+(100 Mbit/s)
o Ericsson F3607 EU/US UMTS HSDPA (DL 7.2 Mbit/s)
o External scanning: PCTEL EX GSM/WCDMA/LTE
o Device scanning: Ericsson F3607 EU/US GSM/WCDMA





Ascom (2013) Document:
NT13-24169 19(28)


5.2.1.3 RTU-5 (Windows 7) with TEMS Automatic 9.2
RTU-5 with Windows 7, with or without dedicated upload device
o Sierra Wireless MC7700 LTE MIMO/UMTS HSPA+
o Sierra Wireless MC7710 LTE MIMO/UMTS HSPA+
o Ericsson F3607 EU/US UMTS HSDPA
o External scanning: PCTEL EX GSM/WCDMA/LTE
o External scanning: PCTEL EX Flex GSM/WCDMA/LTE
o External scanning: PCTEL MX GSM/WCDMA/LTE
5.2.2 Some Examples of Typical RTU Device Configurations
The table below gives some examples of device configurations for an RTU-5 running
Windows 7. These configurations are suitable for regular quality and coverage
monitoring as well as for demanding stress testing.
Please note that the overall performance of the RTU is dependent on its device
configuration. For testing at very high throughputs, it is wise to disable any RTU
devices that are not needed for that particular test (see section 4.3.4).
For further details about RTU configuration and dimensioning, refer to Product
Package description.
RTU-5 Device
Configuration
Slot 1 Slot 2 Slot 3 Slot 4
4 F3607 F3607 F3607 F3607 F3607
2 F3607 +2 MC77x0 F3607 F3607 MC77x0 MC77x0
1 F3607 +1 MC77x0 F3607 MC77x0
3 F3607 +1 MC77x0 F3607 F3607 F3607 MC77x0
1 MC77x0 MC77x0
5.2.3 Device Capabilities
The table below lists some important attributes and capabilities of RTU-5 devices.
Device
Capability
Ericsson
F3607gw
Sierra Wireless
MC8801
Sierra Wireless
MC7710
Sierra Wireless
MC7700
WCDMA band 850/1900/2100 or
900/1900/2100
MHz
800/850/900/
1900/2100 MHz
900/2100 MHz 800/850/
1900/2100 MHz





Ascom (2013) Document:
NT13-24169 20(28)


Device
Capability
Ericsson
F3607gw
Sierra Wireless
MC8801
Sierra Wireless
MC7710
Sierra Wireless
MC7700
GSM band 850/900/1800/
1900 MHz
850/900/1800/
1900 MHz
900/1800/1900
MHz
850/900/1800/
1900 MHz
LTE band DD800/1800/
2100/2600 MHz
700/1700/2100
MHz
GSM/WCDMA
voice
AMR-WB, AMR-
FR, AMR-HR,
EFR, FR, HR
N/A N/A N/A
GSM/GPRS/
EDGE
Multislot class 10
(GPRS, EDGE)
Multislot class 12
(GPRS, EDGE)
Multislot class 12
(GPRS, EDGE)
Multislot class 12
(GPRS, EDGE)
WCDMA R99/
HSPA
HSDPA
Categories up to
7.2 Mbit/s
(Category 18)
HSUPA
Categories up to
2.0 Mbit/s
(Categories
1, 3, 5)
HSDPA
Categories up to
21.1 Mbit/s
(Category 14)
(Evolved HSPA),
or up to 42.2
Mbit/s with Dual
Carrier
(Category 24)
HSUPA
Categories up to
5.76 Mbit/s
(Category 6)
HSDPA
Categories up to
21.1 Mbit/s
(Category 14)
(Evolved HSPA),
or up to 42.2
Mbit/s with Dual
Carrier
(Category 24)
HSUPA
Categories up to
5.76 Mbit/s
(Category 6)
HSDPA
Categories up to
21.1 Mbit/s
(Category 14)
(Evolved HSPA),
or up to 42.2
Mbit/s with Dual
Carrier
(Category 24)
HSUPA
Categories up to
5.76 Mbit/s
(Category 6)
LTE LTE Categories
up to 100 Mbit/s
DL and up to 50
Mbit/s UL, with 20
MHz bandwidth
(Category 3,
MIMO)
LTE Categories
up to 100 Mbit/s
DL and up to 50
Mbit/s UL, with 20
MHz bandwidth
(Category 3,
MIMO)
5.2.4 CS Voice Quality Testing
RTU-4Gs with TA 9.0 RTU-5 with TA 9.0 RTU-5 with TA 9.2
Device
Capability
Ericsson
F3607gw
Sierra
Wireless
MC8700/
8801
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Voice SQI

N/A N/A

N/A

N/A
Voice PESQ

N/A N/A

N/A

N/A





Ascom (2013) Document:
NT13-24169 21(28)


RTU-4Gs with TA 9.0 RTU-5 with TA 9.0 RTU-5 with TA 9.2
Device
Capability
Ericsson
F3607gw
Sierra
Wireless
MC8700/
8801
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Voice POLQA
NB/SWB
N/A N/A N/A

N/A
Mobile to fixed

N/A N/A

N/A

N/A
Mobile to mobile N/A N/A N/A

N/A
Echo, mobile to
fixed
(analog) N/A N/A (analog) N/A (analog)

N/A
Volume N/A N/A N/A N/A
Silent sall N/A N/A N/A N/A
Speech path
delays
N/A N/A N/A N/A
5.2.5 PS Data Quality Testing
RTU-4Gs with TA 9.0 RTU-5 with TA 9.0 RTU-5 with TA 9.2
Device
Capability
Ericsson
F3607gw
Sierra
Wireless
MC8700/
8801
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
FTP DL/UL

HTTP
browsing with
TEMS browser
IE7/
TEMS
Browser
IE7/
TEMS
Browser
IE7/
TEMS
Browser
IE7/
TEMS
Browser
IE7/
TEMS
Browser
IE9/
TEMS
Browser
IE9/
TEMS
Browser
HTTP file DL
HTTP file UL

Ping
SMS
(UMTS)

(UMTS)

Planned

Planned
MMS





Ascom (2013) Document:
NT13-24169 22(28)


RTU-4Gs with TA 9.0 RTU-5 with TA 9.0 RTU-5 with TA 9.2
Device
Capability
Ericsson
F3607gw
Sierra
Wireless
MC8700/
8801
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
(UMTS) (UMTS)
Planned Planned
WAP 1/2
(UMTS)

(UMTS)

Video
streaming
(VSQI)

(UMTS)

(UMTS)

Video
streaming over
HTTP with
VQmon

Email: SMTP,
POP3/IMAP

Iperf 3.0
(UDP/TCP)

5.2.6 Interference Measurements
RTU-4Gs with TA 9.0 RTU-5 with TA 9.0 RTU-5 with TA 9.2
Device
Capability
Ericsson
F3607gw
Sierra
Wireless
MC8700/
8801
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
C/I (GSM)

C/A (GSM)

Ec/No
(WCDMA)

SIR (WCDMA)

SIR Target
(WCDMA)

Ascom (2013) Document:
NT13-24169 23(28)


5.2.7 Measurement Control Capabilities
RTU-4Gs with TA 9.0 RTU-5 with TA 9.0 RTU-5 with TA 9.2
Control
Function
Ericsson
F3607gw
Sierra
Wireless
MC8700/
8801
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
RAT lock GSM

RAT lock
WCDMA

RAT lock UMTS
(non LTE)
N/A N/A N/A N/A
Planned
RAT lock LTE N/A N/A N/A N/A
Band lock GSM

Band lock
WCDMA

Band lock LTE N/A N/A N/A N/A
Disable EDGE

Disable HSPA

GSM vocoder
selection

N/A N/A

N/A N/A
WCDMA
vocoder
selection

N/A N/A

N/A N/A
C/I

Always
on

C/A

Scanning

Set HSDPA
category
(WCDMA)
N/A

N/A

N/A

Set HSUPA
category
(WCDMA)
N/A N/A N/A

Set LTE
category
N/A N/A N/A N/A N/A N/A N/A






Ascom (2013) Document:
NT13-24169 24(28)


5.2.8 Measurement Trigger Capabilities
RTU-4Gs with TA 9.0 RTU-5 with TA 9.0 RTU-5 with TA 9.2
Trigger
Capabilities
Ericsson
F3607gw
Sierra
Wireless
MC8700/
8801
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Date/time

Area

CGI (Cell Id)

Rx Level

RSCP

Distance

5.2.9 Data Upload Trigger Capabilities
RTU-4Gs with TA 9.0 RTU-5 with TA 9.0 RTU-5 with TA 9.2
Trigger
Capabilities
Ericsson
F3607gw
Sierra
Wireless
MC8700/
8801
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Ericsson
F3607gw
Sierra
Wireless
MC7700/
7710
Interval

Startup

Shutdown

Fixed time per day

After action

Manual RSI

Manual OC

Ascom (2013) Document:
NT13-24169 25(28)


5.2.10 Scanning Capabilities of RTU Devices/External Scanners
The PCTEL EX column is valid for both EX, EX mini and EX Flex scanners.
Capability/device
Ericsson
F3607gw

PCTEL
SeeGull EX
(including mini
and Flex)
PCTEL
SeeGull MX
GSM scanning capabilities
RSSI scanning static ARFCN set

RSSI scanning BSIC decoding

RSSI scanning C/I measurement



RSSI scanning system Info decoding



Spectrum analysis


WCDMA scanning capabilities
Pilot scanning static SC set

Pilot scanning Top N

Pilot scanning SIB decoding (continuous)

Pilot scanning SIB decoding (snapshot)

Pilot scanning high speed/high dynamic


P-SCH +S-SCH


Max number of UARFCNs 12 12 12
SCH time slot scanning

RSSI scanning

Spectrum analysis

Network analysis

LTE scanning capabilities
RSSI scanning N/A

Signal scanning N/A

Enhanced signal scanning N/A


Spectrum scanning N/A

Enhanced power scanning N/A

Ascom (2013) Document:
NT13-24169 26(28)


5.2.11 RTU Capabilities
RTU Capabilities RTU-4Gs with TA 9.0 RTU-5 with TA 9.0 RTU-5 with TA 9.2
Upload device (SIM) Dedicated
SIM slot

Configurable
(SIM slot 14)

Configurable
(SIM slot 14)

Disable device remotely

Set as fixed test unit

Set low voltage limit

GPS Ethernet synch (set
master/slave remotely)

GPS Ethernet synch-
daisy-chain connected

Planned

GPS Ethernet synch-
router connected

Set power-off delay

Set SBAS support for GPS
5.2.12 RTU-5 Technical Specifications
Property Value/Description
Operating system Windows XP/XP Pro embedded
Windows Embedded Standard 7
Input voltage range 6.0 ... 32.0 V DC Max. 6A
Power consumption RTU with 2 internal measurement devices: 31.1 W
RTU with 3 internal measurement devices: 34.6 W
RTU with 3 internal +2 external devices: Max. 60 W
RTU with 4 internal +1 external device: Max. 60 W
Dimensions (h w d) 50 260 176 mm
Weight 2.6 kg
Operating temperature
30C ... +50C
a

CPU Intel Core i7
Internal memory 2.0 GB


a. Maximum temperature may be affected by technology and measurement device used.





Ascom (2013) Document:
NT13-24169 27(28)


Property Value/Description
Non-volatile memory 8.0 GB
Number of GPS channels 16
Conformity CE, compliant with FCC rules, CFR 47, Part 15,
Subpart C, Intentional radiator, Paragraph 15.209
5.2.13 RTU-5 Environmental Specifications
The RTU-5 is RoHS compliant, i.e., it satisfies the requirements in the Restriction of
Hazardous Substances directive adopted by the EU.






Ascom (2013) Document:
NT13-24169 28(28)


6 TEMS Automatic System Configuration
6.1 Scalability Options
A TEMS Automatic system can be configured in different ways to suit a wide variety of
customer needs. The dimensioning of the back-end part is dependent on many
parameters, most importantly the number of test units and the measurement tasks to
be performed. For small networks, a compact server that supports up to four test units
is available; from this minimum size, the TEMS Automatic system can be expanded to
suit any network. Please contact us for further information on scaling and customization
of TEMS Automatic.
6.2 Hardware and Software Requirements
The TEMS Automatic system components (Operator Console/ Call Generator/ Remote
Status Indicator) run on Windows-based platforms. The requirements for the servers
and PCs to be used to run TEMS Automatic are determined by the TEMS Automatic
configuration selected. Processor speed, RAM, and disk space requirements will
therefore be identified by a customer-specific installation project in each case.
General OS requirements are as follows:
Server OS: Windows Server 2008/2008 R2
Client applications: Windows 7.
6.3 Intra-system Communication
All components of the TEMS Automatic system communicate over standard data
communication networks based on TCP/IP. This enables a wide variety of configuration
solutions.
The communication between the test units and the communication server is based on
the mobile data communication link.