S1-AP Tab

Version

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

Options: 8.5.1, 8.6.1, 8.7.0, 8.8.0, 8.9.0, 9.4.0, 9.5.0, 9.6.0, 9.7.0, 9.8.0, 10.5.0, 10.6.0, 11.1.0, 11.8.0, 12.6.0, 13.3.0 ,15.0.0 , 15.1.0, 15.4.0 , 15.5.0 (Custom Multiple Choice ValuesCustom Multiple Choice Values)

Also available on the gNB CU Node test case. Only supported version = 15.4.

Default: 13.3.0

Tcl Parameters: S1apVersion

Setup Time

The Setup Time is how long the test will delay before sending the initial S1 Setup Request. This value is only applicable to the Initial Setup Request. If no response is received within the configured Response Time then Landslide will re-transmit the S1 Setup Request.

Tcl Parameters: SetupTime

Response Time

Indicates the length of time (in ms) the Landslide waits for a response to an S1AP request message. By design, Landslide will continue to retry to setup the S1 Link after the timer expires. See note below.  

Range: 1 to 60000

Default: 5000

Tcl Parameters: ResponseTime

UEs Ignore (n) Pages Before Answering

Enter the number of pages to be ignored before answering (on a per UE basis).

Selecting the pages to ignore emulates the scenario where UE is moving between cell towers and not getting every page. This feature allows the MME to perform paging escalation (page known eNodeB, Page TAC area, Page all eNodeBs, etc).

Option: 0 - 254

Default: 0

• Value = 0, all page requests are answered.
• Value = 1, ignore the first paging request for the specified mobile, and respond to the second paging request.
• Value = 2, ignore the first two pages and respond to the third, and so on.

Tcl Parameters: S1apPagesToIgnore

Paging DRX

This is Paging DRX applied to MME Nodal testing only.

Options: 0 - v32, 1 - v64, 2 - v128, 3 - v256

Default: 0 - v32

Tcl Parameters: PagingDrx

NB-IoT Default Paging DRX

This is NB-IoT Default Paging DRX applied to MME Nodal testing only. Available if S1-AP Version >=  13.3.

Options: 0 - v128, 1 - v256, 2 - v512, 3 - v1024

Default: 0 - v128

Tcl Parameters: NbiotPagingDrx

Include Closed Subscriber Group List

Select the Include Closed Subscriber Group List checkbox to enable the CSG ID parameter. Enter the required CSG ID.

Value: True/False

Enabling a closed subscriber group list indicates a CSG network and allows the user equipment access to the closed subscriber group network as a guest member.

Tcl Parameters:

Range: 0 – 134217727

Default: 0

Increment eNodeB UE ID

Use the checkbox to increase the eNodeB UE ID. T. It is unique within the eNodeB.

Tcl Parameter: IncEnbIdEn

Random Starting eNodeB UE ID

Select to make the first eNodeB UE ID randomly different for each run. The random value is in the range of INTEGER (0 to 16777215).

Tcl Parameter: RandomEnbIdEn

Send S1 Reset After S1 Connected

Select to send S1 Reset only after S1 link is established during MME Nodal testing.

Type: True/False

Default: False

Tcl Parameter: EnbSendS1ResetEn

Enable UE Capability Info Indication

In MME Nodal and Node test cases, the UE Capability Info Indication procedure enables the eNodeB to provide MME with UE capability-related information.

See additional details about UE Capability in IntiCtxtSetupReqMsg below. It is used to control whether to add dummy “UERadioCapabiliy" IE in InitialContextSetupRequest if MME does not have real UECapabilityInfo.

Type: True/False

Default: False

Tcl Parameter: UeCapInfoIndicationEn

Include Coverage Enhancement

Available if S1-AP Version >=  13.3. Select for support of enhanced coverage. Per 3GPP Rel 13. If enabled, the Coverage Enhancement IE will be included in the Context Suspend, Release Complete and UECapabilityInfo Indication messages.

In addition, we will send the "Coverage Enhancement" IE in the Release Request/UE Capability Info Indication message which will then cause the MME to include the "Assistance Data for Paging" IE in the Paging Message sent to the UE.

Type: True/False

Default: False

