GTP Tab
The GTP tab is used to define the information in GPRS requests sent from the SGSN node to the GGSN SUT.
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.
When you select the Inter-SGSN or Session Loading With Mobility test activity, a Handoff GTP tab is added to the test case. You can select a different GTP version for the handoff node, modify the RAI attributes, or configure a different QOS profile. With GTP V1, you can also set a different RAT type.
- In the UMTS test case, the GTP tab is added to the (Gn interface) test case when GGSN Node Emulation is enabled.
|
General Settings |
|
|
|
|
|
|
|
User Location Information |
|
|
|
|
|
|
|
|
|
|
|
Quality of Service (GPRS)
|
|
|
|
|
|
|
Related Measurements
Measurements collected for GTP related processing are reported on the GTP report tab.
General Settings
|
Use the drop-down list to select the GTP version to be used by the SGSN nodes: version 1 or version 0. The applicable parameters are enabled depending on your selection.
Options: 0 or 1 Default: 1 Tcl Parameter: GtpVersion
|
|||||||||||||||||||||||||
| Starting IMSI |
The starting International Mobile Subscriber Identifier. This value is incremented for each mobile subscriber. A combination of this value and the NSAPI uniquely identifies a PDP context. In the SGW Nodal testing, when the Test Activity Is Inter Technology Mobility, and UMTS is Release 7, The Starting IMSI is not available on the Gn>GTP tab. Range: 5 — 15 digits Default: 50502410121507 Tcl Parameter:
Related Measurements |
||||||||||||||||||||||||
|
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 context associated with a given mobile subscriber. Range: 5 — 15 (0 — 4 are reserved for GGSN error handling) Default: 5 Tcl Parameter: StartingNsapi
|
|||||||||||||||||||||||||
|
The mobile subscriber's ISDN nature of address type. Range: 0 — 7 Default: 1 Tcl Parameter: MsIsdnNoa
|
|||||||||||||||||||||||||
|
The mobile subscriber's ISDN numbering plan indicator. Range: 0 — 15 Default: 1 Tcl Parameter: MsIsdnNpi
|
|||||||||||||||||||||||||
|
The starting ISDN directory number for the mobile subscriber. This value is incremented for each mobile subscriber. In the SGW Nodal testing, when the Test Activity Is Inter Technology Mobility, and UMTS is Release 7, The Starting MS ISDN Number is not available on the Gn>GTP tab. Range: Maximum 16 digits Default: 17962480141 Tcl Parameter: MsIsdn |
|||||||||||||||||||||||||
|
Use this parameter to send PDP Context Update Request when creating secondary contexts. The Secondary PDP Context Activation Procedure indicates that RAN Procedures are ready and that the SGSN is ready to receive payload from the GGSN on the new PDP Context. Tcl Parameter: SendUpdateWhenCreateSecondaryEn Values: True (1) False (0) Default: False (0) |
|||||||||||||||||||||||||
|
Select to enable Auto Reconnect. From the drop down menu select from the two options. If "Keep Session Rate" is selected (default), the reattach/reconnect attempts do not increase the session rate. If "Increase session Rate" is enabled, then the reattach/reconnect attempts will increase the number of session rate. For example, if session rate is configured at 1,000 session/sec and there are 10 unexpected detaches/disconnects, then the next session will be increased to 1,010 session/sec. 1,00 sessions as defined and 10 sessions for the detached/disconnected sessions. Options: Keep Session Rate (default) or Increase Session Rate Tcl Parameter: GtpAutoReconnectEn Tcl Parameter: GtpAutoReconnectType |
|||||||||||||||||||||||||
|
You can customize Landslide generated messages and or compose your proprietary messages to perform negative testing with invalid values or malformed messages or to add proprietary information. The Custom Message checkbox is available in GGSN Nodal Test Case for GTPv0/GTPv1 with appropriate License. Select the Custom Messages Checkbox, which makes available the New and Open buttons.
Tcl Parameter: Gtp1CustomMsgEn Tcl Parameter: Gtp1CustomMsg |
|||||||||||||||||||||||||
|
The following parameters define the GTP ports used by the SUT:
Range: N/A Default: 2123
Range: N/A Default: 2152 Tcl Parameter:
|
|||||||||||||||||||||||||
|
In the GGSN Nodal test case, you can add an enhanced response to a GGSN-initiated PDP Context Request. Select one of the following responses from the Update Response drop down list:
Tcl Parameter: GtpUpdateResponse |
|||||||||||||||||||||||||
| 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).
Range: 0 -- 65535 Default: 0 Tcl Parameter: EchoTime |
||||||||||||||||||||||||
|
The APN selection mode to be used. If you enter 0 or 1, Starting Access Point Name defines the MS-provided APN. The GGSN may use Selection Mode when deciding whether to accept or reject the requested PDP context activation. If the requested APN requires subscription, the GGSN may reject requests with a Selection Mode of 1 or 2. Range:
Default: 0 Tcl Parameter: SelectionMode Related Measurements |
|||||||||||||||||||||||||
| Restart Counter |
The restart counter that is sent from the SGSN to the GGSN. When a SGSN restarts, it increments its restart counter, notifying the peer node that it has restarted, and that any existing contexts should be dropped without signaling. You can change this value while the test is running, simulating an SGSN that rebooted while servicing PDP contexts. All contexts are dropped and then re-connected using the new restart value. Range: 0 — 255 Default: 1 Tcl Parameter: RestartCnt |
||||||||||||||||||||||||
|
Select to ignore a restart indication received from a GGSN SUT. When the box is cleared (default), the SGSN node will delete active PDP contexts if the GGSN restarts. When the box is checked, PDP contexts will be maintained regardless of the GGSN's restart counter value. Tcl Parameter: GtpIgnorePeerRestart |
|||||||||||||||||||||||||
| N3 - Command Request Attempts |
The maximum number of attempts made by GTP to send a request message without receiving an associated response message from the Srv GW. Enter 1 to disable retries. Range: 1— 65535 Default: 5 Tcl Parameter: N3Attempts Tcl Variable: N3Attempts |
||||||||||||||||||||||||
| T3 - Wait Time for GGSN Response |
The number of seconds to wait for a command request response. The T3 timer starts when a signaling request message (for which a response has been defined) is sent. Range: 1— 65535 Default: 20 Tcl Variable: T3Time See Retries |
GTP Version 1
| Starting GTP-C Tunnel Endpoint |
Indicates the Starting Tunnel Endpoint ID (TEID) that specifies which tunnel a particular T-PDU belongs to. This parameter is incremented for each GTP tunnel. Range: 1 — 4294967295 Default: 1 Tcl Parameter:
|
|||||
| Starting GTP-U Tunnel Endpoint |
Indicates the starting GTP-U tunnel endpoint ID. This parameter is incremented for each GTP tunnel. The transport bearer is identified by the GTP-U TEID and the IP address (source TEID, destination TEID, source IP address, destination IP address). Range: 1 — 4294967295 Default: 1000 Tcl Parameter:
|
|||||
|
The type of charging the PDP context is liable for, selected from one of 16 charging profiles that may be configured on the GSN. Range: 0 - 16 Default: 16 (indicates that it is not used) Tcl Parameter: ChargeCharacteristics |
||||||
| Include APN Restriction |
Use to include the optional APN Restriction information element in the context requests sent by the SGSN nodes. It is used to determine whether the MN is allowed to establish PDP contexts to other APNs. When sent from the SGSN, it reports the highest level restriction type among all of the MN's active PDP contexts (Maximum APN Restriction Value). When an APN Restriction is received from the GGSN, it indicates the restriction level imposed on the PDP contexts associated with the APN. APN Restriction defines the Maximum APN Restriction used in all SGSN requests, regardless of the values received from the GGSN. Example: Tcl Parameter:
Range: 0 — 255
Default: 0 Related Measurements |
|||||
| Include RAT Type |
Use the checkbox to include Radio Access Technology Type information element, which identifies the RAT type used by the SGSN. When enabled, enter the RAT type in the field provided. Range: 0 — 255
Default: 1 Tcl Parameter:
|
|||||
| Include IMEISV |
Use the checkbox to include the International Mobile Equipment Identity (and Software Version) information element. Range: N/A Default: 1234567812345678 Tcl Parameter:
|
|||||
| Starting IMEI |
The International Mobile Equipment Identity that will be used for the first MS. This value will be incremented for each MS. Range: 14 digits Default: 50502410121507 Tcl Parameter: GtpImei |
|||||
| Support Software Version |
Available in SGW and PGW Nodal test cases only (S11/S5/GTPv2 tab). Select and enter a value that will be included in the Create Session Request message (setting IMEISV to MEI (Mobile Equipment Identity) IE). Type: True/False Default: False Tcl Parameter: GtpImeiSwVersion |
|||||
| Teardown Indicator |
Use the checkbox to include a teardown indicator in the Delete PDP Context message. When it is included, the GGSN should tear down all PDP contexts sharing the same IP address with the context referenced in the delete request. Otherwise, the GGSN should only delete the context requested. Tcl Parameter: TeardownIndicator |
|||||
| PDP Context Trace Update Generation |
Use the checkbox to enable trace updates from the SGSN nodes. When this option is enabled and the PDP context is a secondary context, the trace information elements are included in the Update PDP Context messages sent to the GGSN. Tcl Parameter: EmulateTraceUpdate |
|||||
| GGSN Trace Activated |
Use the checkbox to enable tracing. When enabled, you can define the following attributes:
Range: 0 — 65535 Default: 0
Range: 0 — 65535 Default: 0
Range: N/A Default: 0
Range: N/A Default: 0 Tcl Parameter:
|
|||||
| Include MS Time Zone |
Use the Include MS Time Zone to enables calculation of the MN's local time. Time Zone specifies the difference, in quarter-hour increments, between the local time and GMT. Bit 3 defines the algebraic sign of the difference (0 = positive, 1 = negative). The upper 4 bits (4 through 7) and the lower 3 (0 through 2) bits define the time difference. Range: 0 — 255 Default: 0 Daylight Saving Time defines the adjustment for daylight savings time, if any, in the current time zone. Range: 0 — 255
Default: 0 |
|||||
| Upgrade Qos Supported | In GGSN Nodal test case, select to include support of QoS Upgrade to be shown in Create PDP Context request and Update PDP Context request message. Tcl Parameter: GtpQosUpgradeSupportedEn | |||||
| No QoS Negotiation | Select to indicate no QoS negotiation shown in Update PDP Context request message. Tcl Parameter: GtpNoQosNegotiateEn |
|
NOTES:
|
|
Use the checkbox 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. |
||
|
Use the drop-down list to select the number of primary PDP contexts to be established for each mobile subscriber. Options: 1— 11 Default: 1 Tcl Parameter: PrimPdpContextsPerMs
|
||
|
Options: 0 — 10 Default: 0 Tcl Parameter: SecPdpContextsPerMs
|
| Idle Entry Time |
The Idle Entry Time is the length of time to wait before the UE enter idle state. Also indicates the length of time to wait before releasing resources from the Network. Range: 0 — 65535 Default: 0 Tcl Parameters: PppIdleEntryTime |
| Delay DL Packet Notiff Req (50ms) |
The number of milliseconds to delay notifying a Downlink (DL) packet between the SGW and UE. Range: 0 — 255 Default: 1 Tcl Parameter: PppDelayDlPacketNotiffReq |
| 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: ChargGateAddrE
|
| 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 429,496,295 Default: 1 Tcl Parameter: ChargId |
| Include Common Flags |
Use the checkbox 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: IncCommonFlags |
| Charging Characteristics |
The type of charging the PDP context is liable for, selected from one of 16 charging profiles that may be configured on the GSN. Range: 0 - 16 Default: 16 (indicates that it is not used) Tcl Parameter: ChargeCharacteristics
|
| Restart Counter |
The restart counter that is sent from the SGSN to the GGSN. When a SGSN restarts, it increments its restart counter, notifying the peer node that it has restarted, and that any existing contexts should be dropped without signaling. You can change this value while the test is running, simulating an SGSN that rebooted while servicing PDP contexts. All contexts are dropped and then re-connected using the new restart value. Range: 0 — 255 Default: 1 Tcl Parameter: RestartCnt |
| Radio Access Type |
Select the RADIO Access Type to from the dropdown list to indicate connectivity between the UE (user equipment) and the core network. Tcl Parameter: PppRadioAccess
|
| Use GSN Signalling Address |
Use the checkbox 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. |
User Location Information - GPRS Testing
In GGSN Nodal test case, select Include User Location Information to enable and parameters which identify the Cell Global Identification or Service Area Identity for the MS's current location.
Tcl Parameter: IncUli
Include Routing Area Identity Code
In SGSN Node and GGSN Nodal testing, you can configure the test to assign the same LAC, RAC and Cell ID to every MS or define a range of values that will be evenly distributed among the MSs. These values are used in both the BSSGP and GMM layers. 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 values, the value is incremented for each MS.
|
NOTE: Ensure that the LAC range defined on the Mobility Gb tab does not overlap the range on the Gb tab. Handoffs must be performed between different LAC/RAC combinations. |
See RAI Attributes for the RAI parameters.
APN Assignments
Use the APN pane to define the APN values assigned to PDP/bearer contexts. You can define one APN for all contexts, a different APN for every context, or a set of APNs that are distributed among all contexts. With the retry capability, you can also configure alternate APNs that will be used if a context cannot be established using the preferred APN. You can manually define different APN values, generate incremented values during test execution, or use a combination of both methods.
During GPRS testing, In the APN Primary Context Assignments pane, you can choose to use the same APN configuration for all contexts or define an APN configuration by primary context by selecting Summary or Individual radio buttons. When you select Individual, an APN sub-tab is displayed for each primary context. For example, the APNs defined in the P0 sub-tab are used with every MN's first primary context, the APNs defined in the P1 sub-tab are used with every MN's second primary context, and so on. The Number of individual primary contexts sub-tabs depend on the Number of Primary PDP Contexts value selected on the GGSN Nodal Test Configuration tab.
For example, 50 APN values will be generated and used with the first primary PDP context and any associated secondary contexts of each MN. Three of those values are manually defined and the remaining values will be generated with an incrementing format. Since Round Robin is enabled, the first MN's context will be assigned isp.com (APN 0), the second MN's context will be assigned company.com (APN 1), the third will be assigned network.net (APN 2), and then the test will begin assigning the generated incrementing values (my10apn, my11apn, and so on). After all 50 APN values have been used, the test will cycle back to isp.com for the fifty-first MN. Retries is also enabled, allowing a maximum of four attempts to activate each primary context (one initial attempt plus three retries) and each attempt will use the next APN in the list. If the second MN's context activation fails, for example, company.com will be replaced with network.net for the next attempt. When you define a Summary configuration, the round-robin order is by context rather than by MN. Using this same example, the first MN's three primary contexts are assigned and then the second MN's contexts. The second MN's first primary context would be assigned my10apn in this case.
| Total APNs |
The maximum number of APN values that will be generated for the contexts, including both incrementing values and manually-defined values. Range: Variable (depends on your MS licensed capacity) Default: 1 Tcl Parameter: SmApnTotalApns_0
|
|
| Starting Auto-Incrementable APN |
The APN to be used for the first primary bearer context. If your test uses more than one bearer per MS, you can use the Auto-Increment feature to provision a unique name for each context. Range: N/A Default: ssenoauth146 Tcl Parameter: SmApn_0 |
|
| Retries |
The number of times the PDP context will attempt to be activated if the first attempt did not succeed. When you enable Retries, each retry attempt will use the next APN value in the list if you have defined multiple APN values. Range: Variable (limited by the maximum number of PDP contexts) Default: 0 (retries are disabled) Tcl Parameter: SmApnRetries_0
Related Measurements |
|
| Manually Specify First |
Use the drop-down list to select the number of APN values that you will manually define. The appropriate number of value fields (APN 0 — APN 10) are enabled based on your selection. The values that you define in these fields will always be used first when you select Round Robin mode. The number of APN value fields depends on the number of Default Bearers per Session you selected on the Mobile Subscriber pane of the Test Configuration tab. To manually define the 11th APN, use the "Starting Auto-Incrementable APN" field. Tcl Parameter: SmApnNumSpecifiedApns_0
|
|
| Round Robin |
Use the checkbox to enable round-robin APN assignment. When you define multiple APN values, the first value in the list is assigned to the first context, the second value is assigned to the second context, and so on. Manually-defined values are always selected first and when that list is exhausted, incrementing values are used. After the test has cycled through the total number of APNs, the next context is assigned the first APN value in the list. A context will use the same APN through the life of the test as long as the context can be successfully established using that APN. In a Session Loading test, for example, a new APN is not obtained every time the context is re-established.
Tcl Parameter: SmApnRoundRobin_0 |
Quality of Service
During GPRS testing, the Quality of Service pane allows you to specify the QoS parameters for a primary PDP context. The GGSN/SGSN needs the QoS information for IP packet Uplink and Downlink. The GGSN/SGSG SUT ensures that the granted QoS does not exceed the Authorized QoS per IP flow. The authorized bit rate/sec is defined separately for Uplink and Downlink packet flow.
Summary/Individual
You can define one QOS for all Primary PDP contexts or a different QOS for each Primary PDP context.
- Select the Summary radio button to use the same QOS configuration for all bearers in the Summary tab
- Select the Individual radio button to define individual QOS for each bearer per subscriber by selecting the radio buttons.
When you select Individual, a Primary Context e'g; P0) sub-tab is displayed for each Primary Context per subscriber (selected on the Mobile Subscriber pane on the Test Configuration tab). For example, if Primary Context is 3, the Primary Context QoS tabs displayed are Default, P0, P1, and P2.
R97 Only
In GPRS testing, select the R97 Only checkbox to send only 4-byte R97 QoS attributes (2G specification).
Tcl Parameter: QosR97En
| NOTE: When R97 Only checkbox is not selected, R99/3G QoS attributes are sent. |
Apply Parameter Values from Test Data Files
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.
|
||
|
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).
|
||
|
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.
|
||
|
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 |
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. |
View TDF Actions/Options Menu)
Tcl Parameter: GtpGgsnCfgFileEn
|
NOTES:
|