Nas 5G Mm

NAS-5G Version (24.501)

 Select the NAS-5G MM Version. 24.501 is the Spec ID.

 Options: 15.0.0/Jun2018, 15.1.0/Sep2018, 15.2.0/Dec2018, 15.2.1/Jan2019, 15.4.0/Jun2019 , 16.5.0/Jul2020, 17.12.0/Sep2023 (default)

 Tcl Parameter: AmfNas5gMmVersion

 Tcl Parameter: UeNas5gMmVersion

Security Version (33.501)

Select the Security Version. 33.501 is the Spec ID.

Added support for NAS security version 15.6.0 so that zero value NAS COUNTs will no longer lead to Authentication Responses with zero value sequence numbers after handover from 5G to 4G.

Options: 15.1.0/Jun2018, 15.5.0/Jun2019, 15.6.0/Sep2019, 16.5.0/Dec2020, 17.11.0/Sep2023 (default) 

Tcl Parameter: AmfNas5gMmSecurityVersion

Tcl Parameter: UeNas5gMmSecurityVersion

Starting IMEI

Enter the starting IMSI. Also available on UE Subtab in SMF Nodal test case.

Range: 14 digits

Tcl Parameter: UeNas5gMmImei

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

Software Version

Enter the software version. Software Version Number (SVN) identifies the software version number of the mobile equipment.

If this option is enabled, PEI (Permanent Equipment Identifier) will be composed as IMEISV format.

Also available on UE Subtab in SMF Nodal test case.

Must be two digits long.

Default: 00

Tcl Parameter: UeNas5gMmSwVerEn

Tcl Parameter: UeNas5gMmSwVer

Available in AMF Nodal TC when Test Activity is set to "Capacity" or "Session Loading" when NGAP Version (38.413) >= 15.1.0.

The UE RRC state can be manipulated by provisioning the "RRC Inactive Time", "Idle Entry Time for 5G (R)AN Node" and "Active Entry Time" on the NAS-5G | MM tab. Per 38.413, if the received UE Context Modification Request contains the RRC Inactive Transition Report Request IE, the current RRC State (connected or inactive) shall be reported in the UE Context Modification Response. In addition, in the RRC Inactive Transition Report Request IE,

• If the report type is set to Subsequent, the UE will send the RRC Inactive Transition Report each time UE enters or exits RRC inactive mode until UE enters RRC idle mode or when a Cancel report is received.
• If the report type is set to Single and the UE is currently in RRC inactive mode, the UE will send an additional RRC Inactive Transition Report when UE exits RRC inactive mode.
• If the report type is set to Cancel, RRC reporting will be stopped.

Range: 0, or 1000 <= value <= 4294967295

Default: 1500

Tcl Parameter: UeNas5gMmRrcInactiveTime

Idle Entry Time for 5G (R)AN Node (ms)

Available in AMF Nodal TC , gNB CU SA Nodal and available on UE Subtab in SMF Nodal test case. Enter Idle Entry Time in milliseconds. Used in support of Idle Mode / Service Request scenario.

Supports Peak RRC Active to Idle Mode Transition Rate in 5G CU SA Nodal & Node test cases.

Fireball mode is not supported.

Range: 0 (disabled), or 1000 <= value <= 4294967295

Default: 0 (disabled)

Tcl Parameter: UeNas5gMmIdleEntryTime

Plain 5G NAS Messages

Select to disable Ciphering / Integrity for all NAS 5G Messages. Available in AMF Nodal test case. Per 24.501.

Security header type as Plain 5G NAS Message, not security protected.

Tcl Parameter: UeNas5gMmPlainMsgsEn

Available in AMF Nodal. 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). AMF Nodal initiates the UE Triggered Service Request procedure when the timer expires. If the value of the timer is set to 0, AMF Nodal doesn’t initiate the UE Triggered Service Request procedure at all.Time in milliseconds.

Reference : TS 23.501, 23.502. 24.501

Range : 0 to 4294967295

Default : 0 

Tcl Parameter: UeNas5gMmActiveEntryTime

Initial Registration with Follow On

Select to set Initial Registration with Follow On. Per 3GPP TS 23.502, Figure 4.2.2.2.2-1.

See additional details about Registration Only on AMF Nodal test case.

Table 9.11.3.7.1: 5GS registration type information element

Tcl Parameter: UeNas5gMmRegWithFollowOnEn

Available on AMF Nodal. Select Follow On option for Periodic Registration.

Options : Auto, Always On, Always Off

Tcl Parameter: UeNas5gMmPeriodicRegFollowOn

Default DNN

Enter the default DNN (Data Network Name) which the AMF will use when it doesn't receive the DNN from the UE during PDU Session Establishment procedure. Not available on AMF Node test case when SMF Emulation is enabled.

Tcl Parameter: AmfNas5gMmDefaultDataNtwkName

De-registration Type

Available in AMF Nodal TC. Select the de-registration type.

Options: Normal de-registration (default), Switch off

Available in AMF Node TC. Select the de-registration type.

Options: Re-registration not required (default), Re-registration Required

Tcl Parameter: UeNas5gMmDeRegTypeSwitchOff

Tcl Parameter: AmfNas5gMmDeregistrationType

Select to enter the deregistration cause.

Range : 0 to 255

Default : 10

Tcl Parameter: AmfNas5gMmDeregistrationCauseEn

Tcl Parameter: AmfNas5gMmDeregistrationCause

Select to not include the PDU session reactivation result error cause IE in the Service/Registration Accept message. Available in AMF Node test case.

Spec Reference : TS24.501 (Non-Access-Stratum (NAS) Protocol for 5GS), section 5.5.1.3, 5.6.1

Tcl Parameter: AmfNas5gMmNoReactResultCauseEn

Use Emergency registration if first Pdu is Emergency Pdu

Select for Emergency registration to be triggered (Per 23.502 4.2.2.2.2). This is the case where a UE needs to register with the network to receive Emergency services. The UE initiate the Registration procedure using Registration Type = Emergency.

Set the Emergency Flag on the DNN Panel of the Nas 5G SM Tab.

Tcl Parameter: UeMm5gEmergRegFstEmergPduEn

Emergency Registration with IMEI SV

Select to perform Emergency Registration with IMEI SV (Software Version). It is a 16-digit number with the IMEI and an additional software Version Number. Use in conjunction with Use Emergency registration if first pdu is Emergency pdu.

Tcl Parameter: UeMm5gEmergRegiWithImeiSv

