UBMobile Subscribers

Mobile Subscribers

• Number of Subscribers/Mobile Nodes

• Number of Primary PDP Contexts

• Number of Secondary PDP Contexts

• • Support Release 7 TFTs

• Number of Subscribers per Femtocell

• Default Bearer per Session

• Dedicated Bearer per Default

• Report Within Default Session

• Number of Low Priority Subscribers

• Use Real SIM Card (One Subscriber)

• Use SIM Server

• Command (Button)

• Dedicated Bearer Rates and Delay

• UE Initiates LTE Deactivation with Message

• Disconnect Initiated by PGW

• Disconnect Dedicated Bearers After Connected

• Mobile Subscribers per BS

• Home Address Type

• Bearer IPv6 Address Pool

• Bearer IPv4 Address Pool

• UE DHCPV4 IP Address

  • MAC Address

• Aux Svc Instance per Mobile Subscriber

• • Auto-Generated TFT Settings

• Attach Start Delay

• Attach Rate

• Detach Rate

• GMM Attach Start Delay

• GMM Detach Start Delay

• Activation Rate

• Deactivation Rate

• Activation Delay

• PDN Connect and PDN Activation Rate (LTE, PCRF)

• PDN Failed Threshold (%)

• Starting IP Address

• Increment IP Address per Default Bearer

• Starting PDP Context IP

• Starting Private Address (VPN)

• Starting Home Address

• Starting Ipv6 Home Address

• Starting IPv4 Home Address

PGW Node (Overload Control)

Enable Overload Control

• APN Level Overload Control

• Update Granularity

• Validity Period

• Starting Sequence Number

AMF Nodal / AMF Node / SMF Nodal / SMF Node / UPF Nodal

• Number of PDUs

AMF Nodal

• Start PDU Delay (After Registrered) (ms)

• Start PDU Delay (After Prev-PDU) (ms)

• Registration Failed Threshold (%)

• Reserve PDU Session for SSC Mode 3

• Enable Target eNodeB

SMF Nodal

• Enable Target SGW Node

• PDU Failed Threshold (%)

UE Node

• LTE U1 DHCP Delay (s)

Service Based Nodal/Node

• Transaction Count

• Starting SUPI (+=)

• Starting GPSI

• MCC

• MNC

• External ID

  • Starting Local Identifier

  • Domain Identifier

N3IWF Node

• Number of Access Points

RIC Node

• Number of Cells

CDMA Voice Nodal

• Key Pair

LCS Node

• ESRK

• Dynamic Home Address Pool

• Use Static Home Address

• Co-Located Care of Address

• NAT Traversal

• Default Routing/Next Hop IP Address

• Dynamic HA

• Agent Discovery

• Advanced Settings

• Distribution Settings (HNB GW, MME, PGW, SGW Nodal, WiFi Offload TCs)

• Include MS ISDN

• Include IMSI

• ESN

• Starting Value

• Upstream QCI to DSCP Markings

• QCI Settings

• Control Bearer to DSCP Assignments

• DSCP Settings

• Call Establishment Pattern

• Call Clearing Pattern

• Number of BSCs

MS Sub-Tabs

• Mode

• Receive Only

• Initiate Intra-BS Call Call MS

• Initiate External Call

• Hold Time

• Idle Time

AAA Server Node

• Number of Authentication Sessions
• Number of Accounting Sessions
• Deactivation rate (Sessions/Sec)
• DSCP Value (Available in DRA Nodal/Node, IMS Node, OCS Node)

MS Ethernet Configuration

• CDMA/Wifi Convergence

MBMS Bearers (eMBMS Node and Nodal)

WiFi Offload Gateway Settings

UE Random MAC Address

MAC Address Increment

UE Next Hop MAC Address

UE Next Hop IP Address

Assigned IPv4

Assigned IPv6

UE Static IPv4/IPv6

UE DHCPv4

UE DHCPv4/6 via Tunnel

UE SLAAC

Random Address Number

UE Duplicate Address Detection

Neighbor Advertisement Delay (ms)

UE Graceful Shutdown

UE Graceful Mobility

External DHCP Client

UE Authentication

UE Mobility Reauthentication

UE Responds to ARP

UE Routes Data to AP Next Hop

Outer IP Type of Service

UE SWu IPv4 Address

Non-3GPP Access with a 5G Capable UE

Starting PDU Session ID

Maintain UE IP after Handover ( MME Nodal )

Send Router Solicitation after Handoff (AMF Nodal, MME Nodal)

SMS Terminating

• Number of Recipients
• Starting Recipient MSISDN
• Starting Recipient IMSI

SMS Originating

• Number of Subscribers
• Starting Target MSISDN

SMS Source

• Starting SMS Delay (s)
• Enable IWF
• MAP Operation
• Delay for ReadyForSM (ms)

In every test case, you can define activation and deactivation rates for the MS sessions. In the UMTS test case, you can also define rates for GMM attaches and detaches.

Range: Variable1

Default: 1

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

The rate at which the test attempts to activate MN/MS sessions. In tests where the MN/MS establishes a control session with the MN/MS servicing or authorization node, such as an FA, HA, AAA server, SGSN, etc., this rate is the number of MNs/MS that will attempt to establish control sessions every second. When the control plane is not used, this rate is the number of MNs/MS that will begin generating traffic every second.

Tcl Parameter:

AAA Testing

During AAA testing, Activation Rate is the rate at which the test attempts to activate MN/MS sessions. In tests where the MN/MS establishes a control session with the MN/MS servicing or authorization node, such as an FA, HA, AAA server, SGSN, etc., this rate is the number of MNs/MS that will attempt to establish control sessions every second. When the control plane is not used, this rate is the number of MNs/MS that will begin generating traffic every second.

Tcl Parameter:

In AAA Testing, if digital certificates are used with EAP-TLS authentication, the maximum Activation Rate is limited to 1000 sessions/second or the licensed throughput, whichever is lower.

Related Measurements

• Attempted Connect Rate

• Actual Connect Rate

• Attempted PDP Activation Rate (UMTS)

• Actual PDP Activation Rate (UMTS)

UMTS Testing

When PDP contexts are included in a UMTS test, you can define a delay between the attach time and the start of context activation with PDP Context Activate Delay on the MN tab. MNs will attempt to establish contexts at the PDP Activation Rate after successfully attaching to the SGSN SUT. If the SUT cannot process the attaches at the attempted Attach Rate, the defined activation rate may not be achievable. The defined activation rate will not be achievable if it is faster than the attach rate and each MN is only activating one PDP context. In this case, the attach rate becomes the effective activation rate. MNs must activate multiple contexts in order for the activation rate to exceed the attach rate.

Tcl Parameter:

Related Measurements

• Attempted Disconnect Rate

• Actual Disconnect Rate

• Attempted PDP Deactivation Rate (UMTS)

• Actual PDP Deactivation Rate (UMTS)

During AAA testing, the deactivation rate is the rate at which the test attempts to deactivate Diameter sessions, either with an ASR message or by responding to an STR.

• Learn more about MN session management

Range: 0.0010 — Variable1

Default: 1

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 Parameters: DisconnectRate

Related Measurements

• Attempted Disconnect Rate

• Actual Disconnect Rate

The number of milliseconds that the test will wait, after all GTP links are established, before beginning to perform MME attaches for the ENodeB (testing MME Nodal with SGW/PGW emulation, Emulate Srv GW and PDN GW option is selected on the Test Configuration tab)

Range: 0 - 65535

Tcl parameter: MnActivationDelay

CDMA Testing

See also Aux Svc Instances per Subscribers

The rate at which the test attempts to attach MNs/Subscribers to the SGSN SUT after all of the RNC links have been successfully established. You can introduce a delay between the completion of link establishment and the beginning of MN/Subscriber attaches with GMM Attach Start Delay on the MS tab.

Related Measurements

• Attempted Mobile Node Connect Rate

• Actual Mobile Node Connect Rate

Detach Rate

The rate at which the test attempts to detach MNs from the SGSN SUT. When PDP contexts are included in the test, the test will attempt to detach MNs/Subscribers at the rate defined, however a detach cannot occur until all of the MN's/Subscriber's PDP contexts have been deactivated. If the PDP Deactivation Rate is slower than the Detach Rate, the deactivation rate will be used for the detach rate.

Related Measurements

• Attempted Mobile Node Detach Rate

• Actual Mobile Node Detach Rate

Use the drop-down list to select the number of primary PDP contexts to be established for each mobile subscriber.

Tcl Parameter: PrimPdpContextsPerMs

Use the drop-down list to select the number of secondary contexts to create for each primary context. Select 0 to disable secondary contexts.

Tcl Parameter: SecPdpContextsPerPrime

In GGSN and UMTS Nodal testing, the Support Release 7 TFTs checkbox is available only when the Number of Secondary PDP Contexts per Primary is > 0. Select the Support Release 7 TFTs checkbox to indicate custom TFT Filter direction and multiple TFT's per context.

Option: True(1)/False (0)

Default: False

Tcl Parameter: Rel7TftSupportEn

The number of milliseconds that the test will wait, after an MN has successfully attached, before beginning to activate the MN's PDP contexts. When you define a delay time and clear the Follow On checkbox, the SGSN may perform an Iu Release due to inactivity. If the connection is released, the MN will send a Service Request to restore the connection before attempting to activate PDP contexts.

The number of unique mobile subscribers (MSs) emulated during the test. At least one MS must be emulated in every test. It is also the number of simultaneous MS that can be supported by the server node. System resources are reserved for the provisioned number of sessions whether they are used or not.

Range: Variable1

Default: 1

Tcl Parameter:  

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

AAA Testing

During AAA testing, the Number of Mobile Subscribers is the number of unique mobile subscribers (MSs) emulated during the test. At least one MS must be emulated in every test.

It is also the number of simultaneous MS that can be supported by the server node. System resources are reserved for the provisioned number of sessions whether they are used or not.

In DHCP Server Node test case, the Number of Mobile Subscribers indicate the number of simultaneous client bindings that can be supported by the server node. System resources are reserved for the provisioned number of sessions whether they are used or not.

Range: Variable1

Default: 1

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

GPRS/UMTS Testing

The total number of PDP contexts (MN sessions) that will be attempted during a test or supported by a GGSN node is the result of Number of Mobile Subscribers multiplied by the total number of PDP contexts per subscriber. When secondary PDP contexts are used, primary contexts + (primary contexts * secondary contexts) determines the total number of PDP contexts for each MN.

The number and type of PDP contexts are defined on the GTP tab in the GGSN Nodal test case and on the MN tab in the UMTS test case. In the GGSN Node test case, primary contexts are defined in the Mobile Node sub-tab and secondary contexts are defined in the GTP sub-tab (follow the GTP link above for definitions).

MSS ID

A Mobile Node is uniquely identified by its MAC address. Enter a starting address that will be incremented for each MN.

Range: Up to 12 hexadecimal characters (omit "0x")

Default: N/A

Authentication Type

Use the drop-down list to select the message authentication code that is used for all MNs.

Options: HMAC or CMAC

Default: HMAC

In UPF Node Test Case, the Number of Sessions means Sessions not mobile subscribers. One mobile can communicate with multiple UPF Nodes.

In the IP Impairment Node Test Case, IP Impairment Sessions are created for the sole purpose of providing the timing mechanism when delaying a packet. The number of “sessions” is really the maximum number of packets that can be simultaneously on the delay queue. Impairment sessions are created as part of the node configuration when the impairment test case is started. 

In UE Node or WiFi Offload Gateway Nodal with RF UEs enabled : The Maximum number of Subscribers is the minimum of either the licensed RF UEs or the # of supported sessions possible for the number WiFi Ports available.  

• Sessions Established

• Sessions Pending

• Attempted Session Connects

• Attempted Session Disconnects

• Actual Session Connects

• Actual Session Disconnects

Click Settings... to configure the EAP settings.

For EAP Type, use the drop-down list to select either Single or Double EAP.

Tcl Parameter: EapType

In AAA Server Node testing, The number of simultaneous RADIUS or Diameter authentication sessions that will supported by the node. This value should match the number of MS/MNs provisioned in the nodal test case. Unique user name values are provisioned according to the format used in User Name.

