SIST EN 301 811-1-3 V1.1.1:2006

• Abstract:

  The present document contains the Abstract Test Suite (ATS) to test the BRAN HIPERLAN Type 2; Packet based convergence layer; Part 1: Common part. The objective of the present document is to provide a basis for conformance tests for HIPERLAN Type 2 equipment giving a high probability of air interface inter-operability between different manufacturers' HIPERLAN Type 2 equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [3] and ISO/IEC 9646-2 [4]) as well as the ETSI rules for conformance testing (ETS 300 406 [2]) 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 MT side ATS. Annex C provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the AP side ATS. Annex D provides the Protocol Conformance Test Report (PCTR) Proforma of the MT side ATS. Annex E provides the Protocol Conformance Test Report (PCTR) Proforma of the AP side ATS.

• Status: Published
• Publication Date: 31-Jan-2006
• ICS: 33.060.01 - Radiocommunications in general
• ICS: 35.110 - Networking
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Feb-2006
• Due Date: 01-Feb-2006
• Completion Date: 01-Feb-2006
• Mandate: T-325
• Ref Project: ETSI EN 301 811-1-3 V1.1.1 (2001-01) - Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance testing for the packet based convergence layer; Part 1: Common part; Sub-part 3: Abstract Test Suite (ATS) specification

SIST EN 301 811-1-3 V1.1.1:2006 is the Slovenian adoption of the ETSI standard for conformance testing of Broadband Radio Access Networks (BRAN) HIPERLAN Type 2, packet based convergence layer, Part 1: Common part. It specifies the Abstract Test Suite (ATS) and the test method used to assess equipment for interoperability testing between different manufacturers' HIPERLAN Type 2 implementations. The document is aimed at test laboratories, implementers, and quality teams that need to prepare, run, or document conformance tests for Access Point (AP) and Mobile Terminal (MT) equipment.

What does SIST EN 301 811-1-3 V1.1.1:2006 specify?

SIST EN 301 811-1-3 V1.1.1:2006 specifies the ATS for testing the BRAN HIPERLAN Type 2 packet based convergence layer, Part 1: Common part. Its stated objective is to provide a basis for conformance tests that support a high probability of air interface inter-operability between equipment from different manufacturers.

The document organizes that material into the main clauses for scope, references, definitions and abbreviations, abstract test method, untestable test purposes, ATS conventions, and abstract testing service primitives. It then places the executable or record-keeping material in normative annexes.

Annex	What it covers
Annex A	The Abstract Test Suite (ATS), in TTCN graphical and machine-processable form
Annex B	Partial PIXIT proforma for the Common part CL MT side
Annex C	Partial PIXIT proforma for the Common part CL AP side
Annex D	PCTR proforma for the Common part CL MT side
Annex E	PCTR proforma for the Common part CL AP side

The test methodology is based on ISO/IEC 9646-1, ISO/IEC 9646-2, and ETSI ETS 300 406. In practice, that means the document is not a product protocol spec, but the test specification used to turn the protocol requirements into a repeatable conformance test campaign.

What are the key requirements of SIST EN 301 811-1-3 V1.1.1:2006?

SIST EN 301 811-1-3 V1.1.1:2006 defines how the common part of the packet based convergence layer is tested, how the test environment is arranged, and how ATS elements are named and reported. The key points are the test architecture, the supported configurations, the treatment of untestable test purposes, the ATS naming rules, and the test primitives used by the suite.

Test architecture and observation points

Clause 4 uses a single-party testing concept with a Lower Tester (LT), a Convergence Layer (CL) ATS in the remote BRAN H/2 test system, and a notional Upper Tester (UT). The ATS places the points of control and observation at the CLU PCO for U-plane events and the CLC PCO for C-plane events. In practice, this means the testing focuses on what goes in and out of the interface points, rather than on internal implementation details.

Configurations for MT and AP testing

