INET Spectra MLT Training Overview v0[1].4

7/28/2019 INET Spectra MLT Training Overview v0[1].4

1/46

INET Spectra MLT

Training Course Guide

Abstract

This document provides the tester with the general basic instructions in planning,

creating, and executing a Message Level Test plan across the IOS-A1 interface for a

partially simulated CDMA MSC-BSC testing environment.

Status: Preliminary Version: 0.4Issue Date: June 26, 2002

Inter-Vendor Verification & Validation

Motorola, Inc.

Global Telecommunications Solutions Sector

5555 N Beach St, MD TX-14/4H

Ft. Worth, TX 76137 U.S.A


2/46

REVISION HISTORY

DATE VERSION AUTHOR NOTES

May 5, 2002 0.1Minh Nguyen, Richard Smith,

Rich OverathInitial Draft

May 23, 2002 0.2Minh Nguyen, Richard Smith,

Rich OverathUpdated Changes fromReview, Added Section 7&8

July 26, 2002 0.3 Rich OverathRichard Smith

Updates from review.

July 27, 2002 0.4 Brian AustinRichard Smith

Corrected revision tablecorruption section

numbering.

2


3/46

Glossary of Terms

A Interface Messaging interface between the MSC and CBSC as defined in the CDGIOS 4.0 standard.

ANSI-41 American National Standard Institute Interim Standard 41BSC Base Site or Base Station Controller

BSS Base Station System. Consists of one CBSC and associated BTS;represents the fixed end of the radio interface for a cellular system.Provides control and radio coverage functions.

CBSC Centralized Base Station ControllerChC7 China CCITT Signaling System 7CDG-IOS CDMA Development Group Inter-Operability Specification for MSC to

BSC Signaling Interface.CDMA Code Division Multiple Access as defined in IS-95A.CVR Conformance, Validation, and RegressionESN Electronic Serial NumberHLR Home Location Register

IMSI International Mobile Station IdentifierINET Common name used for Spectra test tool developed by Inet Inc.IVVV Inter-Vendor Verification and ValidationIWF Inter-Working FunctionMDN Mobile Directory NumberMC Message Center (SMSC)MIN Mobile Identification NumberMLT Message Level TestMS Mobile StationMO Mobile Origination

MT Mobile TerminationMSC Mobile Switching CenterMWI Message Waiting IndicatorOTASP Over The Air Service ProvisioningPCF Packet Control FunctionPDSN Packet Data Serving NodePSTN Public Switched Telephone NetworkRAN Radio Access NodeSICD System Interface Control DocumentSMS Short Message ServiceSMSC Short Message Service Center

SMS-DPP Short Message Service Delivery Point to PointSP Signaling PointSS7 Signaling System 7TCAP Transaction Capabilities Application PartVLR Visitor Location Register

3


4/46

Table of Contents

1.0 INTRODUCTION..........................................................................................5

2.0 IOS MLT TEST SUITE SELECTION ........................................................52.1 CDG-IOS AND SICD DOCUMENTATIONS .....................................................................................................5 2.2 MOTOROLA-VENDORCOMPLIANCY REGARDING SUPPORTED FEATURES .....................................................5

3.0 INET SPECTRA HARDWARE/SOFTWARE AVAILABILITY ............5

3.1 SYSTEM COMPONENT VERSIONS ...................................................................................................................5 3.2 DECODERS SUPPORTED .................................................................................................................................7

4.0 TEST ENVIRONMENT SETUP..................................................................7

4.1 LAB LAYOUT INTERCONNECTS......................................................................................................................7 4.2 CABLING REQUIREMENTS..............................................................................................................................8

5.0 LINK CONFIGURATION AND ALIGNMENT........................................85.1 LEVEL 1 PARAMETERS ..................................................................................................................................8 5.2 LEVEL 2 PARAMETERS ..................................................................................................................................9 5.3 LEVEL 3 PARAMETERS ................................................................................................................................11 5.4 AUTOMATIC RESPONSES .............................................................................................................................13

6.0 CVR TESTER MODES...............................................................................14

6.1 LEVEL 2 TESTER(781) ......................................................... ................................................................ .......146.2 LEVEL 3 TESTER(782) ......................................................... ................................................................ .......156.3 TCAP TESTER(787) ............................................................. ............................................................. .........15

7.0 SCRIPTING OF CALL FLOWS................................................................16

7.1 VARIABLE INTEGRATION .............................................................................................................................18 7.2 DATABASE INTEGRATION ............................................................................................................................18 7.3 TIMERS AND USERACTIONS........................................................................................................................23 7.4 BATCH MODE ..............................................................................................................................................24

8.0 MESSAGES AND TRIGGERS ..................................................................25

8.1 SYSTEM/SUBSCRIBERDATABASE CHECKLIST .............................................................................................25 8.2 MASKING OF PARAMETERFIELDS ...............................................................................................................27 8.3 ASCII SIGNAL UNIT CONVERSION ..............................................................................................................30

9.0 DATA CAPTURE AND LOGGING..........................................................42

9.1

MESSAGE FILTERS.......................................................................................................................................429.2 DATA FILES VS PRINT FILES ........................................................................................................................43

10.0 NETWORK EMULATION CAPABILITIES...........................................43

10.1 SS7 TESTERMODE......................................................................................................................................44 10.2 ISUP/TUP (PSTN) EMULATION .................................................................................................................45 10.3 IS-41 (HLR/SMSC) EMULATION................................................................................................................45

11.0 DEBUGGING HINTS..................................................................................45

11.1 USE OF SS7 TOOLS (F8) ......................................................... ........................................................... ..........4511.2 SYSTEM-LEVEL TEST DATA LOGS...............................................................................................................46

4


5/46

1.0 Introduction

This course is designed to provide testers with a general guideline on planning, creating, and executing a

Message Level test plan for the basic purpose of verifying and validating the CDG-IOS interface. This

will be accomplished by an instructor led presentation and hands on exercises that will allow the testers

