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:
Protocol Settings Mobile Subscriber Settings |
|
Quality of Service |
|
Enhanced Real-Time Variable Rate |
Non Real-Time Variable Rate
|
Measurements collected for Mobile IP related processing are reported on the Mobile IP report tab.
You can provision explicit values for the R6 Configuration File and WiMax Forum Configuration by using a Test Data File. Tcl Parameters:
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.
|
|||||||||||||||||||||
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. OptionsFor 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)
Default: Single EAP Tcl Parameter: EapType Authentication with Double EAP requires one parameter:
|
||||||||||||||||||||
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.
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:
|
||||||||||||||||||||
WiMAX Forum Version |
Select the WiMAX Forum version from the drop-down list. Options:
Default: Version 1.0.0 Tcl Parameter: WmForumVer
|
||||||||||||||||||||
Vendor Variant |
Select the Vendor Variant from the drop-down list.
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.
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.
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.
Type: True/False Default: False Tcl Parameter:
|
||||||||||||||||||||
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 |
||||||||||||||||||||
|
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
|
||||||||||||||||||||
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
|
|||||||||||||||||||||
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:
Default: Profile A Tcl Parameter: ProfileType
|
|||||||||||||||||||||
|
|
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)
Unidirectional Mode (U-mode): In the Unidirectional mode of operation, packets are sent in one direction only: from compressor to decompressor. This mode therefore makes ROHC usable over links where a return path from decompressor to compressor is unavailable or undesirable.
Bidirectional Optimistic mode (O-mode): The Bidirectional Optimistic mode is similar to the Unidirectional mode, except that a feedback channel is used to send error recovery requests and (optionally) acknowledgments of significant context updates from the decompressor to compressor. The O-mode aims to maximize compression efficiency and sparse usage of the feedback channel. It reduces the number of damaged headers delivered to the upper layers due to residual errors or context invalidation.
Bidirectional Reliable mode (R-mode): The Bidirectional Reliable mode includes a more intensive usage of the feedback channel that the previous two modes. It supports a stricter logic at both the compressor and the decompressor, which prevents loss of context synchronization between compressor and decompressor except for very high residual bit error rates. R-mode aims to maximize robustness against loss propagation and damage propagation, i.e., minimize the probability of context invalidation, even under header loss/error burst conditions.
Tcl Parameter: WmForumRohcBidirectionalMode
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 |
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
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
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.
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 (ERT-VR) was introduced with the 802.16e standard. It is used for real-time applications with variable packet sizes.
Enable ERT-VR Data Delivery Service: Select the checkbox to enable the parameters and define the Enhanced Real-Time Variable Rate (ERT-VR).
Min Reserved Traffic Rate(bits/s): Indicates the minimum rate reserved for a service flow.
Range: 0 — 4294967295
Default: 8000
Max Sustained Traffic rate(bits/s): Indicates the maximum peak rate reserved for the service.
Range: 0 — 4294967295
Default: 8000
Max Latency (ms): Indicates the maximum latency allowed for end-to-end packet transmission/service flow time.
Range: 0 — 4294967295
Default: 50
Max Traffic Burst (Bytes): Indicates the maximum burst size of a service flow in bytes.
Range: 0 — 4294967295
Default: 0
Tolerated Jitter: Indicates the maximum delay variation in milliseconds for the service flow.
Range: 0 — 4294967295
Default: 25
Traffic Priority: Indicates the proportion of successfully delivered packets.
Range: 0 — 255
Default: 3
Request/Transmission Policy: Indicates Real-time traffic that generates fixed-size data packets on a periodic basis.
Range: 0 — 4294967295
Default: 1
Unsolicited Grant Interval (ms): Indicates, Real time service (e.g., VoIP) generating fixed data rate.
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 is used for services where a guaranteed bit rate is required, but guaranteed delay isn’t. For example, file transfer.
Enable NRT-VR Data Delivery Service: Select the checkbox to enable the parameters and define the Non Real-Time Variable Rate (ERT-VR).
Min Reserved Traffic Rate (bits/s): Indicates the minimum rate reserved for a service flow.
Range: 0 — 4294967295
Default: 8000
Max Sustained Traffic Rate (bits/s): Indicates the maximum peak rate reserved for the service.
Range: 0 — 4294967295
Default: 8000
Max Traffic Burst (Bytes): Indicates the maximum burst size of a service flow.
Range: 0 — 4294967295
Default: 0
Traffic Priority: Indicates the proportion of successfully delivered packets.
Range: 0 — 255
Default: 3
Request/Transmission Policy: Indicates Real-time traffic that generates fixed-size data packets on a periodic basis.
Range: 0 — 4294967295
Default: 1
QosNrtVrEn_n |
QosNrtVrMaxSustainedRate_n |
QosNrtVrPriority_n |
QosNrtVrMinReservedRate_n |
QosNrtVrMaxBurst_n |
QosNrtVrReqTxPolicy_n |