Available in AMF Nodal test case. Select to always use the Subscription Concealed Identifier (SUCI), which is a privacy preserving identifier containing the concealed SUPI, in the Registration Request. 

Without this flag enabled, the first Registration Request uses SUCI,  then the second Registration Request  uses 5G GUTI.

Tcl Parameter: UeNas5gMmAlwaysSuciRegEn

Available in AMF Nodal test case.

In the handover test (5g<->5g or 5g<->LTE), 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 registration after de-registration (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 : 

1) Test Activity is “Intra-AMF Mobility or Inter-AMF Mobility”, and N3IWF is disabled.

   2) Test Activity is “Inter Technology Mobility”, and Handoff Protocol is “LTE, and N3IWF is disabled.

   3) Test Activity is “Command Mode or Sequencer”, and Handoff Protocol is “None or LTE”, and N3IWF is disabled.

Limitations:

• The graceful termination at 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 5G side.

Tcl Parameter: UeNas5gMmRestartUeNotReadyForHoEn

Available in AMF Nodal test case. Gracefully stop applications prior to de-registration gives applications time for properly disconnecting with their peers;  and that proper disconnect will help applications to continue working their peers in subsequent restarts (session-loading).

• When checkbox is checked, UE attempts to stop applications and wait for a maximum of 5 seconds for applications to be completed before sending de-registration requests to network.
• When checkbox is unchecked or the wait timer expires, UE will force stopping applications and immediately send de-registration requests to network.

Tcl Parameter: UeNas5gMmGracefulStopEn

Available in AMF Nodal test case. Enter the Delay time (ms) used for triggering Service Request.

Range : 0 to 500 milliseconds

Default : 100

Tcl Parameter: UeNas5gMmDelaySrvRegTime

Available in AMF Nodal test case. Select to allow all configured UEs to attempt Registration Request message to be sent out to a connected AMF, regardless if first AMF is successful or not. If this checkbox is not selected, the Registration Request message will not be sent out if pre-configured AMF is not successfully connected to gNB.

Tcl Parameter: UeNas5gMmInitialRegToConnAmfEn

Authentication and Security Mode

Available in AMF Node. Select to enable input on the Authentication and Security Mode panes.

Tcl Parameter: AmfNas5gMmAuthSecModeEn

Available in AMF Node. With Persistent SUPI enabled, an MM session on AMF side will be reserved for each UE when the registration request is received for the first time. This session will not be released when it goes to idle state, for example, due to de-registration, registration reject or service reject, etc.

Spec reference : 3GPP TS 24.501 - Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS)

Pros: UE handling on AMF side resembles real life better. May reduce network traffic by skipping authentication and security mode when subsequent UE registration requests are integrity protected and the security contexts can be verified on AMF side.

Cons: The AMF may need more memory in handling UE registrations in certain cases because once an MM session is dedicated to an UE, it cannot be reused by another even if the current UE de-registers or MM goes to idle.

Tcl Parameter: AmfNas5gMmPersisSupiEn

Available in AMF Nodal test case. Select for registration with 5G GUTI (Globally Unique Temporary UE Identity). Scenarios in section 5.5.1.2.2 of 3GPP 24.501 specification are supported by enabling this checkbox.

Tcl Parameter: UeNas5gMmRegWith5gGutiEn

Timers

Available in AMF Nodal / AMF Node test cases.

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.

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.

See list of NAS-5G message types currently supported in the Message Editor:

Tcl Parameter: AmfNas5gMmCustomMsgEn

Tcl Parameter: AmfNas5gMmCustomMsg

Tcl Parameter: UeNas5gMmCustomMsgEn

Tcl Parameter: UeNas5gMmCustomMsg

Send Initial Registration Accept with NGAP Initial Context Setup Request

Select to Send Initial Registration Accept with NGAP Initial Context Setup Request. Reference 38.413. Available in AMF Node test case.

Tcl Parameter: AmfNas5gMmRegAccptNgapCsrEn

Emulate Registration Reject

Select to emulate Registration Reject Message. Available in AMF Node test case.

Tcl Parameter: AmfNas5gMmRegRejEn

Reject Option

Select the Reject Option. Available when Emulate Registration Reject is enabled on the AMF Node test case.

Options : Before Security (default) , After Security

Tcl Parameter: AmfNas5gMmRegRejOpt

Reject Cause

Select the Reject Cause. Available when Emulate Registration Reject is enabled on the AMF Node test case.

Range : 0 to 255

Default : 3

Tcl Parameter: AmfNas5gMmRegRejCause

T3502 Timer

T3502 Timer Unit

Select to enter value for T3502 Timer. Available when Emulate Registration Reject is enabled on the AMF Node test case.

Range : 0 to 31

Default : 12

Select T3502 Timer Unit.

Options : 2 Seconds 1 Minute (default), Decihour, Deactivated

Tcl Parameter: AmfNas5gMmT3502En

Tcl Parameter: AmfNas5gMmT3502Value

Tcl Parameter: AmfNas5gMmT3502Unit

Starting SUPI

+=

Enter the starting SUPI (Subscription Permanent Identifier). Corresponds to IMSI in earlier generations of networks.

Also available on the UE Subtab in SMF Nodal test case.

Range: 14 or 15 digits

To support non-sequential SUPI being increased by a given number, use (+ =) widget to enter SUPI incrementation from 1 to 255.

Default :1

Tcl Parameter: UeNas5gMmSupi

Tcl Parameter: UeNas5gMmSupiIncStep

Protection Scheme

Select the Protection Scheme.

Null-Scheme is the only supported Protection scheme for Versions 15.0.0 and 15.0.1.

Option: Null-Scheme, Profile <A>, Profile <B>

Tcl Parameter: AmfNas5gMmProtectionScheme

Tcl Parameter: UeNas5gMmProtectionScheme

Home Network Public Key Id

Available when Version > = 15.2.0 and Protection Scheme = Profile <A> or Profile <B>. Available in AMF Nodal Test Case.

Range: 0 to 255

Default: 0

Tcl Parameter: UeNas5gMmKhnPubKeyId

Home Network Public Key

Available when Version > = 15.2.0 and Protection Scheme = Profile <A> or Profile <B>. Available in AMF Nodal Test Case.

How to generate Home Network Key pair:

SSH to the Landslide test server or connect to any system that can execute the commands listed below:

For Profile <A>:

1. openssl genpkey -algorithm x25519 -out x25519.key.pem
2. openssl pkey -in x25519.key.pem -text

3. Copy the output of the keys and remove the colons, use the hex public key on the Landslide AMF Nodal in the GUI and use the hex decimal private key on UDM ( or on AMF Node if UDM is emulated on it) in the GUI

