Network Devices

Select the SUT distribution method used to identify and utilize SUTs (for testing AAA, DCCA, etc)

Options:

Select the Primary SUT and Secondary SUT in both the Authentication and Accounting tabs. An authentication SUT must be defined when the AAA Test type includes authentication, and an accounting SUT must be defined when the test includes accounting messages. The same AAA server can be selected for both the authentication and accounting functions.

• SUT — Use the SUT list in each sub-pane to select a SUT.

• AAA Multi-Homed —  Use the SUT list in each sub-pane to select a SUT.  (Only available for S6b Interface)

• Host and Realm (Diameter)

1. Host	A Diameter SUT's FQDN, which is used to provision the Destination-Host AVP in messages sent by the node. The presence of a Destination-Host AVP indicates that a request should be serviced by a specific Diameter server rather than any Diameter server in the destination Realm. Range: N/A Default: tester.yournet.com
   Realm	The Diameter Realm serviced by the SUT, which is used to provision the Destination-Realm AVP. This equates to an MN's Home Realm. Range: N/A Default: yournet.com

Up to 10 SUTs can be defined and all traffic for an MN is directed towards one of the servers. The servers are selected in round-robin fashion with the first MN's traffic directed to the first server, the second MN's traffic directed towards the second server, and so on.

When Distribution Mode is set to Round-Robin, you can include up to 10 SUTs in the test. A numbered sub-tab is provided to define each SUT.

• Number of SUTs — Select the number of SUTs.

Options: 1 — 10

Default: 1

• SUT — Select a SUT.

Options: The lists contain all defined SUTs.

Default: N/A

• AAA Multi-Homed — Select a SUT. (Only available for S6b Interface)

• Host and Realm (Diameter)

1. Host	A Diameter SUT's FQDN, which is used to provision the Destination-Host AVP in messages sent by the node. The presence of a Destination-Host AVP indicates that a request should be serviced by a specific Diameter server rather than any Diameter server in the destination Realm. Range: N/A Default: tester.yournet.com
   Realm	The Diameter Realm serviced by the SUT, which is used to provision the Destination-Realm AVP. This equates to an MN's Home Realm. Range: N/A Default: yournet.com

Select to enter Number of AMF SUTs.

Range: 2 to 30

• Number of AMF SUTs is the # of AMF SUTS to be configured.

• If both Number of AMF SUTs and Multiple SUTs per gNB are selected, then each gNB will have multiple AMF SUTs as defined by the Number of AMF SUTs.

• If Number of AMF SUTs is selected and Multiple SUTs per gNB is not selected, then the Number of AMF SUTs will be round robin-ed on gNBs. Each gNB will have a single MME SUT.

• Select Specify AMF SUTs to specify SUTs in different rows from the list. Available when Number of AMF SUTs is selected.

Tcl Parameter: GnbNumSutsEn

Tcl Parameter: GnbNumSuts

Tcl Parameter: MultiSutsPerGnbEn

Tcl Parameter: GnbSutTableEn

Select to indicate that SCTP endpoint is multi-homed, where more than one destination transport address is used to reach the endpoint.

Multi-Home-Dynamic is available only when you select Multi-Homed. Select to allow the secondary IP (dynamically learned during association) and the AMF to use the secondary (not respond to the primary after association is established).

(See RFC 4960 Sections 3.3.3 Sending additional IP in INIT-ACK and 8.3 Path Management using HEART-BEAT).

Tcl Parameter: GnbSctpMultiHomedEn

Tcl Parameter: GnbSctpMultiHomeDynamicEn

• When you select Multi-Home-Dynamic, the Secondary AMF SUT is not available.

The Relative AMF Capacity specifies the capacity of an AMF in an AMF set relative to the other AMFs in the same AMF Set. Relative AMF Capacity is sent to the connected gNodeBs in the NG Setup Response and AMF Configuration Update messages. The Relative AMF Capacity is to be used by the simulated gNBs to distribute subscribers among the AMFs in the set. For example, if AMF1's Relative AMF Capacity = rac1 and AMF2's Relative AMF Capacity = rac2, then gNB will distribute rac2/(rac1+rac2) fraction of the incoming traffic to AMF1 and distribute rac1/(rac1+rac2) fraction of the incoming traffic to AMF2 (i.e., more traffic is distributed to the less loaded AMF). If Relative AMF Capacity of an AMF = 0, the gNB will not send traffic to the AMF.

Indicates the AMF pool capability. The weight factor format is number1#number2, for example, 1#1, 10#4. This means that the weight factor on first link is the "number1" and the second is "number1+1*number2", 3rd is "number1+2*number2", and so on.

If you wish to allocate the same Weight Factor on all the links you can set it as "number1#0".

It is enabled when "Multiple SUTs per gNB" is checked.

Default: 1#0 (Maximum of 6 characters)

Tcl Parameter: AmfCapabilityEn

Tcl Parameter: AmfCapability

From Pool

Primary Pool

Secondary Pool

The "From Pool" checkbox option is enabled when multiple SUTs are being specified in the table and TAS has at least one SUT Pool configured via Admin - About Systems Under Test Pools. When "From Pool" is checked, the table is not editable by the user but becomes updated based on the selected Primary/Secondary pool. The SUT Pool must contain the number of SUTs the table is configured for or else the test case cannot get past the OK validation.

When SUT Pool is enabled, a SutPool class parameter is defined in the Test Case and the user must select a SUT Pool from the TAS. The Test Case GUI and API/Upgrade validation will automatically fill out the actual Sut class parameters based on the pool. SUT Pools act like an auto-fill wizard each time you reopen a Test Session. If the Test Session is exported, the SutPool parameter as well as the last filled out Sut parameters will be included. When the Test Session is imported to a different TAS that does not support SUT Pools or does not have the same named SUT Pool, the SUT Pool will be disabled and it will revert to just the last list of SUTs. If the SUT Pool name is valid for the same or different TAS but the pool configuration contains different SUTs, the session file will be updated based on the current SUT Pool configuration. For any case, the SUT Pool selected must contain at least as many SUT entries as required by the test configuration.

From the APIs, the SUT list is only automatically filled out when Validation occurs. The user could fill out the SUT list themselves, but once saved or executed by the TAS, the TAS validation will replace their list with reloaded list from the defined SUT Pool. In general API users that use SUT Pools should just deal with the SutPool parameters and let TAS do the job of filling out the SUTs.

Also available for the Target AMF SUT.

Tcl Parameter: AmfSutPoolEn

Tcl Parameter: AmfSutPool

Tcl Parameter: MobAmfSutPoolEn

Tcl Parameter: MobAmfSutPool

Select to enter Number of Target AMF SUTs. Available when Test Activity = Inter-AMF Mobility.

Range: 2 to 30

• Number of Target AMF SUTs is the # of Target AMF SUTS to be configured.

• If both Number of Target AMF SUTs and Multiple Target SUTs per gNB are selected, then each Target gNB will have multiple Target AMF SUTs as defined by the Number of Target AMF SUTs.

• If Number of Target AMF SUTs is selected and Multiple Target SUTs per gNB is not selected, then the Number of Target AMF SUTs will be round robin-ed on Target gNBs. Each Target gNB will have a single MME SUT.

• Select Specify Target AMF SUTs to specify SUTs in different rows from the list. Available when Number of AMF SUTs is selected.

Tcl Parameter: MobGnbNumSutsEn

Tcl Parameter: MobGnbNumSuts

Tcl Parameter: MobMultiSutsPerGnbEn

Tcl Parameter: MobGnbSutTableEn

Select to indicate that the Target SCTP endpoint is multi-homed, where more than one destination transport address is used to reach the endpoint.

Multi-Home-Dynamic is available only when you select Multi-Homed. Select to allow the secondary IP (dynamically learned during association) and the AMF to use the secondary (not respond to the primary after association is established).

(See RFC 4960 Sections 3.3.3 Sending additional IP in INIT-ACK and 8.3 Path Management using HEART-BEAT).

Tcl Parameter: MobGnbSctpMultiHomedEn

Tcl Parameter: MobGnbSctpMultiHomeDynamicEn

• When you select Multi-Home-Dynamic, the Secondary Target AMF SUT is not available.

Secondary AMFs becomes available when you select Multi-Homed and you may specify the secondary address for the corresponding AMF SUTs.

Secondary AMFs is not available when you select Multi-Home-Dynamic.

The primary path that carries traffic switches to a secondary path for carrying traffic when a fault is detected, and switches back to the primary path, after it is restored or if the secondary path becomes faulty. (See RFC-4960)

