PMIPv6 Tab
Click here to see this page in full context

Landslide Performance Test System – Release 24.3 September 2024

PMIPv6 Tab

The PMIPv6 tab defines the PMIP interface (S5/S8) between the SGW and PDN-GW during the LTE PGW and SGW test cases.  During SGW Nodal Command Mode and Inter-Technology Mobility testing, the PMIPv6 tab defines the S2a interface (PMIP) between the emulated HSGW Node and PDN-GW SUT.

In MME Nodal test case, the PMIPv6 tab defines the PMIP interface (S2a) when Inter Technology Mobility Handoff Protocol is eHRPD (UE interfaces with S2a via Target HSGW SUT).

In HSGW Nodal testing, the PMIPv6 tab also defines the PMIP interface (S2a) between HSGW SUT and LMA Node. PMIPv6 IPSec requires a Dynamic IPSec license and its use is optional.

In PGW Node testing, the PMIPv6 tab defines the PMIP interface when Interface is S2a/S2b or S5/S8 and Protocol is PMIPv6. PMIPv6 IPSec requires a Dynamic IPSec license and its use is optional.

In PGW Nodal and SGW Nodal testing , the PMIPv6 tab defines the PMIP interface when Interface is S2a/S2b or S5/S8 and Protocol is PMIPv6 or Interface is NEMO and protocol is PMIPv6. PMIPv6 IPSec requires a Dynamic IPSec license and its use is optional.

In SGW Node testing, the PMIPv6 tab defines the PMIP interface when S5/S8 Protocol is PMIPv6.

Proxy Mobile IPv6, a network-based mobility management protocol, enables the mobility entities involved, the Mobile Access Gateway (MAG) and the Local Mobility Anchor (LMA), to dynamically setup tunnels and manage mobility for a mobile node within the Proxy Mobile IPv6 domain.

Parameter Index

APN Assignments
 

Non-3GPP MIPv6 Vendor Specific Options

  

Related Measurements

Measurements collected for Mobile IP related processing are reported on the Mobile IP report tab.

NOTE: TCL Parameters will prefix with Memo when PMIPv6 Tab is used in the NEMO Interface.

Version PMIPv6 Version (29.273)

Select the PMIPv6 for the Local Mobility Anchor (in HSGW Nodal testing)/ Mobile Access Gateway (SGW Nodal testing).

Options: 8.1.0/Mar2009, 8.2.0/Jun2009, 8.3.0/Sep2009, 8.4.0/Dec2009, 8.5.0/Apr2010, 8.6.0/Sep2010, 8.7.0/Dec2010, 9.3.0/Jun2010, 9.4.0/Sep2010, 9.5.0/Dec2010, 9.7.0/Apr2011, 10.5.0/Mar2012, 11.4.0/Dec2012

Default: 8.7.0

Tcl Parameter:

Pmip6Version

S2aPmip6Version

NemoPmip6Version

 
Starting MS Charging ID

In HSGW testing, enter the Starting MS Charging ID for the Local Mobility Anchor. It is only available when version 8.2.0 is selected.

Tcl parameter:

Pmip6MsChargingId

NemoPmip6MsChargingId

 
LMA On-Link Prefix Router Address

Enter the LMA router address prefix used.

Tcl Parameter:

Pmipv6haprefix

NemoPmipv6haprefix

 
IPv4 Default Router Address

This is the UE's IPv4 default router address set by the LMA. Enter the default router address.

Tcl Parameter:

Pmipv6LmaRouterAddr

NemoPmipv6LmaRouterAddr

 
Address Key Type

Indicates Key Type for the IPv4 Default Router Address.

Range: 1 - 255

Default: 31

Tcl Parameter: PmipV4DefRouterAddrKeyType
Access Technology Type

Access Technology Type is set to indicate the Radio Access Technology type. Select the Access Technology Type from the dropdown list.

When Test Activity on the SGW Test Configuration tab is Inter-Technology Mobility and handoff protocol is eHRPD, the Access Technology Type available is only 3GPP2 eHRPD.

Tcl Parameter:

Pmip6AccessType

S2aPmip6AccessType