Tcl Parameter: UeIncCoverageEn

UE Context Release Request Cause

Use to indicate the UE Context Release cause indicated in the release procedure initiated by eNodeB (between eNodeB and MME). The release request initiated may be due to administrative reasons or loss of Radio resources.

Options: User Inactivity (0); Radio Connection With UE Lost (1); CSG Subscription Expiry (2)

Default: User Inactivity

Tcl Parameter: UeContextReleaseReqCause

eNodeB Status Transfer Messages

In MME Nodal TC, select to include eNB Status Transfer message from its emulated eNodeB to the source MME during S1 Handover with or without SGW relocation.

Type: T/F

Default: False

Tcl Parameter: EnbStatusTransferMsgEn

eNodeB GUTI Based MME Selection

Select for MME Pooling with GUTI Reallocation. Per TS 23.401 Section 4.3.10 which indicates that the routing of the signaling traffic from the eNB to the MME pool shall utilize the uniqueness of GUTI within the pool.

Tcl Parameter: EnbGutiBasedMmeSelectionEn

Retrieve UE Info

Select to enable Retrieve UE Info Procedure. Only applies to DMF Protocol = ping, raw, udp, tcp, sctp with limited # of transactions. Retrieve UE Info will be triggered when S1AP Resumes for CPIoT after NAS Idle Mode ( if configured).

On MME Nodal Test Configuration, Send Last Message with RAI should be configured. For UDP/PING/RAW, RAI =2 should be configured; For SCTP/TCP, RAI =1 should be configured becuase of the FIN and Shut-Down control packets of these protocols (the final packet is always uplink). If RAI = 0, the RAI feature is turned off.

Tcl Parameter: RetrieveUeInfoEn

Handover Cancellation Time (ms)

Available in MME Nodal when Sv Interface is selected. Used to configure how quick to send handover cancellation message after starting handover. Time in Mseconds.

Type: T/F

Default: False

Tcl Parameter: S1apHoCancelTimeEn

When Checked the numerical entry field is Enabled.

Range from 0 to Max Int32

Tcl Parameter: S1apHoCancelTime

Do not include Deregistered/Detached/Failed UEs in  'Sessions Not Ready for Handoff' OM

When checked the "Session Not Ready for Handoff" OM will not be pegged if the UE is Deregistered/Detached/Failed (not active). In other words, the TS will not count any UEs that are NAS deregistered (NAS Idle), Detached or Failed (Not in Retry) in the 'Sessions Not Ready for Handoff' measurement.

Default = False (unchecked)

Tcl Parameter: S1apMmeAttOnlyinSessNotRdyCntEn

MME Pooling eNodeB Triggered UE Move

Select for support of eNodeb triggered UE move when MME is not available with MME Pooling. When enabled, Active Mode UE Method become available for selection. Select Tau (default), ReAttach, SR Message or None.

Select to support MME switch when the SCTP link goes down (MME node failure).

Must be enabled for TEST.PROCS support for SCTP communication failure between MME and VM - MME Nodal (SCTP FAILURE) 

Tcl Parameter: MmePoolingEnbTriggeredUeMoveEn

Tcl Parameter: ActiveModeUeMoveMethod

UE Capability in InitCtxtSetupReqMsg

Available in MME Node. UE Capability in IntiCtxtSetupReqMsg is used to control whether to add dummy “UERadioCapabiliy" IE in InitialContextSetupRequest if MME does not have real UECapabilityInfo.

Based on 23.401 5.11.2 UE Radio Capability Handling:

If the UE is performing an Attach procedure or a Tracking Area Update procedure for the "first TAU following GERAN/UTRAN Attach" or for "UE radio capability update", the MME shall delete (or mark as deleted) any UE Radio Capability information that it has stored, and, if the MME sends an S1 interface INITIAL CONTEXT SETUP REQUEST or UE RADIO CAPABILITY MATCH REQUEST message during that procedure, the MME shall not send any UE Radio Capability information to the E-UTRAN in that message. This triggers the E-UTRAN to request the UE Radio Capability from the UE and to upload it to the MME in the S1 interface UE CAPABILITY INFO INDICATION message.

