1. ME7834 Operator Training

2. Hemendra Pandey - Anritsu PCT System Support - Europe
ME7834 Operator Training
Hemendra Pandey - Anritsu PCT System Support - Europe

3. Course Contents System capabilities System Overview Hardware Software
Protocol Conformance Tool
Basics
Configuring PCT
Using PCT
UE Configuration
Protocol Analyzer
Documentation
Advanced
Parallel Test Controller
MMT Application
Licensing
PCT TTCN3 Custom Test Case Development

4. System Capabilities
The ME7834 is a system of hardware and software capable of providing the testing requirements of the following specifications (depending on the purchased options):
Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol conformance specification
User Equipment (UE) conformance specification; Part 1: Protocol conformance specification

5. ME7834 Protocol Conformance Test System
Advantages ..
Broad test case coverage
Parallel test case execution
Auto-pixit generation
Protocol Analyser
Robust graphical execution environment
Reduce external test house costs
Supports Cetecom TOM database
PCTS – The System
Anritsu has the highest number of validated test cases for LTE FDD.

6. ME7834 System Overview - Hardware

7. Block Diagram Blue RF Green Instrument control LAN
Red Call Processing control LAN
Magenta TE Data path LAN
Light Blue LVDS Digital Baseband
Orange Sync
Brown 10MHz reference

8. MD8470A - CDMA2000 signaling tester
Wide frequency coverage (400 MHz to 2.7 GHz)
Up to 6 CDMA Sectors and 3 EVDO Sectors on up to 2 RFs
CDMA2000 1x/1xEV-DO Rev. A
Up to 3 MD8470As in the system
RF connected via MN8141A combiner
Used for Inter-RAT LTE <-> 1x/EVDO testcases

9. MD8480C - UMTS/GSM/GPRS signaling tester
Up to 1 MD8480 in the system
RF connected via MN8141A combiner
Used for Inter-RAT LTE <-> UTRAN/GERAN testcases

10. Z1452A Linux Server DELL R210 rack-mount PC IPv4 and IPv6 supported
Software includes:
Automated Performance Measurement
Anritsu IMS server
Router Advertisement Daemon
Iperf
FTP server

11. MF6900A - LTE/UMTS Fading Simulator
LTE for FDD and TDD covering 350 to 3000 MHz frequency band
100 MB (DL): 50 MB (UL)
4 RF supports 2x2MIMO handover
Up to 6 Cells (2 communication, 4 neighbor)
Future proof – Cat 4 today
1xMD8430 in the system
MD8430 can contain up to 5 firmware versions

12. MN8141A – RF Combiner Main RF interface to UE Combines RF UL/DL from:
Tx/Rx
Rx Diversity
Combines RF UL/DL from:
MD8430A 2xUL,4xDL
MD8480C 1xUL,2xDL
MD8470A 1xUL/DL
Actual paths losses supplied on USB stick

13. MD8430A - LTE signaling tester
1-2 MD8430s in the system
Each MD8430 can contain up to
5 firmware versions
Connect to Master MD8430 main RF ports for LTE-only testcases
Used for all LTE testcases

14. Control PC Control PC spec is fixed (currently Dell Optiplex G780)
Runs Windows XP
Contains PCT framework and all test case packages
Executes and runs all Test cases
Can use used for UE automation
Manages results archives
Hosts USB dongle for node locked licences

15. Other items/Calibration
Different USIMs are provided for each test package
10MHz reference and Sync is taken from Master MD8430A
MN8110B (up to 2 qty) handles call processing timing between MD8480C and MD8470A
Ethernet Hubs
HUB1 - Main instrument control interface
HUB2 – MD8470A Call processing
There is no system calibration necessary for PCT but is mandatory for CAT system (AT&T package)
Ensure individual units are calibrated regularly (recommend yearly interval)

