ETSI TS 102 385-3 V2.5.1 (2008-12)

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

�
2 ETSI TS 102 385-3 V2.5.1 (2008-12)

Reference
RTS/BRAN-004T002-3R5
Keywords
ATS, broadband, DLC, FWA, HiperMAN, MAC,
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 2008.
© WIMAX Forum 2008.
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 385-3 V2.5.1 (2008-12)
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 IEEE 802.16-2004 and ETSI HiperMAN protocol layers.9
4.2 SS Test architecture.10
4.3 BS Test architecture .11
5 Untestable Test Purposes.12
6 ATS conventions.12
6.1 Testing conventions.12
6.1.1 Testing States.12
6.1.2 HiperMAN default values: Reception and transmission at ATS level.13
6.1.3 Templates.13
6.1.4 Functions.13
6.2 Naming conventions.13
6.2.1 General guidelines.13
6.2.2 Test Case (TC) identifier .14
7 External functions.16
7.1 List organized by the type of external function .16
7.1.1 Functions to trigger the IUT .16
7.1.1.1 IUT is a BS.16
7.1.1.2 IUT is a SS .16
7.1.2 Functions to trigger the Tester .16
7.1.2.1 IUT is a BS.16
7.1.2.2 IUT is a SS .16
7.1.3 Functions to check internal Tester's event .17
7.1.3.1 IUT is a BS.17
7.1.3.2 IUT is a SS .17
7.1.3.3 Function is independent of the IUT's type.17
7.1.4 Functions for computation .17
7.1.4.1 IUT is a BS.17
7.1.4.2 IUT is a SS .17
7.1.4.3 Function is independent of the IUT's type.18
7.1.5 Specific TA functions.18
7.1.5.1 IUT is a BS.18
7.1.5.2 IUT is a SS .18
7.1.5.3 Function is independent of the IUT's type.19
7.1.6 Functions for Operator action .19
7.1.6.1 IUT is a BS.19
7.1.6.2 IUT is a SS .19
7.1.7 Functions for Interaction with external servers (IP connectivity).19
7.1.7.1 IUT is a BS.19
7.1.7.2 IUT is a SS .20
7.1.7.3 Function is independent of the IUT's type.20
7.2 Description.20
7.2.1 Functions to trigger the IUT .20
ETSI
4 ETSI TS 102 385-3 V2.5.1 (2008-12)
7.2.1.1 IUT is a BS.20
7.2.1.2 IUT is a SS .22
7.2.2 Functions to trigger the Tester .22
7.2.2.1 IUT is a BS.22
7.2.2.2 IUT is a SS .23
7.2.3 Functions to check internal Tester's event .23
7.2.3.1 IUT is a BS.23
7.2.3.2 IUT is a SS .24
7.2.3.3 Function is independent of the IUT's type.24
7.2.4 Functions for computation .24
7.2.4.1 IUT is a BS.24
7.2.4.2 IUT is a SS .25
7.2.4.3 Function is independent of the IUT's type.26
7.2.5 Specific TA functions.27
7.2.5.1 IUT is a BS.27
7.2.5.2 IUT is a SS .28
7.2.5.3 Function is independent of the IUT's type.32
7.2.6 Functions for Operator action .33
7.2.6.1 IUT is a BS.33
7.2.6.2 IUT is a SS .33
7.2.7 Functions for Interaction with external servers (IP connectivity).33
7.2.7.1 IUT is a BS.33
7.2.7.1.1 IUT side.33
7.2.7.1.2 TA side .34
7.2.7.2 IUT is a SS .34
7.2.7.2.1 IUT side.34
7.2.7.2.2 TA side .35
7.2.7.3 Function is independent of the IUT's type.36
7.2.7.3.1 IUT side.36
7.2.7.3.2 TA side .36
Annex A (normative): Abstract Test Suite (ATS) .37
A.1 The TTCN-3 Module.37
Annex B (normative): Partial PIXIT proforma for HiperMAN DLC .38
B.1 Identification summary.38
B.2 ATS summary.38
B.3 Test laboratory.38
B.4 Client identification.39
B.5 SUT.39
B.6 Protocol layer information.39
B.6.1 Protocol identification.39
B.6.2 IUT information.40
B.6.2.1 Timers.40
B.6.2.2 Common Configuration.40
B.6.2.3 DL-MAP message.40
B.6.2.4 DCD message.40
B.6.2.5 UCD message.41
B.6.2.6 Common RNG Pixits.41
B.6.2.7 RNG-REQ message.41
B.6.2.8 RNG-RSP message.42
B.6.2.9 Common SBC Pixits.42
B.6.2.10 AUTH and KEY messages .43
B.6.2.11 Common REG Pixits.44
B.6.2.12 Common DSA Pixits .45
B.6.2.13 BWA.46
B.6.2.14 DBPC message.46
B.6.2.15 ICMP Echo Request and Reply messages .46
ETSI
5 ETSI TS 102 385-3 V2.5.1 (2008-12)
Annex C (normative): PCTR Proforma for HiperMAN DLC.47
C.1 Identification summary.47
C.1.1 Protocol conformance test report.47
C.1.2 IUT identification.47
C.1.3 Testing environment.47
C.1.4 Limits and reservation.48
C.1.5 Comments.48
C.2 IUT Conformance status .48
C.3 Static conformance summary.48
C.4 Dynamic conformance summary.49
C.5 Static conformance review report.49
C.6 Test campaign report.50
C.7 Observations.56
Annex D (informative): Bibliography.57
History .58

