Test Activity

Emulation Mode

Emulate

(AMF)

5G Core Emulator is a test case that emulates the visited or home network in support of the home routed roaming scenario in 5G system.

Emulation Mode : 

Use the "Emulate" drop-down box to toggle between the V-Network (visited network) and H-Network (home network).

All emulated NFs are optional and can be enabled or disabled with a checkbox. Once selected, the SEPP is forced to be "Initiator" in V-Network and "Responder" in H-Network.

The selection of "NRF Interface" is also optional. Once selected, the NRF interface will be enabled for all selected NFs except for the SEPP node and nodes we don't yet have support on NRF. 

The "Roaming Scenario with SEPP" is currently force selected. All control plane traffic between the V-Network and H-Network must go through the V-SEPP and H-SEPP via the N32 interface.

Emulator Options :

Currently only enabled for the AMF and SMF node. AMF is available when Emulate = V-Network and AMF is enabled.

The content is ported from standalone AMF and SMF node test cases with minor changes. For example, the "N16 Interface" under SMF is force selected in both networks and the "Emulate" is forced to be V-SMF in V-Network and H-SMF in H-Network.

• Mobile Subscribers

SUT : 

• NG-RAN
• Any NF or combination of NFs in 5G roaming core V-Network
• Any NF or combination of NFs in 5G roaming core H-Network
• V-UPF
• H-UPF

Tcl Parameter: Emulate

Tcl Parameter: AmfEn

Select RADIUS, Diameter, or Portal as the AAA protocol for the test. The options that are available depend on the test applications licensed for the test system.

• About Diameter Testing

• About RADIUS Testing

• Select Portal to support HTTP Portal Authentication. The AAA Server Node test case provides HTTP Portal Server Node configuration required for HTTP Portal authentication (Configure Portal I/F tab, AC NAS SUT and Portal Node) 

Options: RADIUS, Diameter, Portal

Default: RADIUS

Select Affinity Mode to turn on performance improvement of Diameter Applications. Only available when AAA Protocol = Diameter.

Significant performance impact can be achieved with Affinity Mode, especially, when running multiple test cases on the same process. A higher activation rate/throughput can be expected. 5 test cases are optimum as all cores will be used per one process on the C100 S2. Other systems may have a different number of cores per process and the recommended number of test cases should be adjusted accordingly.

In AAA Server Nodal test case, select Test Activity as Inter-Technology Mobility and select one of the following:

• LTE: performs LTE to eHRPD Handoff
• eHRPD: performs eHRPD to LTE Handoff
• Untrusted Non-3GPP : performs ePDG interconnection and inter-access mobility for untrusted non-3GPP accesses

Tcl Parameter: DiaClnInitiateType

Use the Alternate Node checkbox to enable the Alternate Node authentication, and the Alternate Node pane on the RADIUS tab is enabled, allowing you to define the NAS emulator.

IP Address Allocation

In AAA Server Node testing, select the IP Address Allocation checkbox to define the IP address pools (IP Address Allocation) and methods (Address Pool Selection Method) used to dynamically allocate MN IP addresses from a virtual AAA or DHCP server. The IP Pools tab becomes available when you select this checkbox.

Tcl Parameter: NasNode2AuthenticationEnabled

In AAA Serve Node test case, use Dual Stack to return both IPv4 and IPv6 addresses when requested. Dual Stack is available for your selection only when AAA Protocol = Radius and IP Address Allocation is selected.

Type: True, False

Default: False.

Tcl Parameter: AaaIpAddrDualStackEn

In AAA Server Node testing, select the CoA Simulation check box to enable and define the CoA Simulation parameters (CoA Simulation) on the RADIUS tab.

Tcl Parameter: RadCoaSimulationEn

In AAA Server Node testing, select the Disconnect Simulation checkbox to define the Deactivation Rate (session/sec) for the Mobile Subscribers.

Tcl Parameter: RadDisconnEn

In AAA testing, Diameter IPSec is only available when one NAS Node and one dedicated AAA authentication SUT are involved in the test (AAA Test is Authentication Only). In CSN Nodal test case, IPSec is not allowed for Inter-ASN mobility but it is allowed for Inter-Tech mobility since the Target NAS is not used.

• NAS-5G - Mm and Sm.
• N2 - NGAP  (over SCTP)

Available when Test Activity = Inter Technology Mobility. Select Initial Network from dropdown list. Options: 5GS , LTE 

Initial Network indicates where the UE will initially attach / register. 

Select the Handoff Protocol below to indicate the "Target" network.

For example: Initial Network = 5GS , Handoff Protocol = LTE (which is the Target). The UEs will initially attach / register to 5GS then handoff to LTE. 

The F2 Help key has been enhanced to indicate which network is the Target.

Tcl Parameter : InitiateType

Available when Test Activity = Inter Technology Mobility, Command Mode or Sequencer. When Handoff protocol = LTE, the S1-MME becomes available for input. EPS Pane is enabled. When Handoff protocol = WiFi or WiFI-LTE the WiFi Subscribers Pane becomes available for input. Interfaces AP/SSID, SWu IPSec and AAA-RADIUS are enabled. AAA Pane becomes available SUT. Select for VoNR HO <->  Procedure VoWiFi (ePDG) <-> per 23.502 Section 4.11.4. Both Single and Continuous Handoffs from 5GS to WiFi are supported Options : LTE , WiFi, WiFi-LTE

Option WiFi-LTE is used to emulate pairs of 5G UE Register to AMF and establish PDU session, setup a VoNR call, handover to WiFi (ePDG as SUT), then handover to LTE (MME as SUT), then end the call and detach 4G. If continuous mobility is configured, UE will do Register again at 5G network in next mobility cycle. AMF and MME SUTs as well as gNB and eNB Control and User nodes become available for input.

In AMF Nodal, when "Test Activity" is "Inter Technology Mobility", please enable "Multiple SUTs per gNB" in "Network Devices" >> AMF.  Inter technology mobility registration for LTE to 5G supports reallocation: Reference : 23.502 4.11.1.3.3 EPS to 5GS Mobility Registration (Idle) using N26 with AMF Reallocation.

Due to the limitation of SBI configuration, AMF Node can only config multi AMF Nodes when "Inter-AMF Only"  or "SMF Emulation" is checked.

Options: None, LTE (Command Mode, Sequencer)

Tcl Parameter : HandoffProtocol

Available when Test Activity = Inter Technology Mobility, Intra-AMF Mobility, Inter-AMF Mobility and Dual Connectivity. Select Handoff Type from dropdown list. For Mobility Registration from 4G to 5G after EPS fallback, Test Activity = Inter Technology Mobility, Handoff Protocol = LTE, Handoff Type = REG/TAU, enable Continuous Handoff and Initial Network = Target. For 5GS to EPS TAU Scenario see 23.502 Section 4.11.1.3.2. For Mobility Registration Update see 3GPP TS 23.502 Section 4.2.2.2.

For RAN Initiated QoS Flow Mobility (per 23.502 section 4.14.1):

This procedure is used to transfer QoS Flows to and from Secondary RAN Node. During this procedure, the SMF and UPF are never re-allocated. The UPF referred in this Figure 4.14.1-1  is the UPF which terminates N3 interface in the 5GC. The presence of IP connectivity between the UPF and the Master RAN node, as well as between the UPF and the Secondary RAN node is assumed. If QoS Flows for multiple PDU Sessions need to be transferred to or from Secondary RAN Node, the procedure shown in the Figure 4.14.1-1 below is repeated for each PDU Session.

Options: Handover , REG/TAU (Inter Technology Mobility)

Options: Xn , N2, Mobility Registration Update (Intra-AMF Mobility) Options: N2, Mobility Registration Update (Inter-AMF Mobility)

Options: RAN Initiated QoS Flow Mobility (Dual Connectivity)  

Tcl Parameter : HandoffType

Select to use IPSec to encrypt Data Traffic (L3-7 Interface). Define IPSec parameters on the Data IPSec tab.

Select to trigger PDU Session Modification request from UE. Available when NAS-5G SM | NAS 5G Version (24.501) is = > 15.2.0 and when NAS-5G SM | NGAP Version (38.413) is = > 15.2.0. NAS-5G SM | QoS Flow Modification becomes available for input. Available on AMF Nodal, AMF Node and SMF Node test cases.

Tcl Parameter: UeReqPduSessionModEn

Select for Secondary Authentication during PDU Session Establishment. Available when NAS-5G SM | NAS 5G Version (24.501) is = > 15.2.0 in AMF Nodal / AMF Node and SMF Nodal / SMF Node test cases. Not available when Registration Only is enabled. Max DNN Mode via TDF is not available with this feature.

When enabled, the “Number of PDUs” in Test Configuration/Mobile Subscribers panel should be equal to “Number of Data Network Names") in NAS-5G/SM Tab.

Enable Include SM PDU DN Req Container in PDU Session Est Req in NAS-5G/SM Tab, Secondary Authentication, EAP Settings (TLS Only) in AMF Nodal and the Secondary Authentication Configuration Timers (Reauthentication Delay (s), T3590 (s)) in AMF Node / SMF Node.

This options is not available in SMF Nodal when UPF Node Emulation is enabled.

The following use cases are supported by AMF Nodal

    1) PDU Session Secondary Authentication during PDU Session Establishment procedure

    2) Re-authentication after PDU Session Establishment procedure

    3) PDU Session Establishment Reject by NW

    4) PDU Session Release by NW

Supported Call Flows:

In B2B test for AMF Nodal, AAA Node Test Case for DN-AAA is not used because AMF currently does not support the interface to communicate with DN-AAA however, SMF Node does support it.

References: 

3GPP TS 23.501: System Architecture for the 5G System; Stage 2
3GPP TS 23.502: Procedures for 5G System; Stage 2
3GPP TS 24.501: NAS protocol for 5G System; Stage 3
3GPP TS 29.561: Interworking between 5G Network and External Data Networks; Stage 3
3GPP TS 33.501: Security architecture and procedures for 5G System

Note: The latest Wireshark doesn't decode IEs in NAS 5G messages and http2 frame headers of NamfCommunication_N1N2MessageTransferReq  when messages include EAP message IE/SM PDU DN request container container IE.

Tcl Parameter: PduSessionSecAuthEn

Currently session loading supports registration followed by pdu establishment request with  follow-on request pending bit set to 1.

Thus feature will send registration request message not followed by pdu establishment and follow-on request pending bit set to 0. Thus, the activity becomes (Reg/periodic reg/./DeReg, PDU session establishment is not triggered)

Table 9.11.3.7.1: 5GS registration type information element

When Registration Only is checked, the Number of PDUs is forced to 0 and UE-Requested PDU Session Modification, Data Traffic, External Data, Data IPSec, Vo5G, and SMF/UPF Node Emulation are disabled. Also, the NAS-5G|SM and N3 tabs are hidden.

Enable or Disable the NAS-5G|MM, Initial Registration with Follow On to set the Follow-on request bit.

Not available when Test Activity = Command Mode, Sequencer or Inter Technology Mobility

N2 IPSec / Target N2 IPSec

Available when Test Activity = Inter Technology Mobility with LTE and Vo5G is enabled and Test Activity = Command Mode / Sequencer with Handoff Protocol =  WiFi-LTE and Vo5G.

Select to emulate the scenario that a Vo5G call is attempted while the gNB does not support Vo5G and has to fallback to an eNB to start the media traffic. The fallback itself is triggered by receiving of a PDU Session Resource Modify Request message on the Vo5G PDU. The gNB that's unable to support Vo5G will send back a response with reject cause ims-voice-eps-fallback-or-rat-fallback-triggered and initiate inter-tech mobility to LTE. After the UE is successfully handed over to LTE, the network will resume the call attempt by initiating a Create Bearer Request / Activate Dedicated EPS Bearer Context Request to create the media bearer.

Mobility between 5GS and EPS without N26 is not yet supported.

Enable N3IWF ( Non-3GPP InterWorking Function). Per 3GPP 23.502 .

The NWu interface becomes available for input with TCP and NWu IPSec tabs.

Available when Test Activity = Capacity Test or Session Loading Test or Inter Technology with Handoff Protocol = WiFi (Support for Handover of a PDU session procedure between 3GPP and Untrusted non-3GPP access) or LTE ( Handover procedures between EPS and 5GC-N3IWF and back based on Spec 3GPP 23.502 Section 4.11.3).

Support handover a UE from a source Untrusted non-3GPP access to a target 3GPP access and UE handover a PDU Session from Untrusted non-3GPP access to 3GPP access based on 3GPP 23.502 Section 4.9.2 )

Note : SMF and PGW-C should be tightly coupled in the same test case to exchange bearer context during mobility between 5GC-N3IWF and EPS (3GPP 23.502  Sec-4.11.3.2). AMF Node test case with SMF Emulation and PGW-C Emulation is recommended. Do not use the MME Node test case for PGW Emulation for this mobility scenario. 

Tcl Parameter: N3iwfEn

Select for the TWIF - Trusted WLAN Interworking function. When enabled, the AAA Interface (RADIUS ), AP/SSID,  GRE become available for input. AAA SUT Pane becomes available as well as the AP WAN Node. Currently we only support Number of PDUs set to 1.

Limitations : TWIF is only allowed with these options: Data Traffic , Data IPSec, External Data, Vo5G

Initial Phase 20.2.0 release supports ; 1 UE, 1 Node, No PDU no Data

Phase 2 in 20.4.0 release includes : 

• L2 over GRE to encapsulate overall traffic from emulated WiFi AP to the TWIF node under test
• Session establishment and UL/DL data flows

Spec Reference:

• TS 23.501 – System Architecture for the 5G System (Rel-16)
• TS 23.502 – Procedures for the 5G System (Rel-16)
• TS 24.502 – Access to the 3GPP 5G Core Network via Non-3GPP Access Networks (Rel-16)
• TS 38.413 – NG Application Protocol (Rel-16)
• TS 33.501 – Security Architecture and Procedures for the 5G System
• RFC 3748 – Extensible Authentication Protocol (EAP)
• RFC 3579 – RADIUS Support For Extensible Authentication Protocol (EAP)
• RFC 7296 – Internet Key Exchange Protocol (IKE v2)
• IEEE 802.1X – Port-based Network Access Control

The following use cases are supported by AMF Nodal: 

Untrusted & Trusted 3GPP Access – TNGF

• Registration via non-3GPP Access
• Deregistration procedure for non-3GPP Access
• N2 procedures via non-3GPP Access
• UE requested PDU Session Establishment via non-3GPP Access
• UE or Network requested PDU Session Modification via non-3GPP Access
• UE or Network requested PDU Session Release via non-3GPP Access
• Support for EAP Re-Authentication (Trusted non-3PP Access only)

For Devices without 5G NAS over WLAN Access (TWIF)

• Initial Registration and PDU Session Establishment
• Deregistration Procedure
• N2 Procedures

1. UE initiates EAP procedure to send AAA requests to TNGF. EAP message will be encapsulated into AAA message. The AAA request also includes the TNAP identifier, which can be treated as the User Location Information.

The TNAP Identifier shall include the SSID of the access point to which the UE is attached. The TNAP Identifier shall include at least one of the following elements unless otherwise determined by the TWAN operator's policies:

-     the BSSID (see IEEE Std 802.11-2012 [106]);

-     civic address information of the TNAP to which the UE is attached.

Per TS 29.571 V16.5.0 section 5.4.4.62      

Type: TnapId :

Table 5.4.4.62-1: Definition of type TnapId

2). During EAP-5G procedure TNGF key is created in the UE and in the AMF after the successful authentication. The TNGF key is transferred from the AMF to TNGF in step 10a (within the N2 Initial Context Setup Request). The TNGF derives a TNAP key, which is provided to the TNAP. 

3). After receiving the TNGF key from AMF in step 10a, the TNGF shall send to UE an EAP-Request/5G-Notification packet containing the "TNGF Contact Info", which includes the IP address of TNGF. 

Phase 2 (release 20.4) adds support for the section circled below:

Tcl Parameter: TwifEn

Available in AMF Nodal test case for Capacity or Session Loading test activities. Disabled by any test options other than Data Traffic, Data IPSec, External Data, and Vo5G.

Select for 5G-RG Emulation support in AMF Nodal. 

The System Under Test (SUT) is AGF with Landslide simulating 5G-RGs, AN & PDN as shown in the figure below. Landslide will generate control and user plane test traffic and initiate various procedures towards the AGF & UPF.

• The interface between AN and AGF is the V interface.
• The following procedures are supported:
  - Registration
  - PDU session Initiation/Establishment (IPv4, IPv6)
  - Service Request
  - Send/receive user plane data
  - 5G-RG or Network Requested PDU Session Release
  - Deregistration
• At a high level, the following capabilities will be supported:
  - Control Plane encapsulated into PPP
  - Multiple PDU sessions generated by 5G-RG
  - IPv4, IPv6 & dual-stack support
  - 5GC is R16 compliant

• Initiation of CP communication between a 5G-RG and an AGF has each layer brought up in the following sequence.
  1) PPPoE procedures as documented in RFC 2516 [39] to establish a PPPoE session.
  2) PPP LCP procedures documented in RFC 1661 [40] augmented with the 5G VSO (RFC 2153 [36]) to open the link and to permit 5G procedure support to be negotiated.
  3) EAP authentication procedures.
  4) VSNCP procedures to open a VSNP channel.

PPPoE procedures

• PPPoE v1 will be used to carry PPP and VSNP for NAS and AS encapsulation. 
• PPPoE is used to discover the AGF at the L2 broadcast domain to start the PPP session.
• PADI message will use a service name tag to request a particular service.
• PPPoE message exchange is mentioned in the Step1, 2, 3, 4 in the call flow diagram
• Sample PADI/PDAO/PADR/PADS messages are shown below.

Spec Reference:

• 3GPP 23.316 
• FMC Fixed 5G Access
• RFC-2516-A Method for Transmitting PPP Over Ethernet (PPPoE)
• RFC-1661-PPP-LCP
• TR-456-AGF Functional Requirements
• TR-470-5G Wireless Wireline Convergence Architecture
• 3GPP 24.502 - EAP-5G
• RFC 3772 - VSNP 

When enabled, the PPP Tab becomes available for input. The SUT is AGF. 

In release 23.3, the following changes were made : In the Network Devices, "AP-WAN Node"  tab was renamed to "5G-RG Node" tab without "# of Nodes". The "Starting IP address" was removed as what is selected for 5G-RG is the Eth Port, not an IP address. The 5G-RG tab in Mobile Subscribers has been removed, and the MAC Address field was moved to the "5G-RG Node" tab on Network Devices.

The UE IP address is derived from the NAS-5G/SM PDU IPv6 Address Pool, not from UE Static IPv4.

Tcl Parameter: 5gRgEn

LCS Support

Reset UE Positioning Stored Info

LCS Support is now available in the 5G AMF Nodal / gNB CU SA Nodal and AMF Node test cases. Currently, we support UE Based and UE assisted A-GNSS method. If TDF file is used, only the A-GNSS related parameters need to be configured.

• When enabled in AMF Nodal / gNB CU SA Nodal, the LCS Interface with LPP Tab and LPPe Tab are available for input.
• When enabled in AMF Node, the LMF Interface with LPP Tab and LPPe Tab are available for input.

If Reset UE Positioning Stored Info is enabled (Per TS38.509 6.6.1), “NRPPa” command is triggered with the following messages;  

• Reset UE positioning stored Info message with NAS-PDU: 0x0f8800;

              Protocol discriminator: 1111  

              Skip indicator: 0000 = No indication of selected PLMN (0)

              Message type: Reset UE Positioning Stored Information (0x88)

              UE Position Technology: 0000 0000 = AGNSS (0)

• e-CID Measurement Initiation with NRPPa-PDU

If Reset UE Positioning Stored Info is disabled, “NRPPa” command is triggered with the following message;

• e-CID Measurement Initiation with NRPPa-PDU

Select for the 5G Wireless Emergency Alert broadcast. Commercial Mobile Alert System (CMAS) Broadcast System for 5G.

In AMF Node/Nodal test cases and gNB CUSA Nodal TC, the PWS Tab for N2 interface allows the user to define requests related to Commercial Mobile Alert System (CMAS) Broadcast System for 5G. Per 3GPP 23.401.

Call flow:

Tcl Parameter: AmfEmergencyAlert

Tcl Parameter: GnbEmergencyAlert

Available on AMF Nodal test for Capacity or Session Loading test activities, Vo5G is enabled, Number of PDUs > 1 , NAS 5G Sm - Number of Network Names > 1, and at least 1 DNN must have the Emergency option selected. 

Select to emulate real 5G UE’s E911 call flow that is consisting of the following steps:

1. UE Register to 5G core and establish 1st PDU for data DNN.
2. UE establish 2nd PDU for ims DNN and complete SIP Registration.
3. (real UE dial 911) UE establish 3rd PDU for sos DNN, UE complete SIP sos register and make 911 call through 3rd.

