About the MIP Revocation Test
With the MIP Revocation test, you can test the SUT's ability to request or respond to revocations. By running the test at various capacity levels and handoff rates, you can determine the maximum revocation rate that an SUT can support under a particular processing load.
The test begins by establishing sessions at the session connect rate. You have the option to begin the revocations as each session is started, or to wait until all sessions have been established before beginning to revoke the registrations. In both cases, the test waits for the defined delay time before executing the first revocation.
If you choose to start the revocations after all sessions are established, you can also define the rate used (revocations per second), and apply a distribution model to the revocation rate. Once all of the sessions have been established, the test waits for the delay time and then begins sending registration revocation requests (RRVs) at the defined rate.
If you start the revocations as each session is established, the test brings up a session, waits for the delay time, and then sends the registration revocation message. The revocation rate in this case is the session connect rate.
The test continues in this manner until all registrations have been revoked.
CDMA2000 Testing
The MIP Revocation test is available in the following test cases:
-
The CDMA HA Nodal test case tests an HA's ability to process revocations with emulated PDSN-FAs.
-
The CDMA FA Nodal test case tests a PDSN-FA's ability to process revocations from an emulated HA.
Mobile IP Testing
The MIP Revocation test is available in the IPv4 HA Nodal and CDMA/WiFi Convergence test cases. It tests an HA's ability to process revocations with emulated FAs or a PDIF.
Compatible Test Options
-
The Data Traffic option can be used to increase the SUT's processing load. Bearer traffic using the data protocol, volume, and rate that you define is transmitted through the established sessions, adding to the real-world activity model.
-
The SUT Query option can be used to monitor the SUT CPU usage or dynamically adjust the connect and disconnect rates to based on the CPU usage.