GTPv2 Tab

Use the drop-down list to select the GTPv2 version to be used by the MME and PGW nodes. The applicable parameters are enabled depending on your selection.

In MME Nodal test Case, when you select Sv Interface on the Test Configuration tab, 10.6.0 is the only GTPv2 version available.

In MME Nodal test case, when you select S10 Interface to MME, GTPv2 version 16.5.0 is available.

Options: 8.0.0, 8.1.1, 8.2.0, 8.3.0, 8.4.0, 8.5.0, 8.6.0, 9.4.0, 9.5.0, 9.6.0, 9.7.0, 9.9.0, 10.6.0, 10.8.0, 11.4.0, 12.6.0, 13.5.0, 13.6.0, 15.2.0, 15.6.0, 15.9.0, 16.5.0

Default: 15.9.0

Tcl Parameter: Gtp2Version

Tcl Parameter: SvGtp2Version

Tcl Parameter: N26Gtp2Version

The starting International Mobile Subscriber Identifier. This value is incremented for each mobile subscriber.

Range: 5 — 15 digits

Default: 505024101215074

Tcl Parameter: Gtp2Imsi

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:

Gtp2SwVersionEn

Gtp2SwVersion

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: Gtp2Imei

Select IMEI Check Digit for the IMEI to be set to 15 digits and the 15th digit to be the check-digit. It will be a non-zero value, per spec 23.003. Otherwise IMEI is set to 14 digits.

Tcl Parameter: Gtp2ImeiCdEn

The MS ISDN directory number for the mobile subscriber ID included as part of the Subscriber ID. This value is incremented for each mobile subscriber.

Range: Maximum 15 digits

Default: 17962480141

Tcl Parameter: Gtp2MsIsdn

Select the RADIO Access Type to from the dropdown list to indicate connectivity between the UE (user equipment) and the core network.

Options: UTRAN (1); GERAN (2); WLAN (3); GAN (4); HSPA Evolution (5); EUTRAN (6); Virtual (7); EUTRAN-NB-IoT (8)

Default: EUTRAN

Tcl Parameter: Gtp2RadioAccessType

Proprietary Extensions

See Proprietary Extension Settings.

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:

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).

For Command Mode / Sequencer test cases in SGW Nodal - the following restriction has been added :

The value for "Starting GTP-U Tunnel Endpoint ID" should satisfy either the equation or inequations as shown below:

  "Starting GTP-U Tunnel Endpoint ID" == "Starting Target GTP-U TEID" (4000000 by default, and could not be configurable in this case)

or

  "Starting GTP-U Tunnel Endpoint ID" >= "Starting Target GTP-U TEID" (4000000) + "Number of Subscribers" * "Default Bearers per Session" * (1 + "Dedicated Bearers per Default")

or

"Starting GTP-U Tunnel Endpoint ID" <= "Starting Target GTP-U TEID" (4000000)  - "Number of Subscribers" * "Default Bearers per Session" * (1 + "Dedicated Bearers per Default")

If the restriction is not met, an error pop-up :

Range: 1 — 4294967295

Default: 1000

Tcl Parameter:

Indirect Forwarding

Indirect forwarding is available when UMTS Version is 7 or 8 and Test Activity is Inter-Technology Mobility, Intra-MME, or Inter-MME.

Tcl Parameter: Gtp2IndirectForwardings

When Test Activity is Intra-MME or Inter-MME:

• Indirect Forwarding is used when the source eNodeB senses an error on the x2 interface with the Target eNodeB. When this feature is enabled, data will be forwarded to the SGW, which then sends data to the Target eNodeB, in the case of no SGW relocation (not enabled on the Test Configuration tab).
• In addition, if SGW relocation is enabled (on the Test Configuration tab), data will be forwarded to the Source SGW->Target SGW->Target eNodeB. When the x2 interface between the eNodeB is up and running (which is the normal case), data will be forwarded directly to the Target eNodeB from the Source eNodeB.

When Test Activity is Inter-Technology Mobility and handoff is Inter RAT:

Indirect Forwarding uses the Gn interface to make an inter-RAT handover.

In addition, Indirect Forwarding allows the source MME to send a Create Indirect Data Forwarding Tunnel Request message to the Serving GW, which returns a Create Indirect Data Forwarding Tunnel Response message to the source MME. If the Serving GW doesn't support data forwarding, an appropriate cause value is be returned.

Select Support Piggyback Messaging to indicate that additional information (multiple messages) is exchanged with between entities as part of the attach procedure (for example, UE, eNodeB, and MME) during SGW Nodal and PGW Nodal testing (UE and Serving Gateway).

Tcl Parameter:

Value: True (1), False (0)

Default: False

Support Piggyback Messaging is available during the following circumstances:

In SGW Nodal case, use Forward Uplink Data In ECM-Idle in conjunction with Activation Delay (s) to delay the Modify Bearer Request following the first uplink packet (UE initiated traffic) sent.

Tcl Parameter: Gtp2FwdUplinkDataEcmIdle

Select Support Multiple Dedicated Bearers per Message to allow/support (send) multiple bearer context (Create Bearer Request/Response) in a single Network initiated dedicated bearer request.  

During SGW Nodal and PGW Node testing, Support Multiple Dedicated Bearers per Message is available if the number of Dedicated Bearers is > 0 (on the Test Configuration tab>Mobile Subscriber pane), UE Initiates Dedicated Bearers is not selected (on the Test Configuration tab), and Support Piggyback Messaging is not selected (on the GTPv2 tab).  