16. Power Up/Power down Ensure Power on sequence
the mains is connected to the rear of the racks
Mains circuit breakers are switched on
Rear power switch on each signalling and fading unit is on
Power on sequence
Power up all MD8470 units
Start MX application on all units
Start MX847031A Remote Interface application on all units
Start MD8480C
Start MF6900 Fading Unit
Start MD8430A Master and Slave
Start Linux Server PC
Power off sequence is reverse of Power on.
Power on sequence is irrelevant if there is no MD8470 unit in the system

17. PCT- Basics Configuring PCT
Creating project, defining test sequence and test case execution
PICS/PIXIT generation
UE configuration
Protocol Analyzer

18. PCT- Software PCTS – Protocol Conformance Toolkit Software
The PCTS software is run from the Control PC, icon on the desktop or
Start>Programs>Protocol Conformance Toolkit>PCT

19. PCT GUI

20. PCT Configuration

21. PCT Configuration
PCT SW has to be configured so that it can communicate with the SS.
Each unit (MD8430/MD8480) has a fixed IP address which can be constructed through the serial number of the unit.e.g.
The MD8480 IP address is derived from its serial number and is of the form:
1.1.1wx.1yz
where w, x, y, z are the 7th,8th,9th, and 10th digits of the 10 digit serial number labelled on the MD8480.
The MD8430 IP address is derived from its serial number and is of the form:
1.1ab.1cd.1ef
where a, b, c, d, e, f are the last 6 digits of the serial number labelled on the
MD8430.
Provide these IP addresses in the signaling tester setup section of the PCT according to the system configuration.
The Control PC needs to have an IP address of with subnet mask
More details for this configuration can be found in “ME7834AL Protocol Conformance Test System Setup Guide.pdf” section “Configuration”.

22. Selecting the Required CAG/iWD Release
PCT Configuration
Selecting the Required CAG/iWD Release
Before running tests, the required PCT release must be selected (CAG or iWD release). This is done from the drop-down selection box in the PCT GUI. To access this, launch the PCT and System >> Release Selection menu item.

23. Selecting the Required Test Case Catalogue
PCT Configuration
Selecting the Required Test Case Catalogue
PCT can be switched between 3G and LTE catalogue from catalogue-> Switch Type ->3G/LTE option.

24. How to Create a Project: Definition of a Project
Using PCT
How to Create a Project: Definition of a Project
A collection of sequences of test cases having specific configurations, and their results that can be saved and recalled.
A Project is a convenient storage container that consists of one or more test sequences selected from a given test case catalog and with a specified set of attributes to run in a sequential sequence to produce a set of results, that may be related by a common theme. The information needed to create a sequence of test cases include:
The UUT attributes.
The PICS/PIXIT deviations.
The test case catalog.
A selection of test cases from the test case catalog.
The number of iterations of each test case.

25. Creating and Executing a Test Sequence
Using PCT
Creating and Executing a Test Sequence
A test sequence is a collection of test cases configured to a given specification that will automatically run one after another.
Phase 1: Creating a Test Sequence
1. Start the Protocol Conformance Toolkit application via Start >> Programs >> Protocol Conformance Toolkit >> PCT.
2. Create a new Test Sequence, by selecting File >> New >> Test Sequence. Add a name for the test sequence (i.e. NewTestSeq) next to the Name field and also any additional notes next to the Comment field.
3. Test cases can be added to a test sequence one by one or by selecting multiple test cases at a time and then right click -> Copy To Archive Test Sequence.
4. The test sequence is saved in an excel file located at the following location (of respective workspace)
C:\Program Files\Protocol Test System\bin\projects\default\test_sequence\LteFdd
5. The same test sequence can be re-used across different workspaces and releases by simply copy-pasting the excel file at the designated location.