When enabled, the E911 Vo5G tab is for the Emergency PDU and a second Gm2 for the Emergency Profile - Control: SIP , Control - TCP

Separate SIP Call Flow profile per Normal and Emergency PDU provides flexibility in configuring context of SIP messages over mechanism of SIP Configurable via that two Gm Tabs (Gm and Gm2) have to be exposed in GUI level.

Gm Tab/Profile is the default one, and it is associated with Vo5G Tab/Profile while Gm2 Tab/Profile is bound to E911 Vo5G. 

Example :

The E911 Call mechanism uses the highlighted timers (Start PDU Delay (After Registered) (ms), Start PDU Delay (After Prev-PDU) (ms)) as shown in screenshot below: 

In the case of two Vo5G PDNs only, ims and sos: 

• UE registers in ims PDU after 1 sec and performs SIP Registration.
• UE registers in sos PDU after 6 sec and performs E911 Call sequence.

In the case of 3 PDUs, data, ims and sos: 

• UE registers in data PDU after 1 sec and activates data exchange. 
• UE registers in ims PDU after 6 sec and performs SIP Registration.
• UE registers in sos PDU after 11 sec and performs E911 Call sequence.

Two Vo5G Profiles, Normal and Emergency, can be implemented by means of exposure of two Vo5G Tabs :

• Vo5G - for Normal PDU (ims DNN, in fact)
• E911 Vo5G - for Emergency PDU (sos DNN, in fact)

Tcl Parameter: E911CallEn

Select for SMF/UPF Node Emulation.

For SMF / UPF Emulation, the Nsmf, SMF-AMF, N4 (PFCP ) and N6 (N6 Data Traffic) interfaces become available.  The SUT is AMF SBI, SMF SBI Node , SMF N4 Node , SMF N4 GTP Node, UPF N3 Node, ,UPF N4 Node and UPF N4 GTP Node.

The NAS-5G SM interface has two panels, UE (same as AMF nodal test case) and SMF (same as AMF Node test case).  There will be two SM measurements, one labeled SM-UE and the other SM-SMF.

The N4 (PFCP ) interface has two panels, UPF (same as UPF Node test case) and SMF (same as SMF Node test case).  

Tcl Parameter: SmfUpfNodeEmulationEn

Select for support for Access Traffic Switching and Steering. Available on AMF Nodal when Test Activity is Inter-Technology Mobility with Wifi Handoff Protocol and  N3IWF is enabled and NAS-5G Version 16.5.0 or higher.

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

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.

Tcl Parameter: AtsssEn

Support Roaming is available on AMF Nodal Test Configuration and AMF Node Emulator Configuration. 

Available on AMF Nodal when Test Activity is Capacity, Session Loading Test, or Command Mode/Sequencer and Handoff Protocol is “None” or Inter Technology Mobility with Handoff Protocol = LTE and Handoff Type = Handover or REG/TAU and "NAS-5G Version" in Nas 5G Mm is 15.1.0 or higher and "NGAP Version" in N2/NGAP is 15.1.0 or higher. It is disabled when “SMF/UPF Node Emulation”, “N3IWF”, “TWIF”, “5G-RG”, “Support URLLC” and “Support ATSSS” in Test options are enabled.

Available on AMF Node when  "NAS-5G Version" in Nas 5G Mm  is 15.1.0 or higher and "NGAP Version" in N2/NGAP is 15.1.0 or higher. It is disabled when SMF Emulation, UPF Emulation, N22 Interface, N14 Interface are enabled.

In AMF Nodal TC, select Support Roaming to indicate whether to include the mapped Home S-NSSAI in NSSAI sent to AMF if available in Requested NSSAI in Registration Request and in Pdu Session Establishment Request.

In the case of Requested NSSAI of Registration Request, if the “Mapped Home S-NSSAIs” in “Requested NSSAI” in NAS-5G/MM Tab are configured, it will be included. In the case of Pdu Session Establishment Request, if the “Mapped Home S-NSSAIs” in “Allowed NSSAI” sent by SUT-AMF are available and one of them is matched with S-NSSAI of the PDU session that UE will establish, it will be included. In addition, If “Network Slicing Info” in DNN Tab which the PDU to be established belongs to is configured and its S-NSSAI is one of the Allowed NSSAI in Registration Accept received from AMF and that S-NSSAI has the mapped Home S-NSSAI,     UE will include the mapped Home S-NSSAI in NSSAI which is optionally sent together with PDU Session Establishment Request Message.

In AMF Node TC, select Support Roaming to indicate whether to support Roaming Scenario for PDU Session Establishment. Whens enabled, AMF will trigger only the Home Routed Roaming scenario when it handles PDU Establishment Procedure, and the SNSSAI for PDU Session has the mapped Home SNSSAI. Select HomeRouted, currently the only option. When Configured NSSAIs is configured in the NAS-5g, AMF Nodal will include Allowed NSSAI with the mapped S-NSSAI in RegistrationAccept message during registration procedure.

Tcl Parameter: SupportRoamingEn

Tcl Parameter: PduEstRoamingType

Select to add Soft GRE feature under User traffic session. Available in AMF Nodal for Capacity or Session Loading Test. It becomes disabled when any other checkbox is enabled except for Data Traffic and Fireball. On the AP/SSID tab for AMF Nodal only, the "Inner VLAN Tag" is allowed for Fireball but "VLAN Tag Type" is restricted to "0x8100".

Interface : AP/SSID ,DHCP and GRE become available for input. The 5G-GRE Pane becomes available for input. L3 measurements are generated when UE DHCPv4 or UE DHCPv6 is enabled for 5G-GRE even when data traffic is not enabled.

Enter the number of GRE Subscribers Per PDU in the 5G-GRE Pane. 

Range : 1 to 100, Default : 1

Select Apply Test Data File to Mobile Subscribers to add UE MAC Address via Test Data File (TDF). 

Tcl Parameter: 5gGreEn

Tcl Parameter: GreSubsPerPdu

Select to support NRNTN (Non-Terrestrial Network) network. AMF to send Forbidden TAI(s) to UE during initial Registration, mobility and periodic update Registration, and Service Request procedures.

Per 3gpp spec 23.502 release 17.6 sections 4.2.2.2.2, 4.2.3.2.

Can be enabled when NAS-5G version is 17.12.0/Sep2023 or higher and NGAP version (N2 tab) is 17.6.0/Sep2023 or higher. Test Activity excludes “Inter Technology Mobility” and “Dual Connectivity”.

For AMF Nodal TC , select the NTN Type in the gNB Control Node.

For AMF Node TC, enter the Number of Forbidden TACs in the Nas 5G MM Tab. 

Available on both AMF Nodal / Node test cases.

Tcl Parameter: SupportNtnEn

• NAS-5G - SM and MM.
• N2 - NGAP  (over SCTP).
• N4 - PFCP (Packet Forwarding Control Protocol) (over UDP) - When SMF Emulation is enabled.

The SUT is UPF (AMF Node , SMF N4 Node , SMF N4 GTP Node )

When SMF Emulation is enabled, N14 Interface and Intra-AMF Only are not available.

When SMF Emulation is disabled, N11 Interface toward SMF becomes available for testing. Namf, AMF-SMF as well as NAS-5G- MM tab only and N2 - NGAP are available for input.

The SUT is SMF SBI SUT (AMF Node and AMF SBI Node)

Tcl Parameter: SmfEmulationEn

UPF Node Emulation is available on AMF Node test case. 

The N4 (PFCP ) and N6 (N6 Data Traffic) interfaces become available as well as UPF N3 Node, ,UPF N4 Node and UPF N4 GTP Node. SMF SBI SUT becomes available for input.

When only  "UPF Emulation" is selected and "User Initiates Association" is selected under N4 (PFCP ), Uner the Network Devices/System Under Test section, the "SMF N4 SUT” tab becomes available for input.

When both "SMF Emulation" and "UPF Emulation" are selected :

• the tabs under the Network Devices/System Under Test section are grayed out and not available for selection
• only one SMF node and one UPF node are supported
• “Change of SSC Mode 2 or 3 PDU Session Anchor” is not available on the Nas 5G Sm

Select for PGW-C Emulation. The S2a/S2b/S5/S8 (GTPv2) interface becomes available for input. Enter the EPS Dedicated Bearers per Default. Available on AMF and SMF Node test cases and on gNB CU SA Nodal test case.

Tcl Parameter: PgwCEmulationEn

Select to trigger PDU Session Modification request from UE. NAS-5G SM | QoS Flow Modification is disabled for input.

Available on AMF Nodal, AMF Node and SMF Node test cases.

Select to enable the Nnrf Client Interface. NF Tab (NF Consumer - Nnrf Client). NF Tab (NF Producer - Namf ). NRF SBI SUT becomes available for input.

Additional details in this NRF Interface section.

Available when SMF Emulation and Intra-AMF Only are disabled on AMF Node test case. N14 interface provides a reference point between 2 Access and Mobility Management functions (AMF). Interface AMF-AMF becomes available for input.

The SUT is AMF SBI SUT and SMF SBI SUT (AMF Node and AMF SBI Node). The number of AMF Nodes and SMF SBI SUTs are always set to 1.

When SMF Emulation is disabled, N11 Interface toward SMF becomes available for testing. Namf, AMF-SMF as well as NAS-5G- MM tab only and N2 - NGAP are available for input.

Tcl Parameter: N14En

Available when SMF Emulation and N14 Interface are disabled on AMF Node test case. The SUT is SMF SBI SUT (AMF Node and AMF SBI Node). When SMF Emulation is disabled, N11 Interface toward SMF becomes available for testing. Namf, AMF-SMF as well as NAS-5G- MM tab only and N2 - NGAP are available for input.

SMF SBI SUTs are always set to 1.

Tcl Parameter: IntraAmfOnlyEn

NLs interface provides a reference point between the Access and Mobility Management functions (AMF) and the (LMF) Location Management function. Interface AMF-LMF becomes available for input.

The NLs Interface is disabled in test configurations when the AMF SBI Node is not enabled on Network Devices. The AMF SBI Node is enabled when SMF Emulation is off, or any of the following test options are on:
    NRF Interface
    N8 Interface
    N12 Interface
    N22 Interface
    N50 Interface

Not available when LCS Support is enabled on AMF Node test case.

The SUT is LMF SBI SUT.

Tcl Parameter: NlsEn

NLg interface provides a reference point between the Access and Mobility Management functions (AMF) and the (GMLC) Gateway Mobile Location Centre. Interface AMF-GMLC becomes available for input.

The SUT is GMLC SBI SUT.

The NLg Interface is disabled in test configurations when the AMF SBI Node is not enabled on Network Devices. The AMF SBI Node is enabled when SMF Emulation is off, or any of the following test options are on:
    NRF Interface
    N8 Interface
    N12 Interface
    N22 Interface
    N50 Interface

Tcl Parameter: NlgEn

The N12 interface is also enabled on AMF Node Emulator Configuration. The SUT is AUSF SBI. Interface Namf (NF Tab - NF Producer) and AMF-AUSF (NF Tab - NF Consumer) become available for input. AMF SBI Node is available for input.

The N12 interface is also available on Service Based Nodal test case.

The SUT is SMSF SBI, select From AMF - Access and Mobility Function. Interface Namf (NF Tab - NF Producer) and AMF-SMSF (NF Tab - NF Consumer) become available for input. AMF SBI Node is available for input.

Tcl Parameter: N20En

The N20 interface is also available on Service Based Nodal test case.

The N22 interface is also enabled on AMF Node Emulator Configuration. The SUT is NSSF SBI. Interface Namf (NF Tab - NF Producer) and AMF-NSSF (Amf to Nssf NF Tab - NF Consumer) become available for input. AMF SBI Node is available for input.

The N22 interface is also available on Service Based Nodal test case.

Support URLLC is available on AMF Node Emulator Configuration with SMF Emulation enabled and on SMF Node Emulator Configuration and on AMF Nodal Test Configuration.

The URLLC (Ultra-Reliable Low Latency Communications) feature comes with two parts, i.e., the control and user plane layer. This feature is specific to the signaling part of redundancy for URLLC in the UE requested PDU Session Establishment procedure. Redundancy is achieved by having two GTP tunnel for the same PDU and the resources have needs to be allocated for the same. URLLC needs a always-on PDU session to be established before hand, this is initiated by the UE and then acknowledged by the network if certain conditions are met and with the local policies. Once the always-on PDU is established, which itself is one of the conditions for Redundancy, other checks have to be verified → SST is 2, 5QI should be set to 82. 

During or after a URLLC QoS flow establishment, if the SMF decided that redundant transmission shall be performed based on authorized 5QI, NG-RAN node capability and/or operator configuration, the SMF informs the PSA UPF and NG-RAN to perform redundant transmission via N4 interface and N2 information accordingly. 

1. Activate Redundant Transmission during PDU Session Establishment procedure. 2. Activate Redundant Transmission during PDU Session Modification procedure per reference is 23.502 and TR 23.725 

Limitations : The Redundant TNL information from the UE→SMF is covered, SMF→UPF is not supported. The 5QI value used for URLLC is 82. The Redundant GTP tunnel info: Transport Layer address and gTP-TEID is same as the existing tunnel info.

On AMF Nodal test case :

• Support URLLC is disabled by either "SMF/UPF Node Emulation" or "Fireball"
• 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.
• Checking "Support URLLC" will automatically check "GTP-U Include Sequencer Number" on the N3|GTP-U tab but it can be unchecked afterwards.
• When "Support URLLC" is checked, either "GTP-U Include Sequence Number" or "GTP-U Include UL QFI Sequence Number" must be checked.

Tcl Parameter: SupportUrllcEn

The N50 interface is also enabled on AMF Node Emulator Configuration. Interface Namf (NF Tab - NF Producer) becomes available for input. AMF SBI Node is available for input. N50 Interface and Emergency Alert are mutually exclusive.

N50 provides a reference point between Cell Broadcast Center Function (CBCF) and the Access and Mobility Management function (AMF).

AMF forwarding logic for CMAS warning messages has been added based on 

3GPP Spec in section 9.1.3.5.2 of 23.041:  

The AMF forwards Write-Replace Warning Message Request NG-RAN to NG-RAN nodes. The AMF shall use the list of NG-RAN TAIs to determine the NG-RAN nodes in the delivery area. If the list of NG-RAN TAIs is not included and no Global RAN Node ID has been received from the CBCF, the message is forwarded to all NG-RAN nodes that are connected to the AMF. If a Global RAN Node ID has been received from the CBCF, the AMF shall forward the message only to the NG-RAN nodeindicated by the Global RAN Node ID IE. Ngap Tab (PWS Configuration).

Tcl Parameter: N50En

The UDM (N8) interface is enabled on AMF Node Emulator Configuration. The SUT is UDM SBI. Interfaces AMF-UDM (NF Tab - NF Consumer) and Namf (NF Tab - NF Producer) become available for input. AMF SBI Node is available for input.

The N8 interface is also available on Service Based Nodal test case.

The SUT is PCF SBI, select From AMF (N15)- Access and Mobility Function. Interface Namf (NF Tab - NF Producer) and AMF-PCF (Amf to Pcf NF Tab - NF Consumer) become available for input. AMF SBI Node is available for input.

Also available on Service Based Nodal test case when Test PCF (Npcf) and From AMF (N15) are enabled. 

We have support of UE Policy Association Establishment in SBI Nodal and Node. Now this support has been extended to the N1/N2 interface and all the way to the UE. Per Spec reference is 29.513 sec 5.6.1.2. See figure 5.6.1.2-1 : UE Policy Association Establishment procedure - Non-roaming. 

24.501 Annex D defines several UE Policy Delivery Service messages:

• UE State Indication
• Manage UE Policy Command
• Manage UE Policy Command Complete
• Manage UE Policy Command Reject

They are embedded either in a NAS container on N1 interface or in a Npcf/Namf message. More specifically:

• During UE registration, the UE State Indication, which contains the current UE local UPSIs, may be carried in a NAS container within Registration Request and then transferred to Npcf_UEPolicyControl_Create request.

• After the Namf_Communication_N1N2MessageSubscribe service operation, if the PCF decides to provide or update UE policies, it will send them using the Manage UE Policy Command which is embedded within Namf_Communication_N1N2MessageTransfer request and then transferred into a NAS container in DownlinkNasTransport.

• After possessing the Manage UE Policy Command, the UE sends Manage UE Policy Command Complete or Reject in the uplink direction.

Limitation:

For now we only support UE Policy Association Establishment with initial UE registration.

When "Command Mode" is "Enabled" and the test case is running, a "Command" button appears under the "Emulator Configuration" by the Mobile Subscribers section. 

Select to trigger Deregistration Request in Command Mode. 

Select to trigger Release Connection in Command Mode. 

Click the Command button on the LPP Tab and AMF-LMF to execute the Request Position Info Command.

Click the Command button on the PWS Tab  to execute the Send Message, Stop Message Command.

Select to enter Boundary Delimiter.

Use the MIP Scheme radio buttons to select a mobility scheme. Choices include Proxy MIP, Client MIP, or Simple IP. Define the MIP settings on the MIP tab. The MIP tab is available when you select Client MIP or HA Node Emulation on the Test Configuration tab.

You can use the BS-ASN gateway IPSec to encrypt control plane traffic between the Base Station and ASN nodes. Define the IKE settings on the ASN IPSec tab.

Tcl Parameter: BsIpSecEn

Select to enable the R3 Interface - MIP Tab.

Tcl Parameter: HaEmulation

Select to be able to adjust (attach / detach) the number of sessions established (mobile or UE) during a running test in the Data Traffic Mixer. Available in AMF Nodal, IP Application Node, MME Nodal and SMF Nodal when Data Traffic is enabled (with DMF) and Test Activity = Capacity. Also requires a TAS that supports Data Tuning. 

Added the ability to adjust the number of Session Established  (UE / mobile) and DMF Rate at test session level.

Added options : Manual / Auto

Default : Manual

When the test is started in Auto Mode, the Data Tuning tab appears. Sample successful Data Tuning in Auto mode:

When the test is started in Manual Mode, the Data Tuning tab appears. Initially no UEs are attached. You can start them manually by adjusting the UE % slider bar. The number of UEs running independently can be adjusted for each process. You can also adjust the DMF Rate %. It is initially configured to do 100% of the configured rate. It can be adjusted up to 250% of the configured transaction rate. Thus, if the configured transaction rate is 100 you can increase it to 250. Likewise you can go the other way and reduce the transaction rate. 

In the Data Traffic Tab - Click on Set UE % to enter the percentage of UEs to actually send data traffic. 

Tcl Parameter: DataTuningEn

Support for SGi PtP tunneling based on UDP. Used to deliver Non-IP data to AS via SGi. Per 3GPP TS 23.401 v 14.3.0.

Available in MME Nodal/MME Node when SGW/PGW Node Emulation is enabled.

Available in SGW Node when PGW Node Emulation is enabled.

Available in PGW Node.

Define PtP Tunnel - Access Stratum (Protocol = UDP, Source Port, Destination Port) in Network Devices (MME Nodal, MME Node, PGW Node and SGW Node).

Tcl Parameter: SgiPtpTunnelEn

Fireball

Fireball is a DMF threading model that provides optimized performance. This is a licensed feature. Additional details in Fireball Data Message Flows. See this table for supported options. 

Fireball does not support any Data IPSec test scenario.

Fireball does not support ciphering protection and integrity protection for F1UP data - Nas 5G Sm (Include Security Indication), Nas 5G Mm Security Mode ( Integrity Algorithm, Ciphering Algorithm)

Fireball does not support fragmentation - Data Message Flow Packet Size