Tcl Parameter: UeCapInInitCtxtSetupReqMsgEn

UE Category

Available in MME Node when S102 Interface is not selected on the MME Node Emulator Configuration tab and when UE Capability in InitCtxtSetupReqMsg is enabled.

This is to ensure the InitialContextSetupRequest message is sent with Category 4 (instead of Category 2), when UEs come out of ECM idle mode and move to ECM connected mode.

Range : 1 to 5

Default : 4

Tcl Parameter: S1apUeCategory

Emulate HeNb-GW Signaling

Available in MME Node when mobility type is None or Intra-MME and S1-AP version >= to 10.5. Enabled this will add GUMMEI in  InitialContextSetupRequest  message sent via HeNB-GW to eNB for signaling emulation, GUMMEI will be used in subsequent X2 handover.

Tcl Parameter: S1apMmeEmulHeNbGwSigEn

Available in MME Node when S1-AP version >= to 8.7.0. When enabled the MME Node will Broadcast Paging messages to all eNodeBs that are connected to it. Otherwise, it only Pages the eNodeB underlying the UE (s) that require paging."

Tcl Parameter: PageEnbTacListEn

Indicate ProSeAuthorizedIE to eNB

Available in MME Node when S1-AP version >= to 12.6. Enable to support Public Safety Proximity Services (ProSe) in the ULR/ULA and IDR/IDA command pairs over S6a.

Tcl Parameter: S1apMmeIndProSeAuthorizedEn

Cell Traffic Trace (MME Node)

S1-AP version must be greater than 10.5 to enable. Three options available - Off (Default), StartTraceMsg and InitCtxSetup/hoRequestMsg

The following become available for input when Cell Traffic Trace is enabled.

Tcl Parameter: CellTrafficTrace

UE Usage Type (MME Node and HSS Node)

S1-AP version must be greater than 13.3 to enable. This is part of the NB-IoT features and it is licensed.

The overall goal of Decor (Dedicated Core Networks TR 23.401) is to have network slicing or different dedicated Cores networks for different devices in the same network.

In DECOR (Dedicated Core Networks TR 23.401) , The "UE Usage type" parameter in TAU/attach makes it to the HSS from the initial MME during ATTACH and TAU. If this Usage type does not match the MME for a given UE, then the HSS tells the initial MME to redirect to a new MME using a Reroute command. Essentially saying to use a different dedicated core network. The initial MME sends "reroute" command back to eNodeB which then sends another attach request to new, now correct MME for the dedicated core network for a given service like NB-IOT and attach and TAU  procedure is normal from there.

Available on HSS Node Emulator Configuration Mobile Subscribers section when S6a Interface is enabled.

In HSS Node, the TDF (Test Data File) allows you to define the UE Usage Type.

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

Range: 0 to 255

Default: 129

Tcl Parameter: UeUsageType

Emulate Handover Preparation Failure (Radio Network Cause)

Available in MME Node TC. Select to send Handover Preparation Failure Message in response to Handover Required Message from eNB. If it is enabled, MME will send Handover Preparation Failure message in response to Handover Required Message from eNB/UE. 

For example,

    UE/eNB is connected to MME -> UE/eNB sends HandoverRequired -> MME sends HandoverPreparationFailure to eNB/UE -> UE/eNB sends HandoverRequired -> MME handles it as normal -> UE/eNB sends HandoverRequired -> MME sends HandoverPreparationFailure to eNB/UE -> UE/eNB sends HandoverRequired -> MME handles it as normal. If eNB/UE keeps triggering handover without being disconnected, it will be toggled.

Cause is the Radio Network Cause value which is included in Handover Preparation Failure Message.

It is the value of enumerated Radio Network Layer Cause defined in 9.2.1.3 Cause - TS 36.413. The default value, 6 is “Failure In Target EPC/eNB Or Target System”.

Range : 0 to 255

Default : 6

Tcl Parameter: S1apMmeHoPrepFailEmulEn

Tcl Parameter: S1apMmeHoPrepFailCause