to become familiar with the various methods and screens required to operate and execute the INET

Spectra applications. After completing the course, each tester should be able to setup the lab environmentneeded to execute the test case, build and simulate the call flows as defined by CDG-IOS, and debug any

necessary problems involved during the test verification steps.

2.0 IOS MLT Test Suite Selection

2.1 CDG-IOS and SICD Documentations

This document presents the interoperability test specifications for the TR45 Interoperability Specification

(IOS) for the CDMA 2000 Access Network Interfaces, also known as TIA/EIA/IS 2001. It is intended to

serve as a guideline for CDMA network element vendors, and network operators, for interoperabilitytesting between Mobile Switching Systems, Base Stations, Packet Control Functions, and Packet Data

Serving Nodes, that implement the Interoperability Specification. Motorola intranet access is needed to

view this document.

2.2 Motorola-Vendor Compliancy Regarding Supported Features

An example of this document is found in the IVVV web site. Motorola intranet web access is needed to

access this document. This document will be specific to the features that all vendors and service

providers agree to.

3.0 INET Spectra Hardware/Software Availability

3.1 System Component Versions

After the INET Spectra box is powered on and booted choose F1 Setup from the screen shown:

5
http://www.cig.mot.com/Organization/asra/projects/sicd/a%2b/ver_16.0.1/sicd.pdfhttp://www.cig.mot.com/Organization/asra/projects/sicd/a%2b/ver_16.0.1/sicd.pdfhttp://ivvv.ftw.mot.com/Alcatel/Projects/AM16.0/AM_16-TS-10.pdfhttp://ivvv.ftw.mot.com/Alcatel/Projects/AM16.0/AM_16-TS-10.pdfhttp://www.cig.mot.com/Organization/asra/projects/sicd/a%2b/ver_16.0.1/sicd.pdfhttp://www.cig.mot.com/Organization/asra/projects/sicd/a%2b/ver_16.0.1/sicd.pdf


6/46

From this screen choose the Component Version (keystrokes to get the screen as pictured will be shown

in bold text before picture):

F1

When Component version is selected you will see this screen:

F1 / COMPONENT VERSION

6


7/46

3.2 Decoders Supported

From the component screen choose the Decode Screen Option to verify the China IOS40 or the newest

decode is loaded. This is an example of the Decode Screen :

F1 / COMPONENT VERSION / D

4.0 Test Environment Setup

4.1 Lab Layout Interconnects

SMSC

BSC (Motorola)

INET Spectra Analyzer

(SMSC or PSTN emulation is optional)

ANSI-41/ChC7/E1A1/ChC7/E1

HLRAi/TUP/E1

PSTN

MSC/VLR

7


8/46

4.2 Cabling Requirements

The INET Spectra as pictured above will be cabled directly to the vendor Mobile Switching Center. Ports

on the Spectra will contain a small cable connection box called a Pod. These Pods will connect the

Spectra to the MSC with a cable. The cables used can be bantam, bnc, 37 pin female, 25 pin female or

RJ-45 connectors. The cable connection is configured in the Level 1 parameters. When the cables have

been connected and configured correctly the port will show up in green at the bottom of the Spectrascreen as shown in the following picture of the Spectra INET box. Notice the port is labeled available

in this picture. Some will be labeled In Service.

F2 / N (for no option)

5.0 Link Configuration and Alignment5.1 Level 1 Parameters

From the F1 screen select the Level1 Parameters option and you will see the following screen:

F1 / LEVEL 1 PARAMETERS

Here is a breakdown of the parameters:

8


9/46

Interface- determined by the pod connected to the port. You cannot change this other than between DS1

and E1.

Fanout- Must have a DS1/E1 pod must connected to link 1 for this option to work. If you want multiple

channels (timeslots) from a single DS1 or E1 interface to be processed. Pressing the F key when the

cursor is on any Board 1 field turns the Fanout Bank 1 option (Boards 1-8) ON or OFF.

Type- defines how the Spectra system uses the link. The options displayed depend on the purchased

configuration. The options available are SS7, ISDN, or X.25. The OFF option allows individual boards to

be deactivated.

Link- This field defines the physical link number for the board. This number is the same as the board

number.

Baud Rate- This field defines the data rate for each interface. This option does not have a function in

DTE mode (other than reference) for the V.35, RS449, and RS232 interfaces.

Mode- This field allows selection of DCE or DTE configuration for the V.35, RS449, and RS232

interfaces.

Data/Clock- This function allows selection of Normal, Invert Data, Invert Clock, or Invert Both.

Bridged/Term/DSX MON- This field sets interface impedance to Bridged, Terminated, or DSX MON.

Use the Bridged option for monitoring a line terminated by another device. Use the Terminated option

when the link is terminated to the Spectra box. Use the DSX MON option (DS1/E1 and DS0-A only)

when monitoring through a DSX monitor port.

Data SRC (LNK)- The Data SRC (LNK) parameter is only available for DS1, E1, and BRI interfaces.

This field indicates the physical interface from which data is processed. This is equal to the link number

when in single channel mode (only one Tx and Rx timeslot is processed from each DS1/E1 physical

interface) and equal to Link 1 when in Fanout mode. This option is not user changeable.

Line Code- This field sets the line code for DS1/E1 interfaces.

Equalization- This field sets the transmit equalization according to the transmit distance for DS1

interfaces.

Framing- This field sets the desired framing format.

Rx/Tx Timeslot- This field indicates the receive and transmit timeslot number to process. The range is 1-

24 for the DS1 and 1-31 for E1.

Local/Loop- This field selects transmit timing source as local oscillator from the Spectra system (local)

or recovers clock from the received signal (loop).

If a problem is encountered in getting a port to come In Service or Available and the green light will

not come on, check and verify your configuration of the Level 1 settings. After making changes to Level

1 parameters always use the Save Configuration option seen in the F1 screen shot. You will be given the

option of choosing a new name when you use Save Configuration.

5.2 Level 2 Parameters

