The test cases provided with the Mobile IP application allow you to test an FA, HA or a CN in a standalone (nodal) configuration, or an FA and HA in an end-to-end configuration. An FA can be tested in an IPv4 network, an HA can be tested in either an IPv4 or IPv6 network, and a CN can be tested in an IPv6 network. Bearer plane traffic can be added to any of the test cases.
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 an HA, with or without the involvement of an FA. 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 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.
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 request that originates from the MN.
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 PDIF-FA and optional HA in a WLAN access model. The test system emulates the MNs and can emulate an HA. IKEv2 with MOBIKE included for mobility support. The MNs initiate IPSec connections with the PDIF-FA and attempt to register with an HA. If your test system is also licensed for the CDMA2000 application, you can use the Inter-Technology Mobility and the Session Loading With Mobility test activities to simulate handoffs between WiFi and CDMA2000 networks.
Measurements collected for the basic 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.
The CDMA/WiMAX Convergence test activities are used to simulate handoffs between WiMAX and CDMA2000 networks. The Inter Technology options are only available when you are licensed for both WiMAX and CDMA2000 applications. Valid MIP Scheme is CMIP for both Inter Technology Mobility and Session Loading With Mobility test configurations.
PCF Node
Base Station (R6) Node
SUTS - FA, ASN Gateway
Measurements collected for the basic 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 IPv4 access models. The test system emulates the MNs and can emulate FAs to provide mobility support. The MN or FA nodes generate control traffic towards the HA, and listen for and respond to messages from the HA.
Measurements collected for the basic 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 FA in any of the supported IPv4 access models. The test system emulates the MNs and can emulate HAs to provide mobility support. The MN or HA nodes generate control traffic towards the FA, and listen for and respond to messages from the FA.
Measurements collected for the basic 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 with any of the MN options provided. The test system emulates the MNs and a CN. Both can generate traffic towards the HA, and listen for and respond to messages from the HA.
Measurements collected for the basic 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 CN for Mobile IPv6 compliance by using Route Optimization with Data Traffic. The test system emulates the MNs and the routing functionality of an HA. The MNs generate traffic towards the CN, and listen for and respond to messages from the CN.
Measurements collected for the basic 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.
Simulate a CN in a separate test case that can be executed on a different test server than the IPv6 HA Nodal test case, doubling the Data Traffic capacity of the test. The CN acts as a Network Host and listens for and responds to Binding Update messages from the MNs when Route Optimization is used.
Measurements collected for the test case are reported on the following tabs:
|