M3UA Tab

The IuPS tab is used to define the radio and transport layers of the Iu-PS interface between the RNC and a 3G-SGSN SUT. The settings for the appropriate protocols are displayed based on your Protocol selection.

The IuCS tab is used to define the radio and transport layers of the Iu-CS interface between the RNC and MSC. The settings for the appropriate protocols are displayed based on your Protocol selection.

NOTE:

When Iu-PS and Iu-CS are both enabled (In MME Nodal and MME Node ) when Handoff Protocol = UMTS (IuCS & IuPS over IP) the Tcl variables will begin with luCs for the lu-Cs interface. The Iu-PS interface will use the regular M3ua Tcl variables.
When Iu-PS and Iu-CS are both enabled (In HNB GW Nodal ) when 3G Macro RNC Emulation is enabled, Tcl variables will begin with luCs for the lu-Cs interface and IuPs for the Iu-PS interface.

In HSS Node testing Gr interface defines mapping and transport layers between the SGSN and HSS/HLR Node.

In UMTS tesing, when you select the Mobility or Session Loading With Mobility test activity, a Mobility IuPS tab is added to the test case to define the interface for the handoff RNC.

UMTS parameters

Parameters:

M3UA

Point Code Format
Originating Point Code
Destination Point Code
Network Indicator
ASP ID

Client
Retries
Retry Time
Starting Routing Context
Fixed Peer Routing Context
Network Appearance
Increment

Apply Parameter Values from Test Data File

Related Measurements

Measurements collected for Gr interface in HSS Node and IuPS radio and transport related processing are reported on the M3UA, MTP-3B, RANAP, and SCCP report tabs.

Point Code Format

The point code is an identifier for a node that can be represented in different formats. Use the radio buttons to select the point code format required by the SUT. Existing values in the Originating Point Code and Destination Point Code fields are converted when you change the format.

When you change/select different formats, the current value is converted to decimal value and then converted to the new format.

Options:

3-8-3 — Code is split into 3-bit, 8-bit, and 3-bit fields
4-3-4-3 — Code is split into 4-bit, 3-bit, 4-bit, and 3-bit fields
8-8-8 — Code is split into three 8-bit fields, that is, 24-bit value (M3UA only — IuPS over IP). The 8-8-8 option is only be available when you select Use Ansi Encoding on the SCCP tab.
Decimal — Code is represented by a decimal value (16383 for 14-bit value, 16777215 for 24-bit value).

Originating Point Code

The point code for an RNC, displayed in the Point Code Format that you chose. If you are using multiple RNCs, this value is incremented for each RNC.

Range: 0 — 16383 (decimal)

Default: 0

Tcl Parameter:

MtpOriPc_1

MtpOriPc

Destination Point Code

The point code for the SGSN SUT, displayed in the Point Code Format that you chose.

Range: 0 — 16383 (decimal)

Default: 0

Tcl Parameter:

MtpDesPc_1

MtpDesPc

Network Indicator

Use the drop-down list to select the network value for the Sub-Service field.

Options: National (2), International (0), or National Backup (1)

Default: International

Tcl Parameter:

MtpNetworkInd_1

MtpNetworkInd

ASP ID

Available in UMTS/SGSN Node test cases under Iu-PS M3UA. If enabled, enter a 32-bit unsigned integer for the ASP Identifier.

Tcl Parameter:

M3uaAspIdEn_1

M3uaAspId_1

Client (M3UA)

Use the checkbox to designate the role for the RNC nodes. When the box is checked (default), the nodes will initiate the SCTP associations. Clear the checkbox if the SUT will initiate the associations.

Tcl Parameter:

M3uaClient_1

M3uaClient

Number of Retries (M3UA)

The number of times a message will be re-transmitted when the Retry Time expires.

Range: 1 — 10

Default: 5

Tcl Parameter:

M3uaNumRetries_1

M3uaNumRetries

Retry Time (M3UA)

The number of milliseconds that the test will wait for a response before re-transmitting a message.

Range: 100 — 30000

Default: 2000

Tcl Parameter:

M3uaRetryTime_1

M3uaRetryTime

Starting Routing Context (M3UA)

The index value associated with an association's Routing Key. The value that you enter will be incremented for each SCTP association.

Range: 1 — 4294967295

Default: 1

Tcl Parameter:

M3uaStartRouteContext_1

M3uaStartRouteContext

Fixed Peer Routing Context (M3UA)

Indicates a fixed index value attributed to an association's routing key.

A zero value indicates no Fixed Peer Routing Context.

A > 0 indicates that the RNC will only accept ASP-Active messages from the peer (SGSN node) with the same Routing Context as provisioned.