Choose an SSID SUT - Available when N3IWF is enabled on AMF Nodal test configuration.

Tcl Parameter: SsidSut

Choose an AGF SUT - Available when 5G-RG is enabled on AMF Nodal test configuration.

Tcl Parameter: AgfSut

Enter MME SUT - Available when Test Activity = Inter Technology Mobility on AMF Nodal test configuration.

Target MME SUT is available when Enable Target eNodeB is enabled on EPS Pane in the AMF Nodal test case.

Tcl Parameter: MmeSut

Select to enable support for simulated SMF node to support UPF discovery via NRF (either real or simulated)
Only available when "NRF Interface” is checked in Emulation options panel.
When "Use UPF Discovery via NRF" is checked, only the "Number of SUTs" and "UPF N4 GTP Node" are available for use.

Tcl parameter: UpfDiscViaNrfEn

See TS 23.214 for Architecture enhancements for Control and User plane separation of EPC Nodes.

See TS 29.244 for Interface specifications between the Control plane and User plane of EPC Nodes.

See TS 23.214 for Architecture enhancements for Control and User plane separation of EPC Nodes.

See TS 29.244 for Interface specifications between the Control plane and User plane of EPC Nodes.

The N3 / N9 Interface provides a reference point between (R) AN and the UPF in a 5G Architecture. See additional details in About the 5g Application. Per 23.501 4.2.7

Available when you select N26 Interface on the AMF Node Emulator Configuration tab or on the gNB CU SA Nodal Test Configuration tab. N26 provides a reference point between Access and Mobility Management function (AMF) and the Mobility Management Entity function (MME).

Choose a SUT

Tcl Parameter: MmeN26Sut

AMF SBI

Available when SMF Emulation is disabled and N14 Interface is enabled on the AMF Node Emulator Configuration tab. N14 interface provides a reference point between 2 Access and Mobility Management functions (AMF).

N14 Interface towards AMF-AMF. The SUT is AMF SBI SUT (AMF Node and AMF SBI Node) for N14.

N11 Interface toward SMF is also 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) for N11.

SMF SBI

Available when SMF Emulation is disabled on the AMF Node Emulator Configuration tab. 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)

DNS Pane allows for capture of DNS Server details.

If NF Instance ID is selected, enter the NF Instance ID. You may change the default value however you must ensure it does not conflict with any other SBI node.

Format : UUID version 4: 4hexOctet-2hexOctet-2hexOctet-2hexOctet-6hexOctet

NRF SBI

Available when NRF Interface is enabled on the AMF Node Emulator Configuration tab.

LMF SBI

The SUT LMF SBI becomes available when NLs Interface is enabled on AMF Node Emulator Configuration. See additional detail in Service Based Nodal LMF SBI SUT section.

GMLC SBI

The SUT GMLC SBI becomes available when NLg Interface is enabled on AMF Node Emulator Configuration.

In addition to selecting a SUT with the ASN SUT, you can define the port used for the BS-ASN interface with ASN Port Number.

Range: 0 — 65535

Default: 2231

• Select Secondary HA to enable the second HA.

• When you use an Inter-PDSN , Inter-PDSN Rate , or Session Loading With Mobility test activity, the handoff FA SUT is defined with the test activity settings.

Enabled when DMU is selected. NAS Node is Enabled.

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 a FA SUT and HA node (FA Nodal) or a HA SUT and a FA node (HA Nodal) for control plane traffic. Define the IKE settings on the MIP IPSec tab.

Select the HA SUT to test a PDIF-FA. This SUT is not available when you select HA Node Emulation on the Test Configuration tab.

• Port: Enter the port used by the SUT for PDIF-FA traffic.

Select the Home Agent address to be used in the RRQ.

Select the Enable Dynamic Home Agent check box if you wish to set the address in the initial RRQ to 0.0.0.0.

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 enabled if Client MIP is selected or HA Node Emulation is enabled.

DCCA Server Distribution Mode

Use the radio buttons to select the method used to identify and utilize DCCA SUTs.

Options:

• Dedicated — Primary and secondary SUTs can be selected and defined for the DCCA Dedicated SUTs.

• Round-Robin — Up to 10 SUTs can be defined for Round-Robin. The servers are selected in round-robin fashion with the first MN's traffic directed to the first server, the second MN's traffic directed towards the second server, and so on.

  NOTE: Failover Handling is supported in Dedicated mode. If an error is encountered with one of the DCCA SUTs in Round-Robin mode, the appropriate error counter is incremented and the MN session is left in the pending state — no attempt is made to utilize one of the other SUTs.

Default: Dedicated

The port used by the SUT for DCCA traffic.

Range: N/A

Default: 3868

When DCCA Distribution Mode is set to Dedicated, you can select the SUT configuration using the Primary Proxy,  CTF Multi-Homed, Secondary proxy, and Secondary Server checkbox. When you select a configuration with a secondary device, you can enable Failover support.

SUT Definition

Use the following parameters to identify the SUT. The Secondary parameters are enabled depending on the checkbox selected (Primary Proxy, CTF Multi-Homed, Secondary Proxy, and Secondary Server).

The SUT selection list is available when the configuration includes a primary and secondary proxy/server. The Host and Realm can be defined for primary and secondary servers.

• IP — In each sub-pane, select the destination for messages sent towards a server — either a proxy or the server itself.

Options: The lists contain all defined SUTs.

Default: N/A

• Host — A Diameter server SUT's FQDN, which is used to provision the Destination-Host AVP in messages sent by the node. The presence of a Destination-Host AVP indicates that a request should be serviced by a specific Diameter server rather than any Diameter server in the destination Realm.

Range: N/A

Default: DCCA_Server.Spirent.com

• Realm — The Diameter Realm serviced by the SUT, which is used to provision the Destination-Realm AVP. This equates to an MN's Home Realm when the Client node is emulating a NAS.

Range: N/A

Default: Spirent.com

When DCCA Server Distribution Mode is set to Round-Robin, you can include up to 10 SUTs in the test. A numbered sub-tab is provided to define each SUT.

DCCA Server — Use the drop-down list on each sub-tab to select a SUT.

Options: The lists contain all defined SUTs.

Default: N/A

CTF Multi-Homed — Use the drop-down list on each sub-tab to select a SUT.

Options: The lists contain all defined SUTs.

Default: N/A

Host and Realm

System Under Test

• Click Add to insert a new SUT information. Insert multiple rows (required number of SUTs)to configure multiple IP addresses when SUT consists of multiple devices or SUT requires different types of traffic to be run on different physical links.

• Click Remove to delete the SUT information from the SUT table.

HSS

Available for configuration when you enable HSS Interfaces on the Test Configuration tab but HSS is not emulated by DRA Nodal test case.

• Host – Specify a Diameter host-name of a HSS.

• Realm – Specify a Diameter realm-name to which a HSS belongs.

• Port – Specify a serving port number of a HSS.

PCRF

Available for configuration when you enable PCRF Interfaces on the Test Configuration tab but PCRF is not emulated by DRA Nodal test case.

• Host – Specify a Diameter host-name of a PCRF.

• Realm – Specify a Diameter realm-name to which a PCRF belongs.

• Port – Specify a serving port number of a PCRF.

Node Connection Assignment

Identifies the local nodes currently assigned to a Primary and Secondary SUTs.

Primary/Secondary SUTs

Indicates that a server node uses multiple addresses, one for each of its enabled interface.

You configure separate address for each enabled interface of a server node.

Server node replicates multiple local nodes (one for each enabled interface).  For example, if both Gx and Rx interface of a PCRF server are enabled and PCRF On Multiple Addresses is selected, 2 local nodes display for a PCRF server as follows:

• PCRF-Node-Gx-1 is required for the Gx interface

• PCRF-Node-Rx-1 is required for the Rx interface  

Number of SUTs

Indicates the number of peers the Node supports. Select from the drop down list or click to add a row to configure a peers the Node supports. You may add a maximum of 60 peers, after which the button is greyed.

Click -- to delete the selected row.

Option: 1 - 60

On the Primary and Secondary tabs, the number of rows displayed/available for peer configuration depends on the value you select in the Number of SUTs.  

Primary / Secondary Tab

The number of SUTs reflects the number of entries/rows in the peer table in Primary and Secondary tabs.

On the Secondary tab, the number of SUTs reflect the number of entries/rows in the peer table on the Primary tab. That is, each row on the Secondary tab is associated with the corresponding row on the Primary tab.