ETSI
6 ETSI TS 102 385-3 V2.5.1 (2008-12)
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.2.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 385-3 V2.5.1 (2008-12)
1 Scope
The present document contains the Abstract Test Suite (ATS) to test BRAN HiperMAN1.2.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 385-3 V2.5.1 (2008-12)
[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 for Physical
and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed
Bands".
[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/ITU-T Recommendation X.295: "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test
specification".
[8] ISO/IEC 9646-7/ITU-T Recommendation X.296: "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] ETSI TS 102 210: "Broadband Radio Access Networks (BRAN); HIPERMAN; System profiles".
2.2 Informative references
[i.1] ISO 3166 (all parts): "Codes for the representation of names of countries and their subdivisions".
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],
and IEEE 802.16-2004 [2] as corrected by Corrigendum 1 of 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] as corrected by
Corrigendum 1 of IEEE 802.16-2005 [3] and the following apply:
ATM Abstract Test Method
ATS Abstract Test Suite
BS Base Station
BW BandWidth
CID Connection IDentifier
CS Convergence Sublayer
DHCP Dynamic Host Configuration Protocol
DLC Data Link Control
IP Internet Protocol
IUT Implementation Under Test
MAC Medium Access Control
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiple Access
PCTR Protocol Conformance Test Report
ETSI
9 ETSI TS 102 385-3 V2.5.1 (2008-12)
PIXIT Partial Protocol Implementation Extra Information for Testing
REQ REQuest
RNG RaNGing
RSP ReSPonse
RTG Receive/Transmit Transition Gap
SS Subscriber Station
SUT System Under Test
TC Test Case
TFTP Trivial File Transfer Protocol
TLV Type, Length, Value
TP Test Purposes
TTCN Tree and Tabular Combined Notation
TTG Transmit/Receive Transition Gap
4 Abstract Test Method (ATM)
This clause describes the ATM used to test the IEEE 802.16-2004 [2] and HiperMAN DLC layer at the BS side and at
the SS side.
4.1 IEEE 802.16-2004 and ETSI HiperMAN protocol layers
Figure 1 shows the mapping of the protocol layers of IEEE 802.16-2004 [2] and ETSI HiperMAN [1]. In the remaining
text and figures of the present documentument only the ETSI terminology is used.
IEEE ETSI
IEEE 802.16-2004 HiperMAN
System Profiles (§12) System Profiles (TS 102 210)
MAC (§6, §7) DLC (TS 102 178)
OFDMA (§8.4)
PHY (TS 102 177)
OFDM (§8.3)
SCa (§8.2)
SC (§8.1)
Figure 1: IEEE 802.16-2004 [2] and ETSI HiperMAN protocol layers
ETSI
10 ETSI TS 102 385-3 V2.5.1 (2008-12)
4.2 SS Test architecture
Figure 2 describes the DLC SS Test Configuration for testing the DLC layer of a product implementing the HiperMAN
base standard. More information for this architecture is provided below.
HiperMAN/WiMAX DLC Test System
TTCN-3 Test Case
TTCN-3 DLC
HiperMAN/WiMAX SS SUT
Upper TTCN-3
BS Simu
Tester
Upper Tester
mac
mac mac
Application
Bc
Msg Pdu
ActionReq
Msg
+
DataInd
DLC
TRI
(IUT)
Broadcast
SUT Adapter
Emulation
Proprietary
Proprietary
PHY
WirelessMAN-OFDM
Transport
Transport
Transport
PHY
Figure 2: DLC SS Test Configuration
The DLC SS Test Configuration provides 1 test component:
• DLC TTCN-3 uses macMsg port to send and receive MAC management messages that belong to the Initial
Ranging, Basic, Primary and Secondary connection. Final verdicts are set on the receive statements.
Additionally to the MAC message received, the real raw data received before decoding by the test adapter are
necessary for log interpretation and fields computation (i.e. checks of the HMAC digest for example). It is also
important to have received the EC bit to know if the received content is encrypted and the EKS key number to
know which of the two keys has to be used for decrypting.
• DLC TTCN-3 uses macPdu port to send and receive MAC PDUs. Final verdicts are set on the receive
statements.
• DLC TTCN-3 controls via external functions the Upper Tester Application. The Upper Tester Application
allows triggering of the IUT actions. Final verdicts are set on the return status of the external functions.
• DLC TTCN-3 controls via external functions the configuration of the Test Adapter. Final verdicts are set on
the return status of the external functions.
ETSI
11 ETSI TS 102 385-3 V2.5.1 (2008-12)
4.3 BS Test architecture
Figure 3 describes the DLC BS Test Configuration for testing the DLC layer of a product implementing the HiperMAN
base standard. More information for this architecture is provided below.
HiperMAN/WiMAX DLC Test System
TTCN-3 Test Case
DLC
TTCN-3
HiperMAN/WiMAX BS SUT
Upper TTCN-3
SS Simu
Tester
Upper Tester
mac mac mac
Application
Msg Bc Pdu
ActionReq
Msg
+
DataInd
DLC
TRI
(IUT)
SUT Adapter
Proprietary Proprietary
PHY
WirelessMAN-OFDM
Transport
Transport
PHY Transport
Figure 3: DLC BS Test Configuration
The DLC BS Test Configuration provides 1 test component:
• DLC TTCN-3 uses macMsg port to send and receive MAC management messages that belong to the Initial
Ranging, Basic, Primary and Secondary connection. Final verdicts are set on the receive statements.
Additionally to the MAC message received, the real raw data received before decoding by the test adapter is
necessary for log interpretation and fields computation (i.e. checks of the HMAC digest for example). It is also
important to receive the EC bit to know if the received content is encrypted and the EKS key number to know
which of the two keys has to be used for decrypting.
• DLC TTCN-3 uses macBcMsg port to receive MAC management messages that belong to the Broadcast
connection. Final verdicts are set on the return status of the receive functions. The MAC management
messages that the Test Adapter shall support are listed in table 1.
• DLC TTCN-3 uses macPdu port to send and receive MAC PDUs. Final verdicts are set on the receive
statements.
• The broadcast emulation handles the reception of the broadcast messages.
ETSI
12 ETSI TS 102 385-3 V2.5.1 (2008-12)
• DLC TTCN-3 controls via external functions the Upper Tester Application. Upper Tester Application allows
triggering IUT actions. Final verdicts are set on the return status of the external functions.
• DLC TTCN-3 controls via external functions the configuration of the Test Adapter. Final verdicts are set on
the return status of the external functions.
Table 1: Port macBcMsg
MAC management messages
DlMapMessage
UlMapMessage
DcdMessage
UcdMessage
5 Untestable Test Purposes
This clause gives a list of TP, which are not implemented in the ATS due to the chosen ATM or other restrictions.
Table 2: Untestable TP
Test Case Name Reason
void
6 ATS conventions
The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions
made for the development of the ATS. These conventions shall be considered during any later maintenance or further
development of the ATS.
The ATS conventions contain two clauses, the naming conventions and the implementation conventions. The naming
conventions describe the structure of the naming of all ATS elements. The implementation conventions describe the
functional structure of the ATS.
To define the ATS, the guidelines of ETS 300 406 [4] were considered.
6.1 Testing conventions
6.1.1 Testing States
BS Null: The BS is switched on and sends broadcast messages.
SS Null: The SS is switched on and is ready to receive broadcast messages.
ETSI
13 ETSI TS 102 385-3 V2.5.1 (2008-12)
6.1.2 HiperMAN default values: Reception and transmission at ATS level
IEEE 802.16-2004 [2] as corrected by Corrigendum 1 of IEEE 802.16e-2005 [3] (but not taking into account the
Amendment 2) lists many default TLV values. IEEE 802.16-2004 [2] says that devices SHOULD NOT transmit TLVs
if the default value applies. However, this is NOT a requirement. Thus, one tested device may not transmit the default
TLVs (or a subset of these default TLVs) while another may transmit all TLVs including the defaults. Including all the
possible combinations of sent and received default TLVs in an ATS is problematic:
• Therefore, for ATS purposes, all TLVs are assumed to be sent and received at the ATS level.
• The Test Adapter will fill in the missing received TLVs with a TLV containing the default value and pass it up
to the ATS.
• The Test Adapter may or may not transmit default TLVs received from the ATS to the IUT. This is a test
equipment vendor decision.
6.1.3 Templates
• Separate templates are defined for use in sending and receiving operations.
• Template definitions should avoid using matching attributes such as "*" or "?" for complete structured values,
e.g. record or set of values.
• PIXIT parameter values are passed as parameters into templates.
6.1.4 Functions
The WMx ATS differentiates between external functions for which only the signature is specified and functions
completely defined in the ATS. The completely defined functions are separated according to their use for SS or BS
testing and preamble and postamble functions.
The SS and BS testing functions are grouped in a general configurations functions group and separate groups with
functions used for testing different types of functionality.
Each type of function is implemented in a separate module, although there may be multiple modules for each function
type. The following general rules apply:
• Functions use the "runs on" statement wherever this is possible.
• Each function provides a return value wherever this is possible. The return value used is the enumeration type
"FncRetCode" defined in the WMx_Types.ttcn file.
EXAMPLE: WMx_Types.FncRetCode.
• The stop statement is used only for controlled test component shutdown.
6.2 Naming conventions
6.2.1 General guidelines
The naming convention is based on the following underlying principles:
• in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the
type of TTCN-3 element it represents;
• suffixes should not be used except in those specific cases identified in table 7;
• prefixes and suffixes should be separated from the body of the identifier with an underscore ("_");
EXAMPLE 1: c_sixteen, t_wait_max.
ETSI
14 ETSI TS 102 385-3 V2.5.1 (2008-12)
• only module names, data type names and module parameters should begin with an upper-case letter. All other
names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter;
• the start of second and subsequent words in an identifier should be indicated by capitalizing the first character.
Underscores should not be used for this purpose.
EXAMPLE 2: f_authenticateUser.
Table 3 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix,
suffixes (if any) and capitalization.
Table 3: TTCN-3 naming convention
Language element Naming convention Prefix Suffix Example Notes
Module Use upper-case initial letter none none WMx_Templates
TSS grouping Use all upper-case letters none none TP_RT_PS_TR
Item group within a Use lower-case initial letter none none messageGroup
module
Data type Use upper-case initial letter none none SetupContents
List type identifiers Use upper-case initial letter none none DlMapIeList
Message template Use lower-case initial letter m_ none m_setupInit

