WiMAX Forum Tab


The WiMAX Forum tab is used to define the MIP scheme you wish to deploy, import a Test Data File with values that override WiMAX Forum defined  message values, and Mobile Subscriber authentication setting. The WiMAX Forum Tab is available in following test cases:

The WiMAX Forum tab is used to define values for the following parameters:

Parameter Index

Protocol Settings

Mobile Subscriber Settings

 

 

Quality of Service

Summary/Individual

 

Enhanced Real-Time Variable Rate

Non Real-Time Variable Rate

 

 

 

Related Measurements

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

^ Back to Top


Apply Parameter Values from Test Data Files

You can provision explicit values for the R6 Configuration File and WiMax Forum Configuration by using a Test Data File.

Tcl Parameters:

R6CfgFileEn

WmForumCfgFileEn

 

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.

 

MS ID

A unique Mobile Subscriber ID. A MS is uniquely identified by its MAC address. Enter a starting address that will be incremented for each MS.

Range: Up to 12 hexadecimal characters (omit "0x"). Use colon or dash delimiters.

Default: N/A

Tcl Parameter: StartingMsId

 

Network Access Identifier

The mobile subscriber's Network Access Identifier (NAI). You can use an Auto-Increment format in this field.

Range: N/A

Default: @domain

Tcl Parameter: StartingNtwkId

 

Paging Group Identifier

A 16-bit number representing the Paging Group that the MN is assigned to.

Range: 0 — 65535 (0 = not active)

Default: 0

Tcl Parameter: PagingGroupId

 

EAP Type

Use the EAP Type drop-down list to select The Extensible Authentication Protocol (EAP) to be used to authenticate MNs in a CSN Nodal or ASN Nodal test for all versions and variants.

Click .Settings to configure the EAP Settings.

Options

For WiMAX Forum Version 1.0.0: Single EAP (user authentication), Double EAP (first device and then user authentication), or None (disable all EAP Settings)

For WiMAX Forum Versions >  1.0.0:  Single EAP (user authentication), Combined EAP (first device and then user authentication), or None (disable all EAP Settings)  

NOTE: When you configure reauthentication with Double EAP, only the device is reauthenticated.

Default: Single EAP

Tcl Parameter: EapType

Authentication with Double EAP requires one parameter:

Device Identity

An MN device is uniquely identified by its MAC address. Enter a starting address that will be incremented for each MN.

Range: Up to 128 hexadecimal characters (omit colons or dash delimiters).

Default: N/A

Example:  #(0X010203040506)

Tcl Parameter: DeviceIdentity

 

Device Secret Key

 

The Device shared key that is known to both the MN and the EAP Server.

Range: Up to 32 hexadecimal digits, excluding "0x."

Default: 0x0123456789ABCDEF0123456789ABCDEF

Tcl Parameter: DeviceSecret

 

None When you select None, all EAP Settings are disabled.
Max Uplink Service Flow

Enter the maximum number of CIDs (Connection Identifiers) in the Uplink direction for the mobile station.

Range: 1 — 32

Default: 1

Tcl Parameter: UplinkServiceFlow

 

Max Downlink Service Flow

Enter the maximum number of CIDs (Connection Identifiers) in the Downlink direction for the mobile station.

Range: 1 — 32

Default: 1

Tcl Parameter: DownlinkServiceFlow

 

Create and Delete Service Flow Delay

The Create Service Flow Delay and Delete Service Flow Delay parameters are available when the UE Initiated Service Flows is > 0. Use these parameters to set delays for provisioning Packet Flow filters.

  • If Create Service Flow Delay is set to a 0, then there is no delay in sending the Data Path Registration Request.  
  • If Delete Service Flow Delay is set to a 0, then no Data Path Deregistration will be sent until the MN Detaches or Handsoff to another BS.

When Dynamic Service Flows is enabled, the Create Service Flow Delay requires a value >=2 to test Dynamic service flows.

Range: 0 - MAX_UINT32,

Default: 0

Tcl Parameters:

CreateServiceFlowDelay

DeleteServiceFlowDelay

 

WiMAX Forum Version

Select the WiMAX Forum version from the drop-down list.

Options:

  • Version 1.0.0

  • Rel. 1 Version 1.2

  • Rel. 1 Version 1.3

  • Version 1.5.0

Default: Version 1.0.0

Tcl Parameter: WmForumVer

 

Vendor Variant

Select the Vendor Variant from the drop-down list.

  • Vendor Variant 7 is available when your system is licensed and when WiMAX Forum Version is:  Rel. 1 Version 1.2.