In addition, during SGW Nodal testing, Support Multiple Dedicated Bearers per Message is available only when you select PGW Node Emulation.

Type: True/False

Default: False

Tcl Parameter: Gtp2MultDedsPerMsgEn

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: Gtp2N3Attempts

Tcl Variable: SvGtp2N3Attempts

Tcl Variable: N26Gtp2N3Attempts

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: Gtp2T3Time

Tcl Variable: SvGtp2T3Time

Tcl Variable: N26Gtp2T3Time

See Retries

The amount of time, in seconds, 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:  

Available in SGW Node and in MME Nodal when "SGW/PGW Node Emulation" is selected. - DDN timer to trigger paging. Time in milliseconds.

For SGW Nodal, this timer controls when/if an automatic UE initiated Service request follows an S1 Release MMM (ECM_IDLE) state. SGW Nodal will send an MBReq (or MABReq) dependent on the configuration to the SGW.

Range: 0 -- 4294967295

Default: 0 (a value of '0' disables the automatic functionality.)  

Tcl Parameter:  

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: Gtp2IdleEntryTime

The amount of time, in seconds, between the UE Registration Query messages sent on the S3 interface to report remote UE activity.

Range: 0 — 65535

Default: 0 (Enter 0 to disable the UE Registration Query messages)

Tcl Parameters: Gtp2UeRegQueryTime

In PGW Nodal test case, the restart counter is sent from the Srv GW to the PDN GW and and in SGW Nodal test case, from MME to SGW (to simulate MME Restart) . When a MME/SGW restarts, it increments its restart counter, notifying the peer node that it has restarted, and that any existing contexts should be dropped without signaling.

In SGW and PGW Nodal test cases, You can change this value while the test is running, simulating a MME/SGW that rebooted while servicing Bearer contexts. All contexts are dropped and then re-connected using the new restart value.

Range: 0 — 255

Default: 1

Tcl Parameter: Gtp2RestartCnt

Indicates the delay timer between the Downlink Data Notification (Page) (DDN rcv) and Modify Bearer Requests (MBReq/Rsp-data) transactions.

Set to 0 for no delay between the DDN rcv and MBReq/Resp data transactions.

Enter a value > 0 to delay the DDN rcv and MBReq/Resp data transactions by the number of seconds entered.

Range: 0 - 65535

Default: 0

Tcl Parameter: Gtp2ModBearerDlDataDelay

Available in PGW and SGW Nodal test case. The Charging Characteristics value is included in the Create Session Request messages (Software Version and selection mode IE values (APN Assigments > Selection Mode)).

Enter a hex value in Charging Characteristic.

Range: Up to a maximum of 16-Bit Hex String

Default: 0x0

Tcl Parameter: Gtp2ChargingChars

Select to ignore the restart counter.

Tcl Parameter: Gtp2IgnoreRestartCtrEn

Select to include the sequence number in the GTP-U header. Available in PGW Node, MME node/MME Nodal, SGW Node/SHW Nodal.

Not available when Fireball is enabled.

Tcl Parameter: Gtp2GtpuIncludeSeqEn

Enter Router Advertisement Delay in seconds.

Range: 1 to 5

Default : 1

Tcl Parameter: Gtp2RouterAdDelay

Available when Handoff type = TAU/RAU. Enable to send modify bearer request.

Tcl Parameter: Gtp2SendModBearerOnHandoverEn

Available in PGW Nodal and SGW Nodal test cases in support of NetLoc.

If enabled in S4 Interface, must "Include Cell Global Identifier" and "Include Service Area Identifier" in User Location Information pane.

If enabled in S11 Interface, must "Include E-UTRAN Cell Global Identifier" in User Location Information pane.

If enabled in S4/S5/S11 Interface, must "Include Cell Global Identifier" , "Include Service Area Identifier"  and "Include E-UTRAN Cell Global Identifier" in User Location Information pane.

Tcl Parameter: Gtp2UliDbCmdCbRspEn

Available in SGW Nodal and Node test cases.

Select to indicate Support Modify Access Bearer Request Response (MABR).

• In SGW Node test case, the Echo Request/Response message includes IE Type=152 with the Modify Access Bearers Request bit set to 1.
• When the SGW Nodal receives a Downlink Data Notification (following an Echo exchange) it will respond with the Modify Access Bearers Request.
• If the SGW Nodal receives a Downlink Data Notification prior to an Echo exchange it will respond with the Modify Bearer Request.

Tcl Parameter: Gtp2SupportMabrEn

Available in SGW Nodal Test Case on S11 Tab when Test Activity is Inter Technology Mobility and Handoff Protocol = eHRPD or Test Activity is Command Mode/Sequencer and "HSGW Node Emulation" is enabled. Per 3GPP TS 29.274 V9.2.0.

Select to indicate when performing a hand down from LTE to eHRPD, the MME should initiate Release access bearer towards SGW indicating the bearers for LTE are being torn town.

Default = False

Tcl Parameter: Gtp2RelAccBearerReqEhrpdHoEn

UE 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 and the lower 3 bits define the time difference, see example below.

Example: The GUI accepts a range from 0 to 255, thus if you capture a value of 249 the binary values is 1111 1001. Since bit 3 (in bold) is 1, it is indicating a negative value. The upper 4 bits are 1111, which is 15 in decimal, the lower three bits are 001 which is 1 in decimal, thus the time difference value will be : 1*10 + 15 = 25 in quarter-hour increments, so the time difference is -6 hours and 15 minutes. The lower three bits must be multiplied by 10 to come up with the correct value.

