NAS Tab

See Applying Test Data FileApplying Test Data File.

Added support for encrypted TDF fields on the S1-MME NAS tab for MME Nodal test case. The Encrypted columns will show up in the other test cases but are only supported by MME Nodal.

Added columns: (Sample file below)
     "Secret Key Encrypted"
     "Operator Variant Encrypted"
     "Operator-c Variant Encrypted"

Landslide has two instances of the TDF-CSV editor, the Embedded TDF-CSV Editor, launched in the Landslide Client from within the context of a TDF Parameter or DMF TDF, and the Standalone TDF-CSV editor, launched as a separate application (can also be launched from within the Landslide Client).  When using encyption feature in the Embedded TDF-CSV Editor, the user level is known and if the user is sms or System-Admin, the encrypted value will be automatically decrypted when editing the value.  For all other user levels and on the Standalone TDF-CSV Editor, which has no user indication, the value will be cleared when editing.   The user must cancel editing (Esc/F2) to maintain the original value.

For Test Data Files containing encrypted columns, all users may generate new encrypted values using the TDF CSV editors starting from an initially blank value. Individual cells may be filled in with a non-encrypted value and the cell editor will encrypt it when the change is committed by pressing Enter or selecting another cell. When not in the process of editing, the TDF CSV editors will only display encrypted values for encrypted columns.  For users with System Admin or Super-User privilege, previously encrypted cells will be decrypted for editing.

Once per client session, an informational dialog will appear the first time the user selects an Encrypted column cell.

For Encrypted columns, the TDF-CSV editor will automatically encrypt the value when it is saved in the cell.

All users may use the Column Fill Wizard on encrypted columns. This wizard never starts out with existing data so there is no difference in its use related to user privilege level.  The Column Fill Wizard works the same on encrypted columns, with the preview window showing the unencrypted values based on the formula set up in the wizard.  When the change is accepted in the dialog, the data filled in an encrypted column will be encrypted.

When an encrypted column is being used, its corresponding non-encrypted column should be blank or can be deleted from the TDF.  If both columns have information, the last column read in by the test server takes effect.  The TDF CSV editor will warn about it but not block it.

Please be aware that the TDF-CSV Editor handles encryption mode automatically based on the name of the column. Currently, these fields are supported : "Secret Key Encrypted",      "Operator Variant Encrypted", "Operator-c Variant Encrypted"

Limitations: Encrypted columns cannot be populated on auto-incrementing rows within the TDF CSV editors.  An auto-incrementing row is when "Auto-Incrementing Groups(~)" is checked on the toolbar and the "Group Size (~)" column has a non-zero number value entered.

• mme_SameIMSI_MMEConfigData
• mme_EPC-SIM_UE_auth_example (See also MME TDF Files)
• EPC-SIM_UE_auth_encrypted_example_1ue.csv
• In MME Node test case, see MME Node - Provisioning TDF.

• Tcl Parameters: NasCfgFileEn

Apply Test Data File to Bearer Context

• mme_BcConfigFile

• mme_pco

• MmeBearerTDF-MME Default BearerAPN (See also MME TDF Files)

• Tcl Parameters: BearerCfgFileEn

Select the proprietary version of the application from the dropdown list.

Options: 8.1.0 (0), 8.2.0 (1), 8.3.0 (2), 8.4.0 (3), 8.5.0 (4), 8.6.0 (5), 9.4.0 (6), 9.5.0 (7), 9.6.0 (8), 9.7.0 (9), 9.8.0 (10), 10.6.0 (11); 10.8.0 (12); 11.4.0 (13); 12.10.0 (14) ; 13.6.1 (15); 15.1.1 (16), 15.5.0 (17)

Tcl Parameters: Version

Select the type of information the IE will contain.

Options: IMSI (International Mobile Subscriber Identifier), GUTI (Globally Unique Temporary Identity), GPRS (Only applicable when Vendor Variant is 2)

Default: IMSI

When you select GUTI, the Starting T-MTSI becomes available. (A Mobile TMSI (M-Temporary Mobile Subscriber Identity) identifies the mobile station within the MME.)

When you select IMSI, the Reattach with GUTI becomes available.

Tcl Parameters:

Select the Attach Type from the dropdown list.

Options: Combined EPS/IMSI Attach, EPS Attach

When (Attach Type is Combined EPS/IMSI Attach and NAS Version is > =  8.4.0) or (Attach Type is EPS Attach and NAS Version is > = 13.6.1), Include Additional Update Type becomes available.

Options: SMS Only, No additional information

Tcl Parameters:

Select the type of detach information the test sends the MME in the detach message.

Options: IMSI Detach, EPS Detach, Combined EPS/IMSI Detach (MME Nodal)

Options: Re-attach Required, Re-attach Not Required, IMSI Detach (MME Node)

Default: EPS Detach

Tcl Parameters: DetachType

Select the type of detach mode from the dropdown list.

Options: Normal Detach, Switch Off

Tcl Parameters: DetachMode

(In HSGW and MME Nodal test cases)

Provides you with an option to send PDN Detach or Disconnect Request.

For multiple Default Bearers, you send a PDN Disconnect Request fot disconnect all Default Bearers except for the last Default Bearer, which is sent PDN Detach Request.  

Tcl Parameter: DetachOption

Options:

• No PDN Disconnect = 0 (default)
• PDN Disconnect for Multiple Defaults = 1

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.

Range: 5 — 15 digits

Default: 50502410121507

Tcl Parameter: Imsi

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: N/A

Tcl Parameter: Imei

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

The version value is combined with the IMEI when IMEISV identity type is used. The same value is used for all MSs and it is a fixed length of 2 digits.

Range: 00 —99

Default: 00

Tcl Parameter: SwVersion

Select the check box to ensure that the UE sends the MME-Assigned GUTI to the base station to identify the MME to which the UE should send requests to re-establish a communication session.

Tcl Parameter: UseMmeAssignedGuti

ESM Information Transfer Required

Secured Transfer of PCO

In MME Nodal , gNB CU NSA and HSGW Nodal testing, when you select the ESM Information Transfer Required checkbox, the MME initiates EMS Information Request and includes the ESM Information Transfer flag in PDN Connectivity Request.

Select for Secured Transfer of PCO.

Tcl Parameter: NasEsmInfoRequiredEn

Tcl Parameter: NasSecPcoTransEn

Value: True, False

Default: False

Used in MME Node testing to indicate Authentication is required. Select Perform Authentication and enter the Secret Key and Operator Variant used for authentication.

Tcl Parameter: AutenticationEn

Select an Authentication Algorithm. Additional fields become available for input.

Options : Milenage ( Defined in 3GPP TS 35.205) , Test Algorithm ( Defined in 3GPP TS 34.108) , TUAK ( Defined in 3GPP TS 35.231)

TUAK is a 3GPP defined algorithm and key generation set of functions (f1, f1*, f2, f2, f4, f5, and f5*).  