• Available in AMF Nodal test case when Data Traffic is enabled, Test Activity = Capacity , Session Loading Test, Intra-AMF Mobility, Inter-AMF Mobility, and Inter Technology Mobility" with Handoff Protocol = LTE and Data IPSec or N3IWF are not enabled. Disabled for SMF/UPF Emulation with N6|Data Traffic/NAT enabled. Fireball is disabled for "Inter Technology Mobility" with Handoff Protocol = Wifi. When Test Activity = Session Loading Test, only Fireball UDP, TCP, HTTP, QUIC (fb_udp, fb_tcp, fb_http, and fb_quic) are supported.
• Available in gNB CU NSA Nodal test case when Data Traffic is enabled , Test Activity = Capacity and Data IPSec is not enabled. Added the capability to run Fireball when Bearer Type = Split Bearer. 
• Available in gNB CU SA Nodal test case when Data Traffic is enabled , Test Activity = Capacity.
• Available in gNB CU Node test case.
• Available in IP Application Node test case when Data Traffic is enabled, Test Activity = Capacity or Session Loading Test, MS Transport IP/Ethernet is enabled and Data IPSec is not enabled. When Test Activity = Session Loading Test, only Fireball UDP, TCP, HTTP, QUIC (fb_udp, fb_tcp, fb_http, and fb_quic) are supported.
• Available in MME Nodal test case when Data Traffic is enabled, Test Activity = Capacity, Session Loading Test, Intra-MME Mobility , Inter-MME Mobility and Data IPSec is not enabled. On MME Nodal's Test Configuration tab and on Gm|Media when VoLTE + RTP Traffic is enabled. When Test Activity = Session Loading Test, only Fireball UDP, TCP, HTTP, QUIC (fb_udp, fb_tcp, fb_http, and fb_quic) are supported.
• Available in MME Node test case when Mobility = None or Intra-MME or  Inter-MME and SGW/PGW Node Emulation is enabled.
• Available in Network Host test case when IP/Ethernet is enabled and Data IPSec is not enabled.
• Available in PGW Nodal test case when Data Traffic is enabled, Test Activity = Capacity, Protocol = GTPv2 and Data IPSec is not enabled.
• Available in PGW Node test case when (Mobility = None and Protocol = GTPv2 is enabled) or (Sxb Interface to CP is enabled). Data Traffic and Fireball are mutually exclusive in the PGW Node TC. If you select Data Traffic, the Fireball checkbox becomes disabled.
• Available in SGW Nodal test case when Data Traffic is enabled, Test Activity = Capacity, and S5/S8 Protocol = GTPv2. Traffic Type = Continuous is required. All other options disabled.
• SGW Nodal now supports PGW Node Emulation with Fireball Data Traffic, and PGW Node Emulation with VoLTE Fireball RTP, (not simultaneously). If emulating PGW Node, requires Local Network Host for Fireball Data Traffic is required. If emulating PGW Node with VoLTE selected (Fireball RTP data), Local IMS Node is required.
• Available in SGW Node test case when (Protocol = GTPv2 and PGW Node Emulation are enabled) or (Sxa Interface to CP and/or Separate S5 Interfaces or (PGW Node Emulation and/or Sxa+Sxb Interface to CP). All other options disabled.
• Available in SMF Nodal test case when Data Traffic is enabled, Test Activity = Capacity, Intra-AMF Mobility, Inter-AMF Mobility,Inter Technology Mobility . Disabled for SMF/UPF Emulation with N6|Data Traffic/NAT enabled. On SMF Nodal's Test Configuration tab and Gm|Media when Vo5G + RTP Traffic is enabled.
• Available in UE Emulator Data Node test case when Data Traffic is enabled and Data IPSec is not enabled.
• Available in UPF Nodal test case when Data Traffic is enabled, Test Activity = Capacity.
• Available in UPF Node test case.
• Available in Wifi Offload Gateway Nodal test case when Test Activity = Capacity and when AP Tunnel Type = NONE. 
• Available in Wifi Offload Gateway Node test case. It is enabled when "AP Tunnel Type" is "GRE L2" and "Mobility Action" is "Normal".  Fireball is disabled by Emulator Options "Gn to GGSN", "S2a to PGW", "S2b to PGW", "Inter SSID Mobility", and "AP-WAN PPPoE".

Added support for Vlan IDs when running Fireball. Dynamic VLAN is not supported at this time.

Your Test Server must be licensed and configured properly to run Fireball. Go to Test Server Configuration and set Data Gen Performance to Fireball. Go to Managing Test Server Capacity License and select an appropriate License. Contact support with any questions.

Next Hop IP Address must be configured. 

For MME Nodal, the Next Hop IP Address must be configured on the eNodeB User Node. It needs to point at the SGW User Node IP address.

Tcl Parameter: FireballEn

CIoT

CP-CIoT EPS Optimization Supported

Ignore RAI

T6a Interface

S1-U Data Transfer Supported

Use Service Request If Apply

Activate S1-U Data Transfer

Active After (ms)

UP-CIoT EPS Optimization Supported

Suspend Context When Idle

NB-IoT

Preferred CIoT

Send Last Message with RAI

Enable ROHC

      ROHC Profile ID      

NB-CIoT Supported on Specific NAS Sessions via TDF

Cellular Internet of Things (CIoT) - Cellular network supporting low complexity and low throughput devices for a network of Things. Cellular IoT supports both IP and Non-IP traffic. This is a licensed feature.

Cellular IoT EPS Optimizations provide improved support of small data transfer. One optimization is based on User Plane transport of user data and is referred to as User Plane (UP-CIoT EPS Optimization). Another optimization, known as Control Plane (CP-CIoT EPS Optimization), transports user data or SMS messages via MME by encapsulating them in NAS, reducing the total number of control plane messages when handling a short data transaction. These optimizations can be used separately e.g. if the UE or the network supports one of them, or in parallel if the UE and the network supports both. If both the Control Plane and User plane CIoT EPS optimizations are supported for a UE, the PDN connections that only use the Control Plane CIoT EPS Optimization i.e. the MME has included Control Plane Only Indicator in ESM request will only be handled via the Control Plane CIoT EPS optimization. All other PDN connections are handled using Control Plane or User Plane CIoT EPS optimizations. In addition, the Control Plane CIoT optimization can be used to support PDN connections to an SCEF, while regular S1-U data transfer is used independently to support PDN connections to P-GW. All the SGi PDN connections of a UE shall either use S11-U or S1-U at any point in time.

The User Plane CIoT EPS Optimization functionality enables support for transfer of user plane data without the need for using the Service Request procedure to establish Access Stratum (AS) context in the serving eNodeB and UE.

Additional details in 3GPP TS 24.401 (v13.7.0), TS 24.301 (v13.6.1), 36.413 (v13.3.0) and 29.274 (v13.6.0).

Available for Test Activity = (Capacity Test, Session Loading Test, Session Loading with Mobility, Intra-MME, Inter-MME, Command Mode/Sequencer when Handoff Protocol = "None" ) and NAS Tab Version >= 13.6.1 and S1-AP Version >= 13.3.0 (MME Nodal).

Available when Mobility = None on MME Node Test Case.

Available for Test Activity = Capacity Test or Session Loading Test (SGW Nodal).

Available for Test Activity = Capacity Test (gNB CU NSA Nodal).

CP-CIoT EPS Optimization Supported - Select to enable Control Plane CIoT EPS Optimization Supported. Available in MME Nodal/Node and SGW Nodal.

Tcl Parameter: CpCiotEpsOptimizationEn

Ignore RAI - Available in MME Node test case when Control Plane CIoT EPS Optimization Supported is enabled. Select to ignore the RAI byte.

Tcl Parameter: CpCiotIgnoreRai

T6a Interface - Available in MME Node test case when Control Plane CIoT EPS Optimization Supported is enabled. Select to support Non-IP Data Delivery (NIDD) through T6a reference point between Mobility Management Entity (MME) and  Service Capability Exposure Function (SCEF) for reporting UE Loss of Connectivity, UE reachability, location of the UE and change in location of the UE, and Communication Failure. This capability provides the ability to send data over the control plane (MME/SGSN) in a NAS message, thus reducing the total number of control plane messages required for small data delivery.

Click to get additional details on T6a Interface.

S1-U Data Transfer Supported - Available in MME Nodal and MME Node test cases when Control Plane CIoT EPS Optimization Supported is enabled. Select to trigger control plane service flag with active flag for NB-IOT device emulation.

Use Service Request If Apply- Available in MME Nodal and MME Node test cases when Control Plane CIoT EPS Optimization Supported and S1-U Data Transfer Supported are enabled. Select for UE Triggered Service Request in Idle Mode (based on 23.401 section 5.3.4.1).

Tcl Parameter: CpCiotUseSvcReqEn

Activate S1-U Data Transfer - Available in MME Nodal and MME Node test cases when Control Plane CIoT EPS Optimization Supported and S1-U Data Transfer Supported are enabled. Select to activate S1-U data transfer.

Enter Active After (ms) - Enter active time in milliseconds. Range: 0 to 65534000, Default = 5000

Tcl Parameter: CpCiotS1uActiveEn

Tcl Parameter: CpCiotS1uActiveDelay

Tcl Parameter: CpCiotS1uXferEn

UP-CIoT EPS Optimization Supported - Select to enable User Plane CIoT EPS Optimization Supported. Available in MME Nodal/Node.

Tcl Parameter: UpCiotEpsOptimizationEn

Suspend Context when Idle  - Available when User Plane CIoT EPS Optimization Supported is enabled. Select to suspend context when idle. (UeContextReleaseRequest)  Available in MME Nodal.

Tcl Parameter: UpCiotIdleSuspendEn

CP-CIoT  - Available when Control Plane CIoT EPS Optimization Supported is enabled. Select for CPCIoT indication.  Available in SGW Nodal.

Tcl Parameter: CpCiotOnlyEn

NB-IoT  - Available when Control Plane CIoT EPS Optimization Supported is enabled. Available in MME Nodal.

Tcl Parameter: NbIotEn

Narrowband-IoT is a 3GPP Radio Access Technology that forms part of Cellular IoT. It allows access to network services via E-UTRAN with a channel bandwidth limited to 180 kHz (Corresponding to one PRB).

To configure for WideBand IoT (WB-CIoT) : Enable CP-CIoT EPS Optimization Supported and UP-CIoT EPS Optimization Supported and

Preferred CIoT = CIoT No Additional Info.

Select to enable Preferred CIoT. Available when Control Plane CIoT EPS Optimization Supported or UP-CIoT EPS Optimization Supported is enabled. Available in MME Nodal.

Options: CIoT No Additional Info, CP-CIoT, UP-CIoT.

Tcl Parameter: PreferredCiot

Send Last Message with RAI. Available for Test Activity = (Capacity Test, Session Loading Test, Session Loading with Mobility, Intra-MME, Inter-MME, Command Mode/Sequencer when Handoff Protocol = "None" ) and NAS Tab Version >= 13.6.1 and S1-AP Version >= 13.3.0 (MME Nodal).  Select for Retrieve UE Info Procedure with RAI (Release Assistance Indication). Only applies to DMF Protocol = ping, raw, udp, tcp, sctp with limited # of transactions.

Options: 0, 1, 2

• Option 0 = No information regarding DDX is conveyed by the information element. If received, it shall be interpreted as 'neither value "01" nor "10" applies'

• Option 1 = No further uplink or downlink data transmission subsequent to the uplink data transmission is expected.

• Option 2 = Only a single downlink data transmission and no further uplink data transmission subsequent to the uplink data transmission is expected.

Tcl Parameter: CpCiotSendLastMsgWithRai

Enable ROHC. Available when CP-CIoT EPS Optimization Supported and NB-IOT are enabled and Preferred CIoT = CP-CIoT on MME Nodal test case and when CP-CIoT EPS Optimization Supported is enabled on MME Node Test Case.

Select for Robust Header Compression.  

Select ROHC Profile ID. Options: ROHC_PROFILE_IP (version 1, default ) or ROHCv2_PROFILE_IP

Tcl Parameter: NbIotRohcEn

Tcl Parameter: NbIotRohcProfileId

NB-CIoT Supported on Specific NAS Sessions via TDF - Available for Test Activity = (Capacity Test, Session Loading Test, Session Loading with Mobility, Intra-MME, Inter-MME, Command Mode/Sequencer when Handoff Protocol = "None" ) and NAS Tab Version >= 13.6.1 and S1-AP Version >= 13.3.0 (MME Nodal). Not available if CP-CIoT EPS Optimization Supported or UP-CIoT EPS Optimization Supported are enabled.

IMSI is used to identify the NAS Session in this TDF. This TDF overlays NAS Sessions with RAT type 0 (NB-CIoT). No other RAT type is currently supported. TACs in this TDF are used for NB-CIoT and should be among the TACs configured by GUI. Multi-TACs can be configured to NB-CIoT. For NAS Sessions not in the TDF, all configurations via the GUI are not changed.

Example tdf file : enbwithdifferentrattype.csv

Tcl Parameter: NbCiotCfgFileEn

Tcl Parameter: NbCiotCfgFile

Enable Network Location. Available in IMS Node, PCRF Node, PGW Node and SGW Nodal.

Follow link for additional information on IMS Node Network Location Support.

Follow link for additional information on PCRF Node Network Location Support.

Follow link for additional information on PGW Node Network Location Support.

Follow link for additional information on SGW Nodal Network Location Support.

Tcl Parameter: NetLocEn

Select to test the SIP Vo5G feature which supports SIP and RTP-based Voice in the 5G test cases.

You are required to configure the following:

• Vo5G
• Phonebook: SIP Subscribers; SIP Endpoints; Server Profile
• Gm Interface: Control: SIP Media: RTP

Available in IP Application Node, MME Nodal, PGW Nodal, SGW Nodal and Wifi Offload Gateway Nodal Test cases. The CSC-4 Interface along with the the CSC-4 APP Tab, TLS Tab and the CSC-4 Flows Tab become available for input.

The Landslide VoLTE modules have been enhanced to support configuration management over HTTP for Mission Critical Push-to-Talk (MCPTT) specified in the 3GPP specifications, including TS 23.280, 22.179, 23.179, 24.379, 24.380, 33.179, 24.382, 24.384, etc. The SUT is the EPC core including PCRF. Landslide is used to emulate MC-PTT clients.

Mission Critical Push-to-Talk (MC-PTT) is one of important technologies that helps to enable the public safety broadband network proposed by First Responder Network Authority (FirstNet). MCPTT is one of the services under the 3GPP Mission Critical Services (MCS) framework. All of the MCS utilize the MC core provided by 3GPP networks to enable MCS subscribers to communicate with fast setup times, strong security and priority handling. MC services include MCPTT, as well as MC Data, MC Video, etc.   

The configuration management interface is called CSC-4 and shown in the following diagram from TS 23.280. It is between the Configuration Management Client (CMC) residing in MCPTT UE, and the Configuration Management Server (CMS) within Common Service Core (CSC). It is used to configure MCPTT service, as well as MCData, and MCVideo services.  This feature focuses on configuration management in MCPTT services based on On-network model, which includes UE configuration, user profile configuration, service configuration, and group configuration.

However, group configuration shown in the diagram is between Group Management Client (GMC) and Group Management Server (GMS) over CSC-5 interface is not currently supported.

Tcl Parameter: MissionCriticalCsc4ClnEn

Select for Network Triggered Service Restoration (NTSR). Available in MME Nodal (Capacity Test only), MME Node and SGW Node Test cases (disabled if either CUPS (Sxa / Sxb) option is enabled).

When NTSR is enabled, the SGW Node will send a DDN  (Down Link Data Notification) to the MME when it detects restart via the "restart counter" ( Restart Counter (GTPv2))  in any GTP Signaling message or Echo Request/ Response Message. The Network Devices (NTSR - MMESut_1 and MMESut_2) configured in the SGW Node will be used to pick an MME S11 link to send the DDN Message to. The MME SUT will send a Paging Message upon receipt of the DDN Message to the eNodeB. This will result in the sending of a Service Request Message to the MME to re-establish the session.

Tcl Parameter: NtsrEn

Available in AMF Nodal, IP Application Node, MME Nodal and Network Host Test cases. Not available when Data Traffic, Data IPSec, External Data, Fireball, VoLTE are selected.

The WebRTC Interface along with the the WebRTC, SIP, TLS Tab, OTT Access Auth and the WebRTC Flows Tab become available for input. Control: WebRTC, TLS Tab, TCP. Media: Voice/Video - RTP, Voice/Video - SRTP , MSRP, OTT Access Auth

Enable WebRTC for support of WebRTC load testing. Refer to RFC 5389 for Session Traversal Utilities for NAT (STUN) and RFC 6455 for WebSocket Protocol.

In the Network Host test case, select either Endpoint or Proxy. When Proxy is enabled, the Media Tab is hidden in the WebRTC.

Available on AMF Nodal Test Configuration.

Available on IP Application Node.

Available on Network Host (for B2B testing)

Available on MME Nodal Test Configuration.

Tcl Parameter: WebRtcEn

Tcl Parameter: WebRtcGwMode

N2 IPSec

Target N2 IPSec

Select N2 IPSec to enable IPSec on the N2 Interface. In AMF Nodal / AMF Node testing, select the N2 IPSec option to encapsulate traffic between the gNB and AMF for Control / User Planes. When enabled N2 IPSec becomes available for input on the N2 Interface.

N2 IPSec disables N3IWF, TWIF, and 5G-RG on AMF Nodal test case.

Select Target N2 IPSec to enable IPSec on the Target N2 Interface. In AMF Nodal , the Target N2 IPSec checkbox is available when Test Activity is with Inter-AMF, Intra-AMF, Command Mode, and Sequencer. Configure parameters on Target N2-IPSec | Target N2-IPSec tab. When enabled the Target N2 IPSec becomes available for input on the Target N2 Interface.

Tcl Parameter: GnbAmfIpsecEn

Tcl Parameter: TargetGnbAmfIpsecEn

N3 IPSec

Target N3 IPSec

Select N3 IPSec to enable IPSec on the N3 Interface. In AMF Nodal / AMF Node / UPF Nodal / UPF Node testing, select the N3 IPSec option to encapsulate traffic between the gNB and UPF for Control / User Planes. When enabled N3 IPSec becomes available for input on the N3 Interface.

Per (3gpp ts33.501 section 9.3) - 9.3 Security requirements and procedures on N3. N3 is the reference point between the 5G-AN and UPF. It is used to carry user plane data from the UE to the UPF.

N3 IPSec disables N3IWF, TWIF, and 5G-RG on AMF Nodal test case.

Select Target N3 IPSec to enable IPSec on the Target N3 Interface. In AMF Nodal , the Target N3 IPSec checkbox is available when Test Activity is Inter-AMF, Intra-AMF, Command Mode, and Sequencer. In UPF Nodal, the Target N3 IPSec checkbox is available when Test Activity is Mobility.

Configure parameters on Target N3-IPSec | Target N3-IPSec tab. When enabled the Target N3 IPSec becomes available for input on the Target N3 Interface.

Tcl Parameter: GnbUpfIpsecEn

Tcl Parameter: TargetGnbUpfIpsecEn

Select N4 IPSec to enable IPSec on the N4 Interface. In AMF Nodal / AMF Node / gNB CU SA Nodal / SMF Node / UPF Nodal / UPF Node testing, select the N4 IPSec option to encapsulate traffic between the gNB and UPF for Control / User Planes. When enabled N4 IPSec becomes available for input on the N4 Interface. In AMF Nodal, SMF/UPF Node Emulation must be enabled for N4 IPSec to become available for selection.

Per (3gpp ts33.501 section 9.9) - Security mechanisms for non-SBA interfaces internal to the 5GC and between PLMNs

Non-SBA interfaces internal to the 5G Core such as N4 and N9 can be used to transport signalling data as well as privacy sensitive material, such as user and subscription data, or other parameters, such as security keys. Therefore, these interfaces shall be confidentiality, integrity, and replay protected. 

Roaming interfaces between PLMNs except for N32, shall be confidentiality, integrity, and replay protected. Protection for the N32 interface is specified in clauses 13.1 and 13.2.

For the protection of the above mentioned non-SBA internal and roaming interfaces except N32, IPSec ESP and IKEv2 certificate-based authentication shall be supported as specified in sub-clauses 9.1.2 of the present document with confidentiality, integrity and replay protection. This security mechanism shall be used,, unless security is provided by other means, e.g. physical security. A SEG may be used to terminate the IPSec tunnels. 

QoS related aspects are further described in sub-clause 9.1.3 of the present document. 

NOTE:   It is up to the operator choice to use cryptographic solutions or other mechanisms to protect internal non-SBA interfaces such as N4 and N9. IPSec ESP implementation shall be done according to RFC 4303 [4] as profiled by TS 33.210 [3]. For IPSec implementation, tunnel mode is mandatory to support while transport mode is optional.  

IKEv2 certificate-based authentication implementation shall be done according to TS 33.310 [5]. The certificates shall be supported according to the profile described by TS 33.310 [5]. IKEv2 shall be supported conforming to the IKEv2 profile described in TS 33.310 [5]. 

Tcl Parameter: SmfN4IpsecEn

Dynamic HA

In the CSN Nodal, FA Nodal, and End-to-End Mobile IP test cases, you can use the Dynamic HA checkbox to enable dynamic Home Agent address resolution. When this option is enabled in the End-to-End Mobile IP test case, the HA SUT drop-down list is disabled. Select the Home Agent address to be used in the RRQ from the drop-down list.

MIP IPSec

In the FA Nodal, HA Nodal and CSN Nodal test cases, you can test using the Mobile IP VPN access model with the MIP IPSec checkbox. In this configuration, one IPSec tunnel is established between either an FA SUT and an HA node (FA Nodal) or an HA SUT and an FA node (HA Nodal) for control plane traffic. Define the IKE settings on the MIP IPSec tab.

MIPv6 IPSec

Use the checkbox to enable IPSec between the MN and HA. Define the IPSec settings on the MIPv6 IPSec tab.

LMA Emulation

Select the LMA Emulation checkbox for control node availability (S2a interface). The Bearer IP Address Pool on the Mobile Subscribers pane is only available when emulation is on.

PMIPv6 Transport

The PMIPv6 Transport dropdown list is available only when you select the LMA Emulation. When you select Transport as IPv4, you must enter the PMIPv6 Source Address for LMA Node.

PMIPv6

Use the checkbox to enable IPSec between the SGW/MAG/HSGW and PDN gateway/LMA. Define the IPSec settings on the PMIPv6 IPSec tab.

• In SGW Nodal and PGW Nodal test cases, the PMIPv6 IPSec checkbox is available only when PMIPv6 protocol is selected. In SGW Nodal testing, PMIPv6 is available only when UMTS release version is 8.

• In PGW Nodal testing, The UE Initiates Dedicated Bearers and Max Bearers per Subscriber parameter are disabled for PMIPv6.

Femtocell IPSec

You can use the Femtocell IPSec checkbox to encrypt control plane and user plane traffic between the Femtocell node and Femtocell Gateway SUT. Define the IKE settings on the RP IPSec tab.

Auto-Start Auxiliary Sessions

When auxiliary service instances are supported, you can choose to activate them immediately after the MN's main service instance is activated or activate them when they are needed by a DMF with the Auto-Start Auxiliary Sessions checkbox. You can trigger service instance activation by adding event controls to your DMF.

Route Optimization

Optional in the IPv6 HA Nodal and IPv6 CN Nodal test cases when Data Traffic is included in the test.

Initial Network

Select the Initial Network from the dropdown list. This option is available only when you select the Inter Technology Mobility as the Test Activity.

Options: CDMA Network, WiMAX Network

Default: WiMAX Network

Tcl Parameter: InitiateType

MIP Protocol

Select the MIP Protocol used to define attributes for Mobile IP Registration Request (RRQ) messages (MIPv4) between UE, PDIF-FA's and HA or the types of Mobile IPv6 and ICMPv6 messages the UE will send (MIPv6).

Tcl Parameter: MipVersion

Route Optimization

Route Optimization is optional in the CDMA WiFi Convergence testing when Data Traffic is included on the Test Configuration tab. See also Route Optimization on the Data Traffic tab.

Tcl Parameter: Mip6MnRouteOptEn

MIP IPSec

Select MIP IPSec (on the CDMA/WiFi Convergence Test Configuration tab) to encrypt control plane traffic between the MSs and the PDIF-FAs sent to the HA node. See MIP IPSec tab for defining IKE settings.

Tcl Parameter: MipIpSecEn

HA Node Emulation

In the CDMA/WiFi Convergence test case to select HA Node Emulation to simulate a Home Agent when an HA SUT is not used. You can define Home Agent node on the Network Configurations tab.

Initial Network

Select the Initial Network from the dropdown list. This option is available only when you select the Inter Technology Mobility as the Test Activity.

Options: CDMA Network, WiMAX Network

Default: WiMAX Network

Tcl Parameter: InitiateType

BS-ASN IPSec

You can use the BS-ASN gateway IPSec to encrypt control plane traffic between the Base Station and ASN nodes. Define the IKE settings on the ASN IPSec tab.

Auto-Start Auxiliary Sessions

Dynamic HA

In the CSN Nodal, FA Nodal, and End-to-End Mobile IP test cases, you can use the Dynamic HA checkbox to enable dynamic Home Agent address resolution. When this option is enabled in the End-to-End Mobile IP test case, the HA SUT drop-down list is disabled. Select the Home Agent address to be used in the RRQ from the drop-down list.

MIP IPSec

In the FA Nodal, HA Nodal and CSN Nodal test cases, you can test using the Mobile IP VPN access model with the MIP IPSec checkbox. In this configuration, one IPSec tunnel is established between either an FA SUT and an HA node (FA Nodal) or an HA SUT and an FA node (HA Nodal) for control plane traffic. Define the IKE settings on the MIP IPSec tab.

MIPv6 IPSec

Use the checkbox to enable IPSec between the MN and HA. Define the IPSec settings on the MIPv6 IPSec tab.

LMA Emulation

Select the LMA Emulation checkbox for control node availability (S2a interface). The Bearer IP Address Pool on the Mobile Subscribers pane is only available when emulation is on.

The PMIPv6 Transport dropdown list is available only when you select the LMA Emulation. When you select Transport as IPv4, you must enter the PMIPv6 Source Address for LMA Node.

PMIPv6

Use the checkbox to enable IPSec between the SGW/MAG/HSGW and PDN gateway/LMA. Define the IPSec settings on the PMIPv6 IPSec tab.

• In SGW Nodal and PGW Nodal test cases, the PMIPv6 IPSec checkbox is available only when PMIPv6 protocol is selected. In SGW Nodal testing, PMIPv6 is available only when UMTS release version is 8.

• In PGW Nodal testing, The UE Initiates Dedicated Bearers and Max Bearers per Subscriber parameter are disabled for PMIPv6.

Dynamic Ha Support

In HA Node test case, select to use Dynamic HA Support to enable dynamic Home Agent address resolution, if you wish to set the address in the initial RRQ to 0.0.0.0.

Find MN By NAI

Select to map NAI to HA and use the TDF on MIP tab

DMU

Select to enable DMU (Dynamic Mobile IP Update) - A security feature that allows RSA encryption keys into mobile station to enable secure distribution of mobile IP keys.

Tcl Parameter: DmuEn

Periodic DMU After Session Established

Select to enable a DMU update after the session is established. Enter the frequency in the DMU Interval. Available when DMU is enabled.

Tcl Parameter: PeriodicDmuEn

DMU Interval (s)

Enter the interval in seconds when to perform a periodic DMU (Dynamic Mobile IP Update) after the session has been established.  

Range : 1 to 4000000

Default : 120

Tcl Parameter: DmuInterval

GPRS Testing

The GGSN Nodal test case tests at least one GGSN SUT, and can support testing two GGSNs in a VPRN configuration.

• The GGSN SUT services the MN PDP contexts in all configurations and terminates the L2TP tunnel in an L2TP VPN test.

• When the SUT uses different IP address for control and bearer plane (user) traffic, you can specify the address used for bearer plane traffic by checking the Alt Data box, and selecting a bearer plane "SUT". If a different address is received in a Create PDP Context Response, that address will be used instead of the defined address. You can also define alternative bearer plane IP addresses for the SGSN nodes by enabling the User Node.

• In a VPRN test, one GGSN services the PDP contexts and another GGSN terminates the L2TP tunnel. Check the L2TP box and select the SUT that will terminate the tunnel.

IP Data Testing

• In the IP Application Node test case, the routing defined for the Client Nodes determines which Content Gateway SUT is tested.

• In the PDG Micro-Mobility test case, the IPSec tunnel endpoint determines which PDG is tested.

Initial Network

Select the Initial Network from the dropdown list. This option is available only when you select the Inter Technology Mobility as the Test Activity.

Options: CDMA Network, WiMAX Network

Default: WiMAX Network

Apply Parameter Values from Test Data Files

You can provision explicit values for the R6 Protocol and WiMAX Forum Protocol by using Test Data Files. Download a sample file by right-clicking the link below.

See Applying Parameter ValuesApplying Parameter Values.

• r6protocol.csv

Vendor Variant

In both DCCA Nodal and Node test cases, select the Vendor Variant from the drop-down list. Selecting Vendor Variant 1 the Vodafone Options checkbox becomes available. Selecting the Vodafone Options checkbox allows you to enter the relevant configuration parameters on the DCCA App tab in DCCA Nodal and DCCA Node test cases.

Tcl Parameter: VendorVariant

Diameter IPsec

DCCA Node Testing

The Diameter IPSec checkbox is available when the test case is set with only a Primary DCCA Node. That is, only when Re-Auth test is not None, Primary/Secondary Proxy check box is not selected, and DCCA Secondary Node is not selected.

Affinity Mode

Select Affinity Mode to turn on performance improvement of Diameter Applications.

Significant performance impact can be achieved with Affinity Mode, especially, when running multiple test cases on the same process. A higher activation rate/throughput can be expected. 5 test cases are optimum as all cores will be used per one process on the C100 S2. Other systems may have a different number of cores per process and the recommended number of test cases should be adjusted accordingly.

In both DCCA Nodal and Node test cases, select the Vendor Variant from the drop-down list. Selecting Vendor Variant 1 the Vodafone Options checkbox becomes available. Selecting the Vodafone Options checkbox allows you to enter the relevant configuration parameters on the DCCA App tab in DCCA Nodal and DCCA Node test cases.

Select Affinity Mode to turn on performance improvement of Diameter Applications.

Significant performance impact can be achieved with Affinity Mode, especially, when running multiple test cases on the same process. A higher activation rate/throughput can be expected. 5 test cases are optimum as all cores will be used per one process on the C100 S2. Other systems may have a different number of cores per process and the recommended number of test cases should be adjusted accordingly.

Use the drop-down list to force the server node to send Re-Auth-Requests to the client for all active CC sessions. The client must respond with a Re-Auth-Answer and follow up with an update CCR for that CC session. You can define the starting time and transmission rate for the RAR messages, and choose whether the server node will respond in a positive or negative manner.

Options:

• None — Re-Auth-Requests are only sent when the validity time expires.

• Re-Auth — Requests are sent for all MN sessions. The server responds to update CCR messages with result code 2001, DIAMETER_SUCCESS, assuming that no other reason prevents the session from continuing.

• Re-Auth-Reject — Requests are sent for all MN sessions. The server always responds to update CCR messages with result code 5003, DIAMETER_AUTHORIZATION_REJECTED.

Default: None

Tcl Parameter: DiaSrvCcReAuth

The rate at which the test attempts to deactivate any active sessions with an ASR message when the test case is stopped.

Range: 1 — Variable1

Default: 1

Tcl Parameter: DiaSrvCcAuthRate

The number of seconds the node will wait, after all CC sessions are established, before beginning to transmit Re-Auth-Requests.

Range: 10 — 65535

Default: 10

1 Maximum rates, number of sessions, and number of emulated nodes vary depending on the test application and the test system's licensed capacity.

Tcl Parameter: DiaSrvCcAuthTime

Use the Primary Proxy and Secondary Proxy checkboxes to indicate whether proxies will be emulated.

When you select Primary and Secondary proxy servers, Failover support is available and the settings for the secondary server emulator are enabled.

Use Secondary DCCA Node checkbox to allow definition of both the Primary and Secondary Server Nodes. See DCCA Server Node.

When the Node Configuration supports primary and secondary servers or proxies, you can enable or disable failover support. Transport layer failure on the primary node can be simulated at a time that you define. The node notifies the client whether failover is supported or not with the CC-Session-Failover AVP

• Learn more about failover processing

Options: Not Supported or Supported

Default: Supported

Tcl Parameter: DiaSrvCcFailover

Use the drop-down list to enable failure simulation.

Options: No or Transport Loss

Default: No

Tcl Parameter: DiaSrvCcFailoverType

Use the drop-down list to select the simulated failure trigger.

Options:

• Before Any Sessions Established — The node will stop responding after the Capabilities Exchange.

• After X Sessions Established — The node will stop responding after the number of sessions provisioned in X have been established.

• X Seconds After All Sessions Established — The node will wait for X seconds after the maximum Number of Sessions have been established and then stop responding. If all sessions are not successfully established, the failure will not be triggered.

Default: Before Any Sessions Established

Tcl Parameter: DiaSrvCcFailoverStart

Tcl Parameter: DiaSrvCcFailoverDelay

Select to process broadcast DHCP messages.

Options: True/False

Tcl Parameter: ProcessBroadcastMsgEn

Affinity Mode

Select Affinity Mode to turn on performance improvement of Diameter Applications.

Significant performance impact can be achieved with Affinity Mode, especially, when running multiple test cases on the same process. A higher activation rate/throughput can be expected. 5 test cases are optimum as all cores will be used per one process on the C100 S2. Other systems may have a different number of cores per process and the recommended number of test cases should be adjusted accordingly.

HSS Interfaces

Enable: Use to indicate whether DRA Nodal will emulate various HSS Interfaces.  When selected, LTE Version, the following nodes and interfaces are available for configuration.

Tcl Parameter: HssInterfacesEn

• LTE Spec Version: Use to specify a release version of 3GPP specification which DRA Nodal uses for constructing or interpreting messages.

Select the required LTE Spec Version from the dropdown list.

Options: 8.10.0, 9.2.0, 10.6.0, 11.4.0, 12.10.0, 12.X.0, 13.4

Tcl Parameter: HssLteVersion

• Client Interfaces: Select one or all of the available Client Interfaces: MME/SGSN, AS , CSCF, SCEF

Selecting one or more of the Client Interfaces requires you to configure MME/SGSN or AS emulated Nodes. Multiple Destination Host and Realm address is supported.

Tcl Parameter: MmeSgsnEn

Tcl Parameter: AsEn

Tcl Parameter: CscfEn

Tcl Parameter: HssScefEn

PCRF Interfaces

• Enable: Use to indicate whether DRA Nodal will emulate various PCRF and Client Interfaces.  When selected, the LTE Spec Version, PCRF Nodes and interfaces will be available for configuration

• LTE Spec Version: Use to specify a release version of 3GPP specification which DRA Nodal uses for constructing or interpreting messages.

Select the required LTE Spec Version from the dropdown list.

Options: 8.4.0, 8.5.0, 8.6.0, 8.7.0, 8.8.0, 9.4.0, 9.5.0, 9.6.0, 9.7.0, 9.8.0, 9.9.0, 10.6.0, 10.7.0, 10.8.0, 11.4.0, 11.6.0, 12.X.0

Tcl Parameter: PcrfLteVersion

• Client Interfaces: Select one or all of the available Client Interfaces: AGW, AF, BBERF, OCS. TDF

Selecting one or more of the Client Interfaces requires you to configure AGW, AF, BBERF , OCS and TDF emulated Nodes. Multiple Destination Host and Realm address is supported.

Tcl Parameter: AgwEn

Tcl Parameter: AfEn

Tcl Parameter: BberfEn

Tcl Parameter: OcsEn

Tcl Parameter: TdfEn

SCEF Interfaces

Enable: Use to indicate whether DRA Nodal will emulate various SCEF Interfaces.  When selected, LTE Version, the following nodes and interfaces are available for configuration.

Tcl Parameter: ScefInterfacesEn

• LTE Spec Version: Use to specify a release version of 3GPP specification which DRA Nodal uses for constructing or interpreting messages.

Select the required LTE Spec Version from the dropdown list.

Options: 13.1

Tcl Parameter: ScefLteVersion

• Client Interfaces: Select one or all of the available Client Interfaces: MME, SGSN,

Selecting one or more of the Client Interfaces requires you to configure MME/SGSN or AS emulated Nodes. Multiple Destination Host and Realm address is supported.

Tcl Parameter: ScefMmeEn

Tcl Parameter: ScefSgsnEn

OCS Interfaces

Enable: Use to indicate whether DRA Nodal will emulate the Gy OCS Interface.  When selected, LTE Version, the following nodes and interfaces are available for configuration.

Tcl Parameter: OcsInterfacesEn

• LTE Spec Version: Use to specify a release version of 3GPP specification which DRA Nodal uses for constructing or interpreting messages.

Select the required LTE Spec Version from the dropdown list.

Options: 9.4.0, 9.5.0, 9.6.0, 9.7.0, 9.8.0, 9.9.0, 10.6.0, 10.7.0, 10.8.0, 11.4.0

Tcl Parameter: OcsLteVersion

• Client Interfaces: Select one or all of the available Client Interfaces: PGW

Selecting one or more of the Client Interfaces requires you to configure PGW or AS emulated Nodes. Multiple Destination Host and Realm address is supported.

Tcl Parameter: OcsPgwEn

Generic (Gen) Interfaces

Enable to configure up to four Interfaces for Client or Server or both. Use the Profile Tab to add commands/Messages and fill them with AVP's from a defined AVP Database.

Tcl Parameter: GenInterfacesEn

Tcl Parameter: Gen1InterfacesEn Tcl Parameter: Gen1Name Tcl Parameter: Gen1ClnEn Tcl Parameter: Gen1SrvEn

Tcl Parameter: Gen2InterfacesEn Tcl Parameter: Gen2Name Tcl Parameter: Gen2ClnEn Tcl Parameter: Gen2SrvEn

Tcl Parameter: Gen3InterfacesEn Tcl Parameter: Gen3Name Tcl Parameter: Gen3ClnEn Tcl Parameter: Gen3SrvEn

Tcl Parameter: Gen4InterfacesEn Tcl Parameter: Gen4Name Tcl Parameter: Gen4ClnEn Tcl Parameter: Gen4SrvEn

Secondary DRA Node

Select to indicate support for DRA Node failover testing.

Tcl Parameter: SecondaryDraEn

Load Balancing

Select Load Balancing option that supports up to 50 million subscribers, only allowing tests in Proxy Mode. Currently only supported on the C100 M2 with Ultra Extreme license. This is a licensed feature.

When enabled, able to enter up to 50,000,000 subscribers on the Number of Subscribers field.

Tcl Parameter: LoadBalanceEn

Command Mode/Sequencer

The Command Mode and Sequencer options are available only when you select Secondary DRA Node, provides you have the appropriate system license.

Select Command Mode or Sequencer as required.

In eMBMS Node test case, there are three emulator modes:

• eMBMS-GW and BMSC: Emulate combined eMBMS-GW and BM-SC, the interface between eMBMS-GW and BM-SC won’t be exposed.

• eMBMS-GW: Emulate standalone eMBMS-GW.

• BMSC: Emulate standalone BM-SC.

Tcl Parameter : EmulatorMode

Capacity and Session Loading. WedDAV supported for Capacity type test only.

Synchronization Interval is the interval that each two continuous synchronization message are transmitted.

Range: 1 to 59999

Tcl Parameter: SyncInterval

The packets delivered over M1 interface are synchronously transmitted by eNodeBs. In order to support the inter-eNodeB content synchronization, SYNC protocol layer defined between BM-SC to eNB carries additional information that enable eNodeBs to identify the timing for radio frame transmission and detect packet loss. Every packet in M1 contains the SYNC protocol information which is encapsulated at BM-SC.

In eMBMS Nodal test case, Select Content Type.

Tcl Parameter : BmscContentType

If Content type = DMF, select to configure streaming IPDV measurement traffic to determine jitter and latency over M1 interface (between eNodeB and MBMS-GW).

If Content Type = WebDav, Configure FLUTE Tab and Content WEBDAV tab

In eMBMS Node Test case, select to emulate Multicast Query. Set Multicast Query Interval in M1 Interface (IGMP Tab).

Not available for standalone BMSC Mode.

Tcl Parameter : EmulateMCastQueryEn

Select for the MB2 reference point between the GCS AS and the BM-SC. Available on eMBMS Node when eMBMS-GW and BMSC is enabled and on IP Application node when SIP VoIP , GM only and Capacity Test Activity are enabled.

On eMBMS Node test case , the GCS-AS SUT is enabled for input. The BMSC MB2-C Node and BMSC MB2-U Node are used for Control and User plane communication between the GCS-AS and the BM-SC. Measurements in MB2 Session, Mb2 Node and Mb2 IP Instance.

On IP Application Node test case , the MB2-BMSC SUT is enabled for input. The MB2-C Node and MB2-U Node are used for Control and User plane communication between the GCS-AS and the BM-SC. Measurements in MB2 Session, Mb2 Node and Mb2 IP Instance.

According to 3GPP TS 23.468 section 5.1.1, MB2 offers access to the MBMS bearer service from a GCS AS. MB2 carries control plane (MB2-C) and user plane (MB2-U) between GCS-AS and BM-SC.

Figure. 1 Non-roaming architecture from 3GPP TS 23.468 v15.0.0.0.

MB2 has the following properties:

• MB2 is used by the GCS AS to interact with BM-SC for MBMS bearer management.

• The GCS AS may use the MBMS service from multiple BM-SCs, each with a separate MB2 interface.

• BM-SC shall provide service to multiple GCS AS (s) via a separate MB2 interface.

• Within one PLMN, an MBMS session is supported by exactly one BM-SC and provided for only one GCS AS.

• The data transferred via MBMS bearer (s) by the GCS AS is transparent to the BM-SC. A GCS AS may transfer data from one or multiple GCS groups via a single MBMS bearer.

• MB2 is a standardized secured interface to an AS.

• The GCS AS needs to be configured with the IP addresses or FQDN of the contact points of MB2-C. The MB2-C contact points needs to be configured per PLMN ID.

• The user plane transport information (e.g. IP address/UDP port) for delivering group communication data flow from the GCS AS to the BM-SC over MB2-U shall be exchanged over MB2-C.

Tcl Parameter : Mb2En

The number of bytes at which fragmentation will take place at the bearer plane IP layer.

Range from 123 to 9300

Default = 1400

Tcl Parameter : TrafficMtu

Enable to support Flute. Available in eMBMS Nodal, MME Nodal and SGW Nodal test cases.

If Flute is supported, treat downlink M1 data as Flute Data and Decode it.

If Flute is NOT checked, treat downlink M1 data as RTP data and it is not decoded.

Tcl Parameter : EmbmsFluteEn

Enter Delay Factor (ms) when Flute is enabled. Used to emulate the data transfer delay via air interface.

Available in eMBMS Nodal, MME Nodal and SGW Nodal test cases.

eMBMS M1/M3 Interfaces

(MME Nodal, MME Node and SGW Nodal)

eMBMS M1/M3 Interfaces is available only if your system is licensed and when Test Activity is Capacity. Available in MME Nodal, MME Node and SGW Nodal test cases.

Tcl Parameter: EmbmsEn

Available when eMBMS M1/M3 Interfaces is enabled in MME Nodal test case.   

M3ap Sessions per eNodeB

Range: 1 - 1000 (Range depends on License and whether FLUTE is enabled. If FLUTE is enabled, maximum = 100, Non-FLUTe = 1000)

Default: 1

eMBMS (MME Node and SGW Nodal)

Sm Sessions per MME

Available when eMBMS M3 Interface is enabled in MME Node Test case and eMBMS M1 Interface is enabled in SGW Nodal test case.

Sm Sessions per MME

Range: 1 - 1000

Default: 1

Available when Inter-CU Mobility Test Activity is enabled in gNB CU NSA Nodal test case. Click Settings and enter the Inter-CU Mobility settings.

Per Spec 3GPP TS 37.340 version 15.6.0 Release/section 10.5 Secondary Node Change (MN/SN initiated).

The Secondary Node Change procedure is initiated either by MN or SN and used to transfer a UE context from a source SN to a target SN and to change the SCG configuration in UE from one SN to another.

Select : MN-Initiated or SN-Initiated

• MN initiated SN Change

•  SN initiated SN Change

S1-MME interface with the NAS tab, F1 (F1-AP) and X2-ENB (X2-AP) become available for input. Target gNB DU Control Node , Target gNB DU User Node, (User and Control) Nodes. SUT is gNB CU (Number of Target gNB-CU SUTs)

Tcl Parameter : InitType

In gNB CU NSA 5GNSA-4G Mobility supports 5G NSA to 4G (eNB) handover as described in spec 3GPP TS 37.340 / section 10.8 Master Node to eNB/gNB Change. You define the S1-MME interface with the NAS tab, F1 with F1-AP, X2-ENB with X2-AP and Target eNodeB Control Node, Target eNodeB User Node, (User and Control) Nodes. SUT is gNB CU (Number of Target gNB-CU SUTs). 

Click Settings to enter the 5GNSA-4G-Mobility settings.

eNB sends out SgNB Release Request when handover happens;

Path Switch Request message is sent after received SgNB Release Request Acknowledge;

Path Switch Request Acknowledge triggers UE Context Release.

Spec 3GPP TS 37.340/section 10.8 Master Node to eNB/gNB Change.

1. Dual Connectivity 5G NSA to 4G eNB -EN-DC:

2. Handover from Dual Connectivity 5G NSA to 5G SA :

10.8.2 MR-DC with 5GC

3. eNB/gNB to Master Node change. Per 3GPP TS 37.340/section 10.9:

Click Settings to enter the 5GNSA-4G-Mobility settings.

Section 10.9.1 EN-DC - The eNB to Master Node change procedure is used to transfer context data from a source eNB to a target MN that adds an SN during the handover:

Master eNB sends out SgNB Addition Request when handover happens;

Path Switch Request message is sent after received SgNB Addition Request Acknowledge;

Path Switch Request Acknowledge triggers UE Context Release.

Select NSA Mode for the F1-AP interface between the gNB CU and gNB DU and the X2-ENB interface between the eNobeB and gNB CU. 

Interfaces F1 (F1-AP) and X2-ENB (X2-AP) become available for input. Nodes gNB CU Control Node and gNB CU User Node are available for input. Fireball is supported in NSA Node.

Tcl Parameter : GnbCuSaMode

Select SA Mode for gNB CU Node to emulate 5G support stand alone (SA) test, through F1-C and F1-U. Interfaces F1 (F1-AP), N2 (NGAP) and N3 (GTPU), AS-5G ( RRC, Message Editor) become available for input. Nodes N2 to AMF and N3 to UPF and AMF SUT are available for input. Fireball is not currently supported in SA Mode.

Select either 3GPP or proprietary customer Vendor 1 or proprietary customer Vendor 2, proprietary customer Vendor 3 or proprietary customer Vendor 4. 

These are the versions and max versions that will be allowed for Vendor 3. Any future version additions with higher values will be blocked at the OK button or Tcl Validate via GUI.

CU Node with Vendor 3 or Vendor 4 options:
   Rrc Tab - RRC max version is "16.5.0/July2021"
   Ngap Tab - NGAP max version is "16.2.0/Jul2020"

When SA Mode is selected, Enable UE Capability Enquiry on F1-AP is automatically enabled to accommodate additional security mode commands after the initial NAS exchange. For SA Mode = Vendor 2, 'UE Context Setup Request' (code 20) must be configured on F1-AP Message Editor - Json Message Editor. 

For SA Mode with Vendor 4 option: For Intra-DU Inter cell Handover.

In the Non Vendor 4 implementation the Transmission action indicator is included in message #3 which has to be moved to message#5 as per Vendor 4 requirements (shown below in the  code flow below). Also, the SpCell ID is not included in any of the Intra-DU Handover cases. Message #3 includes the target Cell ID in the Special Cell ID IE. Once the transmission action indicator with the value stop is received by the gNB-DU, the source cell traffic is stopped by updating with the DL Data Delivery status of the source cell DRB TEID (message #7).
Once the RRC Reconfiguration is complete, the DL Data Delivery status with the target Cell DRB TEID is sent.

Tcl Parameter : GnbCuSaModeType

Select for E1 interface to CU-UP Node in SA Mode. When enabled, "Xn Interface" and Fireball are disabled. Only 1 PDU can be configured.

One SUT gNB CU-UP SUT can be configured. gNB CU Control Node and gNB CU-CP E1 Node, E1 Interface - E1 Ap Tab becomes available for input. E1-AP Measurements

3GPP 38.401 NG-RAN Architecture Description

3GPP 38.462 E1 Signaling

3GPP 38.463 E1AP

Limitations: 

Current E1 interface support Landslide capacity test only.

1. Support one CU-CP to one CU-UP
2. Limited support to gNB-CU-UP E1 Setup procedure (successful case)
3. Limited support to E1AP Bearer Context Setup procedure (successful case)
4. Limited support to E1AP Bearer Context Modification (gNB-CU-CP initiated) procedure (NR-RAN, PDU Session Resource To Setup List, successful case)
5. Limited support to E1AP Bearer Context Release (gNB-CU-CP initiated)
6. Do not support multiple PDUs per UE session. 
7. Do not support mobility test scenarios
8. Do not support RRC inactive
9. Do not support PDU modification
10. Do not support UE Configuration Updates
11. Do not support MR-DC
12. Do not support E1 reset, either triggered from NG reset or F1 reset

Tcl Parameter : E1ToCuUpEn

Select for E1 interface to CU-CP Node in SA Mode.  See figure 6.1.2-1 for overall architecture and limitations for E1 Interface.

When enabled, "Xn Interface" and Fireball are disabled. Only 1 PDU can be configured.

One SUT gNB CU-CP SUT can be configured. gNB CU User Node and gNB CU-Up E1 Node, E1 Interface - E1 Ap Tab becomes available for input. E1-AP Measurements

3GPP 38.401 NG-RAN Architecture Description

3GPP 38.462 E1 Signaling

3GPP 38.463 E1AP

Tcl Parameter : E1ToCuCpEn

The Xn interface connects one gNB Node to another gNb Node in NG-RAN (see figure 4.1-1 per 3GPP TS 38.300 V15.5.0); and for separation of control and data, "Xn" is further divided into 2 interfaces: "Xn-C" is for the control messages connecting gNB-CU-CP of gNB-CU nodes and "Xn-U" is for user-plane messages connecting gNB-CU-UP of gNB-CU nodes.

The Xn interface is mainly used in handover procedures for information transfer and temporary data forwarding when UE moves away from an area controlled by one gNB node (source node) to a new area controlled by a different gNB node (destination node) - See Figure 9.2.3.2.1-1: Intra-AMF/UPF Handover in 3GPP TS 38.300 V15.5.0); 