On ASN Nodal, when Vendor Variant is 7, the ASN Gateway optional MAC address is available, i.e. the checkbox is enable for the user to choose.

NOTE: Currently no Vendor Variants are supported for WiMAX Forum Version Rel.1 Version 1.3 and Version 1.5.0.

Tcl Parameter: WmForumVendorVariant

 

TLV Comprehension Required When the TLV Comprehension Required checkbox is enabled (default), there are no changes to the TLV value. If disabled, then a 0x8000 mask is OR'ed to the TLV value.
Include Source and Destination TLVs in handoff Context Message

During ASN Nodal and CDMA WiMAX Convergence testing you may choose to include the Source and Destination TLVs in the WiMAX messages.

  • Select Include Source and Destination TLVs in Handoff Context Message to include in all context and handoff messages.
  • For Profile C, the Target BS node address will be included as the Destination TLV, for other profiles, the ASN GW Id is used as the Destination TLV.
  • Depending on the Vendor Variants, some vendor specific messages will also include Source and Destination TLVs.
  • Clearing Include Source and Destination TLVs in handoff Context Message ensures that the WiMAX R6 messages do not include the source and destination TLVs.

Tcl Parameter: IncSrcDstTlvsEn

Value: True, False

Include Messages

Use these parameters to include Source Identifier and destination Identifier TLV  messages in pre-attachment and R6 context ID.

  • Select Include Source and Destination TLVs in Preattachment Message to include in all pre-attachment messages.
  • Select Include R6 Context ID TLV in Message to include in all R6 context ID messages.

Type: True/False

Default: False

Tcl Parameter:

IncSrcDstTlvsPreattEn

InR6ContextIdEn

 

AK Lifetime IE Length

AK Lifetime IE Length is available only if you are licensed to use Vendor Variant 2 and when you select V.

Tcl Parameter: AkLifetimeLength

 

Idle Entry Time(s)

Idle Mode allows the mobile station to conserve power and operational resources. You can set the Idle Mode Entry timer value (in seconds), thus causing the Idle Mode Entry procedure to initiate upon its expiration.

Range: 0 — 65535 (0 = not active)

Default: 0

Type: Integer

Tcl Parameter: MsIdleTime

 

Idle Time Exit

Set the Idle Mode Exit timer value (in seconds), to exit the idle mode procedure to upon its expiration.

Range: 0 — 65535 (0 = not active)

Default: 0

Type: Integer

Tcl Parameter: MsIdleExitTime

 

Location Update Time(s)

A Location Update forced by the network for a mobile station is one reason paging occurs. You can set the Location Update timer value (in seconds), thus causing the mobile station to exit Idle Mode upon its expiration.

Range: 0 — 65535 (0 = not active)

Default: 0

Tcl Parameter: MsLuTime

 

Re-authentication Time

The number of seconds after the intitial EAP exchange when EAP re-authentication will be performed. This parameter is not available when EAP type is None.

Range: 0 — 4294967295 (0 = not active)

Default: 0

Tcl Parameter: ReAuthTime

 

Retry Time

The amount of time, in milliseconds, that the test will wait for a response if a response is expected. When the time expires and the Retries has not been exceeded, the message is re-transmitted.

Range: N/A

Default: 15000

Tcl Parameter: MsRetryTime

 

Retries

 

The number of times the test will re-transmit a connection request. Enter 0 to disable retries.

Range : 0 — 255

Default : 5

Tcl Parameter: AsnRetries

 

Data Path Granularity

Select whether the data path is at the service flow or mobile station level.

Options: Per Service Flow or Per Mobile Station

Default: Per Service Flow

Tcl Parameter: DpGranularity

 

Profile Type

In the WiMAX Forum architecture, a profile maps ASN functions into the base station and ASN Gateway, so that protocols and messages over the exposed reference points (interfaces) are identified. Select the Profile Type from the drop-down list.

Options:

Profile A
  • Handover control is in the ASN Gateway.

  • RRC (Radio Resource Controller) is in the ASN Gateway that allows RRM among multiple base stations.

  • ASN anchored mobility among base stations is achieved by utilizing R6 and R4 physical connections.

Profile C
  • Handover control is in the Base Station.

  • RRC (Radio Resource Controller) is in the base station that allows RRM within the base station. An RRC Relay in the ASN Gateway relays the 8 RRM messages sent from base station to base station via the R6 connection.

  • ASN anchored mobility among base stations is achieved by utilizing R6 and R4 physical connections.

Default: Profile A

Tcl Parameter: ProfileType

 

 

 

 


 