For example,

    UE/eNB is connected to MME -> UE/eNB sends Path Switch Request-> MME sends Path Switch Request Failure to eNB/UE -> UE/eNB sends Path Switch Request -> MME handles it as normal -> UE/eNB sends Path Switch Request-> MME sends Path Switch Request Failure to eNB/UE -> UE/eNB sends Path Switch Request-> MME handles it as normal. If eNB/UE keeps triggering path switch HO without being disconnected, it will be toggled.

Cause is the Radio Network Cause value which is included in Path Switch Request Failure Message.

It is the value of enumerated Radio Network Layer Cause defined in 9.2.1.3 Cause - TS 36.413. The default value, 6 is “Failure In Target EPC/eNB Or Target System”.

Range : 0 to 255

Default : 6

Tcl Parameter: S1apMmePathSwitchReqFailEmulEn

Tcl Parameter: S1apMmePathSwitchReqFailCause

Support Dedicated Core Networks

S1-AP version must be >= 13.3 to enable. Selected to enable Dedicated Core Networks (Decor). The overall goal of Decor (Dedicated Core Networks TR 23.401) is to have network slicing or different dedicated Cores networks for different devices in the same network. This is part of the NB-IoT features and it is licensed.

Tcl Parameter: DedicatedCoreNetworksEn

S1 Release on S1 Reset

When enabled, the ENB/MME will release the S1 connection and switch NAS into Idle Mode (waiting for the next Service Request to re-establish the S1 connection). When not enabled, Landslide will disconnect all established sessions on receiving S1 Reset (and will go into re-attach procedure on connection demand).

Tcl Parameter: S1ReleaseOnS1Reset

Reattach When Paging Using IMSI

Available on MME Nodal test case. Select to Reattach when Paging using IMSI.

Per 3GPP 24.301 Chapter 5.6.2.2.2, the UE should reattach after receiving IMSI Paging.

Tcl Parameter: ReattachPagingUseImsiEn

Available on MME Nodal test case. Select to ignore "NRrestrictedIn5GS" flag in InitialContextSetup and do dual connectivity regardless.

Tcl Parameter: IgnoreNrRestrictionEn

Custom Messages

You can customize Landslide generated messages and or compose your proprietary messages to perform negative testing with invalid values or malformed messages or to add proprietary information. The Custom Message checkbox is available only when S1-AP protocol version is higher than 8.6.1.

The Custom Message checkbox is available only when S1-AP Version = 11.8.0 in MME Node test case. Click here for list of supported messages. 

Message Editor Protocol for MME node is "S1-AP MME", for MME Nodal it is "S1-AP".

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.

Sample for translation rules between ASN.1 syntax and Custom Message configuration:

• If an item is a top-level item and of type SEQUENCE, we need to create a Master IE and add child fields and IEs to it. The "Type" field of the Master IE must be the ProtocolIE-ID value in the ASN.1 definition.

• If an item is of type SEQUENCE and nested, we need to create a Master IE and add child IEs to it. The "Type" field of the IEs must be the ProtocolIE-ID value in the ASN.1 definition.

• If an item is of type CHOICE, we need to create a Master IE and add value field to it. The "Type" of the Master IE must be an index of the selection counted from 1.

• If an item is of type ENUMERATED, we need to create a field which value counted from 0 as the ASN.1 definition.

• If an item is of type value (INTEGER, TBCD-STRING, OCTET STRING, BIT STRING, etc.), we need to create a Master Field and set its value.

And an example for configuring Global-eNB-ID will be like this:

Reference to S1-AP ASN.1 syntaxes of Global-ENB-ID defined in 3GPP 36.413:

    id-Global-ENB-ID ProtocolIE-ID ::= 59

    Global-ENB-ID ::= SEQUENCE {

      pLMNidentity PLMNidentity,

      eNB-ID ENB-ID,

      iE-Extensions ProtocolExtensionContainer { {GlobalENB-ID-ExtIEs} } OPTIONAL,

      ...

    }

    PLMNidentity ::= TBCD-STRING

    ENB-ID ::= CHOICE {

      macroENB-ID BIT STRING (SIZE(20)),

      homeENB-ID BIT STRING (SIZE(28)),

      ...

    }

1. Global-ENB-ID is of type SEQUENCE, create a Master IE and set its type to ProtocolIE-ID of Global-ENB-ID (59).

