Nas 5G Sm

NAS-5G Version (24.501)

 Select NAS 5G SM protocol 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 (default)

 Tcl Parameter: AmfNas5gSmVersion

 Tcl Parameter: SmfNas5gSmVersion

 Tcl Parameter: UeNas5gSmVersion

NGAP Version (38.413)

Select NGAP 5G protocol Version.

Options: 15.0.0/Jun2018, 15.1.0/Sep2018, 15.2.0/Jan2019, 15.2.0-Variant1/Jan2019, 15.2.0-Variant2/Mar2019 , 15.4.0/Jul2019, 16.2.0/Jul2020, 17.6.0/Sep2023 (default)

Tcl Parameter: SmfNas5gSmNgapVersion

Tcl Parameter: UeNas5gSmNgapVersion

PDU Type

Select Protocol Data Unit (PDU) Type.

When WiFi Handoff Protocol is selected for Inter-Technology Mobility testing the IP Address Type on the WiFi Subscribers Pane must match with the PDU Type.

Option "both" is not supported when WiFi Handoff Protocol is selected for Inter-Technology Mobility testing.

When "Per DNN" is selected, a dropdown list under each "DNN" tab becomes available with options IPv4, IPv6 or Both for configuring PDU Type for each DNN on AMF Nodal. For each DNN, Tcl variable UeNas5gSmPduType_<dnnidx> is added, where <dnnidx> stands for the index of the DNN in the configuration. Default value is IPv4 (1).

When Ethernet is selected, PDU MAC Address Pool becomes available for input for UPF Nodal test case. Per 3GPP 23501 - 5.6.10.2 - Support of Ethernet PDU Session Type.

Limitations for PDU type = Ethernet : 

• UPF Nodal does not support SDF filter.
• UPF Node needs to pre-resolve Network Host IP address in order to forward uplink traffic to the Network Host. Additional details here: Reserving Ports For Your Test Session (Pre-resolved ARP )
• The following checkboxes are disabled : In QoS Settings and Modified QoS Settings, Number of Filters and Modify Packet Filters.
• The N4|PFCP UP feature "UEIP" is not supported

Options: IPv4  (default) , IPv6, Both, Per DNN, Ethernet

Tcl Parameter: SmfNas5gSmPduType

Tcl Parameter: UeNas5gSmPduType

Tcl Parameter: UeNas5gSmPduType_1

Available on on AMF Nodal and UPF Nodal. Enter the number of seconds between Echo Requests.

In support of GTP Echo Request on N3 interface between gNB and UPF. 

The following messages are supported for AMF Nodal.

• Echo Request messages are sent from gNB to UPF periodically based on the configured "Periodic Echo Msg Time". Echo Request messages are sent only if there is data path between gNB and UPF.
• Error Indication messages are sent from gNB to UPF if data with unknown TEID is received. Error Indications Sent/Received available in the following test cases/OM tabs : 

  AMF Nodal - "gNB Control Node", "gNB User Node", and "SMF SBI Node"
  Non 3GPP GW Access Node - "gNB Control Node" and "gNB User Node"
  SMF Nodal - "gNB User Node"
  SMF Node - "SMF SBI Node"
  UPF Nodal - "gNB User Node"

Range : 0 to 3932100

Default : 0

Tcl Parameter: SmfNas5gSmEchoTimeSec

Tcl Parameter: UeNas5gSmEchoTimeSec

Starting PDU Session ID

Available in AMF Nodal. Enter the Starting Protocol Data Unit (PDU) Session ID.

Range: 1 to 15

Default: 5

Tcl Parameter: UeNas5gSmPduSessId

Delay N1 Message after N2 Response (ms)

When AMF Nodal processes step 6- N2 Session Response and step 9 - PDU Session Modification Command Ack in PDU Session Modification procedure defined in 4.3.3.2 TS23.502, AMF Nodal will send N2 message and then N1 message in order but at the same time. If it is configured, the delay between step 6) and step 9) will be made like the over-air delay between UE and gNB.

Select to enter a delay in milliseconds between N1 Message and N2 Response.

Available in AMF Nodal and SMF Nodal test cases.

This delay will be applied to only PDU modification procedure as of now.

Range : 10 to 200

Default : 50

Tcl Parameter: UeNas5gSmN1MsgAfterN2RspDelayEn

Tcl Parameter: UeNas5gSmN1MsgAfterN2RspDelay

Select to include SM PDU DN request container IE in PDU Session Establishment Request Message which will be sent by UE when Secondary Authentication option of DNN which PDU Session will connect to is enabled.

Available in AMF Nodal and SMF Nodal when PDU Session Secondary Authentication is enabled.

Tcl Parameter: UeNas5gSmInclSmPduDnReqCtnrEn

Select to send PDU Session Modification Request in First Mobility from EPC. 

Available in AMF Nodal and SMF Nodal test cases when Inter-Technology Mobility, Command Mode, or Sequencer with Handoff Protocol = LTE are enabled.

Tcl Parameter: UeNas5gSmModReqInFirstMobFromEpcEn

Timers

T3580 (s) , T3580 Max Retry

Available in AMF Nodal/SMF Nodal. Select to enter PDU Session Establishment Request Retry timer in seconds and the maximum number of retry attempts in T3580 Max Retry.

Range: 0 to  255

Default : 16

Enter the maximum number of retry attempts in T3580 Max Retry.

Range: 0 to  255

Default : 16

Tcl Parameter: UeNas5gSmT3580Timer

Tcl Parameter: UeNas5gSmT3580MaxRetry

PDU Reconnect Time (ms)

Indicates the time a released PDU is reconnected in milliseconds. Available in AMF Nodal and SMF Nodal.

Range: 0 or 1000 to 4294967295

Default: 1000

Tcl Parameter: UeNas5gSmPduReconnectTime

Determines the time (in seconds) the UE needs for keeping the old PDU session during the transition of Change of SSC Mode 3 PSA with Multiple PDU Sessions. If it is set to 0, the UE will never release PDU session from its end. Otherwise the UE will initiate UE requested PDU Session Release when the corresponding timer expires unless the PDU session is already released by the network Available in AMF Nodal.

Range: 0 or 65535

Default: 0

Tcl Parameter: UeNas5gSmSscMode3PduRlsTime

Number of Data Network Names

Enter Number of Data Network Names.

When Max DNN Mode via TDF or DNN with Starting Supi Mode via TDF  is enabled, "Number of Data Network Names” range (usually 1 to 16) will disappear. Instead, it will become available to enter a number. (1 to 3000). See below for additional details.

Select 0 (No Network Names) or up to 15 Network Names. Enter DNN Pane data.

Range: 0 to 15

Default : 1

Tcl Parameter: UeNas5gSmNumNtwkNames

Data Network Name

Enter the Data Network Name of DNN. Available when Number of Data Network Names is > 0.

When Max DNN Mode via TDF is enabled, the Data Network Name will support Auto-Increment Format and up to 200 DNNs via TDF file. Enter up to 100 characters for Data Network Name. A blank (null) DNN is allowed when using "Max DNN Mode via TDF" .

See Parameter Auto-Increment Format Wizard for additional details.

Up to 100 characters

See examples below with 4 UEs, 3 PDUs, 3 DNNs and with 4UEs, 3 PDUs, 2 DNNs.

Tcl Parameter: UeNas5gSmNtwkName_1

LADN Indicator

Select to indicate that DNN is LADN (Local Area Data Network) DNN. Not available when Max DNN Mode via TDF is enabled.

Available to enable when Number of PDUs > 1,  NAS Version >= 15.1.0, Number of DNNs is > =  Number of PDUs and Test Activity = ( Command Mode / Sequencer or Intra-AMF Mobility with Handoff Type Xn).

Per TS 23.501 "5.6.5 Support for Local Area Data Network".

Tcl Parameter: UeNas5gSmDnnLadnIndEn_1

Emergency

Select for 911 Emergency Service Fallback per 23.502 v 15.3.0 section 4.13.4.1. Available when Number of Data Network Names is > 0 and when Max DNN Mode via TDF is enabled.

When Test Activity = Inter Technology Mobility on AMF Nodal test case, Emergency is not available on DNN1. It is available on DNN2 to DNN15. 

Available for all test activities for UE registration to receive emergency services (3GPP 23.502 section 4.2.2.2.2). See additional details on Use Emergency registration if first Pdu is Emergency Pdu on Nas 5G Mm tab.

Emergency and Always-On PDU are mutually exclusive.

Added support for gNB CU SA Nodal for UE registration to receive emergency services (3GPP 23.502 section 4.2.2.2.2). 

Tcl Parameter: UeNas5gSmDnnEmergencyEn_1

Select for support of Activating Redundant Transmission PDU. Available on AMF Nodal test case when NAS-5G Version 15.1.0 or higher. This checkbox is part of the Support URLLC feature on AMF Nodal /Node and SMF Node test cases.

The always-on PDU is requested from the UE with the PDU Establishment procedure IE and then based on the local policies the N/W accepts or rejects it with the Indication IE.

If PDU Session Modification Request includes "Always-On PDU session requested", SMF will send PDU Session Modification Command with "Always-On PDU session Indication(value:1)".

If PDU Session Modification Request includes UE Integrity Protection Maximum Data Rate and/or 5GSM capability without "Always-On PDU session requested", SMF will send PDU Session Modification Command with only Message type.

Emergency and Always-On PDU are mutually exclusive.

When enabled on AMF Nodal : 

• When "Support URLLC" is checked, at least one DNN tab in NAS-5G|SM must select the "Always-On PDU" option
• When "Support URLLC" is checked, any DNN tab with the "Always-On PDU" option selected must also select the "Network Slicing Info" option and configure the SST value as 2.

Spec Reference : TS23.725, TS29.244, TS38.413, TS24.501, TS23.501

Tcl Parameter: UeNas5gSmAlwaysOnEn_1