NemoPmip6AccessType

 

 

^ Back to Top

MN-NAI

Defines the NAI used in the registration messages to identify the MN. You can use a static NAI for one MN node, or configure unique extension values with the Auto-Increment feature  for all MN nodes.

IMPORTANT: When you use an incrementing NAI extension with an HA node in an FA Nodal test, you must specify the starting value; otherwise, the corresponding NAI extensions provisioned for the HA node will continue incrementing from the last MN value.

In a test with 10 MN sessions for example, somename#(0)@sometext produces somename0@sometext through somename9@sometext values for both the MNs and the HA. If you used somename#@sometext, the MNs are provisioned with somename0@sometext through somename9@sometext, but the HA is provisioned to accept somename10@sometext through somename19@sometext.

Range: N/A

Default: N/A

Tcl Parameters:

Pmip6MnNai

S2aPmip6MnNai

NemoPmip6MnNai

 

Related Measurements

An emulated HA will reject registration requests received with an invalid NAI extension and will reply with an error code value of 129. These errors are reported on the Mobile IP and Open RP tabs as HA Admin Prohibited (129).
Charging Characteristics

In PGW Nodal testing, the Charging Characteristics informs both the SGW and PGW of the rules for producing charging information based the values you configure in the related parameters.

Select to provision the Charging Characteristics values.

Range: 0 - 15

Default: 1

Value: True/False

Tcl Parameters:

Pmip6IncChargeCharacteristics

Pmip6ChargeCharacteristics

S2aPmip6IncChargeCharacteristics

S2aPmip6ChargeCharacteristics

 

NemoPmip6IncChargeCharacteristics

NemoPmip6ChargeCharacteristics

 
Handoff Indicator

Handoff Indicator option is set to indicate attachment over a new interface as no Handover indication is specified in the Attach type.  Select the required indicator to be reported.

When Test Activity on the SGW Test Configuration tab is Inter-Technology Mobility and handoff protocol is eHRPD, the Handoff Indicator options is restricted to Between 2 different I/F of the mobile node (2).

 Options:

  • Attachment Over a New Interface (1)
  • Between two different I/F of the mobile node (2)
  • Between mobile access gateways on same I/F (3)
  • State Unknown (4)
  • State not changes (re-registration) (5)

Tcl Parameter:

Pmip6HandoffIndicator

NemoPmip6HandoffIndicator

 
Serving Network

In PGW Nodal test case and the SGW Nodal test case, the Serving Network identifies the serving network the UE (mobile subscriber) is attached to.

Tcl Parameter: Pmip6IncServingNetwork

Tcl Parameter: S2aPmip6IncServingNetwork

  • MCC defines the mobile subscriber's country of domicile.

Range: 000 — 999 (leading zeros are retained)

Default: 111

Tcl Parameter: Pmip6Mcc

Tcl Parameter: S2aPmip6Mcc

Tcl Parameter: NemoPmip6Mcc

  • MNC defines the mobile subscriber's home PLMN (Public Land Mobile Network)

Range: 000 — 999 (leading zeros are retained)

Default: 000

Tcl Parameter: Pmip6Mnc

Tcl Parameter: S2aPmip6Mnc

Tcl Parameter: NemoPmip6Mnc

 
Mobile Equipment Identity

In PGW Nodal test case, the Mobile Equipment Identity (MEI) is the UE's terminal identity from the Serving GW to the PDN GW over the S5/S8 interface.

Tcl Parameters:

Pmip6IncImeiSv

Pmip6Imeisv

 

NemoPmip6IncImeiSv

NemoPmip6Imeisv

 
MS ISDN Starting Number

In PGW Nodal and SGW Nodal test cases, the MS ISDN Starting Number is used to identify the user MS ISDN from the Serving GW to the PDN GW over the S5/S8 interface.

Tcl Parameters:

Pmip6IncIsMsIsdn

Pmip6MsIsdn

NemoPmip6IncIsMsIsdn

NemoPmip6MsIsdn

 

S2aPmip6IncIsMsIsdn

S2aPmip6MsIsdn

 
Set Handoff Indicator to "State Unknown" for Inter Access Handover

