SIST ETS 300 497-2 E2:2003

SLOVENSKI STANDARD
SIST ETS 300 497-2 E2:2003
01-december-2003
'LJLWDOQHL]EROMãDQHEUH]YUYLþQHWHOHNRPXQLNDFLMH'(&7±6NXSQLYPHVQLN&,±
.QMLåQLFDSUHVNXãDOQLKSULPHURY7&/±GHO$EVWUDNWQLSUHVNXãDOQLQL]$76]D
NUPLOMHQMHGRVWRSDGRSODVWLSUHQRVQHJDPHGLMD0$&±3UHQRVQDUDGLMVND
]DNOMXþLWHY37
Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Test
Case Library (TCL); Part 2: Abstract Test Suite (ATS) for Medium Access Control (MAC)
layer - Portable radio Termination (PT)
Ta slovenski standard je istoveten z: ETS 300 497-2 Edition 2
ICS:
33.070.30 'LJLWDOQHL]EROMãDQH Digital Enhanced Cordless
EUH]YUYLþQHWHOHNRPXQLNDFLMH Telecommunications (DECT)
'(&7
SIST ETS 300 497-2 E2:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 497-2 E2:2003

---------------------- Page: 2 ----------------------

SIST ETS 300 497-2 E2:2003
EUROPEAN ETS 300 497-2
TELECOMMUNICATION February 1998
STANDARD Second Edition
Source: DECT Reference: RE/DECT-040094-2
ICS: 33.020
Key words: ATS, DECT, radio, testing
Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI) Test Case Library (TCL);
Part 2: Abstract Test Suite (ATS) for Medium Access Control
(MAC) layer - Portable radio Termination (PT)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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 1998. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 497-2 E2:2003
Page 2
ETS 300 497-2: February 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 497-2 E2:2003
Page 3
ETS 300 497-2: February 1998
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .9
3.1 Definitions .9
3.2 Abbreviations .9
4 Abstract Test Method (ATM).10
4.1 Description of ATM .10
4.2 Test strategy .11
5 Untestable Test Purposes (TP).12
6 ATS conventions (only applicable for PTC LT_TC) .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 .13
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.14
6.1.1.10 PDU type definitions .14
6.1.1.11 Co-ordination Message (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 .15
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 .16
6.2 Implementation conventions .16
6.2.1 Declaration part .16
6.2.2 Constraint part.16
6.2.3 Dynamic part .17
Annex A (normative): Abstract Test Suite (ATS), PTC LT_TC .18
A.1 The machine processable ATS (TTCN.MP) .18
A.2 The graphical ATS (TTCN.GR).18
Annex B (normative): Specification of PTC LT_MAC.19
B.1 General requirements .19
B.2 Additional requirements.19

---------------------- Page: 5 ----------------------

SIST ETS 300 497-2 E2:2003
Page 4
ETS 300 497-2: February 1998
Annex C (normative): Partial PIXIT proforma for DECT MAC . 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. 23
Annex D (normative): Protocol Conformance Test Report (PCTR) proforma for DECT MAC . 24
D.1 Identification summary. 24
D.1.1 Protocol conformance test report. 24
D.1.2 IUT identification. 24
D.1.3 Testing environment. 25
D.1.4 Limits and reservation . 25
D.1.5 Comments. 25
D.2 IUT Conformance status. 25
D.3 Static conformance summary. 25
D.4 Dynamic conformance summary. 26
D.5 Static conformance review report . 26
D.6 Test campaign report. 26
D.7 Observations. 27
Annex E (informative): Bibliography . 28
History. 29

---------------------- Page: 6 ----------------------

SIST ETS 300 497-2 E2:2003
Page 5
ETS 300 497-2: February 1998
Foreword
This second edition European Telecommunication Standard (ETS) has been produced by the Digital
Enhanced Cordless Telecommunications (DECT) Project of the European Telecommunications
Standards Institute (ETSI).
This ETS comprises nine parts, as follows:
Part 1: "Test Suite Structure (TSS) and Test Purposes (TP) for Medium Access Control (MAC)
layer";
Part 2: "Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Portable radio
Termination (PT)";
Part 3: "Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Fixed radio Termination
(FT)";
Part 4: "Test Suite Structure (TSS) and Test Purposes (TP) - Data Link Control (DLC) layer";
Part 5: "Abstract Test Suite (ATS) - Data Link Control (DLC) layer";
Part 6: "Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer - Portable radio
Termination (PT)";
Part 7: "Abstract Test Suite (ATS) for Network (NWK) layer - Portable radio Termination (PT)";
Part 8: "Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer - Fixed radio
Termination (FT)";
Part 9: "Abstract Test Suite (ATS) for Network (NWK) layer - Fixed radio Termination (FT)".
Transposition dates
Date of adoption of this ETS: 23 January 1998
Date of latest announcement of this ETS (doa): 31 May 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 November 1998
Date of withdrawal of any conflicting National Standard (dow): 30 November 1998

---------------------- Page: 7 ----------------------

SIST ETS 300 497-2 E2:2003
Page 6
ETS 300 497-2: February 1998
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 497-2 E2:2003
Page 7
ETS 300 497-2: February 1998
1 Scope
This European Telecommunication Standard (ETS) contains the Abstract Test Suite (ATS) to test the
DECT Portable Part (PP) Medium Access Control (MAC) layer.
The objective of this test specification is to provide a basis for approval tests for DECT equipment giving a
high probability of air interface inter-operability between different manufacturer's DECT equipment. This
test specification contains the ATS specification for testing of the MAC layer at the Portable radio
Termination (PT).
The ISO standard for the methodology of conformance testing (ISO/IEC 9646, parts 1 to 7 [13] to [19]) as
well as the ETSI rules for conformance testing in ETS 300 406 [9] are used as the basis for the test
methodology.
Test specifications for the Physical Layer (PHL) are provided in other DECT ETSs.
Annex A provides the Tree and Tabular Combined Notation (TTCN) part of this ATS.
Annex B provides the specification of the parallel test component LT_MAC.
Annex C provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of
this ATS.
Annex D provides the Protocol Conformance Test Report (PCTR) Proforma of this ATS.
2 Normative references
This ETS incorporates, by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 175-1: "Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI); Part 1: Overview".
[2] ETS 300 175-2: "Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI); Part 2: Physical layer (PHL)".
[3] ETS 300 175-3: "Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI); Part 3: Medium Access Control (MAC) layer".
[4] ETS 300 175-4: "Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI); Part 4: Data Link Control (DLC) layer".
[5] ETS 300 175-5: "Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI); Part 5: Network (NWK) layer".
[6] ETS 300 175-6: "Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI); Part 6: Identities and addressing".
[7] ETS 300 175-7: "Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI); Part 7: Security features".
[8] ETS 300 175-8: "Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI); Part 8: Speech coding and transmission".
[9] ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and
profile conformance testing specifications; Standardization methodology".

---------------------- Page: 9 ----------------------

SIST ETS 300 497-2 E2:2003
Page 8
ETS 300 497-2: February 1998
[10] ETS 300 474: "Digital Enhanced Cordless Telecommunications (DECT);
Generic Access Profile (GAP); Profile requirement list and profile specific
Implementation Conformance Statement (ICS) proforma".
[11] ETS 300 497-1: "Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI) Test Case Library (TCL); Part 1: Test Suite Structure
(TSS) and Test Purposes (TP) for Medium Access Control (MAC) layer".
[12] ETS 300 497-5: "Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI) Test Case Library (TCL); Part 5: Abstract Test Suite
(ATS) - Data Link Control (DLC) layer".
[13] 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)).
[14] 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)).
[15] ISO/IEC 9646-3 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 3:
The tree and tabular combined notation". (See also CCITT Recommendation
X.292 (1992)).
[16] ISO/IEC 9646-4 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 4:
Test realisation". (See also CCITT Recommendation X.292 (1992)).
[17] ISO/IEC 9646-5 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 5:
Requirements on test laboratories and clients for the conformance assessment
process". (See also CCITT Recommendation X.292 (1992)).
[18] ISO/IEC 9646-6 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 6:
Protocol profile test specification".
[19] ISO/IEC 9646-7 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 7:
Implementation conformance statement".
[20] 91/263/EEC: "Council Directive of 29 April 1991 on the approximation of the
laws of the Member States concerning telecommunications terminal equipment,
including the mutual recognition of their conformity" (Terminal Directive).
[21] TBR 6: "Digital Enhanced Cordless Telecommunications (DECT); General
terminal attachment requirements".
[22] TBR 10: "Digital Enhanced Cordless Telecommunications (DECT); General
terminal attachment requirements; Telephony applications".
[23] TBR 11 (1992): "Attachment requirements for terminal equipment for Digital
European Cordless Telecommunications (DECT) Public Access Profile (PAP)
applications".
[24] TBR 22: "Attachment requirements for terminal equipment for Digital Enhanced
Cordless Telecommunications (DECT) Generic Access Profile (GAP)
applications".