To access the Level 2 Parameters return to the original screen accessed by F1 key. From the pull down

menu choose Configure and then select Level 2 Parameters as shown:

F1 / CONFIGURE

9


10/46

Once the Level 2 Parameters is selected you will see the following screen:

F1 / CONFIGURE / SS7 / LEVEL 2 PARAMETERS

Level 2 Parameters screen is for assigning Message Transfer Part level 2 parameters for the Spectra SS7

links. If the Spectra system is being configured for monitoring, only the protocol, error method, and

maximum octet size must be set. For all the emulation, generation, and manipulation modes, allparameters must be set. The timers should be set to match those of the system under test. Here is a brief

description of the Level 2 Parameter fields. Normally the protocol is the only field to set on this page.

Protocol- This field describes the method or language of communication used. These options are

available: ANSI, ITU-T Red, ITU-T Blue, ITU-T White, CHINA, BTNR, JAPAN

Error Correction Method- This field provides both Basic and Preventative Cyclic Retransmission

(PCR) error correction methods.

Basic- When this option is used, PCR-N1 and PCR-N2 fields cannot be applied.

PCR- The PCR error correction method is normally used when there is a substantial distance between

signaling points, such as with satellite transmission of the signal. Inets proprietary PCR filtering

algorithm provides error-free, real-time PCR filtering without signal unit acquisition problems.

10


11/46

PCR N1- The PCR timer that defines the maximum number of MSUs available for retransmission.

PCR N2- The PCR timer that defines the maximum number of MSU octets available for retransmission.

Xmt Flags- This field sets the maximum number of flags transmitted between two messages.

Max Octet Size- This field defines the maximum size of a message before it causes an error (long SU

error).Timers 1-7- Timers 1 through 7 are used for Spectra Level 2 procedures. These timers should be set to

match those of the system under test.

EIM Timer- This timer defines the EIM of the Spectra system. The EIM is an alternate method of error

rate monitoring used by certain variants of SS7.

LSSU Timer- This value defines the rate at which the LSSUs are transmitted by the Spectra system.

FISU TMR- This value defines the rate at which FISUs are transmitted by the Spectra system.

TX Window Size- This value defines the maximum number of transmitted messages allowed by the

Spectra system without receiving an acknowledgement message.

LSSU Length- This defines the LSSU length.

After making changes to Level 2 parameters always use the Save Configuration option seen in the F1

screen shot. You will be given the option of choosing a new name when you use Save Configuration.

5.3 Level 3 Parameters

Refer to the first screen picture in section 5.2 to gain access to Level 3 Parameters. From the menu

choose Level 3 Parameters and the following screen will be displayed:

F1 / CONFIGURE / SS7 / LEVEL 3 PARAMETERS

11


12/46

The fields that need to be configured for most MLT testing are Network Configuration, Link to Linkset

Definitions, and Point Code Names. Once the point codes are known begin with point code names. A

sample of display of Point Code Names is displayed in the following screen:

F1 / CONFIGURE / SS7 / LEVEL 3 PARAMETERS / POINT CODE NAMES

Format- This option sets the point code format, ANSI, China (8-8-8 bit) and ITU (3-8-3 bit).

Point Code- The actual point code for the network object.

Name- The assigned name for the point code. Maximum of 11 characters is allowed.

Linkset Definition Screen is used to assign Spectra links to Linksets and to assign SLCs to the links

within a linkset. An example of a Linkset definition is shown in the following screen:

F1 / CONFIGURE / SS7 / LEVEL 3 PARAMETERS / LINK TO LINKSET DEFINITIONS

12


13/46

Network Configuration- An example will be shown after this brief description of the network

configuration. The entries in this screen define the behavior of the Spectra system. The Network

Configuration Screen can be used to do the following procedures: Assign links to linksets, assign linksets

to signaling nodes, and define SP information such as Network Indicators.

F1 / CONFIGURE / SS7 / LEVEL 3 PARAMETERS / NETWORK CONFIGURATION

Once this screen has been configured it is necessary to choose the CfgLinksets option. Here is an

example of the Configure Linksets screen:

F1 / CONFIGURE / SS7 / LEVEL 3 PARAMETERS / NETWORK CONFIGURATION / C

Many more network configurations can be accessed from this screen but they are outside the scope of

MLT. More information on this or any other section is available on the IVVV Technical web page under

the INET section. This web page is on the Motorola intranet. After making changes to Level 3

parameters always use the Save Configuration option seen in the F1 screen shot. You will be given the

option of choosing a new name when you use Save Configuration.

5.4 Automatic ResponsesThe Spectra system can be set to respond automatically to certain incoming messages (events) by sending

out a defined response. The TUP, BTNR, ISUP, and SCCP options are predefined incoming events with

13
http://ivvv.ftw.mot.com/IVVV/Helpful_Sites/Spectra1.09/http://ivvv.ftw.mot.com/IVVV/Helpful_Sites/Spectra1.09/


14/46

predefined responses. Automatic Responses screen is accessed the same as Level 2 and Level 3

parameters. Here is a sample screen of the Automatic Responses:

F1 / CONFIGURE / SS7 / AUTOMATIC RESPONSE / USER DEFINED / EVENT

6.0 CVR Tester Modes

This screen sets the operating modes for the selected protocols. Once the Spectra system is configured, a

mode must be selected. The next three sections give some of the operating modes used in MLT.

6.1 Level 2 Tester (781)

This screen is accessed through the F1 screen and selecting the Mode option. From there you select CVR

Tester and Level 2 Tester will be an option and selecting this will display the Linksets available. Here isa sample screen for the Level 2 Tester:

F1 / MODE / CVR TESTERS / LEVEL 2 TESTER

Performing the Level 2 tester will verify the level 2 is configured and level 2 is performing properly.

14


15/46


16/46

7.0 Scripting of Call Flows

Scripts are built in the CVR-TCAP menu.

F1 / MODE / SS7 / CRV / TCAP TESTER / LINK SET