TUAK is currently available in MME Nodal, MME Node and in AMF Nodal with Inter Technology Mobility S1-MME Tab.

Tcl Parameter: NasAuthAlgorithm

Enable Encrypt to encrypt Secret Key, Operator Variant, OPc. Available when Algorithm = Milenage or Test Algorithm.

Any user type can enter the value in plain text, and then click an “Encrypt” button which will encrypt the value and switch the TC-GUI to use new parameter variable name with _Enc Suffix. (encrypted-mode). The fields in the GUI will become like passwords with just "****************" in them and they will be not be edit able. However, a Super User or System Admin user is required to Decrypt.

From Encrypted mode:

• The Super-User (sms) or a System-Admin level user or above can click a “Decrypt” button which will decrypt all the values back to plain text and revert back to the normal variable name. Encrypt becomes available again of the user wants to use it.

• Any Test-Operator can click a “Reset” button which will allow them to enter new values, and then click Encrypt later.

The MS's text or hexadecimal key that is associated with its GUTI and is used to derive the MME/LTE ciphering key. Available when Algorithm = Milenage or Test Algorithm.

Range: Either String or HEX, If hex must start with 0x

Variable name with _Enc Suffix denotes Encrypted mode.

Tcl Parameter: SecretKey

Tcl Parameter: SecretKey_Enc

Per 3GPP (33.102) specified RES Length of 4-16 octets. Available when Algorithm = Milenage or Test Algorithm.

Range: 4 to 8

Default : 8

Tcl Parameter: AuthResLen

The 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Available when Algorithm = Milenage or Test Algorithm.

Range: Up to 16-Byte hex string

Default: 0x63BFA50EE6523365FF14C1F45F88737D

Variable name with _Enc Suffix denotes Encrypted mode.

Tcl Parameter: OpType

Tcl Parameter: OpType_Enc

Tcl Parameter: OpVar

Tcl Parameter: OpVar_Enc

A128-bit value derived from OP and K and used in subsequent computations. Hence, less sensitive and if obtained by third party. Available when Algorithm = Milenage or Test Algorithm.

Range: Up to 16-Byte hex string

Default: 0x63BFA50EE6523365FF14C1F45F88737D

Variable name with _Enc Suffix denotes Encrypted mode.

Tcl Parameter: OpC

Tcl Parameter: OpC_Enc

The AMF parameter is available in MME Node test case when you select Perform Authentication. Enter the appropriate AMF (Authentication Management Field) value to be used for different version of separation bit and test algorithm. Available when Algorithm = Milenage or TUAK.

Value: 2 byte Hex String (prefixed with "0x")

Default: 0x8000

Tcl Parameter: Amf

Tcl Parameter: TuakAmf

The following fields become available when Algorithm = TUAK. For information about how the fields are used in the TUAK algorithm the user should refer to the 3GPP TS 35.231 specification.

Key	This is the secret key and is analogous to the Milenage Secret Key field. Enter either a String value or a Hex value beginning with 0x. Tcl Parameter: TuakKey
TOP	The Edit Top data input box associated with TOP allows the user to input a 32 byte Hex string value used for the operator variant. Tcl Parameter: TuakOpType
Key Length (bytes)	Select the maximum length supported for the secret key. Support for 16 or 32 bytes. Tcl Parameter: TuakKeyLen
RES Length (bytes)	Select the maximum length supported for the RES value. Support of 4 or 8 bytes only. Tcl Parameter: TuakResLen
Keccak_f Iterations	Enter the number of times the Keccak permutation is performed. Range : 1 to 255 Default : 1 Tcl Parameter: TuakIterations
MAC Length (bytes)	Select the maximum length supported for the MAC fields (MAC-A and MAC-S). Support 8 bytes. Tcl Parameter: TuakMacLen
CK Length (bytes)	Select the maximum length supported for the confidentiality key. Support 16 bytes only. Tcl Parameter: TuakCkLen
IK Length (bytes)	Select the maximum length supported for the integrity key. Support 16 bytes only. Tcl Parameter: TuakIkLen

In MME Nodal test case, select Authentication Use Test Algorithm to allow the authentication procedure to be performed without the OP Variant. That is, the Test Algorithm allows you to configure any OP Variant value for a successful authentication procedure (the algorithm is used in a XOR cipher).

In MME Node test case, this parameter is available only when you select Perform Authentication.

Tcl Parameter: TestAlgorithmEn

Ability to turn GTP-U sequence number on/off in S1-U. Lte eNode will include the GTP-U sequence number in the  GTP-U packet that is sent to the SGW when this flag is turned on. The Starting sequence number is set in the Starting GTP-U Sequence Number parameter.

Not available when Fireball is enabled or when Handoff Type = X2.

Default: false

Tcl Parameter: NasEnbGtpuSeqInS1uEn

Starting GTP-U Sequence Number will be sent to Lte enode when include GTP-U sequence Number in S1-U is enabled. The GTP-U sequence Number in a GTP-U packet is sent to SGW re-start with the Starting GTP-U Sequnece Number whenever GTP-U tunnel is updated as in Case 1 and 2

Case 1.  When S1-U is released and then re-connected (ex, Session Loading or Inter-Tech Test)

Case 2.  When S1-U GTP tunnel information (Transport Layer Address and TEID) is changed (ex, S1-Handover or X2-Handover Test)

Default :0

Tcl Parameter: NasEnbStartingGtpuSeqNum

The starting GTP-U Tunnel Endpoint ID.  If blank, a default GTP-U tunnel endpoint is used.

Range: 0 - 4294967295

Tcl Parameter: GtpuTunnelEndptId

Select to include Support UE Status IE and indicate N1 Mode as Registered or Un-Registered.

Available on MME Nodal test case and when Version is >= 15.5.0.

Tcl Parameter: UeStatusIeEn

Tcl Parameter: UeStatusN1ModeReg

Select to indicate that Interworking Without N26 Interface is Supported. (IWK N26) (octet 4, bit 7).

Bit 7 is set to 1 when Interworking Without N26 Interface Supported is enabled. Otherwise it is set to 0. 

Available on MME Node test case and when Version is >= 15.5.0.

Tcl Parameter: NasIwkN26En

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

Type: Tue/False

Default: False

Tcl Parameter: NasPersistentImsiEn

Have the sessions on MME 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.

When checked (enabled) RRC-Establishment-cause of NAS attach request shall be set to highPriorityAccess (1) for indicating a priority attachment from a UE who is a member of a special access class (11 to 15). Enable for VoLTE Priority Call.

Tcl Parameter: HiPriRrcEstabCauseEn

Select Perform Security Mode and select the algorithm used for authentication purposes.

Tcl Parameters:

Select to enable GUTI Reallocation command message. The GUTI reallocation procedure allocates a GUTI and optionally provides a new TAI list to a particular UE.