---------------------- Page: 10 ----------------------

SIST ETS 300 497-2 E2:2003
Page 9
ETS 300 497-2: February 1998
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this part of this ETS, the definitions given in ISO/IEC 9646-1 [13] and
ETS 300 175-1 [1] apply.
3.2 Abbreviations
For the purpose of this part of this ETS, the following abbreviations apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
CA Capability tests
CM Co-ordination Message
CP Co-ordination Point
DECT Digital Enhanced Cordless Telecommunication
DLC Data Link Control
FT Fixed radio Termination
IUT Implementation Under Test
LT Lower Tester
MAC Medium Access Control
MTC Main Test Component
PCO Point of Control and Observation
PDU Protocol Data Unit
PHL Physical Layer
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation Extra Information for Testing
PT Portable radio Termination
PTC Parallel Test Component
SAP Service Access Point
SUT System Under Test
TP Test Purposes
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UT Upper Tester

---------------------- Page: 11 ----------------------

SIST ETS 300 497-2 E2:2003
Page 10
ETS 300 497-2: February 1998
4 Abstract Test Method (ATM)
This clause describes the ATM used to test the DECT MAC layer protocol at the Portable radio
Termination (PT).
4.1 Description of ATM
Test System System Under Test
Upper Tester
Lower Tester
Main Test Component DLC-PDUs
Upper
(MTC)
layers
M AC-ASPs
Coordination
CP_TC
DLC-PDUs
m essages CP_MAC
PTC PTC
MAC-PDUs
LT_TC
LT_MAC
IUT
(M AC)
PHL-ASPs
with fram e num ber
PCO
PHL Service provider
Figure 1: Remote test method, embedded variant
A single-party testing concept is used, which consists of the following abstract testing functions:
PCO: the Point of Control and Observation (PCO) for MAC Layer testing is located at
the D-Service Access Point (D-SAP) between the MAC layer and the Physical
layer. All test events at the PCO are specified in terms of Physical Layer -
Abstract Service Primitives (PHL-ASPs) (frame number parameter added);
CP_TC: Co-ordination Point Test Case (CP_TC) is located between the Main Test
Component (MTC) and Parallel Test Component (PTC) LT_TC in the test
system. It is used for passing co-ordination messages between these two
testing functions;
CP_MAC: Co-ordination Point MAC (CP_MAC) is located between the MTC and PTC
LT_MAC in the test system. It is equivalent to the PCO used for Data Link
Control (DLC) layer testing in part 6 of this ETS. All co-ordination messages at
this CP are specified in terms of MAC-ASPs and DLC Protocol Data Units (DLC-
PDUs);