Script Editor Access Menu

Script Editor Menu

Available script options include:

Transmit Signal Unit out designated Link.

The Transmit Options offer a way for the TCAP Tester Mode to assign a signal unit for

transmission with control over the various attributes of the signal unit to be transmitted.

These various attributes are listed in the TCAP Tester Transmit Option Menu. Follow

these steps to transmit messages in TCAP tests:

Wait for trigger on designated Link.

The Trigger Options offer a way for the TCAP Mode to perform certain actions based on

the reception of certain messages.

:COMMENT-Terminal

15 Character message to display/log on the terminal side.

:COMMENT-Tester15 Character message to display/log on the tester side.

16


17/46

:Terminal User Action

The Terminal User Action option allows you to pause the test, and add a short comment

(15 characters maximum) to be added to the screen on the Terminal side. When the test

is run (using F2) and the test reaches this point, the test pauses with the comment

displayed on the screen, and the message Press Spacebar to trigger flashes at the top of

the screen. This signifies that a given manual action is to be performed by the operator atthe terminal and that the Spectra operator is to be notified. Press the Space Bar to resume

the test at anytime.

:Tester User Action

The Tester User Action option allows you to pause the test, and add a short comment (15

characters maximum) to be added to the screen on the Spectra side. When the test is run

(using F2) and the test reaches this point, the test pauses with the comment

displayed on the screen, and the message Press Spacebar to trigger flashes at the top of

the screen. This signifies that the test is paused until it is prompted by the operator. Press

the Space Bar to resume the test at anytime

Wait for *** SEC

This option allows you to place a timed pause in the test. When the test is run using F2,

and the wait is encountered in the test script, no new triggers or actions are processed or

transmitted until the wait time has expired.

Send/Wait signal to Test

The SS7 TCAP Send Signal to Test and Wait for Test Signal options are used to

coordinate the execution of test scripts across protocols. This feature is useful whentesting multiple protocols that require interaction between one another.

GET

This option controls what specific data is to be copied from an incoming trigger message.

In the script, the GET statement must be immediately preceded by the Trigger message

from which it will be copying data. Multiple GET statements can be used to copy more

than one piece of data from the same trigger message. The data derived from the GET

gets stored as a variable. The PUT option can then reference the stored variable.

PUT

PUT Statements control where data is to be placed within an Action (transmitted)

message. The data to be copied is specified by a user defined variable created by the

GET statement, or is selected randomly or sequentially from a number database. Number

databases are created in the Generator section of the Spectra system. If you did not

purchase a Generator package, you cannot create or access number databases.

PLAY TONE

The Play Tone feature allows you to add tone generation to scripts in the Level 4 Tester

modes (TCAP, TUP/ISUP, and ISDN).

17


18/46

7.1 Variable Integration

Some data received in messages from the MSC must be returned in messages transmitted back to the

MSC. This is accomplished using the GET (extract data from received message) and PUT (set data in

transmitted message) statements in the scripts. The most common uses of the GET and PUT statements is

for SCCP connection Reference Numbers and TAG values sent in page commands.

Below is an example of using GET to store the TAG received in the page message from the MSC as a

variable and returned in the page response to the MSC:

GET - PUT Example

7.2 Database Integration

It is desirable to minimize the amount of re-work required when tests are executed in different

environments. Using variables stored in a database can help achieve this and reduce the number of signal

units required.

The scripts should be built in a way that standardizes such things as the originating mobile, terminating

mobile, land line directory numbers, etc.

For example Mobile 1 should always be the originating mobile. Mobile 2 should always be the

terminating mobile. Land 1 should always be the land party in M-L and L-M calls. Of course there are

tests outside the basic M-M,M-L, and L-M calls but these basic calls cover the majority of the test cases.

Using unique signal units and variables can satisfy the cases that are outside of these basic calls. Keeping

this in mind when developing the test scripts will decrease the amount of work required to setup for new

environments.

Example of attributes which will differ from site to site include:

1. MINs/IMSIs.

2. ESNs.

3. Called/Dialed numbers.

4. Feature activation/deactivation codes.

5. Cell Identifiers.

18


19/46

6. LAC identifiers.

7. Market ID / Switch Number

Note: Using the database requires the INET to be equipped with the Generator option.

The database is accessed by:

F1 / MODE / SS7 / TCAP GENERATOR / LINK SET / NUMBER DATABASE

Database Menu

When in the database entry the P key will access the file properties for display and edit.

Database - File Properties:

From the Number Database Properties screen you can configure the following properties:

Database Field Length

This option allows you to set the length (in characters) for a database field (maximum

number of 33 characters) for the entire database. Entries having less than the specified

maximum field length are appended with fill-in characters. Databases with NUMBER

GENERATION set to Sequential append entries with zeros; databases with NUMBER

GENERATION set to Random append entries with asterisks (*). To avoid appended

characters, add leading zeros to entries that are less than the defined field length.

When adding leading zeros to numbers in ranges, ensure the value on the left of the tilde (~)

contains a smaller or equal number of digits than the value on the right side of the tilde (~).

Database Line Selection

This option allows you to set the database line selection to be either either Random or

Sequential. This field is only applicable when a range of numbers is specified.

Number Format

This option allows you to select the type of output number format for the database. Press the

key to toggle between Decimal or Hex format.

Random/Sequential Generation

19


20/46

This option allows you to set the number selection within the DATABASE FIELD to either

Random or Sequential. This field is only applicable when a range of numbers is specified for

the DATABASE FIELD entry. In fields in which a specific digit string is defined without a

range or wildcard, the specified digits are generated regardless of this setting.

NOTE: The NUMBER GENERATION field must be set to Sequential before the DB LINE

SELECTION field can be set to Sequential.

Increment Factor

This option allows you to set the increment value used during number generation. Negative

numbers can be used to decrement the number selection.

NOTE: Valid increment/decrement numbers are -99 to 99.

Digit Encoding

This field allows you to select the digit encoding of the database to BCD or ASCII. Set this