If you capture a value of 90 on the GUI, you will get the same time difference because 90 in binary is 0101 1010. The lower three bits is 010 which is 2 in decimal and the upper four bits are 0101 which is 5 in decimal. Thus, the time difference value is 2*10 + 5 = 25 in quarter-hour increments, so the time difference is -6 hours and 15 minutes. The lower three bits must be multiplied by 10 to come up with the correct value.

Range: 0-255, Default 0

Tcl Parameter: Gtp2UeTimeZone

Daylight Savings Time: Defines the adjustment for daylight savings time, if any, in the current time zone.

Range: 0-3, Default 0

• 0 — none

• 1 — +1 hour adjustment

• 2 — +2 hour adjustment

• 3 — reserved

Tcl Parameter: Gtp2UeDaySaveTime

Select Reject Dedicated Bearer to enter Reject EBI.

See table below that explains the EBI assignment of Default/Dedicated Bearers:

Range: 6 to 15

Default: 6

Tcl Parameter: Gtp2RejectDedEn

Tcl Parameter: Gtp2RejectEbi

The amount of time, in seconds, between the Remote UE Report messages sent on the SGW to report remote UE activity.

Range: 0 — 65535

Default: 0 (Enter 0 to disable the Remote UE messages)

Tcl Parameters: Gtp2RemoteUeReportTime

Available on PGW Node test case. The PGW Node sends a Create Bearer Request and waits for a Response, once the Response is validated the PGW waits this time (Delete Delay Time) before sending the Delete Bearer Request.

Range: 0 — 1000 (in milliseconds)

Default: 1000 

Tcl Parameters: Gtp2DeleteDelayTime

Select to include Bearer level QoS in the Create Session response. Available in PGW Node test case (S2a/S2b/S5/S8).

Tcl Parameters: Gtp2BearerQosInCsrspEn

5GS Interworking Indication

5GS Interworking without N26 Indication

Select for the "Create Session Request" sent by the SGW to properly carry "Indication" with "5GS Interworking Indication" activated.

Available in PGW Nodal test case, (MME Node, SGW Nodal / Node, Wifi Offload Gateway Node when Version >= 15.9.0).

When 5GS Interworking Indication is enabled, you can select 5GS Interworking without N26Indication in MME Node, SGW Nodal / Node when Version >= 15.9.0.

Reference : Spec 3GPP TS 29.274 version 15.9.0 section 7.2.1, 7.2.2, 7.3.1, 7.3.1-2, 7.3.6

Tcl Parameters: Gtp25gsItwkIndEn

Tcl Parameters: Gtp25gsnn26En

Available on SGW Node test case when Sxa Interface to UP is enabled.

Select for SGW Node to forward Modify Bearer Request to PGW on UE Service Request. Reference : Spec 23.401, 5.3.4.1 UE triggered Service Request, step 9.

Tcl Parameter: Gtp2FwdMbrOnUeSvcReqEn

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.

Select Custom Messages, which makes available the New and Open buttons.

• New: Click New to display the Message Editor window. See Message Editor for details of entering a new message.

• Open: Click Open to display the Select Message Editor window. Select the library in which the message exists, select the message you wish to edit and then click the Edit button to display the Message Editor Window. See Message Editor for details of editing existing messages.

Tcl Parameter: Gtp2CustomMsgEn

Tcl Parameter: Gtp2CustomMsg

Available on SGW Nodal S11/5 tab. Select to support “Presence Reporting Area action” IE in Modify Bearer Request.

When enabled, enter the Segment Index and Segment Value.

Segment Index - Range : 1 to 6, default : 6

Segment Value - Range : 0 to 65535, default : 1067

Tcl Parameter: Gtp2Ipv6GtpuAddrCheckEn

Tcl Parameter: Gtp2Ipv6GtpuAddrSegIndex

Tcl Parameter: Gtp2Ipv6GtpuAddrSegValue

Enable to turn on Change Notification Reporting. A change notification reporting message is triggered every time a handover is complete.

Tcl Parameter: Gtp2ChangeNotificationEn

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.

Indicates the Starting Target 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: 3000000

Tcl Parameter:

Indicates the starting Target 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: 4000000

Tcl Parameter:

In SGW Nodal test case, Resource Release Time indicates the MME timer for handovers, that is, time after which the resources are released and is available  for all mobility testing (Test Activity on Test Configuration Tab is Session Loading with Mobility, Inter-MME Mobility, Intra-MME Mobility, Inter Technology Mobility, Command Mode, Sequencer).

Also available in MME Node test case to add the capability to adjust the handover release timer. The default value in the MME Node test case is 5 seconds.

Range: 0 - 65535

Default: 1 second

Tcl Parameter: Gtp2ResourceReleaseTime

During SGW Nodal testing, Activation Delay applies only when Idle Entry Time is > 0. The Activation Delay timer indicates the length of time to wait before responding to the Downlink Data Notification (Page) from the Network (for SGW).

Range: 0 to 65535

Default: 0

Tcl Parameter: Gtp2ActivationDelay

Postpone Update Bearer Response Caused by PRA

Delay Times (ms)

During SGW Nodal testing, select to Postpone Update Bearer Response Caused by PRA. When enabled, enter the Delay Time in milliseconds. When Delay time expires, the Update Bearer Response will be sent.

Range: 10 to 1000

Default : 10

Tcl Parameter: Gtp2PostponeUbrByPra

Tcl Parameter: Gtp2UbrDelayTime

Available in PGW and SGW Node test cases.

