GTP Tab
Click here to see this page in full context

Landslide Performance Test System – Release 24.3 September 2024

GTP Tab

When a test case emulates a GGSN, the following parameters define the Gn interface between the node and an SGSN SUT. In the GGSN Node test case, the parameters also define the Gn interface between the node and an SGSN SUT.

In the UMTS test case, the GTP tab is added to the (Gn interface) test case when GGSN Node Emulation is enabled.

In the MME Nodal test case, the GTP tab is added to the Gn to SGSN interface when you select Emulate Srv GW to PDN GW and also added to the Gn to MME interface when you select Gn Interface to MME on the Test Configuration tab.

In SGSN Node test case, the GTP tab is added when the Gn Interface checkbox is enabled (on the SGSN Node Emulator Configuration tab).

GGSN Testing

 

MME Testing

 

 
Location and Routing Information
GMM  

UMTS Testing

Apply Parameter Values from Test Data File  

Related Measurements

Measurements collected for Gn related processing are reported on the GTP report tab.

SUT Ports

SUT Control Port

Range: N/A

Default: 2123

SUT User Port

Range: N/A

Default: 2152

Tcl Parameter:

MmeSutCtlAddrPort

MmeSutUsrAddrPort

 

N3 - Command Request Attempts

See Retries

Tcl Parameter: MmeN3Attempts

T3 - Wait Time for GGSN Response

See Retries

Tcl Parameter: MmeT3Attempts

Do Not Update MME Control Plane IP Address

Indicates whether the MME-Gn address is updated based on the GSN address received in the Forward Relocation Request message.

Select to make sure that the incoming GTP Gn signalling traffic is sent (from Landslide) to the MME using the sender IP and not the GSN IP address in the Forward  Relocation  Request message.

Type: True/False

Default: False

Tcl Parameter: MmeNoCtrlPlaneIpUpdateEn

 

Periodic Echo Message Time

The amount of time, in minutes, between the periodic echo messages that are sent to the GGSN/SGW to detect path failures. Enter 0 to disable the echo messages.

For GTPv2, Periodic Echo Message Time is used on the responder side (in both MME Nodal and SGW Nodal test cases).

NOTE: The Periodic Echo Message Time is not available on the Gn to SGSN >GTP tab and Gn to MME > GTP tab in MME Nodal test case.

 

^ Back to Top

GTP Version

Use the drop-down list to select the GTP version to be used by the SGSN to MME GTP nodes: version 1 or version 0. The applicable parameters are enabled depending on your selection.

Options: 0 or 1

Default: 1

Tcl Parameter: SgsnGtpVersion

 
Use GSN Signalling Address

Select to ensure that the GGSN emulator sends GTPC messages to the SGSN control plane address specified in the Create PDP Context Request message rather than the IP address of the underlying network service.
Starting NSAPI

The starting Network Service Access Point Identifier. A combination of this value and the IMSI uniquely identifies a PDP context. This value increments for each primary and secondary PDP context associated with a given mobile subscriber.

Range: 5 — 15 (0 — 4 are reserved for GGSN error handling)

Default: 5

Tcl Parameter: SgsnStartingNsapi
Charging Gateway Address Sent to SGSN

 

Informs the SGSN of the IPv4 or IPv6 address of the charging gateway that collects CDRs for the PDP contexts. In the GGSN Node test case, you can include this information by checking the box and entering the address in the field provided. In the UMTS test case, the address is always sent unless you enter 0.0.0.0.

Tcl Parameter: SgsnChargGateAddrEn
Starting PDP Context Charging ID

The Charging ID is used by the SGSN to identify all CDRs produced by a PDP context. The GGSN informs the SGSN of the ID to use for each context. The starting value is incremented for every PDP context serviced by the GGSN node.

Range: 0 — 4294967295

Default: 1

Tcl Parameter: SgsnChargId
Periodic Echo Message Time

The amount of time, in minutes, between the periodic echo messages that are sent to the SGSN to detect path failures. Enter 0 to disable the echo messages.

Range: 0 — 65,535

Default: 0

Tcl Parameter: EchoTime

 
Starting GTPC Tunnel Endpoint

The starting GTPC tunnel endpoint ID. This parameter is incremented for each GTP tunnel.

Range: 1 — 4294967295

Default: 1000000

Tcl Parameter:

GtpcTunnelEndptId

SgsnGtpcTunnelEndptId

MmeGtpcTunnelEndptId

 
Starting GTPU Tunnel Endpoint

The starting GTPU tunnel endpoint ID. This parameter is incremented for each GTP tunnel.

Range: 1 — 4294967295

Default: 2000000

Tcl Parameter:

GtpuTunnelEndptId

SgsnGtpuTunnelEndptId

MmeGtpuTunnelEndptId

 
Starting GTPU II Tunnel Endpoint

The starting GTPU tunnel endpoint ID. This parameter is incremented for each GTP tunnel.

Range: 1 — 4294967295

Default: 2000000

