NS Tab Parameters

When you configure a UMTS or SGSN node test case for Gb interface testing by selecting the GPRS protocol stack, the Gb tab is displayed. With it, you can define the SUT, the BSS link rates, and the transport protocol attributes for the RAN side of the Gb interface.

Network Services Settings

The combination of VCI and NSEI uniquely identifies a BSSGP virtual connection between the RAN and the SGSN. The following describes the Network Services settings parameters:

Starting VCI Starting NS Entity ID Number of Source IP Endpoints Increment Source Port Number of Destination Endpoints Increment Dest Port	Maximum Alive Retries Alive Timer Interval Test Timer Interval Increment Source NSE Port Increment Destination NSE Port
Dynamic Configuration
Dynamic Configuration Use Pre-configure SGSN SUT	SNS-Size Message Retries SNS-CONFIG Message Retries Retry Interval (S)	SNS Add Delete Procedure Toggle Time (s) IP Address
SNS Dynamic Messaging
Source Weights	Destination Weights
Apply Parameter Values from Test Data File

Related Measurements

Starting VCI

The BSSGP Virtual Connection Identifier associated with each BSS NSE.

Range: 1 — 65536

Default: 1

Tcl Parameters: NsStartingVci_1

Starting NS Entity ID

The Network Services Entity Identity identifies the group of VCIs that are associated with a BSS.

Range: 1 — 65536

Default: 1

Number of Source IP Endpoints

The number of endpoints supported by each BSS NSE. The value you select here determines the number of IP Endpoints/rows displayed in the Source Weight table.

Range: 1 — 20

Default: 1

Number of Destination IP Endpoints

The number of endpoints supported by each BSS NSE.

Range: 1 — 20

Default: 1

Increment Source Port

Selecting Increment Source Port increments the starting/source UDP port for multiple NSEs configured, that is, increments only the IP Ports for each NSE defined (BSS Node) and the IP address will remain the same for all the NSEs in a BSS Node/SGSN Node.

NOTE: Increment Source Port is not available when you select Dynamic Configuration.

Increment Source NSE Port

Selecting the Increment Source NSE Port checkbox ensures that the IP address remains the same for all NSEs. Clearing the Increment Source NSE Port checkbox increments the IP address for each NSE created (in a BSS Node).

NOTE: Increment Source NSE Port is available only when you select Increment Source Port.

The example below describes how the source port/NSE port selection work either to increase only the ports and or the IP addresses for each NSE created.

In UMTS test case

Increment Source Port	Increment NSE Source Port	Result
Selected	Selected	Number of IPs = Num BSS (BSS Node)
Selected	Cleared	Number of IPs = Num BSS * Num NSE (BSS Node)
Cleared	Cleared	Number of IPs = Num BSS * Num NSE * Number of Source IP Endpoints

SGSN Node test case

Increment Dest Port	Increment NSE Dest Port	Result
Selected	Selected	Number of IPs = Num SGSN (SGSN Node)
Selected	Cleared	Number of IPs = Num SGSN * Num NSE (SGSN Node)
Cleared	Cleared	No. IPs = Num BSS * NumNSE * Number of Source IP Endpoints

Increment Dest Port

Selecting the Increment Dest Port checkbox increments the destination/end UDP port for multiple NSEs configured, that is, increments only the destination IP Ports for each NSE defined (BSS Node) and the IP address will remain the same for all the NSEs in a BSS Node/SGSN Node.

NOTE: Increment Dest Port is not available when you select Dynamic Configuration.

Increment Dest NSE Port

Selecting the Increment Dest NSE Port checkbox ensures that the IP address remains the same for all NSEs. Clearing the Increment Dest NSE Port checkbox increments the IP address for each NSE created (in a BSS Node/SGSN Node).

NOTE: Increment Dest NSE Port is available only when you select Increment Dest Port.

IP Test Procedure Settings

An NSE can test for connectivity with the SGSN by sending an Alive message on any VC that terminates an SGSN endpoint. When the Test Timer expires, the NSE sends the Alive message and then starts the Alive Timer. If an Alive Acknowledgement is received, the Alive Timer is stopped and the Test Timer is reset for the next interval. If an acknowledgement is not received before the Alive Timer expires and retries are not exhausted, another Alive message is sent and the Alive Timer is reset.

Test Timer Interval

The number of seconds between test procedure cycles.

Range: 1 — 60

Default: 10

Alive Timer Interval

The number of seconds that the test will wait for an Alive Acknowledgement.

Range: 1 — 60

Default: 3

