Session Loading With Mobility Settings


Use these parameters to define the session loading cycle and mobility events for your test. They are accessible by clicking the Settings... button in the Test Activity pane when Session Loading With Mobility is selected from the Test Activity drop-down list. An additional tab may be added to the test case that allows you to define the control protocol parameters used with the handoff node or SUT.

Each MN session is timed independently. If you define a cycle wherein the pending and hold times are shorter than the time required to establish all of the MN sessions, the SUT is constantly connecting, handing off, and disconnecting sessions.

NOTE: Mobility test handoff rates may not be able to reach or sustain the maximum activation rate allowed for Capacity tests.

 

Parameter Index


Session Pending Time

The number of seconds a session is left idle before it is re-connected. This timer begins when the session is disconnected after the Session Hold Time expires.

IMPORTANT: When Data Traffic is used in the test, the Session Pending Time must allow for enough time to release the data resources before re-connecting the session. If the pending time is not long enough, the session will not be able to establish data traffic when it is re-connected.

The Session Pending Time should be at least twice the slowest Transaction Rate plus .5 seconds. For example, if the Transaction Rate is .1 (one transaction every 10 seconds), the Session Pending Time should be at least 21 seconds.

Range: 15 — 100,000 (as of release 16.6, the minimum value supported is 15 (used to be 1))

Default: 1000

^ Back to Top


Session Hold Time

The number of seconds a session is maintained in an established state before being disconnected. This timer begins when the final handoff is complete. The test may generate additional control or data traffic, depending on the capability of the test case, during the hold time.

Range: 15 — 100,000 (as of release 16.6, the minimum value supported is 15 (used to be 1))

Default: 1000

^ Back to Top


Ensure Constant Session Loading

When this box is checked, the test system will validate that the values you entered for Session Pending Time and Session Hold Time will result in a constant load on the SUT. Example:Example:

Assuming that the test connects 200,000 MN sessions (including all PDP contexts or service instances) at a rate of 1,000 sessions/second, 200 seconds are required to connect all of the sessions. To achieve a balanced load, sessions must be active for 100 seconds and idle (Session Pending Time) for 100 seconds.

During the 100 seconds that a session is active, handoffs are performed and then the session is maintained for the hold time. If 2 handoffs are performed with a Handoff Time of 30 seconds, 60 seconds are required to process the handoffs, leaving 40 seconds for the Hold Time.

The hold timers in the first sessions start to expire while the remaining 100,000 sessions are being connected and handed off. By the time all of the 200,000 sessions have been connected for the first time, the pending timers in the first sessions start to expire, and they begin to be reconnected at the same rate that the later sessions are being disconnected.

The result is a balanced session loading cycle with 100,000 active sessions and 100,000 idle sessions at any given time. Every second 1,000 sessions are connected, 1,000 sessions are handed off, and 1,000 sessions are disconnected.

If hold time + pending time + (Number of Handoffs * Handoff Time) = total activation time, the settings are accepted when you click OK. Otherwise, a pop-up window informs you that the calculation was invalid. When the box is cleared, you can enter any valid value in the timers.

^ Back to Top


Handoff Time (ms)

The number of milliseconds to wait before initiating a session's first handoff and the delay between handoffs if the test performs multiple handoffs. This timer begins when the session is connected (first handoff) or when the previous handoff is complete (multiple handoffs).

Range: 1 — 10,000,000

Default: 60,000

^ Back to Top


  Number of Handoffs

The number of handoffs that will be performed with each MN session. If more than one handoff is defined, Handoff Time defines the delay between handoffs.

Range: 1 — 10,000

Default: 2

^ Back to Top


  Mobility Type

The type of handoffs that will be performed. The selections in this list vary depending on the test case. If only one option is valid, that option is displayed and is not selectable.

ASN and CSN Nodal Testing

Options:

This option supports the Network triggered handoff procedure in Rel. 1 Version 1.3. If selected, the BS will not initiate any handoffs, but will respond to a Handoff Directive message from the ASN GW to start the handoff procedure.

Default: Uncontrolled Handoff

The Inter-ASN Gateway available in the ASN Nodal Test Case supports ASN Gateway's ability to process handoffs between two SUTS.

CDMA2000 Testing

Options:

Default: Inter-PDSN (where available)

GPRS Testing

Inter-SGSN is the only option available in the GPRS test case. You can define a Mobility SGSN Node Group that will receive the handoff sessions, and provision the GTP parameters for the handoff SGSNs on the Handoff GTP tab.

IP Data Testing

The type of handoffs that will be performed in a PDG Micro-Mobility test case.

If Mobile Node is selected, you can define the Starting Client IP Address #2 and network mask that form the pool of addresses to be used for the handoffs. See Handoff Test Settings for important notes regarding address format.

Mobile IP Testing

The type of handoffs that will be performed in an IPv4 HA Nodal or CDMA/WiFi Convergence test case.

Options:

Default: Inter-FA

MME Nodal testing

The type of handoffs that will be performed in a MME-Nodal test case.

When you select Intra-MME and X2 Interface, you may select only either Single Handoff or Continuous Handoff, When Session Started.

SGW Nodal Testing

HSGW Nodal Testing

The following types of handoffs will be performed in a HSGW-Nodal test case.

HNB Testing

During HNB testing, Intra HNB GW type of handoffs will be performed.

^ Back to Top


Disconnect Initiated By

Use the drop-down list to select the emulated mode for disconnecting sessions in a CDMA2000 or GPRS test.

CDMA2000 Testing

Options:

Default: Mobile Node

GPRS Testing

Options:

Default: Mobile Node


CDMA Testing

Support Fast Handoff

Use the checkbox to enable fast handoff support. In a fast handoff, the MN's PPP session is maintained throughout the handoff.

Activate Dormant Session on Handoff

Use the checkbox to include an Active Start Airlink record in all handoff registration requests. When the box is cleared, dormant sessions will remain dormant.

^ Back to Top


UMTS Testing

Perform Serving RNS Relocation Procedure

In a UMTS test case, you can use this checkbox to trigger the Serving Radio Network System (SRNS) relocation procedure and simulate RAN-initiated handoffs between RNCs.

When performing UMTS Mobility testing using MXP test Server (STC Chassis), Perform serving RNS Relocation Procedure is selected by default.

Related Measurements:

Perform PS Handover Procedure

In a UMTS Gb interface test, you can use this checkbox to trigger an inter-BSS or Gb-Iu handoff initiated by the SGSN.

Related Measurements