Number of Policy Sets

Indicates the number of policy sets to be defined. Select from the drop down list.

Option: 1 - 60

The number of Policy Set n tab displayed/available for configuration depends on the value you select in the Number of Policy Sets.  

Policy Set n

A policy set contains the number of policies that may be applied to the peer.

Number of Policies: Each Policy Set, may have a maximum of 2 Policies, which allows you to combine different type of policies (Total and Burst).

Option: 1 - 2

The number of Policy n tab displayed/available for configuration depends on the value you select in the Number of Policies.  

Policy n

A Policy allows you to define the type and the number of sessions to which the policy is applicable. When using Policies, must set Action to PROXY on the Realm-based Routing Table.

• Type: Indicates the type of policy enforce.

• Sessions: Indicates the number of session for which the Policy type is enforced. That is, define the number of sessions for the policy.  Not applicable when type is IMSI or MSISDN.

• Range Start: Indicates the Starting Range of IMSI or MSISDN numbers. Valid range between 5 and 15 numbers.  No Default. Not Applicable when type is Burst or Total.

• Range End: Indicates the Ending Range of IMSI or MSISDN numbers. Valid range between 5 and 15 numbers. No Default. Not Applicable when type is Burst or Total.

Select a BM-SC SUT address from the list.

Select a GCS-AS SUT address from the list. Available when MB2 is enabled on the eMBMS Node emulator configuration test case. 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.

HSS SUT

HSS - Select the SUT IP address from the selection list.

The HSS SUT is available when Slh interface is selected.

The SLh interface tab in LCS Node test case for GMLC to request routing information from the HSS/HLR.

MME SUT

MME - Select the SUT IP address from the selection list.

The MME SUT is available when Slg interface is selected.

The SLg interface tab in LCS Node test cases for EPC location services between GMLC and MME.

E-SMLC SUT

Number of SUTs

Multiple SUTs per MME

Specify E-SMLC SUTs

Multi-Homed

E-SMLC SUTs

Secondary E-SMLCs

E-SMLC  - Select the SUT IP address from the selection list.

The E-SMLC SUT is available when the SLs interface is selected.

The SLs interface tab in LCS Nodal test cases for EPC location services between E-SMLC and MME.

Select to enter Number of E-SMLC SUTs.

Range: 2 to 30

• Number of SUTs is the # of E-SMLC SUTs to be configured.

• If both Number of E-SMLC SUTs and Multiple SUTs per MME are selected, then each MME will have multiple E-SMLC SUTs as defined by the Number of SUTs.

• If Number of (E-SMLC) SUTs is selected and Multiple SUTs per MME is not selected, then the Number of E-SMLC SUTs will be round robin-ed on MMEs. Each MME will have a single E-SMLC SUT.

• Select Specify E-SMLC SUTs to specify SUTs in different rows from the list. Available when Number of (E-SMLC) SUTs is selected.

• Select Multi-Homed to enter a Secondary E-SMLCs per SUT.

Tcl Parameter: MMeNumEsmlcutsEn

Tcl Parameter: MmeNumEsmlcSuts

Tcl Parameter: MultiEsmlcSutsPerMmeEn

Tcl Parameter: MMeEsmlcSutTableEn

Tcl Parameter: MMeEsmlcSctpMultiHomedEn

Tcl Parameter: EsmlcSut_1

Tcl Parameter: EsmlcSecSut_1

GMLC SUT

GMLC SUT is available on LCS Nodal test case when Slg or Slh is selected.

Number of GGSN SUTs

Enter the number of SUTs (1 - 1000).

GGSN SUT

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

Apply GGSN SUTs from Test Data File

Available if # of GGSN SUTs > 1 and allows you to configure multiple SUT and Control Node IP addresses.

See Applying Parameter ValuesApplying Parameter Values.

Alternate User Address

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.

CGF

Available when you select Billing on the GGSN Nodal Test Configuration tab.

L2TP

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.

Direct Tunnel

Number of SGSN SUTs

Enter the number of SUTs (1 - 1000).

SGSN SUT

Select the SUT and enter the user and Control ports

Apply SGSN SUTs from Test Data File

Available if # of SGSN SUTs > 1 and allows you to configure multiple SUT and Control Node IP addresses.

See Applying Parameter ValuesApplying Parameter Values.

Primary CGF

Available when you select Billing on the  GGSN Node Emulator Configuration tab.

Select Secondary CGF for failover purposes.

L2TP

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.

APN DNS Lookup

Select to enter the number of gNB-CU SUTs.

Range : 2 to 10

Tcl Parameter : GnbDuNumSutsEn

Tcl Parameter : GnbDuNumSuts

gNB-CU

Select the a SUT IP address from the selection list. Available in both gNB CU NSA Nodal and gNB CU SA Nodal test cases.

Tcl Parameter : GnbCuSut

gNB-CU X2 Enabled

Enable to select an alternate SUT for gNB-CU X2. Available in gNB CU NSA Nodal test case.

Select a gNB-CU X2 SUT IP address from the selection list.

Tcl Parameter : GnbCuSutX2En

Tcl Parameter : GnbCuSutX2

Select to enter the number of gNB-CU SUTs. Available in gNB CU NSA Nodal and gNB CU SA Nodal test cases when Test Activity = Inter-CU Mobility.

Range : 2 to 10

Tcl Parameter : MobGnbCuSut

Tcl Parameter : MobGnbDuNumSutsEn

Tcl Parameter : MobGnbDuNumSuts

Select to enter the number of gNB-CU SUTs. Available in gNB CU SA Nodal when MR-DC is enabled.

Range : 2 to 10

Select the a SUT IP address from the selection list.

Tcl Parameter : SnGnbDuNumSutsEn

Tcl Parameter : SnGnbDuNumSuts

Tcl Parameter : SnGnbCuSut

Target gNB-CU X2 Enabled

Enable to select an alternate SUT for gNB-CU X2. Available in gNB CU NSA Nodal test case when Test Activity = Inter-CU Mobility..

Select a Target gNB-CU X2 SUT IP address from the selection list.

Tcl Parameter : MobGnbCuSutX2En

Tcl Parameter : MobGnbCuSutX2

Number of AMF SUTs

Multiple SUTs per gNB

Specify AMF SUTs

AMF SUTs

Available in gNB CU Node when SA Mode is enabled. N2 to AMF Node and N3 to UPF Node become available for input.

Select to enter the number of AMF SUTs in support of NAS Reroute messages.

Spec reference : TS 23.502 , TS 38.413 

Range : 2 to 30

Select Multiple SUTs per gNB. 

Select to Specify AMF SUTs.

Tcl Parameter : GnbCuNumSutsEn

Tcl Parameter : GnbCuNumSuts

Tcl Parameter : MultiSutsPerGnbCuEn

Tcl Parameter : GnbCuSutTableEn

Tcl Parameter : AmfSut

Xn

Number of gNB-CU SUTs

gNB-CU Xn SUTs

Select to enter the number of gNB-CU Xn SUTs. Available in gNB CU Node when Xn Interface is enabled.

Choose a gNB-CU Xn SUT.

Range : 2 to 10

Tcl Parameter : GnbCuXnNumSutsEn

Tcl Parameter : GnbCuXnNumSuts

Tcl Parameter : GnbCuXnSut

MN-CU

Number of MN-CU SUTs

MN-CU SUTs

Select to enter the number of MN-CU SUTs. Currently 1 is supported.

Available in gNB CU Node when Xn Interface and MR-DC are enabled and when gNB Mode = SN.

Choose a MN-CU SUT.

Tcl Parameter : MnGnbCuXnNumSuts

Tcl Parameter : MnGnbCuXnSut_1

Select to choose a gNB-CU CP SUT. Available in gNB CU Node when E1 Interface to CU-CP is enabled.

Tcl Parameter : GnbCuCpSut

Select to choose a gNB-CU UP SUT. Available in gNB CU Node when E1 Interface to CU-UP is enabled.

Tcl Parameter : GnbCuUpSut

HA

Select the a SUT IP address from the selection list.

Multiple SUTs

Select to support connection to multiple SUTs and enter a value to indication the number of SUTs (2 to 1024).

The HA Nodal used round-robin method to assign the subscribers to different SUTs by default.

HNB GW

Select the a SUT IP address from the selection list.

The HNB SUT selection is not available when the HNB GW DNS Lookup checkbox on the Test Configuration tab is selected.  

SGSN

Available when 3G Macro RNC Emulation checkbox and PS Domain (or PS & CS Domain) on the Test Configuration tab are selected.