Message template Use lower-case initial letters mw_ none mw_setupBasic
with wildcard or
matching expression
Port instance Use lower-case initial letter none none signallingPort
Test component ref Use lower-case initial letter none none userTerminal
Signature Use lower-case initial letter s_ none s_callSignature
none
External function Use lower-case initial letter xf_ xf_calculateLength()
none
Constant Use lower-case initial letter c_ c_maxRetransmission
Function Use lower-case initial letter f_ none f_authentication()
Altstep Use lower-case initial letter a_ none a_receiveSetup()
Altstep (Default) Use lower-case initial letter d_ none d_receiveOtherMessages()
Variable Use lower-case initial letter v_ none v_basicCid
Variable, global to Use lower-case initial letter g_ none g_ssSimu.basicCid
component
Timer Use lower-case initial letter t_ _min t_wait Note 1
_max t_auth_min
Module parameters Use all upper case letters none none Note 2
PICS values PIC_T7PXT_TNOAC
PIXIT values
External constant Use lower-case initial letter xc_ none xc_macId
none
Parameterization Use lower-case initial letter p_ p_macId
Enumerated Value Use lower-case initial letter e_ none e_synCpk
NOTE 1: If a time window is needed, the suffixes "_min" and "_max" should be appended.
NOTE 2: In this case it is acceptable to use underscore as a word delimiter.