Clause 4.2 defines two configurations for MT testing - a normal configuration using one AP, and a handover configuration using two APs. The handover configuration can use either a multi-sector AP or two separate APs, and it uses concurrent TTCN facilities. For AP testing, only the normal configuration with one MT is defined. This tells a lab which physical or simulated peers it must provide for each test run.

Untestable test purposes

Clause 5 lists test purposes that are not implemented in the ATS because of the chosen abstract test method or other restrictions. The practical result is that the ATS does not contain every possible test purpose from the TSS and TP material, and some test case identifiers are therefore not continuous. A user running the suite needs to rely on the documented ATS coverage, not on an assumption that every possible behavior is exercised.

ATS naming and implementation conventions

Clause 6 sets naming conventions for declarations, constraints, and dynamic test elements. It fixes the style for test suite parameters, test suite constants, test case identifiers, timers, labels, and verdict assignment markers, and it also defines how TTCN comments are used to reference the protocol standard. In practice, this keeps the ATS readable and maintainable, and it makes conformance logs easier to interpret.

Abstract testing service primitives

Clause 7 defines the abstract testing service primitives used by the suite:

• PCL_Configuration for tester control
• DLC_Association_request and DLC_Association_indication for C-plane association handling
• DUC_request and DUC_indication for C-plane data connection handling
• SAR_UNITDATA_request and SAR_UNITDATA_indication for U-plane data transfer

These primitives are the language of the ATS. They show what the test system sends and expects at each control or data point.

Reporting material for testing

Annex B and Annex C provide PIXIT proformas for the MT and AP sides, and Annex D and Annex E provide PCTR proformas for the MT and AP sides. In practice, the PIXIT forms collect the implementation details needed to run the ATS, and the PCTR forms record the outcome of the conformance campaign.

What terms does SIST EN 301 811-1-3 V1.1.1:2006 define?

• ATS (Abstract Test Suite) - The set of abstract test cases used to test the protocol behavior in a standardized way.
• PIXIT (Protocol Implementation Extra Information for Testing) - The implementation-specific information that a laboratory needs before executing the ATS.
• PCTR (Protocol Conformance Test Report) - The report form used to record the outcome of a conformance test campaign.
• IUT (Implementation Under Test) - The equipment or software being tested against the specified protocol behavior.
• PCO (Point of Control and Observation) - The interface point where the test system controls and observes the IUT.
• TTCN (Tree and Tabular Combined Notation) - The notation used to express the ATS in a structured test format.
• MT (Mobile Terminal) - The terminal side of the HIPERLAN Type 2 common part testing.
• AP (Access Point) - The access point side of the HIPERLAN Type 2 common part testing.

Who uses SIST EN 301 811-1-3 V1.1.1:2006?

SIST EN 301 811-1-3 V1.1.1:2006 is used by conformance test laboratories, equipment manufacturers, and engineering teams working on HIPERLAN Type 2 systems. It is especially relevant when a team needs to prepare a PIXIT, run ATS-based testing, or complete a PCTR for an MT or AP implementation.

Quality managers and buyers use it to understand what kind of conformance evidence a supplier should be able to provide. Test engineers use it to configure the remote tester, choose the MT or AP scenario, and record results in the prescribed report forms.

Which standards are used with SIST EN 301 811-1-3 V1.1.1:2006?

Reference	What it contributes
ETSI TS 101 493-1	The protocol specification for the BRAN HIPERLAN Type 2 packet based convergence layer, Common part
ETSI ETS 300 406	The ETSI conformance testing methodology and standardization rules used as a basis for the test method
ISO/IEC 9646-1	General concepts for conformance testing methodology and framework
ISO/IEC 9646-2	The method for Abstract Test Suite specification
ISO/IEC 9646-3	The Tree and Tabular Combined Notation (TTCN)
ISO/IEC 9646-6	Protocol profile test specification and the basis for the PIXIT and PCTR proformas
ISO/IEC 9646-7	Implementation Conformance Statements and related definitions
ETSI TS 101 811-1-2	The Test Suite Structure and Test Purposes (TSS&TP) specification that the ATS follows

What does the SIST EN 301 811-1-3 V1.1.1:2006 document contain?