Select the a SUT IP address from the selection list for the SGSN.

MSC

Available when 3G Macro RNC Emulation checkbox and CS Domain (or PS & CS Domain) on the Test Configuration tab are selected.

Select the a SUT IP address from the selection list for the MSC.

HNB GW DNS Lookup

Use the parameters to allow SGSNs to make a DNS query for the DNS  to determine the GGSN address and forward the PDP contexts create request accordingly.

The HNB GW DNS Lookup parameters are available when the HNB GW DNS Lookup checkbox on the Test Configuration tab is selected.  

• Enter the Domain Name

• Configure the DNS Server IP Address to use for the DNS queries

• Enter the DNS Client Port

MME

Select the a SUT IP address from the selection list.

Multi- Homed

Secondary MME

Enable Multi-Homed to Select a Secondary MME SUT IP address from the selection list.

I-CSCF SUT

Available when Core Network is PS Domain and Interface = Mw. Enter I-CSCF SUT, and Port.

Tcl Parameter: IcscfSut

Tcl Parameter: IcscfSutPort

S-CSCF SUT

Available when Core Network is PS Domain and Interface = Mw. Enter S-CSCF SUT, and Port.

Tcl Parameter: ScscfSut

Tcl Parameter: ScscfSutPort

AS SUT

Available when Core Network is PS Domain and Interface = ISC. Enter AS SUT, Host and Port.

Tcl Parameter: AsSut

Tcl Parameter: AsSutPort

Tcl Parameter: AsSutHost

IBCF MX SUT

Available when Core Network is PS Domain and Interface = Mx. Enter IBCF Mx Control Address, IBCF Mx Data Address, and IBCF Mx Port.

Tcl Parameter: MxCtrlSut

Tcl Parameter: MxDataSut

Tcl Parameter: MxSutPort

GMLC

Available when Core Network is PS Domain and Interface = Ml. Enter GMLC SUT, and Port.

Tcl Parameter: GmlcSut

Tcl Parameter: GmlcSutPort

Generic SUT

Available when Core Network is PS Domain and Interface = Generic. Enter Generic SUT, and Port.

Tcl Parameter: GenSut

Tcl Parameter: GenSutPort

MGC SUT

Available when Core Network is CS Domain. Enter MGC SUT, Host and Port.

SIP Registrar SUT

Available when Core Network is CS Domain. Enter SIP Registrar SUT, Host and Port.

Local MGC to Remote MGC Assignments

Available when Core Network is CS Domain. Enter Node ID, Node Name, and MGC SUT.

Used for assigning local MGC to Remote MGC. Required for local MGC to forward messages to remote MGC. May assign multiple local MGC's to the same remote MGC node.

Up to 100 MGC Nodes (MgcSutToNodeList1 to MgcSutToNodeList100)

Tcl Parameter: MgcSutToNodeList1

Local MGC to SIP Registrar Assignments

Available when Core Network is CS Domain. Enter Node ID, Node Name, and SIP Registrar SUT.

Used to configure SIP registrar information (Address, Port, etc) and to provision which local MGC nodes to which SIP Registrars. May assign multiple local MGC nodes to the same SIP Registrar.

Up to 100 MGC Nodes (SipRegSutToNodeList1 to SipRegSutToNodeList100)

Tcl Parameter: SipRegSutToNodeList1

Enter the Host, Realm and Port IDs for the SUTs.

AF (PCRF) SUT

Select the AF (PCRF) SUT from the selection list . Available when Rx interface is Selected.

AF SUT Proxy

Select the AF SUT Proxy from the selection list . Available when Rx interface is Selected.

Secondary AF SUT

Select the Secondary AF (PCRF) SUT from the selection list . Select for support for Failover simulation for the Rx Interface. The Failover Simulation (Diameter Tab) pane becomes available for failover scenarios.

P-CSCF SUT

Select the P-CSCF SUT from the selection list. Available when Mw interface is Selected.

S-CSCF SUT

Select the S-CSCF SUT from the selection list. Available when ISC interface is Selected.

I-CSCF SUT

Select the I-CSCF SUT from the selection list. Available when ISC interface is Selected and mode = B2BUA.

BGCF Mx SUT

Select the BGCF Mx SUT from the selection list. Available when Mx interface is Selected.

MGW SUT

Select the MGW SUT from the selection list. Available when Mx interface is Selected.

ATCF SUT

Select the ATCF SUT from the selection list. Available when Mw + SIC interface is Selected.

MSC SUT

Select the MSC SUT from the selection list. Available when Mw + SIC interface is Selected.

AS SUT

Select the AS SUT from the selection list. Available when Mw + SIC interface is Selected.

Separate IP Addresses for RTP Traffic

Select to enter separate IP addresses for RTP Traffic. Separate IP address can optionally be used on a different Ethernet port.

Available on IMS Node (on Network Devices section) and IP Application Node on Mobile Subscribers section. Requires Gm Interface and RTP Traffic.

A new pane becomes available to enter: Physical Interface, Starting IP, MAC Address, Default Routing or Next Hop IP Address and Outbound Traffic Port.

Unique IP Addresses (IMS Node only) - Select for each SIP Endpoint simulated by IMS Node to have a unique IP Address assigned.

Tcl Parameter: RtpIpAddressEn

Tcl Parameter: RtpIpAddress

Tcl Parameter: UniqueRtpIpAddressEn

Enter the Host, Realm and Port IDs for the SUTs.

IP Application Node

Pilot Packet

WebDAV Server (for MPD) (for Media)

AP/AS

PDG Micro-Mobility

MC CMS

Contains the MC CMS panel. Available in MME Nodal, IP Application Node, PGW Nodal, SGW Nodal and Wifi Offload Gateway Nodal.

• Available when CSC-4 to Mission Critical CMS Interface is enabled.

MC CMS  - SUT. Enter SUT IP Address, Host, Realm and Port.

Select a MB2-BMSC SUT address from the list. Available when MB2 is enabled on IP Application Node Test Configuration. The MB2-C Node and MB2-U Node are used for Control and User plane communication between the GCS-AS and the BM-SC.

MGC SUT

Available when SLh interface is enabled on LCS Node Emulator Cnfg, its between GMLC and SUT ( MME ). 

Available when SLg interface is enabled on LCS Node Emulator Cnfg,  its between GMLC and SUT ( HSS ). 

Available when E2 interface is enabled on LCS Node Emulator Cnfg, its between GMLC and SUT ( PSAP E2 ).  LCS uses this interface for Location Information / Location Query Response on E2- Emergency Services Protocol (ESP).

Enter PSAP SUT E2, and Port (default = 7001).

Tcl Parameter: PsapE2Sut

Tcl Parameter: PsapE2SutPort

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.

CDMA/WiFi Convergence

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.

Mobile IPv6 Testing

Gs interface - Device name is MSC. Local SCTP port can be configured. Only One MSC and one SGSN can be configured. For SCCP, the SSN (sub system number) For BSSAO+ can be configured to either 251 or 252.

Iu-CS interface - Device name is MSC.

Target Iu-CS interface - Device name is MSC. Available when Mobility Support = Intra-MSC on MSC Node Emulator Configuration and Intra-HNB GW is not enabled.

Available when SGd interface is enabled on MSC Node Emulator Configuration. It is used to configure the MME SUT to which the emulated MSC will exchange Diameter SMS messages.  

SUT

Select the a SUT from the selection list: AGW, AF, or BBERF SUT.

The SUT selection list available depends on the checkbox you selected on the PCRF Nodal Test Configuration tab (AGW, AF, or BBERF SUT).

Enter the Host, Realm and Port IDs for the SUTs.

SUT Port

The port used by the SUT for PCRF traffic.

Range: N/A

Default: 3868

AF SUT Proxy

Use the AF SUT Proxy checkbox to set the proxy flag in the AAR message sent.

• Enter the Number of Associations. Maximum allowed is 16.
• Select a SUT for each GR SGSN/SUT row from the selection list and enter the appropriate Port number.

Select the GMLC SLh tab to allocate/select the Total Slh GMLCs and select the number of SUTs from the selection list. The number of rows of GMLC SLh SUTs displayed depends on value you selected from the Total SLh GMLCs list.

• Select a SUT for each GMLC SLh/SUT row from the list.

Select the SWx tab to allocate/select the Total AAA Servers and select the number of SUTs from the selection list. The number of rows of SWx AAA SUTs displayed depends on value you selected from the Total AAA Servers list.

