eCall Test Suite - Spirent · PDF file(eCall Test Suite and TTworkbench require a valid...

eCall Test Suite First Steps User’s Guide

spirent.com

General Information This user’s guide helps you to download and install TTworkbench, and leads you through configuring and running test cases of the eCall Test Suite. For a successful proceeding please follow the instructions step by step! If you need any assistance, please contact Spirent’s customer care department: Mr. Dirk Borowski Manager Support Services Phone: +49 30 726 19 19 0 Email: [email protected]

Spirent eCall Test Suite First Steps User’s Guide

spirent.com | i

Table of Content 1. Requirements……………………………………………………………………………. 3

1.1. Test Environment and Test Suites………………………………………………….. 3 1.2. Hardware Requirements………………………………………………………………3

2. Get TTworkbench and eCall Test Suite..........................………………………….....4 3. Installation……………………………………………………………………………….. 4

3.1. TTworkbench………………………………………………………………………….. 4 3.2. eCall Test Suite........................………………………………………………...........5

4. Possible Configurations........…………………………………………………………....6 4.1. Basic…………………...........……………………………………………………….....6 4.2. Advanced................................……………………………………………….............7 4.3. Ultimate……...............………………………………………………………………....7

5. Preperation.............................................……………………………………………….8 5.1 PCLF Selection…….…………………………………………………………………...8 5.2 Parameters......………….……………………………………………………………...8 5.3 Audio Configuration…....……………………………………………………………..10

6. Running Test Cases…………………………………………………………………….11 6.1. Analysis………………………………………………………………………………..12 6.2. Saving Configurations and Test Results………………………………………….. 12

7. Setting Module and Test Adapter Parameters….....………………………………...13 8. Details………............................…………………………………………...…………..14

8.1. Core Language Editor (CL Editor)…………………………………………………. 14 8.2. TTthree (TTCN-3 Compiler)…………………………………………………………15

9. Test Case List with Configuration……………………………………………..………14 10. Upper Tester Commands……………………………………………..…............……16 11. References……..................................………………………………………..………16 12. ULTS Parameters….......................…………………………………………..……… 17 13. Advanced Configuration……..............…………………………...…………..……… 18 14. Appendix.....................................………………………………..…………..……… 21


spirent.com | 3/21

1. Requirements

1.1. Test Environment and Test Suites TTworkbench is the TTCN-3 execution platform needed to run the eCall Test Suite.

System Requirements Operating Systems: Microsoft Windows 7/8/10 Linux (GTK2, x86-32, x86-64) Java 2 Platform: Version 8 JDK or JRE

Download at www.oracle.com/technetwork/java/javase/downloads/index.html. We strongly recommend using the above Java JDK. With the OpenJDK / IcedTea for Linux the TTworkbench license will not work correctly!

Memory: 2 GB (8 GB recommended)

1.2. Hardware Requirements Modem Emulator: Mandatory Network Emulator: Optional GNSS Emulator: Optional

Figure 1: eCall Simulator


spirent.com | 4/21

2. Get TTworkbench and eCall Test Suite Please use Spirent’s Customer Service Center at https://support.spirent.com. Step 1 In case you are not registered yet, go to https://support.spirent.com/CSC/register and fill in the registration form. The support team will check your data and notify you about your approval. Step 2 Login at Spirent’s CSC and click on the download app tab on the left side. Step 3 Select the product line TTworkbench and filter for categories and operating system. Download the purchased TTworkbench version. Step 4 Select the release type Controlled Release. Click on folder TTsuites for TTworkbench and download the eCall Test Suite file.

3. Installation

3.1. TTworkbench Step 1 Windows Platform: Double click on TTworkbench-xxx-installer.exe (to be found on desktop or selected directory). Linux Platform: Use command line java -jar TTworkbench-xxx-installer.jar Step 2 Follow the pop up installation wizard… Browse for the valid license file license.dat already saved in your favored directory. (eCall Test Suite and TTworkbench require a valid license file for execution.)


spirent.com | 5/21

Step 3 Follow the pop up installation wizard and finish the installation. Step 4 Start TTworkbench from created desktop icon or menu entry. Step 5 Start a new workspace by accepting the default workspace location on request or choose an existing one.

3.2. Import eCall Test Suite Step 6 In the TTworkbench menu, click on menu item Help → Install New Software... Step 7 Click Add… Archive. Choose the downloaded installation file TTsuite-eCall-E2E_Conf_xxx_archived-site.zip and click the check box with Test Suites → Next.

Accept the terms of license agreements. Click Finish and confirm to restart TTworkbench. Step 8 Close the TTworkbench welcome tab. In the project view, click on the right mouse button, go to menu File → Import → TTCN-3 → TTCN-3 Test Solution Projects → Next.


spirent.com | 6/21

Step 9 Select the installed test solution projects and click on Finish. Further details about installation you can find in the integrated User’s Guide. Click on Help → Help Contents → Spirent TTworkbench User's Guide.

4. Possible Configurations

4.1. Basic : PLMN / Optionally with GNSS Simulation

Figure 2: Basic Configuration - PLMN

Test only over PLMN (Public Land Mobile Networks)

Supports testing

• Execution over PLMN • Test cases for in-band modem

Not supports testing

• NAD (Network Access Device) o eCall flag o Network registration

• Precise positioning


spirent.com | 7/21

4.2. Advanced: Network Emulator / No GNSS Simulator

Figure 3: Advanced Configuration – GSM

Test with additional Network/GSM emulator

Supports testing

• In-band modem • NAD (Network Access Device)

o eCall flag o Network registration

Not supports testing


4.3. Ultimate: Network Emulator / GNSS Simulator

Figure 4: Ultimate Configuration – Complete


spirent.com | 8/21

Complete configuration supporting the full range of tests

Supports testing

• In-band modem • NAD (Network Access Device)

o eCall flag o Network registration


5. Preparation

5.1 CLF Selection Depending on your hardware configurations as above, you can load the test campaign.

Test Campaign Configuration

AtsECall_IVS_Testcases_PLMN.clf 4.1 Basic: PLMN / Optionally with GNSS Simulation

AtsECall_IVS_Testcases_Emulator.clf 4.2. Advanced: Network Emulator / No GNSS Simulator

AtsECall_EGTS_IVS_Testcases_Emulator.clf ERA/GLONASS test cases Just double click on the clf ( ) file to switch to the execution perspective. For further setting of module parameters and test adapter parameters please refer to Chapter 7: Setting Module Parameters and Test Adapter Parameters.

5.2 Parameters Test system parameters:

Parameter View Value Description

PX_NETWORK_EMULATOR true GSM emulator available

false GSM emulator unavailable, PLMN will be used, no 112 calls

PX_GNSS_EMULATOR true GNSS emulator available

false GNSS emulator unavailable, position data will not be verified


spirent.com | 9/21

MSD parameters, must match the data set in the DUT:


PX_VIN Structured Vehicle VIN number

PX_VEHICLE_PROPULSION_STORAGE_TYPE Structured Vehicle Propulsion Storage Type

PC_MSD_numerOfPassengers Boolean Does MSD contain the number of passengers

PX_NUMBER_OF_PASSENGERS Integer Number of passengers, only checked if

PC_MSD_numerOfPassengers is true

PC_MSD_optionalAdditionalData Boolean Does MSD contain additional data

PX_ADDITIONAL_DATA Structured Expected additional data, only checked

if PC_MSD_optionalAdditionalData is true

PX_VEHICLE_LOCATION Structured Expected position, must match the

position generated by the GNSS simulator

PC_MSD_recentVehicleLocationN1 Boolean Does MSD contain the recentVehicleLocationN1 field

PX_RECENT_VEHICLE_LOCATION_N1 Structured Expected recentVehicleLocationN1 value

PC_MSD_recentVehicleLocationN2 Boolean Does MSD contain the recentVehicleLocationN1 field

PX_RECENT_VEHICLE_LOCATION_N2 Structured Expected recentVehicleLocationN2 value

DUT parameters:


PC_ECALL_ONLY true IVS is eCall only, testcases will not wait for

the IVS to register

false IVS is eCall capable, testcases will wait for IVS to register before continuing

Test system parameters:


PX_PSAP_PHONE_NUMBER String PSAP phone number used for test calls

PX_IVS_PHONE_NUMBER String IVS phone number

PX_SMS_FALLBACK_NUMBER String (ERA/GLONASS only) Number used to send the SMS messages to


spirent.com | 10/21

5.3. Audio Configuration Requirements for audio connection to the DUT:

• USB headset • SIP client (e.g.: Jitsi)

Configuration of SIP client:

1) Open jitsi, go to Tools → Options, select the audio tab 2) Set the USB headset for audio in and audio out.