6.2.2 Test Case (TC) identifier
Table 4: TC naming convention
TC_______H
= side type BS Base Station
SS Subscriber Station
= protocol group CDM Channel Descriptors and Maps
4 RLC Radio Link Control
INI Registration, IP Connectivity, and Parameter
Transfer
PKM Privacy and Key Management
DS Dynamic Services
BWA Bandwidth Allocation and Polling
RER Reset and Re-registration
CCC Clock Comparison
MAC MAC PDU Construction
ETSI
15 ETSI TS 102 385-3 V2.5.1 (2008-12)
TC_______H
PCS Packet CS
= function group MAP Map and Frame Structure
CD Channel Descriptors
CDC Channel Descriptor Change
IRNG Initial Ranging
PRNG Periodic Ranging
DBPC Downlink Burst Profile Management
SBC Negotiate Basic Capabilities
REG Registration
IPC IP Connectivity
AUTH Authentication/Authorization
TEK Encryption Key Transfer
SAM Security Association Management
EKS Encryption and Key Scheduling
DSA Dynamic Service Addition
DSC Dynamic Service Change
DSD Dynamic Service Deletion
REQ Request/Grant
MCP Multicast Polling
PACK Packing
FRAG Fragmentation
CAT PDU Concatenation
CRC Cyclic Redundancy Check (CRC)
ARQ ARQ
PCU Packet CS Usage
CLS Classification
CDS Classifier DSx Signalling
PHS Payload Header Suppression
= subfunction group INIT Initialization
OPN Operation
RLV Relevance
KU Key Usage
ENC Encryption
DEC Decryption
= initiator of procedure or direction of flow BsIni Procedure is initiated by BS
SsIni Procedure is initiated by SS
DL Downlink
UL Uplink
= type of testing BV Valid Behavior Tests
BI Invalid Syntax or Behavior Tests
BO Inopportune Behavior Tests
TI Timer and Counter Tests
= sequential number Hnnn (H000, H001, …)