The document contains the abstract test method for the common part packet based convergence layer, including the test architecture, MT and AP configurations, and the handling of untestable test purposes. It also contains the naming and implementation conventions that govern the TTCN test suite.

Annex A provides the ATS itself in TTCN graphical and machine-processable form. Annexes B and C provide the PIXIT proformas for collecting test setup information, and Annexes D and E provide the PCTR proformas for recording static and dynamic conformance results.

SLOVENSKI STANDARD
01-februar-2006
âLURNRSDVRYQDUDGLMVNDGRVWRSRYQDRPUHåMD%5$1±=HOR]PRJOMLYRUDGLMVNR
ORNDOQRRPUHåMH+,3(5/$1WLS±6SHFLILNDFLMD]DSUHVNXãDQMHVNODGQRVWL
SDNHWQHNRQYHUJHQþQHSODVWL±GHO6NXSQLGHO±SRGGHO$EVWUDNWQL
SUHVNXãDOQLQL]$76±6SHFLILNDFLMD
Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance testing
for the packet based convergence layer; Part 1: Common part; Sub-part 3: Abstract Test
Suite (ATS) specification
Ta slovenski standard je istoveten z: EN 301 811-1-3 Version 1.1.1
ICS:
33.060.01 Radijske komunikacije na Radiocommunications in
splošno general
35.110 Omreževanje Networking
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)
Broadband Radio Access Networks (BRAN);
HIPERLAN Type 2;
Conformance testing for the
packet based convergence layer;
Part 1: Common part;
Sub-part 3: Abstract Test Suite (ATS) specification