The GUTI reallocation procedure may be implicitly performed along with Attach or Tracking Area Update procedure or using the GUTI reallocation command message. The MME prepares a GUTI reallocation command message and sends it to the UE only in EMM registered state. The UE updates the new GUTI and TAI list and responds with a GUTI reallocation complete message to the MME.

Tcl Parameters: GutiReallocTime

Retries is the number of times a message will be re-transmitted after the retry time/interval expires.

Tcl Parameters: RetryCnt

The Retry Time is the value for the retry interval timer. The second retry attempt, if any, will be made after both Idle Entry Time and the Retry Time are exceeded.

Tcl Parameters: RetryTime

Available only in MME Nodal, MME Node and HSGW Nodal test cases. The MME will send an S1 Release Command when it expires which will put the UE into the idle state.

Range: 0 to 65535

Default : 0

See also the note below

The Idle Entry Time is the length of time an active MN with no data transactions will remain active before going idle. For example, if you have a data transaction rate of 1 transaction per second (1.0) and the idle entry timer is set to 5 seconds, the MN will never go idle. A data transaction rate of 1 transaction per 10 seconds (0.10) will cause the MN to send data, @5 seconds the MN will go idle, @10 seconds the MN will go active and send data, @15 seconds the MN will go idle, etc.

Tcl Parameters: IdleEntryTime

Available only in MME Nodal and HSGW Nodal test cases. Time in milliseconds.

The Active Entry Time is the length of time a UE waits in Idle Mode before entering Active Mode (without using data to trigger Active Mode). You may also use the Command Mode ActivateConnection to initiate UE from idle mode to active mode without using data as the trigger.

Range: 0 - 4294967295

Default: 0

Tcl Parameter: ActiveEntryTimeMs

Select whether the Tracking Area Update (TAU) will function in the normal LTE mode (presented in seconds on GUI - see notes below) or in the call Modeling mode (presented in milliseconds on GUI).  

Tcl Parameters: TauTimeSpec

When TAU Time Spec - LTE (s) mode is selected:

The Tracking Area Update (TAU) Time is the length of time to wait before sending the Tracking Area location used by UE during the attach procedure with the MME (when LTE (s) mode is selected).

Range: 0 to 35712000 (when LTE (s) mode is selected)

Default: 0 (If 0, timer is deactivated, when LTE (s) mode is selected)

When TAU Time Spec - Modeling (ms) mode is selected:

Range: 0 to 4294967295 (when Modeling (ms) mode is selected)

Default: 0

Select to use in call modeling mode where the timer can be defined in milliseconds.

Tcl Parameters: TauTime

The amount of time, in minutes, between the GTPU tunnel echo messages that are sent between the MME and SGW to detect path failures. Enter 0 to disable the echo messages.

Range:  0 - 65535

Default: 0

Tcl Parameters: EchoMessageTime

When an additional PDN connection is requested by the UE which is not combined in the attach procedure, this timer is used to reattempt the PDN Connection upon time out. Per 3GPP 24.301.

Range:  0 - 65535

Default: 8

Tcl Parameters: T3482Time

Enter number of retries to reattempt the additional PDN Connection after T3482 Time out. Per 3GPP 24.301.

Range:  0 - 255

Default: 8

Tcl Parameters: T3482Retries

In MME Nodal testing, use Paging Response Delay to configure a delay between the Paging Request and the Service Request, that is, specify an interval where only paging messages are sent.

Range: 0 - 65535

Default: 0

Tcl Parameters: PagingResponseDelayTime

In MME Node testing, the Paging Time indicates the time taken to send and receive Paging Indication messages.

Tcl Parameters: PagingTime

The Indirect Forwardings checkbox is available only when the Test Activity is Inter-MME and Handoff type is Handover on the Test Configuration tab (TAU does not have indirect forwardings function).

Indirect Forwarding is used when the source eNodeB senses an error on the handoff MME 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 MME 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.

Added support in AMF Nodal for direct data forwarding for EPS to 5GS handover when S1-MME is enabled. During the EPS to 5GS handover, the Direct-Forwarding-Path-Availability IE is contained in the S1AP Handover Required message.

The Indirect Forwardings checkbox is forced checked on when NGAP Version (38.413) is less than 16.0.0. It it configurable on this NAS tab for NGAP Version (38.413) 16.0.0 or above. 

Limitation: Per 23.502, only indirect data forwarding is allowed for Inter-tech handover in Release 15. Release 16 allows both direct and indirect data forwarding. Therefore EPS to 5GS handover using direct data forwarding is limited to NGAP version 16 or above.

Spec reference (5G)

3GPP TS 23.502 - Procedures for the 5G System (5GS); Stage 2

3GPP TS 38.413 - NG Application Protocol (NGAP)

3GPP TS 29.274 - Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)

3GPP TS 36.413 - S1 Application Protocol (S1AP)

Tcl Parameter: NasIndirectForwardings

Indicates the starting APN value assigned to PDP contexts. Not available in MME Nodal Test case.

Range: N/A

Default: ssenoauth146

Tcl Parameters: SmApn

In MME Node test case, used for end-to-end testing of the Emergency APN.

Options: 2 - 256 characters

Default: Emergency.apn.spirent

Tcl Parameter: EmergencyApnName

When testing VoLTE Emergency call configured with dedicated bearer (MME Nodal TC), configure Emergency APN on MME Node TC so ensure the PCRF sends RAR Gx msg to install rules that trigger the Dedicated Bearer creation.

Use the checkbox to include EMM (EPS Mobility Management) in Security Header.

Tcl Parameters: SecurityHeaderEmmEn

The checkbox is enabled for NAS Version 15.1.1 or later. Available in AMF Nodal, MME Nodal and MME Node. Select to support HASHMME per Reference spec 24.301 section 5.4.3.3

"If, during an ongoing attach or tracking area updating procedure, the SECURITY MODE COMMAND message includes a HASHMME, the UE shall compare HASHMME with a hash value locally calculated as described in 3GPP TS 33.401 [19] from the entire plain ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message that the UE had sent to initiate the procedure. If HASHMME and the locally calculated hash value are different, the UE shall include the complete ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message which the UE had previously sent in the Replayed NAS message container IE of the SECURITY MODE COMPLETE
message."

Tcl Parameters: HashMmeEn

Select the checkbox to swap the order of short MAC in the Service Request message.

Tcl Parameters: SwapOrderOfShortMac

Use the following to specify whether context setup is requested during TAU with and without relocation.

On MME Nodal test case, available when you select Handoff Type = TAU/RAU on the Test Configuration tab (UMTS and GPRS) or when the Test Activity = Command Mode/Sequencer and the Handoff Protocol is not 1xRTT.   

Tcl Parameter: NasMobTauEfficiencyEn

When not selected, Mobility TAU is sent irrespective of whether it's in the TAI list or not.

Reattach after TAU Rejects and Timeouts

Select to re-attach after any TAU failures (TAU reject and TAU timeout). Available in MME Nodal. Currently this function works for all Test Types except for "Session Loading Test" and "Session Loading With Mobility".