For Profile <B> :

1. openssl ecparam -name prime256v1 -genkey -conv_form compressed > prime256v1key.pem
2. openssl ec -in prime256v1key.pem -text -noout
3. Copy the output of the keys and remove the colons, use the hex public key on the Landslide AMF Nodal in the GUI and use the hex decimal private key on UDM ( or on AMF Node if UDM is emulated on it) in the GUI

Range: Hex with 0x, at least 1 byte included for instance : 0x00

Default: 0x00

Tcl Parameter: UeNas5gMmKhnPubKey

Home Network Private Key

Available when Version > = 15.2.0 and Protection Scheme = Profile <A> or Profile <B>. Available in AMF Node Test Case.

How to generate Home Network Key pair:

SSH to the Landslide test server or connect to any system that can execute the commands listed below:

For Profile <A>:

1. openssl genpkey -algorithm x25519 -out x25519.key.pem
2. openssl pkey -in x25519.key.pem -text

3. Copy the output of the keys and remove the colons, use the hex public key on the Landslide AMF Nodal in the GUI and use the hex decimal private key on UDM ( or on AMF Node if UDM is emulated on it) in the GUI

For Profile <B> :

1. openssl ecparam -name prime256v1 -genkey -conv_form compressed > prime256v1key.pem
2. openssl ec -in prime256v1key.pem -text -noout
3. Copy the output of the keys and remove the colons, use the hex public key on the Landslide AMF Nodal in the GUI and use the hex decimal private key on UDM ( or on AMF Node if UDM is emulated on it) in the GUI

Range: Hex with 0x, at least 1 byte included for instance : 0x00

Default: 0x00

Tcl Parameter: AmfNas5gMmKhnPrivKey

Routing Indicator

Enter the Routing Indicator. Per 3GPP 24.501, 9.11.3.4. (Should be in Binary-Coded decimal (BCD) format).

Options: Enter 1 to 4 Hex characters (0 to 9, or F) in BCD format with padded F (s)

Default: F0FF

Tcl Parameter: UeNas5gMmRoutingInd

MNC Length

Enter the MNC Length. Also available on UE Subtab in SMF Nodal test case.

Options: 2 or 3

Default: 3

Tcl Parameter: UeNas5gMmMncLength

Type: True/False

Default: False.  

Tcl Parameter:

Select NIA0 or NIA1 or NIA2 or NIA3.

Type: True/False

Default: All True  

Tcl Parameter:

Select Reserved, NIA1 - SNOW3G, NIA2 - AES or NIA3 - ZUC.

Default: NIA1 - SNOW3G

Tcl Parameter:

Select Null, NEA1 - SNOW3G, NEA2 - AES or NEA3 - ZUC.

Default: Null

Tcl Parameter:

Select the EPS NAS Integrity and Ciphering Algorithms. Available on AMF Node test case when N26 Interface is enabled.

Select EPS NAS Integrity Algorithm.

Select Reserved, EIA1 - SNOW3G, EIA2 - AES, EIA3 - ZUC.

Default: Reserved

Select EPS NAS Ciphering Algorithm.

Select Null, EEA1 - SNOW3G, EEA2 - AES or EEA3 - ZUC.

Default: Null

Tcl Parameter:

Select which authentication Algorithm to use. Available in AMF Nodal and AMF Node. In AMF Node, you can only select one or the other, not both (5G AKA, EAP).

5G AKA or EAP are supported.

If 5G AKA is selected, the 5G AKA Pane becomes available for input.

If EAP is selected, the EAP Settings box becomes available to select. Currently only EAP-AKA' is supported.

Tcl Parameter: AmfNas5gMmAlgorithm

Tcl Parameter: UeNas5gMm5gAkaEn

Tcl Parameter: UeNas5gMmEapEn

Select an Authentication Algorithm for 5G AKA. Additional fields become available for input.

Disabled when Use SIM Server is enabled.

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

Tcl Parameter: AmfNas5gMm5gAkaAlg

Tcl Parameter: UeNas5gMm5gAkaAlg

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

Encrypt/Decrypt button is available in AMF Nodal test case.

Encrypt - Click on Encrypt to encrypt the Secret Key. 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 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. When the Secret Key is encrypted , the TDF-CSV editor will automatically encrypt the value when it is saved in the cell "Secret Key Encrypted". Additonal details in Apply Test Data File to NAS Protocol.

Decrypt - Click on Decrypt to decrypt the Secret Key.

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

Default: 0x00

Tcl Parameter: AmfNas5gMmSecretKey

Tcl Parameter: UeNas5gMmSecretKey

Tcl Parameter: UeNas5gMmSecretKey_Enc

Per 3GPP (33.102) specified RES Length of 4-16 octets.

Range: 4, 8, 16

Default : 8

Note : Prior to release 19.8, The Milenage RES Length field had been a numerical entry field in the GUI that always allowed any value between 4 and 8. The values 5, 6, and 7 are invalid but have never been flagged as an error. Now, the RES Length field is a combo-box selection with only 4, 8, and 16 available. If any previously saved RES Length value was 5, 6, or 7, Tcl Validation is going to reset it to the default value of 8.

Tcl Parameter: AmfNas5gMmAuthResLen

Tcl Parameter: UeNas5gMmAuthResLen

The 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network.

Encrypt/Decrypt button is available in AMF Nodal test case.

Encrypt - Click on Encrypt to encrypt the Operator Variant / OPc. 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  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. When the Operator Variant / OPc is encrypted , the TDF-CSV editor will automatically encrypt the value when it is saved in the cell "Operator Variant Encrypted". Additonal details in Apply Test Data File to NAS Protocol.

Decrypt - Click on Decrypt to decrypt the Operator Variant / OPc.

Range: Up to 16-Byte hex string

Default: 0x63BFA50EE6523365FF14C1F45F88737D

Tcl Parameter: AmfNas5gMmOpType

Tcl Parameter: AmfNas5gMmOpVar

Tcl Parameter: UeNas5gMmOpType

Tcl Parameter: UeNas5gMmOpVar

Tcl Parameter: UeNas5gMmOpVar_Enc

A128-bit value derived from OP and K and used in subsequent computations. Hence, less sensitive and if obtained by third party.

Encrypt/Decrypt button is available in AMF Nodal test case.

Encrypt - Click on Encrypt to encrypt the Operator Variant / OPc. 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  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. When the Operator Variant / OPc is encrypted , the TDF-CSV editor will automatically encrypt the value when it is saved in the cell "Operator-c Variant Encrypted". Additonal details in Apply Test Data File to NAS Protocol.

