WiMAX Forum® Test Procedures
WiMAX Forum® Mobile InterOperability Test (MIOT)
WMF-T25-003-R010v08
WMF Approved
(2012-04-16)
WiMAX Forum Proprietary
Copyright © 2012 WiMAX Forum. All Rights Reserved.
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
WMF-T25-003-R010v08
Copyright Notice, Use Restrictions, Disclaimer, and Limitation of Liability
Copyright 2012 WiMAX Forum. All rights reserved.
The WiMAX Forum® owns the copyright in this document and reserves all rights herein. This document is available for
download by the WiMAX Forum members, and may be duplicated for internal use, provided that all copies contain all
proprietary notices and disclaimers included herein. Except for the foregoing, this document may not be duplicated, in whole or
in part, or distributed without the express written authorization of the WiMAX Forum.
Use of this document is subject to the disclaimers and limitations described below. Use of this document constitutes acceptance
of the following terms and conditions:
THIS DOCUMENT IS PROVIDED “AS IS” AND WITHOUT WARRANTY OF ANY KIND. TO THE GREATEST
EXTENT PERMITTED BY LAW, THE WiMAX FORUM DISCLAIMS ALL EXPRESS, IMPLIED AND
STATUTORY WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF TITLE,
NONINFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE WiMAX
FORUM DOES NOT WARRANT THAT THIS DOCUMENT IS COMPLETE OR WITHOUT ERROR AND
DISCLAIMS ANY WARRANTIES TO THE CONTRARY.
Any products or services provided using technology described in or implemented in connection with this document may be
subject to various regulatory controls under the laws and regulations of various governments worldwide. The user is solely
responsible for the compliance of its products and/or services with any such laws and regulations and for obtaining any and all
required authorizations, permits, or licenses for its products and/or services as a result of such regulations within the applicable
jurisdiction.
NOTHING IN THIS DOCUMENT CREATES ANY WARRANTIES WHATSOEVER REGARDING THE
APPLICABILITY OR NON-APPLICABILITY OF ANY SUCH LAWS OR REGULATIONS OR THE SUITABILITY
OR NON-SUITABILITY OF ANY SUCH PRODUCT OR SERVICE FOR USE IN ANY JURISDICTION.
NOTHING IN THIS DOCUMENT CREATES ANY WARRANTIES WHATSOEVER REGARDING THE
SUITABILITY OR NON-SUITABILITY OF A PRODUCT OR A SERVICE FOR CERTIFICATION UNDER ANY
CERTIFICATION PROGRAM OF THE WiMAX FORUM OR ANY THIRD PARTY.
The WiMAX Forum has not investigated or made an independent determination regarding title or noninfringement of any
technologies that may be incorporated, described or referenced in this document. Use of this document or implementation of any
technologies described or referenced herein may therefore infringe undisclosed third-party patent rights or other intellectual
property rights. The user is solely responsible for making all assessments relating to title and noninfringement of any technology,
standard, or specification referenced in this document and for obtaining appropriate authorization to use such technologies,
technologies, standards, and specifications, including through the payment of any required license fees.
NOTHING IN THIS DOCUMENT CREATES ANY WARRANTIES OF TITLE OR NONINFRINGEMENT WITH
RESPECT TO ANY TECHNOLOGIES, STANDARDS OR SPECIFICATIONS REFERENCED OR INCORPORATED
INTO THIS DOCUMENT.
IN NO EVENT SHALL THE WiMAX FORUM OR ANY MEMBER BE LIABLE TO THE USER OR TO A THIRD
PARTY FOR ANY CLAIM ARISING FROM OR RELATING TO THE USE OF THIS DOCUMENT, INCLUDING,
WITHOUT LIMITATION, A CLAIM THAT SUCH USE INFRINGES A THIRD PARTY’S INTELLECTUAL
PROPERTY RIGHTS OR THAT IT FAILS TO COMPLY WITH APPLICABLE LAWS OR REGULATIONS. BY
USE OF THIS DOCUMENT, THE USER WAIVES ANY SUCH CLAIM AGAINST THE WiMAX FORUM AND ITS
MEMBERS RELATING TO THE USE OF THIS DOCUMENT.
The WiMAX Forum reserves the right to modify or amend this document without notice and in its sole discretion. The user is
solely responsible for determining whether this document has been superseded by a later version or a different document.
“WiMAX,” “Mobile WiMAX,” “Fixed WiMAX,” “WiMAX Forum,” “WiMAX Certified,” “WiMAX Forum Certified,” the
WiMAX Forum logo and the WiMAX Forum Certified logo are trademarks or registered trademarks of the WiMAX Forum. All
other trademarks are the property of their respective owners.
58
Page - ii
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Table of Contents
WIMAX FORUM® TEST PROCEDURES............................................................................................................... I
1.
SCOPE ........................................................................................................................................................... 11
2.
PURPOSE ...................................................................................................................................................... 12
3.
REFERENCES .............................................................................................................................................. 13
4.
ABBREVIATIONS ....................................................................................................................................... 14
5.
MOBILE INTEROPERABILITY TEST SUITE ....................................................................................... 15
5.1
How to use the Interoperability Test Suite .................................................................................................. 15
5.2
How to document a Test Campaign............................................................................................................. 15
5.3
Test Configuration ....................................................................................................................................... 15
5.3.1
Test Scenario List MS IOT................................................................................................................... 16
5.3.2
Test Scenario List BS IOT ................................................................................................................... 19
5.4
Test Scenario Identifier Naming Conventions ............................................................................................. 22
5.5
TD Identifier Naming Conventions ............................................................................................................. 23
5.6
Test Scenario List ........................................................................................................................................ 24
6.
TEST CAMPAIGN INFORMATION ........................................................................................................ 26
6.1
Date of statement ......................................................................................................................................... 26
6.2
Vendor Contact Person ................................................................................................................................ 26
6.3
Product Supplier for Test Bed ..................................................................................................................... 26
7.
TEST CAMPAIGN PARAMETERS AND REPORT ............................................................................... 27
7.1.1
7.1.2
7.1.3
7.2
8.
Vendor Specific Instructions for UUT Setup ....................................................................................... 27
MS Test campaign parameters ............................................................................................................. 28
BS Test campaign parameters .............................................................................................................. 29
Test campaign report ................................................................................................................................... 29
TEST SCENARIOS ...................................................................................................................................... 37
8.1
Scenario 1a - Basic Configuration ............................................................................................................... 37
8.1.1
Network Entry procedure ..................................................................................................................... 38
8.1.1.1
MS Synchronization and Ranging ................................................................................................. 38
8.1.1.2
Capabilities Negotiation ................................................................................................................ 39
8.1.1.3
Registration ................................................................................................................................... 39
8.1.2
Traffic Connection Establishment ........................................................................................................ 40
8.1.2.1
Service Flow Provisioning ............................................................................................................ 40
8.1.3
User Data Transfer ............................................................................................................................... 41
8.1.3.1
PING ............................................................................................................................................. 41
8.1.3.2
File Data Transfer ......................................................................................................................... 41
8.2
Scenario 1b – BS initiated CQI Reporting using Fast Feedback Channel ................................................... 42
8.2.1
Network Entry procedure ..................................................................................................................... 43
8.2.1.1
Capabilities Negotiation ................................................................................................................ 43
8.2.1.2
MAP .............................................................................................................................................. 44
Page - iii
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.3
Scenario 1c – HARQ ................................................................................................................................... 45
8.3.1
Network Entry procedure ..................................................................................................................... 46
8.3.1.1
Capabilities Negotiation ................................................................................................................ 46
8.3.2
Traffic Connection Establishment ........................................................................................................ 47
8.3.2.1
Service Flow Provisioning ............................................................................................................ 47
8.3.3
User Data Transfer ............................................................................................................................... 48
8.3.3.1
Verification of DL HARQ Allocations ......................................................................................... 48
8.3.3.2
Verification of UL HARQ Allocations ......................................................................................... 49
8.4
Scenario 1c-B – HARQ on UL MAC Messages ......................................................................................... 50
8.4.1
Network Entry procedure ..................................................................................................................... 51
8.4.1.1
Capabilities Negotiation ................................................................................................................ 51
8.4.2
HARQ on UL MAC messages ............................................................................................................. 52
8.4.2.1
Verification of UL HARQ Allocations of UL MAC messages ..................................................... 52
8.4.3
Traffic Connection Establishment ........................................................................................................ 53
8.4.3.1
Service Flow Provisioning ............................................................................................................ 53
8.4.4
User Data Transfer ............................................................................................................................... 54
8.4.4.1
Verification of DL HARQ Allocations ......................................................................................... 54
8.4.4.2
Verification of UL HARQ Allocations ......................................................................................... 55
8.5
Scenario 1d – Mac-level ARQ ..................................................................................................................... 56
8.5.1
Network Entry procedure ..................................................................................................................... 57
8.5.1.1
Registration ................................................................................................................................... 57
8.5.2
Traffic Connection Establishment ........................................................................................................ 58
8.5.2.1
Service Flow Provisioning ............................................................................................................ 58
8.5.3
User Data Transfer ............................................................................................................................... 59
8.5.3.1
Verification of DL ARQ Allocations ............................................................................................ 59
8.5.3.2
Verification of UL ARQ Allocations ............................................................................................ 60
8.6
Scenario 1eb – BS initiated Open Loop Power Control .............................................................................. 61
8.6.1
Open Loop Power Control Activation .................................................................................................. 62
8.6.2
Open Loop Power Control during User Data Transfer ......................................................................... 63
8.7
Scenario 1ec - Closed Loop Power Control................................................................................................. 64
8.7.1
Initial Ranging ...................................................................................................................................... 65
8.7.2
Closed Loop Power Control during User Data Transfer ...................................................................... 65
8.8
Scenario 1f – Security Version 2 ................................................................................................................. 66
8.8.1
Security Capabilities Negotiation ......................................................................................................... 67
8.8.2
Authentication and Authorization ........................................................................................................ 68
8.8.3
3-way handshake and SA creation........................................................................................................ 69
8.8.4
User Data Transfer ............................................................................................................................... 70
8.8.4.1
PING ............................................................................................................................................. 70
8.8.5
Periodic TEK Refresh .......................................................................................................................... 70
8.8.6
User Data Transfer with refreshed key material ................................................................................... 71
8.8.6.1
PING ............................................................................................................................................. 71
8.9
Scenario 1g- MS initiated Sleep Mode ........................................................................................................ 72
8.9.1
Setup of MS initiated Sleep Mode........................................................................................................ 72
8.9.2
MS initiated Sleep Mode ...................................................................................................................... 73
8.9.3
Sleep Mode Verification ...................................................................................................................... 74
8.9.4
BS initiated PING ................................................................................................................................. 74
8.9.5
MS initiated activation of deactivated PSC .......................................................................................... 75
8.9.6
MS initiated PING ................................................................................................................................ 75
8.10 Scenario 1ha - MS initiated Idle Mode ........................................................................................................ 76
8.10.1 MS initiated Idle Mode......................................................................................................................... 77
8.10.2 Idle Mode Verification ......................................................................................................................... 78
8.10.3 BS initiated PING ................................................................................................................................. 78
Page - iv
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.10.4
8.10.5
8.10.6
8.10.7
WMF-T25-003-R010v08
MS initiated Idle Mode (Re-initiation) ................................................................................................. 79
MS initiated PING ................................................................................................................................ 79
MS initiated Idle Mode (Re-initiation) ................................................................................................. 79
Power Down Final Test ........................................................................................................................ 80
8.11 Scenario 1hb - BS initiated Idle Mode......................................................................................................... 81
8.11.1 Setup for BS initiated Idle Mode .......................................................................................................... 82
8.11.2 BS Triggers Idle Mode ......................................................................................................................... 83
8.11.3 BS initiated PING ................................................................................................................................. 83
8.12 Scenario 1hc - Load Balancing 1 ................................................................................................................. 84
8.12.1 Network Entry procedure ..................................................................................................................... 85
8.12.1.1 MS Synchronization and Ranging ................................................................................................. 85
8.12.1.2 Capabilities Negotiation ................................................................................................................ 86
8.12.1.3 Registration ................................................................................................................................... 86
8.12.2 Traffic Connection Establishment ........................................................................................................ 87
8.12.2.1 Service Flow Provisioning ............................................................................................................ 87
8.12.3 User Data Traffic .................................................................................................................................. 88
8.12.3.1 PING ............................................................................................................................................. 88
8.12.3.2 File Data Transfer ......................................................................................................................... 88
8.13 Scenario 1i – ERT-VR ................................................................................................................................. 89
8.13.1 Traffic Connection Establishment ........................................................................................................ 90
8.13.1.1 Service Flow Provisioning ............................................................................................................ 90
8.13.2 User Data Transfer ............................................................................................................................... 91
8.13.2.1 File Data Transfer ......................................................................................................................... 91
8.14 Scenario 1j - MS initiated Handover ........................................................................................................... 92
8.14.1 Neighbor Advertisement ...................................................................................................................... 93
8.14.2 Handover Decision ............................................................................................................................... 93
8.14.3 Handover Initiation............................................................................................................................... 94
8.14.4 Handover Verification .......................................................................................................................... 95
8.15 Scenario 2 - P2MP Configuration................................................................................................................ 96
8.15.1 Network Entry procedure ..................................................................................................................... 96
8.15.1.1 Ranging ......................................................................................................................................... 96
8.15.1.2 Capabilities Negotiation ................................................................................................................ 98
8.15.1.3 Registration ................................................................................................................................... 98
8.15.2 Traffic Connection Establishment ........................................................................................................ 99
8.15.2.1 Service Flow Provisioning ............................................................................................................ 99
8.15.3 User Data Transfer ............................................................................................................................. 100
8.15.3.1 PING ........................................................................................................................................... 100
8.15.3.2 File Data Transfer ....................................................................................................................... 100
8.16 Scenario 2A0 – DL PUSC with MIMO Matrix A and UL PUSC with Collaborative SM ........................ 101
8.16.1 Network Entry procedure ................................................................................................................... 101
8.16.1.1 Capabilities Negotiation .............................................................................................................. 101
8.16.2 User Data Transfer ............................................................................................................................. 102
8.16.2.1 MAP ............................................................................................................................................ 102
8.16.2.2 Data grants for the MS ................................................................................................................ 103
8.16.2.3 Data Transfer............................................................................................................................... 103
8.17 Scenario 2A1 – DL PUSC with MIMO Matrix B and UL PUSC With Collaborative SM ....................... 104
8.17.1 Network Entry procedure ................................................................................................................... 105
8.17.1.1 Capabilities Negotiation .............................................................................................................. 105
8.17.2 User Data Transfer ............................................................................................................................. 106
8.17.2.1 MAP ............................................................................................................................................ 106
8.17.2.2 Data grants for the MS ................................................................................................................ 107
8.17.2.3 Data Transfer............................................................................................................................... 107
Page - v
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.18 Scenario 2B0 – Beam Forming with DL AMC with Dedicated Pilots and UL AMC ............................... 108
8.18.1 Network Entry procedure ................................................................................................................... 109
8.18.1.1 Capabilities Negotiation .............................................................................................................. 109
8.18.2 User Data Transfer ............................................................................................................................. 110
8.18.2.1 MAP ............................................................................................................................................ 110
8.18.2.2 Data grants for the MS ................................................................................................................ 110
8.18.2.3 Data Transfer............................................................................................................................... 111
8.19 Scenario 2B1 – Beam Forming with DL PUSC with Dedicated Pilots and UL PUSC without channel
rotation................................................................................................................................................................... 112
8.19.1 Network Entry procedure ................................................................................................................... 113
8.19.1.1 Capabilities Negotiation .............................................................................................................. 113
8.19.2 User Data Transfer ............................................................................................................................. 114
8.19.2.1 MAP ............................................................................................................................................ 114
8.19.2.2 Data grants for the MS ................................................................................................................ 115
8.19.2.3 Data Transfer............................................................................................................................... 115
8.20 Scenario 2AB0 – DL PUSC with dedicated pilot with MIMO Matrix A and UL PUSC with Collaborative
SM
116
8.20.1 Network Entry procedure ................................................................................................................... 117
8.20.1.1 Capabilities Negotiation .............................................................................................................. 117
8.20.2 User Data Transfer ............................................................................................................................. 118
8.20.2.1 MAP ............................................................................................................................................ 118
8.20.2.2 Data grants for the MS ................................................................................................................ 119
8.20.2.3 Data Transfer............................................................................................................................... 119
8.21 Scenario 2AB1 – DL PUSC with dedicated pilot with Matrix B MIMO and UL PUSC with Collaborative
SM
120
8.21.1 Network Entry procedure ................................................................................................................... 121
8.21.1.1 Capabilities Negotiation .............................................................................................................. 121
8.21.2 User Data Transfer ............................................................................................................................. 122
8.21.2.1 MAP ............................................................................................................................................ 122
8.21.2.2 Data grants for the MS ................................................................................................................ 123
8.21.2.3 Data Transfer............................................................................................................................... 123
8.22 Scenario 2AC0 – DL PUSC and UL PUSC without subchannel rotation ................................................. 124
8.22.1 Network Entry procedure ................................................................................................................... 125
8.22.1.1 Capabilities Negotiation .............................................................................................................. 125
8.22.2 User Data Transfer ............................................................................................................................. 126
8.22.2.1 MAP ............................................................................................................................................ 126
8.22.2.2 Data grants for the MS ................................................................................................................ 127
8.22.2.3 Data Transfer............................................................................................................................... 127
8.23 Scenario 2C0 – PHS IPv4 .......................................................................................................................... 128
8.23.1 Network Entry procedure ................................................................................................................... 129
8.23.1.1 Registration ................................................................................................................................. 129
8.23.2 Traffic Connection Establishment ...................................................................................................... 129
8.23.2.1 Service Flow Provisioning .......................................................................................................... 129
8.23.3 User Data Transfer ............................................................................................................................. 130
8.23.3.1 Data Transfer............................................................................................................................... 130
8.24 Scenario 2C1 – PHS IPv6 .......................................................................................................................... 131
8.24.1 Network Entry procedure ................................................................................................................... 132
8.24.1.1 Registration ................................................................................................................................. 132
8.24.2 Traffic Connection Establishment ...................................................................................................... 133
8.24.2.1 Service Flow Provisioning .......................................................................................................... 133
8.24.3 User Data Transfer ............................................................................................................................. 134
8.24.3.1 Data Transfer............................................................................................................................... 134
Page - vi
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.25 Scenario 2D0 – ROHC UDP/IPv4 streams ................................................................................................ 135
8.25.1 Network Entry procedure ................................................................................................................... 136
8.25.1.1 Registration ................................................................................................................................. 136
8.25.2 Traffic Connection Establishment ...................................................................................................... 137
8.25.2.1 Service Flow Provisioning .......................................................................................................... 137
8.25.3 User Data Transfer ............................................................................................................................. 138
8.25.3.1 Data Transfer............................................................................................................................... 138
8.26 Scenario 2D1 – ROHC UDP/IPv6 streams ................................................................................................ 138
8.26.1 Network Entry procedure ................................................................................................................... 139
8.26.1.1 Registration ................................................................................................................................. 139
8.26.2 Traffic Connection Establishment ...................................................................................................... 140
8.26.2.1 Service Flow Provisioning .......................................................................................................... 140
8.26.3 User Data Transfer ............................................................................................................................. 141
8.26.3.1 Data Transfer............................................................................................................................... 141
8.27 Scenario 2E0 – MS initiated Service Flow Establishment and Deletion ................................................... 142
8.27.1 MS initiated Service Flow Creation ................................................................................................... 143
8.27.2 UGS Data Transfer ............................................................................................................................. 143
8.27.3 MS initiated Service Flow Deletion ................................................................................................... 144
8.28 Scenario 2F0 – RT-VR/NRT-VR .............................................................................................................. 145
8.28.1 Traffic Connection Establishment ...................................................................................................... 146
8.28.1.1 RT-VR Service Flow Provisioning ............................................................................................. 146
8.28.1.2 NRT-VR Service Flow Provisioning .......................................................................................... 147
8.28.2 User Data Transfer ............................................................................................................................. 147
8.28.2.1 RT-VR Data Transfer .................................................................................................................. 147
8.28.2.2 NRT-VR Data Transfer ............................................................................................................... 148
8.29 Scenario 2G0- BS initiated Handover ....................................................................................................... 149
8.29.1 Neighbor Advertisement .................................................................................................................... 150
8.29.2 Scanning ............................................................................................................................................. 151
8.29.3 Scan Report ........................................................................................................................................ 151
8.29.4 Handover Decision ............................................................................................................................. 152
8.29.5 Handover Initiation............................................................................................................................. 152
8.29.6 Handover Verification ........................................................................................................................ 153
8.29.6.1 PING ........................................................................................................................................... 153
8.30 Scenario 2G1– Drop of Target BS During Handover ................................................................................ 154
8.30.1 Network re-entry with Serving BS ..................................................................................................... 155
8.30.2 Network re-entry Verification ............................................................................................................ 155
8.30.2.1 PING ........................................................................................................................................... 155
8.31 Scenario 2G2 – HO Cancel........................................................................................................................ 155
8.31.1 Neighbor Advertisement .................................................................................................................... 156
8.31.2 Network Re-entry with Serving BS .................................................................................................... 157
8.31.3 Network Re-entry Verification ........................................................................................................... 157
8.32 Scenario 2M0 – Multi-BS MBS ................................................................................................................ 158
8.32.1 MAP ................................................................................................................................................... 159
8.32.2 Traffic Connection Establishment ...................................................................................................... 160
8.32.2.1 Service Flow Provisioning .......................................................................................................... 160
8.32.3 User Data Transfer ............................................................................................................................. 161
8.32.3.1 Data Transfer............................................................................................................................... 161
8.33 Scenario 2N0 – FFR with segmented PUSC ............................................................................................. 162
8.33.1 Capabilities Negotiation ..................................................................................................................... 165
8.33.2 Registration ........................................................................................................................................ 165
8.33.2.1 Traffic Connection Establishment ............................................................................................... 166
8.33.2.1.1 Service Flow Provisioning ...................................................................................................... 166
Page - vii
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.33.2.2 Zone Indication for PUSC with all Sub-channels and Segmented PUSC ................................... 167
8.33.2.2.1 DL and UL Zone Switch IE for PUSC with all Sub-Channels ............................................... 167
8.33.2.3 User Data Transfer ...................................................................................................................... 168
8.33.2.3.1 File Data Transfer for BE service flows.................................................................................. 168
9.
MOBILE IOT AMENDMENT .................................................................................................................. 169
9.1
Amendment References ............................................................................................................................. 169
9.2
Amendment Definitions and abbreviations ............................................................................................... 169
9.2.1
Definitions .......................................................................................................................................... 169
9.2.2
Abbreviations ..................................................................................................................................... 171
9.3
Suggested Common System Mobile IOT amendment Profiles ................................................................. 172
9.3.1
TDD Frame Format ............................................................................................................................ 172
9.3.2
MAP Types ........................................................................................................................................ 172
9.3.3
Convergence Sub-layer ...................................................................................................................... 172
9.3.4
IP Address Configuration ................................................................................................................... 172
9.3.5
Test Structure ..................................................................................................................................... 173
9.3.6
Test Configurations ............................................................................................................................ 173
9.3.6.1
Single BS and Single MS – One Vendor..................................................................................... 173
9.3.6.2
Single BS and Single MS – Two Vendors .................................................................................. 174
9.3.6.3
Single BS and Two MS (from Same Vendor) ............................................................................. 175
9.3.6.4
Single BS and Two MS (From Different Vendors) ..................................................................... 175
9.3.6.5
Single BS and Three MS (Three Different Vendors) .................................................................. 176
9.3.6.6
Single MS and Two BS (for Handover) ...................................................................................... 177
9.3.7
Test Scenarios .................................................................................................................................... 177
9.3.7.1
PHY Tests ................................................................................................................................... 178
9.3.7.1.1 Number of OFDM Symbols in DL / UL ................................................................................... 178
9.3.7.1.1.1 Network Entry procedure ................................................................................................... 179
9.3.7.1.1.1.1 MS Synchronization and Ranging ............................................................................... 179
9.3.7.1.1.1.2 Capabilities Negotiation .............................................................................................. 180
9.3.7.1.1.1.3 Registration ................................................................................................................. 180
9.3.7.1.1.2 Traffic Connection Establishment ...................................................................................... 180
9.3.7.1.1.2.1 Service Flow Provisioning .......................................................................................... 180
9.3.7.1.1.3 User Data Transfer ............................................................................................................. 181
9.3.7.1.1.3.1 PING for BE service flows .......................................................................................... 181
9.3.7.1.1.3.2 File Data Transfer for BE service flows ...................................................................... 182
9.3.7.1.2 DL Subcarrier Allocation .......................................................................................................... 182
9.3.7.1.2.1 Network Entry procedure ................................................................................................... 183
9.3.7.1.2.1.1 MS Synchronization and Ranging ............................................................................... 183
9.3.7.1.2.1.2 Capabilities Negotiation .............................................................................................. 184
9.3.7.1.2.1.3 Registration ................................................................................................................. 184
9.3.7.1.2.2 Traffic Connection Establishment ...................................................................................... 185
9.3.7.1.2.2.1 Service Flow Provisioning .......................................................................................... 185
9.3.7.1.2.3 User Data Transfer ............................................................................................................. 185
9.3.7.1.2.3.1 PING for BE service flows .......................................................................................... 185
9.3.7.1.2.3.2 File Data Transfer for BE service flows ...................................................................... 186
9.3.7.1.3 Periodic Ranging....................................................................................................................... 186
9.3.7.1.3.1 Periodic Ranging Scenario 1 .............................................................................................. 186
9.3.7.1.4 BW Request .............................................................................................................................. 187
Page - viii
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
9.3.7.1.4.1 UGS Service Flow.............................................................................................................. 187
9.3.7.1.5 CQICH Fast Feedback .............................................................................................................. 188
9.3.7.1.5.1 BS initiated CQI Reporting using Fast Feedback Channel ................................................ 188
9.3.7.1.6 DL (Link Adaptation) based on Physical CINR Report on Pilots............................................. 189
9.3.7.1.6.1 Capabilities Negotiation During Network Entry Procedure ............................................... 190
9.3.7.1.6.2 PCINR Report for CQICH Allocation and Link Adaptation.............................................. 190
9.3.7.1.7 Downlink Modulation ............................................................................................................... 191
9.3.7.1.7.1 Support of different MSC level in DL ................................................................................ 191
9.3.7.1.7.1.1 Network Entry procedure ............................................................................................ 193
9.3.7.1.7.1.2 Traffic Connection Establishment ............................................................................... 194
9.3.7.1.7.1.3 User Data Transfer ...................................................................................................... 195
9.3.7.1.8 Uplink Modulation .................................................................................................................... 195
9.3.7.1.8.1 Verifying Uplink link adaptation ....................................................................................... 195
9.3.7.1.8.1.1 Data Transfer ............................................................................................................... 196
9.3.7.1.9 DL MIMO Mode Testing.......................................................................................................... 197
9.3.7.1.9.1 Block Diagram for MIMO Test Setup................................................................................ 199
9.3.7.1.9.2 Capabilities Negotiation during Network Entry ................................................................. 200
9.3.7.1.9.3 MAP ................................................................................................................................... 200
9.3.7.1.9.4 Data grants for the MS ....................................................................................................... 201
9.3.7.2
MAC Tests .................................................................................................................................. 201
9.3.7.2.1 PHS ........................................................................................................................................... 201
9.3.7.2.1.1 Basic MS & BS PHS support for UGS SF ......................................................................... 201
9.3.7.2.2 QoS service flows ..................................................................................................................... 202
9.3.7.2.2.1 Operation of pre-provisioned QoS service flows ............................................................... 202
9.3.7.2.2.2 ErtPS Service Flows ........................................................................................................... 203
9.3.7.2.2.2.1 Basic ertPS operation – one packet per UL grant ........................................................ 203
9.3.7.2.2.2.2 Basic ertPS operation – two packets per UL grant ...................................................... 205
9.3.7.2.3 Scan/Report Trigger Metrics..................................................................................................... 207
9.3.7.2.3.1 Scan Trigger Metric Test case (Mean BS RSSI/CINR Trigger metric type) ..................... 207
9.3.7.2.4 MS initiated Handover with Optimized Re-entry ..................................................................... 208
9.3.7.2.4.1 MS initiated handover test case Behavior .......................................................................... 209
9.3.7.2.4.1.1 Neighbor Advertisement ............................................................................................. 210
9.3.7.2.4.1.2 Scanning Initiation ...................................................................................................... 211
9.3.7.2.4.1.3 Handover Decision ...................................................................................................... 211
9.3.7.2.4.1.4 Handover Initiation ..................................................................................................... 211
9.3.7.2.4.1.5 Handover Confirmation ............................................................................................... 212
9.3.7.2.5 HO Ranging .............................................................................................................................. 213
9.3.7.2.5.1 Handover ranging test case Behavior ................................................................................. 213
9.3.7.2.6 Security ..................................................................................................................................... 214
9.3.7.2.6.1 PKMv2 Authorization initial network entry: initial network entry ................................... 214
9.3.7.2.7 PKMv2 Authorization network re-entry: network re-entry ..................................................... 215
9.3.7.2.7.1 Non Optimized Handoff ..................................................................................................... 215
9.3.7.2.7.2 Optimized Handoff............................................................................................................. 216
9.3.7.2.8 CMAC_KEY_COUNT Test Cases ........................................................................................... 217
9.3.7.2.8.1 CMAC Key Count test case 1 ............................................................................................ 217
9.3.7.2.8.2 CMAC Key Count test case 2 ............................................................................................ 218
9.3.7.2.8.3 CMAC Key Count test case 3 ............................................................................................ 219
9.3.7.2.8.4 CMAC Key Count test case 4 ............................................................................................ 220
9.3.7.2.8.5 CMAC Key Count test case 5 ............................................................................................ 221
Page - ix
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
1. Scope
This document specifies the WiMAX Forum® Inter-Operability Tests (MIOT) to certify compliance with the WiMAX
Forum Mobile Certification Profile [2], the WiMAX Forum System Profile [3] and the WiMAX Forum PICS [4]
Certification Testing. The standard specifications are found in the three IEEE 802.16 referenced documents, [1]. This
document replaces the approved WiMAX Forum Inter-Operability Tests for Wave 1 which are included here.
Page - 11
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
2. Purpose
The purpose of this document is to define test scenarios to verify the interoperability of mobile equipment that meets
WiMAX Forum Mobile Certification Profile [2]. These tests represent the third major test area for WiMAX Certification,
with the other two areas being the Protocol Conformance Test Cases [6] and the WiMAX Forum Radio Conformance Tests
[5]. The detailed processes for WiMAX Certification is found in WiMAX Forum Certification Program Reference
Document [6].
Section 9 of this document covers the MIOT amendment as normative requirement similar to the main section of the
document.
Page - 12
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
3. References
[1]
WiMAX Forum® Mobile Standard Reference, T23-004-R010, WiMAX Forum® Technical Working Group.
[2]
WiMAX Forum® Mobile Radio Specifications, T23-005-R015, WiMAX Forum® Technical Working Group.
[3]
WiMAX Forum® Mobile System Profile, T23-001-R010, WiMAX Forum® Technical Working Group.
[4]
WiMAX Forum® Mobile Protocol Implementation Conformance Statement (PICS) Proforma, T24-001-R010v06,
WiMAX Forum® Technical Working Group.
[5]
WiMAX Forum® Mobile Radio Conformance Tests, T25-002-R010, WiMAX Forum® Technical Working
Group.
[6]
WiMAX Forum® Certification Program Reference Manual, C16-001, WiMAX Forum® Technical Working
Group.
Page - 13
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
4. Abbreviations
BS
Base Station
CQI
Channel Quality Indicator
DL
Downlink
IOT
Inter-Operability Test
MBS
Multicast and Broadcast Services
MS
Mobile Station
NW
Network
PHS
Payload Header Suppression
ROHC
Robust Header Compression
SBS
Serving Base Station
SM
Spatial Multiplexing
TD
Test Description
TO
Transmission Opportunity
SUT
System Under Test
UGS
Unsolicited Grant Service
UL
Uplink
W1
Wave 1
W2
Wave 2
Page - 14
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
5. Mobile Interoperability Test Suite
5.1
How to use the Interoperability Test Suite
-
A test campaign is the execution of test scenarios according to the test scenario list.
-
The test campaign parameters in clause 7 shall be filled out prior to any test scenario execution. The test campaign
parameters specify how certain behavior can be triggered.
-
Some test descriptions can be executed several times with a different parameter set for each execution. In the case
where this is applicable, the test description list is appended below the test description Table.
5.2
How to document a Test Campaign
For each test campaign, the following chapters shall be printed out.
Clause 6:
Test Campaign Information - shall be filled out by the test participant(s).
Clause 7:
Test Campaign Parameters and Report - summarizes the results of the Test Campaign, is filled out during the
Test Campaign.
Clause 8:
Test Scenarios - shall be filled out during the Test Campaign.
A copy of each Text Campaign Report is provided to every test participant after the Test Campaign.
5.3
Test Configuration
The figure below represents the MIOT Test Bed with two BSs (different vendors except for Handoff) and three MS
(different vendors). It is assumed that this Test Bed will be validated and is referred to as the “Gold IOT Test Bed, with all
tests initially run in this testbed during validation. The IOT tests are conductive tests. Each unit under test has to provide a
RF interface for this purpose (female SMA or N connector). The data connector is the RJ45 LAN interface (Ethernet).
For a new vendor (MS or BS) to pass the IOT tests, the vendor replaces one of the units from the “Gold IOT Test Bed and
reruns the test case as specified in the Tables below.
Page - 15
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
BS1
BS2
Link 1
Link 2
Monitor
MS1
MS2
MS3
Figure 1 Basic Test Combinations for IOT Testing
5.3.1
Test Scenario List MS IOT
MS1 is the unit under test. MS in brackets are connected and have successfully performed NW entry before the IOT test
starts. Not mentioned BS is powered off or disconnected. MS2 without brackets is also unit under test with a different PHY
configuration (used for MIMO with collaborative SM). BSx(SBS&TBS) means that 2 units of the same vendor BS are used,
one playing the Serving BS role and the other one playing the Target BS role.
Page - 16
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
Nr.
1
WMF-T25-003-R010v08
Test Scenario Name
Configuration
Scenario 1a Basic Configuration **
MS1+(MS2+MS3)+BS1
2
3
4
5
MS1+(MS2+MS3)+BS2
Scenario 1b BS initiated CQI Reporting using Fast
Feedback Channel
MS1+(MS2+MS3)+BS1
Scenario 1c HARQ
MS1+(MS2+MS3)+BS1
6
7
MS1+(MS2+MS3)+BS2
Scenario 1c-B - HARQ on UL MAC Messages
MS1+(MS2+MS3)+BS1
8
9
MS1+(MS2+MS3)+BS2
Scenario 1d Mac-level ARQ
MS1+(MS2+MS3)+BS1
10
11
12
13
MS1+(MS2+MS3)+BS2
Scenario 1eb - BS initiated Open Loop Power Control
Activation
MS1+(MS2+MS3)+BS1
Scenario 1ec - Closed Loop Power Control
MS1+(MS2+MS3)+BS1
14
15
Scenario 1f – Security Version 2
MS1+(MS2+MS3)+BS1
MS1+(MS2+MS3)+BS2
Scenario 1g – MS initiated Sleep Mode
MS1+(MS2+MS3)+BS1
18
19
MS1+(MS2+MS3)+BS2
Scenario 1ha – MS initiated Idle Mode
MS1+(MS2+MS3)+BS1
20
21
MS1+(MS2+MS3)+BS2
Scenario 1hb – BS initiated Idle Mode
MS1+(MS2+MS3)+BS1
22
23
MS1+(MS2+MS3)+BS2
Scenario 1hc - Load balancing 1
MS1+(MS2+MS3)+BS1
24
25
MS1+(MS2+MS3)+BS2
Scenario 1i – ERT-VR
MS1+(MS2+MS3)+BS1
26
27
MS1+(MS2+MS3)+BS2
Scenario 1ja – MS initiated Handover
MS1+(MS2+MS3)+ BS1(SBS&TBS)
28
29
MS1+(MS2+MS3)+ BS2(SBS&TBS)
Scenario 2 PMP Configuration
MS1+MS2+ MS3+BS1
30
27
28
29
30
31
32
33
34
MS1+(MS2+MS3)+BS2
MS1+(MS2+MS3)+BS2
16
17
MS1+(MS2+MS3)+BS2
MS1+MS2+ MS3+BS2
Scenario 2A0 – DL PUSC with MIMO Matrix A and UL
PUSC with Collaborative SM
MS1+MS2+(MS3)+BS1
Scenario 2A1 – DL PUSC with MIMO Matrix B and UL
PUSC With Collaborative SM
MS1+MS2+(MS3)+BS1
Scenario 2B0 – Beam Forming with DL AMC with Dedicated
Pilots and UL AMC
MS1+(MS2+MS3)+BS1
Scenario 2B1 – Beam Forming with DL PUSC with
Dedicated Pilots and UL PUSC without channel rotation
MS1+(MS2+MS3)+BS1
MS1+MS2+(MS3)+BS2
MS1+MS2+(MS3)+BS2
MS1+(MS2+MS3)+BS2
MS1+(MS2+MS3)+BS2
Page - 17
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
35
36
37
38
39
40
41
WMF-T25-003-R010v08
Scenario 2AB0 – DL PUSC with dedicated pilot with MIMO
Matrix A and UL PUSC with Collaborative SM
MS1+MS2+(MS3)+BS1
Scenario 2AB1 – DL PUSC with dedicated pilot with Matrix
B MIMO and UL PUSC with Collaborative SM
MS1+MS2+(MS3)+BS1
Scenario 2AC0 -DL PUSC and UL PUSC without
subchannel rotation
MS1+(MS2+MS3)+BS1
Scenario 2C0 – PHS IPv4
MS1+(MS2+MS3)+BS1
MS1+(MS2+MS3)+BS2
Scenario 2C1 – PHS IPv6
MS1+(MS2+MS3)+BS1
44
45
MS1+(MS2+MS3)+BS2
Scenario 2D0 – ROHC UDP/IPv4 streams*
MS1+(MS2+MS3)+BS1
46
47
MS1+(MS2+MS3)+BS2
Scenario 2D1 – ROHC UDP/Ipv6 streams*
MS1+(MS2+MS3)+BS1
48
49
50
51
MS1+(MS2+MS3)+BS2
Scenario 2E0 – MS initiated Service Flow Creation and
Deletion
MS1+(MS2+MS3)+BS1
Scenario 2F0 – RT-VR/NRT-VR
MS1+(MS2+MS3)+BS1
52
53
Scenario 2G0- BS initiated Handover
MS1+(MS2+MS3)+BS1(SBS&TBS)
MS1+(MS2+MS3)+BS2(SBS&TBS)
Scenario 2G1– Drop of Target BS During Handover
56
57
MS1+(MS2+MS3)+BS1(SBS&TBS)
MS1+(MS2+MS3)+BS2(SBS&TBS)
Scenario 2M0 – Multi-BS MBS
MS1+(MS2+MS3)+BS1
58
59
MS1+(MS2+MS3)+BS2
MS1+(MS2+MS3)+BS2
54
55
MS1+MS2+(MS3)+BS2
MS1+(MS2+MS3)+BS2
42
43
MS1+MS2+(MS3)+BS2
MS1+(MS2+MS3)+BS2
Scenario 2N0 - FFR with segmented PUSC
MS1+(MS2+MS3)+BS1
60
MS1+(MS2+MS3)+BS2
* - Deferred
** For test Nr.1, BS1 should use compressed MAPs and for test Nr.2, BS2 should use the normal MAPs.
Page - 18
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
5.3.2
WMF-T25-003-R010v08
Test Scenario List BS IOT
BS1 is the unit under test. BS2 in brackets is connected and used for HO tests. Not mentioned MS are powered off or
disconnected. BSx(SBS&TBS) means that 2 units of the same vendor BS are used, one playing the Serving BS role and the
other one playing the Target BS role.
Page - 19
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
Nr.
1
WMF-T25-003-R010v08
Test Scenario Name
Configuration
Scenario 1a Basic Configuration
BS1+MS1
2
BS1+MS2
3
BS1+MS3
4
5
Scenario 1b BS initiated CQI Reporting using Fast Feedback
Channel
6
7
BS1+MS1
BS1+MS2
BS1+MS3
Scenario 1c HARQ
BS1+MS1
8
BS1+MS2
9
BS1+MS3
10
Scenario 1c-B - HARQ on UL MAC Messages
BS1+MS1
11
BS1+MS2
12
BS1+MS3
13
Scenario 1d Mac-level ARQ
BS1+MS1
14
BS1+MS2
15
BS1+MS3
16
17
Scenario 1eb - BS initiated Open Loop Power Control
Activation
18
19
BS1+MS1
BS1+MS2
BS1+MS3
Scenario 1ec – Closed Loop Power Control
BS1+MS1
20
BS1+MS2
21
BS1+MS3
22
Scenario 1f – Security Version 2
BS1+MS1
23
BS1+MS2
24
BS1+MS3
25
Scenario 1g – MS initiated Sleep Mode
BS1+MS1
26
BS1+MS2
27
BS1+MS3
28
Scenario 1ha – MS initiated Idle Mode
BS1+MS1
29
BS1+MS2
30
BS1+MS3
31
Scenario 1hb – BS initiated Idle Mode
BS1+MS1
32
BS1+MS2
33
BS1+MS3
34
Scenario 1hc - Load balancing 1
BS1+MS1
35
BS1+MS2
36
BS1+MS3
37
Scenario 1i – ERT-VR
BS1+MS1
38
BS1+MS2
Page - 20
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
39
40
BS1+MS3
Scenario 1j – MS initiated Handover
BS1(SBS&TBS)+MS1
41
BS1(SBS&TBS)+MS2
42
BS1(SBS&TBS)+MS3
43
Scenario 2 PMP Configuration
BS1+MS1+MS2+MS3
44
Scenario 2A0 – DL PUSC with MIMO Matrix A and UL PUSC
with Collaborative SM
BS1+MS1+MS2
45
46
47
48
BS1+MS3+MS1
Scenario 2A1 – DL PUSC with MIMO Matrix B and UL PUSC
With Collaborative SM
49
50
51
54
Scenario 2B0 – Beam Forming with DL AMC with Dedicated
Pilots and UL AMC
57
Scenario 2B1 – Beam Forming with DL PUSC with Dedicated
Pilots and UL PUSC without channel rotation
60
Scenario 2AB0 – DL PUSC with dedicated pilot with MIMO
Matrix A and UL PUSC with Collaborative SM
63
Scenario 2AB1 – DL PUSC with dedicated pilot with Matrix B
MIMO and UL PUSC with Collaborative SM
BS1+MS1
BS1+MS2
BS1+MS1+MS2
BS1+MS2+MS3
BS1+MS1+MS2
BS1+MS2+MS3
BS1+MS3+MS1
Scenario 2AC0 -DL PUSC and UL PUSC without subchannel
rotation
64
65
BS1+MS2
BS1+MS3+MS1
61
62
BS1+MS1
BS1+MS3
58
59
BS1+MS2+MS3
BS1+MS3
55
56
BS1+MS1+MS2
BS1+MS3+MS1
52
53
BS1+MS2+MS3
BS1+MS1
BS1+MS2
BS1+MS3
Scenario 2C0 – PHS IPv4
BS1+MS1
66
BS1+MS2
67
BS1+MS3
68
Scenario 2C1 – PHS IPv6
BS1+MS1
69
BS1+MS2
70
BS1+MS3
71
Scenario 2D0 – ROHC UDP/IPv4 streams*
BS1+MS1
72
BS1+MS2
73
BS1+MS3
74
Scenario 2D1 – ROHC UDP/Ipv6 streams*
BS1+MS1
75
BS1+MS2
76
BS1+MS3
77
Scenario 2E0 - MS initiated Service Flow Creation and
BS1+MS1
Page - 21
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
78
WMF-T25-003-R010v08
Deletion
BS1+MS2
79
80
BS1+MS3
Scenario 2F0 - RT-VR/NRT-VR
BS1+MS1
81
BS1+MS2
82
BS1+MS3
83
Scenario 2G0- BS initiated Handover
BS1(SBS&TBS)+MS1
84
BS1(SBS&TBS)+MS2
85
BS1(SBS&TBS)+MS3
86
Scenario 2G1– Drop of Target BS During Handover
BS1(SBS&TBS)+MS1
87
BS1(SBS&TBS)+MS2
88
BS1(SBS&TBS)+MS3
89
Scenario 2M0 – Multi-BS MBS
BS1+MS1
90
BS1+MS2
91
BS1+MS3
92
Scenario 2N0 - FFR with segmented PUSC
BS1+MS1
93
BS1+MS2
94
BS1+MS3
* - Deferred
5.4
Test Scenario Identifier Naming Conventions
The identifier of the test scenario is built according to the Table below.
Identifier: SC_<w>_<g>_<n>
<w> = wave
<g> = group
<n> = sequential number
1
2
A
B
C
D
E
F
G
H
J
K
L
M
N
Wave 1
Wave 2
MIMO
BF
PHS
ROHC
MS initiated Service Flow operations
RT-VR and NRT-VR QoS types
HO initiated by BS
Features of Scanning and Association
Sleep mode initiated by BS
FFB initiated by MS
HARQ
MBS
(0, 1, … )
Page - 22
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
5.5
WMF-T25-003-R010v08
TD Identifier Naming Conventions
The identifier of the TD is built according to the Table below.
Identifier: TD_<sc>_<pg>_<fg>_<nn>
<sc> = scenario
<pg> = protocol group
<fg> = function group
<nn> = sequential number
SC2A,…
ARQ
BF
BS_SLM
BS_GHF
FFB
GHF
MBS
MIMO
PHS
RLC
ROHC
ACQ
ADV
DTB
DAT
DSA
DSC
HOD
INI
PRNG
REG
SBC
SCN
ULG
NEW
Nn
Scenario Number
ARQ
Beam Forming
Sleep Mode initiated by the BS
General Handover Functionality initiated by
the BS
Fast Feedback
General Handover Functionality
Multicast and Broadcast services
MIMO
Payload Header Suppression
Radio Link Control
Robust Header Compression
Acquisition of DL and UL parameters
Advertisement
Drop of Target BS
User Data Transfer
Dynamic Service Addition
Dynamic Service Change
HO Decision
Initiation
Periodic Ranging
Registration
Negotiate Basic Capabilities
Scanning
UL grants
Network Entry
(00, 01, … )
Page - 23
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
5.6
WMF-T25-003-R010v08
Test Scenario List
The following Table contains a list of the test scenarios applicable to the interoperability testing process for Wave 2. Each
test scenario leads to one or more test descriptions.
Nr.
Test Scenario Name
Wave1
BS&M
S
Wave2BS
Wave2
MS
1
Scenario 1a Basic Configuration
M
M
M
2
Scenario 1b BS initiated CQI Reporting using Fast Feedback Channel
M
M
M
3
Scenario 1c HARQ
M
M
M
4
Scenario 1c-B - HARQ on UL MAC Messages
M
M
5
Scenario 1d Mac-level ARQ
M
M
M
6
Scenario 1eb BS initiated Open Loop Power Control
M
M
M
7
Scenario 1ec Closed Loop Power Control
M
M
M
8
Scenario 1f Security Version 2
M
M
M
9
Scenario 1g MS initiated Sleep Mode
M
M
M
10
Scenario 1ha MS initiated Idle Mode
M
M
M
11
Scenario 1hb BS initiated Idle Mode
M
M
M
12
Scenario 1hc - Load balancing 1
M
M
13
Scenario 1i ERT-VR
M
M
M
14
Scenario 1j MS initiated Handover
M
M
M
15
Scenario 2 PMP Configuration
M
M
M
16
Scenario 1c-B - HARQ on UL MAC Messages
M
M
17
Scenario 2A0 – DL PUSC with MIMO Matrix A and UL PUSC with
Collaborative SM
Scenario 2A1 – DL PUSC with MIMO Matrix B and UL PUSC With
Collaborative SM
Scenario 2B0 – Beam Forming with DL AMC with Dedicated Pilots and UL
AMC
IO-MIMO
M
IO-MIMO
M
IO-BF
(plus IOSND if
supported)
IO-BF
(plus IOSND if
supported)
IO-BF &
IO-MIMO
(plus IOSND if
supported)
IO-BF &
IO-MIMO
(plus IOSND if
supported)
M
M
M
18
19
20
Scenario 2B1 – Beam Forming with DL PUSC with Dedicated Pilots and UL
PUSC without channel rotation
21
Scenario 2AB0 – DL PUSC with dedicated pilot with MIMO Matrix A and UL
PUSC with Collaborative SM
22
Scenario 2AB1 – DL PUSC with dedicated pilot with Matrix B MIMO and UL
PUSC with Collaborative SM
23
24
Scenario 2AC0 -DL PUSC and UL PUSC without subchannel rotation
Scenario 2C0 – PHS IPv4
25
Scenario 2C1 – PHS IPv6
M
M
26
Scenario 2D0 – ROHC UDP/IPv4 streams
*
*
Page - 24
WiMAX FORUM PROPRIETARY
M
M
M
M
M
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
27
Scenario 2D1 – ROHC UDP/Ipv6 streams
*
*
28
Scenario 2E0 - MS initiated Service Flow Creation and Deletion
M
M
29
Scenario 2F0 - RT-VR/NRT-VR
M
M
30
Scenario 2G0 - BS initiated Handover
M
M
31
Scenario 2G1 – Drop of Target BS During Handover
M
M
32
Scenario 2M0 – Multi-BS MBS
IO-MBS
M
33
Scenario 2N0 – FFR with segmented PUSC
IO-MIMO
M
* - Deferred
Page - 25
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
6. Test Campaign Information
6.1
Date of statement
Date of statement
(MM/DD/YYYY):
6.2
Vendor Contact Person
IOT
Name
Location
Date
IOT Manager
Name.
Telephone Number
Fax Number
E-mail address
Additional
Information
6.3
Product Supplier for Test Bed
BS1
BS2
MS1
Vendor
Vendor Name
Model Name
Model Version
Firmware Version
Test Operator
Name.
Telephone Num
Fax Number
E-mail address
Additional
Information
Page - 26
WiMAX FORUM PROPRIETARY
MS2
MS3
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
7. Test Campaign Parameters and Report
7.1.1
Vendor Specific Instructions for UUT Setup
The following Table lists specific trigger/configure parameters required to run the IOT Tests. The Vendor shall
supply the method for enabling/disabling/initiating each of these trigger/configure parameters by either a test
interface or alternative way of enabling these triggers. In the Test Scenarios in Clause 8, these triggers are denoted
by their specific name and number(N). The vendor of the UUT should review each Test Condition Initialization and
indicate to the IOT Test House, how to accomplish this setup.
Table 7.1 Vendor Specific Instructions for UUT Setup
N
Feature
BS
MS
How to trigger/configure
1
Trigger BE Dynamic flow creation
Yes
No
_________________________________?
2
Allocate Fast feedback channel for MS
Yes
No
_________________________________?
3
Enable/Disable HARQ for transport
connection
Yes
No
_________________________________?
4
Enable/Disable ARQ for transport
connection
Yes
No
_________________________________?
5
Force Open loop Power Control
Yes
No
_________________________________?
6
Disable Open Loop Power Control
Yes
No
_________________________________?
7
Security Enable/Disable Authentication
Yes
No
_________________________________?
8
Trigger Sleep mode (definition with
activation)
No
Yes
_________________________________?
10
Trigger Idle mode
Yes
Yes
_________________________________?
11
Trigger ERT Dynamic flow creation
Yes
No
_________________________________?
12
Trigger Handover
No
Yes
_________________________________?
13
Configuration of DCD Message (Trigger
TLV)
Yes
No
_________________________________?
14
Configure BS
Yes
No
_________________________________?
16
Trigger Delete Service Flow (DSD-REQ)
No
Yes
_________________________________?
17
Trigger MS initiated Service Flow (DSAREQ)
No
Yes
_________________________________?
18
Trigger NRT-VR Dynamic flow creation
Yes
No
_________________________________?
19
Trigger RT-VR Dynamic flow creation
Yes
No
_________________________________?
21
Trigger BS initiated MBS Service Flow
(DSA-REQ)
Yes (IOMBS)
No
_________________________________?
22
Trigger MS initiated MBS Service Flow
(DSA-REQ)
No
Yes
_________________________________?
23
For BS initiated Handover, configure BS
so that BS initiated HO will occur before
the MS initiated HO. Or alternatively, the
vendor might provide a trigger for BS
initiated HO.
Yes
No
_________________________________?
Page - 27
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
25
Trigger to enable and disable MIMO
Matrix B at the BS
Yes
No
_________________________________?
26
Trigger the BS to move the MS to the
PUSC 1/1 zone
Yes
No
_________________________________?
27
Trigger the BS to move the MS to the
PUSC 1/3 zone
Yes
No
_________________________________?
For the UUT, the vendor shall submit the device to the laboratory so that it indicates, in the corresponding network
entry messages (SBC-REQ or REG-REQ, depending on the capability), that it supports each of the capabilities that
the vendor has declared as supported in the PICS. This is applicable to the following capabilities: HARQ, ARQ,
Open Loop Power Control, PKMv2, Sleep Mode, Idle Mode, and Handover.
The term BS shall be interpreted as a logical unit consisting of BS, ASN-Gateway functionality and AAA server
functionality. The reasons are missing standardization and conformance tests of the interfaces between these
network elements. It is not necessary to provide full conformant ASN-GW and CSN AAA servers as specified in
NWG Nework Architecture specifications, but any implementation of the required backbone capabilities specified
above (i.e. ASN/CSN emulator).
The UUT should have the capability to enable user data transfer via PING or FTP. The S/N levels will be set in such
a way that virtually no errors will occur during the user data transfer tests. The maximum allowed packet error rate
of the user data transfer of the UUT is 0.5 percent over at least 10 seconds if a successful user data transfer is part
the pass/fail criterion in the test scenarios unless otherwise specified in the test description. For the BS,
configuration method like local maintenance tools to configure the provided network elements shall be provided.
7.1.2
MS Test campaign parameters
Test campaign parameters to be provided by vendor. The vendor shall specify how that Triggers are set in order for
the test lab to run the each test.
Nr
Item
Question
Answer
SBC
1
PIC_MAX_SBC_REQ_RETRIES
What maximum number of retries on
SBC-REQs does the UUT support?
_____
PIC_MAX_REG_REQ_RETRIES
What maximum number of retries on
REG-REQs does the UUT support?
_____
3
PIC_MAX_DSx_REQ_RETRIES
What maximum number of retries on
DSx-REQs does the UUT support?
_____
4
PIC_MAX_DSx_RSP_RETRIES
What maximum number of retries on
DSx-RSPs does the UUT support?
_____
REG
2
DSA
Page - 28
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
7.1.3
WMF-T25-003-R010v08
BS Test campaign parameters
Test campaign parameters to be provided by vendor.
Nr
Item
Question
Answer
DSA
1
PIC_MAX_DSx_REQ_RETRIES
What maximum number of retries on
DSx-REQs does the UUT support?
_____
2
PIC_MAX_DSx_RSP_RETRIES
What maximum number of retries on
DSx-RSPs does the UUT support?
_____
7.2
Test campaign report
The following Table enables test operators to build a summary of the execution of the test scenarios for the IOT
tests.
Nr.
TD ID
Selected?
Yes/No
Run?
Yes/No
Verdict
Pass/Fail
Page - 29
WiMAX FORUM PROPRIETARY
Observations
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Scenario 1a – Basic
Configuration
TD ID
1
TD_SC1a_RLC_IRNG_00
2
TD_SC1a_RLC_SBC_00
3
TD_SC1a_RLC_REG_00
4
TD_SC1a_RLC_DSA_00
5
TD_SC1a_RLC_DAT_00
6
TD_SC1a_RLC_DAT_01
OK/NOK
Scenario 1b BS initiated CQI
Reporting using Fast Feedback
Channel
TD ID
7
TD_SC1b_FFB_SBC_00
8
TD_SC1b_FFB_SBC_01
OK/NOK
Scenario 1c- HARQ
TD ID
9
TD_SC1c_HARQ_SBC_00
10
TD_SC1c_HARQ_DSA_00
11
TD_SC1c_HARQ_DAT_00
12
TD_SC1c_HARQ_DAT_01
OK/NOK
Scenario 1c- Mac-level ARQ
TD ID
13
TD_SC1d_ARQ_REG_00
14
TD_SC1d_ARQ_DSA_00
15
TD_SC1d_ARQ_DAT_00
16
TD_SC1d_ARQ_DAT_01
OK/NOK
Scenario 1eb BS initiated Open
Loop Power Control
TD ID
17
TD_SC1eb_BS_OPC_SBC_00
18
TD_SC1eb_BS_OPC_PMC_00
19
TD_SC1eb_BS_OPC_DAT_00
OK/NOK
Scenario 1ec Closed Loop Power
Control
Page - 30
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
TD ID
20
TD_SC1ec_CPC_IRNG_00
21
TD_SC1ec_CPC_DAT_00
WMF-T25-003-R010v08
OK/NOK
Scenario 1f Security Version 2
TD ID
22
TD_SC1f_SEC_SBC_00
23
TD_SC1f_SEC_AUTH_00
24
TD_SC1f_SEC_TEK_00
25
TD_SC1f_SEC_DAT_00
26
TD_SC1f_SEC_REAUTH_00
27
TD_SC1f_SEC_DAT_01
OK/NOK
Scenario 1g MS initiated Sleep
Mode
TD ID
28
TD_SC1g_MS_SLM_INI_00
29
TD_SC1g_MS_SLM_PRNG_00
30
TD_SC1g_MS_SLM_DAT_00
31
TD_SC1g_MS_SLM_INI_01
32
TD_SC1g_MS_SLM_DAT_01
OK/NOK
Scenario 1ha MS initiated Idle
Mode
TD ID
33
TD_SC1h_MS_IDM_REG_00
34
TD_SC1h_MS_IDM_DREG_00
35
TD_SC1h_MS_IDM_INI_00
36
TD_SC1h_MS_IDM_DAT_00
37
TD_SC1h_MS_IDM_DREG_01
38
TD_SC1h_MS_IDM_DAT_01
39
TD_SC1h_MS_IDM_DREG_02
40
TD_SC1h_MS_IDM_DOWN
OK/NOK
Scenario 1hb BS initiated Idle
Mode
TD ID
41
TD_SC1h_BS_IDM_REG_00
42
TD_SC1h_BS_IDM_DREG_00
43
TD_SC1h_BS_IDM_DAT_00
OK/NOK
Page - 31
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Scenario 1i ERT-VR
TD ID
44
TD_SC1i_DSA_00
45
TD_SC1i_DAT_00
OK/NOK
Scenario 1j MS initiated Handover
TD ID
46
TD_SC1j_MS_GHF_ADV_00
47
TD_SC1j_MS_GHF_HOD_00
48
TD_SC1j_MS_GHF_NWE_00
49
TD_SC1j_MS_GHF_DAT_00
OK/NOK
Scenario 2 P2MP Configuration
TD ID
50
TD_SC2_RLC_IRNG_00
51
TD_SC2_RLC_SBC_00
52
TD_SC2_RLC_REG_00
53
TD_SC2_RLC_DSA_00
54
TD_SC2_RLC_DAT_00
55
TD_SC2_RLC_DAT_01
Nr.
TD ID
OK/NOK
Selected?
Yes/No
Run?
Yes/No
Verdict
Pass/Fail
Page - 32
WiMAX FORUM PROPRIETARY
Observations
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Scenario 2A0 – DL PUSC with
MIMO Matrix A and UL PUSC
with Collaborative SM
TD ID
55
TD_SC2A0_MIMO_SBC_00
56
TD_SC2A0_MIMO_DAT_00
57
TD_SC2A0_MIMO_DAT_01
58
TD_SC2A0_MIMO_DAT_02
OK/NOK
Scenario 2A1 – DL PUSC with
MIMO Matrix B and UL PUSC
With Collaborative SM
TD ID
59
TD_SC2A1_MIMO_SBC_00
60
TD_SC2A1_MIMO_DAT_00
61
TD_SC2A1_MIMO_DAT_01
62
TD_SC2A1_MIMO_DAT_02
OK/NOK
Scenario 2B0 – Beam Forming
with DL AMC with Dedicated
Pilots and UL AMC
TD ID
63
TD_SC2BO_BF_SBC_00
64
TD_SC2BO_BF_DAT_00
65
TD_SC2BO_BF_DAT_01
66
TD_SC2BO_BF_DAT_02
OK/NOK
Scenario 2B1 – Beam Forming
with DL PUSC with Dedicated
Pilots and UL PUSC without
channel rotation
TD ID
67
TD_SC2B1_BF_SBC_00
68
TD_SC2B1_BF_DAT_00
69
TD_SC2B1_BF_DAT_01
70
TD_SC2B1_BF_DAT_02
OK/NOK
Scenario 2AB0 – DL PUSC with
dedicated pilot with MIMO
Matrix A and UL PUSC with
Collaborative SM
TD ID
71
OK/NOK
TD_SC2AB0_MIMO_SBC_00
Page - 33
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
72
TD_SC2AB0_MIMO_DAT_00
73
TD_SC2AB0_MIMO_DAT_01
74
TD_SC2AB0_MIMO_DAT_02
WMF-T25-003-R010v08
Scenario 2AB1 – DL PUSC with
dedicated pilot with Matrix B
MIMO and UL PUSC with
Collaborative SM
TD ID
75
TD_SC2AB1_MIMO_SBC_00
76
TD_SC2AB1_MIMO_DAT_00
77
TD_SC2AB1_MIMO_DAT_01
78
TD_SC2AB1_MIMO_DAT_02
OK/NOK
Scenario 2C0 – PHS IPv4
TD ID
79
TD_SC2C0_PHS_REG_00
80
TD_SC2C0_PHS_DSA_00
81
TD_SC2C0_PHS_DAT_00
OK/NOK
Scenario 2C1 – PHS IPv6
TD ID
82
TD_SC2C1_PHS_REG_00
83
TD_SC2C1_PHS_DSA_00
84
TD_SC2C1_PHS_DAT_00
OK/NOK
Scenario 2D0 – ROHC UDP/IPv4
streams
TD ID
85
TD_SC2D0_ROHC_REG_00
86
TD_SC2D0_ROHC_DSA_00
87
TD_SC2D0_ROHC_DAT_00
OK/NOK
Scenario 2D1 – ROHC UDP/Ipv6
streams
TD ID
88
TD_SC2D1_ROHC_REG_00
89
TD_SC2D1_ROHC_DSA_00
90
TD_SC2D1_ROHC_DAT_00
OK/NOK
Scenario 2E0 - MS initiated
Service Flow
Page - 34
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Creation/Modification/Deletion
TD ID
91
TD_SC2E0_RLC_DSA_00
92
TD_SC2E0_RLC_DAT_00
93
TD_SC2E0_RLC_DSD_00
OK/NOK
Scenario 2F0 - RT-VR/NRT-VR
TD ID
94
TD_SC2F0_RLC_DSA_00
95
TD_SC2F0_RLC_DSA_00
96
TD_SC2F0_RLC_DAT_00
97
TD_SC2F0_RLC_DAT_00
OK/NOK
Scenario 2G0 - BS initiated
Handover
TD ID
98
TD_SC2G0_BS_GHF_ADV_00
99
TD_SC2G0_BS_GHF_SCN_00
100
TD_SC2G0_BS_GHF_SCNRPT_00
101
TD_SC2G0_BS_GHF_HOD_00
102
TD_SC2G0_BS_GHF_NWE_00
103
TD_SC2G0_BS_GHF_DAT_00
OK/NOK
Scenario 2G1 – Drop of Target
BS During Handover
TD ID
104
TD_SC2G1_GHF_DTB_00
105
TD_SC2G1_GHF_DAT_00
OK/NOK
Scenario 2M0 – Multi-BS MBS
TD ID
106
TD_SC2M0_MBS_ACQ_00
107
TD_SC2M0_MBS_DSA_00
108
TD_SC2M0_MBS_DAT_00
OK/NOK
Scenario 1c-B - HARQ on UL
MAC Messages
TD ID
109
TD_SC1c-B_HARQ_SBC_00
110
TD_SC1c-B_HARQ_MAC_00
OK/NOK
Page - 35
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
111
TD_SC1c-B_HARQ_DSA_00
112
TD_SC1c-B_HARQ_DAT_00
113
TD_SC1c-B_HARQ_DAT_01
WMF-T25-003-R010v08
Scenario 1hc - Load balancing 1
TD ID
114
TD_SC1hc_RLC_IRNG_00
115
TD_SC1hc_RLC_SBC_00
116
TD_SC1hc_RLC_REG_00
117
TD_SC1hc_RLC_DSA_00
118
TD_SC1hc_RLC_DAT_00
119
TD_SC1hc_RLC_DAT_01
OK/NOK
Scenario 2AC0 -DL PUSC and
UL PUSC without subchannel
rotation
TD ID
125
TD_SC2AC0_MIMO_SBC_00
126
TD_SC2AC0_MIMO_DAT_00
127
TD_SC2AC0_MIMO_DAT_01
128
TD_SC2AC0_MIMO_DAT_02
OK/NOK
Scenario 2N0 - FFR with
segmented PUSC
TD ID
120
TD_SC2N0_FFR_SBC_00
121
TD_SC2N0_FFR_REG_00
122
TD_SC2N0_FFR_DSx_00
123
TD_SC2N0_FFR_DSx_01
124
TD_SC2N0_FFR_DAT_00
OK/NOK
Page - 36
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8. Test Scenarios
Each test scenario contains a table to provide a summary description of the test scenario and single pass/fail verdict
and several additional Test Description (TD) test tables used to describe the detailed test procedures. In the case of
an unsuccessful test scenario, the test lab will use the TD test tables “Result Column” to indicate which was the
primary event that failed (OK/NOK) for diagnostic purposes.
8.1
Scenario 1a - Basic Configuration
Test scenario behaviour
Ref
Scenario 1a - Basic Configuration
Goal
Verify the exchange of Ping Traffic and User Data Transfer.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Optional.
HARQ: Optional.
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
- For this test, BS1 should use compressed MAPs and BS2 should use normal MAPs in order to
ensure that the MS can properly receive and process both types of MAPs.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
Pass verdict
criterion
Final Verdict
-
1)
2)
3)
4)
5)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure.
Carry out 1 DL and 1 UL BS initiated BE service flow.
Carry out DL and UL data transfer
a) via the PING procedure:
Host behind the BS pings the MS or pings the host behind the
MS (depending on the type of MS)
Host behind the MS or the
MS itself (depending on the type of the MS) pings the host behind the BS
b) via freestyle BE (such as FTP) data transfer (5 minute transfer for some stability evaluation).
Successful exchange of Ping Traffic and DL/UL data transfer.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 37
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.1.1
WMF-T25-003-R010v08
Network Entry procedure
8.1.1.1
MS Synchronization and Ranging
Test Description
Identifier:
TD_SC1a_RLC_IRNG_00
Description:
Verify that a BS sends broadcast messages (DL-MAP, UL-MAP, UCD, DCD) when switched on and that
MS synchronizes with the BS. Verify the successful completion of initial ranging.
Pre-test
conditions:
MS is deregistered from BS. MS is switched off. BS remains on. BS is configured to transmit in the lowest
channel (fL). Then MS is switched on.
Step
Test Sequence
Result
1
BS sends DL-MAP in every frame.
OK
NOK
2
BS sends UL-MAP if appropriate.
OK
NOK
3
BS sends DCD every ten second(max).
OK
NOK
4
BS sends UCD every ten second(max).
OK
NOK
5
MS synchronizes to the BS.
OK
NOK
6
MS sends initial CDMA ranging codes in the Initial Ranging Region.
OK
NOK
7
BS sends RNG-RSP
OK
NOK
OK
NOK
9
RNG-RSP (with Ranging Status = success),
or CDMA_Allocation_IE in UL-MAP
BS sends
OK
NOK
10
RNG-RSP (with Ranging Status = success) followed by
CDMA_Allocation_IE,
or CDMA_Allocation_IE only.
MS sends RNG-REQ.
OK
NOK
OK
NOK
8
with optional Power, Time or Frequency adjustments.
with ranging status = continue or success
If the Ranging Status = continue in Step 7, MS sends initial CDMA ranging code
in the Periodic Ranging Region until receiving:
-
11
Fill the gap with the MS MAC address read in the RNG-REQ and determine
MAC Address.
MS MAC address:
12
BS sends RNG-RSP with ranging status = success.
OK
NOK
13
Fill the gap with the Basic Cid and Primary Management Cid assigned to the MS
in the RNG-RSP.
OK
NOK
Basic CID:
Prim CID:
Observations
Page - 38
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.1.1.2
WMF-T25-003-R010v08
Capabilities Negotiation
Test Description
Identifier:
TD_SC1a_RLC_SBC_00
Description:
Verify the successful completion of basic capabilities negotiation.
Pre-test
conditions:
Successful completion of initial ranging.
Step
Test Sequence
Result
1
MS sends 1 or more SBC-REQ
OK
NOK
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
with its capabilities set to on.
Are TLVs defined appropriate to the device capabilities?
BS sends SBC-RSP
OK
NOK
-
With valid TLVs that are present in the SBC-REQ appropriate for the
Wave capabilities,
and with values that do not enable a feature disabled/not supported
by MS.
Observations
8.1.1.3
Registration
Test Description
Identifier:
TD_SC1a_RLC_REG_00
Description:
Verify the successful completion of registration.
Pre-test
conditions:
Successful completion of basic capabilities negotiation. No authentication is required.
Step
Test Sequence
Result
1
MS sends 1 or more REG-REQ
OK
NOK
2
not more than PIC_MAX_REG_REQ_RETRIES of REG-REQs,
including valid TLVs defined for the appropriate Wave.
BS sends REG-RSP
OK
NOK
-
with response set to OK.
with valid TLVs that are present in the REG-REQ are in the appropriate
Wave,
and with values that do not enable a feature disabled/not supported by
MS.
Observations
Page - 39
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.1.2
WMF-T25-003-R010v08
Traffic Connection Establishment
8.1.2.1
Service Flow Provisioning
Test Description
Identifier:
TD_SC1a_RLC_DSA_00
Description:
Verify the successful completion of service flow establishment as in TD_SC1a_RLC_DSA_List.
Pre-test
conditions:
Successful completion of registration and 1 DL and 1 UL Service Flows are Pre-Provisioned at the BS for
this MS and the MS can support the Pre-Provisioned Service Flows.
Step
Test Sequence
Result
1
BS sends 1 or more DSA-REQ
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs.
MS sends 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs.
BS sends DSA-ACK
OK
NOK
-
Confirmation Code set to OK.
Observations
TD_SC1a_RLC_DSA_List
Nr.
Stimulate the BS to use the following parameters
Status
Run
UL DSA-REQ
1
Service Flow Scheduling Type set to BE
m
Yes/No
m
Yes/No
DL DSA-REQ
2
Service Flow Scheduling Type set to BE
Page - 40
WiMAX FORUM PROPRIETARY
Result
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.1.3
WMF-T25-003-R010v08
User Data Transfer
8.1.3.1
PING
Test Description
Identifier:
TD_SC1a_RLC_DAT_00
Description:
Verify the successful completion of data transfer via the PING procedure.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number.
Step
Test Sequence
1
Host behind the BS pings the host behind the MS.
The CID of the DL MAC PDU (EchoRequest) is the Transport Cid of
the DL Service Flow.
The CID of the UL MAC PDU (EchoReply) is the Transport Cid of the
UL Service Flow.
Is the PING procedure successfully completed?
Host behind the MS pings the host behind the BS.
Result
OK
NOK
OK
NOK
-
2
-
The CID of the UL MAC PDU (EchoRequest) is the Transport Cid of
the UL Service Flow.
The CID of the DL MAC PDU (EchoReply) is the Transport Cid of the
DL Service Flow.
Is the PING procedure successfully completed?
Observations
8.1.3.2
File Data Transfer
Test Description
Identifier:
TD_SC1a_RLC_DAT_01
Description:
Verify the successful completion of file data transfer for 5 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number.
Step
Test Sequence
Result
1
Has the data from the MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to the MS been transferred correctly?
OK
NOK
Observations
Page - 41
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.2
WMF-T25-003-R010v08
Scenario 1b – BS initiated CQI Reporting using Fast Feedback Channel
Test scenario behaviour
Ref
Scenario 1b – BS initiated CQI Reporting using Fast Feedback Channel.
Goal
Verify the Fast Feedback Channel Allocation of the BS and Fast Feedback Reporting of the MS
during DL data transfer.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Disable
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used to
specify the burst shall set ACK disable = 1.
- Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’.
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
-
Pass verdict
criterion
1) Start the monitor message capture. This is the only scenario that needs a monitor in order to
check that MS sends CINR report headers.
2) Switch on the MS.
3) Carry out the Network Entry procedure with CQI Reporting support..
4) Carry out 1 DL BS initiated BE service flow.
5) BS allocates Fast feedback channel for MS. (Table 7.1 / Item 2).
6) Carry out DL data transfer with enhanced fast feedback activated (BS assigns a CQI channel),
via freestyle BE (such as FTP) data transfer (5 minute transfer for some stability evaluation).
Successful DL data transfer with enhanced fast feedback activated; MS sends CINR report (CQI) in
the assigned fast-feedback channel.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 42
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.2.1
WMF-T25-003-R010v08
Network Entry procedure
8.2.1.1
Capabilities Negotiation
Test Description
Identifier:
TD_SC1b_FFB_SBC_00
Description:
Verify the Fast Feedback capabilities negotiation.
Pre-test
conditions:
X
Step
1
Test Sequence
MS sends 1 or more SBC-REQ
OK
NOK
OK
NOK
-
2
not more than PIC_SBC_REQ_MAX_RETRIES SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs
Uplink Control Channel Support indicating enhanced fast feedback
support,
OFDMA MS CINR measurement capability indicating Physical CINR
measurement from the preamble.
BS sends SBC-RSP
Result
-
with TLVs that are present in the SBC-REQ, and with values
that do not enable a feature disabled by MS,
confirming the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs,
confirming Uplink Control Channel Support
confirming OFDMA MS CINR measurement capability
Observations
Page - 43
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.2.1.2
WMF-T25-003-R010v08
MAP
Test Description
Identifier:
TD_SC1b_FFB_SBC_01
Description:
Verify the fast feedback channel allocation, CQI feedback and the successful completion of file data
transfer for 5 minutes.
Pre-test
conditions:
1 DL Service Flow is established. The classification rule for mapping the CID is based on IP address/port
number.
Step
1
Test Sequence
BS sends UCD with:
-
2
Result
OK
NOK
OK
NOK
OK
NOK
Size of the CQICH_ID field. In case of default value, the BS doesn’t
need to send the size of the CQICH_ID field.
BS sends UCD with:Fast Feedback Region TLV, allocating the fast
feedback region.
and/or BS sends UL-MAP or compressed UL-MAP with:
-
Fast Feedback Allocation IE, allocating the fast-feedback region if a
Fast Feedback Region TLV is not included in the UCD or overriding the
fast-feedback region allocation made with a Fast Feedback Region
TLV included in the UCD.
BS sends UL-MAP or compressed UL-MAP with:
-
3
CQICH Allocation IE, allocating the fast-feedback slots.
MS sends CINR report as indicated in the CQICH Allocation IE.
4
Has the data from the BS to the MS been transferred correctly?
Observations
Page - 44
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.3
WMF-T25-003-R010v08
Scenario 1c – HARQ
Test scenario behaviour
Ref
Scenario 1c – HARQ
Goal
Verify the use of HARQ with chase combining during data transfer when no packet error rate is
introduced. This test may be replaced with an HARQ test with packet errors at a later date.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Disable.
HARQ: Enable.
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
Pass verdict
criterion
Final Verdict
-
1)
2)
3)
4)
5)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure with HARQ support for transport connections.
Carry out 1 DL and 1 UL BS initiated BE service flow with HARQ support. (Table 7.1 / Item 3).
Carry out DL and UL data transfer with HARQ activated.
a) via freestyle BE (such as FTP) data transfer. (5 minute transfer for some stability evaluation).
Successful DL/UL data transfer and HARQ is activated for DL/UL data transfer.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 45
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.3.1
WMF-T25-003-R010v08
Network Entry procedure
8.3.1.1
Capabilities Negotiation
Test Description
Identifier:
TD_SC1c_HARQ_SBC_00
Description:
Verify HARQ capabilities negotiation.
Pre-test
conditions:
X
Step
1
Test Sequence
MS sends 1 or more SBC-REQ
OK
NOK
OK
NOK
-
2
not more than PIC_SBC_REQ_MAX_RETRIES SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs,
OFDMA MAP Capability, bit#1 = 1 (Extended HARQ IE capability)
OFDMA MS Demodulator”, bit#2 = 1 (DL CTC)
And bit#5 = 1 (DL HARQ Chase):
OFDMA MS Modulator”, bit#2 = 1 (UL CTC) and bit#4 = 1 (UL HARQ
Chase):
HARQ Chase Combining and CC-IR Buffer Capability,
Maximum number of burst per frame capability in HARQ.
The number of DL/UL HARQ Channels
BS sends SBC-RSP
Result
-
with TLVs that are present in the SBC-REQ, and with values
that do not enable a feature disabled by MS,
confirming the support of the following capability using OFDMA
Parameters Set and/or individual TLVs,
confirming HARQ capability.
Observations
Page - 46
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.3.2
WMF-T25-003-R010v08
Traffic Connection Establishment
8.3.2.1
Service Flow Provisioning
Test Description
Identifier:
TD_SC1c_HARQ_DSA_00
Description:
Verify the activation of HARQ during traffic connection establishment.
Pre-test
conditions:
Registration completed.
Step
Test Sequence
1
BS sends 1 or more DSA-REQ, if HARQ is enabled for the transport connection,
Result
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES DSA-REQs,
HARQ Service Flows, = 1 (enabled)
HARQ Channel mapping (if specific HARQ channels (ACIDs) are to be
used on the connection),
PDU SN extended subheader for HARQ reordering (if reordering PDUs
at the receiver is enabled.
MS sends 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES DSA-RSPs.
BS sends DSA-ACK
OK
NOK
-
-
Confirmation Code set to OK.
Observations
Page - 47
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.3.3
WMF-T25-003-R010v08
User Data Transfer
8.3.3.1
Verification of DL HARQ Allocations
Test Description
Identifier:
TD_SC1c_HARQ_DAT_00
Description:
Verify the use of HARQ during DL data transfer.
Pre-test
conditions:
1 DL Service Flow is established and Fast Feedback Channel is established
Step
Test Sequence
Result
1
BS sends DL MAP with
OK
NOK
2
- HARQ DL MAP IE containing DL HARQ Chase Sub Burst IE.
BS sends
OK
NOK
3
HARQ allocation containing one or more PDUs and 16 bit CRC.
BS sends UL-MAP
OK
NOK
OK
NOK
OK
NOK
4
MS
-
5
in the same frame as the DL HARQ allocation (ACK is one frame after
DL allocation)
with HARQ ACKCH Region Allocation IE defining an ACK region.
decodes the DL HARQ allocation
then Ms sends ACK or NACK in the correct HARQ ACK channel.
BS
-
6
either re-sends previous blocks, if MS NACKs. The retransmission
allocation uses the same ACID as the previous allocation with the
AI_SN maintained.
or send a new sub-burst, if MS ACKs and DL data is available for
transmission. The next allocation that uses the same ACID has the
AI_SN toggled.
Has the data from the BS to the MS been transferred correctly?
Observations
Page - 48
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.3.3.2
WMF-T25-003-R010v08
Verification of UL HARQ Allocations
Test Description
Identifier:
TD_SC1c_HARQ_DAT_01
Description:
Verify the use of HARQ during UL data transfer.
Pre-test
conditions:
1 UL Service Flow is established.
Step
1
Test Sequence
BS sends UL-MAP with
-
Result
OK
NOK
HARQ UL MAP IE containing UL HARQ Chase Sub Burst IE with UL
allocation to MS’s Basic CID.
2
MS
OK
NOK
3
MS decodes the HARQ UL MAP IE
encodes the UL HARQ allocation,
containing MAC PDUs and 16 bit CRC.
BS decodes the UL HARQ allocation.
OK
NOK
OK
NOK
-
4
Requests retransmission if UL allocation was unsuccessful by using
the same value of AI_SN bit and ACID from previous allocation
Or requests new transmission if UL allocation was successful. The next
allocation that uses the same ACID has the AI_SN toggled.
Has the data from the MS to the BS been transferred correctly?
Observations
Page - 49
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.4
WMF-T25-003-R010v08
Scenario 1c-B – HARQ on UL MAC Messages
Test scenario behaviour
Ref
Scenario 1c-B – HARQ on UL MAC Messages
Goal
Verify the use of HARQ with chase combining on UL HARQ bursts containing UL MAC messages
after SBC negotiation and during data transfer when no packet error rate is introduced.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Disable.
HARQ on data bursts: Enable.
HARQ on UL MAC messages after SBC negotiation: Enable (optional for DL MAC messages)
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
-
1)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure with HARQ enabled for MAC management
messages (PKM, REG, and DSA), if supported by both MS and BS, and with HARQ support for
transport connections.
4)
Carry out 1 DL and 1 UL BS initiated BE service flow with HARQ support.
5)
Carry out DL and UL data transfer with HARQ activated.
a) via freestyle BE (such as FTP) data transfer. (5 minute transfer for some stability evaluation).
Successful DL/UL data transfer and HARQ is activated for DL/UL data transfer.
2)
3)
Pass verdict
criterion
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 50
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.4.1
WMF-T25-003-R010v08
Network Entry procedure
8.4.1.1
Capabilities Negotiation
Test Description
Identifier:
TD_SC1c-B_HARQ_SBC_00
Description:
Verify HARQ capabilities negotiation.
Pre-test
conditions:
X
Step
1
Test Sequence
MS sends 1 or more SBC-REQ
OK
NOK
OK
NOK
-
2
not more than PIC_SBC_REQ_MAX_RETRIES SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs,
OFDMA MAP Capability, bit#1 = 1 (Extended HARQ IE capability)
OFDMA MS Demodulator”, bit#2 = 1 (DL CTC)
And bit#5 = 1 (DL HARQ Chase):
OFDMA MS Modulator”, bit#2 = 1 (UL CTC) and bit#4 = 1 (UL HARQ
Chase):
HARQ Chase Combining and CC-IR Buffer Capability,
Maximum number of burst per frame capability in HARQ.
The number of DL/UL HARQ Channels
UL service flow compound TLV (type 145) with
* HARQ Service Flow TLV = 1
* Optional HARQ channel Mapping TLV (default is all ACIDs used)
* PDU SN extended subheader for HARQ reordering TLV
Optionally, DL service flow compound TLV (type 146) with
* HARQ Service Flow TLV = 1
* Optional HARQ channel Mapping TLV (default is all ACIDs used)
* PDU SN extended subheader for HARQ reordering TLV
BS sends SBC-RSP
Result
-
with TLVs that are present in the SBC-REQ, and with values
that do not enable a feature disabled by MS,
confirming the support of the following capability using OFDMA
Parameters Set and/or individual TLVs,
confirming HARQ capability.
Observations
Page - 51
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.4.2
WMF-T25-003-R010v08
HARQ on UL MAC messages
8.4.2.1
Verification of UL HARQ Allocations of UL MAC messages
Test Description
Identifier:
TD_SC1c-B_HARQ_MAC_00
Description:
Verify the use of HARQ on UL MAC messages during initial network entry.
Pre-test
conditions:
SBC negotiation completed
Step
Test Sequence
Result
1
MS transmits BR code to UL BW to transmit BRH
OK
NOK
2
BS sends CDMA allocation IE as a response to the BR code.
OK
NOK
3
MS transmits Bandwidth Request Header requesting UL BW enough to transmit
PKM-REQ (REG-REQ).
OK
NOK
4
BS sends HARQ UL-MAP IE with HARQ UL Chase subburst IE.
OK
NOK
5
MS transmits PKM-REQ (REG-REQ) using the UL burst allocated with the
HARQ UL-MAP IE.
OK
NOK
6
BS decodes the UL HARQ allocation.
OK
NOK
OK
NOK
OK
NOK
7
8
Requests retransmission if UL allocation was unsuccessful by using
the same value of AI_SN bit and ACID from previous allocation.
BS transmits PKM-RSP (REG-RSP)
-
either using normal DL MAP IE
-
or using HARQ DL-MAP IE with HARQ DL Chase subburst IE (if HARQ
on DL MAC messages supported by both BS and MS).
Has the data from the BS to the MS been transferred correctly?
Observations
For Steps 3, 5, and 7, PKM messages (PKM-REQ/RSP) are transmitted in the stage of PKM process, and REG
messages (REG-REQ/RSP) are transmitted in the stage of REG process after accomplishing PKM process.
Page - 52
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.4.3
WMF-T25-003-R010v08
Traffic Connection Establishment
8.4.3.1
Service Flow Provisioning
Test Description
Identifier:
TD_SC1c-B_HARQ_DSA_00
Description:
Verify the activation of HARQ during traffic connection establishment.
Pre-test
conditions:
Registration completed.
Step
Test Sequence
1
BS sends 1 or more DSA-REQ, if HARQ is enabled for the transport connection,
Result
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES DSA-REQs,
HARQ Service Flows, = 1 (enabled)
HARQ Channel mapping: Optional (TLV is present if specific HARQ
channels (ACIDs) are to be used on the connection),
PDU SN extended subheader for HARQ reordering (if reordering PDUs
at the receiver is enabled.
MS sends 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES DSA-RSPs.
BS sends DSA-ACK
OK
NOK
-
-
Confirmation Code set to OK.
Observations
Page - 53
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.4.4
WMF-T25-003-R010v08
User Data Transfer
8.4.4.1
Verification of DL HARQ Allocations
Test Description
Identifier:
TD_SC1c-B_HARQ_DAT_00
Description:
Verify the use of HARQ during DL data transfer.
Pre-test
conditions:
1 DL Service Flow is established and Fast Feedback Channel is established
Step
Test Sequence
Result
1
BS sends DL MAP with
OK
NOK
2
- HARQ DL MAP IE containing DL HARQ Chase Sub Burst IE.
BS sends
OK
NOK
3
HARQ allocation containing one or more PDUs and 16 bit CRC.
BS sends UL-MAP
OK
NOK
OK
NOK
OK
NOK
4
MS
-
5
in the same frame as the DL HARQ allocation (ACK is one frame after
DL allocation)
with HARQ ACKCH Region Allocation IE defining an ACK region.
decodes the DL HARQ allocation
then Ms sends ACK or NACK in the correct HARQ ACK channel.
BS
-
6
either re-sends previous blocks, if MS NACKs. The retransmission
allocation uses the same ACID as the previous allocation with the
AI_SN maintained.
or send a new sub-burst, if MS ACKs and DL data is available for
transmission. The next allocation that uses the same ACID has the
AI_SN toggled.
Has the data from the BS to the MS been transferred correctly?
Observations
Page - 54
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.4.4.2
WMF-T25-003-R010v08
Verification of UL HARQ Allocations
Test Description
Identifier:
TD_SC1c-B_HARQ_DAT_01
Description:
Verify the use of HARQ during UL data transfer.
Pre-test
conditions:
1 UL Service Flow is established.
Step
1
Test Sequence
BS sends UL-MAP with
-
Result
OK
NOK
HARQ UL MAP IE containing UL HARQ Chase Sub Burst IE with UL
allocation to MS’s Basic CID.
2
MS
OK
NOK
3
MS decodes the HARQ UL MAP IE
encodes the UL HARQ allocation,
containing MAC PDUs and 16 bit CRC.
BS decodes the UL HARQ allocation.
OK
NOK
OK
NOK
-
4
Requests retransmission if UL allocation was unsuccessful by using
the same value of AI_SN bit and ACID from previous allocation
Or requests new transmission if UL allocation was successful. The next
allocation that uses the same ACID has the AI_SN toggled.
Has the data from the MS to the BS been transferred correctly?
Observations
Page - 55
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.5
WMF-T25-003-R010v08
Scenario 1d – Mac-level ARQ
Test scenario behaviour
Ref
Scenario 1d – Mac-level ARQ [11]
Goal
Verify the exchange of data transfer with ARQ active without packet errors. This test may be
replaced with an HARQ test with packet errors at a later date.….
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Enable.
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used to
specify the burst shall set ACK disable = 1.
- Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’.
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
Pass verdict
criterion
Final Verdict
-
1)
2)
3)
4)
5)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure with ARQ support.
Carry out 1 DL and 1 UL BS initiated BE service flow with ARQ support.(Table 7.1 / Item 4)
Carry out DL and UL data transfer with ARQ activated.
a) via freestyle BE (such as FTP) data transfer.
Successful exchange of DL/UL data transfer and ARQ is activated for DL/UL data transfer.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 56
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.5.1
WMF-T25-003-R010v08
Network Entry procedure
8.5.1.1
Registration
Test Description
Identifier:
TD_SC1d_ARQ_REG_00
Description:
Verify the activation of ARQ during registration.
Pre-test
conditions:
X
Step
Test Sequence
Result
1
MS sends 1 or more REG-REQ
OK
NOK
2
not more than PIC_MAX_REG_REQ_RETRIES REG-REQs,
ARQ Support,
ARQ ACK Type.
BS sends REG-RSP
OK
NOK
-
with TLVs that are present in the REG-REQ, and with values
that do not enable a feature disabled by MS,
confirming ARQ support.
Observations
Page - 57
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.5.2
WMF-T25-003-R010v08
Traffic Connection Establishment
8.5.2.1
Service Flow Provisioning
Test Description
Identifier:
TD_SC1d_ARQ_DSA_00
Description:
Verify the activation of ARQ during traffic connection establishment.
Pre-test
conditions:
Registration completed.
Step
Test Sequence
Result
1
BS sends 1 or more DSA-REQ
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES DSA-REQs,
ARQ_enable,
ARQ_WINDOW_SIZE,
ARQ_RETRY_TIMEOUT_TRANSMITTER_DELAY or
ARQ_RETRY_TIMEOUT_RECEIVER_DELAY,
ARQ_BLOCK_LIFETIME,
ARQ_SYNC_LOSS_TIMEOUT,
ARQ_DELIVER_IN_ORDER,
ARQ_RX_PURGE_TIMEOUT,
ARQ_BLOCK_SIZE.
MS sends 1 or more DSA-RSP
OK
NOK
OK
NOK
-
3
not more than PIC_DSx_RSP_MAX_RETRIES DSA-RSPs
ARQ_RETRY_TIMEOUT_TRANSMITTER_DELAY or
ARQ_RETRY_TIMEOUT_RECEIVER_DELAY,
ARQ_BLOCK_SIZE.
BS sends DSA-ACK
-
Confirmation Code set to OK.
Observations
Page - 58
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.5.3
WMF-T25-003-R010v08
User Data Transfer
8.5.3.1
Verification of DL ARQ Allocations
Test Description
Identifier:
TD_SC1d_ARQ_DAT_00
Description:
Verify the use of ARQ during DL data transfer.
Pre-test
conditions:
1 DL Service Flow is established.
Step
Test Sequence
1
BS sends
2
DL allocation(s) to basic CID
or compressed DL allocation(s) to basic CID.
BS sends
-
Result
OK
NOK
OK
NOK
OK
NOK
One or more PDUs including packing and/or fragmentation subheaders
with BSN,
on Transport Cid.
3
MS
4
receives PDU’s on one or more DL allocations
sends an ARQ ACK that allows the MS to ACK or NACK each
individual block.
BS re-sends previous blocks, if there were NACK’s by the MS.
OK
NOK
5
Has the data from the BS to the MS been transferred correctly?
OK
NOK
-
Observations
Page - 59
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.5.3.2
WMF-T25-003-R010v08
Verification of UL ARQ Allocations
Test Description
Identifier:
TD_SC1d_ARQ_DAT_01
Description:
Verify the use of ARQ during UL data transfer.
Pre-test
conditions:
1 UL Service Flow is established.
Step
Test Sequence
1
BS sends
2
UL allocation(s) to basic CID
or compressed UL allocation(s) to basic CID.
MS sends
-
3
OK
NOK
OK
NOK
OK
NOK
PDUs including packing and/or fragmentation subheaders with BSN,
on Transport Cid.
BS
-
Result
receives PDU’s on one or more UL allocations
sends an ACK or NACK for each block.
4
MS
OK
NOK
5
re-sends previous blocks, if there were NACK’s by the BS.
Has the data from the MS to the BS been transferred correctly?
OK
NOK
Observations
Page - 60
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.6
WMF-T25-003-R010v08
Scenario 1eb – BS initiated Open Loop Power Control
Test scenario behaviour
Ref
Scenario 1eb BS Initiated Open Loop Power Control
Goal
Open Loop Power Control is activated by BS. Check that a data transfer continues properly when
there is a fading in the UL channel (needs to be simulated by introducing a certain amount of
attenuation).
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Optional
HARQ: Optional.
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 UL and DL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
-
1)
2)
3)
4)
5)
6)
Pass verdict
criterion
BS Force Open loop Power Control (Table 7.1 / Item 5)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure with BS initiated Open Loop Power Control Activation.
Carry out 1 UL and DL BS initiated BE service flow.
Carry out UL data transfer via freestyle Best Effort (such as FTP) data transfer. During UL data
transfer the MSs UL power is brought to a distance from the desired power level, e.g. with an
attenuator, in order to simulate fading on the UL. In parallel the DL is also attenuated by the
same amount.
Attenuation is introduced during UL data transfer. The data are transferred correctly and the
connection will not be lost.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 61
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.6.1
WMF-T25-003-R010v08
Open Loop Power Control Activation
Test Description
Identifier:
TD_SC1eb_BS_OPC_SBC_00
Description:
Verify the Open Loop Power Control support during negotiation of basic capabilities.
Pre-test
conditions:
BS “Force Open loop Power Control” Table 7.1 / Item 5.
Step
1
Test Sequence
MS sends 1 or more SBC-REQ
OK
NOK
OK
NOK
-
2
not more than PIC_SBC_REQ_MAX_RETRIES SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs,
‘OFDMA MS uplink power control support’ TLV - indicating Uplink open
loop power control support,
with the minimum number of frames that SS takes to switch
from the closed loop power control scheme to the opened loop power
control scheme
with the MS's maximum transmit power for BPSK,QPSK,16-QAM, and
64-QAM (if supported).
BS sends SBC-RSP
Result
-
with TLVs that are present in the SBC-REQ, and with values
that do not enable a feature disabled by MS,
confirming the support of the following capability using OFDMA
Parameters Set and/or individual TLVs,
confirming Open Loop Power Control support.
Observations
Page - 62
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Test Description
Identifier:
TD_SC1eb_BS_OPC_PMC_00
Description:
Verify the Open Loop Power Control Activation.
Pre-test
conditions:
X
Step
Test Sequence
1
BS sends PMC-RSP in unsolicited manner,
Power control mode change = 0b10 or 0b01(Cor2) for Open Loop
power control passive mode
MS sends PMC-REQ,
Result
OK
NOK
OK
NOK
-
2
-
Power control mode change = 0b10 or 0b01(Cor2) for Open Loop
power control passive mode
Confirmation = 1
Observations
8.6.2
Open Loop Power Control during User Data Transfer
Test Description
Identifier:
TD_SC1eb_BS_OPC_DAT_00
Description:
Verify the use of Open Loop Power Control during data transfer.
Pre-test
conditions:
1 UL and DL Service Flow is established and Open Loop Power Control is activated.
During User Data Transfer the MSs UL power is brought to a distance from the desired power level, e.g.
with an attenuator, in order to simulate fading on the UL. In parallel the DL is also attenuated by the
same amount.
Step
Test Sequence
Result
1
BS allocates UL BW sufficient for data transfer.
OK
NOK
2
BS sends to MS
OK
NOK
OK
NOK
OK
NOK
RNG-RSP with power, corrections and status continue or success, or,
unsolicited RNG-RSP with power, corrections and status continue or
success, or
Fast Power Control (FPC) message, or
UL-MAP with Power Control IE.
Verify that BS power corrections are used by MS – or, if MS tx power not readily
available - verify that no additional power corrections adjustments made by BS.
-
3
4
Has the data from the MS to the BS been transferred correctly?
Observations
Page - 63
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.7
WMF-T25-003-R010v08
Scenario 1ec - Closed Loop Power Control
Test scenario behaviour
Ref
Scenario 1e Power Control [11]
Goal
Check that a data transfer continues properly when there is a fading in the UL channel (needs to be
simulated by introducing a certain amount of attenuation) and Closed Loop Power Control is active.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Open Loop Power Control: Not active.
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Optional
HARQ: Optional
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 UL and 1 DL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
-
1)
2)
3)
4)
5)
6)
Pass verdict
criterion
Start the monitor message capture, if available.
Trigger BS to disable Open loop Power Control (Table 7.1 / Item 6)
Switch on the MS.
Carry out the Network Entry procedure.
Carry out 1 UL and 1 DL BS initiated BE service flow.
Carry out UL data transfer via freestyle Best Effort (such as FTP) data transfer. During UL data
transfer the MSs UL power is brought to a distance from the desired power level, e.g. with an
attenuator, in order to simulate fading on the UL. In parallel the DL can also be attenuated by
the same amount.
Attenuation is introduced during UL data transfer. The data are transferred correctly and the
connection will not be lost.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 64
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.7.1
WMF-T25-003-R010v08
Initial Ranging
Test Description
Identifier:
TD_SC1ec_CPC_IRNG_00
Description:
Verify the use of Closed Loop Power Control during initial ranging.
Pre-test
conditions:
X
Step
Test Sequence
Result
1
BS sends RNG-RSP
OK
NOK
2
with possibly Power, Time or Frequency adjustments.
MS sends initial CDMA ranging codes
OK
NOK
OK
NOK
-
where the new transmit power is
P_t = P_last + P_adjust
P_t (is the new transmit power)
P_last (is the previous transmit power)
P_adjust (is the correction term as sent by the BS in previous RNGRSP)
MS sends initial CDMA ranging codes until BS sends RNG-RSP
3
-
with ranging status success
then the MS begins negotiation of basic capabilities.
Observations
8.7.2
Closed Loop Power Control during User Data Transfer
Test Description
Identifier:
TD_SC1ec_CPC_DAT_00
Description:
Verify the use of Closed Loop Power Control during data transfer.
Pre-test
conditions:
1 UL Service Flow is established. During User Data Transfer the MSs UL power is brought to a distance
from the desired power level, e.g. with an attenuator, in order to simulate fading on the UL. In parallel the
DL can also be attenuated by the same amount.
Step
Test Sequence
Result
1
BS allocates UL BW sufficient for data transfer.
OK
NOK
2
BS sends
OK
NOK
OK
NOK
OK
NOK
RNG-RSP with power, corrections and status continue or success, or
unsolicited RNG-RSP with power corrections and status continue or
success, or
Fast Power Control (FPC) message, or
UL-MAP with Power Control IE
Verify that BS power corrections are used by MS – or, if MS tx power not readily
available - verify that no additional power corrections adjustments made by BS.
-
3
4
Has the data from the MS to the BS been transferred correctly?
Observations
Page - 65
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.8
WMF-T25-003-R010v08
Scenario 1f – Security Version 2
Test scenario behavior
Ref
Scenario 1f – Security Version 2
Goal
Verify the general security process.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Disable.
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used to
specify the burst shall set ACK disable = 1.
- Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’.
- Authentication: Enabled.
- Authentication method shall be compliant to NWG WiMAX Forum Network Architecture, Stage 3
document, v1.1.1, section 4.4.1.2.2 or 4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
-
1)
2)
3)
4)
5)
6)
7)
Pass verdict
criterion
Enable PKMv2 (Table 7.1 / Item 7)
Configure MS according to item nr #1 of TD_SC1f_SEC_List.
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure with PKMv2 .
Carry out 1 DL and 1 UL BS initiated BE service flow.
Carry out DL and UL data transfer
a) via the PING procedure:
Host behind the BS pings the MS or pings the host behind the MS (depending on the type of
MS)
Host behind the MS or the MS itself (depending on the type of the MS pings the host behind the
BS.
8) Wait for reauthorization (Periodic TEK refresh is running).
9) Wait until periodic TEK refresh uses the new AK.
10) Carry out again DL and UL data transfer
a) via the PING procedure:
Host behind the BS pings the MS or pings the host behind the MS (depending on the type of
MS)
Host behind the MS or the MS itself (depending on the type of the MS pings the host behind the
BS.
11) Repeat steps 1) to 9) for the other items of TD_SC1f_SEC_List
Successful execution of Initial Authentication, PKM v.2 SA-TEK 3-way handshake, Periodic TEK
refresh process
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 66
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.8.1
WMF-T25-003-R010v08
Security Capabilities Negotiation
Test Description
Identifier:
TD_SC1f_SEC_SBC_00
Description:
Verify the successful completion of security capabilities negotiation.
Pre-test
conditions:
X
Step
1
Test Sequence
MS sends 1 or more SBC-REQ
OK
NOK
OK
NOK
OK
NOK
-
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs,
with its capabilities set to on,
indicating in PKM Version Support the support of PKM version 2.
BS sends SBC-RSP
Result
-
3
with TLVs that are present in the SBC-REQ,
and with values that do not enable a feature disabled/not supported by
MS.
Fill the gap with the Security Negotiation Parameters assigned to the MS in the
SBC-RSP.
Authorization Policy Support
at initial network entry:
Message Authentication Code Mode:
PN Window Size:
Maximum number of supported Security Associations:
Observations
Page - 67
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.8.2
WMF-T25-003-R010v08
Authentication and Authorization
Test Description
Identifier:
TD_SC1f_SEC_AUTH_00
Description:
Verify the successful completion of Authentication and Authorization.
Pre-test
conditions:
Successful completion of security capabilities negotiation. MS and BS have negotiated to perform PKMv2
EAP.
Step
Test Sequence
Result
1
MS may send PKMv2 EAP Start.
OK
NOK
2
MS and BS exchange EAP messages over PKMv2 EAP-Transfer
OK
NOK
3
BS sends PKMv2 EAP - Transfer
OK
NOK
4
with EAP-success.
Are Master Session Key, KEK, CMAC UL key and CMAC DL key created?
OK
NOK
Observations
Page - 68
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.8.3
WMF-T25-003-R010v08
3-way handshake and SA creation
Test Description
Identifier:
TD_SC1f_SEC_TEK_00
Description:
Verify the successful completion of 3-way handshake and SA creation.
Pre-test
conditions:
Successful completion of Authentication and Authorization.
Step
Test Sequence
Result
1
BS sends PKMv2 SA-TEK-Challenge
OK
NOK
2
with CMAC Digest.
MS sends PKMv2 SA-TEK-REQ
OK
NOK
OK
NOK
OK
NOK
OK
NOK
OK
NOK
-
3
indicates its security capabilities with Security Negotiation Parameters
that were included in the SBC-REQ,
with CMAC Digest.
BS sends PKMv2 SA-TEK-RESPONSE
-
4
with primary SA and zero or more static SAs,
confirming the successful validation of the PKMv2 SA-TEK-REQ,
with CMAC Digest,
shall have the same SEC Negotiation Parameters included in the SBCRSP.
Fill the gap with the number of SAs defined in the SA descriptor list assigned to
the MS in the PKMv2 SA-TEK-RESPONSE.
Number of SAs defined in SA Descriptor List:
5
6
MS sends for each SA a PKMv2 KEY-REQ unless the data encryption algorithm
is No Data Encryption
with a SAID,
with the AK sequence number.
BS sends a PKMv2 KEY-REPLY for each PKMv2 KEY-REQ
-
with older and newer TEK parameters.
Observations
Page - 69
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.8.4
WMF-T25-003-R010v08
User Data Transfer
8.8.4.1
PING
Test Description
Identifier:
TD_SC1f_SEC_DAT_00
Description:
Verify the successful completion of data transfer via the PING procedure.
Pre-test
conditions:
Successful completion of 3-way handshake.
1 UL and 1 DL BE Service Flow is established.
Step
Test Sequence
1
Host behind the BS pings the host behind the MS.
-
Result
OK
NOK
The CID of the DL MAC PDU (EchoRequest) is the Transport Cid of
the DL Service Flow.
The CID of the UL MAC PDU (EchoReply) is the Transport Cid of the
UL Service Flow.
Is the PING procedure successfully completed?
Observations
8.8.5
Periodic TEK Refresh
Test Description
Identifier:
TD_SC1f_SEC_REAUTH_00
Description:
Verify the successful completion of Periodic TEK Refresh
Pre-test
conditions:
Successful completion of 3-way handshake and SA creation and successful PING unless the CipherSuite is NO Data Encryption.
Step
Test Sequence
1
MS sends for each SA a PKMv2 KEY-REQ unless the Cipher –Suite is NO Data
Encryption
Result
OK
NOK
2
before the older TEK material expires,
in order to acquire newer TEK material.
BS sends a PKMv2 KEY-REPLY for each PKMv2 KEY-REQ
OK
NOK
3
with older and newer TEK parameters.
MS continues with Periodic TEK refresh.
OK
NOK
OK
NOK
4
The periodic TEK refresh produces key material where the newer key material
has a key sequence number one greater than (modulo 4) that of the older key
material.
Observations
Page - 70
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.8.6
WMF-T25-003-R010v08
User Data Transfer with refreshed key material
8.8.6.1
PING
Test Description
Identifier:
TD_SC1f_SEC_DAT_01
Description:
Verify the successful completion of data transfer, with refreshed key material via the PING procedure.
Pre-test
conditions:
Successful completion of 3-way handshake and SA creation.
1 UL and 1 DL BE Service Flow is established.
Successful completion of Periodic TEK refresh and Reauthorization.
Step
1
Test Sequence
Result
Host behind the BS pings the host behind the MS.
-
OK
NOK
The CID of the DL MAC PDU (EchoRequest) is the Transport Cid of
the DL Service Flow.
The CID of the UL MAC PDU (EchoReply) is the Transport Cid of the
UL Service Flow.
Is the PING procedure successfully completed?
Observations
TD_SC1f_SEC_List
Nr.
Configure the MS to use the following parameters
Status
Run
SA-TEK-REQ
1
Cryptographic-Suite-List indicating only: 0x010001
o
Yes/No
o
Yes/No
o
Yes/No
m
Yes/No
o
Yes/No
o
Yes/No
o
Yes/No
CBC-Mode 56-bit DES, no data authentication and 3-DES,128
2
Cryptographic-Suite-List indicating only: 0x010002
CBC-Mode 56-bit DES, no data authentication and RSA, 1024
3
Cryptographic-Suite-List indicating only: 0x020103
CCM-Mode 128-bit AES, CCM-Mode, 128-bit, ECB mode AES
with 128-bit key
4
Cryptographic-Suite-List indicating only: 0x020104
CCM-Mode 128bits AES, CCM-Mode, AES Key Wrap with 128bit key
5
Cryptographic-Suite-List indicating only: 0x030003
CBC-Mode 128-bit AES, no data authentication, ECB mode AES
with 128-bit key
6
Cryptographic-Suite-List indicating only: 0x080003
MBS CTR Mode 128 bits AES, no data authentication, AES ECB
mode with 128-bit key
7
Cryptographic-Suite-List indicating only: 0x080004
MBS CTR mode 128 bits AES, no data authentication, AES Key
Wrap with 128-bit key
Page - 71
WiMAX FORUM PROPRIETARY
Result
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.9
WMF-T25-003-R010v08
Scenario 1g- MS initiated Sleep Mode
Test scenario behaviour
Ref
Scenario 1g- MS Initiated Sleep Mode
Goal
Verify the MS initiated sleep mode activation.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
TRF-IND Required: set.
TTWF (traffic trigger wakening flag): set.
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Optional
HARQ: Optional
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
-
1)
2)
3)
4)
5)
Pass verdict
criterion
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure.
Carry out 1 DL and 1 UL BS initiated BE service flow.
Trigger MS (Table 7.1 / Item 8) to initiate sleep mode procedure. TRF-IND Required is set,
TTWF (traffic trigger wakening flag) is set for DL and UL connection.
6) Once, MS is in sleep mode, host behind BS pings host behind MS.
7) Trigger MS (Table 7.1 / Item 8) to activate the deactivated PSC.
8) Host behind MS or the MS itself (depending on the type of the MS) pings host behind BS.
Successfully MS initiated sleep mode. MS awakes in order to receive traffic reception, re-initiates
sleep mode and awakes again in order to send traffic.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
8.9.1
Setup of MS initiated Sleep Mode
Test Description
Identifier:
TD_SC1g_MS_SLM_REG_00
Description:
Verify the Sleep Mode parameters during registration.
Pre-test
conditions:
MS is performing network entry.
Step
Test Sequence
Page - 72
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
1
WMF-T25-003-R010v08
MS sends 1 or more REG-REQ
not more than PIC_MAX_REG_REQ_RETRIES of REGREQs
BS sends REG-RSP
OK
NOK
OK
NOK
-
2
-
-
with response set to OK,
with TLVs that are present in the REG-REQ,
and with values that do not enable a feature disabled/not
supported by MS.
with idle mode timeout TLV.
Observations
8.9.2
MS initiated Sleep Mode
Test Description
Identifier:
TD_SC1g_MS_SLM_INI_00
Description:
Verify the successful completion of MS initiated Sleep Mode.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
No data is to be sent.
Step
Test Sequence
Result
1
MS sends 1 or more MOB_SLP-REQs (Initiated by Trigger in Table 7.1 / Item 8)
OK
NOK
2
with one or more PSC definitions and activating one PSC,
or only defining a PSC.
BS sends MOB_SLP-RSP
OK
NOK
-
if MOB_SLP-REQ defined and activated a PSC, then MOB_SLP-RSP
confirms and optionally reconfigures sleep mode parameters,
if MOB_SLP-REQ did only define a PSC, the MOB_SLP-RSP activates
and possibly reconfigures sleep mode parameters.
Observations
Page - 73
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.9.3
WMF-T25-003-R010v08
Sleep Mode Verification
Test Description
Identifier:
TD_SC1g_MS_SLM_PRNG_00
Description:
Verify Sleep Mode.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established. PSC is defined and activated with TRF-IND Required that
includes DL connection.
No data is to be sent. MS is in sleep mode.
Step
Test Sequence
1
BS sends MOB_TRF-INDs
at least one MOB_TRF-IND during each listening window of the
Power Saving Class,
with negative indication.
MS may participate in periodic ranging. The successful periodic ranging does not
deactivate any PSC.
Result
OK
NOK
OK
NOK
-
2
Observations
8.9.4
BS initiated PING
Test Description
Identifier:
TD_SC1g_MS_SLM_DAT_00
Description:
Verify the successful completion of BS sleep mode deactivation.
Pre-test
conditions:
Sleep Mode is activated. Host behind BS pings host behind MS. PSC is defined and activated with TRFIND Required that includes DL connection and TTWF (traffic trigger wakening flag) is set.
Step
Test Sequence
Result
1
BS sends MOB_TRF-IND
OK
NOK
2
with positive indication.
MS receives MOB_TRF_IND and deactivates PSC
OK
NOK
3
Data is transferred.
OK
NOK
-
Is the PING procedure successfully completed?
Observations
Page - 74
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.9.5
WMF-T25-003-R010v08
MS initiated activation of deactivated PSC
Test Description
Identifier:
TD_SC1g_MS_SLM_INI_01
Description:
Verify the successful completion of MS activation of deactivated sleep mode.
Pre-test
conditions:
Sleep Mode is deactivated. No data to be sent.
Step
Test Sequence
Result
1
MS sends 1 or more MOB_SLP-REQs activating the PSC (Initiated by Trigger in
Table 7.1 / Item 8)
OK
NOK
2
BS sends MOB_SLP-RSP to confirm.
OK
NOK
3
BS sends MOB_TRF-INDs
OK
NOK
-
at least one MOB_TRF-IND during each listening window of the
Power Saving Class,
with negative indication.
Observations
8.9.6
MS initiated PING
Test Description
Identifier:
TD_SC1g_MS_SLM_DAT_01
Description:
Verify the successful completion of MS sleep mode deactivation.
Pre-test
conditions:
Sleep Mode is activated. Host behind MS pings host behind BS. PSC is defined and activated with TRFIND Required that includes UL connection and TTWF (traffic trigger wakening flag) is set.
Step
Test Sequence
Result
1
MS sends Bandwidth Request Header and deactivates PSC.
OK
NOK
2
BS receives BW request header and deactivates PSC.
OK
NOK
3
Data is transferred.
OK
NOK
-
Is the PING procedure successfully completed?
Observations
Page - 75
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.10
WMF-T25-003-R010v08
Scenario 1ha - MS initiated Idle Mode
Test scenario behaviour
Ref
Scenario 1ha- MS Idle Mode
Goal
Verify MS initiated Idle Mode.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Optional.
HARQ: Optional.
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
Pass verdict
criterion
Final Verdict
-
1) Start the monitor message capture, if available.
2) Switch on the MS.
3) Carry out the Network Entry procedure.
4) Carry out 1 DL and 1 UL BS initiated BE service flow.
5) Trigger MS to initiate idle mode procedure. TABLE 7.1 / Item 10)
6) Once, MS is in idle mode, host behind BS pings host behind MS.
7) BS Pages the MS and the MS performs Network Re-Entry.
8) Trigger MS to re-initiate idle mode procedure. TABLE7.1 / Item 10)
9) Host behind MS or the MS itself (depending on the type of the MS) pings host behind BS.
10) Trigger MS to re-initiate idle mode procedure. TABLE 7.1 / Item 10)
11) Power down MS.
Successful exchange of Ping Traffic and DL/UL data transfer.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 76
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.10.1 MS initiated Idle Mode
Test Description
Identifier:
TD_SC1h_MS_IDM_REG_00
Description:
Verify the Idle Mode parameters during registration.
Pre-test
conditions:
MS is performing network entry.
Step
Test Sequence
Result
1
MS sends 1 or more REG-REQ
OK
NOK
2
not more than PIC_MAX_REG_REQ_RETRIES of REG-REQs
With bit#2 = 1 in the “Mobility features supported” TLV.
BS sends REG-RSP
OK
NOK
-
3
with response set to OK,
with TLVs that are present in the REG-REQ,
and with values that do not enable a feature disabled/not supported by
MS.
Mobility feature supported: bit#1 (SLM) equals 0. bit#2 (Idle) equals 1
with idle mode timeout TLV.
Fill the gap with the Idle Mode Timer value assigned to the MS in the REG-RSP.
Idle Mode Timer:
Observations
Test Description
Identifier:
TD_SC1h_MS_IDM_DREG_00
Description:
Verify the successful completion of MS initiated Idle Mode.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
No data is to be sent.
Step
Test Sequence
Result
1
MS sends 1 or more DREG-REQs with Deregistration Request Code 0x01
OK
NOK
2
BS sends DREG-CMD with Action Code 0x05
OK
NOK
-
acknowledging MS-initiated Idle Mode, or
if DREG-CMD (with Action Code 0x06) requests re-transmission of
DREG-REQ with Deregistration Request ode 0x01,
then MS sends again DREG-REQ with Deregistration Request Code
0x01.
Observations
Page - 77
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.10.2 Idle Mode Verification
Test Description
Identifier:
TD_SC1h_MS_IDM_INI_00
Description:
Verify Idle Mode.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
No data is to be sent. MS is in idle mode.
Step
1
2
Test Sequence
BS must send MOB_PAG-ADVs.
during the MS Paging Listening Interval,
does not contain MS MAC address hash
After Paging listening interval, MS remains in idle mode.
Result
OK
NOK
OK
NOK
Observations
8.10.3 BS initiated PING
Test Description
Identifier:
TD_SC1h_MS_IDM_DAT_00
Description:
Verify the successful completion of Idle Mode Termination.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
No data is to be sent. MS is in idle mode. Host behind BS pings the MS or pings host behind MS
(depending on the type of the MS).
Step
Test Sequence
Result
1
BS sends MOB_PAG-ADVs
OK
NOK
2
during the MS Paging Listening Interval,
with the MSs MAC address hash.
MS performs Network Re-Entry from Idle mode.
OK
NOK
3
Data is transferred.
OK
NOK
-
Is the PING procedure successfully completed?
Observations
Page - 78
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.10.4 MS initiated Idle Mode (Re-initiation)
Test Description
Identifier:
TD_SC1h_MS_IDM_DREG_01
Description:
Verify the successful completion of MS initiated Idle Mode.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
No data is to be sent.
Step
Test Sequence
Result
1
MS sends 1 or more DREG-REQs.
OK
NOK
2
BS sends DREG-CMD
OK
NOK
-
acknowledging MS-initiated Idle Mode, or
if DREG-CMD requests re-transmission of DRERG-REQ,
then MS sends again DREG-REQ.
Observations
8.10.5 MS initiated PING
Test Description
Identifier:
TD_SC1h_MS_IDM_DAT_01
Description:
Verify the successful completion of Idle Mode Termination.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
No data is to be sent. MS is in idle mode. Host behind MS or the MS itself (depending on the type of the
MS) pings host behind BS.
Step
Test Sequence
Result
1
MS performs Network Re-Entry from Idle mode.
OK
NOK
2
Data is transferred.
OK
NOK
-
Is the PING procedure successfully completed?
Observations
8.10.6 MS initiated Idle Mode (Re-initiation)
Page - 79
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Test Description
Identifier:
TD_SC1h_MS_IDM_DREG_02
Description:
Verify the successful completion of idle mode initiation.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
No data is to be sent.
Step
Test Sequence
Result
1
MS sends 1 or more DREG-REQs.
OK
NOK
2
BS sends DREG-CMD
OK
NOK
-
acknowledging MS-initiated Idle Mode, or
if DREG-CMD requests re-transmission of DREG-REQ,
then MS sends again DREG-REQ.
Observations
8.10.7 Power Down Final Test
Test Description
Identifier:
TD_SC1h_MS_IDM_DOWN_00
Description:
Verify the successful completion of Power Down Update.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
No data is to be sent. MS is in idle mode.
Step
Test Sequence
Result
1
MS sends RNG-REQ
OK
NOK
2
with Power_Down_Indicator TLV.
BS sends RNG-RSP
OK
NOK
-
confirming the power down.
Observations
Page - 80
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.11
WMF-T25-003-R010v08
Scenario 1hb - BS initiated Idle Mode
Test scenario behaviour
Ref
Scenario 1hb- BS Initiated Idle Mode
Goal
Verify BS initiated Idle Mode.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Optional.
HARQ: Optional.
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
Pass verdict
criterion
Final Verdict
-
1)
2)
3)
4)
5)
6)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure.
Carry out 1 DL and 1 UL BS initiated BE service flow.
Trigger BS to initiate idle mode procedure. (Table 7.1 / Item 10)
Once, MS is in idle mode, host behind BS pings the MS or pings host behind MS (depending
on the type of the MS).
Successful exchange of Ping Traffic and DL/UL data transfer.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 81
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.11.1 Setup for BS initiated Idle Mode
Test Description
Identifier:
TD_SC1h_BS_IDM_REG_00
Description:
Verify the Idle Mode parameters during registration.
Pre-test
conditions:
MS is performing network entry.
Step
1
Test Sequence
MS sends 1 or more REG-REQ
OK
NOK
OK
NOK
-
2
not more than PIC_MAX_REG_REQ_RETRIES of REG-REQs
With bit#2 = 1 (Idle Mode supported) in the “Mobility features supported”
TLV.
Extended Capability: bit#3 (extended BS-initiated idle mode) equals 1 if
the MS supports action code 0x07.
BS sends REG-RSP
Result
-
3
with response set to OK.
with TLVs that are present in the REG-REQ,
and with values that do not enable a feature disabled/not supported by
MS.
With idle mode timeout TLV
Mobility feature supported: bit#1 (SLM) equals 0, bit#2 (Idle) equals 1
Extended Capability: bit#3 (extended BS-initiated idle mode) equals 1 if
the BS supports action code 0x07.
Fill the gap with the Idle Mode Timer value assigned to the MS in the REG-RSP.
Observations
Page - 82
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.11.2 BS Triggers Idle Mode
Test Description
Identifier:
TD_SC1h_BS_IDM_DREG_00
Description:
Verify the successful completion of BS initiated Idle Mode.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
No data is to be sent.
Step
1
Test Sequence
BS sends unsolicited DREG-CMD
Result
OK
NOK
OK
NOK
with action code = 0x05 or 0x07 and optional REQ-duration TLV.
Action code = 0x07 shall only be sent if Extended Capability: bit#3 the REG-RSP
meaning extended BS-initiated idle mode was equal 1.
Note: In case of action code 0x05, the BS may include the REQ-duration TLV. The
value of the REQ-duration TLV may be 0.
2
MS send DREG-REQ
- with De-Registration Request Code = 0x02 in order to start Idle Mode.
Observations
8.11.3 BS initiated PING
Test Description
Identifier:
TD_SC1h_BS_IDM_DAT_00
Description:
Verify the successful completion of Idle Mode Termination.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
No data is to be sent. MS is in idle mode. Host behind BS pings the MS or pings host behind MS
(depending on the type of the MS).
Step
Test Sequence
Result
1
BS sends MOB_PAG-ADVs
OK
NOK
2
during the MS Paging Listening Interval,
with the MSs MAC address hash.
MS performs Network Re-Entry from Idle mode.
OK
NOK
3
Data is transferred.
OK
NOK
-
Is the PING procedure successfully completed?
Observations
Page - 83
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.12
WMF-T25-003-R010v08
Scenario 1hc - Load Balancing 1
Test scenario behaviour
Ref
Scenario 1hc - Basic Configuration
Goal
Verify the frequency override mechanism.
Wave
OR1b
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
-
Initial State
Test process
TX Power Level: BS1 High, BS2 Medium.
ARQ: Optional.
HARQ: Optional.
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
SS Management: Unmanaged.
1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
Service Flows Classification Rule: Based on IP address/port number.
For this test two BS are required. BS1 uses frequency F1 and BS 2 uses a different frequency
F2.
Besides MS1, additional MS are required to block the capacity of BS1. Typical values are 2 to 3
MS.
BS1 is configured in the way that causes rejection of additional MS trying to register
Note: Means of configuration to trigger the Frequency override signal by BS1 are vendor
dependent. Possible examples:

Number of allowed MS (BS parameter)

Max total throughput allowed at the BS
The test scenario presumes that the trigger should be achievable in the lab with no more than 3
MSs.
MS1 is switched off and is deregistered from BS1 and BS2. BS1 and BS2 remain on.
1)
Start the monitor message capture, if available.
Switch on MS1.
When MS1 attempts NW entry at BS1, BS1 sends the MS to BS2 by the means of
frequency override TLV (due to sector overload).
4)
MS1 performs NW entry at BS2
5)
Carry out 1 DL and 1 UL BS initiated BE service flow.
6)
Carry out DL and UL data transfer
Successful NW entry at BS2.
2)
3)
Pass verdict
criterion
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 84
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.12.1 Network Entry procedure
8.12.1.1 MS Synchronization and Ranging
Test Description
Identifier:
TD_SC1hc_RLC_IRNG_00
Description:
Verify that BS1 and 2 send broadcast messages (DL-MAP, UL-MAP, UCD, DCD) when switched on and
that MS synchronizes with the BS. Verify the successful completion of initial ranging.
Pre-test
conditions:
MS1 is deregistered from BS 1 and BS 2. BS 1 and BS 2 have no stored context for MS1. MS1 has not
no stored context for BS 1 and BS 2. MS 1 is switched off. Then MS 1 is switched on.
Step
Test Sequence
Result
1
BS1 and BS2 send DL-MAP in every frame.
OK
NOK
2
BS1 and BS 2 send UL-MAP if appropriate.
OK
NOK
3
BS1 and BS 2 send DCD every ten seconds (max).
OK
NOK
4
BS1 and BS 2 send UCD every ten seconds (max).
OK
NOK
5
MS1 synchronizes to the BS1.
OK
NOK
6
MS1 sends initial CDMA ranging codes in the Initial Ranging Region to the BS1.
OK
NOK
7
BS1 sends
OK
NOK
8
If the BS sends a RNG-RSP message with ranging status = abort, steps 8 and 9
are skipped.
MS1 sends RNG-REQ in case of RNG-RSP with ranging status = success
OK
NOK
9
BS1 sends RNG-RSP in response to RNG-REQ sent by MS1
OK
NOK
-
RNG-RSP with DL Frequency Override TLV (frequency of BS2) and
ranging status = abort, or
RNG-RSP with ranging status = success
with DL Frequency Override TLV (frequency of BS2) and ranging status = abort,
10
MS1 synchronizes to the BS2.
OK
NOK
11
MS1 sends initial CDMA ranging codes in the Initial Ranging Region to the BS2.
OK
NOK
12
BS2 sends RNG-RSP
OK
NOK
OK
NOK
13
may include Power, Time or Frequency adjustments.
with ranging status = continue or success
If the Ranging Status = success then continue in Step 12, MS 1 sends initial
CDMA ranging code in the Periodic Ranging Region until receiving:
-
RNG-RSP (with Ranging Status = success), or
-
CDMA_Allocation_IE in UL-MAP
14
MS 1 sends RNG-REQ.
OK
NOK
15
BS 2 sends RNG-RSP with ranging status = success.
OK
NOK
16
Record the Basic Cid and Primary Management Cid assigned to the MS in the
RNG-RSP.
OK
NOK
Basic CID:
Prim CID:
Observations
Page - 85
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.12.1.2 Capabilities Negotiation
Test Description
Identifier:
TD_SC1hc_RLC_SBC_00
Description:
Verify the successful completion of basic capabilities negotiation.
Pre-test
conditions:
Successful completion of initial ranging.
Step
Test Sequence
Result
1
MS 1 sends 1 or more SBC-REQ
OK
NOK
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
with its capabilities set to on.
Are TLVs defined appropriate to the device capabilities?
BS 2 sends SBC-RSP
OK
NOK
-
With valid TLVs that are present in the SBC-REQ appropriate for the
Wave capabilities,
and with values that do not enable a feature disabled/not supported
by MS.
Observations
8.12.1.3 Registration
Test Description
Identifier:
TD_SC1hc_RLC_REG_00
Description:
Verify the successful completion of registration.
Pre-test
conditions:
Successful completion of basic capabilities negotiation. No authentication is required.
Step
Test Sequence
Result
1
MS 1 sends 1 or more REG-REQ
OK
NOK
2
not more than PIC_MAX_REG_REQ_RETRIES of REG-REQs,
including valid TLVs defined for the appropriate Wave.
BS 2 sends REG-RSP
OK
NOK
-
with response set to OK.
with valid TLVs that are present in the REG-REQ are in the appropriate
Wave,
and with values that do not enable a feature disabled/not supported by
MS.
Observations
Page - 86
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.12.2 Traffic Connection Establishment
8.12.2.1 Service Flow Provisioning
Test Description
Identifier:
TD_SC1hc_RLC_DSA_00
Description:
Verify the successful completion of service flow establishment as in TD_SC1a-B_RLC_DSA_List.
Pre-test
conditions:
Successful completion of registration and 1 DL and 1 UL Service Flows are Pre-Provisioned at the BS for
this MS and the MS can support the Pre-Provisioned Service Flows.
Step
Test Sequence
Result
1
BS 2 sends 1 or more DSA-REQ
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs.
MS 1 sends 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs.
BS 2 sends DSA-ACK
OK
NOK
-
Confirmation Code set to OK.
Observations
TD_SC1a-B_RLC_DSA_List
Nr.
Stimulate the BS to use the following parameters
Status
Run
UL DSA-REQ
1
Service Flow Scheduling Type set to BE
m
Yes/No
m
Yes/No
DL DSA-REQ
2
Service Flow Scheduling Type set to BE
Page - 87
WiMAX FORUM PROPRIETARY
Result
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.12.3 User Data Traffic
8.12.3.1 PING
Test Description
Identifier:
TD_SC1hc_RLC_DAT_00
Description:
Verify the successful completion of data transfer via the PING procedure.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number.
Step
1
Test Sequence
Host behind the BS 2 pings the host behind the MS 1.
OK
NOK
OK
NOK
-
2
The CID of the DL MAC PDU (EchoRequest) is the Transport Cid of
the DL Service Flow.
The CID of the UL MAC PDU (EchoReply) is the Transport Cid of the
UL Service Flow.
Is the PING procedure successfully completed?
Host behind the MS pings the host behind the BS 2.
Result
-
The CID of the UL MAC PDU (EchoRequest) is the Transport Cid of
the UL Service Flow.
The CID of the DL MAC PDU (EchoReply) is the Transport Cid of the
DL Service Flow.
Is the PING procedure successfully completed?
Observations
8.12.3.2 File Data Transfer
Test Description
Identifier:
TD_SC1hc_RLC_DAT_01
Description:
Verify the successful completion of file data transfer for 5 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number.
Step
Test Sequence
Result
1
Has the data from MS 1 to BS 2 been transferred correctly?
OK
NOK
2
Has the data from MS 1 to BS 2 been transferred correctly?
OK
NOK
Observations
Page - 88
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.13
WMF-T25-003-R010v08
Scenario 1i – ERT-VR
Test scenario behaviour
Ref
Scenario 1a – Basic Configuration
Goal
Checks that QoS characteristics of the ERT-VR service are not damaged by any simultaneous
transmission through a BE service flow.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Disable (Initiated by Trigger in Table 7.1 / Item 4).
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used to
specify the burst shall set ACK disable = 1 (Initiated by Trigger in Table 7.1 / Item 3)..
- Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 UL and 1 DL ERT-VR and 1 UL and 1 DL BE Service Flows are Pre-Provisioned at the BS for
this MS and the MS can support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
-
Pass verdict
criterion
1) Start the monitor message capture, if available.
2) Switch on the MS.
3) Carry out the Network Entry procedure.
4) Carry out 1 DL and 1 UL BS initiated BE service flow.
5) Carry out 1 UL and 1 DL ERT-VR (Table 7.1 / Item 11).
6) Carry out simultaneous UL data transfer.
QoS characteristics of the ERT-VR service are not damaged by any simultaneous transmission
through a BE service flow.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 89
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.13.1 Traffic Connection Establishment
8.13.1.1 Service Flow Provisioning
Test Description
Identifier:
TD_SC1i_DSA_00
Description:
Verify the successful completion of BS initiated ERT-VR service flow establishment.
Pre-test
conditions:
ERT-VR service is pre-provisioning
Step
1
Test Sequence
BS sends 1 or more DSA-REQ
Result
OK
NOK
2
with Service Flow Scheduling Type set to ertPS (UL only),
with Service Flow Data Delivery Type set to ERT-VR (DL only),
with Maximum Sustained Traffic Rate,
with Minimum Reserved Traffic Rate,
unsolicited grant interval (UL only),
with Maximum Latency,
with Request/Transmission Policy,
Tolerated Jitter,
Traffic Priority,
not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs.
MS sends 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs.
BS sends DSA-ACK to each MS
OK
NOK
-
to define 2 UL and 2 DL service flows,
Scheduling type for one UL SF is BE and is ertPS for the other UL SF.
Data Delivery Service for one DL SF is BE and is ERT-VR for the other
DL SF.
For the ERT-VR (ertPS) SF the following QoS parameters shall be set:
-
Confirmation Code set to OK.
Observations
Page - 90
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.13.2 User Data Transfer
8.13.2.1 File Data Transfer
Test Description
Identifier:
TD_SC1i_DAT_00
Description:
Verify the successful data transfer of the data delivery services ERT-VR.
Pre-test
conditions:
1 UL ERT-VR service flow established and 1 UL BE service flow established.
Step
1
Test Sequence
Are the QoS characteristics of the ERT-VR service not damaged by the
simultaneous transmission through a BE service flow?
Observations
Page - 91
WiMAX FORUM PROPRIETARY
Result
OK
NOK
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.14
WMF-T25-003-R010v08
Scenario 1j - MS initiated Handover
Test scenario behaviour
Ref
Scenario 1j- Handover
Goal
Verify MS initiated handover.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Optional.
HARQ: Optional.
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- TPC Mode: Open Loop.
- SBS & TBS Transmit on same frequency.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the SBS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
- TPC mode: Open loop.
- SBS and TBS transmit on the same frequency.
MS is deregistered from each BS. MS is switched off. BSs remains on.
Initial State
Test process
Pass verdict
criterion
Final Verdict
-
1)
2)
3)
4)
5)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure and create UL and DL service flows.
Ensure the target BS is on.
Use the DCD for BS (Table 7.1 / Item 13) and Fade the Serving BS signal in order to trigger
handover initiation or trigger directly at the MS (Table 7.1 / Item 12).
6) Carry out DL and UL data transfer with TBS
a) via the PING procedure:
Host behind the BS pings the MS or pings the host behind the MS (depending on the type of
MS)
Host behind the MS or the MS itself (depending on the type of the MS pings the host behind the
BS.
Successful handover from SBS to TBS and PING procedure with TBS.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 92
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.14.1 Neighbor Advertisement
Test Description
Identifier:
TD_SC1j_MS_GHF_ADV_00
Description:
Verify the Neighbor Advertisement and UL-MAPs of SBS and TBS.
Pre-test
conditions:
Successful completion of initial network entry and service flow establishment.
Step
1
Test Sequence
SBS and TBS send MOB_NBR-ADV.
Result
OK
NOK
Observations
8.14.2 Handover Decision
Test Description
Identifier:
TD_SC1j_MS_GHF_HOD_00
Description:
Verify the successful completion of MS initiated Handover Decision.
Pre-test
conditions:
Successful completion of initial network entry.
MS received Neighbor Advertisement from Serving BS.
Step
1
Test Sequence
When trigger condition are met MS sends 1 or more MOB_MSHO-REQ to SBS
Result
OK
NOK
2
BS sends MOB_BSHO-RSP
OK
NOK
3
MS optionally sends MOB_HO-IND to serving BS
OK
NOK
- with final indication that it is about to perform a HO.
Observations
Page - 93
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.14.3 Handover Initiation
Test Description
Identifier:
TD_SC1j_MS_GHF_NWE_00
Description:
Verify the successful completion of Handover Initiation from serving BS to target BS.
Pre-test
conditions:
MS has decided to handover from serving BS to target BS.
Step
Test Sequence
Result
1
MS optionally sends MOB_HO-IND to serving BS
OK
NOK
2
with final indication that it is about to perform a HO.
MS sends Handover CDMA ranging codes in the Initial Ranging Interval to the
target BS or uses Fast Ranging IE.
OK
NOK
3
MS finishes Network Entry with TBS and the BS updates the CIDs.
OK
NOK
Observations
Page - 94
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.14.4 Handover Verification
Test Description
Identifier:
TD_SC1j_MS_GHF_DAT_00
Description:
Verify the successful completion of data transfer via the PING procedure.
Pre-test
conditions:
Handover completes at TBS.
Step
1
Test Sequence
Host behind the BS pings the MS or pings the host behind the MS (depending
on the type of the MS).
OK
NOK
OK
NOK
-
2
The CID of the DL MAC PDU (EchoRequest) is the Transport Cid of
the DL Service Flow.
The CID of the UL MAC PDU (EchoReply) is the Transport Cid of the
UL Service Flow.
Is the PING procedure successfully completed?
Host behind the MS or the MS itself (depending on the type of the MS pings the
host behind the BS.
Result
-
The CID of the UL MAC PDU (EchoRequest) is the Transport Cid of
the UL Service Flow.
The CID of the DL MAC PDU (EchoReply) is the Transport Cid of the
DL Service Flow.
Is the PING procedure successfully completed?
Observations
Page - 95
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.15
WMF-T25-003-R010v08
Scenario 2 - P2MP Configuration
Test scenario behaviour
Ref
Scenario 2 – P2MP Configuration
Goal
Verify the exchange of Ping Traffic and data transfer in a P2MP configuration.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Optional
HARQ: Optional
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for all MSs and each MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MSs are switched on. BS remains on.
Initial State
Test process
Pass verdict
criterion
Final Verdict
-
1)
2)
3)
4)
5)
Start the monitor message capture, if available.
Switch on the MSs.
Carry out the Network Entry procedure for each MS simultaneously.
Carry out 1 DL and 1 UL BS initiated BE service flow for each MS simultaneously.
Carry out DL and UL data transfer for each MS simultaneously
a) via the PING procedure
Host behind the BS pings the MS or pings the host behind the MS (depending on the type of
MS)
Host behind the MS or the MS itself (depending on the type of the MS pings the host behind the
BS
b) via freestyle Best Effort (such as FTP) data transfer (5 minute transfer for some stability
evaluation).
Successful exchange of Ping Traffic and DL/UL data transfer in a P2MP configuration.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
8.15.1 Network Entry procedure
8.15.1.1 Ranging
Test Description
Identifier:
TD_SC2_RLC_IRNG_00
Description:
Verify that a BS sends broadcast messages (DL-MAP, UL-MAP, UCD, DCD) when switched on and
that all MSs synchronize with the BS. Verify the successful completion of initial ranging.
Pre-test
conditions:
BS and all MSs are switched off. BS is configured to transmit in the lowest channel (fL). Then BS and all
MSs are switched on.
Step
Test Sequence
Result
1
BS sends DL-MAP in every frame.
OK
NOK
2
BS sends UL-MAP if appropriate.
OK
NOK
3
BS sends DCD every ten second(max).
OK
NOK
4
BS sends UCD every ten second(max).
OK
NOK
Page - 96
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
For each MS the following applies
5
MS synchronizes to the BS.
OK
NOK
6
MS sends initial CDMA ranging codes in the Initial Ranging Region.
OK
NOK
7
BS sends RNG-RSP
OK
NOK
OK
NOK
OK
NOK
10
RNG-RSP (with Ranging Status = success) followed by
CDMA_Allocation_IE,
or CDMA_Allocation_IE only.
MS sends RNG-REQ.
OK
NOK
11
BS sends RNG-RSP with ranging status = success
OK
NOK
12
Fill the table below with the MSs MAC address read in the corresponding RNGREQ and determine MAC Address.
OK
NOK
13
Fill the table below with the Basic Cid and Primary Management Cid assigned
to the MS in the corresponding RNG-RSP.
OK
NOK
8
9
With optional Power, Time or Frequency adjustments.
With ranging status = continue or success
If the Ranging Status = continue in Step 7, MS sends initial CDMA ranging
code in the Periodic Ranging Region until receiving:
RNG-RSP (with Ranging Status = success),
or CDMA_Allocation_IE in UL-MAP.
BS sends
-
Observations
TD_SC2_RLC_IRNG_00_List
Nr.
1
Parameters
MS1
MS2
MAC Address
Basic CID
Primary CID
Page - 97
WiMAX FORUM PROPRIETARY
MS3
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.15.1.2 Capabilities Negotiation
Test Description
Identifier:
TD_SC2_RLC_SBC_00
Description:
Verify the successful completion basic capabilities negotiation.
Pre-test
conditions:
Successful completion of initial ranging.
Step
Test Sequence
Result
1
Each MSs sends 1 or more SBC-REQ
OK
NOK
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
with capabilities set to on.
Are TLVs defined appropriate to the device capabilities?
BS sends SBC-RSP to each MS
OK
NOK
-
With valid TLVs that are present in the SBC-REQ appropriate for the
Wave capabilities,
and with values that do not enable a feature disabled/not supported by
MS.
Observations
8.15.1.3 Registration
Test Description
Identifier:
TD_SC2_RLC_REG_00
Description:
Verify the successful completion of registration.
Pre-test
conditions:
Successful completion of basic capabilities negotiation. No authentication is required.
Step
Test Sequence
Result
1
Each MS sends 1 or more REG-REQ
OK
NOK
2
not more than PIC_MAX_REG_REQ_RETRIES of REG-REQs,
including valid TLVs defined for the appropriate Wave.
BS sends REG-RSP to each MS
OK
NOK
-
with response set to OK.
with valid TLVs that are present in the REG-REQ are in the appropriate
Wave,
and with values that do not enable a feature disabled/not supported by
MS.
Observations
Page - 98
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.15.2 Traffic Connection Establishment
8.15.2.1 Service Flow Provisioning
Test Description
Identifier:
TD_SC2_RLC_DSA_00
Description:
Verify the successful completion of service flow establishment as in TD_SC2_RLC_DSA_List
Pre-test
conditions:
Successful completion of registration and 1 DL and 1 UL Service Flows are Pre-Provisioned at the BS for
all three MS and each MS can support the Pre-Provisioned Service Flows.
Step
Test Sequence
Result
1
BS sends 1 or more DSA-REQ to each MS
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs.
MSs send 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs.
BS sends DSA-ACK to each MS
OK
NOK
-
Confirmation Code set to OK.
Observations
TD_SC2_RLC_DSA_List
Nr.
Stimulate the BS to use the following parameters
Status
Run
UL DSA-REQ
1
Service Flow Scheduling Type set to BE
m
Yes/No
m
Yes/No
DL DSA-REQ
2
Service Flow Scheduling Type set to BE
Page - 99
WiMAX FORUM PROPRIETARY
Result
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.15.3 User Data Transfer
8.15.3.1 PING
Test Description
Identifier:
TD_SC2_RLC_DAT_00
Description:
Verify the successful completion of data transfer via the PING procedure to three MS.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number.
Step
1
Test Sequence
Host behind the BS pings the MS or pings the host behind MS (depending on
the type of the MS).
OK
NOK
OK
NOK
-
2
The CID of the DL MAC PDU (EchoRequest) is the Transport Cid of
the DL Service Flow.
The CID of the UL MAC PDU (EchoReply) is the Transport Cid of the
UL Service Flow.
The Host behind MS or the MS itself (depending on the type of the MS) pings
the host behind the BS.
Result
-
The CID of the UL MAC PDU (EchoRequest) is the Transport Cid of
the UL Service Flow.
The CID of the DL MAC PDU (EchoReply) is the Transport Cid of the
DL Service Flow.
Observations
8.15.3.2 File Data Transfer
Test Description
Identifier:
TD_SC2_RLC_DAT_01
Description:
Verify the successful completion of file data transfer for 5 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
Test Sequence
Result
1
Has the data from MS1, MS2 and MS3 to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to MS1, MS2 and MS3 been transferred correctly?
OK
NOK
Observations
Page - 100
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.16
WMF-T25-003-R010v08
Scenario 2A0 – DL PUSC with MIMO Matrix A and UL PUSC with
Collaborative SM
Test scenario behaviour
Ref
11.8.3.7.5, 11.8.3.7.6 [1]
Goal
Verify DL and UL data transfer between BS and 2 MS when DL PUSC with Matrix A MIMO and UL
PUSC with Collaborative SM is activated.
Configuration
Basic Test Configuration for IOT Testing - 2 MS+ 1 BS
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
DL 2-antenna STC matrix A: Enable in MS and BS.
DL 2-antenna STC matrix B: disable in BS (Table 7.1 / Item 29)
DL zone type. PUSC.
UL Single-antenna Collaborative SM: Enable.
UL zone type. PUSC.
CQI Channel for physical CINR Feedback: Enable.
ARQ: Disable.
HARQ: Optional (The following two sub-bullets apply to the case that HARQ is disabled.)
- HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used
to specify the burst shall set ACK disable = 1.
Any non- HARQ DL/UL connection is established by including HARQ Service Flows field
(TLV Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows
field (which means default value ‘non-HARQ’).
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for all MSs and each MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MSs are switched off. BS remains on.
Initial State
Test process
Pass verdict
criteria
Final Verdict
-
1)
2)
3)
4)
5)
6)
Start the monitor message capture, if available.
Switch on the MSs.
Carry out the Network Entry procedure for each MS simultaneously.
Carry out 1 DL and 1 UL BS initiated BE service flow for each MS simultaneously.
BS allocates Fast feedback channel for each MS. (Table 7.1 / item 2).
Carry out for each MS simultaneously:
DL data transfer with 2-antenna STC matrix A,
and UL data transfer with Single-antenna Collaborative SM,
via freestyle BE (such as FTP) data transfer (5 minute transfer for some stability evaluation).
Successful data transfer in UL and DL.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
8.16.1 Network Entry procedure
8.16.1.1 Capabilities Negotiation
Test Description
Identifier:
TD_SC2A0_MIMO_SBC_00
Description:
Verify the successful completion of basic capabilities negotiation with Matrix A MIMO and
Collaborative SM support.
Pre-test
conditions:
Successful completion of initial ranging.
Page - 101
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Step
Test Sequence
Result
1
MS sends 1 or more SBC-REQ
OK
NOK
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs,
SS Demodulator for MIMO support TLV: 2-Antenna STC Matrix A,
SS Modulator for MIMO support TLV:
Capable of single antenna transmission, Capable of collaborative SM
with one antenna.
Are TLVs defined appropriate to the required device capabilities?
BS sends SBC-RSP
OK
NOK
-
-
With valid TLVs that are present in the SBC-REQ appropriate for the
Wave capabilities,
and with values that do not enable a feature disabled/not supported
by MS.
Observations
8.16.2 User Data Transfer
8.16.2.1 MAP
Test Description
Identifier:
TD_SC2A0_MIMO_DAT_00
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes, with UL data transfer at the
same time for MS1 and MS2 to test collaborative SM functionality.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
1
Test Sequence
BS sends UL-MAP or compressed UL-MAP with
Result
OK
NOK
MIMO UL Basic IE
or HARQ_UL_MAP_IE()+ UL HARQ Chase Sub-Burst IE() with ACK
Disable = 1 or 0..
or HARQ_UL_MAP_IE()+ MIMO UL Chase HARQ Sub-Burst IE() with ACK
Disable = 1 or 0..
2
BS sends DL-MAP or compressed DL-MAP with
OK
NOK
3
STC_DL_ZONE_IE()
DL_MAP_IE() or MIMO DL Basic IE or HARQ_DL_MAP_IE()+ MIMO
DL Chase HARQ Sub-Burst IE() with ACK Disable = 1 or 0..
BS sends UL-MAP, compressed UL-MAP or UCD to each MS with
OK
NOK
4
Fast Feedback Allocation IE or fast-feedback region TLV.
CQICH Allocation IE, allocating the fast-feedback slots.
BS sends UCD to each MS with
OK
NOK
5
Size of the CQICH_ID field. In case of default value, the BS doesn’t
need to send the size of the CQICH_ID field.
MS sends physical CINR report as indicated in the CQICH Allocation IE.
OK
NOK
-
-
Observations
Page - 102
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.16.2.2 Data grants for the MS
Test Description
Identifier:
TD_SC2A0_MIMO_DAT_01
Description:
Verify the generation of data grants for the MS in the UL/DL PUSC zone.
Pre-test
conditions:
Successful network entry.
Step
Test Sequence
Result
1
Are MAP message sent in the DL PUSC zone?
OK
NOK
2
Has the BS sent DL data for each MS in the appropriate DL PUSC zone?
OK
NOK
3
Has the BS generated UL grants for each MS in the appropriate UL PUSC
zone?
OK
NOK
Observations
8.16.2.3 Data Transfer
Test Description
Identifier:
TD_SC2A0_MIMO_DAT_02
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes, with UL data transfer at the
same time for MS1 and MS2 to test collaborative SM functionality.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
Test Sequence
Result
1
Has the data from each MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to each MS been transferred correctly?
OK
NOK
Observations
Page - 103
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.17
WMF-T25-003-R010v08
Scenario 2A1 – DL PUSC with MIMO Matrix B and UL PUSC With
Collaborative SM
Test scenario behaviour
Ref
11.8.3.7.5, 11.8.3.7.6 [1]
Goal
Verify DL and UL data transfer between BS and 2 MS when DL PUSC with Matrix B MIMO and UL
PUSC With Collaborative SM is activated.
Configuration
Basic Test Configuration for IOT Testing - 2 MS+ 1 BS
Test
Condition
Initial State
Frequency channel: Middle.
TX Power Level: Medium.
DL 2-antenna STC matrix A: Enable in MS and BS.
DL 2-antenna STC matrix B: Enable in MS and BS.
DL zone type. PUSC.
UL Single-antenna Collaborative SM: Enable.
UL zone type. PUSC.
CQI Channel for physical CINR Feedback: Enable.
ARQ: Disable.
HARQ: Enable.
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for all MSs and each MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MSs are switched off. BS remains on.
Test process
1) Start the monitor message capture, if available.
-
2) Switch on the MSs.
3) Carry out the Network Entry procedure for each MS simultaneously.
4) Carry out 1 DL and 1 UL BS initiated BE service flow for each MS simultaneously.
5) BS allocates Fast feedback channel for each MS. (Table 7.1 / Item 2).
6) If the field value of ‘MIMO_permutation_feedback_cycle’ in the CQICH allocation IE() is set for
MIMO mode selection by the BS, the MS shall provide MIMO Mode selection via fast-feedback
special codeword.
7) Carry out for each MS simultaneously:
8) DL data transfer with 2-antenna STC matrix B,
and UL data transfer with Single-antenna Collaborative SM,
via freestyle BE (such as FTP) data transfer (5 minute transfer for some stability evaluation).
Pass verdict
criteria
Successful data transfer in UL and DL.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 104
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.17.1 Network Entry procedure
8.17.1.1 Capabilities Negotiation
Test Description
Identifier:
TD_SC2A1_MIMO_SBC_00
Description:
Verify the successful completion of basic capabilities negotiation with Matrix B MIMO and
Collaborative SM support.
Pre-test
conditions:
Successful completion of initial ranging.
Step
Test Sequence
Result
1
MS sends 1 or more SBC-REQ
OK
NOK
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs,
SS Demodulator for MIMO support TLV: 2-Antenna STC Matrix B,
SS Modulator for MIMO support TLV:
Capable of single antenna transmission,
Capable of collaborative SM with one antenna,
Are TLVs defined appropriate to the required device capabilities?
BS sends SBC-RSP
OK
NOK
-
-
With valid TLVs that are present in the SBC-REQ appropriate for the
Wave capabilities,
and with values that do not enable a feature disabled/not supported
by MS.
Observations
Page - 105
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.17.2 User Data Transfer
8.17.2.1 MAP
Test Description
Identifier:
TD_SC2A1_MIMO_DAT_00
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes, with UL data transfer at the
same time for MS1 and MS2 to test collaborative SM functionality.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established. If MIMO mode selection feedback is enabled by the BS, the
MS is expected to select MIMO Matrix B. If MIMO mode selection feedback is not enabled by the BS, the
BS is expected to select MIMO Matrix B. The MS or BS is expected to select MIMO Matrix B, if MIMO
mode selection was enabled by the BS, without a special test trigger since the MS and BS will be in
optimal RF conditions for MIMO matrix B (strong signal conditions with separate cable between each BS
transmitter and MS receiver).
Step
1
Test Sequence
BS sends UL-MAP or compressed UL-MAP with
-
Result
OK
NOK
HARQ_UL_MAP_IE()+ UL HARQ Chase Sub-Burst IE()
or HARQ_UL_MAP_IE()+ MIMO UL Chase HARQ Sub-Burst IE()
2
BS sends DL-MAP or compressed DL-MAP with
OK
NOK
3
STC_DL_ZONE_IE()
HARQ_DL_MAP_IE()+ MIMO DL Chase HARQ Sub-Burst IE()
BS sends UL-MAP, compressed UL-MAP or UCD to each MS with
OK
NOK
4
CQICHAllocation IE or fast-feedback region TLV.
CQICH Allocation IE, allocating the fast-feedback slots, with MIMO
mode selection, if MIMO mode selection was enabled by the BS.
BS sends UCD to each MS with
OK
NOK
5
Size of the CQICH_ID field. In case of default value, the BS doesn’t
need to send the size of the CQICH_ID field.
MS sends physical CINR report as indicated in the CQICH Allocation IE.
OK
NOK
OK
NOK
-
-
6
MS sends special CQICH code to indicate preference for MIMO Matrix B if
MIMO mode selection was enabled by the BS
Observations
Page - 106
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.17.2.2 Data grants for the MS
Test Description
Identifier:
TD_SC2A1_MIMO_DAT_01
Description:
Verify the generation of data grants for the MS in the UL/DL PUSC zone. Note that UL collaborative SM
does not occur if a frame only has an UL allocation for a single MS.
Pre-test
conditions:
Successful network entry.
Step
Test Sequence
Result
1
Are MAP message sent in the DL PUSC zone?
OK
NOK
2
Has the BS sent DL data for each MS in the appropriate DL PUSC zone?
OK
NOK
3
Has the BS generated UL grants for each MS in the appropriate UL PUSC
zone?
OK
NOK
Observations
8.17.2.3 Data Transfer
Test Description
Identifier:
TD_SC2A1_MIMO_DAT_02
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes, with UL data transfer at the
same time for MS1 and MS2 to test collaborative SM functionality.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
Test Sequence
Result
1
Has the data from each MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to each MS been transferred correctly?
OK
NOK
Observations
Page - 107
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.18
WMF-T25-003-R010v08
Scenario 2B0 – Beam Forming with DL AMC with Dedicated Pilots and UL
AMC
Test scenario behaviour
Ref
11.8.3.7.16 [1]
Goal
Verify DL and UL data transfer when Beam Forming with UL AMC and DL AMC with Dedicated
Pilots is activated.
Configuration
Basic Test Configuration for IOT Testing - 1 MS+ 1 BS
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
Beam Forming: Enable.
UL zone type: AMC2x3 zone.
DL zone type: AMC2x3 zone.
Dedicated pilots in AMC2x3 zone: Enable.
CQI Channel for physical CINR Feedback: Enable.
ARQ: Disable.
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used to
specify the burst shall set ACK disable = 1.
- Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’.
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows (BS shall send DSA-REQ to the MS to establish the
Service Flow and BS may activate the Service Flow using DSC-REQ request).
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
Pass verdict
criteria
Final Verdict
-
1)
2)
3)
4)
5)
6)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure.
Carry out 1 DL and 1 UL BS initiated BE service flow.
BS allocates Fast feedback channel for MS. (Table 7.1 / item 2).
Carry out DL and UL data transfer in the AMC zone and Beam Forming is activated,
via freestyle BE (such as FTP) data transfer (5 minute transfer for some stability evaluation).
Successful data transfer in UL and DL.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 108
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.18.1 Network Entry procedure
8.18.1.1 Capabilities Negotiation
Test Description
Identifier:
TD_SC2BO_BF_SBC_00
Description:
Verify the successful completion of basic capabilities negotiation with AMC zone and Beam Forming
supported.
Pre-test
conditions:
Successful completion of initial ranging.
Step
Test Sequence
Result
1
MS sends 1 or more SBC-REQ
OK
NOK
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs,
SS Modulator for MIMO support TLV:
Capable of single antenna transmission,
OFDMA SS Permutation support: AMC 2x3 support,
OFDMA SS demodulator: Dedicated pilots with AMC without MIMO
Are TLVs defined appropriate to the required device capabilities?
BS sends SBC-RSP
OK
NOK
-
-
With valid TLVs that are present in the SBC-REQ,
and with values that do not enable a feature disabled/not supported
by MS.
Observations
Page - 109
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.18.2 User Data Transfer
8.18.2.1 MAP
Test Description
Identifier:
TD_SC2BO_BF_DAT_00
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
Test Sequence
Result
1
BS sends UL-MAP or compressed UL-MAP to the MS with
OK
NOK
1
OFDMA uplink ZONE IE format,
PAPR reduction/Safety zone/Sounding zone allocation IE(),
UL_Sounding_Command_IE()
HARQ_UL_MAP_IE()+ UL HARQ Chase Sub-Burst IE() with ACK
Disable = 1 or direct UL allocation to UIUC1 to 10
BS sends DL-MAP or compressed DL-MAP to the MS with
OK
NOK
2
OFDMA downlink STC_DL_Zone IE format indicating dedicated pilots,
HARQ_DL_MAP_IE()+ DL HARQ Chase Sub-Burst IE() with ACK
Disable = 1
BS sends UL-MAP, compressed UL-MAP, or UCD to the MS with
OK
NOK
3
Fast Feedback Allocation IE orfast-feedback region TLV.
CQICH Allocation IE, allocating the fast-feedback slots.
BS sends UCD to the MS with
OK
NOK
4
Size of the CQICH_ID field. In case of default value, the BS doesn’t
need to send the size of the CQICH_ID field.
MS sends physical CINR report as indicated in the CQICH Allocation IE.
OK
NOK
-
-
-
Observations
8.18.2.2 Data grants for the MS
Test Description
Identifier:
TD_SC2BO_BF_DAT_01
Description:
Verify the generation of data grants for the MS in the UL/DL AMC zone.
Pre-test
conditions:
Successful network entry.
Step
Test Sequence
Result
1
Are MAP message sent in the DL PUSC zone?
OK
NOK
2
Has the BS sent DL data for the MS in the appropriate DL AMC zone?
OK
NOK
3
Has the BS generated UL grants for each MS in the appropriate UL AMC zone?
OK
NOK
Observations
Page - 110
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.18.2.3 Data Transfer
Test Description
Identifier:
TD_SC2BO_BF_DAT_02
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
Test Sequence
Result
1
Has the data from the MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to the MS been transferred correctly?
OK
NOK
Observations
Page - 111
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.19
WMF-T25-003-R010v08
Scenario 2B1 – Beam Forming with DL PUSC with Dedicated Pilots and UL
PUSC without channel rotation
Test scenario behaviour
Ref
11.8.3.7.16 [1]
Goal
Verify DL and UL data transfer when Beam Forming with UL PUSC without channel rotation and DL
PUSC with dedicated Pilots is activated.
Configuration
Basic Test Configuration for IOT Testing - 1 MS+ 1 BS
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
Beam Forming: Enable.
UL zone type: PUSC zone without channel rotation.
DL zone type: PUSC zone.
Sounding :
If BS demands IO-SND certification, there must be a sounding symbol in UL.
If BS does not demand IO-SND certification, there will not be sounding in UL.
- Dedicated pilots in PUSC zone: Enable.
- CQI Channel for physical CINR Feedback: Enable.
- ARQ: Disable.
- HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used to
specify the burst shall set ACK disable = 1.
- Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’.
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
Pass verdict
criteria
Final Verdict
-
1)
2)
3)
4)
5)
6)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure.
Carry out 1 DL and 1 UL BS initiated BE service flow.
BS allocates Fast feedback channel for MS. (Table 7.1 / item 2).
Carry out DL and UL data transfer in the PUSC zone and Beam Forming is activated,
via freestyle BE (such as FTP) data transfer (5 minute transfer for some stability evaluation).
Successful data transfer in UL and DL.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 112
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.19.1 Network Entry procedure
8.19.1.1 Capabilities Negotiation
Test Description
Identifier:
TD_SC2B1_BF_SBC_00
Description:
Verify the successful completion of basic capabilities negotiation with PUSC zone without channel
rotation and Beam Forming supported.
Pre-test
conditions:
Successful completion of initial ranging.
Step
Test Sequence
Result
1
MS sends 1 or more SBC-REQ
OK
NOK
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs,
SS Modulator for MIMO support TLV:
Capable of single antenna transmission,
OFDMA SS demodulator: Dedicated pilots for PUSC with or without
MIMO,
Are TLVs defined appropriate to the required device capabilities?
BS sends SBC-RSP
OK
NOK
-
-
With valid TLVs that are present in the SBC-REQ,
and with values that do not enable a feature disabled/not supported
by MS.
Observations
Page - 113
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.19.2 User Data Transfer
8.19.2.1 MAP
Test Description
Identifier:
TD_SC2B1_BF_DAT_00
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
1
Test Sequence
BS sends UL-MAP or compressed UL-MAP to the MS with
Result
OK
NOK
1
OFDMA uplink ZONE IE format
HARQ_UL_MAP_IE()+ UL HARQ Chase Sub-Burst IE() with ACK
Disable = 1 or direct UL allocation to UIUC1 to 10.
BS sends DL-MAP or compressed DL-MAP to the MS with
OK
NOK
2
OFDMA downlink STC_DL_Zone IE format indicating dedicated pilots
HARQ_DL_MAP_IE()+ DL HARQ Chase Sub-Burst IE() with ACK
Disable = 1,
BS sends UL-MAP, compressed UL-MAP, or UCD to the MS with
OK
NOK
3
Fast Feedback Allocation IE or fast-feedback region TLV.
CQICH Allocation IE, allocating the fast-feedback slots.
BS sends UCD to the MS with
OK
NOK
4
Size of the CQICH_ID field. In case of default value, the BS doesn’t
need to send the size of the CQICH_ID field.
MS sends physical CINR report as indicated in the CQICH Allocation IE.
OK
NOK
If BS demands IO-SND certification,
-
PAPR reduction/Safety zone/Sounding zone allocation IE(),
UL_Sounding_Command_IE()
For all BSs,
-
-
-
Observations
Page - 114
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.19.2.2 Data grants for the MS
Test Description
Identifier:
TD_SC2B1_BF_DAT_01
Description:
Verify the generation of data grants for the MS in the UL/DL PUSC zone.
Pre-test
conditions:
Successful network entry.
Step
Test Sequence
Result
1
Are MAP message sent in the DL PUSC zone?
OK
NOK
2
Has the BS sent DL data for the MS in the appropriate DL PUSC zone?
OK
NOK
3
Has the BS generated UL grants for each MS in the appropriate UL PUSC
zone?
OK
NOK
Observations
8.19.2.3 Data Transfer
Test Description
Identifier:
TD_SC2B1_BF_DAT_02
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
Test Sequence
Result
1
Has the data from the MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to the MS been transferred correctly?
OK
NOK
Observations
Page - 115
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.20
WMF-T25-003-R010v08
Scenario 2AB0 – DL PUSC with dedicated pilot with MIMO Matrix A and UL
PUSC with Collaborative SM
Test scenario behaviour
Ref
11.8.3.7.5, 11.8.3.7.6 [1]
Goal
Verify DL and UL data transfer between BS and 2 MS when DL PUSC with dedicated pilot with
Matrix A MIMO and UL PUSC with Collaborative SM is activated.
Configuration
Basic Test Configuration for IOT Testing - 2 MS+ 1 BS
Test
Condition
-
-
-
Frequency channel: Middle.
TX Power Level: Medium.
DL 2-antenna STC matrix A: Enable.
DL zone type. PUSC.
Dedicated pilots in PUSC zone: Enable.
UL Single-antenna Collaborative SM: Enable.
UL zone type. PUSC.
Sounding :
If BS demands IO-SND certification, there must be a sounding symbol in UL.
If BS does not demand IO-SND certification, there will not be sounding in UL.
CQI Channel for physical CINR Feedback: Enable.
ARQ: Disable.
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used
to specify the burst shall set ACK disable = 1.
Any non- HARQ DL/UL connection is established by including HARQ Service Flows field
(TLV Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows
field (which means default value ‘non-HARQ’.
Authentication: Optional. If authentication is used, the method shall be one of those specified
in NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
SS Management: Unmanaged.
1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for all MSs and each MS can
support the Pre-Provisioned Service Flows.
Service Flows Classification Rule: Based on IP address/port number.
Initial State
MS is deregistered from BS. MSs are switched off. BS remains on.
Test process
1)
2)
3)
4)
5)
6)
Pass verdict
criteria
Final Verdict
Start the monitor message capture, if available.
Switch on the MSs.
Carry out the Network Entry procedure for each MS simultaneously.
Carry out 1 DL and 1 UL BS initiated BE service flow for each MS simultaneously.
BS allocates Fast feedback channel for each MS. (Table 7.1 / item 2).
Carry out for each MS simultaneously:
DL data transfer with 2-antenna STC matrix A and dedicated pilot,
and UL data transfer with Single-antenna Collaborative SM,
via freestyle BE (such as FTP) data transfer (5 minute transfer for some stability evaluation).
Successful data transfer in UL and DL.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 116
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.20.1 Network Entry procedure
8.20.1.1 Capabilities Negotiation
Test Description
Identifier:
TD_SC2AB0_MIMO_SBC_00
Description:
Verify the successful completion of basic capabilities negotiation with Matrix A MIMO and
Collaborative SM support.
Pre-test
conditions:
Successful completion of initial ranging.
Step
Test Sequence
Result
1
MS sends 1 or more SBC-REQ
OK
NOK
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs
SS Demodulator for MIMO support TLV: 2-Antenna STC Matrix A,
SS Modulator for MIMO support TLV:
Capable of single antenna transmission,
Capable of collaborative SM with one antenna,
OFDMA SS demodulator:
o Dedicated pilots for PUSC with or without MIMO
o and if required rectangular combination of allocations for
DL MIMO zone with dedicated pilots (default is no restriction
to rectangular combination)
Are TLVs defined appropriate to the required device capabilities?
BS sends SBC-RSP
OK
NOK
-
With valid TLVs that are present in the SBC-REQ,
and with values that do not enable a feature disabled/not supported
by MS.
Note: If the MS sets the OFDMA SS demodulator TLV bits 10 and 11 to 1, then
a BS may respond with the bits 10 and 11 set to 0.
-
Observations
Page - 117
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.20.2 User Data Transfer
8.20.2.1 MAP
Test Description
Identifier:
TD_SC2AB0_MIMO_DAT_00
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes, with UL data transfer at the
same time for MS1 and MS2 to test collaborative SM functionality.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
1
Test Sequence
BS sends UL-MAP or compressed UL-MAP to each MS with
Result
OK
NOK
OK
NOK
If BS demands IO-SND certification,
-
PAPR reduction/Safety zone/Sounding zone allocation IE(),
UL_Sounding_Command_IE()
For all BS,
MIMO UL Basic IE or HARQ_UL_MAP_IE()+ UL HARQ Chase SubBurst IE() with ACK Disable = 1
OFDMA uplink ZONE IE format
BS sends DL-MAP or compressed DL-MAP to each MS with
-
2
MIMO DL Basic IE or HARQ_DL_MAP_IE()+ MIMO DL Chase HARQ SubBurst IE() with ACK Disable = 1
OFDMA downlink STC_DL_Zone IE format indicating dedicated pilots,
3
BS sends UL-MAP, compressed UL-MAP, or UCD to each MS with
OK
NOK
4
Fast Feedback Allocation IE or fast-feedback region TLV.
CQICH Allocation IE, allocating the fast-feedback slots.
BS sends UCD to each MS with
OK
NOK
5
Size of the CQICH_ID field. In case of default value, the BS doesn’t
need to send the size of the CQICH_ID field.
MS sends physical CINR report as indicated in the CQICH Allocation IE.
OK
NOK
-
Observations
Page - 118
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.20.2.2 Data grants for the MS
Test Description
Identifier:
TD_SC2AB0_MIMO_DAT_01
Description:
Verify the generation of data grants for the MS in the UL/DL PUSC zone.
Pre-test
conditions:
Successful network entry.
Step
Test Sequence
Result
1
Are MAP message sent in the DL PUSC zone?
OK
NOK
2
Has the BS sent DL data for each MS in the appropriate DL PUSC zone?
OK
NOK
3
Has the BS generated UL grants for each MS in the appropriate UL PUSC
zone?
OK
NOK
Observations
8.20.2.3 Data Transfer
Test Description
Identifier:
TD_SC2AB0_MIMO_DAT_02
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes, with UL data transfer at the
same time for MS1 and MS2 to test collaborative SM functionality.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
Test Sequence
Result
1
Has the data from each MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to each MS been transferred correctly?
OK
NOK
Observations
Page - 119
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.21
WMF-T25-003-R010v08
Scenario 2AB1 – DL PUSC with dedicated pilot with Matrix B MIMO and UL
PUSC with Collaborative SM
Test scenario behaviour
Ref
11.8.3.7.5, 11.8.3.7.6 [1]
Goal
Verify DL and UL data transfer between BS and 2 MS when DL PUSC with dedicated pilot with
Matrix B MIMO and UL PUSC with Collaborative SM is activated.
Configuration
Basic Test Configuration for IOT Testing - 2 MS+ 1 BS
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
DL 2-antenna STC matrix B: Enable.
DL zone type. PUSC.
Dedicated pilots in PUSC zone: Enable.
UL Single-antenna Collaborative SM: Enable.
UL zone type. PUSC.
Sounding :
If BS demands IO-SND certification, there must be a sounding symbol in UL.
If BS does not demand IO-SND certification, there will not be sounding in UL.
- CQI Channel for physical CINR Feedback: Enable.
- ARQ: Disable.
- HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used to
specify the burst shall set ACK disable = 1.
- Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’.
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for all MSs and each MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MSs are switched off. BS remains on.
Initial State
Test process
Pass verdict
criteria
Final Verdict
-
1)
2)
3)
4)
5)
6)
Start the monitor message capture, if available.
Switch on the MSs.
Carry out the Network Entry procedure for each MS simultaneously.
Carry out 1 DL and 1 UL BS initiated BE service flow for each MS simultaneously.
BS allocates Fast feedback channel for each MS. (Table 7.1 / item 2).
Carry out for each MS simultaneously:
DL data transfer with 2-antenna STC matrix B and dedicated pilot,
and UL data transfer with Single-antenna Collaborative SM,
via freestyle BE (such as FTP) data transfer (5 minute transfer for some stability evaluation).
Successful data transfer in UL and DL.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 120
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.21.1 Network Entry procedure
8.21.1.1 Capabilities Negotiation
Test Description
Identifier:
TD_SC2AB1_MIMO_SBC_00
Description:
Verify the successful completion of basic capabilities negotiation with Matrix B MIMO and
Collaborative SM support.
Pre-test
conditions:
Successful completion of initial ranging.
Step
Test Sequence
Result
1
MS sends 1 or more SBC-REQ
OK
NOK
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs
SS Demodulator for MIMO support TLV: 2-Antenna STC Matrix B,
SS Modulator for MIMO support TLV:
Capable of single antenna transmission,
Capable of collaborative SM with one antenna,
OFDMA SS demodulator:
o Dedicated pilots for PUSC with or without MIMO
o and if required rectangular combination of allocations for
DL MIMO zone with dedicated pilots (default is no restriction
to rectangular combination)
Are TLVs defined appropriate to the required device capabilities?
BS sends SBC-RSP
OK
NOK
-
With valid TLVs that are present in the SBC-REQ,
and with values that do not enable a feature disabled/not supported
by MS.
Note: If the MS sets the OFDMA SS demodulator TLV bits 10 and 11 to 1, then
a BS may respond with the bits 10 and 11 set to 0.
-
Observations
Page - 121
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.21.2 User Data Transfer
8.21.2.1 MAP
Test Description
Identifier:
TD_SC2AB1_MIMO_DAT_00
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes, with UL data transfer at the
same time for MS1 and MS2 to test collaborative SM functionality.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
1
Test Sequence
BS sends UL-MAP or compressed UL-MAP to each MS with
Result
OK
NOK
2
MIMO UL Basic IE or HARQ_UL_MAP_IE()+ UL HARQ Chase SubBurst IE() with ACK Disable = 1
OFDMA uplink ZONE IE format
BS sends DL-MAP or compressed DL-MAP to each MS with
OK
NOK
3
MIMO DL Basic IE or HARQ_DL_MAP_IE()+ MIMO DL Chase HARQ
Sub-Burst IE() with ACK Disable = 1
OFDMA downlink STC_DL_Zone IE format indicating dedicated pilots.
BS sends UL-MAP, compressed UL-MAP, or UCD to each MS with
OK
NOK
4
Fast Feedback Allocation IE or fast-feedback region TLV.
CQICH Allocation IE, allocating the fast-feedback slots.
BS sends UCD to each MS with
OK
NOK
5
Size of the CQICH_ID field. In case of default value, the BS doesn’t
need to send the size of the CQICH_ID field.
MS sends physical CINR report as indicated in the CQICH Allocation IE.
OK
NOK
If BS demands IO-SND certification,
-
PAPR reduction/Safety zone/Sounding zone allocation IE(),
UL_Sounding_Command_IE()
For all BS,
-
-
-
Observations
Page - 122
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.21.2.2 Data grants for the MS
Test Description
Identifier:
TD_SC2AB1_MIMO_DAT_01
Description:
Verify the generation of data grants for the MS in the UL/DL PUSC zone.
Pre-test
conditions:
Successful network entry.
Step
Test Sequence
Result
1
Are MAP message sent in the DL PUSC zone?
OK
NOK
2
Has the BS sent DL data for each MS in the appropriate DL PUSC zone?
OK
NOK
3
Has the BS generated UL grants for each MS in the appropriate UL PUSC
zone?
OK
NOK
Observations
8.21.2.3 Data Transfer
Test Description
Identifier:
TD_SC2AB1_MIMO_DAT_02
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes, with UL data transfer at the
same time for MS1 and MS2 to test collaborative SM functionality.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
Test Sequence
Result
1
Has the data from each MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to each MS been transferred correctly?
OK
NOK
Observations
Page - 123
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.22
WMF-T25-003-R010v08
Scenario 2AC0 – DL PUSC and UL PUSC without subchannel rotation
Test scenario behaviour
Ref
Goal
Verify DL and UL data transfer when UL PUSC without subchannel rotation and DL PUSC are
activated.
Configuration
Basic Test Configuration for IOT Testing - 1 MS+ 1 BS
Test
Condition
-
Frequency channel: Middle.
TX Power Level: Medium.
Beam Forming: Disable.
UL zone type: Two possible zone configurations where base station can choose one of them
o
o
UL Zone Config A: (One zone) PUSC zone without subchannel rotation.
UCD with UL PUSC subchannel rotation set to ‘1’ indicating default setting of UL
PUSC subchannel rotation be disabled starting from the beginning of the UL
subframe
or
UL Zone Config B: (Two zones) First zone is PUSC with subchannel rotation and
second zone is PUSC without subchannel rotation.
UCD with UL PUSC subchannel rotation is set to ‘0’ indicating default setting
where UL PUSC subchannel rotation be enabled. Subchannel rotation will be
disabled in the second zone using UL Zone Switch IE.
DL zone type: PUSC zone.
Dedicated pilots in DL PUSC zone: Disable.
CQI Channel for physical CINR Feedback: Enable.
ARQ: Optional.
HARQ: Optional.
Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’.
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
-
Initial State
Test process
1)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure.
Carry out 1 DL and 1 UL BS initiated BE service flow.
BS allocates Fast feedback channel for MS. (Table 7.1 / item 2).
Carry out DL and UL data transfer when UL PUSC without subchannel rotation and DL
PUSC are activated, via freestyle BE (such as FTP) data transfer (5 minute transfer for some
stability evaluation).
Successful data transfer in UL and DL.
2)
3)
4)
5)
6)
Pass verdict
criteria
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 124
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.22.1 Network Entry procedure
8.22.1.1 Capabilities Negotiation
Test Description
Identifier:
TD_SC2AC0_MIMO_SBC_00
Description:
Verify the successful completion of basic capabilities negotiation with PUSC zone. If one zone UL
frame configuration (UL Zone Config A) is used SBC-REQ is sent in the zone where subchannel
rotation is disabled. If two zone UL frame configuration (UL Zone Config B) is used SBC-REQ is sent
in the first zone where subchannel rotation is enabled.
Pre-test
conditions:
Successful completion of initial ranging.
Step
Test Sequence
Result
1
MS sends 1 or more SBC-REQ
OK
NOK
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
indicating the support of the following capabilities using OFDMA
Parameters Set and/or individual TLVs,
SS Modulator for MIMO support TLV:
Capable of single antenna transmission,
Capable of disabling UL subchannel rotation
Are TLVs defined appropriate to the required device capabilities?
BS sends SBC-RSP
OK
NOK
-
-
With valid TLVs that are present in the SBC-REQ appropriate for the
Wave capabilities,
and with values that do not enable a feature disabled/not supported
by MS.
Observations
Page - 125
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.22.2 User Data Transfer
8.22.2.1 MAP
Test Description
Identifier:
TD_SC2AC0_MIMO_DAT_00
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
Test Sequence
Result
1
BS sends UL-MAP or compressed UL-MAP to the MS with
OK
NOK
2
HARQ_UL_MAP_IE()+ UL HARQ Chase Sub-Burst IE() with ACK
Disable = 1 or direct UL allocation to UIUC1 to 10.
BS sends DL-MAP or compressed DL-MAP to the MS with
OK
NOK
3
HARQ_DL_MAP_IE()+ DL HARQ Chase Sub-Burst IE() with ACK
Disable = 1,
BS sends UL-MAP, compressed UL-MAP, or UCD to the MS with
OK
NOK
4
Fast Feedback Allocation IE or fast-feedback region TLV.
CQICH Allocation IE, allocating the fast-feedback slots.
BS sends UCD to the MS with
OK
NOK
OK
NOK
OK
NOK
-
-
5
Size of the CQICH_ID field. In case of default value, the BS doesn’t
need to send the size of the CQICH_ID field.
BS indicates UL PUSC subchannel rotation disabled:
If UL ZONE CONFIG A is used,
-
By transmitting UCD with UL PUSC subchannel rotation set to ‘1’
indicating default setting of UL PUSC subchannel rotation be disabled
starting from the beginning of the UL subframe
If UL ZONE CONFIG B is used,
-
6
By uUsing UL zone switch IE with Permutation set to ‘0b00’ (PUSC
permutation) and Disable subchannel rotation set to ‘1’ indicating
subchannel rotation disabled in the second zone.
MS sends physical CINR report as indicated in the CQICH Allocation IE.
Observations
Page - 126
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.22.2.2 Data grants for the MS
Test Description
Identifier:
TD_SC2AC0_MIMO_DAT_01
Description:
Verify the generation of data grants for the MS in the UL/DL PUSC zone.
Pre-test
conditions:
Successful network entry.
Step
Test Sequence
Result
1
Are MAP message sent in the DL PUSC zone?
OK
NOK
2
Has the BS sent DL data for the MS in the appropriate DL PUSC zone?
OK
NOK
3
Has the BS generated UL grants for each MS in the appropriate UL PUSC
zone?
OK
NOK
Observations
8.22.2.3 Data Transfer
Test Description
Identifier:
TD_SC2AC0_MIMO_DAT_02
Description:
Verify the successful completion of data transfer in UL and DL for 5 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
Test Sequence
Result
1
Has the data from each MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to each MS been transferred correctly?
OK
NOK
Observations
Page - 127
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.23
WMF-T25-003-R010v08
Scenario 2C0 – PHS IPv4
Test scenario behaviour
Ref
6.3.14.7 [1], 11.13.19 [1]
Goal
Verify DL/UL UDP/IPv4 streams when IPv4 Header suppression is enabled.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
Compressed-IPv4-Header: Disable.
PHS: Enable.
ARQ: Disable.
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used to
specify the burst shall set ACK disable = 1.
- Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’.
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service flow with classifier (Based on IP address/port number) and associated PHS rules.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
Pass verdict
criterion
Final Verdict
-
1)
2)
3)
4)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure with negotiation of PHS support.
Carry out 1 DL and 1 UL BS initiated service flow defining a PHS rule by adding a new service
flow using DSA-REQ with PHS rule or creating a PHS rule to an existing service flow using
DSC messages.
5) Carry out DL and UL data transfer with PHS activated
a) via UDP/IPv4 streaming (5 minute transfer for some stability evaluation).
Successful DL/UL data transfer with PHS activated.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 128
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.23.1 Network Entry procedure
8.23.1.1 Registration
Test Description
Identifier:
TD_SC2C0_PHS_REG_00
Description:
Verify the PHS support during registration.
Pre-test
conditions:
Step
Test Sequence
Result
1
MS sends 1 or more REG-REQ
OK
NOK
2
not more than PIC_MAX_REG_REQ_RETRIES REG-REQs,
PHS TLV indication PHS support.
BS sends REG-RSP
OK
NOK
-
with TLVs that are present in the REG-REQ, and with values
that do not enable a feature disabled by MS,
confirming PHS support.
Observations
8.23.2 Traffic Connection Establishment
8.23.2.1 Service Flow Provisioning
Test Description
Identifier:
TD_SC2C0_PHS_DSA_00
Description:
Verify the definition of PHS during traffic connection establishment as in TD_SC2C1_PHS_DSA_00_List.
Pre-test
conditions:
Registration completed.
Step
1
Test Sequence
BS sends 1 or more DSA-REQ or DSC-REQ,,
OK
NOK
OK
NOK
OK
NOK
-
2
not more than PIC_DSx_REQ_MAX_RETRIES DSA-REQs,
PHS Rule TLV defining at least,
PHSI value referencing the suppressed byte string,
the header information to be suppressed,
and total number of bytes in the header to be suppressed and then
restored in a service flow that uses PHS,
Packet classification rule TLV defining at least the Associated PHSI
value for the UL SF.
MS sends 1 or more DSA-RSP or DSC-RSP
Result
-
3
not more than PIC_DSx_RSP_MAX_RETRIES DSA-RSPs or DSCRSPs.
BS sends DSA-ACK or DSC-ACK
-
Confirmation Code set to OK.
Observations
Page - 129
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
TD_SC2C0_PHS_DSA_00_List
Nr.
Stimulate the BS to use the following parameters
1
UL DSA-REQ
2
DL DSA-REQ
Status
Run
Result
8.23.3 User Data Transfer
8.23.3.1 Data Transfer
Test Description
Identifier:
TD_SC2C0_PHS_DAT_00
Description:
Verify the successful completion of data transfer in UL and DL.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established. PHS Rule is defined and activated for each SF.
Step
Test Sequence
Result
1
Has the data from the MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to the MS been transferred correctly?
OK
NOK
Observations
Page - 130
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.24
WMF-T25-003-R010v08
Scenario 2C1 – PHS IPv6
Test scenario behaviour
Ref
6.3.14.7 [1], 11.13.19 [1]
Goal
Verify DL/UL UDP/IPv4 streams when IPv6 Header suppression is enabled.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
Compressed-IPv6-Header: Disable.
PHS: Enable.
ARQ: Disable.
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used to
specify the burst shall set ACK disable = 1.
- Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’.
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
Pass verdict
criterion
Final Verdict
-
6)
7)
8)
9)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure with negotiation of PHS support.
Carry out 1 DL and 1 UL BS initiated service flow defining a PHS rule by adding a new service
flow using DSA-REQ with PHS rule or creating a PHS rule to an existing service flow using
DSC messages.
10) Carry out DL and UL data transfer with PHS activated
a) via UDP/IPv6 streaming (5 minute transfer for some stability evaluation).
Successful DL/UL data transfer with PHS activated.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 131
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.24.1 Network Entry procedure
8.24.1.1 Registration
Test Description
Identifier:
TD_SC2C1_PHS_REG_00
Description:
Verify the PHS support during registration.
Pre-test
conditions:
Step
Test Sequence
Result
1
MS sends 1 or more REG-REQ
OK
NOK
2
not more than PIC_MAX_REG_REQ_RETRIES REG-REQs,
PHS TLV indication PHS support.
BS sends REG-RSP
OK
NOK
-
with TLVs that are present in the REG-REQ, and with values
that do not enable a feature disabled by MS,
confirming PHS support.
Observations
Page - 132
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.24.2 Traffic Connection Establishment
8.24.2.1 Service Flow Provisioning
Test Description
Identifier:
TD_SC2C1_PHS_DSA_00
Description:
Verify the definition of PHS during traffic connection establishment as in TD_SC2C1_PHS_DSA_00_List.
Pre-test
conditions:
Registration completed.
Step
1
Test Sequence
Result
BS sends 1 or more DSA-REQ or DSC-REQ,,,
NOK
OK
NOK
OK
NOK
-
2
not more than PIC_DSx_REQ_MAX_RETRIES DSA-REQs,
PHS Rule TLV defining at least,
PHSI value referencing the suppressed byte string,
the header information to be suppressed,
and total number of bytes in the header to be suppressed and then
restored in a service flow that uses PHS,
Packet classification rule TLV defining at least the Associated PHSI
value.
MS sends 1 or more DSA-RSP or DSC-RSP
OK
-
3
not more than PIC_DSx_RSP_MAX_RETRIES DSA-RSPs or DSCRSPs.
BS sends DSA-ACK or DSC-ACK
-
Confirmation Code set to OK.
Observations
TD_SC2C1_PHS_DSA_00_List
Nr.
Stimulate the BS to use the following parameters
1
UL DSA-REQ
2
DL DSA-REQ
Page - 133
WiMAX FORUM PROPRIETARY
Status
Run
Result
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.24.3 User Data Transfer
8.24.3.1 Data Transfer
Test Description
Identifier:
TD_SC2C1_PHS_DAT_00
Description:
Verify the successful completion of data transfer in UL and DL.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established. PHS Rule is defined and activated for each SF.
Step
Test Sequence
Result
1
Has the data from the MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to the MS been transferred correctly?
OK
NOK
Observations
Page - 134
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.25
WMF-T25-003-R010v08
Scenario 2D0 – ROHC UDP/IPv4 streams
This testing for ROHC requires NWG support in their release 1.5. This test case is kept for reference in this
document and may need review before implementation.
Test scenario behaviour
Ref
5.2.7 [1], 6.3.14.7 [1]
Goal
Verify DL/UL UDP/IPv4 streams when a Packet Classification Rule for ROHCCompressed-IP-Header is defined and no PHS rule is defined.
Configuration
Basic Test Configuration for IOT Testing.
Test Condition
-
-
Initial State
Test process
Frequency channel: Middle.
TX Power Level: Medium.
Compressed-IPv4-Header: Enable.
PHS: Disable.
ARQ: Disable.
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP
IE used to specify the burst shall set ACK disable = 1.
Any non- HARQ DL/UL connection is established by including HARQ Service
Flows field (TLV Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the
HARQ Service Flows field (which means default value ‘non-HARQ’.
Authentication: Optional. If authentication is used, the method shall be one of those
specified in NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1,
section 4.4.1.2.2 or 4.4.1.2.3.
SS Management: Unmanaged.
1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the
MS can support the Pre-Provisioned Service Flows.
Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
1)
2)
3)
4)
5)
Pass verdict criterion
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure with ROHC support.
Carry out 1 DL and 1 UL BS initiated BE service flow with ROHC support.
Carry out DL and UL data transfer
a) via UDP/ROHC-compressed IPv4 streaming (5 minute transfer for some
stability evaluation).
Successful DL/UL data transfer with ROHC activated.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 135
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.25.1 Network Entry procedure
8.25.1.1 Registration
Test Description
Identifier:
TD_SC2D0_ROHC_REG_00
Description:
Verify the successful completion of registration with ROHC support.
Pre-test
conditions:
Successful completion of basic capabilities negotiation. No authentication is required.
Step
1
Test Sequence
MS sends 1 or more REG-REQ
OK
NOK
OK
NOK
-
2
not more than PIC_MAX_REG_REQ_RETRIES of REG-REQs,
with Classification/PHS options and SDU encapsulation support TLV
indicating Packet, IP (v4 or v6) with ROHC header compression. REG
messages do not contain classification, PHS or ROHC params TLV
BS sends REG-RSP
Result
-
with response set to OK.
with valid TLVs that are present in the REG-REQ are in the appropriate
Wave,
and with values that do not enable a feature disabled/not supported by
MS.
Observations
Page - 136
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.25.2 Traffic Connection Establishment
8.25.2.1 Service Flow Provisioning
Test Description
Identifier:
TD_SC2D0_ROHC_DSA_00
Description:
Verify the successful completion of service flow establishment as in TD_SC2D0_ROHC_DSA_List.
Pre-test
conditions:
Successful completion of registration and 1 DL and 1 UL Service Flows are Pre-Provisioned at the BS for
this MS and the MS can support the Pre-Provisioned Service Flows.
Step
1
Test Sequence
Result
BS sends 1 or more DSA-REQ
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs,
Service Flow Scheduling Type set to BE,
Request/transmission policy TLV indicating no suppression of payload
headers,
CS specification TLV indicating Packet, IP with header ROHC
compression,
ROHC Parameter Payload TLV.
MS sends 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs,
confirming the requested settings.
BS sends DSA-ACK
OK
NOK
-
-
Confirmation Code set to OK.
Observations
TD_SC2D0_ROHC_DSA_List
Nr.
Stimulate the BS to use the following parameters
1
UL DSA-REQ
2
DL DSA-REQ
Page - 137
WiMAX FORUM PROPRIETARY
Status
Run
Result
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.25.3 User Data Transfer
8.25.3.1 Data Transfer
Test Description
Identifier:
TD_SC2D0_ROHC_DAT_00
Description:
Verify the successful completion of data transfer for 5 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number. IP Header compression is enabled.
Step
Test Sequence
Result
1
Has the data from the MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to the MS been transferred correctly?
OK
NOK
Observations
8.26
Scenario 2D1 – ROHC UDP/IPv6 streams
This testing for ROHC requires NWG support in Release 1.5. This test case is kept for reference in this document
and may need review before implementation.
Test scenario behaviour
Ref
5.2.7 [1], 6.3.14.7 [1]
Goal
Verify DL/UL UDP/IPv6 streams when a Packet Classification Rule for ROHCCompressed-IP-Header is defined and no PHS rule is defined.
Configuration
Basic Test Configuration for IOT Testing.
Test Condition
-
-
-
Frequency channel: Middle.
TX Power Level: Medium.
Compressed-IPv6-Header: Enable.
PHS: Disable.
ARQ: Disable.
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP
IE used to specify the burst shall set ACK disable = 1.
Any non- HARQ DL/UL connection is established by including HARQ Service
Flows field (TLV Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the
HARQ Service Flows field (which means default value ‘non-HARQ’.
Authentication: Optional. If authentication is used, the method shall be one of those
specified in NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1,
section 4.4.1.2.2 or 4.4.1.2.3.
SS Management: Unmanaged.
1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the
MS can support the Pre-Provisioned Service Flows.
Service Flows Classification Rule: Based on IP address/port number.
Page - 138
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Initial State
MS is deregistered from BS. MS is switched off. BS remains on.
Test process
1)
2)
3)
4)
5)
Pass verdict criterion
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure with ROHC support.
Carry out 1 DL and 1 UL BS initiated BE service flow with ROHC support.
Carry out DL and UL data transfer
a) via UDP/ROHC-compressed IPv6 streaming (5 minute transfer for some stability
evaluation).
Successful DL/UL data transfer with ROHC activated.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
8.26.1 Network Entry procedure
8.26.1.1 Registration
Test Description
Identifier:
TD_SC2D1_ROHC_REG_00
Description:
Verify the successful completion of registration with ROHC support.
Pre-test
conditions:
Successful completion of basic capabilities negotiation. No authentication is required.
Step
1
Test Sequence
MS sends 1 or more REG-REQ
OK
NOK
OK
NOK
-
2
not more than PIC_MAX_REG_REQ_RETRIES of REG-REQs,
with Classification/PHS options and SDU encapsulation support TLV
indicating Packet, IP (v4 or v6) with ROHC header compression. REG
messages do not contain classification, PHS or ROHC params TLV
BS sends REG-RSP
Result
-
with response set to OK.
with valid TLVs that are present in the REG-REQ are in the appropriate
Wave,
and with values that do not enable a feature disabled/not supported by
MS.
Observations
Page - 139
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.26.2 Traffic Connection Establishment
8.26.2.1 Service Flow Provisioning
Test Description
Identifier:
TD_SC2D1_ROHC_DSA_00
Description:
Verify the successful completion of service flow establishment as in TD_SC2D1_ROHC_DSA_List.
Pre-test
conditions:
Successful completion of registration and 1 DL and 1 UL Service Flows are Pre-Provisioned at the BS for
this MS and the MS can support the Pre-Provisioned Service Flows.
Step
1
Test Sequence
Result
BS sends 1 or more DSA-REQ
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs,
Service Flow Scheduling Type set to BE,
Request/transmission policy TLV indicating no suppression of payload
headers,
CS specification TLV indicating Packet, IP with header ROHC
compression,
ROHC Parameter Payload TLV.
MS sends 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs,
confirming the requested settings.
BS sends DSA-ACK
OK
NOK
-
-
Confirmation Code set to OK.
Observations
TD_SC2D1_ROHC_DSA_List
Nr.
Stimulate the BS to use the following parameters
1
UL DSA-REQ
2
DL DSA-REQ
Page - 140
WiMAX FORUM PROPRIETARY
Status
Run
Result
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.26.3 User Data Transfer
8.26.3.1 Data Transfer
Test Description
Identifier:
TD_SC2D1_ROHC_DAT_00
Description:
Verify the successful completion of data transfer for 5 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established.
Step
Test Sequence
Result
1
Has the data from the MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to the MS been transferred correctly?
OK
NOK
Observations
Page - 141
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.27
WMF-T25-003-R010v08
Scenario 2E0 – MS initiated Service Flow Establishment and Deletion
Test scenario behaviour
Ref
6.3.14.7 [1], 6.3.14.8 [1]
Goal
Verify MS initiated Service Flow Creation/Deletion.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Disable.
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used to
specify the burst shall set ACK disable = 1.
- Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’.
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- Service Flows Classification Rule: Based on IP address/port number.
- For this test, BS1 should have the ranging region within the first three symbols in the uplink
frame and BS2 should have the ranging region not in the first three symbols in the uplink frame
in order to ensure that the MS can properly transmit with a flexible frame structure.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
Pass verdict
criterion
Final Verdict
-
1)
2)
3)
4)
5)
6)
7)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure.
Carry out 1 DL and 1 UL BS initiated BE service flow
Carry out 1 DL and 1 UL MS initiated UGS service flow. (Table 7.1 / item 17).
Carry out UGS DL and UGS UL data transfer.
Carry out BE DL and BE UL data transfer.
a) via the PING procedure: Host behind the BS pings the MS or pings the host behind the MS
(depending on the type of MS)
Host behind the MS pings
or the MS itself (depending on the type of the MS) the host behind the BS.
8) Carry out MS initiated service flow deletion.
Successful exchange of UGS DL/UL data transfer,
followed by successful exchange of BE Ping Traffic,
followed by indication that all Service Flows are down.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 142
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.27.1 MS initiated Service Flow Creation
Test Description
Identifier:
TD_SC2E0_RLC_DSA_00
Description:
Verify the successful completion of service flow establishment as in TD_SC2E0_RLC_DSA_List.
Pre-test
conditions:
Successful completion of registration.
Step
Test Sequence
Result
1
MS sends 1 or more DSA-REQ (Table 7.1 / item 17)
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs.
BS sends 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs.
MS sends DSA-ACK
OK
NOK
-
Confirmation Code set to OK.
Observations
TD_SC2E0_RLC_DSA_List
Nr.
Stimulate the MS to use the following parameters
Status
Run
Result
DSA-REQ (for UL SF)
1
Service Flow Scheduling Type set to USG
m
Yes/No
m
Yes/No
DSA-REQ (for DL SF)
2
Service Flow Delivery ServiceType set to USG
8.27.2 UGS Data Transfer
Test Description
Identifier:
TD_SC2E0_RLC_DAT_00
Description:
Verify the successful completion of UGS data transfer for 5 minutes.
Pre-test
conditions:
1 UGS UL and 1 UGS DL Service Flow is established. The classification rule for mapping the CID is
based on IP address/port number.
Step
Test Sequence
Result
1
Has the data from the MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to the MS been transferred correctly?
OK
NOK
Observations
Page - 143
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.27.3 MS initiated Service Flow Deletion
Test Description
Identifier:
TD_SC2E0_RLC_DSD_00
Description:
Verify the successful completion of service flow deletion
Pre-test
conditions:
Successful PING procedure.
Step
Test Sequence
Result
1
MS sends 1 or more DSD-REQ (Table 7.1 / item 16)
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES of DSD-REQs,
with SFID of service flow.
BS sends 1 or more DSD-RSP
OK
NOK
-
not more than PIC_DSx_RSP_MAX_RETRIES of DSD-RSPs.
Observations
Page - 144
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.28
WMF-T25-003-R010v08
Scenario 2F0 – RT-VR/NRT-VR
Test scenario behaviour
Ref
6.3.20 [1]
Goal
Checks that QoS characteristics of the RT-VR service and NRT-VR service are not damaged by
any simultaneous transmission through a BE service flow.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Disable.
HARQ: Disabled. If a HARQ MAP IE is used to specify the burst, the HARQ MAP IE used to
specify the burst shall set ACK disable = 1.
- Any non- HARQ DL/UL connection is established by including HARQ Service Flows field (TLV
Type = [145/146].44) set to ‘0’ (non-HARQ) or by omitting the HARQ Service Flows field (which
means default value ‘non-HARQ’.
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 UL NRT-VR and 1 UL RT-VR and 1 UL BE Service Flows are Pre-Provisioned at the BS for
this MS and the MS can support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
Pass verdict
criterion
-
1) Start the monitor message capture, if available.
2) Switch on the MS.
3) Carry out the Network Entry procedure.
4) Carry out 1 DL and 1 UL BS initiated BE service flow.
5) Carry out 1 UL NRT-VR and 1 UL RT-VR. (Table 7.1 / Item 18 and Item 19.
6) Carry out simultaneous UL data transfer.
Verify the successful UL data transfer of the RT-VR service when having a simultaneous UL
transmission through a BE service flow.
Verify the successful UL data transfer of the NRT-VR service when having a simultaneous UL
transmission through a BE service flow.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 145
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.28.1 Traffic Connection Establishment
8.28.1.1 RT-VR Service Flow Provisioning
Test Description
Identifier:
TD_SC2F0_RLC_DSA_00
Description:
Verify the successful completion of BS initiated RT-VR service flow establishment.
Pre-test
conditions:
X
Step
Test Sequence
Result
1
BS sends 1 or more DSA-REQ
OK
NOK
2
to define an UL service flow,
with Service Flow Scheduling Type set to rtPS,
with Maximum Latency,
with Minimum Reserved Traffic Rate,
with Maximum Sustained Traffic Rate,
Traffic Priority,
with Request/Transmission Policy,
unsolicited polling interval,
not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs.
MSs send 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs.
BS sends DSA-ACK to each MS
OK
NOK
-
Confirmation Code set to OK.
Observations
Page - 146
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.28.1.2 NRT-VR Service Flow Provisioning
Test Description
Identifier:
TD_SC2F0_RLC_DSA_00
Description:
Verify the successful completion of BS initiated NRT-VR service flow establishment.
Pre-test
conditions:
X
Step
Test Sequence
Result
1
BS sends 1 or more DSA-REQ
OK
NOK
2
to define an UL service flow,
with Service Flow Scheduling Type set to nrtPS,
with Minimum Reserved Traffic Rate,
with Maximum Sustained Traffic Rate,
Traffic Priority,
with Request/Transmission Policy,
not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs.
MSs send 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs.
BS sends DSA-ACK to each MS
OK
NOK
-
Confirmation Code set to OK.
Observations
8.28.2 User Data Transfer
8.28.2.1 RT-VR Data Transfer
Test Description
Identifier:
TD_SC2F0_RLC_DAT_00
Description:
Verify the successful data transfer of the data delivery services RT-VR.
Pre-test
conditions:
1 UL RT-VR service flow established and 1 UL BE service flow established.
Step
Test Sequence
1
Has the UL data been transferred correctly on the RT-VR service when having a
simultaneous UL transmission through a BE service flow?
Observations
Page - 147
WiMAX FORUM PROPRIETARY
Result
OK
NOK
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.28.2.2 NRT-VR Data Transfer
Test Description
Identifier:
TD_SC2F0_RLC_DAT_01
Description:
Verify the successful data transfer of the data delivery services NRT-VR.
Pre-test
conditions:
1 UL NRT-VR service flow established and 1 UL BE service flow established.
Step
Test Sequence
1
Has the UL data been transferred correctly on the NRT-VR service when having
a simultaneous UL transmission through a BE service flow?
Observations
Page - 148
WiMAX FORUM PROPRIETARY
Result
OK
NOK
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.29
WMF-T25-003-R010v08
Scenario 2G0- BS initiated Handover
Test scenario behaviour
Ref
6.3.22 [1]
Goal
Verify BS initiated handover (Inter FA (different frequencies))
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
SBS and TBS transmit on different frequencies
TX Power Level: SBS Medium, TBS Initially Off.
ARQ: Optional.
HARQ: Optional.
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- TPC mode: Open loop.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the SBS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
- For this test, the vendor must enable that BS initiated HO will occur before the MS will initiate a
HO (Table 7.1 / item 23).
MS is deregistered from BSs. MS is switched off. BSs remain on.
Initial State
-
SBS does not coordinate association between MS and TBS.
Test process
Pass verdict
criterion
Final Verdict
1)
2)
3)
4)
5)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure and create UL and DL service flows.
Ensure the target BS is on. (TX Power Level: SBS and TBS medium level.)
Configure the DCD parameter for BS and use the external attenuator to make the Serving BS
signal lower than that of the target BS, but still high enough so that trigger condition at the MS
for HO is not met. (This is done in order to avoid MS initiated handover.) MS delivers
measurement results to the BS. Now the BS should initiate the handover by sending a
MOB_BSHO-REQ, either based on the measurement results or caused by vendor specific
external trigger (Table 7.1 / item 23).
6) Carry out DL and UL data transfer via the PING procedure:
Host behind the target BS pings the MS or pings the host behind the MS (depending on the
type of MS)
Host behind the MS or the MS itself (depending on the type of the MS pings the host behind
the target BS.
Successful handover from SBS to TBS and PING procedure with TBS.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 149
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.29.1 Neighbor Advertisement
Test Description
Identifier:
TD_SC2G0_BS_GHF_ADV_00
Description:
Verify the Neighbor Advertisement and UL-MAPs of SBS and TBS.
Pre-test
conditions:
Successful completion of initial network entry.
Step
Test Sequence
Result
1
SBS and TBS send MOB_NBR-ADV.
OK
NOK
2
TBS sends UL-MAP with Fast ranging IE with HO ID or MS’s MAC address.
OK
NOK
Observations
Page - 150
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.29.2 Scanning
Test Description
Identifier:
TD_SC2G0_BS_GHF_SCN_00
Description:
Verify the successful completion of allocation of a group of scanning intervals and the use of the
scanning intervals.
Pre-test
conditions:
X
Step
Test Sequence
Result
1
MS sends 1 or more MOB_SCN-REQ
OK
NOK
2
unsolicited,
with Scanning Type indicating Scanning without Association.
SBS sends MOB_SCN-RSP
OK
NOK
-
granting a scanning interval.
OR
1
BS sends DCD
OK
NOK
2
defining a trigger condition with action value 0x3.
MS sends 1 or more MOB_SCN-REQ
OK
NOK
3
because trigger condition is met,
with Scanning Type indicating Scanning without Association.
SBS sends MOB_SCN-RSP
OK
NOK
OK
NOK
-
granting a scanning interval.
OR
1
SBS sends MOB_SCN-RSP
-
with Scanning Type indicating Scanning without Association,
granting a scanning interval.
Observations
8.29.3 Scan Report
Test Description
Identifier:
TD_SC2G0_BS_GHF_SCNRPT_00
Description:
Verify the successful completion of Scan reporting only if Trigger Conditions are met.
Pre-test
conditions:
X
Step
Test Sequence
Result
1
BS sends DCD
OK
NOK
2
defining a trigger condition with action value 0x1
MS sends MOB_SCN-REP
OK
NOK
-
because trigger condition is met,
Observations
Page - 151
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.29.4 Handover Decision
Test Description
Identifier:
TD_SC2G0_BS_GHF_HOD_00
Description:
Verify the successful completion of BS initiated Handover Decision.
Pre-test
conditions:
Successful completion of initial network entry.
MS received Neighbor Advertisement from Serving BS.
Step
1
Test Sequence
If required trigger handover initiation at the Serving BS (Table 7.1 / item 23).
Result
OK
NOK
BS sends MOB_BSHO-REQ
-
indicating the target BS.
Observations
8.29.5 Handover Initiation
Test Description
Identifier:
TD_SC2G0_BS_GHF_NWE_00
Description:
Verify the successful completion of Handover Initiation from serving BS to target BS with network entry.
Pre-test
conditions:
MS has been instructed to handover from serving BS to target BS.
Step
1
2
Test Sequence
MS sends optionally a MOB_HO-IND to serving BS
Result
OK
NOK
OK
NOK
With HO_IND_type = 0b00 (serving BS release)
MS moves to target BS and synchronizes to DL signal
MS sends Handover CDMA ranging codes in the Initial Ranging Interval to the
target BS and sends RNG-REQ or
MS sends RNG-REQ message using the received Fast Ranging IE.
3
MS finishes Network Entry with TBS and the BS updates the CIDs.
Observations
Page - 152
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.29.6 Handover Verification
8.29.6.1 PING
Test Description
Identifier:
TD_SC2G0_BS_GHF_DAT_00
Description:
Verify the successful completion of data transfer via the PING procedure.
Pre-test
conditions:
1 UL and 1 DL BE Service Flow is established.
Step
1
Test Sequence
Host behind the target BS pings the MS or pings the host behind the MS
(depending on the type of the MS).
OK
NOK
OK
NOK
-
2
The CID of the DL MAC PDU (EchoRequest) is the Transport Cid of
the DL Service Flow.
The CID of the UL MAC PDU (EchoReply) is the Transport Cid of the
UL Service Flow.
Is the PING procedure successfully completed?
Host behind the MS or the MS itself (depending on the type of the MS) pings the
host behind the target BS.
Result
-
The CID of the UL MAC PDU (EchoRequest) is the Transport Cid of
the UL Service Flow.
The CID of the DL MAC PDU (EchoReply) is the Transport Cid of the
DL Service Flow.
Is the PING procedure successfully completed?
Observations
Page - 153
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.30
WMF-T25-003-R010v08
Scenario 2G1– Drop of Target BS During Handover
Test scenario behaviour
Ref
6.3.22 [1]
Goal
Verify behavior for Drop of Target BS During BS initiated Handover.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Optional.
HARQ: Optional.
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- TPC mode: Open loop.
- SS Management: Unmanaged.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the SBS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
- The test has to finish before the Resource_Retain_Timer expires.
MS is deregistered from BSs. MS is switched off. BSs remain on.
Initial State
-
SBS does not coordinate association between MS and TBS.
Test process
1)
2)
3)
4)
5)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure and create UL and DL service flows.
Ensure the target BS is on.
Now, BS or MS initiated handover is possible.
In the case of BS initiated handover:
6) Use the DCD for BS and attenuate the Serving BS signal such that it is lower than that of the
target BS, but still high enough so that trigger condition is not met. (This is done in order to
avoid MS initiated handover.) Alternatively, trigger handover initiation at the Serving BS (Table
7.1 / item 23).
In the case of MS initiated handover:
Pass verdict
criterion
Final Verdict
7) Attenuate the Serving BS signal in order to trigger handover initiation or use a manual command
at the MS. (Table 7.1 / item 12 or Item 13).
8) During handover, when MS starts network entry with TBS, drop the signal of the TBS. (One
option is to disconnect instead the receiver path only of the TBS for this test)
9) Bring up SBSs signal in order to allow network re-entry with SBS.
10) Carry out DL and UL data transfer via the PING procedure:
Host behind the serving BS pings the MS or pings the host behind the MS (depending on the
type of MS) and
Host behind the MS or the MS itself (depending on the type of the MS pings the host behind
the serving BS.
After drop of signal of TBS, successful network re-entry with SBS.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 154
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.30.1 Network re-entry with Serving BS
Test Description
Identifier:
TD_SC2G1_GHF_DTB_00
Description:
Verify the reaction of MS to the drop of target BS during Handover.
Pre-test
conditions:
MS has done handover from serving BS to target BS and target BS drops.
Step
Test Sequence
result
1
MS synchronizes to Serving BS.
OK
NOK
2
MS sends MOB_HO-IND to serving BS in case Resource Retain Timer does not
expired.
OK
NOK
-
with HO_IND_Type = 0b01 ( Handover cancel).
Observations
8.30.2 Network re-entry Verification
8.30.2.1 PING
Test Description
Identifier:
TD_SC2G1_GHF_DAT_00
Description:
Verify the successful completion of data transfer via the PING procedure.
Pre-test
conditions:
1 UL and 1 DL BE Service Flow is established.
Step
Test Sequence
1
Host behind the serving BS pings the MS or pings the host behind the MS
(depending on the type of the MS).
The CID of the DL MAC PDU (EchoRequest) is the Transport Cid of
the DL Service Flow.
The CID of the UL MAC PDU (EchoReply) is the Transport Cid of the
UL Service Flow.
Is the PING procedure successfully completed?
Host behind the MS or the MS itself (depending on the type of the MS) pings the
host behind the serving BS.
Result
OK
NOK
OK
NOK
-
2
-
The CID of the UL MAC PDU (EchoRequest) is the Transport Cid of
the UL Service Flow.
The CID of the DL MAC PDU (EchoReply) is the Transport Cid of the
DL Service Flow.
Is the PING procedure successfully completed?
Observations
8.31
Scenario 2G2 – HO Cancel
Page - 155
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Test scenario behaviour
Ref
Scenario 2G2 – HO Cancel
Goal
Verify the HO cancel procedure
Configuration
Basic Test Configuration for IOT Testing.
Test Condition
- Frequency channel: Middle.
- TX Power Level: Medium.
- ARQ: Optional.
- HARQ: Optional.
- Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- TPC Mode: Open Loop.
- SBS & TBS Transmit on same frequency.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the SBS for this MS and the MS can
support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
- TPC mode: Open loop.
- SBS and TBS transmit on the same frequency.
Initial State
Test process
Pass verdict
criterion
Final Verdict
MS is deregistered from each BS. MS is switched off. BSs remains on.
1)
2)
3)
4)
5)
6)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure and create UL and DL service flows.
Disconnect the target BS UL.
Attenuate the Serving BS signal in order to trigger MS initiated handover.
The MS will initiate HO but will come back to the serving BS with HO cancel as the
NWRE at the TBS will not work due to UL problem.
7) Remove the attenuation on the Serving BS.
Successful DL/UL data transfer after HO cancel.
FAIL
PASS
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
8.31.1 Neighbor Advertisement
Test Description
Identifier:
TD_SC1j_MS_GHF_ADV_00
Description:
Verify the Neighbor Advertisement and UL-MAPs of SBS and TBS.
Pre-test
conditions:
Successful completion of initial network entry and service flow establishment.
Step
Test Sequence
Result
1
SBS and TBS send MOB_NBR-ADV.
OK
Observations
Page - 156
WiMAX FORUM PROPRIETARY
NOK
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.31.2 Network Re-entry with Serving BS
Test Description
Identifier:
TD_SC2G1_GHF_DTB_00
Description:
Verify the reaction of MS to the communication problem with the target BS during Handover.
Pre-test
conditions:
The target BS UL is disconnected. MS has initiated handover from serving BS to target BS.
Step
Test Sequence
1
MS synchronizes to Serving BS.
OK
NOK
2
MS sends MOB_HO-IND to serving BS in case Resource Retain Timer does not
expired.
OK
NOK
-
Result
with HO_IND_Type = 0b01 ( Handover cancel).
Observations
8.31.3 Network Re-entry Verification
Test Description
Identifier:
TD_SC2G1_GHF_DAT_00
Description:
Verify the successful completion of data transfer via the PING procedure.
Pre-test
conditions:
1 UL and 1 DL BE Service Flow is established.
Step
Test Sequence
Result
1
Host behind the serving BS pings the MS or pings the host behind the MS (depending
on the type of the MS).
OK
NOK
OK
NOK
The CID of the DL MAC PDU (EchoRequest) is the Transport CID of the DL Service
Flow.
The CID of the UL MAC PDU (EchoReply) is the Transport CID of the UL Service
Flow.
Is the PING procedure successfully completed?
2
Host behind the MS or the MS itself (depending on the type of the MS) pings the host
behind the serving BS.
The CID of the UL MAC PDU (EchoRequest) is the Transport CID of the UL Service
Flow.
The CID of the DL MAC PDU (EchoReply) is the Transport CID of the DL Service
Flow.
Is the PING procedure successfully completed?
Observations
Page - 157
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.32
WMF-T25-003-R010v08
Scenario 2M0 – Multi-BS MBS
Test scenario behaviour
Ref
6.3.23 [1]
Goal
Verify the use of Multi-BS MBS with 1 BS sending in the MBS_Zone in a P2MP configuration.
Configuration
Basic Test Configuration for IOT Testing - 2 MS+ 1 BS
Test
Condition
Frequency channel: Middle.
TX Power Level: Medium.
Single-BS access: Disable.
Multi-BS access: Enable.
MAC layer Encryption for multicast connection: Disable.
Upper layer encryption; Disable.
ARQ: Not Applicable.
HARQ: Not Applicable.
Authentication: Optional. If authentication is used, the method shall be one of those specified in
NWG WiMAX Forum Network Architecture, Stage 3 document, v1.1.1, section 4.4.1.2.2 or
4.4.1.2.3.
- SS Management: Unmanaged.
- 1 DL BE Service Flow is Pre-Provisioned at the BS for all MSs and each MS can support the
Pre-Provisioned Service Flow.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MSs are switched off. BS remains on.
Initial State
Test process
Pass verdict
criterion
Final Verdict
-
1)
2)
3)
4)
5)
Start the monitor message capture, if available.
Switch on the MSs.
Carry out MBS data transfer.
Carry out the Network Entry procedure for each MS simultaneously.
Trigger 1 DL BS initiated MBS service flow for each MS simultaneously
or trigger 1 DL MS initiated MBS service flow (Table 7.1 / item 21 or item 22).
Successful reception of MBS contents at each MS.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 158
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.32.1 MAP
Test Description
Identifier:
TD_SC2M0_MBS_ACQ_00
Description:
Verify the broadcast of MBS relevant information.
Pre-test
conditions:
Multi-BS MBS supported.
Step
1
Test Sequence
BS sends DL-MAP or compressed DL-MAP to each MS with
-
Result
OK
NOK
OK
NOK
MBS MAP IE, which may be omitted even if MBS_MAP message is
present in the DL frame.
BS sends MBS_MAP message
2
BS sends DCD to each MS with
-
MBS zone identifier list.
Observations
Page - 159
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.32.2 Traffic Connection Establishment
8.32.2.1 Service Flow Provisioning
Test Description
Identifier:
TD_SC2M0_MBS_DSA_00
Description:
Verify the BS initiated establishment of a MBS connection for multiple MBS content.
Pre-test
conditions:
Registration completed.
Step
1
Test Sequence
BS sends 1 or more DL DSA-REQ,
Result
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES DSA-REQs,
MBS service TLV indicating Multi-BS-MBS,
MBS Zone Identifier TLV,
MBS contents IDs TLV indicating at least 1 MBS contents ID
and the MBS contents ID matches a Logical Channel ID included in the
Extended MBS_DATA_IE.
MS sends 1 or more DSA-RSP
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES DSA-RSPs.
BS sends DSA-ACK
OK
NOK
Or
OK
NOK
1
MS sends 1 or more DL DSA-REQ,
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES DSA-REQs,
MBS service TLV indicating Multi-BS-MBS,
no MBS Zone Identifier TLV,
no MBS contents IDs TLV.
BS sends 1 or more DSA-RSP
OK
NOK
OK
NOK
-
-
Confirmation Code set to OK.
-
3
not more than PIC_DSx_RSP_MAX_RETRIES DSA-RSPs,
MBS service TLV indicating Multi-BS-MBS,
MBS Zone Identifier TLV,
MBS contents IDs TLV indicating at least 1 MBS contents ID
and the MBS contents ID matches a Logical Channel ID included in the
Extended MBS_DATA_IE.
MS sends DSA-ACK
-
Confirmation Code set to OK.
Observations
Page - 160
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.32.3 User Data Transfer
8.32.3.1 Data Transfer
Test Description
Identifier:
TD_SC2M0_MBS_DAT_00
Description:
Successful reception of MBS contents at each MS.
Pre-test
conditions:
1 MBS DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number.
Step
1
Test Sequence
Has the data from the BS to each MS been transferred correctly?
Observations
Page - 161
WiMAX FORUM PROPRIETARY
Result
OK
NOK
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.33
WMF-T25-003-R010v08
Scenario 2N0 – FFR with segmented PUSC
Test scenario behaviour
Ref
Basic Configuration
Goal
Verify FFR operation at MS and BS
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
-
-
-
-
No of BS: 2
o BS1: FFR Configuration (BS Under test).
o BS2: FFR Configuration of Neighboring Sector
No of MS:
o In case of MS testing: 1 (MS1 is under test and test steps for MS 2 are not applicable).
o In case of BS testing: 2 (Test steps for both MS 1 and MS 2 are applicable).
TX Power Level:
o MS: controlled by power control algorithm; typically at maximum power
o BS: 10 Watt per antenna (BS vendor may select alternate TX power level)
TPC mode: Open loop
DL/UL Ratio: 29:18
DL 2-antenna STC matrix A and B: Enable. When supported by BS, switchable between A and
B.
DL zone type. Segmented PUSC.
UL Single-antenna Collaborative SM: optional.
UL zone type. Segmented or unsegmented PUSC.
CQI Channels for physical CINR Feedback measured on Pilot and Preamble:
o CQICH_Allocation_IE requesting preamble reuse 1 PCINR.
o CQICH_Allocation_IE requesting pilots PCINR for 1st DL zone.
Size of CQICH_ID field: 3bits or 6 bits (preferred, if supported)
ARQ: Optional.
HARQ: (combined MIMO+HARQ) enable or with ACK disable = 0.
Compressed MAP: yes
1 UL and 1 DL BE Service Flows established.
Service Flows Classification Rule: Based on IP address/port number.
The BS will be configured with a combination of both 10 subchannels (5 sub channels) in
Segmented Zone and 30 subchannels (15 subchannels) in Non-segmented Zone in a
frame for DL for 1024 FFT (512 FFT).
o Configure bit 2 and 3 to 1 of the ‘used subchannel bit map’ in FCH, where the
other bits are configured to zero (Table - OFDMA DL Frame Prefix format for all
FFT sizes except 128)
o In zone switch IE (Table- OFDMA STC DL Zone IE format) configure ‘use all SC’
bit to 1
o Preamble index with Segment ID=1
Page - 162
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
Initial State
WMF-T25-003-R010v08
1)
MS1,MS2,BS1, and BS2 are connected as shown in the Fig1.
2)
Set Attenuator1 and Attenuator3 or trigger (Table 7.1 / item 26) .such that MS1 will be in the
PUSC 1/1 zone. Set Attenuator2 and Attenuator 4 or trigger (Table 7.1 / item 27) such that
MS2 will be in the PUSC 1/3 zone
3)
2 MSs are deregistered from the BS. MSs are switched off. BS remains on.
4)
MS1 must see strong signal from BS1 while seeing little interference from BS2. Attenuator1 is
set to ATTEN_PUSC_1_1_LOW while Attenuator 3 is set to ATTEN_PUSC_1_1_HIGH
5)
MS2 is the victim MS seeing high interference in the PUSC 1/1 zone. Attenuator 2 is set to
ATTEN_PUSC_1_3_LOWA and Attenuator 4 is set to PUSC_1_3_LOWB
Note 1: ATTEN_PUSC_1_1_LOW, ATTEN_PUSC_1_1_HIGH, ATTEN_PUSC_1_3_LOWA and
ATTEN_PUSC_1_3_LOWB are values selected by the BS vendor of the device under test.
Test process
1)
2)
3)
4)
5)
6)
7)
Start the monitor message capture, if available.
Switch on the MSs (MS1 only in case the MS is the IUT)
Carry out the Network Entry procedure with a randomly selected preamble sequence.
Carry out 1 DL and 1 UL BS initiated BE service flow.
Ensure that BS allocates PUSC with all sub carriers to MS1 and Segmented PUSC to MS2
Carry out DL and UL data transfer via freestyle BE (such as FTP) data transfer (10 minute
transfer for some stability evaluation).
During data transfer process, change settings of Attenuators 1-4 such that:
Attenuator1 == ATTEN_PUSC_1_3_LOWA
Attenuator2 == ATTEN_PUSC_1_1_LOW
Attenuator3 == ATTEN_PUSC_1_3_LOWB
Attenuator4 == ATTEN_PUSC_1_1_HIGH
Or trigger (Table 7.1 / item 26) for MS 2 (only if the BS is the IUT)
and trigger (Table 7.1 / item 27) for MS 1
Note 1. This step is designed to make MS1 the victim of interference in the PUSC 1/1 zone
and MS2 to receive a high CINR in the PUSC 1/1 zone.
Note 2. Above change in settings of attenuators are just one possible example of trigger
for the BS to move the MSs between FFR zones; the BS vendor can specify other
conditions to trigger the BS.
Pass verdict
criterion
8) BS allocates PUSC 1/3 to MS1 and PUSC 1/1 to MS2.
9) Turn off the BS, and all MSs.
Successful exchange of Ping Traffic without any ping loss and DL/UL data transfer without traffic
dropping to “0” during FTP transfer.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Page - 163
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
BS2
BS1
Interferer
Att2
Att3
Att1
Att4
Splitter/
Combiner
Tx/Rx
Rx
MS1
Splitter/
Combiner
Rx
Tx/Rx
MS2
(present if
the BS if the
IUT)
FFR Measurements Setup
Figure 2 Diagram for Testing Basic FFR
Att 1: Pair of attenuators between BS 1 and the combiner of MS 1
Att 2: Pair of attenuators between BS 1 and the combiner of MS 2
Att 3: Pair of attenuators between BS 2 and the combiner of MS 1
Att 4: Pair of attenuators between BS 2 and the combiner of MS 2
Page - 164
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
8.33.1 Capabilities Negotiation
Test Description
Identifier:
TD_SC2N0_FFR_SBC_0
Description:
Verify the successful completion of basic capabilities negotiation.
Pre-test
conditions:
Successful completion of initial ranging.
Step
Test Sequence
Result
1
MS sends 1 or more SBC-REQ
OK
NOK
2
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
with its capabilities set to on.
Are TLVs defined appropriate to the device capabilities?
BS sends SBC-RSP
OK
NOK
-
With valid TLVs that are present in the SBC-REQ appropriate for the
Wave capabilities,
and with values that do not enable a feature disabled/not supported by
MS.
Observations
8.33.2 Registration
Test Description
Identifier:
TD_SC2N0_FFR_REG_00
Description:
Verify the successful completion of registration.
Pre-test
conditions:
Successful completion of basic capabilities negotiation.
Step
Test Sequence
Result
1
MS sends 1 or more REG-REQ
OK
NOK
2
not more than PIC_MAX_REG_REQ_RETRIES of REG-REQs,
including valid TLVs defined for the appropriate Wave.
BS sends REG-RSP
OK
NOK
-
with response set to OK.
with valid TLVs that are present in the REG-REQ are in the appropriate
Wave,
and with values that do not enable a feature disabled/not supported by
MS.
Observations
Page - 165
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.33.2.1
WMF-T25-003-R010v08
Traffic Connection Establishment
8.33.2.1.1 Service Flow Provisioning
Test Description
Identifier:
TD_SC2N0_FFR_DSx_00
Description:
Verify the successful completion of service flow establishment as in the table RLC_DSA_List_1 below.
Pre-test
conditions:
Successful completion of registration and 1 DL (BE) and UL (BE) Service Flows are Pre-Provisioned at
the BS for this MS and the MS can support the Pre-Provisioned Service Flows.
Step
Test Sequence
Result
1
BS sends 1 DSA-REQ for each MS service flow,
OK
NOK
2
not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs.
MS sends 1 or more DSA-RSP for each MS service flows
OK
NOK
3
not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs.
BS sends DSA-ACK for each DSA_RSP
OK
NOK
-
Confirmation Code set to OK.
Observations
RLC_DSA_List_1
Nr.
Stimulate the BS to use the following parameters
Status
Run
UL DSA-REQ
1
Service Flow Scheduling Type set to BE
m
Yes/No
m
Yes/No
DL DSA-REQ
2
Service Flow Scheduling Type set to BE
Page - 166
WiMAX FORUM PROPRIETARY
Result
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.33.2.2
WMF-T25-003-R010v08
Zone Indication for PUSC with all Sub-channels and Segmented PUSC
8.33.2.2.1 DL and UL Zone Switch IE for PUSC with all Sub-Channels
Test Description
Identifier:
TD_SC2N0_FFR_DSx_01
Description:
Verification of DL Switch IE for PUSC with all Sub-Channel. Optionally verify the UL Switch IE for PUSC
with all Sub-Channels.
Pre-test
conditions:
MS connected to the BS with 1 pair of BE service flows.
Step
1
2
Test Sequence
-
-
BS allocates STC DL Zone IE in DL-MAP with following parameters
o
Permutation : PUSC permutation
o
Use All SC: “1” Use all Subchannels
o
STC: “0b01” STC using 2/3 antennas
o
Matrix Indicator: “0b00 or 0b01”
o
DL_Permbase: “any value”
o
PRBS_ID: “any value between 0,1,2” not coinciding with any zone
in the same DL sub-frame
BS optionally allocates OFDMA UL Zone IE in UL-MAP with following
parameters (This is unnecessary if the BS does not use segmented PUSC
in the uplink)
o
Permutation : PUSC permutation
o
Use All SC: “1” Use all Subchannels
o
UL_Permbase: “any value”
Observations
Page - 167
WiMAX FORUM PROPRIETARY
Result
OK
NOK
OK
NOK
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
8.33.2.3
WMF-T25-003-R010v08
User Data Transfer
8.33.2.3.1 File Data Transfer for BE service flows
Test Description
Identifier:
TD_SC2N0_FFR_DAT_00
Description:
Verify the successful completion of file data transfer for 10 minutes.
Pre-test
conditions:
1 UL and 1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number. The File transfer application is performed on BE service flows
Attenuators setting to configure MS1 as the victim of interference in the PUSC 1/1 zone
Attenuator1 == ATTEN_PUSC_1_1_LOW
Attenuator2 == ATTEN_PUSC_1_3_LOWA
Attenuator3 == ATTEN_PUSC_1_1_HIGH
Attenuator4 == ATTEN_PUSC_1_3_LOWB
Attenuators setting to configure MS2 as the victim of interference in the PUSC 1/1 zone
Attenuator1 == ATTEN_PUSC_1_3_LOWA
Attenuator2 == ATTEN_PUSC_1_1_LOW
Attenuator3 == ATTEN_PUSC_1_3_LOWB
Attenuator4 == ATTEN_PUSC_1_1_HIGH
Step
Test Sequence
Result
1
BS allocates data for MS1 in the zone defined for use of all sub-carriers.
OK
NOK
2
Has the data from the MS1 to the BS been transferred correctly?
OK
NOK
3
Has the data from the BS to the MS1 been transferred correctly?
OK
NOK
4
When MS2 is the victim of interference in the PUSC 1/1 zone, BS allocates data
for MS2 in the zone defined for PUSC 1/3 in at least 75% of the frames. (This is
mandatory in the DL for all BS under test. This is an optional test in the UL for
only BSs configured with UL segmented PUSC)
OK
NOK
5
Has the data from the MS2 to the BS been transferred correctly?
OK
NOK
6
Has the data from the BS to the MS2 been transferred correctly?
OK
NOK
7
When MS1 is the victim of interference in the PUSC 1/1 zone, BS allocates data
for MS2 in the zone defined for PUSC 1/1 in at least 75% of the frames.
OK
NOK
8
Has the data from the MS2 to the BS been transferred correctly?
OK
NOK
9
Has the data from the BS to the MS2 been transferred correctly?
OK
NOK
Observations
Page - 168
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
9. Mobile IOT Amendment
9.1
Amendment References
The following references are supporting documents for this document.
[1] WiMAX Forum Mobile Certification Profile, v1.1.0, Dec. 2008.
[2] WiMAX Forum Mobile System Profile, v1.7.1, Nov. 2008.
[3] WiMAX Forum Mobile PICS, v1.5.1, Sep. 2008.
[4] WiMAX Forum Mobile SRD (Standard Reference Document, v1.1.1 or its latest version)
http://members.wimaxforum.org/apps/org/workgroup/twg/download.php/38518/latest
[5] WiMAX Forum® Mobile InterOperability Test (MIOT) Release 1.0 Approved Specification (Revision 2.3.1),
Oct. 2008.
9.2
9.2.1
Amendment Definitions and abbreviations
Definitions
Center Frequency: The midpoint of the transmitted signal, specifically the frequency of the DC subcarrier
(subcarrier number Nfft/2 for any given FFT size Nfft).
Expected Behavior: Expected result of a test, stimulus or other measurement on/from a device or SUT that is
claiming to be conformant to [1] and [2].
Interoperability: The ability of systems or units to provide services and messages to and accept services and
messages from other systems, units or forces and to use the services so exchanged to enable them to operate
effectively together.
Invalid Behavior: Tests that handle invalid signaling and exchanges of messages which are not properly structured
and/or correctly encoded. These types of test are sometimes referred to as ‘negative tests’. Standards conformant
devices should never generate these types of messages or exchanges, however it is important to evaluate how
implementations respond to such stimulus.
Monitoring device: Mobile WiMAX® Analyzer and/or VSA necessary to realize whether the SUTs are working
properly or not. Details on the specific tools needed for each test case are outlined in the corresponding test
procedure descriptions.
Mobile IOT amendment: A gathering of vendors who are seeking (or intend to seek) WiMAX Forum®
Certification for their equipment. The event allows the vendors the opportunity in an open environment to test for
interoperability. The event is technical and the results not made public. It does not in any way imply that a product
has undergone certification testing and in no way is it certified.
Page - 169
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Quality of Service: Set of mechanisms employed by a BS to comply with the quality requirements set for each of
the service flows established with all the MSs that have been registered with it.
System Under Test (SUT): It is the subject of the test. It consists on the combination of zero to three MSs and one
BS.
Test purpose: Non-formal high-level description of a test, mainly using text. This test description can be used as the
basis for a formal test specification
Valid Behaviour: Tests that handle valid signaling and exchanges of messages which are properly structured and
correctly encoded.
Page - 170
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
9.2.2
WMF-T25-003-R010v08
Abbreviations
For the purposes of the present document, the following abbreviations apply:
BS
Base Station
BE
Best Effort (Service)
CC
Convolutional Coding
CDMA Code Division Multiple Access
CLI
Command Line Interface
CQICH Channel Quality Indicator Channel
CTC
Convolutional Turbo Coding
DCD
Downlink Channel Descriptor
DL
DownLink
DLFP
DownLink Frame Prefix
DSA
Dynamic Service Addition
DSD
Dynamic Service Deletion
FCH
Frame Control Header
FFT
Fast Fourier Transform
FUSC
Full Usage SubChannels
MAP
Media Access Protocol
MIR
Maximum Information Rate
MS
Mobile Station
PICS
Protocol Implementation Conformance Statement
PS
Physical Slot
PRBS
Pseudo Random Binary Sequence
PUSC
Partial Usage SubChannels
QoS
Quality of Service
QPSK
Quadriture Phase-Shift Keying
RTG
Receive/Transmit Transmission Gap
SBC
Negotiate Basic Capabilities
SS
Subscriber Station
SUT
System Under Test
TDD
Time Division Duplex
TP
Test Purpose
TTG
Transmit/Receive Transmission Gap
UCD
Uplink Channel Descriptor
UGS
Unsolicited Grant Service
UL
UpLink
Page - 171
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
VSA
9.3
WMF-T25-003-R010v08
Vector Signal Analyzer
Suggested Common System Mobile IOT amendment Profiles
The certification profile available for this Mobile IOT amendment will be only the one outlined in the table below:
9.3.1
Band Class
Index
Frequency Range
Channel Frequency
Step
Channel
Bandwidth(s)
FFT Size
Duplexing
Mode
MP05(3A)
2.496-2.69 GHz
250 KHz
5 MHz / 10 MHz
512 / 1024
TDD
TDD Frame Format
Preferred DL/UL ratio: 29/18.
Frame duration = 5ms.
9.3.2
MAP Types
Encoding
Encoding is QPSK ½ and CTC
or QPSK ½ and CC.
Type
Regular (Uncompressed) or Compressed
The symbol offset specified in the information element will count the first symbol (preamble) as zero.
The subchannel offset zero specifies the first subchannel.
9.3.3
Convergence Sub-layer
Support IP-CS
Classification Rule will be the IP Destination Address/Port Number if it is not stated differently in the test cases.
Classification rule with only classification rule index is also acceptable in the test cases.
9.3.4
IP Address Configuration
Page - 172
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
The MS shall support DHCP, and the DHCP server functionality shall be provided by an Application Serving Node.
BS Vendors need to bring their own DHCP server.
9.3.5
Test Structure
The Mobile IOT amendment testing flow and structure is described in the MIOT [5] document.
9.3.6
Test Configurations
The following testing configurations are used in the Mobile IOT amendment. Actual use will depend upon vendor
preference and capability.
Devices in each SUT shall be interconnected by wired means. In the following figures, circles with a cross represent
the set of items (splitters, attenuators, etc.) needed to interconnect all the devices when performing wired testing.
The SUT in each of the figures should contain the WiMAX Profile PHY, MAC as well as contain the capability to
control the UUT and send and receive data. A monitor station may be included to help verify specific details of
frame transfer.
9.3.6.1
Single BS and Single MS – One Vendor
BS1
MS1
Figure 9.1 One BS and One MS - Same Vendor
Page - 173
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
In the Figure 9.1 One BS and One MS - Same Vendor test configuration, a single BS1 is connected to a single MS1.
The BS1 and MS1 are from the same vendor. This is generally the initial test configuration for all vendors prior to
engaging in interoperability testing to verify the operation of their own equipment. Vendors without both a BS and
an MS, will not be able to run this test and will move to other testing.
9.3.6.2
Single BS and Single MS – Two Vendors
BS1
MS2
Figure 9.2 One BS1 and One MS2 - Different Vendors
In the Figure 9.2 One BS1 and One MS2 - Different Vendors test configuration, a single BS is connected to a single
MS. The BS1 and MS2 are from different vendors.
Page - 174
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
9.3.6.3
WMF-T25-003-R010v08
Single BS and Two MS (from Same Vendor)
BS1
MS2
MS2
Figure 9.3 One BS and Two MS (same vendor)
In Figure 9.3 One BS and Two MS (same vendor) test configuration a single BS1 is connected to two MS2. The
two MS2s are from the same vendor but different vendor than the BS1.
9.3.6.4
Single BS and Two MS (From Different Vendors)
Page - 175
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
BS1
MS1
MS2
Figure 9.4 Test Configuration One BS and Two MS (Different Vendors)
In Figure 9.4 Test Configuration One BS and Two MS (Different Vendors) this test configuration a single BS1 is
connected to two MSs. The two MSs are from the different vendors. One of the MS vendors may also be the BS
vendor (as shown) depending on equipment availability. Of course, all three UUT may be from different vendors.
9.3.6.5
Single BS and Three MS (Three Different Vendors)
BS1
BS1
MSa
MSc
MSb
Page - 176
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Figure 9.5 Test Configuration One BS and Three MS
In the test configuration in Figure 9.5 Test Configuration One BS and Three MS a single BS is connected to three
MSs. Each of the MS’s may be from different vendors, or two MS’s may be from the same vendor or one of the MS
could be from the same BS1 vendor, depending on test availability at the Mobile IOT amendment.
9.3.6.6
Single MS and Two BS (for Handover)
Simple Handover Scenario can run without interaction between the two BSs.
BS1
BS1
Link 1
Link 2
MSa
Figure 9.6 Basic Test Configuration for Handover
In Figure 7.6 a single MS unit is connected to two BS units. Both BS units shall be from the same vendor, and may
be different sectors on the same station. The MS unit may be from any MS vendor (a), and the setup shall be
validated with a MS unit provided or recommended by vendor 1. Handover will be effected by sequentially adding
attenuation to the RF links to decrease the signal strength and imbalance the signals received by the BS unit.
9.3.7
Test Scenarios
The test scenarios, listed below, follow the MIOT document, except where noted.
The initial SF configuration for all tests is 1 DL BE and 1 UL BE if some other SF type is required in one of the test
scenarios then it will be provisioned additionally to the initial SF configuration.
We recommend that every MS vendor or the test house in case of BS testing will provide 4 MS. 2 MS can be
provisioned with BE (1 DL BE and 1 UL BE) only. And 2 MS can be provisioned with BE (1 DL BE and 1 UL BE)
Page - 177
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
and UGS (1 DL UGS and 1 UL UGS). Then they can exchange the 2 MSs for tests also requiring UGS instead of
touching the SF provisioning if there are 4 MS available.
9.3.7.1
PHY Tests
9.3.7.1.1 Number of OFDM Symbols in DL / UL
Test scenario behaviour
Identifier
Ref
M2_35DL_12UL_BSC _01
Basic Configuration
Goal
Verify the exchange of Ping Traffic and User Data Transfer.
Configuration
Basic Test Configuration for IOT Testing.
Test Condition
-
TX Power Level:
o MS: controlled by power control algorithm; typically at maximum power
o
BS: medium
-
Initial State
TPC mode: Open loop
DL/UL Ratio: 29:18
ARQ: Enabled
HARQ: Enabled
If the MS and BS have WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
- DL 2-antenna STC matrix A and B: Enable. {Switchable between A and B}
- DL zone type. PUSC w/all subchannels.
- UL Single-antenna Collaborative SM: enable.
- UL zone type. PUSC.
- CQI Channel for physical CINR Feedback measured on Preamble: Enable.
- Size of CQICH_ID field: 3bits, 6 bits, or 8 bits
- Corrigendum 2 support: yes
- Compressed MAP: yes
- 1 UL and 1 DL BE Service Flows established.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Test process
1) Start the monitor message capture, if available.
2) Switch on the MSs.
3) Carry out the Network Entry procedure with a randomly selected preamble sequence.
4) Carry out 1 DL and 1 UL BS initiated BE service flow.
5) Carry out DL and UL data transfer
a) via the PING procedure: Host behind the BS pings the host behind the MS. Host behind the
MS pings the host behind the BS
b) via freestyle BE UDP data transfer (5 minute transfer for some stability evaluation).
6) Turn off the BS, and all MSs.
Pass verdict
criterion
Successful exchange of Ping Traffic and DL/UL data transfer. Successful DL/UL data transfer means
packet error rate less than 0.5 percent at 500kbit/sec.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
Page - 178
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
9.3.7.1.1.1
WMF-T25-003-R010v08
Network Entry procedure
9.3.7.1.1.1.1
MS Synchronization and Ranging
Test Description
Identifier
Description
M2_35DL_12UL_IRNG_01
Verify that a BS sends broadcast messages (DL-MAP, UL-MAP, UCD, DCD) when switched on and
that MS synchronizes with the BS. Verify the successful completion of initial ranging.
Pre-test
conditions
MS is deregistered from BS. MS is switched off. BS remains on. BS is configured to transmit in the
lowest channel (fL). Then MS is switched on.
Step
Test Sequence
Result
1
BS sends DL-MAP in every frame.
OK
NOK
2
BS sends UL-MAP if appropriate.
OK
NOK
3
BS sends DCD every ten second(max).
OK
NOK
4
BS sends UCD every ten second(max).
OK
NOK
5
MS synchronizes to the BS.
OK
NOK
6
MS sends initial CDMA ranging codes in the Initial Ranging Region.
OK
NOK
7
BS sends RNG-RSP
OK
NOK
OK
NOK
OK
NOK
OK
NOK
OK
NOK
-
with optional Power, Time or Frequency adjustments.
with ranging status = continue or success
If the Ranging Status = continue in Step 7, MS sends initial CDMA ranging
code in the Periodic Ranging Region until receiving:
-
8
-
RNG-RSP (with Ranging Status = success),
or CDMA_Allocation_IE in UL-MAP
BS sends
-
9
-
10
11
RNG-RSP (with Ranging Status = success) followed by
CDMA_Allocation_IE,
- or CDMA_Allocation_IE only.
MS sends RNG-REQ.
Fill the gap with the MS MAC address read in the RNG-REQ and determine
MAC Address.
MS MAC address:
12
BS sends RNG-RSP with ranging status = success.
OK
NOK
13
Fill the gap with the Basic Cid and Primary Management Cid assigned to the
MS in the RNG-RSP.
OK
NOK
Basic CID:
Prim CID:
Observations
Page - 179
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
9.3.7.1.1.1.2
Capabilities Negotiation
Identifier
M2_35DL_12UL_SBC_01
Verify the successful completion of basic capabilities negotiation.
Test Description
Description
Pre-test
conditions
Successful completion of initial ranging.
Step
Test Sequence
1
MS sends 1 or more SBC-REQ
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
with its capabilities set to on.
- Are TLVs defined appropriate to the device capabilities?
BS sends SBC-RSP
Result
OK
NOK
OK
NOK
-
2
-
With valid TLVs that are present in the SBC-REQ appropriate for the
Wave capabilities,
and with values that do not enable a feature disabled/not supported by MS.
Observations
9.3.7.1.1.1.3
Registration
Test Description
Identifier
Description
Pre-test
conditions
Step
M2_35DL_12UL_NAUTH_01
Verify the successful completion of registration.
Successful completion of basic capabilities negotiation.
Test Sequence
Result
1
MS sends 1 or more REG-REQ
OK
NOK
2
- not more than PIC_MAX_REG_REQ_RETRIES of REG-REQs,
- including valid TLVs defined for the appropriate Wave.
BS sends REG-RSP
OK
NOK
-
with response set to OK.
with valid TLVs that are present in the REG-REQ are in the appropriate
Wave,
and with values that do not enable a feature disabled/not supported by MS.
Observations
9.3.7.1.1.2
9.3.7.1.1.2.1
Traffic Connection Establishment
Service Flow Provisioning
Test Description
Identifier
M2_35DL_12UL_SRV_FLW_01
Page - 180
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Description
Verify the successful completion of service flow establishment as in the table RLC_DSA_List_5 below
Pre-test
conditions
Successful completion of registration and 1 DL (BE) and UL (BE) Service Flows are Pre-Provisioned at
the BS for this MS and the MS can support the Pre-Provisioned Service Flows.
Step
Test Sequence
Result
1
BS sends 1 DSA-REQ for each MS service flow
OK
NOK
2
- not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs.
MS sends 1 or more DSA-RSP for each MS service flows
OK
NOK
3
- not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs.
BS sends DSA-ACK for each DSA_RSP
OK
NOK
-
Confirmation Code set to OK.
Observations
RLC_DSA_List_5
Stimulate the BS to use the following parameters
No
Status
Run
m
Yes/No
m
Yes/No
Result
UL DSA-REQ
1
Service Flow Scheduling Type set to BE
DL DSA-REQ
2
Service Flow Scheduling Type set to BE
9.3.7.1.1.3
User Data Transfer
9.3.7.1.1.3.1
PING for BE service flows
Test Description
Identifier
Description
M2_35DL_12UL_DAT_01
Verify the successful completion of data transfer via the PING procedure.
Pre-test
conditions
1 UL and 1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number. The Ping application is performed on BE service flows
Step
1
Test Sequence
Host behind the BS pings the host behind the MS.
NOK
OK
NOK
-
2
The CID of the DL MAC PDU (EchoRequest) is the Transport Cid of the
DL Service Flow.
- The CID of the UL MAC PDU (EchoReply) is the Transport Cid of the UL
Service Flow.
- Is the PING procedure successfully completed?
Host behind the MS pings the host behind the BS.
Result
OK
-
The CID of the UL MAC PDU (EchoRequest) is the Transport Cid of the
UL Service Flow.
The CID of the DL MAC PDU (EchoReply) is the Transport Cid of the DL
Service Flow.
Is the PING procedure successfully completed?
Observations
Page - 181
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
9.3.7.1.1.3.2
WMF-T25-003-R010v08
File Data Transfer for BE service flows
Test Description
Identifier
Description
M2_35DL_12UL_DAT_TRF_01
Verify the successful completion of file data transfer for 2 minutes.
Pre-test
conditions
1 UL and 1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number. The File transfer application is performed on BE service flows
Step
Test Sequence
Result
1
Has the data from the MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to the MS been transferred correctly?
OK
NOK
Observations
9.3.7.1.2 DL Subcarrier Allocation
Test scenario behaviour
Identifier
Ref
M3_DL_SC_ALLOC_BSC_01
Basic Configuration
Goal
Verify the exchange of Ping Traffic and User Data Transfer.
Configuration
Basic Test Configuration for IOT Testing.
Test Condition
-
TX Power Level:
o MS: controlled by power control algorithm; typically at maximum power
o
BS: medium
-
Initial State
TPC mode: Open loop
DL/UL Ratio: 29:18
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
- DL 2-antenna STC matrix A and B: Enable. Switchable between A and B
- DL zone type. Segmented PUSC
- For the segment to be used, BS will select two of major groups by its own scheme implemented.
Only one sector is to be tested.
- UL Single-antenna Collaborative SM: enable.
- UL zone type: PUSC.
- CQI Channel for physical CINR Feedback measured on Preamble: Enable.
- Size of CQICH_ID field: 3bits, 6 bits, or 8 bits
- Corrigendum 2 support: yes
- Compressed MAP: yes
- 1 UL and 1 DL BE Service Flows established.
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Test process
1) Start the monitor message capture, if available.
2) Switch on the MSs.
3) Carry out the Network Entry procedure with a randomly selected preamble sequence.
Page - 182
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
4) Carry out 1 DL and 1 UL BS initiated BE service flow.
5) Carry out DL and UL data transfer
a) via the PING procedure: Host behind the BS pings the host behind the MS. Host behind the
MS pings the host behind the BS
b) via freestyle BE UDP data transfer (5 minute transfer for some stability evaluation).
6) Turn off the BS, and all MSs.
Pass verdict
criterion
Successful exchange of Ping Traffic and DL/UL data transfer. Successful DL/UL data transfer means
packet error rate less than 0.5 percent at 500kbit/sec.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
9.3.7.1.2.1
Network Entry procedure
9.3.7.1.2.1.1
MS Synchronization and Ranging
Test Description
Identifier
Description
M3_DL_SC_ALLOC_IRNG_01
Verify that a BS sends broadcast messages (DL-MAP, UL-MAP, UCD, DCD) when switched on and
that MS synchronizes with the BS. Verify the successful completion of initial ranging.
Pre-test
conditions
MS is deregistered from BS. MS is switched off. BS remains on. BS is configured to transmit in the
lowest channel (fL). Then MS is switched on.
Step
Test Sequence
Result
1
BS sends DL-MAP in every frame.
OK
NOK
2
BS sends UL-MAP if appropriate.
OK
NOK
3
BS sends DCD every ten second(max).
OK
NOK
4
BS sends UCD every ten second(max).
OK
NOK
5
MS synchronizes to the BS.
OK
NOK
6
MS sends initial CDMA ranging codes in the Initial Ranging Region.
OK
NOK
7
BS sends RNG-RSP
OK
NOK
OK
NOK
OK
NOK
OK
NOK
OK
NOK
-
with optional Power, Time or Frequency adjustments.
with ranging status = continue or success
If the Ranging Status = continue in Step 7, MS sends initial CDMA ranging
code in the Periodic Ranging Region until receiving:
-
8
-
RNG-RSP (with Ranging Status = success),
or CDMA_Allocation_IE in UL-MAP
BS sends
-
9
-
10
11
RNG-RSP (with Ranging Status = success) followed by
CDMA_Allocation_IE,
- or CDMA_Allocation_IE only.
MS sends RNG-REQ.
Fill the gap with the MS MAC address read in the RNG-REQ and determine
MAC Address.
MS MAC address:
Page - 183
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
12
BS sends RNG-RSP with ranging status = success.
OK
NOK
13
Fill the gap with the Basic Cid and Primary Management Cid assigned to the
MS in the RNG-RSP.
OK
NOK
Basic CID:
Prim CID:
Observations
9.3.7.1.2.1.2
Capabilities Negotiation
Test Description
Identifier
M3_DL_SC_ALLOC_SBC_01
Verify the successful completion of basic capabilities negotiation.
Description
Pre-test
conditions
Successful completion of initial ranging.
Step
Test Sequence
1
MS sends 1 or more SBC-REQ
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
with its capabilities set to on.
- Are TLVs defined appropriate to the device capabilities?
BS sends SBC-RSP
Result
OK
NOK
OK
NOK
-
2
-
With valid TLVs that are present in the SBC-REQ appropriate for the
Wave capabilities,
and with values that do not enable a feature disabled/not supported by MS.
Observations
9.3.7.1.2.1.3
Registration
Test Description
Identifier
Description
Pre-test
conditions
Step
M3_DL_SC_ALLOC_NAUTH_01
Verify the successful completion of registration.
Successful completion of basic capabilities negotiation.
Test Sequence
Result
1
MS sends 1 or more REG-REQ
OK
NOK
2
- not more than PIC_MAX_REG_REQ_RETRIES of REG-REQs,
- including valid TLVs defined for the appropriate Wave.
BS sends REG-RSP
OK
NOK
-
with response set to OK.
with valid TLVs that are present in the REG-REQ are in the appropriate
Wave,
and with values that do not enable a feature disabled/not supported by MS.
Page - 184
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Observations
9.3.7.1.2.2
Traffic Connection Establishment
9.3.7.1.2.2.1
Service Flow Provisioning
Test Description
Identifier
Description
M3_DL_SC_ALLOC_SRV_FLW_01
Verify the successful completion of service flow establishment as in the table RLC_DSA_List_6 below
Pre-test
conditions
Successful completion of registration and 1 DL (BE) and UL (BE) Service Flows are Pre-Provisioned at
the BS for this MS and the MS can support the Pre-Provisioned Service Flows.
Step
Test Sequence
Result
1
BS sends 1 DSA-REQ for each MS service flow
OK
NOK
2
- not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs.
MS sends 1 or more DSA-RSP for each MS service flows
OK
NOK
3
- not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs.
BS sends DSA-ACK for each DSA_RSP
OK
NOK
-
Confirmation Code set to OK.
Observations
No
RLC_DSA_List_6
Stimulate the BS to use the following parameters
Status
Run
Result
m
Yes/No
m
Yes/No
UL DSA-REQ
1
Service Flow Scheduling Type set to BE
DL DSA-REQ
2
9.3.7.1.2.3
Service Flow Scheduling Type set to BE
User Data Transfer
9.3.7.1.2.3.1
PING for BE service flows
Test Description
Identifier
Description
M3_DL_SC_ALLOC_DAT_01
Verify the successful completion of data transfer via the PING procedure.
Pre-test
conditions
1 UL and 1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number. The Ping application is performed on BE service flows
Step
1
Test Sequence
Host behind the BS pings the host behind the MS.
-
The CID of the DL MAC PDU (EchoRequest) is the Transport Cid of the
DL Service Flow.
The CID of the UL MAC PDU (EchoReply) is the Transport Cid of the UL
Page - 185
WiMAX FORUM PROPRIETARY
Result
OK
NOK
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Service Flow.
Is the PING procedure successfully completed?
Host behind the MS pings the host behind the BS.
-
2
-
OK
NOK
The CID of the UL MAC PDU (EchoRequest) is the Transport Cid of the
UL Service Flow.
The CID of the DL MAC PDU (EchoReply) is the Transport Cid of the DL
Service Flow.
Is the PING procedure successfully completed?
Observations
9.3.7.1.2.3.2
File Data Transfer for BE service flows
Test Description
Identifier
Description
M3_DL_SC_ALLOC_DAT_TRF_01
Verify the successful completion of file data transfer for 2 minutes.
Pre-test
conditions
1 UL and 1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number. The File transfer application is performed on BE service flows
Step
Test Sequence
Result
1
Has the data from the MS to the BS been transferred correctly?
OK
NOK
2
Has the data from the BS to the MS been transferred correctly?
OK
NOK
Observations
9.3.7.1.3 Periodic Ranging
9.3.7.1.3.1
Periodic Ranging Scenario 1
Test scenario behaviour
Identifier
ID_MS_PRNG_01
Ref
P80216_Cor2_D3.pdf
802.16-2004.pdf
802.16e-2005.pdf
Goal
The MS should perform periodic ranging according to a well-defined state machine. When
there is UL traffic, the MS should not perform periodic ranging unless instructed by the BS.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
1 BS and 1 MS
TX Power Level:
BS: medium
MS: controlled by power control algorithm
-
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA
Page - 186
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
server is available then authentication should be enabled.
1 BE DL Service Flow is Pre-provisioned at the BS for this MS. In addition, 1 BE UL
Service Flow is Pre-provisioned at the BS for this MS.
- Service Flow Classification Rules: Based on source/destination IP address.
- Type of map used: Compressed map
1) MS completed network entry with the BS
-
Initial State
2) A traffic generator is generating a steady stream of UL traffic for UL BE1.
Test process
Described in Fig. 90 in P80216_Cor2_D3.pdf.
1) A traffic generator is started after network entry, creating a steady stream of UL traffic
classified onto UL BE1.
2) The MS resets the periodic ranging timer T4 upon each data grant, and so T4 never
expires.
3) The MS does not initiate periodic ranging. PR can only be initiated by unsolicited BS
RNG-RSP with status Continue.
The MS vendor must indicate what values of T3 and T4 are used. Once the traffic generator
has started, the BS should not detect any PR codes unless it sends an unsolicited RNG-RSP
with status Continue. The test conditions are such that the BS should not send an unsolicited
RNG-RSP with status Continue.
Pass verdict
criterion
Final Verdict
PASS
FAIL
Notes
1) The test results will be verified based on BS logs.
2) The test should be run long enough to include at least 2 potential PR cycles. T4 is
required to be at most 35 seconds, so the test period can be set to 70 seconds.
9.3.7.1.4 BW Request
9.3.7.1.4.1
UGS Service Flow
Test scenario behaviour
Identifier
ID_BW_REQ_UGS_01
Ref
802.16 Cor 2 Draft 3
802.16e-2005
802.16-2004
Goal
Verify correct operation of Bandwidth request and allocation mechanism over UGS
service flows.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
-
1 BS and 1 MS
TX Power Level:
BS: medium
MS: controlled by power control algorithm
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA
server is available then authentication should be enabled.
1 DL UGS service flow and 1 UL UGS service flow are pre-provisioned at the BS for
this MS.
Page - 187
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
Initial State
Test process
Pass verdict
criterion
Final Verdict
WMF-T25-003-R010v08
- Service Flow Classification Rules: Based on IP source/destination address number.
- Type of map used: Compressed map
MS is deregistered from BS. MS is switched off. BS remains on.
1)
2)
3)
4)
5)
6)
1)
2)
Switch on the MS.
Carry out the Network Entry procedure.
Carry out BS initiated service flow provisioning procedure.
Start the monitor message capture, if available.
Perform a UDP data transfer for two minutes in the UL.
Stop the monitor message capture (if started).
File transfer is successful.
If monitor message capture is available, verify the following occurred:
a. No bandwidth request ranging codes were transmitted except for the exchange of
management messages.
b. There are no Bandwidth Request Headers containing a CID assigned to an UL
UGS SF.
c. A Grant Management Subheader (GMSH) may be sent with the UL UDP data
traffic. The GMSH may have the SI, FLI, FL bits set as determined by the MS.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
9.3.7.1.5 CQICH Fast Feedback
9.3.7.1.5.1
BS initiated CQI Reporting using Fast Feedback Channel
Test scenario behaviour
Identifier
ID_BS_CQI_FFC_01
Description
BS initiated CQI Reporting using Fast Feedback Channel.
Goal
Verify the Fast Feedback Channel Allocation of the BS and Fast Feedback Reporting of the
MS during DL data transfer.
Configuration
Basic Test Configuration for IOT Testing.
Test
-
Condition
TX Power Level:
o MS: controlled by power control algorithm; typically at maximum power
o
-
BS: medium
TPC mode: Open loop
DL 2-antenna STC matrix A: Disable.
DL zone type. PUSC.
UL Single-antenna Collaborative SM: Disable.
UL zone type. PUSC.
CQI Channel for physical CINR Feedback measured on Preamble: Enable.
Size of CQICH_ID field: 3bits, 6 bits, or 8bits
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA
server is available then authentication should be enabled.
Corrigendum 2 support: yes
Compressed MAP: yes
1 DL BE Service Flows established.
Service Flows Classification Rule: Based on IP address/port number.
Page - 188
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Initial State
MS is deregistered from BS. MS is switched off. BS remains on.
Test process
1) Start the monitor message capture. This is the only scenario that needs a monitor in
order to check that MS sends CINR report headers.
2) Switch on the MS.
3) Carry out the Network Entry procedure with CQI Reporting support.
4) Carry out 1 DL BS initiated BE service flow.
5) BS allocates Fast feedback channel for MS.
6) Carry out DL data transfer with enhanced fast feedback activated (BS assigns a CQI
channel), via freestyle BE UDP data transfer (5 minute transfer for some stability
evaluation).
Successful DL data transfer (Successful data transfer means packet error rate less than 0.5
percent at 500kbit/sec.) with enhanced fast feedback activated; MS sends CINR report
headers in the assigned fast-feedback channel.
Pass verdict
criterion
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
9.3.7.1.6 DL (Link Adaptation) based on Physical CINR Report on Pilots
Test scenario behaviour
Identifier
M2_PCINR_01
Description
BS Downlink (link adaptation) based on pilot-based PCINR measurement and report by MS
Goal
Verify the CQICH allocation of BS for PCINR report of MS and the downlink link
adaptation according to the PCINR report.
Configuration
Basic Test Configuration for IOT Testing – 1MS + 1BS
Test
-
Condition
TX Power Level:
o MS: controlled by power control algorithm; typically at maximum power
o
BS: medium
-
Initial State
Test process
TPC mode: Open loop
DL 2-antenna STC matrix A: Disable
DL 2-antenna STC matrix B: Disable
DL zone type: PUSC.
UL Single-antenna Collaborative SM: Disable.
UL zone type: PUSC.
CQI Channel for Physical CINR Feedback measured on Pilot: Enable.
Size of CQICH_ID field: 3bits, 6 bits, or 8 bits
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA
server is available then authentication should be enabled.
- Corrigendum 2 support: yes
- Compressed MAP: yes
- 1 DL BE Service Flows established.
- Service Flow Classifier without Classification Rule
MS is deregistered from BS. MS is switched off. BS remains on.
1)
2)
3)
4)
5)
6)
Start the monitor message capture.
Switch on the MS.
Carry out the Network Entry procedure with CQI Reporting support for PCINR.
Carry out 1 DL BS initiated BE service flow.
BS allocates Fast feedback channel for MS.
Carry out DL data transfer with enhanced fast feedback activated (BS assigns a CQI
Page - 189
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
channel), via freestyle BE (such as UDP) data transfer (5 minute transfer for some
stability evaluation).
7) Channel emulator and/or attenuator may be used to control the channel.
Successful DL data transfer with enhanced fast feedback activated; MS sends PCINR report
in the assigned fast-feedback channel; BS carries out link adaptation using the PCINR
reported by MS.
Pass verdict
criterion
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
9.3.7.1.6.1
Capabilities Negotiation During Network Entry Procedure
Test Description
Identifier
M2_PCINR_SBC_01
Description
Verify the successful completion of basic capabilities negotiation with Fast Feedback, PCINR,
and DL HARQ.
Pre-test
X
conditions
Step
Test Sequence
1
MS sends SBC-REQ(s)
one or more, but no more than PIC_SBC_REQ_MAX_RETRIES.
with Uplink Control Channel Support indicating enhanced fast
feedback support.
- with OFDMA MS CINR Measurement Capability indicating support
for Physical CINR measurement for a permutation zone from pilot
subcarriers.
- with OFDMA SS demodulator indicating HARQ Chase support
- with the number of DL HARQ Channels, HARQ Chase combining
Buffer Capability, and the Maximum number of burst per frame
capability in HARQ set according to the HARQ parameter set
supported
BS sends SBC-RSP
Result
OK
NOK
OK
NOK
-
2
-
with TLVs that are present in the SBC-REQ, and with values that do
not enable a feature disabled by MS,
Confirming Uplink Control Channel support.
Confirming OFDMA MS CINR measurement capability.
Confirming Downlink HARQ capability support.
Observations
9.3.7.1.6.2
PCINR Report for CQICH Allocation and Link Adaptation
Test Description
Identifier
M2_PCINR_CQICH_ALOC_DA_01
Description
Verify the fast feedback channel allocation for PCINR report, CQI feedback and the successful
completion of data transfer for 5 minutes.
Pre-test
1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number.
conditions:
Step
1
Test Sequence
BS sends DL MAP with
Result
OK
Page - 190
WiMAX FORUM PROPRIETARY
NOK
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
-
2
HARQ DL MAP IE + DL HARQ Chase Sub-Burst IE() with ACK
disable = 0.
BS sends UCD with.
OK
NOK
3
Size of the CQICH_ID field. In case of default value, the BS doesn’t
need to send the size of the CQICH_ID field.
BS sends UL-MAP with:
OK
NOK
-
-
Fast Feedback Allocation IE, allocating the fast-feedback region.
CQICH Allocation IE, allocating the fast-feedback slots.
CQICH Allocation IE indicates also how MS should measure PCINR
by setting Feedback Type to Physical, Report type to Specific
Permutation Zone, Zone permutation to PUSC with use all SC=1, Zone
type to non-STC zone, and CINR zone measurement type to Pilot
subcarriers. Major group indication should be set to zero.
If Averaging parameter included is set to 1 then Averaging parameter
should be set in the range of [1/16, 16/16] in multiples of 1/16.
MIMO_permutation_feedback_cycle should be set to 0b00.
4
- HARQ ACKCH Region Allocation IE defining an ACK region.
MS sends PCINR report as indicated in the CQICH Allocation IE.
OK
NOK
5
- using 6-bit CQI.
BS sends
OK
NOK
OK
NOK
OK
NOK
OK
NOK
OK
NOK
-
6
HARQ allocation using the MCS level selected for the link adaptation,
based on the PCINR report from the MS.
MS
-
7
decodes the DL HARQ allocation
sends ACK or NACK in the correct HARQ ACK channel.
BS
8
-
either re-sends previous blocks, if MS NACKs. The retransmission
allocation uses the same MCS and the same ACID as the previous
allocation with the AI_SN maintained.
-
or sends a new sub-burst, if MS ACKs and DL data is available for
transmission. The next allocation that uses the same ACID has the AI_SN
toggled, and may use a different MCS.
Link adaptation can be verified as follows:
-
Data throughput should increase when path attenuation is decreased
and vice versa.
Path attenuation change should be large enough to induce the BS to
change MCS. From Table 334 in the standard, path attenuation should
be increased/decreased in at least 3 dB steps.
Has the data from the BS to the MS been transferred correctly?
9
Observations
9.3.7.1.7 Downlink Modulation
9.3.7.1.7.1
Support of different MSC level in DL
Test scenario behaviour
Identifier
ID_BS_MOD_CODE_01
Page - 191
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Ref
DL Modulation and Coding Schemes
Goal
Verify the support of different MCS levels in DL
Configuration
Support different MCS levels in DL
Test Condition
-
TX Power Level:
o MS: controlled by power control algorithm; typically at maximum power
o
BS: medium
-
TPC mode: Open loop
DL 2-antenna STC matrix A: Disable.
DL zone type. PUSC.
UL Single-antenna Collaborative SM: Disable.
UL zone type. PUSC.
CQI Channel for physical CINR Feedback measured on Preamble: Enable.
Size of CQICH_ID field: 3bits, 6 bits, or 8 bits
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
- Corrigendum 2 support: yes
- Compressed MAP: yes
- Service Flows Classification Rule: Based on IP address/port number.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
1)
2)
3)
4)
5)
6)
Configure the BS in Test mode
Initialize the BS to transmit the lowest level MCS specified in
Table 1
Carry out the Network Entry procedure.
Carry out DL data transfer via freestyle BE (such as FTP) data transfer (2 minute transfer for
some stability evaluation).
7) Choose the next higher MCS level in
8)
9) Table 1
10) Repeat steps 3 to 4 for each remaining MCS level.
Successful exchange DL data transfer at each MCS level.
Pass verdict
criterion
Final Verdict
PAS
S
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
Table 1 DL MCS levels
Spectral efficiency
1/6
0.25
0.5
1
1.5
2
3
3
MCS level
QPSK1/2 repetition 6
QPSK1/2 repetition 4
QPSK1/4 repetition 2
QPSK1/2
QPSK3/4
16QAM1/2
16QAM3/4
64QAM1/2
Page - 192
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
4
4.5
5
9.3.7.1.7.1.1
64QAM2/3
64QAM3/4
64QAM5/6
Network Entry procedure
9.3.7.1.7.1.1.1
MS Synchronization and Ranging
Test Description
Identifier
ID_RLC_IRNG_01
Description
Verify that a BS sends broadcast messages (DL-MAP, UL-MAP, UCD, DCD) when switched on and
that MS synchronizes with the BS. Verify the successful completion of initial ranging.
Pre-test
conditions
MS is deregistered from BS. MS is switched off. BS remains on. BS is configured to transmit in the
lowest channel (fL). Then MS is switched on.
Step
Test Sequence
Result
1
BS sends DL-MAP in every frame.
OK
NOK
2
BS sends UL-MAP if appropriate.
OK
NOK
3
BS sends DCD every ten second(max).
OK
NOK
4
BS sends UCD every ten second(max).
OK
NOK
5
MS synchronizes to the BS.
OK
NOK
6
MS sends initial CDMA ranging codes in the Initial Ranging Region.
OK
NOK
7
BS sends RNG-RSP
OK
NOK
OK
NOK
OK
NOK
OK
NOK
OK
NOK
-
with optional Power, Time or Frequency adjustments.
with ranging status = continue or success
If the Ranging Status = continue in Step 7, MS sends initial CDMA ranging
code in the Periodic Ranging Region until receiving:
-
8
-
RNG-RSP (with Ranging Status = success),
or CDMA_Allocation_IE in UL-MAP
BS sends
-
9
-
10
11
RNG-RSP (with Ranging Status = success) followed by
CDMA_Allocation_IE,
- or CDMA_Allocation_IE only.
MS sends RNG-REQ.
Fill the gap with the MS MAC address read in the RNG-REQ and determine
MAC Address.
MS MAC address:
12
BS sends RNG-RSP with ranging status = success.
OK
NOK
13
Fill the gap with the Basic Cid and Primary Management Cid assigned to the
MS in the RNG-RSP.
OK
NOK
Basic CID:
Prim CID:
Observations
Page - 193
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
9.3.7.1.7.1.1.2
WMF-T25-003-R010v08
Capabilities Negotiation
Test Description
Identifier
ID _RLC_SBC_01
Description
Verify the successful completion of basic capabilities negotiation.
Pre-test
conditions
Successful completion of initial ranging.
Step
Test Sequence
1
MS sends 1 or more SBC-REQ
not more than PIC_SBC_REQ_MAX_RETRIES of SBC-REQs,
with its capabilities set to on.
- Are TLVs defined appropriate to the device capabilities?
BS sends SBC-RSP
Result
OK
NOK
OK
NOK
-
2
-
With valid TLVs that are present in the SBC-REQ appropriate for the
Wave capabilities,
and with values that do not enable a feature disabled/not supported by MS.
Observations
9.3.7.1.7.1.1.3
Registration
Test Description
Identifier
ID_RLC_REG_01
Description
Verify the successful completion of registration.
Pre-test
conditions
Successful completion of basic capabilities negotiation.
Step
Test Sequence
Result
1
MS sends 1 or more REG-REQ
OK
NOK
2
- not more than PIC_MAX_REG_REQ_RETRIES of REG-REQs,
- including valid TLVs defined for the appropriate Wave.
BS sends REG-RSP
OK
NOK
-
with response set to OK.
with valid TLVs that are present in the REG-REQ are in the appropriate
Wave, and with values that do not enable a feature disabled/not supported
by MS.
Observations
9.3.7.1.7.1.2
Traffic Connection Establishment
9.3.7.1.7.1.2.1
Service Flow Provisioning
Test Description
Identifier
ID_SRV_FLW_01
Description
Verify the successful completion of service flow establishment as in the table RLC_DSA_List_2 below
Pre-test
conditions
Successful completion of registration and 1 DL BE Service Flows are Pre-Provisioned at the BS for this
MS and the MS can support the Pre-Provisioned Service Flows.
Step
1
Test Sequence
BS sends 1 DSA-REQ
-
Result
OK
not more than PIC_DSx_REQ_MAX_RETRIES of DSA-REQs.
Page - 194
WiMAX FORUM PROPRIETARY
NOK
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
2
MS sends 1 DSA-RSP
OK
NOK
3
- not more than PIC_DSx_RSP_MAX_RETRIES of DSA-RSPs.
BS sends DSA-ACK
OK
NOK
-
Confirmation Code set to OK.
Observations
No
RLC_DSA_List_2
Stimulate the BS to use the following parameters
Status
Run
Result
DL DSA-REQ
1
Service Flow Scheduling Type set to BE and/or UGS
9.3.7.1.7.1.3
m
Yes/No
User Data Transfer
9.3.7.1.7.1.3.1
File Data Transfer
Test Description
Identifier
ID_FILE_DAT_TRF_01
Description
Verify the successful completion of file data transfer for 2 minutes.
Pre-test
conditions
1 DL Service Flow is established. The classification rule for mapping the CID is based on IP
address/port number. The File transfer application is performed on BE service flows
Step
1
Test Sequence
Has the data from the BS to the MS been transferred correctly?
Result
OK
Observations
9.3.7.1.8 Uplink Modulation
9.3.7.1.8.1
Verifying Uplink link adaptation
Test scenario behaviour
Identifier
M2_UL_LA_01
Ref
Uplink Link Adaptation
Goal
Verify the use of UP link adaptation during data transfer.
Configuration
Basic Test Configuration for IOT Testing.
Test Condition
-
-
Open Loop Power Control: Active
TX Power Level:
BS: medium
MS: controlled by power control algorithm
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an
AAA server is available then authentication should be enabled.
1 UL UGS and 1 DL UGS Service Flow are Pre-Provisioned at the BS for this MS
Page - 195
WiMAX FORUM PROPRIETARY
NOK
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
and the MS can support the Pre-Provisioned Service Flows. The UL UGS service
flow should provide a fixed allocation size every frame to facilitate consistent,
accurate power measurements
- Service Flows Classification Rule: Based on IP address/port number
- UL and DL attenuation are symmetric.
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test process
7) BS Force Open loop Power Control
8) Start the monitor message capture, if available.
9) Switch on the MS.
10) Carry out the Network Entry procedure with BS initiated Open Loop Power Control
Activation.
11) Carry out 1 UL and DL BS initiated UGS service flow.
12) During UL data transfer, the link attenuation is changed to test MCS changed.
13) Test with RSSI at MS range from -40dBm to -80dBm and back
Attenuation is introduced during UL data transfer and MCS is changed.
Pass verdict
criterion
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
9.3.7.1.8.1.1
Data Transfer
Test Description
Identifier
M2_UL_LA_DATA_01
Description
Verify MCS is changed adaptively with OLPC if link attenuation is changed.
Pre-test
conditions
OLPC test is passed. 1 UL and DL UGS Service Flow are established and OLPC is activated.
During User Data Transfer the link attenuation is changed.
Step
1
Test Sequence
Change link attenuation by not more than 2dB per step until average C/N and
MCS is changed at BS as per Table 334 – Normalized C/N.
Result
OK
NOK
OK
NOK
OK
NOK
Test with RSSI at MS range from -40dBm to -80dBm and back.
2
If MCS is changed at BS, verify that the changed MCS is delivered to MS
through UIUC, and that MS applied changed MCS for data transfer to BS
3
Check if the number of bytes in each allocation is kept constant, but the # of
allocated slots is changed.
-
4
If MCS is changed to higher one, then check if less number of slots is
allocated for the data transfer
- If MCS is changed to lower one, then check if high number of slots is
allocated for the data transfer
Has the data from the MS to the BS been transferred correctly with changed
MCS?
Note that error happened during the attenuator adjustment may not be counted as
error case, i.e., not an issue of pass or fail.
Observations
Page - 196
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
9.3.7.1.9 DL MIMO Mode Testing
The main purpose of this test is to verify DL MIMO modes A and B and the MIMO mode switching functionality at
BS. The test consists of two alternative scenarios depending on the BS capabilities and also depending on the
available test equipment for performing this test.
Test scenario 1:
In case that either the BS does not support MIMO mode selection feedback from the MS or in case the test setup
(i.e. fading simulator for MIMO) for stimulating the MS to send the MIMO mode selection feedback is not available
and the BS supports a possibility to trigger the MIMO mode switch from A to B (for the case that a fading simulator
is not available) then perform the following test scenario 1.
Test scenario 1 behavior
Identifier
M2_DL_MIMO_MODE_02
Ref
11.8.3.7.5, 11.8.3.7.6 [2]
Goal
Verify DL data transfer between BS and MS with Matrix A/B MIMO switching
Configuration
Basic Test Configuration for IOT Testing
Test
Condition
-
Initial State
TX Power Level: Medium
PC mode: Open loop
DL 2-antenna STC matrix A: Enable in MS and BS.
DL 2-antenna STC matrix B: Enable in MS and BS.
DL zone type. PUSC.
UL Single-antenna Collaborative SM: Disable.
UL zone type. PUSC.
CQI support: physical CINR or Effective CINR in PUSC zone.
Size of CQICH_ID field: 3bits, 6 bits, or 8 bits
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for all MSs and each MS can
support the Pre-Provisioned Service Flows.
- Service Classifier without Classification Rules
MS is deregistered from BS. MSs are switched off. BS remains on.
Test process
1) Start the monitor message capture, if available.
2) Switch on the MSs
3) Carry out the Network Entry procedure for each MS simultaneously.
4) Carry out 1 DL and 1 UL BS initiated BE service flow
5) Use setup that allows BS to prefer MIMO matrix
6) Check if BS set to MIMO matrix A
7) Carry out DL data transfer with 2-antenna STC matrix A, via freestyle BE (such as FTP) data
Page - 197
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
transfer (5 minute transfer for some stability evaluation).
8) Use setup that allows BS to prefer MIMO matrix B
9) Check if BS switched to MIMO matrix B
10) Carry out DL data transfer with 2-antenna STC matrix B, via freestyle BE (such as FTP) data
transfer (5 minute transfer for some stability evaluation).
Pass verdict
criteria
Successful data transfer in DL.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
Alternative test scenario 2:
In case that the BS does support MIMO mode selection feedback from the MS and the test setup (as shown below)
for stimulating the MS to send the MIMO mode selection feedback is available then perform the following test
scenario 2 instead of test scenario 1.
Test scenario 2 behavior
Identifier
M2_DL_MIMO_MODE_01
Ref
11.8.3.7.5, 11.8.3.7.6 [2]
Goal
Verify DL data transfer between BS and MS with Matrix A/B MIMO
Configuration
Basic Test Configuration for IOT Testing
Test
Condition
-
Initial State
TX Power Level: Medium
PC mode: Open loop
DL 2-antenna STC matrix A: Enable in MS and BS.
DL 2-antenna STC matrix B: Enable in MS and BS.
DL zone type. PUSC.
UL Single-antenna Collaborative SM: Disable.
UL zone type. PUSC.
CQI support: physical CINR or Effective CINR in PUSC zone.
Size of CQICH_ID field: 3bits, 6 bits, or 8 bits
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for all MSs and each MS can
support the Pre-Provisioned Service Flows.
- Service Classifier without Classification Rules
MS is deregistered from BS. MSs are switched off. BS remains on.
Test process
1) Start the monitor message capture, if available.
2) Switch on the MS
3) Carry out the Network Entry procedure.
4) Carry out 1 DL and 1 UL BS initiated BE service flow
5) BS allocates Fast feedback channel
6) Setup conditions for MS in such a waythat preferred MIMO Mode for the MS is Matrix A
 MS may provides MIMO Mode selection via fast-feedback special codeword for Matrix A
7) Then setup conditions for MS in such a way that preferred condition for MS is MIMO matrix B
Page - 198
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
 MS may provides MIMO Mode selection via fast-feedback special codeword for Matrix B
8) Carry out DL data transfer with the MS, via freestyle BE (such as FTP) data transfer (2 minute
transfer for some stability evaluation).
9) Reverse the setup condition such that the MS will have Matrix A as preferred condition.

MS may provides MIMO Mode selection via fast-feedback special codeword for Matrix A
10) Carry out DL data transfer with the MS, via freestyle BE (such as FTP) data transfer (5 minute
transfer for some stability evaluation).
Pass verdict
criteria
Successful data transfer in DL.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate TD below.
9.3.7.1.9.1
Block Diagram for MIMO Test Setup
The following block diagram describes the MIMO test setup and the attenuator
settings for MIMO mode selection
Block Diagram 1: MIMO Fader control
MIMO matrix A: a1=a2=a3=a4=1, 
MIMO matrix B: a1=a2=0; a3=a4=1
Fader
a4e 
j
TX/RX
a1e 
j
TX/RX
BS
MS
a2e 
j
RX
a3e 
j
Page - 199
WiMAX FORUM PROPRIETARY
TX/RX
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
9.3.7.1.9.2
WMF-T25-003-R010v08
Capabilities Negotiation during Network Entry
Test Description
Identifier
M2_DL_MIMO_MODE_SBC_01
Description
Verify the successful completion of basic capabilities negotiation with Matrix A/B MIMO
Pre-test
conditions
Successful completion of initial ranging.
Step
Test Sequence
1
MS sends 1 or more SBC-REQ
SS Demodulator for MIMO support TLV: 2-Antenna STC Matrix A
and 2-Antenna STC Matrix B,
- SS Modulator for MIMO support TLV:
Capable of single antenna transmission
BS sends SBC-RSP
Result
OK
NOK
OK
NOK
-
2
-
With valid TLVs that are present in the SBC-REQ appropriate for the
Wave capabilities,
and with values that do not enable a feature disabled/not supported
by MS.
Observations
9.3.7.1.9.3
MAP
Test Description
Identifier
M2_ DL_MIMO_MODE_DAT_00
Description
Verify the successful completion of data transfer in DL for 5 minutes.
Pre-test
conditions
1 UL and 1 DL Service Flow is established.
Step
1
Test Sequence
Verify using tools such as Wireshark, Sanjole or MS logs
Result
OK
NOK
For every DL sub-Frame, BS sends DL-MAP or compressed DL-MAP to each
MS with
-
STC zone IE
Includes default setting for matrix A or B
-
HARQ_DL_MAP_IE() + MIMO DL Chase HARQ Sub-Burst IE() with
ACK disable = 0.
o
BS shall set the indicator to 1 and BS shall include the IE.
The followings are BS requirements:
1. BS shall include Dedicated MIMO control IE in first sub-burst of
MIMO DL Chase HARQ Sub-burst IE if MIMO matrix type is
different from Matrix defined in STC zone IE
BS shall include Dedicated MIMO control IE in later sub-bursts of same MIMO
DL Chase HARQ Sub-burst IE if MIMO matrix type is different from the type
used in the prior sub-burst
2
BS sends UL-MAP, compressed UL-MAP or UCD to each MS with
OK
NOK
3
- Fast Feedback Allocation IE
- CQICH Allocation IE, allocating the fast-feedback slots..
BS sends UCD to each MS with
OK
NOK
-
Size of the CQICH_ID field. In case of default value, the BS doesn’t
Page - 200
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
need to send the size of the CQICH_ID field.
MS sends physical or Effective CINR report as indicated in the CQICH
Allocation IE.
4
5
MS sends special CQICH code (if MIMO Mode feedback is requested by BS in
CQICH) to indicate preference for MIMO Matrix A/B
OK
NOK
OK
NOK
Observations
9.3.7.1.9.4
Data grants for the MS
Test Description
Identifier
M2_ DL_MIMO_MODE_DAT_01
Description
Verify the generation of data grants for the MS in the DL PUSC zone.
Pre-test
conditions
Successful network entry.
Step
Test Sequence
1
BS sends DL MAP with
Result
OK
NOK
OK
NOK
- HARQ DL MAP IE containing MIMO DL Chase HARQ Sub-Burst IE()
with ACK disable = 1 (HARQ disabled).
2
BS sends
- allocation using either Matrix A or B containing one or more PDUs with 16
bit CRC.
3
MS decodes the DL allocation
OK
NOK
4
Has the data from the BS to the MS been transferred correctly?
OK
NOK
Observations
9.3.7.2
MAC Tests
9.3.7.2.1 PHS
9.3.7.2.1.1
Basic MS & BS PHS support for UGS SF
Test Description
Identifier
M2_BS_MS_PHS _UGS_01
Ref
Scenario PHS CS
Goal
Verify BS and MS PHS support with UGS SF enabled for the MS.
Configuration
Basic Test Configuration for iIOT Testing.
Test
Condition
-
Compressed-IPv4-Header: Disable.
PHS: Enable.
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
Page - 201
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
available then authentication should be enabled.
- One UL UGS service flow has classification rule defined with just the Classification Rule Index.
- One DL UGS service flow has classification rule defined with just the Classification Rule Index.
o DL UGS1 Max Sustained Rate = 1 Mbps
o UL UGS1 Max Sustained Rate = 0.5 Mbps
o QoS Parameter Set Type = 7
o Uplink grant scheduling type = 6 (UL only)
o Request/Transmission Policy = 16 (0x10)
o Maximum Latency = 500 msec
o Tolerated Jitter = 500 msec
o Type of Data Delivery Services = 0
MS is deregistered from BS. MS is switched off. BS remains on.
Initial State
Test Process
1)
2)
3)
4)
Pass verdict
Criterion
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure with negotiation of PHS support.
Carry out 1 DL and 1 UL BS initiated service flow defining a PHS rule by adding a new service
flow using DSA-REQ with PHS rule or creating a PHS rule to an existing service flow using DSC
messages.
5) Carry out DL and UL data transfer for UGS SF.
For UGS service flow, traffic statistics indicate that traffic has been transferred with its Maximum
Sustained Rate (policing accuracy plus/minus 20%).
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
Observations
9.3.7.2.2 QoS service flows
9.3.7.2.2.1
Operation of pre-provisioned QoS service flows
Test scenario behaviour
Identifier
ID_QoS_SRV_FLW_01
Ref
Scenario QoS Service Flows
Goal
Verify correct operation of pre-provisioned QoS service flows.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
-
TX Power Level:
BS: medium
MS: controlled by power control algorithm
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
4 DL Service Flows are Pre-provisioned at the BS for this MS – 2 BE and 2 UGS. In addition,
4 UL Service Flows are Pre-provisioned at the BS for this MS – 2 BE and 2 UGS. The MS
can support the Pre-provisioned service flows.
o DL UGS1 Max Sustained Rate = 1 Mbps
Page - 202
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
Initial State
Test process
Pass verdict
criterion
Final Verdict
WMF-T25-003-R010v08
o UL UGS1 Max Sustained Rate = 0.5 Mbps
o All BE flows Max Sustained Rate = unlimited
- Service Flow Classification Rules: Based on IP source/destination address number.
- Type of map used: Compressed map
MS is deregistered from BS. MS is switched off. BS remains on.
1)
2)
3)
4)
5)
6)
7)
8)
1)
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure.
Carry out 2 DL and 2 UL BS-initiated service flows.(1pair UGS and 1pair BE)
Carry out DL continuous data transfer on DL UGS1 only from a traffic generator.
Carry out additional DL FTP file transfer (50 MB file) on DL BE1.
Carry out additional UL continuous data transfer on UL UGS1.
Carry out additional UL FTP file transfer (10 MB file) on UL BE1.
For each UGS service flow, traffic statistics indicate that traffic has been transferred with its
Maximum Sustained Rate (policing accuracy plus/minus 20%).
2) For BE flows carrying FTP traffic, the files are successfully transferred.
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
Notes
Service Flow QoS-related TLV inclusion and settings:
UGS:
QoS Parameter Set Type = 7
Maximum Sustained Traffic Rate (See test procedure definition)
Uplink grant scheduling type = 6 (UL only)
Request/Transmission Policy = 19 (0x13)
Maximum Latency = 500 msec
Tolerated Jitter = 500 msec
Type of Data Delivery Services = 0
BE:
QoS Parameter Set Type = 7
Maximum Sustained Traffic Rate (See test procedure definition)
Uplink grant scheduling type = 2 or omitted (UL only)
Request/Transmission Policy = 16 (0x10)
Maximum Latency = omitted
Tolerated Jitter omitted
Type of Data Delivery Services = 3
9.3.7.2.2.2
9.3.7.2.2.2.1
ErtPS Service Flows
Basic ertPS operation – one packet per UL grant
Test scenario behaviour
Identifier
M2_QOS_ERTPS_01
Page - 203
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
Ref
WMF-T25-003-R010v08
802.16 Cor 2 Draft 3
802.16e-2005
802.16-2004
Goal
Verify correct operation of basic ertPS operation. Turn unsolicited grants on and off
based on traffic activity. One UL packet per unsolicited ertPS grant.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
Initial State
Test process
1 BS and 1 MS
TX Power Level:
BS: medium
MS: controlled by power control algorithm
- ARQ: Enabled
- HARQ: Enabled
- If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA
server is available then authentication should be enabled.
- 1 DL BE service flow, 1 UL BE service flow, and 1 UL ertPS service flow is preprovisioned at the BS for this MS.
- Packing and fragmentation are enabled on the UL ertPS service flow.
- Service Flow Classification Rules: Based on IP source/destination address number.
- Type of map used: Compressed map
MS is deregistered from BS. MS is switched off. BS remains on.
1)
2)
3)
4)
Switch on the MS.
Carry out the Network Entry procedure.
Carry out BS initiated service flow provisioning procedure.
Verify that the BS does not make unsolicited UL grants for the MS greater than 1 UL
slot (i.e., an optional polling grant).
5) Start external UL traffic generator configured to send 1 packet of size 100 bytes
every 20 msec over the UL ertPS service flow.
6) Verify that the MS requests the unsolicited ertPS grants are turned ON.
- MS sends a BwR header with ertPS CID and BR field set appropriately, OR
- MS sends CQICH ertPS codeword to turn grants on.
- If MS sends CQICH ertPS codeword, BS makes unsolicited grants according to
Maximum Sustained Traffic Rate.
- MS then requests grant size change by sending BwR header or grant
management subheader (GMSH) with ertPS CID with BR field set appropriately.
- BS changes unsolicited grant size according to MS request.
Final Verdict
7) After 30 seconds, stop external UL traffic generator.
8) Verify that the MS sends a BwR header with ertPS CID and BR field set to 0.
9) Verify that the BS does not make unsolicited UL grants for the MS greater than 1 UL
slot (i.e., an optional polling grant).
1) The steps outlined above are followed.
2) The BR field in Test Process Step (6) must equal 100 bytes plus MAC PDU overhead
– i.e., the size of one traffic generator packet encapsulated in one MAC PDU for the
ertPS service flow. The MS may optionally add an additional 2 bytes for a GMSH,
or an additional 6 bytes for a bandwidth request header containing any UL CID. The
exact BR value depends on the service flow configuration negotiated during
connection setup.
3) At least 95% of the traffic generator packets are successfully received by the traffic
sink.
PASS
FAIL
Notes
Service Flow QoS-related TLV inclusion and settings:
Pass verdict
criterion
Page - 204
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
ertPS:
QoS Parameter Set Type = 7
Maximum Sustained Traffic Rate = 1 Mbps.
Uplink grant scheduling type = 5
Request/Transmission Policy = 16 (0x10)
Maximum Latency = 50 msec
Unsolicited Grant Interval = 20 msec
Tolerated Jitter = 50 msec
Type of Data Delivery Services = 4
BE:
QoS Parameter Set Type = 7
Maximum Sustained Traffic Rate = 10 Mbps
Uplink grant scheduling type = 2 or omitted (UL only)
Request/Transmission Policy = 16 (0x10)
Maximum Latency = 500 msec
Tolerated Jitter omitted
Type of Data Delivery Services = 3
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
9.3.7.2.2.2.2
Basic ertPS operation – two packets per UL grant
Test scenario behaviour
Identifier
M2_QOS_ERTPS_02
Ref
802.16 Cor 2 Draft 3
802.16e-2005
802.16-2004
Goal
Verify correct operation of basic ertPS operation. Turn unsolicited grants on and off
based on traffic activity. Two UL packets per unsolicited ertPS grant.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
-
1 BS and 1 MS
TX Power Level:
BS: medium
MS: controlled by power control algorithm
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA
server is available then authentication should be enabled.
1 DL BE service flow, 1 UL BE service flow, and 1 UL ertPS service flow is prePage - 205
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
Initial State
Test process
WMF-T25-003-R010v08
provisioned at the BS for this MS.
- Packing and fragmentation are enabled on the UL ertPS service flow.
- Service Flow Classification Rules: Based on IP source/destination address number.
- Type of map used: Compressed map
MS is deregistered from BS. MS is switched off. BS remains on.
1)
2)
3)
4)
Switch on the MS.
Carry out the Network Entry procedure.
Carry out BS initiated service flow provisioning procedure.
Verify that the BS does not make unsolicited UL grants for the MS greater than 1 UL
slot (i.e., an optional polling grant).
5) Start external UL traffic generator configured to send 1 packet of size 100 bytes
every 10 msec over the UL ertPS service flow.
6) Verify that the MS requests the unsolicited ertPS grants are turned ON.
- MS sends a BwR header with ertPS CID and BR field set appropriately, OR
- MS sends CQICH ertPS codeword to turn grants on.
- If MS sends CQICH ertPS codeword, BS makes unsolicited grants according to
Maximum Sustained Traffic Rate.
- MS then requests grant size change by sending BwR header or grant
management subheader (GMSH) with ertPS CID with BR field set appropriately.
- BS changes unsolicited grant size according to MS request.
Final Verdict
7) After 30 seconds, stop external UL traffic generator.
8) Verify that the MS sends a BwR header with ertPS CID and BR field set to 0.
9) Verify that the BS does not make unsolicited UL grants for the MS greater than 1 UL
slot (i.e., an optional polling grant).
1) The steps outlined above are followed.
2) The BR field in Test Process Step (6) must be set to accommodate two traffic
generator packets per unsolicited grant. Specifically, it must equal 200 bytes plus
MAC PDU overhead for one or two MAC PDU’s, depending on whether the MS
chooses to use UL packing. The MS may optionally add an additional 2 bytes for a
GMSH, or an additional 6 bytes for a bandwidth request header containing any UL CID. The
exact BR value depends on the service flow configuration negotiated during
connection setup.
3) At least 95% of the traffic generator packets are successfully received by the traffic
sink.
PASS
FAIL
Notes
Service Flow QoS-related TLV inclusion and settings:
Pass verdict
criterion
ertPS:
QoS Parameter Set Type = 7
Maximum Sustained Traffic Rate = 1 Mbps.
Uplink grant scheduling type = 5
Request/Transmission Policy = 16 (0x10)
Maximum Latency = 50 msec
Unsolicited Grant Interval = 20 msec
Tolerated Jitter = 50 msec
Type of Data Delivery Services = 4
BE:
QoS Parameter Set Type = 7
Page - 206
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Maximum Sustained Traffic Rate = 10 Mbps
Uplink grant scheduling type = 2 or omitted (UL only)
Request/Transmission Policy = 16 (0x10)
Maximum Latency = 500 msec
Tolerated Jitter omitted
Type of Data Delivery Services = 3
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
9.3.7.2.3 Scan/Report Trigger Metrics
9.3.7.2.3.1
Scan Trigger Metric Test case (Mean BS RSSI/CINR Trigger metric type)
Test scenario behavior
Identifier
ID_SCN_TRG_01
Ref
Inter-FA Scan Trigger Metric : mean Serving BS RSSI less than absolute value or
mean Serving BS CINR less than an absolute value
Goal
Verify scan is triggered on the basis of measured mean BS RSSI measured on Preamble, or Verify
scan is triggered on the basis of measurement of mean physical CINR of Serving BS on the
Preamble
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
Initial State
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
- 2 HO enabled BSs and 1 HO-enabled MS
- measurement equipment monitors mean RSSI (RCT Section 9.1.4.4) and CINR (RCT Section
9.1.5.4)
- Channel attenuator is used to control the channels
- TX Power Level:
BS: medium
MS: controlled by open loop power control algorithm
- Corrigendum 2 support: yes
1) BSs and the MS are connected in a wired setup
2) Both BSs are transmitting at equal TX power level at BS transmitter. BS 1 and BS 2 signals
are independently attenuated and combined and connected to the MS. BS 2 signal is
attenuated one of the following two.
- BS 2 signal is attenuated to 7 dB below the absolute trigger value defined in step 6. BS 1
signal is attenuated to 5 dB higher than the absolute trigger value in step 6.
- BS 2 CINR is attenuated to 3 dB below the absolute trigger value defined in step 6, i.e., BS 2
CINR is 3 dB. BS 1 signal is attenuated to 6 dB higher than the absolute trigger value in step
6, i.e. BS 1 CINR is 12 dB.
3) Both BSs are operating at different center frequency.
4) BS 1 transmits MOB_NBR-ADV message periodically with full BSID including BS2 and
other BSs up to total of 32 neighboring BSs.
5) MS is synchronized and connected to BS 1.
Page - 207
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
6) BS 1 sends Trigger Value TLV in DCD with Type (a) and/or Type (b) as follows.
Type (a):
 Trigger metric type = 0x0 (CINR)
 function = 0x6 (CINR of serving BS < absolute value)
 Action = 0x3 (start neighbor BS scanning process by sending MOB_SCN-REQ)
 Trigger value = absolute value (6 dB)
 Trigger average duration in ms (500 ms = 100 frames)
Type (b):
Test process
 Trigger metric type = 0x1 (RSSI)
 function = 0x6 (RSSI of serving BS < absolute value)
 Action = 0x3 (start neighbor BS scanning process by sending MOB_SCN-REQ)
 Trigger value = absolute value (-85 dBm or -90 dBm)
 Trigger average duration in ms = 500 ms (100 frames)
1) Verify that MS decodes MOB_NBR-ADV message.
2) Adjust channel attenuator of BS 1 in 1 dB steps so that
BS 1 CINR is below the configured absolute value, or
BS 1 is at 2 dB lower RSSI than the configured absolute value. Verify that BS 1 signal is 5 dB
above BS 2 at the end of step 2.
Pass verdict
criterion
3) Verify that MS sends MOB_SCN-REQ to BS 1.
4) Verify that MS perform scanning after receiving MOB_SCN-RSP from BS1.
5) Verify that Scan results of BS 2 values are available via debug/logging interface of MS if
possible after the scanning iterations is complete.
MS sends scan request message once the trigger is met and MS starts scanning at start frame
specified in MOB_SCN-RSP message
Final Verdict
PASS
FAIL
Reference:
P80216_Cor2_D3.pdf (Table 358/358b, and Table 384d/384e)
802.16-2004.pdf
802.16e-2005.pdf (Table 109i/109j, Table 348f/348g, Section 11.8.3.7.9, Section 11.11/11.12)
WiMAX_Forum_Mobile_RCT_v1.0.0 (Section 9.1.4, 9.1.5, 9.1.6)
WiMAX Forum Mobile RCT- Wave 2 Amendment v0.2.0.doc
WiMAX Forum Mobile System Profile v1 4 0.pdf (Table A.103, Section 4.1.7)
Note: As specified in Table 348f/g of 802.16e-2005, the trigger TLV is present in MOB_NBR-ADV only if it is
different from that in DCD or that in preceding MOB_NBR-ADV.
9.3.7.2.4 MS initiated Handover with Optimized Re-entry
This procedure utilizes the optimized handover re-entry option where the Fast-Ranging IE is used
in place of handover ranging and re-entry only requires RNG-REQ/RSP exchange without SBC,
REG, PKM, or DSA messages.
Note: If the serving BS negotiates with target BS allocation of a non-contention-based ranging
opportunity for the MS provided that time synchronization between serving and target BSs are
guaranteed, the target BS will allocate a dedicated transmission opportunity for RNG-REQ
message to be transmitted by the MS using Fast_Ranging_IE. Otherwise the MS have to perform
CDMA ranging with HO codes.
Page - 208
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
9.3.7.2.4.1
WMF-T25-003-R010v08
MS initiated handover test case Behavior
Test scenario behavior
Identifier
ID_MS_INI_HO_01
Ref
Goal
Verify MS initiated handover.
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
Initial State
TX Power Level:
o MS: controlled by power control algorithm; typically at maximum power
o BS: medium
- ARQ: Enabled
- HARQ: Enabled
- If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA
server is available then authentication should be enabled.
- Corrigendum 2 support: yes
- SBS and TBS are on different frequencies
- Compressed MAP: yes
- TPC mode after NW entry: Open Loop
MS is registered and active in the BS
Test process
The following steps are repeated for each test environment:
1)
2)
3)
4)
Start the monitor message capture, if available.
Ensure the target BS is on.
Decrease the Serving BS signal to trigger scanning initiation (but not handover).
Decrease the Serving BS signal and/or increase the target BS signal level in order to
trigger handover initiation.
5) After handover, initiate DL and UL data transfer
via the PING procedure: Host behind the BS pings the host behind the MS
Host behind the MS pings the host behind the BS.
Pass verdict
criterion
Successful handover from SBS to TBS and PING procedure with TBS.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
Test Environments
Test runs 5 and 7 will be performed if a channel emulator is available otherwise tests 4 and 6 will be performed.
Parameter Variations on
1.
2.
3.
4.
HARQ
Authentication
Amount of BE and UGS SFs
Attenuator versus Channel emulator
Page - 209
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
5.
6.
WMF-T25-003-R010v08
SBS/TBS same or different ASN
Inter sector or inter cell HO
Test Number
9.3.7.2.4.1.1
4
5
6
7
HARQ
Y
N
N
Y
Authentication
Y
Y
Y
Y
Number BE pairs
(UL/DL)
Number UGS pairs
(UL/DL)
1
1
1
1
1
1
1
1
Inter-Sector HO
(same cell)
Y
Y
N
N
Inter cell HO
N
N
Y
Y
Same ASN
Y
Y
Y
Y
Attenuator
Y
N
Y
N
Channel Emulator
N
Y
N
Y
Neighbor Advertisement
Test Description
Identifier
ID_BCAST_SBS_TBS_01
Description
Verify the broadcast messages/IEs/TLVs in SBS and TBS.
Pre-test
conditions
Successful completion of initial network entry.
Step
Test Sequence
Result
1
SBS and TBS send MOB_NBR-ADV.
OK
NOK
2
SBS and TBS send Noise plus interference IE in DL-MAP
OK
NOK
3
SBS sends Scanning Trigger TLV in DCD and/or MOB_NBR-ADV
OK
NOK
OK
NOK
-
4
Trigger Action = 0x3: (On trigger, MS starts neighbor BS scanning process
by sending MOB_SCN-REQ)
- Trigger Type = 0b00 (CINR metric)
- Trigger value = 15 dB
- Trigger Function (3 bits) = 0b110 (Metric of serving BS less than absolute
value)
SBS sends HO Trigger TLV in DCD and/or MOB_NBR-ADV.
-
Trigger Action = 0x2 (Respond on trigger with MOB_MSHO-REQ).
Trigger Type = 0b00 (CINR metric)
Trigger value = 4 dB
Trigger Function (3 bits) = ob011 (Metric of neighbor BS is greater than
serving BS metric by relative value
Observations:
Page - 210
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
9.3.7.2.4.1.2
WMF-T25-003-R010v08
Scanning Initiation
Test Description
Identifier
ID_MS_INI_SCAN_01
Description
Verify the successful completion of MS initiated scanning procedure
Pre-test
conditions
MS received scan trigger TLVs from Serving BS.
Step
Test Sequence
Result
1
When scan trigger condition met, MS sends 1 or more MOB_SCN-REQ
indicating preferred scanning parameters
OK
NOK
2
BS sends MOB_SCN-RSP with scanning parameters
OK
NOK
3
MS scans neighbor BSs during scan interval as defined in MOB_SCN-RSP
OK
NOK
Observations
Scan trigger TLV should be used by MS to send MOB_SCN-REQ
9.3.7.2.4.1.3
Handover Decision
Test Description
Identifier
ID_MS_INI_HO_DES_01
Description
Verify the successful completion of MS initiated Handover Decision.
Pre-test
conditions
MS received Neighbor Advertisement and trigger TLVs from Serving BS.
Step
Test Sequence
Result
1
When handover trigger condition met, MS sends MOB_MSHO-REQ indicating
the target BS.
OK
NOK
2
BS sends MOB_BSHO-RSP with action time > 0 indicating fast ranging IE is
used in target BS and optionally the HO_ID.
OK
NOK
Observations
Handover trigger TLV should be used by MS to send MOB_MSHO-REQ
9.3.7.2.4.1.4
Handover Initiation
Test Description
Identifier
M2_BS_INI_HO_01
Description
Verify the successful completion of Handover Initiation from serving BS to target BS.
Pre-test
conditions
MS has decided to handover from serving BS to target BS.
Step
Test Sequence
Result
1
MS sends MOB_HO-IND to serving BS with HO_IND_type = 0b00 (serving
BS release)
OK
NOK
2
MS moves to target BS and synchronizes to DL signal
OK
NOK
BS sends Fast-Ranging IE in frame identified by action time in MOB_BSHORSP. Fast-Ranging IE includes either HO_ID or MS’s MAC address.
OK
NOK
MS decodes fast-ranging IE and sends RNG_REQ in the UL allocation with
OK
NOK
3
Page - 211
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
HO-ID and/or the MS’s MAC address.
4
BS sends RNG-RSP with
HO-ID and/or the MS’s MAC address.
Basic CID and Primary Management CID,
CID Update TLV
SAID updated TLV and optionally the SA-TEK-update TLV
HO Process Optimization TLV
o Bit #0 = 1 - Omit SBC-REQ
o Bit #1, Bit #2 has three options:
 (1, 1): Re-authentication and SA-TEK 3-way handshake is not
performed. The RNG-RSP message does not include SA-TEKUpdate TLV nor SA Challenge Tuple TLV. All the TEKs
received from the serving BS are reused.
 (1,0): SA-TEK-Update TLV is included in the RNG-RSP
message. In this case, SA-TEK 3-way handshake is avoided and
SA Challenge Tuple TLV shall not be included in the RNG-RSP
message.
 (0,0): Perform re-authentication and SA-TEK 3-way handshake.
BS shall not include SA-TEK-Update TLV in the SA-TEKResponse message. In addition, the RNG-RSP message does not
include SA-TEK-Update TLV or SA Challenge Tuple TLV
o Bit #3 - 5 = 1 – omit options related to secondary management
connections.
o Bit #6 = 1 – all service and operational state transfer or sharing
between Serving BS and Target BS (static and dynamic content.)
o Bit #7 = 1 - omit REG-REQ
o Bit #8 = 1 - BS shall not send an unsolicited SBC-RSP.
o Bit #9 = 0 - no MS DL data pending at target BS
o Bit #10 = 1 - BS shall not send an unsolicited REG-RSP.
o Bit #11 = 0 - SN_REPORT not issued by MS.
o Bit #12 = 1 - MS shall send notification of MS successful re-entry
o Bit #13 = 0 - MS shall not trigger a higher layer protocol required to
refresh its traffic IP address
- CMAC
If Bit # 1, Bit # 2 is used as 1,0 in HO Process Optimization TLV, using MS
logs verify that OLD SAID Update TLV is not included in the SA-TEKUpdate TLV.
OK
NOK
OK
NOK
OK
NOK
OK
NOK
-
5
6
7
MS confirms receipt of RNG-RSP by sending an UL indication such as:
- UL BW request Header
- UL PDU
- HARQ ACK
- Fast-feedback
Repeat the RNG-RSP from BS using Bit # 1 and Bit # 2 value set to 0,0.
Using MS logs verify that SA-TEK-Update TLV is not included in the SATEK-Response Message.
Observations
9.3.7.2.4.1.5
Handover Confirmation
Test Description
Identifier
ID_HO_CONF_01
Description
Verify the successful completion of data transfer via the PING procedure.
Page - 212
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
Pre-test
conditions
.Handover is complete
Step
Test Sequence
1
WMF-T25-003-R010v08
Result
Host behind the BS pings the host behind the MS
OK
NOK
OK
NOK
-
The CID of the DL MAC PDU (EchoRequest) is the Transport Cid of the
DL Service Flow.
- The CID of the UL MAC PDU (EchoReply) is the Transport Cid of the UL
Service Flow.
- Is the PING procedure successfully completed?
Repeat for all connections
2
Host behind the MS pings the host behind the BS.
-
The CID of the UL MAC PDU (EchoRequest) is the Transport Cid of the
UL Service Flow.
The CID of the DL MAC PDU (EchoReply) is the Transport Cid of the DL
Service Flow.
Is the PING procedure successfully completed?
Repeat for all connections
Observations
Use CS filtering based on source IP address to filter pings to each CID
Issue: Revise test to describe how ping could be used during entire test, not just after handover is complete?
9.3.7.2.5 HO Ranging
This procedure is performed typically as an error case to the MS-initiated
handover. Instead of the MS sending a MOB-MSHO-REQ at the serving BS the
MS directly moves to the target BS and performs handover ranging to re-enter the
network.
9.3.7.2.5.1
Handover ranging test case Behavior
Test scenario behavior
Identifier
ID_HO_RNG_01
Ref
Goal
Verify handover ranging
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
-
TX Power Level:
o MS: controlled by power control algorithm; typically at maximum power
o BS: medium
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA
server is available then authentication should be enabled.
Corrigendum 2 support: yes
SBS and TBS are on different frequencies
Page - 213
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
-
Initial State
Compressed MAP: yes
1 UL and 1 DL BE Service Flows established.
1 UL and 1 DL UGS Service Flows established.
TPC: open loop
Two test environments (choose based on availability):
 Inter-sector - SBS and TBS on different sectors at same cell using attenuator
 Inter-cell - SBS and TBS on different sites (same ASN) using attenuator
MS is registered and active in the BS
Test process
The following steps are repeated for each test environment:
1) Start the monitor message capture, if available.
2) Ensure the target BS is on.
3) Sharply decrease the Serving BS signal level to levels that force MS to fail RF link; MS
should perform HO ranging on target BS
4) After handover, initiate DL and UL data transfer
via the PING procedure: Host behind the BS pings the host behind the MS
Host behind the MS pings the host behind the BS.
Pass verdict
criterion
Successful handover ranging at TBS and PING procedure with TBS.
Final Verdict
PASS
FAIL
If the Final Verdict is evaluated to FAIL, then the error is reported in the appropriate ID below.
9.3.7.2.6 Security
9.3.7.2.6.1
PKMv2 Authorization initial network entry: initial network entry
Test scenario behaviour
Identifier
M2_PKMv2_INI_NW_01
Page - 214
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Goal
Verify the general security process for PKMv2 Network Entry
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
Initial State
Test process
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if
an AAA server is available then authentication should be enabled.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS
and the MS can support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
- TEK refresh timer is set to 10 minutes.
MS is deregistered from BS. MS is switched off. BS remains on.
Pass verdict
criterion
12) Start the monitor message capture, if available.
13) Switch on the MS.
14) Carry out Synchronization and Ranging
15) Carry out Capability Negotiation (Authentication enabled, PKMv2, EAP only)
16) Carry out Authentication with PKMv2
17) Carry out SA-TEK 3-way handshake.
18) Perform PKM Key Request
19) Carry out Registration
20) Carry out Traffic Connection establishment.
21) Carry out 1 DL and 1 UL BE service flow.
22) Carry out DL and UL data transfer
a) via the PING procedure: Host behind the BS pings the host behind the MS.
Host behind the MS pings the host behind the BS.
b) via iPERF tool: Host behind the BS uses iPERF to connect to host behind
the MS. Host behind the MS connects to the host behind the BS.
23) Wait for reauthorization (Periodic TEK refresh is running).
24) Wait until periodic TEK refresh uses the new AK.
25) Carry out again DL and UL data transfer
a) via the PING procedure: Host behind the BS pings the host behind the MS.
Host behind the MS pings the host behind the BS.
Successful execution of Initial Authentication, PKM v.2 SA-TEK 3-way
handshake, Key Request, and Periodic TEK refresh process
Final Verdict
PASS
FAIL
9.3.7.2.7 PKMv2 Authorization network re-entry: network re-entry
9.3.7.2.7.1
Non Optimized Handoff
This test scenario shall be executed only if it is supported by at least two different
BS vendors in the Mobile IOT amendment.
Page - 215
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Test scenario behaviour
Identifier
M2_PKMv2_NO_OPT_HO_01
Goal
Verify the general security process for PKMv2 Network Entry
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
Initial State
Frequency channel: Middle.
TX Power Level: Medium.
ARQ: Enabled
HARQ: Enabled
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA
server is available then authentication should be enabled.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the
MS can support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is registered at a serving BS.
MS is configured for PKMv2 authentication
Test process
Pass verdict
criterion
Final Verdict
1) Start the monitor message capture, if available.
2) Move the MS from its serving BS to a target BS (Use a handoff setting described in
the previous chapter)
3) Carry out Handoff
4) Carry out Initial/Handoff Ranging
5) Carry out Capability Negotiation (Authentication enabled, PKMv2, EAP only)
6) Carry out Authentication with PKMv2
7) Carry out SA-TEK 3-way handshake.
8) Perform PKM Key Request
9) Carry out Registration
10) Carry out Traffic Connection establishment.
11) Carry out 1 DL and 1 UL BE service flow.
12) Carry out DL and UL data transfer
a) via the PING procedure: Host behind the BS pings the host behind the MS. Host
behind the MS pings the host behind the BS.
b) via iPERF tool: Host behind the BS uses iPERF to connect to host behind the MS.
Host behind the MS connects to the host behind the BS.
13) Wait for reauthorization (Periodic TEK refresh is running).
14) Wait until periodic TEK refresh uses the new AK.
15) Carry out again DL and UL data transfer
a) via the PING procedure: Host behind the BS pings the host behind the MS. Host
behind the MS pings the host behind the BS.
Successful execution of Initial Authentication, PKM v.2 SA-TEK 3-way handshake, and
Periodic TEK refresh process. Verify that security contexts transferred correctly from the
serving BS to the new target BS.
PASS
FAIL
Note: This table is applied to the case that HO Optimization is not used.
9.3.7.2.7.2
Optimized Handoff
Test scenario behavior
Identifier
M2_PKMv2_OPT_HO_01
Goal
Verify the general security process for PKMv2 Network Re-Entry
Page - 216
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
- Frequency channel: Middle.
- TX Power Level: Medium.
- ARQ: Enabled
- HARQ: Enabled
- If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA
server is available then authentication should be enabled.
- 1 DL and 1 UL BE Service Flows are Pre-Provisioned at the BS for this MS and the
MS can support the Pre-Provisioned Service Flows.
- Service Flows Classification Rule: Based on IP address/port number.
MS is registered at a serving BS.
Initial State
MS is configured for PKMv2 authentication
Test process
Pass verdict
criterion
Final Verdict
1) Start the monitor message capture, if available.
2) Move the MS from its serving BS to a target BS (Use a handoff setting described in
the previous chapter)
3) Carry out Handoff
4) Carry out Initial/Handoff Ranging
5) Carry out Capability Negotiation (Authentication enabled, PKMv2, EAP only)
(Optional depending on the HO Optimization TLV setting)
6) Carry out Authentication with PKMv2 (Optional depending on the HO Optimization
TLV setting)
7) Carry out SA-TEK 3-way handshake (Optional depending on the HO Optimization
TLV setting)
8) Perform PKM Key Request (Optional depending on the HO Optimization TLV
setting)
9) Carry out Registration (Optional depending on the HO Optimization TLV setting)
10) Carry out Traffic Connection establishment.
11) If SA-TEK is updated, verify using MS logs (use BS logs is MS logs are unavailable)
PN is reset to 1
12) Carry out 1 DL and 1 UL BE service flow.
13) Carry out DL and UL data transfer
a) UDP data transfer over BE. (5 minute transfer)
14) Wait for reauthorization (Periodic TEK refresh is running).
15) Wait until periodic TEK refresh uses the new AK.
16) After TEK Refresh, verify using MS logs (use BS logs is MS logs are unavailable) PN
is reset to 1
17) Carry out again DL and UL data transfer
a) UDP data transfer over BE. (5 minute transfer)
Successful execution of Initial Authentication and Periodic TEK refresh process. Verify
that security contexts transferred correctly from the serving BS to the new target BS.
Verify that each required step is performed, not skipped. After HO verify successful
transfer of DL and UL data. Successful data transfer means packet error rate less than 0.5
percent at 500kbit/sec.
PASS
FAIL
Note: This table is applied to the case that HO Optimization is used.
9.3.7.2.8 CMAC_KEY_COUNT Test Cases
9.3.7.2.8.1
CMAC Key Count test case 1
Test scenario behaviour
Identifier
M2_CMAC_KEY_CNT_01
Page - 217
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Goal
Initialization to 0 of CMAC_KEY_COUNT in AK context during initial authenticated network
entry
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
Initial State
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
CMAC MAC mode (Corr2) enabled MS and BS1
MS and 1 BS are connected in CMAC MAC security mode
Channel attenuator is used to control the channels
TX Power Level:
BS: medium
MS: controlled by power control algorithm
Corrigendum 2 support: yes
1)
2)
1)
2)
3)
MS is up and waiting for authenticated network entry initiation
BS1 is up and running
Start the monitor message capture, if available.
Switch on the MS.
Carry out the Network Entry procedure:
 MS Application triggers authenticated network entry
 Anchor Authenticator (AAA) set CMAC_KEY_COUNT == 0
 MS initializes CMAC_KEY_COUNT == 0
 BS initializes CMAC_KEY_COUNT == 0
4) network entry complete
1) Authenticated network entry is successful with CMAC_KEY_COUNT initialized as 0 in the
AK context
2) Logs at BS show CMAC_KEY_COUNT=0.
3) Logs at AAA show CMAC_KEY_COUNT=1
PASS
FAIL
Test process
Pass verdict
criterion
Final Verdict
Reference
 C80216maint-06_075r
 G_R1.0.0-Stage-3: section 4.3.4
 P80216_Cor2_D3.pdf (Section 7.2.2.2.9, Fig. 130o, Table 133a)
 WiMAX Forum Network Architecture Stage 3 (4.3.4.2.2)
Note: WiMAX Forum Network Architecture defines that the Anchor Authenticator shall set CMAC_KEY_COUNT
to value 1 at initial authentication and after each re-authentication.
Note: The test steps are triggered automatically, i.e., no manual configuration is involved
9.3.7.2.8.2
CMAC Key Count test case 2
Test scenario behaviour
Identfier
M2_CMAC_KEY_CNT_02
Goal
Reset to 0 of CMAC_KEY_COUNT due to re-authentication after HO
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
MS is deregistered from BS. MS is switched off. BS remains on.
HO-enabled 1 MS and 2 BSs are connected in CMAC MAC security mode
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
Channel attenuator is used to control the channels
TX Power Level:
BS: medium (as used in PlugFest 3.5.0, Section 9 for setup, or TBD?)
Page - 218
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
Initial State
WMF-T25-003-R010v08
MS: controlled by power control algorithm
Corrigendum 2 support: yes
1)
2)
1)
2)
3)
4)
MS is up and waiting for authenticated network entry initiation.
BS1 and BS2 are up and running.
Both BSs are transmitting at equal TX power level but the TX signal of BS 2 is attenuated.
MS is switched on and performs NW entry with authentication on BS 1.
BS 1 transmits MOB-NBR-ADV message periodically with full BSID.
BS 1 sends Trigger Value TLV in DCD
o Trigger metric type = 0x0 (CINR)
o Function = 0x3 (CINR of target BS > CINR of serving BS by relative value)
o Action = 0x2 (respond with MOB-MSHO-REQ)
5) Increase the attenuation on BS 1 to trigger MS HO from BS 1 to BS 2, and back again, to
verify that secure HO is working well.
6) MS/BS increases CMAC_KEY_COUNT upon each successful HO with skipping
authentication on the basis of HO optimization TLV
7) Change BS settings to enforce BS to do a re-authentication after HO.
8) Logs at BS show that the successful MS re-authentication resets CMAC_KEY_COUNT to 0.
 MS does resync and thus re-authentication, and CMAC_KEY_COUNT is reset as 0
afterwards.
 The CMAC_KEY_COUNT should be reset to 0 after HO re-authentication,
PASS
FAIL
Test process
Pass verdict
criterion
Final Verdict
Reference:



C80216maint-06_075r
NWG_R1.0.0-Stage-3: section 4.3.4
P80216_Cor2_D3.pdf (Section 7.2.2.2.9, Fig. 130o, Table 133a)
Note: In Test process Step 2, MS re-authentication can be enforced by either one of the
following:

MS resync during HO (with authentication skipped in HO optimization TLV), which can
further be triggered by HO failure due to target BS not replying RNG-RSP, which may not be
easily configured
MS resync due to a small AK lifetime and AK lifetime expiry by configuration
target BS replies RNG-RSP with authentication non-skipped in HO Optimization TLV


9.3.7.2.8.3
CMAC Key Count test case 3
Test scenario behaviour
Identifier
M2_CMAC_KEY_CNT_03
Goal
CMAC_KEY_COUNT in the context of idle mode
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
Initial State
Test process
1)
2)
1)
2)
idle-mode enabled 1 MS and 1 BS are connected in CMAC MAC security mode
Channel attenuator is used to control the channels
TX Power Level:
BS: medium (as used in PlugFest 3.5.0, Section 9 for setup, or TBD?)
MS: controlled by power control algorithm
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
Corrigendum 2 support: yes
MS is up and waiting for authenticated network entry initiation
BS is up and running
MS is switched on and performs NW entry with authentication on BS.
BS 1 transmits MOB-PAG-ADV message periodically.
Page - 219
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Pass verdict
criterion
3) Do not start any activity from MS side (or BS side for this MS) to trigger MS initiated idle
mode.
4) MS sends DREG-REQ for entering idle mode, and BS allowes MS to enter idle mode by
responding with DREG-RSP
5) Let MS remain in idle mode for some time (a couple of mins)
6) Start traffic from MS side so that MS exits idle mode
7) MS/BS increases CMAC_KEY_COUNT upon each successful idle mode re-entry with
skipping authentication on the basis of HO optimization TLV
8) Change BS settings to enforce BS to do a re-authentication after idle
9) Enforce the MS to do a successful re-authentication upon network re-entry from Idle Mode
10) Logs at BS/MS show that the successful MS re-authentication procedure resets
CMAC_KEY_COUNT as 0.
 BS/MS increase CMAC_KEY_COUNT by 1 upon MS’s successful re-entry from IM;
 Once re-authentication procedure is triggered,, CMAC_KEY_COUNT is reset as 0
Final Verdict
PASS
FAIL
Reference:



C80216maint-06_075r
NWG_R1.0.0-Stage-3: section 4.3.4
P80216_Cor2_D3.pdf (Section 7.2.2.2.9, Fig. 130o, Table 133a)
Note: For the step 2 of test process, MS re-authentication upon network re-entry from idle
mode can be triggered by either one of the following:



MS resync due to idle mode exit failure, which as an error scenario may not be easy to trigger
MS resync due to AK lifetime expiry, which will prompt MS to exit from IM.
BS-initiated security policy change through (unsolicited) SBC-RSP, which causes MS re-auth
without resync, and may not be easy to trigger
MS does network reentry from Idle Mode (i.e., IM exit) with authentication on the basis of
HO Optimization TLV

9.3.7.2.8.4
CMAC Key Count test case 4
Test scenario behaviour
Identifier
M2_CMAC_KEY_CNT_04
Goal
CMAC_KEY_COUNT is not changed upon HO cancellation
Configuration
Basic Test Configuration for IOT Testing.
Test Condition
-
Initial State
Test process
1)
2)
1)
2)
3)
4)
5)
HO-enabled 1 MS and 2 BSs are connected in CMAC MAC security mode
Channel attenuator is used to control the channels
TX Power Level:
BS: medium (as used in PlugFest 3.5.0, Section 9 for setup, or TBD?)
MS: controlled by power control algorithm
Corrigendum 2 support: yes
If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
MS is up and waiting for authenticated network entry initiation
BS1 and BS2 are up and running
BSs and the MS are connected
Both BSs are transmitting at equal TX power leve and operating well.
BS transmits MOB-NBR-ADV message periodically with full BSID.
MS is synchronized and connected to BS 1.
BS 1 sends Trigger Value TLV in DCD
a) Trigger metric type = 0x0 (CINR)
b) Function = 0x3 (CINR of target BS > CINR of serving BS by relative value)
c) Action = 0x2 (respond with MOB-MSHO-REQ)
Page - 220
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
6) MS completes authenticated network entry with BS 1
7) Tune the attenuator to trigger MS HO from BS 1 to BS 2, and back again, to verify that secure
HO is working well
8) Verified that CMAC_KEY_COUNT increases upon each successful HO with authentication
skipped on the basis of HO Optimization TLV
9) Enforce HO CANCEL with the current serving BS after HO is triggered
10) Logs at BS show that MS sees no change to CMAC_KEY_COUNT
CMAC_KEY_COUNT has the same value as before, i.e., before the cancelled HO
Pass verdict
criterion
Final Verdict
PASS
FAIL
Reference:
9.3.7.2.8.5



C80216maint-06_075r
NWG_R1.0.0-Stage-3: section 4.3.4
P80216_Cor2_D3.pdf (Section 7.2.2.2.9, Fig. 130o, Table 133a)
Note: For the test step 1 in the process, HO cancel can be triggered by, say:

if current serving BS sends back a BSHO-RSP without the best BS that has been reported in
MSHO-REQ, which as an error scenario may not be easily controlled.
CMAC Key Count test case 5
Test scenario behaviour
Identifier
M2_CMAC_KEY_CNT_05
Goal
CMAC_KEY_COUNT is not changed upon HO abort
Configuration
Basic Test Configuration for IOT Testing.
Test
Condition
-
Initial State
Test process
Pass verdict
criterion
Final Verdict
HO-enabled 1 MS and 2 BSs are connected in CMAC MAC security mode
Channel attenuator is used to control the channels
TX Power Level:
BS: medium
MS: controlled by power control algorithm
- Corrigendum 2 support: yes
- If the MS and BS has WiMAX Forum certificates, same EAP methods and if an AAA server is
available then authentication should be enabled.
1) MS is up and waiting for authenticated network entry initiation
2) BS1 and BS2 are up and running
3) BSs and the MS are connected
4) Both BSs are transmitting at equal TX power level and are operating well.
5) BS transmits MOB-NBR-ADV message periodically with full BSID.
6) MS is synchronized and connected to BS 1.
7) BS 1 sends Trigger Value TLV in DCD
a) Trigger metric type = 0x0 (CINR)
b) Function = 0x3 (CINR of target BS > CINR of serving BS by relative value)
c) Action = 0x2 (respond with MOB-MSHO-REQ)
8) MS completes authenticated network entry with BS 1
9) Tune the attenuator to trigger MS HO from BS 1 to BS 2, and back again, to verify that secure
HO is working well
10) Verified that CMAC_KEY_COUNT increases upon each successful HO with authentication
skipped on the basis of HO Optimization TLV
11) Enforce the BS to do HO ABORT is enforced after HO triggered
12) Logs at BS show no change to CMAC_KEY_COUNT
CMAC_KEY_COUNT has the same value as before, i.e., before the aborted HO
PASS
FAIL
Page - 221
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Reference:



C80216maint-06_075r
NWG_R1.0.0-Stage-3: section 4.3.4
P80216_Cor2_D3.pdf (Section 7.2.2.2.9, Fig. 130o, Table 133a)
Note: HO ABORT can be enforced if current serving BS sends back BSHO-RSP ABORT
back in response to:



Serving BS finds that the target BS does not have a better CINR
Serving BS checked with target BS through backbone and get a rejection of this HO request
Serving BS does not find the target BS in the neighborhood
Note: the above are error scenarios which may not be easy to trigger.
Page - 222
WiMAX FORUM PROPRIETARY
WiMAX Forum® Test Procedures
WiMAX Forum® Mobile IOT
WMF-T25-003-R010v08
Page - 223
WiMAX FORUM PROPRIETARY