Enter Host, Realm, Port and Initiator (Default = Checked). HSS Node will initiate the TCP connection if Initiator is checked.

• Select a SUT for each SWx AAA/SUT row from the list.

Select the S13 tab to allocate/select the Total S13 MMEs and select the corresponding number of SUTs from the selection list. The number of rows of S13 MME/SUT displayed depends on value you selected from the Total S13 MMEs selection list. Select a SUT for each S13/MME SUT row from the selection list.

Enter Host, Realm, Port and Initiator (Default = Checked). HSS Node will initiate the TCP connection if Initiator is checked.

• Select a SUT for each SWx AAA/SUT row from the list.

Select the S13' tab to allocate/select the Total S13' SGSNs and select the corresponding number of SUTs from the selection list. The number of rows of S13' SGSN/SUT displayed depends on value you selected from the Total S13' SGSNs selection list. Select a SUT for each S13'/SGSN SUT row from the selection list.

Enter Host, Realm, Port and Initiator (Default = Checked). HSS Node will initiate the TCP connection if Initiator is checked.

Select the SBc tab to allocate/select the Total SBc MMEs and select the corresponding number of SUTs from the selection list. The number of rows of SBc MME/SUT displayed depends on value you selected from the Total SBc MMEs selection list. Select a SUT for each SBc/MME SUT row from the selection list.

Select the Sh tab to allocate/select the Total Sh Application Serverss and select the corresponding number of SUTs from the selection list. The number of rows of Sh AS/SUT displayed depends on value you selected from the Total Sh Application Serverss selection list. Select a SUT for each Sh/AS SUT row from the selection list.

Enter Host, Realm, Port and Initiator (Default = Checked). HSS Node will initiate the TCP connection if Initiator is checked.

• Select a SUT for each S6t SCEF/SUT row from the selection list.

Select the Cx-I-CSCF tab to allocate/select the Total Cx-I-CSCFs and select the corresponding number of SUTs from the selection list. The number of rows of Cx-I-CSCF/SUT displayed depends on value you selected from the Total Cx-I-CSCFs selection list. Select a SUT for each Cx-I-CSCF SUT row from the selection list.

Enter Host, Realm, Port and Initiator (Default = Checked). HSS Node will initiate the TCP connection if Initiator is checked.

Select the Cx-S-CSCF tab to allocate/select the Total Cx-S-CSCFs and select the corresponding number of SUTs from the selection list. The number of rows of Cx-S-CSCF/SUT displayed depends on value you selected from the Total Cx-S-CSCFs selection list. Select a SUT for each Cx-S-CSCF SUT row from the selection list.

Enter Host, Realm, Port and Initiator (Default = Checked). HSS Node will initiate the TCP connection if Initiator is checked.

Select the Zh tab to allocate/select the Total BSF Servers and select the corresponding number of SUTs from the selection list. The number of rows of  Zh BSF/SUTs displayed depends on value you selected from the Total BSF Servers selection list. Select a SUT for each Zh BSF/ SUT row from the selection list.

Enter Host, Realm, Port and Initiator (Default = Checked). HSS Node will initiate the TCP connection if Initiator is checked.

Available only when HSS-MME/SGSN I/F (S6a, S6d or Gr)  Interface is selected on the HSS Nodal Test Configuration tab and when Target Emulated Interfaces (S6a, S6d and Gr) are enabled for Mobility Test Activities.

• Host — A Diameter server SUT's FQDN, which is used to provision the Destination-Host AVP in messages sent by the node. The presence of a Destination-Host AVP indicates that a request should be serviced by a specific Diameter server rather than any Diameter server in the destination Realm.

Range: N/A

Default: HSSServer.Spirent.com

• Realm — The Diameter Realm serviced by the HSS SUT, which is used to provision the Destination-Realm AVP. This equates to an MN's Home Realm when the Client node is emulating a NAS.

Range: N/A

Default: Spirent.com

• Port — Enter the port used by the HSS SUT for traffic.

Select to indicate that SCTP endpoint is multi-homed, where more than one destination transport address is used to reach the endpoint.

Available only when HSS-Sh I/F (Sh)  Interface is selected on the HSS Nodal Test Configuration tab.

• Host — A Diameter server SUT's FQDN, which is used to provision the Destination-Host AVP in messages sent by the node. The presence of a Destination-Host AVP indicates that a request should be serviced by a specific Diameter server rather than any Diameter server in the destination Realm.

Range: N/A

Default: HSSServer.Spirent.com

• Realm — The Diameter Realm serviced by the HSS SUT, which is used to provision the Destination-Realm AVP. This equates to an MN's Home Realm when the Client node is emulating a NAS.

Range: N/A

Default: Spirent.com

• Port — Enter the port used by the HSS SUT for traffic.

Select to indicate that SCTP endpoint is multi-homed, where more than one destination transport address is used to reach the endpoint.

HSS-IMS I/F SUT Cx

Available only when HSS-Cx I/F (Cx)  Interface is selected on the HSS Nodal Test Configuration tab.

• Host — A Diameter server SUT's FQDN, which is used to provision the Destination-Host AVP in messages sent by the node. The presence of a Destination-Host AVP indicates that a request should be serviced by a specific Diameter server rather than any Diameter server in the destination Realm.

Range: N/A

Default: HSSServer.Spirent.com

• Realm — The Diameter Realm serviced by the HSS SUT, which is used to provision the Destination-Realm AVP. This equates to an MN's Home Realm when the Client node is emulating a NAS.

Range: N/A

Default: Spirent.com

• Port — Enter the port used by the HSS SUT for traffic.

HSS-Cx   Multi_Homed

EIR SUT

Select to indicate that SCTP endpoint is multi-homed, where more than one destination transport address is used to reach the endpoint.

Available when you select SBC I/F (SBc) on the HSS Nodal Test Configuration tab. Select SUT.

Port - Enter the port used by the CBS SUT for traffic.

Select to indicate that SCTP endpoint is multi-homed, where more than one destination transport address is used to reach the endpoint.

Available when you select LDAP I/F (Ud) on the HSS Nodal Test Configuration tab. Select SUT.

Port - Enter the port used by the LDAP SUT for traffic.

Default: 389

Select the AF SUT (PCRF) for the Rx interface for VolTE testing.

SUT Port Number

The port number used for the Rx interface on the PCRF SUT.

Range: 0 - 655535

Default: 3868

Tcl Parameter: TcCInSutPort

Select a SUT from the  list.

The  Multiple Links per SUT parameters is available only when the in Test Activity is Capacity, Inter-MME Mobility, Command Mode when handoff protocol = None or Session Loading Test in MME Nodal test case. Available in the AMF Nodal and gNB CU SA Nodal when Test Activity = Inter Technology Mobility or Command Mode / Sequencer with Handoff protocol = LTE. 

• Number of SUTs is the # of MME SUTS to be configured. Number of MME SUTs is the # of MME SUTS to be configured in AMF nodal test case.

• If both Number of SUTs and Multiple SUTs per eNodeB are selected, then each eNodeB will have multiple MME SUTs as defined by the Number of SUTs.

• If Number of SUTs is selected and Multiple SUTs per eNodeB is not selected, then the Number of MME SUTs will be round robin-ed on eNodeBs. Each eNodeB will have a single MME SUT. 

• When Multiple SUTs per eNodeB is selected, Random Route Selection becomes available to randomize the MME selection from the pool.

• Select Number of SUTs to enable testing of multiple eNodeBs per multiple MME SUTs (maximum of 30). Select Number of SUTs to enable testing of multiple MMEs per multiple MME SUTs when S1-Flex (MME Pooling) is enabled (maximum of 30).

• Select Multiple Links Per SUT to enable testing of multiple links between per eNodeB and per MME.

Range: 2 - 30

Default: 2

• Select Specify MME SUTs to specify SUTs in different rows from the list. Available when Number of SUTs is selected.

• Use Increment Destination Port to automatically increment the destination port for multiple links between per eNodeB and per MME. This checkbox is available only when you select the Multiple Links Per SUT checkbox.

Tcl Parameters:

Indicates the MME pool capability. The weight factor format is number1#number2, for example, 1#1, 10#4. This means that the weight factor on first link is the "number1" and the second is "number1+1*number2", 3rd is "number1+2*number2", and so on.

If you wish to allocate the same Weight Factor on all the links you can set it as "number1#0".

Default: 1#0 (Maximum of 6 characters)

Tcl Parameter: MmeCapabilityEn

Tcl Parameter: MmeCapability