3) Configure the SIP account

a. Open Tools → Options, select the Accounts tab. b. Click Add. c. Select SIP in the network drop down. d. Enter the following data

i. Sip id: [email protected] ii. Password: 1234


spirent.com | 11/21

Configuration of the Test Suite:

1) Open the “Test Adapter Parameters View” 2) Set “eCall Simulator Interface Codec” from

default → MODEM_INSTANCE_CONFIG → [0] → internalSubscriber to a. 101 → audio connection will be set up with the operator b. inactive → audio connection will not be set up with the operator

6. Running Test Cases

Step 1 Open the TTsuite-eCall folder in the Package Explorer (TTCN-3 Development Perspective). Step 2 Open the folder ttcn3 and double click on the test campaign loader file AtsECall_IVS_Testcases_Emulator.clf (with the icon ).

Make sure you have finished the preparation Chapter 5.2 Modem Configuration. The perspective will automatically switch into the TTCN-3 Execution Management. Step 3 Insert the valid USIM card for the public network into your device under test. Step 4 Execution: Select one test case CTP_1_1_14_1 by single click and press the Execute Tests button.

Step 5 Follow the operator commands displayed. First reset the device (e.g. by power cycling it). Then trigger a test eCall. Further details can be found under Help → Help Contents → Using TTsuite-eCall.


