ETSI TS 102 545-3 V1.2.1 (2009-02)

Technical Specification
Broadband Radio Access Networks (BRAN);
HiperMAN;
Conformance Testing for WiMAX/HiperMAN 1.3.1;
Part 3: Abstract Test Suite (ATS)

�
2 ETSI TS 102 545-3 V1.2.1 (2009-02)

Reference
RTS/BRAN-004T008-3-R1
Keywords
ATS, broadband, DLC, FWA, HiperMAN,
point to multipoint, radio, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2009.
© WIMAX Forum 2009.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 102 545-3 V1.2.1 (2009-02)
Contents
Intellectual Property Rights . 6
Foreword . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Abstract Test Method (ATM) . 9
4.1 Test architecture . 9
4.1.1 Test method . 9
4.1.1.1 What is notional upper tester? . 9
4.1.2 Test machine operational parameters . 11
4.1.3 Test machine configuration. 12
4.1.3.1 Presentation . 12
4.1.3.2 Test suite TTCN-3 development concept . 13
4.1.3.3 Test configurations for SS/MS . 14
4.1.3.4 Test configurations for BS . 16
4.1.4 Re-use of existing test specifications . 17
4.1.5 Test architecture . 18
4.1.5.1 Common test architecture . 18
4.1.5.1.1 Single Test Component . 18
4.1.5.1.2 Multiple Test Components . 19
4.2 Description of the ports and their associated primitives . 20
4.2.1 The MacMessagePort type. . 20
4.2.1.1 Description . 20
4.2.1.2 Primitives of the MacMsg port. 20
4.2.2 The MacBcMessagePort type. . 21
4.2.2.1 Description . 21
4.2.2.2 Primitives of the BcMacMsg port . 21
4.2.3 The MacPduPort type. . 22
4.2.3.1 Description . 22
4.2.3.2 Primitives of the MacPdu port . 22
4.2.4 The PhyPort type . 24
4.2.4.1 Description . 24
4.2.4.2 Primitives of the Phy Port . 24
4.2.5 The TaPort type. . 25
4.2.5.1 Description . 25
4.2.5.2 Primitives of the TaPort . 25
4.3 Port mapping rules. 26
4.4 PDU sending/receiving rules . 26
5 Untestable Test Purposes (TP) . 26
6 ATS conventions . 27
6.1 Testing conventions . 27
6.1.1 Testing States . 27
6.1.2 HiperMAN default values: Reception and transmission at ATS level . 27
6.1.3 Templates . 27
6.1.4 Functions . 27
6.2 Naming conventions . 28
6.2.1 General guidelines . 28
6.2.2 Test Case (TC) identifier . 29
6.3 Service Flow parameter support . 30
ETSI
4 ETSI TS 102 545-3 V1.2.1 (2009-02)
6.3.1 CsSpecification support . 30
6.3.2 DataDeliveryServiceType . 31
6.4 Dispatching of test cases over TTCN modules. 31
7 External functions . 32
8 Test strategies . 32
8.1 HARQ testing . 33
8.1.1 HarqAckNack PHY port message . 33
8.1.2 HARQ TA Primitives . 33
8.1.3 HARQ Broadcast Message Filter . 33
8.1.4 HARQ external Functions . 33
8.2 Fast Feedback testing . 34
8.2.1 CQICH PHY port message . 34
8.2.2 CQICH TA Primitives . 34
8.2.3 CQICH Broadcast Message Filter . 34
8.2.4 CQICH external Functions . 34
8.3 Handover testing . 35
8.3.1 Testing Serving BS . 35
8.3.2 Testing Target BS . 36
8.3.2 Testing MS with Handover or MBS procedure . 37
8.4 Processing of EAP messages . 37
8.5 Handling MAC PDU with Fragmentation, Packing or Concatenation . 38
8.5.1 MS (IUT) Processing DL MAC PDUs with FRAG Subheader . 38
8.5.2 MS (IUT) Processing DL MAC PDU with PACK Subheaders . 38
8.5.3 MS (IUT) Processing DL MAC PDU with PACK and FRAG Subheaders. 39
8.5.4 MS (IUT) Processing concatenated DL MAC PDUs . 39
8.5.5 MS (IUT) Generating UL MAC PDU with FRAG Subheader . 39
8.5.6 MS (IUT) Generating UL MAC PDU with PACK Subheaders . 39
8.5.7 MS (IUT) Generating concatenated UL MAC PDUs . 40
8.5.8 BS (IUT) processing UL MAC PDUs with FRAG Subheader . 40
8.5.9 BS (IUT) processing concatenated UL MAC PDUs . 40
8.5.10 BS (IUT) generating DL MAC PDU with FRAG Subheader . 41
8.5.11 BS (IUT) generating DL MAC PDU with PACK Subheaders . 41
8.6 Service Flows management for testing BS . 41
8.6.1 Introduction. 41
8.6.2 Handling of service flows in the default. . 42
8.6.3 Global variables used for the service flow management. 43
8.6.4 How to invoke a required SF that is not available . 44
Annex A (normative): WiMAX/HiperMAN 1.3.1 Abstract Test Suite (ATS) . 45
A.1 The TTCN-3 Module. 45
Annex B (normative): WiMAX/HiperMAN 1.3.1 Partial PIXIT proforma for IUT BS . 46
Annex C (normative): WiMAX/HiperMAN 1.3.1 Partial PIXIT proforma for IUT MS . 47
Annex D (normative): WiMAX/HiperMAN 1.3.1 PCTR Proforma for IUT BS . 48
D.1 Identification summary. 48
D.1.1 Protocol conformance test report . 48
D.1.2 IUT identification . 48
D.1.3 Testing environment . 48
D.1.4 Limits and reservation . 49
D.1.5 Comments. 49
D.2 IUT Conformance status . 49
D.3 Static conformance summary . 49
D.4 Dynamic conformance summary . 50
D.5 Static conformance review report . 50
D.6 Test campaign report . 51
ETSI
5 ETSI TS 102 545-3 V1.2.1 (2009-02)
D.7 Observations . 55
Annex E (normative): WiMAX/HiperMAN 1.3.1 PCTR Proforma for IUT MS . 56
E.1 Identification summary. 56
E.1.1 Protocol conformance test report . 56
E.1.2 IUT identification . 56
E.1.3 Testing environment . 56
E.1.4 Limits and reservation . 57
E.1.5 Comments. 57
E.2 IUT Conformance status . 57
E.3 Static conformance summary . 57
E.4 Dynamic conformance summary . 58
E.5 Static conformance review report . 58
E.6 Test campaign report . 59
E.7 Observations . 64
Annex F (normative): HTML documentation . 65
Annex G (informative): Bibliography . 66
History . 67