Range: Variable1

Default: 1

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

When digital certificates are used with EAP-TLS, the maximum number of sessions is limited to 100,000.

Tcl Parameters: Sessions

Related Measurements

• No Free Sessions

The number of simultaneous accounting sessions that will be supported by the node. This value should match the total number of connections that will be attempted by the nodal test case.

Range: Variable1

Default: 1

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

Related Measurements

• No Free Accounting Session Errors on the RADIUS tab or the Diameter Server Acct tab

Enter the number of PDU (Protocol Data Unit) sessions. Currently up to 15 are supported. In AMF Nodal, when Test Activity = Inter Technology Mobility and Handoff Protocol = WiFI only 2 PDUs are supported.

Tcl Parameter: NumPdu

Select to send the PDU request after this configurable time delay following UE registration.

Range : 100 to 100,000,000

Default : 1000

Parameter: StartPduDelayAfterRegEn

Parameter: StartPduDelayAfterReg

Select to send the PDU request after this configurable time delay following the previous PDU establishment. 

Default : 1000

Parameter: StartPduDelayAfterPrevEn

Parameter: StartPduDelayAfterPrev

Available in AMF Nodal test case.

If Test Activity is Capacity or Intra-AMF Mobility with "When All Sessions Started" checked or
Inter-AMF Mobility with "When All Sessions Started" checked or Intertech Mobility with Initial Network = 5GS and "When All Sessions Started" checked.

This field represents the maximum percentage of failed mobile registrations before any PDU Session Establishment attempt is allowed.

Range : 0 to 100

Default : 10

Tcl Parameter: RegFailedThresholdPercent

Select for support of Change of SSC mode 3 PDU Session Anchor with multiple PDU Sessions per 23.502 4.3.5.2. Currently this feature is only limited to AMF Nodal v.s. AMF Node with SMF Emulation in b2b setting. SMF relocation is not currently supported.

The "Reserve PDU Session for SSC Mode 3" option reserves a peer PDU session for each of the PDU provisioned by the Number of PDUs combo box. An additional PDU session is needed for the change of SSC Mode 3 PSA with multi PDU sessions because it's a make-n-break operation. Two PDU sessions are active during the transition. If you don't enable this option (i.e. no peer session) or the peer session is not free or the UE is running of PSIs when the PDU Session Modification Command is received from the SMF, the UE will reject PDU modification with cause "insufficient resources". If you provision 8 or more PDUs in the "Number of PDUs" field, the total number of PDUs including the peer sessions will go over 15. However, we have a guard internally so that the maximum active PDU sessions will not go over 15. The reason why we choose the peer session approach instead of dynamically link a free session during runtime is due to consideration of Command Mode/Sequencer where PDU sessions are indexed based.

This option is not supported for Inter-tech mobility, Command Mode or Sequencer.

Change of SSC Mode 2 or 3 PDU Session Anchor is not currently supported on standalone SMF node or with N11 interface enabled.

Call flow per 23.502 4.3.5.2.

Tcl Parameter: ResPduSessSscMode3En

Available when Test Activity = Command Mode / Sequencer and Handoff Protocol = LTE on AMF Nodal test case. 

When "Enable Target eNodeB" is checked, the Target MME SUT table and associated multi-set options on the MME SUT tab become available for input. Target eNB Control Node and Target eNB User Node test node tabs become available.

In Command Mode/Sequencer, when "Enable Target eNodeB" is checked, the eNB Control Node node count is added to the Target Nodes range for all relevant operations.

Note : If Cell IDs are not Random (starting value = 0), the values set for eNB Control Node Cell ID & Target eNB Cell ID need to be configured > 256 apart.

eNB Control Node               Cell ID = x

Target eNB Control Node     Cell ID = x + 256

Parameter: TargetEnbEn

Available in SMF Nodal test case when Test Activity is “Capacity” or “Intra-AMF Mobility” or “Inter-AMF Mobility” or “Inter Technology Mobility with Initial Network = 5GS.

It represents the maximum percentage of Failed PDU Session Establishment before the next step after starting PDUs is allowed.

SMF Nodal will check PDU Failed Threshold to decide whether to move TC state to the RUNNING state after it started all PDUs.

If multiple PDUs are configured, SMF Nodal may not start all PDUs. In this case,  configure T3580 (s) on Nas 5g SM with non-zero value (ex: 16s in specification) in accordance with the test condition to avoid waiting on the response.

Range : 1 to 100

Default : 10

Parameter: PduFailedThresholdPercentEn

Parameter: PduFailedThresholdPercent

Available when Test Activity = Command Mode / Sequencer and Handoff Protocol = LTE on SMF Nodal test case. 

Select to enable/disable the configuration of Target Sgw Node to allow 4G handover (between SGW and SGW) in Sequencer or Command Mode with Handoff Protocol = LTE in SMF Nodal Test Case.

When "Enable Target SGW Node" is checked, the Target S5 Bearer becomes available for input. Target SGW Control Node and Target SGW User Node test node tabs become available.

In Command Mode/Sequencer, when "Enable Target SGW Node" is checked, ODC Operations: “X2 Handover” or “S1 Handover” become available.

Note : The index range of Target SGW Nodes should be 1 ~ total # of (sgw nodes + target sgw nodes). For example, if # of sgw nodes is 2 and # of target sgw nodes is 2, The index, 1 ~ 2 is the index of sgw nodes and the index, 3 ~ 4 is the index of target sgw nodes.

Parameter: TargetSgwEn

Enter the number of iterations that the configured message flow will be executed. A value = 0 (zero) means continuous execution of the configured message flow. 

Range: 0 to 4294967295.

Tcl Parameter: SbiTransCount

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

In Service Based Nodal/Node test cases you will see "+=" with an input box. It is used to increment the SUPI by the given number that is entered.

Default is 1, Rnage : 1 to 255

Tcl Parameter: SupiIncStep 

Also available on HSS Node Emulation Cnfg when UDM (Nudm) is enabled.

Range: 14 or 15 digits

Tcl Parameter: StartingSupi

Enter the starting GPSI (General Public Subscription Identifier). Corresponds to MSISDN in earlier generations of networks.

Also available on HSS Node Emulation Cnfg when UDM (Nudm) is enabled.

Range: 15 digits

Tcl Parameter: StartingGpsi

Select to include IMEI. Enter the starting IMEI (International Mobile Equipment Identity).

Range: 14 digits

Enter the Software Version of the IMEI. Enter up to 2 digits.

Tcl Parameter: ImeiEn

Tcl Parameter: StartingImei

Tcl Parameter: ImeiSwVer

External ID

Starting Local Identifier

Domain Identifier

Select to include the External ID.

Enter the Starting Local Identifier.

Range : 1 to 15 digits, Default : 123456789

Enter the Domain Identifier.

Range : 1 to 128 characters, Default : domain.com

Tcl Parameter: ExtIdEn

Tcl Parameter: ExtIdLocalId

Tcl Parameter: ExtIdDomainId

Enter the number of Access Points. Range : 1 to 150000 Default : 1

Tcl Parameter: AccessPoints

Enter the number of Cells. Range : 1 to Licensed max value

Default : 1

Tcl Parameter: NumCells

• Select FA and the available Bootstrap Home Address, to set up attributes in the IKE message exchange to dynamically acquire the MN Home address.
• Select CCoA to ensure that the MNs registers the address obtained during IPSec SA negotiation as their co-located care-of addresses rather than the Local IP Address. You must also use the Request Private Address option in the IPSec tunnel definition if this option is selected.

Selecting the Bootstrap Home Address check box sets up attributes in the IKE message exchange to dynamically acquire the MN Home address when the MN HoA is not a static address.

When a PDSN-FA SUT is included in a test, you can test with multiple auxiliary service instances for each mobile node. When auxiliary services instances are used, all service instances share the same RP and PPP sessions. A separate RP connection is established between the PCF and PDSN-FA for each instance, requiring the PDSN-FA to maintain multiple service instance mappings for each MN and forward bearer plane traffic to the correct service instance. The main service instance is used for all control plane signalling, including PPP negotiation, and the auxiliary service instances are only used for bearer plane traffic. You can define a separate set of Active Start Airlink Parameters for each of the service instances and Traffic Flow Templates for the auxiliary service instances.

When the test case emulates the node that is responsible for assigning addresses to the MNs, you can define a starting address for that is incremented for each MN session. Some test cases allow you to specify that a static address be used for every MN session.

• ASN Nodal Testing

• CDMA2000 Testing

• GPRS Testing

• IP Data Testing

• Mobile IPv4 Testing

• Mobile IPv6 Testing

• UMTS Testing

Include MS ISDN

The MS ISDN directory number for the mobile subscriber ID included as part of the PCC-R3-P/PCRF Subscriber ID. This value is incremented for each mobile subscriber.

Range: Maximum 16 digits

Default: 393462955800

Tcl Parameter: PCRFCinCcMsisdn

Include IMSI

The International Mobile Subscriber Identifier included as part of the PCC-R3-P/PCRF Subscriber ID.

Range: 5 15 digits

Default: 222101000001056

Tcl Parameter: PCRFCinCcImsi

Include NAI

The mobile subscriber's Network Access Identifier (NAI) included as part of the PCRF Subscriber ID.

Range: Up to 127 Characters

Default: NONE

Tcl Parameter: PCRFCinCcNai

Starting MS ISDN Number

The starting ISDN directory number for the mobile subscriber. This value is incremented for each mobile subscriber.

In HSS Node test case, select the checkbox to enable Starting MS ISDN Number.

Range: Maximum 16 digits

Default: 393462955800

Tcl Parameter:

During MME Node testing, select MME Initiated Detachment and enter the number of milliseconds that the test will wait before beginning to perform MME detaches.

Range: 0 - 100000

Tcl parameter: MmeDetachmentDelay

In ASN Nodal Testing, the UE Initiated Service Flow is available you only when the Test Activity is Capacity and WIMAX Forum Version is Rel. 1 Version 1.3. Depending on the value of this parameter, the following parameters are available on the WiMAX Forum tab:

• Zero value: The Max Uplink/Downlink Service Flow parameters are available on the WiMAX Forum tab .
• Non-zero value:  ASN Nodal creates Service Flows equal to the value you selected and initiates the Data Path Registration request.

The TFT settings on the Test configuration tab becomes available

Values: 0 - 5  

Default: 0

Tcl Parameter: NumServiceFlows

During ASN and CSN Nodal Testing, in addition to defining the number of mobile subscribers on the Test Configuration tab, on the WiMAX Forum tab, you can define a unique identifier for each MN and the EAP authentication configuration.

(enabled when HA Node Emulation is selected)

To use dynamic addressing, select Dynamic Home Address Pool from the drop-down list and enter a starting IP address in the field provided. The address will be incremented for each MN session.

You can allow the MNs to use the same home address by selecting Static Home Address from the drop-down list and entering the address.

You can use the Dynamic HA checkbox to enable dynamic Home Agent address resolution by the MN when Client MIP is selected, or to enable the HA node to support Agent Discovery when HA Node Emulation is selected.

Number of Subscribers

The number of MBMS Bearers used in the test. The maximum allowed depends on your system license and type of test that is being executed. i.e. whether DMF, WebDAV or FLUTE Traffic is enabled.

eMBMS Node Test Case =  DMF Traffic up to 1000, WebDAV Traffic up to 100

eMBMS Nodal Test Case = Non-FLUTE Traffic up to 32,000, FLUTE Traffic up to 3,200

Tcl Parameter: MbmsBearers

• Home Type Address

• Bearer IPv6 Pool Address

• Bearer IPv4 Pool Address

In eMBMS Nodal test case, select the Home Address type as both or IPv4, or IPv6. The Bearer Pool IPv6 and/or IPv4 Address field (Test Configuration tab, Mobile Subscriber pane) is required for each subscriber.

• Activation Rate

• Deactivation Rate

In eMBMS Node test case:

• Set to specify the rate for starting all the MBMS Bearers, except the first one.
• Set to specify the rate at which the test attempts to deactivate MS sessions. When the control plane is used, this rate is the number of MS that will attempt to disconnect their control sessions every second. When the control plane is not used, this rate is the number of MS that will stop sending data or release their data connections every second.