EXAMPLE: TP identifier: TP/SS/RLC/IRNG/BV-H002
TC identifier: TC_SS_RLC_IRNG_BV_H002.
ETSI
16 ETSI TS 102 385-3 V2.5.1 (2008-12)
7 External functions
7.1 List organized by the type of external function
7.1.1 Functions to trigger the IUT
7.1.1.1 IUT is a BS
Table 5: Trigger BS as IUT
Nbr Trigger IUT
1 xf_triggerBsEnableProfile
2 xf_triggerBsDsaReq
3 xf_triggerBsDsaReq_pcs
4 xf_triggerBsDsaReq_ip
5 xf_triggerBsDsaReq_prio
6 xf_triggerBsUlDsaReq_CSType
7 xf_triggerBsDsdReq
8 xf_dataReceivedOnIut
9 xf_triggerBsDataTransmission
10 xf_commandIUTIgnoreNextMessage
11 xf_triggerBsDsaReq_newSa
12 xf_triggerBsDataTransmission_classifier

7.1.1.2 IUT is a SS
Table 6: Trigger SS as IUT
Nbr Trigger IUT
1 xf_triggerSsDataTransmission
2 xf_triggerSsSfDeleteLocal
3 xf_triggerSsChangeServiceFlow
4 xf_triggerSsDsaReq
5 xf_triggerSsDataTransmission_priority

7.1.2 Functions to trigger the Tester
7.1.2.1 IUT is a BS
Table 7: Trigger the Tester when IUT is a BS
Nbr Trigger Tester
1 xf_piggyBackRequest
2 xf_triggerSsSimuDataTransmission_wrong_crc

7.1.2.2 IUT is a SS
Table 8: Trigger the Tester when IUT is a SS
Nbr Trigger Tester
1 xf_getFocusedRegionParams
2 xf_checkFocusedContentionSignal
3 xf_getRegionFullParams
4 xf_getDataGrantParams
ETSI
17 ETSI TS 102 385-3 V2.5.1 (2008-12)
7.1.3 Functions to check internal Tester's event
7.1.3.1 IUT is a BS
Table 9: Check internal Tester event when IUT is a BS
Nbr Check internal Tester event
1 xf_checkEthernetData
2 xf_checkServiceFlow
3 xf_checkIpv4SAP
4 xf_checkBsnrtPSUplinkServiceFlow
5 xf_checkBsrtPSUplinkServiceFlow

7.1.3.2 IUT is a SS
Table 10: Check internal Tester event when IUT is a SS
Nbr Check internal Tester event
1 xf_checkIPv4overEthernetSAP
7.1.3.3 Function is independent of the IUT's type
Table 11: Check internal Tester event for BS and SS
Nbr Check internal Tester event
1 xf_checkEthernetSAP
7.1.4 Functions for computation
7.1.4.1 IUT is a BS
Table 12: Computation function for BS
Nbr Computation
1 xf_calcCrc
2 xf_calcHcs
3 xf_calcRawDataDLHmacDigest
7.1.4.2 IUT is a SS
Table 13: Computation function for SS
Nbr Computation
1 xf_calcLen_pktClassificationRuleTLVs
2 xf_calcLen_qosEncodingTLVs
3 xf
...