NOTE: The Fixed Peer Routing Context value can be changed with the Configuration file using the peer_rc parameter.

Note that .

Range: 1 — 4294967295

Default: 0

Tcl Parameter:

M3uaStartPeerRouteContext_1

M3uaStartRouteContext_2

Network Appearance (M3UA)

The combination of the Network Appearance and the Signalling Point Code uniquely identifies an SS7 node.

The value you enter will be incremented for each SCTP association if you select the Increment checkbox. If you do not select the Increment checkbox, the value you enter will be used for all SCTP association.

Range: 1 — 4294967295

Default: 1

Tcl Parameter:

M3uaStartNetAppearance_1

M3uaStartNetAppearance

Increment

Use the check box to have the Network Appearance increment for each SCTP association. If you do not select the Increment checkbox, the value you enter will be used for all SCTP association.

Values: True/False

Default: True

Tcl Parameter:

M3uaNetAppIncEn_1

M3uaNetAppIncEn

^ Back to Top

Apply Parameter Values from Test Data Files

See About Applying Parameter ValuesAbout Applying Parameter Values.

See Test Data Files for further explanation and sample files. If a sample is not found for the specific TDF, you can obtain a sample file from your Technical Support representative. You may also use the following options to select an existing TDF or create/edit TDF-CSV files (TDF-CSV Editor).

For most TDF Parameters used for Applying Parameters, each row in the file is the overridden value for a different “Session”, aka a different UE. But some TDFs are done in other dimensions, like Bearers, eNodeBs, Subscribers (2 per UE sometimes) or even Hosts, etc. Tooltips on the TDF Parameter:

Note that the “ID” is a unique ID. Please Provide the ID when reporting issues with a TDF. For TDFs that do not apply / override Parameters, but instead are just their own configuration or data or media files you won’t see TDF ID row details.

TIP: When including large files, please be aware of memory limitations, since the TDF Editor shares memory with the Client.

NOTE: The available TDF options vary. on the L3-7 | IPSec tab > IKE with RSA Settings you may only select the Certificate TDF from TAS (these are non-CSV TDFs).

In addition, where applicable, any rules for defining TDFs are included in specific Test Cases. (For example, In MME Node test case, see MME Node - Provisioning TDF.)

From the DMF Window, press Shift+Alt+A to display the Save DMF as Tcl window. Click the Save to File button to save as Tcl file. See additional details on Using the Tcl API.

Select/Create a new TDF-CSV

Allows you to create a new TDF by entering a file name that doesn’t already exist or select an existing file by entering a file name that already exists.

Click to open the Select Existing or Create window.

Navigate to the relevant library/folder,
Enter the name of the file:
If the file name already exists, the file is selected and applied in the test case.
If the file name does not exist, a message displays that says you are creating a new TDF and the embedded TDF-CSV will be launched.
- Click Yes to launch the TDF-CSV Editor and create/save the new TDF-CSV.
- Click No to select a different file

NOTE: If you do not have permission to save in the selected library, an error displays when you try to create a new file.

TIP: You may also navigate to the relevant library/folder and select file, and click OK.

Upload a New TDF to TAS

Click to import a new TDF file from your local folder and select in the test Case (instead of having to go to TDF Admin).

Navigate to the file on your local folder and select.
Then navigate to the location (library) where you want to save it on the TAS. You may rename the file, if required.

View Edit Selected TDF in TDF-CSV Editor

Available only when you have selected a TDF on TAS. Click to open the selected file in TDF-CSV Editor (in place, that is, within the Test Case).

Edit the file and save. You may also click Save As to save the edited TDF-CSV to a different library and also rename the file, if required.

NOTE: You may also select a TDF from a library to which you do not have write permissions, edit the file as required, and save (Save As) only to a different library with the same file name or a different name.

The only options available are Save As and Cancel.

Open Selected TDF in Standalone TDF-CSV Editor

Available only when you have selected a TDF on TAS. Select to retrieve the CSV file and open it in the stand alone TDF-CSV Editor.

Generate Stub TDF-CSV

TIP: Available only when a CSV specification has been defined for in the Test Case for the TDF widget ( View TDF Actions/Options Menu)

Opens an example context specific test data parametersexample context specific test data parameters, which you may save as a .CSV file or open in the TDF-CSV Editor.

Launch Standalone TDF-CSV Editor

Click to open a blank TDF-CSV Editor.

The Launch Standalone TDF-CSV editor options handles very large TDFs that may use too much Client memory if opened within the Test Case/in the embedded editor. You may set the standalone TDF-CSV Editor memory high to edit large TDFs.

Tcl Parameter:

M3uaCfgFileEn_1

M3uaCfgFileEn

m3uaBssCfgFileVer2.csv

^ Back to Top