spirent.com | 12/21

6.1. Analysis

• Click on the TTCN-3 Graphical Logging tab. It shows the results of the execution as a graphical output.

• A single click on a “send” message arrow provides further details of the TTCN-3 template representation in the Test Data View. Double click on “send” and “receive” arrows for a coding in the Dump View.

• A single click on a “match” or “mismatch” box shows you the received message compared to the expected TTCN-3 template. Mismatched values are marked red.

6.2. Saving Configurations and Test Results The current executed run of test cases can be saved in a *.tlz file by pressing the export button and selecting Export Log in the Management View. The generated *.tlz file (with the icon ) contains the current configuration (CLF) and the executed log traces.

For reviewing, this file can be imported by pressing the import button and selecting Import Log.

Result Analyser

Graphical Online

Logging

Management View

Test Parameteri-

zation


spirent.com | 13/21

In order to generate a test report, use this button. Further details about execution and savings you can find in the integrated Users Guide, Chapter “Using TTworkbench TTman”. Click on Help → Help Contents → Spirent TTworkbench User's Guide.

7. Setting Module Parameters and Test Adapter Parameters Please configure your TTsuite according to the protocol and your local settings. You can use our MBS (Message Building System) to ease it up. In the Parameter View of the Execution Management you find different parameters to change the settings for your individual test configuration. Please click on the right mouse button over the parameter view to open Message Building System. You can access the single parameter and the attributes of single fields.

After finishing, just click on OK to save the change. The changed parameters are called by the test system during runtime. You can run your test campaign with the new configuration at once without recompilation of your test cases. 8. Details (for Development)

8.1. Core Language Editor (CL Editor) Each TTCN-3 file is view- and editable by double clicking in the CL Editor. As shown in Step 1 of “4. Running My First Test Case” you find the TTCN-3 source code (*.ttcn3) in folder ttcn3. After opening the files, the source code will be syntactically checked and highlighted. In addition, an outline will be generated automatically and the go-to-declaration feature will be enabled.


spirent.com | 14/21

8.2. TTthree (TTCN-3 Compiler) For recompiling all TTCN-3 files, please open the main module (with the icon ) in the CL Editor by double click. Press the Rebuild button .

Please note! Compilation is only necessary if some test cases are changed or some new one is created. Otherwise, the generated *.jar files from TTCN-3 source are already available for execution.

9. Test Case List with Configuration

Test spec. Configuration Accelerated Procedure All types 1.1.0.1 unavailable 1.1.0.2 Network (Advanced & Ultimate) 1.1.0.3 Basic (in-band modem) 1.1.2.2 Basic (in-band modem) 1.1.2.3 Basic (in-band modem) 1.1.2.4 Basic (in-band modem) 1.1.2.5 Basic (in-band modem) 1.1.3.2 Basic (in-band modem)

TTCN-3 Compiler/ Validate Buttons

Project View TTCN-3 Core Language Editor

Outline


spirent.com | 15/21