Decrypt - Click on Decrypt to decrypt the Operator Variant / OPc.

Range: Up to 16-Byte hex string

Default: 0x63BFA50EE6523365FF14C1F45F88737D

Tcl Parameter: AmfNas5gMmOpC

Tcl Parameter: UeNas5gMmOpC

Tcl Parameter: UeNas5gMmOpC_Enc

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.

Enter up to a 2 byte hex string for the AMF. Available on AME Node test case.

Range: 2-Byte hex string

Default: 0x8000

Tcl Parameter: AmfNas5gMmAmf

Tcl Parameter: AmfNas5gMmTuakAmf

Select for AMF nodal to configure the initial value of SQN on UE side in order to cause synch failure and re-synchronization scenario of 5G AKA to be able to execute the following scenario. 

The UE sends an authentication failure message to the SEAF/AMF with synchronization failure (AUTS).

Range : 0 to 16777215

Default : 0

Spec reference : 3GPP TS 33.512 section 4.2.2.1.1 Synchronization failure handling

Limitation / Caveat :

If you use Landslide AMF Node as SUT, if initial Authentication SQN bigger than 708624, AMF Nodal will send out "authentication failure" in response to the first authentication request. 

Tcl Parameter: UeNas5gMmL5apInitAuthSqnEn

Tcl Parameter: UeNas5gMmL5apInitAuthSqn

If the "Simulate Security Mode Complete Replay" checkbox is checked, AMF Nodal will send an extra Security Mode Complete message after each legitimate one, thus simulating a replay attack.

If such a duplicate Security Mode Complete message is received by AMF Node, the AMF Node will ignore this message.

Available if one or more of the following is checked for "Integrity Algorithm" under "UE security capabilities ".

• NIA1
• NIA2
• NIA3

Spec References : 3GPP TS 24.501, 3GPP TS 33.501, 3GPP TS 33.512

Tcl Parameter: UeNas5gMmL5apSimSmcReplayEn

If the "Simulate Sending Incorrect RES* in Authentication Response" checkbox is checked, AMF Nodal will send an incorrect RES* in Authentication Response messages.

Spec References : 3GPP TS 24.501, 3GPP TS 33.501, 3GPP TS 33.512

Tcl Parameter: UeNas5gMmL5apSimWrongResRspEn

When checked, the "UE security capabilities" panel is allowed to have no options checked. And, if "S1 Mode Supported" is checked in the "5GMM Capability" panel, the S1-MME|NAS tab's "UE Network Capabilities" panel is allowed to have no Integrity Algorithm options checked.

This option allows for invalid / unacceptable UE security capabilities (no 5GS encryption algorithms (all bits zero), no 5GS integrity algorithms (all bits zero) ).

Spec References : 3GPP TS 33.501

Tcl Parameter: UeNas5gMmL5apZeroUeSecCapsEn

Available in AMF Nodal test case. If "Use Different 5G Security Capabilities in Path Switch Request Message" is checked, the Path-Switch Request will include a UESecurityCapabilities different from configured. And a correct UESecurityCapabilities should be included in Path-Switch Acknowledge message.

"In the Path-Switch message, the target gNB shall send the UE's 5G security capabilities
received from the source gNB to the AMF. The AMF shall verify that the UE's 5G security capabilities received from the target gNB are the same as the UE's 5G security capabilities that the AMF has locally stored. If there is a mismatch, the AMF shall send its locally stored 5G security capabilities of the UE to the target gNB in the Path-Switch Acknowledge message." as specified in TS 33.501 [2], clause 6.7.3.1.

If this checkbox is enabled, the target gNB sends 5G security capabilities for the UE, different from the ones stored in the AMF, to the AMF under test using a Path-Switch message.

Tcl Parameter: UeNas5gMmL5apDiffSecCapsInPsrEn

Available in AMF Nodal test case. Select to ensure Authentication failure (Synch failure) on the first Authentication Request.

Tcl Parameter: UeNas5gMmL5apSimFailOnFirstAuthReqEn

Select to indicate that S1 Mode is supported. Requires NAS-5G MM Version (24.501) 15.2.0 or higher.

When the test activity is Inter-technology Mobility or Command Mode/Sequencer with Handoff Type = LTE, S1 Mode Supported is forced to always be checked.

When S1 Mode Supported is checked and not in Inter-Tech or Command Mode/Sequencer with Handoff Type = LTE:
      a) the S1-MME tab is shown with just the NAS tab.
      b) the Mobile Subscribers/EPS panel is enabled on the Test Configuration tab.

Default = False (default has been changed from true to false in Release 20.0).

Tcl Parameter: UeNas5gMm5gMmCapS1

Select to indicate that HO Attach from N1 Mode to S1 Mode is supported. Requires NAS-5G MM Version (24.501) 15.2.0 or higher.

Tcl Parameter: UeNas5gMm5gMmCapHoN1S1

Select to indicate that LPP in N1 Mode is supported.

Tcl Parameter: UeNas5gMm5gMmCapLppN1

Select the UE Usage setting.

Options : Voice-centric (default), Data-centric

Tcl Parameter: UeNas5gMmUeUsageSetting

Select to indicate if IMS Voice over PS Session is supported over 3GPP access or not supported.

Options : IMS Voice over PS Session is supported over 3GPP access (Default) , IMS Voice over PS Session is not supported over 3GPP access

Tcl Parameter: AmfNas5gMm5gNfsImsVops3gpp

Select to indicate if IMS Voice over PS Session is supported over non-3GPP access or not supported.

Options : IMS Voice over PS Session not supported over non-3GPP access (Default) , IMS Voice over PS Session supported over non-3GPP access

Tcl Parameter: AmfNas5gMm5gNfsImsVopsN3gpp

Select to indicate if Emergency services (EMC) is supported.

Options : Emergency services not supported (Default) , Emergency services supported in NR connected to 5GCN only, Emergency services supported in E-UTRA connected to 5GCN only, Emergency services supported in NR connected to 5GCN and E-UTRA connected to 5GCN

Tcl Parameter: AmfNas5gMm5gNfsEmc

Select to indicate if Emergency services (EMF) Fallback is supported.

Options : Emergency services fallback not supported (Default) , Emergency services fallback supported in NR connected to 5GCN only, Emergency services fallback supported in E-UTRA connected to 5GCN only, Emergency services fallback supported in NR connected to 5GCN and E-UTRA connected to 5GCN

