Proprietary Extension Settings

In some test cases, you can define proprietary extended information elements and select the control plane messages that will include the extensions. Check the Proprietary Extensions box and then click the Settings... button to open the Proprietary Extension window.

The window is made up of two panes. The upper pane contains the message selection checkboxes and you can enter the extension information, in hexadecimal, in the lower pane. You can enter up to 255 bytes (512 characters) in the exact form that will be used in the message. The same extension values will be used for every MN session.

CDMA Testing

You can define MIP extensions on the MIP tab and RP extensions on the RP tab (and on the Handoff RP tab when you run a handoff test activity). Each tab is handled independently: you can define the same values on both tabs, different values on each tab, or omit the extensions entirely on any tab. The values that you define are used for all MNs for the life of the test.

On the RP tab

Use the checkboxes to specify which Airlink messages will include the extensions:

Setup — Include the extensions in the Setup Airlink record that is sent when the MN session is initially requested.
Start — Include the extensions in the Active-Start Airlink record that is sent when the MN session is connected.
Stop — Include the extensions in the Active-Stop Airlink record that is sent when the MN session is disconnected.
In Main Service Instances — Include the extensions in all selected messages associated with the MN's main session.
In Auxiliary Service Instances — Include the extensions in all selected messages associated with the MN's auxiliary instances.

On the MIP tab

Use the checkboxes to specify which Mobile IP messages will include the extensions:

Agent Solicitation — Include the extensions in solicitations sent by an FA node.
Agent Advertisement — Include the extensions in advertisements sent by an HA node.
Registration Request — Include the extensions in RRQ messages sent by an FA node.
Registration Request Reply — Include the extensions in RRP messages sent by an HA node.
Registration Revocation — Include the extensions in RRV messages sent by a node.
Registration Revocation Ack — Include the extensions in RRVA messages sent by a node.

DHCP Services

You can define IPv4 DHCP extensions, which are used with all selected server responses.

DHCP Server Node Parameters

DHCP Services

Offer — Include the extensions in offer messages sent by the node.
ACK — Include the extensions in ACKs sent by the node.
NAK — Include the extensions in NAKs sent by the node.

GPRS Testing

You can define GTP extensions on the GTP tab. The same values are used with all primary and secondary PDP contexts for the life of the test.

GTP Parameters

Tcl Parameter: GtpExtEn

GTP

Use the checkboxes to specify which messages with include the extensions:

Create — Include the extensions in the Create PDP Context Request that is sent when the context is initially requested.
Update — Include the extensions in the Update PDP Context Request that is sent when the context is handed off or when the QOS profile is updated.
Delete — Include the extensions in the Delete PDP Context Request that is sent when the context is disconnected.
In Primary Contexts — Include the extensions in all requests associated with primary PDP contexts.
In Secondary Contexts — Include the extensions in all requests associated with secondary PDP contexts.

LTE Testing

You can define GTP extensions on the GTPv2 tab. The same values are used with all Default and Dedicated bearer contexts for the life of the test.

GTP Parameters

Tcl Parameter: Gtp2ExtEn

GTPv2

Use the checkboxes to specify which messages with include the extensions:

Create Session — Include the extensions in the Create Session Request that is sent when the session is initially requested.
Delete — Include the extensions in the Delete Session Request that is sent when the session is disconnected.
Create Bearer — Include the extensions in Create Bearer Request associated with Bearer Activation procedure.
Delete Bearer — Include the extensions in Delete Bearer Request associated with Bearer Deactivation Procedures (for example, a PGW or MME initiated bearer deactivation procedures).

In addition to the messages included, you may specify the following for each message:

Type: Enter the message type value to be included in the message header.
Instance: Enter the message Instance value to specify which message instance occurrence should be included. This instance value along with the Type identifies the default message being included.
Comprehension Required: Select to indicate that the entire message body is required.

NOTE: A combination of an Instance value and Type can appear only once in the Message. Valid range is between 0 and 10. An Instance value 0 indicates all occurrences of that message Type and value 1-10 indications the nth occurrence of that message type only.

See also Message Editor.

Mobile IPv4 Testing

You can define MIP extensions on the MIP tab (see the CDMA MIP options above). The values that you define are used for all MNs for the life of the test.

SGW PMIPv6 Testing

Used to define the Vendor Specific Mobility Options for PMIPv6 Proprietary Extensions on the PMIPv6 tab.

Tcl Parameter: S2aPmip6ExtEn

PMIPv6 Parameters