• Preconfigured Service Announcement Bearer

• Preconfigured Bearer Index

• Preconfigured Multicast IP

1. User can only select only one of Pre-Configured bearer index or preconfigured multi cast IP.

2. Preconfigured bearer index and preconfigured multi cast IP should grey out when preconfigured service announcement bearer is not selected.

Tcl Parameter: PreconfigEn

Tcl Parameter: PreconfigType

Tcl Parameter: PreconfigBearer

Tcl Parameter: PreconfigIp

• Number of Downlink Node Lists

Downlink node list represents the list of downstream nodes within a MBMS bearer context.

Maximum 10 Downlink Node Lists can be configured, and maximum 32 Downlink Nodes can be configured in each downlink node list.

Round-Robin method will be used to distribute the MBMS bearers between downlink node lists. For example, if there are 10 MBMS Service bearers and 3 down link node lists. MBMS Bearer 1, 4, 7, 10 will use downlink node list 1 as downlink node list in SGmb interface, MBMS Bearer 2, 5, 8 will use downlink node list 2 as downlink node list in SGmb interface, MBMS Bearer 3, 6, 9 will use downlink node list 3 as downlink node list in SGmb interface.

Number of UEs

Indicates the maximum number of UEs supported in your system (determined by your license capacity).

Tcl Parameter: NumUes

Indicates the number of SIP Subscribers supported per UE.

Tcl Parameter: SipSubscribersPerUe

Each UE places at least 2 simultaneous calls per UE. That is, each UE has at least 2 Public User Identities or at least 2 SIP Subscribers configured per UE.

Starting MSRP Port

The first port of the MSRP session. Enter zero (0) to automatically use an available port for the first port of the MSRP session.

Range: 0 - 65534

Default: 2855

Subscriber ID

Include MS ISDN

Include IMSI

Include Public ID

Include Private ID

• Include MS ISDN : The MS ISDN directory number for the mobile subscriber ID included as part of the PCC-R3-P/PCRF Subscriber ID. This value is incremented for each mobile subscriber.

Range: Maximum 16 digits

Default: 393462955800

Tcl Parameter: PCRFClnCcMsisdn

• Include IMSI (The International Mobile Subscriber Identifier) included as part of the PCC-R3-P/PCRF Subscriber ID.

Range: 5 15 digits

Default: 222101000001056

Tcl Parameter: PCRFClnCcImsi

• Include Public ID: Select to Include SIP Public ID.

Tcl Parameter:  PCRFClnCcPublicIdEn

• Include Private ID: Select to Include SIP Private ID.

Tcl Parameter:  PCRFClnCcPrivateIdEn

Call control options are available only when you configure multiple DMFs via Gm >Media > RTP tab (configure one of the audio DMFs and the other video).

Allows you to control call media by specifying how the calls are started and released. You may also specify a delay in starting the call and duration of the call.

Call Control Options are applicable for both Originate and Terminate sides.

Startup

Indicates the type of call at the beginning of a call. Select the required option.

• Normal (Voice and Video at start of call)
• Video started mid-call

Delay is available when you select the option Video started mid-call. Configure the delay in seconds.

Default: 5 Seconds

Release

Indicates the type of call at the end of a call. Select the required option.

• Normal (Voice and Video at end of call)
• Video released mid-call

 When you select Video release mid-call, you may configure the Duration of the call

Default: 5 Seconds

IPv4 Address Pool

IPv6 Address Pool

Enter either an IPv4 Address or IPv6 Address (In IMS Nodal TC)

Tcl Parameter:  V4AddrPool

Tcl Parameter:  V6AddrPool

IMEI

Enable to enter the International Mobile Equipment Identity (IMEI).  

Tcl Parameter:  ImeiEn

Tcl Parameter:  Imei

Default Bearers per Session

Select the Default Bearers per Session from the dropdown list.

For the OFCS Node/Nodal, SGW Nodal, and PGW Nodal test cases, when you select the number of Default Bearers per Session, you configure the MN connecting to multiple APNs. Up to 11 Default Bearers per Session is supported.

In PGW Nodal test case, when you select NEMO Emulation, Default Bearers per Session is limited to 1.  

In MME Nodal and SGW Nodal testing, supports multiple Default Bearers per Session when Test Activity is Inter Technology Mobility.

3GPP defines a maximum of 11 bearers per UE. Here are the ways to get to 11 bearers total on Landslide:

1. Set up 11 default bearers, one per APN, or
2. Set up 1 default bearer and have it include 10 dedicated bearers

In Landslide, default and dedicated bearers have a “relationship”.  When you use more than 1 default bearer, per design, if you want to assign dedicated bearers with the default bearers, each default bearer must use the same number of dedicated bearers. Here is the maximum number of total bearers per UE based on the number of dedicated bearers per default bearer for each possible combination (Note: the GUI automatically adjusts the “Dedicated bearers per default” pulldown so that it never lets you select a number that would give you more than 11 total):

Tcl Parameter: DefaultBearers

Options: 1 — 11

Default: 1

If the 5G test cases (ex. AMF Nodal, UE Emulator Data Node , UPF Nodal, etc), the DefaultBearers variable is used in the "Enter the number of PDU (Protocol Data Unit) sessions". Currently up to 15 are supported. However, in AMF Nodal, when Test Activity = Inter Technology Mobility and Handoff Protocol = WiFI only 2 PDUs are supported.

Dedicated Bearers per Default

Select the Dedicated Bearers per Default from the list to specify multiple defaults per session.

During PGW Nodal testing, Dedicated Bearers per Default is not available when Protocol = PMIPv6.

Selecting Dedicated Bearers per Default allows you to select the number of TFTs to be configured. Up to 11 Dedicated Bearers per Default is supported.

Tcl Parameter: DedicatedsPerDefaultBearer

Options: 0 — 10

Default: 0

Report within Default Session

Available in OFCS Nodal test case - Select to start accounting records within the default bearers session.

Tcl Parameter: ReportDefaultSession

Number of Low Priority Subscribers

This identifies how many subscribers out of the "Number of Subscribers" are classified as Low Priority Access. All Subscribers or any subset thereof, including none can be marked as Low Priority subscribers. However, there is no control as to which subscribers will be marked as LAPI (Low Access Priority). The method that is used to spread the LAPI subscribers is :

If there are 5 total subscribers and 2 are LAPI, then Mobile subscribers 2 and 4 would be marked as LAPI.  

If there are 100 total subscribers and 5 are LAPI, then Mobile subscribers 20, 40, 60, 80 and 100 would be marked as LAPI.  

Tcl Parameter: NumLapiSubs

Options: 1 — 800000

Default: 0

Use Real SIM Card (One Subscriber)

Available in AMF Nodal, MME Nodal Test Case, UMTS, HNB GW Nodal and Wifi Offload Gateway Nodal (available if AP Tunnel = None and Data IPsec is enabled). Enable for Support of Real SIM Card. On Wifi Offload Gateway Nodal test case, Use SIM Server (see below) and Use Real SIM Card (one Subscriber) are mutually exclusive.

When enabled, only One Subscriber is supported and the following parameters will be grayed out (not available for input).

S1-MME (NAS) - Starting IMSI, Secret Key, Operator Variant, Authentication Use Test Algorithm, OPc and Swap the order of short MAC.

Tcl Parameter: NumRealSimSubs

Use SIM Server

Available in AMF Nodal, MME Nodal, UE node, UMTS and Wifi Offload Gateway Nodal test cases. Select to add support for the Non-RF SIM Client (vSIM) to support LTE Authentication by remotely accessing  the USIM card in the SIM Server in AMF Nodal, MME Nodal, UE Node test cases and Wifi Offload Gateway Nodal. The SIM Clients tab becomes available for input. Not available when Test Activity = Inter Technology Mobility and Handoff Protocol = (GPRS or eHRPD or 1xRTT or Wifii) (see note below) or Command Mode/Sequencer on MME Nodal. Not available when Type = UE Handset on UE Node. 

Use SIM Server is supported when Test Activity = Inter Technology Mobility and Handoff Protocol = ( UMTS (IuPS over IP) or UMTS (IuCS over IP) or UMTS (IuPS & IuPS) over IP) on MME Nodal.  

Available on Wifi Offload Gateway Nodal when RF UEs or (AP Tunnel Type = NONE and Data IPSec ) is enabled. When "Use SIM Server" is selected on Wifi Offload Gateway Nodal, only one subscriber is supported. For EAP-AKA authentication with SIM Server testing (for Visionworks) : Configure "802.1x-EAP" as Authentication type in the "RF Interface" and then click EAP Settings. Set IMSI value to the Username field of EAP tab and check EAP-AKA. The IMSI will be included in the TEST.PROCS file. 

When SIM server is used, SIM server will take RAND and AUTN as verification parameters and verify AUTN instead of MAC. In the Test Algorithm case, a very small difference in the KEY may generate the same AUTN and SIM Server may get authentication pass. For negative test which needs to produce MAC failure in the client, need to use a significant different KEY. 

Available in UMTS test case when Test Activity = Capacity.

Mutually exclusive with Use Real SIM Card (One Subscriber).

Note: When Test Activity = Inter Technology Mobility on MME Nodal and AMF Nodal with Handoff Protocol = WiFi, Use SIM Server is available for EAP Settings = EAP AKA or EAP SIM.

We added the ability to reuse the SIM card within the same Test Session. If there is a conflict, the user may see "SIM Slot already in use within this Test Session".

The Basic SIM Server system consists of three main components: SIM Array(s) and SIM Client(s) and SIM Emulators. SIM Array is a hardware unit that holds up to 13 hot-pluggable SIM Boards. Each SIM Board has a capacity of 32 SIM cards. Virtually any number of SIM Arrays can be combined to build huge “SIM farms”. Add SIM Array via Admin -> vSIM Administration.

Landslide TAS & Test Cases act as Client and communicate with Implementa SimArrayllx through the proprietary interface(Extended SIMCP over TCP/IP) defined by Implementa. https://www.implementa.com/products/sim-array.
The TAS retrieves the information(such as IMSI) of SIM Cards inserted in Implementa SimArrayllx and manages the resources for each test-run. The Test Case such as AMF Nodal or MME Nodal communicates with Implementa SimArrayllx during the test-run to get the 3gpp authentication result from SIM card in Implementa SimArrayllx.

SIM Client is a software component that acts as a gateway between SIM Emulators and SIM Arrays. Each mobile device is equipped with a SIM Emulator inserted into its SIM Holder thereby replacing the physical SIM card. Different versions of SIM Emulators are available. Each mobile device connected to the system by means of a SIM Adapter is represented by a Channel entity in the application software and APIs.

SIM Arrays are typically placed in one or more central locations, while SIM Clients and Emulators are located remotely along with distributed mobile devices (e.g. GSM/UMTS terminals).

The assignment of SIM Cards to the Channels is managed by an external user supplied component.

The purpose of using SIM Server in AMF Nodal, MME Nodal and UE node test cases is to use IMSI stored in USIM and execute LTE authentication by remotely accessing USIM card in SIM Server.

To communicate with SIM Server and access USIM card remotely, TAS and TS (AMF Nodal, MME Nodal, UE node) will use TCP/IP connection via eth0 (management network).

Tcl Parameter: UseSimServerEn

Dedicated Bearer Rates and Delays

You may configure delay times for groups of Dedicated Bearers and in MME Nodal test case, you may also configure delay times for individual dedicated bearers.

• In MME Nodal test case, the Dedicated Bearer Rates and Delay pane parameters are available when Dedicated Bearers Per Default is = or > 1 and you select the UE Initiates Dedicated Bearers or  SGW/PGW Node Emulation.
• In PGW Node test case, the Dedicated Bearer Rates and Delay pane parameters are available when Dedicated Bearers Per Default is = or > 1.

• In SGW Nodal test case and PGW Node test Case, the Dedicated Bearer Rates and Delay pane parameters are available when Dedicated Bearers Per Default is > 0.

Also during SGW Nodal testing, the Dedicated Bearer Rates and Delay pane allows you to enter Dedicated Bearer Inter-Bearer Start Delay times.