Available on AMF Nodal when Test Activity ="Inter Technology Mobility" and HandoffProtocol = "WiFi" and
N3IWF and Support ATSSS are enabled and "NAS-5G Version" >= 16.5.0. "MA PDU" cannot be enabled with "Emergency". 

Select for ATSSS (Access Traffic Steering, Switching, Splitting). When enabled, the Ue sends out Pdu session establishment request with "Ma Pdu Type".

Per the 23.501 section 5.32, The ATSSS feature enables a multi-access PDU Connectivity Service, which can exchange PDUs between the UE and a data network by simultaneously using one 3GPP access network and one non-3GPP access network. The multi-access PDU Connectivity Service is realized by establishing a Multi-Access PDU (MA PDU) Session, i.e. a PDU Session that may have user-plane resources on two access networks.

AMF Nodal support ATSSS Procedures when Non-roaming and Roaming with Local Breakout. According 23.502-gd0 -> 4.22.2.1

Limitations : Support split only. Both 3GPP and Non3GPP need to be registered. Balance rate is hard coded 3GPP 80% and Non3GPP 20%. Only works with AMF Node without SMF emulation. Handover is not supported.

Tcl Parameter: UeNas5gSmMaPduEn_1

Network Slicing Info

Select to enter the Network Slicing Info of DNN. Available when Number of Data Network Names is > 0 or when Max DNN Mode via TDF is enabled.

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

SST : 0 up to 255 (default =1)

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

Tcl Parameter: UeNas5gSmNssaiEn_1

SSC Mode

Select the SSC Mode (as described in 9.8.4.12 of 3GPP TS 24.501 [11]) of DNN. Available when Number of Data Network Names is > 0 and when Max DNN Mode via TDF is enabled.

Options : SSC Mode 1 (default), SSC Mode 2, SSC Mode 3

Tcl Parameter: UeNas5gSmSscMode_1

Enable to make UE’s PDU Session which will be connected to DNN_N support Secondary Authentication procedure. When enabled EAP Settings becomes available. EAP-TLS/EAP-TTLS is currently supported.

Available in AMF Nodal and SMF Nodal test cases when PDU Session Secondary Authentication is enabled,

“Username” in EAP Settings will be used to configure “DN-specific identity”(NAI).

For example, when # of UEs is 2 and # of PDUs/DNNs is 2,

Ex1) if Username in DNN 1/EAP Settings is #(10001)@domain and Username in DNN 2/EAP Settings is #(20001)@example, DN-specific identity will be configured as below:

Ex2) if only DNN2 has EAP Settings and Username in DNN 2/EAP Settings is #(20001)@example, DN-specific identity will be configured as below:

Tcl Parameter: UeNas5gSmDnnSecAuthEn_1

Available in AMF Node and SMF Node test cases when PDU Session Secondary Authentication is enabled. When enabled EAP Settings becomes available. EAP-TLS/EAP-TTLS is currently supported.

Select Reauthentication Delay (s) to trigger Re-authentication of PDU Session Secondary Authentication after establishment of PDU Session.

Range : 1 to 255

Default : 15

Tcl Parameter: SmfNas5gSmSecReauthDelayEn

Tcl Parameter: SmfNas5gSmSecReauthDelay

Timers

Select to enter PDU Session Authentication Command Retry timer (T3590) in seconds and the maximum number of retry attempts in T3590 Max Retry.

Range : 1 to 255 for T3590, 0 to 255 for T3590 Max Retry

Default : 15 for T3590, 0 for T3590 Max Retry

Tcl Parameter: SmfNas5gSmT3590Timer

Tcl Parameter: SmfNas5gSmT3590MaxRetry

On SMF Node test case, select AAA Protocol for the interface to an external DN-AAA server as per 3GPP 23.502 section 4.3.2.3 (Secondary authorization/authentication by an DN-AAA server during the PDU Session establishment). User has the option to choose whether the AAA protocol message is sent from SMF to AAA server directly or via UPF.

Options : RADIUS, Diameter

The following AAA protocols are supported.

• RADIUS
• Diameter, NAS App, TCP or SCTP

When Diameter is chosen as the protocol, "AAA Server Host" and "AAA Server Realm" text fields are enabled alongside "AAA Server Address" if Trigger Secondary Authentication is enabled.

Select Direct Connection to AAA Server for a direct connection to the AAA server.

Tcl Parameter: SmfNas5gSmAaaEn

Tcl Parameter: SmfNas5gSmAaaProtocol

Tcl Parameter: SmfNas5gSmAaaDirectConn

Max DNN Mode via TDF

Select to configure Number of Data Network Names (DNN) up to 3000.

When you select this option, you define only one DNN configuration set in the GUI which is applied to all DNNs. Use the TDF - (Apply Test Data File to DNN Configuration) to apply the different parameters to each DNN.

Not available for selection when PDU Type = "Per DNN" or when Enable E911 Call is enabled. Mutually exclusive with DNN with Starting SUPI Mode via TDF.

Tcl Parameter: UeNas5gSmMaxDnnModeEn

Apply Test Data File to DNN Configuration

Available when Max DNN Mode via TDF is enabled in AMF Nodal test case. The way to assign DNNs to UEs and PDUs is same as shown above in Data Network Name.

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

Each Row: DNN # (1 to 3000)

       ● Columns: parameters belong to each DNN configuration

Column Name     Value

DNN_NAME          Up to 100 characters , Example : dnn1.spirent.com

NSSAI                  SST: 0 up to 255 (default =1) ,  Example : When it is only SST, 1

                           SD: hex-string, maximum length = 6 (optional) , Example: If both SST and SD are used: 1;1a2b3c

SSC_MODE           1 ~ 2: 1(SSC Mode 1), 2(SSC Mode 2)

EMERGENCY_EN    0 ~ 1: 0(false), 1(true)

Example file : Nas5GSMMaxDnnModeEx.csv (for AMF Nodal)

Tcl Parameter: UeNas5gSmDnnCfgFile

Tcl Parameter: SmfNas5gSmDnnCfgFileEn

Tcl Parameter: SmfNas5gSmDnnCfgFile    

DNN with Starting SUPI Mode via TDF

Apply Test Data File to DNN and SUPI Configuration

Select to allocate the SUPI from the DNN entry in the TDF file. Each Row (Multiplier Label) is a different DNN. Same "DNN_NAME" in the TDF file is not supported. Available in AMF Nodal and SMF Nodal test cases. Not available for selection when PDU Type = "Per DNN" or when Enable E911 Call is enabled or PDU Session Secondary Authentication is enabled.

Mutually exclusive with Max DNN Mode via TDF.

If this option is enabled, a new TDF file "Apply Test Data File to DNN and SUPI Configuration" is added. The SUPI values will be allocated based on the STARTING_SUPI and its range of each DNN entry from this new TDF file. 

The TDF file with Starting SUPI and DNN names.

The available columns of new TDF files are: Each Row (Multiplier Label) is a different DNN. Same "DNN_NAME" in the TDF file is not supported.

Each row is a DNN entry. Each Row: DNN (1 to 3000)

When this feature is enabled, if the column "SUPI_RANGE" is not provided for the DNN entry, the range of the SUPI for each DNN will be determined by the number of UEs and number of DNN entries with unique starting SUPI of the TDF file. Then SUPI value for the UE will be allocated based on the STARTING_SUPI and its range of each DNN entry from this new TDF file. If the number of UEs is less than the number of DNN entries with unique starting SUPI, STARTING_SUPI range will set to 1 for each DNN entries so the allocation will be a round-robin fashion for such case.

When the column "SUPI_RANGE" is provided, if the sum of range of the DNN entries with unique starting SUPI in the TDF file is less than the number of UE/subscribers configured, a warning message will be given in the log so user could know. The TC will continue.

For the case of number of UE/subscribers is more than the sum of range of DNN entries with unique starting SUPI in the TDF file, all the additional UEs will be assigned SUPI from the last DNN entry.

If there are multiple PDU sessions per UE are configured, the column "PDU_INDEX" is used to identify the PDU session explicitly.  By default, each DNN entry will have PDU_INDEX as 1. The first PDU session associated with a particular UE will be assigned with the DNN entry's DNN_NAME with PDU_INDEX as 1 from the matched DNN entry based on UE's SUPI value; the 2nd PDU session with a particular UE will be assigned with the DNN entry's DNN_NAME with PDU_INDEX as 2 with same STARTING_SUPI from matched DNN, the 3rd PDU session with a particular UE will be assigned with DNN entry's DNN_NAME as 3 with same STARTING_SUPI from matched DNN and so on. If there are less DNN entries with same STARTING_SUPI configured for the PDU sessions for a particular UE with a matched DNN entry, the DNN entry's DNN_NAME with PDU_INDEX as 1 is used.

The existing field "Number of Data Network Names" will increase to 3000. For the case of per PDU per UE, the max number of DNN entries which having unique starting SUPI will be 3000; For the case of multiple PDUs per UE case, the max number of DNN entries which having unique starting SUPI will be 3000/# of PDUs per UE. For example, if the # of PDU per UE is 15, then the max number of DNN entries which having unique SUPI will be 200, which means only having 200 DNN entries counted when assigning SUPI for UEs.

Examples if this feature is applied:

Case 1 - One PDU session per UE case, without SUPI_RANGE defined: There are 100 UEs, and there are 10 DNNs defined, each DNN has its unique starting SUPI. Then 10 SUPIs of each DNN will be allocated to UE. e.g. first 10 UEs will get SUPI numbers from 1st DNN, second 10 UEs will get SUPI numbers from 2nd DNN and so on... 

Case 2 - One PDU session per UE case, with SUPI_RANGE defined: There are 100 UEs, and there are 5 DNNs defined, each DNN has its unique starting SUPI and the range of SUPI. Then the SUPIs of each DNN will be allocated to UE according to its range. 

The following table illustrates the above Case 2 in more detail:

