The ASN Nodal Test Case
The Access Service Network (ASN) Nodal test case allows you to test an ASN Gateway (ASN-GW). The test system emulates the Mobile Subscriber Stations (MSS) from the aspect of creating unique identifiers for each mobile subscriber, and emulates functional Base Station (BS) nodes that service the MSS contexts. The BS nodes generate traffic towards the ASN-GW, and listen for and respond to messages from the ASN-GW. The test system also emulates the Connectivity Service Network (CSN), AAA Server, Home Agent (HA), and Network Host.
End-to-End Testing
The ASN Nodal test case is, by default, an end-to-end test. That is, it tests the ASN Gateway and CSN together, as shown in the following figure:
ASN Nodal Testing
If you select HA Node Emulation, the test becomes an ASN nodal test. That is, it tests/isolates the ASN Gateway.
The following interfaces are supported for testing the ASN Gateway:
R1 – MSS-BS interface
R3 – ASN Gateway-HA (Emulated)
R6 – BS-ASN Gateway interface: R6 represents Control and Bearer Plane protocols for communication between the BS and the ASN-GW. The Bearer Plane consists of intra-ASN datapath between the BS and ASN gateway. The Control Plane includes protocols for datapath establishment, modification, and release control in accordance with the MS mobility events.
With this test case, you define:
Identifiers for the MSS and BS nodes
The session volume and rates, and an optional rate distribution model
The EAP authentication type
The MIP scheme
Measurements collected for this test case 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
MSS context state and rates
Test Terminology
An MN session is the result of a mobile subscriber successfully registering with its HA and establishing an MSS context. The phrases MN session and MSS context are used interchangeably in this documentation, as are Mobile Subscriber Station and Mobile Node (MN). 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 MSS contexts defined (MSS 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 the attempt to attach to an ASN.
The session is connected and established with a successful attach.
If a session fails during or after establishment, and all retry attempts have been exhausted, 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 a disconnect occurs at the end of the test, the test system releases the session's resources as part of the test clean up.
Test Options
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.
Enable the DHCP Client to obtain IP addresses for MSS contexts from a DHCP server and test the SUT's ability to act as a Relay Agent.
NOTE: DHCP configuration is not supported for Client MIP. It is only available for Proxy MIP and Simple IP, and it is mandatory. |
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.
Measurements
Measurements collected for the basic ASN 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.
Base Station Node