When enabled, Xn-C (Xn Ap Tab), Xn-U (GTPU Tab) , Xn SUT , gNB CU Xn Control Node and gNB CU Xn User node become available for input.

Tcl Parameter : XnEn

Select for Multi-RAT Dual Connectivity (MR-DC) to support S-NG-RAN Node addition. The S-NG-RAN Node Addition procedure is to establish the UE context and relevant resources at the S-NG-RAN node. Added support for M-NG-RAN node initiated S-NG-RAN node Release with / without keeping UE.

Available when Xn interface is enabled on the gNB CU node test case. 

When enabled, the MR DC interface becomes available for input. MN-CU SUT becomes available when gNB Mode = SN. 

The MN-CU will configure A4 event on the NR Object during the UE attach. When the NR-DC trigger timer expires, the gnb CU Nodal will report the measurement for the A4 event. 

The MN-CU will fetch the target cell ID and other contents to take actions (Ex: SCG Addition or inter-gnb handover).

The relationship between the PDU session and SDAP is 1:1. The PDCP and DBR is 1:1.

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

Limitations : 

• Capacity is the only supported Test Activity
• Support for one CU Node only
• PDU Session reconnect/ release/ modify are not supported

Tcl Parameter : GnbCuMrDcEn

Data Forwarding for Mobility has been moved to N2|NGAP's "Direct Forwarding" checkbox with Tcl variable upgrade. Available when SA Mode is enabled. Select to support Xn HO with data forwarding.