Case 3 - Multiple PDU sessions per UE case without SUPI_RANGE defined:

There are 100 UEs, 2 PDUs per UE, and 10 DNNs defined. Then each DNN will have its starting SUPI value and will be identified explicitly by PDU_INDEX. Only the starting SUPI of the DNN entry with PDU_INDEX as 1 will be counted as the # of DNN entries when assigning SUPI to a UE. So 20 SUPIs of each DNNs with PDU_INDEX as 1 will be allocated to UE e.g. first 20 UEs will get SUPI numbers from 1st DNN entry with PDU_INDEX as 1, second 20 UEs will get SUPI numbers from next DNN entry with PDU_INDEX as 1 and so on...and 1st PDU of a UE will get the DNN with PDU_INDEX as 1 entry's DNN name in that pool, 2nd PDU of this UE will get the DNN with PDU_INDEX as 2 entry's DNN name in that pool and so on... 

The following table illustrates the above Case 3 in more detail:

Case 4 - Multiple PDU sessions per UE case with SUPI_RANGE defined:

There are 100 UEs, 2 PDUs per UE, and 10 DNNs defined. Then each DNN will have its starting SUPI value and SUPI_RANGE provided. And the DNN will be identified explicitly by PDU_INDEX. Only the SUPI_RANGE value and the starting SUPI of the DNN entry with PDU_INDEX as 1 will be used when assigning SUPI to a UE. 

The following table illustrates the above Case 4 in more detail:

Tcl Parameter: UeNas5gSmDnnSupiCfgFileEn

Tcl Parameter: UeNas5gSmDnnSupiCfgFile

Select to enable DRB Level Data Forwarding during Handover. Available in AMF Nodal tet case when "Test Activity" is "Inter Technology Mobility" with Handoff Type as "Handover", or  "Intra-AMF Mobility" and "Inter-AMF Mobility" with Handoff Type as "N2". The DRB to QoS Flows mapping information will be used to support DRB level forwarding during the N2-based Inter NG-RAN handover and 4G to 5G with N26 interface Handovers .

On receipt of the "PDU Session Establishment Accept" at a NR-RAN node,  it generates a DRB ID based on the received 5QI value in the "Authorized QoS Flow descriptions" and the user defined DRB profile table.  One DRB ID will be created between one UE and NR-RAN for one DRB profile, which associate the QoS flows with 5QIs.  One DRB ID value will be reserved for the QoS flows with 5QI value not defined in the DRB to 5QI mapping table for each PDU for a particular UE. The value for DRB ID is 1 to 32 per UE. And DRB ID value is uniquely within one UE.

Once the DRB to QoS flows information is created, it can be included in the corresponding IEs in the messages related to the handover procedure to support DRB level data forwarding.

In addition, the Target NG-RAN can receive the downlink data from the Source NG-RAN for DRB level data forwarding for the User Plane data traffic.

Select to include Data Forwarding Accepted IE in the Handover Request Acknowledge Transfer IE for DRB level forwarding.

Select to include DL Forwarding UP TNL Information IE within Data Forwarding Response DRB List IE within the Handover Request Acknowledge Transfer IE. When enabled, you can also select "Include Session Level DL Forwarding UP TNL Information IE" to include top level (session level) DL Forwarding UP TNL Information IE in addition to include DL Forwarding UP TNL Information IE within Data Forwarding Response DRB List IE in the Handover Request Acknowledge Transfer IE.

Select to indicate the Number of 5QI to DRB mapping profiles. If the value is not 0, the number of rows for 5QI to DRB mapping profiles table will be added. The max. allowable number is (32 - # of PDU per UE). For example, if 2 PDUs per UE, then the max. allowable number will be 32 - 2 = 30. Range: 0 to 31, Default : 0

The 5QI List values of QoS flow which can be mapped to a Data Radio Bearer (DRB). The 5QI value is range of 0-255. The multiple 5QI values is separated by ",". For example: 8,9 . The 5QI value should be unique for the table. The same 5QI value should not be repeated for multiple entries. No duplicated entry (ordered or non-ordered) is allowed.

Range: 0 to 31, Default : 0

Tcl Parameter: UeNas5gSmHoDrbFwdEn

Tcl Parameter: UeNas5gSmDataFwdAcceptIeEn

Tcl Parameter: UeNas5gSmDrbDlFwdUpTnlInfoEn

Tcl Parameter: UeNas5gSmSessDlFwdUpTnlInfoEn

Tcl Parameter: UeNas5gSmNumDrbProfiles

Tcl Parameter: UeNas5gSm5qiToDrbToProfile_1

PDU IPv6 Address Pool

Enter valid IPv6 Address pool for PDU. As of release 17.4, you must enter a valid IPv6 prefix, requires "[ipv6-address]/[prefix-length]". The valid range for the prefix-length is: 9 to 64.

PDU IPv6 Address Pool [SmfNas5gSmPduV6AddrPool=2001:0DB8:0:CD30::] Prior to release 17.4

PDU IPv6 Address Pool [SmfNas5gSmPduV6AddrPool=2001:0DB8:0:CD30::/64] upgraded (17.4 until 19.4)

Tcl Parameter: SmfNas5gSmPduV6AddrPool

Additional IPv6 Pools

Select to enter additional IPv6 Address Pools. Available in AMF Node test case.

The IPv6 Address Pool becomes available for input.

Range: 1

Tcl Parameter: SmfNas5gSmAddPduV6AddrPoolEn

Tcl Parameter: SmfNas5gSmAddPduV6AddrPool

IPv6 Address Pool

Enter an additional IPv6 Address Pool. Available in AMF Node test case when Additional IPv6 Pools is enabled.

Tcl Parameter: SmfNas5gSmPduV6AddrPool_1

PDU IPv4 Address Pool

Enter valid IPv4 Address pool (without mask) for PDU.

If UE DHCPV4 IP Address is enabled on AMF Node or SMF Node, PDU IPv4 Address Pool is not available for input on NAS-5G/SM Tab.

Tcl Parameter: SmfNas5gSmPduV4AddrPool

Additional IPv4 Pools

Select to enter additional IPv4 Address Pools. Available in AMF Node test case.

The IPv4 Address Pool becomes available for input.

If UE DHCPV4 IP Address is enabled on AMF Node , Additional IPv4 Pools, and IPv4 Address Pool are not available for input on NAS-5G/SM Tab.

Range: 1

Tcl Parameter: SmfNas5gSmAddPduV4AddrPoolEn

Tcl Parameter: SmfNas5gSmAddPduV4AddrPool

IPv4 Address Pool

Enter an additional IPv4 Address Pool. Available in AMF Node test case when Additional IPv4 Pools is enabled.

If UE DHCPV4 IP Address is enabled on AMF Node , Additional IPv4 Pools, and IPv4 Address Pool are not available for input on NAS-5G/SM Tab.

Tcl Parameter: SmfNas5gSmPduV4AddrPool_1

Available in UPF Nodal when PDU Type = Ethernet. Enter a valid MAC address with colon or dash delimeters. Per 3GPP 23501 - 5.6.10.2 - Support of Ethernet PDU Session Type.

Limitations for PDU type = Ethernet : 

• UPF Nodal does not support SDF filter.
• UPF Node needs to pre-resolve Network Host IP address in order to forward uplink traffic to the Network Host.
• The following checkboxes are disabled : In QoS Settings and Modified QoS Settings, Number of Filters and Modify Packet Filters.
• The N4|PFCP UP feature "UEIP" is not supported

Default : F0:F0:F0:11:11:11

Tcl Parameter: SmfNas5gSmPduMacAddrPool

Available in SMF Node and AMF Nodal with SMF/UPF emulation (NAS-5G SM SMF tab). 

Enter the time used when the SMF itself triggers paging without Data Notification event in Network Triggered Service Request procedure described in clause 4.2.3.3 in TS23.502.

It is the special option to initiate Network Triggered Service Request procedure without exchanging the traffic data between UE and Network.

Range : 0 = Disabled or 100 to 4294967295 (milliseconds)

Default : 0

Tcl Parameter: SmfNas5gSmTrigPagingTime

Available in SMF Node and AMF Nodal with SMF/UPF emulation (NAS-5G SM SMF tab).  

Enter the time that SMF waits for the result of paging from AMF after initiating the network triggered service request procedure (step 3a) in Figure 4.2.3.3-1: Network Triggered Service Request in TS23.502.).

By default, it is disabled (not used) because it is expected that the AMF will always inform the SMF of the result of paging. However, if it is needed to consider the abnormal situation that the AMF will not inform the SMF of the result for some reason, the timer should be longer than T3513 (described in “Figure 5.6.2.2.1.1: Paging procedure” in TS24.501) that AMF uses for the paging procedure.
If this timer expires, the SMF will re-enter idle mode and re-initiate the network triggered service request procedure when receiving Data Notification from UPF or “Trigger Paging Time” expires.

Reference: Figure 4.2.3.3-1 in TS23.502

Range : 0 = Disabled or 0 to 1000 (seconds)

Default : 0

Tcl Parameter: SmfNas5gSmPagingGuardTime

Available in SMF Node, AMF Node with SMF Emulation and AMF Nodal with SMF/UPF emulation (NAS-5G SM SMF tab).  

After UE registration, if a UE sends "PDU session establishment request" and receives the "PDU session establishment reject" with 5GSM cause and back-off timer. The UE can re-attempt the "PDU session establishment request" after the Back-Off Timer expires.

Range : 0 to 35712000 (seconds)

Default : 0

Tcl Parameter: SmfNas5gSmBackoffTime

PDU Release Option

No longer used as of Release 19.8. See additional details below.

PDU Release Time (ms)

Indicates the time an established PDU is released in milliseconds. Available in AMF Nodal, AMF Node, SMF nodal and SMF Node.