26. Executing a Test Sequence
Using PCT
Executing a Test Sequence
Phase 2: Executing a Test Sequence
5. Select Project >> Execute or click the Execute all tests in the active test sequence button to run the sequence. A progress bar displays the execution status and when complete a new window appears containing the execution results.
6. It is expected that some of these Test Cases may fail. Clicking the link on the test case row takes you to the Protocol Analyzer where the test logs can be examined to determine the failure clause.
Note: The test sequence execution can be stopped at any point by selecting Project >>Terminate all or by clicking the Terminate the currently executing sequence button.
7. The test sequence is saved in an xml file located at the following location (of respective workspace)
C:\Program Files\Protocol Test System\bin\projects\default\test_sequence\LteFdd
8. The same test sequence can be re-used across different workspaces and releases by simply copy-pasting the excel file at the designated location.

27. Using PCT Test Case Execution Configure UUT PICS/PIXIT Deviations
9. To amend the appropriate columns with the correct Pixit values, select Project >> Configure UUT PICS/PIXIT Deviations. The following dialog appears:

28. Configuring UUT PICS/PIXIT Deviation
Using PCT
Configuring UUT PICS/PIXIT Deviation
A new PIXIT deviation file can be created by clicking the Add new PICS/ PIXIT deviation button.
In the dialog box, add the new deviation name (for example MyUE) and any further comments you would like to associate with this deviation. Then click the OK button to save the file. A window appears with a list of existing parameters, to allow you to define the new file. The new deviation file appears to the right of the existing columns. Clicking in any of the cells enables you to enter or select a value from the list of possible values of the specific parameter. If, for example you wish to amend whether Algorithm A5/ 3 is supported, scroll to the pc_MS_ClsmkA5_3 row and add 1 to the MyUE column as shown below:

29. Configuring UUT PICS/PIXIT Deviation
Using PCT
Configuring UUT PICS/PIXIT Deviation
8. To save the deviations file click OK. You will notice that the new file appears at the “Modify UUT PICS/PIXIT Deviations” screen at the bottom of the list and the “Selected” column checkbox is checked. The UUT PICS/PIXIT deviations is applied to every test in the test sequence.
9. Click OK to save the changes, save the test sequence and re-run the tests with the updated parameters.
Note: If there are conflicting PICS/PIXIT parameters in both a UUT and a test deviation, then the test deviation's value overwrites the UUT 's value.

30. Using PCT Auto-PIXIT Generator
To automatically generate the required pixit change parameters, select Tools >> AutoPixit Generator.For a selected LTE/3G release, the following dialog is displayed:
LTE
3G/UTRAN

31. Using PCT Auto-PIXIT Generator
Once the settings are created, click OK to run the AutoPixit Generator. While the PICS/PIXIT deviations for the UE is being generated, a progress bar is displayed to indicate the current status in the generation process. Any tests that need to be run are shown in the background.

32. UE Configuration
UE can be configured either in manual or automated mode. The details of automation mode can be found from ME7834AL Protocol Conformance Test System Setup Guide.pdf section “Configuring Automation “.

33. Protocol Analyzer Use to view the conformance test logs.
Starting Up the Protocol Analyzer
The Protocol Analyzer can be started by launching a web browser using the URL

34. Protocol Analyzer Manage Archives
The Manage Archives view allows you to manage multiple archives across multiple servers and associate your own textual name to each archive.
The logs for the “default” workspace are stored at the following location
C:\Program Files\Protocol Test System\bin\projects\default\results

35. Protocol Analyzer
Every test result in an archive has a colour Status indication icon. The meaning of the icons is detailed below.

36. Protocol Analyzer Expanding a Test Run Folder
A test run can be expanded by clicking on the “[+]” box next to the Folder and Status indication icons.
Usually there are four additional lines of information with icons as shown above, which are as follows:
• Log Data Files – these are the logged data in XML data files from the test run
• Test Report File(s) – these are test report files.
• Message Sequence Analysis View – this icon allows access the sequence viewer and TTCN viewer
• TTCN Analysis View - this icon allows access to the TTCN viewer

