SIST EN 301 823-2-3 V1.1.1:2006
(Main)Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance testing for the Data Link Control (DLC) protocol; Part 2: Radio Link Control (RLC) sublayer; Sub-part 3: Abstract Test Suite (ATS) specification
Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance testing for the Data Link Control (DLC) protocol; Part 2: Radio Link Control (RLC) sublayer; Sub-part 3: Abstract Test Suite (ATS) specification
The document shall contain the TSS & TP for HIPERLAN/2 RLC (see work item DTS/BRAN-0020004-2). It covers both the Access Point and the Terminal side.
Š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) – 2. del: Podplast kontrole radijske povezave (RLC) – 3. poddel: Abstraktni preskušalni niz (ATS) specifikacija
General Information
Standards Content (Sample)
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) – 2. del: Podplast kontrole
radijske povezave (RLC) – 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 2: Radio Link Control (RLC) sublayer; Sub-
part 3: Abstract Test Suite (ATS) specification
Ta slovenski standard je istoveten z: EN 301 823-2-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 2: Radio Link Control (RLC) sublayer;
Sub-part 3: Abstract Test Suite (ATS) specification
2 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
Reference
DEN/BRAN-002T004-2-3
Keywords
access, ATS, HIPERLAN
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.:+33492944200 Fax:+33493654716
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-2-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 .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 . 12
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 . 13
6.1.1.11 CM type definitions. 13
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 . 16
6.1.3.6 ATS abbreviations. 16
6.2 Implementation conventions. 16
6.2.1 Declaration part . 16
6.2.2 Constraint part . 17
6.2.3 Dynamic part . 17
7 Abstract testing service primitives.17
7.1 Tester primitives. 17
7.2 Centralized mode primitives . 17
7.3 Direct mode primitives . 17
ETSI
4 ETSI EN 301 823-2-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 RLC 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 RLC 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 RLC 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.27
Annex E (normative): PCTR Proforma for H/2 RLC AP.28
E.1 Identification summary .28
E.1.1 Protocol conformance test report. 28
E.1.2 IUT identification. 28
E.1.3 Testing environment. 29
E.1.4 Limits and reservation . 29
E.1.5 Comments. 29
ETSI
5 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
E.2 IUT Conformance status .29
E.3 Static conformance summary .30
E.4 Dynamic conformance summary.30
E.5 Static conformance review report.30
E.6 Test campaign report .31
E.7 Observations.32
History .33
ETSI
6 ETSI EN 301 823-2-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 2: Radio Link Control (RLC)
sublayer, 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-2-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; Radio Link Control (RLC) sublayer [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-2 (V1.1.1): "Broadband Radio Access Networks (BRAN); HIPERLAN Type 2;
Data Link Control (DLC) Layer; Part 2: Radio Link Control (RLC) sublayer".
[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 CCITT
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 CCITT
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 CCITT 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-2-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-2-2 (V1.1.1): "Broadband Radio Access Networks (BRAN); HIPERLAN
Type 2; Conformance testing for the Data Link Control (DLC) protocol; Part 2: Radio Link
Control (RLC) sublayer; 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-2 [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-2 [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
DCC DLC user Connection Control
DFS Dynamic Frequency Selection
DLC Data Link Control
DM Direct Mode
DUC DLC User Connection
EC Error Control
IUT Implementation Under Test
LT Lower Tester
MTC Main Test Component
MAC Medium Access Control
MAC-ID MAC IDentifier
MT Mobile Terminal
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
RRC Radio Resource Control
SAP Service Access Point
SUT System Under Test
TC Test Cases
TP Test Purposes
ETSI
9 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UT Upper Tester
4 Abstract Test Method (ATM)
This clause describes the ATM used to test the HIPERLAN 2 RLC layer at the AP side and at the MT side.
4.1 Test architecture
Notional U T
SUT
Lower Tester
RCP PCO
RLC
RLC ARQ
(A TS)
(IU T)
DLC/M AC
DLC/M AC
PHY
PHY
Figure 1: Test architecture for RLC
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;
RLC ATS: a RLC Abstract Test Suite (ATS) is located in the remote BRAN H/2 test system;
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 (ATSP defined in Clause 7) 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-2-3 V1.1.1 (2001-01)
4.2 Test Configurations
4.2.1 Test Configurations for MT
Three 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.
Tester
MT2
MT1
(IU T )
AP
Figure 4: 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.
ETSI
11 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
4.2.2 Test Configurations for AP
Two configurations are defined for AP testing.
MT
AP
(IU T )
(T e ste r)
Figure 5: Normal configuration for AP
The normal configuration is defined and used for functionality that requires only interaction between the tested AP and
one MT.
Tester
AP
MT1
(IU T )
MT2
Figure 6: Direct mode configuration for AP
The direct mode configuration is used for direct mode testing. The test system simulates two MT. The two MT of the
test system are necessary to test the centralized initialization procedure of the direct mode. The concurrent TTCN
facilities are used in this configuration.
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
ETSI
12 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
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.
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.
ETSI
13 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
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 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 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 are used.
6.1.1.8 Timer declarations
Two types of timers can be identified:
1) Standardized:
- Those defined in the protocol standard, 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 the suffix "_min";
- The value actually implemented, with no suffix.
EXAMPLE 1: T201_max, T201_min, and T201.
2) Not standardized:
- Those not defined in the protocol standard, i.e. for execution use, e.g. a timer waiting for a response. These
timers begin with the prefix "T_", followed by a string in lowercase letters.
EXAMPLE 2: T_resp represents a timer for controlling the response time of the IUT.
6.1.1.9 ASP type definitions
The general conventions in Sublause 6.1.1.1 apply.
The identifier of an ASP type uses the same name as the name defined in the protocol standard.
6.1.1.10 PDU type definitions
The general conventions in Sublause 6.1.1.1 apply.
The PDU type identifier shall identify the related structure or type as defined in the protocol standard.
6.1.1.11 CM type definitions
The CM types are defined as the ASP types without sub-fields.
ETSI
14 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
6.1.1.12 Alias definitions
Alias definitions are not used.
6.1.2 Constraints part
This subclause describes the naming conventions chosen for the elements of the ATS constraints part.
6.1.2.1 General
Constraints shall be written with the first letter in uppercase, and the rest in lowercase.
The first part of the constraint declaration identifier name is equivalent to the corresponding type identifier used in the
declaration part. The second part of the name describes the content of this constraint.
EXAMPLE: Declaration part: HEADER_FIELD
Constraint part: Header_field_paging
6.1.3 Dynamic part
This subclause describes the naming conventions used for the elements of the ATS dynamic part.
6.1.3.1 General
All test cases shall be listed in the order in which they appear in the Test Suite Structure (TSS) and TP document.
6.1.3.2 Test Case (TC) identifier
The identifier of the test case is built in the same way as for the test purpose described in TS 101 823-2-2 [8], with the
exception that "TP" is replaced by "TC". The identifier of a TC is built according to Table 2.
ETSI
15 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
Table 2: TC naming convention
Identifier: TC_____
= side type AP Access Point
MT Mobile Terminal
= protocol group ACF Association control function
RRC Radio resource control
DUC DLC user connection
= functional module RA RBCH association
MA Mac Id assignment
LC Link_Capability
EN Encryption
AU Authentication
CK Common Key distribution
IT Info_Transfer
MT Multicast
DI Disassociation
KR Key refresh
AR Association rejection
RQ DFS Requesting
RP DFS Reporting
SH Sector Handover
RH Radio Handover
NH Network Handover
HR Handover rejection
SL Sleep
AL Alive
AB Absence
CS Centralized Mode Set-up
CR Centralized Mode Release
CM Centralized Mode Modify
CT Centralized Mode Reset
DS Direct Mode Set-up
DR Direct Mode Release
DM Direct Mode Modify
DY Direct Mode Relay
UM Unsupported message
= type of testing CA Capability Tests
BV Valid Behaviour Tests
BI Invalid Behaviour Tests
BO Inopportune Behaviour Tests
TI Timer Tests
= sequential number (000-999) Test Case Number
EXAMPLE: TP identifier: TP/MT/RRC/RP/BV-010
TC identifier: TC_MT_RRC_RP_BV_010
6.1.3.3 Test step identifier
The test step identifier is built of substrings in lowercase letters, preceded by a string of uppercase letters. Underscore
characters join the substrings. The first substring indicates the main function of the test step; e.g. PR for preamble,
PO for postamble, LTS for local tree and STP for general test step. The second substring indicates the purpose of the
step.
EXAMPLE: PO_release_duc
6.1.3.4 Default identifier
The default identifiers begin with the prefix "DF_", followed by a string in lowercase letters.
ETSI
16 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
6.1.3.5 Label identifier
The identifiers in the label column is built according to Table 3:
Table 3: Naming convention for verdict assignment identifier
Identifier:
CS Check State test step
DF DeFault
PO POstamble
PR PReamble
TS TestStep
= sequential number (00-99) Label number
6.1.3.6 ATS abbreviations
These abbreviations are used to shorten identifier names:
addr address
ack acknowledgement
bear bearer
cap capability
cfm confirm
chn channel
con connection
ctrl control
est establish
ext extension
id identification
ind indication
info information
max maximum
min minimum
par parameter
prop proprietary
rel release
req request
rsp response
std standard
sys system
6.2 Implementation conventions
6.2.1 Declaration part
The comment line of single element TTCN tables (e.g. test suite constants) is used to give a reference where the format
and content of the element is described in the relevant protocol standards. Any particularity of the element format or
content is described in the comment line.
The comment line in the header of multi element TTCN tables (e.g. ASP) is used to reference to the protocol standard.
The detailed comments are used to describe any particularity of the table.
In the ASP and PDU declarations the comment column is further used to give information about the parameter/field
value, in particular if the parameter/field contains a fixed spare value.
ETSI
17 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
6.2.2 Constraint part
The ASPs and PDUs are defined in a way that all relevant parameters/fields are parameterized. That improves the
transparency of the constraints in the dynamic part, as all values, which are relevant for the test, are always present.
Generally no modified constraints are used. This allows an easier reuse and adaptation of constraints if they are reused
in other test specifications.
The Comment line of a constraint always contains a reference to the relevant protocol standard.
The detailed comment footer is used to describe any particularity of the table.
6.2.3 Dynamic part
All events which are defined as a conformance requirement by the TP, causes a preliminary verdict PASS if the
requirement is met.
All invalid events are handled in the default tree. Only FAIL or INCONC verdicts are assigned in the default tree.
The preamble, the test body and the postamble have different defaults, which allows a specific verdict handling, e.g.
only INCONC verdicts are assigned in the preamble.
All verdict assignments are labelled. According to ISO 9646-3 [5], Annex E, Clause E.2, labels should be written to the
conformance log. This allows, for example, to identify where the test failed. To allow an exact identification of the
table, in which the verdict was assigned, the convention described in Sublause 6.1.3.5 is applied.
TP which are listed in the untestable TP list in Clause 5 are not considered in the ATS, thus these TC identifiers are
missing in the ATS and the numbering of the TC is not always continuous.
7 Abstract testing service primitives
7.1 Tester primitives
RLC_Configuration {parameters}
7.2 Centralized mode primitives
RLC_CM_request {MAC_ID, Length, SDU}
RLC_CM_indication {MAC_ID, Length, SDU}
7.3 Direct mode primitives
RLC_DM_request {Src_MAC_ID, Dst_MAC_ID, Length, SDU}
RLC_DM_indication {Src_MAC_ID, Dst_MAC_ID, Length, SDU}
ETSI
18 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
Annex A (normative):
Abstract Test Suite (ATS)
This ATS has been produced using the Tree and Tabular Combined Notation (TTCN) according to ISO/IEC 9646-3 [5].
The ATS was developed on a separate TTCN software tool and therefore the TTCN tables are not completely
referenced in the table of contents. The ATS itself contains a test suite overview part, which provides additional
information and references.
A.1 The TTCN Graphical form (TTCN.GR)
The TTCN.GR representations of this ATS is contained in an Adobe Portable Document Format™ file (hip2_test.PDF
contained in archive en_3018230203v010101p0.ZIP) which accompanies the present document.
A.2 The TTCN Machine Processable form (TTCN.MP)
The TTCN.MP representations corresponding to this ATS is contained in an ASCII file (hip2_test.MP contained in
archive en_3018230203v010101p0.ZIP) which accompanies the present document.
NOTE: Where an ETSI Abstract Test Suite (in TTCN) is published in both .GR and .MP format these two forms
shall be considered equivalent. In the event that there appears to be syntactical or semantic differences
between the two then the problem shall be resolved and the erroneous format (whichever it is) shall be
corrected.
ETSI
19 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
Annex B (normative):
Partial PIXIT proforma for H/2 RLC MT
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that
users of the present document may freely reproduce the PIXIT proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PIXIT.
The PIXIT Proforma is based on ISO/IEC 9646-6 [6]. Any needed additional information can be found in this
international standard document.
B.1 Identification summary
Table B.1
PIXIT Number:
Test Laboratory Name:
Date of Issue:
Issued to:
B.2 ATS summary
Table B.2
Protocol Specification: ETSI TS 101 761-2 V1.1.1
Protocol to be tested:
ATS Specification: ETSI TS 101 823-2-3 V1.1.1
Abstract Test Method: ETSI TS 101 823-2-3 V1.1.1, Clause 4
B.3 Test laboratory
Table B.3
Test Laboratory Identification:
Test Laboratory Manager:
Means of Testing:
SAP Address:
ETSI
20 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
B.4 Client identification
Table B.4
Client Identification:
Client Test manager:
Test Facilities required:
B.5 SUT
Table B.5
Name:
Version:
SCS Number:
Machine configuration:
Operating System Identification:
IUT Identification:
PICS Reference for IUT:
Limitations of the SUT:
Environmental Conditions:
B.6 Protocol layer information
B.6.1 Protocol identification
Table B.6
Name: BRAN H/2 - RLC layer ETSI TS 101 761-2 V1.1.1
Version:
PICS References:
B.6.2 IUT information
Void.
ETSI
21 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
Annex C (normative):
Partial PIXIT proforma for H/2 RLC AP
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that
users of the present document may freely reproduce the PIXIT proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PIXIT.
The PIXIT Proforma is based on ISO/IEC 9646-6 [6]. Any needed additional information can be found in this
international standard document.
C.1 Identification summary
Table C.1
PIXIT Number:
Test Laboratory Name:
Date of Issue:
Issued to:
C.2 ATS summary
Table C.2
Protocol Specification: ETSI TS 101 761-2 V1.1.1
Protocol to be tested:
ATS Specification: ETSI TS 101 823-2-3 V1.1.1
Abstract Test Method: ETSI TS 101 823-2-3 V1.1.1, Clause 4
C.3 Test laboratory
Table C.3
Test Laboratory Identification:
Test Laboratory Manager:
Means of Testing:
SAP Address:
ETSI
22 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
C.4 Client identification
Table C.4
Client Identification:
Client Test manager:
Test Facilities required:
C.5 SUT
Table C.5
Name:
Version:
SCS Number:
Machine configuration:
Operating System Identification:
IUT Identification:
PICS Reference for IUT:
Limitations of the SUT:
Environmental Conditions:
C.6 Protocol layer information
C.6.1 Protocol identification
Table C.6
Name: BRAN H/2 - RLC layer ETSI TS 101 761-2 V1.1.1
Version:
PICS References:
C.6.2 IUT information
Void.
ETSI
23 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
Annex D (normative):
PCTR Proforma for H/2 RLC MT
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that
users of the present document may freely reproduce the PCTR proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PCTR.
The PCTR proforma is based on ISO/IEC 9646-6 [6]. Any needed additional information can be found in the present
document.
D.1 Identification summary
D.1.1 Protocol conformance test report
Table D.1
PCTR Number:
PCTR Date:
Corresponding SCTR Number:
Corresponding SCTR Date:
Test Laboratory Identification:
Test Laboratory Manager:
Signature:
D.1.2 IUT identification
Table D.2
Name:
Version:
Protocol specification:
PICS:
Previous PCTR if any:
ETSI
24 ETSI EN 301 823-2-3 V1.1.1 (2001-01)
D.1.3 Testing environment
Table D.3
PIXIT Number:
ATS Specification:
Abstract Test Method: Remote test method, Embedded variant with notional UT
Means of Testing identification:
Date of testing:
Conformance Log reference(s):
Retention Date for Log reference(s):
D.1.4 Limi
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...