Determines the time the UE needs for keeping the old PDU session during the transition of Change of SSC Mode 3 PSA with Multiple PDU Sessions. If it is set to 0, the UE will never release PDU session from its end. Otherwise the UE will initiate UE requested PDU Session Release when the corresponding timer expires unless the PDU session is already released by the network.

Range: 0 or 1000 to 4294967295 with a default of 0 in AMF and SMF Nodal test cases

Range : 1000 to 4294967295 with a default of 10000 in AMF Node and SMF Node test cases

Default: 1000

As of release 19.8, the "PDU Release Time (ms)" variable has being changed (SmfNas5gSmPduReleaseTime->SmfNas5gSmPduRlsTime) and the "PDU Release Time (ms)" field has been moved to the General panel and the PDU Release Option has been removed and replaced by the Change of SSC Mode 2 or 3 PDU Session Anchor Panel. 

Upgrade from "No Action":
      SM - PDU Release Time (ms) [SmfNas5gSmPduRlsTime=null->0] set to default value
      SM - SSC Mode 2/3 Option [SmfNas5gSmSscMode23Opt=null->0] set to default value

Upgrade from "Normal Release for All":
      SM - PDU Release Time (ms) [SmfNas5gSmPduReleaseTime->SmfNas5gSmPduRlsTime=1111] upgraded (19.8 until 22.8)
      SM - SSC Mode 2/3 Option [SmfNas5gSmSscMode23Opt=null->0] set to default value

Upgrade from "SSC Mode 2 Only Release with Reactivation Requested":
      SM - SSC Mode 2/3 Option [SmfNas5gSmSscMode23Opt=1] upgraded (19.8 until 22.8)
      SM - Delay Time (ms) [SmfNas5gSmSscMode23DelayTime=55555] upgraded (19.8 until 22.8)
      SM - PDU Release Time (ms) [SmfNas5gSmPduRlsTime=55555->0] upgraded (19.8 until 22.8)
      SM - SSC Mode 3 with Multiple PDU Sessions [SmfNas5gSmSscMode3MultSessEn=false] upgraded (19.8 until 22.8)
      SM - SSC Mode 2 with Different PDU Sessions [SmfNas5gSmSscMode2DiffSessEn=null->true] set to default value

Tcl Parameter: SmfNas5gSmPduReleaseTime

Tcl Parameter: SmfNas5gSmPduRlsTime

Tcl Parameter: UeNas5gSmPduReleaseTime

Available in AMF and SMF Node test cases and on AMF Nodal NAS-5G|SM|SMF tab for SMF Emulation.

Enter Path Switch Request Ack Transfer Delay in milliseconds to emulate the delay between N4 Session Modification Response and Nsmf_PDUSession_UpdateSMContext Response.

Range : 0 to 30000

Default : 0

Tcl Parameter: SmfNas5gSmPathSwitchAckDelay

Select the Option Type for change of SSC Mode 2 or PDU Session Anchor. Available in AMF Node.

Options : No Action, Timer Based, Location Based.

If either "Timer Based" or "Location Based" option is selected, you can select the desired flavors of change:  SSC Mode 2 with Different PDU Sessions Only,  SSC Mode 3 with Multiple PDU Sessions Only or both.

On SMF Node test case and on the AMF Node test case with SMF Emulation: 

A "Location Based" UPF selection option has been added in addition to "Manual Configuration" (previously named "UPF Settings"). With the "Location Based" option, each UPF SUT is configured with a serving area (i.e. a list of supported TAIs up to 16). The SMF will dynamically select a UPF SUT based on current UE location during PDU Session Establishment. If no match is found, the first available UPF SUT will be selected.

For the Location Based option ,the UPF N4 Node/Number of SUTs and Multiple SUTs per N4 Node must both be selected on Network Devices. 

Location Based option is limited to Xn Handover only for Change of SSC Mode 2 or 3 PDU Session Anchor.

Tcl Parameter: SmfNas5gSmSscMode23Opt

AMF Node with SMF Emulation:

In prior versions, we supported a trigger for Change of SSC Mode 2 PDU Session Anchor with Different PDU sessions on the SM tab. This trigger is now combined with the trigger for Change of SSC Mode 3 PDU Session Anchor with Multiple PDU sessions under the "Timer Based" option. Once the delay time expires, the selected trigger(s) (SSC Mode 2 Only, SSC Mode 3 Only or both) will take effect. For SSC Mode 3 only, the PDU Session Address Lifetime determines the maximum time the network is willing to maintain the PDU session, which will be sent to the UE in the PCO in PDU Session Modification Command. If it is set to 0, it will not be notified to the UE but both sides will assume a default value of 60s. The SMF will start Timer 3593 using this value once PDU Session Modification Complete is received. When Timer 3593 expires, the SMF will initiate network requested PDU Session Release procedure unless the PDU session is already released by the UE. Similarly on the UE side, we have an SSC Mode 3 PDU Release Time which determines the time the UE needs for keeping the old PDU session. If it is set to 0, the UE will never release PDU session from its end. Otherwise the UE will initiate UE requested PDU Session Release when the corresponding timer expires unless the PDU session is already released by the network.

For now the "Timer Based" option does not guarantee Change of PDU Session Anchor as we select UPF SUTs in a round-robin fashion or through DNN based manual configuration. To test Change of PDU Session Anchor you can select the "Location Based" option. See below for "Location Based" UPF selection. Currently this option is limited to SSC Mode 2 or 3 Change of PSA following an Xn handover.

Tcl Parameter: SmfNas5gSmSscMode2DiffSessEn

Available in AMF Node when Option = Timer Based.

The delay time, in milliseconds, for triggering Change of SSC Mode 2 or 3 PSA after the PDU session enters established state.

Range: 1000 to 4294967295

Default : 15000

Tcl Parameter: SmfNas5gSmSscMode23DelayTime

Select to enable SSC Mode 3 with Multiple PDU Sessions. Available in AMF Node when Option = Timer Based or Location Based. The Reserve PDU Session for SSC Mode 3 must be enabled in order to test Change of SSC Mode 3 PDU Session Anchor with Multiple PDU Sessions. If you don't enable this option (i.e. no peer session) or the peer session is not free or the UE is running of PSIs when the PDU Session Modification Command is received from the SMF, the UE will reject PDU modification with cause "insufficient resources".

Tcl Parameter: SmfNas5gSmSscMode3MultSessEn

Available in AMF Node test case when SSC Mode 3 with Multiple PDU Sessions is enabled.

PDU Session Address Lifetime (s) - Determines the maximum time the network is willing to maintain the PDU session during the Change of SSC Mode 3 PSA with Multiple PDU Sessions, which will be sent to the UE in the PCO in PDU Session Modification Command. If it is set to 0, it will not be notified to the UE but both sides will assume a default value of 60s. The SMF will start Timer 3593 using this value once PDU Session Modification Complete is received. When Timer 3593 expires, the SMF will initiate network requested PDU Session Release unless the PDU session is already released by the UE. (See above for SSC Mode 3 PDU Release Time).

Range : 0 to 65535

Default : 0

Tcl Parameter: SmfNas5gSmSscMode3PduAddrLifeTime

To test Change of PDU Session Anchor you can select the "Location Based" option. Currently this option is limited to SSC Mode 2 or 3 Change of PSA following an Xn handover.

To use this option, the "Location Based" UPF selection on N4 | PFCP must be checked.

Avaialble in AMF Node test case when Option = Location Based.

Select for Xn Handover. 

Tcl Parameter: SmfNas5gSmSscMode23XnHoEn

Enable PDU Configuration

Select to enable PDU Configuration. Available in UPF Nodal test case.

Tcl Parameter: SmfNas5gSmPduConfigEn

Data Network Name

Available when Enable PDU Configuration is selected. Available in UPF Nodal test case.

Select the Data Network Name.  

Range: 1 to Number of Data Network Names (see QoS settings below)

Tcl Parameter: SmfNas5gSmNtwkNameIdx_1

Select the enable Maximum Integrity Protected Data Rate Uplink. Available in AMF Nodal test case when NAS-5G Version is 15.2.0 or higher. 

Options : 64kbps, NULL, Full Data Rate (default)

Tcl variable is "UeNas5gSmMaxIntegRateUl_<pdu>"

Tcl Parameter: UeNas5gSmMaxIntegRateUl_1

Select the enable Maximum Integrity Protected Data Rate Downlink. Available in AMF Nodal test case when NAS-5G Version is 15.2.0 or higher. 

Options : 64kbps, NULL, Full Data Rate (default)

Tcl variable is "UeNas5gSmMaxIntegRateDl_<pdu>"

Tcl Parameter: UeNas5gSmMaxIntegRateDl_1

Number of Data Network Names

Enter maximum number of Data Network Names (DNN) supported per PDU session. Available in AMF Node, SMF Node and UPF Nodal test cases.

Range: 1 to 15

Default:1

Tcl Parameter: SmfNas5gSmNumNtwkNames

Limit QoS Flows per PDU Session

Enter the Limit QoS (Quality of Service) Flows supported per PDU Session. Available in AMF Nodal, AMF Node, SMF Nodal, SMF Node and UPF Nodal test cases. Used for Test Server memory allocation. Sets the maximum number of flows supported per PDU.

Range: 1 to 16

Default:1

Tcl Parameter: SmfNas5gSmNumFlows

Tcl Parameter: UeNas5gSmNumFlows

Limit Signaled Rules per PDU Session

Enter the limit Signaled Rules Flows supported per PDU Session. Available in AMF Nodal, AMF Node, SMF Nodal, SMF Node and UPF Nodal test cases. Used for Test Server memory allocation. Sets the maximum number of signaled rules supported per PDU.

Range: 1 to 16

Default: 1

Tcl Parameter: SmfNas5gSmNumSigRules

Tcl Parameter: UeNas5gSmNumSigRules

Data Network Name

Enter the name of the Data Network (DNN) supported per PDU session. Available in AMF Node, SMF Node and UPF Nodal test cases.