field to match your network requirements. Press the key to toggle between BCD

or ASCII.

Database Entry

The database files are stored in C:\SPECTRA\GENERATE directory. Files can be copied

from/to this directory between INETs.

Note: Hex digits a~f in the database record must be in represented in lower case. (see contents of

ESN_2.NUM below)

20


21/46

Example of database variable used to set the IMSI and ESN:

FILE IMSI_2.NUM

CONTENTS 460120905060024

PROPERTIES:

DB FIELD LENGTH 15

DB LINE SEL NA

NUMBER TYPE DECIMAL

NUMBER GENERATION NA

INC BY NA

DIGIT ENCODING BCD

FILE ESN_2.NUM

CONTENTS acdc0024

PROPERTIES:

DB FIELD LENGTH 8

DB LINE SEL NA

NUMBER TYPE HEX

NUMBER GENERATION NA

INC BY NA

DIGIT ENCODING BCDRAW

USE IN SCRIPT:

SS7 TERMINAL LINKSET LINKSET TCAP TESTER

< ------- 1 PAGRSP.SCC

Src Type=NUM DB Src Name=IMSI_2 Byte=62 Bits=4 Bit Len=60

Src Type=NUM DB Src Name=ESN_2 Byte=73 Bits=0 Bit Len=32

21


22/46

PAGRSP.SCC IMSI and ESN Parameters:

Signal unit contents:

octet061 Mobile Identity (mandatory param)

00001000 Parameter Length.. 8

.....110 Type of Identity.. IMSI

....1... Odd/even indicator Odd number of address signals

0100.... 1st Digit......... 4

........ Digits............ 60030923231200

octet070 CDG-IOS parameter.

00001101 Parameter Ident... Mobile Identity


.....101 Type of Identity.. ESN

....0... Odd/even indicator Even number of address signals

0000.... Digit 1........... 0........ ESN: ManCode+Srial# 23 23 12 00

As sent by Script:

octet061 Mobile Identity (mandatory param)


.....110 Type of Identity.. IMSI

....1... Odd/even indicator Odd number of address signals

0100.... 1st Digit......... 4

........ Digits............ 460120905060024

octet070 CDG-IOS parameter.





0000.... Digit 1........... 0

........ ESN: ManCode+Srial# AC DC 00 24

22


23/46

7.3 Timers and User Actions

Wait statements are used in scripts to allow time between events. Generally it is used to delay the INET

sending a message in response to receipt of a message from the MSC. An example is delaying the time

between the MSC sending the Assignment Request and the INET/CBSC returning the Assignment

Complete.

Terminal/Tester User Action statements are used in the scripts as a prompt where some manual action is

needed. An example would be on a Land to Mobile call the tester is prompted to make the land call to the

mobile subscriber.

Timer / Action Example

23


24/46

7.4 Batch ModeF1 / MODE / SS7 / CRV / BATCH TEST BUILDER

Batch Test Builder Menu Access

BATCH TEST BUILDER

The Batch Test Builder allows a group of Level 2, Level 3, TUP, ISUP, Manipulator, or

programmer's Mode tests to run in sequence without interruption. This allows the user to

conveniently run several tests at a time without having to be at the PC to execute each test

individually. The Batch Test Builder also provides easy viewing of PASS/FAIL test results and

other information in a Batch Test Summary Screen.

There is an overall limit of 50 command lines per script. This limitation becomes a problem

when building some of the more complicated call scenarios. When the call scenario cannot be

contained in 50 lines, the call scenario can be divided into multiple scripts. These segmented

scripts can then be linked together and ran as a batch.

24


25/46

8.0 Messages and Triggers

8.1 System/Subscriber Database Checklist

Managing signal units and databases.

Care must be taken when changes are made to signal units. If an existing signal unit is edited to matchthe condition of a particular script other scripts that also use the signal unit will be affected.

Documenting the signal units and database files using spreadsheets is helpful with the management of

this data.

This information is recorded in three spreadsheets.

1. Transmit / Trigger Signal Unit Registry

This spreadsheet records all signal units used within the test scripts. For each signal unit all

information elements contained in the transmit (PUTS) and trigger (GETS) signal units whichvary from site to site and other fields which require variables are recorded. Information regarding

specifics on the signal unit are also noted. As new signal units are required and created they are

added to this spread sheet. Separate spreadsheets are created for the transmit signal units and the

trigger signal units.

Example signal units:

Transmit Signal Unit Spreadsheet

2. Signal Unit Assignments

This spread sheet records all signal units and their assignments within the scripts. If new signalunits are required and built they must also be added to this spreadsheet.

Example signal unit assignments:

Signal Unit Assignment Spreadsheet


26/46

3. Database Spreadsheet

This spread sheet contains entries for all database files. It includes the file properties and should

be used to record the system configuration for each new test suite execution.

Example of database spreadsheet:

Database Spreadsheet

26


27/46

8.2 Masking of Parameter Fields

Any message used in a script as a Trigger must have the mask defined. This mask defines what data

within the signal unit must match in order for the message to cause the trigger to occur. Data that is

masked is not evaluated. Data that is unmasked is evaluated.

When running a script a message that the INET triggers on will be displayed in BLUE in the buffer

display.

The mask is defined using the CREATE/EDIT MESSAGE feature in the INET.

F6 / CREATE-EDIT MESSAGE / CHINA / select signal unit

Signal Unit Editor Access

27


28/46

When viewing a signal unit in the message editor masked data is highlighted. Data which is not

masked is not highlighted. Below is an example where byte10 (Message Type > Connection

Confirm) and the Protocol Class fields are unmasked.

Example of Defining Mask

When defining the mask in the message editor:

Z will mask all data

U will unmask the selected field/byte.

M will mask the selected field/byte.

General guidelines for defining trigger mask:

1. Data within the header such as the OPC/DPC should be masked There is no need to verify

this data because it must be correct in order for the message to be received/evaluated by the

INET.