Available in the SGW Nodal test case.

Set Handoff Indicator to "Handoff State Unknown" instead of "handoff between two different interface" when the handover is an inter access handover (i.e. from 3GPP to non-3GPP, from non-3GPP to 3GPP, or between two non 3GPP accesses).

Tcl Parameters: S2aPmip6HIStateUnKnownForIAHoEn
Proprietary Extensions

Enable for define proprietary extended information elements.

Tcl Parameter: S2aPmip6ExtEn

See Proprietary Extensions.
GRE Key Type

Enter the mobile GRE Key Type. When Version is 9.3.0 or 9.4.0, GRE Key Type is not available.

Range: 1 - 255

Default: 88

Tcl Parameter: PmipGreKeyType

Tcl Parameter: S2aPmipGreKeyType

Tcl Parameter: NemoPmipGreKeyType
Include GRE Key

Only available in PGW Nodal's NEMO|PMIPv6 tab. Field is used to enable/disable that GRE tunnel uses the GRE Key.

Default: true (checked)

Tcl Parameter: NemoPmip6GreKeyEn
GRE Outer IP Type of Service

Select to set the GRE Outer IP headers's Type of Service field for PMIPv6 GRE Tunnel.  Not available when GRE Outer IP Uses Inner IP ToS is enabled.

Range: 0 to 255

Default: 0

Click ... (TOS Calculator) to select and calculate the appropriate value.

Tcl Parameter: Pmip6GreOuterIpTos
GRE Outer IP Uses Inner IP ToS

Select for the GRE Outer IP to use the Inner IP ToS.

Tcl Parameter: Pmip6GreUseInnerIpTosEn
Use IMSI as NAI User

In SGW Node test case, select to indicate that IMSI is used as the NAI User in the registration messages to identify the SGW Node.

Tcl Parameter:

Pmip6ImsiIsNaiUserEn

NemoPmip6ImsiIsNaiUserEn

 

NOTE: The parameters Use IMSI as NAI User and Use APN as NAI Domain in SGW Node test case is used as a way to interface/communicate with the HSGW Node when HSGW Nodal test case does not emulate the Serving Gateway (Srv GW) during Inter-Technology Mobility testing.

  • The Use IMSI as NAI User provides a way to replace the 15 characters before @ with IMSI in NAI if NAI is formated as xxxx@xxxx. The xxxx before @ needs to contain at least 15 characters.

  • The Use APN as NAI Domain provides a way to replace the xxxx after @ with APN if NAI is formated as xxxx@xxxx.

  (In HSGW Nodal test case, when Test Activity is Inter-Technology Mobility, Emulate Srv GW becomes available. If you do not select Emulate Srv GW, you would need to add the SGW Node test case, which provides a way to interface/communicate with the HSGW Node via the Use IMSI as NAI User and Use APN as NAI Domain parameters).

 
Use APN as NAI Domain

In SGW Node test case, select to indicate that APN is used as the NAI Domain. See the Note above.

Tcl Parameter: Pmip6ApnIsNaiDomainEn

Tcl Parameter: NemoPmip6ApnIsNaiDomainEn

Home Address Type

Select Address Type (IPv4, IPv6 or Both). Available when Nemo Emulation is enabled on PGW Nodal Test Configuration.

Tcl Parameter: NemoPmip6HomeAddrType

Use Static Home Address

Enable to enter a valid IPv4, IPv6 or Both address. Available when Nemo Emulation is enabled on PGW Nodal Test Configuration.

Tcl Parameter: NemoPmip6StaticHomeAddressEn

Tcl Parameter: NemoPmip6V4StaticHomeAddress

Tcl Parameter: NemoPmip6V6StaticHomeAddressEn

Custom Messages

You can customize Landslide generated messages and or compose your proprietary messages to perform negative testing with invalid values or malformed messages or to add proprietary information.

Select the Custom Messages, which makes available the New and Open buttons.

  • New: Click New to display the Message Editor window. See Message Editor for details of entering a new message.

  • Open: Click Open to display the Select Message Editor window. Select the library in which the message exists, select the message you wish to edit and then click the Edit button to display the Message Editor Window. See Message Editor for details of editing existing messages.