Tcl Parameter: NasReattachTauFailureEn

Mobility TAU Active Flag

Select to set Bearer Establishment flag in TAU Request. Available in AMF Nodal and MME Nodal. When Handoff Protocol = 1xRTT, set to Auto.

Options: Auto, Active, Not Active

Tcl Parameter: NasMobTauActiveFlag

Emergency CSFB

Available in MME Nodal test case if Circuit Switched Fallback is enabled. Support for Emergency call with CSFB to 2G (GPRS ) or 3G (UMTS IuPS over IP- with CSFB Paging disabled).

Tcl Parameter: EmergencyCsfbEn

Support Extended PCO

Available in HSGW Nodal/Node and MME Nodal/MME Node test cases and when Version is >= 13.6.1. Select for support of Extended PCO (Protocol Configuration Options).

Tcl Parameter: NasExtendedPcoEn

Available in MME Nodal test case. Select to allow all configured UEs to attempt Attach Request message to be sent out to a connected MME, regardless if first MME is successful or not.

If this checkbox is not selected, the Attach Request message will not be sent out if pre-configured MME is not successfully connected to eNB.

Tcl Parameter: NasAttachToConnMmeEn

Available in MME Nodal test case. Select to restart UE which can’t trigger handover due to “Session Not Ready For Handoff”.

In the handover test (4g<->4g or 4g<->InterTech), if this option is enabled and UE can’t trigger handover procedure during handover test because of “Session Not Ready For Handoff”, UE will start over from the initial attach (on the 4G side) after the detach (if it can be sent) and then trigger handover in the next iteration for handover.

The purpose of this enabler is to make UE which may get stuck due to the unexpected situation keep running during the handover test.

Available when Test Activity is “Intra-MME Mobility or Inter-MME Mobility or Inter Technology Mobility”, and Mobility Mode is "Continuous Handoff". Available when Test Activity is Command Mode or Sequencer.

Limitation / Caveat: The graceful termination at non-LTE side is not supported in the case of InterTech Mobility. If UE is restarted due to "Session Not Ready for Handoff", UE will start from 4G side.

Tcl Parameter: NasRestartUeNotReadyForHoEn

PDN Reconnect Disconnected Bearers After (ms)

Available on MME Nodal test case. Select to enable PDN reconnect mechanism for deactivated bearers after the time entered in milliseconds.

Range : 10 to 100000 (in milliseconds)

Tcl Parameter: NasAutoPdnReconnectEn

Tcl Parameter: NasAutoPdnReconnectDelay

Available in MME Node. Select to Activate Multiple Dedicated Bearers per Message.

Tcl Parameter: NasActMultiDedBearerPerMsgEn

Available in MME Node. Enable to detect APN mismatches.

Tcl Parameter: ApnMismatchChkEn

Adjust Activation Rate for Attach Failures

Available in MME Nodal test case (test activities; Capacity, Session Loading, Mobility scenarios, Command Mode and Sequencer).

Selecting Adjust Activation Rate for Attach Failures allows emulated UEs/subscribers to attempt attach/PDN connect procedure until the attach/PDN connect succeeds. In addition, if UEs/subscribers attempts to establish multiple PDN connections, they try to establish until all PDN connections are established.

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. 

Available on MME Node.

Message Editor Protocol for MME node is "NAS MME".

Defined as "NasMme" for Tcl API:  ls::config $me_ -ProtocolId "NasMme".   

Select the Custom Messages Checkbox, 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.

Supported messages :

Tcl Parameter: MmeNasCustomMsgEn

Tcl Parameter: MmeNasCustomMsg

Type: True/False

Default: False.  

Tcl Parameter:

If this check box is selected, the MME Node will reject all Extended Service Requests from LAPI subscribers with a cause of Congestion.  There currently is no method to accept a portion of Extended Service Requests from LAPI subscribers before the node starts rejecting them. Extended Service Requests from non-LAPI subscribers are not affected

Type: True/False

Default: False.  

Tcl Parameter:

If this check box is selected, the MME Node will reject all Attach Requests from LAPI subscribers with a cause of Congestion.  There currently is no method to accept a portion of Attach request from LAPI subscribers before the node starts rejecting them. Attach Requests from non-LAPI subscribers are not affected.

Type: True/False

Default: False.  

Tcl Parameter:

If this check box is selected, the MME Node will reject all TAU Requests from LAPI subscribers with a cause of Congestion. There currently is no method to accept a portion of TAU request from LAPI subscribers before the node starts rejecting them. TAU Requests from non-LAPI subscribers are not affected.

Type: True/False

Default: False.  

Tcl Parameter:

If any (or all 3) of the above “Reject” check boxes is selected, this field defines the value for the back off timer that the MME node will include in the Reject messages. The input is defined in seconds but is converted to match the format required for the timer information element.  If the value input is 62 seconds or less it is divided by 2 (and the “units” field in the information element indicates the timer is in increments of 2 seconds).  If the value is greater than 60 it is rounded to the nearest minute (and the “units” field in the information element indicates the timer is in increments of minutes). A value of 0 indicates the timer is inactive (the information element will be included in the reject message but the value will be 0 indicating the timer should not be started). The deci-hours unit is not supported.

Range: 0 to 1860

Default: 0  

Tcl Parameter:

If this check box is selected, the MME Node will reject all Bearer Resource Allocation Requests from LAPI subscribers with a cause of Congestion.  There currently is no method to accept a portion of Bearer Resource Allocation request from LAPI subscribers before the node starts rejecting them. Bearer Resource Allocation Requests from non-LAPI subscribers are not affected. 

Type: True/False

Default: False.  

Tcl Parameter:

If this check box is selected, the MME Node will reject all Bearer Resource Modification Requests from LAPI subscribers with a cause of Congestion.  There currently is no method to accept a portion of Bearer Resource Modification request from LAPI subscribers before the node starts rejecting them. Bearer Resource Modification Requests from non-LAPI subscribers are not affected. 

Type: True/False

Default: False.  

Tcl Parameter:

Range: 0 to 111600

Default: 0  

Tcl Parameter:

Tcl Parameter:

Tcl Parameter:

Enable for Continuous Restoration. Is enabled, MME Node will continue to trigger HSS-based P-CSCF Restoration Indication event periodically as long as UE is in a connected state.

Tcl Parameter:

Type: True/False

Default: False.  

Tcl Parameter:

Select EIA1 or EIA2 or EIA3.

Type: True/False

Default: EIA1 = True; EIA2 = False ; EIA3 = False  

Tcl Parameter:

Select ProSe-dd or ProSe-dc. Support for Public Safety Proximity Services (ProSe). Available when Version >= 12.10.0

ProSe-dd =  True - Indicates whether the UE is authorized for ProSe Direct Discovery.

ProSe-dc =  True - Indicates whether the UE is authorized for ProSe Direct Communication.

Type: True/False

Default: False  