When "Command Mode" is "Enabled" and the test case is running, a "Command" button appears under the "Emulator Configuration" by the Mobile Subscribers section. 

Select to trigger Reset in Command Mode. 

Click the Command button on the X2-AP to execute the Reset Command.

Select either 3GPP or proprietary customer Vendor 1 or proprietary customer Vendor 2, proprietary customer Vendor 3, or proprietary customer Vendor 4 .

When "Vendor 3" is selected, only "15.3.0/Sep2018" and "15.7.0/Oct2019" are available under the "Version (38.473)" dropdown list under the F1 (F1-AP).

These are the versions and max versions that will be allowed for Vendor 3. Any future version additions with higher values will be blocked at the OK button or Tcl Validate via GUI.

SA Nodal with Vendor 3 option:
   Rrc Tab - RRC max version is "16.5.0/July2021"
   Nas 5G Mm - NAS-5G max version is "16.5.0/Jul2020"
   Ngap Tab - NGAP max version is "16.2.0/Jul2020"

When "Vendor 3" is selected, the intra-DU inter-cell handover message flow will be as follows : 

Note: Message 5 is changed from DL RRC Message Transfer to UE Context Modification Request, and message 5.1 (UE Context Modification Response) is added.

SA Nodal with Vendor 4 option: For Intra-DU Inter cell Handover.

In the Non Vendor 4 implementation the Transmission action indicator is included in message #3 which has to be moved to message#5 as per Vendor 4 requirements (shown below in the  code flow below). Also, the SpCell ID is not included in any of the Intra-DU Handover cases. Message #3 includes the target Cell ID in the Special Cell ID IE. Once the transmission action indicator with the value stop is received by the gNB-DU, the source cell traffic is stopped by updating with the DL Data Delivery status of the source cell DRB TEID (message #7).
Once the RRC Reconfiguration is complete, the DL Data Delivery status with the target Cell DRB TEID is sent.

Tcl Parameter: VendorVariant

Available when Test Activity = Inter Technology Mobility. Select Initial Network from dropdown list. Options: 5GS

Initial Network indicates where the UE will initially attach / register. 

Select the Handoff Protocol below to indicate the "Target" network.

For example: Initial Network = 5GS , Handoff Protocol = LTE (which is the Target). The UEs will initially attach / register to 5GS then handoff to LTE. 

The F2 Help key has been enhanced to indicate which network is the Target.

Tcl Parameter : InitiateType

Available when Test Activity = Inter Technology Mobility.

When Handoff protocol = LTE, the S1-MME becomes available for input. EPS Pane is enabled.  

Options : LTE 

3GPP 23.501, 23.502, 38.413, 24.501, 33.501, 38.473, 38.331, 36.413

 O-RAN.WG5.C.1-v07.00

Inter RAT Handover to LTE message flow is listed below in section Handoff Type.

Tcl Parameter : HandoffProtocol

Available when Test Activity = Inter Technology Mobility.

When Handoff protocol = LTE, the S1-MME becomes available for input. EPS Pane is enabled. Inter RAT Handover to LTE procedure,

Options : Handover, REG/TAU

3GPP 23.501, 23.502, 38.413, 24.501, 33.501, 38.473, 38.331, 36.413

 O-RAN.WG5.C.1-v07.00

Inter RAT Handover to LTE message flow:

Figure 6.8.1.1-1: Inter RAT Handover to LTE message flow (O-RAN.WG5.C.1-v 07.00)

5GS to EPS handover using N26 interface (23.502)

Tcl Parameter : HandoffType

Select for AMF/SMF Node Emulation within gNB CU SA Nodal.

SUT UPF , SMF N4 Node , SMF N4 GTP Node become available for configuration.

Interface CN NAS-5G includes 2 sub-tabs: Nas 5G Sm (SM) and Nas 5G Mm (MM). 

Interface N2 includes 2 sub-tabs : (NGAP) and (SCTP)