ETSI
6 ETSI TS 102 545-3 V1.2.1 (2009-02)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Broadband Radio Access
Networks (BRAN).
The present document was developed on the basis of the Abstract Test Suite (ATS) specification for HiperMAN
systems that was in the advanced stage of development when the work was reoriented to produce joint
HiperMAN/WiMAX specifications.
The present document is part 3 of a multi-part deliverable covering Broadband Radio Access Networks (BRAN);
HiperMAN; Conformance Testing for WiMAX/HiperMAN 1.3.1, as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS) proforma";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP)";
Part 3: "Abstract Test Suite (ATS)".
ETSI
7 ETSI TS 102 545-3 V1.2.1 (2009-02)
1 Scope
The present document contains the Abstract Test Suite (ATS) to test BRAN HiperMAN1.3.1/WiMAX systems for
conformance.
The objective of the present document is to provide a basis for conformance tests for BRAN HiperMAN/WiMAX
equipment giving a high probability of air interface inter-operability between different manufacturer's BRAN
HiperMAN/WiMAX equipment.
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [5] and ISO/IEC 9646-2 [6]) as well as
the ETSI rules for conformance testing (ETS 300 406 [4]) are used as a basis for the test methodology.
Annex A provides the Tree and Tabular Combined Notation (TTCN) part of the ATS.
Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the SS side
ATS.
Annex C provides the Protocol Conformance Test Report (PCTR) Proforma of the SS side ATS.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or non-
specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TS 102 178 (V1.2.1): "Broadband Radio Access Networks (BRAN); HiperMAN; Data Link
Control (DLC) layer".
[2] IEEE 802.16-2004: "IEEE Standard for Local and Metropolitan Area Networks - Part 16: Air
Interface for Fixed Broadband Wireless Access Systems".
ETSI
8 ETSI TS 102 545-3 V1.2.1 (2009-02)
[3] IEEE 802.16e-2005: "IEEE Standard for Local and metropolitan area networks - Part 16: Air
Interface for Fixed and Mobile Broadband Wireless Access Systems. Amendment 2: Physical and
Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands and
Corrigendum 1".
[4] ETSI ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[5] ISO/IEC 9646-1/ITU-T Recommendation X.290: "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 1: General concepts".
[6] ISO/IEC 9646-2/ITU-T Recommendation X.291: "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite
specification".
[7] ISO/IEC 9646-6: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 6: Protocol profile test specification".
[8] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance Statements".
[9] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[10] IEEE P802.16-2004/Cor1/D3: "Corrigendum to IEEE Standard for Local and Metropolitan Area
Networks - Part 16: Air Interface for Fixed Broadband Wireless Access Systems".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [8], TS 102 178 [1],
IEEE 802.16-2004 [2] and IEEE 802.16e-2005 [3] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TS 102 178 [1], ISO/IEC 9646-1 [5],
ISO/IEC 9646-6 [7], ISO/IEC 9646-7 [8], IEEE 802.16-2004 [2], IEEE 802.16e-2005 [3] and the following apply:
ATS Abstract Test Suite
BS Base Station
BW BandWidth
CID Connection IDentifier
CS Convergence Sublayer
FDD Frequency Division Duplexing
IUT Implementation Under Test
MAC Medium Access Control Layer
MS Mobile Station
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiple Access
PHY Physical LaYer
ETSI
9 ETSI TS 102 545-3 V1.2.1 (2009-02)
PIXIT Partial Protocol Implementation Extra Information for Testing
PMP Point-to-MultiPoint
QAM Quadrature Amplitude Modulation
QPSK Quadrature Phase Shift Keying
REQ REQuest
RNG RaNGing
RSP ReSPonse
RTG Receive/Transmit Transition Gap
SS Subscriber Station
SUT System Under Test
TC Test Case
TLV Type, Length, Value
TP Test Purposes
TTCN Test and Test Control Notation
TTG Transmit/Receive Transition Gap
4 Abstract Test Method (ATM)
This clause describes the ATM used to test the HiperMAN DLC layer at the BS side and at the SS side.
4.1 Test architecture
4.1.1 Test method
The test method chosen is the remote test method with notional upper tester. Remote test method means that the test
tool (the test machine + the executable test suite) shall behave as a BS when the IUT is an SS and shall behave as an SS
when the IUT is a BS. Notional upper tester means that it is possible to trigger and to force the IUT to execute
predefined actions.
Example: Adding a new service flow with defined parameters, sending data over a known service flow, etc.
This could be done by a specific and proprietary application layer inside the IUT or by other procedures clearly
described by the IUT's manufacturer (PIXIT question). As the exchange between the test system and the IUT is the air
interface, the PHY layer of the test machine shall be totally conformant with the corresponding PHY layer specification
to use the remote test method.
4.1.1.1 What is notional upper tester?
Usually the IUT is not only a plane containing Convergence, MAC and PHY layers, but a real product to be marketed
after testing, and therefore the IUT contains also application software to accomplish the purpose of the final product. In
that case, the application inside the IUT could be commanded to generate events in direction of the transmission
sub layers that shall be used by the testing software as expected IUT's actions. The application layer is the Upper tester
as defined in ISO 9646. It is also a notional upper tester, because the test designer cannot determine all of the possible
applications that are only market driven.
Considering the explanation of the former paragraph, in terms of source code writing, requesting a notional upper tester
action is the combination of the call of an external function and a PIXIT parameter. The external function asks the test
laboratory operator to execute the procedure described in the PIXIT parameter. If the action is possible to obtain the
external function succeeds, otherwise the test execution becomes inconclusive. The PIXIT parameter is a "how to"
question, for which the product manufacturer has to explain the procedure to be used in the IUT to obtain the required
action.
Figures 1 to 4 show some examples of possible notional upper tester.
ETSI
10 ETSI TS 102 545-3 V1.2.1 (2009-02)