Robust Header Compression (RoHC)

ROHC is available only if WiMAX Forum version 1.5 is selected. RoHC is supported between the MS and the ASN-GW (RFC3095)

NOTE: ROHC compresses 40 bytes of Ipv4 packets (IP, UDP, and RTP) or 60 bytes of Ipv6 packets overhead typically into only 1 or 3 bytes by placing a compressor before the link that has limited capacity, and a decompressor after that link. The compressor converts the large overhead to only a few bytes, while the decompressor does the opposite.

Tcl Parameter: WmForumRohc

ROHC does not support compression for all types of IP headers.  Profile 0x0000 provides a way to send IP packets without compressing them.  This (Profile 0x0000) can be used for IP fragments, RTCP packets, and for any packet for which header compression has not been defined, for e.g., due to resource constraints.

Tcl Parameter: WmForumRohcProfile

The ROHC scheme has three modes of operation, called Unidirectional, Bidirectional Optimistic, and Bidirectional Reliable mode.

Options: Unidirectional, Bidirectional (Optimistic and Reliable mode)

Tcl Parameter: WmForumRohcBidirectionalMode

^ Back to Top


Convergence Sublayer Type

Select the Convergence Sublayer used to forward encapsulated IP Packets. Select options IP or IP over Ethernet. If you select IP over Ethernet, enter the Destination MAC Address to deliver the IP packets.

Tcl Parameter:

WmForumCsType

WmForumDestMac

 

^ Back to Top


PC ID

Use PC ID to configure an ID to be relayed.  The values requires a requires a valid MAC Address (For example: 00:1d:93:09:54:01) and the parameter is available only when the Vendor Variant is 7.  

Tcl Parameter: WmForumPcId

Network Exit in Idle Time

Available when Vendor Variant =7  and Idle Entry Time 0. Enter a time after expiration of which the test case initiates the Network Exit in Idle mode.

Range = 0 - 65535

Default = 0

Tcl Parameter: MsNtwkExitIdleTime

^ Back to Top


Quality of Service

Use the Quality of Service parameters for provisioning Packet Flow filters and QOS values requested by the MS in the ASN Nodal test case. When UE Initiated Service Flows is > 0, you can define QoS profiles that will be requested for service flow contexts.

Summary/Individual

You can choose to use the same QOS profile for all Service Flow contexts or you can define different profiles for each context. Select either Summary (all contexts use the same profile) or Individual (different profiles can be defined) and define the relevant Quality of Service profiles. If you select Individual, each QOS profile is defined in a separate sub-tab. The sub-tabs are initially provisioned with the Summary settings and are labeled by context.

For example, if QOS profile is Summary, all Service Flow contexts use the same profile defined on the SF0 tab. When QOS profile is Summary and the UE Initiated Service Flows is 3, then the sub-tabs are labeled as SF0, SF1, and SF2 containing 3 Service Flow QOS profiles.

Enhanced Real-Time Variable Rate

Enhanced Real-Time Variable Rate (ERT-VR) was introduced with the 802.16e standard. It is used for real-time applications with variable packet sizes.

Range: 0 — 4294967295

Default: 8000

Range: 0 — 4294967295

Default: 8000

Range: 0 — 4294967295

Default: 50

Range: 0 — 4294967295

Default: 0

Range: 0 — 4294967295

Default: 25

Range: 0 — 255

Default: 3

Range: 0 — 4294967295

Default: 1

Range: 0 — 65535

Default: 25

QosErtVrEn_n

QosErtVrMaxLatency_n

QosErtVrPriority_n

QosErtVrMinReservedRate_n

QosErtVrMaxBurst_n

QosErtVrReqTxPolicy_n

QosErtVrMaxSustainedRate_n

QosErtVrTolJitter_n

QosErtVrUnsolGrantInterval_n

QosErtVrUnsolGrantInterval_n

   


Non Real-Time Variable Rate

Non-Real-Time Variable Rate is used for services where a guaranteed bit rate is required, but guaranteed delay isn’t. For example, file transfer.

Range: 0 — 4294967295

Default: 8000

Range: 0 — 4294967295

Default: 8000

Range: 0 — 4294967295

Default: 0

Range: 0 — 255

Default: 3

Range: 0 — 4294967295

Default: 1

QosNrtVrEn_n

QosNrtVrMaxSustainedRate_n

QosNrtVrPriority_n

QosNrtVrMinReservedRate_n

QosNrtVrMaxBurst_n

QosNrtVrReqTxPolicy_n

^ Back to Top