Tcl Parameter:

Select N1 Mode ( 5G ). Available when Version >= 15.5.0

Tcl Parameter:

Available in AMF Nodal, MME Nodal/MME Node, gNB CU NSA Nodal, UMTS. Available when NAS Version >= 15.1.1 and S1-AP Version >= 15.0.0

Added support for handover from 3x to option 2A (and vice versa) without secondary node on AMF Nodal test case. The 4G gNB User Node is available when Dual Connectivity is enabled and EPC gNB Node Measurements are generated.

Select for 4G-5G dual connectivity.

• Dual Connectivity on the GUI indicates the UE has such capability. The DCNR of the UE Network Capability shall be included in the Attach Request or TAU request. RestrictDCNR of EPS supported network capability returned by MME indicates UE if NR can be applied.

• NR Restriction returned to eNodeB indicates if eNodeB can apply dual connectivity. What type of dual connectivity (option 3/3x/3a) is selected by ENB and transparent to MME and UE.

• The gNB Node always works with the source eNodeB.

• Dual connectivity hold time which indicates when the dual connectivity will be released for option 3a or 3x.

• The dual connectivity is setup and released by the E-RAB modification procedure. For setup, the downlink transport IP address is the gNB Node IP. For release, the downlink transport IP address is the source eNodeB IP address.

Tcl Parameter: DualConnectivityEn

Select for Direct Establishment of SCG (Secondary Cell Group) Bearers. Available when DC Option = 3x or 3a.

Not available when Test Activity = Command Mode / Sequencer.

Tcl Parameter: DirectEstofScgBearers

Dual Connectivity hold time indicates when the dual connectivity will be released for DC option 3x or 3a.

Enter Dual Connectivity Hold Time in the S1-MME tab to support Dual Connectivity (4G + 5G) to 4G mobility after simulated CU shutdown in test case gNB CU NSA Nodal. This timer determines how long data will be sent through the DU User Node. When this time expires it will switch to the eNodeB User Node. This timer is per UE.

Not available when Test Activity = Command Mode / Sequencer.

Range: 0 to 65535000

Default: 0 (0 means Dual Connectivity is not released)

Tcl Parameter: DualConnectivityHoldTime

Enter value for delay timer for SCG Bearer setup.

Not available when Test Activity = Command Mode / Sequencer.

Range: 0.0 to 6.5535E7

Default: 1.5

Tcl Parameter: scgBearerDelayMs

Select for support of handover between two dual-connected 4g+5g nodes. A Target gNB User Node becomes available for input.

Available when Test Activity = Intra-MME Mobility or Inter-MME Mobility or Session Loading with Mobility and Mobility Type = Intra-MME or Inter-MME and DC Option = 3x or 3a.

Not available when Test Activity = Command Mode / Sequencer.

Tcl Parameter: TargetGnbNodeEn

Select for support of handover between two dual-connected 4g+5g nodes. A Target gNB User Node becomes available for input.

Available when Test Activity = Intra-MME Mobility and Handover Type = X2 and DC Option = 3x or 3a and Enable Target gNB User Node.

Not available when Test Activity = Command Mode / Sequencer.

Tcl Parameter: WithoutGnbChangedEn

Select Dual Option. Options : 3, 3x, 3a

Options : MN terminated, SN terminated in test case gNB CU NSA Nodal (see details below).

When DC Option 3 is selected, only MCG (Master Cell Group) Bearer Type allowed, Radio Type can = LTE or NR.

When DC Option 3x is selected, Bearer Type can be MCG (Master Cell Group) or SCG (Secondary Cell Group), Radio Type must = LTE for MCG Bearer Type. For SCG both bearer types (LTE and NR) are available.

When DC Option 3a is selected, Bearer Type can be MCG (Master Cell Group ) or SCG (Secondary Cell Group), Radio Type must = LTE for MCG Bearer Type and Radio Type must = NR for SCG Bearer Type.

For the 4G-5G dual connectivity to 4G mobility, the bearers are setup directly on gNB Node for option 3x or the dual connectivity will be re-setup for option 3x when the UE returns the source eNodeB.

For the capacity test or session loading without mobility, the bearers are setup directly on gNB Node for option 3x, the dual connectivity will be setup for option 3x after all the bearers are setup.

When UE enters state from idle mode in the source eNodeB, the bearers are resumed directly on gNB node for option 3x, the dual connectivity will be setup after UE returns enter est state.

Not available when Test Activity = Command Mode / Sequencer.

Tcl Parameter: DualConnectOption

Available in gNB CU NSA Nodal test case. Select to support split bearers per specification 3GPP  TS 37.340 Version 15.6.0

Select MN Terminated Bearer - In MR-DC, a radio bearer for which PDCP is located in the MN (Master Node). Not currently supported.

Select SN Terminated Bearer - In MR-DC, a radio bearer for which PDCP is located in the SN (Secondary Node).

DRB can be configured either via EUTRA-PDCP or NR-PDCP.

Per 38.323 NR PDCP 4.2.2 : 

For split bearers, routing is performed in the transmitting PDCP entity.

Indicate Bearer Type in table.

When DC Option 3 is selected, Bearer Type = MCG (Master Cell Group) only, Radio Type = NR or LTE

When DC Option 3x is selected, Bearer Type can be MCG (Master Cell Group) or SCG (Secondary Cell Group), Radio Type must = LTE for MCG Bearer Type. For SCG both bearer types (LTE and NR) are available.

When DC Option 3a is selected, Bearer Type can be MCG (Master Cell Group ) or SCG (Secondary Cell Group), Radio Type must = LTE for MCG Bearer Type and Radio Type must = NR for SCG Bearer Type.

When DC Option SN Terminated is selected, Bearer Type = SCG (Secondary Cell Group), LTE Radio is blank (not used) or Bearer Type = Split,  LTE Radio Type select a percentage 0%, 25%, 50%, 75% or 100%.

When using Split Bearer in the gNB CU NSA Nodal Test case, the Split Bearer percent % defines the amount of traffic to send in the UL using the eNodeB User Node. The DL traffic will always come back thru the gNB DU User Node. If you set the % to 100 for a given default bearer then 100% of the UL packets will be sent using the eNode User Node. If you set the % to 50 for a given default bearer then 50% of the UL traffic will be sent using the eNode User Node and the other 50% will be sent UL using the gNB-DU User Node. There will be a few packets for control sent UL over the gNB-DU User Node regardless of the Split Bearer % configured. Please be aware of that. If you run with multiple F1/X2 links then the UEs will be spread evenly across those links. The split bearer will work the same way for the UEs that are using a given F1/X2 pair.

Not available when Test Activity = Command Mode / Sequencer.

Tcl Parameter:

Select to enable Secondary Rat Usage Data Report. When it is enabled and the Periodic Report Timer is set to 0 (zero), it will perform non-periodic report. Otherwise, it will perform periodic and non-periodic report.

Enter Periodic Report Timer in milliseconds for periodic report generation.

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