Interface N4 (PFCP (UPF and SMF) and N4 IPSec

Tcl Parameter: AmfSmfNodeEmulationEn

Select for UPF emulation within gNB CU SA Nodal.

The N4 (PFCP ) and N6 (N6 Data Traffic) interfaces become available as well as UPF N3 Node, ,UPF N4 Node and UPF N4 GTP Node.

Tcl Parameter: UpfNodeEmulationEn

Select for PGW-C Emulation. The S2a/S2b/S5/S8 (GTPv2) interface becomes available for input. Enter the EPS Dedicated Bearers per Default.

Requires AMF/SMF Node Emulation.

Tcl Parameter: PgwCEmulationEn

PGW-U Emulation checkbox was added to gNB CU SA Nodal for 5G/4G mobility scenarios. Select PGW-U Emulation for UPF Node to internally allocate additional map space to accommodate multiple TEIDs (4G Uplink) per PFCP Session. 

Only available for selection when UPF Node Emulation is enabled.

Tcl Parameter: PgwUEmulationEn

Select for N26 Interface - Requires AMF/SMF Node Emulation.

Additional details here - N26 Interface

Select for Emergency Alert - Requires AMF/SMF Node Emulation.

Additional details here - Emergeny Alert

Select for N4 IPSec - Requires AMF/SMF Node Emulation or UPF Node Emulation. Disabled for both together.

Disabled for N26 Interface with PGW-C Emulation.

Additional details here - N4 IPSec

Selecting Slg provides the Slg interface tab in LCS Node/Nodal test cases for EPC location services between GMLC and MME.

Tcl Parameter : SlgEn

Selecting Slh provides the Slh interface tab in LCS Node/Nodal test case for GMLC to request routing information from the HSS/HLR.

Tcl Parameter : SlhEn

Selecting Sls provides the Sls interface tab in LCS Node/Nodal and MME Node/Nodal test cases for MME to request location information from the e-SMLC.

Tcl Parameter : SLsgEn

Selecting E2 provides the E2 interface tab in LCS Node and PSAP Node test cases. LCS Node test case can be used to emulate a GMLC instance and an E2 interface for interacting with an external PSAP. Per reference docs : NENA-05-001 December 2003 (NENA Standard for the Implementation of the Wireless Emergency Service Protocol E2 Interface) and J-STD-036-A - Enhanced Wireless 9-1-1 Phase 2

Tcl Parameter : E2En

The parameter is available when GTP Version > 0 (on the GTP tab) and Number of Secondary PDP Contexts is > 0 (on the Mobile Subscriber pane).

Type:  True/False

Default: False

Tcl Parameter: NetReqSecPdpActEn

During GGSN Node testing, when you select Initiate Delete PDP Context the GGSN sends a Delete PDP Context Request to the SGSN, triggering the SGSN to release the context and tear down its tunnel with the GGSN. Upon completion, the SGSN replies with a Delete PDP Context Accept, allowing the GGSN to tear down its tunnel with the SGSN.

The Delete Timer(s) is available when you select Initiate Delete PDP Context.  The value set in this field determines how long a successful PDP session will be active before the Delete PDP Context Request is sent.

In GPRS testing, select the APN DNS Lookup checkbox to allow SGSNs to make a DNS query for the APN name to determine the GGSN address and forward the PDP contexts create request accordingly.

When you select the APN DNS Lookup checkbox, the APN DNS Lookup parameters on the Network Devices tab becomes available.

During GGSN Node testing, selecting L2TP VPN configuration makes the Security Gateway responsible for assigning IP addresses to PDP contexts.

Use QOS Updates to change a context's address or its QOS profile with GGSN-initiated PDP context updates when you select  QOS Updates. Define update frequency and content on the QOS Update tab. 

Select  either PS Domain or CS Domain (Voice over Iuh) or PS & CS Domain

PS  Domain (Iuh interface - SM/GMM Tabs become available)

CS Domain (Iuh interface - MM/CC Tabs become available, Rtpvoice used to emulate voice traffic)

PS & CS Domain (Iuh interface - SM/GMM and MM/CC Tabs become available, Rtpvoice used to emulate voice traffic)

By default, secondary PDP contexts are automatically activated after the associated primary context is activated. When the test includes secondary contexts, you can clear the Auto-Start Secondary Contexts checkbox and trigger activation of secondary contexts from within a DMF with event controls. Three default DMFs that trigger secondary context activation are provided in the Basic Library:

• RTSP TCP Dynamically Start Secondary Contexts

• RTSP UDP Dynamically Start Secondary Contexts

• SIP TCP Dynamically Start Secondary Contexts

When you select the checkbox (default setting), the test will attempt to activate the number of PDP contexts defined on the Mobile Subscribers pane after an MN successfully attaches to the SGSN SUT. When you clear the checkbox, the test will only perform attaches and detaches with the SGSN.

Select Initial Network from the dropdown list. This option is available only when you select "Inter Macro-HNB Mobility".

Options: HNB, Macro (default)

Tcl Parameter: InitiateType

In HNB testing, select the HNB GW DNS Lookup checkbox to allow SGSNs to make a DNS query for the DNS name to determine the GGSN address and forward the PDP contexts create request accordingly.

When you select the HNB GW DNS Lookup checkbox, the HNB GW DNS Lookup parameters on the Network Devices tab becomes available.  

You can use the HNB IPSec checkbox to encrypt control plane traffic between the UE/HNB and HNB GW.

The Target HNB IPSec checkbox becomes available when the Test Activity is Session Loading With Mobility or Intra-HNB GW Mobility.

Available when Test Activity = Capacity. Enables the Iu-PS (PS Domain), Iu-CS (CS Domain) or both (PS & CS Domain) interfaces.

Support for HHO, connected mode, Intra HNB-GW mobility per 3GPP TS 25.467 (release 9)

Tcl Parameter: MacroRncEmulationEn

The Perform LAU After Handoff becomes available when the Test Activity is Session Loading With Mobility or Intra-HNB GW Mobility and CS Domain is selected.

Tcl Parameter: MobLauEn

Enter TAU Delay (ms) - Default = 1000

Tcl Parameter: MobLauDelay

Relocation Type becomes available when the Test Activity is Session Loading With Mobility or Intra-HNB GW Mobility on HNB GW Nodal TC.

Also available on MSC Node and SGSN Node Test cases.

If UE Involved is selected, the Target Cell Id will be available in the id-RelocationPreparation RANAP Message.

Options: UE Not Involved or UE Involved (default)

Tcl Parameter: RelocationType

CN Involved becomes available when the Test Activity is Session Loading With Mobility or Intra-HNB GW Mobility.

Support for mobility with CN involved. Support for Intra-HNB in SSGN and MSC Emulator configurations.

Tcl Parameter: CnInvolvedEn

Initial Network

Select the Initial Network from the dropdown list. This option is available only when you select the Inter Technology Mobility as the Test Activity.

Options: CDMA, LTE

Default: CDMA

Tcl parameter: InitiateType

If you do not select SGW Node Emulation, you would need to add the SGW Node test case, which provides a way to interface/communicate with the HSGW Node via the Use IMSI as NAI User and Use APN as NAI Domain parameters (in SGW Node test case).

Optimized Handoff

• Target SGW S103 Node between HSGW SUT and SGW Node
• ePCF S101 Node between UE (ePCF Node) and MME SUT (Target MME S101)

Partial Context Handoff

Available (if you system is licensed for LTE) when the Test Activity is Inter Technology Mobility or Session Loading with Mobility and the Mobility Type is Inter Technology.

Tcl Parameter: PartialContextHandoffEn

Partial Context Handoff specifies that when the UE returns to HSGW to resume the existing session, the PDN connections are created only per the existing context UE has on network. Similarly, bearers are established to match those that were available on the network. (Since the HSGW has partial context for the UE, it reduces the delay before the UE can send and receive packets.)

UE Context Maintenance timer

In HSGW Node test case, The UE Context Maintenance Timer (s) is available accessible only when you select Mobility Support as Inter-Technology.

• The HSGW uses the UE Context Maintenance timer to track and maintain the UE partial context.
• The value of the timer indicates the maximum number of consecutive seconds that a partial UE session context (which includes the LCP, CCP, authentication and A10 session context for a given UE) is maintained by the HSGW.
• The value 0 indicates that the UE Context Maintenance timer is not used and consequently the UE partial context is not maintained.

UE Initiates Dedicated Bearers

Available when Test Activity is Inter Technology Mobility and when Aux Srv Instances per Subscriber is > 0. The TFT Settings are only also enabled when Aux Srv Instances per Subscriber is > 0.

Vendor variant

Available when Test Activity is Inter Technology Mobility and Mobility is Inter-Technology in Nodal and Node test cases. Default value is None.

Handoff Mode

The Handoff Mode is available only when you select the Inter-HSGW as the Test Activity.

Select the handoff mode With Context Transfer or Without Context Transfer (default). Selecting the With Context Transfer radio button allows you to enter the UE Aquisition Time.

Tcl Parameter: UeAcqTime

LMA Node Emulation

Select LMA Node Emulation for control node availability (S2a interface). The Home Address Type and Bearer IP Address Pool on the Mobile Subscribers pane are available only when you select LMA Node Emulation. LMA Node also become available for configuration.

PMIPv6 Transport

Use the checkbox to enable IPSec encapsulation between the SGW/MAG/HSGW and LMA. Define the IPSec settings on the PMIPv6 IPSec tab.

Auto-Start Auxiliary Sessions

Available when Test Activity is Inter Technology Mobility and Optimized Handoff is selected (LMA Node Emulation is not selected). Select to indicate Data Forwarding is supported during Optimized Handoff from LTE to eHRPD.

Available when Test Activity is Inter Technology Mobility and Optimized Handoff is selected (LMA Node Emulation is not selected). Select to indicate Handoff In Idle Mode is supported during Optimized Handoff from LTE to eHRPD.

Select Affinity Mode to turn on performance improvement of Diameter Applications.

Significant performance impact can be achieved with Affinity Mode, especially, when running multiple test cases on the same process. A higher activation rate/throughput can be expected. 5 test cases are optimum as all cores will be used per one process on the C100 S2. Other systems may have a different number of cores per process and the recommended number of test cases should be adjusted accordingly.

Use to specify a release version of 3GPP specification which HSS Nodal uses for constructing or interpreting messages.

Select the required LTE Spec Version from the dropdown list.

Options: 8.10.0, 9.2.0, 10.6.0, 11.4.0, 12.10.0, 12.X.0

Tcl Parameter: LteVersion

Available when Test Activity = Mobility. Support for handover scenarios: HSS-MME/SGSN/IF.

S6a -> S6a, S6d -> S6d, Gr -> Gr, S6a -> Gr, S6a -> S6d. Mobility is not supported between S6d and Gr.

Other interfaces are disabled , except S6a, S6d and Gr, when Mobility is selected.

Options: S6a, S6d, Gr

Tcl Parameter: MobHssClnInterface

Authentication After Handoff

Tcl Parameter: AuthAfterHoEn

Select Affinity Mode to turn on performance improvement of Diameter Applications.

Significant performance impact can be achieved with Affinity Mode, especially, when running multiple test cases on the same process. A higher activation rate/throughput can be expected. 5 test cases are optimum as all cores will be used per one process on the C100 S2. Other systems may have a different number of cores per process and the recommended number of test cases should be adjusted accordingly.

Selecting S6a provides the S6a interface tab in HSS Node test case for authenticating/authorizing user access to the evolved system (AAA interface) between MME and HSS.

Tcl Parameter: HssSrvS6aEn

The main applicable reference specs are:

3GPP TS 29.338 (14.1.0) – this defines the Diameter based interfaces specific to SMS when used with SMS in MME architecture. This includes the S6c, SGd, and Gdd interfaces. The Gdd interface is not applicable. 3GPP TS 29.272 (15.6.0) defines the S6a interface.

Tcl Parameter: HssSrvS6cEn

Selecting S6d provides the S6d interface tab in HSS Node test case for authenticating/authorizing user access to the evolved system (AAA interface) between SGSN and HSS.

Tcl Parameter: HssSrvS6dEn

Selecting the Gr radio button provides the Gr interface tab in HSS Node test case to test communication between SGSN and HSS.

Tcl Parameter: HssSrvGrEn

Selecting the SWx radio button provides SWx interface between 3GPP AAA Server and HSS Node is used for transport of authentication, subscription and PDN connection related data.  

Tcl Parameter: HssSrvSwxEn

Select to configure S13 interface, EIR database/HSS for transfer of subscription and authentication data between MME and HSS.

Tcl Parameter: EirSrvMmeEn

Select to configure S13' interface between SGSN and EIR database/HSS for transfer of subscription and authentication data between SGSN and HSS.

Tcl Parameter: EirSrvSgsnEn

Select to configure the CBC interface used for Public Warning message delivery.

Tcl Parameter: CbcSrvEn

Select to configure the Cx interface between the CSCF (Call Session Control function) and the HSS. User Profile tab can be enabled via Cx interface. Available when LTE Spec Version > = 11.4.0

Cx Interface is also available on IMS Node test case.

Tcl Parameter: HssSrvCxEn

Select to configure the Sh interface between the Application Server (AS) and the HSS. Sh interface is used for storing, retrieving and modifying user data. User profile can be enabled via Sh interface. Available when LTE Spec Version > = 11.4.0

Tcl Parameter: HssSrvShEn

S6t

Select to configure the S6t interface used between the HSS and SCEF (Services Capability Exposure Function).  LTE Spec Version = 13.4.0 or 15.X.0. Added inter-working with S6a in release 17.4, LTE Spec Version must be > or = 15.X.0 for both S6a and S6t checkboxes to become available for interoperability testing. Command Mode is not available with S6t interface. Must enter at least one MSISDN or an External Identifier when S6t Interface is enabled.

Tcl Parameter: HssSrvS6tEn

Select to configure the Wx interface used between the HSS and 3GPP AAA. Available when LTE Spec Version = 11.2.0

Tcl Parameter: HssSrvWxEn

Select to configure the SLh interface used between HSS and GMLC.

Tcl Parameter: HssSrvSlhEn

Available when  LTE Spec Version > = 11.4.0 and <= 12.X.0.

The purpose of Zh interface is to perform the retrieval of an authentication vector and possibly GBA User Security Setting (GUSS ) from the HSS.  The reference point Zh used between the BSF and the HSS allows the BSF (Boot Strapping Function) to fetch the required authentication information and all GBA user security settings (GUSS) from the HSS. The reference point Zh is an intra-operator domain interface.

Zh interface will be introduced on top of existing diameter based implementation of IMS Cx interface as depicted in Figure 1 below.

Tcl Parameter: HssSrvZhEn

Emulate UDM (Nudm)

NRF Interface

• N8 to AMF
• N10 to SMF
• N13 to AuSF

Select to emulate UDM (Nudm)- Unified Data Management Function. Interface Nudm (Nudm NF Tab - NF Producer) becomes available for input. UDM SBI Node is available for input. Starting SUPI, Starting GPSI, IMEI, Software Version

Reference is 3GPP TS 23.632 V16.1.0

Architecture:                                                                                      Architecture for Direct UDM-HSS interworking in reference point representation:

Supported Procedure:

Authentication (reference section 5.2/3GPP TS 23.632 V16.1.0)

1. authentication request coming to the UDM (from AusF) indicating that the authentication vectors needs to be generated at the HSS 
2. authentication request coming to the HSS (MME)  indicating that the authentication vectors needs to be generated at the UDM

5GC-EPC Mobility (reference section 5.3/3GPP TS 23.632 V16.1.0) **

As defined in 3GPP TS 23.501 [2], when interworking procedures with N26 are used, the UE operates in single-registration mode. For the 3GPP access, either the AMF or the MME is registered in the HSS+UDM.

1. Mobility from 5GC to EPC, with N26  ( *(reference section 5.3.2/3GPP TS 23.632 V16.1.0)* 

Figure 5.3.2-1 shows the interaction between the HSS and UDM in an interworking scenario with N26, when the UE attaches to the EPC. 

Supported Procedure:

• [1] The HSS receives an S6a ULR request containing the IMSI of the subscriber.
• [2] The HSS responds to the MME with an S6a-ULA.
• [5] UDM cancels the user registration in 5GC by sending a Nudm_UECM_DeregistrationNotification to the AMF.

Procedure [3] and [4] are not require since Landslide emulates both UDM & HSS on HSS Node.

2. Mobility from EPC to 5GC, with N26  (reference section 5.3.3/3GPP TS 23.632 V16.1.0) 

Figure 5.3.3-1 shows the interaction between the UDM and the HSS in an interworking scenario with N26, when the UE attaches to the 5GC. 

Supported Procedure:

• [1] The UDM receives a Nudm_UECM_Registration request for 3GPP access containing the SUPI of the subscriber.
• [2] The UDM responds to the AMF with a Nudm_UECM_Registration Response.
• [3] MME sending a CLR via the S6a interface.

When NRF Interface is enabled on HSS Node, the UDM Registration to NRF procedure is performed once HSS is started . Per 3GPP TS 29.510, Section 5.2.2.2.2 (Figure 5.2.2.2.2-1 NF Instance Registration). In addition, NF Heart-Beat (Figure 5.2.2.3.2-1 NF Heart-Beat) is performed periodically after successful registration. Procedure NF Instance Deregistration ((Figure 5.2.2.4.1-1 NF Instance Deregistration) is performed during de-registration.

When NRF Interface is enabled on HSS Node, Interface Nnrf Client (NF Consumer) , SUT NRF SBI (Network Devices) and NRF SBI Node become available for input.

Use to specify a release version of 3GPP specification which HSS Node uses for constructing or interpreting messages.

Select the required LTE Spec Version from the dropdown list.

Options: 8.4.0, 8.10.0, 9.2.0, 10.6.0, 11.2.0, 11.4.0, 12.10.0, 12.X.0, 13.4.0 (S6t interface only), 15.X.0 (S6a Interface only), 16.1.0

Tcl Parameter: LteVersion

See HSS Node Command Mode test case.

Command Mode option is not available when you select only SWx interface as the IDR and DSR commands are not applicable to the SWx interface command set.

Test Activity

Select Capacity Test, Session Loading Test or Inter Technology Mobility.

Handoff Protocol

Available when Test Activity = Inter Technology Mobility. Select for E-SRVCC (Single Radio Voice Call Continuity) procedure.

New Tabs, ISC-PS and ISC-CS, are enabled for Signaling flows. AS, AS Port and AS Host become available in Network Devices as well as S-CSCF Node and ATGW Node.

The Inter-Technology Mobility Settings dialog supports "Single Handoff" only:

See Flow - Boxes with Black text is depicting PS Subscriber, Boxes with Green text is depicting the paired CS Subscriber:

Reference documents:

• 3rd party registration (Call flows defined in 3GPP 24.237 A.3.3)
• Session Origination with PS to CS SRVCC enhancements (Call flows defined in 3GPP 24.237 A.4.2)
• eSRVCC procedure (Call flows defined in 3GPP 24.237 A.18.3)
• IP Multimedia Subsystem (IMS) Service Continuity Stage 3 - TS 24.235 V15.0

This is a licensed feature.

Option = E-SRVCC

Tcl Parameter: HandoffProtocol

Core Network   

PS Domain     Mw    ISC    Mx   Ml   Generic

CS Domain     Nc

Select to either PS (Packet Switched) or CS (Circuit Switched) domain.

• PS Domain : Enables the Mw Interface (P-CSCF Testing), ISC (S-CSCF Testing), Mx Interface (CSCF/BGCF and IBCF Testing), Ml (E-CSCF and GMLC Testing) or Generic (Generic IMS interface). Enter Generic Interface Name (see additional details below)
• CS Domain : Enables the Nc Interface.

Tcl Parameter: MsNetwork

Generic Interface Name

Available when PS Domain Generic Interface is enabled. In IMS Nodal test case, the Generic interface allows you to configure testing of an IMS Interface. Enter the Generic Interface Name.

The Generic Interface name (If Test1 is used) will be populated on the Test Node Tab (GEN-Test1 Node), the RTP Traffic tab ( GEN-Test1 RTP Traffic), and the SIP OM tabs (e.g. GEN-Test1|Main, GEN-Test1|1xx, etc).

Enter up to 8 letters, number or '_'. The first character must be a letter.

Configure:  

• GEN- (Generic Interface Name) Node -

• GEN- (Generic Interface Name) RTP Traffic (use for different IP for RTP Traffic)

• GEN SUT

• GEN (Generic Interface Name) Tab - Use Paste Buffers to Edit SIP script buffers used in SIP Action message headers and SDP bodies

• SIP VoIP Tab (with limited input fields) become available for input. Enable Supplementary and Enable Call setup are auto enabled and cannot be disabled.

The Generic Interface can used to emulate Mg and Mj interfaces for X-CSCF testing.

Mj interface uses SIP over UDP or TCP , BGCF to MGCF or MGCF to BGCF per 3GPP 23.002, 23.228, 24.229, 29.163.

Mg interface uses SIP over UDP, MGCF to I-CSCF per 3GPP 23.002, 23.228, 24.229.

Tcl Parameter: GenericName

Test Activity

Indicates the Test Activity performed in IMS Node test case. Command Mode/Sequencer available.

P-CSCF Mode

SIP Endpoint    Proxy      B2BUA

Select to indicate whether IMS Node emulates SIP Endpoints, SIP Proxy or Back-to-Back User Agent (B2BUA).

• SIP Endpoints: Select SIP Endpoints to emulate SIP Registrar and SIP Endpoints used to create or receive SIP messages.
• Proxy: Select Proxy to emulate SIP Proxy to route requests as appropriate.

Selecting Proxy allows you to also select Enable Separate Registrar to receive register requests. Selecting Enable Separate Registrar ensures the REGISTER requests goes to the registrar and INVITE requests will go to proxy.

• B2BUA: Select B2BUA (SCC-AS) to parse the 3rd Party REGISTER message (Enable 3rd Party Registration) and send back 200 OK Message. The SCC-AS is also capable of sending back a SIP MESSAGE (which provides SCC-AS related information) and is also capable of providing a B2BUA call. Currently we support: PS Registration and CS Registration with prior PS Registration, PS Calls through ISC Interface, no CS allowed and PS to CS SRVCC.

Tcl Parameter: ImsMode

Interface Gm   Mw   ISC   Mx  Ml

Select either the Gm, Mw (P-CSCF testing), ISC (S-CSCF/I-CSCF Testing), Mx Interface (CSCF/BGCF and IBCF Testing) or Ml (E-CSCF and GMLC Testing).  Additional information in IMS Nodal/Node Test Case.

Tcl Parameter: ImsInterface

I2 Interface

Select to enable the I2 interface.

Tcl Parameter: ImsNodeI2En

Mw + ISC Interface

Select for I/S-CSCF wraparound testing. Inter working between Mw and ISC interface. Used in conjunction with IMS Nodal when Test Activity = Inter Technology Mobility and Handoff Protocol = E-SRVCC.

Registration and Call in PS domain is between ATCF and I-CSCF. Registration in CS domain is between MSC and I-CSCF.

Access transfer from PS to CS is between ATCF and I-CSCF. I-CSCF will communicate with AS. Send 3rd Party Registration message.

For other messages, IMS Node (Mw+ISC) will forward messages.

ATCF SUT, MSC SUT and AS SUT become available for input.

Tcl Parameter: MwPlusIscEn

Select to enable the Cx interface to add interaction between Cx flows and SIP flows.

Available when Gm Interface, SIP Endpoint or Proxy, Enable Registration, Enable Authentication, Type = IMS AKA are enabled and Command Mode is off.

Cx SUT (HSS) become available for input. P-CSCF Node, I-CSCF HSS I/F, S-CSCF HSS I/F Nodes are available for input.

CX Interface "App" sub-tabs (I-CSCF, S_CSCF) are not available for input because they are retrieved from the SIP flows. 

Tcl Parameter: HssCxEn

H.248 Interface

Available in IMS Node in Proxy mode to support a H.248 interface towards Media Gateway for back to back testing.

Interface H.248 and MGC Node become available for input.

SSC - Subscriber Session Control, SSE - Subscriber Service Edge

Tcl Parameter: H248En

Gm Retained After Handoff

If Gm retention is off then terminate 4G session (Terminate SIP dialogue, and release all resources associated with session). If GM retention is enabled, then the network side release will be accomplished.

Tcl Parameter: GmRetainedEn

Enable Preconditions

Select to indicate support for SIP Preconditions, which ensures network resources are reserved (using pre-defined reservation mechanisms before beginning a session) for a SIP session. See Call Flow Info for additional parameters.

• See also SIP Preconditions for details.

Enable Emergency

Select to allow setting up of Emergency call flow functionality. The Emergency service requires you to define the phone number associated with Public User Identity. Configure Emergency Phone Number to Emergency Service URN Translation table for SIP Endpoints.

Enable Subscription

Enable Registration

• Expires: The length of time for which the IMS registration is valid. When the time specified expires, the IMS should register again.

• Temporary User ID: When checked, the IMSI from the PhoneBook Tab is used for Registration as Temporary User ID. Per 3GPP TS 23.238.

Enable Supplementary

Select to modify the Contact header of SIP response messages. Available in IMS Node. This option is enabled for Gm or Mx in SIP Endpoint mode. Per RFC 3261.

Tcl Parameter: ImsNodeUpdateContactHdrEn

Final Response Delay (ms)

Select to configure a delay (in milliseconds) before sending the final (200 OK) response to SIP INVITE request.

Range = 1 to 65535

Default value = 1 ms

Tcl Parameter: Delay2xxForInvValEn

Tcl Parameter: Delay2xxForInvVal

Rx Interface

Select Rx Interface to define the Rx interface between the PCRF and the IMS Node. See also AF Node.  The Rx Interface is available only when your system is licensed for PCRF function.

IMS APN: Enabled when you select Rx Interface. Select to allow APN information from the user, so that the AAR messages can have CalledStationID AVP to specify the APN to which the IMS belongs.

Default: APN0

Tcl Parameter: ImsApn

N5 Interface (5G)

Select N5 Interface to define the N5 interface between the PCF and an Application Function (the IMS Node).

Also available on Service Based Nodal test case when (Test PCF (Npcf), From SMF (N7) , From AF (N5)) is enabled.

Interface AF-PCF is available for input. See also AF SBI Node.  SUT is PCF SBI.

IMS APN (DDN): Enabled when you select N5 Interface. Enter the DDN.

Default: ims

Tcl Parameter: N5En

Tcl Parameter: ImsApn

Select Start Rx after SDP negotiation for IMS Node to send AAR messages after SDP offer & answer have been exchanged i.e. SDP offer is sent in INVITE message and SDP Answer has been received in 183 message or 200 OK of INVITE.

Available when Mode = Proxy and Rx Interface is enabled.

Tcl Parameter: ImsNodeStartRxAfterSdpNegoEn

Available on IMS Node TC when Mode is "Proxy" and Rx Interface selected. Select for IMS Node to forward the 183 Session Progress/ 200 OK only after AAA response is received from PCRF. 

1. Call Setup progress after AAA is received.

2. Time out waiting on AAA response - The timeout interval (waiting for AAA response) is configured on Rx tab on IMS Node TC Diameter - Retry Time (ms) . 

3. AAA response from PCRF with Result-Code AVP set to error (e.g. 5012). IMS Node will cancel the call if AAA response has error.

Tcl Parameter: ImsNodeCallProgAfterRxRspEn

Enable NetLoc Mode

Enable Late SDP Offer

• IMS Node will not send SDP with the INVITE message
• IMS Node expects to receive SDP offer in 183 message
• IMS Node will respond with SDP answer in the PRACK message

Enable RTP Traffic

Enable MSRP

Select Enable MSRP to configure MSRP within SIP/SDP parameters on Gm | Media | MSRP tab. After you Enable MSRP, select Send Messages on the Gm | Media | MSRP tab to define MSRP options and send messages.

Call Starts After

 Indicates when the call starts.

Options: When All Users Registered (0); When User Registered (1)

Default: When User Registered (1)

SIP Subscriber URI Scheme

SIP Endpoint URI Scheme

Available when IMS Node is Endpoint. Select to indicate support for MSISDN based Public Identities in both Tel-URI (e.g., +972-3-7212345) and SIP-URI ([email protected]) forms:

Options: SIP-URI, tel-URI or SIPS-URI (only when GM TLS  or Mm TLS is installed)

Tcl Parameter: SipSubscriberUriScheme

Tcl Parameter: SipEndpointUriScheme

Application Servers

Communications Diversion - The communications Diversion check box must be checked with the CFU (call forwarding) built-in. When enabled the App Servers Tab is presented for provisioning.

Communications Barring - The communications Barring check box when enabled,  the App Servers Tab is presented for provisioning.

Service Centralization and Continuity - The Service Centralization and Continuity check box is enabled when Interface = Mw or ISC. When enabled,  the App Servers Tab is presented for provisioning. Support for call flow between ATCF and SCC AS.

Communications Waiting - The communications Waiting check box when enabled,  the App Servers Tab is presented for provisioning. Used to provision Call Waiting.

MCPTT - The MCPTT check box when enabled (IMS Mode = Proxy, Enable Supplementary), the App Servers Tab is presented for provisioning. Part of the Mission Critical Push-To-Talk (MCPTT) services.

Conference - The Conference check box when enabled,  the App Servers Tab is presented for Conference Policy provisioning.  Available when Mode = B2BUA and ISC Interface is selected.  

Communications Redirection - The communications redirection check box when enabled, the App Servers Tab is presented for provisioning. This option is enabled for Gm/Mw/ISC in Proxy Mode with Enable Supplementary. Select for IMS Node to provide redirection, i.e. will respond to initial INVITE with a 302 response.

Tcl Parameter: AppExternalType

Tcl Parameter: AppServerEn

Tcl Parameter: AppCommDiversionEn

Tcl Parameter: AppCommBarringEn

Tcl Parameter: AppSccEn

Tcl Parameter: AppCommWaitingEn

Tcl Parameter: AppMcpttEn

Tcl Parameter: AppConferenceEn

Tcl Parameter: AppCommRedirectEn

MS Transport :

• IP/Ethernet
• IP/PPPoE

The MS Transport protocol IP/Ethernet and IP/PPPoE requires you to configure the following:

Select to enable the MSs to obtain IP addresses from a DHCP server and configure the DHCP client parameters.

• Learn more about using DHCP

Selecting the Data Traffic option includes the Data Traffic tab to the L3-7 protocol tab.

• If only Data Traffic option is selected (and not Data IPSec or NAS Emulation), the following options on the Data Traffic tab are disabled: the Traffic Start, Data Start Delay, and Auto Stop Control Layer are all disabled.

• If either Data IPSec or NAS Emulation are selected the Traffic Start, Data Start Delay, and Auto Stop Control Layer settings are enabled.

• When you select Pilot Packets, Data Traffic could be started before or after Pilot Packet session establishment depending on Data Start Delay value you enter on the Pilot Packets tab.

You can emulate a DHCP Relay Agent (as described in RFC 3046) with the DHCP Relay Agent checkbox.

Select DHCP Client to enable the DHCP Relay Agent checkbox. When you select the parameter, the DHCP Relay Agent Node sub-tab is enabled for configuration along with the DHCP Relay Agent parameters on the DHCP interface tab.

In the IP Application Node test case, the MN can communicate directly with a DHCP server, or send requests through an emulated DHCP Relay Agent.

In the IP Application Node test case, data transmission begins when the client nodes are started unless you include Data IPSec. The Auto Stop Control Layer, Data Start Delay, and Traffic Start parameters are only available when IPSec and or NAS Emulation is selected on the Test Configuration tab and are not available when only Data Traffic tab is selected on the Test Configuration tab.

IPSec is always used in the PDG Micro-Mobility test case and cannot be disabled.

If your test system is also licensed for one of the AAA test applications, you can add the functionality of the AAA Server Nodal test case to the IP Application Node test case with the NAS Emulation checkbox. When you check the box, the NAS node sub-tabs are enabled, and the NAS tab is added to the test case. In the Mobile Node sub-tab, an option is available to include the MN's IP address in the Framed-IP-Address attribute.

• Learn more about AAA testing

Not available for Inter-PSDN test activity. Select to test the SIP VOIP feature which supports SIP and RTP-based Voice over in IP Application Node test case. Select either the GM or I2 interface- not both.

You are required to configure the following:

• SIP VOIP
• Phonebook: SIP Subscribers; SIP Endpoints; Server Profile
• Gm Interface: Control: SIP Media: RTP
• I2 Interface : Control: SIP Media: RTP, MSC Node, MGW Node

Not available for Inter-PSDN test activity. Select to indicate generation of Pilot Packets and configure the following events emulated on PCEF (PGW or HA).

• PDN Session Establishment
• PDN Session Teardown
• NAT Port Chunk Allocation
• NAT Port Chunk De-allocation
• Reception of first user IPv4 data packet

Enable to Transfer the MPD to the BM-SC via WebDAV. Use the IP App Node as WebDAV Client. Use Two Tabs - Media and WebDAV Client to enter required data.

Support for Ut Interface.

• Ut interface runs over the XCAP protocol.
• XCAP protocol runs over the HTTP1.1 protocol to modify/fetch the user specific XML data. In the Ut Interface, this data is used to enable/disable or modify supplementary services.  
• Supplementary services are supported over the UT interface between UE and AS.

Tcl Parameter: UtEn

Select to emulate the Dispatch Console (DC) Interface. Select for support of  D Interface between T-CN and DC which is based on SIP.

Tcl Parameter: DcInterfaceEn

Note : DnsEn variable and the DNS checkbox are no longer needed and are being removed in release 21.8. For one release cycle, if the value=true, the value will be maintained in the test case until the user edits and saves the test case. This will allow users to continue to use saved test sessions on older TSs versions. 

Select for a dedicated DMF for DNS testing. If enabled, DMF will be limited to DNS. Available when Data Traffic is enabled and Fireball is not enabled. This is a licensed feature.

See Data Message Flow - dns protocol.

Tcl Parameter: DnsEn

Additional details located in Common section - CSC-4 to Mission Critical CMS.

Additional details located in eMBMS section - MB2.

Additional details located in Common section - WebRTC.

Select for Network Address Port Translation (NAPT) functionality for SIP and RTP traffic. Only available when SIP VOIP GM is enabled.

Network topology : SIP UA <-> EDGE Router SIP's NAPT <-> (SIP over UDP) to SUT.

All SIP traffic will be routed to N (Number of ) NAPT Nodes. Enter Private IP Address for UAs in Client Test Node Parameters - Starting IP . Enter Public IP Address for UAs in NAPT Node (Auto Increase per NAPT Node). Enter Starting Public Port for UAs for each NAPT Node in Starting Global SIP Port Number in NAPT Tab.

SIP's NAPT Functionality:

• Perform NAPT for IPv4 Source Address and UDP Source Port.
• The same global IP Address is used for all SIP UAs behind Edge Router.
• Different global port number is used for SIP for each SIP UA.
• SIP header are intact. No modification to private IP address and Port number (No SIP ALG)

The following table show example of how UA will be mapped with the following settings:

• 8 UEs,
  • 1 subscriber per UE
  • Signaling Port: 5060 (non-increase)
• 2 NAPT Nodes
  • Starting Global IP: 10.10.40.1
  • Starting Global SIP Port: 3200

The following table show example of how UA will be mapped with the following settings:

• 4 UEs,
  • 2 subscriber per UE
  • Signaling Port: 5060 (auto-increase, #(N5060))
• 2 NAPT Nodes
  • Starting Global IP: 10.10.40.1
  • Starting Global SIP Port: 3200

Tcl Parameter: NaptEn

Only available when SIP VOIP GM and NAPT are enabled in IP Application Node and IMS node (for back to back testing).

Reference : https://tools.ietf.org/html/rfc3525

SIP UA + SSE will be emulated by IP App Node. Interface H.248 becomes available for input. The H.248 tab is used to define the H.248 / Megaco stack (RadVision).

SSC - Subscriber Session Control, SSE - Subscriber Service Edge

The SUT is MGC SUT. The Node is MG Mgmt Node.

Tcl Parameter: H248En

Select the Iq Interface - 3GPP Reference Point between IMS-ALG and IMS-AGW. The Interface is fully described in 3GPP TS 29.334, and it is an edition of H.248 (MEGACO) protocol suited for IMS infrastructure. 

IMS-ALG or ATCF simulates MEGACO MGC functionality; while IMS-AGW or ATGW functions as MEGACO MGW. IMS-ALG controls over IMS-AGW, and IMS-AGW provides media path with NAT/NAPT capability in the middle.

The example shown below provides a flowchart for VoLTE to VoLTE call. It shows media and signaling path and Gm and Iq interaction and to show NAPT in-action.

Interface Iq with Tab H.248 over UDP become available for input. The H.248 tab is used to define the H.248 / Megaco stack (RadVision).

The SUT is MGC SUT. The Node is MG Mgmt Node and IMS-AGW Node.

Tcl Parameter: IqEn

Use the checkbox to simulate a CN that supports return routability and MN-CN bindings (selected), or simulate a CN that is not Mobile IPv6 compliant (cleared). When Route Optimization is enabled and successful, the CN sends packets directly to MS addresses; otherwise, the CN sends packets to MS home addresses.

The Mobile IPv4 HA Nodal test case tests a standalone HA that you can define with the HA SUT drop-down list. Alternatively, you can enable dynamic Home Agent address resolution with the Enable Dynamic Home Agent checkbox. When this option is used, the Home Agent address in the initial RRQ is set to 0.0.0.0.

The Mobile IPV4 FA Nodal test case tests a standalone FA that you can define with the FA SUT drop-down list. Select the Agent Discovery check box to enable the ICMP agent discovery messages to be exchanged between the MN and FA.

The CDMA/WiFi Convergence test case can be used in a nodal configuration to test a PDIF-FA and emulate an HA or in an end-to-end configuration to test a PDIF FA and up to two HAs.

In the nodal configuration, you can include MIP IPSec to encrypt control plane traffic between the PDIF-FA and the HA node. Define the IKE settings on the MIP IPSec tab.

You can configure the test case for end-to-end testing by selecting the System Under Test radio button in the Home Agent pane. You can include a Secondary Home Agent in the test or enable Dynamic HA address resolution with the applicable checkboxes.

Select to enable Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) [RFC 4951]. The Alternate LNS Node is enabled and available for configuration when you select Enable L2TP Failover.

In the LNS Node test case, you define the number of PPP sessions and L2TP tunnels that the node will support, the rates at which sessions are connected and disconnected, the server emulator, and Data Traffic options. See also LNS Node testing on the Network Devices tab.

If your system is licensed for the L2TP Secure Network Server feature and you have defined an LAC SUT, you can use the L2TP IPSec checkbox to enable IPSec support for L2TP control plane traffic. Define the IPSec settings on the L2TP IPSec tab.

Select the Data Traffic option allows LACs to forward data traffic to the LNS node, you can add Network Host functionality to the node and include DMFs that will respond to the incoming traffic. Refer to Network Host for definitions of the settings supported by the LNS node.

During MME Nodal testing, select the Initial Network from the dropdown list. This option is available only when you select the Inter Technology Mobility as the Test Activity.

Initial Network indicates where the UE will initially attach / register. 

Select the Handoff Protocol below to indicate the "Target" network.

For example: Initial Network = LTE , Handoff Protocol = UMTS (which is the Target). The UEs will initially attach / register to LTS then handoff to UMTS. 

The F2 Help key has been enhanced to indicate which network is the Target.

Options: LTE, UMTS, GPRS, eHRPD, 1xRTT, WiFi

(one of the Target Handoff Protocol options listed below)

Default: LTE

In MME Nodal TC, Inter-Tech Mobility, Gn Interface to MME with /SGWPGW Node Emulation enabled should allow Initial Network = LTE only

In MME Nodal testing, the Handoff Protocol is available when Test Activity is Inter Technology Mobility, Command Mode, and Sequencer.

Tcl Parameter: HandoffProtocol

Options: UMTS (IuPS over IP, IuCS & IuPS over IP (Only available when Test Activity is Inter Technology Mobility), IuCS over IP (Not available when Test Activity is Inter Tech Mobility)) : iups_ip; iucs_ip;iucs_iups_ip

GPRS : gprs;

eHRPD : ehrpd;

1XRTT : 1xrtt

WiFi : wifi

Parameter Class: Basic: Custom Multiple Choice Values:

NAME: VALUE

Parameter Class: Basic: Boolean, T/F Values: true / false

• For UMTS/UMTS (IuPS over IP), GPRS see UMTS Protocol Options.

• For UMTS/UMTS (IuCS over IP), use Target Iu-CS Tab to define interface. Must enable Circuit Switched Fallback CSFB when Test Activity = Inter Technology Mobility and Handoff Protocol = UMTS (IuCS over IP).

• For UMTS (IuCS & IuPS over IP) use Target Iu-PS and Target Iu-CS to define interfaces. When selected,  VoLTE and SRVCC are automatically enabled.

• Dual Stack Network Host option is available when Test Activity is Inter Technology Mobility, Command Mode, and Sequencer with UMTS and GPRS. In addition, all three Home Address Type options, IPv6, IPv4, and Both are available on the Mobile subscriber pane.

• When the Handoff Protocol is eHRPD, S2a interface testing uses IPSec protocols and an Ethernet physical layer. Use the PMIPv6 to define the interface. In addition, the following applies when eHRPD is the handoff protocol:

• UMTS Version is not available and the Initial Network is LTE.  

• The Optimized Handoff checkbox is available.

• The SGW/PGW Node Emulation and Gn Interface to MME checkbox are not available.

• When Handoff Protocol is None, Gn Interface to MME and S3 Interface to MME options are not available for selection.

• When Handoff Protocol is 1xRTT, Circuit Switched Fallback is automatically selected to support CS fallback to 1xRTT. Configure S102 tab parameters,  1xCS IWS Node and MME S102 SUT. See also CS Fallback to 1xRTT.

• When Handoff Protocol is WiFi, AP/SSID, AAA and SWu IPSec interfaces become available. Wifi Offload Node Emulation and ePDG Node Emulation must be disabled for Command Mode/Sequencer with Handoff Protocol is Wifi.

• Initial Network is LTE.

• AP Tunnel Type = NONE

• WiFi Subscribers (on Mobile Subscribers section becomes available for input) 

In MME Nodal testing, depending on the type of Handover test activity, the Handoff dropdown list displays different options.

• Test Activity is Inter-technology mobility: the Handoff Type drop-down list is available for UMTS Version 7 and 8. The Options are Handover and TAU/RAU.
• Test Activity is Intra-MME:  the Handoff Type drop-down list options are  X2, TAU/RAU and CP-CIoT-CpRelocation (available when CP-CIoT EPS Optimization Supported is enabled).
• Test Activity is Inter-MME: the Handoff Type drop-down list options are  S1  and TAU/RAU.

In AMF Nodal (5G) testing, the type of Handover test activity supported:

• Test Activity is Intra-AMF Mobility: the Handoff Type drop-down list options are  Xn, N2, Mobility Registration Update
• Test Activity is Inter-AMF Mobility: the Handoff Type drop-down list options are  N2, Mobility Registration Update
• Test Activity is Inter Technology Mobility : Handover , REG/TAU (Inter Technology Mobility)
• Test Activity is Dual Connectivity : RAN Initiated QoS Flow Mobility

In SMF Nodal (5G) testing, the type of Handover test activity supported:

• Test Activity is Intra-AMF Mobility: the Handoff Type drop-down list options are Xn, N2
• Test Activity is Inter-AMF Mobility: the Handoff Type drop-down list options are Mobility Registration Update, N2
• Test Activity is Inter Technology Mobility: the Handoff Type drop-down list options are Handover, REG/TAU

In UPF Nodal (5G) testing, the type of Handover test activity supported:

• Test Activity is Mobility: the Handoff Type drop-down list options are  Xn

Tcl Parameter: HandoffType

Available when Sv Interface or SRVCC are enabled - Follow link for further details.

Selecting the checkbox allows Tracking Area Update to be performed when connected.

Tcl Parameter: PeriodicTauUpdateEn

Selecting the checkbox allows Tracking Area Update to be performed immediately after the handover and enter TAU Delay in micro seconds to indicate the time before performing Tracking Area Update.

Tcl Parameter: MobTauEn

Tcl Parameter: MobTauDelay

Use the drop-down list to select the UMTS version that will be used in the test.

Options:  7 or 8

Default: 7

Tcl Parameter: UmtsVersion

In MME and gNB CU NSA testing the dedicated bearers can be established by either the UE or the PDN. Selecting the UE Initiates Dedicated Bearers, allows all the provisioned bearers be established by the UE. If not selected, the PDN will establish the dedicated bearers as needed based on the traffic activity and QOS.

• In MME Nodal and gNB CU NSA Nodal test cases, the UE Initiates Dedicated Bearers is available only when Dedicated Bearer per Default is > 1.
• In MME Node test case, UE Initiates Dedicated Bearers is independent of the value of Dedicated Bearer per Default or any other selection.

Tcl Parameter: UeInitBearerEn

In MME Node test case, Use Bearer Parameters From UE is available when you select  UE Initiates Dedicated Bearers.

Select to allow the UE Initiated Dedicated Bearers to either use the UE provided QoS value or use the Bearer parameters you configure (on Landslide).

The values defined applies only to UE initiated dedicated bearers and  not network initiated bearers.

Tcl Parameter: UetBearerParamsEn

You can use the S1-MME IPSec checkbox to encapsulate control plane traffic between the eNodeB and MME.

The Target S1-MME IPSec checkbox is available when Test Activity is Session Loading with Mobility, Inter-MME, and Intra-MME.

In MME Nodal testing, the S1-MME IPSec is automatically disable if any of the Multiple MME parameters are selected on the Network Devices tab.

Tcl Parameter: EnbMmeIpsecEn

In MME Nodal testing, select the S1-U IPSec option to encapsulate traffic between the eNodeB (User Plane) and the Serving Gateway (User Plane).

In HSGW Nodal testing, the S1-U IPSec option is available when Test Activity is Inter Technology Mobility. You can use the S1-U IPSec checkbox to encrypt traffic between the eNodeB and the Serving Gateway.

In gNB CU NSA Nodal testing, S1-U IPSec is not available when S1-MMS NAS (Dual Connectivity - Option)= 3a or 3x.

The Target S1-U IPSec checkbox is available when Test Activity is Session Loading with Mobility, Inter-MME, Intra-MME, Command Mode, and Sequencer.

Tcl Parameter: EnbSgwIpsecEn

In MME Nodal testing and gNB CU NSA Nodal, you can now select a single tunnel to carry both  S1-IPSec control traffic and S1-U IPSec user traffic.

Tcl Parameter: EnbIpsecEn

In MME Nodal testing, when Test Activity is Intra-MME Mobility and the X2 Interface is selected, the S1-IPSEC checkbox is enabled and renamed to S1/X2 IPSec.

In MME Nodal testing, select the S1-IPSec option to encapsulate traffic between the eNodeB and MME, or between eNodeB (User Plane ) and the Serving Gateway (User Plane) per eNodeB. Configure parameters on S1-IPSec | S1-IPSec tab.

Also, when you select S1-IPSec, a separate Security Gateway (Network Devices | eNodeB Security Node) terminates the tunnel.

The Target S1-IPSec checkbox is available when Test Activity is Session Loading with Mobility, Inter-MME, Intra-MME, Command Mode, and Sequencer. Configure parameters on Target S1-IPSec | Target S1-IPSec tab.

Target S1-IPSec is mutually exclusive with Target S1-MME IPSec and/or Target S1-U IPSec.

Select the Control Plane SMS (Short Message Service) checkbox to enable, the device (mobile stations) to send or receive SMS messages (mobile originated or mobile terminated) selected in the SMS tab.

Since this is a licensed feature, the SMS tab will be visible only if your system is licensed for SMS.

The Control Plane SMS (Short Message Service) checkbox on the MME Nodal Test Configuration tab is not available under the following circumstances :

• Test Activity is Inter-Technology Mobility
• Test Activity is Session Loading With Mobility and the Mobility Type is Inter Technology
• Command Mode and Sequencer with Handoff Protocol = 1xRTT.
• ePDG Node emulation is enabled
• X2 Interface is enabled
• WiFi Handoff Type is selected.

The Control Plane SMS  (Short Message Service) checkbox on the MME Node Emulator Configuration tab is not available under the following circumstances :

• If SGs Interface or Sv Interface or SRVCC are enabled

SMSo5G

The SMS Over 5G NAS feature provides support for sending and receiving SMS messages using 5G NAS signaling. The SMS messages are carried in 5G UL NAS Transport (UE to network) and DL NAS Transport (network to UE) messages with a payload container type of SMS. SMS is handled in the MM layer for 5G. SMS Over 5G is supported in 5G NAS version 15.2 and later.

During registration the UE indicates it is requesting SMS over NAS by including the 5GS Update Type information element in the Registration Request message. If the AMF supports SMS Over 5G NAS, it will set the SMS Allowed indicator in the 5GS Registration Result information element in the response it sends.

In the AMF Nodal test case the subscriber can originate MO SMS messages and receive MT SMS messages. Appropriate lower layer signaling (e.g. CP-Data, CP-Ack, RP-Data, etc) is performed as part of the SMS Over 5G NAS procedures. The AMF Node acts as a service center with respect to SMS messaging, it receives MO originated SMS messages and generates proper responses (CP, RP, and SMS reports if requested).  The AMF Node can generate MT messages towards a subscriber.  MO SMS messages terminate within the AMF Node, they are not forwarded to an SMSF. MT SMS messages originate within the AMF Node, they are not received from an SMSF.

The Landslide AMF Node currently does not support interworking with an SMSF.

SMS Over 5G is supported for the following types of Test Activity:  Capacity, Session Loading, Inter Technology Mobility, and Intra-AMF Mobility.

References : TS 23.040 – SMS , TS 24.501 – 5G NAS

Tcl Parameter: ShortMsgSvcEn

Available in MME Nodal when Control Plane SMS (Short Message Service) or Enable SMS-over-IP (on VoLTE) is enabled.

Select for MMS Load testing. The MMS Tab becomes available for input. 

Tcl Parameter: MmsDataEn

Select the SGW/PGW Node Emulation checkbox to enable the SGW GTP Node and PDN GW Node to emulate  Serving Gateway. As of release 17.5, the PDN GW SGi Node becomes available for input.

Tcl Parameter: SgwEmulationEn

Select to have the TEID on the S11 Interface be the same for all bearers per MN (PDNs per UE). Available for selection when SGW/PGW Node Emulation is enabled.

Also available on SGW Node test case - Same GTP-C TEID per MN on S11

Reference : 3GPP 29.274, Chapter 4.1 - "There shall be only one pair of TEID-C per UE over the S11 and the S4 interfaces. The same tunnel shall be shared for the control messages related to the same UE operation. A TEID-C on the S11/S4 interface shall be released after all its associated EPS bearers are deleted".

Tcl Parameter: SameGtpcTeidS11En

Select to include the Load Control Information (LCI) IE in the Create Session Response sent to the MME. Available when SGW/PGW Node Emulation is enabled. Per 3GPP Spec 29.274 (rel 15.4.0) section 12.2.5

Tcl Parameter: LoadControlInfoIeEn

Select to use IPSec to encrypt Data Traffic. Define IPSec parameters on the Data IPSec tab. The Data IPSec option is not available if Default Bearers per Session > 1.

Indicates the customer proprietary version of the application. Default value is None.

During MME Nodal testing, Gn Interface to MME is available only when Test Activity is Inter Technology Mobility, Handoff Protocol is UMTS (IuPS over IP) or GPRS and UMTS Version is 7. The checkbox is not available when Handoff Protocol is UMTS or eHRPD.

Tcl Parameter: GnToMmeEn

The Gn Interface to MME allows you to run a pre-release 8 Inter-Technology Mobility test and verify the operation of the Gn interface on the MME and PGW. The test uses either E-UTRAN (in case of Target = Target) or UTRAN (Target = LTE). When the mobility timer expires, the sessions will handoff between the E-UTRAN<->UTRAN until the test is stopped (assumes continuous handoffs is configured).

During MME Node testing, Gn Interface to SGSN is available only when Mobility is Inter-Tech, UMTS Version is 7 and Handoff Protocol is UMTS, UMTS (IuPS over IP), UMTS (IuCS over IP)or GPRS.

Tcl Parameter: GnToSgsnEn

The Optimized Handoff checkbox in MME Nodal testing is available only when Test Activity is Inter-Technology Mobility and Handoff Protocol is eHRPD.

Use the checkbox to select the SGW S103 SUT and configure the HSGW S103 Node on the Network Devices tab for optimized handoff.

Selecting Optimized Handoff allows you to configure only one eNodeB Control Node and Target HSGW Node.

The test also requires a MME-S101 SUT to be configured, which is not relevant or used in Non-Optimized configuration.

Tcl Parameter: OptimizedHandoffEn

During MME Nodal testing, The S3 Interface to MME checkbox is available only when Test Activity is Inter Technology Mobility, Handoff Protocol is UMTS (IuPS over IP) or GPRS and UMTS Version is 8 and Vendor Variant is NONE.

S3 Interface between MME and SGSN enables bearer information exchange for inter 3GPP access network mobility in idle and/or active mode.

Select the S3 Interface to MME checkbox to enable Direct Tunnel checkboxes.

Tcl Parameter: S3InterfaceEn

During MME Node testing, S3 Interface to SGSN is available when Mobility is None and SGW/PGW Node Emulation is not selected.

Tcl Parameter: S3EmulationEn

During MME Nodal testing, Select the Circuit Switched Fallback (CSFB) to enable the provisioning of CS-domain services. The CSFB checkbox is available when Test Activity is Inter Technology Mobility, Handoff Protocol is UMTS (luPS over IP, IuCS over IP or IuCS & IuPS over IP) or GPRS and Initial Network is LTE, or when Test Activity is Command Mode or Sequencer and Handoff Protocol is UMTS (luPS over IP) or GPRS.

Must enable Circuit Switched Fallback when Test Activity = Inter Technology Mobility and Handoff Protocol = UMTS (IuCS over IP).

During MME Node testing , the Circuit Switched Fallback (CSFB) checkbox is available when Mobility is Inter-Technology or Command Mode, or when Mobility is None and SGW/PGW Node Emulation is not selected.

The Sv Interface is used for SRVCC testing and is not available when Circuit Swift Fallback is enabled and vice versa.

If VoLTE is enabled, Circuit Switched Fallback is disabled and vice versa.

Value: True/False

Tcl parameter: EnbCsfbEn

Tcl parameter: MmeCsfbEn

During MME Nodal Testing, DTM (Dual Transfer Mode) Support is available when Circuit Switched Fallback is selected, Test Activity is Inter-Technology, Handoff Protocol is GPRS, and SI-AP Version is 8.7 or later

When the DTM Support is not selected the traffic data is not transferred after the session HO to GERAN.

Tcl Parameter: CsfbDTMSupportEn

In MME Node testing, selecting Piggyback Simulation allows the dedicated bearers to be established at the same time as the default bearer. Configure MME Node to do piggyback simulation by selecting the number of dedicated bearers you wish to establish.

The value in the Piggyback Simulation dropdown depends on the Number of Dedicated Bearers Configured. The value selected   by the Piggyback Simulation dropdown list indicates the number of Dedicated Bearers that establishes at the same time as the Default Bearer. If Number of Dedicated Bearers is 0, then all dedicated bearers will be established without piggy back simulation.

Tcl parameter: PiggybackSimulation

During MME Nodal testing,  Direct Tunnel is available only when you select S3 Interface to MME.

Tcl parameter: DirectTunnelEn

The Round Robin Handover checkbox is available only when the Test Activity is Inter-MME Mobility or Intra-MME Mobility or Session Loading with Mobility and the handover type is X2, S1 or TAU/RAU.

Selecting the checkbox supports executing X2, S1 and TAU/RAU1 Handovers to any number of eNBs, while UEs move back and forth between many eNBs.

Tcl Parameter: EnbRrHoSupport

Value: True / False

Default: False

Available when Test Activity is Inter-MME Mobility and Session Loading with Mobility using Inter-MME  as Mobility Type, and when you select S10 Interface to MME.

In MME Node test case,

• HSS Interface is available when you select S10 Interface to MME.
• HSS Interface is allowed for Inter-tech mobility with CSFG (Circuit Switched Fallback) and SGs Interface as well as non-mobility configurations.
• HSS Interface is enabled for Command Mode and Inter-Tech when Handoff Protocol = UMTS (IuCS & IuPS over IP). In this configuration, SRVCC is currently forced in a checked state. I2 and HSS Interface are enabled and can be checked.

Select HSS Interface to configure S6a interface tab parameters and HSS SUT controls (IP address, Host, Realm Port). In addition, configure the test nodes as  required, in MME Nodal test case Target MME S6a Node and in MME Node test case MME S6a Node.

Tcl Parameter: HssIfEn

Available when Test Activity is Capacity, Session Loading Test, Intra-MME Mobility, Inter-MME Mobility or Session Loading with Mobility when mobility type is Inter-MME, Intra-MME or Inter Technology Mobility and Handoff Protocol is not = 1xRTT or X2, ePDG node off and not UMTS (IuCS over IP).

Tcl Parameter: VolteEn

Select to test the IMS VoLTE feature which supports SIP and RTP-based Voice over in MME Nodal test case. You are required to configure the following:

• VoLTE
• Phonebook: SIP Subscribers; SIP Endpoints; Server Profile
• Gm Interface: Control:SIP  Media: RTP

Select for the Ut/Ub interface to NAF/BSF. The following diagram in 3GPP TS 33.804 shows the network diagram when Generic Bootstrapping Architecture (GBA) is used with the Authentication Proxy. Network Authentication Function (NAF) will be acting like AP to perform authentication between UE and AS using HTTP Digest. BootStrapping Function (BSF) will be used to prepare bootstrapped security association, which includes Bootstrapping Transaction ID (B-TID) and bootstrapping information, to be used for the authentication session over Ut interface. Bootstrapping over Ub interface is based on HTTP Digest AKA.

Type: True/False

Default: False.  

Tl Parameter: UaUbEn 

The S10 Interface on the MME Nodal allows handover between real MME and an emulated (Landslide) MME. You may select S10 Interface to MME when the Test Activity is Inter-MME.

Type: True/False

Default: False.  

Tcl Parameter: S10InterfaceEn 

In MME Node test case, S10 Interface to MME is available when Mobility is None and SGW/PGW Node Emulation is not selected.

In MME Nodal test case, Sv Interface allows you to indicate the SRVCC Handoff type.

Sv Interface is available when Test Activity is Inter Technology Mobility, Handoff protocol is UMTS (IuPS Over IP) or UMTS (IuCS & Iups over IP) or GPRS, Initial Network is LTE, Handoff Type is Handover and UMTS Version is 8 on MME Nodal Test Configuration tab and the version number is  >= 10 on s1-MME| NAS / S1-AP and S3/S4 | GTPv2 tab if applicable.

When Sv Interface is selected - the SRVCC Handoff Type field is enabled

Tcl Parameter: SvHandoffType

When Handoff Protocol is UMTS (luPS Over IP) - SRVCC Handoff Types

When Handoff Protocol is GPRS - SRVCC Handoff Types

In MME Node test case, Sv Interface is available when you select as follows.

SRVCC

Select to enable SRVCC (Single Radio Voice Call Continuity). VoLTE  and SRVCC automatically enabled when Handoff Protocol = UMTS (IuCS & IuPS over IP) in MME Nodal Test Case.

Tcl Parameter: SrvccEn

See Sv Interface for further explanation.

SGs Interface

Available (in MME Nodal) only when you select Sv Interface or Circuit Switch Fallback and do not select S3 Interface to SGSN or Gn Interface to SGSN. Or when you select Short Message Service (SMS) which is available for all test configurations with the exception of Command Mode, Sequencer, Inter-Technology Mobility, Session Loading With Mobility and the Mobility Type is Inter Technology.

On MME Node, SGs interface is available for all test configurations.

Configure the SGs Interface tab parameters to define re-connection (between UE and MME).

Tcl Parameter: SgsInterfaceEn

Enable the I2 Interface -  to/from the MSC to IMS for SIP portion of VoLTE calls after SRVCC handover.

I2 Control:  SIP , TCP 

Available on MME Nodal and MME Node test cases.

Available in MME Nodal only when Test Activity = Inter Technology Mobility and Handoff Protocol = GPRS or UMTS (IuPS over IP) and you select VoLTE and SRVCC and Sv Interface. 

Available in MME Node only when Mobility = Command Mode and Handoff Protocol = UMTS (IuCS and IuPS over IP) and you select SRVCC. 

MSC I2 Node becomes available for input.

Tcl Parameter: I2En

The MAP-D interface is used by the MSC/VLR to inform the HLR of the whereabouts of the mobile subscriber. See diagram above in I2.

Available in MME Nodal only when Test Activity = Inter Technology Mobility and Handoff Protocol = GPRS or UMTS (IuPS over IP) and you select VoLTE and SRVCC and Sv Interface. 

Interface MAP, MSC MAP Node and HLR SUT become available for input.

Tcl Parameter: MapDEn

Available in MME Nodal and IMS Node test cases for supporting ISUP-based call handling to assist the handover of voice calls from E-UTRAN (PS domain) to UTRAN/GERAN (CS domain) in SRVCC.

Available in MME Nodal when Inter Technology Mobility test-activity for simulating handover procedure from LTE to UMTS (IuCS over IP), VoLTE, SRVCC, Sv Interface, MAP-D are enabled. NC-ISUP Interface becomes available : Control - ISUP , M3UA , SCTP as well as MSC Nc ISUP Node.

Available in IMS Node when Gm interface with Endpoint mode selected to support handover. NC-ISUP Interface becomes available : Control - ISUP App, ISUP FLOW , M3UA , SCTP as well as MGCF Node.

The following diagram shows the component view of end-to-end call with the emphasis of non-ICS MSC server’s ISUP call handling for assisting the handover procedure from E-UTRAN to UTRAN/GERAN. The ISUP-based call handling is highlighted in red.

• (1) Call is started between a MO and MT subscriber on LTE/E-UTRAN and anchored on IMS SCCAS
• (2) MO subscriber moves out of LTE/E-UTRAN and into a new area UTRAN or GERAN belongs to an non-ICS MSC server
• (3) MME send call info (i.e. STN-SR Session Transfer Number - SR) to MSC
• (4) MSC server calls IMS uses ISUP protocol.
• (5) IMS SCC AS accepts new call-leg and terminate old/initial call-leg

Perform the handover procedure specified in the session 6.2 of 3GPP TS 23.216:  This session 6.2 has multiple sub-sessions for various types of handover; however, our focus is on the sub-session involving CS domain.  One of the sample flows is shown below:

Specification Reference:

• 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2"
• 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks"
• 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) centralized services; Stage 2"
• ITU Q.761-Q.764 ISDN User Part (ISUP) Protocol suite
• IETF RFC 4666: SS7 MTP3 User Adaption Layer (M3UA).
• 3GPP TS 23.232: "SIP-I based circuit-switched core network; Stage 2"
• 3GPP TS 23.205: "Bearer-independent circuit-switched core network; Stage 2"

Tcl Parameter: NcIsupEn

In MME Nodal test case, select to ensure that the test run logs reports status of each eNodeB goes up or down.

You may use the available log, for example, to reset some values on the SUT, ignore the associated set of ALARMS, and so on. The log reports

Tcl Parameter: LogEnbStatusEn

In MME Nodal testing, the SGW Relocation checkbox is available for mobility test activities (Session Loading with Mobility,  Intra-MME Mobility, Inter-MME Mobility or Command Mode or Sequencer without 1xRTT, WiFi or ePDG Node Emulation). When selected, you are allowed to configure the Target SGW GTP Node in the Network Devices tab.

In SGW Nodal testing, the SGW Relocation checkbox is available with LTE Relay off Bearers and ( Inter Technology Mobility with UMTS Version 8, not eHRPD, not WiFi , Not SRVCC and not Inter-SGSN or not TAU/RAU Handover), or  Inter-MME Mobility or Intra-MME test activities). With these settings, you are also allowed to configure Target eNodeB User Node, Target SGSN Control Node and Target MME Control Node. When the Test Options are Inter Technology Mobility and you select the SGW Relocation checkbox, the SGSN connects to Target SGW and Direct Tunnel may be selected. The GTPv2 tab displays Target Bearer Settings with handoff settings for ULI and QOS.

Tcl Parameter: SgwRelocationEn

Available Test Activity is Inter-Technology Mobility and Handoff is eHRPD (if licensed for eHRPD Handoff Protocol).  

Select ePCF Node Emulation to configure RP Interface parameters, Target ePCF Node and HSGW SUT.

Tcl Parameter: EpcfEmulationEn

When you select ePCF Node Emulation and if the number of Default Bearers is > 1, CDMA TFT Settings is available for configuration.  

LMA Node Emulation

Available when you select ePCF Node Emulation.

Select LMA Node Emulation for control node availability (S2a interface). The Bearer IP Address Pool on the Mobile Subscribers pane are available only when you select LMA Node Emulation.

Tcl Parameter: LmaNodeEn

In MME Nodal test case, the eHRPD Handoff required you to configure Target HSGW SUT, LMA Node (emulated PDN GW) and Target ePCF Node on the Network Devices tab.

Cell Change Mode

PMIPv6 Transport

Available only when you select the LMA Node Emulation.

Select to enable IPSec encapsulation between the UE/ePCF, HSGW and LMA Node (PDN GW). Define the IPSec settings on the PMIPv6 IPSec tab.

Tcl Parameter: LmaPmip6IpSecEn

X2 Interface

Available in MME Nodal test case, when Test Activity is Intra-MME Mobility and Handoff Type is X2.

Tcl Parameter: X2IfEn

AP Tunnel Type

Available when Handoff Protocol = WiFi and Test Activity = Inter Technology Mobility.  Used to support for WLAN AP emulation for Wi-Fi Calling test.

None indicated no tunnel between Access point and WOGW.

 ePDG Node Emulation  

ePDG Node Emulation is available only if your system is licensed and when Test Activity is Command Mode or Sequencer. When you select ePDG Node Emulation, you are required to configure the PGW S2b  SUT and Target ePDG Control and User Nodes on the Network Devices tab and GTPv2 tab on the S2b interface.

When you select ePDG Node Emulation, S2b interface is available.

Tcl Parameter: EpdgNodeEn

SWm Interface is enabled when ePDG Node Emulation is enabled.

LCS Support

Reset UE Positioning Stored Info

Selecting LCS Support provides the Sls interface tab in MME Node/Nodal test cases for MME to request location information from the e-SMLC.

Available only when S1-AP Version is greater than 9.4.

LCS Support is now available in the 5G AMF Nodal , gNB CU SA Nodal, and AMF Node test cases. Currently, we support UE Based and UE assisted A-GNSS method. If TDF file is used, only the A-GNSS related parameters need to be configured.

• When enabled in AMF Nodal/gNB CU SA Nodal, the LCS Interface with LPP Tab is available for input.
• When enabled in AMF Node, the LMF Interface with LPP Tab is available for input.

If Reset UE Positioning Stored Info is enabled (Per TS38.509 6.6.1), “NRPPa” command is triggered with the following messages;  

• Reset UE positioning stored Info” message with NAS-PDU: 0x0f8800;

              Protocol discriminator: 1111  

              Skip indicator: 0000 = No indication of selected PLMN (0)

              Message type: Reset UE Positioning Stored Information (0x88)

              UE Position Technology: 0000 0000 = AGNSS (0)

• e-CID Measurement Initiation with NRPPa-PDU

If Reset UE Positioning Stored Info is disabled, “NRPPa” command is triggered with the following message;

• e-CID Measurement Initiation with NRPPa-PDU

Tcl Parameter: LcsEn

Tcl Parameter: LcsRstUePosInfoEn

S1-Flex (MME Pooling)

Selecting to send Service Request to specific MMEs (up to 10 MMEs) at a specific rate under the S1-Flex Configuration.  

Available in MME Nodal when Test Activity = Command Mode/Sequencer and Handoff Protocol = None. Disabled when ePDG Node Emulation is enabled.  Available in MME Node when Mobility = None.

This feature enables the Multiple SUTs selection on the Network Devices Tab/Systems Under Test/MME tab.  Enter the number of MME's In Network Devices - Number of SUTs.  

Tcl Parameter: MmePoolingEn

B-TrunC

Available only when S1-AP Version is = 10.5.0 or 10.6.0 or 11.1.0 and Test Activity = Capacity. Also available when Test Activity = Inter-MME Mobility and Handoff Type = S1.

Select for support of LTE based Broadband Trunking Communication (B-TrunC).

B-TrunC is mutually exclusive with VoLTE and SGW/PGW Node Emulation.   

Tcl Parameter: BtruncEn

Wifi Offload Node Emulation

Available only when Test Activity = Command Mode or Sequencer.

Select for support of WLAN AP emulation for Wi-Fi Calling test in Command Mode and Sequencer.

Enables AP Tunnel Type, WiFi Subscribers, Handover for OnDemandCommand, AP-WAN Node, SWu IPSec Tab, AP/SSID Tab on MME Nodal Test.

Tcl Parameter: WifiNodeEn

Init From Target eNodeB

Available on MME Nodal only when Test Activity = Inter-MME Mobility , Intra-MME Mobility, or Session Loading with Mobility where Mobility Type = Inter-MME or Intra-MME.

Select to disable the Source gNodeB to allow the simulation of mobility scenario's where the UE attaches to the 4G cell and then moves to the 5G cell.

Tcl Parameter: InitFromTargetEnbEn

PC3/PC8/Ub

Available on MME Nodal.

In the Proximity-based Services (ProSe) network, PC3 is the reference point between the UE and ProSe Function. PC8 is the reference point between the UE and ProSe Key Management Function. The following diagram is from TS 33.303.

The SUT is ProSe Fn/BSF. Interface PC3 PC8 becomes available for input. Tabs PC3 PC8 APP, Ub App, PC3 PC8 Flows, Ub Flows.

Tcl Parameter: Pc3Pc8UbClnEn