Tcl Parameter: AmfNas5gMm5gNfsEmf

Select to indicate if Interworking without N26 interface is supported or not supported.

Options : Interworking without N26 interface not supported (Default) , Interworking without N26 interface supported

Tcl Parameter: AmfNas5gMm5gNfsIwkN26

Select to indicate if Access Identity 1 is valid or not valid in RPLMN or equivalent PLMN.

Options : Access Identity 1 not valid in RPLMN or equivalent PLMN. (Default) , Access Identity 1 valid in RPLMN or equivalent PLMN.

Tcl Parameter: AmfNas5gMm5gNfsMpsi

Select to indicate if Emergency services (EMC) is supported or not supported over non-3GPP access.

Options : Emergency services not supported over non-3GPP access (Default) , Emergency services supported over non-3GPP access

Tcl Parameter: AmfNas5gMm5gNfsEmcN3

Select to indicate if Access Identity 2 is valid or not valid in RPLMN or equivalent PLMN.

Options : Access Identity 2 not valid in RPLMN or equivalent PLMN. (Default) , Access Identity 2 valid in RPLMN or equivalent PLMN.

Tcl Parameter: AmfNas5gMm5gNfsMcsi

Enter the Number of Requested NSSAIs (Network Slice Selection Assistance Information). Available on AMF Nodal and gNB CU SA Nodal test cases.

The NSSAI contains two components: the SST (Slice / Service Type) and an optional SD (Slice Differentiator).

Range : 0 to 8

SST : 0 up to 255

SD : hex-string, maximum length = 6 (optional)

If Support Roaming is enabled on the AMF Nodal Test Configuration, then the Mapped Home S-NSSAIs table becomes available for input. Indicate if each S-NSSAI in "Requested NSSAI" includes the mapped Home S-NSSAI. 

If the “Mapped” of each S-NSSAI is Y, Mapped SST and Mapped SD (optional) will be included as the mapped Home S-NSSAI of the corresponding S-NSSAI in the Requested NSSAI of Registration Request Message sent by UE.

Select Y or N for Mapped and when Y is selected, enter the SST and SD. The SD is optional.

SST - Range 0 to 255, default : 1

SD - Hex-string with maximum length = 6 long

Tcl Parameter: UeNas5gMmReqNumNssai

Tcl Parameter: UeNas5gMmReqNssai_1

Tcl Parameter: UeNas5gMmReqNssaiMapped_1

Enter the Number of Configured NSSAIs ( Network Slice Selection Assistance Information).

The NSSAI contains two components: the SST (Slice / Service Type) and an optional SD (Slice Differentiator). Indicate the default (Y or N) NSSAIs.

Range : 1 to 8, Default = 3

SST : 0 up to 255

SD : hex-string, maximum length = 6 (optional)

default : Y (default) or N

If Support Roaming is enabled on the AMF Node Emulator Configuration, then the Mapped Home S-NSSAIs table becomes available for input. Indicate if each S-NSSAI in "Configured NSSAI" includes the mapped Home S-NSSAI. 

If the “Mapped” of each S-NSSAI is Y, Mapped SST/SD will be included as the mapped Home S-NSSAI of the corresponding S-NSSAI in the "Allowed NSSAI" of Registration Accept Message sent by AMF.

Select Y or N for Mapped and when Y is selected, enter the SST and SD. The SD is optional.

SST - Range 0 to 255, default : 1

SD - Hex-string with maximum length = 6 long

Tcl Parameter: AmfNas5gMmConfigNumNssai

Tcl Parameter: AmfNas5gMmConfigNssai_1

Tcl Parameter: AmfNas5gMmConfigNssaiMapped_1

Used to indicate whether to emulate the condition that the access bearer at EPS (4g) side was released or not when from Eps to 5gs Idle Mode Mobility is triggered.

If this option is enabled, SMF Nodal will trigger Eps to 5gs Idle Mode Mobility without the activation of PDU(s) which are established in EPS. Otherwise, SMF Nodal will trigger Eps to 5gs Idle Mode Mobility with the activation of PDU(s) which are established in EPS. In other words, if this option is enabled, “pduSessionsActivateList” attribute won’t be included in NsmfPduSession_CreateSmContext_Request message sent by SMF during Eps to 5gs Idle Mode Mobility. Otherwise, it will be included.

Available when Test Activity is “Inter Technology Mobility” and Handoff Protocol is LTE and, Handoff Type is “REG/TAU”, in the SMF Nodal test case.

Tcl Parameter: UeNas5gMmEpsAccBrrIdleDurEto5MobEn

Select to configure GPSI (Global Public Subscriber Identifier).

Select GPSI Type. Refer to TS 23.501 Section 5.9.8

Options : MSISDN (Mobile Station International Subscriber Directory Number) or External ID.

Tcl Parameter: AmfNas5gMmGpsiEn

Tcl Parameter: AmfNas5gMmGpsiType

Tcl Parameter: UeNas5gMmGpsiEn

Tcl Parameter: UeNas5gMmGpsiType

Available when GPSI Type = MSISDN. Enter the starting MSISDN (Mobile Station International Subscriber Directory Number). The pattern of GPSI (MSISDN) is described in TS 29.571 Range: 5 to 15 digits Default : 17962480141

Tcl Parameter: AmfNas5gMmGpsiMsisdn

Tcl Parameter: UeNas5gMmGpsiMsisdn

Enter the Corresponding SUPI.   Range: 14 to 15 digits

Tcl Parameter: AmfNas5gMmGpsiCorrespondingSupi

Available when GPSI Type = External ID. Select to indicate IMSI is used as the Local Identifier of External ID.

Tcl Parameter: UeNas5gMmGpsiExtIdLocalIdUseImsiEn

Enter the Local Identifier of the External Identifier. Refer to TS23.682 - Section 4.6.2 Range: 1 to 15 digits Default : 123456789

Tcl Parameter: UeNas5gMmGpsiExtIdLocalId

Enter the Domain Identifier of the External Identifier. Refer to TS23.682 - Section 4.6.2 Range: 1 to 126 characters Default : domain.com

Tcl Parameter: UeNas5gMmGpsiExtIdDomainId

Select to enable Local Area Data Network (LADN) Service Areas and Enter Number of LADN DNNs.

Range: 1 to 2

Default: 1

Tcl Parameter:

Enter the Data Network Name.

Up to 100 characters

Range: 1 to 16

Default: 1

Tcl Parameter:

Range: 0 to 16777215

Default: 0

Tcl Parameter:

Range: 2 to 4

Default: 0

Tcl Parameter:

RRange: 0 to 16777215

Default: 0

Tcl Parameter:

Enable UE Configuration Update

Select to enable UE Configuration Update procedure as defined in 24.501 5.4.4.

A UE Configuration Update message will be triggered.  

Tcl Parameter: AmfNas5gMmUeConfigUpdateEn

UE Initiate Registration

Select for UE to initiate Registration. Available when Enable UE Configuration Update is enabled.

Tcl Parameter: AmfNas5gMmUeInitRegEn

Update Interval (ms)

Enter the update interval in milliseconds.

Range : 10000 to 60000

Default : 30000

Tcl Parameter: AmfNas5gMmUeConfigUpdateTime

Update Only NITZ Information

Select for sending Configuration Update Command message with only NITZ information to UE after UE is successfully registered to the network.

If this option is enabled, AMF will send a Configuration Update Command message to UE after AMF receives RegistrationComplete Message from UE during the initial registration procedure.

This option will be available only when "Enable UE Configuration Update" is enabled. If this option is enabled, all other options (i.e. "UE Initiates Registration" and "Update Interval(ms)") within UE Configuration Update panel are grayed out.

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

Enter the Configuration Update Command (with only NITZ information) delay in milliseconds.

If the value is 0, AMF will send a Configuration Update Command (with only NITZ information) message to UE without any delay after AMF receives RegistrationComplete Message from UE during the initial registration procedure. 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/gNB.

Range : 0 to 20000

Default : 0

Tcl Parameter: AmfNas5gMmUeCfgUpdNitzDelayTime

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 Configuration Update Command 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 : Landslide5GC

Tcl Parameter: AmfNas5gMmUeCfgUpdNtwFullNameEn

Tcl Parameter: AmfNas5gMmUeCfgUpdNtwFullName

Short name for network - Select to include the "abbreviated name of the network" in Configuration Update Command 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 : LS5GC

Tcl Parameter: AmfNas5gMmUeCfgUpdNtwShortNameEn

Tcl Parameter: AmfNas5gMmUeCfgUpdNtwShortName

