The GGSN Nodal test case provided with the GPRS application allows you to test a GGSN in a standalone (nodal) configuration. The test system emulates the mobile nodes (MN) from the aspect of creating unique identifiers for each mobile subscriber and associated primary PDP and secondary contexts, and emulates functional SGSN nodes that service the PDP contexts. The SGSN nodes generate traffic towards the GGSN, and listen for and respond to messages from the GGSN.
With this test case, you define:
The network environment
The session volume and rates, and an optional rate distribution model
Control protocol attributes and behaviors
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
PDP context state and rates
An MN session is the result of a mobile subscriber successfully registering a PDP context with a GGSN. The phrases MN session and PDP context are used interchangeably in this documentation, as are mobile subscriber and mobile node (MN). Each primary or secondary PDP context associated with one mobile subscriber is recognized as one MN session. 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 PDP contexts 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 SGSN node.
The session is connected and established with a successful registration reply from the GGSN.
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.
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 primary PDP contexts from a DHCP server and test the SUT's ability to act as a Relay Agent.
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.
Generate S-CDRs with the optional GGSN G-CDR Validation feature. If you also purchased the CGF Emulation feature, you can validate the contents of G-CDRs.
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.