1.1.5.2 Basic (in-band modem) 1.1.5.3 Basic (in-band modem) 1.1.5.4 Basic (in-band modem) 1.1.5.5 Basic (in-band modem) 1.1.5.6 Basic (in-band modem) 1.1.5.7 Basic (in-band modem) 1.1.6.1 Basic (in-band modem) 1.1.7.1 Network (Advanced & Ultimate) 1.1.8.1 Network (Advanced & Ultimate) 1.1.9.1 Basic (in-band modem) 1.1.10.1 Network (Advanced & Ultimate) 1.1.10.2 Basic (in-band modem) 1.1.10.3 Basic (in-band modem) 1.1.11.1 Network (Advanced & Ultimate) 1.1.12.1 Network (Advanced & Ultimate) 1.1.13.1 Basic (in-band modem) 1.1.14.1 Basic (in-band modem) 1.1.15.1 Basic (in-band modem) 1.1.15.2 Basic (in-band modem) 1.1.15.3 Basic (in-band modem) 1.1.15.4 Basic (in-band modem) 1.1.15.5 Basic (in-band modem) 1.1.16.1 Basic (in-band modem) 1.1.16.2 Basic (in-band modem) 1.1.16.3 Basic (in-band modem) 1.1.17.2 Basic (in-band modem) 1.1.17.3 Basic (in-band modem) 1.1.17.4 Basic (in-band modem) eCall Only 1.1.1.2 Network (Advanced & Ultimate) 1.1.10.4 Network (Advanced & Ultimate) 1.1.17.5 Network (Advanced & Ultimate) Optional All types 1.1.1.1 unavailable

1.1.2.1 unavailable


spirent.com | 16/21

1.1.3.1 unavailable 1.1.4.1 unavailable 1.1.5.1 Network (Advanced & Ultimate) 1.1.14.2 Basic (in-band modem) 1.1.17.1 Basic (in-band modem) eCall Only 1.1.1.3 unavailable

10. Upper Tester Commands Purpose of an Upper Tester

• Change ignition state (on/off) • Trigger eCall

o Test call or emergency call o Automatic call or manual call

• Trigger non eCall communication • Reset device • Generate invalid trigger • Attempt to disconnect eCall using vehicle HMI

NOTE: For this release, the Upper Tester (UT) commands are provided as plain text instructions in message boxes to the operator, however in future releases an API will be provided.

11. References

• CEN TS 16454: Intelligent transport systems - eSafety - eCall end to end conformance testing (2013) • CEN EN 15722: Intelligent Transport Systems - eSafety - eCall minimum set of data (MSD) • CEN EN 16062: eCall High Level Application Requirements (HLAP) • CEN EN 16072: PanEuropean eCall-operating requirements • EN/ISO 24978: ITS Safety & emergency messages using any available wireless media - Data

registry procedures • ETSI TS 103 321: Mobile Standards Group (MSG); eCall HLAP Conformance Testing Abstract

Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT) ECall HLAP Conformance Testing

• ETSI TS 122 101: Universal Mobile Telecommunications System (UMTS); Service aspects and Service Principles

• ETSI TS 124 008: Digital cellular telecommunications system (Phase 2+); UMTS; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3

• ETSI TS 126 267: eCall data transfer; Inband modem solution; General description • ETSI TS 126 268: eCall data transfer; Inband modem solution; ANSI-C reference code • ETSI TR 126 969: 3rd Generation Partnership Project; Technical Specification Group Services

and System Aspects; eCall Data Transfer; Inband modem solution; Characterisation Report


spirent.com | 17/21

12. ULTS Parameters

Please add the parameters from “OMA SUPL v2.0 TTCN-3 Test Pack User Manual.pdf” chapter 4.3.

IMS_Enable Enable forwarding of voice channel from the emulator. IMS_ prefixed parameters will only be used if IMS_Enable is set to true.

IMS_AudioType Audio codec, one of: GSM_FR, GSM_EFR, AMR

IMS_SipPeerProtFamily Protocol family of the SIP Peer

IMS_SipPeerIpAddr SIP Peer IP address

IMS_SipPeerPort SIP Peer port

IMS_SipLocalProtFamily Address family for the computer running AAHS

IMS_SipLocalIpAddr IP address for the computer running AAHS

IMS_SipLocalPort SIP port for the computer running AAHS

IMS_UserAgentNamePresent Flag for use of custom user agent (set by IMS_UserAgent)

IMS_UserAgent User agent to use

IMS_PeerServer Peer SIP address

IMS_RtpParaPresent Flag for custom RTP parameters

IMS_RtpPeerProtFamily Address family for the RTP peer

IMS_RtpPeerIpAddr RTP peer IP address

IMS_RtpPeerPort RTP peer port

