The test cases provided with the CDMA2000 application allow you to test a PDSN, a PDSN-FA, or an HA in a standalone (nodal) configuration. You can also test one or more PDSN-FAs with a primary and secondary HA in an end-to-end configuration. Data plane traffic can be added to a test in any of the configurations.
With these test cases, you define:
The network environment and the specific access model
The session volume and rates, and an optional rate distribution model
Control protocol attributes and behaviors
Measurements collected for these test cases include:
Counters that record the number and types of messages sent and received
Average response times for the different types of messages received from an SUT
Errors encountered during the test
Session state and rates
An MN session is the result of an MN successfully registering with a network element and establishing a main service instance, or the result of an MN successfully establishing an auxiliary service instance. In a Simple IP model, the MN registers with a PDSN in its home network; in a Mobile IP model, the MN registers with a PDSN-FA in its home network or in a visited network after having been authorized to do so by its HA. The terms used for the various states that a session transitions through are defined as follows:
When the test begins, the test system reserves the resources necessary for the total number of MN sessions defined (IP addresses and other unique identifiers, for example), and the MN side of the sessions are initiated and placed in the pending state.
A pending MN session is started with a registration request from the PCF node.
The session is connected and established with a successful registration reply.
If a session fails during or after establishment, and the retry failure rate reaches 100%, the session is left in the pending state.
An established session is disconnected with a termination that can originate from the MN or a network element.
If a session is disconnected as part of a test cycle and will be re-connected, the test system retains the session's resources for later use, and the session enters the pending state.
When the disconnect occurs at the end of the test, the test system releases the session's resources as part of the test clean up.
When your test activity measures processing capability rather than rates, you can expand the scope of the test:
Add Data Traffic to the test to more closely simulate a live network using various wireless applications and protocols.
Encrypt Data Traffic with the optional Dynamic IPSec feature.
Use the SUT Query option to monitor the CPU utilization of an SUT, and determine the amount of activity that the SUT can handle within a given CPU threshold.
Test a PDSN-FA and an HA in tandem in any of the supported Mobile IP access models. A second PDSN-FA, used for mobility handoffs, can be included in the test as can a secondary HA. The test system emulates the mobile nodes (MN) from the aspect of creating unique identifiers for each MN node, and emulates functional PCF nodes that service MN sessions. The PCF nodes generate traffic towards the PDSN-FA, and listen for and respond to messages from the PDSN-FA.
Measurements collected for the basic End-to-End test case are reported on the following tabs:
Additional measurements may be available depending on the test activity and options executed with the test case.
Test a PDSN-FA in any of the supported Mobile IP access models. The test system emulates the mobile nodes (MN) from the aspect of creating unique identifiers for each MN, emulates functional PCF nodes that service MN sessions, and emulates an HA. The PCF nodes generate traffic towards the PDSN-FA, and listen for and respond to messages from the PDSN-FA. The HA node listens for and responds to messages from the PDSN-FA.
Measurements collected for the basic FA Nodal test case are reported on the following tabs:
Additional measurements may be available depending on the test activity and options executed with the test case.
Test an HA in any of the supported Mobile IP access models. The test system emulates the mobile nodes (MN) from the aspect of creating unique identifiers for each MN, emulates functional PCF nodes that service MN sessions, and emulates PDSN-FAs to host the sessions. The PDSN-FA nodes generate traffic towards the HA SUT, and listen for and respond to messages from the HA.
Measurements collected for the basic HA Nodal test case are reported on the following tabs:
Additional measurements may be available depending on the test activity and options executed with the test case.
Test a PDSN in the basic Simple IP access model. The test system emulates the mobile nodes (MN) from the aspect of creating unique identifiers for each MN, and emulates functional PCF nodes that service MN sessions. The PCF nodes generate traffic towards the PDSN, and listen for and respond to messages from the PDSN.
When you include Data Traffic in the test, the traffic can run over either IPv4 or IPv6.
Measurements collected for the basic Simple IP test case are reported on the following tabs:
Additional measurements may be available depending on the test activity and options executed with the test case.
Test a PDSN in the Simple IP VPN access model, or up to two PDSNs in the Simple IP VPRN access model. The test system emulates the mobile nodes (MN) from the aspect of creating unique identifiers for each MN, emulates functional PCF nodes that service MN sessions, and emulates the private network endpoint of the VPN tunnel, the Secure Gateway. The PCF nodes generate traffic towards the private network, and listen for and respond to messages from the PDSN. The Secure Gateway node negotiates the VPN tunnel with the PDSN.
Measurements collected for the basic Simple IP VPN test case are reported on the following tabs:
Additional measurements may be available depending on the test activity and options executed with the test case.