Default: dnn.spirent.com

Tcl Parameter: SmfNas5gSmNumNtwkName_1

Tcl Parameter: SmfNas5gSmDataNtwkName_1

SST

Available on SMF Nodal test case on Interface NAS-5G.

Available on SMF Node when Single NSSAI is enabled.

Enter the SST (Slice / Service Type).

Range : 0 to 255

Default : 1

Tcl Parameter: UeNas5gSmSst_1

SD

Available on SMF Nodal test case on Interface NAS-5G.

Available on SMF Node when Single NSSAI is enabled.

Enter the SD (Slice Differentiator).

Range : 1 to 6 Hex characters

Default : 0

Tcl Parameter: UeNas5gSmSd_1

NSI ID

Available on SMF Nodal test case on Interface NAS-5G.

Select to enter the NSI ID (Network Slice Information identifier).

Range : 1 to 64 characters

Tcl Parameter: UeNas5gSmNsiIdEn_1

Tcl Parameter: UeNas5gSmNsiId_1

Available on SMF Nodal test case on Interface NAS-5G. Available when Test Activity is “Intra-AMF Mobility” and “Handoff Type” is “Xn”, or when Test Activity is “Command Mode” or “Sequencer” and “Num gNBs per AMF” in Network Devices/gNB User Node Tab is 2 or more.

Select whether to change UE security policy in Security Indication in Path Switch Request Transfer which will be sent to SMF by target gNB during Xn Mobility. 

If this information is provided by SMF during PDU Session Establishment procedure or N2 Handover procedure, gNB should store it and target gNB should include the stored information in Path Switch Request Transfer which will be sent to SMF during Xn Mobility. If this option is enabled, Security Indication in Path Switch Request Transfer will include the configured values instead of the stored values.

Select the value of Integrity Protection Indication defined in 3GPP TS 38.413, 9.3.1.27.

Options : Required, Preferred, Not Needed (default)

Select the value of Confidentiality Protection Indication defined in 3GPP TS 38.413, 9.3.1.27.

Options : Required, Preferred, Not Needed (default)

Tcl Parameter: UeNas5gSmManipSecIndUpSecPolicyEn_1

Tcl Parameter: UeNas5gSmManipSecIndIntegProtectInd_1

Tcl Parameter: UeNas5gSmManipSecIndConfProtectInd_1

Available on SMF Node test case on Interface NAS-5G. Available when NAS-5G Version 16.5.0 or greater and the N4|PFCP ATSSS-LL Supported Features option is checked.

Support Access Traffic Switching: The procedure that moves all traffic of an ongoing data flow from one access network to another access network in a way that maintains the continuity of the data flow. Access traffic switching is applicable when Home-routed Roaming (UE registered to the same PLMN). Between one 3GPP access and one non-3GPP access.

Support Access Traffic Steering: The procedure that selects an access network for a new data flow and transfers the traffic of this data flow over the selected access network. Access traffic steering is applicable between one 3GPP access and one non-3GPP access.

Based on 5.32.6 of 3GPP TS 23.501 and 3GPP TS 24.193

Select Limit ATSSS Rules per PDU Session to become configurable. 

Range : 1 to 8, default : 3

Tcl Parameter: SmfNas5gSmNumAtssRules

Select for Number of ATSSS Rules to become configurable. 

Tcl Parameter: SmfNas5gSmNumAtssUlNum_1

Range : 1 to 8, default : 1

Rules :

Select the Steering Function.

Options : ATSSS-LL Functionality (default)

Select the Steering Mode.

Options : Load Balancing (default)

Select the Steering Mode Information.

Options : 100% over 3GPP and 0% over non-3GPP,          
     90% over 3GPP and 10% over non-3GPP,            
     80% over 3GPP and 20% over non-3GPP, (default)
     70% over 3GPP and 30% over non-3GPP, 
     60% over 3GPP and 40% over non-3GPP, 
     50% over 3GPP and 50% over non-3GPP, 
     40% over 3GPP and 60% over non-3GPP,
     30% over 3GPP and 70% over non-3GPP,
     20% over 3GPP and 80% over non-3GPP,
     10% over 3GPP and 90% over non-3GPP,
     0% over 3GPP and 100% over non-3GPP           

Tcl Parameter: SmfNas5gSmAtssSteerFunc_1

Tcl Parameter: SmfNas5gSmAtssSteerMode_1

Tcl Parameter: SmfNas5gSmStssSteerModeInfo_1

Limitations: 

• There is a little of bit performance impact to data throughput when ATSSS is enabled.
• MPTCP is not supported yet.
• ATSSS traffic Descriptor, AMF Nodal can only support "Match All", "Low Remote Port", "High Remote Port", "Ipv4 Remote Address", "Ipv6 Remote Address", "Protocol ID", "DNN Type". For other traffic Descriptors, AMF Nodal will return "False" to the traffic match. 
• 24.193 > 6.1.4 Network steering functionalities information is not supported yet.
• 24.193 > 6.1.5 Measurement assistance information is not supported yet.

LADN Indicator

Select to indicate DNN is a LADN (Local Area Data Network) DNN. The checkbox is available to enable when Number of PDUs is greater than 1,  NAS Version >= 15.1.0 and Number of DNNs is > than Number of PDUs.

Per TS 23.501 "5.6.5 Support for Local Area Data Network".

Tcl Parameter: SmfNas5gSmDnnLadnIndEn_1

Available in SMF Node when N7 Interface and Traffic Steering are enabled. DN (Data Network) Access Identifier: Identifier of a user plane access to one or more DN(s) where applications are deployed.

Select the Number of DNAI (0 to 8) and enter the DNAI in the table provided. When the "DNAI" table is populated with DNAI names, for each DNAI, there is a sub-tab for each DNN under the N4 tab. Each DNAI tab can be configured with one PSA or one ULCL + one PSA. The purpose of this tab is to configure uplink traffic path for the DNAI. For example, if a DNAI is configured with ULCL 4 + PSA 2, then the uplink data traffic towards this DNAI will be routed through ULCL 4 and PSA 2.

Range : 0 to 128 characters

Tcl Parameter: SmfNas5gSmDnaiNum_1

Tcl Parameter: SmfNas5gSmDnai_1

Enable to trigger Secondary Authentication procedure during PDU Session establishment procedure with DNN_N. 

Available in AMF Node and SMF Node when PDU Session Secondary Authentication is enabled.

In SMF Node TC, when AAA Protocol is enabled, AAA Server Address becomes available to enter the AAA Server Address. Enter a valid IPv4 or IPv6 address.

In SMF Node TC, when AAA Protocol and Diameter are enabled, AAA Server Host and AAA Server Realm become available. 

Enter the AAA Server Host. Default : Spirent.com

Enter the AAA Server Realm. Default : NAS.Spirent.com

Tcl Parameter: SmfNas5gSmDnnTriggerSecAuthEn_1

Tcl Parameter: SmfNas5gSmDnnAaaServerAddr_1

Tcl Parameter: SmfNas5gSmDnnAaaServerHost_1

Tcl Parameter: SmfNas5gSmDnnAaaServerRealm_1

Select to Include Security Indication IE on NGAP messages (ngap.pDUSessionResourceSetupRequestTransfer.) Spec Reference : 3GPP TS 38.413, 8.2.1.2 General (PDU Session Resource Setup Request), 3GPP TS 33.501

Available on AMF Node with SMF emulated, gNB CU Node and SMF Node test cases. Fireball mode is not supported.

Tcl Parameter: SmfNas5gSmSecurityIndEn_1

Spec Reference : Security Indication IE specification in 3GPP TS 38.413, 9.3.1.27

Available in UPF Nodal test case when Enable Usage Report Rules is selected on N4 interface.

Select whether to use session level usage report rule instead of usage report rule in flow / rule. If it is enabled, all PDRs belonging to the session are associated with this Usage Report Rule.

Select the Session Level Usage Report Rule. 

Tcl Parameter: SmfNas5gSmSessLvlUsageRptRuleEn_1

Tcl Parameter: SmfNas5gSmSessLvlUsageRptRule_1

PDU Session AMBR

Enter Session AMBR (Aggregate Maximum Bit Rate) for PDU 1.

Enter Max Bit Rate UL.

Range: 1 to 65535

Select Units: 1 KBPS, 4 KBPS, 16 KBPS, 64 KBPS, 256 KBPS, 1 MBPS, 4 MBPS, 16 MBPS, 64 MBPS, 256 MBPS, 1 GBPS, 4 GBPS, 16 GBPS, 64 GBPS, 256 GBPS, 1 TBPS, 4 TBPS, 16 TBPS, 64 TBPS, 256 TBPS, 1 PBPS, 4 PBPS, 16 PBPS, 64 PBPS, 256 PBPS

Enter Max Bit Rate DL.

Range: 1 to 65535

Select Units: 1 KBPS, 4 KBPS, 16 KBPS, 64 KBPS, 256 KBPS, 1 MBPS, 4 MBPS, 16 MBPS, 64 MBPS, 256 MBPS, 1 GBPS, 4 GBPS, 16 GBPS, 64 GBPS, 256 GBPS, 1 TBPS, 4 TBPS, 16 TBPS, 64 TBPS, 256 TBPS, 1 PBPS, 4 PBPS, 16 PBPS, 64 PBPS, 256 PBPS

Tcl Parameter: SmfNas5gSmAmbrMaxBrUl_1

Tcl Parameter: SmfNas5gSmAmbrMaxBrUlUnits_1

Tcl Parameter: SmfNas5gSmAmbrMaxBrDl_1

Tcl Parameter: SmfNas5gSmAmbrMaxBrDlUnits_1

Flow 1-16 Details

Enter Flow 1-16 details.

QoS Flow Descriptions

Select QoS Flow Descriptions.

Number of Signaled Rules

Enter the number of Signaled Rules.

QRI

Enter the QoS Rule Identifier. Select the "..." for the Current QRI Assignments pane.