37. Mobile Device Test Platform
< Protocol Analyser>
Protocol Analyser shows entire Test Sequence of all
layers, with time stamps for analysis
Allows for Detailed Analysis of any message

38. Protocol Analyzer-Offline Log viewing
Export Logs using protocol Analyzer
Logs open in protocol analyzer can be exported in html format to view offline.
Export Option on Protocol Analyzer.
Logs required for debugging:
Send the complete log folder to Anritsu for debugging.
Please don’t send export log. Export log is just for offline viewing.

39. Documentation
Anritsu provides the following documentation with every CAG release:
ME7834AL Protocol Conformance Test System Setup Guide.pdf
ME7834AL Protocol Conformance Test System User Guide.pdf
ME7834AL Protocol Conformance Toolkit Remote Control Interface Manual.pdf
ME7834L PCT TTCN-3 Custom Test Development Guide.pdf
MX785220A_CAG32A_PVG59_Customer_Release_Note.pdf
Additionally please check the delivery specification

40. PCT- Advanced Parallel Test Controller MMT Licensing
TTCN3 Editor: Custom test case development

41. Parallel Test Controller
Overview
Hardware Setup
System Configuration

42. Parallel Test Controller
Overview
The Parallel Test Controller is part of the Protocol Conformance Test System product. It allows two or three UEs to be tested simultaneously maximising the use of the signalling tester units in a two unit or three unit system resulting in significant reduction in overall test time.
The Parallel Test Controller handles the creation and distribution of pixit files throughout the system (no user intervention is required).

43. Parallel Test Controller
Hardware Setup
LTE
UTRAN

44. Parallel Test Controller
CAMPAIGN CONTROLLER
MD (Master)
MD (1st Slave)
MD (2nd Slave)
PC 1
PC 2
PC 3
Ethernet Switch
RF cable
Ethernet cables
Sync (BNC)
UUT

45. Parallel Test Controller
System Configuration
The system configuration has to be done by an Anritsu Support Engineer.

46. MMT – feature summary Overview Concepts Filtering Logging
Trace logging capability
Monitor logging capability
Measurement logging capability

47. Measurement and Monitor Application
The measurement, monitor and trace information of the LTE test cases can be viewed by using the Measurement and Monitor Application. This application supports accumulation/reset of counters and has the ability to export the information to a spreadsheet.
To use the Measurement and Monitor Application, start the application by selecting Tools > Measurement & Monitor in the PCT window.
Based on the setting defined in the Signalling Tester Setup dialog, the MMT will be automatically connected to the MD8430 and disconnected when the test execution completes.

48. MMT overview MMT is a “helper tool” for the PCT product
MMT is designed to be used during a PCT test case execution to:
Capture & display low level logs from the MD8430A (trace)
Capture & display key data relating to the simulated cells in an MD8430A – Frequency, Power & timing (monitor)
Capture & display key parameters relating to data transmission during a test case execution (measurement)

49. MMT – feature summary : filtering
Filters are used in all the logging types available in MMT
Filters set which parameters are logged
The filter settings are created before MMT logging has started

50. MMT – feature summary : logging
There are 2 types of logging available in MMT
Real time logging
Data is logged (or captured) within one or more windows within the MMT application
Logging stored data to a file
All 3 types of logging (Trace, Monitor, Measurement) can be saved to a log file

51. MMT – trace logging feature
Captures trace data from the MD8430A
The captured data is presented as an MSC view – see screenshot below
This includes messages and data to / from PDCP, RLC, MAC, PHY layers as well as to / from the TE port of the MD8430A.

52. MMT – trace logging feature (cont’d)
Filtering of trace data – filter modes:
There are 2 filter modes for trace data:
Capture : the filtering is applied when the data is captured (i.e. the data excluded from the filter is not displayed or stored)
Display : the filtering is applied when the data is displayed (i.e. the data excluded from the filter is not displayed, but is stored)