NOTE: Message Editor rules that apply to S1-AP protocol messages are included in the Elements of the Message Editor section of the Message Editor topic.

 

Tcl Parameter: PMIPv6CustomMsgEn

Tcl Parameter: PMIPv6CustomMsg

 

^ Back to Top

APN Assignments

APN Restriction

Use the checkbox and select from the dropdown list to include the optional APN Restriction information element in the context requests sent by the MME/MAG nodes. It is used to determine whether the UE/EnodeB is allowed to establish PDP contexts to other APNs.

APN Restriction defines the Maximum APN Restriction used in all MME/MAG requests, regardless of the values received from the SGW/LMA. Example:Example:If the Create PDP Context request contains a Maximum APN Restriction value of 3, the SGW/LMA may only allow the requested context to be established if it has an APN Restriction of 1.

Tcl Parameter: Pmip6IncApnRestriction

Tcl Parameter: S2aPmip6IncApnRestriction

Tcl Parameter: NemoPmip6IncApnRestriction

 

  • No existing contexts or restrictions, all contexts are allowed to be created (0)

  • Public-1 (e.g. WAP, MMS): contexts with restriction values 1-3 are allowed to be created (1).

  • Public-2 (e.g. Internet, PSPDN): contexts with restriction values 1-2 are allowed to be created (2).

  • Private-1 (Corporate): contexts with restriction value 1 are allowed to be created (3).

  • Private-2 (Corporate): no contexts are allowed to be created (4).

Related Measurements
Restriction

Use the dropdown list to include the optional APN Restriction information element messages sent by the PDN GW Node. It indicates the restriction level imposed on the PDP contexts associated with an APN.

Select the APN Restriction used for all APNs. Example:If the Create PDP Context request contains an APN Restriction value of 3, the PDN GW may only allow the requested context to be established if it has an APN Restriction of 1.

Options:

  • No existing contexts or restrictions, all contexts are allowed to be created — 0  

  • Public-1 (e.g. WAP, MMS): contexts with restriction values 1-3 are allowed to be created — 1

  • Public-2 (e.g. Internet, PSPDN): contexts with restriction values 1-2 are allowed to be created — 2

  • Private-1 (Corporate): contexts with restriction value 1 are allowed to be created  — 3

  • Private-2 (Corporate): no contexts are allowed to be created — 4

Tcl Parameter: Pmip6ApnRestriction

Tcl Parameter: S2aPmip6ApnRestriction

Tcl Parameter: NemoPmip6ApnRestriction
Selection Mode

Use the dropdown list to include the Selection Mode. Available in SGW Nodal S2a interface.

Options:

  • MS- or Network-Provided APN, Sub Verified  (default)  

  • MS-Provided APN, Sub Not Verified

  • Network-Provided APN, Sub Not Verified

  • For Future Use

Tcl Parameter: S2aPmip6IncApnSelectMode

Tcl Parameter: S2aPmip6ApnSelectMode
Total APNs

The maximum number of APN values that will be generated for the contexts, including both incrementing values and manually-defined values.

Range: Variable (total APNs >= Number of Default Bearers)

Default: 1

Tcl Parameter: Pmip6ApnTotalApns_0

Tcl Parameter: S2aPmip6ApnTotalApns_0

Tcl Parameter: NemoPmip6ApnTotalApns_0
Starting Auto-Incrementable APN

The format used to generate incrementing APN values. See the Auto-Increment section in Parameter Types and Features for more information incrementing formats and methods.

Range: N/A

Default: ssenoauth146

Tcl Parameter: Pmip6Apn_0

Tcl Parameter: S2aPmip6Apn_0

Tcl Parameter: NemoPmip6Apn_0
Retries

The number of times the PDP context will attempt to be activated if the first attempt did not succeed. When you enable Retries, each retry attempt will use the next APN value in the list if you have defined multiple APN values.

Range: Variable (limited by the maximum number of PDP contexts)

Default: 0 (retries are disabled)

Tcl Parameter: Pmip6ApnRetries_0