2. Data that varies from call to call, such as the SCCP reference numbers/CICs, should be

masked.

3. At a minimum the Message Type should be unmasked.

4. Data which the test is specifically verifies should not be masked

5. The more data is left unmasked the more accurate the test is. The trigger signal units should

be examined closely to determine the mask settings.


29/46

Notes:

The INET message editor will sometimes add an extra byte (00h) at the end of the signal unit.

This extra byte can cause a received message not to trigger correctly. When this occurs the last

byte should be deleted in the signal unit editor. (EndSu function)

If a trigger message is shortened using the editor the trigger can still occur even if the

received message is longer than the trigger message. In this case the received message is

evaluated against the unmasked bytes of the trigger message. All bytes received past the last

byte of the trigger message are not evaluated.

The mask can also be used to designate data within transmitted messages that should not be

changed. Setting the mask in the transmitted messages has no affect on the message/script it is

only a method of designating data that should not be changed.


30/46

8.3 ASCII Signal Unit Conversion

The INET provides a method of importing signal units from file(s) in ASCII format.

F6 / IMPORT ASCII SIGNAL UNITS / CHINA / path.filename

Import Signal Unit Menu

Importing of files allows for signal units to be edited on a PC and imported back to the INET.

This feature is useful for populating the signal units with data which is specific to the test environment.

This section will cover the INET import function.

Procedure to export/import signal units:

1. The signal units must be stored in a ASCII representation of the HEX data.

The signal units can be created in a test editor or extracted from the INET. When extracted from the

INET (as a print file) the format of the message must be changed to the format required for importing.

Procedure to extract the message from the INET:

a. Use F6/CREATE-EDIT MESSAGE function and select the message.

b. T to toggle the message to HEX mode.

c. * - to print the message.

d. F8 / DOS COMMANDS / Select print file in directory C:\SPECTRA\PRINTLOG\signal

unit name.PRT.

e. O and copy file to floppy disk.

f. Copy the file to the PC where the file can be edited.

2. Edit the file ACSII/HEX file that was copied from the INET.

Example file format of INET print file:CLRRQ.SCC

30


31/46


32/46

Example of defining: Source / Destination Point Codes, IMSI of Mobile 1, ESN for Mobile 1,

Land 1 Called Number, LAC 1, and CELL 1.

CM Service Request Message in ASCII/HEX (import) format:

#00003F83SSSSSSGGGGGG0101AA00000202070543SSSSSSFE040543GGGGGG

FE0F4800465705050100Lacel1173C030024910CCA006300020E6A010300F

006M1M1M1M1M1M1M1M1M1C1C1C1C1C1C1C1C1C1E1E1E1E1E1E1E135020380

01110B1B03022F82F0030151C11800#CMS_1

Parsed Message:

(bytes 0 ~ 29)

|0112233445566778899|1112233445566778899|2112233445566778899

#00003F83SSSSSSGGGGGG0101AA00000202070543SSSSSSFE040543GGGGGG

(bytes 30 ~ 48)

|3112233445566778899 |4 1122 334455667788

FE0F4800465705050100 Lacel1 173C03002491

LACCell

(bytes 49 ~ 61)

99|5112233445566778899|611

0CCA006300020E6A010300F006

Classmark Info

(bytes 62 ~ 79)

2233445566778899|7 112233445566778899

M1M1M1M1M1M1M1M1M1 C1C1C1C1C1C1C1C1C1

IMSI CLD

(bytes 80 ~ 91)

|8112233445566 7788 99|911

E1E1E1E1E1E1E1 3502 038001

ESN Slot Ser.Op

(bytes 92 ~ 105)

2233445566778899|A1122334455

110B1B03022F82F0030151C11800#CMS_1

IS2000 Mobile Cap.


33/46

Unique Patterns:SSSSSS = Source Point CodeGGGGGG = Destination Point CodeM1M1M1M1M1M1M1M1M1 = IMSI for Mobile 1C1C1C1C1C1C1C1C1C1 = Called Number Land 1E1E1E1E1E1E1E1 = ESN of Mobile 1

La = Lac 1Cel1 = Cell 1

Global changes using editor:Find: Replace With: Value:SSSSSS 555555 085-085-085GGGGGG 510B00 000-011-081M1M1M1M1M1M1M1 084E06219020500010 460120902050001C1C1C1C1C1C1C1C1C1 5E07803103020500F2 13302050002E1E1E1E1E1E1E1 0D0505ACDC0001 ACDC0001La 01 01Cel1 0064 Cell 6 Sector 4

CM Service Request Message after global Find/Replace:

#00003F83555555510B000101AA00000202070543555555FE040543510B00

FE0F4800465705050100010064173C030024910CCA006300020E6A010300F

006084E062190205000105E07803103020500F20D0505ACDC000135020380

01110B1B03022F82F0030151C11800#CMS_1

33


34/46

4. Defining the mask pattern.

The mask for the signal unit is defined using the following format:

The mask pattern begins and ends with $ character

The mask is defined per each nibble (4bits) as 0 or F.

0 = unmask / F = masked

Example of the Cell Parameter field of CMS_1 masked:

$000000000000000000000000000000000000000000000000000000000000

0000000000000000000000FFFF00000000000000000000000000000000000

0000000000000000000000000000000000000000000000000000000000000

000000000000000000000000000000$

5. Import the signal units to the INET.

Format of Import file:

Each signal unit is composed of signal unit data, the signal unit file name, and the

signal unit data mask.