Default: 0

Tcl Parameter: SecRatReportEn

Tcl Parameter: SecRatReportInterval

Enable Secondary gNB User Node

Master GNB Hold Time Percent

Select for support of 5G gNB only handover scenario in MME Nodal for 5G NSA testing feature. 

Select to add a secondary gNodeB user Node. 

MME Nodal will emulate a UE, an MN (eNB), a S-SN (Source gNB) and a T-SN (Target gNB) and perform the Path Update procedure by sending E-RAB Modification Indication message to SUT MME as defined in Section 10.5.1 in 3GPP TS 37.340.

Available in MME nodal when DC Option is 3x or 3a.

If it's checked, the Master GNB Hold Time percent is enabled except for Command Mode / Sequencer test activity. Range : 5 to 95 , default :50

A Secondary gNB User Node becomes available in the network devices.

If this checkbox is checked, the Dual Connectivity Hold Time (ms) shall be 0 or bigger than 100ms. 0: means always keeps dual connectivity. The dual connectivity hold time is still disabled in Command Mode / Sequencer test activity.  If the hold time is bigger than 100ms, it means the dual connectivity can keep in the master gnb node at least 5ms because the Master GNB Hold Time Percent minimum value is 5. 

"Switch gNB on Source eNB" is a new operation in ControlBearer ODC for Command Mode / Sequencer test activity when "Enable Secondary gNB User Node" is checked on S1-MME|NAS.

Tcl Parameter: SecGnbNodeEn

Tcl Parameter: MstGnbNodeHoldTimePct

Trigger SCG Bearer Setup by Data Consumption

Data Volume Threshold

Select to Trigger SCG Bearer Setup by Data Consumption. Per 3GPP 37.340 section 10.2.

Available when Dual Connectivity is enabled in MME nodal. 

When enabled Dual Connectivity Hold Time (ms), DC Option and Secondary Rat Usage Data Report are available for selection in the Dual Connectivity pane.

Enter the Data Volume Threshold and select MB, KB, GB. MB is the default.

Range : 1 to 1000

Default : 10

Tcl Parameter: NasDcTrigScgBearerSetupByDataEn

Tcl Parameter: NasDcTrigScgBearerVolThresh

Tcl Parameter: NasDcTrigScgBearerVolThreshUnit

Include Last Visited TAI

Select the Include Last Visisted TAI checkbox to enable the location information. These are the location and tracking information reported by the UE as last visited during the MME attach process.

Mobile Country Code

Defines the mobile subscriber's country of domicile.

Range: 000 — 999 (leading zeros are retained)

Default: 111

Tcl Parameter: MsMcc

Mobile Network Code

Defines the mobile subscriber's home PLMN.

Range: 000 — 999 (leading zeros are retained)

Default: 222

Tcl Parameters: MsMnc

Tracking Area Code

Defines the last visited location reported by the UE.

Tcl Parameters: MsTac

MME Code

Defines the MME code reported by the UE.

Tcl Parameters: MsMmec

MME Group ID

Defines the MME Group ID reported by the UE.

Tcl Parameters: MsMmegi

Revision Level  provides with the following options.

• GSM phase 1

• GSM Phase 2: Used by mobile stations

• R99+: Used by mobile stations supporting R99 or later versions of the protocol

Tcl Values: 0, 1, and 2.

Tcl Parameter: MsClassmark2RevLevel

RF Power Capability  

Options: Class 1, Class 2, Class 3, Class 4, Class 5

Tcl Values: 0, 1, 2, 3, and 4

Tcl Parameter: MsClassmark2PowerCapability

Options: 0, 1, 2, and 3

Tcl Parameter: MsClassmark2Screening

Select the checkbox to indicate that this option is implemented in the Mobile Station

Tcl Value:  0 (Not implemented), 1 (Implemented)

Tcl Parameter: MsClassmark2ControlledEarlyClsSendEn

Select the checkbox to indicate that PS capability is present.

Tcl Value: 0 (PS cap not present), 1 (PS Cap Present)

Tcl Parameter: MsClassmark2PseudoSync

Tcl Value: 0 (not supported), 1 (supported)

Tcl Parameter: MsClassmark2MtSmsPtToPt

Tcl Value: 0 (no vbs wanted), 1 (vbs cap wanted)

Tcl Parameter: MsClassmark2Vbs

Tcl Value: 0 (No VGCS wanted), 1 (VGCS wanted)

Tcl Parameter: MsClassmark2Vgcs

The tcl values will be 0 for "Does not support", and 1 for "Supports"

Tcl Parameter: MsClassmark2Classmark3

Tcl Value: 0 (not support), 1 (supported)

Tcl Parameter: MsClassmark2FrequencyCapability

Tcl Value: 0 (has a preference for default), 1 (has no preference)

Tcl Parameter: MsClassmark2Ucs2

Tcl Value: 0 (not support), 1 (supported)

Tcl Parameter: MsClassmark2NetInitMoCmConnRequest

Tcl Value: 0 (A5/1 available), 1 (A5/1 not available)

Tcl Parameter: MsClassmark2A5_1

Tcl Value: 0 (not available), 1 (available)

Tcl Parameter: MsClassmark2A5_2

Tcl Value: 0 (not available), 1 (available)

Tcl Parameter: MsClassmark2A5_3

Tcl Value: 0 (Not supported) 1 (Supported)

Tcl Parameter: MsClassmark2LcsVa

Tcl Value: 0 (does not support), 1 (supports)

Tcl Parameter: MsClassmark2SoLSA

Voice Domain Preferences

Select the Voice Domain Preferences as required.

Tcl Parameter: VoiceDomainPref

Options:

• CS Voice Only (0)
• IMS PS Voice Only (1)
• CS Voice Preferred, IMS PS Voice as Secondary (2)
• IMS PS Voice Preferred, CS Voice as Secondary (3)

UE Usage Setting

Select UE Usage Setting for the selected Voice Domain Preferences as required.

Tcl Parameter: UeUsageSetting

Options: Voice Centric (0); Data Centric (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: QosDetail

The QOS Class ID indicates the maximum authorized QOS class that may be defined for each NAS Transport messages. Enter the required QOS Class ID and define the associated transport rate. 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 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.

Valid Options: 1 - 255

Tcl Parameter:

Range: 1 - 15

Default: 1

Tcl Parameter: QosArpValue_1

Tcl Parameter:

Tcl Parameter:

Tcl Parameter:

Guaranteed Bit Rate Downlink

Tcl Parameter:

Tcl Parameter:

Tcl Parameter:

Tcl Parameter:

Tcl Parameter:

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

Range : 0 to 255

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

Tcl Parameter:

Select Summary or Individual APN assignment.

If individual is selected, each default bearer is associated with each APNs in the APN assignments in the same order as in Bearer Quality of Service.

Available on MME Nodal test case. 

Enable to support an empty APN for regular attach and emergency attach.

Tcl Parameter: NasEmptyApnEn_0

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, limited by the number of PDP contexts)