---------------------- Page: 12 ----------------------

SIST ETS 300 497-2 E2:2003
Page 11
ETS 300 497-2: February 1998
PTC LT_TC: the Lower Tester Parallel Test Component LT_TC (PTC LT_TC) is located in
the test system. It makes restricted use of the PCO by only observing the test
events in both directions. It assigns preliminary verdicts (the MTC assigns the
final verdict);
NOTE: This restricted use of the PCO is a non-ISO/IEC 9646-2 [14] application of the PCO.
PTC LT_MAC: The Lower Tester Parallel Test Component LT_MAC (PTC LT_MAC) is located
in the test system. It provides indirect control and observation of the
Implementation Under Test (IUT) during test execution, via the underlying
service-provider. It does not assign any verdicts;
MTC: The Main Test Component (MTC) is located in the test system. It is responsible
for creating and terminating the PTCs, managing the co-ordination points
CP_TC and CP_MAC, and computation of the final test case verdict;
Upper layers: No explicit Upper Tester (UT) exists in the test system. However, the System
Under Test (SUT) (upper layers) needs to carry out some UT functions to
achieve some effects of test co-ordination procedures.
The primitives used at the PCO (physical SAP) are defined according to ETS 300 175-2 [2] clause 7 and
associated subclauses.
The co-ordination messages used at CP_MAC co-ordination point are abstract primitives including
protocol data units and frames. The abstract primitives (MAC ASPs) are defined according to
ETS 300 175-3 [3] clause 8 and associated subclauses. Two abstract primitives for starting and stopping
the synchronization between the main test component and the parallel test component LT_MAC are
added for the needs of the tester. The protocol data units (DLC C-plane PDUs) are defined according to
ETS 300 175-4 [4] clause 7 and associated subclauses. The frames (DLC U-plane frames) are defined
according to ETS 300 175-4 [4] clause 12 and associated subclauses.
4.2 Test strategy
The ATM defined in subclause 4.1 requires the use of concurrent TTCN, which is specified in
Amendment 1 of ISO/IEC 9646-3 [15]. The parallel test components PTC_TC and PTC_MAC are,
however, seen as two independent entities. This means that there is no communication or synchronization
between the two PTCs during the test.
PTC_TC is specified in TTCN (see annex A). Since PTC_TC is only observing at the PCO, this ATS does
not contain any send statements. Once the Test Purposes (TP) are fulfilled, the PTC_TC terminates, i.e.
there are no post ambles, unless required by the TP. No explicit co-ordination messages is exchanged at
CP_TC. To simplify the TTCN test cases, the underlying service provider has been assigned the task of
frame numbering. Consequently, a frame parameter has been added to some of the PHL-ASPs.
The requirements for PTC_MAC (see annex B) are specified using ETS 300 474 [10].
The Main Test Component (MTC) creates the two PTCs (using CREATE operation), stimulates the
PTC_MAC (using MAC ASPs at CP_MAC) and then waits for the two PTCs to terminate (using the DONE
event). The final verdict is computed as follows:
- a PASS is assigned if PTC_TC returns a PASS verdict and the expected event is received from
PTC_MAC at CP_MAC;
- a FAIL verdict is assigned if PTC_TC returns a FAIL verdict independently of what is received from
PTC_MAC at CP_MAC;
- an INCONC verdict is assigned if:PTC_TC returns an INCONC verdict and the expected event is
received from PTC_MAC at CP_MAC, or returns a PASS verdict and an unexpected event is
received from PTC_MAC at CP_MAC.

