Use these timers to define the session loading cycle for your test. They are accessible by clicking the Settings... button in the Test Activity pane when Session Loading Test is selected from the Test Activity drop-down list.
Each MN session is timed independently. If you define a cycle such that the pending and hold times are shorter than the time required to establish all of the MN sessions, the SUT is constantly connecting and disconnecting sessions.
You can change both the pending time and the hold time while the test is running.
When accounting transactions are used in a AAA Server Nodal test case, the Session Hold Time can affect the accounting message cycle. It takes precedence over the Started Time, and if the hold time is shorter than the Interim Update Time, no update messages will be sent.
The number of seconds a session is left idle before it is re-connected.
|
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
The number of seconds a session is maintained in an established state before being disconnected. The test may generate additional control or bearer plane 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
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 100,000 MN sessions (including all PDP contexts or service instances) at a rate of 1,000 sessions/second, 100 seconds are required to connect all of the sessions.
When the Session Hold Time and Session Pending Time are 50 seconds, the hold timers in the first sessions start to expire while the remaining 50,000 sessions are being connected. By the time all of the 100,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 50,000 active sessions and 50,000 idle sessions at any given time. Every second 1,000 sessions are connected and 1,000 sessions are disconnected.
If hold time + pending 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.
Ensure Constant Session Loading and Load Test Dedicated Bearers Only are mutually exclusive.
Tcl Parameter: EnsConstSesLoad
Selecting Load Test Dedicated Bearer Only ensures that the default bearer is not torn down while the dedicated bearer is activated, modified or deactivated during SGW Nodal testing.
Load Test Dedicated Bearers Only is only visible when Dedicated Bearers Per Default is > 0 on the Mobile Subscriber pane of the Test Configuration tab.
Ensure Constant Session Loading and Load Test Dedicated Bearers Only are mutually exclusive.
Tcl Parameter: DedBearerSessionLoading
Type: True/False
Default: False
| NOTE: When you select Perform Dedicated Bearer Session Loading only, you must provision Activation Rates and Deactivation Rates. |
Use the drop-down list to select the emulated mode for disconnecting sessions in a CDMA2000, GPRS, or LTE test.
Options:
| Mobile Node |
Stops sessions from the Traffic Layer. Data traffic stops -> MIP Layer stops (optional, if this layer exists) -> PPP Layer stops -> RP Layer stops. |
| Mobile Node PPP |
Stops sessions from PPP Layer. PPP Layer stops -> RP Layer stops. The MIP Layer (if it exists) disconnects only when its timers expires. |
| PCF | Stops sessions from RP Layer. Both MIP Layer (if it exists) and PPP Layer disconnects only when their timers expires. |
Default: Mobile Node
Options:
Mobile Node — Emulates a disconnect by the mobile node, with the PPP or IPv4 layer initiating the disconnect.
SGSN — Emulates a disconnect initiated by the SGSN at the GTP layer.
Default: Mobile Node
Options:
Mobile Node — Emulates a disconnect by the mobile node, with the IPv4/IPv6 layer initiating the disconnect.
HSS — Emulates a disconnect by HSS with eNodeB initiating disconnect via MME.
MME — Emulates a disconnect initiated by the MME.
Options:
Mobile Node — Emulates a disconnect by the mobile node, with the IPv4/IPv6 layer initiating the disconnect.
Use the checkbox to set the session loading level in a UMTS test.
When the box is cleared (default), the session loading cycle begins with an MN attach and ends with an MN detach. The Session Hold Time begins when the MN is successfully attached, and the MN is detached when the hold time expires. PDP contexts may or may not be included in the test. If they are included, any active contexts are deleted when the hold time expires and then the MN is detached.
When the box is checked, the session loading cycle begins with PDP context activation and ends with context deactivation. The Session Hold Time begins when the last context is activated, and the Session Pending Time begins when the last context is deactivated. The MNs will remain attached through the life of the test.