Default: 1

Tcl Parameter: NasApnTotalApns_0

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

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

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.

Tcl Parameter: NasApnNumSpecifiedApns_0

Select Operator Specific Use to be able to capture the Container ID and Value for Protocol Configuration Options for up to 5 Containers.

On MME Nodal, Select Operator Specific Use for support of operator specific PCO in NAS PDN Connectivity Request and ESM Information Response messages based on the GUI configuration. On MME node, the operator specific PCO can be transferred to the network through the S11 and S5/S8 interface with the Create Session Request messages.

Limitation : Currently only one operator specific PCO is supported per PDN session.

Select Number of Containers.

Range : 1 to 5

Enter Container ID. (up to 5 Containers). The IDs must be unique among the number of containers selected per default bearer.

Range : 16 bit value starting with 0x.

Default : 0xFF00

Enter Value. (up to 5 Containers)

Range : up to 64 Hex bytes starting with 0x.

Default : 0x

Note: If you use the default 0x, the constructed PCO will be of zero length and will not include any value field.

Tcl Parameter: NasPcoCustomEn_1_1

Tcl Parameter: NasCustomPcoNum_1

Tcl Parameter: NasCustomPcoId_1_1

Tcl Parameter: NasCustomPcoValue_1_1

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

Select to enter the Rate Control in minutes per APN.

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

Tcl Parameter: NasNbIotApnRateEx_1

Bearer Modification

The Bearer Modification pane allows you to specify  QoS parameters for an EPS bearer context (Bearer Quality of Service)

The Bearer Modification checkbox is available only when the Test Activity is Capacity or Session Loading Test and when you select the UE Intiates Dedicated Bearers checkbox on the MME Nodal Test Configuration tab (which in turn is enabled only when Maximum Bearers per Subscriber is greater than 2 on Mobile Subscriber pane).

Select the Bearer Modification checkbox to enter delay time, TFT Settings, and QoS IE for support UE initiated bearer modification.

Value: True/False

Default: False

Tcl Parameter: BearerModEn

Delay Time

The number of seconds to delay a bearer modification.

Range: 1 — 10000

Default: 60

TFT Settings

Click the TFT Settings button  to enter the relevant parameter values.

Include QoS IE

Select the Include QOS IE checkbox to enable the Bearer Quality of Service Modification pane for MME initiated modification.

Value: True/False

Tcl Parameter: IncModQos

Bearer Quality of Service pane

Select as required:

• Summary to use the same QoS IE for all bearer contexts
• Individual to define different QoS IEs for each context

The number of Bearer QoS tabs displayed depends on the number of Dedicated Bearers per Default you selected on the Mobile Subscriber pane of the Test Configuration tab.

Enter the Uplink and downlink rate as required. (See Bearer Quality of Service).

Integrity Key

Select to use this as Integrity Key after Security Mode Procedure. This is a licensed feature.

Enter a 16 byte Hex string starting with "0x".

Tcl Parameter: IntegrityKeyEn

Tcl Parameter: IntegrityKey

Supports Extended Periodic Timer T3412

Select to enable T3412 Extended Value (s). Per 3GPP 24.008 [13] Section 10.5.1.15.

If the UE supports PSM and requests the use of PSM, then the UE shall include the T3324 value IE with a requested timer value in the ATTACH REQUEST message. When the UE includes the T3324 value IE and the UE indicates support for extended periodic timer value in the MS network feature support IE, it may also include the T3412 extended value IE to request a particular T3412 value to be allocated.

The MME may include T3412 extended value IE in the ATTACH ACCEPT message only if the UE indicates support of the extended periodic timer T3412 in the MS network feature support IE in the ATTACH REQUEST message.

Tcl Parameter: NasT3412En

Initial Power Saving (t3324)

Select to enable Initial Power Saving.

Range: 0 to 11660.

Default: 20

Tcl Parameter: InitPwrSavingEn

Tcl Parameter: InitPwrSaving

Initial eDRX

Select to enable eDRX (extended Idle Mode Discontinuous Reception).

The eDRX Parameter consists of two bytes.

• The MSB specified how long the paging window is (PTW- see table below).
• The LSB byte is the closed window time during which no Page messages should be sent (eDRX value - see table below).
• The combination of these two values determines when the MME will attempt to page the UE.

Default: "0x11". - See the breakdown below. Valid values are : 0x00 to (0xff or 0xFF) not case sensitive.

If using the default value of "0x11" for WB-S1, per the tables below, the PTW (value of 1) = 2, 56 seconds and the eDRX (value or 1) = 10, 24 Seconds.

If using the default value of "0x11" for NB-S1, per the tables below, the PTW (value of 1) = 5, 12 seconds and the eDRX (value or 1) = 20, 48 Seconds. (See Note 5 below)

• The "0x" zero followed by lowercase x , denotes Hex Value (cannot change or delete).   
• The first value after the x,  corresponds to Paging Time Window (PTW)  - Octet 3 (Bit 8 to 5).  (see table below) Enter 0-9, or A to F
• The second value after the x,  corresponds to eDRX value - Octet 3 (Bit 4 to 1). (see table below) Enter 0-9, or A to F
• Tables below are in Binary, you must convert to Hex to enter value in GUI. For example, to select a paging time window length of 17, 92 seconds in WB-S1 mode and an S1 mode eDRX value of 655,36 seconds, you would enter 0xDB.

The PTW Value can be applied to WB-S1 mode (WideBand-IoT) and to NB-S1 mode (NarrowBand-IoT).

Tcl Parameter: InitEDrxEn

Tcl Parameter: InitEDrx

T3412 Extended Value (s)

Available if both Supports Extended Periodic Timer T3412 and Initial Power Saving are enabled in MME Nodal Test Case. This timer controls how frequently the tracking area update request is sent while in Power Saving Mode in the MME Nodal Test Case.

The "T3412 extended value" IE has higher priority than "T3412 value" IE.

In MME Node TC, the T3412 Extended Value timer is available to select when Nas Version is 12.10.0 or higher.  The T3412 Extended Value in MME node is based on Spec TS 24.008 10.5.7.4a GPRS Timer).

Range: 2 to 35712000

Default: 40

Tcl Parameter: NasT3412ExValueEn

Tcl Parameter: NasT3412ExValue

eDRX Reference Time

Available if Initial eDRX is enabled in MME Nodal Test Case. Always available in MME Node.

Reference Time - UTC widget available to enter date and time. MME and eNodeB must agree on starting time. The UE, eNodeB and MME should be synchronized. The minimum is set to the Unix Epoch 1970-01-01 00:00:00.  This is the minimum calendar date. Manually entered 'seconds' values below the Unix Epoch 2208988800 are not supported.

Default: 2000-01-01 00:00:00

Tcl Parameter: NasEdrxRefTime

eDRX - Paging Buffering Time (ms)