2 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
Reference
DEN/BRAN-0024T04-1-3
Keywords
access, ATS, HIPERLAN
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: [phone] Fax: [phone]
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://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
[e-mail]
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 2001.
All rights reserved.
ETSI
3 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
Contents
Intellectual Property Rights .6
Foreword.6
1 Scope.7
2 References.7
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.2 Test Configurations. 10
4.2.1 Test Configurations for MT. 10
4.2.2 Test Configurations for AP. 11
5 Untestable Test Purposes (TP) .11
6 ATS conventions .11
6.1 Naming conventions. 11
6.1.1 Declarations part. 11
6.1.1.1 General. 11
6.1.1.2 Test suite operations definition. 12
6.1.1.3 Test suite parameter declarations. 12
6.1.1.4 Test case selection expression definition . 12
6.1.1.5 Test suite constant declarations. 12
6.1.1.6 Test suite variable declarations. 12
6.1.1.7 Test case variable declarations . 12
6.1.1.8 Timer declarations. 13
6.1.1.9 ASP type definitions. 13
6.1.1.10 PDU type definitions . 13
6.1.1.11 CM type definitions. 13
6.1.1.12 Alias definitions . 13
6.1.2 Constraints part. 13
6.1.2.1 General. 13
6.1.3 Dynamic part . 14
6.1.3.1 General. 14
6.1.3.2 Test Case (TC) identifier. 14
6.1.3.3 Test step identifier . 14
6.1.3.4 Default identifier . 14
6.1.3.5 Label identifier . 14
6.1.3.6 ATS abbreviations. 15
6.2 Implementation conventions. 15
6.2.1 Declaration part . 15
6.2.2 Constraint part . 15
6.2.3 Dynamic part . 15
7 Abstract testing service primitives.16
7.1 Tester primitives. 16
7.2 C-plane primitives. 16
7.3 U-plane primitives. 16
ETSI
4 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
Annex A (normative): Abstract Test Suite (ATS).17
A.1 The TTCN Graphical form (TTCN.GR).17
A.2 The TTCN Machine Processable form (TTCN.MP) .17
Annex B (normative): Partial PIXIT proforma for H/2 Common part CL MT .18
B.1 Identification summary .18
B.2 ATS summary .18
B.3 Test laboratory.18
B.4 Client identification .19
B.5 SUT.19
B.6 Protocol layer information .19
B.6.1 Protocol identification . 19
B.6.2 IUT information . 19
Annex C (normative): Partial PIXIT proforma for H/2 Common part CL AP.20
C.1 Identification summary .20
C.2 ATS summary .20
C.3 Test laboratory.20
C.4 Client identification .21
C.5 SUT.21
C.6 Protocol layer information .21
C.6.1 Protocol identification . 21
C.6.2 IUT information . 21
Annex D (normative): PCTR Proforma for H/2 Common part CL MT.22
D.1 Identification summary .22
D.1.1 Protocol conformance test report. 22
D.1.2 IUT identification. 22
D.1.3 Testing environment. 23
D.1.4 Limits and reservation . 23
D.1.5 Comments. 23
D.2 IUT Conformance status .23
D.3 Static conformance summary .24
D.4 Dynamic conformance summary.24
D.5 Static conformance review report.24
D.6 Test campaign report .25
D.7 Observations.25
Annex E (normative): PCTR Proforma for H/2 Common part CL AP.26
E.1 Identification summary .26
E.1.1 Protocol conformance test report. 26
E.1.2 IUT identification. 26
E.1.3 Testing environment. 27
E.1.4 Limits and reservation . 27
E.1.5 Comments. 27
ETSI
5 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
E.2 IUT Conformance status .27
E.3 Static conformance summary .28
E.4 Dynamic conformance summary.28
E.5 Static conformance review report.28
E.6 Test campaign report .29
E.7 Observations.29
History .30
ETSI
6 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
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://www.etsi.org/ipr).
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 European Standard (Telecommunications series) has been produced by ETSI Project Broadband Radio Access
Networks (BRAN).
The present document is sub-part 3 of a multi-part deliverable covering Broadband Radio Access Networks (BRAN);
HIPERLAN Type 2; Conformance testing for the packet based convergence layer; Part 1: Common part, as identified
below:
Sub-part 1: "Protocol Implementation Conformance Statement (PICS) proforma";
Sub-part 2: "Test Suite Structure and Test Purposes (TSS&TP) specification";
Sub-part 3: "Abstract Test Suite (ATS) specification".
National transposition dates
Date of adoption of this EN: 19 January 2001
Date of latest announcement of this EN (doa): 30 April 2001
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 October 2001
Date of withdrawal of any conflicting National Standard (dow): 31 October 2001
ETSI
7 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
1 Scope
The present document contains the Abstract Test Suite (ATS) to test the BRAN HIPERLAN Type 2; Packet based
convergence layer; Part 1: Common part.
The objective of the present document is to provide a basis for conformance tests for HIPERLAN Type 2 equipment
giving a high probability of air interface inter-operability between different manufacturers' HIPERLAN Type 2
equipment.
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [3] and ISO/IEC 9646-2 [4]) as well as
the ETSI rules for conformance testing (ETS 300 406 [2]) 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
MT side ATS.
Annex C provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the
AP side ATS.
Annex D provides the Protocol Conformance Test Report (PCTR) Proforma of the MT side ATS.
Annex E provides the Protocol Conformance Test Report (PCTR) Proforma of the AP side ATS.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ETSI TS 101 493-1 (V1.1.1): "Broadband Radio Access Networks (BRAN); HIPERLAN Type 2;
Packet based Convergence Layer; Part 1: Common Part".
[2] ETSI ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[3] ISO/IEC 9646-1 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 1: General concepts". (See also ITU-T
Recommendation X.290 (1991)).
[4] ISO/IEC 9646-2 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 2: Abstract Test Suite specification". (See also ITU-T
Recommendation X.291 (1991)).
[5] ISO/IEC 9646-3 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
(See also ITU-T Recommendation X.292 (1992)).
[6] ISO/IEC 9646-6 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 6: Protocol profile test specification".
ETSI
8 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
[7] ISO/IEC 9646-7 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 7: Implementation Conformance Statements".
[8] ETSI TS 101 811-1-2 (V1.1.1): "Broadband Radio Access Networks (BRAN); HIPERLAN
Type 2; Conformance testing for the packet based convergence layer; Part 1:Common part;
Sub-part 2: Test Suite Structure and Test Purposes (TSS&TP) specification".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
a) The terms defined in ISO/IEC 9646-7 [7]; and
b) The definitions in TS 101 493-1 [1].
3.2 Abbreviations
For the purposes of the present document, the abbreviations defined in ISO/IEC 9646-1 [3], ISO/IEC 9646-6 [6],
ISO/IEC 9646-7 [7], the abbreviations defined in TS 101 493-1 [1] apply. In particular, the following abbreviations
apply:
AP Access Point
ARQ Automatic Repeat Request
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
ATSP Abstract Testing Service Primitives
BCH Broadcast CHannel
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
CA Capability tests
CC Central Controller
CL Convergence Layer
CPCS Common Part Convergence Sublayer
DCC DLC user Connection Control
DLC Data Link Control
DUC DLC User Connection
EC Error Control
H/2 HIPERLAN Type 2
IUT Implementation Under Test
LT Lower Tester
MAC Medium Access Control
MAC-ID MAC IDentifier
MT Mobile Terminal
MTC Main Test Component
PCO Point of Control and Observation
PCTR Protocol Conformance Test Report
PDU Protocol Data Unit
PHY Physical layer
PICS Protocol Implementation Conformance Statement
RLC Radio Link Control
SAP Service Access Point
SAR Segmentation and Reassembly
SDU Sevice Data Unit
SSCS Service Specific Convergence Sublayer
SUT System Under Test
ETSI
9 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
TC Test Cases
TCS Test Case Selection
TCV Test Case Variable
TP Test Purposes
TSO Test Suite Operations
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
TSP Test Suite Parameter
TSC Test Suite Constant
TSV Test Suite Variable
UT Upper Tester
4 Abstract Test Method (ATM)
This clause describes the ATM used to test the HIPERLAN 2 Common part PBCL layer at the AP side and at the MT
side.
4.1 Test architecture
Notional UT
Lower Tester
Loopback
CLU PCO
CL (ATS)
SUT
IN IT. SAR
CL (IUT)
CLC PCO
ARQ RLC ARQ
RLC
DLC/M AC
DLC/MAC
PHY PHY
Figure 1: Test architecture for Packet CL – Common part
A single-party testing concept is used, which consists of the following abstract testing functions:
Lower Tester A Lower Tester (LT) is located in the remote BRAN H/2 test system. It controls and observes the
behaviour of the IUT.
CL ATS: A Convergence Layer (CL) Abstract Test Suite (ATS) is located in the remote BRAN H/2 test
system. Contains part of SSCS functionalities for establishing a U-plane connection needed for
testing CL common part behaviour.
CLU PCO: U-plane. The first Point of Control and Observation (PCO) for Convergence Layer testing is
located at a SAR_SAP between the Common Part Convergence Sublayer (CPCS) and the SAR
sub-layer. All test events at the PCO are specified in terms of Abstract Testing Service Primitives
(ATSP defined in Clause 7) containing complete SAR SDU.
CLC PCO: C-plane. The second Point of Control and Observation (PCO) for Convergence Layer testing is
located at a SAP between the Service Specific Convergence Sublayer (SSCS) and the DLC layer.
All test events at the PCO are specified in terms of Abstract Testing Service Primitives (ATSP
defined in Clause 7) containing complete DLC SDU. To avoid the complexity of data
fragmentation and recombination testing, the SAP is defined below these functions.
ETSI
10 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
SAR: The Segmentation and Reassembly sub-layer of the Convergence layer - Common Part is
implemented in the test system outside the ATS. This allows implicit testing of the IUT's SAR
entity without any internal requirement of its implementation.
INIT: Part of a generic SSCS has to be simulated as an initialization process by the ATS to provide the
establishment of the U-plane needed for convergence layer testing.
Notional UT: No explicit upper tester (UT) exists in the system under test. Nevertheless, some specific actions to
cover implicit send events and to obtain feedback information are necessary for the need of the test
procedures. A black box covering these requirements is used in the SUT as a notional UT as
defined in ISO 9646 ([3] to [7]). This notional UT is part of the test system.
4.2 Test Configurations
4.2.1 Test Configurations for MT
Two configurations are defined for MT testing.
AP
MT
(IU T )
(T e ste r)
Figure 2: Normal configuration for MT
The normal configuration is defined and used for functionality that requires only interaction between the tested MT and
one AP.
Tester
MT
AP1
(IU T )
AP2
Figure 3: Handover configuration for MT
Thehandover configurationisusedwhentheMThastointeract withtwoAP. Inthatcase, thetwosimulatedAPare
configurable to be either a multi-sector AP or two separate AP. The concurrent TTCN facilities are used in this
configuration.
ETSI
11 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
4.2.2 Test Configurations for AP
Only one configuration is defined for AP testing.
MT
AP
(IU T )
(T e ste r)
Figure 4: Normal configuration for AP
The normal configuration is defined and used for functionality that requires only interaction between the tested AP and
one MT.
5 Untestable Test Purposes (TP)
This clause gives a list of TP, which are not implemented in the ATS due to the chosen ATM or other restrictions.
Table 1: Untestable TP
Test purpose Reason
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 the document ETS 300 406 [2] was considered.
6.1 Naming conventions
6.1.1 Declarations part
This subclause describes the naming conventions chosen for the elements of the ATS declarations part.
6.1.1.1 General
The following general rules apply for the name giving in the declarations part. All type definitions (simple type
definitions, structured type definitions, ASP type definitions and PDU type definitions) shall be written in uppercase.
All element names (structured type definition), parameter names (ASP type definition) and field names (PDU type
definition) shall be written in lowercase.
ETSI
12 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
Predefined types (e.g. BITSTRING[8]) are never used in structured type definitions, ASP type definitions or PDU type
definitions. Simple types are used instead.
6.1.1.2 Test suite operations definition
The test suite operation identifiers are composed of substrings in lowercase letters, except for standard prefix "TSO_".
An underscore character ("_") separates each substring.
EXAMPLE: TSO_substring
6.1.1.3 Test suite parameter declarations
The test suite parameter identifiers are composed of substrings in lowercase letters, except for the standard prefix
"TSP_". An underscore character ("_") separates each substring.
EXAMPLE 1: TSP_t_wait
If the test suite parameter references a Protocol Implementation Conformance Statement (PICS) item, the letter "C" is
addedtothe standardprefix.
EXAMPLE 2: TSPC_encryption_support
If the test suite parameter references a PIXIT item, the letter "X" is added to the standard prefix.
EXAMPLE 3: TSPX_pid
6.1.1.4 Test case selection expression definition
The test case selection expression identifiers are composed of substrings in lowercase letters, beginning with the prefix
"TCS_". An underscore character ("_") separates each substring.
6.1.1.5 Test suite constant declarations
The test suite constant identifiers are composed of substrings in lowercase letters, except for the prefix "TSC_".
An underscore character ("_") separates each substring.
If the test suite constant represents a system parameter, the complete name defined in the protocol standard [1] is used.
6.1.1.6 Test suite variable declarations
The test suite variable identifiers are composed of substrings in lowercase letters, except for the prefix "TSV_". An
underscore character ("_") separates each substring.
Complete names as defined in the protocol standard [1] are used.
6.1.1.7 Test case variable declarations
The test case variable identifiers are composed of substrings in lowercase letters, except for the prefix "TCV_". An
underscore character ("_") separates each substring.
Complete names as defined in the protocol standard [1] are used.
ETSI
13 ETSI EN 301 811-1-3 V1.1.1 (2001-01)
6.1.1.8 Timer declarations
Two types of timers can be identified:
1) Standardized:
- Those defined in the protocol standard [1], e.g. T201. They use exactly the same name as in the standard.
As there is a tolerance margin accepted for these timers, three values are needed:
- The maximum value allowed, which will use the suffix "_max",
- The minimum value allowed, which will use th
...