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

SLOVENSKI STANDARD
01-februar-2006
Širokopasovna radijska dostopovna omrežja (BRAN) – Zelo zmogljivo radijsko
lokalno omrežje (HIPERLAN), tip 2 – Specifikacija za preskušanje skladnosti
protokola krmiljenja podatkovnih povezav (DLC) – 1. del. Funkcija za prenos
osnovnih podatkov – 3. poddel: Abstraktni preskušalni niz (ATS) – Specifikacija
Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance testing
for the Data Link Control (DLC) protocol; Part 1: Basic data transport function; Sub-part
3: Abstract Test Suite (ATS) specification
Ta slovenski standard je istoveten z: EN 301 823-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
Data Link Control (DLC) protocol;
Part 1: Basic data transport function;
Sub-part 3: Abstract Test Suite (ATS) specification

2 ETSI EN 301 823-1-3 V1.1.1 (2001-01)
Reference
DEN/BRAN-002T004-1-3
Keywords
access, ATS, basic, control, data, HIPERLAN,
radio, transport
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33492 94 4200 Fax: +33493 65 4716
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:
editor@etsi.fr
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 823-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 Error control service model for testing. 10
4.3 Test Configurations. 10
4.3.1 Test Configurations for MT. 10
4.3.2 Test Configurations for AP. 11
5 Untestable Test Purposes (TP) .12
6 ATS conventions .12
6.1 Naming conventions. 12
6.1.1 Declarations part. 12
6.1.1.1 General. 12
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 . 13
6.1.1.5 Test suite constant declarations. 13
6.1.1.6 Test suite variable declarations. 13
6.1.1.7 Test case variable declarations . 13
6.1.1.8 Timer declarations. 13
6.1.1.9 ASP type definitions. 13
6.1.1.10 PDU type definitions . 14
6.1.1.11 CM type definitions. 14
6.1.1.12 Alias definitions . 14
6.1.2 Constraints part. 14
6.1.2.1 General. 14
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 . 15
6.1.3.4 Default identifier . 15
6.1.3.5 Label identifier . 15
6.1.3.6 ATS abbreviations. 15
6.2 Implementation conventions. 16
6.2.1 Declaration part . 16
6.2.2 Constraint part . 16
6.2.3 Dynamic part . 16
7 Abstract testing service primitives.16
7.1 RLC PCO. 16
7.1.1 Tester primitives . 16
7.1.2 Centralized mode primitives. 16
7.1.3 Direct mode primitives. 17
7.2 Error control service PCO. 17
7.2.1 Tester primitives . 17
7.2.2 Acknowledge mode primitives . 17
7.2.3 U-plane exchange primitives . 17
7.3 Coordination between RLC and Error control . 17
ETSI
4 ETSI EN 301 823-1-3 V1.1.1 (2001-01)
Annex A (normative): Abstract Test Suite (ATS).18
A.1 The TTCN Graphical form (TTCN.GR).18
A.2 The TTCN Machine Processable form (TTCN.MP) .18
Annex B (normative): Partial PIXIT proforma for H/2 DLC Error Control MT .19
B.1 Identification summary .19
B.2 ATS summary .19
B.3 Test laboratory.19
B.4 Client identification .20
B.5 SUT.20
B.6 Protocol layer information .20
B.6.1 Protocol identification . 20
B.6.2 IUT information . 20
Annex C (normative): Partial PIXIT proforma for H/2 DLC Error Control AP.21
C.1 Identification summary .21
C.2 ATS summary .21
C.3 Test laboratory.21
C.4 Client identification .22
C.5 SUT.22
C.6 Protocol layer information .22
C.6.1 Protocol identification . 22
C.6.2 IUT information . 22
Annex D (normative): PCTR Proforma for H/2 DLC Error Control MT.23
D.1 Identification summary .23
D.1.1 Protocol conformance test report. 23
D.1.2 IUT identification. 23
D.1.3 Testing environment. 24
D.1.4 Limits and reservation . 24
D.1.5 Comments. 24
D.2 IUT Conformance status .24
D.3 Static conformance summary .25
D.4 Dynamic conformance summary.25
D.5 Static conformance review report.25
D.6 Test campaign report .26
D.7 Observations.26
Annex E (normative): PCTR Proforma for H/2 DLC Error Control AP.27
E.1 Identification summary .27
E.1.1 Protocol conformance test report. 27
E.1.2 IUT identification. 27
E.1.3 Testing environment. 28
E.1.4 Limits and reservation . 28
E.1.5 Comments. 28
ETSI
5 ETSI EN 301 823-1-3 V1.1.1 (2001-01)
E.2 IUT Conformance status .28
E.3 Static conformance summary .29
E.4 Dynamic conformance summary.29
E.5 Static conformance review report.29
E.6 Test campaign report .30
E.7 Observations.30
History .31
ETSI
6 ETSI EN 301 823-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 Data Link Control (DLC) protocol; Part 1: Basic data transport
function, 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 823-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; Data Link Control
(DLC) protocol; Part 1: Basic data transport functions [1].
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 761-1 (V1.1.1): "Broadband Radio Access Networks (BRAN); HIPERLAN Type 2;
Data Link Control (DLC) Layer; Part 1: Basic Data Transport Functions".
[2] ETSI ETS 300 406: "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 823-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 823-1-2 (V1.1.1): "Broadband Radio Access Networks (BRAN); HIPERLAN
Type 2; Conformance Testing for the Data Link Control (DLC) protocol; Part 1: Basic data
Transport function; 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 761-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 761-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
BCH Broadcast CHannel
BI Invalid Behaviour
BO inOpportune Behaviour
BV Valid Behaviour
CA CApability tests
CC Central Controller
CL Convergence Layer
DLC Data Link Control
DUC DLC User Connection
DCC DLC user Connection Control
DM Direct Mode
EC Error Control
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
SCH Short CHannel
SUT System Under Test
TC Test Cases
TSS Test Suite Structure
TP Test Purposes
TTCN Tree and Tabular Combined Notation
UT Upper Tester
ETSI
9 ETSI EN 301 823-1-3 V1.1.1 (2001-01)
4 Abstract Test Method (ATM)
This clause describes the ATM used to test the HIPERLAN 2 U-plane layer at the AP side and at the MT side.
4.1 Test architecture
D ata stream generation
Notional UT
and absorption
SUT
Lower Tester
RCP PCO
ARQ RLC
ARQ
RLC
ARQ PCO
(A TS)
(IU T)
DLC/M AC
DLC/MAC
PHY
PHY
Figure 1: Test architecture for Error Control (RLC needed for association, etc.)
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.
ARQ ATS: An ARQ Abstract Test Suite (ATS) is located in the remote BRAN H/2 test system.
ARQ PCO: The Point of Control and Observation (PCO) for ARQ testing is located at a SAP between the
Error Control layer and the MAC layer. All test events at the PCO are specified in terms of
Abstract Testing Service Primitives defined in Clause 7 and containing complete PDU. To avoid
the complexity of data fragmentation and recombination testing, the SAP is defined below these
functions.
RCP PCO: The Point of Control and Observation (PCO) for RLC testing is located at a SAP between the RLC
layer and the MAC layer. All test events at the PCO are specified in terms of Abstract Testing
Service Primitives defined in Clause 7 and containing complete PDU. To avoid the complexity of
data fragmentation and recombination testing, the SAP is defined below these functions.
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.
ETSI
10 ETSI EN 301 823-1-3 V1.1.1 (2001-01)
4.2 Error control service model for testing
Convergence Layer
ARQ
C ontrol Entity (ATS)
PCO
Error detection/
Buffer Handler
CRC generation
M AC
Figure 2: Error control service model for testing
Message Handler: Evaluate or generate CRC; Indicate erroneous PDU; Control read and write to or from
buffer handler; Add or Evaluate Sequence Number; Transmit or Receive PDU to or from
MAC and Convergence Layers controlled by the Control Entity.
Buffer Handler: Provide management of receive and transmit buffer.
Convergence Layer: Provide traffic generation and absorption capabilities.
Control Entity: Transmission: Handle the transmit window on a basis of sequence number; Evaluate ARQ
feedback messages (integrity check); Initiate re-transmission; Release correctly received
message from buffer; Handle errors (e.g. Initiation of Reset).
Reception: Handle the receive window including the knowledge of the buffer status;
Generate ARQ feedback messages; Trigger the message handler to pass correct in-sequence
PDU to the Convergence layer and to release buffer from the buffer handler; Handle errors
(e.g. Discarding).
4.3 Test Configurations
4.3.1 Test Configurations for MT
Tree configurations are defined for MT testing.
AP
MT
(IU T )
(T e ste r)
Figure 3: Normal configuration for MT
The normal configuration is defined and used for functionality that requires only interaction between the tested MT and
one AP.
ETSI
11 ETSI EN 301 823-1-3 V1.1.1 (2001-01)
Tester
MT
AP1
(IU T )
AP2
Figure 4: Handover configuration for MT
The handover configuration is used when the MT has to interact with two APs. In that case, the two simulated APs are
configurable to be either a multi-sector AP or two separate APs. The concurrent TTCN facilities are used in this
configuration.
Tester
MT2
MT1
(IU T )
AP
Figure 5: Direct mode configuration for MT
The direct mode configuration is used for direct mode testing. The test system simulates one AP and one MT. The AP
part of the test system is used to initialize the direct mode with the tested MT. The MT part of the system is used to
verify the communication of the tested MT when the direct mode is active. The concurrent TTCN facilities are used in
this configuration.
4.3.2 Test Configurations for AP
Only one configuration is defined for AP testing.
MT
AP
(IU T )
(T e ste r)
Figure 6: Normal configuration for AP
The normal configuration is defined and used for functionality that requires only interaction between the tested AP and
one MT.
ETSI
12 ETSI EN 301 823-1-3 V1.1.1 (2001-01)
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] were 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.
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
ETSI
13 ETSI EN 301 823-1-3 V1.1.1 (2001-01)
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.
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
...