Signal unit data is preceded and terminated by a pound (#) sign and is represented

in unspaced, uppercase hexadecimal characters.

The signal unit file name immediately follows the signal unit data.

Signal unit mask data follows the signal unit file name. The mask data is preceded

and terminated by a dollar sign ($) and I represented in unspaced, uppercase

hexadecimal characters, Enabled bits mask the signal unit data bits (hexadecimal

F masks an entire nibble; hexadecimal 0 leaves the nibble unmasked)

Multiple messages can be contained within a single ASCII file. The ASCII signal

unit file must be terminated by a carat ^.

Import File For CMS_1 signal unit with cell number field masked:

#00003083555555510B000101AA000002020705435555550E040543510B000E00

4800465705050100010064173C030024910CCA006300020E6A0103000006084E

062190205000105E07803103020500020D0505ACDC00013502038001110B1B03

02208200030151C11800#CMS_1

$000000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000FFFF0000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000000000000000000000

000000000000000000000$

^

F6 / Import ASCII SIGNAL UNITS / SS7 / CHINA / A:CMS_1.TXT

34


35/46

Import File CMS_1.TXT

CMS_l After IMPORT:

octet003 Service information

octet..........................................

....0011 Service indicator. SCCP Signalling connection control part

..00.... Spare............. 0

10...... Network indicator. N National network

octet004 Routing

label......................................................

........ DPC: Zone-Net-SP.. 085-085-085

........ OPC: Zone-Net-SP.. 000-011-081

octet010 Signalling link

selection..........................................

....0001 SLS............... 1

0000.... spare............. 0

octet011 Message

type.......................................................

00000001 Headers H1/H0..... CR Connection Request

octet012 Source local

re0erence.............................................

........ Reference number.. aa 00 00

octet015 Protocolclass.....................................................

....0010 Protocol class.... 2

0000.... spare............. 0

octet016

Pointers...........................................................

00000010 Pointer-> Called # 2

00000111 Pointer-> Optional 7

octet018 Called Party Address

parameter.....................................

00000101 Parameter length.. 5

.......1 SPC indicator..... Address contains Signalling Point Code

......1. SSN indicator..... Address contains a Subsystem Number

35


36/46

..0000.. Global Title...... No global title included

.1...... Routing basis..... RoutingBasedOnLabelDPC&SSNinCalledNumbr

0....... Reserved, Natl use 0

........ DPC: Zone-Net-SP.. 085-085-085

11111110 Subsystem name.... CDG IOS

octet024 SCCP Optional

parameters...........................................

00000100 Parameter name.... Calling party address

00000101 Parameter length.. 5

octet026 Address

indicator..................................................

.......1 SPC indicator..... 1

......1. SSN indicator..... 1

..0000.. Global title...... No global title included

.1...... Routing indicator. 1

0....... Reserved, nat'l... 0

octet027

Address............................................................

........ SPC: Zone-Net-SP.. 000-011-081

11111110 Subsystem name.... CDG IOS

octet031 SCCP Optional

parameter............................................

00001111 Parameter name.... Data

octet032 Data

parameter.....................................................

01001000 Parameter length.. 7200000000 Transparency...... BSMAP

01000110 Length............ 70

octet035 Message Type

BSMAP.................................................

01010111 Message Type...... CompleteLayer3Information

octet036 CDG-IOS

Parameter..................................................

00000101 Parameter name.... Cell Identifier


00000001 Cell IdentDscrmntr LocatnAreaCode(LAC)&CellId(CI)usedToIdCell........ LocationAreaCode.. 1

00000000 CellNumber........ 6

....0100 Sector Number..... Sector 4/Sector U

0110.... CellNumber........ 6

octet043 IS-CI40

Parameter..................................................

00010111 Parameter Ident... Layer 3 Information


....0011 Protocol Discrmntr CC CallProcessing&CallRelatedSSMessages

0000.... Reserved.......... 0

....0000 Reserved.......... 0

.000.... Reserved.......... 0

36


37/46


38/46

........ Digits............ 60120902050001

octet071 CDG-IOS

Parameter..................................................

01011110 Parameter Ident... Called Party BCD Number


....0000 NumberingPlanIdent unknown

.000.... Type of Number.... Unknown

1....... Extension Bit..... Last Octet

........ NmbrDigits/EndMark 13302050002 ST

octet080 CDG-IOS

Parameter..................................................





0000.... Digit 1........... 0

........ ESN: ManCode+Srial# ac dc 00 01

octet087 CDG-IOS

Parameter..................................................

00110101 Parameter Ident... Slot Cycle Index

.....010 Slot Cycle Index.. 2

00000... Spare............. 0

octet089 CDG-IOS

Parameter..................................................

00000011 Parameter Ident... Service Option

10000000 Service Type...... Proprietary service options00000001 Service Type...... QUALCOMM Incorporated

octet092 CDG-IOS

Parameter..................................................

00010001 Parameter Ident... IS-2000 Mobile Capabilities

00001011 MobilityCap Len... 11

.......1 QPCH Supported.... Supported

......1. Enhanc. RCC0G Supp. Supported

.....0.. OTD Supported..... Not Supported

....1... 0CH Supported..... Supported

...1.... DCCH Supported.... Supported000..... Reserved.......... 0

00000011 0CH Info Length... 3

.....010 0CH Info fillBits. 2

....0... GeoLocationIncluded Not Included

.000.... GeoLocationType... No mobile assisted geo-location capabilities

0....... Reserved.......... 0

........ 0CH Info Content.. 20 82 00

00000011 DCCH Info Length.. 3

.....001 DCCH Info fillBits 1

00000... Reserved.......... 0

........ DCCH In0o Content. 51 c1 18

octet105 CDG-IOS

38


39/46

Parameter..................................................

00000000 Parameter Name.... End o0 Optional Parameters

Checksum CRC 16............ 0000000000000000 hex=0000

39


40/46

MLT test script development Process flow

Initial development:

List

Determine Test Cases

to be executed.Test Case

Identify all signal units needed

to accommodate the testSignal Unit

List

Create the signal units in

ASCII/HEX format. Catalog all

signal units in spread sheets.Signal Unit

File

Identify the database entries

required. Catalog each

database file/properties.

Database

Catalo

Determine the test

environment of the system to

be tested. Record the results

in the spreadsheet.

Test

Environment

Record

Edit ASCII/HEX files based on

test environment.Import files to

INET.

Build database files based on

test environment.

Script Creation.

Script Verification/Debug.

40


41/46

Subsequent test cycles:

Determine the test

environment of the system to

be tested. Record the results

in the spreadsheet.

Test

Environment

Record

Edit ASCII/HEX files based on

test environment.Import files to

INET.

Build database files based on

test environment.

Script Execution.

41


42/46

9.0 Data Capture and Logging

This section pertains to logging and creating useful information from the Primary Capture buffer. The

INET Spectra Analyzer allows the tester to capture data to the Primary Capture buffer each time the F2 Run

function is used to restart a test.

9.1 Message FiltersThere are several methods to set up SS7 Filter options to display only necessary call flow messages for

troubleshooting call completion problems. One method is pre-capture filtering in which the data buffer log

filters out any unnecessary messages to save memory space. The SS7 Filter options are accessible through

the F1 Configure Option menu.

The configuration for pre-capture filtering includes Real Time Call Trace and protocol specific Message

Filter. Real Time Call Trace pertains to a single call trace triggered by user-defined phone numbers or

mobile subscriber ID number. Message Filter allows the Spectra to filter only messages to Pass or Block

based on protocol settings under Level 2, User Part, Point Codes, Phone Numbers, Subsystem Number,

Circuit ID, or User Event. The Message Filter is configured on a LINKSET basis. Use the Arrow Keys to

toggle the filters ON/OFF. F1 / Configure/ Filters/ Message Filters

42


43/46

9.2 Data Files vs Print Files

Once the filter configuration has been saved and applied, the real-time buffer data can be logged into raw

data form or printable files. Each type has its own rewards.

Data files allow the tester to rebuild or review the call flow scripts at a later time. Data files are acquired by

using F9 Function Key to stop the logging and saving (S Key) the data log using conventional naming.

These files are stored under the directory: C:\Spectra\Signalog and retrieved through the F8 DOS menu.

Print files are readable by any text editor applications. The files can be saved into two display types: 1)