Available if Initial eDRX is enabled in MME Nodal Test Case. Denotes the eNodeB buffering time used for receiving paging until it syncs up with the UE.

Paging Buffering Time - Enable for support of Loose Hyper SFN Timing per 3GPP. The Paging Hyperframe (PH) calculations are carried out in accordance with 3GPP TS 36.304 V13.2.0.

Range: 0 to 4294967295

Default: 500

Tcl Parameter: NasEdrxPageBuffTime

eDRX - Paging Ahead Time (ms)

Always available in MME Node Test Case. MME may send paging a little bit ahead of Power Window Time (PWT) to accommodate for processing delays.

Paging Ahead Time - Enable for support of Loose Hyper SFN Timing per 3GPP. The Paging Hyperframe (PH) calculations are carried out in accordance with 3GPP TS 36.304 V13.2.0.

Range: 0 to 4294967295

Default: 0

Tcl Parameter: NasEdrxPageAheadTime

Generate UE Hashed ID From

Always available in MME Node Test Case. Available if Initial eDRX is enabled in MME Nodal Test Case. Select to generate the Hashed ID from IMSI or s-TMSI.

Examples of Hashed ID Calculations for IMSI and s-TMSI:

IMSI calculation based on: 3GPP 36.304 V13.2.0 (2016-06)->7.3:

10 most significant bits of IMSI, % 1024; for IMSI = 310150123456789, the UE_ID_H will be 277.

s-TMSI Calculation based on: 36.304 V13.5.0 (2017-03)->7.3:

For b31~b0 of s-TMSI = 0x12341234, Hashed_ID is 0x259dd322,

10 most significant bits of hashed id of b31~b0 of s-TMSI if is monitored on PDCCH or MPDCCH (WB), % 1024; UE_ID_H = 802

or 12 most significant bits of hashed id of b31~b0 of s-TMSI if is monitored on NPDCCH (NB), % 4096; UE_ID_H = 802

Options: IMSI, s-TMSI

Default: s-TMSI

Tcl Parameter: NasEdrxUeldFrom

Enable EMM Information

Select for sending EMM Information message after UE is successfully attached to the network. If this option is enabled, MME will send an EMM Information message to UE after MME receives AttachComplete Message from UE.

Spec 3GPP TS 24.301 section 8.2.13 EMM information.

When this option is enabled, at least one of the NITZ parameters should be selected.

Tcl Parameter: NasEmmInfoEn

Enter the EMM Information delay in milliseconds.

If the value is 0, MME will send an EMM Information message to UE without any delay after MME receives AttachComplete Message from UE. If the delay time needs to be configured with a non-zero value, it should be configured shorter than an inactivity time (Idle Entry Time for Idle Mode) at UE/eNB and MME.

Range : 0 to 20000

Default : 0

Tcl Parameter: NasEmmInfoDelayTime

Select at least one of the Network Identity and Time Zone (NITZ) Parameters.

Full name for network - Select to include the "full-length name of the network" in EMM Information and enter the "full-length name of the network". (Refer to 8.2.13.2/9.9.3.24 in TS24.301 and 10.5.3.5a in TS24.008)

Range : 1 to 127 characters

Default : LandslideEPC

Tcl Parameter: NasEmmInfoNtwFullNameEn

Tcl Parameter: NasEmmInfoNtwFullName

Short name for network - Select to include the "abbreviated name of the network" in EMM Information and enter the "abbreviated name of the network". (Refer to 8.2.13.3/9.9.3.24 in TS24.301 and 10.5.3.5a in TS24.008)

Range : 1 to 127 characters

Default : LSEPC

Tcl Parameter: NasEmmInfoNtwShortNameEn

Tcl Parameter: NasEmmInfoNtwShortName

Local time zone - Select to include the "Local time zone" in EMM Information. (Refer to 8.2.13.4/9.9.3.29 in TS24.301 and 10.5.3.8 in TS24.008). Local time zone information will be from the information of system time of Test Server. Type "timedatctl" on Test Server's terminal for the current system time information to be displayed.

Tcl Parameter: NasEmmInfoNtwLtzEn

Universal Time and Local time zone - Select to include the "Universal time and local time zone" in EMM Information. (Refer to 8.2.13.5/9.9.3.30 in TS24.301 and 10.5.3.9 in TS24.008). Universal time and local time will be from the information of system time of Test Server. Type "timedatctl" on Test Server's terminal for the current system time information to be displayed.

Tcl Parameter: NasEmmInfoNtwUtLtzEn

Network Daylight Saving Time - Select to include the "Network daylight saving time" in EMM Information and for the adjustment for Daylight Saving Time (Refer to 8.2.13.6/9.9.3.6 in TS24.301 and 10.5.3.12 in TS24.008).

Options : No adjustment, +1 hour adjustment, +2 hour adjustment

Tcl Parameter: NasEmmInfoNtwDstTimeEn

Tcl Parameter: NasEmmInfoNtwDstTime

Include Extended Access Restriction

Available when GTPv2 Version >= 15.2.0 in the MME nodal test case when S10 Interface to MME is enabled.

Select to Include Extended Access Restriction Data IE. 

Select to include NRSRNA (NR as Secondary RAT Not Allowed) in the Extended Access Restriction Data IE. Avaialble when GTPv2 version is >= 15.2.0.

Select to include USSRNA () in the Extended Access Restriction Data IE. Avaialble when GTPv2 version is >= 15.2.0.

Select to include NRNA (NR in 5GS Not Allowed) in the Extended Access Restriction Data IE. Avaialble when GTPv2 version is >= 16.5.0.

Select to include NRUSRNA (New Radio Unlicensed as Secondary RAT Not Allowed) in the Extended Access Restriction Data IE. Avaialble when GTPv2 version is >= 16.5.0.

Select to include NRUNA (NR-U in 5GS Not Allowed) in the Extended Access Restriction Data IE. Avaialble when GTPv2 version is >= 16.5.0.

Tcl Parameter: IncExdAccEn

Tcl Parameter: IncExdAccNrsrnaEn

Tcl Parameter: IncExdAccNrnaEn

Tcl Parameter: IncExdAccNrusrnaEn

Tcl Parameter: IncExdAccNrunaEn

Include Core Network Restrictions

Available when GTPv2 Version >= 16.5.0. in the MME nodal test case when S10 Interface to MME is enabled.

Select to Include Core Network Restrictions IE. 

Select Reserved or 5GC Not Allowed in the Core Network Restrictions IE.  

Tcl Parameter: IncCorNwRestEn

Tcl Parameter: IncCorNwRestType

Available when GTPv2 Version >= 16.5.0. in the MME nodal test case when S10 Interface to MME is enabled.

Select to the Include UE Radio Capability ID IE. 

Enter 14 or 20 hex digits in the box provided to include in the UE Radio Capability ID IE.  

Tcl Parameter: IncUeRadCapIdEn

Tcl Parameter: IncUeRadCapId