Select to permit UBR (Update Bearer Response) Delay. Use this parameter checkbox to test the Postponement of the Update Bearer Response Caused by PRA (see above).

Tcl Parameter: Gtp2PermitUbrDelay

Delay DL Packet Notif Req (50ms)

The number of milliseconds to delay notifying a Downlink (DL) packet  between the SGW and UE. Also available in MME Node.

Range: 0 — 255

Default: 1

Tcl Parameter: Gtp2DelayDlPacketNotifReq

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

STN-SR: The Session Transfer Number for SRVCC (STN-SR) is transferred via GTP tunnels and the sending entity copies the value part of the STN-SR into the Value field of the STN-SR IE.

Enter MSISDN. Available on I2 Interface on MME Node Test case.

The MSISDN and STN-SR will be sent in the I2 INVITE Msg as P-Asserted-Identity and Request-URI, respectively. Note,the first two digits of MSISDN are "Nature of Address" and "Number Plan Indicator" which will not be reflected in the SIP INVITE Msf.

Tcl Parameter: SvGtp2MsIsdn

Indicates the value of the Nature of Address included in the STN-SR IE.

Option: 0 - 7

Default: 1

Tcl Parameter: SvPppStnSrNoa

Tcl Parameter: SvGtp2StnSrNoa

Indicates the Numbering Plan Indicator (NANPI) included in the STN-SR IE.

Option: 0 - 15

Default: 1

Tcl Parameter: SvPppStnSrNpi

Tcl Parameter: SvGtp2StnSrNpi

The actual STN-SR (digits of an address encoded) included in the STN-SR IE.

Default: 17962480141

Tcl Parameter: SvPppStnSr

Tcl Parameter: SvGtp2StnSr

Indicates IMS Centralized Service. Select to indicate request of ICS support.

Tcl Parameter: SvPppIcsEn

Tcl Parameter: SvGtp2IcsEn

Indicates Session Transfer Indicator. Select to indicate that IMS session transfer has been invoked.

Tcl Parameter: SvPppStiEn

Tcl Parameter: SvGtp2StiEn

• Starting S5 GTP-C TIED: Available only when you select Separate S5 Interface on the Emulator Configuration tab. Indicates the Starting S5 GTP-C Tunnel Endpoint ID (TEID) (S5 Control plane tunnel set up).

• Starting S5 GTP-U TIED: Available only when you select Separate S5 Interface on the Emulator Configuration tab. Indicates the Starting S5 GTP-U Tunnel Endpoint ID (TEID) (S5 User plane tunnel set up).

• Starting Forwarding GTP-U TIED: Indicates the mobility GTP-U TIED used for forwarding relocating messages

Starting S2b GTP-C TIED

Indicates the S2b GTP-C 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: 5000000

Tcl Parameter: Gtp2S2bGtpcTunnelEndptId

Indicates the Seb 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: 6000000

Tcl Parameter:Gtp2S2bGtpuTunnelEndptId

Include ULI IE

Use the checkbox to include the ULI information element, which identifies the Cell Global Identification or Service Area Identity for the UE's current location.

Value: True/False

Tcl Parameter: S2bGtp2IncModUli

Select to include the location of the Service Area for a MS reported by the UE in SGW Nodal testing.  

Value: True/False  

Tcl Parameter: S2bGtp2IncModServNetw  

Include APN AMBE IE

Select to include the APN-AMBR information element for Bearer Modifications initiated by LTE, eHRPD, or ePDG.  

Value: True/False  

Tcl Parameter: S2bGtp2IncModApnAmbr  

Include RAT IE

Select the Radio Access Type from the dropdown list.

Value: True/False (Virtual : 7)

Tcl Parameters:

Include QOS IE

Select to enable the Bearer Quality of Service pane.

Tcl Parameter: S2bGtp2IncModQos

Include Time Zone IE

Select to include the UE Time Zone information element, which enables calculation of the UE's local time.

Value: True/False

Tcl Parameter: S2bGtp2IncModTimeZone

• 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 define the time difference.

Range: 0-255, Default 0

Tcl Parameter: S2bGtp2UeTimeZone

• Daylight Savings Time: Defines the adjustment for daylight savings time, if any, in the current time zone.

Range: 0-255, Default 0

• 0 — none

• 1 — +1 hour adjustment

• 2 — +2 hour adjustment

• 3 — reserved

Tcl Parameter: S2bGtp2UeDaySaveTime

Select to add TDF file on the S2b tab. S2b is available for Command Mode/Sequencer with ePDG Node Emulation selected.

GTP version 8.1 or later are supported.

TDF ID = 205. The columns will be manually updated.

• See also, 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.

Default columns:
     "Access Point Name"
     "Aggregate Max Bit Rate Downlink"
     "Aggregate Max Bit Rate Uplink"
     "QOS Max Bit Rate Downlink"
     "QOS Max Bit Rate Uplink"
     "QOS Guaranteed Bit Rate Downlink"
     "QOS Guaranteed Bit Rate Uplink"
     "QOS ARP" - QCI ARP IE in TDF includes three items: PVI, PCI and PL (see 3GPP 29.274, Section 8.86)
     "QOS QCI"

Example tdf : tdfS2b_ims.csv

Tcl Parameter: S2bGtp2CfgFileEn

Tcl Parameter: S2bGtp2CfgFile

Allows you to include a value for Cell Identity.

Tcl Parameters:

Allows you to include a value for Service Area Identity.

Tcl Parameters:

Allows you to include a value for Routing Area Identity.