Tcl Parameter: ConnectBearerDelay

The Bearer Start Delay Times provides you with means to control each dedicated bearer starting at the different time. See this example.example.  

Configure Individual Dedicated Bearer Delays

MME Nodal and PGW Node test cases support delay times for individual dedicated bearers. Configure Individual Dedicated Bearer Delays is available in the Dedicated Bearer Rates and Delay pane when UE Initiate Dedicated Bearers or or  SGW/PGW Node Emulation is enabled on MME Nodal test case.

In PGW Node test case, the Dedicated Bearer Rates and Delay pane parameters are available when Dedicated Bearers Per Default is = or > 1.

Type: True/False (default is False).  

Tcl Parameter: ConnectBearerDelayIndivEn

When you select Configure Individual Dedicated Bearer Delays, a table displays allowing you to enter individual dedicated bearer delay for each Default Bearer.  For example, if you have selected 2 Default Bearers per Session and 2 Dedicated Bearers per Default, you may configure individual dedicated bearers for D0-B0, D0-B1, D1-B0, and D1-B1.  

Activation Rate (Bearer)

In SGW testing, Activation Rate indicates the rate at which the test attempts to activate dedicated bearers. When you select the Activation Rate (Bearer) checkbox, the Dedicated Bearer Inter-Bearer Start Delay times are not available.

Connection Delay

The Connection Delay is available only when Activation Rate (Bearer) is selected and defines the period of time that elapses before establishing the dedicated bearers. This timer starts after the primary Dedicated Bearer per Default has been established.

Deactivation Rate (Bearer)

In SGW testing, Deactivation Rate indicates the rate at which the test attempts to deactivate the dedicated bearers.

Range: 0.0010 — 1000

Default: 1.0

Tcl Parameters: DedicatedBearerStopRate

Disconnect Delay

In SGW Nodal testing, the Disconnect Delay parameter becomes available when you select the Deactivation Rate checkbox and indicates the time elapsed before the test attempts to deactivated the Dedicated Bearers.

Range: 1 — 65535

Default: 60

UE Initiates LTE Deactivation with Message

Support for Bearer deactivation via Bearer Resource Modification Request message. Select one of the options.

Options: Radio Bearer Release (default), Request Bearer Resource Modification

Tcl Parameters: UeDeactMsg

Disconnect Initiated by PGW

Available on SGW Nodal Test Case when :

1. Test Activity = Session Loading, PGW Node Emulation, Serving Node S5/S8 = GTPv2 , and Load Test Dedicated Bearers Only
2. Test Activity is NOT Session Loading or NOT Command Mode or Sequencer, and PGW Node Emulation and Disconnect Dedicated Bearer after Connected.  

Select to initiate dedicated bearer delete process from emulated PGW.

Tcl Parameters: PgwInitDisconDedBearerEn

Disconnect Dedicated Bearers After Connected

Use the checkbox to disconnect dedicated bearers after connection. This parameter is available in MME Nodal testing and PGW Node Testing when Dedicated Bearers Per Default is > 1 and in SGW Nodal testing when Dedicated Bearers Per Default is > 0.

Available on AMF Node when PGW-C Emulation is enabled.

In SGW Nodal testing and PGW Node Testing, The Disconnect Dedicated Bearers after Connection allows you to enter Delay Timer for each Dedicated Bearer. You may enter individual Disconnect Delay time for each dedicated bearer except for the default bearer. The Disconnect Dedicated Bearers after Connection is not available if Deactivation Rate (Bearer) is selected.

Disconnect Delay

In MME Nodal testing, the Disconnect Delay parameter becomes available when you select the Disconnect Dedicated Bearers After Connection checkbox.  This defines the time elapsed before the test attempts to deactivate the Dedicated Bearers.

Range: 1 — 65535

Default: 60

Tcl Parameters: DisconnectDedicatedBearerEn

PDN Connect and Activation

Tcl Parameter: PdnConnectDelayTime

Tcl Parameter: PdnActivationRate

Available in MME Nodal test case when Test Activity = Capacity.

This field represents the maximum percentage of failed mobile registrations before any PDU Session Establishment attempt is allowed.

Range : 0 to 100

Default : 10

Tcl Parameter: PdnFailedThresholdPercentEn

Tcl Parameter: PdnFailedThresholdPercent

Home Address Type

Use Home Address Type to configure PDN type option: IPv6, IPv4, both, or Non-IP.

In SGW Nodal and MME Nodal test cases, the Home Address Type options is not available when you select Specify Home Address Type Per Default Bearer. (Supports Dual Stack).

Options: IPv4 (1); IPv6 (2); Both (3), Non-IP (5).

Tcl Parameter: HomeAddrType

Specify Home Address Type per Default Bearer

In SGW Nodal test Case, the parameter is not available when Test Activity is Inter-Technology Mobility, and Handoff Protocol is WiFi on the Test Configuration tab.

Specify Home Address Type per Default Bearer is not available in MME Nodal test Case, if:

• Test Activity is Inter-Technology Mobility, Session Loading with Mobility, Command Mode, Sequencer, or Session Loading with Mobility when the Mobility type is Inter-Technology, and

• Handoff Protocol is UMTS (Iu over IP) or GPRS, and

• Initial Network is Target

Tcl Parameter:

Use Static IP Address

In SGW Nodal, PGW Nodal, and MME Node testing testing, you can allow the Mobile Subscriber to use a static home address by checking the Use Static IP Address checkbox. See also Bearer Address Pools and Starting Home Address Pools.

Tcl parameter: UseStaticBearerIp

UE DHCPv4 IP Address

MAC Address    

In SGW Node, becomes available when "PGW Node Emulation" is selected and "S5/S8 Protocol" is "GTPv2" on SGW Node Emulator Configuration.

In MME Node, becomes available when "Emulate Srv GW and PDN GW" is selected  on MME Node Emulator Configuration.

In PGW Node, becomes available when "Mobility = None" and Protocol  is "GTPv2" on PGW Node Emulator Configuration.

In AMF, MME and SGW Nodal, MAC Address becomes available to capture an valid MAC Address with Colon or Dash delimiters.

In AMF Nodal test case , UE DHCPv4 IP Address is not available when Test Activity = Inter Technology Mobility, or if N3IWF is enabled, or if SMF/UPF Node Emulation is enabled or if PDU Type in NAS-5G/SM Tab is = “IPv6” or "Both".

In AMF Node test case, UE DHCPv4 IP Address is not available if PGW-C Emulation is enabled, or if SMF Emulation is not enabled. If UE DHCPv4 IP Address  is enabled, PDU IPv4 Address Pool, Additional IPv4 Pools, and IPv4 Address Pool are not available for input on NAS-5G/SM Tab.

In SMF Nodal test case, UE DHCPv4 IP Address is not available if UPF Emulation is enabled or or if PDU Type in NAS-5G/SM Tab is = “IPv6” or "Both" or Command Mode / Sequencer with Handoff Protocol other than Node.

In SMF Node test case, UE DHCPv4 IP Address is not available if PGW-C Emulation is enabled.

In AMF Node and SMF Node test cases, the Second Agent(v6) tab displays when you select both UE DHCPV4 IP Address and UE DHCPv6 IP Address on AMF Node Emulator Cnfg or SMF Node Emulator Cnfg. The configuration on this tab corresponds to the Second (v6) DHCP Relay Agent Node on the Network Devices tab. For both UE DHCPV4 IP Address and UE DHCPv6 IP Address to become available, PFCP Version >= 15.0.0 and IP6PL must be enabled on N4 interface.

In Wifi Offload Gateway Nodal Test Configuration, enter a valid MAC Address with Colon or Dash delimiters. When AP Tunnel Type is NONE, enter 00:00:00:00:00:00 to use Network Devices/AP-WAN Node's Eth interface MAC Address.

You will get a warning that you can either click OK or Cancel to return to Gui. Select checkbox labeled "Do not show warnings again during this login session" to prevent showing warnings in all test cases for the remainder of the client session.

Default: 80:B0:3D:CF:A5:B0 (on Wifi Offload Gateway Nodal)

Tcl Parameter: UeDhcpV4En

Tcl parameter: MacAddr

Bearer Address Pools

The type of Bearer Address Pool parameter available depends on the Home Address Type selected (HSGW Nodal TC > Test Configuration tab > Mobile Subscribers pane (when LMA Node Emulation is enabled))

• If Home Address Type = IPv4, only the Bearer IPv4 Address Pool is available and the Bearer IPv6 Address Pool is not available.

• If Home Address Type = IPv6, only Bearer IPv6 Address Pool is available and Bearer IPv4 Address Pool is not available.

• If Home Address Type = Both, then both the Bearer IPv6 Address Pool and Bearer IPv4 Address Pool are available.

The LTE test cases support either static or dynamic addresses for both IPv4 and IPv6 address. Static IP address are used only when Use Static IP Address is selected in PGW and SGW testing.

In SGW Nodal Testing, both Bearer IPv6 Address Pool and Bearer IPv4 Address Pool are available only Use Static IP Address is selected. Allows for the '/' character in the text box for Bearer IPv4 Address Pool. This in return  allows the user to specify a subnet for the given IPv4 address.

In SGW Node testing, both Bearer IPv6 Address Pool and Bearer IPv4 Address Pool are available when you select PGW Node Emulation on the Emulator Configuration tab.

When Sxa Interface to UP or Sxa+Sxb Interface to UP is enabled on SGW Node or Sxb Interface to UP is enabled on PGW Node and as of release 17.4, you must enter a valid IPv6 prefix, requires "[ipv6-address]/[prefix-length]". The valid range for the prefix-length is: 9 to 64.

Bearer IPv6 Address Pool [BearerAddrPool=2001:0DB8::CD30:0:0:0:0] Prior to release 17.4

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

In MME Nodal Testing, both Bearer IPv6 Address Pool and Bearer IPv4 Address Pool are available only when Emulate Srv GW and PDN GW is selected on the Test Configuration tab.

Tcl Parameter:

Starting Home Address Pools

In PGW Nodal test case, the Starting IPv4 Home Address field is available when Home Address Type is IPv4 and Starting IPv6 Home Address is available when Home Address Type is IPv6.

Tcl Parameter:

MME Disconnect Bearer after Connected

• Disconnect Default Bearer

• Disconnect Delay Time (s)

In MME Node test case, select MME Disconnect Bearer after Connected to enable the release of already established E-RABs for a given UE (using the UE-associated signalling).

Available on AMF Node when PGW-C Emulation is enabled.

Select Disconnect Default Bearer to enable release of already established Default Bearers.

Disconnect Delay Time (s) is available when you select MME Disconnect Bearer after Connected and you may enter the time to wait before releasing connect bearers.

Option: 0 - 100000

Default: 0

Defines the period of time that will elapse before handing over additional PDN connection after the handover.  

Available in MME Nodal test case when the Test Activity is Inter-Technology Mobility or Session Loading with Mobility and the Mobility Type is Inter-Technology, and Handoff Protocol is eHRPD.

Upstream QCI to DSCP Markings

Available in MME Nodal and SGW Nodal test cases when you select the VOLTE option.

QCI Settings

You can provision explicit values for Mobile Subscribers by using Test Data Files. Download a sample file by right-clicking the link below.

See Applying Parameter ValuesApplying Parameter Values.

In PGW Nodal test case, available when you select NEMO Emulation on the Test Configuration tab. Each mobile router is responsible for a number of UEs specified in Number UEs per Mobile Router  (depending on your licensed value).

When a mobile router successfully connects to a HA, all the UEs attach to that mobile router will be started.