2. pLMNidentity is of type TBCD-STRING and that is a value, create a Master Field and set its value, then nest it to Global-ENB-ID Master IE.

3. eNB-ID is of type CHOICE, create a Master IE and and set its type to 1 for macroENB-ID or 2 for homeENB-ID. Then nest it to Global-ENB-ID Master IE.

4. homeENB-ID is of type BIT STRING, create a Master Field and set its value, then nest it to eNB-ID Master IE.

  The resulting configuration will be as follows:

    Master IE {Name=Global-eNB-ID, Type=59}

      Master Field {Name=PLMN-ID, Value=<PLMN>}

      Master IE {Name=eNB-ID(Home), Type=2}

        Master Field {Name=HeNB-ID-Value, Value=<HeNB-ID>}

MME Node supports the following messages for customization:

Tcl Parameter: S1apCustomMsgEn

Tcl Parameter: S1apCustomMsg

Apply Test Data File to S1-AP

• In MME Nodal test case, the TDF allows you to define multiple range of Cell IDs.
• See also MME TDF Files.

• In MME Node test case, see MME Node - Provisioning TDF.

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

Tcl Parameter: S1apCfgFileEn

Enable eNodeB Configuration Updates

Select to enable/configure parameters to be included in the eNodeB Configuration Update message.

Default False

Tcl Parameter: EnbUpdateConfigEn

• See also MME TDF Files.

Update eNodeB Name

Seelct to include eNodeB name in the Configuration Update message.

Tcl Parameter: EnbNameUpdateEn

Enter the appropriate eNodeB Name.

Default:  ENB.spirent.com

Tcl Parameter: EnbName2

Update CSG ID List

Select to include CSG Id List in the eNodeB Configuration Update message.

Tcl Parameter: EnbCsgIdUpdateEn

Enter the appropriate CSG-ID value.

Option: 0 - 134217727

Default: 134217727

Tcl Parameter: CsgId2

Update Default Paging DRX

Select to include Paging DRX.

Tcl Parameter: EnbPagingDrxUpdateEn

Select Paging DRX to be included in the Configuration Update message.

Options: v32, v64, v128, v256

Tcl Parameter: PagingDrx2

Update NB-IoT Default Paging DRX

Select to include the NB-IoT Default Paging in the eNodeB Configuration Update message. Available if S1-AP Version >=  13.3.

Options: 0 - v128, 1 - v256, 2 - v512, 3 - v1024

Default: 0 - v128

Tcl Parameter: EnbNbiotPagingDrxUpdateEn

Tcl Parameters: NbiotPagingDrx2

Update Supported TAs

Select to include supported TAs in the Configuration update message.

Tcl Parameter: EnbSupportedTAUpdateEn

Update Interval (ms)

Indicates the interval between consecutive eNodeB Configuration updates.

Option: 10000 and 60,000

Default: 30000

Tcl Parameter: EnbUpdateConfigTime

Retry Interval (ms)

Indicates the eNodeB Update Configuration Retry Time (in msec). That is, the Time to wait before making a second retry attempt to send eNodeB Configuration update.

Option: 1 and 60,000

Default: 15000

Tcl Parameter: EnbUpdateConfigRetryTime

MME Node

Simulate eNobeB Configuration Update Failure

During MME Node test case, select to simulate a failure condition as a response to the eNodeB Configuration Update.

Type: True/False

Default: False

Tcl Parameter: SimulateEnbConfigFailureEn

eNodeB Wait Time After Failure (s)

Indicates the time/duration the eNodeB needs to wait before sending the next eNodeB Configuration Update after a failure,

This parameter is available only when Simulate eNobeB Configuration Update Failure is enabled.

Options: Not Included, 1, 2, 5, 10, 20, 60.

Tcl Parameter: EnbUpdateConfigWaitTime

Number of Configurations

Select the number of configuration profiles for eNodeB Configuration transfers. 

eNB Configuration Transfer per 3GPP TS 36.413 version 15.5.0/section 8.15 (packet 259):