Tcl Parameters:

 Allows you to include a value for Tracking Area Identity. If eNodeB Based Allocation is selected, then Tracking Area Code is disabled. Enter Number of Tracking Areas and Starting Tracking Area code instead.

Tcl Parameters:

Allows you to include a value for E-UTRAN Cell Global Identity. If eNodeB Based Allocation is selected, then E-UTRAN Cell Identity disabled. Enter Number of eNodeB's per Tracking Area, Starting eNodeB ID, Number of Cells per eNodeB and Starting Cell ID.

Tcl Parameters:

Mobile Country Code

Defines the mobile subscriber's country of domicile.

Tcl Parameters:

Mobile Network Code

Defines the mobile subscriber's home PLMN.

Tcl Parameters:

Location Area Code

Defines a location within the PLMN.

Tcl Parameters:

Defines the location of the Cell for a MS reported by the UE in SGW Nodal testing.

Range: 0 — 65535

Default: 0

Tcl Parameter:

Defines the location of the Service Area for a MS reported by the UE in SGW Nodal testing.

Range: 0 — 65535

Default: 0

Tcl Parameter:

Defines the routing information for an MS reported by the UE in SGW Nodal testing.

Range: 0 — 65535

Default: 0

Tcl Parameters:

Defines the last visited location reported by the UE.

Range: 0 — 65535

Default: 0

Tcl Parameters:

Defines the cell identity for an MN reported by the UE in SGW Nodal testing.

Range: 0 — 65535

Default: 0

Tcl Parameters:

Defines the cell identity size for an MN reported by the UE in SGW Nodal testing.

Range: 24-bit or 28-bit

Default: 28-bit

Tcl Parameters:

Available when GTPv2 Version >= 15.2.0. Select to include the UP Function Selection Indication Flags IE to CSReq when Dual Connectivity is indicated. Add Macro eNodeB ID and Extended eNodeB ID to ULI IE.

Tcl Parameters:

Available when GTPv2 Version >= 15.2.0 and Include Macro eNodeB is enabled. Defines the Macro eNodeB cell identity size for an MN reported by the UE in SGW Nodal testing.

Range: 20-bit or 21-bit

Default: 20-bit

Tcl Parameters:

Available when GTPv2 Version >= 15.2.0 and Include Macro eNodeB is enabled. Defines the Macro eNodeB cell identity for an MN reported by the UE in SGW Nodal testing.

Range: 0 — 2097151

Default: 0

Tcl Parameters:

Available when Include E-UTRAN Cell Global Identifier is enabled. Select to include the Multiple Operator Core Network (MOCN). When selected, also enter the MOCN MCC (Mobile Country Code) and MOCN MNC (Mobile Network Code).

Tcl Parameters:

Select to enable eNodeB based allocation - only available if Include Tracking Area Identity or Include E-UTRAN Cell Global Identifier in the User Location Information section are enabled.

If Include Tracking Area Identity (in User Location Information section) is enabled, then Number of Tracking Areas and Starting Tracking Area Code are also enabled.

If Include E-UTRAN Cell Global Identifier (in User Location Information section) is enabled, then Number of eNodeB's per Tracking Area, Starting eNodeB ID, Number of Cells per eNodeB and Starting Cell ID are also enabled.

Tcl Parameters:

Enter Number of Tracking Areas.

Range from 1 to 65535

Default = 1

Tcl Parameters:

Enter Number of eNodeB's per Tracking Area.

Range from 1 to 3000

Default = 1

Tcl Parameters:

Enter Number of Cells per eNodeB.

Range from 1 to 256

Default = 1

Tcl Parameters:

Enter Starting Tracking Area code.

Range from 1 to 65535

Default = 0

Tcl Parameters:

Enter Starting eNodeB ID.

Range from 1 to 524287

Default = 0

Tcl Parameters:

Enter Starting Cell ID.

Range from 0 to 255

Default = 0

Tcl Parameters:

Enter Downlink AMBR.

Range : 0 to 4294967295 (When Version > 8.0.0)

When Version = 8.0.0 the Downlink AMBR includes Octet 3.

Range: 0 — 255 (Use the conversion wizard for rate/value conversion.)

Default: 1

Tcl Parameter:  

Enter Uplink AMBR.

Range : 0 to 4294967295 (When Version > 8.0.0)

When Version = 8.0.0 the Uplink AMBR includes Octet 4.

Range: 0 — 255 (Use the conversion wizard for rate/value conversion.)

Default: 1

Tcl Parameter:

Extended Rates are only applicable when Version = 8.0.0.

Use the checkbox to include octet 5 when a downlink rate larger than 8,640 kbps should be requested. The bit rates are calculated in 100 kbps increments (8,700 — 256,000 kbps) as (8600 kbps + (value * 100 kbps)).

Range: 0 — 250 (Use the conversion wizard for rate/value conversion.)

Default: 1

Tcl Parameter:

Extended Rates are only applicable when Version = 8.0.0.

Use the Extended Rates Uplink checkbox to include octet 6, which is an extension of the APN-AMBR for Uplink in octet 4 and is identical to that of the APN-AMBR for Extended Rates: Downlink.

Range: 0 — 250 (Use the conversion wizard for rate/value conversion.)

Default: 1

Extended Rates are only applicable when Version = 8.0.0.

Use the APN-AMBR for Extended-2 Rates Downlink checkbox to include octet 7.

Range: 0 — 254

Default: 1

Extended Rates are only applicable when Version = 8.0.0.