Tcl Parameter: SmfNas5gSmQosRuleId_1_1_1

Precedence

Enter Precedence.

Range: 0 to 255

Default: 255

Tcl Parameter: SmfNas5gSmPreced_1_1_1

Select to enter the Application Id. Reference : TS 29.212 [8]. Available in AMF Node (with SMF emulation), SMF Node, and UPF Nodal test cases.

In the control plane, include the IE of Application ID when sending pfcp messages (establish, modification, etc...) in UPF Nodal.

Enter up to 128 Characters.

Tcl Parameter: SmfNas5gSmAppIdEn_1_1_1

Tcl Parameter: SmfNas5gSmAppId_1_1_1

Select to include the Activate Predefined Rule IE in the PFCP Session Establishment Request message.

Activate Predefined Rules is a conditional IE in Create PDR IE within PFCP Session Establishment Request.

Available in AMF Nodal with SMF/UPF Node Emulation, AMF Node with SMF simulation, SMF Node and UPF Nodal.

Limitation : This feature only provides a way in GUI to  allow users to config the Activate Predefined Rule in control plane as needed.  There is no change in user plane which means no handling for the newly added Activated Predefined Rules IE.

Enter a Printable-String REGEX that allows 1 to 128 characters in Uplink and Downlink. 

Tcl Parameter: SmfNas5gSmActPredefinedRuleEn_1_1_1

Tcl Parameter: SmfNas5gSmActPredefinedRule_1_1_1

Select to include the Network Instance IE under Create PDR, PDI IE when configured on the QoS Rule basis. Available in AMF Nodal with SMF/UPF Node Emulation, AMF Node with SMF simulation, SMF Node and UPF Nodal.

Also available AMF Node with SMF simulation, SMF Node and UPF Nodal in the DNN Tab, near the top of the tab. When it is enabled there, the "Network Instance" option and its "Uplink" and "Downlink" fields in the QoS Rule tabs is greyed out. When this Network instance is configured on DNN basis, it is applicable to all corresponding PDRs, FARs and Traffic Endpoints (if any) in the uplink, downlink or CP-function directions.

Spec reference - 3GPP TS 29.244 - Interface between the Control Plane and the User Plane Nodes; Stage 3.

Limitation : This feature only provides a way in GUI to  allow users to config the Network Instance in control plane as needed.  There is no change in user plane which means no handling for the newly added Network Instance IE.

Enter a Printable-String REGEX that allows 1 to 128 characters in Uplink/Downlink and CP-Function. 

Tcl Parameter: SmfNas5gSmNwInstEn_1_1_1

Tcl Parameter: SmfNas5gSmNwInstUplink_1_1_1

Tcl Parameter: SmfNas5gSmNwInstDownlink_1_1_1

Tcl Parameter: SmfNas5gSmNwInstCpFunc_1_1_1

Select a usage report rule. The value is chosen from the pull down list of the Number of Usage Report Rules URR rules defined in the N4/PFCP.  

Range : None to 10

Tcl Parameter: SmfNas5gSmUsageReportRule_1_1_1

Number of Filters

Enter Number of Filters

Range: 1 to 15

Tcl Parameter: SmfNas5gSmNumFilters_1_1_1

Filter (1 to 15)

Enter Filters (1 to 15) details.

Select Direction.

Options: Pre-Rel 7 (default), Downlink, Uplink, Bi-Directional

Tcl Parameter: SmfNas5gSmDirection_1_1_1_1

Select Match-all. All criteria will be matched.

Tcl Parameter: SmfNas5gSmMatchallEn_1_1_1_1

Select the Steering Function. 

Options : ATSSS-LL Functionality (default)

Select the Steering Mode.

Options : Load Balancing (default)

Select the Steering Mode Information.

Options : 100% over 3GPP and 0% over non-3GPP,          
     90% over 3GPP and 10% over non-3GPP,            
     80% over 3GPP and 20% over non-3GPP, (default)
     70% over 3GPP and 30% over non-3GPP, 
     60% over 3GPP and 40% over non-3GPP, 
     50% over 3GPP and 50% over non-3GPP, 
     40% over 3GPP and 60% over non-3GPP,
     30% over 3GPP and 70% over non-3GPP,
     20% over 3GPP and 80% over non-3GPP,
     10% over 3GPP and 90% over non-3GPP,
     0% over 3GPP and 100% over non-3GPP           

Tcl Parameter: SmfNas5gSmAtssDlSteerFunc_1_1_1

Tcl Parameter: SmfNas5gSmAtssDlSteerMode_1_1_1

Tcl Parameter: SmfNas5gSmAtssDlSteerModeInfo_1_1_1

QoS Modification

Select to include QoS Modification panel. Available on AMF node, SMF Node and UPF Nodal test cases when Version >= 15.2.0 and NGAP Version >= 15.2.0, Disabled when UE-Requested PDU Session Modification is enabled.

Available on AMF Nodal test case when UE-Requested PDU Session Modification is enabled.

Select to create new QoS Flow during PDU Session Modification.

A typical network initiated QoS flow modification scenario modifies both QoS flow and QoS rule, and affects both N1 and N2 layer. The PDU Session Modification Command is embedded within PDU Session Resource Modify Request and contains both QoS rules and QoS flow descriptions IE.

It is possible to have an N1 or QoS rule only modification. In this case, the PDU Session Modification Command is embedded within Downlink NAS Transport and there is no QoS flow descriptions IE in the N1 message. This scenario can be simulated by LS if you set the Action Type to Modify Existing QoS Flow but do not select any flow parameters except for the QFI.

It is also possible to have a QoS flow only modification. In this case, the PDU Session Modification Command is embedded within PDU Session Resource Modify Request but there is no QoS rules IE in the N1 message. This scenario can be simulated by LS if you set the Action Type to Modify Existing QoS Flow and the Number of Signaled Rules to 0.

UE initiated QoS modification is similar to the network initiated case, except there is an additional triggering N1 message PDU Session Modification Request embedded within Uplink NAS Transport.

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

3GPP TS 24.501 Non-Access-Stratum (NAS) protocol for 5G System (5GS)

3GPP TS 38.413 - NG-RAN;  NG Application Protocol (NGAP)

3GPP TS 29.244 - Interface between the Control Plane and the User Plane Nodes; Stage 3

Tcl Parameter: SmfNas5gSmModQosModEn_1

Tcl Parameter: UeNas5gSmModQosModEn_1

Number of Modifications

Enter the number of modification configuration sets for Ue-Requested PDU modification event. Available on AMF Nodal test case when UE-Requested PDU Session Modification is enabled. If modification configuration sets are configured, mod N will be applied in order when PDU session is established. Mod N+1 will be applied first and then mod N+1 will be applied in order after Mod N is done.

Number of Modifications are restricted to 1, 2 or 3 on SMF Node and UPF Nodal test cases.

Enter number of Modifications for nw-requested pdu modification events.

Range : 1 to 10

Default : 1

Tcl Parameter: SmfNas5gSmModNumMods_1

Tcl Parameter: UeNas5gSmModNumMods_1

Use QFI to Match Flow to Delete

Select to use QFI to Match flow to delete.

Note : QFI only makes sense for delete or modify existing flow. For Create New QoS Flow, no QFI is provided because QFI is allocated by the network instead of UE. The same applies to QRI and PFI (packet filter id). ). For delete existing flow, the default option is to use 5QI instead of QFI. You can only use QFI if you enable this checkbox.

Tcl Parameter: UeNas5gSmModUseQfiToMatchFlow_1

Delay Time (s)

Enter the delay time in seconds to wait for PDU session modification after PDU Session Establishment.

Range: 1 to 1000

Default: 60

Tcl Parameter: SmfNas5gSmModDelayTime_1_1

Tcl Parameter: UeNas5gSmModDelayTime_1_1

Include Session AMBR

Select to include Session AMBR (Aggregate Maximum Bit Rate).

Enter Max Bit Rate UL.

Range: 1 to 65535

Select Units: 1 KBPS, 4 KBPS, 16 KBPS, 64 KBPS, 256 KBPS, 1 MBPS, 4 MBPS, 16 MBPS, 64 MBPS, 256 MBPS, 1 GBPS, 4 GBPS, 16 GBPS, 64 GBPS, 256 GBPS, 1 TBPS, 4 TBPS, 16 TBPS, 64 TBPS, 256 TBPS, 1 PBPS, 4 PBPS, 16 PBPS, 64 PBPS, 256 PBPS

Enter Max Bit Rate DL.

Range: 1 to 65535

Select Units: 1 KBPS, 4 KBPS, 16 KBPS, 64 KBPS, 256 KBPS, 1 MBPS, 4 MBPS, 16 MBPS, 64 MBPS, 256 MBPS, 1 GBPS, 4 GBPS, 16 GBPS, 64 GBPS, 256 GBPS, 1 TBPS, 4 TBPS, 16 TBPS, 64 TBPS, 256 TBPS, 1 PBPS, 4 PBPS, 16 PBPS, 64 PBPS, 256 PBPS

Tcl Parameter: SmfNas5gSmModSessAmbrEn_1_1

Tcl Parameter: SmfNas5gSmModAmbrMaxBrUl_1_1

Tcl Parameter: SmfNas5gSmModAmbrMaxBrUlUnits_1_1

Tcl Parameter: SmfNas5gSmModAmbrMaxBrDl_1_1

Tcl Parameter: SmfNas5gSmModAmbrMaxBrDlUnits_1_1

Available on SMF Node test case on Interface NAS-5G. Available when NAS-5G Version 16.5.0 or greater and the N4|PFCP ATSSS-LL Supported Features option is checked.

Support Access Traffic Switching: The procedure that moves all traffic of an ongoing data flow from one access network to another access network in a way that maintains the continuity of the data flow. Access traffic switching is applicable when Home-routed Roaming (UE registered to the same PLMN). Between one 3GPP access and one non-3GPP access.