IMS_RtpLocalProtFamily Address family for the computer running AAHS

IMS_RtpLocalIpAddr IP address for the computer running AAHS

IMS_RtpLocalPort RTP port for the computer running AAHS

SecondaryMCC MCC for the second simulated cell

SecondaryMNC MNC for the second simulated cell

LimitedMCC MCC used to simulate limited connectivity

LimitedMNC MNC used to simulate limited connectivity


spirent.com | 18/21

13. Advanced Configuration

13.1. Modem Configuration The in-band modem simulator can be configured by opening http://<IP-address-of-server>:8080/simulator/login/index User name: admin Default password: 1234 <IP-address-of-server> should be your server IP address or host name. Open the configuration tab and change the AMQP Broker settings, then press Save. Change the test adapter parameters in your TTworkbench execution perspective to match the AMQP Broker settings.

Setting in AMQP Broker Test Adapter Parameter Description

Host BROKER_HOST IP address of the In-band modem simulator

Port BROKER_PORT The port used for communication between in-band modem and TTworkbench

Username USERNAME Used for registration

Password PASSWORD Used for registration

Virtual host VIRTUAL_HOST Used for registration

Make sure the settings are correct for both port entries. Please use the Message Building System to ease it up.


spirent.com | 19/21

AMQPPort and mno port are connected to the same BROKER_PORT. Therefore, the parameter settings of com.testingtech.ttworkbench.tt3rt.AMQPPortPlugin and com.testingtech.ttsuite.ecall.port.mno are the same.

13.2. Network Emulator Configuration

The Spirent AirAccess WCDMA-HS is required for loading and executing this group of test cases. Please load AtsECall_IVS_Testcases_Emulator.clf and do the following settings in the Parameters view:


spirent.com | 20/21

Now change the following in the Test Adapter Parameters view:

Then configure the link between the Network Emulator and In-band Modem:

Test Adapter Parameter Value Description IMS_ENABLE true VoIP setting as default

IMS_SipPeerProtFamily < SipPeerProtFamily > Protocol family “IPv4” or “IPv6” of the in-band modem

IMS_SipPeerIpAddr < SipPeerIpAddr > IP address of the in-band modem, same as host in AMQP broker

IMS_SipPeerPort < SipPeerPort > Port number of the in-band modem, same as port in AMQP broker

IMS_SiLocalProtFamily < SipLocalProtFamily > Protocol family “IPv4” or “IPv6” of the control PC

IMS_SipLoalIpAddr < SipLocalIpAddr > IP address of the control PC

IMS_SipLocalPort < SipLocalPort > Port number of the control PC

Leave the rest of the parameters to their default, for more details see Chapter 12: ULTS Parameters.

Spirent eCall Alliance SIG Test Suites First Steps User’s Guide

spirent.com/ttworkbench

AMERICAS 1-800-SPIRENT +1-818-676-2683 | [email protected]

US Government & Defense [email protected] | spirentfederal.com

EUROPE AND THE MIDDLE EAST +44 (0) 1293 767979 | [email protected]

ASIA AND THE PACIFIC +86-10-8518-2539 | [email protected]

© Spirent Communications, Inc. All of the company names and/or brand names and/or product names and/or logos referred to in this document, in particular the name “Spirent” and its logo device, are either registered trademarks or trademarks pending registration in accordance with relevant national laws. All rights reserved. Specifications subject to change without notice.

Rev # 2017/04/06 21/21

14. Appendix

Acronyms

CL Editor Core Language Editor NAD Network Access Device CLF Campaign Loader File POTS Plain Old Telephone Service DUT Device Under Test PLMN Public Land Mobile Networks GNSS Global Navigation Satellite System PSAP Public Safety Answering Point HMI Human Machine Interface PSTN Public Switched Telephone Network IVS In Vehicle System TLZ Test Logging Zip File MBS Message Building System USIM Universal Subscriber Identity Module MNO Mobile Network Operator VoIP Voice over IP

Notes This document is subject to change without notice.

Spirent Communications Michaelkirchstraße 17/18, 10179 Berlin, Germany Phone +49 30 726 19 19 0 Fax: +49 30 726 19 19 20 Email: [email protected] Internet: www.spirent.com/ttworkbench

eCall Test Suite - Spirent · PDF file(eCall Test Suite and TTworkbench require a valid...

Documents

Transcript of eCall Test Suite - Spirent · PDF file(eCall Test Suite and TTworkbench require a valid...