Tcl Parameter: MmeGtpu2TunnelEndptId

 
Teardown Indicator

Use the checkbox to include a Teardown Indicator in the Delete PDP Context message.

Tcl Parameter: SgsnTeardownIndicator

 
Include Common Flags

Select to include the Common Flags IE in messages sent to the SGSN. A value of 1 prohibits the SGSN from compressing user data payloads when requested to do so by the MN.

Range: 0 — 255

Default: 1

Tcl Parameter:

SgsnIncCommonFlags SgsnCommonFlags

 
Include APN Restriction

Use the checkbox to include the optional APN Restriction information element messages sent by the GGSN node. It indicates the restriction level imposed on the PDP contexts associated with an APN. Define the Maximum APN Restriction used for all APNs in the field provided. Example:Example:If the Create PDP Context request contains a Maximum APN Restriction value of 3, the GGSN may only allow the requested context to be established if it has an APN Restriction of 1.

Range: 0 — 255

  • 0 — No existing contexts or restrictions, all contexts are allowed to be created.

  • 1 — Public-1 (e.g. WAP, MMS): contexts with restriction values 1-3 are allowed to be created.

  • 2 — Public-2 (e.g. Internet, PSPDN): contexts with restriction values 1-2 are allowed to be created.

  • 3 — Private-1 (Corporate): contexts with restriction value 1 are allowed to be created.

  • 4 — Private-2 (Corporate): no contexts are allowed to be created.

Default: 0

Tcl Parameter:

SgsnIncApnRestriction SgsnApnRestriction

Related Measurements
Persistent IMSI/IMEI

In PGW Node test case, select Persistent IMSI/IMEI to make sure that the IMSI is remembered/stored when the PGW session is torn down.  Selecting Persistent IMSI/IMEI ensures that when the PGW session comes back up, sessions with matching IMSI are assigned/allocated the same IP address.

Type: Tue/False

Default: False

Tcl Parameter: Gtp2PersistentImsiEn

Have the sessions on the GGSN Node and PGW Node remember their IMSI's when the session is torn down.  When it comes back up, the session with the matching IMSI will be assigned and the same IP address will be allocated.
Emulate Session Reject

Select to enable Emulate Session Reject. Enter percentage of rejected items. For example, if there are 1000 total sessions and the Reject Percentage is set to 10, the actual number of rejected sessions may be greater than 100.

Tcl Parameter: EmulateSessionRejectEn
Reject Percentage

Enter Reject Percentage.

Range: 1 to 100

Default : 10

Tcl Parameter: RejectPercentage
Error Indication Timer

When the Direct Tunnel Feature is enabled, this parameter sets the Error Indication Timer value in number of seconds.

Range: 0 — 4294967295

Default: 0

Tcl Parameter: DirectTunnelErrorTime
Apply Parameter Values from Test Data Files

See Applying Test Data FileApplying Test Data File

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.

NOTE: Gn file settings include GTP PDP Address, which overrides Starting PDP Contexts IP Addr Pool on the General tab of the test case.

^ Back to Top

Location and Routing Information

You can configure the test to assign the same Location Area Code (LAC) and Routing Area Code(RAC) to every MS or define a range of values that will be evenly distributed among the MSs. These values are used in the Gn to MME interface.

Enter the same value in the Start and End field to use that value for every MS. Enter the lowest value in the Start field and the highest value in the End field to define a range of values. When you define a range of LAC values, RAC values, or both, the value is incremented for each MN. Example:Example:

Assuming the following settings:

Number of MSs: 5

LAC range: 0— 2

RAC range: 0— 1

The MSs will be assigned LAC/RAC combinations in a round-robin manner:

MS 1: 0/0

MS 2: 1/1

MS 3: 2/0

MS 4: 0/1

MS 5: 1/0

NOTE: Handoffs must be performed between different LAC/RAC combinations.

 

  • Location Area Code Range

Range: 0 — 65535

Default: 0

Tcl Parameter: RanapLac

  • Routing Area Code Range

Range: 0 — 255

Default: 0

Tcl Parameter: RanapRac

The following parameters define the remaining location and routing information elements for the RANAP layer.

  • Mobile Network Code

See Mobile Network Code

Range: 00 — 999 (2-3 digits; leading zeros are retained)

Default: 00

Tcl Parameter: RanapMnc

  • Mobile Country Code

See Mobile Country Code

Range: 000 — 999 (leading zeros are retained)

Default: 000

Tcl Parameter: RanapMcc

  • Service Area Code

Range: 0 — 65535

Default: 0

Tcl Parameter: RanapSac

 

Security Mode

Select the ciphering and integrity protection algorithms to be used in the Security Mode Command messages.

Option: GSM Keys and Quintuplets, UMTS Keys and Quintuplets, Used Cipher, UMTS Keys and Quintuplets

Tcl Parameter: MmeSecurityMode

 

^ Back to Top

© 2024 Spirent Communications Inc. All Rights Reserved.