Support Access Traffic Steering: The procedure that selects an access network for a new data flow and transfers the traffic of this data flow over the selected access network. Access traffic steering is applicable between one 3GPP access and one non-3GPP access.

Based on 5.32.6 of 3GPP TS 23.501 and 3GPP TS 24.193

Select Enable ATSSS Rules for Uplink to become configurable. 

Range : 1 to 8, default : 3

Tcl Parameter: SmfNas5gSmModAtssUlEn_1_1

Select for Number of ATSSS Rules to become configurable. 

Tcl Parameter: SmfNas5gSmModAtssUlNum_1_1

Range : 1 to 8, default : 1

Rules :

Flow 0-16 Details

Enter Flow 0-16 details. Select the total number of all created QoS flows within a DNN. Should be less than or equal to Number of Flows.

In AMF Nodal test case, Number of Flows is 1 ~ 16 or the value of Limit QoS Flows per PDU Session, whichever is smaller.

At most one flow can have Action Type "Create New QoS Flow".

Tcl Parameter: SmfNas5gSmModNumFlows_1_1

Tcl Parameter: UeNas5gSmModNumFlows_1_1

QoS Flow Descriptions

Select QoS Flow Descriptions.

Number of Signaled Rules

Enter the total number of Signaled Rules to be modified. Should be less than or equal to Number of Signaled Rules.

In AMF Nodal test Case, the Number of Signaled Rules has being changed from 1-2 to 1-16.

0 rules are allowed for Action Type = Modify (node and nodal side).

Range: 0 to 16 

Tcl Parameter: SmfNas5gSmModNumSigRules_1_1_1

Tcl Parameter: UeNas5gSmModNumSigRules_1_1_1

QRI

Enter the QoS Rule Identifier (QRI). Select the "..." for the Current QRI Assignments pane. Should be unique across all created QoS rules within a DNN.

For "Op Code" Delete Existing QoS Rule, only QRI is enabled.

RI is enabled for all "Modify" type Op Codes (3-6)

Tcl Parameter: SmfNas5gSmModQosRuleId_1_1_1_1

Operation Code

OP Code

Select Operation Code.

Options : Create New Qos Rule, (Delete Existing QoS Flow, Modify Existing QoS Flow, Modify Existing QoS Rule and Add Packet Filters, Modify Existing QoS Rule and Replace Packet Filters, Modify Existing QoS Rule and Delete Packet Filters, Modify Existing QoS Rule without Modifying Packet Filters, available only if the “Action Type” is “Modify Existing QoS Flow”.)

Note : When Action Type is "Modify Existing QoS Flow" on the Flow tab, the Rule tab has "Op Code" selections:
       Create New QoS Rule - 1
       Delete Existing QoS Rule - 2
       Modify Existing QoS Rule and Add Packet Filters - 3
       Modify Existing QoS Rule and Replace All Packet Filters - 4
       Modify Existing QoS Rule and Delete Packet Filters - 5
       Modify Existing QoS Rule without Modifying Packet Filters - 6

Tcl Parameter: SmfNas5gSmModQosOpCode_1_1_1_1

Tcl Parameter: UeNas5gSmModQosOpCode_1_1_1_1

Precedence

Enter Precedence.

Range: 0 to 255

Default: 255

Tcl Parameter: SmfNas5gSmModPreced_1_1_1_1

Tcl Parameter: UeNas5gSmModPreced_1_1_1_1

Available on AMF node with SMF Emulation, SMF Node and UPF Nodal test cases when Version >= 15.2.0 and NGAP Version >= 15.2.0, Disabled when UE-Requested PDU Session Modification is enabled.

Available when Operation code is “Modify Existing QoS Rule". Select to modify packets fiters.

When this checkbox is available but unchecked, the “Number of Filters” dropdown list is disabled and its value is set to 0, and the “Filter-” sub-tab is unavailable for input. "Modify existing QoS rule without modifying packet filters" will become the operation when the testcase is run.

Tcl Parameter: SmfNas5gSmModFiltersEn_1_1_1_1

Available on AMF node with SMF Emulation, SMF Node and UPF Nodal test cases when Version >= 15.2.0 and NGAP Version >= 15.2.0, Disabled when UE-Requested PDU Session Modification is enabled.

Available when Operation code is “Modify Existing QoS Rule". Select to enable updating FAR with DROP action. When the "Drop Uplink Packets" box is checked, an Update FAR IE will be sent in PFCP Session Modification Request with "Apply Action = DROP" to instruct the UPF to drop all uplink packets for this rule.

Tcl Parameter: SmfNas5gSmModDropUlPktsEn_1_1_1_1

Available on AMF node with SMF Emulation, SMF Node and UPF Nodal test cases when Version >= 15.2.0 and NGAP Version >= 15.2.0, Disabled when UE-Requested PDU Session Modification is enabled.

Available when Operation code is “Modify Existing QoS Rule". Select to enable updating FAR with DROP action. Whennthe "Drop Downlink Packets" box is checked, an Update FAR IE will be sent in PFCP Session Modification Request with "Apply Action = DROP" to instruct the UPF to drop all downlink packets for this rule.

Tcl Parameter: SmfNas5gSmModDropDlPktsEn_1_1_1_1

Number of Filters

Enter Number of Filters. 

On AMF Node/SMF Node, NAS-5G|SM/DNN/Modified QoS Settings/Mod/Flow/Rule tabs:
1) When Operation Code is "Modify Existing QoS Rule and Delete Packet Filters", a different Filter panel is displayed that has only one field "Packet Filter ID". Range is 0-15, default value starts at 0 for Filter 1 and increased by one for each new tab. 

2) The Number of Filters range is normally 0-15. For Op Code 3 & 5, the range is 1-15. For Op Code 6, Number of Filters can only be 0.

Range: 0 to 15

Tcl Parameter: SmfNas5gSmModNumFilters_1_1_1_1

Tcl Parameter: UeNas5gSmModNumFilters_1_1_1_1

Filter (0 to 15)

Enter Filters (0 to 15) details. 

Select Direction. 

• If NAS-5G Version is 16.5.0 or higher, and any filter within the QoS Flow Modification, QoS Settings or Modified QoS Settings has Direction set to Downlink, the Match-all option will be disabled. Spec reference: 24.501-g50 clause 9.11.4.13 - NOTE 2:    The "Match-all type" packet filter component type identifier shall not be used with packet filter direction "downlink only".

Options: Pre-Rel 7 (default), Downlink, Uplink, Bi-Directional

Tcl Parameter: SmfNas5gSmModDirection_1_1_1_1_1

Tcl Parameter: UeNas5gSmModDirection_1_1_1_1_1

Select Match-all. All criteria will be matched.

Tcl Parameter: SmfNas5gSmModMatchallEn_1_1_1_1_1

Tcl Parameter: UeNas5gSmModMatchallEn_1_1_1_1_1

Modify Traffic Endpoint 

TEID

Remove Uplink Endpoint

Remove Downlink Endpoint

Available on AMF node with SMF Emulation, SMF Node and UPF Nodal test cases when Version >= 15.2.0 and NGAP Version >= 15.2.0, Disabled when UE-Requested PDU Session Modification is enabled.

Available only if the “Operation Code” is “Modify Existing QoS Rule” and the “PDIU” box is checked under the N4|PFCP tab. Select to enable Modify Traffic Endpoint.

When enabled, select “Update Traffic Endpoint” (default), “Remove Traffic Endpoint” from the dropdown list.

When “Update Traffic Endpoint” is selected, the checkbox “TEID” becomes available and must be checked.

When the "TEID" box is checked, TEID within Traffic Endpoint will be updated based on the following rule.

If the TEID was assigned by SMF, then the TEID will be incremented by 1.

If the TEID was assigned by UPF, then a PFCP Session Modification Request will be sent to UPF to request a new TEID.

When “Remove Traffic Endpoint” is selected, two checkboxes, “Remove Uplink Endpoint”, and “Remove Downlink Endpoint” become available. These checkboxes are unchecked by default and at least one must be checked.

• If the "Remove Uplink Endpoint" box is checked, the Traffic Endpoint in the uplink direction for the QoS rule will be removed.
• If the "Remove Downlink Endpoint" box is checked, the Traffic Endpoint in the downlink direction for the QoS rule will be removed.

Tcl Parameter: SmfNas5gSmModTrafEndptEn_1_1_1_1

Tcl Parameter: SmfNas5gSmModTrafEndptAction_1_1_1_1

Tcl Parameter: SmfNas5gSmModTrafEndptTeidEn_1_1_1_1

Tcl Parameter: SmfNas5gSmModTrafEndptRemUlEn_1_1_1_1

Tcl Parameter: SmfNas5gSmModTrafEndptRemDlEn_1_1_1_1

Select the Steering Function. 

Enabling requires NAS-5G Version 16.5.0 or higher and the N4|PFCP ATSSS-LL Supported Features option checked.

Options : ATSSS-LL Functionality (default)

Select the Steering Mode.

Options : Load Balancing (default)

Select the Steering Mode Information.

Options : 100% over 3GPP and 0% over non-3GPP,          
     90% over 3GPP and 10% over non-3GPP,            
     80% over 3GPP and 20% over non-3GPP, (default)
     70% over 3GPP and 30% over non-3GPP, 
     60% over 3GPP and 40% over non-3GPP, 
     50% over 3GPP and 50% over non-3GPP, 
     40% over 3GPP and 60% over non-3GPP,
     30% over 3GPP and 70% over non-3GPP,
     20% over 3GPP and 80% over non-3GPP,
     10% over 3GPP and 90% over non-3GPP,
     0% over 3GPP and 100% over non-3GPP           

Tcl Parameter: SmfNas5gSmModAtssDlSteerFunc_1_1_1

Tcl Parameter: SmfNas5gSmModAtssDlSteerMode_1_1_1