Select to indicate that SCTP endpoint is multi-homed, where more than one destination transport address is used to reach the endpoint. Added support for MME Pooling by allowing Multi-Homed selection when Multiple SUTs per eNodeB is enabled and S1-Flex (MME Pooling) is not enabled .

Multi-Home-Dynamic is available only when you select Multi-Homed. Select to allow the secondary IP (dynamically learned during association) and the MME to use the secondary (not respond to the primary after association is established).

(See RFC 4960 Sections 3.3.3 Sending additional IP in INIT-ACK and 8.3 Path Management using HEART-BEAT).

Tcl Parameter: EnbSctpMultiHomedEn

Tcl Parameter: EnbSctpMultiHomeDynamicEn

• When you select Multi-Home-Dynamic, the Secondary MME SUT is not available.
• If the test activity is Inter-MME Mobility and S10 Interface to MME is not selected on the Test Configuration tab, the Target Secondary MME SUT is disabled.

Secondary MMEs becomes available when you select Multi-Homed and you may specify the secondary address for the corresponding MME SUTs.

Secondary MMEs is not available when you select Multi-Home-Dynamic.

Secondary MMEs is now available in a table format:

The primary path that carries traffic switches to a secondary path for carrying traffic when a fault is detected, and switches back to the primary path, after it is restored or if the secondary path becomes faulty. (See RFC-4960)

From Pool

Primary Pool

Secondary Pool

The "From Pool" checkbox option is enabled when multiple SUTs are being specified in the table and TAS has at least one SUT Pool configured via Admin - About Systems Under Test Pools. When "From Pool" is checked, the table is not editable by the user but becomes updated based on the selected Primary/Secondary pool. The SUT Pool must contain the number of SUTs the table is configured for or else the test case cannot get past the OK validation.

When SUT Pool is enabled, a SutPool class parameter is defined in the Test Case and the user must select a SUT Pool from the TAS. The Test Case GUI and API/Upgrade validation will automatically fill out the actual Sut class parameters based on the pool. SUT Pools act like an auto-fill wizard each time you reopen a Test Session. If the Test Session is exported, the SutPool parameter as well as the last filled out Sut parameters will be included. When the Test Session is imported to a different TAS that does not support SUT Pools or does not have the same named SUT Pool, the SUT Pool will be disabled and it will revert to just the last list of SUTs. If the SUT Pool name is valid for the same or different TAS but the pool configuration contains different SUTs, the session file will be updated based on the current SUT Pool configuration. For any case, the SUT Pool selected must contain at least as many SUT entries as required by the test configuration.

From the APIs, the SUT list is only automatically filled out when Validation occurs. The user could fill out the SUT list themselves, but once saved or executed by the TAS, the TAS validation will replace their list with reloaded list from the defined SUT Pool. In general API users that use SUT Pools should just deal with the SutPool parameters and let TAS do the job of filling out the SUTs.

Also available for the Target MME SUT.

Tcl Parameter: MmeSutPoolEn

Tcl Parameter: MmeSutPool

Tcl Parameter: MobMmeSutPoolEn

Tcl Parameter: MobMmeSutPool

When you select Inter-MME as the Test Activity, the Target MME becomes available. Available on AMF Nodal test case when Test Activity = Command Mode or Sequencer and Mobile Subscribers/EPS/Enable Target eNodeB is selected.

Select a Target MME SUT from the list.

Target SEC MME is available when you select test activity as Inter-MME Mobility on the Test Configuration tab and Multi-Homed and is not available when you select Multi-Home-Dynamic.

• If both Number of SUTs and Multiple Target SUTs per eNodeB are selected, then each eNodeB will have multiple MME SUTs as defined by the Number of SUTs.

• If Number of SUTs is selected and Multiple Target SUTs per eNodeB is not selected, then the Number of MME SUTs will be round robin-ed on eNodeBs. Each eNodeB will have a single MME SUT.

• Select Specify MME SUTs to specify SUTs in different rows from the list. Available when Number of SUTs is selected.

Range : 2 to 30

Tcl Parameter: MobEnbNumSutsEn

Tcl Parameter: MobMultiSutsPerEnbEn

Tcl Parameter: MobEnbSutTableEn

When you select Inter Technology Mobility as the Test Activity and GPRS as the UMTS Protocol, the Target SGSN and Port becomes available. Select a SUT from the  list and enter the appropriate port.

Select a SUT from the  list for the MME handoff, which is available only when Test Activity is Inter Technology Mobility and the Gn Interface to MME checkbox is selected on the MME Nodal Test Configuration tab. Available on MME Node test case.

Available on MME Node test case.

Tcl Parameter: PdnGwSut

Select a SUT from the list for the MME handoff, which is available only when:

• Test Activity is Inter Technology Mobility and Gn Interface to MME is selected on the MME Nodal Test Configuration tab OR

• Test Activity is Inter-MME and S10 Interface to MME is selected on the MME Nodal Test Configuration tab.

• MME-S10 is available in MME Node test case when you select S10 Interface to MME on the MME Node Emulator Configuration tab.

Select a SUT from the list for the MME handoff, which is available when Test Activity is Inter-MME and S10 Interface to MME is selected and on the MME Nodal Test Configuration tab (SGW/PGW Node Emulation is not selected)

Select a SUT from the  list for the MME handoff, which is available only when Test Activity is Inter Technology Mobility and Handoff Protocol is eHRPD (The S2A interfaces the HSGW Node and PGW).

Select a SUT from the list for the MME handoff, which is available only when Test Activity is Command Mode, Sequencer, Handoff Protocol is eHRPD and Optimized handoff is selected (The S101 interfaces the ePcf Node and MME).

Select a SUT from the list for the MME handoff, which is available only when Test Activity is Inter Technology Mobility and the Optimized Handoff checkbox is selected on the MME Nodal Test Configuration tab.

In MME Nodal, available when you select S3 Interface to MME on the Test Configuration tab.

In MME Node, available when you select S3 Interface to SGSN on the MME Node Emulator Configuration tab.

SGW FQDN IE is added in the Context Request message from the emulated MME Node.

SGW Node name is included in the Forward Relocation Request sent by the Target MME to the MME over the S10 Interface.

Select the SUT for MME Sv Handoff, which is available when you select Sv Interface on the MME Nodal Test Configuration tab.

ENB-X2

Available in MME Nodal Test Case when Test Activity is Intra-MME Mobility, Handoff Type is X2, and you select X2 Interface on the MME Nodal Test Configuration tab.

• Multi-Homed: Select to indicate that SCTP endpoint is multi-homed, where more than one destination transport address is used to reach the endpoint.
• Secondary ENB-X2: Available when you select Multi-Home.

Target HSGW

Available (in MME Nodal TC) when you select LMA Node Emulation on MME Nodal Test Configuration.

PGW S2b

PCRF AF

HSS

PtP Tunnel

AAA

Contains the AAA SUT panel.

• Available when SWm interface is enabled (AAA - Diameter ). Must enable ePDG Node Emulation and have Command mode and WiFi Offload Gateway license in order to enable SWm Interface.
• Available when Test Activity = Inter Technology Mobility, Handoff Protocol = WiFi and UE Authentication <> None.

AP/BSF

Contains the NAF and BSF SUT panel.

• Available when Ut/Ub is enabled.

NAF - SUT

BSF - SUT

ProSe Fn/BSF

Contains the ProSe Fn and BSF SUT panel.

• Available when PC3/PC8/Ub is enabled.

ProSe Fn - SUT

BSF - SUT

CMS

Contains the MC CMS panel. Available in MME Nodal, IP Application Node, PGW Nodal, SGW Nodal and Wifi Offload Gateway Nodal.

• Available when CSC-4 to Mission Critical CMS Interface is enabled.

MC CMS  - SUT

MME Node

Select a SUT from the  list.

Available when N26 Interface is enabled on MME Node emulator cnfg.

Enter the PGW Node Name, otherwise it will cause N26 handover failure.

Up to 127 characters.

Tcl Parameter: PgwNodeName

Available when you select Handover Protocol UMTS (IuCS over IP) on the Emulator Configuration tab. In addition, a Target MSC Control and Target MSC User Nodes sub tabs and the Target Iu-CS Interface tab is available for configuration.

Available when you select Sv interface on the Emulator Configuration tab. In addition, a MME Sv Node sub tab and the Sv Interface tab is available for configuration.

Available when you select SGd interface on the Emulator Configuration tab. In addition, a MME SGd Node sub tab and the SGd Interface tab is available for configuration. Enter Port, Host and Realm.