Use the APN-AMBR for Extended-2 Rates Uplink checkbox to include octet 8. This parameter is an extension of the APN-AMBR for Uplink and APN-AMBR for Extended Uplink in octets 4 and 6. The coding is identical to that of the APN-AMBR for Extended-2 Rates Downlink.

Range: 0 — 254

Default: 1

Available on SGW Node TC when Sxa Interface to UP or Sxa+Sxb Interface to UP is enabled and on PGW Node when Sxb Interface to UP is enabled. Indicates the status of the Gate Uplink.

Options: On (default), Off

Available on SGW Node TC when Sxa Interface to UP or Sxa+Sxb Interface to UP is enabled and on PGW Node when Sxb Interface to UP is enabled. Indicates the status of the Gate Downlink.

Options: On (default), Off

Select for 4G-5G dual connectivity. Available in PGW Nodal test case.

Additional detail in NAS Tab Dual Connectivity.

Secondary Rat Usage Data Report Timer. Available when Test Activity = Intra-MME Mobility and Handoff Type = Dual Connectivity.

Range: 0 to 900000 (report will not be reported)

Default: 0

Tcl Parameter: SecRatReportInterval

Select to indicate Target support NR (New Radio).

Tcl Parameter: TargetSupportNr

Bearer Type = MCG (Master Cell Group), Radio Type = NR or LTE

Use the dropdown list to include the optional APN Restriction information element messages sent by the PDN GW Node. It indicates the restriction level imposed on the PDP contexts associated with an APN.

Select the APN Restriction used for all APNs. Example:If the Create PDP Context request contains an APN Restriction value of 3, the PDN GW may only allow the requested context to be established if it has an APN Restriction of 1.

Options:

• No existing contexts or restrictions, all contexts are allowed to be created — 0  
• Public-1 (e.g. WAP, MMS): contexts with restriction values 1-3 are allowed to be created — 1
• Public-2 (e.g. Internet, PSPDN): contexts with restriction values 1-2 are allowed to be created — 2
• Private-1 (Corporate): contexts with restriction value 1 are allowed to be created  — 3
• Private-2 (Corporate): no contexts are allowed to be created — 4

Tcl Parameter:

Use dropdown list to indicate the APN selection mode to be used. The Starting Access Point Name uses the value in the Selection Mode. The PDN GW/GGSN may use Selection Mode when deciding whether to accept or reject the requested PDP context activation. If the requested APN requires subscription, the PDN GW/GGSN may reject requests with a Selection Mode of 1 or 2.

Options:

• MS-provided or network-provided APN — 0

• MS-provided APN, subscription not verified — 1

• Network-provided APN, subscription not verified — 2

• Reserved for future use. It is not sent and if received, it is interpreted as 2 — 3

Tcl Parameter:  

Related Measurements

• APN Access Denied Error

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:

Gtp2ApnTotalApns_0

Gtp2ApnTotalApns_1

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: Gtp2Apn_0

Gtp2Apn_1

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: Gtp2ApnRetries_0

Gtp2ApnRetries_1

Related Measurements

• APN Retries

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: Gtp2ApnNumSpecifiedApns_0

Gtp2ApnNumSpecifiedApns_1

Enabling this flag allows the MME Node to use the APN name returned in the ULA message. The Create Session Request sent to the SGW will use this HSS APN name for the first default bearer. The HSS APN Name can completely overwrite the APN Name configured on the MME Node or it can be the prefix/suffix of the APN name configure on the MME Node.

Example: MME Node APN Name = spirent, HSS APN Name = testing123 :

The APN Name sent in the Create Session Request to the SGW can be configured as one of the following:

testing123 with option REPLACE

testing123.spirent with option APPEND_PREFIX

spirent.testing123 with option APPEND_SUFFIX

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.

In GPRS testing, select the R97 Only checkbox to send only 4-byte R97 QoS attributes (2G specification).

Tcl Parameter: QosR97En

• See QOS Profile for parameter settings.

The number of rows per APN Index is controlled by Default Bearers per Session.

Range : 0 to 10

Select to enter the Rate Control in minutes per APN.

Range : 0 to 16777215. Zero (0) = disabled.

Tcl Parameter: Gtp2NbIotApnRate_1

Select to enter the Rate Control in minutes per APN.

Range : 0 to 16777215. Zero (0) = disabled.

Tcl Parameter: Gtp2NbIotApnRateEx_1

You can define one QOS for all bearers or a different QOS for every bearer per subscriber.

• 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.

• Select Per Bearer radio button to define different QOS configuration among default bearers and dedicated bearers. (Supported in SGW Nodal (except when Test Activity is Inter-SGSN Mobility or Inter Technology Mobility, Command Mode/Sequencer) and PGW (except when Mobility is Inter Technology) and MME Nodal either with VoLTE enabled or when Test Activity is not Inter Technology Mobility and MME Node except when Mobility option is Inter-Tech)

When you select Individual, a Bearer sub-tab is displayed for each Maximum Bearer per subscriber (selected on the Mobile Subscriber pane on the Test Configuration tab). For example, if Maximum Bearers Per Subscriber is 10, the bearer QoS tabs displayed are Default, B2, B3 up to B11.

When you select Per Bearer , a Bearer sub-tab is displayed for each Default and Dedicated Bearer (selected on the Mobile Subscriber pane on the Test Configuration tab).

For example, if Default Bearers Per Subscriber is 2 and Dedicated Bearer per Default is 4 , then QoS tabs displayed are:

D0 (1st Default Bearer),

D0-B0 (1st Dedicated bearer associated with 1st Default bearer)  