When you select NEMO Emulation, the total number of sessions for NEMO is (Number of Mobile Routers) * (Number of UE's per Mobile Router) * (Default Bearers per Session).

Enter the number of UEs supported by Mobile Router (depending on your licensed value).

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

When you select Do Not Attach UEs, the following parameters are not avaialble:

• PDN Connect Delay
• PDN Activation Rate
• Attach Start Delay
• Activation Rate

Back-off Timer (s)

Add a Back-off Timer in Seconds to enable the configuration of the APN Congestion table where you can configure the Congestion % per APN.

Range: 0 to 65535, Default = 0

Available in PGW Node test case to configure the max percentage load level (congestion level) for each configured APN. Once the Maximum supported congestion percentage load is reached for a given APN, the PGW will send Create Session Response with Cause = APN_CONGESTION  GTPv2 cause code 113. This cause code is used by the PGW to indicate that the PGW has detected congestion for the requested APN and performs overload control for that APN, which does not allow the PDN connection to be established.

Enable Overload Control

Available in the PGW Node and SGW Node test cases , to indicate that a PGW/SGW can be overloaded or to simulate an overload condition where the ePDG under test will know not to send traffic to the overloaded PGW/SGW. Per 3GPP 29.274 V16.0 and 3GPP TS 24.301 V 16.1.1.

See example.

Tcl Parameter: OverloadCtlEn

Example for Update Granularity :

For example the Node is provisioned

• with 100 bearers,

• the “Update Granularity” is set as 10,

• the original reduction metric is 0%.

After 1 bearers are established, the overload reduction metric is calculated as 1%, the gap between current and previous metric (0%) is less than “Update Granularity”, so the OLC IE is not included.

After 2 bearers are established, the overload reduction metric is calculated as 2%, the gap between current and previous metric (0%) is less than “Update Granularity”, so the OLC IE is not included.

After 10 bearers are established, the overload reduction metric is calculated as 10%, the gap between current and previous metric (0%) is equal or greater than  “Update Granularity”, so the OLC IE is included, ONLY ONE TIME.

After 11 bearers are established, the overload reduction metric is calculated as 11%, the gap between current and previous metric (10%) is less than “Update Granularity”, so the OLC IE is not included.

After 20 bearers are established, the overload reduction metric is calculated as 20%, the gap between current and previous metric (10%) is equal or greater than  “Update Granularity”, so the OLC IE is included, ONLY ONE TIME.

Considering the APN level Overload control together, if one of the OLC IE (Node level or APN level) metric gap (between current reduction metric and previous metric) is equal or greater than the value of “Update Granularity”, all of the OLC IEs should be included in the message.

Load Control

Available in the PGW and SGW Node test cases. Select to support Load Control Information (LCI) IE. Per Spec Reference: 3GPP TS 29.274 V15.6.0

Tcl Parameter: LoadCtlEn

You can include one or more Subscriber-Id AVPs in CCR messages. Use the checkboxes to select the types of identifiers to include and enter the starting values in the fields provided. The values will be incremented for each MN.

• Include MSISDN (default)

• Include IMSI

The Service-Context-Id identifies the service-specific document that applies to the credit request. Service-Context-Id and Rating-Group are inputs to the rating process and the combination of the two can uniquely identify a service.

Format: <service context>@<domain> where domain refers to the standardization body or vendor that allocated the ID.

Default: [email protected]

Select to make sure that the Client includes the Requested-Service-Unit AVP at the message level in addition to within the MSCC AVP.

Use to include a User-Name AVP in CCR messages and enter a starting value in the field provided. See User Credentials for a full definition.

Default Bearers per Session

In DRA Nodal test case, the parameter is available only when you enable PCRF Interfaces, select AGW Client Interfaces and enable emulation of PCRF AGW I/F.

Select the Default Bearers per Session from the dropdown list.

For the DRA Nodal test case, when you select the number of Default Bearers per Session, you configure the MN connecting to multiple APNs (Gx Interface). Up to 11 Default Bearers per Session is supported.

When Default Bearers per Session is > 1, you may configure PDN Connection and Activation delays as well.

Tcl Parameter: DefaultBearers

Options: 1 — 11

Default: 1

Dedicated Bearers per Default

In DRA Nodal test case, the parameter is available only when you enable PCRF Interfaces, select AGW Client Interfaces and enable emulation of PCRF AGW I/F.

Select the Dedicated Bearers per Default from the list to specify multiple defaults per session.

Selecting Dedicated Bearers per Default allows you to select the number of Packet Filters and the requested uplink/downlink to be configured. A maximum of 11 Dedicated Bearers per Default is supported.

Tcl Parameter: DedicatedsPerDefaultBearer

Options: 0 — 10

Default: 0

PDN Activation Rate

The PDN Activation Rate defines the rate at which the secondary default bearers will be established.

Range: 0.0010-1000.0

Default: 1.0

Tcl Parameter: StartRate

Deactivation Rate

The rate at which the test attempts to deactivate MS sessions. When the control plane is used, this rate is the number of MS that will attempt to disconnect their control sessions every second. When the control plane is not used, this rate is the number of MS that will stop sending data or release their data connections every second.

Tcl Parameter:

Subscription ID

In DRA Nodal test case, you may select one or more identifiers and enter the appropriate values, which are incremented for each Mobile Subscriber.

You may also choose specific interfaces to which the configured identifiers are applied.

• Click ... and Include MS ISDN / IMSI/ NAI / Private / SIP URI in Specific Interface window opens.

• Select the interfaces to which the configured identifiers will be applied.

Include Logical Access ID

Enable to fill the Logical-Access-ID AVP with a Circuit ID (RFC 3046 (11)) or a technology independent identifier. Include AVP in CCR-I Message.

Default = XX/YYYY/000000/111/CC/SEG

Where :

XX - Prefix

YYYY - Service Code - Service Code Modifier

000000 - Serial Number

111 - Suffix

CC - Company Identifier

SEG - Segment Name

Enter XX/YYYY/000000/111/CC/SEG#(1) to auto increment Logical Access ID. Value after Hash tag (#) will be replaced by incrementing integer for every user.

Enter  'Select Specific interfaces to include in" window - Currently only Gx and Sd allowed.

Tcl Parameter: PCRFClnCcLogicalAccessId

Include External ID

Available when S6t Interface is enabled. Select to enter an External Identifier.

Must enter at least one MSISDN or an External Identifier when S6t Interface is enabled.

Default: 12345#(N0)@Spirent.com

Click to use the Auto-Increment Format Wizard.

Tcl Parameter: PCRFClnCcExternalIdEn

Tcl Parameter: PCRFClnCcExternalId

Emergency Settings

• Support Emergency Call Flows

• IMEI

• Software Version

Select Support Emergency Flow to enter the applicable emergency settings parameters.

Home Address Type

• Starting IPv6 Address

• Starting IPv4 Address

Select the Home Address type as both or IPv4, or IPv6 or None.

In DRA Nodal, the Starting IPv6 and IPv4 Address field (Test Configuration tab, Mobile Subscriber pane) is required for each subscriber and available depending on your selection of the Home Address Type.

Selecting None disable both IPv4 and IPv6 addresses.

Options:

• IPv4 : 1
• IPv6 : 2
• Both : 3
• None : 4

Tcl Parameter: HomeAddrType

When  Home Address type is IPv4 or IPv6, you may choose the interfaces to which the configured IPv6/IPv4 addresses are applied.

• Click ... and Include IPv6/IPv6 in Specific Interface window opens.

• Select the interfaces to which the configured Starting IPv6 Address/Starting IPv4 Address will be applied.

Number of Subscribers

# of Sessions Per Subscriber

Define the max number of sessions to test. The session information is stored in order to be proxied and during DRA testing, the session state information indicates the service to which the session is bound.  

Option: 1 - 16

Default: 1

Tcl Parameter: NumSessionPerSub

Max Concurrent Transactions

Define the maximum number of concurrent transactions.  

(As a typical transaction time is very short and hard to determine, DRA Node allows you to configure as required. A transaction is active once a request is sent, and considered inactive when an answer is received.)   

You may view/observe the number of transactions from the DRA Session report under Active Transactions which shows you the number of active transactions at any given time.   

Tcl Parameter: Transactions

Enter the number of subscribers allowed per FemtoCell.

Range: 1 — 10

Default: 1

When you use the GGSN Node test case, the node is responsible for assigning IP addresses to the MN's PDP contexts when an address is requested.

During GGSN Nodal testing, Static PDP IPv4 Address Pool is available when you select PDP type as IPv4 or IPv4/IPv6 and Static PDP IPv6 Address Pool is available when PDP Type is IPv6 or IPv4/IPv6.

Tcl Parameter:

Enter valid IPv6 and IPv4 addresses.  Available in CGF Nodal Test Case.

During GGSN Node testing, These parameters are not available when you select DHCP Relay Agent on the Emulator Configuration tab. The address is incremented for each primary PDP context.

Tcl Parameter:

During GGSN Nodal testing,  Context to DSCP Assignments is available only when you select Data Traffic or External Data on the  GGSN Nodal Test Configuration tab and is available by default during GGSN Node testing.

Tcl Parameter: ContextToDscpEn

Select Context to DSCP (Differentiated Service Code Point) Assignments and enter/calculate the DSCP Assignments on the Context to DSCP Assignments window.

See Tcl Parameters for DSCP Context Assignments for Tcl parameter naming convention for Context to DSCP Assignments window.

• Context: The value in the Context column depends on the Number of Primary PDP Contexts and Number of Secondary PDP Contexts you select.
• DSCP: Indicates the DSCP assigned to the traffic class during PDP context creation (valid value ranges from 0-63).
• Calculate: Select the Per Hop Behavior (PHB) and calculate the DSCP assigned to the PDP Context (as 6 bits).

PHB indicates an observable forwarding behavior applied at a Differentiated Service (DS)-compliant node to a DS behavior aggregate.

Starting MSISDN

The MS ISDN directory number for the mobile subscriber may be included as a part of the User-Identity AVP if Public-ID is not included.

Range:  Maximum 16 digits

Default:  393462955800

Tcl Parameter:

Identifier used for communicating with other users.  May be added in the User-Identity AVP, if MSISDN is not present. Use the Auto-Increment wizard to set up User. Click here to find out additional information about Parameter Auto Increment Wizard.

Select and a table of up to 5 rows will become available to capture a Public ID.

Range:  Up to 127 Characters.

Default: user#(N0)

Click to use the Auto-Increment Format Wizard.

Tcl Parameter:

Incremented Private ID

A unique global identity defined by the home network operator that identifies the user’s subscription.  Private ID is included in the User-Name AVP. Use the Auto-Increment wizard to set up User. Click here to find out additional information about Parameter Auto Increment Wizard.

Range:  Up to 127 Characters.

Default: user#(N0)

Click to use the Auto-Increment Format Wizard.

Tcl Parameter:

The starting International Mobile Subscriber Identifier for the mobile subscriber. This value is incremented for each mobile subscriber and is also used as the Open RP MS ID.

IMSI - Enable to enter IMSI Starting Number. Only available is Sh interface is enabled.

Range: 10 - 15 digits

Default: 222101000001056

Tcl Parameter: ImsiEn

Tcl Parameter: StartingImsi

Identifier used for communicating with other users.  May be added in the User-Identity AVP, if MSISDN is not present. Use the Auto-Increment wizard to set up User. Click here to find out additional information about Parameter Auto Increment Wizard.

Range:  Up to 127 Characters.

Default:  User#(N0)

Incremented Private ID

A unique global identity defined by the home network operator that identifies the user’s subscription.  Private ID is included in the User-Name AVP. Use the Auto-Increment wizard to set up User. Click here to find out additional information about Parameter Auto Increment Wizard.

Range:  Up to 127 Characters.

Default:   User#(N0)

Enter a Tel-URI Public ID. Use the Auto-Increment wizard to set up Tel-URI (phone number) per RFC 3966. Click here to find out additional information about Parameter Auto Increment Wizard.

Range:  Up to 127 Characters.

Default:   tel: +123456789#(N0)

• When S6a is selected on the Emulator Options, use the Enable Mobile Deactivation to send/issue the Location Cancellation command.

The Deactivation process sends Location Cancellation Request to MME and waits for Location Cancellation Confirmation from MME.

• When SWx is selected on the Emulator Options, use the Enable Mobile Deactivation to trigger the Deregistration process.  The HSS de-registers the relevant subscriber(s) and informs the 3GPP AAA server to remove the subscribed user from the 3GPP AAA Server.

When Enable Mobile Deactivation is selected, you can set the mobile deactivation Delay Times for a Range of Subscribers.

Default: False

Tcl Parameter: HssDeactivationEn  

Value: True/False

The Delay Time indicates the interval between activating the MS and issuing of the Location Cancellation command.

Range: 0 - 100000

Default: 0

Tcl Parameter: HssDeactDelayTime  

Specify Subscriber Range MS Range if it is different from entire MS range of the Test Case. When you first check "Specify Subscriber Range" the values are defaulted to the normal range of the Test Case.

Tcl Parameter: HssDeactSpecificRangeEn

Value: True/False

Starting IMSI First MS of the Range

Tcl Parameter:HssDeactStartingImsi

Number of MS the command will be applied

Tcl Parameter: HssDeactNumSubscribers

External Identifier

Available when S6t Interface is enabled. Select to enter an External Identifier.

Must enter at least one MSISDN or an External Identifier when S6t Interface is enabled.

Default: 12345#(N0)@Spirent.com

Click to use the Auto-Increment Format Wizard.

Tcl Parameter: ExternalIdEn

Tcl Parameter: ExternalId

You can provision explicit values for Mobile Subscribers by using Test Data Files. Available when Interface = S6a, S6d, S6t, SWx or Wx.

There are two ways to Configure TDF for HSS Node

 TDF 1 constraints S6a, S6d, S6t, Swx, and Wx Interfaces:

When configuring TDF, user must name the column “Key Type” exactly. Key Type is assigned an integer. If the user wants to configure TDF for MSISDN, then Key Type == 1 should be used. Column “Key” represents the subscriber ID values and must be spelled exactly as such.

Download a sample file by right-clicking the link below.

For the Subscriber ID Type in the TDF file, use the Subscriber Integer value from the table to identify the subscriber type. For example, for IMSI subscriber type, indicate "2" in the TDF .csv file for the Subscriber ID type.

HSS Node TDF 2 constraints S6a, S6d,  S6t, Swx, and Wx Interfaces:

TDF column names are MSISDN or IMSI and must be spelled exactly as such. Keep in mind, this method will NOT add to session key container and may get unknown user. This configuration is good if the user wants to configure subscriber Id for messages.

Secret Key, OP, and OPc have been added to this TDF file. You can specify either OP or OPc in the TDF, not both. Secret Key is either string or Hex value starting with "0x", and OP or OPc is 16 byte Hex starting with "0x" - same as GUI. 

If Secret Key column exists in the TDF, it will be used for that subscriber, overriding the secret key from GUI configuration.If OP/OPc column exists in the TDF, it will be used for that subscriber, overriding the OP/OPc values from the GUI configuration.

Tcl Parameter: HssCfgFileEn

See sample file for TDF 1 hssTDFS6a1.csv

See sample file for TDF 2 hssTDFS6a2.csv

See Applying Parameter Values.

You can provision explicit values for Mobile Subscribers by using Test Data Files. Available when Interface = Gr.

Download a sample file by right-clicking the link below.

TDF column names are MSISDN or IMSI and must be spelled exactly as such.

Tcl Parameter: HssGrCfgFileEn

See sample file hssTDFGr.csv

See Applying Parameter Values.

You can provision explicit values for Mobile Subscribers by using Test Data Files. Available when Interface = Sh.

Download a sample file by right-clicking the link below.

TDF column name is MSISDN and must be spelled exactly as such.

Tcl Parameter: HssShCfgFileEn

See sample file hssTDFSh.csv

See Applying Parameter Values.

The number of unique mobile subscribers (MSs) emulated during the test.

Auto-Generate TFTs

The rate at which the test attempts to activate MN/MS sessions.

Use Home Address Type to configure PDN type option: IPv6, IPv4, or both.

In HSGW Nodal test case, the Home Address Type options becomes available only when Test Activity is Inter Technology Mobility and Initial Network is LTE.

Options: IPv4 (1); IPv6 (2); Both (3)

Tcl Parameter: HomeAddrType

The type of Bearer Address Pool parameter available depends on the Home Address Type selected (HSGW Nodal TC > Test Configuration tab > Mobile Subscribers pane (when LMA Node Emulation is enabled))

• If Home Address Type = IPv4, only the Bearer IPv4 Address Pool is available and the Bearer IPv6 Address Pool is not available.

• If Home Address Type = IPv6, only Bearer IPv6 Address Pool is available and Bearer IPv4 Address Pool is not available.

• If Home Address Type = Both, then both the Bearer IPv6 Address Pool and Bearer IPv4 Address Pool are available.

Only works on LTE side. Defines the period of time that will elapse before handing over additional PDN connection after the handover attachment.

Available when the Test Activity is Inter-Technology Mobility or Session Loading with Mobility and the Mobility Type is Inter-Technology.

Available in HSGW Nodal TC when Test Activity is Inter Technology Mobility or Session Loading with Mobility and Mobility Type is Inter Technology or Capacity.

The PDN Connection Delay Time defines the period of time that will elapse before establishing the second default bearers. In LTE network, the timer starts after all subscribers' first default bearer has been established.

For Capacity test, PDN Connect Delay is applied to initial AUX start up.

Range: 1 - 65535:  

Default: 1

Tcl Parameter: PdnConnectDelayTime

Available when the Test Activity is Inter-Technology Mobility with Initial Network is LTE or Session Loading with Mobility and the Mobility Type is Inter-Technology and Initial Network is LTE. The PDN Activation Rate defines the rate at which the secondary default bearers will be established.

 Available when the Test Activity is Capacity Test, or Inter-Technology Mobility or Session Loading with Mobility and the Mobility Type is Inter-Technology and "PDN Connect Delay" is available.

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.

Also available on IMS Node (on Network Devices 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.

Tcl Parameter: RtpIpAddressEn

Tcl Parameter: RtpIpAddress

Random IPv6 Address

Select to generate a random IPv6 address.

Tcl Parameter: RandomIp6Addr

IP Address Type

When you select the DHCP Client option on the Test Configuration tab, IP Address Type IPv4,  IPv6 or Dual-Stack is available for selection. Default is IPv4.

First Dynamic Address Requested

Indicates supports for multiple dynamic address acquisition in sequence.

First Dynamic Address Requested indicates whether you select IPv4 or IPv6 as the first address to request.

The parameters are available configurable when you select IP Type as Dual Stack and as follows.

Delay Before IPv4/IPv6 Requested (ms)

Indicates the delay before requested IPv4 or IPv6 address. The address type delayed depends on your selection of the First Dynamic Address Requested.

• If you select IPV6 as the first requested addresses, then configure a delay before acquiring then IPV4 address.
• If you select IPV4 as the first requested addresses, then configure a delay before acquiring then IPV6 address.

Default value is 0indicates no delay between requesting dynamic addresses.  

Tcl Parameter: SecondDynamicAddressDelay

Default Value: 0

Range: 0 ~ 2147483647

UE Static IPv4/v6

Select to support static UEs. Select the appropriate Address Type: IPv4 or IPv6, and enter the static IP address.

Tcl Parameters:

Tcl Parameter:

UeDhcpv4En

UeDhcpv6En

Select UE SLAAC to indicate that the UE support Stateless Autoconfiguration (SLAAC).

Tcl Parameter: UeSlaacEn

IPv4 Address Pool

Enter a valid IPv4 Address

IPv6 Address Pool

Enter a valid IPv6 Address

IMEI

The International Mobile Equipment Identifier included as part of the ID for Pilot Packet testing.

Range: 5 - 15 digits

Default: 50502410121507

Tcl Parameter: PpImei

IMSI

The International Mobile Subscriber Identifier included as part of the ID for Pilot Packet testing.

Range: 5 - 15 digits

Default: 50502410121507

Tcl Parameter: PpImsi

MSDN/MSISDN

The ISDN directory number for the mobile subscriber. This value is incremented for each mobile subscriber.

In IP Application Node test case, select and enter the MS ISDN Number.

Range: Maximum 16 digits

Default: 17962480141

Tcl Parameter: PpMsIsdn

Number of I2 Mobile Subscribers

Number of I2 Mobile subscribers

Range from 1 to 500,000

Default = 1

Use MS Address in Framed IP

If you enabled the AAA option, you can include the MN's IP address in the Framed-IP-Address attribute of accounting request messages with the Use MN address in Framed IP checkbox. The attribute is provisioned with the address actually used by the MN, whether the address was assigned by the test or by a DHCP server.

When the IP address is obtained from a AAA server, the checkbox is disabled and the attribute is automatically included in the request messages.

In Mobile IPv4 test cases, you can allow the MNs to use a static address by checking the Use Static Home Address checkbox and entering the address. When the box is not checked, the MNs will request that the HA SUT assign a home address.

Tcl Parameter: MipStaticHomeAddress

When co-located care-of addresses are used, you can specify the routing method for the MNs. Select Default Routing to use the static routes that are configured for the test server. Select Specify Next Hop IP Address to force the traffic through a specific interface on the test server or to set the MN's next hop to a physical device in the test network. When you select this option, enter the IP address for the next hop in the adjacent field.

Tcl Parameter: MipCoLocCareOfAddress

Client Transport:

• IP/Ethernet
• IP/PPPoE

Number of Client IP Addresses

Mobile Subscribers

Default Bearers per Session

Select the Default Bearers per Session from the dropdown list.

For the PCRF Nodal test case, when you select the number of Default Bearers per Session, you configure the MN connecting to multiple APNs. Up to 11 Default Bearers per Session is supported.

When Default Bearers per Session is > 1, you may configure PDN Connection and Activation delays as well.

Tcl Parameter: DefaultBearers

Options: 1 — 11

Default: 1

Dedicated Bearers per Default

Select the Dedicated Bearers per Default from the list to specify multiple defaults per session.

During PCRF Nodal testing, Dedicated Bearers per Default is available only AGW I/F is Gx and/or BBER I/F is Gxc.

Selecting Dedicated Bearers per Default allows you to select the number of Packet Filters and the requested uplink/downlink to be configured. A maximum of 11 Dedicated Bearers per Default is supported.

Tcl Parameter: DedicatedsPerDefaultBearer

Options: 1 — 11

Default: 1

PDN Connection Delays

Range: 0 - 65535:  (0 disables the delay)

Default: 1

Tcl Parameter: PdnConnectDelayTime

PDN Activation Rate

Range: 0.10 - 3000.0

Default: 1.0

Tcl Parameter: PdnActivationRate

Include MS ISDN

The MS ISDN directory number for the mobile subscriber ID included as part of the PCC-R3-P/PCRF Subscriber ID. This value is incremented for each mobile subscriber.

Range: Maximum 16 digits

Default: 393462955800

Tcl Parameter:

Include IMSI

The International Mobile Subscriber Identifier included as part of the PCC-R3-P/PCRF Subscriber ID.

Range: 5 - 15 digits

Default: 222101000001056

Tcl Parameter:

The mobile subscriber's Network Access Identifier (NAI) included as part of the PCRF Subscriber ID.

Range: Up to 127 Characters

Default: NONE

Tcl Parameter:

Include Private

Include Private indicates private keys, user-specific requirements that aid in S-CSCF selection, and active registration information.

Range: Up to 127 Characters

Default: NONE

Tcl Parameter:

Include SIP URISIP URI(Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) is an addressing schema that identifies a Mobile subscriber. See RFC 3261 for SIP URI standard.

Tcl Parameter:

Available only when you select IMSI.  Select IMEISV and enter the IMEISV (the MS's IMEI - 8-digit Type Allocation Code + 6-digit serial number extended with a 2-digit software version)

Tcl Parameter:

Select the Home Address type as both or IPv4/IPv6.

In PCRF Nodal, the Starting IPv6 and IPv4 Address field (Test Configuration tab, Mobile Subscriber pane) is required whenever Gxc QOS Rules include either a packet filter or a tunnel header filter. You may enter a valid IPv4 or IPv6 address as required.

In PCRF Node, the Starting IPv6 and IPv4 Address field (Emulator Configuration tab, Mobile Subscriber pane) is required whenever Gx > PCC >Charging Rules > Rule Definition > Policy Rule includes at least one packet filter. You may enter a valid IPv4 or IPv6 address as required.

Tcl Parameter:

Available on PCRF Nodal TC when Gx Interface is enabled.

When In PCRF Nodal, select to increment IP address per default bearer. Used when multiple APNs are configured, to send CCR-I messages including framed-IP AVPs that are different values.

Tcl Parameter:

You can provision explicit values for Mobile Subscribers by using Test Data Files. Available when AGW I/F or BBERF I/F are enabled.

Download a sample file by right-clicking the link below. TDF file type listed here is supported for interfaces: Ty, Gx, Gxc

For the Subscriber ID Type in the TDF file, use the Subscriber Integer value from the table to identify the subscriber type. For example, for IMSI subscriber type, indicate "2" in the TDF .csv file for the Subscriber ID type.

See sample file for TDF 4 (NAI) PcrfNAIExampleTDF.csv

Tcl Parameter: AgwMsCfgFileEn

See Applying Parameter Values.

You can provision explicit values for Mobile Subscribers by using Test Data Files. Available when Interface = OCS I/F Sy is enabled.

Download a sample file by right-clicking the link below.

For the Subscriber ID Type in the TDF file, use the Subscriber Integer value from the table to identify the subscriber type. For example, for IMSI subscriber type, indicate "2" in the TDF .csv file for the Subscriber ID type.

See sample file for TDF 4 (NAI) PcrfNAIExampleTDF.csv

Tcl Parameter: OcsMsCfgFileEn

See Applying Parameter Values.

Starting IP Address

Target IP Address

Enter the Starting (emulator) and Target IP Addresses (network).

Enter an address from the pool of addresses associated with the Physical Interface. If multiple nodes are defined, this is the address used for the first node and it is sequentially incremented for each additional node.

When Test Activity is Mobile Node Mobility (on the Test Configuration tab) a subnet mask is required to be provisioned with the IP address for Starting IP Address and Target IP Address. The addresses MUST be configured such that each address, and its associated mask, is unique and that the starting address and the target address ranges do not overlap. The addresses should be on separate networks. Both address subnet masks should be equal.  

Default Routing

Select Default Routing to use the static routes that are configured for the test server.

Next Hop IP Address

In PDG Micro Mobility test case, the next hop should be the Wireless Access Gateway (WAG) in the UMTS network, or a router that will direct the MN traffic towards a WAG.

Select and specify the Next Hop IP Address to force the traffic through a specific interface on the test server or to set the MS's next hop to a physical device in the test network. When you select this option, enter the IP address for the next hop in the adjacent field.

VLAN ID

Select the VLAN option and enter a VLAN ID to include a VLAN tag with the specified ID in every packet transmitted.

FA support is optional in the IPv4 HA Nodal test case and you can use a co-located care-of address in one of two ways:

• To simulate an MN attaching to a foreign network without FA mobility services. Each MN registers its co-located address directly with the HA SUT. In this case, Foreign Agent must be cleared. Specify the starting pool address in Co-Located Care-of Address.

• To simulate an MN attaching to a foreign network that requires FA registration for accounting or authorization purposes (Foreign Agent is checked).

You can use the Foreign Agent checkbox to include emulated FA nodes in the test. The MNs will register through the FA nodes rather than directly with the HA SUT, and will use the FA node's address as their care-of addresses unless Co-Located Care of Address is checked. Define the emulator on the Foreign Agent sub-tab.

NAT Traversal can be used (Enabled or Forced) when simulating a VPN configuration. This allows the MN to communicate with a host in a private network when the MN's co-located care-of address is not part of the private network's address space.

In Mobile IPv6 test cases, the test always begins with the MN attaching to a foreign link and attempting to register a care-of address with the HA SUT.

• Define the Starting Care-of Address with a valid pool address, and define the Starting Home Address with an address acceptable to the HA SUT.
• Define the Target Care-of Address for Mobile Node Mobility testing.

In a Returning Home mobility test, the home addresses must also be valid pool addresses.

• Learn more about IPv6 Addresses

In the IPv4 FA Nodal test case, a FA is the SUT and is always provisioned, except when Agent Discovery is enabled. You can use a co-located care-of address to simulate a MN attaching to a home network without HA mobility services. Each MN registers its co-located address directly with the FA SUT. Specify the starting pool address in Co-Located Care-of Address.

Related Measurements

When an invalid home address is used, error code 132 or 133 may be received in the Binding Acknowledgements received from the HA and recorded in the error counter measurements.

Configure the Mobile Subscriber Ethernet settings.

• Physical Interface

• # of Nodes: Specify multiple nodes with the Number of Nodes setting. The number of emulated nodes vary depending on the test application and the test system's licensed capacity.

• Starting IP Address

• Default Routing

• Next Hop IP Address

• Outbound Traffic Port

• Activation rate

• Deactivation Rate

Select the required method of VPN distribution mode, Round Robin or Exhaustive.

Enter the transaction rate per second.

Range : 0.001 to 3000.0 (managed by license)

Default: 1.0

Tcl Parameter: SbiTransRate

Select the SMS Source - Internal (Default) or SMPP GW. Available when SMS-SC is enabled.

When Internal is selected, select to Enter Starting SMS Delay (ms).

Range : 100 to 999999999

Default : 5000

Tcl Parameter: SmsSource

Tcl Parameter: StartingSmsDelayEn

Tcl Parameter: StartingSmsDelay

Enable IWF

MAP Operation

Delay for ReadForSM (ms)

Select to enable IWF (InterWorking Function). Available in SMS Network test case when SMS-SC, SMS-HLR and MSC for MAP-D or MAP-E.

When MSC is enabled, select the MAP Operation.

Options : UpdateLocationRequest, PurgeMS, MO-ForwardSM, MT-ForwardSM, Failure-MT-ForwardSM, Failure-MT-ForwardSM-RestoreData

When MAP Operation = Failure-MT-ForwardSM

Enter Delay for ReadyForSM in milliseconds.

Range : 0 to 10000

Default : 0

Tcl Parameter: SmsIwfEn

Tcl Parameter: SmsMapOp

Tcl Parameter: SmsDelayReadyForSm

Control Bearer to DSCP Assignments

Control Context to DSCP Assignments is available only when you select Data Traffic or External Data.

Tcl Parameter: CtlBearerToDscpEn

Select Bearer to DSCP (Differentiated Service Code Point) Assignments and enter/calculate the DSCP Assignments on the Context to DSCP Assignments window.

• Bearer: The value in the Bearer column depends on the Number of Primary PDP Contexts and Number of Secondary PDP Contexts you select.
• DSCP: Indicates the DSCP assigned to the traffic class during PDP context creation (valid value ranges from 0-63).
• Calculate: Select the Per Hop Behavior (PHB) and calculate the DSCP assigned to the PDP Context (as 6 bits).

PHB indicates an observable forwarding behavior applied at a Differentiated Service (DS)-compliant node to a DS behavior aggregate.

Tcl Parameter: QciToDscpMarkingsEn

Select a DSCP new value from the dropdownlist to change the default and assign a different DSCP value to the QCI.

• Qci:  Valid values are 1 through 255. You may modify all 255 QCI values using a Test Data File.
• DSCP Decimal: Valid values 1 - 63 (for use with Test Data File)
• DSCP String: Use the dropdown list to select an appropriate DSCP value for the QCI.

You can provision explicit values for each MS by using a Test Data File. Download an example QciToDscpMap.csv file by right-clicking the link below.

See Applying Parameter ValuesApplying Parameter Values.

• QciToDscpMap.csv

Defines the standard deviation as a percent of mean in the Normal distribution model.

Range: 0 — 100

Default: 0

limits the standard deviation from mean as a percent of mean in the Uniform and Poisson distribution models.

Range: 1 — 99

Default: 10

Related Measurements

All MN rate measurements are affected by Interval Distribution.

In a Continuous data test, you can use the checkbox to automatically include the effective DMF Client Port in the packet filters for all data connections. This option can only be used if none of the data connections is executing more than one DMF. If any of the connections is executing more than one DMF, you must define Starting Destination Port and Ending Destination Port and ensure that none of the ports used with other connections fall within that range.

Available on SGW Node TC when Sxa Interface to UP or Sxa+Sxb Interface to UP is enabled and on PGW Node when Sxb Interface to UP is enabled. If checked, displays TFT Setting for default bearers as well.

An "SDF Index" (Service Data Flow) field has been added for each TFT filter. If this field is set, the corresponding SDF level QoS will be used. Otherwise, the bearer or APN level QoS will be used, depending on whether it belongs to a GBR or Non-GBR bearer.

If default bearer TFT is not enabled, unmatched traffic (against dedicated bearer filters) will go on default bearer. If default bearer TFT is enabled for the uplink and/or downlink direction, unmatched traffic (against default and dedicated bearer filters) will be discarded.

A catchall filter (filter with nothing configured other than direction and precedence) is only allowed for default bearer. If you configure a catchall filter for a dedicated bearer, it will not be used or passed onto the UP side.

Prior to release 16.8, if you do not configure any downlink filters for a dedicated bearer, a downlink PDR without SDF filter will be created but with lower precedence than the default bearer downlink PDR. This PDR has been removed in order to support TFT setting for default bearer. Otherwise, downlink traffic will end up on a dedicated bearer if you configure no downlink filter for dedicated bearer and an unmatched downlink filter for default bearer. Downlink traffic should be discarded in this case. Consequently it is possible that you see no downlink PDR/FAR for a dedicated bearer if you do not configure any downlink filter.

If default bearer TFT is enabled, a "TFT Creation Delay Time" field has been added for each default bearer. If the value is set to 0, the default TFT info will be sent to the UP side in Sx Session Establishment Request. However, per 24.301 6.4.1.1, "The default EPS bearer context does not have any TFT assigned during the activation procedure", so default TFT info will NOT be sent to the UE side. This may create an unbalanced situation between the UE and the network. Alternatively, you can set it to a non-zero value. In this case, no TFT info will be sent to the UP side during default bearer activation. When the delay timer expires, PGW will initiate a bearer modification procedure that creates TFT setting for default bearer. The default TFT info will be sent to both the UE and UP side in the mean time.

Options: On, Off (default)

Available only for Bearer Modification TFT. Indicates the operation performed on the TFT as the option you select from the dropdown list. An Operation Code will be included for Bearer Modification TFT in SGW Nodal, and PGW Nodal when UE Initiates Dedicated Bearers is selected (see SGW Nodal Test Configuration, and PGW Nodal Test Configuration tabs).

Values: Create New TFT, Delete Existing TFT, Add Packet Filters to Existing TFT, Replace Packet Filters in Existing TFT, Delete Packet Filters from Existing TFT

Available only for Bearer Modification TFT on GTPv2 | Bearer Modification | Modified TFT Settings when your test case settings are as follows.

• Select Include in Bearer Modification Request to include information elements for a Bearer Modification TFT (displayed on the GUI) to be included in the Resource Modification Request.

• Clear Include in Bearer Modification Request selection if you do not require any information elements for a Bearer Modification TFT (displayed on the GUI) to be included in the Resource Modification Request.

Indicates the direction of the traffic flow in LTE testing and GGSN Nodal only. The options in the dropdown list are for Release 7 TFTs:

1. Pre-Rel 7

   Uplink (default)

   Downlink

   Bidirectional

 In LTE test cases, the valid range is 0 - 255.

SDF Index

Number of SDFs in the SDF Subpanel in PFCP Tab in Sxa/Sxb interface. (Service Data Flows)

Range: 1 - 15

Default: 1

Mobile Subscribers

The number of unique mobile subscribers (MSs) emulated during the test. At least one MS must be emulated in every test. It is also the number of simultaneous MS that can be supported by the server node. System resources are reserved for the provisioned number of sessions whether they are used or not.

Attach Start Delay (ms)

Enabled when RF UEs is selected - Only visible when RF feature license key is present

Numeric

Tcl Parameter: AttachStartDelay

MPLS

Select to include MPLS label in the GRE message.  The Protocol Type in the GRE header when you select MPLS is MPLS Label-Switched Packet.  When you do not select MPLS, the Protocol Type in the GRE header is Ethernet Bridging.

MPLS is not available when Tunnel Type is CAPWAP, as it applies only to GRE.

Click to use the Auto-Increment Format Wizard.

Range from 0 to 1048575

Default = 0

Tcl Parameter: Mpls

MAC Address

Indicates the MAC address of the UE.  The UE's Ethernet packet gets passed as payload of the GRE message.  This address is auto-incremented for UEs.

Default: 80:B0:3D:CF:A5:B0 (on Wifi Offload Gateway Nodal)

UE Random MAC Address

Select to choose a Random MAC Address. When selected, all the UEs will have a random MAC address.

The MAC address field will be grayed out.

Not available when AP Tunnel Type = DS Lite.

Tcl Parameter: UeRandomMacEn

MAC Address Increment

Enter an increment value used to increment MAC Address. Available if RF UEs is selected or if AP Tunnel type = GRE L2, CAPWAP, or NONE.

Range : 0 to 65535

Default : 1

Tcl Parameter: MacAddrIncrement

UE Next Hop MAC Address

In Wifi Offload Nodal test case, select and enter a valid MAC address.  This address is used as UE destination MAC Address for data traffic when AP Tunnel Type is GRE L2 or CAPWAP.

Not available when RF UEs is enabled or AP Tunnel Type = DS Lite.

Tcl Parameter: UeNextHopMacAddrEn

Tcl Parameter: UeNextHopMacAddr

UE Next Hop IP Address

In Wifi Offload Nodal test case, select and enter a valid IP address.  For CAPWAP tunnel type. when "Use ARP to acquire 802.11 Dest Addr" is enable, UE will send ARP to this IP address to acquires the destination MAC address. For NONE tunnel type, this IP address will be used as EU next hop Address.

Not available when RF UEs is enabled or AP Tunnel Type = DS Lite.

Tcl Parameter: UeNextHopIpAddrEn

Tcl Parameter: UeNextHopIpAddr

Assigned IPv4

Available when Data IPsec is checked and when Specify Mobile Subscriber APNs is not checked. Used to enter a non-zero IP in the Config Payload.

Enable to enter a Valid IPv4 Address.

Tcl Parameter: WfoMsApnAssignedIpv4En_0

Tcl Parameter: WfoMsApnAssignedIpv4_0

Assigned IPv6

Available when Data IPsec is checked and when Specify Mobile Subscriber APNs is not checked. Used to enter a non-zero IP in the Config Payload.

Enable to enter a Valid IPv6 Address.

Tcl Parameter: WfoMsApnAssignedIpv6En_0

Tcl Parameter: WfoMsApnAssignedIpv6_0

IP Address Type

In Wifi Offload Gateway Nodal TC, select the appropriate Address Type: IPv4, IPv6, Dual Stack.

When you select IPv4, UE Static IPv4, and UE DHCPv4 are available for selection.

When you select IPv6, UE Static IPv6, UE SLAAC, and UE DHCPv6 are available for selection.

When you select Dual Stack, UE Static IPv4, UE DHCPv4, UE Static IPv6, UE SLAAC, UE DHCPv6 are available for selection.

In SGW Nodal TC, select UE SLAAC to indicate that the UE support Stateless Autoconfiguration (SLAAC).

In IMS Nodal TC, select IPv4 or IPv6.

In AMF Nodal select IPv4 or IPv6 and it must match with PDU Type selection (IPv4 or IPv6) on Nas 5g Sm Tab.

Tcl Parameter: Iptype

First Dynamic Address Requested

Indicates supports for multiple dynamic address acquisition in sequence.

First Dynamic Address Requested indicates whether you select IPv4 or IPv6 as the first address to request.

The parameters are available configurable when you select IP Type as Dual Stack and as follows.

Delay Before IPv4/IPv6 Requested (ms)

Indicates the delay before requested IPv4 or IPv6 address. The address type delayed depends on your selection of the First Dynamic Address Requested.

• If you select IPV6 as the first requested addresses, then configure a delay before acquiring then IPV4 address.
• If you select IPV4 as the first requested addresses, then configure a delay before acquiring then IPV6 address.

Default value is 0indicates no delay between requesting dynamic addresses.  

Tcl Parameter: SecondDynamicAddressDelay

Default Value: 0

Range: 0 ~ 2147483647

UE Static IPv4/v6

Select to support static UEs over CAPWAP or GRE tunnel or without tunnel. Select the appropriate Address Type: IPv4 or IPv6, and enter the static IP address over the selected Tunnel Type (on the Test Configuration tab).

Tcl Parameters:

When you select UE Static IPv4, the following parameters are not available:

• UE SLAAC
• UE DHCP
• UE Graceful Shutdown

UE Target Static Ipv4/Ipv6

Available when UE Static IPv4/IPv6 is enabled. Must enter a valid address when MOBIKE is selected.

Tcl Parameters:

Selected by default depending on the PDU Type selected.  Allows the UEs to get IP addresses via DHCP.

Available in AMF Nodal / SMF Nodal to get IPv6 address of PDU Session via DHCPv6 procedure. When enabled, UE will get IPv6 Address of PDU Session only via DHCPv6 procedure.

Checkbox is not available in AMF Nodal when Test Activity is Inter Technology Mobility or Command Mode / Sequencer with Handoff Protocol other than None, N3IWF / TWIF  is enabled, SMF/UPF Node Emulation is enabled, PDU Type in NAS-5G/SM Tab is “IPv4”, Reserve PDU Session for SSC Mode 3 is enabled.

Checkbox is not available in SMF Nodal when UPF Node Emulation is enabled, PDU Type in NAS-5G/SM Tab is “IPv4”.

Available in AMF Node or gNB CU SA Nodal when SMF Emulation is enabled and N4 Interface configured for PFCP version >= 16.5.0 with IP6PL option selected. Not available when PGW-C Emulation is enabled in AMF Node / SMF Node / gNB CU SA Nodal.  

Tcl Parameter:

UE SLACC

UE SLACC with Managed address

In AMF Nodal, gNB CU SA Nodal, SMF Nodal and SGW Nodal TC, select UE SLAAC to indicate that the UE support Stateless Autoconfiguration (SLAAC). Available in AMF Nodal / SMF Nodal if UE DHVPv6 IP Address is enabled.

In AMF Node (with SMF emulation enabled), gNB CU SA Nodal & SMF Node TC, select UE SLACC with Managed address to indicate that SMF will assign IPv6 Address of PDU Session via SLAAC even if IPv6 Address allocation via DHCPv6 procedure is enabled. In other words, SMF will assign IPv6 Address of PDU Session via SLAAC during PDU session establishment procedure and allow UE to request IPv6 address allocation via DHCPv6 procedure. Available when UE DHVPv6 IP Address is enabled.

Tcl Parameter: UeSlaacEn

Tcl Parameter: UeSlaacManagedAddrEn

Tcl Parameter: UeSlaacRndAddrNum

Tcl Parameter: UeIpv6DadEn

Tcl Parameter: UeIpv6DadTime

Tcl Parameter:

UeDhcpv4ViaTunnelEn

UeDhcpv6ViaTunnelEn

Available for Mobility testing. Select to send a DHCP Release when during mobility testing.

• When you select UE Graceful Mobility, a DHCP Release is sent to the old SSID, and DHCP negotiation begins anew on the Target SSID, and the UE may receive a new IP address.

• When you do not select UE Graceful Mobility, a DHCP Request is sent with the UE’s existing IP address.

External DHCP Client

Select to use an external DHCP Client. Available when RF UEs and UEDHCPv4 are enabled.

When selected the DHCP interface is no longer available for input.

Tcl Parameter: WfoRfUeExternalDhcpEn

UE Authentication

Select to indicate the authentication performed. The available authentication options depend on the Tunnel Type you selected (Wifi Offload Gateway Nodal Test Configuration / Wifi Offload Gateway Node Emulator Configuration / SGW Nodal Test Configuration).

Tcl Parameter: UeAuthenticationType

Options: None (0); Radius (1); 802.1x (2); WISPR (3); Portal (4); Web Auth (5)

When you select RF UEs interface, options include None and Web Auth. If web Auth is selected, a new tab labeled Web Auth is enabled.

UE Authentication is required when you select the Tunnel Type as CAPWAP and UE Authentication.

Tcl Parameter: UeSupportArpHandlingEn

In Wifi Offload Node test case, select and enter a valid MAC address.  This address is auto-incremented for UEs. UE MAC Address is not available when AP Tunnel Type is GRE L3.

In Wifi Offload Gateway Nodal Test Configuration, enter a valid MAC Address with Colon or Dash delimiters. When AP Tunnel Type is NONE, enter 00:00:00:00:00:00 to use Network Devices/AP-WAN Node's Eth interface MAC Address.

You will get a warning that you can either click OK or Cancel to return to Gui. Select checkbox labeled "Do not show warnings again during this login session" to prevent showing warnings in all test cases for the remainder of the client session.

Default: 80:B0:3D:CF:A5:B0 (on Wifi Offload Gateway Nodal)

Tcl Parameter: UeMacAddr

Available when Tunnel Type is None on Wifi Offload Gateway Nodal Test Configuration tab. Select to force data to the Access Point's Next Hop (defined as per Outer IP Type of Service.). This is used only when the Tunnel Type is NONE.

In WiFi Offload Gateway Node test case, Default Bearers per Session is available when you select S2a to PGW or S2b to PGW options.

Select up to 2 Dedicated Bearers per Default from the list to specify multiple defaults per session.

Tcl Parameter: DefaultBearers

Options: 1 — 2

Default: 1

In WiFi Offload Gateway Node test case, Dedicated Bearers per Default is available when you select S2a to PGW or S2b to PGW options.

Select the Dedicated Bearers per Default from the list to specify multiple defaults per session.

Selecting Dedicated Bearers per Default allows you to select the number of Packet Filters and the requested uplink/downlink to be configured. A maximum of 11 Dedicated Bearers per Default is supported.

Tcl Parameter: DedicatedsPerDefaultBearer

Options: 1 — 11

Default: 1

Available when you select Portal authentication. Configure a timer that will keep the session(s) alive for the specified time.

Option: 0~65535

Default: 7200

Enter a value > zero to ensure an Encapsulated ARP (GRE or CAPWAP) for the UE address is sent form the GW after the provisioned time value for each of the UE's.

Option: 0 - 255

Default: 0

Tcl Parameter: UeInitArpTime

Tcl Parameter: RouterArpMacAddr

Enable to support random UE MACs.

Tcl Parameter: SupportRandomUeMac

Enabled when AP Tunnel Type = GRE L2. Enable to use UE SLACC with a Managed Address.

Tcl Parameter: UeSlaccManagedAddrEn

Add IMEI when SIP VOIP is enabled.

Range: 1 to 14 digits.

Tcl Parameter: Imei

Enter valid IPv4 address when SWu IPSec is enabled.

Tcl Parameter: UeSWuIpv4Addr

Select for a 5G Capable UE connecting to ePDG.

Enter PDU Session ID.

Range: 1 to 15

Default : 5

Tcl Parameter: Ue5gNon3gppAccessEn

Tcl Parameter: Ue5gNon3gppPduSessId

Available when Test Activity = Inter Technology Mobility, Handoff Protocol = WiFi and Initial Network = LTE on MME Nodal Test cnfg.

Select to maintain the same UE IP assigned by the PGW after it is handed over to WiFi ((Handover).

Tcl Parameter: UeIpAfterHandoverEn

Available when Test Activity = Inter Technology Mobility, Handoff Protocol = WiFi and IP Address Type= IPv6 on MME Nodal Test cnfg. 

Disabled for Command Mode with Wifi Offload Node Emulation.

Select to send Route Solicitation after UE handover from LTE to WiFi.

Available when Test Activity = Inter Technology Mobility, Initial Network = 5GS , Handoff Protocol = WiFi (N3IWF)or LTE and NAS-5G | SM = PDU Type = IPv6 on the AMF Nodal Test Cnfg.

Select to send Route Solicitation after UE handover from WiFi to NR or sending Router Solicitation after HO between LTE and NR or to send Route Solicitation after UE handover from NR to WiFi (through N3IWF).

Tcl Parameter: SendRsAfterHoEn

You can provision explicit values for the for Mobile Subscribers by using Test Data Files. Download a sample file by right-clicking the link below.

See Applying Parameter Values.

• Wifi Offload Gateway Nodal Parameters