Available when you select SGs Interface on the Emulator Configuration tab. In addition, a MME SGs Node sub tab and the SGs Interface tab is available for configuration.

Select Multiple MSC SUTs to enable testing of multiple MSCs per multiple MME SUTs (maximum of 10).

Table with two columns is enabled: # and Multiple MSC Node SUTs

Range: 2 to 10 (1 is the Original MSC Node SUT)

Default :2

Tcl Parameter: MscNodeNumSutsEn

Tcl Parameter: MscNodeNumSuts

Available when you select APN DNS Lookup on the Emulator Configuration tab. Used to support NAPTR Queries for APN.

Select DNS Topo selection mode = topoff or topon and Enter DNS Server Address.

Available when you select LCS Support on the Emulator Configuration tab. Used to support the EPC Location services between E-SMLC and MME.

Available when you select Slg Interface on the Emulator Configuration tab. Used to support the EPC Location services between GMLC and MME.

Access Stratum

Available when you select SGi PtP Tunnelling Support on the MME Node Emulator Configuration tab. Per TS 29.061 section 11.8.2.

Available when you select T6a Interface on the Emulator Configuration tab. Used to support the T6a Interface to SCEF. Additional information on T6a Interface in About SCEF Testing.

Enter Host, Realm and Port.

Tcl Parameter: ScefSut

Tcl Parameter: ScefSutHost

Tcl Parameter: ScefSutRealm

Tcl Parameter: ScefSutPort

Available when you select SBc Interface on the Emulator Configuration tab. Used to support the SBc Interface to CBC.

Enter Port. Default = 29168

Tcl Parameter: CbcSut

Tcl Parameter: CbcSutPort

Available when you select N26 Interface on the Emulator Configuration tab. N26 provides a reference point between Access and Mobility Management function (AMF) and the Mobility Management Entity function (MME).

Choose a SUT

Tcl Parameter: AmfN26Sut

Available when you select N2 to AMF on the N3IWF Node Emulator Configuration tab. N2 Provides a reference point between the (R) AN and the Access and Mobility Management function (AMF) for Non-3GPP InterWorking to route messages outside of 5G RAN.

Choose a SUT

Tcl Parameter: N2UserSut

Available when you select N3 to UMF on the N3IWF Node Emulator Configuration tab. N3 Provides a reference point between the (R) AN and the User Plane function (UPF) for Non-3GPP InterWorking to route messages outside of 5G RAN.

Choose a SUT

Tcl Parameter: N3UserSut

Select the OFCS Server (OCFS) for the Rf interface.

SUT Port Number

The port number used for the Rf interface on the OFCS SUT.

Range: 0 - 655535

Default: 3868

Tcl Parameter: OfcsSutPort

Enter the PMIPv6 Destination Address for LMA SUT. This parameter is available and is required for PMIPv6 with IPv4 transport.

Tcl Parameter: LmaDestAddr

Enter Mapped IPv4 Address and IPv6 Address.

• When PMIPv6 transport for S2a Protocol is set to IPV4 (on the Test Configuration tab) and PMIPv6 version >= 9.7.0 (on the PMIPv6 tab), PMIP Source  Address (both IPv6 and mapped IPv4) are not available.

• When PMIPv6 transport for GTPv2 Protocol is set to IPV4 (on the Test Configuration tab) and PMIPv6 version >= 9.7.0 (on the PMIPv6 tab), PMIP Source  Address (both IPv6 and mapped IPv4) are not available.

Select Map APNs to PGWs to specify a PGW address per APN.

Number of APNs Mapped to PGW: Slect from the list of click + to added a tabbed panel and configure PGW and map an APN. The number APN-PGW mapping tab(labeled PGW 1 ...PGW 10) depends of the value you select from the list/number of time you click + to add a tabbed panel. You may add a maximum of 10 APN-PGW map.

Tcl parameter: NumApnToPgw

Select the SUT distribution method used to identify and utilize SUTs for testing Offline Charging.

• Dedicated
• Round Robin

Tcl Parameters:

Set the HA SUT to which a mobile router connects. Available when you select NEMO Emulation on the PGW Nodal Test Configuration tab.

Multiple HA SUTs

Select to support connection to multiple SUTs and enter a value to indication the number of SUTs (2 to 1024).

Uses round-robin method to assign the UEs to different SUTs by default.

Select a SUT from the  list, available when the NEMO Tunnel Mode = Pi-MIP on the PGW Nodal Test Configuration tab.

Set the NEMO HA SUT to which a mobile router connects. Available when you select NEMO Emulation on the PGW Nodal Test Configuration tab.

Multiple NEMO HA SUTs

Select to support connection to multiple SUTs and enter a value to indication the number of SUTs (2 to 1024).

Uses round-robin method to assign the UEs to different SUTs by default.

Select a SUT from the  list, available when the NEMO Tunnel Mode = PMIPv6 on the PGW Nodal Test Configuration tab.

Enter the PMIPv6 DesT Address for LMA SUT. Use Mapped IPv4 Address or Enter IPv6 Address.

Tcl Parameter: NemoLmaDestAddr

Available when you select VOLTE on the PGW Nodal Test Configuration tab and Enable Rx on VoLTE | IMS Node pane when IMS Node Type is Local. Select the SUT and enter the Host, Realm, and Port addresses.

Contains the MC CMS panel. Available in MME Nodal, IP Application Node, PGW Nodal, SGW Nodal and Wifi Offload Gateway Nodal.

• Available when CSC-4 to Mission Critical CMS Interface is enabled.

MC CMS  - SUT. Enter SUT IP Address, Host, Realm and Port.

Available when Mobility is Inter-Technology, Initial Network is UMTS and UMTS Version is 7. Select a SUT from the  list for the PDN Gateway's Control Node address.

V1 Control Port/V1 User Port: Indicates the SGSN Control and user port used to connect the SUT.

See TS 23.214 for Architecture enhancements for Control and User plane separation of EPC Nodes.

See TS 29.244 for Interface specifications between the Control plane and User plane of EPC Nodes.

See TS 23.214 for Architecture enhancements for Control and User plane separation of EPC Nodes.

See TS 29.244 for Interface specifications between the Control plane and User plane of EPC Nodes.

Available in PGW Node test case when you select Gx Interface on the PGW Node Emulator Configuration tab. Select the a AGW SUT from the selection list and enter the Host, Realm and Port IDs for the SUTs.

Select Secondary PCRF AGW for Failover simulation for the Gx Interface. The Failover Simulation pane becomes available on the Diameter Tab for Failover scenarios.

Select a Secondary PCRF AGW SUT from the selection list and enter the Host and Realm Secondary PCRF AGW SUT.

Used by the Mm/SIP interface is between PSAP and SUT (Interconnect Border Control Function (IBCF) ); PSAP receives emergency calls on this interface and is responsible for processing those calls.    

Select SUT Address and Port Number (Default = 5060 or 5061 when TLS is enabled)

Tcl Parameter : IbcfSut

Tcl Parameter : IbcfSutPort

Available when Le interface is enabled on PSAP Node Emulator Cnfg, its between PSAP and SUT ( Gateway Mobile Location Centre (GMLC) Le ).  PSAP uses this interface for querying intermediate/final location of mobile subscriber.

Enter GMLC SUT, Host, Realm and Port.

Tcl Parameter: GmlcSut

Tcl Parameter: GmlcSutHost

Tcl Parameter: GmlcSutRealm

Tcl Parameter: GmlcSutPort

Available when E2 interface is enabled on PSAP Node Emulator Cnfg, its between PSAP and SUT ( Gateway Mobile Location Centre (GMLC) E2 ).  PSAP uses this interface for querying location on E2 - Emergency Services Protocol (ESP).

Enter GMLC SUT E2, and Port (default = 7001).

Tcl Parameter: GmlcE2Sut

Tcl Parameter: GmlcE2SutPort

The SUT Near-RT RIC A1 becomes available when Non-RT is enabled on the RIC Node Emulator Configuration test case. 

The SUT Near-RT RIC E2 Node becomes available on the RIC Nodal Test Configuration test case when E2 interface is enabled.

Select the SUT for the: Near-RT RIC E2 Node.

Tcl parameter: NearRtRicE2Sut

The SUT Non-RT RIC O1 HTTP becomes available on the RIC Nodal Test Configuration test case when O1 interface is enabled.

Available on the RIC Nodal Test Configuration test case when E2 interface is enabled.

Select the gNB Ran Configuration.