---------------------- Page: 13 ----------------------

SIST ETS 300 497-2 E2:2003
Page 12
ETS 300 497-2: February 1998
5 Untestable Test Purposes (TP)
This clause gives a list of TP which are not implemented in the ATS for PTC LT_TC (see annex A) due to
the chosen ATM or other restrictions.
Table 1: Untestable TP
Test purpose Reason
TP/DB/BV-00 It is not possible to distinguish, without confusion, if the PT is unlocked or crashed.
TP/DB/BV-02 It is no possible to distinguish, without confusion, if the PT is unlocked or crashed.
TP/PG/BV-00 No procedure can be defined to verify that the Fixed radio Termination (FT) manages
correctly the paging Extended Flag when it transmit pages.
6 ATS conventions (only applicable for PTC LT_TC)
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 documents ETS 300 406 [9] and ETR 141 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.
All declarations in the test suite are listed in alphabetical order. A different order of listing should be used
for only maintenance reasons.
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_". Each substring is separated by an underscore character ("_").
EXAMPLE: TSO_substring

---------------------- Page: 14 ----------------------

SIST ETS 300 497-2 E2:2003
Page 13
ETS 300 497-2: February 1998
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_". Each substring is separated by an underscore character ("_").
EXAMPLE 1: TSP_t_wait
If the test suite parameter references a Protocol Implementation Conformance Statement (PICS) item, the
letter "C" is added to the standard prefix.
EXAMPLE 2: TSPC_extended_rf_carriers
If the test suite parameter references a PIXIT item, the letter "X" is added to the standard prefix.
EXAMPLE 3: TSPX_pmid
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_". Each substring is separated by an underscore character ("_").
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_". Each substring is separated by an underscore character ("_").
If the test suite constant represents a system parameter, the complete name defined in the protocol ETS
is used.
EXAMPLE: TSC_n200
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_". Each substring is separated by an underscore character ("_").
Complete names as defined in the protocol ETS 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_". Each substring is separated by an underscore character ("_").
Complete names as defined in the protocol ETS are used.
6.1.1.8 Timer declarations
Two types of timers can be identified:
1) standardised:
- those defined in the protocol ETS, e.g. T201. They use exactly the same name as in the
ETS.
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.

---------------------- Page: 15 ----------------------

SIST ETS 300 497-2 E2:2003
Page 14
ETS 300 49
...