The IP Application Node Test Case
Use the IP Application Node test case with the Network Host test case to test a Content Gateway using various data protocols that are transported by either IPv4 or IPv6. The test system emulates the mobile nodes (MN) from the aspect of creating unique source IP addresses for each MN. It also generates data traffic towards a Network Host, and listens for and responds to messages received from the Network Host.
The IP Application Node test case supports Pilot Packet which are generated when the following events are detected on PCEF (PGW or HA).
- NAT chunk is allocated to a session
- NAT chunk is de-allocated
- IPv6 address is allocated to a session
- IPv6 address is de-allocated
- Non-NAT IPv4 address is allocated to a session
- Non-NAT IPv4 address is de-allocated
Below is a High Level Diagram of Pilot Packet emulation.
The Pilot Packet Receiver is the SUT and PCEF emulator generating pilot packets is a function of the IP Application Node test case.
| NOTE: Some SUTs may handle both data traffics and pilot packets. |
With this test cases, you define:
-
The number of MNs (clients) and their IP addresses
-
The rates used to start and stop data traffic, and an optional rate distribution model
-
The Data Message Flows executed by the MNs
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
Testing Terminology
The test definition and measurements used in this test system refer to "session" volumes and rates. A session normally describes a stateful connection between an MN and a servicing node. Since IP does not support a session as such, the following definitions of session, connect, established, disconnect, and pending apply when testing with IP:
-
An IP session is connected, or started, when the client node (MN) begins to execute the first Data Message Flow. When IPSec is used, message flow execution does not begin until the IPSec SAs are successfully negotiated. The client node remains in the started or established state until the test is stopped, or until the end of an iterative test run, when it is disconnected, or stopped. The number of simultaneous sessions equates to the number of client nodes that have been started but have not been stopped.
-
An idle client node, one that has not been started for the first time or one that was stopped and will be started again in an iterative test, is in the pending state.
Test Options
-
Since the purpose of this test case is to generate bearer plane traffic, the Data Traffic option is always used.
-
Enable the DHCP Client to obtain IP addresses for the Client Nodes from a DHCP server.
-
Enable the AAA option to generate authentication and accounting traffic towards AAA servers.
-
Encrypt Data Traffic with the optional Dynamic IPSec feature.
-
Enable SIP VOIP to support SIP and RTP-based Voice over
-
Enable Pilot Packet and configure the events detected on PCEF (PGW or HA).
-
Run a remote Network Host on the same test server.
Measurements
Measurements collected for the basic IP Application Node test case are reported on the following tabs:
Additional measurements may be available depending on the test activity executed with the test case.