TESTER IUT
Debug Software
Debug
console
TTCN-3 code
Notional UT
Figure 1: Debug notional upper tester

TESTER IUT
Network Application
Network
simulator
TTCN-3 code
Notional UT
Figure 2: Network driven notional upper tester
ETSI
11 ETSI TS 102 545-3 V1.2.1 (2009-02)

TESTER IUT
Internal maintenance
application like traffic
Maintenance
generator and loop back
console
responder
TTCN-3 code
Notional UT
Figure 3: Maintenance application notional upper tester

TESTER IUT
Phone application
TTCN-3 code
Notional UT
Figure 4: Phone application notional upper tester
4.1.2 Test machine operational parameters
The test machine operational parameters such as frequency, channels, sub channels, power level, etc., could be
initialized by static and/or dynamic method.
The static method could be:
1) operational parameters included in the firmware or ROM;
2) operational parameters included in a configuration file executed at power up;
3) other static technique;
4) no default or static operational parameters setting.
ETSI
12 ETSI TS 102 545-3 V1.2.1 (2009-02)
The dynamic method could be:
1) before the test cases execution at the beginning of the test campaign and valid for a list of TCs;
2) during the test case execution at the beginning of the test case itself;
3) everywhere during test case execution.
The possibility to acquire and to set all of the operational parameters during the test case execution is a main key to
cover all of the requirements to be tested by the TTCN-3 test code.
Considering all of the techniques exposed above, it is possible that the configuration of the operational parameters is
done either before the beginning of the TTCN-3 environment or during the initialization of the TTCN-3 environment or
during the preamble of a test case. The recommended method is the initialization during preamble of the test case.
Another important problem is the reconfiguration on the fly of some operational parameters. To solve this problem, it is
recommended that the test case itself shall be able to start and stop the PHY layer and all of its environments during test
case execution.
4.1.3 Test machine configuration
4.1.3.1 Presentation
There are six test machine configurations to allow the complete testing of the required functionalities of the
specification.
The test machine configurations are:
1) test machine simulates a BS with OFDM PHY (IUT is a SS with OFDM PHY);
2) test machine simulates a BS with OFDMA PHY (IUT is a SS with OFDMA PHY);
3) test machine simulates a SS with OFDM PHY (IUT is a BS with OFDM PHY);
4) test machine simulates a SS with OFDMA PHY (IUT is a BS with OFDMA PHY);
5) test machine simulates two BS, each of them with OFDM PHY (IUT is an MS with OFDM PHY), This
configuration is used for handover and mobility testing;
6) test machine simulates two BS, each of them with OFDMA PHY (IUT is an MS with OFDMA PHY), This
configuration is used for handover and mobility testing;
7) test machine simulates one SS and one BS, each of them with OFDM PHY (IUT is a BS with OFDM PHY);
8) test machine simulates one SS and one BS, each of them with OFDMA PHY (IUT is a BS with OFDMA
PHY).
NOTE: For a very small number of specification requirements, it may be useful to have a configuration with three
simulated BS. This increases the number of test machine configuration by two (one for OFDM and one
for OFDMA). Considering the effort of hardware and software development and the corresponding costs,
implementation of these configurations should be investigated very carefully, and interoperability testing
may be more suitable than conformance testing.
The configurations 1, 2, 3 and 4 can be covered by a single testing approach. The configurations 5, 6, 7 and 8 shall be
covered by a concurrent testing approach (it is necessary to monitor and synchronize the two simulated BS test code to
obtain a consistent behaviour and a consistent test verdict). The use of the distributed testing possibilities of TTCN-3 is
recommended for the physical architecture of the test machine for the test configurations 5 and 6.
The number of physical test machines to cover the eight test configurations could comprise between one and eight
depending of the level of flexibility and parameterization of the hardware design made by the test tool manufacturer. A
physical test machine could also be constituted by a number greater than one of real hardware machine
(example: intelligent PHY plane connected to one or more PC executing the TTCN-3 code).
ETSI
13 ETSI TS 102 545-3 V1.2.1 (2009-02)
For similar reasons the number of test suites could comprise between 1 and 8 depending of the level of
parameterization, by use of PICS and PIXIT items, used to design the TTCN-3 code. The conditional compilation may
be used to have only one source code and many generated test suite. In terms of performance, it is preferable to have
static conditional code generation to shorten the length of the test suite and improve the time execution rather than to
have dynamic conditional alternatives controlled by PICS or PIXIT items. In terms of readability and maintenance of
the test code it is preferable to have a one to one mapping between the test code and the test machine configuration. The
use of libraries, packages and other recent technique of source code management are recommended.
4.1.3.2 Test suite TTCN-3 development concept
The possible Test suite TTCN-3 development concepts are shown in figures 5, 6 and 7.
TTCN-3 source code TTCN-3 deliverables
Test configuration
Compilation
Project 1
ATS 1
ETS Configuration 1
Test system 1
Project 2
ATS 2 ETS Configuration 2
Test system 2
.
.
. .
Constants
Types
.
Template
.
Functions . .
Source code
.
.
. .
Project n
ATS n
ETS Configuration n
Test system n
Figure 5: TTCN-3 development concept 1
TTCN-3 source code TTCN-3 deliverables
Test configuration
Project Conditional
Compilation
ETS Configuration 1
ETS Configuration 2
.
Constants
Generic
Types
Test system
ATS
Template
Functions .
Source code
.
ETS Configuration n
Figure 6: TTCN-3 development concept 2
ETSI
14 ETSI TS 102 545-3 V1.2.1 (2009-02)
TTCN-3 source code TTCN-3 deliverables
Test configuration
Project Compilation
Generic ETS covering
Constants
all configurations by
Generic
Types
Test system
dynamic selection of
ATS
Template
code part by using PICS
Functions
and PIXIT items
Source code
Figure 7: TTCN-3 development concept 3
For all of the three TTCN-3 development concepts, the Test Configuration shall be done dynamically based on PIXIT
and PICS parameters.
According to a consensus between the TTCN-3 development team and the Test tool manufacturers, the TTCN-3
development concepts 1 showed above will be used for the real development.
4.1.3.3 Test configurations for SS/MS
There are four normal configurations and two optional configurations for SS/MS testing.
The configuration 1 is defined and used for functionality that requires only interaction between the tested OFDM
SS/MS and one OFDM BS. This configuration is shown in figure 8.
BS
SS/M S
P HY O F DM
(T e ste r)
(IU T )
Figure 8: Configuration 1 for SS/MS
The configuration 2 is defined and used for functionality that requires only interaction between the tested OFDMA
SS/MS and one OFDMA BS. This configuration is shown in figure 9.
BS
SS/M S
P H Y OF D M A
(T e ste r)
(IU T )
Figure 9: Configuration 2 for SS/MS
ETSI
15 ETSI TS 102 545-3 V1.2.1 (2009-02)
The configuration 5 is defined and used when an OFDM SS/MS has to interact with two OFDM BSs. The concurrent
TTCN-3 facilities are used in this configuration. This configuration is shown in figure 10.
Tester
SS/M S
BS1
(IU T )
P H Y O F DM
M
T
C
BS2
Figure 10: Configuration 5 for SS/MS
The configuration 6 is defined and used when an OFDMA SS/MS has to interact with two OFDMA BSs. The
concurrent TTCN-3 facilities are used in this configuration. This configuration is shown in figure 11.
Tester
SS/M S
BS1
(IU T )
P H Y O F DM A
M
T
C
BS2
Figure 11: Configuration 6 for SS/MS
The optional configuration Opt1 is defined and used when an OFDM SS/MS has to interact with more than two OFDM
BSs. The concurrent TTCN-3 facilities are used in this configuration. This configuration is shown in figure 12.
Tester
SS/M S
P H Y O F DM
BS1
(IU T )
BS2
BS3
Figure 12: Configuration Opt1 for SS/MS
The optional configuration Opt2 is defined and used when an OFDMA SS/MS has to interact with more than two
OFDMA BSs. The concurrent TTCN-3 facilities are used in this configuration. This configuration is shown in
figure 13.
Tester
SS/M S
P H Y O F DM A
BS1
(IU T )
BS2
BS3
Figure 13: Configuration Opt2 for SS/MS
ETSI
MTC MTC
16 ETSI TS 102 545-3 V1.2.1 (2009-02)
4.1.3.4 Test configurations for BS
There are two normal configurations and four optional configurations for BS testing.
The configuration 3 is defined and used for functionality that requires only interaction between the tested OFDM BS
and one OFDM MS/SS. This configuration is shown in figure 14.
SS/M S
BS
P HY O F DM
(T e ste r)
(IU T )
Figure 14: Configuration 3 for BS
The configuration 4 is defined and used for functionality that requires only interaction between the tested OFDMA BS
and one OFDMA MS/SS. This configuration is shown in figure 15.
SS/M S
BS
P H Y OF D M A
(T e ste r)
(IU T )
Figure 15: Configuration 4 for BS
The optional configuration Opt3 is defined and used when an OFDM BS has to interact with two OFDM MS/SS. The
concurrent TTCN-3 facilities are used in this configuration. This configuration is shown in figure 16.
Tester
BS
MS/
(IU T )
SS1
P H Y O F DM
M
T
C MS/
SS2
Figure 16: Configuration Opt3 for BS
The optional configuration Opt4 is defined and used when an OFDMA BS has to interact with two OFDMA MS/SS.
The concurrent TTCN-3 facilities are used in this configuration. This configuration is shown in figure 17.
Tester
BS
MS/
(IU T )
SS1
P H Y O F DM A
M
T
C
MS/
SS2
Figure 17: Configuration Opt4 for BS
ETSI
17 ETSI TS 102 545-3 V1.2.1 (2009-02)
The optional configuration Opt5 is defined and used when an OFDM BS has to interact with one OFDM BS and one
OFDM MS/SS. The concurrent TTCN-3 facilities are used in this configuration. This configuration is shown in
figure 18.
Tester
BS
MS/
(IU T )
SS1
P H Y O F DM
M
T
C
BS
Figure 18: Configuration Opt5 for BS
The optional configuration Opt6 is defined and used when an OFDMA BS has to interact with one OFDMA BS and one
OFDMA MS/SS. The concurrent TTCN-3 facilities are used in this configuration. This configuration is shown in
figure 19.
Tester
BS
MS/
(IU T )
SS1
P H Y O F DM A
M
T
C
BS
Figure 19: Configuration Opt6 for BS
4.1.4 Re-use of existing test specifications
Due to existing development for IEEE 802.16-2004 [2] and ETSI HiperMAN, it is preferable if not essential to reuse as
much of the existing test specifications.
Nevertheless, considering the preceding considerations such as hardware configuration and test configuration, it appears
that the existing TTCN code may be only partially re-usable. For TTCN-3 code, the constants, types, templates and
internal/external functions could be re-used and extended, but the other parts are certainly not in line with the new
hardware and software configuration.
Considering that, there are two possibilities:
1) Starting from scratch with small re-use of existing test specifications.
2) Defining a test architecture that included the architecture defined for IEEE 802.16-2004 [2] and
ETSI HiperMAN as near as possible and adding small changes in the actual TTCN-3 code.
According to a consensus between the TTCN-3 development team and the Test tool manufacturers, the second
possibility showed above will be used for the real development.
ETSI
18 ETSI TS 102 545-3 V1.2.1 (2009-02)
4.1.5 Test architecture
4.1.5.1 Common test architecture
4.1.5.1.1 Single Test Component
Figures 20 and 21 describe the DLC BS/SS Test Configuration for testing the DLC layer of a product implementing the
HiperMAN base standard. More information for these architectures is provided below. Figure 20 is related to single
testing. Figure 21 is related to concurrent testing.
HiperMAN/WiMAX DLC Test System
TTCN-3 Test Case
Upper
Tester
HiperMAN/WiMAX SUT
External DLC
function
TTCN-3
control
Upper Tester
Application
Cnfg
mac mac mac
Operator
Start Msg Bc Pdu
Action
Stop Msg
and Feedback
DLC
TRI
(IUT)
SUT Adapter Broadcast
Emulation
Proprietary Proprietary
PHY
WirelessMAN-OFDM
Transport Transport
Transport
and/or OFDMA PHY
Figure 20: Single DLC BS/SS Test Configuration
DLC TTCN-3
...