D0-B1 (2nd Dedicated bearer associated with 1st Default bearer)  

D0-B2 (3rd Dedicated bearer associated with 1st Default bearer)  

D0-B3 (4th Dedicated bearer associated with 1st Default bearer)  

D1 (2nd Default Bearer),

D1-B0 (1st Dedicated bearer associated with 2nd Default bearer)  

D1-B1 (2nd Dedicated bearer associated with 2nd Default bearer)  

D1-B2 (3rd Dedicated bearer associated with 2nd Default bearer)  

D1-B3 (4th Dedicated bearer associated with 2nd Default bearer)  

Tcl Parameter: Gtp2QosDetail

Available on MME Node S11 / N26 interface.

Select to support Unique QCI per Bearer for N26 4G/5G Handover.

Tcl Parameter: Gtp2QosAllocateSpaceEn

The Class ID in the Bearer QOS applies to the Uplink (UL) and Downlink (DL) IP flows. LTE test cases provide you with the ability to configure various QCI.

You can choose to use the same QoS Class ID for all IP contexts or you can define different Class IDs for each context.

Range: 0 — 255

• For values 1, 2, 3 and 4 the Maximum Bit Rate UL and DL parameters are available by default. The Set Bit Rates checkbox is not available.
• For values 5, 6, 7, 8 and 9, the Maximum Bit Rate UL and DL parameters are not available. The Set Bit Rates checkbox is not available. For PGW Node Test Case only, the Set Bit Rates checkbox is available and the Maximum Bit Rate UL and DL parameters are available only if the Set Bit Rates checkbox is selected.
• For values 0 and 10 to 255, the Set Bit Rates checkbox is available and the Maximum Bit Rate UL and DL parameters are available only if the Set Bit Rates checkbox is selected.

Tcl Parameter: Gtp2QosClassId_1

Range: 1 - 15

Default: 1

Tcl Parameter: Gtp2QosArpValue_1

The Set Bit Rates checkbox is available only when Class Identifier value is 0 or between 10 and 255.

Select the Set Bit Rates checkbox to enter Maximum Bit Rates and Guaranteed Bit Rates values for UL and DL traffic.

Range : 0 to 255

Tcl Parameter: Gtp2QosBrEn_1

Selecting this checkbox indicates that the bearer may preempt other bearers with a lower ARP value when resource limitations are reached.

Tcl Parameter:

Gtp2QosArpPreemptCapEn_1

Selecting this checkbox indicates that a bearer is vulnerable to being dropped when resource limitations have been reached and there is a bearer with a higher ARP value in service.

Tcl Parameter:

Gtp2QosArpPreemptVulnEn_1

Define the IP flow Maximum Bit Rates and Guaranteed Bit Rates for UL and DL traffic.

Range: 0 - 10000000000

Default: 1

Tcl Parameter:

Gtp2QosMaxUplink_1

Gtp2QosMaxDownlink_1

Gtp2QosGuarUplink_1

Gtp2QosGuarDownlink_1

Available on SGW Node TC when Sxa Interface to UP or Sxa+Sxb Interface to UP is enabled and on PGW Node when Sxb Interface to UP is enabled. Indicates the status of the Gate Uplink and Downlink.

Options: On (default), Off

Tcl Parameter:

Gtp2QosGateStatusUplink_1

Gtp2QosGateStatusDownlink_1

The Protocol Configuration Options in all LTE test cases support configuration of username/password for authentication to the PGW. Use the radio buttons to select an authentication method.

Options: No Authentication, PAP Authentication, CHAP Authentication

Default: No Authentication

When you select Include PAP Authentication, you can define the password and peer ID.

• Password defines the password to be used for PAP authentication. This may be the subscriber's password.

Range:  N/A

Default: Secret

• Peer ID defines the peer to be used for PAP authentication.  A unique ID can be supplied for each context by using the Auto-Increment feature. This value may be the subscriber's user name, and the GGSN may or may not use a DNS or AAA server to validate this field.

Range:  N/A

Default: Secret

Tcl Parameters: Gpt2PcoPapPeerId_1

When you select Include CHAP Authentication, you can define the fields that are used to build the CHAP ID field. The field is coded as a CHAP response, and is not checked by the GGSN. The GGSN sends this value to a RADIUS server in an Access Request message.

• Identifier defines the CHAP identifier to be used for CHAP authentication.

Range:  0 — 255

Default: 0

• Name defines the subscriber's user name to be used for CHAP authentication. A unique name can be supplied for each PDP context by using the Auto-Increment feature.

Range:  N/A

Tcl Parameter: PppPcoChapName_1

• Secret defines the secret used by both the client and server in the MD5 calculation.

Range:  N/A

Default: secret

• CHAP Challenge Value defines the CHAP value, in hex, to be used for CHAP authentication.

Range:  0-F characters

Default: ABCD

Tcl Parameter: Gpt2PcoChapId

Related Measurements

• User Authentication Failure

Select to exclude PCO addresses in Delete Session Request message. Enabled when IP Control Protocol or Additional Parameters are enabled.

Default = False

Tcl Parameter: Gpt2PcoExcludeInDsrEn

During HSGW, SGW, and PGW Nodal testing, select IP Control Protocol to include the protocol configuration options (PCO) IEs in the Create PDP Context Request. In PGW Node test case, only IP Control Protocol is available for selection.

NOTE: Multiple protocol configurations are included in a single PCO.

Tcl Parameter: Gtp2PcoIpcpEn

Type:  True/False

Default: False