53. MMT – trace logging feature (cont’d)
Filtering of trace data – filter types:
The filtering can be specified on the basis of message channel or message primitive or both
Primitive filter selection
Channel filter selection

54. MMT – monitor logging feature
Captures & displays monitor data from the MD8430A
The data is presented in a tabular view – as shown opposite
The data covers key power, frequency and timing parameters output and updating during test execution.

55. MMT – monitor logging feature (cont’d)
Filtering of monitor data:
The filtering can be specified for all the displayed parameters

56. MMT – measurement logging feature
Captures measurement data from the MD8430A
The captured data is presented either in tabular form and can also be displayed graphically
This covers key parameter measurements relating to data transmission during a test execution including:
Tx throughput [DL-SCH]
Rx throughput [UL-SCH]
SDU and PDU counts [DL-SCH, UL-SCH, DTCH]
CRC Error counts
ACK / NACK counts
etc. etc,

57. MMT – measurement logging feature (cont’d)
Main measurement window …

58. MMT – measurement logging feature (cont’d)
Example graphical display …

59. MMT – measurement logging feature (cont’d)
Measurement filtering window …

60. Licensing Installing the Dongle Driver Software Node Locked License
The license key supplied by Anritsu a text file with a ".dat" extension. It will either be a "Node locked" (single user) license or a "Floating" license.
Installing the Dongle Driver Software
It is essential that dongle drivers and license server software are updated to the versions supplied with the PCTS software. The license dongle is supplied by Anritsu with the PCTS software and must be attached to the appropriate port (USB or parallel).
Node Locked License
Floating License

61. PCT TTCN-3 Custom Test Case Development
How to use Anritsu PCT TTCN-3 editor
How to build an executable test
The LTE test case TTCN source files (located at C:\Program Files\Protocol Test System\Development_iWDDev_DYYwkWWvXX\Executable_Test_Suites\ <specification(e.g. Rel8_Mar2009)>\3GPP-TS \ttcn\source) can be edited using the Anritsu PCT TTCN-3 Editor and then the executable must be rebuilt to run the test cases in PCTS.

62. How to Install your Anritsu PCT TTCN-3 Editor and Builder License
Anritsu PCT TTCN-3 Editor and Builder are installed along with your PCT. Standalone installation of Anritsu PCT TTCN-3 Editor and Builder can also be done by using the Install TTCN-3 Editor and Builder Only button in the PCT installer. This will install the TTCN-3 Compiler, Editor and Development parts. After this installation you will be able to edit the TTCN-3, compile and build a new ttcn3Cli.exe.
You must have a Anritsu PCT TTCN-3 Editor and Builder license, which is accessed through a server. A combined license file is provided for Anritsu PCT TTCN-3 Editor (MX785220A-061) and PCT TTCN-3 Builder (MX785220A-062), along with the PCT license.
Refer PCT TTCN-3 “Custom Test Development Guide.pdf” for license installation and verification.

63. Anritsu PCT TTCN-3 Editor
To open the Anritsu PCT TTCN-3 Editor, select Start >> All Programs >> Protocol Conformance Toolkit >> TTCN3 Tools >> Anritsu PCT TTCN-3 Editor or double-click Anritsu PCT TTCN-3 Editor.exe available at C:\Program Files\Anritsu\TTCN-3 Tools\TTCN-3 Editor.

64. Project and TTCN-3 Test Suite Organization
Anritsu PCT TTCN-3 Editor Workspace
The workspace of the Anritsu PCT TTCN-3 Editor is a dedicated folder located at <TTCN 3 Installdir>/eclipse/workspace. It contains all non-linked files and folders of your projects as well as private editor data in the .metadata subfolder.
Please do not change anything in your workspace outside the editor as this can corrupt your workspace.
Project Organization
Projects are used in the editor to group one or more TTCN-3 test suites together.
All projects in your workspace are listed in the Project Selector view.
A project and its contained TTCN-3 test suites are edited and managed in the Project Browser window.

65. End!