Options : 

0 (Standalone CU-CP, CU-UP and DU)

1 (Combined CU-CP/CU-UP, Standalone DU)

2 (Combined CU-CP/CU-UP/DU)

When the value is 0, Tab "gNB-CU-UP" and Tab "gNB-DU" are undimmed.

When the value is 1, and GnbE2Interface is 0, Tab "gNB-CU-UP"is dimmed, Tabe "gNB-DU" is undimmed.

When the value is 2, and GnbE2Interface is 0, Tab "gNB-CU-UP" and Tab "gNB-DU" are all dimmed.

Tcl parameter: GnbRanConfig

Available on the RIC Nodal Test Configuration test case when gNB Ran Configuration is Combined CU-CP/CU-UP, Standalone DU or Combined CU-CP/CU-UP/DU. 

Options : Individual or Shared

Tcl parameter: GnbE2Interface

Available only when HSS/MME/SGSN (S6t, T6a or T6b)  Interface is selected on the SCEF Node Emulator Configuration tab.

• Host — A Diameter server SUT's FQDN, which is used to provision the Destination-Host AVP in messages sent by the node. The presence of a Destination-Host AVP indicates that a request should be serviced by a specific Diameter server rather than any Diameter server in the destination Realm.

Range: N/A

Default: HSSServer.Spirent.com

Default: MME.Spirent.com

Default: SGSN.Spirent.com

• Realm — The Diameter Realm serviced by the HSS/MME/SGSN SUT, which is used to provision the Destination-Realm AVP.

Range: N/A

Default: Spirent.com

• Port — Enter the port used by the HSS/MME/SGSN SUT for traffic.

Default: 3868

The SUT UDM SBI becomes available when Test UDM (Nudm), From AMF (N8), From SMF (N10) and From AUSF (N13) are selected on Service Based Nodal Test Configuration.

The SUT UDM SBI becomes available when ( AUSF (Nausf) To UDM (N13m) or SMSF (Nsmsf), To UDM (N21)) are selected on Service Based Node Test Configuration.

The SUT UDM SBI becomes available when UDM (N8)  interface is enabled on SMF Nodal test Configuration.

The SUT UDM SBI becomes available when UDM (N8)  interface is enabled on AMF Node Emulator Configuration.

The SUT UDM SBI becomes available when N10 Interface interface is enabled on SMF Node Emulator Configuration.

Target UDM SBI becomes available when Test UDM (Nudm), From AMF (N8), and 

Roaming Scenario with SEPP with H-AMF are enabled in Service Based Nodal TC. The TCL variables below start with "h".

The SUT AUSF SBI becomes available when Test AUSF (Nausf) , From AMF (N12), and Emulate UDM (N13) are selected on Service Based Nodal Test Configuration.

The SUT AUSF SBI becomes available when N12  interface is enabled on AMF Node Emulator Configuration.

Target AUSF SBI becomes available when Test AUSF (Nausf) , From AMF (N12), and Roaming Scenario with SEPP with H-AMF are enabled in Service Based Nodal TC. The TCL variables below start with "h".

The SUT PCF SBI becomes available when Test PCF (Npcf), From AMF (N15), and From SMF (N7) are selected on Service Based Nodal Test Configuration and when NEF (Nnef) and To BSF/PCF (Nbsf/N30) or To H-PCF (N24) is enabled on Service Based Node Emulator Configuration.

Available on IMS Node test case when N5 Interface is enabled.

The SUT NSSF SBI becomes available when Test NSSF (Nnssf), From AMF (N22)are selected on Service Based Nodal Test Configuration. The SUT becomes available when N22 interface is enabled on AMF Node Emulator Configuration.

The SUT CHF SBI becomes available when Test CHF (Nchf), From SMF (N40) or From PCF (N28)are selected on Service Based Nodal Test Configuration. Available on SMF Node Emulator Configuration when N40 Interface is enabled.

The SUT NEF SBI becomes available when Test NEF (Nnef), Emulate AMF (N51) or Emulate SMF (N29) or Emulate UDM (N52) or From AF (N33)are selected on Service Based Nodal Test Configuration.

The SUT LMF SBI becomes available when Test NLF (Nlmf), and / or From AMF (NLs) are selected on Service Based Nodal Test Configuration and when NLs Interface is enabled on AMF Node Emulator Configuration.

The SUT SLF SBI becomes available when Test SLF (Nudr), and / or From NRF are selected on Service Based Nodal Test Configuration.

The SUT UDR SBI becomes available when Test UDR (Nudr), and / or From UDM (N35) or From PCF (N36) or From NEF (N37) are selected on Service Based Nodal Test Configuration.

Available on Service Based Node test case when NEF (Nnef), To UDR (N37) or when 

PCF (Npcf) and To UDR (N36) are enabled.

The SUT SMSF SBI becomes available when Test SMSF (Nsmsf), and / or From AMF (N20) is selected on Service Based Nodal Test Configuration.

Also available on AMF Node test case when N20 Interface is enabled.

The SUT NRF SBI becomes available when NRF Interface is selected on Service Based Nodal Test Configuration and on  Service Based Node Emulator Configuration.   The SUT NRF SBI becomes available when NRF Interface is selected on SMF Nodal / SMF Node test case. The SUT NRF SBI becomes available when NRF Interface is selected on AMF Node test case.   The SUT NRF SBI becomes available when NRF Interface is selected on AMF Nodal test case. The SUT NRF SBI becomes available when PCRF Interface - Nnrf is selected on DRA Nodal Test case.   The SUT NRF SBI becomes available when NRF Interface on HSS Node Emulator Cnfg.

Target AUSF SBI becomes available when NRF Interface and Roaming Scenario with SEPP with H-AMF are enabled in Service Based Nodal TC. The TCL variables below start with "h".

Available in Service Based Nodal / Service Based Node and SMF Nodal / SMF Node test cases when Indirect Communication is enabled.

Target SCP becomes available when Indirect Communication and Roaming Scenario with SEPP with H-AMF are enabled in Service Based Nodal TC. The TCL variables below start with "h".

The SUT BSF SBI becomes available when Test BSF (Nbsf), and / or From PCF / From AF  Service Based Nodal Test Configuration and on DRA Nodal when PCRF Interface - Nbsf is selected and when NEF (Nnef) and To BSF/PCF (Nbsf/N30) is enabled on Service Based Node Emulator Configuration.

The SUT SMS-SC becomes available and when NEF (Nnef) and To SMS-SC (T4) is enabled on Service Based Node Emulator Configuration.

The SUT EIR SBI becomes available when Test 5G-EIR (N5g-eir), and / or From AMF (N17) is enabled on Service Based Nodal Test Configuration.

The SUT SEPP N32-c SBI becomes available when SEPP is enabled on  Service Based Node Emulator Configuration.

The SUT CAPIF-3/4/5 becomes available when NEF (Nnef) and To CAPIF-3/4/5 are enabled on Service Based Node Emulator Configuration.

The SUT SEPP N32-f SBI becomes available when SEPP is enabled on  Service Based Node Emulator Configuration.

The SUT SEPP to NF becomes available when Roaming Scenario with SEPP  is enabled on Service Based Nodal Test Cnfg / Service Based Node and SMF Node and AMF Node test cases.

The SUT NWDAF SBI becomes available when Test NWDAF (Nnwdaf) and / or From AMF or From SMF is enabled on Service Based Nodal Test Configuration.

DNS Pane allows for capture of DNS Server details. 

It’s not necessary to set both fields SUT and Host in the SUT tables listed above. But you must set at least one of them. The SUT field is used to set IP address, if it’s not set, we will use hostname in the field Host to start DNS query procedure when starting the test.

Enter DNS Server Address. Enter a valid IPv4 or IPv6 address. 

Default :  1.1.1.1

Enter DNS Response Wait Time (s).

Range: 1 to 65535

Default: 5

Tcl parameter: DnsSbiSrvAddr

Tcl parameter: DnsSbiResWaitTime

The SUT SMF SBI is available on the SMF Nodal Test Configuration.

When SMF Emulation is disabled, the SMF SBI SUT and the N11 Interface toward SMF becomes available for testing on AMF Node Emulator Configuration.

The SUT SMF SBI is available when From V-SMF (N16) is enabled on the Service Based Nodal Test Configuration tab. 

The SUT AMF SBI is available when To SMF (N29) is enabled on the Service Based Node Emulator Configuration tab. N29 interface provides a reference point between the Network Exposure Function (NEF) and the Session Management functions (SMF).