Tcl Parameter: S2aPmip6ApnRetries_0

Tcl Parameter: NemoPmip6ApnRetries_0

Related Measurements
Manually Specify First

Use the drop-down list to select the number of APN values that you will manually define. The appropriate number of value fields (APN 0 — APN 10) are enabled based on your selection. The values that you define in these fields will always be used first when you select Round Robin mode.

Tcl Parameter: Pmip6ApnNumSpecifiedApns_0

Tcl Parameter: S2aPmip6ApnNumSpecifiedApns_0

Tcl Parameter: NempPmip6ApnNumSpecifiedApns_0
Allow UE Multiple PDN Conn Req to Same APN Used for Negative scenario testing. Allows for multiple PDN connection to the SAME APN from the same UE. Should not be used for normal testing. When checked, the validation between "Default Bearers per Session" and "Number of APNs" is disabled.   Tcl Parameter: Pmip6UeMultPdnConnReqSameApnEn_0

^ Back to Top

Force Status

The number of seconds that an MN will request as the binding lifetime in Binding Updates sent to the HA. If a shorter lifetime is returned in a Binding Acknowledgement, that value is used for the binding's lifetime timer. Every binding's lifetime is timed independently.

Pmipv6HaForceStatus

PmipHaLifeTime
Refresh Advice

Use the checkbox to direct the LMA to send Binding Refresh requests to the MS before the Lifetime expires.

Time Prior to Lifetime defines the number of seconds prior to the lifetime expiration that the Binding Refresh is sent.

Range: 0 — 100

Default: 20

Pmipv6AdviceEnabler

Pmipv6HaRefresh
Delay PBAs

Indicates the number of milliseconds to delay an Access Accept message after receipt of an Access Request.

Tcl Parameter: Pmipv6PbsDelayTime

 

^ Back to Top

Non-3GPP MIPv6 Vendor Specific Options

Enable Non-3GPP Vendor Specific Options

Select to enable the Non-3GPP Vendor Specific Options.

S2aPmip6N3VsOptEn
Vendor ID

Enter the Vendor ID.

Range: 0 — 4294967295

Default: 0

S2aPmip6N3VsOptVendorId
MEID

Enter the MEID (Mobile Equipment Identifier).

Range: 1 — 14 Hexadecimal Digits

Default: 0

S2aPmip6N3VsOptMeidValue
BS ID

Enter the Base Station ID (BS ID).

Range: Up to 12 characters

Default: bsid12

S2aPmip6N3VsOptBsid

 

 

^ Back to Top

Heartbeat Interval(s)

Use the Heartbeat Interval to set the time interval in seconds between two consecutive Heartbeat Request messages.

NOTE: In PMIPv6 protocol, the heartbeat mechanism between the MAG and the LMA provides a means to detect failures, quickly inform peers in the event of a recovery from node failures, and allow a peer to take appropriate action.

 

Range: 30 - 65535

Default: 60

Tcl Parameter: Pmip6HeartbeatInterval

Tcl Parameter: S2aPmip6HeartbeatInterval
Max Missing Heartbeat Requests

The Max Missing Heartbeat Requests indicates the maximum number of consecutive Heartbeat Request messages for which a PMIPv6 node did not receive a response before concluding that the peer PMIPv6 node is not reachable.

Range: 0 - 255

Default: 100

Tcl Parameter: Pmip6MaxMissingHeartbeatAllowed

Tcl Parameter: S2aPmip6MaxMissingHeartbeatAllowed
Max Heartbeat Requests Processed

Select the radio button to indicate whether all Heartbeat Requests are processed or only the limited number of requested indicated are processed.

Tcl Parameter:

Pmip6HeartbeatRequestProcessed

Pmip6MaxHeartbeatRequestProcessed

S2aPmip6HeartbeatRequestProcessed

S2aPmip6MaxHeartbeatRequestProcessed

 
Restart Counter

The Restart Counter indicates the current Restart Counter value.

NOTE: Each PMIPv6 node (both the MAG and LMA) maintains a monotonically increasing Restart Counter that is incremented every time the node re-boots and looses PMIPv6 session state.  The counter is not incremented if the recovery happens without losing state for the PMIPv6 sessions active at the time of failure.  This counter is treated as state that is preserved across reboots.