Select IP Control Protocol and then enter IPCP IP Address, primary and secondary addresses for WINS and DNS servers. You may enter IPv4 or IPv6 addresses, as required.

Type: True/False

Default: False

Tcl Parameters:

Select

• Test Activity = Inter-Technology Mobility
• Circuit Switch Fallback
• Handoff Protocol = GPRS
• Handoff Type = TAU/RAU

Do Not Select

Ensure that DTM Support is not selected.

Resume Options

Options: Resume Only (0); Resume and Modify (1); Modify Only (2)

Default: Resume and Modify

Tcl Parameter: PppResumeOption

Tcl Parameter: Gtp2ResumeOption

Modification Initiator

Select the bearer modification initiator from the Modifications Initiator drop-down list. In SGW Nodal and PGW Nodal test cases, Modification Initiator is not available when Test Activity is Command Mode.

Options: HSS, MME, UE

Default: HSS

Tcl Parameter: Gtp2BearerModInit

HSS-Initiated Bearer Modification

In SGW Nodal Testing, the HSS-Initiated Bearer Modification allows you to enter the Aggregate Maximum Bit Rate Information and Bearer Quality of Service Modification and update initiated from the MME Node.

Select the HSS from the Bearer Modification dropdown list to enable Aggregate Maximum Bit Rate and Bearer Quality of Service Modification and Update initiated from the MME.

Delay Time (s)

The Delay Time specifies the time in seconds to wait after initial session creation or the previously Initiated Bearer Modification procedure has completed.

If the Continuous Modification checkbox is selected, the Delay Time indicates the time to wait before starting the HSS/MME/UE Initiated Bearer Modification procedure.

Options: 1 - 10000

Default: 60

Tcl Parameter: Gtp2BearerDelayTime

Continuous Modification

Use the Continuous Modification checkbox to generate the HSS/MME/UE Initiated Bearer Modification procedure repeatedly at the rate defined by the Delay Time.

Value: True/False

default: True

Tcl Parameter: Gtp2BearerContinuousMod

MME-Initiated Bearer Modification

In SGW Nodal Testing, the MME-Initiated Bearer Modification allows you to enter the optional User Location Information elements, Aggregate Maximum Bit Rate Information, Bearer Quality of Service Modification and update initiated from the MME Node.

Select the following checkboxes to include the IEs in an MME-initiated modification.

UE-Initiated Bearer Modification

In SGW Nodal Testing, the UE-Initiated Bearer Modification allows you to enter modified Bearer Quality of Service Modification, Modified TFT Settings and update initiated from the UE.

• Select the Include QoS IE checkbox to include the Bearer Quality of Service Modification IEs in an UE-initiated modification.
• Click the Modified TFT Settings button  to enter the relevant parameter values. The Modified TFT Settings button is enabled only if the Maximum Bearers per Subscriber (SGW Nodal Test Configuration) is greater than one.

APN Aggregate Maximum Bit Rate Information (Bearer Modification)

See APN Aggregate Maximum Bit Rate Information

Bearer Quality of Service (Bearer Modification)

See Bearer Quality of Service.

Enable Trace Management

Select checkbox to Enable the Trace Management options. Currently only available on the PGW Nodal test case when S5/S8 interface is enabled.

Tcl Parameter: Gtp2TraceMgmtEn

Trace ID

Enter the Trace ID.

Range from 0 to 16777215

Default = 0

Tcl Parameter: Gtp2TraceMgmtId

Trace Collection Entity Address

Enter a Valid IPv4 or IPv6 address of trace collection entity.

Tcl Parameter: Gtp2TraceMgmtAddr

Starting IMSI

Enter the starting IMSI

Up to 15 digits

Default = 505024101215074

Tcl Parameter: Gtp2TraceMgmtStartingImsi

Number of IMSI

Enter the Number of IMSI

Range from licensed value of Maximum Subscribers

Default = 1

Tcl Parameter: Gtp2TraceMgmtStartingImsi

Enable Wait Time Options

Enable to be able to generate an Origination Time Stamp and a Max Wait Time for every new PDN connection request. Per 3GPP 29.274  v13.3.0.

Tcl Parameter: Gtp2MaxWaitTimeEn

Max Wait Time (ms)

The amount of time given to establish the PDN connection through the SGW/PGW pair.

Range from 0 to 65535

Default = 10000

Tcl Parameter: Gtp2MaxWaitTime

Origination Timestamp

This is the time at which the MME first tried to establish a PDN connection through a particular SGW/PGW pair.  If the MME decides to select a new SGW/PGW pair it will generate a new Origination Timestamp.

Click to select Date/Time. UTC time accurate to millisecond.

Tcl Parameter: Gtp2OrgTimeStampEn

Tcl Parameter: Gtp2OrgTimeStamp

Private Extension

Select to enable Private Extension.

Tcl Parameter: Gtp2MaxWaitTimePrivExtEn

Distribution Options

Enter Distribution Options. See Additional Details.

Fixed, Poisson, Uniform  (Enter Maximum Deviation From Mean (% of mean)

Normal (Enter Standard Deviation (% of mean)

Tcl Parameter: Gtp2MaxWaitTimeShape

Tcl Parameter: Gtp2MaxWaitTimeDeviation

Delay Response (ms)

Emulate delayed response from PGW/SGW. PGW Emulation on SGW Node Emulator Configuration tab must be enabled to become available.

Range from 0 to 65535

Default = 0

Tcl Parameter: Gtp2ResponseDelayEn

Tcl Parameter: Gtp2ResponseDelay