The procedure is initiated with an ENB CONFIGURATION TRANSFER message sent from the eNB to the MME. If the MME receives the SON Configuration Transfer IE, it shall transparently transfer the SON Configuration TransferIE towards the eNB indicated in the Target eNB-ID IE which is included in the SON Configuration Transfer IE. If the MME receives the EN-DC ((E-UTRA-NR Dual Connectivity ) SON Configuration Transfer IE, it shall transparently transfer the EN-DC SON Configuration Transfer IE either towards the eNB indicated in the Target eNB-ID IE or towards an eNB connected to the en-gNB indicated in the Target en-gNB-ID IE which is included in the EN-DC (E-UTRA-NR Dual Connectivity ) SON Configuration Transfer IE. The EN-DC SON Configuration Transfer IE may also contain, if available,

the Target eNB ID IE, - the Associated TAI IE, - the Broadcast 5GS TAI IE, for purposes described in TS 36.300 [14].

MME Configuration Transfer per 3GPP TS 36.413 version 15.5.0/section 8.16 (packet 261):

The purpose of the MME Configuration Transfer procedure is to transfer RAN configuration information from the MME to the eNB in unacknowledged mode. This procedure uses non-UE associated signalling.

The procedure is initiated with an MME CONFIGURATION TRANSFER message sent from the MME to the eNB. If the eNB receives, in the SON Configuration Transfer IE or the EN-DC (E-UTRA-NR Dual Connectivity ) SON Configuration Transfer IE, the SON Information IE containing the SON Information Request IE, it may transfer back the requested information either towards the eNB indicated in the Source eNB-ID IE of the SON Configuration Transfer IE or towards an eNB connected to the en-gNB indicated in the Source en-gNB-ID IE of the EN-DC SON Configuration Transfer IE by initiating the eNB Configuration Transfer procedure. If the X2 TNL Configuration Info IE contains the eNB Indirect X2 Transport Layer Addresses IE, the eNB may use it for the X2 TNL establishment, and may transfer back the received eNB Indirect X2 Transport Layer Addresses towards the eNB indicated inthe Source eNB-ID IE of the SON Configuration Transfer IE by initiating the eNB Configuration Transfer procedure or towards the eNB connected to the en-gNB indicated inthe Source en-gNB-ID IE of the EN-DC SON Configuration Transfer IE by initiating the eNB Configuration Transfer procedure.

Call Flow:

Range : 1 to 10

Default : 1

Tcl Parameter: EnbCfgTransferProfileNum

SON Configuration Transfer

or

EN-DC SON Configuration Transfer

Enter the following for SON Configuration Transfer or EN-DC (E-UTRA-NR Dual Connectivity) SON Configuration Transfer (Available when S1-AP version >= 15.5.0).

Tcl Parameter: EnDcSonCfgTransferEn_1

Warning Message Transmission Procedure

In MME Nodal Test Case, the Warning Message Transmission Procedure is available for configuration only when Version greater than 9.5.0 and supports receiving/responding to warning messages.

Broadcast Completed Area List IE

Default value: Not Included

Tcl Parameter: InclBroadCastCompletedInWarningRsp

Broadcast Cancelled Area List IE

Default value: Not Included

Tcl Parameter: InclBroadCastCanceledInKillRsp

Select to activate PWS Failure indication after warning message. The purpose of PWS Failure Indication procedure is to inform the MME that PWS information for some of all cells of eNB are available for reloading from the CBC if needed. The procedure uses non UE-associated signaling.

The eNB initiates the procedure by sending a PWS FAILURE INDICATION message to the MME. On receipt of a PWS FAILURE INDICATION message, the MME shall act as defined in TS 23.007 (38).

If the Emergency Area ID is available, the eNB shall include it in the Emergency Area ID List for Restart IE.

Enter Delay Time in seconds before sending the message.

Range: 0 to 9 seconds

Default : 1

Tcl Parameter: PwsFailIndAfterWarningEn

Tcl Parameter: PwsFailIndAfterWarningTime

Enable PWS Restart Indication After Warning Message

Select to activate PWS Restart indication after warning message. The purpose of PWS Restart Indication procedure is to inform the MME that PWS information for some of all cells of eNB are available for reloading from the CBC if needed. The procedure uses non UE-associated signaling.

The eNB initiates the procedure by sending a PWS RESTART INDICATION message to the MME. On receipt of a PWS RESTART INDICATION message, the MME shall act as defined in TS 23.007 (38).

If the Emergency Area ID is available, the eNB shall include it in the Emergency Area ID List for Restart IE.

Enter Delay Time in seconds before sending the message.

Range: 0 to 9 seconds

Default : 1

Tcl Parameter: PwsRestartIndAfterWarningEn

Tcl Parameter: PwsRestartIndAfterWarningTime

Enable PWS Restart Indication After Kill Message

Select to activate PWS Restart indication after Kill message. The purpose of PWS Restart Indication procedure is to inform the MME that PWS information for some of all cells of eNB are available for reloading from the CBC if needed. The procedure uses non UE-associated signaling.

The eNB initiates the procedure by sending a PWS RESTART INDICATION message to the MME. On receipt of a PWS RESTART INDICATION message, the MME shall act as defined in TS 23.007 (38).

If the Emergency Area ID is available, the eNB shall include it in the Emergency Area ID List for Restart IE.

Enter Delay Time in seconds before sending the message.

Range: 0 to 9 seconds

Default : 1

Tcl Parameter: PwsRestartIndAfterKillEn

Tcl Parameter: PwsRestartIndAfterKillTime

Include EAI List For Restart IE

Available if either Enable PWS Restart Indication After Warning Message or Enable PWS Restart Indication After Kill Message are enabled. Select to include EAI (Emergency Area ID) list for Restart IE. Emergency Area ID becomes available for input.

Enter 3 digit EAI (Emergency Area ID). Default = 123

Tcl Parameter: IncEaiListInPwsRestartIndEn

Tcl Parameter: PwsEmergencyAreaIdValue

With this flag is enabled, Landslide will still respond to the WEA S1AP messages but will not report the messages to info_report hence No WEA records in TEST.PROCS. 

This is tied to the VisionWorks TEST.PROCS license key.

Tcl Parameter: PwsVwDoNotReportWeaStatesEn

CDMA 2000 Settings

In MME Nodal Test Case, the CDMA 2000 Settings is available for configuration when Inter Technology test activity and Handoff Protocol 1XRTT are selected.  

Sector ID

Used to Identify an HRPD Access Network.

Default value: Not Included

Tcl Parameter: S1apCdmaSectorId

Cell Traffic Trace (MME Nodal)

RIM Settings (MME Nodal)

MME Node

Warning Message Transmission Procedure

In MME Node Test Case, the Warning Message Transmission Procedure is available for configuration only when Version greater than 9.5.0 and supports receiving/responding to warning messages.

Enable Warning Message Transmission Procedure

Select to Enable Warning Message Transmission Procedure and enter the associated time.

Type: True/False

Default: False

Tcl Parameter:  WarningKillMessagingEn

Warning Request Time

Indicates the time interval the MME waits before sending the first Write-Replace Warning Request after establishment, and also any subsequent Write-Replace Warning Request after the Kill operation.

Option: 10 - 60 seconds

Default: 45

Tcl Parameter:  WarningRequestTime

Kill Request Time

Indicates the time interval the MME waits before sending the Kill Request after Write-Replace Warning Response is received.

Option: 10 - 60 seconds

Default: 30,

Tcl Parameter:  KillRequestTime

Warning Messaging Retry Time

Indicates the retry interval for each Write-Replace Warning Request and Kill Request messages.

Option: 10 - 60 seconds

Default: 10,

Tcl Parameter:  WarningMessagingRetryTime

UE Aggregate Maximum Bit Rate Information

In MME Node test case, select Enable UE AMBR Information to enter the Downlink and Uplink rates.

UE Aggregate maximum bit rate is the maximum allowed total non-GBR throughput among all APN to a specific UE.

MME Configuration Update Information

Not admitted E-RAB Ids by Target eNodeB

Available when Test Activity is Inter-MME Mobility or Session Loading with Inter-MME Mobility Type. Handoff type must be set to S1 and the S10 interface must not be selected.

Used to simulate a partially successful S1-AP handover with multiple E-RABs.

Select to enter list of E-RAB Ids not admitted by Target eNodeB.

Option: 5 to 15 or list of numbers between and including 5 and 15. Ex. '5, 10, 12,14'

Tcl Parameter:  FailedErabIdListEn

Tcl Parameter:  FailedErabIdList

Enable Partial S1-Reset

Select for a Partial S1-Reset. Enter Starting and Ending IMSI for range to reset. This function is available for all test activities as long as you have the license for Command Mode/ Sequencer. A command button appears, when the test case is running, that allow you to execute the S1 Reset commands. This is a licensed feature.

Tcl Parameter:  PartialS1ResetEn

Starting IMSI

Ending IMSI

Available when Enable Partial S1-Reset is selected.

Enter Valid Starting and Ending IMSI for range to reset.

Tcl Parameter:  StartingImsi

Tcl Parameter:  EndingImsi

Cause

Select a Cause IE that will be used in the E-RAB Release message. Per 3GPP 36.413 Section 9.2.1.3

Options : Radio Network Layer Cause, Transport Layer Cause , NAS Cause, Protocol Cause, Miscellaneous Cause (default)

Tcl Parameter:  CauseGroup

Specified Cause

Select a Specified Cause IE which is a sub-type of the Cause IE. code. Per 3GPP 36.413 Section 9.2.1.3

See table below for supported Specified Cause values per Cause.

Tcl Parameter:  SpecifiedCause

ue-Category

ue-CategoryDL

ce-ModeA

ce-ModeB

Available on MME Nodal when Version > = 13.3.0 and Include Coverage Enhancement is enabled. All checkboxes (ue-Category, ue-CategoryDl, ce-ModeA, ce-ModeB) are automatically enabled. 

Select for CAT-M1 UE indicator and the ability to select CE mode. The Coverage Extension (CE) Mode is used by the MME to determine how long the S1-AP-related time-out values, the paging timer, and the NAS timers need to be extended, during UE signaling procedures.

If it is not NB-IoT Rat type, the selection of "ue-Category", "ue-CategoryDL", "ce-ModeA", "ce-ModeB" control the related field of UERadioCapabilityForPaging: in UECapabilityInfoIndication message. Optional IE LTE-M-indication of UECapabilityInfoIndication, will be included when ether "ue-CategoryDL", "ce-ModeA"  or "ce-ModeB" are enabled. Optional IE LTE-M-Indication of UECapabilityInfoIndication, is supported only when S1-Ap version >= 15.4.

Spec References: 3GPP TS 36.413 V15.7.0 (2019-09), 3GPP TS 24.301 V15.7.0 (2019-09). CAT-M1 UE indicator (3GPP TS 36.413 Clause 9.2.1.27) There are two CE modes for CAT-M1 UEs when using Coverage Extension for LTE; namely, CE Mode A and CE Mode B. When a UE supports CE Mode B, the CE-mode-B Support Indicator IE (3GPP TS 36.413 Clause 9.2.1.118) is sent in the S1 Initial UE message from the eNodeB to the MME, or in the Handover Request Acknowledge message from the target eNodeB to the MME. The MME detects if a UE supports CE Mode A by reading the UE Radio Capability IE (3GPP TS 36.413 Clause 9.2.1.27) sent from the eNodeB to the MME.

Tcl Parameter:  UeCategoryEn

Tcl Parameter:  UeCategoryDlEn

Tcl Parameter:  CoverageExtModeAEn

Tcl Parameter:  CoverageExtModeBEn

Initialize Context Setup Request Message

Select to include the Handover Restriction List in the Initialize Context Setup Request Message IE.

When selected, Core Network Type Restrictions and NR Restriction In 5GS become available to select.

Tcl Parameter:  HoResListInInitSetupMsgEn

Downlink NAS Transport Message

Select to include the Handover Restriction List in the Downlink NAS Transport Message IE.

When selected, Core Network Type Restrictions and NR Restriction In 5GS become available to select.

Tcl Parameter:  HoResListInDownlinkMsgEn

Core Network Type Restrictions

Select to include Core Network Type Restrictions information as specified in TS 23.501 [46].

Tcl Parameter:  CnTypeResEn

NR Restriction In 5GS

Select to include Restriction to use NR when the NR connects to 5GS.

Tcl Parameter:  NrResIn5GsEn