Maximum Alive Retries

The maximum number of times an Alive message can be re-transmitted.

Range: 1 — 10

Default: 10

Related Measurements

^ Back to Top

Dynamic Configuration

Use the Dynamic Configuration checkbox to enable configuring endpoints dynamically using Sub Network Service (SNS) and then enter the retry intervals for the sequence of SNS messages exchanged.

Tcl Parameter: NsDynamicConfigEn

Use pre-configured SGSN SUT

Available only in MME Nodal and UMTS test cases.

Select to force force all BSS Nodes to send all SNS messages to the same pre-configured SGSN SUT.

Clear selection to increment the SUT address based on the Number of Destination IPs.

NOTE: You may use Test Data File to change the Destination IP, if required.

SNS-SIZE Message Retries

The number of times an SNS-SIZE message can be re-transmitted.

Tcl Parameter: NsSizeMsgRetries_1

SNS-CONFIG Message Retries

The number of times an SNS-CONFIG message can be re-transmitted.

Tcl Parameter: NsConfigMsgRetries_1

Retry Interval (S)

The number of seconds that the test will wait for an SNS message acknowledgement.

Tcl Parameter: NsSnsRetryInterval_1

SNS Add Delete Procedure

Select the SNS Add and Delete Procedure checkbox to change the parameters initially configured as part of dynamic configuration in SGSN Node test case.

Tcl Parameter: NsSnsAddDeleteEn

Value: True/False

Toggle Time (s) — The number of seconds the test will wait before toggling between add and delete SNS procedure. Valid values are between 15 to 30 seconds.
IP Address — The End Point IP Address that is being deleted by the delete procedure. It will be included in the SNS-DELETE PDU sent to the BSS.

Tcl Parameter:

NsSnsToggleTimer

NsSnsIpAddr

^ Back to Top

SNS Dynamic Messaging

In SGSN test case, use SNS Dynamic Messaging to send Add/Delete/Config SNS messages to pre-configured IP endpoint (s) and the destination NSE ID (s).

SNS Dynamic Messaging

Available only when you select Dynamic Configuration. Select to add/delete/config IP endpoints and destination NSE IDs. Tcl Parameter: NsSnsMsgEn_1

Initiate SNS-CONFIG Message

Available when SNS Dynamic Messaging is enabled. Select to send an SNS-CONFIG Message.

Default: checked (true)

Tcl Parameter: NsInitiateSnsConfig_1

Add Delete

Click Add. A row is inserted with a unique index ID and allows you to enter NSE ID, endpoint IP Address, Port, and Command.

Click Delete to remove the highlighted row and the table is redrawn with new index values for the rows.

Tcl Parameter: NsSnsNseListLength

Range: 0 - 20 (Table Rows)

NOTE: The number of rows in the table is saved in the Tcl Parameter NsSnsNseListLength.

Index

Index is automatically appended to each row inserted by clicking Add.

Tcl Parameter: NsSnsNseIpAdd_1

NSE ID

Enter the the destination NSE ID used in the SNS Command.

Range: 1 - 65535

Default: Blank

Tcl Parameter: NsSnsNseId_1

IP Address and Port

Enter the endpoint IPv4 Address and Port used in the SNS Command.

Range: 1 - 65535

Default: Blank

Tcl Parameter:

NsSnsNseIpAdd_1

NsSnsNseIpPort_1

Port Default: Blank

Port Range: 1 - 65535

Command

Select the SNS Command to send.

Tcl Parameter: NsSnsNseCmd_1

^ Back to Top

Source Weights

The Source Weights array/table is available only when the Data Configuration checkbox is selected. The source weights table allows you to assign different source Signaling and Data weight weights for the source endpoints. The number of rows displayed depends on the value you selected from the Number of Source Endpoints dropdown list.

Range: 0 – 255

Class: Array: one weight item per IP#

Tcl Parameters:

NsVcSrcSignalWeight_1

NsVcSrcDataWeight_1

Destination Weights

The Destination Weights array/table is available only when Data Configuration checkbox is not selected. The destination weights table allows you to assign different Signaling and Data weight weights for the Destination endpoints. The number of rows displayed depends on the value you selected from the Number of Destination Endpoints dropdown list.

Range: 0 – 255

Class: Array: one weight item per IP#

Tcl Parameters:

NsVcDestSignalWeight_1

NsVcDestDataWeight_1

^ Back to Top

Apply Parameter Values from Test Data Files

Tcl Parameter: NsCfgFileEn_1

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.

^ Back to Top