Local time zone - Select to include the "Local time zone" in Configuration Update Command. (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: AmfNas5gMmUeCfgUpdLtzEn

Universal Time and Local time zone - Select to include the "Universal time and local time zone" in Configuration Update Command. (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: AmfNas5gMmUeCfgUpdUtLtzEn

Network Daylight Saving Time - Select to include the "Network daylight saving time" in Configuration Update Command 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: AmfNas5gMmUeCfgUpdNtwDstEn

Tcl Parameter: AmfNas5gMmUeCfgUpdNtwDst

Enable UE Policy

The UPSI List allows the user to provision locally stored UE policies, indicated by UPSIs ( UE Policy Section Identifiers ). "UE Policy" is only supported when NAS-5G | MM version is 15.4 or greater.

Tcl Parameter: UeNas5gMmUePolicyEn

Start or Find PDU by URSP Rules

The "Start or find PDU by URSP rules" allows the user to start UE applications according to the received URSP rules from PCF. This box can be unchecked if you want to run UE Policy message flows but still start PDU sessions the old way ( i.e. not by URSP rules ).

"Start or find PDU by URSP rules" is only supported for Capacity test and when Data traffic is enabled and when Capacity Test Settings - Initiate PDY Connection is set to "When All UEs Registered" .

UE Traffic Route Selection -

The UE Traffic Route Selection function is enabled  when you select  "Start or find PDU by URSP rules" on NAS-5G | MM | UE Policy.

Please note that the Namf_Communication_N1N2MessageTransfer request can happen anytime after UE Policy Association Establishment. If there is no received URSP rules by the time an application is ready to start, the start attempt will fail. In current implementation, we will not retry start of UE applications. But this issue can be avoided by adjusting the "Start Traffic Delay" on NAS-5G | MM | UE Policy.

The received Manage UE Policy Command may contain UE policy parts with different types, such as ANDSP. Currently URSP is the only type we support. The UE will create or update its stored list of URSP rules with any URSP rules received in  Manage UE Policy Command. Please note that URSP rules with a PLMN that does not match with the UE' s home PCF PLMN will be ignored. Currently we use the first PLMN on gNB as the UE's home PCF PLMN.

Each URSP rule consists of a precedence value, a TD ( Traffic Descriptor ) and a list of RSDs ( Route Selection Descriptors ).

The UE traffic route selection is basically a two-step matching process:

Step 1: The UE will go through the list URSP rules ordered by precedence values and try to find a match for a particular application. The matching is between the TD and application attributes. Please note that not all attributes are listed on the Application Attributes tab on Data Message Flow. Some IP based attributes such as remote IP or port  can be found elsewhere on the DMF window or Network Host panel.

A TD with any unrecognized or unsupported components will be regarded as a mismatch per 24.526.

Step 2: If a match or URSP rule is found, the UE will go through the list of RSDs of the URSP rule and try to find a match. The RSDs are also ordered by precedence values and the matching this time is between the RSD and PDU Session attributes. First the UE will try to a match among existing PDU sessions. If no match is found, the UE will try to start a new PDU session. For convenience we don't support randomly select an idle PDU session and populate it with RSDs before PDU start. Instead, we will go through all  the idle PDUs which are pre-configured and try to find a match against the RSD list. Currently we support the following RSD components:

• PDU session type
• SSC mode
• S-NSSAI
• DNN

An RSD with any unrecognized or unsupported components will be ignored or regarded as a mismatch per 24.526.

After step 2, if a match is found, the application will either start traffic or start PDU, depending on the state of the PDU session. If no match is found, the UE will go back to Step 1 and search for the next URSP rule until the list is exhausted.

Limitation:

• The UE Traffic Route Selection function is only supported for basic and command datagens. If you configure a dmf which is neither a basic or command datagen, it will be silently ignored.
• On the UE side, we currently support up to 8 PLMNs, 16 UPSIs and 16 URSP rules per UE. For each URSP rule, we support up to 4 RSDs.

Enter the Start Traffic Delay (after Registered) (ms) timer in milliseconds.

Range : 1000 to 4294967295

Default : 1000

Tcl Parameter: UeNas5gMmUrspEn

Tcl Parameter: UeNas5gMmTrafficDelay

UPSI List

Select the number of UPSIs (UE Policy Section Identifiers). Up to 4. 0 is allowed.

Enter MCC (Mobile Country Code). Default = 111.

Enter MNC (Mobile Network Code). Default = 11.

Select the number of UPSCs (UE Policy Section Code). Up to 8.

Enter the UE Policy Section Code (UPSC). Range 1 to 65535, Default : 1

Tcl Parameter: UeNas5gMmNumUpsiSubListCnt

Tcl Parameter: UeNas5gMmNumUpsiMcc_1

Tcl Parameter: UeNas5gMmNumUpsiMnc_1

Tcl Parameter: UeNas5gMmNumUpsiUpscCnt_1

Tcl Parameter: UeNas5gMmNumUpsiUpscValue_1_1

MR-DC

Select for Multi-RAT Dual Connectivity (MR-DC) and NR-DC is a Dual Connectivity configuration using the 5GC, where by both the master and secondary RAN nodes are 5G gNBs.

Available on the gNB CU SA Nodal test case. When enabled, a second F1 Tab named SN-F1 becomes available for Secondary Node configuration. In addition, the gNB-S-DU Control Node and gNB-S-DU User Node become available for Secondary Node configuration.

Enter the NR-DC Start Delay (s) in seconds.

Range : 5 to 20 , default : 5

Enter the NR-DC Hold Time (s) in seconds.

Range : 5 to 65535 , default : 5

Select the MN Traffic Ratio.

Options : 0, 25%, 50%, 75%

Select SN Initiated Release to support S-NG-RAN node initiated S-NG-RAN Node Release procedure to release the UE context and relevant resources at the S-NG-RAN node. Per NR C-plane profile specification [2] section 7.3.3. 

Select NR-DC PSCell Change Delay (s) to enter the delay in seconds. This  value should be less than the value of NR-DC Hold Time. To support Security Key Change procedure is for SN to initiate Security Key Change in both SN and MN and inform it to the UE per NR C-plane profile specification [2] section 7.2.2.3. In gNB CU SA Nodal, under Network Devices/gNB DU Control Node, check "Apply gNB Cell ID's From Test Data File" to configure two or more cells for the SN gNB DU. In gNB CU Node which is configured as SN Node, under AS-5G/RRC (Rrc Tab), check " Enable Measurement Configuration, Configuration Type = Mobility)". 

Range : 2 to 65534 , default : 4

Spec Reference : 

38.473 F1AP 16.6.0/July 2021 in F1

38.331 RRC 16.5.0/July 2021 in RRC/AS-5G

38.423 XnAp 16.6.0/July 2021 in Xn-C

O-RAN.WG5.C1-v07.00 O-RAN Open F1/W1/E1/X2/Xn Interface Working Group NR C-plane profile.

Tcl Parameter: UeNas5gMmMrDcEn

Tcl Parameter: UeNas5gMmNrDcEn

Tcl Parameter: UeNas5gMmNrStartDelay

Tcl Parameter: UeNas5gMmNrHoldTime

Tcl Parameter: UeNas5gMmNrMnTrafficRatio_1

Tcl Parameter: UeNas5gMmSnInitRelEn

Tcl Parameter: UeNas5gMmNrPscellChgDelayEn

Tcl Parameter: UeNas5gMmNrPscellChgDelay

Apply Test Data File to MM Parameters

Select to add a TDF file for MM parameters.

Example file below - NEW NSSAI - will reset the existing Nssai list and set the new Nssai. NSSAI will append Nssai into the list.

UeMm_TDF.csv

Added columns SUPI_P, IMEI_P - See example file below.

MM-SUPIIMEI.csv

Added parameter support for "KI" (Secret Key), "OP (Operator Variant)", "OPC (Operator-c Variant)", and "RES_LENGTH (RES Length (bytes)) - AMF Nodal test case only" . 

TDF Column Names : CustomKey, SUPI_P,IMEI_P,NEW NSSAI, NSSAI, KI, OP, OPC, RES_LENGTH

• 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: AmfNas5gMmCfgFileEn

Tcl Parameter: AmfNas5gMmCfgFile

Tcl Parameter: UeNas5gMmCfgFileEn

Tcl Parameter: UeNas5gMmCfgFile

Apply Test Data File to Network Side MM Parameters

Select to add a TDF file for MM parameters. Available on the UE tab on SMF Nodal test case.

Added columns CustomKey, SUPI_P, IMEI_P ,NEW NSSAI,NSSAI,GPSI,EXTID_LOCAL_ID,EXTID_DOMAIN- See example file below.

MM_reorder_SMFNodal.csv

MM-SUPIIMEI.csv

• 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: AmfSbiNodeNas5gMmCfgFileEn

Tcl Parameter: AmfSbiNodeNas5gMmCfgFile

Number of Forbidden TACs

Available on AMF Node when Support NTN is enabled. Select to enter up to 16 Forbidden TACs.

Enabled when NAS-5G version is 17.12.0/Sep2023 or higher and NGAP version(N2 tab) is 17.6.0/Sep2023 or higher.  

Range : 1 to 6 hex characters

Tcl Parameter: AmfNas5gMmForbiddenTacsNum

Tcl Parameter: AmfNas5gMmForbiddenTac

UE Location Verification on Receipt of Request

For Registration Request

For Service Request

For PDU Session Establishment Request

Delayed UE Location Verification (ms)

Available on AMF Node when Support NTN (Non Terrestrial Network) is enabled. Select UE Location Verification on Receipt of Request to emulate NTN UE Location Verification failure.

When enabled, select For Registration Request or For Service Request or For PDU Session Establishment Request. 

Select to enter Delayed UE Location Verification in milliseconds.

Range : 1000 to 4294967295

Default : 5000

During PDU session Establishement procedure, the AMF verifies the location of the UE. If the UE is not allowed to operate at the present UE location in the PLMN, the AMF rejects the PDU session establishment request and initiates Network-initiated Deregistration procedures to release any existing PDU session. 

3gpp spec 23.502 release 17.6 section 4.3.2.2.1, 4.3.2.2.2

4.3.2.2.1  Non-roaming and Roaming with Local Breakout

For NR satellite access, the AMF may decide to verify the UE location. In this case, if the AMF can determine based on the ULI (including Cell ID) received from the gNB that UE has registered to a PLMN that is not allowed to operate at the present UE location, then the AMF may reject the PDU Session Establishment Request and further deregister the UE as specified in clause 4.2.2.3.3. Otherwise, if the AMF is not aware of the UE location with sufficient accuracy to make a final decision, the AMF proceeds with the PDU Session Establishment procedure and may initiate 5GC-NI-LR Procedure as specified in clause 6.10.1 of TS23.273 [51], and deregisters the UE as specified in clause 4.2.2.3.3 if the information received form the LMF proves that the UE is registered to a PLMN that is not allowed to operate in the UE location.

4.3.2.2.2  Home-routed Roaming

For NR satellite access, the AMF may decide to verify the UE location. In this case, if the AMF can determine based on the ULI (including Cell ID) received from the gNB that UE has registered to a PLMN that is not allowed to operate at the present UE location, then the AMF may reject the PDU Session Establishment Request and further deregister the UE as specified in clause 4.2.2.3.3. Otherwise, if the AMF is not aware of the UE location with sufficient accuracy to make a final decision, the AMF proceeds with the PDU Session Establishment procedure and may initiate 5GC-NI-LR Procedure as specified in clause 6.10.1 of TS 23.273 [51], and deregisters the UE as specified in clause 4.2.2.3.3 if the information received form the LMF proves that the UE is registered to a PLMN that is not allowed to operate in the UE location.

As described in spec <23.502> - 4.2.2.2.2  and 4.2.3.2, also in spec <24.501> - 5.5.1.2.5.  PLMN re-selection could be done at UE on receipt of Registration/Service Request Reject with cause #78 ((PLMN not allowed to operate at the present UE location).

In B2B test sessions, the testing scenario can be enabled by configuring extra PLMN in AMF Nodal and adding multiple AMF SUTs. 

4.2.2.2.2   General Registration

For NR satellite access, the AMF may verify the UE location and determine whether the PLMN is allowed to operate at the UE location, as described in clause 5.4.11.4 of TS 23.501 [2]. If the UE receives a Registration Reject message with cause value indicating that the PLMN is not allowed to operate at the present UE location, the UE shall attempt to select a PLMN as specified in TS 23.122 [22].

4.2.3.2      UE Triggered Service Request

For NR satellite access, the AMF may decide to verify the UE location and determine whether the PLMN is allowed to operate at the UE location, as described in clause 5.4.11.4 of TS 23.501 [2]. If the UE receives a Service Reject message with cause value indicating that the PLMN is not allowed to operate in the present UE location, the UE shall attempt to select a PLMN, as specified in TS 23.122 [22]. 

5.5.1.2.5    #78   (PLMN not allowed to operate at the present UE location).

      This cause value received from a non-satellite NG-RAN cell is considered as an abnormal case and the behavior of the UE is specified in subclause 5.5.1.2.7.

      The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall store the PLMN identity and, if it is known, the current geographical location in the list of "PLMNs not allowed to operate at the present UE location" and shall start a corresponding timer instance (see subclause 4.23.2). The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122 [5].

Limitation / Caveat :

For spec<23.501>-5.4.11.4 - If the AMF, based on the ULI, is not able to determine the UE's location with sufficient accuracy to make a final decision, the AMF proceeds with the Mobility Management or Session Management procedure and may initiate UE location procedure after the Mobility Management or Session Management procedure is complete, as specified in clause 6.10.1 of TS 23.273 [87], to determine the UE location. The AMF shall be prepared to deregister the UE if the information received from LMF indicates that the UE is registered to a PLMN that is not allowed to operate in the UE location. In the case of a NAS procedure, the AMF should either reject any NAS request targeted towards a PLMN that is not allowed to operate in the known UE location and indicate a suitable cause value, or accept the NAS procedure and initiate deregistration procedure once the UE location is known. In the deregistration message to the UE, the AMF shall include a suitable cause value. 

Landslide's implementation focuses on the parts where a final decision cannot be made. "May initial UE location procedure" part will be skipped.

During PDU session establishment procedure, the AMF verifies the location of the UE. If the UE is not allowed to operate at the present UE location in the PLMN, the AMF rejects the PDU session establishment request and initiates Network-initiated Deregistration procedures to release any existing PDU session.  AMF rejects the NAS message containing PDU Session Establishment Request with cause #78. 

According to TS 24.501, the following default values of MM/SM timer have a bigger value for accessing via a satellite NG-RAN. When the flag "NTN Type" under gNB Control Node is checked on AMF Nodal TC, the GUI will issue a Warning dialog listing any of them that are below the recommended default value per the spec.

NR Satellite access is used, suggest to increase the following default MM|SM timers to the following values according to TS 24.501:
              T3510                  27 (s)
              T3517                  27 (s)
              T3521                  27 (s)
              T3580                  21 (s)

3gpp spec 23.502 release 17.6 section 4.3.2.2.1, 4.3.2.2.2

"Delayed UE Location Verification" IE is used to achieve the process of accept the NAS procedure and initiate deregistration procedure (cause - Illegal UE) to simulate testing scenarios that cannot to make a final decision.

If Delayed UE Location Verification is not checked and For PDU Session Establishment Request is checked, AMF Node will reject the NAS
message containing PDU Session Establishment Request with 5GMM cause #78 (PLMN is not allowed to operate in the present UE location)
If both Delayed UE Location Verification and For PDU Session Establishment Request are checked, AMF Node will start the delay timer on receipt of PDU Session Establishment Request message and deregister the UE after the delay timer timeout.
 

Tcl Parameter: AmfNas5gMmNtnUeLocVerifEn

Tcl Parameter: AmfNas5gMmNtnForRegReqEn

Tcl Parameter: AmfNas5gMmNtnForServReqEn

Tcl Parameter: AmfNas5gMmNtnForPduSessionEstReqEn

Tcl Parameter: AmfNas5gMmNtnDelayUeLocEn

Tcl Parameter: AmfNas5gMmNtnDelayTimer

Available on AMF Node when Support NTN is enabled. 

Select for RAN indication that UE has moved out of PLMN serving area for Satellite access. If N2 Context Release Request cause indicates the release is requested due to a UE using satellite access moved out of PLMN serving area, the AMF may deregister the UE as described in clause 4.2.2.3.3 before continuing with the AN Release procedure.

When AMF receives a UE Context Release Request message with a cause value of "UE not in PLMN serving area", if the "Deregister UEs using satellite access that moved out of PLMN serving area" checkbox is checked, the AMF will send a Downlink NAS Transport message containing Deregistration Request with a cause value of "PLMN not allowed to operate at the present UE location".

Prior to this feature, the AMF would send a UE Context Release Command message in this scenario.

Spec reference : 23.502 release 17.6 section 4.2.6 , 24.501

Enabled when NAS-5G version is 17.12.0/Sep2023 or higher and NGAP version(N2 tab) is 17.6.0/Sep2023 or higher.  

Tcl Parameter: AmfNas5gMmNtnDeregOutOfSvcAreaEn