HEX or 2) IOS-decoded message format by toggling the T Key while in the expanded message screen. To

save call flow selections to a file, use the K Key to mark all the messages necessary or Z Key to zap all

message in the buffer and save using the F5 Function Key menu options. These files are stored under the

directory: C:\Spectra\Printlog, retrievable from the F8 DOS menu, and viewable through the F5 menu

options. F5

10.0 Network Emulation Capabilities

With limited lab equipments, emulation of intelligent networking (IN) equipments such as HLR or SMC

becomes necessary at times for Message-Level testing. PSTN emulation for landline phone networking

may also be required if actual connection to the PABX or similar devices are not available. The INET

Spectra provides emulation of these network devices provided that the tester mode modules required are

available on the box. Scripting and message creations are detailed in section 7 and 8.

43


44/46

10.1 SS7 Tester Mode

SS7 Tester mode is a new module distributed with Spectra version 4.02.xx or higher. This mode allows

single script multi-protocol capability. The single scripting logic allows ISDN User Part (ISUP),

Telephone User Part (TUP), and Transaction Capabilities Application Part (TCAP) messages to be

incorporated into one script. That is the user can select signal units from different database directories. An

additional enhancement is a jump function for timeout triggers. If a trigger times out, the script can specifyto jump to the next line if the break option is selected. See screen capture below. SS7 Tester mode also

allows up to 500 test script lines instead of the usual 50 lines limitation for other tester modes. F1/ MODE/

SS7/ SS7 TESTER

44


45/46

10.2 ISUP/TUP (PSTN) Emulation

ISUP or TUP PSTN emulation can be executed using two different approaches. One of which is to use SS7

Tester mode to combine TCAP, ISUP, and TUP Tester into one script. The other approach is to use CVR

ISUP or TUP Tester mode using a second Spectra box. If a second Spectra box is not available, the script

can combine ISUP or TUP and TCAP Tester by copying ISUP or TUP signaling units with extension

*.SCC into the TCAP signaling unit database directory using the F8 DOS copy function. F1/ SS7/ CVRTESTER/ TUP TESTER

10.3

11.1

IS-41 (HLR/SMSC) EmulationIS-41 HLR or SMSC emulation is scripted using the same method as TUP PSTN emulation by copying or

creating signaling units with the extension *.SCC into the TCAP signaling unit database directory. The

main concern is to make sure the header information and IS-41 layer messages correlate to the MSC

supported protocol. The best result would be to capture real time messages monitored on the IS-41

signaling link and manipulate the messages accordingly for Message-Level testing.

11.0 Debugging Hints

The tester may find many situations that cannot be resolved directly through the decoding of captured call

flow logs. In such case, the use of the SS7 Tools and System-Level data logs become an important aid indeveloping and validating interface problems.

Use of SS7 Tools (F8)

The use of SS7 Tools allows the tester to manipulate links without creating an entire script. The SS7 Tools

menu is accessible through the F8 Function Key. The SS7 Tools apply to the following Test Modes:

STP/SCP Emulation

TUP/ISUP/TCAP Tester

ISUP/TUP/TCAP/GSM Generator

Note that the function list varies among each mode. An example of a function list is shown from the

captured screen below. In addition to the SS7 Tools for link management and signaling unit (SU) transmit

45


46/46

control, the F8 Tools Options offer the capability to reset hardware devices including Input/Output (I/O)

interfaces and Basic Rate Interface (BRI) pods. F8/ SS7 TOOLS/ TRANSMIT SU OUT SPECIFIED

LINK

11.2 System-Level Test Data Logs

Another valuable aid to have is the System-Level data logs taken during validations of previous releases for

the IOS-A1 interface. These captured data buffer serves well in verifying regression message flows as well

as debugging new changes in message parameters. Text files of the system level message call flows and

message layouts from the data logs are suitable, but the preferred method is to save the data in the raw DATfiles. This method will allow the tester to extract the actual message for immediate message generation in

the defined scripts or SS7 Tools selections.

INET Spectra MLT Training Overview v0[1].4

Documents

Transcript of INET Spectra MLT Training Overview v0[1].4