Tcl Parameter: SmfNas5gSmModAtssDlSteerModeInfo_1_1_1

P-CSCF Restoration

Select to trigger for P-CSCF Restoration. Available when either Restoration P-CSCF V4 Address or Restoration P-CSCF V4 Address is selected in Protocol Configuration Options. On SMF Node, when N16 Interface is selected, the "P-CSCF Restoration" panel is disabled because only PDU modifications due to QoS update are currently supported. This applies to both V-SMF and H-SMF node. 

Based on the specification, if the UE indicates Re-selection support in the PCO IE, SMF will trigger a PDU session modification procedure with updated P-CSCF address list. Otherwise, SMF will trigger PDU session release with reactivation requested. Currently we only support P-CSCF restoration when SM session is in connected mode. Spec reference: 23380 5.8.2.2 and 5.8.2.4.

Enter Restoration Delay in milliseconds. Default is 30000 for DNN1, 40000 for DNN2, 50000 for DNN3 and so on.

Range : 10000 to 4294967295

Select for Continuous Restoration.

Tcl Parameter: SmfNas5gSmPcscfRestEn_1

Tcl Parameter: SmfNas5gSmPcscfRestDelay_1

Tcl Parameter: SmfNas5gSmPcscfRestCont_1

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

Tcl Parameter: AmfNas5gSmCustomMsg

Tcl Parameter: SmfNas5gSmCustomMsgEn

Tcl Parameter: SmfNas5gSmCustomMsg

Tcl Parameter: UeNas5gSmCustomMsgEn

Tcl Parameter: UeNas5gSmCustomMsg

Apply Test Data File to SM Parameters

Select to add a TDF file for SM parameters.

Example file below - NSSAI will set the Nssai into pdu.

UeSmTDF.csv

Example of Multiple PDUs using different NSSAI values via TDF file:

Uesmtdfmultpdudiffnssai.csv

Example file with PDU_TYPE, DNN_NAME, SCC_MODE, NSSAI,SSC_Mode,DNN_NSI_ID,EMERGENCY_EN

Added support for UPF Nodal test case for DNN_NAME parameter. Example file : sm-dnn-name.csv

If PDU Configuration is enabled, DNN names will be populated to SM sessions on PDU basis according to GUI selection.

Otherwise DNN names on the Data Network Name panel will be populated to SM sessions in round robin.

If you enable the TDF file on NAS-5G | SM,  you can define session based DNN names for as many SM sessions as you prefer. They will overwrite GUI configuration when the TDF file gets read in.

Please note that we allocate QoS settings based on DNN name stored in the SM session. If the stored DNN name matches with any GUI configured value, the corresponding QoS setting will be picked up. Otherwise, the QoS setting configured for first DNN name (i.e. the default QoS setting) will be picked up. If the number of DNN names defined via the TDF exceeds GUI configuration, it is inevitable that some SM session will pick up the default QoS setting. This behavior is consistent across our UPF Nodal, SMF Node and AMF Node with SMF emulation. However in the case of SMF Node or AMF Node with SMF emulation, the match is based on DNN name received in the PDU Session Establishment Request rather than the one stored in the SM session. Also note that on the N4 tab, the PFCP Version needs to be 16.5.0 or above in order for DNN name to appear in PFCP Session Establishment Request.

SM-PDU-DNN-SCC-NSSAI.csv

Sm_reorder_smfNodal.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: SmfNas5gSmCfgFileEn

Tcl Parameter: SmfNas5gSmCfgFile

Tcl Parameter: UeNas5gSmCfgFileEn

Tcl Parameter: UeNas5gSmCfgFile

Select the required authentication method.

Options: No Authentication, Include PAP Authentication, or Include CHAP Authentication

Default: No Authentication

PAP Authentication

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

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

Range:  N/A

Default: Secret

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

Range:  N/A

Default: Secret

Tcl Parameters:

CHAP Authentication

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

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

Range:  0 — 255

Default: 0

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

Range:  N/A

Default: MSName

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

Range:  N/A

Default: secret

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

Range:  0-F characters

Default: ABCD

Tcl Parameters:

Related Measurements

• User Authentication Failure

During AMF Nodal, SMF Nodal, SMF Node and AMF Node with SMF Emulation testing, select IP Control Protocol to include the protocol configuration options (PCO) IE in messages such as PDU Session Establishment Request or PDU Session Establishment Accept.

Tcl Parameter: UeNas5gSmPcoIpcpEn

Tcl Parameter: SmfNas5gSmPcoIpcpEn

Type:  True/False

Default: False

Selecting IP Control Protocol allows you to further select and enter IPCP IP Address, primary and secondary addresses for WINS and DNS servers. Only IPv4 addresses are supported.

Type: True/False

Default: False

Tcl Parameters:

P-CSCF IPv4 Address Request

Select to indicate that UE requests P-CSCF IPv4/IPv6 address (es).

P-CSCF IPv6 Address Request

DNS Server IPv4 Address Request  

Select to indicate that the UE requests IPv4 DNS Server Address. The UE can then perform a DNS query to retrieve P-CSCF address(es), etc. Select to indicate that the UE requests IPv6 DNS Server Address. The UE can then perform a DNS query to retrieve P-CSCF address(es), etc.

DNS Server IPv6 Address Request

IPv4 Address Allocation Request via DHCPv4

Select to indicate that the UE requests IPv4 address allocation from a DHCPv4 server.

IM CN Subsystem Signalling Flag Request

Select to indicate the dedicated signalling PDP context for IMS signalling.

If UE does not include the IM CN subsystem Signalling flag, the network will consider the PDP context as a general purpose PDP context.

MSISDN Request

Select to indicate request for user MSISDN.

IPv4 Address Allocation Request via NAS Signaling

Select to indicate that the UE requests IP address allocation via NAS signalling.

DNS Server IPv4 Address

Select to enter the DNS Server IPv4 address.

DNS Server IPv6 Address

Select to enter the DNS Server IPv6 address.

P-CSCF IPv4 Address

Select to enter the P-CSCF IPv4 address.

P-CSCF IPv6 Address

Select to enter the P-CSCF IPv6 address.

Secondary P-CSCF IPv4 Address

Enabled if P-CSCF IPv4 Address is enabled. Select to support a secondary P-CSCF V4 Address.

Secondary P-CSCF IPv6 Address

Enabled if P-CSCF IPv6 Address is enabled. Select to support a secondary P-CSCF V6 Address.

Restoration P-CSCF V4 Address

Enabled if P-CSCF IPv4 Address is enabled. Select to support P-CSCF Restoration Procedure. Enter Address. If selected, SMF Node will send this IP address to UE in odd Number restoration events (e.g. 1st, 3rd, etc.)

Restoration P-CSCF V6 Address

Enabled if P-CSCF IPv6 Address is enabled. Select to support P-CSCF Restoration Procedure. Enter Address. If selected, SMF Node will send this IP address to UE in odd Number restoration events (e.g. 1st, 3rd, etc.)

P-CSCF Reselection Support

Applicable on AMF and SMF Nodal test cases when (P-CSCF IPv4 Address Request or P-CSCF IPv6 Address Request is enabled) and NAS-5G Version and NGAP Version = > 15.2.0 .

P-CSCF Restoration can be triggered if you enable the P-CSCF Restoration on NAS-5G | SM | DNN n on AMF and SMF Node Test cases. Based on the spec, if the UE indicates Re-selection support in the PCO IE, SMF will trigger a PDU session modification procedure with updated P-CSCF address list. Otherwise, SMF will trigger PDU session release with reactivation requested. Currently we only support P-CSCF restoration when SM session is in connected mode. Spec reference: 23380 5.8.2.2 and 5.8.2.4.

IPv4 Link MTU Request

MSISDN

Select for S-NSSAI information to incldued via ePCO in S5:Create Session Response for LTE access.

Enter SST and SD of NSSAI in DDN Data Pane.

Spec reference : 23.502, section "1.1.1.1. 4.11.0a.5  PDN Connection Establishment" and 23.501 section "1.1.1.2. 5.15.7.1    General".

IPv4 Link MTU

Selected Bearer Control Mode

MS Support of Local Address in TFT Indicator

Network Support of Local Address in TFT Indicator

MS Support of Network Requested Bearer Control Indicator

QoS Rules with Length of Two Octets Support Indicator

QoS Flow Descriptions with Length of Two Octets Support Indicator

Select to add the PDU Session ID in the PDU Session Establishment Request message.

For Inter-tech mobility, the PDU Session ID PCO will always be included in the PDN Connectivity Request or ESM Information Response message if the UE initially attaches on 4G side.

Spec Reference : 

3GPP TS 24.008 -  Mobile radio interface Layer 3 specification; Core network protocols; Stage 3

3GPP TS 24.501 -  Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3

Tcl Parameter: UeNas5gSmPcoPduSessionIdEn_1

Select to add up to five operator specific use PCOs can be sent in the PDU Session Establishment Request message.

Select Number of Containers. 

Range : 1 to 5

Enter ID and Value for each Container.

Container ID - Range: 0xFF00 ~ 0xFFFF. (16-bit HEX starting with 0x), Default: 0xFF00 for row 1, 0xFF01 for row 2 and so on.

Container Value - Range: 0 ~ 64 bytes. (up to 64-byte HEX starting with 0x),Default: 0x. If you use the default 0x for Container Value, the constructed PCO will be of zero length and does not include any value field.

Spec Reference : 

3GPP TS 24.008 -  Mobile radio interface Layer 3 specification; Core network protocols; Stage 3

3GPP TS 24.501 -  Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3

Tcl Parameter: UeNas5gSmPcoCustomEn_1

Tcl Parameter: UeNas5gSmPcoCustomNum_1

Tcl Parameter: UeNas5gSmPcoCustomPcoId_1_1

Tcl Parameter: UeNas5gSmPcoCustomPcoValue_1_1

Variables for Additional Parameters