Tcl Parameter: Pmip6RestartCounter

Tcl Parameter: S2aPmip6RestartCounter

^ Back to Top

Apply Test Data File to Parameter Values

See Test Data Files for further explanation and sample files. If a sample is not found for the specific TDF, you can obtain a sample file from your Technical Support representative. You may also use the following options to select an existing TDF or create/edit TDF-CSV files (TDF-CSV Editor). 

For most TDF Parameters used for Applying Parameters, each row in the file is the overridden value for a different “Session”, aka a different UE. But some TDFs are done in other dimensions, like Bearers, eNodeBs, Subscribers (2 per UE sometimes) or even Hosts, etc. Tooltips on the TDF Parameter: 

Note that the “ID” is a unique ID. Please Provide the ID when reporting issues with a TDF. For TDFs that do not apply / override Parameters, but instead are just their own configuration or data or media files you won’t see TDF ID row details.

TIP: When including large files, please be aware of memory limitations, since the TDF Editor shares memory with the Client.

NOTE: The available TDF options vary. on the L3-7 | IPSec tab > IKE with RSA Settings you may only select the Certificate TDF from TAS (these are non-CSV TDFs).

In addition, where applicable, any rules for defining TDFs are included in specific Test Cases. (For example, In MME Node test case, see MME Node - Provisioning TDF.)

From the DMF Window, press Shift+Alt+A to display the  Save DMF as Tcl window. Click the Save to File button to save as Tcl file. See additional details on Using the Tcl API.

 

Select/Create a new TDF-CSV

Allows you to create a new TDF by entering a file name that doesn’t already exist or select an existing file by entering a file name that already exists.

Click to open the Select Existing or Create window.

  • Navigate to the relevant library/folder,

  • Enter the name of the file:

  • If the file name already exists, the file is selected and applied in the test case.

  • If the file name does not exist, a message displays that says you are creating a new TDF and the embedded TDF-CSV will be launched.

    • Click Yes to launch the TDF-CSV Editor and create/save the new TDF-CSV.

    • Click No to select a different file

NOTE: If you do not have permission to save in the selected library, an error displays when you try to create a new file.
TIP: You may also navigate to the relevant library/folder and select file, and click OK.

 

Upload a New TDF to TAS

Click to import a new TDF file from your local folder and select in the test Case (instead of having to go to TDF Admin).

  • Navigate to the file on your local folder and select.
  • Then navigate to the location (library) where you want to save it on the TAS. You may rename the file, if required.  

View Edit Selected TDF in TDF-CSV Editor

Available only when you have selected a TDF on TAS. Click to open the selected file in TDF-CSV Editor (in place, that is, within the Test Case).

Edit the file and save. You may also click Save As to save the edited TDF-CSV to a different library and also rename the file, if required.

NOTE: You may also select a TDF from a library to which you do not have write permissions, edit the file as required, and save (Save As) only to a different library with the same file name or a different name.

The only options available are Save As and Cancel.

Open Selected TDF in Standalone TDF-CSV Editor

Available only when you have selected a TDF on TAS. Select to retrieve the CSV file and open it in the stand alone TDF-CSV Editor.

Generate Stub TDF-CSV

TIP: Available only when a CSV specification has been defined for in the Test Case for the TDF widget ( View TDF Actions/Options Menu)

 

Opens an example context specific test data parametersexample context specific test data parameters, which you may save as a .CSV file or open in the TDF-CSV Editor.

 

Launch Standalone TDF-CSV Editor

Click to open a blank TDF-CSV Editor.

The Launch Standalone TDF-CSV editor options handles very large TDFs that may use too much Client memory if opened within the Test Case/in the embedded editor.  You may set the standalone TDF-CSV Editor memory high to edit large TDFs.

 (applies to APN selections and not Local Mobility Anchor.)

Tcl Parameter: Pmip6CfgFileEn

Tcl Parameter: S2aPmip6CfgFileEn

^ Back to Top

© 2024 Spirent Communications Inc. All Rights Reserved.